Request for Information
Application & Data Migration Requirements
  Table of Contents  v-16.01.01 - rfimodel.htm 
  Introduction
  Requirements and Requests
  R-1, System and Software Architecture
  R-1.01, Batch Processing
  R-1.02, Transaction Processing
  R-1.03, Non-relational Data Structures
  R-1.04, Relational Data Base Processing
  R-1.05, Shared Functionality
  R-2, Integration Alternatives
  R-2.01, Third Party Interfaces
  R-2.02, In-house Programs & Documents
  R-3, New Functions & System Changes
  R-4, Share Strategic Advantages & Value of Proposed System
  R-5, Summary
  Proposal and Responses
  P-1, System and Software Architecture
  P-1.01, Batch Processing
  P-1.01.01, Submit a Simple Batch Job
  P-1.01.02, Submit a Job - IEFBR14, SORT, COBOL & Work Files
  P-1.01.03, Submit a Job - Conditional Processing of JES/2 & JES/3
  P-1.02, Transaction Processing
  P-1.02.01, Load of a non-Executable Member
  P-1.02.02, WIP
  P-1.02.03, WIP
  P-1.02.04, WIP
  P-1.02.05, Inquiry & Possible Update
  P-1.02.06, Online, Submit a Batch Job to the Internal Reader (INTRDR)
  P-1.03, Non-relational Data Structures
  P-1.03.01, Data Structures
  P-1.03.02, Impact of ASCII & EBCDIC Collating Sequences
  P-1.03.03, Maintaining Mainframe Numeric Integrity
  P-1.03.04, Populate a Catalog
  P-1.03.05, Create & Populate a Customer Master File for Test
  P-1.03.06, Make a Back-up Copy of the Customer Master
  P-1.03.07, Describe & Demonstrate Dynamic File Allocation
  P-1.03.08, WIP
  P-1.04, Relational Data Base Processing
  P-1.04.01, Load a Relational Table with Customer Information
  P-1.04.02, WIP
  P-1.05, Shared Functionality
  P-1.05.01, Callable Assembler Module Replace
  P-2, Integration Alternatives
  P-2.01, Third Party Interfaces
  P-2.01.01, WIP
  P-2.02, In-house Programs & Documents
  P-2.02.01, WIP
  P-3, Identify New Functions & Changes for Migration & System
  P-3.01, Data File Conversion
  P-3.02, File transfer using FTP
  P-3.03, COBOL Source Code Changes, Embedded Hexadecimal
  P-3.04, Changes to JCL and/or SORT Control Cards
  P-3.05, Application Programmer's Notes
  P-3.05.01, Application Programmer's Notes, Source Editor, Columns
  P-3.05.02, Application Programmer's Notes, Column Selection
  P-3.05.03, Application Programmer's Notes, Case Conversion
  P-3.05.04, Application Programmer's Notes, Bookmark a Field Name
  P-3.05.05, Application Programmer's Notes, Integrate User Documents & Tools
  P-3.05.06, Application Programmer's Notes, WIP
  P-4, Strategic Advantage & Value of Proposed Environment
  P-4.01, WIP
  P-5, Summary
  P-5.01, WIP
  Test Cases
  Test Cases, Preparation and Review
  Prepare, Demonstrate how to Install and Configure the Application Environment
  Review, Demonstrate a Process for Identifying Changes to Data
  Test Cases, Administrative, System and Shared Tasks
  Administration, Show Documentation and Demonstrate User Interface
  System, Demonstrate Debug Capabilities for Online Program Accessing Relational Data
  System, Demonstrate a Scripted Application Build Process for Development, Test and Production
  Shared, Demonstrate a Process for Migrating/Replacing a Callable Assembler Routine
  Test Cases, Data Requirements
  Data Requirements, Describe Data Transfer Approach using FTP
  Data Requirements, Demonstrate How to Convert EBCDIC to ASCII
  Data Requirements, Create a Customer File (VSAM, KSDS) and Populate with Test Data
  Data Requirements, Load a Relational Data Base with a Customer Table
  Test Cases, Batch Requirements
  Batch, Demonstrate How to Submit a Job via the Internal Reader
  Batch, Demonstrate a Regression Test Processing Cycle
  Test Cases, Transaction Requirements
  Online, Demonstrate a Menu Screen Navigation Capability
  Online, Demonstrate a View/Update Capability using VSAM, KSDS
  Online, Demonstrate a Transaction to Submit a Job to Batch
  Summary
  Software Agreement and Disclaimer
  Downloads and Links
  Current Server or Internet Access
  Internet Access Required
  Glossary of Terms
  Comments or Feedback
  Company Overview
The SimoTime Home Page 

Table of Contents Previous Section Next Section Introduction

The primary challenge (or adventure) of adopting new technology is to identify its capabilities and new approaches for addressing the user requirements and efficiently executing the tasks. Using older (and familiar) technology in a stable environment a user can execute tasks habitually and quickly. A user can focus on the business objectives without being distracted with the mechanics of using a new (and unfamiliar) technology.

The purpose of this Request for Information (RFI) is to gather technical information to validate the functionality, usability, training and practicality of deploying a suite of batch and online applications that are currently running in a ZOS Mainframe environment to a Windows, Linux and/or UNIX environment. The requestors have technical backgrounds and are the team managers, system programmers, lead application programmers and personnel from the User Acceptance Testing (UAT) group.

The key to using a new technology or a new development interface and making the experience an adventure instead of an annoying challenge is knowledge, training and readily available support. This is especially important during the initial stages of an application migration project.

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-2018
SimoTime Technologies and Services
All Rights Reserved

Table of Contents Previous Section Next Section Requirements and Requests

The purpose of this section of the document is to provide a quick overview with a list of requests that should validate the practicality of moving a suite of applications that are currently running on a Mainframe System to a Windows System. Currently, the File Transfer Protocol (FTP) is used on the mainframe for data exchanges with other systems. The proposed solution should leverage this capability.

The process for installing system-oriented software on the mainframe is elongated and time consuming. Additional expenditures for mainframe software and services should be avoided. It is acceptable to install and execute application-oriented programs. For example, the approval process for new COBOL compiles and executes in a batch environment can be accomplished in a short time frame.

The following outline provides an overview of the requests by technical category or group.

1. System and Software Architectures
1.1. Batch Processing
1.2. Online Processing
1.3. Non-relational Data Structures
1.4. Relational Data Base Processing
1.5. Shared Functionality
2. Integration Alternatives
2.1. Third Party Interfaces
2.2. In-house Programs & Documentation
3. New Functions & System Changes
4. Share Strategic Advantages & Value of Proposed System
5. Summary

Table of Contents Previous Section Next Section R-1, System and Software Architecture

This section defines the request for additional information about the System and Software requirements and architectures.

Table of Contents Previous Section Next Section R-1.01, Batch Processing

A suite of COBOL-Oriented applications that do batch processing using JCL and including JES Utility programs is currently running on a Mainframe System with ZOS.

Describe the setup and/or configuration process for creating the environment to execute batch jobs that were designed and built to execute in a mainframe batch environment.

Note: Since many of the test cases in each of the groups are dependent on data and a catalog it is recommended that Request Group 3 be performed to create the Test Data and the catalog entries.

1 Describe and demonstrate the submission and execution of a simple batch job that uses IEFBR14, IEBGENER and SORT to create and process a sequential file. Describe and demonstrate how to review the results of the job execution.
2 Describe and demonstrate the submission and execution of a batch job that uses IEFBR14, COBOL and SORT to access a Customer Master File that is a VSAM, KSDS and produce four-across mailing labels. Describe and demonstrate how to review the results of the job execution. Describe and demonstrate how to debug the COBOL programs using an interactive source debugging interface.
3 Describe and demonstrate the submission and execution of a batch job that uses the conditional processing capabilities of JES/2 and JES/3.
4 Describe and demonstrate the submission and execution of a batch job that uses PROC's. Describe and demonstrate how to review the results of the job execution.
5 Describe and demonstrate the submission and execution of a batch job that does parameter substitution and uses PROC's with overrides. Describe and demonstrate how to review the results of the job execution.
6 Describe and demonstrate the submission and execution of a batch job that uses the JCL INCLUDE function. Describe and demonstrate how to review the results of the job execution.
7 Describe and demonstrate the submission and execution of a secondary batch job to the internal reader (INTRDR) from a primary job submitted to the JES input queue. Describe and demonstrate how to review the results of the job execution.
8 The batch applications have a few jobs that execute REXX programs. Describe and demonstrate the execution of a batch job that executes a REXX program.
9 WIP
  Batch Processing, List of Requests

Table of Contents Previous Section Next Section R-1.02, Transaction Processing

A suite of COBOL-Oriented applications that do online transaction processing is currently running on a Mainframe System with ZOS and CICS.

Describe the setup and/or configuration process for creating the environment to execute online transactions that were designed and built to execute in a mainframe, CICS environment.

Note: Since many of the test cases in each of the groups are dependent on data and a catalog it is recommended that Request Group 3 be performed to create the Test Data and the catalog entries.

1 The online application uses a technique to do an EXEC CICS LOAD of a non-executable member to load data tables into memory. The non-executable members are written in Mainframe Assembler and compile as non-executable load members. Please describe and demonstrate this process for the proposed environment.
2 Describe and demonstrate the interactive maintenance and support for BMS screens. Describe and demonstrate a scripted and automated process for creating the COBOL copy files and load members from the BMS source members.
3 Describe and demonstrate the process for executing transactions that use "menu screens" to navigate through the application functions. The menu screens should be created using BMS and accessed using a 3270 emulator.
4 Describe and demonstrate the process for executing transactions the do simple inquires limited to viewing without updates and using a 3270 emulator.
5 Describe and demonstrate the process for executing transactions the do record inquiries and possibly update existing records or add new records to a Customer Master File (VSAM,KSDS) using a 3270 emulator.
6 Describe and demonstrate how to submit a batch job to the Internal Reader (INTRDR) from within a CICS transaction. Describe and demonstrate how to review the results of the job execution.
7 WIP
8 WIP
9 WIP
  Online Processing, List of Requests

Table of Contents Previous Section Next Section R-1.03, Non-relational Data Structures

The batch and online applications process traditional sequential files (both fixed-length and variable-length records). Processing VSAM data sets will be required. The Mainframe environment uses an EBCDIC encoding schema. The preferred encoding schema for the proposed environment is ASCII. Please describe the process for making this transition or conversion.

A solution that would provide the flexibility of doing the data conversion on a Mainframe System, a Windows System, a Linux System or a UNIX System would be preferred.

1 Describe the Data Structures that will be supported in the proposed system. Also, describe the process for doing the file transfers and file format conversions.
2 Describe the impact of the differences in the collating sequences of EBCDIC and ASCII.
3 Describe the capability and impact of maintaining mainframe numeric integrity with the various numeric formats that are used on the mainframe (i.e. Zoned Decimal, Packed Decimal and Binary)
4 The mainframe is heavily dependent on a catalog. Please describe how this will be managed in the proposed environment. This should include the process for creating the entries for PDS's and GDG's.
5 Describe and demonstrate the creation of a Customer Master File that is a VSAM, KSDS. Populate the file with generic test data. The number of records to be placed in the file should be determined by an external control file.
6 Use IDCAMS to make a back-up copy of the Customer Master File.
7 WIP
  Data Management, List of Requests

Table of Contents Previous Section Next Section R-1.04, Relational Data Base Processing

The batch and online applications may process relational tables. The preferred choice of a Relational Data Base Management System (RDBMS) for a non-mainframe environment has not yet been determined. The goal of this request is to gain a better understanding of how relational data will be integrated into the proposed system.

Describe and demonstrate the setup and/or configuration process for connecting to a Relational Data Base.

1 Describe and demonstrate how to read a Customer Master File (VSAM, KSDS) and load a relational table with the customer information.
2 Describe and demonstrate how to sequentially read a Customer Table and write to a sequential file using Cursor Processing.
3 WIP
  Relational Data Base Processing, List of Requests

Table of Contents Previous Section Next Section R-1.05, Shared Functionality

WIP

1 Describe and demonstrate the process for replacing a callable Assembler Module with a functionally equivalent program. The assembler program is provided and does bit manipulation and is callable from a COBOL program.
2 Describe and demonstrate the process for tracking changes to the Customer Master File. This will be a requirement for the application migration effort and is an ongoing requirement for the development and user acceptance test environment.
3 WIP
  Shared Functionality, List of Requests

Table of Contents Previous Section Next Section R-2, Integration Alternatives

WIP

Table of Contents Previous Section Next Section R-2.01, Third Party Interfaces

WIP

1 The batch applications use SYNCSORT for large files. Describe and demonstrate how this will work in the proposed environment.
2 WIP
  Third Party, List of Requests

Table of Contents Previous Section Next Section R-2.02, In-house Programs & Documents

WIP

1 The application currently uses an in-house utility program to extract information from sequential files and VSAM data sets. The parameters for selection use the field name as defined in a COBOL copy file or program. The source code for this utility program is no longer available. Describe and demonstrate how this will be accomplished in the proposed environment.
2 WIP
  In-house Programs and Documentation, List of Requests

Table of Contents Previous Section Next Section R-3, New Functions & System Changes

WIP

1 Describe the proposed File Format and File Content conversion process. The preferred choice is a conversion process that may be executed on ZOS, Windows, Linux and UNIX.
2 Describe the proposed process for transferring data files and VSAM data sets using File Transfer Protocol (FTP). The data will contain packed and binary values.
3 Identify changes required to COBOL source code. The application uses callable members to load and access data table and the data table have hexadecimal characters defined in the source members.
4 The application uses the SORT program to do "case insensitive" sorts. Please describe and demonstrate how will this be handled in the proposed environment.
5 Identify, describe and be prepared to demonstrate the use of the source code editor and the common tasks that are performed by an application programmer in their daily work.
Note: Programmers are very familiar with the current technology. They perform the necessary technical tasks involved without thought (or out of habit) while they are allow to focus the majority of their efforts on the business objective. The primary purpose of this task is to better understand what is required to adapt to the new technology.
6 WIP
  New Functions for Migration and/or Proposed System, List of Requests

Table of Contents Previous Section Next Section R-4, Share Strategic Advantages & Value of Proposed System

WIP

1 WIP
2 WIP
  Share Strategic Advantages & Value of Proposed System, List of Requests

Table of Contents Previous Section Next Section R-5, Summary

WIP

Table of Contents Previous Section Next Section Proposal and Responses

A suite of COBOL-Oriented applications can be transferred to a Windows System and executed using Micro Focus Studio for the Development environment and Micro Focus Server for the Production environment.

WIP

Explore The Enterprise System Model for additional information about defining, creating and managing the Environments, Processes, Functions and Data that are needed (required) to expand the platform flexibility and allow a business application currently running on a mainframe system to run on a Windows, UNIX or Linux system using Micro Focus Server Enterprise Edition.

Table of Contents Previous Section Next Section P-1, System and Software Architecture

WIP

Table of Contents Previous Section Next Section P-1.01, Batch Processing

A Batch Server can be configured in a Micro Focus environment. The will provide the capability of submitting user-coded JCL Members that will be accepted into a job queue and executed by a job initiator.

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

Table of Contents Previous Section Next Section P-1.01.01, Submit a Simple Batch Job

This is a suite of very simple batch jobs that are used to show the job submission and job review capabilities of Micro Focus 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.

WIP

Table of Contents Previous Section Next Section P-1.01.02, Submit a Job - IEFBR14, SORT, COBOL & Work Files

This is a multi-step jobs that reads a VSAM, KSDS and produces a sequential file that is sorted into postal code sequence. The sorted file is then used to produce a sequential file that is used to print the mailing labels.

This job will Read, Sort and Produce Four-Across Mailing Labels. The results of the job execution can be viewed from the Micro Focus spooled output for the batch server.

Table of Contents Previous Section Next Section P-1.01.03, Submit a Job - Conditional Processing of JES/2 & JES/3

This is a multi-step job. Each step executes a COBOL program that displays a message and sets the Condition Code base on the parameter specified in the JCL member.

This job will Execute Job Steps Based on Condition Code. The JES/2 style of coding used a "COND=" keyword and parameter. JES/3 introduced the IF, THEN and ELSE syntax.

Table of Contents Previous Section Next Section P-1.02, Transaction Processing

An Online Transaction Server can be configured to provide a CICS-oriented region running in a Micro Focus environment. This will provide the capability of executing online application transactions and programs that use EXEC CICS syntax and are using a 3270 interface with screens defined with BMS Members.

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

Table of Contents Previous Section Next Section P-1.02.01, Load of a non-Executable Member

Micro Focus Server has the ability to load a non-executable load member. However, Micro Focus Studio does not have the capability to read data definitions that are coded using the mainframe assembler syntax and produce an ASCII-encoded non-executable load member. This function is provided by a third party vendor.

Please review the generator for Creating a non-Executable Load Member that has source code input that is mainframe assembler data definitions and can produce either an EBCDIC or ASCII encoded output module.

Table of Contents Previous Section Next Section P-1.02.02, WIP

WIP

Table of Contents Previous Section Next Section P-1.02.03, WIP

WIP

Table of Contents Previous Section Next Section P-1.02.04, WIP

WIP

Table of Contents Previous Section Next Section P-1.02.05, Inquiry & Possible Update

Describe and demonstrate the process for executing transactions the do record inquiries and possibly update existing records or add new records to a customer Master File (VSAM,KSDS) using a 3270 emulator.

The following uses a suite of COBOL programs and BMS map sets to display screens to a 3270 device. The screens will provide for the entry of a customer number and then display the customer information. The programs (or transactions) will provide a function for only viewing and a function for viewing with possible update to existing records or the adding of new records.

Explore  How to Read a VSAM, KSDS of Customer Data  using a COBOL program with embedded "EXEC CICS" statements to view records in a VSAM, Key-Sequenced-Data-Set (KSDS). This program will only read the records. Updating, adding or deleting records is not allowed.

Explore  How to Access a VSAM, KSDS of Customer Data  using a COBOL program with embedded "EXEC CICS" statements to view, update or insert a record in a VSAM, Key-Sequenced-Data-Set (KSDS).

Table of Contents Previous Section Next Section P-1.02.06, Online, Submit a Batch Job to the Internal Reader (INTRDR)

Describe and demonstrate the approach used by the application that submits a job to the Internal Reader (INTRDR).

Explore How to Submit a Batch Job from a CICS Application using a COBOL program and the Internal Reader (INTRDR).

Table of Contents Previous Section Next Section P-1.03, Non-relational Data Structures

WIP

Table of Contents Previous Section Next Section P-1.03.01, Data Structures

WIP

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.

Table of Contents Previous Section Next Section P-1.03.02, Impact of ASCII & EBCDIC Collating Sequences

WIP

Explore  the differences between the EBCDIC and ASCII collating sequences.  This suite of programs and documentation provides an example of possible logic failures in COBOL source code. This example is in COBOL but the failure would occur with other languages.

Table of Contents Previous Section Next Section P-1.03.03, Maintaining Mainframe Numeric Integrity

WIP

Please review the Numeric Formats that are typically used by applications running in a mainframe environment. The numeric formats are supported when the application is executed on a Window, Linux or UNIX system with Micro Focus.

Table of Contents Previous Section Next Section P-1.03.04, Populate a Catalog

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, VSAM Data Sets, Partitioned Data Sets and GDG Base Definitions add to the confusion. This document describes a possible solution to this challenge.

This link provides a starting point to Populate a Catalog for Micro Focus Enterprise Server.

Table of Contents Previous Section Next Section P-1.03.05, Create & Populate a Customer Master File for Test

Use IDCAMS to DELETE/DEFINE a VSAM, KSDS for the Customer Master File.

Table of Contents Previous Section Next Section P-1.03.06, Make a Back-up Copy of the Customer Master

Use IDCAMS to Copy (or REPRO) the Customer Master. This back-up copy will be used by the follow-on test cases to do a file compare and identify changes.

Explore  How to Create a New or Update an Existing Customer Data Set  that is a VSAM Key-Sequenced-Data-Set (KSDS). This document will describe the jobs and programs that create and maintain a Customer Data Set. The program will run on an IBM Mainframe System or a Linux, UNIX or Windows System with Micro Focus COBOL Support.

Table of Contents Previous Section Next Section P-1.03.07, Describe & Demonstrate Dynamic File Allocation

Execute a COBOL program in a batch job that does dynamic file allocation.

This link will describe and demonstrate the Dynamic File Allocation process for a batch job running in a Micro Focus Enterprise Server environment.

Table of Contents Previous Section Next Section P-1.03.08, WIP

WIP

Table of Contents Previous Section Next Section P-1.04, Relational Data Base Processing

A Micro Focus Server can be configured to connect and provide access to a relational data base. This will provide the capability of executing COBOL programs that use EXEC SQL syntax.

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.

WIP

Table of Contents Previous Section Next Section P-1.04.01, Load a Relational Table with Customer Information

WIP

This link will describe and demonstrate how to Load Data or Insert Rows into a Relational table using Customer information that is accessed from a VSAM Data Set.

Table of Contents Previous Section Next Section P-1.04.02, WIP

WIP

Table of Contents Previous Section Next Section P-1.05, Shared Functionality

WIP

Table of Contents Previous Section Next Section P-1.05.01, Callable Assembler Module Replace

The callable assembler routine that does bit manipulation can be replaced with a callable COBOL program that provides the functionally equivalent results. This alternative will work on the mainframe or in an Windows, Linux or UNIX environment with Micro Focus. The following documents provide additional detail.

Please review the Callable Assembler Module that does bit manipulation

Please review the Callable COBOL Program that does bit manipulation

Table of Contents Previous Section Next Section P-2, Integration Alternatives

WIP

Table of Contents Previous Section Next Section P-2.01, Third Party Interfaces

Table of Contents Previous Section Next Section P-2.01.01, WIP

WIP

Table of Contents Previous Section Next Section P-2.02, In-house Programs & Documents

Table of Contents Previous Section Next Section P-2.02.01, WIP

WIP

Table of Contents Previous Section Next Section P-3, Identify New Functions & Changes for Migration & System

Table of Contents Previous Section Next Section P-3.01, Data File Conversion

WIP

Table of Contents Previous Section Next Section P-3.02, File transfer using FTP

WIP

Table of Contents Previous Section Next Section P-3.03, COBOL Source Code Changes, Embedded Hexadecimal

WIP

Table of Contents Previous Section Next Section P-3.04, Changes to JCL and/or SORT Control Cards

WIP

Table of Contents Previous Section Next Section P-3.05, Application Programmer's Notes

WIP

Table of Contents Previous Section Next Section P-3.05.01, Application Programmer's Notes, Source Editor, Columns

Having access to user documentation and tools with a simple point-and-click action from within Visual Studio can be very helpful in understanding and working in a development environment and assisting in what is required to build, test and deploy a mainframe centric application to a production environment on a Windows, UNIX or Linux platform. Using the "External Tools" option from the Microsoft Visual Studio toolbar a user may configure Hyperlinks to user-oriented tools and documents.

Table of Contents Previous Section Next Section P-3.05.02, Application Programmer's Notes, Column Selection

The ability to select a column of text is available in the Visual Studio. Hold the "alt-key" and use the mouse to select the column of text.

Table of Contents Previous Section Next Section P-3.05.03, Application Programmer's Notes, Case Conversion

The ability to highlight text (by line, column or string) is available in the Visual Studio. From the toolbar select the "Edit" option, from drop-down select "Advanced" and then select "Makeupper Case" or "Makelower Case". The keyboard options are "Ctrl+shift+U" or "ctrl+U" for upper or lower case.

Table of Contents Previous Section Next Section P-3.05.04, Application Programmer's Notes, Bookmark a Field Name

The capability of identifying a field by name and quickly finding all occurrences may be accomplished by using the Book Marking capability in Visual Studio. Use the "Quick Find" to specify a field name and then use the "Bookmark All" button to identify all occurrences. By clicking on the item in the bookmark list a user can easily navigate to the line of code in a source member.

Table of Contents Previous Section Next Section P-3.05.05, Application Programmer's Notes, Integrate User Documents & Tools

Having access to user-oriented documentation and tools with a simple point-and-click action from within Visual Studio can be very helpful in understanding and working in a development environment and assisting in what is required to build, test and deploy a mainframe centric application to a production environment on a Windows, UNIX or Linux platform. Hyperlinks to user-oriented documents and tools may be configured in Microsoft Visual Studio.

Select "Tools" from the Toolbar and then select "External Tools" from the drop down menu. The following shows the entries for creating a link to the documentation for the Mainframe System Model.

Label Text
Title Mainframe System Model
Command c:\Program Files\Internet Explorer\IEXPLORE.EXE
Arguments C:\AC2011\SP11\DEVL\HTML\simsam01.htm
Initial Directory C:\AC2011\SP11\DEVL\HTML
  External Tools, Entries for a Mainframe System Model

Table of Contents Previous Section Next Section P-3.05.06, Application Programmer's Notes, WIP

WIP

Table of Contents Previous Section Next Section P-4, Strategic Advantage & Value of Proposed Environment

Table of Contents Previous Section Next Section P-4.01, WIP

WIP

WIP

Table of Contents Previous Section Next Section P-5, Summary

Table of Contents Previous Section Next Section P-5.01, WIP

WIP

Table of Contents Previous Section Next Section Test Cases

The purpose of this section of the document is to define a set of test cases that will provide the preliminary information to determine and document the effort involved in migrating a suite of application programs from a Mainframe System to a Windows System using Micro Focus Studio, Enterprise Edition with the Microsoft Visual Studio Interface.

Table of Contents Previous Section Next Section Test Cases, Preparation and Review

The primary objective of this group of test cases is to understand the approach and effort of architecting and creating a system environment for receiving the applications. A secondary objective is to understand the effort involved with installing and configuring the necessary software.

Table of Contents Previous Section Next Section Prepare, Demonstrate how to Install and Configure the Application Environment

Provide a document that describes how the environment is architected to execute the test cases. If this environment is significantly different than a deployed development, test and production environment please explain the differences.

Table of Contents Previous Section Next Section Review, Demonstrate a Process for Identifying Changes to Data

Reviewing the results of a regression test is typically accomplished by comparing the output of the job execution in the new environment with the same job execution on the mainframe. Please describe the approach that will be used in the test cases. Also, we would like the capability of doing a file compare on the Mainframe, Windows, UNIX or Linux using the same proposed approach.

Table of Contents Previous Section Next Section Test Cases, Administrative, System and Shared Tasks

The objective of this group of test cases is to gain a basic understanding and insight into the tasks that are required to support the application environment executing on a Windows, UNIX or Linux platform.

Table of Contents Previous Section Next Section Administration, Show Documentation and Demonstrate User Interface

The intent of this test case is to provide an initial familiarity with the execution environment for the batch and online environments.

Table of Contents Previous Section Next Section System, Demonstrate Debug Capabilities for Online Program Accessing Relational Data

The intent of this test case is to provide an introduction to the configuration of a relational data base and the subsequent access to the data base in a development and debugging environment.

Table of Contents Previous Section Next Section System, Demonstrate a Scripted Application Build Process for Development, Test and Production

Describe and demonstrate the process that will do an build of a development, test and/or production application or group of applications. The intent of this test case is to create an application build process that may be scheduled and executed without operator intervention. The process should write information to a log file for both normal and abnormal results.

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.

Table of Contents Previous Section Next Section Shared, Demonstrate a Process for Migrating/Replacing a Callable Assembler Routine

Describe and demonstrate the process that will do an build of a development, test and/or production application or group of applications. The intent of this test case is to create an application build process that may be scheduled and executed without operator intervention. The process should write information to a log file for both normal and abnormal results.

Explore COBOL calls Assembler for Bit Manipulation for an example of a COBOL program calling an Assembler routine that does bit manipulation.

Explore COBOL does Bit Manipulation for an example of a COBOL program calling a COBOL routine that does bit manipulation.

Table of Contents Previous Section Next Section Test Cases, Data Requirements

The objective of this group of test cases is to gain an understanding of the initial efforts to transfer, share, convert and/or compare data between an EBCDIC-encoded Mainframe environment and an ASCII-encoded LUW environment while maintaining mainframe numeric integrity and managing to the requirements of the various file formats.

Table of Contents Previous Section Next Section Data Requirements, Describe Data Transfer Approach using FTP

WIP

Table of Contents Previous Section Next Section Data Requirements, Demonstrate How to Convert EBCDIC to ASCII

WIP

Table of Contents Previous Section Next Section Data Requirements, Create a Customer File (VSAM, KSDS) and Populate with Test Data

WIP

Table of Contents Previous Section Next Section Data Requirements, Load a Relational Data Base with a Customer Table

WIP

Table of Contents Previous Section Next Section Test Cases, Batch Requirements

The objective of this group of test cases is to gain an understanding of the effort and identify possible changes required to move a specific set of batch-oriented applications that leverage the functions of JES/2 and JES/3 from a mainframe environment to a Windows environment.

Table of Contents Previous Section Next Section Batch, Demonstrate How to Submit a Job via the Internal Reader

The following two jobs (JCL Members) will submit a job to the Internal Reader.

This document describes how to use IEBGENER to submit jobs to the Internal Reader (INTRDR).

This document describes how to use a batch COBOL program to submit jobs to the Internal Reader (INTRDR).

Table of Contents Previous Section Next Section Batch, Demonstrate a Regression Test Processing Cycle

This suite of programs is used to describe how to create a new VSAM, Key-Sequenced-Data-Set (KSDS with customer information) at the start of a regression test process and validate the changes made to the customer data set at the end of a regression test process. Also included are the jobs to make changes to the customer data set and then identify the changes by doing a file compare with a copy of the original customer data set.

Explore  How to Create a Customer Data Set and Monitor Changes  that are made by various application processing cycles. The change monitoring is accomplished by doing a record-by-record compare of the master file with a copy that was created prior to the application processing cycles.

Table of Contents Previous Section Next Section Test Cases, Transaction Requirements

The objective of this group of test cases is to describe and demonstrate how to migrate an application that is currently running in a CICS environment on a mainframe to an LUW environment. Once the application is migrated the transactions will be executed in a Windows environment.

Table of Contents Previous Section Next Section Online, Demonstrate a Menu Screen Navigation Capability

This test case uses a suite of COBOL programs and BMS map sets to display menu screens and transfer control to transactions/programs that will perform various application and utilitarian functions such as links between menu programs and data file inquiry or update programs.

This example uses a suite of COBOL programs and BMS mapsets to display menu screens and transfer control to programs that will perform various application and utilitarian functions such as links between menu programs and data file inquiry or update programs.

Table of Contents Previous Section Next Section Online, Demonstrate a View/Update Capability using VSAM, KSDS

This test case uses a suite of COBOL programs and BMS map sets to display screens to a 3270 device. The screens should provide for the entry of a customer number and then display the customer information. The programs (or transactions) should provide a function for only viewing and a function for viewing with possible update to existing records or the adding of new records.

Explore  How to Read a VSAM, KSDS of Customer Data  using a COBOL program with embedded "EXEC CICS" statements to view records in a VSAM, Key-Sequenced-Data-Set (KSDS). This program will only read the records. Updating, adding or deleting records is not allowed.

Explore  How to Access a VSAM, KSDS of Customer Data  using a COBOL program with embedded "EXEC CICS" statements to view, update or insert a record in a VSAM, Key-Sequenced-Data-Set (KSDS).

Table of Contents Previous Section Next Section Online, Demonstrate a Transaction to Submit a Job to Batch

This test case will describe and validate the approach used by the application that submits a job to the Internal Reader (INTRDR) will work in the LUW environment.

Explore How to Submit a Batch Job from a CICS Application using a COBOL program and the Internal Reader (INTRDR).

Table of Contents Previous Section Next Section Summary

The key to using a new technology or a new development interface and making the experience an adventure instead of an annoying challenge is knowledge, training and readily available support. 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 greater awareness of the Data Management and Application Processing alternatives.

The 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 send an e-mail to: helpdesk@simotime.com or call 415 883-6565. We appreciate hearing from you.

Table of Contents Previous Section Next Section 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.

Table of Contents Previous Section Next Section 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.

Table of Contents Previous Section Next Section 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 Link to Internet 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 Link to Server icon.

Link to Internet   Link to Server   Explore the COBOL Connection for more examples of COBOL programming techniques and sample code.

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

Link to Internet   Link to Server   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.

Link to Internet   Link to 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.

Link to Internet   Link to Server   Explore The File Status Return Codes to interpret the results of accessing VSAM data sets and/or QSAM files.

Table of Contents Previous Section Next Section Internet Access Required

The following links will require an internet connect.

This suite of programs and documentation is available to download for review and evaluation purposes. Other uses will require a SimoTime Software License. Link to an Evaluation zPAK Option that includes the program members, documentation and control files.

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 and services available from Micro Focus. This link requires an Internet Connection.

Table of Contents Previous Section Next Section Glossary of Terms

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

Table of Contents Previous Section Next Section Comments or Feedback

This document was created and is copyrighted and maintained by SimoTime Technologies.

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.

Table of Contents Previous Section Next Section 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 or need assistance with converting non-relational data structures simply give us a call at 415 883-6565 or check the web site at http://www.simotime.com

Return-to-Top
Application and Data Migration, A Model for a Request for Information (RFI)
Copyright © 1987-2018
SimoTime Technologies and Services
All Rights Reserved
When technology complements business
http://www.simotime.com