New Co:Z Release 7.1.1 is available. Review the Release Notes and Download.
New Co:Z Release 7.1.1 is available.

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.

Remote processes are securely launched using proven SSH (Secure Shell) technology to the target platform, which may be Linux 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

To use the Co:Z Launcher to launch remote processes to non z/OS systems, build and install the Co:Z Target System Toolkit source code on each remote system. Refer to the download page for instructions on building the source code.

Examples:

The Co:Z Launcher Examples section of the user's guide provides several examples.

Review z/OS Hybrid Batch for more information on the processing model as well as a short introduction video and case study.

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

  • V2R2 or later, with a minimum machine architecture of z10 and above
  • IBM z/OS OpenSSH - See our Quick Install Guide

Unix/POSIX/Linux Target System Requirements

  • An SSHD server, compatible with OpenSSH