Remote VSAM support for z/VSE

You can access remote VSAM files that are defined under z/VSE® and z/VSE CICS® when you run the EGL debugger on a Windows platform.

To access remote VSAM files on z/VSE, do as follows:

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 (Batch)

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

Remote VSAM access (for Batch) requires that you install VSE Connector Client on the workstation. Alternatively, you can use VSE Distributed Data Management (VSEDDM).

For VSEDDM, do as follows:

Find the following compressed file:
```
  installDir\bin\vsamwin.zip
```
where installDir is the installation directory for your product.
Extract vsamwin.zip into a new directory (whether on the development or runtime platform)

Add the following to your system's PATH environment variable:

vseddmDir\EGLDFM
vseddmDir\EGLDFM\DLL
vseddmDir\EGLDFM\DLL2
vseddmDir\EGLDFM\EXE

Where vseddmDir is the directory you extracted the files to.

To define your VSE host and login credentials, open a Command Prompt and navigate to the EGLDFM directory. Run the command bellow specifying your VSE host name and a valid user ID on that system. Provide your password at the prompt (it is visible!) and press Enter.

VSEDDMLO "VSE Host Name" "UseID"

This command creates a configuration file that is called vseddm.cfg in the EGLDFM directory. To complete this setup, create an environment variable that is called VSEDDM_CFG and assign it the value vseddmDir\EGLDFM\vseddm.cfg

Access prerequisites (CICS)

To remotely access VSAM files under the control of VSE CICS, you must install CICS Transaction Gateway on the workstation. For more information about remote access through CICS, see Installing and configuring remote VSAM support for CICS.

EGL Debugger Preferences

You must configure the EGL Debugger before it can access your remote VSAM files. Set the VSE Remote VSAM code page to the ASCII code page configured in your VSE Connector Server. Set the Character Encoding to the EBCDIC code page configured in your VSE Connector Server. Ensure that ctglient.jar (provided by CTG) is in the class path order if you are debugging through CICS. Ensure that VSEConnector.jar and cci.jar (provided by VSE Connector Client) is in the class path order if you are debugging through VSE Connector Client.

For more information, see Setting preferences for the EGL debugger.

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 as follows:

File type

Set the file type to vsam or ibmcobol.

systemName

For batch, specify the system name in the following way:

  VSE:\\machineName:portNumber\catalog ID\data set name

machineName: The host name or IP address of the VSE machine
portNumber: The port number that VSE Connector Server is listening on. The default value is 2893
catalog ID: The name of the VSE catalog that contains the VSAM file
data set name: The VSAM data set name, including a qualifier

Alternatively, you can use VSEDDM with the format :

  VDM:\\machineName\catalog ID\data set name

For CICS, specify the system name in the following way:

CTG:\\install_dns_or_ip:port\cics_region\dataset

install_dns_or_ip: The location where CTG is installed, regardless of platform
port: The port CTG is listening to
cics_region: The target CICS region as defined under CTG
dataset: The name of the VSAM file as defined in the FCT or the File RDO entry for the CICS region

For more information about remote access through CICS, see Installing and configuring remote VSAM support for CICS.

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