Advanced Data Set Information

This chapter expands on the information presented in the chapter Files and Data Sets in your User's Guide. It covers the following subjects:

4.1 Data Set Organizations

The data set organizations supported by Mainframe Express are shown in the following table.

Abbreviation	Organization	Comment
DA	Direct access
DAU	Direct access, unmoveable
GDG	Generation data group
IS	Indexed sequential
ISU	Indexed sequential, unmoveable
PDSM	Partitioned data set member	Micro Focus organization
PO	Partitioned
POU	Partitioned, unmoveable
PS	Physical sequential
PSU	Physical sequential, unmoveable
VSAM	Virtual storage access method

4.2 Record Formats

The following table shows the record formats for all the data set organizations except VSAM.

Abbreviation	Format	Control Characters	Record Delimiters	Comment
F	Fixed	None	None
FA	Fixed	ANSI	None
FB	Fixed blocked	None	None	Same as F format
FBA	Fixed blocked	ANSI	None	Same as FA format
FBM	Fixed blocked	Machine	None	Same as FM format
FBS	Fixed blocked spanned	None	None	Same as F format
FM	Fixed	Machine	None
FS	Fixed spanned	None	None	Same as F format
LSEQ	Line sequential	None	Carriage return/line feed
U	Undefined			Results unpredictable on PC
V	Variable	None	Micro Focus type
VA	Variable	ANSI	Micro Focus type
VB	Variable blocked	None	Micro Focus type	Same as V format
VBA	Variable blocked	ANSI	Micro Focus type	Same as VA format
VBM	Variable blocked	Machine	Micro Focus type	Same as VM format
VBS	Variable blocked spanned	None	Micro Focus type	Same as V format
VM	Variable	Machine	Micro Focus type
VS	Variable spanned	None	Micro Focus type	Same as V format

Note: Blocked and spanned record formats are accepted by Mainframe Express but have no meaning in a PC environment.

Abbreviation	Format	Control Characters	Comment
ES	Entry sequence	None
KS	Key sequence	None
LS	Linear sequence	None	Not supported
RR	Relative record	None

4.3 Logical Record Length

Mainframe Express works with logical record lengths as defined in the following table:

Record Format	Logical Record Length
Fixed	Actual record length
Variable	Actual record length + 4
LSEQ	Maximum record length

4.4 Mapping to PC File Formats

Mainframe Express writes data sets to PC files using the following organization and record format mapping:

Mainframe	PC
Dataset Organization	Record Format	File Organization	Record Format	Comment
DA, DAU, PS, PSU	Any fixed (Fnn) or variable (Vnn) format	Sequential	Micro Focus
DA, DAU, PS, PSU	LSEQ	Line sequential	Micro Focus	Always uses ANSI character set. Can only be edited with a text editor
GDG				Catalog entry only
IS, ISU	Any fixed (Fnn) or variable (Vnn) format	Indexed sequential	Micro Focus
PDSM	Any fixed (Fnn) or variable (Vnn) format	Sequential	Micro Focus
PDSM	LSEQ	Line sequential	Micro Focus
PO, POU				Catalog entry only
VSAM	ES	Sequential	ESDS
VSAM	ES	Indexed sequential	ESDS	Alternate index defined
VSAM	KS	Indexed sequential	Micro Focus
VSAM	LS	Not supported
VSAM	RR	Relative	Micro Focus

4.5 Support for mfextmap.dat and PROXMVS Files

Mainframe Express provides support for PROXMVS files as well as mfextmap.dat files created when using COBOL Workbench, where PROXMVS and COBOL Workbench are earlier products from Micro Focus. For information on how to use such files, see the chapters Migrating from PROXMVS and Your Mfextmap File in your Migration Cookbook.

4.6 Support for Generation Data Groups

A generation data group (GDG) consists of two parts: a GDG model and a series of physical sequential data sets, called biases, that are associated with the GDG.

You can allocate a GDG model in either of two ways:

By using the Allocate dialog on the Catalog tab, selecting GDG for DSORG and entering the information requested
By downloading the IDCAMS job that defined the GDG model on the mainframe and running it on the PC.

When the GDG model is created, you can use the MFA Drag and Drop utility to download the GDG bias or biases from the mainframe.

The following example illustrates a job that can be used to create a generation data group. STEP00 creates the GDG model and STEP01 creates five new GDG biases.

//MFIDMFGD JOB 'MFIDMFGD',CLASS=A,MSGCLASS=A,NOTIFY=MFIDF

//STEP00 EXEC PGM=IDCAMS

//SYSOUT DD SYSOUT=*

//SYSPRINT DD SYSOUT=*

//AMSDUMP DD SYSOUT=*

//SYSIN DD *

DELETE MFIDMF.TEST.GDG

DEFINE GENERATIONDATAGROUP

(NAME(MFIDMF.TEST.GDG) EMPTY NOSCRATCH LIMIT(96))

/*

//STEP01 EXEC PGM=IEFBR14

//SYSUXX DD DSN=MFIDMF.TEST.GDG(+1),DISP=(NEW,CATLG),SPACE=(TRK,(5,2))

//SYSUXY DD DSN=MFIDMF.TEST.GDG(+2),DISP=(NEW,CATLG),SPACE=(TRK,(5,2))

//SYSUXZ DD DSN=MFIDMF.TEST.GDG(+3),DISP=(NEW,CATLG),SPACE=(TRK,(5,2))

//SYSUXA DD DSN=MFIDMF.TEST.GDG(+4),DISP=(NEW,CATLG),SPACE=(TRK,(5,2))

//SYSUXB DD DSN=MFIDMF.TEST.GDG(+5),DISP=(NEW,CATLG),SPACE=(TRK,(5,2))

Five biases named MFIDMF.TEST.GDG.G0001V00, MFIDMF.TEST.GDG.G0002V00, MFIDMF.TEST.GDG.G0003V00, MFIDMF.TEST.GDG.G0004V00 and MFIDMF.TEST.GDG.G0005V00 are created by STEP01.

A bias can be processed by its relative number, its actual reference or as a part of the entire generation data group. For example, each of the following statements could be executed after running the previous job.

//SYSUT1 DD DSN=MFIDMF.TEST.GDG,DISP=SHR

This would cause the entire generation data group MFIDMF.TEST.GDG, consisting of a set of concatenated data sets MFIDMF.TEST.GDG.G0001V00 through MFIDMF.TEST.GDG.G0005V00, to be referenced.

//SYSUT1 DD DSN=MFIDMF.TEST.GDG(0),DISP=SHR

The relative number 0 would cause the data set named MFIDMF.TEST.GDG.G0005V00 to be referenced.

//SYSUT1 DD DSN=MFIDMF.TEST.GDG(-1),DISP=SHR

The relative number -1 would cause the data set named MFIDMF.TEST.GDG.G0004V00 to be referenced.

//SYSUT1 DD DSN=MFIDMF.TEST.GDG(+1),DISP=SHR

The relative number +1 would cause a new data set named MFIDMF.TEST.GDG.G0006V00 to be referenced.

//SYSUT1 DD DSN=MFIDMF.TEST.GDG.G0003V00,DISP=SHR

The actual reference G0003V00 would cause the data set named MFIDMF.TEST.GDG.G0003V00 to be referenced.

The increment of numbers occurs per job, so if you had two consecutive steps that referenced +1, then each step would be using the same data set.

4.6.1 Generation Data Group Restrictions

This section describes restrictions when using GDGs in Mainframe Express:

The maximum number of host GDG biases that you can reference is 99.
Mainframe Express does not support versioning of the GDG biases, so the only biases that versioning works for are those with a data set name ending with V00. For example, if the GDG model name is MFIDMF.TEST.GDG then the GDG biases must have the form MFIDMF.TEST.GDG.G0001V00 .......... MFIDMF.TEST.G9999V00, with gaps in the numbering sequence. If you attempt to use a bias that ends, for example, in V01, it will not be found when GDG names are resolved during program execution.
A GDG model and all of its Generation Data Sets (GDSs) must reside on the same platform. It is not possible to have a mixture of GDSs where some reside on the mainframe and others on the PC.
If you are using relative bias numbers to reference GDSs in your JCL, for example MFIDMF.TEST.GDG(-4) or MFIDMF.TEST.GDG(+1), the following restrictions apply:
- If the GDSs are located on a Mainframe Access server, you cannot reference any numbers greater than zero. The only permitted numbers are 0 through -n, where n is the maximum number of GDSs supported by the GDG model.
- If the GDSs are located on a PC or network, all processing is supported with only the limitations that are already documented in this section.