IBM Developer for z/OS

IBM Developer for z/OS Enterprise Edition

16.0

Troubleshooting and Support

Last updated 2024-10-16

IBM
About this PDF
© International Business Machines Corporation 1992, 2024.

This PDF was generated from the content of the IBM® Developer for z/OS® online documentation. It is
provided for reference only. Many of the links in this PDF do not lead to a target location on the IBM
Developer for z/OS IBM Documentation site. For the most recent content, go to https://www.ibm.com/
docs/en/developer-for-zos/latest.
Some of the content in the IBM Developer for z/OS IBM Documentation site is embedded from other
IBM product documentation sites. Because of this content reuse, the embedded content might not be
included in the generated PDFs.
Troubleshooting and support
Diagnostic documents and support pages are available to help you troubleshoot some of the problems
you might encounter when you develop applications.For release notes, see Release notes.

Obtaining necessary diagnostic documents

General product log files
Developer for z/OS logs all information, warning, and severe error messages in a file called
workspace/.metadata/.log. A new .log file is created for each session of the workbench. If
a .log file exists, it is backed up as .bak_x.log, where x is a sequential number. You can also see
the contents of the log file in the Remote Error Log view. All messages are logged always. You do not
have to do anything to set logging levels or enable logging. The messages in the log file are intended
for user consumption.
For more information about collecting log files, see “Collecting log files” on page 3.
Trace messages
If you set the tracing level for components that support tracing, the product places these messages
in a file called workspace/.metadata/.trace. Trace messages consist of the detailed path of
execution for a product component and are intended for use by Developer for z/OS developers and
support staff, not for user consumption. The trace files are usually requested by the support team.
If trace is enabled, a new .trace file is created for each session of the workbench. If a .trace file
exists, it is backed up as .bak_x.trace.
For more information about setting the trace level for a component that is enabled for tracing, see
Tracing.
Db2® for z/OS Development tooling logs
The Db2 for z/OS Development tooling component of the product logs trace messages in the
metadata/.plugins/com.ibm.systemz.db2/logs folder of the Eclipse workspace.

IBM Support portal

The support page can be found here at IBM Support.
As problems are discovered and resolved, the IBM Support team updates the knowledge base at the IBM
Support portal. By searching the knowledge base, you can find workarounds or solutions to problems. To
find known issues for the product:
1. Open a browser on the IBM Support portal.
2. In the search field, type IBM Developer for z/OS and press Enter.
3. On the search results page:
a. Click Show filters.
b. Select Known issues.
c. Click Apply Filters.

Troubleshooting process overview

Troubleshooting is the process of finding and eliminating the cause of a problem. When you have a
problem with your IBM software, the troubleshooting process begins as soon as you ask yourself what
happened?
A basic troubleshooting strategy:
1. “Recording the symptoms of the problem” on page 2

© Copyright IBM Corp. 1992, 2024 1

 2. “Re-creating the problem” on page 2
3. “Eliminating possible causes” on page 2

Recording the symptoms of the problem

Depending on the problem, whether it is with your application, your server, or your tools, you might
receive a message that indicates that something is wrong. Always record the error message that you
see. As simple as this advice sounds, error messages often contain codes that make more sense as you
investigate your problem further. You might also receive multiple error messages that look similar, but
have subtle differences. By recording the details of each message, you can learn more about the problem.
Sources of error messages:
• Problems view in the workbench
• Console in the workbench
• Log files in your workspace
• Application log files
Note: If you encounter errors or exceptions, you can use the log files and application logging to research
the issues and find resolutions.
• Error dialog boxes

Re-creating the problem

Think back to what steps led you to this problem. Try those steps again to see whether you can easily
re-create this problem. If you have a consistently repeatable test case, you can more quickly determine
what solutions are necessary.
Consider the following questions:
• How did you notice the problem?
• Was anything done differently that made you notice the problem?
• Is the process that is causing the problem a new procedure, or has it worked successfully before?
• If this process worked before, what changed?
• The change can refer to any type of change that is made to the system. Changes might range from
adding new hardware or software to configuration changes you might make to existing software.
• When you noticed the first symptom of this problem, were there other symptoms that occurred around
that time?
• Does the same problem occur elsewhere? Does the problem occur on one computer or is it occurring on
multiple computers?
• What messages are generated that can indicate what the problem is? What else do you see that
indicates there is a problem?
• How often does the problem occur?

Eliminating possible causes

Narrow the scope of your problem by eliminating components that are not causing the problem. By using
a process of elimination, you can simplify your problem and avoid wasting time in other areas. Consult
the release information that comes with the product and other available resources to help you with your
elimination process.
Start with these questions:
• Has anyone else experienced this problem?
• Is there a fix that you can apply?

2 Developer for z/OS: Troubleshooting and Support

 • Have any fixes been applied or any changes made to the system that can be causing the problem? Does
rolling back the fix or the changes solve the problem?

Collecting log files

Use the Help > Collect Logs menu item to collect all or some of the Developer for z/OS client and server
log files and save them to a location on your workstation.
To collect server log files, you need to be authorized. Contact your systems administrator for authorization
to collect server log files.
Be sure that at least one connection to a z/OS system is defined in the Remote Systems view. While a
remote connection is required only for collecting server log files, selecting Help > Collect Logs when no
z/OS connection is defined causes an error message to display. This message prompts you to define a
z/OS connection.
You can collect the following client and server log files:
• Client user logs: The contents of the workspace/.metadata directory on the client. In this directory
path, workspace is the name of the Eclipse workspace that you specified when you started the client.
• Host user logs: The user log directory on the remote system and the ISPF work area on the remote
system. The user log directory contains the rsecomm.log and ffs*.log files for the user ID with
which you are logged on to the remote system.
• Host server logs: The contents of the server log directory, the remote system configuration files, and
output from the installation verification program. The server log directory contains the rse*.log files
and std*.log files.
• Host audit log: The audit.log file on the remote system.
• Limit logs to those updated in the last 24 hours: For Server logs, you can reduce the volume of log
data by selecting this option.
• Select an output location: Specify a location for the log files, or, to navigate to a location on your
workstation, click Browse.
1. From the menu bar, select Help > Collect Logs.
The Collect Logs window opens with the default selection to collect client user logs.
2. To collect server logs, select a remote system connection.
Tip: A remote system connection is not required to collect client logs, but at least one remote
connection must be defined.
3. Select the logs to collect.
4. In the Select an output location field, specify a location for the log files, or, to navigate to a location on
your workstation, click Browse.
5. Click OK.
If you selected any server log files, but you are not connected to the remote system, you are prompted
to log on. For server log files, the client sends a request to the server daemon to collect the log files
and opens a progress window.
6. To run the log collection request in the background, click Run in Background.
The collected log files are compressed into a .zip file and stored in the workstation location that you
specified.

Troubleshooting and support 3

Disabling logging in Eclipse-based products
When you run IBM products that are based on Eclipse, errors and warnings are captured automatically in
a log file. The information in the log file is useful for troubleshooting purposes; however, the file can use a
significant amount of space on the hard disk drive. You can delete .log files that you no longer need.

Accessing the IBM Support portal

You must be a registered user on the IBM Support portal to download fixes and to submit a problem
online to the IBM Support community.
1. Open the IBM Support portal.

2. Click to log in using your IBM.com username.

3. On the IBM Support portal, you can:
a) Search for known issues, documentation, and support forums.
b) Open a case or view cases you opened.
c) Open a chat window with a Support representative.
d) Open Fix Central to view product downloads and updates.
e) Access product documentation and support forums.
f) Manage your support account, including notifications, invoices, orders, contracts, and warranties.
For more information about notifications, see “Subscribing to product updates from the IBM
Support community” on page 5

Getting fixes
A product fix might be available to resolve your problem. You must determine what fixes and other
updates are available and install them appropriately.
Periodically, IBM might provide updates, such as interim fixes, fix packs, and refresh packs. For best
results, install the latest updates when they become available.
To access product fixes:
• If your product includes IBM Installation Manager:
a) Start Installation Manager.

4 Developer for z/OS: Troubleshooting and Support

 b) Click Update. Installation Manager searches the service repositories where fixes are located, and
lists the updates and fix packs that are available for installation.
c) If an update exists, complete the wizard.
• If you do not have the Installation Manager, search for and download fixes from the IBM Support
portal:
a) Open the IBM Support portal.
b) Click Downloads > Fixes, updates & drivers - Fix Central to open Fix Central.
c) Follow the instructions to search for and download product fixes.
To stay informed about new updates and fixes for your product, sign up for weekly email updates or
RSS feeds of support content. For more information, see “Subscribing to product updates from the IBM
Support community” on page 5.

Subscribing to product updates from the IBM Support community

To receive automatic updates when IBM publishes new support content for your products, subscribe to
weekly email updates or RSS feeds. Support content might include information about new releases, fixes,
technotes, APARs, and support flashes.
To sign up for email updates, you must be a registered user on the IBM Support community website.
To subscribe to email updates:
1. Open the IBM Support portal website.
2. Click to log in using your IBM.com username.
3. Click Manage support account > Notifications to view your notifications.
4. Type the product name in the search field or click Browse for a product.
5. Type the product name in the Product lookup field, or click Browse for a product.
6. Click Subscribe beside your product, and in the Select document types window, select the types of
documents for which you want to receive information. Click Submit.

Contacting IBM Support

If the self-help resources do not provide a resolution to your problem, you can contact IBM Support. IBM
Support assists in resolving product issues.
To submit your problem to IBM Support, you must have an active Passport Advantage® software
maintenance agreement. Passport Advantage is the IBM comprehensive software licensing and software
maintenance (product upgrades and technical support) offering. You can enroll online on the Passport
Advantage website.
• To learn more about Passport Advantage, see the Passport Advantage FAQs.
• For further assistance, contact your IBM representative.
To submit your problem online (from the IBM website) to IBM Support:
• Be a registered user on the IBM Support website. For details about registering, see Registering on the
IBM Support website.
• Be listed as an authorized caller in the service request tool.
1. Determine the business impact of your problem.
When you report a problem to IBM, you are asked to supply a severity level. Therefore, you must
understand and assess the business impact of the problem that you are reporting.
Option Description
Severity 1 The problem has a critical business impact: You are unable to use the program, resulting
in a critical impact on operations. This condition requires an immediate solution.

Troubleshooting and support 5

 Option Description
Severity 2 This problem has a significant business impact: The program is usable, but it is severely
limited.
Severity 3 The problem has some business impact: The program is usable, but less significant
features (not critical to operations) are unavailable.
Severity 4 The problem has minimal business impact: The problem causes little impact on
operations or a reasonable circumvention to the problem was implemented.
2. Describe your problem and gather background information,
When you describe a problem to IBM, be as specific as possible. Include all relevant background
information so that IBM Support specialists can help you solve the problem efficiently. To save time,
know the answers to these questions:
• What software versions were you running when the problem occurred?
To determine the exact product name and version, use the option applicable to you:
– Start the IBM Installation Manager and select File > View Installed Packages. Expand a
package group and select a package to see the package name and version number.
– Start your product, and click Help > About to see the offering name and version number.
• What is your operating system and version number (including any service packs or patches)?
• Do you have logs, traces, and messages that are related to the problem symptoms?
• Can you re-create the problem? If so, what steps do you complete to re-create the problem?
• Did you change anything on the system? For example, did you change the hardware, operating
system, networking software, or other system components?
• Are you currently using a workaround for the problem? If so, be prepared to describe the
workaround when you report the problem.
3. Submit your problem to IBM Support.
You can submit your problem to IBM Support in the following ways:
• Online: Open the IBM Support community website. Click Open a case to open a service request and
describe the problem in detail.
• By phone: For the phone number to call in your country or region, see the IBM Directory of
worldwide contacts and click the name of your country or geographic region.
• Through your IBM Representative: If you cannot access IBM Support online or by phone, contact
your IBM Representative. If necessary, your IBM Representative can open a service request for you.
You can find complete contact information for each country at IBM Directory of worldwide contacts.
If the problem you submit is for a software defect or for missing or inaccurate documentation, IBM
Support creates an Authorized Program Analysis Report (APAR). The APAR describes the problem in
detail. Whenever possible, IBM Support provides a workaround that you can implement until the APAR is
resolved and a fix is delivered. IBM publishes information about APARs on the IBM Support website daily
so that other users who experience the same problem can benefit from the same resolution.

Finding known problems for Developer for z/OS

Known problems are documented in the technotes in the IBM Support knowledge base.
As problems are discovered and resolved, the IBM Support team updates the knowledge base at the IBM
Support portal. By searching the knowledge base, you can find workarounds or solutions to problems. To
find known issues for the product:
1. Open a browser on the IBM Support portal.
2. In the search field, type IBM Developer for z/OS and press Enter.
3. On the search results page:

6 Developer for z/OS: Troubleshooting and Support

 a. Click Show filters.
b. Select Known issues.
c. Click Apply Filters.

Troubleshooting help problems

IBM Documentation has some requirements and limitations when accessed from Eclipse-based products.
You might experience any of the following problems opening the helps or populating the web browser
with help content.
• The help content pane is empty.
• A message indicates help is not available.
• A message indicates a network error.
• The browser opens with help content, but performance is slow.
For a list of the products in the Aqua product family that might be affected by the migration to IBM
Documentation, see IBM Explorer for z/OS Aqua Product Versions.
To solve some of the problems with IBM Documentation support for the IBM Explorer for z/OS Aqua
product family, follow these guidelines:
Use a supported browser:
The following browsers have been tested with the product and can open IBM Documentation. Other
browsers might not function correctly. To choose a browser:
1. On the Preferences window, click General > Web Browser.
2. Select Use external web browser, and then select one of these browsers.
• Windows: Chrome, Microsoft Edge
• macOS: Chrome, Safari
Open IBM Documentation in an external browser
On Windows, you must set Help preferences to use an external browser. IBM Documentation does not
support the internal Eclipse browser. On macOS helps open in an external browser by default, and the
preferences in this procedure are not available.
1. Open the Preferences window and click Help in the navigation pane.
2. From the Open help contents list, select In an external browser.
Update plugin_customization.ini
If you select Help > Help Contents to open the online help, you might see the message Help is
unavailable. This issue is caused by an error in the product plugin_customization.ini file. To
resolve this issue, do these steps:
1. Edit this file:

IBM Developer for

zOS\plugins\com.ibm.developer.for.zos.product_16.0.0.202210132216\plugin_
customization.ini
2. Change the org.eclipse.help.base/help_home= parameter from this:

org.eclipse.help.base/help_home=/com.ibm.wsentdev.doc/topics/
kc_version_welcome_rdz.html

to this:

org.eclipse.help.base/help_home=/com.ibm.etools.getstart.wsentdev.doc/topics/aintro.html

3. Restart the product.

4. Click Help > Help Contents.

Troubleshooting and support 7

 The product overview page opens in the online help.

Performance
You might notice a delay as the browser populates with the help content. The IBM Documentation
team is aware of performance issues and is working to improve the speed of populating the help
window.

Out-of-memory or script errors in Internet Explorer

If you receive out-of-memory or script errors while using online help, you might need to use a different
browser.
If you are using Internet Explorer to open the online help, you might receive error messages like the
following:
A script on this page is causing Internet Explorer to run slowly. If it continues to run, your
computer may become unresponsive.

Out of memory at line: number

This is a known problem with Internet Explorer and a workaround is to use a different browser. You can
choose another browser as follows:
1. On the Preferences window, click Help.
2. Click the Use external browser check box and then click Apply.
3. Expand the list of preference pages under General and then click Web Browser.
This page displays a list of browsers installed on your workstation.
4. Click the checkbox next to the browser you want to use and then click Apply.

z/OS Integrated Development Environment (zIDE) tools

Learn how to resolve common problems with the zIDE tools.

Allocate Like function fails with ISPF data set error

Resolve a data set error that can occur when you use the Allocate Like function.

Symptom
The Allocate Like function returns the following error:
ERROR MVSFileSystemMiner: FFS error: severity=12, msgNo=3001, opcode=42, rc=0, reason=0,
message=RC=8

MSG: ISPZ0003 Following function has failed:

8 Developer for z/OS: Troubleshooting and Support

 MSG: ISPF

MSG: ISPZ0012 Error in ISPF data set allocation: See error message below

MSG: ISPZ0013 Error in allocating the following DD and data set names:

MSG: DD=ISPMLIB

MSG: HLQ.DATASET.NAME

MSG: MSG: ISPZ0014 Verify that the ISPF configuration file ISPF.conf on the host is correct

Cause
All data sets in ISPF.CONF must have read permission for all users.

Resolving the problem

Ensure that all data sets specified in ISPF.CONF have read permission for all users.

Resizing columns causes another column to disappear

In any Developer for z/OS view, such as the Remote System Details view, dragging the vertical line that
divides columns to the left can cause the data column to the right to quickly slide left and overlay the data
column to its left.

Symptom
A column in a table view is lost.

Cause
This behavior is normal for Windows. The Eclipse platform and the Developer for z/OS client make internal
calls to Windows functions. You can see the same behavior in Windows Explorer.

Resolving the problem

Before you change the width of a column, maximize the view. You must avoid hiding any columns to the
right before you adjust the column width. You must first widen the view to avoid seeing the horizontal
scroll bar.

Solving problems with host-based projects

Most problems with host-based projects are the result of improper configuration on the remote system,
such as incorrect paths to definition files or errors in the syntax of the definition files themselves. Because
these problems usually show up as missing host-based projects, subprojects, or files, which are easily
overlooked, error messages help with problem determination.
For severe problems, a window box opens with a detailed message of the error condition and the
host-based project stops loading. Project creation actions that precede the error are not rolled back,
but, disconnecting from the remote system removes the projects from the workstation. For less
severe problems, such as a file listed in a subproject not being found, the message is logged in the
CommonBaseEvents log file. Users might not be aware of any such problem until they notice the missing
file and look into the log.
Problems with references to definition files
If a definition file contains an error in a reference to another definition file or to a folder, such as
typographical error or an error in a file path name, an error message indicates which file was not found
and which file contained the error.
Problems with syntax in definition files
If a definition file contains an error in the XML tags, such as a typographical error or a missing end tag,
the XML parser throws an exception and an error message indicates the definition file that contains
the error.

Troubleshooting and support 9

 Problems with references to resources
If a definition file refers to a partitioned data set, data set member, or sequential data set that cannot
be found, either because the definition file contains a typographical error or the file does not exist,
the subproject is created, but the file in error is not. An error message in the CommonBaseEvents
log (provided the logging level is set to SEVERE or lower for the com.ibm.ftt.projects.core.impl logger)
indicates which file was not found.

Solving problems with push-to-client configuration and implementation

Learning more about push-to-client can help you to avoid problems when you use this feature.

Overview of push-to-client
The Developer for z/OS push-to-client feature enables your site to store product updates, preferences,
and configurations in a central location on a remote system and automatically distribute them to client
workstations when users connect to that remote system.
To learn more about push-to-client, see the following topics:
• Distributing updates by using push-to-client
• Creating and distributing push-to-client files

Feature cannot be installed by using push-to-client

If you are distributing a product update to various operating systems, your response file must contain only
the list of features that are supported in all the target operating systems. If you are targeting Windows
XP and Windows 7 clients, for example, then your response file must not include the compilers feature
because it is not supported on Windows 7.

Symptoms
During a push-to-client product update, the user who attempts a product installation receives the
following error message on Windows:
Error: This feature cannot be installed because it is not supported on this operating system.

Causes
The push-to-client update operation is attempting to install a feature that the target operation system
does not support.

Resolving the problem

Edit the response file and remove the unsupported feature from the features attribute of the Developer
for z/OS <offering> tag.
Windows example:
If you are targeting Windows XP and Windows 7 clients, your response file must not include the
compilers feature because it is not supported on Windows 7. Remove com.ibm.rdz.compilers from the
features attribute of the <offering> tag.

Authentication with the Installation Manager repository

If the Installation Manager repository on which a push-to-client product update is stored requires
password authentication, users must store their user IDs and passwords in Installation Manager before
you attempt a push-to-client update.
When you attempt to install a product update by using push-to-client, users receive the following error
message:
WARNING: The following repositories are not connected:
repositoryAddress
(User authentication is required.)

10 Developer for z/OS: Troubleshooting and Support

 The repository on which the update is stored requires authentication with a user ID and password.
If the repository used for update requires user authentication to access, each user must save a user ID
and password in Installation Manager before you attempt to update the product.
1. Start Installation Manager.
2. Select File > Preferences.
3. Click Add Repository.
4. In the Repository field, specify the URL of a repository on the server for which you want to store your
credentials.
5. Click OK.
6. In the Password Required window, type your user ID and password, select Save password, and click
OK.
7. On the Preferences window, click OK.
8. Close Installation Manager.

Package names in response files

When you update the Developer for z/OS product by using push-to-client, a package name is required in
the response file. All users whose product installations are to be updated by using push-to-client must
install the Developer for z/OS product under the same package name that is used in the response file.
When you attempt to install a product update by using push-to-client, users receive the following error
messages:
• In an IBM Installation Manager command window:
ERROR: Cannot satisfy dependency
• In the update log file workspace/.metadata/.plugins/com.ibm.ftt.resources.zos/
responseFileName.log:
Installing PackageName is not allowed in this package group; it is not compatible with
installedPackageName. It may be installed in a different package group.

The response file for a product installation that is automated by using push-to-client records the package
name under which the Developer for z/OS product is installed. This package name must match the
package under which users installed the Developer for z/OS product. All users whose product installations
are updated by using push-to-client must install the Developer for z/OS product under the same package
name as the one recorded in the response file.

Solving problems with remote connections

Learn how to resolve common problems with remote connections.

RSE returns message RSEG1242 on connection attempt

The Developer for z/OS message RSEG1242 Daemon failed to launch server on host using
port port can have the following details: CONNECTION REFUSED or SERVER FAILURE.

Symptom
When you attempt to connect to a remote system, you receive error message RSEG1242.

Diagnosing the problem

When you see CONNECTION REFUSED with the message, the Remote System Explorer daemon is not
active. When you see SERVER FAILURE with the message, your client contacted the remote system but
became disconnected.

Troubleshooting and support 11

 Resolving the problem
CONNECTION REFUSED
1. Check RSED job output in SDSF (Spool Display and Search Facility) for an indication that the RSE
daemon is not using the port that is specified by the client. The RSE daemon is not running.
2. Check console message FEK002I (syslog or RSE daemon job output) for an indication that a
firewall or other network issue is blocking the client from accessing the RSE daemon port. (Port 0
in the RSEG1242 message normally indicates the RSE daemon).
3. Try telnet from the client workstation to the RSE daemon port (the connection hangs for 30
seconds if successful, but a firewall displays a message).
telnet host port
4. If the client can access the RSE daemon, but not the RSE server due to firewall issues (typically
indicated by a nonzero port number in the RSEG1242 message), alter the _RSE_PORTRANGE in
rse.env.
SERVER FAILURE
The detailed remote system logs show the error message that is shown in rseserver.log (only if
the RSE daemon or server was reached):
ERROR RseDaemon: server failure: password revoked

1. In this case, view the detailed remote system logs to see which part of the code failed.
2. Set debug_level=2 in /etc/zexpl/rsecomm.properties and restart the RSE daemon or use the
operator commands to dynamically activate tracing:

F RSED,APPL=RSL ON and F RSED,APPL=RCL ON

3. After you re-create the problem, customize and run FEK.SFEKSAMP(FEKLOGS).

4. Create a service request PMR and send the output to your IBM customer support representative.

RSE returns RSEG1242 PassTicket Generation Error

When you start the RSE daemon with the Developer for z/OS client, you might see the error message
RSEG1242 PassTicket Generation Error.

Cause
The PassTickets were not configured. Although early versions of the product require PassTickets, they
attempt to connect by using the server's ID upon a PassTicket error. Later versions, however, do not
attempt to connect by using the server's ID, but generate a PassTicket error.

Resolving the problem

Refer to "Define PassTicket support for RSE" in IBM Developer for z/OS in the Host Configuration Guide.

Remote system node name not found

When the RSE daemon is started with the Developer for z/OS product by using the parameter IVP=IVP,
the listing shows an incorrect host node name for the remote system.

Symptom
The NODENAME shown in the "host IP address" section of the listing, as shown in the following example,
is incorrect:

-------------------------------------------------------------
host IP address:
-------------------------------------------------------------
hostName=NODENAME
hostAddr=9.42.112.75
bindAddr=9.42.112.75
localAddr=9.42.112.75

12 Developer for z/OS: Troubleshooting and Support

 Cause
The host name resolution failed. This error can have several causes.

Diagnosing the problem

In a z/OS UNIX System Services prompt, type the following command:

hostname -r

If this command returns the wrong host name, then the Developer for z/OS product does not function and
can return the following error message.

EZZ8342I gethostbyname(NODENAME): Unknown host

Resolving the problem

1. Refer to the Host Configuration Reference for information about how to set up TCP/IP and how host
name resolution works.
2. If, after you complete the instructions in the Host Configuration Reference, the problem is not solved,
look for the following line in SYS1.PARMLIB(COMMNDxx):

S EZAZSSI,P=NODENAME

If this line is present, change NODENAME to the correct host name. You can use the symbolic value
&SYSNAME:

S EZAZSSI,P='&SYSNAME.'

Connecting using SSL results in secure socket init() failed error

Attempts to connect to the remote system with an SSL connection result in the error secure socket
init() failed: Socket closed by remote.

Symptom
Clients are unable to connect to the host with an SSL connection. The FEKIVPD job fails when SSL is
enabled.

Cause
The z/OS server must have the Root and the Intermediate certificates added to the key ring. It necessary
to ensure that the exact name of both the Root and the Intermediate certificates exist in the z/OS key ring.

Diagnosing the problem

GSK SSL traces on the host show which specific certificates are being requested. Use racdcert
certauth list commands to display the certificates on the remote system.

Resolving the problem

The remote system server must have the applicable Root and Intermediate certificates in the key ring.

Cannot create an MVS subproject

An attempt to create an MVS™ subproject fails with a duplicate name message.

Symptom
When you attempt to create an MVS subproject, you receive the following message: A subproject
with the same name already exists in the project.

Troubleshooting and support 13

 Diagnosing the problem
This message can be displayed when a previous attempt to create an MVS subproject with the same name
ended incompletely. This situation can occur when, for example, you chose this same MVS subproject
name but ended the subproject creation operation partway through the definition.

Resolving the problem

1. Click Window (on Windows) or IBM Developer for z/OS (on macOS) > Show View > Other > General
> Navigator.
2. From the Navigator view menu, select Filters.
3. Clear the wdz_proj_* checkbox.
4. Look for a subproject named wdz_proj_duplicate_name, in which duplicate_name is the subproject
name that generated the error.
5. Delete this subproject.
6. From the Navigator view menu, select Filters.
7. Select the wdz_proj_* checkbox. You can now create the subproject with the duplicate name.

Messages
The topics in this portion of the documentation document messages that have a unique identifier.
Most message IDs have the format xnnnnL, where:
x
A prefix 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

Client messages
The topics in this portion of the documentation contain information about the client messages.
Most client message IDs have the format CRRZcnnnnL, where:
CRRZ
The message prefix for the product
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

Messages for BMS Screen Designer (BMS Map Editor)

0100-level messages
CRRZB0136E Errors occurred. Follow the instructions or look up the message
that is provided in the message window as further
Explanation: explanation.
This message is typically displayed when some type
of validation is in progress, and further explanation is CRRZB0137E The field name is a duplicate.
provided. Explanation:
User response:

14 Developer for z/OS: Troubleshooting and Support

The field name is the same as another field name in Explanation:
the map. A column cannot be empty.
User response: User response:
Change the field name to a unique field name. Specify content for the column.
CRRZB0138E The length of the field name CRRZB0145E The row value is not valid.
exceeds 30 characters.
Explanation:
Explanation: The value that is used for the row is not allowed.
The length of a field name cannot exceed 30
User response:
characters.
Change the value to an allowed entry.
User response:
CRRZB0146E The column value is not valid.
Specify a field name whose length is 30 or fewer
characters. Explanation:
The value that is used for the column is not allowed.
CRRZB0139E The field name contains an invalid
@ character. User response:
Change the value to an allowed entry.
Explanation:
A field name cannot contain the @ character. CRRZB0147E Row or column values are not
valid.
User response:
Specify a field name that does not contain the @ Explanation:
character. The value that is used for the row or column is not
allowed.
CRRZB0140E The field name contains one or
more spaces. User response:
Change the value to an allowed entry.
Explanation:
A field name cannot contain spaces. CRRZB0148E The field position or length is not
valid.
User response:
Specify a field name that does not contain spaces. Explanation:
The value that is used for the field position or length is
CRRZB0141E The field name does not start with
not allowed.
an alphabetic character.
User response:
Explanation:
Change the value to an allowed entry.
The field name must start with an alphabetic
character. CRRZB0149E The group name exceeds 30
characters.
User response:
Choose a field name that starts with an alphabetic Explanation:
character. A group name cannot exceed 30 characters.
CRRZB0142E The length of the initial value User response:
exceeds the field length. Specify a group name whose length is 30 or fewer
characters.
Explanation:
The length of the initial value cannot exceed the field CRRZB0150E An OCCURS value is specified
length. when a group name is specified.
User response: Explanation:
Specify an initial value whose length does not exceed You cannot specify an OCCURS value if a group name
the field length. is specified.
CRRZB0143E The row is empty. User response:
Specify either an OCCURS value or a group name.
Explanation:
A row cannot be empty. CRRZB0151E The field name contains an invalid
character not supported by the
User response:
Mapset language.
Specify content for the row.
Explanation:
CRRZB0144E The column is empty.

Troubleshooting and support 15

The characters in field names must conform to the Explanation:
character set that is supported by the programming A row must be a numeric value.
language of the application that uses the map.
User response:
User response: Specify a row that is a numeric value.
Refer to the appropriate Language Reference manual
CRRZB0158E The column is not a numeric value.
for information about supported characters.
Explanation:
CRRZB0153E The name contains one or more
A column must be a numeric value.
spaces.
User response:
Explanation:
Specify a numeric value for the column.
A name cannot contain spaces.
CRRZB0182E No column is defined.
User response:
Specify a name that does not contain spaces. Explanation:
At least one column must be defined.
CRRZB0154E The map name is a duplicate.
User response:
Explanation:
Define a column.
The map name must be unique.
CRRZB0183E The total width exceeds the
User response:
defined table width.
Specify a unique map name.
Explanation:
CRRZB0155E The length of the map name
The sum of the width of the columns in the table is
exceeds 30 characters.
greater than the table width.
Explanation:
The length of a map name cannot exceed 30 User response
characters.
Do one of the following steps:
User response:
• Adjust the columns so that their sum is less than or
Specify a map name whose length is 30 or fewer
equal to the table width.
characters.
• Adjust the table width so that it is greater than or
CRRZB0156E The map name contains an invalid equal to the sum of the column width.
@ character.
CRRZB0192E No map has been selected.
Explanation:
A map name cannot contain the @ character. Explanation:
You must select at least one map.
User response:
Specify a map name that does not contain the @ User response:
character. Select one or more maps.
CRRZB0157E The row is not a numeric value.

0200-level messages
CRRZB0270E An error occurred when creating a User response:
nested text editor. Contact IBM Software Support.
Explanation: CRRZB0272W This map set will not assemble
A nested text editor is a text editor that is part of a correctly. A map must be specified
multi-page editor. For the BMS editor, the Source page for this map set.
is the nested text editor. In this case, there was a Explanation:
problem when the Source page was created. The map set does not contain any maps.
User response: User response:
Try closing the BMS file and opening it again. Using the palette that is associated with the editor,
CRRZB0271E The input is not valid; it must be select the map, and then select the design canvas to
IFileEditorInput. create a map.
Explanation:
The BMS editor is expecting a different type of input.

16 Developer for z/OS: Troubleshooting and Support

CRRZB0273W This map set will not assemble CRRZB0297E No name has been specified for
correctly. At least one field must the map set.
be specified for each map.
Explanation:
Explanation: A name must be specified for the map set.
A map in the map set does not contain any fields.
User response:
User response: Specify a name for the map set.
Using the palette that is associated with the editor,
CRRZB0299E The file name does not end in ".
select a field, and then select the design canvas to
{0}".
create a field.
Explanation:
CRRZB0296E The specified map set name is not
The file name must end in the particular file name
valid.
extension.
Explanation:
User response:
A map set name that contains one or more invalid
Specify a file name that ends in the required file name
characters was specified.
extension.
User response:
Specify a map set name that contains any of the
following characters: letters; digits; the symbols #, $,
and @

0300-level messages
CRRZB0306E No valid location is selected. Specify a length that is not greater than the limit.
Explanation: CRRZB0364I A portion of the caption will be
A valid location must be selected. trunctated.
User response: Explanation:
Select a valid location. The length of the caption exceeds the available space
in the caption.
CRRZB0360E No valid field name is entered.
User response:
Explanation:
No action is required. To display the entire caption,
You must enter a valid field name.
increase the length of the Caption field, or decrease
User response: the length of the caption text.
Enter a valid field name.
CRRZB0367I A portion of the initial value will be
CRRZB0361E No valid input field length is truncated.
specified.
Explanation:
Explanation: The length of the initial value exceeds the available
You must specify a valid input field length. space.
User response: User response:
Specify a valid input field length. No action is required. To display the entire initial value,
decrease the length of the initial value or increase the
CRRZB0362E No valid label field length is size of the field that is associated with the initial value.
specified.
CRRZB0377I A dynamic web project has not
Explanation:
been created.
You must specify a valid label field length.
Explanation:
User response: You must create a dynamic web project first.
Specify a valid label field length.
User response:
CRRZB0363E The length of the fields is greater Create a dynamic web project.
than {0}.
CRRZB0381I The file should be saved. Would
Explanation:
you like to save the file now?
The length of the fields cannot be greater than the
limit that is shown in the message. User response:
Save the file to prevent losing any changes.
User response:

Troubleshooting and support 17

CRRZB0396E No map has been selected. User response:
Select one or more maps.
Explanation:
You must select at least one map.

0400-level messages
CRRZB0401E The number of rows exceeds {0} CRRZB0443E The field distance is not between 1
rows. and 99.
Explanation: Explanation:
The number of rows cannot exceed the maximum that The field distance must be 1 - 99.
is shown in the message.
User response:
User response: Specify a field distance in the range 1 - 99.
Specify a number of rows that does not exceed the
CRRZB0444E The dimensions of the structure
maximum.
exceed the available space.
CRRZB0402E The defined number of rows is not
Explanation:
an integer.
The structure is too large.
Explanation:
User response:
The defined number of rows must be an integer.
Make the structure smaller.
User response:
CRRZB0448W The field positions specified will
Define the number of rows to be an integer.
cause overlapping.
CRRZB0403E Column {0} has an invalid field
Explanation:
prefix defined.
The values that are entered for the field positions
Explanation: overlap.
The prefix that is defined for the column that is shown
User response:
in the message is not valid.
Enter values that do not overlap.
User response:
CRRZB0449E The BMS file name is a duplicate.
Specify a valid field prefix.
Explanation:
CRRZB0404W The total width exceeds the
The value that is entered for the BMS file is already in
defined table width. {0} characters
use.
will be truncated.
User response:
Explanation:
Specify a unique file name.
The content of the table is too wide for the table.
CRRZB0450I {0} was added to the MVS
User response:
subproject {1}.
Make the table wider or the contents narrower.
CRRZB0441E An invalid value was specified Explanation
for an OCCURS clause. Enter a
numeric value between 1 and 99. {0}
name of the generated symbolic map
Explanation:
An OCCURS clause entry has an invalid value. {1}
name of the MVS subproject
User response:
Determine the position of the invalid value and enter a A symbolic map was generated and added to the
numerical value 1 - 99. specified MVS subproject.

CRRZB0442E The field length is not numeric and User response:

between 1 and 99. No action is required.

Explanation: CRRZB0455I A symbolic map has been created.

The field length must be numeric and 1 - 99. Explanation:
User response: The symbolic map was created successfully in the
Specify a numeric field length in the range 1 - 99. destination location you specified.
User response:

18 Developer for z/OS: Troubleshooting and Support

No action is required. Explanation:
The alternative map name starts with an invalid
CRRZB0456I The symbolic map file has been
character.
created.
User response:
Explanation:
Remove the invalid character and ensure that the
The symbolic map was created successfully in the
alternative map name begins with a character from the
destination location you specified.
set [a-Z].
User response:
CRRZB0461E The value entered in the alternate
No action is required.
map name is invalid.
CRRZB0457E The file name is not valid.
Explanation:
Explanation: The name that is provided as the alternative map
The specified file name is not valid. name is not valid.
User response: User response:
Specify a valid file name. Provide a valid alternative map name.
CRRZB0458E A duplicate file name was CRRZB0462E The alternate map name contains
specified. one or more spaces.
Explanation: Explanation:
The specified file name is already used. The alternative map name cannot contain spaces.
User response: User response:
Specify a unique file name. Remove all spaces from the alternative map name.
CRRZB0459E The initial value can only contain CRRZB0466I A file has been added to the MVS
numeric characters for a Numeric subproject.
only field.
Explanation:
Explanation: A newly generated BMS file was added to the MVS
Input other than numeric characters was provided to a subproject by the new BMS map set wizard.
numeric field.
User response:
User response: No action is required.
Remove any non-numeric characters in the numeric
field.
CRRZB0460E The first character in the alternate
map name entered is invalid.

Messages for Common Access Repository Manager (CARMA)

These are the messages that pertain to the Common Access Repository Manager (CARMA).

0200-level messages
CRRZC0201E CRASERV: The communication is The CARMA server received a request for an unknown
not formatted correctly. function. Version mismatch between the CASERV load
module and the CARMA RSE miner can cause unknown
Explanation: functions to be called.
The communication to the CARMA server was not
formatted correctly. A non-EBCDIC host code page System programmer response:
that is set for the CARMA connection can cause Verify that all host PTFs are properly installed and
incorrectly formatted communication. configured.
User response: User response:
Disconnect from the CARMA server, check the Contact your system programmer.
host code page setting for the CARMA connection, CRRZC0203E CRASERV: CARMA has not been
reconnect, and try the action again. initialized.
CRRZC0202E CRASERV: Unknown function Explanation:
Explanation:

Troubleshooting and support 19

A CARMA function was called before CAMA was CRRZC0210E CRASERV: A valid locale was not
initialized. provided.
User response: Explanation:
Disconnect from CARMA, reconnect, and try the action The value that is specified for the local was invalid.
again.
User response:
CRRZC0204E CRASERV: The command was In the client, disconnect from CARMA, open the
canceled. CARMA preferences, and specify a valid local
parameter. Reconnect and try your action again.
Explanation:
The CARMA server received a request to cancel the CRRZC0211E CRASERV: Expected parameters
command. were not passed.
User response: Explanation:
No action required. An expected parameter was not provided to the
CARMA server from the client.
CRRZC0205E CRASERV: Could not allocate
enough memory. User response:
If you receive this error when you are performing an
Explanation:
action against a repository instance or the RAM itself,
The CARMA server was unable to allocate memory.
make sure the CARMA host components (CARMA
User response: server) are updated to the same level as the client.
In the client, disconnect, reconnect, and try again. If it If you are using a custom client, have your client
persists, increase the amount of memory available in developer confirm the custom action ID is properly
the address space. provided to the perform action method.
CRRZC0207E CRASERV: Error encountered CRRZC0212E CRASERV: The contents were not
writing to the socket. provided.
Explanation: Explanation:
The CARMA server was unexpectedly unable to write CRASERV did not receive contents from the CARMA
to the socket. server for the putMember action.
User response: User response:
No action is required. CARMA automatically attempts Try your upload again, possibly with a different code
to reconnect. If this problem persists, have your page. You can change the host code page for an
system programmer check your TCP/IP settings. individual member in the properties for that member.
CRRZC0208E CRASERV: The RAM id is not valid. CRRZC0213E CRASERV: Internal error
Explanation: Explanation:
The client attempted to connect to a RAM ID that is not An unexpected, internal error occurred.
valid. Most likely, this error is caused when the client
User response:
attempts to connect to or perform an action against
Disconnect from CARMA, reconnect, and try your
a RAM ID that is not valid. A change in the host RAM
action again. If the problem persists, contact support.
configuration can cause a RAM ID to become invalid.
CRRZC0214E CRASERV: The instance ID or filter
User response:
Restart the workbench and connect to CARMA before was not provided.
you attempt any CARMA actions. Explanation:
CRRZC0209E The CARMA server did not receive the expected
CRASERV: The trace level is not
instance ID or filter.
valid.
User response:
Explanation:
Disconnect from CARMA, reconnect, and try the action
The value that is specified for the trace level is invalid.
again.
User response:
CRRZC0215E CRASERV: The instance ID or
In the client, disconnect from CARMA, open the
CARMA connection properties, and set the trace level member ID was not provided.
to the correct level. Reconnect and try your action Explanation:
again. The CARMA server did not receive the expected
instance ID or member ID.

20 Developer for z/OS: Troubleshooting and Support

User response: CRRZC0220E CRASERV: A timeout occurred
Disconnect from CARMA, reconnect, and try the action while waiting for data on the
again. socket.
CRRZC0216E CRASERV: The lrecl or Explanation:
numRecords is not valid. The CARMA server timed out while it was waiting for a
command.
Explanation
lrecl User response
the length of a record (a line in a host file) No action is required. The CARMA server is scheduled
to timeout after a certain time to keep host resources
numRecords available for other users.
the number of records (lines in the host file) being
sent If the CARMA server is timing out too frequently,
have your system programmer increase the timeout
This error happens either when a putMember action is value. If the system uses CRASTART, modify the
called on a record that has a file length of less than 0 crastart.timeout value in CRASRV.properties. If the
or when the number of records sent is less than 0. system uses batch submit, change the PROC 1 PORT
User response: TIMEOUT(420) line in the CRASUB* CLIST.
Disconnect from CARMA, reconnect, and try your For more information about increasing the timeout
upload again. If the problem persists, contact support. value, see the Host Configuration Guide.
CRRZC0217E CRASERV: There were fewer CRRZC0221E CRASERV: An expected parameter
records than specified. is missing for the putMember
Explanation: command.
The CARMA server expected more records than the Explanation:
number provided for the putMember action The expected parameter for the putMember function
User response: was not provided to the CARMA server from the client.
Disconnect from CARMA, reconnect, and try your User response:
action again. If the problem persists, try with a If you receive this error when you are performing an
different host code page. You can change the host action against a repository instance or the RAM itself,
code page for an individual member in the properties make sure the CARMA host components (CARMA
for that member. server) are updated to the same level as the client.
CRRZC0218E CRASERV: The line is longer than If you are using a custom client, have your client
the specified record length. developer confirm the custom action ID is properly
provided to the perform action method.
Explanation:
A line is the member is longer than the maximum line CRRZC0222E CRASERV: Error retrieving the
length (lrecl). Custom Action Framework
parameter list.
User response:
Ensure that all lines are within length limits and try the Explanation:
upload again. The CARMA server was unable to retrieve the custom
action framework parameter list for the RAMtext.
CRRZC0219E CRASERV: The instance ID,
member ID, metadata key name, User response:
or metadata value was not Disconnect from CARMA, reconnect, and try again. If
provided. the problem persists, confirm that the CRADEF VSAM
file is properly setup.
Explanation:
The CARMA server did not receive the expected CRRZC0223E CRASERV: An expected Custom
instance ID, member ID, metadata key name, or Action Framework parameter is
metadata value. missing.
User response: Explanation:
Disconnect from CARMA, reconnect, and try the action An action was called that required a custom action
again. framework parameter that was not provided.
User response:

Troubleshooting and support 21

Shut down and restart the client. Reconnect to CARMA Explanation:
and the RAM before you try the action again. If you The CARMA server encountered an error while reading
are using a custom client, have your client programmer the custom return values from the RAM.
confirm the client is providing all required parameters.
User response:
CRRZC0224E CRASERV: Unknown type specified Have your system programmer confirm that the
for the Custom Action Framework CRADEF VSAM file is properly set up and that the
parameter. RAM is returning the expected results. For more
information about formatting return values, see the
Explanation:
CARMA Developer's Guide.
An invalid type was specified for a parameter or return
value in the CRADEF configuration VSAM. CRRZC0299E CRASERV: Unknown error
User response: Explanation:
Confirm that the CRADEF VSAM file is properly set up An unknown error occurred in the CARMA server.
and contains valid types for parameters and return
User response:
values. Valid types are STRING, DOUBLE, LONG, and
Disconnect from CARMA, reconnect, and try again.
INT. For more information about valid parameter and
return value types, see the CARMA Developer's Guide.
CRRZC0225E CRASERV: Error gathering Custom
Action Framework returns

0300-level messages
CRRZC0301E The required RAMID is missing. CARMA expected a protocol version of 2 or greater, but
received {0}.
Explanation:
The CARMA Miner received a command that requires a User response:
RAM ID but one was not supplied by the client. Disconnect from the CARMA host, reconnect, and try
the command again. If you are using a custom RAM,
User response: confirm that you are not experiencing a buffer overflow
Disconnect from the CARMA host, reconnect, and condition.
try the command again. If you are using a custom
client, confirm that the client is calling the command CRRZC0304E Server Error: Unsupported CARMA
correctly. return code {0}.
CRRZC0302E The CARMA protocol is not
identified properly in the header: Explanation
{0} {0}
the unexpected integer return code
Explanation CARMA expected an integer return code, but instead
{0} received {0}
the unexpected protocol provided User response:
The communication between the CARMA Server and Disconnect from the CARMA host, reconnect, and try
the CARMA Miner was corrupted. CARMA Miner was the command again. If you are using a custom RAM,
expecting a protocol that begins with "CARMA/" and confirm that you are not experiencing a buffer overflow
instead received {0}. condition.
User response: CRRZC0305E The CARMA response header could
Disconnect from the CARMA host, reconnect, and try not be read.
the command again. If you are using a custom RAM, Explanation:
confirm that you are not experiencing a buffer overflow The response header from the CARMA Server contains
condition. an unexpected character.
CRRZC0303E Unsupported CARMA Protocol User response:
version: {0} Disconnect from the CARMA host, reconnect, and try
the command again. If you are using a custom RAM,
Explanation confirm that you are not experiencing a buffer overflow
condition.
{0}
the unsupported CARMA protocol version

22 Developer for z/OS: Troubleshooting and Support

CRRZC0306E An unexpected end of server CARMA expected an object of type {0}, but instead had
response has been reached. an object of type {1}
Explanation: User response:
The server response ended unexpectedly. An Disconnect from the CARMA host at the Remote
unexpected end of server response can occur when Systems view, refresh the parent container, reconnect,
the socket disconnects prematurely. and try again. Confirm that any custom client code is
sending the correct object types.
User response:
Disconnect from the CARMA host, reconnect, and try CRRZC0315E CARMA Expected
the command again. If you are using a custom RAM, {0,number,integer} attributes
confirm that you are not experiencing a buffer overflow and received {1,number,integer}
condition. attributes.
CRRZC0310E The RAM initialization state could
not be located. Explanation
Explanation: {0}
The CARMA Miner does not have the initialization the expected number of attributes from the
information that is needed to restart a connection to CARMA server
the RAM. {1}
User response: the number of attributes that are received from the
Disconnect from the CARMA host at the Remote CARMA server
Systems view, reconnect, and then try your action The CARMA Miner received the incorrect number of
again. attributes from the CARMA server. This situation can
be caused by a socket communication error.
CRRZC0311W The file code-page conversion
mapping is missing. Assuming User response:
the client is using the default Disconnect from the CARMA host at the Remote
UTF-8:LocalCP. Systems view, reconnect, and try the command
again. If the problem persists, ensure that all host
Explanation:
components of CARMA are at the same level.
The local and code page information was not sent to
the host, so the default code page was used. CRRZC0316E A duplicate item (Id={0}) was
encountered in the response.
User response:
This situation is most likely caused by an outdated
client. No response is required. To remove this Explanation
message, update the client. {0}
CRRZC0312E The file code-page conversion the id that has a duplicate
mapping is formatted incorrectly. A list was returned from the RAM that included
Explanation: duplicates of the same ID.
The code page conversion information that is used to User response:
download a file from CARMA is incorrectly formatted. The RAM developer must update the RAM to ensure
User response: that duplicate elements are not returned with the
Disconnect from the CARMA host at the Remote same ID.
Systems view, reconnect, and try your operation again. CRRZC0317E Internal error: The response body
If the problem persists, verify that there is not a is empty.
problem with custom client code.
Explanation:
CRRZC0313E Illegal CARMA object type. The CARMA Miner received an empty response body
Expecting {0}, received {1} from the CARMA server, possibly caused by a socket
communication error.
Explanation User response:
{0} Disconnect from the CARMA host at the Remote
the object type that is expected by CARMA Systems view, reconnect, and try the command
{1} again. If the problem persists, ensure that all host
the invalid object type provided components of CARMA are at the same level.

Troubleshooting and support 23

CRRZC0318E Internal error: The response Disconnect from the CARMA host at the Remote
processor is not set. Systems view, reconnect, and try again. If the problem
persists, ensure that all host components are at the
Explanation:
same level.
The CARMA Miner was not able to parse a response
from the CARMA Server because of an internal error. CRRZC0352E Server Error: The CARMA
Response Body could not be
User response: processed.
Disconnect from the CARMA host at the Remote
Systems view, reconnect, and try the command again. Explanation:
If the problem persists, contact technical support. The CARMA Miner received an invalid response from
the CARMA server, possibly caused by a socket
CRRZC0320E Server Error: The metadata key communication error.
could not be read.
User response:
Explanation: Disconnect from the CARMA host at the Remote
The CARMA Miner was unable to read a metadata key. Systems view, reconnect, and try again. If the problem
User response: persists, ensure that all host components are at the
Disconnect from the CARMA host at the Remote same level.
Systems view, reconnect, and try again. If you are CRRZC0360E Server Error: The Container check
using a custom RAM, ensure that the RAM does not failed due to an improperly
return any special characters within metadata keys. formatted CARMA response body.
CRRZC0321E Server Error: The metadata value Explanation:
could not be read. While the CARMA Miner was getting container
Explanation: contents, it received an invalid response from the
The CARMA Miner was unable to read a metadata CARMA server. This situation can be caused by a
value. socket communication error.
User response: User response:
Disconnect from the CARMA host at the Remote Disconnect from the CARMA host at the Remote
Systems view, reconnect, and try again. If you are Systems view, reconnect, and try again. If the problem
using a custom RAM, ensure that the RAM does not persists, confirm that all host components are at the
return any special characters within metadata values. same level. If you are using a custom RAM, ensure that
control characters are not used in MemberIDs.
CRRZC0350E Server Error: The return contents
size from the response could not CRRZC0370E Expected {0} attributes and
be determined. received {1} attributes.
Explanation:
The CARMA Miner received an invalid response from Explanation
the CARMA server, possibly caused by a socket {0}
communication error. the expected number of attributes
User response: {1}
Disconnect from the CARMA host at the Remote the received number of attributes
Systems view, reconnect, and try again. If the problem
While the CARMA Miner was getting custom action
persists, ensure that all host components are at the
framework information, it received an invalid response
same level.
from the CARMA server. This situation can be caused
CRRZC0351E Server Error: The returns contents by a socket communication error.
size "{0}" is improperly formatted.
User response:
Disconnect from the CARMA host at the Remote
Explanation Systems view, reconnect, and try again. If the problem
{0} persists, ensure that all host components are at the
same level. Ensure that no newline characters are
The CARMA Miner received an invalid response from used in the VSAM configuration files.
the CARMA server, possibly caused by a socket
communication error. CRRZC0371E A duplicate item (Id={0})
encountered in the response.
User response:

24 Developer for z/OS: Troubleshooting and Support

 Error in CARMA's Custom Action Explanation
Framework configuration.
{0}
A specified type that is required for the value
Explanation
{1}
{0} The default value of a custom parameter
the duplicate id
A custom parameter has a default value of {1}, which is
Two items in the CARMA VSAM configuration files have not a valid example of the type specified.
the same id, {0}.
User response:
User response: Have your system programmer or Custom RAM
Have your system programmer or Custom RAM Developer check the CRADEF VSAM file and modify
Developer check the CRADEF VSAM file and modify it so the custom parameters all have valid default
it so that the id provided is not duplicated. More values that are based on their type. More information
information about the VSAM configuration files can about the VSAM configuration files can be found
be found in the Common Access Repository Manager in the Common Access Repository Manager (CARMA)
(CARMA) Developer's Guide. Developer's Guide.
CRRZC0385E Improper custom action CRRZC0394E The parameter length for
configuration section count ({0}). (Parameter Id={0}) is not an
Integer: {1}.
Explanation
{0} Explanation
the number of custom action information received {0}
Not enough custom action information was returned the parameter id
by the CARMA server, possibly due to a socket error. {1}
At least four sections of information was expected, but 1
only {0} were received.
A custom parameter has a non-integer value for length
User response: in the CARMA configuration VSAM file.
Disconnect from the CARMA host, reconnect, and try
User response:
again. If the problem persists, ensure that all CARMA
Have your system programmer or Custom RAM
files on the host are at the same level.
Developer check the CRADEF VSAM file and modify it
CRRZC0392E Invalid custom parameter type so the custom parameters all have valid lengths. More
"{1}" information about the VSAM configuration files can
be found in the Common Access Repository Manager
(CARMA) Developer's Guide.
Explanation
CRRZC0398E Invalid custom parameter
{0}
identifier ({1}) associated with
the custom parameter
action "{2}".
{1}
the invalid type
Explanation
A custom parameter or return value has an invalid
type. Valid types are "STRING", "DOUBLE", "LONG", and {0}
"INT". the custom parameter
{1}
User response:
the custom return value
Have your system programmer or Custom RAM
Developer check the CRADEF VSAM file and modify {2}
it so the custom parameters and return values all the action
have valid types. More information about the VSAM An action defined in the CARMA configuration VSAM
configuration files can be found in the Common Access file does not have a valid custom parameter or return
Repository Manager (CARMA) Developer's Guide. value. The ID is not a valid integer or is not defined.
CRRZC0393E The default value does not User response:
match with given type: type={0}, Have your system programmer or Custom RAM
value={1}. Developer check the CRADEF VSAM file and modify

Troubleshooting and support 25

it so all actions have valid ids for the custom information about the VSAM configuration files can
parameters and return values. All parameters or return be found in the Common Access Repository Manager
values must also be defined in the VSAM file. More (CARMA) Developer's Guide.

0400-level messages
CRRZC0400E The method has already been Have your system programmer check the CARMA
executed. The method cannot be startup configuration. More information about
executed twice. configuring CARMA can be found in the Host
Configuration Guide.
Explanation:
The CARMA miner attempted to run the same CRRZC0407E The server startup was
command twice. interrupted.
User response: Explanation:
Disconnect from RSE, reconnect, and try your CARMA While the CARMA Server was waiting to connect to
command again. the CARMA Miner, there was an interruption, possibly
caused by a socket error or the RSE Miner shutting
CRRZC0401E Server Error: The Command down unexpectedly.
subject could not be located on the
host User response:
Disconnect from the CARMA host, reconnect, and try
Explanation: your command again.
The CARMA object (member, container, repository
instance) was not found on the host. CRRZC0408E Too many parameters to the REXX
startup script.
User response:
Refresh the parent container, and try the action again. Explanation:
More parameters than expected were passed to the
CRRZC0402E The required parameters are carma.startup.rex script.
missing.
User response:
Explanation: Confirm that all of the CARMA host code is at the same
The CARMA client did not provide the required level. If the carma.startup.rex was modified for your
parameters to the CARMA miner. installation, confirm that it is working as expected.
User response: CRRZC0409E Could not access the configured
Disconnect from RSE, reconnect RSE, reconnect
CLIST.
CARMA, reconnect to the RAM, and then try your
command again. If you are using a custom client, Explanation:
ensure that all required parameters are being sent to The CLIST defined in CRASRV.properties was not
the RAM. found by the carma.startup.rex script. The user might
not have the required permissions to access the CLIST,
CRRZC0403E The CARMA connection was not or the location is incorrect.
initialized.
User response:
Explanation: Confirm that the correct CLIST is defined in
CARMA was not initialized before a CARMA command CRASRV.properties and that the user has permission
was issued. to access it.
System programmer response: CRRZC0410E Server Error: The command is not
Check the CARMA startup configuration on the host.
supported.
User response: Explanation:
Disconnect from the CARMA connection, reconnect, CARMA miner encountered a command that was
and try the action again. unsupported.
CRRZC0405E The server is not loaded properly. System programmer response:
Contact the system programmer. Verify that the host and client versions of the product
Explanation: are the same.
The CARMA miner was unable to start the CARMA User response:
server. Disconnect from CARMA, reconnect, and try the action
User response: again.

26 Developer for z/OS: Troubleshooting and Support

CRRZC0411E Missing the port argument for the Disconnect from CARMA, reconnect, and try the action
CARMA Host server. again.
Explanation: CRRZC0421E Codepage mapping is not
The carma.startup.rex script did not receive a port supported by the CARMA host.
parameter, most likely caused by a modified or out of Explanation:
date carma.startup.rex.
The local or remote code page that is set for the target
User response: CARMA member is not supported by the Host system.
Confirm that all of the CARMA host code is at the same User response:
level. If the carma.startup.rex was modified for your The code page settings for the CARMA Member can
installation, confirm that it is working as expected be modified on its properties page. Change the remote
CRRZC0412E Could not locate the REXX startup code page to something supported by the host system
script. and try your file download or upload again.
Explanation: CRRZC0430E The key/value set on the member
The CARMA Rexx script was not found. Possibly could not be retrieved.
caused by the location not being an absolute location. Explanation:
User response: The CARMA Miner encountered an invalid key or value
Check the location that is defined for the CARMA while it was setting or retrieving metadata info. This
startup script name in the CRASRV.properties file. situation can be caused by a socket error on the host.
"startup.script.name" provides the absolute location of User response:
the startup script. Disconnect from the CARMA host, reconnect, and try
CRRZC0413E Missing the CLIST argument for your command again. If you were retrieving metadata
the CARMA Host server. information, make sure the RAM that you are using
does not use special characters for keys or values for
Explanation: metadata information. If you were setting metadata
The carma.startup.rex script did not receive a CLIST information, make sure that all values were non-null
parameter, most likely caused by a modified or out of and did not use special characters.
date carma.startup.rex.
CRRZC0433E DataStore State Exception: The
User response:
Instance container was not found
Confirm that all of the CARMA host code is at the same
in the required location.
level. If the carma.startup.rex was modified for your
installation, confirm that it is working as expected. Explanation:
The datastore that is used by the CARMA Miner has
CRRZC0415E Starting the CARMA Host server incorrect entries and an appropriate container cannot
encountered an unknown error. be found for the CARMA Object being worked against.
Please check the log.
Explanation: User response
The CARMA startup script encountered an unknown Disconnect from the CARMA host, reconnect, and try
error while it was trying to start the CARMA Server. your action again. If you are using custom client
User response: code, confirm it is operating correctly. If the problem
Check the rsecomm.log file for output from the CARMA persists, delete the CARMA connect, re-create it, and
startup script. This error can be caused by errors in the try your action again.
CARMA Server configuration or the user not having the Note: Deleting the CARMA connect breaks any
required permissions to start the CARMA server. associations between CARMA members and local or
CRRZC0420E The upload did not complete z/OS projects.
successfully. Disconnect and retry
CRRZC0450E The download location argument
the upload.
could not be found.
Explanation:
Explanation:
An I/O error occurred while the file was uploading
The CARMA Miner did not receive the location to
from the CARMA RSE Miner to the CARMA server.
download the member to, most likely caused by an out
Check the rsecomm.log for more information.
of date client or host.
User response:
User response:

Troubleshooting and support 27

Make sure that your client and host are both at the User response:
same level. A difference greater than two levels apart Disconnect from the CARMA host, reconnect, and try
is not supported the upload again. If the problem persists, have your
systems programmer restart the product on the host.
CRRZC0451E LRECL changed value during the
download. CRRZC0490E Error in checking container
property.
Explanation:
The RAM reported a different LRECL value for the Explanation:
CARMA member while in the process of downloading While the CARMA miner was trying to refresh the
the member. contents of a CARMA container or Repository Instance,
it was not able to verify the container information.
User response:
Have your RAM developer correct this error in the User response:
extractMember function. Disconnect from the CARMA host, reconnect, and
try your command again. If the problem persists,
CRRZC0452E RECFM changed value during the
try to refresh the container's container first. This
download.
problem can also be caused by incompatible versions
Explanation: of CARMA on the host and client. Make sure that your
While the CARMA miner was chunking a file download, host and client are on the same level.
it received a different LRECL (logical record length)
CRRZC0499E An unidentified error occurred
value than the download started with.
during upload.
User response:
Explanation:
Disconnect from the CARMA host, reconnect, and try
An unexpected error occurred while the file was
transferring the file again. If you are using a custom
uploading to CARMA.
RAM or client, make sure that LRECL is handled
correctly. User response:
Check the rsecomm.log file for more information about
CRRZC0480E The Upload handler is in an invalid
what caused the error. Disconnect from the CARMA
state. You need to reset.
host, reconnect, and try your upload again.
Explanation:
While the CARMA miner was trying to upload a
member from the client to the host, it encountered an
invalid state.

1000-level messages
CRRZC1010E Invalid member Id search Explanation:
parameter: null or "" The CARMA and RAM connections are no longer
synchronized.
Explanation:
A find resource, or a query for a container or User response:
element supported on CARMA container or repository You need to disconnect and reconnect your CARMA
instances, was called with an empty or null parameter and RAM connection.
ID. CRRZC1102E Custom actions are not available:
User response: Not synchronized
Refresh the parent container and try again. Explanation:
CRRZC1100E Required parameters (LRecl or The CARMA and RAM connections are no longer
RecFM) are not set. The contents synchronized.
cannot be uploaded. User response:
Explanation: You need to disconnect and reconnect your CARMA
The file was not transferred in the proper format. and RAM connection.
User response: CRRZC1103E An Error occurred while writing
Verify that the transfer format is specified correctly new member contents. See the
and try again. Error log for more details.
CRRZC1101E Custom actions are not available: Explanation:
Not synchronized

28 Developer for z/OS: Troubleshooting and Support

The specified character encoding is not supported check the RAM setup on the host by verifying the
when creating the new CARMA member. CRADEF and CRASTRS files.
User response: CRRZC1400E The transport layer connection
Change the character encoding of the source member was not created properly.
and try again.
Explanation:
CRRZC1201E The RAM connect method is The transport service is the connection bridge
disabled. between CARMA and the Remote System Explorer
(RSE) on the client. In this case, this communication
Explanation:
bridge was not create properly.
In the RAM configuration, "Connect to RAM" has been
disabled. User response:
Restart the workbench with the -clean flag.
User response:
Enable "Connect to RAM" in the RAM configuration. CRRZC1401E The Repository Manager transport
For additional information on enabling "Connect to service connection was not
RAM", see "Customizing a RAM API using the CAF" created properly.
in the Common Access Repository Manger (CARMA)
Explanation:
Developers Guide (SC23-7660).
Your CARMA connection is no longer working.
CRRZC1202E Could not load the Repository
User response:
Instances. The operation is not
Disconnect from CARMA, reconnect, and try again.
supported by the host Repository.
CRRZC1402E The repository instances were
Explanation:
not found because CARMA is not
In the RAM configuration, "Get Instances" has been
properly connected.
disabled.
Explanation:
User response:
Your CARMA connection is no longer working.
Enable "Get Instances" in the RAM configuration. For
additional information on enabling "Get Instances", User response:
see "Customizing a RAM API using the CAF" in Disconnect from CARMA, reconnect, and try again.
the Common Access Repository Manger (CARMA)
CRRZC1403E The CARMA transport service
Developers Guide (SC23-7660).
could not be accessed.
CRRZC1300E The CARMA Transport Service was
Explanation:
not initiated.
The transport service is the communication bridge
Explanation: between CARMA and the Remote System Explorer
The transport service is the communication bridge (RSE) on the client. In this case, this communication
between CARMA and the Remote System Explorer bridge could not be accessed.
(RSE) on the client. In this case, this communication
User response:
bridge was not initialized.
Restart the workbench with the -clean flag.
User response:
CRRZC1404E Could not access Repository
Restart the workbench with the -clean flag.
transport service: {0}
CRRZC1304E Problems loading configuration for
'{0}' Explanation
{0}
Explanation 0
{0} The transport service is the communication bridge
0 between CARMA and the Remote System Explorer
Either there was a connection problem while trying to (RSE) on the client. In this case, this communication
load the custom action framework (CAF) for the RAM bridge was not accessible.
or the configuration VSAMs (CRADEF and CRASTRS)
User response:
are incorrect.
Restart the workbench with the -clean flag.
User response:
CRRZC1450E The repository managers were not
Disconnect and reconnect from CARMA/RSE and try
loaded because CARMA is not
again. Additionally, have your systems administrator
properly connected.

Troubleshooting and support 29

Explanation: User response:
Your CARMA connection is no longer working. None needed, CARMA will check the bytes of the
compare files.
User response:
Disconnect from CARMA, reconnect, and try again. CRRZC1551W Could not load the CARMA
compare configuration, using the
CRRZC1490W Skipping extension '{0}' because
default (file) compare criteria.
of an invalid property priority: {1}.
Priority must be an integer greater Explanation:
than 0. The CARMA compare configuration file,
syncConfig.xml cannot be found.
Explanation User response:
{0} None needed, CARMA will check the bytes of the
0 compare files.

{1} CRRZC1601W Could not load the structured type

1,number,integer value ({0}): {1}
If a transport layer has an invalid priority, then the
transport layer will not be loaded. Explanation
User response: {0}
If the process works, then ignore the message. 0
Otherwise, restart the workbench and try again. {1}
1
CRRZC1501E The back end transport service
could not be located using key: {0} CARMA stores its model containing the CARMA
connections and any cached containers and members
Explanation to disk at workspace shut down and reloads at
workspace startup. In this case, there was a problem
{0} reloading this CARMA model.
0
User response:
CARMA is no longer associated with the RSE If CARMA connections appear broken, recreate them
connection. and try again. Otherwise, restart your workbench and
User response: try again.
Delete the CARMA connection and Create a new CRRZC1602W Could not convert the structured
CARMA connection. type value ({0}): {1}
CRRZC1502E Could not load
the TransportServiceFactory Explanation
extension
{0}
Explanation: 0
The TransportServiceFactory, which contains all {1}
loaded transport layers, was not loaded. 1
User response: CARMA stores its model containing the CARMA
If the process works, then ignore the message. connections and any cached containers and members
Otherwise, restart the workbench and try again. to disk at workspace shut down and reloads at
CRRZC1550W Could not load the CARMA workspace startup. In this case, there was a problem
compare configuration, using the reloading this CARMA model.
default (file) compare criteria. User response:
Explanation: If CARMA connections appear broken, recreate them
The CARMA compare configuration file, and try again. Otherwise, restart your workbench and
syncConfig.xml cannot be found. try again.

2000-level messages
CRRZC2001E Could not locate the CARMA Explanation:
Project for temporary downloads. When editing through the CAMRA editor, CARMA
makes use of a temporary location to store temporary

30 Developer for z/OS: Troubleshooting and Support

downloads. While processing, CARMA could not locate CRRZC2008E The CARMA command timed out.
this temporary location. The operation was cancelled.
User response: Explanation:
Retry opening the file. If reopening the file does not While CARMA was waiting for a response from the
work, restart the workbench. host, it timed out.
CRRZC2002E An error occurred creating and User response:
opening the CARMA download Disconnect from RSE, reconnect, and try again. If the
project. problem persists, it could be a configuration problem
on the host.
Explanation:
CARMA stores temporary downloaded files to a hidden CRRZC2009E Error uploading file: {0}
CARMA download project. In this case, there was a
problem creating or opening this project.
Explanation
User response:
{0}
Restart the workbench and try again. If this doesn't
0
work, create a new workspace and try again.
There was an error uploading the file.
CRRZC2003E An error occurred retrieving the
file from the server. User response:
Refresh the parent of the current item, and try again.
Explanation:
There was an error retrieving the file, and more CRRZC2010E Error uploading file: {0} {1}
information should be provided in an accompanying
error message. Explanation
User response: {0}
Check error log for accompanying messages. 0
CRRZC2004E Communication error[LRecl {1}
Format]-- See the error log for 1
details.
There was an error uploading the file, and an
Explanation: additional message with more information will be
CARMA has returned an invalid record length when provided.
trying to open a member.
User response:
User response: Follow the steps in the additional message. If
If the problem persists, have the RAM developer still unsuccessful, then disconnect from CARMA,
confirm an integer is returned for the LRecl or open reconnect, and try again.
the file in binary transfer mode.
CRRZC2011E The key to find is not set.
CRRZC2005E The temporary element type is not
Explanation:
valid.
There was an unexpected error during file upload.
Explanation: Please report this error to technical support.
CARMA encountered an error when making a
User response:
temporary element for communication with the host.
Please report this error to technical support.
User response:
CRRZC2012E The line length is greater than the
Refresh the parent of the current item, and try again.
record size of {2} (line {0} is {1}
CRRZC2007E Error uploading file: {0} characters long).

Explanation Explanation
{0} {0}
File name 2
There was an error uploading a file to CARMA. {1}
0
User response:
Disconnect from CARMA, reconnect, and try again. {2}
1

Troubleshooting and support 31

The file could not be uploaded as the specified line Access Repository Manger (CARMA) Developers Guide
number is longer than the line record length. (SC23-7660).
User response: CRRZC2027E Error uploading file: {0}
Modify the given line of the file so that the length is
shorter than the given record size. Explanation
CRRZC2013E Error uploading file: {0} {1} {0}
0
Explanation There was an error uploading the binary file.
{0} User response:
0 Disconnect from CARMA, reconnect and try again.
{1}
CRRZC2044E Communication error[LRecl
1
Format]-- See the error log for
There was an error uploading the file, and an details.
additional message with more information will be
provided. Explanation:
The value for the logical record length (LRecl) is not
User response: valid.
Follow the steps in the additional message. If
still unsuccessful, then disconnect from CARMA, User response:
reconnect, and try again. Contact the RAM developer to modify the RAM
to return the LRecl in the proper format. For
CRRZC2014I Interrupted while waiting for the additional information on RAMs, see the Common
upload return Access Repository Manger (CARMA) Developers Guide
Explanation: (SC23-7660).
CARMA finished sending the file to the host but was CRRZC2070E StatusChangeListener.{0}
interrupted before it could get final confirmation. communications diagnostic
User response: started.
Confirm the contents of the file on the host, or perform
the upload again. Explanation
CRRZC2017E Error uploading file: {0} {0}
0
Explanation A time out occurred while waiting for an update from
{0} the host.
0 User response:
There was an error uploading the text file. Disconnect from RSE, reconnect, and try again. If the
problem persists, have your system's administrator
User response: check your host configuration and tune the server for
Disconnect from CARMA, reconnect and try again. the number of users connecting concurrently.
CRRZC2018E The LRecl is not formatted CRRZC2071E StatusChangeListener.{0}: done
correctly: {0} = {1}; cancelled = {2};
_networkDown = {3}
Explanation
{0} Explanation
The value for LRecl received from the RAM {0}
The logical record length (LRecl) is not properly status of the listener; possible values: started,
defined in the RAM. working, done
{1}
User response:
true or false, if the upload completed
Contact the RAM developer to modify the RAM
to return the LRecl in the proper format. For {2}
additional information on RAMs, see the Common true or false, if the upload was canceled

32 Developer for z/OS: Troubleshooting and Support

{3} CRRZC2075E StatusChangeListener.ICommunic
true or false, if the network is down ations
This message provides the diagnostic information for Diagnostic exception
message CRRZC2070E. Explanation:
CRRZC2072E StatusChangeListener.{0} A timeout occurred and an exception was caught while
(DataStore): isConnected running diagnostics.
= {1}; isWaiting = {2} User response:
Follow the user response for any messages included
Explanation in the exception; otherwise, disconnect from RSE,
reconnect, and try again. If the problem persists, have
{0} systems administrator check your host configuration
status of the listener; possible values: started, and tune the server for the number of users
working, done connecting concurrently.
{1}
CRRZC2101E An object found in the DataStore is
true or false, if the connection to the host is active
not valid.
{2}
true or false, if the connection Explanation:
The host returned an invalid type of object for CARMA.
This message provides the diagnostic information for
message CRRZZC2070E. User response:
Disconnect from the remote system explorer,
CRRZC2073E StatusChangeListener.{0}.child{1} reconnect, and try again.
(DataElement): {2}
CRRZC2102E An object found in the DataStore is
not valid.
Explanation
Explanation:
{0} The host returned an invalid type of object for CARMA.
status of the listener; possible values: started,
working, done User response:
Disconnect from the remote system explorer,
{1}
reconnect, and try again.
index of the child data element (member, member
attribute, container) CRRZC2103E An object that is not valid was
{2} found in the CARMA Transport.
underlying data element representation of the Explanation:
CARMA object The host returned an invalid type of object for CARMA.
This message provides the diagnostic information for User response:
message CRRZZC2070E. Disconnect from the remote system explorer,
CRRZC2074E StatusChangeListener.{0}.child{1} reconnect, and try again.
(Descriptor): {2} CRRZC2104E An object that is not valid was
found in the CARMA Transport.
Explanation Explanation:
{0} The host returned an invalid type of object for CARMA.
status of the listener; possible values: started, User response:
working, done Disconnect from the remote system explorer,
{1} reconnect, and try again.
index of child data element (member, member
CRRZC2105E CARMA Transport State Exception:
attributes, container)
The member information
{2} referenced by key ({0}) was not
description of child data element, such as the found.
attribute data that describes the child data
element
Explanation
This message provides the diagnostic information for
message CRRZZC2070E. {0}
0

Troubleshooting and support 33

CARMA requested member information for a given key, the contents of a CARMA member in a third-party
which was not found for this CARMA resource. CARMA plug-in.
User response: CRRZC2111E The CARMA transport cannot
No user response is required. The particular piece of locate the element. Refresh at a
information is not set or valid on the CARMA resource. higher level in the hierarchy.
CRRZC2106E An object that is not valid was Explanation:
found in the CARMA Transport. The host side temporary cache of the resource is
missing.
Explanation:
The host returned an invalid type of object for CARMA.
User response
User response:
Try the following:
Disconnect from the remote system explorer,
reconnect, and try again. • refreshing the object again
CRRZC2107E The temporary element was not • refreshing the parent object
created properly. • disconnect and reconnect to the CARMA connection
Explanation: CRRZC2112E RAM Error: The resource returned
An error occurred that prevented the temporary from the host changed type. The
element from being created properly. attempted command is no longer
User response: available.
Disconnect you CARMA connection, reconnect, and try Explanation:
again. A record in the member is too long. The member has
CRRZC2108E The DataStore transport was not not been saved on the host.
synchronized with CARMA. Re- User response:
create your connection. Modify the length of the line and save again.
Explanation: CRRZC2113E Could not initialize. CARMA is not
The CARMA connection could not be synchronized connected.
with the underlying host transport layer.
Explanation:
User response: CARMA is unable to connect to the Host. This can
Remove the CARMA connection, recreate the occur when CARMA is not properly configured.
connection, and try again.
User response:
CRRZC2109E The command was not found: {0} Check the log to see if an error was received from the
CARMA Host (CRRZC2220E). If this error has occurred,
Explanation contact your system programmer to verify that the
host is properly configured as outline in the Common
{0} Access Repository Manger (CARMA) Developers Guide
0 (SC23-7660).
The CARMA command could not be located on the CRRZC2114E A temporary element for the
host. CARMA resource, {0}, was not
User response: created.
Disconnect from the remote system explorer,
reconnect, and try again. If the problem persists, Explanation
confirm with a system programmer that CARMA is
installed on the host and is the correct version. {0}
0
CRRZC2110E The file transfer conversion
mapping is not set. Could not create a temporary object to communicate
with the host for the given resource.
Explanation:
A third-party plug-in tried to set the contents of a User response:
CARMA member using internal API's. Refresh the resources parent, and try again.

User response: CRRZC2115E The CARMA Transport element

Make use of the method associated with the CARMA
CARMAMember.setMemberContents() when setting member is not set.

34 Developer for z/OS: Troubleshooting and Support

Explanation: Access Repository Manger (CARMA) Developers Guide
A third-party plugin tried to set or get the contents of a (SC23-7660).
CARMA member using internal API's.
CRRZC2122E Could not execute {0}: {1}
User response:
Use the CARMAMember.setMemberContents() and Explanation
CARMAMember.getMemberContents() methods to
set and get CARMA member contents respectively. {0}
the CARMA command name
CRRZC2116E The CARMA connect operation was
not successful. {1}
a message describing the problem
Explanation:
CARMA is unable to connect to the Host. This can The first part of the error message will provide
occur when CARMA is not properly configured. the CARMA command name. The second part of
the message includes a meaningful message of the
User response: problem.
Check the log to see if an error was received from the
CARMA Host (CRRZC2220E). If this error has occurred, User response:
contact your system programmer to verify that the Follow the user response instruction for the second
host is properly configured as outline in the Common part of the message to resolve the problem.
Access Repository Manger (CARMA) Developers Guide CRRZC2123E An object that is not valid was
(SC23-7660). found in the CARMA Transport.
CRRZC2117E The CARMA system did not Explanation:
connect properly after calling the The host returned an invalid type of object for CARMA.
connect operation.
User response:
Explanation: Disconnect from the remote system explorer,
CARMA is unable to connect to the Host. This can reconnect, and try again.
occur when CARMA is not properly configured.
CRRZC2124E An object that is not valid was
User response: found in the CARMA Transport.
Check the log to see if an error was received from the
CARMA Host (CRRZC2220E). If this error has occurred, Explanation:
contact your system programmer to verify that the The host returned an invalid type of object for CARMA.
host is properly configured as outline in the Common User response:
Access Repository Manger (CARMA) Developers Guide. Disconnect from the remote system explorer,
CRRZC2118W The terminate CARMA job reconnect, and try again.
command did not succeed. CRRZC2126E An object that is not valid was
Attempting to disconnect the found in the CARMA Transport.
system.
Explanation:
Explanation: The host returned an invalid type of object for CARMA.
There was an error trying to terminate the CARMA job
during disconnect. User response:
Disconnect from the remote system explorer,
User response: reconnect, and try again.
No user action is necessary.
CRRZC2128E Could not retrieve the member
CRRZC2119E The CARMA disconnect operation contents from CARMA.
was not successful.
Explanation:
Explanation: There was an error retrieving the file, and more
CARMA is unable to disconnect from the Host. This can information should be provided in an accompanying
occur when CARMA is not properly configured. error messages.
User response: User response:
Check the log to see if an error was received from the Check the error log for additional messages.
CARMA Host (CRRZC2220E). If this error has occurred,
contact your system programmer to verify that the CRRZC2129E Could not upload the file to the
host is properly configured as outline in the Common host.
Explanation:

Troubleshooting and support 35

There was an error uploading the file to the host. Explanation:
The version of CARMA installed on the host is out of
User response:
date, and it does not support binary transfers. This
Follow the user response in the additional message
error can occur when you attempt to retrieve the
provided.
binary version of a file from CARMA rather than the
CRRZC2200E An error was received from the text version.
CARMA Host [{0}]: [{2}] {1}
User response:
Set the transfer type to text. Alternatively, if you
Explanation need the file in binary, have your system programmer
{0} update the host installation.
host name CRRZC2220E CARMA is not available on the
{1} specified host.
error number Explanation:
{2} The required CARMA jar file is not found in the
error message class path in the Server. The server was not properly
installed and configured.
The error message provides more information about
the problem. User response:
Contact your system programmer and report the
CRRZC2201E CARMA Initialization is not
the problem. For information on installation and
supported.
configuration, see the Host Configuration Guide.
Explanation:
CRRZC2230E An error was encountered while
CARMA has been configured with the initialization
processing the custom action
function disabled and cannot start.
descriptions from the host.
User response:
Explanation:
Have the system programmer or RAM developer
When connecting to CARMA, there was an error getting
modify the CRADEF configuration VSAM on the host
the custom action descriptions.
to not disable action ID 80.
User response:
CRRZC2202E The custom action framework
Disconnect from RSE, reconnect, and try again.
description could not be located:
Additionally, if there is an additional message
This operation is not supported.
included, follow the user response for that particular
Explanation: error message.
CARMA has been configured with the custom action
CRRZC2300W Could not access the key '{0}' from
framework function disabled.
the RAM.
User response:
Have the system programmer modify the CRADEF
Explanation
configuration VSAM on the host not to disable action
ID 83. {0}
0
CRRZC2203E RAM Initialization is not
supported: The RAM could not be CARMA could not find the stated metadata key when
initialized. refreshing the metadata information.

Explanation: User response:

The RAM has been configured with the RAM No action needs to be taken as this is an informational
initialization function disabled and cannot start. warning.

User response: CRRZC2301E The connection alias name is not

Have the system programmer modify or RAM specified.
developer the CRADEF configuration VSAM on the Explanation:
host not to disable action ID 0. Additionally, the CARMA could not find the stated metadata key when
intRAM() function in the RAM should not return 107 refreshing the metadata information.
or RAM_ERR_FUNC_NOT_SUPPORTED, which states a
function is not supported. User response:
No action needs to be taken as this is an informational
CRRZC2205E Binary Transfer is not supported. error message.

36 Developer for z/OS: Troubleshooting and Support

CRRZC2301W Could not access the key '{0}' from User response:
the RAM. Disconnect, reconnect, and refresh CARMA.
CRRZC2305E The repository instance {0} was
Explanation not found in the DataStore.
{0}
0 Explanation
CARMA is no longer associated with the RSE {0}
connection. 0
User response: The local Cache does not match what is on the host.
Delete the existing CARMA connection and Create a User response:
new CARMA connection. Disconnect, reconnect, and refresh the repository
CRRZC2302E The connection with alias, '{0}', manager.
was not found. CRRZC2401E Invalid parameter default value
'{0}' for {1,choice,0#custom
Explanation parameter|1#custom return value|
2#custom field} (parameterId={2})
{0}
0
CARMA is no longer associated with the RSE
Explanation
connection. {0}
0
0
The name of the connection {1}
1,choice,0#custom parameter|1#custom return
User response: value|2#custom field
Delete the existing CARMA connection and Create a
new CARMA connection. {2}
2
CRRZC2303E Connection ({0}) does not have a
CARMA subsystem established. The default value set in the configuration VSAM is not
of the proper type.

Explanation User response:

The RAM developer should modify the configuration
{0} VSAMs to have a default value of the proper type for
0 the parameterID listed in the message.
The CARMA connection is no longer associated with an CRRZC2402E Invalid parameter default value
RSE connection. The RSE connection could have been '{0}' for {1,choice,0#custom
deleted or renamed. parameter|1#custom return value|
User response: 2#custom field} (parameterId={2})
Recreate an RSE connection with the same name and
host, and try connecting to CARMA again. Alternatively, Explanation
you can remove the CARMA connection and create
a new CARMA connection. Removing the CARMA {0}
connection will remove the associations between 0
CARMA and any members extracted to remote and {1}
local projects. 1,choice,0#custom parameter|1#custom return
value|2#custom field
CRRZC2304E The repository manager {0} was
not found in the DataStore. {2}
2
Explanation The default value set in the configuration VSAM is not
of the proper type.
{0}
0 User response:
The local Cache does not match what is on the host.

Troubleshooting and support 37

The RAM developer should modify the configuration (record format) is missing from the
VSAMs to have a default value of the proper type for command returns.
the parameterID listed in the message.
Explanation:
CRRZC2403E Invalid parameter default value CARMA or the RAM did not provide a valid for LRecl or
'{0}' for {1,choice,0#custom recFM when the create member call was made.
parameter|1#custom return value|
User response:
2#custom field} (parameterId={2})
Refresh the parent container to see if the member was
created by the RAM. If not, then retry the action. If the
Explanation problem persists, confirm the RAM developer is setting
{0} these values.
invalid type that is specified in the configuration CRRZC2407E Cannot create the resource: The
VSAM file; valid types are STRING, INT, LONG, and name or member Id is missing
DOUBLE from the command returns.
{1} Explanation:
values can be "custom parameter", "custom return CARMA or the RAM did not provide a valid name or
value", or "custom field" memberID when the create member call was made.
custom parameter User response:
a parameter that is passed to the RAM Refresh the parent container to see if the member was
custom return value created by the RAM. If not, then retry the action. If the
a return value that is passed back from the problem persists, confirm the RAM developer is setting
RAM these values.
custom field CRRZC2410E Invalid parameter length ({0})
a field that is defined by the RAM for {1,choice,0#custom parameter|
{2} 1#custom return value|2#custom
The parameter id that is specified in the field} (parameterId={2})
configuration VSAM files.
The default value set in the configuration VSAM is the Explanation
wrong type. {0}
User response: 0
The RAM developer should modify the configuration {1}
VSAMs to have a default value of the proper type for 1,choice,0#custom parameter|1#custom return
the parameterID listed in the message. value|2#custom field
CRRZC2405E DataStore state exception: An {2}
element type that is not allowed 2
was found in parameter container: The length set for the parameter in the VSAM
{0} configuration is not a valid number.
User response:
Explanation The RAM developer should modify the configuration
{0} VSAMs to have the parameter of the proper length for
0 the parameterID listed in the message.
A custom parameter, custom return value, or CARMA CRRZC2900W The CARMA miner version, {0},
field is being reported as having an unsupported type. was not parsed.
User response:
Disconnect CARMA, reconnect, and try again. If the Explanation
problem persists, have the RAM developer change the {0}
parameter type to a supported one, or update the 0
client to the same version as the host to support the
new parameter type. Could not parse the CARMA

CRRZC2406E Cannot create the resource: The User response:

LRecl(record length) or recFM

38 Developer for z/OS: Troubleshooting and Support

Disconnect from RSE, reconnect, and try again. If the Informational log message that provides the location
message persists or other problems arise, then update in the local file system to which a file is downloaded.
your client to the same version as the host.
CRRZC2905I Setting the trace level for the
CRRZC2901W Could not load the Repository connection to {0}.
Managers. The operation is not
supported by the host Repository. Explanation
Explanation: {0}
CARMA has been configured not load the repository Integer value that represents the host CARMA
manager. trace level
User response: Informational message that provides the trace level of
Have the system programmer or RAM developer the connection. This message is expected to be logged
modify the CRADEF configuration VSAM on the host at every CARMA connection.
not to disable action ID 82.
CRRZC2950E The compare with action on {0}
CRRZC2902E RAM disconnect Unsupported: encountered an error.
Could not disconnect from the
RAM.
Explanation
Explanation:
The terminate RAM action is disabled, so CARMA {0}
returned with an error when trying to disconnect from 0
the RAM. Unexpected error trying to perform a compare with
action. The CARMA member might not exist.
User response:
Have the system programmer or RAM developer User response:
modify the CRADEF configuration VSAM on the host Refresh the parent of the CARMA member in the
not to disable action ID 01. CARMA view, and try again.
CRRZC2903E A RAM termination exception CRRZC2951E The compare with action on {0}
occurred. encountered an error.
Explanation:
An error occurred when disconnecting the RAM. Explanation
User response: {0}
If there is an associated exception, follow the user 0
response in that. Otherwise, no action is required. Unexpected error trying to perform a compare with.
CRRZC2904I Requesting file download to: {0} The CARMA member might not exist.
User response:
Explanation Refresh the parent of the CARMA member in the
CARMA view, and try again.
{0}
Location to which the file is downloaded to

5000-level messages
CRRZC5000E The subproject '{0}' is User response:
already associated with another Remove the association of the subproject from CARMA
Repository Instance: {1} before trying to associate it with a new repository
instance.
Explanation CRRZC5001E Extracting to a z/OS project
resulted in an error. See the error
{0}
log for more details.
The name of a subproject
{1} Explanation:
The name of a repository The local cache for CARMA is out of sync with the local
host, which has caused an error during extract.
A subproject can only be associated with one
repository instance. This error message shouldn't User response:
appear in versions 8.0.1 or later. Refresh the parent in the CARMA view, and try again.

Troubleshooting and support 39

CRRZC5002E Extracting to a z/OS project Explanation
resulted in an error. See the error
{0}
log for more details.
0
Explanation:
The mapping between the resource and the CARMA
CARMA unexpectedly lost connection to the host
resource is incorrect.
during an extract.
User response:
User response:
Reassociate the resource with CARMA.
Check your network connection, reconnect to CARMA,
and try again. CRRZC5102E Could not copy the resource: {0}
CRRZC5004E The subproject '{0}' is
already associated with another Explanation
Repository Manager: {1} {0}
Resource name
Explanation The local cache for CARMA is out of sync with the local
{0} host, which has caused an error.
The name of a subproject User response:
{1} Refresh the parent in the CARMA view, and try again.
The name of a repository
CRRZC5103E Could not copy the resource: {0}
CARMA unexpectedly lost connection to the host
during an extract.
Explanation
User response:
{0}
Check your network connection, reconnect to CARMA,
0
and try again.
CARMA unexpectedly lost connection to the host
CRRZC5010E The z/OS resource was not located during extract.
on the host: {0}. Verify that the
resource exists. User response:
Check your network connection, reconnect to CARMA,
and try again.
Explanation
CRRZC5111E The z/OS project resource, {0},
{0}
was not created.
The name of a remote system
During an extract from CARMA, the host resource
could not be found after the RAM was instructed to
Explanation
create it. {0}
0
User response:
During an extract, the RAM must create the host Error adding the host resource to the z/OS sub project.
resource before returning control back to CARMA. If User response:
this problem persists, talk to your RAM developer. Disconnect from RSE and reconnect, then try
CRRZC5100E All the resources could not be extracting again.
copied into the RAM. CRRZC5200E The project properties could not
Explanation: be retrieved for all members.
When trying to copy multiple resources into the RAM a Explanation:
subset of the resources did not copy. There was an error receiving project properties for one
User response: or more of the members.
Verify which resources did not copy into the RAM and User response:
retry. Also check the log for messages regarding the Check for associated error messages and follow their
resources that did not copy successfully. user response.
CRRZC5101E The CARMA resource associated CRRZC5201E The CARMA resource associated
with '{0}' was not found. with '{0}' was not found.

40 Developer for z/OS: Troubleshooting and Support

Explanation SubProject is associated with
{1}. Properties will still be
{0} copied from below this level
0 and any previously copied project
When attempting to retrieve properties for the listed properties have not been changed.
resource, CARMA could not find the associated CARMA
object. This could be caused by the identifier changing Explanation
for CARMA object, possibly because of an update to
the RAM. {0}
0
User response:
Refresh the parent of the CARMA object, and extract it {1}
again to the same location. 1

CRRZC5202E The properties for resource {0} User response:

were not retrieved. CRRZC5400E The remote member was not
located. Verify that the remote
Explanation member or dataset exists and try
again.
{0}
0 Explanation:
The sequential data set or PDS member that is
The mapping between the resource and the CARMA selected for extract into a z/OS project or upload into
resource is incorrect. CARMA was not found.
User response: User response:
Reassociate the resource with CARMA. Verify that the remote member or data set exists, and
CRRZC5303E The properties for resource {0} try the action again.
were not retrieved. CRRZC5950E The z/OS Subproject could not be
associated with CARMA. See the
Explanation error log for more details.
{0} Explanation:
0 CARMA encountered one or more errors when trying to
CARMA unexpectedly lost connection to the host while associate the z/OS subproject with CARMA.
retrieving project properties. User response:
User response: Check for associated messages and follow their UR.
Check your network connection, reconnect to CARMA, Otherwise disconnect/reconnect RSE and try the
and try again. extract again.

CRRZC5305W Project properties cannot be

copied from {0} because the

7000-level messages
CRRZC7001I Views have been exported Explanation:
successfully. The views were exported from a CARMA RAM that
represented views differently that the RAM into which
Explanation: you are importing the view.
Information message that states that the CARMA
views that were selected for export were successfully User response:
exported. Choose to import the view if you want. Importing the
view can cause unexpected errors to occur in the RAM.
CRRZC7002W The identifier of this repository If problems occur, remove the imported views from
does not match the identifier of the RAM.
the repository from which this file
was exported. Importing this file CRRZC7003E Invalid view file selected.
can create invalid views. Are you Explanation:
sure that you want to import these The file that was selected for import is not correctly
views? formatted as a CARMA view file.

Troubleshooting and support 41

User response: Explanation:
Try the import again with a file of the correct format. CARMA encountered an error while it was saving the
view-export file.
CRRZC7004I Views have been imported
successfully. User response:
Verify that you have the correct access to the save
Explanation:
location on the client. Check the client error log for
Informational message that the CARMA views that
more information.
were selected for import were successfully imported.
CRRZC7005E An error occurred while CARMA
was trying to save the view-export
file.

Client messages for Enterprise Service Tools

The following client messages pertain to the Enterprise Service Tools (EST) component.
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.
CRRZX0047E Element "{0}" must include the specified in DriverSpec/@fileContainer because
required attribute "{1}". no more unique eight-character file names could be
generated from the specified prefix.
Explanation
User response
{0}
WSDL2ELS specification Specify a shorter prefix in DriverSpec/
{1} @fileNamePrefix to allow larger values of the
File container ordinal that is used to resolve file name collisions.

User response: CRRZX0131W No language structures were

generated for global XSD element
CRRZX0092E Unable to create a unique service "{0}" referenced by Operation
parameter name for XML element "{1}" because no mappable
"{0}". elements or attributes were found.

Explanation Explanation
{0} {0}
The name of an XML element Global element name
CRRZX0130E Unique driver file names with {1}
prefix "{0}", suffix "{1}", and Operation name
maximum length {2} have been
WSDL2PLI determined that a global XSD element
exhausted in file container "{3}".
referenced by an operation in the WSDL defines a
message that is empty. This message is issued to
Explanation indicate that a language binding was not provided
{0} and to ensure that the empty message definition is
File name prefix intentional.

{1}
File name suffix User response
{2} If the empty message definition is intentional, no
Number of characters action is required, otherwise correct the XML schema
and try again.
{3}
Container name CRRZX0132E No language structures could be
The Batch Processor could not form a unique name generated for global XSD element
for a converter driver file in the file container that is "{0}" referenced by Fault "{1}"
in Operation "{2}" because no

42 Developer for z/OS: Troubleshooting and Support

 mappable elements or attributes Explanation
exist.
{0}
Operation name
Explanation
{1}
{0} Binding name
Qualified element name {2}
{1} Port number
Qualified fault name {3}
{2} Service name
Operation name
User response:
WSDL2PLI and Compiled XML Conversion do not
support the concept of a generic binding. Therefore, CRRZX0135E The maximum XSD array
when a global XSD element describes the contents of dimension limit of {0} has been
the detail element of a fault message, it cannot be exceeded at XSD XPath: {1}.
of an empty complex type. The complex type must
contain at least one mappable XML element or XML Explanation
attribute.
{0}
User response: An integer that specifies the maximum XSD array
Add at least one XML element or XML attribute to the dimension limit
complex type referenced by the global XSD element. {1}
CRRZX0133E Request and response elements An XSD path name
have the same name "{0}" and User response:
the same namespace "{1}". The
request and response elements CRRZX0136E The correlator file {0} could not
must have different names or must be updated because it is either
be in different namespaces. invalid or needs to be migrated
to the current release. Correlator
files may be migrated using
Explanation the IMS Enterprise Suite SOAP
{0} Gateway deployment utility.
Element name
{1} Explanation
Namespace name
{0}
XsdSpecIn and XsdSpecOut specifications in The name of the correlator file
the ServiceSpecification.xml file contained
identical values for element specification User response:
(xsdElemName="{0}") and identical target namespace Check the correlator file to ensure that it is valid and
values (targetNamespace="{1}"). that it was upgraded to the current release.

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

Messages for the Editors

The following messages pertain to the Editors.
CRRZG0001E The editor is unable to find the If you are using a custom extension to the editor,
lexer from the stream. disable it. Otherwise, contact IBM Software Support.
Explanation: CRRZG0010E The editor could not display the
This error might be caused by a custom extension to message "{0}" at position {1}.
the editor or a product defect.
User response:

Troubleshooting and support 43

Explanation Resolve parsing errors and try the process again. If the
The embedded language parser was attempting to problem persists, contact IBM Software Support.
display an annotation through the editor, but an error CRRZG0052E Due to an invalid selection the
caused the process to stop. A custom extension to the editor is unable to perform the
editor might cause such an error. action.
{0} Explanation:
Message text The selected item is not valid.
{1}
User response:
The current position in the file that you are editing.
Select a different item, and try the operation again.
User response:
CRRZG0053E Due to a null parsing job the editor
If you are using a custom extension to the editor,
is unable to perform the action.
disable it. Otherwise, contact IBM Software Support
for assistance. Explanation:
This error occurs if you try to open the perform
CRRZG0020E Some of the required files were
hierarchy in an item where parsing did not occur.
not found.
User response:
Explanation:
Enable tools or annotations and tools, and try the
The Show Expanded Source action was requested,
operation again. Contact IBM Software Support to
but the include preprocessor could not locate some of
report the problem.
the copybooks or include files.
CRRZG0054E Due to parsing errors the editor is
User response unable to perform the action..
Associate a property group with the source file. The Explanation:
property group must specify these options: An error occurred when opening the perform hierarchy
• In the SYSLIB field of the property group, specify a because of a parsing error.
search path for copybooks and include files. User response:
• On the Local Preprocessors page, select -INC/+ Resolve the parsing errors, and try the action again.
+INCLUDE Preprocessor. Contact IBM Software Support for assistance.
• In the Preprocessor arguments field, specify CRRZG0055E Due to an invalid selection the
CMT(ON). editor is unable to perform the
action.
Ensure that the search path specified in the SYSLIB
field includes all copybooks or include files. Explanation:
The selected item cannot be used because it cannot
CRRZG0050E Due to a null parsing job the editor
be resolved.
is unable to perform the action.
User response:
Explanation:
Select a different item. If the problem persists, contact
The error occurs when a declaration is opened in an
IBM Software Support for assistance.
item where parsing did not occur. The error can occur
if annotations and tools are disabled and the F3 key is CRRZG0056E The editor is unable to create a
pressed to open a declaration. perform graph..
User response: Explanation:
Verify that the tools or annotations are enabled. Try The argument that was passed to the perform graph
the process again. If the tools and annotations are function is incorrect.
enabled or the problem persists, contact IBM Software
User response:
Support.
Try the function again with a different selection. If the
CRRZG0051E Due to parsing errors the editor is problem persists, contact IBM Software Support for
unable to perform the action. assistance.
Explanation: CRRZG0057E An attempt to add a part listener
This error might occur if the F3 key is used to open a to the workbench failed.
declaration when there is a parsing error.
Explanation:
User response: To add listeners to the workbench, they must
be registered during startup. Listeners were not

44 Developer for z/OS: Troubleshooting and Support

registered during startup. This situation can happen CRRZG0102E The editor is unable to add a
if the software is already running in nondisplay mode performer to the perform graph,
when the product is started. node {0}, with declaration {1}..
User response: Explanation:
If the error occurs during normal use, contact IBM The argument passed to the perform graph function is
Software Support for assistance. incorrect.
CRRZG0060I An availability check failed. User response:
Contact IBM Software Support for assistance.
Explanation:
An unknown error occurred during the availability CRRZG0110E The program {0} associated with
checking of the Open Declaration action. file {1} could not be loaded..
User response:
Contact IBM Software Support for assistance. Explanation
CRRZG0061I An availability check failed. {0}
A COBOL or PL/I source program file name.
Explanation:
An error occurred during the availability check of the {1}
Open Perform Hierarchy action. A COBOL copybook or PL/I include file.

User response: The source program file that was associated with
Contact IBM Software Support for assistance. the included file by using the Associate Complete
Program menu item cannot be loaded.
CRRZG0062I An availability check failed.
Explanation: User response
An error occurred during the availability check of a
Refactor action. • Ensure that the file type of the included file that
you want to associate with a complete program file
User response: matches the COBOL Copybook File or PL/I Include
Contact IBM Software Support for assistance. File content type. For more information about
CRRZG0100E The editor is unable to locate a content types, see Setting content type associations.
declaration for {0}. • Associate a property group with the program file.
The editor uses the SYSLIB property group setting
Explanation to locate included files. For more information about
associating a property group with a program file, see
The editor cannot locate a declaration for the {0}
Associating and overriding property groups.
paragraph. The location of the declared paragraph
cannot be determined. CRRZG0111E The content type of included file
{0} {0} is not supported..
The name of the paragraph being referenced.
User response: Explanation
Verify that the paragraph being referred to is declared, {0}
and try the operation again. A COBOL copybook or PL/I include file.
CRRZG0101E The editor is unable to add The file type of the included file that you want to
performee {0} to the perform associate with a complete program file does not
graph.. match the COBOL Copybook File or PL/I Include File
content type.
Explanation User response:
An incorrect argument was passed to the perform Ensure that the file type of the included file that
graph function. you want to associate with a complete program file
{0} matches the COBOL Copybook File or PL/I Include
Performee name File content type. For more information about content
types, see Setting content type associations.
User response:
Contact IBM Software Support for assistance.

Troubleshooting and support 45

 Messages for the z/OS Integrated Development Environment (zIDE)
These messages pertain to the z/OS Integrated Development Environment (zIDE).

0000-level messages
CRRZI0001E The backup of an existing older than IBM WebSphere Developer for zSeries
workspace has failed. Contact v6.0.1. This message explains how to open the
your IBM technical support Remote Error List view, which was introduced in IBM
representative. WebSphere Developer for zSeries v6.0.1 to replace the
Problems view.
Explanation:
Workspaces from IBM WebSphere Developer for User response:
System z® v6.0 or v7.0 or IBM Developer for z/OS Select Window > Show View > Remote Error List
v7.1 are updated to work in the latest version of the or Window > Reset Perspective to open the Remote
client when you open the workspace. The workspace is Error list view.
backed up before it is updated. This message indicates CRRZI0005E The {0} environment variable is
that the backup operation failed. not set. Set the environment
User response: variable in the System Variables
Contact IBM Software Support. table of your operating system's
environment variables. The value
CRRZI0002I A copy of your old workspace has should point to the product
been saved. It can be found at installation directory.
'{0}'.
CRRZI0006E The compiler option "CICS®({0})"
Explanation: is not applicable for a build
Workspaces from IBM WebSphere Developer for operation. Remove the suboption
System z v6.0 or v7.0 or IBM Developer for z/OS "{0}" and try again.
v7.1 are updated to work in the latest version of the
client when you open the workspace. The workspace is Explanation:
backed up before it is updated. This message indicates The CICS suboption CTS31, CTS32, or CTS41 was
the location of the backup copy. specified for a local build. These suboptions are valid
only in the context of syntax check.
User response:
No response is required. User response:
If you are running a local build, remove the CICS
CRRZI0003E The workspace migration has suboption CTS31, CTS32, or CTS41.
failed. A backup copy of the
original workspace can be found CRRZI0007E The compiler option
in '{0}'. Contact your IBM technical "CICS('CTS32')" is not applicable
support representative. for a build operation. Remove the
suboption "CTS32" and try again.
Explanation:
Workspaces from IBM WebSphere Developer for Explanation:
System z v6.0 or v7.0 or IBM Developer for z/OS The CICS suboption CTS32 was specified for a local
v7.1 are updated to work in the latest version of the build. This suboption is valid only in the context of
client when you open the workspace in. This message syntax check when the source code is being checked
indicates that the update operation failed. against the syntax of CICS Transaction Server for z/OS
3.2.
User response:
Contact IBM Software Support. User response:
If you are building a local application, remove the
CRRZI0004I In IBM WebSphere Developer for CTS32 suboption from the CICS compiler option.
zSeries 6.0.1, the Remote Error
List view replaces the Problems CRRZI0008E The compiler option
view. Select Window->Show View- "CICS('CTS41')" is not applicable
>Other...->TPF Toolkit->Remote for a build operation. Remove the
Error List or Window->Reset suboption "CTS41" and try again.
Perspective to open this view. Explanation:
Explanation: The CICS suboption CTS41 was specified for a local
The Remote Error List view is not visible in the build. This suboption is valid only in the context of
perspective in a workspace updated from a release syntax check when the source code is being checked

46 Developer for z/OS: Troubleshooting and Support

against the syntax of CICS Transaction Server for z/OS workspace. To import this file,
4.1. select File -> Import.
User response: Explanation:
If you are building a local application, remove the An attempt was made to open an include macro by
CTS41 suboption from the CICS compiler option. using the Open Include Macro action. The macro was
not added to the current workspace.
CRRZI0009W Data set {0} may be under SCLM
control. To continue, type your User response:
user ID for the system. To add the macro to the current workspace, use the
File > Import action.
Explanation:
An attempt was made to delete a data set that might CRRZI0015E The macro file cannot be found
be under control of SCLM. in the SYSLIB library. Verify that
both the file and the library are
User response:
allocated properly.
To continue deleting the data set, type your user ID
and password for the SCLM system and click OK. Explanation:
An attempt was made to open an include macro by
CRRZI0010I Resource {0} is under SCLM
using the Open Include Macro action. The macro
control. The file will be opened in
cannot be found in the SYSLIB library.
read-only mode.
Explanation: User response
An attempt was made to edit a resource that is under
To verify that the file was allocated properly, locate
control of SCLM.
the file in the Remote Systems view by expanding
User response: the MVS Files subsystem in the remote system
To edit the resource, access it by using the SCLM connection.
Developer Toolkit.
To verify that the SYSLIB is specified correctly, do
CRRZI0011W Resource {0} may be under SCLM these steps:
control. Are you sure you want to
1. Edit the property group associated with the
proceed?
resource.
Explanation: 2. Click the Assembler tab in the property group
An attempt was made to delete a resource that might editor.
be under control of SCLM.
3. Expand the procedure, select the step name, and
User response: click Edit in the Step Options area of the page.
To continue deleting the resource, click OK.
4. Verify that the data sets specified in the Macro
CRRZI0012E {0} is under control of SCLM and Libraries field is correct.
cannot be modified.
CRRZI0016E The macro file could not be
Explanation: opened. Connect to the system
An attempt was made to modify a resource that is before attempting this action.
under control of SCLM.
Explanation:
User response: An attempt was made to open an include macro by
To modify the resource, access it by using the SCLM using the Open Include Macro action. The macro
Developer Toolkit. cannot be opened because the remote system on
which it is located is not connected.
CRRZI0013I An SCLM project definition module
is found for {0}. User response:
To connect to the remote system, open the Remote
Explanation:
Systems view, select the remote system connection,
The resource that is indicated in the message might be
and click Connect on the menu.
under control of SCLM.
CRRZI0017I You must add a corresponding
User response:
filter for the data set before the
No response is required.
member can be added to the
CRRZI0014E The include file cannot be opened project.
until it is added to the current
Explanation:

Troubleshooting and support 47

You requested to add a copy member to a project from and member exist on the remote
an edit session, but there is no current filter for the system.
data set name.
Explanation:
User response: You requested to open a data set or partitioned data
In the Remote Systems view, select MVS Files, and set member from a JCL edit session, but the file
then select New > Filter to add a filter for the data set cannot be found.
name.
User response:
CRRZI0018E The copy library cannot be opened Verify that you selected a member name. In the
until it is added to the current Remote Systems view, verify that the data set and
workspace. To import this file, member exist on the remote system. Try the action
select File -> Import. again.
Explanation: CRRZI0023I The selected file '{0}' is already
You requested to open a copy library from an edit open in another edit session as
session, but it is not yet added to your workspace. a stored procedure. As a result,
no additional edit session will be
User response:
opened.
From the menu bar, click File > Import and browse
to the copy library location to import it into your Explanation:
workspace. You requested to edit a file that is already open for
editing.
CRRZI0019E The copy file cannot be found
in the SYSLIB library. Verify that User response:
both the file and the library are Look for the file name in another editor session and
allocated properly. edit it in that session.
Explanation: CRRZI0024I The selected file '{1}' is already
You requested to open or browse a remote copy open in the editor under a
member from an edit session, but the file cannot be different project as '{0}'. As a
found in the SYSLIB. result, no additional edit session
will be opened.
User response:
In the Remote Systems view, verify that the SYSLIB Explanation:
library was allocated and that the copy member exists You requested to edit a file that is already open for
in this library. Try the action again. editing.
CRRZI0020E The copy member could not be User response:
opened. Connect to the system Look for the file name in another editor session and
before attempting this action. edit it in that session.
Explanation: CRRZI0025E The file cannot be opened until it
You requested to open or browse a remote copy is added to the current workspace.
member from an edit session, but there is no To import this file, select File ->
connection to the remote system. Import.
User response: Explanation:
In the Remote Systems view, select the remote system An attempt was made to open an include file by using
and click Connect. After a connection is established, the Open Include File action. The file is not added to
try the action again. the current workspace.
CRRZI0021I No text was highlighted. Highlight User response:
the copy member name. To add the include file to the current workspace, use
the File > Import action.
Explanation:
You requested to open a copy member in an edit CRRZI0026E The file could not be opened.
session, but no copy member was highlighted. Connect to the system before
attempting this action.
User response:
Highlight the copy member name and try the action Explanation:
again. An attempt was made to open an include file by using
the Open Include File action. The file cannot be found
CRRZI0022E The data set member '{0}' cannot
in the SYSLIB library.
be found. Verify that the data set

48 Developer for z/OS: Troubleshooting and Support

User response Explanation
To verify that the file exists in one of the data sets
Attention: Local syntax check is deprecated.
specified in the SYSLIB concatenation, locate the data
sets in the Remote Systems view. Expand the MVS
Files subsystem in the remote system connection. An attempt was made to run a local syntax check on a
Expand each data set in SYSLIB to find the member. file that was opened for editing. The latest changes
to the file cannot be saved, but the syntax check
To verify that the SYSLIB is specified correctly, do operation can be run on the copy stored in the local
these steps: cache.
1. Edit the property group associated with the User response:
resource. Click Yes to run the syntax check on the cached copy.
2. Click the PL/I tab in the property group editor and
CRRZI0031E This file cannot be deleted
then select Procedures and Steps.
because this is an offline remote
3. Expand the procedure, select the step name, and file that has not been downloaded.
click Edit in the Step Options area of the page. To delete the file, you must move
4. Verify that the data sets specified in the Include the project back online.
Libraries field is correct. Explanation:
CRRZI0027E The include file could not be You requested to delete a placeholder file in an offline
opened. Connect to the system project. A placeholder file represents a remote file
before attempting this action. that is not downloaded and does not exist in the local
workspace. This message usually results from an API
Explanation: operation rather than a user-interface operation.
An attempt was made to open an include file by
using the Open Include File action. The file cannot User response:
be opened because the remote system on which it is Move the project to online state and try the operation
located is not connected. again.

User response: CRRZI0032E This file cannot be deleted

To connect to the remote system, open the Remote because this is an online remote
Systems view, select the remote system connection, file and the associated system
and click Connect on the menu. is not connected. To delete the
file, you must connect to the
CRRZI0029I Local syntax check of a remote associated system.
file is available only if the file
is opened or edited from an MVS Explanation:
subproject. You requested to delete a file in a remote project, but
you are not connected to the remote system.
Explanation User response:
Connect to the remote system and try the operation
Attention: Local syntax check is deprecated. again.
CRRZI0033E This file cannot be moved because
An attempt was made to run a local syntax check on
this is an offline remote file that
a file that was opened for editing from the Remote
has not been downloaded. To
Systems view.
move the file contents you must
move the project back online.
User response
Explanation:
1. Close the current edit session. You requested to move a placeholder file in an offline
2. Add the file to an MVS subproject. project. A placeholder file represents a remote file
that is not downloaded and does not exist in the local
3. Try the local syntax check request again. workspace. This message usually results from an API
CRRZI0030W The file cannot be saved. Do you operation rather than a user-interface operation.
want to check the syntax on the User response:
last saved copy of this file? Move the project to online state and try the operation
again.

Troubleshooting and support 49

CRRZI0034E This file cannot be moved because Move the project to online state and try the operation
this is an online remote file again.
and the associated system is not CRRZI0038E This file's contents cannot be
connected. To move the file, you modified because this is an online
must connect to the associated remote file and the associated
system. system is not connected. To
Explanation: update the file's contents, you
You requested to move a file in a remote project, but must connect to the associated
you are not connected to the remote system. system.
User response: Explanation:
Connect to the remote system and try the operation You requested to edit a file in a remote project, but you
again. are not connected to the remote system.
CRRZI0035E This file's contents are not User response:
available because this is an offline Connect to the remote system and try the operation
remote file that has not been again.
downloaded. To view the file's CRRZI0039I Refresh Dependencies of a remote
contents, you must move the file is available only if the file is
project back online. opened or edited from an MVS
Explanation: subproject.
You requested to open a placeholder file in an offline
CRRZI0041E Could not create IResources for
project. A placeholder file represents a remote file
{0}.
that is not downloaded and does not exist in the local
workspace. This message usually results from an API Explanation:
operation rather than a user-interface operation. An error occurred while accessing the contents of a
remote resource in a z/OS project.
User response:
Move the project to online state and try the operation
again. User response
CRRZI0036E This file's contents are not 1. Check the connection to determine whether the
available because this is an online project is an online project and then try the
remote file and the associated operation again.
system is not connected. To view 2. Clear the remote system cache files by selecting
the file's contents, you must the Remote Systems > File Cache > Clear Cached
connect to the associated system. Files preference, and then try the operation again.
Explanation: 3. Re-create the project.
You requested to open a file in a remote project, but
If the error occurs during normal use, contact IBM
you are not connected to the remote system.
Software Support to report the problem.
User response:
CRRZI0042E Could not download {0}.
Connect to the remote system and try the operation
again. Explanation:
The client failed to download the file from the remote
CRRZI0037E This file's contents cannot be
system to the local cache.
modified because this is an offline
remote file that has not been User response:
downloaded. To update the file's Check connection and try the operation again. If the
contents, you must move the problem still occurs, contact IBM Software Support to
project back online. report the problem.
Explanation: CRRZI0043E Could not find file {0}.
You requested to edit a placeholder file in an offline
Explanation:
project. A placeholder file represents a remote file
The client failed to find the local cache file when
that is not downloaded and does not exist in the local
reading or writing contents of a remote resource in a
workspace. This message usually results from an API
z/OS project.
operation rather than a user-interface operation.
User response:
User response:

50 Developer for z/OS: Troubleshooting and Support

If the project is online, check the remote system workstation-based projects exist in the workspace.
connection and try the operation again. If the problem Host-based projects and workstation-based projects
persists, contact IBM Software Support to report the associated with the same remote system cannot exist
problem. in the same workspace.
CRRZI0046E Could not upload {0}. User response:
Delete the workstation-based projects. Reconnect to
Explanation:
the remote system.
The client failed to upload the file from local cache to
the remote system. CRRZI0052E An I/O error occurred while
loading the host-based project
User response:
configuration file: '{0}'.
Check the remote system connection and try the
operation again. If the problem still occurs, contact Explanation:
IBM Software Support to report the problem. A connection was made to a remote system on which
host-based projects are defined. A host-based project
CRRZI0047E Could not write to {0}.
cannot be loaded into the z/OS Projects view because
Explanation: of an I/O error in the configuration file shown.
An error occurred while writing contents to a file in a
User response:
z/OS project.
Contact your system administrator.
User response:
CRRZI0053E A workbench error occurred while
Check the remote system connection and try the
loading the host-based project
operation again. If the problem still occurs, contact
configuration file: '{0}'.
IBM Software Support to report the problem.
Explanation:
CRRZI0048E {0} is not a valid URL.
A connection was made to a remote system on which
Explanation: host-based projects are defined. A host-based project
An error occurred while accessing an internal resource cannot be loaded into the z/OS Projects view because
in a z/OS project. of a workbench error.
User response: User response:
Contact IBM Software Support to report the problem. Contact your system administrator.
CRRZI0049E The class '{0}' is not a valid CRRZI0054E An I/O error occurred while
classifier. loading the host-based project
definition file: '{0}'.
Explanation:
An error occurred while creating an internal resource. Explanation:
A connection was made to a remote system on which
User response:
host-based projects are defined. A host-based project
Contact IBM Software Support to report the problem.
cannot be loaded into the z/OS Projects view because
CRRZI0050E The data type '{0}' is not a valid of an I/O error in the configuration file shown.
classifier.
User response:
Explanation: Contact your system administrator.
An error occurred while creating an internal resource.
CRRZI0055E Unable to find the project
User response: definition file '{0}' specified by the
Contact IBM Software Support. configuration file '{1}'.
CRRZI0051E The system '{0}' is currently under Explanation:
host-based control but one or A connection was made to a remote system on which
more remote projects associated host-based projects are defined. A host-based project
with the same system already cannot be loaded into the z/OS Projects view because
exist in this workspace. The the project definition file shown cannot be found.
non-host-based projects must be
deleted before any host-based User response
projects can be opened.
Contact your system administrator. The error can have
Explanation: one of the following causes:
A connection was made to a remote system on
• The project definition file does not exist.
which host-based projects are defined. One or more

Troubleshooting and support 51

• The path name for the project definition file is User response:
specified incorrectly in the configuration file. Contact your system administrator to modify the
subproject definition file to specify the correct remote
CRRZI0056E A workbench error occurred while
system name.
loading the host-based project
definition file: '{0}'. CRRZI0065E The subproject definition file for
subproject '{0}' did not contain a
Explanation: system name.
A connection was made to a remote system on which
host-based projects are defined. A host-based project Explanation:
cannot be loaded into the z/OS Projects view because A subproject was loaded from a host-based project.
of a workbench error. The subproject is not associated with a remote
system.
User response:
Contact your system administrator. User response:
Contact your system administrator to modify the
CRRZI0058E An I/O error occurred while subproject definition file to specify the correct remote
loading the host-based subproject system.
definition file: '{0}'.
CRRZI0066E The subproject definition file for
Explanation: subproject '{0}' did not contain any
A connection was made to a remote system on which system information.
host-based projects are defined. A host-based project
cannot be loaded into the z/OS Projects view because Explanation:
of an I/O error in the configuration file shown. A subproject was loaded from a host-based project.
The subproject is not associated with a remote
User response: system.
Contact your system administrator.
User response:
CRRZI0060E A workbench error occurred while Contact your system administrator to modify the
loading the host-based subproject subproject definition file to specify the correct remote
definition file: '{0}'. system name.
Explanation: CRRZI0068I The JCL member '{0}' is generated
A connection was made to a remote system on which
in data set '{1}'.
host-based projects are defined. A host-based project
cannot be loaded into the z/OS Projects view because Explanation:
of a workspace error. This message reports the results of a generate JCL
action. In this message, {0} is the JCL file that is
User response: generated and {1} is the name of the partitioned data
Contact your system administrator. set to which the JCL file is added.
CRRZI0062E A resource with the name '{0}' User response:
already exists in '{1}'. Make sure No action is necessary.
all the resources have a unique
name and try again. CRRZI0069E The operation did not complete
because resource '{0}' is locked.
Explanation:
Another person or program might
An attempt to rename a resource failed because
be using the resource. Try the
another resource by that name exists.
operation again when the resource
User response: is available.
Try the operation again with a different name.
Explanation:
CRRZI0063E The system name '{0}' found in This message displays in response to an attempt to
the subproject definition file for update a locked resource.
subproject '{1}' does not match User response:
any currently defined systems. You can see the lock status of a remote file by looking
Explanation: in the Properties view for the file. A locked file shows
A subproject was loaded from a host-based project. a user ID in the Lock Owner row of the properties
The remote system with which the subproject is table. An unlocked file shows no user ID in this row.
associated does not exist among the currently defined CRRZI0070E The specified data set for the
remote system connections.
generated JCL does not exist.

52 Developer for z/OS: Troubleshooting and Support

 Verify the name of the target data CRRZI0076E The submitted job ended with a
set and try again. JCL error.
Explanation:
A request was made to generate a JCL file, but the Explanation
target data set does not exist. The submitted job failed because of a JCL error. This
message also includes the following message text:
User response:
Request a different data set or allocate the target data Click {0} to view the job output or click {1}
to view the build properties currently in use.
set and resubmit the generation request.
In this message {0} is a link to the job output and
CRRZI0071I A member by this name already {1} is a link to the property group associated with the
exists. Do you want to replace the resource.
existing member?
User response:
Explanation: To check the job output, click the job output link. To
You submitted a generate JCL request and specified a check the build properties for the resource, click the
JCL file name that exists in the partitioned data set. property group link.
User response: CRRZI0077W The operation has been canceled
To generate the JCL and overwrite the existing JCL file, on the workstation. The job {0}
click Yes. To cancel the generate JCL request, click No. might need to be purged from JES.
CRRZI0073E The system submitted a job based Explanation:
on your current user ID to perform The execution of a job submission action was
a syntax check or a build. The canceled.
status of this job cannot be
determined because the JES filter
might be incorrect or the job card User response
might be invalid. Create a JES To purge the job, do these steps:
filter that matches this user ID, 1. In the Remote Systems view, locate the remote
verify the job card, and try again. system on which the resource you are working with
CRRZI0074E The JES subsystem is not is located.
connected. Connect to the 2. Expand the remote system connection and then
subsystem and try the operation expand JES > My Jobs.
again. 3. Select the job name indicated in the message and
Explanation: then select Purge from the menu.
The JES subsystem is not connected.
CRRZI0078E There is no property group
User response: associated with the subproject
In the Remote Systems view, locate the remote '{0}'. Associate a property group
system on which the resource you are working with is with the subproject and try the
located. Expand the remote system connection, select operation again.
JES, and then click Connect on the menu.
Explanation:
CRRZI0075E The submitted job has ended While running a build request for a subproject, the
abnormally. system detected that no property group is associated
with the subproject. A property group is required
Explanation:
to build a subproject. In this message, {0} is the
A submitted job ended abnormally. This message also
subproject name.
includes the following message text:Click {0} to
view the job output or click {1} to view
the build properties currently in use.In User response
this message {0} is a link to the job output and {1} 1. From the z/OS Projects view, select the subproject
is a link to the property group associated with the and then click Property Group > Associate
resource. Property Group.
User response: 2. In the Associate Property Group window, choose a
To check the job output, click the job output link. To property group to associate with the subproject and
check the build properties for the resource, click the click OK.
property group link.
3. Try the build operation again.

Troubleshooting and support 53

CRRZI0079I The alias, or the file it refers to, is in truncation of this line. Do you
already open in the editor. want to continue?
Explanation: Explanation:
A request to edit an alias or the file it refers to was During a file comparison, a line in file {0} was modified
made, but the file is already open in an editor. so that its line length exceeds the maximum length
allowed by the data set characteristics. This message
User response: warns that the line is truncated when the file is saved.
No response is required.
CRRZI0080W This action deletes the alias '{0}'. User response
Deleting an alias does not delete
the referenced data set. Do you • To save the file with the truncated line, click Yes.
want to proceed? • To cancel the save operation, click No. You can then
Explanation: return to the editor, correct the line in error, and try
This message displays in response to a Delete menu to save the file again.
action when the resource selected in the view is a data CRRZI0083W There are {0} lines in the file '{1}'
set alias. on the {2} with contents exceeding
the maximum line length (see
User response Details). Saving the file will result
in truncation of these lines. Do you
• If you intend to delete the alias, click Yes. want to continue?
• If you intend to delete the referenced data set, click
Explanation:
No, select the referenced data set in the view, and
During a file comparison, multiple lines in file {1}
then try the Delete action again.
were modified so that their line length exceeds
• To disable this warning, open the MVS Files the maximum length allowed by the data set
preference page and clear the Show warning characteristics. This message warns that the lines are
message on deleting alias checkbox. truncated when the file is saved.
CRRZI0081W This data set contains {0}
members, and the expansion of User response
the data set might take a long
• To save the file with the truncated lines, click Yes.
time. Do you want to proceed?
• To cancel the save operation, click No. You can then
Explanation: return to the editor, correct the lines in error, and try
The number of members in the partitioned data to save the file again.
set exceeds the warning threshold set in the MVS
Files preference page. This message gives you an CRRZI0084W The file '{0}' is locked. It is either
opportunity to cancel the expansion request. open in another edit session or
locked by another user. This file
will be opened in read-only mode.
User response
Do you want to continue?
• To continue expanding the partitioned data set, click
Explanation:
Yes.
During a file comparison operation, the system found
• To cancel the expansion request, click No. that the file indicated by {0} is already open in an
• To disable the warning, open the MVS Files edit session or locked by another user. This message
preference page and clear the Show warning gives you an opportunity to cancel the file comparison
message on expansion check box. operation or to continue the operation with the file in
read-only mode. If you continue with the comparison
• To change the warning threshold, open the MVS
operation, you are not able to edit the locked file.
Files preference page and specify a different number
in the Maximum number of members expanded
without warning field. User response
CRRZI0082W There is 1 line in the file '{0}' on • To continue with the file comparison operation, click
the {1} with contents exceeding Yes. The file is opened in read-only mode and you
the maximum line length (see are not able to edit it.
Details). Saving the file will result • To cancel the file comparison operation, click No.

54 Developer for z/OS: Troubleshooting and Support

• To open the file in the comparison editor in edit To continue with the file comparison, click Yes. To
mode, do one of the following actions: cancel the file comparison operation, click No.
– Close the file in the current edit session. CRRZI0087W The file '{0}' has a record length of
– Wait until the file is no longer locked and try again. '{1}' and the file '{2}' has a record
length of '{3}'. The record lengths
CRRZI0085W Both files are locked. They are do not match. Do you still want to
either open in other edit sessions continue?
or locked by other users. The files
will be opened in read-only mode.
Explanation
Do you want to continue?
{0}
Explanation:
One of two files that are being compared.
During a file comparison operation, the system found
that both files are already open in an edit session or {1}
locked by another user. This message gives you an The record length of file 0.
opportunity to cancel the file comparison operation or {2}
to continue the operation with the files in read-only One of two files that are being compared.
mode. If you continue with the comparison operation,
{3}
you are not able to edit the locked files.
The record length of file 2.
During a file comparison, the record length of file {0}
User response and record length of file {2} are displayed. If the record
• To continue with the file comparison operation, click lengths of both files do not match, then the user is
Yes. The files are opened in read-only mode and you prompted to confirm whether to continue with the file
are not able to edit them. comparison.
• To cancel the file comparison operation, click No. User response:
• If you want to open the files in the comparison editor To continue with the file comparison, click Yes. To
in edit mode, do one of the following actions: cancel the file comparison operation, click No.

– Close the files in the current edit session. CRRZI0088E The associated subsystem is
not connected. Connect to the
– Wait until the files are no longer locked and try the
subsystem and try the operation
file comparison again.
again.
CRRZI0086W The file '{0}' has a record format of Explanation:
'{1}' and the file '{2}' has a record The requested operation requires access to a remote
format of '{3}'. The record formats subsystem, such as MVS Files, z/OS UNIX Files, or JES.
do not match. Do you still want to
continue? User response:
Connect to the subsystem and try the operation again.
Explanation CRRZI0089I The data set is of type
LIBRARY(PDSE). Compression is
{0}
not required.
One of two files that are being compared.
{1} Explanation:
The record format of file 0. The Compress or Compress with Backup action was
requested for a data set of type LIBRARY(PDSE).
{2} These actions are not supported for this type of data
One of two files that are being compared. set.
{3}
User response:
The record format of file 2.
No action is required.
During a file comparison, the record format of file
CRRZI0090I Success
{0} and record format of file {2} are displayed. If the
record formats of both files do not match, then the Explanation:
user is prompted to confirm whether to continue with The installation verification procedure completed
the file comparison. successfully.
User response: User response:
No action is required.

Troubleshooting and support 55

CRRZI0091E I/O Error For more information about this error, see the
rsecomm.log and ffs*.log files on the remote
Explanation: system.
An I/O error occurred when gathering data set
information. CRRZI0096E Dynamic allocation failed.
User response: Explanation:
For more information about this error, see the A request to allocate a data set failed.
rsecomm.log and ffs*.log files on the remote User response:
system. For more information about this error, see the
CRRZI0092E Write failed rsecomm.log and ffs*.log files on the remote
system.
Explanation:
An I/O error occurred while uploading the file. CRRZI0097E Open failed
User response: Explanation:
For more information about this error, see the A request to open a data set failed.
rsecomm.log and ffs*.log files on the remote User response:
system. For more information about this error, see the
CRRZI0093E Read failed rsecomm.log and ffs*.log files on the remote
system.
Explanation:
An I/O error occurred while downloading a file or CRRZI0098I The resource is not immediately
finding a record in it. available.
User response: Explanation:
For more information about this error, see the The data set cannot be updated because it is being
rsecomm.log and ffs*.log files on the remote updated by another user.
system.
User response:
CRRZI0094E Write Initialization failed Wait for the data set to become available, and try the
operation again.
Explanation:
The process failed to initialize output while writing to a CRRZI0099I A previous request for control of
file. the same resource was made for
the same task.
User response:
For more information about this error, see the Explanation:
rsecomm.log and ffs*.log files on the remote The data set cannot be updated because it is being
system. opened by other task.
CRRZI0095E Read Initialization failed User response:
Disconnect from the remote system, and try the
Explanation: update operation again. If the update fails again,
The process failed to initialize a file while reading the collect the product log files and contact IBM Software
file. Support.
User response:

0100-level messages
CRRZI0130E Locate a catalog entry failed Explanation:
The ESTAE or GETMAIN macro failed.
Explanation:
The LOCATE macro failed while retrieving information User response:
from the catalog. For more information about this error, see the
following topic in z/OS V1R10.0 DFSMSdfp Advanced
User response: Services (SC26-7400): Catalog Processor Return
For more information about this error, see the Codes, code 164.
following topic in z/OS V1R10.0 DFSMSdfp Advanced
Services (SC26-7400): Return codes from LOCATE. CRRZI0132E DELETE failed because of
unmatched device type causing a
CRRZI0131E ESTAE or GETMAIN return code SCRATCH failure.
was nonzero.
Explanation:

56 Developer for z/OS: Troubleshooting and Support

An attempt to locate a catalog entry failed. For more information about this error, see the
following topic in z/OS V1R10.0 DFSMSdfp Advanced
User response:
Services (SC26-7400): Catalog Processor Return
For more information about this error, see the
Codes, code 44.
following topic in z/OS V1R10.0 DFSMSdfp Advanced
Services (SC26-7400): Catalog Processor Return CRRZI0138E The function was not valid.
Codes, code 168.
Explanation:
CRRZI0133E DELETE failed because of data set A request to locate a catalog entry failed.
being currently open, causing a
User response:
SCRATCH failure.
For more information about this error, see the
Explanation: following topic in z/OS V1R10.0 DFSMSdfp Advanced
An attempt to locate a catalog entry failed. Services (SC26-7400): Catalog Processor Return
Codes, code 48.
User response:
For more information about this error, see the CRRZI0139E Security or password verification
following topic in z/OS V1R10.0 DFSMSdfp Advanced failure.
Services (SC26-7400): Catalog Processor Return
Explanation:
Codes, code 184.
A request to locate a catalog entry failed.
CRRZI0134E There was an I/O or unrecoverable
User response:
error.
For more information about this error, see the
Explanation: following topic in z/OS V1R10.0 DFSMSdfp Advanced
A request to locate a catalog entry failed. Services (SC26-7400): Catalog Processor Return
Codes, code 56.
User response:
For more information about this error, see the CRRZI0140E Either the data set was not
following topic in z/OS V1R10.0 DFSMSdfp Advanced found or the catalog could not be
Services (SC26-7400): Catalog Processor Return opened.
Codes, code 24.
Explanation:
CRRZI0135E Unable to allocate a required A request to locate a catalog entry failed.
catalog.
User response:
Explanation: For more information about this error, see the
A request to locate a catalog entry failed. following topic in z/OS V1R10.0 DFSMSdfp Advanced
Services (SC26-7400): Catalog Processor Return
User response:
Codes, code 8.
For more information about this error, see the
following topic in z/OS V1R10.0 DFSMSdfp Advanced CRRZI0141E DELETE failed because of
Services (SC26-7400): Catalog Processor Return Code, unexpired purge date causing a
code 4. SCRATCH failure.
CRRZI0136E Insufficient space was supplied. Explanation:
The size of the calculated space is An attempt to locate a catalog entry failed.
returned in the CTGFDBK area of
User response:
the catalog parameter list.
For more information about this error, see the
Explanation: following topic in z/OS V1R10.0 DFSMSdfp Advanced
A request to locate a catalog entry failed. Services (SC26-7400): Catalog Processor Return
Codes, code 84.
User response:
For more information about this error, see the CRRZI0142E Read a DSCB failed
following topic in z/OS V1R10.0 DFSMSdfp Advanced
Explanation:
Services (SC26-7400): Catalog Processor Return
A request to read a data set control block (DSCB)
Codes, code 40.
failed with a return code of 4, 8, 12 or 16.
CRRZI0137E Insufficient space was supplied.
User response:
The size required is not known.
For more information about this error, see the
Explanation: following topic in z/OS V1R10.0 DFSMSdfp Advanced
A request to locate a catalog entry failed. Services (SC26-7400): Return Codes from OBTAIN
(Reading by Data Set Name).
User response:

Troubleshooting and support 57

CRRZI0143E A permanent I/O error was User response:
encountered, or an invalid For more information about this error, see the
format-1 DSCB was found when following topic in z/OS V1R10.0 DFSMSdfp Advanced
processing the specified volume, Services (SC26-7400): Return Codes from OBTAIN
or an unexpected error return code (Reading by Data Set Name).
was received from CVAF (common CRRZI0147E Migrated Data Set failed
VTOC access facility).
Explanation:
A request to retrieve a migrated data set failed.
Explanation
Retrieval of migrated data sets is not supported
A request to read a data set control block (DSCB)
because of long recall and transmission times.
failed with return code 12. This error can occur for the
following reasons: User response:
No action is required.
• A permanent I/O error was encountered.
• An invalid format-1 DSCB was found when CRRZI0148E Close failed
processing the specified volume. Explanation:
• An unexpected error return code was received from During a request to rename or delete a file, the close
the common VTOC access facility (CVAF). file operation failed.

User response: User response:

For more information about this error, see the For more information about this error, see the
following topic in z/OS V1R10.0 DFSMSdfp Advanced rsecomm.log and ffs*.log files on the remote
Services (SC26-7400): Return Codes from OBTAIN system. Consult with your system administrator. If
(Reading by Data Set Name). you cannot solve the problem, contact IBM Software
Support.
CRRZI0144E Invalid work area pointer.
CRRZI0149E Termination failed
Explanation:
A request to read a data set control block (DSCB) Explanation:
failed with return code 16. This error is caused by an During a request to rename or delete a file, the
invalid work area pointer. termination operation failed.

User response: User response:

For more information about this error, see the For more information about this error, see the
following topic in z/OS V1R10.0 DFSMSdfp Advanced rsecomm.log and ffs*.log files on the remote
Services (SC26-7400): Return Codes from OBTAIN system. Consult with your system administrator. If
(Reading by Data Set Name). you cannot solve the problem, contact IBM Software
Support.
CRRZI0145E The required volume was not
mounted. CRRZI0151E Get Directory failed

Explanation: Explanation:
A request to read a data set control block (DSCB) The DFSMS macro DESERV GET_ALL function failed.
failed with return code 4. This error can occur when User response:
the required volume is not mounted. For more information about this error, see the
User response: following topic in z/OS V1R10.0 DFSMS Macro
For more information about this error, see the Instructions for Data Sets (SC26-7408): DESERV
following topic in z/OS V1R10.0 DFSMSdfp Advanced GET_ALL Function Reason Codes.
Services (SC26-7400): Return Codes from OBTAIN CRRZI0152E Start Command Server failed
(Reading by Data Set Name).
Explanation:
CRRZI0146E The format-1 DSCB was not found This error results from an APPC setup problem for the
in the VTOC of the specified TSO Commands service.
volume.
User response:
Explanation: For information about tuning considerations when
A request to read a data set control block (DSCB) using APPC to start the TSO Commands service, see
failed with return code 8. This error occurs when Understanding the server in the Host Configuration
the format-1 DSCB is not found in the VTOC of the Reference.
specified volume.
CRRZI0188E Create a thread failed.

58 Developer for z/OS: Troubleshooting and Support

Explanation: This error occurs when downloading a load module or
During a request to connect to a remote system server, program object. The transfer types of the source and
the process to create a thread failed. target data sets are different.
User response:
For more information about this error, see the User response
following topic in z/OS V1R10.0 XL C/C++ Run-Time Diagnosing the problem
Library Reference (SA22-7821): pthread_create()–
Create a Thread. 1. Left-click the destination data set. Look at
the Property view (the two-column table with
CRRZI0189E The system lacks the necessary headings Property and Value). Expand the
resources to create another Mapping property. You must see Transfer
thread. Binary in both the source data set and the
Explanation: destination data set.
During a request to connect to a remote system server, 2. This feature requires the client and server to be
the process to create a thread failed. at least at version 8.0.1.
User response: Solving the problem
For more information about this error, see the If the destination data set is Transfer Text, change
following topic in z/OS V1R10.0 XL C/C++ Run-Time it to Transfer Binary by doing one of the following
Library Reference (SA22-7821): pthread_create()– actions:
Create a Thread, error code EAGAIN.
• For a single file:
CRRZI0190E The value specified by thread is
not valid. 1. Right-click the destination data file and click
Properties.
Explanation:
2. Click Mapping.
During a request to connect to a remote system server,
the process to create a thread failed. 3. Click Other beneath Transfer mode, click
binary, and then click OK.
User response:
For more information about this error, see the • For all files with a particular low-level qualifier:
following topic in z/OS V1R10.0 XL C/C++ Run-Time 1. Click Window > Show View > z/OS file
Library Reference (SA22-7821): pthread_create()– System Mapping. The view opens near the
Create a Thread, error code EINVAL. bottom of the workspace window.
CRRZI0191E There is not enough memory to 2. Right-click in the view and click Add data set
create the thread. mapping.
Explanation: 3. Type a pattern in the Mapping Criterion field,
During a request to connect to a remote system server, for example, **LOADMOD. This mapping will
the process to create a thread failed. apply to all future data sets with that low-
level qualifier.
User response:
For more information about this error, see the 4. Click Other beneath the Transfer mode, click
following topic in z/OS V1R10.0 XL C/C++ Run-Time binary, and then click OK.
Library Reference (SA22-7821): pthread_create()– CRRZI0195E Unable to delete file
Create a Thread, error code ENOMEM.
Explanation:
CRRZI0193E Client/Server version mismatch A request to delete a data set failed.
Explanation: User response:
An attempt was made to connect to a remote system For more information about this error, see the
server from a version of the client that is not supported rsecomm.log and ffs*.log files on the remote
on that server. system.
User response: CRRZI0196E Unable to rename file
Verify the client and server versions of the product.
Install the correct version of the client or connect to a Explanation:
remote system that is compatible with the client. A request to rename a data set failed.

CRRZI0194E Record format not allowed User response:

Explanation:

Troubleshooting and support 59

For more information about this error, see the Verify the amount of space in the directory. For
rsecomm.log and ffs*.log files on the remote more information about this error, see the following
system. topic in z/OS DFSMS Macro Instructions for Data Sets
(SC26-7408): STOW Completion Codes.
CRRZI0197E Directory update failed
CRRZI0199E A permanent input or output error
Explanation:
was detected. Control is not given
The STOW macro, update Partitioned Data Set
to the error analysis (SYNAD)
Directory (BPAM), failed.
routine.
User response:
Explanation:
Ensure that you have write authority for the data
The STOW macro, updating partitioned data set
set. Contact your system administrator if you need
directory (BPAM), failed. A permanent input or output
assistance with obtaining write authority.
error was detected. Control is not given to the error
CRRZI0198E No space left in the directory. analysis (SYNAD) routine.
Explanation: User response:
The STOW macro, updating partitioned data set Contact IBM Software Support. For more information
directory (BPAM), failed because there is no space left about this error, see the following topic in z/OS
in the directory. V1R10.0 DFSMS Macro Instructions for Data Sets:
STOW Completion Codes.
User response:

0200-level messages
CRRZI0200E The system found an I/O error The STOW macro, updating partitioned data set
while trying to read or write the directory (BPAM), failed. The system was unable to
VTOC. update the VTOC.
Explanation: User response:
The STOW macro, updating partitioned data set For more information about this error, see the
directory (BPAM), failed. The system found an I/O error following topic in z/OS V1R10.0 DFSMS Macro
while trying to read or write the VTOC. Instructions for Data Sets: STOW Completion Codes.
User response: CRRZI0203E Either no secondary space is
For more information about this error, see the available or a DADSM user exit
following topic in z/OS V1R10.0 DFSMS Macro error occurred. The error occurred
Instructions for Data Sets: STOW Completion Codes. when trying to write an EOF; all
primary space has been used.
CRRZI0201E A permanent I/O error occurred
while attempting to write the EOF Explanation:
mark after the member. Control The STOW macro, updating partitioned data set
is not given to the error analysis directory (BPAM), failed. Either no secondary space
(SYNAD) routine. is available or a DADSM user exit error occurred. The
error occurred when trying to write an EOF; all primary
Explanation: space is used.
The STOW macro, updating partitioned data set
directory (BPAM), failed. A permanent I/O error User response:
occurred while attempting to write the EOF mark after Verify the availability of secondary space. For more
the member. Control is not given to the error analysis information about this error, see the following topic in
(SYNAD) routine. z/OS V1R10.0 DFSMS Macro Instructions for Data Sets:
STOW Completion Codes. For more information about
User response:
abend codes X'737', X'B37', X'D37', and X'E37', see
Contact IBM Software Support. For more information
z/OS V1R10.0 MVS System Codes.
about this error, see the following topic in z/OS
V1R10.0 DFSMS Macro Instructions for Data Sets: CRRZI0204E Either no secondary space is
STOW Completion Codes. available or a DADSM user exit
error occurred.
CRRZI0202E The system was unable to update
the VTOC. Explanation:
The STOW macro, updating partitioned data set
Explanation: directory (BPAM), failed. Either no secondary space is
available or a DADSM user exit error occurred.

60 Developer for z/OS: Troubleshooting and Support

User response: The STOW macro, updating partitioned data set
Verify the availability of secondary space. For more directory (BPAM), failed. Insufficient virtual storage
information about this error, see the following topic in was available to run the STOW function.
z/OS V1R10.0 DFSMS Macro Instructions for Data Sets:
User response:
STOW Completion Codes. For more information about
For more information about this error, see the
abend codes X'737', X'B37', X'D37', and X'E37', see
following topic in z/OS V1R10.0 DFSMS Macro
z/OS V1R10.0 MVS System Codes.
Instructions for Data Sets: STOW Completion Codes.
CRRZI0205E An error occurred while writing
CRRZI0209E The caller attempted to issue
data buffered in system buffers.
add or replace for a member of
Control is not given to the error
the Program Management Library,
analysis (SYNAD) routine.
which is a PDSE that contains
Explanation: program objects.
The STOW macro, updating partitioned data set
Explanation:
directory (BPAM), failed. An error occurred while
The STOW macro, updating partitioned data set
writing data buffered in system buffers. Control is not
directory (BPAM), failed. The caller attempted to
given to the error analysis (SYNAD) routine.
issue add or replace for a member of the Program
User response: Management Library, which is a PDSE that contains
Contact IBM Software Support. For more information program objects.
about this error, see the following topic in z/OS
User response:
V1R10.0 DFSMS Macro Instructions for Data Sets:
For more information about this error, see the
STOW Completion Codes.
following topic in z/OS V1R10.0 DFSMS Macro
CRRZI0206E The specified data control block is Instructions for Data Sets: STOW Completion Codes.
not open or is opened for input, or
CRRZI0210E The alias has an invalid TTR.
a DEB error occurred.
Explanation:
Explanation:
The STOW macro, updating partitioned data set
The STOW macro, updating partitioned data set
directory (BPAM), failed. The alias has an invalid TTR.
directory (BPAM), failed. The specified data control
block is not open or is opened for input, or a DEB error User response:
occurred. For more information about this error, see the
following topic in z/OS V1R10.0 DFSMS Macro
User response:
Instructions for Data Sets: STOW Completion Codes.
For more information about this error, see the
following topic in z/OS V1R10.0 DFSMS Macro CRRZI0211E The directory already contains the
Instructions for Data Sets: STOW Completion Codes. specified new name.
CRRZI0207E The initialize function was Explanation:
specified but the PDSE was The STOW macro, updating partitioned data set
allocated with DISP=SHR. Use directory (BPAM), failed. The directory already
DISP=OLD or DISP=MOD. contains the specified new name.
Explanation: User response:
The STOW macro, updating partitioned data set Verify the directory name. For more information
directory (BPAM), failed. The initialize function was about this error, see the following topic in z/OS
specified, but the PDSE was allocated with DISP=SHR. V1R10.0 DFSMS Macro Instructions for Data Sets:
STOW Completion Codes.
User response:
Use DISP=OLD or DISP=MOD. For more information CRRZI0212E User-supplied TTRs are in the user
about this error, see the following topic in z/OS data field of the directory entry.
V1R10.0 DFSMS Macro Instructions for Data Sets:
Explanation:
STOW Completion Codes.
The STOW macro, updating partitioned data set
CRRZI0208E Insufficient virtual storage was directory (BPAM), failed. User-supplied TTRs are in the
available to perform the STOW user data field of the directory entry (PDSEs only).
function.
User response:
Explanation: For more information about this error, see the
following topic in z/OS V1R10.0 DFSMS Macro
Instructions for Data Sets: STOW Completion Codes.

Troubleshooting and support 61

CRRZI0213E The replace failed because you PDSE is open for update, but the input TTR is not
cannot replace an alias name if it defined for that member (PDSEs only).
is the same name as the primary User response:
member.
For more information about this error, see the
Explanation: following topic in z/OS V1R10.0 DFSMS Macro
The STOW macro, updating partitioned data set Instructions for Data Sets: STOW Completion Codes.
directory (BPAM), failed. The request to replace the file CRRZI0217E The add failed because you cannot
failed because you cannot replace an alias name if it is add a primary member name while
the same name as the primary member (PDSEs only). the PDSE is open for update.
User response: Explanation:
For more information about this error, see the The STOW macro, updating partitioned data set
following topic in z/OS V1R10.0 DFSMS Macro directory (BPAM), failed. The add failed because you
Instructions for Data Sets: STOW Completion Codes. cannot add a primary member name while the PDSE is
CRRZI0214E The add or replace failed when open for update (PDSEs only).
attempting to add or replace an User response:
alias, but the member identified For more information about this error, see the
by the TTR did not exist. following topic in z/OS V1R10.0 DFSMS Macro
Explanation: Instructions for Data Sets: STOW Completion Codes.
The STOW macro, updating partitioned data set CRRZI0218E The replace failed because you
directory (BPAM), failed. The add or replace failed
cannot replace a primary member
when attempting to add or replace an alias, but the
name while the PDSE is open for
member identified by the TTR did not exist (PDSEs
update and the specified name
only).
does not exist.
User response:
Explanation:
For more information about this error, see the
The STOW macro, updating partitioned data set
following topic in z/OS V1R10.0 DFSMS Macro
directory (BPAM), failed. The replace failed because
Instructions for Data Sets: STOW Completion Codes.
you cannot replace a primary member name while the
CRRZI0215E The replace failed when PDSE is open for update and the specified name does
attempting to replace a primary not exist (PDSEs only).
member name while the PDSE is User response:
open for update and the member For more information about this error, see the
name identified an existing alias. following topic in z/OS V1R10.0 DFSMS Macro
Explanation: Instructions for Data Sets: STOW Completion Codes.
The STOW macro, updating partitioned data set CRRZI0219E One or more members were placed
directory (BPAM), failed. The replace failed when
in a pending delete state; the
attempting to replace a primary member name. The
space taken by those modules
PDSE is open for update and the member name
is not immediately available for
identified an existing alias (PDSEs only).
reuse.
User response:
Explanation:
For more information about this error, see the
The STOW macro, updating partitioned data set
following topic in z/OS V1R10.0 DFSMS Macro
directory (BPAM), failed. One or more members were
Instructions for Data Sets: STOW Completion Codes.
placed in a pending delete state; the space taken by
CRRZI0216E The replace failed when those modules is not immediately available for reuse.
attempting to replace a primary User response:
member name while the PDSE is For more information about this error, see the
open for update, but the input following topic in z/OS V1R10.0 DFSMS Macro
TTR has not been defined for that Instructions for Data Sets: STOW Completion Codes.
member.
CRRZI0220E The specified name could not be
Explanation:
found.
The STOW macro, updating partitioned data set
directory (BPAM), failed. The replace failed when Explanation:
attempting to replace a primary member name. The

62 Developer for z/OS: Troubleshooting and Support

The STOW macro, updating partitioned data set CRRZI0225E The concatenation number
directory (BPAM), failed. The specified name cannot specified is greater than the
be found. concatenation number of the last
data set in the concatenation.
User response:
Verify the name. For more information about this error, Explanation:
see the following topic in z/OS V1R10.0 DFSMS Macro The DESERV macro GET_ALL function failed. This
Instructions for Data Sets: STOW Completion Codes. function retrieves all member names and directory
entries from a PDSE or PDS, failed. The concatenation
CRRZI0221E Dynamic allocation failure for PDS
number specified is greater than the concatenation
directory
number of the last data set in the concatenation.
Explanation:
User response:
Allocating a data set by using dynalloc() failed.
For more information about this error, see the
User response: following topic in z/OS V1R10.0 DFSMS Macro
For more information about this error, see the Instructions for Data Sets (SC26-7408): DESERV
following topic in z/OS V1R10.0 XL C/C++ Run-Time GET_ALL Function Reason Codes.
Library Reference (SA22-7821): dynalloc() -- Allocate a
CRRZI0226E Address of the DEB is 0 or DEB is
Data Set.
input but the DCB pointed to by
CRRZI0222E Get all member names from PDS the DEB does not point back to the
failed. DEB.
Explanation: Explanation:
The DESERV macro GET_ALL function failed. This DESERV macro GET_ALL function failed. This function
function retrieves all member names and directory retrieves all member names and directory entries from
entries from a PDSE or PDS. a PDSE or PDS. The address of the DEB is 0 or the DEB
is input but the DCB that the DEB points to does not
User response:
point back to it.
For more information about this error, see the
following topic in z/OS V1R10.0 DFSMS Macro User response:
Instructions for Data Sets (SC26-7408): DESERV For more information about this error, see the
GET_ALL Function Reason Codes. following topic in z/OS V1R10.0 DFSMS Macro
Instructions for Data Sets (SC26-7408): DESERV
CRRZI0223E The ID, length, or level of the
Functions Common Reason Codes.
parameter list is invalid.
CRRZI0227E The passed DCB is not open.
Explanation:
The DESERV macro GET_ALL function failed. The ID, Explanation:
length, or level of the parameter list is invalid. This DESERV macro GET_ALL function failed. This function
function retrieves all member names and directory retrieves all member names and directory entries from
entries from a PDSE or PDS. a PDSE or PDS. The passed DCB is not open.
User response: User response:
For more information about this error, see the For more information about this error, see the
following topic in z/OS V1R10.0 DFSMS Macro following topic in z/OS V1R10.0 DFSMS Macro
Instructions for Data Sets (SC26-7408): DESERV Instructions for Data Sets (SC26-7408): DESERV
GET_ALL Function Reason Codes. Functions Common Reason Codes.
CRRZI0224E This function requires a PDSE data CRRZI0228E The address of the DCB is zero.
set.
Explanation:
Explanation: DESERV macro GET_ALL function failed. This function
The DESERV macro GET_ALL function failed. This retrieves all member names and directory entries from
function retrieves all member names and directory a PDSE or PDS. The address of the DCB is zero.
entries from a PDSE or PDS. It requires a PDSE data
User response:
set.
For more information about this error, see the
User response: following topic in z/OS V1R10.0 DFSMS Macro
For more information about this error, see the Instructions for Data Sets (SC26-7408): DESERV
following topic in z/OS V1R10.0 DFSMS Macro Functions Common Reason Codes.
Instructions for Data Sets (SC26-7408): DESERV
GET_ALL Function Reason Codes.

Troubleshooting and support 63

CRRZI0229E To pass the DEB the caller must be The DESERV macro GET_ALL function failed This
supervisor state or a system key. function retrieves all member names and directory
entries from a PDSE or PDS. The connect intent
Explanation:
specified is not valid with this function.
DESERV macro GET_ALL function failed. This function
retrieves all member names and directory entries from User response:
a PDSE or PDS. To pass the DEB the caller must be in For more information about this error, see the
supervisor state or a system key. following topic in z/OS V1R10.0 DFSMS Macro
Instructions for Data Sets (SC26-7408): DESERV
User response: GET_ALL Function Reason Codes.
For more information about this error, see the
following topic in z/OS DFSMS Macro Instructions for CRRZI0234E The CONN_INTENT(HOLD)
Data Sets: DESERV Functions Common Reason Codes. requires the caller of function
GET_ALL to be in supervisor state
CRRZI0230E The FUNC value is incorrect. or system key.
Explanation: Explanation:
The DESERV macro GET_ALL function failed. This DESERV macro GET_ALL function failed. This function
function retrieves all member names and directory retrieves all member names and directory entries from
entries from a PDSE or PDS. The FUNC value is a PDSE or PDS. The CONN_INTENT(HOLD) requires
incorrect. the caller of function GET_ALL to be in supervisor state
User response: or system key.
For more information about this error, see the User response:
following topic in z/OS V1R10.0 DFSMS Macro For more information about this error, see the
Instructions for Data Sets (SC26-7408): DESERV following topic in z/OS V1R10.0 DFSMS Macro
Functions Common Reason Codes. Instructions for Data Sets (SC26-7408): DESERV
CRRZI0231E The gap specified is too large. GET_ALL Function Reason Codes.
The gap must be larger than CRRZI0235E The DEBCHK macro failed. The
DESP_ENTRY_GAP_MAX. DCB or DEB is invalid.
Explanation: Explanation:
The DESERV macro GET_ALL function failed. This The DESERV macro GET_ALL function failed. This
function retrieves all member names and directory function retrieves all member names and directory
entries from a PDSE or PDS. The gap specified entries from a PDSE or PDS. The DEBCHK macro failed.
is too large. The gap must be larger than The DCB or DEB is invalid.
DESP_ENTRY_GAP_MAX.
User response:
User response: For more information about this error, see the
For more information about this error, see the following topic in z/OS V1R10.0 DFSMS Macro
following topic in z/OS V1R10.0 DFSMS Macro Instructions for Data Sets (SC26-7408): DESERV
Instructions for Data Sets (SC26-7408): DESERV Functions Common Reason Codes.
GET_ALL Function Reason Codes.
CRRZI0236E FREEMAIN failure.
CRRZI0232E The address of the AREAPTR is 0.
Explanation:
Explanation: The DESERV macro GET_ALL function failed. This
The DESERV macro GET_ALL function failed. This function retrieves all member names and directory
function retrieves all member names and directory entries from a PDSE or PDS. FREEMAIN failure.
entries from a PDSE or PDS. The address of the
AREAPTR is 0. User response:
For more information about this error, see the
User response: following topic in z/OS V1R10.0 DFSMS Macro
For more information about this error, see the Instructions for Data Sets (SC26-7408): DESERV
following topic in z/OS V1R10.0 DFSMS Macro GET_ALL Function Reason Codes.
Instructions for Data Sets (SC26-7408): DESERV
GET_ALL Function Reason Codes. CRRZI0237E No members in directory.
CRRZI0233E The connect intent specified is not Explanation:
valid with this function. The DESERV GET_ALL function failed. This function
retrieves SMDEs for all member names (primary and
Explanation: alias) of a PDSE and can establish connections to
members. The directory contains no members.

64 Developer for z/OS: Troubleshooting and Support

User response: For more information about this error, see the
For more information about this error, see the following topic in z/OS DFSMS Macro Instructions for
following topic in z/OS V1R10.0 DFSMS Macro Data Sets (SC26-7408): BLDL--Build a Directory Entry
Instructions for Data Sets (SC26-7408): DESERV List (BPAM).
GET_ALL Function Reason Codes.
CRRZI0242E Invalid data extent block (DEB), or
CRRZI0238E Get PDS directory information the DEB is not owned by a TCB in
failed. 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 Explanation
or partitioned data set extended (PDSE). The BLDL macro failed. This macro obtains a list of
information from the directory of a partitioned data set
User response:
or partitioned data set extended (PDSE). This error has
For more information about this error, see the
one of the following causes:
following topic in z/OS DFSMS Macro Instructions for
Data Sets (SC26-7408): BLDL--Build a Directory Entry • A data extent block (DEB) is invalid.
List (BPAM). • The DEB is not owned by a TCB in the current family
CRRZI0239E One or more entries in the list of TCBs.
could not be filled; the list • The UCB address in the DEB is zero.
supplied can be invalid.
User response:
Explanation: For more information about this error, see the
The BLDL macro failed. This macro obtains a list of following topic in z/OS DFSMS Macro Instructions for
information from the directory of a partitioned data set Data Sets (SC26-7408): BLDL--Build a Directory Entry
or partitioned data set extended (PDSE). One or more List (BPAM).
entries in the list cannot be filled; the list supplied can
be invalid. CRRZI0275E Operation terminated.

User response: Explanation:

For more information about this error, see the A Language Environment® operation failed.
following topic in z/OS DFSMS Macro Instructions for User response:
Data Sets (SC26-7408): BLDL--Build a Directory Entry Verify that you are using the correct version of
List (BPAM). Language Environment and that it is set up correctly.
CRRZI0240E A permanent I/O error was For more information about this error, see the
detected when the system rsecomm.log and ffs*.log files on the remote
attempted to search the directory. system.

Explanation: CRRZI0277E System ABEND {0}.

The BLDL macro failed. This macro obtains a list of
information from the directory of a partitioned data set Explanation
or partitioned data set extended (PDSE). A permanent
{0}
I/O error was detected when the system attempted to
The abend code.
search the directory.
A system ABEND occurred.
User response:
For more information about this error, see the User response:
following topic in z/OS DFSMS Macro Instructions for For more information about this error, see the
Data Sets (SC26-7408): BLDL--Build a Directory Entry rsecomm.log and ffs*.log files on the remote
List (BPAM). system. Consult with your system administrator. If
you cannot solve the problem, contact IBM Software
CRRZI0241E Insufficient virtual storage was Support.
available.
CRRZI0278E The OPEN/EOV volume security
Explanation: exit requested that the volume be
The BLDL macro failed. This macro obtains a list of rejected.
information from the directory of a partitioned data set
or partitioned data set extended (PDSE). Insufficient User response:
virtual storage was available. For more information about this error, see the
rsecomm.log and ffs*.log files on the remote
User response:

Troubleshooting and support 65

system. Consult with your system administrator. If For more information about this error, see the
you cannot solve the problem, contact IBM Software rsecomm.log and ffs*.log files on the remote
Support. system. Consult with your system administrator. If
you cannot solve the problem, contact IBM Software
CRRZI0279E An OPEN was issued for a RACF®-
Support.
protected data set to which the
caller was not authorized. CRRZI0284E I/O operation failed.
User response: Explanation:
For more information about this error, see the An I/O operation failed when renaming data set.
rsecomm.log and ffs*.log files on the remote
User response:
system. Consult with your system administrator. If
Determine whether there is a resource shortage and
you cannot solve the problem, contact IBM Software
try the operation again.
Support.
CRRZI0285E TGET macro failed.
CRRZI0280E A data set opened for output used
all the primary space, and no Explanation:
secondary space was requested. An I/O operation failed because the TGET macro
failed.
User response:
For more information about this error, see the User response:
rsecomm.log and ffs*.log files on the remote For more information about this error, see the
system. Consult with your system administrator. If rsecomm.log and ffs*.log files on the remote
you cannot solve the problem, contact IBM Software system. Consult with your system administrator. If
Support. you cannot solve the problem, contact IBM Software
Support.
CRRZI0281E An installation DADSM exit,
IGGPRE00, rejected the extend CRRZI0286E TPUT macro failed.
request.
Explanation:
User response: An I/O operation failed because the TPUT macro
For more information about this error, see the failed.
rsecomm.log and ffs*.log files on the remote
User response:
system. Consult with your system administrator. If
For more information about this error, see the
you cannot solve the problem, contact IBM Software
rsecomm.log and ffs*.log files on the remote
Support.
system. Consult with your system administrator. If
CRRZI0282E A data set opened for output you cannot solve the problem, contact IBM Software
used all space available to or on Support.
the current volume, and no more
CRRZI0287E Provide relative position failed.
volumes were available.
Explanation:
User response:
An I/O operation failed because an attempt to provide
For more information about this error, see the
a relative position failed.
rsecomm.log and ffs*.log files on the remote
system. Consult with your system administrator. If User response:
you cannot solve the problem, contact IBM Software For more information about this error, see the
Support. rsecomm.log and ffs*.log files on the remote
system. Consult with your system administrator. If
CRRZI0283E A multi-volume physical
you cannot solve the problem, contact IBM Software
sequential data set was being
Support.
written on a direct access device.
All space was filled on the volume, CRRZI0288E DEVTYPE macro failed.
and an attempt was made to
Explanation:
obtain space on the next specified
An I/O operation failed because the DEVTYPE macro
volume. Either the space was
failed.
not available on that volume, the
data set already existed on that User response:
volume, or there is no space For more information about this error, see the
available in the VTOC or the VTOC rsecomm.log and ffs*.log files on the remote
index. system. Consult with your system administrator. If
User response:

66 Developer for z/OS: Troubleshooting and Support

you cannot solve the problem, contact IBM Software For more information about this error, see the
Support. rsecomm.log and ffs*.log files on the remote
system. Consult with your system administrator. If
CRRZI0289E RDJFCB macro failed.
you cannot solve the problem, contact IBM Software
Explanation: Support.
An I/O operation failed because the RDJFCB macro
CRRZI0294E No volume containing any part
failed.
of data set was mounted, nor
User response: was there a unit available for
For more information about this error, see the mounting.
rsecomm.log and ffs*.log files on the remote
Explanation:
system. Consult with your system administrator. If
An I/O operation failed because no volume that
you cannot solve the problem, contact IBM Software
contains any part of the data set was mounted and
Support.
no unit was available for mounting.
CRRZI0290E TRKCALC macro failed.
User response:
Explanation: For more information about this error, see the
An I/O operation failed because the TRKCALC macro rsecomm.log and ffs*.log files on the remote
failed. system. Consult with your system administrator. If
you cannot solve the problem, contact IBM Software
User response:
Support.
For more information about this error, see the
rsecomm.log and ffs*.log files on the remote CRRZI0295E An unusual condition was
system. Consult with your system administrator. If encountered on one or more
you cannot solve the problem, contact IBM Software volumes.
Support.
Explanation:
CRRZI0291E Cataloging a non-VSAM data set An I/O operation failed because an unusual condition
failed. was encountered on one or more volumes.
Explanation: User response:
An I/O operation failed because an attempt to catalog For more information about this error, see the
a non-VSAM data set failed. rsecomm.log and ffs*.log files on the remote
system. Consult with your system administrator. If
User response:
you cannot solve the problem, contact IBM Software
For more information about this error, see the
Support.
rsecomm.log and ffs*.log files on the remote
system. Consult with your system administrator. If CRRZI0296E Deleting a data set from the VTOC
you cannot solve the problem, contact IBM Software failed.
Support.
Explanation:
CRRZI0292E Uncataloging a non-VSAM data set An I/O operation failed because an attempt to delete a
failed. data set from the VTOC failed.
Explanation: User response:
An I/O operation failed because of an attempt to For more information about this error, see the
uncatalog a non-VSAM data set failed. rsecomm.log and ffs*.log files on the remote
system. Consult with your system administrator. If
User response:
you cannot solve the problem, contact IBM Software
For more information about this error, see the
Support.
rsecomm.log and ffs*.log files on the remote
system. Consult with your system administrator. If CRRZI0297E Position for access failed.
you cannot solve the problem, contact IBM Software
Explanation:
Support.
An I/O operation failed because a request for the
CRRZI0293E Renaming a data set in the VTOC position for access failed.
failed.
User response:
Explanation: For more information about this error, see the
An I/O operation failed because an attempt to rename rsecomm.log and ffs*.log files on the remote
a data set in the VTOC failed. system. Consult with your system administrator. If
you cannot solve the problem, contact IBM Software
User response:
Support.

Troubleshooting and support 67

CRRZI0298E Dynamic allocation failed. Explanation:
Dynamic allocation failed because of duplicate data
User response: set names on the volume.
For more information about this error, see the
rsecomm.log and ffs*.log files on the remote User response:
system. Consult with your system administrator. If For more information about this error, see the
you cannot solve the problem, contact IBM Software rsecomm.log and ffs*.log files on the remote
Support. system. Consult with your system administrator. If
you cannot solve the problem, contact IBM Software
CRRZI0299E Duplicate data set name on the Support.
volume.

0300-level messages
CRRZI0300E The volume table of contents Explanation:
(VTOC) for the specified or Dynamic allocation failed because the requested
defaulted volume for a new data absolute track is not available.
set request had insufficient space User response:
in the VTOC index for a new entry, For more information about this error, see the
or did not have the minimum rsecomm.log and ffs*.log files on the remote
number of data set control blocks system. Consult with your system administrator. If
(DSCBs) required to allocate the you cannot solve the problem, contact IBM Software
data set. Support.
CRRZI0303E More space was requested than is
Explanation
available on the DASD volume, or
Dynamic allocation failed for one of the following
the DASD volume's VTOC is full,
reasons:
or the DASD volume's VTOC Index
• The volume table of contents (VTOC) for the (VTOCIX) is full.
specified or defaulted volume for a new data set
request had insufficient space in the VTOC index for Explanation
a new entry. Dynamic allocation failed for one of the following
• The VTOC did not have the minimum number of data reasons:
set control blocks (DSCBs) required to allocate the
• More space was requested than is available on the
data set.
DASD volume.
User response: • The VTOC of the DASD volume is full.
For more information about this error, see the
rsecomm.log and ffs*.log files on the remote • The VTOC Index (VTOCIX) of the DASD volume is full.
system. Consult with your system administrator. If User response:
you cannot solve the problem, contact IBM Software For more information about this error, see the
Support. rsecomm.log and ffs*.log files on the remote
CRRZI0301E Space on the direct access storage system. Consult with your system administrator. If
device (DASD) containing the you cannot solve the problem, contact IBM Software
requested volume could not be Support.
obtained. CRRZI0304E The average block length specified
Explanation: on text unit key DALAVGR (key
Dynamic allocation failed because space on the 0009) was greater than the track
direct access storage device (DASD) containing the capacity of the requested DASD
requested volume cannot be obtained. volume.

User response: Explanation:

For more information about this error, see the Dynamic allocation failed because the average block
rsecomm.log and ffs*.log files on the remote length on text unit key DALAVGR (key 0009) was
system. Consult with your system administrator. If greater than the track capacity of the requested DASD
you cannot solve the problem, contact IBM Software volume.
Support. User response:
CRRZI0302E Requested absolute track is not For more information about this error, see the
available. rsecomm.log and ffs*.log files on the remote

68 Developer for z/OS: Troubleshooting and Support

system. Consult with your system administrator. If Dynamic allocation failed because a profile for the
you cannot solve the problem, contact IBM Software specified data set on this volume exists in the
Support. Resource Access Control Facility (RACF) data set.
CRRZI0305E Invalid DADSM REALLOC User response:
parameter list. For more information about this error, see the
rsecomm.log and ffs*.log files on the remote
Explanation:
system. Consult with your system administrator. If
Dynamic allocation failed because of an invalid DADSM
you cannot solve the problem, contact IBM Software
REALLOC parameter list.
Support.
User response:
CRRZI0309E User is not authorized to define
For more information about this error, see the
this data set. The user has the
rsecomm.log and ffs*.log files on the remote
automatic data set protection
system. Consult with your system administrator. If
characteristic without the RACF
you cannot solve the problem, contact IBM Software
authorization to define data sets.
Support.
Explanation:
CRRZI0306E The system did not allocate the
Dynamic allocation failed because the user is not
directory for a new partitioned
authorized to define this data set. The user has the
data set (PDS) because the space
automatic data set protection characteristic without
requested for the directory on
the RACF authorization to define data sets.
text unit key DALDIR (key 000C)
exceeded the space available on User response:
the specified volume. For more information about this error, see the
rsecomm.log and ffs*.log files on the remote
Explanation:
system. Consult with your system administrator. If
Dynamic allocation failed because the system did
you cannot solve the problem, contact IBM Software
not allocate the directory for a new partitioned data
Support.
set (PDS). The space requested for the directory on
text unit key DALDIR (key 000C) exceeded the space CRRZI0310E Installation exit rejected this
available on the specified volume. request.
User response: Explanation:
For more information about this error, see the Dynamic allocation failed because the installation exit
rsecomm.log and ffs*.log files on the remote rejected this request.
system. Consult with your system administrator. If
User response:
you cannot solve the problem, contact IBM Software
For more information about this error, see the
Support.
rsecomm.log and ffs*.log files on the remote
CRRZI0307E No space parameter given for system. Consult with your system administrator. If
a new data set or zero space you cannot solve the problem, contact IBM Software
requested at absolute track zero. Support.
Explanation: CRRZI0311E Space request was rejected by
Dynamic allocation failed because no space parameter installation exit.
was given for a new data set or zero space was
Explanation:
requested at absolute track zero.
Dynamic allocation failed because a space request
User response: was rejected by the installation exit.
For more information about this error, see the
User response:
rsecomm.log and ffs*.log files on the remote
For more information about this error, see the
system. Consult with your system administrator. If
rsecomm.log and ffs*.log files on the remote
you cannot solve the problem, contact IBM Software
system. Consult with your system administrator. If
Support.
you cannot solve the problem, contact IBM Software
CRRZI0308E A profile for the specified data Support.
set on this volume already exists
CRRZI0312E Non-SMS managed data set
in the Resource Access Control
cannot be created on an SMS-
Facility (RACF) data set.
managed volume.
Explanation:
Explanation:

Troubleshooting and support 69

Dynamic allocation failed because a non-SMS you cannot solve the problem, contact IBM Software
managed data set cannot be created on an SMS- Support.
managed volume.
CRRZI0317E CATALOG space is exhausted on
User response: the control volume.
For more information about this error, see the
Explanation:
rsecomm.log and ffs*.log files on the remote
Dynamic allocation failed because CATALOG space is
system. Consult with your system administrator. If
exhausted on the control volume.
you cannot solve the problem, contact IBM Software
Support. User response:
For more information about this error, see the
CRRZI0313E An unexpected or internal error
rsecomm.log and ffs*.log files on the remote
code was received by Allocation.
system. Consult with your system administrator. If
User response: you cannot solve the problem, contact IBM Software
For more information about this error, see the Support.
rsecomm.log and ffs*.log files on the remote
CRRZI0318E A CATALOG I/O error has occurred.
system. Consult with your system administrator. If
you cannot solve the problem, contact IBM Software Explanation:
Support. Dynamic allocation failed because a CATALOG I/O
error occurred.
CRRZI0314E Required CATALOG volume is
currently not mounted. User response:
For more information about this error, see the
Explanation:
rsecomm.log and ffs*.log files on the remote
Dynamic allocation failed because a required CATALOG
system. Consult with your system administrator. If
volume is currently not mounted.
you cannot solve the problem, contact IBM Software
User response: Support.
For more information about this error, see the
CRRZI0319E CATALOG error.
rsecomm.log and ffs*.log files on the remote
system. Consult with your system administrator. If Explanation:
you cannot solve the problem, contact IBM Software Dynamic allocation failed, because of a CATALOG error.
Support.
User response:
CRRZI0315E Either the existing catalog For more information about this error, see the
structure is inconsistent with the rsecomm.log and ffs*.log files on the remote
operation, or the program was system. Consult with your system administrator. If
not authorized to perform the you cannot solve the problem, contact IBM Software
operation. Support.
Explanation: CRRZI0320E Data set not on volume as
Dynamic allocation failed because either the existing indicated in the catalog or volume
catalog structure is inconsistent with the operation, or text unit.
the program was not authorized to run the operation.
Explanation:
User response: Dynamic allocation failed, because the data set was
For more information about this error, see the not on the volume as indicated in the catalog or
rsecomm.log and ffs*.log files on the remote volume text unit.
system. Consult with your system administrator. If
User response:
you cannot solve the problem, contact IBM Software
For more information about this error, see the
Support.
rsecomm.log and ffs*.log files on the remote
CRRZI0316E The index structure necessary to system. Consult with your system administrator. If
catalog the data set does not exist. you cannot solve the problem, contact IBM Software
Support.
Explanation:
Dynamic allocation failed because the index structure CRRZI0321E OBTAIN I/O error. During data set
necessary to catalog the data set does not exist. allocation, an uncorrectable I/O
error occurred when the system
User response:
attempted to obtain a data set
For more information about this error, see the
control block (DSCB).
rsecomm.log and ffs*.log files on the remote
system. Consult with your system administrator. If Explanation:

70 Developer for z/OS: Troubleshooting and Support

Dynamic allocation failed because of an OBTAIN I/O User response:
error. During data set allocation, an uncorrectable I/O For more information about this error, see the
error occurred when the system attempted to obtain a rsecomm.log and ffs*.log files on the remote
data set control block (DSCB). system. Consult with your system administrator. If
you cannot solve the problem, contact IBM Software
User response:
Support.
For more information about this error, see the
rsecomm.log and ffs*.log files on the remote CRRZI0326E Requested data set is unavailable.
system. Consult with your system administrator. If The data set is allocated to
you cannot solve the problem, contact IBM Software another job and its usage attribute
Support. conflicts with this request.
CRRZI0322E An invalid work area pointer was Explanation:
supplied. Dynamic allocation failed because the requested data
set is unavailable. The data set is allocated to another
Explanation:
job and its usage attribute conflicts with this request.
Dynamic allocation failed because an invalid work area
pointer was supplied. User response:
For more information about this error, see the
User response:
rsecomm.log and ffs*.log files on the remote
For more information about this error, see the
system. Consult with your system administrator. If
rsecomm.log and ffs*.log files on the remote
you cannot solve the problem, contact IBM Software
system. Consult with your system administrator. If
Support.
you cannot solve the problem, contact IBM Software
Support. CRRZI0327E Device(s) not available.
CRRZI0323E The absolute address passed was Explanation:
not within the boundaries of the Dynamic allocation failed because one or more devices
VTOC. are not available.
Explanation: User response:
Dynamic allocation failed because the absolute For more information about this error, see the
address passed was not within the boundaries of the rsecomm.log and ffs*.log files on the remote
VTOC. system. Consult with your system administrator. If
you cannot solve the problem, contact IBM Software
User response:
Support.
For more information about this error, see the
rsecomm.log and ffs*.log files on the remote CRRZI0328E Specified volume or an acceptable
system. Consult with your system administrator. If volume is not mounted, and
you cannot solve the problem, contact IBM Software user does not have volume
Support. mounting authorization through
the DYNALLOC request.
CRRZI0324E Virtual storage unavailable.
Explanation:
Explanation:
Dynamic allocation failed. The specified volume or an
Dynamic allocation failed because virtual storage is
acceptable volume is not mounted, and the user is not
unavailable.
authorized to mount a volume through the DYNALLOC
User response: request.
For more information about this error, see the
User response:
rsecomm.log and ffs*.log files on the remote
For more information about this error, see the
system. Consult with your system administrator. If
rsecomm.log and ffs*.log files on the remote
you cannot solve the problem, contact IBM Software
system. Consult with your system administrator. If
Support.
you cannot solve the problem, contact IBM Software
CRRZI0325E Request for exclusive use of Support.
a shared data set cannot be
CRRZI0329E Device name specified is
honored.
undefined.
Explanation:
Explanation:
Dynamic allocation failed because a request for
Dynamic allocation failed because the device name
exclusive use of a shared data set cannot be
specified is undefined.
completed.
User response:

Troubleshooting and support 71

For more information about this error, see the CRRZI0334E Permanently resident or reserved
rsecomm.log and ffs*.log files on the remote volume on required device.
system. Consult with your system administrator. If
Explanation:
you cannot solve the problem, contact IBM Software
Dynamic allocation failed because a permanently
Support.
resident or reserved volume is on the required device.
CRRZI0330E Requested volume is not available.
User response:
Explanation: For more information about this error, see the
Dynamic allocation failed because the requested rsecomm.log and ffs*.log files on the remote
volume is not available. system. Consult with your system administrator. If
you cannot solve the problem, contact IBM Software
User response:
Support.
For more information about this error, see the
rsecomm.log and ffs*.log files on the remote CRRZI0335E More than one device required
system. Consult with your system administrator. If for a request specifying a specific
you cannot solve the problem, contact IBM Software device.
Support.
Explanation:
CRRZI0331E Eligible device types do not Dynamic allocation failed because more than one
contain enough devices. device is required for a request that specifies a device.
Explanation: User response:
Dynamic allocation failed because eligible device For more information about this error, see the
types do not contain enough devices. rsecomm.log and ffs*.log files on the remote
system. Consult with your system administrator. If
User response:
you cannot solve the problem, contact IBM Software
For more information about this error, see the
Support.
rsecomm.log and ffs*.log files on the remote
system. Consult with your system administrator. If CRRZI0336E Space unavailable in task input
you cannot solve the problem, contact IBM Software output table (TIOT).
Support.
Explanation:
CRRZI0332E Specified volume or device in use Dynamic allocation failed because space is unavailable
by system. in the task input/output table (TIOT).
Explanation: User response:
Dynamic allocation failed because the specified For more information about this error, see the
volume or device is in use by the system. rsecomm.log and ffs*.log files on the remote
system. Consult with your system administrator. If
User response:
you cannot solve the problem, contact IBM Software
For more information about this error, see the
Support.
rsecomm.log and ffs*.log files on the remote
system. Consult with your system administrator. If CRRZI0337E Required catalog is not mounted,
you cannot solve the problem, contact IBM Software and user does not have volume
Support. mounting authorization.
CRRZI0333E Volume mounted on ineligible Explanation:
permanently resident or reserved Dynamic allocation failed because the required catalog
device. is not mounted, and the user is not authorized to
mount a volume.
Explanation:
Dynamic allocation failed because the volume is User response:
mounted on an ineligible permanently resident or For more information about this error, see the
reserved device. rsecomm.log and ffs*.log files on the remote
system. Consult with your system administrator. If
User response:
you cannot solve the problem, contact IBM Software
For more information about this error, see the
Support.
rsecomm.log and ffs*.log files on the remote
system. Consult with your system administrator. If CRRZI0338E CATALOG LOCATE error. Either the
you cannot solve the problem, contact IBM Software data set name specified is in error,
Support. or a system error occurred when
processing the data set name.

72 Developer for z/OS: Troubleshooting and Support

Explanation: Explanation:
Dynamic allocation failed because of a CATALOG Dynamic allocation failed because an unexpected
LOCATE error. Either the data set name specified is in return code was returned by catalog LOCATE.
error, or a system error occurred when processing the
User response:
data set name.
For more information about this error, see the
User response: rsecomm.log and ffs*.log files on the remote
For more information about this error, see the system. Consult with your system administrator. If
rsecomm.log and ffs*.log files on the remote you cannot solve the problem, contact IBM Software
system. Consult with your system administrator. If Support.
you cannot solve the problem, contact IBM Software
CRRZI0343E Dynamic allocation of new file
Support.
failed.
CRRZI0339E Permanent I/O error processing
User response:
cataloged data set.
For more information about this error, see the
Explanation: rsecomm.log and ffs*.log files on the remote
Dynamic allocation failed because of a permanent I/O system. Consult with your system administrator. If
error while processing the cataloged data set. you cannot solve the problem, contact IBM Software
Support.
User response:
For more information about this error, see the CRRZI0344E Dynamic deallocation failed.
rsecomm.log and ffs*.log files on the remote
User response:
system. Consult with your system administrator. If
For more information about this error, see the
you cannot solve the problem, contact IBM Software
rsecomm.log and ffs*.log files on the remote
Support.
system. Consult with your system administrator. If
CRRZI0340E Insufficient real or virtual storage you cannot solve the problem, contact IBM Software
for processing cataloged data set. Support.
Explanation: CRRZI0345E Output data was truncated.
Dynamic allocation failed because of insufficient real
Explanation:
or virtual storage for processing the cataloged data
An I/O operation failed because the output data was
set.
truncated.
User response:
User response:
For more information about this error, see the
For more information about this error, see the
rsecomm.log and ffs*.log files on the remote
rsecomm.log and ffs*.log files on the remote
system. Consult with your system administrator. If
system. Consult with your system administrator. If
you cannot solve the problem, contact IBM Software
you cannot solve the problem, contact IBM Software
Support.
Support.
CRRZI0341E An unsuccessful attempt was
CRRZI0346E FCB is corrupted.
made to access a catalog that was
locked for recovery. The job does Explanation:
not have the proper authorization An I/O operation failed because the file control block
to perform this function. is corrupted.
Explanation: User response:
Dynamic allocation failed because an unsuccessful For more information about this error, see the
attempt was made to access a catalog that was locked rsecomm.log and ffs*.log files on the remote
for recovery. The job does not have authorization to system. Consult with your system administrator. If
run this function. you cannot solve the problem, contact IBM Software
Support.
User response:
For more information about this error, see the CRRZI0347E There was no room left in a
rsecomm.log and ffs*.log files on the remote physical record for anymore DBCS
system. Consult with your system administrator. If characters.
you cannot solve the problem, contact IBM Software
Explanation:
Support.
An I/O operation failed because there was no room left
CRRZI0342E An unexpected return code was in a physical record for any more DBCS characters.
returned by catalog LOCATE.
User response:

Troubleshooting and support 73

For more information about this error, see the CRRZI0351E An attempt was made to extend a
rsecomm.log and ffs*.log files on the remote file that allows writing, but the file
system. Consult with your system administrator. If cannot be extended.
you cannot solve the problem, contact IBM Software
Explanation:
Support.
An I/O operation failed because an attempt was made
CRRZI0348E There was not enough room in a to extend a file that allows writing, but the file cannot
record to start any DBCS string or be extended.
a redundant SO was written to the
User response:
file before an SI.
For more information about this error, see the
rsecomm.log and ffs*.log files on the remote
Explanation system. Consult with your system administrator. If
An I/O operation failed for one of the following you cannot solve the problem, contact IBM Software
reasons: Support.
• There was not enough room in a record to start any CRRZI0352E OPEN macro failed.
DBCS string.
Explanation:
• A redundant SO was written to the file before an SI. An I/O operation failed because the OPEN macro
User response: failed.
For more information about this error, see the User response:
rsecomm.log and ffs*.log files on the remote For more information about this error, see the
system. Consult with your system administrator. If rsecomm.log and ffs*.log files on the remote
you cannot solve the problem, contact IBM Software system. Consult with your system administrator. If
Support. you cannot solve the problem, contact IBM Software
CRRZI0349E There was not enough room to Support.
start a DBCS string and data was CRRZI0353E CLOSE macro failed.
written anyway, with an SI to end
it. Explanation:
An I/O operation failed because the CLOSE macro
Explanation: failed.
An I/O operation failed because there was not enough
room to start a DBCS string and data was written User response:
anyway with an SI to end it. For more information about this error, see the
rsecomm.log and ffs*.log files on the remote
User response: system. Consult with your system administrator. If
For more information about this error, see the you cannot solve the problem, contact IBM Software
rsecomm.log and ffs*.log files on the remote Support.
system. Consult with your system administrator. If
you cannot solve the problem, contact IBM Software CRRZI0354E Find a data set member failed.
Support. Explanation:
CRRZI0350E An SI was written before the The FIND macro, Establish the Beginning of a Data
last double byte character is Set Member (BPAM), failed when finding a data set
completed, thereby forcing z/OS member.
to fill in the last byte of the DBCS User response:
string with a padding byte X'FE'. For more information about this error, see the
Explanation: following topic in z/OS V1R10 DFSMS Macro
An I/O operation failed because an SI was written Instructions for Data Sets (SC26-7408): FIND--
before the last double byte character was completed. Establish the Beginning of a Data Set Member (BPAM).
z/OS must complete the last byte of the DBCS string CRRZI0355E Name not found.
with a padding byte X'FE'.
Explanation:
User response: The FIND macro, Establish the Beginning of a Data
For more information about this error, see the Set Member (BPAM), failed when finding a data set
rsecomm.log and ffs*.log files on the remote member. The data set name was not found.
system. Consult with your system administrator. If
you cannot solve the problem, contact IBM Software User response:
Support.

74 Developer for z/OS: Troubleshooting and Support

For more information about this error, see the For more information about this error, see the
following topic in z/OS V1R10 DFSMS Macro following topic in z/OS V1R10 DFSMS Macro
Instructions for Data Sets (SC26-7408): FIND-- Instructions for Data Sets (SC26-7408): FIND--
Establish the Beginning of a Data Set Member (BPAM). Establish the Beginning of a Data Set Member (BPAM).
CRRZI0356E The PDSE is open for output and CRRZI0360E An I/O error occurred while
the FIND macro was issued to flushing system buffers containing
point to a member other than the member data.
one currently processing.
Explanation:
Explanation: The FIND macro, Establish the Beginning of a Data
The FIND macro, Establish the Beginning of a Data Set Member (BPAM), failed when finding a data set
Set Member (BPAM), failed when finding a data set member. An I/O error occurred while flushing system
member. The PDSE is open for output and the FIND buffers containing member data.
macro was issued to point to a member other than the
User response:
one currently processing.
For more information about this error, see the
User response: following topic in z/OS V1R10 DFSMS Macro
For more information about this error, see the Instructions for Data Sets (SC26-7408): FIND--
following topic in z/OS V1R10 DFSMS Macro Establish the Beginning of a Data Set Member (BPAM).
Instructions for Data Sets (SC26-7408): FIND--
CRRZI0361E No DCB address was input.
Establish the Beginning of a Data Set Member (BPAM).
Explanation:
CRRZI0357E The caller has only RACF execute
The FIND macro, Establish the Beginning of a Data
authority to the PDSE.
Set Member (BPAM), failed when finding a data set
Explanation: member. No DCB address was provided.
The FIND macro, Establish the Beginning of a Data
User response:
Set Member (BPAM), failed when finding a data set
For more information about this error, see the
member. The caller has only RACF execute authority to
following topic in z/OS V1R10 DFSMS Macro
the PDSE.
Instructions for Data Sets (SC26-7408): FIND--
User response: Establish the Beginning of a Data Set Member (BPAM).
For more information about this error, see the
CRRZI0362E Insufficient virtual storage
following topic in z/OS V1R10 DFSMS Macro
available.
Instructions for Data Sets (SC26-7408): FIND--
Establish the Beginning of a Data Set Member (BPAM). Explanation:
The FIND macro, Establish the Beginning of a Data
CRRZI0358E The PDSE member's share options
Set Member (BPAM), failed when finding a data set
do not allow you to access it.
member. Insufficient virtual storage is available.
Explanation:
User response:
The FIND macro, Establish the Beginning of a Data
For more information about this error, see the
Set Member (BPAM), failed when finding a data set
following topic in z/OS V1R10 DFSMS Macro
member. The share options of the PDSE member do
Instructions for Data Sets (SC26-7408): FIND--
not allow you to access it.
Establish the Beginning of a Data Set Member (BPAM).
User response:
CRRZI0363E Invalid DEB, or DEB is not owned
For more information about this error, see the
by a TCB in the current family of
following topic in z/OS V1R10 DFSMS Macro
TCBs.
Instructions for Data Sets (SC26-7408): FIND--
Establish the Beginning of a Data Set Member (BPAM). Explanation:
The FIND macro, Establish the Beginning of a Data
CRRZI0359E Permanent I/O error during
Set Member (BPAM), failed when finding a data set
directory search.
member. The DEB is invalid or not owned by a TCB in
Explanation: the current family of TCBs.
The FIND macro, Establish the Beginning of a Data
User response:
Set Member (BPAM), failed when finding a data set
For more information about this error, see the
member. A permanent I/O error occurred during the
following topic in z/OS V1R10 DFSMS Macro
directory search.
Instructions for Data Sets (SC26-7408): FIND--
User response: Establish the Beginning of a Data Set Member (BPAM).

Troubleshooting and support 75

CRRZI0365E Out of memory. Explanation:
An attempt to lock the requested file failed. The
Explanation: resource name that was provided is invalid.
An out of memory error occurred.
User response:
User response: Verify whether another user locked the file and try the
Verify memory usage and increase the memory heap operation again. If the file is not locked by another
size. user, verify that you have authority to lock the file. If
CRRZI0366E Code page conversion failed with these actions do not solve the problem, contact IBM
{0}. Software Support.
CRRZI0372E The resource is not immediately
Explanation available.
{0} Explanation:
The name of the function for which the code page An attempt to lock the requested file failed. Another
conversion failed. user might have a lock on the file.
User response: User response:
For more information about this error, see the Verify whether another user locked the file and try the
rsecomm.log and ffs*.log files on the remote operation again. If the file is not locked by another
system. user, verify that you have authority to lock the file.
CRRZI0367E Code page {0} is not supported. CRRZI0373E A previous request for control of
the same resource has been made
Explanation for the same task. The task has
control of the resource.
{0}
The unsupported code page. Explanation:
An attempt to lock the requested file failed. Another
The code page conversion failed because the code user might have a lock on the file.
page is not supported.
User response:
User response: Verify whether another user locked the file and try the
Verify that the correct code page is used. If correcting operation again. If the file is not locked by another
the code page does not resolve the error, contact IBM user, verify that you have authority to lock the file.
Software Support.
CRRZI0374E Unlock failed.
CRRZI0369E Lock failed.
Explanation:
Explanation: An attempt to lock the requested file failed. Another
An attempt to lock the requested file failed. Another user might have a lock on the file.
user might have a lock on the file.
User response:
User response: Verify whether another user locked the file and try the
Verify whether another user locked the file and try the operation again. If the file is not locked by another
operation again. If the file is not locked by another user, verify that you have authority to lock the file.
user, verify that you have authority to lock the file.
CRRZI0375E The resource has been requested
CRRZI0370E A previous request for control of for the task, but the task has not
the same resource has been made been assigned control of it. The
for the same task. The task does task continues waiting.
not have control of the resource.
Explanation:
Explanation: An attempt to lock the requested file failed. Another
An attempt to lock the requested file failed. Another user might have a lock on the file.
user might have a lock on the file.
User response:
User response: Verify whether another user locked the file and try the
Verify whether another user locked the file and try the operation again. If the file is not locked by another
operation again. If the file is not locked by another user, verify that you have authority to lock the file.
user, verify that you have authority to lock the file.
CRRZI0376E Control of the resource has not
CRRZI0371E Invalid resource name. been requested by the active task,

76 Developer for z/OS: Troubleshooting and Support

 or the resource has already been mkdir WORKAREA
released.
3. Set the permissions so that all users have write
Explanation:
authority:
An attempt to lock the requested file failed. Another
user might have a lock on the file. chmod 777 /var/rdz/WORKAREA
User response:
4. To ensure that a log directory is created and that
Verify whether another user locked the file and try the
users have write authority for it, issue the following
operation again. If the file is not locked by another
commands and look for the logs directory:
user, verify that you have authority to lock the file.
CRRZI0377E Internal server error occurred. cd /var/rdz
ls -al
Explanation:
An unexpected internal server error occurred. 5. If the "logs" directory does not exist, then create it
by issuing the following command:
User response:
For more information about this error, see the mkdir logs
rsecomm.log and ffs*.log files on the remote
6. To set the permissions so that all users have write
system. Contact IBM Software Support.
authority to the /var/rdz/logs directory, issue
CRRZI0378E Exception occurred. the following command:
Explanation: chmod 777 logs
An unexpected server error occurred.
User response: CRRZI0383E The data set compression has
For more information about this error, see the failed.
rsecomm.log and ffs*.log files on the remote Explanation:
system. A request to compress a partitioned data set failed. If
CRRZI0379E The request has timed out because you used the Compress with Backup action, then a
there is no response from the backup copy of the data set is saved. In some cases,
server. the failure might occur before the data set is backed
up. In this case, a backup copy is not created.
User response:
For more information about this error, see the User response:
rsecomm.log and ffs*.log files on the remote If you used the Compress with Backup action and the
system. failure occurred after the backup, then you can restore
the data set from the backup copy.
CRRZI0380E No response from TSO command
server. CRRZI0384E The data set compression has
failed. Data Set is missing.
Explanation:
This error can occur while attempting to allocate a Explanation:
partitioned or sequential data set. Your user ID does A request to compress a partitioned data set failed
not have the necessary permission and there is no because the target data set cannot be found. A backup
ISPF Client Gateway in /var/rdz/WORKAREA. This data set is not created.
work area must be allocated and all users must have User response:
permission to write to the work area. Select a valid data set and try the operation again.
CRRZI0385E The data set compression has
User response failed. The data set is not a PDS.
1. To determine whether the work area was created, Explanation:
issue the following commands from either telnet or A request to compress a data set failed because the
MVS: target data set is not a partitioned data set. The
cd /var/rdz
compress action is not valid for data sets of type
ls -al sequential or PDSE (Library). A backup data set is not
created.
2. If the WORKAREA directory does not exist, then
create it by issuing the following command: User response:
Select a partitioned data set and try the operation
again.

Troubleshooting and support 77

CRRZI0386E Data set compression has failed. CRRZI0393E ALLOCATE failed. Record length is
Problems in allocating SYSUT data inconsistent with block size for
set. See the Error log for more this record format.
details.
User response:
User response: For more information about this error, see the
For more information about this error, see the rsecomm.log and ffs*.log files on the remote
rsecomm.log and ffs*.log files on the remote system. Contact IBM Software Support.
system.
CRRZI0394E Server initialization failed.
CRRZI0387E Data set compression has failed.
User response:
Problems creating the backup
For more information about this error, see the
data set. See the Error log for more
rsecomm.log and ffs*.log files on the remote
details.
system.
Explanation:
CRRZI0395E Migrate failed.
A request to compress a data set failed. An attempt to
back up the data set before compressing it failed. User response:
For more information about this error, see the
User response:
rsecomm.log and ffs*.log files on the remote
For more information about this error, see the
system.
rsecomm.log and ffs*.log files on the remote
system. CRRZI0396E Recall failed.
CRRZI0388E The data set compression has Explanation:
failed. See the Error log for more An HRECALL command failed.
details.
User response:
User response: For more information about this error, see the
For more information about this error, see the rsecomm.log and ffs*.log files on the remote
rsecomm.log and ffs*.log files on the remote system.
system.
CRRZI0397E Delete failed.
CRRZI0389E Copy command has failed.
Explanation:
User response: An HDelete operation for a migrated data set failed.
For more information about this error, see the
User response:
rsecomm.log and ffs*.log files on the remote
For more information about this error, see the
system.
rsecomm.log and ffs*.log files on the remote
CRRZI0390E Copy command has failed. system.
Problem in allocating SYSUT data
CRRZI0398E Server internal error. TSO server
set. See the Error log for more
cannot be located.
details.
Explanation:
Explanation:
The TSO command server did not start normally.
A copy command failed, because the request to
allocate the SYSUT data set failed. User response:
For more information about this error, see the
User response:
rsecomm.log and ffs*.log files on the remote
For more information about this error, see the
system. Collect the ffs*.log files and contact IBM
rsecomm.log and ffs*.log files on the remote
Software Support.
system.
CRRZI0399E Server internal error. Bad TSO
CRRZI0391E Copy command has failed. See the
server response {0}.
Error log for more details.
Explanation:
User response:
The TSO command server returned a bad response.
For more information about this error, see the
rsecomm.log and ffs*.log files on the remote User response:
system. Collect the fek*.log files and contact IBM Software
Support.

78 Developer for z/OS: Troubleshooting and Support

 0400-level messages
CRRZI0400E Server internal error. Command • 12: Cluster
target is not set. A severe internal error occurred while synchronizing
Explanation: the client and server.
An internal command that was sent by the client is User response:
incomplete. This message indicates an internal logic Collect the fek*.log files and contact IBM Software
error. Support.
User response: CRRZI0408E Server internal error. Exception
Collect the fek*.log files and contact IBM Software occurred.
Support.
Explanation:
CRRZI0401E Server internal error. Unsupported A severe internal error occurred.
command {0}.
User response:
Explanation: Collect the fek*.log files and contact IBM Software
File Manager Integration detected an unsupported Support.
command sent by the client.
CRRZI0410E Server internal error. Unknown
User response: target container type.
Contact IBM Software Support.
Explanation:
CRRZI0402E Server internal error. Undefined The target data set is not supported as a target data
message number {0}. set for a COPY or MOVE operation.
User response:
Explanation
Select the correct target data set for the COPY or
{0} MOVE operation.
An undefined message number.
CRRZI0411E Server internal error. Bad
A server internal error occurred, but the message ENQUEUE name {0}.
number is not defined in the resource file. This error
might be caused by an inconsistency between the
installed modules.
Explanation
{0}
User response:
An invalid ENQUEUE name.
Check that the installation finished correctly. If
completing the installation does not solve the An internal server error occurred.
problem, contact IBM Software Support. User response:
CRRZI0405E Server internal error. Bad resource Contact IBM Software Support.
type {0}. CRRZI0412E Failed to open file {0} in the editor.

Explanation Explanation
{0} {0}
The resource type is: File name.
• 1: Sequential data set An internal error occurred while the product was
• 2: Partitioned data set opening a file in an editor.
• 3: Migrated data set User response:
• 4: Offline data set No action is required.
• 5: Alias CRRZI0414W The build dependencies might
• 6: VSAM data set have changed since the last
syntax check. You might want to
• 7: Undefined recheck its dependencies before
• 8: Volume serial number proceeding with the syntax check.
• 9: PDS(E) Explanation:
• 10: Generation data group Copybook or include files changed since the last
syntax check.

Troubleshooting and support 79

User response: Explanation
Request the Check Dependencies action and then try
the operation again. {0}
Resource name
CRRZI0415W Check the dependencies before
{1}
proceeding with the syntax check.
Resource type
Explanation: An internal error occurred.
The product must gather information that pertains to
the copybooks or include files that are used by the User response:
source program. No action is required.
User response: CRRZI0420I The file {0} will be opened for read
Request the Check Dependencies action. only.
CRRZI0416W File type {0} is not a local file.
Explanation
Explanation {0}
File name
{0}
File type. A request was made to open a file, but the user is not
authorized to write to the file.
An internal error occurred when the product was
opening a remote resource. User response:
Obtain write access to file and try the operation again.
User response: If you cannot obtain write access, copy the file to a
No action is required. partitioned data set that you have write access to and
CRRZI0417E Could not retrieve an editable file edit the copied file.
for resource {0} of type {1}. CRRZI0421E Could not perform the refresh
dependencies operation.
Explanation Explanation:
{0} The job that was submitted to the remote system
Resource name failed.
{1} User response:
Resource type To determine whether the job completed or JCL errors
An internal error occurred. occurred, examine the job output under the JES
node in the Remote Systems view. If there are JCL
User response: errors, the entry fields in the compilation step of the
No action is required. Procedures and Steps page might point to data sets
CRRZI0418E Could not retrieve an editor object that do not exist. To verify that the specified data sets
for resource {0} of type {1}. exist, click Validate Data Sets.
CRRZI0422I For local syntax check to perform
Explanation correctly, make sure that all the
dependent libraries referenced by
{0} this file are also added to this
Resource name MVS subproject. You can use
{1} "Show Dependencies" to reveal
Resource type the dependent libraries, and then
An internal error occurred. add them to your MVS subproject.

User response: CRRZI0423E This operation cannot be

No action is required. performed because error feedback
is not supported when either
CRRZI0419E Could not retrieve a remote file for the Db2 precompiler or the CICS
resource {0} of type {1}. translator option is set.
Explanation:

80 Developer for z/OS: Troubleshooting and Support

The product relies on error feedback from the compiler An internal error occurred while the product was
to check syntax remotely. When error feedback is not opening a file in an editor.
available, a remote syntax check cannot be completed.
User response:
User response: No action is required.
Verify that the Db2 precompiler or the CICS translator
CRRZI0428E Could not retrieve a remote file for
options are required. If so, then remote syntax check
resource {0} of type {1}.
cannot be completed. If these procedures are not
required, then disable them on the Procedures and
Steps page of the property group that is associated Explanation
with the file for which you are trying to run a remote {0}
syntax check. Resource name
CRRZI0424E Could not perform the remote {1}
syntax check operation. Resource type
Explanation: An internal error occurred while the product was
The compilation job that was submitted to the remote opening a file in an editor.
system failed.
User response:
User response: No action is required.
To verify that the job completed successfully, look in
the job output under the JES node in the Remote CRRZI0429I The system default values have
Systems view. If there is a syntax error, verify been updated for system {0}. Do
that the entry fields in the compilation step on the you want to replace the previous
Procedure and Steps page are correct. To verify that defaults with the new ones?
the partitioned data sets that are specified exist, click Explanation:
Validate Data Sets. An administrator can configure site-specific defaults
CRRZI0425E Could not perform the show for particular properties in a property group. This
dependencies operation. message indicates that the default values were
changed for the remote system indicated by {0}.
Explanation:
The job that was submitted to the remote system User response:
failed. Click Yes to accept the updates or No to leave your
property groups unchanged.
User response:
Examine the job output to see whether the job CRRZI0430I The system property groups have
completed or JCL errors occurred. If JCL errors been updated for system {0}. Do
occurred, the entry fields in the compilation step of the you want to replace the ones that
Procedures and Steps page might point to data sets were already loaded?
that do not exist. To verify that the specified data sets Explanation:
exist, click Validate Data Sets. An administrator can set up predefined property
CRRZI0426E The property group associated groups for a remote system. These property groups
with this resource does not have are downloaded to your workspace when you connect
the "Support Error Feedback" to the remote system. This message indicates that the
option selected. Modify the system property groups were changed for the remote
property group and try again. system indicated by {0}.

CRRZI0427E Could not retrieve a z/OS UNIX User response:

System Services file for resource Click Yes to accept the updates or No to leave your
{0} of type {1}. property groups unchanged.
CRRZI0431W The file {0} already exists. Do you
Explanation want to overwrite it?

{0}
Resource name Explanation
{1} {0}
Resource type File name
User response:

Troubleshooting and support 81

Click Yes to overwrite the file or No to cancel the Explanation
operation.
{0}
CRRZI0432E '{0}' is not a valid local project File name
properties file. Make sure the file
An error occurred during an import of a property group
you are trying to import defines
file that was requested on the Import Property Group
properties for a local project.
window. The import file is not in the expected format.

Explanation CRRZI0436W Are you sure you want to delete

the overrides for this resource?
{0}
File name Explanation:
This message confirms a Property Group > Delete
An error occurred during an import of a local project Overrides request.
properties file that was requested on the Import
Property Group window. The import file is not in the User response:
expected format. Click Yes to delete the property group overrides
defined for the resource or No to cancel the request
Although project properties are stored in property and leave the overrides in place.
groups, the product still supports the local project
properties file for backward compatibility. CRRZI0437W Are you sure you want to delete
property group {0}?
CRRZI0433E '{0}' is not a valid MVS subproject
properties file. Make sure the file Explanation:
you are trying to import defines This message confirms a property group Delete
properties for an MVS subproject. request.
User response:
Explanation Click Yes to delete the property group or No to cancel
the request.
{0}
File name CRRZI0438E A property group exists with name
{0}. Change the name to a unique
An error occurred during an import of an MVS name.
subproject properties file that was requested on the
Import Property Group window. The import file is not Explanation:
in the expected format. An attempt was made to create a property group with
the same name as an existing property group
Although project properties are stored in property
groups, the product still supports the MVS subproject User response:
project properties file for backward compatibility. Specify a new name for the property group.

CRRZI0434E '{0}' is not a valid MVS Files CRRZI0439W The property file you are importing
subsystem properties file. Make is an old version. Property group
sure the file you are trying to {0} will be created to hold the
import defines properties for an values. Do you want to proceed?
MVS Files subsystem. Explanation:
The current product version uses property groups to
Explanation define the build properties for z/OS resources. The file
you are importing contains properties from an earlier
{0}
release. This message indicates that the properties are
File name
to be imported into a property group.
User response:
User response:
Select a different import file.
Click Yes to import the properties into a property
CRRZI0435E Unable to import properties from group or No to cancel the import request.
file '{0}'. Make sure the file you
CRRZI0440E The resource '{0}' does not have a
are trying to import is a valid .xml
property group associated with it.
or .properties file.
Choose an action and then try the
operation again:
Explanation:

82 Developer for z/OS: Troubleshooting and Support

You requested an operation that requires the resource 8.0 property group into a version 7.6 workspace. Later
to have a property group associated with it. No versions of clients are not compatible with earlier
property group is associated with the resource. versions.
User response:
User response Manually create a workspace or property group with
Choose one of the following options: the characteristics you want.
• To choose an existing property group to associate CRRZI0444W Some property groups cannot be
with the resource, click Associate an existing imported due to name conflicts.
property group. After making this selection and
Explanation:
associating the property group, try the operation
During a property group import operation that involves
again.
multiple property groups, some of the groups cannot
• To create a property group and associate it with the be imported because groups with the same names
resource, click Associate a new property group. exist. The groups that do not present name conflicts
After making this selection, creating a property are imported
group, and associating it with the resource, try the
operation again. User response:
No action is required.
• To cancel the operation, click Do not associate a
property group. CRRZI0445E Error reading from file {0}.

CRRZI0441E Could not open file {0}. Explanation:

In an attempt to import property groups from the file
Explanation: indicated by {0}, the import file cannot be read.
During a property group export operation, the target
export file, indicated by {0}, cannot be opened. User response:
Ensure that the file you specified is a valid property
User response: group .xml file. Try the operation again. If the error
Ensure that the file name specified is valid and that persists, contact your system administrator.
you have write access to the target location. Try the
operation again. If the error persists, contact your CRRZI0446E A duplicate category instance was
system administrator. detected in property group {0}. The
category of the instance is {1}.
CRRZI0442E Error writing to file {0}.
Explanation:
Explanation: A property group import file has more than one
During a property group export operation, the target instance of a property group category for the property
export file, indicated by {0}, cannot be written to. group indicated by {1}. The property group is not
User response: imported.
Ensure that the file name specified is valid and that User response:
you have write access to the target location. Try the Remove the duplicate category instance and try
operation again. If the error persists, contact your importing the property group again.
system administrator.
CRRZI0447E {0} is not a registered property.
CRRZI0443E {0} is not a registered category.
Explanation:
The .xml file that is being imported during a property
Explanation group import operation contains an invalid property
The .xml file that is being imported during a property name. The property group is not imported.
group or workspace import operation contains an
invalid category. The property group or workspace is User response:
not imported. The following sample messages show Correct the property name and try the import
examples of this error: operation again.

CRRZI0443E USE_LOCAL_PREPROCESSORS is not a

CRRZI0448W The system default values have
registered category. been updated for system {0}. Do
CRRZI0443E RUN_FOR_CODECOVERAGE is not a you want to replace the previous
registered category.
defaults with the new ones?
This error can occur when you try to import a property Explanation:
group or workspace from a later product version into An administrator can configure site-specific defaults
an earlier version, for example, importing a version for particular properties in a property group. This

Troubleshooting and support 83

message indicates that the default values were A remote resource cannot be deleted if it is locked by
changed for the remote system indicated by {0}. another user or program.
User response: User response:
Click Yes to accept the updates or No to leave your To determine the lock owner of a remote resource,
property groups unchanged. open the properties view and expand the Info category
to see the Lock owner property.
CRRZI0449W The system property groups have
been updated for system {0}. Do CRRZI0456E Local project names are case
you want to replace the ones you insensitive. There is an existing
previously loaded? project that conflicts with '{0}'.
Choose another name for the
Explanation:
project.
An administrator can set up predefined property
groups for a remote system. These property groups Explanation:
are downloaded to your workspace when you connect A name specified for a new local project exists in
to the remote system. This message indicates that the the workspace. Because names are not case-sensitive,
system property groups were changed for the remote the names "MyNewProject" and "Mynewproject", for
system indicated by {0}. example, conflict.
User response: User response:
Click Yes to accept the updates or No to leave your Choose a unique name for the project.
property groups unchanged.
CRRZI0457E An internal error occurred during
CRRZI0450E The check dependencies operation creation of local project '{0}'.
could not be performed. See Contact your IBM technical
details for more information. support representative.
Explanation: Explanation:
A Check Dependencies request was made, but could An internal error occurred during creation of local
not be completed. project '{0}'.
User response: User response:
For more information about the errors that occurred Contact IBM Software Support.
during this operation, click Details.
CRRZI0458I The JCL was submitted to remote
CRRZI0451E Copying a partitioned data set or system '{1}' and the Job ID is '{0}'.
folder is not supported. Click Locate Job to locate the job
in the Remote Systems view.
Explanation:
This message displays in response to an attempt to Explanation:
copy a folder or a partitioned data set into an MVS During execution of the DCLGEN utility wizard,
subproject by dragging it. the client generates and submits JCL to generate
copybooks, include files, macros, and C/C++ header
User response files from database table information by using the Db2
utility DCLGEN. This message indicates that the job
To copy the contents from a source folder or
was submitted.
partitioned data set into an MVS subproject:
1. Create a partitioned data set in the MVS subproject.
User response
2. Copy the members from the source folder or To check the job output, do these steps:
partitioned data set.
1. In the Remote Systems view, locate the remote
3. Paste the members into the new partitioned data system on which the Db2 table you are working
set. with is located.
CRRZI0452E Resource '{0}' is locked and cannot 2. Expand the remote system connection and then
be deleted. Another person or expand JES > My Jobs.
program might be using the 3. Look for the job name indicated in the message and
resource. Try the operation again expand it to see the job output.
when the resource is available.
CRRZI0459E The job has not been submitted
Explanation:
because the Job Monitor server
is not connected. Contact your

84 Developer for z/OS: Troubleshooting and Support

 System Administrator to start Explanation
the Job Monitor server. After
the server is started, you may Attention: The work offline and work
resubmit the job. online operations for a remote resource are
deprecated.
Explanation:
The Job Monitor server must be started before jobs {0}
can be submitted. File name
{1}
User response:
Location of file
Contact your system administrator to start the Job
Monitor server A work online operation found a file with the same
name, but without the file extension, in the current
CRRZI0460E A problem occurred while creating
folder.
or saving the properties. See the
log for further information. User response:
Make sure that the file names in the folder are unique
Explanation:
with or without the extensions. Specify a new unique
During an export properties operation, the export file
name for the files in the folder.
cannot be created or saved.
CRRZI0464E Invalid MVS name. A member
User response:
name cannot be more than 8
To open the log file, open
characters. Return to the offline
workspace/.metadata/.log on your workstation
project, rename the member, and
file system.
try the operation again.
CRRZI0461E No connection is defined for '{0}'.
Define a connection and import Explanation
the project again.
Attention: The work offline and work
Explanation: online operations for a remote resource are
To import a remote z/OS project, you must be deprecated.
connected to the remote system that contains the
project resources. During a work online upload operation, an invalid MVS
name was found. Member names cannot be more than
eight characters.
User response
User response:
1. Define a connection to the remote system indicated
Correct any member names that do not confirm to data
by {0}.
set member naming rules and try the operation again.
2. Connect to the remote system.
CRRZI0465E Invalid MVS name. The member
3. Try to import the project again. name must not have a period.
CRRZI0462E The project to be imported is Return to the offline project,
named '{0}'. There is a project in rename the member, and try the
the workspace with this name. operation again.
Specify a unique name for the new
project and try again. Explanation
Explanation: Attention: The work offline and work
During a project import operation, an existing project online operations for a remote resource are
with the same name was found in the workspace. deprecated.
Projects must have unique names.
During a work online upload operation, an invalid MVS
User response: name was found. The member name must not have a
Specify a new name for the project. period.
CRRZI0463E A file with the name '{0}' already User response:
exists in '{1}'. Make sure all Correct any member names that do not confirm to data
the files have a unique name set member naming rules and try the operation again.
(excluding extension) and try
again. CRRZI0466E Invalid MVS name. Each segment
of a data set name can have no
more than 8 characters. Return

Troubleshooting and support 85

 to the offline project, rename the A team provider plug-in can add properties to
member, and try the operation resources by registering its own properties provider.
again. The message indicates that the registration failed
because the specified resource does not support
Explanation:
properties.
When a project is offline, you can rename data sets or
add new data sets to it. This message indicates that a User response:
new or renamed data set does not conform to data set Contact IBM Software Support.
naming rules.
CRRZI0470I z/OS UNIX Files and Shells are
User response: hidden by the server setting.
Be sure that any new or renamed data sets use no
Explanation:
more than 8 characters in each segment of the data
A setting on the remote system is causing z/OS UNIX
set name. Correct any data set names that do not
Files and Shells to be hidden on the client user
conform to data set naming rules and try the operation
interface.
again.
User response:
CRRZI0467W {0} has the following encoding
If you believe this setting is incorrect, contact your
mismatch:
systems administrator.

Explanation CRRZI0471E While synchronizing changes

resulting from a request to rename
Attention: The work offline and work a shared folder from {1} to {2}, the
online operations for a remote resource are rename operation for the sandbox
deprecated. resource {0} failed. The sandbox
resource will be unloaded from
{0}
the z/OS project. Resolve the error
The item that contains an encoding mismatch
described below and reload the
The work online upload operation checks for any shared resource to the project.
encoding mismatch between a local resource and
the corresponding remote resource. If encoding for
SO/SI is specified for a local resource, the operation
Explanation
compares it to the host encoding of the remote {0}
resource. If the encodings do not match, the user is Resource name
asked to override the host encoding with the SO/SI {1}
encoding or cancel the operation. Folder name
User response: {2}
The encoding mismatch must be resolved. To change Folder name
the host code page of the remote resource to the
SO/SI encoding of the local resource, click Yes. To CRRZI0472E While synchronizing changes
leave the host code page of the remote resource resulting from a request to delete
unchanged and cancel the operation, click No. the shared resource {1}, the delete
operation for sandbox resource {0}
CRRZI0468E Another properties provider is failed. The sandbox resource will
registered for the resource. be disconnected. Resolve the error
Explanation: described below or the sandbox
A team provider plug-in can add properties to might not be available for use.
resources by registering its own properties provider.
The message indicates that the registration failed Explanation
because another properties provider is already
{0}
registered.
Resource name
User response: {1}
Contact IBM Software Support. Resource name
CRRZI0469E The object does not have CRRZI0473E While synchronizing changes
properties. resulting from a request to rename
Explanation: a shared resource from {1} to
{2}, the rename operation for the

86 Developer for z/OS: Troubleshooting and Support

 sandbox resource {0} failed. The This message displays in response to a drag operation
sandbox resource will be unloaded on a Procedures and Steps page of the property group
from the z/OS project. Resolve the editor. It indicates that an object other than a data set
error described below and reload was dragged to the field.
the shared resource to the project.
User response:
Drag a data set name into the field.
Explanation
CRRZI0478E This text field specifies one data
{0} set name. Drag and drop one data
Resource name set onto this text field.
{1} Explanation:
Resource name This message displays in response to a drag operation
{2} on a Procedures and Steps page of the property group
Resource name editor. It indicates that the field to which a data set
name was dragged can contain only one data set
CRRZI0474E While synchronizing changes
name.
resulting from a request to update
Failed to update the shared User response:
resource {1}, the update operation To replace the data set name already in the field, clear
for the sandbox resource {0} the filed and then drag another name to the field.
failed. The sandbox resource
CRRZI0479W The length of the data set name
will be unloaded from the
might exceed the maximum of
z/OS project. Resolve the error
44 characters, depending on the
described below and reload the
length of the high-level qualifier.
shared resource to the project.
Explanation:
Data set names in the fields on the Procedures and
Explanation
Steps page of the property group editor are limited to
{0} 44 characters. This warning indicates that the current
Resource name data set name is nearing this limit and might exceed it
{1} if the high-level qualifier is too long.
Resource name User response:
CRRZI0475E The data set {0} does not exist. Check the length of the high-level qualifier to ensure
that it does not result in a data set name that exceeds
Explanation: the maximum length.
This message displays in response to a Check Data
Sets request on a Procedures and Steps page of the CRRZI0480E The system {0} is not connected.
property group editor. It indicates that the data set Connect to the system and try
name specified does not exist. again.

User response:
Specify another data set name and try again. Explanation
CRRZI0476E The data set {0} is already {0}
specified in the text field. The name of a remote system.
Data set validation for a property group requires a
Explanation:
connection to a remote system.
This message displays in response to a Check Data
Sets request on a Procedures and Steps page of the
property group editor. It indicates that the data set User response
name specified was already added to the field. Connect to the remote system and try the operation
again. To connect to the remote system:
User response:
Specify another data set name and try again. 1. On the Information page of the property group
editor, identify the system that the property group
CRRZI0477E Invalid source {0} for this text
belongs to.
field. Drag and drop a valid data
set onto this text field. 2. To connect to the system, locate the system in
the Remote Systems view, right click, and select
Explanation: Connect.

Troubleshooting and support 87

CRRZI0481E There is no name for the property code pages, however, it is not possible to preserve
group. round-trip integrity of certain characters. This message
warns that the file under edit contains characters
Explanation:
whose round-trip integrity cannot be preserved.
During a property group create operation, the property
group name was found to be missing. User response:
To save the file with corrupted characters, click Yes. To
User response: close the file without saving your changes, click No.
Specify a name for the property group on the Property
Group Information page and try saving the property CRRZI0487E File '{0}' contains characters that
group again. cannot be transferred correctly
between the local and remote
CRRZI0483E While synchronizing changes to systems. These characters will
the sandbox resource {1}, a delete be highlighted. The file will be
operation for the shared resource opened in read-only mode.
{0} failed. The resource is not
synchronized. Resolve the error Explanation:
described below and share the The editors are able to preserve the integrity of
sandbox or reload the shared characters as they are transferred from the remote
resource. system to the workstation and back again. For some
code pages, however, it is not possible to preserve
round-trip integrity of certain characters. This message
Explanation
warns that the file under edit contains characters
{0} whose round-trip integrity cannot be preserved. One
Resource name cause of this message can be the definition of an
{1} inappropriate alternative logical NOT symbol. Because
Resource name the file is being edited from the remote system, it is
opened in read-only mode.
CRRZI0484E While synchronizing changes
resulting from a request to rename User response:
the sandbox from {1} to {2}, the To edit the file, copy it to a local project in your
rename operation for the shared workspace and change the corrupted characters
resource {0} failed. The resource before you copy it to the remote system. For
is not synchronized. Resolve the instructions for setting an alternative logical NOT
error described below and share symbol, see the related topics.
the sandbox or reload the shared CRRZI0489E An attempt to move the logical
resource. resource '{0}' to '{1}' has failed.

Explanation Explanation
{0} An error occurred while a remote resource was being
Resource name shared with a team provider and creating a local copy
of the resource.
{1}
Sandbox name {0}
Resource name
{2}
Sandbox name {1}
Resource name
CRRZI0485E The editor contains characters
that cannot be transferred User response:
correctly between the local and For details about this error, see the .log file in
remote systems. Saving the file the .metadata folder of the current workspace.
on the remote system will cause CRRZI0490E The logical resource '{0}' is not a
these characters to become subproject.
corrupted. Do you want to
continue?
Explanation
Explanation: When you load a team resource into the remote file
The editors are able to preserve the integrity of system, the remote resource must be added to a
characters as they are transferred from the remote
system to the workstation and back again. For some

88 Developer for z/OS: Troubleshooting and Support

subproject. A subproject was not specified by the team CRRZI0494E The local sandbox path '{0}'
provider application. specified for the team resource
{0} '{1}' is invalid.
Resource name
User response:
Explanation
Contact your systems administrator. When you share a remote resource with a team
provider, a local copy of the remote resource
CRRZI0491E The remote sandbox file path is downloaded to the client. The team provider
name '{0}' is not found on the application specified an invalid local destination.
system '{1}'.
{0}
Path name
Explanation {1}
When you load a team resource into the remote file Resource name
system, a local copy of the remote resource is also
downloaded to the client. The remote resource was User response:
not found. Contact your systems administrator.
{0} CRRZI0495E The resource '{0}' is already
Path name registered with a team provider.
{1} Registering a resource with
System name multiple team providers is not
allowed.
User response:
Contact your systems administrator.
Explanation
CRRZI0492E There are no systems found for the
{0}
logical subproject '{0}'.
Resource name

Explanation User response:

When you load a team resource into the remote file No response is required.
system, the remote system is inferred from the target CRRZI0496E The resource '{0}' is already
subproject. No remote system was associated with the shared with a team provider.
subproject. Sharing a resource with multiple
{0} team providers is not allowed.
Subproject name
User response:
Explanation
Contact your systems administrator. {0}
Resource name
CRRZI0493E An attempt to load resource '{0}' to
the subproject '{1}' has failed. User response:
No response is required.
Explanation CRRZI0497E The resource '{0}' is not shared
When you load a team resource into the remote with a team provider. The
file system, the remote resource must be added to disconnect operation can be
a subproject. An error occurred when the remote performed only on a shared
resource was added to the subproject. resource.
{0}
Resource name Explanation
{1} {0}
Subproject name Resource name
User response: User response:
For details about this error, see the .log file in No response is required.
the .metadata folder of the current workspace.
CRRZI0498E The sandbox prefix was specified
for '{0}', but the remote sandbox
file name is required. Specify the

Troubleshooting and support 89

 remote sandbox file name and try CRRZI0499I Data set validation is complete. All
the operation again. validated data sets exist.
Explanation:
Explanation This message displays in response to a Check Data
{0} Sets request on a Procedures and Steps page of the
Sandbox prefix property group editor. It indicates that the data set
names specified are valid.
During a resource check-in operation, a sandbox prefix
was provided when the remote sandbox file name was User response:
expected. No response is required.

User response:
Try the operation again. Specify the remote sandbox
file name.

0500-level messages
CRRZI0500W Data set validation is complete. not exist so that it can be allocated with the same
One or more data set names characteristics as the source data set.
contain the variable <HLQ> and CRRZI0503E Member {0} already exists.
these data sets cannot be
validated.
Explanation
Explanation:
This message displays in response to a Check Data {0}
Sets request on a Procedures and Steps page of Member name
the property group editor. It indicates that the data The target of the copy or rename operation exists but
set names specified cannot be validated because they the option to replace an existing data set was not
contain the <HLQ> variable. The data set names might specified.
or might not be valid.
User response:
User response: Try the operation again and either choose a different
No response is required. target name or specify the replace option.
CRRZI0501E Data set {0} already exists. CRRZI0504I The closed project {0} contained
one or more shared resources.
Explanation They have been unloaded. You will
need to reload them when you
{0} reopen the project later.
The name of a data set.
The target of the copy or rename operation exists, Explanation
but the option to replace an existing data set was not
specified. {0}
Project name
User response:
Try the operation again and either choose a different User response:
target name or specify the replace option. No action is required.

CRRZI0502E Data set {0} has conflicting CRRZI0505E Overrides are being edited for
attributes. property group '{0}'. Close the edit
session for the overrides before
editing the property group.
Explanation
Explanation:
{0}
During a property group edit operation, for the
The name of a data set.
property group indicated by {0}, the property group
A target data set was found, but its characteristics do was found to be open for a property group override
not match the characteristics of the source data set. request. You cannot edit a property group while it is
open for overrides.
User response:
Specify a different source or target data set so that User response:
the characteristics match or specify a target that does

90 Developer for z/OS: Troubleshooting and Support

Close the Property Group Editor and then try the edit Explanation
operation again.
{0}
CRRZI0506E The property group '{0}' is being Resource name
edited. Close the edit session
for the property group before CRRZI0510W The data set '{0}' contains
attempting to override it. {1} members. Working with a
large number of members in a
Explanation: subproject might take a long
During a property group override operation for the time. To improve performance,
property group indicated by {0}, the property group add only required members to
was found to be open for a property group edit the subproject. Do you want to
request. You cannot override a property group while proceed?
it is open for edit.
Explanation:
User response: The number of members in the partitioned data
Close the Property Group Editor and then try the set exceeds the warning threshold set in the MVS
override operation again. Files preference page. This message gives you
CRRZI0507E Possible reason for failure: An an opportunity to cancel the request to add the
invalid CICS Debug profile server partitioned data set to the subproject.
port ({0}) is being used for the
CICS region {1}. Contact the User response
administrator for the valid port
• To continue adding the partitioned data set to the
and update the port in the CICS
subproject, click Yes.
Debug Configuration preference
page. • To cancel the request, click No.
Explanation: • To disable the warning, open the MVS Files
An attempt to create a CICS debug configuration preference page and clear the Show warning
failed. A possible reason for the failure is an invalid message on adding to subproject check box.
CICS Debug profile server port number specified on • To change the warning threshold, open the MVS
the CICS Debug Configuration preference page. Files preference page and specify a different number
in the Maximum number of members added to
User response:
subproject without warning field.
Contact your system administrator to obtain the
correct CICS Debug profile server port number. Specify CRRZI0511E CICS region ({0}) does not exist.
the port number on the CICS Debug Configuration Make sure the appropriate CICS
preference page and then try to create the debug connection is connected.
configuration again.
Explanation:
CRRZI0508I Specify the CICS Debug profile The region specified on the CICS page of the Debug
server port for the CICS region {0}. Configurations > Remote CICS Application wizard
Explanation: does not exist.
An attempt was made to create a debug configuration, User response:
but there is no CICS Debug profile server port On the CICS page of the Debug Configurations >
associated with the CICS region. Remote CICS Application wizard, click the Define
User response: CICS Connection link to open the CICS Explorer
Contact your system administrator to obtain the > Connections preference page. Use this page to
correct CICS Debug profile server port number. Specify connect to a CICS region and then try again to define
the port number on the CICS Debug Configuration the CICS debug configuration.
preference page and then try to create the debug CRRZI0512W The size of file '{0}' is {1}
configuration again. KB, which exceeds the threshold
CRRZI0509E The remote sandbox resource {0} defined in the z/OS Solutions
has been updated by another preferences. Opening large files
person or program. Resolve the can cause out-of-memory errors
conflict and then try the operation leading to a forced shutdown of
again. the workbench. Do you want to
continue or open the member in
the z Systems® Data Editor?

Troubleshooting and support 91

Explanation: remote systems. This file will be
The preferences provide a warning threshold for opened in read-only mode. Do you
opening large files. This warning helps to prevent out- want to continue?
of-memory errors.
Explanation:
The editors are able to preserve the integrity of
User response characters as they are transferred from the remote
system to the workstation and back again. For some
• To continue opening the file click Continue.
code pages, however, it is not possible to preserve
• To open the file by using the z Systems Data Editor, round-trip integrity of certain characters. This message
which is better able to handle large data files, click warns that the file under edit contains characters
Use z Systems Data Editor. whose round-trip integrity cannot be preserved.
• To cancel the file open operation, click Cancel. User response:
• To disable the warning, open the z/OS Solutions To open the file in the comparison editor, click Yes. To
preference page and clear the Show warning cancel the file comparison request, click No.
message on opening files checkbox.
CRRZI0516W Both files contain characters that
• To change the file size threshold for the warning, cannot be transferred correctly
specify a new value in the Maximum file size to between the local and remote
open without warning (in KB) field. systems. The files will be opened
CRRZI0513W Some categories will not be in read-only mode. Do you want to
imported because this version of continue?
the client does not support them. Explanation:
Explanation: The editors are able to preserve the integrity of
The property group that is being imported contains characters as they are transferred from the remote
property group categories that are not supported by system to the workstation and back again. For some
the current version. The supported categories are code pages, however, it is not possible to preserve
imported and the unsupported categories are ignored. round-trip integrity of certain characters. This message
warns that the files under edit contain characters
User response: whose round-trip integrity cannot be preserved.
No response is required.
User response:
CRRZI0514E The operation did not complete To open the files in the comparison editor, click Yes. To
successfully. Verify that the JCL cancel the file comparison request, click No.
procedure on the remote system
has the error feedback compiler CRRZI0518W A decoding error occurred while
options configured correctly to fetching the keymapping file. The
support this operation. system will be processed as
though there were no keymapping
Explanation: file.
The operation requires the error feedback compilation
option to be specified. Explanation:
While attempting to export configuration files, the
client encountered problems with the keymapping.xml
User response file and cannot update the file. A new keymapping.xml
Enable the error feedback option and try the operation file is generated and uploaded to the remote system.
again. To enable the error feedback option:
User response:
1. Edit the property group associated with the No action is required. The new key mapping file
resource. contains settings for only the configuration files
2. Select the category appropriate for the resource included in the current export request.
type: Assembler, COBOL, or PL/I. CRRZI0519I There are no connected remote
3. In the Procedure and Step Table, click a step systems with the push-to-client
name to display the step options. function enabled. Connect to a
4. Select the Support Error Feedback check box. remote system with the push-to-
client function enabled and try
CRRZI0515W The file '{0}' contains characters again.
that cannot be transferred
correctly between the local and Explanation:

92 Developer for z/OS: Troubleshooting and Support

You requested to export configuration files, but none You attempted to copy a partitioned data set member
of the remote systems to which you are connected are that is an alias. The copy operation cannot be
enabled for push-to-client. completed because alias processing is disabled.
User response: User response:
Connect to a remote system that has the push-to- To enable alias processing, navigate to the Remote
client function enabled and try again. Contact your Systems > z/OS > MVS Files preference page, and
system administrator if you do not know which remote select the Process member aliases on module copy
systems are enabled for push-to-client. option. For more information about enabling alias
processing, see MVS Files.
CRRZI0521E The error feedback file cannot
be parsed because its format or CRRZI0524E The member {0} is the alias of {1},
content is invalid or incomplete. which does not exist. Copying an
Check the build properties alias without copying its primary is
and view the job output for not supported.
unrecoverable errors.
Explanation:
Explanation: You attempted to copy a partitioned data set member
The file specified in the Error Feedback XML File that is an alias. The copy operation cannot be
Name field of the Local Preprocessor page of the completed because the primary member does not
current property group contains formatting or content exist.
errors.
User response:
For more information about copying data set aliases,
User response see Copying load modules. For more information about
enabling alias processing, see MVS Files.
• Open the property group in the Property Group
Editor and verify that the Error Feedback XML File CRRZI0525E The member {0} is an alias or
Name field refers to the correct file. has one or more aliases. The copy
• To view the job output, expand the JES subsystem in target cannot be the same as the
the Remote Systems view and look for the job name. copy source.

CRRZI0522W The server has been configured to Explanation:

automatically download product You attempted to copy a partitioned data set member
updates to the client when you that is an alias or has an alias defined. The copy
connect to the remote system. operation cannot be completed because the copy
Current® Product Version shows source and the copy target are the same.
the product version currently User response:
installed on your workstation. A Try the copy operation again and specify a different
new version will be installed when target. For more information about copying data set
you click OK. aliases, see Copying load modules.
Explanation: CRRZI0526E IEBCOPY has failed. See {0} for
The remote system to which you are connecting is more details.
configured to automatically install product updates
when you connect to it. Product updates are available
for installation.
Explanation
{0}
User response:
The log file name.
Click OK to install the product updates. Your
workbench is shut down and IBM Installation Manager The copy command failed because the request to
is started to install the product updates. Restart the allocate a data set before the IEBCOPY command
client when the product installation is complete. failed.
CRRZI0523E The member {0} is the alias User response:
of {1}. Support for copying For more information about this error, see the
aliases has been disabled in the rsecomm.log and ffs*.log files on the remote
preference settings. Copying an system.
alias without copying its primary is CRRZI0527W Both files use an encoding that
not supported. permits bidirectional characters.
Explanation: The files will be opened in read-

Troubleshooting and support 93

 only mode. Do you want to a different primary system than the one to which you
continue? exported previously.
Explanation:
The comparison editor does not support edit of User response
bidirectional file content. If you intend to export to a different primary system,
no action is required. You can continue with the export
User response:
action.
To open the files in the comparison editor, click Yes. To
cancel the file comparison request, click No. If you did not intend to export to a different system:
CRRZI0528W The file '{0}' uses an encoding that 1. Cancel the current export action.
permits DBCS characters. The file 2. Disconnect from primary system {1}.
will be opened in read-only mode.
Do you want to continue? 3. Connect to primary system {0}.
4. Try the export action again.
Explanation:
The comparison editor does not support edit of CRRZI0533I Two or more primary systems are
double-byte character set (DBCS) file content. connected. Only one connection
to a primary system is allowed.
User response:
Disconnect from all but one
To open the file in the comparison editor, click Yes. To
primary system.
cancel the file comparison request, click No.
Explanation:
CRRZI0529W Both files use an encoding that
You are connected to two or more remote systems that
permits DBCS characters. The files
are defined as the primary system in a push-to-client
will be opened in read-only mode.
environment. The push-to-client feature allows only
Do you want to continue?
one connection to a primary remote system.
Explanation:
User response:
The comparison editor does not support edit of
Disconnect from all but one primary remote system.
double-byte character set (DBCS) file content.
Contact your system administrator if you do not know
User response: which remote systems are primary.
To open the files in the comparison editor, click Yes. To
CRRZI0534E Insufficient permission to the
cancel the file comparison request, click No.
directory {0} when exporting {1}.
CRRZI0530W The file '{0}' uses an encoding that
Explanation:
permits bidirectional characters.
An attempt to export a configuration file to a remote
The file will be opened in read-
system failed. Your user ID does not have the correct
only mode. Do you want to
file permissions to write to the parent directory.
continue?
To export system or global configuration settings to
Explanation: the remote system, you must have write access to
The comparison editor does not support edit of the push-to-client configuration directories on the
bidirectional file content. remote system. File permissions for the push-to-client
directory on the remote system are set by using the
User response:
file.permission directive in the pushtoclient.properties
To open the file in the comparison editor, click Yes. To
file.
cancel the file comparison request, click No.
User response:
CRRZI0532I You are requesting to export
For more information about push-to-client file
to primary system {1}. Primary
permissions and configuring push-to-client support
system {0} was used last to export
on z/OS, see Basic customization in the Host
the configuration files. Verify that
Configuration Guide (SC23-7658).
{1} is the correct primary system.
CRRZI0535I There are no changes between the
Explanation:
workstation copy and the remote
You are currently connected to primary system {1} and
copy.
initiated an export configuration files action. The last
time you requested this action, you were connected Explanation:
to primary system {0}. This message is a reminder to This message displays in response to a Team >
verify that you intend to export configuration files to Synchronize with remote request. It indicates that
the local and remote resources are synchronized.

94 Developer for z/OS: Troubleshooting and Support

User response: Synchronizing the local project with the remote system
No response is required. results in overwriting changes that were made on the
remote system.
CRRZI0536E Errors occurred moving changed
files User response:
Click Yes to continue and overwrite the remote
Explanation:
changes or No to cancel the request.
This message displays in response to a Team >
Synchronize with remote request. It indicates that CRRZI0541E Error copying {0} to the local
an error occurred while synchronizing the local and workspace
remote files.
Explanation:
User response: An inbound change cannot be copied to the local
Contact your system administrator. project in the synchronize perspective.
CRRZI0537E No remote systems are defined. User response:
Cancel this action, define a remote Contact your system administrator.
system, and try the operation
CRRZI0542E Error copying {0} to the remote
again.
system
Explanation:
Explanation:
This message displays in response to a Team >
An outbound change cannot be copied to the remote
Synchronize with remote request. It indicates that no
system in the synchronize perspective.
remote system is defined.
User response:
User response:
Contact your system administrator.
Define a connection to a remote system, connect to
the system, and try the operation again. CRRZI0543W The chosen remote system
location differs from the project's
CRRZI0538E Could not mark {0} as merged
target remote system. Do you
Explanation: want to change the project's
A Mark as Merged request in the Synchronize target remote system to match the
perspective failed. chosen remote system location?
User response: Explanation:
Contact your system administrator. The remote system specified in the Pushable
Manifest Editor differs from the remote system
CRRZI0539E You must be connected to the
associated with the local project.
remote system and have at least
one filter defined to use the <HLQ> User response:
variable. To change the remote system associated with the
local project, click Yes. To leave the remote system
Explanation associated with the project unchanged, click No.
CRRZI0544W The extension is already in the
Attention: The push-to-host (remote
mapping.
synchronization) function is deprecated.
Explanation:
For some operations, such as Enable Remote
A local file extension specified in the Pushable
Synchronization, you can type the <HLQ> variable in
Manifest Editor is already added to the mapping.
the high-level qualifier field of the user interface. Use
of this variable requires a connection to a remote User response:
system for the variable to be correctly substituted. Specify a different file extension.
User response: CRRZI0545W You are going to overwrite changes
Connect to a remote system and try the operation that have been made in the
again. local workspace. Update the
workspace?
CRRZI0540E You are going to overwrite changes
that have been made on the Explanation:
remote system. Commit these Synchronizing the local project with the remote system
changes? results in overwriting changes that were made on the
local system.
Explanation:
User response:

Troubleshooting and support 95

Click Yes to continue and overwrite the local changes Explanation
or No to cancel the request.
Attention: The remote synchronization function
CRRZI0546E Failed to connect to {0}. is deprecated.
CRRZI0550E Failure to retrieve member
Explanation contents {0}.
Attention: The remote synchronization function
is deprecated. Explanation
During a remote synchronization operation, the Attention: The remote synchronization function
product could not connect to the remote system. is deprecated.
{0}
CRRZI0551E Contents cannot be set on {0}.
The name of a remote system.
User response: Explanation
Ensure that the remote system connection is defined
in the Remote Systems view and that the connection Attention: The remote synchronization function
properties are defined correctly. Contact your systems is deprecated.
administrator for the correct connection properties.
CRRZI0552E Failure to write member contents.
CRRZI0547E Could not find {0} on {1}.
Explanation
Explanation
Attention: The remote synchronization function
Attention: The push-to-host (remote is deprecated.
synchronization) function is deprecated.
CRRZI0553E Failed to connect to {0}.
A request was made to copy a local resource to the
remote system by using the push-to-host Remote
Explanation
> Copy to Remote or Remote > Synchronize with
Remote operation. The target data set was not found Attention: The remote synchronization function
on the remote system. is deprecated.
{0} CRRZI0554E Could not find {0} on {1}.
The name of a remote data set.
{1} Explanation
The name of a remote system.
Attention: The remote synchronization function
User response: is deprecated.
You must allocate the target remote data set before
you can copy a local resource to it. Allocate the data CRRZI0555E Contents cannot be retrieved from
set on the remote system. Ensure that the remote {0}.
data set name and the remote system are specified
correctly in the remote mapping. Try the operation Explanation
again.
Attention: The remote synchronization function
CRRZI0548E Failure to retrieve modification is deprecated.
stamp.
CRRZI0556E Contents cannot be set on {0}.
Explanation
Explanation
Attention: The remote synchronization function
is deprecated. Attention: The remote synchronization function
is deprecated.
CRRZI0549E Contents cannot be retrieved from
{0}. CRRZI0557E Could not access properties.

Explanation
Attention: The remote synchronization function
is deprecated.

96 Developer for z/OS: Troubleshooting and Support

CRRZI0558E Syntax check not successful. An error occurred while a mapping for remote
synchronization was being created. The local resource
that is specified in a mapping does not exist.
Explanation
User response:
Attention: The remote synchronization function
Either create the local resource or clear the mapping
is deprecated.
from the editor.
CRRZI0559W Some project resources are not CRRZI0564E Unrecognized remote resource
synchronized. Do you want to stop type {0}.
the syntax check and open the
Team Synchronizing perspective?
Explanation
Explanation Attention: The remote synchronization function
is deprecated.
Attention: The remote synchronization function
is deprecated. An error occurred while a mapping for remote
synchronization was being created. The remote
CRRZI0560E Invalid Format. Expected a path, resource type is incorrect for a mapping. Valid
but found {0}. resource types are MVS and z/OS UNIX System
Explanation: Services.
A file referenced in the .RemoteMapping pushable User response:
manifest editor file is in an unsupported format. A non- Open the Pushable Manifest Editor and set a valid
path item was found when a path was expected. remote resource type, or clear the mapping for that
User response: item.
Open the .RemoteMapping file in a text editor and CRRZI0565E Unspecified remote resource type.
correct the line in error.
CRRZI0561E The specified remote system {0} is Explanation
unknown.
Attention: The remote synchronization function
Explanation: is deprecated.
A remote system referenced in the .RemoteMapping
pushable manifest editor file is unknown. An error occurred while a mapping for remote
synchronization was being created. The remote
User response: resource type is missing.
Open the Pushable Manifest Editor and specify a valid
remote system location. User response:
Open the Pushable Manifest Editor and specify a
CRRZI0562E A remote system must be remote resource type, or clear the remote location.
specified.
CRRZI0566E The same remote resource is
specified multiple times.
Explanation
Attention: The remote synchronization function Explanation
is deprecated.
Attention: The remote synchronization function
An error occurred while a mapping for remote is deprecated.
synchronization was being created. The remote system
name is missing. An error occurred while a mapping for remote
synchronization was being created. More than one
User response: local resource is mapped to the same remote
Open the Pushable Manifest Editor and specify a valid resource.
remote system location.
User response:
CRRZI0563E The local resource does not exist. Open the Pushable Manifest Editor and specify a
different remote resource for each local resource, or
Explanation remove duplicate entries from the manifest.

Attention: The remote synchronization function CRRZI0567E Unrecognized remote resource

is deprecated. location.

Troubleshooting and support 97

Explanation Explanation
Attention: The remote synchronization function {0}
is deprecated. The name of the feature that is being imported.
An error occurred while a mapping for remote During an import operation, a feature was found to
synchronization was being created. The remote exist.
resource that is specified in a mapping cannot be User response:
found. To replace the feature, click Yes. To cancel the import
User response: operation, click No.
Open the Pushable Manifest Editor and set a valid CRRZI0573E Not a valid COBOL comment.
remote resource location, or allocate the remote data
set that is specified in the mapping. Explanation:
While a COBOL code template was being edited, an
CRRZI0568E Could not determine if the project invalid COBOL comment was provided.
is pushable: {0}
User response:
Type a valid COBOL comment and save the template.
Explanation
CRRZI0574E Missing required variable '{0}'.
Attention: The remote synchronization function
is deprecated.
Explanation
CRRZI0569W This action removes all COBOL
feature customization and returns {0}
to the product defaults. Are you The name of the missing variable.
sure? While a code template was being edited, a required
variable was omitted.
Explanation:
This message prompts you to confirm a Restore User response:
Defaults action on the Features preference page for Type a variable or select one by clicking Insert
COBOL. Variable.
User response: CRRZI0575W Unrecognized or illegal variable
Click OK to remove all COBOL feature customization or '{0}'.
Cancel to cancel the restore defaults request.
CRRZI0570W This action deletes the selected Explanation
feature(s). Are you sure?
{0}
Explanation: The name of a variable that is not recognized or is
This message prompts you to confirm a delete action invalid in the template.
on the Features preference page for COBOL. While a code template was being edited, one of the
User response: following situations occurred:
Click Yes to delete the feature or No to cancel the • A variable was used that is not predefined.
delete request.
• The predefined variable that was used is not valid for
CRRZI0571W The file already exists. Do you the template.
want to replace it?
User response:
Explanation: Use a different variable and save the changes to the
A request was made to export the customizable template.
features for COBOL programs to an XML, but the file
exists in the same location on the file system. CRRZI0576I The selected configuration file
updates have been downloaded.
User response:
To replace the file, click Yes. To cancel the export Explanation:
operation, click No. The remote system to which you are connected uses
the push-to-client feature to distribute workspace
CRRZI0572W Overwrite '{0}' ? configuration updates to clients. Your workspace was
updated with new configurations.
User response:

98 Developer for z/OS: Troubleshooting and Support

No action is required. If you would like to suppress User response:
this message the next time you connect to the remote No action is required.
system, click Do not show this message again on the
CRRZI0582E The backup of an existing
message window.
workspace has failed. Make sure
CRRZI0577I You are requesting to import that there is sufficient free disk
configuration files from the group space and that none of the files
{1}. The group {0} was used last in the workspace has a path
to import the configuration files. that is too long. Do you want to
Verify that {1} is the correct group. continue without backing up the
workspace?
Explanation:
The push-to-client feature allows a workspace to be Explanation:
associated with only one access group. You previously When you open a workspace that was created in an
imported configuration files from group {0} and are earlier version of the product, it is migrated to the
now requesting to import configuration files from current version. Before the migration, the workspace
group {1}. is backed up. This message indicates that the backup
operation failed.
User response User response:
To continue migrating the workspace without backing
• If you intended to import the configuration files a
it up, click Yes. To stop the migration and correct the
different group, click OK.
problems, click No.
• If you intended to import files from group {1}
to a different workspace, click Cancel, switch to CRRZI0583E A NullPointerException was
a different workspace, and then try the import encountered during migration of
operation again. the workspace.

CRRZI0579W Your authorization to access group Explanation:

{0} has changed since you last The workspace was not migrated.
connected to this remote system. User response:
The configuration updates will not For information about migrating workspaces, see
be imported into this workspace. Migrating workspaces to a new version.
Explanation: CRRZI0584E Workstation folder {0} under the
The remote system to which you connected uses offline project cannot be migrated.
push-to-client access groups to control access to
configuration updates. Since you last connected to
this system, you were removed from access group {0}.
Explanation
While you can still connect to this remote system, you Attention: The work offline and work
can no longer receive push-to-client updates from it. online operations for a remote resource are
User response: deprecated.
If you do not need any configuration updates from this {0}
remote system, then no action is required. If, however, A folder name.
you need to receive updates from this remote system,
The specified folder is not migrated.
contact your system administrator.
User response:
CRRZI0580W Configuration groups have been
No action is required.
disabled since you last connected
to this remote system. The CRRZI0585E Unable to find the VisualAge®
configuration updates for group CICS Translator or the Transaction
{0} will not be imported into this Server Translator
workspace.
Explanation:
Explanation: The operation requires the VisualAge CICS Translator
The remote system to which you connected previously or the Transaction Server Translator, but these tools
used push-to-client access groups to distribute were not found.
configuration updates. Since you last connected to this
User response:
system, access groups were disabled. While you can
Install one of these translators and try the operation
still connect to this remote system, you can no longer
again.
receive push-to-client updates from group {0}.

Troubleshooting and support 99

CRRZI0586E Unable to find the CICS TX {1}
Series Translator. If you are using The name of a file.
Windows, install the CICS TX {2}
Series Translator. The line number in the file.
CRRZI0587E Local build and local syntax check Because of the specified error, the dependency list of
require an application driver JDBC the selected resource might be incomplete.
connection. The driver associated
with connection {0} is not an User response:
application driver connection. The Correct the condition that caused the specified error
operation will continue. The SQL and try the action again.
coprocessor will not be invoked. CRRZI0593E An exception occurred during file
operation validation.
Explanation
{0} Explanation
The name of a database connection definition. A validation error occurred when you attempted one of
the following actions:
User response:
If you want to the SQL coprocessor top be started, • An action on a file, such as read, create, write, or
use a database connection that has application driver copy.
associated with it. Otherwise, no action is required. • An operation on a data set such as COMPRESS,
MIGRATE, or HRECALL.
CRRZI0590E Problems occurred while
determining build dependencies. You might not have the correct authority to do these
actions.
Explanation:
One or more errors occurred while the product was User response:
attempting to determine the build dependencies of Make sure that you have the correct authority on the
the selected resource. The detailed message for each remote system to do the operation. Ask your systems
error was collected and associated with the original administrator to grant you the authority that you need.
error message.
CRRZI0595I The Java™ Virtual Machine (JVM)
User response: has not yet terminated. Click OK
Examine the detailed error message for each error and to terminate the JVM, wait 30
take the appropriate remedial action. seconds for it to terminate on its
CRRZI0591W own, or click Cancel to cancel the
Resource type {0} is not
installation of product updates.
supported.
Explanation:
Explanation The remote system to which you are connecting
is configured to automatically download product
{0} updates. During the process of shutting down the
The name of the resource that was selected for an client, the Java virtual machine (JVM) failed to
action. terminate in a short amount of time.
The current action was expecting the input resource to
be a member of an MVS subproject. User response
User response: • To terminate the Java virtual machine immediately,
Select an MVS subproject or one of its members and click OK. The client shuts down and IBM Installation
try the action again. Manager starts to begin the product update. After
CRRZI0592E '{0}' was found while processing the product update completes, the client restarts
file '{1}' at line '{2}'. The automatically.
dependency list might be • To cancel the product update and shut down, click
incomplete. Cancel. The next time you start the client and
connect this remote system, you are prompted to
Explanation install the product update again.
• To allow more time for the Java virtual machine to
{0}
terminate, wait 30 seconds. If it does not terminate
An error condition.
within 30 seconds, click OK or Cancel.

100 Developer for z/OS: Troubleshooting and Support

CRRZI0596E '{0}' is not a valid PL/I logical NOT A problem was encountered while attempting to
symbol. carry out the requested operation which prevents the
operation from completing.
Explanation User response:
Examine the detailed error message for the problem
{0}
and take the appropriate remedial action.
A symbol
The specified symbol cannot be used as the PL/I CRRZI0599E Failed to load mapping from file
logical NOT symbol. {0}.

User response:
Refer to the PL/I language reference for a list of valid
Explanation
symbols and try the action again. {0}
The name of an MVS mapping file.
CRRZI0597E The file operation type {0} for
resource {1} is not valid. A problem was encountered when trying to read the
specified MVS mapping root file.
Explanation User response:
For details about this error, see the .log file in
{0}
the .metadata folder of the current workspace.
A file operation
{1}
A resource name

0600-level messages
CRRZI0601E Resource {0} is already locked. User response:
Check that you entered the correct target name and try
the operation again.
Explanation
CRRZI0604E The upload failed.
{0}
The name of a file Explanation:
The current operation requires an exclusive lock on the A problem occurred while attempting to upload the file
specified file but the file is already locked. contents to the remote system.

User response: User response:

If you are not already working with the file, contact Examine the detailed error message for the problem
your systems administrator for assistance locating the and take the appropriate remedial action.
source of the lock. CRRZI0605E An unexpected error occurred
CRRZI0602E Could not find the log in during exception handling. {0}
DataStore.
Explanation:
Explanation
The current operation requires a DataStore log, but {0}
one was not available. A file operation
User response: An unexpected error occurred when attempting to
Disconnect from the remote system and connect validate the requested file operation.
again. Try the operation again. If you continue to User response:
receive this error, contact your systems administrator. For details about this error, see the .log file in
CRRZI0603E The high-level qualifier {0} cannot the .metadata folder of the current workspace.
be added. CRRZI0606E Failed to set the browse request
for file {0}.
Explanation
{0} Explanation
A high-level qualifier {0}
The high-level qualifier that is associated with the A file name
target of the move or copy operation cannot be found.

Troubleshooting and support 101

A problem occurred while attempting to set the User response:
browse request session property on the file. Connect to the remote system and try the operation
again.
User response:
Examine the detailed error message for the problem CRRZI0613I The specified member '{0}' does
and take the appropriate remedial action. not exist in the data set '{1}'.
Do you want to create this new
CRRZI0607E The file is already locked by alias
member?
or reference.
Explanation:
Explanation:
On the Find Member window, you typed a member
The current operation requires an exclusive lock on the
name that does not exist in the partitioned data set.
specified file, but an alias of or reference to the file is
already locked.
User response
User response:
If you are not already working with the alias or • To create a member, click Yes. The new member is
reference, contact your systems administrator for created in the data set.
assistance locating the source of the lock. • To close this message and return to the Find
CRRZI0608E The file cannot be downloaded. Member window without creating a member, click
No. If you mistyped the member name, you can try
Explanation: the search again.
An unexpected error occurred when the client
attempted to download the requested remote file. CRRZI0614W The result set contains {0}
matches. A maximum of {1}
User response: matches can be displayed. Refine
For details about this error, see the .log file in the member name pattern or
the .metadata folder of the current workspace. change the preference and try
CRRZI0609E Resource type {0} is not again.
supported. Explanation:
On the Find Member window, you typed a member
Explanation name pattern that results in more matches than the
current limit.
{0}
A resource type
User response
A remote error marker cannot be created because the
selected resource is not an MVS resource. • To refine the member name pattern, try including
more characters in the name. Instead of searching
User response:
for MY*, for example, search for MYFIL*.
Select an MVS resource and try the action again.
• To increase the result set limit:
CRRZI0611E Failed to store mapping to file {0}.
1. In the Preferences window, navigate to Remote
Systems > z/OS > MVS Files.
Explanation
2. In the Maximum results for Find Member field,
{0} specify the maximum number of search results to
The name of an MVS mapping file. return with the Find Member action. The default
A problem occurred when the client attempted to save value is 1000 members.
the current file system mappings.
CRRZI0615I Request was submitted for '{0}'.
User response:
Examine the detailed error message for the problem Explanation
and take the appropriate remedial action.
{0}
CRRZI0612E The system is not connected. A data set name.
Connect to the remote system and
try the operation again. The requested action for the data set indicated by {0}
completed successfully.
Explanation:
You must be connected to a remote system to work User response:
with remote z/OS resources. No action is required.

102 Developer for z/OS: Troubleshooting and Support

CRRZI0616I Request was submitted for {0} In the Retrieve Data Set window a maximum of {1}
data sets. matching data sets can be displayed. The data set
name pattern entered matches more data set names
than the maximum allowed.
Explanation
User response:
{0}
Use a data set name pattern that results in fewer
The number of data sets for which the request was
matches. For example, if you previously typed
submitted.
USERID.TEST.C*, typing USERID.TEST.COB* might
The requested action for the number of data sets result in fewer matches.
indicated by {0} completed successfully.
CRRZI0621I '{0}' has been compressed
User response: successfully.
No action is required.
Explanation:
CRRZI0617I Request was submitted for {0} of This message indicates that the Compress action for
{1} selected data sets. the data set indicated by {0} completed successfully.
User response:
Explanation No action is required.
{0} CRRZI0622I {0} data sets have been
The number of data sets for which the action compressed successfully.
completed.
Explanation:
{1}
This message indicates that the Compress action for
The number of data sets for which the action was
a number of data sets indicated by {0} completed
requested.
successfully.
The requested action for some data sets completed
User response:
successfully. The action was requested for the
No action is required.
number of data sets indicated by {1} and completed
successfully for the number of data sets indicated by CRRZI0623I {0} of {1} data sets have been
{0}. compressed successfully.
User response: Explanation:
No action is required. This message indicates that the Compress action for
some data sets completed successfully. The action
CRRZI0618E Request was not submitted.
was requested for the number of data sets indicated
Explanation: by {1} and completed successfully for the number of
The requested action for the selected data set did not data sets indicated by {0}.
complete successfully.
User response:
User response: No action is required.
Try the operation again. If the failure recurs, contact
CRRZI0624E The data set was not compressed.
your systems programmer.
Explanation:
CRRZI0619W Are you sure you want to delete
This message indicates that the Compress action
mapping '{0}'?
for the data set indicated by {0} did not complete
Explanation: successfully.
This message prompts you to confirm a request to
User response:
delete a z/OS file system mapping.
Attempt the compress again. If the failure recurs,
User response: contact your systems programmer.
Click Yes to delete the mapping or No to cancel the
CRRZI0626I Are you sure you want to remove
request.
the selected global variable?
CRRZI0620W The result set contains {0}
Explanation:
matches. A maximum of {1}
This message is a prompt to confirm the removal of a
matches can be displayed. Refine
global variable.
the data set name pattern and try
again. User response:
Select Yes or No.
Explanation:

Troubleshooting and support 103

CRRZI0627I Are you sure you want to remove Make sure that the copybook does not have any
the selected user variable? dependencies. Try the operation again.
Explanation: CRRZI0635I This kind of project is associated
This message is a prompt to confirm the removal of a with the {0} perspective. Do you
user variable. want to switch to this perspective
now?
User response:
Select Yes or No. Explanation:
This message displays in response to successful
CRRZI0628I Are you sure you want to remove creation of a new project. It prompts you to switch to
the preprocessor? the perspective that is most commonly used to work
Explanation: with the project type.
This message is displayed when you remove a local User response:
preprocessor on the Local Preprocessor page of the Click Yes to switch to the perspective or No to remain
property group editor. There is no undo action for in the current perspective.
removing a local preprocessor.
CRRZI0636I This kind of project, including MVS
User response: subprojects, workstation COBOL
To delete the local preprocessor, click OK. To keep the projects, and workstation PL/I
local preprocessor, click Cancel. projects, is associated with the
CRRZI0629I Are you sure you want to remove z/OS Projects perspective. Do you
the step? want to switch to this perspective
now?
Explanation:
This message is displayed when you remove a step Explanation:
from a Procedures and Steps table in the property This message displays in response to successful
group editor. There is no undo action for removing a creation of a new project. It prompts you to switch
step. to the z/OS Projects perspective, which is most
commonly used to work with this project type.
User response:
To remove the step, click OK. To keep the step, click User response:
Cancel. Click Yes to switch to the z/OS Projects perspective or
No to remain in the current perspective.
CRRZI0630E Cannot open a null resource.
CRRZI0637W The project {0} cannot be built
Explanation:
because it is offline.
An editor could not open on the selected resource.
Explanation:
User response: A build request was submitted for an offline project. A
Select a different file and try the operation again. project must be online to be built.
CRRZI0631E Cannot find {0}. User response:
Move the project to online state and try the build
Explanation operation again.
{0} CRRZI0638W Contact your administrator to
The path of the z/OS UNIX file. ensure that the build server is
running on the remote system and
User response:
that the correct port is specified.
Ensure that the z/OS UNIX file exists. Try the operation
again. Explanation:
A build request was submitted, but the build server
CRRZI0632I For successful generation from
cannot be found.
this copybook, the copybook
should be self-contained. User response:
Contact your system administrator.
Explanation:
For the operation to work successfully for this CRRZI0642W The file {0} is locked by another
copybook, the copybook must not have any user and will be opened in read-
dependencies. only mode.
User response: Explanation:

104 Developer for z/OS: Troubleshooting and Support

An edit request was submitted for a locked file. The file current lock owner user ID, but the user ID may not
can be opened for read-only access, but it cannot be be obtainable if the owning threadpool process fails
edited. to respond in time due to high system load or other
problems. In these cases, the job name and process
User response:
ID of the threadpool process will be displayed instead
To determine the lock owner of a remote resource,
of the lock owner user ID.
open the properties view and expand the Info category
to see the Lock owner property. User response:
If the problem persists, contact your system
CRRZI0643W The file {0} is locked by '{1}' and
programmer who may choose to terminate the
will be opened in read-only mode.
affected threadpool process or restart the Remote
Explanation: System Explorer daemon.
An edit request was submitted for the specified file,
CRRZI0665E Could not perform the project
which is locked by the specified user. The file can be
build operation.
opened for read-only access, but it cannot be edited.
Explanation:
User response:
A Rebuild Project or Rebuild Subproject request
No response is required.
cannot be completed.
CRRZI0644W An error occurred while
attempting to obtain a file lock. User response
The file {0} will be opened
Before building a project or subproject:
in read-only mode. Disconnect
and reconnect all z/OS remote • Ensure that you are connected to the remote system.
systems. • Verify that the build settings in the property group
Explanation: are specified correctly.
An edit request was submitted for a locked file. The file CRRZI0666W Could not open file {0}.
can be opened for read-only access, but it cannot be
edited.
Explanation
User response:
You can continue to browse the file in read-only mode, {0}
but to correct the file lock problem you need to The name of a file.
reconnect to the remote system. The editor tried to open the file, but the open
CRRZI0645W '{0}' already exists. Do you want to operation failed with an exception. The file cannot be
overwrite it? opened.
User response:
Explanation Verify that the file exists and try the operation again.

{0} CRRZI0667W Could not open file {0}: {1}.

A file name.
A request was made to export a property group, z/OS Explanation
project, or z/OS file system mapping to a file, but the {0}
target file exists. The name of a file.
User response: {1}
To overwrite the file, click Yes. To cancel the export A message that indicates the exception that
operation, click No. occurred.
CRRZI0646W The file {0} is locked by '{1}' and The editor tried to open a file, but failed with an
will be opened in read-only mode. exception. The file cannot be opened
Please contact your support team
User response:
if problem persists.
Verify that the file exists and try the operation again.
Explanation:
CRRZI0668I The z/OS project has been
This message may be displayed when a user attempts
exported successfully. The source
to open a file resource that is locked by another user
files in the project are not
that is logged into an unresponsive Remote System
exported in this operation. Only
Explorer threadpool process running on the z/OS host.
the project structure and the
Normally, a message would be displayed showing the

Troubleshooting and support 105

 associated property groups are CRRZI0673W Any non-uploaded changes will be
exported. lost. Are you sure you want to
Explanation: continue?
This message indicates a successful export z/OS
project operation. Explanation
User response: Attention: The work offline and work
No response is required. online operations for a remote resource are
deprecated.
CRRZI0669E A resource exists with a different
case: Before you take a project online by using the Work
Online action, you must upload the changes that you
Explanation:
made to the resources when the project was offline. If
A request to drag a local file into a local folder in the
you click Work Online without uploading the changes
z/OS Projects view failed. The file cannot be copied
that were made locally (while the project was offline),
because a resource with the same name but in a
the changes are lost. You must confirm that the work
different case exists in the target folder.
online operation can continue, which causes the local
User response: changes to be lost.
Verify the source file name and target folder and try
the operation again.
User response
CRRZI0671W Failed to download {0}.
1. Before you click Work Online, upload any changes
that you made to the resources when the project
Explanation was offline.
Attention: The work offline and work 2. To upload any changes that you made while the
online operations for a remote resource are project was offline, select them in the Changes
deprecated. view and then select Upload from the menu.
{0} 3. After you upload all the changes that you want to
The name of a remote resource. save, click Work Online.

A problem occurred during the download action of a CRRZI0674W At least one of the values of your
work online operation. A local copy of the resource SYSLIB or local compiler options
cannot be created in the offline project. has changed since the project was
taken offline. These changes will
User response: be lost when the project is online.
No action is required. Click OK to continue, or click
CRRZI0672W Unable to migrate property {0}. Cancel to return to the wizard.
Explanation:
Explanation When a project is offline, the resources on the remote
system are still accessible to others. You must merge
Attention: The work offline and work your changes with any changes other users made to
online operations for a remote resource are resources.
deprecated.
User response:
{0} To upload and changes that you made while the
The name of a property in a property group. project was offline, select them in the Changes and
As part of a work offline operation, all the selected then select Upload from the menu. After you upload
remote resources are downloaded to a local project all the changes you want to save, click Work Online.
and all the properties that are associated with the
CRRZI0675W Failed to upload {0}.
remote resource are migrated to the local resource.
An error occurred while the operation was migrating a
property. Explanation
User response: {0}
Check the property for which the migration failed and The name of a local resource.
make sure to set it before you run operations like During the upload action of a work online operation, a
syntax check, which uses the properties of the local problem occurred while the operation was uploading
resource. the local resource and creating a remote resource.

106 Developer for z/OS: Troubleshooting and Support

User response: CRRZI0678W Product groups have been
No action is required. disabled since you last connected
to this remote system. The product
CRRZI0676I You are requesting to export
updates for group {0} will not be
configuration files to group {1},
imported into this workspace.
which is different from the group
{0} currently associated with your Explanation:
workspace. Click OK to continue The remote system to which you connected previously
or Cancel to return to the Export used push-to-client access groups to distribute
wizard. product updates. Since you last connected to this
system, access groups were disabled. While you can
Explanation:
still connect to this remote system, you can no longer
The push-to-client feature allows a workspace to be
receive push-to-client updates from group {0}.
associated with only one access group. You previously
exported configuration files to group {0} and are now User response:
requesting to export these configuration files to group No action is required.
{1}.
CRRZI0687E z Systems Data Editor failed to
open the file {0}.
User response
Explanation:
• If you intended to export the same configuration files The z Systems Data Editor could not open the specified
to both groups, click OK. file. This error occurs when the downloaded cache files
• If you intended to export files to group {1} from are not valid.
a different workspace, click Cancel, switch to User response:
a different workspace, and then try the export Clear the local downloaded cache and open the
operation again. dataset again.
CRRZI0677W Your authorization to access CRRZI0691E z Systems Data Editor failed to
product group {0} has changed save the file {0} on the remote
since you last connected to system.
this remote system. The product
updates will not be imported into
this workspace. Explanation
The z Systems Data Editor cannot save the data set
Explanation: and the editing content cannot be saved to the remote
The remote system to which you connected uses system.
push-to-client access groups to control access to
product updates. Since you last connected to this {0}
system, you were removed from access group {0}. File name
While you can still connect to this remote system, you User response:
can no longer receive push-to-client updates from it. Confirm that the data set is not locked by another
User response: editor. If the data set is open in another editor, close
If you do not need any product updates from this the editor and the z Systems Data Editor. Reopen the
data set with the System z Data Editor.
remote system, then no action is required. If, however,
you need to receive updates from this remote system,
contact your system administrator.

0700-level messages
CRRZI0735I A folder was passed to the CRRZI0736I This file's contents are not
LogicalFSFileStore#getContents() available because the scheduling
method, which requires a file as rule for the current job does
input. not contain all the necessary
resources.
Explanation:
Getting the contents of a LogicalFSFileStore is valid Explanation:
only when the resource associated with the store is a This message can occur when you add a remote
file. partitioned data set (PDS) to a subproject. To update
the content-type file decoration, the Eclipse system
User response:
must query the contents of the Eclipse file system
No action is required.

Troubleshooting and support 107

resource that represents one of the members of the User response:
added PDS. To read its contents, however, it is using To see the error, click Details.
a scheduling rule that does not include the cached
CRRZI0741E The preprocessor output {0} was
files folder. The request to add the resource to the
not found.
subproject completed successfully.
User response: Explanation
No action is required.
{0}
CRRZI0737W The server has been configured to The file that contains the preprocessor output.
automatically download product
updates to the client when you The product ran the script that starts the remote
connect to the remote system. preprocessor, but cannot find the preprocessor output.
Current Product Version shows User response:
the product version currently Verify that you are running the script that you intend to
installed on your workstation. A run. If so, verify that the script is executing correctly.
new version cannot be rejected
and will be installed when you CRRZI0742E The remote preprocessor {0} was
click OK. not found.

Explanation:
The remote system to which you are connecting Explanation
is configured to automatically download product {0}
updates. You are not allowed to reject these updates. The preprocessor name.
When you click OK, your workbench is shut down
The product cannot find the remote preprocessor that
and IBM Installation Manager is started to install
is specified in the property group.
the product updates. The workbench is automatically
restarted after the product update completes. User response:
Verify that the remote preprocessor has the data set
User response:
and member name that is specified in the property
Click OK.
group and that you have read access to the data set
CRRZI0738E Update of a remote file failed. that contains the preprocessor.
Explanation: CRRZI0745E The project '{0}' does not have
A request to update a remote file failed. a property group associated with
it. Associate a property group
User response:
and then try the project build
For more information about this error, see the
operation again.
rsecomm.log and ffs*.log files on the remote
system. Explanation:
To build a project, you need associate a property
CRRZI0739E An error occurred when
group with it. No property group is associated with the
downloading the preprocessor
project.
output.
User response:
Explanation:
Use the Associate Property Group action to associate a
The product attempts to download the remote
property group with a subproject and then try the build
preprocessor output after it runs the remote
operation again.
preprocessor. An error while the product was
downloading the output. CRRZI0746E VSAM data set allocation failed.
User response: Explanation:
Verify that you are still connected to the system on A New > Allocate VSAM Data Set operation failed to
which the remote preprocessor runs and that you allocate the data set. The most common reason for
have read access to the data set that contains the this failure is missing values for the space unit, primary
preprocessor output. unit, and secondary unit parameters.
CRRZI0740E The remote preprocessor ended User response:
with an error. Check the allocation parameters on page 3 of
the wizard and try the operation again. Contact
Explanation:
your system administrator for guidance on specific
The script that runs the remote preprocessor finished
allocation parameter values.
with an error.

108 Developer for z/OS: Troubleshooting and Support

CRRZI0747E The compiler option CRRZI0751E An error occurred when creating
"CICS('CTS42')" is not applicable the remote preprocessor input
for a build operation. Remove the data set {0}.
suboption "CTS42" and try again.
Explanation: Explanation
The CICS suboption CTS42 was specified for a local When you start a remote preprocessor, the input for
build. This suboption is valid only in the context of the remote preprocessor is written to a file in a
syntax check when the source code is being checked sequential data set. Then, the remote preprocessor
against the syntax of CICS Transaction Server for z/OS can read from the sequential data set to get the
4.2. information it needs. An error occurred allocating the
data set or writing to it.
User response:
If you are building a local application, remove the {0}
CTS42 suboption from the CICS compiler option. A data set name.
CRRZI0748E Record length is not available User response:
Verify with your systems administrator that you
Explanation: have permission to allocate and write to sequential
The record length information is not available from the data sets on the remote system where the remote
property associated with the data set. preprocessor runs.
User response: CRRZI0752E Unable to communicate with the
Check the status of the server to see if there are server. Verify the port number and
errors. Try connecting to the server again. Debug Tool classpath variables
CRRZI0749E The dataset cannot be opened in job IPVGSVRJ on the remote
because data format is Undefined. system.
Explanation: Explanation:
The file cannot be open because the data set record A connection to the debug tool cannot be made.
is defined as RECFM=U. The z Systems Data Editor User response:
cannot open a data set whose record format is Verify the port number and try the operation again.
undefined because the editor uses the record format
and length to determine each record of the sequential CRRZI0753I Specify the required information
data set. to connect to IBM Problem
Determination Tools Common
User response: Components Server.
Use a different editor to open the data set.
Explanation:
CRRZI0750E File '{0}' contains characters that This message displays when you save a new Db2
cannot be transferred correctly and IMS debug configuration. It prompts you to
between the local and remote define connection settings for the Db2 and IMS debug
systems. The file will be opened in configuration.
read-only mode.
User response:
Explanation: Click OK. The Db2 and IMS Debug Configuration
The editors are able to preserve the integrity of preferences window opens. Use this window to define
characters as they are transferred from the remote connection settings.
system to the workstation and back again. For some
code pages, however, it is not possible to preserve CRRZI0754E Unable to update the debug
round-trip integrity of certain characters. This message profile. The profile data set "{0}"
warns that the file under edit contains characters might be in use or you do not have
whose round-trip integrity cannot be preserved. write access.
Because the file is being edited from the remote Explanation:
system, it is opened in read-only mode. The Debug Configurations wizard cannot update the
User response: debug profile data set.
To edit the file, copy it to a local project in your User response:
workspace and change the corrupted characters Ensure that you have write access to the debug profile
before you copy it to the remote system. data set and that it is not in use and try the operation
again.

Troubleshooting and support 109

CRRZI0755W You are requesting to export User response:
configuration files to group {0}. No response is required.
This action creates an association CRRZI0760W This filter contains {0} data sets,
between the workspace and and the expansion of the filter
configuration group {0}. might take a long time. Do you
Explanation: want to proceed?
When you export a configuration file from a workspace Explanation:
to a configuration group, the workspace is bound to The number of data sets in a filter exceeds the
that group. All subsequent export requests from this threshold set in the Default expansion page size
workspace are exported to the same group. for filters and data sets field of the MVS Files
User response: preferences page.
No response is required.
CRRZI0756I You are opening a file that has User response
an associated property group that Click Yes to continue expanding the filter or No to
specifies remote libraries on the cancel the operation. To change the warning threshold:
system "{0}". To access the include 1. In the Preferences window, navigate to Remote
files in those libraries, connect to Systems > z/OS > MVS Files.
the remote system.
2. Type a number in the Default expansion page size
Explanation: for filters and data sets field.
Access to remote libraries requires access to the
remote system on which they are located. CRRZI0761E The selected remote system is not
connected. Connect to the remote
User response: system and try again.
Connect to the remote system.
Explanation:
CRRZI0757E The copy function doesn't support On the Add Include Library, Edit Include Library,
a record length that exceeds the Add Copy Library, or Edit Copy Library window, the
maximum block size. remote system that is selected is not connected.
Explanation: User response:
This error occurs when attempting to copy and paste Connect to the remote system and try the operation
from a local text file with a large record length to a new again.
MVS sequential data set. The product cannot allocate
a data set with a record length that is longer than the CRRZI0762E Could not read a remote file that
maximum block size. The data set is not created. has invalid block size.

User response: Explanation:

No response is required. An attempt was made to open, browse, or view a data
set with a block size of 0.
CRRZI0758E Resources with an undefined
record format cannot be copied. User response:
Modify the data set characteristics to specify a valid
Explanation: block size and try the operation again.
An attempt was made to copy a binary file (such as a
load module) from one remote system to another or CRRZI0763I You are opening a remote file with
between local and remote systems. This operation is an external editor. As a result, any
not supported. changes made to the file cannot be
saved on the remote system.
User response:
No response is required. Explanation:
Remote files that are edited with an external editor
CRRZI0759E Resources with an undefined cannot be saved to the remote system.
record format cannot be copied
across systems. User response:
To edit a remote file and save the changes to the
Explanation: remote system, use an internal editor, such as the z
An attempt was made to copy a binary file (such as a Systems LPEX Editor, COBOL Editor, or PL/I Editor.
load module) from one remote system to another or
between local and remote systems. This operation is CRRZI0764W Migrated data sets will not be
not supported. considered in the look up path.

110 Developer for z/OS: Troubleshooting and Support

 Select the '{0}' in the Remote When you open a file in an editor, it checks for
Systems view and perform the a property group associated with the file. Property
HRECALL action. groups contain settings that enable the editor the
resolve dependencies, such as copybooks and include
Explanation files. This message prompts you to either open the file
without a property group or to create or associate a
{0} property group with the file.
The migrated data set
The JCL procedure lookup path contains a data set User response
that is migrated. Migrated data sets are not accessible To open the file without associating a property group,
for JCL navigation. click OK. To create or associate a property group, click
User response: one of the following links:
To recall a migrated data set, select the data set • Associate an existing property group: Opens the
name in the Remote Systems view and then select Associate Property Group window so that you can
HRECALL from the menu. choose a property group to associate with the file.
CRRZI0765E The data set '{0}' could not • Associate an existing property group with the parent
be found. Verify that both the data set: Opens the Associate Property Group
data set name was highlighted window so that you can choose a property group to
correctly and the data set exists. associate with the file and with the file's parent data
set.
Explanation • Associate an existing property group with parent
MVS subproject: Opens the Associate Property
{0}
Group window so that you can choose a property
The data set name
group to associate with the file and with the
A data set highlighted in the editor cannot be found by subproject that contains the file.
using the Navigate to data set action. • Create and associate a new property group: Opens
User response: the property group editor so that you can create a
Verify the data set name and try the action again. property group and associate it with the file.
CRRZI0766E The JCL procedure cannot be • Create and associate a new property group with the
found in the JCL procedure look up parent data set: Opens the property group editor so
path. Verify that both the file and that you can create a property group and associate it
the library are allocated properly. with the file and with the file's parent data set.
• Create and associate a new property group with
Explanation:
parent MVS subproject: Opens the property group
A JCL procedure name highlighted in the editor cannot
editor so that you can create a property group and
be found by using the Open JCL Procedure action.
associate it with the file and with the subproject that
User response: contains the file.
Verify that the libraries specified in the Include and
If you choose to associate an existing property group,
procedure search libraries property are correct and
the file is opened after the association is made. If you
that the member name is correct. Try the action again.
choose to create a property group, you need to request
CRRZI0767W The resource '{0}' does not the file open action again.
have a property group associated
CRRZI0768I {0} of {1} jobs were submitted
with it. A property group
successfully. To see a list of jobs
contains information required to
and their status, click Details.
resolve dependencies and enable
From the Details view, you can
advanced editor features. Click
select one or more successfully
OK to open the resource without
submitted jobs to locate in the
associating a property group or
Remote Systems view.
choose an action.

Explanation Explanation
{0}
{0}
The number of jobs that were submitted
A partitioned data set member
successfully

Troubleshooting and support 111

{1} Configuration groups are created and administered on
The total number of jobs that were submitted the remote system. If a configuration group name
contains invalid characters, then the configurations
User response:
that it controls cannot be downloaded to the
No action is required. For more information about
workstation.
submitting multiple jobs, see the related topics.
User response:
CRRZI0769E The Work Offline action is disabled
Contact your systems administrator. For more
for remote system {0}.
information about configuration groups, see Push-
to-client considerations in the Host Configuration
Explanation Reference.
Attention: The work offline and work CRRZI0772W The server does not have enough
online operations for a remote resource are memory available to perform the
deprecated. search.
{0} Explanation:
The name of a remote system A partitioned data set member is tool large for the
The remote system is configured to deny permission to server to search.
work offline.
User response:
User response
Do one of the following actions:
Consult your systems administrator if you have
questions about offline permissions on a remote • Specify more specific search conditions. In the
system. Remote z/OS Search window, click Search Options
and specify a smaller number in the Search results
CRRZI0770E The remote system {0} associated
limit field.
with this project is not connected.
Connect to the remote system and • To expand the server memory size, specify a larger
try the operation again. value for the Java maximum heap size in the
rse.env file on the server. For more information
about this file, see Basic customization in the Host
Explanation
Configuration Guide.
Attention: The work offline and work
CRRZI0773E The server does not have enough
online operations for a remote resource are
memory available to download {0}.
deprecated.
{0}
Explanation
The name of a remote system
{0}
Systems administrators have the ability to configure
A data set name.
remote systems to deny permission to work offline. To
determine if working offline is allowed on the remote A data set is tool large for the server to download.
system, you must be connected to the remote system User response:
before you request the Work Offline action. Expand the server memory size. Specify a larger value
User response: for the Java maximum heap size in the rse.env file
Connect to the remote system and try the Work on the server. For more information about this file, see
Offline action again. Basic customization.
CRRZI0771E The configuration group name {0} CRRZI0774E Some characters cannot be
contains the invalid character {1}. mapped using host code page '{0}'.
Contact your administrator to have Either change the host code page
the name changed. or remove the characters which
are not supported by the host code
page '{0}'.
Explanation
{0}
Explanation
The name of a push-to-client configuration group.
{0}
{1}
The host code page.
The character that is invalid.

112 Developer for z/OS: Troubleshooting and Support

This error occurs when you create or save a remote 2. From the list on the left side of the Properties
file that uses characters that are not supported by the window, click Resource.
host code page of the container. 3. In the Text file encoding area of the window, click
Other and specify a local code page.
User response
CRRZI0776E Failed to get the characteristics of
Modify the host code page property of the remote
the data set.
container:
Explanation:
1. To open the container Properties window, do one
An attempt to obtain the characteristics of the data
of the following actions:
set, such as DSN type, data set organization, or record
• Right-click the container and select Properties format, failed. This error might be caused by a TSO
from the menu. command server error.
• Select the container and press Alt+Enter. User response:
2. From the list on the left side of the Properties Try the operation again. For more information about
window, click Mapping. this error, see the rsecomm.log and ffs*.log files
on the remote system.
3. In the Host code page area of the window, click
Other and specify a host code page. CRRZI0777E Problems occurred while adding
Data Access Support to the
CRRZI0775E Some characters cannot be selected resource.
mapped using local code page
'{0}'. Either change the local code Explanation:
page or remove the characters Data Access Support was not added to the resource.
which are not supported by the User response:
local code page '{0}'. Try the operation again.
CRRZI0778E Problems occurred while removing
Explanation Data Access Support from the
{0} selected resource.
The local code page.
Explanation:
This error occurs when you create or save a local or Data Access Support was not removed from the
remote file that uses characters that are not supported selected resource.
by the local code page of the container.
User response:
Try the operation again.
User response
To modify the local code page property of a remote CRRZI0779E The options data set exists, but is
container: not a sequential data set. Delete
the data set before attempting to
1. To open the container Properties window, do one update the profile.
of the following actions:
User response:
• Right-click the container and select Properties Specify a sequential data set.
from the menu.
CRRZI0780E The options data set is migrated.
• Select the container and press Alt+Enter. From the Remote Systems
2. From the list on the left side of the Properties Explorer view, request HRECALL
window, click Mapping. for the sequential data set.
3. In the Local code page area of the window, click User response:
Other and specify a local code page. Recall the data set and try the operation again.
To modify the local code page property of a local CRRZI0781E The options specified "{0}" contain
container: a string of more than 72
1. To open the container Properties window, do one consecutive characters with no
of the following actions: comma to break the string.

• Right-click the container and select Properties

from the menu.
• Select the container and press Alt+Enter.

Troubleshooting and support 113

Explanation CRRZI0786W The file {0} is locked by ''{1}'' and
cannot be opened.
{0}
The Language Environment options that were
specified in the debug profile. Explanation
User response: {0}
Specify a string of 72 characters or less. A file name.

CRRZI0782E An error occurred while writing to {1}

the profile data set "{0}". A user ID.
Another user has a lock on the specified file.
Explanation User response:
{0} Ask the user to release the file or wait until the file is
A data set name. no longer locked and try the operation again.

User response: CRRZI0787W The program {0} is duplicated

Make sure you have write access to the data set and elsewhere in the scan.
try the operation again.
CRRZI0783E The EQAOPTS data set "{0}" could Explanation
not be allocated. {1} {0}
A program name.
Explanation The COBOL call analyzer determined that the program
{0} name shown in the message is duplicated in another
A data set name. program source file.

{1} User response:

A return code. Consider updating the source programs to ensure that
each program source file specifies a unique name in
CRRZI0784I The JCL was submitted to remote the PROGRAM-ID statement.
system ''{1}'' and the Job ID is
''{0}''. Click Locate Job to locate CRRZI0788E {0} is using {1} parameters but {2}
the job in the Remote Systems expects {3} parameters.
view. Click Notify to be notified
when the job completes. Explanation
{0}
Explanation The name of a calling program.
{0} {1}
The job ID of a job that was submmitted to JES. The number of parameters that the calling program
{1} is passing to a called program.
A remote system name. {2}
User response: The name of the called program.
No action is required. {3}
The number of parameters expected by a called
CRRZI0785W The file {0} is locked by another
program.
user and cannot be opened.
The COBOL call analyzer determined that the calling
program name shown in the message is calling another
Explanation program with an unexpected number of parameters.
{0} The message shows the number of parameters
A file name. expected by the called program.
Another user has a lock on the specified file. User response:
User response: Consider updating the parameters in the call to the
Wait until the file is no longer locked and try the target program.
operation again. CRRZI0789E {0} is using {1} parameter but {2}
expects {3} parameters.

114 Developer for z/OS: Troubleshooting and Support

Explanation Explanation
{0} {0}
The name of a calling program. The name of a calling program.
{1} {1}
The number of parameters that the calling program The name of a called program.
is passing to a called program. {2}
{2} The order of a parameter in a program call.
The name of the called program. {3}
{3} The size of the parameter
The number of parameters expected by a called {4}
program. The name of the called program.
The COBOL call analyzer determined that the calling {5}
program name shown in the message is calling another The expected size of the parameter.
program with an unexpected number of parameters.
The message shows the number of parameters The COBOL call analyzer determined that the calling
expected by the called program. program name shown in the message is calling another
program with a parameter that has an unexpected
User response: size. The message shows the size of the parameter
Consider updating the parameters in the call to the that is exepcted by the called program.
target program.
User response:
CRRZI0790E {0} is using {1} parameter but {2} Consider updating the parameter in the call to the
expects {3} parameter. target program.
CRRZI0792W The file {0} is locked by '{1}' and
Explanation cannot be opened. Please contact
{0} your support team if problem
The name of a calling program. persists.
{1} Explanation:
The number of parameters that the calling program This message may be displayed when a user attempts
is passing to a called program. to open a file resource that is locked by another user
{2} that is logged into an unresponsive Remote System
The name of the called program. Explorer threadpool process running on the z/OS host.
Normally, a message would be displayed showing the
{3} current lock owner user ID, but the user ID may not
The number of parameters expected by a called be obtainable if the owning threadpool process fails
program. to respond in time due to high system load or other
The COBOL call analyzer determined that the calling problems. In these cases, the job name and process
program name shown in the message is calling another ID of the threadpool process will be displayed instead
program with an unexpected number of parameters. of the lock owner user ID.
The message shows the number of parameters User response:
expected by the called program. If the problem persists, contact your system
User response: programmer who may choose to terminate the
Consider updating the parameters in the call to the affected threadpool process or restart the Remote
target program. System Explorer daemon.
CRRZI0791E {0} is incompatible with {1};
parameter {2} has a size of {3} but
{4} is expecting a size of {5}.

0800-level messages
CRRZI0802W Resource {0} does not exist. Verify that the file system resource exists.
Explanation: CRRZI0803W Resource {0} is specified as
The file system resources does not exist. DISP={1}, but already exists.
User response: Explanation:

Troubleshooting and support 115

A JCL DD statement is specified with DISP=NEW, but referenced this file system resource. See DISP
the data set or file specified by the DD statement parameter for more information.
already exists.
CRRZI0805W Resource {0} is specified as
User response: DISP={1}, but may have been
Delete the existing file system resource, or modify deleted by a previous step which
the DISP parameter of the DD statement. See DISP specified DISP={2} on line {3}.
parameter for more information.
Explanation:
CRRZI0804W Resource {0} is specified as A JCL DD statement is specified with DISP=SHR, MOD
DISP={1}, but may not have been or OLD, but a previous DD statement for the same the
deleted by a previous step which data set or file may have specified the DISP parameter
specified DISP={2} on line {3}. with DELETE as the normal or abnormal termination
sub-parameter.
Explanation:
A JCL DD statement is specified with DISP=NEW, but User response:
a previous DD statement for the same the data set or Modify the DISP parameter of either the current
file may have specified the DISP parameter with KEEP, DD statement or the previous DD statement that
PASS, CATLG, or UNCATLG as the normal or abnormal referenced this file system resource. See DISP
termination sub-parameter. parameter for more information.
User response:
Modify the DISP parameter of either the current
DD statement or the previous DD statement that

0900-level messages
CRRZI0901W RSE threadpool is approaching MAXTHREADTASKS limit. Contact your
system programmer (ProcessID={0}).
Explanation:
The amount of MAXTHREADTASKS created for this RSE threadpool is approaching the limit defined in
SYS1.PARMLIB(BPXPRMxx).
User response:
Adjust the MAXTHREADTASKS limit defined in SYS1.PARMLIB(BPXPRMxx) appropriately.

8000-level messages
CRRZI8503E The source file is not available. The data set member that is associated with the
You might need to connect to a stored procedure belongs to an MVS system in the
z/OS system. Remote Systems Explorer with the name {0}. The
system no longer exists.
Explanation:
A deployment operation was attempted, but you are User response:
not connected to an MVS system in the Remote Switch to the z/OS Projects perspective and define {0}
Systems view. as a z/OS system with the appropriate IP address.
User response: CRRZI8501E A connection to {0} is required to
Connect to the MVS system in the Remote Systems complete this action.
view and try the operation again.
CRRZI8505E The z/OS system definition for '{0}' Explanation
does not exist. Switch to the z/OS {0}
Projects perspective and define A database system.
'{0}' as a z/OS system with the
appropriate IP address. User response:
Connect to the specified database and try the
operation again.
Explanation
CRRZI8502E The format of the stored procedure
{0} source location is invalid.
The name of a remote z/OS system.
Explanation:

116 Developer for z/OS: Troubleshooting and Support

The stored procedure file in the Data Development Explanation
project no longer contains the name of a valid source
file on a valid MVS System. {0}
The name of a remote z/OS system.

User response The data set member that is associated with the
stored procedure belongs to an MVS system in the
1. If the source file exists as a member in a Remote Systems Explorer with the name {0}. The
partitioned data set on a system that is defined in system no longer exists.
the Remote Systems Explorer, rename or copy the
User response:
source file to a safe location.
Switch to the z/OS Projects perspective and define {0}
2. Delete the stored procedure in the Data as a z/OS system with the appropriate IP address.
Development Project.
CRRZI8506E The data set '{0}' is migrated.
3. Re-create the stored procedure by using the Create
Select the data set in the Remote
Stored Procedure Wizard.
Systems view and perform the
4. When the stored procedure is created, copy the HRECALL action.
saved source file to the location of the default
source file that was created by the wizard. Explanation:
You submitted a generate JCL request and specified
5. Try the action again. the partitioned data set name indicated by {0} as the
CRRZI8503E The source file is not available. target data set for the generated JCL file. This data set
You might need to connect to a is migrated and is not available.
z/OS system. User response:
Explanation: In the Remote Systems view, select the partitioned
A deployment operation was attempted, but you are data set and then select HRECALL from the menu.
not connected to an MVS system in the Remote CRRZI8507E '{0}' already exists in '{1}'. Select a
Systems view. different source data set.
User response:
Connect to the MVS system in the Remote Systems Explanation
view and try the operation again.
{0}
CRRZI8504E Unable to locate source file '{0}' on A member name.
system '{1}'. {1}
A partitioned data set name.
Explanation An attempt was made to save a stored procedure to
{0} a partitioned data set, but the partitioned data set
The name of a stored procedure source file. contains a member with the same name.
{1} User response:
The name of a remote system. Select a different partitioned data set.
The source file that is associated with the stored CRRZI8508E '{0}' is not connected. Switch to
procedure is no longer available on the remote system. the z/OS Projects perspective and
It might be in a different location on your MVS system connect to the z/OS system.
or renamed to a different data set member name.
User response: Explanation
Delete the stored procedure from the Data
{0}
Development project and re-create the stored
The name of a remote z/OS system.
procedure. If the source file is available on the remote
system, copy the source file to the location of the an edit or deploy operation for a stored procedure was
default source file that was created by the Stored requested, but the MVS system that is associated with
Procedure Creation Wizard. the stored procedure is not connected. The source file
cannot be accessed.
CRRZI8505E The z/OS system definition for '{0}'
does not exist. Switch to the z/OS User response:
Projects perspective and define in the Remote Systems Explorer, connect to the
'{0}' as a z/OS system with the remote system. Try the operation again.
appropriate IP address.

Troubleshooting and support 117

CRRZI8509E The volume '{0}' is offline. Contact An attempt was made to open the file as a stored
your systems programmer to bring procedure, but the file is open in another edit session.
the volume online. User response:
Close the editor and try the operation again.
Explanation
CRRZI8511W The stored procedure already
{0} exists. Replace the existing stored
The name of a data set. procedure?
The stored procedure source is in a data set that is Explanation:
offline or migrated. An attempt was made to save a stored procedure with
User response: the same name as an existing stored procedure.
Contact your systems programmer to bring the volume User response:
online. Click Yes to replace the existing stored procedure or
CRRZI8510I The selected file '{0}' is already No to return to the editor. Save the stored procedure
open in another edit session. Close with a different name.
the edit session before opening
this file as a stored procedure.

Explanation
{0}
A file name.

9000-level messages
CRRZI9501W There is 1 line with contents editor positions the file at the first line that exceeds
that exceed the maximum line the record length limit.
length. Saving the file will result in
CRRZI9503W The source has been modified
truncation of this line. Do you want
since the backup copy was saved.
to continue?
Explanation:
Explanation:
The client has an autosave function that creates a
Whenever you save a file in the z Systems LPEX Editor,
backup copy of editor files on the local system. This
COBOL Editor, or PL/I Editor, it checks for any lines
warning indicates that the backup copy created by an
that exceed the record length limit. This warning opens
autosave operation is based on an earlier copy of the
when a line in the file exceeds the record length limit.
source. The backup copy is opened in the editor.
User response:
User response:
Click Yes to continue with the file save operation or No
Use File > Save As to save the backup to a different
to return to the editor to fix the line in question. The location and then use the compare tool to merge
editor positions the file at the line that exceeds the changes from the backup with the source.
record length limit.
CRRZI9504I A backup copy from {0} exists
CRRZI9502W There are {0} lines with contents for the source you are opening.
that exceed the maximum line This occurred when your previous
length. Saving the file will result editing session ended abnormally.
in truncation of these lines. Do you Do you want to open the backup
want to continue? copy in the editor?
Explanation: Explanation:
Whenever you save a file in the z Systems LPEX Editor, The client has an autosave function that creates a
COBOL Editor, or PL/I Editor, it checks for any lines backup copy of editor files on the local system.
that exceed the record length limit. This warning opens
when more than one line in the file exceeds the record User response:
length limit. Click Yes to open the backup copy.
User response: CRRZI9505W The file cannot be saved on the
Click Yes to continue with the file save operation or No host system. A backup copy has
to return to the editor to fix the lines in question. The been created locally. You will be
prompted to restore from this

118 Developer for z/OS: Troubleshooting and Support

 backup file the next time you open Click Yes to update the contents in the z Systems
the remote file. LPEX Editor. Click No to keep the current contents
of the editor. If you save the file without refreshing
Explanation:
the contents, the changes that are made in the other
The client has an autosave function that creates a
editor are lost.
backup copy of editor files on the local system. This
warning indicates that a backup copy is created for a CRRZI9507W Host RSE threadpool, process id
file that cannot be saved on the remote system. nnnn, is experiencing a timeout in
a connection request.
User response:
No action is required. Explanation:
The thread pool hosting the current client connection
CRRZI9506W The file has been changed on
is experiencing a timeout in handling a new connection
the file system. Do you want to
request. Its status is changed to timeout.
replace the z Systems LPEX Editor
contents with these changes? Explanation:
The thread pool may have encountered a resource
Explanation:
limit or a technical issue. Save your current
A file was changed in another editor on the file system.
tasks and prepare to log out. Tuning RSE server
Its contents no longer match the contents that are
might help address resource limit issues. For more
shown in the z Systems LPEX Editor.
information about tuning the RSE server, see the Host
User response: Configuration Reference Guide.

Messages for the JES Job Monitor

These messages pertain to the Job Entry System (JES) Job Monitor.
CRRZI0072E The job submission failed because User response
the job card is incomplete or You can choose from the following two options for
invalid. Verify the job card and displaying job output:
submit the job again.
• Show output from the first line to line number:
CRRZI9001I This job output contains {0} lines. Choose this option to open a portion of the job
Specify the starting line and output. Specify a line number in the input field to
number of lines to retrieve. open output from line 1 to the line number entered.
Explanation: • Show the complete job output: Choose this option
This message displays as a result of the Open from to open the complete job output.
line action in the Remote Systems view. It shows the
CRRZI9003E Unable to connect to the JES Job
number of lines in the currently selected job output.
Monitor on port {1} of host {0}.
It also prompts you to enter the starting line and the
number of lines of the job output to display. Explanation:
The client was unable to establish a connection to
User response:
JES on the port number shown on the remote system
Type the starting line number in the Retrieve output
(host) shown.
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 User response
example, type 500 in the Retrieve output starting at
1. Verify with your system administrator that the
line field and 100 in the Number of lines to retrieve
remote system is available and that the JES Job
field and click OK.
Monitor is installed and running.
CRRZI9002I This job output contains {0} lines, 2. Open the JES properties page by selecting JES
which exceeds your specified job in the Remote Systems view and then selecting
output retrieval limit. How do you Properties. Verify with your system administrator
want to proceed? that the correct port is specified.
Explanation: CRRZI9004E Not authorized for job {0}.
This message displays when you request to open job
output for a job whose number of lines exceeds the Explanation:
Max Number of Lines to Download setting in the JES You are not authorized to do the requested action for
preferences. It prompts you to specify how you want the job number shown.
to open the output.

Troubleshooting and support 119

User response: Wait for the job to complete or select another job and
Verify that you selected the correct job ID. Select a try again.
job that you are authorized to do the action on and try
CRRZI9012E The entry for Job output class is
again.
an empty string.
CRRZI9005I Cancel has been issued for job {0}.
Explanation:
Explanation: The Job output class field on the New JES Job Filter
A Cancel action was issued for the job ID shown. window is required, but this field is empty.
User response: User response:
No action is required. Specify a value in the Job output class field.
CRRZI9006E Job {0} cannot be canceled. CRRZI9013E The entry for Job owner is invalid.
Explanation: Explanation:
A Cancel action was issued for the job ID shown, but The Job 0wner field on the New JES Job Filter
the job is complete. window is required, but this field is empty or the value
specified is not valid.
User response:
No action is required. User response:
Specify a value in the Job owner field. To specify the
CRRZI9007E The entry for Job class is an empty
user ID with which you logged in to the remote system,
string.
specify &USERID.
Explanation:
CRRZI9014E The entry for Job name prefix is an
The Job class field on the New JES Job Filter window
empty string.
is required, but this field is empty.
Explanation:
User response:
The Job name prefix field on the New JES Job Filter
Specify a value in the Job class field.
window is required, but this field is empty.
CRRZI9008I Hold has been issued for job {0}.
User response:
Explanation: Specify a value in the Job name prefix field.
A Hold action was issued for the job ID shown.
CRRZI9015I Print has been issued for job {0}.
User response:
Explanation:
No action is required.
A Print action was issued for the job ID shown.
CRRZI9009W No information is available for job
User response:
{0}. Unable to update the status.
No action is required.
Explanation:
CRRZI9016I Purge has been issued for job {0}.
A Refresh Status action was issued for the selected
job, but no information is available. The job might be Explanation:
complete. A Purge action was issued for the job ID shown.
User response: User response:
No action is required. No action is required.
CRRZI9010W No jobs match the search criteria. CRRZI9017I Release has been issued for job
{0}.
Explanation:
A filter string entered into the Retrieve Job window Explanation:
resulted in no matches. A Release action was issued for the job ID shown.
User response: User response:
Enter another filter string and try again. No action is required.
CRRZI9011W No output for job {0}. CRRZI9018I Restart has been issued for job {0}.
Explanation: Explanation:
An Open action for the job ID shown failed because A Restart action was issued for the job ID shown.
the job produced no output or is not yet complete.
User response:
User response: No action is required.

120 Developer for z/OS: Troubleshooting and Support

CRRZI9019E The entry for Job status is an Explanation
empty string. The Job Monitor server and the RSE JES Miner were
Explanation: unable to negotiate an acceptable command protocol
The Job status field on the New JES Job Filter level.
window is required, but this field is empty. {0}
The server protocol level that is unsupported.
User response:
Specify a value in the Job status field. User response:
Either the Job Monitor server (load module FEJJMON)
CRRZI9020E Login failed. The user ID or
or the RSE JES Miner (jesminers.jar) is not at the
password is incorrect.
latest level. Make sure that you correctly installed
Explanation: these components.
An attempt to log on to the JES subsystem failed
CRRZI9026E Unexpected RACF error
because the password specified is incorrect.
encountered.
User response:
Explanation:
Specify a different password and try again.
A RACF error occurred while attempting to log on to
CRRZI9021E The entry for the maximum the remote system.
number of lines to download ({0})
User response:
is invalid.
Contact your system administrator.
Explanation:
CRRZI9027I The session has been idle more
The value specified in the Max Number of Lines to
than {0} seconds. The connection
Download field of the Properties for JES window is
has been terminated.
invalid.
Explanation:
User response:
The connection to the remote system ended because
Specify a value 1 - 2147483647.
of inactivity.
CRRZI9022E The password has expired.
User response:
Explanation: Connect to the remote system again.
Your password for the remote system to which you are
CRRZI9028E Unable to allocate session code
trying to connect expired.
page conversion ({0}). Continue
User response: using default conversion.
Enter a new password when prompted. If you are
Explanation:
not able to reset your password, contact your system
The Job Monitor server (JMON) attempted to allocate
administrator.
a code page converter, but the allocation failed.
CRRZI9023E The new password is not valid.
User response:
Reenter a valid password.
Make sure that enough memory is available to the Job
Explanation: Monitor server (JMON).
The password entered does not match the security
CRRZI9029E Unable to set the JES Job Monitor
requirements of your site.
host code page to {0}. Continuing
User response: with the default host code page.
Consult with your system administrator to obtain valid
password requirements and try again.
Explanation
CRRZI9024E The entry for port {0} is invalid. The host code page cannot be set to the value
specified in the system code page mapping.
Explanation:
The value specified in the JES Job Monitor Port field {0}
of the Properties for JES window is invalid. A host code page.
User response: User response:
Consult your system administrator for the correct port Check that the JMON job is running on the host, and
number and try again. that it is at the correct level.
CRRZI9025E Unsupported server protocol level
{0}.

Troubleshooting and support 121

 Messages for Deep Program Analysis Tools for COBOL and PL/I
These messages pertain to the common program analysis tools for deep program analysis of COBOL and
PL/I code.
CRRZJ0001I No unreachable code was CRRZJ0006I Unreachable code calculation is
detected in the program. based on source analysis and not
on the compiler results. You may
Explanation:
want to verify the results for
The Source > Identify Unreachable Code action was
your program before taking further
requested, but the file contains no unreachable code.
action.
User response:
Explanation:
No action is required.
Because the Identify Unreachable Code feature uses
CRRZJ0002E The view cannot be opened a static analysis of the program source to identify
because the program cannot potential dead code, it is not a reflection of the actual
be parsed or parsing has not execution path.
completed.
Explanation: User response
The Open Program Control Flow function was Before you delete any code, verify that the code is
requested in the COBOL Editor or z Systems LPEX correctly identified as unreachable.
Editor. This function uses an internal COBOL parser to
This message is displayed each time that you use the
analyze program control flow in a source file. Either the
Identify Unreachable Code function. To prevent this
analysis cannot be completed because of syntax errors
message from being displayed, click Do not show this
in the source file, or the analysis is still in progress.
message again.
User response:
CRRZJ0007E The program can not be analyzed
Check for syntax errors in the file. Correct the errors,
for unreachable code because it
and try the operation again.
cannot be parsed.
CRRZJ0003E An unexpected error was found
Explanation:
while selecting a diagram node in
The Identify Unreachable Code function was
the Program Control Flow view.
requested in the COBOL Editor or z Systems LPEX
Explanation: Editor. This function uses an internal COBOL parser
An internal error occurred in the Program Control Flow to analyze a source file. The analysis cannot be
diagram. completed because of syntax errors in the source file.
User response: User response:
Try the operation again. If the problem persists, Check for syntax errors in the file. Correct the errors,
contact IBM Software Support. and try the operation again.
CRRZJ0004E An unexpected error was found CRRZJ0008E Unexpected internal error found:
while opening the view. {0}. Additional information may be
written to trace if enabled.
Explanation:
An internal error occurred during a request to open the
Program Control Flow view. Explanation
User response: {0}
Try the operation again. If the problem persists, An internal code location to help identify the
contact IBM Software Support. source of the error. This code location might be
accompanied by more log or trace messages.
CRRZJ0005E An unexpected error was found
while analyzing the program for An internal error occurred during a request to show the
unreachable code. source file in the Data Elements view.

Explanation:
An internal error occurred during an Identify User response
Unreachable Code request • Examine the log and trace files for error messages.
User response: The product log and trace files are in the .metadata
Try the operation again. If the problem persists, folder of the workspace path. To see the path name
contact IBM Software Support. of the workspace, click File > Switch Workspace >

122 Developer for z/OS: Troubleshooting and Support

 Other. The Launch Workspace window opens and • Copy books that are associated with the open file are
displays the path of the current workspace. not included in the program analysis. The analysis
• To turn on tracing for the deep code analysis feature: works within the boundary of the file.
• Quick fix is not available.
1. Open the Tracing preference page.
• Not available for programs that contain the following
2. In the Tracer Name column, select
statements:
com.ibm.systemz.common.analysis.
3. In the Tracing Level column, choose a tracing – EXEC CICS HANDLE
level option. – EXEC CICS IGNORE
CRRZJ0009E An unexpected error was found – EXEC CICS PUSH
while updating the view. – EXEC CICS POP
Explanation: – EXEC SQL WHENEVER
An internal error occurred in the Program Control Flow • CALL statements that do not return to the calling
diagram. program can result in results that are not correct.
User response: Statements after a CALL statement are not marked
Try the operation again. If the problem persists, as unreachable.
contact IBM Software Support. • Unreachable code is reported on a per line basis. If
a line contains both code that is reachable and code
CRRZJ0010W Program Control Flow diagram
that is unreachable, the reported results might be
may not be accurate for this
incorrect. Use the COBOL formatting tool to enforce
program because it contains one
the one-verb-per-line rule to prevent reachable and
of the following unsupported
unreachable code in the same line.
statements: EXEC CICS HANDLE,
EXEC CICS IGNORE, EXEC CICS User response:
PUSH, EXEC CICS POP, and EXEC Use the Identify Unreachable Code function in
SQL WHENEVER. programs that do not contain these statements.
CRRZJ0102E The Data Flow view cannot be
Explanation opened because the program
The program control flow diagram does not display cannot be parsed or parsing has
control flow nodes for control transfers that are not completed.
generated by the following statements:
CRRZJ0103E An unexpected error was found
• EXEC CICS HANDLE while selecting a diagram node in
• EXEC CICS IGNORE the Data Flow view.
• EXEC CICS PUSH CRRZJ0104E An unexpected error was found
• EXEC CICS POP while opening the Data Flow view.

• EXEC SQL WHENEVER CRRZJ0109E An unexpected error was found

while updating the Data Flow
User response: view.
Use the Show In > Program Control Flow function in
programs that do not contain these statements. CRRZJ0110E A data flow cannot be computed
for the current selection. Select a
CRRZJ0011E The unreachable code feature data element.
does not support programs
containing the following CRRZJ0111E The program contains a statement
statements: EXEC CICS HANDLE, that is not yet supported. A data
EXEC CICS IGNORE, EXEC CICS flow cannot be computed.
PUSH, EXEC CICS POP, and EXEC
SQL WHENEVER.

Explanation
The Identify Unreachable Code function has several
restrictions:

Troubleshooting and support 123

 Messages for MFS Screen Designer (MFS Map Editor)
These are the messages that pertain to the MFS Screen Designer (MFS Map Editor).

0100-level messages
CRRZM0159E The input is not valid. CRRZM0164E The column is null.
Explanation: Explanation:
The input is not valid. You must define at least one column.
User response: User response:
Remove the invalid input, and provide valid input. Define one or more columns.
CRRZM0161E The inital value not valid. CRRZM0165E The length of the group name is
not valid.
Explanation:
The initial value that was provided is not valid. Explanation:
The group name entered is too long or short.
User response:
Remove the invalid initial value, and provide a valid User response:
initial value. Enter a shorter or longer group name.
CRRZM0162E The row is null. CRRZM0177E An error occurred while parsing
the source.
Explanation:
The row value in the definition of a new MFS Device Explanation:
field was left null. A syntax error in the source caused an error.
User response: User response:
Provide a row value when defining a new MVS Device Open the Source Page and modify the source so that
field. the error is resolved.
CRRZM0163E The position is not valid. CRRZM0178E An invalid name was specified.
Explanation: Explanation:
The selected position is not within the map The specified name is either invalid or empty.
boundaries.
User response:
User response: Specify a valid name.
Select a position that is within the map boundaries.

0200-level messages
CRRZM0241E File container must be specified The file name is required to perform the process.
Explanation: User response:
The location for the destination of a process is not Specify a valid file name.
specified. CRRZM0243E File extension must be mfs
User response: Explanation:
Provide the destination location for the process. The file extension is not correct.
CRRZM0242E File name must be specified User response:
Explanation: Change the file extension to mfs.

0300-level topics
CRRZM0323E Device format name is not valid. The device name is missing.
Explanation: User response:
The device format name is not defined or not correct. Enter a valid device format name.
User response: CRRZM0325E The message definition name is
Enter a valid device format name. not valid.
CRRZM0324E The device format name is null. Explanation:
The message definition name is not defined or not
Explanation: correct.

124 Developer for z/OS: Troubleshooting and Support

User response: CRRZM0333E A duplicate file name has been
Enter a valid message definition name. specified.
CRRZM0326E The message definition name is Explanation:
null. The file name entered is already in use.
Explanation: User response:
The message definition name is missing. Enter a different file name.
User response: CRRZM0350E No column has been defined.
Enter a valid message definition name.
Explanation:
CRRZM0331E The file name is null. Table does not have a defined column.
Explanation: User response:
A file name cannot be null. Select a valid column or insert a column into the table.
User response: CRRZM0370E The total width exceeds the
Specify a file name that is not null. defined table width.
CRRZM0332E The file name is not valid. Explanation:
Size of insert is greater than table width..
Explanation:
The file name used is not correct. User response:
Insert a smaller selection.
User response:
Change the file name.

0400-level messages
CRRZM0437E The width value is not valid. It Enter a literal value of less than 255 characters.
must be in the range 1-120.
CRRZM0453E An extended attribute value is not
Explanation: between 1 and 10.
The width value is not valid.
Explanation:
User response: An extended attribute value is not in the range 1-10.
Enter a valid value in the range of 1-120.
User response:
CRRZM0438E The Features value is not set. Specify an extended attribute value in the range 1-10.
Explanation: CRRZM0454E The length of the value does not
The features value is missing. equal the field length.
User response: Explanation:
Enter a valid features value. The length of the value does not equal the field length.
CRRZM0450E The exit number value is not valid. User response:
Enter a valid length value.
Explanation:
The exit value i snot defined or not correct. CRRZM0455E The field length is 0.
User response: Explanation:
Enter a valid exit number value. The length of the value does not equal the field length.
CRRZM0451E The exit vector value is not valid. User response:
Enter a valid length value.
Explanation:
The exit vector value is missing. CRRZM0456E The row is null.
User response: Explanation:
Enter a valid exit vector value. You must define at least one row.
CRRZM0452E A literal is longer than 255 User response:
characters. Define one or more rows.
Explanation: CRRZM0457E The column is null.
The literal value is over 255 characters. Explanation:
User response: You must define at least one column.

Troubleshooting and support 125

User response: The path to the field is not valid or the file name is not
Define one or more columns. valid.
CRRZM0458E The field position is not valid. User response:
Verify both the path to the file and the file name.
Explanation:
The entry used is not correct. CRRZM0471E An error occurred when opening
the file.
User response:
Change or delete the field position value. Explanation:
An error occurred that kept the file from opening.
CRRZM0459E The value of the offset is not valid.
User response:
Explanation:
This message is the header to additional messages.
The entry is not correct.
See the documentation for the additional message.
User response:
CRRZM0474E Invalid character {0} was found
Change or delete the offset value.
after {1} at line {2} and column
CRRZM0460E An invalid division name was {3}..
entered.
Explanation:
Explanation: The character you entered is not allowed at the
The entry used is not correct. indicated location.
User response: User response:
Change or delete the division name value. Change or delete the character.
CRRZM0463E The value of PAGE is not valid. CRRZM0475E The editor failed to parse
statement {0} at line {1} column
Explanation:
{2}.
The entry used is not correct.
Explanation:
User response:
A parse error was found at the indicated location.
Change or delete the PAGE value.
User response:
CRRZM0464E The value entered for Device Field
Change or delete the parse statement.
cannot be used.
CRRZM0477E A lexical error was encountered at
Explanation:
line {0} and column {1}.
The entry used is not correct.
Explanation:
User response:
A lexical error was found at the indicated location.
Change and delete the Device Field value.
User response:
CRRZM0465I The COPY keyword is not
Change or delete the character.
supported.
CRRZM0480E An invalid location is selected.
Explanation:
The COPY keyword is not supported. Explanation:
The location that is selected is not valid.
User response:
Remove any instance of the COPY keyword. User response:
Select a valid location.
CRRZM0467I The selected statement cannot be
edited. It is read-only. CRRZM0481E An invalid field name is entered.
Explanation: Explanation:
The statement is a read-only statement and cannot be The field name that is entered is not valid.
modified.
User response:
User response: Enter a valid field name.
No action required.
CRRZM0482I A copybook file was created.
CRRZM0470E Copy file {0} was not found at the
Explanation:
specified location.
The requested copybook file was created successfully.
Explanation:
User response:
No action required.

126 Developer for z/OS: Troubleshooting and Support

CRRZM0483I The copybook file has been Names in MFS must be unique, and the name that is
created. specified is not unique.
Explanation: User response:
The requested copy book file was created successfully. Modify the name that you entered to be unique.
User response: CRRZM0490E Device Page cannot accept
No action required. multiple physical pages.
CRRZM0484E The file name is not valid. Explanation:
A physical page was attempted to be created on a
Explanation: device page that already had a single physical page
A file name was specified that is not valid. and did not specify the MULT=YES attribute.
User response: User response:
Specify a valid file name. To specify that the device page can accept multiple
CRRZM0485E EGCS value range should be physical pages, select the device page in the outline
between X'40' and X'FE' view. In the properties view, mark the Multiple
physical pages checkbox. The MULT=YES attribute is
Explanation: added to the device page in the source and physical
The EGCS value that was provided does not fall within pages can be added without error.
the range X'40' and X'FE'.
CRRZM0491E The file type is invalid. Please
User response: select a valid MFS file.
Change the EGCS value so that it falls within the range
X'40' and X'FE'. Explanation:
The file that is selected as the target for the created
CRRZM0486E Programmed Symbol value range MFS message is not a correctly formatted MFS file.
should be between X'40' and X'FE'
User response:
Explanation: Select a file that has a MFS extension and contains no
The Programmed Symbol value range that was parse errors when opened with the MFS editor.
provided does not fall within the valid range of X'40'
and X'FE'. CRRZM0492E MFS Message cannot be created
because the selected file has
User response:
syntax errors.
Change the Programmed Symbol value range so that it
falls within the range of X'40' to X'FE'. Explanation:
The file that is selected as the target for the MFS
CRRZM0487E Fill value is invalid. Enter a valid message creation contains syntax errors. Syntax errors
HEX value in the MFS source prevent the MFS message from
Explanation: being appended to the file.
The FILL value that is specified violates the valid User response:
format. Open the file in the MFS editor, view the source page,
User response: and correct any syntax errors. After you correct any
Replace the specified fill value with a correctly syntax errors, save the file and try creating the MFS
formatted hex value, for example FILL X'00'. message again.
CRRZM0488E Fill value is invalid. Enter a valid CRRZM0493E Field will overlap an existing field
Fill character in the specified Physical Page
Explanation: Explanation:
The FILL value that is specified violates the valid A field is modified with new a new location that,
format. if placed, will overlap with an existing field in the
specified physical page. This overlap can happen when
User response: the row, column, or physical page attributes of a field
Replace the specified fill value with a correctly are updated.
formatted character, for example FILL C'c'.
User response:
CRRZM0489E A duplicate name has been Correct the position attribute, or attributes, that
specified. causes the overlap.
Explanation: CRRZM0494E The copybook generation for this
MFS file failed.

Troubleshooting and support 127

 Messages for Common Access Repository Manager (CARMA) Endevor
The following messages pertain to Common Access Repository Manager (CARMA) Endevor.
CRRZR1001E Unsupported editor input type. Explanation:
The file is not valid SCL and cannot be opened by the
Explanation:
CA Endevor Package Editor.
The input type is an unsupported type for the
CA Endevor Package Editor. The Endevor Package User response:
Editor requires any custom editor to implement If you believe that the file is valid SCL, open the file in
org.eclipse.ui.IStorageEditorInput. the text editor by right-clicking the file and selecting
Open With > Text Editor. Fix any errors before you
User response:
open the files again in the Endevor Package Editor.
Change the input type to a type that is
supported by the CA Endevor Package Editor. CRRZR1004E The Endevor search failed. Ensure
If you are working on a custom client, that you are connected to the host
contact your client developer to investigate and that the host is running a
whether the package editor is implementing current version.
org.eclipse.ui.IStorageEditorInput.
Explanation:
CRRZR1002E The Endevor Package Editor was The Endevor search did not complete successfully.
unable to open the source for
System programmer response:
reading.
Verify that the current version of the Endevor RAM is
Explanation: installed and running on the remote system.
The source file was not open and read successfully.
User response:
User response: Verify that you are connected to the remote system. If
In the client, close the file and try again. If the problem the problem persists, contact the system programmer.
persists, restart the workbench.
CRRZR1003E The Endevor Package Editor was
unable to parse the source into
valid SCL.

Messages for Code Review for COBOL and PL/I

These are the messages that pertain to Code Review for COBOL and Code Review for PL/I.
CRRZV0000E The COBOL source file could not be User response:
closed: {0}. Error message: {1} Verify that the COBOL source code file does not
contain any syntax errors, and then try running the
code review again.
Explanation
CRRZV0002E The backup of the launch
{0}
configuration file failed: {0}. Error
File name
message: {1}
{1}
Exception message
Explanation
User response:
{0}
Verify that other program is using the COBOL source
File name
code file, and then try running the code review again.
{1}
CRRZV0001E An error occurred during the Exception message
parsing of the COBOL source file
{0}. Error message: {1} User response:
Verify that no other program is using the launch
configuration file. Restart the product and accept the
Explanation
push-to-client updates if prompted.
{0}
CRRZV0003E The launch configuration files
File name
could not be copied. Error
{1} message: {0}
Exception message

128 Developer for z/OS: Troubleshooting and Support

Explanation {2}
Exception message
{0}
Exception message User response:
Verify that no other program is using the launch
User response: configuration file. Restart the product and accept any
Verify that no other program is using the launch push-to-client updates if prompted.
configuration files. Restart the product and accept any
push-to-client updates if prompted. CRRZV0008E A metadata collector plug-in could
not be loaded. Error message: {0}
CRRZV0004E The export of the launch
configuration files failed. Error
message: {0} Explanation
{0}
Explanation Exception message
{0} User response:
Exception message Restart the product. If the problem persists, contact
your system administrator.
User response:
Verify that no other program is using the launch CRRZV0009E The following files contained
configuration files. Then try exporting the launch syntax errors and were not
configuration files again. processed.
CRRZV0005E The launch configuration files Explanation:
could not be loaded. Error The code review program detected syntax errors in the
message: {0} specified COBOL source code files.

Explanation User response

{0} 1. If you need more information about the
Exception message error, see the Error Log view or the log file
workspace\.metadata\.log, where workspace is the
User response:
name of your workspace.
Verify that no other program is using the launch
configuration files. Restart the product and accept any 2. Fix the syntax errors in the specified COBOL source
push-to-client updates if prompted. files and then try running the code review again.

CRRZV0006E An error occurred during the CRRZV0010I {0} reports the result: {1}
refreshing of the local workspace.
Error message: {0} Explanation
{0}
Explanation A rule provider
{0} {1}
Exception message A Software Analyzer result
User response: When the -verbose parameter is used, this message is
Verify that no other program is using files in the local written to the workspace log when a Software Analyzer
workspace, then try running the code review again. result is found. The -verbose parameter is enabled by
CRRZV0007E The following launch configuration default in sample Windows scripts and the z/OS REXX
file could not be copied: {0} The front-end.
copy destination is: {1} The error User response:
message is: {2}. Use the information in this message to recover results
if a batch code review process fails or is terminated.
Explanation CRRZV0100E The PL/I source file could not be
{0} closed: {0}. Error message: {1}
File name
{1}
File name

Troubleshooting and support 129

Explanation User response
{0} 1. Determine whether the failing program fragment
Source file contains one of the documented limitations
{1} of the COBOL Application Model API. For
Exception message more information see the technote "The
COBOL Application Model (CAM) API in
User response: Code Review for COBOL: Limitations in
Verify that no other program is using the PL/I source Version 8.5.0.1" at http://www.ibm.com/support/
code file, and then try running the code review again. docview.wss?uid=swg21598204.
CRRZV0101E An error occurred during the 2. If the fragment does not contain a documented
parsing of the PL/I source file {0}. limitation, and if the problem persists, contact your
Error message: {1} system administrator.
CRRZV0203E An error occurred during the
Explanation translation of the procedure
{0} division to the Cobol Application
PL/I source file Model: ({0})

{1}
Exception message Explanation
User response: {0}
Verify that the PL/I source code file does not contain Exception message
any syntax errors, and then try running the code review
again. User response
CRRZV0201E An error occurred during the 1. Determine whether the failing program fragment
translation of data to the Cobol contains one of the documented limitations
Application Model: ({0}) of the COBOL Application Model API. For
more information see the technote "The
Explanation COBOL Application Model (CAM) API in
Code Review for COBOL: Limitations in
{0} Version 8.5.0.1" at http://www.ibm.com/support/
Exception message docview.wss?uid=swg21598204.
2. If the fragment does not contain a documented
User response limitation, and if the problem persists, contact your
1. Determine whether the failing program fragment system administrator.
contains one of the documented limitations CRRZV0204E An exception was thrown during
of the COBOL Application Model API. For the translation of the following
more information see the technote "The statement to the Cobol Application
COBOL Application Model (CAM) API in Model: {0}
Code Review for COBOL: Limitations in
Version 8.5.0.1" at http://www.ibm.com/support/
docview.wss?uid=swg21598204. Explanation
2. If the fragment does not contain a documented {0}
limitation, and if the problem persists, contact your Statement
system administrator.
CRRZV0202E An error occurred during the
User response
translation of the environment 1. Determine whether the failing program fragment
division to the Cobol Application contains one of the documented limitations
Model: ({0}) of the COBOL Application Model API. For
more information see the technote "The
Explanation COBOL Application Model (CAM) API in
Code Review for COBOL: Limitations in
{0} Version 8.5.0.1" at http://www.ibm.com/support/
Exception message docview.wss?uid=swg21598204.

130 Developer for z/OS: Troubleshooting and Support

2. If the fragment does not contain a documented COBOL Application Model (CAM) API in
limitation, and if the problem persists, contact your Code Review for COBOL: Limitations in
system administrator. Version 8.5.0.1" at http://www.ibm.com/support/
docview.wss?uid=swg21598204.
CRRZV0205E An error occurred during the
translation of an expression to the 2. If the fragment does not contain a documented
Cobol Application Model: ({0}) limitation, and if the problem persists, contact your
system administrator.
Explanation CRRZV0207E A statement contains a reference
that could not be translated to
{0}
the COBOL Application Model. The
Exception message
statement is: {1}. The reference is:
{0}
User response
1. Determine whether the failing program fragment Explanation
contains one of the documented limitations {0}
of the COBOL Application Model API. For Reference
more information see the technote "The
COBOL Application Model (CAM) API in {1}
Code Review for COBOL: Limitations in Statement
Version 8.5.0.1" at http://www.ibm.com/support/ User response:
docview.wss?uid=swg21598204. Verify that the program does not contain unresolved
2. If the fragment does not contain a documented references. Verify that all the required copy books are
limitation, and if the problem persists, contact your present. Then try running the code review again.
system administrator.
CRRZV0208E Unable to resolve reference '{0}' in
CRRZV0206E An exception was thrown '{1}'
during the translation of the
following expression to the Cobol Explanation
Application Model: {0}
{0}
The name of a data element.
Explanation
{1}
{0} The name of the program with the unresolved data
Expression element reference.
The parser cannot locate the declaration of a data
User response element in a program.
1. Determine whether the failing program fragment User response:
contains one of the documented limitations Verify that the program does not contain unresolved
of the COBOL Application Model API. For references. Verify that all the required copy books are
more information see the technote "The present. Then try running the code review again.

Messages for TPF Toolkit Core

These are the messages that pertain to TPF Toolkit Core.

1000-level messages
TPFC1001E The file name field for {1} is empty. TPFC1002E The file name field for {1} is not
unique.
Explanation
{1}
Explanation
File name {1}
File name
User response:
User response:

Troubleshooting and support 131

TPFC1003E The file name field for {1} is User response:
invalid. TPFC1006E The file cannot be created. The
parent folder is not valid.
Explanation Select a valid parent folder.
{1} Explanation:
File name
User response:
User response:
TPFC1007I File creation has been cancelled.
TPFC1004E The selected file {1} is not remote.
Explanation:
You cannot set remote properties
on a local file. User response:
TPFC1008W A file by the name of {1} already
Explanation exists. Do you want to overwrite
{1} the existing file with the build
File name script you are generating?

User response:
Explanation
TPFC1005E The selected file {1} is not a TPF
{1}
DLL configuration file.
File name
The file is probably a dynamic link
library. User response:
TPFC1010E Error creating file.
Explanation
Explanation:
{1}
File name User response:

2000-level messages
TPFC2001E The field {1} must be numeric. The value must be between 0 and
32767, exclusive.
Explanation
Explanation
{1}
The content of the field {1}
The content of the value
User response:
User response:
TPFC2002E The LINECOUNT value is invalid.
The value must be 0, or between TPFC2100E No fields included.
10 and 32767, inclusive. Select one or more fields to be
written to the output file.
Explanation:
Explanation:
User response:
User response:
TPFC2003E The N field value is invalid.
The value must be numeric or "*" TPFC2101E No line-specific fields included.
(asterisk). Operation will continue with file
information only. Select one or
Explanation: more line-specific field.
User response: Explanation:
TPFC2004E M value must be less than N value. User response:
Explanation: TPFC2102E Unknown error occured while
User response: writing to file {1}.
Ensure the file can be accessed.
TPFC2005E The {1} value is invalid.

132 Developer for z/OS: Troubleshooting and Support

Explanation {2}
File name
{1}
File name User response:
User response: TPFC2104E Action unavailable - Remote
Search view contains no results.
TPFC2103I Successfully wrote {1} messages
to file {2} Explanation:
User response:
Explanation
{1}
The content of the message

3000-level messages
TPFC3000I Filter name cannot be empty. {2}
File name
Explanation:
{3}
User response: The name of a remote system
TPFC3001E Filter name is not unique. User response:
Filter names must be unique.
TPFC3005E None of the {1} XML files in the
Explanation: folder {2} contain valid {3} file
User response: content.
Select a folder that represents a
TPFC3002E Filter name is not valid. z/OS UNIX {4} and contains a {3}
Explanation: file with valid content.

User response:
Explanation
TPFC3003E The folder {1} does not contain a
valid {2} file. {1}
Select a folder that represents a The name of an XML file
z/OS UNIX {3} and contains a {2} {2}
file with valid content. Folder name
{3}
Explanation File name
{1} {4}
Folder name The name of a remote system
{2} User response:
File name TPFC3006E The folder {1} does not represent
{3} a z/OS UNIX subproject. It has no
The name of a remote system {2} file and no child z/OS UNIX
Filter folders.
User response:
Select a folder that has a {2} file or
TPFC3004E The file {1} does not contain has child folders with a {3} file in
content that is valid for them.
representing a z/OS UNIX {3}.
Select a folder that represents a
Explanation
z/OS UNIX {3} and contains a {2}
file with valid content. {1}
Folder name
Explanation {2}
File name
{1}
File name {3}
File name

Troubleshooting and support 133

User response: Explanation
TPFC3007E The folder {1} does not represent a {1}
subproject. Folder name
Select a folder that represents
{2}
a z/OS UNIX subproject. Folders
File name
that represent subprojects contain
a {2} file. {3}
The name of an HFS folder
Explanation User response:
{1} TPFC3050I Filter string cannot be empty.
Folder name Explanation:
{2}
User response:
File name
TPFC3051E There is already an identical filter
User response:
string in the filter.
TPFC3008E The subproject {1} is not a z/OS Change the path or file name
UNIX subproject. pattern to make the filter string
Select a folder that was created by unique.
exporting a z/OS UNIX subproject.
Explanation:

Explanation User response:

{1} TPFC3052E Filter string is invalid.

The name of a subproject Explanation:
User response: User response:
TPFC3009E The {1} in subproject {2} could not TPFC3053E An existing, broader filter exists.
be accessed. It will override the current filter
Ensure the {1} file exists and has information.
appropriate read permission.
Explanation:

Explanation User response:

{1} TPFC3054E Parent z/OS UNIX subproject must
File name be specified.
{2} Explanation:
The name of a subproject
User response:
User response:
TPFC3055W The filter string you are attempting
TPFC3010E TPF Toolkit v2 and v3 projects to add includes one or more files
cannot be selected in a single that are already included by an
import. existing filter string. If you add
this filter string, it will be merged
Explanation:
with the existing filter strings.
User response:
Explanation:
TPFC3011E A target environment must be
User response:
selected.
TPFC3056E There are already one or more
Explanation:
filter strings that include files from
User response: the same location with a different
user ID. You cannot include files
TPFC3012E The folder {1} does not contain a
from the same location with
valid {2} file.
different user IDs in the same
Select a folder that represents a
filter.
HFS {3} and contains a {2} file with
valid content. Explanation:

134 Developer for z/OS: Troubleshooting and Support

User response: Explanation
TPFC3060E Connection type is invalid. {1}
Explanation: Filter name

User response: User response:

TPFC3061E System name must be specified. TPFC3080E Files from {0} cannot be shown in
filter {1} with user ID {2} because
Explanation: they are already shown with user
User response: ID {3}.
Files from {0} cannot be shown in
TPFC3062E User name must be specified. filter {1} with user ID {2} because
Explanation: they are already shown with user
ID {3}.
User response:
TPFC3063E Path must be specified. Explanation
Explanation: {0}
The name of a remote system
User response:
{1}
TPFC3064E Path is invalid. Filter name
Explanation: {2}
User response: A user identifier
{3}
TPFC3065E File pattern must be specified.
A user identifier
Explanation:
User response:
User response:
TPFC3081W The files from {0} are already
TPFC3066E File pattern is invalid. shown in filter {1} under a
different parent.
Explanation:
The files from {0} are already
User response: shown in filter {1} under a
different parent. The existing and
TPFC3070E Filter creation failed.
new filter strings will be merged.
Explanation:
User response: Explanation
TPFC3071E Filter creation cancelled. {0}
The name of a remote system
Explanation:
{1}
User response: Filter name
TPFC3072E Error loading filter: {1} User response:
The filter could not be loaded. Its
filter.xml file may be corrupted. TPFC3082I All files and folders from {0} are
already shown in filter {1} by {2}.
All files and folders from {0} are
Explanation already shown in filter {1} by {2}.
{1} The new filter string will not be
Filter name added.

User response:
Explanation
TPFC3075E One or more filter strings in filter
{1} could not be resolved. {0}
The name of a remote system
{1}
Filter name

Troubleshooting and support 135

{2} {2}
A user identifier The error message returned by the failure
User response: User response:
TPFC3083W All files and folders from {0} are TPFC3087W Could not find some or all of the
included in {1} by the new filter files from {1}. {2}
string {2}.
All files and folders from {0} are Explanation
included in {1} by the new filter
string {2}. The existing filter string {1}
will be replaced with the new one. A list of remote system names
{2}
Explanation The error message returned by the failure

{0} User response:

The name of a remote system TPFC3100E Cannot paste into folder {1}
{1} because the folder does not exist.
Filter name Check that the folder has not been
{2} deleted from the file system.
The content of filter string
User response:
Explanation
{1}
TPFC3084I The filter {0} already contains a
Folder name
filter string {1}.
The filter {0} already contains a User response:
filter string {1}. The new filter
TPFC3101E Cannot paste {1} to folder {2}
string will not be added.
because {1} does not exist.
Check that the file has not been
Explanation deleted, renamed or moved on the
{0} file system since it was copied.
Filter name
{1} Explanation
The content of filter string {1}
User response: File name
{2}
TPFC3085W Could not find files from folder {1}
Folder name
on host {2}. {3}
User response:
Explanation TPFC3102E Error pasting {1} to folder {2}.
{1} Check that the parent folder exist
Folder name and has write access.
{2}
The name of a remote system Explanation
{3} {1}
The error message returned by the failure File name
User response: {2}
Folder name
TPFC3086W Could not show files from host {1}.
{2}. User response:
TPFC3103E Cannot paste items into filter
Explanation {1} because the filter does not
reference any folder.
{1}
The name of a remote system

136 Developer for z/OS: Troubleshooting and Support

 You must paste the filter strings User response:
or choose a filter that represents a
folder.

Explanation
{1}
Filter name

4000-level messages
TPFC4000W Remote working directory has not Explanation
been specified. Some actions may
{1}
not work.
A command
The subproject's remote working
directory cannot be empty. {2}
The message returned by the command
Explanation:
User response:
User response:
TPFC4055I Executed target environment user
TPFC4001E The subproject's remote working exit {1}. Return code was {2}
directory is invalid.
Explanation: Explanation
User response: {1}
TPFC4050E Subproject creation failed. A command
{2}
Explanation:
The message returned by the command
User response:
User response:
TPFC4051I Subproject creation cancelled.
TPFC4080E The subproject's build list is
Explanation: empty.
User response: Explanation:
TPFC4052E Error loading subproject: {1}. User response:
The subproject could not be
TPFC4081I Building {1} with {2}...
loaded. One or more of its filters
may be corrupted.
Explanation
Explanation {1}
The item being built
{1}
The name of the subproject {2}
The build action
User response:
User response:
TPFC4053I Executed subproject create user
exit {1}. Return code was {2} TPFC4082E {1} is already included in the build
list.
Explanation
Explanation
{1}
A command {1}
File name
{2}
The message returned by the command User response:
User response: TPFC4083E {1} cannot be added to the build
list.
TPFC4054I Executed filter create user exit {1}.
Only remote files with extension
Return code was {2}
{2} can be added to the build list.

Troubleshooting and support 137

Explanation Explanation
{1} {1}
File name The name of an action
{2} User response:
A list of file-name extensions; for example, *.c,
*.cpp, *.asm TPFC4090E The build item {1} could not be
found.
User response: The file may have been deleted.
TPFC4084I {1} has been successfully added to
the build list. Explanation
{1}
Explanation File name
{1} User response:
File name
TPFC4091E The build item {1} does not have
User response: an associated build action ID.
TPFC4085E Subproject Build List does not Check the subproject's build list
exist. and assign a build action to the
build item.
Explanation:
User response: Explanation
TPFC4086E Subproject Build failed. {1}
{1} File name
User response:
Explanation
TPFC4092W The build action with ID {1} could
{1} not be found. Now building with
Detailed messages for the build error default build action {2}.
User response:
TPFC4087I Subproject Build has been
Explanation
cancelled. {1}
An action identifier
Explanation:
{2}
User response: An action name or identifier
TPFC4088I Select the items to add to the build User response:
list.
Only remote files with extension TPFC4093E Unexpected exception occurred:
{1} can be added to the build list. Subproject is not valid.
Explanation:
Explanation User response:
{1}
TPFC4094I Building subproject using
A list of file-name extensions; for example, *.c,
subproject build list...
*.cpp, *.asm
Explanation:
User response:
User response:
TPFC4089E The build action with ID {1} could
not be found. TPFC4095E Build Actions List is Empty.
The action may have been deleted. Make sure you have defined a valid
Use the Menu Manager to create build action for the specified file
the action. type.
Explanation:
User response:

138 Developer for z/OS: Troubleshooting and Support

TPFC4096W Invalid build action found TPFC4104E Action failed. TPF Make control file
One or more build actions {1} cannot be found.
referenced in the build list are not
valid based on the menu option Explanation
of the current target environment.
Click OK to continue building the {1}
subproject or click Cancel to abort The name of a TPF Make control file
the build. User response:
Explanation: TPFC4108E Subproject build failed. A default
User response: build action cannot be found for
submitting JCL.
TPFC4100E Action failed. MakeTPF control Verify that a default build action
file {1} cannot be found in is associated for *.jcl file in the
the subproject's remote working Default Build Action preferences
directory. Subproject's remote page.
working directory has not been
specified. Explanation:
Specify the remote working User response:
directory for the subproject and
try again. TPFC4109E Subproject build failed. A JCL file
has not been specified to build the
subproject.
Explanation Verify that a JCL file has been
{1} specified in the Build Mechanism
The name of the control file preferences page.
User response: Explanation:
TPFC4101E Action failed. TPF Make control User response:
file {1} cannot be found in
TPFC4110E Subproject build failed. The JCL
the subproject's remote working
file {1} required for building the
directory {2}.
subproject could not be located.
Verify that a valid JCL file
Explanation has been specified in the Build
{1} Mechanism preferences page.
The name of the control file
{2} Explanation
The name of the subproject's directory {1}
User response: The name of a JCL file

TPFC4102E Action failed. A default build User response:

action cannot be found for the TPF TPFC4111E Subproject build failed. The JCL
Make control file. file {1} is not on the same remote
Verify that a default build action system as the subproject's remote
is associated for *.cntl file in the working directory {2}.
Default Build Action preferences Specify a JCL file that is on the
page. same remote system as the remote
Explanation: working directory or modify the
remote working directory.
User response:
TPFC4103E Building project using TPF Make Explanation
build tools...
{1}
Explanation: The name of a JCL file
User response: {2}
The location of a directory

Troubleshooting and support 139

User response: to remove the invalid target
environment from the list.
TPFC4112E Building subproject using JCL file
{1}.
Explanation
Explanation {1}
The target environment
{1}
The name of a JCL file User response:
User response: TPFC4300E Select a parent project or
subproject for the imported filter.
TPFC4120E Specify a valid JCL file.
Explanation:
Explanation:
User response:
User response:
TPFC4301E Subproject names cannot be
TPFC4121E A valid build action must be
empty.
selected.
Specify a unique and valid
Explanation: subproject name for source folder
{1}.
User response:
TPFC4130E Cannot register subproject for Explanation
debug. Either the subproject's
build list is empty or the {1}
subproject's build list does not The name of the source folder
contain any programs that can be User response:
registered.
Only DLMs, LLMs and BAL TPFC4302E {1}
programs can be registered. Specify a unique and valid
subproject name for source folder
Explanation: {2}.
User response:
TPFC4131E Cannot register subproject for Explanation
debug. The build mechanism for {1}
the subproject is invalid. The The name of a subproject
subproject's build list cannot be
{2}
determined.
The name of the source folder
Explanation:
User response:
User response:
TPFC4303E There is already a subproject in
TPFC4132E Registering the following the workspace with the name {1}.
programs from the subproject's Specify a unique subproject name
build list:{1} {2} for source folder {2}.

Explanation Explanation
{1} {1}
A line-break character The name of a subproject
{2} {2}
A list of program names The name of the source folder
User response: User response:
TPFC4200E Subproject references an invalid TPFC4304E Cannot import multiple
target environment - {1}. subprojects with the name {1}.
Use the subproject's target Specify a unique name subproject
environment properties page name for all source folders.

140 Developer for z/OS: Troubleshooting and Support

Explanation Explanation
{1} {1}
The names of the subprojects A target environment name; for example, My
Target Environment
User response:
{2}
TPFC4310E Cannot set current target A subproject name; for example, My SubProject
environment {1} for subproject {2}.
The target environment exit failed {3}
with a return code of {3}. The return code of the failure
User response:

5000-level messages
TPFC5000E Script name cannot be empty. TPFC5010E Configuration file {1} could not be
Specify a name for the script. found.
Explanation:
Explanation
User response:
{1}
TPFC5001E Build script name exceeds limit of The name of the configuration file
{1} characters.
Specify a name up to {1} User response:
characters. TPFC5011E Specify a valid data file.
The data file must be a valid
Explanation remote file on the same remote
host as the build script.
{1}
The maximum length of the name Explanation:
User response: User response:
TPFC5002E Build script file name and location TPFC5012E Specify a JCL template file.
cannot be empty.
Explanation:
Select a remote location and
specify a build script file name. User response:
Explanation: TPFC5013E Specify a valid system name. The
system must be defined in the
User response:
preferences page.
TPFC5003E Build script location is not remote.
Explanation:
Select a remote location for the
build script. User response:
Explanation: TPFC5014E Specify a valid name for GDS
output.
User response:
Explanation:
TPFC5004E Build script for {1} must have a {2}
extension. User response:
Specify a {2} extension for the file
TPFC5015E Specify the volume for the GDS
name.
output.

Explanation Explanation:

{1} User response:

File name TPFC5016E Specify a valid system name for
{2} VRDR output. The name must be
File-name extension defined in the preferences page.

User response: Explanation:

User response:

Troubleshooting and support 141

TPFC5017E Specify a user ID for VRDR output. Specify a PDS member names with
8 characters or fewer.
Explanation:
User response: Explanation
TPFC5018E The selected build script file does {1}
not mention a valid module. The name of a PDS member
The selected build script file does
not indicate that it is for a DLM, User response:
DLL or LLM. TPFC5036E PDS member {1} is already an
Explanation: input.
Specify a different PDS member.
User response:
TPFC5020E Specify the output location for the Explanation
module.
{1}
Explanation: The name of a PDS member
User response: User response:
TPFC5021E Specify inputs for the module. TPFC5037E The file {1} is already an input.
Explanation: Specify a different file name.

User response:
Explanation
TPFC5022E Specify the right value for {1}. The
{1}
current one is invalid.
File name

Explanation User response:

{1} TPFC5038E PDS member {1} is specified twice.

The name of the item for which an invalid version Remove one instance of {1} from
was specified the list.

User response:
Explanation
TPFC5030E Specify the system name.
{1}
Explanation: The name of a PDS member
User response: User response:
TPFC5031E Specify the system ID. TPFC5100E Specify a valid TPF build script
file.
Explanation:
The build script file must be a
User response: valid remote file.
TPFC5032E Specify SALVERS. Explanation:
Explanation: User response:
User response: TPFC5101E Specify a valid *.lsc file.
The lsc file must be a valid remote
TPFC5033E Specify PATVERS.
file.
Explanation:
Explanation:
User response:
User response:
TPFC5034E System already exists.
TPFC5102E Error parsing {1}.
Explanation: The BSC file must be a valid
remote file.
User response:
TPFC5035E PDS member name {1} exceeds 8
character limit.

142 Developer for z/OS: Troubleshooting and Support

Explanation User response:
{1} TPFC5502E The file {1} is already included in
The name of a BSC file the dependency list.
User response:
Explanation
TPFC5103E The bsc file {1} cannot be used to
create a {2} build script. {1}
The selected bsc file is for creating File name
a {3}. User response:
TPFC5503E Dependency must have a {1} file-
Explanation name extension.
{1}
File name Explanation
{2} {1}
DLM, DLL, or LLM File-name extension
{3}
User response:
DLM, DLL, or LLM
TPFC5504E Name field contains duplicate
User response:
name {1}.
TPFC5110E Specify a valid file extension to Ensure all names listed are
append to the input files. unique.
Explanation:
Explanation
User response:
{1}
TPFC5112E The file {1} is already listed as a
The content of name field
configuration file.
Choose a unique file name to add User response:
to the list.
TPFC5505E Specify the program name.
The program name must be four
Explanation characters.
{1} Explanation:
File name
User response:
User response:
TPFC5506E Specify a valid program name.
TPFC5200E Error generating the build script. The program name must be four
Explanation: characters.
Explanation:
User response:
User response:
TPFC5500E The file {1} is already included in
the source segment list. TPFC5507E Specify a function name for the
App entry point.
Explanation An app entry point must be
specified if export file is used.
{1}
File name Explanation:

User response: User response:

TPFC5501E Source segment must have a {1} TPFC5508E Export file cannot be specified if
file extension. app entry point is {1}

Explanation
{1}
File name

Troubleshooting and support 143

Explanation Explanation:
{1} User response:
One of the following constants: Main, Locale, TPFC5521E Specify the number of passes
Iconv required in build (1 or 2).
User response: Explanation:
TPFC5509E Invalid makefile target. User response:
Explanation: TPFC5522E Specify the makefile name.
User response: Explanation:
TPFC5510E Specify at least one source User response:
segment.
TPFC5523E Specify the target environment.
Explanation:
Explanation:
User response:
User response:
TPFC5511E BAL name must be in lower case.
TPFC5524E Specify the load attribute.
Explanation:
Explanation:
User response:
User response:
TPFC5516E Specify a value for {1}.
TPFC5525E Specify the program type.
Explanation Explanation:
{1} User response:
The label of the corresponding text field
TPFC5526E Program name is not valid.
User response: Program name must be four
characters only.
TPFC5517E Error parsing control file {1}.
Verify that the control file is valid. Explanation:
User response:
Explanation
TPFC5527E Program name must match
{1} makefile name. Makefile name is
File name {1}.
User response:
TPFC5518E Control file {1} could not be
Explanation
found in the subproject's working {1}
directory {2}. The name of the makefile
Verify that the control exists in the
User response:
subproject's working directory
TPFC5528E MakeTPF build list cannot
Explanation be saved. Subproject's remote
working directory has not been
{1} specified.
File name Specify the remote working
{2} directory for the subproject and
Directory name try again.

User response: Explanation:

TPFC5519E Specify a valid timeout value. User response:

Explanation: TPFC5529E MakeTPF build list cannot be

saved. Error writing to the control
User response: file {1}.
TPFC5520E Specify the program name.

144 Developer for z/OS: Troubleshooting and Support

 Verify that the control file {1} is not Verify that the subproject's remote
locked and is not write-protected. working directory is specified.

Explanation Explanation
{1} {1}
File name The name of the makefile
User response: User response:
TPFC5530E Makefiles must have a {1} TPFC5535E Error generating the subproject
extension. stub makefile. The subproject is
Specify a {1} extension for the file invalid.
name.
Explanation:

Explanation User response:

{1} TPFC5536W Error finding or loading the

A file-name extension, for example, .mak subproject stub makefile {1}.
Verify that a makefile exists by
User response: that name or regenerate the stub
TPFC5531E Error writing to the subproject makefile from this page.
stub makefile {1}.
Verify that the subproject stub Explanation
makefile {1} is not locked and is
{1}
not write-protected.
The name of the makefile

Explanation User response:

{1} TPFC5537E Specify at least one environment

The name of the makefile for the stub generation.

User response: Explanation:

TPFC5532E Error generating the subproject User response:

stub makefile {1}. The subproject's TPFC5538E Specify an external control file.
control file could not be found.
Verify that the subproject's remote Explanation:
working directory is specified. User response:
TPFC5539E Error parsing configuration file {1}.
Explanation Verify that the TPF Make
{1} configuration file is valid.
The name of the makefile
User response: Explanation
TPFC5533E Error generating the subproject {1}
stub makefile {1}. No owning File name
environment has been specified User response:
for the stubs.
TPFC5541E Sub-system name is invalid.

Explanation Explanation:

{1} User response:

The name of the makefile TPFC5542E Specify at least one z/OS UNIX
User response: source location.

TPFC5534E Error generating the subproject Explanation:

stub makefile {1}. User response:

Troubleshooting and support 145

TPFC5543E Specify at least one application TPFC5580W The MakeTPF configuration file
source location. {1} was not found. The remote
working directory has not been
Explanation:
specified.
User response:
TPFC5544E MakeTPF configuration file cannot Explanation
be found. {1}
Make sure maketpf.cfg exists in File name
your project working directory or
TPF_CFG variable is set. User response:
Explanation: TPFC5590E Action failed. The selection is
invalid.
User response: You can only run this action on a
TPFC5545E The project's configuration file z/OS UNIX subproject.
cannot not be found. Explanation:
Make sure maketpf.cfg exists in
your project working directory or User response:
TPF_CFG variable is set. TPFC5591I Running MakeTPF target {1}...
Explanation:
User response: Explanation
TPFC5546E Error generating project's {1}
configuration file. A make target label; for example, clean, objs, or
hfs2pds
Explanation:
User response:
User response:
TPFC5592I Action failed. The MakeTPF
TPFC5547E Error generating maketpf.cfg. based build mechanism of the
Explanation: current target environment {1}
for subproject {2} references an
User response: invalid action.
TPFC5548E Subproject cannot be built. Verify that the action exists in the
Menu Manager.
Explanation:
User response: Explanation
TPFC5549E MakeTPF configuration cannot {1}
be saved. Subproject's remote The name of a target environment
working directory has not been
{2}
specified.
The name of a subproject
Specify the remote working
directory for the subproject and User response:
try again.
TPFC5593I Action failed. The MakeTPF
Explanation: based build mechanism of the
current target environment {1} for
User response:
subproject {2} is invalid.
TPFC5550I A MakeTPF configuration file was Verify that the build mechanism
not found in the subproject's information exists in the
remote working directory. Specify Build Mechanism building block
the appropriate values to generate preference page.
a new one.
Explanation: Explanation
User response: {1}
The name of a target environment

146 Developer for z/OS: Troubleshooting and Support

{2} TPFC5600E The LoadTPF file action definition
The name of a subproject could not be found.
Verify that there is a file action
User response:
definition in the Menu Manager
TPFC5594I Action failed. The MakeTPF for the loadtpf command and it is
based build mechanism of the assigned as a default build action
current target environment {1} for *.loadtpf file type.
for subproject {2} references an
Explanation:
invalid action. An action with ID
{3} cannot be found. User response:
Verify that the build mechanism is
TPFC5601E The LoadTPF file action has failed.
referring to a valid action.
The project MakeTPF control file
cannot be found or it is empty.
Explanation
Explanation:
{1}
The name of a target environment User response:
{2} TPFC5602E The LoadTPF file action has failed.
The name of a subproject A valid TPF IP address was not
specified.
{3}
An action ID Explanation:
User response: User response:

6000-level messages
TPFC6000W The file {0} will still be shown in TPFC6003E The folder {0} is a parent of the
filter {1} after the move because of folder {1}. The folder cannot be
a broad filter. moved into one of it's children.
Select a different parent folder
Explanation that is not already a child of the
folder being moved.
{0}
File name
Explanation
{1}
Filter name {0}
Folder name
User response:
{1}
TPFC6001W The folder {0} will still be shown in Folder name
filter {1} after the move because of
User response:
a broad filter.
TPFC6004E The folder {0} cannot be a source
Explanation folder and a destination folder.
Select a different parent folder.
{0}
Folder name
Explanation
{1}
Filter name {0}
Folder name
User response:
User response:
TPFC6002W Some items may still be shown in
their parent filters due to broad TPFC6005E Move validation cancelled. Change
filters. the selection to revalidate.

Explanation: Explanation:

User response: User response:

Troubleshooting and support 147

TPFC6006E Move cannot be completed. Source Check the connection and retry
folders and destination folder are the download action.
related.
Select a different parent folder. Explanation
Explanation: {1}
User response: File name

TPFC6007E Move cannot be completed. The User response:

selected filter contains files from TPFC6102E Download of file {1} failed because
{0} with user ID {1}; you cannot folder {2} could not be accessed.
add files from the same location Check the connection and retry
with user ID {2}. the download action.
Select a different parent filter.

Explanation
Explanation
{1}
{0} File name
The name of a remote system
{2}
{1} Folder name
A user identifier
User response:
{2}
A user identifier TPFC6103E Download of file {1} failed because
the file is not remote.
User response:
Only remote files can be
TPFC6008E No parent filter selected. downloaded.
Select a parent filter for moved
files and folders. Explanation
Explanation: {1}
User response: File name

TPFC6009E Can't move files or folders. User response:

Select a different physical location TPFC6104E Download of file {1} failed
or a different parent filter to because the file is disconnected or
complete the move. inaccessible.
Explanation:
User response: Explanation
TPFC6100W Download action failed because a {1}
file named {1} already exists in File name
folder {2}. User response:
Select a target folder that does not
contain a file with the same name, TPFC6105E Upload of file {1} failed because
or choose to overwrite the existing the file is disconnected or
file when prompted. inaccessible.

Explanation Explanation
{1} {1}
File name File name
{2} User response:
Folder name TPFC6106E Upload of file {1} failed because
User response: the file is not remote.
Only remote files can be uploaded.
TPFC6101E Download action failed because
the file {1} could not be accessed.

148 Developer for z/OS: Troubleshooting and Support

Explanation Explanation
{1} {1}
File name The name of a remote file
User response: {2}
The name of a local file
TPFC6107E Upload of file {1} failed because
the file was never properly User response:
downloaded. TPFC6112E Paste action failed because the
clipboard is empty.
Explanation You must copy a file, folder,
z/OS UNIX Filter, or z/OS UNIX
{1}
Subproject before performing a
File name
paste.
User response:
Explanation:
TPFC6108E File {1} is disconnected.
User response:
Enter connected mode for host {2}
and retry. TPFC6113E Paste action failed because the
clipboard contains invalid items.
When pasting to a folder, only files
Explanation
and folders can be pasted. Copy
{1} only files and/or folders to the
File name clipboard and retry.
{2} Explanation:
The name of a remote system
User response:
User response:
TPFC6114E Paste action failed because the
TPFC6109E The file {1} does not exist in folder clipboard contains invalid items.
{2}. When pasting to a z/OS UNIX
Select the local folder where {1} filter, only files and folders can
was originally downloaded. be pasted. Copy only files and/or
folders to the clipboard and retry.
Explanation Explanation:
{1} User response:
File name
TPFC6115E Paste action failed because the
{2}
clipboard contains invalid items.
Folder name
When pasting to a z/OS UNIX
User response: subproject, only z/OS UNIX Filters
can be pasted. Copy only z/OS
TPFC6110E The file {1} has been modified on
UNIX Filters to the clipboard and
the remote system since it was
retry.
downloaded.
Explanation:
Explanation User response:
{1} TPFC6116E Unexpected error pasting {1} into
File name folder {2}.
User response: Ensure folder {2} is not read-only
and that there is enough disk
TPFC6111I The file {1} was successfully space.
downloaded.
Local copy is: {2}
Explanation
{1}
File name or folder name

Troubleshooting and support 149

{2} {2}
Folder name Folder name
User response: User response:
TPFC6117E Paste failed because the folder {1} TPFC6503I The folder {1} was successfully
is read-only. copied to {2}.
Select a destination that is not
read-only. Explanation
{1}
Explanation Folder name
{1} {2}
Folder name Folder name
User response: User response:
TPFC6200E Link action failed because a TPFC6504E Copy of file {1} failed.
default build action was not found Ensure that the source and target
for *.o or *.obj files. are accessible and that the target
Explanation: is not write protected.

User response:
Explanation
TPFC6500W Download of file {1} failed because
the copy operation to folder {2} {1}
was cancelled. File name
Retry the download operation. User response:
TPFC6505E Copy of {1} failed.
Explanation Ensure that the source exists and
{1} is accessible.
File name
{2} Explanation
Folder name {1}
User response: File name
TPFC6501W Download action failed because a User response:
file named {1} already exists in TPFC6506E Copy of {1} to folder {2} failed.
folder {2}. Ensure that the target folder exists
Select a target folder that does not and is accessible.
contain a file with the same name,
or specify the -r flag to replace the
existing file. Explanation
{1}
Explanation File name or folder name
{1} {2}
File name Folder name
{2} User response:
Folder name TPFC6507I The file {1} was changed on
User response: the remote system since it was
downloaded.
TPFC6502I The file {1} was successfully
copied to {2}.
Explanation
Explanation {1}
File name
{1}
File name User response:

150 Developer for z/OS: Troubleshooting and Support

TPFC6508E Deletion of file {1} failed because Explanation
the file could not be accessed.
{1}
File name
Explanation
User response:
{1}
File name TPFC6515I File {1} was successfully uploaded
as {2}.
User response:
TPFC6509E Deletion of folder {1} failed Explanation
because the folder could not be
{1}
accessed.
File name
{2}
Explanation The name of a remote file
{1}
User response:
Folder name
TPFC6516E Upload of file {1} failed because
User response:
the remote version was modified.
TPFC6510I File {1} successfully deleted.
Explanation
Explanation {1}
{1} File name
File name
User response:
User response:
TPFC6517I The file {1} was successfully
TPFC6511I Folder {1} and it's contents were uploaded.
successfully deleted.
Explanation
Explanation {1}
{1} File name
Folder name
User response:
User response:
TPFC6518E Upload of file {1} failed with an
TPFC6512E Delete action failed with an unknown error.
unexpected error.
Explanation: Explanation
User response: {1}
File name
TPFC6513E Upload of file {1} from folder {2}
failed because the folder {2} could User response:
not be accessed. TPFC6519E CreateFolder failed because the
subproject {1} does not exist.
Explanation
{1} Explanation
File name {1}
{2} The name of a subproject
Folder name
User response:
User response:
TPFC6520E CreateFolder failed because the
TPFC6514I File {1} was successfully uploaded filter {1} does not exist in the
and remote changes were subproject {2}.
overwritten.

Troubleshooting and support 151

Explanation TPFC6526I CreateFolder failed to create {1}
because the folder already exists.
{1}
Filter name
{2}
Explanation
The name of a subproject {1}
Folder name
User response:
User response:
TPFC6521E CreateFolder failed because the
folder argument (-o) was invalid or TPFC6527I setProperties failed because the
not specified. subproject {1} or the filter {2} does
not exist.
Explanation:
User response: Explanation
TPFC6522I CreateFolder successfully created {1}
the folder {1} in the folder {2}. The name of a subproject
{2}
Explanation Filter name
{1} User response:
Folder name
TPFC6528E QueryVariables failed because the
{2}
subproject {1} does not exist.
Folder name
User response: Explanation
TPFC6523I CreateFolder successfully created {1}
all folders on the path {1}. The name of a subproject
User response:
Explanation
TPFC6529E QueryVariables failed because the
{1}
filter {1} does not exist in the
Path name
subproject {2}.
User response:
TPFC6524E CreateFolder failed to create Explanation
folder(s) {1} because an {1}
unexpected error occurred. Filter name
{2}
Explanation The name of a subproject
{1} User response:
Folder names
TPFC6530E QueryVariables failed because the
User response: file {1} does not exist in the filter
TPFC6525E Could not create a filter string to {2}.
show the folder {1} in the filter {2}.
There may be a user ID conflict. Explanation
{1}
Explanation File name
{1} {2}
Folder name Filter name
{2} User response:
Filter name
TPFC6531E QueryVariables failed because
User response: there are no substitution variables
named {1}.

152 Developer for z/OS: Troubleshooting and Support

Explanation Explanation
{1} {1}
The name of a variable A name
User response: {2}
An option-set type
TPFC6532E QueryVariables failed because the
variable {1} cannot be resolved for {3}
the specified target. Valid names for the type of option set
User response:
Explanation TPFC6539E The property {1} cannot be set at
{1} the file level. Specify a subproject
The name of a variable only.

User response:
Explanation
TPFC6533E QueryVariables failed to write
output to file {1}. {1}
The name of a property

Explanation User response:

{1} TPFC6540E The folder {1} is not a valid remote

File name working directory.

User response:
Explanation
TPFC6534I The variable is resolved
successfully. {1}
Folder name
Explanation:
User response:
User response:
TPFC6541E The subproject {1} does not exist.
TPFC6535E Open file failed because the file {1}
could not be opened.
Explanation
Explanation {1}
The name of a subproject
{1}
File name User response:

User response: TPFC6542E A file named {1} already exists and

will not be replaced.
TPFC6536I Open file success. File {1} opened. Specify a new file name or add the
-r flag to replace the existing file.
Explanation
{1} Explanation
File name {1}
User response: File name

TPFC6537W Filter string added. Warning: {1} User response:

TPFC6543E Migration scan cancelled by user.
Explanation No results written to output file.

{1} Explanation:
The returned warning message User response:
User response: TPFC6544E Migration scan failed writing
TPFC6538E The name {1} is invalid for type {2}. output to file {1}. Error {2}.
Valid names for type {2} are: {3}.

Troubleshooting and support 153

Explanation Explanation
{1} {1}
File name File name
{2} {2}
The returned message The returned error message
User response: User response:
TPFC6545I Migration scan successfully TPFC6550I Successfully read and fixed {1}
completed. {1} results written to problems from results file {2}.
file {2}.
Explanation
Explanation {1}
{1} The number of problems
The number of results {2}
{2} File name
File name
User response:
User response:
TPFC6551E {1} results successfully read from
TPFC6546E Migration results file {1} contains file {2}.
invalid date {2}. {3} errors fixed. {4} warnings
fixed. {5} problems not resolvable.
Explanation {6} problems not resolved due
to overlap. {7} potential errors
{1} ignored.
File name
{2} Explanation
A date
{1}
User response: The number of results
TPFC6547E File {1} is not a valid migration {2}
scan results file because it does File name
not contain a scan date. {3}
The number of errors
Explanation {4}
{1} The number of warnings
File name {5}
User response: The number of problems
{6}
TPFC6548I Successfully listed {1} results from
The name of the problems
{2}.
{7}
The number of potential errors
Explanation
User response:
{1}
The number of results TPFC6552E Compare file with migrated
{2} version action was unable to
File name repair all {1} problems in file file
{2}.
User response: {3} errors fixed. {4} warnings
TPFC6549E Failed reading results from file {1}. fixed. {5} problems not resolvable.
Error: {2} {6} problems not resolved due
to overlap. {7} potential errors
ignored.

154 Developer for z/OS: Troubleshooting and Support

Explanation TPFC6557E Additional flags not required by
the specified launch type was set.
{1}
Check your options again to verify
The total number of problems
that your settings are correct.
{2}
File name Explanation:

{3} User response:

The number of errors TPFC6558E The connection could not be
{4} created. Since a launch option was
The number of warnings not selected, no optional flags,
{5} aside from -w, should be set.
The number of problems that are not resolvable Explanation:
{6} User response:
The name of the problems
TPFC6559E The connection could not be
{7}
created. Enter a valid port number.
The number of potential errors
Explanation:
User response:
User response:
TPFC6553E {1} cannot be resolved, do not
specify both a subproject and a TPFC6560E The connection could not
target environment. be created. Ensure that the
connection does not already exist,
and that all specified parameters
Explanation
are valid.
{1}
Query options Explanation:

User response: User response:

TPFC6554E The {1} subproject does not have TPFC6561I The connection was created
a current target environment successfully.
associated with it. Explanation:
User response:
Explanation
TPFC6562I The filter string(s) for {1} are listed
{1} below.
The name of a subproject
User response: Explanation
TPFC6555E The {1} target environment does {1}
not exist. The specified target environmen
User response:
Explanation
TPFC6563E Query failed because the
{1} subproject {1} does not exist.
The specified target environment
User response: Explanation
TPFC6556E Failed to resolve {1}. Make sure {1}
that this target environment The name of a subproject
variable is defined.
User response:

Explanation TPFC6564E Query failed because the filter {1}

does not exist.
{1}
The specified target environment
User response:

Troubleshooting and support 155

Explanation TPFC6571E Import failed. The file {1} does not
contain any target environment
{1}
definitions.
Filter name
User response: Explanation
TPFC6565I The import was completed {1}
successfully. File name
Explanation: User response:
User response: TPFC6572E Import failed due to conflicting
TPFC6566E Import failed. The specified file {1} target environment names.
does not exist. Explanation:
User response:
Explanation
TPFC6573W Import completed. Some option
{1}
sets are conflicting, and were not
File name
imported.
User response:
Explanation:
TPFC6567E Import failed. The specified file
User response:
{1} is not a valid .xml file. Verify
that this file contains proper target TPFC6574I The outcomes of each individual
environment definitions, and that target environment import is listed
it is a Local file. below.
Explanation:
Explanation
User response:
{1}
File name TPFC6575E Export failed. Ensure that the file
name is valid, and that it ends
User response: with a XML extension.
TPFC6568E Import failed. The specified target Explanation:
environment {1} does not exist in
the file {2}. Verify that the correct User response:
target environment was specified TPFC6576E Export failed. Specify either the
for this file. -a flag to export all blocks of this
type, or the -n flag to export a
Explanation specific building block.

{1} Explanation:
The specified target environment User response:
{2} TPFC6577E Export failed. The specified
File name building block {1} could not be
User response: found.
TPFC6569E Import failed. Specify either a
target environment, or the -all Explanation
option. {1}
Explanation: The specified building block

User response: User response:

TPFC6570E Import failed. Do not specify both TPFC6578E The export was completed
the -all and the -targetEnv options. successfully.

Explanation: Explanation:

User response: User response:

156 Developer for z/OS: Troubleshooting and Support

TPFC6579I The Action file was imported TPFC6586I Import succeeded. The file {1} was
successfully. successfully imported.
Explanation:
Explanation
User response:
{1}
TPFC6580W Import successful. Warning: An File name
absolute path was used to
reference the action file. It is User response:
not recommended that you use TPFC6587I The Action file was promoted to
an absolute path to reference a Enterprise level.
shared file. If you intended to use
an environement variable in this Explanation:
path, use the appropriate escape User response:
characters to prevent the variable
from being prematurely resolved. TPFC6588E The target environment name was
not specified.
Explanation: Specify the name of an existing
User response: target environment.
TPFC6581E Import failed, invalid Options Explanation:
specified. User response:
Explanation: TPFC6589E The target environment {1} does
User response: not exist.
Specify the name of an existing
TPFC6582E Import failed. This Action file is target environment.
already known to Menu Manager.
Specify the -promote option to
promote the existing file to the Explanation
Enterprise level. {1}
Explanation: The specified target environment

User response: User response:

TPFC6583E Import failed. The file is not a valid TPFC6590E The type {1} is not a valid option
Action file. set type.
Specify a valid option set type
Explanation: (BuildAndLink, BuildMechanism,
User response: EditorOptions, LoadOptions,
MenuOptions, TargetEnvVars,
TPFC6584E Import failed. The file {1} already TPFMakeConfig).
exists at the Enterprise Level.
Explanation
Explanation
{1}
{1} A specified option set type
File name
User response:
User response:
TPFC6591E The option set type was not
TPFC6585I Import succeeded. The file {1} was specified.
successfully imported. Specify an option set type. (e.g.
BuildAndLink)
Explanation Explanation:
{1} User response:
File name
TPFC6592E An unknown error occurred while
User response: processing the QueryTargetEnv
command.

Troubleshooting and support 157

Explanation: TPFC6601I Import completed, but some
templates were not imported due
User response:
to conflicts. These are listed
TPFC6593I The command completed below.
successfully.
Explanation:
Explanation:
User response:
User response:
TPFC6602I The specified file {1} was not
TPFC6594I The command completed found.
successfully. No results were
found.
Explanation
Explanation:
{1}
User response: File name
TPFC6595E The connection could not be User response:
created. A user ID must also
TPFC6603I The specified file {1} is invalid.
be specified if you specify the
Please specify a file with a .xml
password.
extension.
Explanation:
User response: Explanation
TPFC6596I The query variable succeeded {1}
without user ID. File name

Explanation: User response:

User response: TPFC6604I The specified target

environments(s) were deleted
TPFC6597I Import completed. However, successfully.
conflicting target environments or
building blocks were not imported. Explanation:

Explanation: User response:

User response: TPFC6605I The specified target

environments(s) along with their
TPFC6598I Import completed. Any conflicting referenced option sets were
target environments and Option deleted successfully.
Sets have been overwritten.
Explanation:
Explanation:
User response:
User response:
TPFC6606E Invalid parameters. Please specify
TPFC6599E The rule group {1} does not exist. either a target environment to
Specify the name of an existing delete, or the -alltargetEnv option.
rule group.
Explanation:
Explanation User response:
{1} TPFC6607E The specified target environment
The name of a rule group {1} was not found.
User response:
Explanation
TPFC6600I The import was completed
successfully. {1}
The specified target environment
Explanation:
User response:
User response:

158 Developer for z/OS: Troubleshooting and Support

TPFC6608E Specify either a target Explanation
environment to delete, or the
{1}
-allTargetEnv option, but not both.
The name of an option set
Explanation:
User response:
User response:
TPFC6612E Specify either an option set name,
TPFC6609I Some referenced option sets could or the -allOptionSet option.
not be deleted, because they
Explanation:
are referenced by other target
environments. These option sets User response:
are listed below.
TPFC6613I All specified option sets have been
Explanation: deleted. target environments that
are now invalid are listed below.
User response:
Explanation:
TPFC6610E The specified option sets were
deleted successfully. User response:
Explanation: TPFC6614I Option sets that were referenced
by other target environments were
User response:
not deleted, and are listed below.
TPFC6611E The specified option set {1} does
Explanation:
not exist.
User response:

7000-level messages
TPFC7000E Unable to create connection path Explanation
for TPFFile {0}.
{0}
The name of a remote system
Explanation {1}
{0} A user identifier
File name {2}
User response: Filter name

TPFC7001E Unable to create connection path User response:

for TPFFolder {0}. TPFC7004I A conflict between filter string {0}
and filter string {1} was found and
Explanation resolved while loading filter {2}
Details: {3}
{0}
Folder name
Explanation
User response:
{0}
TPFC7002E Unable to refresh IResource object A specified filter string
{0} before performing eclipse
actions. {1}
A specified filter string

Explanation {2}
The name of a filter
{0}
{3}
The name of an IResource object
The returned message
User response:
User response:
TPFC7003E A user ID conflict will prevent the
TPFC7005I Ensure the environment variable
files from {0} from showing with
is set, and the location can be
user ID {1} in filter {2}.
accessed. Restart once problems
have been resolved.

Troubleshooting and support 159

 If the variable is set to an NFS or Explanation:
SMB mounted location, ensure the
User response:
connection has been established.

8000-level messages
TPFC8000E Parent filter must be specified. Explanation:
Explanation: User response:
User response: TPFC8024E Select a filter that is not the source
filter.
TPFC8010E Select a remote file or folder.
If browsing for an NFS/SMB Explanation:
connected system, browse under User response:
LOCAL for the mounted drive
letter. TPFC8025E The selected subproject is
the source subproject. Select
Explanation: a different subproject as the
User response: destination.
TPFC8011I Select a remote file. If browsing Explanation:
for an NFS/SMB connected User response:
system, browse under LOCAL for
the mounted drive letter. TPFC8026E Select a destination subproject.
Explanation: Explanation:
User response: User response:
TPFC8012I Select a remote folder. If browsing TPFC8027E No target subproject selected.
for an NFS/SMB connected Select an existing subproject to
system, browse under LOCAL for merge the imported subproject
the mounted drive letter. into.
Explanation: Explanation:
User response: User response:
TPFC8015E Only select one folder. TPFC8028E No file selected.
Select a file.
Explanation:
Explanation:
User response:
User response:
TPFC8016E Only select folders.
TPFC8029E No folder selected.
Explanation:
Select a folder.
User response: Explanation:
TPFC8017E Only select files. User response:
Explanation: TPFC8030E No z/OS UNIX Subproject
User response: selected.
Select a z/OS UNIX Subproject.
TPFC8018E Path already exists.
Explanation:
Explanation:
User response:
User response:
TPFC8031E No z/OS UNIX Filter selected.
TPFC8020I Select a file. Select a z/OS UNIX Filter.
Explanation: Explanation:
User response: User response:
TPFC8021I Select a folder.

160 Developer for z/OS: Troubleshooting and Support

TPFC8032E The file {1} does not reside in Explanation
TPFPROJ ({2}).
{0}
Choose a file from the TPFPROJ
A port number
directory.
User response:
Explanation TPFC8603I The TPFtool server has stopped
{1} listening on port {0}.
File name
{2} Explanation
The path name of the TPFPROJ {0}
User response: A port number

TPFC8501E The selected resource is not a User response:

valid trace file. TPFC8604E The TPFtool server cannot be
Explanation: started on port(s) {0}. Change the
port list and restart the server.
User response:
TPFC8502E The file {1} could not be read. Explanation
Check that a connection to access
{0}
the file exists and is connected.
A port number or port numbers

Explanation User response:

{1} TPFC8605I You have entered a new Available

File name Ports list for the TPFtool server.
Would you like to restart the
User response: TPFtool server now to reflect the
TPFC8601E The port number specified is out of change?
bound. Explanation:
Explanation: User response:
User response:
TPFC8602I The TPFtool server is started on
port {0}.

9000-level messages
TPFC9050E Internal error. Could not resolve Explanation:
the resource. User response:
Explanation: TPFC9200E No files selected.
User response: Select at least one file to be
available while disconnected.
TPFC9051E Internal error. Could not initialize
the z/OS UNIX Navigator. Explanation:
Explanation: User response:
User response: TPFC9201E Unable to download file {1}.
The file will not be available in
TPFC9052E Internal error. z/OS UNIX disconnected mode.
Navigator action failed. The system may have been
Explanation: disconnected or there is not
enough space.
User response:
TPFC9053E Internal error. Could not initialize
the z/OS UNIX Toolkit Perspective.

Troubleshooting and support 161

Explanation Explanation:
{1} User response:
File name TPFC9207E No hosts are in disconnected
User response: mode.
In order to upload changes, one or
TPFC9202E Unable to find a connection to host more systems must already be in
{1}. disconnected mode.
Explanation:
Explanation
User response:
{1}
The name of a remote system TPFC9208E The remote version of the
file {1} was changed while in
User response:
disconnected mode.
TPFC9203E Unable to access folder {1} on host Both the local replica and the
{2}. remote version of the file {1} have
different changes.
Explanation
{1}
Explanation
Folder name {1}
{2} File name
The name of a remote system User response:
User response: TPFC9506E {1} cannot be blank.
TPFC9204E Local changes made in folder {1}
on host {2} can't be uploaded Explanation
because the remote folder does
{1}
not have write permission.
The name of a component
The local changes will not be
uploaded to the remote system. User response:
TPFC9507E {1} already exists.
Explanation
{1} Explanation
Folder name
{1}
{2} The name of a component
The name of a remote system
User response:
User response:
TPFC9508E {1} cannot contain ; or |.
TPFC9205W An internal error occurred while
detecting changes on host(s): {1}.
Only new and changed files will be Explanation
uploaded, deletions are lost. {1}
The name of a component
Explanation User response:
{1} TPFC9510E Invalid IP Address
The name or names of one or more remote Specify in the format a.b.c.d,
systems where a,b,c,and d must be
User response: integers between 0 and 255.

TPFC9206E No hosts selected to enter Explanation:

disconnected mode. User response:
Check at least one host that you
want to use disconnected mode TPFC9599E Error saving file {1}
on.

162 Developer for z/OS: Troubleshooting and Support

Explanation User response:
{1} TPFC9608E Select a user variable set
File name
Explanation:
User response:
User response:
TPFC9600E Specify the IP address.
Specify "?" if the IP address is not TPFC9609E Select a make option set
known. Explanation:
Explanation: User response:
User response: TPFC9610E This name is already in use.
TPFC9601E Select at least one build option set Specify a unique name.
Explanation: Explanation:
User response: User response:
TPFC9602E Select a build mechanism TPFC9611E Specify a valid name
Explanation: Explanation:
User response: User response:
TPFC9603E Select an editor option set TPFC9612E Select at least one link option set
Explanation: Explanation:
User response: User response:
TPFC9604E Select at least one load option set TPFC9620E Select at least one target
environment.
Explanation:
Explanation:
User response:
User response:
TPFC9605E Select at least one make option set
TPFC9621E Set a current target environment.
Explanation:
Explanation:
User response:
User response:
TPFC9606E Select a menu option set
TPFC9630E Specify the base comment for
Explanation: Autocomment.
User response: Explanation:
TPFC9607E Select a user exit set User response:
Explanation:

Messages for TPF Toolkit Connection Manager

These are the messages that pertain to TPF Toolkit Connection Manager.

1000-level messages
TPFR1000E The device '{1}' does not exist on Explanation
the local file system.
{1}
An absolute path name
Explanation
User response:
{1}
The name of the device TPFR1002E Empty input could not be used to
locate any files.
User response:
Explanation:
TPFR1001E The path '{1}' is invalid.
User response:

Troubleshooting and support 163

TPFR1003E The file name '{1}' is invalid. User response:
TPFR1009E Empty input could not be used to
Explanation locate any folders.
Type a folder name.
{1}
A file name Explanation:
User response: User response:
TPFR1004E No host information found for UNC TPFR1010E Empty input could not be used to
path '{1}'. locate any files or folders.
Explanation:
Explanation
User response:
{1}
An absolute Universal Naming Convention path TPFR1011E File name cannot be empty.
name Explanation:
User response: User response:
TPFR1005E No path information found for UNC TPFR1012E No file name specified for path
path '{1}'. '{1}'.

Explanation Explanation
{1} {1}
An absolute Universal Naming Convention path An absolute path name
name
User response:
User response:
TPFR1013E Could not find '{1}' on host '{2}'.
TPFR1006E The location '{1}' does not Connected locations on host '{2}'
represent a file. are {3}.

Explanation Explanation
{1} {1}
A specified location The name of a file or folder
User response: {2}
The name of a remote system
TPFR1007E Could not find an NFS, SMB or RSE
connection for host '{1}'. {3}
One or more currently connected locations
Explanation User response:
{1} TPFR1014E There are no NFS or SMB
The name of a remote system connections for host '{1}'.
User response:
Explanation
TPFR1008E Invalid UNC syntax: '{1}'.
{1}
The name of a remote system
Explanation
User response:
{1}
A specified value that does not use valid Universal
Naming Convention syntax

2000-level messages
TPFR2000W No connections to host '{1}' could Explanation
be found.
{1}
The name of a remote system

164 Developer for z/OS: Troubleshooting and Support

User response: TPFR2011E No connections to host '{1}' with
user ID '{2}' could be found.
TPFR2001W The local file system does not have
Create a new z/OS connection in
a device named '{1}'.
RSE to access host '{1}', or create
an NFS or SMB connection.
Explanation
{1} Explanation
The name of a device
{1}
User response: The name of a remote system
TPFR2002W No NFS or SMB connections could {2}
be found to access '{1}' on host A user identifier
'{2}'.
User response:
TPFR2012E Unable to connect to host '{1}'.
Explanation
RSE was unable to establish a
{1} connection to host '{1}'. Try again.
The name of a device
{2} Explanation
The name of a remote system
{1}
User response: The name of a remote system
TPFR2003W The folder '{1}' does not exist on User response:
host '{2}'.
TPFR2013E Unable to locate a host connection
to access '{1}'.
Explanation Ensure there is an RSE, NFS or
{1} SMB connection that allows access
The name of a folder to the location.
{2}
The name of a remote system Explanation
User response: {1}
The name of a remote system
TPFR2004W The host '{1}' is already in
disconnected mode. User response:
Only previously downloaded TPFR2014E '{1}' does not exist on host '{2}'.
content will be available. Make sure the file or folder exists.

Explanation Explanation
{1} {1}
The name of a remote system The name of a file or folder
User response: {2}
The name of a remote system
TPFR2010E No connections to host '{1}' could
be found. User response:
Create a new z/OS connection in
TPFR2015E '{1}' is currently available in
RSE to access host '{1}', or create
disconnected mode only.
an NFS or SMB connection.
To perform remote operations on
the file or folder, you must enter
Explanation connected mode for host '{2}'.
{1}
The name of a remote system Explanation
User response: {1}
The name of a file or folder

Troubleshooting and support 165

{2} TPFR2017W There are no matches for file
The name of a remote system pattern '{1}' in folder '{2}'.
User response:
Explanation
TPFR2016E The host '{1}' is in disconnected
mode and '{2}' does not exist in {1}
local replicas. The specified file-name pattern
If the file or folder does exist {2}
on the remote system, enter The name of a folder
connected mode to locate the file
or folder. User response:
TPFR2100I Export succeeded. Results written
Explanation to file: '{1}'.
{1}
The name of a remote system Explanation
{2} {1}
The name of a file or folder The name of a file
User response: User response:

3000-level messages
TPFR3000E The file '{1}' cannot be accessed. Ensure the file can be accessed.
Ensure there is a connection
available to access the file. Explanation
{1}
Explanation The name of a file
{1} User response:
The name of a file
TPFR3004I Successfully wrote {1} messages
User response: to file '{2}'
TPFR3001E Action unavailable - Remote Error
List contains no errors. Explanation
Run actions that produce error
messages to populate the Remote {1}
Error List and retry. The number of messages written to the file

Explanation: {2}
The name of a file
User response:
User response:
TPFR3002E No fields included.
Select one or more fields to be TPFR3005E Action unavailable - Ignored Error
written to the output file. List contains no errors.
Run actions that produce error
Explanation: messages to populate the Ignored
User response: Error List and retry.

TPFR3003E Unknown error occured while Explanation:

writing to file '{1}'. User response:

6000-level messages
TPFR6001E The login was incorrect. TPFR6002W The messages exceed the buffer
Check that the user ID and size.
password are set correctly. Some of the messages may not
appear.
Explanation:
Explanation:
User response:
User response:

166 Developer for z/OS: Troubleshooting and Support

TPFR6003W Host name {1} was found User response:
associated with more than one TPFR6043E The action command is not a valid
system type and the first one will one.
be picked up.
Open the preferences page and Explanation:
update the saved passwords User response:
information.
TPFR6044E Cannot find an existing connection
to the remote host.
Explanation
Explanation:
{1}
The name of a remote system User response:
User response: TPFR6045E Failed in removing the command
script file.
TPFR6011I The command {2} is running on
remote system {1} Explanation:
User response:
Explanation
TPFR6046E Cannot open the file to read.
{1}
Value Explanation:
{2} User response:
Value TPFR6047E Invalid connection type.
User response: Explanation:
TPFR6012I The following is the output of the User response:
command:
{1} TPFR6048E Host name is missing.
Explanation:
Explanation User response:
{1}
TPFR6049E Cannot find the file bbsjcl.cfg in
The output of the command
the project directory.
User response:
Explanation:
TPFR6013I The following is the output of the
User response:
user exit:
{1} TPFR6050E Failed processing the BBSOUT
card in the configuration file.
Explanation Explanation:
{1} User response:
The output of the user exit
TPFR6051E Failed adding error message to the
User response: task list.
TPFR6041E The action cannot be performed Explanation:
against the selected object.
Please check that the right object User response:
is selected. TPFR6052E Cannot find the JCL template
Explanation: file for loadset generation in the
project directory.
User response:
Explanation:
TPFR6042E Cannot find the project directory.
Ensure that the environment User response:
variable BBSPROJ is set up TPFR6053W DSN TLDROUT and OUTPUT are
correctly. found in the JCL template file.
Explanation: OUTPUT is used.

Troubleshooting and support 167

Explanation: TPFR6145E Failed running the user exit {1}.
User response:
Explanation
TPFR6054E Cannot find the target system for
the selected resource. {1}
The name of a local log file
Explanation:
User response:
User response:
TPFR6146E The active connection to the host
TPFR6055W The action configuration set on the
{1} cannot be found.
Multi System Script action page is
ignored.
Explanation
Explanation:
{1}
User response: The name of a remote system
TPFR6062E Login failed. Password not User response:
specified.
TPFR6147W Failed to find the offset in the file
Explanation: {1}.
User response:
TPFR6063E Login failed. User ID not specified. Explanation
Explanation: {1}
The name of a file
User response:
User response:
TPFR6141E File {1} could not be found.
TPFR6148E Cannot find the file {1}.

Explanation
Explanation
{1}
The name of a file {1}
The name of a file
User response:
User response:
TPFR6142E Failed processing command
header {1}. TPFR6149E Found the wrong file {1}.

Explanation Explanation
{1} {1}
The header of the command The name of a file

User response: User response:

TPFR6143E The length of command exceeds TPFR6150E Failed moving the file to {1}.
the command length limit {1}.
Explanation
Explanation {1}
{1} The name of a file
The limit of command length User response:
User response: TPFR6151E Failed deleting the file {1}.
TPFR6144E Failed processing the file {1}.
Explanation
Explanation {1}
{1} The name of a file
The name of a file User response:
User response:

168 Developer for z/OS: Troubleshooting and Support

TPFR6152E Failed connecting to {1}. Explanation
{1}
Explanation A user ID
{1} User response:
The name of a remote system
TPFR6159I Filter matched {1} of {2} messages
User response:
TPFR6153E Failed finding root on {1}. Explanation
{1}
Explanation The number of messages matched
{1} {2}
The name of a remote system The total number of messages
User response: User response:
TPFR6154E Cannot find the configuration for TPFR6200E Error Creating File: File Exists.
the system {1} in the configuration
Explanation:
file.
User response:
Explanation TPFR6201E Error Creating File: No Write
{1} Permission.
The name of a remote system Explanation:
User response: User response:
TPFR6155I The file filter {1} cannot be TPFR6202E Unknown error creating file. File
resolved. not created.
Explanation:
Explanation
User response:
{1}
The name of a file filter TPFR6203E Error Creating Folder: Folder
Exists.
User response:
Explanation:
TPFR6156E Failed processing the file {1}.
User response:
Explanation TPFR6204E Error Creating Folder '{1}' in '{2}':
No write Permission.
{1}
The name of a file
Explanation
User response:
{1}
TPFR6157E The object '{1}' matched the filter The name of a folder to be created
'{2}' but could not be used as a file.
{2}
The name of a folder
Explanation
User response:
{1}
The name of an object TPFR6205E Unknown error creating folder.
Folder not created.
{2}
The name of a file filter Explanation:
User response: User response:
TPFR6158E The working directory TEMPDIR TPFR6206E Failed transferring the file.
can't be found for the user '{1}' Explanation:
User response:

Troubleshooting and support 169

TPFR6207E Failed processing the JCL file. User response:
Explanation: TPFR6212E Unknown error while creating
folder '{1}'.
User response:
TPFR6208E Failed opening the JCL file. Explanation
Explanation: {1}
User response: The name of a folder

TPFR6209E The host name is unknown. User response:

Explanation: TPFR6213E Failed to locate '{1}' because a

connection can not be established
User response: during a user exit.
TPFR6210E Cannot read from the file Create a connection to '{2}' and try
bbsjcl.cfg in the project directory. again.

Explanation:
Explanation
User response:
{1}
TPFR6211E Unknown error while creating file The name of a file or folder
'{1}'.
{2}
The name of a remote system
Explanation
User response:
{1}
The name of a file

8000-level messages
TPFR8020E No folder selected. User response:
Select a folder or a system filter
TPFR8027E Folder name cannot be empty.
with a filter string for the desired
Type in a name for the new folder.
location.
Explanation:
Explanation:
User response:
User response:
TPFR8028E Files are not a valid selection.
TPFR8021E No file specified.
Select the parent folder of the file.
Select a file or select a parent
folder and type in the name of a Explanation:
new file. User response:
Explanation: TPFR8029E The file name filter cannot be
User response: empty.
Specify a file filter (For example,
TPFR8022E File does not exist. *.*).
Select a file.
Explanation:
Explanation:
User response:
User response:
TPFR8030E The file '{1}' already exists in the
TPFR8023E No file or folder selected. folder '{2}'.
Select a file or folder. Enter a new unique name for the
Explanation: file.
User response:
Explanation
TPFR8024E File name cannot be empty.
Type in a name for the new file. {1}
The name of a folder
Explanation:

170 Developer for z/OS: Troubleshooting and Support

{2} TPFR8036E The name '{1}' contains invalid file
The name of the containing folder name characters.
Remove all invalid characters from
User response:
the file name.
TPFR8031E The folder '{1}' already exists in
the folder '{2}'.
Explanation
Enter a new unique name for the
folder. {1}
The name of a file
Explanation User response:
{1} TPFR8037E The name '{1}' contains invalid
The name of a folder folder name characters.
{2} Remove all invalid characters from
The name of the containing folder the folder name.

User response:
Explanation
TPFR8032E The folder '{1}' does not have the
necessary permissions to create {1}
the file '{2}'. The name of a folder
Select a parent folder that you User response:
have write permission on.
TPFR8038E The name '{1}' does not identify a
file in the folder '{2}'.
Explanation Specify a file in the folder '{2}'.
{1}
The name of a folder Explanation
{2} {1}
The name of a file The name of a file
User response: {2}
TPFR8033E The folder '{1}' does not have the The name of a folder
necessary permissions to create User response:
the folder '{2}'.
Select a parent folder that you TPFR8039E The file '{1}' does not exist in the
have write permission on. folder '{2}'.
Specify an existing file name.

Explanation
Explanation
{1}
The name of a folder {1}
The name of a file
{2}
The name of a folder {2}
The name of a folder
User response:
User response:
TPFR8034E File name cannot be empty.
Enter a file name. TPFR8040E The connection type '{1}' is invalid.
Specify a location on '{2}'.
Explanation:
User response: Explanation
TPFR8035E Folder name cannot be empty. {1}
Enter a folder name. A connection type
Explanation: {2}
The name of a remote system
User response:
User response:

Troubleshooting and support 171

TPFR8041E The host name '{1}' is invalid. Explanation
Specify a location on host '{2}'.
{1}
A file name
Explanation {2}
{1} A file-name format
The name of a remote system
User response:
{2}
The name of a remote system TPFR8048E The file '{1}' could not be created
in the folder '{2}'.
User response: Ensure the folder '{2}' exists and
TPFR8042E The path '{1}' does not exist. there is not already a file with the
Specify an existing path. name '{1}' in '{2}'.

Explanation Explanation
{1} {1}
An absolute path name The name of a file
{2}
User response:
The name of a folder
TPFR8043E The file is not remote.
User response:
Select a remote file. {1}
TPFR8049E The folder '{1}' could not be
Explanation created in the folder '{2}'.
Ensure the folder '{2}' exists and
{1} there is not already a folder with
The name of a file the name '{1}' in '{2}'.
User response:
TPFR8044E The folder is not remote.
Explanation
Select a remote folder. {1} {1}
The name of a folder
Explanation {2}
The name of a folder
{1}
The name of a folder User response:
User response: TPFR8050E The file is not local.
Select a local file.
TPFR8045E Multiple paths entered.
Enter a single location. Explanation:
Explanation: User response:
User response: TPFR8051E The folder is not local.
Select a local folder.
TPFR8046E The file extension '{1}' is invalid.
The file extension must be '{2}'. Explanation:
User response:
Explanation
TPFR8052E The filter '{1}' is ambiguous as
{1} a folder selection because it
The specified file-name extension contains filter strings for multiple
{2} folders ({2}, {3} ...).
A file-name extension Select a folder, or a filter that
references files from a single
User response: folder only.
TPFR8047E The file name '{1}' is invalid.
The file name must have the
format {2}.

172 Developer for z/OS: Troubleshooting and Support

Explanation TPFR8058E The folder '{1}' is selected twice.
{1} Remove one occurrence of '{1}'
The name of a filter from the selection.
{2}
The name of a folder Explanation
{3} {1}
The name of a folder The name of a folder
User response: User response:
TPFR8053E The selection contains a non-file. TPFR8059E The folder '{1}' does not have read
Select one or more files and clear access.
any folder selections. Select a folder that has read
access permission.
Explanation:
User response:
Explanation
TPFR8054E {1} contains duplicate name '{2}'.
{1}
Make sure the {1} field contains a
The name of a folder
list of unique names.
User response:
Explanation TPFR8060E The folder '{1}' does not have write
{1} access.
The name of a field Select a folder that has write
access permission.
{2}
The specified name
Explanation
User response:
{1}
TPFR8055E Multiple parents selected for new The name of a folder
folder(s).
Select one parent folder and type User response:
one or more new folder names. TPFR8061E The file '{1}' does not have read
Explanation: access.
Select a file that has read access
User response: permission.
TPFR8056E Multiple parents selected for new
file(s). Explanation
Select one parent folder and type
{1}
one or more new file names.
A file name
Explanation:
User response:
User response:
TPFR8062E The file '{1}' does not have write
TPFR8057E The file '{1}' is selected twice. access.
Remove one occurrence of '{1}' Select a file that has write access
from the selection. permission.

Explanation Explanation
{1} {1}
A file name A file name
User response: User response:
TPFVAL1000E Sample validation error message
Explanation:
User response:

Troubleshooting and support 173

 Messages for TPF Toolkit Utilities
These are the messages that pertain to TPF Toolkit Utilities.
TPFU9009E TPF launch user exit failed with RC Specify an existing folder with
{1}. write permission as the value of
TPF Toolkit perspective and views '{2}'.
will be disabled. Although other
Eclipse functions are not affected, Explanation
you must correct the cause of the
user exit failure to use the TPF {1}
Toolkit functions. Then, shut down A folder name
the workbench and restart. {2}
The name of an environment variable
Explanation User response:
{1} TPFU9014W The folder '{1}' referenced by the
A return code environment variable '{2}' is not
User response: local.
Specify an existing local folder as
TPFU9010W '{1}' is not a valid environment the value of '{2}'.
variable name.
Specify a non-null value as an
environment variable name. Explanation
{1}
Explanation A folder name
{2}
{1}
The name of an environment variable
A name specified as an environment variable name
User response:
User response:
TPFU9020E More than one password is
TPFU9011W '{1}' could not be resolved as an
associated with host {1} and user
environment variable.
ID {2}.
Ensure that the variable '{1}' has
Open the preferences page and
been defined and set.
update the saved passwords
information.
Explanation
{1} Explanation
The name of an environment variable
{1}
User response: The name of a remote system
TPFU9012W The folder '{1}' referenced by the {2}
environment variable '{2}' does not A user identifier
exist. User response:
Specify an existing, accessible
folder as the value of '{2}'. TPFU9021E A cached password is already
associated with host {1} and user
ID {2}.
Explanation
The input you just made is ignored.
{1}
A folder name
Explanation
{2}
{1}
The name of an environment variable
The name of a remote system
User response: {2}
TPFU9013W The folder '{1}' referenced by the A user identifier
environment variable '{2}' does not User response:
have write permission.

174 Developer for z/OS: Troubleshooting and Support

TPFU9025E Failed to run command '{1}'. The User response:
message from the command is
'{2}'. TPFU9050W The index that you are searching is
outdated. Do you want to update
the index and perform the search
Explanation
again?
{1}
Explanation:
The name of a command
{2} User response:
The error message returned by the command TPFU9051W Do you want to delete all index
User response: data from the removed index
locations?
TPFU9030I Running action {1} ...
Explanation:

Explanation User response:

{1} TPFVAL1000E Sample validation message
An action Explanation:
User response: This is a sample validation message.
TPFU9040E Invalid host name or IP address. User response:
No user response is required.
Explanation:

Messages for zSeries Utility

These messages pertain to the zSeries Utility.
TPFVAL1000E Sample validation messages. {3}
The message received from the remote system
Explanation:
This is a sample validation message. The remote system sent the message that is displayed.
User response: User response:
No user response is required. Verify that the host is available and that the host name
and port number are correct.
TPFZ1001E A connection to the {1} host
cannot be established. The host is TPFZ1003E The host name or the user ID
unknown. cannot be found.
Explanation:
Explanation The connection failed because the host name or user
ID is unknown.
{1}
The name of a remote system User response:
The remote system is unknown. Verify that the host name and user ID are correct and
available.
User response:
Verify that the host name is correct and that the host is TPFZ1004E User {1} cannot log on to the {2}
available. host.

TPFZ1002E A connection to the {1} host at the

{2} port could not be established.
Explanation
Message from host: {3} {1}
A user ID
Explanation {2}
The name of a remote system
{1}
The name of a remote system The entered password for user {1} for the {2} host is
incorrect.
{2}
The port number User response:

Troubleshooting and support 175

Verify that the password for the specified user ID is Verify that the host system has an SSH server running
correct. at the specified port.
TPFZ1005I Starting Remote System Explorer TPFZ1010E The SSH server on the {1} host at
host server using SSH. the {2} port is not compatible with
TPF Toolkit.
Explanation:
The Remote System Explorer is starting with the SSH
proxy. Explanation
User response: {1}
No user response is required. The name of a remote system
TPFZ1006E SSH key authentication could not {2}
be completed. The number of a communications port

Explanation: The version of SSH server that was found is not

Secure Shell key authentication could not be compatible with TPF Toolkit. TPF Toolkit requires that
completed. A password is required to establish the the SSH server be compliant with OpenSSH 3.4 or
SSH session and exchange public keys so that the next later.
key authentication request can be completed. User response:
User response: Check the version of the SSH server that is running on
Enter the password to exchange keys and continue. the host.

TPFZ1007E Password authentication failed. TPFZ1011E A connection to the SSH server on

the {1} host at the {2} port was not
Explanation: established.
The provided password is incorrect.
User response: Explanation
Enter the correct password for authentication.
{1}
TPFZ1008E No connection exists to the SSH The name of a remote system
server on the {1} host at the {2} {2}
port. The number of a communications port
User response:
Explanation Try your request again. If the connection fails again,
{1} obtain a trace by following the instructions in IBM
The name of a remote system Documentation, and analyze the output in the
{2} TPF_Toolkit_installaton_directory\eclipse
The number of a communications port \workspace\.metadata\ssh.log file.

An SSH connection does not exist at the specified port. TPFZ1012E Authentication failed during the
attempt to connect to the SSH
User response: server on the {1} host at the {2}
Verify that the host system has an SSH server running port.
at the specified port.
TPFZ1009E The SSH server was not found on Explanation
the {1} host at the {2} port.
{1}
The name of a remote system
Explanation
{2}
{1} The number of a communications port
The name of a remote system
If you are using password authentication, an incorrect
{2} user ID or password was used to access the system. If
The number of a communications port you are using key authentication, an invalid key or user
A Secure Shell server on the specified host at the ID was used.
specified port could not be found. User response:
User response: Correct the user ID or password, and try your request
again.

176 Developer for z/OS: Troubleshooting and Support

If you use key authentication, correct the user ID, {2}
delete the The message received from the remote system
TPF_Toolkit_installaton_directory\eclipse An error was encountered when disconnecting from
\workspace\.metadata\id_dsa file, and try your
the remote system.
request again.
User response:
TPFZ1013E An unknown error occurred while Try to disconnect again. If disconnection attempt fails
the connection to the SSH server again, contact IBM Software Support.
on the {1} host at the {2} port was
in use. TPFZ6001W A connection with the remote
system cannot be established.
Explanation Explanation:
The name of a remote system is not specified.
{1}
The name of a remote system User response:
{2} Specify the name of a remote system.
The number of a communications port TPFZ6002W The specified system cannot be
User response: used.
Try your request again. If the connection fails again, Explanation:
obtain a trace by using the instructions in IBM A system that already exists has been specified. You
Documentation, and analyze the output in the must specify an unused system.
TPF_Toolkit_installaton_directory\eclipse
\workspace\.metadata\ssh.log file. User response:
Specify another system.
TPFZ1014E Failed to disconnect from host {1}.
Message from host: {2}

Explanation
{1}
The name of a remote system

Host and runtime messages

The topics in this portion of the documentation contain information about the host and runtime messages.
Most IDs for host and runtime messages 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

Host messages for CRASTART

These host messages pertain to CRASTART.
CRAD0001I Config File:{1} This message shows the hhhh internal file number,
which is associated with a reading of the CRASERV
Explanation: configuration file. The config handle is for diagnostic
This message shows the configuration file name from purposes only.
which CRASERV receives the commands to run.
Response:
Response: No response is required.
No response is required.
CRAD0003I A:{1} {2}
CRAD0002I Config handle {1}
Explanation:
Explanation:

Troubleshooting and support 177

This message displays the standard command that is Explanation:
read from the CRASERV configuration file. This is a A CARMA user explicitly ended his or her connection.
diagnostic message.
Response:
Response: No response is required.
No response is required.
CRAD0010I CRASERV ended due to a normal
CRAD0004I C:{1} timeout.
Explanation: Explanation:
This message displays the dynamic allocation A CARMA user's session timed out after inactivity.
command that was read from the CRASERV
Response:
configuration file. This is a diagnostic message.
No response is required.
Response:
CRAD0011I Referback {1}
No response is required.
Explanation:
CRAD0005I {1} OPEN
A dynamic allocation was completed for the dsname
Explanation: data set by using a referback.
This message displays the dddddddd value that
Response:
CRASERV uses as a ddname.
See the previous allocation statement for details about
Response: the referback.
If the ddname is not the same as is expected, verify
CRAD1001W {1} Returned {2}, May be ABEND
that the correct ddname is specified in the CRASERV
{3}
configuration file.
Explanation:
CRAD0006I P:{1} {2}
A program started by CRASTART ended with an aaaaa
Explanation: return code, which might indicate a bbb abend code.
This message displays the program invocation
Response:
command that was read from the CRASERV
This might not indicate a problem, but if the started
configuration file. This is a diagnostic message.
program did not complete correctly, diagnose the
Response: failing program by using the bbb abend code.
No response is required.
CRAD1002W {1}
CRAD0007I {1} Attach
Explanation:
Response: The content of this returned message comes from
No response is required. dynamic allocation (BPXWDYN) that CRASERV called.
CRAD0008I {1} {2} Response:
Your response depends on the message contents.
Explanation:
This message displays the program name (cccccccc) CRAD1003W DYNALLOC return {1}
and parameters (p1 and p2) that CRASERV is about to
Explanation:
run. This is a diagnostic message.
This message shows the cccc return code from
Response: dynamic allocation (BPXWDYN) that CRASERV called.
Verify that any variable substitutions are correct.
Response:
CRAD0009I CRASERV ended by user initiated Your response depends on the message contents.
disconnect.

Host messages for Common Access Repository Manager (CARMA)

The following host messages pertain to the Common Access Repository Manager (CARMA).

0000-level messages
CRRZC0020E Internal Error: {0} Explanation
{0}
An error message.

178 Developer for z/OS: Troubleshooting and Support

The CARMA server encountered an unexpected • Have your systems programmer re-create the
internal error. CRADEF VSAM file from the source files as described
in the Host Configuration Guide.
User response:
Confirm that the VSAM files are correct. If you • Define a RAM in the CARDEF as described in the
modified the VSAM file, verify that you followed the CARMA Developer's Guide.
guidelines in the CARMA Developer's Guide. Otherwise, CRRZC0028E CRADEF read error
verify that the files were created properly by using the
directions in the Host Configuration Guide. Explanation:
The CARMA server encountered an error while it was
CRRZC0022E No RAMs defined for this locale reading the CRADEF configuration file.
Explanation: User response:
There are no RAMs defined that are associated with On the client, disconnect from CARMA, reconnect, and
the current language. try again. If the problem persists, have your systems
programmer verify that the file is accessible from the
User response user's account.
Do one of the following actions:
CRRZC0032E Invalid CRADEF record found: {0}
• In the client, change the language locale that is used
by CARMA. Explanation
1. Disconnect from the CARMA connection. {0}
2. Right-click the disconnected CARMA connection, An eight-character string that is the name of the
and select Properties. record.
3. In the Remote Locale menu, select a locale that The specified VSAM record in the CRADEF file is
is supported by the RAM. invalid.
• On the remote system, the systems programmer can User response:
update the configuration VSAM files on the remote Have your systems programmer correct the specified
system as defined in the CARMA Developer's Guide to record. For more information about the correct record
support the additional locale. format, see the CARMA Developer's Guide.
CRRZC0024E CRADEF could not be opened for CRRZC0034E Requested RAM not found: {0}
reading
Explanation: Explanation
The CARMA server was unable to open the CRADEF
{0}
VSAM file for reading.
The RAM ID number.
User response:
The client tried to connect to a RAM that is not defined
Have your systems programmer confirm that the file
on the remote system.
exists and is accessible from the user's account.
User response:
CRRZC0025E CRASTRS could not be opened for
In the client, disconnect the CARMA connection and
reading
restart the workspace. Then, connect to the CARMA
Explanation: connection before you try any other actions. If the
The CARMA server was unable to open the CRASTRS RAM you require is no longer listed, contact the
VSAM file for reading. systems programmer. The RAM might be removed or
the RAM ID number might be changed.
User response:
Have your systems programmer confirm that the file CRRZC0036E Could not load RAM module: {0}
exists and is accessible from the user's account.
CRRZC0026E No RAM records found in CRADEF Explanation
Explanation: {0}
No RAMs are defined in the CRADEF configuration The RAM load module.
VSAM file on the remote system. The CARMA server was unable to load the RAM load
module.
User response
Do one of the following actions:

Troubleshooting and support 179

User response Disconnect, reconnect, and try the action again. If you
Have your systems programmer confirm the following are using a custom remote system client, verify that
information: the initCARMA function was called. If the problem
persists, contact IBM Software Support.
• The RAM load module exists.
CRRZC0046E Failed attempting to load the RAM
• It is accessible from CARMA.
list
• It is accessible from the user's ID.
Explanation:
• It is a properly compiled DLL. CARMA did not successfully load the RAM list.
CRRZC0038E Could not load pointer to RAM User response:
function: {0} Disconnect, reconnect, and try the action again.
CRRZC0048E Out of memory
Explanation
Explanation:
{0} The CARMA address space is out of memory.
A RAM function.
User response:
The RAM does not have the specified function.
Have your systems programmer increase the memory
User response: that is allocated to CARMA address spaces.
If the function is required, recompile the RAM with
CRRZC0050W Record {0} in CRADEF does not
the required function. For more information about
have equivalent in CRASTRS for
developing a RAM, see the CARMA Developer's Guide.
this locale
CRRZC0040E Requested RAM ({0}) has not been
loaded Explanation
{0}
Explanation A record name.
{0} The specified record is not defined in the CRASTRS file
The RAM ID. for the current locale.
The function was not called because the compiled
RAM was not loaded by CARMA on the remote system. User response
User response: This message is only a warning and does not require
Disconnect, reconnect, and try the action again. If any action by the user.
you are using a custom remote system client, have If local specific strings are required for this record,
your systems programmer verify that the initRAM then create an appropriate record in the CRASTRS file
function was called. If the problem persists, contact to provide the strings. A CRASTRS record can also be
IBM Software Support. created to stop this warning from being written to the
CRRZC0042E Invalid CRASTRS record found: {0} log files. Contact your systems programmer for these
modifications.
Explanation If you are experiencing these errors while you are
using the CA Endevor RAM, have your systems
{0}
programmer install APAR PM56551 to fix this problem.
A CRASTRS record.
The CRASTRS record that is specified is invalid. CRRZC0052E Action {0} references unknown
parameter
User response:
Have your systems programmer or RAM developer, if
you are using a custom RAM, verify that the CRASTRS
Explanation
VSAM file was properly created and that the specified {0}
record is correct. An action name.
CRRZC0044E CARMA has not been initialized One or more parameters that are referenced by the
specified action do not exist in the CRADEF VSAM file.
Explanation:
The initCARMA function was not initialized. User response:
Have your RAM developer add any missing parameters
User response:
to the CRADEF VSAM file.

180 Developer for z/OS: Troubleshooting and Support

CRRZC0054E Action {0} references unknown Have your systems programmer confirm that the file
return type exists and is accessible from the users account.
CRRZC0062E CRAMSG read error
Explanation
Explanation:
{0} The CARMA server encountered an error white it was
An action name. reading the CRAMSG configuration file.
One or more return types that are referenced by the User response:
specified action do not exist in the CRADEF VSAM file. On the client, disconnect from CARMA, reconnect, and
User response: try again. If the problem persists, have your systems
Have your RAM developer add any missing return programmer verify that the file is accessible from the
types to the CRADEF VSAM file. user's account.

CRRZC0056E CRASTRS read error CRRZC0064E CRADEF error: Action 16 can not
have custom parameters and/or
Explanation: returns
The CARMA server encountered an error while it was
reading the CRASTRS configuration file. Explanation:
Action 16 is the performAction function and is used
User response: to call custom actions in CARMA. The parameters
On the client, disconnect from CARMA, reconnect, and that are associated with the called custom action are
try again. If the problem persists, have your systems used as parameters to action 16. Providing your own
programmer verify that the file is accessible from the custom parameters and returns interferes with the
user's account. passing of the custom action that is called, and is not
CRRZC0058E Neither the specified locale nor allowed.
EN_US 00037 could be found in User response:
CRASTRS Have the RAM developer remove the VSAM record for
Explanation: action 16 from CRADEF.
CARMA could not find a locale to use for this RAM. CRRZC0066E Invalid type specified in VSAM
record {0}
User response
Have your systems programmer or RAM developer Explanation
confirm that the CRASTRS VSAM file was properly
{0}
created. If the problem persists, do one of the
A VSAM record name.
following actions:
The type that is specified in the VSAM record is invalid.
• Have your RAM developer create the missing locales
in the CRASTRS VSAM file. User response:
• Change the properties on the CARMA connection to Have your RAM developer update the VSAM record
use the locale that is specified by the RAM. file to have one of the following types: "STRING",
"DOUBLE", "LONG", or "INT."
To change the language locale that is used by CARMA
in the client: CRRZC0068E Invalid default value in VSAM
record {0}
1. Disconnect from the CARMA connection.
2. Right click the disconnected CARMA connection, Explanation
and select Properties.
{0}
3. In the Remote Locale menu, select a locale that is A VSAM record name.
supported by the RAM.
The default value for the VSAM record is invalid.
CRRZC0060E CRAMSG not found
User response:
Explanation: Have your RAM developer ensure that the default
CARMA was unable to find the CRAMSG VSAM file. value of the VSAM record matches the type and length
User response: that is specified for that record.

Troubleshooting and support 181

 0100-level messages
CRRZC0101E Could not allocate memory Explanation:
The requested function is not supported by the RAM.
Explanation:
The RAM was unable to allocate memory. User response:
No action is required.
User response:
Have your systems programmer increase the memory CRRZC0108E Member is not a container
that is allocated to CARMA address spaces. Explanation:
CRRZC0102E TSO/ISPF Library functions not The function that was called expected a container as a
available parameter, and instead it received a member.
Explanation: User response:
The TSO or ISPF library function is not available to the In the client, refresh the parent container and try the
RAM. action again. If you are using a custom remote system
client, notify the developer. If the problem persists,
User response: notify your RAM developer.
Have your systems programmer confirm that the TSO
and ISPF environments are properly started with the CRRZC0109E Invalid parameter value
CARMA server. This process is explained in the Host Explanation:
Configuration Guide. A parameter with an invalid value was passed to the
CRRZC0103E Invalid member identifier action.
Explanation: User response:
The member identifier that is provided to the RAM Confirm that all parameters contain the correct values
is incorrect or out of date. This problem can occur and try the action again.
because the RAM was updated, or the RAM developer
CRRZC0110E Member cannot be updated
changed the way RAM IDs are represented to the
CARMA server. Explanation:
The target member was unable to update successfully.
User response:
In the client, refresh the parent container and try the User response:
action again. If the problem persists, contact your RAM In the client, disconnect, reconnect, and try the action
developer. again. If the problem persists, specify a different target
member. If the problem still persists, contact your
CRRZC0104E Cannot allocate (out of space) RAM developer.
Explanation: CRRZC0111E Member cannot be created
The RAM was unable to allocate memory.
Explanation:
User response: The member was not successfully created.
Have your systems programmer increase the memory
that is allocated to CARMA address spaces.
User response
CRRZC0105E Member not found In the client, attempt to do the following steps:
Explanation: 1. Refresh the parent container and confirm that the
The RAM was unable to locate the requested number. member is not already present.
User response: 2. Disconnect, reconnect, and try the create the
In the client, refresh the parent container and try member again.
again. If the problem persists, contact your RAM
3. Try to create a different member under a different
developer.
container.
CRRZC0106E Instance not found
If the problem persists, contact your RAM developer.
Explanation:
CRRZC0112E Not authorized
The RAM was unable to locate the requested instance.
Explanation:
User response:
The user is not authorized to do this action.
In the client, refresh the RAM and try again. If the
problem persists, contact the RAM developer. User response:
CRRZC0107E Function not supported

182 Developer for z/OS: Troubleshooting and Support

If you think this message is in error, disconnect, Explanation
reconnect, and try the action again. If the problem The target member has a record format that is
persists, contact your RAM developer. unsupported by this RAM.
CRRZC0113E Could not initialize Note: If you are using the sample RAMs provided with
Explanation: CARMA, they do not support the 'U' (undefined) record
The RAM did not initialize. format.

User response: User response:

In the client, disconnect from CARMA, reconnect, and If you are using the sample RAMs provided with
try again. If you are still unable to do the action, CARMA, work with members that have a record format
have your systems programmer confirm that you have of FB (fixed block) or VB (variable block).
access to all files that are needed by the RAM. CRRZC0119E Invalid LRECL
If you still experience problems, contact your RAM
developer. Explanation:
LRECL is the length of the record. For the
CRRZC0114E Could not terminate RAM putMember function, the client specifies the
Explanation: maximum length of the record. For the RAM
The RAM was unable to terminate properly. createMember function, the length of the record of
the created member is returned. For some reason, the
User response: length of the record is invalid.
No action is required.
User response:
CRRZC0115E Resource out of sync Download a new copy of the file from the RAM, and try
Explanation: the action again. If the problem persists, contact your
The RAM is reporting that the resource is out of sync. RAM developer.

User response: CRRZC0120E Invalid metadata key

Refresh the parent container, and try the action again. Explanation:
If the problem persists, contact your RAM developer. The metadata key is the key in a key-value pair to a
CRRZC0116E File locked property of a CARMA resource. The requested key is
not valid.
Explanation:
The file is locked and is most likely in use by another User response:
user or process. Refresh the properties of the CARMA resource. If the
problem persists, contact the RAM developer.
User response:
You can wait until the file is freed and try CRRZC0121E Cannot update property value
again. Additionally, verify that you have the correct Explanation:
permissions to access the file. The property value was unable to update. It is most
CRRZC0117E Specified next record out of range likely read only.

Explanation: User response:

The client is requesting a starting record number No action is required.
that does not exist. The client is calling the CRRZC0122E Invalid metadata value
extractMember function, which retrieves chunks of
records that start with a specific record number. In Explanation:
this case, the starting record number parameter is an The metadata value was invalid.
invalid number that does not correspond with a record User response:
number. Try the operation again with a valid metadata value.
User response: If you are unsure of correct metadata values, contact
In the client, attempt to open the file again. If the your RAM developer.
problem persists, contact your RAM developer. If you CRRZC0123E Property value is read-only
are using a custom remote system client, contact your
client developer. Explanation:
The target metadata value is read-only and cannot be
CRRZC0118E Unsupported record format updated.
User response:
No action is required.

Troubleshooting and support 183

CRRZC0124E Requested member is empty CRRZC0130E Versioning not supported on
member
Explanation:
The RAM attempted to open a member that was Explanation:
empty. The selected CARMA member does not support the
Show History action. This message does not mean
User response:
that the Show History action is disabled for all
If you believe that this message is in error, contact
members.
your RAM developer.
User response:
CRRZC0125E Empty instance
No action is required.
Explanation:
CRRZC0196E Could not setup ISPF variables
The repository instance was unable to expand because
it was empty. Explanation:
The RAM encountered an error it was trying to access
User response:
ISPF variables.
No action is required.
User response:
CRRZC0126E No members found
In the client, disconnect from CARMA, reconnect, and
Explanation: try again. If the problem persists, confirm that the
The container was unable to expand because it was ISPF system is properly set up at CARMA startup by
empty. reviewing the Host Configuration Guide.
User response: CRRZC0197E (encapsulated ISPF/LMF error
No action is required. message)
CRRZC0127E Reset error Explanation:
The RAM encountered an error from an ISPF or
Explanation:
LMF system call. This ISPF or LMF error message is
An error occurred while the CARMA server was
provided by the RAM.
resetting the RAM.
User response:
User response:
Check the response to the ISPF or LMF message
In the client, disconnect and reconnect from CARMA
that is included. Additionally, confirm that the ISPF or
and try the action again. If the problem persists,
LMF system is properly set up at CARMA startup by
contact your RAM developer.
reviewing the Host Configuration Guide.
CRRZC0128E Delete error
CRRZC0198E Unable to access log file
Explanation:
Explanation:
The RAM encountered an error it was trying to
The RAM was unable to access the log file.
complete a Delete operation.
User response:
User response:
Confirm that the CARMALOG is properly set up and that
In the client, refresh the parent container to confirm
the user has access to the log file. If the problem
that the delete was unsuccessful and try again.
persists, contact your RAM developer.
CRRZC0129E Member/Version is read-only
CRRZC0199E Unknown RAM error
Explanation:
Explanation:
Version is a previous view of the member in the
The RAM encountered an unexpected error.
CARMA Version History view. The target member or
version is read-only. User response:
In the client, disconnect from CARMA, reconnect, and
User response:
try again. If the problem persists, contact your RAM
No action is required.
developer.

4000-level messages
CRRZC4011W Could not load RAM. Not adding it User response:
to the list. If the failed RAM is not required, no action is required.
Otherwise, make sure that the VSAM configuration
Explanation: is correct and that the target RAM is accessible to
The initRAM function call cannot be completed the CARMA user. If you are using a custom RAM,
successfully, so the RAM was not loaded.

184 Developer for z/OS: Troubleshooting and Support

make sure that the initRAM function is operating as CRRZC4042W Warning: Attempt to disable action
expected. Check the CARMALOG or job spool for RAM that does not exist in VSAM record
initialization errors. {0}
CRRZC4038W Could not terminate the RAM.
Explanation
Explanation:
The terminateRAM function call returned an error {0}
from the RAM. If the RAM has state information that the VSAM record name
must be saved, this error can cause problems. The VSAM configuration erroneously tries to disable
User response: an action that does not exist. This situation can occur
If you are using a non-custom RAM, no action is when you are using an earlier version of the CARMA
required . If you are using a custom RAM, check with remote system code, where the disabled action is not
your RAM developer to verify that this error is not a yet supported.
problem. User response:
CRRZC4039I Custom action {0} disabled. Have your RAM developer confirm that the correct
action IDs are disabled.
Explanation CRRZC4043W Warning: No prompt given for
VSAM record {0}
{0}
The ID of a custom action. Explanation:
A prompt was not supplied for the custom parameter.
The action with the displayed action ID was disabled in
CARMA uses the custom parameter name in place of
the configuration VSAM file.
the prompt when it is asking for the custom parameter.
User response:
User response:
No action is required. You can find a list of action IDs in
If you want a prompt, have your RAM developer add it
the CARMA Developer's Guide.
to the VSAM record.
CRRZC4040I VSAM record {0} requires '|'
CRRZC4044W Warning: No description given for
after parameter list for 6.0.1.x
VSAM record {0}
compatibility
Explanation: Explanation:
The specified VSAM action record does not have a '|' A description was not provided for the custom
character after the list of parameters, or has an empty parameter.
parameter and return list. Earlier versions of CARMA User response:
required the separating character even if a return list No action is required, but if you want a description,
was not specified. have your RAM developer add it to the custom
User response: parameter.
No action is required. CRRZC4045W Warning: Could not find RAM(s) for
CRRZC4041W locale {0}, using default locale of
Warning: {0} Perform Action
EN_US 00037
(id=16) can not be disabled
Explanation:
Explanation:
No RAMs were found that use the specified locale.
The VSAM configuration erroneously tries to disable
CARMA is using the default locale instead. A RAM
the performAction call, which is used to call custom
is enabled only for the locales specified. This action
actions. This action cannot be disabled in the VSAM
allows RAM developers to release multiple versions for
configuration.
different locales, and display only one at a time to the
User response: user.
Have your RAM developer remove the record to
User response:
disable action 16. Have your RAM developer confirm
Specify a different locale under the CARMA connection
that the record to disable action 16 was not a
properties. If you do not want to use RAMs for the
typographical error and that the correct action IDs
default locale, have your RAM developer add support
are disabled. A list of action IDs can be found in the
for your locale.
CARMA Developer's Guide.
CRRZC4050I RAM {0} does not support function
{1} ({0})

Troubleshooting and support 185

Explanation: No action is required. To remove this error message,
The specified function is not supported by the RAM. have your RAM developer either implement the new
New functions added to the CARMA API can cause this functions or disable them in the configuration VSAM
condition. This condition is not an error. files.
User response:

Host messages for Code Review for COBOL and PL/I

These are the host messages that pertain to Code Review .
The messages in this section are not shown to you on a workstation. They exist only in the workspace log
on the host system.
CRRZW0000E An error occurred while reading User response
the rule file {0}. Error message: {1}
1. Verify that PDS and the path of the workspace are
Explanation: specified correctly in the input data.
The code review application cannot read the rule file.
2. Verify that the PDS members exist and that the user
has permission to access the PDS.
User response 3. Verify that the workspace exists and that the user
1. Verify that the path of the rule file is specified has permission to access it.
correctly in the input data.
CRRZW0003E An error occurred while retrieving
2. Verify that the rule file exists in the specified the PL/I include file {0}. Error
directory, that the user has permission to access it, message: {1}
and that it contains readable text encoded in UTF-8
format. Explanation:
The code review application cannot access a PL/I
3. If the problem persists, export the rule file again include file.
and upload it to z/OS UNIX System Services.
CRRZW0001E An error occurred while closing User response
the rule file {0}. Error message: {1} When the code application parses a PL/I program it
Explanation: accesses PL/I include files. This includes PL/I include
The code review application cannot close the rule file. files that are shipped with the compiler:
1. Verify that the path of the property group file is
User response specified correctly in the input data.
2. Verify that the path of the include file is specified
1. Verify that the path of the rule file is specified
correctly in the property group file. To do this,
correctly in the input data.
open the LOCAL PL/I property group in the product
2. Verify that the rule file exists in the specified workbench. Then verify that the path of the include
directory, that the user has permission to access it, file is specified in the SYSLIB field of the property
and that it contains readable text encoded in UTF-8 group. If not, then enter the correct path, close the
format. property group, and go to Step 4.
3. If the problem persists, export the rule file again 3. Verify that the include file specified in the error
and upload it to z/OS UNIX System Services. message exists in the specified directory, and that
the user has permission to access it.
CRRZW0002E An error occurred while
transferring PDS members to the 4. If the problem persists, export the property group
workspace. file again and upload it to z/OS UNIX System
Services.
Explanation:
The code review application transfers the members of CRRZW0004E An error occurred while retrieving
the PDS to an Eclipse workspace in z/OS UNIX System the COBOL copybook file {0}. Error
Services for processing. An error occurred during a message: {1}
member transfer.
Explanation:
The code review application cannot access a COBOL
copybook.

186 Developer for z/OS: Troubleshooting and Support

User response 2. If the problem persists, export the property group
When the code application parses a COBOL program file again and upload it to z/OS UNIX System
it accesses COBOL copybooks. This includes COBOL Services.
copybooks that are shipped with the compiler: CRRZW0007E An error occurred while setting up
1. Verify that the path of the property group file is the property group.
specified correctly in the input data. Explanation:
2. Verify that the path of the copybook is specified The code review application cannot read the property
correctly in the property group file. To do this, group file.
open the LOCAL COBOL property group in the
product workbench. Then verify that the path of
User response
the copybook is specified in the SYSLIB field of the
property group. If not, then enter the correct path, 1. Verify that the property group file is a properly
close the property group, and go to Step 4. formatted XML file and that the user has permission
3. Verify that the copybook specified in the error to access it.
message exists in the specified directory, and that 2. If the problem persists, export the property group
the user has permission to access it. file again and upload it to z/OS UNIX System
4. If the problem persists, export the property group Services.
file again and upload it to z/OS UNIX System 3. Verify that the version of the client is not later than
Services. the version of the host Batch Runtime.
CRRZW0005E An error occurred while reading CRRZW0008E The code review application
file {0}. The default mapping will cannot find the workspace.
be used.
Explanation:
Explanation: The code review application cannot initialize the
The code review application cannot read the z/OS Eclipse workspace.
File System Mapping file (that is, the file extension
mapping file) that is specified in the input data. User response
The code review application uses the Eclipse
User response workspace as a work area. Verify that the workspace
exists and is accessible:
1. Verify that the path of the z/OS File System
Mapping file is specified correctly in the input data. 1. Verify that the path of the workspace is specified
2. Verify that the z/OS File System Mapping file correctly in the input data.
exists in the specified directory, that the user has 2. Verify that the workspace exists and that the user
permission to access it, and that it is a correctly has permission to access it.
formatted zip file. 3. Try the operation again.
3. If the problem persists, export the z/OS File System 4. Check the workspace log for errors.
Mapping file again and upload it to z/OS UNIX
System Services. 5. If the problem persists, contact IBM Software
Support.
CRRZW0006E An error occurred while
associating the property group {0} CRRZW0009E An error occurred while setting up
with the data set {1}. custom rule definitions.

Explanation: Explanation:
The code review application extracted a property The code review application cannot read the custom
group from the property group file but cannot rules and categories file (that is, the custom validation
associate the property group with a data set. rules file) that is specified in the input data.

User response User response

1. Verify that the property group file is a properly 1. Verify that the path of the custom rule and
formatted XML file and that the user has permission categories file is specified correctly in the input
to access it. data.
2. Verify that the custom rule and categories file
exists in the specified directory, that the user

Troubleshooting and support 187

 has permission to access it, and that it contains 2. Verify that the rule file exists in the specified
readable text. directory, that the user has permission to access it,
3. If the problem persists, export the custom rules and that it contains readable text encoded in UTF-8
and categories file again and upload it to z/OS UNIX format.
System Services. 3. If the problem persists, export the rule file again
and upload it to z/OS UNIX System Services.
CRRZW0010E Software analysis cannot
continue. The {0} parameter was CRRZW0014E Software analysis cannot
not specified. continue. The baseline {0} does not
exist.
Explanation:
A required input parameter to the code review Explanation:
application is missing. The code review application cannot find the baseline
file.
User response:
Verify that the parameter identified by the error
message is specified correctly in the input data. User response
CRRZW0011E Software analysis cannot 1. Verify that the path of the baseline file is specified
continue. The rule file {0} does not correctly in the input data.
exist. 2. Verify that the baseline file exists in the specified
Explanation: directory and that the user has permission to
The code review application cannot find the rule file. access it.
3. If the problem persists, export the baseline file
User response again and upload it to z/OS UNIX System Services.

1. Verify that the path of the rule file is specified CRRZW0015E Software analysis cannot
correctly in the input data. continue. The list file {0} does not
exist.
2. Verify that the rule file exists in the specified
directory and that the user has permission to
access it. Explanation
3. If the problem persists, export the rule file again {0}
and upload it to z/OS UNIX System Services. 0
CRRZW0012E Software analysis cannot CRRZW0016W Non-fatal warnings occurred while
continue. The data set {0} does not processing the list file {0}.
exist.
Explanation: Explanation
The code review application cannot find the PDS. {0}
0
User response CRRZW0017W The list file record does not specify
1. Verify that PDS is specified correctly in the input a data set name. The record will be
data. ignored: {0}
2. Verify that the PDS exists.
Explanation
CRRZW0013E Software analysis cannot
continue. The rule file {0} does not {0}
contain any rules. 0

Explanation: CRRZW0018W The list file record does not

The code review application cannot process the rule contain a language. The record will
file. be ignored: {0}

User response Explanation

1. Verify that the path of the rule file is specified {0}
correctly in the input data. 0

188 Developer for z/OS: Troubleshooting and Support

CRRZW0019W The list file record has an illegal Explanation
value {0} for the select keyword.
{0}
The record will be treated as if
0
SELECT=INCLUDE.
CRRZW0022E An error occurred while processing
Explanation the list file {0}. Error message: {1}

{0}
0
Explanation
{0}
CRRZW0020W The list file record specifies a data
0
set that does not exist. The record
will be ignored: {0} {1}
1
Explanation CRRZW0023W The list file record specifies an
unsupported language. The record
{0}
will be ignored: {0}
0
CRRZW0021W The list file record specifies a Explanation
member that does not exist. The
record will be ignored: {0} {0}
0

Host messages for Configuration Utility

The following host messages pertain to the Configuration Utility.

FEKM messages
FEKM001A Java directory invalid Unable to locate &RDZHLQ..SFEKLOAD. The high-level
qualifier that is specified might be invalid.
Explanation:
The Java location field does not contain a valid User response:
directory name, or the directory that is specified does Correct the high-level qualifier for the SFEKLOAD data
not exist or does not contain /bin/java. This error set.
might also occur if your TSO region size is too small
FEKM006A Data set name invalid
and Java failed to run.
Explanation:
User response:
The data set name does not comply with z/OS
Correct the Java directory name or ensure that the
standards.
TSO region size is 128M (SIZE=128000).
User response:
FEKM002A Directory invalid Specify a valid data set name.
Explanation: FEKM007I Invalid Delete
The directory name that is specified for configuration
files contains invalid syntax. Explanation:
The DEFAULT user ID cannot be deleted.
User response:
Correct the directory name. User response:
No action is required. This message is for informational
FEKM003A Directory invalid purposes only.
Explanation: FEKM011I Invalid Work Flow
The directory name that is specified for the installation
does not exist. Explanation:
The DEFAULT user ID does not have a work flow.
User response:
Correct the directory name. User response:
Run the G Generate configuration jobs to create a work
FEKM004A HLQ invalid flow.
Explanation: FEKM015I Invalid Prefix Command

Troubleshooting and support 189

Explanation: Use a valid prefix command.
Valid prefix commands are C, D, F, L, N, S, or W.
FEKM019I Invalid Prefix Command
User response:
Explanation:
Use a valid prefix command.
Valid prefix commands are N or S until configured.
FEKM016I Invalid Prefix Command
User response:
Explanation: Use a valid prefix command.
Valid prefix commands are C or V.
FEKM020I No Log Available
User response:
Explanation:
Use a valid prefix command.
There is no log available for this work flow request
FEKM017I Invalid Prefix Command because the request was not Actioned.
Explanation: User response:
Valid prefix commands are A, C, or E Action the work flow request.
User response:

0000-level messages
FEK0000W Message {1} Undefined Explanation:
An internal error occurred.
Explanation:
This message is an internal warning. User response:
Contact IBM Software Support.
User response:
If this message is issued with an error, contact IBM FEK0006I XML {1} class processing complete
Software Support. Explanation:
FEK0001I {1} This message is for informational purposes only.
Explanation: User response:
This message is for informational purposes only. No action is required.
User response: FEK0007E Unknown XML class specified:
No action is required. line={1} text={2}
FEK0002E Malformed XML header: line={1} Explanation:
text={2} An internal error occurred.
Explanation: User response:
An internal error occurred. Contact IBM Software Support.
User response: FEK0008E Invalid command environment
Contact IBM Software Support. attribute: environment={1}
xmlid={2}
FEK0003E Malformed XML attribute: line={1}
text={2} Explanation:
An internal error occurred.
Explanation:
An internal error occurred. User response:
Contact IBM Software Support.
User response:
Contact IBM Software Support. FEK0009E EXECIO for {1} failed: rc={2}
FEK0004E Incorrect XML class terminator: Explanation:
line={1} text={2} An internal error occurred.
Explanation: User response:
An internal error occurred. Contact IBM Software Support.
User response: FEK0010E '{1}' Trapped on line {2}, rc {3} -
Contact IBM Software Support. '{4}'
FEK0005E New XML class started before Explanation:
class end: line={1} text={2} An internal error occurred.

190 Developer for z/OS: Troubleshooting and Support

User response: Review the work flow routine and any other associated
Contact IBM Software Support. messages. Make the necessary corrections and run the
routine again.
FEK0011E Unrecoverable error - processing
terminates FEK0018E Member {1} of data set {2} not
found
Explanation:
An internal error occurred. Explanation:
An internal error occurred.
User response:
Contact IBM Software Support. User response:
Contact IBM Software Support.
FEK0012I FEK Processing completed
successfully for {1} FEK0019E Invalid selection
Explanation: Explanation:
This message is for informational purposes only. The selected value is invalid.
User response: User response:
No action is required. Select a valid command.
FEK0013E EXECIO DISKR from {1} failed: FEK0020I Copy attempt FAILED, attempt to
rc={2} copy to user directory
Explanation: Explanation:
An internal error occurred. The copy to the user directory failed.
User response: User response:
Contact IBM Software Support. Be sure that the user has write access to the specified
directory or that there is available space in that
FEK0014E EXECIO DISKW to {1} failed: rc={2}
directory.
Explanation:
FEK0030I Work Flow actioned by {1} on {2}
An internal error occurred.
{3}
User response:
Explanation:
Contact IBM Software Support.
This message is for informational purposes only.
FEK0015W FEK routine {1} gave bad return
User response:
code {2}
No action is required.
Explanation:
FEK0031I Work Flow processing commands
The work flow routine run failed.
from: {1}
User response:
Explanation:
Review the work flow routine and any other associated
This message is for informational purposes only.
error messages. Make the necessary corrections and
run the routine again. User response:
No action is required.
FEK0016E z/OS UNIX command {1} gave bad
return code {2} FEK0032I Copy from {1} to {2} completed
successfully
Explanation:
The work flow routine run failed. Explanation:
This message is for informational purposes only.
User response:
Review the work flow routine and any other associated User response:
messages. Make the necessary corrections and run the No action is required.
routine again.
FEK0033E Copy from {1} to {2} failed , rc={3}
FEK0017E TSO command {1} gave bad return
Explanation:
code {2}
An internal error occurred.
Explanation:
User response:
The work flow routine run failed.
Contact IBM Software Support.
User response:

Troubleshooting and support 191

 1000-level messages
FEK1001I File {1} created. User response:
No action is required.
Explanation:
This message is for informational purposes only. FEK1010I Job {1}
User response: Explanation:
No action is required. This message is for informational purposes only.
FEK1002I HFS file {1} created. User response:
No action is required.
Explanation:
This message is for informational purposes only. FEK1011I ... submitted
User response: Explanation:
No action is required. This message is for informational purposes only.
FEK1003I Panel {1} displayed. User response:
No action is required.
Explanation:
This message is for informational purposes only. FEK1013I Command {1}
User response: Explanation:
No action is required. This message is for informational purposes only.
FEK1004I PDS file {1} created. User response:
No action is required.
Explanation:
This message is for informational purposes only. FEK1014I ...issued in environment {1}, rc=
{2}
User response:
No action is required. Explanation:
This message is for informational purposes only.
FEK1005I OCOPY {1} to {2}
User response:
Explanation: No action is required.
This message is for informational purposes only.
FEK1015I Action manually completed by {1}
User response:
on {3} {3}
No action is required.
Explanation:
FEK1006I {1} This message is for informational purposes only.
Explanation: User response:
This message is for informational purposes only. No action is required.
User response: FEK1016I Command response: {1}
No action is required.
Explanation:
FEK1007I Unknown file type specified in file This message is for informational purposes only.
class.
User response:
Explanation: No action is required.
This message is for informational purposes only.
FEK1017I Syscall environment not available.
User response:
No action is required. Explanation:
This message is an internal warning.
FEK1008I Run REXX exec {1}
User response:
Explanation: If this message is issued with an error, contact IBM
This message is for informational purposes only. Software Support.
User response: FEK1018I All returns are 0, this means the
No action is required.
dir exists.
FEK1009I Include ISPF skeleton {1} Explanation:
Explanation: This message is for informational purposes only.
This message is for informational purposes only.

192 Developer for z/OS: Troubleshooting and Support

User response: User response:
No action is required. No action is required.
FEK1019I Retval= {1} errono= {2} FEK1023I Could not create {1}.
Explanation: Explanation:
This message is for informational purposes only. This message is issued with message FEK1024I. The
specified directory could not be created.
User response:
No action is required. User response:
The systems programmer must modify user authority
FEK1020I The directory probably does
so the user can create this directory.
not exist, attempting to create
directory FEK1024I ...ensure you have authority to
create this directory.
Explanation:
This message is for informational purposes only. Explanation:
This message is issued in conjunction with message
User response:
FEK1023I. The specified directory could not be
No action is required.
created.
FEK1021I After mkdir rc= {1}, retval= {2},
User response:
errorno= {3}
The systems programmer must modify user authority
Explanation: so the user can create this directory.
This message is for informational purposes only.
FEK1025I Directory {1} created.
User response:
Explanation:
No action is required.
This message is for informational purposes only.
FEK1022I lrc= {1}, retval= {2}, errorno= {3}
User response:
Explanation: No action is required.
This message is for informational purposes only.

FEKR messages
FEKR000W Message {1} Undefined Contact IBM Software Support.
Explanation: FEKR004E Incorrect XML class terminator:
This message is for informational purposes only. line={1} text={2}
User response: Explanation:
No action is required. An internal error occurred.
FEKR001I {1} User response:
Contact IBM Software Support.
Explanation:
This message is for informational purposes only. FEKR005E New XML class started before
class end: line={1} text={2}
User response:
No action is required. Explanation:
An internal error occurred.
FEKR002E Malformed XML header: line={1}
text={2} User response:
Contact IBM Software Support.
Explanation:
This message is for informational purposes only. FEKR006I XML Class parsing complete for {1}
name {2}
User response:
No action is required. Explanation:
This message is for informational purposes only.
FEKR003E Malformed XML attribute: line={1}
text={2} User response:
No action is required.
Explanation:
An internal error occurred. FEKR007E Unknown XML class specified:
line={1} text={2}
User response:

Troubleshooting and support 193

Explanation: Explanation:
An internal error occurred. An internal error occurred.
User response: User response:
Contact IBM Software Support. Contact IBM Software Support.
FEKR008E Invalid command environment FEKR101I File {1} created.
attribute: environment={1}
Explanation:
xmlid={2}
This message is for informational purposes only.
Explanation:
User response:
An internal error occurred.
No action is required.
User response:
FEKR117I Syscall environment not available.
Contact IBM Software Support.
Explanation:
FEKR009E EXECIO for {1} failed: rc={2}
This message is an internal warning.
Explanation:
User response:
An internal error occurred.
If this message is issued with an error, contact IBM
User response: Software Support.
Contact IBM Software Support.
FEKR118I All returns are 0, this means the
FEKR010E '{1}' Trapped on line {2}, rc {3} - dir exists.
'{4}'
Explanation:
Explanation: This message is for informational purposes only.
An internal error occurred.
User response:
User response: No action is required.
Contact IBM Software Support.
FEKR119I Retval= {1} errono= {2}
FEKR011E Unrecoverable error - processing
Explanation:
terminates
This message is for informational purposes only.
Explanation:
User response:
An internal error occurred.
No action is required.
User response:
FEKR120I The directory probably does
Contact IBM Software Support.
not exist, attempting to create
FEKR012I Processing completed: RC={1} directory
Explanation: Explanation:
This message is for informational purposes only. This message is for informational purposes only.
User response: User response:
No action is required. No action is required.
FEKR013E EXECIO DISKR from {1} failed: FEKR121I After mkdir rc= {1}, retval= {2},
rc={2} errorno= {3}
Explanation: Explanation:
An internal error occurred. This message is for informational purposes only.
User response: User response:
Contact IBM Software Support. No action is required.
FEKR014E EXECIO DISKW to {1} failed: rc={2} FEKR122I lrc= {1}, retval= {2}, errorno= {3}
Explanation: Explanation:
An internal error occurred. This message is for informational purposes only.
User response: User response:
Contact IBM Software Support. No action is required.
FEKR015W Routine {1} gave bad return code FEKR123I Could not create {1}.
{2}
Explanation:

194 Developer for z/OS: Troubleshooting and Support

This message is issued with message FEKR124I. The Explanation:
specified directory could not be created. This message is for informational purposes only.
User response: User response:
The systems programmer must modify user authority No action is required.
so the user can create this directory.
FEKR204E z/OS UNIX command {1} failed.
FEKR124I ...ensure you have authority to
Explanation:
create this directory.
The work flow routine run failed.
Explanation:
User response:
This message is issued with message FEKR123I. The
Review the work flow routine and any other associated
specified directory could not be created.
messages. Correct the errors and run the routine
User response: again.
The systems programmer must modify user authority
FEKR205I z/OS UNIX command {1}
so the user can create this directory.
Returned:
FEKR125I Directory {1} created.
Explanation:
Explanation: This message is for informational purposes only.
This message is for informational purposes only.
User response:
User response: No action is required.
No action is required.
FEKR206I {1}
FEKR201I Java {1} ICSF and RACF
Explanation:
Explanation: This message is for informational purposes only.
This message is for informational purposes only.
User response:
User response: No action is required.
No action is required.
FEKR202I Java {1} ICSF and no RACF

Host messages for RSE daemon and RSE server

These host messages pertain to the RSE daemon or the RSE server.

FEK messages
FEK001I RseDaemon being initialized in {0} System programmer response:
bit mode No action is required.
FEK003I Stop command being processed
Explanation
Explanation:
{0} The operator entered the STOP command.
The addressing mode: 31 or 64.
System programmer response:
This message is shown when the server daemon is No action is required.
started. It provides information about the addressing
mode: 31 or 64. FEK004I RseDaemon: Max Heap
Size={0}MB and private AS
System programmer response: Size={1}MB
No action is required.
FEK002I RseDaemon started. (port={0}) Explanation
{0}
Explanation The JVM maximum heap size.
{0} {1}
The daemon port for each client user to log on. The private address space size of the application.
This message indicates that the daemon was started This message provides the JVM maximum heap size
successfully and provides information about the and the private address space size of the application.
daemon port for each client user to log on.

Troubleshooting and support 195

System programmer response: This message provides the location of the active
No action is required. modules that are related to the product server.
FEK005I Server process started. System programmer response:
(processId={0}) No action is required.
FEK100E Daemon port/timeout value must
Explanation be digits
{0} Explanation:
The process ID with which the started server The daemon port and timeout values are provided as
process is associated. a parameter of the JVM start command and must be
This message provides information about the process digits.
ID with which the started server process is associated System programmer response:
System programmer response: Correct the daemon port and timeout value in the
No action is required. started procedure.

FEK009I RseDaemon is waiting for the FEK101E JRE {0} or higher required
server process to start.
Explanation: Explanation
This message is issued every time that it takes more {0}
than 30 seconds for the server process to start. The minimum level of the JRE that is required to
run the daemon.
System programmer response:
If the server process never starts, contact IBM This message provides the minimum level of the JRE
Software Support. that is required to run the daemon.
FEK010I (rse.env location = {0}) System programmer response:
Change the rse.env file to use the JRE that the error
Explanation message indicates.

{0} FEK102E REGISTRATION HAS BEEN

The location of the active rse.env file. DENIED FOR PRODUCT WITH {0}
DUE TO {1}
This message provides the location of the active
rse.env file.
Explanation
System programmer response:
{0}
No action is required.
The name of the invalid argument in the console
FEK011I (log directory = {0}) command. The only valid argument name is
Process_ID.
Explanation The console command contains invalid arguments.
{0} System programmer response:
The location of the rsedaemon.log and Enter the correct process ID for the command.
rseserver.log.
FEK103E Almost Disk-Full in {0}
This message provides the location of
rsedaemon.log and rseserver.log. When the
enable.standard.log parameter is set to true in Explanation
rse.env, the standard out and error logs are also in {0}
the same directory. The directory that is almost full.
System programmer response: The z/OS UNIX System Services directory that is
No action is required. shown in the message is almost full. This message is
issued when the log becomes 80% full.
FEK012I (RSE home directory = {0})
System programmer response:
Explanation To prevent the loss of log contents, increase the size of
the directory.
{0}
The location of the active modules.

196 Developer for z/OS: Troubleshooting and Support

FEK104E Maximum number of processes Explanation
has been reached
{0}
Explanation: The reason code. For a list of reason codes, see
The maximum number of server processes was the following topic in XL C/C++ Run-Time Library
reached. Reference (SA22-7821): socket.
System programmer response: The TCP/IP socket failed for the reason code that is
Increase the value that is specified for the specified in the message.
maximum.threadpool.process parameter in the
System programmer response:
rse.env file.
Contact IBM Software Support.
FEK105E Error in sending audit data (rc={0})
FEK111E setsockopt() failed. reason=({0})

Explanation Explanation
{0}
{0}
The reason code. For a list of reason codes, see
The reason code. For a list of reason codes, see
the following topic in XL C/C++ Run-Time Library
the following topic in XL C/C++ Run-Time Library
Reference (SA22-7821): send.
Reference (SA22-7821): setsockopt.
An error occurred when the server process tried to
The TCP/IP setsockopt call failed for the reason
send audit data to the daemon process.
code that is specified in the message.
System programmer response:
System programmer response:
Contact IBM Software Support.
Contact IBM Software Support.
FEK106E No Resource Bundle of {0}
FEK112E bind() failed. reason=({0})

Explanation Explanation
{0}
{0}
0
The reason code. For a list of reason codes, see
System programmer response: the following topic in XL C/C++ Run-Time Library
Reference (SA22-7821): bind.
FEK107E Almost Disk-Full in {0}, existing {1}
removed The TCP/IP bind call failed for the reason that is
specified in the message.
Explanation System programmer response:
Contact IBM Software Support.
{0}
The directory that is almost full. FEK113E listen() failed. reason=({0})
{1}
The log file to be removed to clear space in the Explanation
directory.
{0}
This message is issued when the directory that The reason code. For a list of reason codes, see
contains the ffs*.log and rsecomm*.log files the following topic in XL C/C++ Run-Time Library
becomes 95% full. The log file that is shown in the Reference (SA22-7821): listen.
message was removed to clear space in the directory.
The TCP/IP listen call failed for the reason that is
System programmer response: specified in the message
To determine the timeframe of messages that were
System programmer response:
removed from the log file, see the rseserver.log
Contact IBM Software Support.
file or ffs.log file.
FEK114E accept() failed. reason=({0})
FEK110E socket() failed. reason=({0})

Troubleshooting and support 197

Explanation Explanation
{0} {0}
The reason code. For a list of reason codes, see The reason code. For a list of reason codes, see
the following topic in XL C/C++ Run-Time Library the following topic in XL C/C++ Run-Time Library
Reference (SA22-7821): accept. Reference (SA22-7821): select.
The TCP/IP accept call failed for the reason that is The select call failed for the reason that is specified
specified in the message. in the message.
System programmer response: System programmer response:
Contact IBM Software Support. Contact IBM Software Support.
FEK115E write() failed. reason=({0}) FEK119E _console() failed. reason=({0})

Explanation Explanation
{0} {0}
The reason code. For a list of reason codes, see The reason code. For a list of reason codes, see
the following topic in XL C/C++ Run-Time Library the following topic in XL C/C++ Run-Time Library
Reference (SA22-7821): write. Reference (SA22-7821): _console().
The TCP/IP write call failed for the reason that is The _console() call failed for the reason that is
specified in the message specified in the message.
System programmer response: System programmer response:
Contact IBM Software Support. Contact IBM Software Support.
FEK116E pipe() failed. reason=({0}) FEK120E REGISTRATION HAS BEEN
DENIED FOR PRODUCT WITH {0}
Explanation DUE TO {1}

{0}
The reason code. For a list of reason codes, see
Explanation
the following topic in XL C/C++ Run-Time Library {0}
Reference (SA22-7821): pipe. Product name and identifier information that is
The PIPE that is used between the daemon and server reported by the registration service.
processes failed for the reason that is specified in the {1}
message. The reason for the denial that is reported by the
registration service.
System programmer response:
Contact IBM Software Support. When the product server software starts, it registers
with z/OS to verify that it is being started on a
FEK117E socketpair() failed. reason=({0}) licensed CPU. This message displays when the product
registration is denied. It reports information about the
Explanation product and the reason for the denial.
{0} User response:
The reason code. For a list of reason codes, see Check that the product has been correctly enabled.
the following topic in XL C/C++ Run-Time Library For more information about enabling the product with
Reference (SA22-7821): socketpair. the registration service, see Product enablement in
IFAPRDxx.
The socketpair call failed for the reason that is
specified in the message. FEK130E gsk_environment_open() failed.
reason=({0})
System programmer response:
Contact IBM Software Support.
Explanation
FEK118E select() failed. reason=({0})
{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.

198 Developer for z/OS: Troubleshooting and Support

The gsk_environment_open() system SSL call System programmer response:
failed for the reason that is specified in the message. Contact IBM Software Support.
System programmer response: FEK134E gsk_attribute_set_buffer
Contact IBM Software Support. (GSK_KEYRING_FILE) failed.
reason=({0})
FEK131E gsk_attribute_set_enum
(GSK_PROTOCOL_SSLV2) failed.
reason=({0}) Explanation
{0}
Explanation The reason code. For a list of reason codes,
see the following topic in z/OS Cryptographic
{0}
Services System Secure Sockets Layer Programming
The reason code. For a list of reason codes,
(SC24-5901): gsk_attribute_set_buffer.
see the following topic in z/OS Cryptographic
Services System Secure Sockets Layer Programming The
(SC24-5901): gsk_attribute_set_enum. gsk_attribute_set_buffer(GSK_KEYRING_FILE
) system SSL call failed for the reason that is specified
The
in the message.
gsk_attribute_set_enum(GSK_PROTOCOL_SSLV2
) system SSL call failed for the reason that is specified System programmer response:
in the message. Contact IBM Software Support.
System programmer response: FEK135E gsk_attribute_set_buffer
Contact IBM Software Support. (GSK_KEYRING_PW) failed.
reason=({0})
FEK132E gsk_attribute_set_enum
(GSK_PROTOCOL_SSLV3) failed.
reason=({0}) Explanation
{0}
Explanation The reason code. For a list of reason codes,
see the following topic in z/OS Cryptographic
{0}
Services System Secure Sockets Layer Programming
The reason code. For a list of reason codes,
(SC24-5901): gsk_attribute_set_buffer.
see the following topic in z/OS Cryptographic
Services System Secure Sockets Layer Programming The
(SC24-5901): gsk_attribute_set_enum. gsk_attribute_set_buffer(GSK_KEYRING_PW)
system SSL call failed for the reason that is specified in
The
the message.
gsk_attribute_set_enum(GSK_PROTOCOL_SSLV3
) system SSL call failed for the reason that is specified System programmer response:
in the message. Contact IBM Software Support.
System programmer response: FEK136E gsk_environment_init() failed.
Contact IBM Software Support. reason=({0})
FEK133E gsk_attribute_set_enum
(GSK_PROTOCOL_TLSV1) failed. Explanation
reason=({0}) {0}
The reason code. For a list of reason codes,
Explanation see the following topic in z/OS Cryptographic
Services System Secure Sockets Layer Programming
{0}
(SC24-5901): gsk_environment_init.
The reason code. For a list of reason codes,
see the following topic in z/OS Cryptographic The gsk_environment_init() system SSL call
Services System Secure Sockets Layer Programming failed for the reason that is specified in the message.
(SC24-5901): gsk_attribute_set_enum. System programmer response:
The Contact IBM Software Support.
gsk_attribute_set_enum(GSK_PROTOCOL_TLSV1
FEK137E gsk_secure_socket_open() failed.
) system SSL call failed for the reason that is specified
reason=({0})
in the message.

Troubleshooting and support 199

Explanation Services System Secure Sockets Layer Programming
(SC24-5901): gsk_attribute_set_enum.
{0}
The reason code. For a list of reason codes, The
see the following topic in z/OS Cryptographic gsk_attribute_set_enum(GSK_SESSION_TYPE)
Services System Secure Sockets Layer Programming system SSL call failed for the reason code that is
(SC24-5901): gsk_secure_socket_open. specified in the message.
The gsk_secure_socket_open() system SSL call System programmer response:
failed for the reason that is specified in the message. Contact IBM Software Support.
System programmer response: FEK141E gsk_attribute_set_callback
Contact IBM Software Support. (GSK_IO_CALLBACK) failed.
reason=({0})
FEK138E gsk_attribute_set_numeric_value
(GSK_FD) failed. reason=({0})
Explanation
Explanation {0}
The reason code. For a list of reason codes,
{0} see the following topic in z/OS Cryptographic
The reason code. For a list of reason codes, Services System Secure Sockets Layer Programming
see the following topic in z/OS Cryptographic (SC24-5901): gsk_attribute_set_callback.
Services System Secure Sockets Layer Programming
(SC24-5901): gsk_attribute_set_numeric_value. The
gsk_attribute_set_callback(GSK_IO_CALLBAC
The K) system SSL call failed for the reason that is
gsk_attribute_set_numeric_value(GSK_FD) specified in the message.
system SSL call failed for the reason that is specified in
the message. System programmer response:
Contact IBM Software Support.
System programmer response:
Contact IBM Software Support. FEK142E gsk_secure_socket_init() failed.
reason=({0})
FEK139E gsk_attribute_set_buffer
(GSK_KEYRING_LABEL) failed.
reason=({0}) Explanation
{0}
Explanation The reason code. For a list of reason codes,
see the following topic in z/OS Cryptographic
{0} Services System Secure Sockets Layer Programming
The reason code. For a list of reason codes, (SC24-5901): gsk_secure_socket_init.
see the following topic in z/OS Cryptographic
Services System Secure Sockets Layer Programming The gsk_secure_socket_init() system SSL call
(SC24-5901): gsk_attribute_set_buffer. failed for the reason that is specified in the message.
The System programmer response:
gsk_attribute_set_buffer(GSK_KEYRING_LABE A system SSL trace might be needed to solve the
L) system SSL call failed for the reason that is problem. Contact IBM Software Support.
specified in the message. FEK143E gsk_attribute_set_enum
System programmer response: (GSK_CLIENT_AUTH_TYPE) failed.
Contact IBM Software Support. reason=({0})
FEK140E gsk_attribute_set_enum
(GSK_SESSION_TYPE) failed. Explanation
reason=({0}) {0}
The reason code. For a list of reason codes,
Explanation see the following topic in z/OS Cryptographic
Services System Secure Sockets Layer Programming
{0} (SC24-5901): gsk_attribute_set_enum.
The reason code. For a list of reason codes,
see the following topic in z/OS Cryptographic The
gsk_attribute_set_enum(GSK_CLIENT_AUTH_TY

200 Developer for z/OS: Troubleshooting and Support

PE) system SSL call failed for the reason that is Explanation
specified in the message.
{0}
System programmer response: The code that is returned by the Java virtual
A system SSL trace might be needed to solve the machine (JVM).
problem. Contact IBM Software Support.
The RSE daemon terminated because of an
FEK144E gsk_get_cert_info failed. unrecoverable TCP/IP error.
reason=({0})
System programmer response:
Contact IBM Software Support.
Explanation
FEK201I {0} Command has been processed
{0}
The reason code. For a list of reason codes,
see the following topic in z/OS Cryptographic
Explanation
Services System Secure Sockets Layer Programming {0}
(SC24-5901): gsk_attribute_get_cert_info. A command.
The gsk_attribute_get_cert_info system SSL A command was processed successfully.
call failed for the reason that is specified in the
System programmer response:
message.
No action is required.
System programmer response:
FEK202E Invalid Command Entered
A system SSL trace might be needed to solve the
problem. Contact IBM Software Support. Explanation:
An invalid command was issued.
FEK145E gsk_secure_socket_read() failed.
reason=({0}) System programmer response:
Correct the command parameters and issue the
Explanation command again.

{0} FEK203E Invalid Display Command: Display

The reason code. For a list of reason codes, Process|Client|Owner
see the following topic in z/OS Cryptographic Explanation:
Services System Secure Sockets Layer Programming An invalid Display command was entered. The
(SC24-5901): gsk_secure_socket_read. Display command must be Display Process or
The gsk_secure_socket_read() system SSL call Display Client.
failed for the reason that is specified in the message. System programmer response:
System programmer response: Correct the command and try again.
A system SSL trace might be needed to solve the FEK204E Invalid Cancel Command: Cancel
problem. Contact IBM Software Support. ID=|User=
FEK146E gsk_secure_socket_write() failed. Explanation:
reason=({0}) An invalid Cancel command was entered. The
command must be Cancel ID=nnnn or Cancel
Explanation User=userid, where nnnn is a user display ID that
is shown in the Display Client command.
{0}
The reason code. For a list of reason codes, System programmer response:
see the following topic in z/OS Cryptographic Correct the Cancel command parameters and try
Services System Secure Sockets Layer Programming again.
(SC24-5901): gsk_secure_socket_write. FEK205E Command was not processed
The gsk_secure_socket_write() system SSL call owing to consecutive SWITCHs
failed for the reason that is specified in the message.
Explanation:
System programmer response: The SWITCH audit log command cannot be processed
A system SSL trace might be needed to solve the because a previous SWITCH command is not yet
problem. Contact IBM Software Support. processed.
FEK150E RseDaemon abnormally System programmer response:
terminated; {0}

Troubleshooting and support 201

Wait for the completion of the previous SWITCH A cancel ID command was invalid because the user
command and try again. ID is not logged on. This warning is sometimes issued
when a cancel ID command is issued for a user ID that
FEK206E Audit Log facility is not active
has not yet been logged on.
Explanation:
System programmer response:
The SWITCH audit log command was entered, but the
No action is required.
audit log facility is not active.
FEK212E Invalid {0} command option: {1}
System programmer response:
Verify the settings that are related to the audit log in
the rse.env file and try again. Explanation
FEK207I No Client to be displayed {0}
The command that was entered: Display
Explanation: Process or Display Process,CPU
A Display Client command was issued, but there
is no client that the server serves. {1}
The invalid command option
System programmer response:
No action is required. A Display Process or Display Process,CPU
command with an invalid command option was
FEK208I {0} canceled entered.
System programmer response:
Explanation Correct the command option and issue the command
{0} again.
A user ID. FEK215W Command {0} is not processed by
The specified user was successfully canceled by a all thread pools
Cancel User command.
System programmer response: Explanation
No action is required. {0}
FEK209I No Process to be displayed The command that was issued

Explanation: When a command is issued to multiple thread pool

The Display Process command was issued, but no processes, the DaemonMonitor receives confirmations
server process is running. from each process and displays the command results.
If the timer expires before the DaemonMonitor
System programmer response: receives all of the confirmations, then the
No action is required. DaemonMonitor issues this message to show that
FEK210I {0} was disconnected forcibly some processes timed out before processing the
because of the active single.logon command.
directive. System programmer response:
Explanation: No action is required.
The client user who logged on was canceled because FEK216W Unable to process command, busy
the single logon capability is enabled. processing previous command.
System programmer response: Explanation:
No action is required unless you want to disable the A command was entered before the system completed
single logon capability. To disable the single logon processing a previous instance of the same command.
capability, change the settings for the single.logon
parameter in the rse.env file. The FEK010I message System programmer response:
shows the location of the rse.env file. Wait for the system to process the previous command
and then enter the second command again.
FEK211W User, {0}, not logged on
FEK217I {0} is locked by {1}

Explanation
Explanation
{0}
The user ID {0}
A data set.

202 Developer for z/OS: Troubleshooting and Support

{1} Explanation
A user ID.
{0}
A DISPLAY OWNER command was issued. This The process of the tool or program that was
message shows the lock owner of a data set. interrupted.
System programmer response: {1}
No action is required. The reason for the interruption.
FEK218I {0} is not locked The process of the tool or program was interrupted for
the specified reason.
Explanation System programmer response:
{0} If the specified reason is a timeout, check whether the
A data set. tool or program was hung.

A DISPLAY OWNER command was issued to display FEK301E {0} (uid:{1}) does not own the
the lock owner of a data set. The data set is not locked. directory of {2} (file_owner uid:{3})

System programmer response:

No action is required.
Explanation
{0}
FEK219E Failed to determine lock owner for
A log file name.
{0}
{1}
The user ID that attempted to access the log file.
Explanation
{2}
{0} The directory where the log file is stored.
A data set.
{3}
A DISPLAY OWNER command was issued, but the lock The user ID that owns the directory.
owner could not be determined.
An attempt was made to access a log file, but the user
System programmer response: ID does not have the correct authority.
No action is required.
System programmer response:
FEK220I LOGS Command has been started Ensure that your user ID is authorized to access the
to write onto {0} for the requester, log file.
{1}
FEK302E The requester, {0}, of the {1}
command does not have authority
Explanation to access the profile of {2}
{0}
The location of the output file. Explanation
A command was issued to collect host log files. {0}
This message shows the location of the output file. The user ID that requested the command.
The default name for the output file is $TMPDIR/
{1}
feklogs.%sysname.%jobname.log.
The command that was requested.
$TMPDIR
{2}
The default directory is /tmp.
A security profile.
%sysname
A command was issued, but the user ID does not have
The z/OS system name.
the correct authority to access the specified security
%jobname profile.
The name of the RSE daemon.
System programmer response:
System programmer response: Ensure that your user ID is authorized to access the
No action is required. specified security profile.
FEK221E {0} was interrupted because of {1} FEK303E The symbolic link, {0}, cannot be
used as a log directory

Troubleshooting and support 203

Explanation • ISPF: ISPF IVP
{0} {1}
0 A message that is issued by the IVP.
FEK304W Invalid {0}, {1}, was specified. The This message is a response that is issued when an
default mode, {2}, is used instead. operator runs the IVP program by using a console
command.
Explanation System programmer response:
No action is required.
{0}
0 FEK901I {0} IVP Exit code = {1}
{1}
1 Explanation
{2} {0}
2 The IVP name. This name can be one of the
FEK305E The ID, {0}, does not have following values:
appropriate privileges to access • DAEMON: Daemon IVP
{1}.
• PASSTICKET: PassTicket IVP
• ISPF: ISPF IVP
Explanation
{1}
{0}
The exit code.
0
This message shows the exit code that is provided by
{1}
the IVP program.
1
System programmer response:
FEK800S {0} {1}
No action is required.

Explanation FEK910I {0} EXIT: {1}

{0}
0
Explanation
{1} {0}
1 AUDIT indicates that the message originates in an
audit exit program.
FEK900I {0} IVP: {1}
{1}
A message that is issued by the audit exit program.
Explanation The audit exit program is created by the customer.
{0} This message is a response for an audit exit program
The IVP (Installation Verification Program) name. or logon exit program.
This name can be one of the following values:
System programmer response:
• DAEMON: Daemon IVP No action is required.
• PASSTICKET: PassTicket IVP

BPXM messages
BPXM023 (stclock) data set[(member)] NOT Explanation:
LOCKED This message is a response for the lock daemon query
command. The specified data set was locked by the
Explanation: specified user ID.
This message is a response for a lock daemon query
command. System programmer response:
No action is required.
System programmer response:
No action is required. BPXM023 (stclock) command, WRONG
COMMAND
BPXM023 (stclock) data set[(member)]
LOCKED BY userid Explanation:

204 Developer for z/OS: Troubleshooting and Support

An invalid lock daemon command was entered. BPXM023 (stclock) argument, WRONG
ARGUMENT
System programmer response:
Correct the lock daemon command and try again. Explanation:
An invalid argument was specified for the lock daemon
BPXM023 (stclock) command, MISSING
command.
ARGUMENT
System programmer response:
Explanation:
Correct the argument for the lock daemon command
An argument for the lock daemon command is missing.
and try again.
System programmer response:
Supply the missing argument for the lock daemon
command and try again.

CEARC messages
CEARC-87 A TSO logon parameter (for System programmer response:
example, procedure name or For information about the return code, see "Interactive
account number) is not valid. ISPF Gateway return codes" in z/OS V2R2.0 ISPF
Planning and Customization.
Explanation:
This message describes a return code for a TSO CEARC-91 An error occurred on a call to the
command execution error from the Interactive ISPF iconv_open() function.
Gateway. Explanation:
System programmer response: This message describes a return code for a TSO
For information about the return code, see "Interactive command execution error from the Interactive ISPF
ISPF Gateway return codes" in z/OS V2R2.0 ISPF Gateway.
Planning and Customization. System programmer response:
CEARC-88 Conflicting parameters are For information about the return code, see "Interactive
specified on the gateway request. ISPF Gateway return codes" in z/OS V2R2.0 ISPF
Planning and Customization.
Explanation:
This message describes a return code for a TSO CEARC-92 An error occurred on a call to the
command execution error from the Interactive ISPF iconv() function.
Gateway. Explanation:
System programmer response: This message describes a return code for a TSO
For information about the return code, see "Interactive command execution error from the Interactive ISPF
ISPF Gateway return codes" in z/OS V2R2.0 ISPF Gateway.
Planning and Customization. System programmer response:
CEARC-89 A message was received on the For information about the return code, see "Interactive
message queue with a message ISPF Gateway return codes" in z/OS V2R2.0 ISPF
type of ISPF. This is not expected. Planning and Customization.
Explanation: CEARC-93 An error occurred on a call to the
This message describes a return code for a TSO msgsnd() function.
command execution error from the Interactive ISPF Explanation:
Gateway. This message describes a return code for a TSO
System programmer response: command execution error from the Interactive ISPF
For information about the return code, see "Interactive Gateway.
ISPF Gateway return codes" in z/OS V2R2.0 ISPF System programmer response:
Planning and Customization. For information about the return code, see "Interactive
CEARC-90 An error occurred on a call to the ISPF Gateway return codes" in z/OS V2R2.0 ISPF
iconv_close() function. Planning and Customization.
Explanation: CEARC-94 An error occurred on a call to the
This message describes a return code for a TSO __msgrcv_timed() function.
command execution error from the Interactive ISPF Explanation:
Gateway.

Troubleshooting and support 205

This message describes a return code for a TSO Explanation:
command execution error from the Interactive ISPF This message describes a return code for a TSO
Gateway. command execution error from the Interactive ISPF
Gateway.
System programmer response:
For information about the return code, see "Interactive System programmer response:
ISPF Gateway return codes" in z/OS V2R2.0 ISPF For information about the return code, see "Interactive
Planning and Customization. ISPF Gateway return codes" in z/OS V2R2.0 ISPF
Planning and Customization.
CEARC-95 An error occurred on a call to the
setenv() function. CEARC-98 A parameter value on the gateway
request is bad.
Explanation:
This message describes a return code for a TSO Explanation:
command execution error from the Interactive ISPF This message describes a return code for a TSO
Gateway. command execution error from the Interactive ISPF
Gateway.
System programmer response:
For information about the return code, see "Interactive System programmer response:
ISPF Gateway return codes" in z/OS V2R2.0 ISPF For information about the return code, see "Interactive
Planning and Customization. ISPF Gateway return codes" in z/OS V2R2.0 ISPF
Planning and Customization.
CEARC-96 The response contains no text.
CEARC-99 A required parameter is missing on
Explanation:
the gateway request.
This message describes a return code for a TSO
command execution error from the Interactive ISPF Explanation:
Gateway. This message describes a return code for a TSO
command execution error from the Interactive ISPF
System programmer response:
Gateway.
For information about the return code, see "Interactive
ISPF Gateway return codes" in z/OS V2R2.0 ISPF System programmer response:
Planning and Customization. For information about the return code, see "Interactive
ISPF Gateway return codes" in z/OS V2R2.0 ISPF
CEARC-97 No data was read from STDIN.
Planning and Customization.

Runtime messages for Enterprise Service Tools

The following runtime messages pertain to the Enterprise Service Tools component (EST).
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 link: z/OS V1R10.0 Language Environment Run-Time Messages (SA22-7566-09)

0200-level messages
IRZ0279S XML to language structure 'true', 'false', '1', or '0'. The
conversion could not complete error occurred at XML path XML-
in program PROGRAM-NAME PATH with the character content
because conversion of the CHARACTER-CONTENT.
character content of an XML
element or attribute that is of
type xsd:boolean did not match

206 Developer for z/OS: Troubleshooting and Support

Explanation Explanation
XML to language structure conversion detected that XML to language structure conversion might encounter
the content of an XML element or attribute that is of errors when it transforms an XML message to a
type xsd:boolean did not match 'true', 'false', '1', or language structure. These errors are distinct from XML
'0'. PARSE errors.
System action: System action:
The converter either signals a Language Environment The converter either signals a Language Environment
condition or, if the optional feedback code argument is condition or, if the optional feedback code argument is
provided, places a condition token that represents the provided, places a condition token that represents the
condition in the argument. condition in the argument.

System programmer response System programmer response

Correct the input XML message. Ensure that the Correct the input XML message. Ensure that the
message is valid according to the XML schema upon message is valid according to the XML schema upon
which the XML to language structure converter is which the XML to language structure converter is
based. based.
IRZ0280S XML to language structure IRZ0282S XML to language structure
conversion could not complete conversion could not complete
in program PROGRAM-NAME in program PROGRAM-NAME
because an error return code of because none of the elements in
RETURN-CODE was received from the input XML document matched
the XML PARSE statement. The a mapped element in the XML
error occurred at XML path XML- Schema upon which the XML
PATH with the character content converter is based.
CHARACTER-CONTENT.
Explanation
Explanation
XML to language structure conversion might encounter
XML to language structure conversion uses the COBOL errors when it transforms an XML message to a
XML PARSE statement. When the XMLPARSE(COMPAT) language structure. These errors are distinct from XML
compiler option is in effect, the return code is provided PARSE errors.
from the XML PARSE statement and is described in
System action:
the Enterprise COBOL Programming Guide. When the
The converter either signals a Language Environment
XMLPARSE(XMLSS) compiler option is in effect, the
condition or, if the optional feedback code argument is
return code is provided from the z/OS XML System
provided, places a condition token that represents the
Services Parser and is described in the XML System
condition in the argument.
Services User's Guide and Reference.
System action: System programmer response
The converter either signals a Language Environment
condition or, if the optional feedback code argument is Correct the input XML message. Ensure that the
provided, places a condition token that represents the message is valid according to the XML schema upon
condition in the argument. which the XML to language structure converter is
based.
System programmer response IRZ0283S XML to language structure
Use the return code to determine the error and correct conversion could not complete
the input XML message. in program PROGRAM-NAME
because the character content
IRZ0281S XML to language structure for XML path XML-PATH was
conversion could not complete longer than the mapped language
in program PROGRAM-NAME structure member's maximum of
because the valid range of a LIMIT characters.
repeating group or repeating data
item was exceeded. The error
occurred at XML path XML-PATH.

Troubleshooting and support 207

Explanation Explanation
XML to language structure conversion might encounter XML to language structure conversion imposes a limit
errors when it transforms an XML message to a on the length of XML documents that can be converted
language structure. These errors are distinct from XML into language structures. The maximum length in bytes
PARSE errors. of the input XML document is 16 MB when version 3
of Enterprise COBOL for z/OS is used and 32 MB when
System action:
version 4 of Enterprise COBOL for z/OS is used.
The converter either signals a Language Environment
condition or, if the optional feedback code argument is System action:
provided, places a condition token that represents the The converter either signals a Language Environment
condition in the argument. condition or, if the optional feedback code argument is
provided, places a condition token that represents the
System programmer response condition in the argument.

Correct the input XML message. Ensure that the

System programmer response
message is valid according to the XML schema upon
which the XML to language structure converter is The product normally prevents generation of XML to
based. language structure converters when it is detected that
an input XML message can exceed the 16 MB or 32 MB
IRZ0284S XML to language structure
limit. Check that the input XML message conforms to
conversion could not complete
the XML schema upon which it is based and that any
in program PROGRAM-NAME
white space outside of element content is trimmed.
because conversion of the
character content of an XML IRZ0286S XML to language structure
path that is mapped as numeric conversion could not complete
failed. The error occurred at XML in program PROGRAM-NAME
path XML-PATH with the character because the character content for
content CHARACTER-CONTENT. XML path XML-PATH had a length
greater than or equal to LENGTH
Explanation characters, which was too long for
the converter to process.
XML to language structure conversion might encounter
errors when it transforms an XML message to a
Explanation
language structure. These errors are distinct from XML
PARSE errors. XML to language structure conversion maintains a
buffer for character content that has a maximum size
System action:
equal to 10 times the size of the largest item in the
The converter either signals a Language Environment
target data structure. The content of an element was
condition or, if the optional feedback code argument is
longer than expected.
provided, places a condition token that represents the
condition in the argument. System action:
The converter either signals a Language Environment
System programmer response condition or, if the optional feedback code argument is
provided, places a condition token that represents the
Correct the input XML message. Ensure that the condition in the argument.
message is valid according to the XML schema upon
which the XML to language structure converter is
System programmer response
based.
Correct the input XML message. Ensure that the
IRZ0285S XML to language structure
message is valid according to the XML schema upon
conversion could not complete
which the XML to language structure converter is
in program PROGRAM-NAME
based.
because the length of the XML
document is LENGTH characters, IRZ0287S Language structure to XML
which exceeds the maximum of conversion could not complete
MAXIMUM characters for this in program PROGRAM-NAME
converter. because the maximum output
message length of LENGTH

208 Developer for z/OS: Troubleshooting and Support

 characters was exceeded while STRUCTURE-NAME contained
generating the XML document. characters that are not legal in an
XML document.
Explanation
Explanation
Language structure to XML conversion processes
white space processing and expands entity references Certain COBOL data declarations allow characters that
expansion when it generates the XML document. Entity are not allowed in an XML document. The allowed
reference expansion increases the length of data characters are defined by the XML specification at
which is included as element content and can cause http://www.w3c.org.
it to grow up to six times the original length of the data
System action:
(the longest predefined entity is six characters long).
The converter either signals a Language Environment
System action: condition or, if the optional feedback code argument is
The converter either signals a Language Environment provided, places a condition token that represents the
condition or, if the optional feedback code argument is condition in the argument.
provided, places a condition token that represents the
condition in the argument. System programmer response
Ensure that the language structure member is properly
System programmer response
initialized and does not contain any characters that are
Ensure that the language structure was not changed not allowed in XML before you attempt conversion.
after the Language structure to XML converter was
generated. Regenerate the XML converter if changes IRZ0290S Language structure to XML
were made to the language structure. conversion could not complete
in program PROGRAM-NAME
IRZ0288S conversion could not complete because the content of numeric
in program PROGRAM-NAME member MEMBER-NAME of
because a non-zero return code language structure STRUCTURE-
was received from the Unicode NAME is invalid.
Conversion Service CUNLCNV
while converting from CCSID Explanation
SOURCE-CCSID to CCSID TARGET-
CCSID. Language structure to XML conversion determined that
the contents of the storage that is occupied by a
numeric language structure member is invalid for the
Explanation
type.
XML Conversion might convert XML and language data
System action:
to and from Unicode during parsing and generation of
The converter either signals a Language Environment
XML if XML is expected to be exchanged in Unicode.
condition or, if the optional feedback code argument is
System action: provided, places a condition token that represents the
The converter either signals a Language Environment condition in the argument.
condition or, if the optional feedback code argument is
provided, places a condition token that represents the System programmer response
condition in the argument.
Ensure that the numeric language structure member is
properly initialized according to COBOL semantics.
System programmer response
Check that conversion services are properly installed, IRZ0291S XML to language structure
and that the Unicode conversion attempted by the conversion could not complete
XML Converter is supported by the installation of in program PROGRAM-NAME
conversion services on the target system. because the maximum XML
element nesting depth was
IRZ0289S Language structure to XML exceeded. The error occurred
conversion could not complete at XML path XML-PATH with
in program PROGRAM-NAME character content CHARACTER-
because the content of CONTENT.
non-numeric member MEMBER-
NAME of language structure

Troubleshooting and support 209

Explanation errors that occur during conversion. An attempt to
unregister such a handler failed.
The language structure to XML converter maintains an
internal stack which represents the full qualification of System action:
the current element that is being processed in the XML The converter either signals a Language Environment
document. If extraneous XML elements not described condition or, if the optional feedback code argument is
in the XML schema to which the converter is bound are provided, places a condition token that represents the
present in the XML document, they might exceed the condition in the argument.
maximum supported element depth.
System action: System programmer response
The converter either signals a Language Environment Ensure that Language Environment is configured
condition or, if the optional feedback code argument is correctly and that no conditions that could prevent
provided, places a condition token that represents the correct operation exist in the chain of execution that
condition in the argument. leads up to the XML converter.
IRZ0294S XML conversion could not
System programmer response complete in program PROGRAM-
Ensure that the numeric language structure member is NAME because the address of one
properly initialized according to COBOL semantics. or more required parameters to
the main entry point did not have
IRZ0292S XML conversion could not valid addresses.
complete in program PROGRAM-
NAME because an attempt to
register an exception handler Explanation
failed with Language Environment The converter detected that one or more of the
error LE-ERROR parameters that were passed to its main entry point
do not have valid storage addresses to which the
Explanation converter could refer and obtain the value.

XML conversion uses Language Environment callable System action:

services to register a user-written handler to handle The converter either signals a Language Environment
errors that occur during conversion. An attempt to condition or, if the optional feedback code argument is
register such a handler failed. provided, places a condition token that represents the
condition in the argument.
System action:
The converter either signals a Language Environment
condition or, if the optional feedback code argument is System programmer response
provided, places a condition token that represents the Ensure that each parameter passed to the XML
condition in the argument. converter has a valid non-null storage address unless
a particular parameter can be null as defined by the
System programmer response converter call interface. For example, passing the XML
converter a null value for the XML buffer address to the
Ensure that Language Environment is configured language structure does not perform XML conversion,
correctly and that no conditions that could prevent but returns the required size of the XML buffer instead.
correct operation exist in the chain of execution that
leads up to the XML converter. IRZ0295S XML to language structure
conversion could not complete
IRZ0293S XML conversion could not in program PROGRAM-NAME
complete in program PROGRAM- because a response code of
NAME because an attempt to RESPONSE-CODE with reason
unregister an exception handler code REASON-CODE was received
failed with Language Environment from the bidirectional data
error LE-ERROR. conversion module MODULE-
NAME while processing the XML
Explanation path XML-PATH.
XML conversion uses Language Environment callable
services to register a user-written handler to handle

210 Developer for z/OS: Troubleshooting and Support

Explanation because the target namespace
of XML path XML-PATH was
XML to language structure conversion uses an external NAMESPACE-ACTUAL which is
module to handle bidirectional data conversions. inconsistent with the expected
System action: target namespace of NAMESPACE-
The converter either signals a Language Environment EXPECTED.
condition or, if the optional feedback code argument is
provided, places a condition token that represents the Explanation
condition in the argument.
XML to language structure conversion can optionally
validate the namespace name of XML elements.
System programmer response
System action:
Refer to the bidirectional data conversion module The converter either signals a Language Environment
documentation for explanations of return codes. condition or, if the optional feedback code argument is
IRZ0296S Language structure to XML provided, places a condition token that represents the
conversion could not complete condition in the argument.
in program PROGRAM-NAME
because a return code of RETURN- System programmer response
CODE with reason code REASON-
CODE was received from the Correct the XML instance document such that the XML
bidirectional data conversion elements have namespace names consistent with the
module MODULE-NAME while names specified in the XML schema.
processing member MEMBER- IRZ0299S XML to language structure
NAME of language structure conversion could not complete
STRUCTURE-NAME. in program PROGRAM-NAME
because the minimum count of
Explanation language structure STRUCTURE-
NAME was not met.
Language structure to XML conversion uses an
external module to handle bidirectional data
conversions. Explanation
System action: XML to language structure conversion can optionally
The converter either signals a Language Environment validate the namespace name of XML elements.
condition or, if the optional feedback code argument is System action:
provided, places a condition token that represents the The converter either signals a Language Environment
condition in the argument. condition or, if the optional feedback code argument is
provided, places a condition token that represents the
System programmer response condition in the argument.

Refer to the bidirectional data conversion module

documentation for explanations of return codes. System programmer response
IRZ0298S XML to language structure Correct the XML instance document such that the XML
conversion could not complete elements have namespace names consistent with the
in program PROGRAM-NAME names specified in the XML schema.

0300-level messages
IRZ0300S XML to language structure Explanation
conversion could not complete
in program PROGRAM-NAME XML to language structure conversion detected that
because the maximum count of the count of a language structure exceeds the
language structure STRUCT-NAME maximum that was specified when the XML converter
was exceeded. was generated.
System action:
The converter either signals a Language Environment
condition or, if the optional feedback code argument is

Troubleshooting and support 211

provided, places a condition token that represents the length that is less than the minimum length of the
condition in the argument. structure. The minimum length of a language structure
is computed as the sum of the bytes consumed by
System programmer response all subordinate fields. For fields that specify OCCURS
DEPENDING ON, the minimum number of occurrences
Correct the XML document or replace the XML is assumed.
converter with one having a higher maximum.
System action:
IRZ0301S Language structure to XML The converter either signals a Language Environment
conversion could not complete condition or, if the optional feedback code argument is
in program PROGRAM-NAME provided, places a condition token that represents the
because the total count of condition in the argument.
language structure instances
received was ACTUAL-COUNT System programmer response
which is less than the minimum
of MINIMUM-COUNT instances Correctly set the 2-byte length prefix of each language
required by the message layout. structure in the language structure buffer.
IRZ0303S Language structure to XML
Explanation conversion could not complete
in program PROGRAM-NAME
Language structure to XML conversion detected that
because the total count of
the language structure buffer it received contained
language structure instances
fewer language structure instances in total than is
received was ACTUAL-COUNT
required by the message layout.
which is greater than the
System action: maximum of MAXIMUM-COUNT
The converter either signals a Language Environment instances allowed by the message
condition or, if the optional feedback code argument is layout.
provided, places a condition token that represents the
condition in the argument.
Explanation
System programmer response Language structure to XML conversion detected that
the language structure buffer it received contained
Correct the language structure buffer so that each more language structure instances in total than is
language structure occurs at least as many times as allowed by the message layout.
is required per the message layout.
System action:
IRZ0302S Language structure to XML The converter either signals a Language Environment
conversion could not complete condition or, if the optional feedback code argument is
in program program-name provided, places a condition token that represents the
because the length prefix of condition in the argument.
language structure STRUCTURE-
NAME specified a length of System programmer response
SPECIFIED-LENGTH bytes, which
is less than the structure's Correct the language structure buffer so that it
minimum length of MINIMUM- contains no more than the maximum number of
LENGTH bytes. instances of each language structure in the message
layout.
Explanation
Language structure to XML conversion detected that
the length prefix of a language structure specified a

0500-level messages
IRZ0500S XML to language structure API DFSXSETS when attempting
conversion could not complete to store language structure
in procedure PROCEDURE-NAME STRUCTURE-NAME into the IMS
because a return code of RETURN- Connect message output buffer.
CODE was received from the

212 Developer for z/OS: Troubleshooting and Support

Explanation System action:
The converter either signals a Language Environment
In the IMS top-down scenario, XML to language condition or, if the optional feedback code argument is
structure conversion starts an API named DFSXSETS provided, places a condition token that represents the
to store one or more language structures into the condition in the argument.
IMS Connect message output buffer according to
a symmetric protocol. A nonzero return code from
DFSXSETS indicates that a language structure could System programmer response
not be stored in the IMS Connect message output For explanations of DFSXGETS return codes, see the
buffer and therefore cannot be sent to the IMS IRZPWSIO module documentation.
application.
IRZ0502S Language Structure to XML
System action: coversion could not complete
The converter either signals a Language Environment in procedure PROCEDURE-NAME
condition or, if the optional feedback code argument is because the array counter variable
provided, places a condition token that represents the COUNTER-NAME for array ARRAY-
condition in the argument. NAME specified a value of
System programmer response: COUNTER-VALUE which exceeds
For explanations of DFSXSETS return codes, see the the array's limit of ARRAY-LIMIT.
IRZPWSIO module documentation.
IRZ0501S Language Structure to XML Explanation
coversion could not complete Explanation: In the top-down scenario language
in procedure PROCEDURE-NAME structure to XML conversion provides an application
because a return code of RETURN- programmer the ability to specify the count of entries
CODE was received from the that XML conversion reads from an array by using
API DFSXGETS hen attempting generated counter variables. This message is issued
to retrieve language structure if a counter variable is found to contain a value that
STRUCTURE-NAME from the IMS exceeds the limit of its corresponding array.
Connect message input buffer.
System action:
The converter either signals a Language Environment
Explanation condition or, if the optional feedback code argument is
In the IMS top-down scenario, language structure to provided, places a condition token that represents the
XML conversion starts an RDz-provided API named condition in the argument.
DFSXGETS to retrieve one or more language structures
from the IMS Connect message input buffer according System programmer response
to a symmetric protocol. A nonzero return code from
DFSXGETS indicates that a language structure could Set the counter variable to a value that does not
not be retrieved from the IMS Connect message input exceed the limit of the corresponding array.
buffer and therefore cannot be converted to XML.

0900-level messages
IRZ0960S XML to language structure provided is from the PL/I PLISAXx built-in function
conversion could not complete as described in Enterprise PL/I for z/OS Programming
in procedure PROCEDURE-NAME Guide Version 3, SC27-1457-05 (or later).
because an error return code System action:
of RETURN-CODE was received The converter either signals a Language Environment
from the PLISAX FUNCTION- condition or, if the optional feedback code argument is
SUFFIX built-in function. The error provided, places a condition token that represents the
occurred at element ELEMENT- condition in the argument.
NAME with the character content
CHARACTER-CONTENT.
System programmer response
Explanation Use the return code to determine the error and correct
the input XML message.
XML to language structure conversionuses the PL/I
PLISAXx built-in function. The return code that is

Troubleshooting and support 213

IRZ0961S XML to language structure Explanation
conversion could not complete
in procedure PROCEDURE-NAME XML to language structure conversion might encounter
because the valid range of a errors that are distinct from PLISAXA/B errors.
repeating group or repeating data System action:
item was exceeded. The error The converter either signals a Language Environment
occurred at element ELEMENT- condition or, if the optional feedback code argument is
NAME. provided, places a condition token that represents the
condition in the argument.
Explanation
XML to language structure conversion might encounter
System programmer response
errors that are distinct from PLISAXA/B errors. Correct the input XML message.
System action: IRZ0964S XML to language structure
The converter either signals a Language Environment conversion could not complete
condition or, if the optional feedback code argument is in procedure PROCEDURE-NAME
provided, places a condition token that represents the because conversion of the
condition in the argument. character content of an element
that is mapped as numeric
System programmer response failed. The error occurred at
element ELEMENT-NAME with the
Correct the input XML message. Check that the input character content CHARACTER-
XML document has the correct number of occurrences CONTENT.
of all entries that repeat.
IRZ0962S XML to language structure Explanation
conversion could not complete
in procedure PROCEDURE-NAME XML to language structure conversion might encounter
because no element names in the errors that are distinct from PLISAXA/B errors.
XML document were recognized by System action:
the converter. The converter either signals a Language Environment
condition or, if the optional feedback code argument is
Explanation provided, places a condition token that represents the
condition in the argument.
XML to language structure conversion might encounter
errors that are distinct from PLISAXA/B errors.
System programmer response
System action:
The converter either signals a Language Environment Correct the input XML message.
condition or, if the optional feedback code argument is IRZ0965S XML to language structure
provided, places a condition token that represents the conversion could not complete
condition in the argument. in procedure PROCEDURE-NAME
because the size of the input XML
System programmer response message was LENGTH characters,
which exceeds the maximum of
Supply the correct XML message corresponding to this MAXIMUM characters for this
converter. converter.
IRZ0963S XML to language structure
conversion could not complete Explanation
in procedure PROCEDURE-NAME
because the character content XML to language structure conversion supports parsing
for element ELEMENT-NAME XML messages whose length falls within certain
was longer than the element's compiler limits.
maximum of LIMIT characters. System action:
The converter either signals a Language Environment
condition or, if the optional feedback code argument is

214 Developer for z/OS: Troubleshooting and Support

provided, places a condition token that represents the System programmer response
condition in the argument.
Avoid the use of the five predefined entries in XML
when you populate the language structure or define
System programmer response an auxiliary language structure to generate the output
Correct the input XML message or define an auxiliary XML in segments.
language structure to process the XML in segments. IRZ0968S XML Conversion could not
IRZ0966S XML to language structure complete in procedure
conversion could not complete PROCEDURE-NAME because a
in procedure PROCEDURE-NAME non-zero return code was received
because the character content for from the Unicode Conversion
element ELEMENT-NAME had a Service CUNLCNV while converting
length equal to or greater than from CCSID SOURCE-CCSID to
LENGTH characters which was too CCSID TARGET-CCSID.
long for the converter to process.
Explanation
Explanation XML Conversion uses PL/I built-in support for
The XML converter maintains a buffer for character UNICODE when the input XML or output XML is
content whose size is equal to that of the largest encoded in either UTF-16 or UTF-8.
character member in the language structure or 128, System action:
whichever is larger. The converter either signals a Language Environment
System action: condition or, if the optional feedback code argument is
The converter either signals a Language Environment provided, places a condition token that represents the
condition or, if the optional feedback code argument is condition in the argument.
provided, places a condition token that represents the
condition in the argument. System programmer response
Check that z/OS Support for UNICODE is properly
System programmer response installed and that the conversion attempted by
Correct the input XML message. Check for any the XML Conversion is supported by the current
excessive white space in the element content. conversion image.

IRZ0967S Language structure to XML IRZ0969S Language structure to XML

conversion could not complete conversion could not complete
in procedure PROCEDURE-NAME in procedure PROCEDURE-NAME
because the maximum output because the content of
message size of SIZE characters non-numeric member MEMBER-
was exceeded while creating the NAME of language structure
outbound XML document. STRUCTURE-NAME contained
characters that are not legal in an
XML document.
Explanation
Language structure to XML conversion supports Explanation
generation of XML messages whose length falls within
certain compiler limits. White space suppression Certain language structure members allow storage of
and entity reference expansion are performed during characters that are not valid in an XML document.
creation of the XML document. Entity reference The allowed characters are defined by the XML
expansion increases the size of a message in relation specification at http://www.w3c.org.
to the number of special characters in the source System action:
language structure that must be represented as one The converter either signals a Language Environment
of the five predefined entity references in XML. condition or, if the optional feedback code argument is
System action: provided, places a condition token that represents the
The converter either signals a Language Environment condition in the argument.
condition or, if the optional feedback code argument is
provided, places a condition token that represents the
condition in the argument.

Troubleshooting and support 215

System programmer response System programmer response
Ensure that the language structure member is properly Either supply XML documents to the converter that
initialized and does not contain any characters that are validate against the bound XML schema or remove the
not allowed in XML before you attempt conversion. extraneous element that causes the failure from the
input XML document.
IRZ0970S Language structure to XML
conversion could not complete IRZ0972S XML conversion could not
in procedure PROCEDURE-NAME complete in procedure
because the content of numeric PROCEDURE-NAME because an
member MEMBER-NAME of attempt to register an exception
language structure STRUCTURE- handler failed with Language
NAME is invalid. Environment error LE-ERROR.

Explanation Explanation
Language structure to XML conversion determined that The converter uses Language Environment callable
the contents of the storage that is occupied by a services to handle errors that might occur during
numeric data structure member is invalid for the type. conversion. An attempt by the converter to register a
Language Environment condition handler failed.
System action:
The converter either signals a Language Environment System action:
condition or, if the optional feedback code argument is The converter either signals a Language Environment
provided, places a condition token that represents the condition or, if the optional feedback code argument is
condition in the argument. provided, places a condition token that represents the
condition in the argument.
System programmer response
System programmer response
Ensure that the numeric data structure member is
properly initialized following the semantics of the Ensure that Language Environment is configured
language. properly and that no conditions that would prevent
correct operation exist in the chain of execution that
IRZ0971S XML to language structure leads up to the converter.
conversion could not complete
in procedure PROCEDURE-NAME IRZ0973S XML conversion could not
because the maximum XML complete in procedure
element nesting depth was PROCEDURE-NAME because an
exceeded. The error occurred attempt to unregister an exception
at element ELEMENT-NAME with handler failed with Language
character content CHARACTER- Environment error LE-ERROR.
CONTENT.
Explanation
Explanation
The converter uses Language Environment callable
XML to language structure conversion maintains an services to handle errors that might occur during
internal stack which represents the full qualification of conversion. An attempt by the converter to register a
the current element that is being processed in the XML Language Environment condition handler failed.
document. If extraneous XML elements not described
System action:
in the XML schema to which the converter is bound are
The converter either signals a Language Environment
present in the XML document, they might exceed the
condition or, if the optional feedback code argument is
maximum supported element depth.
provided, places a condition token that represents the
System action: condition in the argument.
The converter either signals a Language Environment
condition or, if the optional feedback code argument is System programmer response
provided, places a condition token that represents the
condition in the argument. Ensure that Language Environment is configured
properly and that no conditions that would prevent
correct operation exist in the chain of execution that
leads up to the converter.

216 Developer for z/OS: Troubleshooting and Support

IRZ0974S XML conversion could not in procedure PROCEDURE-NAME
complete in procedure because a response code of
PROCEDURE-NAME because the RESPONSE-CODE with reason
address of one or more parameters code REASON-CODE was received
was not valid. from the bidirectional data
conversion module MODULE-
NAME while processing member
Explanation
MEMBER-NAME of language
The converter detected that one or more of the structure STRUCTURE-NAME.
parameters that were passed to its main entry point
do not have valid storage addresses to which the Explanation
converter could refer and obtain the value.
Language structure to XML conversion uses an
System action: external module to handle bidirectional data
The converter either signals a Language Environment conversions.
condition or, if the optional feedback code argument is
provided, places a condition token that represents the System action:
condition in the argument. The converter either signals a Language Environment
condition or, if the optional feedback code argument is
provided, places a condition token that represents the
System programmer response
condition in the argument.
Ensure that each parameter passed to the converter
has a valid storage address unless a particular System programmer response
parameter can be null as defined by the converter call
interface. For example, a null message address that is Refer to the bidirectional data conversion module
passed to the outbound converter is interpreted as a documentation for explanations of return codes.
request for the maximum outbound message size to
IRZ0977S Language Structure to XML
be returned instead of a conversion.
conversion could not complete
IRZ0975S XML to language structure in procedure PROCEDURE-NAME
conversion could not complete because the length prefix in the
in procedure PROCEDURE-NAME language structure STRUCTURE-
because a response code of NAME specified a length of
RESPONSE-CODE with reason SPECIFIED-LENGTH bytes, which
code REASON-CODE was received is less than the structure's
from the bidirectional data minimum length of MINIMUM-
conversion module MODULE- LENGTH bytes.
NAME while processing element
ELEMENT-NAME. Explanation
Language Structure to XML conversion detected that
Explanation the length prefix of a language structure specified a
XML to language structure conversion uses an external length that is less than the minimum length of the
module to handle bidirectional data conversions. structure. The minimum length of a language structure
is computed as the sum of the bytes used by all
System action:
subordinate fields.
The converter either signals a Language Environment
condition or, if the optional feedback code argument is System action:
provided, places a condition token that represents the The converter either signals a Language Environment
condition in the argument. condition or, if the optional feedback code argument is
provided, places a condition token that represents the
condition in the argument.
System programmer response
Refer to the bidirectional data conversion module System programmer response
documentation for explanations of return codes.
Correctly set the 2-byte length prefix of each language
IRZ0976S Language structure to XML structure in the language structure buffer.
conversion could not complete

Troubleshooting and support 217

 1000-level messages
IRZ1000S CEEGTST failed in Compiled The module either signals a Language Environment
XML Conversion module condition or, if the optional feedback code argument
MODULE-NAME with message is provided, places a condition token that represents
number MESSAGE-NUMBER when the condition in the argument.
attempting to allocate COUNT- Programmer response:
BYTES bytes of storage for Ensure that all pointers and associated lengths that
STORAGE-USAGE. are supplied to the Compiled XML Conversion module
Explanation: mentioned in the message are valid. Additionally,
The Compiled XML Conversion module cited in this check for and correct any storage allocation failures
message encountered an error when it attempted to that might occur before the raising of this condition.
allocate storage by using the Language Environment IRZ1002S CUNLCNV failed in Compiled
CEEGTST callable service. XML Conversion module MODULE-
System action: NAME with return code RETURN-
The module either signals a Language Environment CODE and reason code REASON-
condition or, if the optional feedback code argument CODE when attempting to convert
is provided, places a condition token that represents from CCSID FROM-CCSID to
the condition in the argument. CCSID TO-CCSID.
Programmer response: Explanation:
Increase the amount of storage available to Compiled The Compiled XML Conversion module cited in
XML Conversion by increasing the maximum size of the this message encountered an error when it used
region in which the module runs. z/OS unicode services character conversion service
CUNLCNV to convert a code page.
IRZ1001S CEEFRST failed in Compiled
XML Conversion module MODULE- System action:
NAME with message number The module either signals a Language Environment
when attempting to free storage condition or, if the optional feedback code argument
for STORAGE-USAGE located at is provided, places a condition token that represents
address STORAGE-ADDRESS. the condition in the argument.
Explanation: Programmer response:
The Compiled XML Conversion module cited in this Determine the cause of the error by looking up the
message was unable to free storage by using the return and reason codes in the z/OS Unicode Services
Language Environment CEEFRST callable service. User's Guide and Reference.
System action:

218 Developer for z/OS: Troubleshooting and Support

Documentation notices
© International Business Machines Corporation 1992, 2024.

This information was developed for products and services offered in the US. This material might be
available from IBM in other languages. However, you may be required to own a copy of the product or
product version in that language in order to access it.
IBM may not offer the products, services, or features discussed in this document in other countries.
Consult your local IBM representative for information on the products and services currently available in
your area. Any reference to an IBM product, program, or service is not intended to state or imply that
only that IBM product, program, or service may be used. Any functionally equivalent product, program, or
service that does not infringe any IBM intellectual property right may be used instead. However, it is the
user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter described in this
document. The furnishing of this document does not grant you any license to these patents. You can
send license inquiries, in writing, to ipemail@us.ibm.com.
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 jurisdictions 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 websites are provided for convenience only and do not in
any manner serve as an endorsement of those websites. The materials at those websites are not part of
the materials for this IBM product and use of those websites is at your own risk.
IBM may use or distribute any of the information you provide 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
ipemail@us.ibm.com.
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.
Any performance data and client examples cited are presented for illustrative purposes only. Actual
performance results may vary depending on specific configurations and operating conditions.
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.
Statements regarding IBM's future direction or intent are subject to change or withdrawal without notice,
and represent goals and objectives only. Such statements should not be relied upon when making
purchasing decisions.

© Copyright IBM Corp. 1992, 2024 219

 This information contains examples of data and reports used in daily business operations. To illustrate
them as completely as possible, the examples include the names of individuals, companies, brands, and
products. All of these names are fictitious and any similarity to the names and addresses used by actual
people or business enterprises is entirely coincidental.
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.
Each copy or any portion of these sample programs or any derivative work must include a copyright notice
as follows:

© (your company name) (year).

Portions of this code are derived from IBM Corp. Sample Programs.
© International Business Machines Corporation _enter the year or years_.

Trademarks
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business
Machines Corporation, 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 at
"Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.

Terms and conditions for product documentation

Permissions for the use of these publications are granted subject to the following terms and conditions.

Applicability
These terms and conditions are in addition to any terms of use for the IBM website.

Personal use
You may reproduce these publications for your personal, noncommercial use provided that all proprietary
notices are preserved. You may not distribute, display or make derivative work of these publications, or
any portion thereof, without the express consent of IBM.

Commercial use
You may reproduce, distribute and display these publications solely within your enterprise provided
that all proprietary notices are preserved. You may not make derivative works of these publications, or
reproduce, distribute or display these publications or any portion thereof outside your enterprise, without
the express consent of IBM.

Rights
Except as expressly granted in this permission, no other permissions, licenses or rights are granted, either
express or implied, to the publications or any information, data, software or other intellectual property
contained therein.

220 Developer for z/OS: Troubleshooting and Support

IBM reserves the right to withdraw the permissions granted herein whenever, in its discretion, the use
of the publications is detrimental to its interest or, as determined by IBM, the above instructions are not
being properly followed.
You may not download, export or re-export this information except in full compliance with all applicable
laws and regulations, including all United States export laws and regulations.
IBM MAKES NO GUARANTEE ABOUT THE CONTENT OF THESE PUBLICATIONS. THE PUBLICATIONS
ARE PROVIDED "AS-IS" AND WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED,
INCLUDING BUT NOT LIMITED TO IMPLIED WARRANTIES OF MERCHANTABILITY, NON-INFRINGEMENT,
AND FITNESS FOR A PARTICULAR PURPOSE.

Documentation notices 221

222 Developer for z/OS: Troubleshooting and Support
Security considerations
This topic highlights some of the security limitations that you might encounter with this application. To
help ensure the security of your installation, customize your security settings and set up user access
controls.

Enabling security during the installation process

Security configuration for Developer for z/OS is addressed in Security definitions. More details on all
security aspects can be found in Security considerations.
Security considerations for Developer for z/OS:
• Installing Developer for z/OS results in a basic configuration with default settings for a basic, secure
setup. Extra configuration tasks, such as configuring SSL, allow for tighter controls. This information is
covered in detail in Security considerations.
Note: Security is not fully enabled during the installation process and must be enabled during
customization after installation is complete. The customization of some security-related aspects must
be completed for the product to work and for certain security features to be enabled. This limitation
applies to silent installations.
• Security for Developer for z/OS on the host is configured through a combination of Developer for z/OS
configuration files and RACF commands (or other similar security products).
• Developer for z/OS does not provide a login option when the Developer for z/OS host is used as an LDAP
client that accesses a customer-specific LDAP server to get group membership information that is used
to enforce wanted client behavior. LDAP logon information can be provided in a configuration file when
the Developer for z/OS host is used as an LDAP client that accesses public certificate revocation lists
(CRLs).
• Security for Developer for z/OS database authentication is enabled through RACF commands.
• For information about setting up SSL and installing a custom certificate, see these topics in the IBM
Explorer for z/OS documentation: (Optional) ssl.properties, the RSE encrypted communication, RSE -
ssl.properties, and Setting up encrypted communication and X.509 authentication.
• For information about enabling security between the client and server or web client and server, see
Connection flow.
• To configure the security settings of other applications that communicate with Developer for z/OS (Db2
Connect, Debug Tool, Fault Analyzer, File Manager), use the security configuration options available in
those products.
• To verify that you correctly configured the security settings, see Verify the security settings.
• More information:
– With the host connection in Enterprise Service Tools, you can set up a terminal session with a remote
z/OS system. You can configure the session to use SSL, client authentication, and host authentication.
You can use the IBM Key Management tool iKeyman to create a key database file, to create or request
certificates, and to import and export certificates.
Note: Developer for z/OS also uses REXEC, or the more secure SSH, to compile UNIX System Services
projects. For more information, see z/OS UNIX subprojects.

Enabling secure communication between multiple applications

For integrated products, Developer for z/OS provides security for the communications between the
products through the Developer for z/OS communication configuration by using Developer for z/OS tools.
The communication is host only, so there is no encryption.

© Copyright IBM Corp. 1992, 2024 223

 To handle user access controls between products in Developer for z/OS, the receiving application (for
example, JMON) requires authentication, which is done by the calling application (RSE) on the user’s
behalf. Where possible (for example, JMON or CARMA), Developer for z/OS binds to the loopback stack
only, which can be reached only from the same system.
For single-sign on, the user authenticates with RSE. RSE then does authentications on the user’s behalf
for other servers. While the user stays within Developer for z/OS, it all looks like one server, but this
situation is not true for other servers. Users must manually authenticate for other servers outside of
Developer for z/OS.

Ports, protocols, and services

Developer for z/OS internal processes, tasks, or services do not require a fixed user ID. You can create
your own user ID for these processes, tasks, or services, and associate the user ID with them by using
RACF commands. For more information about what ports, protocols, and services Developer for z/OS
uses, see Planning and TCP/IP considerations.
Before you can connect to a remote system from the Developer for z/OS client, you must define
a connection for the remote system and specify connection properties. For more information about
connecting to a remote system and the ports that are used for a connection, see Creating a connection to
a z/OS system.

Customizing your security settings

Customizing your security settings is covered in Security considerations. For more information about
setting and changing passwords, and client certificate authentication, see these topics:
• Connecting to a remote system
• Changing your password
• Creating a connection by using client certificate authentication
• Setting preferences for client certificate authentication
Note: Developer for z/OS uses generated PassTickets and does not store passwords on the host. The
Remote Connection Emulator (RCE) stores SSL-related passwords in the Eclipse Secure Storage. For more
information, see Secure storage in the Eclipse documentation. Clients mask password fields with ***, and
a password that is provided by a client during logon is always transmitted in a masked format, even for
SSL encrypted communication.
To enable multiple levels of security, and determine the implications of each, see the various chapters
about security in the host configuration documentation. Each chapter addresses a specific aspect of
security configuration.
Developer for z/OS relies on the options that are offered by TCP/IP to set up notifications of security
breaches or attempts.
Note: Information about login attempts is stored in the Developer for z/OS server logs, and in various
other places (for example, server log, user logs, audit log, syslog).

Multi-Factor Authentication
Developer for z/OS relies on IBM Explorer for z/OS for multi-factor authentication (MFA) support. For
information about configuring MFA in IBM Explorer for z/OS, see Using Multi-Factor Authentication.

Setting up user roles and access

RACF commands are used for the following purposes:
• Create and delete users and set their access levels.
• Create groups and assign them privileges.
• Establish password rules for users (such as no reuse, minimum length, or character requirements).

224 Developer for z/OS: Troubleshooting and Support

• Setup superuser IDs or IDs with special security privileges.
For more information about RACF, see the Security Server RACF Security Administrator's Guide,
SA23-2289.

Privacy policy considerations

This software offering does not use cookies or other technologies to collect personally identifiable
information.

Security considerations 225

226 Developer for z/OS: Troubleshooting and Support
IBM®

Product Number: 5755-A05

5724-T07