The key component of J2U is responsible for the execution of unmodified JCL on the decentralized platform.

Represents the interface of the J2U Engine and accepts queries to be carried out in the J2U Engine.

The optional J2U Hierarchical Storage Management (HSM) Emulation provides functions to transfer files to more cost effective storage media. The configuration occurs as with z/OS via storage classes. In combination with archiving systems the files can be archived for the lifecycle of the job, reloaded, or deleted.

Provides the interface for the actual print system. The Print Daemon processes the spool files produced during the lifecycle of the job and carries out other functions depending on configuration such as conversion. It also transfers the prepared file for printing to the printing system connected such as VPSX or CUPS.

Integrated archiving of the job log files in the file system or a connected archiving system such as TSM.

Optional archiving of job lists (job output files) in the file system or in a connected archiving system such as TSM.

Creates access to launch execution commands directly to the J2U Engine from the console.

Enables the connection of diverse job schedulers such as TWS or Control-M to J2U.

The web application provides the central user interface for controlling and managing J2U.

Broadens the Eclipse IDE around functions for J2U. With the J2U plugin, jobs can be commenced directly from Eclipse IDE and the results displayed.

Unchanged use of productive batch procedures developed over many years without changing the JCL secures your investment and provides simultaneously for increased migration safety.
To put it briefly: With J2U, your batch production runs just as before but on a different platform.

J2U emulates JESx to carry out the z/OS-JCL as well as functionality and control commands from IBM utilities such as ICEGENER/IEBGENER, IEBCOPY, IDCAMS, IKJEFT01, IEFBR14, FTP, FTPS, SMTP, SORT.
The functions of the central catalogue under z/OS, which contains all information about all the files in the whole system, are built using database tables.
The logic of file handling within batch jobs remains completely unchanged.

J2U produces the typical JESx job lists, which provide information about the status and progress of jobs. Your production planning steers the batch procedures according to the usual guidelines.
For employees with long-term z/OS experience, this makes the possibility of a change to the new platform easier by using familiar JCL instructions.
The web front end J2U Control Panel for controlling and managing J2U provides functions that mirror similar tools used in z/OS.

Through the unchanged use of established batch procedures and associated jobs, there is no need to carry out all the usual tasks involved in migration projects or in testing each individual job. That means the lifecycle of the project is instantly reduced.