The z/VSE e-business connectors (5686-VS6-35 and 5686-VS6-38) enable you to integrate your VSE system into an e-business world. You can have real time access to z/VSE resources (like VSE/VSAM, VSE/POWER, DL/I, Librarian, VSE/ICCF, console) from remote platforms. You can also access remote data (like databases or flat files) from your z/VSE programs. In addition there are a set of utilities for download, that helps you to manage your z/VSE system.
To read more about a specific component, click on the area of your interest in the picture, or choose one.
VSE/ESA 2.5 introduced the Java-based connector, which enables you to write Java applications that access z/VSE data and functionality. You can have real time access to z/VSE resources (like VSE/VSAM, VSE/POWER, DL/I, Librarian, VSE/ICCF, console) from remote platforms.
The Java-based connector is part of the z/VSE e-business connectors component (5686-VS6-35 and 5686-VS6-38) and consists of two parts:
The z/VSE Connector Client provides extensive online documentation about the z/VSE connectors, 2-tier and 3-tier environments, and writing z/VSE-based Web applications. See the z/VSE Navigator application for a ready-to-run tool, which makes use of this class library.
Web services is a technology that allows applications to communicate with each other in a platform- and programming language-independent manner. A Web service is a software interface that describes a collection of operations that can be accessed over the network through standardized XML messaging. It uses protocols based on the XML language to describe an operation to be executed or data to be exchanged with another Web service.
SOAP is a lightweight protocol for exchange of information in a decentralized, distributed environment. It is an XML based protocol that consists of three parts: an envelope that defines a framework for describing what is in a message and how to process it, a set of encoding rules for expressing instances of application-defined data types, and a convention for representing remote procedure calls and responses. SOAP can potentially be used in combination with a variety of other protocols; however, the only bindings defined in this document describe how to use SOAP in combination with HTTP and HTTP Extension Framework.
Since VSE/ESA 2.7 there is a SOAP implementation available for CICS TS. It is also available for VSE/ESA 2.6 with APAR PQ78973 / PTF UQ81044. The SOAP implementation is part of the z/VSE e-business Connectors component (5686-VS6-35 and 5686-VS6-38) and runs within CICS TS. A simple SOAP example for z/VSE is part of the z/VSE Connector Client.
The implementation allows a z/VSE system to act as a Web Service provider (server) and as a Web Service requestor (client).
Note: The z/VSE SOAP implementation does not have any z/VSE specific workstation part. There are a lot of SOAP implementations available for various operating systems and programming languages.
The SOAP interfaces are defined by the C-header file IESSOAPH.H in PRD1.BASE. For more information please see the z/VSE e-business Connectors User's Guide.
The CICS2WS Toolkit is a development tool that helps you to use Web Services with your existing CICS programs. The tool reads WSDL files and Copybooks and creates proxy code that you use as a layer between your existing programs and the z/VSE SOAP engine. The proxy code is generated as Assembler program, therefor you do not need a COBOL or PL/I compiler.
It allows a z/VSE system to act as a Web Service provider (server) and as a Web Service requestor (client) and can create proxy code for both scenarios.
The VSAM Redirector allows you to redirect all accesses to a certain VSAM file into any other file system or database on any other (Java-enabled) platform.
The VSAM Redirector connector is part of the z/VSE e-business connectors component (5686-VS6-35 and 5686-VS6-38) and consists of two parts:
You redirect access to a VSAM file by setting up the Redirector's config table (see job skeleton SKRDCFG in ICCF library 59), which specifies a list of VSAM files and their new locations.
The VSAM Redirector can be used to migrate a VSE/VSAM file to a DB2 database running on a Linux on IBM z Systems in another LPAR, or running on any other Java enabled platform. By utilizing the VSAM Redirector your existing VSAM programs do not require any revisions.
The z/VSE Script Server provides access to z/VSE resources using the Java based connectors, but without writing Java programs. The z/VSE Script Server is part of the z/VSE e-business connectors component (5686-VS6-35 and 5686-VS6-38) and is used to execute so called z/VSE scripts. z/VSE scripts are written in a simple script language. It provides statements like if, while, for to control the program flow. z/VSE scripts can use various script commands to access z/VSE resources.
A z/VSE Script can be invoked by any kind of programs (especially non Java Programs). The downloadable package contains samples to invoke a z/VSE script from office applications like Microsoft Excel or Lotus 1-2-3. The samples shows how to read a VSAM record and include it into a spread sheet. You can also call a z/VSE Script from a z/VSE program (batch or CICS). This allows you to run processes on the distributed side (e.g. as a replacement for REXEC).
The Fast Path to Linux on z Systems (Linux Fast Path for short, or even LFP) allows selected TCP/IP applications to communicate with the TCP/IP stack on Linux on z Systems without using a TCP/IP stack on z/VSE.
All socket requests are transparently forwarded to a Linux on z Systems system. On Linux on z Systems, the LFP daemon must run. This daemon fulfills all socket requests by forwarding them to the Linux TCP/IP stack.
The Linux Fast Path can be run in either a z/VM environment or an LPAR environment.
The z/VSE MQ Client Trigger Monitor function provided with z/VSE V6.1, APAR PI42615 / PTF UI28409 (z/VSE 5.2), or APAR PI42612 / PTF UI28408 (z/VSE 5.1) implements a trigger monitor to be used with the MQ Client on z/VSE. Similar to the MQ Server on z/VSE, the z/VSE MQ Client Trigger Monitor runs under CICS and allows triggering CICS applications when messages arrive on queues.
The triggering performed by the z/VSE MQ Client Trigger Monitor works the same way as it did with WebSphere MQ for z/VSE V3.0 (which is no longer available and no longer supported). Thus no changes in the triggered applications are required specific to the use of the z/VSE MQ Client Trigger Monitor. However, the triggered applications must have been migrated to use the MQ Client instead of the MQ Server.
The z/VSE MQ Client Trigger Monitor works exactly the same way as trigger monitors on other platforms. Thus the trigger setup and configuration is the same as for other triggering monitors.
The Database Call Level Interface (DBCLI) allows z/VSE applications to access a relational database on any suitable database server. Therefore, you have the flexibility of being able to choose a database server (IBM DB2, Oracle, Microsoft SQL Server, MySQL, and so on) that runs on a platform other than z/VSE.
Because neither the DBCLI client nor the DBCLI server inspect the SQL statements being used by your application program, you can use any type of SQL statements and SQL dialect that are supported by the Vendor's JDBC Driver providing the database-provider also supplies a suitable JDBC driver.
The z/VSE DBCLI consist of 2 main parts:
The DBCLI client provides a programming API for your application programs:
The z/VSE Navigator Function provides a graphical user interface (GUI) for the z/VSE operating system, which behaves very much like file managers that you know from other platforms, such as Windows (Explorer). The difference is, that it includes host based z/VSE file systems (VSE Librarian, VSE/POWER queues, VSE/ICCF, VSE/VSAM) and provides host specific functions, such as Generate and submit z/VSE jobs, Operator Console, List VTOC, Retrace products and PTFs, Display phases in the SVA, Display host CPU activity, and many more.
The z/VSE Navigator is a client/server Java application that is based on the z/VSE e-business Connectors, which are delivered as part of VSE/ESA 2.5 and later releases. The z/VSE Navigator client is implemented using the z/VSE Java Beans that are part of the z/VSE e-business Connectors.
The VSAM Maptool allows to create a data map for a given VSE/VSAM file. Another way to create a VSAM map is using the z/VSE Java Beans VSEVsamMap, VSEVsamView, and VSEVsamField, or using the IDCAMS RECMAP command.
The VSAM Maptool allows you to create a map from parsing a given COBOL or PL/I copy book. Additionally, the VSAM Maptool allows you to:
Examples are provided with the VSAM Maptool installation package.
The VSEPrint utility allows you to print VSE/POWER list queue entries on any locally or LAN-attached printer. The queue entry can be formatted for proper output by specifying a meta-file, which contains instructions for formatting the file. The print-file can be previewed on the platform where the LAN-printer is attached.
On z/VSE, the TCP/IP command DEFINE EVENT is used to setup a listener for list queue entries which have a given class. These queue entries are then sent via AUTOFTP to a platform, where the VSEPrint utility runs. The VSEPrint utility then performs all print setup, formatting and optional previewing.
Keyman/VSE is a tool to manage the z/VSE specific public key infrastructure. It can create RSA key pairs, create and sign certificates, and upload them to a z/VSE system. It can also read and write PKCS#12 keyring files (PFX). Recent updates include support for Java key stores (JKS) and OpenPGP.
In general, Keyman/VSE can
In addition to these basic functions, Keyman/VSE provides two "Wizard dialogs" for
Note: This tool is based on the VSE Connector Client and its current version requires a JRE/JDK 1.5 or higher.
The z/VSE Health Checker is a Java-based system diagnosis utility to retrieve, display, and analyze performance relevant data from a z/VSE system. Gathered data can be exported and imported in XML format. A health check is performed by applying a set of rules against a snapshot of retrieved z/VSE data.
z/VSE data is retrieved by sending console commands, submitting VSE/POWER jobs, downloading z/VSE Librarian members, and invoking CICS transactions. There is no dependency to any vendor tools. The output is transferred to the workstation, parsed, and displayed in the GUI for further analysis. The z/VSE data is retrieved using the z/VSE System class library and the z/VSE System class library, that are also available separately.
The z/VSE Health Checker does not change any system parameters on z/VSE. All actions only read data from z/VSE. Although the whole process of getting data from z/VSE can take up to several minutes, this is just elapsed time. CPU overhead is minimal.
Note: This tool is based on the z/VSE Connector Client and requires a JRE/JDK 1.5 or higher.
The z/VSE System class library provides a Java API to access general z/VSE system parameters. Data is retrieved from a z/VSE system on the basis of the z/VSE Connector Client by executing console commands, invoking CICS transactions, submitting VSE/POWER jobs, or downloading z/VSE library members. The API includes access to data from z/VSE components, like CICS, VSE/POWER, VTAM, or TCP/IP, but also output from basic commands like SIR, GETVIS, MAP, PRTY, and others.
Note: This class library is based on the z/VSE Connector Client and requires a JRE/JDK 1.5 or higher.
The z/VSE Security class library provides a Java API to access security related z/VSE system parameters. Data is retrieved from a z/VSE system on the basis of the z/VSE Connector Client by executing console commands, submitting VSE/POWER jobs, or downloading z/VSE library members.
Note: This class library is based on the z/VSE Connector Client and requires a JRE/JDK 1.5 or higher.
The Virtual z/VSE FTP Daemon can be installed on any Java-enabled platform and emulates an FTP server. The actual access to z/VSE resources is done using the z/VSE Connector Server.
The Virtual z/VSE FTP Daemon:
Note: This tool is based on the VSE Connector Client and requires a JRE/JDK 1.5 or higher.
Get the latest news about z/VSE:
IBM z13 delivers a data and transaction system reinvented as a system of insight for digital business.