Dear Visitor,

Access to our ACMU Online Demo is no longer not available.

Why don't you just contact us instead ?
and we will be happy to offer you a ACMU demo converting a sample of your JCLs to Shell scripts as well as showing your Cross-References !

• Free of charge
• JCL and PROC converted to UNIX/Linux Shell scripts
• Cross-Reference (see below screenshots) : See immediately how is structured your Legacy batch:
  • Application dependancies on JCL, Procedure, Programs, Datasets,
  • Counters: how many application and utility programs called by the JCLs
  • Application affinity: with DB2, Oracle, Natural, Java, USS, ...
  • How tricky are your JCL/Procs: in particular, IBM "Swiss Army Knife" IKJEFT01 utility
  • Legacy dataset names turned into a commonly used Filenaming convention for UNIX/Linux. On top of it, Client can give its Filenaming specifications.
• Real run on Linux (or AIX or Sun if you prefer!) of your Shell Script jobs, including dummy programs and datasets required for demo (We create dummy programs/dataset to allow running all steps of jobs). Most standard IBM utilities IKJEFT01, IDCAMS, IEBCOPY, IEBGENER, SORT, ... already ported to UNIX/Linux.
• under NDA if requested, or just send us anonymized JCLs by removing comments and changing all HLQ, as well as explicit instream statements (such as SQL)

ACMU Cross-References Screenshots

Doing Cross-Ref analysis of your +30-years old Legacy MVS, z/OS material show you figures you might not be aware of!

Following are sample outcomes of XRef produced from JCLs/PROCs you supply: it is a standalone flat -- macro free -- Excel spreadsheet, easy to read, manipulate, search, filter data.

Outcomes of XRef will dramatically help HH&S and client to appreciate feasibility, make a decision for target landscape, set priorities for porting applications and data, and plan project a very realistic way.

Index Sheet

This screenshot displays counts of JCL, PROC, distinct (unique) PGM. It gives an idea of requested effort for porting Legacy application and utility programs to target platform: Whatever the number of JCLs is, what is most important is number and nature of distinct programs / procedures / utilities.

(Invalid JCL means non-JCL files featuring my mystake in Joblibs, such as ASM, REXX, CLIST, Cobol, ...)

JCL/EXEC XRef Sheet

This screenshot shows usage of Application and utility pograms,Procedures among all JCLs of all applications.
It answers these questions:

• Which application/JCL is using this program ?
• Which programs are needed to migrate this application ?

Furthermore, we can see that different applications, in this example CUSTOMER and FINANCIAL, share common programs and technologies, such as DB2 (DSN*), MQSeries (EQQ*), ...

JCL - IKJEFT01 Sheet

With IBM "Swiss Army Knife" IKJEFT01 you can do a lot of things!
The question is:

• What are your IKJEFT01 jobs doing ?
• How tricky will it be to migrate to Unix/Linux?

Our XRef sheet gives meaningfull tags to IKJEFT01 operations:

• DB2, TSO command, ISPSTART command: can be tricky, needs some analysis
• REXX procedures: needs some analysis to decide for REXX porting vs rewriting
• BPXBATCH, OMVS commands: easy

From this outcome of XRef, we will focus on tricky points to give a pretty good estimate of feasibility and workload that will be required on HH&S as well as on client side.

XRef Datasets

How sweet it is to view at glance your Legacy Batch Datasets !

• Ordered by Application, JCL, Step, and DDNAME.
• Original Dataset Name, Disposition, RECFM (Fixed/Variable)
• High Level Qualifier
• Proposed Target filenaming for Unix/Linux. Obviously, filenaming convention is decided by Client, and will be customized in ACMU.
• Easy to sort / search / filter, draw your new filenaming convention.

Program/Utility Count Sheet

This screenshot shows number of programs, procs calls among all JCLs, per application, and total.

We can see at glance which technologies are used by applications.
Mainframe eyes can see in this example HR is sole user of Oracle (SQLPLUS,SQLLoader), CUSTOMER, PURCHASE and SALES applications are using DB2 (DSNUTIL, DSNUPROC), all applications are using MQSeries (EQQ*).

Once XRef is done, HH&S team will identify which program/utility is complex/tricky to port.
In such case, XRef will help making a decision: Remove / Replace / Rewrite.

For instance, for an ISPSTART command, we will look at it and tell if it makes sense to port to UNIX/Linux.

Typical cases:

Legacy	Decision	Target
ADRDSSU backup	Replace utility	Your UNIX/Linux favorite backup tool: tar, zip, ... We'll write a custom ACMU Userexit that will replace "on the fly" ADRDSSU pattern by your target pattern
REXX proc	Rewrite proc	Your UNIX/Linux favorite language: Shell, Perl, Python, ...
BPXBATCH Shell commands	Remove utility	BPXBATCH only usefull on z/OS: Shell commands will run naturaly on UNIX/Linux

Missing Material Sheet

Not sure you have supplied all Legacy items ?
Don't worry! Our Missing Material Sheet will point out missing files!