Using Mainframe Access (MFA) - Micro Focus

Using Mainframe Access (MFA) from a COBOL program
This article describes the methods necessary to access the services of Mainframe Access (MFA) to
allow a COBOL application program on the PC to access resources on your mainframe system.
The MFA command line can be called from a COBOL program by using a Micro Focus call-by-number
function called X'91' function 35. The MFA command line function uses MFDAS.EXE and documented
functions that have been included below. For this program to work, you must have a working MFA
client installed on the machine. The DISPLAY that is presented to the COMMAND LINE will be
executed by MFDAS.EXE by the call. Note that the display does not include the MFDAS because it is
passed in the COMMAND of the call. The MFDAS.EXE directory would need to be in the PATH
environment variable for the execution to work.
MFA requires a login to the mainframe. Should a login daemon not be currently running a GUI login
screen will appear for the user to sign in with their mainframe sign on ID and Password.
The following is a tested program sample:
IDENTIFICATION DIVISION.
PROGRAM-ID. TESTCLIX.
ENVIRONMENT DIVISION.
CONFIGURATION SECTION.
SOURCE-COMPUTER. IBM-PC.
OBJECT-COMPUTER. IBM-PC.
DATA DIVISION.
WORKING-STORAGE SECTION.
01 RESULT PIC X COMP-X.
01 FUNC PIC X COMP-X VALUE 35.
01 COMMAND.
05 LEN PIC X COMP-X VALUE 10.
05 PGM PIC X(10) VALUE 'MFDAS.EXE'.
PROCEDURE DIVISION.
DISPLAY
"IMPORT TEXT H:\customers\mfa\filename.dat FROM QSAM MFICWA.S
- "YSCIN" UPON COMMAND-LINE
CALL X'91' USING RESULT FUNC COMMAND
IF RESULT = 0
Display "IMPORT SUCCESSFUL"
ELSE
Display "IMPORT failed " RESULT
END-IF.
GOBACK.
The following are excerpts from the stand-alone MFA product documentation.
On return, Drag and Drop sets the COBOL RESULT variable. The following return-codes are
produced:
00 Successful call
01 An error was returned from MFLSC
14 The program MFLSC is missing
15 Call to DFCONV failed
48 The mainframe member is locked by another user
49 A mainframe ABEND occurred
50 A dynamic allocation error occurred when accessing a dataset
51 An open error occurred on the mainframe
52 An invalid request for a valid function was detected
53 An I/O error has occurred on a mainframe dataset
54 An invalid sub-code was given to the mainframe
55 A load error on a program on the mainframe was detected
Page 1 of 4

Using Mainframe Access (MFA) from a COBOL program
56 A length error, at a record level, has been detected
57 A general security error has been detected
58 A hash code mismatch has been detected
59 The remote execution failed
60 The JES spool file is not an output file
61 The JES spool file is not a held output file
100 Syntax error in call
125 Too many concurrent users are active
139 The record length was too large
218 The DCB is not supported. This is usually caused by trying to use RECFM=U
219 The mainframe load libraries are not APF authorized
220-241 Various SAF security return codes
242 The component in use has not been activated on the mainframe
243 Unable to write the specified file to the workstation
244 Unable to read the specified file from the workstation
245 The catalog search detected an error
246 The catalog search did not yield any results
247 The /F MFENDDRV* statement was not in FHREDIR.CFG
248 The /F MFLSCDRV* statement was not in FHREDIR.CFG
249 The file FHREDIR.CFG could not be located
250 A communications failure occurred
251 The file did not have a positive length
252 An invalid mask was given
253 The local access mask was not specified
254 The local access mode was not set
255 Invalid function was requested
Importing Data
You can import individual members, or a collection of members defined by a filter, from the JES
spool, a partitioned dataset or source code control system or you can import entire QSAM, VSAM
datasets, IMS databases or DB/2 tables with automatic data conversion to the appropriate Micro
Focus format. You may optionally specify a control file containing one or more commands and allow
MFDAS to run them as a batch. To do this, place the commands in a control file of any name,
without the preceding MFDAS parameter, then run MFDAS with the parameter @filename, where
filename is the name of the control file.
Text or binary transfers are possible. Use the BINARY or TEXT operand to override the default
transfer type for the type. The default transfer type for PDS, Librarian, Panvalet, Endevor, or
CCC/LCM, is TEXT. The default transfer type for QSAM is BINARY. VSAM, IMS and DB/2 cannot be
overridden.
The MEMBER parameter can specify a specific mainframe member name, or can include special filter
characters to allow multiple imports to occur based on the special filter characters that you specify.
These special filter characters are:
• * means any characters may follow
• ? means any character in this position
• + means the character in this position must be non-blank
• - means the character in this position must be blank
• \ means the character in this position must be non-numeric
• / means the character in this position must be numeric
Page 2 of 4

Using Mainframe Access (MFA) from a COBOL program
Import command examples:
JES
To import from the mainframe JES2 or JES3 spool:
MFDAS IMPORT filename FROM JES JOB#####|filter
PDS
To import from a Partitioned data set:
MFDAS IMPORT [BINARY | TEXT] filename FROM PDS pdsname MEMBER memname|filter
Librarian
To import from a Librarian data set:
MFDAS IMPORT [BINARY | TEXT] filename FROM LIB libname MEMBER memname|filter
Panvalet
To import from a Panvalet dataset:
MFDAS IMPORT [BINARY | TEXT] filename FROM PAN panname MEMBER memname|filter
Endevor
To import from an Endevor data set:
MFDAS IMPORT [BINARY | TEXT] filename FROM END ENV 'env' SYS 'sys' SUB 'sub' MEMBER
memname|filter TYPE memtype CCID ccid COMMENT user comment
CCC/LCM
To import from a CCC/LCM data set. If you wish to lock this member out, then specify the LOCK Y
parameter.
MFDAS IMPORT [BINARY | TEXT] filename FROM LCM lcmname SYSTEM systemid CONFIG configid
MEMBER memname|filter TYPE memtype [LOCK y]
In-House System
To import from your own in-house source code control system dataset:
MFDAS IMPORT [BINARY | TEXT] filename FROM IHS ihsdatasetname MEMBER memname|filter
QSAM
To import from a QSAM data set with automatic data conversion:
MFDAS IMPORT [BINARY | TEXT] filename FROM QSAM qsamname
VSAM KSDS
To import from a VSAM KSDS data set with automatic data conversion and produce a variable
length workstation indexed file. If you wish to produce a fixed length indexed file, then use KSDS-
FIXED instead of KSDS.
MFDAS IMPORT filename FROM KSDS vsamksdsname
VSAM ESDS
To import from a VSAM ESDS data set with automatic data conversion and produce a variable
Page 3 of 4

Using Mainframe Access (MFA) from a COBOL program
length workstation indexed file. If you wish to produce a fixed length indexed file, then use ESDS-
FIXED instead of ESDS.
MFDAS IMPORT filename FROM ESDS vsamesdsname
VSAM RRDS
To import from a VSAM RRDS data set with automatic data conversion and produce a variable
length workstation indexed file. If you wish to produce a fixed length indexed file, then use RRDS-
FIXED instead of RRDS.
MFDAS IMPORT filename FROM RRDS vsamrrdsname
IMS Database
To import from an unloaded IMS database with automatic data conversion and produce a
workstation PCIMS format database. Three additional parameters are available after the mainframe
IMS unloaded datasetname field. These parameters are the required database name, location of
segment name in the data record (relative to 1) and the location of the segment data in the data
record (relative to 1). If the mainframe database has been unloaded using the Micro Focus PCIMS
unload utility, then these three fields are not required, as they are automatically picked up from the
mainframe unloaded dataset.
MFDAS IMPORT filename FROM IMS imsunloadedname [databasename] [segmentnamelocation]
[segmentdatalocation]
DB/2 Table
To import from an unloaded DB/2 table with automatic data conversion and produce a workstation
XDB format table. Three additional parameters are required after the mainframe DB/2 unloaded
datasetname field. These parameters are the required location, authid, and table name. The
mainframe table must have been unloaded into a sequential file using the DSNTIAUL DB/2 unload
utility. The table must exist and the SQLWizard must be available on the path.
MFDAS IMPORT filename FROM DB2 db2unloadedname location authid tablename
NOTE: The MFA product and the example shown here are designed only to be used in a mainframe
application offload development environment utilizing our Mainframe Express product. The MFA
product is not designed to be used in any production environment or application.
Page 4 of 4