Non-Relational Data Connection  File Accessing Methods

Introduction
(Next) (Previous) (Table-of-Contents)

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 or updating are included for both VSAM and QSAM. The sample members are written to run as MVS batch jobs on an IBM mainframe or as a project with Micro Focus Mainframe Express (MFE) running on a PC with Windows. If a technique is used that is unique to the mainframe and not supported by Mainframe Express it will be noted.

Status Codes and Common Utility Programs
(Next) (Previous) (Table-of-Contents)

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 Codes, Reference Document
(Next) (Previous) (Table-of-Contents)

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, Populate a KSDS with Code Information
(Next) (Previous) (Table-of-Contents)

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.

File Status Codes, Program Example, Format and Display
(Next) (Previous) (Table-of-Contents)

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.

Utility Programs - Create, Update or Delete a File or VSAM Data Set
(Next) (Previous) (Table-of-Contents)

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.

VSAM Programming Examples
(Next) (Previous) (Table-of-Contents)

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, Keyed Sequential Data Sets (KSDS), Programming Examples
(Next) (Previous) (Table-of-Contents)

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.

VSAM, KSDS processing with a Single COBOL Program
(Next) (Previous) (Table-of-Contents)

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.

VSAM, KSDS processing using COBOL with a COBOL I/O Routine
(Next) (Previous) (Table-of-Contents)

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.

VSAM, KSDS processing using COBOL with an Assembler I/O Routine
(Next) (Previous) (Table-of-Contents)

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, Entry Sequential Data Sets (ESDS), Programming Examples
(Next) (Previous) (Table-of-Contents)

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.

VSAM, ESDS Delete, Define with JCL & Add Records using COBOL
(Next) (Previous) (Table-of-Contents)

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.

QSAM Programming Examples
(Next) (Previous) (Table-of-Contents)

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.

QSAM processing with a Single COBOL Program
(Next) (Previous) (Table-of-Contents)

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.

QSAM File processing using COBOL with a COBOL I/O
(Next) (Previous) (Table-of-Contents)

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.

QSAM processing using COBOL with an Assembler I/O Routine
(Next) (Previous) (Table-of-Contents)

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 File Format with CSV Record Content
(Next) (Previous) (Table-of-Contents)

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).

Create a New Sequential File with CSV Record Content
(Next) (Previous) (Table-of-Contents)

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.

Access an Existing Sequential File with CSV Record Content
(Next) (Previous) (Table-of-Contents)

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.

Data File Information Collection
(Next) (Previous) (Table-of-Contents)

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.

Data Allocation and Access Methods
(Next) (Previous) (Table-of-Contents)

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.

Managing Partitioned Data Sets (PDS's)
(Next) (Previous) (Table-of-Contents)

This suite of programs provides examples of how to create PDS's.

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

Generation Data Groups (GDG's)
(Next) (Previous) (Table-of-Contents)

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
(Next) (Previous) (Table-of-Contents)

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.

Alternate Index for VSAM, KSDS
(Next) (Previous) (Table-of-Contents)

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.

Sort a File
(Next) (Previous) (Table-of-Contents)

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.

SORT, Mainframe Example using JCL
(Next) (Previous) (Table-of-Contents)

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.

SORT, Mailing Labels, Postal Code Sequence
(Next) (Previous) (Table-of-Contents)

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.

SORT, Simple Examples for Mainframe and Micro Focus
(Next) (Previous) (Table-of-Contents)

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.

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, How to use a COBOL Program to call SORT
(Next) (Previous) (Table-of-Contents)

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.

The SimoCARD Series, Sequential File Access, 80-Bytes
(Next) (Previous) (Table-of-Contents)

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, White Papers
(Next) (Previous) (Table-of-Contents)

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
(Next) (Previous) (Table-of-Contents)

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
(Next) (Previous) (Table-of-Contents)

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
(Next) (Previous) (Table-of-Contents)

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)
(Next) (Previous) (Table-of-Contents)

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
(Next) (Previous) (Table-of-Contents)

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 File Transfer, Share, Convert or Compare
(Next) (Previous) (Table-of-Contents)

This section provides examples and links to documents that describes the data file transfer, convert or compare 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, download the flat sequential file from the mainframe to the PC and create a new file of a compatible format of ASCII or EBCDIC content on the PC.

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 Compare, a User's Guide
(Next) (Previous) (Table-of-Contents)

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.

Compare - Basic Function, A Simple 80/80 Compare
(Next) (Previous) (Table-of-Contents)

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.

Compare - Moderate Function, Customer File with Partial Record Compare
(Next) (Previous) (Table-of-Contents)

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.

Compare - Advanced Function, Report File Compare with Compaction and Bypass Capability
(Next) (Previous) (Table-of-Contents)

WIP

Data File Convert, a User's Guide
(Next) (Previous) (Table-of-Contents)

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.

Convert - Basic Function, A Simple 80/80 Convert
(Next) (Previous) (Table-of-Contents)

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 - Moderate Function, Customer File Conversion with Packed and Binary Data
(Next) (Previous) (Table-of-Contents)

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.

Convert - Advanced Function, Convert Fixed Field to Comma Separated Values for Excel
(Next) (Previous) (Table-of-Contents)

WIP

Convert - Miscellaneous Programs
(Next) (Previous) (Table-of-Contents)

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 File Content Conversion
(Next) (Previous) (Table-of-Contents)

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.

Convert between Line & Record Sequential, EBCDIC & ASCII
(Next) (Previous) (Table-of-Contents)

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.

Convert between Comma-Separated-Values and Fixed-Field-Lengths
(Next) (Previous) (Table-of-Contents)

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.

Calculate Record Counts and Summary Totals
(Next) (Previous) (Table-of-Contents)

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 and may be compiled and executed on an IBM Mainframe 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.

Data File Management and Manipulation with Miscellaneous Examples
(Next) (Previous) (Table-of-Contents)

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
(Next) (Previous) (Table-of-Contents)

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 and Compare Processes
(Next) (Previous) (Table-of-Contents)

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
(Next) (Previous) (Table-of-Contents)

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.

Data File Processing with Multiple Record Types
(Next) (Previous) (Table-of-Contents)

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.

Sequential Files with Variable Length Records
(Next) (Previous) (Table-of-Contents)

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.

Variable Length Records (process using Standard COBOL)
(Next) (Previous) (Table-of-Contents)

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.

Variable Length Records (using Byte-Stream I/O)
(Next) (Previous) (Table-of-Contents)

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.

Variable Length Records (Transfer, Share, Convert, Compare)
(Next) (Previous) (Table-of-Contents)

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.

Micro Focus Environment
(Next) (Previous) (Table-of-Contents)

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

File Formats for Micro Focus
(Next) (Previous) (Table-of-Contents)

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

Micro Focus, Compiler Directives
(Next) (Previous) (Table-of-Contents)

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 s permanent storage media the format of the records and their content structure must be maintained.

Micro Focus, Creating & Processing Large Files (greater than 2-gig)
(Next) (Previous) (Table-of-Contents)

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.

Micro Focus, Dynamic File Allocation
(Next) (Previous) (Table-of-Contents)

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.

Micro Focus, Populate a Catalog
(Next) (Previous) (Table-of-Contents)

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.

Micro Focus, Extract File Information from JCL
(Next) (Previous) (Table-of-Contents)

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 File
(Next) (Previous) (Table-of-Contents)

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 File.

The Customer 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 is defined in a COBOL copy file and contains text strings and various numeric formats including zoned-decimal, packed and binary.

Customer Master, Create and Populate, Small Test File
(Next) (Previous) (Table-of-Contents)

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.

Customer Master, Extract and Format Data for Excel
(Next) (Previous) (Table-of-Contents)

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.

Customer Master, Convert between EBCDIC and ASCII
(Next) (Previous) (Table-of-Contents)

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.

Customer Master, Create and Populate, Generic Name and Address
(Next) (Previous) (Table-of-Contents)

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.

Customer Master, Convert from EBCDIC to ASCII
(Next) (Previous) (Table-of-Contents)

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.

The Item Master File
(Next) (Previous) (Table-of-Contents)

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 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 is defined in a COBOL copy file and contains text strings and various numeric formats including zoned-decimal, packed and binary.

Item Master, Create and Populate
(Next) (Previous) (Table-of-Contents)

This program suite provides an example of how to create and populate the Item 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 item 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.

Item Master, Extract and Format Data for Excel
(Next) (Previous) (Table-of-Contents)

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.

Item Master, Convert between EBCDIC and ASCII
(Next) (Previous) (Table-of-Contents)

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.

Repository Management Programs
(Next) (Previous) (Table-of-Contents)

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
(Next) (Previous) (Table-of-Contents)

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
(Next) (Previous) (Table-of-Contents)

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
(Next) (Previous) (Table-of-Contents)

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
(Next) (Previous) (Table-of-Contents)

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 or updating are included for both VSAM and QSAM.

This document may be used as a tutorial for new programmers or as a quick reference for experienced programmers. In the world of programming there are many ways to solve a problem. This document and the links to other documents are intended to provide a choice of alternatives.

Software Agreement and Disclaimer
(Next) (Previous) (Table-of-Contents)

Permission to use, copy, modify and distribute this software, documentation or training material for any purpose requires a fee to be paid to SimoTime Enterprises. 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 Enterprises.

SimoTime Enterprises 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 Enterprises 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 to Similar Pages
(Next) (Previous) (Table-of-Contents)

This section includes links to documents with additional information that is beyond the scope and purpose of this document. The first sub-section requires an internet connection, the second sub-section references locally available documents.

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

Downloads and Links, Internet Access Required
(Next) (Previous) (Table-of-Contents)

The following links will require an internet connect.

A good place to start is The SimoTime Home Page for access to white papers, program examples and product information.

Explore The COBOL Connection in the SimoTime Library for more examples of COBOL programming techniques and sample code.

explore The CICS Connection for more examples of mainframe CICS coding techniques and sample code.

Explore The JCL Connection in the SimoTime Library for more examples of JCL coding techniques and batch utility programs.

Explore The Numbers Connection in the SimoTime Library for more examples of programs and documentation that describe and demonstrate techniques for understanding and processing the various numeric field formats used in a mainframe environment.

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 to interpret the results of accessing VSAM data sets and QSAM files.

Explore The Micro Focus Web Site for more information about products and services available from Micro Focus.

Downloads and Links, Local Access
(Next) (Previous) (Table-of-Contents)

The following links may be accessible without an internet connection.

Explore The File Status Return Codes to interpret the results of accessing VSAM data sets and QSAM files.

Glossary of Terms
(Next) (Previous) (Table-of-Contents)

Check out  The SimoTime Glossary  for a list of terms and definitions used in the documents provided by SimoTime.

Comments, Suggestions or Feedback
(Next) (Previous) (Table-of-Contents)

This document was created and is maintained by SimoTime Enterprises.

If you have any questions, suggestions, comments or feedback please call or send an e-mail to: helpdesk@simotime.com

We appreciate hearing from you.

Company Overview
(Next) (Previous) (Table-of-Contents)

Founded in 1987, SimoTime Enterprises 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. This includes the smallest thin client using the Internet and the very large mainframe systems. There is more to making the Internet work for your company's business than just having a nice looking WEB site. It is about combining the latest technologies and existing technologies with practical business experience. It's about the business of doing business and looking good in the process. 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.

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