- Does it always happen ?
Varies from server to server.
- When did it begin to happen ?
Not sure for certain. Reason being I implemented / fixed an ITO script to report when maestro wasn't running. Since then ITO reports that maestro isn't running and after a check you see that it started, hit traps 68 then aborted, but batchman logs back on again ( as if you'd performed a STOP ), a 2nd start seems to fix it. So it could've been happening for a while but the 'maestro not running' heads up has brouight it to light.
- What did you change IMMEDIATELY before it began to happen (hints : MPE version powerpatch, patches, Maestro, etc.)
Nothing. As mentioned above it varies from server to server on a variety of OS's, however presently it appears to be slaves that are affected. Haven't seen the problem on a maestro master as yet.
- Any idea what triggers the error ?
Had a feeling it might be connected to the backups. Our backup jobs stop all processing then perform a STORE ;ONLINE and once it hits the "FILES ARE NOW FREE" with the NOTIFY, a job streams to restart processing / maestro. As most of our system backups occur at the same time was thinking that maybe the master is still trying to do the first store bit and the start on the slave is perhaps getting some conflict but enough time has elapsed between start's that the 2nd time a start is performed it's then ok.
Regards,
Nige...
-----Original Message-----
From: HP-3000 Systems Discussion [mailto:[log in to unmask]] On Behalf Of Christian Lheureux
Sent: 22 August 2005 15:57
To: [log in to unmask]
Subject: Re: [HP3000-L] Maestro TRAPS 68
Hi Nigel,
That's a DMPT (Data Memory Protection Trap), which is written a little below what you cut-and-pasted in your post. What would be useful would be to restart Maestro with ;DEBUG, check what's at address R-24 immediately before the abort (easier said than done, OK), perhaps set a breakpoint at HPERRPUSH to watch error codes .... basic debug/dumpreading techniques.
Now, here are a few things to check :
- Does it always happen ?
- When did it begin to happen ?
- What did you change IMMEDIATELY before it began to happen (hints : MPE version powerpatch, patches, Maestro, etc.)
- Any idea what triggers the error ?
HTH.
Christian Lheureux
Directeur BU Infrastructure / Manager of IT Infrastructure BU ________________________________
29, rue de Rosières
91240 SAINT-MICHEL-SUR-ORGE
FRANCE
Téléphone :
+33 1 69 72 12 83
Fax :
+33 1 60 15 30 62
Email :
[log in to unmask]
Web :
www.btwcomputing.com
________________________________
En mai 2004,APPIC RH devient BTW Computing, une activité du Groupe BTW In May 2004, APPIC RH becomes BTW Computing, an activity of the BTW Group
> -----Message d'origine-----
> De : HP-3000 Systems Discussion [mailto:[log in to unmask]] De la
> part de Nigel Skeet Envoyé : lundi 22 août 2005 15:43
> À : [log in to unmask]
> Objet : [HP3000-L] Maestro TRAPS 68
>
> Hi Listers,
>
> Any Maestro experts about ? Just wanted to know what causes Maestro to
> abend when starting with a TRAPS 68. Here's an extract from the
> STDLIST and seems that another START seems to fix the problem.
>
> 221 MAESTRO XL/BATCHMAN D.01.63 (C) Tivoli Systems Inc. 1998
> 222 XL: D.01.05 Library - XLAIF30 (C) Unison Software Inc. 1990
> 223 XL: D.01.00 Maestro Access (C) Unison Software Inc. 1990
> 226 **** Data memory protection trap (TRAPS 68).
> 227
> 228 ABORT: BATCHMAN.MAESTRO.CCC
> 229 PC=868.0000f548 $big_wa1
> 230 NM* 0) SP=41846530 RP=868.00068718 readhead+$90
> 231 NM 1) SP=41846530 RP=868.0001e7a8 initialize+$620
> 232 NM 2) SP=418464f0 RP=868.0001f2dc PROGRAM+$1a4
> 233 NM 3) SP=418461b0 RP=868.00000000
> 234 (end of NM stack)
> 235
> 236 R0 =00000000 00000000 0001e7ab 82dde400 R4 =d634a018 00000001
> 00000000
> 00000000
> 237 R8 =00000000 00000000 00000000 00000000 R12=00000000 00000000
> 00000000
> 00000000
> 238 R16=00000000 00000000 00000000 00000518 R20=4163aa40 00000000
> 00000a18
> 00000000
> 239 R24=00000100 4163aa40 00000000 41638000 R28=00000002 00000100
> 41846530
> 0006871b
> 240
> 241 IPSW=0004000f=jthlnxbCvmrQPDI PRIV=3 SAR=0010 PCQF=868.f54b
> 868.f
> 54f
> 242
> 243 SR0=0000000a 00000a18 00000518 00000000 SR4=00000868 00000518
> 0000000b
> 0000000a
> 244 TR0=02f69280 0000a000 008434c8 d852c000 TR4=d400b734 41847580
> 0022c374
> 0000000f
> 245 PID1=0312=0189(W) PID2=0000=0000(W) PID3=0000=0000(W)
> PID4=0000=00
> 00(W)
> 246
> 247 RCTR=00000000 ISR=00000a18 IOR=00000000 IIR=4f574100
> IVA=00149000 ITMR
> =a8daafa5
> 248 EIEM=ffffffff EIRR=00000000 CCR=00c0
> 249
> 251 MAILMAN:01:47/+
> 252 MAILMAN:01:47/+ Error Batchman abended, Status: No info avail
> [2073.1]
>
> 253 MAILMAN:01:47/+
>
> Regards,
>
> Nige...
>
> * To join/leave the list, search archives, change list settings, *
> * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
|
