Resolving PL/I Importer Errors

When your application is unsuccessful in importing a PL/I file into your project, your application displays an error message. You can then correct the problem and reimport the file.

Types of Error Messages

  • PL/I files that are part of your workspace (local): When your application is unsuccessful in importing a local PL/I file (which is part of the workspace) into your project, syntax error messages appears in the problem view. To view the source of the error in your code, click the error message line in the problem view. Errors are also logged in a generic log file, located under the metadata directory: [workspace]\.metadata\.log
  • PL/I files that are not part of your workspace: If the file is not part of the workspace the syntax error messages, if any, are logged in the log file.
  • Data name mangling: Duplicate names are made unique by the addition of two numeric digits. For example, two instances of year become year01 and year02.
  • Data import error: On the data import page, in the CICS option: field, if you select CICS Transaction Server for z/OS v3.1 OR CICS Transaction Server for z/OS v3.2, you can see the following error after you click Query:
    PL/I import error

    If the file that you are importing is included in your workspace, you can also see the problem contained in the Problems view:

    Problems view for PL/I error

    The reason for this error is that the IBM® PL/I for Windows compiler that is shipped with IBM® Rational® Application Developer requires IBM TX Series for Multiplatforms V6.2 to be installed to perform CICS® translations. If your Windows PL/I program contain EXEC CICS statements, you need to install IBM TX Series for Multiplatforms version 6.2 before you can import the PL/I program.

Feedback