1.0 New in this Release
1.1 New Features in Version 7.1.1
1.2 New Features in Version 7.1
2.0 Known limitations, problems, and workarounds
2.1 Using the development environment
2.1.1 Inaccurate representation in z/OS Projects and Remote Systems views
2.1.2 Content assist limitation
2.1.3 CVS and z/OS projects (Local/Remote/Offline) interaction
2.1.4 User CLASSPATH variable problems and workarounds
2.1.5 Truncated text message in wizards
2.1.6 Possible NullPointerException Entry in .log File
2.2 Connecting to remote systems
2.2.1 Error conditions when connecting to a remote system
2.2.2 Preventing users from saving their password
2.3 Manipulating z/OS files
2.3.1 Remote file system support
2.3.2 Unable to delete load modules from an active job
2.3.3 Display of cataloged data sets residing on offline volumes
2.3.4 Creation of new folders or new files under an offline MVS project
2.3.5 MOVE not supported
2.3.6 Keyboard accessibility limitation in copying a host member to its own dataset
2.3.7 Uploading folders created while offline not supported
2.3.8 Local command actions against host artifacts are not supported
2.4 Editing, compiling, and building
2.4.1 Assembler
2.4.2 LPEX Editor
2.4.3 Error messages for build or syntax check
2.4.4 PL/I Preprocessor messages do not appear in the Task list
2.4.5 Windows COBOL known limitations, problems, and workarounds
2.4.6 Preserving changes when modifying PDS members and sequential data sets
2.4.7 Compiler options when the COBOL host compiler options are specified
2.4.8 Compiler options when the PL/I host compiler options are specified
2.4.9 Local project build problem for PL/I
2.4.10 Clarification of meaning of buttons for environment variable setting
2.4.11 Local syntax check of remote file support
2.5 Debugging
2.5.1 Debugging and running programs
2.5.2 Debugging source files with duplicate names
2.5.3 Breakpoints prior to a remote debug session with a PL/I Program
2.5.4 Setting the default action for the Terminate button in the Debug View
2.5.5 Too many variables to monitor in the local variables window
2.5.6 PL/I BEGIN blocks with no local variables cause debug session problems
2.5.7 Project name longer than 80 characters causes problem in local debug
2.5.8 Debugging a COBOL program with an XML PARSE statement
2.5.9 Change in ADATA format produced by HLASM
2.6 Working with z/OS jobs and commands
2.6.1 Uncompleted TSO command causes user interface to hang
2.6.2 JCL generation fields on Properties page require explicit data set names
2.6.3 JCL submission with dynamic variable substitution
2.7 Using subsystems (CICS/DB2)
2.7.1 DB2 SDK required for syntax check with EXEC SQL
2.7.2 Subsystems (CICS and DB2 support)
2.8 Migrating from a previous release
2.8.1 Migration Considerations
2.8.2 Workspace migration
2.9 National languages
2.9.1 Nonstandard code page translation in SCLM
2.9.2 Job Monitor Server Code-Page compatibility
2.9.3 Some Japanese PL/I compiler messages do not appear
2.9.4 Status of translations
2.10 Stored Procedures Limitations
3.0 System z Database Application Generator
3.0.1 JCL might need additional customization
3.0.2 Database Application Projects containing Bidirectional characters need to remove BCT
3.0.3 Version 7.0.0.4 or later of Rational Business Developer Extensions is required
4.0 MFS Editor Limitations
5.0 AIX Support
5.0.1 Supported functions on AIX using Rational Developer
5.0.2 RSE AIX Server Installation
5.0.3 Using SSL with RSE AIX Server
5.0.4 Starting and accessing the RSE AIX Server
5.0.5 Debugging COBOL programs on AIX using Rational Developer for System z
6.0 CICS Syntax Checker
7.0 APARs closed between WebSphere Developer for zSeries 7.0.1 and Rational Developer for System z 7.1.1
7.0.1 APARs closed in WebSphere Developer for zSeries 7.0.1 Interim Fixes
7.0.2 APARs reported in WebSphere Developer for zSeries 7.0.1 and fixed in Rational Developer for System z 7.1
7.0.3 APARs closed between Rational Developer for System z 7.1 and Rational Developer for System z 7.1.1
8.0 Link to Rational Developer for zSeries support site
For performance reasons, data sets and folders inside the z/OS Projects view and data sets inside the Remote Systems view are only refreshed on demand. This leads to situations where an empty data set or folder is displayed with a "+" symbol next to it until you explicitly expand that data set or folder. Additions or deletions to the content shown inside the z/OS Projects view or the Remote Systems view by an outside agent (for example, deletion of a shared data set by another user, or addition of a data set member via ISPF) can be viewed only after you perform a view refresh. To perform a view refresh, select the project (in the z/OS Projects view) or the filter (in the Remote Systems view) and choose Refresh from the context menu.
Limitation: The content assist function for PL/I programs works best when the source being analyzed contains a PROCEDURE statement. If your source code uses the PL/I macro facility to generate a PROCEDURE statement, the content assist parser will not see it. If no PROCEDURE statement is found, content assist will behave as if all of the code is within a PROCEDURE - END block. This condition (no visible PROCEDURE statement) also exists if you are editing a PL/I include file.
z/OS Local Projects (local projects that are created in the z/OS Perspectives) can be checked in and checked out of the CVS Repository, but project properties are not maintained. Every time the project is checked out of CVS, it will have the default properties.
There is no support for using CVS with Remote MVS projects, regardless of the project state (offline or online).
Rational Developer for System z depends on a properly set System CLASSPATH environment variable. If a User CLASSPATH environment variable also exists, that variable would override the System CLASSPATH variable and could cause certain functions to fail. This can be resolved by appending ";%CLASSPATH%" to the User CLASSPATH environment variable, or by removing the User CLASSPATH variable.
Problem description: Messages in the text area that appear below the title of some wizards might be truncated. Sometimes, if the text spans several lines, only the first line is shown.
Workaround: Set the icons to display maximum colors to see the text correctly. To do so, go to Start -> Settings -> Control Panel Settings -> Display. Go to the "Effects" tab and select the check box that says "Show icons using all possible colors." Then go to the "Settings" tab and set Colors to support at least 32-bit colors. Do this by selecting True Color (32 bit) from the list of color choices.
You may see a NullPointerException entry in the .log file that begins something like this:
!ENTRY org.eclipse.core.resources 4 2 2007-07-18 09:52:34.443 !MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.core.resources". !STACK 0 java.lang.NullPointerException at com.rational.clearcase.RSCMService.visit(Unknown Source) ...
This exception is not harmful in any way. It has been logged for internal information only and may safely be ignored.
When you connect to a remote system in the Remote Systems view, an error occurs if one of the following conditions is not met:
If one or more of these is incorrect, an error dialog pops up detailing the cause of the problem.
A system administrator can setup a system to prevent users from saving their password by uncommenting the following line in rsed.envvars.
#_RSE_JAVAOPTS="$_RSE_JAVAOPTS -DDENY_PASSWORD_SAVE=true"
When a user connects to a system with the option, any saved passwords for the system will be cleared, and any further attempt to connect to the system will not allow the user to save a password. The option works only for 7.1 clients going against 7.1 servers
Rational Developer for System z supports access to the traditional MVS data sets, hierarchical file system under Unix System Services on zSeries, and AIX filesystem. Other server file systems are not supported.
Load Modules in a PDS currently allocated to an active Job cannot be deleted.
Cataloged data sets residing on offline volumes are displayed on the Remote Systems view, along with other migrated data sets. On the Remote Systems view, offline data sets are denoted with their own icons. These unmounted data sets are only available for display on the Remote Systems view. No other actions or operations are supported in this release.
To uncatalog a data set, you can submit a TSO command:
DELETE datasetname NOSCRATCH
where datasetname is the name of the data set to be uncataloged. This command will uncatalog the data set without the need to specify the volume to be mounted on.
Although functionally enabled under the New menu, the creation of new folders or new files is not supported under offline MVS projects. This problem is a limitation of the current Eclipse framework. If you create new folders or new files under an MVS project while it is offline, these new artifacts will prevent it from returning to online. Therefore, you should not create new folders or files under an offline MVS project. Creation of a new file under a folder (corresponding to a data set added to an MVS project) is supported.
MOVE is not supported. To accomplish a move, you can do a COPY and then a DELETE.
There is a known problem in attempting to copy a host member to its own containing dataset when using only the keyboard. The problem arises from the dialog box that contains the table where you specify the target name. Currently, this name cannot be changed without using an external pointing device. To get around this problem when using only the keyboard, copy the member to another dataset, rename the member, and then copy it back to the dataset that contains it.
Problem: The uploading of folders you created while Offline from an MVS system is currently not supported.
Workaround: Allocate the PDS directly through the Remote Systems view and then copy the associated members to it.
For Menu Manager, local command actions (e.g. notepad '$fullname') against host artifacts are not supported.
Assembler errors do not appear in the task list. To view your assembler errors from a batch compile, view the job output using the JES subsystem in the tree or table viewer. Similarly, error feedback does not work for BMS Map Builds.
To edit PDS members you should use the z/OS LPEX editor. z/OS LPEX address mainframe-specific considerations such as record length, file locking (ISPF ENQ/DEQ), sequence numbers, and EBCDIC/DBCS code pages.
When you edit remote z/OS files with the z/OS LPEX editor, text in the sequence number field (columns 73 through 80) is maintained separately by the z/OS LPEX editor only if the field contains valid ordered sequence numbers for every line in the file when the file is opened. Unordered numbers and arbitrary text are not maintained separately by the editor, but you may maintain them yourself by using replace mode instead of insert mode.
When you are using any profile other than ISPF, tab settings in the LPEX preferences will not take effect when editing COBOL or PL/I source files because the respective parsers override the tab preferences.
When you are using the ISPF profile, tab preferences will take effect for COBOL, PL/I and all other files. However, the first time you make a change to the tab preferences, the change will not immediately take effect in already-open LPEX sessions. You can work around this problem by entering the command updateProfile in the LPEX command-line window. The problem will not reoccur for new LPEX sessions.
If TCP/IP connectivity is lost while a remote host system is connected, and the connectivity is later regained, Rational Developer for System z Foreign File System will have lost its ability to ensure the exclusive use of remote files (file locking by ISPF ENQ/DEQ) until Rational Developer for System z is restarted. Any files that you had opened prior to the connectivity loss would have their lock released. Before attempting to save any unsaved changes, make sure that these files were not modified by others during the connectivity loss.
When running Rational Developer for System z 7.1 or 7.1.1 with a workspace that was created using an older version of WebSphere Developer for System z, the default editor for COBOL, PL/I, and other files may be the base LPEX editor. This is not what is intended and it won't provide the features provided by the System z LPEX editor, such as content assist. The following workaround is suggested:
In your workspace, locate and delete the following file before starting Rational Developer for System z. This can be done anytime, and need only be done once.
<workspace-location>\.metadata\.plugins\org.ecliplse.core.runtime\.setting\org.eclipse.ui.workbench.prefsThis will cause the desired editor defaults to be established.
The following error message may be displayed when you perform a build or syntax check: Error reading XML file from compilation:
Problem with SAX parser. Document root element is missing.
This may occur in the following circumstance:
The workaround is to view your preprocessor messages in the listing file, or apply PTF UQ77592 to Enterprise PL/I for z/OS V3.R2.M0.
Problem: The XML PARSE statement has limitations if the CHAR(EBCDIC) compiler option is in effect. The contents of special register XML-TEXT might not be encoded in EBCDIC as expected. The encoding of XML-TEXT depends on the encoding of the source XML document.
Workaround: The content of special register XML-TEXT is encoded in EBCDIC if the XML document is encoded in EBCDIC. If the XML document is encoded in ASCII in a native alphanumeric data item, the content of XML-TEXT is encoded in ASCII. Such content can be translated to EBCDIC if desired, using the following technique: FUNCTION DISPLAY-OF (FUNCTION NATIONAL-OF (XML-TEXT 819) )
Problem: If you attempt to do a Local Syntax check of a remote COBOL source file with dependencies with the Remote System's connection name or the workspace path containing a character (such as the German u-umlaut character) that is not in the ASCII character range 0x00-0x7f, then the operation fails and an error message such as the following is displayed in the Remote Error List view:
The 'COPY' library was not found. Skipped to the period terminating the 'COPY' statement.
Workaround: Change the name of Remote system's connection or any subdirectory in the path that contains the problem characters so that the name contains only characters in the range ASCII 0x00-0x7f.
Problem: If you attempt to local syntax check or build a local COBOL file with dependencies from your workstation, and the path to the copybook(s) contains a character (such as the German u-umlaut character) that is not in the ASCII character range 0x00-0x7f, then the operation fails and an error message such as the following is displayed in the Remote Error List view:
The 'COPY' library was not found. Skipped to the period terminating the 'COPY' statement.
Workaround: Change the name of any subdirectory in the path that contains the problem characters so that the name contains only characters in the range ASCII 0x00-0x7f. Or, move the COBOL copybook to another subdirectory so that the path contains only characters in the range ASCII 0x00-0x7f.
Problem: Remote COBOL files or COBOL files copied from the host to the workstation which contain BIDI characters may not be handled correctly by the local syntax check action. As a result, unexpected error messages may occur during local syntax check which do not occur during remote syntax check.
Workaround: We recommend that for remote COBOL files or COBOL files copied from the host to the workstation which contain BIDI characters, you only use remote syntax check
The LPEX editor in Rational Developer honors the ISPF file lock (ENQ), which prevents different users from editing the same file and from overwriting each other's changes. Nonetheless, it is possible for an application that does not honor the ISPF enqueue/dequeue to overwrite a file that is being edited in LPEX. For data set members, this condition will be detected at save time, and the following messages will be displayed
"The file has changed on the remote system since it was opened."
The user has a chance to preserve the changes on the workstation using either the Save As menu item, or Copy and Paste.
For sequential data sets, Rational Developer cannot display this notification, since sequential data sets do not have sufficient timestamp information.
To avoid overwriting any such changes when you save the data set from the editor, do not edit a sequential data set while running applications which may modify it and do not perform a copy operation to a sequential data set while you are editing it.
If COBOL host compiler options are specified in the Compiler Options field of COBOL Settings, then the compiler options ADATA,EXIT(ADEXIT(ELAMGUX)) are enforced to ensure the errors always get fed back to the task list.
If PL/I host compiler options are specified in the Compiler Options field of PL/I Settings, then the compiler option XINFO(XML) is enforced to ensure the errors always get fed back to the task list.
A Project build CICS TX Series with PL/I will result in link errors if there are multiple object decks to link into the TX Series DLL.
When you create a "Compiled Application" Launch Configuration, you have the ability to specify environment variables to be passed to the application when the application is run or debugged. When supplying a value for an environment variable, there are two radio buttons that affect how the definition is handled.
Append environment to native environment: Selection of this button means that environment variables added within the launch configuration will be added to the environment which would have been passed to the application if no additional variables had been defined. Variables which are defined with the same name as an existing variable will REPLACE the existing value. Furthermore, trying to include the existing value in the new value using %variable% does not work. What does work, however, is to select the Select button rather than the Add button, and mark the existing environment variable that you want to modify. This will add the existing value to the list of environment variables for the launch configuration, and then you can edit that definition to make whatever changes or additions are necessary.
For example, if you need to add an additional folder to the end of the existing path definition, click the Select button, check the PATH setting, and click OK. Then highlight the PATH variable and click the Edit button. You can then append the new folder to the end of the existing specification.
Replace native environment with specified environment: Selection of this button means that existing environment variables that would normally be passed to the application will not be passed, and only those variables defined within this launch configuration will be passed.
Local syntax check of remote files is supported for members and sequential data sets in a project. The user should make sure refresh dependencies is run at least once, and whenever the copybook/include file dependency of the source file may have changed.
Debugging a batch PL/I program does not work if the source is inline in the JCL. The debugger requires a source file.
When you perform Debug Application on a remote executable, this action starts a batch debugging session. Since the application is running in batch, you cannot provide program input at the TSO command prompt. To work around that, provide any necessary user input in the additional JCL field in the Runtime options property page of the project.
In addition to the DTCN transaction, with CICS TX Series, the CADP transaction can be used to debug a remote transaction. Please see the Debug Tool Users Guide for more information.
The debugger provides two interfaces for inserting the debug code into a CICS program during the Link step:
Here is an example of how the EQADCCXT interface was link edited into the CICS programs:
If you decide to use the EQADCCXT interface, the debugger provides a CICS program called Debug Tool Control Panel to dynamically change your debug test environment. The debug session can be tested solely on the CICS region using the MFI protocol or redirected to a workstation, where Rational Developer is running, using the TCP protocol.
The Debug Tool Control Panel can be started by entering DTCN at the CICS terminal. When the Control Panel appears, simply enter TCP for the protocol, the port number on which the Rational Developer for System z debugger server program is listening on the workstation (usually port 8001) and the IP address of the workstation. Specify the transaction ID that maps to your program definition. Press PF4 to save and PF3 to exit. At this point, check Rational Developer for System z to make sure that the debugger server is listening at the correct port number. You can invoke the CICS program (via the transaction ID) and the Debug perspective should come into view in Rational Developer for zSereies on your workstation.
There is a known problem with the workstation distributed debugger that can cause it to debug the wrong source file. Given the same source file name in two Local Projects, the wrong application is debugged. Setting breakpoints in the source file in one will cause the debugger to stop in the other source file as if breakpoints were set in it. This is a known defect and will be fixed in a future release of the product. To work around the problem, keep only one source file with a given name in your workspace. To work around the breakpoint problem, continue pressing Run in the distributed debugger to skip over unwanted breakpoints.
Breakpoints will not be honored if set before launching a remote debug session (PQ71801). To work around the problem, launch the debug session and then set the breakpoint while in the debug perspective. To launch the debug session, select the program in the z/OS Projects view, then select Debug Application from the context menu.
This applies to debugging with Debug Tool.
The Terminate action (button or menu action) in the Debug perspective can be set to "Terminate" or "Terminate and abend". The default action can be set using a new preference. The preference can be found in the Preferences dialog by entering "Debug Tool" in the filter field at the top of the Preferences dialog or by going to Run/Debug->Compiled Debug->Debug Tool Preferences
If you are debugging a large program and see the message, "Too many local variables for local monitor," close the Variables view and use the program monitor to view the variables instead.
If you have a BEGIN Block in PL/I that contains either no local variables declared directly within the block, or a variable that was declared but unused, Debug sessions on z/OS do not behave correctly.
Local debug of an executable residing in a project with a name longer than 80 characters may result in a "Communications failure" error in the debugger, ending your debug session.
When debugging a COBOL program with an XML PARSE statement, variables may not appear in the Variables view, and variables may not support being monitored. When you want to see all of the variables in the Variables view, click on the COBOL program in the stack that is the name of the COBOL program in the Debug window. For example, if you are debugging a COBOL program called XML1, in the stack you will see XML_XML1 and XML1. You need to click on XML1 and then click on the Variables tab.
When you want to monitor a variable, in the source window, click on the line with the PROGAM-ID; then, in the Monitors window, add the data-item you want to monitor.
The format of the ADATA produced by the High Level Assembler (HLASM) has changed format from Version 1 Release 4 to Version 1 Release 5. The Debug Tool utility EQALANGX - needed for debugging symbolic assembler debugging - requires the ADATA Version 1 Release 4 format. HLASM ships an optional ADATA exit, ASMAXADR, that converts the ADATA file from Release 5 to Release 4 format. You must install and enable this exit for the Debug Tool symbolic HLASM debugging. If you do not convert the ADATA format to the Release 4 format, the EQALANGX utility will seemingly succeed and the failure will occur during the debug session.
If a TSO command is issued from the z/OS Commands view but this command does not get completed on the host, the user interface might go into an infinite loop (the system hangs) until this command is terminated on the host. The termination will cause unsaved data and metadata to be lost.
Fields on the properties pages for projects, folders, and files should not contain substitution variables for JCL generation and project build.
The asterisk (*) is not allowed in any of the fields for z/OS build options. If you enter a data set that is not valid or not allocated, a JCL error will occur.
A new feature is available which allows you to create specialized JCL templates with special markers to indicate the variables that need to be substituted during JCL submission. A new Menu Manager action is provided to specify the JCL template to use and the default values. You can also specify whether or not to prompt for the default overrides when submitting the JCL. The customized template is then loaded, all variables substituted and the JCL is submitted. The template, at the original location, is not modified. This allows multiple users to use the same template.
A white paper providing more information about JCL submission with dynamic variable substitution is available at http://www.ibm.com/software/awdtools/devzseries/library/.
To perform a local build, or syntax check of a PL/I or COBOL program that contains EXEC SQL statements, DB2 UDB Personal Edition 8.2 (or above) should be installed, as well as DB2 Application Development Client.
Local: Source files in a local project with CICS EXEC functions can be preprocessed and compiled to produce the .dll file on the local workstation. To run CICS, you can use CICS TX Series, which you can also use for local compiling.
To compile and debug a COBOL program with DB2, select the "Source Contains Embedded SQL" check box in the properties page or the project creation wizard. You can create a DB2 Connection or select an existing connection.
After migrating to RDz 7.1, you may find that some editor functions (content assist, for example) are not working. This can be caused by the wrong default editor being used following migration. Please see the LPEX Editor section for further information and a workaround for this problem.
Before migrating from a previous release, you should back-up your workspace to prevent possible data loss.
Migrating WebSphere Developer for zSeries 6.x and 7.0 workspaces to Rational Developer for System z 7.1 or 7.1.1:
If you have a workspace you used in WebSphere Developer for zSeries 6.x, or 7.0 and you want to migrate the workspace for use with Rational Developer for System z 7.1, you must follow these steps.
Migrating WebSphere Studio Enterprise Developer 5.1.1 and 5.1.2 workspaces to Rational Developer for System z 7.1:
If you have a workspace you used in WebSphere Studio Enterprise Developer 5.1.1 or 5.1.2, and you want to migrate the workspace for use with Rational Developer for System z 7.1, you must follow these steps.
NOTE: Be sure you still have WebSphere Studio Enterprise Developer 5.1.1 or 5.1.2 installed on your workstation.
If you require an ASCII/EBCDIC code page translation other than the standard default (IBM-1047 / ISO8859-1), you must code the following parameters in the httpd.conf (elaxwebc.conf) file for the HTTP Web server:
For example, for Japanese translation the required code pages would be as follows:
Note: Some restrictions exist in Windows Japanese with regard to SCLM host character translation. Rational Developer translates the following EBCDIC characters to ? (0x3F):
DBCS users should not modify the default Code-Page CODEPAGE=UTF-8.
Not all of the PL/I compiler messages are translated. This results in a "message could not be read" message in the task list and in the PL/I listing file. The workaround is to compile with NATLANG(ENU), to view the message in English.
There will be a mixture of English and translated text in some messages, menus, menu options, and so forth. The mixture varies by language and was determined by each country individually.
There are some limitations associated with Stored Procedures:
Some of the generated JCL artifacts might need further customization in order to work correctly in certain environments.
When deploying generated COBOL members from a Database Application Project which contain Bidi characters ensure that no Bidi Conversion Table is set for the remote destination. You should still set the remote and local codepages normally.
In order to use Rational Developer 7.1 with Rational Business Developer Extensions in the same package group, Rational Business Developer Extensions Version 7.0.0.4 is the minimum level required.
Some of the keywords associated with CICS command have changed over the years, but have been retained for compatibility reasons. A few of these obsolete keywords are incorrectly flagged as invalid by the syntax checker. These are listed in Table 1, together with an explanation of the problem, and the action that you should take if you encounter it.
Command | Description | Action |
---|---|---|
ALLOCATE | The NOSUSPEND keyword is an alternative to the
NOQUEUE keyword for this command.
If you specify NOSUSPEND, the syntax checker returns: Invalid command option 'NOSUSPEND' |
You can ignore this error because the syntax is correct. |
ASSIGN | The OPSECURITY and OPERKEYS keywords are
supported for compatibility reasons.
If you specify either of these keywords, the syntax checker returns: Invalid command option 'OPSECURITY' Invalid command option 'OPERKEYS |
You can ignore these errors because the syntax is correct. |
DELETE | You can use the keyword DATASET as an
alternative to FILE for this command. (This is for compatibility with
earlier releases, and is not documented.)
If you do this, the syntax checker returns: Invalid command option 'DATASET' This might cause other options to be flagged as invalid. |
You can ignore this error because DATASET is
accepted as an alternative to FILE.
If this problem has caused other options to be flagged as invalid, you might want to change DATASET to FILE to check that there are no other errors. |
DELETEQ TS | The keyword TS is optional for this command.
(This is for compatibility with earlier releases, and is not
documented.)
If you do not specify the TS option, the syntax checker assumes that the command is DELETEQ TD, and returns: Command is ambiguous, 'TD' has been assumed This causes other options to be flagged as invalid. |
You can ignore this error because the syntax
is correct.
However, if you want to check the other options that were flagged as invalid you must specify TS to check that there are no other errors. |
DEQ | A CVDA value of LUW is supported as an
alternative to UOW for compatibility reasons.
If you specify LUW, the syntax checker returns: Invalid command option 'LUW |
You can ignore this error because the syntax is correct. |
DOCUMENT RETRIEVE | The CLNTCODEPAGE keyword is an alternative to
the CHARACTERSET keyword for this command.
If you specify CLNTCODEPAGE, the syntax checker returns: Invalid command option 'CLNTCODEPAGE' |
You can ignore this error because the syntax is correct. |
ENDBR | You can use the keyword DATASET as an
alternative to FILE for this command. (This is for compatibility with
earlier releases, and is not documented.)
If you do this, the syntax checker returns: Invalid command option 'DATASET' This might cause other options to be flagged as invalid. |
You can ignore this error because DATASET is
accepted as an alternative to FILE.
If this problem has caused other options to be flagged as invalid, you might want to change DATASET to FILE to check that there are no other errors. |
ENQ | A CVDA value of LUW is supported as an
alternative to UOW for compatibility reasons.
If you specify LUW, the syntax checker returns: Invalid command option 'LUW |
You can ignore this error because the syntax is correct. |
INQUIRE DSNAME | The BKOUTSTATUS option is obsolete on this
command, but has been retained for compatibility with earlier
releases.
If you specify BKOUTSTATUS, the syntax checker returns: Invalid command option 'BKOUTSTATUS' |
You can ignore this error because the syntax
is correct.
However, CICS will accept the keyword and issue an informational message |
INQUIRE JOURNALNUM | This command is obsolete and is retained only
for compatibility reasons.
If you specify this command, the syntax checker returns: Invalid command option 'JOURNALNUM' This might cause other options to be flagged as invalid. |
You can ignore these errors because the syntax
is correct.
However, CICS will accept the command and issue an informational message |
INQUIRE NETNAME | The SCREENWIDTH and SCREENHEIGHT keywords have
been replaced by SCRNHT and SCRNWD on this command, but are supported
for compatibility reasons.
If you specify either of these keywords, the syntax checker returns: Invalid command option 'SCREENWIDTH' Invalid command option 'SCREENHEIGHT' |
You can ignore these errors because the syntax is correct. |
INQUIRE PROGRAM | The JVMDEBUG option is obsolete on this
command, but has been retained for compatibility with earlier
releases.
If you specify JVMDEBUG, the syntax checker returns: Invalid command option 'JVMDEBUG' |
You can ignore this error because the syntax
is correct.
CICS returns NODEBUG as the CVDA value. |
INQUIRE TASK | The DTB option is obsolete and was replaced by
INDOUBT on this command. However, it has been retained for
compatibility with earlier releases.
If you specify DTB, the syntax checker returns: Invalid command option 'DTB' |
You can ignore this error because the syntax
is correct.
CICS returns NOTSUPPORTED as the CVDA value. |
INQUIRE TERMINAL | The SCREENWIDTH and SCREENHEIGHT keywords have
been replaced by SCRNHT and SCRNWD on this command, but are supported
for compatibility reasons.
If you specify either of these keywords, the syntax checker returns: Invalid command option 'SCREENWIDTH' Invalid command option 'SCREENHEIGHT' |
You can ignore these errors because the syntax is correct. |
INQUIRE VOLUME | This command is obsolete and is retained only
for compatibility reasons.
If you specify this command, the syntax checker returns: Invalid command option 'VOLUME' This might cause other options to be flagged as invalid. |
You can ignore these errors because the syntax
is correct.
However, CICS will accept the command and issue an informational message |
READ | You can use the keyword DATASET as an
alternative to FILE for this command. (This is for compatibility with
earlier releases, and is not documented.)
If you do this, the syntax checker returns: Invalid command option 'DATASET' This might cause other options to be flagged as invalid. |
You can ignore this error because DATASET is
accepted as an alternative to FILE.
If this problem has caused other options to be flagged as invalid, you might want to change DATASET to FILE to check that there are no other errors. |
READNEXT | You can use the keyword DATASET as an
alternative to FILE for this command. (This is for compatibility with
earlier releases, and is not documented.)
If you do this, the syntax checker returns: Invalid command option 'DATASET' This might cause other options to be flagged as invalid. |
You can ignore this error because DATASET is
accepted as an alternative to FILE.
If this problem has caused other options to be flagged as invalid, you might want to change DATASET to FILE to check that there are no other errors. |
READPREV | You can use the keyword DATASET as an
alternative to FILE for this command. (This is for compatibility with
earlier releases, and is not documented.)
If you do this, the syntax checker returns: Invalid command option 'DATASET' This might cause other options to be flagged as invalid. |
You can ignore this error because DATASET is
accepted as an alternative to FILE.
If this problem has caused other options to be flagged as invalid, you might want to change DATASET to FILE to check that there are no other errors. |
READQ TS | The keyword TS is optional for this command.
(This is for compatibility with earlier releases, and is not
documented.)
If you do not specify the TS option, the syntax checker assumes that the command is READQ TD, and returns: Command is ambiguous, 'TD' has been assumed This causes other options to be flagged as invalid. |
You can ignore this error because the syntax
is correct.
However, if you want to check the other options that were flagged as invalid you must specify TS to check that there are no other errors. |
RESETBR | You can use the keyword DATASET as an
alternative to FILE for this command. (This is for compatibility with
earlier releases, and is not documented.)
If you do this, the syntax checker returns: Invalid command option 'DATASET' This might cause other options to be flagged as invalid. |
You can ignore this error because DATASET is
accepted as an alternative to FILE.
If this problem has caused other options to be flagged as invalid, you might want to change DATASET to FILE to check that there are no other errors. |
REWRITE | You can use the keyword DATASET as an
alternative to FILE for this command. (This is for compatibility with
earlier releases, and is not documented.)
If you do this, the syntax checker returns: Invalid command option 'DATASET' This might cause other options to be flagged as invalid. |
You can ignore this error because DATASET is
accepted as an alternative to FILE.
If this problem has caused other options to be flagged as invalid, you might want to change DATASET to FILE to check that there are no other errors. |
SET DSNAME | The FAILEDBKOUT, NORMALBKOUT and BKOUTSTATUS
options are obsolete on this command, but have been retained for
compatibility with earlier releases.
If you specify any of these keywords, the syntax checker returns: Invalid command option 'FAILEDBKOUT' Invalid command option 'NORMALBKOUT' Invalid command option 'BKOUTSTATUS' |
You can ignore these errors because the syntax
is correct.
However, CICS will accept the keywords and issue informational messages |
SET JOURNALNUM | This command is obsolete and is retained only
for compatibility reasons.
If you specify this command, the syntax checker returns: Invalid command option 'JOURNALNUM' This might cause other options to be flagged as invalid. |
You can ignore these errors because the syntax
is correct.
However, CICS will accept the command and issue an informational message |
SET VOLUME | This command is obsolete and is retained only
for compatibility reasons.
If you specify this command, the syntax checker returns: Invalid command option 'VOLUME' This might cause other options to be flagged as invalid. |
You can ignore these errors because the syntax
is correct.
However, CICS will accept the command and issue an informational message |
STARTBR | You can use the keyword DATASET as an
alternative to FILE for this command. (This is for compatibility with
earlier releases, and is not documented.)
If you do this, the syntax checker returns: Invalid command option 'DATASET' This might cause other options to be flagged as invalid. |
You can ignore this error because DATASET is
accepted as an alternative to FILE.
If this problem has caused other options to be flagged as invalid, you might want to change DATASET to FILE to check that there are no other errors. |
UNLOCK | You can use the keyword DATASET as an
alternative to FILE for this command. (This is for compatibility with
earlier releases, and is not documented.)
If you do this, the syntax checker returns: Invalid command option 'DATASET' This might cause other options to be flagged as invalid. |
You can ignore this error because DATASET is
accepted as an alternative to FILE.
If this problem has caused other options to be flagged as invalid, you might want to change DATASET to FILE to check that there are no other errors. |
WEB READ | The CLNTCODEPAGE keyword is an alternative to
the CHARACTERSET keyword for this command.
If you specify CLNTCODEPAGE, the syntax checker returns: Invalid command option 'CLNTCODEPAGE' |
You can ignore this error because the syntax is correct. |
WEB RECEIVE | The CLNTCODEPAGE keyword is an alternative to
the CHARACTERSET keyword for this command.
If you specify CLNTCODEPAGE, the syntax checker returns: Invalid command option 'CLNTCODEPAGE' |
You can ignore this error because the syntax is correct. |
WEB SEND | The CLNTCODEPAGE keyword is an alternative to
the CHARACTERSET keyword for this command.
If you specify CLNTCODEPAGE, the syntax checker returns: Invalid command option 'CLNTCODEPAGE' |
You can ignore this error because the syntax is correct. |
WEB STARTBROWSE | The CLNTCODEPAGE keyword is an alternative to
the CHARACTERSET keyword for this command.
If you specify CLNTCODEPAGE, the syntax checker returns: Invalid command option 'CLNTCODEPAGE' |
You can ignore this error because the syntax is correct. |
WRITE | You can use the keyword DATASET as an
alternative to FILE for this command. (This is for compatibility with
earlier releases, and is not documented.)
If you do this, the syntax checker returns: Invalid command option 'DATASET' This might cause other options to be flagged as invalid. |
You can ignore this error because DATASET is
accepted as an alternative to FILE.
If this problem has caused other options to be flagged as invalid, you might want to change DATASET to FILE to check that there are no other errors. |
WRITEQ TS | The keyword TS is optional for this command.
(This is for compatibility with earlier releases, and is not
documented.)
If you do not specify the TS option, the syntax checker assumes that the command is WRITEQ TD, and returns: Command is ambiguous, 'TD' has been assumed This causes other options to be flagged as invalid. |
You can ignore this error because the syntax
is correct.
However, if you want to check the other options that were flagged as invalid you must specify TS to check that there are no other errors. |
Some coding errors do not cause the syntax checker to issue a message. These errors are listed in Table 2. If your program contains one of these errors, it will not be flagged by the syntax checker, but it will be flagged when you translate the program using the CICS translator.
Command | Error |
---|---|
All INQUIRE and FEPI INQUIRE commands that support browsing | You cannot use any other keywords if you use
the START, AT, or END keywords to start or finish browsing.
You cannot provide a resource name if you use the START, AT, or END keywords to start or finish browsing. |
ALLOCATE | You cannot use the PARTNER and PROFILE keywords together. |
COLLECT STATISTICS | If you specify the NODE keyword, you must also specify the TARGET keyword. |
CONNECT PROCESS | You must specify either SESSION or PARTNER.
If you specify the PARTNER keyword, you must also specify the CONVID keyword. |
CONVERSE | You cannot use the ATTACHID keyword with the
CTLCHAR, DEST, ERASE, DEFAULT, ALTERNATE, LDC, LINEADDR, PSEUDOBIN,
or STRFIELD keywords
You cannot use the FMH and LDC keywords together. If you specify the SET keyword you must also specify either the TOLENGTH or TOFLENGTH keyword. |
DEFINE TIMER | You cannot use the AT and DAYS keywords
together.
You cannot use the AFTER keyword with the ON, YEAR, MONTH, DAYOFMONTH, or DAYOFYEAR keywords. |
DELETE CONTAINER | You cannot use the CHANNEL keyword with the ACTIVITY, ACQACTIVITY, PROCESS, or ACQPROCESS keywords. |
DELETE FILE | You cannot use the RBA, XRBA or RRN keywords with the KEYLENGTH, GENERIC, or NUMREC keywords. |
DISABLE PROGRAM | You cannot use the EXIT keyword with the FORMATEDF, PURGEABLE, SHUTDOWN, SPI or TASKSTART keywords. |
ENABLE PROGRAM | You cannot use the EXIT keyword with the FORMATEDF, INDOUBTWAIT, LINKEDITMODE, OPENAPI, PURGEABLE, QUASIRENT, SHUTDOWN, SPI, TALENGTH, TASKSTART, or THREADSAFE keywords. |
EXTRACT ATTACH | You cannot use the SESSION or CONVID keywords with the ATTACHID keyword. |
EXTRACT WEB | You cannot use the SESSTOKEN keyword with the REQUESTTYPE keyword. |
FEPI CONVERSE DATASTREAM | You cannot use the CHAIN or RU keywords with
the POOL keyword.
You can use the POOL keyword only if you also use the UNTILCDEB keyword. |
FEPI CONVERSE FORMATTED | You cannot use the AID or FROMCURSOR keywords with the POOL keyword. |
FEPI INQUIRE CONNECTION | You cannot use the other keywords apart from NODE or TARGET if you use the START or END keywords to start or finish browsing all FEPI connections |
GET CONTAINER | You cannot use the INTOCCSID keyword with the ACTIVITY, ACQACTIVITY, PROCESS, or ACQPROCESS keywords. |
INQUIRE ASSOCIATION LIST | You cannot use any INQUIRE ASSOCATION LIST options with any of the INQUIRE ASSOCIATION options. |
INQUIRE MODENAME | If you use the NEXT keyword, you must also use the CONNECTION keyword. |
INQUIRE TASK | You cannot use any INQUIRE TASK LIST options with any of the INQUIRE TASK options. |
LINK | You cannot use the DATALENGTH, SYNCONRETURN,
SYSID, or TRANSID keywords with the INPUTMSG or INPUTMSGLEN keywords.
You cannot use the CHANNEL keyword with the COMMAREA, LENGTH, or DATALENGTH keywords. |
MOVE CONTAINER | You cannot use the CHANNEL keyword with the
TOPROCESS or TOACTIVITY keywords.
You cannot use the TOCHANNEL keyword with the FROMPROCESS or FROMACTIVITY keywords. |
PERFORM JVMPOOL | If you use the START keyword, you must also use the JVMPROFILE keyword. |
PUT CONTAINER | You cannot use the FROMCCSID or DATATYPE keywords with the ACTIVITY, ACQACTIVITY, PROCESS, or ACQPROCESS keywords. |
READ | You cannot use the KEYLENGTH keyword with the
RBA, XRBA or RRN keywords.
You cannot use the GENERIC or GTEQ keywords with the RBA, XRBA, DEBREC, or DEBKEY keywords. You must use the EQUAL keyword if you use the RBA, XRBA, DEBREC or DEBKEY keywords. You cannot use the RRN keyword with the GENERIC keyword. |
READNEXT | You cannot use the KEYLENGTH keyword with the
RBA, RRN or XRBA keywords.
You must use the UPDATE keyword if you use the TOKEN keywords |
READPREV | You cannot use the KEYLENGTH keyword with the
RBA, RRN or XRBA keywords.
You must use the UPDATE keyword if you use the TOKEN keywords |
READQ TS | If you use the SET keyword, you must also use the LENGTH keyword. |
RECEIVE | If you use the SET keyword, you must also use the LENGTH or FLENGTH keyword. |
RESETBR | You cannot use the KEYLENGTH keyword with the
RBA, XRBA or RRN keywords.
You cannot use the GENERIC keyword with the RBA, XRBA or RRN keywords. You must use the EQUAL keyword if you use the RBA or XRBA keywords. You cannot use the RBA or XRBA keywords with the GTEQ keyword. |
RETURN | You cannot use any other keywords with the
ENDACTIVITY keyword.
You cannot use the CHANNEL keyword with the COMMAREA or LENGTH keywords. |
SEND | You cannot use the ATTACHID keyword with the
CBUFF, CNOTCOMPL, CTLCHAR, DEST, ERASE, DEFAULT, ALTERNATE, LDC,
LEAVEKB, LINEADDR, PASSBK, PSEUDOBIN, or STRFIELD keywords.
You cannot use the CNOTCOMPL keyword with the CONFIRM or INVITE keywords. You cannot use the ERASE, DEFAULT or ALTERNATE keywords with the STRFIELD keyword. You cannot use the LAST keyword with the PASSBK or CBUFF keywords. You cannot use the LDC keyword with the FMH keyword. Must use WAIT if PASSBK or CBUFF is used. |
SEND MAP | You cannot use the MAPPINGDEV keyword with the NLEOM, MSR, FMHPARM, LDC, OUTPARTN, ACTPARTN, ACCUM, REQID, or NOFLUSH keywords. |
SET CONNECTION | You cannot use the ACQUIRED keyword with the OUTSERVICE keyword. |
SET JOURNALNAME | You cannot use the STATUS, ENABLED, or DISABLED keywords with the ACTION, FLUSH, or RESET keywords. |
SET TASK | You cannot use the PRIORITY keyword with the PURGETYPE, KILL, FORCEPURGE, or PURGE keywords. |
SET TRANSACTION | You cannot use the RUNAWAY keyword with the SYSTEM keyword. |
START | You can use only one of the ATTACH, BREXIT or
CHANNEL keywords at a time.
You cannot use the ATTACH or CHANNEL keywords with any of the START options (for example, INTERVAL or TIME). You cannot use the BREXIT keyword with the FROM or LENGTH keywords. |
STARTBR | You cannot use the KEYLENGTH keyword with the
RBA, XRBA or RRN keywords.
You cannot use the GENERIC or GTEQ keywords with the RBA, XRBA, DEBREC, or DEBKEY keywords. You must use the EQUAL keyword if you use the RBA, XRBA, DEBREC or DEBKEY keywords. You cannot use the RRN keyword with the GENERIC keyword. |
WEB EXTRACT | You cannot use the SESSTOKEN keyword with the REQUESTTYPE keyword. |
WEB READ | You cannot use the HTTPHEADER keyword with the
CLNTCODEPAGE or HOSTCODEPAGE keyword.
You cannot use the HTTPHEADER keyword with the SET keyword. |
WEB RECEIVE | You cannot use the SESSTOKEN, MEDIATYPE,
STATUSCODE, STATUSTEXT, STATUSLEN, CLIENTCONV, CLICONVERT, or
NOCLICONVERT keywords with the TYPE, CLNTCODEPAGE, or HOSTCODEPAGE
keywords.
If you use the CLIENTCONV, CLICONVERT, or NOCLICONVERT keywords, you must also use the SESSTOKEN keyword. You cannot use the SESSTOKEN keyword with the SERVERCONV, SRVCONVERT, or NOSRVCONVERT keywords. |
WEB SEND | You cannot use the SESSTOKEN keyword with the
CLNTCODEPAGE, HOSTCODEPAGE, STATUSCODE, STATUSTEXT, STATUSLEN,
LENGTH, SERVERCONV, SRVCONVERT, or NOSRVCONVERT keywords.
If you use the CLIENTCONV, CLICONVERT, or NOCLICONVERT keywords, you must also use the SESSTOKEN keyword. |
WEB STARTBROWSE | You cannot use the HTTPHEADER keyword with the CLNTCODEPAGE or HOSTCODEPAGE keywords. |
WRITE | You cannot use the RBA, XRBA or RRN keywords with the KEYLENGTH keyword. |
XCTL | You cannot use the CHANNEL keyword with the COMMAREA or LENGTH keywords. |
For infromation on APARs closed in WebSphere Developer for System z 7.0.1 Interim Fixes, please visit the WebSphere Developer for System Z Recommended Fixes site.
The Rational Developer for System z support page can be found here:
(C) Copyright IBM Corporation 2000, 2005, 2006, 2007. All Rights Reserved.