Non-Relational Data Access Methods, Processing & SORT

Introduction

The Non-Relational Data Connection provides a suite of sample programs and reference documentation for managing VSAM Data Sets or flat, sequential files (QSAM). Processing principles and techniques that may be used to create, delete, update, edit, convert or compare are included for both VSAM Data Sets, QSAM Sequential Files or Directory Structures.

The examples are written to run as batch jobs on an IBM Mainframe System running ZOS. Also, the examples will run as batch jobs on a Windows System with Micro Focus Enterprise Server/Developer. If a technique is used that is unique to the Mainframe or Micro Focus it will be noted.

We have made a significant effort to ensure the documents and software technologies are correct and accurate. We reserve the right to make changes without notice at any time. The function delivered in this version is based upon the enhancement requests from a specific group of users. The intent is to provide changes as the need arises and in a timeframe that is dependent upon the availability of resources.

Copyright © 1987-2025
SimoTime Technologies and Services
All Rights Reserved

Non-Relational Data, What is Available

SimoTime provides a variety of technology and services offerings for migrating business applications and/or data structures between systems of differing architectures. The business applications are typically batch or online. The data structures include both relational and non-relational.

A major part of our services business is working with non-relational data structure for conversion and validation (including data file compares). We have experience with converting VSAM Data Sets with complex, EBCDIC-encoded record structures that contain packed and binary data into ASCII-encoded record structures that maintain the numeric integrity of the packed and binary fields and are processed on a Window, UNIX or Linux System using Micro Focus Enterprise Server.

For additional information about SimoTime Services or Technologies please call or send an e-mail to: helpdesk@simotime.com or 415 883-6565. We appreciate hearing from you.

File Types or Data Structures

In today's environments there are many types of non-relational data structures being used on a variety of hardware platforms that are managed by uniquely architected operating systems. In this document we will focus on the data structures used on an IBM Mainframe with ZOS and Linux, UNIX or Windows (LUW) Systems with Micro Focus Enterprise Server/Developer.

The following link describes the non-relational data structures supported by Micro Focus Enterprise Server. Many of the file structures and VSAM data sets will also apply to the Mainframe System environment.

    Explore the File Formats and various Numeric Formats being used in a multi-system complex consisting of Mainframe (z/OS), Linux, UNIX or Windows systems.

Data Access Methods

Non-relational data structures may be processed using a vendor-supplied utility program or a user-written program. For the Mainframe System an example of utility programs that process non-relational data structures would be IDCAMS, IEBGENER, DFSORT and more. For a Windows, Linux or UNIX system using Micro Focus an example of utility programs that process non-relational data structures would be MFCAMS, MFJGENER, MFSORT and more.

User programs that process non-relational data structures were typically written using programming languages such as COBOL, Assembler (HLASM) and PL/I.

The non-relational data structures are typically processed using a sequential or random access methodology. The sequential methodology may be "Sequential-by-Record" or "Sequential-by-Key" (the key may be the primary index or an alternate index).

The random methodology may be "Random-by-Relative-Record" or "Random-by-Key" (the key may be the primary index or an alternate index).

Data Management & Support

The following sub-sections will focus on some of the functional requirements for managing and supporting non-relational data structures in a development, test and production environment.

Data File Transfer

The data file transfer process should be a repeatable process with an audit or validation trail. The process should be executable as an automated, unattended process.

    Explore the alternatives for transferring data files between systems. This link provides access to a repository of information that includes the transferring and/or sharing of data between Mainframe (ZOS or VSE), Linux, UNIX and Windows Systems.

Data File Convert

Ever since the second computer architecture was introduced the task of data conversion in preparation for data migration and data sharing has been a never-ending process. Data conversions may be driven by business requirements or system requirements such as changes in system architectures.

    Explore the Principles of Data File Conversion. This link includes guidelines for defining requirements and determining the scope of effort for a data conversion effort.

    Explore How to Generate a Data File Convert Program using simple specification statements in a Process Control File (PCF). This link to the User Guide includes the information necessary to create a Process Control File and generate the COBOL programs that will do the actual data file conversion. The User Guide contains a list of the PCF statements that are used for the data file convert process.

The following discussion will divide the data file conversion tasks into three (3) categories.

File Format Conversion

File format conversion varies widely across Mainframes, Wintel, UNIX and Linux systems. The least common denominator for file formats is a record sequential file of fixed length records. It is a common practice to take a proprietary file format on one system and copy it to a record sequential file. The record sequential file is then transferred to the target platform (usually FTP in binary mode) and used as the base to create a new file in a format that is native to the receiving system.

Record Content Conversion

Record content conversion may present a bigger challenge. It is the exception when a file on a mainframe contains records that are all text and may be converted between EBCDIC and ASCII as a single string. The reality is that records in mainframe files contain a mix of text strings and numeric fields that may be signed or un-signed, zoned-decimal, packed-decimal, binary or floating point formats. Therefore, the record content conversion must be done at the field level.

Extract by Field, Fixed Field-Length to CSV

The extract of data by fields within the record and the reformatting of the output records is actually accomplished with two COBOL programs that are generated using SimoTime Technologies. The first program does the File I/O of reading the data file and writing reformatted records to a sequential file. The File I/O program calls the second program to do the record formatting that expands the numeric fields (converts packed-decimal format to display-text format) and does blank truncation on the text fields and then places a comma between the fields as the field delimiter.

    Explore How to Convert a Fixed-Field-Length Record Structure to a Comma-Separated-Values Record Structure.  This technique is used to extract data from a VSAM, Key-Sequenced-Data-Set (KSDS) with a record structure that uses fixed-length fields. The new CSV format may be easily loaded into an Excel spread sheet.

Import by Field, CSV to Fixed Field-Length

The import of data by fields within the record and the reformatting of the output records is actually accomplished with two COBOL programs that are generated using SimoTime Technologies. The first program does the File I/O of reading the data file and writing reformatted records to a VSAM, KSDS. The File I/O program calls the second program to do the record formatting that converts the numeric fields (converts display-text format to packed-decimal format) and expands the text fields to a predefined fixed length.

    Explore How to Convert a Comma-Separated-Values Record Structure to a Fixed-Field-Length Record Structure.  This technique may be used to import data into a VSAM, Key-Sequenced-Data-Set (KSDS) with a record structure that uses fixed-length fields. The CSV format may be accessed by Microsoft Excel or loaded into a relational data base.

Data Validation

Quite often the Data Validation requirements go beyond a simple file compare. Additional processes (or checkpoints) will need to be put in place to meet the concerns of management and auditors.

When business data is stored in non-relational data structures the physical structures are usually a combination of VSAM Data Sets and traditional sequential files containing records of fixed or variable length. The records are typically concatenated strings of data referred to as fields. A field may contain text strings, binary values (hexadecimal characters or numeric values) or special numeric formats (such a Packed-Decimal or COMP-3). The text strings may be EBCDIC or ASCII encoded.

An extra effort or secondary check becomes a requirement for numeric fields that contain currency values.

    Explore Data Validation Techniques that are used with non-relational data structures such as sequential files and VSAM Data Sets. The techniques include using a text editor to view the hex-dump format of records, compare records in two files or accumulate summary totals and record counts.

Compare Content of Two Data Files

Reviewing the results obtained during a regression test that follows a system, application or programming change is one of the factors that drive a requirement for comparing data files. The scope of this effort is dependent of the type (or format) of file being compared and the complexity of the record structure within the file. Comparing the files is only half of the effort. What to do once an error (or non-equal) condition occurs can be a significant part of the effort.

    Explore the Principles of Data File Validation. This link includes guidelines for defining requirements and determining the scope of effort for a data validation effort. This effort includes a data file compare process, a technique for accumulating summary totals with a record count and a technique for reading a VSAM, KSDS and producing a hex-dump output based on a list of user-defined keys.

    Explore How to Generate a Data File Compare, Validate or Hex-Dump Program using simple specification statements in a Process Control File (PCF). This link to the User Guide includes the information necessary to create a Process Control File and generate the COBOL programs that will do a data file compare, accumulate summary totals with a record count or produce a Hex-Dump of records in a VSAM, KSDS based on a list of user-defined keys. The User Guide contains a list of the PCF statements that are used for the data file compare, validate or dump process.

Compare Content of Two Directory Structures

This document describes a process that will compare the content of two (2) directory structures and their associated sub-directories. The methodology will create a directory listing for each of the directory structures. The listing files are then reformatted and sorted prior the compare and tracking of added or deleted members within the directory structures.

    Explore a Directory Structure Compare Utility Program that is used to compare the content of two directory structures.

Summary Totals & Record Counts

It may be a requirement to accumulate batch totals for numeric fields and this may be especially true for currency fields. The SimoTime technology allows a user to leverage various approaches for this requirement.

    Explore how to accumulate Summary Totals and Record Counts by reading a sequential file or VSAM Data Set. This suite of programs and documentation will describe and demonstrate an approach for reading a file, calculating record counts and producing summary totals for a set of pre-defined numeric fields. This technology has the capability of managing non-numeric values in numeric fields.

Hex-Dump with Record Selection

This generated program will create a Hexadecimal dump file (or HEXDUMP) of user-defined records in the Customer Master VSAM, Key Sequenced Data Set (KSDS). The CUDUMP01 program will compile and execute on a Linux, UNIX or Windows System with Micro Focus Enterprise Developer/Server, version 2.2 or later. The CUDUMP01 program should compile and execute on a ZOS Mainframe System. The JOB statement and the data set names (DSN's) will need to be changed to comply with security and naming standards on the host mainframe system.

    Explore How to Create Hexadecimal Dump information for the records in a Customer Master file. The Customer Master file is a VSAM, KSDS. This document describes a process for generating a COBOL program that will read a VSAM/KSDS and write hexadecimal dump information to a sequential file. The user may define the records to be dumped by providing a list of primary keys in a control file. A second COBOL program is called to write the HEX-Dump information to a sequential file that contains variable length records.

Non-Relational Data, How to Manage

This section will focus on the data management tasks that do Data file Conversion, comparison and validation.

Data Management & Support

The following sub-sections will provide an overview with information for configuring a user system to meet the functional requirements for managing and supporting non-relational data structures in a development, test and production environment.

Overview for Managing non-Relation Data Structures

The following link will provide an overview of the technology and processes available for managing non-Relational Data Structures.

    Explore How to use a group of Job Scripts, Programs and Control Files that are used for sharing, converting, comparing and reviewing data structures such as non-relational data files and VSAM Data Sets.

Configure a User Environment

The following link will provide a description of a user environment that is used to manage non-relational data structures in a mixed, multi-system environment.

    Explore the SIMOUSER directory structure. The SIMOUSER Library is a directory and sub-directory structure that provides an environment for analyst, technical administrators, testing groups and support individuals to generate and execute programs that will be used to convert, verify or review the content and properties of non-relational data structures.

Create Documentation of Data Structures

The following link will focus on the task of generating documentation for a Record Structure (or Record Layout).

Document a Record Structure

The following link will focus on the task of generating documentation for a Record Structure (or Record Layout). The generation is based on the record and field structure as defined in a COBOL Copy File. The generated document will be an ASCII/Text File with an HTML content and may be viewed with a browser of choice.

    Explore how to generate HTML Documentation for Records Structures. This link will describe and demonstrate the process of reading a COBOL Copy File and producing an HTML document that contains the record and field properties.

Document a Record Structure with Field Selection

The following link will focus on the task of generating COBOL programs that will read data files or VSAM Data Sets and produce Hexadecimal Dump information of selected records based on a user request. The generation phase will require a Windows system. The generated source code may be compiled and executed on a system of choice.

    Explore how to generate HTML Documentation and Identify Numeric Values. This link will describe and demonstrate the process of reading a COBOL Copy File and producing an HTML document that contains the record and field properties. As a secondary item it will produce a list of the field names that are defined as numeric values. This list may be used when generating programs that will calculate Summary Totals.

Data File Convert

The following link will focus on the task of generating COBOL programs that will do a file format or record content conversion. The generation phase will require a Windows system. The generated source code may be compiled and executed on a system of choice.

    Explore how to generate a Data Conversion Program. This link will describe and demonstrate the process.

Data File Compare

The following link will focus on the task of generating COBOL programs that will compare the content of data files on a record by record basis. The generation phase will require a Windows system. The generated source code may be compiled and executed on a system of choice.

    Explore how to generate a Data Compare Program. This link will describe and demonstrate the process.

Data Validate

The following link will focus on the task of generating COBOL programs that will be used to validate the integrity of numeric fields or present records in a format that may be reviewed in a manual validation process.

Data Validation, Accumulate Summary Totals

The following link will focus on the task of generating COBOL programs that will read data files or VSAM Data Sets and accumulate summary totals. The generation phase will require a Windows system. The generated source code may be compiled and executed on a system of choice.

    Explore how to generate a Summary Totals Program. This link will describe and demonstrate the process.

Data Validation, Hexadecimal Dump

The following link will focus on the task of generating COBOL programs that will read data files or VSAM Data Sets and produce Hexadecimal Dump information of selected records based on a user request. The generation phase will require a Windows system. The generated source code may be compiled and executed on a system of choice.

    Explore how to generate a Hexadecimal Dump Program. This link will describe and demonstrate the process.

Non-Relational Data, Test Cases

This section will focus on the how to Create, document and maintain the test data used by the SIMOTIME Test Cases.

    Explore Data Files used in the Test Cases. This document provides an overview of the non-Relational Data Structures with tips and techniques for creating, documenting and maintaining the files.

Status Codes and Utility Programs

This section is intended for individuals that are learning, creating or maintaining applications that access VSAM Data Sets. Sample programs are provided and most samples will run on an IBM Mainframe or Micro Focus Mainframe Express platform.

File Status Code, Reference Document

The ANS/85 standard provides for a two-byte file-status-key. The first character of the file-status-key is known as status-key-1. The second character is known as status-key-2.

The combinations of possible values and their meanings are shown in the File Status Codes Documents with some comments where vendor additions or extensions may occur.

File Status Codes & Description (KSDS)

This example will use IEBGENER to create a sequential file. This file will be used by IDCAMS to populate a VSAM, KSDS. The KSDS will information about file status codes.

Review the Documentation for this suite of program members. Link to an Evaluation zPAK Option that includes the program members, documentation and control files.

Format & Display a File Status Code

This COBOL programming example will show how to display the file status code by converting the two byte file status code that may contain binary data to a four byte numeric value. This example contains two COBOL programs. The first is a demonstration program that generates various two byte, file status codes. The second COBOL routine does the actual conversion to a four byte, numeric value that may be displayed. A brief description of the file status code is also provided.

Review the Documentation for this suite of program members. Link to an Evaluation zPAK Option that includes the program members, documentation and control files.

Create, Update or Delete a Data Set

This suite of programs will create, populate and delete the QSAM file and the VSAM, KSDS data set used by many of the sample programs. Sample mainframe JCL and a sample COBOL program are included.

Review the Documentation for this suite of program members. Link to an Evaluation zPAK Option that includes the program members, documentation and control files.

Test Cases and Data Access

The link to the test cases is included here because most of the test cases include some form of data access using non-relation data files, VSAM Data Sets or other data structures such as Partitioned Data Sets (PDS's).

    Explore a List of Test Cases that are currently available to be used for Regression or User Acceptance Testing. This suite of Test Cases may be used in the Unit, Application or System Testing environments.

VSAM Program Examples

This section is intended for individuals that are learning, creating or maintaining applications that access VSAM Data Sets. Sample programs are provided and most samples will run on an IBM Mainframe or Micro Focus Mainframe Express platform.

VSAM & KSDS, Program Examples

The following describes how to create or maintain applications that access VSAM Key Sequenced Data Sets (KSDS). Sample programs are provided and most samples will run on an IBM Mainframe or Micro Focus Mainframe Express platform.

Access, a Single COBOL Program

This program suite provides an example of how a single COBOL program is used to access a VSAM data set. The COBOL programs are written using COBOL/2 dialect but also works with COBOL for MVS and COBOL/370.

Review the Documentation for this suite of program members. Link to an Evaluation zPAK Option that includes the program members, documentation and control files.

Access, COBOL with COBOL I/O Routine

This program suite provides an example of how a single COBOL program is used to access a VSAM data set. The COBOL programs are written using COBOL/2 dialect but also works with COBOL for MVS and COBOL/370.

Review the Documentation for this suite of program members. Link to an Evaluation zPAK Option that includes the program members, documentation and control files.

Access, COBOL with Assembler I/O Routine

This program suite provides an example of how a mainline COBOL program calls a mainframe Assembler I/O routine to access a VSAM data set. The COBOL program is written using the COBOL/2 dialect but also work with COBOL for MVS and COBOL/370. The assembler IO routine is written in IBM Mainframe Assembler, it will compile using Assembler/H or HLASM.

Review the Documentation for this suite of program members. Link to an Evaluation zPAK Option that includes the program members, documentation and control files.

VSAM & ESDS, Program Examples

The following describes how to create or maintain applications that access VSAM Entry Sequenced Data Sets (KSDS). Sample programs are provided and most samples will run on an IBM Mainframe or Micro Focus Mainframe Express platform.

JCL to Define, COBOL to Add Records

This program suite provides an example of how to delete and define a new Entry Sequenced Data Set (ESDS) using Mainframe JCL. Once the new ESDS is created a COBOL program is used to add records to the data set.

Review the Documentation for this suite of program members. Link to an Evaluation zPAK Option that includes the program members, documentation and control files.

VSAM & RRDS, Program Examples

The following describes how to create or maintain applications that access VSAM Relative Record Data Sets (RRDS). Sample programs are provided and most samples will run on an IBM Mainframe or Micro Focus Mainframe Express platform.

JCL to Define, COBOL to Add Records

This program suite provides an example of how to delete and define a new Relative Record Data Set (RRDS) using Mainframe JCL. Once the new RRDS is created a COBOL program is used to add records to the data set.

Review the Documentation for this suite of program members. Link to an Evaluation zPAK Option that includes the program members, documentation and control files.

QSAM Access, Program Examples

This section is intended for individuals that are learning, creating or maintaining applications that access QSAM Files. Sample programs are provided and most samples will run on an IBM Mainframe or Micro Focus Mainframe Express platform.

A Single COBOL Program

This program suite provides an example of how a single COBOL program is used to access a QSAM or Sequential file. The COBOL programs are written using COBOL/2 dialect but also works with COBOL for MVS and COBOL/370.

Review the Documentation for this suite of program members. Link to an Evaluation zPAK Option that includes the program members, documentation and control files.

COBOL with COBOL I/O Routine

This program suite provides an example of how a mainline COBOL program calls a mainframe COBOL I/O routine to access a QSAM or Sequential file. The I/O routine will also display the file status codes when an I/O error occurs. The COBOL programs are written using the COBOL/2 dialect but also work with COBOL for MVS and COBOL/370.

Review the Documentation for this suite of program members. Link to an Evaluation zPAK Option that includes the program members, documentation and control files.

COBOL with Assembler I/O Routine

This program suite provides an example of how a mainline COBOL program calls a mainframe Assembler I/O routine to access a QSAM sequential file. The COBOL program is written using the COBOL/2 dialect but also work with COBOL for MVS and COBOL/370. The assembler IO routine is written in IBM Mainframe Assembler, it will compile using Assembler/H or HLASM.

Review the Documentation for this suite of program members. Link to an Evaluation zPAK Option that includes the program members, documentation and control files.

Sequential Files

This section provides information and links to documents and examples for creating and accessing sequential files.

CSV Record Structure

This section provides information and links to documents and examples for creating and accessing sequential files with a record structure of Comma-Separated-Values (CSV).

CSV, Create a New Sequential File

This example describes how to create a sequential file with CSV formatted records.

Review the Documentation for this suite of program members. Link to an Evaluation zPAK Option that includes the program members, documentation and control files.

CSV, Access an Existing Sequential File

This example describes how to access an existing sequential file with CSV formatted records.

Review the Documentation for this suite of program members. Link to an Evaluation zPAK Option that includes the program members, documentation and control files.

Variable-Length, Record Sequential

This program suite provides an example of how to create and access a sequential file containing variable length records. The COBOL programs are written using the COBOL/2 dialect but also works with COBOL for MVS and COBOL/370.

VREC, Process using Standard COBOL

This program suite provides an example of how to create and access a sequential file containing variable length records using standard SELECT and FD statements. The COBOL programs are written using the COBOL/2 dialect but also works with COBOL for MVS and COBOL/370.

Review the Documentation for this suite of program members. Link to an Evaluation zPAK Option that includes the program members, documentation and control files.

VREC, Process using Byte-Stream I/O

This program suite provides an example of how to transfer and convert a sequential file containing variable length records. The example includes a description of how to use FTP to download a file without doing a conversion on the Mainframe System. The COBOL programs are written using the Micro Focus dialect and requires Micro Focus Net Express or Micro Focus Mainframe Express.

Review the Documentation for this suite of program members. Link to an Evaluation zPAK Option that includes the program members, documentation and control files.

VREC, Transfer, Share, Convert, Compare

This program suite provides an example of how to Transfer, Share, Convert and Compare record and line sequential files containing variable length records. The example includes a description of how to use FTP to download a file without doing a conversion on the Mainframe System. The COBOL programs are written using the Micro Focus dialect and requires Micro Focus Net Express.

Review the Documentation for this suite of program members. Link to an Evaluation zPAK Option that includes the program members, documentation and control files.

VREC, ASCII/Text to Record Sequential

The example will describe how to convert an ASCII/Text file (Line Sequential) to a Micro Focus Record Sequential file with variable length records. The COBOL program that does the file format conversion was generated using SimoTime Technology running on a Windows System and using Micro Focus COBOL.

Review the Documentation for this suite of program members. Link to an Evaluation zPAK Option that includes the program members, documentation and control files.

VREC, Create, Convert, Compare and more

This document will describe and demonstrate how to access and process Record Sequential files with variable length records. The processing techniques include file create, convert, compare and view in a Hex Dump format.

Partitioned Data Sets (PDS's)

This section provides information and links to documents and examples for creating, populating and deleting PDS structures and/or members within a PDS.

Manage Partitioned Data Sets (PDS's)

This suite of programs provides examples of how to create and manage a Partitioned Data Set (PDS) in a ZOS environment or a Micro Focus Enterprise environment.

Review the Documentation for this suite of program members. Link to an Evaluation zPAK Option that includes the program members, documentation and control files.

Extract and Transfer PDS Members

    Explore how to Transfer all the members within a PDS to a Windows Directory using File Transfer Protocol (FTP). This approach uses the IEBPTPCH Utility Program (available on a ZOS Mainframe System) to extracts all the members from a PDS and concatenates the members into a single sequential file. Each member in the file will be preceded by a record that contains the member name. The single sequential file is then transferred to the target system.

Unstring PDS Members from a File

There is a number of utilitarian programs on a Mainframe System that will extract all the members from a PDS and place them into a single sequential file with a special record preceding each member. The single sequential file is then transferred to a Linux, UNIX or Windows (LUW) system. The following three (3) sub-sections describe and demonstrate how to unstring the members and place them in a directory for use with Micro Focus Enterprise Developer.

Unstring Multiple PDS Members, Option 1

    Explore How to Extract Multiple Source Members contained in a single sequential file into a folder (or directory) on a Windows System. Each member in the sequential file is delimited by a -PUNCH record.

Unstring Multiple PDS Members, Option 2

    Explore How to Extract Multiple Source Members contained in a single sequential file into a folder (or directory) on a Windows System. Each member in the sequential file is delimited by a START and END record.

Unstring Multiple PDS Members, Option 3

    Explore How to Extract Multiple Source Members contained in a single sequential file into a folder (or directory) on a Windows System. The sequential file was created on a Mainframe System using IEBPTPCH.

Data Processing Tips & Techniques

This group of documents and programs describes and demonstrates various approaches to allocating data resources to a job. Various processing or access methods are discussed based on the type of allocation and the file structure.

Generation Data Groups (GDG's)

This suite of sample programs describes how to define a Generation Data Group (GDG). Once the GDG is defined the creation of a Generation Date Set (referred to as a generation or GDS) within the group is discussed. The COBOL program is written using the COBOL/2 dialect but works with COBOL for MVS and COBOL/370.

Review the Documentation for this suite of program members. Link to an Evaluation zPAK Option that includes the program members, documentation and control files.

Working with Concatenated Data Sets

This suite of programs and documentation will describe and demonstrate the data set concatenation function provided with JCL, Utility Programs and COBOL. It is possible to process more than one data set as a single data set by concatenating the DD statements.

Review the Documentation for this suite of program members. Link to an Evaluation zPAK Option that includes the program members, documentation and control files.

Merge or Concatenate Three Files

This suite of programs will describe and demonstrate how to merge or concatenate multiple files of various record lengths into a single file. This package includes a job (JCL Member) that will create the test files. The techniques for merging the files will use IEBGENER, IDCAMS or SORT.

Review the Documentation for this suite of program members. Link to an Evaluation zPAK Option that includes the program members, documentation and control files.

Alternate Index for VSAM, KSDS

This program suite provides an example of how a COBOL program can process a VSAM, Keyed Sequential Data Set (KSDS) with a primary key and an alternate index. The COBOL programs are written using the COBOL/2 dialect but work with COBOL for MVS and COBOL/370.

Review the Documentation for this suite of program members. Link to an Evaluation zPAK Option that includes the program members, documentation and control files.

Data Validation Techniques

This section provides access to documents and test cases that will describe and demonstrate how to create and/or use tools that will assist in the validation and review of data within non-relational data structures.

Execute and Review Results

WIP

The following is a test case that will describe and demonstrate various techniques for transferring and sharing data between systems of different architectures.

    Explore how to assess, prepare, maintain and validate data in a pre and post transition or sharing of data in a multi-user and multi-system environment. The data structures are based on the definitions provided from COBOL copy files. This includes record layouts for non-relational files and/or VSAM Data Sets.

Diagnostic Aids

This section provides access to documents with sample programs that will describe and demonstrate how to create and/or use tools that will assist in the review of data within non-relational data structures.

Hexadecimal Dump Capabilities

The SIMOTIME Technologies provide a Hex-Dump capability using Record-Level I/O (RLIO) access or Byte-Stream I/O (BSIO) access. The RLIO access may be referred to as logical file access because it accesses the file at the logical record level and requires a knowledge of the file format and record structure. The BSIO access may be referred to as physical file access because it accesses the file at the byte level and does not need or use any knowledge of the file format or logical record structure.

VSAM, KSDS to Hex-Dump

The SIMOTIME Technologies have the capability of generating COBOL programs that will read a VSAM, KSDS and write hexadecimal dump information to a sequential file. The dumped records are defined by the user via a control file containing a list of keys for the KSDS. Since the hex-dump information is all text the dump file may be viewed with a text editor of choice.

Hex Dump, Generate with User Exit

This is an example of how a COBOL program can read from an Indexed file (or a VSAM KSDS) and write to a sequential ASCII/Text file containing HEX dump information of a data structure with Text, Packed and Binary Data Strings (or User Defined Fields).

Review the Documentation for this suite of program members. Link to an Evaluation zPAK Option that includes the program members, documentation and control files.

Hex Dump, Generate with Dump by Call

This is an interesting program that would have required an assembler routine prior to the introduction of COBOL/2 for the mainframe. This program reads the Customer Master File that is a VSAM, Keyed-Sequential-Data-Set (KSDS) and writes a variable-length, sequential file that contains hexadecimal information. Records to be written to the Hex-Dump file are selected based on a list of primary keys in a control file.

Review the Documentation for this suite of program members. Link to an Evaluation zPAK Option that includes the program members, documentation and control files.

Hex Dump, Generate a Single Program

This is an interesting program that would have required an assembler routine prior to the introduction of COBOL/2 for the mainframe. This program reads the Customer Master File that is a VSAM, Keyed-Sequential-Data-Set (KSDS) and writes a sequential file that contains hexadecimal information. Records to be written to the Hex-Dump file are selected based on a list of primary keys in a control file. The File I-O and Dump Formatting are done within a single COBOL program

Review the Documentation for this suite of program members. Link to an Evaluation zPAK Option that includes the program members, documentation and control files.

Sequential File to Hex Dump

This suite of sample programs performs Sequential File I/O and HEX-Dump formatting of a record sequential file containing 80-byte, fixed-length records using Micro Focus COBOL. The programs describe how to dump the input records to an output file in Hexadecimal format.

Review the Documentation for this suite of program members. Link to an Evaluation zPAK Option that includes the program members, documentation and control files.

ASCII/Text to Hex Dump

This suite of sample programs performs Sequential File I/O and HEX-Dump formatting of an ASCII/Text File using Micro Focus COBOL. The programs describe how to dump the input records to an output file in Hexadecimal format.

Review the Documentation for this suite of program members. Link to an Evaluation zPAK Option that includes the program members, documentation and control files.

Sort a File

This section provides information and links to white papers and examples for using the SORT on an IBM Mainframe System or a Micro Focus environment running on a Windows, Linux or UNIX System.

Mainframe SORT using JCL

This suite of programs provides an example of how to do syntax checking of a JCL member without executing the job steps. The first two JOB steps use IEFBR14 to delete previously created files and then uses IEBGENER to create a new file. The next two JOB steps use the SORT utility to copy a file and to sort a file. A job step is included that will do a case insensitive sort.

Review the Documentation for this suite of program members. Link to an Evaluation zPAK Option that includes the program members, documentation and control files.

Mailing Labels, Postal Code Sequence

This suite of programs provides an example of how a mainline application processes a VSAM, KSDS or Indexed File containing Name, Address information and creates a sorted (by postal code sequence) sequential file containing mailing labels that are formatted with 1, 2, 3 or 4 labels across of six lines for each label. This example uses a two-dimensional array to build the label-printing output.

Review the Documentation for this suite of program members. Link to an Evaluation zPAK Option that includes the program members, documentation and control files.

Simple Case Insensitive Sort

This suite of programs will describe how to do use the Micro Focus SORT program with a Windows command line or Mainframe JCL. The Mainframe JCL will execute on a Mainframe System with ZOS. A small sequential file is created and then sorted based on the standard collating sequence for the system (i.e. EBCDIC or ASCII). A subsequent job step will do a Case Insensitive Sort using the ALTSEQ function of the SORT program.

Review the Documentation for this suite of program members. Link to an Evaluation zPAK Option that includes the program members, documentation and control files.

How to use COBOL to call SORT

This suite of programs will describe and demonstrate by example how to use a COBOL program to call the SORT program to sort the records in a data file in ascending order by the surname that is located in positions 8-22.

Review the Documentation for this suite of program members. Link to an Evaluation zPAK Option that includes the program members, documentation and control files.

ASCII or EBCDIC Sort using ALTSEQ

This suite of programs will describe and demonstrate by example how to sort ASCII-encoded Files into an EBCDIC collating sequence or EBCDIC-encoded files into an ASCII collating sequence using the ALTSEQ function of the Mainframe SORT or the ALTSEQ function of the Micro Focus SORT.

Review the Documentation for this suite of program members. Link to an Evaluation zPAK Option that includes the program members, documentation and control files.

SORT a File, Create a Report

This suite of jobs will describe and demonstrate by example how to sort a record sequential file and produce a report with sub-totals and final totals. The process for sorting and producing the report will use the SORT program and is executable on an IBM/ZOS Mainframe System or on a Linux, UNIX or Windows (LUW) System using Micro Focus Server.

Review the Documentation for this suite of program members. Link to an Evaluation zPAK Option that includes the program members, documentation and control files.

Create KSDS, use SORT or RECORG

This suite of programs will describe how to use the Micro Focus SORT program and a Windows command file to create an empty Key-Sequenced-Data-Set (or VSAM, KSDS>. This function is similar to the DELETE/DEFINE function of IDCAMS. Two sample JCL members are included that describe how to create a VSAM cluster using JCL on a Mainframe System with ZOS or a Linux, UNIX or Windows System with Micro Focus.

Review the Documentation for this suite of program members. Link to an Evaluation zPAK Option that includes the program members, documentation and control files.

Data File Information Collection

This example will use a Windows System running a Micro Focus sub-system to create a Key-Sequenced-Data-set containing an inventory of traditional sequential files and VSAM Data Sets. Once the inventory of files has been created it will be possible to use this information to build a catalog for Micro Focus Mainframe Express or Micro Focus Studio/Server environments.

Review the Documentation for this suite of program members. Link to an Evaluation zPAK Option that includes the program members, documentation and control files.

The SimoCARD Series, 80-Bytes

The SimoCARD Suite of Programs will provide read and write access to Record Sequential and Line Sequential data files consisting of eighty (80) byte records that have been downloaded from a mainframe using the File Transfer Protocol (FTP). The Record Sequential files are usually downloaded in BINARY mode and contain EBCDIC encoded data. The Line Sequential files are usually downloaded in ASCII mode and contain ASCII encoded data. In addition to the four I/O routines a fifth callable routine is provided that will convert eighty (80) byte text strings between ASCII and EBCDIC.

Note: A Line Sequential file may also be referred to as an ASCII/Text file.

Data Management Series, Articles

This section provides examples and links to documents that describe the management of data sharing or application migration between an IBM Mainframe System and a Windows System using Micro Focus. The information provided will cover data file transfer, conversion and comparison of non-relation or traditional sequential files and VSAM, Keyed Sequential Data Sets (KSDS). Click here for a Consolidated Look at the White Papers and Sample Programs provided by the Data Management Series.

Data File Abstract

This is a link to a white paper that provides a Quick Overview of the Data Management Tasks required to migrate or share data between a Mainframe system and a Windows, Linux or UNIX system.

Data File Transfer

This is a link to a white paper that provides a Quick Overview of the Data File Transfer options available when transferring or sharing data between a Mainframe system and a Windows, Linux or UNIX system.

Data File Conversion

This is a link to a white paper that provides a Quick Overview of the Possible Data File Conversion options available when migrating or sharing data between a Mainframe system and a Windows, Linux or UNIX system.

Data File Comparison (or Validation)

This is a link to a white paper that provides a Quick Overview of the Possible Data File Comparison options available when testing an application or data that has been moved between a Mainframe system and a Windows, Linux or UNIX system.

File Formats for Micro Focus

This is a link to a white paper that provides a quick overview of the various Micro Focus File Formats provided for the Windows, Linux and UNIX environments supported by Micro Focus

Data Flow across Multiple Systems

This is a link to the documentation for a suite of test cases that actually transfer and convert non-relational data structures between IBM Mainframe Systems (EBCDIC encoded) and Windows, Linux or UNIX Systems (ASCII or EBCDIC encoded using Micro Focus). The data structures may contain various numeric formats such as COMP (Binary) or COMP-3 (Packed-Decimal).

File Transfer-Convert-Validate

This section provides examples and links to documents that describes the data file transfer, convert or validate (using compare, summary totals or hex-dump for viewing) of non-relation or traditional sequential files and keyed sequential data sets.

There are many options available when moving and converting data between an IBM Mainframe and a Linux, UNIX or Windows environment. This link provides an overview of the processes for file transfer and conversion with an example of how to convert a VSAM data set to a flat Sequential file on the Mainframe System. Using FTP the sequential file may be transferred from the Mainframe System to a Linux, UNIX or Windows (LUW) System. On the LUW System using Micro Focus technology along with SimoTime technology a new file of a compatible format of ASCII or EBCDIC content may be created and processed.

This link provides detailed examples for file transfer and conversion processes. The examples cover the three commonly used file formats. The formats are a sequential file with fixed length records, a sequential file with variable length records and a keyed sequential data set.

Data File Convert, a User's Guide

Many companies are looking for ways to convert data files using a mainframe system and/or a distributed system (i.e. Linux, UNIX and/or Windows or "LUW") running Micro Focus sub-systems. The SimoTime Utility program (UTCONVRT) is intended to assist in these efforts. The UTCONVRT program runs in the Windows environment and generates conversion programs (COBOL Source Code) that may be compiled and executed on a distributed LUW platform with Micro Focus or on an IBM Mainframe.

The SimoTime Utility for Data File Convert will provide additional detail about creating a Process Control File and generating the COBOL source code for a data file convert program. The sample convert programs described in this document were generated using this utility program.

A Simple 80/80 Convert

This link provides an example of A Simple 80/80 Convert using a generated COBOL program that compares the content of two sequential files. The package includes documentation, programs and control files.

Convert Text and Expand Numeric Values

This test case will convert the file format, record content and record structure of an EBCDIC-encoded file that was created and transferred from an IBM Mainframe System to a format and structure that may be easily imported and accessed from within a relational data base or a spread sheet using Excel or LibreOffice Calc. This expanded request will involve more than a simple EBCDIC to ASCII conversion. This test case will describe and demonstrate how to identify and convert text strings between EBCDIC and ASCII and how to identify, expand and convert numeric values that are formatted as Signed-Zoned-Decimal, Packed-Decimal or Binary.

Customer File with Packed & Binary Data

This link how to Convert an EBCDIC-encoded Customer Master File to ASCII using a set of generated COBOL programs that perform the conversion on a field-by-field basis. The conversion routine will retain the mainframe numeric integrity for packed and binary fields. The package includes documentation, programs and control files.

Fixed-Field to Comma-Separated-Values

This document and the test case will describe and demonstrate how to read a VSAM, Key-Sequenced-Data-Set (KSDS) and create a sequential file with a record structure of Comma-Separated-Values (CSV) that may be easily imported into an Excel spreadsheet. The fixed-length field from the VSAM, KSDS input will be converted to variable length field and the various numeric formats will be expanded to text-orientation with an explicit decimal point and a trailing sign byte.

This is actually two COBOL programs. The first program (File Format Conversion) does the File I/O for reading the Customer Master File and writing reformatted records to a sequential file. The File I/O program calls the second program to do the record content conversion (or record formatting) that expands the numeric fields and does blank truncation on the text fields and then places a comma between the fields as the field delimiter.

Review the Documentation for this suite of program members. Link to an Evaluation zPAK Option that includes the program members, documentation and control files.

Packed & Binary Numbers to Text Strings

This suite of test programs describes how to extract data from an ASCII-encoded, record sequential file. The numeric fields will be expanded (Packed or Binary) into text strings with an explicit decimal point and a separate sign character. The trailing spaces within the original text fields will be truncated. A new record will be constructed with the fields being concatenated and separated by a comma. The newly constructed records will be written to a sequential file.

Review the Documentation for this suite of program members. Link to an Evaluation zPAK Option that includes the program members, documentation and control files.

Convert - Miscellaneous Programs

This section describes additional Data File Conversion programs and processes that are commonly used across a variety of application groups.

A Simple EBCDIC to ASCII Conversion

This example uses a single COBOL program that reads an EBCDIC-encoded file of eighty (80) byte records and creates a new file of ASCII-encoded, eighty (80) byte records. The input records should contain text strings that are valid print characters.

Review the Documentation for this suite of program members. Link to an Evaluation zPAK Option that includes the program members, documentation and control files.

Line & Record Sequential, EBCDIC & ASCII

This suite of sample programs will show an approach to the task of File format conversion between Line Sequential and Record Sequential files. Also, file content (or record content)conversion between ASCII and EBCDIC will be discussed. This example uses sequential files with 80-byte records.

Review the Documentation for this suite of program members. Link to an Evaluation zPAK Option that includes the program members, documentation and control files.

Comma-Separated-Values & Fixed-Fields

When data is transferred or shared across a number of different systems it is often necessary to change the file format and/or the record content structure. The purpose of this suite of programs is to show an approach for preparing or converting data to be transferred or shared across systems of different architectures. This example uses sequential files with 80-byte records and ASCII/Text files.

Review the Documentation for this suite of program members. Link to an Evaluation zPAK Option that includes the program members, documentation and control files.

File Format & Record Content Conversion

This suite of programs includes examples for converting record content between ASCII and EBCDIC. The document describes file format conversion between ASCII/Text and Record Sequential file formats and includes examples of repositioning and expanding field sizes and record keys for indexed files.

Review the Documentation for this suite of program members. Link to an Evaluation zPAK Option that includes the program members, documentation and control files.

Advanced Data Convert Functions

The following will discribe and demonsttrate how to use and combine the basic and advanced functions of the data conversion technologies and implementation techniques.

Manage Numeric Integrity

WIP

Run Book, Numeric Integrity

This is the Run Book for the TCNBRS01 Test Case. This test case will describe and demonstrate the process of converting an EBCDIC-encoded, Record Sequential file to an ASCII-encoded Record Sequential file. The numeric values stored in a Packed-Decimal or Binary format will be maintained in their original format. The numeric values stored in a Zoned-Decimal format will be converted between EBCDIC and ASCII as required.

Sys Prep, Numeric Integrity

This is the System Preparation Manual for the TCNBRS01 Test Case. This test case will convert the file format, record content and record structure of an EBCDIC-encoded file that was created and transferred from an IBM Mainframe System to a format and structure that may be easily imported and accessed from within an ASCII-oriented system environment. The numeric values stored in a Packed-Decimal or Binary format will be maintained in their original format. The numeric values stored in a Zoned-Decimal format will be converted between EBCDIC and ASCII as required.

Manage EBCDIC ASCII Convert

WIP

Run Book, VSAM KSDS EBC ASC

This is the Run Book for the TCKSDSRB Test Case. This test case will describe and demonstrate the process of converting an EBCDIC-encoded, Record Sequential file to an ASCII/Text file. The convert process includes file format, record content and field format conversion. This test case will describe and demonstrate how to identify and convert text strings between EBCDIC and ASCII and how to identify, expand and convert numeric values that are formatted as Signed-Zoned-Decimal, Packed-Decimal or Binary.

Sys Prep, VSAM KSDS EBC ASC

This is the System Preparation Manual for the TCKSDSSP Test Case. This test case will convert the file format, record content and record structure of an EBCDIC-encoded file that was created and transferred from an IBM Mainframe System to an ASCII-encoded Indexed file.

Manage Numeric Convert

WIP

Run Book, Numeric Convert

This is the Run Book for the TCNTXT01 Test Case. This test case will describe and demonstrate the process of converting an EBCDIC-encoded, Record Sequential file to an ASCII/Text file. The convert process includes file format, record content and field format conversion. This test case will describe and demonstrate how to identify and convert text strings between EBCDIC and ASCII and how to identify, expand and convert numeric values that are formatted as Signed-Zoned-Decimal, Packed-Decimal or Binary.

Sys Prep, Numeric Convert

This is the System Preparation Manual for the TCNTXT01 Test Case. This test case will convert the file format, record content and record structure of an EBCDIC-encoded file that was created and transferred from an IBM Mainframe System to a format and structure that may be easily imported and accessed from within an ASCII-oriented relational data base or a spread sheet using Excel or LibreOffice Calc.

Data File Compare, a User's Guide

Many companies are looking for ways to compare data files using a mainframe system and/or a distributed system (i.e. Linux, UNIX and/or Windows or "LUW") running Micro Focus sub-systems. The SimoTime Utility program (UTCOMPRT) is intended to assist in these efforts. The UTCOMPRT program runs in the Windows environment and generates comparison programs (COBOL Source Code) that may be compiled and executed on a distributed LUW platform with Micro Focus or on an IBM Mainframe.

The SimoTime Utility for Data File Compare will provide additional detail about creating a Process Control File and generating the COBOL source code for a data file compare program. The sample compare programs described in this document were generated using this utility program.

A Simple 80/80 Compare

This link provides an example of A Simple 80/80 Compare using a generated COBOL program that compares the content of two sequential files. The package includes documentation, programs and control files.

Customer File, Partial Record Compare

This link provides an example of A Moderate Data Set Compare using a generated COBOL program that compares the content of two VSAM Keyed-Sequence-Data-Sets (or KSDS). The package includes documentation, programs and control files.

Report File Compare, Compaction & Bypass

This suite of programs and documentation will describe and demonstrate additional capabilities and advanced data file compare functions for comparing report-oriented files that contain page headers with date and time stamps and user-defined line items. The ability to conditionally omit records from the compare process and to write the results of the compare process to a log file are included.

Review the Documentation for this suite of program members. Link to an Evaluation zPAK Option that includes the program members, documentation and control files.

Compare Files, Variable-Length Records

This suite of programs will describe and demonstrate how to compare two record-sequential files that have variable-length records and a maximum record length of 80 bytes. The program that does the actual data file compare is a COBOL program that is generated using SimoTime technologies. The compare logic will compare the entire record for each file by using predefined positions for comparison. The results of the compare and the summary information will be posted to the SYSYOUT device.

Review the Documentation for this suite of program members. Link to an Evaluation zPAK Option that includes the program members, documentation and control files.

Compare Positions Defined at Execution Time

This suite of programs will describe and demonstrate how to compare two record-sequential files that have variable-length records and a maximum record length of 80 bytes. The program that does the actual data file compare is a COBOL program that is generated using SimoTime technologies. The compare logic will read a specifications file (SYSUT3) and compare positions within each record based on the compare statements in the specifications file. The results of the compare and the summary information will be posted to a SYSLOG file.

Review the Documentation for this suite of program members. Link to an Evaluation zPAK Option that includes the program members, documentation and control files.

Compare with a Call to Convert

When data files are transferred or shared between systems the ability to do data file compares and data processing confirmation becomes a requirement. This document and the associated test cases will describe and demonstrate a minimum set of alternatives for the compare or confirm process. This suite of programs contains a test case with a call to do record conversion prior to performing the compare function.

Review the Documentation for this suite of program members. Link to an Evaluation zPAK Option that includes the program members, documentation and control files.

Data File Validation

The data file validation (confirmation or verification) process will read a file and calculate record counts and check sum totals for user defined numeric fields.

Calculate Record and Summary Totals

This suite of programs and documentation will describe and demonstrate an approach for reading a file, calculating record counts and producing summary totals for a set of pre-defined numeric fields. The approach uses two COBOL programs that were generated using SimoTime technology. The programs are generated on a Windows System with Micro Focus COBOL. The generated programs may be compiled and executed on an IBM Mainframe (ZOS or VSE) or a Linux, UNIX or Windows System with Micro Focus COBOL.

Review the Documentation for this suite of program members. Link to an Evaluation zPAK Option that includes the program members, documentation and control files.

Calculate Totals for an Item Master File

This suite of programs and documentation will describe and demonstrate an approach for reading an Item Master file, calculating record counts and producing summary totals for a set of pre-defined numeric fields. The approach uses two COBOL programs that were generated using SimoTime technology. The programs are generated on a Windows System with Micro Focus COBOL. The generated programs may be compiled and executed on an IBM Mainframe (ZOS or VSE) or a Linux, UNIX or Windows System with Micro Focus COBOL.

Review the Documentation for this suite of program members. Link to an Evaluation zPAK Option that includes the program members, documentation and control files.

Calculate Totals for Packed-Decimal Fields

The SimoTime Technologies have the capability to read a Data File or VSAM Data Set and calculate a record count and accumulate summary totals for the user-defined, numeric fields within a record. Once the record count and summary totals are accumulated they are written to a user-defined output device that may be a file or a SYSOUT device. This suite of programs and documentation will access a test file that contains packed-decimal numeric values. The approach uses two COBOL programs that were generated using SimoTime technology. The programs are generated on a Windows System with Micro Focus Enterprise Developer. The generated programs may be compiled and executed on an IBM Mainframe (ZOS or VSE) or a Linux, UNIX or Windows System with Micro Focus COBOL.

Review the Documentation for this suite of program members. Link to an Evaluation zPAK Option that includes the program members, documentation and control files.

Unique or Proven Requirements

This group of documents and programs provides additional and/or creative techniques for processing files and manipulating the data within files.

A File Format Conversion from Mainframe Image with Variable Length Records

The objective of this suite of programs and documentation is to provide a solution for using FTP to download a mainframe sequential file with variable length records to a system that is running Microsoft Windows and Micro Focus COBOL and convert the file format to a Micro Focus sequential file with variable length records.

Review the Documentation for this suite of program members. Link to an Evaluation zPAK Option that includes the program members, documentation and control files.

A Data File Transition Cycle with Various Convert & Compare Processes

This link provides an example of the various conversion and comparison processes that move data from EBCDIC encoded environments to ASCII encoded environments and from a Mainframe format to a format that may be easily imported into an excel spreadsheet.

Review the Documentation for this suite of program members. Link to an Evaluation zPAK Option that includes the program members, documentation and control files.

Various Data File Create, Convert, Copy and Compare Examples

This link provides an example of the various create, convert, copy and compare processes that do a variety of file format conversions using IDCAMS and the REPRO function.

Review the Documentation for this suite of program members. Link to an Evaluation zPAK Option that includes the program members, documentation and control files.

File Access, Multiple Record Types

This link provides an example of processing a file with multiple record types using COBOL programs.

Review the Documentation for this suite of program members. Link to an Evaluation zPAK Option that includes the program members, documentation and control files.

Micro Focus Environment

This section describes sample programs and documents that are unique to the Micro Focus Environment.

File Formats for Micro Focus

This is a link to a white paper that provides a quick overview of the various Micro Focus File Formats provided for the Windows, Linux and UNIX environments supported by Micro Focus

Compiler Directives

This white paper describes the various Micro Focus compiler directives that may be required to control program behavior in the Linux, UNIX or Windows environments in a manner compliant with the compiler options and subsequent execution on the Mainframe System. The directives will affect the way programs process and format numeric fields. Once the data is stored in a data file on a permanent storage media the format of the records and their content structure must be maintained.

Create & Process Large Files (greater than 2-gig)

This program suite provides an example of how to create or access data files that exceed two gigabytes in size. Micro Focus provides support for files that exceed two gigabytes but the capability must be configured. The COBOL program is written using the COBOL/2 dialect but also work with COBOL for MVS and COBOL/370.

Review the Documentation for this suite of program members. Link to an Evaluation zPAK Option that includes the program members, documentation and control files.

Baseline Elapsed Timings (Small, Medium & Large Files)

This document will demonstrate and describe how to establish a set of baseline performance metrics by calculating elapsed time for batch jobs from information extracted from the Micro Focus JES output.

Review the Documentation for this suite of program members. Link to an Evaluation zPAK Option that includes the program members, documentation and control files.

Override Default File Location

When a Region (or Server Instance) is configured within Micro Focus Enterprise Server to run batch jobs (i.e. submit JCL) a default directory is defined and used for placement of new physical files that are allocated by a job. This is an example of how to catalog a new data set and override the base configuration and place the physical file in an alternate directory.

Review the Documentation for this suite of program members. Link to an Evaluation zPAK Option that includes the program members, documentation and control files.

Define a Directory for Print Output

The DATACLAS=PRINTOUT on a DD statement is used to route the file to a user defined destination. This is an example of how to catalog a new data set and override the default location and place the physical file in an alternate directory.

Review the Documentation for this suite of program members. Link to an Evaluation zPAK Option that includes the program members, documentation and control files.

Options for Tape Processing

This suite of programs will describe and demonstrate how tape files are processed in a Micro Focus Enterprise Server environment.

Review the Documentation for this suite of program members. Link to an Evaluation zPAK Option that includes the program members, documentation and control files.

Delete/Define a KSDS using SORT

This suite of programs will describe how to do use the Micro Focus SORT program and a Windows command file to create an empty VSAM, KSDS Data Set. This function is similar to the DELETE/DEFINE function of IDCAMS.

Review the Documentation for this suite of program members. Link to an Evaluation zPAK Option that includes the program members, documentation and control files.

Dynamic File Allocation

This suite of programs and documentation will describe and demonstrate the dynamic file allocation function for the Micro Focus Studio and Server environments.

Review the Documentation for this suite of program members. Link to an Evaluation zPAK Option that includes the program members, documentation and control files.

Populate a Catalog

When doing an "application migration" or "transferring and sharing data" between a Mainframe System and a Windows System with Micro Focus Server it can be a challenge to create and populate the Server Catalog entries and make this a repeatable process. This document describes a possible solution to this challenge.

Review the Documentation for this suite of program members. Link to an Evaluation zPAK Option that includes the program members, documentation and control files.

Extract File Information from JCL

This suite of programs will scan JCL members and extract file information based on the IDCAMS specifications or DD statements. The file information will be written to a sequential file. This capability and the information it provides is quite useful when migrating a batch application and data between a Mainframe System to a Windows System using Micro Focus technologies.

Review the Documentation for this suite of program members. Link to an Evaluation zPAK Option that includes the program members, documentation and control files.

The Customer Master Files

On the IBM Mainframe the Customer Master File is a VSAM Keyed Sequential Data Set (referred to as KSDS). On a Windows or UNIX System using Micro Focus the Customer Master File is an Indexed File or Key Sequenced Data Set.

The SIMOTIME regression testing process uses a number of different file formats for a Customer Master File. This session will describe three (3) of the formats.

Customer File, 512 Byte Format

This program suite provides an example of how to create and populate a Customer Master File. On the Mainframe System the file is a VSAM, Key-Sequenced-Data-Set (or KSDS). On a Windows or UNIX System the Micro Focus Indexed File format is used. The file contains 512 byte records and the key (or customer number) is twelve (12) bytes starting at the first position of each record.

This Customer Master file contains variable length records with the minimum and average record length being the same length of 512 bytes. The key starts at the first position of the record and is 12 bytes in length. The record layout (or record structure) is defined in a COBOL copy file and contains text strings and various numeric formats including zoned-decimal, packed and binary. The COBOL copy file provides information for an application program to build a data structure in Working Storage. However, it does not provide explicit information about the start positions of fields within the records or the physical size of the various numeric formats. The HTML document provides this information.

Create and Populate a Test File

This program suite provides an example of how to create and populate a Customer Master File. On the Mainframe System the file is a VSAM, Key-Sequenced-Data-Set (or KSDS). On a Windows or UNIX System the Micro Focus Indexed File format is used. The file contains 512 byte records and the key (or customer number) is twelve (12) bytes starting in the first position of each record.

Review the Documentation for this suite of program members. Link to an Evaluation zPAK Option that includes the program members, documentation and control files.

Extract and Format Data for Excel

This is actually two COBOL programs. The first program does the File I/O of reading the Customer Master File and writing reformatted records to a sequential file. The File I/O program calls the second program to do the record formatting that expands the numeric fields and does blank truncation on the text fields and then places a comma between the fields as the field delimiter.

Review the Documentation for this suite of program members. Link to an Evaluation zPAK Option that includes the program members, documentation and control files.

Convert between EBCDIC & ASCII

This is actually two COBOL programs. The first program does the File I/O of reading the Customer Master File and writing reformatted records to a sequential file. The File I/O program calls the second program to do the record formatting that expands the numeric fields and does blank truncation on the text fields and then places a comma between the fields as the field delimiter.

Review the Documentation for this suite of program members. Link to an Evaluation zPAK Option that includes the program members, documentation and control files.

Create & Populate, Generic Data

This program suite provides an example of how to create and populate a Customer Master File. The number of records in the file is determined by a parameter in a configuration file. The individual names (both first and last), the street name and the city, state are obtained from separate data files. On the Mainframe System the file is a VSAM, Key-Sequenced-Data-Set (or KSDS). On a Windows or UNIX System the Micro Focus Indexed File format is used. The file contains 512 byte records and the key (or customer number) is twelve (12) bytes starting in the first position of each record.

Review the Documentation for this suite of program members. Link to an Evaluation zPAK Option that includes the program members, documentation and control files.

Convert from EBCDIC to ASCII

This suite of sample programs describes how to convert an EBCDIC encoded VSAM Key-Sequenced-Data-Set (KSDS) to an ASCII encoded VSAM Key-Sequenced-Data-Set (KSDS). The data set contains customer information with text, packed and binary data strings.

Review the Documentation for this suite of program members. Link to an Evaluation zPAK Option that includes the program members, documentation and control files.

File Formats for Micro Focus

This is a link to a white paper that provides a quick overview of the various Micro Focus File Formats provided for the Windows, Linux and UNIX environments supported by Micro Focus

Create QAT Files

This suite of batch jobs and programs will describe and demonstrate how to create, modify and monitor files and VSAM, Key-Sequenced-Data-Sets (KSDS) that contain customer information.

The Item Master File

On the IBM Mainframe the Item Master File is a VSAM Keyed Sequential Data Set (referred to as KSDS). On a Windows or UNIX System using Micro Focus the Item Master File is an Indexed File or Key Sequenced File.

The Item (or Product) Master file contains variable length records with the minimum and average record length being the same length of 512 bytes. The key starts in the first position of the record and is 12 bytes in length. The record layout (or record structure) is defined in a COBOL copy file and contains text strings and various numeric formats including zoned-decimal, packed and binary. The COBOL copy file provides information for an application program to build a data structure in Working Storage. However, it does not provide explicit information about the start positions of fields within the records or the physical size of the various numeric formats. The HTML document provides this information.

Extract and Format Data for Excel

This is actually two COBOL programs. The first program does the File I/O of reading the Item Master File and writing reformatted records to a sequential file. The File I/O program calls the second program to do the record formatting that expands the numeric fields and does blank truncation on the text fields and then places a comma between the fields as the field delimiter.

Review the Documentation for this suite of program members. Link to an Evaluation zPAK Option that includes the program members, documentation and control files.

Convert between EBCDIC and ASCII

This is actually two COBOL programs. The first program does the File I/O of reading the Item Master File and writing reformatted records to a sequential file. The File I/O program calls the second program to do the record formatting that expands the numeric fields and does blank truncation on the text fields and then places a comma between the fields as the field delimiter.

Review the Documentation for this suite of program members. Link to an Evaluation zPAK Option that includes the program members, documentation and control files.

Produce HEX-Dump of Records

Provide an individual with the ability to view a record or groups of records from a VSAM/KSDS (the Item Master File). The output will be in a Hexadecimal-Dump format.

Review the Documentation for this suite of program members. Link to an Evaluation zPAK Option that includes the program members, documentation and control files.

Repository Management Programs

The repositories described in the section are VSAM, Key Sequenced Data Structures (or KSDS's). The information stored in each of the repositories can be quite useful when moving or sharing an application and data between an IBM Mainframe and a Linux, UNIX or Windows (LUW) platform running a Micro Focus Server.

Repository for Application Properties

This suite of programs and documentation will provide process knowledge and technology that will collect and build a repository of information about the application source members. This includes COBOL programs and copy files, JCL and PROC's, BMS Screen Definitions and Mainframe Assembler Source Members. This example includes batch and on-line (CICS) programs. The batch is required and the on-line is optional.

Review the Documentation for this suite of program members. Link to an Evaluation zPAK Option that includes the program members, documentation and control files.

Repository for File Properties

This suite of programs and documentation will provide process knowledge and technology that will collect and build a repository of information about the data files, VSAM Data Structures, Partitioned Data Sets (PDS's) and Generation Data Groups (GDG's). This example includes batch and on-line (CICS) programs. The batch is required and the on-line is optional.

Review the Documentation for this suite of program members. Link to an Evaluation zPAK Option that includes the program members, documentation and control files.

Repository for File Status Codes

The ANS/85 standard provides for a two-byte file-status-key. The first character of the file-status-key is known as status-key-1. The second character is known as status-key-2.

The combinations of possible values and their meanings are shown in the File Status Codes Documents with some comments where vendor additions or extensions may occur.

Summary

The Non-Relational Data Connection provides a suite of sample programs and reference documentation for managing VSAM Data Sets or flat, sequential files (QSAM). Techniques for creating, deleting, updating, viewing, converting and comparing are included for both VSAM and QSAM.

In the world of programming there are many ways to solve a problem. This documentation and software were developed and tested on systems that are configured for a SIMOTIME environment based on the hardware, operating systems, user requirements and security requirements. Therefore, adjustments may be needed to execute the jobs and programs when transferred to a system of a different architecture or configuration.

SIMOTIME Services has experience in moving or sharing data or application processing across a variety of systems. For additional information about SIMOTIME Services or Technologies please contact us using the information in the  Contact or Feedback  section of this document.

Software Agreement and Disclaimer

Permission to use, copy, modify and distribute this software, documentation or training material for any purpose requires a fee to be paid to SimoTime Technologies. Once the fee is received by SimoTime the latest version of the software, documentation or training material will be delivered and a license will be granted for use within an enterprise, provided the SimoTime copyright notice appear on all copies of the software. The SimoTime name or Logo may not be used in any advertising or publicity pertaining to the use of the software without the written permission of SimoTime Technologies.

SimoTime Technologies makes no warranty or representations about the suitability of the software, documentation or learning material for any purpose. It is provided "AS IS" without any expressed or implied warranty, including the implied warranties of merchantability, fitness for a particular purpose and non-infringement. SimoTime Technologies shall not be liable for any direct, indirect, special or consequential damages resulting from the loss of use, data or projects, whether in an action of contract or tort, arising out of or in connection with the use or performance of this software, documentation or training material.

Downloads and Links

This section includes links to documents with additional information that are beyond the scope and purpose of this document. The first group of documents may be available from a local system or via an Internet connection, the second group of documents will require an Internet connection.

Note: A SimoTime License is required for the items to be made available on a local system or server.

Current Server or Internet Access

The following links may be to the current server or to the Internet.

Note: The latest versions of the SimoTime Documents and Program Suites are available on the Internet and may be accessed using the icon. If a user has a SimoTime Enterprise License the Documents and Program Suites may be available on a local server and accessed using the icon.

    Explore the Assembler Connection for more examples of mainframe Assembler programming techniques and sample code.

    Explore the COBOL Connection for more examples of COBOL programming techniques and sample code.

    Explore the JCL Connection for more examples of JCL functionality with programming techniques and sample code.

    Explore Documents and Examples that Describe or Show many of the Details Involved with Application or Data Migration and the moving of an application between platforms such as a Mainframe System running ZOS and a Linux, UNIX or Windows (LUW) System running Micro Focus Enterprise Server.

    Explore the Numbers Connection for additional information about the structure and processing of numeric data items (or numeric fields).

    Explore the SQL Connection for more examples of how to create, manipulate and delete Relational Data Bases. The COBOL programs are written to compile and execute on a Windows System with SQL Server and Micro Focus Enterprise Server or an IBM Mainframe System with DB2.

    Explore An Enterprise System Model that describes and demonstrates how Applications that were running on a Mainframe System and non-relational data that was located on the Mainframe System were copied and deployed in a Microsoft Windows environment with Micro Focus Enterprise Server.

    Explore an Extended List of Software Technologies that are available for review and evaluation. The software technologies (or Z-Packs) provide individual programming examples, documentation and test data files in a single package. The Z-Packs are usually in zip format to reduce the amount of time to download.

    Explore The ASCII and EBCDIC Translation Tables. These tables are provided for individuals that need to better understand the bit structures and differences of the encoding formats.

    Explore The File Status Return Codes that are used to interpret the results of accessing VSAM data sets and/or QSAM files.

Internet Access Required

The following links will require an Internet connection.

A good place to start is The SimoTime Home Page for access to white papers, program examples and product information. This link requires an Internet Connection

Explore The Micro Focus Web Site for more information about products (including Micro Focus COBOL) and services available from Micro Focus. This link requires an Internet Connection.

Explore the GnuCOBOL Technologies available from SourceForge. SourceForge is an Open Source community resource dedicated to helping open source projects be as successful as possible. GnuCOBOL (formerly OpenCOBOL) is a COBOL compiler with run time support. The compiler (cobc) translates COBOL source to executable using intermediate C, designated C compiler and linker. This link will require an Internet Connection.

Glossary of Terms

    Explore the Glossary of Terms for a list of terms and definitions used in this suite of documents and white papers.

Contact or Feedback

This document was created and is maintained by SimoTime Technologies. If you have any questions, suggestions, comments or feedback please use the following contact information.

We appreciate hearing from you.

Company Overview

SimoTime Technologies was founded in 1987 and is a privately owned company. We specialize in the creation and deployment of business applications using new or existing technologies and services. We have a team of individuals that understand the broad range of technologies being used in today's environments. Our customers include small businesses using Internet technologies to corporations using very large mainframe systems.

Quite often, to reach larger markets or provide a higher level of service to existing customers it requires the newer Internet technologies to work in a complementary manner with existing corporate mainframe systems. We specialize in preparing applications and the associated data that are currently residing on a single platform to be distributed across a variety of platforms.

Preparing the application programs will require the transfer of source members that will be compiled and deployed on the target platform. The data will need to be transferred between the systems and may need to be converted and validated at various stages within the process. SimoTime has the technology, services and experience to assist in the application and data management tasks involved with doing business in a multi-system environment.

Whether you want to use the Internet to expand into new market segments or as a delivery vehicle for existing business functions simply give us a call or check the web site at http://www.simotime.com