Importing COBOL source files from a remote system

Edit online

This topic describes how to use the Import Source Files wizard to import COBOL source files from a remote host 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 host system (see Importing source files into a single-service project).

This topic describes how to use the Import Source Files wizard to import COBOL 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 COBOL source files

The Import Source Files wizard has the following requirements for importing COBOL source files from a remote system:
  • The remote file must be mapped to one of the following extensions: .cbl, .cob, ccp or .cpy.
  • If the file is mapped to a .cbl, .cob or .ccp extension, then the file is assumed to be a complete COBOL program that can have dependencies on other files. If the COBOL program does in fact have dependencies on other files, then you should provide the information about the partitioned data sets (PDSs) where the copy books exist by setting the SYSLIB for the remote file.
  • If the file is mapped to .cpy, it is assumed to be a copy book consisting of only 01 data structures or 01 or 77 elementary data item definitions. If the copy book that you select has references to other copy books, then their contents must be listed in the copy book that you select.
Note: You can change the default behavior of the file extension by using the File Extension Support table in the More COBOL options tab of the Importer > Cobol 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 COBOL program or a copy book:
    • If you select a complete COBOL 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 a copy book, a message is displayed stating that the selected copy book is expected to have no dependencies. (You can select to have this message not be displayed again.)

Troubleshooting information for importing COBOL source files

If you encounter errors when trying to download a COBOL 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 "COPY library not found" when you are try to generate output files from a single-service project, it is possible that files on which an imported COBOL source file has dependencies were not imported with the COBOL 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.