Instant transfer messages

HUL1000I

HULSNDGO(HULS) START

Description:

Execution of the Instant Transfer Send File Issuance command starts.

HUL1001I

SEND FILE SUCCESSFUL ENDED, CHECK SEND LOG, FID=_INSTANT_TRANSFER_

Description:

The Send File Issuance command was issued.

Measures:

Check the Send Log and the console on the sending-side host. (FILEID=_INSTANT_TRANSFER_)

HUL1002E

SEND FILE FAILED

Description:

Failed to issue the Send File Issuance command.

HUL1003I

SENDING FILE ENDED RC=code

code:

Status code (Refer to Table 2.17 Status Codes.)

Description:

The send processing was completed successfully.

Table 2.17 Status Codes

Status Code

Messages

0

Transfer to all the hosts ended successfully.

Or, transfer to several of the hosts was canceled. (*1)

4

Transfer to several of the hosts ended unsuccessfully.

8

Transfer to all the hosts ended unsuccessfully.

78

Transfer to all the hosts was canceled.

79

Transfer to several of the hosts was canceled. (*1)

9999

The transfer in the Send Queue was canceled.

*1

:

If the Handling of Cancellation of Synchronous Transfer (SCANMODE) in the System Environment Settings is specified as "N", the value "0" is set. If "A" is specified, the value "79" is set.

HUL1004E

SENDING SIDE ERROR, CHECK SEND LOG, FID=_INSTANT_TRANSFER_

Description:

An error occurred on the host on the sending side.

Measures:

Check the Send Log and the console on the sending-side host.

(FILEID=_INSTANT_TRANSFER_)

HUL1005E

RECEIVING SIDE ERROR, CHECK RECEIVE LOG, FID=_INSTANT_TRANSFER_

Description:

An error occurred on the host on the receiving side.

Measures:

Check the Receive Log and the console on the receiving-side host.

(FILEID=_INSTANT_TRANSFER_)

HUL1006E

SYNC FAILED, CHECK SEND/RECEIVE LOG FID=_INSTANT_TRANSFER_

Description:

An error occurred during transfer.

Measures:

Check the logs and consoles on the sending-side host and receiving-side host.

(FILEID=_INSTANT_TRANSFER_)

HUL1007I

SYNC TRASFERRING IN PROGRESS

Description:

Synchronous Transfer is in progress.

HUL1008E

SEND PROGRAM IS NOT RUN

Description:

Because the Send program has not been run, the Synchronous Transfer cannot be executed, and the command is terminated.

Measures:

Run the Send program, and execute the command again.

HUL1009E

XRQUE OPEN FAILED RC=code-fdbk

code:

Status code (Refer to File access error code list.)

fdbk:

Detail code of the VSAM macro (Refer to DFSMS Macro Instructions for Data Sets.)

Description:

Failed to open the send control file.

Measures:

Look up the detail code and take the appropriate measures.

HUL1010E

XRQUE PUT FAILED RC=code-fdbk

code:

Status code (Refer to File access error code list.)

fdbk:

Detail code of the VSAM macro (Refer to DFSMS Macro Instructions for Data Sets.)

Description:

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

Measures:

Look up the detail code and take the appropriate measures.

HUL1011E

XRQUE NOT FOUND FILE=quefile

Description:

The send control file does not exist.

Measures:

Check if the correct send control file is specified for Send Control File to Issue Instant Transfer (INSTTRANSCMDQUE) in the System Environment Settings.

HUL1012E

XRQUE FREE FAILED

Description:

Failed to release the send control file.

Measures:

Log off the user who uses HULSNDGO, or use the FREE command of the operating system to release the send control file.

HUL1013E

COMMAND PARAM CHECK ERROR RC=code-fdbk

code:

Status code for the command parameter check

fdbk:

Detail code for the command parameter check

Description:

An error occurred during the command parameter check.

Measures:

Correctly specify the parameter by referring to the chapter about HULSNDGO in Operation Manual, and try again.

HUL1014E

MODIFY COMMAND ISSUE FAILED RC=rtncd

Description:

Failed to issue the MODIFY command for the Send File request.

Measures:

Check the error of the internal reader. If you cannot resolve the problem and you have already entered into the Technical Support Agreement, contact your Technical Support Service representative.

HUL1015E

SEND FILE DSORG ERROR, CHECK DSORG

Description:

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

Measures:

Check the data set organization of the Send file.

HUL1016E

SEND FILE RECFM ERROR, CHECK RECFM

Description:

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

Measures:

Check the data set format of the Send file.

HUL1017E

SEND FILE NOT SUPPORTED : LRECL=0

Description:

The Record Length of the Send file is 0 bytes.

Measures:

Check the Record Length of the Send file.

HUL1018E

SEND FILE NOT SUPPORTED : BLKSIZE=0

Description:

The Block Size of the Send file is 0 bytes.

Measures:

Check the Block Size of the Send file.

HUL1019E

XRQUE ACCESS FAILED RC=code-fdbk

code:

Status code (Refer to File access error code list.)

fdbk:

Detail code of the VSAM macro (Refer to DFSMS Macro Instructions for Data Sets.)

Description:

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

Measures:

Look up the detail code and take the appropriate measures.

HUL1020E

XRQUE DELETE ERROR RC=code-fdbk

code:

Status code (Refer to File access error code list.)

fdbk:

Detail code of the VSAM macro (Refer to DFSMS Macro Instructions for Data Sets.)

Description:

Failed to delete an unsent record.

HUL1022W

SEND FILE ATTRIBUTE GET FAILED RC=code

code:

Status code (Refer to Table 2.18 .)

Description:

Cannot acquire the attribute information for the Send file.

Measures:

Look up the status code and take the appropriate measures.

Table 2.18 Status Codes

Status Code

Error Message

0001

An error occurred in the OBTAIN macro.

0002

The data set does not exist on the applicable volume.

0003

The data set does not exist in the catalog.

Other than above

Refer to the DYNALLOC macro error codes in MVS/ESA SP Authorized Assembler Services Reference ALE-DYN.

HUL1023E

INSUFFICIENT STORAGE RC=code

Description:

The available memory is insufficient.

Measures:

Increase the available REGION size and try again. If you cannot resolve the problem and you have already entered into the Technical Support Agreement, contact your Technical Support Service representative.

HUL1026E

COMMAND PARAM ERROR. REENTER PARAM

Description:

There is an error in the command parameter of the interactive command.

Measures:

Enter it again.

HUL1027E

TGET ERROR RC=code

code:

Status code for TGET

Description:

An error occurred for the TGET macro in the interactive command.

Measures:

Contact your Technical Support Service representative, if you have already concluded the Technical Support Agreement.

HUL1029E

PO FILE MEMBER ERROR

Description:

A member name is not specified for the send file which is a partitioned file.

Measures:

Include the member name when you specify the Send file.

HUL1032I

HULSNDGO(HULS) ENDED RC=code

code:

Status code for HULSNDGO

Description:

The Instant Transfer Send File Issuance command is complete.

Measures:

If the status code is not 0, take the appropriate measures according to the content of the error message that is output.

HUL1033E

INSTTRANSCMDQUE ALLOC ERROR RC=code-fdbk

code:

Status code for DYNALLOC

fdbk:

Detail code for DYNALLOC

Description:

Failed to allocate the file specified for Send Control File to Issue Instant Transfer (INSTTRANSCMDQUE) in the System Environment Settings.

Measures:

Look up the status code and detail code, and take the appropriate measures.

HUL1034E

RCVLOC UTF-8 CONVERSION ERROR

Description:

An error has occurred during the attempt to convert the RCVLOC parameter into UTF-8.

Measures:

Refer to the chapter about HULSNDGO in Operation Manual to check the content that is specified for the RCVLOC parameter. If you cannot resolve the problem and you have already entered into the Technical Support Agreement, contact your Technical Support Service representative.

HUL1035E

RCVFILE UTF-8 CONVERSION ERROR

Description:

An error has occurred during the attempt to convert the RCVFILE parameter into UTF-8.

Measures:

Refer to the chapter about HULSNDGO in Operation Manual to check the content that is specified for the RCVFILE parameter. If you cannot resolve the problem and you have already entered into the Technical Support Agreement, contact your Technical Support Service representative.

HUL1036E

STRONG KEY MODE ERROR

Description:

"1" (Enabled) is specified for Forced Strong Key Mode (STRONGKEYMODE).

Measures:

Specify "0" (Disabled) for Forced Strong Key Mode (STRONGKEYMODE), and try again.

HUL1037E

UNDEFINED PARAM ERROR PARAM=parameter

parameter:

Parameter where the error occurred

Description:

The specified parameter does not exist.

Measures:

Check the content of the parameter, and try again.

HUL1038E

DATASET NAME ERROR PARAM=parameter

parameter:

Parameter where the error occurred

Description:

It does not comply with the data set naming conventions for Mainframe.

Measures:

Check the content of the parameter, and try again.

HUL1039E

INVALID SINGLE QUOTES

Description:

There is an error in the usage of single quotation marks.

Measures:

Check the content of the command parameter, and try again.

HUL1040E

PARAM DUPLICATE ERROR PARAM=parameter

parameter:

Parameter where the error occurred

Description:

Duplicate specifications exist for the parameter.

Measures:

Check the content of the parameter, and try again.

HUL1041E

BRACKETS ERROR

Description:

There is an error in the usage of brackets.

Measures:

Check the content of the command parameter, and try again.

HUL1042E

VALUE ERROR PARAM=parameter

parameter:

Parameter where the error occurred

Description:

The value is incorrect.

Measures:

Check the content of the parameter, and try again.

HUL1043E

NUMERIC ERROR PARAM=parameter

parameter:

Parameter where the error occurred

Description:

The parameter does not consist of numbers.

Measures:

Check the content of the parameter, and try again.

HUL1044E

REQUIRED PARAM MISSING PARAM=parameter

parameter:

Parameter where the error occurred

Description:

The required parameter is not specified.

Measures:

Check the content of the parameter, and try again.

HUL1045E

PLUS SIGN OF GDG IS NOT SUPPORTED

Description:

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

Measures:

Specify only numbers as relative generation numbers for generation files, without using plus signs.