Send File messages
* XRSNDGO * HULFT INFORMATI0N FILE OPEN FAILED R/C=code FDBK=fdbk
- code:
-
Error code (Refer to Error code list.)
- fdbk:
-
Detail code of the VSAM macro (Refer to DFSMS Macro Instructions for Data Sets.)
- Description:
-
Failed to open the Send and Receive Management file (HULFT.FILE).
- Measures:
-
Look up the detail code and take the appropriate measures.
* XRSNDGO * CARD NOTHING
- Description:
-
The XRCRD definition card does not exist.
- Measures:
-
Check the XRCRD definition card in the JCL.
* XRSNDGO * NOT EXIST FILE-ID:fileid
- fileid:
-
File ID
- Description:
-
The file ID on the specified XRCRD definition card does not exist.
- Measures:
-
Check the file ID in the JCL on the XRCRD definition card.
* XRSNDGO * FILE INFORMATION ACCESS ERROR R/C=code FDBK=fdbk
- code:
-
Error code (Refer to Error code list.)
- fdbk:
-
Detail code of the VSAM macro (Refer to DFSMS Macro Instructions for Data Sets.)
- Description:
-
Failed to input and output the Send and Receive Management file (HULFT.FILE).
- Measures:
-
Look up the detail code and take the appropriate measures.
* XRSNDGO * TRANS GROUP=SPACE IS INVALID
- Description:
-
The Transfer Group ID is not specified in the Send Management Information.
- Measures:
-
Specify the Transfer Group ID in the Send Management Information.
* XRSNDGO * FORMAT-ID IS SPACE
- Description:
-
The Format ID is not specified in the Send Management Information.
- Measures:
-
Specify the Format ID in the Send Management Information.
* XRSNDGO * QUEUE INFORMATION FILE OPEN FAILED R/C=code FDBK=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 (HULFT.QUEUE).
- Measures:
-
Look up the detail code and take the appropriate measures.
* XRSNDGO * QUEUE INFORMATION PUT FAILED R/C=code FDBK=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.
* XRSNDGO * MULTI FORMAT INFORMATION ACCESS ERROR R/C=code FDBK=fdbk
- code:
-
Error code (Refer to Error code list.)
- fdbk:
-
Detail code of the VSAM macro (Refer to DFSMS Macro Instructions for Data Sets.)
- Description:
-
Failed to read the Multi Format Information.
- Measures:
-
Look up the detail code and take the appropriate measures.
* XRSNDGO * QUEUE ACCESS ERROR
- Description:
-
Failed to read the Send Control file (HULFT.QUEUE).
* XRSNDGO * QUEUE DELETE ERROR
- Description:
-
Failed to delete the Send Control file (HULFT.QUEUE).
* XRSNDGO * **NORMAL END** FILE-ID:fileid
- fileid:
-
File ID
- Description:
-
Send File ended successfully.
* XRSNDGO * PARAMETER CARD ERROR CARD-NO:nn
- nn:
-
Card No.
- Description:
-
The definition method of the XRCRD definition card for the above card number is incorrect.
- Measures:
-
Check the XRCRD definition card in the JCL.
* XRSNDGO * FORMAT INFORMATION ACCESS ERROR R/C=code FDBK=fdbk
- code:
-
Error code (Refer to Error code list.)
- fdbk:
-
Detail code of the VSAM macro (Refer to DFSMS Macro Instructions for Data Sets.)
- Description:
-
Failed to read the Format Information.
- Measures:
-
Look up the detail code and take the appropriate measures.
* XRSNDGO * FORMAT INFORMATION IS NOT EXIST FORMAT-ID:formatid
- formatid:
-
Format ID
- Description:
-
The Format ID does not exist in the Format Information.
- Measures:
-
Check the Format Information.
* XRSNDGO * TRANS GROUP INFORMATION IS NOT EXIST HGRP-ID:grpid
- grpid:
-
Transfer Group ID
- Description:
-
The Transfer Group ID does not exist in the Transfer Group Information.
- Measures:
-
Check the Transfer Group Information.
* XRSNDGO * TRANS GROUP INFORMATION ACCESS ERROR R/C=code FDBK=fdbk
- code:
-
Error code (Refer to Error code list.)
- fdbk:
-
Detail code of the VSAM macro (Refer to DFSMS Macro Instructions for Data Sets.)
- Description:
-
Failed to read the Transfer Group Information.
- Measures:
-
Look up the detail code and take the appropriate measures.
* XRSNDGO * TRANS WORK FILE CREATE FAILED R/C=code
- code:
-
Status code (Refer to Table 2.1 .)
- Description:
-
Failed to create the work file.
- Measures:
-
Look up the Error code and take the appropriate measures.
Status Code |
Error Message |
---|---|
0001 |
An error occurred during VTOC search. |
0002 |
The file does not exist on the volume. |
0003 |
The specified file does not exist in the catalog. |
0004 |
One of the following may be the cause:
|
0008 |
The file does not exist on the volume. |
0009 |
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. |
000C |
An I/O error occurred during VTOC search. |
C3C1 |
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). |
C3F7 |
There is invalid data in numerical fields for format or multi format transfer. |
C5D9 |
The work file capacity is insufficient. |
C7C9 |
Cannot execute custom character conversion. |
D3D5 |
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. |
D4C6 |
The key for the Send file does not exist in the Multi Format Information. |
D6D7 |
Failed to open the Send file. |
E4E3 |
The user code table is not set. |
Fxxx |
The Send processing ended unsuccessfully. 'xxx' shows the system abend code. Refer to the system message. |
0204 and later |
This is an error code of the DYNALLOC macro. Refer to Authorized Assembler Services Guide. |
* For error codes other than the above, or if the cause of the error code is something different, contact your Technical Support Service representative, if you have already concluded the Technical Support Agreement.
* XRSNDGO * TRANS WORK FILE INSUFFICIENT CAPACITY R/C=C5D9
- Description:
-
The work file capacity is insufficient.
- Measures:
-
Change the 1ST Extent and the Secondary in the Send Management Information.
* XRSNDGO * FORMAT INFORMATION LENGTH ERROR R/C=D3D5
- Description:
-
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.
- Measures:
-
Check if the Format Information matches the actual data. For text transfer, set the Record Length of the Send file to 32751 bytes or less.
* XRSNDGO * FILE LOCK FAILED R/C=code
- code:
-
Detail code (Refer to Error code list.)
- Description:
-
Failed to delete the Send file because it is locked.
- Measures:
-
Look up the detail code and take the appropriate measures.
* XRSNDGO * FILE CLEAR FAILED R/C=code
- code:
-
Detail code (Refer to Error code list.)
- Description:
-
Failed to clear the Send file.
- Measures:
-
Look up the detail code and take the appropriate measures.
* XRSNDGO * SYNC TRANSFER TERMINATED R/C=code FILE-ID:fileid
- fileid:
-
File ID
- code:
-
Status code (Refer to Table 2.2 .)
- Description:
-
Synchronous Transfer to all the hosts is complete.
- Measures:
-
Look up the status code for Send Detail Information Inquiry, and take the appropriate measures.
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. |
* XRSNDGO * ASCII CODE USER TABLE ERROR R/C=E4E3
- Description:
-
The user code table is not set.
- Measures:
-
Either set the user code table, or check the EBCDIC Code Set in the Send Management Information.
* XRSNDGO * MULTI FORMAT INFORMATION IS NOT EXIST MULTI FORMAT-ID:multiformatid
- multiformatid:
-
Multi Format ID
- Description:
-
The Multi Format ID does not exist in the Multi Format Information.
- Measures:
-
Check the Multi Format Information.
* XRSNDGO * MULTI FORMAT ERROR R/C=C4C1
- Description:
-
The Format ID specified for the Multi Format Information does not exist in the Format Information.
- Measures:
-
Check the Format Information and the Multi Format Information.
* XRSNDGO * MULTI FORMAT INFORMATION ERROR R/C=D4C6
- Description:
-
The key for the Send file does not exist in the Multi Format Information.
- Measures:
-
Check if the Send file and the Multi Format Information match.
* XRSNDGO * EXEC PREJOB FAILURE R/C=code FILE-ID:fileid
- fileid:
-
File ID
- code:
-
Error code (Refer to Error code list (hexadecimal number).)
- Description:
-
Failed to execute the Pre-send Job.
- Measures:
-
Look up the Error code (hexadecimal number) and take the appropriate measures.
* XRSNDGO * FILE CLEAR ERROR
- Description:
-
When multicasting, you cannot clear the Send file after send processing is complete.
- Measures:
-
Either change the Post-send Clear Mode in the System Environment Settings to 'B' (Clear after the Send work file is created) before carrying out the Work File Transfer, or specify the Send File Mode as 'K' (Keep).
* XRSNDGO * FILE DELETE ERROR
- Description:
-
When multicasting, you cannot delete the Send file after send processing is complete.
- Measures:
-
Either change the Post-send Clear Mode in the System Environment Settings to 'B' (Clear after the Send work file is created) before carrying out the Work File Transfer, or specify the Send File Mode as 'K' (Keep).
* XRSNDGO * FILE LOCK ERROR
- Description:
-
When multicasting, you cannot lock the Send file.
- Measures:
-
Either stop multicasting, or specify 'K' (Keep) for the Send File Mode to proceed without locking the file.
* XRSNDGO * TRANSFER HOST OR TRANSFER GROUP PARAMETER ERROR
- Description:
-
You cannot specify a host and a transfer group at the same time.
- Measures:
-
Specify either a host or a transfer group.
* XRSNDGO * FILE DELETE FAILED R/C=code
- code:
-
Error code of the DYNALLOC macro (Refer to Authorized Assembler Services Guide.)
- Description:
-
Failed to delete the Send file.
- Measures:
-
Look up the Error code and take the appropriate measures.
* XRSNDGO * DDNAME DCB-INFORMATION GET ERROR
- Description:
-
Cannot acquire the attribute information for the Send file with the DD name specified.
- Measures:
-
Check the Send file or the Send Management Information.
* XRSNDGO * PO OR VSAM FILE CLEAR ERROR
- Description:
-
You cannot clear Partitioned Organization files or VSAM files.
- Measures:
-
Check the Send File Mode in the Send Management Information.
* XRSNDGO * PO OR VSAM FILE DELETE ERROR
- Description:
-
You cannot delete Partitioned Organization files or VSAM files.
- Measures:
-
Check the Send File Mode in the Send Management Information.
* XRSNDGO * PO FILE MEMBER ERROR
- Description:
-
The specified Send file is a Partitioned Organization file.
- Measures:
-
Include the member name when you specify the Send file.
* XRSNDGO * DD=ddname CANNOT LOCK,DELETE,CLEAR : WARNING
- ddname:
-
DD name
- Description:
-
You cannot specify 'L' (Lock), 'D' (Delete), or 'C' (Clear) as the Send File Mode for a file if the DD name is specified.
- Measures:
-
Specify the Send File Mode as 'K' (Keep).
* XRSNDGO * WORK FILE TRANSFER CHANGED : WARNING
- Description:
-
The Work File Transfer is performed, because the conditions do not allow the Direct Transfer.
- Measures:
-
The Send processing is executed. However, check if conditions allow the Direct Transfer for the dynamically specified file.
* XRSNDGO * 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.
* XRSNDGO * LENGTH ERROR DBID:&MSG FILE-ID:fileid
- fileid:
-
File ID
- Description:
-
The length of the specified &MSG is incorrect.
- Measures:
-
You can specify only up to 8 bytes for the Interface DBID.
* XRSNDGO * LENGTH ERROR NORMAL-JOBID:&MSG FILE-ID:fileid
- fileid:
-
File ID
- Description:
-
The length of the specified &MSG is incorrect.
- Measures:
-
You can specify only up to 50 bytes for the Successful Job ID.
* XRSNDGO * LENGTH ERROR ABNORMAL-JOBID:&MSG FILE-ID:fileid
- fileid:
-
File ID
- Description:
-
The length of the specified &MSG is incorrect.
- Measures:
-
You can specify only up to 50 bytes for the Unsuccessful Job ID.
* XRSNDGO * LENGTH ERROR PRE-JOBID:&MSG FILE-ID:fileid
- fileid:
-
File ID
- Description:
-
The length of the specified &MSG is incorrect.
- Measures:
-
You can specify only up to 50 bytes for the Pre-send Job ID.
* XRSNDGO * LENGTH ERROR M/FORMATID:&MSG FILE-ID:fileid
- fileid:
-
File ID
- Description:
-
The length of the specified &MSG is incorrect.
- Measures:
-
You can specify only up to 50 bytes for the Multi/Format ID.
* XRSNDGO * LENGTH ERROR TGRPID:&MSG FILE-ID:fileid
- fileid:
-
File ID
- Description:
-
The length of the specified &MSG is incorrect.
- Measures:
-
You can specify only up to 50 bytes for the Transfer Group ID.
* XRSNDGO * LENGTH ERROR DSNAME:&MSG FILE-ID:fileid
- fileid:
-
File ID
- Description:
-
The length of the specified &MSG is incorrect.
- Measures:
-
You can specify only up to 44 bytes for the Dataset Name.
* XRSNDGO * LENGTH ERROR VOLUME:&MSG FILE-ID:fileid
- fileid:
-
File ID
- Description:
-
The length of the specified &MSG is incorrect.
- Measures:
-
You can specify only up to 6 bytes for the Volume Serial.
* XRSNDGO * LENGTH ERROR WORK-VOLUME:&MSG FILE-ID:fileid
- fileid:
-
File ID
- Description:
-
The length of the specified &MSG is incorrect.
- Measures:
-
You can specify only up to 6 bytes for the Work Volume Serial .
* XRSNDGO * LENGTH ERROR UNIT:&MSG FILE-ID:fileid
- fileid:
-
File ID
- Description:
-
The length of the specified &MSG is incorrect.
- Measures:
-
You can specify only up to 8 bytes for the UNIT Name.
* XRSNDGO * SEND FILE ERROR R/C=code
- code:
-
Error code of the DYNALLOC macro (Refer to Authorized Assembler Services Guide.)
- Description:
-
The Send file cannot be sent.
- Measures:
-
Look up the Error code and take the appropriate measures.
* XRSNDGO * SEND FILE USES DD=ddname DSNAME=dsname
- ddname:
-
DD name
- dsname:
-
Send file name
- Description:
-
The file specified for ddname was sent.
* XRSNDGO * SEND FILE DCB-INFORMATION GET ERROR R/C=code
- code:
-
Status code (Refer to Table 2.3 .)
- Description:
-
Cannot acquire the attribute information for the Send file.
- Measures:
-
Look up the status code and take the appropriate measures. If data was sent from a tape volume or if a migrated file was sent, this message is output even though operation is normal.
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. |
* XRSNDGO * SEND FILE DSORG ERROR
- Description:
-
The data set organization of the Send file is not supported by HULFT.
- Measures:
-
Check the data set organization of the Send file.
* XRSNDGO * SEND FILE RECFM ERROR
- Description:
-
The data set format of the Send file is not supported by HULFT.
- Measures:
-
Check the data set format of the Send file.
* XRSNDGO * SEND FILE RECORD LENGTH ERROR
- Description:
-
The Record Length of the Send file is 0 bytes.
- Measures:
-
Check the Record Length of the Send file.
* XRSNDGO * SEND FILE BLOCK LENGTH ERROR
- Description:
-
The Block Size of the Send file is 0 bytes.
- Measures:
-
Check the Block Size of the Send file.
* XRSNDGO * SEND FILE UNIT ERROR R/C=code
- code:
-
Status code (Refer to Table 2.4 .)
- Description:
-
Failed to acquire the UNIT information specified in the Send Management Information.
- Measures:
-
Either change the UNIT in the Send Management Information, or look up the status code and take the appropriate measures.
* XRSNDGO * MT CANNOT LOCK,DELETE,CLEAR : WARNING
- Description:
-
You cannot specify 'L' (Lock), 'D' (Delete), or 'C' (Clear) for the Send File Mode when the Send processing is carried out directly from a tape volume.
- Measures:
-
Specify the Send File Mode as 'K' (Keep).
* XRSNDGO * GAIJI CONVERT ERROR CODE=code
- code:
-
Kanji Code for which custom character conversion was not possible (displayed as hexadecimal)
- Description:
-
The character that corresponds to the code is not registered in the custom character table.
- Measures:
-
Check if the Kanji Code that could not be converted exists in the custom character table.
* XRSNDGO * THIS MODULE IS NOT APF MODULE. GDG CANNOT BE USED
- Description:
-
If you are using a non-APF-authorized version, you cannot use a relative file name to specify generational management in the Send file.
- Measures:
-
In order to use a relative file name to specify generational management in the Send file, use an APF-authorized version.
* XRSNDGO * THIS MODULE IS CHANGED NON APF MODULE
- Description:
-
Changed from an APF-authorized version to a non-APF-authorized version, because a custom character exit routine module was added to the Send File JCL.
* XRSNDGO * TRANS WORK FILE SPACE UNITS ERROR
- Description:
-
You can create work files only in tracks and cylinders.
- Measures:
-
If the Send file is a VSAM file, you cannot specify 'Omit' for the Capacity for work files.
* XRSNDGO * SMS FILE ALLOC ERROR R/C=code SMSRC=smsrc
- code:
-
Status code for the DYNALLOC macro
- smsrc:
-
Detail code related to SMS (Refer to Table 2.5 .)
- Description:
-
Failed to allocate the SMS Management file.
- Measures:
-
Look up the detail code and take the appropriate measures.
* XRSNDGO * SYSTEM ERROR R/C=code
- code:
-
HULFT system error code
- Description:
-
An internal error has occurred.
- Measures:
-
This is HULFT system error. Contact your Technical Support Service representative, if you have already concluded the Technical Support Agreement.
* XRSNDGO * RDW SEND FILE ATTRIBUTE ERROR
- Description:
-
The Send file attributes are invalid for Sending with RDW.
- Measures:
-
For Sending with RDW, only files in variable-length record format and with a record length of 32752 bytes or less can be sent.
* XRSNDGO * EBCDIC CODESET ERROR
- Description:
-
A user table cannot be specified for code conversion to UTF-8.
- Measures:
-
Check the EBCDIC Code Set parameter in the Send Management Information, and specify something other than a user table.
* XRSNDGO * CODE CONVERSION LENGTH OVER
- Description:
-
The data size after code conversion to UTF-8 exceeded 32750 bytes.
- Measures:
-
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.
* XRSNDGO * MSGL IS UNAVAILABLE
- Description:
-
You cannot use long messages because the Use HULFT7 Comm. Mode is enabled.
Long messages are invalid.
* XRSNDGO * SND DISCRIMINATE NUMBER MAX OVER
- Description:
-
The maximum number that the Send Control file (HULFT.QUEUE) can store has been exceeded.
- Measures:
-
Execute the Counter Reset for Send SEQ or Resend Queue List command, and try again.
* XRSNDGO * ID LENGTH ERROR
- Description:
-
When 'Y' (Yes) is specified for the Use HULFT7 Comm. Mode in the Host Information, you cannot specify an ID of 9 bytes or more for the File ID or the Format/Multi Format ID in the Send Management Information.
- Measures:
-
Specify IDs of 8 bytes or less for the File ID and the Format/Multi Format ID in the Send Management Information.
* XRSNDGO * M/FORMAT-ID IS SPACE
- Description:
-
The Format/Multi Format ID is not registered in the Send Management Information.
- Measures:
-
Check the Send Management Information, and try again.
* XRSNDGO * MULTI FORMAT-ID IS SPACE
- Description:
-
The Format/Multi Format ID is not registered in the Send Management Information.
- Measures:
-
Check the Send Management Information, and try again.
* XRSNDGO * CODE CONVERSION ON WRONG SIDE
- Description:
-
If the Code Set for Transfer (cs4trnsfr) in the System Environment Settings is 'UTF-8,' sending-side conversion cannot be carried out. (ML=E)
- Measures:
-
Specify 'Receiving Side' for the Code Conversion in the Send Management Information, and try carrying out the transfer again.
* XRSNDGO * CODE SET COMBINATION ERROR RC=543
- Description:
-
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)
- Measures:
-
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.
* XRSNDGO *_INSTANT_TRANSFER_ IS A SYSTEM-RESERVED WORD
- Description:
-
Cannot execute the Send File request because the file ID "_INSTANT_TRANSFER_" is a system-reserved word. (ML=E)
* XRSNDGO * SEND FILE CANNOT BE ISSUED IN FORCED STRONG KEY MODE BECAUSE USE HULFT7 COMM. MODE IS SET TO "Y"
- Description:
-
The Forced Strong Key mode is enabled, but because the HULFT7 communication mode is enabled, communication failed.
- Measures:
-
Disable the HULFT7 communication mode and reissue the request.
* XRSNDGO * CIPHER KEY LENGTH ERROR
- Description:
-
The Forced Strong Key mode in the System Environment Settings and the length of the cipher key in the management information do not match.
- Measure 1:
-
If the Forced Strong Key mode is enabled, specify a hexadecimal character string of 64 bytes for the cipher key.
- Measure 2:
-
If the Forced Strong Key mode is disabled, specify an alphanumeric character string of 0 bytes or an alphanumeric character string of 8 to 20 bytes for the cipher key.