HULFT functional restrictions for uploads to object storage

When uploading receive files to object storage, transfers from the sending-side host to the receiving-side host use the HULFT transfer method, and transfers from the receiving-side host to object storage use HTTPS protocol.

Therefore, settings related to HULFT file transfers are applied only to transfers from the sending-side host to the receiving-side host and are not applied to uploads to object storage as a general rule.

Some functions related to HULFT file transfers are restricted for uploads to object storage for this reason. This section explains those HULFT functional restrictions. For details on functional restrictions for HULFT Cloud Storage Option, refer to Functional restrictions for object storage.

Checkpoint Resend File

Checkpoint Resend File cannot be performed.

Even if you specify resending from checkpoint with the Resend File Issuance command or the Resend Request Issuance command, the send files are resent from the beginning.

Instant Transfer

Files cannot be uploaded to object storage by using Instant Transfer.

If you specify a path including "://" for the save destination of the receive files with the Instant Transfer Send File Issuance command, the transfer results in an error.

Multiple Receive

Multiple Receive cannot be performed.

For uploads to object storage, you must specify "New Creation" or "Replace" for Registration Mode and "Restore" for Error Handling in the Receive Management Information.

However, if you specify "Multiple Receive" for Receive Mode in the Receive Management Information, you must specify "Append" for Registration Mode and "Keep" for Error Handling.

Therefore, if you specify Multiple Receive when uploading to object storage, the receiving results in an error.

Generational Management

Generational Management cannot be applied.

For uploads to object storage, you must specify "Restore" for Error Handling in the Receive Management Information.

However, if you specify "Yes" for Generational Management in the Receive Management Information, you must specify "Delete" for Error Handling.

Therefore, if you specify to apply Generational Management when uploading to object storage, the receiving results in an error.

Mail Interface (HULFT10 for Windows only)

If Mail Interface is used on the receiving-side host, receive files cannot be attached to mail.

If you specify to attach receive files, the receive files cannot be opened and an error occurs.

CSV Format Receive

For uploads to object storage, an error occurs if you specify "CSV" for Interface DBID in the Send Management Information.

Permission (HULFT10 for Linux only)

Owner name, group name, and permission are disabled for receive files.

Any values specified for Owner Name, Group Name, and Permission in the Receive Management Information cannot be used.

Exclusive control of objects

Exclusive control is handled differently for objects on object storage than for files on the disk. The settings for the following fields in the System Environment Settings are not used for objects on object storage.

Table 8.1 Fields that are not used

Host Type

Field

Windows

Retry Count on Locked Receive File (rretrycnt)
Retry Interval on Locked Receive File (rretrytime)
Receive File Lock Standby (rcvfilelockwait)

Linux

Receive Open Mode (rcvfilewait)
Note

  • For objects specified as receive files, if any operation is performed on the object storage during transfer, the receive files may not be created correctly.

  • If multiple transfers are performed simultaneously for one receive file (object), the receive file may not be created correctly.

Connect Retry

When connection to object storage fails, the settings for retrying follow the SDK specifications provided by each cloud vendor. Therefore, the settings for the following fields in the System Environment Settings are not used:

Table 8.2 Fields that are not used

Host Type

Field

Windows

Connect Retry Count (retrycnt)
Connect Retry Interval (retrytime)

Linux

Connect Retry Count (retrycnt)
Connect Retry Interval (retrytime)

Post-receive job environment variables

The "$FILENM" environment variable for post-receive jobs is converted to a path for uploading to cloud storage, so that value cannot be used to handle receive files in the same way as files on the disk.

To operate uploaded objects with the post-receive job, you may need to revise the startup job in the Job Information.

Dynamic specification in receiving (HULFT Cloud Storage Option Ver.8.4.1 only)

If you use dynamic specification in receiving, the receive files may not be created correctly.

Do not specify "$SNDFILE" for a file name or "$SNDPATH" for a path.

"$MSG0" to "$MSG5" and "$MSGL0" to "$MSGL1" can be used for message transmission.

Input and output of files on object storage

The HULFT utilities cannot be used for input and output of files on object storage.

Examples of utilities that cannot be used:

  • Joining multiple files (utljoin) for files on object storage

  • Splitting joined files (utlbreak) for files on object storage

  • Editing file code (utllf) for files on object storage

  • Unicode conversion (utlchgunicode) for files on object storage

Cancelation timing

If you cancel during uploading, it may take some time for cancelation to complete.