Usage notes for the HSMRQUE function

This method was established during product customization. See the JCLHSMRQ member in BBSAMP for examples.

Recall requests

When HSMRQ_SCOPE=GLOBAL is specified in SMMSYSxx, recall requests that originate on other systems are run through the filter and rule list statements on the local system.

HSM_CANCEL=Y can be used only on recall requests that originated on the local system. If HSM_CANCEL=Y is specified on a recall that originated on a another system, it is ignored and the request is not canceled.

HSMRQUE checks the recall queue once every minute. Most requests are completed before the function checks the queue file. To check the recall queue as soon as the request is issued, use the HSMPRTY function. The TIME= filter will most likely never happen for the HSMRQUE function.

Recall queue file sharing

The recall request queue file is maintained as a KSDS VSAM data set with SHAREOPTIONS(4 3) and is always allocated with DISP=SHR.

The cluster name of this VSAM data set is defined in the SMMSYSxx SET keyword HSMRQ_VSAM. The same recall queue file can be shared across DFSMShsms and systems if the VSAM data set (queue file) is on shared DASD. If you change the data set name with the REFRESH command, the change is propagated to all DFSMShsms on the same image, causing reallocation. However, to share the recall queue across systems, you must repeat this action on all participating systems.

Multicluster MCDS and MCDS serialization

MainView SRM supports multicluster MCDS and supports the MCDS serialization method that is dictated by DFSMShsm startup, including the following:

• ENQ/DEQ (startup parameter CDSQ=YES)

• RESERVE (startup parameter CDSQ=NO or CDSR=YES)

• RLS VSAM data set recall queue file

HSMRQUE actions frequency

You can use the RQ_INTRVL rule list SET parameter to control the frequency of the same HSMRQUE action generation. (The REC_TYPE filter list parameter specifies selection criteria for defining and grouping the action.)