Downloads

• VSE Virtual Tape Server (updated 02/2018 for APAR PI92815)
• VSAM Redirector Server (updated 12/2017 for z/VSE V6.2 GA)
• VSE Connector Client (updated 12/2017 for z/VSE V6.2 GA)
• z/VSE Database Connector (updated 12/2017 for z/VSE V6.2 GA)
• VSE Script Server (updated 12/2017 for z/VSE V6.2 GA)
• Linux Fast Path Daemon (updated 12/2017 for z/VSE V6.2 GA)
• CICS2WS Toolkit Version 2.8 (updated 12/2017 for z/VSE V6.2 GA)
• Keyman/VSE (updated 03/2017)
• VSE Navigator (updated 03/2017)
• VSE Health Checker (updated 11/2016)
• VSE System class library (updated 11/2016)
• VSE Security class library (updated 11/2016)
• VSAM Maptool (updated 11/2015)

DISCLAIMER OF WARRANTIES:

Permission is granted to copy this Tools or Sample code for internal use only, provided that this permission notice and warranty disclaimer appears in all copies.

THIS TOOLS OR SAMPLE CODE IS LICENSED TO YOU AS-IS.

IBM AND ITS SUPPLIERS AND LICENSORS DISCLAIM ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, IN SUCH SAMPLE CODE, INCLUDING THE WARRANTY OF NON-INFRINGEMENT AND THE IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT WILL IBM OR ITS LICENSORS OR SUPPLIERS BE LIABLE FOR ANY DAMAGES ARISING OUT OF THE USE OF OR INABILITY TO USE THE TOOLS OR SAMPLE CODE, DISTRIBUTION OF THE TOOLS OR SAMPLE CODE, OR COMBINATION OF THE TOOLS OR SAMPLE CODE WITH ANY OTHER CODE. IN NO EVENT SHALL IBM OR ITS LICENSORS AND SUPPLIERS BE LIABLE FOR ANY LOST REVENUE, LOST PROFITS OR DATA, OR FOR DIRECT, INDIRECT, SPECIAL, CONSEQUENTIAL,INCIDENTAL OR PUNITIVE DAMAGES, HOWEVER CAUSED AND REGARDLESS OF THE THEORY OF LIABILITY, EVEN IF IBM OR ITS LICENSORS OR SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

Back to top

The VSE Connectors, tools and samples are downloaded to your workstation as a ZIP file. Some components are also available as WBOOK in VSE library PRD2.PROD. You must install the VSE Connector Workstation Code from the extended base tape prior to downloading. If you download it from PRD2.PROD, you must rename the WBOOK to <filename>.zip before extracting it.

In order to install and use the VSE Connetcors, tools and samples, you need a Java runtime environment (JRE) or a Java developers kit (JDK) 1.5 or higher. You can download JDKs/JREs for various platforms from IBM developerWorks or Oracle. To verify if Java is installed on your workstation enter the following command in a command prompt or shell:
java -version
In case Java is installed, you should see something like this:
java version "1.6.0_33"
Java(TM) SE Runtime Environment (build 1.6.0_33-b05)
Java HotSpot(TM) Client VM (build 20.8-b03, mixed mode, sharing)
If Java is not installed on your computer or can not be found in the PATH, you would see a message like
'java' is not recognized as an internal or
external command, operable program or batch file.

Note: On Windows Windows 7 or later, the Java Runtime installation process does no longer copy the Java executable (java.exe) into the C:\Windows\System32\ folder. That means you have to manually update the PATH environment variable and add the Java installation directory (e.g. "C:\Program Files\Java\jre7\bin" or "C:\Program Files (x86)\Java\jre7\bin") to the PATH. This can be done via Control Panel → System → Advanced System Settings → Advanced Tab → Environment Variables. Locate the PATH variable either in the user or system variables, and add the Java's bin directory (e.g. "C:\Program Files\Java\jre7\bin" or "C:\Program Files (x86)\Java\jre7\bin") to the end of the PATH variable, separated by a semi colon (;).

Most components are packaged into an Java based installer. This installer is contained in the file setup.jar and can be invoked by running one of the install scripts setup.bat (Windows), setup.cmd (OS/2 and Windows), setup.sh (Linux, Unix). When running the Java installer, some dialog boxes will appear which guide you through the installation.

If you want to install the component on a system that does not have a graphical user interface (e.g. Linux/Unix without a X-Windows), you may run the installer in text mode (you may have to edit the setup script):
setup.bat -t

If you are updating an existing installation, please reinstall the component into the same directory. You may want to save your modified configuration or sample files before reinstalling. During the installation process you will be asked to overwrite existing files. Answer 'Yes' to all files (except your modified configuration or sample files).

Please refer to the frequently asked questions for information on how to solve common problems.

Back to top