Based on the output of the debug commands, it does not appear
to be a corrupt SL..I have seen the corrupt SL problem before
and it will be line for line as documented.

>>If you don't see the "SUB,NSV & BLE", then you don't have this problem.

If you take that literally (and you should) then you don't have the problem

-Guy

> -----Original Message-----
> From: Eben Yong [mailto:[log in to unmask]]
> Sent: Monday, February 03, 2003 11:58
> To: [log in to unmask]
> Subject: Re: ADAGER REPACK bombed
>
>
> Sorry, the $STDLIST has already been deleted.  Even so, since
> the system
> crashed, the $STDLIST, when I reviewed it, did not contain any errors.
> Presumably, the errors did not get written to the $stdlist, or the
> system crash precluded that from occurring.
>
> I assumed that the problem was as a result of the incorrectly
> OCTCOMP'ed
> system SL, so I did not make much of the crash.  I had a
> backup, and it
> took me all of 20 minutes to reboot the system, and 90 minutes for the
> DB restore.  I'll attempt this again soon and will be sure to
> record the
> FLT codes on the console IF the system crashes again.
>
> By the way, I *would* have done a much better of job of
> trouble-shooting
> the system, except that I was constrained by family duties.  This past
> weekend was Chinese New Year, and my priority was to get the
> system back
> up and running, and spend as much time with family as possible.  The
> family gathering, at least, did not experience any "system
> crashes", in
> spite of my HPe3000's "misbehavior"!
>
> -----Original Message-----
> From: Patrick Mullen [mailto:[log in to unmask]]
> Sent: Monday, February 03, 2003 10:17 AM
> To: [log in to unmask]
> Cc: Eben Yong
> Subject: [HP3000-L] ADAGER REPACK bombed
>
> Eben,
>
> >This past weekend, I attempted a repack of a jumbo dataset, and it
> >crashed my system.  Apparently the problem may have already been
> >identified in previous R&D, with a fix already provided by
> HP.  Here's
> >the note from SR: 8606232211 (KBRC00007442):
>
> Crashed the system?  No, that was NOT a hallmark of the incorrectly
> OCTCOMP'ed system SL.  That problem caused an integer overflow that
> terminated Adager, but it never 'crashed a system' as far as
> I have ever
> encountered.
>
> Do you have any feedback from the session or job that was running
> Adager?
> A stdlist, pscreen, copy and paste?
>
> Please let me know.
>
> Patrick
>  _______________
> |               |
> |               |
> |            r  |  Patrick                   [log in to unmask]
> |          e    |                            http://www.adager.com
> |        g      |  Patrick Mullen
> |      a        |  R & D Labs / Technical Support
> |    d          |  Adager Corporation
> |  A            |  Sun Valley, Idaho 83353-3000             U.S.A.
> |               |
> |_______________|
>
>
> CONFIDENTIALITY NOTICE:  This e-mail, including attachments,
> is for the
> sole use of the individual(s) to whom it is addressed, and may contain
> confidential and privileged information. Any unauthorized review, use,
> disclosure, distribution, or reproduction is prohibited. If you have
> received this e-mail in error, please notify the sender by
> reply e-mail
> and destroy this message and its attachments. Thank you for your
> cooperation.
>
> * 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 *