FLMTXFER Workstation Transfer

Purpose

The FLMTXFER translator uses the FILEXFER service to send and receive files from a workstation. When sending files to the workstation, the source data sets on the host (MVS™) system can be SCLM members, sequential data sets, or members of partitioned data sets. When receiving files from the workstation, the target data sets on the host (MVS) system can be sequential data sets or members of partitioned data sets.

When transferring SCLM members to the workstation, SCLM keeps track of which members have been sent to the workstation during a build and only sends each member to the workstation one time during the build.

For an example of the usage of this translator, see FLMLTWST Workstation Build translator.

Parameters

All parameters are keyword parameters and can be specified in any order. Parameters must be separated by commas. Extraneous parameters are ignored without any messages being produced.

COMMAND=PUT|GET

This parameter is required and must be specified in the options list. The valid values are:

PUT: Use this value to send files to the workstation.
GET: Use this value to retrieve files from the workstation.

This parameter will be truncated to 3 characters.

BLDINFO=@@FLMBIO

This parameter is required and must be specified in the options list with the value from @@FLMBIO.

SCLMINFO=@@FLMINF

This parameter is required and must be specified in the options list with the value from @@FLMINF.

MESSAGEDD=dd_name

This parameter is optional. If not specified, it defaults to MESSAGE. This is the ddname where messages will be written. This parameter will be truncated to 8 characters.

FILESDD=dd_name

This parameter is optional. If not specified, it defaults to FILES. This is the ddname containing the list of files to transfer. This parameter will be truncated to 8 characters. The data set allocated to this ddname must list one transfer specification per line. Each part of the transfer specification must be separated from other parts by one or more spaces. The following information must be provided with each transfer specification:

transfer format

This is a single character value that specifies the format of the file transfer.

A: Translate to ASCII
B: No translation

host data

This specifies what data set or member is the source or target of the transfer. If COMMAND=PUT is specified, this is the source of the file transfer. If COMMAND=GET is specified, this is the target of the file transfer. The format varies depending on the data being transferred.

For COMMAND=PUT, use IOTYPE=P to take advantage of the build caching function.

Data: Format
SCLM member: member.type
This format is only valid for COMMAND=PUT. The member name must be separated from the type name by a period. The member must be in the scope of the build. These members are tracked during the build and only sent to the workstation once even if FLMTXFER is called multiple times with the same member. FLMTXFER finds the member in the SCLM hierarchy and generates a fully qualified data set name with the member name for the file transfer.
Data set: 'data.set.name'
This format transfers a fully qualified data set name. The data set must be sequential or specify the member name. The data set name must be surrounded by quotes. SCLM does not track the data sets sent to the workstation. If FLMTXFER is called multiple times to transfer the same data set, the data set is transferred each time.
ddname: DDNAME:member
The member name is optional, but the colon (:) must be specified. The data set allocated to the ddname must be cataloged (CATLG=Y on the FLMALLOC). FLMTXFER gets the data set name allocated to the ddname and specifies it in the file transfer command.
workstation file name: The fully qualified workstation file name including the drive and path, if they apply.

Environment

The FLMTXFER translator must have access to ISPF services. It must be called from an FLMTRNSL with CALLMETH=ISPLNK.

Return codes

In addition to the return codes listed here, messages can be written to the ddname specified by the MESSAGEDD parameter.

FILES DD example

The following examples show the content of the FILES ddname. The first shows how to send compiler inputs to a workstation and the second how to retrieve the outputs.

Given COMMAND=PUT, in the first example the following transfers take place:

The data set allocated to the RESPONSE ddname is sent to c:\temp\response.file in ASCII format.
The member PMLINES in type C is found in the SCLM hierarchy and sent to c:\temp\PMLINES.c in ASCII format.
The member PMLINES in type H is found in the SCLM hierarchy and sent to c:\temp\PMLINES.h in ASCII format.
The data set 'PROJ1.C.LIB' is sent to c:\temp\proj1.lib in BINARY format.

A RESPONSE: c:\temp\response.fil
A PMLINES.C c:\temp\PMLINES.c
A PMLINES.H c:\temp\PMLINES.h
B 'PROJ1.C.LIB' c:\temp\proj1.lib

Given COMMAND=GET, in the second example the following transfers take place:

The file c:\temp\PMLINES.obj is sent to the member PMLINES in the data set allocated to the OBJ ddname in BINARY format.
The file c:\temp\PMLINES.lst is sent to the member PMLINES in the data set allocated to the LIST ddname in ASCII format.
The file c:\temp\temp.msg is sent to the data set 'SCLMUSR.C.MSGS' in ASCII format.

B OBJ:PMLINES c:\temp\PMLINES.obj
A LIST:PMLINES c:\temp\PMLINES.lst
A 'SCLMUSR.C.MSGS' c:\temp\temp.msg