Send processing messages

An error occurred during access of the Send file. (ML=E)

There may be an error in the DASD. Perform error recovery and then carry out the Send Request again.

An error occurred while the Send processing was in progress. (ML=E)

Take the appropriate measures for the communication error code, and then carry out resending.

An error occurred in the execution of the communication macro. (ML=E)

Take the appropriate measures for the communication error code, and then carry out resending.

Failed to allocate the Send file. (ML=E)

Take the appropriate measures for the status code and information code, and then carry out the Send File request again.

Failed to release the Send file. (ML=E)

Although the Send processing ended successfully, rerun the Send program (XRSND).

An error occurred during access of the Send Control file. (ML=E)

Re-create the Send Control file (HULFT.QUEUE).

An error occurred during access of the Send and Receive Log file. (ML=E)

Re-create the Send and Receive Log file.

An error occurred during access of the Send and Receive Management file. (ML=E)

Re-create the Send and Receive Management file.

An internal error has occurred. (ML=E)

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

The Send task ended. (ML=I)

Connected to the host. (ML=I)

Disconnected from the host. (ML=I)

An error occurred on the host on the receiving side. (ML=E)

Take the appropriate measures for the error on the host on the receiving side, and then carry out resending.

The Send processing ended. (ML=I)

The available memory is insufficient to run this program. (ML=E)

Increase the REGION size and rerun the Send program (XRSND).

Could not connect to the applicable host. (ML=E)

Take the appropriate measures for the communication error code, and then carry out resending.

The Record Count received by the host on the receiving side does not match the Record Count that was sent. (ML=E)

Check the content of the data. If there is an error in the content of the data, resend the data.

Vertical compression is not available, because HULFT on the remote host is Ver. 2 or lower. (ML=E)

Change the value specified for compression.

Code conversion on the host on the receiving side is not available, because HULFT on the remote host is Ver. 2 or lower. (ML=E)

Change the code conversion destination to the host on the sending side.

Started sending from the checkpoint. (ML=I)

The member name does not exist in the Partitioned Organization file. Or, an access error occurred in the Partitioned Organization file. (ML=E)

Check the member name of the Partitioned Organization file. Also, check if the Partitioned Organization file can be used.

The Block Size of the Send file is 0 bytes. (ML=E)

Check the Send file, and try again.

The work file was deleted. (ML=I)

Binary compression is not available, because HULFT on the remote host is Ver. 4 or lower. (ML=E)

Change the specification for the Compression Level.

Multi format transfer is not available, because HULFT on the remote host is Ver. 4 or lower. (ML=E)

Change the specification for the Transfer Type.

The available memory is insufficient to carry out the Direct Transfer. (ML=E)

Increase the REGION size and rerun the Send program (XRSND).

Failed to carry out the Direct Transfer due to one of the following reasons. (ML=E)

1. Failed to read the Send file.

2. The Send file has a file attribute that is not supported for sending by HULFT.

3. While compressing the data to send, the record length after compression exceeded 32767 bytes.

Take the measure with the corresponding number from the following:

1. Check the attributes of the Send file.

2. Check the attributes of the Send file.

3. Send the file with 'N' (None) specified for Compression Preference (COMP) in the Send Management Information.

The length that is specified for the Format ID and the record length of the actual data do not match. (ML=E)

Check if the Format Information matches the actual data.

The length that is specified for the Format ID in the Multi Format Information and the record length of the actual data do not match. (ML=E)

Check if the Format Information matches the actual data.

An error occurred during the Direct Transfer. (ML=E)

Check the Send file and the Send Management Information.

When the Checkpoint Resend File was carried out, all records of the file were skipped. (ML=E)

Check the Send file and Resend Queue Status List.

The Shiftcode Mode cannot be set as space because the target HULFT is Ver. 4 or lower. (ML=E)

Change the Shiftcode Mode.

For the Checkpoint Resend File, the record count or the data size registered in the Send Control file (HULFT.QUEUE) is not the same as the actual data. (ML=E)

Check the actual data and the Resend Queue Status List.

The product of the Transfer Block Length and the Transfer Block Count values is not correct. (ML=E)

If you send files to HULFT Ver.4 or a lower version, specify the Transfer Block Length and the Transfer Block Count in the Send Management Information as values the product of which is '32767' or less.

The Job Information was not found. (ML=E)

Check if the job ID is registered in the Job Information.

Failed to open the Send file. (ML=E)

Check the Send file, and try again.

Failed to delete the Send file. (ML=E)

Look up the Error code and take the appropriate measures.

Failed to clear the Send file. (ML=E)

Look up the Error code and take the appropriate measures.

Conditions to execute PSCHG (Pack Zone Conversion) as specified in the System Environment are not met. (ML=E)

Check the PSCHG settings and sending conditions that are specified in the System Environment, and the version of the remote host.

The record length that is registered in the Format Information and the record length of the Send file do not match. (ML=E)

Check if the content of the Format Information matches the Send file.

The Multiplex Level has been exceeded on the host on the receiving side. HULFT retries connection the number of times that is set for the connect count. (ML=I)

Check the Multiplex Level of HULFT on the receiving side.

A communication error occurred during the Send processing. (ML=I)

Execute auto resending.

Unable to carry out Conversion between EBCDIC Codes. (ML=E)

Check whether the local host supports the EBCDIC Code Set that was specified by the remote host, or if something other than a user table is specified for the EBCDIC Code Set in the Send Management Information.

Cannot execute custom character conversion. (ML=E)

Check if the Kanji Code that could not be converted exists in the custom character table. Or, if there is a Kanji Code that is not registered in the custom character table, you can use the Handling of Unregistered Custom Characters in the System Environment to set the default value without causing an error.

Encryption processing failed. (ML=E)

The detail code in the Send Log shows the EXIT code for the encryption exit routine. Check the detail code.

Conditions do not allow XML transfer. (ML=E)

For multi format transfer, you cannot send files if the Code Conversion is specified as 'No Conversion.'

Could not use the user code table. (ML=E)

Check if user code tables can be used.

Cannot send files in undefined-length record format. (ML=E)

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

HULFT-SAN is not installed. (ML=E)

Install HULFT-SAN.

The Resend Queue List No. reached the maximum value. It will return to '1.' (ML=I)

The Send processing is complete. (ML=I)

Check the detail code in Status codes and detail codes for Send processing.

The Send file attributes are invalid for Sending with RDW. (ML=E)

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

A version inconsistency occurred in the connection to the destination product. (ML=E)

Check the supported version.

Cannot use the speed priority mode. (ML=I)

The Framed Message Transfer Type is changed to the Error Detection Priority mode. Check the version of the host on the receiving side and the Framed Message Transfer Type.

A user table cannot be specified for code conversion to UTF-8. (ML=E)

Check the EBCDIC Code Set parameter in the Send Management Information, and specify something other than a user table.

The data size after code conversion to UTF-8 exceeded 32750 bytes. (ML=E)

Check the sending data to ensure that the data size after code conversion does not exceed 32750 bytes.

You can change the setting of the Handling of Data Exceeded Max Length after code conversion in the System Environment Settings so that HULFT does not return an error when the data size after code conversion exceeds 32750 bytes, and HULFT completes the transfer by cutting the data of byte 32751 and after.

An ID that is 9 bytes or more cannot be specified, because the version of HULFT on the receiving side is HULFT7 or lower. (ML=E)

Specify an ID within 8 bytes.

HULFT will reconnect in HULFT7 communication mode, because the version of HULFT on the receiving side is HULFT7 or lower. (ML=I)

Long messages are invalid when HULFT7 or lower carries out the Receive processing. (ML=W)

The Use HULFT7 Comm. Mode is enabled, even though the version of HULFT on the receiving side is HULFT8 or higher. (ML=I)

HULFT on the receiving side does not support the compression preference that was specified by HULFT on the sending side. (ML=W)

The setting of the Compression Preference will be changed to 'None.' Check the version and product of HULFT on the receiving side.

A protocol error has occurred during the Send processing. (ML=E)

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

Invalid data was received from the communication destination. (ML=E)

Take either of the following measures:

1. Enable the Use HULFT7 Comm. Mode in the Host Information and transfer the data again.

2. Confirm that the communication destination is a process of HULFT.

The processing switches to the Test-run Mode according to the setting on the host on the receiving side. (ML=I)

The Send processing in the Test-run Mode is complete. (ML=I)

The processing has switched to the Test-run Mode according to the setting on the host on the receiving side, but the Transfer Test that includes the host on the receiving side cannot be carried out because the Use HULFT7 Comm. Mode is enabled. (ML=E)

The sending is carried out in the Test-run Mode. (ML=I)

The Transfer Test that includes the host on the receiving side cannot be carried out because the host on the receiving side is a version that does not support the Transfer Test function. (ML=W)

The Transfer Test that includes the host on the receiving side cannot be carried out because the Use HULFT7 Comm. Mode is enabled. (ML=E)

The combination of the code set specified for the Code Set for Transfer (KCODETYPE) in the Host Information and the setting of the EBCDIC Set in the Send Management Information or the Receive Management Information is not supported. (ML=E)

Confirm that the combination of the code set specified for the Code Set for Transfer (KCODETYPE) and the setting of the EBCDIC Set in the Send Management Information or the Receive Management Information is supported.

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

The sending-side transferring is terminated because the version of the receiving-side host does not support instant transfers. (ML=E)

Check the version of the receiving-side host.

The code conversion setting is switched to receiving-side conversion because the sending-side conversion cannot process the code-set combination. (ML=W)

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 not supported. (ML=E)

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.

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

Specify 'Receiving Side' for the Code Conversion in the Send Management Information, and try carrying out the transfer again.

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 not supported. (ML=E)

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.

The Forced Strong Key mode is enabled, but because the remote host is lower than V8.4, communication failed. (ML=E)

Check the version of the receiving-side host.

The Forced Strong Key mode is enabled, but because the Forced Strong Key mode is disabled on the remote host, communication failed. (ML=E)

Check whether the Forced Strong Key mode is enabled on the remote host.

The Forced Strong Key mode is enabled, but because the remote host is a version that does not include a cipher option, communication failed. (ML=E)

Check the specified receiving-side host information.

The registered Format Information and the sending data do not match. (ML=E)

Check if the data type for the applicable field matches the sending data.

The content of the error that occurred during access of the Receive file is displayed. (ML=E)

Look up the SYNAD error messages in DFSM Macro Instructions for Data Sets.

An error occurred while the Send processing was in progress. (ML=E)

Take the appropriate measures for the communication error code, and then carry out resending.

Failed to allocate the Send file. (ML=E)

Take the appropriate measures for the status code and information code, and then carry out the Send File request again.

Failed to release the Send file. (ML=E)

Although the Send processing ended successfully, rerun the Send program (XRSND).

An internal error has occurred. (ML=E)

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

An error occurred on the host on the receiving side. (ML=E)

Take the appropriate measures for the error on the host on the receiving side, and then carry out resending.

The Send processing is complete. (ML=I)

Could not connect to the applicable host. (ML=E)

Take the appropriate measures for the communication error code, and then carry out resending.

Started sending from the checkpoint. (ML=I)

Failed to delete the Send file. (ML=E)

Look up the Error code and take the appropriate measures.

Failed to clear the Send file. (ML=E)

Look up the Error code and take the appropriate measures.

The Multiplex Level has been exceeded on the host on the receiving side. HULFT retries connection the number of times that is set for the connect count. (ML=I)

Check the Multiplex Level of HULFT on the receiving side.

A communication error occurred during the Send processing. (ML=I)

Execute auto resending.

The Send processing is complete. (ML=I)

Check the detail code in Status codes and detail codes for Send processing.

Failed to open the Send Control file. (ML=E)

Re-create the Send Control file (HULFT.QUEUE).

The available memory is insufficient to run this program. (ML=E)

Increase the REGION size and rerun the Send program (XRSND).

Failed to open the Send Log. (ML=E)

Re-create the Send Log.

The available memory is insufficient to run this program. (ML=E)

Increase the REGION size and rerun the Send program (XRSND).

Failed to open the management information file. (ML=E)

Re-create the management information file.

The Host Name of the specified transfer destination is not registered in the DNS or TCP/IP hosts file. (ML=E)

Refer to Installation Manual to check the details of the settings.

The Host Name of the specified transfer destination is not registered in the DNS or TCP/IP hosts file. (ML=E)

Refer to Installation Manual to check the details of the settings.