Differences in file transfer and request acceptance operations

HULFT 8.0.0

In HULFT8, the communication method was expanded to support long messages and the extension of the byte count for the Management Information ID. For this reason you may experience the following effects when connecting to a lower version of HULFT.

• When you connect to HULFT Ver.7 or HULFT Ver.6, because the number of exchanges increase when switching to a communication mode that is backward compatible, it may take longer than connecting from HULFT Ver.6.

• When you connect to a version of HULFT for Mainframe lower than Ver.8, additional multiplicity might be consumed on the connecting side.

• Sending files and issuing requests cannot be performed with the following products:

  • HULFT for Mainframe Type VOS Ver.5

  • HULFT for Mainframe Type ACOS Ver.5

  • HULFT for Himalaya Ver.5

  • HULFT for K

  • HULFT-SAN Ver.5

If you specify "Yes" for Use HULFT7 Comm. Mode in Host Information, you can avoid the above effects, because from the start HULFT connects to the host by using a communication method that is backward compatible.

Also, for details on the products whose communication with HULFT8 is assured, see List of products whose communication is assured.