Hi,
I agree the CSV_APF_EXISTS check is working correctly. I think DFSMShsm
certainly can and should determine a data set is APF regardless of
weather it was defined in the recommended way using SMS or incorrectly
using a volume serial.
SCP honors a volser specified for an SMS managed data for APF till that
changes everyone else should too. I don't know if HSM uses CSVAPF for
each data set that it has selected to migrate. If so then it probably
is invoking it with VOLTYPE=SMS for an SMS managed library and so no
match.
This is a lot of guessing but if that is the case just using VOLTYPE=ANY
would get correct results. If HSM has some sort of RYO code to inspect
a list retrieved once from CSVAPF at the beginning of migration then
that code would need to change.
HSM should not care if you have defined a data set to APF using the
correct "style".
IMHO the CSV_APF_EXISTS is useful and is working correctly telling me
what I should do. HSM should honor the APF processing as it is warts
and all. Extending HSM to do this protection HSMPlex wide would be an
enhancement but I think the case discussed of migration of an SMS
managed library APF by volser is defect. The HSM team may not agree I
have not reported this.
CSVAPF
,VOLTYPE=SMS
,VOLTYPE=ANY,VOLUME=volume
Specifies the status of the library specified on the DSNAME
parameter,
which is one of the following:
SMS The library is managed by the storage management subsystem
(SMS).
ANY The library may or may not be SMS-managed. The library is
located
on volume volume, which specifies the address of a 6-character
volume serial number; for an ADD request, you can also specify
****** (six asterisks) to indicate the current sysres volume,
or
*MCAT* to indicate the volume on which the master catalog
resides. If volume is all zeros, the system assumes that the
library is SMS-managed.
Note: The return code on a Query is determined by whether the match
is exact or inexact.
A return code of 0 indicates an exact match which could be:
o You coded DSNAME=d and VOLTYPE=ANY and VOLUME=v and there
is an entry in the APF list that matches both the data
set
and the volser.
o You coded DSNAME=d and an indication of "SMS-managed"
(VOLTYPE=SMS) and there is an entry in the APF list that
matches the data set and indicates "SMS-managed".
A return code of 4 with a reason code = 0401 indicates an
inexact match which is:
o You coded DSNAME=d and VOLTYPE=ANY and VOLUME=v and there
is no exact match, but there is an entry in the APF list
that matches the data set and indicates "SMS-managed".
Best Regards,
Sam Knutson, GEICO
System z Performance and Availability Management
mailto:[EMAIL PROTECTED]
(office) 301.986.3574
"Think big, act bold, start simple, grow fast..."
-----Original Message-----
Knutson, Sam wrote:
>
> I think you could make a good case for DFSMShsm not functioning
> correctly. It should refuse to migrate both since using SMS is
> recommended by not required by APF.
>
The check's documentation states that, "In order for [HSM] to verify
APF-authorization properly, the APF list entry must indicate that the
data set is SMS-managed." And, that's exactly what you've demonstrated
here. HSM is unable to verify the APF property when an SMS-managed data
set is improperly defined as non-SMS-managed in the APF list. So, the
data set gets migrated in that case.
In summary, HSM will allow migration when the APF list entry is
erroneously defined:
|Data Set is APF Entry Indicates Erroneous Can Be
|SMS Managed SMS-Managed Definition Migrated?
|----------- ------------------- ---------- ---------
| YES YES NO NO
| NO NO NO Not if matching volume
| YES NO YES YES
| NO YES YES YES
So, the CSV_APF_EXISTS check is doing its job! Right?
--
Edward E Jaffe
Phoenix Software International, Inc
5200 W Century Blvd, Suite 800
Los Angeles, CA 90045
310-338-0400 x318
[EMAIL PROTECTED]
http://www.phoenixsoftware.com/
====================
This email/fax message is for the sole use of the intended
recipient(s) and may contain confidential and privileged information.
Any unauthorized review, use, disclosure or distribution of this
email/fax is prohibited. If you are not the intended recipient, please
destroy all paper and electronic copies of the original message.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
