Send

Table C.1 Problems That Are Related to Send Processing

Trouble

Measure

Unable to send due to socket error

  • Is the Host Information of HULFT correct?

  • Is the port number of the remote host correct?

  • Is the /etc/hosts file registration of the remote host correct?

  • Is there a response to a ping?

  • Is the remote host physically connected to the LAN (WAN)?

  • Has HULFT started on the remote host?

  • Has an interruption such as a no-communication time-out or a disconnection of a network relay device occurred?

Unable to send due to file or disk error

  • Is the name of the Send file that is registered in the Send Management Information correct?

  • Does the directory specified for Work File Generation Path (tmpdir) exist?

Unable to start the Send daemon

  • Does the directory specified for Work File Generation Path (tmpdir) exist?

  • Are the environment variables HULPATH and HULEXEP defined?

  • Does the user who is attempting to start HULFT have execution permission?

  • Does the user have the permissions to read and write the directory that is specified as HULPATH?

  • Does the user have the permissions to read and write 'hulenv.conf' in HULPATH?

  • Is the content of 'hulenv.conf' in HULPATH correct?

Unable to terminate the Send daemon

  • Are the environment variables HULPATH and HULEXEP defined?

  • Does the user who is attempting to terminate HULFT have execution permission?

  • Does the user have the permissions to read and write the directory that is specified as HULPATH?

  • Does the user have the permissions to read and write 'hulenv.conf' in HULPATH?

  • Is transfer of the file in progress?

Sending or receiving does not end, and the status shown in the Transfer Status List remains 'Transferring.'

  • Are the environment variables HULPATH and HULEXEP defined?

Modification of the Send Multiplex Level or the Use Custom Character Table Mode is not reflected

  • Has the Send daemon been restarted?

Job ends with unknown error code

  • Since HULFT returns a signal number when the job that is being executed receives a signal, check the content of the signal.

Unable to send file that uses network resources (networked file)

  • Does the user who started the Send daemon have permission to access the target file and the Path to Location for Cross-Product Sharing?

  • Confirm that the target file is not being used by HULFT on another host or by another application.

  • Check the following points concerning the path in which the file is located:

    • If the path is NFS-mounted

    • If the version of NFS is 3 (NFS v3) or higher

    • If the attribute caching is disabled

  • Check the following points concerning the server on which the file is located:

    • If the ping command succeeds

    • If the prerequisites for the use of networked files are satisfied

    • If you can view or edit the target file with applications other than HULFT