SDSP is defined in the HSM parms for small data sets, and the SDSP file is actually a VSAM data set allocated to one of the ML1 volumes. If the SDSP file does not occupy the entire logical ML1 volume, the volume is eligible for other ML1 migration activity. The idea behind SDSP is to prevent fragmentation on the ML1 volumes and prevent RC37 errors during Primary Space Management. You might want to consider removing SDSP from DFHSM, and let the small data sets live and die on primary disk, saving on costly CPU cycles used by DFHSM to migrate and manage small data sets.
Mike Spencer BMC Software -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of willie bunter Sent: Friday, May 27, 2011 1:25 PM To: [email protected] Subject: DFHSM QUESTION - SDSP DSNS Hallo To All, I ran a report to obtain a list of SDSP dsns on an ML1 volume which is defined as SDSP : HSEND LIST DATASETNAME MCDS SELECT(VOLUME(ML1101) SDSP). There were 42,403 dsns listed. I ran another report HSEND LIST DATASETNAME MCDS SELECT(VOLUME(ML1101)). In this report there were 42,499 dsns. My question is why is there a discrepancy? Since the volume is defined as SDSP shouldn't only dsns that fit the criteria be housed on the SDSP volume? Since there are 2 volumes defined as NOSDP shouldn't they be allocated on those volumes. I would appreciate it if someone could clear up my misunderstanding about SDSP and NOSDP. Thanks. ---------------------------------------------------------------------- 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 ---------------------------------------------------------------------- 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
