Hitachi MK-96RD647-01 Verifying Mainframe Dataset Requirements, 11 z/OS Dataset Requirements

Verifying Mainframe Dataset Requirements

FAL and FCU have specific requirements for the FX source and target datasets. Table 3-11specifies the requirements for FX datasets. The FCU GUI (see sections Performing File Transfer Operations - UNIX and Performing File Transfer Operations – Windows) allows the user to display the dataset attributes and verify the dataset requirements. FCU for UNIX (version 01-01- 41 and later) also provides the listvol function to display z/OS dataset attributes without using the GUI. The FXotm target dataset (which can also be an FXoto intermediate dataset) must be created and properly configured before the FX operation is performed. FCU does not support automatic expansion of the extent during FXotm operations. The FX ALC utility allocates intermediate datasets in accordance with the requirements specified below.

Table 3-11 z/OS Dataset Requirements

	Item		Requirement(s)
	Dataset organization		SAM (sequential-access method). FAL/FCU does not support any other DO types (e.g.,
	(DO) type		DAM, VSAM, PAM). If a non-SAM dataset is specified, FAL/FCU will return an error.
			Multiple-volume datasets are not supported. FAL/FCU can only process the portion within one logical volume.
	Dataset name		No spaces. If FAL/FCU encounters a space, it will accept the characters before the space
			as the dataset name and continue processing.
	Record format (RF)		Fixed-length or variable-length record format. FAL/FCU does not support undefined-
			length or spanned record formats. If an illegal RF is detected, FAL/FCU will return an error.
			No key. If a record with a key is accessed, FAL/FCU will return an error.
			For FXotm, the record format of the target dataset must be preconfigured to match the record format of the data
			entities in the source file.
			For VSE source and target datasets, the VSE record option must be used to specify the RF.
	Block length (BL)		Any length within the extent supported by the OS. If an illegal BL is detected, FAL/FCU will
			return an error.
			For FXotm, the block length of the target dataset must be preconfigured to match the block length of the data
			entities in the source file.
			For VSE source and target datasets, the VSE record option must be used to specify the BL.
	Record length (RL)		Any length within the extent supported by the OS. If an illegal RL is detected, FAL/FCU will
			return an error.
			Note: FAL/FCU cannot process a variable-length dataset which includes a record with no
			data entity (RL = 4).
			For FXotm, the record length of the target dataset must be preconfigured to match the record length of the data
			entities in the source file.
			For VSE source and target datasets, the FCU VSE record option must be used to specify the RL.
	Track format		Standard record 0 (R0). FAL/FCU cannot process tracks with nonstandard R0.
	VTOC		For MVS: standard or index VTOC. For an index VTOC, FAL/FCU ignores the index and
			accesses the entire VTOC sequentially.
			For VSE: The user must specify the RF, BL, and RL using the FCU VSE record option.
			Note: The FAL functions cannot be used on VSE datasets.
	Database file		Direct access is not supported; must be converted to a SAM file.
3-32		Preparing for Cross-OS File Exchange Operations

Hitachi USP V Cross-OS File Exchange User’s Guide