This table describes the standard return codes for the SEND FILE and RECEIVE FILE functions of HLLAPI.
| File Transfer Error Codes | ||
| Error Code | Error Description | User Response |
| 200 | The file transfer program cannot attach to the HCON shared memory. | Check that the HCON resource manager is running. |
| 201 | The file transfer program received no response from the HCON resource manager (hcondmn) about the session profile. | Check that the resource manager is running, check to make sure the session profile specified exists and is valid, or use local problem reporting procedures. |
| 202 | A RESTART file exists. The file transfer is stopped. A programmatic file transfer cannot run while a RESTART file exists. | Remove the RESTART file ( i_fxfer.r or x_fxfer.r ) before trying to run the programmatic file transfer. |
| 203 | Cannot get information about the RESTART file. The stat() system call error number is ( fxs_errno ). | Check path name and permissions or use local problem reporting procedures. |
| 209 | Cannot get the path name of the current working directory. | Check path name and permissions, or use local problem reporting procedures. |
| 210 | Two options that cannot be set together have been specified. | Check the flag options for the setting of similar or mutually exclusive options. |
| 211 | An incorrect option has been specified with the CMS host operating system. | |
| 213 | The file transfer program cannot properly connect to the HCON resources. | Check that the resource manager is running, be sure the session profile exists and is valid, or use local problem reporting procedures. |
| 214 | The file transfer program cannot communicate with the HCON resource manager. | Check that the HCON resource manager is running or use local problem reporting procedures. |
| 215 | Return code ( fxs_errno ) from the HCON resource manager is not correct. | Check that the HCON resource manager is running, check that the session is available, or use local problem reporting procedures. |
| 216 | An incorrect option has been specified with the CICS/VS or VSE host operating system. | |
| 217 | The specified CMS host file name is not correct. | Check the specified CMS file name for a missing file type. |
| 218 | An incorrect option has been specified with the CICS/VS or VSE host operating system. The FXC_FIXED option (-F flag) and FXC_VAR option (-V flag) are only valid if the FXC_TNL option (-t flag) or the FXC_TCRLF option (-T flag) is specified. | |
| 219 | The destination file already exists. | Specify the FXC_REPL option (-r flag) or give a different destination file name. |
| 220 | The specified TSO host file name is not correct. | Check the TSO file name either includes an open parentheses or is not enclosed by both open and closed parentheses. |
| 221 | This user cannot run the dfxfer file transfer background process. | Check for the dfxfer process in /usr/bin , check permissions, or use local problem reporting procedures. |
| 222 | The HOME environment variable is not defined. | Set the HOME environment variable to your HOME directory. |
| 223 | An incorrect option has been specified with the CICS or VSE host operating system. The FXC_LRECL option (-L flag) is only valid if the FXC_FIXED option (-F flag) is specified. | |
| 225 | Either the host link address is busy, the host link address does not exist, or there are some remaining messages on the message queues. | If the host link address is busy, try again later. If the host link address is not busy, restart the emulator and try the file transfer again or use local problem reporting procedures. |
| 226 | The host operating system specified is invalid. | Specify TSO, CMS, CICS, or VSE. |
| 227 | An incorrect option has been specified with the CICS or VSE host operating system. The FXC_APPEND option (-a flag) is only valid during a download. | |
| 229 | The f_inputfld value (-I flag) can be set only when issuing a file transfer to a CICS or VSE host operating system. | |
| 230 | The file transfer process cannot get information about the specified file name. | Check that the specified file name exists and has the correct permissions. |
| 253 | Cannot create another dfxfer process at this time. The fork system call error number is ( fxs_errno ). | Check that there is a valid dfxfer process in the directories of the PATH environment variable or use local problem reporting procedures. |
| 259 | Cannot send an interrupt signal to kill the dfxfer file transfer daemon background process. The kill system call error number is ( fxs_errno ). | Kill the dfxfer file transfer daemon process by issuing a kill -9 command to the dfxfer process on the command line or use local problem reporting procedures. |
| 265 | Transfer Status: The file transfer request was cancelled. Diagnostics: An error occurred while trying to create the file transfer buffer shared segment ID. | Try the file transfer again or use local problem reporting procedures. |
| 266 | Transfer Status: The file transfer request was cancelled. Diagnostics: An error occurred while trying to attach to the file transfer buffer shared segment ID. | Try the file transfer again or use local problem reporting procedures. |
| 271 | Cannot initialize the e789x emulator server process. | Check that there is a valid e789x program in the directories of the PATH environment variable or use local problem reporting procedures. |
| 273 | Cannot initialize the e789x emulator server process. The emulator server process ended abnormally. | Check that there is a valid e789x program in the directories of the PATH environment variable, retry the file transfer, or use local problem reporting procedures. |
| 274 | A session profile identifier was not specified or the SNAME environment variable is not set to a valid session profile. | Specify a valid session profile for the session profile parameter or set the SNAME environment variable to a valid session profile name. |
| 276 | Transfer Status: The file transfer request was cancelled. Diagnostics: An error was detected while trying to send the IND$FILE command to the host. | Check that the control unit is running, check that all connections are up, or use local problem reporting procedures. |
| 277 | Transfer Status: The file transfer request was cancelled. Diagnostics: There was an error sending the file transfer request to the host. | Check that the control unit is running or use local problem reporting procedures. |
| 279 | Transfer Status: The file transfer request was cancelled. Diagnostics: The CICS or VSE file name specified is missing, is invalid, or the host disk has read-only access. | Specify a valid data set name, or talk with the host system administrator to get write permissions on the specified disk. |
| 280 | Transfer Status: The file transfer request was cancelled by the host. Diagnostics: The wrong host operating system has been specified either on the command line or in the session profile. | Retry the file transfer specifying the correct operating system. |
| 281 | The file transfer completed with no errors. | The host file records are segmented. |
| 282 | Transfer Status: The file transfer request was cancelled by the host. Diagnostics: There is not enough disk space available on the host. | Delete some useless files on your host disk or ask the host system administrator for more disk space. |
| 283 | Transfer Status: The file transfer request was cancelled by the host. Diagnostics: The request code was not correct. | Retry the file transfer using correct request codes or use local problem reporting procedures. |
| 284 | Transfer Status: The file transfer request was cancelled by the host. Diagnostics: A specified flag is not correct, the specified host file does not exist on the host, or the host operating system is incorrect. | Retry the file transfer using correct flags for the specified host operating system, retry the file transfer using an existing host file, or specify the correct host operating system. |
| 285 | Transfer Status: The file transfer request was cancelled by the host. Diagnostics: There is an error reading from or writing to the host disk, the specified partitioned data set is full, or the specified partitioned data set member does not exist. | Make sure that the host disk you are transferring to or from exists, is valid, and can be written to or read from, increase the size of the specified partitioned data set, or specify an existing partition data set member. |
| 286 | Transfer Status: The file transfer request was cancelled by the host. Diagnostics: A host option specified is invalid for this particular host operating system. | Retry the file transfer specifying the correct host operating system or the correct flag value. |
| 287 | Transfer Status: The file transfer request was cancelled by the host. Diagnostics: Cannot write a file to the host. | Check to make sure that the host disk you are transferring to exists, is valid, and has write permissions. |
| 288 | Transfer Status: The file transfer request was cancelled by the host. Diagnostics: Cannot read a file from the host. | Check to make sure that the host disk you are transferring from exists, is valid, and the file you are attempting to download from the host exists. |
| 289 | Transfer Status: The file transfer request was cancelled by the host. Diagnostics: The TSO data set name specified is missing, already exists, or the host disk has read-only access. | Specify a data set name that is valid or talk with the host system administrator to get write permissions on the specified host disk. |
| 290 | Transfer Status: The file transfer request was cancelled by the host. Diagnostics: The -S flag was specified incorrectly. | Refer to the help menu by entering fxfer -h for the correct usage of the -S flag. |
| 291 | Transfer Status: The file transfer request was cancelled by the host. Diagnostics: Do not specify the flags specified with a Partitioned Data Set. | |
| 292 | Transfer Status: The file transfer request was cancelled by the host. Diagnostics: Specify only one of tracks, cylinders, or avblocks when specifying the -S flag. | |
| 293 | Transfer Status: The file transfer request was cancelled by the host. Diagnostics: The CMS file identifier is missing or not correct. | Specify all CMS file identifiers correctly. |
| 294 | Transfer Status: The file transfer request was cancelled by the host. Diagnostics: The CMS file specified as the source file does not exist on the host. | |
| 295 | Transfer Status: The file transfer request was cancelled by the host. Diagnostics: The CMS disk has read permissions only. | Talk with the host system administrator to get write permissions on the specified disk. |
| 296 | Transfer Status: The file transfer request was cancelled by the host. Diagnostics: Either the CMS disk is not accessible or the file already exists. | Try to upload the file using the -r flag to replace the existing file on the host or talk to the host system administrator. |
| 297 | Transfer Status: The file transfer request was cancelled by the host. Diagnostics: The CMS disk is full. | Delete some useless files on your host disk or ask the host system administrator for more disk space. |
| 298 | Transfer Status: The file transfer request was cancelled by the host. Diagnostics: Invalid options specified without the -a flag. | Specify the FXC_APPEND option (-a flag) to do the file transfer specified. |
| 299 | Transfer Status: The file transfer request was cancelled by the host. Diagnostics: Specify -r flag to replace the file. | The specified file already exists on the host, the user must specify the FXC_REPL option (-r flag) to replace it. |
| 300 | Transfer Status: The file transfer completed with no errors. | |
| 301 | Transfer Status: The file transfer request was cancelled by the host. Diagnostics: The host error message was not recognizable. | Check to make sure the host file transfer utility (IND$FILE or its equivalent) you are using is correct and up to date. Or use local problem reporting procedures. |
| 302 | Warning: The dfxfer file transfer daemon process attempts to send file transfer complete acknowledgement to the fxfer front end process failed. The msgsnd() system call error number is (fxs_errno). | The fxfer front-end process was either removed or the emulator session was terminated. |
| 303 | Transfer Status: The file transfer request was cancelled. Diagnostics: A message sent by the fxfer front-end process to the dfxfer file transfer background process failed. The msgrcv() system call error number is (fxs_errno). | Make sure that neither the fxfer nor the dfxfer processes were interrupted. Or use local problem reporting procedures. |
| 304 | Transfer Status: The file transfer request was cancelled. Diagnostics: Cannot read from the source file for uploading. The read() system call error number is (fxs_errno). | Check path name and permissions, try again later, or use local problem reporting procedures. |
| 305 | Transfer Status: The file transfer request was cancelled. Diagnostics: Cannot open the source file for uploading. The open() system call error number is (fxs_errno). | Check path name and permissions, or use local problem reporting procedures. |
| 306 | Transfer Status: The file transfer request was cancelled. Diagnostics: Cannot close the uploaded source file. The close() system call error number is (fxs_errno). | Check path name and permissions or use local problem reporting procedures. |
| 307 | Transfer Status: The file transfer request was cancelled. Diagnostics: The specified source file is empty. | Files with zero bytes cannot be transferred. |
| 309 | Transfer Status: The file transfer request was cancelled. Diagnostics: Cannot write to the destination file. The write() system call error number is (fxs_errno). | Check path name and permissions, try again later, or use local problem reporting procedures. |
| 310 | Transfer Status: The file transfer request was cancelled. Diagnostics: Cannot open the temporary replace file for downloading. The open() system call error number is (fxs_errno). | Check path name and permissions, do not use the -r flag, or use local problem reporting procedures. |
| 311 | Transfer Status: The file transfer request was cancelled. Diagnostics: Cannot open the destination file for download. The open() system call error number is (fxs_errno). | Check path name and permissions or use local problem reporting procedures. |
| 312 | Transfer Status: The file transfer request was cancelled. Diagnostics: Cannot close the destination file. The close() system call error number is (fxs_errno). | Check path name and permissions or use local problem reporting procedures. |
| 313 | Transfer Status: The file transfer request was cancelled. Diagnostics: Cannot delete the original destination file. The unlink() system call error number is (fxs_errno). | Check path name and permissions, try to download to a different file name without using the -r flag, or use local problem reporting procedures. |
| 314 | Transfer Status: The file transfer request was cancelled. Diagnostics: Cannot link the replace file to the destination file. The link() system call error number is (fxs_errno). | Check path name and permissions, try to download to to a different file name without using the -r flag, or use local problem reporting procedures. |
| 315 | Transfer Status: The file transfer completed with one warning. Warning: Cannot delete the temporary replace file name. The unlink() system call error number is (fxs_errno). | Check path name and permissions, try to download to a different file name without using the -r flag, or use local problem reporting procedures. |
| 316 | Diagnostics: Cannot open the diagnostics output file that contains the status information. The open() system call error number is (fxs_errno). | Check path name and permissions or use local problem reporting procedures. |
| 318 | Transfer Status: The file transfer request was cancelled. No RESTART file was created. Diagnostics: There was an error in the RESTART file input or output operation. A system call error occurred. The error number is (fxs_errno). | Check path name and permissions or use local problem reporting procedures. |
| 319 | Transfer Status: The file transfer request was cancelled. Diagnostics: Cannot log on to the host. The AUTOLOG program return code is (fxs_errno). | Use the tlog command to make sure that the AUTOLOG script used to log on to the host is correct. |
| 320 | Transfer Status: The file transfer completed with one warning. Warning: Could not get the destination file creation time. | Check permissions or use local problem reporting procedures. |
| 323 | Transfer Status: The file transfer request was cancelled. Diagnostics: Cannot receive a message through the fxfer message queue. The msgrcv() system call error number is (fxs_errno). | Ensure the HCON resource manager has not been removed; check that the fxfer and/ordfxfer processes have not been removed; check that the message queue in question has not been removed; or use local problem reporting procedures. |
| 325 | Transfer Status: The file transfer did not complete. Diagnostics: The connection with the host is lost and no recovery for an explicit file transfer is available. | Check that the coaxial cable is still connected or use local problem reporting procedures. |
| 326 | Transfer Status: The file transfer request was cancelled. Diagnostics: Cannot send a message through the fxfer message queue. The msgsnd() system call error number is (fxs_errno). | Check to make sure that the HCON resource manager has not been removed; check that the fxfer and/or dfxfer processes have not been removed; check that the ipcs message queue in question has not been removed; or use local problem reporting procedures. |
| 327 | Transfer Status: The file transfer did not complete. Diagnostics: The connection with the host is lost. Cannot recover in the specified recovery time. | Check that the coaxial cable is connected, check that the control unit is running, or use local problem reporting procedures. |
| 328 | Transfer Status: The file transfer did not complete. Diagnostics: An error specific to the VSE host environment has occurred. | If in explicit mode, refer to the VSE host file transfer handbook or contact a VSE host administrator. If running in implicit mode, attempt to recreate the problem following the instructions for explicit mode. |
| 330 | Transfer Status: The file transfer request was cancelled. Diagnostics: The session is busy at this time. | Try again later or use local problem reporting procedures. |
| 331 | Transfer Status: The file transfer request was cancelled. Diagnostics: An error was received while trying to receive a message from the emulator server. | Check that the emulator server session was not deleted, that the HCON resource manager (hcondmn) is still running, and that the ipcs message queue has not been deleted, or use local problem reporting procedures. |
| 333 | Transfer Status: The file transfer request was cancelled. Diagnostics: The file transfer received an interrupt signal. | A RESTART file should be created that will allow the user to restart the interrupted file transfer. |
| 334 | Transfer Status: An error occurred during the file transfer. Diagnostics: A system call failed. The system call error number is (fxs_errno). | Check path name and permissions and try the file transfer again. Or use local problem reporting procedures. |
| 335 | Transfer Status: The file transfer request was cancelled. Diagnostics: A bad message queue input was sent to the emulator server. | Try the file transfer again or use local problem reporting procedures. |
| 336 | Transfer Status: The file transfer request was canceled. Diagnostics: The file transfer was interrupted due to an attention key or system request key. A RESTART file should have been created that will allow the user to restart the interrupted file transfer. | Restart the file transfer. |
| 338 | Transfer Status: The file transfer request was cancelled. Diagnostics: Cannot get the status of the file transfer message queue. The msgctl() system call error number is (fxs_errno). | Make sure that the HCON resource manager has not been removed; check that the fxfer and dfxfer processes have not been removed; check that the ipcs message queue in question has not been removed; or use local problem reporting procedures. |
| 339 | Transfer Status: The file transfer request was cancelled. Diagnostics: The dfxfer file transfer background process queue was removed. The system call error number is (fxs_errno). | The user removed either the emulator server session or the HCON resource manager before the file transfer had completed or before the file transfer wait time had run out. |
| 340 | Transfer Status: The file transfer request was cancelled. Diagnostics: An interrupt was received while the file transfer fxfer process was receiving a message from the dfxfer file transfer background process. The interrupt is not of a known type. The system call error number is (fxs_errno). | The user removed either the emulator server session or the HCON resource manager before the file transfer had completed or before the file transfer wait time had run out. |
| 343 | Restart Status: The RESTART file was created. | |
| 344 | Restart Status: Cannot create the RESTART file. There was an input or output error. | Check path name and permissions or use local problem reporting procedures. |
| 345 | Transfer Status: The file transfer request was cancelled. Diagnostics: Cannot initialize the e789x emulator process. The fork() system call error number is n. | Check for the e789x process in /usr/bin; check permissions; try again later; or use local problem reporting procedures. |
| 347 | Transfer Status: The file transfer request was cancelled. Diagnostics: The file transfer timed out. | If this is the user's first time to run a file transfer, make sure that the PSERVIC value has been changed on the host and that VTAM has been recycled. Check to make sure that the host is set in extended mode; check that the control unit is not down; check that the host file transfer program variable within the session profile is valid; or use local problem reporting procedures. |
| 349 | The connection to the host is lost. Trying to recover the connection. | |
| 350 | The system queue is full. | All file transfer requests are cancelled. Increase the system queue value or use local problem reporting procedures. Too many asynchronous file transfer requests may have been queued up also. |
| 352 | A message sent to the dfxfer file transfer background process has been interrupted. The dfxfer file transfer background process may have been deleted, the HCON resource manager may have been removed, or the file transfer message queue may have been removed. | Try the file transfer again or use local problem reporting procedures. |
| 367 | The host operating system specified is not valid. This code only applies to the DBCS environment. | Specify TSO, CMS, or CICS. |
| 368 | Transfer Status: The file transfer request was cancelled by the host. Diagnostics: The host (APVUFILE) detected an error during the file transfer operation. This code only applies to the DBCS environment. | Refer to the help menu by entering fxfer -h for the correct usage of flags or talk with the host system administrator. |