Cross Platform Commander

What is Cross Platform Commander?

Cross Platform Commander (CPC) is middleware that provides a bridge between different computing platforms—Unix, Linux, HP-UX, Solaris, Windows, IBM z Series, IBM i systems, and more. CPC can be used to integrate any number of computing systems and applications across an enterprise.

CPC can solve or simplify a wide variety of problems in which multiple machines or several operating systems are involved. For example, a Unix machine can perform work on a z OS mainframe and integrate the results locally. Similarly, a mainframe job scheduler can become a cross-platform job scheduler, or a Windows machine can integrate Unix data into its applications.

Features of Cross Platform Commander

Our Cross Platform Commander (CPC) middleware consists of three types of components: clients, managers, and servers. A client connects to a manager, and the manager directs work to a server. The manager validates the user, accepts work, and leads the work to the appropriate server. The server performs the requested work, and the output is returned to the client via the manager.

Unlike other middleware solutions, CPC does not favor one platform or operating system over another. All components can be run on any supported platform, and all operations can be performed from any platform to any platform. Platform-specific job-scheduling products can use CPC to schedule work on machines running other operating systems or even separate computers running the same operating system. CPC is flexible and configurable. CPC components can be installed and configured in a variety of ways to address the needs of any organization.

This diagram shows how CPC is able to be the middleware for mainframe, Unix, Linux, HP-UX, Solaris, Windows, IBM z, as400, IBM i, and more.

Show All Hide All
  • Open Architecture

    The basic unit of work is a script file. A CPC script contains conditional logic and commands to be executed in the native environment of a remote CPC server on behalf of a local CPC client. CPC clients can drive Perl, Unix shell scripts, and Windows scripts to access data on legacy systems. Processing and formatting of the data can be done on the legacy system. The system displaying the data does not require intimate knowledge of the information it presents.

  • Flexible Scripting

    On Unix and Windows CPC servers, script commands can execute programs or native scripts. CPC traps stdout (screen output) and stderr (error message output) and returns these files to the client. On z OS CPC servers, script commands can run programs directly, execute REXX (Restructured Extended Executor) execs, or submit batch JCL jobs. In any of these modes, the output of any DD (data definition) statement can be captured and returned to the client.

    Cross Platform Commander - Flexible Scripting

  • Data Encryption / Compression / Security

    All communications can be encrypted for security purposes and compressed to conserve bandwidth. Nine levels of encryption and three levels of compression are provided with CPC. Internal security controls access to all features, commands, and components.

  • Flexible Interfaces

    CPC’s interfaces are also flexible, allowing CPC to be run from multiple sources, including:

    • Batch JCL
    • REXX
    • Unix shell commands
    • Unix command lines
    • AS400 commands and jobs
    • Scripting languages

    Cross Platform Commander - Flexible Interfaces

  • Supports All Platforms

    CPC supports multiple platforms:

    • zOS/MVS, IBM Z
    • i5, AS/400, IBM i
    • Solaris
    • HP-UX
    • AIX
    • z/Linux
    • Linux x86
    • Linux S/390
    • Windows
    • and more

    Our CPC middleware technology is able to connect a multitude of systems including the Mainframe, IBM i, Unix, Linux, Solaris, Windows, and More!