HP3000-L Archives

February 1996, Week 2

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Stan Sieler <[log in to unmask]>
Reply To:
Stan Sieler <[log in to unmask]>
Date:
Tue, 13 Feb 1996 14:47:48 -0800
Content-Type:
text/plain
Parts/Attachments:
text/plain (36 lines)
Hi all,
 
I tried to telnet to the HPSL machine, and ran into an ironic problem
which can't be reported:
 
   1) telnet support.mayfield.hp.com
   2) enter: hpsl
   3) (behind your back: you've just logged into an HP-UX machine, which
     then connects to an MPE machine, and runs the program:
      SLXUIP.SLXPRG.HPSL
   4) observe the SLXUIP program aborting!
 
      *** Illegal data address (TRAPS 65).
 
   ABORT: SLXUIP.SLXPRG.HPSL
   NM USER  f15.0030e2e0 prcb_mgmt:allocate_prcb+$14c
   NM PROG  155.000e13b4 PROGRAM+$488
 
So, I'd normally use HPSL to report the problem, but....
 
 
BTW, note the relatively high Space ID of $f15, and the procedure in
which the abort occurs (allocate_prcb).  These imply to me:
 
   1) the SLXUIP program is using an XL (other than XL.PUB.SYS)
      (XL.PUB.SYS doesn't have allocate_prcb in it, on any release
      from 4.0 through 5.0.
 
   2) either a bug exists, losing Space IDs, or the 3000 is doing things
      in addition to HPSL work.  (If every session ran SLXUIP.SLXPRG.HPSL,
      with the same XL, then the Space ID would probably be much lower.)
 
--
Stan Sieler                                          [log in to unmask]
                                     http://www.allegro.com/sieler.html

ATOM RSS1 RSS2