EGL support for VSAM files

To access a VSAM data set, you can use indexed, relative, and serial records if the file type in the resource association element for the record is vsam, vsamrs, or ibmcobol.
Three record stereotypes correspond to VSAM files:
These resource association file types provide VSAM access:

Remote VSAM support

To access remote VSAM files on z/OS when you debug EGL code on Windows or when you run that code in an application server:
  • Satisfy the access prerequisites
  • Provide resource association information and reference the resource association part from the build descriptor that you use for debugging your program

Access prerequisites

To access VSAM files, you first define the VSAM file on the system where you want the file to reside.

Remote VSAM access requires that you install the Distributed File Manager (DFM) on the workstation. Additional capabilities are also available in the JAR file that contains the DFM installation code.

Do as follows:
  1. Find the following subdirectory:
      <installDir>\eclipse\plugins
    where <installdir> is the installation directory for your product.
  2. In that directory, find the following JAR file:
      com.ibm.etools.egl.java.binaries_<version>.jar
    where <version> is a version number, such as 7.1.101.v20090718_0331.
To gain remote VSAM access, do as follows:
  1. Find the file EGLRuntimes\win\bin\Vsamwin.zip within the JAR file
  2. Extract Vsamwin.zip into a new directory
  3. Follow the directions in the extracted INSTALL.README file.
The JAR file makes possible two other capabilities, which do not require the installation of the DFM. Those features are as follows:
  1. Calls to non-EGL-generated programs, where the callLink element of the linkage options part has the following settings:
    • The remoteComType property is set to DISTINCT
    • The remotePgmType property is set to EXTERNALLYDEFINED
  2. Access to the following functions, which run operating system commands in the development environment: SysLib.callCmd and SysLib.startCmd.
To use those two features, retrieve additional content from the JAR file:
  1. Extract fda7.jar to the JVM CLASSPATH on the development workstation
  2. Extract the platform-specific files:
    • For Linux, the files are in the Linux directory. After you extract the files, change the PATH and LD_LIBRARY_PATH environment variables so that they reference the directory that contains those files.
    • For the supported Windows platforms, the files are in the Win32 directory. After you extract the files, change the PATH environment variable so that it references the directory that contains those files.

Resource Association

When you create the resource association part to use when you debug your EGL program on Windows, specify the file type and systemName:
File type
Set the file type to ibmcobol.
systemName
Specify the system name:
  \\machineName\qualifier.fileName
machineName
The SNA LU alias name as specified in the SNA configuration
qualifier.fileName
The VSAM data set name, including a qualifier

The naming convention is similar to the Universal Naming Convention (UNC) format. For details on UNC format, see the Distributed FileManager User's Guide, which is included in the vsamwin.zip file.

For more details, see “VSAM file access.”


Feedback