Working with files and coding

Specific parameters for z/OS

This section describes the parameters and values that are specific to Transfer CFT z/OS and information about:

  • Transfer CFT z/OS specific values
  • Transferable files
  • Filename coding

Platform specific characters

  Description Windows Unix **OpenVMS z/OS IBM i
char_file

Logical name prefix

$ _

No specific character;

logical names are

processed transparently by RMS

x'5B'

285 = £

297 = $

x'4E'

285 = +

297 = +

char_mask Wildcard character ? ? %x

x' 6F

285 = ?

297 = ?

x'6F'

285 = ?

297 = ?

char_unit Separator character (volume) % \01

No volume concept

x' 6C'

285 = %

297 = %

x '5E'

285 = ;

297 = ;

char_symb Symbolic variable prefix & & &

x'50'

285 = &

297 = &

x'6F'

285 = ?

297 = ?

file_symb Character introducing a file name passed to CFTUTIL as a parameter # @ Either # or @

x'7B’

285 = #

297 = £

x'B1'

285 = [

297 = #

char_directory

Character introduced in the path name of the FNAME parameter (CFTRECV) from which a tree structure can be created

+ + +

+

Limited to USS files

+

Limited to HFS files

Transferable files

File characteristics that are found automatically for sending are listed in the following table.

File characteristics

Parameter Found automatically for sending

FSPACE

YES

FLRECL

YES

FBLKSIZE

YES

FRECFM

YES

FTYPE

YES

FTYPE and FRECFM combinations for sending

Type of file to be sent Implicit value of FTYPE Implicit value of FRECFMz

Disk sequential files

 

F/V/U

Members of PDS files (1 transfer per member)

 

F/V/U

Designated version of a file in GDG

 

F/V/U

Multivolume disk file

 

F/V/U

VSAM KSDS or ESDS file

 

F/V

Print file with ASA jump codes (z/OS to z/OS)

A

F/V/U

Print file with machine jump codes (z/OS to z/OS)

M

F/V

Spanned variable format file (z/OS to z/OS)

S

V

Note Variable SPANNED files can be routed through an intermediary Transfer CFT for the PeSIT protocol only (ANY profile). In this case, the file received on Transfer CFT z/OS is always in the ‘U’ format.

The PDS files copied by IEBCOPY are also received in the ‘U’ format, which is compatible with IEBCOPY.

Receiving values for FORG, FTYPE and FRECFM

FORG FTYPE FRECFM   Type of receive file

SEQ

 

F/V/U

Disk sequential file

PART

 

F/V/U

Member of PDS files (1 transfer per member)

SEQ

 

F/V/U

Version designated -1 to 0 of a file in GDG

SEQ

 

F/V/U

Multivolume disk file

DIRECT

 

F/V

VSAM ESDS file

INDEXED

 

F/V

VSAM KSDS file (already exists but empty)

SEQ

A

F/V/U

Print file with ASA jump code (z/OS to z/OS)

SEQ

M

F/V/U

Print file with machine jump code (z/OS to z/OS)

SEQ

S

V

File in spanned variable format (z/OS to z/OS)

SEQ

 

F/V/U

Magnetic tape or cartridge file in position 1 (with STANDARD LABELS)

These values are explicit in CFTRECV or are deduced from the received protocol values.

Related Links