### Configuring SdU for Remote Data Access

This section describes the base configuration requirements for SdU setup for using Remote Data Access. See VSAM in a Distributed Environment, on the Online Book tab of the Information Notebook for additional information on setting up for and working with remote files.

If you plan to use APPC for Remote E/C/D (which uses SdU), refer to the E/C/D section.

There are two files that you must update: STARTDFM.CMD and CONFIG.DFM.

#### Update the STARTDFM.CMD file

The STARTDFM.CMD file is used to activate the remote data support on your workstation.

A sample STARTDFM.CMD file is supplied in the VisualAge COBOL's samples subdirectory named \SAMPLES\SDU; change this file to fit your environment.

1. Make a working copy of the file by copying it into the VisualAge COBOL's BIN directory that is in your CONFIG.SYS PATH.
2. Search for the string CALL DFMDRIVE near the bottom of the file. Change the line for MVS at the bottom of the file to: 'CALL DFMDRIVE ASSIGN x //mvsluname' where mvsluname is the value given to you by your LAN administrator for the MVS LU name at your location. This call to DFMDRIVE makes an association between an OS/2 drive letter and your target (MVS) system.
3. Change the x to whatever OS/2 drive letter you want to use on your workstation.
4. Activate this CALL statement by removing the surrounding comment symbols. The comment at the end of the line can be left alone.

#### Update the CONFIG.DFM file

The CONFIG.DFM file specifies your workstation environment to the remote data component.

A sample CONFIG.DFM file is supplied in the VisualAge COBOL's samples subdirectory named \SAMPLES\SDU; change this file to fit your environment. Make a working copy of the file by copying it into the VisualAge for COBOL's \BIN directory that is in your CONFIG.SYS PATH.

1. Search for the string DFM_TARGET.

   Several of these statements are supplied. Activate the entry that corresponds to the MVS system that will be your target system by removing the semicolon comment symbol.

2. To update the REMOTE_LU keyword to reference your target system LU name, change the supplied value of MVS to:

             remote_lu(yourmvslu)

   where yourmvslu is the LU name supplied to you by your LAN administrator.
3. Later when you start the remote data support on your workstation, you will be prompted for your MVS user ID and password.
4. Search for the string LOCAL_LU, which is a statement by itself.

   Replace the supplied LU name inside the parentheses, APPCLU, with the LU name defined by your LAN administrator for your OS/2 workstation.

5. Search for the string MODE_NAME, which is a statement by itself.

   The supplied mode value inside the parentheses is the mode value of QPCSUPP.

   Note: This might not be required at your site.

   The QPCSUPP mode must be defined to MVS via VTAM before you can use it with DFM. If it were not defined when DFM/MVS was installed, you can use the mode of #INTER, which is supplied with Communications Manager and VTAM.

6. Search for the string DEFAULT_DFM_TARGET, which is a statement by itself.

   Replace the supplied value inside the parentheses with the LU name defined by your LAN administrator for your MVS system. This is the same value you used earlier for your DFM_TARGET name. Activate the statement by removing the semicolon comment symbol.

7. Data conversion between remote-local systems

   Your data conversion specifications are made with a single parameter or a special language that allows for field level control.

   When an entire file must be converted (for example, EBCDIC to ASCII for a COBOL PDS member), an additional parameter can be added to the OS/2 drive that represents the remote MVS system. This is done from an OS/2 window by entering:

             DFMDRIVE ASSIGN X:X0"\, TEXT" X0 //mvsluname

   where x is the drive letter representing the MVS system. You may also use a GUI interface by entering the DFMDRIVE command without any parameters. From the GUI, select a drive letter and press Enter. Then enter :font facename='Courier' size=15x9.\,TEXT :font facename=default size=0x0.into the Directory entry field, located near the bottom of the screen. This entry will specify that ASCII-EBCDIC data conversion is to be done on the entire file. This type of conversion is referred to as "Stream Data Conversion" by the Distributed File Manager.

   When you need to be more granular than an entire file and convert individual fields of a record (for example, a VSAM file), provide field-level specifications in a special file.