Communication media

Related topics

In this topic...

About the communication media CFTCOM

The CFTCOM object defines the communication media used by Transfer CFT. You can define as many CFTCOM objects as needed. Depending on the system, you can set the communication medium to:

  • One or more shared files: requests are entered in a file, which is periodically scanned by the Transfer CFT
  • A mailbox
  • A synchronous communication medium supported by the TCP/IP network

z/OS: You must define one communication file for BATCH/TSO applications and one for CICS applications, if needed.

Windows: In a stand-alone configuration, the recommended communication method is the mailbox. On a LAN, requests made by Windows applications concerning a Transfer CFT which is not on the same computer can only be accomplished via a file.

The CFTCOM command enables Transfer CFT to open the media communicating with applications. Depending on the system, it is possible to use one or more of the following media:

  • One, or more, shared files (parameter setting TYPE = FILE)
    Requests are entered in this file (or files) which CFT periodically scans. The presence of Transfer CFT is not required to deposit requests unless such requests saturate the file. A CFTCOM command then defines a communication file and the frequency with which it is scanned by Transfer CFT.
  • A Transfer CFT mailbox (parameter setting TYPE = MBX)
    The CFTCOM command allows CFT to connect to a mailbox defined by its logical name
  • A synchronous communication medium supported by the TCP/IP network (parameter TYPE= TCPIP)

The communication media which can be used for each system are indicated in the OS specific Installation and Operations Guide.

The declaration of the communication medium used by a requesting application program must be consistent with the media opened by Transfer CFT:

  • Command CONFIG TYPE = COM, ... of the CFTUTIL utility
  • COM function of programming interfaces
  • 7 option – Transfer CFT characteristics

z/OS (MVS)

You must define one communication file for BATCH/TSO applications and one for CICS applications (if needed).

Windows

In a "stand-alone" operating configuration, requests made by Windows 3 Transfer CFT applications concern the Transfer CFT and so in this case, the recommended communication method is the mailbox.

In a local area network operating configuration, requests made by Windows applications concern a Transfer CFT thatis not on the same computer. In this scenario, communication can only be accomplished via a file.

What is a service file medium

Transfer CFT medium refers to any data support or local communication means used by Transfer CFT. A distinction is made between the media:

  • Accessed by the Transfer CFT
  • Accessed by the Transfer CFT utility
  • Used by the interactive functions
  • Used by the programming interface

Definitions

The following terms are used in this section:

  • PHYSICAL FILE which describes the name and physical location of a file type medium
  • If the file name begins with a reserved character, designated by char-file - see the Transfer CFT Operations Guide corresponding to your OS, this is a logical name interpreted by Transfer CFT
  • MAILBOX to designate an inter-task communication support (non file) not limited to the tasks of the Transfer CFT alone; this concept is only pertinent for certain systems. Refer to the Transfer CFT Operations Guide corresponding to your OS
  • CFTIN and CFTOUT for standard task input/output
  • TCP synchronous medium to designate a communication channel

The Transfer CFT medium names can be set up for the:

  • Programming interface (catalog name, communication medium name with the Transfer CFT): by the OPEN and COM services
  • Transfer CFT: CFTPARM, CFTCOM, CFTCAT, CFTLOG, CFTACCNT objects (the name of the Parameter file cannot be changed)
  • Transfer CFT utility: CONFIG command
  • Interactive functions: the customization function is used to set the names of the Parameter, Partner, Catalog and Log files, and the Transfer CFT communication medium

Transfer CFT media files

You cannot change the name of the parameter file . It constitutes the Transfer CFT anchor point containing all the data defined by the parameter setting, and in particular the names of the other files and media. However, you can establish a correspondence between this logical name and a physical name in the flow of CFT activation commands.

The names of the other Transfer CFT media are defined by parameter setting, although Transfer CFT has default values.

Transfer CFT media by type of object and parameter

Object Parameter File type described

CFTCAT 

FNAME 

Catalog file 

CFTCOM 

FNAME 

Communication medium 

CFTLOG 

FNAME
AFNAME 

Log files 

CFTACCNT 

FNAME
AFNAME 

Statistics files 

CFTPARM 

PARTFNAM 

Partner file 

CFTXLATE 

FNAME 

File containing the description of a translation table 

CFTDEST 

FNAME 

File containing a list of partners 

CFTAUTH 

FNAME 

File containing a list of authorized or prohibited IDFs 

CFTPARM 

EXEC ... 

End-of-transfer procedures 

CFTLOG 

EXEC 

Log switching procedure 

CFTACCNT 

EXEC 

Statistics file switching procedure 

Depending on the system, Transfer CFT supports the following communication media:

  • Direct organization file (relative)
  • Mailbox
  • TCP synchronous medium

For a communication medium based on TCP/IP:

  • Host name
  • Configuration file name

Refer to the Transfer CFT Operations Guide corresponding to your OS.

CFTUTIL media utility

Use the CFTUTIL utility command CONFIG to set the names of the media it accesses, as presented in the table:

CONFIG command TYPE parameter File type described

PARM 

Parameter file 

PART 

Partner file 

CAT 

Catalog file 

COM 

Communication medium 

INPUT 

Input data medium 

OUTPUT 

Output data medium 

By default, in the absence of the CONFIG command, the media accessed by the utility are defined in the Transfer CFT Operations Guide corresponding to your OS.

Depending on the operating system, the media names may be physical files or logical files. Refer to the Transfer CFT Operations Guide corresponding to your OS.

Depending on the system, the Transfer CFT utility supports the following communication media:

  • Direct organization file (relative)
  • Mailbox
  • TCP synchronous medium

For a communication medium based on TCP/IP:

  • Host name
  • Configuration file name

Programming interface media

The programming interface provides the following services:

  • Access to the transfer catalog
  • Dispatch of commands to CFT

The tables below list the media names by service for the Cobol and C language applications.

Media names by service in COBOL language interface

Service Command Parameter File type described

CFTI 

OPEN 

D-CAT 

Catalog file 

CFTU 

COM 

D-COM 

CFT communication medium 

Media names by service in C language interface

Service Command Parameter File type described

cftai 

OPEN 

cat 

Catalog file 

cftaix 

OPEN 

cat 

Catalog file 

cftau 

COM 

param 

Transfer CFT communication medium 

The default names of the media accessed by the programming interface, CATALOG file and COMMUNICATION medium, are defined in the Transfer CFT Operations Guide corresponding to your OS.

Depending on the system, the programming interface supports the following communication media:

  • Direct organization file
  • Mailbox (default name MBXCFT)
  • TCP synchronous medium

And in the case of a communication medium based on TCP/IP

  • Host name
  • Configuration file name

Refer to the Transfer CFT Operations Guide corresponding to your OS.

Interactive function media

The interactive function media are defined by the customization function of this component. The table below indicates, for each field, the file type described:

Field File type described

Parm 

Parameter file 

Part 

Partner file 

Cat 

Catalog files 

Log1 

Log files 

Log2 

 

Com 

Monitor communication medium 

If this function is not activated, the media accessed are those defined at the time the product is installed.

Depending on the system, the interactive functions support the following communication media:

  • Direct organization file
  • Mailbox (default name MBXCFT)
  • TCP synchronous medium

For a communication medium based on TCP/IP:

  • Host name
  • Configuration file name

Refer to the Transfer CFT Operations Guide corresponding to your OS.

Communication media characteristics

  • For file communication:

The Transfer CFT can be inactive at the time the commands assigned to it are issued, to the limit of the file size. Commands are taken into account at the time the Transfer CFT is activated, if a CFTCOM command relative to this communication file has been defined. A communication file can be created by the CFTFILE command.

  • For Mailbox communication:
    • MVS or z/OS These communications allow all commands to be submitted to the Transfer CFT , even if it is absent.
    • VMS Communication is only possible if the Transfer CFT is present. This mechanism allows users of a group other than the Transfer CFT group to submit commands to Transfer CFT.
  • For TCP synchronous mediums:
    • Communication is only possible if the Transfer CFT is present. To retrieve the IDT and the IDTU values of the transfer, you can use the variables %_CAT_IDT% and %_CAT_IDTU%.

Example

SEND
PART = PART1
IDF = TEST1

 

Then...

LISTCAT
IDT = %_CAT_IDT%

Related Links