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.com>wrote:
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=*
//STDOUT DD SYSOUT=*
//STDERR DD 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
