Copyright Digital Equipment Corp. All rights reserved.

DIAGNOSTICS

      DIAGNOSTICS
      
          The following error messages can occur when running I-MON:
      
          can't access image file `ARGUMENT' VMS-MESSAGE
      
               I-MON  cannot read the symbol table of the image executing in
               the process being monitored. The VMS-MESSAGE is the RMS  file
               open message. If the problem persists, copy the image file to
               a  local  directory  and  use  the /exe=file option to direct
               I-MON to read the file locally.
      
          can't assign terminal `ARGUMENT' VMS-MESSAGE
      
               There  is  a  problem  with  the  logical  name   TT   and/or
               sys$output.
      
          can't collect to file for states/modes select
          can't deas chan stat = VMS-MESSAGE
      
               Internal failure which should not occur.
      
          can't find my old priority VMS-MESSAGE
      
               I-MON  needs  to  be  able  to alter its priority. This is an
               internal failure which should not occur.
      
          can't get to terminal `ARGUMENT'
      
               There  is  a  problem  with  the  logical  name   TT   and/or
               sys$output.
      
          can't locate image 'ARGUMENT'
      
               The  image  name  specified  on the command line could not be
               found. Run I-MON again and specify either the  correct  image
               or  use  /process  or  /id  to  specify  the  process  to  be
               monitored.
      
          can't locate process 'ARGUMENT'
      
               The process name specified on the command line could  not  be
               found. Run I-MON again and specify either the correct process
               name  or  use  /image  or  /id  to  specify the process to be
               monitored.
      
          can't open file for replay
      
               The file specified in /input could  not  be  opened  (usually
               because the file name was misspelled).
      
          can't open terminal description file
      
               The file specified in /terminal=file could not be accessed.
      
          can't set up an exit handler VMS-MESSAGE
          cant associate mailbox `ARGUMENT' in assign: VMS-MESSAGE
          cant do crembx: VMS-MESSAGE
          cant enable mailbox: VMS-MESSAGE
          cant set up ast on mailbox: VMS-MESSAGE
      
               All  of the above are messages which indicate some failure in
               I-MON due to some  VMS-type  problems  such  as  insufficient
               quotas or privileges.
      
          invalid /restrict=PROC or /restrict=(PROC:SIZE) format
          invalid delta quantity `ARGUMENT'
          invalid numeric argument 'ARGUMENT'
          invalid numeric argument 'ARGUMENT' (0..4000)
          invalid numeric argument for seconds 'ARGUMENT'
          invalid process id `ARGUMENT'
          invalid screen descriptor field `ARGUMENT'
      
               A  syntax  error or a value not in the correct range. Correct
               the input command line and run again.
      
          license required
      
               An attempt has been made to run I-MON on a machine for  which
               it is not configured. Call Bear Computer Systems.
      
          missing values for /buckets=(from,to,by)
          missing values for /collect=(from,to)
      
          process is suspended or hibernating, can't determine pid
      
               If the process  to  be  monitored  was  specified  using  the
               process  name  or  image name, and it will not respond to the
               getjpi service, then the process can not be monitored.
      
          qualifier(s) /rawin requires an input file via /input
          qualifier(s) /restrict and /collect are mutually exclusive
      
          syntax error or VALUE required with /terminal
      
               If  /terminal was entered, then an argument describing either
               a file or the name of a supported terminal, such as vt100  or
               vt52, must be supplied.
      
          terminal has invalid sizing
      
               When specifying a terminal specification file enter the  size
               for the number of columns and rows.
      
          terminal must support a clear function
          terminal must support a home function
      
               When specifying a terminal specification file, a clear and  a
               home function must be specified.
      
          timer failure VMS-MESSAGE
          timer startup failure
      
               The  above  are messages which indicate some failure in I-MON
               due to some VMS type problems such as insufficient quotas  or
               privileges.
      
          too few  buckets
          too many buckets
      
               When  using the /buckets command qualifier, I-MON requires at
               least 10 buckets, and at most 20000 buckets.  Check  to  make
               sure  that the bucket size argument is correct. Remember that
               if it begins with a leading '0', this means that the value is
               the decimal number of buckets instead of the bucket  size  in
               hex.
      
          unknown terminal type, not vt52 or vt100
      
               If I-MON is not told what type of terminal is being used (see
               /terminal) then it will check  the  terminal  characteristics
               for device TT. If this is not vt52  or  vt100,  vt200,  vt300
               compatible,  then  /terminal must be used. If a terminal type
               of vtxx is specified in the set  terminal  VMS  command  (for
               example, vt220) then I-MON will assume that the terminal is a
               vt100  (any  vt100,vt200,vt300  series compatible terminal is
               considered a vt100 by I-MON).
      
          virtual address space full
      
               This  is  probably caused by the high speed memory allocation
               routine running out of space during a long run. Try rerunning
               the same command but add "/free" to use  the  more  efficient
               but slower memory allocation scheme.
      
               If  the  use  of  the  /free  qualifier doesn't help then the
               "pagefile" quota may be too small. This can be changed by the
               system manager in the authorization  file.  If  this  is  not
               enough   then   investigate   whether  the  sysgen  parameter
               "virtualpagecnt" is now too small.