Today, it is very common in mainframe shops to transfer data from mainframe to desktops. With the advent of powerful PC software, data is mostly extracted from the mainframe systems and manipulated on desktops. Also it is routine for developers/testers to share JCLs, PROCs, Programs, Program listings etc. Developers also print their program and program listings. Users have either used FTP or the numerous 3270 emulators to transfer data from mainframe to PC. MEMAIL is a powerful tool that sends mainframe data as an attachment file in Word, Excel or Notepad file to a valid email address or addresses. Users have saved enormous time and money from data extraction into various Microsoft Office products directly.

MEMAIL sends mainframe data as attachments to a valid email address/addresses to any email program. Normally it takes two to three minutes to get the email notification in your mail box. Attachments can be sent as Text files, Excel spread sheets or Word documents. You can send a complete file, part of a file (rows) and part or parts (Columns) of a record. You can send files from JES, ENDEVOR as well as SDSF. You can send the files from any environment in TSO, VIEW, EDIT, as well as through a batch job. Users have rated this tool as #1 time saver. The same command - MEMAIL - works in TSO as well as in EDIT/VIEW mode. This tool can be run interactively as a Question and Answer session too. Once an email address is given, the tool remembers it and recalls it every time the tool is used. The tool will not send the files to Email addresses beyond your organization. This tool can also send SMS messages and multiple files.

• A tool with many powerful features
• An enormous time saver
• A great productivity tool
• Send reports from mainframes to users as Word Document, Excel Spread Sheet or as Text file attachments as well as send an email notifications if a job abends
• A favorite tool with users
• Can be run interactively
• Batch JCL generated with exhaustive help through MGENJCL – another Makware tool

• Developers
• Testers
• Operators
• Analysts
• Users of corporate reports

Every day developers, testers and integrators have to create JCL’s needed for testing jobs modeled after production jobs. Often the production JCLs are huge and complicated with symbolic parameters and overrides present in the JCLs and PROCs. It takes a great effort and time, sometimes lasting for days, just to have a working set of test JCLs that are customized to the enterprise environment from the production JCL. Generally enterprises have no standards for creating such JCLs, resulting in more time and effort. If you have to test a series of jobs and more than one developer or a team is involved as generally is, as in Integration or system testing, you have to apply the same standards across otherwise you will spent more time on creating the right test JCLs than on testing them.

MJCL4TST is a very comprehensive panel based tool to customize Production JCLs to Test JCLs. It reads and expands the production JCL for PROCs. If overrides and symbolics are present in the production JCL or PROC. MJCL4TST will replace the symbolics with the values, inserts the right JOB cards needed for testing, inserts the appropriate test libraries before production libraries, expands PDS members and replaces these as in-line data, prefixes the production datasets with the user prefix (it has logic to truncate the dataset name, including GDGs, to the IBM JCL standards, converts Tape or CARTridges datasets to DASD, modifies to test DB2 system names, changes DB2 Plan cards for DB2 and IMS/DB2 programs appropriately, replaces the IMS databases to test ones, comments steps, if not needed during test runs like balancing steps, audit trails steps. During the creation of the test JCL, if the base for the customized GDGs is not present, this tool creates another JCL member with complete JCL to create the new GDGs If there are any datasets that are coming from another Job, another JCL member is created to copy such datasets to the customized datasets. For DB2 programs, it generates necessary BIND Cards as a separate PDS member.

• A tool with many powerful features
• Huge time saving utility for developers and testers
• A great productivity tool for testing in different test environments
• Customized and working set of Test JCLs in less than 30 minutes
• Flexible customization of JCL parameters through a panel
• Customized JCLs are consistent across users, jobs and projects.
• Consistent naming standards across enterprise
• A one-stop tool as all the necessary JCLs are created in a single execution of the tool
• Original JCL statements are shown as notes or comments
• Produces necessary JCL to create the new customized test GDG Bases if they don't exist
• Produces the required BIND Cards statements and JCL for DB2 programs.

• Developers
• Testers
• Integrators
• Analysts

IBM JCL in itself is a complex language to learn and master as it has numerous parameters and control statements. IBM utilities have their own set of control cards and manuals. Commonly used products like SORT, EASYTRIEVE PLUS, FILE-AID, ENDEVOR, IDCAMS and DB2 have their own set of rules and thick manuals. For a developer, it is indeed a daunting task to code and remember the control cards necessary to write a complete JCL. Many a times the developer has to refer to separate manuals for each product. This utility follows the 80-20 rule - 80% of the time a developer uses 20% of the features. Often while writing the code, the Corporate standards are not adhered while the tool generates the control statements as per the local standards.

MGENJCL generates JCL statements and the necessary control cards for various products with a detailed help and explanation of parameters in EDIT mode. Explanation of parameters is not saved to the file. All the JCL and Control statements are created according to the Corporate standards. You can get JOB, EXEC, LIBRARY, JOBLIB, DD etc JCL statements as well as Control Statements for every IBM Utility (like IEFBR14, IEBGENER etc ), and many popular utilities like SORT, COMPAREX, IDCAMS, DB2, IMS, DATAVAN, ENDEVOR, FILEAID, EASYTRIEVE etc. Comprehensive help is also provided when the statements are inserted in your edit mode. If you have specified a destination (i.e. A or B Command in EDIT), the utility will insert the cards after/before the destination. Control statements for other program products that are not present in MGENJCL can be added very easily along with the explanation of parameters. MGENJCL also generates all the necessary statements and the JCL needed for Makware tools that can be run in batch mode.

• One simple command in EDIT mode to create the necessary JCL and control statements for many commonly used products.
• Consistent JCL standards adhering to Corporate standards across.
• A great productivity tool for testing in different test environments
• Very easy and simple to use and extremely powerful
• Have a running JCL in no time Daily usage
• An enormous time saver and a great productivity tool
• Developers and Testers love this tool!

• Developers
• Testers
• Integrators
• Analysts

Developers often are scanning Libraries for Strings for due diligence, impact analysis and to research. Even though MVS has an option for searching strings, it has limitations. There is more than one panel to input. You cannot have a range of columns to search for each string. Also you cannot issue sophisticated search operands like OR, AND and NOT. The output of the search cannot be used directly into any desktop application.

MSCANSTR is a powerful one-panel application to scan for multiple strings across multiple Libraries. You can issue strings with search operands like OR, AND and NOT. Example your search string can be (CHEESE & CHEDDAR & \LIGHT) to search for strings that have both CHEDDAR and CHEESE but do not have LIGHT in the same row.) You can search across multiple libraries with Pattern. If a member is found in multiple patterns, only the first occurrences is searched. You can output those members that DO NOT have the search strings to a separate dataset. Users can see the progress of your search on the panel. When a record meets the search criteria, a record is written with Library name, member name, Line# where the occurrence is found and the data itself. For those members that DO NOT have the search string, only the Library name and the member name is written. After the successful search, you will be put in VIEW mode. While VIEWing, the dataset can be emailed as a text attachment. If you want the dataset to be emailed as an Microsoft’s EXCEL spreadsheet attachment, necessary instructions are displayed while viewing the dataset. You can also list just member names and stop if certain number of members have been found.

• Simple to use
• Sophisticated search capabilities
• Search Multiple libraries with or without patterns
• Get both found and not found members list
• Email as attachments - as text or as Excel spreadsheet
• An enormous time saver and a great productivity tool
• Can be run in Batch too!

• Developers
• Testers
• Analysts

In every installation, various elements needed for development and maintenance of applications are scattered across various libraries. Developers constantly access JCLs, EXECs, PROCedures, PROGRAMs, Program listings, Parameters, INCLUDES, COPYBOOKS and datasets every day. It becomes more complicated and time consuming should these elements be stored in propriety programs like ENDEVOR, PANAVALET etc. During development, maintenance, and testing, Developers, Analyst and Testers are always navigating from one panel to another and from one dataset to another to see / edit the contents of datasets.

MV is a hyperlink utility that allows the developers/testers to view datasets, PDS members, Libraries, Listings etc in EDIT or in TSO mode with a single command. In TSO mode, just give the member name to scan all the appropriate libraries and view the member. You can give a dataset name to bring the dataset in View/Browse mode. In EDIT/VIEW mode the tool depending upon the source code performs a different action. If you are EDIT/VIEWing a COBOL source, place the cursor anywhere on a line that has INCLUDE or COPY to expand it. The expanded INCLUDE/COPY is inserted in the source that you are viewing as Messages. A RESET command will clear this. If you are in VIEW/EDIT mode for a JCL member, place cursor on a line with PROC statement to see the PROC as comments inserted right after the PROC Statement. If you place your cursor on a PDS member, the PDS member is expanded and the statements are inserted as messages in the source that you are editing / viewing. If you have placed the cursor on a dataset, you will be placed on a BROWSE/VIEW mode for that dataset.

• One command across TSO and ISPF EDIT/VIEW to see the contents of elements
• Very easy and simple to use and extremely powerful
• Any number of MV sessions can be active. ( Ex Display the compilation listing in one ISPF panel and make corrections to the source in another.)
• Daily usage
• A favorite tool with users
• An enormous time saver
• A great productivity tool

• Developers
• Testers
• Operators
• Analysts

Often IT projects are delivered late. Resources are acute. Writing new programs is expensive and time-consuming. Frequently when the business needs data/reports, IT cannot deliver these in time. The perception that IT cannot respond in a timely manner persists in every organization.

MSELECT is a powerful yet easy to use utility that has features which are not available even in the most sophisticated packages available today. Some of the functions present in this utility can only be written using COBOL or similar languages. You can issue simple to sophisticated queries, reformat the results, view the results on a screen or get them in a dataset, convert from one format to another, do date manipulation and queries, split the output to as many lines as you want, and print a file. While reformatting, you can realign the data or split the data. You can run this exec in MVS, VM or DOS environments.

• Define fields and generate new records with stripping fields of spaces, zeroes and delimit by a special character ( You need a program to do this!)
• Implode raw data with a Delimiter Character to new record
• Explode and reformat records that have fields delimited by a special character ( You need a program to do this). Implode raw data with a Delimiter Character
• Extract records with sophisticated queries – extract those that satisfy the query or those that do not satisfy the query
• Extract the data to a different layout
• Extract, split, reformat data to multiple lines
• Insert Constants, Hexadecimal values and results of Rexx functions applied on fields
• Translate values
• Check whether fields are numeric and/or hexadecimal
• Convert from Binary, Packed Decimal (Both zoned and non-zoned) to Numbers
• Convert from Character to Hexadecimal
• Convert from Numbers to Binary and Packed Decimal (Both zoned and non-zoned)
• Convert date to multi formats
• Calculate difference between Dates and do arithmetic operations on Dates.
• Apply all the extremely sophisticated functionality of REXX functions
• Left justify fields and auto fill with any character, Right justify fields and auto fill with any character, Center or Strip the fields of leading and trailing spaces or any other character.
• Convert from ASCII to EBCDIC and vice-versa
• Create test files from raw data – even if raw data is delimited by a special character
• Translate numbers to words in English
• Apply your own Rexx routines to defined fields.

• A very powerful and yet simple to use tool.
• Very useful during development and testing phase.
• A job which takes days can be done in hours.
• Extract data in Excel format and use MEMAIL to send the report to any user
• Extract data and format to XML
• Convert data, change SSN to a dummy number, convert numbers to text etc
• Extract data and create SQL
• Too much functionality to specify
• Can be run interactively
• MVS Batch JCL with exhaustive help generated through MGENJCL – another

• Developers
• Testers
• Operators
• Analysts
• IT & Non-IT users.

It is very common practice in mainframe shops to manipulate PDS members and Libraries. Standard installation libraries are often added new, or changed or removed due to new release. Sometimes the installation standards for coding also change. During migration and conversion of applications, global changes need to be made. When a product is replaced or the installation moves to a new version, to make changes across all the members of libraries is a tedious process. Developers are always manipulating the library members. Also if you have to copy libraries from one site to another, or copy one users library to others, this tool comes extremely handy.

MPCKUNPK will pack a PDS/Library to a flat file, if the input file is a PDS/Library and unpack a packed file to a PDS/Library, if the file is already packed through this utility. Once held as a flat file, you can edit the dataset to manipulate the data. You can make global changes as well as add new lines, modify existing lines and, delete lines within a member, because each PDS member is identified with its own header record. You can manipulate this header too. You can change the member names, and statistics details, delete entire contents of a member, or insert data for new members. After modifications within this file, you can restore the flat file to an existing PDS or to a new one, restore or reset ISPF statistics if you want to.

• A great tool for migration as well as conversion projects.
• If you have to make changes across libraries, 'feel' the changes before you apply.
• Very easy to use.
• Quick and fast
• Saves time drastically.
• Great productivity tool

• Developers
• Testers

Developers, testers, integrators are always working with a set of datasets during a project / projects. Developers typically create programs, edit and compile them and run test JCLs. Depending upon the setup, compilations steps vary. If there are third party packages like PANAVALET or ENDEVOR used, there are separate steps to extract and load back source. Once the source is successfully compiled, they submit test JCLs. They view the datasets that were created or input to the program. Testers do similar things except for compilation. They submit jobs for execution and validate results. Frequently JCLs, programs, datasets, results are sent to other team members.

MTOPTEN is a one-stop panel based application that remembers your last 10 datasets that you have used. The datasets can be flat files or PDS members. You can Email, Edit, view Details, Submit JCL to TSO ( you are prompted to accept or reject SUBMIT in case MTOPTEN finds a RESTART in the JCL), Browse data sets, extract, retrieve elements from libraries, Generate compilations (through ENDEVOR or other program products), Print, Copy, Move, and Rename them. The most current used dataset is always the first dataset in the panel. You can override the name of any dataset in the panel by over typing. There is an entry for eleventh dataset that will not be stored.
Users can have the list of most used (ten) dataset names stored in files and recall any list depending on their needs. Also the users can save the working list onto a new file.

• A tool with many powerful features on a single Panel
• Quick and fast
• Remembers your most frequently used datasets in order.
• No need to move from one panel to another in ISPF.
• Great productivity tool
• Huge Time saver

• Developers
• Testers
• Operators
• Analysts
• Corporate Users who execute their own jobs to get reports

Today's Mainframe users analyze data and produce information using the powerful desktop tools available to them. They need to receive the Mainframe data in a format that is compatible with their desktop tools. The dynamic query tools that are commonly available to extract data from and modify data into DB2 tables are expensive, cumbersome to use and are limited in functionality. For example, the ability to extract the data and email the results in text or excel format to an email address is limited in these tools. There are a number of limitations to use these products; for example, if the report produced by one such tool is beyond the normal report length, the data is split in parts, making it extremely difficult to read the report. In another example, while generating SQL statements in edit, column names are separated by a coma and are grouped together in a line. It is rare that all the columns are used in one query. For more than one table, column names from different tables are grouped together. If the columns names present across tables have same name, you have to add a prefix manually to each column name

MASKDB2 offers powerful functionality that overcomes the deficiencies of many tools that are available to query DB2 databases.

Query Results can be generated in many ways:

• To exact length
• To best fit
• Strip column results for unwanted trailing spaces and delimit by a special character (can be exported directly to desktop applications)
• With column titles or without column titles, and
• In XML format

The MDRAW command can be used in any ISPF/EDIT session to get the SQL statements against DB2 tables required for other development needs. If a Query returns a nonzero return code, displays a separate panel with comprehensive help about the return code.(QMF just shows the return code; leaving the users to research what it means) The tool stores a complete history of the queries used; allows storing up to 80 characters of comments / notes against a query. During testing, the same query is tested repeatedly. The tool stores and recalls all the input fields like input query name, output name, options, email addresses etc.Only one panel to process which is very easy to use. Access any authorized DB2 system from this panel. Pressing PF1 provides comprehensive help.

• Users have saved at least three hours per report by using the Excel file email feature alone
• A very powerful and yet simple to use tool to access DB2 tables
• A big time saver
• Incredibly useful during development and testing.
• Can replace many expensive tools

• Developers
• Testers
• Analysts
• Corporate Users who run Ad-Hoc Queries to generate reports

On projects, often developers have to compare a series of elements in various Development environments with Production Versions. A large number of Corporations have Software Management Products like ENDEVOR or PANAVAETs. Developers spend considerable time and efforts to generate the necessary JCLs. On projects, the number of elements sometime exceed 100. Making changes to the JCLs thus becomes a time-consuming process. This Utility presents a menu and you have to enter the Element Name, Environment Name, System Name, Subsystem Name, Type, and Stage Num against the two elements that you want to compare. The panel is filled with a number of default values. If the names (like Element Name, System and subsystem Name ) are same in both the elements, you can leave the fields in Elements#2 blank.

MCOMPARE is a single panel Utility which presents a menu and the developer has to enter the various element details to be compared in any two different environments – like PRODUCTION, ACCEPTANCE, TEST etc The panel is filled with a number of default values. If the names of various element parameters are same in both the environments, you can leave the fields in the right side of elements to be blank. The tool validates the input data entered by the user and submit s a batch job generating the necessary JCL and statements for various Software Management products. Finally the compare results are emailed to the Developer as a Text attachment or as a Word document. You can also compare different columns in same position in both the files or different columns in different positions.

• A Big time saver for Developers and Analysts for Code Compares.
• A great productivity tool for Developers
• Very easy to use
• Compare results are Emailed to the Developer
• A favorite tool of users.

• Developers
• Testers

Developers often need to copy a small subset of production data to test. Sometimes they need to copy a portion of data that meets their business requirements. Sometimes they have to copy the records and edit the dataset for their requirements. They need quick tools to copy as they do not want to submit batch jobs and wait for the completion of the job.

MQWKCOPY will copy and if needed reformat the input data from a dataset either in MVS Batch or TSO ISPF with sophisticated functionality. The easiest way to use this tool is to be in ISPF option 3.4 and type MQWKCOPY and overtype parameters on the file name.

Users can copy records :-

• Stopping after certain count limit has reached
• Starting from when a string or a series of strings are found anywhere in the record or at specific locations
• Stopping when another string or a series of strings are found anywhere in the record or at specific locations
• Only those that have the string or a series of strings are found anywhere in the record or at specific locations
• Copy after skipping certain counts of string or a series of strings found anywhere in the record or at specific locations
• Copy records from end - Example last 10 records
• Reformat records while writing out.

You can copy to a new dataset or you can prefix the current dataset name if in ISPF option 3.4. The utility will generate the output dataset name according to IBM standards.

• Very easy to use.
• Quick and fast
• Saves time
• Great productivity tool
• Can be used in MVS batch, interactively or by typing over a dataset name in TSO option 3.4
• One of the favorite tools of developers
• Batch JCL generated with exhaustive help.through MGENJCL – another Makware tool

• Developers
• Testers
• Analysts

Often there are occasions when developers and testers need to match two files based on keys and need either matched or non-match records. If the input files have multiple sort keys or multiple records with same keys, the process of comparing keys to determine whether they match or non-match between two input files becomes extremely complex. Many a times, a new program has to be written to meet the requirements.

MCOLLATE matches two files on multiple sorted keys to create a third file. The sorted input files can have ascending or descending sort keys and both files can have multiple records with the same keys. MCOLLATE checks for the sorting order while comparing keys and if the files are not in the correct sort order, displays the key and the record# and abends the tools

There are five options available:-

• Match File#1 & File#2 records on keys, and Write File#1 records onto a third file
• Match File#1 & File#2 records on keys, and Write File#1 and File#2 records onto a third file
• Match File#1 & File#2 records on keys, and write Non-Match records of File#1 only to a third file
• Match File#1 & File#2 records on keys, and write Non-Match records of File#1 and File#2 to a third file
• Merge File#1 & File#2 records on keys, and Write to a third file.

You can copy to a new dataset or you can prefix the current dataset name if in ISPF option 3.4. The utility will generate the output dataset name according to IBM standards.

• A very powerful and yet simple to use tool.
• Very useful during development and testing.
• A great productivity tool and a big time saver
• Developers dream tool
• No need to write new programs - eliminates the efforts needed for the development cycle.
• Can be run interactively as a Question and Answer session or in a batch mode
• Batch JCL generated with exhaustive help.through MGENJCL – another Makware tool

• Developers
• Testers
• Analysts

It is a very common practice in mainframe projects to match and merge data from two files. Sometimes data is in a master file and the transaction files need to have information from the master. Also the developers/testers need to match two files and need data from both the files. The logic gets complicated when the data to be matched is on multiple sort keys.

MSWAP matches two files on multiple sorted keys and copies/overlays data from one file onto another to create a new file. Data can be moved from one file from any position to another file on any position – even beyond the logical record length of files. You can move the same data from one file to multiple positions/locations in a record to create a new record. If the files have keys, you can superimpose data on the keys itself. There are two options available.

• Match File#1 & File#2 on keys, COPY/OVERLAY fields from File#2 To File#1. Write only matched File#1 records. You have two options while copying. Either you can copy the whole File#1 Record or you can define fields from both files and write these fields (you can insert Constants, Text, Hexadecimal Values) to form a new record.
• Match File#1 & File#2 on keys, COPY/OVERLAY fields from File#2 To File#1. Write ALL File#1 Records. You have two options while copying. Either you can copy the whole File#1 Record or you can define fields from both files and write these fields (you can insert Constants, Text, Hexadecimal Values) to form a new record. For those records that do not have a corresponding match, you can insert default values.

• Data from File#2 is moved to File#1 on a one-to-one basis to create a third file. If File#1 has more records than File#2, excess records in File#1 are copied as they stand. If File#2 has more records than File#1, excess records in File#2 are ignored. You can choose either of the files to be File#1.

• Avoids writing of Program and related efforts
• A very powerful and yet simple to use tool.
• Very useful during development and testing.
• A great productivity tool and a big time saver
• Can be run interactively as a Question and Answer session or in a batch mode
• Batch JCL generated with exhaustive help.through MGENJCL – another Makware tool

• Developers
• Testers
• Analysts

In CICS, the screens also known as Maps are generated by coding BMS Macros. These macros are written using IBM’s Assembler coding standards. To generate a BMS Map, you have to code BMS macros first following the IBM assembler language standards and compile them successfully to see how the screen looks like. You should be familiar with IBM’s Assembler language and know the right Macros and their parameters to assemble. Often, after seeing the image of the screen, you have to correct the BMS Macros until you get the right screen.

MCICSBMS generates BMS Macros from a screen image. A job that normally takes days can be finished in hours. This program does reverse engineering. With this program, you paint the screen first with field names and titles and call this utility to get your BMS Macros. A simple BMS screen takes days to complete correctly but with this utility you can finish even complex BMS maps in less than half a day. The utility incorporates different BMS rules. Thus developers with no or little knowledge of CICS BMS Maps can code the BMS. A very comprehensive help is provided during development. The utility takes care of all the rules of CICS BMS.

This utility can further be tailored to allow for automatic compile of maps and can be customized to generate Cobol copybooks where the installation doesn't need the COPYLIBS generated by CICS.

• Big Time saver for CICS BMS Development
• Provides a comprehensive help.
• Shows you how to paint the screen
• Great tool for standardization of code as the generated code across different BMS maps is similar (otherwise each developer has a different style and maintenance is a big nightmare.)
• No or little knowledge of CICS BMS Mapping

• CICS Developers

In IMS/DC, to generate a Screen using MFS, Developer need to know the extremely complex and confusing MFS coding rules – a daunting task. To have a working screen, developers spend days. Often, after seeing the image of the screen in IMS/DC regions, developers have to correct the DIF/DOF and MID/MOD macros and regenerate the screen until they get it right. The toughest task, thus, in coding the MFS is coding the MID/MOD, DIF/DOF and creating COBOL copybooks. It is very difficult to remember the MFS coding rules. Even after developers have coded the MID/MOD and DIF/DOF, only after generation will they be able to see the screen.

MGENMFS generates DIF/DOF, MID/MOD and COBOL copy book from a screen image. A job that normally takes days (often 7 to 10) can be finished in hours. This program does reverse engineering. With this program, Developer paint the screen first with field names and titles and call this utility to get Developer DIF/DOF, MID/MOD and COBOL copy books. A simple MFS screen takes days to be completed correctly but with this utility Developers can finish even complex MFS screens in fraction of time that they would have spent normally. The utility incorporates different MFS rules. Thus developers with no knowledge of IMS/DC can code the MFS. A very comprehensive help is provided during development. The utility takes care of all the rules of MFS.

• Big Time saver for IMS/DC Developers
• Provides a comprehensive help.
• Shows you Developers how to paint the screen
• Great tool for standardization of code as the generated code across different MFSs is similar (Otherwise every programmer has a different style and maintenance is a big nightmare.)
• Generates COBOL copybook – another huge time saver
• No or little knowledge of IMS/DC
• Even dummies can code a MFS!

• IMS/DC/DB Developers

COBOL programs are written very often in mainframe shops. With coding standards hard to find, developers code the programs as per their style or copy an existing program with many an unwanted data. In today’s environment, organizations need to develop COBOL programs quickly, accurately and to the Company’s standard with standard routines to handle errors.

MCBLXPRS generates a complete COBOL program by reading a file which has the Input and Output file names defined. (You can also have VSAM files in this file.) The installations standards are stored and the generated code adheres to the standards. The IDENTIFICATION DIVISION, ENVIRONMENT DIVISION, DATA DIVISION including WORKING-STORAGE SECTIONS are populated appropriately. In the PROCEDURE DIVISION, except for the processing logic, all the relevant logic to open, close and to read files is added. Appropriate statements needed for VSAM files processing are inserted. The tool can handle all the three types of VSAM files and access methods. Errors are handled appropriately. End of Job messages are displayed at the end of the program.

• An enormous time saver. Generates code according to the Company standards.- Quick and fast
• Great tool for standardization of code as the generated code across different programs is similar (Otherwise every programmer has a different style and maintenance is a big nightmare.)
• A great tool to generate standard COBOL programs. No need to know how to code to access VSAM files.
• Great tool for standardization of code as the generated code across different MFSs is similar (Otherwise every programmer has a different style and maintenance is a big nightmare.)
• Great productivity tool for migration and conversion projects

• COBOL Developers
• Programmers

With the removal of TRACE functionality from the COBOL compiler, developers have lost an important functionality for debugging their COBOL programs. Often the developers want to see the flow of the program. TRACE command within the COBOL programs provided that functionality. Now the developers have to code 'DISPLAY' Paragraph Name after every paragraph in their COBOL programs to trace the flow of the program. Sometimes the programs are so huge that it takes hours to add these comments. Also if the developer wants to see the value of a variable they have to add another DISPLAY statement.

MCBLTRAC inserts the DISPLAY Paragraph Name after every paragraph if the DISPLAY paragraph Name statement is not present in the COBOL program that the developer is editing. It can also add variable names so that the developer can see the contents of the variable at the beginning of each paragraph in the COBOL Program.
It removes all the DISPLAY paragraph statements from the COBOL Program if these statements are present within the program.

• An enormous time saver
• Quick and fast
• One command to insert and remove debugging statements.
• Developers love this tool.

• Developers

During migration and conversion projects as well as multi-application projects across corporate applications, analysis is carried on Datasets to find where they are created and used. This type of research is extremely common in any enterprise. In order to do influence analysis, often the production JCL’s are scanned to retrieve DD names. This task is huge and complicated more so if there are symbolic parameters and overrides are present in the JCL’s, PROCs. IMS, and DB2 program names are hidden in various places. An IMS program name is present in the PARM card of the JCL that is executing the IMS driver program. DB2 programs are defined in the SYSTSIN datasets while IMS/DB2 program is hidden in the DDITV02 dataset. Developers/Analysts spend considerable time to extract the information that they need.

MANLYZDD is a single panel application tool that extracts the necessary information based on the production JCL name pattern. It will extract the production JCL members from the pattern entered in the panel. It will then expand the Production JCL by exploding the PROCs and will replace all the symbolics and overrides with the values present in the PROC or JCL before extracting the data needed for analysis. The tool ignores temporary (&&DSN) datasets, Libraries and System datasets. For IMS programs, it extracts the program name and PSB name from the PARM card present in the exploded JCL. Similarly for DB2 programs, it expands the SYSTSIN DD dataset and extracts the program name, and DB2 PLAN name and for IMS-DB2 programs it expands the DDITV02 DD dataset and extracts the program name from the exploded JCL. Finally the tool writes the result to a dataset with the following details for each DD:-

• Step Name
• Seq# of DD within JCL Name ( If you sort the file on DD name and this Seq#, you should be able to see the flow of the file)
• DD Name
• Initial Disposition
• Final Disposition
• Program Name
• Program is IMS one or Not
• Program uses DB2 or not
• PSB Name
• Plan Name

After extraction of the data for analysis, the tool will put the developer in a VIEW mode to see the results. If developer wants to e-mail this dataset as an attachment to a valid e-mail address to do further analysis using any desktop applications, appropriate help is provided while in VIEW mode. Example: If the developer wants this dataset as an excel spread sheet using MEMAIL tool, then he/she makes the line which has --------+ as data line by issuing MD line command against this line and then issues on command line.

• A big time saver for Developers and Analysts while doing analysis regarding JCL step overrides and program names associated with datasets.
• Impact analysis on JCLs and PROCs can be completed quickly
• A great productivity tool for application analysis
• Very easy to use

• Developers
• Analysts

There are occasions when to do impact analysis during migration projects, conversion projects or for replacing applications , developers and analysts want to know the complete statements issued against IMS databases, DB2 tables, within CICS or against MQ series. Each developer has a different standard for coding these statements. Many a times, developers would have introduced comments within these statements. It is extremely difficult, laborious, and time-consuming to gather such data. There are no tools that can list such statements. Most of the time, developers have to go program by program to extract the needed data.

MEXECALL will scan an entire library either fully or selectively or a sequential file for all DLI, DB2/SQL, MQ and/or CICS calls in COBOL Programs. Every call is then listed onto a new output file. For DLI and MQ series calls, it will list all the parameters that were passed via the CALL statement along with the CALL statement and for DB2/SQL and CICS statements, it will list all the lines within EXEC and END-EXEC statements. The program name is listed in Column 1-8

You can scan for all the statements for DL/I, DB2/SQL, CICS or MQ series or choose the ones that you need.

• An enormous time saver
• Quick and fast
• Great productivity tool for Analysis during migration and conversion projects
• Easy to use

• Developers
• Analysts

Developers and testers need Production JCLs for their day to day jobs. They need to expand these JCLs. Productions JCLs have many PROCs. Each PROC can have its own symbolics and overrides. Adding to this complexity, there may be override DDs prsent in the JCL. It is an extremely complex process to expand such JCLs as there may be overrides both in the PROC as well as JCL. There are not many tools that can expand such JCLs which have PROCs with overrides and substitute symbolics.

MXPNDJCL expands the JCLs from Production Libraries. It expands each PROC present in the JCL by substituting the symbolics and overrides present in JCL statements first from PROC and then from JCL. It then substitute override DDs, if present. It applies this process of substitution to every PROC that is present in the JCL. The output of the expanded JCL is written to a new dataset.

• Expanding JCL which have PROCs with overrides and symbolics is extremely tedious process. This tool makes it easy and simple to expand such jobs.
• Very useful in migration and conversion of applications.
• A powerful and yet simple to use tool.
• Very helpful during development and testing.
• A job which takes days can be done in hours.

• Developers
• Analysts
• Testers