MVSJCL.doc - Converting MVS JCL to Unix/Linux scripts - Contents

MVS JCL Documentation - Contents

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

MVSJCL.doc - Converting MVS JCL to Unix/Linux scripts - Contents

MVSJCL2.doc

 MVSJCL2.htm#Part_26 - Special conversions for SORT/SYNCSORT, FTP, etc
         - Manual Changes Required for SORT/SyncSort
         - uvsort has all the powerful capabilities of SyncSort, but some
           of the more complex conversions may require manual correction.
         - Alternate solutions for SORTs with too many OMIT/INCLUDEs
         - Merging SyncSort converted parameters into VU JCL/scripts
         - FTP conversion examples

 MVSJCL2.htm#Part_27 - Scanning for Problems & Mass-Change Fix-ups
         - grep, sed, uvcopy scan1d, scan2d, rep1d, rep2d, etc

 MVSJCL2.htm#Part_28 - Special Considerations, Problems & Solutions
         - CONDition tests
         - Run a JCL/script when an input file is detected (ftrigger51)
         - detect FTP'd files & move/rename to a 2nd subdir to prevent overwrite
         - Convert mainframe JCL containing Cybermatics ESP scheduler coding
         - Process scripts converted from mainframe JCL containing BMC Control-M
           to allow testing on unix before unix version of control-M installed.

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

MVSJCL.doc - Converting MVS JCL to Unix/Linux scripts - Contents

Mainframe Conversion Documentation Summary

Here is a brief review of the documentation relevant to mainframe conversions & accessible on the UV Software web site (www.uvsoftware.ca).

 MvsJclPerl.htm - MVS JCL Conversion to Perl scripts     <--- Alternate

Copyright UV Software Inc. 1993-2012

Owen Townsend, UV Software, 4667 Hoskins Rd., North Vancouver BC, V7K2R3

 Tel: 604-980-5434 Fax: 604-980-5404

mailto:owen@uvsoftware.ca

http://www.uvsoftware.ca

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

Part_0 MVS JCL Conversion - Major Features

MVSJCL.doc is the detailed step by step instructions for converting IBM MVS JCL to Unix/Linux, using the Vancouver Utilities from UV Software Inc.

MVS JCL Conversion - Major Features

1. MVS JCL is automatically converted to Korn shell scripts to run on Unix, Linux, or Windows with SFU (Services for Unix). Mainframe file assignments for COBOL programs are converted to export the external name for Micro Focus COBOL. Mainframe DATA and SORT utilities are converted to the Vancouver Utility Unix/Linux equivalent (uvcp or uvsort). Note that the Unix/Linux/Windows system sort cannot be used for mainframe file types since it does not support fixed record lengths with no linefeeds.
   
   
2. Converting the JCL to Korn shell scripts provides much more flexibility for future enhancements than the 'emulations' offered by some other conversion alternatives. Korn shell scripts allow you to use the full power of your unix/linux system. Korn shell scripts allow you to integrate other software desired, such as schedulers.
   
   
3. JCL Converted scripts simplified. The JCL conversion has been designed to make the resulting Unix/Linux scripts as easy as possible to read, to debug, and to maintain in future. Steps are sequence numbered & step separator lines are inserted.
   
   
4. The JCL converter inserts code to allow 'step restart' at any desired step. For example to restart the 'jar200' job at step2 the command line would be --> jar200.ksh STEP=S0020 (4 digit step#s incremented by 10).
   
   
5. The JCL converter uses the 'logmsg1' function to ensure that all console messages are prefixed with date:time:jobid on the left side. Important messages such as 'Terminated Abnormally' are shown in reverse video & an acknowledgment is requested.
   
   
6. The 'jobstop' script is provided to allow operators to pause jobs at the next step or at any desired step. 'jobstop' writes a control file that is tested by the 'stepctl' function which is inserted at the begining of each step by the JCL converter.
   
   
7. The JCL conversion performs a 1 time expansion of PROC's before converting the JCL to Korn shell scripts. The JCL converter will replace mainframe '&variables' with their default values. We have found many mainframe jobs with dozens or hundreds of &variables (now $symbols in Korn shell scripts) that were in fact never used. Many of these were mainframe related (VSN's,cylinders,etc) with no applicability to Unix/Linux. Removing these means we have to re-insert the few that are in fact used, but removing the vast majority greatly simplifies debugging and future maintenance. Under MVS, variables could exist only in the PROCS, but under Unix/Linux we can have many $SYMBOLS in the Korn shell scripts.
   

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

0A2. MVS JCL Conversion to Korn shell scripts - Major Features

11. Cross-References of JCL/scripts & COBOL programs/copybooks. XREFjobs.htm documents a complete plan to provide: Inventory control lists of all filenames & line counts, Content listing of JCL/scripts before & after conversion, Copybook layout maps, COBOL File info reports,& JCL Job-Flow reports. These listings should be run after you have transferred & converted the JCL & COBOL programs, but before you begin testing & debugging. House these reports in 3-ring binders with index tabs for easy access during testing & debugging.
    
    
12. Job-Flow reports extract File Info from both JCLs & COBOL programs. One line is printed for each datafile in each step. From the JCL we show: Step#, Program-name, DDname,& DSNname. From the matching COBOL program, we show: file Organization, Access-mode, Open-mode(I/O/E), Record-size,& Copybook-name. These reports are your essential guide to testing & debugging.
    
    
13. Unix functions have been written to provide the essential functionality of the IBM cataloged generation files. Please see exportgen0 & exportgen1 which are discussed & listed in 'Part_5'.
    
    
14. Directory Design. A lot of time and effort was invested to ensure the directory design would accommodate multiple separate systems, but allowing for interconnections. Program libraries and data are in separate file systems, which are each subdivided by the various applications. The design allows for 4 or 5 levels of sub-directories before files are assigned. This gives us more flexibility & better file protection. See ADMjobs.htm for a discussion of RAID & file system design.
    
    
15. Separate logins for each system facilitates console logging. Operators can use multiple screens on 1 terminal and each screen displays only the jobs running for one system. This avoids confusion and allows us to collect console logs separately by system.
    
    
16. Environmental variables RUNDATA & RUNLIBS allow programmers to operate on test data & test libraries while production personnel operate on production data & production libraries. RUNLIBS is defined in the profiles to control the PATH to JCL/scripts. All converted JCL/scripts call a common function (jobset51) which performs a 'change directory' to $RUNDATA at the beginning of the script. All file accesses are then relative to $RUNDATA which is either test data or production data depending on the user profile. This facility is vital if production & development are on the same machine, but still useful for separate machines. For example, different programmers can use different sets of data files &/or libraries.
    
    
17. Protection from running the wrong JCL/script. Since operators login to the system to be run, they cannot accidentally run jobs belonging to other systems, because their profile PATH would search only the libraries for the intended system.
    
    
18. No problem if COBOL programs named the same as JCL/scripts. Because the COBOL program library is not in the PATH, but rather is defined in the 'jobset51' function which is inserted by the JCL converter at the beginning of each JCL/script.
    

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

0A3. MVS JCL Conversion to Korn shell scripts - Major Features

16. Programmers may turn on debugging (animation) for COBOL simply by exporting a runtime variable (ANIM=+A for COBOL, UVCOPYROP=d for uvcopy), no need to modify JCL or recompile programs with debug options.
    
    
17. Console Logging. This is a VITAL feature to replace the console logging systems provided by proprietary mainframe systems. Console Logging uses the Unix/Linux 'script' command inserted at the end of the profile to create a date/time stamped console log file which captures all console I/O until the operator logs off. Console log files must be processed (to remove screen control codes) before being viewed or printed & this is accomplished automatically when the user logs off & back on. He may then use the logview script to view or print the latest (or earlier) log file. See the sample console log created when the conversion test/demo jobs are executed later beginning on page '1S3'. Or see console logging in ADMjobs.htm. Note that you must uncomment the last 6 lines of the profile to activate console logging. See the profile listed at ADMjobs.htm#1C1. You must also setup a subdir in /home/appsadm/log1,2,3 matching userid. Console logging should be mandatory for operators, but can be optional for programmers (highly recommended for testing).
    
    
18. 'uvsort' (A Vancouver Utility program) replaces mainframe SORT & SYNCSORT. Mainframe sorts must be converted to 'uvsort', because the Unix/Linux sort can not be used for mainframe type data files. The major problem is that the unix/linux system sort cannot sort files without LineFeeds. Mainframe files are usually fixed length records without line feeds. uvsort can also read & create indexed files which is not possible with the unix/linux system sort. uvsort includes SYNCSORT features such as record INCLUDE/OMIT, record reformatting INREC/OUTREC, etc. See the many examples given in MVSJCL2.htm#Part_6.
    
    
19. IDCAMS replacement. IDCAMS 'REPRO' (file copy) is converted to the Vancouver Utility 'uvcp'. Most of the other IDCAMS functions are not required for MicroFocus COBOL on Unix/Linux/Windows systems. For example 'DEFINE CLUSTER' was required by the mainframe to create a VSAM file, but MicroFocus COBOL can create VSAM files simply by 'OPEN OUTPUT'.
    

However the IDCAMS DEFINE CLUSTER is converted to 'uvcp' which will create an empty file, in case the IDCAMS step is followed by a COBOL program that expects to ADD/UPDATE records to an empty existing file. The uvcp will create the file with any indexed keys specified.

20. Replacements for mainframe Ditto, File-Aid, Easytrieve, QuikJob, DYL280, etc. The uvcopy & uvqrpg utilities can supply more functionality than many of these mainframe utilities.
    

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

0A4. MVS JCL Conversion to Korn shell scripts - Major Features

21. Tape Files. Jobs using tape files will need to be examined. COBOL programs can not read/write tape files on Unix/Linux systems.
    

Tape files will be redirected to a disc subdirectory to reduce the extensive tape handling that was common on mainframes. If the copy to tape was simply a backup it may be unnecessary on unix due to superior backup frequency (every night automatically scheduled by 'cron').

The disc file (tape equivalent) is date/time stamped in case of multiple runs between the backup cycles. You should remove the date/time stamp if not required - if it should always be the latest version & there is no need for prior versions. You should also remove the date/time stamp if the tape file was re-input on a subsequent job & make sure the filenames match.

You may still need tape files for data transfer with outside agencies. Unix/Linux systems do not natively support IBM standard labelled tapes but the Vancouver Utilities do include jobs (t9copy2, t9write1, etc) to read and write IBM/EBCDIC standard labeled tapes.

22. Print Spooling for SYSOUT type files. The first job of the day creates a new subdirectory for all SYSOUT files created that day. For example /p2/proddata/sysout/030930 would hold reports for the act system created on September 30/2003. The sysout subdirectories are accumulated, but purged automatically by the nightly 'cron' job after 20 days (easily modified). Many SYSOUT files do not need to be automatically printed. It may be more convenient for programmers to view the report files with the editor and to print selectively.
    
    
23. COBOL programs usually write important reports to disc files with assigned DSN names (not SYSOUT's). You could use a unix/linux spooling package (such as Easy Spooler) to spool & print these files. It is a simple matter to insert the spooling commands into the scripts at the appropriate points (after COBOL programs have created the disc files).
    
    
24. The Vancouver Utilities provides several laser printing scripts that may be used to print the reports. Several customers have used these scripts for standard reports and use Easy Spooler for special forms. The laser printing scripts allow mainframe reports to be printed Landscape on 8 1/2 by 11 inch standard copy paper (preferably 3 hole punched). Several scripts are provided (see details in uvlist.htm.
    

     uvlpLS13 - prints Landscape Simplex at 13 cpi to fit 132 cols on 11" wide
              - prints at 8.1 lpi to fit 60 lines in 8 1/2 deep

uvlpLD13 - prints Landscape Duplex

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

0A5. MVS JCL Conversion to Korn shell scripts - Major Features

25. We suggest you setup an 'applications administrator account' (appsadm). to handle administrative duties (common to various applications), such as console logging & backups. /home/appsadm contains the following subdirectories: a. log1/log2/log3 - console logs subdirs for today, this month, last month. b. sf (script files) - common to applications (backups, crontabs, etc) c. pf (uvcopy jobs) - common to applications d. logs - logs of nightly backups (run automatically by cron) - cpio stdout stores lists of files backed up - stderr appends to nightly log to collect history of backups & any error messages (should be reviewed periodically).
    
    
26. Backups can be scheduled by 'cron' (unix/linux job scheduler). The backups are controlled by a 'crontab' file belonging to the 'appsadm' account. Crontab files can be customized for the various systems (accounting, manufacturing, etc).
    
    
27. The Vancouver Utilities includes sample backup scripts such as /home/uvadm/sf/adm/nightly1. These scripts use cpio to stack multiple archives on DAT tape for the various systems. Multiple archives allow you to easily restore a desired system & retrieve desired files. Note that the Directory Design facilitates backup/restores by logical groups. You can backup production data & production libraries separately from test data & test libraries.
    
    
28. Some customers use on-disc backups for the data before & after nightly batch jobs. The operator runs the before backups as the 1st step of the nightly batch, and the after backups are run automatically by cron at 3 AM (for all systems). Nightly on-disc backups are also made for the libraries which allow instant recovery from accidental erasures.
    
    
29. Mainframe GDG (Generation) files are implemented via unix/linux Korn shell functions (exportgen0, exportgen1,& exportgenall). 'exportgen0' defines the current (highest gen#) of the file & 'exportgen1' defines the next (not yet existing gen#).
    

GDG files in MVS JCL are recognized by the suffixes (0), (+1), (-1).In the ksh scripts, the (0),(+1),(-1) is indicated by functions exportgen0/1 and a filename will be suffixed with an '_' underscore. The converted data files will be suffixed by '_######' (underscore & 6 digit gen#). Please see Part_5 for further discussion.

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

0A6. MVS JCL Conversion

more than conversion tools

UV Software has the complete solution to batch conversions of JCL, COBOL,& DATA. The Vancouver Utility package supplies several additional items essential to the successful conversion & ongoing operation on Unix/Linux systems:

1. Profiles define RUNLIBS & RUNDATA to allow multiple sets of test or production libraries & data on the same machine. See profiles listed & described at www.uvsoftware.ca/admjobs.htm#1B1
   
   
2. Directory Design. It is essential to have a well thought out directory design within your RAID file systems. See TESTLIBS, TESTDATA, PROLIBS, PRODDATA designs starting at ADMjobs.htm#2C0 or MVSJCL.htm#4C1. Environmental variables RUNLIBS/RUNDATA are set to TESTLIBS/TESTDATA or PRODLIBS/PRODDATA in the profiles of programmers & operators, so you never have to change any JCL/scripts for use by programmers & operators. This also allows programmers to hve different sets of libraries & data.
   
   
3. Backup systems described at www.uvsoftware.ca/admjobs.htm#Part_4 As well as backups to tape, this system takes advantage of the massive inexpensive disc systems now available to maintain date stamped zip file backups on-disc for the last 40 days, the last 15 end of month backups,& the last 7 end of year backups. Backups on disc are immediately available.
   
   
4. Using cron to schedule nightly jobs, backups, etc See www.uvsoftware.ca/admjobs.htm#Part_5
   
   
5. Console logging described at www.uvsoftware.ca/admjobs.htm#Part_6. Mainframes include a console logging system, but unix/linux systems do not. UV Software has developed a console logging system for unix/linux.
   
   
6. Utilities to replace mainframe utilities for data file maintenance (SORT, IDCAMS, IEBGENER, DITTO, FILEAID, EasyTrieve, etc). Note that uvcopy, uvsort, uvcp can process mainframe indexed files with packed decimal fields, etc (normal unix utilities can not).
   
   
7. The 'uvcopy' utilities are an essential part of the mainframe conversions because they can do many things not possible with the standard unix/linux utilities (such as processing packed decimal fields & handling Indexed files compatible with Micro Focus COBOL).
   
   
8. uvcopy is a general purpose data manipulation utility which can be used to reformat files, modify records, and perform almost any imaginable data data conversion & translation that may be required or desired. It is especially useful when transferring files to new machines or converting record layouts to fit the requirements of new application packages.
   

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

0A7. MVS JCL Conversion

Test/Demo files provided

Test/Demo JCL, PROCs, COBOL programs,& DATA files are provided, for you to run the conversion procedures & verify you results match the results listed in this documentation.

The Test/Demo conversion sessions will give you a clear understanding of these conversion procedures & make it easier for you to get started on your own conversions. If you are reading this on the web site (www.uvsoftware.ca), the test/demo documentation will make it easier for you to understand these conversion concepts.

If you have not yet purchased the Vancouver Utilities conversion package, UV Software invites you to send samples of your JCL for conversion & return by email attachments. Please be sure to include all referenced PROCs and any library members containing SORT keys, etc.

Running Conversion Test/Demos

You can run the test/demos without the extensive planning & file system setup recommended for your own conversions. After installing the Vancouver Utilities, the test/demo subdirs & files will be found in directory 'mvstest' (/home/uvadm/mvstest if installed as recommended).

We recommend you do not run the test/demos in /home/uvadm/mvstest, since any updated installation of Vancouver Utilities would wipe this out. So we advise you to setup a new user 'mvstest' (/home/mvstest), and setup the profile for mvstest as described in install.htm or ADMjobs.htm. Then copy the test/demo subdirs & files from /home/uvadm/mvstest/* to /home/mvstest/...

You could copy the 'mvstest' directory to a subdir within your home directory, if you modify your profile as described in install.htm or ADMjobs.htm. If you don't want to do that yet, setup user 'mvstest' for initial testing. When you decide to proceed with your own conversions, you can then modify your profile & the profiles of all programmers & operators involved.

Compile 'C' programs if not Linux

The Vancouver Utilities are distributed with the 'C' utility programs already compiled (into /home/uvadm/bin) using Red Hat 9.0. If you are running Linux, you should not have to recompile. If you are running Unix, please see install.htm for the compile instructions for the various flavors of Unix. If you are running on Windows with SFU (Services For Unix), please see WindowsSFU.htm for compile instructions.

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

0A8. MVS JCL Conversion

Korn shell 1993 version recommended

The converted scripts are designed for the Korn Shell (ksh) and I recommend the 1993 version, which can be downloaded from http://www.kornshell.com.

Vancouver Utilities for Windows 95,98,NT,2000,XP

 The Vancouver Utilities & the conversion tools & scripts may now be run on
 Windows systems, using SFU, UWIN, or CYGWIN (unix emulators for windows).
 You can download SFU from http://www.microsoft.com/windows/sfu,
 UWIN from http://www.wipro.com/uwin,
 and CYGWIN from http://www.cygwin.com.

There is also a low cost version of Vancouver Utilities for native windows, but that package does not include the conversion tools since the conversions depend on many unix style scripts that can only be run on windows with the aid of an emulator such as SFU, UWIN, CYGWIN, or KMS Tools.

Please see WindowsSFU.htm for important notes on installing SFU & VU. Please see CygwinUwin.htm for important notes on installing UWIN & CYGWIN for the Vancouver Utilities.

The various JCL & COBOL conversions illustrated in this documentation have been tested on SFU, UWIN, & CYGWIN as well as on Unix & Linux. Notes are made where there is any difference.

SFU/UWIN/CYGWIN differences to Unix/Linux

COBOL compile scripts are different since the MicroFocus COBOL compiler is different (Server Express for Unix/Linux vs Net Express for Windows). The script to compile 1 program at a time is 'mfcbl1' for unix/linux, and 'mfnxcbl1' for SFU/UWIN/CYGWIN (see listings at MVSCOBOL.htm#5E0). To compile all programs in a directory the scripts are 'mfcblA' & 'mfnxcblA'.

JCL/scripts use functions (exportgen0 & exportgen1) to simulate mainframe generation files. Until June 2004, these complex functions required the 1993 version of the Korn shell & would not work under 'bash' (default shell for CYGWIN) or under 'pdksh' (public domain ksh), which is supplied with CYGWIN and UWIN (and aliased as 'ksh'). In June 2004, the exportgen functions were modified & tested for SFU (probably also OK for CYGWIN).

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

Part_1. MVS JCL Conversion to Korn shell scripts

Before you attempt to convert your own JCL, we recommend you perform the demo conversions illustrated in Part 1, using the supplied test JCLs & data files.

Part_1 will help you understand these tools & ensure they work at your site, but be sure to use Part_4 to convert your own JCL vs the test/demos in Part 1.

Part 1 Contents

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

Part 1 MVS JCL Conversion to Korn shell scripts

Part 1 Contents - continued

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

1A1. Directory Design for JCL Conversion

Directory-Design for UV test/demo JCL Conversion

 /home/mvstest         <-- setup user 'mvstest' & copy subdirs from uvadm/mvstest
 :-----testlibs
 :     :------Csub        - C subroutines for COBOL programs
 :     :--MF--cbl0        - COBOL programs ('*' means files present)
 :     :------cbl1        - cleaned up, cols 1-6 & 73-80 cleared, etc
 :     :------cbl2        - cnvMF5 converts mainframe COBOL to MicroFocus COBOL
 :     :------cbl3        - sysin1 converts instream ACCEPTs to READs from a file
 :     :------cbl4        - sysout1 converts DISPLAY on SYSOUT to WRITE to a file
 :     :---ux-cbls        - copy here (standard source library) before compiling
 :     :------cblst       - cobol source listings from compiles
 :     :------cblx        - compiled COBOL programs (.int's)
 :     :--MF--parm0       - control cards & includes (SORT FIELDS, etc)
 :     :------parms       - control cards with 73-80 cleared
 :     :--MF--cpy0        - for COBOL copybooks
 :     :------cpy1        - cleaned up, cols 1-6 & 73-80 cleared, etc
 :     :------cpy2        - cnvMF5 converts mainframe COBOL to MicroFocus COBOL
 :     :---ux-cpys        - copy here (standard copybook library)
 :     :--UV--ctl         - conversion control files (jclunixop5,datactl53I,etc)
 :     :------errs        - JCL converter writes ERROR reports here
 :     :--MF--jcl0        - test/demo JCLs supplied
 :     :------jcl1        - intermediate conversion 73-80 cleared
 :     :------jcl2        - PROCs expanded from procs
 :     :------jcl3        - JCLs converted to Korn shell scripts
 :     :---ux-jcls        - copy here manually 1 by 1 during test/debug
 :     :------maps        - 'cobmaps' record layouts generated from copybooks
 :     :------pf          - uvcopy jobs to replace utilities (easytrieve,etc)
 :     :--MF--proc0       - test/demo PROCs supplied
 :     :------procs       - will be merged with jcl1, output to jcl2
 :     :------sf          - for misc scripts you may wish to write
 :     :------tmp               - tmp subdir used by various conversions
 :     :------xref              - cross-references (see XREFjobs.htm)

 :-----testdata          - test/demo data files supplied
 :     :--MF--ap          - Accounts Payable
 :     :--MF--ar          - Accounts Receivable
 :     :--MF--gl          - General Ledger
 :     :--UV--ctl         - GDG control file
 :     :------jobtmp      - temporary files for SYSIN instream data
 :     :      :----030926 - jobtmp subdir created in jobset51 (script line 10)
 :     :------sysout      - SYSOUT printer files
 :     :------tmp         - tmp subdir for uvsort & misc use
 :     :------wrk         - interstep temporary work files

        --MF--  marks subdirs containing MainFrame files for conversion
                (COBOL programs, copybooks, parms, PROCs,& data)

        --UV--  marks control files supplied by UV Software

        ---ux-  marks the most important outputs of the conversion
                most other subdirs can go away after the conversion is complete

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

1A2. Directory Design for JCL Conversion

Notes re: JCL/PROC test/demo subdirs provided

The sub directories illustrated on the previous page are included on the Vancouver Utility distribution media and after installation will be contained within /home/uvadm/mvstest (1 of about 20 directories in the package).

You will later be instructed to setup a test/demo userid/login 'mvstest' and copy the subdirs from /home/uvadm/mvstest to /home/mvstest. Please do not run tests within /home/uvadm because new distributions of Vancouver Utilities would destroy your test results.

The following pages will list several test/demo JCLs & PROCs provided and their converted equivalents (Korn shell scripts). Studying these examples will give you a good understanding of the JCL conversion process.

If you have just installed the package, you can run the conversion procedures (starting on page '1P1') and verify that you get the same results listed here. If you have not yet purchased the package, you are invited to send samples of your JCL & PROCs to UV Software for conversion & return.

Note that the directory design listed here is for test/demo convenience only. The recommended directory design for your own testing & production is illustrated later begining on page '4C2'. The big difference is that you should assign your data directories to a separate file system from the libraries.

setup required to run test/demo jobs

See the detailed operating instructions on page '1P1' ahead. These instructions review everything required (loading Vancouver Utilities, setting up users, etc).

setup required to convert your own JCL,COBOL,DATA

Please see Part_4 when you think you are ready to start converting your own JCL, COBOL,& DATA files. But be first run these test/demos in Part 1 (with supplied demo files) before you attempt to perform your own conversions.

setup for quick conversion of a few of your JCLs

See page '1X1' if you need to do a quick preliminary conversion of a few of your JCLs before you invest the time & effort that should be expended when you launch your mainframe conversion project.

Page '1X2' shows you how to use script 'mvslibsdirs' to create the (empty) sub-dirs (shown on the previous page). You could create a directory within your homedir (call it testlibs) to contain the subdirs required for conversion.

Page '1X2' also shows you script 'jcl2ksh51A' to perform all steps of JCL conversion, BUT we recommend you first use the step by step method (starting on page '1P1') to better understand the process.

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

1A3. Directory Design for JCL Conversion

RUNLIBS/RUNDATA & profiles

The Library & Data directories used by the converted JCL/scripts is determined by environmental variables 'RUNLIBS' & 'RUNDATA' defined in user profiles. See recommended profiles for these test/demos listed at ADMjobs.htm#1C1.

$RUNLIBS is used in the PATH to define where the JCL/scripts are to be found.

$RUNDATA is used in the jobset51 function called at the beginning of each script to perform a change directory to the data files super directory.

All data files are addressed relative to RUNDATA, which allows us to easily switch between test data & production data simply by changing the value of RUNDATA. This is done most reliably by providing different profiles to the programmers & the production personnel.

The stub_profile is copied/renamed as .profile for ksh & .bash_profile for bash. The stub_profile listed ADMjobs.htm#1C1 defines RUNLIBS & RUNDATA as follows:

 export RUNLIBS=$HOME/testlibs
 #============================
 export RUNDATA=$HOME/testdata
 #============================

If you setup separate user 'mvstest' for these tests, the expansions would be:

 export RUNLIBS=/home/mvstest/testlibs
 #====================================
 export RUNDATA=/home/mvstest/testdata
 #====================================

Alternatively, you could create a 'mvstest' subdir within your current HOME dir, in which case you would modify the exports as follows:

 export RUNLIBS=/home/userxx/testlibs
 #===================================
 export RUNDATA=/home/userxx/testdata
 #===================================

Note that setting up RUNLIBS & RUNDATA in a HOME dir is a convenience to get you started testing quickly. You would NOT do this for serious testing & definitely not for production.

See the recommendations for your serious testing & production described later on pages '4C2' thru '4C10'

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

1B1. Sample Conversions of MVS JCL to Korn shell scripts

test/demo JCL PROCs,& COBOL

We will illustrate the original mainframe JCL & the converted Korn shell script equivalents for several test/demo JCLs. Then we present the Operating Instructions to Convert, Execute,& Check the results.

We will illustrate the conversion (before & after) of the following JCLs:

JAR100 & JAR200 are as simple as possible - no PROCs, no &SYMBOLS, no Generation (GDG) files, no instream data,& no control card members.

JGL100 & JGL200 are more typical of MVS JCL - including PROCs, &SYMBOLS, Generation (GDG) files, instream data,& control card members.

Our test/demo mainframe JCLs, PROCs, COBOL programs,& control card members are supplied in the 'mvstest' sub-directories illustrated on page '1A1'.

By convention, we have given these UPPER case names to reinforce their mainframe origins. The cleanup, PROC expansion,& conversion procedures will convert the UPPER case names to lower case names & append a .extension ('.jcl' for JCL, '.proc' for PROCs, '.ksh' for converted scripts,& '.cbl' for COBOL programs).

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

1B2. Sample Conversions of MVS JCL to Korn shell scripts

test/demo DATA files

The test/demo JCLs reference the following data files:

1. AR.CUSTOMER.MASTER
2. AR.SALES.ITEMS
3. GL.ACCOUNT.MASTER
4. GL.ACCOUNT.TRANS
   

The JCL conversion will assume the 1st node (High Level Qualifier or HLQ) is to be a sub-directory containing data files (named from the remaining nodes). Filenames with only 1 node will be assigned to $DW or 'wrk'. See TOPDIRDEFAULT in the conversion control file listed later on page '3E1'.

We have supplied the test data files in /home/uvadm/mvstest/testdata. Later on page '1P1', you will be instructed to setup userid 'mvstest' & copy the testdata files to the following structure.

 /home/mvstest/
 :-----testdata/
 :     :-----ar/
 :     :     :--customer.master
 :     :     :--sales.items
 :     :-----gl/
 :     :     :--account.master
 :     :     :--account.trans
 :     :-----py/
 :     :     :--payroll.master
 :     :     :--time.cards

Our test/demo data files have already been converted from EBCDIC to ASCII, preserving packed fields & correcting zoned signed fields to MicroFocus COBOL standards. You can see the details of the data conversions in DATAcnv1.htm & MVSDATA.htm.

By our conventions, all converted filenames are in lower case. This eliminates a lot of confusion on Unix/Linux systems where filenames are case sensetive.

We will later (after converting JCL & compiling COBOL programs) be using these test data files to execute our converted JCLs & COBOL programs.

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

1C1. Sample Conversion of MVS JCL to Unix/Linux Korn Shell Script

Note that we will present the detailed operating instructions later on starting on page '1Q1'. First we will illustrate some sample JCL/script before/after to ensure you understand the desired conversions.

First we will present the simplest possible JCL conversion (no PROC's, no GDG files, no control card members).

The 1st procedure is to remove any obsolete sequence numbers from the right side of JCLs & PROCs, change filenames to lower case,& append extension to identify the files (.jcl).

jcl0/JAR100 - original Mainframe JCL

 //JAR100   JOB  'TEST MVS2UNIX CONVERSION',DATE=20080323                00000010
 //* CUSTOMER NAME & ADDRESS LIST (WITH DATE & RPT HDNGS)                00000020
 //STEP010  EXEC PGM=CAR100,PARM=2008                                    00000030
 //CUSTMAS  DD DSN=AR.CUSTOMER.MASTER,DISP=SHR                           00000040
 //NALIST   DD DSN=AR.CUSTOMER.NAMEADRS.LIST100,DISP=(,CATLG,DELETE),    00000050
 //            UNIT=DISK,SPACE=(TRK,(25,25),RLSE),                       00000060
 //            DCB=(MODEL.DSCB,LRECL=133,BLKSIZE=6118,RECFM=FBA)         00000070
 //SYSOUT   DD SYSOUT=*                                                  00000080

jcl1/jar100.jcl - after cleanup

 j#001 //JAR100   JOB  'TEST MVS2UNIX CONVERSION',DATE=20080323
 j#002 //* CUSTOMER NAME & ADDRESS LIST (WITH DATE & RPT HDNGS)
 j#003 //STEP010  EXEC PGM=CAR100,PARM=2008
 j#004 //CUSTMAS  DD DSN=AR.CUSTOMER.MASTER,DISP=SHR
 j#005 //NALIST   DD DSN=AR.CUSTOMER.NAMEADRS.LIST100,DISP=(,CATLG,DELETE),
 j#006 //            UNIT=DISK,SPACE=(TRK,(25,25),RLSE),
 j#007 //            DCB=(MODEL.DSCB,LRECL=133,BLKSIZE=6118,RECFM=FBA)
 j#008 //SYSOUT   DD SYSOUT=*

The 'cleanup' job removes any sequence#s from the right side. We have re-inserted a sequence# on the left side only to facilitate references. We will prefix JCL sequence#s with 'j#' and the Korn shell script sequence#s with 'k#'.

Any 'PROC's are expanded & any 'INCLUDE's are included by the 'jclproc51' utility as it copies from subdir 'jcl1' to subdir 'jcl2'. Our first sample JCL has no 'PROC's or 'INCLUDE's so it will be copied unchanged.

The next step is the actual JCL conversion to Korn shell script. Please see the results listed on the next page --->

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

1C2. jcl3/jar100.ksh - JCL after conversion

 k#001 #!/bin/ksh
 k#002 ##JAR100   JOB  'TEST MVS2UNIX CONVERSION',DATE=20080323
 k#003 export JOBID2=JAR100 jobid2=jar100; scriptpath="$0"; args="$*"
 k#004 if [[ -z "$JOBID1" ]]; then export JOBID1=$JOBID2; fi
 k#005 for arg in $args; do if [[ "$arg" == *=* ]]; then export $arg; fi; done
 k#006 integer JCC=0 SCC=0 LCC=0  # init step status return codes
 k#007 autoload jobset51 jobset52 jobend51 jobabend51 logmsg1 logmsg2 stepctl51
 k#008 autoload exportfile exportgen0 exportgen1 exportgenall exportgenx
 k#009 . $APPSADM/env/stub.ini  #<-- for control-M (see notes in env/stub.ini)
 k#010 jobset51  # call function for JCL/script initialization
 k#011 goto
 k#012 S0000=A
 k#013 # * CUSTOMER NAME & ADDRESS LIST (WITH DATE & RPT HDNGS)
 k#014 #1======================= begin step#S0010 CAR100 ========================
 k#015 S0010=A
 k#016 stepctl51;  #calc StepTimes & check jobstop/goto end
 k#017 goto
 k#018 export JSTEP=S0010; ((XSTEP+=1)); SCC=0; LCC=0; alias goto="";
 k#019 logmsg2 "******** Begin Step $JSTEP car100 (#$XSTEP) ********"
 k#020 ##STEP010  EXEC PGM=CAR100,PARM=2008
 k#021 export PROGID=car100
 k#022 export PARM="2008"
 k#023 exportfile  CUSTMAS data/ar.customer.master
 k#024 exportfile  NALIST data/ar.customer.nameadrs.list100
 k#025 exportfile SYSOUT $SYOT/${JOBID2}_${JSTEP}_SYSOUT
 k#026 logmsg2 "Executing--> cobrun $ANIM $RLX/car100"
 k#027 #3----------------------------------------------------------------------
 k#028 cobrun $ANIM $RLX/car100
 k#029 #4----------------------------------------------------------------------
 k#030 LCC=$?; S0010C=$LCC; ((SCC+=LCC)); ((JCC+=LCC)); S0010R=1; alias goto="";
 k#031 if ((S0010C != 0))
 k#032    then logmsg2 "ERR: step#$JSTEP car100 abterm $SCC"
 k#033    alias goto="<<S9900=A"; fi
 k#034 goto
 k#035 #8======================================================================
 k#036 S9000=A
 k#037 jobend51 #move any GDG files from jobtmp/GDG/subdirs to RUNDATA/subdirs
 k#038 logmsg2 "JobEnd=Normal, StepsExecuted=$XSTEP, LastStep=$JSTEP"
 k#039 exit 0 #ver:20120208 a1b2c0d1e2f3g1i1j0k3l40m4n3o0p0r0s0t1u1v3w0x0y1z0
 k#040 #9======================================================================
 k#041 S9900=A
 k#042 logmsg2 "JobEnd=AbTerm, JCC=$JCC,StepsX/L=$XSTEP/$JSTEP" RV ACK
 k#043 jobabend51 #report GDGs NOT moved from jobtmp/GDG/subdirs to outdirs
 k#044 exit $JCC

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

1C3. MVS JCL conversion to Unix/Linux Korn shell scripts

front end code in output script

The following block of front end code is inserted at the beginning of each Korn shell script (output from the JCL converter). This is the same for all jobs, except for the JOB name & description which is extracted from the // JOB card & inserted on lines 3 & 4 below.

 k#001 #!/bin/ksh
 k#002 ##JAR100   JOB  'TEST MVS2UNIX CONVERSION',DATE=20080323
 k#003 export JOBID2=JAR100 jobid2=jar100; scriptpath="$0"; args="$*"
 k#004 if [[ -z "$JOBID1" ]]; then export JOBID1=$JOBID2; fi
 k#005 for arg in $args; do if [[ "$arg" == *=* ]]; then export $arg; fi; done
 k#006 integer JCC=0 SCC=0 LCC=0  # init step status return codes
 k#007 autoload jobset51 jobset52 jobend51 jobabend51 logmsg1 logmsg2 stepctl51
 k#008 autoload exportfile exportgen0 exportgen1 exportgenall exportgenx
 k#009 . $APPSADM/env/stub.ini  #<-- for control-M (see notes in env/stub.ini)
       ========
 k#010 jobset51  # call function for JCL/script initialization
       ========
 k#011 goto
 k#012 S0000=A

JOBID1 & JOBID2

 k#003 export JOBID2=JAR100 jobid2=jar100; scriptpath="$0"; args="$*"

 k#004 if [[ -z "$JOBID1" ]]; then export JOBID1=$JOBID2; fi

'$JOBID2' always holds the name of the current job, which may have been called by a 'parent' job, whose name is probably held in '$JOBID1' ($JOBID1 holds the name of the 1st job in a series of called jobs).

scriptpath & args

'$scriptpath' & '$args' will be displayed by the 'jobset51' function which is listed on page '1C5' (see lines js#36 & js#37).

"$0" & "$*" had to be saved as labelled variables, since a called function would receive numbered $arguments from the function call not the script call.

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

1C4. MVS JCL conversion to Unix/Linux Korn shell scripts

JCL/script arguments

JCL/scripts may have 2 types of arguments, for example:

 #1. jobname.ksh step=S0020     <-- keyword argument (to restart at step2)
     ======================

 #2. jobname.ksh 123456789      <-- positional argument (arg1 might be SSN#)
     =====================

Keyword arguments must be 'export'ed to capture their values in the script but 'export'ing positional arguments (without '=' signs) would cause errors. This problem is solved by line#5 which examines each argument (for arg in $*) and exports only if it contains an '=' sign.

 k#005 for arg in $args; do if [[ "$arg" == *=* ]]; then export $arg; fi; done
 =============================================================================

jobset51 function - explained

 You should understand the vital importance of the 'jobset51' function
 called on line 10 of all converted JCL/scripts. This is a powerful concept
 - having 1 common function called at the begining of all jobs.

You might use this to your advantage during your conversion. For example VSE sites could use 'partition standard labels' to define commonly used files for all jobs & omit these definitions from the JCL.

You could add 'export's for these commonly used files, at the end of the jobset51 function, to achieve the same effect as 'partition standard labels'.

jobset51 'extract' listing

I have extracted the more important lines of jobset51 onto the next 2 pages. I have sequence numbered the lines for reference in the following discussion. I have added an '*' on the right side of important lines discussed on the pages following the listing.

You can see the full listing of jobset51 on page '5K1'.

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

1C5. MVS JCL conversion to Unix/Linux Korn shell scripts

'jobset51' function - code extract from '5K1'

 js#001 # jobset51 - setup environment for UNIX scripts converted from MVS JCL
 js#005 function jobset51
 js#006 { # jobset51 - called at the begining of each JCL/script
 js#007 #            - inserted by JCL converter from the ctl/jclunixop51
 js#008 # jobset51 uses $RUNLIBS & $RUNDATA (exported in prgmr/oprtr profiles)
 js#009 #          to define Libraries & Data dirs for 'test' or 'prod'uction
 js#010 #
 js#011 #        - - - sample RUNLIBS/RUNDATA for programer testing - - -
 js#012 # export RUNLIBS=/home/mvstest/testlibs #<-- test/demo Libraries
 js#013 # export RUNDATA=/home/mvstest/testdata #<-- test/demo Data superdir
 js#014 #
 js#015 #        - - - sample RUNLIBS/RUNDATA for production operators - - -
 js#016 # export RUNLIBS=/p2/apps/prodlibs      #<-- production libraries
 js#017 # export RUNDATA=/p2/apps/proddata      #<-- production Data superdir
 js#018 #
 js#019 # - JCL/scripts are found via $RUNLIBS/jcls in the profile PATH
 js#020 # - COBOL program subdir defined here in jobset51 as '$RUNLIBS/cblx'
 js#021 #   (this allows programs to have same names as JCL/scripts)
 js#022 #
 js#044 cd $RUNDATA         #change to working dir for production or test      **
 js#045 cdstatus=$?         # capture status of cd $RUNDATA
 js#046 if ((cdstatus))     # ERR if cdstatus not zero (OK)
 js#047    then logmsg2 "ERR: cd \$RUNDATA ($RUNDATA) failed in jobset51"
 js#048         logmsg2 "- investigate, RUNDATA definition in profiles"
 js#049         logmsg1 "- enter to exit"; read reply; exit 91; fi
 js#050 #
 js#051 # cd $RUNDATA means all files are referenced relative to $RUNDATA      **
 js#052 # - allows switching between prod & test files by changing $RUNDATA
 js#053 # - JCL converter has converted HLQs of DSNs to subdirs in $RUNDATA
 js#054 # - High Level Qualifiers might be applications (ar,gl,mstr,tape,etc)
 js#055 #
 js#056 export RLX=$RUNLIBS/cblx      # path for loading COBOL programs        **
 js#057 export RPX=$RUNLIBS/rpgx      # path for loading RPG programs
 js#061 # - COBOL programs are found via $RLX/progname in JCL/scripts
 js#062 # - RPG   programs are found via $RPX/progname in JCL/scripts
 js#064 #
 js#065 if [ -z "$ANIM" ]; then ANIM=-F; fi
 js#066 # 'ANIM=-F' inhibits non-numeric field checks (could change to +F ?)
 js#067 # - cobol programs are called via ---> cobrun $ANIM $RLX/progname <---
 js#068 #
 js#069 # Make subdirs for work files, instream data files,& GDG subdirs       **
 js#079 export JTMP=jobtmp/$JOBID2                                             **
 js#080 export RPTS=rpts                                                        *
 js#081 export SYOT=sysout/$JOBID2                                              *
 js#086 #
 js#087 # Define jobtmp/subdirs for new GDG files                              **
 js#088 umask 002  # ensure perms to create dirs/files 775/664 (group share)    *
 js#089 export JGDG=$JTMP/GDG                                                   *
 js#090 export GTMP=$JTMP/gtmp                                                  *
 js#091 if [[ ! -d $JTMP ]]; then mkdir $JTMP; fi                              **
 js#092 if [[ ! -d $JGDG ]]; then mkdir $JGDG; fi                              **
 js#093 if [[ ! -d $GTMP ]]; then mkdir $GTMP; fi                               *
 js#094 # JTMP/...     - for work files & instream data files
 js#095 # GTMP/...     - for exportgen0,1,etc 'ls' output files
 js#096 #                GDG matching filenames readback to determine latest gen#
 js#097 # JGDG/subdirs - store new GDGs for move back at Normal EOJ
 js#098 #              - see $RUNDATA/ctl/GDGmkdirs called later in jobset51
 js#102 #
 js#110 # Define subdir that might be used for printer output                  **
 js#111 # - some sites might sub-directory by date rpts/yymmdd/...              *
 js#112 # export RPTS=rpts/$(date +%y%m%d)  # use this for subdirs by date      *
 js#113 if [[ ! -d $RPTS ]]; then mkdir $RPTS; fi                              **
 js#114 #
 js#115 # make subdir for SYSOUT files (or any file w/o DSN=...)
 js#116 # $RUNDATA/$SYOT/step#_SYSOUT (where SYOT=sysout/JOBNAME)
 js#117 if [[ ! -d $SYOT ]]; then mkdir $SYOT; fi
 js#118 #
 js#119 # $JTMP & $SYOT are vital - ensure created successfully else exit
 js#120 if [[ -d $JTMP && -d $SYOT ]]; then :
 js#121    else logmsg2 "ERR: $JTMP &/or $SYOT failed creation (in jobset51)"
 js#122         logmsg2 "- investigate: permissions,JTMP,SYOT dirnames changed?"
 js#123         logmsg1 "- enter to exit"; read reply; exit 92; fi
 js#128 #
 js#129 # define subdir for interstep temp/work files & in IDCAMS conversions
 js#130 # ensure wrk/nullfile present & empty, for use on DD DUMMY
 js#131 >wrk/nullfile    # ensure present & empty
 js#132 # could use /dev/null, but some unix variants had problems with that
 js#133 #
 js#134 # Begin code to preserve GDGs if jobs abort
 js#135 # - see doc at www.uvsoftware.ca/mvsjcl.htm#Part_5
        # --> GDG explanations omitted here in Part 1 <--
        #
 js#190 # Default RUNDATE to system date yyyymmdd, but allow cmd line override **
 js#191 # --> jobname.ksh RUNDATE=20091120  <-- override sysdate for this job   *
 js#192 # See explanations at www.uvsoftware.ca/mvscobol.htm#2E1 - 2E9          *
 js#193 # COBOL converter inserts unixwork1.cpy,unixproc1.cpy,perform unixproc1 *
 js#194 # - unixproc1 reformats $RUNDATE into various date formats for COBOL    *
 js#195 if [[ -z "$RUNDATE" ]]; then RUNDATE=$(date +%Y%m%d); fi; export RUNDATE*
 js#197 #
 js#198 # Display various information at begining of JCL/script execution      **
 js#199 # - for the console log, info may be useful to debug problems           *
 js#200 logmsg2 "Begin Job=$JOBID2"                                             *
 js#201 logmsg1 "$scriptpath"                                                   *
 js#202 logmsg1 "Arguments: $args"                                              *
 js#203 logmsg1 "RUNLIBS=$RUNLIBS"                                              *
 js#204 logmsg1 "RUNDATA=$RUNDATA"                                              *
 js#205 logmsg1 "JTMP=$JTMP SYOT=$SYOT"                                         *
 js#206 logmsg1 "RUNDATE=$RUNDATE"                                              *
 js#207 uvtime W1D0 $JTMP/jobbgn
 js#208 export JSTEP=S0000 XSTEP=0
 js#209 integer JCC=0 SCC=0 LCC=0;
 js#210 #
 js#211 # Allow for RESTART at any step by step=... argument on command line:  **
 js#212 # --> jobname.ksh step=S0020   <-- restart at step 2                    *
 js#213 if [[ -n "$step" ]]; then STEP="$step"; fi                              *
 js#214 if [[ -z "$STEP" ]]; then export STEP=S0000; fi                         *
 js#215 if [[ $STEP != S[0-9][0-9][0-9][0-9] ]]                                 *
 js#216    then logmsg2 "ERR: STEP=$STEP invalid"; exit 91; fi                  *
 js#217 alias goto="<<${STEP}=A"                                               **
 js#218 return 0
 js#219 }
 js#220 #----------------------------- end jobset51 -----------------------------

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

1C6. MVS JCL conversion to Unix/Linux Korn shell scripts

jobset51 function - explained

js#044--> cd $RUNDATA #change to working dir for production (or test)

• RUNDATA defines the super directory for all 'DATA' subdirs & files
• RUNDATA is defined in the profiles of programmers & operators
• would be 'test' files for programmers & 'production' files for operators
• scripts address all files relative to $RUNDATA (no absolute filenames)
• means that no changes are required in JCL/scripts for programmers or operators
• we can change file locations on same computer or to different computers
• can have multiple sets of 'test' or 'prod' files for different prgmrs/oprtrs

 js#056--> export RLX=$RUNLIBS/cblx  #setup path for loading programs

• RUNLIBS defines the super directory for all 'LIBrary' subdirs & files
• RUNLIBS is defined in the profiles of programmers & operators (with RUNDATA)
• would be 'test' files for programmers & 'production' files for operators
• RUNLIBS superdir contains subdirs: cpys, cbls, cblx, jcls, parms, etc
• JCL/scripts call COBOL programs (compiled into subdir 'cblx') as follows:

   cobrun $ANIM $RLX/progname
   ==========================

 js#065--> if [ -z "$ANIM" ]; then ANIM=-F; fi  #inhibit non-num field check

   cobrun $ANIM $RLX/progname   <-- scripts execute COBOL programs like this
   ==========================
   export ANIM="+A-F" <-- define switch "+A" to debug/animate
   ==================
 - $ANIM defaults to "-F" 'inhibit non-numeric field check'

 js#079 export JTMP=jobtmp/$JOBID2
 js#089 export JGDG=$JTMP/GDG
 js#090 export GTMP=$JTMP/gtmp
 js#091 if [[ ! -d $JTMP ]]; then mkdir $JTMP; fi
 js#092 if [[ ! -d $JGDG ]]; then mkdir $JGDG; fi
 js#093 if [[ ! -d $GTMP ]]; then mkdir $GTMP; fi

• setup subdirs for work files, instream data,& new generations of GDG files
• instream data must be redirected into a real file for use by COBOL programs
• ACCEPT from SYSIN will read these files due to compile option INDD(SYSIN)
• these subdirs/files are temporary, but might be useful for debugging problems
• there is a rerun option to recover new GDG files from GTMP to RUNDATA/subdirs

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

1C7. MVS JCL conversion to Unix/Linux Korn shell scripts

jobset51 function explained (continued)

 js#081--> export SYOT=sysout/$JOBID2; if [[ ! -d $SYOT ]]; then mkdir $SYOT; fi

• setup a subdir (named from script) for SYSOUT files
• used by Micro Focus COBOL option OUTDD(SYSOUT) which redirects
• 'DISPLAY upon SYSOUT's are redirected into these subdirs
• could rename the directory as desired: 'SYOT=reports' vs 'SYOT=sysout'

js#131 >wrk/nullfile # ensure present & empty

• scripts need a null file for conversion of some IDCAMS functions
• could use /dev/null, but some unix systems had a problem with /dev/null

 js#190--> if [ -z "$RUNDATE" ]; then RUNDATE=$(date +%Y%m%d); fi; export RUNDATE

• allows for RUNDATE to be entered on the command line, for example:

   jobname.ksh RUNDATE=20060718
   ============================

• if RUNDATE not entered on cmdline, then it defaults to the current date
• COBOL program conversions insert copybooks unixwork1.cpy & unixproc1.cpy
• these copybooks reformat $RUNDATE into various formats for use by the program
• see more detail at MVSCOBOL.htm#2E1

js#200 logmsg2 "Begin Job=$JOBID2" js#201 logmsg1 "$scriptpath" js#202 logmsg1 "Arguments: $args" js#203 logmsg1 "RUNLIBS=$RUNLIBS" js#204 logmsg1 "RUNDATA=$RUNDATA" js#205 logmsg1 "JTMP=$JTMP SYOT=$SYOT" js#206 logmsg1 "RUNDATE=$RUNDATE"

• these lines display several vital variables to get them into the console log
• "$scriptpath" shows pathname of the script so you can see if 'test' or 'prod'

 js#213 if [[ -n "$step" ]]; then STEP="$step"; fi
 js#214 if [[ -z "$STEP" ]]; then export STEP=S0000; fi
 js#215 if [[ $STEP != S[0-9][0-9][0-9][0-9] ]]
 js#216    then logmsg2 "ERR: STEP=$STEP invalid"; exit 91; fi
 js#217 alias goto="<<${STEP}=A"

• provides 'step RESTART' for all JCL/scripts
• operators may specify the restart step# on the command line, for example:

   payroll1.ksh step=S0030       <-- restart at step 3
   =======================

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

1C8. MVS JCL conversion to Unix/Linux Korn shell scripts

jobset51 & prompts for dates, etc

The PROC expansion resolves as many &symbols (which become $symbols in scripts) as possible because many sites had coded a lot of symbols that were in fact never used & the defaults were always used.

Another reason we resolved $symbols with defaults is that a common use for &symbols was to determine whether we were using 'test' files or 'prod' files.

The converted systems do not need those because test & production is determined by environment variables (RUNLIBS & RUNDATA) which are set in the profiles of programmers & operators and tested in 'jobset51' as explained on page '1C6'.

But of course you may need to add back some &variables (now $variables) for the (hopefully few) items that really do need to be modified at run time. Here is some sample coding that you might use:

example#1 - prompt for date if not entered on cmd line

 jobname.ksh date=20060718    <-- operator can specify date on command line
 =========================

 # if date not entered on command line - prompt for it now
 if [[ -z "$date" ]]                  # if $date Zero length
    then echo "enter date yyyymmdd"
         read date
 fi

example#2 - better way to prompt & verify a variable

 # if date not entered on command line - prompt until valid date entered
 until [[ -n "$date" ]]              # until $date Non-zero length
 do echo "enter date yyyymmdd"
    read date
 done

example#3 - even better way to prompt & verify a variable

 # if date not entered on command line - prompt until valid date entered
 while ((1))                          # while ((forever))
 do if [[ (${#date} -eq 8) && ($date == 20*) ]]; then break; fi
    echo "enter date yyyymmdd"
    read date
 done

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

1C9. MVS JCL conversion to Unix/Linux Korn shell scripts

sample conversion of 1 step COBOL JCL

Here is the input/output for just the COBOL EXEC step, extracted from the JCL & Korn shell script listed previously. This typical step is the basis for much discussion on the following pages.

sample COBOL step - in JCL

 j#03 //STEP010  EXEC PGM=CAR100,PARM=2003
 j#04 //CUSTMAS  DD DSN=AR.CUSTOMER.MASTER,DISP=SHR
 j#05 //NALIST   DD DSN=AR.CUSTOMER.NAMEADRS.LIST100,DISP=(,CATLG,DELETE),
 j#06 //            UNIT=DISK,SPACE=(TRK,(25,25),RLSE),
 j#07 //            DCB=(MODEL.DSCB,LRECL=133,BLKSIZE=6118,RECFM=FBA)
 j#08 //SYSOUT   DD SYSOUT=*

sample COBOL step - converted to ksh

 k#015 #1======================= begin step#S0010 CAR100 ========================
 k#016 stepctl51;  #calc StepTimes & check jobstop/goto end
 k#017 goto
 k#018 export JSTEP=S0010; ((XSTEP+=1)); SCC=0; LCC=0; alias goto="";
 k#019 logmsg2 "******** Begin Step $JSTEP car100 (#$XSTEP) ********"
 k#020 ##STEP010  EXEC PGM=CAR100,PARM=2008
 k#021 export PROGID=car100
 k#022 export PARM="2008"
 k#023 exportfile  CUSTMAS data/ar.customer.master
 k#024 exportfile  NALIST data/ar.customer.nameadrs.list100
 k#025 exportfile SYSOUT $SYOT/${JOBID2}_${JSTEP}_SYSOUT
 k#026 logmsg2 "Executing--> cobrun $ANIM $RLX/car100"
 k#027 #3----------------------------------------------------------------------
 k#028 cobrun $ANIM $RLX/car100
 k#029 #4----------------------------------------------------------------------
 k#030 LCC=$?; S0010C=$LCC; ((SCC+=LCC)); ((JCC+=LCC)); S0010R=1; alias goto="";
 k#031 if ((S0010C != 0))
 k#032    then logmsg2 "ERR: step#$JSTEP car100 abterm $SCC"
 k#033    alias goto="<<S9900=A"; fi
 k#034 goto

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

1C10. MVS JCL conversion to Unix/Linux Korn shell scripts

'DD' converted to 'exportfile'

 j#04 //CUSTMAS  DD DSN=AR.CUSTOMER.MASTER,DISP=SHR
 j#05 //NALIST   DD DSN=AR.CUSTOMER.NAMEADRS.LIST100,DISP=(,CATLG,DELETE),
 j#06 //            UNIT=DISK,SPACE=(TRK,(25,25),RLSE),
 j#07 //            DCB=(MODEL.DSCB,LRECL=133,BLKSIZE=6118,RECFM=FBA)

k#023 exportfile CUSTMAS data/ar.customer.master k#024 exportfile NALIST data/ar.customer.nameadrs.list100

'exportfile' is a function (see listing on page '3C1') that displays the filenames (for the console log), in addition to generating the korn shell 'export'. For the above examples, the 'export's would be:

The 'export's load the environmental variables for the 'Logical File Names' with the values for the 'Physical File Names'. These values are available to the COBOL programs, since the COBOL converter has inserted 'external' into the file 'select' clauses.

Note that the High Level Qualifier ('ar' in this case) becomes a subdir (within $RUNDATA) & the data files will be converted correspondingly. Any DISK SPACE EXTENT info is ignored (not applicable to unix/linux).

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

1C11. MVS JCL conversion to Unix/Linux Korn shell scripts

COBOL EXECs converted to 'cobrun's

 j#03 //STEP010  EXEC PGM=CAR100,PARM=2003

 k#020 ##STEP010  EXEC PGM=CAR100,PARM=2008
 ..... ............. file exports here ................
 k#026 logmsg2 "Executing--> cobrun $ANIM $RLX/car100"
 k#027 #3----------------------------------------------------------------------
 k#028 cobrun $ANIM $RLX/car100
 k#029 #4----------------------------------------------------------------------

COBOL 'EXEC's converted to 'cobrun's for MicroFocus COBOL. 'cobrun' will execute/interpret the '.int' (car100.int in this example). '.int's are much smaller than executables & allows animation (debugging) without having to recompile or modify any JCL/script, for example:

 --> export ANIM=+A         <-- activate the Animation option
 --> jar100.ksh             <-- run the job (will animate COBOL programs)
 --> export ANIM=""         <-- deactivate Animation

The '.int's usually do not run significantly slower than executables. But if you had some programs doing a lot of memory table indexing, you can compile it to a .gnt (native code) or an executable

'.gnt's are faster & still quire small, but you have to recompile to .int when you need to animate.

Fully compiled executable COBOL programs are fastest, but huge (1 MB each) You would have to remove the 'cobrun $ANIM' from the script. When you need to animate you would have to restore the cobrun $ANIM & recompile to .int.

I recommend leaving all programs as '.int's. The convenience of being able to animate simply by exporting a value (& not having to change anything or recompile) far outweighs the usually insignificant difference in speed.

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

1C12. MVS JCL conversion to Unix/Linux Korn shell scripts

testing program Return Condition

After each EXEC, code is inserted to test the program return status. The mainframe did this automatically, but unix/linux scripts must test success/fail after each program execution.

 j#03 //STEP010  EXEC PGM=CAR100,PARM='MARCH 10, 2005'

 k#027 #3----------------------------------------------------------------------
 k#028 cobrun $ANIM $RLX/car100
 k#029 #4----------------------------------------------------------------------
 k#030 LCC=$?; S0010C=$LCC; ((SCC+=LCC)); ((JCC+=LCC)); S0010R=1; alias goto="";
 k#031 if ((S0010C != 0))
 k#032    then logmsg2 "ERR: step#$JSTEP car100 abterm $SCC"
 k#033    alias goto="<<S9900=A"; fi
 k#034 goto

The Korn shell stores the program status in '$?'. Our converted script saves the status from this temporary variable to a dedicated variable constructed from the current step# (S0010C in example above).

If the status is non-zero, we display the 'abterm' message and we 'goto' the Abnormal termination (tag 'S9900=A') at the end of the program.

This code is a little complex since ksh does not have a real 'goto'. We are using redirected input to 'eat up' the script itself until we reach the stop pattern ('S9900=A' in the example above).

We assigned the redirected input statement to an alias 'goto' in case we needed a $variable in the stop pattern. The goto alias is initialized to null on line k#030 (goto=""), so that if the return code is 0, then the goto on line k#034 will do nothing.

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

1C13. MVS JCL conversion to Unix/Linux Korn shell scripts

EOJ Terminated Normally/Abnormally

 k#035 #8======================================================================
 k#036 S9000=A
 k#037 jobend51 #move any GDG files from jobtmp/GDG/subdirs to RUNDATA/subdirs
 k#038 logmsg2 "JobEnd=Normal, StepsExecuted=$XSTEP, LastStep=$JSTEP"
 k#039 exit 0 #jclunix51 ver:20111015 a1b0c0d3e2f3g1i1j0k3l20m4n3o0p0r0s0t1u1w0x0y1z0
 k#040 #9======================================================================
 k#041 S9900=A
 k#042 logmsg2 "JobEnd=AbTerm, JCC=$JCC,StepsX/L=$XSTEP/$JSTEP" RV ACK
 k#043 jobabend51 #report GDGs NOT moved from jobtmp/GDG/subdirs to outdirs
 k#044 exit $JCC

If all step return codes were zero (normal), then we would reach 'Terminated Normally' & exit 0.

If any step return code was non-zero, then we would 'goto' the 'S9900=A' label (line k#041 above), display 'Terminated Abnormally',& exit 99.

If the JCL had any COND=EVEN steps, you would move them to this point.

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

1C14. MVS JCL conversion to Unix/Linux Korn shell scripts

'SYSOUT' assumed a printer file

COBOL programs can 'DISPLAY UPON SYSOUT' or they can 'WRITE' to a file. If they WRITE reports, the converter will treat the printer files the same as any other data file. The files would be assigned to a directory derived from the top level node in the MVS JCL data file name.

COBOL programs that 'DISPLAY UPON SYSOUT' did not need to declare a printer file, and the MVS JCL did not need to include a DSN for the printer file.

We assume that Micro Focus COBOL was used with option '-C OUTDD(SYSOUT)'. See the ctl/cobdirectives options file listed at MVSCOBOL.htm#5D1.

This option is similar to converting 'DISPLAY UPON SYSOUT' to 'WRITE's to a file which is inserted into the COBOL program (using select name 'SYSOUT').

We give special treatment to any file in the JCL without a DSN assigned. We code the directory as '$SYOT', which is assigned to the 'sysout' directory with a subdir coded as the jobname ($JOBID). Expansion examples follow:

SYSOUT filename expansions

j#08 //SYSOUT DD SYSOUT=*

 k#025 exportfile SYSOUT $SYOT/${JSTEP}_SYSOUT

 k#025 exportfile SYSOUT sysout/JAR100/S0010_SYSOUT              <-- for testing

 k#025 exportfile SYSOUT sysout/JAR100_yymmddHHMMSS/S0010_SYSOUT <-- production

'SYOT' is assigned in the 'jobset51' function inserted at the begining of each script (see listing on page '5K1'). For testing I recommend 'sysout/$JOBID', but for production you might change to 'sysout/${JOBID}_$(date +%y%m%d%H%M%S)' to allow the job to be rerun without overwriting previous SYSOUTs.

Printing Options

Printer files might be sent to a spooling package to allow page restarts, etc. EasySpooler is a popular Unix/Linux spooling package.

For laser printers, you could use one of the 'uvlp' scripts provided by UV Software. For example, 'uvlpLD1' will print a mainframe style report (originally on 15x11 paper) Landscape & Duplex, reducing the cpi & lpi to fit on standard 8 1/2 by 11 (leaving margins for 3 hole punched paper).

The JCL conversion might be enhanced to send the printer files to the spooling package or a uvlp script at the Terminated Normally end of script.

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

1D1. Sample Conversions MVS JCL to Korn shell scripts

Here is a typical 2 step JCL (SORT + COBOL report).

ex#2 jcl0/JAR200 - original JCL

 j#001 //JAR200   JOB  (1234),'TEST/DEMO MVS JCL CONVERT'
 j#002 //* SORT AR.SALES.ITEMS BY PRODUCT CODE FOR LISTING
 j#003 //STEP010  EXEC PGM=SORT,REGION=2048K
 j#004 //SORTIN   DD DSN=AR.SALES.ITEMS,DISP=SHR
 j#005 //SORTOUT  DD DSN=&&TEMPSLS,DISP=(NEW,PASS),
 j#006 //            DCB=(LRECL=64,BLKSIZE=6400,RECFM=FB),
 j#007 //            SPACE=(TRK,(50,50),RLSE),UNIT=DISK
 j#008 //SYSIN    DD *
 j#009 SORT FIELDS=(31,6,CH,A,1,6,CH,A)
 j#010 OMIT COND=((11,2,CH,EQ,C'65'),OR,(COND=(11,2,CH,EQ,C'85'))
 j#011 /*
 j#012 //* LIST AR.SALES.ITEMS IN PRODUCT CODE SEQUENCE
 j#013 //STEP020  EXEC PGM=CAR200,COND=(4,LT,STEP010),PARM=2006
 j#014 //SALEDTL  DD DSN=&&TEMPSLS,DISP=(OLD,PASS)
 j#015 //CUSTMAS  DD DSN=AR.CUSTOMER.MASTER.INDEXED,DISP=SHR
 j#016 //SALELST  DD DSN=AR.SALES.LIST,DISP=(,CATLG,DELETE),
 j#017 //            UNIT=DISK,SPACE=(TRK,(25,25),RLSE),
 j#018 //            DCB=(MODEL.DSCB,LRECL=133,BLKSIZE=6118,RECFM=FBA)

Please see the converted equivalent Korn shell script on the next page ---->

We have omitted the front end 12 lines & the back end 11 lines, since they are the same for all conversions & have already been illustrated for example #1 on page '1C2'.

Please see comments about the conversion of SORT to uvsort 2 pages ahead --->

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

1D2. Sample Conversions MVS JCL to Korn shell scripts

ex#2 jcl3/jar200.ksh - converted equivalent

 k#013 # * SORT AR.SALES.ITEMS BY PRODUCT CODE FOR LISTING
 k#014 #1======================= begin step#S0010 SORT ========================
 k#015 S0010=A
 k#016 stepctl51;  #calc StepTimes & check jobstop/goto end
 k#017 goto
 k#018 export JSTEP=S0010; ((XSTEP+=1)); SCC=0; LCC=0; alias goto="";
 k#019 logmsg2 "******** Begin Step $JSTEP sort (#$XSTEP) ********"
 k#020 ##STEP010  EXEC PGM=SORT,REGION=2048K
 k#021 export PROGID=sort
 k#022 export PARM=""
 k#023 exportfile  SORTIN1 data/ar.sales.items
 k#024 exportfile  SORTOUT $JTMP/__tempsls
 k#025 exportfile SYSIN $JTMP/${JSTEP}_${PROGID}_SYSIN
 k#026 cat > $SYSIN <</*
 k#027 SORT FIELDS=(31,6,CH,A,1,6,CH,A)
 k#028 OMIT COND=((11,2,CH,EQ,C'65'),OR,(COND=(11,2,CH,EQ,C'85'))
 k#029 /*
 k#030 logmsg2 "Executing--> uvsort \"fili1=$SORTIN1,typ=RSF,rcs=64,filo1=$SORT..."
 k#031 #3----------------------------------------------------------------------
 k#032 uvsort "fili1=$SORTIN1,typ=RSF,rcs=64,filo1=$SORTOUT,typ=RSF,rcs=64\
 k#033 ,keys=(30,6,c,a,0,6,c,a),del1=10(2c):65,del1=10(2c):85"
 k#034 #4----------------------------------------------------------------------
 k#035 LCC=$?; S0010C=$LCC; ((SCC+=LCC)); ((JCC+=LCC)); S0010R=1; alias goto="";
 k#036 if ((S0010C != 0)) #need to modify for COND step S0020
 k#037    then logmsg2 "ERR: step#$JSTEP sort abterm $SCC"
 k#038    alias goto="<<S9900=A"; fi
 k#039 goto
 k#040 #/=* LIST AR.SALES.ITEMS IN PRODUCT CODE SEQUENCE
 k#041 #1======================= begin step#S0020 CAR200 ========================
 k#042 if ((S0010C >  4)); then   # COND=(4,LT,STEP010)
 k#043     alias goto="<<S9000=A"; fi
 k#044 goto
 k#045 S0020=A
 k#046 stepctl51;  #calc StepTimes & check jobstop/goto end
 k#047 goto
 k#048 export JSTEP=S0020; ((XSTEP+=1)); SCC=0; LCC=0; alias goto="";
 k#049 logmsg2 "******** Begin Step $JSTEP car200 (#$XSTEP) ********"
 k#050 ##STEP020  EXEC PGM=CAR200,COND=(4,LT,STEP010),PARM=2006
 k#051 export PROGID=car200
 k#052 export PARM="2006"
 k#053 exportfile  SALEDTL $JTMP/__tempsls
 k#054 exportfile  CUSTMAS data/ar.customer.master.indexed
 k#055 exportfile  SALELST data/ar.sales.list
 k#056 logmsg2 "Executing--> cobrun $ANIM $RLX/car200"
 k#057 #3----------------------------------------------------------------------
 k#058 cobrun $ANIM $RLX/car200
 k#059 #4----------------------------------------------------------------------
 k#060 LCC=$?; S0020C=$LCC; ((SCC+=LCC)); ((JCC+=LCC)); S0020R=1; alias goto="";
 k#061 if ((S0020C != 0))
 k#062    then logmsg2 "ERR: step#$JSTEP car200 abterm $SCC"
 k#063    alias goto="<<S9900=A"; fi
 k#064 goto

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

1D4. MVS JCL Conversion to Korn shell scripts - example #2

SORT conversion to uvsort

 j#003 //STEP010  EXEC PGM=SORT,REGION=2048K
 j#004 //SORTIN   DD DSN=AR.SALES.ITEMS,DISP=SHR
 j#005 //SORTOUT  DD DSN=&&TEMPSLS,DISP=(NEW,PASS),
 j#006 //            DCB=(LRECL=64,BLKSIZE=6400,RECFM=FB),
 j#007 //            SPACE=(TRK,(50,50),RLSE),UNIT=DISK
 j#008 //SYSIN    DD *
 j#009 SORT FIELDS=(31,6,CH,A,1,6,CH,A)
 j#010 OMIT COND=((11,2,CH,EQ,C'65'),OR,(COND=(11,2,CH,EQ,C'85'))
 j#011 /*

 k#023 exportfile  SORTIN1 data/ar.sales.items
 k#024 exportfile  SORTOUT $JTMP/__tempsls
 k#025 exportfile SYSIN $JTMP/${JSTEP}_${PROGID}_SYSIN
 k#026 cat > $SYSIN <</*
 k#027 SORT FIELDS=(31,6,CH,A,1,6,CH,A)
 k#028 OMIT COND=((11,2,CH,EQ,C'65'),OR,(COND=(11,2,CH,EQ,C'85'))
 k#029 /*
 k#030 logmsg2 "Executing--> uvsort \"fili1=$SORTIN1,typ=RSF,rcs=64,filo1=$SORT..."
 k#031 #3----------------------------------------------------------------------
 k#032 uvsort "fili1=$SORTIN1,typ=RSF,rcs=64,filo1=$SORTOUT,typ=RSF,rcs=64\
 k#033 ,keys=(30,6,c,a,0,6,c,a),del1=10(2c):65,del1=10(2c):85"
 k#034 #4----------------------------------------------------------------------

The original SORT control cards are seen in the converted script since all control streams are redirected into a tmp file & brought ahead of the program execution. The tmp file is not required for uvsort since the converter has already inserted the SORT FIELDS & RECORD SIZE into the uvsort command string. But listing the control stream allows you to check the SORT/uvsort conversion without referring back to the input.

The uvsort I/O files are declared by keywords 'fili1=...' & 'filo1=...'. The converter will define these using the $SYMBOLS ($SORTIN & $SORTOUT).

      exportfile SORTIN data/ar.sales.items
      exportfile SORTOUT $JTMP/__tempsls
      ====================================================================
      uvsort "fili1=$SORTIN,typ=RSF,rcs=64,filo1=$SORTOUT,typ=RSF,rcs=64\

Note that the SORT FIELD displacements were one relative for the mainframe, but are zero relative for uvsort.

      SORT FIELDS=(31,6,CH,A,1,6,CH,A)
      OMIT COND=((11,2,CH,EQ,C'65'),OR,(COND=(11,2,CH,EQ,C'85'))
      ================================================================
      ,keys=(30,6,c,a,0,6,c,a),del1=10(2c):65,del1=10(2c):85"

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

1E1. Sample Conversion of MVS JCL to Unix/Linux Korn Shell Script

JCL conversion #3 - demo PROCs & GDG files

This page lists the 2 components of sample JCL 'JGL100'(JCL) & 'PGL100'(PROC). The next page will list the JCL after PROC expansion and the following page will list the Korn shell script conversion result.

jcl0/JGL100 - JCL before PROC expansion

 //JGL100   JOB  (1234),'LIST GL MASTER CHART OF ACCOUNTS'               00000010
 //* MVS JCL CONVERSION DEMO - PROCs & GDG files                         00000020
 //STEPA    EXEC PGL100,HLQ=GL,YEAREND=2003                              00000030

proc0/PGL100 - PROC called by JGL100

 //PGL100   PROC HLQ=GL,YEAREND=2002                                     00000010
 //* LIST G/L CHART OF ACCOUNTS FROM ACCOUNT.MASTER                      00000020
 //STEP010  EXEC PGM=CGL100,REGION=1024K,PARM=&YEAREND                   00000030
 //ACCTMAS  DD DSN=&HLQ..ACCOUNT.MASTER(0),DISP=SHR                      00000040
 //ACTLIST  DD DSN=&HLQ..ACCOUNT.ACNTLIST(+1),DISP=(,CATLG,DELETE),      00000050
 //            UNIT=DISK,SPACE=(TRK,(25,25),RLSE),                       00000060
 //            DCB=(MODEL.DSCB,LRECL=133,BLKSIZE=6118,RECFM=FBA)         00000070
 //SYSOUT   DD SYSOUT=*                                                  00000080

Notes

See the step by step conversion instructions beginning on page '1Q1'.

The 1st procedure is to remove any obsolete sequence numbers from the right side of JCLs & PROCs, change filenames to lower case,& append extensions to identify the files (.jcl or .proc).

The 2nd procedure is the 1 time expansion of PROCs and the 3rd procedure will convert the expanded JCL to Korn shell scripts.

Please relate these conversions to the directories illustrated on page '1A1'

1. strip seq#s: proc0 --> procs, jcl0 --> jcl1, parm0 --> parms
   
   
2. expand procs: jcl1 + procs --> jcl2
   
   
3. convert JCL: jcl2 + parms --> jcl3
   

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

1E2. Sample Conversion of MVS JCL to Korn Shell Script

jcl2/jgl100.jcl - JCL after PROC expansion

 j#01 //JGL100   JOB  (1234),'LIST GL MASTER CHART OF ACCOUNTS'
 j#02 //* MVS JCL CONVERSION DEMO - PROCs & GDG files
 j#03 //*
 j#04 ##STEPA    EXEC PGL100,HLQ=GL,YEAREND=2003               #<-- PROC1 call
 j#05 //PGL100   PROC HLQ=GL,YEAREND=2002
 j#06 //*
 j#07 //STEPA    EXEC PGL100,HLQ=GL,YEAREND=2003               #<-- PROC1 exp
 j#08 //* LIST G/L CHART OF ACCOUNTS FROM ACCOUNT.MASTER
 j#09 //STEP010  EXEC PGM=CGL100,REGION=1024K,PARM=&YEAREND
 j#10 //ACCTMAS  DD DSN=GL.ACCOUNT.MASTER(0),DISP=SHR
 j#11 //ACTLIST  DD DSN=GL.ACCOUNT.ACNTLIST(+1),DISP=(,CATLG,DELETE),
 j#12 //            UNIT=DISK,SPACE=(TRK,(25,25),RLSE),
 j#13 //            DCB=(MODEL.DSCB,LRECL=133,BLKSIZE=6118,RECFM=FBA)
 j#14 //SYSOUT   DD SYSOUT=*
 j#15 ##PEND1 PGL100

Notes

1. This is the result of expanding the PROCs while copying from jcl1 to jcl2. See the input listings on the previous page.
   

    jcl1/jgl100.jcl + procs/pgl100.jcl --> jcl2/jgl100.jcl

2. Note that any symbol values on the PROC declaration are overridden by symbol values on the PROC call. 'YEAREND=2002' is overridden by 'YEAREND=2003', so the value of '&YEAREND' (on //STEP010) will be '2003'.
   
   
3. The next page will list the result of converting this expanded JCL (jcl2/jgl100.jcl) to a Korn shell script (jcl3/jgl100.ksh).
   

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

1E3. Sample Conversion of MVS JCL to Korn Shell Script

jcl3/jgl100.ksh - JCL after conversion to ksh script

 k#013 # * MVS JCL CONVERSION DEMO - PROCs & GDG files
 k#014 ##STEPA    EXEC PGL100,HLQ=GL,YEAREND=2003                    #<-PROC1call
 k#015 ##PGL100   PROC HLQ=GL,YEAREND=2002
 k#016 HLQ="GL";YEAREND="2002";
 k#017 ##STEPA    EXEC PGL100,HLQ=GL,YEAREND=2003                    #<-PROC1exp
 k#018 HLQ="GL";YEAREND="2003";
 k#019 # * LIST G/L CHART OF ACCOUNTS FROM ACCOUNT.MASTER
 k#020 #1======================= begin step#S0010 CGL100 ========================
 k#021 S0010=A
 k#022 stepctl51;  #calc StepTimes & check jobstop/goto end
 k#023 goto
 k#024 export JSTEP=S0010; ((XSTEP+=1)); SCC=0; LCC=0; alias goto="";
 k#025 logmsg2 "******** Begin Step $JSTEP cgl100 (#$XSTEP) ********"
 k#026 ##STEPA  EXEC PGM=CGL100,REGION=1024K,PARM=&YEAREND
 k#027 export PROGID=cgl100
 k#028 export PARM="2003"
 k#029 exportgen0 0 ACCTMAS data/gl.account.master_
 k#030 exportgen1 +1 ACTLIST $JGDG/data/gl.account.acntlist_
 k#031 #exportgen1 $JGDG/subdir/tempfiles restored to outdir at Normal EOJ
 k#032 exportfile SYSOUT $SYOT/${JOBID2}_${JSTEP}_SYSOUT
 k#033 logmsg2 "Executing--> cobrun $ANIM $RLX/cgl100"
 k#034 #3----------------------------------------------------------------------
 k#035 cobrun $ANIM $RLX/cgl100
 k#036 #4----------------------------------------------------------------------
 k#037 LCC=$?; S0010C=$LCC; ((SCC+=LCC)); ((JCC+=LCC)); S0010R=1; alias goto="";
 k#038 if ((S0010C != 0))
 k#039    then logmsg2 "ERR: step#$JSTEP cgl100 abterm $SCC"
 k#040    alias goto="<<S9900=A"; fi
 k#041 goto

We have omitted the front end 11 lines & the back end 10 lines, since they are the same for all conversions & have already been illustrated for example #1 on page '1C2'.

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

1E4. Sample Conversion of MVS JCL to Korn Shell Script

JCL conversion #3 - demo PROCs & GDG files

Here are the data file definitions extracted from the previous JCL & the corresponding converted equivalents from the Korn shell script.

 j#08 //ACCTMAS  DD DSN=GL.ACCOUNT.MASTER(0),DISP=SHR
 j#09 //ACTLIST  DD DSN=GL.ACCOUNT.ACNTLIST(+1),DISP=(,CATLG,DELETE),
 j#10 //            UNIT=DISK,SPACE=(TRK,(25,25),RLSE),
 j#11 //            DCB=(MODEL.DSCB,LRECL=133,BLKSIZE=6118,RECFM=FBA)

 k#029 exportgen0 0 ACCTMAS data/gl.account.master_           #<-- current generation
 k#030 exportgen1 +1 ACTLIST $JGDG/data/gl.account.acntlist_  #<-- next generation

One of the main objectives of this demo #3 was to illustrate the conversion of Generation (GDG) files to Korn shell functions (exportgen0 & exportgen1).

You can see exportgen0 & exportgen1 listed ahead on pages '5J1' & '5J2'. Also see Part_5 for more discussion including features that go well beyond the GDG implementation on the mainframe.

Note that the '(0)' suffix on an MVS DSN indicates the current generation & '(+1)' indicates the next generation.

GDG filename examples

data/gl.account.master_000001 <-- 1st generation of GDG file after conversion data/gl.account.master_000002 data/gl.account.master_000003

The data conversion procedures should append '_000001' to any GDG filenames.

See data conversion procedures in MVSDATA.htm. Page 4E1+ & 4G1 describes making a data conversion control file from the LISTCAT info. Page 4G5 gives the operating instructions to generate 'uvcopy jobs' from the COBOL copybooks to translate character fields from EBCDIC to ASCII while preserving any packed fields & correcting any zoned signs.

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

1F1. Sample Conversion of MVS JCL to Unix/Linux Korn Shell Script

This page lists the 3 components of sample JCL 'JGL200' (JCL, PROC,& a library member for the SORT keys). The next page will list the JCL after PROC expansion and the following page will list the Korn shell script conversion result.

ex#4 jcl0/JGL200 - JCL before PROC expansion

 //JGL200   JOB  (1234),'TEST/DEMO MVS JCL CONVERSION'                   00000010
 //* SORT TRANSACTIONS & UPDATE GL ACCOUNT MASTER                        00000020
 //* - demo GDG processing, write gltrans(+1) & read back as (+1)        00000030
 //STEPA    EXEC PGL200,HLQ=GL,YEAREND=2003                              00000040

proc0/PGL200 - PROC called by JGL200

 //PGL200   PROC HLQ=GL,YEAREND=2002                                     00000010
 //* SORT GL TRANSACTIONS BEFORE UPDATING ACCOUNT MASTER                 00000020
 //STEP010  EXEC PGM=SORT,REGION=2048K                                   00000030
 //SORTIN   DD DSN=&HLQ..ACCOUNT.TRAN1,DISP=OLD                          00000040
 //SORTOUT  DD DSN=&HLQ..ACCOUNT.TRANS(+1),DISP=(,CATLG,DELETE),         00000050
 //            DCB=(LRECL=80,BLKSIZE=8000,RECFM=FB),                     00000060
 //            SPACE=(TRK,(50,50),RLSE),UNIT=DISK                        00000070
 //SYSIN    DD DSN=&HLQ..PARMS(PGL200S1)                                 00000080
 //* UPDATE ACCOUNT.MASTER WITH TRANSACTION DETAIL                       00000090
 //STEP020  EXEC PGM=CGL200,COND=(4,LT,STEP010),PARM=&YEAREND            00000100
 //GLTRANS  DD DSN=&HLQ..ACCOUNT.TRANS(+1),DISP=OLD                      00000110
 //GLMSOLD  DD DSN=&HLQ..ACCOUNT.MASTER(0),DISP=OLD                      00000120
 //GLMSNEW  DD DSN=&HLQ..ACCOUNT.MASTER(+1),DISP=(,CATLG,DELETE),        00000130
 //            UNIT=DISK,SPACE=(TRK,(50,50),RLSE),                       00000140
 //            DCB=(MODEL.DSCB,LRECL=80,BLKSIZE=6118,RECFM=FBA)          00000150

parm0/PGL200S1 - library member called by PGL200

 SORT FIELDS=(1,18,CH,A,69,12,CH,A)

Notes

1. See the step by step conversion instructions beginning on page '1Q1'.
   
   
2. The 1st procedure is to remove any obsolete sequence numbers from the right side of JCLs & PROCs, change filenames to lower case,& append extensions to identify the files (.jcl or .proc).
   
   
3. The 2nd procedure is the 1 time expansion of PROCs and the 3rd procedure will convert the expanded JCL to Korn shell scripts.
   
   
4. Please relate these conversions to the directories illustrated on page '1A1'
   

      strip seq#s:  proc0 --> procs, jcl0 --> jcl1, parm0 --> parms

      expand procs: jcl1 + procs + parms --> jcl2

      convert JCL:  jcl2 --> jcl3

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

1F2. Sample Conversion of MVS JCL to Korn Shell Script

ex#4 jcl2/jgl200.jcl - JCL after PROC expansion

 j#01 //JGL200   JOB  (1234),'TEST/DEMO MVS JCL CONVERSION'
 j#02 //* SORT TRANSACTIONS & UPDATE GL ACCOUNT MASTER
 j#03 //* - demo GDG processing, write gltrans(+1) & read back as (+1)
 j#04 //*
 j#05 ##STEPA    EXEC PGL200,HLQ=GL,YEAREND=2003               #<-- PROC1 call
 j#06 //PGL200   PROC HLQ=GL,YEAREND=2002
 j#07 //*
 j#08 //STEPA    EXEC PGL200,HLQ=GL,YEAREND=2003               #<-- PROC1 exp
 j#09 //* SORT GL TRANSACTIONS BEFORE UPDATING ACCOUNT MASTER
 j#10 //STEP010  EXEC PGM=SORT,REGION=2048K
 j#11 //SORTIN   DD DSN=GL.ACCOUNT.TRAN1,DISP=OLD
 j#12 //SORTOUT  DD DSN=GL.ACCOUNT.TRANS(+1),DISP=(,CATLG,DELETE),
 j#13 //            DCB=(LRECL=80,BLKSIZE=8000,RECFM=FB),
 j#14 //            SPACE=(TRK,(50,50),RLSE),UNIT=DISK
 j#15 //SYSIN    DD DSN=GL.PARMS(PGL200S1)
 j#16 /=* UPDATE ACCOUNT.MASTER WITH TRANSACTION DETAIL
 j#17 //*============================ step# 002 ============================
 j#18 //STEP020  EXEC PGM=CGL200,COND=(4,LT,STEP010),PARM=&YEAREND
 j#19 //GLTRANS  DD DSN=GL.ACCOUNT.TRANS(+1),DISP=OLD
 j#20 //GLMSOLD  DD DSN=GL.ACCOUNT.MASTER(0),DISP=OLD
 j#21 //GLMSNEW  DD DSN=GL.ACCOUNT.MASTER(+1),DISP=(,CATLG,DELETE),
 j#22 //            UNIT=DISK,SPACE=(TRK,(50,50),RLSE),
 j#23 //            DCB=(MODEL.DSCB,LRECL=80,BLKSIZE=6118,RECFM=FBA)
 j#24 ##PEND1 PGL200

Please compare this jgl200.jcl conversion with the previous jar200.jcl. Both are 2 step jobs executing a SORT & a COBOL program. This job is intended to illustrate the following:

1. PROC expansions and &SYMBOL substitutions.
   
   
2. Generation (GDG) files. Note lines j#16 & j#17 above. The '(0)' suffix on GL.ACCOUNT.MASTER(0) signifies the current generation, while '(+1)' causes the 'next' generation to be created.
   
   
3. In the output scripts GDG files are implemented via functions exportgen0 & exportgen1. See these functions listed on pages '5J1' & '5J2' in Part_5.
   
   
4. Generation data files are suffixed with a 6 digit generation#. Later on page '1S4', you will be able to execute this job & observe the incrementing of the generation#.
   
   
5. Note the control card library member which contains the SORT FIELDS. This will be explained in detail on page '1F4' ahead.
   

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

1F3. jcl3/jgl200.ksh - JCL after conversion to ksh script

 k#013 # * SORT TRANSACTIONS & UPDATE GL ACCOUNT MASTER
 k#014 # * - demo GDG processing, write gltrans(+1) & read back as (+1)
 k#020 # * SORT GL TRANSACTIONS BEFORE UPDATING ACCOUNT MASTER
 k#021 #1======================= begin step#S0010 SORT ========================
 k#022 S0010=A
 k#023 stepctl51;  #calc StepTimes & check jobstop/goto end
 k#024 goto
 k#025 export JSTEP=S0010; ((XSTEP+=1)); SCC=0; LCC=0; alias goto="";
 k#026 logmsg2 "******** Begin Step $JSTEP sort (#$XSTEP) ********"
 k#027 ##STEPA  EXEC PGM=SORT,REGION=2048K
 k#028 export PROGID=sort
 k#029 export PARM=""
 k#030 exportfile  SORTIN1 data/gl.account.tran1
 k#031 exportgen1 +1 SORTOUT $JGDG/data/gl.account.trans_
 k#032 #exportgen1 $JGDG/subdir/tempfiles restored to outdir at Normal EOJ
 k#033 exportfile  SYSIN $RUNLIBS/parms/pgl200s1
 k#034 #2-------------------------- parms/pgl200s1 ---------------------------
 k#035 # SORT FIELDS=(1,8,CH,A,69,12,CH,A)
 k#036 logmsg2 "Executing--> uvsort \"fili1=$SORTIN1,typ=RSF,rcs=80,filo1=$SORT..."
 k#037 #3----------------------------------------------------------------------
 k#038 uvsort "fili1=$SORTIN1,typ=RSF,rcs=80,filo1=$SORTOUT,typ=RSF,rcs=80\
 k#039 ,keys=(0,8,c,a,68,12,c,a)"
 k#040 #4----------------------------------------------------------------------
 k#041 LCC=$?; S0010C=$LCC; ((SCC+=LCC)); ((JCC+=LCC)); S0010R=1; alias goto="";
 k#042 if ((S0010C != 0)) #need to modify for COND step S0020
 k#043    then logmsg2 "ERR: step#$JSTEP sort abterm $SCC"
 k#044    alias goto="<<S9900=A"; fi
 k#045 goto
 k#046 #/=* UPDATE ACCOUNT.MASTER WITH TRANSACTION DETAIL
 k#047 #1======================= begin step#S0020 CGL200 ========================
 k#048 if ((SCC >  4)); then   # COND=(4,LT,STEP010)
 k#049     alias goto="<<S9000=A"; fi
 k#050 goto
 k#051 S0020=A
 k#052 stepctl51;  #calc StepTimes & check jobstop/goto end
 k#053 goto
 k#054 export JSTEP=S0020; ((XSTEP+=1)); SCC=0; LCC=0; alias goto="";
 k#055 logmsg2 "******** Begin Step $JSTEP cgl200 (#$XSTEP) ********"
 k#056 ##STEP020  EXEC PGM=CGL200,COND=(4,LT,STEP010),PARM=&YEAREND
 k#057 export PROGID=cgl200
 k#058 export PARM="2003"
 k#059 exportgen1 +1 GLTRANS $JGDG/data/gl.account.trans_
 k#060 #exportgen1 $JGDG/subdir/tempfiles restored to outdir at Normal EOJ
 k#061 exportgen0 0 GLMSOLD data/gl.account.master_
 k#062 exportgen1 +1 GLMSNEW $JGDG/data/gl.account.master_
 k#063 logmsg2 "Executing--> cobrun $ANIM $RLX/cgl200"
 k#064 #3----------------------------------------------------------------------
 k#065 cobrun $ANIM $RLX/cgl200
 k#066 #4----------------------------------------------------------------------
 k#067 LCC=$?; S0020C=$LCC; ((SCC+=LCC)); ((JCC+=LCC)); S0020R=1; alias goto="";
 k#068 if ((S0020C != 0))
 k#069    then logmsg2 "ERR: step#$JSTEP cgl200 abterm $SCC"
 k#070    alias goto="<<S9900=A"; fi
 k#071 goto

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

1F4. Sample Conversion of MVS JCL to Korn Shell Script

control card library members

jgl200.jcl illustrates a SYSIN control card library member, which contains the 'SORT FIELDS'. Note that the previous jar200.jcl included the SORT FIELDS as embedded '//SYSIN DD *' instream data, but PROCs are not allowed to contain instream data, so control card library members are used.

SYSIN control card member conversion

j#13 //SYSIN DD DSN=GL.CTLCDLIB(PGL200S1)

 k#033 exportfile  SYSIN $RUNLIBS/parms/pgl200s1
 k#034 #2-------------------------- parms/pgl200s1 ---------------------------
 k#035 # SORT FIELDS=(1,8,CH,A,69,12,CH,A)
 k#036 logmsg2 "Executing--> uvsort \"fili1=$SORTIN1,typ=RSF,rcs=80,filo1=$SORT..."
 k#037 #3----------------------------------------------------------------------
 k#038 uvsort "fili1=$SORTIN1,typ=RSF,rcs=80,filo1=$SORTOUT,typ=RSF,rcs=80\
 k#039 ,keys=(0,8,c,a,68,12,c,a)"
 k#040 #4----------------------------------------------------------------------

Notes

1. For the conversion you must store the control card members in subdir 'parms'. When the converter encounters 'SYSIN DD DSN=GL.CTLCDLIB(PGL200S1)' it will look for file 'parms/pgl200s1' in the conversion library $RUNLIBS. The subdir will be changed to .../parms/..., for example 'GL.CTLCDLIB(PGL200S1)' will be changed to 'data/gl.parms/pgl200s1'
   
   
2. Storing the control cards in subdir parms/... was required by the converter for the many SYSINs for SORT FIELDS, etc, But this will also work for your COBOL programs that read SYSIN control cards. This assumes that you are OK with having all SYSIN control card modules in 1 common directory (parms).
   
   
3. Note that the converter will always show the control card member contents as #comments within the converted script.
   
   
4. In the SORT case, the #comments may help you to verify the conversion to uvsort, especially for more complex SORTs with INCLUDEs, OMITs, etc (see several examples later in MVSJCL2.htm#Part_6).
   
   
5. After conversion, you could remove the file definition for 'parms' & the embedded #comments if you wish, since the SORT FIELDS have been inserted into the 'uvsort' converted equivalent.
   

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

1G1. Sample Conversion of MVS JCL to Unix/Linux Korn Shell Script

jcl2/jgl300.jcl - demo IEBGENER/IDCAMS & CONDition codes

 j#01 //JGL300   JOB  (1234),'TEST MVS JCL CONVERSION'
 j#02 //* DEMO CONVERSION OF IEBGENER (TO UVCP) & IDCAMS (TO CP)
 j#03 //* COPY GL.ACCOUNT.MASTER TO A TEMP/WORK FILE & BACK (GEN# +1)
 j#04 //* - demos CONDition code testing (also see JGL320 IF/THEN/ENDIF)
 j#05 //STEP010  EXEC PGM=IEBGENER
 j#06 //SYSUT1   DD   DSN=GL.ACCOUNT.MASTER(0),DISP=SHR
 j#07 //SYSUT2   DD   DSN=&&TEMPGLM,DISP=(NEW,PASS),DCB=(LRECL=80)
 j#08 /=*
 j#09 //*============================ step# 002 ============================
 j#10 //STEP020  EXEC PGM=IDCAMS,COND=(4,LT,STEP010)
 j#11 //TEMPGLM  DD   DSN=&&TEMPGLM,DISP=(OLD,PASS)
 j#12 //ACNTMAS  DD   DSN=GL.ACCOUNT.MASTER(+1),DISP=(NEW,CATLG),LRECL=80
 j#13 //SYSIN    DD   *
 j#14   REPRO INFILE(TEMPGLM) OUTFILE(ACNTMAS) RECORDSIZE(80)
 j#15 /*

1. See the converted output Korn shell script on the next page --->
   
   
2. 'JGL300' illustrates how IEBGENER & IDCAMS are converted to uvcp. It simply copies the account.master file to a temporary file & back. Note that the '&&TEMPCM' file will be assigned to the 'wrk' subdir in the converted JCL/script.
   
   
3. The '(0)' suffix of 'account.master(0)' indicates a generation file. When you later execute this job (on page '1S5'), you will notice that 'account.master_000003' (the latest generation) will be selected by the 'exportgen0' function. When copied back to data/gl.account.master(+1), the 'exportgen1' function will create a new generation as 'account.master_000004'. See much more about the VU GDG system in 'Part_5'.
   
   
4. We have omitted the front end 11 lines & the back end 10 lines, since they are the same for all conversions & have already been illustrated for example #1 on page '1C2'.
   
   
5. This JCL also illustrates the conversion of 'CONDition code testing. 'COND=(4,LT,STEP010)' on line J#09 above is converted to 'if ((S0010C <= 4))' and 'goto S9000' on lines k#037&k#038. Note that satisfied CONDitions 'shut off' step execution. Satisfied unix 'if' conditions enable execution. This reversal is compensated for by the reversed operands on the 'if'.
   
   
6. To test the COND 'failure' condition, you could simply change the name of the input filename to something that will not be found.
   
   
7. See more 'COND' discussion at MVSJCL2.htm#28F1
   

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

1G2. Sample Conversion of MVS JCL to Korn Shell Script

jcl3/jgl300.ksh - JCL/script

 k#013 # * DEMO CONVERSION OF IEBGENER (TO UVCP) & IDCAMS (TO CP)
 k#014 # * COPY GL.ACCOUNT.MASTER TO A TEMP/WORK FILE & BACK (GEN# +1)
 k#015 # * - demos CONDition code testing (also see JGL320 IF/THEN/ENDIF)
 k#016 #1======================= begin step#S0010 IEBGENER ========================
 k#017 S0010=A
 k#018 stepctl51;  #calc StepTimes & check jobstop/goto end
 k#019 goto
 k#020 export JSTEP=S0010; ((XSTEP+=1)); SCC=0; LCC=0; alias goto="";
 k#021 logmsg2 "******** Begin Step $JSTEP iebgener (#$XSTEP) ********"
 k#022 ##STEP010  EXEC PGM=IEBGENER
 k#023 export PROGID=iebgener
 k#024 export PARM=""
 k#025 exportgen0 0 SYSUT1 data/gl.account.master_
 k#026 exportfile  SYSUT2 $JTMP/__tempglm
 k#027 logmsg2 "Executing--> uvcp \"fili1=$SYSUT1,typ=RSF,rcs=80,filo1=$SYSUT2,..."
 k#028 #3----------------------------------------------------------------------
 k#029 uvcp "fili1=$SYSUT1,typ=RSF,rcs=80,filo1=$SYSUT2,typ=RSF,rcs=80"
 k#030 #4----------------------------------------------------------------------
 k#031 LCC=$?; S0010C=$LCC; ((SCC+=LCC)); ((JCC+=LCC)); S0010R=1; alias goto="";
 k#032 if ((S0010C != 0)) #need to modify for COND step S0020
 k#033    then logmsg2 "ERR: step#$JSTEP iebgener abterm $SCC"
 k#034    alias goto="<<S9900=A"; fi
 k#035 goto
 k#036 #1======================= begin step#S0020 IDCAMS ========================
 k#037 if ((S0010C >  4)); then   # COND=(4,LT,STEP010)
 k#038     alias goto="<<S9000=A"; fi
 k#039 goto
 k#040 S0020=A
 k#041 stepctl51;  #calc StepTimes & check jobstop/goto end
 k#042 goto
 k#043 export JSTEP=S0020; ((XSTEP+=1)); SCC=0; LCC=0; alias goto="";
 k#044 logmsg2 "******** Begin Step $JSTEP idcams (#$XSTEP) ********"
 k#045 ##STEP020  EXEC PGM=IDCAMS,COND=(4,LT,STEP010)
 k#046 export PROGID=idcams
 k#047 export PARM=""
 k#048 exportfile  TEMPGLM $JTMP/__tempglm
 k#049 exportgen1 +1 ACNTMAS $JGDG/data/gl.account.master_
 k#050 #exportgen1 $JGDG/subdir/tempfiles restored to outdir at Normal EOJ
 k#051 exportfile SYSIN $JTMP/${JSTEP}_${PROGID}_SYSIN
 k#052 cat > $SYSIN <</*
 k#053   REPRO INFILE(TEMPGLM) OUTFILE(ACNTMAS) RECORDSIZE(80)
 k#054 /*
 k#055 logmsg2 "Executing--> uvcp \"fili1=$TEMPGLM,typ=RSF,rcs=80,filo1=$ACNTMA..."
 k#056 #3----------------------------------------------------------------------
 k#057 uvcp "fili1=$TEMPGLM,typ=RSF,rcs=80,filo1=$ACNTMAS,typ=RSF,rcs=80";
 k#058 LCC=$?; ((SCC+=LCC)); ((JCC+=LCC));
 k#059 #4----------------------------------------------------------------------
 k#060 S0020C=$SCC; ((JCC+=SCC)); S0020R=1; alias goto="";
 k#061 if ((S0020C != 0))
 k#062    then logmsg2 "ERR: step#$JSTEP idcams abterm $SCC"
 k#063    alias goto="<<S9900=A"; fi
 k#064 goto

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

1G3. Sample Conversion of MVS JCL to Unix/Linux Korn Shell Script

jcl2/jgl320.jcl - demo IF/THEN/ENDIF

 j#01 //JGL320   JOB  (1234),'TEST MVS JCL CONVERSION'
 j#02 //* DEMO CONVERSION OF IEBGENER (TO UVCP) & IDCAMS (TO CP)
 j#03 //* COPY GL.ACCOUNT.MASTER TO A TEMP/WORK FILE & BACK (GEN# +1)
 j#04 //* - demos IF/THEN/ENDIF (vs CONDition codes in JGL320)
 j#05 //* - change input filename (step1 will fail) & step2 will be skipped
 j#06 //STEP010  EXEC PGM=IEBGENER
 j#07 //SYSUT1   DD   DSN=GL.ACCOUNT.MASTER(0),DISP=SHR
 j#08 //SYSUT2   DD   DSN=&&TEMPGLM,DISP=(NEW,PASS),DCB=(LRECL=80)
 j#09 //*
 j#10 // IF (RC = 0) THEN
 j#11 //STEP020  EXEC PGM=IDCAMS,COND=(4,LT,STEP010)
 j#12 //TEMPGLM  DD   DSN=&&TEMPGLM,DISP=(OLD,PASS)
 j#13 //ACNTMAS  DD   DSN=GL.ACCOUNT.MASTER(+1),DISP=(NEW,CATLG),LRECL=80
 j#14 //SYSIN    DD   *
 j#15    REPRO INFILE(TEMPGLM) OUTFILE(ACNTMAS)
 j#16 /*
 j#17 // ENDIF

Notes

1. This job is the same as jgl300.jcl with the addition of IF/THEN/ENDIF to make step 2 conditional on successful Return Code from step 1.
   
   
2. The CONDition code tests already do this, but this was a convenient JCL to test/demo IF/THEN/ENDIF.
   
   
3. See the converted script on the next page & note that the equivalent of IF & ENDIF on lines k#037 & k#067.
   
   
4. jgl320 has added the IF/ENDIF tests in addition to the 'COND' tests already described in jgl300 above. More likely you would remove the 'COND' tests if you were adding IF/ENDIF tests.
   
   
5. To test the IF 'failure' condition, you could simply change the name of the input filename to something that will not be found.
   
   
6. Note that the condition code test at the end of step 1 on line k#033 has been changed from the usual 'if ((S0010C != 0))' to 'if ((S0010C > 4))' to allow us to reach the 'COND' test.
   
   
7. uvcp returns 99 on failure which would be detected by the normal return code test, vs the IF/THEN test which follows.
   
   
8. See more 'IF' discussion at MVSJCL2.htm#28G1
   

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

1G4. jcl3/jgl320.ksh - demo IF/THEN/ENDIF

 k#013 # * DEMO CONVERSION OF IEBGENER (TO UVCP) & IDCAMS (TO CP)
 k#014 # * COPY GL.ACCOUNT.MASTER TO A TEMP/WORK FILE & BACK (GEN# +1)
 k#015 # * - demos IF/THEN/ENDIF (vs CONDition codes in JGL320)
 k#016 # * - change input filename (step1 will fail) & step2 will be skipped
 k#017 #1======================= begin step#S0010 IEBGENER ========================
 k#018 S0010=A
 k#019 stepctl51;  #calc StepTimes & check jobstop/goto end
 k#020 goto
 k#021 export JSTEP=S0010; ((XSTEP+=1)); SCC=0; LCC=0; alias goto="";
 k#022 logmsg2 "******** Begin Step $JSTEP iebgener (#$XSTEP) ********"
 k#023 ##STEP010  EXEC PGM=IEBGENER
 k#024 export PROGID=iebgener
 k#025 export PARM=""
 k#026 exportgen0 0 SYSUT1 data/gl.account.master_
 k#027 exportfile  SYSUT2 $JTMP/__tempglm
 k#028 logmsg2 "Executing--> uvcp \"fili1=$SYSUT1,typ=RSF,rcs=80,filo1=$SYSUT2,..."
 k#029 #3----------------------------------------------------------------------
 k#030 uvcp "fili1=$SYSUT1,typ=RSF,rcs=80,filo1=$SYSUT2,typ=RSF,rcs=80"
 k#031 #4----------------------------------------------------------------------
 k#032 LCC=$?; S0010C=$LCC; ((SCC+=LCC)); ((JCC+=LCC)); S0010R=1; alias goto="";
 k#033 if ((S0010C > 4)) #need to modify for COND step S0020
 k#034    then logmsg2 "ERR: step#$JSTEP iebgener abterm $SCC"
 k#035    alias goto="<<S9900=A"; fi
 k#036 goto
 k#037 if ((S0010C == 0)); then #IF (RC = 0) THEN #J001(1)
 k#038 #1======================= begin step#S0020 IDCAMS ========================
 k#039 if ((S0010C >  4)); then   # COND=(4,LT,STEP010)
 k#040     alias goto="<<S9000=A"; fi
 k#041 goto
 k#042 S0020=A
 k#043 stepctl51;  #calc StepTimes & check jobstop/goto end
 k#044 goto
 k#045 export JSTEP=S0020; ((XSTEP+=1)); SCC=0; LCC=0; alias goto="";
 k#046 logmsg2 "******** Begin Step $JSTEP idcams (#$XSTEP) ********"
 k#047 ##STEP020  EXEC PGM=IDCAMS,COND=(4,LT,STEP010)
 k#048 export PROGID=idcams
 k#049 export PARM=""
 k#050 exportfile  TEMPGLM $JTMP/__tempglm
 k#051 exportgen1 +1 ACNTMAS $JGDG/data/gl.account.master_
 k#052 #exportgen1 $JGDG/subdir/tempfiles restored to outdir at Normal EOJ
 k#053 exportfile SYSIN $JTMP/${JSTEP}_${PROGID}_SYSIN
 k#054 cat > $SYSIN <</*
 k#055   REPRO INFILE(TEMPGLM) OUTFILE(ACNTMAS) RECORDSIZE(80)
 k#056 /*
 k#057 logmsg2 "Executing--> uvcp \"fili1=$TEMPGLM,typ=RSF,rcs=80,filo1=$ACNTMA..."
 k#058 #3----------------------------------------------------------------------
 k#059 uvcp "fili1=$TEMPGLM,typ=RSF,rcs=80,filo1=$ACNTMAS,typ=RSF,rcs=80";
 k#060 LCC=$?; ((SCC+=LCC)); ((JCC+=LCC));
 k#061 #4----------------------------------------------------------------------
 k#062 S0020C=$SCC; ((JCC+=SCC)); S0020R=1; alias goto="";
 k#063 if ((S0020C != 0))
 k#064    then logmsg2 "ERR: step#$JSTEP idcams abterm $SCC"
 k#065    alias goto="<<S9900=A"; fi
 k#066 goto
 k#067 fi  #ENDIF #J001(1) #IF (RC = 0) THEN #J001(1)

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

1G5. sample MVS JCL Conversions to Korn shell scripts

jgl360.jcl IDCAMS DEFINE CLUSTER - Create VSAM

 j#01 //JGL360   JOB  'TEST MVS JCL IDCAMS DEFINE CLUSTER CONVERSION'
 j#02 //* CREATE VSAM INDEXED FILE (INIT EMPTY FILE FOR RANDOM UPDATES)
 j#03 //STEP010  EXEC PGM=IDCAMS
 j#04 //SYSPRINT DD   SYSOUT=*
 j#05 //SYSIN    DD   *
 j#06    DELETE (GL.ACCOUNT.MASTER2) PURGE CLUSTER CATALOG (USERCAT5)
 j#07    DEFINE CLUSTER (NAME (GL.ACCOUNT.MASTER2) -
 j#08                    RECORDSIZE(80) -
 j#09                    KEYS(6 0) )
 j#10 /*
 j#11 //

See the 'uvcp' equivalent of IDCAMS listed on the next page --->

Most of the IDCAMS functions are not required for MicroFocus COBOL on Unix/Linux/Windows systems. For example 'DEFINE CLUSTER' was required by the mainframe to create a VSAM file, but MicroFocus COBOL can create VSAM files simply by 'OPEN OUTPUT'.

However the IDCAMS DEFINE CLUSTER is converted to 'uvcp' which will create an empty file, in case the IDCAMS step is followed by a COBOL program that expects to ADD/UPDATE records to an empty existing file. The uvcp will create the file with any indexed keys specified.

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

1G6. sample MVS JCL Conversions to Korn shell scripts

jgl360.ksh IDCAMS DEFINE CLUSTER converted to uvcp

The front end 11 lines & the back end 10 lines are omitted since they are the same for all jobs (except for jobname & any JCL comments).

 k#013 # * CREATE VSAM INDEXED FILE (INIT EMPTY FILE FOR RANDOM UPDATES)
 k#014 #1======================= begin step#S0010 IDCAMS ========================
 k#015 S0010=A
 k#016 stepctl51;  #calc StepTimes & check jobstop/goto end
 k#017 goto
 k#018 export JSTEP=S0010; ((XSTEP+=1)); SCC=0; LCC=0; alias goto="";
 k#019 logmsg2 "******** Begin Step $JSTEP idcams (#$XSTEP) ********"
 k#020 ##STEP010  EXEC PGM=IDCAMS
 k#021 export PROGID=idcams
 k#022 export PARM=""
 k#023 exportfile SYSPRINT $SYOT/${JOBID2}_${JSTEP}_SYSPRINT
 k#024 exportfile SYSIN $JTMP/${JSTEP}_${PROGID}_SYSIN
 k#025 cat > $SYSIN <</*
 k#026    DELETE (GL.ACCOUNT.MASTER2) PURGE CLUSTER CATALOG (USERCAT5)
 k#027    DEFINE CLUSTER (NAME (GL.ACCOUNT.MASTER2) -
 k#028                    RECORDSIZE(80) -
 k#029                    KEYS(6 0) )
 k#030 /*
 k#031 logmsg2 "Executing--> #rm -f data/gl.account.master2.dat"
 k#032 #3----------------------------------------------------------------------
 k#033 #rm -f data/gl.account.master2.dat
 k#034 #rm -f data/gl.account.master2.idx
 k#035 uvcp "fili1=ctl/nullfile,typ=RSF,rcs=80,filo1=data/gl.account.master2,typ=ISF\
 k#036 ,rcs=80,isk1=0(6)"
 k#037 LCC=$?; ((SCC+=LCC)); ((JCC+=LCC));
 k#038 #4----------------------------------------------------------------------
 k#039 S0010C=$SCC; ((JCC+=SCC)); S0010R=1; alias goto="";
 k#040 if ((S0010C != 0))
 k#041    then logmsg2 "ERR: step#$JSTEP idcams abterm $SCC"
 k#042    alias goto="<<S9900=A"; fi
 k#043 goto

Most of the IDCAMS functions are not required for MicroFocus COBOL on Unix/Linux/Windows systems. For example 'DEFINE CLUSTER' was required by the mainframe to create a VSAM file, but MicroFocus COBOL can create VSAM files simply by 'OPEN OUTPUT'.

However the IDCAMS DEFINE CLUSTER is converted to 'uvcp' which will create an empty file, in case the IDCAMS step is followed by a COBOL program that expects to ADD/UPDATE records to an empty existing file. The uvcp will create the file with any indexed keys specified.

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

1H1. Sample Conversion of MVS JCL to Unix/Linux Korn Shell Script

Deleting Files - Regular & GDG

IEFBR14 steps were often used to DELETE files. Here is a demo job to illustrate deleting files - both regular & GDG (all members of a generation file set).

jcl2/jgl500.jcl - demo file DELETEs

 j#01 //JGL500   JOB  'test DELETE files - regular & GDG (all members)'
 j#02 //STEP010  EXEC PGM=IEFBR14
 j#03 //ACTEXPT  DD   DSN=GL.ACCOUNT.EXPORT,DISP=(OLD,DELETE)
 j#04 //ACTLIST  DD   DSN=GL.ACCOUNT.ACNTLIST,DISP=(OLD,DELETE)

jcl3/jgl500.ksh - script equivalent

 k#013 #1======================= begin step#S0010 IEFBR14 ========================
 k#014 S0010=A
 k#015 stepctl51;  #calc StepTimes & check jobstop/goto end
 k#016 goto
 k#017 export JSTEP=S0010; ((XSTEP+=1)); SCC=0; LCC=0; alias goto="";
 k#018 logmsg2 "******** Begin Step $JSTEP iefbr14 (#$XSTEP) ********"
 k#019 ##STEP010  EXEC PGM=IEFBR14
 k#020 export PROGID=iefbr14
 k#021 export PARM=""
 k#022 exportfile  ACTEXPT data/gl.account.export
 k#023 exportgenall  ACTLIST data/gl.account.acntlist_
 k#024 logmsg2 "Executing--> #rm -f $ACTEXPT"
 k#025 #3----------------------------------------------------------------------
 k#026 #rm -f $ACTEXPT
 k#027 #rm -f ${ACTLIST}[0-9][0-9][0-9][0-9][0-9][0-9]
 k#028 #4----------------------------------------------------------------------
 k#029 :  # dummy step set cc 0 for status tests
 k#030 LCC=$?; S0010C=$LCC; ((SCC+=LCC)); ((JCC+=LCC)); S0010R=1; alias goto="";
 k#031 if ((S0010C != 0))
 k#032    then logmsg2 "ERR: step#$JSTEP iefbr14 abterm $SCC"
 k#033    alias goto="<<S9900=A"; fi
 k#034 goto

Regular file DELETE - JCL & script equivalent

j#03 //ACTEXPT DD DSN=GL.ACCOUNT.EXPORT,DISP=(OLD,DELETE)

k#022 exportfile ACTEXPT data/gl.account.export k#026 rm -f $ACTEXPT

GDG file DELETE - JCL & script equivalent

j#04 //ACTLIST DD DSN=GL.ACCOUNT.ACNTLIST,DISP=(OLD,DELETE)

 k#023 exportgenall ACTLIST data/gl.account.acntlist_
 k#027 rm -f ${ACTLIST}[0-9][0-9][0-9][0-9][0-9][0-9]

The Regular file delete is straitforward, but the GDG file delete deserves some explanation. How does the converter know that 'GL.ACCOUNT.ACNTLIST' is a GDG file ? - since it does not have the usual identifying suffix (0) (1).

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

1H2. Sample Conversion of MVS JCL to Unix/Linux Korn Shell Script

Control file to supply recsizes, ID GDG files, etc

Before the 1st JCL conversion, job 'jcldata51' reads thru all JCLs, extracting all file definitions, sorting,& dropping duplicates. An output file is written to 'ctl/datactl53I' which is read by the JCL converter as an Indexed file or stored in a memory table. The JCL converter can then lookup this file to determine which files are GDG & get record sizes, keys, etc if not in JCL.

Here are a few lines from the control file. You can see the entire test/demo file listed later on page '3F1'.

sample datajcl51

 #01 &&TEMPGLM                    cntf=0016 rca=00080 rcm=00080 typ=RSF src=Jr__________ job=jgl420 prg=COBOL1
 #02 AR.CUSTOMER.MASTER           cntf=0010 rca=00000 rcm=00000 typ=RSF src=J___________ job=jar100 prg=CAR100
 #03 AR.CUSTOMER.NAMEADRS.LIST100 cntf=0002 rca=00133 rcm=00133 typ=RSF src=Jr__________ job=jar109 prg=CAR100
 #04 GL.ACCOUNT.ACNTLIST(+1)      cntf=0001 rca=00133 rcm=00133 typ=RSF src=Jr__________ job=jgl100 prg=CGL100
 #05 GL.ACCOUNT.MASTER            cntf=0001 rca=00000 rcm=00000 typ=RSF src=J___________ job=jgl900 prg=IEFBR14
 #06 GL.ACCOUNT.MASTER(+1)        cntf=0014 rca=00080 rcm=00080 typ=RSF src=Jr__________ job=jgl420 prg=COBOL2
 #07 GL.ACCOUNT.MASTER(0)         cntf=0020 rca=00000 rcm=00000 typ=RSF src=J___________ job=jgl100 prg=CGL100
 #08 GL.ACCOUNT.MASTER2           cntf=0002 rca=00080 rcm=00080 typ=ISF src=Jk__________ job=jgl360 prg=IDCAMS key=(0,6)
 #09 GL.ACCOUNT.TRANS(+1)         cntf=0005 rca=00080 rcm=00080 typ=RSF src=Jr__________ job=jgl211 prg=SORT
 #10 PY.PARMS(PPY200S1)           cntf=0001 rca=00000 rcm=00000 typ=RSF src=J___________ job=jpy200 prg=SORT
 #11 PY.TIME.&DAY..&MONTH..&YEAR  cntf=0001 rca=00000 rcm=00000 typ=RSF src=J___________ job=jpy910 prg=IEFBR14
 #12 PYTEST.PAYROLL.MASTER        cntf=0006 rca=00200 rcm=00200 typ=ISF src=Jk__________ job=jpy400 prg=IDCAMS key=(0,8)

sample datajcl51 - right side (filename omitted)

 #01 rca=00080 rcm=00080 typ=RSF src=Jr__________ job=jgl420 prg=COBOL1
 #02 rca=00000 rcm=00000 typ=RSF src=J___________ job=jar100 prg=CAR100
 #03 rca=00133 rcm=00133 typ=RSF src=Jr__________ job=jar109 prg=CAR100
 #04 rca=00133 rcm=00133 typ=RSF src=Jr__________ job=jgl100 prg=CGL100
 #05 rca=00000 rcm=00000 typ=RSF src=J___________ job=jgl900 prg=IEFBR14
 #06 rca=00080 rcm=00080 typ=RSF src=Jr__________ job=jgl420 prg=COBOL2
 #07 rca=00000 rcm=00000 typ=RSF src=J___________ job=jgl100 prg=CGL100
 #08 rca=00080 rcm=00080 typ=ISF src=Jk__________ job=jgl360 prg=IDCAMS key=(0,6)
 #09 rca=00080 rcm=00080 typ=RSF src=Jr__________ job=jgl211 prg=SORT
 #10 rca=00000 rcm=00000 typ=RSF src=J___________ job=jpy200 prg=SORT
 #11 rca=00000 rcm=00000 typ=RSF src=J___________ job=jpy910 prg=IEFBR14
 #12 rca=00200 rcm=00200 typ=ISF src=Jk__________ job=jpy400 prg=IDCAMS key=(0,8)

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

1H3. Sample Conversion of MVS JCL to Unix/Linux Korn Shell Script

Control file to supply recsizes, ID GDG files, etc

Prior to May 2007, all GDG files defaulted to a system wide value for the number of generations maintained - unless you modified by coding 'gdg=..' in this control file for datafiles you wanted different from the default.

As of May 2007, an indexed file (ctl/gdgctl51I) now holds the 'gdg=..' info. This file is looked up by exportgen1 to get the gdg=.. value. This is a big improvement since you can make changes in 1 place to affect all references to each datafile.

See much more about the enhanced GDG system in 'Part_5' of this MVSJCL.doc.

Also note that ctl/datactl53I is used to determine references to an entire set of GDG files when there is no (0) or (+1) suffix on the reference, but the control file knows it is a GDG file from other references in the JCL. In this case the converter generates the 'exportgenall' function which concatenates all members of the file.

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

1I1. Sample Conversion of MVS JCL to Unix/Linux Korn Shell Script

IKJEFT01 - TSO Batch job for DB2

The mainframe required IKJEFT01 to execute COBOL programs that access DB2 tables. Microfocus COBOL on Unix/Linux/Windows(SFU) does not require this, so the converter retrieves the COBOL program name from the SYSTSIN control cards, and formats the cobrun command to execute the COBOL program directly.

jcl2/ikjeft01.jcl - demo IKJEFT01 conversion

 //IKJEFT01 JOB (MXP,WXS91),'sample job to demo IKJEFT01 conversion'
 //STEP0010 EXEC PGM=IKJEFT01,DYNAMNBR=20
 //SYSTSIN  DD  DSN=MXPLIB(IKJDEMO1),DISP=SHR
 //*note - for demo simplicity all files commented out except SYSTSIN
 //*SYSTSPRT DD  SYSOUT=&SYSOUT1
 //*SYSOUT,SYSPRINT,SYSABOUT,SYSDBOUT,SYSUDUMP,PRT(all similar SYSTSPRT)
 //*SXH      DD  DSN=MXP.PSXH.KSVSAM.MAST,DISP=SHR

parms/ikjdemo1 - SYSTSIN control cards for IKJEFT01

 DSN SYSTEM(DB2P)
 RUN PROGRAM(IKJPROG1) PLAN(IKJPROG1) LIB('MEPP.WXS91.LOADLIB')
 END

jcl3/ikjeft01.ksh - converted script

 k#013 #1======================= begin step#S0010 IKJEFT01 ========================
 k#014 S0010=A
 k#015 stepctl51;  #calc StepTimes & check jobstop/goto end
 k#016 goto
 k#017 export JSTEP=S0010; ((XSTEP+=1)); SCC=0; LCC=0; alias goto="";
 k#018 logmsg2 "******** Begin Step $JSTEP ikjeft01 (#$XSTEP) ********"
 k#019 ##STEP0010 EXEC PGM=IKJEFT01,DYNAMNBR=20
 k#020 export PROGID=car100
 k#021 export PARM=""
 k#022 exportfile  SYSTSIN $RUNLIBS/parms/ikjdemo1
 k#023 #2-------------------------- parms/ikjdemo1 ---------------------------
 k#024 # DSN SYSTEM(DB2P)
 k#025 # RUN PROGRAM(CAR100) PLAN(IKJPROG1) LIB('MEPP.WXS91.LOADLIB')
 k#026 # PARMS('parmsdata added on IKJEFT01 demo Aug28/07')
 k#027 # END
 k#028 export PARM="parmsdata added on IKJEFT01 demo Aug28/07"
 k#029 logmsg2 "Executing--> cobrun $ANIM $RLX/car100"
 k#030 #3----------------------------------------------------------------------
 k#031 cobrun $ANIM $RLX/car100
 k#032 #4----------------------------------------------------------------------
 k#033 LCC=$?; S0010C=$LCC; ((SCC+=LCC)); ((JCC+=LCC)); S0010R=1; alias goto="";
 k#034 if ((S0010C != 0))
 k#035    then logmsg2 "ERR: step#$JSTEP ikjeft01 abterm $SCC"
 k#036    alias goto="<<S9900=A"; fi
 k#037 goto

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

1J1. Sample Conversion of MVS JCL to Unix/Linux Korn Shell Script

FTP test/demo conversion

After converting the test/demo JCL, you can run the converted script. The demo JCL specifies TCP/IP adrs as '127.0.0.1' which is the unix/linux host. The demo assumes you have setup test users mvstest/vsetest and FTP's from 'mvstest' & logs in the 'vsetest' on the same machine.

FTP demo JCL - jcl0/FTPPUT1.jcl

 //FTPPUT1  JOB 'test FTP conversion'
 //FTPSTEP1 EXEC PGM=FTP,PARM='127.0.0.1'
 //INPUT    DD   *
 vsetest vsetest00
 put GL.ACCOUNT.TRANS(0)            <-- Note - GDG files are handled
 quit
 /*

converted JCL/script - jcl3/ftpput1.ksh

 k#013 #1======================= begin step#S0010 FTP ========================
 k#014 S0010=A
 k#015 stepctl51;  #calc StepTimes & check jobstop/goto end
 k#016 goto
 k#017 export JSTEP=S0010; ((XSTEP+=1)); SCC=0; LCC=0; alias goto="";
 k#018 logmsg2 "******** Begin Step $JSTEP ftp (#$XSTEP) ********"
 k#019 ##FTPSTEP1 EXEC PGM=FTP,PARM='127.0.0.1'
 k#020 export PROGID=ftp
 k#021 export PARM="127.0.0.1"
 k#022 exportfile INPUT1 $JTMP/${JSTEP}_${PROGID}_INPUT1
 k#023 cat > $INPUT1 <</*
 k#024 mvstest mvstest00
 k#025 cd testdata
 k#026 binary
 k#027 put GL.ACCOUNT.TRANS(0)
 k#028 quit
 k#029 /*
 k#030 exportgen0 0 FTPPUT01 data/gl.account.trans_
 k#031 exportfile FTPTMP2 $JTMP/${JSTEP}_${PROGID}_FTPTMP2
 k#032 cat > $FTPTMP2 <</*FTP2
 k#033 open 127.0.0.1
 k#034 user mvstest mvstest00
 k#035 cd testdata
 k#036 binary
 k#037 put $FTPPUT01
 k#038 quit
 k#039 /*FTP2
 k#040 logmsg2 "Executing--> ftp -i -n -u -v <$FTPTMP2"
 k#041 #3----------------------------------------------------------------------
 k#042 ftp -i -n -u -v <$FTPTMP2
 k#043 #4----------------------------------------------------------------------
 k#044 LCC=$?; S0010C=$LCC; ((SCC+=LCC)); ((JCC+=LCC)); S0010R=1; alias goto="";
 k#045 if ((S0010C != 0))
 k#046    then logmsg2 "ERR: step#$JSTEP ftp abterm $SCC"
 k#047    alias goto="<<S9900=A"; fi
 k#048 goto

 ftpdemo1.ksh   <-- execute FTP demo (after conversion)
 ============     - see console log on the next page

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

1J2. Sample Conversion of MVS JCL to Unix/Linux Korn Shell Script

console log from FTP test/demo

 090314:135607:FTPPUT1: Begin Job=FTPPUT1
 090314:135607:FTPPUT1: /home/mvstest/testlibs/jcls/ftpput1.ksh
 090314:135607:FTPPUT1: Arguments:
 090314:135607:FTPPUT1: RUNLIBS=/home/mvstest/testlibs
 090314:135607:FTPPUT1: RUNDATA=/home/mvstest/testdata
 090314:135607:FTPPUT1: JTMP=/home/mvstest/testdata/jobtmp/FTPPUT1 SYOT=/home/mvstest/testdata/sysout/FTPPUT1
 090314:135607:FTPPUT1: RUNDATE=20090314
 090314:135607:FTPPUT1: ******** Begin Step S0010 ftp (#1) ********
 090314:135607:FTPPUT1: file: INPUT1=/home/mvstest/testdata/jobtmp/FTPPUT1/S0010_ftp_INPUT1 bytes=66
 090314:135607:FTPPUT1: EOF fili01 rds=5 size=120: /home/mvstest/testdata/jobtmp/FTPPUT1/gtmp/0010I_gl_account.trans_
 090314:135607:FTPPUT1: EOF filr01 rds=1 upds=1 size=10240: /home/mvstest/testlibs/ctl/gdgctl51I
 090314:135607:FTPPUT1: EOF filo02 wrts=1 size=51: /home/mvstest/testdata/jobtmp/FTPPUT1/gtmp/0010G0_gl_account.trans_
 090314:135607:FTPPUT1: gen0: FTPPUT01=data/gl.account.trans_000005 insize=1600
 090314:135607:FTPPUT1: file: FTPTMP2=/home/mvstest/testdata/jobtmp/FTPPUT1/S0010_ftp_FTPTMP2 bytes=
 090314:135607:FTPPUT1: Executing--> ftp -i -n -u -v </home/mvstest/testdata/jobtmp/FTPPUT1/S0010_ftp_FTPTMP2
 Connected to 127.0.0.1.
 220 (vsFTPd 2.0.5)
 331 Please specify the password.
 230 Login successful.
 250 Directory successfully changed.
 200 Switching to Binary mode.
 local: data/gl.account.trans_000005 remote: data/gl.account.trans_000005
 550 Permission denied.
 Passive mode refused.  Turning off passive mode.
 200 PORT command successful. Consider using PASV.
 150 Ok to send data.
 226 File receive OK.
 1600 bytes sent in 4.5e-05 seconds (3.5e+04 Kbytes/s)
 221 Goodbye.
 090314:135607:FTPPUT1: Job Times: Begun=13:56:07 End=13:56:07 Elapsed=00:00:00
 090314:135607:FTPPUT1: EOF filr01 rds=5 size=10240: /home/mvstest/testlibs/ctl/gdgctl51I
 090314:135607:FTPPUT1: JobEnd=Normal, StepsExecuted=1, LastStep=S0010

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

1K1. Sample Conversion of MVS JCL to Unix/Linux Korn Shell Script

MAILSMTP.jcl

j#001 //MAILSMTP JOB 'test/demo SMTP MAIL convert to sendmail' j#003 //STEP010 EXEC PGM=IEBGENER j#004 //SYSUT2 DD SYSOUT=(B,SMTP) j#005 //SYSUT1 DD * j#006 TO: appsadm j#007 FROM: mvstest j#008 SUBJECT: testing SMTP/sendmail to other unix logins j#009 j#010 Hello: appsadm, sending this mail from batch job MAILSMTP (a test) j#011 Note: the blank line between SUBJECT: & message is mandatory j#012 Similar mail might be used to alert you of problems in batch jobs ? j#013 This mail from 1 unix login to another unix login j#014 Not sure if we can send to an internet email address yet ? j#015 (may need to install more software ?) j#016 /*

2H2. mailsmtp.ksh

 k#013 #1======================= begin step#S0010 IEBGENER ========================
 k#014 S0010=A
 k#015 stepctl51;  #calc StepTimes & check jobstop/goto end
 k#016 goto
 k#017 export JSTEP=S0010; ((XSTEP+=1)); SCC=0; LCC=0; alias goto="";
 k#018 logmsg2 "******** Begin Step $JSTEP iebgener (#$XSTEP) ********"
 k#019 ##STEP010  EXEC PGM=IEBGENER
 k#020 export PROGID=iebgener
 k#021 export PARM=""
 k#022 exportfile SYSUT2 $SYOT/${JOBID2}_${JSTEP}_SYSUT2
 k#023 exportfile SYSUT1 $JTMP/${JSTEP}_${PROGID}_SYSUT1
 k#024 cat > $SYSUT1 <</*
 k#025 TO: appsadm
 k#026 FROM: mvstest
 k#027 SUBJECT: testing SMTP/sendmail to other unix logins
 k#028
 k#029 Hello: appsadm, sending this mail from batch job MAILSMTP (a test)
 k#030 Note: the blank line between SUBJECT: & message is mandatory
 k#031 Similar mail might be used to alert you of problems in batch jobs ?
 k#032 This mail from 1 unix login to another unix login
 k#033 Not sure if we can send to an internet email address yet ?
 k#034 (may need to install more software ?)
 k#035 /*
 k#036 logmsg2 "Executing--> sendmail -t <$SYSUT1"
 k#037 #3----------------------------------------------------------------------
 k#038 sendmail -t <$SYSUT1
 k#039 #4----------------------------------------------------------------------

 mailsmtp.ksh     <-- execute (as mvstest)
 Login appsadm    <-- Login as appsadm (mail addressee)
 mail             <-- read mail (sent from mvstest)

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

1K2. Sample Conversion of MVS JCL to Unix/Linux Korn Shell Script

converting mainframe 'MAILTOLN' to 'mutt'

Here are listings of mainframe MAILTOLN & the converted 'mutt' JCL/script, that you can run after conversion.

test/demo JCL - jcl0/MAILDEMO.jcl

 //MAILDEMO JOB  'test/demo MAIL conversion to linux mutt'
 //* demo conversion of mainframe 'MAILTOLN' to linux 'mutt'
 //STEP010  EXEC PGM=MAILTOLN
 //PARMFILE DD *
 TO: uvadm
 SUBJECT: current generation of GL.ACCOUNT.TRANS file attached
 //MAIL   DD  DISP=SHR,DSN=GL.ACCOUNT.TRANS(0)

converted JCL/script - jcl3/maildemo.ksh

 #1======================= begin step#S0010 MAILTOLN ========================
 S0010=A
 JSTEP=S0010; ((XSTEP+=1)); SCC=0; LCC=0; alias goto="";
 logmsg1 "Begin Step $JSTEP mailtoln (#$XSTEP)"
 stepctl51;  #calc StepTimes & check jobstop/goto end
 goto
 ##STEP010  EXEC PGM=MAILTOLN
 export PROGID=mailtoln
 export PARM=""
 PARMFILE=$JTMP/${JSTEP}_${PROGID}_PARMFILE
 cat > $PARMFILE <</*
 TO: uvadm
 SUBJECT: current generation of GL.ACCOUNT.TRANS file attached
 /*
 exportfile PARMFILE $PARMFILE
 exportgen0 +1 MAIL data/gl.account.trans_       #<--NOTE: GDG file attachment
 #3----------------------------------------------------------------------
 mutt -s "current generation of GL.ACCOUNT.TRANS file attached"\
      -a $MAIL uvadm <$PARMFILE
 #4----------------------------------------------------------------------

 maildemo.ksh      <-- execute test/demo JCL/script (after conversion)
 ============

This demo JCL/script assumes you will be logged in as 'mvstest' & will mail to user 'uvadm'. Note the attachment is '$MAIL' which is a GDG file defined by 'exportgen0'. It is addressed in subdir 'gl/' since all JCL/scripts call function 'jobset51' (on line 10 not shown here) which changes directory to $RUNDATA. RUNDATA will be /home/mvstest/testdata/ if logged in as mvstest using the profile listed at ADMjobs.htm#1C1.

See the resulting 'mbox' for 'uvadm' listed on the next page.

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

1K3. Sample Conversion of MVS JCL to Unix/Linux Korn Shell Script

mbox result from maildemo.ksh

From mvstest@uvsoft3.uvsoft.ca Mon Jul 30 13:11:42 2007 Return-Path: <mvstest@uvsoft3.uvsoft.ca> Received: from uvsoft3.uvsoft.ca (uvsoft3.uvsoft.ca [127.0.0.1]) by uvsoft3.uvsoft.ca (8.12.10/8.12.10) with ESMTP id l6UKBgdd009858 for <uvadm@uvsoft3.uvsoft.ca>; Mon, 30 Jul 2007 13:11:42 -0700 Received: (from mvstest@localhost) by uvsoft3.uvsoft.ca (8.12.10/8.12.10/Submit) id l6UKBf1U009856 for uvadm@localhost.localdomain; Mon, 30 Jul 2007 13:11:41 -0700 Date: Mon, 30 Jul 2007 13:11:41 -0700 From: MVSTEST <mvstest@uvsoft3.uvsoft.ca> To: UVADM <uvadm@uvsoft3.uvsoft.ca> Subject: current generation of GL.ACCOUNT.TRANS file attached Message-ID: <20070730201141.GA9851@localhost.localdomain> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="Kj7319i9nmIyA2yE" Content-Disposition: inline User-Agent: Mutt/1.4.1i Status: RO

--Kj7319i9nmIyA2yE Content-Type: text/plain; charset=us-ascii Content-Disposition: inline

TO: uvadm SUBJECT: current generation of GL.ACCOUNT.TRANS file attached

--Kj7319i9nmIyA2yE Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="account.trans_000005"

 00011100T Bank Fee                      000000100} 1234BJ      040428
 00011100T EMJ Sony Tape Drive           000012314J 1234BC000871040428
 00011100T Telephone                     000000559Q 1234BC000882040428
 00011100T FEDEX                         000000109J 1234BC000870040428
 00011100T VISA payment                  000040000} 1234BC000884040428
 00011100T Staples office supplies       000001227N 1234BC000874040428
 00011100T Datex office rent             000003210} 1234BC000885040428
 00011200T VISA payment                  0000400000 1234BC000884040428
 00011200T Dollar rent a car             000014177O 1234VS      040428
 00033700T EMJ Sony Tape Drive           0000008056 1234BC000871040428
 00033700T Telephone                     0000000344 1234BC000882040428
 00033700T FEDEX                         0000001091 1234BC000870040428
 00033700T Staples office supplies       0000000754 1234BC000874040428
 00033700T Datex office rent             0000002100 1234BC000885040428
 00061500T EMJ Sony Tape Drive           0000115085 1234BC000871040428
 00062200T Staples office supplies       0000011521 1234BC000874040428
 00063300T Dollar rent a car             0000141776 1234VS      040428
 00074100T Bank Fee                      0000001000 1234BJ      040428
 00075100T Datex office rent             0000030000 1234BC000885040428
 00075300T Telephone                     0000005254 1234BC000882040428

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

1L1. Sample Conversion of MVS JCL to Unix/Linux Korn Shell Script

ISRSUPC conversion to 'cmp' & 'uvcmp'

The 'ISRSUPC' (SUPERC) file comparison utility is converted to unix/linux 'cmp' and to the Vancouver Utility 'uvcmp1' utilties.

'cmp' is used to set the condition code for any following 'IF', often the only purpose of the ISRSUPC step. 'uvcmp' creates a report in SYSOUT in case you do need the file comparison report (see sample report on the next page).

Here are listings of the JCL (ISRSUPC.jcl) & converted script (isrsupc1.ksh) provided to demo SUPERC conversion (relevant lines only).

test/demo jcl0/ISRSUPC1.jcl

 //ISRSUPC1 JOB 'test ISRSUPC (file compare) July 2007'
 //STEP010 EXEC PGM=ISRSUPC,PARM=(CHNGL,LINECMP,'','')
 //NEWDD  DD DSN=GL.ACCOUNT.TRANS(0),DISP=SHR         <-- GDG current generation
 //OLDDD  DD DSN=GL.ACCOUNT.TRANS(-1),DISP=SHR        <-- GDG previous generation
 //OUTDD  DD SYSOUT=(A)
 //SYSIN  DD *
 CMPCOLM 1:80
 DPLINE  'HDR1',1
 /*
 // IF STEP010.RC=0 THEN
 // ...................

converted to cmp/uvcmp - jcl3/isrsupc.ksh

 exportgen0 0 NEWDD data/gl.account.trans_          #<-- GDG current generation
 exportgen0 -1 OLDDD data/gl.account.trans_         #<-- GDG previous generation
 exportfile OUTDD $SYOT/${JSTEP}_OUTDD_A
 #3----------------------------------------------------------------------
 uvcopy uvcmp1,fili1=$OLDDD,fili2=$NEWDD,filo3=$OUTDD,rop=r0,uop=q0s5r80
 #NB - ISRSUPC conversion sets condition (via cmp below) for following IF
 #   - uvcopy uvcmp1 above creates SYSOUT/OUTDD report
 #   - need to modify record size 'r80' in uop=q0s5r80 above
 #   - any CMPCOLM & DPLINE ignored as of July 2007
 cmp $OLDDD $NEWDD
 #4----------------------------------------------------------------------
 LCC=$?; S0010C=$LCC; ((SCC+=LCC)); ((JCC+=LCC)); S0010R=1; alias goto="";
 if ((S0010C == 0)); then  # IF STEP010.RC=0 THEN #J001(1)
    ..................................................

You might not need to modify the converted JCL/script, if the only purpose was to set the condition code for al following 'IF' statement.

If you want the 'uvcmp' report, you will need to correct the record size option from the default 'r80' (at the end of the 'uvcopy uvcmp1' line above),

'CMPCOLM' & 'DPLINE' are not yet supported as of July 2007.

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

1L2. Sample Conversion of MVS JCL to Unix/Linux Korn Shell Script

demo ISRSUPC conversion - sample report

After converting the test/demo JCLs, you can run the 'isrsupc1.ksh' demo script as follows & you should get the report listed below:

 isrsupc1.ksh       <-- execute the ISRSUPC test/demo provided
 ============         - output report (in SYSOUT) shown below:

 uvcmp1 - compare 2 files "*" diffs (uops=q1e0p30r256s5t500000v2x0q0s5r80)
 recsize  reccount   file-size  typ  filename sysout/ISRSUPC1/S0010_OUTDD_A
 1:   80        20       1,600  RSF  data/gl.account.trans_000004
 2:   80        20       1,600  RSF  data/gl.account.trans_000005
 2007/07/30_08:29:54   1         2         3         4         5         6
 f#rec#byte# 0123456789012345678901234567890123456789012345678901234567890123
 ============================================================================

 1    3    0 00011100T Telephone XX                  000000559Q 1234BC0008820
             3333333352566676666255222222222222222222333333333523333443333333
             000111004045C508FE5088000000000000000000000000559101234230008820
                                 **
          64 40499          ^
             3333322222222220
             404990000000000A
                **

 2    3      00011100T Telephone                     000000559Q 1234BC0008820
             3333333352566676666222222222222222222222333333333523333443333333
             000111004045C508FE5000000000000000000000000000559101234230008820
                                 **
          64 40428          ^
             3333322222222220
             404280000000000A
                **

 2007/07/30_08:29:54   1         2         3         4         5         6
 f#rec#byte# 0123456789012345678901234567890123456789012345678901234567890123
 ============================================================================

 1   18    0 00074100T Bank Fee XX                   0000001099 1234BJ      0
             3333333352466624662552222222222222222222333333333323333442222223
             000741004021EB065508800000000000000000000000001099012342A0000000
                                **                           **
          64 40428          ^
             3333322222222220
             404280000000000A

 2   18      00074100T Bank Fee                      0000001000 1234BJ      0
             3333333352466624662222222222222222222222333333333323333442222223
             000741004021EB065500000000000000000000000000001000012342A0000000
                                **                           **
          64 40428          ^
             3333322222222220
             404280000000000A

 ======================= EOF or stop count reached ==========================
 Total=000020,read=000020,mismatches=000002,stop=000005,term=500000

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

1P1. Converting Test/Demo JCL to Unix/Linux scripts

Preparations for JCL test/demo conversions

Here are the preparations required for you to run the conversions for the supplied test/demo JCLs, some of which have been listed previously beginning on page '1C1'. The operating Instructions for your own JCL conversions will be presented later in Part_4. We recommend you perform the following before proceeding.

 #1. Install the Vancouver Utilities as documented in install.htm.

 #2. Download & installed the Korn shell from http://www.kornshell.com
     if not supplied with your system or if it is the old 1988 version (vs 1993).
     We recommend 'bash' for interactive use, but 'ksh' is better for batch
     scripts. The JCLs are converted for the Korn shell (1st line #!/bin/ksh).

 #3. Setup 'appsadm' & modify profiles as documented in Part 1 of ADMjobs.htm.

You must have installed the Vancouver Utilities, you must have the Korn shell, and we highly recommend setting up 'appsadm' & modifying the profiles, as instructed in ADMjobs.htm.

If desired you could delay setting up 'appsadm' & performing the actions in ADMjobs.htm, until you complete the test/demos here in Part 1 (of MVSJCL.doc), and are ready to begin your own conversions in Part_4.

setup 'mvstest' - plan/overview

1. Setup a user login account for the test/demo. Please make it 'mvstest' so the test/demo conversions will work without having to modify any control files (profile, jobset51, jclunixop5, etc). We recommend the 'bash' shell if available, else specify 'ksh'.
   
   
2. Copy the supplied profile (from /home/uvadm/env/stub_profile) to the unix/linux system profile (/home/mvstest/.bash_profile). See instructions at the beginning of the supplied profile listed at ADMjobs.htm#1C1.
   
   
3. Modify the supplied profile appropriately for your Unix/Linux site. If you have followed the recommendations so far, I think the only changes required (for the test/demos) is to define your laser printer & modify COBDIR (depending on where you installed COBOL).
   
   

   alternative - setup demo files in your homedir

If you prefer or if there are multiple programmers at your site who wish to perform these demos, you can setup the 'testlibs' & 'testdata' subdirs in your own homedir & copy the supplied demo files to them.

See alternative setup in your homedir on page '1P4' --->

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

1P2. Converting Test/Demo JCL to Unix/Linux scripts

setup 'mvstest' - Op. Instrns

The following instructions presume the 'bash' profile. If you do not have bash, please see the alternatives for 'ksh' in Part 1 of ADMjobs.htm.

 #1. login as 'root'

 #2. groupadd apps        <-- setup group 'apps', if not already setup
     =============            (when uvadm was setup in install.htm)

 #3. useradd -m -g apps -s /bin/bash mvstest  <-- setup 'mvstest' for bash
     =======================================

 #3a. useradd -m -g apps -s /bin/ksh mvstest  <-- alternative for 'ksh'
      ======================================

 #4. passwd mvstest    <-- set password for mvstest
     ==============

 #5. cp -p /home/uvadm/env/stub_profile /home/mvstest/.bash_profile
     ==============================================================
     - copy supplied 'stub' profile to mvstest homedir & rename for bash

 #5a. cp -p /home/uvadm/env/stub_profile /home/mvstest/.profile
      =========================================================
      - alternative if you are using 'ksh' (vs bash)

 #6. vi /home/uvadm/common_profile        <-- modify common_profile
     =============================

      export COBDIR=/opt/microfocus/cobol <-- change COBDIR for your site
      ===================================
      export UVLPDEST="-dlp0"             <-- change 'lp0' to your laser printer
      =======================
      export UVLPDEST="-dLPT1"            <-- for Windows SFU
      =======================

 #7. Logout of Root & login as 'mvstest', on the next page --->

You should realize that the above are the minimum setups for mvstest & not the most efficient method if you later proceed to setup your own additional programmers & operators. Setting up 'appsadm' & modifying the profiles as described in Part 1 of ADMjobs.htm is more efficient because you would avoid duplication.

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

1P3. Converting Test/Demo JCL to Unix/Linux scripts

copy demo files to your mvstest home dir

 #1. login: mvstest --> /home/mvstest
     ================================

 #2. cp -r /home/uvadm/mvstest/* /home/mvstest
     =========================================
     - copy supplied test/demo files from uvadm to mvstest home dir

       /home/mvstest should now contain the subdirs & files listed on page '1A1'.
       The more relevant subdirs for the JCL conversions are:
       ctl, parm0, parms, proc0, procs, jcl0, jcl1, jcl2,& jcl3.

scripts for your own conversions (vs test/demos)

If you later want to create these subdirs for your own use (without demo files) you can use the the following scripts. You might set them up in your home dir or you might create another user (mvstest2, etc).

 #1. Login as yourself or vsetest2, etc --> homedir

 #2. vsetestdirs   <-- create conversion superdirs (testlibs, testdata, cnvdata)
     ===========

 #3a. cdl --> alias 'cd $RUNLIBS' --> $HOME/testlibs/

 #3b. vselibsdirs  <-- create empty set of testlibs (cbl0,cbl1,etc)
      ===========

 #3c. vsetestlibsinit  <-- clear testlibs subdirs for retesting
      ===============    - cbl1,cbl2,cbls, jcl1,jcl2,jcl3,jcls, etc
                         - not the '0' subdirs or ctl/...

 #4a. cdd --> alias 'cd $RUNDATA' --> $HOME/testdata/

 #4b. vsedatadirs  <-- create empty set of testdata subdirs (ar,gl,jobtmp,etc)
      ===========

 #4c. testdatainit      <-- clear testdata subdirs for retesting
      ============       - jobtmp, joblog, tmp, wrk, rpts, etc
                         - not the master data in ar, gl, mstr, tape, etc

converting your own JCL ? (vs test/demos)

We strongly recommend you 1st work thru these test/demos before trying to convert your own JCL & then to study Part_4 carefully before attempting to convert your own JCL.

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

1P4. Converting Test/Demo JCL to Unix/Linux scripts

shortcuts to convert your own JCL ? (vs test/demos)

We strongly recommend you 1st work thru these test/demos before trying to convert your own JCL & then to study Part_4 carefully before attempting to convert your own JCL.

BUT see page '1X1', if you need to do a quick preliminary conversion of a few of your JCLs before you invest the time & effort that should be expended when you launch your mainframe conversion project.

Page '1X2' shows you how to use the scripts above & also 'jcl2ksh51A' to perform all steps of JCL conversion.

BUT again, we strongly recommend you first use the step by step method (here in Part 1) to better understand the process.

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

1P5. Converting Test/Demo JCL to Unix/Linux scripts

alternative - setup demo files in your homedir

The previous pages setup userid 'mvstest' & copied the test/demo files to the mvstest homedir, in preparation for the JCL demo conversions documented on the following pages.

If you prefer or if there are multiple programmers at your site who wish to perform these demos, you can setup the 'testlibs' & 'testdata' subdirs in your own homedir & copy the supplied demo files to them.

If you do not already have a login, see ADMjobs.htm#Part_1 to setup your account & copy the supplied 'stub_profile' to your homedir.

The following assumes you already have a login, but it has not yet been updated with the 'stub_profile' required to perform the JCL conversions.

 #1. Login as youself --> your homedir
     ================

 #2. vi .bash_profile    <-- edit your .bash_profile for Linux bash shell
     ================      - OR .profile for Unix Korn shell

 #2a. G                  <-- Go to the end of your existing profile
      ===

 #2b. :r /home/uvadm/env/stub_profile
      ===============================
      - read supplied stub_profile onto the end of your existing profile

 #3. logout & log back in   <-- to activate the new profile
     ====================

 #4. mkdir testlibs testdata  <-- make subdirs within your homedir
     =======================      to receive the supplied demo files

 #5. cp -r /home/uvadm/mvstest/testlibs/* testlibs
     =============================================
     - copy supplied demo libraries to testlibs/... in your homedir
       (JCL,COBOL,etc)

 #6. cp -r /home/uvadm/mvstest/testdata/* testdata
     =============================================
     - copy supplied demo data-files to testdata/... in your homedir

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

1Q1. Converting Test/Demo JCL to Unix/Linux scripts

JCL conversion overview

These operating instructions will convert all files in a directory, outputting to a 2nd directory. The instructions for all files are actually simpler than for 1 file at a time & almost as fast (especially for the test/demo files). Some instructions such as the PROC expansion only work with all files in the directory.

script to perform all JCL conversion steps

'jcl2ksh51A' will perform all steps of the JCL conversion - the same as the 'step by step' procedures documented on pages 1Q2 thru 1Q5. The script is easier than the step by step method, but you might not gain as much understanding.

You should use the 'step by step' method the 1st time you convert your own JCL (as documented in Part_4), because you will be able to detect & fix problems that may occur in your JCL conversions (vs the proven test/demos here in Part 1).

jcl2ksh51A procedures illustrated

 jcl0 -------> jcl1 --------------> jcl2 -------------> jcl3 ------------> jcls
      cleanup       PROC/SLI expand      convert to ksh      manual copy

 proc0 -------> procs     parm0 -------> parms
       cleanup                 cleanup

 #1. jcl2ksh51A all    <-- convert JCL thru all steps, as illustrated above
     =============      - reply null (take default) at all prompts
                        - or reply 'y' for prompts that demand a y/n response

 #2. cp jcl3/* jcls   <-- copy JCL/scripts to jcls (in PATH)
     ==============     - ONLY for the test/demos here in Part 1
                        - since they have already been tested & debugged

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

1Q2. Converting Test/Demo JCL to Unix/Linux scripts

step by step JCL conversion

The next few pages document the 'step by step' procedures for JCL conversion (vs the jcl2ksh51A 'script' documented on the previous page).

It is much easier to use the jcl2ksh51A script than the step by step procedures, but you might not get as much understanding from it.

You should use the 'step by step' method the 1st time you convert your own JCL (as documented in Part_4), because you will be able to detect & fix problems that may occur in your JCL conversions (vs the proven test/demos here in Part 1).

step by step JCL conversion procedures

cleanup mainframe JCL, PROCs,& Control Cards

The 1st 3 procedures will cleanup the demo mainframe code, clearing cols 73-80, translating filenames to lower case,& assigning filename extensions (.jcl or .proc or nothing).

 #1a. uvcopyx cleanup jcl0 jcl1 uop=q0i7g8n1,arg1=.jcl  <-- cleanup mainframe JCL
      ================================================
      - strip any CR's, clear cols 73-80,& shorten back to last nonblank
      - ensure output filenames are translated to lower case
      - assign filename extension '.jcl'

 #1b. uvcopyx cleanup proc0 procs uop=q0i7g8n1,arg1=.proc  <-- cleanup PROCs
      ===================================================
      - strip any CR's, clear cols 73-80,& shorten back to last nonblank
      - ensure output filenames are translated to lower case
      - assign filename extension '.proc'

 #1c. uvcopyx cleanup parm0 parms uop=q0i7g8n5 <-- control cards & includes
      ========================================
      - strip any CR's, clear cols 73-80,& shorten back to last nonblank
      - ensure output filenames are translated to lower case
      - includes combined with parms (include0/include1 subdirs dropped May2006)

expand PROCs in all JCL

 #2.  jclpx51 jcl1 jcl2 procs parms
      =============================
      - copy all jcl from jcl1 to jcl2, expanding PROCs & including INCLUDEs
      - 'jclpx1' is a script that calls the 'jclproc51' utility for each file
        found in the directory

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

1Q3. Converting Test/Demo JCL to Unix/Linux scripts

Creating the DataFile Info control file

 #3.  jcldata5A all  <-- generate datafile info control file for JCL converter
      =============
      - extracts datafilenames from all JCL, sorts, & drops duplicates
      - collects file info (record sizes, file types, key locations/lengths, etc)
      - encoding on keywords (rca=... typ=... key=...) on right side of filename
      - combines with other file info (LISTCAT, Excel spreadsheets, etc)
      - loads Indexed file 'datactl53I' for look up by JCL converter

'jcldata5A' reads all JCL & gathers datafile info for use by the JCL converter. Record sizes, indexed keys, etc are collected onto 1 entry per unique datafilename. See sample ctl/datactl53 listed on page '3F5'.

The Datafile Info control file is vital to conversions of your JCL, but we can delay these considerations until Part_4 where we discuss conversions of 'YOUR' JCL versus the test/demo JCL conversions illustrated here in Part 1.

For the JCL converter test/demos here in Part 1, you can just run 'jcldata5A' to create 'datactl53I' used by the JCL converter. In Part 4, we will explain how you would create datactl53I for your own JCL conversions from up to six sources.

1. datajcl51/52 - datafile info extracted from all JCL - this is the only mandatory datafile info source - create null files for any files below not available
   
   
2. datacat51/52 - datafile info extracted from LISTCAT (mainframe report) - optional, if absent create null file >ctl/datacat52
   
   
3. dataxl151/52 - datafile info extracted from Excel spreadsheet #1 - optional, if absent create null file >ctl/dataxl152
   
   
4. dataxl251/52 - datafile info extracted from Excel spreadsheet #2 - optional, if absent create null file >ctl/dataxl252
   
   
5. dataedt52 - datafile info created manually with editor - may supply info not available from other 5 sources - optional, if absent create null file >ctl/dataedt52
   
   
6. datacnv51/52 - datafile info created by scanning the EBCDIC datafiles - currently indicates only if packed/binary fields present - optional, if absent create null file >ctl/datacnv52
   

Note that we have supplied some sample data in most of these files that you can see in /home/uvadm/mvstest/ctl/... or /home/mvstest/testlibs/ctl (if you followed test/demo setup instructions begining on page '1P1'.

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

1Q4. Converting Test/Demo JCL to Unix/Linux scripts

Modifying JCL conversion options - unix/linux

Before you run the actual JCL/script conversion (step #5 on the next page), you may need to modify the options in the control file ctl/jclunixop51. See the sample JCL options control file listed on page '3E1'.

You will not have to modify for these test/demos (here in Part 1), but you may need to modify options for your own JCL conversions (documented in Part 4).

Modifying JCL conversion options - Windows

If you are using Windows SFU, Cygwin, or Uwin, you must change option 'r' in the control file (ctl/jclunixop5), before you run the JCL converter. See the control file listed on page '3E1' further ahead.

You must change option 'r0' to 'r1' on line 1 of ctl/jclunixop5. The control file is supplied with option 'r0' to generate 'cobrun' for MicroFocus COBOL Server Express on Unix/Linux systems. 'r1' will cause the converter to generate 'cobw' which is the equivalent for MicroFocus COBOL Net Express on Windows.

 #4. vi ctl/jclunixop51        <-- edit change only for Windows SFU/Cygwin/Uwin
     ==================

 jclunixop5:d0g10j1n0p0r0u1x0y0  #<-- option defaults for JCL converter
 ======================r1======   <-- change r0 to r1

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

1Q5. Converting Test/Demo JCL to Unix/Linux scripts

Convert ALL JCLS in directory

 #5. jclxx51 jcl2 jcl3    <-- convert all JCL in jcl2 to scripts in jcl3
     =================

'jclxx51' is a script that executes the 'jclunix51' conversion program for each file found in input subdir & copy results to output subdir.

jclxx51 requires control files: ctl/jclunixop5, ctl/datactl53I, parms/... The control files may need changes. See discussion on the next page.

 #6. vi jcl3/*           <-- investigate your results
     =========

Your results should match those listed previously. For example the original JCL for the first demo job (jar100.jcl) is listed on page '1C1', and the expected results (jar100.ksh) are listed on page '1C2'.

Before you can execute the sample jobs, you must convert & compile the COBOL programs as shown begining on page '1R1'. Then see the script executions starting on page '1S1'.

copy converted scripts to execution subdir

 #7. cp jcl3/* jcls      - copy all converted JCL/scripts to subdir jcls
     ==============        (since jcls is in the PATH, but not jcl3)

1. If you need to reconvert (after improving tables in jclunixop5), the converter converts all JCL from jcl2 to jcl3 (never to jcls). Then you will manually copy desired jobs from 'jcl3' to 'jcls'.
   
   
2. This protects you from destroying jobs in 'jcls', which may have had considerable effort invested in debugging & manual improvements.
   
   
3. Copying 1 job at a time as we test/debug also provides with a means to track our progress - just listing the contents of jcls shows us the jobs already tested & debugged.
   

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

1Q6. Converting Test/Demo JCL to Unix/Linux scripts

JCL Conversion Errors

Here is the console display you should get when you run the jclxx51 script.

 jclxx51 jcl2 jcl3   <-- convert all JCL in jcl2 to Korn shell scripts in jcl3
 =================

 script to convert mainframe JCLs to UNIX scripts
 jclunix51 jcl2/jar100.jcl
 jclunix51 jcl3/jar100.ksh     8 in,   55 out,    0 errs
 jclunix51 jcl2/jar200.jcl
 jclunix51 jcl3/jar200.ksh    16 in,   79 out,    0 errs
 jclunix51 jcl2/jgl100.jcl
 jclunix51 jcl3/jgl100.ksh    12 in,   64 out,    0 errs
 jclunix51 jcl2/jgl200.jcl
 jclunix51 jcl3/jgl200.ksh    20 in,   87 out,    0 errs
 jclunix51 jcl2/jgl300.jcl
 jclunix51 jcl3/jgl300.ksh    14 in,   79 out,    0 errs
 jclunix51 jcl2/jgl320.jcl
 jclunix51 jcl3/jgl320.ksh    17 in,   83 out,    0 errs
 jclunix51 jcl2/jpy200.jcl
 ERR: SYSIN parms/member not found: parms/ppy200s1
 ERR@ in#13 out#43 file: jpy200.jcl
 jclunix51 jcl3/jpy200.ksh    20 in,   88 out,     1 errs
 jclunix51 jcl2/splitsl1.jcl
 jclunix51 jcl3/splitsl1.ksh   21 in,   68 out,    0 errs
 9 IBM MVS JCLs converted from jcl2 to UNIX KORN shell scripts in jcl3

ERR: SYSIN parms/member not found: parms/ppy200s1 ERR@ in#13 out#43 file: jpy200.jcl

This is a common error (missing control card library members for SORT FIELDS, etc). In this case we intentionally caused the error by mismatching the name of the control card member in the parms subdir vs the name coded in the JCL.

 ls -l parms       <-- display control card members
 ============

 -rw-rw-r--    1 poha     users          46 May 11 16:40 pap100s1
 -rw-rw-r--    1 poha     users          34 May 11 16:40 pgl200s1
 -rw-rw-r--    1 mvstest  users          34 May 13 12:49 ppy200s2

 vi jcl2/jpy200.jcl    <-- inspect JCL for SYSIN control card member name
 ==================

 //JPY200   JOB
   - - - many lines omitted - - -
 //SYSIN    DD DSN=PY.CTLCDLIB(PPY200S1)

Note the mismatched names; the JCL calls 'PPY200S1', but the closest member in the library is 'ppy200s2'. If you wish, change the member name to 'ppy200s1' & rerun the 'jclxx51' script. The error should go away.

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

1Q7. Converting Test/Demo JCL to Unix/Linux scripts

JCL Conversion Error Log

The previous page illustrated the console display created by 'jclxx51'. The JCL converter also creates an error log file in the 'tmp' subdir containing just the error messages & omitting all successful conversions.

 vi tmp/jclunix51.err          <-- inspect JCL conversion Error Log
 ====================

ERR: SYSIN parms/member not found: parms/ppy200s1 ERR@ in#13 out#43 file: jpy200.jcl Errs=1, In=20, Out=88, File=jcl3/jpy200.ksh

 uvlp12 tmp/jclunix51.err      <-- print the JCL conversion Error Log
 ========================

We recommend you print the JCL conversion Error Log to serve as your guide in correcting the JCL conversion problems. Please see later discussions of how best to correct/test/debug your JCL in Part 4 (pages '4M1' to '4M4').

In the early stages of conversion, you should not make any manual corrections, but rather find & correct any common problems that will be eliminated by reconverting. Missing control card library members is such a problem.

Part 4 also shows you how to setup search/replace table entries in the JCL conversion control file (ctl/jclunixop5) to improve re conversions.

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

1Q8. Converting Test/Demo JCL to Unix/Linux scripts

Convert 1 job at a time

Normally you would use the script method on the previous pages to convert all JCL's in the directory. Converting 1 job at a time might be used to re-convert new jobs brought over from the mainframe. As an example, here are the conversion instructions for demo job 'jgl200'.

 #0.  login: mvstest --> /home/mvstest

      relevant subdirs --> proc0, procs, jcl0, jcl1, jcl2, jcl3, jcls.

 #1a. uvcopy cleanup,fili1=jcl0/JGL200.jcl,filo1=jcl1/jgl200.jcl,uop=g8n1
      ===================================================================
      - cleanup mainframe JCL
      - strip CR's, clear cols 73-80,& shorten back to last nonblank
      - output filenames are lower case & have extension '.jcl' added.

 #1b. uvcopy cleanup,fili1=proc0/PGL200,filo1=procs/pgl200.proc,uop=g8n1
      ==================================================================
      - cleanup PROCs
      - strip CR's, clear cols 73-80,& shorten back to last nonblank

 #1c. uvcopy cleanup,fili1=parm0/PGL200S1,filo1=parms/pgl200s1,uop=g8n1
      =================================================================
      - cleanup Control Card library modules (SORT FIELDS, etc)
      - strip CR's, clear cols 73-80,& shorten to last nonblank

 #2.  jclproc51 jcl1/jgl200.jcl jcl2/jgl200.jcl procs parms
      =====================================================
      - expand PROCs & INCLUDEs as we copy jcl from subdir jcl1 to subdir jcl2

 #3. Note that you must run the 'convert all files in directory' procedures
     first, before you can convert 1 JCL at a time, because the converter
     needs the data info control file (to get recsizes, keys, ID GDG files, etc)
     See the procedures to generate 'ctl/datactl53I' on page '1Q3'.
     Those procedures process the entire directory (not just 1 jcl).

 #4. jclunix51 jcl2/jgl200.jcl jcl3/jgl200.ksh  <-- convert 1 JCL (jgl200)
     =========================================
     - using jgl200 as an example of converting 1 jcl at a time:

 #5. cp jcl3/jgl200.ksh jcls  <-- copy converted script to test/production lib
     =======================      before any changes, testing, debugging

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

1Q9. Converting Test/Demo JCL to Unix/Linux scripts

scripts to convert JCL

JCL conversion scripts are listed in Part_9:

Note that it is much more efficient to convert all JCL's in the directory as documented previously on pages '1Q1' thru '1Q6', or with the 'jcl2ksh51A' script. Script 'jcl2ksh51' would be most useful for JCL's subsequently transferred due to changes on the mainframe.

This assumes that all PROCs & control card library members are already present in procs & parms.

jcl2ksh51A includes the following scripts which might be used separately in some circumstances. If you modify the JCL options control file, you would only need to rerun 'jclxx51' to reconvert jcl2/* to jcl3 (vs jcl2ksh51A).

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

1R1. Converting Test/Demo JCL to Unix/Linux scripts

Converting Mainframe COBOL to Unix/Linux

We have just converted our demo JCL to Korn shell scripts, and we would now like to execute the scripts and show you the results (console displays).

But, we must also have converted & compiled the demo COBOL programs called by the JCL. COBOL conversion & compile is documented in MVSCOBOL.htm, but in case you have skipped directly to this JCL conversion (MVSJCL.doc), we will briefly repeat the COBOL conversion & compile instructions here. You must of course have MicroFocus COBOL installed to compile & execute the COBOL programs, but if you do not, you can still do everything except the 'mfcblA' compiles (#5 on page '1R3'). You can even execute the 'jar200.ksh' demo job. The 1st step will work since it is a SORT.

script to perform all COBOL conversion steps

'cnvMF51Ac' will perform all steps of the copybook conversion & 'cnvMF51A' will perform all steps of the COBOL program conversion - the same as the 'step by step' procedures documented on pages 1R2 thru 1R5. The script is easier than the step by step method, but you might not gain as much understanding.

You should use the 'step by step' method the 1st time you convert your own COBOL (as documented in Part_4), because you will be able to detect & fix problems that may occur in your COBOL conversions (vs the proven test/demos here in Part 1).

converting All Copybooks & COBOL programs

 cpy0 ---------> cpy1 ---------> cpy2 ----------> cpys
       cleanup         convert         copy(cp)

 cbl0-------->cbl1-------->cbl2------->cbl3------->cbl4------->cbls-------->cblx
      cleanup      convert      sysin1     sysout1       copy       compile
                               |--------optional-------|

 #1. cnvMF51Ac all <-- convert copybooks thru all steps, as illustrated above
     ============   - reply null (take defaults) or reply 'y' if y/n demanded

 #2. cnvMF51A all  <-- convert COBOL programs thru all steps, as illustrated above
     ===========    - reply null (take defaults) or reply 'y' if y/n demanded
                    - 1 exception, reply 'n' when asked to run 'cobfil55'

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

1R2. Converting Test/Demo JCL to Unix/Linux scripts

step by step procedures for COBOL conversion

Converting Mainframe COBOL CopyBooks to Unix/Linux

First we will convert the CopyBooks, then the COBOL Programs (on the next page). Our test/demo mainframe copybooks are stored in subdir 'cpy0'. We recommend the following procedure:

 cpy0--------->cpy1---------->cpy2------->cpys
      cleanup       convert        copy

 #1. Cleanup copybooks from mainframe (may have extraneous CR's from FTP)
     - remove CR's, clear cols 1-6 & 73-80, translate to lower (not in quotes)
     - shorten text back to last non-blank, ensure output filenames in lowercase
     - cpy0 filenames UPPER case indicates mainframe,
       but all subsequent subdirs must have filenames in lowercase

 #1. uvcopyx cleanup cpy0 cpy1 uop=q0i7c5e15g8j1k1l1n1s8t1,arg1=.cpy
     ===============================================================

 #2.  uvcopy cnvMF5,fild1=cpy1,fild2=cpy2,fili3=ctl/cnvcob5.tbl,uop=q0i7m2
      ====================================================================
            - convert COBOL CopyBooks for Unix/Linux MicroFocus compiler

 #3.  cp cpy2/* cpys        - copy converted copybooks to standard library
      ==============

       cp cpy1/* cpys       <-- alternative to steps #2a, #2b,& #3
       ==============

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

1R3. Converting Test/Demo JCL to Unix/Linux scripts

Converting Mainframe COBOL to Unix/Linux Micro Focus COBOL

These instructions will convert & compile ALL programs in the directory. Three demo programs (CAP100, CAR100,& CGL100) are supplied in subdir cbl0. The conversions & compile progress thru several subdirs as follows:

 cbl0-------->cbl1-------->cbl2------->cbl3------->cbl4------->cbls-------->cblx
      cleanup      convert      sysin1     sysout1       copy       compile
                               |--------optional-------|

 #1. Cleanup copybooks from mainframe (may have extraneous CR's from FTP)
     - remove CR's, clear cols 1-6 & 73-80, translate to lower (not in quotes)
     - shorten text back to last non-blank, ensure output filenames in lowercase
     - cpy0 filenames UPPER case indicates mainframe,
       but all subsequent subdirs must have filenames in lowercase

 #1. uvcopyx cleanup cbl0 cbl1 uop=q0i7c5e15g8j1k1l1n1s8t1,arg1=.cbl
     ===============================================================

 #2. uvcopy cnvMF5,fild1=cbl1,fild2=cbl2,fili3=ctl/cnvcob5.tbl,uop=q0i7m1
     ====================================================================
            - convert COBOL programs for Unix/Linux Micro Focus compiler
            - for demo programs, only important change is to add 'external'
              onto the file assignments.

Optional sysin1 & sysout1

 #3.  uvcopyx sysin1 cbl2 cbl3 uop=q0i7    <-- optional, see NOTE below
      =================================
            - convert ACCEPT's from control streams to READ's from a file

 #4.  uvcopyx sysout1 cbl3 cbl4 uop=q0i7   <-- optional, see NOTE below
      ==================================
            - convert DISPLAY's upon SYSOUT to WRITE's to a file

Note re sysin1 & sysout1 above

You will NOT need to do #3 & #4 above if you have MicroFocus COBOL which has options INDD & OUTDD to cause 'ACCEPTs from SYSIN' & 'DISPLAYs upon SYSOUT' to use external files defined by exports for SYSIN & SYSOUT. Please see the options file ctl/cobdirectives & a test/demo program & JCL in MVSCOBOL.htm begining on page 2G1.

For customers that do not have MicroFocus COBOL, the Vancouver Utilities includes uvcopy utility jobs 'sysin1' & 'sysout1' which will insert file definitions into the COBOL source programs.

sysin1 will convert 'accepts from sysin' to 'reads' from a real file with external name SYSIN. sysout1 will convert 'displays upon sysout' to 'writes' to a real file with external name SYSOUT.

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

1R4. Converting Test/Demo JCL to Unix/Linux scripts

copy converted programs to compile library

 #5. cp cbl2/* cbls   - copy converted programs to standard source library
     ==============     expected by the compile script (mfcblA)

 #5a. cp cbl3/* cbls  - copy from cbl3/* for optional conversion
      ==============    accept/SYSIN to read from file

 #5b. cp cbl4/* cbls  - copy from cbl4/* for optional conversion
      ==============    display on SYSOUT to write to a file

 #6. mfcblA all       - compile all programs for unix/linux
     ==========         (input source from cbls & output .int/.idy to cblx)

compiling COBOL programs on Unix/Linux

 mfcblA started 050320:1514

#compile #1 - car100.cbl start compile of: car120.cbl

#compile #2 - car120.cbl start compile of: car130.cbl

   - - - etc, 8 clean compiles & 1 Intentional Failure - - -

 #compile #9 - cpy100.cbl
 *                  copy "paymas.cpy".
 *   8-S*****************************                                   (   0)**
 **    Unknown COPY file paymas.cpy specified
 * 256-S***********                                                     (   1)**
 **    Preceding record has zero length
     18 fd  nalist record contains 120 characters.
 * 205-S**                                                              (   1)**
 **    RECORD missing or has zero size
 #compile #9 - cpy100.cbl - *FAILED*
 *** 1 compiles failed, of 9 attempts of 9 total ***
 programs compiled from cbls to cblx
 compile options file=/home/mvstest/ctl/cobdirectives
 mfcblA started 050320:1514, ended 050320:1514

Print Compile Error Reports

 #7. uvlpd1p cblx .err      <-- print 1st page of compile failure reports
     =================

• compile script 'mfcblA' leaves .err reports in the 'cblx' output subdir.
• script 'uvlpd1p' will print the 1st page of all .err files in subdir 'cblx'.
• the .err reports make it easy to perform a mass error correction edit.
• then recompile all with 'mfcblA' until all errors are resolved.

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

1R5. Converting Test/Demo JCL to Unix/Linux scripts

Note re MicroFocus COBOL

You must of course have MicroFocus COBOL installed to compile & execute the COBOL programs, but if you do not, you can still do everything except the 'mfcblA' compiles above. You can even execute the 'jar200.ksh' demo job. The 1st step will work since it is a SORT, before bombing out on step 2.

For the 'mfcblA' COBOL compiles to work, you will probably have to modify the COBDIR definition in the common_profile, depending on where COBOL is installed at your site. The supplied profile (listed at ADMjobs.htm#1C2) defines COBDIR as follows:

 export COBDIR=/opt/microfocus/cobol     <-- COBDIR install default
 ===================================

compiling under SFU/UWIN/CYGWIN on Windows

 #6a. mfnxcblA all   - compile all programs to .int/.idy for SFU/UWIN/CYGWIN
     =============     (input source from cbls & output .int/.idy to cblx)

 #6b. mfnxcblB all   - compile all programs to executables for SFU/UWIN/CYGWIN
     =============     (input source from cbls & output .exe's to cblx)

COBOL compile scripts are different since the MicroFocus COBOL compiler is different (Server Express for Unix/Linux vs Net Express for Windows). The script to compile 1 program at a time is 'mfcbl1' for unix/linux, and 'mfnxcbl1' for SFU/UWIN/CYGWIN (or 'mfnxcbl2' to compile to executables). See listings at MVSCOBOL.htm#5E0.

COBOL compile console logs

 mfnxcblA started 040609:1549
 MicroFocus Net Express V4
 Version 4.0.38 Copyright (C) 1984-2003 MicroFocus International Ltd.
 * Checking complete with no errors - starting code generation
 * Generating car100
 * Data:        2000     Code:        1424     Literals:         484
 #compile #1 - car100.cbl

   - - - etc, 8 clean compiles & 1 Intentional Failure - - -

9 programs compiled from cbls to cblx 1 compiles failed, of 9 attempts mfnxcblA started 040609:1549, ended 040609:1549

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

1S1. Executing the Test/Demo JCL/scripts

Operating Instructions to Execute the Test/Demo JCL/scripts

Now we are ready to execute the demo JCL/scripts. Note that RUNLIBS & RUNDATA (vital environmental variables in the profile) control which libraries are searched & which data directories will be accessed. The following illustrates only the subdirs that are actually required for the demo JCL/script execution and omits the various conversion subdirs illustrated previously.

export RUNLIBS=/home/mvstest/testlibs

 /home/mvstest
 :-----testlibs        <-- $RUNLIBS
 :     :-----cblx        - compiled COBOL programs (.int's)
 :     :-----jcls        - copy here manually 1 by 1 during test/debug

export RUNDATA=/home/mvstest/testdata

 /home/mvstest
 :-----testdata        <-- $RUNDATA
 :     :-----ap          - Accounts Payable
 :     :-----ar          - Accounts Receivable
 :     :-----gl          - General Ledger
 :     :-----ctl         - GDG control file
 :     :-----jobctl      - for jobstop stop at begin each step for debug
 :     :-----jobtmp      - temp files for SYSIN instream data
 :     :-----jobmsgs     - job progress msgs (step begin, end Normal/AbTerm)
 :     :-----sysout      - SYSOUT printer files
 :     :-----tmp         - tmp subdir for uvsort
 :     :-----wrk         - interstep temporary work files

Executing the test/demo JCL/scripts

The pages ahead will present the commands to execute the following JCL/scripts:

After each execute command, we will illustrate the console display expected. Please confirm that you get the same results.

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

1S2. Executing the Test/Demo JCL/scripts

BEFORE attempting to Test/Debug YOUR JCL/scripts

Before you begin to test/debug, I strongly recommend that you study XREFjobs.htm & run the test/demo Inventory Listings, Cross-References, COBOL File Info reports,& JCL Job-Flow reports.

This would be vital if you were about to start testing & debugging your own JCL & COBOL programs. For these demos it would not matter whether you studied & ran them BEFORE or AFTER you execute the supplied JCL & COBOL programs. But, please be sure to run these reports for your own JCL & COBOL programs BEFORE you begin your own testing & debugging.

Here is a summary of the types of reports documented in XREFjobs.htm.

 #1. Inventory lists & counts of all filenames in all directories of relevance.
     ==========================================================================

 #2. Contents listings of JCLs, scripts, control-cards,& copybook maps.
     ==================================================================

 #3. Cross-References of COBOL programs & JCL/scripts.
     =================================================
     - copybooks vs programs, datafiles vs Jobnames, Programs vs Jobnames

 #4. COBOL File Information reports (1 line per datafile)
     ====================================================
     - externalname, Org & Access, Open mode, record-size, copybook, internalname

 #5. JobFlow reports - combine file info from the JCL with the COBOL info above
     ==========================================================================
     - step#, programname, DDname, COBOL info(above), DSNname

These will be explained in more detail in XREFjobs.htm with Operating Instructions to generate them using the test/demo files supplied. You will also need to have an organized way of housing them for easy access when required.

Three Ring Binders with Index Tabs

Before you start your conversion, be sure to obtain a good supply of 3-hole pre-punched paper, 3 ring binders & index tabs. The 3 ring binders should have the clear plastic pockets on the spines & covers so you can insert content identifications. The index tabs should be the 'Avery worksaver BIG TAB insertable dividers'.

Keeping your listings in 3 ring binders with Tabs to identify contents is far superior to the alternative (piles of loose paper all over the place). Note that the listings (of JCL, scripts, copybooks, etc) will appear in alphabetical sequence since unix maintains alpha sequence within directories.

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

1S3. Executing the Test/Demo JCL/scripts

Execute demo scripts & observe console displays

 jar100.ksh        <-- execute test/demo JCL/script 'jar100'
 ==========
 080827:155517:JAR100: Begin Job=JAR100
 080827:155517:JAR100: /home/mvstest/testlibs/jcls/jar100.ksh
 080827:155517:JAR100: Arguments:
 080827:155517:JAR100: RUNLIBS=/home/mvstest/testlibs
 080827:155517:JAR100: RUNDATA=/home/mvstest/testdata
 080827:155517:JAR100: JTMP=jobtmp/JAR100 SYOT=sysout/JAR100
 080827:155517:JAR100: RUNDATE=20080827
 080827:155517:JAR100: Begin Step S0010 car100 (#1)
 080827:155517:JAR100: file: CUSTMAS=data/ar.customer.master bytes=8192
 080827:155517:JAR100: file: NALIST=data/ar.customer.nameadrs.list100 bytes=2858
 080827:155517:JAR100: file: SYSOUT=sysout/JAR100/S0010_SYSOUT bytes=0
 080827:155517:JAR100: Job Times: Begun=15:55:17 End=15:55:17 Elapsed=00:00:00
 080827:155517:JAR100: JobEnd=Normal, StepsExecuted=1, LastStep=S0010

 jar200.ksh        <-- execute JCL/script 'jar200'
 ==========
 080827:155553:JAR200: Begin Job=JAR200
 080827:155553:JAR200: /home/mvstest/testlibs/jcls/jar200.ksh
 080827:155553:JAR200: Arguments:
 080827:155553:JAR200: RUNLIBS=/home/mvstest/testlibs
 080827:155553:JAR200: RUNDATA=/home/mvstest/testdata
 080827:155553:JAR200: JTMP=jobtmp/JAR200 SYOT=sysout/JAR200
 080827:155553:JAR200: RUNDATE=20080827
 080827:155553:JAR200: Begin Step S0010 sort (#1)
 080827:155553:JAR200: file: SORTIN=data/ar.sales.items bytes=1280
 080827:155553:JAR200: file: SORTOUT=jobtmp/JAR200/__tempsls bytes=0
 080827:155553:JAR200: file: SYSIN=jobtmp/JAR200/S0010_sort_SYSIN bytes=92
 080827:155553:JAR200: uvsort fili1=data/ar.sales.items,filo1=jobtmp/JAR200/__tempsls
 080827:155553:JAR200: EOF fili01 20 rds, 1280 size; data/ar.sales.items
 080827:155553:JAR200: sort phase complete, used 64 megabytes, sort output begin
 080827:155553:JAR200: EOF filo01 16 wrts, 1024 size; jobtmp/JAR200/__tempsls
 080827:155553:JAR200: Begin Step S0020 car200 (#2)
 080827:155553:JAR200: file: SALEDTL=jobtmp/JAR200/__tempsls bytes=1024
 080827:155553:JAR200: file: CUSTMAS=data/ar.customer.master.indexed bytes=0
 080827:155553:JAR200: file: SALELST=data/ar.sales.list bytes=1521
 080827:155553:JAR200: Job Times: Begun=15:55:53 End=15:55:53 Elapsed=00:00:00
 080827:155553:JAR200: JobEnd=Normal, StepsExecuted=2, LastStep=S0020

Notes re Console Displays

1. Please see the JCL/scripts (previously listed beginning on page '1C1'), if you wish to relate the console displays to the originating lines in the converted scripts.
   
   
2. Values of $RUNLIBS & $RUNDATA are displayed at 'JOB begin', to avoid any possible confusion between test libs/data & production libs/data.
   
   
3. 'begin step' messages identify the step# & program executed.
   

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

1S4. Executing the Test/Demo JCL/scripts

 jgl100.ksh        <-- execute JCL/script 'jgl100'
 ==========
 080827:155743:JGL100: Begin Job=JGL100
 080827:155743:JGL100: /home/mvstest/testlibs/jcls/jgl100.ksh
 080827:155743:JGL100: Arguments:
 080827:155743:JGL100: RUNLIBS=/home/mvstest/testlibs
 080827:155743:JGL100: RUNDATA=/home/mvstest/testdata
 080827:155743:JGL100: JTMP=jobtmp/JGL100 SYOT=sysout/JGL100
 080827:155743:JGL100: RUNDATE=20080827
 080827:155743:JGL100: Begin Step S0010 cgl100 (#1)
 080827:155743:JGL100: gen0: ACCTMAS=data/gl.account.master_000003 insize=8720
 080827:155743:JGL100: gen+1: ACTLIST=jobtmp/JGL100/GDG/data/gl.account.acntlist_000004 gens=8
 080827:155743:JGL100: file: SYSOUT=sysout/JGL100/S0010_SYSOUT bytes=0
 080827:155743:JGL100: Job Times: Begun=15:57:43 End=15:57:43 Elapsed=00:00:00
 080827:155743:JGL100: moving jobtmp/JGL100/GDG/subdir/files back to $RUNDATA/subdirs/
 `jobtmp/JGL100/GDG/data/gl.account.acntlist_000004' -> `data/gl.account.acntlist_000004'
 080827:155743:JGL100: JobEnd=Normal, StepsExecuted=1, LastStep=S0010

Generation files in jgl100 & jgl200

1. Non-GDG files are displayed, prefixed by 'file:' (jar100/200 on prior page). These displays are created by the 'exportfile' function. Note the calls to exportfile in scripts jar100/jar200 previously listed on page '1C2' & '1D2'. See the exportfile function listed later on page '3C1'.
   
   
2. GDG files are displayed, prefixed by 'gen0:' or 'gen+1:' (jgl100/200 above). These displays are created by functions 'exportgen0' & 'exportgen1'. Note the calls to exportgen0/exportgen1 in scripts jgl100/jgl200 listed previously on pages '1E3' & '1F3'. See these functions listed later on beginning on page '5J1'.
   

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

1S5. Executing the Test/Demo JCL/scripts

 jgl200.ksh        <-- execute JCL/script 'jgl200'
 ==========
 080827:155906:JGL200: Begin Job=JGL200
 080827:155906:JGL200: /home/mvstest/testlibs/jcls/jgl200.ksh
 080827:155906:JGL200: Arguments:
 080827:155906:JGL200: RUNLIBS=/home/mvstest/testlibs
 080827:155906:JGL200: RUNDATA=/home/mvstest/testdata
 080827:155906:JGL200: JTMP=jobtmp/JGL200 SYOT=sysout/JGL200
 080827:155906:JGL200: RUNDATE=20080827
 080827:155906:JGL200: Begin Step S0010 sort (#1)
 080827:155906:JGL200: file: SORTIN=data/gl.account.tran1 bytes=1600
 080827:155906:JGL200: gen+1: SORTOUT=jobtmp/JGL200/GDG/data/gl.account.trans_000006 gens=18
 080827:155906:JGL200: file: SYSIN=data/gl.parms/pgl200s1 bytes=0
 080827:155906:JGL200: file: SYSIN=/home/mvstest/testlibs/parms/pgl200s1 bytes=34
 080827:155906:JGL200: uvsort fili1=data/gl.account.tran1,filo1=jobtmp/JGL200/GDG/data/gl.account.trans_000006
 080827:155906:JGL200: EOF fili01 20 rds, 1600 size; data/gl.account.tran1
 080827:155906:JGL200: sort phase complete, used 64 megabytes, sort output begin
 080827:155906:JGL200: EOF filo01 20 wrts, 1600 size; jobtmp/JGL200/GDG/data/gl.account.trans_000006
 080827:155906:JGL200: Begin Step S0020 cgl200 (#2)
 080827:155906:JGL200: gen+1: GLTRANS=jobtmp/JGL200/GDG/data/gl.account.trans_000006 gens=18
 080827:155906:JGL200: gen0: GLMSOLD=data/gl.account.master_000003 insize=8720
 080827:155906:JGL200: gen+1: GLMSNEW=jobtmp/JGL200/GDG/data/gl.account.master_000004 gens=10
 080827:155906:JGL200: Job Times: Begun=15:59:06 End=15:59:06 Elapsed=00:00:00
 080827:155906:JGL200: moving jobtmp/JGL200/GDG/subdir/files back to $RUNDATA/subdirs/
 `jobtmp/JGL200/GDG/data/gl.account.master_000004' -> `data/gl.account.master_000004'
 `jobtmp/JGL200/GDG/data/gl.account.trans_000006' -> `data/gl.account.trans_000006'
 080827:155906:JGL200: JobEnd=Normal, StepsExecuted=2, LastStep=S0020

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

1S6. Executing the Test/Demo JCL/scripts

 jgl320.ksh        <-- execute JCL/script 'jgl320'
 ==========
 080827:155938:JGL320: Begin Job=JGL320
 080827:155938:JGL320: /home/mvstest/testlibs/jcls/jgl320.ksh
 080827:155938:JGL320: Arguments:
 080827:155938:JGL320: RUNLIBS=/home/mvstest/testlibs
 080827:155938:JGL320: RUNDATA=/home/mvstest/testdata
 080827:155938:JGL320: JTMP=jobtmp/JGL320 SYOT=sysout/JGL320
 080827:155938:JGL320: RUNDATE=20080827
 080827:155938:JGL320: Begin Step S0010 iebgener (#1)
 080827:155938:JGL320: gen0: SYSUT1=data/gl.account.master_000005 insize=8720
 080827:155938:JGL320: file: SYSUT2=jobtmp/JGL320/__tempglm bytes=0
 080827:155938:JGL320: uvcp fili1=data/gl.account.master_000005,filo1=jobtmp/JGL320/__tempglm
 080827:155938:JGL320: EOF fili01 109 rds, 8720 size; data/gl.account.master_000005
 080827:155938:JGL320: EOF filo01 109 wrts, 8720 size; jobtmp/JGL320/__tempglm
 080827:155938:JGL320: Begin Step S0020 idcams (#2)
 080827:155938:JGL320: file: TEMPGLM=jobtmp/JGL320/__tempglm bytes=8720
 080827:155938:JGL320: gen+1: ACNTMAS=jobtmp/JGL320/GDG/data/gl.account.master_000006 gens=10
 080827:155938:JGL320: file: SYSIN=jobtmp/JGL320/S0020_idcams_SYSIN bytes=84
 080827:155938:JGL320: uvcp fili1=jobtmp/JGL320/__tempglm,filo1=jobtmp/JGL320/GDG/data/gl.account.master_000006
 080827:155938:JGL320: EOF fili01 109 rds, 8720 size; jobtmp/JGL320/__tempglm
 080827:155938:JGL320: EOF filo01 109 wrts, 0 size; jobtmp/JGL320/GDG/data/gl.account.master_000006
 080827:155938:JGL320: DISAMdat: recs=109,rcsz=80,keys=1; jobtmp/JGL320/GDG/data/gl.account.master_000006
 080827:155938:JGL320: Job Times: Begun=15:59:38 End=15:59:38 Elapsed=00:00:00
 080827:155938:JGL320: moving jobtmp/JGL320/GDG/subdir/files back to $RUNDATA/subdirs/
 `jobtmp/JGL320/GDG/data/gl.account.master_000006.dat' -> `data/gl.account.master_000006.dat'
 `jobtmp/JGL320/GDG/data/gl.account.master_000006.idx' -> `data/gl.account.master_000006.idx'
 080827:155938:JGL320: JobEnd=Normal, StepsExecuted=2, LastStep=S0020

jgl300 & jgl320 are intended to demonstrate CONDition (Return Code) testing. You could create a failure in step#1 & observe that step#2 would be inhibited. An easy way to cause step#1 to fail is to change the input data filename or to change the filename definition in the script.

jgl300 & jgl320 are almost the same (see listings on pages '1G2' & '1G4'). The difference is that jgl320 illustrates IF/THEN/ENDIF in addition to the CONDition codes (see notes with previous listings).

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

1T1. Checking Test/Demo Output Results

Checking Test/Demo Results

On the previous few pages, we executed the converted jcl/scripts & observed the console displays. The next few pages will illustrate the data inputs & the expected report outputs.

First we will review the directories directly involved in the execution of the jcl/scripts. Compared to the complete list on page '1A2', you will notice we have omitted several other directories not required for execution (original source JCL/COBOL & various subdirs required for conversion)

We have coded the datafiles with '--I--' to identify a supplied test data file or '--O--' to identify a file created during our test/demo executions (output reports, sort work files, etc).

subdirs & I/O files used in execution

 /home/mvstest
 :-----testlibs            <-- super directory for test libs subdirs
 :     :-----cblx          <-- executable (compiled) COBOL programs
 :     :-----jcls          <-- JCLs converted to Korn shell scripts
 :-----testdata            <-- super directory for test/data subdirs & files
 :     :-----ar
 :     :     :--I--customer.master
 :     :     :--O--customer.namelist     <-- report created by jar100.ksh
 :     :     :--I--sales.items
 :     :-----gl
 :     :     :--O--account.acntlist      <-- report created by jgl100.ksh
 :     :     :--I--account.master_000001
 :     :     :--I--account.master_000002
 :     :     :--I--account.master_000003
 :     :     :--O--account.master_000004 <-- updated master from jgl200.ksh
 :     :     :--O--account.master_000005 <-- new generation from jcl300.ksh
 :     :     :--O--account.master_000006 <-- new generation from jcl320.ksh
 :     :     :--I--account.trans
 :     :-----jobtmp                      <-- temp files for SYSIN instream data
 :     :     :--O--JAR200_1_sort_SYSIN   <-- instream data stored by jar200.ksh
 :     :     :--O--JGL200_1_sort_SYSIN   <-- instream data stored by jgl200.ksh
 :     :-----sysout
 :     :     :-----040429                <-- subdir for today's SYSOUT files
 :     :     :     :-----SYSOUT.files... <-- no SYSOUTs created in these tests
 :     :-----tmp                         <-- temp files for uvsort & misc use
 :     :-----wrk
 :     :     :--O--JAR200_tempsls        <-- sorted sales.items from jar200.ksh
 :     :     :--O--JGL200_tempglt        <-- sorted GLtransctns from jgl200.ksh
 :     :     :--O--JGL300_tempglm        <-- copy out backup from jgl300.ksh
 :     :     :--O--JGL320_tempglm        <-- copy out backup from jgl320.ksh

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

1T2. Checking Test/Demo Output Results

Check I/O for jar100.ksh

 #1. cd testdata      <-- change into testdata super-directory
     ===========

 #1a. cdd             <-- shorter alias, very handy for production data
      ===               - usually in separate filesystem with long pathnames

 #2. uvhd data/ar.customer.master r256 <-- investigate input to jar100.ksh
     =================================   - 1st record shown below
                                         - cant use uvhd due to packed & no LFs

                      10        20        30        40        50        60
 r#        1 0123456789012345678901234567890123456789012345678901234567890123
           0 130140    EVERGREEN MOTORS LTD.    1815 BOWEN ROAD          NANA
             3333332222454545444244545524542222233332445442544422222222224444
             130140000056527255E0DF4F230C44E0000181502F75E02F140000000000E1E1
          64 IMO          BC V9S1H1    250-754-5531 LARRY WRENCH     ..4V|...
             4442222222222442535343222233323332333324455525544442222201357000
             9DF00000000002306931810000250D754D55310C12290725E38000000246C000
         128 .........W0....`........)X}..f3.....\.................4V}...f...
             0000000005300016000000002570063100095000000000000000013570016000
             0C0000C0270D0540C0000C0098D0263C0444C0000C0000C0000C0246D0056C00
         192 ...............................f.....<........f.C 19950531
             0000008900000000880000000018000680001300000000694233333333222222
             00C0026C0000C0023C0000C0083C0056D0012C0000C0016D3019950531000000
 rec#=1 rcount=32 rsize=256 fsize=8192 data/ar.customer.master
 null=next,r#=rec,s=search,u=update,p=print,i=iprint,w=write,t=tally,c=checkseq
 ,R#=Recsize,h1=char,h2=hex,q=quit,?=help --> q  <-- quit program

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

1T3. Checking Test/Demo Output Results

jar100/car100 - sample output report

 #3. vi data/ar.customer.nameadrs.list100
     ====================================

 CAR100: CUSTOMER NAME & ADDRESS LIST    080322

 130140    EVERGREEN MOTORS LTD.    1815 BOWEN ROAD          NANAIMO          BC V9S1H1
 132588    GEECOE GENERATOR SERVICESUNIT 170 - 2851 SIMPSON  RICHMOND         BC V6X2R2
 139923    JOHNSTONE BOILER & TANKS 1250 EAST PENDER STREET  VANCOUVER        BC V5L1W1
 142175    LILLY ELECTRIC (1973) LTD16809 - 24TH AVENUE      SURREY           BC V4B5E7
 145264  D MAGRATH SUPPLIES LTD.    1939 KIRSCHNER ROAD      KELOWNA          BC V1Y4N7
 147615  X O'CONNER R.V. CENTRE     44430 YALE ROAD WEST     CHILLIWACK       BC V2P6J1
 149304    POINT GREY GOLF & COUNTRY3350 S.W. MARINE DRIVE   VANCOUVER        BC V6N3Y9
 150825    RIGGERS INDUSTRIAL       960 - 6TH AVENUE         HOPE             BC
 152355    SHAW, JOHN               477 CARIBOO CRES.        PORT COQUITLAM   BC V3M1X1
 154688    TAURUS RESOURCES         1110 - 625 HOWE STREET   VANCOUVER        BC V6C2T6
 157352  D WHYTE, W.                1150 LODGE ROAD          NORTH VANCOUVER  BC V7R1W8
 173320  X ZENITH TRANSPORT         2381 ROGERS AVE          COQUITLAM        BC V3K5Y2
 201120    ALLTYPE RENTAL LTD.      BOX 1819                 DRAYTON VALLEY   AL T0E0M0
 204700    CASE POWER EQUIPMENT     12611-100 ST             GRANDE PRAIRIE   AL T8V4H2
 208060    E&L TRUCKING             LAND & CATTLE LTD        WARBURG          AB T0C2T0
 211140  D FORD NEW HOLLAND         BOX 1, 440 ELLIS ROAD    WINTERBURN       AB T0E2N0
 223240  X NICHOLSON CHEVROLET LTD. 7215 ARGYLL ROAD         EDMONTON         AL T6C4J2
 224700    OTTO MOBILES WESTERN LTD.8441 CORONET ROAD        EDMONTON         AL T6E4N7
 231550    SPARROW ELECTRIC CO. LTD.BOX 88                   NISKU            AL T0C2G0
 234300    TERRITORIAL REWIND       BPX 1648                 YELLOWKNIFE      NW X1A2P2
 237286    WEBER, TOM               BOX 5503                 FORT MCMURRAY    AL T9H3G5
 301120  D ALBERTA GAS CHEMICALS LTD3RD. FLOOR, 11456 JASPER EDMONTON         AL T5K0M1
 306959  X 356582 ALBERTA LTD.      DEVITT NURSERY           CALGARY          AL T2T5N1
 308685    FOOTHILLS ELECTRIC       3932 - 3A ST. N.W.       CALGARY          AL T2E6R4
 313720    MONITREX ENGINEERING LTD 7-2280-39 AVE, N.E.      CALGARY          AL T2E6P7
 315512    PARTS PLUS               BOX 510 MAIN ST          THREE HILLS      AB T0M2A0
 318833    TOP NOTCH CONSTRUCTION   BOX 308, STN J           CALGARY          AL T2A4X6
 400002    ACKLANDS LTD             945 -2ND AVE             PRINCE GEORGE    BC V2L3A7
 401210    COAST RANGE CONSTRUCTION 1103-207 W. HASTINGS ST  VANCOUVER        BC V6B1H7
 402875    HULL, DON & SONS LTD.    BOX 1297                 PRINCE GEORGE    BC V2L4V3
 403887  D MILNER, LARRY            BOX 28 RAU ROAD R.R.8    QUESNEL          BC V2J5E6
 406082    PRECAM RENTALS LTD:      10116-94TH AVE           FORT ST. JOHN    BC V1G5G6

We can use 'vi' to inspect the output report because the COBOL program defines report files as 'ORGANIZATION LINE SEQUENTIAL' which appends Carriage-Returns & Line-Feeds. The 'CRs' are displayed as '^M' by vi. ('LF's are not displayed since they are standard in unix/linux text files)

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

1T4. Checking Test/Demo Output Results

Check I/O for jcls/jar200.ksh

'jar200' sorts data/ar.sales.items by product code & lists the detail records with final totals of quantity & amount.

Although there are no packed fields in this file, we still cannot use 'vi' (or more,page,lp,etc) because the records have no LineFeeds & the entire file looks like 1 long record to vi. Here is the 1st record shown by uvhd:

 #1. uvhd data/ar.sales.items r64h2 <-- display 64 byte records in hexadecimal
     ==============================   - 1st of 20 (all listed below by listrec2)

                      10        20        30        40        50        60
 r#        1 0123456789012345678901234567890123456789012345678901234567890123
           0 130140    21 940802 IN111001  HAM001  000020 0000001 000000020
             3333332222332333333244333333224443332233333323333333233333333322
             130140000021094080209E1110010081D0010000002000000001000000002000

We can use 'listrec2' (uvcopy pre-programmed job) to list files w/o LineFeeds

 #2. uvcopy listrec2,fili1=data/ar.sales.items,uop=r64 <-- list file no LineFeeds
     =================================================
                    ,filo1=tmp/sales.items.lst    <-- output report default name

 listrec2 - list (100 bytes/line) file=data/ar.sales.items 2004/04/29_18:18:26
           1         2         3         4         5         6
 0123456789012345678901234567890123456789012345678901234567890123

 130140 2  21 940802 IN111001  HAM001  000020 0000001 000000020
 130140 2  21 940802 IN111001  SCR012  000021 0001001 000021021
 130140 2  21 940802 IN111001  CHR001  000022 0002001 000044022
 139923 2  35 950802 IN111002  TAB013  000023 0003001 000069023
 139923 2  35 950807 IN111002  TAB013  000024 0004001 000096024
 150825 2  44 960804 IN1122    HAM001  000025 0005001 000125025
 150825 2  44 960804 IN1122    HAX129  000026 0006001 000156026
 201120 2  44 970807 CR5234    WHIP75  000027 0007001 000189027
 223240 2  65 980816 CR955     HAM001  000028 0008001 000224028
 223240 2  65 980816 IN441     BBQ001  000029 0009001 000261029
 308685 2  21 990812 IN6605    SAW051  00001p 0000001 00000001p
 308685 2  21 990812 IN6605    WHIP75  00001q 0001001 00001101q
 308685 2  21 990812 CR8835    TAB013  00001r 0002001 00002401r
 315512 2  44 000805 IN2251    HAM001  00001s 0003001 00003901s
 315512 2  44 000805 IN2251    SAW051  00001t 0004001 00005601t
 315512 2  44 000805 IN2255    WHIP75  00001u 0005001 00007501u
 400002 2  85 010812 CR245     HAX129  00001v 0006001 00009601v
 406082 2  35 020815 IN33001   BBQ001  00001w 0007001 00011901w
 406082 2  35 020815 IN33001   TAB013  00001x 0008001 00014401x
 406082 2  65 020816 IN441     HAM001  00001y 0009001 00017101y
 ==============================================================
 cust#   slsmn date  invoice   product  qty    price    amount

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

1T5. Checking Test/Demo Output Results

run jar200.ksh & inspect Output

 #3. jar200.ksh        <-- run job to sort, update,& execute COBOL car200.cbl
     ==========

 #4. vi data/ar.sales.list  <-- use vi to inspect report created by car200.cbl
     =====================

 406082 PRECAM RENTALS LTD:     35 020815 IN33001  BBQ001      17-    70.01     1,190.17-
 130140 EVERGREEN MOTORS LTD.   21 940802 IN111001 CHR001      22     20.01       440.22
 130140 EVERGREEN MOTORS LTD.   21 940802 IN111001 HAM001      20       .01          .20
 150825 RIGGERS INDUSTRIAL      44 960804 IN1122   HAM001      25     50.01     1,250.25
 315512 PARTS PLUS              44 000805 IN2251   HAM001      13-    30.01       390.13-
 150825 RIGGERS INDUSTRIAL      44 960804 IN1122   HAX129      26     60.01     1,560.26
 308685 FOOTHILLS ELECTRIC      21 990812 IN6605   SAW051      10-      .01          .10-
 315512 PARTS PLUS              44 000805 IN2251   SAW051      14-    40.01       560.14-
 130140 EVERGREEN MOTORS LTD.   21 940802 IN111001 SCR012      21     10.01       210.21
 139923 JOHNSTONE BOILER & TANK 35 950802 IN111002 TAB013      23     30.01       690.23
 139923 JOHNSTONE BOILER & TANK 35 950807 IN111002 TAB013      24     40.01       960.24
 308685 FOOTHILLS ELECTRIC      21 990812 CR8835   TAB013      12-    20.01       240.12-
 406082 PRECAM RENTALS LTD:     35 020815 IN33001  TAB013      18-    80.01     1,440.18-
 201120 ALLTYPE RENTAL LTD.     44 970807 CR5234   WHIP75      27     70.01     1,890.27
 308685 FOOTHILLS ELECTRIC      21 990812 IN6605   WHIP75      11-    10.01       110.11-
 315512 PARTS PLUS              44 000805 IN2255   WHIP75      15-    50.01       750.15-
                                                               78               2,320.78

1. The output file has been sorted into product code sequence (bytes 30-35) and total quantity & amount are printed at EOF.
   
   
2. Four records were dropped due to 'OMIT's for slsmn 65 & 85 (see JCL/script listing on page '1D4')
   

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

1T6. Checking Test/Demo Output Results

data/gl.account.master_ GDG file

data/gl.account.master_ is a GDG file with packed fields, so must use 'uvhd':

 #1. uvhd data/gl.account.master_000001 r128 <-- display 128 byte records in hex
     =======================================

                      10        20        30        40        50        60
 r#        1 0123456789012345678901234567890123456789012345678901234567890123
           0  11100       11100Royal Bank Lynn Valley        ....b.20090131
             2333332222222333335676624666247662566667222222220010683333333322
             0111000000000111002F91C021EB0C9EE061CC590000000000972C2009013100
          64
             2222222222222222222222222222222222222222222222222222222222222222
             0000000000000000000000000000000000000000000000000000000000000000
                      10        20        30        40        50        60
 r#        2 0123456789012345678901234567890123456789012345678901234567890123
         128  11200       11200VISA settlement               .....\20090131
             2333332222222333335454276776666672222222222222220000853333333322
             011200000000011200693103544C5D5E400000000000000000197C2009013100
          64
             2222222222222222222222222222222222222222222222222222222222222222
             0000000000000000000000000000000000000000000000000000000000000000
                      10        20        30        40        50        60
 r#        3 0123456789012345678901234567890123456789012345678901234567890123
         256  11500       11500Investments RBMF              ..4.1.20090131
             2333332222222333334676776667725444222222222222220039313333333322
             0115000000000115009E6534D5E43022D60000000000000001421C2009013100
          64
             2222222222222222222222222222222222222222222222222222222222222222
             0000000000000000000000000000000000000000000000000000000000000000

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

1T7. Checking Test/Demo Output Results

run jgl00.ksh & inspect Output

 #2. jgl100.ksh     <-- run job to execute COBOL cgl100.cbl
     ==========

 #3. vi data/gl.account.acntlist_000000 <-- inspect report created by cgl100.cbl
     ==================================

data/gl.account.acntlist_000000

  11100    Royal Bank Lynn Valley             19,076.28   20090331
  11200    VISA settlement                     1,098.75   20090331
  11500    Investments RBMF                  134,923.11   20090331
  11600    RBMF - capital gains db             3,486.06   20090331
  11610    RBMF capital gains 100%             3,486.06   20090331
  11620    RBMF CG 66%                         5,713.24   20090331
  11630    RBMF CG 50%                         1,446.71   20090331
  11700    RBMF - interest                     3,419.60   20090331
  12100    Accounts Receivable                11,900.00   20090331
  12200    Allowance for Bad Debts                  .00   20090331
        - - - - - 1st 10 lines only of 109 total - - - - -

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

1U1. Re-run Test/Demo JCL/scripts with Console Logging

Previous pages illustrated executing the demo JCL/scripts & capturing the console display via redirection or using 'tee'. A better way is to use the Unix/Linux 'script' command to capture console logs into date/time stamped files. Console Logging is extensively documented in ADMjobs.htm but here is the short version.

UV Console Logging Features

1. Collects everything that happens during the operators login session (not just the JCL/script messages). This will include any unix/linux commands entered between the various JCL/script executions.
   
   
2. Console Log files are collected in 1 central location for all users who wish to participate. Mandatory for operators, but advantageous for programmers debugging jobs.
   
   
3. Console logs collected into date/time stamped files within a subdir for each user. This is made automatic by uncommenting the last few lines provided in the recommended profile (listed at ADMjobs.htm#1C1). The critical line is reproduced here:
   

    exec script $LOGDIR/log1/$LOGNAME/$(date +%y%m%d:%H%M%S)
    ========================================================

4. We recommend setting up an 'applications administrator' account (appsadm), to administer console logging along with other administrative functions that may span multiple applications.
   
   

   Console Log Collection subdirs

 /home/appsadm
 :-----log1                        <-- log1 superdir for logs in progress
 :     :-----user1                 <-- subdir for each userid to be logged
 :     :-----user2
 :     :-----mvstest
             :------030925:080115  <-- sample logfile in progress
             :
 :-----log2                        <-- log2 superdir for current month
 :     :-----user1
 :     :-----user2
 :     :-----mvstest
             :------030921:102652   <-- logfiles for current month
             :------030922:130116     - date/time stamped YYMMDD:HHMMSS
             :------030923:074559     - processed from log1 on logoff/logon
             :------030924:074559       (screen control codes removed)
             :
 :-----log3                        <-- prior month logfiles
 :     :-----user1                   - copied from log2 at end month (by cron)
 :     :-----user2                     (then log2 subdirs cleared out)
 :     :-----mvstest

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

1U2. Re-run Test/Demo JCL/scripts with Console Logging

Activate Console Logging & Re-run demos

1. Setup the 'appsadm' login account using the same profiles as for mvstest (but with console logging disabled for appsadm itself).
   
   
2. Setup the log1, log2, log3 superdirs as shown on the prior page. Within each of log1,log2,log3, and for each user account to be logged, setup a subdir matching their login userid ($LOGNAME). For our demos userid 'mvstest' is the only one required.
   
   
3. Now uncomment the last few lines in the profile of the 'mvstest' login. The critical line was shown on the previous page.
   
   
4. Logout & back into 'mvstest' to start collecting the logs. Logging back in will fail if the subdir matching the userid is not found within the superdir (/home/appsadm/log1).
   
   
5. Re-run the JCL/script demos (we will illustrate the following 3):
   

 5a. jar100.ksh
     ==========

 5b. jgl100.ksh
     ==========

 5c. jgl200.ksh
     ==========

6. Logoff & back on to process the logfile from log1/mvstest to log2/mvstest (as illustrated on the previous page).
   
   
7. You may display any prior logfile using the 'logview' script provided (and print if desired).
   

 7a. logview   <-- display list of date/time stamped logfiles in current month
     =======

 -rw-rw-r--    1 mvs      users      495823 Sep 21 13:01 030921:102652
 -rw-rw-r--    1 mvs      users       69075 Sep 22 07:11 030922:130116
 -rw-rw-r--    1 mvs      users      253990 Sep 23 09:02 030923:074559
 -rw-rw-r--    1 mvs      users      178428 Sep 24 10:26 030924:221341
 enter 1,2,3,etc to vi logfile (counting backwards) q to quit
  - may follow file# with -dprinterdest to print

 --> 1             <-- to see the latest logfile (uses vi editor)

 --> 1 -dprinter1  <-- to print the latest logfile

Logview prompts for the file# desired (1 is the latest & usually what you want to see). You may follow the file# with a printer destination. Or you could login as appsadm & print the file from the 'log2/mvstest' subdir.

Please see the next page for the console log result of running the 2 demo jobs.

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

1U3. Re-run Test/Demo JCL/scripts with Console Logging

Console Log from demo JCL/scripts

 Script started on Mon 17 Jul 2006 07:47:16 PM PDT

 <@:mvstest:/home/mvstest> jar100.ksh
 080827:155517:JAR100: Begin Job=JAR100
 080827:155517:JAR100: /home/mvstest/testlibs/jcls/jar100.ksh
 080827:155517:JAR100: Arguments:
 080827:155517:JAR100: RUNLIBS=/home/mvstest/testlibs
 080827:155517:JAR100: RUNDATA=/home/mvstest/testdata
 080827:155517:JAR100: JTMP=jobtmp/JAR100 SYOT=sysout/JAR100
 080827:155517:JAR100: RUNDATE=20080827
 080827:155517:JAR100: Begin Step S0010 car100 (#1)
 080827:155517:JAR100: file: CUSTMAS=data/ar.customer.master bytes=8192
 080827:155517:JAR100: file: NALIST=data/ar.customer.nameadrs.list100 bytes=2858
 080827:155517:JAR100: file: SYSOUT=sysout/JAR100/S0010_SYSOUT bytes=0
 080827:155517:JAR100: Job Times: Begun=15:55:17 End=15:55:17 Elapsed=00:00:00
 080827:155517:JAR100: JobEnd=Normal, StepsExecuted=1, LastStep=S0010

..... other logs omitted (only 1st & last shown) .....

 <@:mvstest:/home/mvstest> jgl320.ksh
 080827:155938:JGL320: Begin Job=JGL320
 080827:155938:JGL320: /home/mvstest/testlibs/jcls/jgl320.ksh
 080827:155938:JGL320: Arguments:
 080827:155938:JGL320: RUNLIBS=/home/mvstest/testlibs
 080827:155938:JGL320: RUNDATA=/home/mvstest/testdata
 080827:155938:JGL320: JTMP=jobtmp/JGL320 SYOT=sysout/JGL320
 080827:155938:JGL320: RUNDATE=20080827
 080827:155938:JGL320: Begin Step S0010 iebgener (#1)
 080827:155938:JGL320: gen0: SYSUT1=data/gl.account.master_000005 insize=8720
 080827:155938:JGL320: file: SYSUT2=jobtmp/JGL320/__tempglm bytes=0
 080827:155938:JGL320: uvcp fili1=data/gl.account.master_000005,filo1=jobtmp/JGL320/__tempglm
 080827:155938:JGL320: EOF fili01 109 rds, 8720 size; data/gl.account.master_000005
 080827:155938:JGL320: EOF filo01 109 wrts, 8720 size; jobtmp/JGL320/__tempglm
 080827:155938:JGL320: Begin Step S0020 idcams (#2)
 080827:155938:JGL320: file: TEMPGLM=jobtmp/JGL320/__tempglm bytes=8720
 080827:155938:JGL320: gen+1: ACNTMAS=jobtmp/JGL320/GDG/data/gl.account.master_000006 gens=10
 080827:155938:JGL320: file: SYSIN=jobtmp/JGL320/S0020_idcams_SYSIN bytes=84
 080827:155938:JGL320: uvcp fili1=jobtmp/JGL320/__tempglm,filo1=jobtmp/JGL320/GDG/data/gl.account.master_000006
 080827:155938:JGL320: EOF fili01 109 rds, 8720 size; jobtmp/JGL320/__tempglm
 080827:155938:JGL320: EOF filo01 109 wrts, 0 size; jobtmp/JGL320/GDG/data/gl.account.master_000006
 080827:155938:JGL320: DISAMdat: recs=109,rcsz=80,keys=1; jobtmp/JGL320/GDG/data/gl.account.master_000006
 080827:155938:JGL320: Job Times: Begun=15:59:38 End=15:59:38 Elapsed=00:00:00
 080827:155938:JGL320: moving jobtmp/JGL320/GDG/subdir/files back to $RUNDATA/subdirs/
 `jobtmp/JGL320/GDG/data/gl.account.master_000006.dat' -> `data/gl.account.master_000006.dat'
 `jobtmp/JGL320/GDG/data/gl.account.master_000006.idx' -> `data/gl.account.master_000006.idx'
 080827:155938:JGL320: JobEnd=Normal, StepsExecuted=2, LastStep=S0020

 <@:mvstest:/home/mvstest> exit

 Script done on Mon 17 Jul 2006 07:47:53 PM PDT

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

1V1. Reconvert Test/Demo JCL/scripts

reconverting JCL - 1 at a time

 jcl2ksh51 jcl0/JAR100.jcl   <-- reconvert 1 JCL thru all steps
 =========================       jcl0 --> jcl1 --> jcl2 --> jcl3 ?--> jcls
                               - prompts to copy to jcls or not ?

--> y <-- reply y if OK to copy to jcls overwriting prior version

reconverting JCL - All JCL in directory

 jcl2ksh51A all    <-- reconvert All JCL in directory
 =============        jcl0 --> jcl1 --> jcl2 --> jcl3 ?--> jcls
                    - prompts to continue at various points

--> cleanup PROCs, INCLUDEs,& control-cards ? --> y <-- usually reply 'y' unless very large numbers & only JCL needs reconvert

 --> recreate ctl/datactl53I
 --> n <-- reply 'n' if you have not changed any input JCLs, or the other 2
           inputs for datafile info (LISTCAT & Excel spreadsheet)

 --> copy to jcls (overwriting existing jcl/scripts) or not ?
 --> n <-- reply 'n' if you have spent considerable time editing & debugging
      - reply 'y' only early in conversion & testing
      - when enhancements are made to JCL converter & control files
      - before many JCL/scripts have been modified/tested/debugged

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

1V2. Reconvert/Recompile Test/Demo COBOL copybooks/programs

reconvert COBOL copybook - 1 at a time

 cnvMF51c cpy0/CAR100.cpy   <-- reconvert 1 COBOL copybook thru all steps
 ========================       cpy0 --> cpy1 --> cpy2 --> ?--> cpys
                              - prompts to copy to cpys ?
 --> y <-- reply y if OK to copy to cpys overwriting prior version
 --> n <-- reply 'n' if you have spent a lot of time modifying copybook in cpys
         - might reconvert to pick up some features of converter enhancements ?
         - or improving search/replace tables
         - cut & paste to combine new parts with old parts

reconvert COBOL copybooks - All in directory

 cnvMF51Ac all    <-- reconvert All copybook in directory
 ============        cpy0 --> cpy1 --> cpy2 --> ?--> cpys
                   - prompts to continue at various points
 --> copy UNIXWORK1 & UNIXPROC1 from /home/uvadm/mvstest/cpy0 ?
 --> y <-- reply y if 1st time conversion of this directory

--> cleanup complete, enter to convert --> y <-- reply y to continue

 --> copy All copybooks from cpy2 to cpys
 --> y <-- reply 'y' if OK to overwriting prior versions
         - when enhancements are made to COBOL converter & search/replace tables
         - before many copybooks have been modified/tested/debugged
 --> n <-- reply 'n' if you have spent a lot of time modifying copybooks in cpys

reconvert & recompile COBOL - 1 program at a time

 cnvMF51 cbl0/CAR100.cbl   <-- reconvert 1 COBOL program thru all steps
 =======================       cbl0 --> cbl1 --> cbl2 --> cbl3 ?--> cbls
                             - prompts to copy to cbls & recompile
 --> y <-- reply y if OK to copy to cbls overwriting prior version

 --> n <-- reply 'n' if you have spent a lot of time modifying program in cbls
         - might reconvert to pick up some features of converter enhancements ?
         - or improving search/replace tables
         - cut & paste to combine new parts with old parts

reconvert & recompile COBOL - All programs in directory

 cnvMF51A all    <-- reconvert All programs in directory
 ===========        cbl0 --> cbl1 --> cbl2 --> cbl3 ?--> cbls
                  - prompts to continue at various points
 --> cleanup complete, enter to convert
 --> y <-- reply y to continue

 --> copy All programs from cbl2 to cbls & recompile ?
 --> y <-- reply 'y' if OK to overwrite prior versions & recompile all
         - when enhancements are made to COBOL converter & search/replace tables
         - before many programs have been modified/tested/debugged
 --> n <-- reply 'n' if you have spent a lot of time modifying programs in cbls

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

1X1. Quick conversion for your JCL vs test/demos

Expedient vs Recommended

I recommend you follow the procedures documented in part 1 of MVSJCL.doc before attempting to convert your own JCL. Page '1P1' & '1P2' instruct you to setup user 'mvstest' & copy the test/demo JCLs,Procs,etc to /home/mvstest/... from /home/uvadm/mvstest/... and then run the conversions starting on page '1Q1'.

You can then execute the converted JCL/scripts starting on page '1S3'. This will give you a good understanding of how these conversions work, before starting your own conversions as documented in Part_4. Part 4 recommends you take the time to setup 'appsadm', modify profiles,& setup your own directories as documented in ADMjobs.htm.

The procedures documented here are for customers who want a quick way to to convert some of their JCL without a lot of setup required. The minimum is to setup a userid, profile, and then use the 'mvslibsdirs' script to setup the required conversion subdirs (listed on page '1A1').

The following is a modified version of the setups shown on page '1P2'. For illustration we will assume userid 'userxx' running Korn shell (vs bash). For SUN systems you may need to code '/export/home' wherever I code '/home' in the following instructions.

 #1. login as 'root'

 #2. groupadd apps        <-- setup group 'apps', if not already setup
     =============            (when uvadm was setup in install.htm)

 #3. useradd -m -g apps -s /bin/ksh userxx  <-- setup user 'userxx'
     =====================================

 #4. passwd userxx01       <-- prompts for password (userxx01 for example)
     ===============

 #5. cp -p /home/uvadm/env/stub_profile /home/userxx/.profile
     ========================================================
     - copy supplied 'stub' profile to userxx homedir & rename for ksh

 #6. Logout from root

Now login as userxx & perform your conversions as shown on next page --->

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

1X2. Quick conversion for your JCL vs test/demos

converting your JCL under userxx

 #1. login: userxx --> /home/userxx
     ==============================

 #1a. OR, login under your existing userid --> /home/yourhomedir
      ==========================================================

 #2. mkdir testlibs testdata cnvdata tmp
     ===================================
     - make superdirs to hold subdirs
     - you only need 'testlibs' to convert JCL/COBOL only
       (vs converting data & executing JCL/scripts)

 #3. cd testlibs  <-- change into testlibs (before making subdirs)
     ===========    - testlibs must be defined in profiles
                      by env-vars $TESTLIBS & $RUNLIBS

 #4. mvslibsdirs  <-- create an empty set of the conversion subdirs
     ===========    - see subdirs illustrated on page '1A1'
     - relevant subdirs for JCL conversion only are:
       ctl, parm0, parms, proc0, procs, jcl0, jcl1, jcl2,& jcl3.

 #5a. cp /home/uvadm/mvstest/ctl/* ctl    <-- copy supplied control files
      ================================
      - required for JCL & COBOL converters

 #6. copy YOUR JCLs, PROCs,& Parms into jcl0, proc0,& parm0

 #6a. cp /???/yourjcls/* jcl0
 #6b. cp /???/yourprocs/* proc0
 #6c. cp /???/yourparms/* parm0

 #7. jcl2ksh51A all        <-- run All JCL conversions
     =============

See the script listed on page '9A2' & stored at /home/uvadm/sf/IBM/jcl2ksh51A.

If you have problems, I recommend you revert to the 'step by step' method as illustrated on pages '1Q1' thru '1Q8'.

 #8. cp /home/uvadm/sfun/* /home/appsadm/sfun  <-- copy supplied functions
     ========================================
     - required to execute JCL/scripts

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

1X3. Quick conversion for your JCL vs test/demos

using 'runlibs' not in $HOME

The profiles are designed to facilitate JCL conversions & script executions under 2 conditions:

1. You have defined RUNLIBS in any homedir ($HOME), since the stub_profile provided in /home/uvadm/env/... defines RUNLIBS as follows:
   

    export RUNLIBS=$HOME/testlibs
    =============================

2. For serious conversions (vs investigation), you should define runlibs in a separate file system for access by the conversion team, for example:
   

    export RUNLIBS=/p1/apps/apps/testlibs
    =====================================

All this is explained at ADMjobs.htm#1D1 thru 1D7.

Actually the conversion scripts will work in any directory containing the subdirs documented on page '1A1', but the executions will not work unless RUNLIBS is defined as specified above.

The recommended definitions are much more flexible since it allows your various programmers to each have their own RUNLIBS or more importantly, their own RUNDATA since:

 export RUNLIBS=$HOME/testlibs
 =============================

 export RUNDATA=$HOME/testdata
 =============================

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

Part_2 JCL/COBOL/DATA Conversion Aids

Conversion Aids

Introduction & Overview

This document is intended to make you aware of the many conversion, testing, & debugging aids supplied by the Vancouver Utilities, that should help you to convert mainframes to unix/linux.

I believe you will find many of these aids essential to the success of your conversion, testing,& debugging.

These aids were originally in several documents (MVSJCL,MVSCOBOL,MVSDATA,etc). In January 2008, a separate document (CNVaids) was created to avoid the duplications in the original documents, which now have links to CNVaids.htm.

Many of these aids are illustrated using supplied test/demo files & you can run many of these once you have installed the Vancouver Utilities. These 'practice sessions' will help you when you start working on your own conversions of JCL, COBOL,& DATA files.

Links to other documents

The intention is to give you a short introduction to the various utilities available, and then give you a link to the complete documentation which could be in various other books.

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

CNVaids.doc Vancouver Utility Conversion Aids

Unix/Linux Aids - Contents

CNVaids.htm#1A1 Profiles

• profiles & related files provided in /home/uvadm/env/...
• setup user appsadm & copy to /home/appsadm/env/...

• rename as .bash_profile for bash, .profile for ksh
• defines RUNLIBS as testlibs for programmers OR prodlibs for operators
• defines RUNDATA as testdata for programmers OR proddata for operators

• defines search PATHs to libraries & data based on $RUNLIBS & $RUNDATA

CNVaids.htm#1B1 aliases

• 'alias'es make life easier
• alias rm,mv,cp to confirm remove or overwrite y/n
• cdd & cdl to switch easily between RUNDATA & RUNLIBS

CNVaids.htm#1C1 Rename scripts

• rename all files in a directory
• to lower case, to UPPer case, add/remove/change extensions
• save a lot of keystrokes working with many & long filenames

CNVaids.htm#1D1 dtree

• draw directory tree from any specified starting directory
• see demo & try it yourself

CNVaids.htm#1E1 llr

• script to list All levels of directories & files within
• useful for displaying jobtmp subdirs when testing JCL/scripts

CNVaids.htm#1F1 statdir1

• report file counts & KB used in any directory & all subdirs

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

Unix/Linux Aids - Contents

CNVaids.htm#1G1 diff

• unix/linux utility to compare 2 text files
• marvelous utility, shows changes, inserts & deletes

CNVaids.htm#1G2 alldiff

• script using 'diff' to compare all files in 2 directories
• great for confirming results of mass changes to directories
  of JCL/scripts or COBOL source programs
• this script is supplied in /home/uvadm/sf/util/alldiff2
• it employs the marvelous unix/linux system 'diff' utility,
  repeating it for each pair of files found in the 2 directories.

CNVaids.htm#1H1 grep

• powerful unix/linux tool frequently used to search for patter
  in files. For example finding all 'EXEC' program names in JCL.

CNVaids.htm#1I1 dos2unix

• convert DOS/Windows files to Unix/Linux files (remove 'CR's)

CNVaids.htm#1I1 unix2dos

• convert Unix/Linux files to DOS/Windows files (insert 'CR's)

CNVaids.htm#1J1 Vancouver Utility backup scripts scheduled by cron

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

CNVaids.doc Vancouver Utility Conversion Aids

Vancouver Utility General Purpose Aids - Contents

CNVaids.htm#2A1 uvlp__

• 'uvlp' scripts to list files at various chars per inch
• 'uvlp12' is most popular (12 chars/inch, 60 lines/page)
• uvlp12D prints Duplex at 12 cpi, uvlp12L prints Landscape
• all the 'uvlp' scripts call the 'uvlist' utility C program
  which provides page headings with filename, date last modified,
  date listed, userID, line#,& page#.
• No more wondering where a listing came from & when it was made.
• see uvlist.htm for more about 'uvlist', the 'uvlp' scripts &
  the many options (cpi,lpi,spacing,portrait,landscape,etc)

CNVaids.htm#2B1 listall

• very useful for printing all contents of a directory which
  contains many small files.
• does not page break between files, just leaves a space.
• ideal for 'parms' subdir of control cards (SORT FIELDS, etc).

CNVaids.htm#2C1 spreadA

• list all filenames in a directory 5-up. Convenient for listing
  the hundreds of JCLs,scripts,& COBOL programs in the conversion.

CNVaids.htm#2D1 cleanup

• source code maintenance utility (for JCL, COBOL, etc).
• many options to translate, clear columns, gang constants, etc
• see demo for COBOL with options explained

CNVaids.htm#2E1 verifytext

• scan all files in a subdir & report unprintable characters
• verify COBOL programs, copybooks,& JCL have no bad data

CNVaids.htm#2F1 grepsum1

• a uvcopy utility job that will sort the grep results, dropping
  duplicates, to get the desired unique list of EXEC programs.

CNVaids.htm#2G1 scan/replace

• Vancouver Utility scan/replace jobs can be more effective
  than grep/sed because you can have qualifiers present/absent
• they create an audit trail to guide subsequent edits

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

CNVaids.doc Vancouver Utility Conversion Aids

Cross-References - COBOL & JCL/scripts

CNVaids.htm#3A1 cross-refs summary

CNVaids.htm#3B1 - xrefall generate ALL Cross-Ref reports

CNVaids.htm#3B2 - xref... generate any 1 Cross-Ref report

COBOL Cross-Ref sample reports

 CNVaids.htm#3C1 - xcobcopy1 list all COPYBOOKS in any 1 PROGRAM
 CNVaids.htm#3C1 - xcobcopy2 crossref all PROGRAMS copying any 1 COPYBOOK
 CNVaids.htm#3C2 - xcobcall1 list of all CALLED-PROGRAMs in each PROGRAM
 CNVaids.htm#3C2 - xcobcall2 crossref all PROGRAMS calling any 1 CALLED-PROGRAM
 CNVaids.htm#3C3 - xcobfile2 crossref all PROGRAMS using each external-file
 CNVaids.htm#3C4 - xcobsql1 list all SQL Includes in any 1 PROGRAM
 CNVaids.htm#3C4 - xcobsql2 crossref all PROGRAMS using any 1 SQL Include

JCL Cross-Ref sample reports

 CNVaids.htm#3D1 - xkshfile1 list all DATAFILES used in any 1 ksh SCRIPT
 CNVaids.htm#3D1 - xkshfile2 crossref show all SCRIPTs using any 1 DATAFILE
 CNVaids.htm#3E1 - xkshprog1 list all PROGRAMs executed in any 1 ksh SCRIPT
 CNVaids.htm#3E1 - xkshprog2 crossref show all SCRIPTS executing any 1 PROGRAM

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

CNVaids.doc Vancouver Utility Conversion Aids

Table Summaries & Statistics - Contents

CNVaids.htm#4B1

CNVaids.htm#4C1 - statlogin1

• should appeal to Unix/Linux system administrators.
• reads system file /var/log/messages and creates table summary
  report of user logins by month & userid.

CNVaids.htm#4D1 - table2

• general purpose table summary by any desired argument
• for any file of fixed length records
• specify table arguments & acum fields by displacement & length
• see sample table summary of sales qty & amount by product#

CNVaids.htm#4D2 - table3d

• allows you to specify a 'key-word', preceding a 'target-word'.
• job searches all lines of all files in the directory
• report shows 1 line for each target-word with counts & '%'s

CNVaids.htm#4E1 - tblext1

• create table summary counts of file extensions in a subdir
  (.cbl, .cpy, .jcl, .ctl, etc)

CNVaids.htm#4F1 - recsizes1

• create summary table of record-sizes in a text file
• demo uvcopy to table analyze any item with very little code

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

CNVaids.doc Vancouver Utility Conversion Aids

COBOL aids - Contents

CNVaids.htm#3A1 - COBOL cross-refs documented with JCL/script cross-refs

CNVaids.htm#5B1 - statcbl1

• table summarize mainframe COBOL copybooks & called programs
• counts each copybook & called program found in all programs

CNVaids.htm#5C1 - cobfil51

• COBOL Files Report
• information extracted from all COBOL programs in directory
• filenames, Input/Output, Org, Access, record size, copybook
• all programmers should have a copy before starting test/debug

CNVaids.htm#5C1 - Animation

• essential for debugging MicroFocus COBOL programs
• animation illustrated for Server Express under Unix/Linux
• also illustrated for Net Express under SFU/UWIN/CYGWIN/Windows
• This discussion shows you how our JCL/script conversion
  makes it easy for you to turn animation on & off.
• Animation is fully documented in the MicroFocus manuals

CNVaids.htm#5D1 - cobmap1

• create record layouts from COBOL copybooks
• another of the favorite tools in Vancouver Utilities
• short demo here, fully documented in COBaids1.htm.

CNVaids.htm#5F1 - Micro Focus COBOL 'file status' error codes

• 2 byte codes 00-49, excluding 1st byte '9'
• codes extracted from Micro Focus website:

CNVaids.htm#5F2 - Micro Focus COBOL 'run time' error codes

• 1st byte character '9' x'39'
• 2nd byte binary x'00'- x'FF' (decimal 000-255)

 http://supportline.microfocus.com/Documentation/books/sx40sp1/smpubb.htm

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

CNVaids.doc Vancouver Utility Conversion Aids

JCL/script Test/Debug Aids - Contents

CNVaids.htm#6A1 - jobflow51

• JCL data files with COBOL file information inserted
• jobname,progname,LFD,org,access,I/O,rcsz,copybook,datafilename
• illustrates data file usage in multi-step jobs
• invaluable aid to debugging converted JCL
• short demo here, fully documented in XREFjobs.htm#Part5.

CNVaids.htm#6B1 - joblog

• run a JCL/script & capture a log file (via tee)
• names the log file by dropping the .ksh & appending .log
• writes the logfile into subdir 'joblog' in the current directory
  (creates it if not present)

CNVaids.htm#6C1 - separate datafiles

• supplied profiles make it easy for programmers
  to have their own set of testdata

CNVaids.htm#6D1 - lastgenr

• display latest generation of a file without having to go look
• you can run from anywhere, without keying long pathnames.

CNVaids.htm#6E1 - getEtime

• script to display 'job times' for last run of any JOBNAME
• retrieves jobtimes file written by last run of any JCL/script
• demos how to retrieve data fields into environmental variables

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

CNVaids.doc Vancouver Utility Conversion Aids

Data File Aids - Contents

CNVaids.htm#7A1 uvhd

• file browse/search utility for mainframe type files that do
  not have LineFeeds & may contain Packed/Binary data
• the all time favorite tool in Vancouver Utilities
• short demo here, fully documented in uvhd.htm.

CNVaids.htm#7B1 uvhdcob

• similar to uvhd, but also shows the COBOL copybook fieldnames
  beside the data contents. Excellent for verifying data
  conversions. You can see at a glance any mismatches between
  the actual data fields & the COBOL field definitions.
• short demo here, fully documented in uvhdcob.htm.
• Jan2009 'verify' command to verify character, numeric,& packed data fields

CNVaids.htm#7B2 uvhdc

• script for easier use of uvhdcob, can run from anywhere
• without specifying long pathnames for the data file
• without having to specify or know the copybookname
• short demo here, fully documented in uvhdcob.htm.

CNVaids.htm#7C1 uvcp

• data file manipulation utility
• convert file types (text, fixed, variable, indexed, Micro Focus)
• example given to correct files FTP'd from mainframe
  (drop off CR/LF added by FTP to ASCII to match COBOL fixed length)

CNVaids.htm#7D1 uvcpF2L

• script using uvcp to convert Fixed length records w/o LineFeed
• to text files with LineFeeds inserted after last nonblank
• makes it easier to use the 'uvcp' utility

CNVaids.htm#7D2 uvcpL2F

• script using uvcp to convert text files to Fixed length record
• use when you need to convert a text file for use in a mainframe
  type application that requires fixed length with no LineFeeds.

CNVaids.htm#7E1 CMPjobs

• Data File Comparisons for mainframe type files
• fixed length, variable length,& Indexed files
• originally for Y2K, now enhanced for mainframe conversions

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

CNVaids.doc Vancouver Utility Conversion Aids continued

Data File Aids - Contents (continued)

CNVaids.htm#7F1 listrec2

• list fixed length records in 100 byte segments with scale
• any unprintable characters will be translated to periods
• record length must be supplied since no LineFeeds present

CNVaids.htm#7F2 listhex2

• list fixed length records in 100 byte segments with scale
• same as listrec2, but list records in vertical hexadecimal

CNVaids.htm#7G1 gentest1

• Generate test data files
• based on COBOL copybooks

CNVaids.htm#7H1 vtocr1

 - create VTOC report for files converted from mainframe
 - provides record counts, indexed keys, etc
 (information not displayed by the usual unix/linux tools)
 - see sample report & operating instructions in MVSDATA.htm

CNVaids.htm#7I1 uvsort

• provides most SYNCSORT features at a much lower price
• up to 60 input files & 20 output files
• selects, deletes, reformats
• options to drop duplicate keys, select duplicate keys, etc
• unique option to start a new output file on key break

CNVaids.htm#7J1 uxcp

• convert mainframe EBCDIC variable length (RDW format)
  to ASCII variable length Indexed file for Micro Focus COBOL

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

CNVaids.doc Vancouver Utility Conversion Aids

Pre-Programmed uvcopy jobs

CNVaids.htm#Part_8 pre-programmed jobs (written in uvcopy code)

• Over 500 Pre-Programmed jobs are provided to perform mainframe conversions
  & help you solve data file problems not possible with unix system utilities.
• pre-programmed jobs can solve data file problems without writing code
• uvcopy is a powerful data manipulation utility that you can use to
  solve complex problems with very little code

CNVaids.htm#8B1 - tabfix1

• tabs can cause problems, such as COBOL compile failures.
• Or maybe you want to reduce the default expansion of 8 to 4
  so you can view/print the file without text on multiple lines.
• tabfix1 converts tabs to a desired number of blanks (4 default).
• alternative jobs (tabfix2 & tabfix3). tabfix2
• inserts blanks so next field at multiple of option t (default t4) tabfix3
• inserts blanks to place next field depending on tab rack

CNVaids.htm#8C1 - tolower

• translate to lower case with options to inhibit translate within
  single &/or double quotes, clear cols 1-6 &/or 73-80 (for COBOL).

CNVaids.htm#8D1 - toascii

• translate EBCDIC files to ASCII with options to specify I/O
  filenames, file types, record-sizes,& record translate areas

CNVaids.htm#8E1 - scand2

• scan all files in directory for patterns & qualifiers
• very useful to identify files that match multiple criteria
• grep is great when you only need to scan for 1 pattern
• scand2 scans for a primary pattern qualified by 1 or 2 patterns
  on same line & qualified by 1 or 2 patterns anywhere in the file.

CNVaids.htm#8F1 - acum1

• pre-programmed job to accumulate any 1 field in any datafile
• might be for a hash total to prove file validity after conversions
  or to get a 2nd opinion when COBOL reports look suspicious
• prompts for file-name, file-type, field dsplcmnt, length,& type,
• option to crossfoot a number of consecutive same-size fields.

CNVaids.htm#8G1 - cmrpt1

• customer master sales report for test file dat1/custmas1
  (used to demo both acum1 above & selectf1 below)
• report presented here, so you can verify your results
  if you run 'acum1' or 'selectf1'.

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

CNVaids.doc Vancouver Utility Conversion Aids

CNVaids.htm#8H1 - selectf1

• select records depending on field value <=> 2 specified values.
• prompts for field displacement, length, type, number, & values.
• 2 values allows you to select a range of values in any 1 field.
• option to crossfoot multi contiguous same size fields for test.

CNVaids.htm#8J1 - splitjclproc1

• split subdir of mixed JCLs & PROCs to separate subdirs
• used to separate emailed zip files of mixed JCLs & PROCs
• JCL conversion requires JCLs & PROCs in separate subdirs
• demos uvcopy ability to read directories & process files

CNVaids.htm#8K1 - splitcblcpy1

• split mixed directories of COBOL programs & copybooks
  to separate subdirs required by COBOL conversion & compile

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

CNVaids.doc Vancouver Utility Conversion Aids

Tips for users new to Unix/Linux - Contents

CNVaids.htm#9A1 vi editor tutorial for users new to unix/linux

• the essential commands to get you started

CNVaids.htm#9B1 Work in your working directory & address files thru subdirs

• working directories should have subdirs only
• all files are in subdirs

CNVaids.htm#9B2 setup a 'tmp/' subdir in your working directories

• to keep your working directory clean (no files, subdirs only)

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

Part_3. Conversion Support Files - profiles, functions, control files, etc

Part3 - Conversion Support Files

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

3A1. Conversion Support Files - profiles, functions, control files, etc

conversion support files - Overview

There are several 'conversion support files' that you should be aware of and that you may possibly need to modify to obtain optimum conversions.

I have categorized them into the groups shown above (profiles, functions, GDG functions, control files, scripts, uvcopy jobs).

Here in Part 3 we will list or give references to the more important control files that you may have to modify to optimize your conversion.

In Part_9 we will list or give references to the scripts, uvcopy jobs,& C programs, that you should not have to modify. If you think you need changes to these, please contact UV Software.

The next page illustrates the contents of the Vancouver Utilities distribution & identifies the subdirectories housing these groups.

There are certainly other important subdirs & file groups (such as src & bin, where the JCL converter is found), but you should not have to modify them.

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

3A2. Conversion Support Files - profiles, functions, control files, etc

Vancouver Utilities - contents after install

 /home/uvadm
 :-----batDOS
 :-----bin
 :-----cobs
 :-----ctl            <-- '3E0' control files used in JCL conversion
 :-----dat1
 :-----doc
 :-----dochtml
 :-----env            <-- environmental profiles ADMjobs.htm#1C1
 :-----hdr
 :-----htmlcode
 :-----lib
 :-----pf            <-- '9B0' uvcopy jobs used by JCL conversion (& much more)
 :     :-----adm
 :     :-----demo
 :     :-----IBM
 :     :-----util
 :-----sf            <-- '9A0' scripts used by JCL conversion (& much more)
 :     :-----adm
 :     :-----demo
 :     :-----IBM
 :     :-----util
 :-----sfun           <-- '3C0','5J0','5K0' functions for JCL/scripts & GDG files
 :-----src
 :-----srcf
 :-----tf
 :-----tmp
 :-----mvstest
 :     :-----testlibs
 :     :     :-----archive
 :     :     :-----cbl0
 :     :     :-----cpy0
 :     :     :-----Csub
 :     :     :-----ctl
 :     :     :-----jcl0
 :     :     :-----pf
 :     :     :-----proc0
 :     :     :-----sf
 :     :-----tmp
 :     :-----xref
 :     :-----testdata
 :     :     :-----ar, gl,
 :     :     :-----jobctl, joblog, jobtmp
 :     :     :-----rpts, sysout, tmp, wrk

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

3B1. Conversion support files - profiles

'profiles' provided in /home/uvadm/env

 /home/uvadm/env      <--- profiles provided here
 :-----stub_profile      - copy/rename to .profile (ksh) or .bash_profile (bash)
 :                       - defines RUNLIBS/RUNDATA for programmers & operators
 :-----common_profile    - common profile (called by stub_profile)
 :                         defines PATH's etc using $RUNLIBS/$RUNDATA
 :-----root_profile      - profile for root, copy to /root/.bash_profile (RedHat)
 :                         to access Vancouver Utility scripts & uvcopy jobs
 :
 /home/appsadm/env    <--- setup user 'appsadm' & copy from /home/uvadm/env/*
 :-----stub_profile      - customize & copy to homedirs .profile or .bash_profile
 :-----common_profile    - common profile (called by stub_profile)

Mainframe conversion sites should setup an application administrator userid 'appsadm', copy /home/uvadm/env/* to /home/appsadm/env,& customize profiles there depending on the locations of their libraries & data.

Do NOT customize profiles in /home/uvadm/env/... because they would be overwritten when a new version of Vancouver Utilities is installed.

We recommend the concept of 'stub' & 'common' profiles. The shell profile in each user's homedir is a 'stub' that calls 'common_profile' which are stored in /home/appsadm/env/...

1. The supplied 'stub_profile' is copied to homedirs, renamed as '.bash_profile' for bash shell (Linux) & '.profile' for Korn shell (Unix), and then modified depending on whether the user is a programmer or operator. - defines RUNLIBS as testlibs/prodlibs for programmers/operators - defines RUNDATA as testdata/proddata for programmers/operators
   
   
2. 'common_profile' then defines the 'PATH's using $RUNLIBS,$COBDIR,$UV,etc For example: export PATH=$PATH:$RUNLIBS/jcls (converted JCL/scripts). Defines software superdirs (uvadm, COBDIR, ORACLE_BASE, ORACLE_HOME, etc)
   
   
3. '$RUNDATA' determines data-file locations indirectly as follows: $RUNDATA defines the superdir housing all data-files. All JCL/scripts call a common function 'jobset51' which changes directory to $RUNDATA (cd $RUNDATA). The JCL converter inserts jobset51 at the begining of all converted JCL/scripts and then addresses all data files relative to $RUNDATA.
   

Note that stub profiles must call 'common_profile' using '.' (dot execution), which means the 'export's made in the common_profile will still be effective on return to the users profile.

This system is a big advantage for any site with multiple users, it means the sysadmin can update common_profile once in 1 place & those changes are effective for all users.

See more explanations at: http://www.uvsoftware.ca/admjobs.htm#1B2

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

3B2. profiles for Vancouver Utilities on Unix/Linux

 ADMjobs.htm#1C1 - stub_profile
      - distributed in /home/uvadm/env/...
      - copy (to user homedirs) & rename depending on the desired shell
        (.bash_profile for bash, .profile for ksh)
      - modify RUNLIBS/RUNDATA differently for programmers or operators
        define RUNLIBS as testlibs for programmers OR prodlibs for operators
        define RUNDATA as testdata for programmers OR proddata for operators
      - contains user aliases, preferences, console logging on or off
      - modify TERM & 'stty erase' character depending on user's terminal
      - modify UVLPDEST to define a laser printer near the user
      - calls common_profile

 ADMjobs.htm#1C2 - common_profile, called by stub_profile
      - defines search PATHs to libraries & data based on $RUNLIBS & $RUNDATA
      - distributed in /home/uvadm/env/...
      - you should copy to /home/appsadm/env/ & customize there
        (to avoid overwriting when new versions of VU installed)
      - contains most items, allows updates in 1 place for all
      - modify TERM & 'stty erase' character depending on user's terminal
        (distribution has TERM=linux & stty erase '^?')
      - the common_profile should be correct for the majority of users
        & the stub profiles can be modified for the exceptions
      - change 'COBDIR' depending on where you have installed Micro Focus COBOL

 ADMjobs.htm#1C6 - bashrc
      - 'rc file' distributed in /home/uvadm/env/...
      - copy (to user homedirs) & rename depending on the desired shell
        (.bashrc for bash, .kshrc for ksh)
      - master version supplied without the '.' for visibility
      - required if you invoke another shell level (console logging script)
      - carries aliases & umask which get lost on another shell level
      - you should customize & store in /home/appsadm/env/...

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

3B3. conversion support files - profiles

customizing the profile for Unix/Linux conversions

1. Modify TERM & 'stty erase' character depending on user's terminal (distribution has TERM=linux & stty erase '^?')
   

      export TERM=linux       # TERM - modify depending on your terminal
      #================       # (vt100,xterm,at386,ansi,etc)
      stty erase '^?'         # erase char - modify depending on your terminal
      #==============         #  '^?' for linux/at386, '^H' for vt100,ansi,xterm

2. Change the laser printer name defined by 'UVLPDEST' (environmental variable used by uvlist (file list scripts uvlp12, etc), and by uvhd (hexdump file investigation utility).
   

      export UVLPDEST="-dlp0"     <-- change 'lp0' to your laser printer
      =======================

3. Change 'COBDIR', the environmental variable defining where Micro Focus COBOL is installed on your system (see common_profile ADMjobs.htm#1C2).
   

      export COBDIR=/opt/microfocus/cobol  <-- change for your site
      ===================================

setting up profiles in /home/appsadm/env

Please see ADMjobs.htm re setting up profiles in /home/appsadm/env. ADMjobs.doc recommends setting up an 'appsadm' account to store the profiles so they do not get overwritten when a new version of Vancouver Utilities is installed.

ADMjobs.htm recommends copying /home/uvadm/env/* to /home/appsadm/env/... Then make any site specific modifications in appsadm/env. One significant change is to modify the stub profiles to call the common profile from appsadm not uvadm. See the details in ADMjobs.htm.

You can run the test/demo JCL conversions & executions in Part_1 without setting up appsadm, but you definitely should setup appsadm & modify profiles before starting your own JCL conversions.

The most important thing would be to modify RUNLIBS & RUNDATA depending on where you decide to store your Libraries & Data for Testing & Production.

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

3C0. conversion support functions - for JCL/scripts

GDG functions moved to Part 5

jobset51,jobend51,jobabend51 moved to Part 5

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

3C1. conversion support functions - logmsg1

logmsg1 - display with date:time:JOBID2: stamps

 # logmsg1 - function to prefix echo/print messages with jobname & date/time
 #         - calling script must have defined symbol "JOBID2"
 #         - 2 versions of logmsg (as of Oct 11/2005)
 #*logmsg1 - prints only to the screen (stdout)
 # logmsg2 - prints to screen & appends to $RUNDATA/jobmsgs/yymmdd/ymd_HMS_JOBID
 #
 # logmsg1 "x---message---x"           <-- sample command in calling JOBXXX
 # 051011:124700:JOBXXXXX x---msg---x  <-- sample output (at 12:47 Oct 11/05)
 #
 # logmsg1 "x---message---x" RV        <-- arg2/3 "RV" for Reverse Video
 # logmsg1 "x---message---x" ACK       <-- arg2/3 "ACK" to force acknowledge y/n
 # logmsg1 "x---message---x" RV ACK    <-- arg2/arg3 either sequence
 #
 # export LOGMSGACK=y  <-- profiles set LOGMSGACK=y to activate acknowledgement
 # - default in common_defines could be overridden in user profiles
 # - running JCL/scripts by cron automatically disables operator prompts
 #
 function logmsg1
 {
 REV='\033[7m'; OFF='\033[0m'; reply=x; rc=0;
 #
 if [[ "$2" = "RV" || "$3" = "RV" ]]
    then msg="$REV$(date +%y%m%d:%H%M%S):$JOBID2: ${1}$OFF"
    else msg="$(date +%y%m%d:%H%M%S):$JOBID2: $1"
 fi
 #
 if [[ ("$2" = "ACK" || "$3" = "ACK") && ("$LOGMSGACK" = "y") ]]
    then until [[ "$reply" = "y" || "$reply" = "n" ]]
         do print -r "$msg y/n?"
            tty -s || break  # test login terminal, break if run by cron
            read reply
         done
     else print -r "$msg"
 fi
 # return 1 if reply y, else 0
 if [[ "$reply" = "y" ]]; then return 1; else return 0; fi
 }

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

3C2. conversion support functions - logmsg1

 # logmsg2 - function to prefix echo/print messages with jobname & date/time
 #         - calling script must have defined symbol "JOBID2"
 #Aug02/2008 - $RUNDTTM on filenames (RUNDTTM exported by jobset51 in script)
 #Jan25/2012 - change jobmsgs/yymmdd/yymmdd_HHMMSS_JOBID2
 #                to  jobmsgs/yymmdd/HHMMSS_JOBID2
 #
 # logmsg1 - prints only to the screen (for infomsgs vs errmsgs)
 #*logmsg2 - prints to the screen & appends to 2 files (for errmsgs vs infomsgs)
 #         - $RUNDATA/jobmsgs/yymmdd:HHMMSS_$JOBID2
 #         - $APPSADM/jobmsgs/yymmdd/yymmdd:HHMMSS_$JOBID2
 # - use cron to remove $RUNDATA/jobmsgs/* files every day before batch shift
 # - use cron to remove $APPSADM/jobmsgs/... subdirs older than 10 days ?
 #
 # logmsg2 "x---message---x"           <-- sample command in calling JOBXXX
 # 051011:124700:JOBXXXXX x---msg---x  <-- sample output (at 12:47 Oct 11/05)
 #
 # logmsg2 "x---message---x" RV        <-- arg2/3 "RV" for Reverse Video
 # logmsg2 "x---message---x" ACK       <-- arg2/3 "ACK" to force acknowledge y/n
 # logmsg2 "x---message---x" RV ACK    <-- arg2/arg3 either sequence
 #
 # export LOGMSGACK=y  <-- profiles set LOGMSGACK=y to activate acknowledgement
 # - default in common_defines could be overridden in user profiles
 # - running JCL/scripts by cron automatically disables operator prompts
 #
 function logmsg2
 {
 REV='\033[7m'; OFF='\033[0m'; reply=x; rc=0;
 DTTM="$(date +%y%m%d:%H%M%S)"
 YMD="$(date +%y%m%d)"
 if [[ "$HMS" = "" ]]; then HMS="$(date +%H%M%S)"; fi
 # HMS="$(date +%H%M%S)"  #<-- defined in jobset51
 # HMS defined in jobset51, not here, else would change every logmsg2 in job
 #
 if [[ "$2" = "RV" || "$3" = "RV" ]]
    then msg="$REV$DTTM:$JOBID2: ${1}$OFF"
    else msg="$DTTM:$JOBID2: $1"
 fi
 if [[ ("$2" = "ACK" || "$3" = "ACK") && ("$LOGMSGACK" = "y") ]]
    then until [[ "$reply" = "y" || "$reply" = "n" ]]
         do print -r "$msg y/n?"
            tty -s || break  # test login terminal, break if run by cron
            read reply
         done
     else print -r "$msg"
 fi
 # append msg to jobmsgs in $RUNDATA
 # - $RUNDATA/jobmsgs/yymmdd:HHMMSS_$JOBID2
 # make subdir if it does not yet exist
 test -d $RUNDATA/jobmsgs/$YMD || mkdir $RUNDATA/jobmsgs/$YMD
 print -r "$msg" >>$RUNDATA/jobmsgs/$YMD/${HMS}_$JOBID2
 #
 # return 1 if reply y, else 0
 if [[ "$reply" = "y" ]]; then return 1; else return 0; fi
 }

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

3C3. conversion support functions - stepctl51

stepctl51 - JCL/script step control pause/go

 #!/bin/ksh
 # stepctl51 - step control function
 #           - for UNIX scripts converted from IBM MVS JCL
 #           - this KORN shell function stored in $APPSADM/sfun
 #           - see more doc at: www.uvsoftware.ca/mvsjcl.htm
 #
 # A call to this function (stepctl51) is inserted at begining of each step
 # - to provide operators with a means to pause multi-step jobs
 # - at begining of the next step, or at a specified step# (programmer debug?)
 # - scripts 'jobstop' & 'jobclear' are provided to pause & restart jobs
 #Jan14/11 - call uvtime in stepctl51 to calculate StepTimes
 #
 # jobstop jobname.ksh        <-- pause specified JCL/script at begin next step
 # ===================          - writes control file (tested by JCL/script)
 #                              - step# dflt S0000 meaning pause at all steps
 #                              - will wait wait for oprtr 'go' or 'clear'
 # jobstop jobname.ksh S0050  <-- pause job at step S0050 (step 5, inc by 10)
 # =========================    - will wait wait for oprtr 'go' or 'clear'
 #                              - 'go' does not clear, so rerun will pause again
 # jobclear jobname.ksh        <-- clear the control file (same as clear response)
 # ====================
 #
 # Step Control files are written to $RUNDATA/jobctl/...
 # - named same as JCL/script but with extension '.ctl' (vs .ksh)
 # - jobstop writes 1 line in the control file with: jobname.ksh step# date_time
 # - step# is the step# specified by oprtr as arg#2 on jobstop script command
 # - step# is S0000 if no step# spcfd on jobstop (indicates stop at all steps)
 #
 #Feb05/12 - change replies to: cont(inue), clear, endok, endab
 # - jobset51 now allows stop step#, for example 'stop=S0050'
 # - writes jobctl/jobname.ctl S0050
 # - causes stepctl at S0050+ to display: cont,clear,endok,endab
 #

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

 function stepctl51 {
 #Jan14/11 - call uvtime in stepctl51 (to save a line in JCL/scripts)
 uvtime W1D2 steptimes
 #Jan26/12 - arg2 filename disabled, now dummy
 # - JCL converter modified to report prior step for JObTimes report
 # - for pause, would need to specify prior step OK?

 # begin loop to open stepctlfile, read 1st line,& test step#
 # if open succesful and:
 # - if step# S0000, display paused msg & wait for oprtr reply
 # - if step#>S0000 & matches current step#, display pause msg & wait reply
 # - else no msg, no pause, return immediately
 alias goto="";   # ensure goto cleared in case reply endok/endab
 while ((1))
 do if [[ ! -f jobctl/$jobid2.ctl ]]; then break; fi
    exec 3< jobctl/$jobid2.ctl   # open step control file
    openstat=$?                  # capture open file status
    if (($openstat)); then break; fi
    read -u3 job start2 stop2 date
    exec 3<&-                    # close step control file
    stop=${stop2##stop=}
    if [[ $stop != S[0-9][0-9][0-9][0-9] ]]; then break; fi
    if [[ $JSTEP < $stop ]]; then break; fi
    logmsg1 "$jobid2.ksh paused by job control file: jobctl/$jobid2.ctl"
    logmsg1 "- job control record: $job $stop $date"
    logmsg1 "- waiting for reply: cont(inue), clear, endok, endab"
    read reply1; logmsg2 "stepctl51: reply1=$reply1"
    if [[ "$reply1" == "endok" ]]; then alias goto="<<S9000=A"; break; fi
    if [[ "$reply1" == "endab" ]]; then alias goto="<<S9900=A"; break; fi
    if [[ "$reply1" == "cont" ]]; then break; fi
    if [[ "$reply1" == "clear" ]]; then
       mv jobctl/$jobid2.ctl jobctl/$jobid2.ctl_old; break; fi
    sleep 1
 done
 return 0
 }
 #

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

3C4. conversion support functions - customizing

Customizing Korn shell functions

Here are some important notes re the proper use of Korn shell functions.

These functions reside in /home/appsadm/sfun defined to the Unix/Linux KORN shell by the 'FPATH' variable in your profile, for example:

 export FPATH=/home/appsadm/sfun
 ===============================

This is separate from the Unix/Linux KORN shell 'PATH' variable which is used to find normal scripts (in jcls & sf) for example:

 export PATH=$PATH:$RUNLIBS/jcls:$RUNLIBS/sf
 ===========================================

'RUNLIBS' is defined in the profile prior to PATH or FPATH. For the 'mvstest' demos this was:

 export RUNLIBS=/home/mvstest
 ============================

But for YOUR conversion & testing/production RUNLIBS might be:

 export RUNLIBS=/p1/apps/testlibs     <-- for Your Testing
 ================================
 export RUNLIBS=/p2/apps/prodlibs     <-- for Your Production
 ================================

These functions must be defined as 'autoload' in the calling scripts. Note that the JCL converter inserts the following about line #10 of each converted JCL/script.

 autoload jobset51 logmsg1 exportfile stepctl51
 ==============================================

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

3E1. conversion support files - ctl/jclunixop5

ctl/jclunixop51 JCL Conversion control file

 jclunixop51:a1b2c0d3e2f3g1i1j0k3l50m4n3o0p0r0s0t1u1v0w0x0y1z0 #<-- options
 #           =================================================
 # jclunixop51:a1b2c0d1e2f3g1i1j7k3l40m4n3o0p0r0s0t1u1v3w0x0y1z0 #<-- Sears Java
 #            ==================================================
 # Jan21/12 sears diff: d1 drop DDN LIB (not LOAD), j7 for Java,
 #                      v3 inhibit DELETE via IDCAMS & DISP=(MOD,DELETE)
 #  a1                           - append 1 on COBOL reserved word DDNAMES
 #    b1                         - generate blank line between steps
 #    b2                         - insert stepctl51 (mandatory as of Feb08/12)
 #      c1                       - program names UPPER case
 #      c2                       - filenames UPPER case (also uop=l2 jcldata52)
 #      c4                       - control card modulenames UPPER case
 #        d1                     - drop DDNAMES that begin/end with LOAD/LIB
 #        d2                     - drop DSNAMES that begin/end with load/lib
 #          e1                   - echo run command to test script w/o programs
 #          e2                   - option '-v' on cp & mv echo to console log
 #            f1                 - copy FTP commands from lib module to instream
 #            f2                 - use FTP option '-u' to inhibit authorization
 #              g0               - create new GDG's in $RUNDATA/subdir/gdgfile_
 #              g1               - new GDGs $JGDG relative move to subdir/ at EOJ
 #              g2               - new GDGs $JGDG absolute $RUNDATA/jobtmp/...
 #                 i1            - use datactl53I Indexed file for recsz,keys,etc
 #                 i0            - will try to load datactl53I into memory table
 #                   j1          - generate cmd line for JAVA (vs COBOL)
 #                   j2          - include -DDDNAME=$DDNAME for each file in step
 #                   j4          - special convert IKJEFT01, see MVSJCL.doc
 #                     k1        - FTP: insert 'open' prior to 1st line if IP#
 #                     k2        - FTP: insert 'user' prior 1st word if not cmd
 #                       l50     - limit SYSIN/SYSTSIN lines shown in script
 #                          m0   - generate exportfile modules original filename
 #                          m1   - redirect modules to $RUNDATA vs $RUNLIBS dflt
 #                          m2   - redirect SYSIN modules to $RUN____/parms/...
 #                          m4   - redirect ALL modules to $RUN____/parms/...
 #                          m8   - show original filename prior to $RUN____/parms
 #                            n0 - unrecognized JCL passed thru as is
 #                            n1 - unrecognized JCL cmntd out with '#?' cols 1-2
 #                            n2 - if any '=' present, convert any ','s to ';'s
 #                            n3 - if n2 & no '=', cmnt out with '#?' cols 1-2
 #                            n4 - convert unrecognized JCL to instream data
 #                          o1   - remove 1st segment of DDName overrides
 #                        p1     - append parm data on COBOL execution command
 #                      r0       - gen cobrun, executes .int's & allows animation
 #                      r1       - gen runw for .ints NetExpress/Windows
 #                      r2       - assume executable programs either unix/windows
 #                      r4       - assume executables in PATH (progname only)
 #                      r8       - generate 'findexec' Multi-Level program search
 #                      r16      - generate 'unikixvsam $RLX/COBOLX'
 #                      r32      - generate Natural call (natsec batch ...)
 #                    s1         - convert SORT for SYNCSORT (not uvsort)
 #                  t1           - disabled, see TOPNODE table & TOPDIRINSERT
 #                u1             - use uvcp for IEBGENER/IDCAMS REPRO (vs cp)
 #                u2             - use uxcp/uxsort (vs uvcp/uvsort) for IDX3/8
 #              v1               - inhibit DELETE via IDCAMS DELETE
 #              v2               - inhibit DELETE via DISP=(OLD/SHR/MOD,DELETE,
 #            w1                 - generate 'unikixbld -i -d $KIXDATA/filename'
 #            w2                 - insert $RUNDATA on exportfile/gen for unikix
 #          x#                   - make all indexed output files IDXf# (1,3,4,8)
 #        y1                     - generate oprtr prompt to acknowledge Abterms
 #      z1                       - custom for DST, make topnode $SYMBOL no/sep
 # jclunixop51:b2c0d1e2f1g1i1j0k3l20m4n3o0p0r0s0t1u1w0x0y1z0  #mvstest Apr2009
 # ----------------------------------------------------------------------------
 # Note re w2 - use sfun/jobset52 if you use w2
 #            - $RUNDATA/... inserted on export JTMP, RPTS,& SYOT
 # uvadm/ctl/jclunixop51 - control file for MVS JCL to Korn shell converter
 # - must copy/modify to ctl/ subdir where jclunix converter executed
 # Following lines will be inserted in scripts until :ENDINSERT
 # - except for '# ' comment (col1 '#', col2 ' ' blank)
 # '#!/.......' is 1st line output - usually '#!/bin/ksh' or '#!/bin/ksh93'
 # ------------------------------------------------------------------------
 #!/bin/ksh
 export JOBID2=JOBIDX jobid2=jobidx; scriptpath="$0"; args="$*"
 if [[ -z "$JOBID1" ]]; then export JOBID1=$JOBID2; fi
 for arg in $args; do if [[ "$arg" == *=* ]]; then export $arg; fi; done
 integer JCC=0 SCC=0 LCC=0  # init step status return codes
 autoload jobset51 jobset52 jobend51 jobabend51 logmsg1 logmsg2 stepctl51
 autoload exportfile exportgen0 exportgen1 exportgenall exportgenx
 . $APPSADM/env/stub.ini  #<-- for control-M (see notes in env/stub.ini)
 jobset51  # call function for JCL/script initialization
 goto
 S0000=A
 :ENDINSERT: - above non #comment lines inserted at begin output scripts
 # jobset51 OR jobset52 function inserted at begin each script
 # - sets up job environment: export subdirs, setup printer subdir/date
 # - RUNDATA & RUNLIBS must have been exported (in .profile or in shell)
 # - .profile must "export FPATH=$RUNLIBS/sfun" to find functions
 # - autoload declares functions called by jcl/scripts
 # - stores any restart step# in alias 'goto' (last line inserted above)
 # jobset51 - option g0 omits $RUNDATA from exportfile/gen
 #          - option g1 defines JTMP/JGDG without $RUNDATA (relative adrsng)
 # jobset52 - option g2 defines JTMP/JGDG with $RUNDATA (full path Essentis)
 #          - option w2 inserts $RUNDATA on exportfile/gen
 #          - g1/g2 same in jclunix51, dif is jobset51 or 52 here in jclunixop51
 #            OR use alt jclunixop52 with JTMP JGDG defined with $RUNDATA/...
 #
 #------------------ general purporse search/replace tables ------------------
 # REPTBL1 - replace any pattern on any INPUT (JCL before conversion to script)
 # - entries must be tidle filled & table ended by a line of all tildes
 # 01-30=search pattern, 31-60=replace pattern, 61-80=qualifier pattern
 #
 :REPTBL1:     search/replace table for input IBM JCL
 oldpattern~~~~~~~~~~~~~~~~~~~~newpattern~~~~~~~~~~~~~~~~~~~~qualifier~~~~~~~~~~~
 .DSN=~~~~~~~~~~~~~~~~~~~~~~~~~.,DSN=~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 #
 # REPTBL2 - replace any pattern on any OUTPUT (after conversion to script)
 :REPTBL2:     search/replace table for output UNIX script
 oldpattern~~~~~~~~~~~~~~~~~~~~newpattern~~~~~~~~~~~~~~~~~~~~qualifier~~~~~~~~~~~
 %%MDY~~~~~~~~~~~~~~~~~~~~~~~~~$(date +%m%d%y)~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 #
 #--------------------- filename search/replace table ---------------------
 # 01-30=search pattern, 31-60=replace pattern, 61-80=qualifier pattern
 # - entries must be tidle filled & table ended by a line of all tildes
 #
 :FILEREP1:     filename search/replace table for input JCL DSNs
 oldpattern~~~~~~~~~~~~~~~~~~~~newpattern~~~~~~~~~~~~~~~~~~~~qualifier~~~~~~~~~~~
 HIQUAL.ENVIRON~~~~~~~~~~~~~~~~app_files~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 #
 #----------------------- control table --------------------------------
 :CTLTBL:
 TOPDIRDEFAULT~~~~~~~~~~~~~~~~~data~~~~~~~~~~~~~~~~~~~~~~~~~~
 TOPDIRINSERT~~~~~~~~~~~~~~~~~~data~~~~~~~~~~~~~~~~~~~~~~~~~~
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 # TOPDIRDEFAULT - inserted if only 1 node (no High Level Qualifier) in DSN
 #               - recommend 'wrk' (1 node files likely temp files)
 # TOPDIRINSERT - if specified, will be inserted above HLQ, retaining all '.'s
 #              - some sites code this as 'mstr'
 #              - TOPNODES table would be irrelevant if TOPDIRINSERT specified
 # - if NOT specified, the existing top-node is used as a subdir within $RUNDATA
 #   use TOPNODES table to allow desired topnodes & convert unwanteds to 'misc'
 # - could use FILEREP1 table to convert any part of filenames before above
 #
 #------------------------ TOPNODES table ------------------------------
 # table of TOPNODES allowed & replacements (optional)
 # 01-30 - topnodes allowed
 # 31-60 - topnode replacements (if col 31 not '~')
 # - if 01-30 of last entry 'ALLOTHER', any others replaced by 31-60
 # - use statmvsjcl1 to create summary table of topnodes used in all JCL
 # - see www.uvsoftware.ca/mvsjcl.htm#6A2
 # - code in lower case since applied at output time(script) vs input(JCL)
 :TOPNODES:
 data~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 tape~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 ALLOTHERS~~~~~~~~~~~~~~~~~~~~~data~~~~~~~~~~~~~~~~~~~~~~~~~~
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 #Note1 - you must also code valid top-nodes in $RUNLIBS/ctl/GDGmkdirs
 #      - called by jobset51 to setup subdirs for new generations of GDG files
 #      - see listing at MVSJCL.htm#4E5
 #Note2 - above TOPNODES table used for mvstest demo conversions
 #      - verifies topnodes listed & converts others to 'misc'
 #      - you could also change existing topnodes, for example:
 # c900pali~~~~~~~~~~~~~~~~~~~~~~ali~~~~~~~~~~~~~~~~~~~~~~~~~~~
 # c900pfhb~~~~~~~~~~~~~~~~~~~~~~fhb~~~~~~~~~~~~~~~~~~~~~~~~~~~
 # c900etc~~~~~~~~~~~~~~~~~~~~~~~etc~~~~~~~~~~~~~~~~~~~~~~~~~~~
 # ALLOTHERS~~~~~~~~~~~~~~~~~~~~~misc~~~~~~~~~~~~~~~~~~~~~~~~~~
 #      - above mainframe topnodes are being shortened to 3 chars from 8
 #      - since 1st 5 chars always 'c900p'
 #
 # comment lines in output script by search patterns & qualifiers
 # - inserts '# ' in cols 1 & 2 if search & qualifier patterns present
 :CMTTBL:
 cmtsearch~~~~~~~~~~~~~~~~~~~~~cmtqualifier~~~~~~~~~~~~~~~~~~
 BLKSIZE=6300~~~~~~~~~~~~~~~~~~INPFIL~~~~~~~~~~~~~~~~~~~~~~~~
 BLKSIZE=6500~~~~~~~~~~~~~~~~~~OUTFIL~~~~~~~~~~~~~~~~~~~~~~~~
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 #
 :DROPDDN:    drop DDnames on input //DDname DD
 PROCLIB~~~~~~~~~~~~~~~~~~~~~~~
 STEPLIB~~~~~~~~~~~~~~~~~~~~~~~
 JOBLIB~~~~~~~~~~~~~~~~~~~~~~~~
 SYSLIB~~~~~~~~~~~~~~~~~~~~~~~~
 ESYLIB~~~~~~~~~~~~~~~~~~~~~~~~
 RESLIB~~~~~~~~~~~~~~~~~~~~~~~~
 DFSRESLB~~~~~~~~~~~~~~~~~~~~~~
 SORTLIB~~~~~~~~~~~~~~~~~~~~~~~
 SORTWK*~~~~~~~~~~~~~~~~~~~~~~~
 SYSUDUMP~~~~~~~~~~~~~~~~~~~~~~
 SYSABEND~~~~~~~~~~~~~~~~~~~~~~
 SYSOUX~~~~~~~~~~~~~~~~~~~~~~~~
 SYSDBOUT~~~~~~~~~~~~~~~~~~~~~~
 SYSABOUT~~~~~~~~~~~~~~~~~~~~~~
 SYSTSPRT~~~~~~~~~~~~~~~~~~~~~~
 CEEDUMP~~~~~~~~~~~~~~~~~~~~~~~
 DMPUBLIB~~~~~~~~~~~~~~~~~~~~~~
 DMNETMAP~~~~~~~~~~~~~~~~~~~~~~
 DMMSGFIL~~~~~~~~~~~~~~~~~~~~~~
 DMPRINT~~~~~~~~~~~~~~~~~~~~~~~
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 #
 # Table of DSNnames to drop if pattern matched anywhere in filename
 # - optionally qualified by EXECname in cols 31-38
 :DROPDSN:
 LINKLIB~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 LOADLIB~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 JCLLIB~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 JCL.LIB~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 PROD.LOAD~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 TEST.LOAD~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 EMER.LOAD~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 COBOLMVS~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

 STREAMW~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 LOADRUN~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 PROD.JCL~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 USERCAT~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 CATALOG~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 SORTWK~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 #
 # Table of STEP names to be #commented out
 :COMMENTSTEP:
 BMCSIU~~~~~~~~~~~~~~~~~~~~~~~~
 XMOPEN~~~~~~~~~~~~~~~~~~~~~~~~
 DSNUTILB~~~~~~~~~~~~~~~~~~~~~~
 DSNOSTEP~~~~~~~~~~~~~~~~~~~~~~
 AMUUMAIN~~~~~~~~~~~~~~~~~~~~~~
 INFOPAC~~~~~~~~~~~~~~~~~~~~~~~
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 #Oct21/07 - ADUUMAIN converted for eFunds
 #Oct11/07 - DSNUTILB,DSNOSTEP,INFOPAC added for eFunds
 # - IEFBR14 & IDCAMS removed (identified & converted in program)
 #
 # Table of symbols whose value is to be translated to lower case
 :LOWERCASE:
 APPLID~~~~~~~~~~~~~~~~~~~~~~~~
 FLEV~~~~~~~~~~~~~~~~~~~~~~~~~~
 DPC~~~~~~~~~~~~~~~~~~~~~~~~~~~
 PE~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 #
 #May06/06 - add table of 3rd party programs for EDS/RRD
 #         - to modify presumption of COBOL (construct cobrun)
 :3RDPARTY:
 CDEXEC~~~~~~~~~~~~~~$P3_CDEXEC/bin/cdexec~~~~~~~~~~~~~~~~~~~~~~~
 ENGEXE~~~~~~~~~~~~~~$P3_ENGEXE/version/Engine~~~~~~~~~~~~~~~~~~~
 FILEAID~~~~~~~~~~~~~$P3_FILEAID/bin/fileaid~~~~~~~~~~~~~~~~~~~~~
 FTUCMD~~~~~~~~~~~~~~$P3_FTUCMD/bin/ftucmd~~~~~~~~~~~~~~~~~~~~~~~
 INFOMOVR~~~~~~~~~~~~$P3_INFOMOVR/bin/infomovr~~~~~~~~~~~~~~~~~~~
 MACH~~~~~~~~~~~~~~~~$P3_MACH/bin/mach~~~~~~~~~~~~~~~~~~~~~~~~~~~
 NDMEXEC~~~~~~~~~~~~~$P3_NDMEXEC/bin/ndmexec~~~~~~~~~~~~~~~~~~~~~
 PDRFILES~~~~~~~~~~~~$P3_PDRFILES/bin/pdrfiles~~~~~~~~~~~~~~~~~~~
 PDRSW000~~~~~~~~~~~~$P3_PDRSW000/bin/sweaver~~~~~~~~~~~~~~~~~~~~
 PKZIP~~~~~~~~~~~~~~~$P3_PKZIP/bin/pkzip~~~~~~~~~~~~~~~~~~~~~~~~~
 SYNCsort~~~~~~~~~~~~$P3_SYNCsort/bin/syncsort~~~~~~~~~~~~~~~~~~~
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 # user would define the $EXECNAMEs in the common_profile
 # - as the PATH to the 3rd party apps dirs
 # - & modify above table depending on bin, etc
 # export P3_PDRSW000=/apps/StreamWeaver
 # export P3_ENGEXE=/apps/dialogue
 # - ENGEXE(dialogue) is special case with version subdir
 # - taken from DSN of MSGSYM DDN, for example
 # //MSGSYM DD DSN=STS2.EXSTREAM.V4R0M060.MESSAGES
 #
 #--------------------------------------------------------------
 #Oct28/2010 - add table of Connect:Direct code
 # export NDMAPICFG=$CDNDM/cfg/cliapi/ndmapi.cfg
 # - above NDMAPICFG will be defined in profile
 # - will replace PROCESSNAME with $JOBID2_$STEP_CD
 # - Inode --> pnode if copy from mainframe(unix) to NT, else snode
 # - Onode --> snode if copy from mainframe(unix) to NT, else pnode
 #Nov09/10 - direct option '-s' removed for debug ?
 :CONNECTDIRECT:
 logmsg1 "/search for any CD ERROR codes in \$CDNDM/cfg/msgfile.cfg"
 $CDNDM/bin/direct $CDOPTNS << EOJ
 submit maxdelay=0 PROCESSNAME
  process snode=$CDSERVER
   step1 copy from (file=$INFILE Inode)
              to   (file=$OUTFILE Onode)
  pend ;
 EOJ
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 #Nov14/10 - 'snode=CD.ZAOMNT02' replaced by 'snode=$CDSERVER'
 #         - 'export CDSERVER=CD.ZAOMNT02' added to comon_profile
 #------------------------ end jclunixop51 ---------------------------

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

3E2. conversion support files - ctl/jclunixop5

GDGmkdirs - script to make subdirs for GDG files

 # GDGmkdirs - make subdirs for new versions of GDG files
 #             saved in jobtmp/subdirs/... until Normal EOJ
 #           - by Owen Townsend, UV Software, Aug 25/2008
 #
 #Apr16/2009 - this script moved from $RUNLIBS/ctl/ to $RUNDATA/ctl/
 #           - to allow multiple $RUNDATA's to have different GDG controls
 #
 # script in $RUNDATA/ctl/... called by jobset51 (called by all JCL/scripts)
 # exportgen1 creates new GDG files in $RUNDATA/$JGDG/subdirs/...
 # - where: JGDG=$RUNDATA/jobtmp/$JOBID2/GDG/
 # - at normal EOJ, GDG files are moved to intended subdirs (NOT if Abterm)
 #
 # user must code names of his site's data file subdirs here
 # - matching the TOPNODEs table in $RUNLIBS/ctl/jclunixop51
 # - following subdirs are for the demo JCL/scripts
 #   (at www.uvsoftware.ca/mvsjcl.htm#Part_1)
 #
 #Mar14/09 - JCL converter option g1 inserts $JGDG/... on new GDGs exportgen1
 # - new option 'g0' omits $GDG/ so new GDGs in same subdir as old
 # - this GDGmkdirs script must still exist (since called by jobset51)
 #   BUT, subdirs created will not be used, since no files redirected to $JGDG/
 #
 if [[ ! -d $JTMP ]]; then
    echo "JTMP not defined or not in \$RUNDATA"; exit 81; fi
 #
 # make $JGDG/ for gdg subdirs
 # also make $GTMP/ for exportgen0/1 'ls' outputs to determine latest gen#s
 if [[ ! -d $JGDG ]]; then mkdir $JGDG; fi
 if [[ ! -d $GTMP ]]; then mkdir $GTMP; fi
 #
 # You MUST code mkdirs for the subdirs desired at your site
 #==========================================================================
 if [[ ! -d $JGDG/data ]]; then mkdir $JGDG/data; fi
 #Aug29/2011 - consolidated all datafiles into 1 directory (data/...)
 # old subdirs ar/ gl/ py/ #cmtd out, now top level node, for example:
 # $RUNDATA/ar/customer.master --> $RUNDATA/data/ar.customer.master
 #-------- old mkdirs below replaced by the 1 mkdir data above ----------
 # if [[ ! -d $JGDG/ar ]]; then mkdir $JGDG/ar; fi
 # if [[ ! -d $JGDG/gl ]]; then mkdir $JGDG/gl; fi
 # if [[ ! -d $JGDG/py ]]; then mkdir $JGDG/py; fi
 # if [[ ! -d $JGDG/mstr ]]; then mkdir $JGDG/mstr; fi
 # if [[ ! -d $JGDG/data ]]; then mkdir $JGDG/data; fi
 # if [[ ! -d $JGDG/tape ]]; then mkdir $JGDG/tape; fi
 exit 0

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

3E3. conversion support files - ctl/jclunixop5

Customizing the JCL Conversion control file

The files listed above is correct for the 'mvstest' system & will not need any changes to convert & execute the demo scripts & programs provided. However you will need to modify for your own JCL conversions. You should 1st run the 'mvstest' conversions beginning on page '1Q1' (& verify the results match the listings in section 1C1), before modifying for your own JCL conversions.

This file (ctl/jclunixop5) controls various activities performed by the jclunix51 conversion program. Several options are specified on line 1:

 jclunixop51:b0c0d1g31e1f0i1j0k1l20m1n3o0p0r0s0t1u1w0x0y1z0 #<-- options
 ==========================================================

See explanations in the full listing above on page '3E1'.

Note the search/replace tables to modify conversion for site variances you can use REPTBL2 to modify the directory name taken from the top-node of DSNs.

you can use the DROPDDN & DROPDSN tables to get rid of mainframe file definitions that have no relevance to unix/linux scripts (such as PROCLIB, STEPLIB, JOBLIB, etc)

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

3F0. Control Files for JCL Converter

datafile information sources for JCL converter

The JCL converter looks up an Indexed file 'ctl/datactl53I' to get information about the data-files (record-size, file-type, key-location/length, GDG or not). This info is required for SORTs, IDCAMS, IEBGENER, etc that are converted to uvsort & uvcp.

The mainframe JCL did not necessarily specify record-size etc, since this info could be obtained from the mainframe VTOC or LISTCAT. But there is no VTOC or LISTCAT on unix/linux, so we will supply that info to the JCL converter via an Indexed file (ctl/datactl53I). We can collect datafile info from 6 sources as described below.

 We show the uvcopy utility jobnames below the -------> lines. For example
 uvcopy job 'jcldata51' is used to create 'ctl/datajcl51', which is then
 processed/resorted by 'jcldata52' to create 'ctl/datajcl52'.

 #1. JCL -----------> ctl/datajcl51 -----------> ctl/datajcl52
          jcldata51                  jcldata52
     - datafile info extracted from all JCL
     - this is the primary & only mandatory datafile info source
     - create null files for any files below not available

 #2. LISTCAT -----------> ctl/datacat51 -----------> ctl/datacat52
              catdata51                  catdata52
     - info extracted from LISTCAT (mainframe report)
     - optional, if absent create null file >ctl/datacat52

 #3. Excel spreadsheet#1 -----------> ctl/dataxl151 ----------> ctl/dataxl152
                          xl1data51                  xldata52
     - info extracted from Excel spreadsheet #1
     - optional, if absent create null file >ctl/dataxl152

 #4. Excel spreadsheet#2 -----------> ctl/dataxl251 -----------> ctl/dataxl252
                          xl2data51                  xl2data52
     - info extracted from Excel spreadsheet #2
     - optional, if absent create null file >ctl/dataxl252

 #5. ----------> ctl/dataedt52
      editor
     - info created manually with editor (no uvcopy job involved)
     - may supply info not available from other 5 sources
     - optional, if absent create null file >ctl/dataedt52

 #6. EBCDIC datafiles -----------> ctl/datacnv51 -----------> ctl/datacnv52
                       cnvdata51                  cnvdata52
     - info created by scanning the EBCDIC datafiles
     - currently indicates only if packed/binary fields present
     - optional, if absent create null file >ctl/datacnv52

 #7. Six ...52 files above -----------> ctl/datactl53 -----------> ctl/datactl53I
                            ctldata53                  uvcp (load Indexed file)

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

3F1. Control Files for JCL Converter

sample datajcl51

 #01 &&TEMPGLM                    cntf=0016 rca=00080 rcm=00080 typ=RSF src=Jr__________ job=jgl420 prg=COBOL1
 #02 AR.CUSTOMER.MASTER           cntf=0010 rca=00000 rcm=00000 typ=RSF src=J___________ job=jar100 prg=CAR100
 #03 AR.CUSTOMER.NAMEADRS.LIST100 cntf=0002 rca=00133 rcm=00133 typ=RSF src=Jr__________ job=jar109 prg=CAR100
 #04 GL.ACCOUNT.ACNTLIST(+1)      cntf=0001 rca=00133 rcm=00133 typ=RSF src=Jr__________ job=jgl100 prg=CGL100
 #05 GL.ACCOUNT.MASTER            cntf=0001 rca=00000 rcm=00000 typ=RSF src=J___________ job=jgl900 prg=IEFBR14
 #06 GL.ACCOUNT.MASTER(+1)        cntf=0014 rca=00080 rcm=00080 typ=RSF src=Jr__________ job=jgl420 prg=COBOL2
 #07 GL.ACCOUNT.MASTER(0)         cntf=0020 rca=00000 rcm=00000 typ=RSF src=J___________ job=jgl100 prg=CGL100
 #08 GL.ACCOUNT.MASTER2           cntf=0002 rca=00080 rcm=00080 typ=ISF src=Jk__________ job=jgl360 prg=IDCAMS key=(0,6)
 #09 GL.ACCOUNT.TRANS(+1)         cntf=0005 rca=00080 rcm=00080 typ=RSF src=Jr__________ job=jgl211 prg=SORT
 #10 PY.PARMS(PPY200S1)           cntf=0001 rca=00000 rcm=00000 typ=RSF src=J___________ job=jpy200 prg=SORT
 #11 PY.TIME.&DAY..&MONTH..&YEAR  cntf=0001 rca=00000 rcm=00000 typ=RSF src=J___________ job=jpy910 prg=IEFBR14
 #12 PYTEST.PAYROLL.MASTER        cntf=0006 rca=00200 rcm=00200 typ=ISF src=Jk__________ job=jpy400 prg=IDCAMS key=(0,8)

sample datajcl51 - right side (filename omitted)

 #01 rca=00080 rcm=00080 typ=RSF src=Jr__________ job=jgl420 prg=COBOL1
 #02 rca=00000 rcm=00000 typ=RSF src=J___________ job=jar100 prg=CAR100
 #03 rca=00133 rcm=00133 typ=RSF src=Jr__________ job=jar109 prg=CAR100
 #04 rca=00133 rcm=00133 typ=RSF src=Jr__________ job=jgl100 prg=CGL100
 #05 rca=00000 rcm=00000 typ=RSF src=J___________ job=jgl900 prg=IEFBR14
 #06 rca=00080 rcm=00080 typ=RSF src=Jr__________ job=jgl420 prg=COBOL2
 #07 rca=00000 rcm=00000 typ=RSF src=J___________ job=jgl100 prg=CGL100
 #08 rca=00080 rcm=00080 typ=ISF src=Jk__________ job=jgl360 prg=IDCAMS key=(0,6)
 #09 rca=00080 rcm=00080 typ=RSF src=Jr__________ job=jgl211 prg=SORT
 #10 rca=00000 rcm=00000 typ=RSF src=J___________ job=jpy200 prg=SORT
 #11 rca=00000 rcm=00000 typ=RSF src=J___________ job=jpy910 prg=IEFBR14
 #12 rca=00200 rcm=00200 typ=ISF src=Jk__________ job=jpy400 prg=IDCAMS key=(0,8)

sample datajcl52 (jcldata51 filenames lowercased)

 #02 ar.customer.master               rca=00000 rcm=00000 typ=RSF src=J___________ job=jar100 prg=CAR100
 #03 ar.customer.nameadrs.list100     rca=00133 rcm=00133 typ=RSF src=Jr__________ job=jar109 prg=CAR100
 #04 gl.account.acntlist_             rca=00133 rcm=00133 typ=RSF src=Jr__________ job=jgl100 prg=CGL100
 #05 gl.account.master                rca=00000 rcm=00000 typ=RSF src=J___________ job=jgl900 prg=IEFBR14
 #06 gl.account.master2               rca=00080 rcm=00080 typ=ISF src=Jk__________ job=jgl360 prg=IDCAMS key=(0,6)
 #07 gl.account.master_               rca=00080 rcm=00080 typ=RSF src=Jr__________ job=jgl420 prg=COBOL2
 #08 gl.account.master_               rca=00000 rcm=00000 typ=RSF src=J___________ job=jgl900 prg=IEFBR14
 #09 gl.account.trans_                rca=00080 rcm=00080 typ=RSF src=Jr__________ job=jgl211 prg=SORT
 #10 py.parms@ppy200s1                rca=00000 rcm=00000 typ=RSF src=J___________ job=jpy200 prg=SORT
 #11 py.time.${DAY}.${MONTH}.${YEAR}  rca=00000 rcm=00000 typ=RSF src=J___________ job=jpy910 prg=IEFBR14
 #12 pytest.payroll.master            rca=00200 rcm=00200 typ=ISF src=Jk__________ job=jpy400 prg=IDCAMS key=(0,8)

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

3F2. Control Files for JCL Converter

Secondary control files for JCL converter

The primary datafile info source for the JCL converter is ctl/datajcl51 which was shown on the previous page. There are 5 other sources which are illustrated below. If you don't have them, just create null files so the conversions run OK.

The files shown here were created for the 'mvstest' demos in Part_1. You can see some more realistic examples in Part 4 where we document the procedures for converting YOUR JCL (vs the test/demo JCL).

From the summary on page '3F0' you will know that most of the 6 sources are created in 2 stages. For example LISTCAT info is 1st extracted to ctl/datacat51, which is further processed to ctl/datacat52, which is then combined with the other 5 sources to create ctl/datactl53.

For most of the 5 secondary sources, we will show only the ...51 file. The main difference is that the ...52 files are converted from mainframe standards to VU ksh script standards (lowercase, &symbols to ${SYMBOLS}, etc).

ctl/datacat51 - info from LISTCAT

 PY.PAYROLL.MASTER        rca=00128 rcm=00239 typ=IDXf8v cntr=15946788 src=__Lk________ key=(0000,0016)
 PY.TIME.CARDS            rca=00080 rcm=00080 typ=RSF    cntr=00000102 src=__Lr________
 PYTEST.PAYROLL.MASTER    rca=00256 rcm=00384 typ=IDXf8v cntr=00000537 src=__Lk________ key=(0010,0022)
 PYTEST.PAYROLL.MASTER2   rca=00128 rcm=00256 typ=IDXf8v cntr=00006597 src=__Lk________ key=(0000,0011)

ctl/datacat52 - info from LISTCAT

 py.payroll.master      rca=00128 rcm=00239 typ=IDXf8v  src=__Lk________ key=(0000,0016)
 py.time.cards          rca=00080 rcm=00080 typ=RSF     src=__Lr________
 pytest.payroll.master  rca=00256 rcm=00384 typ=IDXf8v  src=__Lk________ key=(0010,0022)
 pytest.payroll.master2 rca=00128 rcm=00256 typ=IDXf8v  src=__Lk________ key=(0000,0011)

1. LISTCAT may be the best of the 5 secondary sources of datafile information. You probably will not need any of the others if you can transfer the LISTCAT report from the mainframe & convert it as described in Part_4.
   
   
2. LISTCAT reports include all required info (record-sizes, etc) for VSAM files, but NOT for non-VSAM files. That is 1 reason for the other 4 info sources.
   

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

3F3. Control Files for JCL Converter

ctl/dataxl151 - info from Excel spreadsheet#1

 AR.CUSTOMER.MASTER      cpy=____________ rca=00256 rcm=00256 src=____Xr______
 PY.PAYROLL.MASTER       cpy=____________ rca=00320 rcm=00320 src=____Xr______
 PY.TIME.CARDS           cpy=____________ rca=00088 rcm=00088 src=____Xr______
 PYTEST.PAYROLL.MASTER   cpy=____________ rca=00384 rcm=00384 src=____Xr______

1. This Excel spreadsheet info was available at a site where LISTCAT was not, so UV Software wrote the xl1data51,52 & xl2data51,52 jobs to extract the information & combine with the other JCL & LISTCAT info to create the ctl/datactl53I info file used by the JCL converter.
   
   
2. Therefore, this is not directly transferrable to other sites, but if you have similar Excel spreadsheets, UV Software might modify the jobs to process your particular Excel spreadsheet formats.
   
   
3. Note that the copybook info 'cpy=____________' was captured here for use by the DATA conversion tools - see MVSDATA.htm#Part_4.
   
   

   ctl/dataxl251 - info from Excel spreadsheet#2

 AR.ACCOUNT.MASTER       src=______Yi____ prg=IKJEFT01
 GL.ACCOUNT.MASTER       src=______Yi____ prg=PDM00800

1. This 2nd Excel was another existing spreadsheet with several other fields that we ignored. Primarily we wanted to extract the fact that this was an 'input file that we needed to convert (vs many other inter-step work files that we did not need to convert).
   

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

3F4. Control Files for JCL Converter

ctl/dataedt52 - info created with the editor

 py.payroll.master     rca=00249 rcm=00249 typ=ISF key=(0,22)
 py.time.cards_        rca=00080 rcm=00080 typ=RSF

1. ctl/dataedt52 may be created with the editor to supply info that is not available from any of the automated sources.
   
   
2. Just create a null file for your 1st conversion. For subsequent conversions you can add info here especially for high volume files with missing info (record sizes, etc).
   
   
3. You can edit the info here in 1 place & on reconversion it will get coded on all occurrences of that file in all your JCLs, which is better than having to manually correct many separate JCL/scripts.
   
   

   ctl/datacnv51 - info from EBCDIC datafiles

 gl.account.trans_000001                      src=__________A_
 ar.customer.master                           src=__________Ap
 gl.account.acntlist_000001                   src=__________Ap
 ar.nameadrs.list100                          src=__________Ap

ctl/datacnv52 - info from EBCDIC datafiles

 ar.customer.master                           src=__________Ap
 ar.nameadrs.list100                          src=__________Ab
 gl.account.acntlist_                         src=__________Ap
 gl.account.trans_                            src=__________A_

1. ctl/datacnv51 was included only to indicate which files had 'p'acked or 'b'inary fields. This was used more for the datafile conversions than for the JCL conversions.
   
   
2. 'cnvdata51' scans the datafiles for packed/binary fields. Note that GDG filenames will have suffix '_000001' for conversion. 'cnvdata52' will modify to agree with the conventions used in the JCL/scripts to reference GDG datafiles (replace '_000001' with just a trailing '_').
   

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

3F5. Control Files for JCL Converter

ctl/datactl53 - 6 datafile info sources combined

 #02 ar.customer.master             rca=00256 rcm=00256 typ=RSF    src=J___Xr____Ap job=jar100   prg=CAR100
 #03 ar.customer.nameadrs.list100   rca=00133 rcm=00133 typ=RSF    src=Jr________Ap job=jar109   prg=CAR100
 #04 gl.account.acntlist_           rca=00133 rcm=00133 typ=RSF    src=Jr__________ job=jgl100   prg=CGL100
 #05 gl.account.master              rca=_____ rcm=_____ typ=RSF    src=J___________ job=jgl900   prg=IEFBR14
 #06 gl.account.master2             rca=00080 rcm=00080 typ=ISF    src=Jk__________ job=jgl360   prg=IDCAMS   key=(0,6)
 #07 gl.account.master_             rca=00080 rcm=00080 typ=RSF    src=Jr__________ job=jgl900   prg=COBOL24
 #08 gl.account.trans_              rca=00080 rcm=00080 typ=RSF    src=Jr__________ job=isrsupc1 prg=SORTUPC
 #09 py.parms@ppy200s1              rca=_____ rcm=_____ typ=RSF    src=J___________ job=jpy200   prg=SORT
 #10 py.time.${DAY}.${MONTH}.${YEAR} rca=_____ rcm=_____ typ=RSF    src=J___________ job=jpy910   prg=IEFBR14
 #11 pytest.payroll.master          rca=00384 rcm=00384 typ=IDXf8v src=JkLkXr______ job=jpy400   prg=IDCAMS   key=(0010,0022)

ctl/datactl53a - omitting filenames to show right side

 #02 rca=00256 rcm=00256 typ=RSF    src=J___Xr____Ap job=jar100   prg=CAR100
 #03 rca=00133 rcm=00133 typ=RSF    src=Jr________Ap job=jar109   prg=CAR100
 #04 rca=00133 rcm=00133 typ=RSF    src=Jr__________ job=jgl100   prg=CGL100
 #05 rca=_____ rcm=_____ typ=RSF    src=J___________ job=jgl900   prg=IEFBR14
 #06 rca=00080 rcm=00080 typ=ISF    src=Jk__________ job=jgl360   prg=IDCAMS   key=(0,6)
 #07 rca=00080 rcm=00080 typ=RSF    src=Jr__________ job=jgl900   prg=COBOL24
 #08 rca=00080 rcm=00080 typ=RSF    src=Jr________A_ job=isrsupc1 prg=SORTUPC
 #09 rca=_____ rcm=_____ typ=RSF    src=J___________ job=jpy200   prg=SORT
 #10 rca=_____ rcm=_____ typ=RSF    src=J___________ job=jpy910   prg=IEFBR14
 #11 rca=00384 rcm=00384 typ=IDXf8v src=JkLkXr______ job=jpy400   prg=IDCAMS   key=(0010,0022)

1. ctl/datactl53 is the final result of 6 possible sources sorted together collecting keyword info on the right side of 1 entry per unique filename.
   
   
2. ctl/datactl53 is a valuable list of all datafiles & their attributes. I suggest you list it for handy reference during & after conversion. You might use the 'uvlp14LD' script for Landscape Duplex.
   

    uvlp14LD ctl/datactl53
    ======================

3. ctl/datactl53 is loaded into Indexed file ctl/datactl53I for use by the JCL converter. Script 'jcldata5A' is the easiest way to load the Indexed file. It runs jcldata51, jcldata52, ctldata53,& a uvcp to load the Indexed file. You must have created the other 5 data...52 info files OR made null files.
   

    jcldata5A all
    =============

4. jcldata5A is called by 'jcl2ksh51A' the script that performs all steps of converting all JCL, PROCs, parms to Korn shell scripts.
   

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

Part_4 Converting 'YOUR' MVS JCL to Korn shell scripts

Part 4 Contents

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

Part 4 Converting 'YOUR' MVS JCL to Korn shell scripts

Part 4 Contents (continued)

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

Part 4 Converting 'YOUR' MVS JCL to Korn shell scripts

Part 4 Contents (continued)

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

4A1. Converting YOUR MVS JCL to Korn shell scripts

Introduction & Overview

Part 4 is intended to present a plan for you to follow in converting 'YOUR' JCL (vs the test/demo conversions illustrated in Part_1.

Your JCL conversion will be the primary focus in Part 4, but we will refer you to other parts of the documentation for the many other procedures required to make the entire conversion successful.

In fact this (Part 4 of MVSJCL.doc) is probably your best roadmap to follow when planning & executing your conversion.

Note that you must follow the step by step method for your 'first' conversion of all JCL, but for subsequent conversion you may use the handy scripts provided to convert all JCL with 1 command.

Part 4 also gives the operating instructions for the scripts to re-convert All COBOL,& DATA files, but you must use the step by step method for the 'first' conversions as documented in MVSCOBOL.htm & MVSDATA.htm.

before digging in to Part 4

Before you dig into this very detailed conversion plan, I recommend you review the very concise '25 point preparation plan' presented in uvprices.htm#G1.

Also review the 'optional conversions' described at uvprices.htm#K0.

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

4B1. Converting YOUR MVS JCL to Korn shell scripts

Planning Your conversion

Part 4 is intended to present a plan for you to follow in converting 'YOUR' JCL (vs the test/demo conversions illustrated in Part_1.

The Vancouver Utilities makes the conversions fast. But since you must test all JCL/scripts & COBOL programs, you should allow from 6 months to 1 year for the conversion project.

We recommend having UV Software personnel onsite for training & conversion assistance. We suggest an initial 4 weeks & perhaps another 3 or 4 weeks 2 or 3 months later.

setup hardware & install unix/linux

We recommend Red Hat Enterprise Linux, but the Vancouver Utilities will run under most popular unix systems (SUN, AIX, HP, etc).

Please see ADMjobs.htm#Part2 for some suggestions about setting up your unix/linux system (RAID arrays, disc partitioning, etc).

We strongly recommend Micro Focus COBOL and please ensure that your unix/linux O/S is certified by Micro Focus COBOL.

Setup users & groups for programmers & operators

1. You might setup group 'apps' for all users involved in the conversion project. You need a common group so users can work on a common set of JCL/scripts & programs. Security is extended to the group level (directories 775 & files 664).
   
   
2. Setup userids for your programmers & operators (all with group 'apps')
   
   
3. Also setup userid 'uvadm' for the Vancouver Utilities administrator & setup userid 'appsadm' for your applications administrator.
   
   
4. We are not setting up profiles until the Vancouver Utilities are installed (next page), because the recommended profiles are included on the VU distribution media.
   

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

4B2. Converting YOUR MVS JCL to Korn shell scripts

Installing the Vancouver Utilities

Please see install.htm for detailed instructions to install the Vancouver Utilities from the distribution CD & to compile the C programs on your machine.

setup 'profiles' for uvadm,appsadm,& your team

The profiles are supplied in /home/appsadm/env/... & consist of multiple parts.

1. stub_profile - copy to user homedirs overwriting .profile or .bash_profile - defines RUNLIBS as testlibs for programmers OR prodlibs for operators - defines RUNDATA as testdata for programmers OR proddata for operators
   
   
2. common_profile - called by 'stub_profile' - defines search PATHs to libraries & data based on $RUNLIBS & $RUNDATA
   
   
3. 'rc' files (.bashrc/.kshrc) - copy to user homedirs. 'rc' files reestablish aliases, that are disabled if console logging is activated.
   

See the profiles listed begining at ADMjobs.htm#1B1

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

4B3. Converting YOUR MVS JCL to Korn shell scripts

profiles

Profiles are split to 2 parts (stub_profile & common_profile). Profiles are supplied in /home/uvadm/env/... but should be copied to /home/appsadm/env/... & modified there depending on site requirements.

Note that the 'stub_profile' is copied to each users homedir & renamed as .bash_profile for Linux & .profile for unix. You must then modify the stub_profile definitions of RUNLIBS & RUNDATA depending on whether the user is a programmer or an operator.

Please see the profile listings at ADMjobs.htm#1C1 but here are some examples of critical definitions extracted from common_defines & stub_profile.

common_defines

      export TESTLIBS=/p1/apps/testlibs
      export TESTDATA=/p1/apps/testdata
      export PRODLIBS=/p2/apps/prodlibs
      export PRODDATA=/p2/apps/proddata
      export CNVDATA=/p4/apps/cnvdata

stub_profile

RUNLIBS, RUNDATA,& CNVDATA are assigned in the .profile or .bash_profile of programmers & operators. see the stub_profile listed at ADMjobs.htm#1C1. stub_profiles should use only the $symbols defined in common_defines.

 export RUNLIBS=/p1/apps/testlibs     <-- for programmers
 export RUNDATA=/p1/apps/testdata
 export CNVDATA=/p1/apps/cnvdata

 export RUNLIBS=/p2/apps/prodlibs     <-- for operators
 export RUNDATA=/p2/apps/proddata

 export RUNLIBS=$HOME/testlibs   <-- for programmers, who wish to test
 export RUNDATA=$HOME/testdata       in their homedir, only for education
 export CNVDATA=$HOME/cnvdata        & exception testing (no development)

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

4C1. Converting YOUR MVS JCL to Korn shell scripts

Directories for test/demo conversions in Part_1

Up to this point the directory design was intended only to test/demo the UV conversion procedures using the supplied JCL & PROCs. In Part_1 we setup our test/demo directories in homedir (mvstest) for convenience & simplicity.

 /home
 :----user1
 :----user2
 :-----etc-
 :----mvstest
 :    :----testdata     <-- $RUNLIBS for demo JCL conversions in Part_1
 :    :    :----cbls
 :    :    :----jcls
 :    :    :-----etc-
 :    :----testdata     <-- $RUNDATA for demo JCL conversions in Part_1
 :    :    :----ar
 :    :    :----gl
 :    :    :----etc

You should not use homedirs for your actual conversion, testing,& production for several reasons which will be explained below.

I recommend separate file systems for test-libraries, test-data, production-libraries, & production-data. This gives you a lot more flexibility for backups and any required restores. Separate file systems protects other file systems in case of runaway programs filling up the data file system. Other file systems are also protected against corruption in any 1 file system.

We have already explained how RUNLIBS & RUNDATA are defined in the profiles to control the locations of the active libraries (test or production) and the locations of the active data (test or production). From the following pages you can see that RUNLIBS & RUNDATA for programmers & production personnel might be:

 export RUNLIBS=/p1/apps/testlibs   <-- testlibs/testdata for programmers

export RUNDATA=/p1/apps/testdata

 export RUNLIBS=/p2/apps/prodlibs   <-- prodlibs/proddata for operators

export RUNDATA=/p2/apps/proddata

/p1, /p2, /p3, /p4 are file system mount points, which could be different on your system, but all our conversion scripts & generated JCL/scripts will work without change, since they all depend on RUNLIBS & RUNDATA, which are defined in the profiles of programmers & operators.

The next few pages will illustrate the details of testlibs/testdata & prodlibs/proddata, and also describe the uses of /p3 for backup/restore, and /p4 for data conversions.

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

4C2. Converting YOUR MVS JCL to Korn shell scripts

Directories for YOUR Conversion,Testing,& Production

 /root
 /...              <-- unix/linux O/S directories
 /...
 /home             <-- home directories
 :----user1
 :----user2
 :----etc---
 :
 /p1/apps               <-- /p1 file system mount point
 :----testlibs       - test-libraries & test-data
 :----testdata
 /p2/apps               <-- /p2 file system mount point
 :----prodlibs       - production-libraries & production-data
 :----proddata
 /p3/apps               <-- /p3 file system mount point
 :----backup         - backup & restore directories
 :----restore
 /p4/apps               <-- /p4 file system mount point
 :----cnvdata        - data conversion directories

Note that this file design is the first practical design that you would want to use for your development & production. The earlier test/demos used home directories (/home/mvstest) which should not be used for your development & production because:

1. The /home file system would not usually have sufficient space allocated for your large data files.
   
   
2. You should have separate file systems to protect against runaway COBOL programs filling up the entire file system, rather than just the data file system. Other file systems are also protected against corruption in any 1 file system.
   
   
3. You should have separate file systems designed to facilitate your backup & restore procedures. You should be able to do backup/restores separately for testlibs, testdata, prodlibs,& proddata.
   
   
4. Separate file systems facilitate writing backup tapes with multiple archives. The restore script allows you to restore just the desired archive, rather than the entire tape, saving time & disc space.
   
   

   Alternative File System Designs

The next few pages will present the details of this 1st practical yet simple file system design. Also see alternative file designs in ADMjobs.htm#Part_2 that discuss provisions for multiple companies &/or multiple separate applications. ADMjobs also gives a brief description of using RAID for your O/S & applications.

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

4C3. Converting YOUR MVS JCL to Korn shell scripts

Libraries for Your Conversion & Testing

Please understand the preceding notes about these directory structures.

       '--MF--' marks subdirs transferred from your MainFrame for conversion

       '--UV--' marks control files & functions supplied by UV Software

 /p1/apps
 :-----testlibs        <-- RUNLIBS=$TESTLIBS=/p1/apps/testlibs
 :     :------Csub       - C subroutines for COBOL programs
 :     :--MF--cbl0       - your COBOL programs transferred from mainframe
 :     :------cbl1       - cleaned up, cols 1-6 & 73-80 cleared, etc
 :     :------cbl2       - cnvMF5 converts mainframe COBOL to Micro Focus COBOL
 :     :------cbl3       - optional to convert accept sysin to read from a file
 :     :------cbls       - copy here (standard source library) before compiling
 :     :------cblst      - cobol source listings from compiles
 :     :------cblx       - compiled COBOL programs (.int's)
 :     :--MF--cpy0       - for COBOL copybooks
 :     :------cpy1       - cleaned up, cols 1-6 & 73-80 cleared, etc
 :     :------cpy2       - cnvMF5 converts mainframe COBOL to Micro Focus COBOL
 :     :------cpys       - copy here (standard copybook library)
 :     :------ditto0     - DITTO jobs from MainFrame
 :     :------ditto1     - DITTO jobs cleaned up
 :     :------dittos     - DITTO jobs converted to uvcopy
 :     :------ezt0       - EasyTrieve jobs from MainFrame
 :     :------ezt1       - EasyTrieve jobs cleaned up
 :     :------ezts       - EasyTrieve jobs converted to uvcopy
 :     :------ftp        - subdir for FTP transfers
 :     :--UV--ctl        - conversion control files (jclunixop51, datactl53I)
 :     :------include1   - optional (PROC expansion allows include files)
 :     :--MF--jcl0       - your JCLs transferred from mainframe
 :     :------jcl1       - intermediate conversion 73-80 cleared
 :     :------jcl2       - PROCs expanded from procs
 :     :------jcl3       - JCLs converted to Korn shell scripts
 :     :------jcls       - copy here manually 1 by 1 during test/debug
 :     :------jobparmx1  - datacards extracted from JCL/scripts (date-stamped)
 :     :------jobparmx2  - datacards extracted from JCL/scripts (no datestamps)
 :     :------maps       - 'cobmaps' record layouts generated from copybooks
 :     :------pf         - uvcopy jobs to replace utilities (easytrieve,etc)
 :     :--MF--proc0      - your PROCs transferred from mainframe
 :     :------procs      - will be merged with jcl1, output to jcl2
 :     :------sf         - for misc scripts you may wish to write
 :     :------tmp        - tmp subdir used by various conversions
 :     :------xref       - cross-references (see XREFjobs.htm)

 mvslibsdirs       <-- script to create above subdirs
 ===========

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

4C4. Converting YOUR MVS JCL to Korn shell scripts

DATA Directories for Your Testing

 /p1/apps
 :-----testdata             <-- RUNDATA=$TESTDATA=/p1/apps/testdata
 :     :-----ar               - option to use top-node as subdir
 :     :-----gl
 :     :-----py
 :     :-----ctl               - GDG control file
 :     :-----jobctl            - for jobstop stop at begin each step for debug
 :     :-----joblog            - Job Debug logs stored here (by joblog script)
 :     :-----jobmsgs           - progress msgs (step begin, end Normal/AbTerm)
 :     :-----jobparms1         - current datacards from $RUNLIBS/jobparmx1 at 6PM
 :     :-----jobparms2         - datacards from $RUNLIBS/jobparmx2 at 6PM
 :     :-----jobtmp            - job temporary files
 :     :-----mstr              - could put all datafiles in 1 subdir
 :     :-----pf                - user written uvcopy jobs
 :     :-----rpts            <-- reports
 :     :-----sf                - user written Korn shell scripts
 :     :-----sysout            - COBOL DISPLAY upon SYSLST reports
 :     :-----tape            <-- tape files reassigned to disc by JCL converter
 :     :-----tmp               - misc temp files & sort work files
 :     :-----wrk             <-- work files (inter-step)

 mvsdatadirs       <-- script to create above subdirs
 ===========

shortcuts to convert a few JCL ? (preliminary)

See page '1X1', if you need to do a quick preliminary conversion of a few of your JCLs before you invest the time & effort that should be expended when you launch your mainframe conversion project.

You could setup the 'testlibs' superdir in a new user homedir or within your own homedir & use script 'mvslibsdirs' to setup the required subdirs. Page '1X2' uses script 'jcl2ksh51A' to perform all steps of JCL conversion.

BUT again, we strongly recommend you follow these detailed procedures in here in Part 4, to perform any serious mainframe conversion project.

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

4C5. Converting YOUR MVS JCL to Korn shell scripts

DATA Directories for Your Testing

 /p1/apps
 :-----testdata             <-- RUNDATA=$TESTDATA=/p1/apps/testdata
 :     :-----ar               - option to use top-node as subdir
 :     :     :-----customer.master
 :     :     :-----sales.items
 :     :-----gl
 :     :     :-----account.master
 :     :     :-----account.trans
 :     :-----py
 :     :     :-----payroll.master
 :     :     :-----time.cards
 :     :-----ctl               - GDG control file
 :     :-----joblog            - Job Debug logs stored here (by joblog script)
 :     :-----jobmsgs           - vital/error messages here (date/time stamped)
 :     :-----jobparms1         - current datacards from $RUNLIBS/jobparmx1 at 6PM
 :     :-----jobparms2         - datacards from $RUNLIBS/jobparmx2 at 6PM
 :     :-----jobtmp            - job temporary files
 :     :     :-----jobname     - subdir by jobset51 function
 :     :     :     :-----S0080_E212540C  - for job temp files (SYSINs, GDGs)
 :     :-----mstr              - could put all datafiles in 1 subdir
 :     :     :-----ar.customer.master  (vs using topnode subdir as above)
 :     :     :-----ar.sales.items
 :     :-----pf
 :     :-----rpts              - reports
 :     :     :-----070218      - subdir for today's reports
 :     :     :-----070219      - created by function jobset51 on 1st run of day
 :     :     :     :-----JAR200_S0050_E212540C_074648
 :     :-----sf
 :     :-----sysout
 :     :-----tape              - tape files reassigned to disc by JCL converter
 :     :     :-----070218      - subdir for today's tape file outputs
 :     :     :-----070219
 :     :-----tmp
 :     :-----wrk               - work files (inter-step)

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

4C6. Converting YOUR MVS JCL to Korn shell scripts

Libraries for Your Production

 /p2/apps
 :-----prodlibs          <-- RUNLIBS=$PRODLIBS=/p2/apps/prodlibs
 :     :-----cbls          - end point for converted COBOL programs
 :     :-----cblst         - cobol source listings from compiles
 :     :-----cblx          - compiled COBOL programs (.int's)
 :     :-----cpys          - converted, ready for compiles
 :     :-----jcl3          - JCLs converted to Korn shell scripts
 :     :-----jcls          - copy here manually 1 by 1 during test/debug
 :     :-----jobparmx1     - datacards extracted from JCL/scripts (date-stamped)
 :     :-----jobparmx2     - datacards extracted from JCL/scripts (no datestamps)
 :     :-----pf            - uvcopy jobs to replace utilities (easytrieve,etc)
 :     :-----sf            - for misc scripts you may wish to write
 :     :-----tmp           - tmp subdir used by various conversions

Please compare these production libraries to the conversion & testing libraries on the preceding page. Note that many original mainframe & intermediate conversion subdirs have been dropped, retaining only the fully converted subdirs of COBOL programs, copybooks,& JCL(now Korn shell scripts).

DATA Directories for Your Production

 /p2/apps
 :-----proddata             <-- RUNDATA=$PRODDATA=/p2/apps/proddata
 :     :-----ar               - option to use top-node as subdir
 :     :     :-----customer.master
 :     :     :-----sales.items
 :     :-----gl
 :     :     :-----account.master
 :     :     :-----account.trans
 :     :-----ctl               - GDG control file
 :     :-----joblog            - Job Debug logs stored here (by joblog script)
 :     :-----jobmsgs           - vital/error messages here (date/time stamped)
 :     :-----jobparms1         - current datacards from $RUNLIBS/jobparmx1 at 6PM
 :     :-----jobparms2         - datacards from $RUNLIBS/jobparmx2 at 6PM
 :     :-----jobtmp            - job temporary files
 :     :     :-----jobname1    - subdir jobname created at job init by jobset51
 :     :-----mstr              - master files (or topnode subdirs as above)
 :     :-----pf
 :     :-----rpts              - reports
 :     :     :-----070218      - subdir for today's reports
 :     :-----sf
 :     :-----sysout
 :     :-----tape              - tape files reassigned to disc by JCL converter
 :     :     :-----070218      - subdir for today's tape file outputs
 :     :-----tmp
 :     :-----wrk               - work files (inter-step)

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

4C7. Converting YOUR MVS JCL to Korn shell scripts

Backup/Restore Directories

 /p3/apps/backup
 :-----homedirs             <-- $HOMEDIRS backup from last night
 :     :-----appsadm          - showing only 1 user to save lines
 :     :     :-----ctl          & showing only a few subdirs in 1st user
 :     :     :-----env
 :     :     :-----logs
 :     :     :-----...
 :-----homedirs-1           <-- $HOMEDIRS backup from 2 nights ago
 :     :-----...same as above...
 :-----proddata             <-- $PRODDATA backup from last night
 :     :-----ap
 :     :-----ar
 :     :-----gl
 :     :-----rpts
 :     :-----wrk
 :-----proddata-1           <-- $PRODDATA backup from 2 nights ago
 :     :-----...same as above...
 :-----prodlibs             <-- $PRODLIBS backups from last night
 :     :-----cbls
 :     :-----cpys
 :     :-----ctl
 :     :-----jcls
 :     :-----parms
 :-----prodlibs-1           <-- $PRODLIBS backup from 2 nights ago
 :     :-----...same as above...
 :-----zip                  <-- last nights backup (only)
 :     :-----homedirs_070529_0301.zip
 :     :-----proddata_070529_0302.zip  <-- sample for May 29/2007
 :     :-----prodlibs_070529_0303.zip
 :     :-----...
 :-----Day                  <-- Daily backups in .zip files for last 40 days
 :     :-----homedirs_070419_0301.zip
 :     :-----proddata_070419_0302.zip  <-- 40 days ago = April 19/2007
 :     :-----prodlibs_070419_0303.zip
 :     :-----...(39 sets not shown)
 :-----Month                <-- Monthly backups in .zip files for last 15 months
 :     :-----homedirs_060201_0301.zip
 :     :-----proddata_060201_0302.zip  <-- 15 months ago = Feb 1/2006
 :     :-----prodlibs_060201_0303.zip
 :     :-----...(14 sets not shown)
 :-----Year                 <-- Yearly backups in .zip files for last 7 years
 :     :-----homedirs_000501_0301.zip
 :     :-----proddata_000501_0302.zip  <-- 7 years ago = Jan 1/2000
 :     :-----prodlibs_000501_0303.zip
 :     :-----...(6 sets not shown)

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

4C8. Converting YOUR MVS JCL to Korn shell scripts

Data Conversion Directories

 /p4/apps
 :-----cnvdata            - $CNVDATA=/tax/cnvdata ($symbol for PATH independence)
 :     :------archive     - copy unwanted files here for later deletion
 :     :--MF--cpys      <-- COBOL copybooks
 :     :--MF--ctl       <-- control files (LISTCAT from the mainframe)
 :     :--MF--d0        <-- data files FTP'd from mainframe (variable length)
 :     :------d0ebc       - filenames lower case, '.clus.vseprd' dropped
 :     :------d1ebc       - converted to fixed length for conversion
 :     :------d2asc       - converted to ASCII (packed/binary preserved)
 :     :------d3ebc       - possible convert back to EBCDIC to verify
 :     :------errs        - error reports from conversion utilities
 :     :------maps        - copybooks converted to record layouts
 :     :------pf          - misc uvcopy jobs
 :     :------pfv1        - uvcopy jobs to convert varlth to fixlth
 :     :------pfv2        - copied here for execution
 :     :------pfx1        - uvcopy skeleton jobs generated from 'maps'
 :     :------pfx1a       - uvcopy instructions extracted from pfx1 jobs
 :     :------pfx2        - uvcopy jobs completed, datafilenames (vs cpybknms)
 :     :------pfx3        - uvcopy jobs copied here for modify/execute
 :     :------pfx3.bak    - backup before regens to recover modified R/T code
 :     :------pfx4        - optional jobs to convert back to EBCDIC for verify
 :     :------sf          - misc scripts
 :     :------sfload      - scripts to copy/sort/load d2asc/... to $TESTDATA/mstr
 :     :------sfloadalt   - alternates (must be only 1 script per file in sfload)
 :     :------stats       - reports to assist multi record type file conversions
 :     :------tmp         - misc files here (keep working dir clean, rm daily)
 :     :------tmp1        - misc files (remove weekly vs daily)

       '--MF--' indicates subdirs receiving files from the mainframe

 cnvdatadirs     <-- script to create subdirs shown above
 ===========

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

4C9. Converting YOUR MVS JCL to Korn shell scripts

Programmer & Operator Logins

The preceding pages have discussed our file design, which might be summarized as follows:

 /home             <-- home directories
 :----prgmr1
 :----prgmr2
 :----oper1
 :----oper2
 :
 /p1/apps                 <---- /p1/apps file system mount point
 :-----testlibs        <-- RUNLIBS=$TESTLIBS=/p1/apps/testlibs
 :     :-----cbls        - COBOL programs
 :     :-----jcls        - JCL/scripts
 :     :---etc---        - see other subdirs at ADMjobs.htm#2B1
 :-----testdata      <---- RUNDATA=$TESTDATA=/p1/apps/testdata
 :     :-----mstr        - data files (or use topnodes as subdirs)
 :     :-----jobtmp      - job temporary files
 :     :---etc---        - see other subdirs at ADMjobs.htm#2B2
 :
 /p2/apps                 <---- /p2/apps file system mount point
 :-----prodlibs        <-- RUNLIBS=$PRODLIBS=/p2/apps/prodlibs
 :     :-----cbls        - COBOL programs (production)
 :     :-----jcls        - JCL/scripts (production)
 :     :---etc---
 :-----proddata
 :     :-----mstr        - data files (or use topnodes as subdirs)
 :     :-----jobtmp      - job temporary files
 :
 /p3/apps                 <---- /p3/apps file system mount point
 :-----backup            - backup & restore directories
 :-----restore
 :
 /p4/apps                 <---- /p4/apps file system mount point
 :-----cnvdata           - data conversion directories
 :     :----d1ebc        - EBCDIC data files from mainframe
 :     :----d2asc        - converted to ASCII (preserving packed)

RUNLIBS/RUNDATA defs in 'stub_profiles'

export RUNLIBS=/p1/apps/testlibs <-- stub_profile_test for programmers export RUNDATA=/p1/apps/testdata

export RUNLIBS=/p2/apps/prodlibs <-- stub_profile_prod for operators export RUNDATA=/p2/apps/proddata

aliases in profiles for quick change

 alias cdl='cd $RUNLIBS' <-- /p1/apps/testlibs(prgmr) or /p2/apps/prodlibs(oprtr)
 alias cdd='cd $RUNDATA' <-- /p1/apps/testdata(prgmr) or /p2/apps/proddata(oprtr)

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

4D1. Converting YOUR MVS JCL to Korn shell scripts

Copying VU control files & functions to Your $TESTLIBS

You must copy some control files (supplied with Vancouver Utilities) over to your $TESTLIBS/ctl. Here is a cut-down version of the testlibs dtree shown on page '4C3'. We have omitted most subdirs & to highlight the 'ctl' subdirs.

 /p1/apps
 :-----testlibs       <-- RUNLIBS=$TESTLIBS=/p1/apps/testlibs
 :     :-----cbl0
 :     :-----cpy0
 :     :--*--ctl      <-- control files (cobdirectives,datactl53I,jclunixop51)
 :     :-----jcl0
 :     :
 :-----testdata       <-- RUNDATA=$TESTDATA=/p1/apps/testdata
 :     :-----ar
 :     :--*--ctl      <-- control files (gdgctl53,gdgctl53I.dat,gdgctl53I.idx)
 :     :-----gl
 :     :-----jobtmp
 :     :-----wrk

Copying VU ctl/... to Your $TESTLIBS

 #1. Login as yourself or appsadm --> your homedir or /home/appsadm

 #2. cdl  --> $RUNLIBS

 #3. mvslibsdirs   <-- setup LIBRARY subdirs for JCL & COBOL conversions
     ===========     - if not already setup (see page '4C3')

 #4. cdd  --> $RUNDATA

 #5. mvsdatadirs   <-- setup DATA subdirs for JCL/COBOL executions
     ===========     - if not already setup (see page '4C3')

 #6. copymvsctls   <-- copy supplied control files to $TESTLIBS/ctl/...
     ===========     - see the 'copymvsctls' script listed on the next page:

setup appsadm profiles & functions

• you must setup appsadm at ADMjobs.htm#1D1 thru 1D4.
• you must setup the profiles as per ADMjobs.htm#1B1 - 1C7
• RUNLIBS defined in /home/appsadm/env/stub_profile
• RUNLIBS=/p1/apps/testlibs in examples above, setup appropriate for your site
• you must copy the functions called by JCL/scripts (jobset51,exportgen0,etc)
  to the directory defined by 'FPATH' in the profiles

     export FPATH=/home/appsadm/sfun
     ===============================

 #7. cp /home/uvadm/sfun/* /home/appsadm/sfun <-- copy supplied functions
     ========================================   - required to execute JCL/scripts

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

4D2. Converting YOUR MVS JCL to Korn shell scripts

script to copy supplied control files & functions

 # copymvsctls - copy Vancouver Utility control files & functions
 #               required to convert mainframe JCL & COBOL
 #             - by Owen Townsend, UV Software, Oct 04/2008
 #
 # Run this script after creating testlibs/subdirs for JCL/COBOL conversion
 #
 # 1. login        <-- login (to your homedir, or as mvstest, or ?)
 # 2. mvstestdirs  <-- setup subdirs required for JCL/COBOL conversion
 # 3. cdl          <-- alias for 'cd $RUNLIBS or 'cd $TESTLIBS'
 # 4. mvslibsdirs  <-- make about 25 subdirs in $RUNLIBS
 # 5. cdd          <-- alias for 'cd $RUNDATA or 'cd $TESTDATA'
 # 6. mvsdatadirs  <-- make about 10 subdirs in $RUNDATA
 # 7. copymvsctls  <-- copy control files & functions for conversion & execution
 #    ===========
 #
 # copy control files
 cp $UV/ctl/cnvcob5.tbl     $RUNLIBS/ctl #search/replace table for COBOL cnvrtr
 cp $UV/ctl/cobdirectives   $RUNLIBS/ctl #COBOL DIRECTIVES for compiler
 cp $UV/ctl/extfh.cfg       $RUNLIBS/ctl #COBOL file handler configuration
 cp $UV/ctl/jclunixop51     $RUNLIBS/ctl #options for JCL to Korn shell converter
 #
 cp $UV/ctl/GDGmkdirs       $RUNDATA/ctl #script make subdirs for new GDG files
 # cp $UV/ctl/gdgctl51_sample $RUNDATA/ctl #sample GDG ctlfile, regen/customize
 #Apr16/09 - GDG control files moved from $RUNLIBS/ctl/ to $RUNDATA/ctl/...
 #           to allow multiple $RUNDATA's to have different control files
 #
 #Feb18/11 - following disabled
 # cp $UV/ctl/jclperlop61   $RUNLIBS/ctl #options for JCL to Perl converter
 # cp $UV/sfun/* sfun    # copy ksh functions, disabled Nov12/2010
 #Nov12/2010 - functions now in $APPSADM/sfun/...
 # ------ function descriptions --------
 # jobset51       - job init for insert at begin JCL/scripts
 # jobend51       - job end copy new GDGs from jobtmp to subdirs
 # jobabend51     - job ABend, ERRmsg & warn new GDGs not updated
 # logcron1       - console msg for scripts run by cron (date/time stamped)
 # logmsg1        - console msg (date/time stamp)
 # logmsg2        - console msg (date/time stamp) reverse video
 # exportfile     - exports Logicalname=Physicalname (non GDG)
 # exportgen0     - exports for GDG file - current generation
 #                  or prior generation, -1, -2, etc
 # exportgen1     - exports for next generation, +2, +3, etc
 # stepctl51      - step ctl function for jcpause
 exit 0

'exportfile' & 'exportgen_' fucntions are vital to JCL conversion. See descriptions & listings starting in 'Part_5'. The JCL converter converts 'DD's to exportfile or exportgen, for example:

     exportfile E212653 $MSTR/e2121653.mtaxe.piscines
     exportgen0 0 E212044 $TAPE/tu.f01.e212-no.auxtxj_

When the JCL/scripts are executed, the export... functions will be called via the Korn shell 'FPATH' variable which is defined in the profile as $APPSADM/sfun.

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

4E1. Converting YOUR MVS JCL to Korn shell scripts

Modifying JCL converter options

Here are the 1st 50 lines from the JCL converter control file listed on '3E1'. You must review & modify these options appropriately for your site.

 jclunixop51:a1b2c0d3e2f3g1i1j0k3l50m4n3o0p0r0s0t1u1v0w0x0y1z0 #<-- options
 #           =================================================
 #  a1                           - append 1 on COBOL reserved word DDNAMES
 #    b1                         - generate blank line between steps
 #    b2                         - insert stepctl51 (mandatory as of Feb08/12)
 #      c1                       - program names UPPER case
 #      c2                       - filenames UPPER case (also uop=l2 jcldata52)
 #      c4                       - control card modulenames UPPER case
 #        d1                     - drop DDNAMES that begin/end with LOAD/LIB
 #        d2                     - drop DSNAMES that begin/end with load/lib
 #          e1                   - echo run command to test script w/o programs
 #          e2                   - option '-v' on cp & mv echo to console log
 #            f1                 - copy FTP commands from lib module to instream
 #            f2                 - use FTP option '-u' to inhibit authorization
 #              g0               - create new GDG's in $RUNDATA/subdir/gdgfile_
 #              g1               - new GDGs $JGDG relative move to subdir/ at EOJ
 #              g2               - new GDGs $JGDG absolute $RUNDATA/jobtmp/...
 #                 i1            - use datactl53I Indexed file for recsz,keys,etc
 #                 i0            - will try to load datactl53I into memory table
 #                   j1          - generate cmd line for JAVA (vs COBOL)
 #                   j2          - include -DDDNAME=$DDNAME for each file in step
 #                   j4          - special convert IKJEFT01, see MVSJCL.doc
 #                     k1        - FTP: insert 'open' prior to 1st line if IP#
 #                     k2        - FTP: insert 'user' prior 1st word if not cmd
 #                       l50     - limit SYSIN/SYSTSIN lines shown in script
 #                          m0   - generate exportfile modules original filename
 #                          m1   - redirect modules to $RUNDATA vs $RUNLIBS dflt
 #                          m2   - redirect SYSIN modules to $RUN____/parms/...
 #                          m4   - redirect ALL modules to $RUN____/parms/...
 #                          m8   - show original filename prior to $RUN____/parms
 #                            n0 - unrecognized JCL passed thru as is
 #                            n1 - unrecognized JCL cmntd out with '#?' cols 1-2
 #                            n2 - if any '=' present, convert any ','s to ';'s
 #                            n3 - if n2 & no '=', cmnt out with '#?' cols 1-2
 #                            n4 - convert unrecognized JCL to instream data
 #                          o1   - remove 1st segment of DDName overrides
 #                        p1     - append parm data on COBOL execution command
 #                      r0       - gen cobrun, executes .int's & allows animation
 #                      r1       - gen runw for .ints NetExpress/Windows
 #                      r2       - assume executable programs either unix/windows
 #                      r4       - assume executables in PATH (progname only)
 #                      r8       - generate 'findexec' Multi-Level program search
 #                      r16      - generate 'unikixvsam $RLX/COBOLX'
 #                      r32      - generate Natural call (natsec batch ...)
 #                    s1         - convert SORT for SYNCSORT (not uvsort)
 #                  t1           - disabled, see TOPNODE table & TOPDIRINSERT
 #                u1             - use uvcp for IEBGENER/IDCAMS REPRO (vs cp)
 #                u2             - use uxcp/uxsort (vs uvcp/uvsort) for IDX3/8
 #              v1               - inhibit DELETE via IDCAMS DELETE
 #              v2               - inhibit DELETE via DISP=(OLD/SHR/MOD,DELETE,
 #            w1                 - generate 'unikixbld -i -d $KIXDATA/filename'
 #            w2                 - insert $RUNDATA on exportfile/gen for unikix
 #          x#                   - make all indexed output files IDXf# (1,3,4,8)
 #        y1                     - generate oprtr prompt to acknowledge Abterms
 #      z1                       - custom for DST, make topnode $SYMBOL no/sep

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

4E2. Converting YOUR MVS JCL to Korn shell scripts

control tables for Top-Nodes

 Here are lines 106-133 extracted from ctl/jclunixop51 (listed on page '3E1').

 :CTLTBL:
 TOPDIRDEFAULT~~~~~~~~~~~~~~~~~$WRK~~~~~~~~~~~~~~~~~~~~~~~~~~
 TOPDIRINSERT~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 # TOPDIRDEFAULT - inserted if only 1 node (no High Level Qualifier) in DSN
 #               - recommend '$WRK' or 'wrk' (1 node files likely temp files)
 # TOPDIRINSERT - if specified, will be inserted above HLQ, retaining all '.'s
 #                (some sites code this as 'mstr')
 # - if NOT specified, the existing top-node is used as a subdir within $RUNDATA
 # - could use TOPNODES to convert any unwanted HLQs as desired
 # - could use FILEREP1 table to convert multiple nodes as desired
 #
 #------------------------ TOPNODES table ------------------------------
 # table of TOPNODES allowed & replacements (optional)
 # 01-30 - topnodes allowed
 # 31-60 - topnode replacements (if col 31 not '~')
 # - if 01-30 of last entry 'ALLOTHER', any others replaced by 31-60
 # - use statmvsjcl1 to create summary table of topnodes used in all JCL
 # - see www.uvsoftware.ca/mvsjcl.htm#6A2
 # - code in lower case since applied at output time(script) vs input(JCL)
 :TOPNODES:
 ar~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 gl~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 py~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 rpts~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 tape~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 ALLOTHERS~~~~~~~~~~~~~~~~~~~~~misc~~~~~~~~~~~~~~~~~~~~~~~~~~
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 #Note1 - you must also code valid top-nodes in $RUNLIBS/ctl/GDGmkdirs
 #      - called by jobset51 to setup subdirs for new generations of GDG files
 #      - see listing at MVSJCL.htm#4E5

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

4E3. Converting YOUR MVS JCL to Korn shell scripts

customizing for YOUR Top-Nodes

Before converting your JCL to Korn shell scripts, you must decide whether to store all your data-files in 1 directory (suggest mstr/...), or to use your top-nodes as subdirs within $RUNDATA.

We will illustrate 'customizing for your topnodes' using the demo files distributed in /home/uvadm/mvstest/testlibs/ctl/... If you performed the demos in Part_1, you would have setup user 'mvstest' & the demo files would now be in /home/mvstest/testlibs/ctl/... ($TESTLIBS/ctl/ & $RUNLIBS/ctl/).

For your own conversion, you would setup a new set of TESTLIBS as illustrated on page '4C3' & populated subdirs cbl0, cpy0, jcl0, proc0, etc with your own COBOL & JCL modules. Page '4C3' shows these subdirs at /p1/apps/testlibs/..., but you can place them wherever desired.

topnode/subdir assignment

Topnode validation & subdir assignment is controlled by the :CTLTBL: & :TOPNODES: tables within the JCL converter control file (ctl/jclunixop51).

The supplied tables reflect the test/demos in Part_1 (using top-node/subdirs ar, gl, py). You should modify the :TOPNODES: table for your valid top-nodes.

You should code your most common top-nodes in the :TOPNODES: (allowed) table & all other (low volume) will be combined into a 'misc' directory.

You must also code your valid topnodes in the '$RUNLIBS/ctl/GDGmkdirs' script, listed on the page '4E5'.

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

4E4. customizing for YOUR Top-Nodes

full-PATH or relative-PATH data filenames

We strongly recommend that all data filenames be coded as relative-PATH, since that allows us to use the same script for TESTing & PRODuction &/or to allow different programmers to use different sets of TEST data.

This flexibility is achieved by defining variables RUNDATA=TESTDATA or PRODDATA and RUNLIBS=TESTLIBS or PRODLIBS in the profiles of programmers & operators, It works because the JCL converter inserts function 'jobset51' or 'jobset52' at the begining of all output scripts. These functions perform 'cd $RUNDATA' so all data filenames can be coded relative to $RUNDATA.

However, some customers may need full-PATH data filenames (probably because they are using unikix software). MVS customers can use option 'w2' in ctl/jclunixop51 to insert '$RUNDATA/' at the begining of all data filenames.

Full-PATH names also requires jobset52 vs jobset51. Both define subdirs for temporary files & new generations of GDG files until successful EOJ.

      export JTMP=jobtmp/$JOBID2              <-- relative-PATH in jobset51
      export JGDG=jobtmp/$JOBID2/GDG

      export JTMP=$RUNDATA/jobtmp/$JOBID2     <-- full-PATH in jobset52
      export JGDG=$RUNDATA/jobtmp/$JOBID2/GDG

options g0,g1,g2

Options g0,g1,g2 (in ctl/jclunix41) are related to the above discussion.

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

4E5. customizing for YOUR Top-Nodes

customizing Top-Nodes - Procedures Required

You can determine the topnodes used by your JCL, using the 'statmvsjcl1' job. See the demo summary table output listed below. Here are the concise operating instructions for your JCL.

This assumes that the JCL has been FTP'd into $TESTLIBS/jcl0/..., that the PROCs have been FTP'd into $TESTLIBS/proc0/..., and that $RUNLIBS & 'cdl' are defined in your profiles for your $TESTLIBS vs demo testlibs used for mvstest in Part_1.

 1. Login --> your home directory
    =====

 2. cdl alias --> your TESTLIBS/RUNLIBS
     ===

 3. jcl2ksh51A all   <-- run partial conversion
    =============     - enough to expand the JCL/PROCs into $TESTLIBS/jcl2/...
                      - see jcl2ksh51A documented on pages '4J1' - 4J3

 3. uvcopy statmvsjcl1,fild1=jcl2
    =============================
    - create summary tables for programs,procs,& topnodes
    - just the 'topnodes' table listed below
      (see programs & procs tables at CNVaids.htm#4B1)

stats/jcl2_topnodes summary table

     statmvsjcl1 2008/08/08_20:03:18 Summary table of DSN Top-Nodes in jcl0
     tbl#003 pg#001     -argument-
     line#  count    %  Top-Node
         1      27  19  &&(ALLTempFiles)
         2      33  23  AR
         3      57  41  GL
         4      10   7  PY
         5       2   1  RPTS
         6       3   2  WRK
         7       1   0  WRK(IKJDEMO1)
               138*100   *TOTAL*

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

4E6. customizing for YOUR Top-Nodes

4. Based on your topnode summary table, decide on any changes & consolidations desired. You might combine low volume topnodes into a 'misc/' subdir. You can also change topnode spellings if desired.
   
   
5. Modify the :TOPNODES: table in the JCL conversion control file. See demo topnodes table listed above on page '4e1' (lines 100-125 excerpted from $TESTLIBS/ctl/jclunixop51). Replace the demo topnodes with your topnodes.
   

 5a. vi ctl/jclunixop51   <-- edit the JCL conversion control field
     ==================     - replace demo topnodes with your topnodes

6. Modify the topnode/subdirs in $TESTLIBS/ctl/GDGmkdirs. 'GDGmkdirs' is a script to create topnode/subdirs in the 'jobtmp' directory, used to store new generations of GDG files until successful EOJ reached, then moved to the intended $RUNDATA/subdirs. The GDGmkdirs script is called by function 'jobset51', which is called on line 10 of all converted JCL/scripts.
   

 6a. vi ctl/GDGmkdirs     <-- edit supplied GDGmkdirs script
     ================       - replace demo topnode/subdirs with yours

See the GDGmkdirs script listed on the next page --->

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

4E7. customizing for YOUR Top-Nodes

ctl/GDGmkdirs - make topnode/subdirs

'GDGmkdirs' is a script to make the topnode/subdirs in the jobtmp/subdirs used to hold new generations of GDG files, until successful EOJ, when they are moved back to the intended $RUNDATA/subdirs. Here is the demo script distributed in $TESTLIBS/ctl/GDGmkdirs.

 # GDGmkdirs - make subdirs for new versions of GDG files
 #             saved in jobtmp/subdirs/... until Normal EOJ
 #           - by Owen Townsend, UV Software, Aug 25/2008
 #
 #Apr16/2009 - this script moved from $RUNLIBS/ctl/ to $RUNDATA/ctl/
 #           - to allow multiple $RUNDATA's to have different GDG controls
 #
 # script in $RUNDATA/ctl/... called by jobset51 (called by all JCL/scripts)
 # exportgen1 creates new GDG files in $RUNDATA/$JGDG/subdirs/...
 # - where: JGDG=$RUNDATA/jobtmp/$JOBID2/GDG/
 # - at normal EOJ, GDG files are moved to intended subdirs (NOT if Abterm)
 #
 # user must code names of his site's data file subdirs here
 # - matching the TOPNODEs table in $RUNLIBS/ctl/jclunixop51
 # - following subdirs are for the demo JCL/scripts
 #   (at www.uvsoftware.ca/mvsjcl.htm#Part_1)
 #
 #Mar14/09 - JCL converter option g1 inserts $JGDG/... on new GDGs exportgen1
 # - new option 'g0' omits $GDG/ so new GDGs in same subdir as old
 # - this GDGmkdirs script must still exist (since called by jobset51)
 #   BUT, subdirs created will not be used, since no files redirected to $JGDG/
 #
 if [[ ! -d $JTMP ]]; then
    echo "JTMP not defined or not in \$RUNDATA"; exit 81; fi
 #
 # make $JGDG/ for gdg subdirs
 # also make $GTMP/ for exportgen0/1 'ls' outputs to determine latest gen#s
 if [[ ! -d $JGDG ]]; then mkdir $JGDG; fi
 if [[ ! -d $GTMP ]]; then mkdir $GTMP; fi
 #
 # You MUST modify following (ar,gl,etc) to the subdirs desired at your site
 #==========================================================================
 if [[ ! -d $JGDG/ar ]]; then mkdir $JGDG/ar; fi
 if [[ ! -d $JGDG/gl ]]; then mkdir $JGDG/gl; fi
 if [[ ! -d $JGDG/py ]]; then mkdir $JGDG/py; fi
 if [[ ! -d $JGDG/mstr ]]; then mkdir $JGDG/mstr; fi
 if [[ ! -d $JGDG/misc ]]; then mkdir $JGDG/misc; fi
 if [[ ! -d $JGDG/tape ]]; then mkdir $JGDG/tape; fi
 exit 0

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

4F1. Converting YOUR MVS JCL to Korn shell scripts

Transferring LIBS & DATA from the mainframe

I assume you will have FTP connections from the mainframe to unix/linux. Please see page '4C4' for the recommended directory design to receive the libraries onto the unix/linux system. By convention the directories receiving the mainframe modules have suffix '0', intermediate conversions have suffix 1,2,3,etc, and fully converted directories have suffix 's'. Only the '0' subdirs are shown here.

If possible create .zip files on the mainframe. You might name them cbl.zip, cpy.zip, jcl.zip, proc.zip, etc. FTP them into the appropriate subdirs. Then change into each subdir, unzip & remove the .zip file.

 /p1/apps
 :-----testlibs        <-- RUNLIBS=$TESTLIBS=/p1/apps/testlibs
 :     :------
 :     :--MF--cbl0     <-- your COBOL programs transferred from mainframe
 :     :------
 :     :--MF--cpy0     <-- for COBOL copybooks
 :     :------
 :     :--MF--jcl0     <-- your JCLs transferred from mainframe
 :     :------
 :     :--MF--proc0    <-- your PROCs transferred from mainframe
 :     :------
       '--MF--'          - 'MF' indicates subdirs receiving from 'MainFrame'

 /p4/apps
 :-----cnvdata           <-- $CNVDATA=/p4/apps/cnvdata
 :     :------
 :     :--MF--cpys       <-- COBOL copybooks
 :     :--MF--ctl        <-- control files (LISTCAT)
 :     :--MF--d0         <-- data files FTP'd from mainframe (variable length)
 :     :------d0ebc        - filenames lower case, '.clus.vseprd' dropped
 :     :------d1ebc        - converted to fixed length for conversion
 :     :------d2asc        - converted to ASCII (packed/binary preserved)
 :     :------maps         - copybooks converted to record layouts
 :     :------pfx1         - uvcopy jobs generated from copybooks
 :     :------.etc.        - see other subdirs on page '4C7'

'd0' will hold the data files to be converted.

If possible, create LISTCAT reports on the mainframe & transfer to ctl/listcat0. We will extract record-sizes, indexed keys, etc to guide us in datafile & JCL conversions. See LISTCAT processing on page '4H1'.

The 'copybooks' are used to generate the 'uvcopy jobs' that perform the datafile conversions. Copybooks might be stored directly into $CNVDATA/cpys (to assist datafile conversion), but better if you 1st convert in $TESTLIBS (as instructed on page '4G1') & then copy from $TESTLIBS/cpys to $CNVDATA/cpys.

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

4G1. Converting YOUR MVS JCL to Korn shell scripts

Converting COBOL copybooks/programs & Compiling

COBOL conversion is covered here in the JCL conversion documentation to make this a complete review of all steps required for the several 'Re-Conversions' that may be performed during the mainframe conversion period.

But for your 1st COBOL conversions, you must follow the procedures documented in MVSCOBOL.htm. Initial conversions & compiles usually encounter many errors that can be resolved by modifying the search/replace tables provided for reserved word differences & customer site coding peculiarities.

Here in MVSJCL.doc we are summarizing the COBOL re-conversions, that might be performed 2 or 3 times during the conversion/test/debug period, to capture updates that have been made on the mainframe.

converting All COPYBOOKs

 cpy0 ---------> cpy1 ---------> cpy2 ----------> cpys
       cleanup         convert         copy(cp)

 #0a. Login as appsadm ---> /home/appsadm

 #0b. cdl  --> $TESTLIBS

 #1. cnvMF51Ac all        <-- convert ALL copybooks from cpy0 to cpy1 & cpy2
     ============

 #2. cp cpy2/* cpys      <-- copy converted copybooks to cpys (used by compiler)
     ==============

 #3. cp cpy2/* $CNVDATA/cpys  <-- also copy to $CNVDATA for datafile conversion
     =======================

converting All PROGRAMs & compiling

 cbl0 -------> cbl1 -------> cbl2 --------> cbl3 ----------> cbls -------> cblx
      cleanup       convert       copy(cp)       sysin cnvt       compile

 #1. cnvMF51A all         <-- convert ALL programs from cbl0 to cbl1 & cbl2
     ===========

 #2. cp cbl3/* cbls      <-- copy converted programs to cbls (used by compiler)
     ==============

 #4. mfcblA all          <-- recompile all cobol programs, cbls --> cblx
     ==========

 #5. uvlpd1p cblx .err   <-- print 1st page of all .err reports
     =================     - to guide programmers making corrections
                           - should be very few on these re-conversions

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

4G2. Converting YOUR MVS JCL to Korn shell scripts

Converting 1 COBOL copybook/program & Re-compiling

Here are some handy scripts you can use to re-convert & re-compile 1 copybook or 1 COBOL program at a time (vs prior page ALL copybooks & ALL programs). The scripts are supplied in /home/uvadm/sf/IBM/... & are listed in MVSCOBOL.htm#5C1.

converting 1 COPYBOOK at a time

 cpy0 ---------> cpy1 ---------> cpy2 ----------> cpys
       cleanup         convert         copy(cp)

 #0a. Login as appsadm or yourself

 #0b. cdl  --> $TESTLIBS

 #1. cnvMF51c cpy0/copybknm.cpy  - convert 1 copybook cpy0->cpy1->cpy2
     ============================

 #2. cp cpy2/copybknm.cpy cpys   - copy converted copybook to cpys
     =========================   - above script prompts for this

 #3. cp cpy2/copybknm.cpy $CNVDATA/cpys  - also copy to $CNVDATA
     ==================================  - for datafile conversion

converting 1 PROGRAM & Re-Compiling

 cbl0 -------> cbl1 -------> cbl2 ------> cbl3 ------> cbls ------> cblx
      cleanup       convert      acpt cnv --- prompt for copy & compile ---
                                             copy(cp)       compile

 #1. cnvMF51 cbl0/progname.cbl  - convert 1 program cbl0->cbl1->cbl2->cbl3
     =========================    (prompts to copy cbl3->cbls)

 #2. cp cbl3/progname.cbl cbls  - copy cnvrtd program to cbls
     =========================    (if you replied`'n' above)

 #3. mfcbl1 progname.cbl        - recompile 1 cobol program cbls-->cblx
     ===================

only if compile fails

 #4. uvlp12 cblx/progname.err e1  - print 1st page of .err reports
     ===========================  - to guide correction & recompile

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

4H1. Converting YOUR MVS JCL to Korn shell scripts

create Data conversion control file from LISTCAT

We assume the LISTCAT report has been transferred from the mainframe & stored at $CNVDATA/ctl/listcat0. 'catdata51' will extract filenames, avg-recsize, max-recsize, indexed key start(lth) onto 1 line per file.

Initial data conversions must be performed as instructed in MVSDATA.htm. Here in MVSJCL.doc, we are covering 'Re-Conversion', because you might reconvert all JCL,COBOL,DATA 2 or 3 times during conversion period

You will not recreate the DATA conversion control file ($CNVDATA/ctl/datacnv54), because it required manual editing to add copybook names.

But you might want to recreate the 'JCL conversion control file' ($TESTLIBS/ctl/datactl53I), because a newer LISTCAT from the mainframe might provide more accurate information on the datafiles for the JCL converter.

 #1a. Login as appsadm ---> /home/appsadm

 #1b. cdc  --> $CNVDATA

 #2. uvcopy catdata51,fili1=ctl/listcat0,filo1=ctl/datacat51
     =======================================================
     - extract data conversion info from mainframe LISTCAT report

 #3. sort -o ctl/datacat52 ctl/datacat51
     ===================================
     - sort by data file name, see sample listing on page '3F2'
     - see full listing at MVSDATA.htm#8B1.

 #4. uvlp12 ctl/datacat52     <-- list the output file
     ====================

 #5. vi ctl/datacat52         <-- edit the datacat52 extract
     ================
     - drop unwanted files (not required for conversion)
     - add any missing files (not on disc when LISTCAT run)

 #6. uvlp12 ctl/datacat52     <-- re-list the datacat52 extract report
     ====================
     - store in 3 ring binder for frequent reference during conversion

 #7. cp ctl/datacat52 $TESTLIBS/ctl
     ==============================
     - copy datacat52 from $CNVDATA to $TESTLIBS for later use in JCL conversion
     - see page '4K1' to create JCL conversion control file ctl/datactl53I
       from up to 6 sources (JCL itself, LISTCAT, spreadsheets, edited info)

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

4I1. Converting YOUR MVS JCL to Korn shell scripts

Converting Your DATA files

DATA conversion is covered here in the JCL conversion documentation to make this a complete review of all steps required for the several 'Re-Conversions' that may be performed during the mainframe conversion period.

The mainframe data files might be re-transferred & reconverted 2 or 3 times during the test/debug period, & of course 1 final time on the 'go live' weekend.

For your 1st DATA file conversions, you must follow the procedures documented in MVSDATA.htm. MVSDATA.doc shows you how to generate the data conversion 'uvcopy jobs' from the COBOL copybooks. This can be completely automatic, unless you have files with multiple record types, in which case some manual coding is required.

For subsequent DATA file conversions, you can use the data conversion uvcopy jobs that were generated (& modified) during the initial conversion. You may need changes to some jobs if the mainframe copybooks change during the conversion period.

Here in MVSJCL.doc, we will briefly review how to re-convert datafiles, assuming the data conversion jobs have already been generated as documented in MVSDATA.htm#Part_4. You can use the data re-convert instructions when you re-transfer data files from the mainframe, which you might do several times during the testing period.

BUT, if you change any copybooks (from which data conversion jobs are generated) or the control file ctl/datacnv54I (which relates copybooks to datafilenames & provides file types & keys), then you must refer to MVSDATA.htm#PART_4 to re-generate the data conversion 'uvcopy jobs' in $CNVDATA/pfx3.

Important Notes

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

4I2. Converting YOUR MVS JCL to Korn shell scripts

GENERATING data conversion jobs

• 'GENERATING' the conversion jobs is covered very briefly here in MVSJCL.doc
• Only to give you some understanding of the procedures involved
• you MUST follow procedures in MVSDATA.htm#Part_4 to perform the generations

'EXECUTE' data conversions here in MVSJCL

• IF you have already GENERATED the uvcopy jobs in MVSDATA.htm#PART_4
• IF you have not changed any copybooks describing the datafiles to be converted
• IF no file types, rec-sizes, keys, etc need to be changed in the control file
• IE, you are RE-CONVERTING only because you RE-TRANSFERRED data from mainframe

subdirs to GENERATE 'data conversion uvcopy jobs'

 /p4/apps/cnvdata/  <-- Data conversion superdir ($CNVDATA)
 :-----cpys      - COBOL copybooks
 :-----ctl       - conversion control files
 :-----maps      - 'cobmaps' record layouts generated from copybooks
 :-----pfx1      - conversion jobs generated from COBOL copybooks by 'uvdata51'
 :-----pfx2      - conversion jobs with actual datafile names & indexed keys
 :               - coded by utility 'uvdata52' using control file ctl/datacnv54I
 :-----pfx3      - uvcopy jobs copied from pfx2 & modified for various reasons
 :               - for Multi Record Type files (insert code to test types)
 :               - will execute the jobs from pfx3

generating data conversion jobs

 cpys ---------> maps ---------> pfx1 ---------> pfx2 ----------> pfx3/...
       cobmap1          uvdata51       uvdata52         cp & vi  (data cnvt jobs)
                                   (ctl file req'd)

The data conversion jobs are generated from the COBOL copybooks, but we also need a control file to relate the copybooks to the datafilenames, and also to supply file types, indexed keys, etc.

creating the data conversion control file

The mainframe 'LISTCAT' report is the best place to get this information. We can transfer the mainframe file & extract the information into a control file used in the conversion job generations. See procedures at MVSDATA.htm#4E1 thru page 4F6.

 mainframe         unix/linux
 LISTCAT -----> ctl/listcat0 ---------> ctl/datacat51 ----------> ctl/datacnv54I
          FTP                catdata51            (many steps omitted)

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

4I3. Converting YOUR MVS JCL to Korn shell scripts

subdirs to GENERATE 'data conversion uvcopy jobs'

 /p4/apps/cnvdata/  <-- Data conversion superdir ($CNVDATA)

 :-----cpys      - COBOL copybooks
 :-----ctl       - conversion control files
 :-----maps      - 'cobmaps' record layouts generated from copybooks
 :-----pfx1      - conversion jobs generated from COBOL copybooks by 'uvdata51'
 :-----pfx2      - conversion jobs with actual datafile names & indexed keys
 :-----pfx3      - uvcopy jobs copied from pfx2 & modified for multi R/T files
 :               - will execute the uvcopy jobs from pfx3

subdirs for DATA files to be converted

                         (in same superdir as above)

 :-----d0ebc                    <-- EBCDIC data files FTP'd from mainframe
 :     :---AR.DATA.FILE1          - filenames UPPER case
 :     :---GL.DATA.FILE1(0)       - GDG file suffixes (0), G1234V00, etc
 :     :---GL.DATA.FILE2.G1234V00 - GDG file suffixes (0), G1234V00, etc
 :     :---...etc...
 :-----d1ebc                    <-- EBCDIC data filenames changed to unix stds
 :     :---ar.data.file1          - filenames lower case
 :     :---gl.data.file1_000001   - GDG file suffixes changed to VU conventions
 :     :---gl.data.file2_000001   - GDG file suffixes changed to VU conventions
 :     :---...etc...
 :-----d2asc                    <-- to receive ASCII conversions
 :     :---ar.data.file1          - ASCII data files from most recent conversion
 :     :---gl.data.file1_000001   - copy from here to refresh testdata subdirs
 :     :---gl.data.file2_000001   - copy from here to refresh testdata subdirs
 :     :---...etc...

subdirs for $TESTDATA

 p1/testdata/                   <-- $TESTDATA ($RUNDATA) for testing
 :-----ar                          - topnodes/subdirs (ar,gl for illustrations)
 :     :---data.file1              - subdirs/datafiles copied here for testing
 :     :---...etc...               - refreshed whenever required from cnvdata
 :-----gl
 :     :---data.file1_000001
 :     :---data.file2_000001
 :     :---...etc...
 :     :

Then script 'copy2nodes' copies all files from $CNVDATA/d2asc to the subdirs in $TESTDATA/... making subdirs as required from the topnode of the filenames.

Note that the datafiles in $CNVDATA/d2asc topnodes 'ar' & 'gl' are converted to subdirs when copied to $TESTDATA/...

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

4I4. Converting YOUR MVS JCL to Korn shell scripts

Re-Transfer/Re-Convert DATA files

            FTP         rename        convert     copy to TopNode subdirs
 mainframe -----> d0ebc-------->d1ebc-------->d2asc------->$TESTDATA/TNsub/...
            FTP      cpd0d1rename    pfx3/jobs     copy2nodes

You might need to re-transfer/re-convert data files several times during the testing period. You can use the following 'Execution' Instructions for this, provided you have not changed any copybooks or the control file that relates copybooks to datafilenames & file types, keys,etc.

If you have changed any copybooks or the control file, then you MUST follow the data conversion job 'Generation' Instructions detailed in MVSDATA.htm#Part_4

The following Execution Instructions originate from MVSDATA.htm#4G2.

 #00. Transfer (FTP) mainframe DATA files ---> $CNVDATA/d0ebc

 #01. cdc ---> alias 'cd $CNVDATA' ---> /home/mvstest/cnvdata for example
      ============================

 #02. ls d0ebc >tmp/ls_d0ebc
      ======================
      - create mainframe filenames to be converted to unix/linux conventions

 #03. uvcopy mksfd0d1,fili1=tmp/ls_d0ebc,filo1=sf/cpd0d1rename
      ========================================================
      - make script to copy d0ebc to d1ebc, changing filenames
        from mainframe conventions to unix/linux VU standards
        GDG filename(0) --> filename_000001, etc

 #04. sf/cpd0d1rename   <-- execute script to copy/rename
      ===============

 #__. ................  <-- many steps omitted (see MVSDATA.htm#4G2)
      ================

 #23. uvcopyxx 'pfx3/*'
      =================
      - execute all jobs to convert all files from d1ebc to d2asc

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

4I5. Converting YOUR MVS JCL to Korn shell scripts

copying converted data files to $TESTDATA

Most mainframe conversion sites choose to use the topnode as a sub-directory on the unix/linux target systems. UV software provides the 'copy2nodes' script to facilitate this.

 #24. rm -rf $TESTDATA/*   <-- remove all subdirs from testdata dir
      ==================

 #25. mvsdatadirs    <-- recreate the basic subdirs required in testdata
      ===========      - jobtmp, joblog, rpts, sysout, tmp, wrk

 #26. copy2nodes d2asc $TESTDATA
      ==========================
      - copy all converted datafiles, creating subdirs from topnodes
        (subdir created when new topnode 1st encountered)

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

4I6. Converting YOUR MVS JCL to Korn shell scripts

Re-transfer/Re-convert 1 datafile (vs all)

The following Execution Instructions originate from MVSDATA.htm#4G2.

 #00. Transfer (FTP) mainframe DATA files ---> $CNVDATA/d0ebc

 #01. Login as appsadm or yourself

 #02. cdc --> alias 'cd $CNVDATA' --> /app/risk/cnvdata for example
      ===========================

 #03. cp d0ebc/DBDPDW.PDW200.$ADDR.DLY(0) d1ebc/dbdpdw.pdw200._addr.dly_000001
      ========================================================================

 #10. uvcopy pfx3/dbdpdw.pdw200._addr.dly_000001
      ==========================================
      - execute 1 job to convert 1 file from d1ebc to d2asc

copying converted data file to $TESTDATA

Most mainframe conversion sites choose to use the topnode as a sub-directory on the unix/linux system.

 #11. cp  d2asc/dbdpdw.pdw200._addr.dly_000001
      ========================================
          $TESTDATA/dbdpdw/pdw200._addr.dly_000001
          ========================================
      - copy 1 converted datafile to $TESTDATA topnode subdir

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

4J1. Converting YOUR MVS JCL to Korn shell scripts

Initial conversion of All JCL

You should perform the initial conversion of All Your JCL, using the step by step method documented in this section. Then you should test/debug 1 or 2 JCL/scripts to verify the conversions.

From the testing & debugging 1 or 2 JCL/scripts you may find improvements that can be made to the JCL converter options file (ctl/jclunixop51) & to the data information file (ctl/datactl53I). After modifying these control files you can reconvert the 1 or 2 JCLs using the 'jcl2ksh51' script (page '4N1')

After you are satisfied with the conversion & testing of 1 or 2 JCL/scripts, you can the use the 'jcl2ksh51A' script to reconvert all JCL/scripts, to realize the improvements in all JCL/scripts.

This works well because automatic conversions stop at jcl3, & we copy JCL/scripts from jcl3 to jcls, only when we are ready to test/debug each JCL/script.

directories involved in JCL conversion

 /p1/apps
 :-----testlibs        <-- RUNLIBS=$TESTLIBS=/p1/apps/testlibs
 :     :------
 :     :--MF--ctl      <-- control files
 :     :------           - jclunixop51 specifies options for JCL conversion
 :     :------           - datactl53I supplies file types,recsizes,indexed keys
 :     :------           - datajcl51 (filenames) extracted from all JCL
 :     :------             supplies file info for files missing from datactl53I
 :     :------             (work files scratched, not present for LISTCAT)
 :     :------           - you can edit dataedt52 to override datajcl51 entries
 :     :------
 :     :--MF--jcl0     <-- your JCLs transferred from mainframe
 :     :------jcl1       - intermediate conversion 73-80 cleared
 :     :------jcl2       - PROCs expanded from procs
 :     :------jcl3       - JCLs converted to Korn shell scripts
 :     :------jcls       - copy here manually 1 by 1 during test/debug
 :     :------
 :     :--MF--proc0    <-- your PROCs transferred from mainframe
 :     :------
 :     :--MF--slis     <-- SLI library may be included in JCLs
 :     :------

JCL conversion steps

 jcl0 -------> jcl1 --------------> jcl2 -------------> jcl3 ------------> jcls
      cleanup       PROC/SLI expand      convert to ksh      manual copy
                                                             1 at a time

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

4J2. Converting YOUR MVS JCL to Korn shell scripts

preparation for JCL conversion

The first part of Part_4 documented several preparations required before attempting to convert your JCL. These are listed below with references back to the original documentation.

1. You have installed the Vancouver Utilities as per '4B2' (briefly) and in complete detail in install.htm.
   
   
2. You have setup user profiles as per '4B3' (briefly) and in complete detail at ADMjobs.htm#Part_1.
   
   
3. I recommend you setup user 'appsadm' for initial conversions by the team leader. After initial mass conversions, the various team members will use their own logins for individual program compiling & JCL/script testing. See 'appsadm' setup at ADMjobs.htm#1D1 thru 1D7.
   
   
4. Setup the conversion 'super-directory' as per pages '4C1' & '4C2'. The conversion superdir is defined as 'RUNLIBS' in the stub_profile. In our example it is:
   

 export RUNLIBS=/p1/apps/testlibs
 ================================

5. Setup the JCL & COBOL conversion subdirs. You can use the 'mvslibsdirs' script to setup the 30 subdirs listed on page '4C3'.
   

 #5a. login appsadm --> /home/appsadm

 #5b. cd $RUNLIBS  <-- change to the conversion superdir '/p1/apps/testlibs'

 #5b. cdl          <-- same as above but easier
      ===              alias cdl='cd $RUNLIBS' is defined in the profile

 #5c. mvslibsdirs  <-- setup 30 subdirs for JCL & COBOL conversions
      ===========

6. Copy conversion 'control files' to subdir ctl/... as per page '4D2'.
   

 #6a. copymvsctls  <-- script to copy control files from /home/uvadm/ctl
      ===========      to $RUNLIBS/ctl/...

7. Modify JCL converter options 'ctl/jclunixop51' listed on page '4E1' and discussed thru page 4E4.
   

 #7a. vi ctl/jclunixop51  <-- modify JCL converter options
      ==================

8. Transfer your mainframe JCLs, PROCs,& SYSIN/parms into the appropriate subdirs (jcl0, proc0, parm0) as discussed on page '4F1'.
   

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

4J3. Converting YOUR MVS JCL to Korn shell scripts

convert All JCL - 'script' method

For your initial conversion we recommend you use the 'step by step' method (starting on page '4K1'), because you can more easily notice any errors.

If you do try the 'do everything' script (jcl2ksh51A), be prepared to revert to the step by step method if you have problems. Or you could activate 'console logging' to capture all screen messages, or you could login from a 'putty' terminal with a large windows history.

 #1. Login as appsadm ---> /home/appsadm

 #2a. cd $TESTIBS  <-- change to the conversion superdir '/p1/apps/testlibs'
      ===========

 #2b. cdl          <-- same as above but easier
      ===              alias cdl='cd $RUNLIBS' is defined in the profile

 #2c. cd $TESTIBS  <-- also same as above, since RUNLIBS=TESTLIBS at this point
      ===========

 #3. jcl2ksh51A all    <-- convert JCL thru all steps, as illustrated below
     =============      - reply null (take default) at all prompts
                        - or reply 'y' for prompts that demand a y/n response

 jcl0 -------> jcl1 --------------> jcl2 -------------> jcl3 ------------> jcls
      cleanup       PROC/SLI expand      convert to ksh     copy 1 at a time
                                                          (before test/debug)

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

4K1. Converting YOUR MVS JCL to Korn shell scripts

convert All JCL - 'step by step' method

1. cleanup mainframe JCL, PROCs, SLIs,& PARMs (strip CR's, clear cols 73-80, & shorten to last nonblank).
   

 #1a. uvcopyx cleanup jcl0 jcl1 uop=q0i7g8n1,arg1=.jcl     #<-- cleanup JCL
      ================================================
 #1b. uvcopyx cleanup proc0 procs uop=q0i7g8n1,arg1=.proc  #<-- cleanup PROCs
      ===================================================
 #1c. uvcopyx cleanup sli0 slis uop=q0i7g8n1,arg1=.sli     #<-- cleanup SLIs
      ================================================
 #1d. uvcopyx cleanup parm0 parms uop=q0i7g8n1             #<-- cleanup parms
      ========================================

 #2. jclpx51 jcl1 jcl2 procs slis
     ===========================
     - expand procs as we copy JCL from subdir jcl1 to subdir jcl2

JCL conversion subdirs

 jcl0 -------> jcl1 --------------> jcl2 -------------> jcl3 ------------> jcls
      cleanup       PROC/SLI expand      convert to ksh     copy 1 at a time
                                                          (before test/debug)

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

4K2. Converting YOUR MVS JCL to Korn shell scripts

creating JCL converter DATA-INFO control file

The JCL converter needs an Indexed file 'ctl/datactl53I' to get information about the data-files (record-size, file-type, key-location/length, GDG or not). This info is required for SORTs, IDCAMS, IEBGENER, etc that are converted to uvsort & uvcp.

The mainframe JCL did not necessarily specify record-size etc, since this info could be obtained from the mainframe VTOC or LISTCAT. But there is no VTOC or LISTCAT on unix/linux, so we will supply that info to the JCL converter via an Indexed file (ctl/datactl53I). We can collect datafile info from up to 'six' sources. See detailed descriptions in Part_6 begining on page '6C1'.

The only mandatory source is the JCL itself. Utility job 'jcldata51' will extract all DSN's from all JCL. These are sorted & duplicates dropped resulting in 1 line per unique datafilename found in all JCL.

 #3. uvcopy jcldata51,fild1=jcl2,filo2=ctl/datajcl51
     ===============================================
     - generate data info control file for JCL converter
     - extract DSNs from all JCL, sort, drop dups

 #3a. uvcopy jcldata51   <-- same as above (files default as shown)
      ================

 #4. uvcopy jcldata52,fili1=ctl/datajcl51,filo2=ctl/datajcl52
     ========================================================
     - convert mainframe filenames to conventions used in Korn shell scripts
     - translate UPPER case to lower case
     - convert any embedded '$' '#' to '_'s
     - convert any filename(module) to filename@module
     - modify GDG (0), (+1), G0587V00, etc to '_000001'

 #4a. uvcopy jcldata52   <-- same as above (files default as shown)
      ================

Please see sample outputs listed on the next page --->

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

4K3. Converting YOUR MVS JCL to Korn shell scripts

sample ctl/datajcl51

 DB2.PROD.DWPARM(QUDW33)                cntf=0002 rca=00000 rcm=00000 typ=RSF src=J___________ job=pdwkscix prg=DSNUTILB
 DBDPCSM.CSM781.$CHP14.EFDS.MERGE(+1)   cntf=0001 rca=00000 rcm=00000 typ=RSF src=J___________ job=csm781m prg=CSM78100
 DBDPCSM.CSMUNLK3.$MDBCID.IN.PDW.%%MDY  cntf=0005 rca=00147 rcm=00147 typ=RSF src=Jr__________ job=csmunlk3 prg=SORT
 DBDPDW.DBDFTP.$ABA.MONTHLY(0)          cntf=0001 rca=00000 rcm=00000 typ=RSF src=J___________ job=pdw202p1 prg=PDW20200
 DBDPCSM.CSMSRT.$WELLS.G0587V00         cntf=0001 rca=00753 rcm=00753 typ=RSF src=Jr__________ job=csmwel_1 prg=SYNCSORT
 DBDPDW.PDW202.$ADDR.USG.WKY(+1)        cntf=0001 rca=00039 rcm=00039 typ=RSF src=Jr__________ job=pdw202p1 prg=PDW20200

sample ctl/datajcl52

 db2.prod.dwparm@qudw33       rca=00000 rcm=00000 typ=RSF src=J___________ job=pdwkscix prg=DSNUTILB
 dbdpcsm.csm781._chp14.efds.merge_     rca=00000 rcm=00000 typ=RSF src=J___________ job=csm781m prg=CSM78100
 dbdpcsm.csmunlk3._mdbcid.in.pdw.%%MDY rca=00147 rcm=00147 typ=RSF src=Jr__________ job=csmunlk3 prg=SORT
 dbdpdw.dbdftp._aba.monthly_  rca=00000 rcm=00000 typ=RSF src=J___________ job=pdw202p1 prg=PDW20200
 dbdpdw.dbdftp._aba.monthly_  rca=00000 rcm=00000 typ=RSF src=J___________ job=pdw202p1 prg=PDW20200
 dbdpdw.pdw202._addr.usg.wky_ rca=00039 rcm=00039 typ=RSF src=Jr__________ job=pdw202p1 prg=PDW20200

• ctl/datajcl52 is combined with up to 5 additional component files
  to create 'ctl/datactl53I' used by the JCL converter

• see Part 6 pages '6C1' thru 6C5 for descriptions of the 5 optional files

• if at all possible you should get the mainframe LISTCAT report to
  create ctl/datacat52 (component #2 of 6 optional files).

final result - ctl/datactl53

 db2.prod.dwparm@qudw33                   cpy=____________ rca=_____ rcm=_____ typ=RSF src=J_____Yi__D_ job=pdwkscix prg=DSNUTIL
 dbdpcsm.csm781._chp14.efds.merge_        cpy=nasc354.cpy  rca=_____ rcm=_____ typ=RSF src=J_____Yi__D_ job=pdw100pe prg=PDW2100
 dbdpcsm.csmunlk3._mdbcid.in.pdw.%%MDY    cpy=____________ rca=00147 rcm=00147 typ=RSF src=J___XrYi__D_ job=pdm825mp prg=SORT
 dbdpdw.dbdftp._aba.monthly_              cpy=____________ rca=_____ rcm=_____ typ=RSF src=J_________D_ job=pdw202p1 prg=PDW2020
 dbdpdw.dbdftp._aba.monthly_              cpy=____________ rca=_____ rcm=_____ typ=RSF src=J_________D_ job=pdw202p1 prg=PDW2020
 dbdpdw.pdw202._addr.usg.wky_             cpy=____________ rca=00039 rcm=00039 typ=RSF src=Jr____Yi__Dp job=pdw301p1 prg=PDW2020

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

4K4. Converting YOUR MVS JCL to Korn shell scripts

script to create JCL DATA-INFO file ctl/datactl53I

The easy way to create the JCL converter DATA-INFO control file is to use script 'jcldata5A'.

'jcldata5A' creates ctl/datajcl51 & ctl/datajcl52 (shown above) & merges ctl/datajcl52 with 5 other optional sources to create the final result (ctl/datactl53I used by the JCL converter).

The 5 optional information files must have been created before you run script 'jcldata5A' (or 'jcl2ksh51A' which calls jcldata5A & performs all conversions). See Part 6 pages '6C1' thru 6C5 for descriptions of the 5 optional files. You should get the mainframe LISTCAT & create ctl/datacat52 if at all possible.

You can make null files for any of the 5 optional information sources that you do not have. If you had none of the 5 optional files you could create null files as follows. We sequence from #5b to #5f to indicate that the 1st file #5a (ctl/datajcl52) has already been created above.

 #5b. >ctl/datacat52
 #5c. >ctl/dataxl152
 #5d. >ctl/dataxl252
 #5e. >ctl/datacnv52
 #5f. >ctl/dataedt52

 #6. jcldata5A  <-- create datajcl51 & datajcl52 & sort 6 files together:
     =========      (datajcl52+datacat52+dataxl152+dataxl252+dataedt52+datacnv52)
                  - to create datactl53 & load Indexed file datactl53I

modifying JCL conversion control files

After your 1st conversion, you might notice that some files do not have record sizes (in converted SORTs etc), & you might want to add the record sizes into the control file & reconvert all JCL.

You should not modify ctl/datajcl52 or ctl/datacat52 since any rerun of jcldata5A or LISTCAT reconvert would overwrite your manual changes.

'ctl/dataedt52' is provided for you to code any missing record sizes, file types, etc.

 #5f. vi ctl/dataedt52  <-- create ctl/dataedt52 to override file info
      ================      on matching filenames in ctl/datajcl51

 #6. jcldata5A    <-- rerun to sort 6 files together & create ctl/datactl53I
     =========

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

4K5. Converting YOUR MVS JCL to Korn shell scripts

JCL to Korn shell script conversion

 #6. jclxx51 jcl2 jcl3     <-- convert expanded JCL to Korn shell scripts
     =================
     - JCL converter called for each JCL found in jcl2 & ksh written to jcl3
     - uses ctl/datactl53 to get file characteristics (record-sizes,etc)

Alternative 'script' method to convert All JCL

Here is the alternative to the above 'step by step' conversion documented on the previous 4 pages. You were advised to use the 'step by step' method for your 1st conversion to better understand & detect errors sooner.

But, do use the 'jcl2ksh51A' script for your subsequent re-conversions after you have proven the conversions work OK at your site.

 #1. jcl2ksh51A all    <-- convert JCL thru all steps, as illustrated above
     =============      - reply null (take default) at all prompts
                        - or reply 'y' for prompts that demand a y/n response

 jcl0 -------> jcl1 --------------> jcl2 -------------> jcl3 ------------> jcls
      cleanup       PROC/SLI expand      convert to ksh      manual copy

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

4L1. Optional Preparations depending on site preferences

Preparations Required before test/debug can begin

Depending on your site, you may have some initial preparations that must be performed before you can begin testing & debugging your JCL/scripts.

creating the gdgctl file

Before you can execute any JCL/scripts, you must create the GDG control file. 'ctl/gdgctl51I' is an Indexed file that is accessed by GDG functions (exportgen0, exportgen1,& gdgupab1) to supply the number of generations for each datafile & also to record a history of the last 14 accesses or errors).

Please study 'Part_5' for complete details, but if you are anxious to run some jobs (that do not contain GDG files), here is the minimum instructions with few explanations.

Utility job 'jcldata56' will read all JCL, extract all DSN's,& sort with data reduction to 1 line per unique filename. The output file is then reformatted into the gdgctl layout & loaded into the Indexed file by 'gdgload1'.

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

4L2. Optional Preparations before testing begins

Op. Instrns. to create gdgctl file

 #1a. login mvstest,appsadm,or yourself --> /home/mvstest,appsadm,homedir

 #1b. cdl --> $TESTLIBS (/home/mvstest/testlibs, /p1/apps/testlibs, ???)
           - see directories,profiles,$RUNLIBS,etc discussed page '1A1' +

 #2. [ jcl2ksh51A all ]      <-- we assume JCL conversion already completed
     =================        - left all converted scripts in jcl3/...

 #3. uvcopy jcldata56,fild1=jcl3,filo2=ctl/datafiles56
     =================================================

 #3a. uvcopy jcldata56     <-- same as above (files default as shown above)
      ================       - sample output shown below

     gl/account.master_                       gdg=31
     gl/account.trans_                        gdg=31 opt=c

These samples are based on the test/demo JCLs shown in Part_1 (but most lines removed for this illustration).

 #4. cp ctl/datafiles56 $RUNDATA/ctl/gdgctl51
     ========================================
     - copy/rename for GDG control file

 #5. cdd  (alias cdd='cd $RUNDATA') --> /home/mvstest/testdata
     ===

 #6. vi ctl/gdgctl51    <-- edit to modify no of generations as desired
     ===============      - replace any $SYMBOLS with values
                            (see '5F1', could ignore for early testing)

 #7. uvcopy gdgload1,fili1=ctl/gdgctl51,filo1=ctl/gdgctl51I
     ======================================================
     - load Indexed file to supply file info to JCL converter

 #7a. uvcopy gdgload1   <-- same but easier (files default as shown above)
      ===============

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

4L3. Optional Preparations before testing begins

Cross References for COBOL & JCL/scripts

These cross-reference reports will be invaluable during testing & debugging.

Please see complete instructions & illustrated reports at XREFjobs.htm, but here are the reports & concise instructions to create them in subdir 'xref'.

Cross-Ref Reports Available

Operating Instructions for Cross-Refs reports

 #1. xrefall cbls jcl3 ksh   <-- crossref COBOL & ksh scripts
     =====================

 #2.  uvlpd12D xref   <-- print all files in the directory (Duplex)
      =============

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

4L4. Optional Preparations before testing begins

Job-Flow reports

The 'JobFlow' reports are your guide to testing & debugging. They show you the programs & datafiles used in each step of each JCL/script.

I recommend you print these out before you start your testing & debugging. They serve as your guide & checklist to monitor your progress & make notes about any problems.

The JObFlow reports extract the essential info about each datafile in each step. The file info from the COBOL program is inserted onto the matching info from the JCL. The following items are shown for each file in each step:

• job-step#, COBOL program, Org, Access, Open mode, Recsize, Copybook, filename

See complete instructions & sample reports at XREFjobs.htm#Part_2.

You could run jobflow reports for all jobs but the report would be huge so we will give you the instructions to run the jobflow report for any 1 job.

You must have run 'cobfiles5A' to load an Indexed file for lookup by jobflow51 to include COBOL file information on the jobflow report.

You may regenerate the Job-Flow reports any time you make significant changes to the JCL/scripts during testing & debugging.

 #1. jobflow51 jcls/jar200.ksh   <-- generate JobFlow report for 1 job only
     =========================

 #2. uvlp12L tmp3/jar200.ksh     <-- print jobflow report for 1 JCL only
     =======================

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

4L5. Optional Preparations depending on site preferences

Extract control cards from JCL to separate files

The VSE JCL converter has an option to #comment out all embedded control cards (for dates, rates, etc) & to create filename references to those records in subdir $RUNDATA/jobparms1 & $RUNDATA/jobparms2.

Utility job 'jobparmx1' is provided to extract the embedded control cards from i JCL/scripts into separate files that can be updated before JCL/scripts are executed.

Control files will have a date-stamp appended (current date at generation time). Run control administrators may duplicate the files & append future dates which will be selected when the current data reaches or passes file dates.

Also see 'jobparms1' which will be run at 6PM (before batch shift) to copy $RUNLIBS/jobparmx1/* to $RUNDATA/jobparms1, selecting the appropriate control card from any multiple dates for any 1 jobname_step_program

See more details in Part_6 (optional procedures) begining on page '6D1'.

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

4M1. Converting YOUR MVS JCL to Korn shell scripts

Test/Debug 1 JCL/script to fine tune conversion

The previous section '4J1' - 4K4 documented the initial conversion of All JCL. Now you should test/debug 1 or 2 JCL/scripts to verify the conversions.

From the testing & debugging 1 or 2 JCL/scripts you may find improvements that can be made to the JCL converter options file (ctl/jclunixop51) & to the data information file (ctl/datactl53I). After modifying these control files you can reconvert the 1 or 2 JCLs using the 'jcl2ksh51' script (page '4N1')

After you are satisfied with the conversion & testing of 1 or 2 JCL/scripts, you can the use the 'jcl2ksh51A' script to reconvert all JCL/scripts, to realize the improvements in all JCL/scripts.

This works well because automatic conversions stop at jcl3, & we copy JCL/scripts from jcl3 to jcls, only when we are ready to test/debug each JCL/script.

 jcl0 -------> jcl1 --------------> jcl2 -------------> jcl3 ------------> jcls
      cleanup       PROC/SLI expand      convert to ksh      prompt & copy

We will present the operating instructions for jcl2ksh51 & jcl2ksh51A on page '4N1' & '4N2', but 1st we will remind you of a few aids to assist you in testing & debugging. These & many more aids were 1st presented in 'Part_2'.

1. testdatainit - clear output subdirs before test runs
   
   
2. joblog - capture logs in joblog subdir of current directory
   

 2a. joblogA    - capture logs And turn on COBOL Animation
                - saves having to 'export ANIM=+A' to animate

3. llr - script to list all files & subdirs within a subdir (Recursive)
   

We will illustrate using these aids as we test/debug JCL/script 28401d23.ksh

 28401d23.ksh          <-- execute JCL/script to demo debug aids
 ============

 joblog 28401d23.ksh  <-- execute & capture log in $TESTLIBS/joblog/28401d23.log
 ====================

 joblogA 28401d23.ksh <-- execute & capture log in $TESTDATA/joblog/28401d23.log
 ====================   - the 'A' version also turns on COBOL Animation
                        - saves having to 'export ANIM=+A' to animate

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

4M2. Testing & Debugging Aids

testdatainit - clear output subdirs before testing

You can use the 'testdatainit' script before running your JCL/script tests, to clear out any old outputs & enable you to more easily examine the outputs of your current test runs.

You can run testdatainit anytime, if you have changed your profile (as shown above) to redefine TESTDATA as a subdir in your homedir, or if you know that no other programmers are currently testing & do not need to retain any existing outputs.

TESTDATA subdirs cleared by testdatainit

 $TESTDATA
 :     :-----ftp         ---
 :     :-----jobctl       0  <-- '0' marks subdirs cleared by testdatainit
 :     :-----joblog       0    - Job Debug logs stored here (by joblog script)
 :     :-----jobmsgs      0    - vital/error messages here (date/time stamped)
 :     :-----jobparms1   --- SYSIN data cards, originally embedded in JCL
                             jobparmx1 utility extracts to $TESTLIBS/jobparmx1
                             dates appended to allow updates for future runs
                             jobparms1 utility copies current cards each day
                             from $TESTLIBS/jobparmx1 dropping date stamps
 :     :-----jobparms2   --- SYSIN data cards that do not need updates
 :     :-----jobtmp       0
 :     :-----mstr        --- Master datafiles
 :     :-----rpts         0
 :     :-----sysout       0
 :     :-----tape        -?- Tape files (might clear if only outputs)
 :     :-----tmp          0
 :     :-----wrk          0

 #1. cdd                    <-- change to $TESTDATA superdir

 #2. testdatainit           <-- run the testdatainit script
     ============           <-- will prompt y/n to proceed or not
     --> y                  <-- to proceed or 'n' to cancel

 #3. joblog 28401d23.ksh   <-- run JCL/script being test/debugged
     ===================

 #4. llr rpts              <-- display report files
     ========                - 'llr' lists all subdirs & all files in rpts

 #5. llr jobtmp            <-- display temp/work/inter-step files
     ==========

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

4M3. Testing & Debugging Aids

joblog - capture logs via 'tee'

Console logging is highly recommended (especially for production) since it captures everything that happens on the screen, including operator commands & replies to prompts. See console logging activation on page '1U1' & '1U2'.

But until you get console logging activates, you could use the joblog script (provided in /home/uvadm/sf/IBM/...).

These scripts capture the JCL/script screen displays into a file using the unix/linux 'tee' command. The log filename is created by dropping the '.ksh' extension from the jobname & then appending '.log'.

 28401d23.ksh          <-- execute JCL/script (with no logging)
 ============

 joblog 28401d23.ksh  <-- execute & capture log in $TESTLIBS/joblog/28401d23.log
 ====================

 joblogA 28401d23.ksh <-- execute & capture log in $TESTDATA/joblog/28401d23.log
 ====================   - the 'A' version also turns on COBOL Animation
                        - saves having to 'export ANIM=+A' to animate

llr - display all files in multilevel subdirs

The 'llr' script is convenient to examine the contents of multi-level subdirs, such as $RPTS, $JTMP, or the entire $TESTDATA.

 #4. llr rpts > tmp/llr  <-- run the 'llr' script & capture output
     ==================

 #4a. uvlp12 tmp/llr      <-- print results (or vi, more, etc)
      ==============

sample llr of rpts after running 1 job

 ./rpts:
 drwxrwxr-x    2 laval3   users        4096 Feb 13 08:43 070213

 ./rpts/070213:
 -rw-rw-r--    1 laval3   users       40033 Feb 13 08:43 28401D23_S0060_E212640C_084349.lvl
 -rw-rw-r--    1 laval3   users        2437 Feb 13 08:43 28401D23_S0060_E212640C.hex

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

4M4. Testing & Debugging Aids

jobstop - pause at each step

The JCL converter inserts a call to function 'stepctl51' st the begining of each step. This function normally just calculates StepTimes, but can be activated to stop at the begining of each step (or a specified step) & wait for the operator to enter cont(inue), clear, endok,or endab.

 stepctl51  # test oprtr jobstop/jobclear
 #========  # inserted at begining of each step by JCL converter option 'b2'

Pausing at the begining of each step allows you to investigate the files in data/... & jobtmp/JOBXX/GDG/data/... that might be deleted at the end of the step. Also note JCL converter option 'v3' will #comment out the 'rm's (converted from original 'DELETE's).

execute job with jobstop activated

 #1. Login --> /home/mvstest OR your homedir
 #2. cdd --> $HOME/testdata

 #3. jobstop jobxx.ksh   <-- activate stop at begin each step
     =================     - stores control record in jobctl/jobxx.ctl

 #4. joblog jobxx.ksh    <-- execute the job
     ================      - will get following display at begin each step

   --> jobxx.ksh paused by job control file: jobctl/jobxx.ctl
       - job control record: jobxx.ksh S0000 111125_124512
       - waiting until reply 'go' or 'clear'

 #5. Login on a 2nd screen --> $HOME
 #6. cdd --> $HOME/testdata

 #7. l data      <-- investigate data files on screen#2
     =======       - while jobxx paused on screen#1

 #8. l jobtmp/JOBXX/GDG/data/  <-- investigate GDG files in jobtmp
     ========================

option to specify stop step

The 'jobstop' script may also specify the 1st step# to stop (art end of step)

 #6a. jobstop jobxx.ksh stop=S0030 <-- store jobctl file with stop step#
      ============================

 #6b. joblog jobxx.ksh    <-- execute the job
      ================       - will stop at end of step S0030
                               & subsequent steps if you reply 'cont'inue

See 'jobstop' script listed on page '9A6'

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

4N1. Converting YOUR MVS JCL to Korn shell scripts

jcl2ksh51 - reconvert 1 JCL to script

Pages '4J1' - 4K4 documented the initial conversion of All JCL. Then you should test/debug 1 or 2 JCL/scripts to verify the conversions.

 jcl0 -------> jcl1 --------------> jcl2 -------------> jcl3 ------------> jcls
      cleanup       PROC/SLI expand      convert to ksh      prompt & copy

As an example, we will convert 'JAR100', a demo JCL supplied with Vancouver Utilities in /home/uvadm/mvstest/jcl0/JAR100. You can see it listed on page '1C1' & the expected output script on page '1C2'.

 #0a. Login as appsadm ---> /home/appsadm

 #0b. cdl  --> $TESTLIBS

 #1. jcl2ksh51 jcl0/JAR100.jcl    <-- convert 1 JCL at a time
     =========================

alternate example from City of Lynn Valley

 #1a. jcl2ksh51 jcl0/28401D23.jcl   <-- convert 1 JCL at a time
      ===========================

prompt/overwrite warning

The final destination is 'jcls' where JCL/scripts must be copied to be found by the search PATH. Before overwriting any existing JCL/script, you will be prompted to answer 'y' or 'n'.

If you had made substantial modifications to the existing script, you might want to answer NO. Then you could save modified parts of existing script (in tmp subdir), copy the new script from jcl3 to jcls, then edit the new script in jcls & read in modified parts of the previous script from the saved version (or vice versa if it were easier to read new parts into the existing).

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

4N2. Converting YOUR MVS JCL to Korn shell scripts

Re-Convert All JCL using 'jcl2ksh51A' script

'4M1' suggested test/debug 1 or 2 JCL/scripts & modifying option/control files for optimum results.

We now suggest you reconvert all JCL/scripts, to realize the improvements in all JCL/scripts. You can do this quickly using the 'jcl2ksh51A' script (vs step by step method required on the initial conversion of All JCL).

      cleanup          jclproc51           jclunix51              cp
 jcl0 -------> jcl1 --------------> jcl2 -------------> jcl3 ------------> jcls
      cleanup       PROC/SLI expand      convert to ksh      prompt & copy

 #0a. Login as appsadm ---> /home/appsadm

 #0b. cdl  --> $TESTLIBS

 #1. jcl2ksh51A all
     =============
     - convert all JCL from jcl0/... thru several steps to scripts in jcl3/...
     - jclunixop51 has options to use ctl/datactl53I to supply file types,
       record sizes, Indexed keys, etc
     - see more explanations on pages '4K1' - 4K3.

2. The conversion team leader would now assign the various JCLs to the various team members for testing & debugging
   

 #3. cp jcl3/??? jcls
     ================
     - team members will copy JCL/scripts 1 at a time to jcls/... (in PATH)
       just before they are ready to test/debug each script
     - this allows us to reconvert anytime to jcl3/... to improve conversions
       after updating datactl53 & reloading datactl53I (as shown above)

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

4N3. Testing & Debugging Aids

alldiff2 - diff report for all files in 2 dirs

The 'alldiff2' script will run the unix 'diff' utility on all pairs of files in 2 subdirs. The unix 'diff' command is a marvelous thing. It shows you the differences between any 2 text files.

I recommend you use 'alldiff2' whenever you make changes to the JCL converter or the control files.

First save the existing scripts as jcl3.old, remake jcl3, rerun the converter, & then run alldiff2 to verify that the changes made are the changes you intended & nothing else has gotten screwed up.

You can use the 'newold' script to change the name & make the new subdir.

 #1a. Login as yourself or appsadm

 #1b. cdl ---> $TESTLIBS

2. Modify the control files to enhance conversions. See ctl/jclunixop51 listed at MVSJCL.htm#3E1. See ctl/datactl53I listed on page '3F5' or '4K2'
   

 #3. newold jcl3   <-- script to 'mv jcl3 jcl3.old' & 'mkdir jcl3'
     ===========

 #4. jclxx51 jcl2 jcl3       <-- reconvert all JCL in jcl2 to ksh in jcl3
     =================

 #5. alldiff2 jcl3.old jcl3  <-- run alldiff2 script
     ======================    - saves jcl3.dif in the tmp subdir

 #6. uvlp12 tmp/jcl3.dif     <-- print the jcl3.dif file
     ===================       - or vi, more, etc

sample jcl3.dif

Here is a sample dif file resulting from updating ctl/datactl53I. We added 'topi=$TAPE2' onto the control file line for data file 'tu.f01.e212801.adrpos'. We then ran uvcopy loadcat3I to reload the indexed file & reconverted all JCL as shown above.

 37c37
 < exportgen0 0 E211801 $TAPE/tu.f01.e211801.adrpos_
 ---
 > exportgen0 0 E211801 $TAPE2/tu.f01.e211801.adrpos_
 diff file# 10 - jcl3.old/... vs jcl3/24599j04.ksh

 97c97
 < exportgen1 +1 E212990 $TAPE/tu.f01.e211801.adrpos_
 ---
 > exportgen1 +1 E212990 $TAPE2/tu.f01.e211801.adrpos_
 diff file# 78 - jcl3.old/... vs jcl3/28401j04.ksh

2 different of 280 files compared jcl3.old to jcl3

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

4O1. Aids & Techniques to assist Your Testing/Debugging

setup 'testdata' in Your homedir ?

If you have multiple programmers, you might need to setup the testdata superdir in programmer homedirs to prevent update conflicts.

 /p1/apps
 :-----testdata            <-- RUNDATA=$TESTDATA=/p1/apps/testdata
 :     :-----jobctl            - for jobstop stop at begin each step for debug
 :     :-----joblog            - Job Debug logs stored here (by joblog script)
 :     :-----jobmsgs           - progress msgs (step begin, end Normal/AbTerm)
 :     :-----jobparms1         - current datacards from $RUNLIBS/jobparmx1 at 6PM
 :     :-----jobparms2         - datacards from $RUNLIBS/jobparmx2 at 6PM
 :     :-----jobtmp            - job temporary files
 :     :-----mstr              - master files
 :     :-----rpts              - reports
 :     :-----sysout            - COBOL DISPLAY upon SYSLST reports
 :     :-----tape              - tape files reassigned to disc by JCL converter
 :     :-----tmp               - misc temp files & sort work files
 :     :-----wrk               - work files (inter-step)

Here is how 'userx' might setup his own testdata superdir, copy all data files, & modify his profile to use the private version of testdata.

1. Login ---> /home/userx
   

 #2. mkdir testdata            <-- make private testdata superdir
     ==============

 #3. cp -r $TESTDATA testdata  <-- copy all files from shared testdata
     ========================

 #4. vi .bash_profile          <-- edit profile to modify $TESTDATA
     ================

     export TESTLIBS=$TESTLIBS
     export TESTDATA=$TESTDATA       <-- existing definitions in profile
     export CNVDATA=$CNVDATA

     export TESTLIBS=$TESTLIBS
     export TESTDATA=$HOME/testdata     <-- change ONLY TESTDATA def
     export CNVDATA=$CNVDATA

 #5a. exit              <-- logoff

 #5b. Login             <-- log back on to activate new TESTDATA definition

 #6a. echo $TESTDATA    <-- verify change effective

 #6b. cdd               <-- alias cdd should not take you to $HOME/testdata

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

4O2. Aids & Techniques to assist Your Testing/Debugging

uvhdcob display copybook names with data

uvhdcob demo from /home/uvadm

 uvcopy cobmap1,fili1=tf/custmas1,filo1=tmp/custmas1
 ===================================================
 - make the cobmap required from supplied copybook

 uvhdcob dat1/custmas1 tmp/custmas1
 ==================================

 dat1/custmas1 rcsz=256 totrecs=32 current=1 fsiz=8192 fptr=0
 cobmapfile=maps/custmas1 today=199911291108 datalastmod=1999112910
 rec#       1 fieldname occurs  bgn end typ<------ data (hex if typ=p/b) ----->
 001 cm-num                       0   5 n  130140
 002 cm-delete                    6   9
 003 cm-name                     10  34    EVERGREEN MOTORS LTD.
 004 cm-adrs                     35  59    1815 BOWEN ROAD
 005 cm-city                     60  75    NANAIMO
 006 filler001                   76  76
 007 cm-prov                     77  78    BC
 008 filler002                   79  79
 009 cm-postal                   80  89    V9S1H1
 010 cm-phone                    90 101    604-754-5531
 011 cm-contact                 102 119
 012 cm-thisyr-sales       012  120 124pns 001234567C
 013 cm-lastyr-sales       012  180 184pns 001234567D
 014 cm-thisyr-xft              240 244pns 4320202020
 015 cm-lastyr-xft              245 249pns 2020202020
 016 filler003                  250 255
 null=next,r#=rec,s=search,u=update,p=print,i=iprint,w=write,t=tally,c=checkseq
 ,e=exit to uvhd, q=quit, ?=help --> q

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

4O3. Aids & Techniques to assist Your Testing/Debugging

uvhdcob sample for City of Lynn Valley

 #1a. Login as yourself --> your homedir

 #1b. cdd       <-- change to $TESTDATA

 #2. uvhdcob mstr/e2121653/mtaxe.piscines.dat $TESTLIBS/maps/e212159b r83
     ====================================================================

sample uvhdcob for the piscines file

 uvhdcob mstr/e2121653.mtaxe.piscines.dat lastmod=20070307:1612
 record#=1 totalrecs=263 recsize=83 filesize=21829 fileptr=0
 cobmap=/tax/cnvdata/maps/e212159b today=20070322:1249
 rec#       1 fieldname occurs  bgn end typ<------ data (hex if typ=p/b) ----->
 001 fp-role-k                    0  19    015     5  14   4
 002 fp-code-maj                 20  20pns 1C
 003 fp-dt-crea                  21  25pns 019910305C
 004 fp-dt-maj                   26  30pns 019920319C
 005 fp-mat1                     31  36pns 86532599502C
 006 fp-mat2                     37  41pns 000000000C
 007 fp-code-post                42  47    H7K3E2
 008 fp-nbr-pisc                 48  48pns 2C
 009 fp-code-pisc                49  49
 010 fp-no-semaine               50  51pns 000C
 011 fp-no-vendeur               52  53pns 000C
 012 fp-annee-fact               54  56pns 01991C
 013 filler001                   57  81
 rec#=1 of 263,null=next,r#=rec,s=search,u=update,p=print,i=iprint,w=write
 ,t=tally,c=chkseq,e=exit to uvhd,q=quit,?=help -->

script to save having to specify the map

We can use the data conversion control file (ctl/datacnv54I) & the 'uvhdc' script to save having to specify the copybook map & to enable running uvhdcob from any location & avoid having to code recsize for indexed files.

 #2a. uvhdc mstr/e2121653/mtaxe.piscines
      ==================================

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

4P1. Converting YOUR MVS JCL to Korn shell scripts

Determine solutions for any 3rd party software

The JCL converter automatically converts SORT, IDCAMS, IEBGENER, and some DITTOs, but you may need conversion solutions for 3rd party software such as EASYTRIEVE.

You can code equivalent solutions using uvcp, uvsort, & uvcopy, but you may have to write COBOL programs for complex EasyTrieves.

Easytrieve conversion to 'uvcopy'

As of March 2008, the Easytrieve conversion is documented separately in EZTRVetc.htm.

'ez2uvcopy' is a Vancouver Utility (from UV Software) to convert CA Easytrieve to the uvcopy interpretive language. 'uvcopy' is a powerful data manipulation language that was developed to replace various mainframe utilities when converting to Unix or Linux systems.

uvcopy provides functions that are non-existent in the usual Unix utilities:

• Fixed Length record processing without LineFeeds
• Indexed file compatibility with Micro Focus COBOL (fixed & variable length)
• Packed decimal field processing
• Binary field processing choice of & conversion between Big-End & Little-End
• Fixed field processing, most unix utilities do not provide column addressing
• Translate EBCDIC to ASCII & vice versa, entire record, or selectively by field

uvcopy is somewhat similar to the IBM 360 assembler language, so if you have a mainframe background the code will look familiar to you. In addition to the usual basic instructions, uvcopy has many powerful instructions for scan/replace, table processing, etc.

uvcopy has the power of assembler but without the complexity of compiling since it is 'interpretive' (just edit the parameter file & rerun).

There is a lot of documentation for uvcopy, but if you have a mainframe background, I think you could get a quick start by studying the examples given in UVjobs1.htm. Then you could run the 'ezdemo2' conversion given in Part 1 of EZTRVetc.htm & refer to the uvcopy3.htm instruction manual as required.

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

4Q1. Converting YOUR MVS JCL to Korn shell scripts

Setup Backup scripts now (vs later)

Setup Your backup scripts now to protect your programmers from 'oops'. See several backup scripts suggested in ADMjobs.htm#Part_3 (& Part 4).

We recommend setting up 'crontabs' to backup cnvdata, testdata,& testlibs every night to both tape & disc (documented in ADMjobs.htm#Part_5). Those procedures provide 2 days backups on disc for immediate recoveries

The backup scripts & crontabs are stored in the 'appsadm' home directory.

appsadm - Application Administrator

We recommend you setup a login/userid 'appsadm' to serve as the applications administrator for the unix/linux site. The appsadm home directory would hold various scripts, crontabs, log files, etc used in application administration. Here are some suggested sub-directories:

 /home/appsadm
 :-----bin              - binaries for site developed/modified programs
 :-----ctl              - control files (miscellaneous)
 :-----env              - master copies of profiles etc
 :                        modified appropriately for your site
 :-----log1             - console logging files (currently active)
 :     :-----user1        - sub-directoried by user login
 :     :-----user2
 :     :     :-----070306_175400
 :     :-----.etc.
 :-----log2             - console logging files (for current month)
 :     :-----user1
 :     :-----user2
 :     :     :-----070304_153300
 :     :     :-----070305_134500
 :     :     :-----070306_175400
 :     :-----.etc.
 :-----log3             - console logging files (for last month)
 :     :-----user1
 :     :-----user2
 :     :-----.etc.
 :-----logs             - backup logs (run by cron)
 :
 :-----pf             <-- uvcopy jobs developed/modified by site admin
 :
 :-----sf             <-- shell scripts developed/modified by appsadm
 :                      - also holds the 'crontabs' used to schedule backups
 :                        & any other jobs you wish to run automatically
 :
 :-----src              - source for any programs developed/modified by appsadm
 :-----tmp

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

4R1. Converting YOUR MVS JCL to Korn shell scripts

setup console logging

This is a VITAL feature to replace the console logging systems provided by proprietary mainframe systems. Console Logging uses the Unix/Linux 'script' command inserted at the end of the profile to create a date/time stamped console log file which captures all console I/O until the operator logs off.

Console log files must be processed (to remove screen control codes) before being viewed or printed & this is accomplished automatically when the user logs off & back on. He may then use the logview script to view or print the latest (or earlier) log file.

See the sample console log created when the conversion test/demo jobs are executed on page '1U3'. See complete details about console logging in ADMjobs.htm#Part_6.

Console logging is activated by uncommenting 4 lines at the end of the supplied profile. See the stub_profile listed at ADMjobs.htm#1C1. You must also setup a subdir in /home/appsadm/log1,2,3 matching your userid.

Console logging should be mandatory for operators, but can be optional for programmers, who can use the 'joblog' script during test/debug.

 #1. vi .bash_profile   <-- edit your profile
     ================     - uncomment following 4 lines near end

     login1 || exit 2          # exit here if 2nd login
     logfixA                   # process log1 file to log2 (to allow read/print)
     echo 'console logging requires aliases to be stored in .bashrc or .kshrc'
     exec script $APPSADM/log1/$LOGNAME/$(date +%y%m%d_%H%M%S)

 #2a. cd /home/appsadm    <-- change to appsadm & make subdirs matching userid
 #2b. mkdir log1/userx    <-- make subdir in log1 for current log collection
 #2c. mkdir log2/userx    <-- make subdir in log2 for current month collection
 #2d. mkdir log3/userx    <-- make subdir in log3 for last month history

 #3a. exit            <-- logoff
 #3b. Login           <-- log back in to activate console logging

 #4a. 28401d23.ksh    <-- run some of your JCL/scripts
      ============
 #4b. llr rpts        <-- list some directories, etc
      ========

 #5. logoff & back on to process console log
     (from /home/appsadm/log1/userx/... to log2/userx/...)

 #6. logview          <-- display your log files
     =======
     --> 1            <-- enter 1 to view the latest

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

4S1. Converting YOUR MVS JCL to Korn shell scripts

Parallel, Re-transfer, Setup for production,& go live

1. Run parallels with mainframe when you have enough JCL/scripts debugged
   
   
2. Re-transfer mainframe JCL,COBOL,& DATA a few times during conversion period
   
   
3. Setup the production machine.
   
   
4. Go live (over a weekend usually), You will need to re-transfer & reconvert all data files as documented on page '4I2' or in MVSDATA.htm. The JCL/scripts & programs will not need re-transfer/reconvert on the 'go live' weekend, since you will already have them well tested.
   
   
5. See 'Part_7' Operating Aids - Console Logging (captures all console messages) - Job Logging (captures only VITAL & ERRor messages)
   

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

Part_5 MVS JCL conversion - Special Sub-Systems

Part 5 GDG files - Contents

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

Part 5 MVS JCL conversion - Special Sub-Systems

Part 5 GDG files - Contents (continued)

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

5A1. Vancouver Utilities GDG system - Introduction & Overview

GDG Enhancements

The Vancouver Utilities provides GDG (Generation Data Group) processing similar to the mainframe facility. In May 2007, the VU GDG system was significantly enhanced and some new features go well beyond the original implementation provided on the mainframe.

Vancouver Utility GDG system - Basic Features

1. After mainframe GDG files are converted (from EBCDIC to ASCII, preserving packed/binary fields), they are copied to the testdata/proddata directories & renamed with suffix '_000001' (1st generation using 6 digit#).
   
   
2. When mainframe JCL is converted to Korn shell scripts, GDG files are identified with a trailing '_' underscore only.
   
   
3. The JCL calls Korn shell 'functions' to determine the appropriate generation. 'exportgen0' defines the latest/highest generation (for reading). 'exportgen1' defines the next generation (for writing).
   
   
4. Earlier versions of exportgen1 incremented the generation# immediately (vs delaying until the job terminated normally as on the mainframe). If a multi-step job terminated abnormally, you were advised to use the 'restart' facility (provided for every step by the VU JCL converter). But if for some reason you wanted to restart from the begining, you had to manually remove any new generations created before the abterm.
   
   
5. The abterm problem is now solved by an enhanced version of 'exportgen1' & a new function 'jobend51' called at Normal End of Job. 'exportgen1' now assigns new generations to the 'jobtmp' directory & at Normal EOJ, function 'jobend51' will move the jobtmp files back to the $RUNDATA directories. This allows you to rerun abterm jobs from the begining , but if you do restart, you will be prompted if it is OK to move any jobtmp files back to the $RUNDATA directories.
   

6. Earlier versions of exportgen1 used a hard-coded number of generations to be accumulated before erasing older generations, unless you coded the gdg=... keyword on all exportgen1's for the file, which could be problematic.
   
   
7. The new system provides an Indexed control file which exportgen1 accesses to get the desired number of generations for each file.
   
   
8. We provide a utility to automatically create the indexed file by extracting all GDG filenames from all JCL/scripts, sorting,& dropping duplicates. You then edit the control file to modify the default number of generations as desired & run another utility job to load the indexed file.
   

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

5A2. Vancouver Utilities GDG system - Introduction & Overview

Vancouver Utility GDG system - Advanced Features

The indexed control file allows us to provide some significant enhancements that go well beyond the original GDG implementation on the mainframe.

1. You can specify a prior generation of a file to be defined by exportgen0 for the next run only, or until a specified expiry date/time is reached. This avoids having to modify the JCL/scripts. Note that you only have to modify one entry in the control file, whereas you could easily miss some of the possible multiple references in one or more JCL/scripts.
   
   
2. You can specify range processing for a series of prior generations This is a powerful feature that 1 customer is already planning to make good use of. On the mainframe he had 30 tapes that had to be processed one at a time by a batch COBOL program & the operator simply mounted the tapes in turn.
   
   
3. On the new unix system, all tape files are automatically converted to generation disc files, so to process the 30 tapes (now GDG disc files) separately, the customer might have to modify the JCL to hard-code the next desired generation# or he might specify via an operator keyin.
   
   
4. With the enhanced GDG system, he edits the control file specifying the low to high range of generation#s to be processed. He can then run the batch job 30 times to process the 30 files (with no changes to JCL/scripts & no operator generation# keyins).
   
   
5. This is possible because 'exportgen0' uses the current next generation#, which is incremented by the 'jobend51' function at normal EOJ. At the high end of the range, processing returns to normal, but an historical record is maintained in the indexed file database, making it easier to reactivate if the same cycle is repeated periodically.
   
   
6. You can specify 'opt=c' (confirm) on control file entries to cause exportgen0 to prompt the operator to confirm the generation# selection, or to enter an alternative 6 digit generation#.
   
   
7. The new system maintains a history of the last 30 accesses by exportgen0 and exportgen1. You can look at the control file (with uvhd) and for each of the last 30 accesses, you can see: date:time, generation# selected, lowest:highest generations on-file, jobname, step#,& program of last access.
   
   
8. Each of the last 30 entries that define access history is identified with one of three status codes: 'G0'=exportgen0(reading current/selected gen), 'G1'=exportgen1(writing next gen), or 'AB'=ABnormal Termination (indicates file not moved from jobtmp/subdirs back to RUNDATA/subdirs).
   

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

5B1. MVS JCL conversion - Generation files

Generation Data Groups

Mainframe GDG files are implemented via unix/linux Korn shell functions (exportgen0, exportgen1/2/..., exportgen-1/-2/...,& exportgenall). These functions are listed later beginning on page '5J0'. Here is a sample conversion (before & after) of GDG files:

JCL conversion - GDG files (BEFORE & AFTER)

 //ACCTMAS  DD DSN=GL.ACCOUNT.MASTER(0),DISP=SHR
 //ACTLIST  DD DSN=GL.ACCOUNT.ACNTLIST(+1),DISP=(,CATLG,DELETE),
 //            UNIT=DISK,SPACE=(TRK,(25,25),RLSE),
 //            DCB=(MODEL.DSCB,LRECL=133,BLKSIZE=6118,RECFM=FBA)

 exportgen0 ACCTMAS gl/account.master_           #<-- current generation
 exportgen1 ACTLIST $JTMP/gl/account.acntlist_   #<-- next generation

Note that the '(0)' suffix on an MVS DSN indicates the current generation & '(+1)' indicates the next generation. The JCL converter identifies GDG files with a trailing '_' underscore & uses function 'exportgen0' to define the current generation & function 'exportgen1' to define the next generation (for the following COBOL or utility programs).

Note that exportgen1 writes the next generation to $JTMP/... for move back to gl/... at successful end of job.

Data filename conversion

After the data files are converted from EBCDIC to ASCII (preserving any packed/binary fields), they must be renamed as they are copied from $CNVDATA/subdirs to $TESTDATA/subdirs.

The 1st generation might be assigned as generation _000001. After a few updates to the account.master file we might have:

 gl/account.master_000001     <-- 1st generation of GDG file after conversion
 gl/account.master_000002
 gl/account.master_000003
 gl/account.master_000004
 gl/account.master_000005     <-- current generation

Generation# does not auto wrap

The unix function exportgen1 does not automatically handle generation wrap (as did the mainframe), but note that if you had a generation file that was updated once a day it would take 2500 years to exceed 900000.

However uvcopy jobs are provided to rename files with suffixes over 900000 The uvcopy job is 'gdgreset6' for 6 digit GDG#s (versions since Dec 2005). and 'gdgreset4' for 4 digit GDG#s (versions older than Dec 2005).

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

5B2. MVS JCL conversion - GDG files

Allowing for Abterms (don't increment GDGs)

Early versions of the exportgen1 function wrote new GDG files into the same directory as the prior generations, thus creating a problem if multi-step JCL/scripts terminated abnormally & had to be rerun.

You might have been able to use the restart at any step capability, but if not you would have to manually remove any newly created generations before rerunning.

The new version of exportgen1 (exportgen1c) writes new generations of GDG files into the jobtmp/subdirs. When the job reached the normal EOJ point, the 'jobend51' function copies the new generations back to the defined $RUNDATA/subdirs.

Option g0/g1 now controls writing new GDGs to $RUNDATA/subdirs/... or jobtmp/subdirs/... See option g0/g1 in ctl/jclunixop51 listed on page '3E1'.

For g0, you could restart failed jobs at step after failure, else you must remove any new GDGs created up to failure before rerunning.

Generation limits per file

Early versions of exportgen1 used a system wide number of generations for all files, or you had to specify gdg=... as an argument on all instances of exportgen1 for a particular file.

The new version of exportgen1 (exportgen1c) accesses an indexed control file to retrieve the desired number of generations for each file.

When changes are desired, you can edit the text version of the control file (ctl/gdgctl51) & reload the indexed file (ctl/gdgctl51I), which is accessed by exportgen1.

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

5B3. MVS JCL conversion - GDG files

sample GDG control file

 gl/account.acntlist_                     gdg=08
 gl/account.master_                       gdg=10
 gl/account.trans_                        gdg=20 opt=c
 py/payroll.master_                       gdg=30
 py/time.cards_                           gdg=52 next=000021

1. The GDG control file ($RUNLIBS/ctl/gdgctl51) can be automatically created by extracting the 'exportgen1's from all JCL/scripts. See Operating Instructions later on page '5C1'.
   
   
2. If desired, there is an option to include all files in the control file (both GDG & non-GDG).
   
   
3. You will be prompted for the default number of generations per file.
   
   
4. After initial creation, you can edit the control file to specify the number of generations desired for each file.
   
   
5. You can also specify 'opt=c' for operator confirmation of selected gen# & opportunity to enter an alternative 6 digit generation#.
   
   
6. You can specify 'next=...' to override the usual selection of the highest generation. See more about this begining on the following pages.
   
   

   loading the GDG Indexed control file

The actual GDG control file used by exportgen0,exportgen1,etc is an Indexed file for random lookup by filename, but it is much easier to prepare the contents as a text file (for easy editing).

A sample text file is provided in /home/uvadm/ctl/gdgctl51. You could use this as a guide, add your own filenames & desired generations, then load it into the Indexed GDG control file which is $RUNDATA/ctl/gdgctl51I as follows.

This assumes you have setup a user such as 'mvstest' with profiles,directories,& environmental variables (RUNLIBS & RUNDATA) as described in MVSJCL.htm#Part_1.

If setting up your own directories (vs subdirs copied from /home/uvadm/mvstest) you could use scripts mvslibsdirs & mvsdatadirs as at MVSJCL.htm#4C3 & '4C4' and use script copymvsctls to copy sample control files from /home/uvadm/ctl/ as on MVSJCL.htm#4D1.

 #1. login mvstest --> /home/mvstest

 #2. cd $RUNDATA  --> /home/mvstest/testdata

 #3. uvcopy gdgload1[,fili1=ctl/gdgctl51,filo1=ctl/gdgctl51I]
     ========================================================

 #3a. uvcopy gdgload1   <-- same as above (files default as shown)
      ===============

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

5B4. MVS JCL conversion - GDG files

exportgen0 & gdgctl - Exception Processing

Normally exportgen0 defines the latest generation (file with highest 6 digit suffix). Consider the following data files & the 'exportgen0' example:

gl/account.master_000001 gl/account.master_000002 gl/account.master_000003 gl/account.master_000004 gl/account.master_000005

 exportgen0 0 GLMSTR gl/account.master_  <-- JCL/script coding to define the file
 ====================================        for the following COBOL program

 export GLMSTR=gl/account.master_000005  <-- effective result
 ======================================

option to process prior generations

To process prior generations, you could temporarily modify the JCL/script, explicitly coding the desired 6 digit suffix. For example we could code:

 export GLMSTR=gl/account.master_000002   <-- script modified with specific#
 ======================================

            - - - OR - - -

 exportfile GLMSTR gl/account.master_000002 <-- OR use this to display filename
 ==========================================

1. If you hard-code the 6 digit seq#, you have to change 'exportgen0' to 'export' or 'exportfile' since exportgen0 is valid only for filenames with trailing '_'
   
   
2. 'export' is the underlying command & 'exportfile' is a function which does issue the 'export' command, but in addition displays the filename for the console log.
   
   

   disadvantages of changing the JCL/scripts

3. You have to remember to change them back after your reruns.
   
   
4. Anytime you edit the JCL/scripts, there is the possibility of making mistakes.
   
   
5. There may be multiple 'exportgen0's in multiple JCL/scripts to be modified for the reruns desired.
   

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

5B5. MVS JCL conversion - GDG files

exportgen0 & gdgctl rerun facility

In May 2007, a new version of exportgen0 (exportgen0c) was developed to provide a powerful rerun (prior generation access) capability.

This system uses the same control file ($RUNDATA/ctl/gdgctl51) that was 1st added to carry the desired no of generations per file (for exportgen1c).

Consider the following few lines of the gdgctl file & the following generations of the account.master file:

      gl/account.acntlist_     gdg=4
      gl/account.master_       gdg=6   <-- samples extracted from ctl/gdgctl51
      gl/account.trans_        gdg=50 opt=c

      gl/account.master_000001
      gl/account.master_000002
      gl/account.master_000003         <-- last 5 generations of account.master
      gl/account.master_000004
      gl/account.master_000005

If you wanted to rerun a JCL/script using prior generation _000002, you could modify the control file as follows:

      gl/account.acntlist_     gdg=4
      gl/account.master_       gdg=6   next=000002   <-- gen# for rerun
      gl/account.trans_        gdg=50  opt=c

1. It is safest to edit only the ctl/gdgctl51 text file, not the indexed file (ctl/gdgctl51I.dat) used by exportgen0 (& the jobend51 function).
   
   
2. After modifying the text file, you must load it to the indexed file using 'uvcopy gdgload1'
   
   
3. Or you could update the Indexed file directly using 'uvhd' (as shown later on page '5C3').
   
   
4. Or if very careful, you could edit the Indexed file directly using the 'vi' editor since we do have the text file as backup & we can recreate the text file by rerunning jcldata56.
   
   
5. At the end of the 1st JCL/script with exportgen0 reference to account.master, the 'next=000002' is disabled by changing it to 'next=000000'
   
   
6. You do have to remember to clear the original 'next=000002' from the text file version before you reload the indexed file for some other reason.
   
   
7. It might be safer to 1st run the 'gdgunload1' job to convert the indexed file back to a text file for future edits & reload.
   

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

5B6. MVS JCL conversion - GDG files

Expiry Times

The system allows you to specify an expiry time when modifying the gdgctl file. For example:

     gl/account.master_  gdg=6  next=000002_yymmdd:HHMMSS
     ====================================================

The exception processing (defining prior generations of the file) is disabled if the expiry date has been exceeded when the next JCL/script is run with exportgen0 references to the account.master.

Progressing thru a range of prior generations

The system also allows for successive runs to process thru a range of prior generations. For example:

     gl/account.trans_ gdg=50 opt=c next=000001(000001:000012)
     =========================================================

This would allow you to load the transaction files for all 12 months, before you do any processing, then process the 12 months on successive runs. (with no changes to JCL/scripts or control file required).

After the 12th run the control file entry would be updated by the jobend51 function executed at Normal EOJ, to:

     gl/account.trans_ gdg=50 opt=c next=000000(000001:000012)
     =========================================================

IE, the next gen# is set to '000000' to indicate the processing is completed but not lose a record of the manual edits. The next reference by exportgen0 for this file would define the then highest generation# (which might still be '000012').

You could combine expiry times with progression, but it is not necessary, since the progression automatically ends the exception processing when the upper limit is reached. Expiry dates are ignored if a low < high range is specified, but the format would be:

     gl/account.trans_ gdg=50 opt=c next=000001(000001:000012)yymmdd:HHMMSS
     ======================================================================

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

5B7. MVS JCL conversion - GDG files

Retaining History in gdgctl

An earlier simplified example of a 1 time access to a prior generation is shown below, followed by the actual format required, which retains some history of your prior generation overrides in the gdgctl file.

     gl/account.master_ gdg=6 next=000002  <-- gen# for next access (1 time)
     ======================================

     gl/account.master_ gdg=6 next=000000  <-- reset to this at Normal EOJ
     ======================================

     gl/account.master_ gdg=6 next=000002(000002:000002)yymmdd:HHMMSS <-- req'd
     ================================================================

     gl/account.master_ gdg=6 next=000000(000002:000002)yymmdd:HHMMSS <-- reset
     ==============================******============================

gdgctl illustrating prior gen# over-rides

 gl/account.acntlist_ gdg=08
 gl/account.master_   gdg=10 next=000002(000002:000002)000000:000000 <--note1
 gl/account.trans_    gdg=20 next=000002(000002:000002)070529:235959 <--note2
 py/payroll.master_   gdg=30 op=c                                     <--note3
 py/time.cards_       gdg=52 next=000001(000001:000012)000000:000000 <--note4
 py/time.cards.div2_  gdg=52 next=000001(000001:000012)070529:235959 <--note5

1. 'next=000002' will be reset to 'next=000000' (disabling over-ride) at the end of the 1st JCL/script that references the file with exportgen0.
   
   
2. Specify an 'expiry date' if you want the over-ride to persist for multiple runs until some specified date/time.
   
   
3. Specify 'opt=c' if you want an operator prompt to confirm gen# selection or enter an alternative generation#
   
   
4. The generation# will be incremented each time you run the JCL/script referencing the file. After the 12th run it will be set to 'next=000000(000001:000012)' disabling the over-ride, but leaving some history, in case you wanted to reactivate in future.
   

5a. You could also specify a non-zero expiry date/time, but not necessary since the override is automatically disabled at the high end of the range.

5b. Expiry dates are ignored for ranges (when low & high different), but you could code expiry dates with ranges for an historical record.

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

5C1. MVS JCL conversion - GDG files

creating the gdgctl file

For these discussions, we assume you have already setup userid mvstest & copied the demo files from /home/uvadm/mvstest/* to /home/mvstest/... as instructed on page MVSJCL.htm#1P1 thru 1P3. And then converted the supplied demo JCLs & COBOL programs as per 1Q1-1R3.

If you had very few GDG files you could create ctl/gdgctl51 with the editor (see the sample further below), but in case you have a lot of GDG files, we provide a utility job. 'jcldata56' will read all JCL, extract all DSN's,& sort with data reduction to 1 line per unique filename.

There are several options (as shown below at #3), but the ones you might want to change are 'g15' default generations & 'h40' the column# where you want to insert the gdg=...

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

5C2. MVS JCL conversion - GDG files

Op. Instrns. to create gdgctl file

 #1a. login mvstest,appsadm,or yourself --> /home/mvstest,appsadm,homedir

 #1b. cdl --> $TESTLIBS (/home/mvstest/testlibs, /p1/apps/testlibs, ???)
           - see directories,profiles,$RUNLIBS,etc discussed page '1A1' +

 #2. [ jcl2ksh51A all ]      <-- we assume JCL conversion already completed
     =================        - left all converted scripts in jcl3/...

 #3. uvcopy jcldata56,fild1=jcl3,filo2=ctl/datafiles56,uop=c0f2g99h40j1
     ==================================================================
     options: c0 = no filecounts, f2 = exportgen files only, g99 = default gens
              h40 = col# to insert gdg=..., j1 = remove $JTMP/

 #3a. uvcopy jcldata56     <-- same as above (files default as shown)
      ================       - sample output shown below

     gl/account.master_                       gdg=31
     gl/account.trans_                        gdg=31 opt=c
     py/payroll.master_                       gdg=31

These samples are based on the test/demo JCLs shown in Part_1 (but several lines removed for this illustration).

 #4. cp ctl/datafiles56 $RUNDATA/ctl/gdgctl51
     ========================================
     - copy/rename for GDG control file

 #5. cdd  (alias cdd='cd $RUNDATA') --> /home/mvstest/testdata
     ===

 #6. vi ctl/gdgctl51    <-- edit to modify no of generations as desired
     ===============      - replace any $SYMBOLS with values

 #7. uvcopy gdgload1,fili1=ctl/gdgctl51,filo1=ctl/gdgctl51I
     ======================================================
     - load Indexed file to supply file info to JCL converter

 #7a. uvcopy gdgload1   <-- same but easier (files default as shown above)
      ===============

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

5C3. MVS JCL conversion - GDG files

updating text file with vi & reloading Indexed file

 #1. login mvstest --> /home/mvstest

 #2. cdd  (alias cdd='cd $RUNDATA') --> /home/mvstest/testdata
     ===

 #3. vi ctl/gdgctl51    <-- view the supplied file
     ===============

     gl/account.acntlist_  gdg=31
     gl/account.master_    gdg=31
     gl/account.trans_     gdg=31
     py/payroll.master_    gdg=31
     py/time.cards_        gdg=31

 #3a. update the file as shown below:

     gl/account.acntlist_  gdg=08
     gl/account.master_    gdg=10 next=000002(000002:000002)_991231:235959
     gl/account.trans_     gdg=20 opt=c next=000001(000001:000012)000000:000000
     py/payroll.master_    gdg=30
     py/time.cards_        gdg=52

 #3b. quit the editor & reload the Indexed file

 #4. uvcopy gdgload1,fili1=ctl/gdgctl51,filo1=ctl/gdgctl51I
     ======================================================
     - load Indexed file to supply file info to JCL converter

 #4a. uvcopy gdgload1    <-- same as above (files default as shown)
      ===============

 #5.  Run the supplied demo JCL/script (jgl100.ksh) & observe that it
      processes gl/account.master_000002 (NOT the latest gen# 000003

 #5a. jgl100.ksh    <-- run demo job, observe console log
      ==========      - should see input generation ..._000002

 #5b. jgl100.ksh    <-- rerun demo job, observe console log
      ==========      - should see input ..._000003 (last gen#)
                      - override was reset by jobend51 at end 1st run

updated control file supplied

An alternate version of the gdgctl file is supplied with the next=... controls as shown above. We will use it for the jgl220.ksh demos begining on page '5E1'. We will load it as follows:

 #3b. uvcopy gdgload1,fili1=ctl/gdgctl51test2
      =======================================
      - must specify alternate input file (else would default to ctl/gdgctl51)
      - no need to specify output file which defaults to ctl/gdgctl51I

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

5C4. MVS JCL conversion - GDG files

display gdgctl Indexed file with uvhd (char mode)

Rather than updating the text file version & reloading the Indexed file, you could update the Indexed file directly with 'uvhd'. This is safer than updating the indexed file directly with 'vi'.

Note that when the text file is loaded into an Indexed file, you get 2 partitions (gdgctl51I.dat & gdgctl51I.idx).

 uvhd ctl/gdgctl51I.dat r2048u   <-- execute uvhd to display gdgctl file
 =============================     - options: r2048=record-size, u=update

                      10        20        30        40        50        60
 r#        2 0123456789012345678901234567890123456789012345678901234567890123
        2048 gl/account.master_                                 gdg=10
          64 next=000000(000000:000000)000000:000000
         128 000000:000000:G0_000000(000000:000000)_______  _____ _________
         192 000000:000000:G0_000000(000000:000000)_______  _____ _________
         256 000000:000000:G0_000000(000000:000000)_______  _____ _________
         320 000000:000000:G0_000000(000000:000000)_______  _____ _________
         384 000000:000000:G0_000000(000000:000000)_______  _____ _________
         448 000000:000000:G0_000000(000000:000000)_______  _____ _________
         512 000000:000000:G0_000000(000000:000000)_______  _____ _________
         576 000000:000000:G0_000000(000000:000000)_______  _____ _________
         640 000000:000000:G0_000000(000000:000000)_______  _____ _________
         704 000000:000000:G0_000000(000000:000000)_______  _____ _________
         768 000000:000000:G0_000000(000000:000000)_______  _____ _________
         832 000000:000000:G0_000000(000000:000000)_______  _____ _________
         896 000000:000000:G0_000000(000000:000000)_______  _____ _________
         960 000000:000000:G0_000000(000000:000000)_______  _____ _________
        1024 000000:000000:G0_000000(000000:000000)_______  _____ _________
        1088 000000:000000:G0_000000(000000:000000)_______  _____ _________
        1152 000000:000000:G0_000000(000000:000000)_______  _____ _________
        1216 000000:000000:G0_000000(000000:000000)_______  _____ _________
        1280 000000:000000:G0_000000(000000:000000)_______  _____ _________
        1344 000000:000000:G0_000000(000000:000000)_______  _____ _________
        1408 000000:000000:G0_000000(000000:000000)_______  _____ _________
        1472 000000:000000:G0_000000(000000:000000)_______  _____ _________
        1536 000000:000000:G0_000000(000000:000000)_______  _____ _________
        1600 000000:000000:G0_000000(000000:000000)_______  _____ _________
        1664 000000:000000:G0_000000(000000:000000)_______  _____ _________
        1728 000000:000000:G0_000000(000000:000000)_______  _____ _________
        1792 000000:000000:G0_000000(000000:000000)_______  _____ _________
        1856 000000:000000:G0_000000(000000:000000)_______  _____ _________
        1920 000000:000000:G0_000000(000000:000000)_______  _____ _________
        1984 000000:000000:G0_000000(000000:000000)_______  _____ _________..

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

5C5. MVS JCL conversion - GDG files

gdgctl file displayed by uvhd

 uvhd ctl/gdgctl51I.dat r2048u   <-- execute uvhd to display gdgctl file
 =============================     - options: r2048=record-size, u=update

1. Please see the uvhd display on the previous page. We are showing records 2 & 3 after loading the indexed file with ctl/gdgctl51test2. Each 2048 byte record is display on 26 lines (of 64 bytes). Here are the 1st 2 lines for records 2 & 3.
   

        2048 gl/account.master_                                 gdg=12
          64 next=000002(000002:000002)991231:235959
                 - - - 11 lines omitted - - -

        2048 gl/account.trans_                                  gdg=18 opt=c
          64 next=000001(000001:000012)000000:000000
                 - - - 11 lines omitted - - -

2. Only lines 2 & 3 have items that might be updated with uvhd or vi. You might want to modify the number of generations (gdg=12 or gdg=18 above). You might want to add option 'opt=c' to prompt operator to confirm gen# (as shown for the gl/account.trans file).
   
   
3. Some users may have a reason to code the 'next=...' options shown above 'next=000002...' for gl/account.master overrides the normal selection of the highest generation until the expiry date is reached.
   
   
4. 'next=000001(000001:000012)...' on gl/account/trans, will increment the generation# thru a range of previously stored generations from low to high. 'exportgen0' will use the next=... value & 'jobend51/gdgupok1' will increment the generation# at successful EOJ. We will demonstrate later using jgl220.ksh (see pages '5E1' thru '5E11').
   
   
5. Note that the last 2 bytes of each record show as '..' because uvhd shows any unprintable characters as '.'. The 1st '.' is a real period inserted in the last data byte to allow possible updating with the editor. The last byte of the record & the 2nd '.' is x'0A' which is the indexed file record status byte for a good record, whereas x'00' indicates a deleted record.
   
   
6. You can see the hex characters by adding option 'h2' to force display in 'vertical hexadecimal', which is automatic if the record contains any non-character bytes. The above was in character because the only non-char was the LineFeed x'0A' which is expected at the end of text records.
   
   
7. On page '5C5' we will show how to use uvhd to perform the same updates as shown using vi on the text file on the previous page.
   

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

5C6. MVS JCL conversion - GDG files

updating gdgctl Indexed file with uvhd

On this page we will show you only the 'uvhd' commands to update the Indexed file. Please see the records displayed on page '5C3'. The records already have the updates shown below because we loaded the file from ctl/gdgctl51test2 which was already updated with 'vi' before loading the indexed file (the easier way to make extensive updates).

 #1. login mvstest --> /home/mvstest

 #2. cdd  (alias cdd='cd $RUNDATA') --> /home/mvstest/testdata
     ===

 #3. uvhd ctl/gdgctl51I.dat r2048u  <-- start uvhd with options
     =============================      r2048=recsize, u=update

      <--- see uvhd record display on prior page
         - uvhd displays the 1st record & prompts for commands
         - you can reply as shown below:

 #3a. -->    <-- null entry to advance to record #2

 #3b. --> u 64(38),'next=000002(000002:000002)000000:000000'
          ==================================================

easier alternative

Actually the gdgload1 utility inserts zero-filled inactive entries, so you only have to update the 6 digit next gen# as follows:

 #3b. --> u 69(6),'000002'
          ================

 #3c. --> q   <-- quit

Notes

1. If you use uvhd, you must be sure not to modify the keys (1st 50 bytes)
   
   
2. using uvhd is more awkward than an editor, but much safer. uvhd will never change the record size which would corrupt the remainder of the file, since the index partition depends upon all data record being same size. Adding or deleting bytes inadvertently is very easy to do with vi.
   
   
3. Updating the Indexed file directly with 'vi' is dangerous, but it is fast & convenient, and we will show you how on the next page.
   
   
4. After updating with 'vi' you should always run the 'dcheck' utility to ensure the validity of the Indexed file.
   

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

5C7. MVS JCL conversion - GDG files

updating gdgctl Indexed file with vi

 #1. cdd  (alias cdd='cd $RUNDATA') --> /home/mvstest/testdata

 #2. vi ctl/gdgctl51I.dat   <-- start 'vi' on the Indexed file .dat partition
     ====================

 gl/account.trans_                                  gdg=18 opt=c next=000001(0000
 01:000003)000000:000000                         000000:000000:G0_000000(000000:0
 00000)_______  _____ _________  000000:000000:G0_000000(000000:000000)_______  _
 ____ _________  000000:000000:G0_000000(000000:000000)_______  _____ _________
 000000:000000:G0_000000(000000:000000)_______  _____ _________  000000:000000:G0
 _000000(000000:000000)_______  _____ _________  000000:000000:G0_000000(000000:0
 00000)_______  _____ _________  000000:000000:G0_000000(000000:000000)_______  _
 ____ _________  000000:000000:G0_000000(000000:000000)_______  _____ _________
 000000:000000:G0_000000(000000:000000)_______  _____ _________  000000:000000:G0
 _000000(000000:000000)_______  _____ _________  000000:000000:G0_000000(000000:0
 00000)_______  _____ _________  000000:000000:G0_000000(000000:000000)_______  _
 ____ _________  000000:000000:G0_000000(000000:000000)_______  _____ _________
 000000:000000:G0_000000(000000:000000)_______  _____ _________  000000:000000:G0
 _000000(000000:000000)_______  _____ _________  000000:000000:G0_000000(000000:0
 00000)_______  _____ _________  000000:000000:G0_000000(000000:000000)_______  _
 ____ _________  000000:000000:G0_000000(000000:000000)_______  _____ _________
 000000:000000:G0_000000(000000:000000)_______  _____ _________  000000:000000:G0
 _000000(000000:000000)_______  _____ _________  000000:000000:G0_000000(000000:0
 00000)_______  _____ _________  000000:000000:G0_000000(000000:000000)_______  _
 ____ _________  000000:000000:G0_000000(000000:000000)_______  _____ _________
 000000:000000:G0_000000(000000:000000)_______  _____ _________  000000:000000:G0
 _000000(000000:000000)_______  _____ _________  000000:000000:G0_000000(000000:0
 00000)_______  _____ _________  000000:000000:G0_000000(000000:000000)_______  _
 ____ _________  000000:000000:G0_000000(000000:000000)_______  _____ _________
 000000:000000:G0_000000(000000:000000)_______  _____ _________  000000:000000:G0
 _000000(000000:000000)_______  _____ _________.

 #2a. -->vi updates ...

 #2x. -->:wq  <-- write & quit vi editor

 #3. dcheck ctl/gdgctl51I    <-- validate the Indexed file
     ====================      - to ensure you did not screw up with editor

notes re display above

To the 'vi' editor the gdgctl51I.dat records are considered very long lines, since there is only 1 Linefeed at the end of the 2048 byte records. They appear as 26 lines on the screen, since screen lines wrap at 80 bytes. If we printed the original record you would see only the 1st 90 bytes (page-width).

To simulate the screen appearance I ran a uvcopy job 'splitrec1' which inserts a Line-Feed every 80 bytes. I 1st used vi to write 1 record to tmp/gdgctl1.

 uvcopy splitrec1,fili1=tmp/gdgctl1,filo1=tmp/gdgctl2
 ====================================================

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

5C8. MVS JCL conversion - GDG files

Notes re updating gdgctl with 'vi'

1. Shown above is the 3rd record of gdgctl51I after loading from gdgctl51test2. Each 2048 byte record requires 26 lines. The filename appears 1st, in this example 'gl/account.trans. The only items you might need to update are on the 1st 2 lines (+ 6 chars of the 3rd line). The rest is history.
   

 gl/account.trans_                                  gdg=18 opt=c next=000005(0000
 01:000012)000000:000000 JGL220             err4 070621:210051:G0_000003(000001:0
 00003)JGL220   S0010 cgl200err4 070621:210030:G0_000003(000001:000003)JGL220   S

2. 'gdg=18' is the number of generations to be maintained. 'opt=c' is the option for operator confirmation of gen# selection. 'next=...' is the option to process a series of existing prior generations.
   
   
3. Note 'next=000005(000001:000012)...'. This 'vi' snapshot was captured 4 runs after setting next=000001(000001:000012)...'
   
   
4. If you are very careful you might be able to update with vi. Use only the 'R'eplace command of vi, not insert or delete. Note that 'gdgload1' inserts a period '.' at col 2047 to indicate the end of the record. See the end-of-record '.' on the last of the 13 x 80 column lines required to show the 2048 byte record. You know the record has not shifted if the '.' is 1 column left of the 'S' on the line above.
   
   
5. When you rewrite the file, check that the file-size is a multiple of the record-size (256). Or use control-G in the editor to check before writing.
   
   
6. Updating the indexed file is only justified if you always run the 'dcheck' utility to validate & if you maintain the text file version.
   
   
7. If you do much updating with vi, you could periodically run 'gdgunload1' to convert the Indexed file back to the text file backup.
   
   
8. If need be you can recreate the text file by running jcldata56 (see '5C1').
   

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

5C9. MVS JCL conversion - GDG files

Alternate location for GDG control file

The location of the GDG control file is determined by the common_profile (stored at /home/appsadm/env/common_profile & called by .profile or .bash_profile). Here are lines 61-64 of $APPSADM/env/common_profile.

 export GDGCTL=$RUNDATA/ctl       #<-- default location
 # export GDGCTL=$APPSADM/ctl     #<-- could change to this ?
 #Mar14/12 - allow gdgctl51I.dat/.idx & GDGmkdirs to be located anywhere
 # - vs $RUNDATA/ctl, see doc at www.uvsoftware.ca/mvsjcl.htm#5C2

If you have multiple RUNDATA directories you might want to activate 'export GDGCTL=$APPSADM/ctl' & #comment out 'export GDGCTL=$RUNDATA/ctl' so you would have only 1 GDG control file vs multiple.

If you created the GDG control file as instructed on page '5C2', you could now copy the GDG control files to $APPSADM as follows (assuming you are in $RUNDATA).

 #1. cp ctl/gdgctl51* $APPSADM/ctl
     =============================
     - GDG control file created/edited on page '5C2'

 #2. cp ctl/GDGmkdirs $APPSADM/ctl
     =============================
     - script to make GDG subdirs in $RUNDATA/jobtmp/GDG
     - previously copied to $RUNDATA/ctl by copymvsctls on page '4D1'

'GDGmkdirs' is also copied to the alternate location, since it is called (in jobset51) using the same path ('$GDGCTL') as for the GDG control file. A sample GDGmkdirs was copied to $RUNDATA/ctl by script 'copymvsctls' on page '4D1'.

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

5D1. MVS JCL conversion - GDG files

GDG logic illustrated

This illustration will show you how we prevent incrementing the generation# on abnormal terminations. We will use the 'jgl100.ksh' JCL/script from pages '1E1' - '1E4'. Here we will show only lines relevant to GDG logic.

jgl100.ksh to illustrate GDG logic

 ##JGL100   JOB  (1234),'LIST GL MASTER CHART OF ACCOUNTS'
          - - - omitting lines Not Relevant to GDG logic - - -
 jobset51  # call function for JCL/script initialization             <--Note1,2,3
 #=======
            - - - omitting non relevant lines - - -

 exportgen0 0 ACCTMAS gl/account.master_                              <--Note4
 exportgen1 +1 ACTLIST $JGDG/gl/account.acntlist_                     <--Note5
 #exportgen1 GDG subdir/file, option g1 move to outdir at Normal EOJ
 logmsg2 "Executing--> cobrun $ANIM $RLX/cgl100"
 #3----------------------------------------------------------------------
 cobrun $ANIM $RLX/cgl100
 #4----------------------------------------------------------------------
 LCC=$?; S0010C=$LCC; ((SCC+=LCC)); ((JCC+=LCC)); S0010R=1; alias goto="";
 if ((S0010C != 0))                                                      <--Note6
    then logmsg2 "ERR: step#$JSTEP cgl100 abterm $SCC"
    alias goto="<<S9900=A"; fi
 goto
 #8======================================================================
 S9000=A                                                                 <--Note7
 jobend51 #move any GDG files from jobtmp/GDG/subdirs to RUNDATA/subdirs
 logmsg2 "JobEnd=Normal, StepsExecuted=$XSTEP, LastStep=$JSTEP"
 exit 0 #jclunix51 ver:20090313 b2c0d1g1e0f1i1j0k3l20m4n3o0p0r0s0t1u1w0x0y1z0
 #9======================================================================
 S9900=A                                                                 <--Note8
 logmsg2 "ERR: Terminated Abnormally,JCC=$JCC,StepsX/L=$XSTEP/$JSTEP" RV ACK
 jobabend51 #report GDGs NOT moved from jobtmp/GDG/subdirs to outdirs
 exit $JCC

Goto:   Begin this doc ,  End this doc ,  Index this doc ,  Contents this library ,  UVSI Home-Page

5D2. MVS JCL conversion - GDG files

Notes re jgl100.ksh above

1. 'jobset51' sets up jobtmp/JGL100/subdirs to hold any new GDG files until normal EOJ. See jobset51 listed on page '5K1'.
   
   
2. You must modify jobset51 to make subdirs required for your applications. Our supplied version sets up subdirs ar, gl, mstr,& tape (for our demos).
   
   
3. jobset51 performs 'cd $RUNDATA', so all files are defined in the script relative to $RUNDATA, which is /home/mvstest/testdata/... for the test/demos documented in MVSJCL.htm#Part_1.
   
   
4. exportgen0 defines the current generation for input. Assuming there are 3 generations in the file 000001,000002,000003, the result would be:
   

    export ACCTMAS=gl/account.master_000003
    =======================================

5. exportgen1 defines the next generation for output, effectively:
   

    exportgen1 +1 ACTLIST $JTMP/gl/account.acntlist_000004
    ======================================================
    #exportgen1 assign to $JTMP/subdir/file, move to subdir/file at Normal EOJ

6. Return code from the COBOL program is tested & control goes to S9900 on failure(non-zero) & S9000 on success(zero).
   
   
7. At S9000 (Normal EOJ), function 'jobend51' will move GDG files from jobtmp/subdirs back to $RUNDATA/subdirs. In this case from jobtmp/JGL100/GDG/gl/... to $RUNDATA/gl/...
   
   
8. At S9900 (Abnormal EOJ), jobset51 is not called, so any new GDG files are not moved back to $RUNDATA/subdirs. This means you can rerun the job without having to remove any new GDGs (so exportgen0 will get intended input).
   
   
9. Note that for a multi-step JCL/script, you might use the restart facility to restart at the step that failed. On a restart jobset51 will prompt you & copy any new GDG files back to $RUNDATA/subdirs.