Importing PL/I source files from a remote system

This topic describes how to use the Import Source Files wizard to import PL/I source files from a remote z/OS® system.

The Import Source Files wizard allows you to import files into the Enterprise Service Tools perspective either from the local file system, from the current workspace, or from a remote z/OS system (see Importing source files into a single-service project).

This topic describes how to use the Import Source Files wizard to import PL/I source files from a remote system.

Prerequisite

Before you can import files from a remote system, you must first create a connection to the remote system (see the topic "Connecting to a remote system" in the online help).

The basic steps for creating a connection to the remote system are as follows:
  1. Use the Remote Systems view to create connections to JES, to MVS and (if applicable) to z/OS UNIX System services.
  2. Use the Remote Systems view to start the new connection to the remote z/OS system.

Requirements for PL/I source files

The Import Source Files wizard has the following requirements for importing PL/I source files from a remote system:
  • The remote file must be mapped to one of the following extensions: .pli, .mac or .inc.
  • If the file is mapped to a .pli extension, then the file is assumed to be a complete PL/I program that can have dependencies on other files. If the PL/I program does in fact have dependencies on other files, then you should provide the information about the partitioned data sets (PDSs) where the files exist by setting the SYSLIB for the remote file.
  • If the file is mapped to a .inc or .mac extension, it is assumed to be a PL/I include file consisting of only 01 data structures. If the include file that you select has references to other include files, then their contents must be listed in the include file that you select.
Note: You can change the default behavior of the file extension by using the File Extension Support table in the General tab of the Importer > PL/I preferences page.

Importing a remote file:

To import a remote file:
  1. In the Import Source Files wizard, click Remote. A remote file selection window opens.
  2. In the remote file selection window, select either a complete PL/I program or a PL/I include file:
    • If you select a complete PL/I program, choose one of the following options:
      • Import the selected resource only: Select this option to import only the selected file.
      • Import the selected resource and any dependent files: Select this option to import (copy) the selected file and also import all other files that the selected file has dependencies on.
    • If you select an include file, a message is displayed stating that the selected include file is expected to have no dependencies. (You can select to have this message not be displayed again.)

Troubleshooting information for importing PL/I source files

If you encounter errors when trying to download a PL/I source file from a remote system, consult the following checklist of common problems:
  1. The following messages may appear in the Refresh Dependencies Problems window. Click Details to display the specific error message:
    • The following message may appear if the JES subsystem is not connected.
      JES subsystem is not connected. 
       Connect to the subsystem and retry the operation.
    • The following message may appear if, for example, you have specified a PDS that does not exist in the SYSLIB.
      The submitted job has ended with a JCL error. 
       Check the build properties and retry the operation. 

  2. If you see error messages related to "Cannot find/open INCLUDE file" when you are try to generate output files from a single-service project, it is possible that files on which an imported PL/I source file has dependencies that were not imported with the PL/I source file into your Enterprise Service Tools project. To resolve this problem, provide all the PDSs which contain the dependencies, and import the source file again.