List of detail codes for Send File on the Management Console

An error occurred during VTOC search.

The file does not exist on the volume.

The specified file does not exist in the catalog.

One of the following may be the cause:

• The specified DD name is not defined in the JCL.

• There is an error on the volume.

• The organization of the specified file is invalid.

The file does not exist on the volume.

The member name does not exist for the Partitioned Organization file registered in the Send Management Information.

Or, an access error occurred in the Partitioned Organization file.

An I/O error occurred during VTOC search.

Failed to clear or delete the Send file. Check the attributes and usage conditions of the Send file.

The specified Send Management Information does not exist.

Failed to read the specified Send Management Information.

The Transfer Group ID registered in the Send Management Information does not exist.

The Format ID registered in the Send Management Information does not exist.

Failed to read the Send Control file (HULFT.QUEUE).

Failed to read the Send Control file (HULFT.QUEUE).

Failed to read the Format Information registered in the Send Management Information.

The Transfer Group ID registered in the Send Management Information does not exist.

Failed to read the Transfer Group ID registered in the Send Management Information.

Failed to clear the Send file.

An internal reader error has occurred.

The maximum number that the Send Control file (HULFT.QUEUE) can store has been exceeded. Reduce the number of records in the Send Queue to 0, and try again.

The Multi Format ID registered in the Send Management Information does not exist.

Failed to read the Multi Format ID registered in the Send Management Information.

The keys for the Multi Format Information and the Send file registered in the Send Management Information do not match. Check the Send file and the Multi Format Information.

The Pre-send Job ended in error or time-out.

Check the Pre-send Job and time-out duration.

The following message is displayed on the console:

* XRSNDISS * EXEC PREJOB FAILURE RC=code

For details about the code, see Error code list (decimal number).

If any of the following conditions are met, multicasting is not possible.

• Send mode is other than Keep for the Direct Transfer.

• Send mode is Lock for the Work File Transfer.

• Send mode is Clear or Delete for the Work File Transfer, and the

  Post-send Clear Mode in the System Environment Settings is 'A.'

Failed to acquire the UNIT information specified in the Send Management Information. Check if the Send File was executed from MT.

Failed to delete the Send file.

The data set format of the Send file is not supported by HULFT.

The record length of the Send file is 0 bytes.

The Block Size of the Send file is 0 bytes.

You cannot clear Partitioned Organization files or VSAM files.

You cannot delete Partitioned Organization files or VSAM files.

The specified Send file is a Partitioned Organization file. Specify a member name.

The specified Send file is a Partitioned Organization file. Specify a member name.

The Format ID registered in the Send Management Information does not exist.

The Multi Format ID registered in the Send Management Information does not exist.

This is HULFT system error. Contact your Technical Support Service representative, if you have already concluded the Technical Support Agreement.

A user table cannot be specified for code conversion to UTF-8.

The record length exceeded 32750 bytes after code conversion to UTF-8.

The maximum number that the Send Control file (HULFT.QUEUE) can store has been exceeded. Execute the Counter Reset for Send SEQ or Resend Queue List command, and try again.

A function that cannot be used with the version of HULFT at the communication destination is specified.

• A string that is 9 bytes or more is specified for a field such as the File ID.

If the Code Set for Transfer (cs4trnsfr) in the System Environment Settings is 'UTF-8,' sending-side conversion cannot be carried out.

Confirm that the combination of the code set of the remote host that is specified for the Code Set for Transfer (KCODETYPE) in the Host Information and the code set that is specified for the Code Set for Transfer (CS4TRNSFR) in the System Environment Settings is supported.

For details, refer to the explanation on Convertible Code Set Combinations in Code Conversion Manual.

For direct transfer and Sending with RDW, only files in variable-length record format and with a record length of 32752 bytes or less can be sent.

Use of plus signs is not supported in relative generation numbers for generation files.

There is invalid data in numerical fields for format or multi format transfer.

Use tracks or cylinders as the space unit for the creation of work files.

Failed to acquire the space unit, because the Capacity for the work file is specified as 'O' (Omit).

The work file capacity is insufficient.

Cannot execute custom character conversion.

There is not enough available memory to execute the Send File. Increase the REGION size, and then log on to the terminal on which the Management Console runs.

The length that is specified for the Format ID and the record length of the actual data do not match. Or, the record length of the Send file exceeded 32751 bytes for text transfer.

The key for the Send file does not exist in the Multi Format Information.

Relative file names for generational management in the Send file cannot be specified in non-APF-authorized versions.

Failed to open the Send file.

For Work File Transfer and Sending with RDW, only files in variable-length record format and with a record length of 32752 bytes or less can be sent.

HULFT does not support files in undefined-length record format.

The user code table is not set.

The Send processing ended unsuccessfully. 'xxx' shows the system abend code. Refer to the system message.

This is an error code of the DYNALLOC macro. Refer to Authorized Assembler Services Guide.