### Configuring SdU for Remote E/C/D

This section describes the base configuration requirements for SdU setup for using Remote E/C/D. If you plan to use SdU for Remote Data Access, refer to SdU: data section.

To configure SdU, a customized CONFIG.DFM file must be present in the IBMCOBOL\MACROS directory. A sample CONFIG.DFM file can be obtained from the samples provided for SdU in the IBMCOBOL\SAMPLES\SDU directory.

The CONFIG.DFM file requirements for using Remote E/C/D are minimal. Only the following customizing is required:

- The DFM_TARGET must be defined.

  Defining the target consists of filling in the `remote_lu` name and system description. The `remote_lu` is the same as the Partner LU Alias defined in Figure 12 or the PLUALIAS described in Table 1. Remove all the comment indicators ( ; ) from column 1 on all the lines in the DFM_TARGET statement.

  Optionally you can define a userid in this section by adding `userid (youruser)` within the outer parentheses at the bottom of the DFM_TARGET description. If no userid is specified in CONFIG.DFM, SdU will prompt for it along with the password when the drives are being connected.

  Note: When connecting to the host with SdU, you must use the same userid as the one specified in MVSINFO.DAT)

- The LOCAL_LU must be defined.

  This is the same as the local node alias name defined in Figure 8 or the LUALIAS described in Table 1. Remove the comment indicator ( ; ) from column 1 of the LOCAL_LU statement.

- If there is more than one DFM_TARGET system defined, the DEFAULT_DFM_TARGET must be defined. If the DEFAULT_DFM_TARGET is defined, remove the comment indicator ( ; ) from the statement.
- Comment indicators ( ; ) should also be removed from column 1 of the following:
  - MODE_NAME statement
  - DEFAULT_CCSID statement

  Note that, for Remote Edit/Compile, the CCSID defaults to 850 rather than 500. Even if 500 is specified in the CONFIG.DFM file, Remote Edit Compile will override that specification with code page 850 due to translation problems with hex characters when editing files.

- In addition to the SdU setup, you also need to perform the steps described in the setup information under the Host Applications tab of the Information Notebook.

Figure 17 contains a sample CONFIG.DFM file using values from Table 1.

In order to submit batch jobs for processing on the host, you need to allocate the following two sequential data sets on the host:

  userid.DFMXTSO.SYSTSIN - FB LRECL=80
  userid.DFMXTSO.SYSTSPRT - VBA LRECL=125

The space values can be primary=10 and secondary=2 tracks.

#### Code page considerations

Your host MVS SMARTdata UTILITIES (SdU) server may support using only code page 850 for translation between host EBCDIC and workstation ASCII. Workstations configured for United States English typically default to use code page 437; however, code page 850 is almost identical to code page 437 and is sufficient for COBOL purposes.

To determine whether your host MVS SdU server can support your workstation default code page, do the following after you have performed all other required Remote Edit/Compile/Debug setup:

- Edit the MVSINFO.DAT file located in the MACROS directory.
  Insure that you have at least one drive defined to be accessed as text.
  Look for the line that reads:

      sdu pc_ccsid(850)

  Change the line to a comment so that it reads:

      *sdu pc_ccsid(850)

- From an OS/2 command prompt issue:

      iwzmstr

  You may be prompted for your TSO userid and password.

  When attempting to assign the first drive defined to be accessed as text, you may get a full screen message saying that contact to your host system for that drive has ended. In some cases the error message might not be in full screen and indicates that contact with the system has ended. If you get this message press the Esc key to cancel the message. If you get this message, your host MVS SdU server is not able to support your workstation default code page. You will get the error message for each drive to be accessed as text.

- From an OS/2 command prompt issue:

           iwzmstp

  This will terminate the connection to the host MVS SdU server.
- If your host MVS SdU server was not able to support using your workstation default code page, again edit the MVSINFO.DAT file located in the MACROS directory to restore the changed line so that it again reads:

           sdu pc_ccsid(850)

  and again from an OS/2 command prompt issue:

           iwzmstr

  This time you should not get any error messages. If you do not intend to immediately start using the Remote Edit/Compile/Debug facilities, from an OS/2 command prompt you can again issue:

           iwzmstp