My initial DLIB allocations for AARSOBJ1, AARSHAS1, AARSHMS1 were too small.
I made them the same as what I had allocated for 8.x and I was good to go.
//STEP1 EXEC PGM=BPXBATCH,REGION=0M
//*
//STEPLIB DD DISP=SHR,DSN=ARS.ARSV900.SARSLOAD
// DD DISP=SHR,DSN=DSN.DB2VA10.SDSNEXIT
// DD DISP=SHR,DSN=DSN.DB2VA10.SDSNLOAD
// DD DISP=SHR,DSN=ARS.IXM.SIXMLOD1
//SYSPRINT DD SYSOUT=*
//SYSOUT DD SYSOUT=*
//STDERR DD SYSOUT=*
//STDOUT DD SYSOUT=*
//STDPARM DD *
PGM /usr/lpp/ars/V9R0M0/bin/arsxml
add
-h ARCH900 -u odadmin -p blahblah -v
-i /usr/lpp/ars/V9R0M0/bin/xml/samples/ARSIVPadd.ebcdic.xml
/*
//STDENV DD *
CLASSPATH=/usr/lpp/ars/V9R0M0/bin/xml/ODAdmin.jar:
/usr/lpp/java/J6.0_64/lib/core.jar
I noticed that the Load ID is much larger from the IVP:
ARS1144I OnDemand Load Id = >5013-1-0-2FAA-20121010172643-20121010172643-5017<
That's due to the expanded date/time field:
http://www-01.ibm.com/support/docview.wss?uid=swg27036188
I like to run my unloads from batch, so I tried to unload the IVP ***but forgot to update my STEPLIB and ARSBIN***
//STEP1 EXEC PGM=ARSADMIN,REGION=0M,
// PARM=('/-V //DD:IN -u odadmin -p applepi')
//STEPLIB DD DISP=SHR,DSN=ARS.ARSV850.SARSLOAD <<<<---- wrong
//SYSPRINT DD SYSOUT=*
//SYSOUT DD SYSOUT=*
//IN DD *
unload
-h
ARCH900
-g
"ARSIVPR3"
-L
5013-1-0-2FAA-20121010172643-20121010172643-5017
/*
//ARSBIN DD PATH='/usr/lpp/ars/V8R5M0/bin' <------ wrong
//SYSPRINT DD SYSOUT=*,DCB=(RECFM=FBA,LRECL=134,BLKSIZE=134)
//INPSTATS DD SYSOUT=*
//INDSTATS DD SYSOUT=*
//SYSOUT DD SYSOUT=*
//STDERR DD SYSOUT=*
So I got this error message:
The option >-L< argument >5013-1-0-2FAA-20121010172643-20121010172643-5017< is invalid
Proper STEPLIB/ARSBIN took care of that.
However, this is interesting. I logged on with the 8.5.0.5 client to view the System Log and there was no date field displayed to search on.
Aha! The 8.5.0.5 client *works* with a V9 server, but functionality is limited.
Just now ACCEPTing 8.5.0.5 maintenance and AARSHAS1 is not big enough.
I reallocated and it's now 54% used for 4087 tracks.
I'm going to re-allocate AARSHAS1 on V9 to hopefully save myself some grief later.
If so, make sure you have this APAR on when available:
| PTF UK91244 is now available 30 Jan 2013
PM76821 --- MISC UPDATES FOR ONDEMAND V9 INSTALL WIZARD
It'll fix some minor annoyances.
Before UK91244 the ISPF libraries were the same for V8.5 and V9.0. With 9.0, be sure to update your definitions to point to the right libraries.
I just installed the ++APAR for 9.0.0.1.
Quote
IOEZ00312I Dynamic growth of aggregate ARS.ARSV900.PRODUCT.ZFS in
progress, (by user ODV733).
IOEZ00329I Attempting to extend ARS.ARSV900.PRODUCT.ZFS by a secondary
extent.
IOEZ00324I Formatting to 8K block number 81000 for secondary extents of
ARS.ARSV900.PRODUCT.ZFS
IOEZ00309I Aggregate ARS.ARSV900.PRODUCT.ZFS successfully dynamically
grown (by user ODV733).
ALLOCATION for ARS.ARSV900.PRODUCT.ZFS:
SPACE-TYPE------CYLINDER
SPACE-PRI------------300
SPACE-SEC------------100
Here's a list of effective PTFs (supersedes omitted) for V9:
PTF# Size-KB PUT Hiper FMID
-------- ------- ---- ----- -------
UK81565 105 1209 NO H272900
UK81873 33 1209 NO H272900
UK82848 48 1210 NO H272900
UK82993 7220 1210 YES H272900
UK83478 44 1211 NO H272900
UK83602 571 1211 NO H272900
UK91241 70 1301 NO H272900
UK91244 244 1301 NO H272900
UK91344 178909 1302 NO H272900 <--- 9.0.0.1
UK91952 145 1302 NO H272900
UK92228 73 1303 NO H272900
UK92435 88 1303 NO H272900
UK94079 55 1305 NO H272900
UK94202 85 1305 NO H272900
UK94686 55 1305 NO H272900
UK95849 175380 NO H272900 <--- 9.0.0.2