I should have mentioned that my zfsadm module is broken. The /usr/bin/zfsadm
is corrupted. The one in my service directory is fine, but the one in my
production omvs root data set is un unusable.
That is why I was looking for a way to copy the current JV390 file into a new
JV390.NEW file.
Since I seem to have everything in place, I am not sure why I cannot grow this
aggr unless it is due to the zfsadm being broken.
Lizette
>>To answer Mark's questions I have
>>
>>AGGRFULL(85,5)
>>AGGRGROW=ON
>>
>>The define had
>>ALLOC -
>> DSNAME('ZOS19.OMVS.JV390') -
>> RECORG(LS) -
>> TRACKS SPACE(5011,417) -
>> BLKSIZE(4096) -
>> VOLUME(Z19HF2) -
>> UNIT(3390) -
>> CATALOG
>>
>>
>>Lizette
>
>Is there space on the Z19HF2 volume? If so, then I think that you can simply
>use the zfsadm command.
>
>zfsadm grow -aggregate ZOS19.OMVS.JV390 -size 1024
>
>would extend the zFS file by 1024K (1 Meg). If not, then unmount the
>filesystem. Do an IDCAMS ALTER command to add a second volume. Then try the
>zfsadm command. I don't know if you need to MOUNT the filesystem before the
>zfsadm command in this case, or afterwards. I'd try before and if that
>didn't work, then MOUNT it and try the zfsadm command again.
>
>--
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
