Problem

Resolution

The asynchronous HSM recall is not available for receive operation and will not be available.

When, sending, the option has been made available because the network session is opened with the partner only after the file has been recalled.

When server / receiver, receiving on a migrated/archived or tape file is non sens because the PeSIT session is already opened when we get details of the file, then, the time to mount, restore or recover the file is unpredictable and will engage issues with the PeSIT session RTO set at the partner side. Keeping it synchronous makes sense as the recall messages and time to recall can be aligned after we will have a PeSIT error due to the timeout.

It is not reliable doing like this and receiving in unique file-name using IDTU is always the best choice. Dealing with the final name can be achieved by rename or from an EOT procedure that will not suffer from the recall time.