Oracle Tuxedo Application Rehosting Workbench JCL Converter

Overview

Purpose

Oracle Tuxedo Application Rehosting Workbench JCL Translator translates complete z/OS JCL files (main jobs, PROCs, INCLUDEs, etc.) into complete Unix/Linux shell scripts using the Korn shell (ksh) syntax and the Oracle Tuxedo Application Runtime for Batch components.

Skills

This guide is intended for anyone using the Rehosting Workbench to convert from z/OS JCL to UNIX/ Linux Korn Shell script.

When translating JCL, a good knowledge of JCL, Z/OS utilities and UNIX/Linux Korn Shell is required.

In particular, a knowledge of how Job Control Language (JCL) manages programs, jobs and utilities and allocates necessary resources to fulfill required functions.

In addition a good knowledge of how target shell scripts are structured and how Batch Runtime components are used will help the user to better understand JCL translation.

See also

For more information, see:

•	Oracle Tuxedo Application Rehosting Workbench Reference Guide.

•	Oracle Tuxedo Application Runtime for Batch User Guide

Organization

Translating JCL is described in the following sections:

•	Requirements & Prerequisites

•	Overview of the JCL Translator in the replatforming process

•	Translation steps

•	Using a make file

Requirements & Prerequisites

Cataloguing requirements

Cataloguing is mandatory before running the JCL translator in order to check the consistency of the assets to be migrated and fix any errors related either to syntax or to the coherency (missing or unused components) of the asset.

Data Conversion

The data migration process must have been performed before the JCL translation is started. This dependency is because the file migration tools generate some of the configuration files read by the JCL Translator. The configuration files from data conversion are documented in the Oracle Tuxedo Application Rehosting Workbench Reference Guide.

Overview of the JCL Translator in the replatforming process

The inputs to the Rehosting Workbench JCL Translator process are:

•	The abstract syntax trees of the JCL stored in the pob files produced by the Oracle Tuxedo Application Rehosting Workbench Cataloger.

•	A set of configuration files produced by the data conversion tools that specifies information about the Oracle Tuxedo Application Rehosting Workbench DB2 to Oracle Converter conversion and the Oracle Tuxedo Application Rehosting Workbench DB2 to Oracle Converter conversion.

•	A set of configuration files which are either:

•	Generated by other Oracle Tuxedo Application Rehosting Workbench tools, the e Oracle Tuxedo Application Rehosting Workbench DB2 to Oracle Converter provides the JCL translator with the list of files to be converted to Oracle tables

•	Supplied together with the Rehosting Workbench and customizable.

Translation steps

This section provides information and procedures for:

Building and setting the configuration files

Translation steps

Checking results

Building and setting the configuration files

In addition to the AST of the JCL(s) to convert produced by the Oracle Tuxedo Application Rehosting Workbench Cataloger, the Rehosting Workbench JCL Translator takes as input a main configuration file that specifies various aspects of the translation, such as:

•	Customizable top skeleton and bottom skeleton;

•	Root pathname for migrated data files, temporary files and spool files;

•	The list of data files converted to Oracle tables;

•	The sort utility to use on the target platform;

•	Component and data-file renaming information;

•	Program-launcher configuration;

This file is very easy to write using any standard text editor, or to generate from other sources of information. below, we comment a sample of configuration file written to translate JCL files in the simple application STFILEORA provided with the Rehosting Workbench tools.

The main configuration file also refers to separate sub-files which are either:

•	Generated by other Oracle Tuxedo Application Rehosting Workbench tools,

•	Supplied together with the Rehosting Workbench (and customizable)

•	Wholly written by the user.

Oracle Tuxedo Application Rehosting Workbench comes with examples of configuration files.

The main configuration file for the JCL translation is called config-trad-JCL.desc in this guide for use with the Simple Application application.

The following sections describe the different configuration parameters and configuration sub-files and gives a full sample at the end of this section.

Top skeleton and Bottom skeleton

The sub-files specified by the two options top-skeleton and bottom-skeleton represent respectively a header file and a footer file for the generated script. You can customize these files.

Listing 7‑1 Top skeleton and bottom skeleton entries in the main configuration file

top-skeleton = "../param/top-ksh.txt"

bottom-skeleton = "../param/bottom-ksh.txt"

 

Listing 7‑2 Example of top-ksh.txt prolog code

#@(#)-------------------------------------------------------------------

#@(#)- SCRIPT NAME == $[JOBNAME].ksh --- VERSION OF $[DATE]

#@(#)- AUTHOR ==

#@(#)- TREATMENT ==

#@(#)- OBSERVATIONS == MAINFRAME MIGRATION

#@(#)- …..

 

Where:

JOBNAME

Will take the name of the current JOB after translation.

DATE

Is the generation date of the KSH script.

List of data files converted to Oracle tables

When files are converted to Oracle tables, the main configuration file must reference a sub-configuration file such as:

file-list-in-table = "../param/dynamic-config/File-in-table.txt"

This sub-file is generated by the Oracle Tuxedo Application Rehosting Workbench File-to-Oracle Converter. This file indicates to the JCL Translator, which are the files that will be converted to Oracle tables in order to correctly translate the steps involving these files. In our example PJ01AAA.SS.VSAM.CUSTOMER is the file to be converted.

For example, when the JCL source involves files that will be converted to Oracle tables, the corresponding shell script uses the Batch Runtime function m_ProgramExec with the -b option to execute a Cobol program. The -b option indicates a connection to the database must be opened before executing the program. For example:

m_ProgramExec -b RSSABB01

Full example configuration

The general options root-skeleton, target-proc, label-end, management of FSN, etc. are described in the JCL Translator section of the Oracle Tuxedo Application Runtime Workbench Reference Guide.

Listing 7‑3 JCL translator configuration file for STFILEORA simple application (config-trad-JCL.desc ):

% config.desc :

%

root-skeleton = "../trf-jcl/"

target-proc = "../trf-jcl/Master-Proc"

use-sort=mf-sort

%

var-dataroot = "${DATA}/"

var-tmp = "${TMP}/"

var-spool = "${SPOOL}/"

 

% Ksh heading

%

top-skeleton = "../param/top-ksh.txt"

 

% KSH footer

%

bottom-skeleton = "../param/bottom-ksh.txt"

 

% Files passed in tables

file-list-in-table = "../param/dynamic-config/File-in-table.txt"

 

% Suffix of translated ksh du ksh traduit

suffix-skeleton = "ksh"

 

% Management of FSN to keep

set-no-delete-fsn = SYSIN ( DSNUTILB ),

SORTIE ( ZIP390 ),

ENTREE ( ZIP390 ),

* ( DB2CMD,CSQUTIL ),

CFTIN ( CFTUTIL ),

SYSUT1 ( DUMMY ),

* ( ADRDSSU ).

 

% Management of FSN to delete

set-delete-fsn = SYSOUT ( IDCAMS ),

SYSEXEC ( CSCOLMVS ),

SYSTSIN ( * ),

SYSIN ( IDCAMS,XMFSORT,ICEMAN,SPOOL,SORT ),

SYSPUNCH ( * ),

TOOLIN ( * ),

SYSUDUMP ( * ),

SYSDBOUT ( * ),

SYSABOUT ( * ),

SYSTSPRT ( * ),

SORTLIB ( * ),

OPLIB ( * ),

STEPLIB ( * ),

JOBLIB ( * ).

 

Full example configuration

The general options root-skeleton, target-proc, label-end, etc. are described in the JCL Translator section of the Oracle Tuxedo Application Rehosting Workbench Reference Guide.

Listing 7‑4 JCL converter configuration file for Simple Application (config-trad-JCL.desc ):

%

% config.desc :

%

%

root-skeleton = "../trf-jcl/"

target-proc = "../trf-jcl/Master-Proc"

use-sort=mf-sort

%

%

var-dataroot = "${DATA}/"

var-tmp = "${TMP}/"

var-spool = "${SPOOL}/"

 

%

% Ksh heading

-------------------------------------------------------------------------

%

 

top-skeleton = "../param/top-ksh.txt"

 

% Ksh heading -------------------------------------------------------------------------

 

%

% KSH footer ------------------------------------------------------------------------

%

bottom-skeleton = "../param/bottom-ksh.txt"

%

% KSH footer --------------------------------------------------------------------------

 

%

% File passed in table

%

file-list-in-table = "../param/dynamic-config/File-in-table.txt"

 

% Suffix of translated ksh

suffix-skeleton = "ksh"

 

% Management of FSN to keep

set-no-delete-fsn = SYSIN ( DSNUTILB ),

OUTPUT ( ZIP390 ),

INPUT ( ZIP390 ),

* ( DB2CMD,CSQUTIL ),

CFTIN ( CFTUTIL ),

SYSUT1 ( DUMMY ),

* ( ADRDSSU ).

 

% Management of FSN to delete

set-delete-fsn = SYSOUT ( IDCAMS ),

SYSEXEC ( CSCOLMVS ),

SYSTSIN ( * ),

SYSIN ( IDCAMS,XMFSORT,ICEMAN,SPOOL,SORT ),

SYSPUNCH ( * ),

TOOLIN ( * ),

SYSUDUMP ( * ),

SYSDBOUT ( * ),

SYSABOUT ( * ),

SYSTSPRT ( * ),

SORTLIB ( * ),

OPLIB ( * ),

STEPLIB ( * ),

JOBLIB ( * ).

 

Translation steps

The Oracle Tuxedo Application Rehosting Workbench JCL Translator executes on a migration platform (Linux) and can automatically translate a single job file, a series of jobs files or the entire system content.

Set environment variables

Before executing the translator the following variables must be set:

Variable	Value	Usage
REFINEDIR	/product/art_wb11gR1/refine	the Rehosting Workbench product file structure.
PROJECT	$(HOME)/ simpleapp	Project location.
PARAM	$PROJECT/param	Location of configuration files.
SOURCE	$PROJECT/source	Location of source files.
LOGS	$PROJECT/Logs	Location of source files.

Translation commands

The following commands can be used to execute the translation. Logs file are generated in $LOGS/trad-jcl.

Command line to translate one JCL file

To create a Korn shell script with the same name as the input file except with a .ksh suffix.

Listing 7‑5 Single JCL translation script

cd $LOGS/trans-jcl

$REFINEDIR/refine jclz-unix -v version -s $PARAM/system.desc -c $PARAM/config-trad-JCL.desc JCL/defvcust.jcl

 

Command line to translate a list of JCL files

To translate a list of JCL files invoke following command:

Listing 7‑6 List of JCL translation script

cd $LOGS/trans-jcl

$REFINEDIR/refine jclz-unix -v version -s $PARAM/system.desc -c $PARAM/config-trad-JCL.desc -f jcl-files-list

 

Command line to translate all JCL files

To translate all JCL files invoke a command:

Listing 7‑7 All JCL translation script

cd $LOGS/trans-jcl

$REFINEDIR/refine jclz-unix -v version -s $PARAM/system.desc -c $PARAM/config-trad-JCL.desc

 

Checking results

To check conversion results, verify that:

•	All expected files are generated.

•	All corresponding ksh scripts are generated.

•	All procs and includes are extracted.

•	There are no empty scripts.

•	There are no truncated scripts.

Check the error messages; the JCL translator prints error messages encountered during the translation in the generated script. Check if any messages are present by searching for the following keywords: " UNDEFINED ", " NIL ", " UNTRANSLATED ". The complete list of error messages along with their explanation can be found in the Oracle Tuxedo Application Rehosting Workbench Reference Guide.

•	Control the procedures

•	Control the Batch RunTime functions.

•	Check that there are no unjustified warning messages.

Using a make file

The use of makefiles when using the Rehosting Workbench is recommended because it enables you to:

•	Document all (executable) processes

•	Effectively manage incremental operations and thereby save time.

•	Control and check the results of processes

A makefile should be placed in the source directory in which the operations are implemented at the initialization of a project.

Configuration

See Make configuration in the Cataloger user guide

JCL translation

To translate all the JCL in the $SOURCE file system

From the $SOURCE directory launch the command:

make trad_jcl

The JCLs are translated sequentially one by one.