Rational Developer for System z

Importing COBOL files from a remote z/OS system

Follow the instructions in this topic if you want to use the Import COBOL Files wizard to import COBOL files and their dependent copy book files from a remote z/OS® system into your service flow project.
Follow these steps to configure the Remote Systems view in the Enterprise Service Tools perspective so that you can import COBOL files and their dependent copy book files from a remote z/OS system:
  1. Create a connection to the remote z/OS system using the Remote Systems view:
    1. Follow the steps in Step B3. (Optional) Create a connection to the remote z/OS system using the Remote Systems view to create an connection to MVS™ on the remote z/OS system.
    2. Verify that the connection is active.

  2. Modify the properties of the Partitioned Data Set (PDS) that contains the COBOL source file:
    Note: You must do this configuration on the PDS itself (for example, USER25.SFP003.USER.SRCLIB) inside the MVS Files folder. If you do this configuration on the MVS Files folder, then the configuration has no effect.
    1. In the Enterprise Service Tools perspective, in the Remote Systems view, expand MVS Files > My Data Sets.
    2. Right-click the PDS that contains the COBOL source file.
    3. Select Properties. The Properties window opens.
    4. If the COBOL source file in your PDS does not have the extension .cbl, then follow these steps to add the extension:
      1. In the left pane of the Properties window, select Mapping.
      2. In the right pane:
        1. Select Extension > Other.
        2. In the input field, type cbl without a leading period (cbl not .cbl).
    5. Modify the COBOL Settings property page:
      1. In the left pane, select COBOL Settings.
      2. In the right pane:
        1. Expand the procedure ELAXFCOC.
        2. Select the COBOL step.
        3. Click Edit Step. The COBOL Compile Step Options window opens.
        4. In the COBOL Compile Step Options window:
          1. Clear the field Debug Data Set.
          2. Clear the field Object Deck Data Set.
          3. In the Copy Libraries field, type the name of the PDS in which the copy book files are located.
            Note: You can enter multiple PDS names in this field. Type a space to separate each name from a following name.
          4. Select the Support Error Feedback check box if it is not already selected.
          5. The input field Data Set Qualifier for Compiler Errors must contain a valid data set qualifier. The default value is <userid.ERRCOB, where <userid is your user ID.
            Note: During the Show Dependencies operation (see step 5 below), when the Show Dependencies processor creates an output data set to contain status messages and error messages, the Show Dependencies processor uses this qualifier as a prefix to the name of the output data set.
            • The output data set is written using your RACF® permissions.
            • Before you attempt to import a COBOL file, verify that you have write access to the area that you specify in this data set qualifier.
          6. Click OK.
    6. Modify the JCL Job Card and Data Set page:
      1. In the left pane of the Properties window, select JCL Job Card and Data Set.
      2. In the right pane:
        1. In the JCL Job Card field, add a third line that contains the JCLLIB CARD value for the server that you are using.
    7. Click OK to close the Properties window.

  3. Modify the properties of the Partitioned Data Set (PDS) that contains the COBOL copy books:
    1. Right-click the PDS that contains the copy book files.
    2. Select Properties. The Properties window opens.
    3. If the copy book files in your PDS do not have the extension .cpy, then follow these steps to add the extension:
      1. In the left pane of the Properties window, select Mapping.
      2. In the right pane:
        1. Select Extension > Other.
        2. In the input field, type .cpy.
    4. Click OK to close the Properties window.
  4. Start the JES connection if it is not already connected:
    1. In the Remote Systems view, right-click the JES node.
    2. Select Connect.
  5. Verify that the Show Dependencies feature is now working correctly for this COBOL source file:
    1. Right-click the COBOL source file.
    2. Click Show Dependencies.
    3. The Remote Systems view attempts to show the dependencies of the COBOL source file by running the JCL statements that you modified on the JCL Job Card and Data Set page of the Properties window for the COBOL source code file (see step 3).

    If the JCL statements are successful, then the Remote Systems view displays the dependencies of copy book files on the COBOL source file that you right-clicked.

    Note: If an error occurs when you try to import a COBOL file from a remote z/OS system:
    1. In the Remote Systems view:
      1. Find the most recently submitted job. This is the Show Dependencies job.
      2. Open the Show Dependencies job and look for a JCL error, such as an invalid data set name.
    2. Fix the problem that caused the JCL error.
    3. Try again to import the remote COBOL file.

If the Show Dependencies operation completed successfully, then you should now be able to use the Import COBOL Files wizard to import the COBOL source file and its dependent copy book files from the remote z/OS system into your service flow project (see Starting the Import COBOL Files wizard).


Terms of use | Feedback

This information center is powered by Eclipse technology. (http://www.eclipse.org)