Every zfs doc I've ever seen has CISIZE of 4096.
1. First, use IDCAMS to create a VSAM linear data set.
Note: Carefully consider defining the aggregate as extended format,
extended addressability, and with a secondary allocation size. If you do not
use
these attributes in the beginning, to add them, you will need to define and
format a new zFS aggregate, migrate the data from the original file system
into the new one, unmount the original, and then mount the new one. You
might want to extend beyond the 4 G aggregate size because version 1.5
aggregates can be much larger than version 1.4 aggregates, or because
secondary
extents are required to dynamically grow the aggregate, and dynamic grow
(aggrgrow) is the default. See _Dynamically growing a compatibility mode
aggregate_
(https://www.ibm.com/support/knowledgecenter/SSLTBW_2.2.0/com.ibm.zos.v2r2.ioea700/ioea7d0041006636.htm?view=kc#ioea7d0041006636)
for more
information.
2. Then format the VSAM linear data set as a compatibility mode
aggregate and create a file system in the aggregate using ioeagfmt (see
_ioeagfmt_
(https://www.ibm.com/support/knowledgecenter/SSLTBW_2.2.0/com.ibm.zos.v2r2.ioea700/ioea7zcmd1031559.htm?view=kc#ioea7zcmd1031559)
). When using
ioeagfmt, the user must meet one of the following authorization requirements:
* Have ALTER authority to the VSAM linear data set.
* Be UID 0.
* Have read authority to the SUPERUSER.FILESYS.PFSCTL resource in
the RACF UNIXPRIV class.
Beginning in z/OS V2R1, ioeagfmt fails if the zFS PFS is not active on
the system. In addition, if the zFS started task does not have the TRUSTED
attribute or the OPERATIONS attribute, the DFS user ID must have at least
ALTER authority to all VSAM linear data sets that contain zFS aggregates. For
details, see _z/OS Security Server RACF Security Administrator's Guide_
(https://www.ibm.com/support/knowledgecenter/SSLTBW_2.2.0/com.ibm.zos.v2r2.icha7
00/toc.htm?view=kc) .
You can also create a compatibility mode aggregate using the ISHELL, or
the automount facility, or the zfsadm define and zfsadm format commands.
For more information about ISHELL, see _z/OS V2R2.0 UNIX System Services
User's Guide_
(https://www.ibm.com/support/knowledgecenter/SSLTBW_2.2.0/com.ibm.zos.v2r2.bpxa400/toc.htm?view=kc)
. For more information about automount,
see _z/OS UNIX System Services Planning_
(https://www.ibm.com/support/knowledgecenter/SSLTBW_2.2.0/com.ibm.zos.v2r2.bpxb200/toc.htm?view=kc)
. For more
information about the zfsadm define command, see _zfsadm define_
(https://www.ibm.com/support/knowledgecenter/SSLTBW_2.2.0/com.ibm.zos.v2r2.ioea700/ioe
a70021.htm?view=kc#ioea700-gen20) . For more information about the zfsadm
format command, see _zfsadm format_
(https://www.ibm.com/support/knowledgecenter/SSLTBW_2.2.0/com.ibm.zos.v2r2.ioea700/ioea70022.htm?view=kc#ioea700-gen
21) .
The VSAM linear data set, the aggregate, and the file system all have the
same name and that name is equal to the VSAM linear data set cluster name.
The zFS file system is then mounted into the z/OS® UNIX hierarchy.
Rule: The Control Interval (CI) size of a VSAM linear data set that is
formatted as a zFS aggregate must be 4 K. This is the default for IDCAMS. As
such, it is not specified in _Figure 1_
(https://www.ibm.com/support/knowledgecenter/SSLTBW_2.2.0/com.ibm.zos.v2r2.ioea700/ioea7d0041003067.htm?view=kc#i
oea7d0041003067__ioea7d0041003169) , which shows an example of a job that
creates a compatibility mode file system.
Figure 1. Example job to create a compatibility mode file system
//USERIDA JOB ,'Compatibility Mode',
// CLASS=A,MSGCLASS=X,MSGLEVEL=(1,1)
//DEFINE EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=H
//SYSUDUMP DD SYSOUT=H
//AMSDUMP DD SYSOUT=H
//DASD0 DD DISP=OLD,UNIT=3390,VOL=SER=PRV000
//SYSIN DD *
DEFINE CLUSTER (NAME(OMVS.PRV.COMPAT.AGGR001) -
VOLUMES(PRV000) -
LINEAR CYL(25 0) SHAREOPTIONS(3))
/*
//CREATE EXEC PGM=IOEAGFMT,REGION=0M,
// PARM=('-aggregate OMVS.PRV.COMPAT.AGGR001 -compat')
//SYSPRINT DD SYSOUT=H
//STDOUT DD SYSOUT=H
//STDERR DD SYSOUT=H
//SYSUDUMP DD SYSOUT=H
//CEEDUMP DD SYSOUT=H
In a message dated 7/5/2017 4:38:39 A.M. Central Daylight Time,
nitz-...@gmx.net writes:
Now exit, stage left, muttering: Why didn't IBM just specify in plain
English that one cannot determine CISIZE instead of using an obscure,
undocumented reason code and an unhelpful amount of dumps and messages?!?!?
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
