I don't know if this is related, but we just got bit with DB2 server hard down. We installed z/VM 5.2.0 on a 2084 this weekend and DB2 came up OK at 6am Sunday and ran until 11pm. A batch job at that point crashed and took down the DB2 server. The directory, we think, was corrupted. Fortunately, we had a backup from Sunday so we were able to get the server back up, but we aren't running that batch job. The job was tested OK on a second level guest of the same VM system, running z/VM 5.2.0 under z/VM 5.1.0.
DB2 support seem to think it is a problem with data spaces. VM support says we have all the latest PTFs, but there is a piece of microcode for the 2084 that we don't have. On Mon, 30 Jan 2006 09:30:59 -0500, Roland P. Chung <[EMAIL PROTECTED]> wrote: >Hi all, Please be adviced that you shouold do more frequent archive of your >DB2/VM database if you are using dataspace support and is running under z/VM 5.20. > > I will provide more information on this subject later. > > > *** cross post to VSE-L *** > > >With best regards, > >...Roland Chung >Senior Technical Specialist (S/390,VM/VSE,DB2/VSE&VM) >MAXC Consultants Inc. >Voice/Fax: 416-469-3280 (If busy, call: 416-469-2268) >197 Hastings Ave., Toronto, Ontario, Canada. M4L 2L6 > >** Life is short. Stop once in a while and smell the roses. **
