Guidelines & Test Cases Getting Started, SimoTime Examples

Introduction

This document is an introduction to the moving of business processing and data between systems or the sharing of business processing and data across systems. This includes a brief discussion of alternatives and "How to" examples with links to separate documents for additional detail.

In today's world the practice of migrating and sharing data and the "processing of data" across a variety of systems has become a requirement in controlling cost, improving service levels and putting some of the control and processing functions back into the hands of the users.

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

Systems, Sub-Systems & Utilities

This section provides information and links to information about preparing an environment and running the SimoTime sample programs. The techniques used in this effort may be used as a model when moving applications and data between systems.

Hardware

The hardware used for the sample applications may be an IBM Mainframe System or a Linux, UNIX or Windows System capable of running Micro Focus Server or Studio. For individual developers the system of choice has been a dual core Laptop Computer with 4gb of memory and a 300gb hard disk running at 7200rpm. The sample programs will run on a smaller system but this configuration provides for multiple processes with very little impact on individual performance.

Operating System

The Operating System used with the sample applications may be ZOS, Linux, UNIX or Windows. Many of the sample applications were originally developed on an IBM Mainframe running OSVS or MVS and continue to run on ZOS today. Many of the sample applications have been ported to the AS/400 and continue to run in this environment today.

In the early 1990's we began porting the sample applications to a Micro Focus environment running on distributed systems. At the turn of the century all of the sample applications were ported to Windows, UNIX and Linux systems running Micro Focus.

Today, we use Windows with Micro Focus Studio and Server as the primary development and production environments. For individual developers the system of choice is Windows/7. For the User Acceptance Testing (UAT) and Production environments the system of choice is Windows Server/2008.

The SimoTime Libraries

The SimoTime suite of programs and documentation provide complementary technology to the Micro Focus environment and the process for migrating applications and data between or across systems. To obtain a copy of the SimoTime Libraries use the following link to make an email request for the Application and Data Migration Libraries.

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

There are three libraries that are required in order to access the complete suite of sample programs, utility programs and documentation.

SIMOLIBR, Utility Programs

This library (or directory) contains the utility programs and shared callable modules. SimoTime provides a zipped file that will need to be unzipped into C:\SIMOLIBR. This directory will need to be added to the system path.

Many of the programs in the SIMOLIBR directory are used to support applications that are currently running on a Mainframe System and are being deployed to Linux, UNIX and Windows Systems with Micro Focus Server. Many of the utility programs are written in Micro Focus COBOL. Therefore, a Micro Focus license is required,

SIMOSAM1, Test Programs and Data

This library (or directory) contains the sample programs. SimoTime provides a zipped file (SIMOSAM1.ZIP) that will need to be unzipped into C:\SIMOSAM1.

The programs in this directory with a few exceptions originally executed on an IBM Mainframe System. Many of the programs still execute on the Mainframe and have been ported to the Linux, UNIX and Windows Systems supported by Micro Focus Server.

SIMOWEB1, Documentation

This library (or directory) contains the documentation in an HTML or browser based format. SimoTime provides a zipped file (SIMOWEB1.ZIP) that will need to be unzipped into C:\SIMOWEB1. This directory (or library) is optional and many companies put the documentation on a server or shared drive. The entry point or home page is index.htm.

Micro Focus Enterprise Server

The obvious and basic function of Server and Studio is to run COBOL programs. The broader purpose of Enterprise Server and Enterprise Studio is to run Jobs and/or execute transactions. The Server is for the production environment and the Studio is for the development environment. The Enterprise Editions of Server and Studio (Enterprise Server/Mainframe Sub-System or ES/MSS) provide the function for submitting and executing mainframe-oriented jobs or jobs using JCL in a Linux, UNIX or Windows (LUW) environment. For the online application using CICS the ES/MSS provides for configuring a CICS Region to run in the LUW environments.

The Micro Focus Enterprise Server technology is delivered on Compact Disk (CD) or electronically. The installation process is very simple and takes less that 30 minutes. Refer to the Micro Focus documentation and online help for additional detail.

Once the Micro Focus Enterprise Server has been installed it will be necessary to configure user-oriented servers to run under control of Enterprise Server. The following sections show how to configure user-oriented servers (or Regions). Each Server configuration will focus on a functional solution. However the functions described in the individual configurations may be combined into a single server configuration where appropriate.

Install and Configure for Batch

The section will focus on the minimum items needed to configure a region (or JES sub-system) that will process mainframe-oriented jobs using Job Control Language (or JCL) to define and submit the jobs.

This link provides an example of  How to Configure a Micro Focus Server  for batch processing using JCL scripts.

Install and Configure for Online

The section will focus on the minimum items needed to configure a region that will process CICS transaction.

This link provides an example of  How to Configure a Micro Focus Server or Region  for processing CICS transactions.

Define the XA Resources using ODBC

The section will focus on the minimum items needed to configure a region that will manage the interface to an SQL Data Base.

This link provides an example of  How to Configure the XA Resources for a Micro Focus Server  that will provide support for executing COBOL programs with embedded SQL statements accessing relational tables.

Build a Catalog for the Application

When doing an "application migration" or "transferring and sharing data" between a Mainframe System and a Windows System with Micro Focus Enterprise Server it can be a challenge to create the catalog entries for a user-defined application server. The unique specifications required for Sequential Data Files, VASM Data Sets, Partitioned Data Sets and GDG Base Definitions add to the confusion.

We prefer to use Excel to manage the list of file names and properties. It is possible to have all the non-relational data files defined in a single Excel spread sheet. However, we prefer to separate the files into four categories or four separate Excel spread sheets. The first Excel spread sheet is for Partitioned Data Sets (or PDS's). The second Excel spreadsheet is for Generation Data Groups (or GDG's). The third Excel spread sheet is for standard record sequential files (both fixed and variable length records). The fourth Excel spread sheet is for VSAM Data Sets. The following provides additional detail about the four categories.

Entries for Partitioned Data Sets (PDS's)

In a mainframe batch environment the cataloging of Partitioned Data Sets (PDS'S) will probably be required prior to executing many of the batch jobs.

This link provides detailed information to Identify, Document and Create Catalog Entries for Partioned Data Sets (PDS's).  This approach uses a list of PDS Members that are managed in an Excel Spreadsheet and saved as a Comma-Separated-Values (CSV) file. This provides for a documented, repeatable process.

Entries for Generation Data Groups (GDG's)

In a mainframe batch environment the cataloging of the base for Generation Data Groups (GDG's) may be required prior to executing many of the batch jobs.

This suite of sample programs describes how to  Identify, Document and Define a Generation Data Group (GDG).  Once the GDG is defined the creation of a Generation Data Set (referred to as a generation or GDS) within the group is discussed. This provides for a documented, repeatable process.

Entries for Sequential Data Files

In a mainframe batch environment the transfer, conversion and cataloging of sequential data files may be required prior to executing many of the batch jobs.

This link provides detailed information to  Identify, Document and Create Catalog Entries for Sequential Data Files.  This approach uses a list of Sequential Data Files that are managed in an Excel Spreadsheet and saved as a Comma-Separated-Values (CSV) file. This provides for a documented, repeatable process.

Entries for VSAM Data Sets

In a mainframe batch environment the transfer, conversion and cataloging of VSAM Data Sets may be required prior to executing many of the batch jobs.

This suite of sample programs describes how to  Identify, Document and Define a Key Sequenced Data Set (VSAM, KSDS).  Once the VSAM, KSDS is identified and documented the process for creating a catalog entry and copying the data into the pre-defined directory is discussed.

Execute the User Validation Jobs

This section describes a suite of jobs and associated programs the are used to validate the installation, configuration and start-up of a Micro Focus User-Defined Server that is configured to run mainframe-oriented jobs (i.e. submit a JCL Member for execution). This server will be referred to as the JES Server.

This link provides detailed information to the  User Verification Tests for the JES Server  . This suite of test jobs starts with a simple test of the basic functions and advances step-by-step through the advanced functions.

The following sections provide a brief description of the test jobs.

Simple Job Execution using IEFBR14

This is a very simple test job (UVBR00J1.jcl) that uses IEFBR14 to return to caller. This job will test the basic functions of the JES Server's configuration.

//UVBR00J1 JOB SIMOTIME,CLASS=1,MSGCLASS=0,NOTIFY=CSIP1,USER=SIMOTIME
//* *******************************************************************
//*       UVBR00J1.JCL - a JCL Member for Batch Job Processing        *
//*       This JCL Member is provided by SimoTime Technologies        *
//*           (C) Copyright 1987-2019 All Rights Reserved             *
//*             Web Site URL:   http://www.simotime.com               *
//*                   e-mail:   helpdesk@simotime.com                 *
//* *******************************************************************
//*
//* Text   - Set Condition-Code to ZERO and return to caller
//* Author - SimoTime Technologies
//* Date   - January 24, 1996
//*
//* *******************************************************************
//* Step 1 of 1, Execute the program...
//*
//NULLSTEP EXEC PGM=IEFBR14
//*

Simple job Execution and File Creation

This is a simple test job (UVDD01J1.jcl) that will execute the SORT program and test the JES Server's configuration for accessing and sorting data files. The sorting specification are obtained by accessing a PDS Member within a PDS. It will also show the differences in the EBCDIC and ASCII collating sequencing.

//UVDD01J1 JOB SIMOTIME,CLASS=1,MSGCLASS=0,NOTIFY=CSIP1
//* *******************************************************************
//*       UVDD01J1.JCL - a JCL Member for Batch Job Processing        *
//*       This JCL Member is provided by SimoTime Technologies        *
//*           (C) Copyright 1987-2019 All Rights Reserved             *
//*             Web Site URL:   http://www.simotime.com               *
//*                   e-mail:   helpdesk@simotime.com                 *
//* *******************************************************************
//*
//* Text   - Create a Sequential Data Set on disk using IEBGENER.
//* Author - SimoTime Technologies
//* Date   - January 24, 1996
//*
//* The first job step (PREPARE) will delete a previously created
//* file. The second job step (BUILDNEW) will create a new file.
//*
//* This set of programs will run on a mainframe under MVS or on a
//* Personal Computer with Windows and Micro Focus Mainframe Express.
//*
//* *******************************************************************
//* Step 1 of 2, Delete any previously created file...
//*
//JOBSETUP EXEC PGM=IEFBR14
//SYSUT2   DD  DSN=SIMOTIME.DATA.UVFILE01,DISP=(MOD,DELETE,DELETE),
//             STORCLAS=MFI,
//             SPACE=(TRK,5),
//             DCB=(RECFM=FB,LRECL=80,DSORG=PS)
//*
//* *******************************************************************
//* Step 2 of 2, Create and populate a new QSAM file...
//*
//BUILDNEW EXEC PGM=IEBGENER
//SYSPRINT DD  SYSOUT=*
//SYSIN    DD  DUMMY
//* :....1....:....2....:....3....:....4....:....5....:....6....:....7.
//SYSUT1   DD  *
UVFILE01,RECORD,001,ABC
UVFILE01,RECORD,002.0123456789
UVFILE01,RECORD,003,ABCDEFGHIJKLMNOPQRSTUVWXYZ
UVFILE01,RECORD,004,abcdefghijklmnopqrstuvwxyz
UVFILE01,RECORD,005,9876543210
UVFILE01,RECORD,006,ZYX
/*
//SYSUT2   DD  DSN=SIMOTIME.DATA.UVFILE01,
//             DISP=(NEW,CATLG,DELETE),
//             STORCLAS=MFI,
//             SPACE=(TRK,5),
//             DCB=(RECFM=FB,LRECL=80,DSORG=PS)
//

Job Execution, Access a PDS & Sort a File

This is a simple job (UVDD01J2.jcl) that uses IEBGENER to create a test file. This job will execute the SORT program and test the JES Server's configuration for access to a PDS that is the PARMLIB. Also, it will show the differences in the EBCDIC and ASCII collating sequencing.

//UVDD01J2 JOB SIMOTIME,ACCOUNT,CLASS=1,MSGCLASS=0,NOTIFY=&SYSUID
//* *******************************************************************
//*       UVDD01J2.JCL - a JCL Member for Batch Job Processing        *
//*       This JCL Member is provided by SimoTime Technologies        *
//*           (C) Copyright 1987-2019 All Rights Reserved             *
//*             Web Site URL:   http://www.simotime.com               *
//*                   e-mail:   helpdesk@simotime.com                 *
//* *******************************************************************
//*
//* Text   - Sort a File, create a new sorted file.
//* Author - SimoTime Technologies
//* Date   - January 24, 1996
//*
//* The first job step (PREPARE) will delete a previously created
//* file. The second job step (SORTFILE) will sort records from an
//* input file and create a new file. The sorting specifications are
//* obtained from a PDS Member in a PDS.
//*
//* Note: the input file to be sorted is created by UVDD01J1.JCL
//*
//* This set of programs will run on a mainframe under MVS or on a
//* Personal Computer with Windows and Micro Focus Server.
//*
//* *******************************************************************
//* Step 1 of 2, Delete previously created files...
//*
//JOBSETUP EXEC PGM=IEFBR14
//SYSUT2   DD  DSN=SIMOTIME.DATA.UVFILES1,DISP=(MOD,DELETE,DELETE),
//             STORCLAS=MFI,
//             SPACE=(TRK,5),
//             DCB=(RECFM=FB,LRECL=80,DSORG=PS)
//*
//* *******************************************************************
//* Step 2 of 2, Sort the file...
//*
//SORTFILE EXEC PGM=SORT,COND=(0,LT),
//             REGION=1024K
//SYSIN    DD  DSN=SIMOTIME.PDS.PARMLIB(UVDD01T1),DISP=SHR
//SORTIN   DD  DSN=SIMOTIME.DATA.UVFILE01,DISP=OLD
//SORTWK01 DD  UNIT=SYSDA,SPACE=(CYL,55)
//SORTWK02 DD  UNIT=SYSDA,SPACE=(CYL,55)
//SORTWK03 DD  UNIT=SYSDA,SPACE=(CYL,55)
//SORTOUT  DD  DSN=SIMOTIME.DATA.UVFILES1,DISP=(NEW,CATLG,DELETE),
//             STORCLAS=MFI,SPACE=(TRK,5),
//             DCB=(RECFM=FB,LRECL=80,DSORG=PS)
//SYSOUT   DD  SYSOUT=*
//*

Application Processing

The suite of sample programs started out with a focus on applications that originally ran on a Mainframe System in an OSVS or MVS environment and were ported to a Linux, UNIX or Windows System with Micro Focus. Many of the sample programs are still running on ZOS and VSE Mainframe Systems today. We still maintain an approach to keep the application platform flexible. However, it is sometimes necessary to solve a problem at the system level. When this is necessary we try to create individual programs for each platform.

Micro Focus introduced their Enterprise Server in the early 2000's. Prior to Enterprise Server we had to convert JCL to Windows Command Files and/or UNIX Kornshell scripts. This was mostly a manual effort. After the announcement of Micro Focus Enterprise Server we could no longer cost justify a conversion of JCL to other scripting languages. We simply submit the JCL to Enterprise Server and it executes. However, we kept the converted CMD members as reference items for many of the sample programs.

Note: It is important to note that Micro Focus Enterprise Server does more than parse and execute JCL members. It provides a JES-Oriented Sub-System (or Job Entry System) on the LUW platforms. This includes spooling and a catalog. The JES components are the real challenge when attempting to convert JCL to CMD scripts.

Batch Processing

WIP

Batch Jobs using CMD Files

WIP

Batch Jobs using JCL Members

WIP

Check out The JCL Connection for more mainframe JCL examples.

Transaction Processing using CICS

WIP

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

Data Access Management

The objective for this section is to provide additional insight into the data transfer, share, convert and compare requirements of a mixed system complex and the data management challenges.

non-Relational Data Structures

This section describes the file structures that are available in the Micro Focus environment and how these structures map to functionally equivalent file structures on the mainframe.

This link provides additional detail for  Micro Focus Files and various Numeric Formats  being used in a multi-system complex consisting of Mainframe (z/OS), Linux, UNIX or Windows environments.

Customer Master File

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.

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.

Check out  How to Create and Populate a Customer Master File  for more information and examples.

Item or Product 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 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.

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

Check out  How to Create and Populate an Item Master File  for more information and examples.

Manage Files, Multi-System Complex

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

This link provides a repository of information for  Managing Data in a Multi-System Complex  and this includes the transfer, share, convert and compare of data between Mainframe (z/OS), Linux, UNIX and Windows Systems.

File Conversion Alternatives

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.

This link provides a repository of information for Data File Conversion Requirements and Alternatives that are available for Mainframe (z/OS), Linux, UNIX and Windows Systems.

This link provides additional information for using  The Data File Convert Utility Program  . A description of the batch interface and examples are included.

Data Validation, Alternatives & Choices

This document is an introduction or overview of the data file comparison challenges created as a result of doing an application or data migration between a Mainframe System and a Linux, UNIX or Windows (LUW) System running a Micro Focus sub-system such as Enterprise Server.

This link provides a repository of information for Data File Comparision Requirements and Alternatives that are available for Mainframe (z/OS), Linux, UNIX and Windows Systems.

This link provides additional information for using  The Data File Compare Utility Program.  This utility program runs on a Windows System with Micro Focus and will generate the COBOL source code for a program that will do a compare of two data files on a record by record basis.

File Compare, a Simple Example

WIP

Summary Totals & Record Count

WIP

Human Observation & Hex-Dump View

When a problem determination effort requires a closer look at the physical content of records within a file a hexadecimal dump capability can be very useful.

    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.

Additional Reference Materials

This section includes links to general purpose reference documentation that applies to many areas of the data management environment

File Status Codes

User programs and system utility programs that access data files have the ability to view a file status code after each I/O request. This status code is available in the ABEND routine of the user or system when an I/O operation is performed. The status code is two bytes of information indicating a normal I/O operation or an ABEND. To find out additional information a system user needs to look up the two byte status code.

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

ASCII and EBCDIC Tables

In a Linux, UNIX or Windows environment the encoding schema most widely used is ASCII. In the Mainframe environment the encoding schema is EBCDIC. When applications and/or data is being moved between systems a single conversion or reference table of the binary values for both encoding schemas is a requirement.

This conversion table is provided as a reference for ASCII and EBCDIC translation.

Process Management

WIP

Create Repository, Application Assets

WIP

Build the Load/Execute Members

Once the Infra-Structure is in place building the application is usually a simply task of compiling the source code (usually COBOL for Mainframe Legacy Applications) to create the executable or load members. For the program maintenance and unit testing the Micro Focus Studio provides a "project-oriented" interface to do the compile, test and debug functions from a Graphical User Interface. When it comes to building the entire application or suite of applications the quality control groups and/or auditors prefer a documented, automated, unattended, repeatable process that can be reviewed. To meet this requirement we provide scripted builds for the LUW platforms running Micro Focus technologies or sub-systems.

The number of programs being compiled from a single script may range from a few programs to several hundreds or even thousands of programs. The programs may be grouped into five categories.

Explore A Scripted Build for additional information about how to do an automated, unattended build of an application that was migrated from a Mainframe System.

An example of special requirements would be the way in which numeric fields are processed and stored in memory and in data files. Over the years systems have processed numbers and performed arithmetic operations in a variety of different formats. Identifying and processing this variety of numeric formats sometimes require special compiler options for programs that need to handle numeric formats outside the mainstream.

This link provides additional detail for  Micro Focus Files and various Numeric Formats  being used in a multi-system complex consisting of Mainframe (z/OS), Linux, UNIX or Windows environments.

The preceding links will describe the compiler options for all five categories.

Execute Jobs and Transactions

WIP

Monitor the Execution Processes

WIP

Review Application Execution Results

WIP

Make Adjustments

WIP

Test Cases

A suite of test cases is available to be used for regression or User Acceptance Testing (UAT). Also, the Test Cases may be used as hands on training exercises.

    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.

Summary

This document is an introduction to the moving of business processing and data between systems or the sharing of business processing and data across systems. This document may be used to assist 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 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 JCL Connection for more examples of JCL functionality with programming techniques and sample code.

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

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

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.

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