Space errors in JAVA during SMP/E Apply
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) CREATION2008.263 RELEASE2 EXPIRATION--.000 ACCOUNT-INFO---(NULL) PROTECTION-PSWD-(NULL) RACF(NO) ASSOCIATIONS CLUSTER--ZOS19.OMVS.JV390 ATTRIBUTES KEYLEN-0 AVGLRECL---0 BUFSPACE8192 CISIZE--4096 RKP0 MAXLRECL---0 EXCPEXIT--(NULL) CI/CA180 SHROPTNS(3,3) RECOVERY UNIQUE NOERASE LINEAR NOWRITECHK NOIMBED NOREPLICAT UNORDEREDNOREUSE NONSPANNED ZFS STATISTICS REC-TOTAL--0 SPLITS-CI--0 EXCPS--0 REC-DELETED0 SPLITS-CA--0 EXTENTS1 REC-INSERTED---0 FREESPACE-%CI--0 SYSTEM-TIMESTAMP: REC-UPDATED0 FREESPACE-%CA--0 X'' REC-RETRIEVED--0 FREESPC0 ALLOCATION SPACE-TYPE--CYLINDER HI-A-RBA---246988800 SPACE-PRI335 HI-U-RBA---246988800 SPACE-SEC-28 VOLUME VOLSERZ19HF2 PHYREC-SIZE-4096 HI-A-RBA---246988800 EXTENT-NUMBER--1 DEVTYPE--X'3010200F' PHYRECS/TRK---12 HI-U-RBA---246988800 EXTENT-TYPEX'40' VOLFLAGPRIME TRACKS/CA-15 EXTENTS: LOW-CCHH-X'1250' LOW-RBA0 TRACKS--5025 HIGH-CCHHX'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. 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? Lizette -- 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
Re: Space errors in JAVA during SMP/E Apply
My understanding (from Share), though I have not done this myself (caveat emptor!) is that you would unmount the zfs and then use your VSAM LDS handler of choice - IDCAMS, DSS, FDR, CA-DISK to increase the size of the LDS and load the records back in. Then mount it and use it. Linda Mooney -- Original message -- From: Lizette Koehler [EMAIL PROTECTED] 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) CREATION2008.263 RELEASE2 EXPIRATION--.000 ACCOUNT-INFO---(NULL) PROTECTION-PSWD-(NULL) RACF(NO) ASSOCIATIONS CLUSTER--ZOS19.OMVS.JV390 ATTRIBUTES KEYLEN-0 AVGLRECL---0 BUFSPACE8192 CISIZE--4096 RKP0 MAXLRECL---0 EXCPEXIT--(NULL) CI/CA180 SHROPTNS(3,3) RECOVERY UNIQUE NOERASE LINEAR NOWRITECHK NOIMBED NOREPLICAT UNORDERED NOREUSE NONSPANNED ZFS STATISTICS REC-TOTAL--0 SPLITS-CI--0 EXCPS--0 REC-DELETED0 SPLITS-CA--0 EXTENTS1 REC-INSERTED---0 FREESPACE-%CI--0 SYSTEM-TIMESTAMP: REC-UPDATED0 FREESPACE-%CA--0 X'' REC-RETRIEVED--0 FREESPC0 ALLOCATION SPACE-TYPE--CYLINDER HI-A-RBA---246988800 SPACE-PRI335 HI-U-RBA---246988800 SPACE-SEC-28 VOLUME VOLSERZ19HF2 PHYREC-SIZE-4096 HI-A-RBA---246988800 EXTENT-NUMBER--1 DEVTYPE--X'3010200F' PHYRECS/TRK---12 HI-U-RBA---246988800 EXTENT-TYPEX'40' VOLFLAGPRIME TRACKS/CA-15 EXTENTS: LOW-CCHH-X'1250' LOW-RBA0 TRACKS--5025 HIGH-CCHHX'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. 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? Lizette -- 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 -- 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
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) CREATION2008.263 RELEASE2 EXPIRATION--.000 ACCOUNT-INFO---(NULL) PROTECTION-PSWD-(NULL) RACF(NO) ASSOCIATIONS CLUSTER--ZOS19.OMVS.JV390 ATTRIBUTES KEYLEN-0 AVGLRECL---0 BUFSPACE8192 CISIZE--4096 RKP0 MAXLRECL---0 EXCPEXIT--(NULL) CI/CA180 SHROPTNS(3,3) RECOVERY UNIQUE NOERASE LINEAR NOWRITECHK NOIMBED NOREPLICAT UNORDEREDNOREUSE NONSPANNED ZFS STATISTICS REC-TOTAL--0 SPLITS-CI--0 EXCPS--0 REC-DELETED0 SPLITS-CA--0 EXTENTS1 REC-INSERTED---0 FREESPACE-%CI--0 SYSTEM-TIMESTAMP: REC-UPDATED0 FREESPACE-%CA--0 X'' REC-RETRIEVED--0 FREESPC0 ALLOCATION SPACE-TYPE--CYLINDER HI-A-RBA---246988800 SPACE-PRI335 HI-U-RBA---246988800 SPACE-SEC-28 VOLUME VOLSERZ19HF2 PHYREC-SIZE-4096 HI-A-RBA---246988800 EXTENT-NUMBER--1 DEVTYPE--X'3010200F' PHYRECS/TRK---12 HI-U-RBA---246988800 EXTENT-TYPEX'40' VOLFLAGPRIME TRACKS/CA-15 EXTENTS: LOW-CCHH-X'1250' LOW-RBA0 TRACKS--5025 HIGH-CCHHX'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 Regards, Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group - ZFUS G-ITO mailto:[EMAIL PROTECTED] z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html -- 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
Re: Space errors in JAVA during SMP/E Apply
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: IBM-MAIN@BAMA.UA.EDU
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) CREATION2008.263
RELEASE2 EXPIRATION--.000
ACCOUNT-INFO---(NULL)
PROTECTION-PSWD-(NULL) RACF(NO)
ASSOCIATIONS
CLUSTER--ZOS19.OMVS.JV390
ATTRIBUTES
KEYLEN-0 AVGLRECL---0
BUFSPACE8192 CISIZE--4096
RKP0 MAXLRECL---0
EXCPEXIT--(NULL) CI/CA180
SHROPTNS(3,3) RECOVERY UNIQUE NOERASE LINEAR
NOWRITECHK NOIMBED NOREPLICAT
UNORDEREDNOREUSE NONSPANNED ZFS
STATISTICS
REC-TOTAL--0 SPLITS-CI--0
EXCPS--0
REC-DELETED0 SPLITS-CA--0
EXTENTS1
REC-INSERTED---0 FREESPACE-%CI--0 SYSTEM-TIMESTAMP:
REC-UPDATED0 FREESPACE-%CA--0
X''
REC-RETRIEVED--0 FREESPC0
ALLOCATION
SPACE-TYPE--CYLINDER HI-A-RBA---246988800
SPACE-PRI335 HI-U-RBA---246988800
SPACE-SEC-28
VOLUME
VOLSERZ19HF2 PHYREC-SIZE-4096
HI-A-RBA---246988800 EXTENT-NUMBER--1
DEVTYPE--X'3010200F' PHYRECS/TRK---12
HI-U-RBA---246988800 EXTENT-TYPEX'40'
VOLFLAGPRIME TRACKS/CA-15
EXTENTS:
LOW-CCHH-X'1250' LOW-RBA0
TRACKS--5025
HIGH-CCHHX'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
Re: Space errors in JAVA during SMP/E Apply
On Mon, 22 Sep 2008 16:27:01 -0400, Lizette Koehler
[EMAIL PROTECTED] wrote:
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.
--
John McKown
--
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
Re: Space errors in JAVA during SMP/E Apply
I think Mark had your answer. Please double-check:
BROWSESYS1.PROCLIB(ZFS)
Command ===
* Top of Data
//ZFS PROC REGSIZE=0M
//*
//ZFZGOEXEC PGM=BPXVCLNY,REGION=REGSIZE,TIME=1440
//*
Bottom of Data **
Make sure your ZFS started task does NOT have an IOEZPRM DD statement.
If there is no IOEZPRM DD statement, then ZFS gets its parms from the
system parmlib concatenation - and the exact member and data set name it
was fetched from are echoed in SYSLOG at IPL / ZFS startup.
BROWSESYS1.PARMLIB(IOEPRM00) - 01.01
Command ===
* Top of Data ***
aggrgrow=on
Bottom of Data **
Again, please confirm by looking at your IPL time SYSLOG exactly which
IOEPRM00 member, from exactly which system parmlib concatenation data set,
was used for ZFS startup.
Brian
On Mon, 22 Sep 2008 16:27:01 -0400, Lizette Koehler wrote:
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
--
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
Re: Space errors in JAVA during SMP/E Apply
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
Re: Space errors in JAVA during SMP/E Apply
On Mon, 22 Sep 2008 16:27:01 -0400, Lizette Koehler
[EMAIL PROTECTED] wrote:
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
Looks correct on the surface. Are you sure that parm is in use.
Use this unix command:
zfsadm configquery -aggrgrow
What does the o/p of this unix command show:
zfsadm aggrinfo -aggregate ZOS19.OMVS.JV390 -long
You should also be able to force it to grow with
zfsadm grow
All the zfsadm commands are documented in:
Distributed File Service zSeries File System Administration
Mark
--
Mark Zelden
Sr. Software and Systems Architect - z/OS Team Lead
Zurich North America / Farmers Insurance Group - ZFUS G-ITO
mailto:[EMAIL PROTECTED]
z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/
Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html
--
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
Re: Space errors in JAVA during SMP/E Apply
On Mon, 22 Sep 2008 16:48:38 -0400, Lizette Koehler [EMAIL PROTECTED] wrote: 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 1. Fix zfsadm as soon as you can. 2) define your new JV390 file with the new size. 3) create a new mountpoint for it, say /usr/lpp/jdk.new 4) mount it, say as /usr/lpp/jdk.new 5) su - (go to root) 6) cd /usr/lpp/jdk #current JDK mount point. 7) pax -rw -pe * /usr/lpp/jdk.new #copy to new 8) unmount /usr/lpp/jdk 9) unmount /usr/lpp/jdk.new 10) ALTER old.jdk.LDS.name some.new.name.just.to.be.safe 11) ALTER new.jdk.LDS.name old.jdk.LDS.name 12) mount /usr/lpp/jdk #mount copy of filesystem at old mount point === The above is off the top of my head, but should be close. I think. Maybe. YMMV. -- John McKown -- 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
Re: Space errors in JAVA during SMP/E Apply
John, Thanks so much. This is probably what I need to do. I will add this to my notes file on UNIX commands. Lizette -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of John McKown Sent: Monday, September 22, 2008 4:56 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: Space errors in JAVA during SMP/E Apply On Mon, 22 Sep 2008 16:48:38 -0400, Lizette Koehler [EMAIL PROTECTED] wrote: 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 1. Fix zfsadm as soon as you can. 2) define your new JV390 file with the new size. 3) create a new mountpoint for it, say /usr/lpp/jdk.new 4) mount it, say as /usr/lpp/jdk.new 5) su - (go to root) 6) cd /usr/lpp/jdk #current JDK mount point. 7) pax -rw -pe * /usr/lpp/jdk.new #copy to new 8) unmount /usr/lpp/jdk 9) unmount /usr/lpp/jdk.new 10) ALTER old.jdk.LDS.name some.new.name.just.to.be.safe 11) ALTER new.jdk.LDS.name old.jdk.LDS.name 12) mount /usr/lpp/jdk #mount copy of filesystem at old mount point === The above is off the top of my head, but should be close. I think. Maybe. YMMV. -- 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
