Detail codes related to SAN

1  A difference in the record between the sending side and the receiving side was detected by verification after completion of SAN (FAL) Transfer.

Description:

A difference in the record between the sending side and the receiving side was detected by verification after completion of SAN (FAL) Transfer. The file may have been replaced during the transfer, or dataset writing from a system other than HULFT may have caused a conflict.

Measure:

Transferred data is not guaranteed. Transfer again. Description of the detected difference in the record is output to the dump file. Check the content and identify the cause by analyzing inconsistent data.

2  It was detected by verification after completion of SAN (FAL) Transfer that the record count of the Receive dataset is higher than that of the Send file.

Description:

It was detected by verification after completion of SAN (FAL) Transfer that the record count of the Receive dataset is higher than that of the Send file.

Measure:

The file may have been replaced during the transfer, or dataset writing from a system other than HULFT may have caused a conflict. The transferred data is not guaranteed. Transfer again. The detected record number (a serial number starting with 1) is output to the dump file. Check the content and identify the cause by analyzing inconsistent data.

3  It was detected by verification after completion of SAN (FAL) Transfer that the record count of the Send file is higher than that of the Receive dataset.

Description:

It was detected by verification after completion of SAN (FAL) Transfer that the record count of the Send file is higher than that of the Receive dataset.

Measure:

The file may have been replaced during the transfer, or dataset writing from a system other than HULFT may have caused a conflict. The transferred data is not guaranteed. Transfer again. The detected record number (a serial number starting with 1) is output to the dump file. Check the content and identify the cause by analyzing inconsistent data.

4  There is no permission for writing from the Send process to the file output destination directory of SAN (FAL) Transfer. 

Description:

There is no permission for writing from the Send process to the file output destination directory of SAN (FAL) Transfer. Or, the partition of the dump file output destination has insufficient space.

Measure:

Transferred data is not guaranteed. Transfer again. Grant permission for writing from the Send process to the directory specified by raiddumpdir or tmpdir in the System Environment Settings file and check free space in the specified partition. As output of dump file has also failed, you cannot check the detected difference in data. When both the Send file and the Receive dataset remain, compare each content and identify the cause of the difference by analyzing inconsistent data.

240  Failed to open data set for SAN (FAL) Transfer.

Description:

Failed to open data set for SAN (FAL) Transfer.

Measure:

Check whether the value specified for send and receive data set at the Mainframe side specifies the shared volume and also check the UNIX volume definition file contents or send and receive daemon startup directory.

241  A value for Code conversion for SAN (FAL) Transfer is set to Mainframe side. 

Description:

A value for Code conversion for SAN (FAL) Transfer is set to Mainframe side.

Measure:

The Code Conversion can be executed only on the UNIX side at the time of a SAN-Transfer.
Specify a value that corresponds to the UNIX side for Code Conversion in the Send Management Information.

242  A Volume Serial Number has not been set in partner side Mainframe receive management information.

Description:

Volume Serial is not specified in the Receive Management Information on the Mainframe side that is the destination of SAN Transfer or the Receive daemon on the remote host Mainframe cannot execute SAN Transfer.

Measure:

Set Volume Serial in the Receive Management Information on Mainframe.

243  The size of the Send file for SAN (FAL) Transfer is 2 GB or more.

Description:

The size of the Send file for SAN (FAL) Transfer is 2 GB or more.

Measure:

This error is detected when '2' or higher is specified for RAIDONLY that is specified with JCL at the startup of the Receive daemon on Mainframe. Data of 2GB or more cannot be transferred due to the limitation of FAL. Execute transfer via LAN. To execute transfer via LAN, specify '1' or lower for RAIDONLY that is specified with JCL at the startup of the Receive daemon on Mainframe.

244  The file to be sent in SAN (FAL) Transfer contains a record longer than the dataset record length on the receiving side.

Description:

The file to be sent in SAN (FAL) Transfer contains a record longer than the dataset record length on the receiving host.

Measure:

The transfer record length may have increased due to code conversion. Set a longer record length of the Receive dataset on Mainframe. Or, do not specify RECCHK that is specified with JCL at the startup of the Receive daemon on Mainframe. Without RECCHK specified, a part that cannot be included in a record is discarded and stored in the dataset.

245  Unable to load the library required for HULFT-SAN (FAL).

Description:

Unable to load the library required for HULFT-SAN (FAL).

Measure:

FAL HULFT-SAN option is not installed, or there is a problem in the environment. Check the environment.

250  Unable to load the shared library required for HULFT-SAN (XLD).

Description:

Unable to load the shared library required for HULFT-SAN (XLD).

Measure:

XL Data Mover API is not installed, or there is a problem in the environment. Check the environment.

251  HULFT-SAN (XLD) is not installed in the receiving host.

Description:

HULFT-SAN (XLD) is not installed in the receiving host.

Measure:

Check the environment. Or, execute file transfer via LAN.

252  There is an error in the message received in SAN (XLD) Transfer.

Description:

There is an error in the message received in SAN (XLD) Transfer.

Measure:

An error may have occurred while receiving data. Check the environment, then retry the transfer.

253  There is an error in the message received in SAN (XLD) Transfer.

Description:

There is an error in the message received in SAN (XLD) Transfer.

Measure:

An error may have occurred while receiving data. Check the environment, then retry the transfer.

370  The record length is inconsistent between the Send file and the Format Information.

Description:

The record length is inconsistent between the Send file and the Format Information.

Measure:

Check the Send file or the Format Information.

371  Failed to open the file on the shared volume or the Send file.

Description:

Failed to open the file on the shared volume or the Send file.

Measure:

If SAN-Transfer has never been executed before, check the permissions for the volume definition file and for the special device described in the file. In an environment where SAN-Transfer has already been executed, check that the volume serial of the shared volume in send management information on the remote host Mainframe has been set correctly and that the shared volume line has been described correctly in the volume definition file. When you want to execute LAN-Transfer, specify '1' or less for RAIDONLY that is specified in JCL at the startup of the Send daemon. Also, when opening of send data set failed, check that send data set exists.

372  Failed to read the file on the shared volume in SAN (FAL) Transfer.

Description:

Failed to read the file on the shared volume in SAN (FAL) Transfer.

Measure:

If SAN-Transfer has never been executed before, check the permissions for the volume definition file and for the special device described in the file. If SAN-Transfer has been executed before, check that the volume serial of the shared volume is correctly set in the Receive Management Information on the remote host Mainframe and that the shared volume line is correctly described in the volume definition file.

373  An error occurred in memory operation during the verification of SAN (FAL) Transfer.

Description:

An error occurred in memory operation during the verification of SAN (FAL) Transfer.

Measure:

HULFT is in unstable condition. Restart HULFT.

374  Host Type for the remote side of SAN (FAL) Transfer is defined with a host type other than 'Mainframe.'

Description:

Host Type for the remote side of SAN (FAL) Transfer is defined with a host type other than 'Mainframe.'

Measure:

SAN-Transfer is not available when the host type of the remote-side host is not Mainframe. Change the host type to Mainframe, or change the RAIDONLY setting.

375  It was detected by verification after completion of SAN (FAL) Transfer that the record count of the Send dataset is lower than that of the Receive file.

Description:

It was detected by verification after completion of SAN (FAL) Transfer that the record count of the Send dataset is lower than that of the Receive file. Or, variable-length 0-byte data is received in binary.

Measure:

The file may have been replaced during the transfer, or dataset writing from a system other than HULFT may have caused a conflict. The transferred data is not guaranteed. Transfer again. The detected record number (a serial number starting with 1) is output to the dump file. Check the content and identify the cause by analyzing inconsistent data.

376  It was detected by verification after completion of SAN (FAL) Transfer that the record count of the Receive file is lower than that of the Send dataset.

Description:

It was detected by verification after completion of SAN (FAL) Transfer that the record count of the Receive file is lower than that of the Send dataset.

Measure:

The file may have been replaced during the transfer, or dataset writing from a system other than HULFT may have caused a conflict. The transferred data is not guaranteed. Transfer again. The detected record number (a serial number starting with 1) is output to the dump file. Check the content and identify the cause by analyzing inconsistent data.

377  Writing to the Receive file in SAN (FAL) Transfer failed.

Description:

Writing to the Receive file in SAN (FAL) Transfer failed.

Measure:

There may be an operating system error or a file system error. Check the operating system and the file system environment.

378  A difference in the record between the sending side and the receiving side was detected by verification after completion of SAN (FAL) Transfer. 

Description:

A difference in the record between the sending side and the receiving side was detected by verification after completion of SAN (FAL) Transfer. The file may have been replaced during the transfer, or dataset writing from a system other than HULFT may have caused a conflict.

Measure:

Transferred data is not guaranteed. Transfer again. Description of the detected difference in the record is output to the dump file. Check the content and identify the cause by analyzing inconsistent data.