Problem

Was working fine before the upgrade to version 3.1.3

Wrong value in NFNAME after HSM migrated GDG recall

FNAME pass its value to NFNAME (NFNAME=FNAME)

GDG migrated via HSM

Transfer issued using the relative GDG name

After the HSM recall, the FNAME contains the absolute GDG name

After the HSM recall, the NFNAME still remains with the relative GDG name

Resolution

The reported issue is due to the asynchronous operation for HSM recalls that was not the default in previous versions.

Change the option in SGINSTAL module (job A12OPTS)

For HSM ( HSMASYNC=YES, HSM RECALL IS ASYNCHRONOUS ) needs to be changed to NO.

You will get back get back to the synchronous HSM recalls and NFNAME will be set after the absolute GDG name has been retreived.