Re: Allocated a Non SMS managed Multi volume HFS dataset
That JCL example works fine for a single ZFS file system, but if you
need to define many, and don't want to use multiple job steps, you can
do something like this using the CoZ Toolkit.
//COZBATCH EXEC COZBATCH
//STDENV DD *
cyl=1 1
volumes=ZOS3AZ
aggr001=SYSZFS.FILESYSA
aggr002=SYSZFS.FILESYSB
/*
//STDIN DD *
export _BPX_SHAREAS=YES
zfsadm define -aggr $aggr001 -cyl $cyl -volumes $volumes
zfsadm define -aggr $aggr002 -cyl $cyl -volumes $volumes
zfsadm format -aggr $aggr001 -compat
zfsadm format -aggr $aggr002 -compat
/*
On 06/08/13 03:59, baby eklavya wrote:
Sure . Thank you John !
On Fri, Jun 7, 2013 at 5:43 PM, John McKown john.archie.mck...@gmail.comwrote:
I agree. One argument that I have gotten in the past was but I can easily
allocate an HFS filesystem using simple JCL. To allocate a ZFS, I need to
run an IDCAMS, then the initialization program. What a bother!. Well,
assuming that your ZFS data sets are SMS managed, you can easily allocate
and format a ZFS data set using simple JCL too! I use:
// SET FS= DATA SET NAME
//MKZFS EXEC PGM=IOEAGFMT,REGION=0M,
// PARM=('-aggregate FS -compat')
//ZFS DD DSN=FS,
// DISP=(NEW,CATLG),
// UNIT=SYSDA,
// SPACE=(CYL,(200,100)),
// RECORG=LS
//SYSPRINT DD SYSOUT=*
//STDOUTDD SYSOUT=*
//STDERRDD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//CEEDUMP DD SYSOUT=*
//*
snip
--
Mark Jacobs
Time Customer Service
Tampa, FL
The quiet ones are the ones that change the universe...
The loud ones only take the credit.
Londo Mollari - Babylon 5
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Allocated a Non SMS managed Multi volume HFS dataset
Sure . Thank you John !
On Fri, Jun 7, 2013 at 5:43 PM, John McKown john.archie.mck...@gmail.comwrote:
I agree. One argument that I have gotten in the past was but I can easily
allocate an HFS filesystem using simple JCL. To allocate a ZFS, I need to
run an IDCAMS, then the initialization program. What a bother!. Well,
assuming that your ZFS data sets are SMS managed, you can easily allocate
and format a ZFS data set using simple JCL too! I use:
// SET FS= DATA SET NAME
//MKZFS EXEC PGM=IOEAGFMT,REGION=0M,
// PARM=('-aggregate FS -compat')
//ZFS DD DSN=FS,
// DISP=(NEW,CATLG),
// UNIT=SYSDA,
// SPACE=(CYL,(200,100)),
// RECORG=LS
//SYSPRINT DD SYSOUT=*
//STDOUTDD SYSOUT=*
//STDERRDD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//CEEDUMP DD SYSOUT=*
//*
The only changes are to the // SET FS= to set the DSN name. And perhaps to
change the SPACE= in the JCL. Easy, easy! as my Russian teacher would
say.
On Fri, Jun 7, 2013 at 2:19 AM, Miklos Szigetvari
miklos.szigetv...@isis-papyrus.com wrote:
I think it would be better , to use ZFS instead of HFS.
On 06.06.2013 23:57, baby eklavya wrote:
Greetings ,
Thanks everyone for your inputs .
I converted those volumes to SMS managed and added them to a new storage
group . Modified the STGROUP ACS routines by adding DSNTYPE = HFS .
coding
LLQ=HFS also worked fine in my case . The dataset was allocated as SMS
managed and i was able to mount it successfully .
Regards,
Baby
On Thu, Jun 6, 2013 at 6:54 PM, Elardus Engelbrecht
elardus.engelbre...@sita.co.za** wrote:
Lizette Koehler wrote:
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.
What would ACSENVIR be in the case of TSO / ISPF allocation?
Perhaps evaluating JOB or XMODE can help you to determine the
environment.
If LLQ = 'HFS'
Then STGROUP = HFSVOLS
Else
WRITE ' Not using HFS Pool '
EXIT
Consider adding DSNTYPE = 'HFS' in your IF statement in the ACS
routines.
Groete / Greetings
Elardus Engelbrecht
--**--**
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
--**--**
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
--
Kind regards, / Mit freundlichen Grüßen
Miklos Szigetvari
Research Development
ISIS Papyrus Europe AG
Alter Wienerweg 12, A-2344 Maria Enzersdorf, Austria
T: +43(2236) 27551 333, F: +43(2236)21081
E-mail: miklos.szigetvari@isis-**papyrus.com
miklos.szigetv...@isis-papyrus.com
Info: i...@isis-papyrus.com Hotline: +43-2236-27551-111
Visit our brand new extended Website at www.isis-papyrus.com
--**--**---
This e-mail is only intended for the recipient and not legally
binding. Unauthorised use, publication, reproduction or
disclosure of the content of this e-mail is not permitted.
This email has been checked for known viruses, but ISIS Papyrus accepts
no responsibility for malicious or inappropriate content.
--**--**---
--**--**--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
--
This is a test of the Emergency Broadcast System. If this had been an
actual emergency, do you really think we'd stick around to tell you?
Maranatha!
John McKown
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Allocated a Non SMS managed Multi volume HFS dataset
I think it would be better , to use ZFS instead of HFS. On 06.06.2013 23:57, baby eklavya wrote: Greetings , Thanks everyone for your inputs . I converted those volumes to SMS managed and added them to a new storage group . Modified the STGROUP ACS routines by adding DSNTYPE = HFS . coding LLQ=HFS also worked fine in my case . The dataset was allocated as SMS managed and i was able to mount it successfully . Regards, Baby On Thu, Jun 6, 2013 at 6:54 PM, Elardus Engelbrecht elardus.engelbre...@sita.co.za wrote: Lizette Koehler wrote: 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. What would ACSENVIR be in the case of TSO / ISPF allocation? Perhaps evaluating JOB or XMODE can help you to determine the environment. If LLQ = 'HFS' Then STGROUP = HFSVOLS Else WRITE ' Not using HFS Pool ' EXIT Consider adding DSNTYPE = 'HFS' in your IF statement in the ACS routines. Groete / Greetings Elardus Engelbrecht -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- Kind regards, / Mit freundlichen Grüßen Miklos Szigetvari Research Development ISIS Papyrus Europe AG Alter Wienerweg 12, A-2344 Maria Enzersdorf, Austria T: +43(2236) 27551 333, F: +43(2236)21081 E-mail: miklos.szigetv...@isis-papyrus.com Info: i...@isis-papyrus.com Hotline: +43-2236-27551-111 Visit our brand new extended Website at www.isis-papyrus.com --- This e-mail is only intended for the recipient and not legally binding. Unauthorised use, publication, reproduction or disclosure of the content of this e-mail is not permitted. This email has been checked for known viruses, but ISIS Papyrus accepts no responsibility for malicious or inappropriate content. --- -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Allocated a Non SMS managed Multi volume HFS dataset
I agree. One argument that I have gotten in the past was but I can easily
allocate an HFS filesystem using simple JCL. To allocate a ZFS, I need to
run an IDCAMS, then the initialization program. What a bother!. Well,
assuming that your ZFS data sets are SMS managed, you can easily allocate
and format a ZFS data set using simple JCL too! I use:
// SET FS= DATA SET NAME
//MKZFS EXEC PGM=IOEAGFMT,REGION=0M,
// PARM=('-aggregate FS -compat')
//ZFS DD DSN=FS,
// DISP=(NEW,CATLG),
// UNIT=SYSDA,
// SPACE=(CYL,(200,100)),
// RECORG=LS
//SYSPRINT DD SYSOUT=*
//STDOUTDD SYSOUT=*
//STDERRDD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//CEEDUMP DD SYSOUT=*
//*
The only changes are to the // SET FS= to set the DSN name. And perhaps to
change the SPACE= in the JCL. Easy, easy! as my Russian teacher would say.
On Fri, Jun 7, 2013 at 2:19 AM, Miklos Szigetvari
miklos.szigetv...@isis-papyrus.com wrote:
I think it would be better , to use ZFS instead of HFS.
On 06.06.2013 23:57, baby eklavya wrote:
Greetings ,
Thanks everyone for your inputs .
I converted those volumes to SMS managed and added them to a new storage
group . Modified the STGROUP ACS routines by adding DSNTYPE = HFS .
coding
LLQ=HFS also worked fine in my case . The dataset was allocated as SMS
managed and i was able to mount it successfully .
Regards,
Baby
On Thu, Jun 6, 2013 at 6:54 PM, Elardus Engelbrecht
elardus.engelbre...@sita.co.za** wrote:
Lizette Koehler wrote:
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.
What would ACSENVIR be in the case of TSO / ISPF allocation?
Perhaps evaluating JOB or XMODE can help you to determine the
environment.
If LLQ = 'HFS'
Then STGROUP = HFSVOLS
Else
WRITE ' Not using HFS Pool '
EXIT
Consider adding DSNTYPE = 'HFS' in your IF statement in the ACS
routines.
Groete / Greetings
Elardus Engelbrecht
--**--**
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
--**--**
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
--
Kind regards, / Mit freundlichen Grüßen
Miklos Szigetvari
Research Development
ISIS Papyrus Europe AG
Alter Wienerweg 12, A-2344 Maria Enzersdorf, Austria
T: +43(2236) 27551 333, F: +43(2236)21081
E-mail:
miklos.szigetvari@isis-**papyrus.commiklos.szigetv...@isis-papyrus.com
Info: i...@isis-papyrus.com Hotline: +43-2236-27551-111
Visit our brand new extended Website at www.isis-papyrus.com
--**--**---
This e-mail is only intended for the recipient and not legally
binding. Unauthorised use, publication, reproduction or
disclosure of the content of this e-mail is not permitted.
This email has been checked for known viruses, but ISIS Papyrus accepts
no responsibility for malicious or inappropriate content.
--**--**---
--**--**--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
--
This is a test of the Emergency Broadcast System. If this had been an
actual emergency, do you really think we'd stick around to tell you?
Maranatha!
John McKown
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Allocated a Non SMS managed Multi volume HFS dataset
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:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of baby eklavya Sent: Thursday, 6 June 2013 7:46 PM To: IBM-MAIN@LISTSERV.UA.EDU 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 anthony.thomp...@nt.gov.au 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:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of baby eklavya Sent: Thursday, 6 June 2013 6:58 PM To: IBM-MAIN@LISTSERV.UA.EDU 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Allocated a Non SMS managed Multi volume HFS dataset
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:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of baby eklavya Sent: Thursday, June 06, 2013 2:28 AM To: IBM-MAIN@LISTSERV.UA.EDU 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Allocated a Non SMS managed Multi volume HFS dataset
Lizette Koehler wrote: 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. What would ACSENVIR be in the case of TSO / ISPF allocation? Perhaps evaluating JOB or XMODE can help you to determine the environment. If LLQ = 'HFS' Then STGROUP = HFSVOLS Else WRITE ' Not using HFS Pool ' EXIT Consider adding DSNTYPE = 'HFS' in your IF statement in the ACS routines. Groete / Greetings Elardus Engelbrecht -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Allocated a Non SMS managed Multi volume HFS dataset
Greetings , Thanks everyone for your inputs . I converted those volumes to SMS managed and added them to a new storage group . Modified the STGROUP ACS routines by adding DSNTYPE = HFS . coding LLQ=HFS also worked fine in my case . The dataset was allocated as SMS managed and i was able to mount it successfully . Regards, Baby On Thu, Jun 6, 2013 at 6:54 PM, Elardus Engelbrecht elardus.engelbre...@sita.co.za wrote: Lizette Koehler wrote: 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. What would ACSENVIR be in the case of TSO / ISPF allocation? Perhaps evaluating JOB or XMODE can help you to determine the environment. If LLQ = 'HFS' Then STGROUP = HFSVOLS Else WRITE ' Not using HFS Pool ' EXIT Consider adding DSNTYPE = 'HFS' in your IF statement in the ACS routines. Groete / Greetings Elardus Engelbrecht -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
