I imagine allocation routines haven't been changed to cope for this special 
case (HFS' are just PS datasets that are used by a different access method). 
Possibly you can add your volumes to a SMS storage group, activate your SCDS 
and convert the volumes? If you have the authority...

Ant. 

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf 
Of baby eklavya
Sent: Thursday, 6 June 2013 7:46 PM
To: [email protected]
Subject: Re: Allocated a Non SMS managed Multi volume HFS dataset

Thank you ...But i was expecting that ISPF 3.2 allocation attempt would
fail . But it did not .

Looks like the HFS code is setup to fail the mount of non-sms multivolume
dataset whereas system still allows the allocation of the dataset .Is there
a specific reason for this ?

Regards,
Baby


On Thu, Jun 6, 2013 at 3:22 PM, Anthony Thompson <[email protected]
> wrote:

> See OA37880 http://www-01.ibm.com/support/docview.wss?uid=isg1OA37880
>
> I think you'll have issues.
>
> Ant.
>
> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:[email protected]] On
> Behalf Of baby eklavya
> Sent: Thursday, 6 June 2013 6:58 PM
> 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
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to [email protected] with the message: INFO IBM-MAIN
>

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to