Batch Environment

JCLs coming from mainframe system must be converted into UNIX/Linux shell scripts or Windows scripting to run.

To minimize the changes in user programs and batch scheduling flow, the logic of the script must reflect the logic of the source JCL. Very often this logic is strictly dependant or based on some basic features of mainframe OSes (i.e. DISPOSITIONs) which are not available on UNIX/Linux and Windows systems: XFRAME supplies many of this missing features through its core components (i.e. XVSAM and XSORT) and some auxiliary utilities.

Furthermore, the XFRAME JCL converter (xmvsconv) translates the source JCL codes into corresponding C or Korn shell statements for UNIX/Linux and Windows Scripting Host (WSH) for Windows, using, wherever is possible, system native functions or constructs to emulate the mainframe behaviour.

On UNIX/Linux, VSE JCLs can only be migrated using the C shell, while when migrating z/OS JCLs both C shell and Korn Shell may be used, depending on the presence of GOTO statements or not.

The conversion logic as well as the auxiliary utilities are described in the following pages.

Running JCL scripts

Obviously, converted JCLs are standard C or Korn shell scripts, therefore may be started as a standard script.

I.e. Unix/Linux:

# csh MYJCL01.csh

I.e. Windows:

C:\> cscript MYJCL01.wsf