I think that your ACS code would need to verify for ISPF 3.2 that the allocation was valid. ISPF 3.2 really does not check ( at least I do not think it checks) if the volumes being used are correct.
I do know that in the ACS code I have, there are sections that will not allow allocations when it does not meet the requirements I setup in ACS. So, does your ACS code restrict HFS files from going on certain volumes? My code looks like (Pseudo). This is not perfect, but more in what code could do You would need to review the ACS constructs to see what would work for your shop. You might use a DSN Mask or VOLSER mask. If LLQ = 'HFS' Then STGROUP = HFSVOLS Else WRITE ' Not using HFS Pool ' EXIT Lizette -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of baby eklavya Sent: Thursday, June 06, 2013 2:28 AM To: [email protected] Subject: Allocated a Non SMS managed Multi volume HFS dataset Hello , DSS manuals says that a multi volume HFS dataset must be SMS managed . But i was able to allocate a multi volume HFS using a set of 15 NON SMS managed volumes via ISPF 3.2 option . When i do a listcat against the dataset,it shows all the 15 volumes . I am wondering how it allowed me to create a NON SMS managed HFS dataset which is spanned across multiple volumes .Here , i used 15 MOD-3 volumes and the dataset is allocated with pri=3000 , sec=3000 cylinders . Does it really allow non-sms managed HFS datasets or am i going to face issues when the dataset extends to secondary extent ? Regards, Baby ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
