On Mon, 13 Jun 2005 05:29:08 -0500, Dave Cartwright <[EMAIL PROTECTED]> wrote:
>We were finally due to migrate our production system to a supported level >last weekend, but had to back out because JES2 kept falling over. >It is a monoplex running on Flex-ES. We have had a test system and full >clone of Prod running for months with no problem. I cloned the JES spool >volume serials, format started under a test 2.10 system then brought up >zOS - no problem. I have $ACTIVATEd to Z2 and back on the test system. >$D ACTIVATE on Prod shows that is R4 or later - originally it came from a >2.6 system. JES never got syslog going at the migration, so I have no >messages, but on reverting to 2.10 we got this; >HASP096 DISASTROUS ERROR AT SYMBOL DSCDSERR IN CSECT HASPNUC, 396 > MTTR=0015B707,UNIT=0A7C,VOLSER=JES8K1 >HASP080 JES2 SYSTEM DUMP REQUESTED FROM HASPTERM 000116E8 + 003192 >HASP088 JES2 ABEND ANALYSIS 398 >HASP088 ------------------------------------------------------ >HASP088 FMID = HJE7703 LOAD MODULE = HASJES20 >HASP088 SUBSYS = JES2 OS 2.10 >HASP088 DATE = 2005.163 TIME = 15.00.06 >HASP088 DESC = DISASTROUS ERROR AT LABEL DSCDSERR >HASP088 MODULE MODULE OFFSET SERVICE ROUTINE EXIT >HASP088 NAME BASE + OF CALL LEVEL CALLED ## >HASP088 -------- -------- ------- ------- ---------- ---- >HASP088 HASPRAS 000FBC80 + 0003E6 OW49317 *ERROR $DIS >HASP088 HASPNUC 00007000 + 008EDA OW55693 $DISTERR >HASP088 HASPHOPE 0011A698 + 00146C OW48246 $DSCLOSE >HASP088 HASPHOPE 0011A698 + 000708 OW48246 OPJLOG >HASP088 HASPHOPE 0011A698 + 0000E6 OW48246 OPPJOB >HASP088 PCE = HOPE (0B545B70) >HASP088 R0 = 0B5A200C 0B50DC10 0B50DBB8 0B5A200C >HASP088 R4 = 8000FEDA 0B862000 0015B707 0B5A2008 >HASP088 R8 = 0B5A57FC 00000000 0B5A57FC 00007000 >HASP088 R12 = 800FBE62 0B545B70 800FC020 000FBCD0 >HASP088 ------------------------------------------------------ >EA794I SVC DUMP HAS CAPTURED: 397 >UMPID=001 REQUESTED BY JOB (JES2 ) >UMP TITLE=HASPDUMP SUBSYS= JES2 OS 2.10 MODULE= HA > > >JES recovers and carries on. Happened each time we IPL'ed 2.10 >Similar to the messages seen on zOS, but there JES2 said it recovered but >didn't. Do you have all the compatibility maintenance applied? How current are you on maintenance in general for both versions? >Any ideas where to start? IBMLINK. Have you searched for APARs. This could be a fit: APAR Identifier ...... OA09383 ABEND0C4 or msgHASP064 may occur following a DSCDSERR error with OA04212 applied on HJE7703, HJE7705, and HJE7707 *only*. A dump and an open PMR with IBM is also helpful. >Are we going to have to Cold Start? (WHY?) > Doubtfull. $ZAPJOB should fix it. But do you know what the "falling over" error was on z/OS 1.4? This problem could be as a result of what happend during your attempted migration. Be prepared to take a SADUMP next time if you can't figure it out. Cheers, Mark -- Mark Zelden Sr. Software and Systems Architect mailto: [EMAIL PROTECTED] Systems Programming expert at http://Search390.com/ateExperts/ 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
