Populate the Catalog
Micro Focus Enterprise Server

Table of Contents

v-24.01.01 - catpop01.htm

	Introduction
	Getting Started
	Format of the Excel Spreadsheet
	Record Layout, List of Names
	Categories of non-Relational Data
	Partitioned Data Sets (PDS's)
	Generation Data Groups (GDG's)
	Sequential Files (RSEQ)
	Key Sequenced Data Set (KSDS)
	Special Purpose Files or Data Sets
	Diagram, Create Catalog Entries
	Summary
	Software Agreement and Disclaimer
	Downloads and Links
	Current Server or Internet Access
	Internet Access Required
	Glossary of Terms
	Contact or Feedback
	Company Overview

The SimoTime Home Page

Introduction

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.

The process described in this document may be used as a model for automating the creation of the catalog entries. The process starts with a list of files in an Excel spreadsheet. The spreadsheet is saved as a Line Sequential (LSEQ) file with the records formatted as a text string of Comma-Separated-Values (CSV).

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.

Getting Started

For this approach we have chosen to use Excel to manage the list of names and properties for the non-relational data files. 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 five groups or five 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 fifth Excel spread sheet is for Special Purpose files.

The following is a brief description of each of the categories for Data Files or Data Structures.

* * H * H

Name	Description
LONAPPDS	1. Use Excel to create a file containing a list of names and properties for the Partitioned Data Sets (PDS's). Save a copy of the Excel spreadsheet as a CSV file. 2. Run the CATPDSE1.CMD to convert the CSV list of names and properties file to a record sequential file with records of a fixed-field format. Note: the CATPDSE1.CMD will submit a job that will create the catalog entry for the list file. 3. Run the CATPDSE2.CMD to submit a job that will read the list of names and properties file and submit generated or user-specified JCL to the internal reader to make the catalog entries for the PDS's.
LONAPGDG	1. Use Excel to create a file containing a list of names and properties for the Generation Data Groups (GDG's). Save a copy of the Excel spreadsheet as a CSV file. 2. Run the CATGDGE1.CMD to convert the CSV list of names and properties file to a record sequential file with records of a fixed-field format. Note: the CATGDGE1.CMD will submit a job that will create the catalog entry for the list file. 3. Run the CATGDGE2.CMD to submit a job that will read the list of names and properties file and submit generated or user-specified JCL to the internal reader to make the catalog entries for the GDG bases and possible GDG Models.
LONAPSEQ	1. Use Excel to create a file containing a list of names and properties for the Sequential Files. Save a copy of the Excel spreadsheet as a CSV file. 2. Run the CATSEQE1.CMD to convert the CSV list of names and properties file to a record sequential file with records of a fixed-field format. Note: the CATSEQE1.CMD will submit a job that will create the catalog entry for the list file. 3. Run the CATSEQE2.CMD to submit a job that will read the list of names and properties file and submit generated or user-specified JCL to the internal reader to make the catalog entries for the sequential files.
LONAPKSD	1. Use Excel to create a file containing a list of names and properties for the VSAM Key Sequenced Data Sets (KSDS's). Save a copy of the Excel spreadsheet as a CSV file. 2. Run the CATKSDE1.CMD to convert the CSV list of names and properties file to a record sequential file with records of a fixed-field format. Note: the CATKSDE1.CMD will submit a job that will create the catalog entry for the list file. 3. Run the CATKSDE2.CMD to submit a job that will read the list of names and properties file and submit generated or user-specified JCL to the internal reader to make the catalog entries for the VSAM Key Sequenced Data Sets (KSDS's).
LONAPX10	1. Use Excel to create a file containing a list of names and properties for the Special Purpose files. Save a copy of the Excel spreadsheet as a CSV file. 2. Run the CATX10E1.CMD to convert the CSV list of names and properties file to a record sequential file with records of a fixed-field format. Note: the CATX10E1.CMD will submit a job that will create the catalog entry for the list file. 3. Run the CATX10E2.CMD to submit a job that will read the list of names and properties file and submit generated or user-specified JCL to the internal reader to make the catalog entries for the Special Purpose files.
Note-1	The catalog entries for the Partitioned Data Sets (PDS's) are done first since this step typically creates the catalog entries for the Procedure Library (PROC LIB) that may be used in later steps if a user defined job is executed.
Note-2	The preceding sequence of processing assumes a new catalog is being populated, this avoids the possibility of duplicate data set conflicts.
Note-3	With this approach the catalog entries can and should be created prior to moving the data into the directory, this reduces the possibility of deleting a physical data set if a user defined job does a DELETE/DEFINE to create a VSAM cluster.

The Five Categories of non-Relational Data and the Processes for Populating a Catalog

Additional detail and links to documents with additional detail for each of the preceding processing tasks is provided in later sections of this document.

Format of the Excel Spreadsheet

The following is the column structure for an Excel spreadsheet to be used as a starting point to populate the catalog.

* HTMGE

Column - Label

Description

A - Level Number

This should be a "1" for the primary file definition information. A zero (0) is used to define the row that is used for column headers.

B - DSN

This is a text string with a maximum length of forty-four (44) characters. It is the fully-qualified MVS Data Set Name (DSN) or VSAM Cluster Name

C - DD Name

This is a text string with a maximum length of eight (8) characters. It is the DD Name.

D - DSORG

This is the Data Set Organization.

E - RECFM

This is the Record Format.

F - lrecl-MIN

This is a numeric string with a maximum length of five (5) digits. It is the minimum or average record length.

G - lrecl-MAX

This is a numeric string with a maximum length of five (5) digits. It is the maximum record length.

H - KeyPos

This is a numeric string with a maximum length of five (5) digits. It is the key starting position. The first position in a record is 1

I - KeyLen

This is a numeric string with a maximum length of five (5) digits. It is for the length of the key.

J - VSAM Data Name

This is a text string with a maximum length of forty-four (44) characters. It is the VSAM Data Name for KSDS and ESDS

K - VSAM Index Name

This is a text string with a maximum length of forty-four (44) characters. It is the VSAM Index Name for KSDS

L - Override Job

This is a text string with a maximum length of eight (8) characters. It is the JCL Member name that will be used to override the generated JCL that is used to create the catalog entry.

M - User Job 1

This is a text string with a maximum length of eight (8) characters. It is the JCL Member name for a job that will be submitted to the internal reader after the catalog creation process is complete.

N - User Job 2

This is a text string with a maximum length of eight (8) characters. It is the JCL Member name for a job that will be submitted to the internal reader after the previous steps are completed.

O - Extended S1

This is a text string with a maximum length of four (4) characters. The content varies.
If DSORG=PO then this field contains the extension of the PDSM that is used for a dynamic PDS.

P - Extended S2

This is a text string with a maximum length of four (4) characters. The content varies.

Q - Extended M1

This is a text string with a maximum length of sixteen (16) characters. The content varies, refer to Note-1

R - Extended M2

This is a text string with a maximum length of sixteen (16) characters. The content varies, refer to Note-1

S - Extended M3

This is a text string with a maximum length of sixteen (16) characters. The content varies, refer to Note-1

T - Extended M4

This is a text string with a maximum length of sixteen (16) characters. The content varies, refer to Note-1

U - Extended X1

This is a text string with a maximum length of 256 characters. It is the path to the directory that contains the Members for a Job Override, User Job 1 and/or User Job 2.

V - Extended X2

This is a text string with a maximum length of 256 characters. The content varies.
If DSORG=PO then this field contains the path to the directory that contains the PDS Members.

Note-1:

The Extended M1 trhough M4 fields are sixteen (16) byte fields. The content varies.

If	DSORG=GDG the following values are accepted:
	LIMIT(nnn) where nnn is the number of active generations
	SCRATCH or NOSCRATCH, SCRATCH will physically delete the generation, NOSCRATCH will uncatalog the latest generation
	NOEMPTY or EMPTY, This specifies, what action is to be taken when the GDG becomes full base on the number in the LIMIT.

Format of an Excel Spread Sheet

Record Layout, List of Names

The utility programs used in this approach to creating catalog entries will process a file containing a List Of Names And Properties (referred to as the LONAP files). The information in the LONAP files is maintained in various Excel spread sheets and saved to a file using the Comma-Separated-Values (or CSV) format.

However, since this approach is typically used in a mainframe-oriented, COBOL-oriented environment a processing step has been included to convert the CSV files that contain the list of names and properties to a sequential files with the traditional fixed field length and fixed record length format. This provides the COBOL application programmers with access to the information in a format that is familiar and easy to use.

The following COBOL Copy File (LONAPFFL.CPY) shows the record layout for the Record Sequential File with a Fixed Field Format

      *****************************************************************
      *               LONAPFFL.CPY - a COBOL Copy File                *
      *     Record Layout for the File Properties Repository          *
      *  The record stucture is a fixed length of 1,024 characters    *
      *         Copyright (C) 1987-2019 SimoTime Technologies         *
      *                     All Rights Reserved                       *
      *              Provided by SimoTime Technologies                *
      *        Our e-mail address is: helpdesk@simotime.com           *
      *     Also, visit our Web Site at http://www.simotime.com       *
      *****************************************************************
      *  The information that is imported into this format originates
      *  from an Excel spreadsheet. The spreadsheet is saved to an
      *  ASCII/Text File with a Comma-Separated-Values (or CSV) record
      *  structure.
      *
      *  LONAP is an acronym for a List Of Names And Properties.
      *  CSV   is an acronym for Comma-Separated-Values.
      *  FFL   is an acronym for Fixed-Field-Length.
      *
      *  A conversion program is used to convert the CSV File to a
      *  Record Sequential File with the following Fixed Field format.
      *
      *  The fields are all fixed length.
      *  Numeric fields are right-adjusted with leading zeroes.
      *  Alpha-numeric fields are left adjusted with trailing spaces.
      *
      *  Positions 73-80 of the following statements are used to
      *  identify the original columns used in the Excel spreadsheet.
      *
       01  LONAPFFL-REC.                                                Excel
           05  LONAPFFL-LEVEL-CHR.
               10  LONAPFFL-LEVEL-NBR      PIC 9(2).                    col-A
           05  LONAPFFL-FILE-INFO.
               10  LONAPFFL-DSN            PIC X(54).                   col-B
               10  LONAPFFL-DD-NAME        PIC X(17).                   col-C
               10  LONAPFFL-DSORG          PIC X(4).                    col-D
               10  LONAPFFL-RECFM          PIC X(4).                    col-E
               10  LONAPFFL-LRECL-MIN      PIC 9(5).                    col-F
               10  LONAPFFL-LRECL-MAX      PIC 9(5).                    col-G
               10  LONAPFFL-KEYPOS         PIC 9(5).                    col-H
               10  LONAPFFL-KEYLEN         PIC 9(5).                    col-I
               10  LONAPFFL-VSAM-DAT       PIC X(58).                   col-J
               10  LONAPFFL-VSAM-IDX       PIC X(58).                   col-K
           05  LONAPFFL-JOB-EXEC.
               10  LONAPFFL-JCL-OVR1       PIC X(8).                    col-L
               10  LONAPFFL-JCL-USR1       PIC X(8).                    col-M
               10  LONAPFFL-JCL-USR2       PIC X(8).                    col-N
           05  LONAP-EXTENDED-GROUP.
               10  LONAPFFL-EXTENDED-S1    PIC X(4).                    col-O
               10  LONAPFFL-EXTENDED-S2    PIC X(4).                    col-P
               10  LONAPFFL-EXTENDED-M1    PIC X(16).                   col-Q
               10  LONAPFFL-EXTENDED-M2    PIC X(16).                   col-R
               10  LONAPFFL-EXTENDED-M3    PIC X(16).                   col-S
               10  LONAPFFL-EXTENDED-M4    PIC X(16).                   col-T
               10  LONAPFFL-EXTENDED-X1    PIC X(256).                  col-U
               10  LONAPFFL-EXTENDED-X2    PIC X(256).                  col-V
           05  FILLER                      PIC X(199).
      *
      ***  LONAPFFL - End-of-Copy File - - - - - - - - - - - LONAPFFL *
      *****************************************************************
      *

Categories of non-Relational Data

The following five sub-sections provide a brief overview of the five categories of non-relational data structures and links to documents with additional technical detail.

Note: A separate Excel spreadsheet and LONAP file is created and maintained for each category.

Partitioned Data Sets (PDS's)

The processing to create catalog entries for Partitioned Data Sets (PDS's) uses generated JCL by default. If an override job is specified then JCL is not generated and the override job is submitted to the internal reader. The generated JCL will use IEFBR14 with a DD statement to create the catalog entry.

Note: A PDS catalog entry simply points to the directory (or folder) where the PDS members are stored.

If User Job 1 is specified it will be submitted before the generated or override job is submitted. If User Job 2 is specified it will be submitted after the generated or override job is submitted. The following is an example of the generated JCL to create a PDS for a PROC Library (or PDS).

**SIMOTIME-SEPARATOR-----------------------------------------SIMOTIME**
//MAKEPO   JOB SIMOTIME,CLASS=1,MSGCLASS=0,USER=SIMOTIME,NOTIFY=CSIP1
//* *******************************************************************
//* Do Catalog Entry for SIMOTIME.PDS.PROCLIB
//* Generated JCL Code, the file properties were user defined.
//PODEFINE EXEC PGM=IEFBR14
//SYSOUT   DD   SYSOUT=*
//PROCLIB1 DD  DSN=SIMOTIME.PDS.PROCLIB,
//             DISP=(NEW,CATLG,CATLG),
//             STORCLAS=MFI,
//             SPACE=(TRK,5),
//             DCB=(DSORG=PO,LRECL=00080,RECFM=LSEQ)
//*MFE: %PCDSN=C:\SIMOSAM1\DEVL\PROCLIB\*.PRC
//*

For the Micro Focus environment there is an ability to create dynamic PDS's. To do this requires information about the directory where PDS members are stored and the file extension used with the PDS member. This information is specified in the "//*MFE: %PCDSN=" statement as shown in the preceding example.

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.

Generation Data Groups (GDG's)

The processing to create catalog entries for Generation Data Group's (or GDG's) uses generated JCL by default. If an override job is specified then JCL is not generated and the override job is submitted to the internal reader. The generated JCL will use IDCAMS and the DEFINE function to create the catalog entry for the GDG Base.

**SIMOTIME-SEPARATOR-User-Defined-JOB-2----------------------SIMOTIME**
//MAKEAGDG JOB SIMOTIME,CLASS=1,MSGCLASS=0,USER=SIMOTIME,NOTIFY=CSIP1
//* *******************************************************************
//* Do Catalog Entry for SIMOTIME.DATA.GDGROUP2
//* Generated JCL Code, the file properties were user defined.
//GDGIDXX1 EXEC PGM=IDCAMS
//SYSPRINT DD   SYSOUT=*
//SYSIN    DD   *
   DEFINE GDG(                                                       -
          NAME(SIMOTIME.DATA.GDGROUP2)                               -
          LIMIT(003)                                                 -
          NOEMPTY                                                    -
          SCRATCH)
/*
//*
**SIMOTIME-SEPARATOR-Generated-JCL-for-a-Sequential-File-----SIMOTIME**
//MAKERSEQ JOB SIMOTIME,CLASS=1,MSGCLASS=0,USER=SIMOTIME,NOTIFY=CSIP1
//* *******************************************************************
//* Do Catalog Entry for SIMOTIME.DATA.GDMODEL2
//* Generated JCL Code, the file properties were user defined.
//PSDEFINE EXEC PGM=IEFBR14
//SYSOUT   DD   SYSOUT=*
//GDMODEL2 DD  DSN=SIMOTIME.DATA.GDMODEL2,
//             DISP=(NEW,CATLG,CATLG),
//             STORCLAS=MFI,
//             SPACE=(TRK,5),
//             DCB=(DSORG=PS,LRECL=00080,RECFM=FB)
//*

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.

Sequential Files (RSEQ)

The processing to create catalog entries for Sequential Files uses generated JCL by default. If an override job is specified then JCL is not generated and the override job is submitted to the internal reader. The generated JCL will use IEFBR14 with a DD statement to create the catalog entry.

**SIMOTIME-SEPARATOR-Generated-JCL-for-a-Sequential-File-----SIMOTIME**
//MAKERSEQ JOB SIMOTIME,CLASS=1,MSGCLASS=0,USER=SIMOTIME,NOTIFY=CSIP1
//* *******************************************************************
//* Do Catalog Entry for SIMOTIME.DATA.CUSRE512
//* Generated JCL Code, the file properties were user defined.
//PSDEFINE EXEC PGM=IEFBR14
//SYSOUT   DD   SYSOUT=*
//CUSRE512 DD  DSN=SIMOTIME.DATA.CUSRE512,
//             DISP=(NEW,CATLG,CATLG),
//             STORCLAS=MFI,
//             SPACE=(TRK,5),
//             DCB=(DSORG=PS,LRECL=00512,RECFM=FB)
//*

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.

Key Sequenced Data Set (KSDS)

The processing to create catalog entries for VSAM, KSDS's uses generated JCL by default. If an override job is specified then JCL is not generated and the override job is submitted to the internal reader. The generated JCL will use IDCAMS and the DEFINE function to create the catalog entry for the VSAM cluster.

//MAKEKSDS JOB SIMOTIME,CLASS=1,MSGCLASS=0,USER=SIMOTIME,NOTIFY=CSIP1
//* *******************************************************************
//* Do Catalog Entry for SIMOTIME.UTIL.FPMASTER
//* Generated JCL Code, the file properties were user defined.
//KSDEFINE EXEC PGM=IDCAMS
//SYSPRINT DD   SYSOUT=*
//SYSIN    DD   *
 DEFINE CLUSTER (NAME(SIMOTIME.UTIL.FPMASTER)                        -
                TRACKS(45,15)                                        -
                INDEXED)                                             -
           DATA (NAME(SIMOTIME.UTIL.FPMASTER.DAT)                    -
                KEYS(00054,00002)                                    -
                RECORDSIZE(01024,01024)                              -
                FREESPACE(10,15)                                     -
                CISZ(8192))                                          -
          INDEX (NAME(SIMOTIME.UTIL.FPMASTER.IDX))
/*
//*
//* DATA (NAME(SIMOTIME.UTIL.FPMASTER.DAT)
//*      KEYS(00054,00002)
//*      RECORDSIZE(01024,01024)
//*

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.

Special Purpose Files or Data Sets

This category is reserved as a "Catch-All" for files and/or data sets that are typically used for specialized purposes on the mainframe. They may be critical to the application or used for debugging, tracking and tracing purposes.

The processing to create catalog entries for the Special Purpose Files uses generated JCL by default. If an override job is specified then JCL is not generated and the override job is submitted to the internal reader. Depending on the file specifications the generated JCL will use IEFBR14 or IDCAMS and the DEFINE function to create the catalog entry for a User-Defined file or data set.

If User Job 1 is specified it will be submitted before the generated or override job is submitted. If User Job 2 is specified it will be submitted after the generated or override job is submitted. The following is an example of a user-coded JCL member that is very similar to the generated JCL that would be used to create a catalog entry for a VSAM, ESDS.

//ES128CJ1 JOB SIMOTIME,CLASS=1,MSGCLASS=0,NOTIFY=CSIP1
//* *******************************************************************
//*       ES128CJ1.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   - Delete and Define an ESDS using IDCAMS.
//* Author - SimoTime Technologies
//* Date   - July 24, 2007
//*
//* The process will create a new Entry Sequenced Data Set (ESDS).
//*
//* This set of programs will run on a mainframe under ZOS or on a
//* Personal Computer with Windows and Micro Focus Mainframe Express
//* or Enterprise Server.
//*
//STEP0010 EXEC PGM=IDCAMS
//SYSIN    DD *
 DEFINE CLUSTER(                        -
        NAME(SIMOTIME.ESDS.ESDSC128)    -
        NONINDEXED                      -
        SHR(2 3)                        -
        CYL(9 9)                        -
        VOL(*))                         -
 DATA                                   -
        (NAME(SIMOTIME.ESDS.ESDSD128)   -
         RECSZ(004 128)                 -
         CISZ(8192)                     -
         FREESPACE(0 0))
//SYSOUT   DD  SYSOUT=*
//SYSPRINT DD  SYSOUT=*
//SYSUDUMP DD  SYSOUT=*
//*

This link provides detailed information to Identify, Document and Create Catalog Entries for Special Purpose Files. This category of files is used to address unique requirements of the application processing cycle or application support functions. This file list is managed in an Excel Spreadsheet and saved as a Comma-Separated-Values (CSV) file. This provides for a documented, repeatable process.

Diagram, Create Catalog Entries

The following diagram shows the steps in the processing cycle of creating the catalog entries.

START-UP

Start the Process to Create Catalog Entries

CATALLE2

CMD File to Create Catalog Entries

Step 1

Catalog Entries for PDS's

CALL

CATPDSE1

Create a PDSLIST File and Catalog Entry

CATPDSJ9

PDSLIST1

Delete a Previously Created PDS List File, Note-1

LONAPCSV

LONAPTIO

PDSLIST1

Convert CSV Format to Fixed Field Length Format

CATPDSJ1

PDSLIST1

Create a New Catalog Entry for PDS List File, Note-1

CALL

CATPDSE2

Submit Jobs to Create Catalog Entries for PDS's

CATPDSJ2

Allocate resources and execute MFCATPOP

PDSLIST1

MFCATPOP

INTRDR

Read PDSLIST and Create Catalog Entries, Note-2

BEHAVIOR

PDSTRACE

Modify program behavior, write to trace file, Note-3

Step 2

Catalog Entries for GDG's

CALL

CATGDGE1

Create a GDGLIST File and Catalog Entry

CATGDGJ9

GDGSLIST1

Delete a Previously Created GDG List File, Note-1

LONAPCSV

LONAPTIO

GDGLIST1

Convert CSV Format to Fixed Field Length Format

CATGDGJ1

GDGLIST1

Create a New Catalog Entry for GDG List File, Note-1

CALL

CATGDGE2

Submit Jobs to Create Catalog Entries for GDG's

CATGDGJ2

Allocate resources and execute MFCATPOP

GDGLIST1

MFCATPOP

INTRDR

Read GDGLIST and Create Catalog Entries, Note-2

BEHAVIOR

GDGTRACE

Modify program behavior, write to trace file, Note-3

Step 3

Catalog Entries for Sequential Files

CALL

CATSEQE1

Create a SEQLIST File and Catalog Entry

CATSEQJ9

SEQLIST1

Delete a Previously Created SEQ List File, Note-1

LONAPCSV

LONAPTIO

SEQLIST1

Convert CSV Format to Fixed Field Length Format

CATSEQJ1

SEQLIST1

Create a New Catalog Entry for SEQ List File, Note-1

CALL

CATSEQE2

Submit Jobs to Create Catalog Entries for Sequential Files

CATSEQJ2

Allocate resources and execute MFCATPOP

SEQLIST1

MFCATPOP

INTRDR

Read SEQLIST and Create Catalog Entries, Note-2

BEHAVIOR

SEQTRACE

Modify program behavior, write to trace file, Note-3

Step 4

Catalog Entries for VSAM, KSDS's

CALL

CATKSDE1

Create a KSDLIST File and Catalog Entry

CATSKSDJ9

KSDLIST1

Delete a Previously Created KSD List File, Note-1

LONAPCSV

LONAPTIO

KSDLIST1

Convert CSV Format to Fixed Field Length Format

CATKSDJ1

KSDLIST1

Create a New Catalog Entry for KSD List File, Note-1

CALL

CATKSDE2

Submit Jobs to Create Catalog Entries for VSAM, KSDS's

CATKSDJ2

Allocate resources and execute MFCATPOP

KSDLIST1

MFCATPOP

INTRDR

Read KSDLIST and Create Catalog Entries, Note-2

BEHAVIOR

KSDTRACE

Modify program behavior, write to trace file, Note-3

Step 5

Catalog Entries for Special Purpose Files

CALL

CATX10E1

Create an X10LIST File and Catalog Entry

CATSX10J9

X10LIST1

Delete a Previously Created X10 List File, Note-1

LONAPCSV

LONAPTIO

X10LIST1

Convert CSV Format to Fixed Field Length Format

CATX10J1

X10LIST1

Create a New Catalog Entry for X10 List File, Note-1

CALL

CATX10E2

Submit Jobs to Create Catalog Entries for the X10 category

CATKSDJ2

Allocate resources and execute MFCATPOP

X10LIST1

MFCATPOP

INTRDR

Read X10LIST and Create Catalog Entries, Note-2

BEHAVIOR

X10TRACE

Modify program behavior, write to trace file, Note-3

Note-1: The SYS1SCHEDULE Command is used to Submit a Job via a call from another CMD file.

Note-2: The MFCATPOP Program reads a LIST file and submits jobs via the Internal Reader (INTRDR) to create the catalog entries. The Jobs may be user-defined or programatically-generated.

Note-3: The BEHAVIOR file contains control records that will enable or disable certain program functions. The Trace file contains a list of the JCL that was generated and submitted to the Internal Reader (INTRDR)

Processing Cycle to Create Catalog Entries

Color Associations: The light-green boxes are unique to SIMOTIME Technologies using an IBM Mainframe System or Micro Focus Enterprise Developer. The light-red boxes are unique to the SIMOTIME Technologies using a Linux, UNIX or Windows System and COBOL Technologies such as Micro Focus. The light-yellow boxes are SIMOTIME Technologies, Third-party Technologies, decision points or program transitions in the processing logic or program generations. The light-blue boxes identify the input/output data structures such as Documents, Spreadsheets, Data Files, VSAM Data Sets, Partitioned Data Set Members (PDSM's) or Relational Tables. The light-gray boxes identify a system function or an informational item.

Summary

The process described in this document may be used as a model for automating the creation of the catalog entries. 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.

1.	Send an e-mail to our helpdesk.

1.1.	helpdesk@simotime.com.

2.	Our telephone numbers are as follows.

2.1.	1 415 763-9430 office-helpdesk

2.2.	1 415 827-7045 mobile

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

Return-to-Top

Populate a Catalog for the Micro Focus Enterprise Server Environment

When technology complements business

http://www.simotime.com