| Dovetailed Technologies | Solutions | Support | Contact Us |
You are here :: Home :: Solutions :: Co:Z Launcher
The Co:Z Launcher was designed to allow any z/OS batch job to remotely launch a process on a distributed system, redirecting input and output from the remote process to traditional z/OS datasets or spool files. This functionality is particularly well suited for the IBM zEnterprise hybrid processor architecture, relocating traditional z/OS programs to z/BX blade servers running AIX, Linux, or Windows.
Remote processes are securely launched using proven SSH (Secure Shell) technology to the target platform, which may be Linux, Windows, or other Unix/POSIX platforms.
The remote/target process can use Dataset Pipes commands or APIs to "reach back" into the Co:Z Launcher jobstep and access z/OS datasets - by name or "DD" reference. These APIs allow for very flexible control over the conversion of record-oriented z/OS datasets to or from byte-stream pipes usable by the target application.
From the perspective of the z/OS operator, the job can be managed and controlled like other batch jobs. Output from long running remote processes is immediately available on SYSOUT spool files. z/OS console commands can be used to control, monitor the remote process. z/OS automation facilities can be engaged throughout to manage and control distributed processes started by the Co:Z Launcher.
Co:Z Target System Toolkit
If you wish to use the Co:Z Launcher to launch remote processes to non z/OS systems, install the associated Co:Z Target System Toolkit on each remote system. The Co:Z Target System Toolkit is available in many distributions. Refer to the downloads page for the complete list.
The Co:Z Target System Toolkit is Linux Standard Base 3.0 certified. Binary RPMS are available for any LSB 3.0 compliant Linux distribution on several hardware platforms, including IBM z Series. The Co:Z Target System Toolkit has also been certified by IBM's Chiphopper program.
Examples:
Co:Z Documentation provides several examples and demos illustrating how to use the Co:Z Launcher. Additionally, we have documented case studies that detail how to convert existing z/OS programs to run on a distributed system:
Features:
- Securely launch and control remote processes (programs, scripts, etc.) from a z/OS batch job step or started task.
- Redirect input and output of remote process to DDs in the launching job step.
- Target process exit code is captured as job step condition code.
- Co:Z Launcher job step acts as a server for z/OS dataset I/O.
- z/OS console commands can be used to monitor, control, and send input to remote process.
- Existing z/OS scheduling and automation facilities can be used to schedule, monitor, and control processes on all servers on the network.
- Dataset Pipes client commands and APIs provide flexible conversion of z/OS datasets to streams for use in target applications. Options allow for control of line rules, translation, padding/truncation, dataset allocation and DCB processing.
Supported Environments:
z/OS Host Requirements
- z/OS V1R4 or later
- IBM Ported Tools for z/OS (OpenSSH)
Windows Target System Requirements
- Supports 32-bit Windows environments (Windows NT, 2000, XP, Vista)
- Requires the Cygwin environment
Unix/POSIX/Linux Target System Requirements
- An SSHD server, compatible with OpenSSH