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
-----Original Message-----
>From: Mark Zelden <[EMAIL PROTECTED]>
>Sent: Sep 22, 2008 3:50 PM
>To: [email protected]
>Subject: Re: Space errors in JAVA during SMP/E Apply
>
>On Mon, 22 Sep 2008 15:43:46 -0400, Lizette Koehler
><[EMAIL PROTECTED]> wrote:
>
>>List -
>>
>>I know this is a simple answer, but my brain does not process JAVA very
>well yet. So be gentle.
>>
>>I am doing an APPLY of 400+ ptfs to my system (z/OS V1.9)
>>
>>During the APPLY I got the following failure
>>J1.4/bin/classic/libjvm.so
>>pax: FSUM6260 write error on file "J1.4/bin/classic/libjvm.so": EDC5133I No
>space left on device.
>>J1.4/bin/classic/libcore.so
>>pax: FSUM6260 write error on file "J1.4/bin/classic/libcore.so": EDC5133I
>No space left on device.
>>
>>
>>My zos19.omvs.jv390 data set is a zFS file.
>>
>>Its attributes are:
>>
>> DATASET-OWNER-----(NULL) CREATION--------2008.263
>> RELEASE----------------2 EXPIRATION------0000.000
>> ACCOUNT-INFO-----------------------------------(NULL)
>>PROTECTION-PSWD-----(NULL) RACF----------------(NO)
>>ASSOCIATIONS
>> CLUSTER--ZOS19.OMVS.JV390
>>ATTRIBUTES
>> KEYLEN-----------------0 AVGLRECL---------------0
>BUFSPACE------------8192 CISIZE--------------4096
>> RKP--------------------0 MAXLRECL---------------0
>EXCPEXIT----------(NULL) CI/CA----------------180
>> SHROPTNS(3,3) RECOVERY UNIQUE NOERASE LINEAR
>NOWRITECHK NOIMBED NOREPLICAT
>> UNORDERED NOREUSE NONSPANNED ZFS
>>STATISTICS
>> REC-TOTAL--------------0 SPLITS-CI--------------0
>EXCPS------------------0
>> REC-DELETED------------0 SPLITS-CA--------------0
>EXTENTS----------------1
>> REC-INSERTED-----------0 FREESPACE-%CI----------0 SYSTEM-TIMESTAMP:
>> REC-UPDATED------------0 FREESPACE-%CA----------0
>X'0000000000000000'
>> REC-RETRIEVED----------0 FREESPC----------------0
>>ALLOCATION
>> SPACE-TYPE------CYLINDER HI-A-RBA-------246988800
>> SPACE-PRI------------335 HI-U-RBA-------246988800
>> SPACE-SEC-------------28
>>VOLUME
>> VOLSER------------Z19HF2 PHYREC-SIZE---------4096
>HI-A-RBA-------246988800 EXTENT-NUMBER----------1
>> DEVTYPE------X'3010200F' PHYRECS/TRK-----------12
>HI-U-RBA-------246988800 EXTENT-TYPE--------X'40'
>> VOLFLAG------------PRIME TRACKS/CA-------------15
>> EXTENTS:
>>LOW-CCHH-----X'12500000' LOW-RBA----------------0
>TRACKS--------------5025
>>HIGH-CCHH----X'139E000E' HIGH-RBA-------246988799
>>
>>my volume z19hf2 has 1200 cylinders on it.
>>
>>I can see the HI-A-RB and HI-U-RBA are the same - so it is out of space.
>>
>
>It is out of space, but not because of that. High used always equals high
>allocated since it is a formatted data set.
>
>
>>How can I make it bigger?????? If I unmount the zos19.omvs.jv390 data set
>and then create a new zFS file. Can I just use IDCAMS repro or how to I get
>the info into the new one?
>>
>
>I don't see any secondary extents. You either:
>
>1) don't have aggrgrow=on in your zfs parms
>2) didn't mount it with parm 'aggrgrow=on'
>3) don't have enough space left on the Z19HF2 volume
>
----------------------------------------------------------------------
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
