Ray asks:
>
> I'm getting a status value of -12451740
> (-190/100) from HPSWTONMNAME, but I can't
> find any reference to error -190 for subsys
> 100 anywhere on our system.
>
> Anybody have any ideas?
 
But of course!  :)
 
But...only if you submit an SR against a missing error catalog message :)
(Every error should be in the message catalog!)
 
Answer:  "Illegal Proc Len"
 
This is probably an error indicating that the length of the name
of the procedure you wanted to switch to was "bad" (illegal).
 
How did I find this?   (input is show indented)
 
   :debug
       (requires PM)
 
   = -#12451740
$ff420064
 
       (unpack the original error number, will then sign extend the)
       (upper 16 bits... (the "info" field)...                     )
       (ok, the "info" is $ffffff42, and the "subsys" is $64 (#100))
 
   = errmsg (#32765, #100)
'Switch'
 
       (#32765 is a magic number which generally gets you the subsystem
       name.  True, it *should* have been:  = errmsg (0, #100), but...)
 
   symopen symos.osb79.telesup             (the 5.0 push file)
 
   :fetch symos.osb79.telesup
 
       (The SYMOS file is big (19 MB).  Without a "prefetch" of the file,
        the following SYML command would cause 4941 page faults, and
        therefore take many more minutes to complete)
       (Plug: fetch calls KLONDIKE, one of the Nuggets, which brings the
        file into memory with about 20 disc read
 
   env filter '$ffffff42'
   syml ,, c
 
DBG_INFO_TARGET_NON_EXIST               CONST   SUBRANGE     $ffffff42
SWERR_ILL_PROC_LEN                      CONST   SUBRANGE     $ffffff42
W_DIR_SELEQ_NO_FILES                    CONST   SUBRANGE     $ffffff42
 
Only the "SWERR_ILL_PROC_LEN" looked like a constant likely to be
associated with a Switch error.
 
   env filter ''
   c
 
--
Stan Sieler                                          [log in to unmask]
                                     http://www.allegro.com/sieler.html