1 
    2 
    3 
    4 
    5 
    6 
    7 
    8 
    9 
   10 
   11 
   12               MULTICS MR12.7 ERROR MESSAGE DOCUMENTATION
   13 
   14                          February 17, 2020^L
   15 
   16 
   17 INTRODUCTION
   18 
   19      This  document  has  been  prepared  automatically  from the
   20 system source by Multics Software Support.  Every effort has been
   21 made  to supply  documentation for  each and  every message  that
   22 could appear either on the system console, or in the system logs.
   23 However,  some of the  system messages are  not provided in  this
   24 document due  to the messages developed prior  to the development
   25 of  the  error  messages  document,  or  omitted  in  error.  The
   26 following is a list of modules  that are known to be missing from
   27 this document:
   28 
   29 
   30 as_access_audit_.pl1             monitor_cache.pl1
   31 as_any_other_handler_.pl1        mos_edac_summary.pl1
   32 as_ibm3270_mpx_.pl1              mos_edac_summary.pl1
   33 as_send_user_mail_.pl1           mpc_data_summary.pl1
   34 as_send_user_message_.pl1        mseg_error_v3_.pl1
   35 as_uncp_mpx_.pl1                 mseg_error_v4_.pl1
   36 as_vip7760_mpx_.pl1              multiplexer_mgr_.pl1
   37 asr_com_channel_info_srvr_.pl1   pc_recover_sst.pl1
   38 asum_error_.pl1                  pdir_volume_manager_.pl1
   39 bootload_fs_.pl1                 poll_fnp.pl1
   40 cancel_abs_request.pl1           poll_mpc.pl1
   41 dir_dump.pl1                     polled_vip_mpx.pl1
   42 display_cpu_error.pl1            print_syserr_msg_.pl1
   43 display_cpu_error.pl1            print_syserr_msg_.pl1
   44 ec_shift_config_change_.pl1      protocol_mpx.pl1
   45 emergency_shutdown.alm           rcp_mount_timer_poll_.pl1
   46 extract_msg_doc_.pl1             rcp_pre_claim_.pl1
   47 find_rpv_subsystem.pl1           rcprm_verify_registries_.pl1
   48 fnp_data_summary.pl1             read_disk_label.pl1
   49 hc_device_acct_.pl1              salv_directory.pl1
   50 hc_tune.pl1.pmac                 salv_err_msg.pl1
   51 hc_tune.pl1.pmac                 salvager.pl1
   52 heals_collect_data_.pl1          sc_admin_mode_.pl1
   53 initial_error_handler.pl1        sys_log_.pl1
   54 initial_error_handler.pl1        syserr.alm
   55 install_ttt_.pl1                 syserr_log_daemon.pl1
   56 io_error_summary.pl1             tty_read.pl1
   57 io_error_summary.pl1             uc_create_process_.pl1
   58 io_reconfig.pl1                  uc_create_process_check_.pl1
   59 ioi_page_table.pl1               uc_dial_.pl1
   60 iom_switches.pl1                 uc_list_disconnected_procs_.pl1
   61 level_error.pl1                  uc_login_.pl1
   62 list_abs_requests.pl1            uc_logout_.pl1
   63 ls_request_server_.pl1           uc_ls_create_request_.pl1
   64 mc_check_acs_.pl1                uc_ls_destroy_request_.pl1
   65 mc_con_rec_.pl1                  uc_ls_dial_request_.pl1
   66 mc_wakeups_.pl1                  uc_ls_disconnect_request_.pl1
   67 mcs_timer_daemon.pl1             uc_ls_list_request_.pl1
   68 mdc_check_mdcs_.pl1              uc_ls_logout_request_.pl1
   69 monitor_cache.pl1                uc_ls_new_proc_request_.pl1
   70 
   71 
   72                                 2             08/03/23     MR12.7^L
   73 
   74 
   75 uc_ls_operator_request_.pl1      uc_setup_process_connect_.pl1
   76 uc_ls_process_request_.pl1       uncp.pl1
   77 uc_ls_rq_server_wakeup_.pl1      uncp_boot_interrupt.pl1
   78 uc_ls_validate_request_.pl1      uncp_multiplexer.pl1
   79 uc_proc_term_handler_.pl1        uncp_util.pl1
   80 uc_send_ls_response_.pl1         up_cdt_.pl1
   81 uc_set_pit_tty_info_.pl1         user_table_mgr_.pl1
   82 
   83 EXPLANATION OF ERROR MESSAGES
   84 
   85      For each message,  an example of the text of  the message is
   86 provided, followed by four  paragraphs:  Severity, Time, Meaning,
   87 and Action.
   88 
   89 Message Example
   90 
   91      The message example  is a literal copy of  the message, with
   92 substitutable fields  shown in all capitals.   Each substitutable
   93 field is described in the Meaning paragraph.
   94 
   95 Output
   96 
   97      The output  field describes how the message  is output.  For
   98 hardcore  messages  it  shows  the  interpretation  of  the first
   99 argument to SYSERR, which  determines whether the system crashes,
  100 sounds  the  beeper,  etc.   For  answering  service messages, it
  101 describes the output stream and source.
  102 
  103 Time
  104 
  105      The  time section  describes the  time when  the message  is
  106 possible.
  107 
  108 Meaning
  109 
  110      The meaning paragraph describes  the situation that prompted
  111 the  message and the  probable cause of  the situation.  It  then
  112 describes  the  consequences  of  the  situation.   Substitutable
  113 parameters in the message example are explained here.
  114 
  115 Action
  116 
  117      The  action  paragraph  describes  what  operator  action is
  118 required when the message occurs.
  119 
  120 
  121 
  122 
  123 
  124 
  125 
  126 
  127 
  128 
  129 
  130                                 3             08/03/23     MR12.7^L
  131 
  132 
  133                [rldr_arg_reader_.pl1]
  134                rldr_arg_reader_:  Implementation Restriction, the
  135                RPV  must  be  reloaded  separately  to obtain the
  136                required physical volume information.
  137 
  138 
  139 
  140      Stream:   BOS Typewriter.
  141 
  142      Time:     While system is running.
  143 
  144      Meaning:  Due to an implementation restriction, the RPV must
  145                be  reloaded separately   from the  other physical
  146                volumes.  Reload the RPV first, then re-invoke the
  147                reload_volue  command  with   the  other  physical
  148                volume names to be reloaded.
  149 
  150      Action:   Enter a corrected command line.
  151 
  152 
  153                [scas_init.pl1]
  154                "scas_init:   MEM Y.   Tags greater  than "D"  not
  155                supported by DPS8 CPUs",
  156 
  157 
  158      Stream:   BOS Typewriter (Crashes system)
  159 
  160      Time:     System Intialization.
  161 
  162      Meaning:  The  physical configuration  or the  configuration
  163                deck is  incorrect.  DPS8 CPUs have  only 4 memory
  164                ports, therefore Multics systems comprised of DPS8
  165                cpus or  mixed systems of  DPS, L68 and  DPS8 cpus
  166                can  only  have   4  memories  configured.   (i.e.
  167                Memory tags A, B, C, and D).
  168 
  169      Action:   Correct  the  physical  configuration  and/or  the
  170                configuration deck and reboot.
  171 
  172 
  173                [sc_process_command_line_.pl1]
  174                (input on SWITCH_NAME) REQUEST_LINE
  175 
  176 
  177      Stream:   as (severity 0)
  178 
  179      Time:     In response to an operator command.
  180 
  181      Meaning:  Logs a  REQUEST_LINE typed by the  operator, or by
  182                another   user  via   the  send_admin_command   or
  183                send_initializer_command commands.
  184 
  185      Action:   No operator action is required.
  186 
  187 
  188 abs ACTION                      4             08/03/23     MR12.7^L
  189 
  190 
  191 
  192 
  193                [absentee_utility_.pl1]
  194                abs ACTION:  N requests ACTIONed.
  195 
  196 
  197      Stream:   as (severity1)
  198 
  199      Time:     In  response  to  an  abs  defer  or  abs  release
  200                command.
  201 
  202      Meaning:  Indicates  success  or  failure  of  the  command.
  203                ACTION can be defer or  release, and N can be "no"
  204                or the number of requests acted upon.
  205 
  206      Action:   Confirm that the expected results were obtained.
  207 
  208 
  209                [absentee_utility_.pl1]
  210                abs  run:   job   selection  arguments  matched  N
  211                requests; be more specific.
  212 
  213 
  214      Stream:   as (severity1)
  215 
  216      Time:     In response to an abs run command.
  217 
  218      Meaning:  The  specified arguments  matched either  zero, or
  219                more than one, request, and so no job was run.
  220 
  221      Action:   Re-enter  the command  with correct  arguments, to
  222                select exactly one job for running.
  223 
  224 
  225 
  226                [absentee_utility_.pl1]
  227                abs run:  request PATH ID is already running.
  228 
  229 
  230      Stream:   as (severity1)
  231 
  232      Time:     In response to an abs run command.
  233 
  234      Meaning:  The specified job is already running.
  235 
  236      Action:   If  a  mistake  was   made,  repeat  the  command,
  237                specifying the correct job.
  238 
  239 
  240                [absentee_user_manager_.pl1]
  241                absentee_user_manager_  (abs   run):   System  too
  242                full; no absentee jobs can be started now.
  243 
  244 
  245 
  246 absentee_user_manager_ (abs run)5             08/03/23     MR12.7^L
  247 
  248 
  249      Stream:   as (severity1)
  250 
  251      Time:     In response to an abs run command.
  252 
  253      Meaning:  The system  is too near the upper  limit on logged
  254                in users to start any absentee jobs.
  255 
  256      Action:   If the immediate running  of the job is essential,
  257                use  "abs  stop  queue  all"  to  halt  all  other
  258                absentee logins, change the login word to halt all
  259                interactive logins, and either  wait for a process
  260                to log out, or bump  one, before repeating the abs
  261                run command.
  262 
  263 
  264 
  265                [absentee_user_manager_.pl1]
  266                absentee_user_manager_$init:    MESSAGE.    Cannot
  267                truncate absentee_user_table.
  268 
  269 
  270      Stream:   as (severity1)
  271 
  272      Time:     System Intialization.
  273 
  274      Meaning:  It    was    not    possible    to    clear    the
  275                absentee_user_table segment.
  276 
  277      Action:   Contact the system programming staff.
  278 
  279 
  280                [absentee_user_manager_.pl1]
  281                absentee_user_manager_:    ERROR   attempting   to
  282                cancel reservation R for USER.PROJ absN
  283 
  284 
  285      Stream:   as (severity1)
  286 
  287      Time:     While system is running.
  288 
  289      Meaning:  The  system  was  unable   to  cancel  a  resource
  290                reservation for an absentee  process that is being
  291                destroyed.     The   resource(s)    might   remain
  292                unavailable to other users.  There is some problem
  293                in the resource reservation mechanism.
  294 
  295      Action:   Contact the system programming staff.
  296 
  297 
  298                [absentee_user_manager_.pl1]
  299                absentee_user_manager_:    ERROR   attempting   to
  300                pre-claim reservation R for USER.PROJ absN
  301 
  302 
  303 
  304 absentee_user_manager_          6             08/03/23     MR12.7^L
  305 
  306 
  307      Stream:   as (severity1)
  308 
  309      Time:     While system is running.
  310 
  311      Meaning:  The  system  was  unable   to  assign  a  resource
  312                reservation  to  an  absentee  job  that  is being
  313                logged in.  The job will be run, but it might fail
  314                if the resources it needs happen to be unavailable
  315                when it  requests them.  There is  some problem in
  316                the resource reservation mechanism.
  317 
  318      Action:   Contact the system programming staff.
  319 
  320 
  321                [absentee_user_manager_.pl1]
  322                absentee_user_manager_:   Error   in  initializing
  323                absentee.  Don't bring up absentee facility
  324 
  325 
  326      Stream:   as (severity1)
  327 
  328      Time:     While system is running.
  329 
  330      Meaning:  The absentee mechanism will not initialize.
  331 
  332      Action:   Contact the system programming  staff.  Do _^Hn_^Ho_^Ht try
  333                to initialize the absentee facility.
  334 
  335 
  336 
  337                [absentee_user_manager_.pl1]
  338                absentee_user_manager_:  Error:  CONDITION
  339 
  340 
  341      Stream:   as (severity2)
  342 
  343      Time:     While system is running.
  344 
  345      Meaning:  An unexpected fault  has occurred while performing
  346                some  absentee function such  as logging in  a new
  347                absentee user.  The  system automatically performs
  348                an Answering Service dump and attempts to recover.
  349 
  350      Action:   No  action   is  required  unless   the  condition
  351                persists.  If this  message occurs repeatedly, try
  352                stopping   the  absentee   facility;  inform   the
  353                programming staff.
  354 
  355 
  356 
  357                [absentee_user_manager_.pl1]
  358                absentee_user_manager_:    ERROR_MESSAGE.   Cannot
  359                create absentee event channel
  360 
  361 
  362 absentee_user_manager_          7             08/03/23     MR12.7^L
  363 
  364 
  365      Stream:   as (severity2)
  366 
  367      Time:     System Intialization.
  368 
  369      Meaning:  The absentee facility could not create part of its
  370                communications mechanism.  No absentee process can
  371                be logged in.
  372 
  373      Action:   Try the abs start  command again.  If the absentee
  374                facility  still  fails,   inform  the  programming
  375                staff.
  376 
  377 
  378 
  379                [absentee_user_manager_.pl1]
  380                absentee_user_manager_:   ERROR_MESSAGE.  Creating
  381                proc for NAME.PROJ
  382 
  383 
  384      Stream:   as (severity2)
  385 
  386      Time:     While system is running.
  387 
  388      Meaning:  A storage system error prevented the absentee user
  389                from logging in.  This is due to some error in the
  390                process  creating  mechanism.   The  user  is  not
  391                logged in.
  392 
  393      Action:   Contact the  system programming staff.   Shut down
  394                the absentee facility with an  abs bump * * and an
  395                abs stop if this message occurs repeatedly.
  396 
  397 
  398 
  399                [absentee_user_manager_.pl1]
  400                absentee_user_manager_:  ERROR_MESSAGE.  Trying to
  401                wakeup   PERSON.PROJECT.TAG   process   after  abs
  402                release.
  403 
  404 
  405 
  406      Stream:   as (severity 0)
  407 
  408      Time:     Called  in  response  to  an  operator abs release
  409                command.
  410 
  411      Meaning:  A failure  occurred while sending a  wakeup to the
  412                absentee process being released.  ERROR_MESSAGE is
  413                the text  associated with the error  code returned
  414                by hcs_$wakeup.
  415 
  416      Action:   No operator action is required.
  417 
  418 
  419 
  420 absentee_user_manager_          8             08/03/23     MR12.7^L
  421 
  422 
  423 
  424 
  425                [absentee_user_manager_.pl1]
  426                absentee_user_manager_:  event calls were masked.
  427 
  428 
  429      Stream:   sc (user_output)
  430 
  431      Time:     While system is running.
  432 
  433      Meaning:  This  message  indicates  a  serious  error in the
  434                Initializer  programs.   The  system  attempts  to
  435                recover and keep running.
  436 
  437      Action:   Contact the system programming staff.
  438 
  439 
  440                [absentee_user_manager_.pl1]
  441                absentee_user_manager_:  Premature stopstop for ID
  442 
  443 
  444      Stream:   as (severity0)
  445 
  446      Time:     While system is running.
  447 
  448      Meaning:  An error has occurred  while trying to destroy the
  449                absentee  process  ID.   The  system  recovers and
  450                continues.
  451 
  452      Action:   No operator action is required.
  453 
  454 
  455                [absentee_user_manager_.pl1]
  456                absentee_user_manager_:      Process    terminated
  457                USER.PROJ ID MESSAGE.
  458 
  459 
  460      Stream:   as (severity0)
  461 
  462      Time:     While system is running.
  463 
  464      Meaning:  The   absentee  process    ID  of   USER.PROJ  has
  465                terminated for  the reason specified, and  will be
  466                logged out.
  467 
  468      Action:   No operator action is required.
  469 
  470 
  471                [absentee_user_manager_.pl1]
  472                absentee_user_manager_:   Strange   event  message
  473                WWWWWWWWWWWW    WWWWWWWWWWWW   from    user   proc
  474                WWWWWWWWWWWW
  475 
  476 
  477 
  478 absentee_user_manager_          9             08/03/23     MR12.7^L
  479 
  480 
  481      Stream:   as (severity1)
  482 
  483      Time:     While system is running.
  484 
  485      Meaning:  This message  is similar to the  preceding message
  486                described above,  except that the signal  does not
  487                come  from  the  Initializer  but  from some other
  488                process.  The process ID of the sending process is
  489                printed  in octal.   The event  message was  not a
  490                valid  item.  The  system ignores  the signal  and
  491                goes on.
  492 
  493      Action:   If absentee  jobs will no  longer run, try  an abs
  494                stop  and   an  abs  start.   Inform   the  system
  495                programming staff.
  496 
  497 
  498 
  499                [absentee_user_manager_.pl1]
  500                absentee_user_manager_:   Strange   event  message
  501                WWWWWWWWWWWW WWWWWWWWWWWW from Initializer
  502 
  503 
  504      Stream:   as (severity1)
  505 
  506      Time:     While system is running.
  507 
  508      Meaning:  An unrecognizable event  message has been received
  509                from the Answering Service.   Its value is printed
  510                in octal.  Usually, the first word is the function
  511                code  and the  second word   is the  index in  the
  512                absentee user  table.  This condition is  due to a
  513                error  in   the  Answering  Service   or  absentee
  514                programs.  The system ignores  the signal and goes
  515                on.  The absentee facility may cease to operate.
  516 
  517      Action:   If absentee  jobs will no  longer run, try  an abs
  518                stop  and   an  abs  start.   Inform   the  system
  519                programming staff.
  520 
  521 
  522 
  523                [absentee_user_manager_.pl1]
  524                absentee_user_manager_:   Strange   event  message
  525                WWWWWWWWWWWW WWWWWWWWWWWW from NAME.PROJ TTY
  526 
  527 
  528      Stream:   as (severity1)
  529 
  530      Time:     While system is running.
  531 
  532      Meaning:  This message is similar  to the preceding message,
  533                except that the name, project, and tty name of the
  534 
  535 
  536 absentee_user_manager_          10            08/03/23     MR12.7^L
  537 
  538 
  539                user sending  the wakeup are printed.   The system
  540                ignores the signal and goes on.
  541 
  542      Action:   No operator action is required.
  543 
  544 
  545                [absentee_user_manager_.pl1]
  546                absentee_user_manager_:  Trace ....
  547 
  548 
  549      Stream:   as (severity1)
  550 
  551      Time:     While system is running.
  552 
  553      Meaning:  This is trace output.   It begins coming out about
  554                every          five         minutes          after
  555                absentee_user_manager_$aum_trace_on is called.
  556 
  557      Action:   No  operator  action  is  required.   To shut this
  558                message                 off,                 type:
  559                absentee_user_manager_$aum_trace_off    while   in
  560                admin mode.
  561 
  562 
  563 
  564                [absentee_utility_.pl1]
  565                absentee_utility_ (abs run):  Request PATH ID will
  566                be  run  in   spite  of  unavailable  resource(s):
  567                RESOURCE
  568 
  569 
  570      Stream:   as (severity1)
  571 
  572      Time:     In response to an abs run command.
  573 
  574      Meaning:  The  job selected  by  the  abs run  command needs
  575                RESOURCE, which  is unavailable.  The job  will be
  576                logged in anyway.
  577 
  578      Action:   If the job is critical, the resource could be made
  579                available  by force  detaching it  from some other
  580                process.  This is a drastic action, and should not
  581                be   taken  without  the   System  Administrator's
  582                approval.
  583 
  584 
  585 
  586                [absentee_utility_.pl1]
  587                absentee_utility_  (setup_queue):   Invalid  queue
  588                number:  QUEUE
  589 
  590 
  591      Stream:   as (severity2)
  592 
  593 
  594 absentee_utility_ (setup_queue) 11            08/03/23     MR12.7^L
  595 
  596 
  597      Time:     While system is running.
  598 
  599      Meaning:  The internal queue number in absentee_utility_ was
  600                invalid when trying to  find an absentee to login.
  601                If  this  occurs,  there   is  a  logic  error  in
  602                absentee_utility_.
  603 
  604      Action:   Contact the system programming staff.
  605 
  606 
  607                [absentee_utility_.pl1]
  608                absentee_utility_:      >sc1>absentee_data     has
  609                overflowed its limit of N entries.
  610 
  611 
  612      Stream:   as (severity2)
  613 
  614      Time:     While system is running.
  615 
  616      Meaning:  The  absentee facility  keeps a  list of  absentee
  617                jobs  that   are  either  deferred   or  currently
  618                running.  This list has a capacity of about 13,000
  619                entries.  It is extremely  unlikely that this data
  620                area  will fill  up unless  some user  program has
  621                entered a loop and is submitting requests for jobs
  622                faster than the jobs are being run.
  623 
  624      Action:   Contact the system programming staff.
  625 
  626 
  627                [absentee_utility_.pl1]
  628                absentee_utility_:   >sc1>absentee_data   will  be
  629                rebuilt.
  630 
  631 
  632      Stream:   as (severity1)
  633 
  634      Time:     While system is running.
  635 
  636      Meaning:  An  attempt will  be made  to rebuild  the request
  637                lists  in  absentee_data   to  correct  the  error
  638                reported by the previous message.
  639 
  640      Action:   Note for system programmer action.
  641 
  642 
  643                [absentee_utility_.pl1]
  644                absentee_utility_:  Absentee processing suspended.
  645                Contact system programmer.
  646 
  647 
  648      Stream:   as (severity2)
  649 
  650 
  651 
  652 absentee_utility_               12            08/03/23     MR12.7^L
  653 
  654 
  655      Time:     While system is running.
  656 
  657      Meaning:  Absentee processing has  been suspended because of
  658                the error  described in the previous  message.  No
  659                more jobs will be started, but logged in jobs will
  660                continue running.   The absentee facility  has not
  661                been stopped,  and an "abs start"  command will be
  662                rejected.  After the error has been corrected, the
  663                "abs start queue N" command  may be used to resume
  664                the processing of  requests from queues unaffected
  665                by the error.
  666 
  667      Action:   Contact the system programming staff.
  668 
  669 
  670                [absentee_utility_.pl1]
  671                absentee_utility_:  Attempt to  set defer timer to
  672                time in past (TIME).  Setting  it to a minute from
  673                now.
  674 
  675 
  676      Stream:   as (severity0)
  677 
  678      Time:     While system is running.
  679 
  680      Meaning:  An attempt  was made to set  the absentee deferred
  681                request timer to a time in the past.
  682 
  683      Action:   No operator action is required.
  684 
  685 
  686                [absentee_utility_.pl1]
  687                absentee_utility_:  Attempting to reserve RESOURCE
  688                for PERS.PROJ (PATH)
  689 
  690 
  691      Stream:   as (severity2)
  692 
  693      Time:     While system is running.
  694 
  695      Meaning:  An error occurred during  the attempt to reserve a
  696                resource for an absentee job.  The job is deferred
  697                and  the  attempt  to   reserve  the  resource  is
  698                repeated  at   some  later  time.    The  absentee
  699                facility continues to operate.  There is something
  700                wrong with  the resource reservation  mechanism or
  701                with some other part of RCP.
  702 
  703      Action:   Contact the system programming staff.
  704 
  705 
  706                [absentee_utility_.pl1]
  707 
  708 
  709 
  710 absentee_utility_               13            08/03/23     MR12.7^L
  711 
  712 
  713                absentee_utility_:   BUG:   lc  ineligible (INDEX)
  714                not at head of resource list.
  715 
  716 
  717      Stream:   as (severity2)
  718 
  719      Time:     While system is running.
  720 
  721      Meaning:  The  current  absentee  request,  which  would  be
  722                deferred by  load control, is  not at the  head of
  723                the  absentee list.   If this  occurs, there  is a
  724                logic error in absentee_utility_.
  725 
  726      Action:   Contact the system programming staff.
  727 
  728 
  729                [absentee_utility_.pl1]
  730                absentee_utility_:  Entry not found.  Creating new
  731                >sc1>absentee_data
  732 
  733 
  734      Stream:   as (severity1)
  735 
  736      Time:     During startup of the absentee facility.
  737 
  738      Meaning:  The  absentee data segment  was missing and  a new
  739                one has been created.
  740 
  741      Action:   Note for system programmer action.
  742 
  743 
  744                [absentee_utility_.pl1]
  745                absentee_utility_:  Entry not found.  Creating new
  746                >sc1>absentee_N.ms
  747 
  748 
  749      Stream:   as (severity1)
  750 
  751      Time:     During startup of the absentee facility.
  752 
  753      Meaning:  The  absentee  message  segment  for  queue  N was
  754                missing,  and a  new  one  has been  created.  Any
  755                previously submitted absentee jobs  in queue N are
  756                not executed.
  757 
  758      Action:   If  the  absentee  queues  never  existed  or were
  759                deliberately  deleted  or  removed,  this  message
  760                should be ignored.  Otherwise, it may be necessary
  761                to inform  users via the  message of the  day that
  762                the  absentee  requests  for  queue  N  were lost.
  763                Contact the  system programming staff for  help in
  764                recovering the queue.
  765 
  766 
  767 
  768 absentee_utility_               14            08/03/23     MR12.7^L
  769 
  770 
  771 
  772 
  773                [absentee_utility_.pl1]
  774                absentee_utility_:   ERROR_MESSAGE Dropping  queue
  775                >sc1>absentee_N.ms due to M consecutive errors
  776 
  777 
  778      Stream:   as (severity2)
  779 
  780      Time:     While system is running.
  781 
  782      Meaning:  This  message is printed  when a series  of errors
  783                prevents the  absentee facility from  reading jobs
  784                from a given queue.   Absentee requests in queue N
  785                are ignored until the absentee facility is stopped
  786                and restarted, or the command abs start queue N is
  787                used to restart the dropped queue.
  788 
  789      Action:   Note for system programmer action.
  790 
  791 
  792                [absentee_utility_.pl1]
  793                absentee_utility_:     ERROR_MESSAGE    Truncating
  794                absentee_data.
  795 
  796 
  797      Stream:   as (severity2)
  798 
  799      Time:     While system is running.
  800 
  801      Meaning:  An error  occurred during the attempt  to truncate
  802                absentee_data prior to rebuilding it.  It will not
  803                be possible to rebuild it.
  804 
  805      Action:   Contact the system programming staff.
  806 
  807 
  808                [absentee_utility_.pl1]
  809                absentee_utility_:    ERROR_MESSAGE.    Error   in
  810                creating defer event channel
  811 
  812 
  813      Stream:   as (severity2)
  814 
  815      Time:     During startup of the absentee facility.
  816 
  817      Meaning:  The  event  channel  used  in  processing absentee
  818                requests  that  are  deferred  until  a later time
  819                cannot  be  created.   No  deferred  requests  are
  820                activated.
  821 
  822      Action:   Issue  an  abs  stop  command  and  wait until all
  823                absentees run  to completion.  Then, issue  an abs
  824 
  825 
  826 absentee_utility_               15            08/03/23     MR12.7^L
  827 
  828 
  829                start  command.   If  this  same  message  recurs,
  830                contact the system programming staff.
  831 
  832 
  833 
  834                [absentee_utility_.pl1]
  835                absentee_utility_:    ERROR_MESSAGE.   Unable   to
  836                create >sc1>absentee_data
  837 
  838 
  839      Stream:   as (severity2)
  840 
  841      Time:     During startup of the absentee facility.
  842 
  843      Meaning:  The  absentee data  segment could  not be created.
  844                Faults  will   probably  occur  in   the  absentee
  845                facility  if the  system attempts  to run absentee
  846                jobs.
  847 
  848      Action:   Notify  the  system  programming  staff.   Do  _^Hn_^Ho_^Ht
  849                attempt to run absentee jobs.
  850 
  851 
  852 
  853                [absentee_utility_.pl1]
  854                absentee_utility_:    ERROR_MESSAGE.   Unable   to
  855                create >sc1>absentee_N.ms
  856 
  857 
  858      Stream:   as (severity1)
  859 
  860      Time:     During startup of the absentee facility.
  861 
  862      Meaning:  The absentee message segment for queue N cannot be
  863                created.  Users cannot queue  jobs in queue N, and
  864                jobs in queue N cannot be executed.
  865 
  866      Action:   Contact the system programming staff.
  867 
  868 
  869                [absentee_utility_.pl1]
  870                absentee_utility_:  ERROR_MESSAGE.  Unable to open
  871                new >sc1>absentee_N.ms
  872 
  873 
  874      Stream:   as (severity1)
  875 
  876      Time:     During startup of the absentee facility.
  877 
  878      Meaning:  The  absentee  message  segment  for  queue N just
  879                created  cannot be  found.  No  absentee jobs  are
  880                run.
  881 
  882 
  883 
  884 absentee_utility_               16            08/03/23     MR12.7^L
  885 
  886 
  887      Action:   Contact the system programming staff.
  888 
  889 
  890                [absentee_utility_.pl1]
  891                absentee_utility_:  ERROR_MESSAGE.   Unable to set
  892                access on >sc1>absentee_data
  893 
  894 
  895      Stream:   as (severity1)
  896 
  897      Time:     During startup of the absentee facility.
  898 
  899      Meaning:  The newly-created segment  absentee_data cannot be
  900                given correct access.   The system should continue
  901                to run.
  902 
  903      Action:   Note for system programmer action.
  904 
  905 
  906                [absentee_utility_.pl1]
  907                absentee_utility_:    ERROR_MESSAGE.   Unable   to
  908                terminate >sc1>absentee_data
  909 
  910 
  911      Stream:   as (severity1)
  912 
  913      Time:     During shutdown of the absentee facility.
  914 
  915      Meaning:  While  shutting down   the absentee  facility, the
  916                system   attempted   to   terminate   the  segment
  917                absentee_data   and  received   an  error.    This
  918                condition is not serious.
  919 
  920      Action:   Note for system programmer action.
  921 
  922 
  923                [absentee_utility_.pl1]
  924                absentee_utility_:  ERROR_MESSAGE.   Attempting to
  925                cancel reservation REQUEST for USER (ABSENTEE)
  926 
  927 
  928      Stream:   Logged in SYSERR log.
  929 
  930      Time:     While system is running.
  931 
  932      Meaning:  An   error  occurred   while  cancelling   an  RCP
  933                reservation for an absentee being deferred.
  934 
  935      Action:   No operator action is required.
  936 
  937 
  938                [absentee_utility_.pl1]
  939 
  940 
  941 
  942 absentee_utility_               17            08/03/23     MR12.7^L
  943 
  944 
  945                absentee_utility_:      ERROR_MESSAGE.     Closing
  946                >sc1>absentee_N.ms
  947 
  948 
  949      Stream:   as (severity1)
  950 
  951      Time:     While shutting down the absentee facility.
  952 
  953      Meaning:  A  storage system  error occurred  as part  of the
  954                processing  of  "abs  stop"  while  attempting  to
  955                terminate the  absentee message segment  for queue
  956                N.   Absentee requests for  queue N may  have been
  957                lost.
  958 
  959      Action:   If  you are  shutting down  the absentee  facility
  960                because  of some  previous message-segment  error,
  961                contact  the system  programming staff  and do not
  962                try  to restart  the absentee  facility.  If  this
  963                absentee  shutdown is   a normally  scheduled one,
  964                notify the  system programmers of the  message and
  965                do not try to  restart the absentee facility again
  966                until they have looked at the problem.
  967 
  968 
  969 
  970                [absentee_utility_.pl1]
  971                absentee_utility_:    ERROR_MESSAGE.     queue   N
  972                >sc1>absentee_N.ms
  973 
  974 
  975      Stream:   as (severity1)
  976 
  977      Time:     While system is running.
  978 
  979      Meaning:  An  error occurred   while reading,  rewriting, or
  980                deleting  a request from  queue N.  An  attempt is
  981                made to correct the error and retry the operation.
  982                Additional  messages are  printed if  this attempt
  983                fails.
  984 
  985      Action:   Contact the system programming staff.
  986 
  987 
  988                [absentee_utility_.pl1]
  989                absentee_utility_:     ERROR_MESSAGE.    Searching
  990                queue QUEUE skip list for USER (ABSENTEE)
  991 
  992 
  993      Stream:   Logged in SYSERR log.
  994 
  995      Time:     While system is running.
  996 
  997 
  998 
  999 
 1000 absentee_utility_               18            08/03/23     MR12.7^L
 1001 
 1002 
 1003      Meaning:  An  error occurred  while searching  the skip list
 1004                for an absentee request.
 1005 
 1006      Action:   No operator action is required.
 1007 
 1008 
 1009                [absentee_utility_.pl1]
 1010                absentee_utility_:  ERROR_MESSAGE.  Searching skip
 1011                list for USER (ABSENTEE)
 1012 
 1013 
 1014      Stream:   Logged in SYSERR log.
 1015 
 1016      Time:     While system is running.
 1017 
 1018      Meaning:  An  error occurred  while searching  the skip list
 1019                for an absentee request.
 1020 
 1021      Action:   No operator action is required.
 1022 
 1023 
 1024                [absentee_utility_.pl1]
 1025                absentee_utility_:   ERROR_MESSAGE.  Sending  TYPE
 1026                wakeup to PROCID (ABS-EVENT)
 1027 
 1028 
 1029      Stream:   Logged in SYSERR log.
 1030 
 1031      Time:     While system is running.
 1032 
 1033      Meaning:  An  error occurred  while sending  an "aum_ctl" or
 1034                "login" wakeup to the specified absentee process.
 1035 
 1036      Action:   No operator action is required.
 1037 
 1038 
 1039                [absentee_utility_.pl1]
 1040                absentee_utility_:    ERROR_MESSAGE.   Unable   to
 1041                delete request for USER (ABSENTEE); queue:  QUEUE;
 1042                index:  QUEUE_INDEX
 1043 
 1044 
 1045      Stream:   as (severity0)
 1046 
 1047      Time:     While system is running.
 1048 
 1049      Meaning:  An  error occurred  while deleting  a request from
 1050                the absentee queue.
 1051 
 1052      Action:   No operator action is required.
 1053 
 1054 
 1055                [absentee_utility_.pl1]
 1056 
 1057 
 1058 absentee_utility_               19            08/03/23     MR12.7^L
 1059 
 1060 
 1061                absentee_utility_:    ERROR_MESSAGE.   Unable   to
 1062                notify user USER of absentee event.
 1063 
 1064 
 1065      Stream:   Logged in SYSERR log.
 1066 
 1067      Time:     While system is running.
 1068 
 1069      Meaning:  An error occurred while  sending a message to USER
 1070                as notification of an absentee event.
 1071 
 1072 
 1073 
 1074                [absentee_utility_.pl1]
 1075                absentee_utility_:  ERROR_MESSAGE.   Unable to set
 1076                extended access on >sc1>absentee_N.ms
 1077 
 1078 
 1079      Stream:   as (severity1)
 1080 
 1081      Time:     During startup of the absentee facility.
 1082 
 1083      Meaning:  The  absentee  message  segment  for  queue N just
 1084                created cannot be set up  so that users can access
 1085                it  properly.  Users  will not  be able  to submit
 1086                absentee requests.
 1087 
 1088      Action:   Contact the system programming staff.
 1089 
 1090 
 1091                [absentee_utility_.pl1]
 1092                absentee_utility_:  ERROR_MESSAGE.   While reading
 1093                message  MESSAGE   from  USER  (ABSENTEE)   to  be
 1094                rewritten.
 1095 
 1096 
 1097      Stream:   Logged in SYSERR log.
 1098 
 1099      Time:     While system is running.
 1100 
 1101      Meaning:  An error occurred while reading a request from the
 1102                absentee queue.
 1103 
 1104      Action:   No operator action is required.
 1105 
 1106 
 1107                [absentee_utility_.pl1]
 1108                absentee_utility_:  ERROR_MESSAGE.   While reading
 1109                message MESSAGE to be rewritten.
 1110 
 1111 
 1112      Stream:   Logged in SYSERR log.
 1113 
 1114 
 1115 
 1116 absentee_utility_               20            08/03/23     MR12.7^L
 1117 
 1118 
 1119      Time:     While system is running.
 1120 
 1121      Meaning:  An  error  occurred   while  reading  an  absentee
 1122                request to be marked as "running".
 1123 
 1124      Action:   No operator action is required.
 1125 
 1126 
 1127                [absentee_utility_.pl1]
 1128                absentee_utility_:   Illegal  proxy  for NAME.PROJ
 1129                from NAME1.PROJ1 for job JJJJ
 1130 
 1131 
 1132      Stream:   as (severity1)
 1133 
 1134      Time:     While system is running.
 1135 
 1136      Meaning:  This message is printed  whenever a proxy absentee
 1137                job is  submitted by some user who  is not allowed
 1138                to submit a proxy.  User NAME1.PROJ1 submitted job
 1139                JJJJ to be run with the user ID NAME.PROJ, but the
 1140                absentee facility  will not do so  and ignores the
 1141                request.
 1142 
 1143      Action:   Note for system programmer action.
 1144 
 1145 
 1146                [absentee_utility_.pl1]
 1147                absentee_utility_:   Illegal queue  number (QUEUE)
 1148                for USER (ABSENTEE)
 1149 
 1150 
 1151      Stream:   as (severity0)
 1152 
 1153      Time:     While system is running.
 1154 
 1155      Meaning:  The queue number specified for the absentee job in
 1156                the absentee user table has an illegal value.
 1157 
 1158      Action:   No operator action is required.
 1159 
 1160 
 1161                [absentee_utility_.pl1]
 1162                absentee_utility_:   Loop in PROC,  searching NAME
 1163                list for queue N.
 1164 
 1165 
 1166      Stream:   as (severity1)
 1167 
 1168      Time:     While system is running.
 1169 
 1170      Meaning:  A software error has  damaged the list of requests
 1171                in absentee_data.   The error was detected  by the
 1172 
 1173 
 1174 absentee_utility_               21            08/03/23     MR12.7^L
 1175 
 1176 
 1177                internal procedure, PROC, while searching the NAME
 1178                list belonging  to queue N.  The  system makes one
 1179                attempt to rebuild  the list.  Additional messages
 1180                are printed if this attempt fails.
 1181 
 1182      Action:   Contact the system programming staff.
 1183 
 1184 
 1185                [absentee_utility_.pl1]
 1186                absentee_utility_:  Loop occurred while rebuilding
 1187                absentee_data after previous loop.
 1188 
 1189 
 1190      Stream:   as (severity2)
 1191 
 1192      Time:     While system is running.
 1193 
 1194      Meaning:  The  error   reported  by  the   previous  message
 1195                occurred  while  absentee_data  was  being rebuilt
 1196                following an  earlier error.  The  rebuild attempt
 1197                will not be repeated.
 1198 
 1199      Action:   Contact the system programming staff.
 1200 
 1201 
 1202                [absentee_utility_.pl1]
 1203                absentee_utility_:  rejected request  ID (PATH) in
 1204                queue N from PERS.PROJ:  REASON
 1205 
 1206 
 1207      Stream:   as (severity1)
 1208 
 1209      Time:     While system is running.
 1210 
 1211      Meaning:  This message is printed  if a message that appears
 1212                to be garbled or  meaningless is found in absentee
 1213                queue  N.  The  garbled message  is ignored.  This
 1214                condition  may be  evidence of  damage to absentee
 1215                queue N, unless REASON indicates otherwise.
 1216 
 1217      Action:   Note for system programmer action.
 1218 
 1219 
 1220                [absentee_utility_.pl1]
 1221                absentee_utility_:   Timer  rang  and  no deferred
 1222                request found.
 1223 
 1224 
 1225      Stream:   as (severity0)
 1226 
 1227      Time:     While system is running.
 1228 
 1229 
 1230 
 1231 
 1232 absentee_utility_               22            08/03/23     MR12.7^L
 1233 
 1234 
 1235      Meaning:  The  deferred  request  timer   went  off  and  no
 1236                deferred absentee jobs were found.
 1237 
 1238      Action:   No operator action is required.
 1239 
 1240 
 1241                [accept_fs_disk.pl1]
 1242                accept_fs_disk:   part NAME  on PVNAME  (dskX_NNS)
 1243                from AAA for BBB overlaps pages from CCC
 1244 
 1245 
 1246      Stream:   BOS Typewriter.
 1247 
 1248      Time:     When accepting a disk volume.
 1249 
 1250      Meaning:  The  supervisor checks  the partitions  defined in
 1251                the  volume  label  against  the  beginning of the
 1252                paging  partition when  it accepts  a volume.  The
 1253                partition  NAME  overlaps  the  paging  area.  The
 1254                volume label may have been damaged.
 1255 
 1256      Action:   Be  careful not  to destroy  the contents  of part
 1257                NAME, since this will destory the contents of user
 1258                segments.  Note for system programmer action.
 1259 
 1260 
 1261 
 1262                [accept_rpv.pl1]
 1263                accept_rpv:  Error ERRORMESSAGE accepting RPV
 1264 
 1265 
 1266      Stream:   BOS Typewriter (Crashes system)
 1267 
 1268      Time:     System Intialization.
 1269 
 1270      Meaning:  Some problem was encountered  trying to set up the
 1271                use  of the  RPV for  normal segment  creation and
 1272                activation.   The label of  the RPV may  have been
 1273                damaged, or encountered  disk errors, as indicated
 1274                by the ERRORMESSAGE.
 1275 
 1276      Action:   Make  sure that  the RPV  label area  (first eight
 1277                records), or a dump of it, is available for system
 1278                programmer inspection.  Note for system programmer
 1279                action.
 1280 
 1281                Message:  accept_rpv:  HC part on dskX_NN used XXX
 1282                out of YYY records.
 1283 
 1284      Stream:   This message is printed on  the console if an HCPT
 1285                card  is in  the  config  deck.  Otherwise,  it is
 1286                logged into the syserr_log.
 1287 
 1288 
 1289 
 1290 accept_rpv                      23            08/03/23     MR12.7^L
 1291 
 1292 
 1293      Time:     System Intialization.
 1294 
 1295      Meaning:  The  message appears  for each  disk volume  which
 1296                contains  a  Hardcore  Partition  (PART  HC).   It
 1297                indicates  how  many  records  were  actually used
 1298                (XXX) in the partition, which had size YYY.
 1299 
 1300      Action:   No operator action is required.
 1301 
 1302 
 1303                [accept_rpv.pl1]
 1304                accept_rpv:  pv PVNAME lv  LVNAME (DSKX_NN) is not
 1305                part of root.
 1306 
 1307 
 1308      Stream:   BOS Typewriter (Crashes system)
 1309 
 1310      Time:     System Intialization.
 1311 
 1312      Meaning:  The pack on the drive DSKX_NN, with pv name and lv
 1313                name as  read from its label, is  specified on the
 1314                ROOT  CONFIG card,  but is  not part  of the  same
 1315                logical volume as the RPV.
 1316 
 1317      Action:   Check the ROOT CONFIG  card for errors.  Check for
 1318                the proper packs.  Reboot the system.
 1319 
 1320 
 1321 
 1322                [access_audit_.pl1]
 1323                access_audit_$ENTRY:    (USER_ID)    Called   with
 1324                insufficient      arguments     (#args=      ^d).(
 1325                Caller=""CALLING_PROC".)
 1326 
 1327 
 1328      Stream:   BOS Typewriter.
 1329 
 1330      Time:     While system is running.
 1331 
 1332      Meaning:  This indicates a logic error in the supervisor, or
 1333                CPU  or memory  hardware problems.   access_audit_
 1334                was  invoked with   an improper  calling sequence.
 1335                There  may have  been enough  arguments to display
 1336                the offending caller name.
 1337 
 1338      Action:   Contact the system programming staff.
 1339 
 1340 
 1341                [access_audit_.pl1]
 1342                access_audit_$ENTRY:      (USER_ID)    Encountered
 1343                illegal   meter    index.    OperCode=XXXXXXXXXXXX
 1344                EventFlags=YYYYYYYYYYYY.( Caller="CALLING_PROC".)
 1345 
 1346 
 1347 
 1348 access_audit_$ENTRY             24            08/03/23     MR12.7^L
 1349 
 1350 
 1351      Stream:   Logged in SYSERR log.
 1352 
 1353      Time:     While system is running.
 1354 
 1355      Meaning:  This indicates a logic error in the supervisor, or
 1356                CPU or memory hardware problems.  The access audit
 1357                meters  in  active_hardcore_data  are inconsistant
 1358                with the format of the process access flags or the
 1359                supplied operation code and/or event flags.
 1360 
 1361      Action:   Contact the system programming staff.
 1362 
 1363 
 1364                [access_audit_.pl1]
 1365                access_audit_$ENTRY:      (USER_ID)    Encountered
 1366                illegal           parameter           combination.
 1367                OperCode=XXXXXXXXXXXX    EventFlags=YYYYYYYYYYYY.(
 1368                Caller="CALLING_PROC".)
 1369 
 1370 
 1371      Stream:   BOS Typewriter.
 1372 
 1373      Time:     While system is running.
 1374 
 1375      Meaning:  This indicates a logic error in the supervisor, or
 1376                CPU  or  memory  hardware  problems.   There is an
 1377                error  in  the  access_operations_  entry  or  the
 1378                eventflags passed to access  audit.  The error was
 1379                detected  in the  code which  decides whether  the
 1380                caller needs  to audit its event.   Because of the
 1381                error, the event will be audited regardless of the
 1382                process audit flags.
 1383 
 1384      Action:   Contact the system programming staff.
 1385 
 1386 
 1387                [access_audit_.pl1]
 1388                access_audit_$ENTRY:   (USER_ID) Improper  calling
 1389                sequence   (from   "get_entry_pointer_and_class").
 1390                Caller="CALLING_PROC".
 1391 
 1392 
 1393      Stream:   BOS Typewriter.
 1394 
 1395      Time:     While system is running.
 1396 
 1397      Meaning:  This indicates a logic error in the supervisor, or
 1398                CPU  or memory  hardware problems.   The entry was
 1399                called  with  an  improper  argument  combination.
 1400                Most    likely   the     entry   will    be   (log
 1401                check)_obj_ptr_(user)  and  the  obj_ptr  supplied
 1402                will be null.
 1403 
 1404 
 1405 
 1406 access_audit_$ENTRY             25            08/03/23     MR12.7^L
 1407 
 1408 
 1409      Action:   Contact the system programming staff.
 1410 
 1411 
 1412                [access_audit_.pl1]
 1413                access_audit_$ENTRY:  (USER_ID) Unable to generate
 1414                path   for  entry   at  PTR   due  to   "MESSAGE".
 1415                Caller="CALLING_PROC".
 1416 
 1417 
 1418      Stream:   Logged in SYSERR log.
 1419 
 1420      Time:     While system is running.
 1421 
 1422      Meaning:  This indicates a logic error in the supervisor, or
 1423                CPU  or  memory  hardware  problems.   A  call  to
 1424                get_pathname_ returned an unexpected error code.
 1425 
 1426      Action:   Contact the system programming staff.
 1427 
 1428 
 1429                [access_audit_.pl1]
 1430                access_audit_$ENTRY:   (USER_ID)   Unable  to  get
 1431                entry  pointer   for  seg  [#N  |   PATH]  due  to
 1432                "MESSAGE".
 1433 
 1434 
 1435      Stream:   Logged in SYSERR log.
 1436 
 1437      Time:     While system is running.
 1438 
 1439      Meaning:  This indicates a logic error in the supervisor, or
 1440                CPU  or  memory  hardware  problems.   A  call  to
 1441                sum$getbranch_root_my   or   dc_find$obj_for_audit
 1442                returned an unexpected error code.
 1443 
 1444      Action:   Contact the system programming staff.
 1445 
 1446 
 1447                [access_audit_.pl1]
 1448                access_audit_$ENTRY:  (USER_ID) Unable  to get raw
 1449                access  modes  for  entry  PTR  due  to "MESSAGE".
 1450                Caller="CALLER_PROC".
 1451 
 1452 
 1453      Stream:   Logged in SYSERR log.
 1454 
 1455      Time:     While system is running.
 1456 
 1457      Meaning:  This indicates a logic error in the supervisor, or
 1458                CPU  or memory   hardware problems.   Although the
 1459                directory   is  locked   a  failure   occurred  in
 1460                access_mode$raw.
 1461 
 1462 
 1463 
 1464 access_audit_$ENTRY             26            08/03/23     MR12.7^L
 1465 
 1466 
 1467      Action:   Contact the system programming staff.
 1468 
 1469 
 1470                [access_audit_.pl1]
 1471                access_audit_$ENTRY:  (USER_ID) Unable  to get UID
 1472                path  for  directory  seg  #N  due  to  "MESSAGE".
 1473                Caller="CALLER_PROC".
 1474 
 1475 
 1476      Stream:   Logged in SYSERR log.
 1477 
 1478      Time:     While system is running.
 1479 
 1480      Meaning:  This indicates a logic error in the supervisor, or
 1481                CPU  or memory   hardware problems.   Although the
 1482                directory  is   locked,  a  failure   occurred  in
 1483                uid_path_util$get.
 1484 
 1485      Action:   Contact the system programming staff.
 1486 
 1487 
 1488                [access_audit_.pl1]
 1489                access_audit_$ENTRY:   (USER_ID) Unexpected  error
 1490                obtaining        caller       text        pointer.
 1491                Caller="CALLING_PROC".
 1492 
 1493 
 1494      Stream:   BOS Typewriter.
 1495 
 1496      Time:     While system is running.
 1497 
 1498      Meaning:  This indicates a logic error in the supervisor, or
 1499                CPU or memory hardware  problems.  An error exists
 1500                in the calling sequence to access_audit_.
 1501 
 1502      Action:   Contact the system programming staff.
 1503 
 1504 
 1505                [access_audit_.pl1]
 1506                access_audit_$UNKNOWN:       (USER_ID)     Illegal
 1507                entrypoint      index     "N"      detected     in
 1508                form_audit_message_text.  Caller="CALLING_PROC".
 1509 
 1510 
 1511      Stream:   BOS Typewriter.
 1512 
 1513      Time:     While system is running.
 1514 
 1515      Meaning:  This indicates a logic error in the supervisor, or
 1516                CPU  or  memory  hardware  problems.   There  is a
 1517                coding error in access_audit_ where the entrypoint
 1518                index  is  uninitialized  or  set  to an incorrect
 1519                value.
 1520 
 1521 
 1522 access_audit_$UNKNOWN           27            08/03/23     MR12.7^L
 1523 
 1524 
 1525      Action:   Contact the system programming staff.
 1526 
 1527 
 1528                [access_audit_.pl1]
 1529                access_audit_:   Insufficient   room  to  allocate
 1530                [ssobj|link] data.
 1531 
 1532 
 1533      Stream:   BOS Typewriter.
 1534 
 1535      Time:     While system is running.
 1536 
 1537      Meaning:  This indicates a logic error in the supervisor, or
 1538                CPU  or memory   hardware problems.   An automatic
 1539                data area  is too small to  accomodate the storage
 1540                system object or link binary info.
 1541 
 1542      Action:   Contact the system programming staff.
 1543 
 1544 
 1545                [access_audit_log_fault_.pl1]
 1546                access_audit_log_fault_:   (USER_ID Unable  to get
 1547                path of seg #N due to "MESSAGE".
 1548 
 1549 
 1550      Stream:   BOS Typewriter.
 1551 
 1552      Time:     While system is running.
 1553 
 1554      Meaning:  This indicates a logic error in the supervisor, or
 1555                CPU  or  memory  hardware  problems.   A  call  to
 1556                get_pathname_ returned an unexpected error code.
 1557 
 1558      Action:   Contact the system programming staff.
 1559 
 1560 
 1561                [access_audit_log_fault_.pl1]
 1562                access_audit_log_fault_:   (USER_ID)  Called  with
 1563                bad machine conditions.
 1564 
 1565 
 1566      Stream:   BOS Typewriter.
 1567 
 1568      Time:     While system is running.
 1569 
 1570      Meaning:  This indicates a logic error in the supervisor, or
 1571                CPU      or     memory      hardware     problems.
 1572                access_audit_log_fault_    was    given    machine
 1573                conditions  for  a  fault  which  was  neither  an
 1574                illegal_procedure or an access_violation.
 1575 
 1576      Action:   Contact the system programming staff.
 1577 
 1578 
 1579 
 1580 access_audit_log_fault_         28            08/03/23     MR12.7^L
 1581 
 1582 
 1583 
 1584 
 1585                [access_audit_log_fault_.pl1]
 1586                access_audit_log_fault_:    (USER_ID)  Encountered
 1587                illegal meter index value.
 1588 
 1589 
 1590      Stream:   BOS Typewriter.
 1591 
 1592      Time:     While system is running.
 1593 
 1594      Meaning:  This indicates a logic error in the supervisor, or
 1595                CPU or memory hardware problems.  The access audit
 1596                meters  in  active_hardcore_data  are inconsistant
 1597                with the format of the process access flags.
 1598 
 1599      Action:   Contact the system programming staff.
 1600 
 1601 
 1602                [access_audit_log_fault_.pl1]
 1603                access_audit_log_fault_:  (USER_ID)  Unable to get
 1604                access mode for data seg #N due to "MESSAGE".
 1605 
 1606 
 1607      Stream:   BOS Typewriter.
 1608 
 1609      Time:     While system is running.
 1610 
 1611      Meaning:  This indicates a logic error in the supervisor, or
 1612                CPU  or  memory  hardware  problems.   A  call  to
 1613                fs_modes  failed unexpectedly.  The  AUDIT message
 1614                text  will  show  the  modes  as  "???"   and ring
 1615                brackets  of  7,7,7.    The  message  binary  will
 1616                reflect  null  access  mode  and  ring  bracket of
 1617                7,7,7.
 1618 
 1619      Action:   Contact the system programming staff.
 1620 
 1621 
 1622                [access_audit_log_fault_.pl1]
 1623                access_audit_log_fault_:  (USER_ID)  Unable to get
 1624                entry pointer for seg #N due to "MESSAGE".
 1625 
 1626 
 1627      Stream:   BOS Typewriter.
 1628 
 1629      Time:     While system is running.
 1630 
 1631      Meaning:  This indicates a logic error in the supervisor, or
 1632                CPU  or  memory  hardware  problems.   A  call  to
 1633                sum$getbranch_root_my returned an unexpected error
 1634                code.
 1635 
 1636 
 1637 
 1638 access_audit_log_fault_         29            08/03/23     MR12.7^L
 1639 
 1640 
 1641      Action:   Contact the system programming staff.
 1642 
 1643 
 1644                [access_audit_log_fault_.pl1]
 1645                access_audit_log_fault_:  (USER_ID)  Unable to get
 1646                raw access modes for entry PTR due to "MESSAGE".
 1647 
 1648 
 1649      Stream:   BOS Typewriter.
 1650 
 1651      Time:     While system is running.
 1652 
 1653      Meaning:  This indicates a logic error in the supervisor, or
 1654                CPU  or memory   hardware problems.   Although the
 1655                directory   is  locked   a  failure   occurred  in
 1656                access_mode$raw.
 1657 
 1658      Action:   Contact the system programming staff.
 1659 
 1660 
 1661                [access_audit_log_fault_.pl1]
 1662                access_audit_log_fault_:  (USER_ID)  Unable to get
 1663                UID path for directory seg #N due to "MESSAGE".
 1664 
 1665 
 1666      Stream:   BOS Typewriter.
 1667 
 1668      Time:     While system is running.
 1669 
 1670      Meaning:  This indicates a logic error in the supervisor, or
 1671                CPU  or memory   hardware problems.   Although the
 1672                directory  is   locked,  a  failure   occurred  in
 1673                uid_path_util$get.
 1674 
 1675      Action:   Contact the system programming staff.
 1676 
 1677 
 1678                [access_audit_log_fault_.pl1]
 1679                access_audit_log_fault_:  Link  entry where branch
 1680                expected (ep=PTR).
 1681 
 1682 
 1683      Stream:   BOS Typewriter (Crashes system)
 1684 
 1685      Time:     While system is running.
 1686 
 1687      Meaning:  This indicates a logic error in the supervisor, or
 1688                CPU or memory hardware  problems.  After getting a
 1689                directory  entry for  a specific  segno the branch
 1690                switch in the entry was found to be off.
 1691 
 1692      Action:   Follow normal recovery procedures.
 1693 
 1694 
 1695 
 1696 access_viol                     30            08/03/23     MR12.7^L
 1697 
 1698 
 1699 
 1700 
 1701                [access_viol.pl1]
 1702                access_viol:  associative memory fault.
 1703 
 1704 
 1705      Stream:   BOS Typewriter (Crashes system)
 1706 
 1707      Time:     While system is running.
 1708 
 1709      Meaning:  The  processor associative  memory has  detected a
 1710                usage count error.
 1711 
 1712      Action:   Notify Field Engineering personnel.
 1713 
 1714 
 1715                [act_ctl_.pl1]
 1716                act_ctl_$dp:    Net   accounting   array   version
 1717                (VERSION_RETURNED)   not    supported.    Expected
 1718                version (VERSION_SUPPORTED)
 1719 
 1720 
 1721 
 1722      Stream:   as (severity2).
 1723 
 1724      Time:     While system is running.
 1725 
 1726      Meaning:  network_accounting_gate_$read_and_reset_table
 1727                returned a  structure version which  act_ctl_ does
 1728                not  support.This indicates  a logic  error in the
 1729                supervisor, or CPU or memory hardware problems.
 1730 
 1731      Action:   Contact the system programming staff._sm
 1732 
 1733 
 1734                [act_ctl_.pl1]
 1735                act_ctl_$init:             cannot           locate
 1736                Initializer.SysDaemon pdt entry
 1737 
 1738 
 1739      Stream:   as (severity2)
 1740 
 1741      Time:     System Intialization.
 1742 
 1743      Meaning:  The  accounting  system  requires  the  entry  for
 1744                Initializer in the project SysDaemon to be present
 1745                because certain  system metering figures  are kept
 1746                there.  This entry cannot be found, either because
 1747                SysDaemon.pdt  has  been   lost,  or  because  its
 1748                contents  have been   destroyed.  The  system will
 1749                probably  encounter a   simfault_xxx error  and be
 1750                unable to start up.
 1751 
 1752 
 1753 
 1754 act_ctl_$init                   31            08/03/23     MR12.7^L
 1755 
 1756 
 1757      Action:   Contact  the  system  programming  staff.   Do not
 1758                attempt to  run the system until  this problem has
 1759                been fixed.
 1760 
 1761 
 1762 
 1763                [act_ctl_.pl1]
 1764                act_ctl_$init:  ERROR_MESSAGE.   Cannot unlock PDT
 1765                PATHNAME.
 1766 
 1767 
 1768      Stream:   as (severity2)
 1769 
 1770      Time:     System Intialization.
 1771 
 1772      Meaning:  This  message  occurs   during  answering  service
 1773                initialization when attempting to unlock all PDTs.
 1774                ERROR_MESSAGE  specifies the   the reason  for the
 1775                problem.  The PDT is  skipped.  Later problems may
 1776                arise because of this error.
 1777 
 1778      Action:   Contact the system programming staff.
 1779 
 1780 
 1781                [act_ctl_.pl1]
 1782                act_ctl_$init:   ERROR_MESSAGE.   creating  update
 1783                channel
 1784 
 1785 
 1786      Stream:   as (severity2)
 1787 
 1788      Time:     System Intialization.
 1789 
 1790      Meaning:  The timer  channel that causes  accounting updates
 1791                to  be  performed  could   not  be  created.   All
 1792                accounting updates will be  manual, triggered by a
 1793                user logging out.
 1794 
 1795      Action:   Contact the system programming staff.
 1796 
 1797 
 1798                [act_ctl_.pl1]
 1799                act_ctl_$init:  illegal value  (DD) for accounting
 1800                update interval in installation_parms.
 1801 
 1802 
 1803      Stream:   as (severity2)
 1804 
 1805      Time:     System Intialization.
 1806 
 1807      Meaning:  The value  given in installation_parms.acct_update
 1808                is   less   than   or    equal   to   zero.    The
 1809                installation_parms file is probabily damaged.
 1810 
 1811 
 1812 act_ctl_$init                   32            08/03/23     MR12.7^L
 1813 
 1814 
 1815      Action:   Contact  the  system  programming  staff.   Do not
 1816                attempt to  run the system until  this problem has
 1817                been fixed.
 1818 
 1819 
 1820 
 1821                [act_ctl_.pl1]
 1822                act_ctl_$init:  The PDT is damaged.  Cannot unlock
 1823                PATHNAME.
 1824 
 1825 
 1826      Stream:   as (severity2)
 1827 
 1828      Time:     System Intialization.
 1829 
 1830      Meaning:  This  message  occurs   during  answering  service
 1831                initialization when attempting to unlock all PDTs.
 1832                The  specified PDT  had its  damaged switch turned
 1833                on.  Because of this, it was not unlocked from the
 1834                previous bootload.  It is skipped.  Later problems
 1835                may  arise when  an attempt  is made  to reference
 1836                this PDT.
 1837 
 1838      Action:   Contact the system programming staff.
 1839 
 1840 
 1841                [act_ctl_.pl1]
 1842                act_ctl_$update:  Error from ROUTINE:  MESSAGE
 1843 
 1844 
 1845      Stream:   as (severity2).
 1846 
 1847      Time:     While system is running.
 1848 
 1849      Meaning:  The system encountered  problems while referencing
 1850                the         network_accounting_table.          The
 1851                network_accounting_   ROUTINE  being   called  and
 1852                MESSAGE text further describe the error.
 1853 
 1854      Action:   Contact the system programming staff.
 1855 
 1856 
 1857                [act_ctl_.pl1]
 1858                act_ctl_$update:   Net  accounting  array  version
 1859                (VERSION_RETURNED)   not    supported.    Expected
 1860                version (VERSION_SUPPORTED)
 1861 
 1862 
 1863 
 1864      Stream:   as (severity2).
 1865 
 1866      Time:     While system is running.
 1867 
 1868 
 1869 
 1870 act_ctl_$update                 33            08/03/23     MR12.7^L
 1871 
 1872 
 1873      Meaning:  network_accounting_gate_$read_and_reset_table
 1874                returned a  structure version which  act_ctl_ does
 1875                not  support.This indicates  a logic  error in the
 1876                supervisor, or CPU or memory hardware problems.
 1877 
 1878      Action:   Contact the system programming staff._sm
 1879 
 1880 
 1881                [act_ctl_.pl1]
 1882                act_ctl_$update:  Processid XXXXXXXX missing.  Not
 1883                charged  for  XX  pkt,  YY  byte  and  ZZ seconds;
 1884                was/was not purged.
 1885 
 1886 
 1887 
 1888      Stream:   as (severity2)
 1889 
 1890      Time:     While system is running.
 1891 
 1892      Meaning:  After  charging network  accounting usage  for all
 1893                users  on  the  system,  an  entry  was  found for
 1894                processid XXXXXXXX.  The XX,  YY and ZZ are counts
 1895                of the usage which the  process had.  If the entry
 1896                was for  a process which  is no longer  logged in,
 1897                the accounting record was  purged from the network
 1898                accounting file.
 1899 
 1900      Action:   Note for system programmer action.
 1901 
 1902 
 1903                [act_ctl_.pl1]
 1904                act_ctl_:  accounting disabled
 1905 
 1906 
 1907      Stream:   as (severity1)
 1908 
 1909      Time:     May occur at any time.
 1910 
 1911      Meaning:  The accounting system has  been disabled by a call
 1912                to act_ctl_$act_ctl_disable.
 1913 
 1914      Action:   No operator action is required.
 1915 
 1916 
 1917                [act_ctl_.pl1]
 1918                act_ctl_:  accounting enabled.
 1919 
 1920 
 1921      Stream:   as (severity1)
 1922 
 1923      Time:     May occur at any time.
 1924 
 1925 
 1926 
 1927 
 1928 act_ctl_                        34            08/03/23     MR12.7^L
 1929 
 1930 
 1931      Meaning:  The accounting  system has been  enabled, probably
 1932                after   a   special   session,   by   a   call  to
 1933                act_ctl_$act_ctl_reable.
 1934 
 1935      Action:   No operator action is required.
 1936 
 1937 
 1938                [act_ctl_.pl1]
 1939                act_ctl_:   alarm clock  late or  failing by XX.XX
 1940                mins
 1941 
 1942 
 1943      Stream:   as (severity1)
 1944 
 1945      Time:     While system is running.
 1946 
 1947      Meaning:  The  alarm   clock  channel  has  not   caused  an
 1948                accounting update to be performed when it was due.
 1949                (The time between updates is stored in the segment
 1950                installation_parms.)  The system performs a manual
 1951                accounting update.  This message may appear if the
 1952                system has entered BOS,  and Multics has then been
 1953                restarted  by the GO  command.  In such  case, the
 1954                message can be ignored.
 1955 
 1956      Action:   Note for system programmer action.
 1957 
 1958 
 1959                [act_ctl_.pl1]
 1960                act_ctl_:  bumping absNN  NAME.PROJ - inactive too
 1961                long
 1962 
 1963 
 1964      Stream:   as (severity1)
 1965 
 1966      Time:     While system is running.
 1967 
 1968      Meaning:  The  absentee job  on  absentee  slot NN  for user
 1969                NAME.PROJ  has remained   blocked too  long.  (The
 1970                inactive  time  limit  is  stored  in  the segment
 1971                installation_parms.)  The absentee job is bumped.
 1972 
 1973      Action:   No operator action is required.
 1974 
 1975 
 1976                [act_ctl_.pl1]
 1977                act_ctl_:  bumping absXX NAME.PROJ - too much time
 1978 
 1979 
 1980      Stream:   as (severity1)
 1981 
 1982      Time:     While system is running.
 1983 
 1984 
 1985 
 1986 act_ctl_                        35            08/03/23     MR12.7^L
 1987 
 1988 
 1989      Meaning:  The absentee job on absentee  slot XX for the user
 1990                NAME.PROJ has exceeded the  CPU time limit for the
 1991                queue.   (This  limit  is  stored  in  the segment
 1992                installation_parms.)  The absentee job is bumped.
 1993 
 1994      Action:   No operator action is required.
 1995 
 1996 
 1997                [act_ctl_.pl1]
 1998                act_ctl_:  bumping NAME.PROJ for inactivity
 1999 
 2000 
 2001      Stream:   as (severity1)
 2002 
 2003      Time:     While system is running.
 2004 
 2005      Meaning:  The user with name NAME  and project PROJ has been
 2006                inactive too  long, and is bumped  off the system.
 2007                The maximum inactive time is stored in the segment
 2008                installation_parms.
 2009 
 2010      Action:   No operator action is required.
 2011 
 2012 
 2013                [act_ctl_.pl1]
 2014                act_ctl_:  bumping NAME.PROJ.  REASON
 2015 
 2016 
 2017      Stream:   as (severity1)
 2018 
 2019      Time:     While system is running.
 2020 
 2021      Meaning:  The user with name NAME  and project PROJ has been
 2022                bumped  because  some   per-user  limit  has  been
 2023                exceeded.  REASON tells what was wrong; it will be
 2024                a  message such  as "User  resource limit  of $100
 2025                monthly exceeded,"  depending on which  user limit
 2026                has been exceeded.
 2027 
 2028      Action:   No operator action is required.
 2029 
 2030 
 2031                [act_ctl_.pl1]
 2032                act_ctl_:  changing shift from x to y
 2033 
 2034 
 2035      Stream:   as (severity1)
 2036 
 2037      Time:     While system is running.
 2038 
 2039      Meaning:  The  current accounting   shift has  changed.  The
 2040                table that tells the beginning time for each shift
 2041                is stored in the segment installation_parms.
 2042 
 2043 
 2044 act_ctl_                        36            08/03/23     MR12.7^L
 2045 
 2046 
 2047      Action:   No operator action is required.
 2048 
 2049 
 2050                [act_ctl_.pl1]
 2051                act_ctl_:  charged X, available Y mins
 2052 
 2053 
 2054      Stream:   as (severity0)
 2055 
 2056      Time:     While system is running.
 2057 
 2058      Meaning:  X is  the sum of  virtual CPU time  charged to all
 2059                processes and Y is the total virtual CPU time used
 2060                by  all  processes.   This  message  logs detailed
 2061                accounting  information and  appears whenever  the
 2062                message  "act_ctl_:   discrepancy  of  XX.XX mins"
 2063                appears.
 2064 
 2065      Action:   No operator action is required.
 2066 
 2067 
 2068                [act_ctl_.pl1]
 2069                act_ctl_:  discrepancy of XX.XX mins
 2070 
 2071 
 2072      Stream:   as (severity1)
 2073 
 2074      Time:     While system is running.
 2075 
 2076      Meaning:  The total time available from traffic control does
 2077                not  agree with  the total  time charged  to users
 2078                plus  the  Initializer  time  plus  the idle time.
 2079                Some process has escaped being accounted for.
 2080 
 2081      Action:   Contact the system programming staff._sa
 2082 
 2083 
 2084                [act_ctl_.pl1]
 2085                act_ctl_:    Lock  wait   time  exceeded.    While
 2086                destroying proc for NAME.PROJ
 2087 
 2088 
 2089      Stream:   as (severity2)
 2090 
 2091      Time:     While system is running.
 2092 
 2093      Meaning:  The accounting  system was unable to  lock the PDT
 2094                entry for the user NAME in the project PROJ within
 2095                its  time limit  (usually five  minutes) This user
 2096                attempted  to log out  or destroy a  process.  The
 2097                entry  was   probably  locked  because   a  system
 2098                administrator or  daemon process locked  the entry
 2099                and then failed.  The system attempts to continue.
 2100 
 2101 
 2102 act_ctl_                        37            08/03/23     MR12.7^L
 2103 
 2104 
 2105      Action:   Contact the system programming staff._sa
 2106 
 2107 
 2108                [act_ctl_.pl1]
 2109                act_ctl_:   MODE  update:    users  =  NN,  pf=XX,
 2110                vcpu=YY.Y, rt=ZZ.Z MESSAGE
 2111 
 2112 
 2113      Stream:   as (severity1)
 2114 
 2115      Time:     While system is running.
 2116 
 2117      Meaning:  Periodically,  the  accounting  programs  read and
 2118                store the  CPU usage for each  user.  This message
 2119                is printed when the update completes.  MODE may be
 2120                'Automatic', in which case  the update occurred at
 2121                the normal system  parameter time; 'Manual', where
 2122                the  normal update  didn't occur;  or 'Shift Cmnd'
 2123                where the update occurred  due to a shift command.
 2124                XX  is   the  number  of  page   faults  taken  by
 2125                Initializer for  update.  YY.Y is the  virtual CPU
 2126                time taken by Initializer for update.  ZZ.Z is the
 2127                real  time   taken  by  Initializer   for  update.
 2128                MESSAGE  may  be  one  or  both  of  the following
 2129                strings:   'answer  table  locked'  or 'install(s)
 2130                pending'
 2131 
 2132      Action:   No  operator action  is required.   The number  of
 2133                seconds  between accounting   updates is  a system
 2134                parameter that  an installation may change;  it is
 2135                stored in the segment installation_parms.
 2136 
 2137 
 2138 
 2139                [act_ctl_.pl1]
 2140                act_ctl_:   process   XXXXXXXXXXXX  for  NAME.PROJ
 2141                vanished
 2142 
 2143 
 2144      Stream:   as (severity2)
 2145 
 2146      Time:     While system is running.
 2147 
 2148      Meaning:  Traffic control cannot locate a process for a user
 2149                who should have one  according to accounting.  The
 2150                system attempts to run  normally, but this user is
 2151                not charged.  An attempt is  made to bump the user
 2152                in  question.  This  may be  the first  indication
 2153                that  the  segment  >system_control_1>answer_table
 2154                has been damaged.
 2155 
 2156      Action:   Note for system programmer action.
 2157 
 2158 
 2159 
 2160 act_ctl_                        38            08/03/23     MR12.7^L
 2161 
 2162 
 2163 
 2164 
 2165                [act_ctl_.pl1]
 2166                act_ctl_:  shutdown,  NNN WW.WW XX.XX  YY.YY ZZ.ZZ
 2167                HH:MM:SS $DDD.DD
 2168 
 2169 
 2170      Stream:   as (severity1)
 2171 
 2172      Time:     System shutdown.
 2173 
 2174      Meaning:  A successful shutdown of the accounting portion of
 2175                the system has been accomplished.  NNN logins were
 2176                recorded,  for a  total usage  of HH:MM:SS  of CPU
 2177                time charged.   The other numbers are  of interest
 2178                to  system administrators and  programmers.  WW.WW
 2179                is the average queue  length, XX.XX is the average
 2180                eligible, YY.YY  is the thrashing index,  ZZ.ZZ is
 2181                the  average  response,  and  DDD.DD  is the total
 2182                dollar  charge since  startup.  A  shutdown of the
 2183                hardcore system follows this message.
 2184 
 2185      Action:   No operator action is required.
 2186 
 2187 
 2188                [act_ctl_.pl1]
 2189                act_ctl_:  STRING for  USER.PROJ is negative (NUM)
 2190                at logout; set it to zero.
 2191 
 2192 
 2193 
 2194      Stream:   as (severity2)
 2195 
 2196      Time:     While system is running.
 2197 
 2198      Meaning:  A counter value of STRING was decremented by 1 and
 2199                went negative.  It was  noticed when attempting to
 2200                log out USER on the  PROJ project.  This is a sign
 2201                of possible damage to the PROJ pdt.
 2202 
 2203      Action:   Note for system programmer action.
 2204 
 2205 
 2206                [act_proc.pl1]
 2207                act_proc:  from grab_aste ERRORMESSAGE
 2208 
 2209 
 2210      Stream:   BOS Typewriter (Crashes system)
 2211 
 2212      Time:     While system is running.
 2213 
 2214      Meaning:  In  attempting  to  create  a  process, the system
 2215                could not  force the PDS or  descriptor segment of
 2216 
 2217 
 2218 act_proc                        39            08/03/23     MR12.7^L
 2219 
 2220 
 2221                that  process  to  be  activated  and held active.
 2222                ERRORMESSAGE  is  an  error_table_  message.  This
 2223                indicates a logic error  in the supervisor, or CPU
 2224                or memory hardware problems.
 2225 
 2226      Action:   Follow normal recovery procedures.
 2227 
 2228 
 2229                [act_proc.pl1]
 2230                act_proc:   KST size   specified (SIZE)  less than
 2231                minimum (MIN_SIZE).  Creating process for GROUPID.
 2232 
 2233 
 2234 
 2235      Stream:   Logged in SYSERR log.
 2236 
 2237      Time:     While system is running.
 2238 
 2239      Meaning:  The     project    administrator     (or    system
 2240                administrator) for  user GROUPID set  the kst_size
 2241                parameter in  the PDT to SIZE, which  is less than
 2242                the  valid minimum  MIN_SIZE.  The  process is not
 2243                created.   Note that  a process  with MINIMUM  KST
 2244                size will probably not be of any use.  The minimum
 2245                useful KST size is on the order of MINIMUM + 50.
 2246 
 2247      Action:   Change the PMF/PDT.
 2248 
 2249 
 2250                [activate.pl1]
 2251                activate:  activating into father PPPP
 2252 
 2253 
 2254      Stream:   BOS Typewriter (Crashes system)
 2255 
 2256      Time:     While system is running.
 2257 
 2258      Meaning:  The  AST  entry  pointer  returned  by get_aste is
 2259                identical to the AST  entry pointer for the parent
 2260                of the segment being  activated.  This indicates a
 2261                logic  error in the  supervisor, or CPU  or memory
 2262                hardware   problems.    BOS   Typewriter  (Crashes
 2263                system)es
 2264 
 2265      Action:   Follow normal recovery procedures.
 2266 
 2267 
 2268                [activate.pl1]
 2269                activate:  error on (deciduous) (dir) NAME
 2270 
 2271 
 2272      Stream:   Logged in SYSERR log.
 2273 
 2274 
 2275 
 2276 activate                        40            08/03/23     MR12.7^L
 2277 
 2278 
 2279      Time:     While system is running.
 2280 
 2281      Meaning:  An attempt  has been made to  activate a deciduous
 2282                segment, or to activate a segment when the VTOCE's
 2283                directory  switch  did  not  match  the branch.  A
 2284                connection  failure   is  returned  to   the  user
 2285                process.  This  information is logged for  the use
 2286                of system programmers.
 2287 
 2288      Action:   No operator action is required.
 2289 
 2290 
 2291                [activate.pl1]
 2292                activate:  Setting damaged switch on NAME at VTOCX
 2293                (dskX_NN{s}).  Filemap damaged.
 2294 
 2295 
 2296      Stream:   Logged in SYSERR log.
 2297 
 2298      Time:     While system is running.
 2299 
 2300      Meaning:  The segment's File Map in the VTOCE had an invalid
 2301                checksum,  which indicates   likely damage  to the
 2302                File Map.   The segment is marked  as damaged.  It
 2303                is  possible that  there  is  other damage  on the
 2304                physical  volume  due  to  invalid  or reused disk
 2305                addresses.  The count of volume inconsistencies is
 2306                incremented by 1.
 2307 
 2308      Action:   Examine the VTOCE for damage using dump_vtoce.  If
 2309                other   damage  is    evident,  delete   it  using
 2310                hp_delete_vtoce  -clear and  recover the  segment.
 2311                Run  the  physical  volume  scavenger  as  soon as
 2312                possible to detect and correct other damage on the
 2313                physical volume.
 2314 
 2315 
 2316 
 2317                [obs_reconfigure.pl1]
 2318                addcpu:  Associative  memories not enabled  on CPU
 2319                X.
 2320 
 2321 
 2322      Stream:   Initializer process output.
 2323 
 2324      Time:     In response to an operator command.
 2325 
 2326      Meaning:  The SDWAM  and/or PTWAM on  CPU X is  not enabled.
 2327                CPU X was not added.
 2328 
 2329      Action:   Set the  appropriate associative memory  switch on
 2330                and try addcpu again.
 2331 
 2332 
 2333 
 2334 addcpu                          41            08/03/23     MR12.7^L
 2335 
 2336 
 2337 
 2338 
 2339                [obs_reconfigure.pl1]
 2340                addcpu:  CPU X is already online.
 2341 
 2342 
 2343      Stream:   Initializer process output.
 2344 
 2345      Time:     In response to an operator command.
 2346 
 2347      Meaning:  A  redundant  addcpu  X  command  was  issued.  No
 2348                action was taken.
 2349 
 2350      Action:   Enter a corrected command line.
 2351 
 2352 
 2353                [obs_reconfigure.pl1]
 2354                addcpu:  CPU X is not configured.
 2355 
 2356 
 2357      Stream:   Initializer process output.
 2358 
 2359      Time:     In response to an operator command.
 2360 
 2361      Meaning:  There   is  no   CPU  card   for  CPU   X  in  the
 2362                configuration deck.  The CPU cannot be added.
 2363 
 2364      Action:   If  the CPU name  was mistyped, enter  a corrected
 2365                command.   If the  configuration deck  omitted the
 2366                CPU  card,  that  CPU  cannot  be  added until the
 2367                system is shut down and the deck corrected.
 2368 
 2369 
 2370 
 2371                [obs_reconfigure.pl1]
 2372                addcpu:  CPU X is not enabled at MEM Y.
 2373 
 2374 
 2375      Stream:   Initializer process output.
 2376 
 2377      Time:     In response to an operator command.
 2378 
 2379      Meaning:  CPU  X cannot  be  added  because the  PORT ENABLE
 2380                switch at MEM Y does not enable it.
 2381 
 2382      Action:   Fix the switches and try addcpu again.
 2383 
 2384 
 2385                [obs_reconfigure.pl1]
 2386                addcpu:  CPU X is not in Multics mode.
 2387 
 2388 
 2389      Stream:   Initializer process output.
 2390 
 2391 
 2392 addcpu                          42            08/03/23     MR12.7^L
 2393 
 2394 
 2395      Time:     In response to an operator command.
 2396 
 2397      Meaning:  CPU X  cannot be added because its  mode switch is
 2398                wrong.
 2399 
 2400      Action:   Fix the switch and try again.
 2401 
 2402 
 2403                [obs_reconfigure.pl1]
 2404                addcpu:   Illegal command or  subroutine argument.
 2405                BLAH
 2406 
 2407 
 2408      Stream:   Initializer process output.
 2409 
 2410      Time:     In response to an operator command.
 2411 
 2412      Meaning:  Invalid input was typed.
 2413 
 2414      Action:   Enter a corrected command line.
 2415 
 2416 
 2417                [obs_reconfigure.pl1]
 2418                addcpu:  Lockup fault trying to start CPU X.
 2419 
 2420 
 2421      Stream:   Initializer process output.
 2422 
 2423      Time:     In response to an operator command.
 2424 
 2425      Meaning:  This happens  occasionally.  The reason for  it is
 2426                unknown.
 2427 
 2428      Action:   Try addcpu a few more times.
 2429 
 2430 
 2431                [obs_reconfigure.pl1]
 2432                addcpu:  No response from CPU X.
 2433 
 2434 
 2435      Stream:   Initializer process output.
 2436 
 2437      Time:     In response to an operator command.
 2438 
 2439      Meaning:  CPU X did not start  up when commanded.  It may be
 2440                malfunctioning or in STEP.
 2441 
 2442      Action:   Check  the switches.   If any  are wrong,  correct
 2443                them  and retry  addcpu.  Otherwise,  notify Field
 2444                Engineering.
 2445 
 2446 
 2447 
 2448 
 2449 
 2450 addcpu                          43            08/03/23     MR12.7^L
 2451 
 2452 
 2453 
 2454 
 2455                [obs_reconfigure.pl1]
 2456                addcpu:  Reconfiguration database is locked.
 2457 
 2458 
 2459      Stream:   Initializer process output.
 2460 
 2461      Time:     In response to an operator command.
 2462 
 2463      Meaning:  Another  process   is  performing  reconfiguration
 2464                currently, or  a fault during  reconfiguration has
 2465                left the reconfiguration tables locked.
 2466 
 2467      Action:   If  it  is  certain   that  no  other  process  is
 2468                reconfiguring,   and   that    the   fault   which
 2469                interrupted  reconfiguration has  been cured,  the
 2470                reconfigure$force_unlock  command may  be used  to
 2471                clear the lock at the direction of system staff.
 2472 
 2473 
 2474 
 2475                [obs_reconfigure.pl1]
 2476                addcpu:  Startup fault trying to start CPU X.
 2477 
 2478 
 2479      Stream:   Initializer process output.
 2480 
 2481      Time:     In response to an operator command.
 2482 
 2483      Meaning:  This happens sometimes.  Nobody knows why.
 2484 
 2485      Action:   Try again a few times.
 2486 
 2487 
 2488                [obs_reconfigure.pl1]
 2489                addcpu:  The  following switches on CPU  X are set
 2490                incorrectly:
 2491                Fault Base
 2492                Processor Number
 2493                Port Assignment MEM Y
 2494                Port Enable MEM Y
 2495                Interlace MEM Y
 2496                Size MEM Y
 2497                Half/Full MEM Y
 2498 
 2499 
 2500 
 2501      Stream:   Initializer process output.
 2502 
 2503      Time:     In response to an operator command.
 2504 
 2505      Meaning:  The listed switches are set incorrectly.
 2506 
 2507 
 2508 addcpu                          44            08/03/23     MR12.7^L
 2509 
 2510 
 2511      Action:   Correct the switches and try addcpu again.
 2512 
 2513 
 2514                [obs_reconfigure.pl1]
 2515                addcpu:  Trouble fault trying to start CPU X.
 2516 
 2517 
 2518      Stream:   Initializer process output.
 2519 
 2520      Time:     In response to an operator command.
 2521 
 2522      Meaning:  This happens sometimes.  Nobody knows why.
 2523 
 2524      Action:   Try again a few times.
 2525 
 2526 
 2527                [obs_reconfigure.pl1]
 2528                addcpu:  Wrong number of arguments supplied.
 2529 
 2530 
 2531      Stream:   Initializer process output.
 2532 
 2533      Time:     In response to an operator command.
 2534 
 2535      Meaning:  Invalid input was typed.
 2536 
 2537      Action:   Enter a corrected command line.
 2538 
 2539 
 2540                [obs_reconfigure.pl1]
 2541                Added frame XXX.
 2542 
 2543 
 2544      Stream:   Initializer process output.
 2545 
 2546      Time:     In response to an operator command.
 2547 
 2548      Meaning:  This is  the response to a  successful addmain XXX
 2549                command.
 2550 
 2551      Action:   No operator action is required.
 2552 
 2553 
 2554                [obs_reconfigure.pl1]
 2555                Added frames XXX thru YYY.
 2556 
 2557 
 2558      Stream:   Initializer process output.
 2559 
 2560      Time:     In response to an operator command.
 2561 
 2562      Meaning:  This is the response to a successful addmain XXX N
 2563                command.
 2564 
 2565 
 2566 Added                           45            08/03/23     MR12.7^L
 2567 
 2568 
 2569      Action:   No operator action is required.
 2570 
 2571 
 2572                [disk_table_.pl1]
 2573                added pv PVNAME to mounted lv LVNAME.
 2574 
 2575 
 2576      Stream:   Initializer process output.
 2577 
 2578      Time:     While system is running.
 2579 
 2580      Meaning:  An av command  was used to increase the  size of a
 2581                mounted volume.
 2582 
 2583      Action:   No operator action is required.
 2584 
 2585 
 2586                [obs_reconfigure.pl1]
 2587                Added SCU X and its memory.
 2588 
 2589 
 2590      Stream:   Initializer process output.
 2591 
 2592      Time:     In response to an operator command.
 2593 
 2594      Meaning:  This  is the  response  to  a successful  addmem X
 2595                command.
 2596 
 2597      Action:   No operator action is required.
 2598 
 2599 
 2600                [obs_reconfigure.pl1]
 2601                Added SCU's X and Y (interlaced) and their memory.
 2602 
 2603 
 2604      Stream:   Initializer process output.
 2605 
 2606      Time:     In response to an operator command.
 2607 
 2608      Meaning:  This  is the  response  to  a successful  addmem X
 2609                command  when SCU's  X and  Y have  their memories
 2610                interlaced.
 2611 
 2612      Action:   No operator action is required.
 2613 
 2614 
 2615                [obs_reconfigure.pl1]
 2616                addmain:  Illegal command  or subroutine argument.
 2617                BLAH
 2618 
 2619 
 2620      Stream:   Initializer process output.
 2621 
 2622 
 2623 
 2624 addmain                         46            08/03/23     MR12.7^L
 2625 
 2626 
 2627      Time:     In response to an operator command.
 2628 
 2629      Meaning:  Invalid input was typed.
 2630 
 2631      Action:   Enter a corrected command line.
 2632 
 2633 
 2634                [obs_reconfigure.pl1]
 2635                addmain:  Reconfiguration database is locked.
 2636 
 2637 
 2638      Stream:   Initializer process output.
 2639 
 2640      Time:     In response to an operator command.
 2641 
 2642      Meaning:  Another  process   is  performing  reconfiguration
 2643                currently, or  a fault during  reconfiguration has
 2644                left the reconfiguration tables locked.
 2645 
 2646      Action:   If  it  is  certain   that  no  other  process  is
 2647                reconfiguring,   and   that    the   fault   which
 2648                interrupted  reconfiguration has  been cured,  the
 2649                reconfigure$force_unlock  command may  be used  to
 2650                clear the lock at the direction of system staff.
 2651 
 2652 
 2653 
 2654                [obs_reconfigure.pl1]
 2655                addmain:  Request is not  within range of a single
 2656                controller.  MAIN XXX
 2657 
 2658 
 2659      Stream:   Initializer process output.
 2660 
 2661      Time:     In response to an operator command.
 2662 
 2663      Meaning:  An addmain command  must specify memory completely
 2664                within the range of a single controller.
 2665 
 2666      Action:   Enter a corrected command line.
 2667 
 2668 
 2669                [obs_reconfigure.pl1]
 2670                addmain:  Wrong number of arguments supplied.
 2671 
 2672 
 2673      Stream:   Initializer process output.
 2674 
 2675      Time:     In response to an operator command.
 2676 
 2677      Meaning:  Invalid input was typed.
 2678 
 2679      Action:   Enter a corrected command line.
 2680 
 2681 
 2682 addmem                          47            08/03/23     MR12.7^L
 2683 
 2684 
 2685 
 2686 
 2687                [add_scu.pl1]
 2688                addmem:  Added MEM X.
 2689 
 2690 
 2691      Stream:   BOS Typewriter.
 2692 
 2693      Time:     In response to an operator command.
 2694 
 2695      Meaning:  The system control unit X has been added.
 2696 
 2697      Action:   No operator action is required.
 2698 
 2699 
 2700                [obs_reconfigure.pl1]
 2701                addmem:   Illegal command or  subroutine argument.
 2702                BLAH
 2703 
 2704 
 2705      Stream:   Initializer process output.
 2706 
 2707      Time:     In response to an operator command.
 2708 
 2709      Meaning:  Invalid input was typed.
 2710 
 2711      Action:   Enter a corrected command line.
 2712 
 2713 
 2714                [obs_reconfigure.pl1]
 2715                addmem:  MEM Y cannot be accessed by CPU X.
 2716 
 2717 
 2718      Stream:   Initializer process output.
 2719 
 2720      Time:     In response to an operator command.
 2721 
 2722      Meaning:  CPU   X  is   unable   to   access  MEM   Y.   The
 2723                configuration  deck may  be incorrect,  or the CPU
 2724                and SCU switches may be in the wrong settings.
 2725 
 2726      Action:   Check the  switches and make sure  that they agree
 2727                with  the  configuration  deck.   Then  try addmem
 2728                again.
 2729 
 2730 
 2731 
 2732                [obs_reconfigure.pl1]
 2733                addmem:  MEM Y does not  have mask assigned to CPU
 2734                X.
 2735 
 2736 
 2737      Stream:   Initializer process output.
 2738 
 2739 
 2740 addmem                          48            08/03/23     MR12.7^L
 2741 
 2742 
 2743      Time:     In response to an operator command.
 2744 
 2745      Meaning:  The  MASK/PORT  ASSIGNMENT  (4MW  SCU)  or EXECUTE
 2746                INTERRUPT MASK  ASSIGNMENT (6000 SCU)  switches on
 2747                SCU Y are incorrect.
 2748 
 2749      Action:   Fix the switches and try addmem again.
 2750 
 2751 
 2752                [obs_reconfigure.pl1]
 2753                addmem:  MEM  Y has duplicate mask  assignments to
 2754                CPU X.
 2755 
 2756 
 2757      Stream:   Initializer process output.
 2758 
 2759      Time:     In response to an operator command.
 2760 
 2761      Meaning:  The  MASK/PORT  ASSIGNMENT  (4MW  SCU)  or EXECUTE
 2762                INTERRUPT MASK  ASSIGNMENT (6000 SCU)  switches on
 2763                SCU Y are incorrect.
 2764 
 2765      Action:   Fix the switches and try addmem again.
 2766 
 2767 
 2768                [obs_reconfigure.pl1]
 2769                addmem:   MEM Y  has  mask  Z assigned  to non-CPU
 2770                port.
 2771 
 2772 
 2773      Stream:   Initializer process output.
 2774 
 2775      Time:     In response to an operator command.
 2776 
 2777      Meaning:  The  MASK/PORT  ASSIGNMENT  (4MW  SCU)  or EXECUTE
 2778                INTERRUPT MASK  ASSIGNMENT (6000 SCU)  switches on
 2779                SCU Y are incorrect.
 2780 
 2781      Action:   Fix the switches and try addmem again.
 2782 
 2783 
 2784                [obs_reconfigure.pl1]
 2785                addmem:  MEM Y is already online.
 2786 
 2787 
 2788      Stream:   Initializer process output.
 2789 
 2790      Time:     In response to an operator command.
 2791 
 2792      Meaning:  An  addmem Y  command was   typed when  SCU Y  was
 2793                already online.
 2794 
 2795      Action:   No operator action is required.
 2796 
 2797 
 2798 addmem                          49            08/03/23     MR12.7^L
 2799 
 2800 
 2801 
 2802 
 2803                [obs_reconfigure.pl1]
 2804                addmem:  MEM Y is not configured.
 2805 
 2806 
 2807      Stream:   Initializer process output.
 2808 
 2809      Time:     In response to an operator command.
 2810 
 2811      Meaning:  There is no MEM card  in the configuration for MEM
 2812                y.  The SCU cannot be added.
 2813 
 2814      Action:   If  the SCU name  was mistyped, enter  a corrected
 2815                command.   If the  configuration deck  omitted the
 2816                MEM card, the SCU cannot be added until the system
 2817                is shut down and the deck corrected.
 2818 
 2819 
 2820 
 2821                [obs_reconfigure.pl1]
 2822                addmem:  MEM Y is not enabled on CPU X.
 2823 
 2824 
 2825      Stream:   Initializer process output.
 2826 
 2827      Time:     In response to an operator command.
 2828 
 2829      Meaning:  The  ENABLE switch  on the  CONFIGURATION panel of
 2830                CPU X does not enable SCU Y.  The memory cannot be
 2831                added.
 2832 
 2833      Action:   Fix the switches and try addmem again.
 2834 
 2835 
 2836                [obs_reconfigure.pl1]
 2837                addmem:  MEM Y is not in PROGRAM mode.
 2838 
 2839 
 2840      Stream:   Initializer process output.
 2841 
 2842      Time:     In response to an operator command.
 2843 
 2844      Meaning:  The  MODE switch on  4MW SCU Y  is not in  PROGRAM
 2845                mode.  The SCU cannot be added.
 2846 
 2847      Action:   Fix the switches and try addmem again.
 2848 
 2849      Action:   No operator action is required.
 2850 
 2851 
 2852                [obs_reconfigure.pl1]
 2853                addmem:  Reconfiguration database is locked.
 2854 
 2855 
 2856 addmem                          50            08/03/23     MR12.7^L
 2857 
 2858 
 2859      Stream:   Initializer process output.
 2860 
 2861      Time:     In response to an operator command.
 2862 
 2863      Meaning:  Another  process   is  performing  reconfiguration
 2864                currently, or  a fault during  reconfiguration has
 2865                left the reconfiguration tables locked.
 2866 
 2867      Action:   If  it  is  certain   that  no  other  process  is
 2868                reconfiguring,   and   that    the   fault   which
 2869                interrupted  reconfiguration has  been cured,  the
 2870                reconfigure$force_unlock  command may  be used  to
 2871                clear the lock at the direction of system staff.
 2872 
 2873 
 2874 
 2875                [obs_reconfigure.pl1]
 2876                addmem:   Size   of  MEM  Y  disagrees   with  CPU
 2877                switches.
 2878 
 2879 
 2880      Stream:   Initializer process output.
 2881 
 2882      Time:     In response to an operator command.
 2883 
 2884      Meaning:  The memory size on  the configuration card for MEM
 2885                Y disagrees with the size on the CPU switches.
 2886 
 2887      Action:   If  the switches are  incorrect, fix them  and try
 2888                addmem  again.   If   the  configuration  deck  is
 2889                incorrect,  the system must  be shut down  and the
 2890                deck corrected before the SCU can be added.
 2891 
 2892 
 2893 
 2894                [obs_reconfigure.pl1]
 2895                addmem:  Switches for MEM  Y set improperly on CPU
 2896                X.
 2897 
 2898 
 2899      Stream:   Initializer process output.
 2900 
 2901      Time:     In response to an operator command.
 2902 
 2903      Meaning:  The  ADDRESS  ASSIGNMENT  switches  for  SCU Y are
 2904                incorrect on CPU X.
 2905 
 2906      Action:   Correct the switches and try addmem again.
 2907 
 2908 
 2909                [obs_reconfigure.pl1]
 2910                addmem:  Wrong number of arguments supplied.
 2911 
 2912 
 2913 
 2914 addmem                          51            08/03/23     MR12.7^L
 2915 
 2916 
 2917      Stream:   Initializer process output.
 2918 
 2919      Time:     In response to an operator command.
 2920 
 2921      Meaning:  Invalid input was typed.
 2922 
 2923      Action:   Enter a corrected command line.
 2924 
 2925 
 2926                [admin_.pl1]
 2927                admin_:   abs   ABS_FUNCTION:   Expected  argument
 2928                missing.  After PREV_ARG.
 2929 
 2930 
 2931      Stream:   as (severity 1)
 2932 
 2933      Time:     In response to an operator abs command.
 2934 
 2935      Meaning:  A required value to a control argument supplied in
 2936                the "abs" command line is missing.
 2937 
 2938      Action:   Reenter corrected command line.
 2939 
 2940 
 2941                [admin_.pl1]
 2942                admin_:  abs:  ABS_FUNCT:  error:  absentee not up
 2943 
 2944 
 2945      Stream:   as (severity 1)
 2946 
 2947      Time:     In response to an operator command.
 2948 
 2949      Meaning:  An  abs  command  was   given,  but  the  absentee
 2950                facility had never been started up.  No action was
 2951                taken on the command.
 2952 
 2953      Action:   Type abs start to start up the absentee facility.
 2954 
 2955 
 2956                [admin_.pl1]
 2957                admin_:  abs:  ABS_FUNCT:  error:  Invalid abs job
 2958                selection argument:  SSSS
 2959 
 2960 
 2961      Stream:   as (severity 1)
 2962 
 2963      Time:     In response to an operator command.
 2964 
 2965      Meaning:  The job selection argument  SSSS is not recognized
 2966                as valid.
 2967 
 2968      Action:   Type  "help abs"  for details  of the  abs command
 2969                usage and try again.
 2970 
 2971 
 2972 admin_                          52            08/03/23     MR12.7^L
 2973 
 2974 
 2975 
 2976 
 2977                [admin_.pl1]
 2978                admin_:  abs:  ABS_FUNCT:  error:  Job in absentee
 2979                slot X does not match absin entry name SSSS
 2980 
 2981 
 2982      Stream:   as (severity 1)
 2983 
 2984      Time:     In response to an operator command.
 2985 
 2986      Meaning:  The  entry  name  SSSS  of  the  absin  of the job
 2987                running  in specified  absentee slot  of absX does
 2988                not match the specified absin entry name.
 2989 
 2990      Action:   Recheck job specifications and try again.
 2991 
 2992 
 2993                [admin_.pl1]
 2994                admin_:  abs:  ABS_FUNCT:  error:  Job in absentee
 2995                slot    X    does    not    match    absin    path
 2996                DIR_PATH>ENTRY_NAME
 2997 
 2998 
 2999      Stream:   as (severity 1)
 3000 
 3001      Time:     In response to an operator command.
 3002 
 3003      Meaning:  The pathname  of the absin  of the job  running in
 3004                specified absentee slot of absX does not match the
 3005                specified absin pathname.
 3006 
 3007      Action:   Recheck job specifications and try again.
 3008 
 3009 
 3010                [admin_.pl1]
 3011                admin_:  abs:  ABS_FUNCT:  error:  Job in absentee
 3012                slot X does not match request ID YYYY
 3013 
 3014 
 3015      Stream:   as (severity 1)
 3016 
 3017      Time:     In response to an operator command.
 3018 
 3019      Meaning:  The  ID of the  job running in  specified absentee
 3020                slot of  absX does not  match the specified  ID of
 3021                YYYY.
 3022 
 3023      Action:   Recheck job specifications and try again.
 3024 
 3025 
 3026                [admin_.pl1]
 3027 
 3028 
 3029 
 3030 admin_                          53            08/03/23     MR12.7^L
 3031 
 3032 
 3033                admin_:  abs:  ABS_FUNCT:  error:  Job in absentee
 3034                slot X is not from queue DDDD
 3035 
 3036 
 3037      Stream:   as (severity 1)
 3038 
 3039      Time:     In response to an operator command.
 3040 
 3041      Meaning:  The  queue of  the absin   of the  job running  in
 3042                specified absentee slot of absX does not match the
 3043                queue number DDDD.
 3044 
 3045      Action:   Recheck job specifications and try again.
 3046 
 3047 
 3048                [admin_.pl1]
 3049                admin_:  abs:  ABS_FUNCT:  error:  Job in absentee
 3050                slot X is not from sender SSSS
 3051 
 3052 
 3053      Stream:   as (severity 1)
 3054 
 3055      Time:     In response to an operator command.
 3056 
 3057      Meaning:  The  sender of  the absin  of the  job running  in
 3058                specified absentee slot of absX does not match the
 3059                specified sender, SSSS.
 3060 
 3061      Action:   Recheck job specifications and try again.
 3062 
 3063 
 3064                [admin_.pl1]
 3065                admin_:  abs:  ABS_FUNCT:  error:  Job in absentee
 3066                slot X is not from user NAME.PROJ
 3067 
 3068 
 3069      Stream:   as (severity 1)
 3070 
 3071      Time:     In response to an operator command.
 3072 
 3073      Meaning:  The job running in specified absentee slot of absX
 3074                is not from specified user, NAME.PROJ.
 3075 
 3076      Action:   Recheck job specifications and try again.
 3077 
 3078 
 3079                [admin_.pl1]
 3080                admin_:  abs:   ABS_FUNCT:  error:  More  than one
 3081                specification of an attribute is present:  SSSS
 3082 
 3083 
 3084      Stream:   as (severity 1)
 3085 
 3086 
 3087 
 3088 admin_                          54            08/03/23     MR12.7^L
 3089 
 3090 
 3091      Time:     In response to an operator command.
 3092 
 3093      Meaning:  The SSSS  attribute has already been  specified to
 3094                select  an  absentee  job   on  the  operator  abs
 3095                command.  An attribute can only be used once.
 3096 
 3097      Action:   Enter a corrected command line.
 3098 
 3099 
 3100                [admin_.pl1]
 3101                admin_:   abs:   ABS_FUNCT:   error:   No  job  in
 3102                absentee slot X (status= SSSS).
 3103 
 3104 
 3105      Stream:   as (severity 1)
 3106 
 3107      Time:     In response to an operator command.
 3108 
 3109      Meaning:  The absentee slot absX has an entry status of SSSS
 3110                indicating that no user is using it.
 3111 
 3112      Action:   Enter a corrected command line.
 3113 
 3114 
 3115                [admin_.pl1]
 3116                admin_:  abs:  ABS_FUNCT:  error:  Personid NAME >
 3117                22 characters.
 3118 
 3119 
 3120      Stream:   as (severity 1)
 3121 
 3122      Time:     In response to an operator command.
 3123 
 3124      Meaning:  The "abs  ABS_FUNCT" operator command  specified a
 3125                user name that is longer than 22 characters.
 3126 
 3127      Action:   Enter a corrected command line.
 3128 
 3129 
 3130                [admin_.pl1]
 3131                admin_:  abs:  ABS_FUNCT:   error:  Projectid SSSS
 3132                is longer than 9 characters.
 3133 
 3134 
 3135      Stream:   as (severity 1)
 3136 
 3137      Time:     In response to an operator command.
 3138 
 3139      Meaning:  The  "abs ABS_FUNCT" operator  command incorrectly
 3140                specified  a project  name that  is longer  than 9
 3141                characters.
 3142 
 3143      Action:   Enter a corrected command line.
 3144 
 3145 
 3146 admin_                          55            08/03/23     MR12.7^L
 3147 
 3148 
 3149 
 3150 
 3151                [admin_.pl1]
 3152                admin_:    abs:    ABS_FUNCT:    error:   Relative
 3153                pathnames not allowed:  SSSS
 3154 
 3155 
 3156      Stream:   as (severity 1)
 3157 
 3158      Time:     In response to an operator command.
 3159 
 3160      Meaning:  The pathname of the absin was expected and it must
 3161                be  an  absolute  pathname,  starting  with  a ">"
 3162                character.
 3163 
 3164      Action:   Enter a corrected command line.
 3165 
 3166 
 3167                [admin_.pl1]
 3168                admin_:    abs:   ABS_FUNCT:    error:   Selection
 3169                arguments matched no running absentee jobs.
 3170 
 3171 
 3172      Stream:   as (severity 1)
 3173 
 3174      Time:     In response to an operator command.
 3175 
 3176      Meaning:  No  running   job  was  found  that   matched  the
 3177                selection  arguments supplied  on the  abs command
 3178                line.
 3179 
 3180      Action:   Recheck job specifications and try again.
 3181 
 3182 
 3183                [admin_.pl1]
 3184                admin_:  abs:   ABS_FUNCT:  error:  SSSS is  not a
 3185                valid Person.Project.
 3186 
 3187 
 3188      Stream:   as (severity 1)
 3189 
 3190      Time:     In response to an operator command.
 3191 
 3192      Meaning:  The  "abs  ABS_FUNCT"  operator  command  did  not
 3193                specify a valid Person.Project in the string SSSS.
 3194 
 3195      Action:   Enter a corrected command line.
 3196 
 3197 
 3198                [admin_.pl1]
 3199                admin_:    abs:   ABS_FUNCT:   error:    The  absN
 3200                argument is not valid.
 3201 
 3202 
 3203 
 3204 admin_                          56            08/03/23     MR12.7^L
 3205 
 3206 
 3207      Stream:   as (severity 1)
 3208 
 3209      Time:     In response to an operator command.
 3210 
 3211      Meaning:  The "abs ABS_FUNCT"  operator command cannot allow
 3212                use of the absN argument for job selection.
 3213 
 3214      Action:   Enter a corrected command line.
 3215 
 3216 
 3217                [admin_.pl1]
 3218                admin_:  abs:  ABS_FUNCT:   error:  User name (not
 3219                ""*"") must be given.
 3220 
 3221 
 3222      Stream:   as (severity 1)
 3223 
 3224      Time:     In response to an operator command.
 3225 
 3226      Meaning:  The "abs ABS_FUNCT" operator command requires that
 3227                a user name be supplied.  Cannot use "*".
 3228 
 3229      Action:   Enter a corrected command line.
 3230 
 3231 
 3232                [admin_.pl1]
 3233                admin_:  abs:  ABS_FUNCT:   error:  User name must
 3234                be given.
 3235 
 3236 
 3237      Stream:   as (severity 1)
 3238 
 3239      Time:     In response to an operator command.
 3240 
 3241      Meaning:  The "abs ABS_FUNCT" operator command requires that
 3242                a user name be supplied.
 3243 
 3244      Action:   Enter a corrected command line.
 3245 
 3246 
 3247                [admin_.pl1]
 3248                admin_:   abs:  ABS_FUNCT:   Invalid queue  number
 3249                DDDD
 3250 
 3251 
 3252      Stream:   as (severity 1)
 3253 
 3254      Time:     In response to an operator command.
 3255 
 3256      Meaning:  The value after the  -queue job selection argument
 3257                is  invalid.   It  must  be  the  strings  "fg" or
 3258                "foreground" or  a between the values of  1 and 4,
 3259                inclusive.
 3260 
 3261 
 3262 admin_                          57            08/03/23     MR12.7^L
 3263 
 3264 
 3265      Action:   Enter a corrected command line.
 3266 
 3267 
 3268                [admin_.pl1]
 3269                admin_:    abs:   ABS_FUNCT:   No   job  selection
 3270                arguments given.
 3271 
 3272 
 3273      Stream:   as (severity 1)
 3274 
 3275      Time:     In response to an operator command.
 3276 
 3277      Meaning:  After  processing   the  arguments  on   the  "abs
 3278                abs_funct"  operator  command,  no  job  selection
 3279                arguments were encountered.
 3280 
 3281      Action:   Type  "help abs"  for details  of the  abs command
 3282                usage and try again.
 3283 
 3284 
 3285                [admin_.pl1]
 3286                admin_:   abs:  absentee not  up, and will  not be
 3287                started automatically
 3288 
 3289 
 3290      Stream:   as (severity 1)
 3291 
 3292      Time:     When operator  entered "abs stop"  before absentee
 3293                facility was started.
 3294 
 3295      Meaning:  The command can be  entered at standard to prevent
 3296                the    absentee   facility   from    starting   up
 3297                automatically after a "startup" command is used.
 3298 
 3299      Action:   No operator action is required.
 3300 
 3301 
 3302                [admin_.pl1]
 3303                admin_:  abs:  All absentee  processes have run to
 3304                completion.
 3305 
 3306 
 3307      Stream:   as (severity 1)
 3308 
 3309      Time:     When shutting down the absentee facility.
 3310 
 3311      Meaning:  This  message is  printed after  the operator  has
 3312                issued  an  abs  stop  command  or  the system has
 3313                issued  an automatic  abs stop  prior to shutdown.
 3314                The system allows 30 minutes for all absentee jobs
 3315                to finish before logging them out, then prints the
 3316                message.
 3317 
 3318 
 3319 
 3320 admin_                          58            08/03/23     MR12.7^L
 3321 
 3322 
 3323      Action:   It is now safe to proceed with the shutdown.
 3324 
 3325 
 3326                [admin_.pl1]
 3327                admin_:  abs:   auto abs stop will  be at MM/DD/YY
 3328                HHMM.T
 3329 
 3330 
 3331      Stream:   as (severity 1)
 3332 
 3333      Time:     In  response to  an  operator  down command  or at
 3334                startup.
 3335 
 3336      Meaning:  This  is the  response to  a down  command if  the
 3337                absentee facility  is running, or to  an abs start
 3338                command if the absentee is brought up after a down
 3339                time has been set.  The  time for an automatic abs
 3340                stop is  20 minutes before  the system is  to shut
 3341                down.  An "abs stop now"  is done 10 minutes after
 3342                the  scheduled shutdown.   Refer also  to the stop
 3343                command description.
 3344 
 3345      Action:   No operator action is required.
 3346 
 3347 
 3348                [admin_.pl1]
 3349                admin_:   abs:   Bumping  all  remaining  absentee
 3350                processes.
 3351 
 3352 
 3353      Stream:   as (severity 1)
 3354 
 3355      Time:     System shutdown.
 3356 
 3357      Meaning:  The  absentee facility  waits 30  minutes for  all
 3358                absentee jobs  to run to completion  after the abs
 3359                stop command has been  issued.  Then it types this
 3360                message  and bumps  them all.   Refer also  to the
 3361                stop command description.
 3362 
 3363      Action:   No operator action is required.
 3364 
 3365 
 3366                [admin_.pl1]
 3367                admin_:  abs:   cpu_limit (MMMM), queues  1-4:  WW
 3368                XX YY ZZ (seconds)
 3369 
 3370 
 3371      Stream:   as (severity 1)
 3372 
 3373      Time:     In  response to   "abs cpu_limit"  command without
 3374                arguments.
 3375 
 3376 
 3377 
 3378 admin_                          59            08/03/23     MR12.7^L
 3379 
 3380 
 3381      Meaning:  Informative  message indicating current  values of
 3382                cpu_limit  for each  absentee queue.   MMM is  the
 3383                mode, "auto" or "manual".
 3384 
 3385      Action:   No operator action is required.
 3386 
 3387 
 3388                [admin_.pl1]
 3389                admin_:  abs:  cpu_limit:  error:  Usage is:  "abs
 3390                cpu_limit l1,l2,l3,l4" (limits in seconds)
 3391 
 3392 
 3393      Stream:   as (severity 1)
 3394 
 3395      Time:     In response to an operator command.
 3396 
 3397      Meaning:  Informative  message  that  is  displayed  when an
 3398                operator "abs cpu_limit" command without arguments
 3399                is entered.
 3400 
 3401      Action:   Enter a corrected command line.
 3402 
 3403 
 3404                [admin_.pl1]
 3405                admin_:   abs:  error:   The abs  CCCC command can
 3406                not be used before answering service startup.
 3407 
 3408 
 3409      Stream:   as (severity 1)
 3410 
 3411      Time:     In response to an operator abs command.
 3412 
 3413      Meaning:  Only  the "abs stop"  command may be  given before
 3414                the answering service starts  up.  This allows the
 3415                operator to stop the  absentee facility before the
 3416                system finishes initialzation.
 3417 
 3418      Action:   Enter a corrected command line.
 3419 
 3420 
 3421                [admin_.pl1]
 3422                admin_:   abs:  error:   unknown absentee  command
 3423                WXYZ
 3424 
 3425 
 3426      Stream:   as (severity 1)
 3427 
 3428      Time:     In response to an operator command.
 3429 
 3430      Meaning:  The  operator  typed  abs   WXYZ  where  WXYZ  was
 3431                unrecognizable  to  the  system.   No  action  was
 3432                taken.
 3433 
 3434 
 3435 
 3436 admin_                          60            08/03/23     MR12.7^L
 3437 
 3438 
 3439      Action:   Enter a corrected command line.
 3440 
 3441 
 3442                [admin_.pl1]
 3443                admin_:  abs:  ERROR_TABLE_MESSAGE PATHNAME
 3444 
 3445 
 3446      Stream:   as (severity 1)
 3447 
 3448      Time:     In response to the operator abs command.
 3449 
 3450      Meaning:  The   ERROR_TABLE_MESSAGE  was   encountered  when
 3451                trying  to  expand  the  PATHNAME  supplied in the
 3452                operator abs command line.
 3453 
 3454      Action:   Enter a corrected command line.
 3455 
 3456 
 3457                [admin_.pl1]
 3458                admin_:  abs:   list:  error:  No job  in absentee
 3459                slot X.
 3460 
 3461 
 3462      Stream:   as (severity 1)
 3463 
 3464      Time:     In response to an operator command.
 3465 
 3466      Meaning:  The absentee slot absX does not exist.
 3467 
 3468      Action:   Enter a corrected command line.
 3469 
 3470 
 3471                [admin_.pl1]
 3472                admin_:   abs:  list:   error:  The  absN argument
 3473                cannot be used when absentee is not up.
 3474 
 3475 
 3476      Stream:   as (severity 1)
 3477 
 3478      Time:     $reponse
 3479 
 3480      Meaning:  Cannot use the "absN"  argument to select absentee
 3481                jobs to list until  the absentee facility has been
 3482                started.
 3483 
 3484      Action:   Use  other  job  selection  criteria  or type "abs
 3485                start" and try again.
 3486 
 3487 
 3488                [admin_.pl1]
 3489                admin_:  abs:  maxq (MMMM):  Q
 3490 
 3491 
 3492 
 3493 
 3494 admin_                          61            08/03/23     MR12.7^L
 3495 
 3496 
 3497      Stream:   as (severity 1)
 3498 
 3499      Time:     In response to "abs maxq" without arguments.
 3500 
 3501      Meaning:  Informative  message indicating current  status of
 3502                maxq  and queue  last searched  (Q).  MMMM  is the
 3503                mode, "auto" or "manual".
 3504 
 3505      Action:   No operator action is required.
 3506 
 3507 
 3508                [admin_.pl1]
 3509                admin_:   abs:  maxq:    error:  abs  maxqueue has
 3510                invalid value:  XXX
 3511 
 3512 
 3513      Stream:   as (severity 1)
 3514 
 3515      Time:     In response to an operator command.
 3516 
 3517      Meaning:  An  abs  maxq  or  abs  start  command  had  as an
 3518                argument something  that was not a  number, or was
 3519                too big,  or was a negative number.   No action is
 3520                taken.
 3521 
 3522      Action:   Enter a corrected command line.
 3523 
 3524 
 3525                [admin_.pl1]
 3526                admin_:  abs:  maxu (MMMM):  UUUU
 3527 
 3528 
 3529      Stream:   as (severity 1)
 3530 
 3531      Time:     In response to "abs maxu" operator command without
 3532                arguments.
 3533 
 3534      Meaning:  Informative  message indicating current  status of
 3535                maxu and maximum absentee  users allowed.  MMMM is
 3536                the  mode,  "auto"  or   "manual".   UUUU  is  the
 3537                load_units.
 3538 
 3539      Action:   No operator action is required.
 3540 
 3541 
 3542                [admin_.pl1]
 3543                admin_:  abs:  maxu:  error:  abs maxusers may not
 3544                be greater than system maxusers:  SSSS
 3545 
 3546 
 3547      Stream:   as (severity 1)
 3548 
 3549      Time:     In response to an operator command.
 3550 
 3551 
 3552 admin_                          62            08/03/23     MR12.7^L
 3553 
 3554 
 3555      Meaning:  The  argument, SSSS,  to the  operator "abs  maxu"
 3556                command cannot be greater than the maximum allowed
 3557                users that can be on the system.
 3558 
 3559      Action:   Enter a corrected command line.
 3560 
 3561 
 3562                [admin_.pl1]
 3563                admin_:  abs:  maxu:  error:  abs maxusers may not
 3564                be negative:  SSSS
 3565 
 3566 
 3567      Stream:   as (severity 1)
 3568 
 3569      Time:     In response to an operator command.
 3570 
 3571      Meaning:  The  argument, SSSS,  to the  operator "abs  maxu"
 3572                command was not a  positive numeric or the string,
 3573                "auto".  The numeric value is  in tenths of a load
 3574                unit.
 3575 
 3576      Action:   Enter a corrected command line.
 3577 
 3578 
 3579                [admin_.pl1]
 3580                admin_:  abs:  maxu:  error:  abs maxusers must be
 3581                numeric or "auto":  SSSS
 3582 
 3583 
 3584      Stream:   as (severity 1)
 3585 
 3586      Time:     In response to an operator command.
 3587 
 3588      Meaning:  The  argument, SSSS,  to the  operator "abs  maxu"
 3589                command was not a  positive numeric or the string,
 3590                "auto".  The numeric value is  in tenths of a load
 3591                unit.
 3592 
 3593      Action:   Enter a corrected command line.
 3594 
 3595 
 3596                [admin_.pl1]
 3597                admin_:  abs:  qres (MMMM):  WW XX YY ZZ
 3598 
 3599 
 3600      Stream:   as (severity 1)
 3601 
 3602      Time:     In response to "abs maxq" without arguments.
 3603 
 3604      Meaning:  Informative  message indicating current  status of
 3605                absentee queue  reservation for each  queue.  MMMM
 3606                is the mode, "auto" or "manual".
 3607 
 3608 
 3609 
 3610 admin_                          63            08/03/23     MR12.7^L
 3611 
 3612 
 3613      Action:   No operator action is required.
 3614 
 3615 
 3616                [admin_.pl1]
 3617                admin_:  abs:  qres:  error:  abs qres has invalid
 3618                value:  DDDD
 3619 
 3620 
 3621      Stream:   as (severity 1)
 3622 
 3623      Time:     In response to an operator command.
 3624 
 3625      Meaning:  An  invalid  qres  argument  was  detected  in  an
 3626                operator "abs qres" command.  The argument must be
 3627                "auto" or a positive decimal number.
 3628 
 3629      Action:   Enter a corrected command line.
 3630 
 3631 
 3632                [admin_.pl1]
 3633                admin_:  abs:  queue limits:  WW XX YY ZZ
 3634 
 3635 
 3636      Stream:   as (severity 1)
 3637 
 3638      Time:     In response to "abs qres" operator command.
 3639 
 3640      Meaning:  Informative  message indicating the  current queue
 3641                reservation limits.
 3642 
 3643      Action:   No operator action is required.
 3644 
 3645 
 3646                [admin_.pl1]
 3647                admin_:  abs:  Queue errors (*=dropped):
 3648                admin_:  abs:  FG 0 1 2 3 4
 3649                admin_:  abs:  TT VV WW XX YY ZZ
 3650                admin_:  abs:  * * * * * *
 3651 
 3652 
 3653 
 3654      Stream:   as (severity 1)
 3655 
 3656      Time:     In response to "abs queue" operator command.
 3657 
 3658      Meaning:  Displays the  errors for each queue  and indicates
 3659                which  one has  been dropped.   If none  have been
 3660                dropped, the  last line will not  be displayed nor
 3661                will the string "(*=dropped)"  appear in the first
 3662                line.
 3663 
 3664      Action:   Contact the system programming staff.
 3665 
 3666 
 3667 
 3668 admin_                          64            08/03/23     MR12.7^L
 3669 
 3670 
 3671 
 3672 
 3673                [admin_.pl1]
 3674                admin_:  abs:   release:  error:  Job  in absentee
 3675                slot X is not suspended.
 3676 
 3677 
 3678      Stream:   as (severity 1)
 3679 
 3680      Time:     In response to an operator command.
 3681 
 3682      Meaning:  The specified job running in absentee slot of absX
 3683                is not suspended so a release does not apply.
 3684 
 3685      Action:   Recheck job specifications and try again.
 3686 
 3687 
 3688                [admin_.pl1]
 3689                admin_:    abs:    release:    error:    Selection
 3690                arguments   matched  no   deferred  or   suspended
 3691                absentee requests.
 3692 
 3693 
 3694      Stream:   as (severity 1)
 3695 
 3696      Time:     In response to an operator command.
 3697 
 3698      Meaning:  No suspended or deferred  job was found to release
 3699                with  the arguments  supplied on  the abs  release
 3700                command line.
 3701 
 3702      Action:   Recheck job specifications and try again.
 3703 
 3704 
 3705                [admin_.pl1]
 3706                admin_:  abs:  resetting auto abs stop
 3707 
 3708 
 3709      Stream:   as (severity 1)
 3710 
 3711      Time:     In response to an operator abs stop command.
 3712 
 3713      Meaning:  An  abs stop  command overrides  an automatic  abs
 3714                stop that was set up by a down command.
 3715 
 3716      Action:   No operator action is required.
 3717 
 3718 
 3719                [admin_.pl1]
 3720                admin_:  abs:  start:  error:  absentee already up
 3721 
 3722 
 3723      Stream:   as (severity 1)
 3724 
 3725 
 3726 admin_                          65            08/03/23     MR12.7^L
 3727 
 3728 
 3729      Time:     In response to an operator abs start command.
 3730 
 3731      Meaning:  abs start was typed twice.  No action was taken on
 3732                the second issuance of the command.
 3733 
 3734      Action:   No operator action is required.
 3735 
 3736 
 3737                [admin_.pl1]
 3738                admin_:   abs:  start:   error:  absentee  not up.
 3739                cannot restart queue X
 3740 
 3741 
 3742      Stream:   as (severity 1)
 3743 
 3744      Time:     In response to an operator command.
 3745 
 3746      Meaning:  Cannot use the "abs start queue" command until the
 3747                absentee facility has been started.
 3748 
 3749      Action:   Issue the "abs start" command and try again.
 3750 
 3751 
 3752                [admin_.pl1]
 3753                admin_:  abs:  start:  error:  invalid queue to be
 3754                restarted X
 3755 
 3756 
 3757      Stream:   as (severity 1)
 3758 
 3759      Time:     In response to an operator command.
 3760 
 3761      Meaning:  An  invalid  queue  number  was  specified  in  an
 3762                operator "abs start queue"  command line.  It must
 3763                be between 1 and 4 inclusive.
 3764 
 3765      Action:   Enter a corrected command line.
 3766 
 3767 
 3768                [admin_.pl1]
 3769                admin_:  abs:  start:   error:  system coming down
 3770                soon:  no abs start
 3771 
 3772 
 3773      Stream:   as (severity 1)
 3774 
 3775      Time:     In response to an operator command.
 3776 
 3777      Meaning:  The system  is shutting down within  30 minutes so
 3778                the absentee facility will not be started.
 3779 
 3780      Action:   No operator action is required.
 3781 
 3782 
 3783 
 3784 admin_                          66            08/03/23     MR12.7^L
 3785 
 3786 
 3787 
 3788 
 3789                [admin_.pl1]
 3790                admin_:  abs:  stop:  error:   abs stop queue only
 3791                works after answering service startup
 3792 
 3793 
 3794      Stream:   as (severity 1)
 3795 
 3796      Time:     In response to an operator abs stop queue command.
 3797 
 3798      Meaning:  The answering service must complete initialization
 3799                before the "abs stop queue" command can be used.
 3800 
 3801      Action:   Allow  the system  to complete  initialization and
 3802                try again.
 3803 
 3804 
 3805                [admin_.pl1]
 3806                admin_:   abs:  stop:    error:  absentee  stop in
 3807                progress
 3808 
 3809 
 3810      Stream:   as (severity 1)
 3811 
 3812      Time:     In response to an operator command.
 3813 
 3814      Meaning:  An  abs start,  abs stop,  abs maxu,  abs maxq, or
 3815                down  command   was  issued  while   the  absentee
 3816                facility was in the process of shutting down.
 3817 
 3818      Action:   Wait for  the message that all  absentee processes
 3819                have run to completion, then reissue the command.
 3820 
 3821 
 3822 
 3823                [admin_.pl1]
 3824                admin_:  abs:  stop:  error:   invalid queue to be
 3825                stopped:  DDDD
 3826 
 3827 
 3828      Stream:   as (severity 1)
 3829 
 3830      Time:     In  response  to  an  operator  "abs  stop  queue"
 3831                command.
 3832 
 3833      Meaning:  The value  of the queue number was  not within the
 3834                values of 1 and 4, inclusive.
 3835 
 3836      Action:   Enter a corrected command line.
 3837 
 3838 
 3839                [admin_.pl1]
 3840 
 3841 
 3842 admin_                          67            08/03/23     MR12.7^L
 3843 
 3844 
 3845                admin_:   abs:  stop:   error:  missing  argument:
 3846                queue to be stopped
 3847 
 3848 
 3849      Stream:   as (severity 1)
 3850 
 3851      Time:     In  response  to  an  operator  "abs  stop  queue"
 3852                command.
 3853 
 3854      Meaning:  The "abs  stop queue" command was  entered without
 3855                supplying the number of the queue to be stopped.
 3856 
 3857      Action:   Enter a corrected command line.
 3858 
 3859 
 3860                [admin_.pl1]
 3861                admin_:   abs:   stop:   error:   unknown argument
 3862                SSSS
 3863 
 3864 
 3865      Stream:   as (severity 1)
 3866 
 3867      Time:     In response to an operator "abs stop" command.
 3868 
 3869      Meaning:  An  unknown argument,  SSSS, was  supplied to  the
 3870                "abs stop" command.
 3871 
 3872      Action:   Type "help abs" for details of the abs command and
 3873                try again.
 3874 
 3875 
 3876                [admin_.pl1]
 3877                admin_:  abs:   suspend:  error:  Job  in absentee
 3878                slot X is already suspended.
 3879 
 3880 
 3881      Stream:   as (severity 1)
 3882 
 3883      Time:     In response to an operator command.
 3884 
 3885      Meaning:  The specified job running in absentee slot of absX
 3886                is  already  suspended  and  cannot  be  suspended
 3887                again.
 3888 
 3889      Action:   Recheck job specifications and try again.
 3890 
 3891 
 3892                [admin_.pl1]
 3893                admin_:   abs:    Warning:   cpu  limits   are  in
 3894                seconds.   You just  set  queue  QQ limit  to LLLL
 3895                seconds.
 3896 
 3897 
 3898 
 3899 
 3900 admin_                          68            08/03/23     MR12.7^L
 3901 
 3902 
 3903      Stream:   as (severity 1)
 3904 
 3905      Time:     In  response  to   "abs  cpu_limit"  command  with
 3906                arguments.
 3907 
 3908      Meaning:  The  cpu_limit (LLLL)  for  queue  QQ is  below 60
 3909                seconds  which is  likely  to  be a  mistake.  The
 3910                value already given will be still be accepted.
 3911 
 3912      Action:   Reenter  the  command  with  corrected  values  if
 3913                originally incorrect.
 3914 
 3915 
 3916                [admin_.pl1]
 3917                admin_:  abs:  Zero errors on all absentee queues.
 3918 
 3919 
 3920      Stream:   as (severity 1)
 3921 
 3922      Time:     In response to "abs queue" operator command.
 3923 
 3924      Meaning:  Informative message which  indicates that no queue
 3925                has  been dropped and  no errors recorded  for any
 3926                queue.
 3927 
 3928      Action:   No operator action is required.
 3929 
 3930 
 3931                [admin_.pl1]
 3932                admin_:  bump:  USER.PROJECT bumped.
 3933 
 3934 
 3935      Stream:   as (severity 1)
 3936 
 3937      Time:     In  response  to  the  bump  command  or  a system
 3938                shutdown.
 3939 
 3940      Meaning:  The  specified user has  been notified that  he or
 3941                she must get off the  system.  If a grace time was
 3942                specified, the user is allowed that amount of time
 3943                to  logout.  Otherwise,  the user  is removed from
 3944                the system immediately.
 3945 
 3946      Action:   No operator action is required.
 3947 
 3948 
 3949                [admin_.pl1]
 3950                admin_:  COMMAND:  error:  Invalid FNP tag:  X
 3951 
 3952 
 3953      Stream:   as (severity 1)
 3954 
 3955 
 3956 
 3957 
 3958 admin_                          69            08/03/23     MR12.7^L
 3959 
 3960 
 3961      Time:     Response  to an operator  "load_fnp", "fdump_fnp",
 3962                "dump_fnp", "start_fnp", or "stop_fnp" command.
 3963 
 3964      Meaning:  The supplied  FNP tag was more  than one character
 3965                or was not between a-h inclusive.
 3966 
 3967      Action:   Enter a corrected command line.
 3968 
 3969 
 3970                [admin_.pl1]
 3971                admin_:  COMMAND:  error:  No FNP tag specified.
 3972 
 3973 
 3974      Stream:   as (severity 1)
 3975 
 3976      Time:     Response  to an operator  "load_fnp", "fdump_fnp",
 3977                "dump_fnp", "start_fnp", or "stop_fnp" command.
 3978 
 3979      Meaning:  The operator did not supply an FNP identifier.
 3980 
 3981      Action:   Enter a corrected command line.
 3982 
 3983 
 3984                [admin_.pl1]
 3985                admin_:    COMMAND:     error:    No   multiplexer
 3986                specified.
 3987 
 3988 
 3989      Stream:   as (severity 1)
 3990 
 3991      Time:     Response  to an  operator "load_mpx",  "dump_mpx",
 3992                "start_mpx", "shutdown_mpx" or "stop_mpx" command.
 3993 
 3994      Meaning:  The operator did not supply a multiplexer name.
 3995 
 3996      Action:   Enter a corrected command line.
 3997 
 3998 
 3999                [admin_.pl1]
 4000                admin_:  COMMAND:  ERROR_TABLE_MESSAGE
 4001 
 4002 
 4003      Stream:   as (severity 1)
 4004 
 4005      Time:     In response to operator command, COMMAND.
 4006 
 4007      Meaning:  The  ERROR_TABLE_MESSAGE error was  encounted when
 4008                processing the operator command, COMMAND.
 4009 
 4010      Action:   Type "help  COMMAND" for details of  the command's
 4011                usage.
 4012 
 4013 
 4014 
 4015 
 4016 admin_                          70            08/03/23     MR12.7^L
 4017 
 4018 
 4019 
 4020 
 4021                [admin_.pl1]
 4022                admin_:  COMMAND:  PERSON.PROJECT has "nobump"
 4023 
 4024 
 4025      Stream:   as (severity 1)
 4026 
 4027      Time:     System shutdown.
 4028 
 4029      Meaning:  The  PERSON.PROJECT user  cannot be  bumped by the
 4030                automatic  shutdown  or  in  response  to the stop
 4031                command.   The nobump  attribute is  normally only
 4032                used by system administrator users.
 4033 
 4034      Action:   Try  to contact  the user   to arrange  a time  to
 4035                actually shutdown.  If necessary,  the user can be
 4036                bumped by specifying the  channel name in the bump
 4037                command.  This  will only work if  the process has
 4038                not been  disconnected.  Otherwise, you  will have
 4039                to answer "yes" to the shutdown command.
 4040 
 4041 
 4042 
 4043                [admin_.pl1]
 4044                admin_:  down:  auto shutdown  will be at MM/DD/YY
 4045                HHMM.T
 4046 
 4047 
 4048      Stream:   as (severity 1)
 4049 
 4050      Time:     In  response to  an  operator  down command  or at
 4051                startup.
 4052 
 4053      Meaning:  This  is the  response  to  the down  command.  It
 4054                indicates  the scheduled   shutdown time.   A down
 4055                command is issued  automatically at system startup
 4056                time after  a crash; if  a down command  was given
 4057                before  the crash  occurred, and  the time  of the
 4058                scheduled shutdown is more  than 30 minutes in the
 4059                future.
 4060 
 4061      Action:   If  the value  shown  in  the message  is correct,
 4062                proceed.   If not  correct, reset  the shutdown by
 4063                typing down 0 and then try again.
 4064 
 4065 
 4066 
 4067                [admin_.pl1]
 4068                admin_:    down:   error:    no  system   shutdown
 4069                scheduled
 4070 
 4071 
 4072 
 4073 
 4074 admin_                          71            08/03/23     MR12.7^L
 4075 
 4076 
 4077      Stream:   as (severity 1)
 4078 
 4079      Time:     In response to operator entering, "down 0".
 4080 
 4081      Meaning:  The "down  0" command line  cancels a down  but no
 4082                system  shutdown  was  scheduled.   No  action was
 4083                taken.
 4084 
 4085      Action:   No operator action is required.
 4086 
 4087 
 4088                [admin_.pl1]
 4089                admin_:   down:  error:    uptime is  earlier than
 4090                downtime.
 4091 
 4092 
 4093      Stream:   as (severity 1)
 4094 
 4095      Time:     In response to an operator down command.
 4096 
 4097      Meaning:  The  operator  down  command  specifies  that  the
 4098                expected time that the system will be up is before
 4099                the time that it is  scheduled to be shutdown.  No
 4100                action was taken.
 4101 
 4102      Action:   Enter a corrected command line.
 4103 
 4104 
 4105                [admin_.pl1]
 4106                admin_:  down:  error:  XXX invalid clock time.
 4107 
 4108 
 4109      Stream:   as (severity 1)
 4110 
 4111      Time:     In response to an operator down command.
 4112 
 4113      Meaning:  The  time  arguments  of  a  down  command must be
 4114                specified in 4-digit time  or some form acceptable
 4115                to convert_date_to_binary_.  No  action was taken.
 4116                If the second time argument is an invalid time, it
 4117                is considered  part of the message.   This message
 4118                is  also displayed if  the first time  argument is
 4119                not in the future.
 4120 
 4121      Action:   Enter a corrected command line.
 4122 
 4123 
 4124                [admin_.pl1]
 4125                admin_:   down:  Next  shutdown from  DATE_TIME to
 4126                DATE_TIME1 REASON
 4127 
 4128 
 4129      Stream:   as (severity 1)
 4130 
 4131 
 4132 admin_                          72            08/03/23     MR12.7^L
 4133 
 4134 
 4135      Time:     Response to an operator "down" command.
 4136 
 4137      Meaning:  This  message   tells  when  the   next  scheduled
 4138                shutdown is.
 4139 
 4140      Action:   No operator action is required.
 4141 
 4142 
 4143                [admin_.pl1]
 4144                admin_:  down:  No shutdown is scheduled.
 4145 
 4146 
 4147      Stream:   as (severity 1)
 4148 
 4149      Time:     In response to an operator down command.
 4150 
 4151      Meaning:  The operator  issued a down  0 command to  reset a
 4152                scheduled  automatic  shutdown  when  none  was in
 4153                effect.  No action was taken on the command.
 4154 
 4155      Action:   No operator action is required.
 4156 
 4157 
 4158                [admin_.pl1]
 4159                admin_:   down:   resetting  previous  shutdown at
 4160                MM/DD/YY HHMM.T
 4161 
 4162 
 4163      Stream:   as (severity 1)
 4164 
 4165      Time:     In response to an operator down command.
 4166 
 4167      Meaning:  A  second down  command has  been issued  before a
 4168                previously issued down  command has been executed.
 4169                The  new shutdown time  is honored instead  of the
 4170                previous one.
 4171 
 4172      Action:   No operator action is required.
 4173 
 4174 
 4175                [admin_.pl1]
 4176                admin_:  dump_fnp:  error:  unknown argument AAAA
 4177 
 4178 
 4179      Stream:   as (severity 1)
 4180 
 4181      Time:     In response to an operator dump_fnp command.
 4182 
 4183      Meaning:  An unknown argument, AAAA,  was encountered in the
 4184                dump_fnp  command  line.    This  is  an  obsolete
 4185                command.  No action was taken.
 4186 
 4187 
 4188 
 4189 
 4190 admin_                          73            08/03/23     MR12.7^L
 4191 
 4192 
 4193      Action:   Type "help  dump_mpx" for details of  the dump_mpx
 4194                command and try again.
 4195 
 4196 
 4197 
 4198                [admin_.pl1]
 4199                admin_:  dump_mpx:  error:  unknown argument AAAA
 4200 
 4201 
 4202      Stream:   as (severity 1)
 4203 
 4204      Time:     In response to an operator dump_mpx command.
 4205 
 4206      Meaning:  An unknown argument, AAAA,  was encountered in the
 4207                dump_mpx command line.  No action was taken.
 4208 
 4209      Action:   Type "help  dump_mpx" for details of  the dump_mpx
 4210                command and try again.
 4211 
 4212 
 4213 
 4214                [admin_.pl1]
 4215                admin_:  ERROR_MESSAGE SYSDIR>absentee_user_table
 4216 
 4217 
 4218      Stream:   as (severity 1)
 4219 
 4220      Time:     When operator entered abs command.
 4221 
 4222      Meaning:  The ERROR_MESSAGE gives reason  why system was not
 4223                able to find or  access the absentee_user_table in
 4224                the  SYSDIR directory.   Execution of  the command
 4225                was not completed.
 4226 
 4227      Action:   %inform
 4228 
 4229 
 4230                [admin_.pl1]
 4231                admin_:  ERROR_MESSAGE SYSDIR>answer_table
 4232 
 4233 
 4234      Stream:   as (severity 2)
 4235 
 4236      Time:     In  response  to  operator  commands  that require
 4237                access to the system answer_table.
 4238 
 4239      Meaning:  The ERROR_MESSAGE gives reason  why system was not
 4240                able  to find  or access  the answer_table  in the
 4241                SYSDIR  directory.  Execution  of the  command was
 4242                not completed.
 4243 
 4244      Action:   Contact the system programming staff.
 4245 
 4246 
 4247 
 4248 admin_                          74            08/03/23     MR12.7^L
 4249 
 4250 
 4251 
 4252 
 4253                [admin_.pl1]
 4254                admin_:  ERROR_MESSAGE SYSDIR>cdt
 4255 
 4256 
 4257      Stream:   as (severity 2)
 4258 
 4259      Time:     In  response  to  operator  commands  that require
 4260                access to the system cdt.
 4261 
 4262      Meaning:  The ERROR_MESSAGE gives reason  why system was not
 4263                able  to find  or access   the cdt  in the  SYSDIR
 4264                directory.   Execution  of  the  command  was  not
 4265                completed.
 4266 
 4267      Action:   Contact the system programming staff.
 4268 
 4269 
 4270                [admin_.pl1]
 4271                admin_:  ERROR_MESSAGE SYSDIR>installation_parms
 4272 
 4273 
 4274      Stream:   as (severity 2)
 4275 
 4276      Time:     In  response  to  operator  commands  that require
 4277                access to the system installation_parms.
 4278 
 4279      Meaning:  The ERROR_MESSAGE gives reason  why system was not
 4280                able to  find or access the  installation_parms in
 4281                the  SYSDIR directory.   Execution of  the command
 4282                was not completed.
 4283 
 4284      Action:   Contact the system programming staff.
 4285 
 4286 
 4287                [admin_.pl1]
 4288                admin_:  ERROR_MESSAGE SYSDIR>whotab
 4289 
 4290 
 4291      Stream:   as (severity 2)
 4292 
 4293      Time:     In  response  to  operator  commands  that require
 4294                access to the system whotab.
 4295 
 4296      Meaning:  The ERROR_MESSAGE gives reason  why system was not
 4297                able to  find or access  the whotab in  the SYSDIR
 4298                directory.   Execution  of  the  command  was  not
 4299                completed.
 4300 
 4301      Action:   Contact the system programming staff.
 4302 
 4303 
 4304 
 4305 
 4306 admin_                          75            08/03/23     MR12.7^L
 4307 
 4308 
 4309 
 4310 
 4311                [admin_.pl1]
 4312                admin_:  fdump_fnp:  error:  unknown argument AAAA
 4313 
 4314 
 4315      Stream:   as (severity 1)
 4316 
 4317      Time:     In response to an operator fdump_fnp command.
 4318 
 4319      Meaning:  An unknown argument, AAAA,  was encountered in the
 4320                fdump_fnp command.   This is an  obsolete command.
 4321                No action was taken.
 4322 
 4323      Action:   Type "help  dump_mpx" for details of  the dump_mpx
 4324                command and try again.
 4325 
 4326 
 4327 
 4328                [admin_.pl1]
 4329                admin_:  load_fnp:  unknown argument AAAA
 4330 
 4331 
 4332      Stream:   as (severity 1)
 4333 
 4334      Time:     In response to an operator load_fnp command.
 4335 
 4336      Meaning:  An unknown argument, AAAA,  was encountered in the
 4337                load_fnp  command  line.    This  is  an  obsolete
 4338                command.  No action was taken.
 4339 
 4340      Action:   Type "help  load_mpx" for details of  the load_mpx
 4341                command and try again.
 4342 
 4343 
 4344 
 4345                [admin_.pl1]
 4346                admin_:  load_mpx:  error:  unknown argument AAAA
 4347 
 4348 
 4349      Stream:   as (severity 1)
 4350 
 4351      Time:     In response to an operator load_mpx command.
 4352 
 4353      Meaning:  An unknown argument, AAAA,  was encountered in the
 4354                load_mpx command line.  No action was taken.
 4355 
 4356      Action:   Type "help  load_mpx" for details of  the load_mpx
 4357                command and try again.
 4358 
 4359 
 4360 
 4361 
 4362 
 4363 
 4364 admin_                          76            08/03/23     MR12.7^L
 4365 
 4366 
 4367 
 4368 
 4369                [admin_.pl1]
 4370                admin_:  load_mpx:  error:  unknown argument AAAA
 4371 
 4372 
 4373      Stream:   as (severity 1)
 4374 
 4375      Time:     In response to an operator load_mpx command.
 4376 
 4377      Meaning:  An unknown argument, AAAA,  was encountered in the
 4378                load_mpx command line.  No action was taken.
 4379 
 4380      Action:   Type  "help  load_mpx"  for  use  of  the load_mpx
 4381                command and try again.
 4382 
 4383 
 4384                [admin_.pl1]
 4385                admin_:  log:  MESSAGE
 4386 
 4387 
 4388      Stream:   as (severity 0)
 4389 
 4390      Time:     While system is running.
 4391 
 4392      Meaning:  The log command simply enters its arguments in the
 4393                system log.  It is  occasionally used by operators
 4394                and system programmers to record events.
 4395 
 4396      Action:   No operator action is required.
 4397 
 4398 
 4399                [admin_.pl1]
 4400                admin_:   login:   Entry  not  found.   No  MC ACS
 4401                segment for the source SSSS.
 4402 
 4403 
 4404      Stream:   as (severity 1)
 4405 
 4406      Time:     In response to operator login command.
 4407 
 4408      Meaning:  An MC  ACS was not found  in >sc1>mc_acs directory
 4409                for the source identifier, SSSS.
 4410 
 4411      Action:   Contact the system programming staff.
 4412 
 4413 
 4414                [admin_.pl1]
 4415                admin_:     login:     error:     Usage:     login
 4416                Person.Project SOURCE {-control_args}
 4417 
 4418 
 4419      Stream:   as (severity 1)
 4420 
 4421 
 4422 admin_                          77            08/03/23     MR12.7^L
 4423 
 4424 
 4425      Time:     In  response  to  operator  login  command with no
 4426                arguments.
 4427 
 4428      Meaning:  Informative  message to   operator when  the login
 4429                command was entered without arguments.
 4430 
 4431      Action:   Also  type  "help  login"  for  further details of
 4432                command line syntax.
 4433 
 4434 
 4435                [admin_.pl1]
 4436                admin_:   login:   ERROR_TABLE_MESSAGE  Login  not
 4437                permitted for message coordinator source SSSS.
 4438 
 4439 
 4440      Stream:   as (severity 1)
 4441 
 4442      Time:     In response to operator login command.
 4443 
 4444      Meaning:  The  error identified  by ERROR_TABLE_MESSAGE  was
 4445                encountered  attempting  to  check  the  access to
 4446                login the daemon whose source identifier is SSSS.
 4447 
 4448 
 4449 
 4450                [admin_.pl1]
 4451                admin_:     logout:    error:     Usage:    logout
 4452                Person.Project {SOURCE}
 4453 
 4454 
 4455      Stream:   as (severity 1)
 4456 
 4457      Time:     In  response  to   operator  logout  command  when
 4458                entered without arguments.
 4459 
 4460      Meaning:  Informative message indicating usage of the logout
 4461                command.
 4462 
 4463      Action:   Type "help logout" for  further details of command
 4464                usage.
 4465 
 4466 
 4467                [admin_.pl1]
 4468                admin_:  maxu:  (MMMM):  UUUU (DDDD normal users)
 4469 
 4470 
 4471 
 4472      Stream:   as (severity 1)
 4473 
 4474      Time:     When operator entered "maxu" command.
 4475 
 4476      Meaning:  This  is  an  informative  message  indicating the
 4477                current  values manipulated  by the  maxu command.
 4478 
 4479 
 4480 admin_                          78            08/03/23     MR12.7^L
 4481 
 4482 
 4483                MMMM is the mode, "auto"  or "level".  UUUU is the
 4484                load units  in tenths.  DDDD is the  load units in
 4485                whole numbers.
 4486 
 4487      Action:   No operator action is required.
 4488 
 4489 
 4490                [admin_.pl1]
 4491                admin_:  maxu:   Warning:  maxunits are  in tenths
 4492                of load units.
 4493                You just set maxu to UUUU, or DDDD normal users.
 4494 
 4495 
 4496 
 4497      Stream:   as (severity 1)
 4498 
 4499      Time:     When  operator entered  a maxu  command line  that
 4500                specified < 200 load units or 20 normal users.
 4501 
 4502      Meaning:  This message is a warning  to the operator that he
 4503                may have made a mistake  in setting the load units
 4504                of the  system.  A normal system is  not likely to
 4505                set its maximum load units to less than 200.
 4506 
 4507      Action:   Take corrective  action (reenter the  command with
 4508                corrected arguments).
 4509 
 4510 
 4511 
 4512                [admin_.pl1]
 4513                admin_:  maxunits:  error:   XXX invalid value for
 4514                maxunits
 4515 
 4516 
 4517      Stream:   as (severity 1)
 4518 
 4519      Time:     In response to an operator maxunits command.
 4520 
 4521      Meaning:  The  argument of  the maxunits  command was  not a
 4522                number, or  was zero, or negative.   No action was
 4523                taken.
 4524 
 4525      Action:   Enter a corrected command line.
 4526 
 4527 
 4528                [admin_.pl1]
 4529                admin_:  rcp:  error:  unknown rcp command RRRR
 4530 
 4531 
 4532      Stream:   as (severity 1)
 4533 
 4534      Time:     In response to an operator rcp command.
 4535 
 4536 
 4537 
 4538 admin_                          79            08/03/23     MR12.7^L
 4539 
 4540 
 4541      Meaning:  The operator  has entered an unknown  rcp operator
 4542                on the command line.
 4543 
 4544      Action:   Type "help rcp" for further details on rcp command
 4545                usage.
 4546 
 4547 
 4548                [admin_.pl1]
 4549                admin_:  shift:  error:  CCCC invalid clock time.
 4550 
 4551 
 4552      Stream:   as (severity 1)
 4553 
 4554      Time:     In response to an operator shift command.
 4555 
 4556      Meaning:  The time  argument of the  shift command is  not a
 4557                valid      clock      time      acceptable      to
 4558                convert_date_to_binary_.
 4559 
 4560      Action:   Enter a corrected command line.
 4561 
 4562 
 4563                [admin_.pl1]
 4564                admin_:   shift:  error:   CCCC is  not within the
 4565                next week.
 4566 
 4567 
 4568      Stream:   as (severity 1)
 4569 
 4570      Time:     In response to an operator shift command.
 4571 
 4572      Meaning:  The  time  argument  of  the  shift command cannot
 4573                specify a  time stamp that  is over a  week in the
 4574                future.
 4575 
 4576      Action:   Enter a corrected command line.
 4577 
 4578 
 4579                [admin_.pl1]
 4580                admin_:  shift:  error:  XXXX is not a legal shift
 4581                number.
 4582 
 4583 
 4584      Stream:   as (severity 1)
 4585 
 4586      Time:     In response to an operator shift command.
 4587 
 4588      Meaning:  A shift  argument to the  shift command was  not a
 4589                valid decimal number between 1 and 6 inclusive.
 4590 
 4591      Action:   Enter a corrected command line.
 4592 
 4593 
 4594 
 4595 
 4596 admin_                          80            08/03/23     MR12.7^L
 4597 
 4598 
 4599 
 4600 
 4601                [admin_.pl1]
 4602                admin_:  shift:  N until DATE_TIME
 4603 
 4604 
 4605      Stream:   as (severity 1)
 4606 
 4607      Time:     response to an operator "shift" command.
 4608 
 4609      Meaning:  The  operator has  issued the  shift command.   If
 4610                issued  with no  arguments this  command types the
 4611                current  setting.  If  issued with  arguments, the
 4612                command changes the shift and types the new value.
 4613 
 4614      Action:   No operator action is required.
 4615 
 4616 
 4617                [admin_.pl1]
 4618                admin_:   shutdown_mpx:  error:   unknown argument
 4619                AAAA
 4620 
 4621 
 4622      Stream:   as (severity 1)
 4623 
 4624      Time:     In response to an operator shutdown_mpx command.
 4625 
 4626      Meaning:  An unknown argument, AAAA,  was encountered in the
 4627                shutdown_mpx command line.  No action was taken.
 4628 
 4629      Action:   The  shutdown_mpx  command  is  the  same  as  the
 4630                dump_mpx command  except that no dump  is created.
 4631                Type "help dump_mpx" for command usage details and
 4632                try again.
 4633 
 4634 
 4635 
 4636                [admin_.pl1]
 4637                admin_:  stop:   All users are out.   You may shut
 4638                down.
 4639 
 4640 
 4641      Stream:   as (severity 1)
 4642 
 4643      Time:     System shutdown.
 4644 
 4645      Meaning:  This is  the response to  the stop command  if all
 4646                users have been logged out.  This message provides
 4647                a  quick  check  of  whether  all  users have been
 4648                bumped since  it does not adversely  affect system
 4649                operation to issue the stop command repeatedly.
 4650 
 4651      Action:   Proceed with the shutdown.
 4652 
 4653 
 4654 admin_                          81            08/03/23     MR12.7^L
 4655 
 4656 
 4657 
 4658 
 4659                [admin_.pl1]
 4660                admin_:   stop:  all  users have  been given  XXXX
 4661                minutes to logout
 4662 
 4663 
 4664      Stream:   as (severity 1)
 4665 
 4666      Time:     System shutdown.
 4667 
 4668      Meaning:  A  stop command,  either manual  or automatic, has
 4669                been initiated.   All users have been  warned that
 4670                they  have XXXX minutes  to finish up  and logout.
 4671                After  XXXX  minutes,  all  users  will  be bumped
 4672                except those with the nobump attribute.  The login
 4673                word has  been set so  that no more  users may log
 4674                in.  To  cancel this shutdown, issue  a word login
 4675                command and an unbump * * command.
 4676 
 4677      Action:   No operator action is required.
 4678 
 4679 
 4680                [admin_.pl1]
 4681                admin_:  stop:  auto abs stop
 4682 
 4683 
 4684      Stream:   as (severity 1)
 4685 
 4686      Time:     While system is running.
 4687 
 4688      Meaning:  It is  30 minutes before an automatic  stop, so an
 4689                automatic abs stop command  is being issued.  This
 4690                is the  result of a previous  down command.  Refer
 4691                also to the stop command description.
 4692 
 4693      Action:   No operator action is required.
 4694 
 4695 
 4696                [admin_.pl1]
 4697                admin_:  stop:  Automatic shutdown
 4698 
 4699 
 4700      Stream:   as (severity 1)
 4701 
 4702      Time:     System shutdown.
 4703 
 4704      Meaning:  A  down command  issued earlier  has taken effect.
 4705                An automatic stop command  is executed.  All users
 4706                are bumped in three minutes.
 4707 
 4708      Action:   Prepare to shut down the system.
 4709 
 4710 
 4711 
 4712 admin_                          82            08/03/23     MR12.7^L
 4713 
 4714 
 4715 
 4716 
 4717                [admin_.pl1]
 4718                admin_:  stop:   error:  no arguments  are allowed
 4719                for "stop"
 4720 
 4721 
 4722      Stream:   as (severity 1)
 4723 
 4724      Time:     In response to an operator stop command.
 4725 
 4726      Meaning:  The  operator has  given an  argument to  the stop
 4727                command.  No arguments are allowed.  No action was
 4728                taken.
 4729 
 4730      Action:   If abs stop was meant, type that command.  If stop
 4731                was  meant, type  that command  instead.  If "down
 4732                ...."  was meant, type in that command.
 4733 
 4734 
 4735 
 4736                [admin_.pl1]
 4737                admin_:  stop:   There were no active  users to be
 4738                bumped.
 4739 
 4740 
 4741      Stream:   as (severity 1)
 4742 
 4743      Time:     System shutdown.
 4744 
 4745      Meaning:  The  system did  not find  any active  users to be
 4746                bumped.
 4747 
 4748      Action:   No operator action is required.
 4749 
 4750 
 4751                [admin_.pl1]
 4752                admin_:  stop_fnp:  error:  unknown argument AAAA
 4753 
 4754 
 4755      Stream:   as (severity 1)
 4756 
 4757      Time:     In response to an operator stop_mpx command.
 4758 
 4759      Meaning:  An unknown argument, AAAA,  was encountered in the
 4760                stop_fnp  command  line.    This  is  an  obsolete
 4761                command.  No action was taken.
 4762 
 4763      Action:   Type "help  stop_mpx" for details of  the stop_mpx
 4764                command and try again.
 4765 
 4766 
 4767 
 4768 
 4769 
 4770 admin_                          83            08/03/23     MR12.7^L
 4771 
 4772 
 4773 
 4774 
 4775                [admin_.pl1]
 4776                admin_:  stop_mpx:  error:  unknown argument AAAA
 4777 
 4778 
 4779      Stream:   as (severity 1)
 4780 
 4781      Time:     In response to an operator stop_mpx command.
 4782 
 4783      Meaning:  An unknown argument, AAAA,  was encountered in the
 4784                stop_mpx command line.  No action was taken.
 4785 
 4786      Action:   Type "help  stop_mpx" for details of  the stop_mpx
 4787                command and try again.
 4788 
 4789 
 4790 
 4791                [admin_.pl1]
 4792                admin_:      warn:     error:      Usage:     warn
 4793                Person.Project MESSAGE
 4794 
 4795 
 4796      Stream:   as (severity 1)
 4797 
 4798      Time:     In  response to  an operator  warn command without
 4799                any arguments.
 4800 
 4801      Meaning:  Informative message  indicating usage of  the warn
 4802                command.
 4803 
 4804      Action:   Also,  type "help warn"  for more details  on warn
 4805                command usage.
 4806 
 4807 
 4808                [admin_.pl1]
 4809                admin_:  warn:  NAME.PROJ has "no_warning"
 4810 
 4811 
 4812      Stream:   as (severity 1)
 4813 
 4814      Time:     Response to operator warn command.
 4815 
 4816      Meaning:  This  is the  response to  the command  "warn NAME
 4817                PROJ  Message..."  if  the user  has specified the
 4818                -no_warning argument at login.  The message is not
 4819                sent to the user.
 4820 
 4821      Action:   Attempt to contact the user by other means.
 4822 
 4823 
 4824                [admin_.pl1]
 4825                admin_:  warn:  NAME.PROJ not found.
 4826 
 4827 
 4828 admin_                          84            08/03/23     MR12.7^L
 4829 
 4830 
 4831      Stream:   as (severity 1)
 4832 
 4833      Time:     In response to an operator warn command.
 4834 
 4835      Meaning:  The  warn  command  was  issued  for a nonexistent
 4836                user.  No action was taken.
 4837 
 4838      Action:   The  user is  probably not  logged in.   Check the
 4839                spelling  of the   name.Enter a  corrected command
 4840                line.
 4841 
 4842 
 4843 
 4844                [admin_.pl1]
 4845                admin_:   warn:   USER.PROJ  not  connected  to  a
 4846                channel
 4847 
 4848 
 4849      Stream:   as (sevreity1)
 4850 
 4851      Time:     Response to operator warn command.
 4852 
 4853      Meaning:  This  is the  response to  the command  "warn NAME
 4854                PROJ Message" if the  pointer to the channel table
 4855                entry in  the user table entry for  the named user
 4856                (ute.cdtep) is not set (null).  The message cannot
 4857                be sent to the user.
 4858 
 4859      Action:   Attempt to contact the user by other means.
 4860 
 4861 
 4862                [admin_.pl1]
 4863                admin_:   word:   length  of  login-word  must not
 4864                exceed 8 characters
 4865 
 4866 
 4867      Stream:   as (severity 1)
 4868 
 4869      Time:     In response to an operator word command.
 4870 
 4871      Meaning:  The operator tried to set  the login word with the
 4872                word command but the  first argument was too long.
 4873                No action was taken on the command.
 4874 
 4875      Action:   Enter a corrected command line.
 4876 
 4877 
 4878                [admin_.pl1]
 4879                admin_:  word:  message  truncated; maximum length
 4880                is CCCC characters
 4881 
 4882 
 4883      Stream:   as (severity 1)
 4884 
 4885 
 4886 admin_                          85            08/03/23     MR12.7^L
 4887 
 4888 
 4889      Time:     In response to an operator word command.
 4890 
 4891      Meaning:  The operator issued the  command "word XXXX TEXT".
 4892                The message TEXT was too long to fit in the dialup
 4893                message buffer.  The login  word has been changed,
 4894                and the  dialup message has been set  to the first
 4895                CCCC characters of the given message.
 4896 
 4897      Action:   Reword   the    message   to   fit    within   the
 4898                CCCC-character limit, and retype the command.
 4899 
 4900 
 4901 
 4902                [admin_.pl1]
 4903                admin_:  word:  TYPE message:  TEXT
 4904 
 4905 
 4906      Stream:   as (severity 1)
 4907 
 4908      Time:     In response to an operator word command.
 4909 
 4910      Meaning:  The operator issued the  command "word XXXX TEXT".
 4911                The  login word  was set  to XXXX,  and a  special
 4912                buffer was loaded with the message TEXT so that it
 4913                is typed  out whenever a user dials  up.  The type
 4914                of  system session is  TYPE; this may  be special,
 4915                normal, or shutdown.
 4916 
 4917      Action:   Check the message for accuracy.
 4918 
 4919 
 4920                [admin_.pl1]
 4921                admin_:  word:  XXXX is a reserved word.
 4922 
 4923 
 4924      Stream:   as (severity 1)
 4925 
 4926      Time:     In response to an operator word command.
 4927 
 4928      Meaning:  The  operator attempted  to set  the system  login
 4929                word  to enter,  enterp, e,  ep, dial,  or d.   No
 4930                action was taken.
 4931 
 4932      Action:   Pick another word and type it in.
 4933 
 4934 
 4935                [admin_.pl1]
 4936                admin_:  word:  XXXX; TYPE message:  TEXT
 4937 
 4938 
 4939      Stream:   as (severity 1)
 4940 
 4941      Time:     In response to an operator word command.
 4942 
 4943 
 4944 admin_                          86            08/03/23     MR12.7^L
 4945 
 4946 
 4947      Meaning:  The  operator  issued  the  word  command  with no
 4948                arguments, and the current values were typed.  The
 4949                login word  is XXXX, the message is  TEXT, and the
 4950                type of session is TYPE.  The TEXT is displayed as
 4951                the   first  line   of  the   greeting  banner  to
 4952                interactive users making the  banner 3 lines long.
 4953                If TEXT is "" (NO  MESSAGE), then nothing is added
 4954                to the normal 2 line greeting banner.
 4955 
 4956      Action:   Check the word, type, and message for accuracy.
 4957 
 4958 
 4959                [salv_dir_checker_.pl1]
 4960                ADUIT  (salv_dir_checker_):  GRANTED  modification
 4961                of security out-of-service ADDED_INFO
 4962 
 4963 
 4964      Stream:   $access_audit
 4965 
 4966      Time:     Salvaging
 4967 
 4968      Meaning:  The security-out-of-service switch has been set on
 4969                a directory  because of an AIM  error.  The access
 4970                class  of a branch  was not equal  to that of  the
 4971                containing directory,  or the access class  in the
 4972                directory's  branch was  not equal  to the  access
 4973                class stored in its header.
 4974 
 4975      Action:   Contact the system programming staff._ssa
 4976 
 4977 
 4978                [announce_chwm.pl1]
 4979                announce_chwm:  WWW pages wired, UUU pages usable.
 4980 
 4981 
 4982      Stream:   BOS Typewriter.
 4983 
 4984      Time:     System Intialization.
 4985 
 4986      Meaning:  This message is produced when the CHWM paramter is
 4987                specified  on the  PARM CONFIG  card.  WWW  is the
 4988                number of  wired pages in collection  one.  UUU is
 4989                the  number  of   available  main  memory  frames,
 4990                including those  occupied by wired pages,  but not
 4991                those occupied by unpaged segments.
 4992 
 4993      Action:   No operator action is required.
 4994 
 4995 
 4996                [announce_chwm.pl1]
 4997                announce_chwm:  WWW.  pages used of XXX.  in wired
 4998                environment.
 4999 
 5000 
 5001 
 5002 announce_chwm                   87            08/03/23     MR12.7^L
 5003 
 5004 
 5005      Stream:   BOS Typewriter.
 5006 
 5007      Time:     System Intialization.
 5008 
 5009      Meaning:  This message  is produced when the  CHWM parameter
 5010                is specified on the PARM  CONFIG card.  WWW is the
 5011                number of pages of memory which remain unused (out
 5012                of  a maximum  of XXX)  after all  the segments in
 5013                collection  one  have  been  loaded,  and  all the
 5014                segments constructed  by collection one  have been
 5015                created.
 5016 
 5017      Action:   No operator action is required.
 5018 
 5019 
 5020                [announce_chwm.pl1]
 5021                announce_chwm:   WWW.   words  used  of  XXX.   in
 5022                int_unpaged_page_tables.
 5023 
 5024 
 5025      Stream:   BOS Typewriter.
 5026 
 5027      Time:     System Intialization.
 5028 
 5029      Meaning:  This message  is produced when the  CHWM parameter
 5030                is specified on the PARM  CONFIG card.  WWW is the
 5031                number  of  words  of  the  XXX  word long segment
 5032                int_unpaged_page_tables  used to hold  page tables
 5033                for temporary collection 1 segments.
 5034 
 5035      Action:   No operator action is required.
 5036 
 5037 
 5038                [announce_chwm.pl1]
 5039                announce_chwm:   WWW.   words  used  of  XXX.   in
 5040                unpaged_page_tables.
 5041 
 5042 
 5043      Stream:   BOS Typewriter.
 5044 
 5045      Time:     System Intialization.
 5046 
 5047      Meaning:  This message  is produced when the  CHWM parameter
 5048                is specified on the PARM  CONFIG card.  WWW is the
 5049                number  of  words  of  the  XXX  word long segment
 5050                unpaged_page_tables used  to hold page  tables for
 5051                permanent "unpaged" segments.
 5052 
 5053      Action:   No operator action is required.
 5054 
 5055 
 5056                [append.pl1]
 5057 
 5058 
 5059 
 5060 append                          88            08/03/23     MR12.7^L
 5061 
 5062 
 5063                append:    error  from   delete_vtoce  for   PATH:
 5064                ERROR_MESSAGE
 5065 
 5066 
 5067      Stream:   Logged in SYSERR log.
 5068 
 5069      Time:     While system is running.
 5070 
 5071      Meaning:  While  deleting  a  VTOC  entry  to  clean  up  an
 5072                unsuccessful attempt  to create an  branch, append
 5073                got an error.  This indicates a logic error in the
 5074                supervisor, or CPU or memory hardware problems.
 5075 
 5076      Action:   Note for system programmer action.
 5077 
 5078 
 5079                [append.pl1]
 5080                append:  error from hash$out for PATH:  ERROR_CODE
 5081 
 5082 
 5083      Stream:   Logged in SYSERR log.
 5084 
 5085      Time:     While system is running.
 5086 
 5087      Meaning:  While removing a name  to clean up an unsuccessful
 5088                attempt to  create a branch, append  got an error.
 5089                This indicates a logic error in the supervisor, or
 5090                CPU or memory hardware problems.
 5091 
 5092      Action:   Note for system programmer action.
 5093 
 5094 
 5095                [append.pl1]
 5096                append:    error  from   makeunknown_  for   PATH:
 5097                ERROR_CODE
 5098 
 5099 
 5100      Stream:   Logged in SYSERR log.
 5101 
 5102      Time:     While system is running.
 5103 
 5104      Meaning:  Append made  the new directory PATH  unknown after
 5105                initializing  its  header.    While  doing  so  it
 5106                encountered  an  error.   This  indicates  a logic
 5107                error in the supervisor, or CPU or memory hardware
 5108                problems.
 5109 
 5110      Action:   Note for system programmer action.
 5111 
 5112 
 5113                [append.pl1]
 5114                append:   makeunknown_  err  after  quota  err for
 5115                PATH:  ERROR_CODE
 5116 
 5117 
 5118 append                          89            08/03/23     MR12.7^L
 5119 
 5120 
 5121      Stream:   Logged in SYSERR log.
 5122 
 5123      Time:     While system is running.
 5124 
 5125      Meaning:  During  the creation  of a  new directory,  append
 5126                encountered an error moving quota.  While cleaning
 5127                up   from   this   error   a   further  error  was
 5128                encountered.   The  system  continues  to operate.
 5129                This indicates a logic error in the supervisor, or
 5130                CPU or memory hardware problems.
 5131 
 5132      Action:   Note for system programmer action.
 5133 
 5134 
 5135                [as_add_admin_acl_.pl1]
 5136                as_add_admin_acl_:  ERROR_MESSAGE.   Could not add
 5137                PGID to ACL of PATH.
 5138 
 5139 
 5140      Stream:   as (severity2)
 5141 
 5142      Time:     Answering  Service  initialization,  or  while the
 5143                system is running.
 5144 
 5145      Meaning:  An  error  occurred  while  trying  to rebuild the
 5146                access   control  list    (ACL)  on   PATH  where:
 5147                ERROR_MESSAGE is an error_table_ message
 5148                PGID is a process group id
 5149                PATH is a full pathname
 5150 
 5151      Action:   Manually   give  PGID   read  access   (or  status
 5152                permission) to PATH.
 5153 
 5154 
 5155                [as_add_admin_acl_.pl1]
 5156                as_add_admin_acl_:  ERROR_MESSAGE.   Could not add
 5157                to ACL of PATH.
 5158 
 5159 
 5160      Stream:   as (severity2)
 5161 
 5162      Time:     Answering  Service  initialization,  or  while the
 5163                system is running.
 5164 
 5165      Meaning:  Some  fatal error   occurred while  rebuilding the
 5166                access control list  (ACL) of PATH.  ERROR_MESSAGE
 5167                is  an error_table_ message  and PATH is  the full
 5168                pathname of a segment or a directory.
 5169 
 5170      Action:   Contact   the  system   programming  staff.    The
 5171                operation that caused the error must be determined
 5172                and the operation repeated after correction.
 5173 
 5174 
 5175 
 5176 as_add_admin_acl_               90            08/03/23     MR12.7^L
 5177 
 5178 
 5179 
 5180 
 5181                [as_dump_.pl1]
 5182                as_dump_:   Answering  service   dump  created  in
 5183                segment >sc1>asdump.-.MM/DD/YY-HHMM
 5184 
 5185 
 5186      Stream:   as (severity1)
 5187 
 5188      Time:     While system is running.
 5189 
 5190      Meaning:  Some program  has encountered an  unexpected fault
 5191                and  has  called  for  a  dump  of  the  Answering
 5192                Service.  This segment is automatically dprinted.
 5193 
 5194      Action:   No operator action is required.
 5195 
 5196 
 5197                [as_dump_.pl1]
 5198                as_dump_:  Cannot attach I/O switch.  No dump NAME
 5199 
 5200 
 5201      Stream:   as (severity2)
 5202 
 5203      Time:     While system is running.
 5204 
 5205      Meaning:  An  error  occurred  while  dumping.   No dump was
 5206                taken.
 5207 
 5208      Action:   Contact the system programming staff.
 5209 
 5210 
 5211                [as_dump_.pl1]
 5212                as_dump_:   Cannot  obtain  quota,  dump  aborted.
 5213                NAME
 5214 
 5215 
 5216      Stream:   as (severity2)
 5217 
 5218      Time:     While system is running.
 5219 
 5220      Meaning:  An  error  occurred  while  dumping.   No dump was
 5221                taken.
 5222 
 5223      Action:   Contact the system programming staff.
 5224 
 5225 
 5226                [as_dump_.pl1]
 5227                as_dump_:  CONDITION while dumping.  Dump aborted
 5228 
 5229 
 5230      Stream:   as (severity1)
 5231 
 5232 
 5233 
 5234 as_dump_                        91            08/03/23     MR12.7^L
 5235 
 5236 
 5237      Time:     While system is running.
 5238 
 5239      Meaning:  During the attempt to perform an Answering Service
 5240                dump, some unexpected fault occurred.  The dump is
 5241                stopped and the system tries to continue.
 5242 
 5243      Action:   Notify the system programming staff.
 5244 
 5245 
 5246                [as_dump_.pl1]
 5247                as_dump_:     ERROR_MESSAGE.      Cannot    attach
 5248                as_dump_stream_    to     FILENAME.     No    dump
 5249                asdump.MM/DD/YY-HHMM
 5250 
 5251 
 5252      Stream:   as (severity1)
 5253 
 5254      Time:     While system is running.
 5255 
 5256      Meaning:  The  Answering  Service  dump  program  could  not
 5257                attach a file for the Answering Service dump.  The
 5258                dump will abort, and the system will continue.
 5259 
 5260      Action:   Contact the system programming staff.
 5261 
 5262 
 5263                [as_dump_.pl1]
 5264                as_dump_:  ERROR_MESSAGE.  Cannot  obtain quota of
 5265                >sc1, dump aborted.  DUMPID
 5266 
 5267 
 5268      Stream:   as (severity2)
 5269 
 5270      Time:     While system is running.
 5271 
 5272      Meaning:  An  error  occurred  while  dumping.   No dump was
 5273                taken.
 5274 
 5275      Action:   Contact the system programming staff.
 5276 
 5277 
 5278                [as_dump_.pl1]
 5279                as_dump_:   Message  coordinator  dump  created in
 5280                segment >sc1>asdump.-.MM/DD/YY-HHMM
 5281 
 5282 
 5283      Stream:   BOS Typewriter.
 5284 
 5285      Time:     While system is running.
 5286 
 5287      Meaning:  Some program  has encountered an  unexpected fault
 5288                and  has   called  for  a  dump   of  the  message
 5289 
 5290 
 5291 
 5292 as_dump_                        92            08/03/23     MR12.7^L
 5293 
 5294 
 5295                coordinator.    This   segment   is  automatically
 5296                dprinted.
 5297 
 5298      Action:   No operator action is required.
 5299 
 5300 
 5301                [as_dump_.pl1]
 5302                as_dump_:  Out of room for dump DUMPID
 5303 
 5304 
 5305      Stream:   as (severity2)
 5306 
 5307      Time:     While system is running.
 5308 
 5309      Meaning:  An  error  occurred  while  dumping.   No dump was
 5310                taken.
 5311 
 5312      Action:   Contact the system programming staff.
 5313 
 5314 
 5315                [as_hasp_mpx_.pl1]
 5316                as_hasp_mpx_:   Crash  signalled  for  multiplexer
 5317                TTY.
 5318 
 5319 
 5320      Stream:   as (severity 1)
 5321 
 5322      Time:     While system is running.
 5323 
 5324      Meaning:  The physical  connection for the  HASP multiplexer
 5325                on channel  TTY has been broken  either because of
 5326                an  error or  or because   of a  request from  the
 5327                remote host/workstation.
 5328 
 5329      Action:   Check  the console  for a  message concerning this
 5330                channel  from  hasp_mpx.   If  such  a  message is
 5331                found,  refer  to  its  documentation  for further
 5332                action; otherwise, the remote host/workstation has
 5333                requested  termination of  the connection  and the
 5334                I/O  daemons using  this channel  should be logged
 5335                out.
 5336 
 5337 
 5338 
 5339                [as_hasp_mpx_.pl1]
 5340                as_hasp_mpx_:  Duplicate subchannel  name NAME for
 5341                HASP multiplexer TTY.
 5342 
 5343 
 5344      Stream:   as (severity 1)
 5345 
 5346      Time:     In  response  to  a  load_mpx  operator command or
 5347                during system initialization.
 5348 
 5349 
 5350 as_hasp_mpx_                    93            08/03/23     MR12.7^L
 5351 
 5352 
 5353      Meaning:  The  same  name  has  been  used  for  two or more
 5354                subchannels  of the   HASP multiplexer  on channel
 5355                TTY.
 5356 
 5357      Action:   Correct  the CDT  entry for  this multiplexer  and
 5358                reload it.
 5359 
 5360 
 5361                [as_hasp_mpx_.pl1]
 5362                as_hasp_mpx_:     ERROR_MESSAGE.     Cannot    get
 5363                additional  info  from   terminal  type  NAME  for
 5364                multiplexer TTY.
 5365 
 5366 
 5367      Stream:   as (severity 1)
 5368 
 5369      Time:     In  response  to  a  load_mpx  operator command or
 5370                during system initialization.
 5371 
 5372      Meaning:  The terminal type specified  by NAME was not given
 5373                an additional_info string in  its TTT entry.  This
 5374                string  is required  to specify  the configuration
 5375                parameters  for the   HASP multiplexer  on channel
 5376                TTY.
 5377 
 5378      Action:   Check both the CDT  entry for this multiplexer and
 5379                the TTT  entry for the terminal  type.  Either the
 5380                wrong  terminal type was  specified in the  CDT or
 5381                the  terminal  type's  definition  is  incomplete.
 5382                Correct whichever table is in error and reload the
 5383                multiplexer.
 5384 
 5385 
 5386 
 5387                [as_hasp_mpx_.pl1]
 5388                as_hasp_mpx_:    ERROR_MESSAGE.   Creating   event
 5389                channel for multiplexer TTY.
 5390 
 5391 
 5392      Stream:   as (severity 1)
 5393 
 5394      Time:     In  response  to  a  load_mpx  operator command or
 5395                during system initialization.
 5396 
 5397      Meaning:  A system error arose  during the initialization of
 5398                the HASP multiplexer on channel TTY.
 5399 
 5400      Action:   Contact the system programming staff.
 5401 
 5402 
 5403                [as_hasp_mpx_.pl1]
 5404                as_hasp_mpx_:    Invalid  PARM   specification  in
 5405                terminal type NAME for multiplexer TTY.
 5406 
 5407 
 5408 as_hasp_mpx_                    94            08/03/23     MR12.7^L
 5409 
 5410 
 5411      Stream:   as (severity 1)
 5412 
 5413      Time:     In  response  to  a  load_mpx  operator command or
 5414                during system initialization.
 5415 
 5416      Meaning:  The   value   specified   for   the  configuration
 5417                parameter  PARM in  the additional  info string of
 5418                the   terminal  type   NAME  used   for  the  HASP
 5419                multiplexer  on channel  TTY is  not acceptable to
 5420                the system.
 5421 
 5422      Action:   Correct the value of the  parameter in the TTT and
 5423                reload the multiplexer.
 5424 
 5425 
 5426                [as_hasp_mpx_.pl1]
 5427                as_hasp_mpx_:   Invalid subchannel  name NAME  for
 5428                HASP multiplexer TTY.
 5429 
 5430 
 5431      Stream:   as (severity 1)
 5432 
 5433      Time:     In  response  to  a  load_mpx  operator command or
 5434                during system initialization.
 5435 
 5436      Meaning:  The  name specified for  a subchannel of  the HASP
 5437                multiplexer on channel TTY does not conform to the
 5438                conventions  defined  in  MAM  Communications  for
 5439                naming such channels.
 5440 
 5441      Action:   Correct  the CDT  entry for  this multiplexer  and
 5442                reload it.
 5443 
 5444 
 5445                [as_hasp_mpx_.pl1]
 5446                as_hasp_mpx_:  Line type for hasp operator console
 5447                on  multiplexer   TTY  must  be   "HASP_OPR"  when
 5448                configured for login service.
 5449 
 5450 
 5451 
 5452      Stream:   as (severity 1)
 5453 
 5454      Time:     In  response  to  a  load_mpx  operator command or
 5455                during system initialization.
 5456 
 5457      Meaning:  The line type  must be set for HASP_OPR  on a hasp
 5458                operator console subchannel  when it is configured
 5459                for login service.
 5460 
 5461      Action:   Correct  the CDT  entry for  this multiplexer  and
 5462                reload it.
 5463 
 5464 
 5465 
 5466 as_hasp_mpx_                    95            08/03/23     MR12.7^L
 5467 
 5468 
 5469 
 5470 
 5471                [as_hasp_mpx_.pl1]
 5472                as_hasp_mpx_:  Load signalled for multiplexer TTY.
 5473 
 5474 
 5475      Stream:   as (severity 1)
 5476 
 5477      Time:     While system is running.
 5478 
 5479      Meaning:  The  physical  connection  and  initial connection
 5480                protocl  for the  HASP multiplexer  on channel TTY
 5481                has been completed  successfully.  The multiplexer
 5482                is now ready for use.
 5483 
 5484      Action:   Start the appropriate I/O daemon processes for the
 5485                multiplexer    as   indicated   by    the   system
 5486                administrators  or by  the user  who requested the
 5487                multiplexer be loaded.
 5488 
 5489 
 5490 
 5491                [as_hasp_mpx_.pl1]
 5492                as_hasp_mpx_:  More than  17 subchannels specified
 5493                for HASP multiplexer TTY (COUNT).
 5494 
 5495 
 5496      Stream:   as (severity 1)
 5497 
 5498      Time:     In  response  to  a  load_mpx  operator command or
 5499                during system initialization.
 5500 
 5501      Meaning:  The definition of the  HASP multiplexer on channel
 5502                TTY contains too many subchannels.
 5503 
 5504      Action:   Correct  the CDT  entry for  this multiplexer  and
 5505                reload it.
 5506 
 5507 
 5508                [as_hasp_mpx_.pl1]
 5509                as_hasp_mpx_:  Subchannel NAME  of multiplexer TTY
 5510                does not have TYPE service type.
 5511 
 5512 
 5513      Stream:   as (severity 1)
 5514 
 5515      Time:     In  response  to  a  load_mpx  operator command or
 5516                during system initialization.
 5517 
 5518      Meaning:  The specified  subchannel of the  HASP multiplexer
 5519                on  channel TTY  was not  given the  slave service
 5520                type   or,  in   the  case   of  operator  console
 5521                subchannels, slave or login.
 5522 
 5523 
 5524 as_hasp_mpx_                    96            08/03/23     MR12.7^L
 5525 
 5526 
 5527      Action:   Correct  the CDT  entry for  this multiplexer  and
 5528                reload it.
 5529 
 5530 
 5531                [as_hasp_mpx_.pl1]
 5532                as_hasp_mpx_:   Too  many   printers  and  punches
 5533                configured for HASP multiplexer TTY.
 5534 
 5535 
 5536      Stream:   as (severity 1)
 5537 
 5538      Time:     In  response  to  a  load_mpx  operator command or
 5539                during system initialization.
 5540 
 5541      Meaning:  More  than 8 card  punches and line  printers have
 5542                been specified for the HASP multiplexer on channel
 5543                TTY or a card punch and line printer which use the
 5544                same flow control flag  have been specified.  (See
 5545                MAM Communications for a  description of the rules
 5546                for naming card punches and line printers.)
 5547 
 5548      Action:   Correct  the CDT  entry for  this multiplexer  and
 5549                reload it.
 5550 
 5551 
 5552                [as_hasp_mpx_.pl1]
 5553                as_hasp_mpx_:   Unexpected  wakeup  (DATA1  DATA2)
 5554                from process ID.
 5555 
 5556 
 5557      Stream:   as (severity 1)
 5558 
 5559      Time:     While system is running.
 5560 
 5561      Meaning:  A  message  was  received  from  the process whose
 5562                processid  is  the  12-digit  octal  value ID; the
 5563                contents  of  the  message  are  given  by the two
 5564                12-digit octal values DATA1 and DATA2.  No message
 5565                was expected at this time.  The wakeup is ignored.
 5566 
 5567      Action:   No operator action is required.
 5568 
 5569 
 5570                [as_hasp_mpx_.pl1]
 5571                as_hasp_mpx_:   Wakeup  from  multiplexer  TTY has
 5572                invalid state code VALUE.
 5573 
 5574 
 5575      Stream:   as (severity 1)
 5576 
 5577      Time:     While system is running.
 5578 
 5579 
 5580 
 5581 
 5582 as_hasp_mpx_                    97            08/03/23     MR12.7^L
 5583 
 5584 
 5585      Meaning:  A  message  was  received  indicating  a change of
 5586                state for the multiplexer on channel TTY; however,
 5587                the  new state  of the  multiplexer, given  by the
 5588                decimal  number VALUE,  is not  recognized by this
 5589                module.
 5590 
 5591      Action:   Contact the system programming staff.
 5592 
 5593 
 5594                [as_init_.pl1]
 5595                as_init_:    Answering    Service   initialization
 5596                failed.
 5597 
 5598 
 5599      Stream:   as (severity 2)
 5600 
 5601      Time:     System Intialization.
 5602 
 5603      Meaning:  This indicates a logic error in the supervisor, or
 5604                CPU   or  memory  hardware   problems.   Answering
 5605                Service  initialization  failed.   Normally,  this
 5606                message is preceded by  a more specific indication
 5607                of the reason for failure.
 5608 
 5609      Action:   Contact the system  programming staff.  Attempt to
 5610                correct the problem and try startup again.
 5611 
 5612 
 5613 
 5614                [as_init_.pl1]
 5615                as_init_:  CDT rethreading complete.
 5616 
 5617 
 5618      Stream:   as (severity 1)
 5619 
 5620      Time:     System Intialization.
 5621 
 5622      Meaning:  Rethreading  of  Channel  Definition  Table  (CDT)
 5623                entries  into  a  multiplexer/subchannel hierarchy
 5624                completed  successfully.    System  initialization
 5625                continues.
 5626 
 5627      Action:   Contact the system programming staff._sa
 5628 
 5629 
 5630                [as_init_.pl1]
 5631                as_init_:   CDT   threading  inconsistency  found.
 5632                Rethreading.
 5633 
 5634 
 5635      Stream:   as (severity 1)
 5636 
 5637      Time:     System Intialization.
 5638 
 5639 
 5640 as_init_                        98            08/03/23     MR12.7^L
 5641 
 5642 
 5643      Meaning:  An error was detected  while tracing the threading
 5644                of Channel  Definition Table (CDT) entries  into a
 5645                hierarchy    of    multiplexer    and   subchannel
 5646                entries.This  indicates  a   logic  error  in  the
 5647                supervisor,  or CPU  or memory  hardware problems.
 5648                The entire channel hierarchy will be rethreaded.
 5649 
 5650      Action:   Contact the system programming staff._sa
 5651 
 5652 
 5653                [as_init_.pl1]
 5654                as_init_:    Condition   COND   signalled   during
 5655                startup.  Taking AS dump.  CONDITION_INFO
 5656 
 5657 
 5658 
 5659      S.  as (severity 1)
 5660 
 5661      Time:     System Intialization.
 5662 
 5663      Meaning:  An  unexpected  condition   COND  occurred  during
 5664                system initialization.  An  answering service dump
 5665                is  taken.  The  stack trace  information in  this
 5666                dump further  describes the error.  Some  steps of
 5667                Answering   Service    initialization   were   not
 5668                performed.  This  may cause the system  to operate
 5669                incorrectly.  CONDITION_INFO if optionally present
 5670                if  further  information  about  the  condition is
 5671                available.
 5672 
 5673      Action:   Contact the system programming staff.
 5674 
 5675 
 5676                [as_init_.pl1]
 5677                as_init_:     Condition   was    signalled   while
 5678                processing another condition.  CONDITION
 5679 
 5680 
 5681      Stream:   BOS Typewriter (sounds beeper)
 5682 
 5683      Time:     System Intialization.
 5684 
 5685      Meaning:  This indicates a logic error in the supervisor, or
 5686                CPU or memory hardware problems.  During Answering
 5687                Service  initialization,  a  CONDITION  was raised
 5688                while   as_init_  was   already  processing   some
 5689                condition.  It may be that the error occured while
 5690                making  an   as_dump  for  the   first  condition.
 5691                as_init_ will not attempt  to make an as_dump, but
 5692                will instead abort the initialization.
 5693 
 5694      Action:   Contact the system programming staff.
 5695 
 5696 
 5697 
 5698 as_init_                        99            08/03/23     MR12.7^L
 5699 
 5700 
 5701 
 5702 
 5703                [as_init_.pl1]
 5704                as_init_:  ERROR_MESSAGE.
 5705 
 5706 
 5707      Stream:   as (severity 1)
 5708 
 5709      Time:     System Intialization.
 5710 
 5711      Meaning:  A  fatal error  occurred during  Answering Service
 5712                initialization.   Previous  messages  describe the
 5713                error in more detail.
 5714 
 5715      Action:   Contact the system programming staff._sa
 5716 
 5717 
 5718                [as_init_.pl1]
 5719                as_init_:          ERROR_MESSAGE.          Calling
 5720                multiplexer_mgr_$ENTRYPOINT.
 5721 
 5722 
 5723      Stream:   as (severity 1)
 5724 
 5725      Time:     System Intialization.
 5726 
 5727      Meaning:  The  multiplexer_mgr_  failed  when  accessing the
 5728                Channel   Definition   Table    (CDT)   in   >sc1,
 5729                initializing   the  CDT   or  loading   the  FNPs.
 5730                ERROR_MESSAGE  is  the  text  associated  with the
 5731                error    code   returned    by   multiplexer_mgr_.
 5732                Answering   service  initialization   fails.   The
 5733                system  administrator must   enter admin  mode and
 5734                correct the problem.  Then reboot the system.
 5735 
 5736      Action:   Contact the system programming staff._sa
 5737 
 5738 
 5739                [as_init_.pl1]
 5740                as_init_:  ERROR_MESSAGE.  Calling ROUTINE.
 5741 
 5742 
 5743      Stream:   as (severity 1)
 5744 
 5745      Time:     System Intialization.
 5746 
 5747      Meaning:  An  error  occurred  when  calling  ROUTINE during
 5748                Answering  Service initialization.   ERROR_MESSAGE
 5749                is  the  text  associated   with  the  error  code
 5750                returned    by    ROUTINE.     Answering   service
 5751                initialization  fails.   The  system administrator
 5752                must  enter admin  mode and  correct the  problem.
 5753                Then reboot the system.
 5754 
 5755 
 5756 as_init_                       100            08/03/23     MR12.7^L
 5757 
 5758 
 5759      Action:   Contact the system programming staff._sa
 5760 
 5761 
 5762                [as_init_.pl1]
 5763                as_init_:  ERROR_MESSAGE.  Cannot create pit_temp_
 5764 
 5765 
 5766      Stream:   as (severity 1)
 5767 
 5768      Time:     System Intialization.
 5769 
 5770      Meaning:  The system could not create a temporary segment in
 5771                the Answering Service process's process directory.
 5772                This  is a fatal  error that will  cause answering
 5773                service startup to fail.
 5774 
 5775      Action:   Contact the system programming staff._sa
 5776 
 5777 
 5778                [as_init_.pl1]
 5779                as_init_:   ERROR_MESSAGE.  Cannot  create sat.ht.
 5780                REASON
 5781 
 5782 
 5783      Stream:   as (severity 1)
 5784 
 5785      Time:     System Intialization.
 5786 
 5787      Meaning:  This message indicates that  the sat is damaged or
 5788                that a storage system error prevented the creation
 5789                of  a  new  hash  table  for  the  sat.  Answering
 5790                Service startup will fail.
 5791 
 5792      Action:   Contact the system programming staff._sa
 5793 
 5794 
 5795                [as_init_.pl1]
 5796                as_init_:      ERROR_MESSAGE.     cdt_mgr_$thread:
 5797                ADDED_INFO
 5798 
 5799 
 5800      Stream:   as (severity 1)
 5801 
 5802      Time:     System Intialization.
 5803 
 5804      Meaning:  as_init_  called cdt_mgr_$thread  to rethread  the
 5805                Channel  Definition  Table  (CDT)  entries  into a
 5806                multiplexer/subchannel     hierarchy.     cdt_mgr_
 5807                encountered an unexpected error.  ERROR_MESSAGE is
 5808                the text  associated with the error  code returned
 5809                by  cdt_mgr_.   ADDED_INFO  further  describes the
 5810                error  and whether  or not  further rethreading is
 5811                attempted.
 5812 
 5813 
 5814 as_init_                       101            08/03/23     MR12.7^L
 5815 
 5816 
 5817      Action:   Contact the system programming staff._sa
 5818 
 5819 
 5820                [as_init_.pl1]
 5821                as_init_:    ERROR_MESSAGE.    Could   not  create
 5822                SYSTEM_CONTROL_DIR>TABLE.
 5823 
 5824 
 5825      Stream:   as (severity 1)
 5826 
 5827      Time:     System Intialization.
 5828 
 5829      Meaning:  The  Initializer could  not create  a new  segment
 5830                TABLE  in  SYSTEM_CONTROL_DIR.   Answering service
 5831                initialization  fails.   The  system administrator
 5832                must  enter admin  mode, and  type "create TABLE",
 5833                where TABLE is the  name given above.  Then reboot
 5834                the system.
 5835 
 5836      Action:   Contact the system programming staff._sa
 5837 
 5838 
 5839                [as_init_.pl1]
 5840                as_init_:  ERROR_MESSAGE.  Could  not force access
 5841                on SYSTEM_CONTROL_DIR>TABLE.
 5842 
 5843 
 5844      Stream:   as (severity 1)
 5845 
 5846      Time:     System Intialization.
 5847 
 5848      Meaning:  The  Initializer could not  change the ACL  on the
 5849                TABLE  segment  in  SYSTEM_CONTROL_DIR.  Answering
 5850                service   initialization    fails.    The   system
 5851                administrator must  enter admin mode,  and correct
 5852                the problem.  Then reboot the system.
 5853 
 5854      Action:   Contact the system programming staff._sa
 5855 
 5856 
 5857 
 5858 
 5859 
 5860                [as_init_.pl1]
 5861                as_init_:   ERROR_MESSAGE.    Could  not  initiate
 5862                SYSTEM_CONTROL_DIR>TABLE.
 5863 
 5864 
 5865      Stream:   as (severity 1)
 5866 
 5867      Time:     System Intialization.
 5868 
 5869 
 5870 
 5871 
 5872 as_init_                       102            08/03/23     MR12.7^L
 5873 
 5874 
 5875      Meaning:  The  Initializer  could  not  initiate  the  TABLE
 5876                segment in  SYSTEM_CONTROL_DIR.  Answering service
 5877                initialization  fails.   The  system administrator
 5878                must  enter admin  mode, and  correct the problem.
 5879                Then reboot the system.
 5880 
 5881      Action:   Contact the system programming staff._sa
 5882 
 5883 
 5884                [as_init_.pl1]
 5885                as_init_:  ERROR_MESSAGE.  Could  not set priority
 5886                for IPC wait channels.
 5887 
 5888 
 5889      Stream:   as (severity 1)
 5890 
 5891      Time:     System Intialization.
 5892 
 5893      Meaning:  A   call    to   ipc_$set_wait_prior   failed.This
 5894                indicates a logic error  in the supervisor, or CPU
 5895                or memory hardware problems.
 5896 
 5897      Action:   Contact the system programming staff._sa
 5898 
 5899 
 5900                [as_init_.pl1]
 5901                as_init_:  ERROR_MESSAGE.  Could not set RW access
 5902                on SYSTEM_CONTROL_DIR>TABLE.
 5903 
 5904 
 5905      Stream:   as (severity 1)
 5906 
 5907      Time:     System Intialization.
 5908 
 5909      Meaning:  An error occurred attempting to add ACL entries to
 5910                TABLE  in  SYSTEM_CONTROL_DIR.   Answering Service
 5911                initialization  fails.   The  system administrator
 5912                must  enter admin  mode and  correct the  problem.
 5913                Then reboot the system.
 5914 
 5915      Action:   Contact the system programming staff._sa
 5916 
 5917 
 5918                [as_init_.pl1]
 5919                as_init_:   ERROR_MESSAGE.   Error  while defining
 5920                initial work classes.
 5921 
 5922 
 5923      Stream:   as (severity 1)
 5924 
 5925      Time:     System Intialization.
 5926 
 5927 
 5928 
 5929 
 5930 as_init_                       103            08/03/23     MR12.7^L
 5931 
 5932 
 5933      Meaning:  This indicates a logic error in the supervisor, or
 5934                CPU   or  memory  hardware   problems.   Answering
 5935                Service   initialization    fails.    The   system
 5936                administrator  must enter  admin mode  and correct
 5937                the problem.  Then reboot the system.
 5938 
 5939      Action:   Contact the system programming staff._sa
 5940 
 5941 
 5942                [as_init_.pl1]
 5943                as_init_:    ERROR_MESSAGE.    Initialization   of
 5944                MODULE failed.  {ADDED_INFO.}
 5945 
 5946 
 5947      Stream:   as (severity 1)
 5948 
 5949      Time:     System Intialization.
 5950 
 5951      Meaning:  MODULE  was being  initialized when  it detected a
 5952                problem.  It  called sub_err_ to report  the error
 5953                to   as_init_.   ERROR_MESSAGE   gives  the   text
 5954                associated with the error  code MODULE returned to
 5955                as_init_.   If present,  ADDED_INFO gives  further
 5956                details   about  the   problem.   Some   steps  of
 5957                Answering   Service    initialization   were   not
 5958                performed.  This  may cause the system  to operate
 5959                incorrectly.
 5960 
 5961      Action:   Contact the system programming staff.
 5962 
 5963 
 5964                [as_init_.pl1]
 5965                as_init_:    ERROR_MESSAGE.     MODULE   signalled
 5966                sub_error_;        initialization       continues.
 5967                {ADDED_INFO.}
 5968 
 5969 
 5970 
 5971      Stream:   as (severity 1)
 5972 
 5973      Time:     System Intialization.
 5974 
 5975      Meaning:  MODULE  was being  initialized when  it detected a
 5976                problem.  It  called sub_err_ to report  the error
 5977                to   as_init_.   ERROR_MESSAGE   gives  the   text
 5978                associated with the error  code MODULE returned to
 5979                as_init_.   If present,  ADDED_INFO gives  further
 5980                details about the  problem.  Initialization of the
 5981                module continues.
 5982 
 5983      Action:   Contact the system programming staff..
 5984 
 5985 
 5986 
 5987 
 5988 as_init_                       104            08/03/23     MR12.7^L
 5989 
 5990 
 5991                [as_init_.pl1]
 5992                as_init_:  ERROR_MESSAGE.   Repeated CDT threading
 5993                inconsistencies.
 5994 
 5995 
 5996      Stream:   as (severity 1)
 5997 
 5998      Time:     System Intialization.
 5999 
 6000      Meaning:  Channel Definition Table  (CDT) entry threads were
 6001                found  to   be  damaged  even   after  rethreading
 6002                completed  successfully.This   indicates  a  logic
 6003                error in the supervisor, or CPU or memory hardware
 6004                problems.
 6005 
 6006      Action:   Contact the system programming staff._sa
 6007 
 6008 
 6009                [as_init_.pl1]
 6010                as_init_:  ERROR_MESSAGE.  Shutting down the login
 6011                server request mechanism.
 6012 
 6013 
 6014      Stream:   as (severity 1)
 6015 
 6016      Time:     System shutdown.
 6017 
 6018      Meaning:  An  error occurred  while shutting  down the login
 6019                server request mechanism.  The ERROR_MESSAGE gives
 6020                the text  associated with the error  code returned
 6021                from ls_request_server_$shutdown.
 6022 
 6023      Action:   No operator action is required.
 6024 
 6025 
 6026                [as_init_.pl1]
 6027                as_init_:                           ERROR_MESSAGE.
 6028                SYSTEM_CONTROL_DIR>TABLE.  Forcing access.
 6029 
 6030 
 6031      Stream:   as (severity 1)
 6032 
 6033      Time:     System Intialization.
 6034 
 6035      Meaning:  During    system    initialization,    TABLE    in
 6036                SYSTEM_CONTROL_DIR was found  to have an incorrect
 6037                ACL.  Access was set for Initializer.SysDaemon.
 6038 
 6039      Action:   No operator action is required.
 6040 
 6041 
 6042 
 6043 
 6044 
 6045 
 6046 as_init_                       105            08/03/23     MR12.7^L
 6047 
 6048 
 6049                [as_init_.pl1]
 6050                as_init_:   installation_parms  damaged.   N  rate
 6051                structures defined; from I to J allowed.
 6052 
 6053 
 6054 
 6055      Stream:   as (severity 1)
 6056 
 6057      Time:     System Intialization.
 6058 
 6059      Meaning:  The installation_parms table  claims to declare an
 6060                unallowed   number  of   rate  structures.    This
 6061                indicates  that the  table has  been damaged.  The
 6062                system  administrator  must  rectify  the  problem
 6063                using   ed_installation_parms  from   admin  mode,
 6064                before the Answering  Service will initialize.  It
 6065                will  be  necessary  to  re-boot  Multics to retry
 6066                Answering Service initialization.
 6067 
 6068      Action:   Contact the system programming staff._sa
 6069 
 6070 
 6071                [as_init_.pl1]
 6072                as_init_:    Multics   SYSID;   Answering  Service
 6073                VERSION
 6074 
 6075 
 6076      Stream:   as (severity 1)
 6077 
 6078      Time:     System Intialization.
 6079 
 6080      Meaning:  Answering  Service initialization is  complete and
 6081                users may now log  in.  The current system version
 6082                number,  from  the  system  tape,  is  SYSID.  The
 6083                current   Answering  Service  version   number  is
 6084                VERSION.
 6085 
 6086      Action:   Proceed with startup.
 6087 
 6088 
 6089                [as_init_.pl1]
 6090                as_init_:   No  "tcd"  card  in  the  config deck.
 6091                Assuming APT size of 1000.
 6092 
 6093 
 6094      Stream:   as (severity 1)
 6095 
 6096      Time:     System Intialization.
 6097 
 6098      Meaning:  This message  indicates that there is  no TCD card
 6099                in  the  config  deck.   The  system  will operate
 6100                normally, but  it is recommended that  an explicit
 6101                TCD card be added at the first convenience.
 6102 
 6103 
 6104 as_init_                       106            08/03/23     MR12.7^L
 6105 
 6106 
 6107      Action:   Contact the system programming staff._sa
 6108 
 6109 
 6110                [as_init_.pl1]
 6111                as_init_:  rebuilding SAT hash table.
 6112 
 6113 
 6114      Stream:   as (severity 1)
 6115 
 6116      Time:     System Intialization.
 6117 
 6118      Meaning:  The  hash table  for the  SAT was  corrupted.  The
 6119                hash table is regenerated.
 6120 
 6121      Action:   No operator action is required.
 6122 
 6123 
 6124                [as_init_.pl1]
 6125                as_init_:    Resource   management   is  disabled;
 6126                >sc1>rtdt needs it enabled.
 6127 
 6128 
 6129      Stream:   as (severity 1)
 6130 
 6131      Time:     System Intialization.
 6132 
 6133      Meaning:  The  copy  of  installation_parms  encountered  by
 6134                system startup claims that RCP resource management
 6135                is disabled.   This disagrees with  information in
 6136                the  RTDT.   If  startup  were  to  continue,  all
 6137                information in resource  registries would be lost.
 6138                Answering   Service  initialization   fails.   The
 6139                system        administrator        must        use
 6140                ed_installation_parms  from admin  mode to  repair
 6141                the damage.  Then reboot the system.
 6142 
 6143      Action:   Contact the system programming staff._sa
 6144 
 6145 
 6146                [as_init_.pl1]
 6147                as_init_:     SAT   version    inconsistent   with
 6148                declarations used in this program.
 6149 
 6150 
 6151      Stream:   as (severity 1)
 6152 
 6153      Time:     System Intialization.
 6154 
 6155      Meaning:  The  version number  stored  in  the SAT  does not
 6156                match  the  expected  version  number,  which is a
 6157                constant in the  Answering Service programs.  This
 6158                may  be because  the  SAT  has been  destroyed, or
 6159                because  an  incorrect  version  of  the Answering
 6160 
 6161 
 6162 as_init_                       107            08/03/23     MR12.7^L
 6163 
 6164 
 6165                Service  programs is  being used.   BOS Typewriter
 6166                (Crashes system)es
 6167 
 6168      Action:   Contact  the  system   programming  staff._sa  The
 6169                System  Administrator must  either generate  a new
 6170                SAT,  or  install  the   correct  version  of  the
 6171                Answering Service.  If the System Administrator is
 6172                not  available, enter  admin mode  and attempt  to
 6173                retrieve a recent copy of the SAT.  Then exit from
 6174                admin mode and try startup again.
 6175 
 6176 
 6177 
 6178                [as_init_.pl1]
 6179                as_init_:     SYSTEM_CONTROL_DIR>TABLE    missing.
 6180                Creating new one.
 6181 
 6182 
 6183      Stream:   as (severity 1)
 6184 
 6185      Time:     System Intialization.
 6186 
 6187      Meaning:  A   new   version   of   TABLE   was   created  in
 6188                SYSTEM_CONTROL_DIR     as    part     of    system
 6189                initialization.
 6190 
 6191      Action:   No operator action is required.
 6192 
 6193 
 6194                [as_init_.pl1]
 6195                as_init_:  The requested action was not performed.
 6196                Cannot type go twice.
 6197 
 6198 
 6199      Stream:   as (severity 1)
 6200 
 6201      Time:     System Intialization.
 6202 
 6203      Meaning:  The operator typed go  when Multics was already in
 6204                operation.  No action was taken.
 6205 
 6206      Action:   No operator action is required.
 6207 
 6208 
 6209                [as_init_.pl1]
 6210                as_init_:  The requested action was not performed.
 6211                Type multics first.
 6212 
 6213 
 6214      Stream:   as (severity 1)
 6215 
 6216      Time:     System Intialization.
 6217 
 6218 
 6219 
 6220 as_init_                       108            08/03/23     MR12.7^L
 6221 
 6222 
 6223      Meaning:  The operator typed go  without typing multics.  No
 6224                action was taken.
 6225 
 6226      Action:   Type multics first, or startup.
 6227 
 6228 
 6229                [as_init_.pl1]
 6230                as_init_:  The requested action was not performed.
 6231                Multics already initialized.
 6232 
 6233 
 6234      Stream:   as (severity 1)
 6235 
 6236      Time:     System Intialization.
 6237 
 6238      Meaning:  The  operator typed  startup, multics,  or go when
 6239                Multics was  already in operation.  No  action was
 6240                taken.
 6241 
 6242      Action:   No operator action is required.
 6243 
 6244 
 6245                [as_init_.pl1]
 6246                as_init_:  This  procedure does not  implement the
 6247                requested version.  installation_parms version N.
 6248 
 6249 
 6250 
 6251      Stream:   as (severity 1)
 6252 
 6253      Time:     System Intialization.
 6254 
 6255      Meaning:  This indicates a logic error in the supervisor, or
 6256                CPU    or   memory    hardware   problems.     The
 6257                installation_parms segment has  been damaged or is
 6258                not  up-to-date.   The  system  administrator must
 6259                rectify  the  problem  using ed_installation_parms
 6260                from admin mode, before the Answering Service will
 6261                initialize.   It  will  be  necessary  to  re-boot
 6262                Multics to retry Answering Serviceinitialization.
 6263 
 6264      Action:   Contact the system programming staff._sa
 6265 
 6266 
 6267                [as_lap_mpx_.pl1]
 6268                as_lap_mpx:   Unexpected  signal  for  multiplexer
 6269                MPX.
 6270 
 6271 
 6272      Stream:   as (severity1)
 6273 
 6274      Time:     While system is running.
 6275 
 6276 
 6277 
 6278 as_lap_mpx                     109            08/03/23     MR12.7^L
 6279 
 6280 
 6281      Meaning:  An unknown type event was signaled for multiplexer
 6282                MPX.  It will be ignored.
 6283 
 6284      Action:   Contact the system programming staff.
 6285 
 6286 
 6287                [as_lap_mpx_.pl1]
 6288                as_lap_mpx_:  Bad argument to parm PPPP, should be
 6289                XXXX or YYYY
 6290 
 6291 
 6292      Stream:   as (severity1)
 6293 
 6294      Time:     In  response to  an operator  load_mpx command for
 6295                during system startup.
 6296 
 6297      Meaning:  A bad  value was specified for  the PPPP parameter
 6298                in the  TTF entry for this  muliplexer.  Its value
 6299                must be either XXXX or YYYY.
 6300 
 6301      Action:   Check  the  contents  of  the  TTF  entry  for the
 6302                terminal_type associated with  the multiplexer for
 6303                errors.
 6304 
 6305 
 6306 
 6307                [as_lap_mpx_.pl1]
 6308                as_lap_mpx_:  Crash signalled for multiplexer MPX.
 6309 
 6310 
 6311      Stream:   as (severity1)
 6312 
 6313      Time:     While system is running.
 6314 
 6315      Meaning:  The  multiplexer has  crashed.  The  LAP link  has
 6316                entered the disconnected state.
 6317 
 6318      Action:   Contact the system programming staff.
 6319 
 6320 
 6321                [as_lap_mpx_.pl1]
 6322                as_lap_mpx_:   Error  in  conversion.   Converting
 6323                FIELD VALUE to a number for multiplexer MPX.
 6324 
 6325 
 6326      Stream:   as (severity1)
 6327 
 6328      Time:     In  response to  an operator  load_mpx command  or
 6329                during system start up.
 6330 
 6331      Meaning:  It was  impossible to convert a  numeric parameter
 6332                from  the terminal_type additional_info  string to
 6333                its  internal  form.   FIELD  is  the  name of the
 6334 
 6335 
 6336 as_lap_mpx_                    110            08/03/23     MR12.7^L
 6337 
 6338 
 6339                parameter  in error.   VALUE is  the string  which
 6340                could not be converted.
 6341 
 6342      Action:   Check  the  contents  of  the  TTF  entry  for the
 6343                terminal_type associated with  the multiplexer for
 6344                errors.
 6345 
 6346 
 6347 
 6348                [as_lap_mpx_.pl1]
 6349                as_lap_mpx_:   ERROR.  Cannot get  additional info
 6350                for terminal type TTP for multiplexer MPX.
 6351 
 6352 
 6353      Stream:   as (severity1)
 6354 
 6355      Time:     In  response to  an operator  load_mpx command  or
 6356                during system start up.
 6357 
 6358      Meaning:  An error occurred  while retrieving the parameters
 6359                of  the  multiplexer  from  the  TTT.   Either the
 6360                terminal type specified in  the CDT does not exist
 6361                or    it   does    not   contain    the   required
 6362                additional_info field.
 6363 
 6364      Action:   Check  that the  CMF  and  TTF contain  the proper
 6365                information.
 6366 
 6367 
 6368                [as_lap_mpx_.pl1]
 6369                as_lap_mpx_:   ERROR.  Creating event  channel for
 6370                multiplexer MPX.
 6371 
 6372 
 6373      Stream:   as (severity1)
 6374 
 6375      Time:     In  response to  an operator  load_mpx command  or
 6376                during system start up.
 6377 
 6378      Meaning:  An ipc_ error occurred  while trying to initialize
 6379                the multiplexer.
 6380 
 6381      Action:   Contact the system programming staff.
 6382 
 6383 
 6384                [as_lap_mpx_.pl1]
 6385                as_lap_mpx_:  Load failed for multiplexer MPX.
 6386 
 6387 
 6388      Stream:   as (severity1)
 6389 
 6390      Time:     In  response to  an operator  load_mpx command  or
 6391                during system start up.
 6392 
 6393 
 6394 as_lap_mpx_                    111            08/03/23     MR12.7^L
 6395 
 6396 
 6397      Meaning:  The attempt to load  the multiplexer failed.  This
 6398                should never happen.
 6399 
 6400      Action:   Contact the system programming staff.
 6401 
 6402 
 6403                [as_lap_mpx_.pl1]
 6404                as_lap_mpx_:  Load signalled for multiplexer MPX.
 6405 
 6406 
 6407      Stream:   as (severity1)
 6408 
 6409      Time:     In  response to  an operator  load_mpx command  or
 6410                during system start up.
 6411 
 6412      Meaning:  The multiplexer has  been successfully loaded.  It
 6413                will  be  started  unless  the  -no_start  control
 6414                argument was  given when the load_mpx  command was
 6415                typed.
 6416 
 6417      Action:   No operator action is required.
 6418 
 6419 
 6420                [as_lap_mpx_.pl1]
 6421                as_lap_mpx_:    Unexpected   wakeup   (DATA)  from
 6422                process PRCID.
 6423 
 6424 
 6425      Stream:   as (severity1)
 6426 
 6427      Time:     While system is running.
 6428 
 6429      Meaning:  The multiplexer manager received  a wakeup from an
 6430                unexpected source.  The wakeup is ignored.
 6431 
 6432      Action:   No operator action is required.
 6433 
 6434 
 6435                [as_lap_mpx_.pl1]
 6436                as_lap_mpx_:   Wakeup  for   multiplexer  MPX  has
 6437                invalid state code STATE.
 6438 
 6439 
 6440      Stream:   as (severity1)
 6441 
 6442      Time:     While system is running.
 6443 
 6444      Meaning:  A  wakeup with  invalid data  was received  by the
 6445                multiplexer manager.  The wakeup is ignored.
 6446 
 6447      Action:   Contact the system programming staff.
 6448 
 6449 
 6450 
 6451 
 6452 as_mcs_mpx_ (trace)            112            08/03/23     MR12.7^L
 6453 
 6454 
 6455                [as_mcs_mpx_.pl1]
 6456                as_mcs_mpx_  (trace):  FNP FNP_NUMBER,  MPXE state
 6457                MPX_STATE, FNP state FNP_STATE{, deconfigured}.
 6458 
 6459 
 6460 
 6461      Stream:   as (severity 1)
 6462 
 6463      Time:     While system is running.
 6464 
 6465      Meaning:  This  is  a  tracing  message  which displays some
 6466                values  of variables  that describe  the status of
 6467                the FNP.
 6468 
 6469      Action:   Contact the system programming staff.
 6470 
 6471 
 6472                [as_mcs_mpx_.pl1]
 6473                as_mcs_mpx_:  Crash signalled for FNP TAG.
 6474 
 6475 
 6476      Stream:   as (severity 1)
 6477 
 6478      Time:     While system is running.
 6479 
 6480      Meaning:  FNP TAG has crashed.  A  reload of the FNP will be
 6481                attempted  if it  is not  in a  crash loop  or not
 6482                inactive.
 6483 
 6484      Action:   Contact the system programming staff.
 6485 
 6486 
 6487                [as_mcs_mpx_.pl1]
 6488                as_mcs_mpx_:                    ERROR_CODE_MESSAGE
 6489                >sc1>fnp_crash_notify.ec does not exist.
 6490 
 6491 
 6492      Stream:   as (severity 1)
 6493 
 6494      Time:     While system is running.
 6495 
 6496      Meaning:  An   error   occured   (ERROR_CODE_MESSAGE)   when
 6497                checking for the  existence of fnp_crash_notify.ec
 6498                in the system_control_1 directory.
 6499 
 6500      Action:   Contact the system programming staff.
 6501 
 6502 
 6503                [as_mcs_mpx_.pl1]
 6504                as_mcs_mpx_:   ERROR_CODE_MESSAGE  Creating  event
 6505                channel for FNP TAG.
 6506 
 6507 
 6508 
 6509 
 6510 as_mcs_mpx_                    113            08/03/23     MR12.7^L
 6511 
 6512 
 6513      Stream:   as (severity 1)
 6514 
 6515      Time:     While system is running.
 6516 
 6517      Meaning:  An  error  occured  (ERROR_CODE_MESSAGE)  when  an
 6518                attempt  was made to  create an event  channel for
 6519                FNP TAG.  The load attempt has been aborted.  This
 6520                message  can also  be logged  if an  error occured
 6521                when changing the  just created event-wait channel
 6522                into an event-call channel.
 6523 
 6524      Action:   Contact the system programming staff.
 6525 
 6526 
 6527                [as_mcs_mpx_.pl1]
 6528                as_mcs_mpx_:     ERROR_CODE_MESSAGE   Failed    to
 6529                establish an SCI environment.
 6530 
 6531 
 6532      Stream:   as (severity 1)
 6533 
 6534      Time:     While system is running.
 6535 
 6536      Meaning:  An error occured  (ERROR_CODE_MESSAGE) when trying
 6537                to create an  system control subsystem environment
 6538                pointer.
 6539 
 6540      Action:   Contact the system programming staff.
 6541 
 6542 
 6543                [as_mcs_mpx_.pl1]
 6544                as_mcs_mpx_:   ERROR_CODE_MESSAGE   Reading  event
 6545                channel for FNP TAG.
 6546 
 6547 
 6548      Stream:   as (severity 1)
 6549 
 6550      Time:     While system is running.
 6551 
 6552      Meaning:  An  error  occured  (ERROR_CODE_MESSAGE)  when  an
 6553                attempt  was  made  to  read  the  bootload  event
 6554                channel for FNP TAG.
 6555 
 6556      Action:   Contact the system programming staff.
 6557 
 6558 
 6559                [as_mcs_mpx_.pl1]
 6560                as_mcs_mpx_:   ERROR_CODE_MESSAGE Resetting  event
 6561                channel for FNP TAG.
 6562 
 6563 
 6564      Stream:   as (severity 1)
 6565 
 6566 
 6567 
 6568 as_mcs_mpx_                    114            08/03/23     MR12.7^L
 6569 
 6570 
 6571      Time:     While system is running.
 6572 
 6573      Meaning:  An  error  occured  (ERROR_CODE_MESSAGE)  when  an
 6574                attempt was made to drain  all events from the FNP
 6575                boot event channel.
 6576 
 6577      Action:   Contact the system programming staff.
 6578 
 6579 
 6580                [as_mcs_mpx_.pl1]
 6581                as_mcs_mpx_:   ERROR_CODE_MESSAGE  Taking  dump of
 6582                FNP TAG.  FNP_DUMP_ENTRY_NAME
 6583 
 6584 
 6585      Stream:   as (severity 1)
 6586 
 6587      Time:     While system is running.
 6588 
 6589      Meaning:  An  error  occured  (ERROR_CODE_MESSAGE)  when  an
 6590                attempt  was  made  to   dump  FNP  TAG  into  the
 6591                FNP_DUMP_ENTRY_NAME segment in >dumps.
 6592 
 6593      Action:   Contact the system programming staff.
 6594 
 6595 
 6596                [as_mcs_mpx_.pl1]
 6597                as_mcs_mpx_:    FDUMP  of   FNP  TAG   created  in
 6598                >dumps>FNP_DUMP_ENTRY_NAME
 6599 
 6600 
 6601      Stream:   as (severity 1)
 6602 
 6603      Time:     While system is running.
 6604 
 6605      Meaning:  FNP  TAG  has  been  dumped  successfully into the
 6606                >dumps>FNP_DUMP_ENTRY_NAME   segment    after   it
 6607                crashed.
 6608 
 6609      Action:   Contact the system programming staff.
 6610 
 6611 
 6612                [as_mcs_mpx_.pl1]
 6613                as_mcs_mpx_:   Inconsistent  wakeup  received from
 6614                FNP  TAG.   FNP  state  =  FNP_STATE,  msg state =
 6615                MSG_STATE.
 6616 
 6617 
 6618 
 6619      Stream:   as (severity 1)
 6620 
 6621      Time:     While system is running.
 6622 
 6623 
 6624 
 6625 
 6626 as_mcs_mpx_                    115            08/03/23     MR12.7^L
 6627 
 6628 
 6629      Meaning:  The  data in the  message from the  bootload event
 6630                channel for FNP TAG indicates  that the FNP was in
 6631                an inconsistant state (MSG_STATE) with the current
 6632                state (FNP_STATE) of the FNP in the CDT.
 6633 
 6634      Action:   Contact the system programming staff.
 6635 
 6636 
 6637                [as_mcs_mpx_.pl1]
 6638                as_mcs_mpx_:  Invalid wakeup received for FNP TAG.
 6639                Wakeup   appears   to   be   for   FNP   OTHER_TAG
 6640                (#FNP_NUMBER).
 6641 
 6642 
 6643 
 6644      Stream:   as (severity 1)
 6645 
 6646      Time:     While system is running.
 6647 
 6648      Meaning:  Invalid wakeup received  on bootload event channel
 6649                for FNP TAG.  Wakeup data  indicates it is for FNP
 6650                OTHER_TAG whose number is FNP_NUMBER.
 6651 
 6652      Action:   Contact the system programming staff.
 6653 
 6654 
 6655                [as_mcs_mpx_.pl1]
 6656                as_mcs_mpx_:  Load failed for FNP TAG.
 6657 
 6658 
 6659      Stream:   as (severity 1)
 6660 
 6661      Time:     While system is running.
 6662 
 6663      Meaning:  The FNP TAG failed to load successfully.
 6664 
 6665      Action:   Try  the  bootload   attempt  again.   If  problem
 6666                persists, contact the programing staff.
 6667 
 6668 
 6669 
 6670                [as_mcs_mpx_.pl1]
 6671                as_mcs_mpx_:   Load of  FNP TAG  did not  complete
 6672                within X minutes.
 6673 
 6674 
 6675      Stream:   as (severity 2)
 6676 
 6677      Time:     While system is running.
 6678 
 6679      Meaning:  FNP TAG  did not signal that it  had completed the
 6680                load  attempt within  the required  X minutes from
 6681                the time that the image was sent to the FNP.
 6682 
 6683 
 6684 as_mcs_mpx_                    116            08/03/23     MR12.7^L
 6685 
 6686 
 6687      Action:   Try to  load the FNP again.   If problem persists,
 6688                contact system programing staff.
 6689 
 6690 
 6691 
 6692                [as_mcs_mpx_.pl1]
 6693                as_mcs_mpx_:  Load signalled for FNP TAG.
 6694 
 6695 
 6696      Stream:   as (severity 1)
 6697 
 6698      Time:     While system is running.
 6699 
 6700      Meaning:  FNP TAG bootloaded successfully.
 6701 
 6702      Action:   No operator action is required.
 6703 
 6704 
 6705                [as_mcs_mpx_.pl1]
 6706                as_mcs_mpx_:  Procedure called with bad fnpep into
 6707                cdt:  POINTER
 6708 
 6709 
 6710      Stream:   as (severity 1)
 6711 
 6712      Time:     While system is running.
 6713 
 6714      Meaning:  The  compute_fnp_no  internal  procedure  detected
 6715                that  as_mcs_mpx_  was  supplied  with  a prointer
 6716                value (POINTER) that should  point to an FNP entry
 6717                in  the CDT  but doesn't.   Current operation  has
 6718                been aborted.
 6719 
 6720      Action:   Contact the system programming staff.
 6721 
 6722 
 6723                [as_mcs_mpx_.pl1]
 6724                as_mcs_mpx_:  Tracing off.
 6725 
 6726 
 6727      Stream:   as (severity 1)
 6728 
 6729      Time:     While system is running.
 6730 
 6731      Meaning:  The trace_off entry point  has been called and now
 6732                tracing has been disabled.
 6733 
 6734      Action:   Contact the system programming staff.
 6735 
 6736 
 6737                [as_mcs_mpx_.pl1]
 6738                as_mcs_mpx_:  Tracing on.
 6739 
 6740 
 6741 
 6742 as_mcs_mpx_                    117            08/03/23     MR12.7^L
 6743 
 6744 
 6745      Stream:   as (severity 1)
 6746 
 6747      Time:     While system is running.
 6748 
 6749      Meaning:  The trace_on  entry point has been  called so that
 6750                as_mcs_mpx_ trace data will now be displayed.
 6751 
 6752      Action:   Contact the system programming staff.
 6753 
 6754 
 6755                [as_mcs_mpx_.pl1]
 6756                as_mcs_mpx_:   Unexpected   wakeup  (EV_MSG_WORD_1
 6757                EV_MSG_WORD_2) from process PROC_ID.
 6758 
 6759 
 6760 
 6761      Stream:   as (severity 1)
 6762 
 6763      Time:     While system is running.
 6764 
 6765      Meaning:  An  unexpected wakeup  occured on  an FNP bootload
 6766                event  channel from   process PROC_ID.   The event
 6767                message    data    is    in    EV_MSG_WORD_1   and
 6768                EV_MSG_WORD_2.  Unable to determine FNP tag.
 6769 
 6770      Action:   Contact the system programming staff.
 6771 
 6772 
 6773                [as_mcs_mpx_.pl1]
 6774                as_mcs_mpx_:  Wakeup for FNP TAG has invalid state
 6775                code:  CODE.
 6776 
 6777 
 6778      Stream:   as (severity 1)
 6779 
 6780      Time:     While system is running.
 6781 
 6782      Meaning:  Wakeup  message data   received on  bootload event
 6783                channel for FNP TAG contains an invalid state code
 6784                value  of CODE.   Valid values  for mpxe.state are
 6785                defined  in the  cdt.incl.pl1 include  file by the
 6786                FNP_* variables.
 6787 
 6788      Action:   Contact the system programming staff.
 6789 
 6790 
 6791                [as_mcs_mpx_.pl1]
 6792                as_mcs_mpx_:    Wakeup  with   bad  data   pointer
 6793                ignored:  POINTER
 6794 
 6795 
 6796      Stream:   as (severity 1)
 6797 
 6798 
 6799 
 6800 as_mcs_mpx_                    118            08/03/23     MR12.7^L
 6801 
 6802 
 6803      Time:     While system is running.
 6804 
 6805      Meaning:  A  wakeup was  received on  an FNP  bootload event
 6806                channel  with   which  a  bad  data   pointer  was
 6807                supplied.  Unable to determine FNP tag.
 6808 
 6809      Action:   Contact the system programming staff.
 6810 
 6811 
 6812                [as_meter_.pl1]
 6813                as_meter_:  FDUMP number is NNN
 6814 
 6815 
 6816      Stream:   as (severity1)
 6817 
 6818      Time:     System Intialization.
 6819 
 6820      Meaning:  The system is coming up after a crash.  There is a
 6821                dump, created by the bce dump command, in the DUMP
 6822                partition.   Usually,   system_start_up.ec  copies
 6823                this dump into the directory >dumps.
 6824 
 6825      Action:   Follow site instructions concerning the processing
 6826                of online  dumps.  The normal procedure  is to log
 6827                in   Print_Dump.SysDaemon  and  request   that  it
 6828                process the dump.
 6829 
 6830 
 6831 
 6832                [as_meter_.pl1]
 6833                as_meter_:   Problem   getting  "ITEM".   Metering
 6834                disabled.
 6835 
 6836 
 6837      Stream:   as (severity2)
 6838 
 6839      Time:     System Intialization.
 6840 
 6841      Meaning:  The metering module cannot obtain a pointer to the
 6842                ring   0  hardcore   data  item   ITEM,  used   in
 6843                calculating  system usage.   Metering figures  are
 6844                scrambled, but the system should be able to run.
 6845 
 6846      Action:   Contact the system programming staff.
 6847 
 6848 
 6849                [as_request_bump_user_.pl1]
 6850                as_request_bump_user_:     BUMPING   PERS.PROJ.TAG
 6851                PROCESSID for requestor REQ_PERS.REQ_PROJ.REQ_TAG.
 6852 
 6853 
 6854 
 6855      Stream:   as (severity 0)
 6856 
 6857 
 6858 as_request_bump_user_          119            08/03/23     MR12.7^L
 6859 
 6860 
 6861      Time:     While system is running.
 6862 
 6863      Meaning:  An     answering      service     request     from
 6864                REQ_PERS.REQ_PROJ.REQ_TAG  to   bump  the  process
 6865                PERS.PROJ.TAG PROCESSID has been initiated.
 6866 
 6867      Action:   No operator action is required.
 6868 
 6869 
 6870                [as_request_bump_user_.pl1]
 6871                as_request_bump_user_:     ERROR_MSG.     Rejected
 6872                BUMP_USER  request  from   PERS.PROJ.TAG  to  bump
 6873                process PROCESS_ID.  REASON
 6874 
 6875 
 6876 
 6877      Stream:   as (severity 0)
 6878 
 6879      Time:     While system is running.
 6880 
 6881      Meaning:  The  answering service request  from PERS.PROJ.TAG
 6882                to bump the process identified by PROCESSID failed
 6883                for the given REASON and ERROR_MSG.
 6884 
 6885      Action:   Contact the system programming staff._sa
 6886 
 6887 
 6888                [as_request_note_pnt_change_.pl1]
 6889                as_request_note_pnt_change_:      Bumping     user
 6890                PERS.PROJ.TAG PROCESSID on channel CHN.  (REASON)
 6891 
 6892 
 6893 
 6894      Stream:   as (severity 0)
 6895 
 6896      Time:     While system is running.
 6897 
 6898      Meaning:  Process PERS.PROJ.TAG on channel CHN was bumped by
 6899                a  change  to  the  PNT  entry  for  PERS.  REASON
 6900                describes the type of PNT change.
 6901 
 6902      Action:   No operator action is required.
 6903 
 6904 
 6905 
 6906                [as_request_note_pnt_change_.pl1]
 6907                as_request_note_pnt_change_:  ERROR_MSG.  Rejected
 6908                NOTE_PNT_CHANGE request from PERS.PROJ.  REASON
 6909 
 6910 
 6911 
 6912      Stream:   as (severity 0)
 6913 
 6914 
 6915 
 6916 as_request_note_pnt_change_    120            08/03/23     MR12.7^L
 6917 
 6918 
 6919      Time:     While system is running.
 6920 
 6921      Meaning:  An answering  service request to note  a change to
 6922                the  PNT  sent  by  PERS.PROJ  failed  because  of
 6923                REASON.This  indicates   a  logic  error   in  the
 6924                supervisor, or CPU or memory hardware problems.
 6925 
 6926      Action:   Contact the system programming staff.
 6927 
 6928 
 6929 
 6930                [as_request_note_pnt_change_.pl1]
 6931                as_request_note_pnt_change_:     Lowered   maximum
 6932                authorization  for  PERS.PROJ.TAG  on  channel CHN
 6933                from OLD_MAX_AUTH to NEW_MAX_AUTH.  PNT change.
 6934 
 6935 
 6936 
 6937      Stream:   as (severity 0)
 6938 
 6939      Time:     While system is running.
 6940 
 6941      Meaning:  A  change to  the PNT  entry for  PERS lowered the
 6942                maximum authorization associated  with the process
 6943                PERS.PROJ.TAG  on channel CHN.   The authorization
 6944                was changed from OLD_MAX_AUTH to NEW_MAX_AUTH.
 6945 
 6946      Action:   No operator action is required.
 6947 
 6948 
 6949 
 6950                [as_request_note_pnt_change_.pl1]
 6951                as_request_note_pnt_change_:     Raised    minimum
 6952                authorization  for  PERS.PROJ.TAG  on  channel CHN
 6953                from OLD_MIN_AUTH to NEW_MIN_AUTH.  PNT change.
 6954 
 6955 
 6956 
 6957      Stream:   as (severity 0)
 6958 
 6959      Time:     While system is running.
 6960 
 6961      Meaning:  A  change to  the PNT  entry for  PERS raised  the
 6962                minimum authorization associated  with the process
 6963                PERS.PROJ.TAG  on channel CHN.   The authorization
 6964                was changed from OLD_MIN_AUTH to NEW_MIN_AUTH.
 6965 
 6966      Action:   No operator action is required.
 6967 
 6968 
 6969 
 6970                [as_request_note_pnt_change_.pl1]
 6971                as_request_note_pnt_change_:   User  has  "nobump"
 6972 
 6973 
 6974 as_request_note_pnt_change_    121            08/03/23     MR12.7^L
 6975 
 6976 
 6977                attribute.   Did not bump  PERS.PROJ.TAG PROCESSID
 6978                on channel CHN.  (REASON)
 6979 
 6980 
 6981 
 6982      Stream:   as (severity 0)
 6983 
 6984      Time:     While system is running.
 6985 
 6986      Meaning:  Bump   attempt  for  process   PERS.PROJ.TAG  with
 6987                PROCESSID on channel CHN  failed, because the user
 6988                has  the nobump  attribute.  REASON  indicates why
 6989                bumping was attempted.
 6990 
 6991      Action:   Contact the system programming staff._sa
 6992 
 6993 
 6994 
 6995                [as_request_server_.pl1]
 6996                as_request_sender_:    MSG.    Could   not  delete
 6997                message MID for PERS.PROJ.
 6998 
 6999 
 7000      Stream:   as (severity0)
 7001 
 7002      Time:     While system is running.
 7003 
 7004      Meaning:  MSG is  an error_table_ message, MID  is a message
 7005                ID, PERS.PROJ  is the group  ID of the  AS request
 7006                sender.   The  AS  request  message  could  not be
 7007                deleted after executing the AS request.
 7008 
 7009      Action:   No operator action is required.
 7010 
 7011 
 7012                [as_request_server_.pl1]
 7013                as_request_sender_:   PERS.PROJ  (PID)  set  fatal
 7014                process error [logout|new_proc].
 7015 
 7016 
 7017      Stream:   as (severity0)
 7018 
 7019      Time:     While system is running.
 7020 
 7021      Meaning:  The  process group  id PERS.PROJ  (process id PID)
 7022                has  set the  AS flag  which indicates  that fatal
 7023                process errors will cause a {logout|new_proc}.
 7024 
 7025      Action:   No operator action is required.
 7026 
 7027 
 7028                [as_request_server_.pl1]
 7029 
 7030 
 7031 
 7032 as_request_server_$init        122            08/03/23     MR12.7^L
 7033 
 7034 
 7035                as_request_server_$init:       MSG.       Deleting
 7036                >sc1>as_request_.ms.
 7037 
 7038 
 7039      Stream:   as (severity1)
 7040 
 7041      Time:     Answering Service initialization.
 7042 
 7043      Meaning:  MSG  is  an  error_table_  message.   An error was
 7044                encountered   while  attempting   to  delete   the
 7045                as_request  message segment, prior  to re-creating
 7046                it.     as_request_server_$init   continues    and
 7047                attempts to create the message segment.
 7048 
 7049      Action:   No operator action is required.
 7050 
 7051 
 7052                [as_request_server_.pl1]
 7053                as_request_server_$init:     MSG.     Manipulating
 7054                >sc1>as_request_.ms or IPC channels.
 7055 
 7056 
 7057      Stream:   as (severity1)
 7058 
 7059      Time:     Answering Service initialization.
 7060 
 7061      Meaning:  MSG  is an   error_table_ message.   A programming
 7062                error has been encountered.
 7063 
 7064      Action:   Contact the  system programming staff.   After the
 7065                problem   is   corrected,   repeat   the  bootload
 7066                operation.
 7067 
 7068 
 7069 
 7070                [as_request_server_.pl1]
 7071                as_request_server_:   ERROR_MESSAGE.   Can't  find
 7072                message from PGID
 7073 
 7074 
 7075      Stream:   as (severity0)
 7076 
 7077      Time:     While system is running.
 7078 
 7079      Meaning:  MSG  is  an  error_table_  message  and  PGID is a
 7080                process group id.  A process  sent a wakeup to the
 7081                Answering  Service, but did  not put a  message in
 7082                as_request.ms.
 7083 
 7084      Action:   No operator action is required.
 7085 
 7086 
 7087                [as_request_server_.pl1]
 7088 
 7089 
 7090 as_request_server_             123            08/03/23     MR12.7^L
 7091 
 7092 
 7093                as_request_server_:   Message {for  "REQUEST NAME"
 7094                (type N)} too short from PERS.PROJ.
 7095 
 7096 
 7097      Stream:   as (severity0)
 7098 
 7099      Time:     While system is running.
 7100 
 7101      Meaning:  A request of  type N sent by the  process group id
 7102                specified by PERS.PROJ was  in error.  The request
 7103                is  ignored.  If the  request is shorter  than the
 7104                standard   request  header   which  precedes   all
 7105                requests, then the request  type is not present in
 7106                the message.
 7107 
 7108      Action:   No operator action is required.
 7109 
 7110 
 7111                [as_request_server_.pl1]
 7112                as_request_server_:    MSG.   Process   no  longer
 7113                active for request from PERS.PROJ.
 7114 
 7115 
 7116      Stream:   as (severity0)
 7117 
 7118      Time:     While system is running.
 7119 
 7120      Meaning:  MSG is an error_table_ message and PERS.PROJ isthe
 7121                sender  id.   A  process  sent  a  wakeup  to  the
 7122                Answering Service  but then logged out  before the
 7123                Answering Service handled the wakeup.
 7124 
 7125      Action:   No operator action is required.
 7126 
 7127 
 7128                [as_request_server_.pl1]
 7129                as_request_server_:   MSG.  Error  reading message
 7130                from message segment.
 7131 
 7132 
 7133      Stream:   as (severity0)
 7134 
 7135      Time:     While system is running.
 7136 
 7137      Meaning:  MSG is an error_table_ message.  An error occurred
 7138                while  reading an AS  message from the  AS request
 7139                queue.
 7140 
 7141      Action:   No operator action is required.
 7142 
 7143 
 7144                [as_request_server_.pl1]
 7145 
 7146 
 7147 
 7148 as_request_server_             124            08/03/23     MR12.7^L
 7149 
 7150 
 7151                as_request_server_:   Rejected   invalid  type  XX
 7152                message from PERS.PROJ PID.
 7153 
 7154 
 7155      Stream:   as (severity0)
 7156 
 7157      Time:     While system is running.
 7158 
 7159      Meaning:  An  invalid  wakeup  request   has  been  sent  to
 7160                as_request_server_.   The  sending  process  ID is
 7161                PID,  and  the  sender  name  in  the  message  is
 7162                PERS.PROJ.  The request is  a type XX request.  No
 7163                action was taken.
 7164 
 7165      Action:   No operator action is required.
 7166 
 7167 
 7168                [as_request_server_.pl1]
 7169                as_request_server_:   Request message  segment not
 7170                initialized or shutdown has been typed.
 7171 
 7172 
 7173      Stream:   as (severity1)
 7174 
 7175      Time:     While system is running.
 7176 
 7177      Meaning:  A request is being  ignored because the AS request
 7178                queue has not been initialized or the the operator
 7179                has typed the shutdown command.
 7180 
 7181      Action:   No operator action is required.
 7182 
 7183 
 7184                [as_x25_mpx_.pl1]
 7185                as_x25_mpx_:  Bad argument to parm PARM, should be
 7186                THIS or THAT, but was VALUE for multiplexer MPX.
 7187 
 7188 
 7189      Stream:   as (severity1)
 7190 
 7191      Time:     In  response to  an operator  load_mpx command  or
 7192                during system start up.
 7193 
 7194      Meaning:  A  bad value was  specified for parameter  PARM in
 7195                the additional_info field of the TTF entry for the
 7196                multiplexer  MPX.  The  choices are  THIS or THAT,
 7197                but VALUE was specified.
 7198 
 7199      Action:   Check  the  contents  of  the  TTF  entry  for the
 7200                terminal_type associated with  the multiplexer for
 7201                an improper  parameter value.  Correct  and reload
 7202                mpx.
 7203 
 7204 
 7205 
 7206 as_x25_mpx_                    125            08/03/23     MR12.7^L
 7207 
 7208 
 7209 
 7210 
 7211                [as_x25_mpx_.pl1]
 7212                as_x25_mpx_:   Bad argument   to parm  PARM.  Must
 7213                have:  LOW  <= value <=  HIGH, but value  = VALUE,
 7214                for multiplexer MPX.
 7215 
 7216 
 7217      Stream:   as (severity1)
 7218 
 7219      Time:     In  response to  an operator  load_mpx command  or
 7220                during system start up.
 7221 
 7222      Meaning:  A  bad value was  specified for parameter  PARM in
 7223                the additional_info field of the TTF entry for the
 7224                multiplexer  MPX.  The  value must  be between LOW
 7225                and HIGH, but VALUE was specified.
 7226 
 7227      Action:   Check  the  contents  of  the  TTF  entry  for the
 7228                terminal_type associated with  the multiplexer for
 7229                an improper  parameter value.  Correct  and reload
 7230                mpx.
 7231 
 7232 
 7233 
 7234                [as_x25_mpx_.pl1]
 7235                as_x25_mpx_:  Crash signalled for multiplexer MPX.
 7236 
 7237 
 7238      Stream:   as (severity1)
 7239 
 7240      Time:     While system is running.
 7241 
 7242      Meaning:  The  multiplexer has  crashed.  The  LAP link  has
 7243                entered the disconnected state.
 7244 
 7245      Action:   Contact the system programming staff.
 7246 
 7247 
 7248                [as_x25_mpx_.pl1]
 7249                as_x25_mpx_:   Error  in  conversion.   Converting
 7250                FIELD VALUE to a number for multiplexer MPX.
 7251 
 7252 
 7253      Stream:   as (severity1)
 7254 
 7255      Time:     In  response to  an operator  load_mpx command  or
 7256                during system start up.
 7257 
 7258      Meaning:  It was  impossible to convert a  numeric parameter
 7259                from  the terminal_type additional_info  string to
 7260                its  internal  form.   FIELD  is  the  name of the
 7261 
 7262 
 7263 
 7264 as_x25_mpx_                    126            08/03/23     MR12.7^L
 7265 
 7266 
 7267                parameter  in error.   VALUE is  the string  which
 7268                could not be converted.
 7269 
 7270      Action:   Check  the  contents  of  the  TTF  entry  for the
 7271                terminal_type associated with  the multiplexer for
 7272                errors.
 7273 
 7274 
 7275 
 7276                [as_x25_mpx_.pl1]
 7277                as_x25_mpx_:   ERROR.  Cannot get  additional info
 7278                for terminal type TTP for multiplexer MPX.
 7279 
 7280 
 7281      Stream:   as (severity1)
 7282 
 7283      Time:     In  response to  an operator  load_mpx command  or
 7284                during system start up.
 7285 
 7286      Meaning:  An error occurred  while retrieving the parameters
 7287                of  the  multiplexer  from  the  TTT.   Either the
 7288                terminal type specified in  the CDT does not exist
 7289                or    it   does    not   contain    the   required
 7290                additional_info field.
 7291 
 7292      Action:   Check  that the  CMF  and  TTF contain  the proper
 7293                information.
 7294 
 7295 
 7296                [as_x25_mpx_.pl1]
 7297                as_x25_mpx_:   ERROR.  Creating event  channel for
 7298                multiplexer MPX.
 7299 
 7300 
 7301      Stream:   as (severity1)
 7302 
 7303      Time:     In  response to  an operator  load_mpx command  or
 7304                during system start up.
 7305 
 7306      Meaning:  An ipc_ error occurred  while trying to initialize
 7307                the multiplexer.
 7308 
 7309      Action:   Contact the system programming staff.
 7310 
 7311 
 7312                [as_x25_mpx_.pl1]
 7313                as_x25_mpx_:  Load failed for multiplexer MPX.
 7314 
 7315 
 7316      Stream:   as (severity1)
 7317 
 7318      Time:     In  response to  an operator  load_mpx command  or
 7319                during system start up.
 7320 
 7321 
 7322 as_x25_mpx_                    127            08/03/23     MR12.7^L
 7323 
 7324 
 7325      Meaning:  The attempt to load  the multiplexer failed.  This
 7326                should never happen.
 7327 
 7328      Action:   Contact the system programming staff.
 7329 
 7330 
 7331                [as_x25_mpx_.pl1]
 7332                as_x25_mpx_:  Load signalled for multiplexer MPX.
 7333 
 7334 
 7335      Stream:   as (severity1)
 7336 
 7337      Time:     In  response to  an operator  load_mpx command  or
 7338                during system start up.
 7339 
 7340      Meaning:  The multiplexer has  been successfully loaded.  It
 7341                will  be  started  unless  the  -no_start  control
 7342                argument was  given when the load_mpx  command was
 7343                typed.
 7344 
 7345      Action:   No operator action is required.
 7346 
 7347 
 7348                [as_x25_mpx_.pl1]
 7349                as_x25_mpx_:  MPX:  n_lc must be specified.
 7350 
 7351 
 7352      Stream:   as (severity1)
 7353 
 7354      Time:     In  response to  an operator  load_mpx command for
 7355                during system startup.
 7356 
 7357      Meaning:  The  TTF entry for  the X.25 multiplexer  does not
 7358                specify the number of logical channels.
 7359 
 7360      Action:   Correct the TTF and reload the multiplexer.
 7361 
 7362 
 7363                [as_x25_mpx_.pl1]
 7364                as_x25_mpx_:   Unexpected  signal   NUM  in  state
 7365                STATE.
 7366 
 7367 
 7368      Stream:   as (severity1)
 7369 
 7370      Time:     While system is running.
 7371 
 7372      Meaning:  A signal, NUM, was  received unexpectedly in state
 7373                STATE.  The signal is ignored.
 7374 
 7375      Action:   Contact the system programming staff.
 7376 
 7377 
 7378 
 7379 
 7380 as_x25_mpx_                    128            08/03/23     MR12.7^L
 7381 
 7382 
 7383                [as_x25_mpx_.pl1]
 7384                as_x25_mpx_:    Unexpected   wakeup   (DATA)  from
 7385                process PRCID.
 7386 
 7387 
 7388      Stream:   as (severity1)
 7389 
 7390      Time:     While system is running.
 7391 
 7392      Meaning:  The multiplexer manager received  a wakeup from an
 7393                unexpected source.  The wakeup is ignored.
 7394 
 7395      Action:   No operator action is required.
 7396 
 7397 
 7398                [as_x25_mpx_.pl1]
 7399                as_x25_mpx_:   Wakeup  for   multiplexer  MPX  has
 7400                invalid state code STATE.
 7401 
 7402 
 7403      Stream:   as (severity1)
 7404 
 7405      Time:     While system is running.
 7406 
 7407      Meaning:  A  wakeup with  invalid data  was received  by the
 7408                multiplexer manager.  The wakeup is ignored.
 7409 
 7410      Action:   Contact the system programming staff.
 7411 
 7412 
 7413                [asr_abs_command_server_.pl1]
 7414                asr_abs_command_server_:    Request  REQUEST   not
 7415                found, could not cancel for USER.
 7416 
 7417 
 7418      Stream:   as (severity0)
 7419 
 7420      Time:     While system is running.
 7421 
 7422      Meaning:  User USER  requested cancellation of  absentee job
 7423                REQUEST which did not exist.
 7424 
 7425      Action:   No operator action is required.
 7426 
 7427 
 7428                [asr_daemon_command_server_.pl1]
 7429                asr_daemon_command_server_:                 Denied
 7430                send_daemon_command for USER in ring RING.
 7431 
 7432 
 7433      Stream:   $sc
 7434 
 7435      Time:     While system is running.
 7436 
 7437 
 7438 asr_daemon_command_server_     129            08/03/23     MR12.7^L
 7439 
 7440 
 7441      Meaning:  User USER requested the system to execute a daemon
 7442                command,      but       lacked      access      to
 7443                >sc1>admin_acs>send_admin_command.acs    or    the
 7444                appropriate daemon source ACS.
 7445 
 7446      Action:   No operator action is required.
 7447 
 7448 
 7449                [asr_daemon_command_server_.pl1]
 7450                asr_daemon_command_server_:    Failed   to   check
 7451                access for USER.
 7452 
 7453 
 7454      Stream:   $sc
 7455 
 7456      Time:     While system is running.
 7457 
 7458      Meaning:  User USER requested the system to execute a daemon
 7459                command,  but   validate_daemon_commands  was  not
 7460                enabled and  the system could not  determine their
 7461                access to the send_daemon_command acs.
 7462 
 7463      Action:   No operator action is required.
 7464 
 7465 
 7466                [asr_daemon_command_server_.pl1]
 7467                asr_daemon_command_server_:  PERSON:  COMMAND INFO
 7468 
 7469 
 7470      Stream:   $sc
 7471 
 7472      Time:     While system is running.
 7473 
 7474      Meaning:  A system administrator has sent  a for a daemon to
 7475                the Initializer, which executes it.
 7476 
 7477      Action:   No operator action is required.
 7478 
 7479 
 7480                [astty_.pl1]
 7481                astty_:  ERROR_TABLE_MESSAGE CHANNEL has undefined
 7482                terminal type TERM_TYPE for set_term_type order.
 7483 
 7484 
 7485      Stream:   as (severity 0) or $as1
 7486 
 7487      Time:     While system is running.
 7488 
 7489      Meaning:  The  system received the  ERROR_TABLE_MESSAGE when
 7490                an attempt  was made to  set the terminal  type of
 7491                CHANNEL to  TERM_TYPE.  Suspect the  terminal type
 7492                is not known on  to the system.  The set_term_type
 7493                control order was ignored.
 7494 
 7495 
 7496 astty_                         130            08/03/23     MR12.7^L
 7497 
 7498 
 7499      Action:   Contact the system programming staff.
 7500 
 7501 
 7502                [astty_.pl1]
 7503                astty_:  ERROR_TABLE_MESSAGE CHANNEL NN TEXT
 7504 
 7505 
 7506      Stream:   as (severity 0) or $as1
 7507 
 7508      Time:     While system is running.
 7509 
 7510      Meaning:  This  is tracing  or error  logging output.   This
 7511                output may appear in the  AS log, or be printed on
 7512                the severity1  stream as directed by  astty_ trace
 7513                and log_error requests described below.
 7514 
 7515      Action:   No  operator  action  is  required.   Tracing  and
 7516                logging  is controlled  by the  following entries,
 7517                which may be typed as commands in admin mode.
 7518                astty_$trace  -  causes  tracing  of  all calls to
 7519                astty_
 7520                astty_$notrace - disables tracing
 7521                astty_$log_error -  logs calls to astty_  that get
 7522                errors.  does not print.
 7523                astty_$log_error_1  -  logs  and  prints  calls to
 7524                astty_ that get errors.
 7525                astty_$no_log_error - disables error logging.
 7526 
 7527 
 7528 
 7529                [astty_.pl1]
 7530                astty_:     ERROR_TABLE_MESSAGE    CHANNEL    SSSS
 7531                line_status failed after line_status_pending
 7532 
 7533 
 7534      Stream:   as (severity 0) or $as1
 7535 
 7536      Time:     While system is running.
 7537 
 7538      Meaning:  System  received the  ERROR_TABLE_MESSAGE when  it
 7539                tried to do a line status control order on CHANNEL
 7540                in    state    SSSS    after    it    received   a
 7541                line_status_pending  error code.   The error  code
 7542                for ERROR_TABLE_MESSAGE  was returned back  to the
 7543                caller.
 7544 
 7545      Action:   Contact the system programming staff.
 7546 
 7547 
 7548                [astty_.pl1]
 7549                astty_:  ERROR_TABLE_MESSAGE CHANNEL  state SSSS >
 7550                TTY_HUNG on hung-up error code.
 7551 
 7552 
 7553 
 7554 astty_                         131            08/03/23     MR12.7^L
 7555 
 7556 
 7557      Stream:   as (severity 0) or $as1
 7558 
 7559      Time:     While system is running.
 7560 
 7561      Meaning:  An error code  of ERROR_TABLE_MESSAGE was returned
 7562                while   servicing  CHANNEL  indicating   that  the
 7563                channel is  not useable.  However, the  state SSSS
 7564                of  the  channel  indicates  that  the channel was
 7565                active,  thus the  CHANNEL state  is inconsistant.
 7566                The channel will be hungup.
 7567 
 7568      Action:   Contact the system programming staff.
 7569 
 7570 
 7571                [astty_.pl1]
 7572                astty_:  ERROR_TABLE_MESSAGE  error attaching IOCB
 7573                for channel CCCC.
 7574 
 7575 
 7576      Stream:   as (severity 0) or $as1
 7577 
 7578      Time:     While system is running.
 7579 
 7580      Meaning:  The   system   received   the  ERROR_TABLE_MESSAGE
 7581                attempting  to  attach  to  channel  CCCC using an
 7582                IOCB.  The channel was then hungup.
 7583 
 7584      Action:   Contact the system programming staff.
 7585 
 7586 
 7587                [astty_.pl1]
 7588                astty_:  ERROR_TABLE_MESSAGE error finding an IOCB
 7589                for channel CCCC.
 7590 
 7591 
 7592      Stream:   as (severity 0) or $as1
 7593 
 7594      Time:     While system is running.
 7595 
 7596      Meaning:  The  system received the  ERROR_TABLE_MESSAGE when
 7597                it  attempted to  find an  IOCB for  channel CCCC.
 7598                The channel was then hungup.
 7599 
 7600      Action:   Contact the system programming staff.
 7601 
 7602 
 7603                [astty_.pl1]
 7604                astty_:   ERROR_TABLE_MESSAGE  error  opening IOCB
 7605                for channel CCCC.
 7606 
 7607 
 7608      Stream:   as (severity 0) or $as1
 7609 
 7610 
 7611 
 7612 astty_                         132            08/03/23     MR12.7^L
 7613 
 7614 
 7615      Time:     While system is running.
 7616 
 7617      Meaning:  The   system   received   the   ERROR_TALE_MESSAGE
 7618                attemping to open the  channel CCCC using an IOCB.
 7619                The channel was then hungup.
 7620 
 7621      Action:   Contact the system programming staff.
 7622 
 7623 
 7624                [astty_.pl1]
 7625                astty_:  tty_state returned  SSSS for hung-up line
 7626                CHANNEL.
 7627 
 7628 
 7629      Stream:   as (severity 0) or $as1
 7630 
 7631      Time:     While system is running.
 7632 
 7633      Meaning:  In processing  the astty_$tty_state entry,  a call
 7634                to hcs_$tty_state  returned a state value  of SSSS
 7635                for  hung-up  CHANNEL  which  indicates  that  the
 7636                channel  is active.   However, the  returned error
 7637                code indicated  that the channel is  hung-up.  The
 7638                channel will be hungup.
 7639 
 7640      Action:   Contact the system programming staff.
 7641 
 7642 
 7643                [asu_.pl1]
 7644                asu_$release_ate:  bad cdte.process (LOCATION) for
 7645                CHANNEL
 7646 
 7647 
 7648      Stream:   as (severity 0)
 7649 
 7650      Time:     While system is running.
 7651 
 7652      Meaning:  This indicates a logic error in the supervisor, or
 7653                CPU  or memory  hardware problems.   When asked to
 7654                release   a  User   Table  Entry   (UTE)  for   an
 7655                interactive  process,   the  cdte.process  pointer
 7656                (LOCATION)  did not  point into  the answer table.
 7657                The UTE was not released.
 7658 
 7659      Action:   No operator action is required.
 7660 
 7661 
 7662                [asu_.pl1]
 7663                asu_$release_suspended_process:     PERSON.PROJECT
 7664                CHANNEL is not suspended
 7665 
 7666 
 7667      Stream:   as (severity 0)
 7668 
 7669 
 7670 asu_$release_suspended_process 133            08/03/23     MR12.7^L
 7671 
 7672 
 7673      Time:     Called  in response  to an  operator "abs release"
 7674                command, or in response  to a user reconnecting to
 7675                an interactive process.
 7676 
 7677      Meaning:  One  of   the  process  termination   handlers  is
 7678                incorrectly calling to release  a process which is
 7679                not currently suspended.
 7680 
 7681      Action:   No operator action is required.
 7682 
 7683 
 7684                [asu_.pl1]
 7685                asu_$remote_cdte:   ERROR_MESSAGE.   cdte  CCC|XXX
 7686                error from tty_state
 7687 
 7688 
 7689      Stream:   as (severity0)
 7690 
 7691      Time:     While system is running.
 7692 
 7693      Meaning:  Remove_cdte is trying to get rid of a channel.  It
 7694                cannot obtain the line state.
 7695 
 7696      Action:   No operator action is required.
 7697 
 7698 
 7699                [asu_.pl1]
 7700                asu_$suspend_process:   PERSON.PROJECT CHANNEL  is
 7701                already suspended
 7702 
 7703 
 7704      Stream:   as (severity 1)
 7705 
 7706      Time:     asu_$suspend_process  was  called  by  one  of the
 7707                process   termination  handlers   to  suspend   an
 7708                interactive  process whose  terminal disconnected,
 7709                or to suspend an absentee process via the operator
 7710                "abs suspend" command.
 7711 
 7712      Meaning:  The  process is   already suspended.   The current
 7713                request will be ignored.
 7714 
 7715      Action:   No operator action is required.
 7716 
 7717 
 7718                [asu_.pl1]
 7719                asu_:  attach channel not done on CHANNEL; service
 7720                type = TYPE
 7721 
 7722 
 7723      Stream:   as (severity 0)
 7724 
 7725      Time:     When attaching channels to the Answering Service.
 7726 
 7727 
 7728 asu_                           134            08/03/23     MR12.7^L
 7729 
 7730 
 7731      Meaning:  The CHANNEL was found in an inactive state (TYPE =
 7732                INACTIVE),  or  was  found  to  be  a  multiplexer
 7733                channel   (TYPE  =   MULTIPLEXER).   It   was  not
 7734                attached.This  indicates  a  logic  error  in  the
 7735                supervisor, or CPU or memory hardware problems.
 7736 
 7737      Action:   No operator action is required.
 7738 
 7739 
 7740                [asu_.pl1]
 7741                asu_:  listen not done on CHANNEL; current service
 7742                type = TYPE
 7743 
 7744 
 7745      Stream:   as (severity 0)
 7746 
 7747      Time:     When the Answering Service  tried to listen to the
 7748                channel.
 7749 
 7750      Meaning:  The CHANNEL was found in an inactive state (TYPE =
 7751                INACTIVE), was  found to be a  multiplexer channel
 7752                (TYPE =  MULTIPLEXER), was found  to be in  use by
 7753                the message coordinator (TYPE  = MC), or was found
 7754                to be attached for Testing and Diagnostics (TYPE =
 7755                TANDD_SERVICE).   The  attempt  to  listen  on the
 7756                channel failed.This indicates a logic error in the
 7757                supervisor, or CPU or memory hardware problems.
 7758 
 7759      Action:   No operator action is required.
 7760 
 7761 
 7762                [asu_.pl1]
 7763                asu_:  (called by PROCEDURE)  USER PROJ CHN is not
 7764                stopped (state = S) even  though destroy flag = D;
 7765                it might not be possible to destroy this process
 7766 
 7767 
 7768 
 7769      Stream:   as (severity1)
 7770 
 7771      Time:     In response to an operator  command to bump or log
 7772                out an interactive, absentee, or daemon user.
 7773 
 7774      Meaning:  The process  being bumped or logged  out was found
 7775                to be partially logged out already, but not in the
 7776                stopped state.  An attempt will be made to destroy
 7777                this process, but it might fail.
 7778 
 7779      Action:   Contact the system programming staff.
 7780 
 7781 
 7782                [asu_.pl1]
 7783                asu_:   (called by   PROCEDURE) USER.PROJ  CHN was
 7784 
 7785 
 7786 asu_                           135            08/03/23     MR12.7^L
 7787 
 7788 
 7789                already  stopped and  will be  destroyed (stopstop
 7790                wakeup was lost)
 7791 
 7792 
 7793      Stream:   as (severity1)
 7794 
 7795      Time:     In response to an operator  command to bump or log
 7796                out an interactive, absentee, or daemon user.
 7797 
 7798      Meaning:  The process  being bumped or logged  out was found
 7799                to be in the stopped state (partially logged out).
 7800                A  wakeup  from  ring  zero  indicating  that  the
 7801                process  was stopped  and could  be destroyed  was
 7802                apparently lost.  Destruction  of the process will
 7803                be completed.
 7804 
 7805      Action:   Contact the system programming staff.
 7806 
 7807 
 7808                [asu_.pl1]
 7809                asu_:  cdte CCC|XXX (CHANNEL) hung up
 7810 
 7811 
 7812      Stream:   as (severity0)
 7813 
 7814      Time:     While system is running.
 7815 
 7816      Meaning:  Remove_cdte  is trying  to get  rid of  a channel.
 7817                The indicated CHANNEL is in the hung up state.
 7818 
 7819      Action:   No operator action is required.
 7820 
 7821 
 7822                [asu_.pl1]
 7823                asu_:  cdte CCC|XXX (CHANNEL) state A in use B tra
 7824                vec C
 7825 
 7826 
 7827      Stream:   as (severity0)
 7828 
 7829      Time:     While system is running.
 7830 
 7831      Meaning:  Remove_cdte is trying to get rid of a channel.  It
 7832                first logs the state of the line.
 7833 
 7834      Action:   No operator action is required.
 7835 
 7836 
 7837                [asu_.pl1]
 7838                asu_:  cdtep (CCC|ZZZ) not cdt (YYY|0)
 7839 
 7840 
 7841      Stream:   as (severity0)
 7842 
 7843 
 7844 asu_                           136            08/03/23     MR12.7^L
 7845 
 7846 
 7847      Time:     While system is running.
 7848 
 7849      Meaning:  This indicates a logic error in the supervisor, or
 7850                CPU or  memory hardware problems.   Remove_cdte is
 7851                trying to get rid of a channel which is no good.
 7852 
 7853      Action:   No operator action is required.
 7854 
 7855 
 7856                [asu_.pl1]
 7857                asu_:   CHANNEL  cannot  be  attached  because its
 7858                service type is TYPE (N).
 7859 
 7860 
 7861      Stream:   as (severity1)
 7862 
 7863      Time:     While system is running.
 7864 
 7865      Meaning:  An  attach  command   specified  a  CHANNEL  whose
 7866                service  type does not  permit it to  be attached.
 7867                No action was taken.
 7868 
 7869      Action:   Enter a correct command.
 7870 
 7871 
 7872                [asu_.pl1]
 7873                asu_:    CHANNEL  has   been  deleted   by  a  CDT
 7874                installation and so cannot be attached.
 7875 
 7876 
 7877 
 7878      Stream:   as (severity1)
 7879 
 7880      Time:     While system is running.
 7881 
 7882      Meaning:  An  attach command  specified a  CHANNEL that  has
 7883                been deleted.  No action was taken.
 7884 
 7885      Action:   Enter a correct command.
 7886 
 7887 
 7888                [asu_.pl1]
 7889                asu_:  CHANNEL has in_use =  N, current state = S,
 7890                {CDTE.state was OS}
 7891 
 7892 
 7893      Stream:   as (severity 1)
 7894 
 7895      Time:     When the operator attempts to attach the channel.
 7896 
 7897      Meaning:  The  Channel  Definition  Table  (CDT)  entry  for
 7898                CHANNEL   is  in   an  inconsistent   state.   See
 7899                dialup_values.incl.pl1  for a  description of  the
 7900 
 7901 
 7902 asu_                           137            08/03/23     MR12.7^L
 7903 
 7904 
 7905                in_use and  state values.  The old  state value OS
 7906                is displayed  only if it differs  from the current
 7907                state.
 7908 
 7909      Action:   Enter a corrected command line.
 7910 
 7911 
 7912                [asu_.pl1]
 7913                asu_:  CHANNEL in use  as a multiplexer and cannot
 7914                be attached.
 7915 
 7916 
 7917      Stream:   as (severity 0)
 7918 
 7919      Time:     When  issuing  an  operator  attach  command for a
 7920                channel.
 7921 
 7922      Meaning:  CHANNEL is operating  as a multiplexer, supporting
 7923                one  or  more  channels.   It  cannot  be attached
 7924                directly.  The attach operation fails.
 7925 
 7926      Action:   Enter a corrected command line.
 7927 
 7928 
 7929                [asu_.pl1]
 7930                asu_:   CHANNEL in  use for  T &  D and  cannot be
 7931                attached.
 7932 
 7933 
 7934      Stream:   as (severity1)
 7935 
 7936      Time:     While system is running.
 7937 
 7938      Meaning:  An  operator attach   command specified  a CHANNEL
 7939                being  tested via   Test and  Diagnostic routines.
 7940                The channel was not attached.
 7941 
 7942      Action:   Enter a corrected command line.
 7943 
 7944 
 7945                [asu_.pl1]
 7946                asu_:   CHANNEL  is  a  multiplexer  and cannot be
 7947                removed.
 7948 
 7949 
 7950      Stream:   as (severity 1)
 7951 
 7952      Time:     When the operator attempts to remove a channel.
 7953 
 7954      Meaning:  CHANNEL  is a   multiplexer channel  which handles
 7955                data   for   one   or   more   subchannels.   Such
 7956                multiplexers  are not   attached by  the Answering
 7957                Service, and therefore cannot be removed.
 7958 
 7959 
 7960 asu_                           138            08/03/23     MR12.7^L
 7961 
 7962 
 7963      Action:   Enter a corrected command line.
 7964 
 7965                Message:       asu_$bump_user:      ERROR_MESSAGE.
 7966                BLAST_MESSAGE.     Sending   blast    message   to
 7967                PERSON.PROJECT on CHANNEL
 7968 
 7969      Stream:   as (severity 0)
 7970 
 7971      Time:     While system is running.
 7972 
 7973      Meaning:  An  error  occurred  while  attempting  to send an
 7974                operator  warning  message  to  PERSON.PROJECT  on
 7975                CHANNEL.   ERROR_MESSAGE  is  the  text associated
 7976                with the  error which occurred.   BLAST_MESSAGE is
 7977                the undelivered operator warning.
 7978 
 7979      Action:   No operator action is required.
 7980 
 7981 
 7982                [asu_.pl1]
 7983                asu_:   CHANNEL is  already attached;  will try to
 7984                listen to it again
 7985 
 7986 
 7987      Stream:   as (severity 1)
 7988 
 7989      Time:     When the operator attempts to attach a channel.
 7990 
 7991      Meaning:  The CHANNEL was already  attached by the Answering
 7992                Service,  but was  not dialed  up.  The  Answering
 7993                Service will attempt to  listen for dialups on the
 7994                channel.
 7995 
 7996      Action:   Enter a corrected command line.
 7997 
 7998 
 7999                [asu_.pl1]
 8000                asu_:    CHANNEL  is   in  use   by  the   message
 8001                coordinator and cannot be attached.
 8002 
 8003 
 8004      Stream:   as (severity1)
 8005 
 8006      Time:     While system is running.
 8007 
 8008      Meaning:  An  operator attach   command specified  a message
 8009                coordinator   CHANNEL.    The   channel   was  not
 8010                attached.
 8011 
 8012      Action:   Enter a correct command.
 8013 
 8014 
 8015                [asu_.pl1]
 8016 
 8017 
 8018 asu_                           139            08/03/23     MR12.7^L
 8019 
 8020 
 8021                asu_:   CHANNEL is  not in  CDT and  so cannot  be
 8022                attached
 8023 
 8024 
 8025      Stream:   as (severity1)
 8026 
 8027      Time:     While system is running.
 8028 
 8029      Meaning:  An  attach command  specified an  unknown CHANNEL.
 8030                No action was taken.
 8031 
 8032      Action:   Enter a correct command.
 8033 
 8034 
 8035                [asu_.pl1]
 8036                asu_:   CHANNEL  was  not  configured  at bootload
 8037                time, and so cannot be attached.
 8038 
 8039 
 8040 
 8041      Stream:   as (severity1)
 8042 
 8043      Time:     While system is running.
 8044 
 8045      Meaning:  An attach command specified  a CHANNEL that cannot
 8046                be  used until the  next bootload.  No  action was
 8047                taken.
 8048 
 8049      Action:   Enter a correct command.
 8050 
 8051 
 8052                [asu_.pl1]
 8053                asu_:  ENTRYPOINT called with null UTE ptr.
 8054 
 8055 
 8056      Stream:   as (severity0)
 8057 
 8058      Time:     ENTRYPOINT     may    be     suspend_process    or
 8059                setup_login_server_handle.    suspend_process  was
 8060                called by one of  the process termination handlers
 8061                to suspend  an interactive process  whose terminal
 8062                disconnected,  or to  suspend an  absentee process
 8063                via   the   operator    "abs   suspend"   command.
 8064                setup_login_server_handler was  called in response
 8065                to  a  validate,  connect,  new_proc,  or  destroy
 8066                request from a login server.
 8067 
 8068      Meaning:  Programming  error  in   the  process  termination
 8069                handlers,  or  the  login  server  support  of the
 8070                Answering Service.
 8071 
 8072      Action:   Contact the system programming staff.
 8073 
 8074 
 8075 
 8076 asu_                           140            08/03/23     MR12.7^L
 8077 
 8078 
 8079 
 8080 
 8081                [asu_.pl1]
 8082                asu_:  ERROR_MESSAGE.  ENTRY OPERATION error; will
 8083                remove channel CHANNEL DESC
 8084 
 8085 
 8086 
 8087      Stream:   as (severity1)
 8088 
 8089      Time:     While system is running.
 8090 
 8091      Meaning:  A channel error has  occurred on CHANNEL.  DESC is
 8092                the  comment field  for the  channel given  in its
 8093                Channel    Definition     Table    (CDT)    entry.
 8094                ERROR_MESSAGE gives the  text describing the error
 8095                code  returned  by   the  operation  in  progress.
 8096                OPERATION       may        be       create_ev_chn,
 8097                decl_event_call_chn,     listen,    set_term_type,
 8098                tty_event   or  tty_index,   dependent  upon   the
 8099                operation  in progress   when the  error occurred.
 8100                ENTRY  specifies  the  asu_  entrypoint  that  was
 8101                running  when the  operation was  performed on the
 8102                channel.  It may  be asu_listen or attach_channel.
 8103                The channel will be removed from use.
 8104 
 8105      Action:   It may be necessary to  busy out the modem for the
 8106                channel.
 8107 
 8108 
 8109                [asu_.pl1]
 8110                asu_:   ERROR_MESSAGE.  Sending initial  wakeup to
 8111                PROCESS_ID (PERSON.PROJECT)
 8112 
 8113 
 8114      Stream:   as (severity 0)
 8115 
 8116      Time:     Called  at process  creation to  start the process
 8117                running.
 8118 
 8119      Meaning:  ERROR_MESSAGE  is  the  text  of  an  error  which
 8120                occurred   attempting   to   send   a   wakeup  to
 8121                PERSON.PROJECT.   As  a   result  of  this  error,
 8122                process creation will fail.
 8123 
 8124      Action:   No operator action is required.
 8125 
 8126 
 8127                [asu_.pl1]
 8128                asu_:   ERROR_MESSAGE.  Retrieving  the values  of
 8129                R-0ffset     and    R-Factor     for    PROCESS_ID
 8130                (PERSON.PROJECT).
 8131 
 8132 
 8133 
 8134 asu_                           141            08/03/23     MR12.7^L
 8135 
 8136 
 8137      Stream:   as (severity 0)
 8138 
 8139      Time:     Called at process creation.
 8140 
 8141      Meaning:  asu_$start_process called hphcs_$get_ipc_operands.
 8142                This call failed with an error whose text is shown
 8143                as ERROR_MESSAGE.   As a result, the  process will
 8144                not be started.
 8145 
 8146      Action:   No operator action is required.
 8147 
 8148 
 8149                [asu_.pl1]
 8150                asu_:  listen failed on CHANNEL:  state = N
 8151 
 8152 
 8153      Stream:   as (severity 0)
 8154 
 8155      Time:     When  attempting  to  listen  for  dialups  on the
 8156                channel.
 8157 
 8158      Meaning:  The  Channel  Definition  Table  (CDT)  entry  for
 8159                CHANNEL  has an  invalid state  value N.   Channel
 8160                listening will not occur.
 8161 
 8162      Action:   No operator action is required.
 8163 
 8164 
 8165                [asu_.pl1]
 8166                asu_:   listen not  done on  CHANNEL:  IN_USE with
 8167                state  =   STATE,  in_use  =  IN_USE,   tra_vec  =
 8168                CURRENT_OPERATION
 8169 
 8170 
 8171 
 8172      Stream:   as (severity 0)
 8173 
 8174      Time:     When the Answering Service  tries to listen to the
 8175                channel.
 8176 
 8177      Meaning:  The  Channel  Definition  Table  (CDT)  entry  for
 8178                CHANNEL   is  in   an  inconsistent   state.   See
 8179                dialup_values.incl.pl1  for a  description of  the
 8180                state, in_use and tra_vec values.
 8181 
 8182      Action:   No operator action is required.
 8183 
 8184 
 8185                [asu_.pl1]
 8186                asu_:  lock  was N, ev  call mask was  M, ips mask
 8187                was ZZZZZZ
 8188 
 8189 
 8190 
 8191 
 8192 asu_                           142            08/03/23     MR12.7^L
 8193 
 8194 
 8195      Stream:   as (severity1)
 8196 
 8197      Time:     In response to an operator reset command.
 8198 
 8199      Meaning:  N  is the  value  of  anstbl.lock_value, M  is the
 8200                value of  event call masking.  ZZZZZZ  was the ips
 8201                mask.   This  message   verifies  that  the  reset
 8202                command was given, and what effect it had.
 8203 
 8204      Action:   No operator action is required.
 8205 
 8206 
 8207                [asu_.pl1]
 8208                asu_:  MESSAGE.  unable to unmask channel CHANNEL.
 8209 
 8210 
 8211      Stream:   as (severity1)
 8212 
 8213      Time:     In  response to  an operator  command to  attach a
 8214                channel which had been masked by MCS.
 8215 
 8216      Meaning:  The CHANNEL could not be unmasked.
 8217 
 8218      Action:   Contact the system programming staff.
 8219 
 8220 
 8221                [asu_.pl1]
 8222                asu_:  Unable to create  event channel for new UTE
 8223                LOCATION
 8224 
 8225 
 8226      Stream:   as (severity 2)
 8227 
 8228      Time:     While system is running.
 8229 
 8230      Meaning:  This indicates a logic error in the supervisor, or
 8231                CPU or memory hardware problems.
 8232 
 8233      Action:   Contact the system programming staff.
 8234 
 8235 
 8236                [asu_.pl1]
 8237                asu_:  unmasking channel CHANNEL.
 8238 
 8239 
 8240      Stream:   as (severity1)
 8241 
 8242      Time:     In  response to  an operator  command to  attach a
 8243                channel which has been masked by MCS.
 8244 
 8245      Meaning:  A  special  order  is  issued  to  MCS  to  unmask
 8246                CHANNEL, and the channel  should then be available
 8247                for regular use.
 8248 
 8249 
 8250 asu_                           143            08/03/23     MR12.7^L
 8251 
 8252 
 8253      Action:   No operator action is required.
 8254 
 8255 
 8256                [asum_inner_ring_caller_.pl1]
 8257                asum_inner_ring_caller_:    ASUM  database   found
 8258                locked after return from call by GROUP_ID
 8259 
 8260 
 8261 
 8262      Stream:   BOS Typewriter.
 8263 
 8264      Time:     While system is running.
 8265 
 8266      Meaning:  This indicates a logic error in the supervisor, or
 8267                CPU  or  memory  hardware  problems.   The AS user
 8268                message facility  was called and upon  return from
 8269                the      call       the      transfer      routine
 8270                asum_inner_ring_caller_  detected  that  the  ASUM
 8271                database
 8272                (>sc1>user_messages>as_user_message_system)    was
 8273                left locked.   The lock has been  unlocked but the
 8274                database may  be inconsistent.  This  should never
 8275                happen and if it does, indicates a coding error in
 8276                the AS user message facility.
 8277 
 8278      Action:   Contact the system programming staff.
 8279 
 8280 
 8281                [operator_com_channel_cmds_.pl1]
 8282                attach:  Action not performed.  ttyXXX
 8283 
 8284 
 8285      Stream:   as (severity1).
 8286 
 8287      Time:     In response to an operator attach command.
 8288 
 8289      Meaning:  This is  the response to attach TTYxxx  if no more
 8290                room is available in  the answer table for channel
 8291                entries.  The line is not attached.
 8292 
 8293      Action:   Contact the system programming staff.
 8294 
 8295 
 8296                [operator_com_channel_cmds_.pl1]
 8297                attach:  bad arg "AAAA"
 8298 
 8299 
 8300      Stream:   as (severity1).
 8301 
 8302      Time:     In response to an operator command.
 8303 
 8304      Meaning:  A  bad  argument  was  furnished  with  an  attach
 8305                command.  The argument is skipped.
 8306 
 8307 
 8308 attach                         144            08/03/23     MR12.7^L
 8309 
 8310 
 8311      Action:   Enter a corrected command.
 8312 
 8313 
 8314                [operator_com_channel_cmds_.pl1]
 8315                attach:  error:  not done
 8316 
 8317 
 8318      Stream:   as (severity1).
 8319 
 8320      Time:     In response to an operator command.
 8321 
 8322      Meaning:  Bad arguments were given to an attach command.  No
 8323                action resulted.
 8324 
 8325      Action:   Enter a corrected command line.
 8326 
 8327 
 8328                [operator_com_channel_cmds_.pl1]
 8329                attach:  TTYxxx attached
 8330 
 8331 
 8332      Stream:   as (severity1).
 8333 
 8334      Time:     In response to an operator attach command.
 8335 
 8336      Meaning:  This is the response  to an attach TTYxxx command.
 8337                The  device  channel  is   now  connected  to  the
 8338                Answering Service and ready for dialups.
 8339 
 8340      Action:   No operator action is required.
 8341 
 8342 
 8343                [terminate_proc.pl1]
 8344                attempt to terminate an idle process
 8345 
 8346 
 8347      Stream:   BOS Typewriter (Crashes system)
 8348 
 8349      Time:     While system is running.
 8350 
 8351      Meaning:  This indicates a logic error in the supervisor, or
 8352                CPU or memory hardware problems.
 8353 
 8354      Action:   Follow normal recovery procedures.
 8355 
 8356 
 8357                [terminate_proc.pl1]
 8358                attempt to terminate initializer process
 8359 
 8360 
 8361      Stream:   BOS Typewriter (Crashes system)
 8362 
 8363      Time:     While system is running.
 8364 
 8365 
 8366 attempt                        145            08/03/23     MR12.7^L
 8367 
 8368 
 8369      Meaning:  This indicates a logic error in the supervisor, or
 8370                CPU or memory hardware problems.
 8371 
 8372      Action:   Follow normal recovery procedures.
 8373 
 8374 
 8375                [terminate_proc.pl1]
 8376                attempt to terminate process with TYPE lock set
 8377 
 8378 
 8379      Stream:   BOS Typewriter (Crashes system)
 8380 
 8381      Time:     While system is running.
 8382 
 8383      Meaning:  This indicates a logic error in the supervisor, or
 8384                CPU or memory hardware problems.
 8385 
 8386      Action:   Follow normal recovery procedures.
 8387 
 8388 
 8389                [access_audit_util_.pl1]
 8390                AUDIT (access_audit_util_):   GRANTED modification
 8391                of process audit flags ADDED_INFO
 8392 
 8393 
 8394      Stream:   $access_audit
 8395 
 8396      Time:     While system is running.
 8397 
 8398      Meaning:  The  specified  user   has  invoked  a  privileged
 8399                operation to change the process audit flags.  This
 8400                may result in more or less audit messages for that
 8401                user.
 8402 
 8403      Action:   Contact the system programming staff._ssa
 8404 
 8405 
 8406                [access_class_check.pl1]
 8407                AUDIT (access_class_check):   GRANTED modification
 8408                of security out_of_service ADDED_INFO
 8409 
 8410 
 8411      Stream:   $access_audit
 8412 
 8413      Time:     While system is running.
 8414 
 8415      Meaning:  The  soos switch for  the specified path  has been
 8416                turned on or off  by the security administrator as
 8417                indicated.
 8418 
 8419      Action:   No operator action is required.
 8420 
 8421 
 8422 
 8423 
 8424 AUDIT (create_vtoce)           146            08/03/23     MR12.7^L
 8425 
 8426 
 8427                [create_vtoce.pl1]
 8428                AUDIT  (create_vtoce):   DENIED  creation  of file
 8429                system object ADDED_INFO entry class range outside
 8430                LV (CLASS_RANGE lvid LVID)
 8431 
 8432 
 8433      Stream:   $access_audit
 8434 
 8435      Time:     While system is running.
 8436 
 8437      Meaning:  The specified  user attempted to create  a segment
 8438                whose access  class is outside the  range accepted
 8439                by the logical volume.
 8440 
 8441      Action:   Contact the system programming staff._ssa
 8442 
 8443 
 8444                [fim.alm]
 8445                AUDIT  (fim):   access   violation  fault  -  mode
 8446                ADDED_INFO
 8447 
 8448 
 8449 
 8450      Stream:   $access_audit
 8451 
 8452      Time:     While system is running.
 8453 
 8454      Meaning:  The  specified process   took an  access violation
 8455                fault "  because the access mode  was inconsistant
 8456                with the operation.
 8457 
 8458      Action:   No operator action is required.
 8459 
 8460 
 8461                [fim.alm]
 8462                AUDIT  (fim):   access   violation  fault  -  ring
 8463                ADDED_INFO
 8464 
 8465 
 8466 
 8467      Stream:   $access_audit
 8468 
 8469      Time:     While system is running.
 8470 
 8471      Meaning:  The  specified process   took an  access violation
 8472                fault " due to ring brackets inconsistant with the
 8473                operation.
 8474 
 8475      Action:   No operator action is required.
 8476 
 8477 
 8478                [fim.alm]
 8479                AUDIT (fim):  illegal procedure fault ADDED_INFO
 8480 
 8481 
 8482 AUDIT (fim)                    147            08/03/23     MR12.7^L
 8483 
 8484 
 8485      Stream:   $access_audit
 8486 
 8487      Time:     While system is running.
 8488 
 8489      Meaning:  The  specified process  took an  illegal procedure
 8490                fault.
 8491 
 8492      Action:   No operator action is required.
 8493 
 8494 
 8495                [mseg_message_.pl1]
 8496                Audit  (mseg_$add_message):  DENIED addition  of a
 8497                message to  a message segment  ADDED_INFO <Message
 8498                segment is full.>
 8499 
 8500 
 8501 
 8502      Stream:   $access_audit
 8503 
 8504      Time:     While system is running.
 8505 
 8506      Meaning:  A message  was not added  to a mailbox  or message
 8507                segment because  there is not enough  room for the
 8508                message  in the  segment.  Repeated  occurences of
 8509                this  event  over  a  short  period  of time could
 8510                indicate   an  attempt   to  exploit   a  moderate
 8511                bandwidth   covert   channel.    ADDED_INFO   will
 8512                identify the user and segment in question.
 8513 
 8514      Action:   Contact the system programming staff._ssa
 8515 
 8516 
 8517                [mseg_segment_.pl1]
 8518                Audit   (mseg_$reset_salvaged_flag_seg):   GRANTED
 8519                modifying  message  segment  attributes ADDED_INFO
 8520                <Message segment salvage flag reset.>
 8521 
 8522 
 8523 
 8524      Stream:   $access_audit
 8525 
 8526      Time:     While system is running.
 8527 
 8528      Meaning:  The  salvaged indicator  of a  message segment  or
 8529                mailbox was reset at the user's request.  Repeated
 8530                occurences  of this event  over a short  period of
 8531                time  could  indicate  an  attempt  to  exploit  a
 8532                moderate  bandwidth  covert  channel.   ADDED_INFO
 8533                will identify the user and segment in question.
 8534 
 8535      Action:   Contact the system programming staff._ssa
 8536 
 8537 
 8538 
 8539 
 8540 Audit (mseg_check_access_)     148            08/03/23     MR12.7^L
 8541 
 8542 
 8543 
 8544 
 8545                [mseg_check_access_.pl1]
 8546                Audit  (mseg_check_access_):   [GRANTED  | DENIED]
 8547                OPERATION_DESCRIPTION ADDED_INFO
 8548 
 8549 
 8550      Stream:   $access_audit
 8551 
 8552      Time:     While system is running.
 8553 
 8554      Meaning:  An  access control decision  has been made  by the
 8555                mseg_   primitives.    The   OPERATION_DESCRIPTION
 8556                specifies  the operation   requested by  the user.
 8557                GRANTED  or DENIED   indicates whether  access was
 8558                granted or not.  the ADDED_INFO describes the user
 8559                and   the  message    segment  or   mailbox.   The
 8560                associated  binary info  describes the  message in
 8561                the segment if a specific message was involved.
 8562 
 8563      Action:   Contact the system programming staff._ssa
 8564 
 8565 
 8566                [page_error.alm]
 8567                AUDIT  (page_fault):   GRANTED  excessive  segment
 8568                state  changes (Moderate_cc)  for PROCESS_GROUP_ID
 8569                (AUTHORIZATION)
 8570 
 8571 
 8572 
 8573      Time:     While system is running.
 8574 
 8575      Stream:   $security_log
 8576 
 8577      Meaning:  An  attempt  to  use  the  modification of various
 8578                segment  "  attributes  as  a  covert  channel was
 8579                detected.
 8580 
 8581 
 8582 
 8583                [pnt_db_util_.pl1]
 8584                AUDIT  (pnt_db_util_):   GRANTED  addition  of pnt
 8585                entry  (Admin_op)  for  PERSON.PROJECT.TAG  (AUTH)
 8586                Level=1 to PNT entry USERID (no access class).
 8587 
 8588 
 8589      Stream:   $access_audit
 8590 
 8591      Time:     While system is running.
 8592 
 8593      Meaning:  The  user,  PERSON.PROJECT.TAG,  added  a  new PNT
 8594                entry for USERID
 8595 
 8596 
 8597 
 8598 AUDIT (pnt_db_util_)           149            08/03/23     MR12.7^L
 8599 
 8600 
 8601      Action:   No operator action is required.
 8602 
 8603 
 8604                [pnt_db_util_.pl1]
 8605                AUDIT  (pnt_db_util_):   GRANTED  deletion  of pnt
 8606                entry  (Admin_op)  for  PERSON.PROJECT.TAG  (AUTH)
 8607                Level=1 to PNT entry USERID (no access class).
 8608 
 8609 
 8610      Stream:   $access_audit
 8611 
 8612      Time:     While system is running.
 8613 
 8614      Meaning:  The user PERSON.PROJECT.TAG  deleted the PNT entry
 8615                for USERID.
 8616 
 8617      Action:   No operator action is required.
 8618 
 8619 
 8620                [pnt_db_util_.pl1]
 8621                AUDIT (pnt_db_util_):  GRANTED modification of pnt
 8622                entry  (Admin_op)  for  PERSON.PROJECT.TAG  (AUTH)
 8623                Level=1 to  PNT entry USERID:  CHANGES  (no access
 8624                class).
 8625 
 8626 
 8627      Stream:   $access_audit
 8628 
 8629      Time:     While system is running.
 8630 
 8631      Meaning:  The user PERSON.PROJECT.TAG modified the PNT entry
 8632                for  USERID.  CHANGES   describes in  brief format
 8633                what security relevant changes were made.  See the
 8634                binary  information  in   the  audit  message  for
 8635                further details.
 8636 
 8637      Action:   No operator action is required.
 8638 
 8639 
 8640                [reclassify.pl1]
 8641                AUDIT (reclassify$ENTRY):  GRANTED modification of
 8642                security out-of-service ADDED_INFO
 8643 
 8644 
 8645      Stream:   $access_audit
 8646 
 8647      Time:     While system is running.
 8648 
 8649      Meaning:  An AIM error was found in respect to the specified
 8650                directory.   There was   a disagreement  in access
 8651                class between the directory  and one of it's sons,
 8652                or   there   was   an   upgraded   directory  with
 8653                non-terminal quota.
 8654 
 8655 
 8656 AUDIT (reclassify$ENTRY)       150            08/03/23     MR12.7^L
 8657 
 8658 
 8659      Action:   No operator action is required.
 8660 
 8661 
 8662                [reclassify.pl1]
 8663                AUDIT      (reclassify$ENTRY):      GRANTED|DENIED
 8664                modification of fs_obj access class ADDED_INFO
 8665 
 8666 
 8667      Stream:   $access_audit
 8668 
 8669      Time:     While system is running.
 8670 
 8671      Meaning:  Indicates  whether an   attempt to  reclassify the
 8672                specified  file  system   object  was  granted  or
 8673                denied.  In the case of reclassify$node, a message
 8674                will be generated for  each entry in the directory
 8675                being reclassified.
 8676 
 8677      Action:   No operator action is required.
 8678 
 8679 
 8680                [salv_check_vtoce_.pl1]
 8681                AUDIT  (salv_check_vtoce_):  GRANTED  modification
 8682                of security out-of-service ADDED_INFO
 8683 
 8684 
 8685      Stream:   $access_audit
 8686 
 8687      Time:     While system is running.
 8688 
 8689      Meaning:  Security  out-of-service  switch  was  set because
 8690                vtoce access class did  not match the entry access
 8691                class for the specified file system entry.
 8692 
 8693      Action:   Contact the system programming staff._ssa
 8694 
 8695 
 8696                [salv_dir_checker_.pl1]
 8697                AUDIT  (salv_dir_checker_):  GRANTED  modification
 8698                of fs_obj access ADDED_INFO
 8699 
 8700 
 8701      Stream:   $access_audit
 8702 
 8703      Time:     Salvaging
 8704 
 8705      Meaning:  The salvager has truncated the ACL of a branch.
 8706 
 8707      Action:   Contact the system programming staff._ssa
 8708 
 8709 
 8710                [set_privileges.pl1]
 8711 
 8712 
 8713 
 8714 AUDIT (set_privileges)         151            08/03/23     MR12.7^L
 8715 
 8716 
 8717                AUDIT  (set_privileges):  GRANTED  modification of
 8718                system AIM privilege ADDED_INFO
 8719 
 8720 
 8721      Stream:   $access_audit
 8722 
 8723      Time:     While system is running.
 8724 
 8725      Meaning:  The  specified  user  made  a  privileged call for
 8726                modifying the process AIM privileges
 8727 
 8728      Action:   No operator action is required.
 8729 
 8730 
 8731                [set_sys_audit_thresholds_.pl1]
 8732                AUDIT (set_sys_audit_thresholds_):  GRANTED|DENIED
 8733                modification of system  audit flags and thresholds
 8734                ADDED_INFO
 8735 
 8736 
 8737      Stream:   $access_audit
 8738 
 8739      Time:     While system is running.
 8740 
 8741      Meaning:  Indicates that the system  wide audit enable flags
 8742                and the thresholds have been changed as indicated.
 8743 
 8744      Action:   No operator action is required.
 8745 
 8746 
 8747                [bce_abs_seg.pl1]
 8748                bce_abs_seg:  Too many bce abs-segs.
 8749 
 8750 
 8751      Stream:   BOS Typewriter (Crashes system)
 8752 
 8753      Time:     System Intialization.
 8754 
 8755      Meaning:  More per-bce  pass abs-segs were  encountered than
 8756                fit  in the  abs-seg  array.   This is  a software
 8757                error.
 8758 
 8759 
 8760 
 8761                [bce_ioi_post.pl1]
 8762                bce_ioi_post:    Error  posting   i/o  completion.
 8763                ioi_event_channel:     CCCCCCCCCCCC   ioi_message:
 8764                MMMMMMMMMMMM
 8765 
 8766 
 8767 
 8768      Stream:   BOS Typewriter (Crashes system)
 8769 
 8770 
 8771 
 8772 bce_ioi_post                   152            08/03/23     MR12.7^L
 8773 
 8774 
 8775      Time:     System Intialization.
 8776 
 8777      Meaning:  No   posting   buffer   was   found   in  an  "I/O
 8778                outstanding"  state for  the above  event channel.
 8779                This indicates a logic error in the supervisor, or
 8780                CPU or memory hardware problems.
 8781 
 8782      Action:   Contact the system programming staff.
 8783 
 8784 
 8785                [bce_ioi_post.pl1]
 8786                bce_ioi_post:  System not at correct level to post
 8787                I/O completion.
 8788 
 8789 
 8790      Stream:   BOS Typewriter (Crashes system)
 8791 
 8792      Time:     System Intialization.
 8793 
 8794      Meaning:  The  flag  sys_info$service_system  indicates that
 8795                the  system  is  up  and  should  be  posting  I/O
 8796                completions via pxss$io_wakeup,  not this program.
 8797                This indicates a logic error in the supervisor, or
 8798                CPU or memory hardware problems.
 8799 
 8800      Action:   Contact the system programming staff.
 8801 
 8802 
 8803                [bce_ioi_post.pl1]
 8804                bce_ioi_post:      Unexpected    System     Fault.
 8805                ioi_event_channel:     CCCCCCCCCCCC   ioi_message:
 8806                MMMMMMMMMMMM
 8807 
 8808 
 8809 
 8810      Stream:   BOS Typewriter (Crashes system)
 8811 
 8812      Time:     System Intialization.
 8813 
 8814      Meaning:  This indicates a logic error in the supervisor, or
 8815                CPU or memory hardware problems.
 8816 
 8817      Action:   Contact the system programming staff.
 8818 
 8819 
 8820                [bce_save.pl1]
 8821                bce_save:  Error issuing tape connect for TAPE_DEV
 8822                (TAPE_SET).  ERR_MESSAGE
 8823 
 8824 
 8825      Stream:   BOS Typewriter (Crashes system)
 8826 
 8827      Time:     System Intialization.
 8828 
 8829 
 8830 bce_save                       153            08/03/23     MR12.7^L
 8831 
 8832 
 8833      Meaning:  IOI has returned a  non-zero error, which has been
 8834                expanded  in  ERR_MESSAGE.This  indicates  a logic
 8835                error in the supervisor, or CPU or memory hardware
 8836                problems.
 8837 
 8838      Action:   Contact the system programming staff.
 8839 
 8840 
 8841                [bce_save.pl1]
 8842                bce_save:  Internal bit map for PV_NAME (TAPE_SET)
 8843                contains no in use pages.
 8844 
 8845 
 8846      Stream:   BOS Typewriter (Crashes system)
 8847 
 8848      Time:     System Intialization.
 8849 
 8850      Meaning:  The  copied/packed internal   version of  the PV's
 8851                volume  bit  map  contains   no  used  pages  (OFF
 8852                bits).This   indicates  a   logic  error   in  the
 8853                supervisor, or CPU or memory hardware problems.
 8854 
 8855      Action:   Contact the system programming staff.
 8856 
 8857 
 8858                [bce_save.pl1]
 8859                bce_save:  IO complete, but NO status returned for
 8860                TAPE_SET.
 8861 
 8862 
 8863      Stream:   BOS Typewriter (Crashes system)
 8864 
 8865      Time:     System Intialization.
 8866 
 8867      Meaning:  An  I/O   has  been  posted,  but   there  was  no
 8868                indication of status being returned.This indicates
 8869                a logic error in the  supervisor, or CPU or memory
 8870                hardware problems.
 8871 
 8872      Action:   Contact the system programming staff.
 8873 
 8874 
 8875                [bce_save.pl1]
 8876                bce_save:  Out of disk buffers for TAPE_SET.
 8877 
 8878 
 8879      Stream:   BOS Typewriter (Crashes system)
 8880 
 8881      Time:     System Intialization.
 8882 
 8883      Meaning:  This indicates a logic error in the supervisor, or
 8884                CPU or memory hardware problems.
 8885 
 8886 
 8887 
 8888 bce_save                       154            08/03/23     MR12.7^L
 8889 
 8890 
 8891      Action:   Contact the system programming staff.
 8892 
 8893 
 8894                [bce_save.pl1]
 8895                bce_save:  Out of tape buffers for TAPE_SET.
 8896 
 8897 
 8898      Stream:   BOS Typewriter (Crashes system)
 8899 
 8900      Time:     System Intialization.
 8901 
 8902      Meaning:  This indicates a logic error in the supervisor, or
 8903                CPU or memory hardware problems.
 8904 
 8905      Action:   Contact the system programming staff.
 8906 
 8907 
 8908                [bce_save_util_.pl1]
 8909                bce_save_util_:  Out of disk buffers for TAPE_SET.
 8910 
 8911 
 8912      Stream:   BOS Typewriter (Crashes system)
 8913 
 8914      Time:     System Intialization.
 8915 
 8916      Meaning:  This indicates a logic error in the supervisor, or
 8917                CPU or memory hardware problems.
 8918 
 8919      Action:   Contact the system programming staff.
 8920 
 8921 
 8922                [wired_shutdown.pl1]
 8923                begin emergency shutdown part 1
 8924 
 8925 
 8926      Stream:   BOS Typewriter.
 8927 
 8928      Time:     Emergency shutdown
 8929 
 8930      Meaning:  The system emergency shutdown environment has been
 8931                successfully established.  An attempt will be made
 8932                to write  out all of  memory and flush  the paging
 8933                device.
 8934 
 8935      Action:   No operator action is required.
 8936 
 8937 
 8938                [boot_tape_io.pl1]
 8939                boot_tape_io:  Code CODE from absadr.
 8940 
 8941 
 8942      Stream:   BOS Typewriter (Crashes system)
 8943 
 8944 
 8945 
 8946 boot_tape_io                   155            08/03/23     MR12.7^L
 8947 
 8948 
 8949      Time:     System Intialization.
 8950 
 8951      Meaning:  boot_tape_io was unable to find the address of its
 8952                buffer.   This  indicates  a  logic  error  in the
 8953                supervisor, or CPU or memory hardware problems.
 8954 
 8955      Action:   $boot_tape
 8956 
 8957 
 8958                [boot_tape_io.pl1]
 8959                boot_tape_io:  Code CODE from io_manager$assign
 8960 
 8961 
 8962      Stream:   BOS Typewriter (Crashes system)
 8963 
 8964      Time:     System Intialization.
 8965 
 8966      Meaning:  The bootload tape reading package could not assign
 8967                the bootload tape drive to itself.  This indicates
 8968                a logic error in the  supervisor, or CPU or memory
 8969                hardware problems.
 8970 
 8971      Action:   $boot_tape
 8972 
 8973 
 8974                [boot_tape_io.pl1]
 8975                boot_tape_io:  Unable to allocate buffer.
 8976 
 8977 
 8978      Stream:   BOS Typewriter (Crashes system)
 8979 
 8980      Time:     System Intialization.
 8981 
 8982      Meaning:  The  bootload  tape   reading  package  could  not
 8983                allocate  a wired-down  buffer into  which to read
 8984                the bootload  tape.  This indicates a  logic error
 8985                in  the  supervisor,  or  CPU  or  memory hardware
 8986                problems.
 8987 
 8988      Action:   $boot_tape
 8989 
 8990 
 8991                [bootload_error.alm]
 8992                bootload_0:  An unpaged  page table overflowed for
 8993                seg N.
 8994 
 8995 
 8996      Stream:   BOS Typewriter (Crashes system)
 8997 
 8998      Time:     System Intialization.
 8999 
 9000 
 9001 
 9002 
 9003 
 9004 bootload_0                     156            08/03/23     MR12.7^L
 9005 
 9006 
 9007      Meaning:  The  size of the  page table needed  for "unpaged"
 9008                segment  N exceeded  the area  left for  such page
 9009                tables.
 9010 
 9011      Action:   The  system  tape  was  generated  improperly; use
 9012                another copy of the system tape.
 9013 
 9014 
 9015 
 9016                [bootload_error.alm]
 9017                bootload_0:  Bad MST format.
 9018 
 9019 
 9020      Stream:   BOS Typewriter (Crashes system)
 9021 
 9022      Time:     System Intialization.
 9023 
 9024      Meaning:  The records on the MST tape were out of sequence.
 9025 
 9026      Action:   Try another tape.
 9027 
 9028 
 9029                [bootload_error.alm]
 9030                bootload_0:  Booted tape MPC.
 9031 
 9032 
 9033      Stream:   BOS Typewriter.
 9034 
 9035      Time:     System Intialization.
 9036 
 9037      Meaning:  The system succeeded in  booting the bootload tape
 9038                mpc.
 9039 
 9040 
 9041                [bootload_error.alm]
 9042                bootload_0:   Booting FWNAME   IOM CHAN  with FWID
 9043                FWREV firmware.
 9044 
 9045 
 9046      Stream:   BOS Typewriter.
 9047 
 9048      Time:     System Intialization.
 9049 
 9050      Meaning:  The  system is  about  to  boot firmware  into the
 9051                bootload tape mpc.
 9052 
 9053 
 9054 
 9055                [bootload_error.alm]
 9056                bootload_0:    Booting   system   SYSID  generated
 9057                CREATION_TIME
 9058 
 9059 
 9060 
 9061 
 9062 bootload_0                     157            08/03/23     MR12.7^L
 9063 
 9064 
 9065      Stream:   BOS Typewriter.
 9066 
 9067      Time:     System Intialization.
 9068 
 9069      Meaning:  This  is  the  first  message  printed by Multics,
 9070                announcing the sysid and creation date/time of the
 9071                system tape.
 9072 
 9073 
 9074 
 9075                [bootload_error.alm]
 9076                bootload_0:  Console status WORD1 WORD2
 9077 
 9078 
 9079      Stream:   BOS Typewriter (Crashes system)
 9080 
 9081      Time:     System Intialization.
 9082 
 9083      Meaning:  An  I/O  error  was  encountered  on  the console.
 9084                WORD1 and  WORD2 are the  two words of  the status
 9085                returned.
 9086 
 9087      Action:   Run T&D on the console.
 9088 
 9089 
 9090                [bootload_error.alm]
 9091                bootload_0:  Enter boot tape MPC model:
 9092 
 9093 
 9094      Stream:   BOS Typewriter.
 9095 
 9096      Time:     System Intialization.
 9097 
 9098      Meaning:  This query  requests the operator to  identify the
 9099                bootload tape mpc so  that firmware may be loaded.
 9100                Refer to the MOH for details.
 9101 
 9102 
 9103 
 9104                [bootload_error.alm]
 9105                bootload_0:   Enter tape  drive number  for memory
 9106                dump:
 9107 
 9108 
 9109      Stream:   BOS Typewriter.
 9110 
 9111      Time:     BOS Typewriter (Crashes system)
 9112 
 9113      Meaning:  An initialization failure occured when the toehold
 9114                was  not  active.   The  system  is requesting the
 9115                number of a tape drive on the bootload tape mpc on
 9116                which to write a dump of memory.
 9117 
 9118 
 9119 
 9120 bootload_0                     158            08/03/23     MR12.7^L
 9121 
 9122 
 9123 
 9124 
 9125                [bootload_error.alm]
 9126                bootload_0:   Error  status  WORD1  WORD2  booting
 9127                FWTYPE firmware.
 9128 
 9129 
 9130      Stream:   BOS Typewriter.
 9131 
 9132      Time:     System Intialization.
 9133 
 9134      Meaning:  An error occured when  attempting to boot firmware
 9135                into the  bootload tape mpc.  WORD1  and WORD2 are
 9136                the status returned.
 9137 
 9138      Action:   Try another firmware identifier.
 9139 
 9140 
 9141                [bootload_error.alm]
 9142                bootload_0:  Excessive tape  errors:  status WORD1
 9143                WORD2.
 9144 
 9145 
 9146      Stream:   BOS Typewriter.
 9147 
 9148      Time:     BOS Typewriter (Crashes system)
 9149 
 9150      Meaning:  An excessive  number of write errors  occured when
 9151                trying to  write an early dump tape.   The dump to
 9152                this tape will be aborted.
 9153 
 9154      Action:   Try another tape.
 9155 
 9156 
 9157                [bootload_error.alm]
 9158                bootload_0:  External symbol not found:  SEG$ENTRY
 9159 
 9160 
 9161      Stream:   BOS Typewriter.
 9162 
 9163      Time:     System Intialization.
 9164 
 9165      Meaning:  The  entrypoint  ENTRY  was  not  found within the
 9166                existant   segment  SEG   during  pre-linking   of
 9167                collection 1.   This may indicate that  the system
 9168                tape was generated improperly.
 9169 
 9170 
 9171 
 9172                [bootload_error.alm]
 9173                bootload_0:  Improper text/link/def sequence.
 9174 
 9175 
 9176 
 9177 
 9178 bootload_0                     159            08/03/23     MR12.7^L
 9179 
 9180 
 9181      Stream:   BOS Typewriter (Crashes system)
 9182 
 9183      Time:     System Intialization.
 9184 
 9185      Meaning:  Text,  linkage,  or  definitions  appeared  out of
 9186                proper sequence " on the Multics system tape.
 9187 
 9188      Action:   The  system  tape  was  generated  improperly; use
 9189                another copy " of the system tape.
 9190 
 9191 
 9192 
 9193                [bootload_error.alm]
 9194                bootload_0:  Out of main memory.
 9195 
 9196 
 9197      Stream:   BOS Typewriter (Crashes system)
 9198 
 9199      Time:     System Intialization.
 9200 
 9201      Meaning:  Not enough  main memory is configured  in order to
 9202                load " collection 1.
 9203 
 9204      Action:   Configure more main memory and boot again.
 9205 
 9206 
 9207                [bootload_error.alm]
 9208                bootload_0:  Shutdown
 9209 
 9210 
 9211      Stream:   BOS Typewriter (Crashes system)
 9212 
 9213      Time:     System Intialization.
 9214 
 9215      Meaning:  The  operator answered  "shut" when  asked for the
 9216                bootload tape mpc information.
 9217 
 9218      Action:   $reboot
 9219 
 9220 
 9221                [bootload_error.alm]
 9222                bootload_0:  Tape read error:  WORD1 WORD2
 9223 
 9224 
 9225      Stream:   BOS Typewriter (Crashes system)
 9226 
 9227      Time:     System Intialization.
 9228 
 9229      Meaning:  An I/O error was  encountered when reading the MST
 9230                tape.  WORD1  and WORD2 are  the two words  of the
 9231                status returned.
 9232 
 9233      Action:   $reboot
 9234 
 9235 
 9236 bootload_0                     160            08/03/23     MR12.7^L
 9237 
 9238 
 9239 
 9240 
 9241                [bootload_error.alm]
 9242                bootload_0:  Too many supervisor segments.
 9243 
 9244 
 9245      Stream:   BOS Typewriter (Crashes system)
 9246 
 9247      Time:     System Intialization.
 9248 
 9249      Meaning:  More than 256 supervisor segments were declared on
 9250                the MST.
 9251 
 9252      Action:   The  system  tape  was  generated  improperly; use
 9253                another copy of the system tape.
 9254 
 9255 
 9256 
 9257                [bootload_error.alm]
 9258                bootload_0:   Unexpected  control   word  on  tape
 9259                CONTROL_WORD.
 9260 
 9261 
 9262      Stream:   BOS Typewriter (Crashes system)
 9263 
 9264      Time:     System Intialization.
 9265 
 9266      Meaning:  An unexpected Multics system tape control word was
 9267                encountered.
 9268 
 9269      Action:   The  system  tape  was  generated  improperly; use
 9270                another copy of the system tape.
 9271 
 9272 
 9273 
 9274                [bootload_error.alm]
 9275                bootload_0:  Unknown tape MPC model NAME.
 9276 
 9277 
 9278      Stream:   BOS Typewriter.
 9279 
 9280      Time:     System Intialization.
 9281 
 9282      Meaning:  The   operator  entered   an  unrecognizable   mpc
 9283                identifier.
 9284 
 9285      Action:   Try another mpc identifier.
 9286 
 9287 
 9288                [bootload_disk_post.pl1]
 9289                bootload_disk_post:  Attempt to post non-requested
 9290                i/o completion.
 9291 
 9292 
 9293 
 9294 bootload_disk_post             161            08/03/23     MR12.7^L
 9295 
 9296 
 9297      Stream:   BOS Typewriter (Crashes system)
 9298 
 9299      Time:     System Intialization.
 9300 
 9301      Meaning:  disk_control  detected  an   i/o  completion  that
 9302                Bootload Multics does not believe it requested.
 9303 
 9304      Action:   Reboot.
 9305 
 9306 
 9307                [boundfault.pl1]
 9308                boundfault:  activating into father XXX|YYY
 9309 
 9310 
 9311      Stream:   BOS Typewriter (Crashes system)
 9312 
 9313      Time:     While system is running.
 9314 
 9315      Meaning:  While activating  a segment, the  parent directory
 9316                for   the   segment   became   deactivated.   This
 9317                indicates a logic error  in the supervisor, or CPU
 9318                or memory hardware problems.
 9319 
 9320      Action:   Follow normal recovery procedures.
 9321 
 9322 
 9323                [boundfault.pl1]
 9324                boundfault:  on the root
 9325 
 9326 
 9327      Stream:   BOS Typewriter (Terminates user process)
 9328 
 9329      Time:     While system is running.
 9330 
 9331      Meaning:  A  boundfault  on  the  root  directory  has  been
 9332                encountered.  This indicates a  logic error in the
 9333                supervisor, or CPU or memory hardware problems.
 9334 
 9335      Action:   Contact the system programming staff.
 9336 
 9337 
 9338                [cache_tester.pl1]
 9339                cache_tester:  cache parity  error detected on CPU
 9340                <TAG>  bit  failures  at  level  W,  column XXX in
 9341                cache:    YYYYYYYYYYYYYYYYYYYYYYYY    in   memory:
 9342                ZZZZZZZZZZZZZZZZZZZZZZZZ.
 9343 
 9344 
 9345 
 9346      Stream:   BOS Typewriter.
 9347 
 9348      Time:     While system is running.
 9349 
 9350 
 9351 
 9352 cache_tester                   162            08/03/23     MR12.7^L
 9353 
 9354 
 9355      Meaning:  This message is the result of a multiple bit cache
 9356                failure   detected   and   cache   data   and  its
 9357                corresponding memory data captured by the fim.  It
 9358                should be noted that when  a cache parity error is
 9359                detected  by the  fim, there  is a  window of time
 9360                before the address in cache  and in main store can
 9361                be determined.   Although the cache error  data is
 9362                frozen  (cache is  turned off  unconditionaly when
 9363                the  parity  retry  of  the  fim  is  called), the
 9364                corresponding  address in   main store  might have
 9365                been changed  through paging migration  from other
 9366                processors.   This  message  then  might  not be a
 9367                multiple  error  but  rather  the  result  of this
 9368                window  condition.  If  this message  was the only
 9369                diagnostic displayed (i.e.   the static test found
 9370                no errors), the cache will be turned back on.  The
 9371                values  of W,  XXX,  YYY...Y,  and ZZZ...Z  are as
 9372                explained above.
 9373 
 9374      Action:   Contact Field Engineering
 9375 
 9376 
 9377                [cache_tester.pl1]
 9378                cache_tester:  cache parity  error detected on CPU
 9379                <TAG> at:  board XXXX, chip YY.
 9380 
 9381 
 9382 
 9383      Stream:   BOS Typewriter.
 9384 
 9385      Time:     While system is running.
 9386 
 9387      Meaning:  This message  is the result of a  single bit cache
 9388                failure   detected   and   cache   data   and  its
 9389                corresponding  memory data   captured by  the fim.
 9390                This message  will be displayed if  the diagnostic
 9391                error data  from the fim is valid.   The board and
 9392                chip callout are as explained above.
 9393 
 9394      Action:   Contact field Engineering.
 9395 
 9396 
 9397                [cache_tester.pl1]
 9398                cache_tester:  cache parity  error detected on CPU
 9399                <TAG>  cache data  is  equal  to the  memory data.
 9400                parity generation problem for level <L>.
 9401 
 9402 
 9403 
 9404      Stream:   BOS Typewriter.
 9405 
 9406      Time:     While system is running.
 9407 
 9408 
 9409 
 9410 cache_tester                   163            08/03/23     MR12.7^L
 9411 
 9412 
 9413      Meaning:  This  message is  the  result  of a  cache failure
 9414                detected  and  cache  data  and  its corresponding
 9415                memory  data captured  by the  fim.  This  message
 9416                will  be displayed  if the  diagnostic error  data
 9417                from the fim is valid.
 9418 
 9419      Action:   Contact field Engineering.
 9420 
 9421 
 9422                [cache_tester.pl1]
 9423                cache_tester:  Entire  cache memory for  CPU <TAG>
 9424                has been disabled.
 9425 
 9426 
 9427      Stream:   BOS Typewriter (sounds beeper)
 9428 
 9429      Time:     While system is running.
 9430 
 9431      Meaning:  The  static test  of  cache  memory for  CPU <TAG>
 9432                detected repeatable errors in both halfs of cache.
 9433                or one half of  cache had previously been disabled
 9434                and  the static  test of  the other  half detected
 9435                repeatable errors.
 9436 
 9437      Action:   Contact field Engineering
 9438 
 9439 
 9440                [cache_tester.pl1]
 9441                cache_tester:  LLUU cache  memory (csh<n>) for CPU
 9442                <TAG> has been turned off OTHER was AA and has not
 9443                been changed.
 9444 
 9445 
 9446 
 9447      Stream:   BOS Typewriter (sounds beeper)
 9448 
 9449      Time:     While system is running.
 9450 
 9451      Meaning:  Either the lower  half (LLUU = Lower, <n>  = 1) or
 9452                the upper  half (LLUU =  Upper, <n> =  2) of cache
 9453                memory for  CPU <TAG> has  been turned off  as the
 9454                result  of   the  static  cache  test   finding  a
 9455                repeatable  cache failure.    The OTHER  (Upper or
 9456                Lower) was in state AA.  If AA is off this half of
 9457                cache was  not tested.  If  AA is on  this half of
 9458                cache had no errors.
 9459 
 9460      Action:   Contact Field Engineering
 9461 
 9462 
 9463                [cache_tester.pl1]
 9464                cache_tester:  No errors found in cache memory for
 9465                CPU <TAG>, cache will remain on.
 9466 
 9467 
 9468 cache_tester                   164            08/03/23     MR12.7^L
 9469 
 9470 
 9471      Stream:   BOS Typewriter.
 9472 
 9473      Time:     While system is running.
 9474 
 9475      Meaning:  The  static test  of  cache  memory for  CPU <TAG>
 9476                found no errors and no cache error information was
 9477                captured by the fim.
 9478 
 9479      Action:   cache is turned back on
 9480 
 9481 
 9482                [cache_tester.pl1]
 9483                cache_tester:    repeatable  cache   parity  error
 9484                detected on  CPU <TAG> cache data is  equal to the
 9485                memory data.  parity  generation problem for level
 9486                <L>.
 9487 
 9488 
 9489 
 9490      Stream:   BOS Typewriter.
 9491 
 9492      Time:     While system is running.
 9493 
 9494      Meaning:  The  static test  of  cache  memory for  CPU <TAG>
 9495                detected  a cache  failure, but  the data  and its
 9496                corresponding memory data are equal.
 9497 
 9498      Action:   Contact field Engineering.
 9499 
 9500 
 9501                [cache_tester.pl1]
 9502                cache_tester:   repeatable  cache  parity error(s)
 9503                detected  on CPU  <TAG> bit  failures at  level W,
 9504                column XXX in  cache:  YYYYYYYYYYYYYYYYYYYYYYYY in
 9505                memory:  ZZZZZZZZZZZZZZZZZZZZZZZZ.
 9506 
 9507 
 9508 
 9509      Stream:   BOS Typewriter.
 9510 
 9511      Time:     While system is running.
 9512 
 9513      Meaning:  The  static test  of  cache  memory for  CPU <TAG>
 9514                indicated  a   multiple  bit  error   between  the
 9515                contents  of cache and  the contents of  the wired
 9516                test buffer.  The multiple  bit failure is further
 9517                broken down to the failing cache level (W) (0 - 3)
 9518                and  column  (XXX)  address.   The  data read from
 9519                cache (YYY...Y) and the expected data (ZZZ...Z) is
 9520                displayed as an aid for the field engineer.  Since
 9521                the  failure happened  during the  static test  of
 9522                cache,  it is  assumed to  be a  solid failure and
 9523                that  segment of  cache memory  (csh1 or  csh2) is
 9524 
 9525 
 9526 cache_tester                   165            08/03/23     MR12.7^L
 9527 
 9528 
 9529                turned  off.   There  could  be  up  to 3 multiple
 9530                messages or some combination of multiple bit error
 9531                messages  and  board   and  chip  callouts,  since
 9532                diagnostic  data for the  first 3 cache  errors is
 9533                captured.
 9534 
 9535      Action:   Contact Field Engineering personnel.
 9536 
 9537 
 9538                [cache_tester.pl1]
 9539                cache_tester:   repeatable  cache  parity error(s)
 9540                detected on CPU <TAG> at:  board XXXX, chip YY.
 9541 
 9542 
 9543 
 9544      Stream:   BOS Typewriter.
 9545 
 9546      Time:     While system is running.
 9547 
 9548      Meaning:  The  static test  of  cache  memory for  CPU <TAG>
 9549                indicated a single bit  error between the contents
 9550                of  cache  and  the  contents  of  the  wired test
 9551                buffer.  The single bit  failure is further broken
 9552                down  to  the  failing  wire  wrapped board (board
 9553                XXXX) and  integrated circuit chip (chip  YY) that
 9554                failed.  Since it happened  during the static test
 9555                of cache, it is assumed  to be a solid failure and
 9556                that  segment of  cache memory  (csh1 or  csh2) is
 9557                turned off.  There could be up to 3 board and chip
 9558                callouts  since diagnostic  data for  the first  3
 9559                cache errors is  captured.  These additional board
 9560                and  chip callouts will  only be displayed  if the
 9561                single  bit   failure  was  a  different   bit  or
 9562                different  cache  level  than  the  board and chip
 9563                diagnostic already displayed.
 9564 
 9565      Action:   Contact Field Engineering personnel.
 9566 
 9567 
 9568                [cache_tester.pl1]
 9569                cache_tester:  Unable to allocate wired buffer.
 9570 
 9571 
 9572      Stream:   BOS Typewriter.
 9573 
 9574      Time:     While system is running.
 9575 
 9576      Meaning:  Attempted to allocate  wired contiguous buffer for
 9577                cache testing and pc_contig  could not find enough
 9578                pages available.
 9579 
 9580 
 9581 
 9582 
 9583 
 9584 cache_tester                   166            08/03/23     MR12.7^L
 9585 
 9586 
 9587      Action:   If cache error information was captured in the fim
 9588                this  information is  displayed.  Cache  memory is
 9589                turned back on.
 9590 
 9591 
 9592 
 9593                [cache_tester.pl1]
 9594                cache_tester:  Unable to run  on CPU <TAG> to EEDD
 9595                cache ERRORMESSAGE.
 9596 
 9597 
 9598      Stream:   BOS Typewriter (sounds beeper)
 9599 
 9600      Time:     While system is running.
 9601 
 9602      Meaning:  The attempt  to run on CPU <TAG>  to either enable
 9603                (EEDD - enable) or  disable (EEDD = disable) cache
 9604                memory failed.
 9605 
 9606      Action:   CPU <TAG>  should be taken offline  if the attempt
 9607                was to disable cache memory.
 9608 
 9609 
 9610 
 9611                [cache_tester.pl1]
 9612                cache_tester:  Unable to set CPU required to <TAG>
 9613                cache is off ERRORMESSAGE.
 9614 
 9615 
 9616      Stream:   BOS Typewriter.
 9617 
 9618      Time:     While system is running.
 9619 
 9620      Meaning:  Attempted  to run on  CPU <TAG> for  cache testing
 9621                and could not set CPU required to that CPU.
 9622 
 9623      Action:   Cache memory is turned back on.
 9624 
 9625 
 9626                [call_bce.pl1]
 9627                call_bce:  bce called from Multics.
 9628 
 9629 
 9630      Stream:   BOS Typewriter.
 9631 
 9632      Time:     While system is running.
 9633 
 9634      Meaning:  An outer ring  program has called hphcs_$call_bce.
 9635                This is usually done after printing an explanatory
 9636                message.   The  system  will  resume  operation if
 9637                continue is typed.
 9638 
 9639      Action:   Follow normal recovery procedures.
 9640 
 9641 
 9642 Cannot                         167            08/03/23     MR12.7^L
 9643 
 9644 
 9645 
 9646 
 9647                [disk_rebuild_caller.pl1]
 9648                Cannot   shrink  VTOC   from  XX   to  YY  VTOCEs.
 9649                Respecify parameters.
 9650 
 9651 
 9652      Stream:   Initializer process output.
 9653 
 9654      Time:     In response to an operator command.
 9655 
 9656      Meaning:  An attempt has been made to shrink the VTOC, which
 9657                is illegal.
 9658 
 9659      Action:   Respecify the parameters.
 9660 
 9661 
 9662                [mc_tty_.pl1]
 9663                Channel    CHANNEL_NAME   attached    by   Message
 9664                Coordinator.
 9665 
 9666 
 9667      Stream:   Initializer terminal.
 9668 
 9669      Time:     While system is running.
 9670 
 9671      Meaning:  The  terminal  has  been  attached  by the message
 9672                coordinator  in response  to an  accept or substty
 9673                command.
 9674 
 9675      Action:   Proceed to use the terminal.
 9676 
 9677 
 9678                [channel_manager.pl1]
 9679                channel_manager:     Cleanup   while    processing
 9680                interrupt for devx N.
 9681 
 9682 
 9683      Stream:   BOS Typewriter (Crashes system)
 9684 
 9685      Time:     While system is running.
 9686 
 9687      Meaning:  The   cleanup   condition   was   signalled  while
 9688                processing an interrupt for  the channel with devx
 9689                N.
 9690 
 9691      Action:   Contact the system programming staff.
 9692 
 9693 
 9694                [channel_manager.pl1]
 9695                channel_manager:  Error while processing interrupt
 9696                for devx N.  REASON
 9697 
 9698 
 9699 
 9700 channel_manager                168            08/03/23     MR12.7^L
 9701 
 9702 
 9703      Stream:   BOS Typewriter (Crashes system)
 9704 
 9705      Time:     While system is running.
 9706 
 9707      Meaning:  An  error occurred  while processing  an interrupt
 9708                for the channel with devx N.  The specific kind of
 9709                error is explained by REASON.
 9710 
 9711 
 9712 
 9713                [dn355_boot_interrupt.pl1]
 9714                checksum error in core image for FNP X
 9715 
 9716 
 9717      Stream:   BOS Typewriter.
 9718 
 9719      Time:     When bootloading an FNP
 9720 
 9721      Meaning:  The core image received for loading in the FNP had
 9722                a checksum error.
 9723 
 9724      Action:   Try to  load the FNP again.  If  the error recurs,
 9725                either  the DIA hardware  is failing, or  the core
 9726                image in the Multics hierarchy is damaged.  In the
 9727                latter case, the core image must be rebound.
 9728 
 9729 
 9730 
 9731                [system_startup_.pl1]
 9732                Command:
 9733 
 9734 
 9735      Stream:   BOS Typewriter.
 9736 
 9737      Time:     System Intialization.
 9738 
 9739      Meaning:  The Initializer types this  message whenever it is
 9740                waiting for a ring 1 command.
 9741 
 9742      Action:   Type the  desired command.  The normal  command to
 9743                type when bringing the system up is startup.
 9744 
 9745 
 9746 
 9747                [config_.pl1]
 9748                config_$find_table:  TBLS card  specifies no value
 9749                for NAME.
 9750 
 9751 
 9752      Stream:   BOS Typewriter (sounds beeper)
 9753 
 9754      Meaning:  The config deck does not specify a value for NAME.
 9755 
 9756 
 9757 
 9758 config_$find_table             169            08/03/23     MR12.7^L
 9759 
 9760 
 9761      Action:   One  should  be  added.   Message:  config_$ENTRY:
 9762                the config deck is full.
 9763 
 9764      Stream:   BOS Typewriter (Crashes system)
 9765 
 9766      Meaning:  No   space  remained   in  the   config  deck  for
 9767                additional cards.
 9768 
 9769      Action:   If  this recurs,  try another  boot tape.   Remove
 9770                unneccessary config cards.
 9771 
 9772 
 9773 
 9774                [dn355_boot_interrupt.pl1]
 9775                configuration   error   reported   by  bootloading
 9776                program for FNP X
 9777 
 9778 
 9779      Stream:   BOS Typewriter.
 9780 
 9781      Time:     When bootloading an FNP
 9782 
 9783      Meaning:  The   FNP  bootload    program,  gicb,   found  an
 9784                inconsistency in the FNP configuration.
 9785 
 9786      Action:   Contact the system programming staff.
 9787 
 9788 
 9789                [dn355_boot_interrupt.pl1]
 9790                configuration error reported by FNP X:  DETAILS
 9791 
 9792 
 9793      Stream:   BOS Typewriter.
 9794 
 9795      Time:     When bootloading an FNP
 9796 
 9797      Meaning:  The FNP  initialization program detected  an error
 9798                or   inconsistency  in   the  FNP   configuration.
 9799                DETAILS  is  a  more  specific  description of the
 9800                error.
 9801 
 9802      Action:   If possible, correct the error, either by updating
 9803                the  CDT to  reflect the  actual configuration, or
 9804                recabling  the  FNP.   If   the  error  cannot  be
 9805                corrected or is not understood, inform the systems
 9806                programming staff.
 9807 
 9808 
 9809 
 9810                [configure_test_cpu.pl1]
 9811                configure_test_cpu:   Unable  to   run  on  CPU  X
 9812                ERRORMESSAGE
 9813 
 9814 
 9815 
 9816 configure_test_cpu             170            08/03/23     MR12.7^L
 9817 
 9818 
 9819      Stream:   BOS Typewriter (Crashes system)
 9820 
 9821      Time:     When ISOLTS is terminating
 9822 
 9823      Meaning:  The system is attempting to restore the ISOLTS CPU
 9824                to  service.    In  attempting  to   reassign  its
 9825                interrupt mask, it was unable  to run on that CPU.
 9826                This indicates hardware or software malfunction.
 9827 
 9828      Action:   Follow normal recovery procedures.
 9829 
 9830 
 9831                [disk_table_.pl1]
 9832                continuing demount of lv LVNAME
 9833 
 9834 
 9835      Stream:   Initializer process output.
 9836 
 9837      Time:     While  system is  running.  The  operator issued a
 9838                dlv  command  for  a  logical  volume  for which a
 9839                previous dlv command failed.
 9840 
 9841      Action:   No operator action is required.
 9842 
 9843 
 9844                [copy_fdump.pl1]
 9845                copy_fdump:   Copied   fdump  image  of   erf  NNN
 9846                (MM/DD/YY HHMM.M) for USERNAME
 9847 
 9848 
 9849      Stream:   BOS Typewriter.
 9850 
 9851      Time:     While system is running.
 9852 
 9853      Meaning:  The user  identified by USERNAME  has successfully
 9854                copied the  FDUMP image for the  specified ERF out
 9855                of  the DUMP  partition.  The  time the  FDUMP was
 9856                taken  is  also  included  in  the  message.  This
 9857                message  is informational   only, and  is intended
 9858                only  as an  aid  in  tracking system  progress by
 9859                perusing the syserr log.
 9860 
 9861      Action:   No operator action is required.
 9862 
 9863 
 9864                [copy_fdump.pl1]
 9865                copy_fdump:  unexpected NAME signal.
 9866 
 9867 
 9868      Stream:   BOS Typewriter.
 9869 
 9870      Time:     While system is running.
 9871 
 9872 
 9873 
 9874 copy_fdump                     171            08/03/23     MR12.7^L
 9875 
 9876 
 9877      Meaning:  An  attempt  to  copy   the  dump  from  the  DUMP
 9878                partition with copy_fdump resulted in an unclaimed
 9879                signal.   This may  be due  to damage  to the DUMP
 9880                partition contents, a malfunction  of the BCE dump
 9881                command,   a  supervisor    error,  or   a  simple
 9882                difficulty  like running  out of  space in >dumps.
 9883                The system  continues operation.  The  copied dump
 9884                may be only partly valid.
 9885 
 9886      Action:   Contact the system programming staff.
 9887 
 9888 
 9889                [correct_qused.pl1]
 9890                correct_qused:  hash error
 9891 
 9892 
 9893      Stream:   BOS Typewriter (Crashes system)
 9894 
 9895      Time:     While system is running.
 9896 
 9897      Meaning:  Multiple  entries  within  a  directory undergoing
 9898                quota correction have the same UID.
 9899 
 9900 
 9901 
 9902                [cpg_.pl1]
 9903                cpg_:   Error:   CONDITION  attempting  to  create
 9904                process for NAME.PROJ
 9905 
 9906 
 9907      Stream:   as (severity1)
 9908 
 9909      Time:     While system is running.
 9910 
 9911      Meaning:  A supervisor error prevented creation of a process
 9912                for the user NAME.PROJ.  An Answering Service dump
 9913                was  performed  and  the  user  was  logged out if
 9914                possible.
 9915 
 9916      Action:   Note  for  system   programmer  action.   If  this
 9917                message is printed at  every login, it is probably
 9918                wise  to  shut  the  system  down  and  perform  a
 9919                bootload operation.
 9920 
 9921 
 9922 
 9923                [cpg_.pl1]
 9924                cpg_:   ERROR_MESSAGE.  Assigning pdir  volume for
 9925                USER
 9926 
 9927 
 9928      Stream:   as (severity2)
 9929 
 9930 
 9931 
 9932 cpg_                           172            08/03/23     MR12.7^L
 9933 
 9934 
 9935      Time:     While system is running.
 9936 
 9937      Meaning:  The system  was unable to assign  a logical volume
 9938                on which to place the process directory of a user.
 9939                The user might not be able to log in
 9940 
 9941      Action:   Contact the system programming staff.
 9942 
 9943 
 9944                [cpg_.pl1]
 9945                cpg_:  ERROR_MESSAGE.  Cannot truncate pit_temp_
 9946 
 9947 
 9948      Stream:   as (severity2)
 9949 
 9950      Time:     While system is running.
 9951 
 9952      Meaning:  The  system  was  unable  to  clear  its temporary
 9953                segment  while attempting to  log in a  user.  The
 9954                user will be unable to log in.
 9955 
 9956      Action:   Contact the system programming staff.
 9957 
 9958 
 9959                [tc_init.pl1]
 9960                CPU CPUTAG:   Model #:  MODEL; Serial  #:  SERIAL;
 9961                Ship date:  YYMMDD.
 9962 
 9963 
 9964      Stream:   BOS Typewriter.
 9965 
 9966      Time:     When  the bootload  CPU is  a DPS8,  whose tag  is
 9967                CPUTAG is "added" to the system.
 9968 
 9969      Meaning:  The MODEL, SERIAL and YY/MM/DD information is read
 9970                from the DPS8 cpu's ID PROM.  It is intended to be
 9971                used  as  historical  information  for  identifing
 9972                CPUs,  regardless  of  what  their  current tag is
 9973                assigned as.
 9974 
 9975      Action:   No operator action is required.
 9976 
 9977 
 9978                [tc_init.pl1]
 9979                CPU CPUTAG:   Model #:  MODEL; Serial  #:  SERIAL;
 9980                Ship date:  YYMMDD;  PROM Layout Version:  LAYOUT;
 9981                Simulator Release:  VERSION; Build Number:  BUILD;
 9982                Build Arch:   BARCH; Build OS:  BOS;  Target Arch:
 9983                TARCH; Target OS:  TOS.
 9984 
 9985 
 9986 
 9987      Stream:   BOS Typewriter.
 9988 
 9989 
 9990 CPU CPUTAG                     173            08/03/23     MR12.7^L
 9991 
 9992 
 9993      Time:     When  the bootload  CPU is  a DPS8,  whose tag  is
 9994                CPUTAG is "added" to the system.
 9995 
 9996      Meaning:  The MODEL, SERIAL, YYMMDD, LAYOUT, VERSION, BUILD,
 9997                BARCH,  BOS, TARCH,  and TOS  information is  read
 9998                from the DPS8 cpu's ID PROM.  It is intended to be
 9999                used  as  historical  information  for  identifing
10000                CPUs,  regardless  of  what  their  current tag is
10001                assigned as.   The LAYOUT, VERSION,  BUILD, BARCH,
10002                BOS, TARCH, and TOS fields  are only found in DPS8
10003                PROMs of the DPS8M simulator.
10004 
10005      Action:   No operator action is required.
10006 
10007 
10008                [obs_reconfigure.pl1]
10009                CPU X is now running.
10010 
10011 
10012      Stream:   Initializer process output.
10013 
10014      Time:     In response to an operator command.
10015 
10016      Meaning:  This  is the  response  to  a successful  addcpu X
10017                command.
10018 
10019      Action:   No operator action is required.
10020 
10021 
10022                [create_homedir_.pl1]
10023                create_homedir_:  Bad syntax in pathname.  DIRNAME
10024                NAME.PROJ
10025 
10026 
10027      Stream:   as (severity0).
10028 
10029      Time:     While system is running.
10030 
10031      Meaning:  Typically   caused  by  a   homedir  specification
10032                starting  with other  than >user_dir_dir  or >udd.
10033                It may  also occur while attempting  to create the
10034                home  directory for  the user  with name  NAME and
10035                project PROJ.
10036 
10037      Action:   Note for system programmer action._sa
10038 
10039 
10040                [bound_as_install_ctl_.s.archiv.1]
10041                create_homedir_:  Bad syntax in pathname.  DIRNAME
10042                NAME.PROJ
10043 
10044 
10045      Stream:   as (severity0).
10046 
10047 
10048 create_homedir_                174            08/03/23     MR12.7^L
10049 
10050 
10051      Time:     While system is running.
10052 
10053      Meaning:  Typically   caused  by  a   homedir  specification
10054                starting  with other  than >user_dir_dir  or >udd.
10055                It may  also occur while attempting  to create the
10056                home  directory for  the user  with name  NAME and
10057                project PROJ.
10058 
10059      Action:   Note for system programmer action._sa
10060 
10061 
10062                [create_homedir_.pl1]
10063                create_homedir_:  creating "DIRNAME" for "USERID"
10064 
10065 
10066      Stream:   as (severity0).
10067 
10068      Time:     While system is running.
10069 
10070      Meaning:  The user USERID did not have a home directory.  It
10071                was  created for  him  during  login, or  when his
10072                project's PDT  was installed.  This  is reasonable
10073                if  this  is  the  first  time  he  has logged in.
10074                However, his directory may  have been destroyed by
10075                the Salvager,  in which case you  have to retrieve
10076                his files.
10077 
10078      Action:   A  retrieval  of  the   user's  directory  may  be
10079                necessary.
10080 
10081 
10082                [bound_as_install_ctl_.s.archiv.1]
10083                create_homedir_:  creating "DIRNAME" for "USERID"
10084 
10085 
10086      Stream:   as (severity0).
10087 
10088      Time:     While system is running.
10089 
10090      Meaning:  The user USERID did not have a home directory.  It
10091                was  created for  him  during  login, or  when his
10092                project's PDT  was installed.  This  is reasonable
10093                if  this  is  the  first  time  he  has logged in.
10094                However, his directory may  have been destroyed by
10095                the Salvager,  in which case you  have to retrieve
10096                his files.
10097 
10098      Action:   A  retrieval  of  the   user's  directory  may  be
10099                necessary.
10100 
10101 
10102                [create_homedir_.pl1]
10103 
10104 
10105 
10106 create_homedir_                175            08/03/23     MR12.7^L
10107 
10108 
10109                create_homedir_:       ERROR_MESSAGE.      DIRNAME
10110                NAME.PROJ
10111 
10112 
10113      Stream:   as (severity0).
10114 
10115      Time:     While system is running.
10116 
10117      Meaning:  An error  occurred while attempting to  create the
10118                home  directory for  the user  with name  NAME and
10119                project PROJ.
10120 
10121      Action:   Note for system programmer action._sa
10122 
10123 
10124                [bound_as_install_ctl_.s.archiv.1]
10125                create_homedir_:       ERROR_MESSAGE.      DIRNAME
10126                NAME.PROJ
10127 
10128 
10129      Stream:   as (severity0).
10130 
10131      Time:     While system is running.
10132 
10133      Meaning:  An error  occurred while attempting to  create the
10134                home  directory for  the user  with name  NAME and
10135                project PROJ.
10136 
10137      Action:   Note for system programmer action._sa
10138 
10139 
10140                [create_root_dir.pl1]
10141                create_root_dir:      allocating    hash     table
10142                ERROR_MESSAGE
10143 
10144 
10145      Stream:   BOS Typewriter (Crashes system)
10146 
10147      Time:     Cold boot of Multics hierarchy.
10148 
10149      Meaning:  This indicates a logic error in the supervisor, or
10150                CPU  or memory  hardware problems.   An error  has
10151                occurred  allocating the  hash table  for the root
10152                directory.
10153 
10154      Action:   Reboot with a different version of the system.
10155 
10156 
10157                [create_root_dir.pl1]
10158                create_root_dir:  lock error on PPP
10159 
10160 
10161      Stream:   BOS Typewriter (Crashes system)
10162 
10163 
10164 create_root_dir                176            08/03/23     MR12.7^L
10165 
10166 
10167      Time:     System Intialization.
10168 
10169      Meaning:  The supervisor was unable  to lock the root.  This
10170                indicates a logic error  in the supervisor, or CPU
10171                or memory hardware problems.
10172 
10173      Action:   Follow normal recovery procedures.  $boot_tape
10174 
10175 
10176 
10177                [create_root_vtoce.pl1]
10178                create_root_vtoce:  Cannot  alloc-write root vtoce
10179                ERROR_MESSAGE
10180 
10181 
10182      Stream:   BOS Typewriter (Crashes system)
10183 
10184      Time:     Cold boot of Multics hierarchy.
10185 
10186      Meaning:  The system  is unable to write out  the VTOC entry
10187                for the root directory.
10188 
10189      Action:   Correct the disk problem if one exists and reboot.
10190                Otherwise reboot  with a different version  of the
10191                system.
10192 
10193 
10194 
10195                [create_root_vtoce.pl1]
10196                create_root_vtoce:   Cannot set  dmpr bit  map for
10197                root ERROR_MESSAGE
10198 
10199 
10200      Stream:   BOS Typewriter.
10201 
10202      Time:     Cold boot of Multics hierarchy.
10203 
10204      Meaning:  This indicates a logic error in the supervisor, or
10205                CPU or memory hardware problems.
10206 
10207      Action:   Contact the system programming staff.
10208 
10209                Message:     create_root_vtoce:      Cannot    set
10210                root_vtocx in RPV label.
10211 
10212      Stream:   BOS Typewriter (Crashes system)
10213 
10214      Time:     Cold boot of Multics hierarchy.
10215 
10216      Meaning:  The system  is unable to update the  RPV label for
10217                the root directory.
10218 
10219 
10220 
10221 
10222 create_root_vtoce              177            08/03/23     MR12.7^L
10223 
10224 
10225      Action:   Correct the disk problem if one exists and reboot.
10226                Otherwise reboot  with a different version  of the
10227                system.
10228 
10229                Message:    create_root_vtoce:   Root   vtoce  not
10230                allocated at 0, RPV not initialized.
10231 
10232      Stream:   BOS Typewriter (Crashes system)
10233 
10234      Time:     Cold boot of Multics hierarchy.
10235 
10236      Meaning:  A  boot -cold  was attempted  without init_vol for
10237                RPV.
10238 
10239      Action:   Reboot  system  answering  the  find_rpv_subsystem
10240                with cold instead of rpv.
10241 
10242 
10243                [create_rpv_partition.pl1]
10244                create_rpv_partition:  Error accessing record NNN.
10245 
10246 
10247      Stream:   BOS Typewriter (Crashes system)
10248 
10249      Time:     System Intialization.
10250 
10251      Meaning:  An i/o error occured  when accessing record NNN of
10252                the rpv while attempting to add a new partition.
10253 
10254      Action:   Try  again.  IF the  error persists, the  rpv will
10255                need to be rebuilt.
10256 
10257 
10258                [create_rpv_partition.pl1]
10259                create_rpv_partition:   No room  in partition  map
10260                for NAME.
10261 
10262 
10263      Stream:   BOS Typewriter (Crashes system)
10264 
10265      Time:     System Intialization.
10266 
10267      Meaning:  The  partition  map  of  the  rpv  was  full.  The
10268                partition could not be added.
10269 
10270      Action:   The rpv will need to be rebuilt.
10271 
10272 
10273                [create_rpv_partition.pl1]
10274                create_rpv_partition:  Out of disk.
10275 
10276 
10277      Stream:   BOS Typewriter (Crashes system)
10278 
10279 
10280 create_rpv_partition           178            08/03/23     MR12.7^L
10281 
10282 
10283      Time:     System Intialization.
10284 
10285      Meaning:  Not enough  free space existed  on the rpv  to add
10286                the new partition.
10287 
10288      Action:   The rlv will have to be rebuilt.
10289 
10290 
10291                [create_rpv_partition.pl1]
10292                create_rpv_partition:   Paging  region  ends  past
10293                start of high partitions.
10294 
10295 
10296      Stream:   BOS Typewriter (Crashes system)
10297 
10298      Time:     System Intialization.
10299 
10300      Meaning:  An  inconsistency was  found in  the partition map
10301                when adding a new partition to the rpv.
10302 
10303      Action:   The rpv will need to be rebuilt.
10304 
10305 
10306                [create_rpv_partition.pl1]
10307                create_rpv_partition:  Paging  region starts below
10308                end of low partitions.
10309 
10310 
10311      Stream:   BOS Typewriter (Crashes system)
10312 
10313      Time:     System Intialization.
10314 
10315      Meaning:  An  inconsistency was  found in  the partition map
10316                when adding a new partition to the rpv.
10317 
10318      Action:   The rpv will need to be rebuilt.
10319 
10320 
10321                [create_rpv_partition.pl1]
10322                create_rpv_partition:   vtoce  NNN's  file  map is
10323                damaged.  Volume will need salvaging.
10324 
10325 
10326      Stream:   BOS Typewriter (Crashes system)
10327 
10328      Time:     System Intialization.
10329 
10330      Meaning:  The  vtoce  named  was  found  to  be damaged when
10331                adding a new partition to the rpv.
10332 
10333      Action:   Salvage  the  rpv  using  a  boot  of the previous
10334                release.
10335 
10336 
10337 
10338 daemon_user_manager_           179            08/03/23     MR12.7^L
10339 
10340 
10341 
10342 
10343                [daemon_user_manager_.pl1]
10344                daemon_user_manager_:      Command     sent     to
10345                daemon_user_manager_ before it was initialized
10346 
10347 
10348      Stream:   as (severity1)
10349 
10350      Time:     In response to an operator command.
10351 
10352      Meaning:  This message  indicates an error in  the Answering
10353                Service or  an incorrect installation.   No daemon
10354                users can log in.
10355 
10356      Action:   Contact the system programming staff.
10357 
10358 
10359                [daemon_user_manager_.pl1]
10360                daemon_user_manager_:   Daemon  init  error.  NAME
10361                PROJ SOURCE REASON
10362 
10363 
10364      Stream:   as (severity2)
10365 
10366      Time:     In response to an operator command.
10367 
10368      Meaning:  The daemon user NAME PROJ  on SOURCE was logged in
10369                correctly  but his  process could  not be started.
10370                The daemon will be logged out.
10371 
10372      Action:   Contact the system programming staff.
10373 
10374 
10375                [daemon_user_manager_.pl1]
10376                daemon_user_manager_:  Daemon will be logged out.
10377 
10378 
10379      Stream:   as (severity1)
10380 
10381      Time:     While system is running.
10382 
10383      Meaning:  An  error in  a daemon  process has  caused it  to
10384                terminate.   The daemon  suffered a  fatal process
10385                error  during  initialization  or  it  has set the
10386                option  which causes  it to  be logged  out when a
10387                fatal process error occurs.
10388 
10389      Action:   Attempt to log in the daemon again and proceed.
10390 
10391 
10392                [daemon_user_manager_.pl1]
10393 
10394 
10395 
10396 daemon_user_manager_           180            08/03/23     MR12.7^L
10397 
10398 
10399                daemon_user_manager_:  Error:  CONDITION during OP
10400                for NAME.PROJ SOURCE
10401 
10402 
10403      Stream:   as (severity2)
10404 
10405      Time:     While system is running.
10406 
10407      Meaning:  An unexpected fault has  occurred while the daemon
10408                user manager  was performing an operation  of type
10409                OP  for the  named daemon  process.  An  Answering
10410                Service dump was performed and the system attempts
10411                to continue,  but the daemon process may  be in an
10412                unusable state.
10413 
10414      Action:   Contact the system programming staff.
10415 
10416 
10417                [daemon_user_manager_.pl1]
10418                daemon_user_manager_:  ERROR_MESSAGE.   Logout not
10419                permitted for message coordinator source SOURCE.
10420 
10421 
10422      Stream:   as (severity1)
10423 
10424      Time:     In response to an operator command.
10425 
10426      Meaning:  The  message  coordinator  access  control segment
10427                >system_control_1>mc_acs>SOURCE.mcacs   does   not
10428                permit   the  operator   to  logout   the  daemon.
10429                Therefore, the operator cannot logout the daemon.
10430 
10431      Action:   Contact the system programming staff._sa
10432 
10433 
10434                [daemon_user_manager_.pl1]
10435                daemon_user_manager_:   ERROR_MESSAGE.   NAME.PROJ
10436                SOURCE terminated.
10437 
10438 
10439      Stream:   as (severity1)
10440 
10441      Time:     While system is running.
10442 
10443      Meaning:  An  error in  a daemon  process has  caused it  to
10444                terminate.   A  following  message  will  indicate
10445                whether  a  new  process  has  been  automatically
10446                created.
10447 
10448      Action:   If  the  daemon  is  logged  out, reinitialize the
10449                daemon  and  continue.   Otherwise,  a  new daemon
10450                process  is  created  automatically  and  you  can
10451                continue from there.
10452 
10453 
10454 daemon_user_manager_           181            08/03/23     MR12.7^L
10455 
10456 
10457 
10458 
10459                [daemon_user_manager_.pl1]
10460                daemon_user_manager_:   ERROR_MESSAGE.  No  MC ACS
10461                segment for message coordinator source SOURCE
10462 
10463 
10464      Stream:   as (severity1)
10465 
10466      Time:     In response to an operator command.
10467 
10468      Meaning:  The  message  coordinator  access  control segment
10469                >system_control_1>mc_acs>SOURCE.mcacs    was   not
10470                found.  It must be created  and given an ACL which
10471                permits  the   operator  to  logout   the  daemon.
10472                Therefore, the operator cannot logout the daemon.
10473 
10474      Action:   Contact the system programming staff._sa
10475 
10476 
10477                [daemon_user_manager_.pl1]
10478                daemon_user_manager_:   Event  entry  called  with
10479                null ev_msg_ptr
10480 
10481 
10482      Stream:   as (severity2)
10483 
10484      Time:     While system is running.
10485 
10486      Meaning:  This indicates an error in the Answering Service.
10487 
10488      Action:   Contact the system programming staff.
10489 
10490 
10491                [daemon_user_manager_.pl1]
10492                daemon_user_manager_:   Fatal  process  error loop
10493                for NAME.PROJ SOURCE.
10494                Daemon will be logged out.
10495 
10496 
10497 
10498      Stream:   as (severity1)
10499 
10500      Time:     While system is running.
10501 
10502      Meaning:  An  error in  a daemon  process has  caused it  to
10503                terminate repeatedly within  the last few minutes.
10504                Detection  of the  loop  causes  the daemon  to be
10505                logged out.
10506 
10507      Action:   Try to login the daemon again.  If it still fails,
10508                notify your System Administrator of the problem.
10509 
10510 
10511 
10512 daemon_user_manager_           182            08/03/23     MR12.7^L
10513 
10514 
10515 
10516 
10517                [daemon_user_manager_.pl1]
10518                daemon_user_manager_:   Invalid  signal  from NAME
10519                PROJ SOURCE
10520                daemon_user_manager_:    signal   was   "XXXXXXXX"
10521                YYY|ZZZZ
10522 
10523 
10524 
10525      Stream:   as (severity2)
10526 
10527      Time:     While system is running.
10528 
10529      Meaning:  This  message  may  result  from  an  error in the
10530                Answering Service,  an error in one  of the daemon
10531                processes, or  an attempt by an  unauthorized user
10532                to signal  the daemon user manager.   If the NAME,
10533                PROJ, and SOURCE cannot be determined, the process
10534                ID  of  the  sender  is  shown  instead.   The DUT
10535                (daemon user  table) entry affected is  located at
10536                YYY|ZZZZ in the Answering Service.
10537 
10538                The  signal is  ignored and  the Answering Service
10539                attempts to  continue.  If a daemon  user is named
10540                on the  first line of the message,  this user will
10541                probably be unable to continue.
10542 
10543      Action:   Contact the system programming staff.  If the user
10544                named in the message is  a daemon user, try typing
10545                "logout NAME  PROJ SOURCE", and if  this succeeds,
10546                log the user in again if necessary.
10547 
10548 
10549 
10550                [daemon_user_manager_.pl1]
10551                daemon_user_manager_:      NAME    PROJ     SOURCE
10552                terminated.  Daemon will be logged out.
10553 
10554 
10555      Stream:   as (severity2)
10556 
10557      Time:     While system is running.
10558 
10559      Meaning:  NAME is  the Person_id of the daemon,  PROJ is the
10560                Project_id  of  the  daemon,  and  SOURCE  is  the
10561                Message Coordinator source id  of the daemon.  The
10562                daemon encountered  a fatal process error  and was
10563                logged out to prevent the system from getting into
10564                a loop.
10565 
10566      Action:   Contact the system programming staff.  You can try
10567                logging  the daemon in  again, but if  the process
10568 
10569 
10570 daemon_user_manager_           183            08/03/23     MR12.7^L
10571 
10572 
10573                error is  recurrent the problem must  be corrected
10574                before the daemon will operate successfully.
10575 
10576 
10577 
10578                [daemon_user_manager_.pl1]
10579                daemon_user_manager_:  New process created.
10580 
10581 
10582      Stream:   as (severity1)
10583 
10584      Time:     While system is running.
10585 
10586      Meaning:  An  error in  a daemon  process has  caused it  to
10587                terminate.  A new process has been created.
10588 
10589      Action:   A new daemon process  is created automatically and
10590                you can continue from there.
10591 
10592 
10593 
10594                [daemon_user_manager_.pl1]
10595                daemon_user_manager_:    premature  STOPSTOP   for
10596                NAME.PROJ SOURCE
10597 
10598 
10599      Stream:   as (severity0)
10600 
10601      Time:     While system is running.
10602 
10603      Meaning:  This indicates a logic error in the supervisor, or
10604                CPU or memory hardware problems.
10605 
10606      Action:   No operator action is required.
10607 
10608 
10609                [daemon_user_manager_.pl1]
10610                daemon_user_manager_:     process   PERSON.PROJECT
10611                SOURCE ignored trm_ signal.
10612 
10613 
10614      Stream:   as (severity 1)
10615 
10616      Time:     While system is running.
10617 
10618      Meaning:  The  daemon process  PERSON.PROJECT using  message
10619                coordinator SOURCE had been  sent a trm_ signal to
10620                cause process termination, but the process did not
10621                respond  to  the  signal.   The  answering service
10622                proceeds  with the  bump, new_proc,  log out,  etc
10623                operation.
10624 
10625      Action:   No operator action is required.
10626 
10627 
10628 daemon_user_manager_           184            08/03/23     MR12.7^L
10629 
10630 
10631 
10632 
10633                [daemon_user_manager_.pl1]
10634                daemon_user_manager_:     process   PERSON.PROJECT
10635                SOURCE     ignored    wakeup     EVENT_MSG    from
10636                SENDER_PROCESS_ID
10637 
10638 
10639      Stream:   as (severity 1)
10640 
10641      Time:     While system is running.
10642 
10643      Meaning:  The  daemon process  PERSON.PROJECT using  message
10644                coordinator  SOURCE had  been sent  a wakeup  with
10645                EVENT_MSG   by   the   process   with   process_id
10646                SENDER_PROCESS_ID.  This event  message is unknown
10647                and will be ignored.
10648 
10649      Action:   No operator action is required.
10650 
10651 
10652                [daemon_user_manager_.pl1]
10653                daemon_user_manager_:  You cannot  new_proc to the
10654                requested authorization.
10655                Cannot  new_proc to  an authorization  outside the
10656                daemon's allowed range.
10657 
10658 
10659 
10660      Stream:   as (severity1)
10661 
10662      Time:     While system is running.
10663 
10664      Meaning:  A  daemon executed  an improper  new_proc command,
10665                trying to change to  an authorization greater than
10666                its  maximum allowed  authorization, or  less than
10667                its minimum allowed authorization, as specified in
10668                the    Person    Name    Table    (PNT),    System
10669                Administrator's  Table  (SAT)  and  Project Master
10670                File  (PMF).   The  new_proc  is  performed at the
10671                original authorization of the process.
10672 
10673      Action:   Contact the system programming staff._sa
10674 
10675 
10676                [dbm_man.pl1]
10677                dbm_man:     attempt    to    initialize   already
10678                initialized map for PV on dskX_NNS
10679 
10680 
10681      Stream:   BOS Typewriter (Crashes system)
10682 
10683      Time:     While system is running.
10684 
10685 
10686 dbm_man                        185            08/03/23     MR12.7^L
10687 
10688 
10689      Meaning:  This indicates a logic error in the supervisor, or
10690                CPU or memory hardware problems.
10691 
10692      Action:   Follow normal recovery procedures.
10693 
10694 
10695                [dbm_man.pl1]
10696                dbm_man:  bit map  relp not set in pvte  for PV on
10697                dskX_NNS
10698 
10699 
10700      Stream:   BOS Typewriter (Crashes system)
10701 
10702      Time:     While system is running.
10703 
10704      Meaning:  This indicates a logic error in the supervisor, or
10705                CPU or memory hardware problems.
10706 
10707      Action:   Follow normal recovery procedures.
10708 
10709 
10710                [dbm_man.pl1]
10711                dbm_man:  Cannot get ASTE for dbm_seg
10712 
10713 
10714      Stream:   BOS Typewriter (Crashes system)
10715 
10716      Time:     System Intialization.
10717 
10718      Meaning:  The  system was unable  to create the  dbm_seg and
10719                obtain an ASTE for this segment.
10720 
10721      Action:   Contact the system programming staff._sa
10722 
10723 
10724                [dbm_man.pl1]
10725                dbm_man:  csl failure
10726 
10727 
10728      Stream:   Logged in SYSERR log.
10729 
10730      Time:     While system is running.
10731 
10732      Meaning:  The CSL instruction appears  to have failed on one
10733                of the processors.
10734 
10735      Action:   No operator action is required.
10736 
10737 
10738                [dbm_man.pl1]
10739                dbm_man:  unable to allocate dumper bit map for PV
10740                on dskX_NNS
10741 
10742 
10743 
10744 dbm_man                        186            08/03/23     MR12.7^L
10745 
10746 
10747      Stream:   BOS Typewriter (Crashes system)
10748 
10749      Time:     While system is running.
10750 
10751      Meaning:  The system was unable to allocate a dumper bit map
10752                in dbm_seg  for the volume on  dskX_NNS.  Too many
10753                volumes  are online,  or there  is something wrong
10754                with the volume header.
10755 
10756      Action:   Follow normal recovery procedures.
10757 
10758 
10759                [dbm_man.pl1]
10760                dbm_man:  unable to initialize area:  ERROR_MESS
10761 
10762 
10763      Stream:   BOS Typewriter (Crashes system)
10764 
10765      Time:     While system is running.
10766 
10767      Meaning:  This indicates a logic error in the supervisor, or
10768                CPU or memory hardware problems.
10769 
10770      Action:   Follow normal recovery procedures.
10771 
10772 
10773                [deactivate_for_demount.pl1]
10774                deactivate_for_demount:  Error  freeing vtocx OOOO
10775                on dskX_NN for UID.  ERRORMESSAGE.
10776 
10777 
10778      Stream:   Logged in SYSERR log.
10779 
10780      Time:     During system shutdown.
10781 
10782      Meaning:  The  VTOCE for  a deciduous  segment could  not be
10783                freed for the reason indicated.  The VTOCE will be
10784                freed   by   the   next   volume   salvage  or  by
10785                delete_old_pdds.
10786 
10787      Action:   No operator action is required.
10788 
10789 
10790                [deactivate_segs.pl1]
10791                deactivate_segs:  unflushed trailer
10792 
10793 
10794      Stream:   BOS Typewriter (Crashes system)
10795 
10796      Time:     While system is running.
10797 
10798      Meaning:  After destroying a process,  the system found that
10799                some system trailer (specifying connection of that
10800 
10801 
10802 deactivate_segs                187            08/03/23     MR12.7^L
10803 
10804 
10805                process  to some  segment) still  exists for  that
10806                process  in  str_seg.   This  indicates  that some
10807                segment  was  improperly   disconnected  from  the
10808                process at some time.This  indicates a logic error
10809                in  the  supervisor,  or  CPU  or  memory hardware
10810                problems.
10811 
10812      Action:   Follow normal recovery procedures.
10813 
10814 
10815                [debug_check.pl1]
10816                debug_check:  too many parameters on parm cards
10817 
10818 
10819      Stream:   BOS Typewriter.
10820 
10821      Time:     System Intialization.
10822 
10823      Meaning:  A  total of  14 options  may be  specified on PARM
10824                cards.   This limit   has been  exceeded.  Options
10825                after the 14th will be ignored.
10826 
10827      Action:   Correct  the configuration   deck before  the next
10828                bootload.
10829 
10830 
10831 
10832                [obs_reconfigure.pl1]
10833                delcpu:  Cannot stop CPU X.
10834 
10835 
10836      Stream:   Initializer process output.
10837 
10838      Time:     In response to an operator command.
10839 
10840      Meaning:  CPU X did not respond  to a command to stop within
10841                the expected time.  The  CPU may be malfunctioning
10842                or in STEP, or it may be in a very tight loop.
10843 
10844      Action:   Check the CPU panel.   If the processor appears to
10845                be in a  loop, it may be possible to  break it out
10846                by  placing zeros  in the  processor switches  and
10847                using  the EXECUTE  button to  cause a  fault; but
10848                this action sometimes causes  the system to crash,
10849                depending on where the loop is.
10850 
10851 
10852 
10853                [obs_reconfigure.pl1]
10854                delcpu:  CPU X is not online.
10855 
10856 
10857      Stream:   Initializer process output.
10858 
10859 
10860 delcpu                         188            08/03/23     MR12.7^L
10861 
10862 
10863      Time:     In response to an operator command.
10864 
10865      Meaning:  A  delcpu X  command finds  that CPU  X is already
10866                deleted.
10867 
10868      Action:   No operator action is required.
10869 
10870 
10871                [obs_reconfigure.pl1]
10872                delcpu:  CPU X is the only CPU.
10873 
10874 
10875      Stream:   Initializer process output.
10876 
10877      Time:     In response to an operator command.
10878 
10879      Meaning:  A  delcpu X command  attempted to delete  the last
10880                CPU.  No action was taken.
10881 
10882      Action:   No operator action is required.
10883 
10884 
10885                [obs_reconfigure.pl1]
10886                delcpu:   Illegal command or  subroutine argument.
10887                BLAH
10888 
10889 
10890      Stream:   Initializer process output.
10891 
10892      Time:     In response to an operator command.
10893 
10894      Meaning:  Invalid input was typed.
10895 
10896      Action:   Enter a corrected command line.
10897 
10898 
10899                [obs_reconfigure.pl1]
10900                delcpu:  Reconfiguration database is locked.
10901 
10902 
10903      Stream:   Initializer process output.
10904 
10905      Time:     In response to an operator command.
10906 
10907      Meaning:  Another  process   is  performing  reconfiguration
10908                currently, or  a fault during  reconfiguration has
10909                left the reconfiguration tables locked.
10910 
10911      Action:   If  it  is  certain   that  no  other  process  is
10912                reconfiguring,   and   that    the   fault   which
10913                interrupted  reconfiguration has  been cured,  the
10914                reconfigure$force_unlock  command may  be used  to
10915                clear the lock at the direction of system staff.
10916 
10917 
10918 delcpu                         189            08/03/23     MR12.7^L
10919 
10920 
10921 
10922 
10923                [obs_reconfigure.pl1]
10924                delcpu:  Wrong number of arguments supplied.
10925 
10926 
10927      Stream:   Initializer process output.
10928 
10929      Time:     In response to an operator command.
10930 
10931      Meaning:  Invalid input was typed.
10932 
10933      Action:   Enter a corrected command line.
10934 
10935 
10936                [delentry.pl1]
10937                delentry:  deleting damaged dir PATH for USERID
10938 
10939 
10940      Stream:   Logged in SYSERR log.
10941 
10942      Time:     While system is running.
10943 
10944      Meaning:  An  attempt to delete  a directory found  that the
10945                directory  header had  a zero  UID.  The directory
10946                was deleted anyway.
10947 
10948      Action:   No operator action is required.
10949 
10950 
10951                [delentry.pl1]
10952                delentry:   error  from  hash$out  on  "NAME"  for
10953                USERID.  ERROR_CODE
10954 
10955 
10956      Stream:   Logged in SYSERR log.
10957 
10958      Time:     While system is running.
10959 
10960      Meaning:  An attempt to delete the  entry name NAME from the
10961                directory  hash table   failed.  This  indicates a
10962                logic  error in the  supervisor, or CPU  or memory
10963                hardware problems.
10964 
10965      Action:   No operator action is required.
10966 
10967 
10968                [delentry.pl1]
10969                delentry:   error  from   terminate_  for  USERID.
10970                ERROR_CODE
10971 
10972 
10973      Stream:   Logged in SYSERR log.
10974 
10975 
10976 delentry                       190            08/03/23     MR12.7^L
10977 
10978 
10979      Time:     While system is running.
10980 
10981      Meaning:  An error code was returned  while trying to make a
10982                directory   unknown  while   deleting  it.    This
10983                indicates a logic error  in the supervisor, or CPU
10984                or memory hardware problems.
10985 
10986      Action:   No operator action is required.
10987 
10988 
10989                [delentry.pl1]
10990                delentry:   priv_dfile  error  deleting  vtoce for
10991                PATH for USERID.  ERROR_CODE
10992 
10993 
10994      Stream:   Logged in SYSERR log.
10995 
10996      Time:     While system is running.
10997 
10998      Meaning:  A privileged call to delete a segment discovered a
10999                branch  with not  VTOC entry.   This situation  is
11000                called  a "connection   failure."  The  branch was
11001                deleted anyway.
11002 
11003      Action:   No operator action is required.
11004 
11005 
11006                [delete_vtoce.pl1]
11007                delete_vtoce:    cannot   add   time/page  product
11008                (SEGTPP  DIRTPP) to  pvid  PPP  vtocx VVV  uid UUU
11009                ERRORMESSAGE
11010 
11011 
11012 
11013      Stream:   Logged in SYSERR log.
11014 
11015      Time:     While system is running.
11016 
11017      Meaning:  During  the deletion  of a  directory which  had a
11018                quota  account, a   difficulty was  encountered in
11019                reflecting  its time/page product  upward.  SEGTPP
11020                and DIRTPP are the  time/page product for segments
11021                and directories, respectively.
11022 
11023      Action:   Contact the system programming staff._sa
11024 
11025 
11026                [delete_vtoce.pl1]
11027                delete_vtoce:  from  quotaw, pvid PPP.   vtocx VVV
11028                ERRORMESSAGE
11029 
11030 
11031      Stream:   Logged in SYSERR log.
11032 
11033 
11034 delete_vtoce                   191            08/03/23     MR12.7^L
11035 
11036 
11037      Time:     While system is running.
11038 
11039      Meaning:  While  deleting  a  directory  which  had  a quota
11040                account, a  quota handling problem  usually record
11041                quota overflow, was encountered.
11042 
11043      Action:   No operator action is required.
11044 
11045 
11046                [obs_reconfigure.pl1]
11047                Deleted CPU X.
11048 
11049 
11050      Stream:   Initializer process output.
11051 
11052      Time:     In response to an operator command.
11053 
11054      Meaning:  This  is the  response  to  a successful  delcpu X
11055                command.
11056 
11057      Action:   No operator action is required.
11058 
11059 
11060                [obs_reconfigure.pl1]
11061                delmain:  Abs wired pages in memory.
11062 
11063 
11064      Stream:   Initializer process output.
11065 
11066      Time:     In response to an operator command.
11067 
11068      Meaning:  A delmain  command attempted to delete  a range of
11069                pages  which included  some pages  which cannot be
11070                deleted.  No action was taken.
11071 
11072      Action:   Enter a corrected command line.
11073 
11074 
11075                [obs_reconfigure.pl1]
11076                delmain:  Illegal command  or subroutine argument.
11077                BLAH
11078 
11079 
11080      Stream:   Initializer process output.
11081 
11082      Time:     In response to an operator command.
11083 
11084      Meaning:  Invalid input was typed.
11085 
11086      Action:   Enter a corrected command line.
11087 
11088 
11089 
11090 
11091 
11092 delmain                        192            08/03/23     MR12.7^L
11093 
11094 
11095 
11096 
11097                [obs_reconfigure.pl1]
11098                delmain:  Not enough main memory left.
11099 
11100 
11101      Stream:   Initializer process output.
11102 
11103      Time:     In response to an operator command.
11104 
11105      Meaning:  A  delmain  command  attempted  to  delete so much
11106                memory that the system would be unable to function
11107                correctly.  No action was taken.
11108 
11109      Action:   Enter a corrected command line.
11110 
11111 
11112                [obs_reconfigure.pl1]
11113                delmain:  Reconfiguration database is locked.
11114 
11115 
11116      Stream:   Initializer process output.
11117 
11118      Time:     In response to an operator command.
11119 
11120      Meaning:  Another  process   is  performing  reconfiguration
11121                currently, or  a fault during  reconfiguration has
11122                left the reconfiguration tables locked.
11123 
11124      Action:   If  it  is  certain   that  no  other  process  is
11125                reconfiguring,   and   that    the   fault   which
11126                interrupted  reconfiguration has  been cured,  the
11127                reconfigure$force_unlock  command may  be used  to
11128                clear the lock at the direction of system staff.
11129 
11130 
11131 
11132                [obs_reconfigure.pl1]
11133                delmain:  Request is not  within range of a single
11134                controller.  MAIN XXX
11135 
11136 
11137      Stream:   Initializer process output.
11138 
11139      Time:     In response to an operator command.
11140 
11141      Meaning:  A  delmain command must  specify a range  of pages
11142                which lies  completely within one  controller.  No
11143                action was taken.
11144 
11145      Action:   Enter a corrected command line.
11146 
11147 
11148 
11149 
11150 delmain                        193            08/03/23     MR12.7^L
11151 
11152 
11153 
11154 
11155                [obs_reconfigure.pl1]
11156                delmain:  Wrong number of arguments supplied.
11157 
11158 
11159      Stream:   Initializer process output.
11160 
11161      Time:     In response to an operator command.
11162 
11163      Meaning:  Invalid input was typed.
11164 
11165      Action:   Enter a corrected command line.
11166 
11167 
11168                [obs_reconfigure.pl1]
11169                delmem:  Abs wired pages in MEM Y.
11170 
11171 
11172      Stream:   Initializer process output.
11173 
11174      Time:     In response to an operator command.
11175 
11176      Meaning:  An  attempt  was  made  to  delete  a memory which
11177                included some  pages which cannot be  deleted.  No
11178                action was taken.
11179 
11180      Action:   The memory cannot be deleted.
11181 
11182 
11183                [obs_reconfigure.pl1]
11184                delmem:   Illegal command or  subroutine argument.
11185                BLAH
11186 
11187 
11188      Stream:   Initializer process output.
11189 
11190      Time:     In response to an operator command.
11191 
11192      Meaning:  Invalid input was typed.
11193 
11194      Action:   Enter a corrected command line.
11195 
11196 
11197                [obs_reconfigure.pl1]
11198                delmem:  MEM Y is not online.
11199 
11200 
11201      Stream:   Initializer process output.
11202 
11203      Time:     In response to an operator command.
11204 
11205 
11206 
11207 
11208 delmem                         194            08/03/23     MR12.7^L
11209 
11210 
11211      Meaning:  A delmem Y command was typed but no such memory is
11212                in use.
11213 
11214      Action:   No operator action is required.
11215 
11216 
11217                [obs_reconfigure.pl1]
11218                delmem:  Not enough main memory to remove MEM Y.
11219 
11220 
11221      Stream:   Initializer process output.
11222 
11223      Time:     In response to an operator command.
11224 
11225      Meaning:  The system  would be unable to  function correctly
11226                if SCU  Y and its memory were  deleted.  No action
11227                was taken.
11228 
11229      Action:   Try something else.
11230 
11231 
11232                [obs_reconfigure.pl1]
11233                delmem:  Reconfiguration database is locked.
11234 
11235 
11236      Stream:   Initializer process output.
11237 
11238      Time:     In response to an operator command.
11239 
11240      Meaning:  Another  process   is  performing  reconfiguration
11241                currently, or  a fault during  reconfiguration has
11242                left the reconfiguration tables locked.
11243 
11244      Action:   If  it  is  certain   that  no  other  process  is
11245                reconfiguring,   and   that    the   fault   which
11246                interrupted  reconfiguration has  been cured,  the
11247                reconfigure$force_unlock  command may  be used  to
11248                clear the lock at the direction of system staff.
11249 
11250 
11251 
11252                [add_scu.pl1]
11253                delmem:  Removed MEM X.
11254 
11255 
11256      Stream:   BOS Typewriter.
11257 
11258      Time:     In response to an operator command.
11259 
11260      Meaning:  The system control unit X has been deleted.
11261 
11262      Action:   No operator action is required.
11263 
11264 
11265 
11266 delmem                         195            08/03/23     MR12.7^L
11267 
11268 
11269 
11270 
11271                [obs_reconfigure.pl1]
11272                delmem:  Wrong number of arguments supplied.
11273 
11274 
11275      Stream:   Initializer process output.
11276 
11277      Time:     In response to an operator command.
11278 
11279      Meaning:  Invalid input was typed.
11280 
11281      Action:   Enter a corrected command line.
11282 
11283 
11284                [demount_pv.pl1]
11285                demount_pv:  ast out of sync
11286 
11287 
11288      Stream:   BOS Typewriter (Crashes system)
11289 
11290      Time:     Volume demounting or system shutdown.
11291 
11292      Meaning:  The  volume  demounter  has  detected  irreparable
11293                damage to the system segment table (SST).
11294 
11295      Action:   Emergency  shutdown  will  fail,  and  need not be
11296                attempted.  Follow normal  recovery procedures for
11297                ESD failure.
11298 
11299 
11300 
11301                [demount_pv.pl1]
11302                demount_pv:     ioi_PROGNAME     for    DRIVENAME:
11303                ERRORMESSAGE
11304 
11305 
11306      Stream:   BOS Typewriter.
11307 
11308      Time:     Volume demounting.
11309 
11310      Meaning:  In  attempting to  cycle down  drive DRIVENAME, an
11311                unexpected  error   was  received  from   the  I/O
11312                Interfacer.  The drive may not be cycled down.
11313 
11314      Action:   Notify the  system programming staff.   Cycle down
11315                the drive if it was not cycled down.
11316 
11317 
11318                [demount_pv.pl1]
11319                demount_pv:     vtoc    cleanup    of   DRIVENAME:
11320                ERRORMESSAGE
11321 
11322 
11323 
11324 demount_pv                     196            08/03/23     MR12.7^L
11325 
11326 
11327      Stream:   BOS Typewriter.
11328 
11329      Time:     Volume demounting or shutdown.
11330 
11331      Meaning:  An  unexpected error  was encountered  in flushing
11332                VTOC information  out to a volume  being shut down
11333                or demounted.   The volume will not  be demounted.
11334                message.
11335 
11336      Action:   Contact the system  programming staff.  Attempt to
11337                repeat the demount of  the logical volume, if this
11338                is  not  during  shutdown.   The  physical  volume
11339                involved may have to be salvaged.
11340 
11341 
11342 
11343                [demount_pv.pl1]
11344                demounted DRIVENAME
11345 
11346 
11347      Stream:   BOS Typewriter.
11348 
11349      Time:     Volume   demounting,  in  response   to  delete_lv
11350                command or user action.
11351 
11352      Meaning:  The disk pack on  drive DRIVENAME was successfully
11353                demounted.
11354 
11355      Action:   No operator action is required.
11356 
11357 
11358                [disk_table_.pl1]
11359                demounted lv LVNAME
11360 
11361 
11362      Stream:   Initializer process output.
11363 
11364      Time:     While system is running.
11365 
11366      Meaning:  The  demount  of  the  logical  volume  LVNAME  is
11367                complete.
11368 
11369      Action:   No operator action is required.
11370 
11371 
11372                [device_acct_.pl1]
11373                device_acct_$init:  ERROR_MESSAGE.  device_table
11374 
11375 
11376      Stream:   as (severity 2)
11377 
11378      Time:     System Intialization.
11379 
11380 
11381 
11382 device_acct_$init              197            08/03/23     MR12.7^L
11383 
11384 
11385      Meaning:  An   error   occurred   which   initializing   the
11386                device_table.     ERROR_MESSAGE   is    the   text
11387                associated  with  the  error  code  describing the
11388                error.  Device accounting  is disabled, and system
11389                initialization fails.
11390 
11391      Action:   Contact the system programming staff.
11392 
11393 
11394                [device_acct_.pl1]
11395                device_acct_$off:    device   N   (ACCT_TYPE_NAME,
11396                DEV_NAME) not in device table for PERSON.PROJECT
11397 
11398 
11399      Stream:   as (severity 0)
11400 
11401      Time:     While system is running.
11402 
11403      Meaning:  Device DEV_NAME, which  has device accounting type
11404                number  N associated with  ACCT_TYPE_NAME devices,
11405                was  not found   in PERSON.PROJECT's  device table
11406                entries.  Probable  cause is damage to  the device
11407                table.
11408 
11409      Action:   Contact the system programming staff._sa
11410 
11411 
11412                [device_acct_.pl1]
11413                device_acct_:   deve.pdtep (PTR1) not  = ute.pdtep
11414                (PTR2) for PERSON.PROJECT.
11415 
11416 
11417      Action:   as (severity 2)
11418 
11419      Time:     While system is running.
11420 
11421      Meaning:  The Project Definition  Table entry pointer (PTR1)
11422                stored  in  the  device  table  for PERSON.PROJECT
11423                differs from the PDT  entry pointer stored in that
11424                user's  User Table   Entry (UTE).This  indicates a
11425                logic  error in the  supervisor, or CPU  or memory
11426                hardware problems.
11427 
11428      Action:   Contact the system programming staff.
11429 
11430 
11431                [device_acct_.pl1]
11432                device_acct_:  ERROR_MESSAGE.   Attempting to lock
11433                PDT entry of PERSON.PROJECT
11434 
11435 
11436      Stream:   as (severity 2)
11437 
11438 
11439 
11440 device_acct_                   198            08/03/23     MR12.7^L
11441 
11442 
11443      Time:     While system is running.
11444 
11445      Meaning:  An attempt was made to lock the Project Definition
11446                Table  (PDT) entry   for PERSON.PROJECT  to update
11447                device  usage charges  for the  user.  Locking did
11448                not succeed within 15 seconds, so the charges were
11449                not  updated.  If  the attempt  occurred during an
11450                accounting  update, the  charges will  continue to
11451                accrue  until  the  next  update,  at  which  time
11452                locking the PDT entry  is again attempted.  If the
11453                original attempt  occurred as part of  a logout or
11454                new_proc operation, the device charges are lost.
11455 
11456      Action:   Contact the system programming staff._sa
11457 
11458 
11459                [page_error.alm]
11460                device_control:  invalid pvtx XX
11461 
11462 
11463      Stream:   BOS Typewriter (Crashes system)
11464 
11465      Time:     While system is running.
11466 
11467      Meaning:  An  invalid  PVT  index  XX  was  found  by device
11468                control, or an invalid device type appeared in the
11469                PVT entry  of that index.  This  indicates a logic
11470                error in the supervisor, or CPU or memory hardware
11471                problems.
11472 
11473      Action:   Follow normal recovery procedures.
11474 
11475 
11476                [dial_ctl_.pl1]
11477                dial_ctl_:   Autocall   channel  CHANNEL  declared
11478                multi-class,     but      does     not     support
11479                set_required_access_class.
11480 
11481 
11482      Stream:   as (severity2)
11483 
11484      Time:     While system is running._
11485 
11486      Meaning:  The  autocall channel   CHANNEL has  been declared
11487                multi-class  in   the  CDT,  but   the  underlying
11488                multiplexer      does     not      support     the
11489                set_required_access_class   control  order.    The
11490                channel  should be  defined as  single class.  The
11491                user's dial out request was refused.
11492 
11493      Action:   Contact the system programming staff._sa
11494 
11495 
11496 
11497 
11498 dial_ctl_                      199            08/03/23     MR12.7^L
11499 
11500 
11501 
11502 
11503                [dial_ctl_.pl1]
11504                dial_ctl_:  Can't find process WWWWWWWWWWW
11505 
11506 
11507      Stream:   as (severity0)
11508 
11509      Time:     While system is running.
11510 
11511      Meaning:  An  invalid signal  was received  by the secondary
11512                terminal manager.
11513 
11514      Action:   Note for system programmer action.
11515 
11516 
11517                [dial_ctl_.pl1]
11518                dial_ctl_:  Channel CHANNEL (AIM_CLASS, SERV_TYPE)
11519                hung up on Initializer
11520 
11521 
11522      Stream:   as (severity1)
11523 
11524      Time:     While system is running.
11525 
11526      Meaning:  The  channel CHANNEL  with access  class AIM_CLASS
11527                and  service  type  SERV_TYPE  hung  up.   It  had
11528                previously been dialed to the Initializer.
11529 
11530      Action:   No operator action is required.
11531 
11532 
11533                [dial_ctl_.pl1]
11534                dial_ctl_:  Channel CHANNEL (AIM_CLASS, SERV_TYPE)
11535                hung up on missing process WWWWWWWWWWWW
11536 
11537 
11538      Stream:   as (severity1)
11539 
11540      Time:     While system is running.
11541 
11542      Meaning:  The  channel CHANNEL  with access  class AIM_CLASS
11543                and service  type SERV_TYPE hung up.   It had been
11544                dialed  to  a  process,   but  the  system  cannot
11545                determine what  process it had been  connected to.
11546                The process may have  terminated before the hangup
11547                was detected.
11548 
11549      Action:   If  this  happens  often,  inform  the programming
11550                staff.
11551 
11552 
11553                [dial_ctl_.pl1]
11554 
11555 
11556 dial_ctl_                      200            08/03/23     MR12.7^L
11557 
11558 
11559                dial_ctl_:  Channel CHANNEL  dialed to Initializer
11560                {(PERSON.PROJECT)}
11561 
11562 
11563      Stream:   as (severity2)
11564 
11565      Time:     While system is running.
11566 
11567      Meaning:  An additional secondary terminal has been attached
11568                to the  Initializer process as a result  of a dial
11569                system command.  CHANNEL  specifies which terminal
11570                dialed Initializer.
11571 
11572      Action:   If  this  terminal  has   been  connected  to  the
11573                Initializer  by  an  authorized  operations  staff
11574                member, proceed  to use it by  issuing an "accept"
11575                command  and possibly  the "substty"  command.  If
11576                this  is  an  invalid  attempt  to  connect to the
11577                system,  type  "drop  CHANNEL"  to  disconnect the
11578                terminal.
11579 
11580 
11581 
11582                [dial_ctl_.pl1]
11583                dial_ctl_:  Channel CHANNEL hung up after dial_out
11584                for PERSON.PROJECT
11585 
11586 
11587      Stream:   as (severity0)
11588 
11589      Time:     While system is running.
11590 
11591      Meaning:  During   a   dial_out   of   channel   CHANNEL  by
11592                PERSON.PROJECT, the channel hung up.  The dial_out
11593                attempt was aborted.
11594 
11595      Action:   No operator action is required.
11596 
11597 
11598                [dial_ctl_.pl1]
11599                dial_ctl_:  Dialing channel CHANNEL (ACC_CLASS) to
11600                DESTINATION   for   PERSON.PROJECT   {using   comm
11601                privilege}
11602 
11603 
11604      Stream:   as (severity0)
11605 
11606      Time:     While system is running.
11607 
11608      Meaning:  The  user PERSON.PROJECT  is dialing  out on  dial
11609                channel CHANNEL with access class ACC_CLASS to the
11610                destination DESTINATION.  If this log message ends
11611                with  "using  comm  privilege",  then  the process
11612 
11613 
11614 dial_ctl_                      201            08/03/23     MR12.7^L
11615 
11616 
11617                dialing  out  has  used   the  comm  privilege  to
11618                circumvent AIM restrictions.
11619 
11620      Action:   No operator action is required.
11621 
11622 
11623                [dial_ctl_.pl1]
11624                dial_ctl_:            ERROR_MESSAGE           From
11625                get_required_access_class control order on channel
11626                CHANNEL.
11627 
11628 
11629      Stream:   as (severity0)
11630 
11631      Time:     While system is running.
11632 
11633      Meaning:  While attempting to  determine whether the channel
11634                CHANNEL had any  access class restrictions imposed
11635                on it by the hardcore, ERROR_MESSAGE was returned.
11636                The request in progress was aborted.
11637 
11638      Action:   Note for system programmer action.
11639 
11640 
11641                [dial_ctl_.pl1]
11642                dial_ctl_:  ERROR_MESSAGE.  Can't  find PNT entry:
11643                PERSON_ID
11644 
11645 
11646      Stream:   as (severity2)
11647 
11648      Time:     While system is running.
11649 
11650      Meaning:  An attempt was made to  find the Person Name Table
11651                entry  of  the  PERSON_ID   specified  in  a  dial
11652                preaccess  command.   However,  an  error occurred
11653                which searching in the PNT.
11654 
11655      Action:   Contact the system programming staff._sa
11656 
11657 
11658                [dial_ctl_.pl1]
11659                dial_ctl_:  ERROR_MESSAGE.   dial_out (CHANNEL for
11660                PERSON.PROJECT) failed.
11661 
11662 
11663      Stream:   as (severity0)
11664 
11665      Time:     While system is running.
11666 
11667      Meaning:  While attempting  to dial_out channel  CHANNEL for
11668                PERSON.PROJECT,  the error  ERROR_MESSAGE occured.
11669                The dial_out attempt was aborted.
11670 
11671 
11672 dial_ctl_                      202            08/03/23     MR12.7^L
11673 
11674 
11675      Action:   No operator action is required.
11676 
11677 
11678                [dial_ctl_.pl1]
11679                dial_ctl_:   ERROR_MESSAGE.  after  dial_out order
11680                (CHANNEL for PERSON.PROJECT)
11681 
11682 
11683      Stream:   as (severity0)
11684 
11685      Time:     While system is running.
11686 
11687      Meaning:  The user  PERSON.PROJECT is attempting  a dial_out
11688                of  channel CHANNEL.   The dial_out  control order
11689                produced  the error  ERROR_MESSAGE.  The  dial_out
11690                attempt is aborted.
11691 
11692      Action:   Note for system programmer action.
11693 
11694 
11695                [dial_ctl_.pl1]
11696                dial_ctl_:   ERROR_MESSAGE.  Attempting  to detach
11697                CHANNEL from PERSON.PROJECT
11698 
11699 
11700      Stream:   as (severity0)
11701 
11702      Time:     While system is running.
11703 
11704      Meaning:  An  attempt  to  disconnect  channel  CHANNEL from
11705                PERSON.PROJECT  failed.    ERROR_MESSAGE  explains
11706                why.
11707 
11708      Action:   Note for system programmer action.
11709 
11710 
11711                [dial_ctl_.pl1]
11712                dial_ctl_:       ERROR_MESSAGE.       call      to
11713                astty_$tty_new_proc of  CHANNEL for PERSON.PROJECT
11714                failed
11715 
11716 
11717      Stream:   as (severity0)
11718 
11719      Time:     While system is running.
11720 
11721      Meaning:  An  attempt  to  connect  the  channel  CHANNEL to
11722                PERSON.PROJECT  failed.   ERROR_MESSAGE  indicates
11723                why.
11724 
11725      Action:   Contact the system programming staff._sa
11726 
11727 
11728 
11729 
11730 dial_ctl_                      203            08/03/23     MR12.7^L
11731 
11732 
11733                [dial_ctl_.pl1]
11734                dial_ctl_:  ERROR_MESSAGE.  Could not check access
11735                to >sc1>admin_acs>tandd.acs for PERSON.PROJECT.
11736 
11737 
11738      Stream:   as (severity0)
11739 
11740      Time:     While system is running.
11741 
11742      Meaning:  The user PERSON.PROJECT  attempted to tandd_attach
11743                a  communications  channel.    This  operation  is
11744                controlled  by  rw  access   to  the  ACS  segment
11745                specified.   For  the  reason  ERROR_MESSAGE,  the
11746                answering  service could  not check  access to the
11747                segment.    The  user  tandd_attach   request  was
11748                refused.
11749 
11750      Action:   Contact the system programming staff._sa
11751 
11752 
11753                [dial_ctl_.pl1]
11754                dial_ctl_:          ERROR_MESSAGE.         getting
11755                dial_out_status   or   tty   info   (CHANNEL   for
11756                PERSON.PROJECT)
11757 
11758 
11759      Stream:   as (severity0)
11760 
11761      Time:     While system is running.
11762 
11763      Meaning:  During   a   dial_out   of   channel   CHANNEL  by
11764                PERSON.PROJECT,   the   error   ERROR_MESSAGE  was
11765                returned  while  attempting  to  determine  if the
11766                dial_out control order succeeded or failed.
11767 
11768      Action:   No operator action is required.
11769 
11770 
11771                [dial_ctl_.pl1]
11772                dial_ctl_:   ERROR_MESSAGE.  Issuing  tandd_attach
11773                control order for channel CHAN
11774 
11775 
11776      Stream:   as (severity0)
11777 
11778      Time:     While system is running.
11779 
11780      Meaning:  The user PERSON.PROJECT  attempted to tandd_attach
11781                a  communications  channel  which  failed  for the
11782                reason   given   by   ERROR_MESSAGE.    The   user
11783                tandd_attach request was refused.
11784 
11785      Action:   Contact the system programming staff._sa
11786 
11787 
11788 dial_ctl_                      204            08/03/23     MR12.7^L
11789 
11790 
11791 
11792 
11793                [dial_ctl_.pl1]
11794                dial_ctl_:  ndialed negative CHANNEL
11795 
11796 
11797      Stream:   as (severity0)
11798 
11799      Time:     While system is running.
11800 
11801      Meaning:  The count  of secondary consoles for a  user is in
11802                error.  A  terminal is hanging up  which claims to
11803                be attached  to a user  but his count  of attached
11804                terminals is zero.
11805 
11806      Action:   Note for system programmer action.
11807 
11808 
11809                [dial_ctl_.pl1]
11810                dial_ctl_:              Program             error.
11811                as_request_sender.version (N) not  correct in dial
11812                request.  Should be M.
11813 
11814 
11815      Stream:   as (severity1)
11816 
11817      Time:     While system is running.
11818 
11819      Meaning:  There is a mismatch in  the version number used by
11820                the the programs  as_request_server_ and dial_ctl_
11821                for the as_request_sender_ structure.
11822 
11823      Action:   Contact the system programming staff.
11824 
11825 
11826                [dial_ctl_.pl1]
11827                dial_ctl_:     Refused   unknown    request   from
11828                PERSON.PROJECT; ERROR_MESSAGE REASON
11829 
11830 
11831      Stream:   as (severity0)
11832 
11833      Time:     While system is running.
11834 
11835      Meaning:  PERSON.PROJECT send  a dial_server request  to the
11836                Initializer  of unknown  format.  It  was rejected
11837                for  the reasons   specified in  ERROR_MESSAGE and
11838                REASON.
11839 
11840 
11841 
11842                [dial_ctl_.pl1]
11843                dial_ctl_:    Rejected    unknown   request   from
11844 
11845 
11846 dial_ctl_                      205            08/03/23     MR12.7^L
11847 
11848 
11849                PERSON.PROJECT.    No   request   flags   set   in
11850                dial_server_request.
11851 
11852 
11853      Stream:   as (severity0)
11854 
11855      Time:     While system is running.
11856 
11857      Meaning:  The  user  PERSON.PROJECT  attempted  to  send  an
11858                dial_server request to the Initializer, but failed
11859                to specify what type of request he/she wanted.
11860 
11861      Action:   No operator action is required.
11862 
11863 
11864                [dial_ctl_.pl1]
11865                dial_ctl_:    sat.ht  has   PROJECT_ID,  sat   has
11866                OTHER_PROJECT_ID at LOC.
11867 
11868 
11869      Stream:   as (severity2)
11870 
11871      Time:     While system is running.
11872 
11873      Meaning:  The  System Administrator's Table  is inconsistent
11874                with the location information in its hash table.
11875 
11876      Action:   Contact the system programming staff._sa
11877 
11878 
11879                [dial_ctl_.pl1]
11880                dial_ctl_:  Tracing turned off
11881 
11882 
11883      Stream:   as (severity1)
11884 
11885      Time:     While system is running.
11886 
11887      Meaning:  A  system  administrator  has  disabled  dial_ctl_
11888                tracing.
11889 
11890      Action:   No operator action is required.
11891 
11892 
11893                [dial_ctl_.pl1]
11894                dial_ctl_:  Tracing turned on.
11895 
11896 
11897      Stream:   as (severity1)
11898 
11899      Time:     While system is running.
11900 
11901 
11902 
11903 
11904 dial_ctl_                      206            08/03/23     MR12.7^L
11905 
11906 
11907      Meaning:  A system administrator had  enabled tracing of the
11908                dial_ctl_ program.   Many status messages  will be
11909                logged and printed on the console.
11910 
11911      Action:   No operator action is required.
11912 
11913 
11914                [dial_ctl_.pl1]
11915                DIALIN  {PERSON1.PROJECT1}  CHANNEL  to  QUALIFIER
11916                {PERSON2.PROJECT2}
11917 
11918 
11919      Stream:   as (severity0)
11920 
11921      Time:     While system is running.
11922 
11923      Meaning:  A  user on  channel  CHANNEL  has used  the "dial"
11924                preaccess  command  to  dial  the  dial  qualifier
11925                QUALIFIER  owned  by   PERSON2.PROJECT2.   If  the
11926                check_acs  "slave_dial"  flags   was  on  for  the
11927                channel,   then  PERSON1.PROJECT1   specifies  the
11928                identified user.
11929 
11930      Action:   No operator action is required.
11931 
11932 
11933                [dial_ctl_.pl1]
11934                DIALIN   DENIED   {PERSON1.PROJECT1}   CHANNEL  to
11935                QUALIFIER {PERSON2.PROJECT2} REASON
11936 
11937 
11938      Stream:   as (severity0)
11939 
11940      Time:     While system is running.
11941 
11942      Meaning:  A  user on  channel CHANNEL  attempted to  use the
11943                "dial"  preaccess command   to dial  to QUALIFIER,
11944                owned   by  PERSON2.PROJECT2.   The   attempt  was
11945                rejected  for REASON.    If the  channel check_acs
11946                "slave_dial"  flag was  on, then  PERSON1.PROJECT1
11947                specifies the identified user on this channel.
11948 
11949      Action:   Note for system programmer action.
11950 
11951 
11952                [dialup_.pl1]
11953                dialup_:    answer   table    damaged   at   UTEP,
11954                tra_vec=TTTT
11955 
11956 
11957      Stream:   as (severity 2)
11958 
11959      Time:     While system is running.
11960 
11961 
11962 dialup_                        207            08/03/23     MR12.7^L
11963 
11964 
11965      Meaning:  The tra_vec  value was found to be  invalid for an
11966                answer table  wakeup.  Damage to the  answer table
11967                is indicated.
11968 
11969      Action:   Contact the system programming staff.
11970 
11971 
11972                [dialup_.pl1]
11973                dialup_:  called while ansp = null
11974 
11975 
11976      Stream:   as (severity 2)
11977 
11978      Time:     While system is running.
11979 
11980      Meaning:  A programming error in the Answering Service or an
11981                incorrect  library  installation  has  caused  the
11982                Answering  Service  to   be  called  before  being
11983                initialized.  The system will ignore the error and
11984                attempt to continue.
11985 
11986      Action:   Shut  down  the  system  and  perform  a  bootload
11987                operation.
11988 
11989 
11990                [dialup_.pl1]
11991                dialup_:   called with   bad ptr  EVENT_MSG_PTR by
11992                WWWWWWWWWWWW
11993 
11994 
11995      Stream:   as (severity 2)
11996 
11997      Time:     While system is running.
11998 
11999      Meaning:  A   programming   error    in   the   interprocess
12000                communication system, the network software, or the
12001                Answering Service itself has occurred.  An invalid
12002                message pointer  has been passed to  the Answering
12003                Service.   The  system  ignores  the  message  and
12004                attempts  to continue.   This message  may be  the
12005                result of an incorrect library installation.
12006 
12007      Action:   Shut  down  the  system  and  perform  a  bootload
12008                operation.
12009 
12010 
12011                [dialup_.pl1]
12012                dialup_:  called with null message ptr
12013 
12014 
12015      Stream:   as (severity 2)
12016 
12017      Time:     While system is running.
12018 
12019 
12020 dialup_                        208            08/03/23     MR12.7^L
12021 
12022 
12023      Meaning:  A   programming   error    in   the   interprocess
12024                communication system, the network software, or the
12025                Answering Service itself has occurred.  An invalid
12026                message pointer  has been passed to  the Answering
12027                Service.   The  system  ignores  the  message  and
12028                attempts  to continue.   This message  may be  the
12029                result of an incorrect library installation.
12030 
12031      Action:   Shut  down  the  system  and  perform  a  bootload
12032                operation.  Inform the system programming staff.
12033 
12034 
12035 
12036                [dialup_.pl1]
12037                dialup_:     cancelling    inactivity    bump   of
12038                PERSON.PROJECT
12039 
12040 
12041      Stream:   as (severity 1)
12042 
12043      Time:     While system is running.
12044 
12045      Meaning:  This  is  a  logging  message  indicating that the
12046                PERSON.PROJECT  process that  had been  previously
12047                bumped due  to inactivity has become  active.  The
12048                automatic  logout  was  therefore  cancelled.  The
12049                user will receive a message to this effect.
12050 
12051      Action:   No operator action is required.
12052 
12053 
12054                [dialup_.pl1]
12055                dialup_:  CDT damaged at CDTEP, tra_vec=TTTT
12056 
12057 
12058      Stream:   as (severity 2)
12059 
12060      Time:     While system is running.
12061 
12062      Meaning:  The tra_vec  value was found  to be invalid  for a
12063                channel wakeup.  Damage to the CDT is indicated.
12064 
12065      Action:   Contact the system programming staff.
12066 
12067 
12068                [dialup_.pl1]
12069                dialup_:  cdte CDTEP (CHANNEL) state  M in use N -
12070                notify system programmer",
12071 
12072 
12073      Stream:   as (severity 0)
12074 
12075      Time:     While system is running.
12076 
12077 
12078 dialup_                        209            08/03/23     MR12.7^L
12079 
12080 
12081      Meaning:  This indicates a logic error in the supervisor, or
12082                CPU or memory hardware problems.
12083 
12084      Action:   Contact the system programming staff.
12085 
12086 
12087                [dialup_.pl1]
12088                dialup_:  cdtep  = null and ate.active  = DDDD for
12089                UTEP
12090 
12091 
12092      Stream:   as (severity 2)
12093 
12094      Time:     While system is running.
12095 
12096      Meaning:  This indicates a logic error in the supervisor, or
12097                CPU or memory hardware problems.
12098 
12099      Action:   Contact the system programming staff.
12100 
12101 
12102                [dialup_.pl1]
12103                dialup_:    channel_error  called  with   cdte  in
12104                functional state.
12105 
12106 
12107      Stream:   as (severity 1)
12108 
12109      Time:     While system is running.
12110 
12111      Meaning:  This indicates a logic error in the supervisor, or
12112                CPU or memory hardware problems.
12113 
12114      Action:   Contact the system programming staff.
12115 
12116 
12117                [dialup_.pl1]
12118                dialup_:  error - event calls were masked
12119 
12120 
12121      Stream:   as (severity 1)
12122 
12123      Time:     While system is running.
12124 
12125      Meaning:  This  message  indicates  a  serious  error in the
12126                Initializer  programs.   The  system  attempts  to
12127                recover and keep running.
12128 
12129      Action:   Contact the system programming staff.
12130 
12131 
12132                [dialup_.pl1]
12133 
12134 
12135 
12136 dialup_                        210            08/03/23     MR12.7^L
12137 
12138 
12139                dialup_:   ERROR_MESSAGE Getting  pointer to  help
12140                file, SYS_DIR>ENTRY_NAME
12141 
12142 
12143      Stream:   as (severity 2)
12144 
12145      Time:     While system is running.
12146 
12147      Meaning:  An ERROR_MESSAGE was returned  when an attempt was
12148                made  to  find   the  login_help  or  connect_help
12149                segment in the SYS_DIR, usually >sc1.
12150 
12151      Action:   Contact the system programming staff.
12152 
12153 
12154                [dialup_.pl1]
12155                dialup_:  ERROR_MESSAGE  setting new tty  info for
12156                CHANNEL
12157 
12158 
12159      Stream:   as (severity 0)
12160 
12161      Time:     While system is running.
12162 
12163      Meaning:  An  ERROR_MESSAGE  was  returned   by  a  call  to
12164                cpg_$set_pit_tty_info  when  setting  new terminal
12165                attributes  in a   reconnected process  on channel
12166                CHANNEL.
12167 
12168      Action:   Contact the system programming staff.
12169 
12170 
12171                [dialup_.pl1]
12172                dialup_:  ERROR_MESSAGE Unable  to declare handler
12173                for ev chn EVENT_CHN for ate UTEP for CDT_CHANNEL
12174 
12175 
12176      Stream:   as (severity 2)
12177 
12178      Time:     While system is running.
12179 
12180      Meaning:  An ERROR_MESSAGE was returned  when an attempt was
12181                made  to declare  an  event  call channel  for new
12182                process   (UTEP)   on    EVENT_CHN   attached   to
12183                CDT_CHANNEL.
12184 
12185      Action:   Contact the system programming staff.
12186 
12187 
12188                [dialup_.pl1]
12189                dialup_:   ERROR_MESSAGE attempting to  allocate a
12190                user table entry for CHANNEL
12191 
12192 
12193 
12194 dialup_                        211            08/03/23     MR12.7^L
12195 
12196 
12197      Stream:   as (severity 1)
12198 
12199      Time:     While system is running.
12200 
12201      Meaning:  An  ERROR_MESSAGE  was  returned  from  a  call to
12202                asu_$attach_ate  which  allocates   a  user  table
12203                entry.
12204 
12205      Action:   Contact the system programming staff.
12206 
12207 
12208                [dialup_.pl1]
12209                dialup_:    ERROR_MESSAGE  creating   process  for
12210                PERSON.PROJECT
12211 
12212 
12213      Stream:   as (severity 2)
12214 
12215      Time:     While system is running.
12216 
12217      Meaning:  An ERROR_MESSAGE  was returned and the  system was
12218                unable    to   create    a   user    process   for
12219                PERSON.PROJECT.
12220 
12221      Action:   If possible, get in touch  with the user.  (He got
12222                a message  to contact you.)  Ask him  to try again
12223                and to tell you of any peculiarities of his login.
12224                Note all  particulars and contact  the programming
12225                staff.
12226 
12227 
12228 
12229                [dialup_.pl1]
12230                dialup_:  ERROR_MESSAGE From write_status order on
12231                CHANNEL
12232 
12233 
12234      Stream:   as (severity 1)
12235 
12236      Time:     While system is running.
12237 
12238      Meaning:  This is a debugging  message that will only appear
12239                if tracing has been  enabled.  An ERROR_MESSAGE by
12240                a call  to astty_$tty_order with  a "write_status"
12241                order.
12242 
12243      Action:   Contact the system programming staff.
12244 
12245 
12246                [dialup_.pl1]
12247                dialup_:   ERROR_MESSAGE get_required_access_class
12248                order failed for CHANNEL
12249 
12250 
12251 
12252 dialup_                        212            08/03/23     MR12.7^L
12253 
12254 
12255      Stream:   as (severity 1)
12256 
12257      Time:     While system is running.
12258 
12259      Meaning:  An  ERROR_MESSAGE  was  returned   by  a  call  to
12260                astty_$tty_order with  a get_required_access_class
12261                order for CHANNEL.  The channel will be hungup.
12262 
12263      Action:   Contact the system programming staff._ssa
12264 
12265 
12266                [dialup_.pl1]
12267                dialup_:    ERROR_MESSAGE   ttt   error,  removing
12268                channel CHANNEL COMMENT
12269 
12270 
12271      Stream:   as (severity 2)
12272 
12273      Time:     While system is running.
12274 
12275      Meaning:  An ERROR_MESSAGE resulting  from accessing the TTT
12276                has caused the CHANNEL with COMMENT to be unusable
12277                when attempting  to set the default  terminal type
12278                based  on  line-type/baud-rate.   The  channel has
12279                been removed from known channels.
12280 
12281      Action:   Contact the  system programming staff.   An attach
12282                of the CHANNEL can be tried.  If the channel is to
12283                be left detached, busy out the modem.
12284 
12285 
12286 
12287                [dialup_.pl1]
12288                dialup_:   ERROR_MESSAGE  tty_dim  error, removing
12289                channel CHANNEL COMMENT
12290 
12291 
12292      Stream:   as (severity 2)
12293 
12294      Time:     While system is running.
12295 
12296      Meaning:  An   ERROR_MESSAGE  caused   the  CHANNEL   to  be
12297                unusable.   The  CHANNEL   with  COMMENT  will  be
12298                removed from service.
12299 
12300      Action:   You may try to attach the channel.  If that fails,
12301                notify the system programmers.   If the channel is
12302                to be left detached, busy out the modem.
12303 
12304 
12305 
12306                [dialup_.pl1]
12307 
12308 
12309 
12310 dialup_                        213            08/03/23     MR12.7^L
12311 
12312 
12313                dialup_:  ERROR_MESSAGE when  attempting to notify
12314                user PERSON.PROJECT of dialup event
12315 
12316 
12317      Stream:   as (severity 0)
12318 
12319      Time:     While system is running.
12320 
12321      Meaning:  An ERROR_MESSAGE was returned  when an attempt was
12322                made to  send a message to  PERSON.PROJECT about a
12323                dialup event.
12324 
12325      Action:   Contact the system programming staff.
12326 
12327 
12328                [dialup_.pl1]
12329                dialup_:  ERROR_MESSAGE.  Trying to wakeup process
12330                after reconnection for PERSON.PROJECT.TAG
12331 
12332 
12333 
12334      Stream:   as (severity 0)
12335 
12336      Time:     Called  in response to  a user reconnecting  to an
12337                interactive process.
12338 
12339      Meaning:  A failure  occurred while sending a  wakeup to the
12340                process   being   connected   to   the   terminal.
12341                ERROR_MESSAGE  is  the  text  associated  with the
12342                error code returned by hcs_$wakeup.
12343 
12344      Action:   No operator action is required.
12345 
12346 
12347                [dialup_.pl1]
12348                dialup_:  fatal error  during process creation for
12349                PERSON.PROJECT CHANNEL
12350 
12351 
12352      Stream:   as (severity 1)
12353 
12354      Time:     While system is running.
12355 
12356      Meaning:  A fatal error occurred during process creation for
12357                PERSON.PROJECT  on CHANNEL.    Reason is  given in
12358                previous  log entry.   This may  be due  to a user
12359                error:   incorrect  segments  in  the  user's home
12360                directory  or bad  login arguments  can cause this
12361                problem.
12362 
12363      Action:   No operator action is required.
12364 
12365 
12366 
12367 
12368 dialup_                        214            08/03/23     MR12.7^L
12369 
12370 
12371                [dialup_.pl1]
12372                dialup_:      ignored     SSSS     for     CHANNEL
12373                st=DDDD,inuse=UUUU,tv=TTTT
12374 
12375 
12376      Stream:   as (severity 2)
12377 
12378      Time:     While system is running.
12379 
12380      Meaning:  A  spurious signal  SSSS has  arrived for CHANNEL.
12381                The state of the channel is DDD, inuse is UUUU and
12382                tra_vec is TTTT.
12383 
12384      Action:   This  may  be  some  user  trying  to  disrupt the
12385                system.  Notify the programming staff.
12386 
12387 
12388 
12389                [dialup_.pl1]
12390                dialup_:   ignored  SSSS  from  PERSON.PROJECT for
12391                CHANNEL state=DDDD,inuse=UUUU,tv=TTTT
12392 
12393 
12394      Stream:   as (severity 2)
12395 
12396      Time:     While system is running.
12397 
12398      Meaning:  A  spurious signal  SSSS from  user PERSON.PROJECT
12399                has arrived for CHANNEL.  The state of the channel
12400                is DDD, inuse is UUUU and tra_vec is TTTT.
12401 
12402      Action:   This  may  be  some  user  trying  to  disrupt the
12403                system.  Do a who and  save it for the programming
12404                staff.
12405 
12406 
12407 
12408                [dialup_.pl1]
12409                dialup_:    non-null   atep    (UTEP)   for   cdte
12410                (CDTEP,CHANNEL), tv=TRAVEC,inuse=INUSE
12411 
12412 
12413      Stream:   as (severity 0)
12414 
12415      Time:     While system is running.
12416 
12417      Meaning:  A  wakeup occurred  for CHANNEL  whose user  table
12418                entry pointer (UTEP) was  non-null.  A test on the
12419                above information determined that the state of the
12420                channel to be inconsistant.   The system will null
12421                the UTEP pointer in the CDT for the above channel.
12422 
12423      Action:   Contact the system programming staff.
12424 
12425 
12426 dialup_                        215            08/03/23     MR12.7^L
12427 
12428 
12429 
12430 
12431                [dialup_.pl1]
12432                dialup_:   premature  stopstop  for PERSON.PROJECT
12433                CHANNEL
12434 
12435 
12436      Stream:   as (severity 0)
12437 
12438      Time:     While system is running.
12439 
12440      Meaning:  This indicates a logic error in the supervisor, or
12441                CPU or memory hardware problems.
12442 
12443      Action:   Contact the system programming staff.
12444 
12445 
12446                [dialup_.pl1]
12447                dialup_:  process did not respond properly to trm_
12448                signal.  PERSON.PROJECT CHANNEL
12449 
12450 
12451      Stream:   as (severity 0)
12452 
12453      Time:     While system is running.
12454 
12455      Meaning:  The  PERSON.PROJECT process  on CHANNEL  was being
12456                terminated and  had been sent the  trm_ signal but
12457                it did not respond.   User process will be bumped,
12458                logged out or new_proced.  It is possible that the
12459                user can cause this message.
12460 
12461      Action:   No operator action is required.
12462 
12463 
12464                [dialup_.pl1]
12465                dialup_:     process     ignored    sus_    signal
12466                PERSON.PROJECT CHANNEL
12467 
12468 
12469      Stream:   as (severity 1)
12470 
12471      Time:     While system is running.
12472 
12473      Meaning:  The PERSON.PROJECT process  on CHANNEL ignored the
12474                sus_ signal  that had been  sent to it.   The user
12475                can cause this message.
12476 
12477      Action:   No operator action is required.
12478 
12479 
12480                [dialup_.pl1]
12481 
12482 
12483 
12484 dialup_                        216            08/03/23     MR12.7^L
12485 
12486 
12487                dialup_:     process     ignored    trm_    signal
12488                PERSON.PROJECT CHANNEL
12489 
12490 
12491      Stream:   as (severity 1)
12492 
12493      Time:     While system is running.
12494 
12495      Meaning:  The  PERSON.PROJECT process   on CHANNEL  had been
12496                sent a trm_ signal but the process did not respond
12497                to  it.   The  process  will  be  handled  as  was
12498                intended to be; bumped, logged out, etc.
12499 
12500      Action:   No operator action is required.
12501 
12502 
12503                [dialup_.pl1]
12504                dialup_:    process    terminated   PERSON.PROJECT
12505                CHANNEL TERM_MESSAGE
12506 
12507 
12508      Stream:   as (severity 0)
12509 
12510      Time:     While system is running.
12511 
12512      Meaning:  The  process  for  PERSON.PROJECT  on  CHANNEL was
12513                terminated    abnormally   due   to    reason   in
12514                TERM_MESSAGE.
12515 
12516      Action:   No operator action is required.
12517 
12518 
12519                [dialup_.pl1]
12520                dialup_:               program              error.
12521                cdte.current_access_class_valid    =    "0"b    at
12522                disconnected     process      manipulation     for
12523                PERSON.PROJECT channel CHANNEL.
12524 
12525 
12526      Stream:   as (severity 1)
12527 
12528      Time:     While system is running.
12529 
12530      Meaning:  When the AIM authorization  of the current process
12531                was        to        be        checked,        the
12532                cdte.current_access_class_valid flag  was found to
12533                be off.  It  should never be at this  point in the
12534                software.
12535 
12536      Action:   Contact the system programming staff._ssa
12537 
12538 
12539                [dialup_.pl1]
12540 
12541 
12542 dialup_                        217            08/03/23     MR12.7^L
12543 
12544 
12545                dialup_:    program  error:   attempt   to  create
12546                process for PERSON.PROJECT CHANNEL,
12547                with      ate     UTEP     not      filled     in;
12548                n_disc=XX,disc_com=YY,disc_ate_ix=ZZ
12549 
12550 
12551 
12552      Stream:   as (severity 1)
12553 
12554      Time:     While system is running.
12555 
12556      Meaning:  The lg_ctl_ program is  supposed to have filled in
12557                process     creation     variables     and     set
12558                ute.uflags.proc_create_ok but  apparently did not.
12559                This message in the log indicates a program error.
12560 
12561      Action:   Contact the system programming staff.
12562 
12563 
12564                [dialup_.pl1]
12565                dialup_:   program error:  disconnected  ate index
12566                no.  CUR_IDX for PERSON.PROJECT is NEXT_IDX
12567 
12568 
12569      Stream:   as (severity 1)
12570 
12571      Time:     While system is running.
12572 
12573      Meaning:  This indicates a logic error in the supervisor, or
12574                CPU or memory hardware problems.
12575 
12576      Action:   Contact the system programming staff.
12577 
12578 
12579                [dialup_.pl1]
12580                dialup_:    Program   error:    null   atep   with
12581                per-process tra_vec value
12582 
12583 
12584      Stream:   as (severity 2)
12585 
12586      Time:     While system is running.
12587 
12588      Meaning:  A  system  programming   error  in  the  answering
12589                service  has occurred  as a  wakeup occurred  when
12590                tra_vec indicated to  expect a process termination
12591                but the ate pointer was null.
12592 
12593      Action:   Contact the system programming staff.
12594 
12595 
12596                [dialup_.pl1]
12597 
12598 
12599 
12600 dialup_                        218            08/03/23     MR12.7^L
12601 
12602 
12603                dialup_:    Program   error:    null   cdtep  with
12604                per-channel tra_vec value
12605 
12606 
12607      Stream:   as (severity 2)
12608 
12609      Time:     While system is running.
12610 
12611      Meaning:  A  wakeup  was  received  when  the  tra_vec value
12612                indicated a channel operation was required but the
12613                cdtep  was  null.   This  is  considered  to  be a
12614                programming error.
12615 
12616      Action:   Contact the system programming staff.
12617 
12618 
12619                [dialup_.pl1]
12620                dialup_:  Program error:   per-process wakeup with
12621                per-channel-only tra_vec value
12622 
12623 
12624      Stream:   as (severity 2)
12625 
12626      Time:     While system is running.
12627 
12628      Meaning:  A process  wakeup occurred when the  tra_vec value
12629                indicated it should be  a channel wakeup.  This is
12630                considered a programing error.
12631 
12632      Action:   Contact the system programming staff.
12633 
12634 
12635                [dialup_.pl1]
12636                dialup_:   re-used  cdte  (CDTEP,CHANNEL)  by  ate
12637                UTEP, destroy_flag=DDDD
12638 
12639 
12640      Stream:   as (severity 0)
12641 
12642      Time:     While system is running.
12643 
12644      Meaning:  An  ate wakeup occurred  which pointed to  a CDTEP
12645                that was already in use by another process.
12646 
12647      Action:   Contact the system programming staff.
12648 
12649 
12650                [dialup_.pl1]
12651                dialup_:  SLAVE CHANNEL
12652 
12653 
12654      Stream:   as (severity 0)
12655 
12656 
12657 
12658 dialup_                        219            08/03/23     MR12.7^L
12659 
12660 
12661      Time:     While system is running.
12662 
12663      Meaning:  Logging message indicating  that the slave command
12664                has been entered in  on channel CHANNEL which does
12665                not have the "slave_dial" keyword in its check_acs
12666                statement.
12667 
12668      Action:   No operator action is required.
12669 
12670 
12671                [dialup_.pl1]
12672                dialup_:  SLAVE PERSON.PROJECT CHANNEL
12673 
12674 
12675      Stream:   as (severity 0)
12676 
12677      Time:     While system is running.
12678 
12679      Meaning:  Logging message indicating  that the slave command
12680                has been entered in  on channel CHANNEL which does
12681                have  the "slave_dial"   keyword in  its check_acs
12682                statement.
12683 
12684      Action:   No operator action is required.
12685 
12686 
12687                [dialup_.pl1]
12688                dialup_:  terminating fatal process error loop for
12689                PERSON.PROJECT CHANNEL
12690 
12691 
12692      Stream:   as (severity 1)
12693 
12694      Time:     While system is running.
12695 
12696      Meaning:  The  process  for  PERSON.PROJECT  on  CHANNEL has
12697                taken  too  many  fatal  process  errors.  This is
12698                governed    by     fatal_error_loop_seconds    and
12699                fatal_error_loop_count in  the installation_parms.
12700                The user will not get  a new process.  The channel
12701                will  not  be  hungup   but  will  get  a  message
12702                indicating  this condition.   This message  may be
12703                due to a user error.
12704 
12705      Action:   No operator action is required.
12706 
12707 
12708                [dialup_.pl1]
12709                dialup_:  The answer table is full (MAX entries).
12710 
12711 
12712      Stream:   as (severity 1)
12713 
12714 
12715 
12716 dialup_                        220            08/03/23     MR12.7^L
12717 
12718 
12719      Time:     While system is running.
12720 
12721      Meaning:  The  system  answer  table  is  full  and  has MAX
12722                entries.  No more users will be able to login.
12723 
12724      Action:   Contact the system programming staff.
12725 
12726 
12727                [dialup_.pl1]
12728                dialup_:     trace    event    CHANNEL    FFFFFFFF
12729                WWWWWWWWWWWW RRRRRRDDDDDD SS XXXX st N wp M
12730 
12731 
12732      Stream:   as (severity 1)
12733 
12734      Time:     While system is running.
12735 
12736      Meaning:  This  is trace  output.  When  dialup_$trace_on is
12737                called, these  messages are printed out  for every
12738                signal concerning  a device channel.   FFFFFFFF is
12739                the function being performed.  WWWWWWWWWWWW is the
12740                sending process ID.  RRRRRR  is the ring origin of
12741                the   signal.   DDDDDD    is  the   device  signal
12742                information.   The  pointer  SS  XXXX  locates the
12743                answer table entry for CHANNEL.  The channel state
12744                is N and the wait point (transaction vector) is M.
12745 
12746      Action:   No  operator action  is required.   To turn  these
12747                messages  off,  type  dialup_$trace_off  while  in
12748                admin mode.
12749 
12750 
12751 
12752                [dialup_.pl1]
12753                dialup_:  tracing turned off.
12754 
12755 
12756      Stream:   as (severity 1)
12757 
12758      Time:     While system is running.
12759 
12760      Meaning:  The dialup_ tracing function has been turned off.
12761 
12762      Action:   No operator action is required.
12763 
12764 
12765                [dialup_.pl1]
12766                dialup_:  tracing turned on for channel CHANNEL.
12767 
12768 
12769      Stream:   as (severity 1)
12770 
12771      Time:     While system is running.
12772 
12773 
12774 dialup_                        221            08/03/23     MR12.7^L
12775 
12776 
12777      Meaning:  The dialup_$trace_on  entry point was  called with
12778                an  argument, the begining  part of a  CDT channel
12779                name; to trace all channels  on FNP a, then supply
12780                "a"; to  trace all channels on second  hsla of FNP
12781                B, supply "b.h1".
12782 
12783      Action:   No operator action is  required.  If tracing is to
12784                be  turned off,   type dialup_$trace_off  in admin
12785                mode.
12786 
12787 
12788 
12789                [dialup_.pl1]
12790                dialup_:  tracing turned on.
12791 
12792 
12793      Stream:   as (severity 1)
12794 
12795      Time:     While system is running.
12796 
12797      Meaning:  The   dialup_$trace_on  entry  point   was  called
12798                without arguments.  All channels will be traced.
12799 
12800      Action:   No operator action is  required.  If tracing is to
12801                be  turned off,   type dialup_$trace_off  in admin
12802                mode.
12803 
12804 
12805 
12806                [dialup_.pl1]
12807                dialup_:   turning off  disconnected flag  for ate
12808                UTEP, cdte CDTEP,CHANNEL
12809 
12810 
12811      Stream:   as (severity 0)
12812 
12813      Time:     While system is running.
12814 
12815      Meaning:  If processing an ate  wakeup, the CHANNEL is known
12816                and the process  is disconnected, the disconnected
12817                flag for the ate will be turned off.
12818 
12819      Action:   Contact the system programming staff.
12820 
12821 
12822                [dialup_.pl1]
12823                dialup_:   turning on   disconnected flag  for ate
12824                UTEP
12825 
12826 
12827      Stream:   as (severity 0)
12828 
12829      Time:     While system is running.
12830 
12831 
12832 dialup_                        222            08/03/23     MR12.7^L
12833 
12834 
12835      Meaning:  If  after   detecting  a  re-used  cdte   and  the
12836                disconnected flag is not on, the disconnected flag
12837                will be turned on and noted by this message.
12838 
12839      Action:   Contact the system programming staff.
12840 
12841 
12842                [dialup_.pl1]
12843                dialup_:   Unable  to  determine  initial terminal
12844                type for channel CHAN
12845 
12846 
12847      Stream:   as (severity 2)
12848 
12849      Time:     While system is running.
12850 
12851      Meaning:  cdte.initial_terminal_type is  not set, indicating
12852                CDT  damage.   Channel  CHAN  is  removed from the
12853                system.
12854 
12855      Action:   Contact the system programming staff.
12856 
12857 
12858                [dialup_.pl1]
12859                dialup_:   Unexpected termsgnl  for PERSON.PROJECT
12860                CHANNEL (preempted=DDDD).
12861 
12862 
12863      Stream:   as (severity 0)
12864 
12865      Time:     While system is running.
12866 
12867      Meaning:  A   "termsgnl"  wakeup    was  received   for  the
12868                PERSON.PROJECT    process    on    CHANNEL   whose
12869                ute.preempted value DDDD did  not indicate one was
12870                allowed.   This  is  considered  to  be  a program
12871                error.  User will be given a new process.
12872 
12873      Action:   Contact the system programming staff.
12874 
12875 
12876                [dialup_.pl1]
12877                dialup_:   wrong answerback on  CHANNEL (COMMENT);
12878                expected "ID1", got "ID2".
12879 
12880 
12881      Stream:   as (severity 2)
12882 
12883      Time:     While system is running.
12884 
12885      Meaning:  A terminal attempted to  connect on CHANNEL (whose
12886                CDT  comment is COMMENT)  that is restricted  to a
12887                specific  answerback   and  did  not   return  the
12888 
12889 
12890 dialup_                        223            08/03/23     MR12.7^L
12891 
12892 
12893                expected value.   ID1 is the  answerback expected;
12894                ID2  is  the  answerback  actually  received.  The
12895                terminal is hung up.
12896 
12897      Action:   No operator action is required.
12898 
12899 
12900                [dir_lock_init.pl1]
12901                dir_lock_init:  cannot get ASTE for dir_lock_seg.
12902 
12903 
12904      Stream:   BOS Typewriter (Crashes system)
12905 
12906      Time:     System Intialization.
12907 
12908      Meaning:  No space could be obtained for dir_lock_seg.  This
12909                can result from inadequate  ASTE pools or hardcore
12910                partition.
12911 
12912      Action:   Follow normal recovery procedures.  $boot_tape
12913 
12914 
12915 
12916                [disk_control.pl1]
12917                disk_control:  Adding channel ICC.
12918 
12919 
12920      Stream:   BOS Typewriter.
12921 
12922      Time:     While system is running.
12923 
12924      Meaning:  A  message to  confirm that  channel ICC  has been
12925                added to  the system in response  to a reconfigure
12926                command.
12927 
12928      Action:   No operator action is required.
12929 
12930 
12931                [disk_control.pl1]
12932                disk_control:  dskX_NN now operational.
12933 
12934 
12935      Stream:   BOS Typewriter.
12936 
12937      Time:     While system is running.
12938 
12939      Meaning:  A  disk  drive  which  required  intervention  has
12940                successfully  completed  an  I/O  operation.   The
12941                system will again use its contents.
12942 
12943      Action:   No operator action is required.
12944 
12945 
12946 
12947 
12948 disk_control                   224            08/03/23     MR12.7^L
12949 
12950 
12951 
12952 
12953                [disk_control.pl1]
12954                disk_control:  dskX_NN requires intervention.
12955 
12956 
12957      Stream:   BOS Typewriter (sounds beeper)
12958 
12959      Time:     While system is running.
12960 
12961      Meaning:  A  disk error has  occurred which could  have been
12962                caused  by  the  pack  or  drive  being  broken or
12963                requiring  operator  attention.   The  system  has
12964                retried  the operation   an appropriate  number of
12965                times  without success.   The system  will try the
12966                device  periodically  to  check  if  it  has  been
12967                repaired.
12968 
12969      Action:   Inspect the device.  If it is not ready, ready it.
12970                If it is ready, try unreadying and re-readying it.
12971                If  the  drive  cannot   be  made  ready,  contact
12972                Customer Service personnel.
12973 
12974 
12975 
12976                [disk_control.pl1]
12977                disk_control:   MAJOR_STAT   SUBSTAT  for  dskX_NN
12978                (channel ICC).
12979                rec RRRR, sect SSSS, main AAAA
12980                detailed status:  XX XX XX XX XX XX XX XX
12981 
12982 
12983 
12984      Stream:   BOS Typewriter.
12985 
12986      Time:     While system is running.
12987 
12988      Meaning:  A disk  error has occurred on  drive dskX_NN.  The
12989                major  status  and  substatus  are  interpreted as
12990                character strings.  The disk address is given both
12991                as a  Multics record address  in octal, and  as an
12992                absolute sector  number in octal.  The  main store
12993                address being used was AAAA octal.  The third line
12994                gives the hexadecimal value of the detailed status
12995                in  cases where this  data is useful.   See manual
12996                AN87, System  Formats, for interpretation  of this
12997                information.
12998 
12999      Action:   Note  for Customer   Service action.   The segment
13000                involved in  a disk error can  often be identified
13001                by an application of the "record_to_vtocx" tool to
13002                the Multics record number given in the message.
13003 
13004 
13005 
13006 disk_control                   225            08/03/23     MR12.7^L
13007 
13008 
13009 
13010 
13011                [disk_control.pl1]
13012                disk_control:   MAJOR_STAT   SUBSTAT  for  dskX_NN
13013                (channel ICC).
13014                rec RRRR, sect SSSS, main AAAA
13015                subvol V, logical rec OOOO, logical sect TTTT
13016                detailed status:  XX XX XX XX XX XX XX XX
13017 
13018 
13019 
13020      Stream:   BOS Typewriter.
13021 
13022      Time:     While system is running.
13023 
13024      Meaning:  A disk  error has occurred on  drive dskX_NN.  The
13025                major  status  and  substatus  are  interpreted as
13026                character strings.  The disk address is given both
13027                as a  Multics record address  in octal, and  as an
13028                absolute sector  number in octal.  The  main store
13029                address being used was  AAAA octal.  The subvolume
13030                name is  V (the logical device  name is dskX_NNV),
13031                the logical  record address is OOOO  octal and the
13032                logical sector  number is TTTT octal.   The fourth
13033                line gives  the hexadecimal value of  the detailed
13034                status  in cases where  this data is  useful.  See
13035                manual AN87, System Formats, for interpretation of
13036                this information.
13037 
13038      Action:   Note  for Customer   Service action.   The segment
13039                involved in  a disk error can  often be identified
13040                by an application of the "record_to_vtocx" tool to
13041                the  Multics logical  record number  given in  the
13042                message.
13043 
13044 
13045 
13046                [disk_control.pl1]
13047                disk_control:  Placing dskX_NN in operation.
13048 
13049 
13050      Stream:   BOS Typewriter.
13051 
13052      Time:     While system is running.
13053 
13054      Meaning:  A special  interrupt has been received  for a disk
13055                drive marked  as broken.  The system  will attempt
13056                to use the device.
13057 
13058      Action:   No operator action is required.
13059 
13060 
13061 
13062 
13063 
13064 disk_control                   226            08/03/23     MR12.7^L
13065 
13066 
13067 
13068 
13069                [disk_control.pl1]
13070                disk_control:  Queuing error.
13071 
13072 
13073      Stream:   BOS Typewriter (Crashes system)
13074 
13075      Time:     While system is running.
13076 
13077      Meaning:  This indicates a logic error in the supervisor, or
13078                CPU or memory hardware problems.
13079 
13080      Action:   Follow normal recovery procedures.
13081 
13082 
13083                [disk_control.pl1]
13084                disk_control:  Reconnected IO_TYPE  I/O on dskX_NN
13085                (channel ICC).
13086 
13087 
13088      Stream:   BOS Typewriter.  and/or $log
13089 
13090      Time:     While system is running.
13091 
13092      Meaning:  A disk interrupt was  apparently lost.  Status for
13093                the disk did not  arrive within the expected time.
13094                This  may  be  an   indication  of  a  channel  or
13095                controller  malfunction.  The system  restarts the
13096                disk operation.
13097 
13098      Action:   No  operator  action  is  required.   Unless these
13099                messages  persist, which  may indicate  a hardware
13100                malfunction that needs  investigation.  Some types
13101                of channel adapters and/or disk controllers can be
13102                "reset" in an attempt to correct the condition.
13103 
13104 
13105 
13106                [disk_control.pl1]
13107                disk_control:  Removing channel ICC.
13108 
13109 
13110      Stream:   BOS Typewriter (sounds beeper)
13111 
13112      Time:     While system is running.
13113 
13114      Meaning:  Errors  occurred indicative   of a  defective disk
13115                channel or MPC.  The  channel receiving the errors
13116                is placed offline.
13117 
13118      Action:   Contact the system programming staff.  Also inform
13119                Customer Service personnel.
13120 
13121 
13122 disk_control                   227            08/03/23     MR12.7^L
13123 
13124 
13125 
13126 
13127                [disk_control.pl1]
13128                disk_control:   Unexpected  IOM  status  SSSS  for
13129                dskX_NN (channel ICC).
13130 
13131 
13132      Stream:   BOS Typewriter.
13133 
13134      Time:     While system is running.
13135 
13136      Meaning:  Status has been received  from a channel which was
13137                not  marked  active.   This   is  due  to  a  disk
13138                subsystem or  IOM problem, or to a  logic error in
13139                the supervisor.  See  manual AN87, System Formats,
13140                for  an interpretation  of the  status SSSS.   The
13141                system ignores the status and attempts to continue
13142                operation.
13143 
13144      Action:   No operator action is required.
13145 
13146 
13147                [disk_emergency.pl1]
13148                disk_emergency:  DSKX_NN  inoperative; shutdown of
13149                DSKX_NN suspended
13150 
13151 
13152      Stream:   BOS Typewriter (sounds beeper)
13153 
13154      Time:     Emergency shutdown.
13155 
13156      Meaning:  During  emergency  shutdown,   DSKX_NN  was  found
13157                inoperative.  Data in main memory or on the paging
13158                device  which need  to be  flushed to  the pack on
13159                DSKX_NN  cannot be  written out.   The data remain
13160                where they were and ESD may be tried again.
13161 
13162      Action:   If the drive can be  made ready, make it ready and
13163                try  ESD again.  Do  NOT move packs  before trying
13164                ESD, unless address plugs  are changed so that the
13165                same pack  appears to have the  same address.  (If
13166                this action  is performed, the MPC  must be halted
13167                and  restarted with a  reset and branch.)   If the
13168                pack  is not  successfully shut  down, the  system
13169                will volume salvage it when it is next brought up,
13170                and  data from  main memory  which belongs  on the
13171                pack will be lost.
13172 
13173 
13174 
13175                [disk_init.pl1]
13176                disk_init:   Devices D1 and  D2 of DSKn  must have
13177                the same model number.
13178 
13179 
13180 disk_init                      228            08/03/23     MR12.7^L
13181 
13182 
13183      Stream:   BOS Typewriter (Crashes system)
13184 
13185      Time:     System Intialization.
13186 
13187      Meaning:  Two devices that share  a common spindle have been
13188                configured with different model numbers.
13189 
13190      Action:   Correct the config deck and reboot.
13191 
13192 
13193                [disk_init.pl1]
13194                disk_init:    Disk  model    XXXX  not   found  in
13195                config_data_.
13196 
13197 
13198      Stream:   BOS Typewriter (Crashes system)
13199 
13200      Time:     System Intialization.
13201 
13202      Meaning:  This indicates a logic error in the supervisor, or
13203                CPU or memory hardware problems.
13204 
13205      Action:   Follow   normal  recovery  procedures.    Fix  the
13206                configuration deck and reboot.
13207 
13208 
13209 
13210                [disk_init.pl1]
13211                disk_init:  DSKn D1 must  be configured if DSKn D2
13212                is configured.
13213 
13214 
13215      Stream:   BOS Typewriter (Crashes system)
13216 
13217      Time:     System Intialization.
13218 
13219      Meaning:  Only one of a pair  of devices that share a common
13220                spindle has been configured.
13221 
13222      Action:   Change  the  config  deck  to  include the missing
13223                device and reboot.
13224 
13225 
13226                [disk_init.pl1]
13227                disk_init:  error WWWW from absadr for DSKX iom N,
13228                ch ZZ.
13229 
13230 
13231      Stream:   BOS Typewriter (Crashes system)
13232 
13233      Time:     System Intialization.
13234 
13235 
13236 
13237 
13238 disk_init                      229            08/03/23     MR12.7^L
13239 
13240 
13241      Meaning:  This indicates a logic error in the supervisor, or
13242                CPU or memory hardware problems.
13243 
13244      Action:   Follow normal recovery procedures.  $boot_tape
13245 
13246 
13247 
13248                [disk_init.pl1]
13249                disk_init:  Invalid channel on CHNL DSKx card.
13250 
13251 
13252      Stream:   BOS Typewriter (Crashes system)
13253 
13254      Time:     System Intialization.
13255 
13256      Meaning:  An invalid channel specification  was found on the
13257                CHNL card for DSKx.
13258 
13259 
13260                [disk_init.pl1]
13261                disk_init:  Invalid channel on PRPH DSKx card.
13262 
13263 
13264 
13265      Stream:   BOS Typewriter (Crashes system)
13266 
13267      Time:     System Intialization.
13268 
13269      Meaning:  An invalid channel specification  was found on the
13270                PRPH DSKx card.
13271 
13272 
13273                [disk_init.pl1]
13274                disk_init:  Invalid format for XXXX card.
13275 
13276 
13277      Stream:   BOS Typewriter (Crashes system)
13278 
13279      Time:     System Intialization.
13280 
13281      Meaning:  A required field on the XXXX card is not present.
13282 
13283      Action:   Follow   normal  recovery  procedures.    Fix  the
13284                configuration deck and reboot.
13285 
13286 
13287 
13288                [disk_init.pl1]
13289                disk_init:   No valid  disk models  found on  PRPH
13290                DSKx card.
13291 
13292 
13293      Stream:   BOS Typewriter (Crashes system)
13294 
13295 
13296 disk_init                      230            08/03/23     MR12.7^L
13297 
13298 
13299      Time:     System Intialization.
13300 
13301      Meaning:  All disk model fields were found to be zero.
13302 
13303      Action:   Fix the configuration deck and reboot.
13304 
13305 
13306                [disk_init.pl1]
13307                disk_init:  Too many channels configured for DSKn.
13308                Limit is N.
13309 
13310 
13311      Stream:   BOS Typewriter (Crashes system)
13312 
13313      Time:     System Intialization.
13314 
13315      Meaning:  The  per  subsystem  software  limit  for  logical
13316                channels has been exceeded.
13317 
13318      Action:   Fix the config deck  and reboot.  If more channels
13319                are  needed,  split  the  configuration  into more
13320                subsystems in the config deck.
13321 
13322 
13323 
13324                [disk_init.pl1]
13325                disk_init:  Too many  devices configured for DSKn.
13326                Max device is N.
13327 
13328 
13329      Stream:   BOS Typewriter (Crashes system)
13330 
13331      Time:     System Intialization.
13332 
13333      Meaning:  The software  limit for devices per  subsystem has
13334                been exceeded.
13335 
13336      Action:   Fix the config deck and reboot.
13337 
13338 
13339                [disk_init.pl1]
13340                disk_init:  Unable to assign CCCC for DSKx.
13341 
13342 
13343      Stream:   BOS Typewriter (Crashes system)
13344 
13345      Time:     System Intialization.
13346 
13347      Meaning:  An  error has  occurred  trying  to assign  an IOM
13348                channel for the disk subsystem DSKX.
13349 
13350 
13351 
13352 
13353 
13354 disk_init                      231            08/03/23     MR12.7^L
13355 
13356 
13357      Action:   Follow  normal  recovery  procedures.   Check  the
13358                configuration  deck  and  the  operability  of the
13359                hardware before rebooting.
13360 
13361 
13362 
13363                [disk_init.pl1]
13364                disk_init:   Unknown  model  number  NNNN  on PRPH
13365                dskN.
13366 
13367 
13368      Stream:   BOS Typewriter (Crashes system)
13369 
13370      Time:     System Intialization.
13371 
13372      Meaning:  The model  number NNNN on  the prph card  for disk
13373                subsystem N is invalid.
13374 
13375      Action:   Correct the config deck and reboot.
13376 
13377 
13378                [disk_reader.pl1]
13379                disk_reader:   Attempt  to  read  past  end of mst
13380                area.
13381 
13382 
13383      Stream:   BOS Typewriter (Crashes system)
13384 
13385      Time:     System Intialization.
13386 
13387      Meaning:  An attempt was made to read more data from the mst
13388                area of  disk than was placed there  from the MST.
13389                This is most likely the result of an MST misformed
13390                originally.
13391 
13392      Action:   Follow normal recovery procedures.  $boot_tape
13393 
13394 
13395 
13396                [disk_rebuild.pl1]
13397                disk_rebuild:  Disk rebuild  finished with errors:
13398                ERRORMESS
13399 
13400 
13401      Stream:   $salvout
13402 
13403      Time:     $dskr
13404 
13405      Meaning:  The  disk  rebuild  has  been  aborted  due to the
13406                indicated ERRORMESS.
13407 
13408      Action:   Contact the system programming staff.
13409 
13410 
13411 
13412 disk_rebuild                   232            08/03/23     MR12.7^L
13413 
13414 
13415 
13416 
13417                [disk_rebuild.pl1]
13418                disk_rebuild:  base of  paging region changed from
13419                XXX.  to YYY.
13420 
13421 
13422      Stream:   $salvout
13423 
13424      Time:     $dskr
13425 
13426      Meaning:  The base of the paging  region for the new pack is
13427                different from that for the old one.
13428 
13429      Action:   No operator action is required.
13430 
13431 
13432                [disk_rebuild.pl1]
13433                disk_rebuild:   Begin disk  rebuild of  DSKX_NN{s}
13434                onto DSKY_MM{s}
13435 
13436 
13437      Stream:   $salvout
13438 
13439      Time:     $dskr
13440 
13441      Meaning:  This  message  is  printed  when  disk  rebuilding
13442                begins.
13443 
13444      Action:   No operator action is required.
13445 
13446 
13447                [disk_rebuild.pl1]
13448                disk_rebuild:  Cannot compress  VTOC on dskX_NN{s}
13449                because active VTOCEs in the truncated region.
13450 
13451 
13452 
13453      Stream:   $salvout
13454 
13455      Time:     $dskr
13456 
13457      Meaning:  A  rebuild was  requested in  which the  number of
13458                VTOCEs  on the  new  volume  was smaller  than the
13459                number  of  VTOCEs  on  the  old  volume.  This is
13460                permitted  only if there  are no active  VTOCEs in
13461                the truncated region (that is, no active VTOCEs on
13462                the old  volume have VTOCE indices  which would be
13463                too high for the new volume).
13464 
13465      Action:   Run  sweep_pv  -from  num_vtoces  to  remove these
13466                VTOCEs from the old  volume and retry the rebuild.
13467 
13468 
13469 
13470 disk_rebuild                   233            08/03/23     MR12.7^L
13471 
13472 
13473                It  may  be  necessary  to  salvage  the volume to
13474                recover lost VTOCEs in the truncated region.
13475 
13476 
13477 
13478                [disk_rebuild.pl1]
13479                disk_rebuild:  copying XXX.  rec of part NAME
13480 
13481 
13482      Stream:   $salvout
13483 
13484      Time:     $dskr
13485 
13486      Meaning:  A  disk  rebuild  is  reformatting  a  pack  which
13487                contains  non-paging partitions.  The  contents of
13488                these partitions are copied exactly.
13489 
13490      Action:   No operator action is required.
13491 
13492 
13493                [disk_rebuild.pl1]
13494                disk_rebuild:  Disk rebuild finished.
13495 
13496 
13497      Stream:   $salvout
13498 
13499      Time:     $dskr
13500 
13501      Meaning:  The disk rebuild has completed.
13502 
13503      Action:   No operator action is required.
13504 
13505 
13506                [disk_rebuild.pl1]
13507                disk_rebuild:   dskX_NN{s}  must  be  mounted  for
13508                rebuild.
13509 
13510 
13511      Stream:   $salvout
13512 
13513      Time:     $dskr
13514 
13515      Meaning:  The "from" volume must be mounted for the rebuild.
13516 
13517      Action:   Mount  the  logical  volume  to  which  the "from"
13518                volume belongs and try the rebuild abain.
13519 
13520 
13521 
13522                [disk_rebuild.pl1]
13523                disk_rebuild:  dskX_NN{s} must  not be mounted for
13524                rebuild.
13525 
13526 
13527 
13528 disk_rebuild                   234            08/03/23     MR12.7^L
13529 
13530 
13531      Stream:   $salvout
13532 
13533      Time:     $dskr
13534 
13535      Meaning:  The "to" volume must not be mounted to the Storage
13536                System for a rebuild.
13537 
13538      Action:   Demount  the logical  volume to  which the  volume
13539                belongs and retry the rebuild.
13540 
13541 
13542 
13543                [disk_rebuild.pl1]
13544                disk_rebuild:   End  of  rebuilding.   New summary
13545                report follows:
13546 
13547 
13548      Stream:   $salvout
13549 
13550      Time:     $dskr
13551 
13552      Meaning:  Rebuilding has completed.  A summary report of the
13553                new volume parameter is printed.
13554 
13555      Action:   No operator action is required.
13556 
13557 
13558                [disk_rebuild.pl1]
13559                disk_rebuild:   Error  from  read_disk,  aborting:
13560                ERRORMESS
13561 
13562 
13563      Stream:   $salvout
13564 
13565      Time:     $dskr
13566 
13567      Meaning:  This indicates a logic error in the supervisor, or
13568                CPU or memory hardware problems.  The disk rebuild
13569                is aborted.
13570 
13571      Action:   Contact the system programming staff.
13572 
13573 
13574                [disk_rebuild.pl1]
13575                disk_rebuild:   Error  from  write_disk, aborting:
13576                ERRORMESS
13577 
13578 
13579      Stream:   $salvout
13580 
13581      Time:     $dskr
13582 
13583 
13584 
13585 
13586 disk_rebuild                   235            08/03/23     MR12.7^L
13587 
13588 
13589      Meaning:  This indicates a logic error in the supervisor, or
13590                CPU or memory hardware problems.  The disk rebuild
13591                is aborted.
13592 
13593      Action:   Contact the system programming staff.
13594 
13595 
13596                [disk_rebuild.pl1]
13597                disk_rebuild:  Error writing label:  ERRORMESS
13598 
13599 
13600      Stream:   $salvout
13601 
13602      Time:     $dskr
13603 
13604      Meaning:  A  disk error has  occurred writing the  new label
13605                during  a  disk  rebuild.   The  disk  rebuild  is
13606                aborted.
13607 
13608      Action:   Correct the problem and issue a new command.
13609 
13610 
13611                [disk_rebuild.pl1]
13612                disk_rebuild:  freeing deciduous vtocx XXXo:  NAME
13613 
13614 
13615      Stream:   $salvout
13616 
13617      Time:     $dskr
13618 
13619      Meaning:  The  segment originally  named NAME  at vtoc index
13620                XXXo was deciduous, and  has been deleted from the
13621                RPV.  This is debugging  output printed for system
13622                programmers if a SALV DEBG card is supplied.
13623 
13624      Action:   No operator action is required.
13625 
13626 
13627                [disk_rebuild.pl1]
13628                disk_rebuild:  freeing process vtocx XXXo:  NAME
13629 
13630 
13631      Stream:   $salvout
13632 
13633      Time:     $dskr
13634 
13635      Meaning:  The  segment originally  named NAME  at vtoc index
13636                XXXo was  per-process and has been  deleted.  This
13637                is debugging output printed for system programmers
13638                if a SALV DEBG card is used.
13639 
13640      Action:   No operator action is required.
13641 
13642 
13643 
13644 disk_rebuild                   236            08/03/23     MR12.7^L
13645 
13646 
13647 
13648 
13649                [disk_rebuild.pl1]
13650                disk_rebuild:   INIT_TABLES:  aste  pool WWWo  too
13651                small
13652 
13653 
13654      Stream:   BOS Typewriter.
13655 
13656      Time:     While system is running.
13657 
13658      Meaning:  The physical volume salvager  was unable to obtain
13659                the necessary  temporary AST entries for  its work
13660                segments.  No salvaging was done.
13661 
13662      Action:   Shut  down,  manually  correct  the  SST card, and
13663                reboot.   Then  salvage  all  volumes,  since  the
13664                indicator  that volumes   need salvaging  may have
13665                been lost.
13666 
13667 
13668 
13669                [disk_rebuild.pl1]
13670                disk_rebuild:  Map of assigned addresses changed
13671 
13672 
13673      Stream:   $salvout
13674 
13675      Time:     $dskr
13676 
13677      Meaning:  If  any corrections  were made  to the  map on the
13678                volume  which shows  which addresses  are free and
13679                which are in use, this message is printed.  If the
13680                volume was not properly shut down, this message is
13681                to be expected.
13682 
13683      Action:   No operator action is required.
13684 
13685 
13686                [disk_rebuild.pl1]
13687                disk_rebuild:   NN vtoces  added to  list of  free
13688                vtoces.
13689 
13690 
13691      Stream:   $salvout
13692 
13693      Time:     $dskr
13694 
13695      Meaning:  NN  free VTOC  entries were  found while salvaging
13696                and added to the list  of free VTOC entries.  This
13697                is a normal message.
13698 
13699      Action:   No operator action is required.
13700 
13701 
13702 disk_rebuild                   237            08/03/23     MR12.7^L
13703 
13704 
13705 
13706 
13707                [disk_rebuild.pl1]
13708                disk_rebuild:  no.  of free recs changed from OLD.
13709                to NEW.
13710 
13711 
13712      Stream:   $salvout
13713 
13714      Time:     $dskr
13715 
13716      Meaning:  If The number of free  records in the volume label
13717                is  changed by a  volume salvage, this  message is
13718                printed.   If  the  volume  was  not properly shut
13719                down, this message is to be expected.
13720 
13721      Action:   No operator action is required.
13722 
13723 
13724                [disk_rebuild.pl1]
13725                disk_rebuild:   no.  of  free vtoces  changed from
13726                OLD.  to NEW.
13727 
13728 
13729      Stream:   $salvout
13730 
13731      Time:     $dskr
13732 
13733      Meaning:  If the  number of free VTOC entries  in the volume
13734                label is changed by a volume salvage, this message
13735                is printed.
13736 
13737      Action:   No operator action is required.
13738 
13739 
13740                [disk_rebuild.pl1]
13741                disk_rebuild:  not enough free records (only XXX.)
13742                for increase (need YYY.)
13743 
13744 
13745      Stream:   $salvout
13746 
13747      Time:     $dskr
13748 
13749      Meaning:  An attempt  was made to increase the  size of some
13750                partitions  or  of  the  VTOC.   This  required  a
13751                decrease  in the size  of the paging  region.  The
13752                paging  region  is  too   full  to  be  shrunk  as
13753                required.  The disk rebuild is aborted.
13754 
13755      Action:   Issue a  different disk_rebuild command,  or bring
13756                up Multics and delete  some segments from the pack
13757                before trying again.
13758 
13759 
13760 disk_rebuild                   238            08/03/23     MR12.7^L
13761 
13762 
13763 
13764 
13765                [disk_rebuild.pl1]
13766                disk_rebuild:   out of  room on  vtocx XXXo,  page
13767                YYYo
13768 
13769 
13770      Stream:   $salvout
13771 
13772      Time:     $dskr
13773 
13774      Meaning:  This indicates a logic error in the supervisor, or
13775                CPU or memory hardware problems.  The disk rebuild
13776                is aborted.
13777 
13778      Action:   Contact the system programming staff.
13779 
13780 
13781                [disk_rebuild.pl1]
13782                disk_rebuild:  processing VTOCE #XXX.
13783 
13784 
13785      Stream:   BOS Typewriter.
13786 
13787      Time:     $dskr
13788 
13789      Meaning:  This  message  indicates  that  a  disk rebuild is
13790                progressing normally.   It is printed  every 1000.
13791                VTOC entries.
13792 
13793      Action:   No operator action is required.
13794 
13795 
13796                [disk_rebuild.pl1]
13797                disk_rebuild:   Read error  accessing VTOC  Map of
13798                dskX_NN{s}
13799 
13800 
13801      Stream:   $salvout
13802 
13803      Time:     $dskr
13804 
13805      Meaning:  This indicates a logic error in the supervisor, or
13806                CPU or  memory hardware problems.  The  rebuild is
13807                aborted.
13808 
13809      Action:   Contact the system programming staff.
13810 
13811 
13812                [disk_rebuild.pl1]
13813                disk_rebuild:  reading vtocx XXXo:  ERRORMESS
13814 
13815 
13816 
13817 
13818 disk_rebuild                   239            08/03/23     MR12.7^L
13819 
13820 
13821      Stream:   $salvout
13822 
13823      Time:     $dskr
13824 
13825      Meaning:  This indicates a logic error in the supervisor, or
13826                CPU or memory hardware problems.
13827 
13828      Action:   Contact the system programming staff.
13829 
13830 
13831                [disk_rebuild.pl1]
13832                disk_rebuild:   salv cleanup debugging  stop, dump
13833                and type go
13834 
13835 
13836      Stream:   BOS Typewriter (Crashes system)
13837 
13838      Time:     During disk rebuild
13839 
13840      Meaning:  A disk rebuild has aborted  due to a crawlout, and
13841                the debug switch is  set.  This message causes the
13842                system  to return  to BCE  so that  a dump  can be
13843                taken.
13844 
13845      Action:   Follow programmer instructions.
13846 
13847 
13848                [disk_rebuild.pl1]
13849                disk_rebuild:  same drive specified for source and
13850                copy, aborting
13851 
13852 
13853      Stream:   $salvout
13854 
13855      Time:     During disk rebuilding
13856 
13857      Meaning:  The operator  attempted to specify the  same drive
13858                as input and output.  No action was taken.
13859 
13860      Action:   Enter a corrected command.
13861 
13862 
13863                [disk_rebuild.pl1]
13864                disk_rebuild:   Summary of original  disk contents
13865                follows:
13866 
13867 
13868      Stream:   $salvout
13869 
13870      Time:     $dskr
13871 
13872      Meaning:  A summary  report of the volume  parameters before
13873                rebuilding is printed.
13874 
13875 
13876 disk_rebuild                   240            08/03/23     MR12.7^L
13877 
13878 
13879      Action:   No operator action is required.
13880 
13881 
13882                [disk_rebuild.pl1]
13883                disk_rebuild:  Summary Report
13884                Volume PVNAME of logical volume LVNAME.
13885 
13886                Paging region begins at record DD.  (WWo), for LL.
13887                (XXo) records.
13888                DD.  (WWo) free records therein.
13889                Label/VTOC size is RR.  records, MM.  VTOCEs.
13890                VTOC version X., TTT.  free VTOCEs.
13891 
13892                Partition Map
13893                Name Start Length
13894 
13895                NAME DDD.  ( WWWo) DDD.  ( WWWo)
13896                ______ _______
13897                DDD.  ( WWWo)
13898 
13899                Volume size is DDDD.  (YYYYo) records total.
13900 
13901                DD.  damaged segments.
13902 
13903 
13904 
13905      Stream:   $salvout
13906 
13907      Time:     During disk rebuilding.
13908 
13909      Meaning:  This  is  a  report  summarizing  physical  volume
13910                parameters  printed  by  the  disk  rebuilder both
13911                before and after rebuilding.  The partition map is
13912                omitted  if  no  partitions  are  defined  on  the
13913                volume.
13914 
13915      Action:   No operator action is required.
13916 
13917 
13918                [disk_rebuild.pl1]
13919                disk_rebuild:  vtocx XXXo  NAME branch unconnected
13920                due to YYYo
13921 
13922 
13923      Stream:   $salvout
13924 
13925      Time:     $dskr
13926 
13927      Meaning:  This  is  debugging  output  produced  only if the
13928                debug  switch is  on  during  a disk  rebuild with
13929                branch   checking.    It    informs   the   system
13930                programmers of the reasons for connection failure.
13931 
13932 
13933 
13934 disk_rebuild                   241            08/03/23     MR12.7^L
13935 
13936 
13937      Action:   No operator action is required.
13938 
13939 
13940                [disk_table_.pl1]
13941                disk_table_:  "KEY" is not "io", "storage_system",
13942                or "ss".
13943 
13944 
13945      Stream:   Initializer process output.
13946 
13947      Time:     While system is running.
13948 
13949      Meaning:  The operator  issued an set_drive_usage  DRIVE KEY
13950                command.  KEY is invalid.
13951 
13952      Action:   Enter a corrected command line.
13953 
13954 
13955                [mdx.pl1]
13956                disk_table_:  accepted PV PVNAME on DSKX_NN
13957 
13958 
13959      Stream:   Logged in SYSERR log.
13960 
13961      Time:     In  response  to   an  operator  command.   System
13962                Intialization.
13963 
13964      Meaning:  A storage  system physical volume has  been placed
13965                in use.  The volume and drive name are identified.
13966 
13967      Action:   No operator  action is required.  This  message is
13968                provided  for  the   benefit  of  automatic  error
13969                analysis and logging.
13970 
13971 
13972 
13973                [mdx.pl1]
13974                disk_table_:  Added drive DSKX_NN
13975 
13976 
13977      Stream:   BOS Typewriter.
13978 
13979      Time:     In response to an operator command.
13980 
13981      Meaning:  The operator has added a storage system disk drive
13982                with adddev.
13983 
13984      Action:   No operator action is required.
13985 
13986 
13987                [disk_table_.pl1]
13988                disk_table_:  cannot locate DRIVE
13989 
13990 
13991 
13992 disk_table_                    242            08/03/23     MR12.7^L
13993 
13994 
13995      Stream:   Initializer process output.
13996 
13997      Time:     While system is running.
13998 
13999      Meaning:  A del_vol DRIVE command was issued but there is no
14000                such drive in the configuration.
14001 
14002      Action:   Enter a corrected command line.
14003 
14004 
14005                [disk_table_.pl1]
14006                disk_table_:  cannot locate DRIVE
14007 
14008 
14009      Stream:   Initializer process output.
14010 
14011      Time:     While system is running.
14012 
14013      Meaning:  A command specifying DRIVE  was issued but no such
14014                drive can be found.
14015 
14016      Action:   Enter a corrected command line.
14017 
14018 
14019                [disk_table_.pl1]
14020                disk_table_:  cannot locate DRIVE
14021 
14022 
14023      Stream:   Initializer process output.
14024 
14025      Time:     While system is running.
14026 
14027      Meaning:  A  disk_rebuild command  cannot locate  the output
14028                drive.
14029 
14030      Action:   Enter a corrected command line.
14031 
14032 
14033                [disk_table_.pl1]
14034                disk_table_:  cannot reregister from ring 4
14035 
14036 
14037      Stream:   Initializer process output.
14038 
14039      Time:     While system is running.
14040 
14041      Meaning:  A reregister command was issued from ring 4.
14042 
14043      Action:   Enter a corrected command line.
14044 
14045 
14046                [disk_table_.pl1]
14047 
14048 
14049 
14050 disk_table_                    243            08/03/23     MR12.7^L
14051 
14052 
14053                disk_table_:    Cannot  verify  label   of  DRIVE:
14054                REASON
14055 
14056 
14057      Stream:   Initializer process output.
14058 
14059      Time:     While system is running.
14060 
14061      Meaning:  An  error occurred  checking the  label of  DRIVE.
14062                Usually either the drive is not ready, or the pack
14063                label does not match the required pack label.
14064 
14065      Action:   Enter a corrected command line.
14066 
14067 
14068                [disk_table_.pl1]
14069                disk_table_:   Could  not  finish  demount  of  lv
14070                LVNAME
14071 
14072 
14073      Stream:   Initializer process output.
14074 
14075      Time:     While system is running.
14076 
14077      Meaning:  The system encountered a  problem trying to delete
14078                the logical volume LVNAME.
14079 
14080      Action:   Contact the system programming staff.
14081 
14082 
14083                [mdx.pl1]
14084                disk_table_:  Deleted drive DSKX_NN
14085 
14086 
14087      Stream:   BOS Typewriter.
14088 
14089      Time:     In response to an operator command.
14090 
14091      Meaning:  The  operator has  deleted a  storage system  disk
14092                drive with deldev.
14093 
14094      Action:   No operator action is required.
14095 
14096 
14097                [mdx.pl1]
14098                disk_table_:    Deleted  root   PV  "PV_NAME"   on
14099                DSKX_NN.
14100 
14101 
14102      Stream:   BOS Typewriter (sounds beeper)
14103 
14104      Time:     System Intialization.
14105 
14106 
14107 
14108 disk_table_                    244            08/03/23     MR12.7^L
14109 
14110 
14111      Meaning:  The  specified drive  did not  appear in  the ROOT
14112                config  card.   Thus,  it  was  removed  from  the
14113                disk_table_.  This will also occur when the volume
14114                is intentionally deleted.
14115 
14116      Action:   Contact the system programming staff.
14117 
14118 
14119                [disk_table_.pl1]
14120                disk_table_:  demounting  partially mounted volume
14121                LVNAME
14122 
14123 
14124      Stream:   Initializer process output.
14125 
14126      Time:     While system is running.
14127 
14128      Meaning:  The  operator issued  a dlv  LVNAME command  for a
14129                logical  volume for  which a  previous dlv command
14130                did not succeed.
14131 
14132      Action:   No operator action is required.
14133 
14134 
14135                [disk_table_.pl1]
14136                disk_table_:  DRIVE in use with PVNAME
14137 
14138 
14139      Stream:   Initializer process output.
14140 
14141      Time:     While system is running.
14142 
14143      Meaning:  A del_vol  DRIVE command was issued  but the drive
14144                is currently in use.
14145 
14146      Action:   Enter  a corrected  command line.   To demount the
14147                pack, use the dlv command.
14148 
14149 
14150 
14151                [disk_table_.pl1]
14152                disk_table_:  DRIVE in use:  contains PVNAME
14153 
14154 
14155      Stream:   Initializer process output.
14156 
14157      Time:     While system is running.
14158 
14159      Meaning:  An attempt to use DRIVE finds it already in use.
14160 
14161      Action:   Enter a corrected command line.
14162 
14163 
14164 
14165 
14166 disk_table_                    245            08/03/23     MR12.7^L
14167 
14168 
14169 
14170 
14171                [disk_table_.pl1]
14172                disk_table_:  DRIVE is an IO drive
14173 
14174 
14175      Stream:   Initializer process output.
14176 
14177      Time:     While system is running.
14178 
14179      Meaning:  A command has been issued  to affect DRIVE, but it
14180                is currently in use as an IO drive.
14181 
14182      Action:   Enter   a  corrected    command  line.    Use  the
14183                set_drive_usage command to change it if necessary.
14184 
14185 
14186 
14187                [disk_table_.pl1]
14188                disk_table_:  DRIVE is deleted
14189 
14190 
14191      Stream:   Initializer process output.
14192 
14193      Time:     While system is running.
14194 
14195      Meaning:  The drive named is deleted.
14196 
14197      Action:   Enter a corrected command line.
14198 
14199 
14200                [disk_table_.pl1]
14201                disk_table_:  DRIVE not found.
14202 
14203 
14204      Stream:   Initializer process output.
14205 
14206      Time:     While system is running.
14207 
14208      Meaning:  The operator  issued an set_drive_usage  DRIVE KEY
14209                command,   but  DRIVE   is  not   in  the  current
14210                configuration.
14211 
14212      Action:   Enter a corrected command line.
14213 
14214 
14215                [disk_table_.pl1]
14216                disk_table_:  DRIVE not in use.
14217 
14218 
14219      Stream:   Initializer process output.
14220 
14221      Time:     While system is running.
14222 
14223 
14224 disk_table_                    246            08/03/23     MR12.7^L
14225 
14226 
14227      Meaning:  A del_vol command was issued but nothing is on the
14228                drive.
14229 
14230      Action:   Enter a corrected command line.
14231 
14232 
14233                [disk_table_.pl1]
14234                disk_table_:  DRIVENAME is an IO drive
14235 
14236 
14237      Stream:   Initializer process output.
14238 
14239      Time:     While system is running.
14240 
14241      Meaning:  The  operator  issued  a  del_vol  command but the
14242                drive is an IO drive.
14243 
14244      Action:   Enter a corrected command line.
14245 
14246 
14247                [disk_table_.pl1]
14248                disk_table_:  DRIVENAME is deleted
14249 
14250 
14251      Stream:   Initializer process output.
14252 
14253      Time:     While system is running.
14254 
14255      Meaning:  A  del_vol command  was issued  but the  drive has
14256                been deleted.
14257 
14258      Action:   Enter a corrected command line.
14259 
14260 
14261                [disk_table_.pl1]
14262                disk_table_:  ERROR_MESSAGE.
14263 
14264 
14265      Stream:   Initializer process output.
14266 
14267      Time:     System Intialization.
14268 
14269      Meaning:  An     error     has     been     returned    from
14270                initializer_mdc_$init.   This  indicates  a  logic
14271                error in the supervisor, or CPU or memory hardware
14272                problems.   Subsequent attempts  to mount  volumes
14273                may malfunction.
14274 
14275      Action:   Contact the system programming staff.
14276 
14277 
14278                [disk_table_.pl1]
14279                disk_table_:  ERROR_MESSAGE.
14280 
14281 
14282 disk_table_                    247            08/03/23     MR12.7^L
14283 
14284 
14285      Stream:   Initializer process output.
14286 
14287      Time:     While system is running.
14288 
14289      Meaning:  An  error has  occurred in  a storage  system disk
14290                manipulation command.
14291 
14292      Action:   Enter a corrected command line.
14293 
14294 
14295                [disk_table_.pl1]
14296                disk_table_:   ERROR_MESSAGE.   Cannot  demount lv
14297                LVNAME
14298 
14299 
14300      Stream:   Initializer process output.
14301 
14302      Time:     While system is running.
14303 
14304      Meaning:  A  dlv  LVNAME  command  was  issued  but an error
14305                prevents the dlv from working.
14306 
14307      Action:   Enter a corrected command line.
14308 
14309 
14310                [disk_table_.pl1]
14311                disk_table_:   ERROR_MESSAGE.   Cannot  get volume
14312                registration for the root logical volume.
14313                Shutdown and reboot with "boot nolv".
14314 
14315 
14316 
14317      Stream:   Initializer process output.
14318 
14319      Time:     System Intialization.
14320 
14321      Meaning:  The   system  is   unable  to   read  the   volume
14322                registration  for  the  root  logical  volume, and
14323                cannot   therefore  determine   if  the   root  is
14324                complete.
14325 
14326      Action:   Shutdown.   If you can  mount the entire  root, do
14327                so, describe all volumes  on the root config card,
14328                "boot  stan nosc",  and fix  the registration.  If
14329                this fails, shutdown, and "boot nolv".
14330 
14331 
14332 
14333                [disk_table_.pl1]
14334                disk_table_:  ERROR_MESSAGE.  cannot stop mount of
14335                LVNAME
14336 
14337 
14338 
14339 
14340 disk_table_                    248            08/03/23     MR12.7^L
14341 
14342 
14343      Stream:   Initializer process output.
14344 
14345      Time:     While system is running.
14346 
14347      Meaning:  A  dlv  LVNAME  command  was  issued  but an error
14348                prevents the dlv from working.
14349 
14350      Action:   Enter a corrected command line.
14351 
14352 
14353                [disk_table_.pl1]
14354                disk_table_:  ERROR_MESSAGE.   Cannot verify label
14355                of DRIVE
14356 
14357 
14358      Stream:   Initializer process output.
14359 
14360      Time:     While system is running.
14361 
14362      Meaning:  An error  occurred checking the label  of the pack
14363                on DRIVE.  Usually either  the drive is not ready,
14364                or the pack label does not match the required pack
14365                label.
14366 
14367      Action:   Enter a corrected command line.
14368 
14369 
14370                [disk_table_.pl1]
14371                disk_table_:  ERROR_MESSAGE.  Could not demount pv
14372                PVNAME of lv LVNAME (DRIVE)
14373 
14374 
14375      Stream:   Initializer process output.
14376 
14377      Time:     While system is running.
14378 
14379      Meaning:  An  error  occurred  when   trying  to  demount  a
14380                physical  volume.   This  may  be  due  to process
14381                directory or wired segments being on this physical
14382                volume.   The  del_lv  command  will  be partially
14383                successful when this happens.
14384 
14385      Action:   Determine  which processes,  if any,  have process
14386                directories  on this  logical volume  and bump  or
14387                terminate them.  Use list_disks to determine which
14388                volumes  are  still  mounted,  and  try dlv again.
14389                Contact the system programming staff.
14390 
14391 
14392 
14393                [disk_table_.pl1]
14394                disk_table_:  ERROR_MESSAGE.   error reregistering
14395                DRIVE
14396 
14397 
14398 disk_table_                    249            08/03/23     MR12.7^L
14399 
14400 
14401      Stream:   Initializer process output.
14402 
14403      Time:     While system is running.
14404 
14405      Meaning:  The reregister DRIVE command did not succeed.
14406 
14407      Action:   Enter a corrected command line.
14408 
14409 
14410                [disk_table_.pl1]
14411                disk_table_:  ERROR_MESSAGE.  LVNAME
14412 
14413 
14414      Stream:   Initializer process output.
14415 
14416      Time:     While system is running.
14417 
14418      Meaning:  An  error  occurred  trying  to  get  the  list of
14419                physical volumes which comprise LVNAME.
14420 
14421      Action:   Enter a corrected command line.
14422 
14423 
14424                [disk_table_.pl1]
14425                disk_table_:    ERROR_MESSAGE.    New   disk_table
14426                created
14427 
14428 
14429      Stream:   Initializer process output.
14430 
14431      Time:     System Intialization.
14432 
14433      Meaning:  The system  has created a new copy  of the segment
14434                >disk_table at initialization time.  The copy from
14435                the  previous bootload  could not  be found.   The
14436                position  of all   previously mounted  volumes has
14437                been forgotten.
14438 
14439      Action:   Use the av command to  specify the position of all
14440                volumes, and the alv command to mount them.
14441 
14442 
14443 
14444                [disk_table_.pl1]
14445                disk_table_:  ERROR_MESSAGE.   salvaging PVNAME on
14446                DRIVE
14447 
14448 
14449      Stream:   Initializer process output.
14450 
14451      Time:     While system is running.
14452 
14453      Meaning:  An error occurred while doing a salvage_vol -all.
14454 
14455 
14456 disk_table_                    250            08/03/23     MR12.7^L
14457 
14458 
14459      Action:   Enter a corrected command line.
14460 
14461 
14462                [disk_table_.pl1]
14463                disk_table_:  invalid drive id "ARG"
14464 
14465 
14466      Stream:   Initializer process output.
14467 
14468      Time:     While system is running.
14469 
14470      Meaning:  The drive id ARG does not have the form dskX_NN.
14471 
14472      Action:   Enter a corrected command line.
14473 
14474 
14475                [disk_table_.pl1]
14476                disk_table_:   lv  LVNAME  cannot  be  mounted, in
14477                process of demount.
14478 
14479 
14480      Stream:   Initializer process output.
14481 
14482      Time:     While system is running.
14483 
14484      Meaning:  An alv  LVNAME command was issued  but the logical
14485                volume is in the process of demounting.
14486 
14487      Action:   Enter a corrected command line.
14488 
14489 
14490                [disk_table_.pl1]
14491                disk_table_:  lv LVNAME already mounted
14492 
14493 
14494      Stream:   Initializer process output.
14495 
14496      Time:     While system is running.
14497 
14498      Meaning:  An  alv   LVNAME  command  finds   LVNAME  already
14499                mounted.
14500 
14501      Action:   Enter a corrected command line.
14502 
14503 
14504                [disk_table_.pl1]
14505                disk_table_:  lv LVNAME not found
14506 
14507 
14508      Stream:   Initializer process output.
14509 
14510      Time:     While system is running.
14511 
14512 
14513 
14514 disk_table_                    251            08/03/23     MR12.7^L
14515 
14516 
14517      Meaning:  A  dlv  LVNAME  command  was  issued  but  no such
14518                logical volume is mounted.
14519 
14520      Action:   Enter a corrected command line.
14521 
14522 
14523                [disk_table_.pl1]
14524                disk_table_:  no drive available for PVNAME LVNAME
14525 
14526 
14527      Stream:   Initializer process output.
14528 
14529      Time:     While system is running.
14530 
14531      Meaning:  An  alv LVNAME  command was  unable to  allocate a
14532                drive for PVNAME.
14533 
14534      Action:   Demount  some  un-needed  logical  volume  and try
14535                again.
14536 
14537 
14538                [disk_table_.pl1]
14539                disk_table_:  PVNAME already in use on DRIVE.
14540 
14541 
14542      Stream:   Initializer process output.
14543 
14544      Time:     While system is running.
14545 
14546      Meaning:  An  attempt to  add  a  physical volume  finds the
14547                volume already in use on another drive.
14548 
14549      Action:   Enter a corrected command line.
14550 
14551 
14552                [disk_table_.pl1]
14553                disk_table_:   PVNAME  currently  known  to  be on
14554                DRIVE
14555 
14556 
14557      Stream:   Initializer process output.
14558 
14559      Time:     While system is running.
14560 
14561      Meaning:  An attempt to specify that  PVNAME is on a certain
14562                drive finds it on another drive.
14563 
14564      Action:   Enter a  corrected command line.  Use  the del_vol
14565                command if necessary to cause the system to forget
14566                DRIVE's old contents, if a pack has been moved.
14567 
14568 
14569 
14570 
14571 
14572 disk_table_                    252            08/03/23     MR12.7^L
14573 
14574 
14575 
14576 
14577                [disk_table_.pl1]
14578                disk_table_:  PVNAME not found.
14579 
14580 
14581      Stream:   Initializer process output.
14582 
14583      Time:     While system is running.
14584 
14585      Meaning:  An  initialize_disk -copy  command could  not find
14586                the source volume.
14587 
14588      Action:   Enter a corrected command line.
14589 
14590 
14591                [mdx.pl1]
14592                disk_table_:  Root PV "PV_NAME" moved from DSKX_NN
14593                to DSKX_NN.
14594 
14595 
14596      Stream:   BOS Typewriter.
14597 
14598      Time:     System Intialization.
14599 
14600      Meaning:  The  specified root  volume  has  been moved  to a
14601                different drive since the last shutdown.
14602 
14603      Action:   No operator action is required.
14604 
14605 
14606                [disk_table_.pl1]
14607                disk_table_:    Some   volumes   are   incomplete.
14608                Complete or demount them.
14609 
14610 
14611      Stream:   Initializer process output.
14612 
14613      Time:     System Intialization.
14614 
14615      Meaning:  Initialization  has  failed  to  remount  all  the
14616                volumes which  were previously known,  in response
14617                to a startup command.
14618 
14619      Action:   Use  the  list_disks  command  to  find  out which
14620                volumes  are  incomplete.   Use   the  av  or  dlv
14621                commands to rectify the situation, and try startup
14622                again.
14623 
14624 
14625 
14626                [disk_table_.pl1]
14627 
14628 
14629 
14630 disk_table_                    253            08/03/23     MR12.7^L
14631 
14632 
14633                disk_table_:    The   root   logical   volume   is
14634                incomplete.
14635 
14636 
14637      Stream:   Initializer process output.
14638 
14639      Time:     System Intialization.
14640 
14641      Meaning:  Some  registered physical   volume(s) of  the root
14642                logical volume  are not mounted, but  the operator
14643                has attempted  to execute a command  that requires
14644                the root  to be completely mounted.   This message
14645                is  followed  by  mount  messages  for the missing
14646                volumes.
14647 
14648 
14649      Action:   Mount the  missing volumes, and notify  the system
14650                of their location with the add_vol command.
14651 
14652 
14653 
14654                [dn355.pl1]
14655                dn355:  attempted crawlout with FNP queue locked
14656 
14657 
14658      Stream:   BOS Typewriter (Crashes system)
14659 
14660      Time:     While system is running.
14661 
14662      Meaning:  An  attempt was  made to  crawl out  while an  FNP
14663                queue lock (a processor lock) was locked.
14664 
14665      Action:   Contact the system programming staff.
14666 
14667 
14668                [dn355.pl1]
14669                dn355:  emergency interrupt from FNP X:  FAULT
14670                FNP instruction counter = IC
14671                channel CHN, fault status = FS
14672                FNP_MODULE:  REASON_FOR_CRASH
14673 
14674 
14675 
14676      Stream:   BOS Typewriter (sounds beeper)
14677 
14678      Time:     While system is running.
14679 
14680      Meaning:  An emergency interrupt has  been received from FNP
14681                X indicating it has  crashed.  All lines dialed to
14682                FNP X  will be hung  up.  The crash  was nominally
14683                caused by a fault  of type FAULT.  Lines following
14684                the  first  line  of  the  message  appear only in
14685 
14686 
14687 
14688 dn355                          254            08/03/23     MR12.7^L
14689 
14690 
14691                certain  cases and provide  additional information
14692                about the nature of the crash.
14693 
14694      Action:   The  system will  automatically attempt  to reboot
14695                the   crashed  FNP.    Subsequent  messages   will
14696                indicate the  success or failure of  this attempt.
14697                No  action  is  required  now,  but  action may be
14698                required if the automatic reboot fails.
14699 
14700 
14701 
14702                [dn355.pl1]
14703                dn355:  Error sending mailbox  interrupt to FNP X,
14704                will retry.
14705 
14706 
14707      Stream:   BOS Typewriter.
14708 
14709      Time:     While system is running.
14710 
14711      Meaning:  An error has been  detected in the transmission of
14712                a mailbox interrupt to  the FNP.  The transmission
14713                will be retried once.
14714 
14715      Action:   None required.
14716 
14717 
14718                [dn355.pl1]
14719                dn355:   FNP  masked  channel  NAME  for excessive
14720                interrupts
14721 
14722 
14723      Stream:   BOS Typewriter.
14724 
14725      Time:     While system is running.
14726 
14727      Meaning:  The FNP has masked the  channel whose name is NAME
14728                because it  was generating interrupts  faster than
14729                they could be handled.
14730 
14731      Action:   The interruptions  can be caused by  any number of
14732                problems.  This can be caused by the dataset leads
14733                changing too  fast for the FNP  software to handle
14734                properly; disconnecting or  connecting FNP cables,
14735                powering  off or  on a  hardwired terminal,  a bad
14736                modem,  etc.  It  is  also  possible that  the FNP
14737                channel hardware is defective.  Future attempts to
14738                use this  channel may possibly crash  the FNP.  CS
14739                representatives   may  need    to  be   called  to
14740                investigate.    An   "attach"   command   will  be
14741                necessary to put the channel back in service.
14742 
14743 
14744 
14745 
14746 dn355                          255            08/03/23     MR12.7^L
14747 
14748 
14749 
14750 
14751                [dn355.pl1]
14752                dn355:  FNP X did not respond to mailbox interrupt
14753 
14754 
14755      Stream:   BOS Typewriter (sounds beeper)
14756 
14757      Time:     While system is running.
14758 
14759      Meaning:  An  attempt to  interrupt FNP  X was unsuccessful.
14760                The FNP is assumed to be down.
14761 
14762      Action:   The  system will  automatically attempt  to reboot
14763                the   crashed  FNP.    Subsequent  messages   will
14764                indicate the  success or failure of  this attempt.
14765                No  action  is  required  now,  but  action may be
14766                required if the automatic reboot fails.
14767 
14768 
14769 
14770                [dn355.pl1]
14771                dn355:  FNP X invalid interrupt level N
14772 
14773 
14774      Stream:   BOS Typewriter (sounds beeper)
14775 
14776      Time:     While system is running.
14777 
14778      Meaning:  An FNP interrupt has been received from frontend X
14779                with an  invalid interrupt level of  octal value N
14780                and will be ignored.  If this message is displayed
14781                when  a DN6670 is  being powered up,  this message
14782                can be ignored.  If  this message occurs under any
14783                other  circumstances,  there  might  be  something
14784                wrong with the system's interface with the FNP and
14785                should be investigated by FE representatives.
14786 
14787      Action:   Contact the system programming staff.
14788 
14789 
14790                [dn355.pl1]
14791                dn355:  FNP X level L status S STATE
14792 
14793 
14794      Stream:   BOS Typewriter.
14795 
14796      Time:     While system is running.
14797 
14798      Meaning:  An interrupt at a level  other than 3 (or possibly
14799                at level 3 if the FNP is not running) was received
14800                from FNP  X.  S is an octal  representation of the
14801                status   accompanying    the   interrupt.    STATE
14802 
14803 
14804 dn355                          256            08/03/23     MR12.7^L
14805 
14806 
14807                indicates the current state  of the FNP:  running,
14808                bootloading, or in T&D.  This message only appears
14809                if tracing is enabled for the specified FNP.
14810 
14811      Action:   None required.
14812 
14813 
14814                [dn355.pl1]
14815                dn355:  inconsistent queue lock
14816 
14817 
14818      Stream:   BOS Typewriter (Crashes system)
14819 
14820      Time:     While system is running.
14821 
14822      Meaning:  A process attempted to  unlock the interrupt queue
14823                lock without having it locked.
14824 
14825      Action:   Contact the system programming staff.
14826 
14827 
14828                [dn355.pl1]
14829                dn355:  LCTE lock ^= processid
14830 
14831 
14832      Stream:   BOS Typewriter (Crashes system)
14833 
14834      Time:     While system is running.
14835 
14836      Meaning:  The FNP channel lock did not contain the processid
14837                of the process attempting to unlock it.
14838 
14839 
14840 
14841                [dn355.pl1]
14842                dn355:  line number of 0 with non-global opcode in
14843                submbx N, FNP X
14844 
14845 
14846      Stream:   BOS Typewriter (sounds beeper)er
14847 
14848      Time:     While system is running.
14849 
14850      Meaning:  Mailbox N from FNP X contained a non-global opcode
14851                which requires a non-zero line number.
14852 
14853 
14854 
14855                [dn355.pl1]
14856                dn355:  Message from FNP X:  MESSAGE
14857 
14858 
14859      Stream:   BOS Typewriter.
14860 
14861 
14862 dn355                          257            08/03/23     MR12.7^L
14863 
14864 
14865      Time:     While system is running.
14866 
14867      Meaning:  An error  has been detected by FNP  X as explained
14868                by MESSAGE.
14869 
14870      Action:   No action is required by the operator to deal with
14871                the error mentioned in the message.  Action may be
14872                required by  appropriate personnel to  correct the
14873                problem  that caused the  error and undo  what the
14874                FNP may have done to continue operation.  This may
14875                require shutting down the FNP for repairs by Field
14876                Engineering and reboot of  the FNP to restore full
14877                operation.
14878 
14879 
14880 
14881                [dn355.pl1]
14882                dn355:  no slot number match for sub mbx N, FNP X
14883 
14884 
14885      Stream:   BOS Typewriter (sounds beeper)er
14886 
14887      Time:     While system is running.
14888 
14889      Meaning:  An error has occurred  processing submailbox N for
14890                FNP X.  The submailbox indicates a line number for
14891                which no match could be found.
14892 
14893      Action:   Contact the system programming staff.
14894 
14895 
14896                [dn355.pl1]
14897                dn355:  output buffer at N has zero tally
14898 
14899 
14900      Stream:   BOS Typewriter (Crashes system)
14901 
14902      Time:     While system is running.
14903 
14904      Meaning:  An output buffer with a  zero tally has been found
14905                at offset N in the segment tty_buf.
14906 
14907      Action:   Contact the system programming staff.
14908 
14909 
14910                [dn355.pl1]
14911                dn355:  Timeout  sending mailbox interrupt  to FNP
14912                X, will retry.
14913 
14914 
14915      Stream:   BOS Typewriter.
14916 
14917      Time:     While system is running.
14918 
14919 
14920 dn355                          258            08/03/23     MR12.7^L
14921 
14922 
14923      Meaning:  The FNP  did not respond  within 2 seconds  to the
14924                previously    sent    mailbox    interrupt.    The
14925                transmission will be retried once.
14926 
14927      Action:   None required.
14928 
14929 
14930                [dn355.pl1]
14931                dn355:  unable to allocate block for delay queue
14932 
14933 
14934      Stream:   BOS Typewriter (Crashes system)
14935 
14936      Time:     While system is running.
14937 
14938      Meaning:  There  was insufficient  space left  in tty_buf to
14939                allocate a block in which to build a delay queue.
14940 
14941      Action:   Contact the system programming staff.
14942 
14943 
14944                [dn355.pl1]
14945                dn355:  unrecognized  io command C from  FNP X for
14946                line N
14947 
14948 
14949      Stream:   BOS Typewriter (sounds beeper)er
14950 
14951      Time:     While system is running.
14952 
14953      Meaning:  An invalid io command was  received from FNP X for
14954                line  N.  C  is  the  octal representation  of the
14955                command.
14956 
14957      Action:   Contact the system programming staff.
14958 
14959 
14960                [dn355.pl1]
14961                dn355:  unrecognized op code  OPCODE with rcd from
14962                FNP X for devx N
14963 
14964 
14965      Stream:   BOS Typewriter (sounds beeper)er
14966 
14967      Time:     While system is running.
14968 
14969      Meaning:  An invalid op code, OPCODE, has been received from
14970                FNP X  for device index N in  a mailbox containing
14971                an rcd (read control data) command.
14972 
14973      Action:   Contact the system programming staff.
14974 
14975 
14976 
14977 
14978 dpg_                           259            08/03/23     MR12.7^L
14979 
14980 
14981                [dpg_.pl1]
14982                dpg_:   COND  condition  signalled  while  copying
14983                stack_0 into >pdd>DIRNAME
14984 
14985 
14986      Stream:   as (severity0)
14987 
14988      Time:     While system is running.
14989 
14990      Meaning:  An error  occurred while copying the  ring-0 stack
14991                of the defunct process  from ring-0 into the saved
14992                process  directory.  This   error caused  the COND
14993                condition to be signalled.   The ring-0 stack will
14994                not be copied into the saved process directory.
14995 
14996      Action:   No operator action is required.
14997 
14998 
14999                [dpg_.pl1]
15000                dpg_:   ERROR_MESSAGE.  Attempting to  rename pdir
15001                for NAME.PROJ CHN after fatal process error.
15002 
15003 
15004      Stream:   as (severity1)
15005 
15006      Time:     While system is running.
15007 
15008      Meaning:  The  error  described  by  ERROR_MESSAGE  occurred
15009                while  attempting to   save the  process directory
15010                belonging  to  the  user  PERS.PROJ  after a fatal
15011                process  error.  The  directory was  not saved.  A
15012                typical cause of this is that the user already has
15013                a  saved process  directory from  a previous fatal
15014                process error in this bootload.
15015 
15016      Action:   Contact the system programming staff.
15017 
15018 
15019                [dpg_.pl1]
15020                dpg_:            ERROR_MESSAGE.            Calling
15021                hphcs_$destroy_process_begin                   for
15022                PERSON.PROJECT.TAG on channel CHN, process_id PID.
15023 
15024 
15025 
15026      Stream:   as (severity 1)
15027 
15028      Time:     While system is running.
15029 
15030      Meaning:  An error  has occurred while destroying  a process
15031                belonging to the user PERSON.PROJECT.TAG connected
15032                to  terminal channel  CHN.  This  process probably
15033                cannot  be destroyed.   ERROR_MESSAGE is  the text
15034 
15035 
15036 dpg_                           260            08/03/23     MR12.7^L
15037 
15038 
15039                associated    with   the    error   returned    by
15040                hphcs_$destroy_process_begin.
15041 
15042      Action:   Contact the system programming staff.
15043 
15044 
15045                [dpg_.pl1]
15046                dpg_:  ERROR_MESSAGE.  Creating  saved stack_0 for
15047                PERS.PROJ (PROCESSID).
15048 
15049 
15050      Stream:   as (severity0)
15051 
15052      Time:     While system is running.
15053 
15054      Meaning:  An error has occurred while attempting to create a
15055                segment in the saved process directory for copying
15056                the  ring-0  stack  of  the  defunct process.  The
15057                ring-0  stack will  not be  copied into  the saved
15058                process directory.
15059 
15060      Action:   No operator action is required.
15061 
15062 
15063                [dpg_.pl1]
15064                dpg_:     ERROR_MESSAGE.     destroying    process
15065                WWWWWWWWWWWW for NAME.PROJ
15066 
15067 
15068      Stream:   as (severity2)
15069 
15070      Time:     While system is running.
15071 
15072      Meaning:  An error  has occurred while destroying  a process
15073                belonging  to  the  user  NAME.PROJ.   He  was not
15074                charged for his CPU usage.
15075 
15076      Action:   Contact the system programming staff.
15077 
15078 
15079                [dpg_.pl1]
15080                dpg_:     removed    USER    (PROCESSID)   process
15081                termination monitor.
15082 
15083 
15084      Stream:   as (severity0)
15085 
15086      Time:     While system is running.
15087 
15088      Meaning:  Process  termination monitoring for  USER (process
15089                id PROCESSID) has been terminated by user request,
15090                IPC error, or the destruction of the process.
15091 
15092 
15093 
15094 dpg_                           261            08/03/23     MR12.7^L
15095 
15096 
15097      Action:   No operator action is required.
15098 
15099 
15100                [dpg_.pl1]
15101                dpg_:   Saved   >pdd>PERS.PROJ.f.CHN  after  fatal
15102                process error.
15103 
15104 
15105      Stream:   as (severity1)
15106 
15107      Time:     While system is running.
15108 
15109      Meaning:  The process directory  belonging to user PERS.PROJ
15110                has  been saved after  a fatal process  error.  It
15111                has been renamed to the name shown in the message.
15112                It will be saved  until the next shutdown.  System
15113                programmers might want to  examine its contents to
15114                determine the cause of the fatal process error.
15115 
15116      Action:   Inform the  system programming staff.  Do  so well
15117                in advance of the next shutdown.
15118 
15119 
15120                [dpg_.pl1]
15121                dpg_:   USER  (PROCESSID)  {set/replaced}  process
15122                termination monitor.
15123 
15124 
15125      Stream:   as (severity0)
15126 
15127      Time:     While system is running.
15128 
15129      Meaning:  USER    (processid    PROCESSID)    will   receive
15130                notifications of all process destructions from the
15131                Answering  Service.   'set'   indicates  that  the
15132                process  was  not  already  monitoring  processes;
15133                'replaced' indicates that  the process already had
15134                a  monitor  established,  and  that  it  has  been
15135                replaced by this request.
15136 
15137      Action:   No operator action is required.
15138 
15139 
15140                [wired_shutdown.pl1]
15141                emergency shutdown part 1 complete
15142 
15143 
15144      Stream:   BOS Typewriter.
15145 
15146      Time:     Emergency shutdown
15147 
15148      Meaning:  All of memory has been written out once, and those
15149                pages on the paging  device which could be written
15150 
15151 
15152 emergency                      262            08/03/23     MR12.7^L
15153 
15154 
15155                out to operative drives flushed.  All segments and
15156                directories  will  now  be  deactivated,  and  all
15157                drives shut down.
15158 
15159      Action:   No operator action is required.
15160 
15161 
15162                [dn355_boot_interrupt.pl1]
15163                error reading core image for FNP X
15164 
15165 
15166      Stream:   BOS Typewriter.
15167 
15168      Time:     When bootloading an FNP
15169 
15170      Meaning:  An  I/O error  was  detected  by the  FNP bootload
15171                program  while attempting  to read  the core image
15172                into FNP memory.  A hardware failure of either the
15173                DIA or the Multics IOM is indicated.
15174 
15175      Action:   Try  the  FNP  load  again.   If  it  fails again,
15176                consult Field Engineering.
15177 
15178 
15179                [multiplexer_mgr_.pl1]
15180                ERROR.  cdt_mgr_$find_cdt_channel:  INFO
15181 
15182 
15183      Stream:   as (severity1)
15184 
15185      Time:     While system is running.
15186 
15187      Meaning:  An error  (identified by the status  code reported
15188                in  ERROR) has  occurred  while  trying to  find a
15189                multiplexer name in  the CDT.  Further information
15190                about the error is given in INFO.
15191 
15192      Action:   Contact the system programming staff.
15193 
15194 
15195                [mrd_util_.pl1]
15196                Error:  CONDITION in mrd_util_$ENTRY
15197 
15198 
15199      Stream:   BOS Typewriter (sounds beeper)
15200 
15201      Time:     While system is running.
15202 
15203      Meaning:  CONDITION  was  signalled  during  a  call  to the
15204                entrypoint   ENTRY   in   mrd_util_.    A  message
15205                coordinator dump is taken.  If the calling process
15206                had  a message   coordinator segment  locked, that
15207                segment is  checked for consistency, and  the lock
15208 
15209 
15210 Error                          263            08/03/23     MR12.7^L
15211 
15212 
15213                is unlocked.  mrd_util_ then returns to its caller
15214                without retrying the  operation that failed.  This
15215                indicates a logic error  in the supervisor, or CPU
15216                or memory hardware problems.
15217 
15218      Action:   Contact  the system  programming staff.   Save all
15219                console and message coordinator terminal output.
15220 
15221 
15222 
15223                [wired_shutdown.pl1]
15224                esd before fs enabled
15225 
15226 
15227      Stream:   BOS Typewriter.
15228 
15229      Time:     Emergency shutdown
15230 
15231      Meaning:  The system  crashed before the storage  system was
15232                accessed by Multics.  An ESD was attempted, but no
15233                ESD is necessary.  The "shutdown complete" message
15234                will always follow.
15235 
15236      Action:   Reboot the system.
15237 
15238 
15239                [page_error.alm]
15240                evict_page:  fatal parity error moving page, frame
15241                at AAA, SCU TAG.
15242 
15243 
15244      Stream:   BOS Typewriter (Crashes system)
15245 
15246      Time:     While system is running.
15247 
15248      Meaning:  A  parity  error  was  encountered  while moving a
15249                wired  page around  memory.  The  page may  not be
15250                usable.
15251 
15252      Action:   Contact Field Engineering personnel about possible
15253                problems  with SCU   TAG.  Follow  normal recovery
15254                procedures.
15255 
15256 
15257 
15258                [page_error.alm]
15259                evict_page:   parity error  moving page,  frame at
15260                AAA, SCU TAG.
15261 
15262 
15263      Stream:   BOS Typewriter.
15264 
15265      Time:     While system is running.
15266 
15267 
15268 evict_page                     264            08/03/23     MR12.7^L
15269 
15270 
15271      Meaning:  A parity error was encountered while moving a page
15272                within main memory.  This may  occur as part of an
15273                attempt to  delete that main memory, or  use it as
15274                an I/O buffer.
15275 
15276      Action:   Inform Field Engineering  personnel about possible
15277                problems with this SCU.
15278 
15279 
15280 
15281                [find_file_partition.pl1]
15282                find_file_partition:    file   partition   is  NNN
15283                records, not between 30 and 255.
15284 
15285 
15286      Stream:   BOS Typewriter (Crashes system)
15287 
15288      Time:     System Intialization.
15289 
15290      Meaning:  The partition holding the bce file system is of an
15291                invalid size.  The rpv was either mal-formatted or
15292                damaged.
15293 
15294      Action:   The rpv will need to be rebuilt.
15295 
15296 
15297                [find_file_partition.pl1]
15298                find_file_partition:  Initting file partition.
15299 
15300 
15301      Stream:   BOS Typewriter.
15302 
15303      Time:     System Intialization.
15304 
15305      Meaning:  The  bce file  system was  found to  be damaged or
15306                never  initialized.   Any  previous  contents  are
15307                discarded.
15308 
15309 
15310 
15311                [find_file_partition.pl1]
15312                find_file_partition:  No file partition defined on
15313                RPV.
15314 
15315 
15316      Stream:   BOS Typewriter (Crashes system)
15317 
15318      Time:     System Intialization.
15319 
15320      Meaning:  The partition used to hold  the bce file system is
15321                missing from the rpv.  Suspect damage of the rpv.
15322 
15323      Action:   The rpv will need to be rebuilt.
15324 
15325 
15326 FNP                            265            08/03/23     MR12.7^L
15327 
15328 
15329 
15330 
15331                [fnp_util.pl1]
15332                FNP T deleted from configuration^[ by ^a^].
15333 
15334 
15335 
15336 
15337 
15338 
15339                [dn355_boot_interrupt.pl1]
15340                FNP X loaded successfully
15341 
15342 
15343      Stream:   BOS Typewriter.
15344 
15345      Time:     When bootloading an FNP
15346 
15347      Meaning:  The FNP bootload has completed successfully.
15348 
15349      Action:   This message is for informational purposes only.
15350 
15351 
15352                [dn355_boot_interrupt.pl1]
15353                FNP X not loaded.
15354 
15355 
15356      Stream:   BOS Typewriter.
15357 
15358      Time:     When bootloading an FNP
15359 
15360      Meaning:  The attempted  bootload was not  successful.  This
15361                message  is always  preceded by  one of  the above
15362                error messages.
15363 
15364      Action:   This message is for informational purposes only.
15365 
15366 
15367                [fnp_init.pl1]
15368                fnp_init:  FNP number N > max allowed number (MAX)
15369                of FNPs
15370 
15371 
15372      Stream:   BOS Typewriter (Crashes system)
15373 
15374      Time:     System Intialization.
15375 
15376      Meaning:  An fnp card from the  config deck specifies an FNP
15377                tag other than A, B, C, D, E, F, G, or H.
15378 
15379      Action:   Replace the bad fnp card and reboot.
15380 
15381 
15382 
15383 
15384 fnp_init                       266            08/03/23     MR12.7^L
15385 
15386 
15387 
15388 
15389                [fnp_init.pl1]
15390                fnp_init:  inconsistent fnp cards.
15391 
15392 
15393      Stream:   BOS Typewriter (Crashes system)
15394 
15395      Time:     System Intialization.
15396 
15397      Meaning:  Two or more fnp cards from the config deck specify
15398                the same FNP tag.
15399 
15400      Action:   Replace or remove the bad fnp card(s) and reboot.
15401 
15402 
15403                [fnp_init.pl1]
15404                fnp_init:  Invalid  model # (MODELN) on  prph fnpX
15405                card.
15406 
15407 
15408      Stream:   BOS Typewriter (Crashes system)
15409 
15410      Time:     System Intialization.
15411 
15412      Meaning:  The  current fnp  model  number  MODELN, is  not a
15413                supported number.
15414 
15415      Action:   Contact the system programming staff.
15416 
15417 
15418                [fnp_init.pl1]
15419                fnp_init:  Invalid state on prph fnpX card.
15420 
15421 
15422      Stream:   BOS Typewriter (Crashes system)
15423 
15424      Time:     System Intialization.
15425 
15426      Meaning:  The only valid states are "on" or "off".
15427 
15428      Action:   Contact the system programming staff.
15429 
15430 
15431                [fnp_init.pl1]
15432                fnp_init:   Less than 256  words of free  space in
15433                tty_buf:  N
15434 
15435 
15436      Stream:   BOS Typewriter (Crashes system)
15437 
15438      Time:     System Intialization.
15439 
15440 
15441 
15442 fnp_init                       267            08/03/23     MR12.7^L
15443 
15444 
15445      Meaning:  Only N words of free space remain in tty_buf after
15446                allocating  the  header  and  circular  queue.   A
15447                minimum  of 256  words is  required and ordinarily
15448                more free space is  desirable.  Either the size of
15449                tty_buf,  as  specified  by  the  PARM TTYB config
15450                card,  must  be  increased  or  the circular queue
15451                size, as  specified by the PARM  TTYQ config card,
15452                must be decreased.
15453 
15454      Action:   Correct the config deck and reboot the system.
15455 
15456 
15457                [fnp_init.pl1]
15458                fnp_init:  no fnp cards in config deck
15459 
15460 
15461      Stream:   BOS Typewriter.
15462 
15463      Time:     System Intialization.
15464 
15465      Meaning:  There  are no  fnp cards  in the  config deck  and
15466                therefore,  no FNP  will be  initialized.  Usually
15467                this indicates  an error, although it  is possible
15468                to run Multics without an FNP.
15469 
15470      Action:   If  an FNP  is wanted,  reboot the  system with an
15471                appropriate config deck.
15472 
15473 
15474 
15475                [fnp_init.pl1]
15476                fnp_init:   The  number   of  configured  protocol
15477                channels of N exceeds the maximum allowed of N.
15478 
15479 
15480 
15481      Stream:   BOS Typewriter (Crashes system)
15482 
15483      Time:     System Intialization.
15484 
15485      Meaning:  The prot  parm from the config  deck specifies too
15486                many protocol channels.
15487 
15488      Action:   Contact the system programming staff.
15489 
15490 
15491                [fnp_init.pl1]
15492                fnp_init:     Unable    to    abs_wire    tty_buf.
15493                ERROR_CODE_MESSAGE
15494 
15495 
15496      Stream:   BOS Typewriter (Crashes system)
15497 
15498 
15499 
15500 fnp_init                       268            08/03/23     MR12.7^L
15501 
15502 
15503      Time:     System Intialization.
15504 
15505      Meaning:  The call to allocate memory in the bootload memory
15506                controller for tty_buf failed.
15507 
15508      Action:   Contact the system programming staff.
15509 
15510 
15511                [fnp_multiplexer.pl1]
15512                fnp_multiplexer$assign_channel:  Assignment of FNP
15513                X {succeeded | failed}.
15514 
15515 
15516      Stream:   BOS Typewriter.
15517 
15518      Time:     While system is running.
15519 
15520      Meaning:  Indicates    the    result    of    a    call   to
15521                io_manager$assign  for FNP  X.  This  message only
15522                appears  if tracing  is enabled  for the specified
15523                FNP.
15524 
15525      Action:   none required.
15526 
15527 
15528                [fnp_multiplexer.pl1]
15529                fnp_multiplexer$ENTRY:  Tracing call.
15530 
15531 
15532      Stream:   BOS Typewriter.
15533 
15534      Time:     While system is running.
15535 
15536      Meaning:  A call was made to  the ENTRY entry.  This message
15537                only  appears  if  tracing   is  enabled  for  the
15538                specified FNP.
15539 
15540      Action:   none required.
15541 
15542 
15543                [fnp_multiplexer.pl1]
15544                fnp_multiplexer$ENTRY:  Tracing error.  ERROR.
15545 
15546 
15547      Stream:   BOS Typewriter.
15548 
15549      Time:     While system is running.
15550 
15551      Meaning:  The   error   code   represented   by   ERROR  was
15552                encountered by  ENTRY.  This message  only appears
15553                if tracing is enabled for the specified FNP.
15554 
15555      Action:   none required.
15556 
15557 
15558 fnp_multiplexer$shutdown       269            08/03/23     MR12.7^L
15559 
15560 
15561 
15562 
15563                [fnp_multiplexer.pl1]
15564                fnp_multiplexer$shutdown:  Called with FNP wired.
15565 
15566 
15567      Stream:   BOS Typewriter.
15568 
15569      Time:     While system is running.
15570 
15571      Meaning:  A call  was made to  the shutdown entry  while the
15572                pages for  I/O for an FNP were  still wired.  This
15573                message only appears if tracing is enabled for the
15574                specified FNP.
15575 
15576      Action:   none required.
15577 
15578 
15579                [fnp_multiplexer.pl1]
15580                fnp_multiplexer$shutdown:    Called    with   null
15581                fnp_ptr
15582 
15583 
15584      Stream:   BOS Typewriter.
15585 
15586      Time:     While system is running.
15587 
15588      Meaning:  A call was made to  the shutdown entry with a null
15589                pointer to fnp_info.  This message only appears if
15590                tracing is enabled for the specified FNP.
15591 
15592      Action:   Contact the system programming staff.
15593 
15594 
15595                [fnp_multiplexer.pl1]
15596                fnp_multiplexer$shutdown:   Failed to  unwire fnp.
15597                ERROR.
15598 
15599 
15600      Stream:   BOS Typewriter.
15601 
15602      Time:     While system is running.
15603 
15604      Meaning:  An attempt to unwire the  pages used for I/O to an
15605                FNP  failed at  FNP shutdown.   ERROR contains the
15606                message derived from a standard system error code.
15607 
15608      Action:   Contact the system programming staff.
15609 
15610 
15611                [fnp_multiplexer.pl1]
15612                fnp_multiplexer$unassign_channel:  Unassignment of
15613                FNP X {succeeded | failed}.
15614 
15615 
15616 fnp_multiplexer$unassign_channel^H270            08/03/23     MR12.7^L
15617 
15618 
15619      Stream:   BOS Typewriter.
15620 
15621      Time:     While system is running.
15622 
15623      Meaning:  Indicates    the    result    of    a    call   to
15624                io_manager$unassign for FNP  X.  This message only
15625                appears  if tracing  is enabled  for the specified
15626                FNP.
15627 
15628      Action:   none required.
15629 
15630 
15631                [fnp_multiplexer.pl1]
15632                fnp_multiplexer:   debugging  stop   (type  go  to
15633                continue).
15634 
15635 
15636      Stream:   BOS Typewriter (Crashes system)
15637 
15638      Time:     While system is running.
15639 
15640      Meaning:  An  error has  been encountered  in setting  up an
15641                FNP, and debugging mode is turned on.
15642 
15643      Action:   Use  BCE  commands  to  analyze  the condition, if
15644                necessary; type "go" to resume system operation.
15645 
15646 
15647 
15648                [fnp_multiplexer.pl1]
15649                fnp_multiplexer:  get_meters order for FNP X, line
15650                N, timed out.
15651 
15652 
15653      Stream:   BOS Typewriter.
15654 
15655      Time:     While system is running.
15656 
15657      Meaning:  A get_meters order  for line N of FNP  X failed to
15658                complete  within  10  seconds.   The  buffer space
15659                associated with the order  has been abandoned, and
15660                get_meters, dump, and patch orders to that FNP are
15661                disabled until the FNP is reloaded.
15662 
15663 
15664 
15665                [fnp_multiplexer.pl1]
15666                fnp_multiplexer:  mylock error
15667 
15668 
15669      Stream:   BOS Typewriter (Crashes system)
15670 
15671      Time:     While system is running.
15672 
15673 
15674 fnp_multiplexer                271            08/03/23     MR12.7^L
15675 
15676 
15677      Meaning:  An attempt  has been made  to lock an  FNP channel
15678                lock to a process that already has it locked.
15679 
15680      Action:   Contact the system programming staff.
15681 
15682 
15683                [fnp_multiplexer.pl1]
15684                fnp_multiplexer:  NAME order to FNP X timed out.
15685 
15686 
15687      Stream:   BOS Typewriter.
15688 
15689      Time:     While system is running.
15690 
15691      Meaning:  NAME is "get_meters",  "dump_fnp", or "patch_fnp".
15692                The named order to FNP X failed to complete within
15693                10 seconds.  The buffer  space associated with the
15694                order  has been  abandoned, and  get_meters, dump,
15695                and  patch orders to  that FNP are  disabled until
15696                the FNP is reloaded.
15697 
15698      Action:   Contact the system programming staff.
15699 
15700 
15701                [fnp_multiplexer.pl1]
15702                fnp_multiplexer:  patching  FNP X for  USER:  ADDR
15703                from XXX to YYY
15704 
15705 
15706 
15707      Stream:   BOS Typewriter.
15708 
15709      Time:     While system is running.
15710 
15711      Meaning:  The  memory  of  FNP  X  is  being  patched by the
15712                privileged  user whose  user_id is  USER.  ADDR is
15713                the absolute location in  FNP memory that is being
15714                patched (in  octal); XXX and  YYY are the  old and
15715                new values  of the location respectively  (also in
15716                octal).   The second  line may  be repeated  (with
15717                different values)  if more than one  word is being
15718                patched.
15719 
15720      Action:   This information is for logging purposes.
15721 
15722 
15723                [fnp_util.pl1]
15724                fnp_util$configure:  FNP T already configured.
15725 
15726 
15727 
15728 
15729 
15730 
15731 
15732 fnp_util$ENTRY                 272            08/03/23     MR12.7^L
15733 
15734 
15735 
15736 
15737                [fnp_util.pl1]
15738                fnp_util$ENTRY:    Debugging  stop  (type   go  to
15739                continue).
15740 
15741 
15742 
15743 
15744 
15745 
15746                [fnp_util.pl1]
15747                fnp_util$ENTRY:  Invalid call for FNP INDEX.  (not
15748                in cdeck)
15749 
15750 
15751 
15752 
15753 
15754 
15755                [fnp_util.pl1]
15756                fnp_util$ENTRY:  Invalid call.  (trace)
15757 
15758 
15759 
15760 
15761 
15762 
15763                [fnp_util.pl1]
15764                fnp_util$ENTRY:  Tracing call for fnp T.
15765 
15766 
15767 
15768 
15769 
15770 
15771                [fnp_util.pl1]
15772                fnp_util$fdump_seg_io:  IO_OP for CALLER (trace)
15773 
15774 
15775 
15776 
15777 
15778 
15779                [fnp_util.pl1]
15780                fnp_util$load:   Error  loading   FNP  T.   REASON
15781                (trace)
15782 
15783 
15784 
15785 
15786 
15787 
15788 
15789 
15790 fnp_util$load                  273            08/03/23     MR12.7^L
15791 
15792 
15793                [fnp_util.pl1]
15794                fnp_util$load:  FNP  load already in  progress for
15795                FNP T.
15796 
15797 
15798 
15799 
15800 
15801 
15802                [fnp_util.pl1]
15803                fnp_util$load:  FNP T is running T&D.
15804 
15805 
15806 
15807 
15808 
15809 
15810                [fnp_util.pl1]
15811                fnp_util$load:  FNP T is running.  (trace)
15812 
15813 
15814 
15815 
15816 
15817 
15818                [fnp_util.pl1]
15819                fnp_util$load:  FNP T not wired.
15820 
15821 
15822 
15823 
15824 
15825 
15826                [fnp_util.pl1]
15827                fnp_util$unwire:  Unwire failed for FNP T.  REASON
15828 
15829 
15830 
15831 
15832 
15833 
15834                [fnp_util.pl1]
15835                fnp_util$validate_assigned_ret    (CALLER):     IO
15836                manager assignment lacking.  (trace)
15837 
15838 
15839 
15840 
15841 
15842 
15843                [fnp_util.pl1]
15844                fnp_util$wire:  failed.  REASON (trace)
15845 
15846 
15847 
15848 fnp_util$wire                  274            08/03/23     MR12.7^L
15849 
15850 
15851 
15852 
15853                [fnp_util.pl1]
15854                fnp_util$wire:  FNP T already wired (trace)
15855 
15856 
15857 
15858 
15859 
15860 
15861                [fnp_util.pl1]
15862                fnp_util:  assigned FNP T to NAME for T & D.
15863 
15864 
15865 
15866 
15867 
15868 
15869                [fnp_util.pl1]
15870                fnp_util:   channel assignment  failed for  FNP ^T
15871                REASON.  (tandd)
15872 
15873 
15874 
15875 
15876 
15877 
15878                [fnp_util.pl1]
15879                fnp_util:    Could   not   unassign   FNP   T   at
15880                reassign_interrupt.
15881 
15882 
15883 
15884 
15885 
15886 
15887                [fnp_util.pl1]
15888                fnp_util:   FNP  T  added  to  configuration^[  by
15889                NAME^].
15890 
15891 
15892 
15893 
15894 
15895 
15896                [fnp_util.pl1]
15897                fnp_util:  force detaching FNP T from process PID.
15898 
15899 
15900 
15901 
15902 
15903 
15904 
15905 
15906 fnp_util                       275            08/03/23     MR12.7^L
15907 
15908 
15909 
15910 
15911                [fnp_util.pl1]
15912                fnp_util:  io channel  unassignment failed for FNP
15913                T.  (tandd)
15914 
15915 
15916 
15917      Message:  fnp_util:  releasing FNP T from NAME (tandd)
15918 
15919 
15920 
15921                [fnp_util.pl1]
15922                fnp_util:  io channel  unassignment failed for FNP
15923                T.  (tandd)
15924 
15925 
15926 
15927 
15928 
15929 
15930                [fnp_util.pl1]
15931                fnp_util:  ioam_$assign failed  for FNP T.  REASON
15932                (tandd)
15933 
15934 
15935 
15936 
15937 
15938 
15939                [fnp_util.pl1]
15940                fnp_util:  lock_fnp called with lock locked.
15941 
15942 
15943 
15944 
15945 
15946 
15947                [page_error.alm]
15948                free_store:  Deposit non-disk address XXXXXXXXXXXX
15949                on dskX_NN{S}
15950 
15951 
15952      Stream:   BOS Typewriter (Crashes system)
15953 
15954      Time:     While system is running.
15955 
15956      Meaning:  free_store was called to  return an address to the
15957                free pool for dskX_NN{S}, but the address type was
15958                not  disk.   This  probably  indicates  a software
15959                error.
15960 
15961      Action:   Follow normal recovery procedures.
15962 
15963 
15964 free_store                     276            08/03/23     MR12.7^L
15965 
15966 
15967 
15968 
15969                [page_error.alm]
15970                free_store:   Deposit/withdraw address  XXXXXX out
15971                of paging region on dskX_NN{S}.
15972 
15973 
15974      Stream:   BOS Typewriter (Crashes system)
15975 
15976      Time:     While system is running.
15977 
15978      Meaning:  Address XXXXXX was being deposited to or wtihdrawn
15979                from  the pool  of free  addresses for dskX_NN{S},
15980                but  the address is  not within the  Paging Region
15981                for  the   device.   This  probably   indicates  a
15982                software error.
15983 
15984      Action:   Follow normal recovery procedures.
15985 
15986 
15987                [page_error.alm]
15988                free_store:         Invalid         call        to
15989                free_store$deposit_list.
15990 
15991 
15992      Stream:   BOS Typewriter (Crashes system)
15993 
15994      Time:     While system is running.
15995 
15996      Meaning:  free_store$deposit_list was called  with the wrong
15997                number of arguments.  This is a software error.
15998 
15999      Action:   Follow normal recovery procedures.
16000 
16001 
16002                [page_error.alm]
16003                free_store:  out of room in hardcore partition.
16004 
16005 
16006      Stream:   BOS Typewriter (Crashes system)
16007 
16008      Time:     While system is running.
16009 
16010      Meaning:  During  bootload, the  PART HC  on the  RLV became
16011                full.   This  indicates  a   logic  error  in  the
16012                supervisor, or CPU or memory hardware problems.
16013 
16014      Action:   Follow  normal  recovery  procedures.   It  may be
16015                necessary  to  boot  with  another  tape.  If this
16016                error occurs with a new version of the system boot
16017                tape, the  system programming staff  may determine
16018                that  the size of  the hardcore partition  must be
16019 
16020 
16021 
16022 free_store                     277            08/03/23     MR12.7^L
16023 
16024 
16025                increased by  using the rebuild_disk command  on a
16026                copy of the RPV.
16027 
16028 
16029 
16030                [page_error.alm]
16031                free_store:    PVTE/Stock   out    of   synch   on
16032                dskX_NN{S}.  stockp=YYY|YYYYY.
16033 
16034 
16035      Stream:   BOS Typewriter (Crashes system)
16036 
16037      Time:     While system is running.
16038 
16039      Meaning:  The  PVTE and record  stock for dskX_NN{S}  do not
16040                point to each other.  This indicates a hardware or
16041                software error.
16042 
16043      Action:   Follow normal recovery procedures.
16044 
16045 
16046                [page_error.alm]
16047                free_store:  Scavenger STACQ fails on dskX_NN{S}.
16048 
16049 
16050      Stream:   BOS Typewriter (Crashes system)
16051 
16052      Time:     During a physical volume scavenge of dskX_NN{S}.
16053 
16054      Meaning:  A  STACQ  instruction,  used  to  unlock  a record
16055                address during a volume  scavenge, did not operate
16056                correctly.   This  indicates  processor  or memory
16057                malfunction.
16058 
16059      Action:   Follow normal recovery procedures.
16060 
16061 
16062                [page_error.alm]
16063                free_store:  volmap_seg async error for dskX_NN{S}
16064 
16065 
16066      Stream:   BOS Typewriter (Crashes system)
16067 
16068      Time:     While system is running.
16069 
16070      Meaning:  When attempting to write a  page of the Volume Map
16071                to  dskX_NN{S}, the  page was  found not  to be in
16072                memory.  This probably indicates a software error.
16073 
16074      Action:   Follow normal recovery procedures.
16075 
16076 
16077 
16078 
16079 
16080 freecore                       278            08/03/23     MR12.7^L
16081 
16082 
16083 
16084 
16085                [freecore.pl1]
16086                freecore:  parity error in frame XXX of memory.
16087 
16088 
16089      Stream:   BOS Typewriter.
16090 
16091      Time:     System Intialization.
16092 
16093      Meaning:  A  memory parity error  has been detected  in page
16094                XXX of memory.  The page will not be put in use.
16095 
16096      Action:   No operator action is required.
16097 
16098 
16099                [fs_search.pl1]
16100                fs_search:  Fatal damage detected  to WHAT in ring
16101                RING for USER.
16102 
16103 
16104      Stream:   Logged in SYSERR log.
16105 
16106      Time:     While system is running.
16107 
16108      Meaning:  Some  object  crucial  to  the  operation  of  the
16109                dynamic linker in ring  RING was detected damaged.
16110                Since  the dynamic  linker cannot  operate in  the
16111                process, it is terminated.
16112 
16113      Action:   No operator action is required.
16114 
16115 
16116                [fsout_vol.pl1]
16117                fsout_vol:   Discarding old   dumper bit  maps for
16118                dskX_NNS.
16119 
16120 
16121      Stream:   BOS Typewriter.
16122 
16123      Time:     System shutdown and volume demounting.
16124 
16125      Meaning:  An  error  occurred  attempting  to  read the VTOC
16126                header from physical  volume on dskX_NNS.  Writing
16127                of the  dumper bit maps to disk  will be bypassed.
16128                The dumper  bit maps will be freed  and the system
16129                will attempt to continue,  however, the dumper bit
16130                maps may not be accurate on disk.
16131 
16132      Action:   Contact the system programming staff.
16133 
16134 
16135                [fsout_vol.pl1]
16136 
16137 
16138 fsout_vol                      279            08/03/23     MR12.7^L
16139 
16140 
16141                fsout_vol:  label  for PVNAME (dskX_NNS)  uid does
16142                not match pvt.
16143 
16144 
16145      Stream:   BOS Typewriter.
16146 
16147      Time:     System shutdown, volume mounting and demounting.
16148 
16149      Meaning:  The unique physical volume ID  in the label of the
16150                pack  on dskX_NNS  (PVNAME) does  not compare with
16151                the value it had when  the pack was first mounted.
16152                Damage to the pack has probably occurred.
16153 
16154      Action:   Attempt  to demount  the  volume  if this  has not
16155                already been  done.  Save the pack  for inspection
16156                and  dumping  by  the  system  programming  staff.
16157                Initiate volume recovery procedures.
16158 
16159 
16160 
16161                [fsout_vol.pl1]
16162                fsout_vol:   XXX volume inconsistenices  on PVNAME
16163                (dskX_NNS).   YYYYY  free   records.   ZZZZZ  free
16164                VTOCEs.
16165 
16166 
16167      Stream:   Logged only if the number  of free records and the
16168                number  of free  VTOCEs are  both above  threshold
16169                values.   Printed and  logged if  either is  below
16170                threshold.
16171 
16172      Time:     Volume demounting and system shutdown time.
16173 
16174      Meaning:  At some  time during the use of  volume PVNAME (on
16175                drive  dskX_NNS), the system  encountered problems
16176                which  left the  volume in  an inconsistent state.
16177                The  effect  of  this  is  that  some free records
16178                and/or free  VTOCEs are unavailable (lost)  to the
16179                system.  These inconsistencies can be corrected by
16180                a  volume salvage.   The number  of unused records
16181                and VTOCEs which are available for use is printed.
16182 
16183      Action:   If the  number of free  records or free  vtoces is
16184                low, a  physical volume salvage should  be done on
16185                the volume  prior to mounting it  again to recover
16186                the lost items.
16187 
16188 
16189 
16190                [fsout_vol.pl1]
16191                fsout_vol:   {REASON} Error  OPERATION OBJECT_TYPE
16192                for dskX_NNS {(PVNAME)}
16193 
16194 
16195 
16196 fsout_vol                      280            08/03/23     MR12.7^L
16197 
16198 
16199      Stream:   BOS Typewriter.
16200 
16201      Time:     System   shutdown   and    volume   mounting   and
16202                demounting.
16203 
16204      Meaning:  A   physical  device   error  has   occured  while
16205                attempting  to read   or write  (OPERATION) volume
16206                header  information  (OBJECT_TYPE)   of  the  pack
16207                (PVNAME) on dskX_NNS.
16208 
16209      Action:   If  this message  occurs at  volume mounting time,
16210                check  the drive   specified for  write-protect or
16211                standby status,  and retry the add_lv  command for
16212                the  logical volume.   If this  message occurs  at
16213                shutdown or  demount time, the volume  may contain
16214                inconsistencies   (lost  free   records  or   free
16215                VTOCEs).   These inconsistencies can  be corrected
16216                by a physical volume salvage.
16217 
16218 
16219 
16220                [ftp_dialup_.pl1]
16221                ftp_dialup_:    answer  table  damaged   at  UTEP,
16222                tra_vec=TTTT
16223 
16224 
16225      Stream:   as (severity 2)
16226 
16227      Time:     While system is running.
16228 
16229      Meaning:  The tra_vec  value was found to be  invalid for an
16230                answer table  wakeup.  Damage to the  answer table
16231                is indicated.
16232 
16233      Action:   Contact the system programming staff.
16234 
16235 
16236                [ftp_dialup_.pl1]
16237                ftp_dialup_:  called while ansp = null
16238 
16239 
16240      Stream:   as (severity 2)
16241 
16242      Time:     While system is running.
16243 
16244      Meaning:  A programming error in the Answering Service or an
16245                incorrect  library  installation  has  caused  the
16246                Answering  Service  to   be  called  before  being
16247                initialized.  The system will ignore the error and
16248                attempt to continue.
16249 
16250      Action:   Shut  down  the  system  and  perform  a  bootload
16251                operation.
16252 
16253 
16254 ftp_dialup_                    281            08/03/23     MR12.7^L
16255 
16256 
16257 
16258 
16259                [ftp_dialup_.pl1]
16260                ftp_dialup_:  called with bad ptr EVENT_MSG_PTR by
16261                WWWWWWWWWWWW
16262 
16263 
16264      Stream:   as (severity 2)
16265 
16266      Time:     While system is running.
16267 
16268      Meaning:  A   programming   error    in   the   interprocess
16269                communication system, the network software, or the
16270                Answering Service itself has occurred.  An invalid
16271                message pointer  has been passed to  the Answering
16272                Service.   The  system  ignores  the  message  and
16273                attempts  to continue.   This message  may be  the
16274                result of an incorrect library installation.
16275 
16276      Action:   Shut  down  the  system  and  perform  a  bootload
16277                operation.
16278 
16279 
16280                [ftp_dialup_.pl1]
16281                ftp_dialup_:  called with null message ptr
16282 
16283 
16284      Stream:   as (severity 2)
16285 
16286      Time:     While system is running.
16287 
16288      Meaning:  A   programming   error    in   the   interprocess
16289                communication system, the network software, or the
16290                Answering Service itself has occurred.  An invalid
16291                message pointer  has been passed to  the Answering
16292                Service.   The  system  ignores  the  message  and
16293                attempts  to continue.   This message  may be  the
16294                result of an incorrect library installation.
16295 
16296      Action:   Shut  down  the  system  and  perform  a  bootload
16297                operation.  Inform the system programming staff.
16298 
16299 
16300 
16301                [ftp_dialup_.pl1]
16302                ftp_dialup_:  CDT damaged at CDTEP, tra_vec=TTTT
16303 
16304 
16305      Stream:   as (severity 2)
16306 
16307      Time:     While system is running.
16308 
16309 
16310 
16311 
16312 ftp_dialup_                    282            08/03/23     MR12.7^L
16313 
16314 
16315      Meaning:  The tra_vec  value was found  to be invalid  for a
16316                channel wakeup.  Damage to the CDT is indicated.
16317 
16318      Action:   Contact the system programming staff.
16319 
16320 
16321                [ftp_dialup_.pl1]
16322                ftp_dialup_:  cdte CDTEP (CHANNEL)  state M in use
16323                N - notify system programmer",
16324 
16325 
16326      Stream:   as (severity 0)
16327 
16328      Time:     While system is running.
16329 
16330      Meaning:  This indicates a logic error in the supervisor, or
16331                CPU or memory hardware problems.
16332 
16333      Action:   Contact the system programming staff.
16334 
16335 
16336                [ftp_dialup_.pl1]
16337                ftp_dialup_:  cdtep  = null and ate.active  = DDDD
16338                for UTEP
16339 
16340 
16341      Stream:   as (severity 2)
16342 
16343      Time:     While system is running.
16344 
16345      Meaning:  This indicates a logic error in the supervisor, or
16346                CPU or memory hardware problems.
16347 
16348      Action:   Contact the system programming staff.
16349 
16350 
16351                [ftp_dialup_.pl1]
16352                ftp_dialup_:  ERROR_MESSAGE attempting to allocate
16353                a user table entry for CHANNEL
16354 
16355 
16356      Stream:   as (severity 1)
16357 
16358      Time:     While system is running.
16359 
16360      Meaning:  An  ERROR_MESSAGE  was  returned  from  a  call to
16361                asu_$attach_ate  which  allocates   a  user  table
16362                entry.
16363 
16364      Action:   Contact the system programming staff.
16365 
16366 
16367                [ftp_dialup_.pl1]
16368 
16369 
16370 ftp_dialup_                    283            08/03/23     MR12.7^L
16371 
16372 
16373                ftp_dialup_:      ERROR_MESSAGE    new_proc     of
16374                PERSON.PROJECT denied by channel AIM restriction.
16375 
16376 
16377      Stream:   as (severity 0)
16378 
16379      Time:     While system is running.
16380 
16381      Meaning:  A user attempted to issue a new_proc an specify an
16382                AIM  authorization  which  is  not  allowed by the
16383                terminal channel in use.
16384 
16385      Action:   No operator action is required.
16386 
16387 
16388                [ftp_dialup_.pl1]
16389                ftp_dialup_:  ERROR_MESSAGE occurred attempting to
16390                declare handler for ev  chn EVENT_CHN for ate UTEP
16391                for CDT_CHANNEL
16392 
16393 
16394      Stream:   as (severity 2)
16395 
16396      Time:     While system is running.
16397 
16398      Meaning:  An ERROR_MESSAGE was returned  when an attempt was
16399                made  to declare  an  event  call channel  for new
16400                process   (UTEP)   on    EVENT_CHN   attached   to
16401                CDT_CHANNEL.
16402 
16403      Action:   Contact the system programming staff.
16404 
16405 
16406                [ftp_dialup_.pl1]
16407                ftp_dialup_:     ERROR_MESSAGE   tty_dim    error,
16408                removing channel CHANNEL COMMENT
16409 
16410 
16411      Stream:   as (severity 2)
16412 
16413      Time:     While system is running.
16414 
16415      Meaning:  An   ERROR_MESSAGE  caused   the  CHANNEL   to  be
16416                unusable.   The  CHANNEL   with  COMMENT  will  be
16417                removed from service.
16418 
16419      Action:   You may try to attach the channel.  If that fails,
16420                notify the system programmers.   If the channel is
16421                to be left detached, busy out the modem.
16422 
16423 
16424 
16425                [ftp_dialup_.pl1]
16426 
16427 
16428 ftp_dialup_                    284            08/03/23     MR12.7^L
16429 
16430 
16431                ftp_dialup_:  ERROR_MESSAGE  when creating process
16432                for PERSON.PROJECT
16433 
16434 
16435      Stream:   as (severity 2)
16436 
16437      Time:     While system is running.
16438 
16439      Meaning:  An ERROR_MESSAGE  was returned and the  system was
16440                unable    to   create    a   user    process   for
16441                PERSON.PROJECT.
16442 
16443      Action:   If possible, get in touch  with the user.  (He got
16444                a message  to contact you.)  Ask him  to try again
16445                and to tell you of any peculiarities of his login.
16446                Note all  particulars and contact  the programming
16447                staff.
16448 
16449 
16450 
16451                [ftp_dialup_.pl1]
16452                ftp_dialup_:  fatal error  during process creation
16453                for PERSON.PROJECT CHANNEL
16454 
16455 
16456      Stream:   as (severity 1)
16457 
16458      Time:     While system is running.
16459 
16460      Meaning:  A fatal error occurred during process creation for
16461                PERSON.PROJECT  on CHANNEL.    Reason is  given in
16462                previous  log entry.   This may  be due  to a user
16463                error:   incorrect  segments  in  the  user's home
16464                directory  or bad  login arguments  can cause this
16465                problem.
16466 
16467      Action:   No operator action is required.
16468 
16469 
16470                [ftp_dialup_.pl1]
16471                ftp_dialup_:  ignored SSSS from PERSON.PROJECT for
16472                CHANNEL state=DDDD,inuse=UUUU,tv=TTTT
16473 
16474 
16475      Stream:   as (severity 2)
16476 
16477      Time:     While system is running.
16478 
16479      Meaning:  A  spurious signal  SSSS from  user PERSON.PROJECT
16480                has arrived for CHANNEL.  The state of the channel
16481                is DDD, inuse is UUUU and tra_vec is TTTT.
16482 
16483 
16484 
16485 
16486 ftp_dialup_                    285            08/03/23     MR12.7^L
16487 
16488 
16489      Action:   This  may  be  some  user  trying  to  disrupt the
16490                system.  Do a who and  save it for the programming
16491                staff.
16492 
16493 
16494 
16495                [ftp_dialup_.pl1]
16496                ftp_dialup_:    non-null  atep  (UTEP)   for  cdte
16497                (CDTEP,CHANNEL), tv=TRAVEC,inuse=INUSE
16498 
16499 
16500      Stream:   as (severity 0)
16501 
16502      Time:     While system is running.
16503 
16504      Meaning:  A  wakeup occurred  for CHANNEL  whose user  table
16505                entry pointer (UTEP) was  non-null.  A test on the
16506                above information determined that the state of the
16507                channel to be inconsistant.   The system will null
16508                the UTEP pointer in the CDT for the above channel.
16509 
16510      Action:   Contact the system programming staff.
16511 
16512 
16513                [ftp_dialup_.pl1]
16514                ftp_dialup_:       premature     stopstop      for
16515                PERSON.PROJECT CHANNEL
16516 
16517 
16518      Stream:   as (severity 0)
16519 
16520      Time:     While system is running.
16521 
16522      Meaning:  This indicates a logic error in the supervisor, or
16523                CPU or memory hardware problems.
16524 
16525      Action:   Contact the system programming staff.
16526 
16527 
16528                [ftp_dialup_.pl1]
16529                ftp_dialup_:  process did  not respond properly to
16530                trm_ signal.  PERSON.PROJECT CHANNEL
16531 
16532 
16533      Stream:   as (severity 0)
16534 
16535      Time:     While system is running.
16536 
16537      Meaning:  The  PERSON.PROJECT process  on CHANNEL  was being
16538                terminated and  had been sent the  trm_ signal but
16539                it did not respond.   User process will be bumped,
16540                logged out or new_proced.  It is possible that the
16541                user can cause this message.
16542 
16543 
16544 ftp_dialup_                    286            08/03/23     MR12.7^L
16545 
16546 
16547      Action:   No operator action is required.
16548 
16549 
16550                [ftp_dialup_.pl1]
16551                ftp_dialup_:    process    ignored   term   signal
16552                PERSON.PROJECT CHANNEL
16553 
16554 
16555      Stream:   as (severity 1)
16556 
16557      Time:     While system is running.
16558 
16559      Meaning:  The  PERSON.PROJECT process   on CHANNEL  had been
16560                sent a trm_ signal but the process did not respond
16561                to  it.   The  process  will  be  handled  as  was
16562                intended to be; bumped, logged out, etc.
16563 
16564      Action:   No operator action is required.
16565 
16566 
16567                [ftp_dialup_.pl1]
16568                ftp_dialup_:   process  terminated  PERSON.PROJECT
16569                CHANNEL TERM_MESSAGE
16570 
16571 
16572      Stream:   as (severity 0)
16573 
16574      Time:     While system is running.
16575 
16576      Meaning:  The  process  for  PERSON.PROJECT  on  CHANNEL was
16577                terminated    abnormally   due   to    reason   in
16578                TERM_MESSAGE.
16579 
16580      Action:   No operator action is required.
16581 
16582 
16583                [ftp_dialup_.pl1]
16584                ftp_dialup_:   Program  error:    null  atep  with
16585                per-process tra_vec value
16586 
16587 
16588      Stream:   as (severity 2)
16589 
16590      Time:     While system is running.
16591 
16592      Meaning:  A  system  programming   error  in  the  answering
16593                service  has occurred  as a  wakeup occurred  when
16594                tra_vec indicated to  expect a process termination
16595                but the ate pointer was null.
16596 
16597      Action:   Contact the system programming staff.
16598 
16599 
16600 
16601 
16602 ftp_dialup_                    287            08/03/23     MR12.7^L
16603 
16604 
16605                [ftp_dialup_.pl1]
16606                ftp_dialup_:   Program  error:   null  cdtep  with
16607                per-channel tra_vec value
16608 
16609 
16610      Stream:   as (severity 2)
16611 
16612      Time:     While system is running.
16613 
16614      Meaning:  A  wakeup  was  received  when  the  tra_vec value
16615                indicated a channel operation was required but the
16616                cdtep  was  null.   This  is  considered  to  be a
16617                programming error.
16618 
16619      Action:   Contact the system programming staff.
16620 
16621 
16622                [ftp_dialup_.pl1]
16623                ftp_dialup_:   Program error:   per-process wakeup
16624                with per-channel-only tra_vec value
16625 
16626 
16627      Stream:   as (severity 2)
16628 
16629      Time:     While system is running.
16630 
16631      Meaning:  A process  wakeup occurred when the  tra_vec value
16632                indicated it should be  a channel wakeup.  This is
16633                considered a programing error.
16634 
16635      Action:   Contact the system programming staff.
16636 
16637 
16638                [ftp_dialup_.pl1]
16639                ftp_dialup_:  re-used cdte  (CDTEP,CHANNEL) by ate
16640                UTEP, destroy_flag=DDDD
16641 
16642 
16643      Stream:   as (severity 0)
16644 
16645      Time:     While system is running.
16646 
16647      Meaning:  An  ate wakeup occurred  which pointed to  a CDTEP
16648                that was already in use by another process.
16649 
16650      Action:   Contact the system programming staff.
16651 
16652 
16653                [ftp_dialup_.pl1]
16654                ftp_dialup_:  re-used cdte  (CDTEP,CHANNEL) by ate
16655                UTEP, destroy_flag=DDDD
16656 
16657 
16658 
16659 
16660 ftp_dialup_                    288            08/03/23     MR12.7^L
16661 
16662 
16663      Stream:   as (severity 0)
16664 
16665      Time:     While system is running.
16666 
16667      Meaning:  An  ate wakeup occurred  which pointed to  a CDTEP
16668                that was already in use by another process.
16669 
16670      Action:   Contact the system programming staff.
16671 
16672 
16673                [ftp_dialup_.pl1]
16674                ftp_dialup_:  terminating fatal process error loop
16675                for PERSON.PROJECT CHANNEL
16676 
16677 
16678      Stream:   as (severity 1)
16679 
16680      Time:     While system is running.
16681 
16682      Meaning:  The  process  for  PERSON.PROJECT  on  CHANNEL has
16683                taken  too  many  fatal  process  errors.  This is
16684                governed    by     fatal_error_loop_seconds    and
16685                fatal_error_loop_count in  the installation_parms.
16686                The user will not get  a new process.  The channel
16687                will  not  be  hungup   but  will  get  a  message
16688                indicating  this condition.   This message  may be
16689                due to a user error.
16690 
16691      Action:   No operator action is required.
16692 
16693 
16694                [ftp_dialup_.pl1]
16695                ftp_dialup_:   The  answer   table  is  full  (MAX
16696                entries).
16697 
16698 
16699      Stream:   as (severity 1)
16700 
16701      Time:     While system is running.
16702 
16703      Meaning:  The  system  answer  table  is  full  and  has MAX
16704                entries.  No more users will be able to login.
16705 
16706      Action:   Contact the system programming staff.
16707 
16708 
16709                [ftp_dialup_.pl1]
16710                ftp_dialup_:    trace   event   CHANNEL   FFFFFFFF
16711                WWWWWWWWWWWW RRRRRRDDDDDD SS XXXX st N wp M
16712 
16713 
16714      Stream:   as (severity 1)
16715 
16716 
16717 
16718 ftp_dialup_                    289            08/03/23     MR12.7^L
16719 
16720 
16721      Time:     While system is running.
16722 
16723      Meaning:  This       is       trace       output.       When
16724                ftp_dialup_$ftp_dial_loud    is   called,    these
16725                messages   are  printed   out  for   every  signal
16726                concerning  a  device  channel.   FFFFFFFF  is the
16727                function  being  performed.   WWWWWWWWWWWW  is the
16728                sending process ID.  RRRRRR  is the ring origin of
16729                the   signal.   DDDDDD    is  the   device  signal
16730                information.   The  pointer  SS  XXXX  locates the
16731                answer table entry for CHANNEL.  The channel state
16732                is N and the wait point (transaction vector) is M.
16733 
16734      Action:   No  operator action  is required.   To turn  these
16735                messages off, type ftp_dialup_$ftp_dial_soft while
16736                in admin mode.
16737 
16738 
16739 
16740                [ftp_dialup_.pl1]
16741                ftp_dialup_:   turning off  disconnected flag  for
16742                ate UTEP, cdte CDTEP,CHANNEL
16743 
16744 
16745      Stream:   as (severity 0)
16746 
16747      Time:     While system is running.
16748 
16749      Meaning:  If processing an ate  wakeup, the CHANNEL is known
16750                and the process  is disconnected, the disconnected
16751                flag for the ate will be turned off.
16752 
16753      Action:   Contact the system programming staff.
16754 
16755 
16756                [ftp_dialup_.pl1]
16757                ftp_dialup_:  Unable to determine initial terminal
16758                type for channel CHANNEL
16759 
16760 
16761      Stream:   as (severity 2)
16762 
16763      Time:     While system is running.
16764 
16765      Meaning:  Unable  to  determine  the  default  terminal type
16766                based  on  line-type/baud-rate  in  the  TTT.  The
16767                channel has been removed from known channels.
16768 
16769      Action:   Contact the system programming staff.
16770 
16771 
16772                [ftp_dialup_.pl1]
16773 
16774 
16775 
16776 ftp_dialup_                    290            08/03/23     MR12.7^L
16777 
16778 
16779                ftp_dialup_:   unexpected state  SSSS for  channel
16780                definition table at CDTEP
16781 
16782 
16783      Stream:   as (severity 2)
16784 
16785      Time:     While system is running.
16786 
16787      Meaning:  This indicates a logic error in the supervisor, or
16788                CPU or memory hardware problems.
16789 
16790      Action:   Contact the system programming staff.
16791 
16792 
16793                [ftp_dialup_.pl1]
16794                ftp_dialup_:      Unexpected      termsgnl     for
16795                PERSON.PROJECT CHANNEL (preempted=DDDD).
16796 
16797 
16798      Stream:   as (severity 0)
16799 
16800      Time:     While system is running.
16801 
16802      Meaning:  A   "termsgnl"  wakeup    was  received   for  the
16803                PERSON.PROJECT    process    on    CHANNEL   whose
16804                ute.preempted value DDDD did  not indicate one was
16805                allowed.   This  is  considered  to  be  a program
16806                error.  User will be given a new process.
16807 
16808      Action:   Contact the system programming staff.
16809 
16810 
16811                [ftp_dialup_.pl1]
16812                ftp_dialup_:    wrong    answerback   on   CHANNEL
16813                (COMMENT); expected "ID1", got "ID2".
16814 
16815 
16816      Stream:   as (severity 2)
16817 
16818      Time:     While system is running.
16819 
16820      Meaning:  A terminal attempted to  connect on CHANNEL (whose
16821                CDT  comment is COMMENT)  that is restricted  to a
16822                specific  answerback   and  did  not   return  the
16823                expected value.   ID1 is the  answerback expected;
16824                ID2  is  the  answerback  actually  received.  The
16825                terminal is hung up.
16826 
16827      Action:   No operator action is required.
16828 
16829 
16830                [get_aste.pl1]
16831 
16832 
16833 
16834 get_aste                       291            08/03/23     MR12.7^L
16835 
16836 
16837                get_aste:  Error deactivating UUUU  (vtoc V of pvt
16838                PV) to free XXXk ASTE for USERNAME.
16839 
16840 
16841      Stream:   Logged in SYSERR log.
16842 
16843      Time:     While system is running.
16844 
16845      Meaning:  The  system encountered  an error  deactivating an
16846                AST entry  which was selected for  deactivation by
16847                the AST  replacement algorithm.  The AST  on which
16848                the  error was encountered  will be flagged  to be
16849                ingored by  further passes of the  algorithm; this
16850                flag  will  be  reset   during  the  next  run  of
16851                flush_ast_pool.
16852 
16853      Action:   If  the  problem   persists,  contact  the  system
16854                programming staff.
16855 
16856 
16857                [get_aste.pl1]
16858                get_aste:  Invalid csl x
16859 
16860 
16861      Stream:   Logged in SYSERR log.
16862 
16863      Time:     While system is running.
16864 
16865      Meaning:  get_aste was  called to activate a  segment with x
16866                pages,  which is  larger than  the maximum segment
16867                size.  This is indicative  of hardware or software
16868                failure (a typical problem is an invalid VTOCE).
16869 
16870      Action:   If  the  problem   persists,  contact  the  system
16871                programming staff.
16872 
16873 
16874                [get_aste.pl1]
16875                get_aste:  no removable XXXk ast entries
16876 
16877 
16878      Stream:   BOS Typewriter.
16879 
16880      Time:     While system is running.
16881 
16882      Meaning:  An AST entry was needed  for a segment of size XXX
16883                k, but no free entries  of that size were present,
16884                and  no segments  occupying such  entries could be
16885                deactivated.  This could be symptomatic of a logic
16886                problem, but may also  indicate a grossly mistuned
16887                AST.
16888 
16889 
16890 
16891 
16892 get_aste                       292            08/03/23     MR12.7^L
16893 
16894 
16895      Action:
16896                Substantially increase  the number of  AST entries
16897                of this size as given  on the SST CONFIG card.  If
16898                the   problem   persists,   contact   the   system
16899                programming staff.
16900 
16901 
16902 
16903                [get_aste.pl1]
16904                get_aste:   no  removable  XXXk  synchronized  AST
16905                entries
16906 
16907 
16908      Stream:   Logged in SYSERR log.
16909 
16910      Time:     While system is running.
16911 
16912      Meaning:  An AST entry was needed for a synchronized segment
16913                of  size XXX  k,  and  the per-ASTE-pool  limit on
16914                synchronized    segments    was    reached.     No
16915                synchronized  segments  in   that  pool  could  be
16916                deactivated.
16917 
16918      Action:   Contact the system programming staff.
16919 
16920 
16921                [get_io_segs.pl1]
16922                get_io_segs:   DSKQ  mmm.    <  xxx.   per  drive,
16923                forcing DSKQ nnn.
16924 
16925 
16926      Stream:   BOS Typewriter (sounds beeper)
16927 
16928      Time:     System Intialization.
16929 
16930      Meaning:  The dskq card specifies  less than 5 queue entries
16931                per configured drive.  This  is considered too few
16932                for efficient operation and is forced to 5 entries
16933                per drive.
16934 
16935      Action:   $config
16936 
16937 
16938                [get_io_segs.pl1]
16939                get_io_segs:   DSKQ  mmm.    >  xxx.   per  drive,
16940                forcing DSKQ nnn.
16941 
16942 
16943      Stream:   BOS Typewriter (sounds beeper)
16944 
16945      Time:     System Intialization.
16946 
16947 
16948 
16949 
16950 get_io_segs                    293            08/03/23     MR12.7^L
16951 
16952 
16953      Meaning:  The dskq card specifies an excess of queue entries
16954                beyond  that  reasonably  required  for  efficient
16955                operation.  The free queue  will be limited to 100
16956                entries per drive.
16957 
16958      Action:   $config
16959 
16960 
16961                [get_io_segs.pl1]
16962                get_io_segs:  Missing ndrives field on config card
16963                prph NAME.
16964 
16965 
16966      Stream:   BOS Typewriter (Crashes system)
16967 
16968      Time:     System Intialization.
16969 
16970      Meaning:  The prph card for the NAME subsystem is missing an
16971                ndrives field.
16972 
16973      Action:   $config
16974 
16975 
16976                [get_main.pl1]
16977                get_main:  insufficient storage available for NAME
16978 
16979 
16980      Stream:   BOS Typewriter (Crashes system)
16981 
16982      Time:     System Intialization.
16983 
16984      Meaning:  Insufficient wired memory  was available to create
16985                the  segment  NAME   during  initialization.   The
16986                system tape  may be bad, or  the configuration may
16987                be too  small, or the system  parameters specified
16988                in  the  configuration  deck  may  be incorrect or
16989                inconsistent  with  the  amount  of  main  storage
16990                available.
16991 
16992      Action:   Follow  normal  recovery  procedures.   Check  the
16993                configuration and the CONFIG deck.  $boot_tape
16994 
16995 
16996 
16997                [get_main.pl1]
16998                get_main:   not enough   room to  allocate unpaged
16999                page table for NAME.
17000 
17001 
17002      Stream:   BOS Typewriter (Crashes system)
17003 
17004      Time:     System Intialization.
17005 
17006 
17007 
17008 get_main                       294            08/03/23     MR12.7^L
17009 
17010 
17011      Meaning:  Either   the    segment   unpaged_page_tables   or
17012                int_unpaged_page_tables was  not big enough  so as
17013                to have the page  table for segment NAME allocated
17014                within it.  The system tape may be bad, or changes
17015                made  to  the  mst  require  bigger  unpaged  page
17016                tables.
17017 
17018      Action:   Follow  normal recovery  procedures.  Try  another
17019                tape.  If bigger unpaged page tables are in order,
17020                a  change must  be made  to bootload_equs.incl.alm
17021                and collection 0 recompiled.  $boot_tape
17022 
17023 
17024 
17025                [get_pvtx.pl1]
17026                get_pvtx$cleanup:  Force released  hold on pvtx ^d
17027                for USER_ID.
17028 
17029 
17030      Stream:   BOS Typewriter.
17031 
17032      Time:     While system is running.
17033 
17034      Meaning:  This indicates a logic error in the supervisor, or
17035                CPU or memory hardware  problems.  A condition was
17036                signalled  in  ring-0  which  caused  a  crawlout.
17037                get_pvtx$cleanup will release all PV holds for the
17038                process.
17039 
17040      Action:   Contact the system programming staff.
17041 
17042 
17043                [get_pvtx.pl1]
17044                get_pvtx:     drain_pvtx:     pvte.being_demounted
17045                should be on.
17046 
17047 
17048      Stream:   BOS Typewriter (Crashes system)
17049 
17050      Time:     While system is running.
17051 
17052      Meaning:  The   entry  to    the  physical   volume  demount
17053                protection mechanism  which awaits all use  of the
17054                volume  to cease  is being  called improperly.   A
17055                necessary  precondition for  its proper  operation
17056                (pvte.being_demounted) is not met.  This indicates
17057                a logic error in the  supervisor, or CPU or memory
17058                hardware problems.
17059 
17060      Action:   Follow normal recovery procedures.
17061 
17062 
17063 
17064 
17065 
17066 get_pvtx                       295            08/03/23     MR12.7^L
17067 
17068 
17069 
17070 
17071                [get_pvtx.pl1]
17072                get_pvtx:  hold_pvtx finds table full
17073 
17074 
17075      Stream:   BOS Typewriter (Crashes system)
17076 
17077      Time:     While system is running.
17078 
17079      Meaning:  There are  no free entries in  the physical volume
17080                hold table.  There should never be more than twice
17081                the number of eligible  processes of used entries.
17082                This indicates a logic error in the supervisor, or
17083                CPU or memory hardware problems.
17084 
17085      Action:   Follow normal recovery procedures.
17086 
17087 
17088                [get_pvtx.pl1]
17089                get_pvtx:  release_pvtx:  mark not found
17090 
17091 
17092      Stream:   BOS Typewriter (Crashes system)
17093 
17094      Time:     While system is running.
17095 
17096      Meaning:  While attempting to release a physical volume from
17097                demount   protection,  the    mark  made   by  the
17098                protection  could  not  be  found  in the physical
17099                volume hold table.  This message can also occur if
17100                somehow the physical volume was demounted in spite
17101                of this  protection, or this entry  point is being
17102                used improperly.  This indicates  a logic error in
17103                the   supervisor,  or   CPU  or   memory  hardware
17104                problems.
17105 
17106      Action:   Follow normal recovery procedures.
17107 
17108 
17109                [get_pvtx.pl1]
17110                get_pvtx:  ZERO_ENTRY fails
17111 
17112 
17113      Stream:   BOS Typewriter (Crashes system)
17114 
17115      Time:     While system is running.
17116 
17117      Meaning:  The STACQ instruction has failed to clear an entry
17118                in the physical volume hold table.  This indicates
17119                a logic error in the  supervisor, or CPU or memory
17120                hardware problems.
17121 
17122 
17123 
17124 get_pvtx                       296            08/03/23     MR12.7^L
17125 
17126 
17127      Action:   Follow normal recovery procedures.
17128 
17129 
17130                [grab_aste.pl1]
17131                grab_aste:  Attempt to reuse segno SSS
17132 
17133 
17134      Stream:   BOS Typewriter (Crashes system)
17135 
17136      Time:     While system is running.
17137 
17138      Meaning:  A  call has  been made  to force  active a segment
17139                already   forced   active.    This   indicates  an
17140                inconsistency   in   the    programming   of   the
17141                supervisor.  This  indicates a logic error  in the
17142                supervisor, or CPU or memory hardware problems.
17143 
17144      Action:   Follow  normal recovery  procedures.  Contact  the
17145                system programming staff.
17146 
17147 
17148 
17149                [grab_aste.pl1]
17150                grab_aste:  failed to reactivate PPPP ERRORMESSAGE
17151 
17152 
17153      Stream:   BOS Typewriter (Crashes system)
17154 
17155      Time:     While system is running.
17156 
17157      Meaning:  This indicates a logic error in the supervisor, or
17158                CPU or memory hardware problems.
17159 
17160      Action:   Follow  normal recovery  procedures.  Contact  the
17161                system programming staff.
17162 
17163 
17164 
17165                [grab_aste.pl1]
17166                grab_aste:  Unprotected segment:  astep = AAA
17167 
17168 
17169      Stream:   BOS Typewriter (Crashes system)
17170 
17171      Time:     While system is running.
17172 
17173      Meaning:  An  attempt  was  made   to  release  from  forced
17174                activity  a segment  (whose AST  entry is  at AAA)
17175                which was not even in  a state of forced activity.
17176                This indicates a logic error in the supervisor, or
17177                CPU or memory hardware problems.
17178 
17179 
17180 
17181 
17182 grab_aste                      297            08/03/23     MR12.7^L
17183 
17184 
17185      Action:   Contact  the  system  programming  staff.   Follow
17186                normal recovery procedures.
17187 
17188 
17189 
17190                [bootload_error.alm]
17191                HALT with octal 5's in the upper half of the AQ.
17192 
17193 
17194      Stream:   BOS Typewriter (Crashes system)
17195 
17196      Time:     System Intialization.
17197 
17198      Meaning:  The  collection zero   call stack  has overflowed.
17199                This  indicates a  logic error  in the  collection
17200                zero supervisor,  or a hardware  problem (possibly
17201                with id or di modifiers).
17202 
17203      Action:   Try another tape, and/or look for a CPU bug.
17204 
17205 
17206                [bootload_error.alm]
17207                HALT with octal 6's in the upper half of the AQ.
17208 
17209 
17210      Stream:   BOS Typewriter (Crashes system)
17211 
17212      Time:     System Intialization.
17213 
17214      Meaning:  A recursive error condition was encountered:  that
17215                is, the  collection zero error handler  was called
17216                recursively.  The  low half of the  A contains the
17217                unique error  number of the recursive  error.  See
17218                the   listing  of  bootload_error.alm   for  error
17219                numbers.  bootload_error$disaster_AQ  contains the
17220                AQ at the time of recursive entry.
17221 
17222      Action:   This error  indicates a logic error  or a hardware
17223                problem.  Use  execute switches to return  to BOS.
17224                Try  a different tape.   Failing that, look  for a
17225                CPU problem.
17226 
17227 
17228 
17229                [bootload_io.alm]
17230                HALT with octal 777777000001 in the A register.
17231 
17232 
17233      Stream:   BOS Typewriter (Crashes system)
17234 
17235      Time:     System Intialization.
17236 
17237 
17238 
17239 
17240 HALT                           298            08/03/23     MR12.7^L
17241 
17242 
17243      Meaning:  The interrupt base set on  the bootload IOM is not
17244                1200 octal.
17245 
17246      Action:   Set the switches correctly.
17247 
17248 
17249                [bootload_io.alm]
17250                HALT with octal 777777000002 in the A register.
17251 
17252 
17253      Stream:   BOS Typewriter (Crashes system)
17254 
17255      Time:     System Intialization.
17256 
17257      Meaning:  The  iom  base  set  on  the  bootload  IOM is not
17258                correct.  I.e., for IOM's 0,  1, 2 and 3 it should
17259                be 1400, 2000, 2400 and 3000 octal respectively.
17260 
17261      Action:   Set the switches correctly.
17262 
17263 
17264                [bootload_tape_label.alm.1]
17265                HALT with only the first MST tape record read.
17266 
17267 
17268 
17269      Stream:   BOS Typewriter (Crashes system)
17270 
17271      Time:     System Intialization.
17272 
17273      Meaning:  If the  high-order bit of  the AQ register  is on,
17274                the pattern in the AQ register is the (bad) status
17275                returned by  the IOM while reading  a tape record.
17276                If the  high order bit  is not on,  the A register
17277                contains the  flags word from a  MST header record
17278                indicating that this record is bad.
17279 
17280      Action:   Try  booting  on  a  different  drive  or  with  a
17281                different tape.
17282 
17283 
17284                [bootload_tape_label.alm]
17285                HALT with only the first MST tape record read.
17286 
17287 
17288 
17289      Stream:   BOS Typewriter (Crashes system)
17290 
17291      Time:     System Intialization.
17292 
17293      Meaning:  If the  high-order bit of  the AQ register  is on,
17294                the pattern in the AQ register is the (bad) status
17295                returned by  the IOM while reading  a tape record.
17296 
17297 
17298 HALT                           299            08/03/23     MR12.7^L
17299 
17300 
17301                If the  high order bit  is not on,  the A register
17302                contains the  flags word from a  MST header record
17303                indicating that this record is bad.
17304 
17305      Action:   Try  booting  on  a  different  drive  or  with  a
17306                different tape.
17307 
17308 
17309                [hardware_fault.pl1]
17310                hardware_fault:  Deleting frame at  WWW from SCU X
17311                due to parity errors
17312 
17313 
17314      Stream:   BOS Typewriter (sounds beeper)
17315 
17316      Time:     While system is running.
17317 
17318      Meaning:  A  parity  error  was  detected  at  main  storage
17319                address  WWWW.   The  main  memory  frame with the
17320                error was  removed from service via  delmain.  The
17321                user process encountering  the parity fault cannot
17322                be  restarted at  the point  of error  because the
17323                processor state is imprecise.  If the parity error
17324                could have  damaged user data, the  damaged switch
17325                is set on  the segment, and the user  is given the
17326                best version we can come up with for the page.
17327 
17328      Action:   Contact  Field Engineering personnel.   The memory
17329                page will  remain out of service  until added back
17330                by addmain.
17331 
17332 
17333 
17334                [hardware_fault.pl1]
17335                hardware_fault:   FFF  fault   on  CPU  CPUTAG  by
17336                PROCESSNAME.
17337 
17338 
17339      Stream:   BOS Typewriter.
17340 
17341      Time:     While system is running.
17342 
17343      Meaning:  A  fault  indicating   processor  or  main  memory
17344                malfunction  has occurred  on CPU  CPUTAG.  FFF is
17345                the name of the fault.  Complete binary data about
17346                the fault is logged for automatic processing.
17347 
17348      Action:   Contact Field engineering personnel.
17349 
17350 
17351                [hasp_mpx.pl1]
17352                hasp_mpx (line  TTY):  Bad block line  status from
17353                FNP; line will be hungup.
17354 
17355 
17356 hasp_mpx (line TTY)            300            08/03/23     MR12.7^L
17357 
17358 
17359      Stream:   Note for system programmer action.
17360 
17361      Time:     While system is running.
17362 
17363      Meaning:  A  block  generated  by  the  HASP  multiplexer on
17364                channel TTY  for transmission was  malformed.  The
17365                connection  to  the   remote  host/workstation  is
17366                broken  as  communications  cannot  continue under
17367                these conditions.
17368 
17369      Action:   Contact the system programming staff.
17370 
17371 
17372                [hasp_mpx.pl1]
17373                hasp_mpx  (line  TTY):    Block  received  out  of
17374                sequence:  expected  = N, recevied =  M; line will
17375                be hungup.
17376 
17377 
17378      Stream:   Note for system programmer action.
17379 
17380      Time:     While system is running.
17381 
17382      Meaning:  One   or  more   data  blocks   from  the   remote
17383                host/workstation  for  the   HASP  multiplexer  on
17384                channel  TTY  were  lost.   The  connection to the
17385                remote     host/workstation    is     broken    as
17386                communications   cannot   continue   under   these
17387                conditions.
17388 
17389      Action:   There  are two  possible causes  for this message:
17390                communications  equipment failures or  problems in
17391                the remote host/workstation  itself.  The operator
17392                should  contact the  appropriate personnel  before
17393                reusing the multiplexer.
17394 
17395 
17396 
17397                [hasp_mpx.pl1]
17398                hasp_mpx  (line  TTY):    Block  recevied  out  of
17399                sequence:   expected  =  N,  received  =  M; block
17400                ignored.
17401 
17402 
17403      Stream:   Logged in SYSERR log.
17404 
17405      Time:     While system is running.
17406 
17407      Meaning:  A  duplicate data block  was received by  the HASP
17408                multiplexer  on  channel   TTY  from  the  foreign
17409                host/workstation.
17410 
17411 
17412 
17413 
17414 hasp_mpx (line TTY)            301            08/03/23     MR12.7^L
17415 
17416 
17417      Action:   The operator should ignore  this message unless it
17418                occurs  quite frequently.  Frequent  occurences of
17419                this  message indicate   possible problems  in the
17420                communications    equipment   which    should   be
17421                investigated by the appropriate personnel.
17422 
17423 
17424 
17425                [hasp_mpx.pl1]
17426                hasp_mpx  (line TTY):    Block transmitted  out of
17427                sequence:  expected  = N, received =  M; line will
17428                be hungup.
17429 
17430 
17431      Stream:   Note for system programmer action.
17432 
17433      Time:     While system is running.
17434 
17435      Meaning:  One  or more data  blocks transmitted by  the HASP
17436                multiplexer  on channel  TTY were  not received by
17437                the  remote host/workstation.   The connection  to
17438                the   remote   host/workstation   is   broken   as
17439                communications   cannot   continue   under   these
17440                conditions.
17441 
17442      Action:   Contact  the system  programming staff.   The HASP
17443                software  is designed   to prevent  this situation
17444                even  if  the   communications  equipment  is  not
17445                functioning properly.
17446 
17447 
17448 
17449                [hasp_mpx.pl1]
17450                hasp_mpx  (line  TTY):   Duplicate  loopback block
17451                received:  BCB = NNN
17452 
17453 
17454      Stream:   Note for system programmer action.
17455 
17456      Time:     While system is running.
17457 
17458      Meaning:  The output  block identified by the  3-digit octal
17459                sequence NNN was returned  to Multics twice by the
17460                FNP for reprocessing.
17461 
17462      Action:   Contact the system programming staff.
17463 
17464 
17465                [hasp_mpx.pl1]
17466                hasp_mpx   (line   TTY):    Invalid   input  block
17467                header/trailer; line will be hungup.
17468 
17469 
17470 
17471 
17472 hasp_mpx (line TTY)            302            08/03/23     MR12.7^L
17473 
17474 
17475      Stream:   Note for system programmer action.
17476 
17477      Time:     While system is running.
17478 
17479      Meaning:  A data block whose format  does not conform to the
17480                HASP  protocol   was  received  from   the  remote
17481                host/workstation   by  the  HASP   multiplexer  on
17482                channel  TTY.    The  connection  to   the  remote
17483                host/workstation   is  broken   as  communications
17484                cannot continue under these conditions.
17485 
17486      Action:   Frequent occurences of  this message indicate that
17487                hardware  or software  problems may  exist in  the
17488                remote  host/workstation.    The  operator  should
17489                contact  the appropriate personnel  before reusing
17490                the multiplexer.
17491 
17492 
17493 
17494                [hasp_mpx.pl1]
17495                hasp_mpx  (line  TTY):    No  space  available  to
17496                preserve minor state; line will be hungup.
17497 
17498 
17499      Stream:   BOS Typewriter.
17500 
17501      Meaning:  Insufficient  space was   available in  tty_buf to
17502                perform part  of the critical input  processing of
17503                the   HASP  multiplexer   on  channel   TTY.   The
17504                connection  to  the   remote  host/workstation  is
17505                broken  as  communications  cannot  continue under
17506                these conditions.
17507 
17508      Action:   Contact the  system programming staff.  It  may be
17509                necessary  to  increase  the  size  of  tty_buf as
17510                specified  on the  PARM config  card before  using
17511                this multiplexer again.
17512 
17513 
17514 
17515                [hasp_mpx.pl1]
17516                hasp_mpx (line  TTY):  No space available  to save
17517                loopback chain; line will be hungup.
17518 
17519 
17520      Stream:   BOS Typewriter.
17521 
17522      Meaning:  Insufficient  space was   available in  tty_buf to
17523                perform part  of the critical input  processing of
17524                the   HASP  multiplexer   on  channel   TTY.   The
17525                connection  to  the   remote  host/workstation  is
17526                broken  as  communications  cannot  continue under
17527                these conditions.
17528 
17529 
17530 hasp_mpx (line TTY)            303            08/03/23     MR12.7^L
17531 
17532 
17533      Action:   Contact the  system programming staff.  It  may be
17534                necessary  to  increase  the  size  of  tty_buf as
17535                specified  on the  PARM config  card before  using
17536                this multiplexer again.
17537 
17538 
17539 
17540                [hasp_mpx.pl1]
17541                hasp_mpx (line TTY):  Too  many NAKs; line will be
17542                hungup.
17543 
17544 
17545      Stream:   Note for system programmer action.
17546 
17547      Time:     While system is running.
17548 
17549      Meaning:  A  block could not  be transmitted or  received by
17550                the  HASP multiplexer  on channel  TTY because  of
17551                excessive  line  noise.   The  connection  to  the
17552                remote     host/workstation    is     broken    as
17553                communications   cannot   continue   under   these
17554                conditions.
17555 
17556      Action:   The   operator  should  contact   the  appropriate
17557                personnel  to check  the communications  equipment
17558                used by  the line before attempting  to reuse this
17559                multiplexer.
17560 
17561 
17562 
17563                [hc_dmpr_primitives.pl1]
17564                hc_dmpr_primitives:  bad uid  pathname detected at
17565                pvid WWWW vtocx XXXX
17566 
17567 
17568      Stream:   Logged in SYSERR log.
17569 
17570      Time:     While system is running.
17571 
17572      Meaning:  Part 3 of the indicated  VTOCE is bad.  The dumper
17573                will treat the vtoce as a null vtoce and continue.
17574 
17575      Action:   No operator action is required.
17576 
17577 
17578                [hc_dmpr_primitives.pl1]
17579                hc_dmpr_primitives:     trailer    storage    area
17580                exhausted
17581 
17582 
17583      Stream:   BOS Typewriter (Crashes system)
17584 
17585      Time:     While system is running.
17586 
17587 
17588 hc_dmpr_primitives             304            08/03/23     MR12.7^L
17589 
17590 
17591      Meaning:  This indicates a logic error in the supervisor, or
17592                CPU or memory hardware problems.
17593 
17594      Action:   Follow normal recovery procedures.
17595 
17596 
17597                [hc_dmpr_primitives.pl1]
17598                hc_dmpr_primitives:   Unable  to  set  label time.
17599                PVID = wwwwwwwwwwww
17600 
17601 
17602      Stream:   BOS Typewriter.
17603 
17604      Time:     While system is running.
17605 
17606      Meaning:  A  disk  error  prevented   the  updating  of  the
17607                time-last-dumped field  in the volume  label.  The
17608                physical volume identifier is wwwwwwwwwwww.
17609 
17610      Action:   Contact the system programming staff.
17611 
17612 
17613                [hc_initlzr_auxl_init_.pl1]
17614                hc_initlrz_auxl_init_:        MESSAGE.        From
17615                hc_device_acct_$init.
17616 
17617 
17618      Stream:   as (severity2)
17619 
17620      Time:     System Intialization.
17621 
17622      Meaning:  An  error was  detected while  initializing device
17623                accounting.
17624 
17625      Action:   Contact the system programming staff.
17626 
17627 
17628                [hc_ipc.pl1]
17629                hc_ipc:  ITT overflow caused by NAME.PROJ
17630 
17631 
17632      Stream:   BOS Typewriter.
17633 
17634      Time:     While system is running.
17635 
17636      Meaning:  When wakeups are sent from one process to another,
17637                or from a  device like a tape drive  to a process,
17638                the   wakeups  are   stored  temporarily   in  the
17639                Interprocess Transmission Table (ITT).  If wakeups
17640                are  sent too  fast, or  if the  receiving process
17641                never calls block to read its wakeups, the ITT may
17642                overflow.  When  the ITT is full,  this message is
17643                printed  for   each  lost  wakeup.    The  message
17644 
17645 
17646 hc_ipc                         305            08/03/23     MR12.7^L
17647 
17648 
17649                identifies  the sender of  the wakeup, who  may be
17650                innocent of any error or wrongdoing.
17651 
17652                If  a  critical  system  function  cannot  send  a
17653                wakeup, the system may crash.
17654 
17655      Action:   If the ITT overflow is a transient condition, this
17656                message will stop coming  out after a few minutes.
17657                If so, system operation  may return to normal.  If
17658                the message comes out  repeatedly, the system will
17659                have to be crashed, since user terminal operation,
17660                daemon  operations,  and  the  message coordinator
17661                depend   on  wakeups.    Follow  normal   recovery
17662                procedures.
17663 
17664 
17665 
17666                [hc_ipc.pl1]
17667                hc_ipc:  Unable to allocate in ring RINGNO ECT for
17668                NAME.PROJ
17669 
17670 
17671      Stream:   Logged in SYSERR log.
17672 
17673      Time:     While system is running.
17674 
17675      Meaning:  When a  process recieves wakeups, they  are copied
17676                from  the Interprocess   Transmission Table  to an
17677                Event Channel Table (ECT).  A process owns one ECT
17678                per  ring.  If,  for any  reason, an  entry for  a
17679                wakeup cannot be allocated in a process' ECT, that
17680                process is terminated.
17681 
17682      Action:   If  the process  is a  daemon process,  it must be
17683                reinitialized.  If the  process is the initializer
17684                process, the system will crash.
17685 
17686 
17687 
17688                [hc_load_mpc.pl1]
17689                hc_load_mpc:   Booting  channel   CHNL  with  FWID
17690                Revision  REV hc_load_mpc:   Booting channel  CHNL
17691                with FWID Revision REV Overlay FWOVERLAY
17692 
17693 
17694 
17695      Stream:   BOS Typewriter.
17696 
17697      Time:     System Intialization.
17698 
17699      Meaning:  No operator action is required.
17700 
17701      Action:   $config
17702 
17703 
17704 hc_load_mpc                    306            08/03/23     MR12.7^L
17705 
17706 
17707 
17708 
17709                [hc_load_mpc.pl1]
17710                hc_load_mpc:  Could not abs_wire buffer.
17711 
17712 
17713      Stream:   BOS Typewriter (Crashes system)
17714 
17715      Time:     System Intialization.
17716 
17717      Meaning:  This indicates a logic error in the supervisor, or
17718                CPU or memory hardware problems.
17719 
17720      Action:   Contact the system programming staff.
17721 
17722 
17723                [hc_load_mpc.pl1]
17724                hc_load_mpc:  data buffer not in low 256K
17725 
17726 
17727      Stream:   BOS Typewriter (Crashes system)
17728 
17729      Time:     System Intialization.
17730 
17731      Meaning:  This indicates a logic error in the supervisor, or
17732                CPU or memory hardware problems.
17733 
17734      Action:   Contact the system programming staff.
17735 
17736 
17737 
17738 
17739                [hc_page_trace.pl1]
17740                hc_page_trace:  pds$trace.threshold found zero for
17741                USER.
17742 
17743 
17744      Meaning:  The  signalling  threshold  for  page  tracing was
17745                found  to be zero  for USER.  This  indicates that
17746                the user's pds has been damaged.
17747 
17748      Stream:   BOS Typewriter (Terminates user process)
17749 
17750      Time:     While system is running.
17751 
17752      Action:   Investigate the saved dead process.
17753 
17754 
17755                [ibm3270_mpx.pl1]
17756                ibm3270_mpx:  Attempt  to queue write  while write
17757                queued CHANNEL.SUBCHANNEL
17758 
17759 
17760 
17761 
17762 ibm3270_mpx                    307            08/03/23     MR12.7^L
17763 
17764 
17765      Stream:   Logged in SYSERR log.
17766 
17767      Time:     While system is running.
17768 
17769      Meaning:  An  attempt was  made to   queue a  write while  a
17770                previous  write was still  queued.  A dump  of the
17771                subchannel entry  as defined by the  mde structure
17772                in ibm3270_mpx_data.incl.pl1 is included with this
17773                message.
17774 
17775      Action:   No operator action is required.
17776 
17777 
17778                [ibm3270_mpx.pl1]
17779                ibm3270_mpx:  Buffer tally error on CHANNEL.
17780 
17781 
17782      Stream:   BOS Typewriter (Crashes system)
17783 
17784      Time:     While system is running.
17785 
17786      Meaning:  An attempt was made to  add characters to a buffer
17787                which should have fit but couldn't.
17788 
17789      Action:   Contact the system programming staff.
17790 
17791 
17792                [ibm3270_mpx.pl1]
17793                ibm3270_mpx:   Could  not  find  queued  write  on
17794                CHANNEL.
17795 
17796 
17797      Stream:   BOS Typewriter (sounds beeper)
17798 
17799      Time:     While system is running.
17800 
17801      Meaning:  The  reset_channel  internal  procedure  could not
17802                find  a queued  write  on  CHANNEL or  it detected
17803                itself  looping  in  releasing  queued  writes for
17804                CHANNEL.  Will attempt to continue.
17805 
17806      Action:   Contact the system programming staff.
17807 
17808 
17809                [ibm3270_mpx.pl1]
17810                ibm3270_mpx:   Error  trimming  buffer  chain  for
17811                CHANNEL
17812 
17813 
17814      Stream:   BOS Typewriter (Crashes system)
17815 
17816      Time:     While system is running.
17817 
17818 
17819 
17820 ibm3270_mpx                    308            08/03/23     MR12.7^L
17821 
17822 
17823      Meaning:  An  inconsistency  was  found  while  trimming the
17824                buffer  chain  for  CHANNEL  which  is  stored  in
17825                tty_buf.
17826 
17827      Action:   Contact the system programming staff.
17828 
17829 
17830                [ibm3270_mpx.pl1]
17831                ibm3270_mpx:   Input  for  illegal  device address
17832                DEV_ADDRESS on CHANNEL
17833 
17834 
17835      Stream:   BOS Typewriter.
17836 
17837      Time:     While system is running.
17838 
17839      Meaning:  Received   input  for   a  device   whose  address
17840                (DEV_ADDRESS)  is  not  in  the  channel  map  for
17841                CHANNEL.
17842 
17843      Action:   Contact the system programming staff.
17844 
17845 
17846                [ibm3270_mpx.pl1]
17847                ibm3270_mpx:    Input   for   unconfigured  device
17848                DEV_ADDRESS on CHANNEL
17849 
17850 
17851      Stream:   BOS Typewriter.
17852 
17853      Time:     While system is running.
17854 
17855      Meaning:  Received  input for  a device  (DEV_ADDRESS) whose
17856                subchannel  was  <=  0  in  the  channel  map  for
17857                CHANNEL.
17858 
17859      Action:   Contact the system programming staff.
17860 
17861 
17862                [ibm3270_mpx.pl1]
17863                ibm3270_mpx:   Unrecognized   input  for  CHANNEL:
17864                DATA
17865 
17866 
17867      Stream:   BOS Typewriter.
17868 
17869      Time:     While system is running.
17870 
17871      Meaning:  DATA received  from CHANNEL does not  meet certain
17872                format   requirements.   This   message  is   only
17873                displayed if in debug mode.
17874 
17875      Action:   Contact the system programming staff.
17876 
17877 
17878 ibm3270_mpx                    309            08/03/23     MR12.7^L
17879 
17880 
17881 
17882 
17883                [ibm3270_mpx.pl1]
17884                ibm3270_mpx:  Unrecognized  interrupt for CHANNEL.
17885                INT_TYPE INTERRUPT_INFO
17886 
17887 
17888      Stream:   BOS Typewriter.
17889 
17890      Time:     While system is running.
17891 
17892      Meaning:  An interrupt was received  from the FNP which does
17893                not have a defined  action.  The type of interrupt
17894                received is INT_TYPE  and the information supplied
17895                with the interrupt is INTERRUPT_INFO.
17896 
17897      Action:   Contact the system programming staff.
17898 
17899 
17900                [init_branches.pl1]
17901                init_branches:  $branch From asd_:  ERRORMESSAGE
17902 
17903 
17904      Stream:   BOS Typewriter.
17905 
17906      Time:     System Intialization.
17907 
17908      Meaning:  This indicates a logic error in the supervisor, or
17909                CPU  or memory hardware  problems.  Initialization
17910                continues.
17911 
17912      Action:   Contact the system programming staff.
17913 
17914 
17915                [init_branches.pl1]
17916                init_branches:    couldn't   add   name   pdd   to
17917                process_dir_dir:  ERRORMESSAGE
17918 
17919 
17920      Stream:   BOS Typewriter.
17921 
17922      Time:     System Intialization.
17923 
17924      Meaning:  This indicates a logic error in the supervisor, or
17925                CPU  or memory hardware  problems.  Initialization
17926                continues.  Certain application  programs may fail
17927                to work.
17928 
17929      Action:   Contact the system programming staff.
17930 
17931 
17932                [init_branches.pl1]
17933 
17934 
17935 
17936 init_branches                  310            08/03/23     MR12.7^L
17937 
17938 
17939                init_branches:    couldn't   add   name   sl1   to
17940                system_library_1:  ERRORMESSAGE
17941 
17942 
17943      Stream:   BOS Typewriter.
17944 
17945      Time:     System Intialization.
17946 
17947      Meaning:  This indicates a logic error in the supervisor, or
17948                CPU  or memory hardware  problems.  Initialization
17949                continues.  Certain application  programs may fail
17950                to work.
17951 
17952      Action:   Contact the system programming staff.
17953 
17954 
17955                [init_branches.pl1]
17956                init_branches:  couldn't set {dir}quota on >pdd to
17957                XXXX:  ERRORMESSAGE
17958 
17959 
17960      Stream:   BOS Typewriter.
17961 
17962      Time:     System Intialization.
17963 
17964      Meaning:  This indicates a logic error in the supervisor, or
17965                CPU  or memory hardware  problems.  Initialization
17966                continues.   The answering  service may  encounter
17967                trouble in creating processes.
17968 
17969      Action:   Contact the system programming staff.
17970 
17971 
17972                [init_branches.pl1]
17973                init_branches:  deleting old pdd:  ERRORMESSAGE
17974 
17975 
17976      Stream:   BOS Typewriter (Crashes system)
17977 
17978      Time:     System Intialization.
17979 
17980      Meaning:  The name pdd could not be removed from >pdd.  This
17981                indicates a logic error  in the supervisor, or CPU
17982                or memory hardware problems.
17983 
17984      Action:   Follow normal recovery procedures.
17985 
17986 
17987                [init_branches.pl1]
17988                init_branches:  error from initiate.  ERRORMESSAGE
17989 
17990 
17991      Stream:   BOS Typewriter (Crashes system)
17992 
17993 
17994 init_branches                  311            08/03/23     MR12.7^L
17995 
17996 
17997      Time:     System Intialization.
17998 
17999      Meaning:  A deciduous segment could not be made known.  This
18000                indicates a logic error  in the supervisor, or CPU
18001                or memory hardware problems.
18002 
18003      Action:   Follow normal recovery procedures.
18004 
18005 
18006                [init_branches.pl1]
18007                init_branches:     error    from    set$max_length
18008                ERRORMESSAGE
18009 
18010 
18011      Stream:   BOS Typewriter (Crashes system)
18012 
18013      Time:     System Intialization.
18014 
18015      Meaning:  This indicates a logic error in the supervisor, or
18016                CPU or memory hardware problems.
18017 
18018      Action:   Follow normal recovery procedures.
18019 
18020 
18021                [init_branches.pl1]
18022                init_branches:      error     from     terminate_:
18023                ERRORMESSAGE
18024 
18025 
18026      Stream:   BOS Typewriter (Crashes system)
18027 
18028      Time:     System Intialization.
18029 
18030      Meaning:  This indicates a logic error in the supervisor, or
18031                CPU or memory hardware problems.
18032 
18033      Action:   Follow normal recovery procedures.
18034 
18035 
18036                [init_branches.pl1]
18037                init_branches:   error  in  adding  acl  of dumps:
18038                ERRORMESSAGE
18039 
18040 
18041      Stream:   BOS Typewriter.
18042 
18043      Time:     System Intialization.
18044 
18045      Meaning:  This indicates a logic error in the supervisor, or
18046                CPU  or memory hardware  problems.  Initialization
18047                continues.  The copy_fdump  command may fail.  The
18048                online  salvager  may  fail   to  make  stack  and
18049                directory copies in >dumps.
18050 
18051 
18052 init_branches                  312            08/03/23     MR12.7^L
18053 
18054 
18055      Action:   Contact the system programming staff.
18056 
18057 
18058                [init_branches.pl1]
18059                init_branches:   error in  replacing acl  of >sl1.
18060                ERRORMESSAGE
18061 
18062 
18063      Stream:   BOS Typewriter.
18064 
18065      Time:     System Intialization.
18066 
18067      Meaning:  This indicates a logic error in the supervisor, or
18068                CPU  or memory hardware  problems.  Initialization
18069                continues.    User   and   daemon   processes  may
18070                malfunction.
18071 
18072      Action:   Contact the system programming staff.
18073 
18074 
18075                [init_branches.pl1]
18076                init_branches:  From set$max_length:  ERRORMESSAGE
18077 
18078 
18079      Stream:   BOS Typewriter (Crashes system)
18080 
18081      Time:     System Intialization.
18082 
18083      Meaning:  This indicates a logic error in the supervisor, or
18084                CPU or memory hardware problems.
18085 
18086      Action:   Follow normal recovery procedures.
18087 
18088 
18089                [init_branches.pl1]
18090                init_branches:  From status_$long:  ERRORMESSAGE
18091 
18092 
18093      Stream:   BOS Typewriter (Crashes system)
18094 
18095      Time:     System Intialization.
18096 
18097      Meaning:  This indicates a logic error in the supervisor, or
18098                CPU or memory hardware problems.
18099 
18100      Action:   Follow normal recovery procedures.
18101 
18102 
18103                [init_branches.pl1]
18104                init_branches:    getting   dir   entry   pointer:
18105                ERRORMESSAGE
18106 
18107 
18108 
18109 
18110 init_branches                  313            08/03/23     MR12.7^L
18111 
18112 
18113      Stream:   BOS Typewriter (Crashes system)
18114 
18115      Time:     System Intialization.
18116 
18117      Meaning:  This indicates a logic error in the supervisor, or
18118                CPU or memory hardware problems.
18119 
18120      Action:   Follow normal recovery procedures.
18121 
18122 
18123                [init_branches.pl1]
18124                init_branches:  Mysterious directory deactivation
18125 
18126 
18127      Stream:   BOS Typewriter (Crashes system)
18128 
18129      Time:     System Intialization.
18130 
18131      Meaning:  This indicates a logic error in the supervisor, or
18132                CPU or memory hardware problems.
18133 
18134      Action:   Follow normal recovery procedures.
18135 
18136 
18137                [init_branches.pl1]
18138                init_branches:  renaming old pdd:  ERRORMESSAGE
18139 
18140 
18141      Stream:   BOS Typewriter (Crashes system)
18142 
18143      Time:     System Intialization.
18144 
18145      Meaning:  This indicates a logic error in the supervisor, or
18146                CPU or memory hardware problems.
18147 
18148      Action:   Follow normal recovery procedures.
18149 
18150 
18151                [init_branches.pl1]
18152                init_branches:       renaming     process_dir_dir:
18153                ERRORMESSAGE
18154 
18155 
18156      Stream:   BOS Typewriter (Crashes system)
18157 
18158      Time:     System Intialization.
18159 
18160      Meaning:  This indicates a logic error in the supervisor, or
18161                CPU or memory hardware problems.
18162 
18163      Action:   Follow normal recovery procedures.
18164 
18165 
18166 
18167 
18168 init_branches                  314            08/03/23     MR12.7^L
18169 
18170 
18171 
18172 
18173                [init_branches.pl1]
18174                init_branches:  replacing >pdd acl:  ERRORMESSAGE
18175 
18176 
18177      Stream:   BOS Typewriter.
18178 
18179      Time:     System Intialization.
18180 
18181      Meaning:  This indicates a logic error in the supervisor, or
18182                CPU  or memory hardware  problems.  Initialization
18183                continues.
18184 
18185      Action:   Contact the system programming staff.
18186 
18187 
18188                [init_branches.pl1]
18189                init_branches:    replacing   acl   of   >pdd  for
18190                Initializer:  ERRORMESSAGE
18191 
18192 
18193      Stream:   BOS Typewriter.
18194 
18195      Time:     System Intialization.
18196 
18197      Meaning:  This indicates a logic error in the supervisor, or
18198                CPU  or memory hardware  problems.  Initialization
18199                continues.
18200 
18201      Action:   Contact the system programming staff.
18202 
18203 
18204                [init_branches.pl1]
18205                init_branches:  unable to  append dumps directory.
18206                ERRORMESSAGE
18207 
18208 
18209      Stream:   BOS Typewriter (sounds beeper)
18210 
18211      Time:     System Intialization.
18212 
18213      Meaning:  This indicates a logic error in the supervisor, or
18214                CPU  or memory hardware  problems.  Initialization
18215                continues.
18216 
18217      Action:   Contact the system programming staff.
18218 
18219 
18220                [init_branches.pl1]
18221                init_branches:    unable  to   initiate  >DIRNAME:
18222                ERRORMESSAGE
18223 
18224 
18225 
18226 init_branches                  315            08/03/23     MR12.7^L
18227 
18228 
18229      Stream:   BOS Typewriter (Crashes system)
18230 
18231      Time:     System Intialization.
18232 
18233      Meaning:  This indicates a logic error in the supervisor, or
18234                CPU or memory hardware problems.
18235 
18236      Action:   Follow normal recovery procedures.
18237 
18238 
18239                [init_branches.pl1]
18240                init_branches:  unable  to make >system_library_1:
18241                ERRORMESSAGE
18242 
18243 
18244      Stream:   BOS Typewriter (Crashes system)
18245 
18246      Time:     System Intialization.
18247 
18248      Meaning:  This indicates a logic error in the supervisor, or
18249                CPU or memory hardware problems.
18250 
18251      Action:   Follow normal recovery procedures.
18252 
18253 
18254                [init_branches.pl1]
18255                init_branches:   unable  to  make process_dir_dir:
18256                ERRORMESSAGE
18257 
18258 
18259      Stream:   BOS Typewriter (Crashes system)
18260 
18261      Time:     System Intialization.
18262 
18263      Meaning:  This indicates a logic error in the supervisor, or
18264                CPU or memory hardware problems.
18265 
18266      Action:   Follow normal recovery procedures.
18267 
18268 
18269                [init_branches.pl1]
18270                init_branches:      {dir}quotas      for     pdir:
18271                ERRORMESSAGE
18272 
18273 
18274      Stream:   BOS Typewriter.
18275 
18276      Time:     System Intialization.
18277 
18278      Meaning:  This indicates a logic error in the supervisor, or
18279                CPU  or memory hardware  problems.  Initialization
18280                continues.
18281 
18282 
18283 
18284 init_branches                  316            08/03/23     MR12.7^L
18285 
18286 
18287      Action:   Contact the system programming staff.
18288 
18289 
18290                [init_disk_pack_.pl1]
18291                init_disk_pack_:   Specified control  argument not
18292                accepted.  "-rlv" allowed only  at ring-1 during a
18293                cold boot.
18294 
18295 
18296 
18297      Stream:   Initializer process output.
18298 
18299      Time:     In response to an operator command.
18300 
18301      Meaning:  Automatic registration of root PVs is allowed only
18302                during a cold boot of Multics.
18303 
18304      Action:   Use  the "add_volume_registration"  administrative
18305                command  to register  the PV  before attempting to
18306                initialize it.
18307 
18308 
18309 
18310                [init_disk_pack_.pl1]
18311                init_disk_pack_:   Cannot  read  current  label of
18312                DRIVE:  ERROR_MESSAGE
18313 
18314 
18315      Stream:   Initializer process output.
18316 
18317      Time:     In response to an operator command.
18318 
18319      Meaning:  A  disk error prevents  checking the label  of the
18320                pack on DRIVE.  The pack  may need to be formatted
18321                before it can be initialized.
18322 
18323      Action:   Take appropriate action.
18324 
18325 
18326                [init_disk_pack_.pl1]
18327                init_disk_pack_:   DRIVE PVNAME  disk err  WWWW on
18328                ITEM
18329 
18330 
18331      Stream:   Initializer process output.
18332 
18333      Time:     In response to an operator command.
18334 
18335      Meaning:  A disk error prevents  writing the ITEM section of
18336                the disk volume PVNAME.
18337 
18338      Action:   Fix the drive, or use a new pack.
18339 
18340 
18341 
18342 init_disk_pack_                317            08/03/23     MR12.7^L
18343 
18344 
18345 
18346 
18347                [init_disk_pack_.pl1]
18348                init_disk_pack_:   INTK card  missing from  config
18349                deck.
18350 
18351 
18352      Stream:   Initializer process output.
18353 
18354      Time:     In response to an operator command.
18355 
18356      Meaning:  When  the operator   specifies the  "-rlv" control
18357                argument  to "init_vol"  this program  attempts to
18358                verify  that  the  system   is  in  cold  boot  by
18359                inspecting the INTK card in the config deck.  When
18360                this message appears, there  is some difficulty in
18361                locating that card.
18362 
18363      Action:   If really trying to boot cold, try again.
18364 
18365 
18366                [init_disk_pack_.pl1]
18367                init_disk_pack_:  unrecognized argument:  BLAH
18368 
18369 
18370      Stream:   Initializer process output.
18371 
18372      Time:     In response to an operator command.
18373 
18374      Meaning:  Illegal input was typed.
18375 
18376      Action:   Enter a corrected command line.
18377 
18378 
18379                [init_disk_pack_.pl1]
18380                init_disk_pack_:   Volume on  DRIVE is  a copy  of
18381                Multics Storage System Volume "PVNAME",
18382                last used DATE_TIME.  Do you wish to overwrite it?
18383 
18384 
18385 
18386      Stream:   Initializer process output.
18387 
18388      Time:     In response to an operator command.
18389 
18390      Meaning:  The init_disk  command specifed a disk  pack which
18391                has a valid Multics label.  Another copy of PVNAME
18392                is currently in use.   Initializing this pack will
18393                destroy all data contained on it.
18394 
18395      Action:   Do  not answer  yes unless  you are  sure that the
18396                pack contents should be destroyed.  Check the pack
18397                serial number.
18398 
18399 
18400 init_disk_pack_                318            08/03/23     MR12.7^L
18401 
18402 
18403 
18404 
18405                [init_disk_pack_.pl1]
18406                init_disk_pack_:  Volume on DRIVE  is a copy of pv
18407                "PVNAME",
18408                last used DATE_TIME.  Do you wish to overwrite it?
18409 
18410 
18411 
18412      Stream:   Initializer process output.
18413 
18414      Time:     In response to an operator command.
18415 
18416      Meaning:  The init_disk  command specifed a disk  pack which
18417                has  a valid  Multics label.   It appears  to be a
18418                copy  of a  mounted pack.   Initializing this pack
18419                will destroy all data contained on it.
18420 
18421      Action:   Do  not answer  yes unless  you are  sure that the
18422                pack contents should be destroyed.  Check the pack
18423                serial number.
18424 
18425 
18426 
18427                [init_disk_pack_.pl1]
18428                init_disk_pack_:   Volume on  DRIVE is  an earlier
18429                instance of pv "PVNAME",
18430                last used DATE_TIME.  Do you wish to overwrite it?
18431 
18432 
18433 
18434      Stream:   Initializer process output.
18435 
18436      Time:     In response to an operator command.
18437 
18438      Meaning:  The init_disk  command specifed a disk  pack which
18439                has a valid Multics label.  Initializing this pack
18440                will destroy all data contained on it.
18441 
18442      Action:   Do  not answer  yes unless  you are  sure that the
18443                pack contents should be destroyed.  Check the pack
18444                serial number.
18445 
18446 
18447 
18448                [init_disk_pack_.pl1]
18449                init_disk_pack_:    Volume   on    DRIVE   is   an
18450                unregistered pack named "PVNAME",
18451                last used DATE_TIME.  Do you wish to overwrite it?
18452 
18453 
18454 
18455      Stream:   Initializer process output.
18456 
18457 
18458 init_disk_pack_                319            08/03/23     MR12.7^L
18459 
18460 
18461      Time:     In response to an operator command.
18462 
18463      Meaning:  The init_disk  command specifed a disk  pack which
18464                has a valid Multics label.  Initializing this pack
18465                will destroy all data contained on it.
18466 
18467      Action:   Do  not answer  yes unless  you are  sure that the
18468                pack contents should be destroyed.  Check the pack
18469                serial number.
18470 
18471 
18472 
18473                [init_disk_pack_.pl1]
18474                init_disk_pack_:   Volume  on   DRIVE  is  Multics
18475                Storage System Volume "PVNAME",
18476                last used DATE_TIME.  Do you wish to overwrite it?
18477 
18478 
18479 
18480      Stream:   Initializer process output.
18481 
18482      Time:     In response to an operator command.
18483 
18484      Meaning:  The init_disk  command specifed a disk  pack which
18485                has a valid Multics label.  Initializing this pack
18486                will destroy all data contained on it.
18487 
18488      Action:   Do  not answer  yes unless  you are  sure that the
18489                pack contents should be destroyed.  Check the pack
18490                serial number.
18491 
18492 
18493 
18494                [init_dm_journal_seg.pl1]
18495                init_dm_journal_seg:  Invalid DBMJ config card.
18496 
18497 
18498      Stream:   BOS Typewriter (Crashes system)
18499 
18500      Time:     System Intialization.
18501 
18502      Meaning:  The  DBMJ  configuration  card  is  not  in proper
18503                format.  This  could be a format error,  or one of
18504                the following criteria may  not be satisfied.  The
18505                limit  on  active  segments  for  a  pool  must be
18506                smaller than the pool size.
18507 
18508      Action:   Correct the configuration deck and reboot.
18509 
18510 
18511                [init_dm_journal_seg.pl1]
18512                init_dm_journal_seg:     make_sdw    failed    for
18513                dm_journal_seg_
18514 
18515 
18516 init_dm_journal_seg            320            08/03/23     MR12.7^L
18517 
18518 
18519      Stream:   BOS Typewriter (Crashes system)
18520 
18521      Time:     System Intialization.
18522 
18523      Meaning:  The ASTE for dm_journal_seg_ could not be created.
18524 
18525      Action:   Contact the system programming staff.
18526 
18527 
18528                [init_early_config.pl1]
18529                init_early_config:   Cannot  add  card  to  config
18530                deck:  CARD.
18531 
18532 
18533      Stream:   BOS Typewriter (Crashes system)
18534 
18535      Time:     System Intialization.
18536 
18537      Meaning:  The config_deck  being generated during  the early
18538                (hardware  inspection)  pass  of  bce  is damaged.
18539                This can be either a hardware or software problem.
18540 
18541      Action:   $reboot
18542 
18543 
18544                [init_hc_part.pl1]
18545                init_hc_part:  HC PART on dskX_NN too small
18546 
18547 
18548      Stream:   BOS Typewriter (Crashes system)
18549 
18550      Time:     System Intialization.
18551 
18552      Meaning:  The Hardcore Partition on  the device indicated is
18553                unreasonably  small,   as  it  does   not  contain
18554                sufficient  space to  hold the  bit map describing
18555                it.
18556 
18557      Action:   Recreate the partition and reboot.
18558 
18559 
18560                [init_hc_part.pl1]
18561                init_hc_part:  volmap_abs_seg size too small
18562 
18563 
18564      Time:     System Intialization.
18565 
18566      Stream:   BOS Typewriter (Crashes system)
18567 
18568      Meaning:  The  maximum length  of volmap_abs_seg  on the MST
18569                header  is  not  sufficient  to  access  an entire
18570                Volume Map.
18571 
18572 
18573 
18574 init_hc_part                   321            08/03/23     MR12.7^L
18575 
18576 
18577      Action:   Recreate the MST with  a larger maximum length for
18578                volmap_abs_seg and reboot.
18579 
18580 
18581 
18582                [init_lvt.pl1]
18583                init_lvt:  unable to define RLV, code = WWWW
18584 
18585 
18586      Stream:   BOS Typewriter (Crashes system)
18587 
18588      Time:     System Intialization.
18589 
18590      Meaning:  This indicates a logic error in the supervisor, or
18591                CPU or memory hardware problems.
18592 
18593      Action:   Follow normal recovery procedures.  $boot_tape
18594 
18595 
18596 
18597                [init_lvt.pl1]
18598                init_lvt:  unable to read RPV label, code = WWWW
18599 
18600 
18601      Stream:   BOS Typewriter (Crashes system)
18602 
18603      Time:     System Intialization.
18604 
18605      Meaning:  The RPV  label, which was successfully  read a few
18606                seconds ago, cannot be read.
18607 
18608      Action:   Follow normal recovery procedures.  $boot_tape
18609 
18610 
18611 
18612                [init_partitions.pl1]
18613                init_partition:   part PART_NAME for  part PART_ID
18614                not in label of DISK_DRIVE (pvtx PVTX).
18615 
18616 
18617      Stream:   BOS Typewriter (Crashes system)
18618 
18619      Time:     System Intialization.
18620 
18621      Meaning:  A PART  card specified DISK_DRIVE as  the location
18622                of   partition  PART_NAME,    but  the   label  of
18623                DISK_DRIVE does not define it.
18624 
18625      Action:   Fix the config deck.
18626 
18627 
18628                [init_partitions.pl1]
18629 
18630 
18631 
18632 init_partition                 322            08/03/23     MR12.7^L
18633 
18634 
18635                init_partition:   part PART_NAME  not in  label of
18636                DISK_DRIVE (pvtx PVTX).
18637 
18638 
18639      Stream:   BOS Typewriter (Crashes system)
18640 
18641      Time:     System Intialization.
18642 
18643      Meaning:  A PART  card specified DISK_DRIVE as  the location
18644                of   partition  PART_NAME,    but  the   label  of
18645                DISK_DRIVE does not define it.
18646 
18647      Action:   Fix the config deck.
18648 
18649 
18650                [init_partitions.pl1]
18651                init_partition:   There are  no partitions  in the
18652                label for DISK_DRIVE (pvtx PVTX).
18653 
18654 
18655      Stream:   BOS Typewriter (Crashes system)
18656 
18657      Time:     System Intialization.
18658 
18659      Meaning:  DISK_DRIVE has been specified  on a part card, but
18660                has no partitions defined in its label.
18661 
18662      Action:   Fix the config deck.
18663 
18664 
18665                [init_partitions.pl1]
18666                init_partitions:  Error  reading DISK_DRIVE label.
18667                PROBLEM ERROR_MESSAGE
18668 
18669 
18670      Stream:   BOS Typewriter (Crashes system)
18671 
18672      Time:     System Intialization.
18673 
18674      Meaning:  An error has been  detected attempting to read the
18675                label of DISK_DRIVE.
18676 
18677      Action:   Correct problem and type "go" to retry the read.
18678 
18679 
18680                [init_partitions.pl1]
18681                init_partitions:  Ignoring  COLD_SPEC on PART_NAME
18682                part card.
18683 
18684 
18685      Stream:   BOS Typewriter (sounds beeper)
18686 
18687      Time:     System Intialization.
18688 
18689 
18690 init_partitions                323            08/03/23     MR12.7^L
18691 
18692 
18693      Meaning:  Cold boot partition  specifications were found for
18694                partition PART_NAME, and will be ignored.
18695 
18696 
18697 
18698                [init_partitions.pl1]
18699                init_partitions:   Invalid device,  DISK_DRIVE, on
18700                PART_NAME part card.
18701 
18702 
18703      Stream:   BOS Typewriter (Crashes system)
18704 
18705      Time:     System Intialization.
18706 
18707      Meaning:  An invalid drive definition has been found for the
18708                PART_NAME part card.
18709 
18710      Action:   Fix PART card.
18711 
18712 
18713                [init_partitions.pl1]
18714                init_partitions:  Unable to  locate DISK_DRIVE for
18715                PART_NAME partition.
18716 
18717 
18718      Stream:   BOS Typewriter (Crashes system)
18719 
18720      Time:     System Intialization.
18721 
18722      Meaning:  Partition  PART_NAME is   specified in  the config
18723                deck for a non existent DISK_DRIVE.
18724 
18725      Action:   Fix PART and/or PRPH DSK cards.
18726 
18727 
18728                [init_proc.pl1]
18729                init_proc:   bad   process  type  (N)   given  for
18730                PERSON.PROJ.T
18731 
18732 
18733      Stream:   BOS Typewriter (sounds beeper)
18734 
18735      Time:     While system is running.
18736 
18737      Meaning:  The  answering service   has specified  an unknown
18738                integer  in  the  process  type  field.  Incorrect
18739                arguments were passed  to hphcs_$create_proc.  The
18740                user cannot be logged in.
18741 
18742      Action:   Contact the system programming staff.
18743 
18744 
18745                [init_proc.pl1]
18746 
18747 
18748 init_proc                      324            08/03/23     MR12.7^L
18749 
18750 
18751                init_proc:  bad syntax  in initial procedure name:
18752                STRING for PERSON.PROJ.T
18753 
18754 
18755      Stream:   Logged in SYSERR log.
18756 
18757      Time:     While system is running.
18758 
18759      Meaning:  An  illegal initial  procedure name  was specified
18760                for  the  user.   The   user  may  have  given  an
18761                incorrect -po  argument, or the project's  PDT may
18762                be wrong.  No process is created.
18763 
18764      Action:   No operator action is required.
18765 
18766 
18767                [init_proc.pl1]
18768                init_proc:  can not call out to initial procedure:
18769                NAME for PERSON.PROJ.T ERROR_MESSAGE
18770 
18771 
18772      Stream:   Logged in SYSERR log.
18773 
18774      Time:     While system is running.
18775 
18776      Meaning:  The supervisor could not snap a link to NAME$NAME.
18777                The  process  overseer  may  be  in  invalid form,
18778                inaccessible, or missing.  The user may have given
18779                an  incorrect -po  argument, or  the project's PDT
18780                may be incorrect.
18781 
18782      Action:   No operator action is required.
18783 
18784 
18785                [init_proc.pl1]
18786                init_proc:   can   not  get  pointer   to  initial
18787                procedure:  PATH for PERSON.PROJ.T ERROR_MESSAGE
18788 
18789 
18790      Stream:   Logged in SYSERR log.
18791 
18792      Time:     While system is running.
18793 
18794      Meaning:  The  supervisor could  not initiate  the specified
18795                initial procedure PATH.   The process overseer may
18796                be in invalid form, inaccessible, or missing.  The
18797                user may have given  an incorrect -po argument, or
18798                the project's PDT may be incorrect.
18799 
18800      Action:   No operator action is required.
18801 
18802 
18803                [init_proc.pl1]
18804 
18805 
18806 init_proc                      325            08/03/23     MR12.7^L
18807 
18808 
18809                init_proc:   could  not  get  pointer  to  pit for
18810                PERSON.PROJ.T ERROR_MESSAGE
18811 
18812 
18813      Stream:   BOS Typewriter (sounds beeper)
18814 
18815      Time:     While system is running.
18816 
18817      Meaning:  The  answering  service  has  created  the process
18818                directory for a new process incorrectly.  The user
18819                cannot be logged in.
18820 
18821      Action:   Contact the system programming staff.
18822 
18823 
18824                [init_pvt.pl1]
18825                init_pvt:  Duplicate prph DISK_NAME card.
18826 
18827 
18828      Stream:   BOS Typewriter (Crashes system)
18829 
18830      Time:     System Intialization.
18831 
18832      Meaning:  Two different PRPH cards define DISK_NAME.
18833 
18834      Action:   Fix the config deck.
18835 
18836 
18837                [init_pvt.pl1]
18838                init_pvt:  Invalid parm  wlim value WLIM.  Default
18839                of DEFAULT used.
18840 
18841 
18842      Stream:   BOS Typewriter (sounds beeper)
18843 
18844      Time:     System Intialization.
18845 
18846      Meaning:  An unreasonable  value (WLIM) was found  on a PARM
18847                WLIM card.  DEFAULT has be substituted.
18848 
18849      Action:   Fix the config deck.
18850 
18851 
18852                [init_pvt.pl1]
18853                init_pvt:  Missing model MODEL on PRPH DISK.
18854 
18855 
18856      Stream:   BOS Typewriter (Crashes system)
18857 
18858      Time:     System Intialization.
18859 
18860      Meaning:  There  was no model  number specified on  the prph
18861                DISK card.
18862 
18863 
18864 init_pvt                       326            08/03/23     MR12.7^L
18865 
18866 
18867      Action:   Fix the config deck.
18868 
18869 
18870                [init_pvt.pl1]
18871                init_pvt:   Missing ndrives  field on  config card
18872                for DISK subsystem.
18873 
18874 
18875      Stream:   BOS Typewriter (Crashes system)
18876 
18877      Time:     System Intialization.
18878 
18879      Meaning:  The  PRPH  DSK  card  for  DISK  lacks the ndrives
18880                parameter for some model.
18881 
18882      Action:   Fix the config deck.
18883 
18884 
18885                [init_pvt.pl1]
18886                init_pvt:  More than N drives defined for XXXX.
18887 
18888 
18889      Stream:   BOS Typewriter (Crashes system)
18890 
18891      Time:     System Intialization.
18892 
18893      Meaning:  The  PRPH card  for disk  subsystem XXXX specified
18894                more  than the  maximum allowable  number of  disk
18895                drives.
18896 
18897      Action:   Follow  normal recovery  procedures.  Correct  the
18898                configuration deck and reboot.
18899 
18900 
18901 
18902                [init_pvt.pl1]
18903                init_pvt:  no PRPH DSKn cards
18904 
18905 
18906      Stream:   BOS Typewriter (Crashes system)
18907 
18908      Time:     System Intialization.
18909 
18910      Meaning:  No  PRPH  cards  describing  disk  subsystems were
18911                found in the CONFIG deck.
18912 
18913      Action:   Correct  the CONFIG  deck to  include the  correct
18914                PRPH  cards   to  describe  the   disk  subsystems
18915                present, and reboot.
18916 
18917 
18918 
18919                [init_pvt.pl1]
18920 
18921 
18922 init_pvt                       327            08/03/23     MR12.7^L
18923 
18924 
18925                init_pvt:   Too many  disk subsystems  configured.
18926                Limit is NUMBER.
18927 
18928 
18929      Stream:   BOS Typewriter (Crashes system)
18930 
18931      Time:     System Intialization.
18932 
18933      Meaning:  More  than NUMBER   subsystems are  defined.  Only
18934                NUMBER are allowed.
18935 
18936      Action:   Rearrange the config deck for disks and try again.
18937 
18938 
18939                [init_pvt.pl1]
18940                init_pvt:  Unknown model MODEL on PRPH DISK.
18941 
18942 
18943      Stream:   BOS Typewriter (Crashes system)
18944 
18945      Time:     System Intialization.
18946 
18947      Meaning:  The model number MODEL  specified somewhere on the
18948                prph DISK card is not a legal model number.
18949 
18950      Action:   Fix the config deck.
18951 
18952 
18953                [init_pvt.pl1]
18954                init_pvt:   XXXX contains   a drive  number higher
18955                than N.
18956 
18957 
18958      Stream:   BOS Typewriter (Crashes system)
18959 
18960      Time:     System Intialization.
18961 
18962      Meaning:  The  PRPH card  for disk  subsystem XXXX specified
18963                disk(s)  with addresses   larger than  tha maximum
18964                allowable device number, N.
18965 
18966      Action:   Follow  normal recovery  procedures.  Correct  the
18967                configuration deck and reboot.
18968 
18969 
18970 
18971                [init_root_dir.pl1]
18972                init_root_dir:   Error  from   makeknown  on  root
18973                ERROR_MESSAGE
18974 
18975 
18976      Stream:   BOS Typewriter (Crashes system)
18977 
18978 
18979 
18980 init_root_dir                  328            08/03/23     MR12.7^L
18981 
18982 
18983      Time:     System Intialization.
18984 
18985      Meaning:  This indicates a logic error in the supervisor, or
18986                CPU or memory hardware problems.
18987 
18988      Action:   Reboot with a different version of the system.
18989 
18990 
18991                [init_root_dir.pl1]
18992                init_root_dir:  Error on root vtoce ERROR_MESSAGE
18993 
18994 
18995      Stream:   BOS Typewriter (Crashes system)
18996 
18997      Time:     System Intialization.
18998 
18999      Meaning:  The  supervisor cannot  locate the  VTOC entry for
19000                the  root  directory.   The   RPV  may  have  been
19001                damaged.
19002 
19003      Action:   Follow normal recovery  procedures.  A recovery of
19004                the RPV may be required.
19005 
19006 
19007 
19008                [init_root_dir.pl1]
19009                init_root_dir:  Root damaged.
19010 
19011 
19012      Stream:   BOS Typewriter (Crashes system)
19013 
19014      Time:     System Intialization.
19015 
19016      Meaning:  The  unique  ID  of  the  root  directory  in  the
19017                directory  header is  incorrect.  The  contents of
19018                the RPV may have been damaged.
19019 
19020      Action:   Follow normal recovery  procedures.  A recovery of
19021                the RPV may be required.
19022 
19023 
19024 
19025                [init_root_vols.pl1]
19026                init_root_vols:  Adding config (conf) partition to
19027                rpv.
19028 
19029 
19030      Stream:   BOS Typewriter.
19031 
19032      Time:     System Intialization.
19033 
19034 
19035 
19036 
19037 
19038 init_root_vols                 329            08/03/23     MR12.7^L
19039 
19040 
19041      Meaning:  No conf  partition was found on the  rpv.  It will
19042                be  created by  extracting 4  records from  the hc
19043                partition.
19044 
19045      Action:   No operator action is required.
19046 
19047 
19048                [init_root_vols.pl1]
19049                init_root_vols:    Adding   {bce}   {file}   {log}
19050                partition(s) to rpv.
19051 
19052 
19053      Stream:   BOS Typewriter.
19054 
19055      Time:     System Intialization.
19056 
19057      Meaning:  The  rpv does  not contain  the listed partitions.
19058                The  pages of  the rpv  are being  arranged to add
19059                these  partitions.  This  operation takes  several
19060                minutes.
19061 
19062      Action:   No operator action is required.
19063 
19064 
19065                [init_root_vols.pl1]
19066                init_root_vols:   bce  partition  is  XXX records,
19067                must be YYY.
19068 
19069 
19070      Stream:   BOS Typewriter (Crashes system)
19071 
19072      Time:     System Intialization.
19073 
19074      Meaning:  The  bce  partition  defined  on  the  rpv  is not
19075                sufficiently large.
19076 
19077      Action:   Rebuild  the  rpv  to  have  a  large  enough  bce
19078                partition.  Contact the system programming staff.
19079 
19080 
19081 
19082                [init_root_vols.pl1]
19083                init_root_vols:   DISK_VOL appears  twice on  root
19084                cards.
19085 
19086 
19087      Stream:   BOS Typewriter (Crashes system)
19088 
19089      Time:     System Intialization.
19090 
19091      Meaning:  The volume DISK_VOL appears  more than once on the
19092                ROOT config card(s).
19093 
19094 
19095 
19096 init_root_vols                 330            08/03/23     MR12.7^L
19097 
19098 
19099      Action:   Fix the config deck and try again.
19100 
19101 
19102                [init_root_vols.pl1]
19103                init_root_vols:   DISK_VOL  is  not  the  rpv, but
19104                rather is VOLUME.
19105 
19106 
19107      Stream:   BOS Typewriter (Crashes system)
19108 
19109      Time:     System Intialization.
19110 
19111      Meaning:  The   label   for   the   RPV   is   inconsistent.
19112                label.root.here does not agree with other data, or
19113                an  incorrect pack is  mounted on the  first drive
19114                specified by the "root" card.
19115 
19116      Action:   Reload/restore,  or  patch   the  RPV  label  back
19117                together or correctly mount the RPV.
19118 
19119 
19120 
19121                [init_root_vols.pl1]
19122                init_root_vols:  Error adding partitions to rpv on
19123                DISK_VOL.  ERROR_MESSAGE
19124 
19125 
19126      Stream:   BOS Typewriter (Crashes system)
19127 
19128      Time:     System Intialization.
19129 
19130      Meaning:  It was  not possible to add the  new partitions to
19131                the rpv.  This message will be preceeded by a more
19132                informative message.
19133 
19134      Action:   Depending on the previous message, either a reboot
19135                should  be attempted  or the  rpv will  need to be
19136                rebuilt.
19137 
19138 
19139 
19140                [init_root_vols.pl1]
19141                init_root_vols:   Error  reading  DISK_VOL  label.
19142                PROBLEM ERROR_MESSAGE
19143 
19144 
19145      Stream:   BOS Typewriter (Crashes system)
19146 
19147      Time:     System Intialization.
19148 
19149      Meaning:  An error has been  detected attempting to read the
19150                label of DISK_VOL.
19151 
19152 
19153 
19154 init_root_vols                 331            08/03/23     MR12.7^L
19155 
19156 
19157      Action:   Correct problem and type "go" to retry the read.
19158 
19159 
19160                [init_root_vols.pl1]
19161                init_root_vols:    Error  reading  RPV   label  on
19162                DISK_VOL.  PROBLEM ERROR_MESSAGE
19163 
19164 
19165      Stream:   BOS Typewriter (Crashes system)
19166 
19167      Time:     System Intialization.
19168 
19169      Meaning:  An error has been  detected attempting to read the
19170                label of the RPV.
19171 
19172      Action:   Correct problem and type "go" to retry the read.
19173 
19174 
19175                [init_root_vols.pl1]
19176                init_root_vols:    Error  writing  rpv   label  on
19177                DISK_VOL.  ERROR_MESSAGE
19178 
19179 
19180      Stream:   BOS Typewriter (Crashes system)
19181 
19182      Time:     System Intialization.
19183 
19184      Meaning:  An  i/o prevented updating  the rpv label  to show
19185                the new partitions.
19186 
19187      Action:   Correct problem and type "go" to retry the write.
19188 
19189 
19190                [init_root_vols.pl1]
19191                init_root_vols:   Invalid  device   on  root  card
19192                DISK_VOL.
19193 
19194 
19195      Stream:   BOS Typewriter (Crashes system)
19196 
19197      Time:     System Intialization.
19198 
19199      Meaning:  A  root  card  has  been  found  with  an  invalid
19200                DISK_VOL.
19201 
19202      Action:   Change the config deck and try again.
19203 
19204 
19205                [init_root_vols.pl1]
19206                init_root_vols:   Maximum of   LIMIT RLV  vols has
19207                been exceeded.
19208 
19209 
19210 
19211 
19212 init_root_vols                 332            08/03/23     MR12.7^L
19213 
19214 
19215      Stream:   BOS Typewriter (Crashes system)
19216 
19217      Time:     System Intialization.
19218 
19219      Meaning:  The "root" card in  the config deck specified more
19220                RLV volumes than the system can handle.
19221 
19222      Action:   Change the config deck and try again.
19223 
19224 
19225                [init_root_vols.pl1]
19226                init_root_vols:    No  part   hc  on   RPV  volume
19227                DISK_VOL.
19228 
19229 
19230      Stream:   BOS Typewriter (Crashes system)
19231 
19232      Time:     System Intialization.
19233 
19234      Meaning:  Disk  DISK_VOL was specified  on a "root"  card as
19235                the  RPV,  but  does  not  have  a  hardcore  (hc)
19236                partition.
19237 
19238      Action:   The "root" card is incorrect, or the wrong pack is
19239                mounted on the first drive described by the "root"
19240                cards.
19241 
19242 
19243 
19244                [init_root_vols.pl1]
19245                init_root_vols:   No room  in rpv  label for  conf
19246                partition.
19247 
19248 
19249      Stream:   BOS Typewriter (Crashes system)
19250 
19251      Time:     BOS Typewriter.
19252 
19253      Meaning:  The  partition  map  for  the  rpv  did  not  have
19254                sufficient room to add the conf partition.
19255 
19256      Action:   The  rpv will  need  to  be rebuilt.   Contact the
19257                system programming staff.
19258 
19259 
19260 
19261                [init_root_vols.pl1]
19262                init_root_vols:    No  room   in  rpv   label  for
19263                partitions.
19264 
19265 
19266      Stream:   BOS Typewriter (Crashes system)
19267 
19268 
19269 
19270 init_root_vols                 333            08/03/23     MR12.7^L
19271 
19272 
19273      Time:     System Intialization.
19274 
19275      Meaning:  The  rpv label  does not  have enough  room in the
19276                partition  map  for  the  new  bce,  file  or  log
19277                partitions.
19278 
19279      Action:   The  rpv will  need  to  be rebuilt.   Contact the
19280                system programming staff.
19281 
19282 
19283 
19284                [init_root_vols.pl1]
19285                init_root_vols:  No root card.
19286 
19287 
19288      Stream:   BOS Typewriter (Crashes system)
19289 
19290      Time:     System Intialization.
19291 
19292      Meaning:  No "root"  card(s) were found in  the config deck.
19293                At least one must be present, defining the RPV and
19294                other RLV volumes.
19295 
19296      Action:   Fix the config deck and reboot.
19297 
19298 
19299                [init_root_vols.pl1]
19300                init_root_vols:   root card  specifies nonexistent
19301                drive DISK_VOL.
19302 
19303 
19304      Stream:   BOS Typewriter (Crashes system)
19305 
19306      Time:     System Intialization.
19307 
19308      Meaning:  The volume DISK_VOL, specified in the config deck,
19309                is not defined by the prph dskX cards.
19310 
19311      Action:   Fix the config deck and reboot.
19312 
19313 
19314                [init_root_vols.pl1]
19315                init_root_vols:  RPV not found.
19316 
19317 
19318      Stream:   BOS Typewriter (Crashes system)
19319 
19320      Time:     System Intialization.
19321 
19322      Meaning:  None of  the disk volumes specified  in the "root"
19323                card(s) admitted to being the RPV.
19324 
19325 
19326 
19327 
19328 init_root_vols                 334            08/03/23     MR12.7^L
19329 
19330 
19331      Action:   Check  to be sure  the drive on  which the RPV  is
19332                mounted is specified first on the "root" card(s).
19333 
19334 
19335 
19336                [init_root_vols.pl1]
19337                init_root_vols:     RPV     specified    in    the
19338                configuration   deck   (DRIVE)   does   not  match
19339                sys_boot_info (DRIVE).
19340 
19341 
19342      Stream:   BOS Typewriter (Crashes system)
19343 
19344      Time:     System Intialization.
19345 
19346      Meaning:  The RPV defined  on the root card is  not the same
19347                as the RPV that is currently being used.
19348 
19349      Action:   Fix the config deck and try again.
19350 
19351 
19352                [init_scavenger_data.pl1]
19353                init_scavenger_data:                scavenger_data
19354                inconsistency.
19355 
19356 
19357      Time:     System Intialization.
19358 
19359      Stream:   BOS Typewriter (Crashes system)
19360 
19361      Meaning:  An   error   was   encountered   initializing  the
19362                scavenger's data base.
19363 
19364      Action:   Contact the system programming staff.
19365 
19366 
19367                [init_scavenger_data.pl1]
19368                init_scavenger_data:  scavenger_data too small.
19369 
19370 
19371      Stream:   BOS Typewriter (Crashes system)
19372 
19373      Time:     System Intialization.
19374 
19375      Meaning:  The  size  of  the  scavenger_data  segment is too
19376                small.   It  can  be  increased  by  the TBLS SCAV
19377                config card.   It must be  at least 68KW,  with an
19378                additional   67KW  for  each   additional  process
19379                (beyond   1)    which   is   to    be   scavenging
19380                simultaneously.
19381 
19382      Action:   Correct the configuration deck and reboot.
19383 
19384 
19385 
19386 init_scu                       335            08/03/23     MR12.7^L
19387 
19388 
19389 
19390 
19391                [init_scu.pl1]
19392                init_scu:   Warning -  Not all  of MEM  Y will  be
19393                used.
19394 
19395 
19396      Stream:   BOS Typewriter.
19397 
19398      Time:     System Intialization.
19399 
19400      Meaning:  The actual amount of memory  present in MEM Y does
19401                not agree  with the config deck.  Only  as much as
19402                the configuration deck specifies will be used.
19403 
19404      Action:   If  this is  an unintentional  error, correct  the
19405                configuration deck before the next bootload.
19406 
19407 
19408 
19409                [init_sst.pl1]
19410                init_sst:   insufficient   storage  available  for
19411                sst_seg and core map.
19412 
19413 
19414      Stream:   BOS Typewriter (Crashes system)
19415 
19416      Time:     System Intialization.
19417 
19418      Meaning:  Not  enough main  storage was  available to create
19419                the  sst_seg  during  initialization.   The system
19420                tape may  be bad, or the configuration  may be too
19421                small, or  the system parameters specified  in the
19422                configuration    deck   may   be    incorrect   or
19423                inconsistent  with  the  amount  of  main  storage
19424                available.
19425 
19426      Action:   Follow  normal  recovery  procedures.   Check  the
19427                configuration and the CONFIG deck $boot_tape
19428 
19429 
19430 
19431                [init_sst.pl1]
19432                init_sst:   No SST card  in config deck.   One has
19433                been added:  SST N N N N
19434 
19435 
19436      Stream:   BOS Typewriter (sounds beeper)
19437 
19438      Time:     System Intialization.
19439 
19440      Meaning:  No SST  card was found  in the config  deck.  ASTE
19441                pool sizes of N N N N have been set as defaults.
19442 
19443 
19444 init_sst                       336            08/03/23     MR12.7^L
19445 
19446 
19447 
19448 
19449                [init_stack_0.pl1]
19450                init_stack_0:   Error  creating  >sl1>XXXXXX  from
19451                YYYYY.  Retrying.
19452 
19453 
19454      Stream:   BOS Typewriter.
19455 
19456      Time:     System Intialization.
19457 
19458      Meaning:  An error  was encountered in creating  the stack_0
19459                segment XXXXXX.  The error  was returned by module
19460                YYYYYY,  and   is  described  in  detail   in  the
19461                following  message.  init_stack_0 will  attempt to
19462                correct the problem by renaming the segment XXXXXX
19463                to   stack_0.<unique  name>,   deleting  it,   and
19464                retrying the creation of segment XXXXXX once.
19465 
19466      Action:   No action is required if the above actions correct
19467                the problem.   If the message persists,  it may be
19468                symptomatic of hardware  or software problems, and
19469                it  should  be  brought  to  the  attention of the
19470                System Programming Staff.
19471 
19472 
19473 
19474                [init_stack_0.pl1]
19475                init_stack_0:   Error  creating  >sl1>XXXXXX  from
19476                YYYYYY.  Stack skipped.
19477 
19478 
19479      Stream:   BOS Typewriter.
19480 
19481      Time:     System Intialization.
19482 
19483      Meaning:  An error  was encountered in creating  the stack_0
19484                segment XXXXXX.  The error  was returned by module
19485                YYYYYY,  and   is  described  in  detail   in  the
19486                following  message.   This   error  could  not  be
19487                corrected  by  renaming   the  segment  XXXXXX  to
19488                stack_0.<unique  name>, deleting it,  and retrying
19489                the creation of segment  XXXXXX once.  The stack_0
19490                represented  by  segment  XXXXXX  is  skipped, and
19491                there will be one  fewer stack_0 than specified by
19492                the  max_max_eligible  tuning  parameter  for each
19493                message of this sort.
19494 
19495      Action:   This  message may  be symptomatic  of hardware  or
19496                software  problems.  It  should be  brought to the
19497                attention of the System Programming Staff.
19498 
19499 
19500 
19501 
19502 init_sys_var                   337            08/03/23     MR12.7^L
19503 
19504 
19505 
19506 
19507                [init_sys_var.pl1]
19508                init_sys_var:  max_hproc_segno < hcscnt of XXX
19509 
19510 
19511      Stream:   BOS Typewriter (Crashes system)
19512 
19513      Time:     System Intialization.
19514 
19515      Meaning:  The  upper  bound  of  the  descriptor segment for
19516                hardcore processes is too small.  This indicates a
19517                logic  error in the  supervisor, or CPU  or memory
19518                hardware problems.
19519 
19520      Action:   Follow normal recovery procedures.  $boot_tape
19521 
19522 
19523 
19524                [init_syserr_log.pl1]
19525                init_syserr_log:   Cannot  create  logger process.
19526                ERROR-MESSAGE
19527 
19528 
19529      Stream:   BOS Typewriter.
19530 
19531      Time:     System Intialization.
19532 
19533      Meaning:  This indicates a logic error in the supervisor, or
19534                CPU  or  memory   hardware  problems.   No  syserr
19535                messages will be logged during this bootload.
19536 
19537      Action:   Follow normal recovery procedures.
19538 
19539 
19540                [init_syserr_log.pl1]
19541                init_syserr_log:   Cannot  get  last  message info
19542                from paged syserr log PTR.  ERROR-MESSAGE
19543 
19544 
19545      Stream:   BOS Typewriter.
19546 
19547      Time:     System Intialization.
19548 
19549      Meaning:  This indicates a logic error in the supervisor, or
19550                CPU or memory hardware problems.
19551 
19552      Action:   Follow  normal  recovery  procedures.   It  may be
19553                necessary to  reinitialize the LOG  partition with
19554                the BCE test_disk command after this error.
19555 
19556 
19557 
19558 
19559 
19560 init_syserr_log                338            08/03/23     MR12.7^L
19561 
19562 
19563                [init_syserr_log.pl1]
19564                init_syserr_log:   Cannot  get  service  bit  from
19565                paged syserr log PTR.  MESSAGE
19566 
19567 
19568      Stream:   BOS Typewriter.
19569 
19570      Time:     System Intialization.
19571 
19572      Meaning:  This indicates a logic error in the supervisor, or
19573                CPU  or  memory  hardware  problems.   Some  error
19574                occurred when  attempting to check the  in service
19575                bit for the specified ring 0 paged log segment.
19576 
19577      Action:   No operator action is required.  The log partition
19578                will be automatically reinitialized.
19579 
19580 
19581 
19582                [init_syserr_log.pl1]
19583                init_syserr_log:   Cannot initialize  paged syserr
19584                log PTR.
19585 
19586 
19587      Stream:   BOS Typewriter (Crashes system)
19588 
19589      Time:     System Intialization.
19590 
19591      Meaning:  This indicates a logic error in the supervisor, or
19592                CPU or memory hardware problems.
19593 
19594      Action:   Follow normal recovery procedures.
19595 
19596 
19597                [init_syserr_log.pl1]
19598                init_syserr_log:  Cannot write  initial message to
19599                paged syserr log PTR.  ERROR-MESSAGE
19600 
19601 
19602      Stream:   BOS Typewriter (Crashes system)
19603 
19604      Time:     System Intialization.
19605 
19606      Meaning:  This indicates a logic error in the supervisor, or
19607                CPU or memory hardware problems.
19608 
19609      Action:   Follow  normal  recovery  procedures.   It  may be
19610                necessary to  reinitialize the LOG  partition with
19611                the BCE test_disk command after this error.
19612 
19613 
19614 
19615                [init_syserr_log.pl1]
19616 
19617 
19618 init_syserr_log                339            08/03/23     MR12.7^L
19619 
19620 
19621                init_syserr_log:     Converting   MR10.2    syserr
19622                partition.
19623 
19624 
19625      Stream:   BOS Typewriter.
19626 
19627      Time:     System Intialization.
19628 
19629      Meaning:  This message occurs during the first bootload with
19630                an MR11.0 system tape,  and indicates that the LOG
19631                partition is now in the new format.
19632 
19633      Action:   No operator action is required.
19634 
19635 
19636                [init_syserr_log.pl1]
19637                init_syserr_log:     LOG     partition    damaged.
19638                Reinitializing.
19639 
19640 
19641      Stream:   BOS Typewriter (sounds beeper)
19642 
19643      Time:     System Intialization.
19644 
19645      Meaning:  The LOG partition has been damaged.  Some messages
19646                may be lost if the previous shutdown was caused by
19647                a   crash.    The   partition   is   automatically
19648                reinitialized.
19649 
19650      Action:   Follow normal recovery procedures.
19651 
19652 
19653                [init_syserr_log.pl1]
19654                init_syserr_log:   No LOG partition  found, syserr
19655                logging disabled.
19656 
19657 
19658      Stream:   BOS Typewriter (Crashes system)
19659 
19660      Time:     System Intialization.
19661 
19662      Meaning:  The  system requires  a LOG  partition on  the RPV
19663                disk  to  hold  syserr  messages  before  they are
19664                copied into >sc1>syserr_log.   This partition must
19665                exist  on the  volume, and  be defined  by a "PART
19666                LOG" card in the config deck.
19667 
19668      Action:   Create a LOG partition on the RPV and define it in
19669                the config deck, then  re-boot.  The LOG partition
19670                should be at least 200 records long, and may be as
19671                large as 513.
19672 
19673 
19674 
19675 
19676 init_syserr_log                340            08/03/23     MR12.7^L
19677 
19678 
19679 
19680 
19681                [init_syserr_log.pl1]
19682                init_syserr_log:  Service  bit off for  live paged
19683                syserr log PTR.
19684 
19685 
19686      Stream:   BOS Typewriter.
19687 
19688      Time:     System Intialization.
19689 
19690      Meaning:  The in service flag for the specified ring 0 paged
19691                log segment was found off.  Being this is supposed
19692                to be  the live log, an error  is indicated.  This
19693                may occur when booting after a system crash.
19694 
19695      Action:   No  operator action  is required.   The syserr log
19696                partition will be automatically reinitialized.
19697 
19698 
19699 
19700                [init_syserr_log.pl1]
19701                init_syserr_log:  Size of PTR  larger on disk than
19702                in header.
19703 
19704 
19705      Stream:   BOS Typewriter (Crashes system)
19706 
19707      Time:     System Intialization.
19708 
19709      Meaning:  The LOG partition has been damaged.  Some messages
19710                may be lost if the previous shutdown was caused by
19711                a crash.
19712 
19713      Action:   Reinitialize  the  LOG   partition  with  the  BCE
19714                test_disk command and re-boot.
19715 
19716 
19717                [init_syserr_log.pl1]
19718                init_syserr_log:     Size   of   wired    log   is
19719                inconsistent.
19720 
19721 
19722      Stream:   BOS Typewriter (Crashes system)
19723 
19724      Time:     System Intialization.
19725 
19726      Meaning:  The    definitions    in    syserr_data.cds    are
19727                inconsistent  with those  in syserr_data.incl.pl1.
19728                This indicates a programming error.
19729 
19730      Action:   Follow normal recovery procedures.
19731 
19732 
19733 
19734 init_syserr_log                341            08/03/23     MR12.7^L
19735 
19736 
19737 
19738 
19739                [init_syserr_log.pl1]
19740                init_syserr_log:  Unable to  retrieve IPC operands
19741                from APTE.  Syserr log copying disabled.
19742 
19743 
19744      Stream:   BOS Typewriter.
19745 
19746      Time:     System Intialization.
19747 
19748      Meaning:  This indicates a logic error in the supervisor, or
19749                CPU  or  memory   hardware  problems.   No  syserr
19750                messages will be logged during this bootload.
19751 
19752      Action:   Follow normal recovery procedures.
19753 
19754 
19755                [init_toehold.pl1]
19756                init_toehold:  No "bce" partition on rpv.  Rebuild
19757                the RPV to add one.
19758 
19759 
19760      Stream:   BOS Typewriter (Crashes system)
19761 
19762      Time:     System Intialization.
19763 
19764      Meaning:  The  partition used  to hold  the bootload command
19765                environment is missing from the rpv.
19766 
19767      Action:   A rebuild of the rpv is necessary.
19768 
19769 
19770                [init_toehold.pl1]
19771                init_toehold:   Unable  to  save  bootload Multics
19772                image to disk.
19773 
19774 
19775      Stream:   BOS Typewriter (Crashes system)
19776 
19777      Time:     System Intialization.
19778 
19779      Meaning:  An  i/o error  prevented the  establishment of the
19780                bce crash handler.
19781 
19782 
19783                [init_toehold.pl1]
19784                init_toehold:  Unable to  save safe_config_deck to
19785                disk.
19786 
19787 
19788      Stream:   BOS Typewriter (sounds beeper)
19789 
19790 
19791 
19792 init_toehold                   342            08/03/23     MR12.7^L
19793 
19794 
19795      Time:     System Intialization.
19796 
19797      Meaning:  The  safe_config_deck,  used  to  re-establish bce
19798                when a failure of bce  itself occurs, could not be
19799                updated to  disk.  A future failure of  bce may be
19800                catastrophic.
19801 
19802      Action:   Try  performing a  reinitialize operation,  making
19803                sure that the config deck is perfect.
19804 
19805 
19806 
19807                [init_volmap_seg.pl1]
19808                init_volmap_seg:  Records  left on dskX_NN(PVNAME)
19809                changed from X to Y.
19810 
19811 
19812      Stream:   Logged in SYSERR log.
19813 
19814      Time:     During  system initialization as  physical volumes
19815                of  the Root  Logical Volume  (RLV) are  accepted,
19816                during system  start_up as physical  volumes which
19817                were mounted at the last shutdown are accepted, or
19818                when a physical volume is mounted and accepted.
19819 
19820      Meaning:  A VTOC header was  encountered which did not agree
19821                with  the  Volume  Map.   This  will  occur when a
19822                volume  which  was  not   shut  down  properly  is
19823                mounted.
19824 
19825      Action:   Contact the system programming staff.
19826 
19827 
19828                [init_volmap_seg.pl1]
19829                init_volmap_seg:   Unable  to   get  NK  ASTE  for
19830                volmap_seg.
19831 
19832 
19833      Stream:   BOS Typewriter (Crashes system)
19834 
19835      Time:     During  system initialization as  physical volumes
19836                of  the Root  Logical Volume  (RLV) are  accepted,
19837                during system  start_up as physical  volumes which
19838                were mounted at the last shutdown are accepted, or
19839                when a physical volume is mounted and accepted.
19840 
19841      Meaning:  An  NK ASTE  was not  available for  accessing the
19842                Volume Map.  The most likely cause is an ASTE pool
19843                size which is too small.
19844 
19845      Action:   Follow  normal recovery procedures.   Increase the
19846                number of  ASTEs in the appropriate  pool by means
19847                of the SST configuration card.
19848 
19849 
19850 init_volmap_seg                343            08/03/23     MR12.7^L
19851 
19852 
19853 
19854 
19855                [init_volmap_seg.pl1]
19856                init_volmap_seg:  Unable  to get NK ASTE  for VTOC
19857                header.
19858 
19859 
19860      Stream:   BOS Typewriter (Crashes system)
19861 
19862      Time:     During  system initialization as  physical volumes
19863                of  the Root  Logical Volume  (RLV) are  accepted,
19864                during system  start_up as physical  volumes which
19865                were mounted at the last shutdown are accepted, or
19866                when a physical volume is mounted and accepted.
19867 
19868      Meaning:  An  NK ASTE  was not  available for  accessing the
19869                VTOC  header.  The  most likely  cause is  an ASTE
19870                pool size which is too small.
19871 
19872      Action:   Follow  normal recovery procedures.   Increase the
19873                number of  ASTEs in the appropriate  pool by means
19874                of the SST configuration card.
19875 
19876 
19877 
19878                [init_volmap_seg.pl1]
19879                init_volmap_seg:  Unable to  initialize dumper map
19880                for dskX_NN(PVNAME)
19881 
19882 
19883      Stream:   BOS Typewriter.
19884 
19885      Time:     During  system initialization as  physical volumes
19886                of  the Root  Logical Volume  (RLV) are  accepted,
19887                during system  start_up as physical  volumes which
19888                were mounted at the last shutdown are accepted, or
19889                when a physical volume is mounted and accepted.
19890 
19891      Meaning:  An    unexpected   error   was    encountered   in
19892                initializing  the  backup  queue  bit  map for the
19893                Physical Volume  Dumper.  The volume on  which the
19894                error  occurred  cannot  be  backed  up  with  the
19895                Physical Volume Dumper.
19896 
19897      Action:   Contact the system programming staff.
19898 
19899 
19900                [init_volmap_seg.pl1]
19901                init_volmap_seg:   VTOCEs left  on dskX_NN(PVNAME)
19902                changed from X to Y.
19903 
19904 
19905      Stream:   Logged in SYSERR log.
19906 
19907 
19908 init_volmap_seg                344            08/03/23     MR12.7^L
19909 
19910 
19911      Time:     During  system initialization as  physical volumes
19912                of  the Root  Logical Volume  (RLV) are  accepted,
19913                during system  start_up as physical  volumes which
19914                were mounted at the last shutdown are accepted, or
19915                when a physical volume is mounted and accepted.
19916 
19917      Meaning:  A VTOC header was  encountered which did not agree
19918                with the VTOC Map.  This  will occur when a volume
19919                which was not shut down properly is mounted.
19920 
19921      Action:   Contact the system programming staff.
19922 
19923 
19924                [init_volmap_seg.pl1]
19925                init_volmap_seg:   YYYY volume  inconsistencies on
19926                dskX_NN(PVNAME).  UUUU records  left.  VVVV VTOCEs
19927                left.
19928 
19929 
19930      Stream:   Logged only if the number  of free records and the
19931                number of  free VTOCEs are both  above thresholds.
19932                Logged  and printed  on the  console if  either is
19933                below threshold.
19934 
19935      Time:     During  system initialization as  physical volumes
19936                of  the Root  Logical Volume  (RLV) are  accepted,
19937                during system  start_up as physical  volumes which
19938                were mounted at the last shutdown are accepted, or
19939                when a physical volume is mounted and accepted.
19940 
19941      Meaning:  The   volume  was   not  shut   down  properly  or
19942                inconsistencies were detected while the volume was
19943                mounted.  The  effect of these  inconsistencies is
19944                that free records and free  VTOCEs are lost to the
19945                system.  Lost records and  VTOCEs can be recovered
19946                by a volume salvage.
19947 
19948      Action:   Contact the system programming staff.
19949 
19950 
19951                [init_vtoc_man.pl1]
19952                init_vtoc_man:   Unexpected   error  from  absadr.
19953                Code XX.
19954 
19955 
19956      Stream:   BOS Typewriter (Crashes system)
19957 
19958      Time:     System Intialization.
19959 
19960      Meaning:  The absolute address  of vtoc_buffer_seg could not
19961                be   determined.   This   indicates  hardware   or
19962                software malfunction.
19963 
19964 
19965 
19966 init_vtoc_man                  345            08/03/23     MR12.7^L
19967 
19968 
19969      Action:   Follow normal recovery procedures.
19970 
19971 
19972                [real_initializer.pl1.pmac]
19973                initializer:  Bad root volume.
19974 
19975 
19976      Stream:   BOS Typewriter (Crashes system)
19977 
19978      Time:     System Intialization.
19979 
19980      Meaning:  A volume  specified on a  ROOT card was  found ill
19981                formatted by init_root_vols.
19982 
19983      Action:   Follow normal recovery procedures.
19984 
19985 
19986                [real_initializer.pl1.pmac]
19987                initializer:  bad_dir_ signal raised
19988 
19989 
19990      Stream:   BOS Typewriter (Crashes system)
19991 
19992      Time:     System Intialization.
19993 
19994      Meaning:  During  system  bootload,  directory  control  has
19995                encountered  an invalid  directory.  This  usually
19996                occurs   due  to   damage  to   the  root   or  to
19997                >system_control_1.    The  RPV   is  automatically
19998                scheduled for volume salvage.
19999 
20000      Action:   Follow normal recovery procedures.
20001 
20002 
20003                [real_initializer.pl1.pmac]
20004                initializer:  ENTRY_TO_CALL check_stop.
20005 
20006 
20007      Stream:   BOS Typewriter (sounds beeper)
20008 
20009      Time:     System Intialization.
20010 
20011      Meaning:  The initializer  has detected that the  first nine
20012                data  switches on the  CPU contain an  octal "123"
20013                and the STOP number of  the entry to be called and
20014                the current collection_1_phase match the other CPU
20015                data  switches.  The  initializer calls  BCE after
20016                displaying  this  message,   but  before  actually
20017                calling the entry.  The CPU data switches have the
20018                following usage:
20019 
20020                 0  -  8: must  be set to  an octal "123"  for any
20021                          other switches to be valid.
20022 
20023 
20024 initializer                    346            08/03/23     MR12.7^L
20025 
20026 
20027                 9  - 14: area   for   the   BCD   value   of  the
20028                          collection_1_phase to stop in.
20029                 15 - 20: area for  the BCD hundreds digit  of the
20030                          STOP number.
20031                 21 - 26: area for the BCD  tens digit of the STOP
20032                          number.
20033                 27 - 32: area for the BCD  ones digit of the STOP
20034                          number.
20035                 33 - 35: not used or checked.
20036 
20037      Action:   Execute  any BCE   functions desired.   Modify the
20038                setting  of  the  CPU  data  switches as required.
20039                Execute   the   BCE   "go"   function   to  resume
20040                initialization.
20041 
20042 
20043 
20044                [real_initializer.pl1.pmac]
20045                initializer:  intk card missing.
20046 
20047 
20048      Stream:   BOS Typewriter (Crashes system)
20049 
20050      Time:     System Intialization.
20051 
20052      Meaning:  No "intk" card was found in the config deck.
20053 
20054      Action:   $config
20055 
20056 
20057                [real_initializer.pl1.pmac]
20058                initializer:    Multics  SYSID   (VERSION)  syserr
20059                logging initialized.
20060 
20061 
20062      Stream:   Logged in SYSERR log.
20063 
20064      Time:     System Intialization.
20065 
20066      Meaning:  This is the first syserr message produced by every
20067                bootload.   It is produced  as soon as  the syserr
20068                logging mechanism is made operative, which insures
20069                that  it is  the  first  message logged  for every
20070                bootload.  It identifies the system ID and version
20071                of the running system.
20072 
20073      Action:   No operator action is required.
20074 
20075 
20076                [real_initializer.pl1.pmac]
20077                initializer:    Segment   fault   error   by  PPPP
20078                referencing PPPP:  ERROR
20079 
20080 
20081 
20082 initializer                    347            08/03/23     MR12.7^L
20083 
20084 
20085      Stream:   BOS Typewriter (Crashes system)
20086 
20087      Time:     System Intialization.
20088 
20089      Meaning:  During system bootload, a  segment fault error has
20090                occurred.  This  usually indicates running  out of
20091                room on the RLV.  A  BOOT RPVS may recover some of
20092                this space.   The procedure causing the  error and
20093                the segment being referenced are identified, along
20094                with the error message.
20095 
20096      Action:   Follow normal recovery procedures.
20097 
20098 
20099                [real_initializer.pl1.pmac]
20100                initializer:  STOP_NUM  ENTRY_TO_CALL state ISTATE
20101                phase CPHASE.
20102 
20103 
20104      Stream:   BOS Typewriter (sounds beeper)
20105 
20106      Time:     System Intialization.
20107 
20108      Meaning:  The "loud" config parm is currently enabled.  This
20109                message gives the  current stop number (STOP_NUM),
20110                that  can  be  used  to  stop  the  initialization
20111                process   and  return    to  BCE   before  calling
20112                ENTRY_TO_CALL.     The     current    values    of
20113                sys_infoSystem      Intialization.ialization_state
20114                (ISTATE) and  sys_info$collection_1_phase (CPHASE)
20115                are also given.
20116 
20117      Action:   No operator action is required.
20118 
20119 
20120                [dn355_boot_interrupt.pl1]
20121                Invalid bootload interrupt for FNP X, status N
20122 
20123 
20124      Stream:   BOS Typewriter.
20125 
20126      Time:     When bootloading an FNP
20127 
20128      Meaning:  The FNP responded to  the bootload attempt with an
20129                interrupt, but the high-order  bit of the reported
20130                status was  not on.  N is the  reported status (in
20131                octal).
20132 
20133      Action:   Contact the system programming staff.
20134 
20135 
20136                [io_config_init.pl1]
20137 
20138 
20139 
20140 io_config_init                 348            08/03/23     MR12.7^L
20141 
20142 
20143                io_config_init:  Invalid iom  or channel number on
20144                prph NAME card.
20145 
20146 
20147      Stream:   BOS Typewriter (Crashes system)
20148 
20149      Time:     System Intialization.
20150 
20151      Meaning:  The iom number or the channel number is invalid on
20152                the prph card that defines NAME.
20153 
20154      Action:   Fix the config deck.
20155 
20156 
20157                [io_error.pl1]
20158                io_error:   Illegal  address   value  in  call  to
20159                io_manager.
20160 
20161 
20162      Stream:   BOS Typewriter (Crashes system)
20163 
20164      Time:     While system is running.
20165 
20166      Meaning:  An address  that was not  in the required  part of
20167                memory or was not aligned properly was passed in a
20168                call to io_manager.  This  indicates a logic error
20169                in  the  supervisor,  or  CPU  or  memory hardware
20170                problems.
20171 
20172      Action:   Follow  normal recovery  procedures.  Contact  the
20173                system programming staff.
20174 
20175 
20176 
20177                [io_error.pl1]
20178                io_error:   Invalid  channel   index  in  call  to
20179                io_manager.
20180 
20181 
20182      Stream:   BOS Typewriter (Crashes system)
20183 
20184      Time:     While system is running.
20185 
20186      Meaning:  A  channel index  which did  not correspond  to an
20187                assigned logical channel was passed to io_manager.
20188                This indicates a logic error in the supervisor, or
20189                CPU or memory hardware problems.
20190 
20191      Action:   Follow  normal recovery  procedures.  Contact  the
20192                system programming staff.
20193 
20194 
20195 
20196 
20197 
20198 ioam_                          349            08/03/23     MR12.7^L
20199 
20200 
20201                [ioam_.pl1]
20202                ioam_:   The IOAT  is too  small, use  TBLS config
20203                card to increase size.
20204 
20205 
20206      Stream:   BOS Typewriter (sounds beeper)
20207 
20208      Time:     System Intialization.
20209 
20210      Meaning:  The system was  unable to make an entry  in the IO
20211                Assignment  Table.   One  or  more  devices may be
20212                unattachable.
20213 
20214      Action:   Contact the system programming staff.  Correct the
20215                configuration deck before the next bootload.
20216 
20217 
20218 
20219                [ioi_init.pl1]
20220                ioi_init:  Duplicate "prph NAME" card found.
20221 
20222 
20223      Stream:   BOS Typewriter (Crashes system)
20224 
20225      Time:     System Intialization.
20226 
20227      Meaning:  $msg
20228 
20229      Action:   $config
20230 
20231 
20232                [ioi_init.pl1]
20233                ioi_init:   ERROR_CODE  Unable  to  assign channel
20234                CHANID.
20235 
20236 
20237      Stream:   BOS Typewriter (Crashes system)
20238 
20239      Time:     System Intialization.
20240 
20241      Meaning:  A  logical channel could  not be assigned  to IOI.
20242                This indicates a logic error in the supervisor, or
20243                CPU or memory hardware problems.
20244 
20245      Action:   Contact the system programming staff.
20246 
20247 
20248                [ioi_init.pl1]
20249                ioi_init:   ERROR_CODE Unable  to get  the name of
20250                name of iom IOMNO channel CHANNO.
20251 
20252 
20253      Stream:   BOS Typewriter (Crashes system)
20254 
20255 
20256 ioi_init                       350            08/03/23     MR12.7^L
20257 
20258 
20259      Time:     System Intialization.
20260 
20261      Meaning:  An attempt to generate the name of logical channel
20262                CHANNO of iom IOMNO failed.
20263 
20264      Action:   $config
20265 
20266 
20267                [ioi_init.pl1]
20268                ioi_init:  Multiple definitions  of channel CHANID
20269                found for subsystem NAME.
20270 
20271 
20272      Stream:   BOS Typewriter (Crashes system)
20273 
20274      Time:     System Intialization.
20275 
20276      Meaning:  $msg
20277 
20278      Action:   $config
20279 
20280 
20281                [ioi_init.pl1]
20282                ioi_init:   Multiple  definitions  of  device NAME
20283                found.
20284 
20285 
20286      Stream:   BOS Typewriter (Crashes system)
20287 
20288      Time:     System Intialization.
20289 
20290      Meaning:  $msg
20291 
20292      Action:   $config
20293 
20294 
20295                [ioi_init.pl1]
20296                ioi_init:  No cte found for channel CHANID.
20297 
20298 
20299      Stream:   BOS Typewriter (Crashes system)
20300 
20301      Time:     System Intialization.
20302 
20303      Meaning:  This indicates a logic error in the supervisor, or
20304                CPU or memory hardware problems.
20305 
20306      Action:   Contact the system programming staff.
20307 
20308 
20309                [ioi_init.pl1]
20310                ioi_init:  No entry for NAME found in disk_data.
20311 
20312 
20313 
20314 ioi_init                       351            08/03/23     MR12.7^L
20315 
20316 
20317      Stream:   BOS Typewriter (Crashes system)
20318 
20319      Time:     System Intialization.
20320 
20321      Meaning:  This indicates a logic error in the supervisor, or
20322                CPU or memory hardware problems.
20323 
20324      Action:   Contact the system programming staff.
20325 
20326 
20327                [ioi_init.pl1]
20328                ioi_init:  No matching "prph NAME" found for "chnl
20329                NAME".
20330 
20331 
20332      Stream:   BOS Typewriter (Crashes system)
20333 
20334      Time:     System Intialization.
20335 
20336      Meaning:  $msg
20337 
20338      Action:   $config
20339 
20340 
20341                [ioi_masked.pl1]
20342                ioi_masked$interrupt:  absadr failed.
20343 
20344 
20345      Stream:   BOS Typewriter (Crashes system)
20346 
20347      Time:     While system is running.
20348 
20349      Meaning:  A call to the  absadr function returned a non-zero
20350                error code,  indicating that the  absolute address
20351                of the workspace could not be obtained.  Since the
20352                workspace is  wired, this error should  never have
20353                occurred.
20354 
20355      Action:   Contact  the  system  programming  staff.   Follow
20356                normal recovery procedures.
20357 
20358 
20359 
20360                [ioi_masked.pl1]
20361                ioi_masked$interrupt:  I/O error.
20362 
20363 
20364      Stream:   Logged in SYSERR log.
20365 
20366      Time:     While system is running.
20367 
20368 
20369 
20370 
20371 
20372 ioi_masked$interrupt           352            08/03/23     MR12.7^L
20373 
20374 
20375      Meaning:  An  error,  or  accumulation  of  like errors, has
20376                occured.  All  needed information is  contained in
20377                the binary portion of the entry.
20378 
20379      Action:   No operator action is required.
20380 
20381 
20382                [ioi_masked.pl1]
20383                ioi_masked$interrupt:    Interrupt  for   inactive
20384                device (device DEVID).  Type go to continue.
20385 
20386 
20387 
20388      Stream:   BOS Typewriter (Crashes system)
20389 
20390      Time:     While system is running.
20391 
20392      Meaning:  An interrupt has been  received over a channel for
20393                which  the device  is not  marked "active".   This
20394                could indicate an error in  the I/O hardware or in
20395                the setting/checking of the device active flag.
20396 
20397      Action:   Typing  "go"  at  BCE  will  cause  Multics  to be
20398                reentered and ioi_masked to dismiss this error and
20399                properly cleanup.
20400 
20401 
20402 
20403                [ioi_masked.pl1]
20404                ioi_masked$interrupt:  Special.
20405 
20406 
20407      Stream:   Logged in SYSERR log.
20408 
20409      Time:     While system is running.
20410 
20411      Meaning:  A  special interrupt,  or accumulation  of special
20412                interrupts,  has occured.  All  needed information
20413                is contained in the binary portion of the entry.
20414 
20415      Action:   No operator action is required.
20416 
20417 
20418                [ioi_masked.pl1]
20419                ioi_masked$timer:    Attempt    to   unwire   NULL
20420                workspace.  (device DEVID).
20421 
20422 
20423      Stream:   BOS Typewriter.
20424 
20425      Time:     While system is running.
20426 
20427 
20428 
20429 
20430 ioi_masked$timer               353            08/03/23     MR12.7^L
20431 
20432 
20433      Meaning:  Device  entry flag  and time  stamp indicated that
20434                its  workspace  required  unwiring.   However  the
20435                pointer  to the ASTE  for the workspace  was null.
20436                This indicates a logic error in the supervisor, or
20437                CPU or memory hardware problems.
20438 
20439      Action:   Contact  the  system  programming  staff.   Follow
20440                normal recovery procedures.
20441 
20442 
20443 
20444                [ioi_masked.pl1]
20445                ioi_masked$timer:    Timeout  on   channel  CHANID
20446                (device DEVID).
20447 
20448 
20449      Stream:   BOS Typewriter.
20450 
20451      Time:     While system is running.
20452 
20453      Meaning:  The time limit has expired waiting for status from
20454                CHANID for  a previous connect.  The  channel will
20455                be masked "OFF", then unmasked if multiple devices
20456                exist  (i.e.   tapes  and  disks)  so that special
20457                interrupts can be received.
20458 
20459      Action:   Contact    your     Customer    Service    Account
20460                Representative if the errors persist.
20461 
20462 
20463 
20464                [ioi_masked.pl1]
20465                ioi_masked$timer:   Timeout on channel  CHANID (no
20466                device).
20467 
20468 
20469      Stream:   BOS Typewriter.
20470 
20471      Time:     While system is running.
20472 
20473      Meaning:  The time limit has expired waiting for status from
20474                CHANID for the connect to unmask the channel.  The
20475                channel  will be  masked "OFF",  then then  unmask
20476                will be tried again.
20477 
20478      Action:   Contact    your     Customer    Service    Account
20479                Representative if the errors persist.
20480 
20481 
20482 
20483                [ioi_masked.pl1]
20484                ioi_masked:   Channel CHANID not  responding, will
20485                remain masked.
20486 
20487 
20488 ioi_masked                     354            08/03/23     MR12.7^L
20489 
20490 
20491      Stream:   BOS Typewriter.
20492 
20493      Time:     While system is running.
20494 
20495      Meaning:  The time limit has expired waiting for status from
20496                a previous unmask connect (reset-status idcw).  It
20497                is apparent  that the channel is  inoperative.  No
20498                further  attempt  will  be  made  to  re-open  the
20499                channel.
20500 
20501      Action:   Contact    your     Customer    Service    Account
20502                Representative if the errors persist.
20503 
20504 
20505 
20506                [ioi_masked.pl1]
20507                ioi_masked:   Lock  for  subsystem  SUBSYSTEM  not
20508                locked to process OOOOOO.
20509 
20510 
20511      Stream:   BOS Typewriter (Crashes system)
20512 
20513      Time:     While system is running.
20514 
20515      Meaning:  An unlock of the subsystem lock was attempted, but
20516                is was not locked by this process.  This indicates
20517                a logic error in the  supervisor, or CPU or memory
20518                hardware problems.
20519 
20520      Action:   Contact  the  system  programming  staff.   Follow
20521                normal recovery procedures.
20522 
20523 
20524 
20525                [ioi_masked.pl1]
20526                ioi_masked:  Mylock error on subsystem SUBSYSTEM.
20527 
20528 
20529      Stream:   BOS Typewriter (Crashes system)
20530 
20531      Time:     While system is running.
20532 
20533      Meaning:  An lock  of the subsystem lock  was attempted, but
20534                is  was  already  locked  by  this  process.  This
20535                indicates a logic error  in the supervisor, or CPU
20536                or memory hardware problems.
20537 
20538      Action:   Contact  the  system  programming  staff.   Follow
20539                normal recovery procedures.
20540 
20541 
20542 
20543                [ioi_masked.pl1]
20544 
20545 
20546 ioi_masked                     355            08/03/23     MR12.7^L
20547 
20548 
20549                ioi_masked:  No Ext.  Stat.  with MAJOR/SUB status
20550                on chnl CHANID (DEVID).
20551 
20552 
20553      Stream:   Logged in SYSERR log.
20554 
20555      Time:     While system is running.
20556 
20557      Meaning:  An error status has occured that requires detailed
20558                status.   This CHANID   should have  supplied this
20559                with the status, but did not.  This CHANID is also
20560                not capable of requesting the detailed status.  An
20561                octal  dump  of  the  status_entry  area  will  be
20562                displayed along with the error message.
20563 
20564      Action:   No operator action is required.
20565 
20566 
20567                [ioi_verify_lock.pl1]
20568                ioi_verify_lock:  Force unlocked device entry lock
20569                #N for USERID.
20570 
20571 
20572      Stream:   BOS Typewriter.
20573 
20574      Time:     While system is running.
20575 
20576      Meaning:  This indicates a logic error in the supervisor, or
20577                CPU  or  memory  hardware  problems.   The process
20578                encountered a  condition in ring-0 which  forced a
20579                crawlout.  IOI unlocks all locks for the process.
20580 
20581      Action:   Contact the system programming staff.
20582 
20583 
20584                [ioi_verify_lock.pl1]
20585                ioi_verify_lock:  Force unlocked  group entry lock
20586                for USERID.
20587 
20588 
20589      Stream:   BOS Typewriter.
20590 
20591      Time:     While system is running.
20592 
20593      Meaning:  This indicates a logic error in the supervisor, or
20594                CPU  or  memory  hardware  problems.   The process
20595                encountered a  condition in ring-0 which  forced a
20596                crawlout.  IOI unlocks all locks for the process.
20597 
20598      Action:   Contact the system programming staff.
20599 
20600 
20601                [ioi_verify_lock.pl1]
20602 
20603 
20604 ioi_verify_lock                356            08/03/23     MR12.7^L
20605 
20606 
20607                ioi_verify_lock:  Force  unlocked reconfigure lock
20608                for USERID.
20609 
20610 
20611      Stream:   BOS Typewriter.
20612 
20613      Time:     While system is running.
20614 
20615      Meaning:  This indicates a logic error in the supervisor, or
20616                CPU  or  memory  hardware  problems.   The process
20617                encountered a  condition in ring-0 which  forced a
20618                crawlout.  IOI unlocks all locks for the process.
20619 
20620      Action:   Contact the system programming staff.
20621 
20622 
20623                [iom_data_init.pl1]
20624                IOM model of "nsa" for  IOM TAG will be changed to
20625                "iom".
20626 
20627 
20628      Stream:   $announce
20629 
20630      Time:     System Intialization.
20631 
20632      Meaning:  The model field of this  IOM card should be "iom".
20633                The system will correct it for this boot.
20634 
20635      Action:   Correct configuration deck before next boot.
20636 
20637 
20638                [iom_data_init.pl1]
20639                iom_data_init:   Bad   IOM  tag  TAG.    IOM  card
20640                ignored.
20641 
20642 
20643      Stream:   BOS Typewriter (Crashes system)
20644 
20645      Time:     System Intialization.
20646 
20647      Meaning:  An IOM card contained an  IOM tag other than A, B,
20648                C, or D.
20649 
20650      Action:   Correct configuration deck and reboot.
20651 
20652 
20653                [iom_data_init.pl1]
20654                iom_data_init:  Bad model MODEL  for IOM TAG.  IOM
20655                card ignored.
20656 
20657 
20658      Stream:   BOS Typewriter (Crashes system)
20659 
20660 
20661 
20662 iom_data_init                  357            08/03/23     MR12.7^L
20663 
20664 
20665      Time:     System Intialization.
20666 
20667      Meaning:  The model field for IOM TAG was not recognized.
20668 
20669      Action:   Correct configuration deck and reboot.
20670 
20671 
20672                [iom_data_init.pl1]
20673                iom_data_init:  Bad state STATE  for IOM TAG.  IOM
20674                card ignored.
20675 
20676 
20677      Stream:   BOS Typewriter (Crashes system)
20678 
20679      Time:     System Intialization.
20680 
20681      Meaning:  The state for IOM TAG was neither "on" or "off".
20682 
20683      Action:   Correct configuration deck and reboot.
20684 
20685 
20686                [iom_data_init.pl1]
20687                iom_data_init:  Data not in low 256K.
20688 
20689 
20690      Stream:   BOS Typewriter (Crashes system)
20691 
20692      Time:     System Intialization.
20693 
20694      Meaning:  The IOM data bases are not located in the low 256K
20695                of  memory.  This indicates  a logic error  in the
20696                supervisor, or CPU or memory hardware problems.
20697 
20698      Action:   Correct configuration deck and reboot.
20699 
20700 
20701                [iom_data_init.pl1]
20702                iom_data_init:  Duplicate IOM TAG in config deck.
20703 
20704 
20705      Stream:   BOS Typewriter (Crashes system)
20706 
20707      Time:     System Intialization.
20708 
20709      Meaning:  Two IOM cards specifying IOM tag TAG were found in
20710                the configuration deck.
20711 
20712      Action:   Correct configuration deck and reboot.
20713 
20714 
20715                [iom_data_init.pl1]
20716                iom_data_init:  Error from absadr.
20717 
20718 
20719 
20720 iom_data_init                  358            08/03/23     MR12.7^L
20721 
20722 
20723      Stream:   BOS Typewriter (Crashes system)
20724 
20725      Time:     System Intialization.
20726 
20727      Meaning:  This indicates a logic error in the supervisor, or
20728                CPU or memory hardware problems.
20729 
20730      Action:   Contact the system programming staff.
20731 
20732 
20733                [iom_data_init.pl1]
20734                iom_data_init:  Illegal  port number PORT  for IOM
20735                TAG.
20736 
20737 
20738      Stream:   BOS Typewriter (Crashes system)
20739 
20740      Time:     System Intialization.
20741 
20742      Meaning:  The IOM card for IOM TAG contained an illegal port
20743                number.  The port number must be between 0 and 7.
20744 
20745      Action:   Correct configuration deck and reboot.
20746 
20747 
20748                [iom_data_init.pl1]
20749                iom_data_init:  IOM TAG reuses port PORT.
20750 
20751 
20752      Stream:   BOS Typewriter (Crashes system)
20753 
20754      Time:     System Intialization.
20755 
20756      Meaning:  IOM TAG has been given the same port as some other
20757                active module (CPU or IOM).
20758 
20759      Action:   Correct configuration deck and reboot.
20760 
20761 
20762                [iom_data_init.pl1]
20763                iom_data_init:  No valid IOM cards found.
20764 
20765 
20766      Stream:   BOS Typewriter (Crashes system)
20767 
20768      Time:     System Intialization.
20769 
20770      Meaning:  There were no valid IOM cards in the configuration
20771                deck.
20772 
20773      Action:   Correct configuration deck and reboot.
20774 
20775 
20776 
20777 
20778 iom_data_init                  359            08/03/23     MR12.7^L
20779 
20780 
20781                [iom_data_init.pl1]
20782                iom_data_init:  Unable to  assign overhead channel
20783                for IOM TAG.
20784 
20785 
20786      Stream:   BOS Typewriter (Crashes system)
20787 
20788      Time:     System Intialization.
20789 
20790      Meaning:  Could not set up overhead channel handlers for IOM
20791                TAG.   This   indicates  a  logic  error   in  the
20792                supervisor, or CPU or memory hardware problems.
20793 
20794      Action:   Contact the system programming staff.
20795 
20796 
20797                [iom_error.pl1]
20798                iom_error:   Unexpected level  LEVEL_NUM interrupt
20799                from channel CHNL [Status word - OOOOOOOOOOOO]~
20800 
20801 
20802      Stream:   BOS Typewriter.
20803 
20804      Time:     While system is running.
20805 
20806      Meaning:  The  specified  level  interrupt  has  occured  on
20807                channel  CHNL, either   no channel  assignment was
20808                found  for the specified  channel or there  was no
20809                handler specified  for the channel.  If  CHNL is a
20810                "?",  this indicates  an error  occured converting
20811                the iom  and channel numbers, which  are displayed
20812                in  parenthesis  "(iom  N,  chan_no  N)" after the
20813                question  mark.  The  status word  associated with
20814                the interrupt will be displayed when non-zero.
20815 
20816      Action:   Contact the system programming staff.
20817 
20818 
20819                [iom_overhead.pl1]
20820                iom_overhead:  IOM TAG System fault status STATUS.
20821 
20822 
20823      Stream:   BOS Typewriter.
20824 
20825      Time:     While system is running.
20826 
20827      Meaning:  An IOM system fault  has occurred.  This indicates
20828                a problem in either hardware or system software.
20829 
20830      Action:   Contact the system programming staff.
20831 
20832 
20833                [iom_overhead.pl1]
20834 
20835 
20836 iom_overhead                   360            08/03/23     MR12.7^L
20837 
20838 
20839                iom_overhead:   Status queue  overrun for  IOM TAG
20840                channel CHANNEL.
20841 
20842 
20843      Stream:   BOS Typewriter.
20844 
20845      Time:     While system is running.
20846 
20847      Meaning:  The  IOM has  failed to   refresh the  DCW for  an
20848                overhead  channel.   This   indicates  a  hardware
20849                problem.
20850 
20851      Action:   Contact the system programming staff.
20852 
20853 
20854                [lap_simplex.pl1]
20855                lap_simplex(CHN):   Attempt  to  write  overlength
20856                frame.
20857 
20858 
20859      Stream:   Logged in SYSERR log.
20860 
20861      Time:     While system is running.
20862 
20863      Meaning:  An  attempt was made  to add a  buffer to a  frame
20864                which  didn't have  room for  it.  The  connection
20865                will be crashed.
20866 
20867      Action:   Contact the system programming staff.
20868 
20869 
20870                [lap_simplex.pl1]
20871                lap_simplex(CHN):   Failure,  Link  state:  STATE,
20872                Current  Action:   FUNCTION,  in  ESTATE,  Primary
20873                state:  PSTATE, Secondary state:  SSTATE.
20874 
20875 
20876      Stream:   Logged in SYSERR log.
20877 
20878      Time:     While system is running.
20879 
20880      Meaning:  Normal request to crash the line when the link has
20881                been disconnected  by the FNP.  STATE  is the main
20882                state of the link.   FUNCTION is the last function
20883                the link  processed.  The ESTATE is  the execution
20884                state of the last function.  PSTATE and SSTATE are
20885                the link up substate.
20886 
20887      Action:   Contact the system programming staff.
20888 
20889 
20890                [lap_simplex.pl1]
20891                lap_simplex(CHN):  Invalid subchannel index XXX
20892 
20893 
20894 lap_simplex(CHN)               361            08/03/23     MR12.7^L
20895 
20896 
20897      Stream:   $alarm
20898 
20899      Time:     While system is running.
20900 
20901      Meaning:  Some  call  which  attempted  to  write, process a
20902                control  order   or  process  a   modes  operation
20903                specified a subchannel other than 1.
20904 
20905      Action:   Contact the system programming staff.
20906 
20907 
20908                [lap_simplex.pl1]
20909                lap_simplex(CHN):    Link   disconnected   due  to
20910                mis-matched frame sizes.  CMDR/FRMR frame:  FRAME.
20911 
20912 
20913      Stream:   Logged in SYSERR log.
20914 
20915      Time:     While system is running.
20916 
20917      Meaning:  The  FNP has received  a command reject  (LAPB) or
20918                frame  reject (LAP)  which specified  a reason  of
20919                "wide frame"  on channel CHN.  The  actual level 2
20920                command is  FRAME.  This means the  frame received
20921                by the other end was too long.  Instead of looping
20922                continuously trying  to send this frame,  the link
20923                will be  disconnected.  The maximum frame  size in
20924                the  Multics TTF for  this link should  be checked
20925                against the size expected by  the other end of the
20926                link, and corrected.
20927 
20928      Action:   Contact the system programming staff.
20929 
20930 
20931                [lap_simplex.pl1]
20932                lap_simplex(CHN):  Unexpected  interrupt TYPE DATA
20933                received.
20934 
20935 
20936      Stream:   Logged in SYSERR log.
20937 
20938      Time:     While system is running.
20939 
20940      Meaning:  An unexpected MCM interrupt was processed.
20941 
20942      Action:   Contact the system programming staff.
20943 
20944 
20945                [lap_simplex.pl1]
20946                lap_simplex(CHN):   Write  failed  to  take  whole
20947                frame, discarding rest.
20948 
20949 
20950 
20951 
20952 lap_simplex(CHN)               362            08/03/23     MR12.7^L
20953 
20954 
20955      Stream:   Logged in SYSERR log.
20956 
20957      Time:     While system is running.
20958 
20959      Meaning:  A attempt  to write a  whole frame failed,  only a
20960                part of it was taken.   An attempt will be made to
20961                continue.
20962 
20963      Action:   Contact the system programming staff.
20964 
20965 
20966                [lg_ctl_.pl1]
20967                lg_ctl_$logout:             called            with
20968                active=N,{^}proc_create_ok  for NAME.PROJ  TTY ute
20969                MM||NN
20970 
20971 
20972      Stream:   as (severity0)
20973 
20974      Time:     While system is running.
20975 
20976      Meaning:  At attempt was made to  logout a process which was
20977                not logged in.  This is most likely the cause of a
20978                login error in the answering service.
20979 
20980      Action:   Contact the system programming staff._sa
20981 
20982 
20983                [lg_ctl_.pl1]
20984                lg_ctl_:  lowered max ring for PERSON.PROJECT from
20985                N (in PDTE) to M (in SATE)
20986 
20987 
20988      Stream:   as (severity0)
20989 
20990      Time:     While system is running.
20991 
20992      Meaning:  The value  for the max  ring specified in  the PDT
20993                entry for PERSON on project PROJECT was lower than
20994                the  maximum  allowed  ring  in  the  SAT  for the
20995                project.  The  SAT value was used  for this login.
20996                The  project administrator  should change  the PDT
20997                value  to conform  to  the  limits imposed  by the
20998                system administrator.
20999 
21000 
21001 
21002                [lg_ctl_.pl1]
21003                lg_ctl_:  breach of physical security by NAME.PROJ
21004                from CHANNEL (TYPE terminal "ID").
21005                lg_ctl_:    person   authorization   is   AUTH_NUM
21006                (AUTH_STRING)
21007 
21008 
21009 
21010 lg_ctl_                        363            08/03/23     MR12.7^L
21011 
21012 
21013                lg_ctl_:    terminal  access  class   is  AUTH_NUM
21014                (AUTH_STRING)
21015 
21016 
21017 
21018      Stream:   as (severity2)
21019 
21020      Time:     While system is running.
21021 
21022      Meaning:  The user  identified in the first  message by NAME
21023                on the project PROJ has somehow gotten access to a
21024                terminal with an access  class higher than his own
21025                authorization.    The  next   two  messages   give
21026                additional  information,  where   AUTH_NUM  is  an
21027                encoding of  the authorization or access  class in
21028                numeric form and AUTH_STRING is the mnemonic form.
21029                The login is refused and the terminal is hung up.
21030 
21031      Action:   Notify the system security administrator.
21032 
21033 
21034                [lg_ctl_.pl1]
21035                lg_ctl_:   disconnected count  for USER  is N1  in
21036                cdte, N2 in pdte, n_processes=N3.
21037 
21038 
21039      Stream:   as (severity1)
21040 
21041      Time:     While system is running.
21042 
21043      Meaning:  The PDT entry for the user indicates that the user
21044                has a  different number of  disconnected processes
21045                than could actually be  found in the answer_table.
21046                The   PDT  count  is   forced  to  the   count  of
21047                disconnected processes found  in the answer_table.
21048                If  this  message  occurs  repeatedly  for a given
21049                user, notify the system administrator.
21050 
21051      Action:   No operator action is required.
21052 
21053 
21054                [lg_ctl_.pl1]
21055                lg_ctl_:  ERROR_MESSAGE.  Error updating PNT entry
21056                of USER.
21057 
21058 
21059      Stream:   as (severity2)
21060 
21061      Time:     While system is running.
21062 
21063      Meaning:  The system  was unable to  update the PNT  for the
21064                user.  Login for the user was refused.
21065 
21066 
21067 
21068 lg_ctl_                        364            08/03/23     MR12.7^L
21069 
21070 
21071      Action:   Contact the system programming staff._sa
21072 
21073 
21074                [lg_ctl_.pl1]
21075                lg_ctl_:  ERROR_MESSAGE.  >sc1>pdt>PROJ.pdt
21076 
21077 
21078      Stream:   as (severity2)
21079 
21080      Time:     While system is running.
21081 
21082      Meaning:  All  users on  project PROJ  are unable  to log in
21083                because the  project's pdt cannot be  accessed for
21084                the reason ERROR_MESSAGE.
21085 
21086      Action:   Contact  the system  programming staff._sa  If the
21087                file was lost  due to a crash, it  may be possible
21088                to retrieve it.  If  the file cannot be retrieved,
21089                the person in charge of  the project or the system
21090                administrator has to regenerate the file.
21091 
21092 
21093 
21094                [lg_ctl_.pl1]
21095                lg_ctl_:   ERROR_MESSAGE.    Changing  Mail  Table
21096                default project for USER to PROJ
21097 
21098 
21099      Stream:   as (severity2)
21100 
21101      Time:     While system is running.
21102 
21103      Meaning:  USER.PROJ       logged      in       with      the
21104                -change_default_project  control argument,  but it
21105                was  not possible to  change his Mail  Table entry
21106                for  the reason   noted in  ERROR_MESSAGE.  USER's
21107                default project was changed,  though, but the Mail
21108                Table and the PNT are now inconsistent.
21109 
21110      Action:   Contact the system programming staff._sa
21111 
21112 
21113                [lg_ctl_.pl1]
21114                lg_ctl_:  ERROR_MESSAGE.  Checksum failure reading
21115                PNT entry of USER.
21116 
21117 
21118      Stream:   as (severity2)
21119 
21120      Time:     While system is running.
21121 
21122      Meaning:  The PNT entry for USER is damaged.  It may have to
21123                be  recreated, or  the entire  PNT may  have to be
21124 
21125 
21126 lg_ctl_                        365            08/03/23     MR12.7^L
21127 
21128 
21129                retrieved in special session.  This can occur as a
21130                result of a  damaged PNT, or due to  a logic error
21131                in the answering service.
21132 
21133      Action:   Contact the system programming staff._sa
21134 
21135 
21136                [lg_ctl_.pl1]
21137                lg_ctl_:  ERROR_MESSAGE.  Error  reading PNT entry
21138                of USER.
21139 
21140 
21141      Stream:   as (severity2)
21142 
21143      Time:     While system is running.
21144 
21145      Meaning:  This  indicates  that  the  system  was  unable to
21146                access the PNT.  Login for the user was refused.
21147 
21148      Action:   Contact the  system programming staff._sa  Some or
21149                all users will be unable to log in.
21150 
21151 
21152 
21153                [lg_ctl_.pl1]
21154                lg_ctl_:   ERROR_MESSAGE.  Unable to  check access
21155                for channel CHANNEL.
21156 
21157 
21158      Stream:   as (severity 1)
21159 
21160      Time:     While system is running.
21161 
21162      Meaning:  The  channel CHANNEL  has the  check_acs attribute
21163                set.  However, it was  not possible to examine the
21164                Access  Control Segment  for the  reason noted  in
21165                ERROR_MESSAGE.  Login  for the user  attempting to
21166                use this channel was refused.
21167 
21168      Action:   Contact the system programming staff._sa
21169 
21170 
21171                [lg_ctl_.pl1]
21172                lg_ctl_:  ERROR_MESSAGE.  unable to rehash sat.ht:
21173                REASON
21174 
21175 
21176      Stream:   as (severity2)
21177 
21178      Time:     While system is running.
21179 
21180      Meaning:  An attempt to recreate  the SAT hash table failed.
21181                The  user attempting to  log in was  denied login.
21182 
21183 
21184 lg_ctl_                        366            08/03/23     MR12.7^L
21185 
21186 
21187                In all  probably no users  will be able  to log in
21188                until the situation is repaired.
21189 
21190      Action:   Contact the system programming staff._sa
21191 
21192 
21193                [lg_ctl_.pl1]
21194                lg_ctl_:  hash table of PROJ.pdt has PERS, pdt has
21195                PERS2, at MM|NN
21196 
21197 
21198      Stream:   as (severity2)
21199 
21200      Time:     While system is running.
21201 
21202      Meaning:  The  PDT for  PROJ is  out of  step with  its hash
21203                table.   The system attempts  to log the  user in.
21204                The PDT  must be re-installed in  order to correct
21205                the problem.
21206 
21207      Action:   Contact the system programming staff._sa
21208 
21209 
21210                [lg_ctl_.pl1]
21211                lg_ctl_:  login word is "QQQQ"
21212 
21213 
21214      Stream:   as (severity1)
21215 
21216      Time:     System Intialization.
21217 
21218      Meaning:  If multics  is typed, a random  4-digit login word
21219                is made up.
21220 
21221      Action:   If any system programmers are to be allowed access
21222                to the system during  this special session, inform
21223                them of  the login word.   To allow normal  use of
21224                Multics, type "word login".  In order to start the
21225                absentee facility, which special sessions disable,
21226                type "abs start".
21227 
21228 
21229 
21230                [lg_ctl_.pl1]
21231                lg_ctl_:  no hash table at WWWWWW of PROJ.pdt
21232 
21233 
21234      Stream:   as (severity2)
21235 
21236      Time:     While system is running.
21237 
21238      Meaning:  A  user  is  logging  in  to  project  PROJ.   The
21239                project's  pdt does  not have  a hash  table, even
21240 
21241 
21242 lg_ctl_                        367            08/03/23     MR12.7^L
21243 
21244 
21245                though  the pdt header  says it does.   The system
21246                attempts to log the  user in anyway.  Possibly the
21247                PDT has been damaged.
21248 
21249      Action:   Contact the system programming staff.
21250 
21251 
21252                [lg_ctl_.pl1]
21253                lg_ctl_:    password    used   PERS.PROJ   CHANNEL
21254                TERM_TYPE ID
21255 
21256 
21257      Stream:   as (severity2)
21258 
21259      Time:     While system is running.
21260 
21261      Meaning:  The system  administrator has set a  password trap
21262                on the password for the person PERS.  This message
21263                is  typed when  the person  tries to  log in.  The
21264                login was attempted from a TERM_TYPE terminal with
21265                identification code ID, using channel CHANNEL.
21266 
21267      Action:   Unless the  system administrator has asked  you to
21268                watch  for this  message, ignore  it.  The  system
21269                administrator can  locate this message in  the log
21270                and is presumably watching for it.
21271 
21272 
21273 
21274                [lg_ctl_.pl1]
21275                lg_ctl_:  PDT for project PROJECTID has its damage
21276                switch set.  Login for user PERSONID refused.
21277 
21278 
21279 
21280      Stream:   as (severity 2)
21281 
21282      Time:     Contact the system programming staff.
21283 
21284      Meaning:  During a login attempt of user PERSONID on project
21285                PROJECTID,  the system  noticed the  damage switch
21286                set on  the PDT for  this project.  The  login was
21287                denied.   A system administrator  should determine
21288                whether  the  PDT  is  in  fact  damaged.  If not,
21289                he/she should  turn off the damage  switch for the
21290                PDT        (i.e.          switch_off        damage
21291                >sc1>pdt>PROJECTID.pdt)   If   the   PDT   appears
21292                damaged, then  it should be retrieved  from backup
21293                tape or re-installed when the system is in special
21294                session.
21295 
21296 
21297 
21298 
21299 
21300 lg_ctl_                        368            08/03/23     MR12.7^L
21301 
21302 
21303                [lg_ctl_.pl1]
21304                lg_ctl_:  PDT for project PROJECTID has its damage
21305                switch set.  Login for user PERSONID refused.
21306 
21307 
21308 
21309      Stream:   as (severity2)
21310 
21311      Time:     Contact the system programming staff.
21312 
21313      Meaning:  During a login attempt of user PERSONID on project
21314                PROJECTID,  the system  noticed the  damage switch
21315                set on  the PDT for  this project.  The  login was
21316                denied.   A system administrator  should determine
21317                whether  the  PDT  is  in  fact  damaged.  If not,
21318                he/she should  turn off the damage  switch for the
21319                PDT        (i.e.          switch_off        damage
21320                >sc1>pdt>PROJECTID.pdt)   If   the   PDT   appears
21321                damaged, then  it should be retrieved  from backup
21322                tape or re-installed when the system is in special
21323                session.
21324 
21325 
21326 
21327                [lg_ctl_.pl1]
21328                lg_ctl_:  project PROJ, state N, still in sat.ht
21329 
21330 
21331      Stream:   as (severity2)
21332 
21333      Time:     While system is running.
21334 
21335      Meaning:  A user  on a deleted project attempted  to log in,
21336                and  the supposedly  deleted project  was still in
21337                the  SAT hash table.   The user is  refused login.
21338                The SAT and  its hash table are out  of step.  The
21339                system continues operating.
21340 
21341      Action:   Contact the system programming staff.
21342 
21343 
21344                [lg_ctl_.pl1]
21345                lg_ctl_:     project     PROJECT    has    invalid
21346                rate_structure number N.  Using rate_structure 0.
21347 
21348 
21349      Stream:   as (severity2)
21350 
21351      Time:     While system is running.
21352 
21353      Meaning:  The  SAT  entry  for  the  project  has an invalid
21354                rate_structure number.  The user is allowed to log
21355                in,  but  is  charged  at  the  default rate (i.e.
21356 
21357 
21358 lg_ctl_                        369            08/03/23     MR12.7^L
21359 
21360 
21361                according to  rate_structure 0) Notify  the system
21362                administrator  so  that  the   SAT  entry  may  be
21363                corrected.  This message will occur for each login
21364                using project PROJECT.
21365 
21366      Action:   Contact the system programming staff._sa
21367 
21368 
21369                [lg_ctl_.pl1]
21370                lg_ctl_:   project.n_users =   N for  PROJ (logout
21371                PERSON)
21372 
21373 
21374      Stream:   as (severity0)
21375 
21376      Time:     While system is running.
21377 
21378      Meaning:  The count  of the active  users on a  project went
21379                negative when  attempting to logout  PERSON.  This
21380                is most likely the result  of a logic error in the
21381                answering service or a damaged PDT.
21382 
21383      Action:   Contact the system programming staff._sa
21384 
21385 
21386                [lg_ctl_.pl1]
21387                lg_ctl_:  project.n_users  = N for  PROJECT (login
21388                PERSON)
21389 
21390 
21391      Stream:   as (severity0)
21392 
21393      Time:     While system is running.
21394 
21395      Meaning:  The value  of project.n_users for  project PROJECT
21396                went  negative while  attempting to  login PERSON.
21397                The  user was  permitted  login  but there  may be
21398                discrepancies which may affect future operations.
21399 
21400      Action:   Contact the system programming staff._sa
21401 
21402 
21403                [lg_ctl_.pl1]
21404                lg_ctl_:   raised initial ring  for PERSON.PROJECT
21405                from N (in PDTE) to M (in SATE)
21406 
21407 
21408      Stream:   as (severity0)
21409 
21410      Time:     While system is running.
21411 
21412      Meaning:  The  value for the  initial ring specified  in the
21413                PDT entry for PERSON  on project PROJECT was lower
21414 
21415 
21416 lg_ctl_                        370            08/03/23     MR12.7^L
21417 
21418 
21419                than than allowed for the project in the SAT.  The
21420                value in the SAT was used in logging in this user.
21421                The project  adminstrator should change  the value
21422                in the PDT to conform to the limits imposed by the
21423                system adminstrator.
21424 
21425      Action:   No operator action is required.
21426 
21427 
21428                [lg_ctl_.pl1]
21429                lg_ctl_:   reduced pdir  quota for  PERSON.PROJECT
21430                from N (in PDTE) to M (in SATE)
21431 
21432 
21433      Stream:   as (severity0)
21434 
21435      Time:     While system is running.
21436 
21437      Meaning:  The value for process directory quota specified in
21438                the  PDT entry for  PERSON on project  PROJECT was
21439                greater than the maximum allowed process directory
21440                quota specified in the SAT entry for PROJECT.  The
21441                SAT  value was used  for this login.   The project
21442                administrator for the project should set the value
21443                within   the   limits   imposed   by   the  system
21444                administrator.
21445 
21446      Action:   No operator action is required.
21447 
21448 
21449                [lg_ctl_.pl1]
21450                lg_ctl_:   sat.ht has  "WWWW", SAT  has "xxxx"  at
21451                MM|NN.
21452 
21453 
21454      Stream:   as (severity2)
21455 
21456      Time:     While system is running.
21457 
21458      Meaning:  The SAT  and its hash table  are out of step  or a
21459                storage system error has  occurred.  This could be
21460                the  result of  an incomplete  reload.  The system
21461                attempts to rehash the table and continue.
21462 
21463      Action:   Contact the system programming staff._sa
21464 
21465 
21466                [lg_ctl_.pl1]
21467                lg_ctl_:   too many   bad passwords  for NAME.PROJ
21468                from CHANNEL (TYPE terminal "ID").
21469 
21470 
21471      Stream:   as (severity2)
21472 
21473 
21474 lg_ctl_                        371            08/03/23     MR12.7^L
21475 
21476 
21477      Time:     While system is running.
21478 
21479      Meaning:  The  user identified by  NAME on the  project PROJ
21480                has either forgotten his  password or someone else
21481                is trying to guess it.  The system has refused the
21482                login  for  an  installation-specified  number  of
21483                times before this message is printed.  The maximum
21484                number   of  times   the  password   can  be  used
21485                incorrectly  before  this  message  is  printed is
21486                stored in the segment installation_parms.
21487 
21488      Action:   Contact the system programming staff._sa
21489 
21490 
21491                [lg_ctl_.pl1]
21492                lg_ctl_:  tracing turned off.
21493 
21494 
21495      Stream:   as (severity1)
21496 
21497      Time:     While system is running.
21498 
21499      Meaning:  A system adminstrator has  disabled tracing of the
21500                module lg_ctl_.
21501 
21502      Action:   No operator action is required.
21503 
21504 
21505                [lg_ctl_.pl1]
21506                lg_ctl_:  tracing turned on.
21507 
21508 
21509      Stream:   as (severity1)
21510 
21511      Time:     While system is running.
21512 
21513      Meaning:  A system administrator has  enabled tracing of the
21514                module lg_ctl_.  Debugging information will appear
21515                on the console.
21516 
21517      Action:   No operator action is required.
21518 
21519 
21520                [lg_ctl_.pl1]
21521                lg_ctl_:   TYPE  access   to  channel  CHANNEL  by
21522                NAME.PROJ denied by ACS.
21523 
21524 
21525      Stream:   as (severity 0)
21526 
21527      Time:     While system is running.
21528 
21529 
21530 
21531 
21532 lg_ctl_                        372            08/03/23     MR12.7^L
21533 
21534 
21535      Meaning:  The  user  NAME.PROJ  attempted  to  use  the TYPE
21536                command   while  dialed-up  on   channel  CHANNEL.
21537                However, the  access to the channel  is restricted
21538                by  Access Control  Segment, and  the user  is not
21539                permitted to use the channel.
21540 
21541      Action:   No operator action is required.
21542 
21543 
21544                [lg_ctl_.pl1]
21545                lg_ctl_:   user  PERSON,  state  N,  still in hash
21546                table of PROJ.pdt
21547 
21548 
21549      Stream:   as (severity2)
21550 
21551      Time:     While system is running.
21552 
21553      Meaning:  A  deleted user  attempted  to  log in  to project
21554                PROJ, and his name was  still in the hash table of
21555                the  project's PDT.   The user  is refused  login.
21556                The  PDT has probably  been damaged by  a software
21557                malfunction.
21558 
21559      Action:   Contact the system programming staff.
21560 
21561 
21562                [load_ctl_.pl1]
21563                load_ctl_:   bumping  NAME1.PROJ  for  NAME2.PROJ:
21564                REASON
21565 
21566 
21567      Stream:   as (severity1)
21568 
21569      Time:     While system is running.
21570 
21571      Meaning:  This message  is typed out when a  user is bumped.
21572                A user may be bumped by another member of his load
21573                control  group, in  which case  REASON is  pr_grp,
21574                which means group preemption.  If a secondary user
21575                is bumped by a primary  user, either from the same
21576                group  or from  another group,  REASON is  pr_sec,
21577                meaning secondary  user preemption.  If  REASON is
21578                pr_emrg,  meaning emergency  preemption, a  system
21579                programmer  was logging  in and  had to  bump some
21580                user.  A user is usually given three minutes after
21581                this message to clean up  and log out before being
21582                automatically logged out.
21583 
21584      Action:   No operator action is required.
21585 
21586 
21587                [load_ctl_.pl1]
21588 
21589 
21590 load_ctl_                      373            08/03/23     MR12.7^L
21591 
21592 
21593                load_ctl_:  configuration not in tables.  X cpu, Y
21594                mem, W  bulk, shift Z using  configuartion XX cpu,
21595                YY mem, WW bulk, shift ZZ
21596 
21597 
21598 
21599      Stream:   as (severity2)
21600 
21601      Time:     May occur at any time.
21602 
21603      Meaning:  The  automatic  setting  of  maxunits  by the load
21604                control   facility   was    attempted,   but   the
21605                configuration tables did  not have a configuration
21606                defined  that matched  the current  configuration.
21607                No change was made  to the system parameters.  The
21608                system  continues  operation,  selecting  the last
21609                entry   in  the    config  tables   (which  should
21610                correspond to the largest  system described by the
21611                system  administrator.)   The  values  assumed  by
21612                automatic  load control  are given  in the  second
21613                line of the message.
21614 
21615      Action:   Set  maxunits  and   the  absentee  max  manually.
21616                Inform  the system  administrator so  that he  can
21617                update the load control tables.
21618 
21619 
21620 
21621                [load_ctl_.pl1]
21622                load_ctl_:  demote NAME.PROJ GROUP NNN
21623 
21624 
21625      Stream:   as (severity1)
21626 
21627      Time:     While system is running.
21628 
21629      Meaning:  This is trace output.   This user has been demoted
21630                to secondary status.
21631 
21632      Action:   No operator action is  required.  To turn off this
21633                output, type load_ctl_$lctraceoff from admin mode.
21634 
21635 
21636 
21637                [load_ctl_.pl1]
21638                load_ctl_:  Entry not found.  master_group_table
21639 
21640 
21641      Stream:   as (severity2)
21642 
21643      Time:     System Intialization.
21644 
21645 
21646 
21647 
21648 load_ctl_                      374            08/03/23     MR12.7^L
21649 
21650 
21651      Meaning:  load_ctl_ cannot find the master_group_table.  The
21652                system  will probably not  be able to  perform the
21653                bootload operation.
21654 
21655      Action:   Contact the system programming staff.
21656 
21657 
21658                [load_ctl_.pl1]
21659                load_ctl_:    ERROR_MESSAGE   During   work  class
21660                redefinition
21661 
21662 
21663      Stream:   as (severity2)
21664 
21665      Time:     While  the  system  is  running  or  during system
21666                startup.
21667 
21668      Meaning:  Either  some system  table has  been damaged  or a
21669                system  administrator  was   changing  work  class
21670                definitions at the time of a shift change, or when
21671                a "maxu auto" command  was issued.  Error messages
21672                immediately   preceding  this  one   contain  more
21673                information about the exact nature of the problem.
21674 
21675      Action:   Contact  the system  programming staff._sa  He may
21676                want you to type the  "maxu auto" command to retry
21677                the  operation  that   failed.   If  that  command
21678                produces no  error messages, the problem  has been
21679                eliminated.
21680 
21681 
21682 
21683                [load_ctl_.pl1]
21684                load_ctl_:  group GRPID missing at logout
21685 
21686 
21687      Stream:   as (severity2)
21688 
21689      Time:     While system is running.
21690 
21691      Meaning:  The   master_group_table  entry   for  GRPID   has
21692                vanished.   The system  is attempting  to logout a
21693                user  from that  group but  cannot find  the table
21694                entry for  the group.  The system  will attempt to
21695                continue.
21696 
21697      Action:   Contact the system programming staff._sa
21698 
21699 
21700                [load_ctl_.pl1]
21701                load_ctl_:  group GRPID missing at preempt
21702 
21703 
21704 
21705 
21706 load_ctl_                      375            08/03/23     MR12.7^L
21707 
21708 
21709      Stream:   as (severity2)
21710 
21711      Time:     While system is running.
21712 
21713      Meaning:  The   master_group_table  entry   for  GRPID   has
21714                vanished.  The  system is attempting to  preempt a
21715                user  from that  group but  cannot find  the table
21716                entry for  the group.  The system  will attempt to
21717                continue.
21718 
21719      Action:   Contact the system programming staff._sa
21720 
21721 
21722                [load_ctl_.pl1]
21723                load_ctl_:  Group GRPID missing for NAME.PROJ
21724 
21725 
21726      Stream:   as (severity2)
21727 
21728      Time:     While system is running.
21729 
21730      Meaning:  The system  administrator has designated  that the
21731                project PROJ  should be in the  load control group
21732                GRPID but the entry  in the master_group_table for
21733                that  load  control  group  is  missing.  The user
21734                cannot log in.  This may be an indication that the
21735                segment master_group_table has been damaged.
21736 
21737      Action:   Contact the system programming staff._sa
21738 
21739 
21740                [load_ctl_.pl1]
21741                load_ctl_:  group GRPID not authorized for project
21742                PROJ
21743 
21744 
21745      Stream:   as (severity2)
21746 
21747      Time:     While system is running.
21748 
21749      Meaning:  A project administrator has designated that one of
21750                the users  in project PROJ  should be in  the load
21751                control group GRPID,  but the system administrator
21752                has  not authorized  that  project  to be  in that
21753                group.  An  attempt will be  made to log  the user
21754                in,  using  the  default  group  for  his project.
21755                Subsequent messages  will indicate the  success or
21756                failure of this attempt.
21757 
21758      Action:   Contact the system programming staff._sa
21759 
21760 
21761                [load_ctl_.pl1]
21762 
21763 
21764 load_ctl_                      376            08/03/23     MR12.7^L
21765 
21766 
21767                load_ctl_:   group  GRPID  not  found  in  mgt for
21768                NAME.PROJ
21769 
21770 
21771      Stream:   as (severity2)
21772 
21773      Time:     While system is running.
21774 
21775      Meaning:  A system  or project administrator  has designated
21776                that  the user  NAME.PROJ  should  be in  the load
21777                control  group GRPID,  but the  master_group_table
21778                (mgt)  has no  entry for  that group.   An attempt
21779                will be made to log the user in, using the default
21780                group for  his project.  Subsequent  messages will
21781                indicate the success or failure of this attempt.
21782 
21783      Action:   Contact the system programming staff._sa
21784 
21785 
21786                [load_ctl_.pl1]
21787                load_ctl_:   maxu  too  small  (XX),  YY units for
21788                group GRPID
21789 
21790 
21791      Stream:   as (severity2)
21792 
21793      Time:     While system is running.
21794 
21795      Meaning:  The  system administrator  has specified  that the
21796                load control group GRPID is to have "all the rest"
21797                of the  primary load units after  all other groups
21798                have   taken  their  allocations   from  maxunits.
21799                However,  maxunits is  less  than  the sum  of the
21800                primary  allocations, giving  the group  GRPID the
21801                negative  allocation  of  YY  units.   The  system
21802                proceeds,  attempting to  log the  user in anyway.
21803                Of  course, the  user is  allowed secondary status
21804                only if he  is allowed to log in at  all.  This is
21805                often  the result of  the operator typing  maxu 30
21806                instead of maxu 300, or some similar error.
21807 
21808      Action:   Check the value of maxunits  and, if a mistake was
21809                made,  correct  it.   If  the  maxunits  value  is
21810                correct,  note  this   situation  for  the  system
21811                administrator.
21812 
21813 
21814 
21815                [load_ctl_.pl1]
21816                load_ctl_:  more than one group has -1 max:  GRPID
21817 
21818 
21819      Stream:   as (severity2)
21820 
21821 
21822 load_ctl_                      377            08/03/23     MR12.7^L
21823 
21824 
21825      Time:     System Intialization.
21826 
21827      Meaning:  The  system administrator  has accidentally  given
21828                more than one group a  "take all the rest" maximum
21829                primary unit allocation.  The user control package
21830                cannot  handle this  situation.  The  second group
21831                with a -1 maxprim is listed.  The system completes
21832                startup and users can log  in but maxunits may not
21833                be obeyed.
21834 
21835      Action:   Contact the system programming staff._sa
21836 
21837 
21838                [load_ctl_.pl1]
21839                load_ctl_:  promote NAME.PROJ GROUP NNN
21840 
21841 
21842      Stream:   as (severity1)
21843 
21844      Time:     While system is running.
21845 
21846      Meaning:  This is trace output.  This user has been promoted
21847                to primary status.
21848 
21849      Action:   No operator action is  required.  To turn off this
21850                output, type load_ctl_$lctraceoff from admin mode.
21851 
21852 
21853 
21854                [load_ctl_.pl1]
21855                load_ctl_:  reduced grace  for PERSON.PROJECT from
21856                MINUTES1 (in PDTE) to MINUTES2 (in SATE)
21857 
21858 
21859      Stream:   as (severity 0)
21860 
21861      Time:     While system is running.
21862 
21863      Meaning:  The  Project  Definition  Table  (PDT)  entry  for
21864                PERSON.PROJECT specifies a larger grace time (time
21865                during   which  a    process  is   protected  from
21866                preemption)  than does the  System Administrator's
21867                Table (SAT) entry for the project.  The time given
21868                in the SAT entry is used.
21869 
21870      Action:   No operator action is required.
21871 
21872 
21873                [load_ctl_.pl1]
21874                load_ctl_:   Too many  primes.  NAME.PROJ  (GROUP)
21875                MM/NN
21876 
21877 
21878 
21879 
21880 load_ctl_                      378            08/03/23     MR12.7^L
21881 
21882 
21883      Stream:   as (severity0)
21884 
21885      Time:     While system is running.
21886 
21887      Meaning:  This  is  trace  output.    The  system  has  been
21888                committed to allow a  certain number of users from
21889                group GROUP to be logged in at one time.  In order
21890                to  log this  user in,   some other  user must  be
21891                bumped,  but  all  users  have  primary status and
21892                cannot  be  bumped.   This   situation  may  be  a
21893                consequence   of  system   programmers  with   the
21894                overloading privilege  logging in when  the system
21895                is full.  The user is allowed to log in anyway.
21896 
21897      Action:   No operator action is required.
21898 
21899 
21900                [load_ctl_.pl1]
21901                load_ctl_:  Unknown mgt version number:  NUMBER
21902 
21903 
21904      Stream:   as (severity2)
21905 
21906      Time:     System Intialization.
21907 
21908      Meaning:  Either  the  master_group_table   (mgt)  has  been
21909                damaged,  or its  format is  incompatible with the
21910                current Answering  Service.  The system  cannot be
21911                brought up until a correct mgt is provided.
21912 
21913      Action:   Contact the system programming staff._sa
21914 
21915 
21916                [load_disk_mpcs.pl1]
21917                load_disk_mpcs:  Disk mpc(s):  NAMES appear not to
21918                be operating.
21919 
21920 
21921 
21922      Stream:   $announce
21923 
21924      Time:     System Intialization.
21925 
21926      Meaning:  The  named disk mpcs,  listed in the  config deck,
21927                did  not  respond  to  a  "request status" control
21928                order.  They are believed  not to be operating; in
21929                particular,  firmware  should  probably  be loaded
21930                into them.
21931 
21932 
21933 
21934                [load_disk_mpcs.pl1]
21935 
21936 
21937 
21938 load_disk_mpcs                 379            08/03/23     MR12.7^L
21939 
21940 
21941                load_disk_mpcs:    Operator   aborted   disk   MPC
21942                loading.
21943 
21944 
21945      Stream:   BOS Typewriter (Crashes system)
21946 
21947      Time:     System Intialization.
21948 
21949      Meaning:  The  operator answered  "abort" when  requested to
21950                supply disk mpcs to be  loaded.  This will cause a
21951                return to the previous bce command level.
21952 
21953 
21954 
21955                [load_fnp_.pl1]
21956                load_fnp_:  Core image for  FNP X will not support
21957                HSLA #N; <core image pathname>
21958 
21959 
21960      Stream:   BOS Typewriter.
21961 
21962      Time:     While system is running.
21963 
21964      Meaning:  The CDT  specifies that a channel  should be used,
21965                but the MCS core image  for FNP X does not contain
21966                support  for the  indicated HSLA.   Either the MCS
21967                core image  or the CDT must be  modified.  The FNP
21968                cannot be loaded.
21969 
21970      Action:   Contact the system programming staff._sa
21971 
21972 
21973                [load_fnp_.pl1]
21974                load_fnp_:  Core image for  FNP X will not support
21975                LSLA #N; <core image pathname>
21976 
21977 
21978      Stream:   BOS Typewriter.
21979 
21980      Time:     While system is running.
21981 
21982      Meaning:  The CDT  specifies that a channel  should be used,
21983                but the MCS core image  for FNP X does not contain
21984                support  for the  indicated LSLA.   Either the MCS
21985                core image  or the CDT must be  modified.  The FNP
21986                cannot be loaded.
21987 
21988      Action:   Contact the system programming staff._sa
21989 
21990 
21991                [load_fnp_.pl1]
21992                load_fnp_:  ERROR_MESSAGE.   Creating boot segment
21993                in process directory for FNP X.
21994 
21995 
21996 load_fnp_                      380            08/03/23     MR12.7^L
21997 
21998 
21999      Stream:   BOS Typewriter.
22000 
22001      Time:     While system is running.
22002 
22003      Meaning:  Ths  system  was  unable  to  create  a  temporary
22004                segment in the  initializer's process directory to
22005                hold core image for FNP X.  This indicates a logic
22006                error in the supervisor, or CPU or memory hardware
22007                problems.  The FNP cannot be loaded.
22008 
22009      Action:   Contact the system programming staff.
22010 
22011 
22012                [load_fnp_.pl1]
22013                load_fnp_:  ERROR_MESSAGE.  During  FNP X bootload
22014                attempt.
22015 
22016 
22017      Stream:   BOS Typewriter.
22018 
22019      Time:     While system is running.
22020 
22021      Meaning:  An error occurred while sending the new core image
22022                to FNP X.  The FNP cannot be loaded.
22023 
22024      Action:   Contact the system programming staff.
22025 
22026 
22027                [load_fnp_.pl1]
22028                load_fnp_:   ERROR_MESSAGE.   expand_pathname_  on
22029                IMAGE_PATH for FNP X.
22030 
22031 
22032      Stream:   BOS Typewriter.
22033 
22034      Time:     While system is running.
22035 
22036      Meaning:  The CDT entry  for FNP X specifies a  bad path for
22037                its core image.  The FNP cannot be loaded.
22038 
22039      Action:   Contact the system programming staff._sa
22040 
22041 
22042                [load_fnp_.pl1]
22043                load_fnp_:   ERROR_MESSAGE.  Getting FNP  info for
22044                FNP X.
22045 
22046 
22047      Stream:   BOS Typewriter.
22048 
22049      Time:     While system is running.
22050 
22051 
22052 
22053 
22054 load_fnp_                      381            08/03/23     MR12.7^L
22055 
22056 
22057      Meaning:  The system could not  obtain information about FNP
22058                X  from the hardcore.   The CDT may  disagree with
22059                the CONFIG deck.  The FNP cannot be loaded.
22060 
22061      Action:   Contact the system programming staff._sa
22062 
22063 
22064                [load_fnp_.pl1]
22065                load_fnp_:   ERROR_MESSAGE.   Locating  IMAGE_PATH
22066                for FNP X.
22067 
22068 
22069      Stream:   BOS Typewriter.
22070 
22071      Time:     While system is running.
22072 
22073      Meaning:  The system cannot locate the core image for FNP X.
22074                The CDT entry for the FNP may be incorrect, or the
22075                copy of  the MCS may  have been deleted.   The FNP
22076                cannot be loaded.
22077 
22078      Action:   Contact the system programming staff._sa
22079 
22080 
22081                [load_fnp_.pl1]
22082                load_fnp_:  ERROR_MESSAGE.  Wiring  memory for FNP
22083                X bootload.
22084 
22085 
22086      Stream:   BOS Typewriter.
22087 
22088      Time:     While system is running.
22089 
22090      Meaning:  The system cannot wire  down the process directory
22091                segment which  will be used  to boot FNP  X.  This
22092                indicates a logic error  in the supervisor, or CPU
22093                or  memory hardware  problems.  The  FNP cannot be
22094                loaded.
22095 
22096      Action:   Contact the system programming staff.
22097 
22098 
22099                [load_fnp_.pl1]
22100                load_fnp_:  Invalid  core image for FNP  X (.crldt
22101                exceeds current time), <core image pathname>
22102 
22103 
22104      Stream:   BOS Typewriter.
22105 
22106      Time:     While system is running.
22107 
22108      Meaning:  The creation date of the  MCS core image for FNP X
22109                is past  the current time.  The MCS  core image is
22110 
22111 
22112 load_fnp_                      382            08/03/23     MR12.7^L
22113 
22114 
22115                probably  damaged and  will have  to be recreated.
22116                The FNP cannot be loaded.
22117 
22118      Action:   Contact the system programming staff.
22119 
22120 
22121                [load_fnp_.pl1]
22122                load_fnp_:   Invalid  core  image  for  FNP X (bad
22123                .crmem value of N in image), <core image pathname>
22124 
22125 
22126      Stream:   BOS Typewriter.
22127 
22128      Time:     While system is running.
22129 
22130      Meaning:  The  value of  .crmem  should  be 24575,  32767 or
22131                65535  in a  valid fnp  core image.   The MCS core
22132                image for FNP X will have to be modified.  The FNP
22133                cannot be loaded.
22134 
22135      Action:   Contact the system programming staff.
22136 
22137 
22138                [load_fnp_.pl1]
22139                load_fnp_:   Invalid  core  image  for  FNP X (bad
22140                module chain), <core image pathname>
22141 
22142 
22143      Stream:   BOS Typewriter.
22144 
22145      Time:     While system is running.
22146 
22147      Meaning:  An inconsistency was found  in tracing through the
22148                module chain of the MCS core image for FNP X.  The
22149                MCS core  image is probably damaged  and will have
22150                to be recreated.  The FNP cannot be loaded.
22151 
22152      Action:   Contact the system programming staff.
22153 
22154 
22155                [load_fnp_.pl1]
22156                load_fnp_:  Invalid core image  for FNP X (binding
22157                of image  was done over N years  ago), <core image
22158                pathname>
22159 
22160 
22161      Stream:   BOS Typewriter.
22162 
22163      Time:     While system is running.
22164 
22165      Meaning:  The creation date of the  MCS core image for FNP X
22166                indicates the image is over  N years old.  The MCS
22167 
22168 
22169 
22170 load_fnp_                      383            08/03/23     MR12.7^L
22171 
22172 
22173                core image is probably damaged and will have to be
22174                recreated.  The FNP cannot be loaded.
22175 
22176      Action:   Contact the system programming staff.
22177 
22178 
22179                [load_fnp_.pl1]
22180                load_fnp_:   Invalid core  image for  FNP X (found
22181                only  N  modules,  minimum  required  is M), <core
22182                image pathname>
22183 
22184 
22185      Stream:   BOS Typewriter.
22186 
22187      Time:     While system is running.
22188 
22189      Meaning:  Only N program modules were  found in the MCS core
22190                image  for FNP X  out of a  minimum of M  modules.
22191                The  minimum number  of  modules  is based  on the
22192                number  required  to   support  the  smallest  FNP
22193                configuration.   The MCS   core image  is probably
22194                damaged  and will have  to be recreated.   The FNP
22195                cannot be loaded.
22196 
22197      Action:   Contact the system programming staff.
22198 
22199 
22200                [load_fnp_.pl1]
22201                load_fnp_:   Invalid core  image for  FNP X (image
22202                length error), <core image pathname>
22203 
22204 
22205      Stream:   BOS Typewriter.
22206 
22207      Time:     While system is running.
22208 
22209      Meaning:  The bit  count of the  image was adjusted  and did
22210                not  compare with  the image  length found  in the
22211                core image  for FNP X.   The first 36  bits of the
22212                image  segment contains  the image  length set  by
22213                bind_fnp_load_.   The MCS  core image  is probably
22214                damaged  and will have  to be recreated.   The FNP
22215                cannot be loaded.
22216 
22217      Action:   Contact the system programming staff.
22218 
22219 
22220                [load_fnp_.pl1]
22221                load_fnp_:   Invalid core  image for  FNP X  (init
22222                module  is not  last in  the module  chain), <core
22223                image pathname>
22224 
22225 
22226 
22227 
22228 load_fnp_                      384            08/03/23     MR12.7^L
22229 
22230 
22231      Stream:   BOS Typewriter.
22232 
22233      Time:     While system is running.
22234 
22235      Meaning:  In  tracing  through  the  module  chain, the last
22236                module in the  core image for FNP X  was not found
22237                to be the init module.   The init module has to be
22238                the  last module in  the module chain  because the
22239                init module releases itself and the rest of memory
22240                for  buffer space  when it  is finished executing.
22241                The  MCS core image  is probably damaged  and will
22242                have to be recreated.  The FNP cannot be loaded.
22243 
22244      Action:   Contact the system programming staff.
22245 
22246 
22247                [load_fnp_.pl1]
22248                load_fnp_:   Memory size of  MK in image  does not
22249                agree  with memory size  of NK in  CDT for FNP  X.
22250                Memory  size of  <min(M, N)>  from <CDT  or image>
22251                will be used.
22252 
22253 
22254 
22255      Stream:   BOS Typewriter.
22256 
22257      Time:     While system is running.
22258 
22259      Meaning:  The  memory size specified  in the MCS  core image
22260                does  not match the  memory size specified  in the
22261                CDT.  The  memory size in the MCS  core image that
22262                is loaded  will be set to the  minimum value.  The
22263                FNP load attempt will continue.
22264 
22265      Action:   The memory size value  in the MCS bind_fnp segment
22266                or CDT should be modified by site personnel.
22267 
22268 
22269                [load_fnp_.pl1]
22270                load_fnp_:  Unable to load  core image into FNP X.
22271                Core image  <core image pathname> will  not fit in
22272                32K.
22273 
22274 
22275      Stream:   BOS Typewriter.
22276 
22277      Time:     While system is running.
22278 
22279      Meaning:  The MCS core image to  be loaded into FNP X larger
22280                than   32K.    The   MCS   image   is  incorrectly
22281                constructed or damaged.  The FNP cannot be loaded.
22282 
22283      Action:   Contact the system programming staff.
22284 
22285 
22286 load_mst                       385            08/03/23     MR12.7^L
22287 
22288 
22289 
22290 
22291                [load_mst.pl1]
22292                load_mst:  bad header size SSS
22293 
22294 
22295      Stream:   BOS Typewriter (Crashes system)
22296 
22297      Time:     System Intialization.
22298 
22299      Meaning:  A  bad segment  header was  found on  the bootload
22300                tape.
22301 
22302      Action:   Follow normal recovery procedures.  $boot_tape
22303 
22304 
22305 
22306                [load_mst.pl1]
22307                load_mst:  error from slt_manager$build_entry
22308 
22309 
22310      Stream:   BOS Typewriter (Crashes system)
22311 
22312      Time:     System Intialization.
22313 
22314      Meaning:  This indicates a logic error in the supervisor, or
22315                CPU or memory hardware problems.
22316 
22317      Action:   Follow normal recovery procedures.  $boot_tape
22318 
22319 
22320 
22321                [load_mst.pl1]
22322                load_mst:  Missing linkage or defs.
22323 
22324 
22325      Stream:   BOS Typewriter (Crashes system)
22326 
22327      Time:     System Intialization.
22328 
22329      Meaning:  A linkage  or definitions section which  should be
22330                in the mst source appears to be missing.
22331 
22332      Action:   Follow normal recovery procedures.  $boot_tape
22333 
22334 
22335 
22336                [load_mst.pl1]
22337                load_mst:    NAME  can't   be  placed   into  file
22338                partition.
22339 
22340 
22341      Stream:   BOS Typewriter (Crashes system)
22342 
22343 
22344 load_mst                       386            08/03/23     MR12.7^L
22345 
22346 
22347      Time:     System Intialization.
22348 
22349      Meaning:  An error occurred while adding the named file from
22350                the mst into the bootload Multics file system.
22351 
22352      Action:   Follow normal recovery procedures.  $boot_tape
22353 
22354 
22355 
22356                [load_mst.pl1]
22357                load_mst:   Out  of  space  in  mst  area  of  bce
22358                partition.
22359 
22360 
22361      Stream:   BOS Typewriter (Crashes system)
22362 
22363      Time:     System Intialization.
22364 
22365      Meaning:  There is  not enough room  in the mst  area of the
22366                bce partition to hold collections 2.0 and 3.0.
22367 
22368      Action:   The size  of this area will need  to be increased.
22369                $boot_tape
22370 
22371 
22372 
22373                [load_mst.pl1]
22374                load_mst:  too many bce command segments.
22375 
22376 
22377      Stream:   BOS Typewriter (Crashes system)
22378 
22379      Time:     System Intialization.
22380 
22381      Meaning:  An exceptionally large number of segments appeared
22382                in  collection 1.5.    This probably  indicates an
22383                error in the mst.
22384 
22385      Action:   Follow normal recovery procedures.  $boot_tape
22386 
22387 
22388 
22389                [load_mst.pl1]
22390                load_mst:  unexpected control type TTT
22391 
22392 
22393      Stream:   BOS Typewriter (Crashes system)
22394 
22395      Time:     System Intialization.
22396 
22397      Meaning:  A segment  control word was found  out of sequence
22398                on the bootload tape.
22399 
22400 
22401 
22402 load_mst                       387            08/03/23     MR12.7^L
22403 
22404 
22405      Action:   Follow normal recovery procedures.  $boot_tape
22406 
22407 
22408 
22409                [load_mst.pl1]
22410                load_mst:  Unexpected DEFS/LINKAGE
22411 
22412 
22413      Stream:   BOS Typewriter (Crashes system)
22414 
22415      Time:     System Intialization.
22416 
22417      Meaning:  A linkage or definitions  section was found out of
22418                sequence in the mst source.
22419 
22420      Action:   Follow normal recovery procedures.  $boot_tape
22421 
22422 
22423 
22424                [load_mst.pl1]
22425                load_mst:  unknown control type TTT
22426 
22427 
22428      Stream:   BOS Typewriter (Crashes system)
22429 
22430      Time:     System Intialization.
22431 
22432      Meaning:  A  bad  segment  control  word  was  found  on the
22433                bootload tape.
22434 
22435      Action:   Follow normal recovery procedures.  $boot_tape
22436 
22437 
22438 
22439                [load_mst.pl1]
22440                load_mst:  XXX.   out of WWW.  pages  used in disk
22441                mst area.
22442 
22443 
22444      Stream:   BOS Typewriter.
22445 
22446      Meaning:  This message  shows the amount of the  mst area of
22447                the bce partition that is used to hold the mst.
22448 
22449      Action:   No operator action is required.  $boot_tape
22450 
22451 
22452 
22453                [load_system.pl1]
22454                load_system:   error  from  asd_$add_sentries  The
22455                system  could not remove  the write access  it had
22456                set to load the contents of a segment from the mst
22457                source.
22458 
22459 
22460 load_system                    388            08/03/23     MR12.7^L
22461 
22462 
22463      Stream:   BOS Typewriter (Crashes system)
22464 
22465      Time:     System Intialization.
22466 
22467      Meaning:  This indicates a logic error in the supervisor, or
22468                CPU or memory hardware problems.
22469 
22470      Action:   Follow normal recovery procedures.  $boot_tape
22471 
22472 
22473 
22474                [load_system.pl1]
22475                load_system:  error from set$entry_bound_ptr
22476 
22477 
22478      Stream:   BOS Typewriter (Crashes system)
22479 
22480      Time:     System Intialization.
22481 
22482      Meaning:  This indicates a logic error in the supervisor, or
22483                CPU or memory hardware problems.
22484 
22485      Action:   Follow normal recovery procedures.  $boot_tape
22486 
22487 
22488 
22489                [load_system.pl1]
22490                load_system:  illegal header length in mst source
22491 
22492 
22493      Stream:   BOS Typewriter (Crashes system)
22494 
22495      Time:     System Intialization.
22496 
22497      Meaning:  This indicates a logic error in the supervisor, or
22498                CPU or memory hardware problems.
22499 
22500      Action:   Follow normal recovery procedures.  $boot_tape
22501 
22502 
22503 
22504                [load_system.pl1]
22505                load_system:  illegal type in mst source
22506 
22507 
22508      Stream:   BOS Typewriter (Crashes system)
22509 
22510      Time:     System Intialization.
22511 
22512      Meaning:  This indicates a logic error in the supervisor, or
22513                CPU or memory hardware problems.
22514 
22515      Action:   Follow normal recovery procedures.  $boot_tape
22516 
22517 
22518 load_system                    389            08/03/23     MR12.7^L
22519 
22520 
22521 
22522 
22523                [load_system.pl1]
22524                load_system:  illegal type in mst source
22525 
22526 
22527      Stream:   BOS Typewriter (Crashes system)
22528 
22529      Time:     System Intialization.
22530 
22531      Meaning:  This indicates a logic error in the supervisor, or
22532                CPU or memory hardware problems.
22533 
22534      Action:   Follow normal recovery procedures.  $boot_tape
22535 
22536 
22537 
22538                [fnp_util.pl1]
22539                Loading FNP X, CORE_IMAGE VERSION
22540 
22541 
22542      Stream:   BOS Typewriter.
22543 
22544      Time:     Answering   service    initialization   and   each
22545                subsequent FNP bootload.
22546 
22547      Meaning:  Loading of FNP X has begun with a core image named
22548                CORE_IMAGE  (normally  "mcs")  of  version  number
22549                VERSION.
22550 
22551      Action:   No operator action is required.
22552 
22553 
22554                [lock.pl1]
22555                lock:  AST lock set at dir unlock time.
22556 
22557 
22558      Stream:   BOS Typewriter (Crashes system)
22559 
22560      Time:     While system is running.
22561 
22562      Meaning:  The  AST  was  found  locked  to  this  process at
22563                directory   unlock   time.    This   indicates   a
22564                supervisor programming error.
22565 
22566      Action:   $reboot
22567 
22568 
22569                [lock.pl1]
22570                lock:  dir_lock_read mylock err.  dp =PTR
22571 
22572 
22573      Stream:   BOS Typewriter (Crashes system)
22574 
22575 
22576 lock                           390            08/03/23     MR12.7^L
22577 
22578 
22579      Time:     While system is running.
22580 
22581      Meaning:  An attempt  to lock a directory  for reading found
22582                the  directory  already  locked  to  this process.
22583                This indicates a supervisor programming error.
22584 
22585      Action:   $reboot
22586 
22587 
22588                [lock.pl1]
22589                lock:  dir_lock_write mylock err.  dp =PTR
22590 
22591 
22592      Stream:   BOS Typewriter (Crashes system)
22593 
22594      Time:     While system is running.
22595 
22596      Meaning:  An attempt  to lock a directory  for writing found
22597                the  directory  already  locked  to  this process.
22598                This indicates a supervisor programming error.
22599 
22600      Action:   $reboot
22601 
22602 
22603                [lock.pl1]
22604                lock:  lock PTR not  equal to processid.  caller =
22605                PTR
22606 
22607 
22608      Stream:   $lock_severity
22609 
22610      Time:     While system is running.
22611 
22612      Meaning:  An attempt was made to  unlock a lock found not to
22613                be  held  by  this   process.   This  indicates  a
22614                supervisor programming error.
22615 
22616      Action:   $reboot
22617 
22618 
22619                [lock.pl1]
22620                lock:  LOCK_DIR:  dir_lock_seg full.
22621 
22622 
22623      Stream:   BOS Typewriter (Crashes system)
22624 
22625      Time:     While system is running.
22626 
22627      Meaning:  The segment used to  record all locked directories
22628                overflowed.  This may be a hardware problem.
22629 
22630      Action:   $reboot
22631 
22632 
22633 
22634 lock                           391            08/03/23     MR12.7^L
22635 
22636 
22637 
22638 
22639                [lock.pl1]
22640                lock:  LOCK_DIR:  Too many readers.
22641 
22642 
22643      Stream:   BOS Typewriter (Crashes system)
22644 
22645      Time:     While system is running.
22646 
22647      Meaning:  Too  many processes  attempted to  request a  read
22648                lock  on a given  directory.  This may  indicate a
22649                hardware problem.
22650 
22651      Action:   $reboot
22652 
22653 
22654                [lock.pl1]
22655                lock:  LOCK_DIR:   write lock call with  read lock
22656                held.  dp = PTR, uid = UID.
22657 
22658 
22659      Stream:   BOS Typewriter (Terminates user process)
22660 
22661      Time:     While system is running.
22662 
22663      Meaning:  A request was made to lock a directory for writing
22664                when the process already  possessed a read lock on
22665                that  directory.   This   indicates  a  supervisor
22666                programming error.
22667 
22668      Action:   $reboot
22669 
22670 
22671                [lock.pl1]
22672                lock:  lock_fast mylock err PTR
22673 
22674 
22675      Stream:   BOS Typewriter (Crashes system)
22676 
22677      Time:     While system is running.
22678 
22679      Meaning:  An  attempt to  lock a  fast lock  found the  lock
22680                already  locked to  the requesting  process.  This
22681                indicates a supervisor programming error.
22682 
22683      Action:   $reboot
22684 
22685 
22686                [lock.pl1]
22687                lock:  pds$block_lock_count <= 0.  caller = PTR
22688 
22689 
22690 
22691 
22692 lock                           392            08/03/23     MR12.7^L
22693 
22694 
22695      Stream:   $lock_severity
22696 
22697      Time:     While system is running.
22698 
22699      Meaning:  An attempt to unlock a lock found that the process
22700                was holding no locks.  This indicates a supervisor
22701                programming error.
22702 
22703      Action:   $reboot
22704 
22705 
22706                [lock.pl1]
22707                lock:  stacq hardware failure on PTR
22708 
22709 
22710      Stream:   BOS Typewriter (Crashes system)
22711 
22712      Time:     While system is running.
22713 
22714      Meaning:  The hardware  failed to unlock the  specified lock
22715                using a stacq instruction.
22716 
22717      Action:   Fix the hardware.
22718 
22719 
22720                [lock.pl1]
22721                lock:   unlock_dir with dir.modify  - uid =  UID -
22722                callerp = PTR
22723 
22724 
22725      Stream:   Logged in SYSERR log.
22726 
22727      Time:     While system is running.
22728 
22729      Meaning:  A  directory being  unlocked appears  to have been
22730                undergoing  a modification  sequence that  has not
22731                completed.
22732 
22733      Action:   The next  reference to the directory  will force a
22734                directory salvage.
22735 
22736 
22737                [lock.pl1]
22738                lock:   UNLOCK_DIR:  dir DIR_LOCK_IND  not locked.
22739                caller = PTR.
22740 
22741 
22742      Stream:   $lock_severity
22743 
22744      Time:     While system is running.
22745 
22746      Meaning:  A  request to  unlock a  directory found  that the
22747                dir_lock_seg   entry  does   not  show   that  the
22748 
22749 
22750 lock                           393            08/03/23     MR12.7^L
22751 
22752 
22753                directory was locked.
22754 
22755 
22756                A:  $reboot
22757 
22758 
22759 
22760                [lock.pl1]
22761                lock:  UNLOCK_DIR:  dir DIR_LOCK_IND unlock called
22762                with bad uid, caller = PTR
22763 
22764 
22765      Stream:   Logged in SYSERR log.
22766 
22767      Time:     While system is running.
22768 
22769      Meaning:  A request to unlock a directory found that the UID
22770                of  the directory  does not  match the  UID at the
22771                time the  directory was locked.  However,  the UID
22772                does  match  that  in   the  KST.   This  normally
22773                indicates that  the directory was  salvaged during
22774                the time that it was locked.
22775 
22776 
22777 
22778                [lock.pl1]
22779                lock:  UNLOCK_DIR:  lock count 0.
22780 
22781 
22782      Stream:   $lock_severity
22783 
22784      Time:     While system is running.
22785 
22786      Meaning:  An  attempt  to  unlock   a  directory  found  the
22787                dir_lock_seg entry  for the directory  not listing
22788                the directory as locked.
22789 
22790      Action:   $reboot
22791 
22792 
22793                [lock.pl1]
22794                lock:   UNLOCK_DIR:   lock   not  read  locked  to
22795                process.
22796 
22797 
22798      Stream:   $lock_severity
22799 
22800      Time:     While system is running.
22801 
22802      Meaning:  A request to unlock a directory locked for reading
22803                found that the requesting  process was not holding
22804                the directory locked.
22805 
22806 
22807 
22808 lock                           394            08/03/23     MR12.7^L
22809 
22810 
22811      Action:   $reboot
22812 
22813 
22814                [lock.pl1]
22815                lock:   UNLOCK_DIR:   lock  not  write  locked  to
22816                process.
22817 
22818 
22819      Stream:   $lock_severity
22820 
22821      Time:     While system is running.
22822 
22823      Meaning:  A request to unlock a  directory that was found to
22824                be  locked  for  writing  was  not  locked to this
22825                process.
22826 
22827      Action:   $reboot
22828 
22829 
22830                [lock.pl1]
22831                lock:  UNLOCK_DIR:  UID Mismatch.
22832 
22833 
22834      Stream:   $lock_severity
22835 
22836      Time:     While system is running.
22837 
22838      Meaning:  When attempting to unlock a directory, the UID for
22839                the directory found in  the dir_lock_seg entry did
22840                not match that of the directory.
22841 
22842      Action:   $reboot
22843 
22844 
22845                [lock.pl1]
22846                lock:  unlock_fast lock PTR not locked to process.
22847                caller = PTR
22848 
22849 
22850      Stream:   $lock_severity
22851 
22852      Time:     While system is running.
22853 
22854      Meaning:  An attempt  to unlock a  fast lock found  that the
22855                lock was not held by the requesting process.  This
22856                indicates a supervisor programming error.
22857 
22858      Action:   $reboot
22859 
22860 
22861                [lock.pl1]
22862                lock:  VALIDATE_CACHE:   FAILED running on  cpu N,
22863                memory address OOOOOOOO (oct).
22864 
22865 
22866 lock                           395            08/03/23     MR12.7^L
22867 
22868 
22869      Stream:   BOS Typewriter.
22870 
22871      Time:     While system is running.
22872 
22873      Meaning:  This is  most likely a cache  write notify problem
22874                with  the 8/70m processor  "CPU N", or  the System
22875                Control   Unit  containing  the   "memory  address
22876                OOOOOOOO."
22877 
22878      Action:   Contact the system programming staff._sa
22879 
22880 
22881                [page_error.alm]
22882                lock_volmap:    MYLOCK   on    volmap   lock   for
22883                dskX_NN{S}.
22884 
22885 
22886      Stream:   BOS Typewriter (Crashes system)
22887 
22888      Time:     While system is running.
22889 
22890      Meaning:  A  process attempted to  lock the Volume  Map lock
22891                for  dskX_NN{S}  while  already  owning  the lock.
22892                This indicates a software malfunction.
22893 
22894      Action:   Follow normal recovery procedures.
22895 
22896 
22897                [page_error.alm]
22898                lock_volmap:  STACQ fails on dskX_NN{S}.
22899 
22900 
22901      Stream:   BOS Typewriter (Crashes system)
22902 
22903      Time:     While system is running.
22904 
22905      Meaning:  The stacq instruction, used to lock the Volume Map
22906                on  dskX_NN{S}, did  not operate  correctly.  This
22907                indicates processor or memory malfunction.
22908 
22909      Action:   Follow normal recovery procedures.
22910 
22911 
22912                [logical_volume_manager.pl1]
22913                logical_volume_manager:    nonzero   brother   pvt
22914                thread
22915 
22916 
22917      Stream:   BOS Typewriter (Crashes system)
22918 
22919      Time:     While system is running.
22920 
22921 
22922 
22923 
22924 logical_volume_manager         396            08/03/23     MR12.7^L
22925 
22926 
22927      Meaning:  This indicates a logic error in the supervisor, or
22928                CPU or memory hardware problems.
22929 
22930      Action:   Follow normal recovery procedures.
22931 
22932 
22933                [lg_ctl_.pl1]
22934                LOGIN PERSON.PROJECT PROC_TYPE CHANNEL (STATE)
22935 
22936 
22937      Stream:   as (severity1)
22938 
22939      Time:     While system is running.
22940 
22941      Meaning:  The    user   PERSON.PROJECT    was   successfully
22942                identified  and authenticated on  channel CHANNEL.
22943                The process type, PROC_TYPE, indicates the type of
22944                login and can be either "int", "dmn", "opr", or "Q
22945                N".  These correspond  to "interactive", "daemon",
22946                "operator",   or   "absentee"   logins.    "Q   N"
22947                designates  the absentee  queue.  STATE  indicates
22948                the  state  of  the   login.   It  can  either  be
22949                "create",  indicating that  a process  was created
22950                for the user; "connect  loop", indicating that the
22951                user was  queried as to  what he/she wanted  to do
22952                with  respect to  disconnected processes;  or some
22953                other value indicating what was done to the user's
22954                disconnected processes.
22955 
22956 
22957 
22958                [lg_ctl_.pl1]
22959                LOGIN  DENIED   PERSON.PROJECT  PROC_TYPE  CHANNEL
22960                (REASON)
22961 
22962 
22963      Stream:   as (severity1)
22964 
22965      Time:     While system is running.
22966 
22967      Meaning:  An operator login was denied for PERSON.PROJECT on
22968                channel  CHANNEL  for   the  reason  specified  in
22969                REASON.   The  process  type  is  opr for operator
22970                login attempts.
22971 
22972 
22973 
22974                [daemon_user_manager_.pl1]
22975                login:  Cannot login NAME.PROJ SOURCE
22976                ERROR_MESSAGE
22977 
22978 
22979 
22980 
22981 
22982 login                          397            08/03/23     MR12.7^L
22983 
22984 
22985      Stream:   as (severity1)
22986 
22987      Time:     While system is running.
22988 
22989      Meaning:  Illegal  login  arguments  have  been  given  when
22990                attempting to log in a daemon user.  No action was
22991                taken.
22992 
22993      Action:   Enter a corrected command.
22994 
22995 
22996                [daemon_user_manager_.pl1]
22997                login:  ERROR_MESSAGE.  creating event channel for
22998                NAME PROJ SOURCE
22999 
23000 
23001      Stream:   as (severity2)
23002 
23003      Time:     In response to an operator command.
23004 
23005      Meaning:  This message  indicates a system error  in setting
23006                up a daemon user.  The daemon cannot be logged in.
23007 
23008      Action:   Contact the system programming staff.  Try again.
23009 
23010 
23011 
23012                [daemon_user_manager_.pl1]
23013                login:   ERROR_MESSAGE.   creating  proc  for NAME
23014                PROJ SOURCE
23015 
23016 
23017      Stream:   as (severity2)
23018 
23019      Time:     In response to an operator command.
23020 
23021      Meaning:  A  daemon  process  cannot  be  created.   This is
23022                probably due to a  serious system bug.  The daemon
23023                is not logged in.
23024 
23025      Action:   Contact the system programming staff.
23026 
23027 
23028                [daemon_user_manager_.pl1]
23029                login:  ERROR_MESSAGE.   declaring ev_call_chn for
23030                NAME PROJ SOURCE
23031 
23032 
23033      Stream:   as (severity2)
23034 
23035      Time:     In response to an operator command.
23036 
23037 
23038 
23039 
23040 login                          398            08/03/23     MR12.7^L
23041 
23042 
23043      Meaning:  This message  indicates a system error  in setting
23044                up a daemon user.  The daemon cannot be logged in.
23045 
23046      Action:   Contact the system programming staff.
23047 
23048 
23049                [daemon_user_manager_.pl1]
23050                login:  NAME.PROJ already logged in on SOURCE
23051 
23052 
23053      Stream:   as (severity1)
23054 
23055      Time:     In response to an operator command.
23056 
23057      Meaning:  This is  the response to the login  command if the
23058                source  specified  by  SOURCE  is  already in use.
23059                Each daemon  process must have a  different source
23060                name.  The daemon user is not logged in.  Usually,
23061                this  message  is  the  result  of  attempting  to
23062                perform an operation that has already been done.
23063 
23064      Action:   Reissue  the   command  with  another   source  or
23065                continue.
23066 
23067 
23068                [daemon_user_manager_.pl1]
23069                login:  no login NAME.PROJ SOURCE REASON
23070 
23071 
23072      Stream:   as (severity1)
23073 
23074      Time:     In response to an operator command.
23075 
23076      Meaning:  The  operator  issued  a  login  NAME  PROJ SOURCE
23077                command but the daemon user named cannot be logged
23078                in for the reason given.   If REASON is badpers or
23079                bad_proj,   the   NAME   or   PROJ   was  probably
23080                misspelled.   If  REASON  is  non_daem,  the  user
23081                NAME.PROJ is not authorized to be a daemon user.
23082 
23083      Action:   Correct the  command if misspelled and  try to log
23084                in again.
23085 
23086 
23087                [lg_ctl_.pl1]
23088                LOGOUT PERSON.PROJECT PROC_TYPE CHANNEL (REASON)
23089 
23090 
23091      Stream:   as (severity1)
23092 
23093      Time:     While system is running.
23094 
23095 
23096 
23097 
23098 LOGOUT                         399            08/03/23     MR12.7^L
23099 
23100 
23101      Meaning:  The user, PERSON.PROJECT, on channel CHANNEL, with
23102                process type  PROC_TYPE either logged out,  or was
23103                logged  out.  The  reason is  specified in REASON.
23104                This user/channel logout did not affect a process.
23105                This  can  occur  for  slave  dialed  channels  or
23106                channels dropped from message coordinator service.
23107 
23108 
23109 
23110                [daemon_user_manager_.pl1]
23111                logout:  Entry not found.  NAME PROJ SOURCE
23112 
23113 
23114      Stream:   as (severity1)
23115 
23116      Time:     In response to an operator logout command.
23117 
23118      Meaning:  This is a response to an incorrect logout command.
23119                There  is no  entry in  the daemon  user table for
23120                NAME.PROJ.
23121 
23122      Action:   Check the spelling for accuracy and try again.
23123 
23124 
23125                [disk_table_.pl1]
23126                lv LVNAME is not mounted
23127 
23128 
23129      Stream:   Initializer process output.
23130 
23131      Time:     While system is running.
23132 
23133      Meaning:  The  operator  issued  a  dlv  LVNAME  command but
23134                LVNAME was not mounted.
23135 
23136      Action:   Enter a corrected command line.
23137 
23138 
23139                [disk_table_.pl1]
23140                lv LVNAME mounted
23141 
23142 
23143      Stream:   Initializer process output.
23144 
23145      Time:     While system is running.
23146 
23147      Meaning:  The mounting of LVNAME is complete.
23148 
23149      Action:   Enter a corrected command line.
23150 
23151 
23152                [lv_request_.pl1]
23153 
23154 
23155 
23156 lv_request_                    400            08/03/23     MR12.7^L
23157 
23158 
23159                lv_request_:   Beginning mount   of LV  LVNAME for
23160                PERSON.PROJECT.TAG PROCESSID
23161 
23162 
23163      Stream:   as (severity 0)
23164 
23165      Time:     When processing a disk mount/demount interrupt.
23166 
23167      Meaning:  The volumes  associated with LVNAME are  now being
23168                mounted    for   the    process   identified    by
23169                PERSON.PROJECT.TAG and PROCESSID.
23170 
23171      Action:   No operator action is required.
23172 
23173 
23174                [lv_request_.pl1]
23175                lv_request_:  ERROR_MESSAGE.  Masking event calls.
23176 
23177 
23178      Stream:   as (severity 2)
23179 
23180      Time:     When processing a disk mount/demount interrupt.
23181 
23182      Meaning:  An error  occurred while attempting to  mask event
23183                call   wakeups.    ERROR_MESSAGE   is   the   text
23184                associated  with   the  error  code   returned  by
23185                ipc_$mask_ev_calls.This indicates a logic error in
23186                the   supervisor,  or   CPU  or   memory  hardware
23187                problems.
23188 
23189      Action:   Contact the system programming staff._sa
23190 
23191 
23192                [lv_request_.pl1]
23193                lv_request_:      ATTACHED     LV     LVNAME    to
23194                PERSON.PROJECT.TAG PROCESSID.
23195 
23196 
23197      Stream:   as (severity 0)
23198 
23199      Time:     When processing a disk mount/demount interrupt.
23200 
23201      Meaning:  This message records  attachment of logical volume
23202                LVNAME    to    the    process    identified    by
23203                PERSON.PROJECT.TAG and PROCESSID.
23204 
23205      Action:   No operator action is required.
23206 
23207 
23208                [lv_request_.pl1]
23209                lv_request_:   bad  LV  attach  table  index  N in
23210                {DE}MOUNT request
23211 
23212 
23213 
23214 lv_request_                    401            08/03/23     MR12.7^L
23215 
23216 
23217      Stream:   as (severity 2)
23218 
23219      Time:     When processing a disk mount/demount interrupt.
23220 
23221      Meaning:  The Logical Volume attach table index given in the
23222                event message associated with the mount or demount
23223                interrupt is invalid.This  indicates a logic error
23224                in  the  supervisor,  or  CPU  or  memory hardware
23225                problems.
23226 
23227      Action:   Contact the system programming staff._sa
23228 
23229 
23230                [lv_request_.pl1]
23231                lv_request_:  bad transmission:  EVENT_MESSAGE
23232 
23233 
23234      Stream:   as (severity 2)
23235 
23236      Time:     When processing a disk mount/demount interrupt.
23237 
23238      Meaning:  An  unexpected EVENT_MESSAGE  was received  by the
23239                mount/demount  interrupt handler.This  indicates a
23240                logic  error in the  supervisor, or CPU  or memory
23241                hardware problems.
23242 
23243      Action:   Contact the system programming staff._sa
23244 
23245 
23246                [lv_request_.pl1]
23247                lv_request_:      Cannot    send     message    to
23248                PERSON.PROJECT.TAG PROCESSID:  ADDED_INFO
23249 
23250 
23251      Stream:   as (severity 2)
23252 
23253      Time:     When processing a disk mount/demount interrupt.
23254 
23255      Meaning:  The  Initializer  is  attempting  to  respond to a
23256                request to mount or  demount a logical volume, but
23257                is unable  to send a  wakeup to the  user process.
23258                The process  may have logged out.This  indicates a
23259                logic  error in the  supervisor, or CPU  or memory
23260                hardware problems.
23261 
23262      Action:   Contact the system programming staff._sa
23263 
23264 
23265                [lv_request_.pl1]
23266                lv_request_:      Denied      LV     LVNAME     to
23267                PERSON.PROJECT.TAG PROCESSID
23268 
23269 
23270 
23271 
23272 lv_request_                    402            08/03/23     MR12.7^L
23273 
23274 
23275      Stream:   as (severity 0)
23276 
23277      Time:     When dismounting a logical volume.
23278 
23279      Meaning:  The user process  identified by PERSON.PROJECT.TAG
23280                and  PROCESSID  was  waiting  to  mount  a logical
23281                volume  LVNAME which  is being  dismounted by  the
23282                operator.  The mount request was therefore denied.
23283 
23284      Action:   No operator action is required.
23285 
23286 
23287                [lv_request_.pl1]
23288                lv_request_:     DETACHED     LV    LVNAME    from
23289                PERSON.PROJECT.TAG PROCESSID.
23290 
23291 
23292      Stream:   as (severity 0)
23293 
23294      Time:     When processing a disk mount/demount interrupt.
23295 
23296      Meaning:  This message records  detachment of logical volume
23297                LVNAME    from   the    process   identified    by
23298                PERSON.PROJECT.TAG and PROCESSID.
23299 
23300      Action:   No operator action is required.
23301 
23302 
23303                [lv_request_.pl1]
23304                lv_request_:   ERROR_MESSAGE.   Cannot  initialize
23305                logical volume mounting software.
23306 
23307 
23308 
23309      Stream:   as (severity 2)
23310 
23311      Time:     System Intialization.
23312 
23313      Meaning:  Initialization of the  logical volume attach table
23314                failed.  ERROR_MESSAGE is the text associated with
23315                the       error       code       returned       by
23316                initializer_mdc_$init_lvat.
23317 
23318      Action:   Contact the system programming staff._sa
23319 
23320 
23321                [lv_request_.pl1]
23322                lv_request_:   No  drives  available  to  mount LV
23323                LVNAME for PERSON.PROJECT.TAG PROCESSID
23324 
23325 
23326 
23327      Stream:   as (severity 0)
23328 
23329 
23330 lv_request_                    403            08/03/23     MR12.7^L
23331 
23332 
23333      Time:     When processing a disk mount/demount interrupt.
23334 
23335      Meaning:  Drives needed to mount  the volumes of LVNAME were
23336                in use  or deleted.  The logical  volume could not
23337                be   mounted  for    the  process   identified  by
23338                PERSON.PROJECT.TAG and PROCESSID.
23339 
23340      Action:   No operator action is required.
23341 
23342 
23343                [lv_request_.pl1]
23344                lv_request_:    Spurious    wakeup   EVENT_MESSAGE
23345                received from PERSON.PROJECT.TAG PROCESSID RINGNO
23346 
23347 
23348 
23349      Stream:   as (severity 0)
23350 
23351      Time:     When processing a disk mount/demount interrupt.
23352 
23353      Meaning:  A wakeup was received on the lv_request_ interrupt
23354                event channel  with event data  EVENT_MESSAGE from
23355                the process with PERSON.PROJECT.TAG, PROCESSID and
23356                RINGNO.   This message  is invalid  because it did
23357                not come from the Initializer, ring 1 environment.
23358 
23359      Action:   No operator action is required.
23360 
23361 
23362                [lv_request_.pl1]
23363                lv_request_:    Unexpected    condition   CONDNAME
23364                occurred.
23365 
23366 
23367      Stream:   as (severity 2)
23368 
23369      Time:     When processing a disk mount/demount interrupt.
23370 
23371      Meaning:  Condition  CONDNAME   was  signalled  unexpectedly
23372                during a  mount or demount request.   An answering
23373                service  dump is  created to  further document the
23374                cause of the error.
23375 
23376      Action:   Contact the system programming staff._sa.
23377 
23378 
23379                [lv_request_communicator_.pl1]
23380                lv_request_communicator_:  code CCC from wakeup
23381 
23382 
23383      Stream:   BOS Typewriter.
23384 
23385      Time:     While system is running.
23386 
23387 
23388 lv_request_communicator_       404            08/03/23     MR12.7^L
23389 
23390 
23391      Meaning:  A  wakeup could  not  be  sent to  the initializer
23392                process  in order  to perform  communication about
23393                attachment/detachment of logical volumes.
23394 
23395      Action:   Contact the system programming staff.
23396 
23397 
23398                [lv_request_communicator_.pl1]
23399                lv_request_communicator_:  lock ^= processid lvate
23400                PPP
23401 
23402 
23403      Stream:   BOS Typewriter.
23404 
23405      Time:     In response to a user's detach_lv command
23406 
23407      Meaning:  A  logical volume   attachment table  entry became
23408                disassociated  from a  user  to  whom it  had been
23409                assigned.   This indicates  a logic  error in  the
23410                supervisor, or CPU or memory hardware problems.
23411 
23412      Action:   Contact the system programming staff.  Be prepared
23413                to  demount logical  volumes manually  which might
23414                otherwise have been demounted automatically.
23415 
23416 
23417 
23418                [make_branches.pl1]
23419                make_branches:  bad path name PATH
23420 
23421 
23422      Stream:   BOS Typewriter (Crashes system)
23423 
23424      Time:     System Intialization.
23425 
23426      Meaning:  This indicates a logic error in the supervisor, or
23427                CPU or memory hardware problems.
23428 
23429      Action:   Follow normal recovery procedures.  $boot_tape
23430 
23431 
23432 
23433                [make_branches.pl1]
23434                make_branches:     could    not    delete    PATH:
23435                ERROR_MESSAGE
23436 
23437 
23438      Stream:   BOS Typewriter (Crashes system)
23439 
23440      Time:     System Intialization.
23441 
23442      Meaning:  This indicates a logic error in the supervisor, or
23443                CPU or memory hardware problems.
23444 
23445 
23446 make_branches                  405            08/03/23     MR12.7^L
23447 
23448 
23449      Action:   Follow normal recovery procedures.  $boot_tape
23450 
23451 
23452 
23453                [make_branches.pl1]
23454                make_branches:   delete:   could   not  turn  PATH
23455                safety switch off:  ERROR_MESSAGE
23456 
23457 
23458      Stream:   BOS Typewriter (Crashes system)
23459 
23460      Time:     System Intialization.
23461 
23462      Meaning:  This indicates a logic error in the supervisor, or
23463                CPU or memory hardware problems.
23464 
23465      Action:   Follow normal recovery procedures.  $boot_tape
23466 
23467 
23468 
23469                [make_branches.pl1]
23470                make_branches:  delete:  failed to rename
23471 
23472 
23473      Stream:   BOS Typewriter (Crashes system)
23474 
23475      Time:     System Intialization.
23476 
23477      Meaning:  This indicates a logic error in the supervisor, or
23478                CPU or memory hardware problems.
23479 
23480      Action:   Follow normal recovery procedures.  $boot_tape
23481 
23482 
23483 
23484                [make_branches.pl1]
23485                make_branches:   delete:  renaming NAME  to UNIQUE
23486                in DIRNAME
23487 
23488 
23489      Stream:   BOS Typewriter.
23490 
23491      Time:     System Intialization.
23492 
23493      Meaning:  A  segment which is  being loaded from  the system
23494                tape  encountered a  previous copy  on a  physical
23495                volume which is not  now mounted.  The old version
23496                of the  segment is being  renamed so that  the new
23497                copy can be loaded.
23498 
23499      Action:   Note  for system   programmer action.   The system
23500                programmers will  want to delete  the unique-named
23501                segment.
23502 
23503 
23504 make_branches                  406            08/03/23     MR12.7^L
23505 
23506 
23507 
23508 
23509                [make_branches.pl1]
23510                make_branches:    error  from   append  on   PATH:
23511                ERROR_MESSAGE
23512 
23513 
23514      Stream:   BOS Typewriter (Crashes system)
23515 
23516      Time:     System Intialization.
23517 
23518      Meaning:  This indicates a logic error in the supervisor, or
23519                CPU or memory hardware problems.
23520 
23521      Action:   Follow normal recovery procedures.  $boot_tape
23522 
23523 
23524 
23525                [make_branches.pl1]
23526                make_branches:   error  from  asd_$replace_sall on
23527                PATH:  ERROR_MESSAGE
23528 
23529 
23530      Stream:   BOS Typewriter (Crashes system)
23531 
23532      Time:     System Intialization.
23533 
23534      Meaning:  This indicates a logic error in the supervisor, or
23535                CPU or memory hardware problems.
23536 
23537      Action:   Follow normal recovery procedures.  $boot_tape
23538 
23539 
23540 
23541                [make_branches.pl1]
23542                make_branches:    error  from   chname  on   PATH:
23543                ERROR_MESSAGE
23544 
23545 
23546      Stream:   BOS Typewriter (Crashes system)
23547 
23548      Time:     System Intialization.
23549 
23550      Meaning:  This indicates a logic error in the supervisor, or
23551                CPU or memory hardware problems.
23552 
23553      Action:   Follow normal recovery procedures.  $boot_tape
23554 
23555 
23556 
23557                [make_sdw.pl1]
23558                make_sdw:  no hardcore partitions available.
23559 
23560 
23561 
23562 make_sdw                       407            08/03/23     MR12.7^L
23563 
23564 
23565      Stream:   BOS Typewriter (Crashes system)
23566 
23567      Time:     System Intialization.
23568 
23569      Meaning:  No hardcore partitions were  defined on any of the
23570                packs on  the drives specified by  the ROOT CONFIG
23571                card.   At  least  the  RPV  must  have a hardcore
23572                partition.  Supervisor segments cannot be created.
23573 
23574      Action:   If this is a cold  boot, which is most likely, the
23575                RPV was initialized  without a hardcore partition.
23576                It  must  be  reinitialized.   Check  the  PART HC
23577                CONFIG  card, one of  which must describe  the RPV
23578                during a cold boot, and  reboot.  If this is not a
23579                cold  boot, the RPV  has been damaged,  and volume
23580                recovery must be undertaken.
23581 
23582 
23583 
23584                [make_sdw.pl1]
23585                make_sdw:  out of hardcore partition for SEGNAME.
23586 
23587 
23588      Stream:   BOS Typewriter (Crashes system)
23589 
23590      Time:     System Intialization.
23591 
23592      Meaning:  In  attempting  to  allocate  space  for  hardcore
23593                segment  SEGNAME, no more  room could be  found in
23594                any of the defined hardcore partitions.
23595 
23596      Action:   If  this is  a  cold  boot, redefine  the hardcore
23597                partition of the RPV to  be larger.  At least 1000
23598                (decimal) records is recommended.  Change the PART
23599                HC  CONFIG  card  describing  the  RPV to indicate
23600                this,  and reboot.   If this  is not  a cold boot,
23601                this  situation is  highly unlikely  and indicates
23602                damage to  one or more RLV  volume labels.  Volume
23603                recovery  for part  or all  of the  RLV should  be
23604                undertaken.
23605 
23606 
23607 
23608                [make_sdw.pl1]
23609                make_sdw:  XXXk ast pool to small.
23610 
23611 
23612      Stream:   BOS Typewriter (Crashes system)
23613 
23614      Time:     System Intialization.
23615 
23616 
23617 
23618 
23619 
23620 make_sdw                       408            08/03/23     MR12.7^L
23621 
23622 
23623      Meaning:  There were not enough AST entries of size XXX k to
23624                allocate   the  permanent   AST  entries   of  the
23625                supervisor.
23626 
23627      Action:   Increase the  number of AST entries  of that size,
23628                as   specified    on   the   SST    CONFIG   card,
23629                substantially, and reboot.
23630 
23631 
23632 
23633                [make_segs_paged.pl1]
23634                make_segs_paged:  sorted_segs array overflowed.
23635 
23636 
23637      Stream:   BOS Typewriter (Crashes system)
23638 
23639      Time:     System Intialization.
23640 
23641      Meaning:  The  number of paged  segments in collection  1 is
23642                larger  than the  internal buffer  in the  program
23643                make_segs_paged  required  to  sort  them  by main
23644                memory  address.   This   indicates  an  error  in
23645                construction of the system  (i.e., too many header
23646                entries), or may be  symptomatic of main memory or
23647                CPU hardware problems.
23648 
23649      Action:   If this recurs, revert  to a previous system tape.
23650                No emergency shutdown is needed.
23651 
23652 
23653 
23654                [makestack.pl1]
23655                makestack:  error appending STACKNAME
23656 
23657 
23658      Stream:   BOS Typewriter (Terminates user process)
23659 
23660      Time:     System         Intialization.         Process/ring
23661                initialization.  Just prior to using a new ring.
23662 
23663      Meaning:  The process directory is probably messed up.
23664 
23665      Action:   Ignore unless it's the  initializer, in which case
23666                bring  the system  back up.   If problem persists,
23667                contact the system administrator.
23668 
23669 
23670 
23671                [makestack.pl1]
23672                makestack:    error   finding   DIRNAME>ENAME  for
23673                STACKNAME.
23674 
23675 
23676 
23677 
23678 makestack                      409            08/03/23     MR12.7^L
23679 
23680 
23681      Stream:   BOS Typewriter (Terminates user process)
23682 
23683      Time:     System         Intialization.         Process/ring
23684                initialization.
23685 
23686      Action:   Ignore unless it's the  initializer, in which case
23687                bring  the system  back up.   If problem persists,
23688                contact the system administrator.
23689 
23690 
23691 
23692                [makestack.pl1]
23693                makestack:  error from initiate_search_rules.
23694 
23695 
23696      Stream:   BOS Typewriter (Terminates user process)
23697 
23698      Time:     Process/ring initialization.  Just  prior to using
23699                new ring.
23700 
23701      Meaning:  The  default  search  rules  are  missing from ahd
23702                (active hardcore data).   These are usually loaded
23703                by the command set_system_search_rules.
23704 
23705      Action:   Contact the system programming staff._sa
23706 
23707 
23708                [makestack.pl1]
23709                makestack:    error  from   set$max_length_ptr  on
23710                STACKNAME.
23711 
23712 
23713      Stream:   BOS Typewriter (Terminates user process)
23714 
23715      Time:     System         Intialization.         Process/ring
23716                initialization.  Just prior to using a new ring.
23717 
23718      Meaning:  The process directory is probably messed up.
23719 
23720      Action:   Ignore unless it's the  initializer, in which case
23721                bring  the system  back up.   If problem persists,
23722                contact the system administrator.
23723 
23724 
23725 
23726                [makestack.pl1]
23727                makestack:  error  getting bit count  for original
23728                prelinked STACK_NAME
23729 
23730 
23731      Stream:   BOS Typewriter (Terminates user process)
23732 
23733 
23734 
23735 
23736 makestack                      410            08/03/23     MR12.7^L
23737 
23738 
23739      Time:     System         Intialization.         Process/ring
23740                initialization.  Just prior to using a new ring.
23741 
23742      Meaning:  A  directory containing  a prelinked  subsystem is
23743                probably messed up.
23744 
23745      Action:   The directory should be prelinked again.
23746 
23747 
23748                [makestack.pl1]
23749                makestack:  error initiating STACKNAME
23750 
23751 
23752      Stream:   BOS Typewriter (Terminates user process)
23753 
23754      Time:     System         Intialization.         Process/ring
23755                initialization.  Just prior to using a new ring.
23756 
23757      Action:   Ignore unless it's the  initializer, in which case
23758                bring  the system  back up.   If problem persists,
23759                contact the system administrator.
23760 
23761 
23762 
23763                [mc_commands_.pl1]
23764                mc_commands_$mc_login:   Channel  XXXX  dialed  to
23765                Initializer (NAME ACCEPTED).
23766 
23767 
23768      Stream:   as (severity 1)
23769 
23770      Time:     In response to a message coordinator dial request.
23771 
23772      Meaning:  Informative  message indicating that  a successful
23773                dialin  occured on  the specified  channel by  the
23774                named operator.
23775 
23776      Action:   No operator action is required.
23777 
23778 
23779                [mc_commands_.pl1]
23780                mc_commands_$mc_login:   Channel  XXXX  dialed  to
23781                Initializer (NAME).
23782 
23783 
23784      Stream:   as (severity 1)
23785 
23786      Time:     In response to a message coordinator dial request.
23787 
23788      Meaning:  Informative  message indicating that  a successful
23789                dialin  occured on  the specified  channel by  the
23790                named operator.   A subsequent accept  is required
23791 
23792 
23793 
23794 mc_commands_$mc_login          411            08/03/23     MR12.7^L
23795 
23796 
23797                by  an  authenticated  operator  to  complete  the
23798                attachment.
23799 
23800      Action:   No operator action is required.
23801 
23802 
23803                [mc_commands_.pl1]
23804                mc_commands_$mc_login:    Channel  XXXX   vchannel
23805                (YYYY) dialed to Initializer (NAME ACCEPTED).
23806 
23807 
23808      Stream:   as (severity 1)
23809 
23810      Time:     In response to a message coordinator dial request.
23811 
23812      Meaning:  Informative  message indicating that  a successful
23813                dialin  occured on  the specified  channel by  the
23814                named operator.
23815 
23816      Action:   No operator action is required.
23817 
23818 
23819                [mc_commands_.pl1]
23820                mc_commands_$mc_login:    Channel  XXXX   vchannel
23821                (YYYY) dialed to Initializer (NAME).
23822 
23823 
23824      Stream:   as (severity 1)
23825 
23826      Time:     In response to a message coordinator dial request.
23827 
23828      Meaning:  Informative  message indicating that  a successful
23829                dialin  occured on  the specified  channel by  the
23830                named operator.   A subsequent accept  is required
23831                by  an  authenticated  operator  to  complete  the
23832                attachment.
23833 
23834      Action:   No operator action is required.
23835 
23836 
23837                [mc_commands_.pl1]
23838                mc_commands_$mc_login:    error:    Channel   XXXX
23839                already in use.
23840 
23841 
23842      Stream:   sc (error_output)
23843 
23844      Time:     In response to an operator command.
23845 
23846      Meaning:  The  channel  specified   for  MNA  attachment  is
23847                already in use by the message coordinator.
23848 
23849      Action:   Enter a corrected command line.
23850 
23851 
23852 mc_tty_                        412            08/03/23     MR12.7^L
23853 
23854 
23855 
23856 
23857                [mc_tty_.pl1]
23858                mc_tty_:  called with bad pointer
23859 
23860 
23861      Stream:   BOS typewriter.
23862 
23863      Time:     While system is running.
23864 
23865      Meaning:  This message indicates a bug in system_control_ or
23866                in the Message Coordinator.  An illegal signal has
23867                been received by the  attached terminal handler in
23868                system_control_;  the  data  pointer  that  should
23869                point to an entry in  the mc_anstbl does not point
23870                to the correct segment.  The signal is ignored.
23871 
23872      Action:   Contact the system programming staff.
23873 
23874 
23875                [mc_tty_.pl1]
23876                mc_tty_:  called with null ptr
23877 
23878 
23879      Stream:   BOS typewriter.
23880 
23881      Time:     While system is running.
23882 
23883      Meaning:  This message indicates a bug in system_control_ or
23884                in the Message Coordinator.  An illegal signal has
23885                been received by the  attached terminal handler in
23886                system_control_.  The signal is ignored.
23887 
23888      Action:   Contact the system programming staff.
23889 
23890 
23891                [mc_tty_.pl1]
23892                mc_tty_:  channel CHAN hung up.
23893 
23894 
23895      Stream:   BOS Typewriter (sounds beeper)
23896 
23897      Time:     While system is running.
23898 
23899      Meaning:  This  message indicates  that an  attempt has been
23900                made to read input  from a terminal device channel
23901                attached to  the Message Coordinator and  that the
23902                channel is not active.   This condition may be due
23903                to a transient line condition, a terminal failure,
23904                or  a  communications  line  failure.   The system
23905                attempts to proceed.
23906 
23907 
23908 
23909 
23910 mc_tty_                        413            08/03/23     MR12.7^L
23911 
23912 
23913      Action:   If the  terminal is a hardwired device  and can be
23914                reconnected, do  so.  If this is  a dialup channel
23915                that has failed, use  the substty or drop commands
23916                to remove the channel.
23917 
23918 
23919 
23920                [mc_tty_.pl1]
23921                mc_tty_:  channel CHAN masked by FNP.
23922 
23923 
23924      Stream:   BOS Typewriter (sounds beeper)
23925 
23926      Time:     While system is running.
23927 
23928      Meaning:  The  channel, CHAN,  has just  been masked  by the
23929                FNP.  This is usually due to some hardware problem
23930                with the channel.
23931 
23932      Action:   Fix the problem before re-using the channel.
23933 
23934 
23935                [mc_tty_.pl1]
23936                mc_tty_:   Channel   CHANNEL  (vchannel  VCHANNEL)
23937                received TIMEOUT while awaiting DIALUP wakeup.
23938 
23939 
23940      Stream:   BOS Typewriter.
23941 
23942      Time:     While system is running.
23943 
23944      Meaning:  Wakeup was not acted on soon enough by AS.
23945 
23946      Action:   Contact the system programming staff.
23947 
23948 
23949                [mc_tty_.pl1]
23950                mc_tty_:   Channel   CHANNEL  (vchannel  VCHANNEL)
23951                received WAKEUP_TYPE wakeup while awaiting DIALUP.
23952 
23953 
23954      Stream:   BOS Typewriter.
23955 
23956      Time:     While system is running.
23957 
23958      Meaning:  Received  an unexpected  WAKEUP_TYPE wakeup  while
23959                waiting  for  a  DIALUP  wakeup.   Dialup will not
23960                succeed.
23961 
23962      Action:   Contact the system programming staff.
23963 
23964 
23965                [mc_tty_.pl1]
23966 
23967 
23968 mc_tty_                        414            08/03/23     MR12.7^L
23969 
23970 
23971                mc_tty_:   Channel CHANNEL received  TIMEOUT while
23972                awaiting DIALUP wakeup.
23973 
23974 
23975      Stream:   BOS Typewriter.
23976 
23977      Time:     While system is running.
23978 
23979      Meaning:  Wakeup was not acted on soon enough by AS.
23980 
23981      Action:   Contact the system programming staff.
23982 
23983 
23984                [mc_tty_.pl1]
23985                mc_tty_:   Channel  CHANNEL  received  WAKEUP_TYPE
23986                wakeup while awaiting DIALUP.
23987 
23988 
23989      Stream:   BOS Typewriter.
23990 
23991      Time:     While system is running.
23992 
23993      Meaning:  Did not  receive a DIALUP wakeup  WAKEUP_TYPE when
23994                should have.  Recieved an unexpected WAKEUP_TYPE.
23995 
23996      Action:   Contact the system programming staff.
23997 
23998 
23999                [mc_tty_.pl1]
24000                mc_tty_:    ERROR_TABLE_MESSAGE    Connecting   to
24001                CHANNEL (vchannel VCHANNEL).
24002 
24003 
24004      Stream:   BOS Typewriter.
24005 
24006      Time:     While system is running.
24007 
24008      Meaning:  Error creating an IOCB while attempting to connect
24009                channel  CHANNEL as message  coordinator terminal.
24010                Channel cannot be accepted as MC terminal.  Cannot
24011                attach and open I/O switches.
24012 
24013      Action:   Contact the system programming staff.
24014 
24015 
24016                [mc_tty_.pl1]
24017                mc_tty_:    ERROR_TABLE_MESSAGE    Connecting   to
24018                CHANNEL.
24019 
24020 
24021      Stream:   BOS Typewriter.
24022 
24023      Time:     While system is running.
24024 
24025 
24026 mc_tty_                        415            08/03/23     MR12.7^L
24027 
24028 
24029      Meaning:  Error creating an IOCB while attempting to connect
24030                channel  CHANNEL as message  coordinator terminal.
24031                Channel cannot be accepted as MC terminal.  Cannot
24032                attach and open I/O switches.
24033 
24034      Action:   Contact the system programming staff.
24035 
24036 
24037                [mc_tty_.pl1]
24038                mc_tty_:    ERROR_TABLE_MESSAGE   Could   not  get
24039                channel CHAN back from MC.
24040 
24041 
24042      Stream:   BOS Typewriter.
24043 
24044      Time:     While system is running.
24045 
24046      Meaning:  An  error, described  by ERROR_TABLE_MESSAGE,  was
24047                returned  from  astty_$tty_event  while  trying to
24048                give channel CHAN back to the AS after a hangup.
24049 
24050      Action:   Contact the system programming staff.
24051 
24052 
24053                [mc_tty_.pl1]
24054                mc_tty_:   ERROR_TABLE_MESSAGE  Could  not  notify
24055                answering service of new login channel CHAN.
24056 
24057 
24058 
24059      Stream:   BOS Typewriter.
24060 
24061      Time:     While system is running.
24062 
24063      Meaning:  An  error, described  by ERROR_TABLE_MESSAGE,  was
24064                returned from  hcs_$wakeup while trying  to notify
24065                the AS  about the new login channel  CHAN, after a
24066                hangup.
24067 
24068      Action:   Contact the system programming staff.
24069 
24070 
24071                [mc_tty_.pl1]
24072                mc_tty_:   ERROR_TABLE_MESSAGE  Could  not  remove
24073                CHAN from MC use.
24074 
24075 
24076      Stream:   BOS Typewriter.
24077 
24078      Time:     While system is running.
24079 
24080      Meaning:  An  error, described  by ERROR_TABLE_MESSAGE,  was
24081                returned from  mc_commands_$remove_tty while tring
24082 
24083 
24084 mc_tty_                        416            08/03/23     MR12.7^L
24085 
24086 
24087                to  remove channel  CHAN from  MC service  after a
24088                hangup.
24089 
24090      Action:   Contact the system programming staff.
24091 
24092 
24093                [mc_tty_.pl1]
24094                mc_tty_:    ERROR_TABLE_MESSAGE   Failed   to  set
24095                terminal type for CHAN.
24096 
24097 
24098      Stream:   BOS Typewriter.
24099 
24100      Time:     While system is running.
24101 
24102      Meaning:  An  error  described  ty  ERROR_TABLE_MESSAGE  was
24103                returned while trying to  set the terminal type on
24104                channel CHAN.
24105 
24106      Action:   Depending on the error, it  may be ignored, or the
24107                channel may be hungup.   If the channel is hungup,
24108                an attempt should be made  to fix the error before
24109                connecting the terminal again.
24110 
24111 
24112 
24113                [mc_tty_.pl1]
24114                mc_tty_:  ERROR_TABLE_MESSAGE wru failed for CHAN.
24115 
24116 
24117      Stream:   BOS Typewriter.
24118 
24119      Time:     While system is running.
24120 
24121      Meaning:  The  CDT  entry  for   channel  CHAN  requires  an
24122                answerback, but an error was returned while trying
24123                to  read it.  The  returned error is  described by
24124                ERROR_TABLE_MESSAGE.
24125 
24126      Action:   Verify that the channel is configured correctly in
24127                the CDT.
24128 
24129 
24130                [mc_tty_.pl1]
24131                mc_tty_:  Event  sent from incorrect  ring.  event
24132                channel = N, event message  = M, event sender = S,
24133                device signal = D ring = R, event data ptr = P
24134 
24135 
24136 
24137      Stream:   BOS Typewriter.
24138 
24139      Time:     While system is running.
24140 
24141 
24142 mc_tty_                        417            08/03/23     MR12.7^L
24143 
24144 
24145      Meaning:  An  event was  sent from  a ring  higher than  the
24146                specified MNA ring 2.
24147 
24148      Action:   Contact the system programming staff.
24149 
24150 
24151                [mc_tty_.pl1]
24152                mc_tty_:   Invalid argument.   Invalid DSA  wakeup
24153                event type TYPE.
24154 
24155 
24156      Stream:   as (severity 0)
24157 
24158      Time:     While system is running.
24159 
24160      Meaning:  A DSA wakeup event type TYPE was received which is
24161                out of the range of known event types.  The wakeup
24162                was ignored.
24163 
24164      Action:   No operator action is required.
24165 
24166 
24167                [mc_tty_.pl1]
24168                mc_tty_:   Invalid argument.   Invalid MCS  wakeup
24169                event type TYPE.
24170 
24171 
24172      Stream:   as (severity 0)
24173 
24174      Time:     While system is running.
24175 
24176      Meaning:  An MCS  wakeup event type TYPE  was received which
24177                is  out of  the range  of known  event types.  The
24178                wakeup was ignored.
24179 
24180      Action:   No operator action is required.
24181 
24182 
24183                [mc_tty_.pl1]
24184                mc_tty_:  Invalid argument.  Unexpected DSA wakeup
24185                event type TYPE.
24186 
24187 
24188      Stream:   as (severity 0)
24189 
24190      Time:     While system is running.
24191 
24192      Meaning:  A  known DSA wakeup  event type TYPE  was received
24193                but  was not  expected for  a message  coordinator
24194                terminal.  The wakeup was ignored.
24195 
24196      Action:   No operator action is required.
24197 
24198 
24199 
24200 mc_tty_                        418            08/03/23     MR12.7^L
24201 
24202 
24203 
24204 
24205                [mc_tty_.pl1]
24206                mc_tty_:  Invalid argument.  Unexpected MCS wakeup
24207                event type TYPE.
24208 
24209 
24210      Stream:   as (severity 0)
24211 
24212      Time:     While system is running.
24213 
24214      Meaning:  A  known MCS wakeup  event type TYPE  was received
24215                but  was not  expected for  a message  coordinator
24216                terminal.  The wakeup was ignored.
24217 
24218 
24219 
24220                [mc_tty_.pl1]
24221                mc_tty_:   Invalid  argument.   Unexpected network
24222                type TYPE in event message.
24223 
24224 
24225      Stream:   as (severity 0)
24226 
24227      Time:     While system is running.
24228 
24229      Meaning:  An unknown  network ident in wakeup  event message
24230                was received.  The wakeup was ignored.
24231 
24232      Action:   No operator action is required.
24233 
24234 
24235                [mc_tty_.pl1]
24236                mc_tty_:  Line CHAN hung up.
24237 
24238 
24239      Stream:   as (severity 0)
24240 
24241      Time:     While system is running.
24242 
24243      Meaning:  Channel  CHAN  has  been  hungup  during  a system
24244                shutdown.
24245 
24246      Action:   No operator action is required.
24247 
24248 
24249                [mc_tty_.pl1]
24250                mc_tty_:   No default  ttp for  CHANNEL line  LINE
24251                baud BAUD.
24252 
24253 
24254      Stream:   BOS Typewriter (sounds beeper)
24255 
24256 
24257 
24258 mc_tty_                        419            08/03/23     MR12.7^L
24259 
24260 
24261      Time:     While system is running.
24262 
24263      Meaning:  Could not  get default terminal type  for terminal
24264                on CHANNEL which has a  line type of LINE.  Hangup
24265                will follow.
24266 
24267      Action:   Contact the system programming staff.
24268 
24269 
24270                [mc_tty_.pl1]
24271                mc_tty_:  sc_stat_$mc_ansp is null
24272 
24273 
24274      Stream:   BOS Typewriter.
24275 
24276      Time:     While system is running.
24277 
24278      Meaning:  This message indicates a bug in system_control_ or
24279                in  the Message  Coordinator.  A  signal has  been
24280                received  by  the  attached  terminal  handler  in
24281                system_control_ but  the signal cannot  be handled
24282                because  the  mc_anstbl  cannot  be  located.  The
24283                signal is ignored.
24284 
24285      Action:   Contact the system programming staff.
24286 
24287 
24288                [mca_attach_.pl1]
24289                MCA:  IO not released  on DEVICE (ipcNN in IMU-X),
24290                PERSON.PROJ.T.
24291 
24292 
24293      Stream:   $warn
24294 
24295      Time:     While system is running.
24296 
24297      Meaning:  The user  is detaching the IPC, but  does not want
24298                the IO to be resumed.
24299 
24300      Action:   This is  normally because the IPC  is defective or
24301                no longer capable of handling normal I/O.
24302 
24303 
24304 
24305                [mca_attach_.pl1]
24306                MCA:   IO  released  on  DEVICE  (ipcNN in IMU-X),
24307                PERSON.PROJ.T.
24308 
24309 
24310      Stream:   Logged in SYSERR log.
24311 
24312      Time:     While system is running.
24313 
24314 
24315 
24316 MCA                            420            08/03/23     MR12.7^L
24317 
24318 
24319      Meaning:  This  message is stating  that the normal  flow of
24320                I/O for this device is being resumed.
24321 
24322      Action:   No operator action is required.
24323 
24324 
24325                [mca_attach_.pl1]
24326                MCA:  IO suspended on  DEVICE (ipcNN in IMU-X) for
24327                PERSON.PROJ.T.
24328 
24329 
24330      Stream:   Logged in SYSERR log.
24331 
24332      Time:     While system is running.
24333 
24334      Meaning:  This  message is stating  that the normal  flow of
24335                I/O  for  this  device  is  being suspended.  This
24336                allows  the user  to stop  or alter/reload  an IPC
24337                without affecting the system.
24338 
24339      Action:   No operator action is required.
24340 
24341 
24342                [mcs_timer.pl1]
24343                mcs_timer:  Cannot get space  to set timer NNN for
24344                devx(subchan) DDD(SSS).
24345 
24346 
24347      Stream:   Logged in SYSERR log.
24348 
24349      Time:     While system is running.
24350 
24351      Meaning:  An attempt was  made to set an MCS  timer with the
24352                specified  timer ID,  but it  was not  possible to
24353                allocate  the necessary  space in  tty_buf to hold
24354                timer data block.  The call is ignored.
24355 
24356      Action:   Contact the system programming staff.
24357 
24358 
24359                [mcs_timer.pl1]
24360                mcs_timer:   Channel not  locked by  this process.
24361                Devx = DDDD.
24362 
24363 
24364      Stream:   BOS Typewriter (Crashes system)
24365 
24366      Time:     While system is running.
24367 
24368      Meaning:  A   process  called   to  perform   an  MCS  timer
24369                operation,  but  the  channel  it  specified (devx
24370                DDDD) was  not locked by the  calling process.  by
24371                the calling process.
24372 
24373 
24374 mcs_timer                      421            08/03/23     MR12.7^L
24375 
24376 
24377      Action:   Contact the system programming staff.
24378 
24379 
24380                [mcs_timer.pl1]
24381                mcs_timer:  Duplicate timer  ID.  Cannot set timer
24382                NNN for devx(subchan) DDD(SSS).
24383 
24384 
24385      Stream:   Logged in SYSERR log.
24386 
24387      Time:     While system is running.
24388 
24389      Meaning:  An attempt was  made to set an MCS  timer with the
24390                specified timer ID, but the channel already had an
24391                outstanding timer  or queued timer  interrupt with
24392                that ID.  The call is ignored.
24393 
24394      Action:   Contact the system programming staff.
24395 
24396 
24397                [mcs_timer.pl1]
24398                mcs_timer:   Timer  lock  already  locked  to this
24399                process.
24400 
24401 
24402      Stream:   BOS Typewriter (Crashes system)
24403 
24404      Time:     While system is running.
24405 
24406      Meaning:  A process that had the MCS timer lock locked tried
24407                to lock it again.
24408 
24409      Action:   Contact the system programming staff.
24410 
24411 
24412                [mcs_timer.pl1]
24413                mcs_timer:  Timer lock not locked by this process.
24414 
24415 
24416      Stream:   BOS Typewriter (Crashes system)
24417 
24418      Time:     While system is running.
24419 
24420      Meaning:  A process called to unlock the MCS timer lock, but
24421                did not have it locked.
24422 
24423      Action:   Contact the system programming staff.
24424 
24425 
24426                [mcs_timer.pl1]
24427                mcs_timer:  Timer  not found.  Cannot  OOOOO timer
24428                NNN for devx(subchan) DDD(SSS).
24429 
24430 
24431 
24432 mcs_timer                      422            08/03/23     MR12.7^L
24433 
24434 
24435      Stream:   Logged in SYSERR log.
24436 
24437      Time:     While system is running.
24438 
24439      Meaning:  An  attempt was  made to  perform operation  OOOOO
24440                (reset or change) on an MCS timer when no timer or
24441                queued timer interrupt with the specified ID could
24442                be found for the  requesting channel.  The call is
24443                ignored.
24444 
24445      Action:   Contact the system programming staff.
24446 
24447 
24448                [mdc_create_.pl1]
24449                mdc_create_$delete:  No MDCS for DIRNAME.
24450 
24451 
24452      Stream:   Logged in SYSERR log.
24453 
24454      Time:     While system is running.
24455 
24456      Meaning:  When deleting master directory DIRNAME, the master
24457                directory control segment  (MDCS) could not found.
24458                The directory was deleted anyway.
24459 
24460      Action:   No operator action is required.
24461 
24462 
24463                [mdc_create_.pl1]
24464                mdc_create_$delete:   TRP  for  DIRNAME  on LVNAME
24465                negative.
24466 
24467 
24468      Stream:   Logged in SYSERR log.
24469 
24470      Time:     While system is running.
24471 
24472      Meaning:  While   deleting  master  directory   DIRNAME,  an
24473                invalid  negative time-record  product was  found.
24474                The  invalid number  has been  ignored, but volume
24475                accounting data may have been lost.
24476 
24477      Action:   No operator action is required.
24478 
24479 
24480                [mdc_lock_.pl1]
24481                mdc_lock_$lock:  LOCK ERROR MESSAGE.
24482 
24483 
24484      Stream:   Logged in SYSERR log.
24485 
24486      Time:     While system is running.
24487 
24488 
24489 
24490 mdc_lock_$lock                 423            08/03/23     MR12.7^L
24491 
24492 
24493      Meaning:  A master  directory operation failed because  of a
24494                problem with the master directory control lock.
24495 
24496      Action:   No operator action is required.
24497 
24498 
24499                [mdc_lock_.pl1]
24500                mdc_lock_$mdc_data_init:     Unable   to    create
24501                PATHNAME.  REASON.
24502 
24503 
24504      Stream:   BOS Typewriter.
24505 
24506      Time:     System Intialization.
24507 
24508      Meaning:  Master directory control was  unable to create the
24509                segment  PATHNAME,  to  be  used  for  the  master
24510                directory  control  lock,  for  the  REASON given.
24511                Subsequent master directory control operations may
24512                fail.
24513 
24514      Action:   ignore
24515 
24516 
24517                [mdc_lock_.pl1]
24518                mdc_lock_$mdc_data_init:   Unable   to  reclassify
24519                PATHNAME.  REASON.
24520 
24521 
24522      Stream:   BOS Typewriter.
24523 
24524      Time:     System Intialization.
24525 
24526      Meaning:  Master directory control  was unable to reclassify
24527                the  segment PATHNAME  to its  proper access class
24528                for the REASON given.  This  segment is to be used
24529                for the master directory control lock.  Subsequent
24530                master directory control operations may fail.
24531 
24532 
24533 
24534                [mdc_lock_.pl1]
24535                mdc_lock_$mdc_data_init:    Unable   to   truncate
24536                PATHNAME.  REASON.
24537 
24538 
24539      Stream:   BOS Typewriter.
24540 
24541      Time:     System Intialization.
24542 
24543      Meaning:  Master  directory control  was unable  to truncate
24544                the segment  PATHNAME for the REASON  given.  This
24545                segment  is to  be used  for the  master directory
24546 
24547 
24548 mdc_lock_$mdc_data_init        424            08/03/23     MR12.7^L
24549 
24550 
24551                control lock.  Subsequent master directory control
24552                operations may fail.
24553 
24554      Action:   No operator action is required.
24555 
24556 
24557                [mdc_lock_.pl1]
24558                mdc_lock_$unlock:  LOCK ERROR MESSAGE.
24559 
24560 
24561      Stream:   Logged in SYSERR log.
24562 
24563      Time:     While system is running.
24564 
24565      Meaning:  At  the completion  of a  master directory control
24566                operation, some error occured unlocking the master
24567                directory control lock.
24568 
24569      Action:   No operator action is required.
24570 
24571 
24572                [mdc_lock_.pl1]
24573                mdc_lock_:  Unable to initiate PATHNAME.  REASON.
24574 
24575 
24576      Stream:   Logged in SYSERR log.
24577 
24578      Time:     While system is running.
24579 
24580      Meaning:  Master  directory control  was unable  to initiate
24581                PATHNAME,  which  contains  the  master  directory
24582                control  lock,  because  of  REASON.   The  master
24583                directory  control  operation  requested  was  not
24584                performed.
24585 
24586      Action:   No operator action is required.
24587 
24588 
24589                [mdc_repair_.pl1]
24590                mdc_repair_$register_mdir:  DIRNAME  registered on
24591                LVNAME, quota=N.
24592 
24593 
24594      Stream:   Logged in SYSERR log.
24595 
24596      Time:     While system is running.
24597 
24598      Meaning:  The master directory DIRNAME  has been found which
24599                had  not  been  recorded  in  the  MDCS for volume
24600                LVNAME.  The master  directory has been registered
24601                and  the  quota  of  N  has  been  charged  to the
24602                Initializer.SysDaemon quota account.  This problem
24603                may  have been caused  by the loss  and subsequent
24604 
24605 
24606 mdc_repair_$register_mdir      425            08/03/23     MR12.7^L
24607 
24608 
24609                retreival of the master directory control segment,
24610                or by retreving a  master directory.  This message
24611                can  only appear  as a  result of  a register_mdir
24612                command performed by a system administrator.
24613 
24614      Action:   No operator action is required.
24615 
24616 
24617                [mdc_repair_.pl1]
24618                mdc_repair_$register_mdir:   Quota for  DIRNAME on
24619                LVNAME changed from OLD to NEW.
24620 
24621 
24622      Stream:   Logged in SYSERR log.
24623 
24624      Time:     While system is running.
24625 
24626      Meaning:  The quota of master directory DIRNAME was found be
24627                different  from the  quota recorded  in the  MDCS.
24628                The real  quota is assumed  to be correct  and the
24629                MDCS is  updated to reflect this  quota.  This may
24630                happen if  a set_quota command had been  used on a
24631                master directory.  This message can only appear as
24632                a result of a register_mdir command performed by a
24633                system administrator.
24634 
24635      Action:   No operator action is required.
24636 
24637 
24638                [mdc_repair_.pl1]
24639                mdc_repair_$register_mdir:  Quota of N reported by
24640                ring 0 for DIRNAME on LVNAME.  1 assumed.
24641 
24642 
24643      Stream:   Logged in SYSERR log.
24644 
24645      Time:     While system is running.
24646 
24647      Meaning:  The master directory DIRNAME for volume LVNAME has
24648                been  found to have  an invalid quota.   The quota
24649                has been  assumed to be  1.  The message  can only
24650                appear  as  a  result  of  a register_mdir command
24651                performed by a system administrator.
24652 
24653      Action:   No operator action is required.
24654 
24655 
24656                [mdc_repair_.pl1]
24657                mdc_repair_:validate_uidpaths:   Master  directory
24658                entry  with  bad   uidpath  deleted  from  LVNAME.
24659                PARTIAL-PATHNAME.
24660 
24661 
24662 
24663 
24664 mdc_repair_                    426            08/03/23     MR12.7^L
24665 
24666 
24667      Stream:   Logged in SYSERR log.
24668 
24669      Time:     While system is running.
24670 
24671      Meaning:  The  master directory  control segment  for LVNAME
24672                contains an  entry for a mastr  directory which no
24673                longer exists.  The entry has been deleted and the
24674                quota is returned to the account from which it was
24675                drawn.   This  can  happen  if  a master directory
24676                control segment has been lost and retreived, or if
24677                a mastr directory has been lost.
24678 
24679      Action:   No operator action is required.
24680 
24681 
24682                [mos_memory_check.pl1]
24683                mos_memory_check:  EDAC error on mem X store Y.
24684 
24685 
24686      Stream:   $warn
24687 
24688      Time:     While system is running.
24689 
24690      Meaning:  MOS memory polling has  found that the maintenance
24691                register in the system  controller shows a nonzero
24692                syndrome.  The data is logged  for use by HEALS or
24693                mos_edac_summary.   Only the  first occurrence  of
24694                this error is printed online for each box.
24695 
24696      Action:   No operator action is required.
24697 
24698 
24699                [mos_memory_check.pl1]
24700                mos_memory_check:  Lock error.
24701 
24702 
24703      Stream:   BOS Typewriter.
24704 
24705      Time:     While system is running.
24706 
24707      Meaning:  After checking the  memory controllers for errors,
24708                the program  mos_memory check attempted  to unlock
24709                the  reconfiguration lock  and found  it unlocked.
24710                The system continues to run.
24711 
24712      Action:   No operator action is required.
24713 
24714 
24715                [mos_memory_check.pl1]
24716                mos_memory_check:  MOS polling disabled
24717 
24718 
24719      Stream:   Logged in SYSERR log.
24720 
24721 
24722 mos_memory_check               427            08/03/23     MR12.7^L
24723 
24724 
24725      Time:     While system is running.
24726 
24727      Meaning:  A  system administrator   has disabled  MOS memory
24728                polling.
24729 
24730      Action:   No operator action is required.
24731 
24732 
24733                [mos_memory_check.pl1]
24734                mos_memory_check:  MOS polling time NN minutes.
24735 
24736 
24737      Stream:   Logged in SYSERR log.
24738 
24739      Time:     While system is running.
24740 
24741      Meaning:  A  system  administrator  has  set  the MOS memory
24742                polling time to NN minutes.
24743 
24744      Action:   No operator action is required.
24745 
24746 
24747                [disk_table_.pl1]
24748                mount of LVNAME stopped
24749 
24750 
24751      Stream:   Initializer process output.
24752 
24753      Time:     While system is running.
24754 
24755      Meaning:  The  operator issued  a dlv  LVNAME command  for a
24756                volume which was being mounted.
24757 
24758      Action:   No operator action is required.
24759 
24760 
24761                [disk_table_.pl1]
24762                mount pack PVNAME {on DRIVE}
24763 
24764 
24765      Stream:   Initializer process output.
24766 
24767      Time:     While system is running.
24768 
24769      Meaning:  This message occurs when  the system is attempting
24770                to mount  a logical volume  and finds one  or more
24771                physical volumes have not  been made known via the
24772                add_vol command.  If the pack is a non-demountable
24773                volume, a DRIVE will only be printed if the system
24774                knows the  drive on which the  pack was previously
24775                mounted.   If the  pack is  a demountable  volume,
24776                then  a  DRIVE  will  be  printed  always.  If the
24777                system does  not know the drive on  which the pack
24778 
24779 
24780 mount                          428            08/03/23     MR12.7^L
24781 
24782 
24783                was  last mounted, then  it chooses a  drive where
24784                the  pack  should  be   mounted  and  prints  this
24785                message.
24786 
24787      Action:   Mount the pack specified.  If it is not convenient
24788                to use the specified DRIVE, use another.  Then use
24789                the  add_vol command to  tell the system  that the
24790                physical volume has been  mounted.  When all packs
24791                have been mounted and  either accepted via add_vol
24792                or are  on the drives where the  system called for
24793                them, issue a "alv  LVNAME" command to accept them
24794                all at  once.  The logical  volume will be  put in
24795                use.
24796 
24797 
24798 
24799                [move_non_perm_wired_segs.pl1]
24800                move_non_perm_wired_segs:   mem TAG  on in  config
24801                deck, but port off.
24802 
24803 
24804      Stream:   BOS Typewriter (Crashes system)
24805 
24806      Time:     System Intialization.
24807 
24808      Meaning:  Memory controller  TAG is specified ON  on its MEM
24809                card,  but its  port is  disabled on  the bootload
24810                CPU.
24811 
24812      Action:   Enable the port or set the MEM OFF and reboot.
24813 
24814 
24815                [move_non_perm_wired_segs.pl1]
24816                move_non_perm_wired_segs:   mem  TAG  size  nK  in
24817                config, mK on port.
24818 
24819 
24820      Stream:   BOS Typewriter (Crashes system)
24821 
24822      Time:     System Intialization.
24823 
24824      Meaning:  Memory  controller TAG  has a  size of  nK in  the
24825                config deck,  but the address assignment  and port
24826                size switches specify mK.
24827 
24828      Action:   Fix the switches or config deck and reboot.
24829 
24830 
24831                [move_non_perm_wired_segs.pl1]
24832                move_non_perm_wired_segs:     no    main    memory
24833                configured.
24834 
24835 
24836 
24837 
24838 move_non_perm_wired_segs       429            08/03/23     MR12.7^L
24839 
24840 
24841      Stream:   BOS Typewriter (Crashes system)
24842 
24843      Time:     System Intialization.
24844 
24845      Meaning:  No MEM cards were found ON in the config deck.
24846 
24847      Action:   Fix the config deck and reboot.
24848 
24849 
24850                [mrd_util_.pl1]
24851                mrd_util_$ENTRY:  CALL_CODE (MESSAGE) in ENAME
24852 
24853 
24854      Stream:   BOS Typewriter (sounds beeper)
24855 
24856      Time:     While system is running.
24857 
24858      Meaning:  A problem has been  discovered in the threading of
24859                the message coordinator  segment ENAME.  CALL_CODE
24860                identifies  the particular  call that  failed, and
24861                MESSAGE  identifies the   reason for  the failure.
24862                Entry identifies the  entrypoint in mrd_util_ that
24863                was  called.  All  pending messages  in ENAME  are
24864                discarded.  Debugging information  is written into
24865                ENAME,   and   may    be   displayed   using   the
24866                dump_syscon_mseg  tool.   The  message coordinator
24867                recovers from these errors and continues, possibly
24868                with the  loss of some input or  output.  If ENAME
24869                is mc.message, some daemon output may be lost.  If
24870                ENAME is anything else,  some input to that daemon
24871                may be  lost, and the operator  should communicate
24872                with  the  daemon  immediately,  in  case this has
24873                happened.   This indicates  a logic  error in  the
24874                supervisor, or CPU or memory hardware problems.
24875 
24876      Action:   Contact  the system  programming staff.   Save all
24877                console and message coordinator terminal output.
24878 
24879 
24880 
24881                [mrd_util_.pl1]
24882                mrd_util_$ENTRY:  had to blast lock in ENAME
24883 
24884 
24885      Stream:   BOS Typewriter (sounds beeper)
24886 
24887      Time:     While system is running.
24888 
24889      Meaning:  The lock in the  message coordinator segment ENAME
24890                did not unlock within thirty seconds.  The lock is
24891                reset forcibly, and locked to the calling process.
24892                ENTRY identifies the  entrypoint in mrd_util_ that
24893                was called.  Debugging information is written into
24894 
24895 
24896 mrd_util_$ENTRY                430            08/03/23     MR12.7^L
24897 
24898 
24899                ENAME,   and   may    be   displayed   using   the
24900                dump_syscon_mseg tool.  Further  errors may result
24901                if the process that  originally locked the segment
24902                left it  in an inconsistent state, or  if it later
24903                starts up again.
24904 
24905      Action:   Contact  the system  programming staff.   Save all
24906                console and message coordinator terminal output.
24907 
24908 
24909 
24910                [mrd_util_.pl1]
24911                mrd_util_$ENTRY:  inconsistent threads in ENAME
24912 
24913 
24914      Stream:   BOS Typewriter (sounds beeper)
24915 
24916      Time:     While system is running.
24917 
24918      Meaning:  While  trying to  add  unused  blocks to  the free
24919                chain in the message coordinator segment ENAME, an
24920                error   was  discovered.   ENTRY   identifies  the
24921                entrypoint   in   mrd_util_   that   was   called.
24922                Debugging information  is written into  ENAME, and
24923                may be displayed  using the dump_syscon_mseg tool.
24924                This indicates a logic error in the supervisor, or
24925                CPU or memory hardware problems.
24926 
24927      Action:   Contact  the system  programming staff.   Save all
24928                console and message coordinator terminal output.
24929 
24930 
24931 
24932                [mrd_util_.pl1]
24933                mrd_util_$ENTRY:   killing process  due to  mylock
24934                error in ENAME
24935 
24936 
24937      Stream:   BOS Typewriter (Terminates user process)
24938 
24939      Time:     While system is running.
24940 
24941      Meaning:  While  trying  to  lock  the  message  coordinator
24942                segment  ENAME, the lock  was found to  already be
24943                locked to  the calling process.   ENTRY identifies
24944                the  entrypoint  in  mrd_util_  that  was  called.
24945                Debugging information  is written into  ENAME, and
24946                may be displayed  using the dump_syscon_mseg tool.
24947                This indicates a logic error in the supervisor, or
24948                CPU or memory hardware problems.
24949 
24950      Action:   Contact  the system  programming staff.   Save all
24951                console and message coordinator terminal output.
24952 
24953 
24954 mrd_util_$ENTRY                431            08/03/23     MR12.7^L
24955 
24956 
24957 
24958 
24959                [mrd_util_.pl1]
24960                mrd_util_$ENTRY:  reset bad lock in ENAME
24961 
24962 
24963      Stream:   BOS Typewriter (sounds beeper)
24964 
24965      Time:     While system is running.
24966 
24967      Meaning:  The message  coordinator segment ENAME  was locked
24968                to a  nonexistent process.  The lock  is reset and
24969                locked to  the calling process.   ENTRY identifies
24970                the  entrypoint  in  mrd_util_  that  was  called.
24971                Debugging information  is written into  ENAME, and
24972                may be displayed  using the dump_syscon_mseg tool.
24973                Further errors may be reported  if ENAME was in an
24974                inconsistent state.
24975 
24976      Action:   Contact  the system  programming staff.   Save all
24977                console and message coordinator terminal output.
24978 
24979 
24980 
24981                [mseg_index_.pl1]
24982                mseg_$initiate_seg:    The   ACL   for   PATH   is
24983                inconsistent -- USER_ID does not have "rw" access.
24984 
24985 
24986 
24987      Stream:   Logged in SYSERR log.
24988 
24989      Time:     While system is running.
24990 
24991      Meaning:  This indicates a logic error in the supervisor, or
24992                CPU  or  memory  hardware  problems.   For  proper
24993                operation of  the message segment  primitives, all
24994                ACL  terms of  a message  segment or  mailbox must
24995                specify "rw" access to the segment when running in
24996                ring  1.  One  or more  ACL terms  for the segment
24997                PATH do not provide  the required access.  USER_ID
24998                identifies  one of  the user  whose access  to the
24999                segment is incorrect.
25000 
25001      Action:   Contact the system programming staff.
25002 
25003 
25004                [mseg_utils_.pl1]
25005                mseg_$OPERATION:   Beginning salvage  of PATH  for
25006                USER_ID.  REASON
25007 
25008 
25009      Stream:   Logged in SYSERR log.
25010 
25011 
25012 mseg_$OPERATION                432            08/03/23     MR12.7^L
25013 
25014 
25015      Time:     While system is running.
25016 
25017      Meaning:  The message segment primitives operation OPERATION
25018                detected an internal  inconsistency in the message
25019                segment or mailbox PATH and has requested that the
25020                segment   be   salvaged.    REASON   provides   an
25021                explanation  of  why  the  operation  invoked  the
25022                salvager.
25023 
25024      Action:   No operator action is required.
25025 
25026 
25027                [mseg_utils_.pl1]
25028                mseg_$OPERATION:   Completed salvage  of PATH  for
25029                USER_ID.    N  {out    of  M   possible}  messages
25030                recovered.
25031 
25032 
25033 
25034      Stream:   Logged in SYSERR log.
25035 
25036      Time:     While system is running.
25037 
25038      Meaning:  The salvage of the message segment or mailbox PATH
25039                requested   by  the  message   segment  primitives
25040                operation OPERATION has been  completed.  Of the M
25041                messages  which might  have been  in the  segment,
25042                only  N could be  recovered; the others  have been
25043                deleted.  If all possible messages were recovered,
25044                the "out of M possible" phrase is omitted from the
25045                message.
25046 
25047      Action:   Contact  the  system   programming  staff._sa  The
25048                administrator may wish to  notify the owner of the
25049                segment that some of his messages have been lost.
25050 
25051 
25052 
25053                [mseg_utils_.pl1]
25054                mseg_$OPERATION:   Unable  to   salvage  PATH  for
25055                USER_ID.  REASON
25056 
25057 
25058      Stream:   Logged in SYSERR log.
25059 
25060      Time:     While system is running.
25061 
25062      Meaning:  This indicates a logic error in the supervisor, or
25063                CPU   or  memory  hardware   problems.   OPERATION
25064                identifies   the    message   segment   primitives
25065                operation  which provoked  the attempted  salvage.
25066                PATH  is the  pathname of  the message  segment or
25067                mailbox  which  could  not  be  salvaged.   REASON
25068 
25069 
25070 mseg_$OPERATION                433            08/03/23     MR12.7^L
25071 
25072 
25073                provides additional information  about the failure
25074                of the attempted salvage.
25075 
25076      Action:   Contact the system programming staff.
25077 
25078 
25079                [mseg_utils_.pl1]
25080                mseg_$OPERATION:   Unable  to   salvage  PATH  for
25081                USER_ID.  Rebuilding  the contents of  the message
25082                segment -- Record quota overflow.
25083 
25084 
25085 
25086      Stream:   Logged in SYSERR log.
25087 
25088      Time:     While system is running.
25089 
25090      Meaning:  The salvage of the message segment or mailbox PATH
25091                requested   by  the  message   segment  primitives
25092                operation OPERATION failed due to a lack of quota.
25093                The segment  in question will  remain inaccessible
25094                until the salvage can be successfully completed.
25095 
25096      Action:   Contact the system  programming staff._sa In order
25097                to make the message  segment or mailbox accessible
25098                again, the  administrator must increase  the quota
25099                available to the segment to any value greater than
25100                the   current   length   of   the   segment.   The
25101                administrator  should  then  attempt  to  use  the
25102                segment  to  allow  the  salvager  to  be  run  to
25103                completion.
25104 
25105 
25106 
25107                [mseg_utils_.pl1]
25108                mseg_$OPERATION:  Unable to  salvage PTR (pathname
25109                unknown)      for      USER_ID.       Call      to
25110                hcs_$get_access_info_seg failed.  REASON
25111 
25112 
25113 
25114      Stream:   Logged in SYSERR log.
25115 
25116      Time:     While system is running.
25117 
25118      Meaning:  This indicates a logic error in the supervisor, or
25119                CPU   or  memory  hardware   problems.   OPERATION
25120                identifies   the    message   segment   primitives
25121                operation  which provoked  the attempted  salvage.
25122                PTR is USER_ID's pointer to the message segment or
25123                mailbox  which  could  not  be  salvaged.   REASON
25124                provides additional information  about the failure
25125                of the call to hcs_$get_access_info_seg.
25126 
25127 
25128 mseg_$OPERATION                434            08/03/23     MR12.7^L
25129 
25130 
25131      Action:   Contact the system programming staff.
25132 
25133 
25134                [mseg_utils_.pl1]
25135                mseg_$OPERATION:   Unable  to  upgrade  PATH  from
25136                version N to version 5 for USER_ID.  REASON
25137 
25138 
25139 
25140      Stream:   Logged in SYSERR log.
25141 
25142      Time:     While system is running.
25143 
25144      Meaning:  This indicates a logic error in the supervisor, or
25145                CPU   or  memory  hardware   problems.   OPERATION
25146                identifies   the    message   segment   primitives
25147                operation  which  required  that  the  segment  be
25148                upgraded.   PATH is  the pathname  of the  message
25149                segment  or mailbox  which could  not be upgraded.
25150                REASON  provides additional information  about the
25151                failure of the attempted upgrade.
25152 
25153      Action:   Contact the system programming staff.
25154 
25155 
25156                [mseg_utils_.pl1]
25157                mseg_$OPERATION:  Unable to  upgrade PTR (pathname
25158                unknown) from version N  to version 5 for USER_ID.
25159                Call to hcs_$get_access_info_seg failed.  REASON
25160 
25161 
25162 
25163      Stream:   Logged in SYSERR log.
25164 
25165      Time:     While system is running.
25166 
25167      Meaning:  This indicates a logic error in the supervisor, or
25168                CPU   or  memory  hardware   problems.   OPERATION
25169                identifies   the    message   segment   primitives
25170                operation  which  required  that  the  segment  be
25171                upgraded.  PTR is USER_ID's pointer to the message
25172                segment  or mailbox  which could  not be upgraded.
25173                REASON  provides additional information  about the
25174                failure of the call to hcs_$get_access_info_seg.
25175 
25176      Action:   Contact the system programming staff.
25177 
25178 
25179                [mseg_utils_.pl1]
25180                mseg_$OPERATION:  Upgraded PATH  from version N to
25181                version 5 for USER_ID.  M messages were deleted.
25182 
25183 
25184 
25185 
25186 mseg_$OPERATION                435            08/03/23     MR12.7^L
25187 
25188 
25189      Stream:   Logged in SYSERR log.
25190 
25191      Time:     While system is running.
25192 
25193      Meaning:  The format of the  message segment or mailbox PATH
25194                was upgraded from the old format known as "version
25195                N" to  the latest format.  However,  M messages in
25196                the segment  could not be upgraded  to the current
25197                format because  there was no room for  them in the
25198                segment.   As a  consequence, these  messages were
25199                deleted.  OPERATION identifies the message segment
25200                primitives  operation  which   required  that  the
25201                segment be upgraded.
25202 
25203      Action:   Contact  the  system   programming  staff._sa  The
25204                administrator may wish to  notify the owner of the
25205                segment that some of his messages have been lost.
25206 
25207 
25208 
25209                [syserr_real.pl1]
25210                Multics   not  in   operation;  control   process:
25211                PERSON.PROJ.
25212 
25213 
25214      Stream:   BOS Typewriter (Crashes system)
25215 
25216      Time:     While system is running.
25217 
25218      Meaning:  This message is always  preceded by an explanation
25219                of the error which crashed the system.
25220 
25221      Action:   Follow normal recovery procedures.
25222 
25223 
25224                [system_startup_.pl1]
25225                Multics SYSID:  DATE TIME
25226 
25227 
25228      Stream:   BOS Typewriter.
25229 
25230      Time:     System Intialization.
25231 
25232      Meaning:  This is the first message  that will be typed when
25233                the system  is started up.  It  indicates that the
25234                Initializer process is ready to go.  The system ID
25235                on the tape is SYSID.
25236 
25237      Action:   Check  the  date  and  time  to  ensure  both  are
25238                correct.  If the clock reading is wrong, shut down
25239                and correct the clock.
25240 
25241 
25242 
25243 
25244 multiplexer_mgr_$CMD           436            08/03/23     MR12.7^L
25245 
25246 
25247 
25248 
25249                [multiplexer_mgr_.pl1]
25250                multiplexer_mgr_$CMD:  CDT rethreading failed.
25251 
25252 
25253      Stream:   as (severity2)
25254 
25255      Time:     While system is running.
25256 
25257      Meaning:  An attempt to repair  damage to the CDT discovered
25258                while  executing CMD  (and reported  in a previous
25259                message) has failed.
25260 
25261      Action:   Contact the system programming staff.
25262 
25263 
25264                [multiplexer_mgr_.pl1]
25265                multiplexer_mgr_$CMD:   Command used too  early in
25266                answering service initialization.  MPX
25267 
25268 
25269 
25270      Stream:   as (severity1)
25271 
25272      Time:     While system is running.
25273 
25274      Meaning:  An operator  command (identified by CMD)  has been
25275                entered for  the multiplexer named MPX  before the
25276                answering service has been initialized.
25277 
25278      Action:   No operator  action is required.  The  command may
25279                have  to  be   entered  manually  after  answering
25280                service initialization is complete.
25281 
25282 
25283 
25284                [multiplexer_mgr_.pl1]
25285                multiplexer_mgr_$CMD:   Error   while  rethreading
25286                CDT.
25287 
25288 
25289      Stream:   as (severity1)
25290 
25291      Time:     While system is running.
25292 
25293      Meaning:  An  error  (reported  by  a  previous message) was
25294                encountered   while   attempting   to   repair  an
25295                inconsistency   in   the   CDT   discovered  while
25296                executing CMD.
25297 
25298      Action:   Contact the system programming staff.
25299 
25300 
25301 
25302 multiplexer_mgr_$CMD           437            08/03/23     MR12.7^L
25303 
25304 
25305 
25306 
25307                [multiplexer_mgr_.pl1]
25308                multiplexer_mgr_$CMD:     ERROR.     cdt_mgr_$init
25309                failed.
25310 
25311 
25312      Stream:   as (severity1)
25313 
25314      Time:     While system is running.
25315 
25316      Meaning:  An error (desribed by  ERROR) occurred when trying
25317                to initialize the CDT in preparation for executing
25318                CMD.
25319 
25320      Action:   Contact the system programming staff.
25321 
25322 
25323                [multiplexer_mgr_.pl1]
25324                multiplexer_mgr_$CMD:     ERROR.    cdt_mgr_$init:
25325                INFO
25326 
25327 
25328      Stream:   as (severity0)
25329 
25330      Time:     While system is running.
25331 
25332      Meaning:  An  error  (described  by  ERROR,  with additional
25333                information in INFO) occurred  while trying to get
25334                a  pointer to  the CDT   in order  to execute  the
25335                command named CMD.
25336 
25337      Action:   Contact the system programming staff.
25338 
25339 
25340                [multiplexer_mgr_.pl1]
25341                multiplexer_mgr_$CMD:    ERROR.   cdt_mgr_$thread:
25342                INFO
25343 
25344 
25345      Stream:   as (severity1)
25346 
25347      Time:     While system is running.
25348 
25349      Meaning:  An  error  (described  by  ERROR,  with additional
25350                information  in  INFO)  occurred  while  trying to
25351                repair   damage  to   the  CDT   discovered  while
25352                executing CMD.
25353 
25354      Action:   Contact the system programming staff.
25355 
25356 
25357                [multiplexer_mgr_.pl1]
25358 
25359 
25360 multiplexer_mgr_$CMD           438            08/03/23     MR12.7^L
25361 
25362 
25363                multiplexer_mgr_$CMD:    ERROR.   cdt_mgr_$thread:
25364                INFO
25365 
25366 
25367      Stream:   as (severity3)
25368 
25369      Time:     While system is running.
25370 
25371      Meaning:  An  error  (described  by  ERROR,  with additional
25372                information  in  INFO)  occurred  while  trying to
25373                repair   damage  to   the  CDT   discovered  while
25374                executing CMD;  the attempt at repair  will not be
25375                repeated.
25376 
25377      Action:   Contact the system programming staff.
25378 
25379 
25380                [multiplexer_mgr_.pl1]
25381                multiplexer_mgr_$CMD:  MPX(X1)  has daughter count
25382                N, but first daughter X2
25383 
25384 
25385 
25386      Stream:   as (severity1)
25387 
25388      Time:     While system is running.
25389 
25390      Meaning:  An  inconsistency has  been discovered  in the CDT
25391                while executing  CMD.  The multiplexer  named MPX,
25392                occupying  CDT entry  X1,  is  marked as  having N
25393                subchannels, but the first subchannel entry number
25394                is X2, where either N or X2, but not both, is 0.
25395 
25396      Action:   Contact the system programming staff.
25397 
25398 
25399                [multiplexer_mgr_.pl1]
25400                multiplexer_mgr_$CMD:   multiplexers  may  not  be
25401                manipulated before AS initialization.
25402 
25403 
25404 
25405      Stream:   as (severity1)
25406 
25407      Time:     While system is running.
25408 
25409      Meaning:  An  attempt was  made to  execute the  command CMD
25410                before the answering service was initialized.
25411 
25412      Action:   No  operator  action  is   required.   It  may  be
25413                necessary to  reenter the command  after answering
25414                service initialization is complete.
25415 
25416 
25417 
25418 multiplexer_mgr_$CMD           439            08/03/23     MR12.7^L
25419 
25420 
25421 
25422 
25423                [multiplexer_mgr_.pl1]
25424                multiplexer_mgr_$CMD:   N daughters found  for mux
25425                MPX(X1)[ at CHAN(X2]), but daughter count is M
25426 
25427 
25428 
25429      Stream:   as (severity1)
25430 
25431      Time:     While system is running.
25432 
25433      Meaning:  An  inconsistency  in  the  CDT  was  found  while
25434                executing  CMD.    The  CDT  indicates   that  the
25435                multiplexer named MPX,  occupying entry number X1,
25436                has M subchannels, but  N subchannels are threaded
25437                to  it.  If  N >  M, the  Nth subchannel  is CHAN,
25438                occupying entry number X2.
25439 
25440      Action:   Contact the system programming staff.
25441 
25442 
25443                [multiplexer_mgr_.pl1]
25444                multiplexer_mgr_$CMD:   Repeated   damage  to  CDT
25445                threads encountered.
25446 
25447 
25448      Stream:   as (severity1)
25449 
25450      Time:     While system is running.
25451 
25452      Meaning:  After an attempt to repair an inconsistency to the
25453                CDT  discovered while  executing CMD,  the CDT was
25454                still inconsistent.
25455 
25456      Action:   Contact the system programming staff.
25457 
25458 
25459                [multiplexer_mgr_.pl1]
25460                multiplexer_mgr_$CMD:  Rethreading CDT.
25461 
25462 
25463      Stream:   as (severity0)
25464 
25465      Time:     While system is running.
25466 
25467      Meaning:  In the process of  performing the action requested
25468                by  CMD,  the  CDT  was  found  to  be damaged (as
25469                indicated by a separate  message); an attempt will
25470                be made to repair the damage.
25471 
25472      Action:   No operator action is required.
25473 
25474 
25475 
25476 multiplexer_mgr_$CMD           440            08/03/23     MR12.7^L
25477 
25478 
25479 
25480 
25481                [multiplexer_mgr_.pl1]
25482                multiplexer_mgr_$CMD:  Rethreading complete.
25483 
25484 
25485      Stream:   as (severity1)
25486 
25487      Time:     While system is running.
25488 
25489      Meaning:  An  inconsistency  discovered  in  the  CDT  while
25490                executing CMD (and reported in a previous message)
25491                has been successfully repaired.
25492 
25493      Action:   No operator action is required.
25494 
25495 
25496                [multiplexer_mgr_.pl1]
25497                multiplexer_mgr_$CMD:     Rethreading    of    CDT
25498                complete.
25499 
25500 
25501      Stream:   as (severity0)
25502 
25503      Time:     While system is running.
25504 
25505      Meaning:  Damage  to the  CDT  discovered  in the  course of
25506                executing CMD, and reported in a previous message,
25507                has been successfully repaired.
25508 
25509      Action:   No operator action is required.
25510 
25511 
25512                [multiplexer_mgr_.pl1]
25513                multiplexer_mgr_$CMD:    Threading   inconsistency
25514                detected in CDT.  Rethreading.
25515 
25516 
25517 
25518      Stream:   as (severity1)
25519 
25520      Time:     While system is running.
25521 
25522      Meaning:  An inconsistency in the CDT has been discovered in
25523                the CDT  while executing CMD.  An  attempt will be
25524                made to repair the inconsistency.
25525 
25526      Action:   No operator action is required.
25527 
25528 
25529                [multiplexer_mgr_.pl1]
25530                multiplexer_mgr_$COMMAND:  Dumping MPX.  [force]
25531 
25532 
25533 
25534 multiplexer_mgr_$COMMAND       441            08/03/23     MR12.7^L
25535 
25536 
25537      Stream:   as (severity1)
25538 
25539      Time:     While system is running.
25540 
25541      Meaning:  If  tracing  is  on,  this  message  appears  when
25542                dumping  a  multiplexer  in  response  to either a
25543                dump_mpx or shutdown_mpx  command (as indicated by
25544                COMMAND).   The  string  "force"  appears  if  the
25545                -force control argument was specified.
25546 
25547      Action:   No operator action is required.
25548 
25549 
25550                [multiplexer_mgr_.pl1]
25551                multiplexer_mgr_$COMMAND:  User(s) of N channel(s)
25552                would be hung up.  MPX  not dumped.  Use -force if
25553                necessary.
25554 
25555 
25556 
25557      Stream:   as (severity1)
25558 
25559      Time:     While system is running.
25560 
25561      Meaning:  The multiplexer named MPX had logged-in users on N
25562                subchannels   when  a  dump_mpx   or  shutdown_mpx
25563                command (as indicated by  COMMAND) was given.  The
25564                multiplexer cannot  be dumped or shut  down unless
25565                the -force control argument is used.
25566 
25567      Action:   Retry   the  command   with  the   -force  control
25568                argument, or wait for the users to be disconnected
25569                or logged out.
25570 
25571 
25572 
25573                [multiplexer_mgr_.pl1]
25574                multiplexer_mgr_$init:         ERROR.         From
25575                hphcs_$lct_init
25576 
25577 
25578      Stream:   as (severity1)
25579 
25580      Time:     While system is running.
25581 
25582      Meaning:  An  error (described  by ERROR)  was returned from
25583                hphcs_$lct_init   while   trying   to   initialize
25584                multiplexer management.
25585 
25586      Action:   Contact the system programming staff.
25587 
25588 
25589                [multiplexer_mgr_.pl1]
25590 
25591 
25592 multiplexer_mgr_$init          442            08/03/23     MR12.7^L
25593 
25594 
25595                multiplexer_mgr_$init:  ERROR.   Unable to perform
25596                requested stop_mpx of MPX.
25597 
25598 
25599      Stream:   as (severity1)
25600 
25601      Time:     While system is running.
25602 
25603      Meaning:  An attempt to shut down the multiplexer named MPX,
25604                while   reinitializing   multiplexer   management,
25605                encountered an error (described by ERROR).
25606 
25607      Action:   Contact the system programming staff.
25608 
25609 
25610                [multiplexer_mgr_.pl1]
25611                multiplexer_mgr_$init:  Shutting  down initialized
25612                multiplexers prior to re-initialization.
25613 
25614 
25615 
25616      Stream:   as (severity1)
25617 
25618      Time:     While system is running.
25619 
25620      Meaning:  Multiplexer  management   is  being  reinitialized
25621                after  some multiplexers   had been  loaded.  Such
25622                multiplexers   will   be   shut   down   prior  to
25623                reinitialization.
25624 
25625      Action:   No operator action is required.
25626 
25627 
25628                [multiplexer_mgr_.pl1]
25629                multiplexer_mgr_$listen_mpx:    asu_$listen_chanel
25630                failed for MPX.CHAN.
25631 
25632 
25633      Stream:   as (severity1)
25634 
25635      Time:     While system is running.
25636 
25637      Meaning:  If  tracing  is  on,  this  message  appears if an
25638                attempt to listen to  the subchannel named CHAN of
25639                the multiplexer  named MPX returned a  status code
25640                of      error_table_$action_not_performed.      An
25641                additional  message  from  asu_$asu_listen  should
25642                appear giving more information about the failure.
25643 
25644      Action:   Contact the system programming staff.
25645 
25646 
25647                [multiplexer_mgr_.pl1]
25648 
25649 
25650 multiplexer_mgr_$listen_mpx    443            08/03/23     MR12.7^L
25651 
25652 
25653                multiplexer_mgr_$listen_mpx:                ERROR.
25654                asu_$attach_channel failed MPX.CHAN
25655 
25656 
25657      Stream:   as (severity1)
25658 
25659      Time:     While system is running.
25660 
25661      Meaning:  An error was  returned by asu_$attach_channel when
25662                attempting  to attach   the subchannel  CHAN while
25663                listening  to all  subchannels of  the multiplexer
25664                named MPX.   This message only appears  if tracing
25665                is on.
25666 
25667      Action:   Contact the system programming staff.
25668 
25669 
25670                [multiplexer_mgr_.pl1]
25671                multiplexer_mgr_$listen_mpx:     ERROR.    Channel
25672                MPX.CHAN listen failed.
25673 
25674 
25675      Stream:   as (severity1)
25676 
25677      Time:     While system is running.
25678 
25679      Meaning:  An attempt to listen to the subchannel CHAN of the
25680                multiplexer MPX encountered an error (described by
25681                ERROR).
25682 
25683      Action:   Contact the system programming staff.
25684 
25685 
25686                [multiplexer_mgr_.pl1]
25687                multiplexer_mgr_$listen_mpx:  Listening to MPX.
25688 
25689 
25690      Stream:   as (severity1)
25691 
25692      Time:     While system is running.
25693 
25694      Meaning:  If  tracing  is  on,  this  message  appears  when
25695                starting  to  listen  to  the  subchannels  of the
25696                multiplexer named MPX after it has been loaded and
25697                started.
25698 
25699      Action:   No operator action is required.
25700 
25701 
25702                [multiplexer_mgr_.pl1]
25703                multiplexer_mgr_$listen_mpx:  MPX  is not running.
25704                Unable to listen to channels.
25705 
25706 
25707 
25708 multiplexer_mgr_$listen_mpx    444            08/03/23     MR12.7^L
25709 
25710 
25711      Stream:   as (severity1)
25712 
25713      Time:     While system is running.
25714 
25715      Meaning:  An attempt  was made to listen  to the subchannels
25716                of the multiplexer named  MPX, but the multiplexer
25717                was  not   running.   This  might  occur   if  the
25718                multiplexer  crashed  very   shortly  after  being
25719                loaded.
25720 
25721      Action:   If  there   is  a  message  indicating   that  the
25722                multiplexer crashed shortly  after loading, try to
25723                reload   it.    Otherwise,   contact   the  system
25724                programming staff.
25725 
25726 
25727 
25728                [multiplexer_mgr_.pl1]
25729                multiplexer_mgr_$load_mpx:  ERROR.   Unable to get
25730                a devx for MPX
25731 
25732 
25733      Stream:   as (severity1)
25734 
25735      Time:     While system is running.
25736 
25737      Meaning:  An  error  code  (described  by  ERROR)  has  been
25738                returned from an attempt  to find the device index
25739                ("devx") of the multiplexer named MPX.
25740 
25741      Action:   Contact the system programming staff.
25742 
25743 
25744                [multiplexer_mgr_.pl1]
25745                multiplexer_mgr_$load_mpx:    ERROR.   Unable   to
25746                initialize MPX.
25747 
25748 
25749      Stream:   as (severity1)
25750 
25751      Time:     While system is running.
25752 
25753      Meaning:  An  error  code  (described   by  ERROR)  hs  been
25754                returned  from   an  attempt  to   initialize  the
25755                multiplexer named MPX in ring 0.
25756 
25757      Action:   Contact the system programming staff.
25758 
25759 
25760                [multiplexer_mgr_.pl1]
25761                multiplexer_mgr_$load_mpx:  ERROR.  Unable to load
25762                MPX.
25763 
25764 
25765 
25766 multiplexer_mgr_$load_mpx      445            08/03/23     MR12.7^L
25767 
25768 
25769      Stream:   as (severity1)
25770 
25771      Time:     While system is running.
25772 
25773      Meaning:  An  error (described  by ERROR)  has prevented the
25774                loading of the multiplexer named MPX.
25775 
25776      Action:   Contact the system programming staff.
25777 
25778 
25779                [multiplexer_mgr_.pl1]
25780                multiplexer_mgr_$load_mpx:  Initialization  of MPX
25781                already in progress.
25782 
25783 
25784      Stream:   as (severity1)
25785 
25786      Time:     While system is running.
25787 
25788      Meaning:  An  attempt  to  load  the  multiplexer  named MPX
25789                failed  because a  previous  load  of MPX  has not
25790                completed.
25791 
25792      Action:   Either  allow the  load currently  in progress  to
25793                complete,  or use  the dump_mpx  command to  abort
25794                before retrying the load.
25795 
25796 
25797 
25798                [multiplexer_mgr_.pl1]
25799                multiplexer_mgr_$load_mpx:  Loading MPX.  ARGS
25800 
25801 
25802      Stream:   as (severity1)
25803 
25804      Time:     While system is running.
25805 
25806      Meaning:  A  load  of  the  multiplexer  named  MPX has been
25807                started.   ARGS,  if  present,  lists  the control
25808                arguments given  to the load_mpx  command (-check,
25809                -go, and/or -force).
25810 
25811      Action:   No operator action is required.
25812 
25813 
25814                [multiplexer_mgr_.pl1]
25815                multiplexer_mgr_$load_mpx:   MPX cannot  be loaded
25816                because its parent multiplexer is not running.
25817 
25818 
25819 
25820      Stream:   as (severity1)
25821 
25822 
25823 
25824 multiplexer_mgr_$load_mpx      446            08/03/23     MR12.7^L
25825 
25826 
25827      Time:     While system is running.
25828 
25829      Meaning:  An  attempt  to  load  the  multiplexer  named MPX
25830                failed  because  its  parent  multiplexer  was not
25831                running.
25832 
25833      Action:   Try to load the parent multiplexer before retrying
25834                the load of MPX.
25835 
25836 
25837 
25838                [multiplexer_mgr_.pl1]
25839                multiplexer_mgr_$load_mpx:      MPX     has     no
25840                subchannels.
25841 
25842 
25843      Stream:   as (severity1)
25844 
25845      Time:     While system is running.
25846 
25847      Meaning:  The multiplexer  named MPX cannot be  used because
25848                it has no subchannels specified in the CDT.
25849 
25850      Action:   Contact the system programming staff._sa
25851 
25852 
25853                [multiplexer_mgr_.pl1]
25854                multiplexer_mgr_$load_mpx:    MPX    not   loaded.
25855                Unable to determine the state of its parent.
25856 
25857 
25858 
25859      Stream:   as (severity1)
25860 
25861      Time:     While system is running.
25862 
25863      Meaning:  An  attempt  to  load  the  multiplexer  named MPX
25864                failed because the system  was unable to determine
25865                whether its parent multiplexer was loaded.
25866 
25867      Action:   Contact   the   system   programming   staff.   If
25868                possible, attempt to load the parent multiplexer.
25869 
25870 
25871 
25872                [multiplexer_mgr_.pl1]
25873                multiplexer_mgr_$load_mpx:   No  devx  assigned to
25874                MPX.CHAN.
25875 
25876 
25877      Stream:   as (severity1)
25878 
25879      Time:     While system is running.
25880 
25881 
25882 multiplexer_mgr_$load_mpx      447            08/03/23     MR12.7^L
25883 
25884 
25885      Meaning:  The  subchannel CHAN  of multiplexer  MPX was  not
25886                assigned  a  device  index  ("devx")  when MPX was
25887                initialized.
25888 
25889      Action:   Contact the system programming staff.
25890 
25891 
25892                [multiplexer_mgr_.pl1]
25893                multiplexer_mgr_$load_mpx:  Unable to init channel
25894                CHAN on MPX.
25895 
25896 
25897      Stream:   as (severity1)
25898 
25899      Time:     While system is running.
25900 
25901      Meaning:  The subchannel  CHAN of multiplexer MPX  could not
25902                be initialized.
25903 
25904      Action:   Contact the system programming staff.
25905 
25906 
25907                [multiplexer_mgr_.pl1]
25908                multiplexer_mgr_$load_mpx:     User(s)     of    N
25909                channel(s) would be hung up.  MPX not loaded.  Use
25910                -force if necessary.
25911 
25912 
25913 
25914      Stream:   as (severity1)
25915 
25916      Time:     While system is running.
25917 
25918      Meaning:  The multiplexer  named MPX has N  subchannels with
25919                users  logged in.   It can  only be  loaded if the
25920                -force  control   argument  is  provided   to  the
25921                load_mpx command.
25922 
25923      Action:   Either  reenter  the  load_mpx  command  with  the
25924                -force control argument, or  wait for the users to
25925                be disconnected or logged out.
25926 
25927 
25928 
25929                [multiplexer_mgr_.pl1]
25930                multiplexer_mgr_$mpx_crashed:  Automatic reloading
25931                is disabled.  MPX will not be reloaded.
25932 
25933 
25934 
25935      Stream:   as (severity1)
25936 
25937      Time:     While system is running.
25938 
25939 
25940 multiplexer_mgr_$mpx_crashed   448            08/03/23     MR12.7^L
25941 
25942 
25943      Meaning:  The multiplexer  named MPX, which has  crashed, is
25944                not being reloaded  because automatic reloading of
25945                multiplexers  has been   disabled (by  setting the
25946                FNP_required_up_time field in the CMF to 0).
25947 
25948      Action:   If it is desired  to reload the multiplexer, enter
25949                a load_mpx command.
25950 
25951 
25952 
25953                [multiplexer_mgr_.pl1]
25954                multiplexer_mgr_$mpx_crashed:  Crash  reported for
25955                MPX.
25956 
25957 
25958      Stream:   as (severity1)
25959 
25960      Time:     While system is running.
25961 
25962      Meaning:  If  tracing is on,  this message appears  when the
25963                answering service is notified that the multiplexer
25964                named MPX has crashed.
25965 
25966      Action:   No operator action is required.
25967 
25968 
25969                [multiplexer_mgr_.pl1]
25970                multiplexer_mgr_$mpx_crashed:    ERROR.   Shutting
25971                down MPX
25972 
25973 
25974      Stream:   as (severity1)
25975 
25976      Time:     While system is running.
25977 
25978      Meaning:  An  error  (described   by  ERROR)  occurred  when
25979                attempting to shut down  the multiplexer named MPX
25980                after it had crashed.
25981 
25982      Action:   Contact the system programming staff.
25983 
25984 
25985                [multiplexer_mgr_.pl1]
25986                multiplexer_mgr_$mpx_crashed:  MPX  is in apparent
25987                crash loop and will not be reloaded
25988 
25989 
25990 
25991      Stream:   as (severity1)
25992 
25993      Time:     While system is running.
25994 
25995 
25996 
25997 
25998 multiplexer_mgr_$mpx_crashed   449            08/03/23     MR12.7^L
25999 
26000 
26001      Meaning:  The  multiplexer named  MPX has  crashed more than
26002                twice    in    the     interval    specified    by
26003                FNP_required_up_time,    and     will    not    be
26004                automatically reloaded.
26005 
26006      Action:   Contact the system programming staff.
26007 
26008 
26009                [multiplexer_mgr_.pl1]
26010                multiplexer_mgr_$mpx_crashed:  MPX  is stopped and
26011                will not be reloaded.
26012 
26013 
26014      Stream:   as (severity1)
26015 
26016      Time:     While system is running.
26017 
26018      Meaning:  The multiplexer  named MPX has crashed  and is not
26019                being  reloaded  because  of  a  previous stop_mpx
26020                command.
26021 
26022      Action:   No operator action is required.
26023 
26024 
26025                [multiplexer_mgr_.pl1]
26026                multiplexer_mgr_$mpx_load_failed:   ERROR.  Trying
26027                to shutdown MPX.
26028 
26029 
26030      Stream:   as (severity1)
26031 
26032      Time:     While system is running.
26033 
26034      Meaning:  An  error  (described   by  ERROR)  occurred  when
26035                attempting to shut down  the multiplexer named MPX
26036                after it had failed to load.
26037 
26038      Action:   Contact the system programming staff.
26039 
26040 
26041                [multiplexer_mgr_.pl1]
26042                multiplexer_mgr_$mpx_load_failed:   Load   of  MPX
26043                failed.
26044 
26045 
26046      Stream:   as (severity1)
26047 
26048      Time:     While system is running.
26049 
26050      Meaning:  If  tracing is  on,  this  message appears  if the
26051                answering service  is notified that an  attempt to
26052                load the multiplexer named MPX failed.  A previous
26053 
26054 
26055 
26056 multiplexer_mgr_$mpx_load_failed^H450            08/03/23     MR12.7^L
26057 
26058 
26059                message  should give   more information  about the
26060                failure.
26061 
26062      Action:   No operator action is required.
26063 
26064 
26065                [multiplexer_mgr_.pl1]
26066                multiplexer_mgr_$mpx_load_failed:    Report   load
26067                failure for MPX while not loading.
26068 
26069 
26070 
26071      Stream:   as (severity1)
26072 
26073      Time:     While system is running.
26074 
26075      Meaning:  The answering service was notified that loading of
26076                the multiplexer named MPX  had failed, but no load
26077                of that multiplexer was in progress at the time.
26078 
26079      Action:   Contact the system programming staff.
26080 
26081 
26082                [multiplexer_mgr_.pl1]
26083                multiplexer_mgr_$shut:  ERROR.  Could not shutdown
26084                FNP X.
26085 
26086 
26087      Stream:   as (severity1)
26088 
26089      Time:     While system is running.
26090 
26091      Meaning:  An error (described by ERROR) occurred when trying
26092                to  shut  down  the  FNP  named  X  during  system
26093                shutdown  or after  an error  in answering service
26094                initialization.
26095 
26096      Action:   Contact the system programming staff.
26097 
26098 
26099                [multiplexer_mgr_.pl1]
26100                multiplexer_mgr_$shut:  ERROR.  Could not shutdown
26101                MPX.
26102 
26103 
26104      Stream:   as (severity1)
26105 
26106      Time:     While system is running.
26107 
26108      Meaning:  An error (described by ERROR) occurred when trying
26109                to  shut  down  the  multiplexer  named MPX during
26110                system  shutdown or  after an  error in  answering
26111                service initialization.
26112 
26113 
26114 multiplexer_mgr_$shut          451            08/03/23     MR12.7^L
26115 
26116 
26117      Action:   Contact the system programming staff.
26118 
26119 
26120                [multiplexer_mgr_.pl1]
26121                multiplexer_mgr_$shut:     Shutting    down    all
26122                multiplexers.
26123 
26124 
26125      Stream:   as (severity1)
26126 
26127      Time:     While system is running.
26128 
26129      Meaning:  If  tracing  is  on,  this  message  appears  when
26130                multiplexers are being shut down as part of system
26131                shutdown or  when an error was  encountered during
26132                answering service initialization.
26133 
26134      Action:   No operator action is required.
26135 
26136 
26137                [multiplexer_mgr_.pl1]
26138                multiplexer_mgr_$shutdown_mpx:   ERROR.   Shutting
26139                down MPX.
26140 
26141 
26142      Stream:   as (severity1)
26143 
26144      Time:     While system is running.
26145 
26146      Meaning:  An  error (described  by ERROR)  has occurred when
26147                attempting to shut down the multiplexer named MPX.
26148 
26149      Action:   Contact the system programming staff.
26150 
26151 
26152                [multiplexer_mgr_.pl1]
26153                multiplexer_mgr_$shutdown_mpx:              ERROR.
26154                Terminating MPX.
26155 
26156 
26157      Stream:   as (severity1)
26158 
26159      Time:     While system is running.
26160 
26161      Meaning:  An  error (described  by ERROR)  has occurred when
26162                attempting to terminate the multiplexer named MPX.
26163 
26164      Action:   Contact the system programming staff.
26165 
26166 
26167                [multiplexer_mgr_.pl1]
26168                multiplexer_mgr_$shutdown_mpx:              ERROR.
26169                Terminating MPX.CHAN.
26170 
26171 
26172 multiplexer_mgr_$shutdown_mpx  452            08/03/23     MR12.7^L
26173 
26174 
26175      Stream:   as (severity1)
26176 
26177      Time:     While system is running.
26178 
26179      Meaning:  An error  (described by ERROR) has  occurred while
26180                terminating the subchannel CHAN of the multiplexer
26181                named MPX.
26182 
26183      Action:   Contact the system programming staff.
26184 
26185 
26186                [multiplexer_mgr_.pl1]
26187                multiplexer_mgr_$shutdown_mpx:  ERROR.   Unable to
26188                dump MPX.
26189 
26190 
26191      Stream:   as (severity1)
26192 
26193      Time:     While system is running.
26194 
26195      Meaning:  An  error (described  by ERROR)  has occurred when
26196                attempting to dump the multiplexer named MPX.
26197 
26198      Action:   Contact the system programming staff.
26199 
26200 
26201                [multiplexer_mgr_.pl1]
26202                multiplexer_mgr_$shutdown_mpx:  Shutting down MPX.
26203                [dump]
26204 
26205 
26206      Stream:   as (severity1)
26207 
26208      Time:     While system is running.
26209 
26210      Meaning:  If  tracing is  on,  this  message appears  when a
26211                multiplexer  is  shut  down.   The  string  "dump"
26212                appears  at the  end of   the message  if the  the
26213                shutdown  is in  response to  a dump_mpx  command,
26214                rather than a shutdown_mpx command.
26215 
26216      Action:   No operator action is required.
26217 
26218 
26219                [multiplexer_mgr_.pl1]
26220                multiplexer_mgr_$start_mpx:   ERROR.    Can't  get
26221                devx for MPX.
26222 
26223 
26224      Stream:   as (severity1)
26225 
26226      Time:     While system is running.
26227 
26228 
26229 
26230 multiplexer_mgr_$start_mpx     453            08/03/23     MR12.7^L
26231 
26232 
26233      Meaning:  An error (described by ERROR) was returned from an
26234                attempt to  get the device index  ("devx") for the
26235                multiplexer named MPX.
26236 
26237      Action:   Contact the system programming staff.
26238 
26239 
26240                [multiplexer_mgr_.pl1]
26241                multiplexer_mgr_$start_mpx:  ERROR.  Starting MPX.
26242 
26243 
26244      Stream:   as (severity1)
26245 
26246      Time:     While system is running.
26247 
26248      Meaning:  An  error  (described   by  ERROR)  occurred  when
26249                attempting to start the multiplexer named MPX.
26250 
26251      Action:   Contact the system programming staff.
26252 
26253 
26254                [multiplexer_mgr_.pl1]
26255                multiplexer_mgr_$start_mpx:   MPX   has  not  been
26256                loaded, so it can't be started.
26257 
26258 
26259 
26260      Stream:   as (severity1)
26261 
26262      Time:     While system is running.
26263 
26264      Meaning:  A   start_mpx   command   was   entered   for  the
26265                multiplexer named MPX, but it has not been loaded.
26266 
26267      Action:   Load  the   multiplexer  by  using   the  load_mpx
26268                command.
26269 
26270 
26271                [multiplexer_mgr_.pl1]
26272                multiplexer_mgr_$start_mpx:    MPX    is   already
26273                started.
26274 
26275 
26276      Stream:   as (severity1)
26277 
26278      Time:     While system is running.
26279 
26280      Meaning:  A   start_mpx   command   was   entered   for  the
26281                multiplexer  named MPX,  but it  had already  been
26282                started.
26283 
26284      Action:   No operator action is required.
26285 
26286 
26287 
26288 multiplexer_mgr_$start_mpx     454            08/03/23     MR12.7^L
26289 
26290 
26291 
26292 
26293                [multiplexer_mgr_.pl1]
26294                multiplexer_mgr_$start_mpx:    MPX  is   currently
26295                loading.  It will be started when load completes.
26296 
26297 
26298 
26299      Stream:   as (severity1)
26300 
26301      Time:     While system is running.
26302 
26303      Meaning:  A   start_mpx   command   was   entered   for  the
26304                multiplexer named MPX while  loading of MPX was in
26305                progress.  The start_mpx  command will take effect
26306                after the load is completed.
26307 
26308      Action:   No operator action is required.
26309 
26310 
26311                [multiplexer_mgr_.pl1]
26312                multiplexer_mgr_$start_mpx:      Starting     MPX.
26313                [force]
26314 
26315 
26316      Stream:   as (severity1)
26317 
26318      Time:     While system is running.
26319 
26320      Meaning:  If  tracing is on,  this message appears  when the
26321                multiplexer   named   MPX   is   started,   either
26322                automatically after loading, or  in response to an
26323                explicit  start_mpx command.   The string  "force"
26324                appears  if   the  -force  control   argument  was
26325                specified.
26326 
26327      Action:   No operator action is required.
26328 
26329 
26330                [multiplexer_mgr_.pl1]
26331                multiplexer_mgr_$stop_mpx:  ERROR.  Can't get devx
26332                for MPX.
26333 
26334 
26335      Stream:   as (severity1)
26336 
26337      Time:     While system is running.
26338 
26339      Meaning:  An error (described by ERROR) was returned from an
26340                attempt to  get the device index  ("devx") for the
26341                multiplexer named MPX.
26342 
26343      Action:   Contact the system programming staff.
26344 
26345 
26346 multiplexer_mgr_$stop_mpx      455            08/03/23     MR12.7^L
26347 
26348 
26349 
26350 
26351                [multiplexer_mgr_.pl1]
26352                multiplexer_mgr_$stop_mpx:  ERROR.  Unable to stop
26353                MPX.
26354 
26355 
26356      Stream:   as (severity1)
26357 
26358      Time:     While system is running.
26359 
26360      Meaning:  An  error  (described   by  ERROR)  occurred  when
26361                attempting to stop the multiplexer named MPX.
26362 
26363      Action:   Contact the system programming staff.
26364 
26365 
26366                [multiplexer_mgr_.pl1]
26367                multiplexer_mgr_$stop_mpx:   MPX  is  now loading,
26368                but will not be started
26369 
26370 
26371      Stream:   as (severity1)
26372 
26373      Time:     While system is running.
26374 
26375      Meaning:  This message  acknowledges a stop_mpx  command for
26376                the  multiplexer  named  MPX,  which  is currently
26377                being loaded.
26378 
26379      Action:   No operator action is required.
26380 
26381 
26382                [multiplexer_mgr_.pl1]
26383                multiplexer_mgr_$stop_mpx:  MPX is  running but no
26384                longer accepting calls.
26385 
26386 
26387      Stream:   as (severity1)
26388 
26389      Time:     While system is running.
26390 
26391      Meaning:  This message acknowledges  that a stop_mpx command
26392                has  been  successfully  executed  on  the running
26393                multiplexer named MPX.
26394 
26395      Action:   No operator action is required.
26396 
26397 
26398                [multiplexer_mgr_.pl1]
26399                multiplexer_mgr_$stop_mpx:    MPX   will   not  be
26400                loaded.
26401 
26402 
26403 
26404 multiplexer_mgr_$stop_mpx      456            08/03/23     MR12.7^L
26405 
26406 
26407      Stream:   as (severity1)
26408 
26409      Time:     While system is running.
26410 
26411      Meaning:  This message  acknowledges a stop_mpx  command for
26412                the multiplexer named MPX,  which is currently not
26413                loaded.
26414 
26415      Action:   No operator action is required.
26416 
26417 
26418                [multiplexer_mgr_.pl1]
26419                multiplexer_mgr_$stop_mpx:  Stopping MPX
26420 
26421 
26422      Stream:   as (severity1)
26423 
26424      Time:     While system is running.
26425 
26426      Meaning:  If tracing is on, this message appears in response
26427                to  a stop_mpx  command for  the multiplexer named
26428                MPX.
26429 
26430      Action:   No operator action is required.
26431 
26432 
26433                [multiplexer_mgr_.pl1]
26434                multiplexer_mgr_$validate_mpx_name:        Invalid
26435                multiplexer name:  MPX REASON
26436 
26437 
26438      Stream:   as (severity1)
26439 
26440      Time:     While system is running.
26441 
26442      Meaning:  The multiplexer  name MPX, which has  been used in
26443                an  operator command,  is invalid,  for the reason
26444                given by REASON.
26445 
26446      Action:   If  the name  was mistyped,  reenter the  command.
26447                Otherwise, contact the system administrator.
26448 
26449 
26450 
26451                [multiplexer_mgr_.pl1]
26452                multiplexer_mgr_mpx_loaded:     Successful    load
26453                reported for MPX.
26454 
26455 
26456      Stream:   as (severity1)
26457 
26458      Time:     While system is running.
26459 
26460 
26461 
26462 multiplexer_mgr_mpx_loaded     457            08/03/23     MR12.7^L
26463 
26464 
26465      Meaning:  If  tracing is on,  this message appears  when the
26466                answering service is notified that the multiplexer
26467                named MPX has been successfully loaded.
26468 
26469      Action:   No operator action is required.
26470 
26471 
26472                [disk_rebuild_caller.pl1]
26473                New starting parameters (no partitions defined):
26474 
26475 
26476      Stream:   Initializer process output.
26477 
26478      Time:     In response to an operator command.
26479 
26480      Meaning:  This  message  requests  the  input  of  new  disk
26481                parameters.
26482 
26483      Action:   Input  the  new  disk  parameters.   Use the "end"
26484                request when done.
26485 
26486 
26487                [syserr_real.pl1]
26488                Now terminating user process:  PERSON.PROJ.
26489 
26490 
26491      Stream:   BOS Typewriter.
26492 
26493      Time:     While system is running.
26494 
26495      Meaning:  This line is always  preceded by an explanation of
26496                the error  which required the terminaation  of the
26497                user process PERSON.PROJ.
26498 
26499      Action:   No operator action is required.
26500 
26501 
26502                [ocdcm_.pl1]
26503                ocdcm_ (bump_io_to_mc):  Console recovery failure.
26504 
26505 
26506      Stream:   BOS Typewriter (Crashes system)
26507 
26508      Time:     While system is running.
26509 
26510      Meaning:  The software detected  Message Coordinator failure
26511                while  the Message  Coordinator was  being used in
26512                place  of a  functioning console.   Since the CCRF
26513                parameter was specified the system crashed.
26514 
26515      Action:   Contact the system programming staff.  Contact the
26516                system programming staff._sa
26517 
26518 
26519 
26520 ocdcm_ (bump_io_to_mc)         458            08/03/23     MR12.7^L
26521 
26522 
26523 
26524 
26525                [ocdcm_.pl1]
26526                ocdcm_   (bump_io_to_mc):    Message   Coordinator
26527                failure.
26528 
26529 
26530      Stream:   Logged in SYSERR log.
26531 
26532      Time:     While system is running.
26533 
26534      Meaning:  The  Message  Coordinator  is  no  longer  able to
26535                handle console traffic.
26536 
26537      Action:   Attempt to get an active console online as soon as
26538                possible and reset the Message Coordinator.
26539 
26540 
26541 
26542                [ocdcm_.pl1]
26543                ocdcm_   (console_recovery):     Console   failed,
26544                assignment of alternate OPCx failed.
26545 
26546 
26547      Stream:   Logged in SYSERR log.
26548 
26549      Time:     While system is running.
26550 
26551      Meaning:  The  console software  detected a  failure of  the
26552                bootload  console   and  found  an   alternate  to
26553                utilize.   However, when  it tried  to attach  the
26554                alternate it too was found to be inoperative.  The
26555                search continues for a usable console.
26556 
26557      Action:   Attempt  to determine   why the  alternate console
26558                failed  to come  online.   If  it can  be repaired
26559                configure  it with the  set_system_console command
26560                from a highly priviliged process.
26561 
26562 
26563 
26564                [ocdcm_.pl1]
26565                ocdcm_  (console_recovery):  Console  inoperative,
26566                alternate OPCx assigned.
26567 
26568 
26569      Stream:   Logged in SYSERR log.
26570 
26571      Time:     While system is running.
26572 
26573      Meaning:  The  software  has  detected  a  bootload  console
26574                failure and has assigned the specifed alternate to
26575 
26576 
26577 
26578 ocdcm_ (console_recovery)      459            08/03/23     MR12.7^L
26579 
26580 
26581                take over.  The inoperative  console is flagged as
26582                such.
26583 
26584      Action:   Contact the system programming staff.
26585 
26586 
26587                [ocdcm_.pl1]
26588                ocdcm_  (console_recovery):  Console  inoperative,
26589                no alternates available.
26590 
26591 
26592      Stream:   Logged in SYSERR log.
26593 
26594      Time:     While system is running.
26595 
26596      Meaning:  The  software  dected   failure  of  the  bootload
26597                console,  but no   alternates are  configured.  It
26598                will  direct  subsequent  console  traffic  to the
26599                Message Coordinator.
26600 
26601      Action:   Attempt  to get a  running console online  via the
26602                set_system_console command as soon as possible.
26603 
26604 
26605 
26606                [ocdcm_.pl1]
26607                ocdcm_  (console_recovery):  Console  inoperative,
26608                no alternates, no MC.
26609 
26610 
26611      Stream:   Logged in SYSERR log.
26612 
26613      Time:     While system is running.
26614 
26615      Meaning:  The  software  detected  failure  of  the bootload
26616                console, but no alternates  are configured and the
26617                Message  Coordinator  is   not  functioning.   All
26618                subsequent  console traffic  will be  sent to  the
26619                syserr log.
26620 
26621      Action:   Attempt  to get a  running console online  via the
26622                set_system_console command as soon as possible.
26623 
26624 
26625 
26626                [ocdcm_.pl1]
26627                ocdcm_   (console_recovery):    Console   recovery
26628                failure.
26629 
26630 
26631      Stream:   BOS Typewriter (Crashes system)
26632 
26633      Time:     While system is running.
26634 
26635 
26636 ocdcm_ (console_recovery)      460            08/03/23     MR12.7^L
26637 
26638 
26639      Meaning:  The  software  detected  console  failure  and was
26640                unable to continue because  the CCRF parameter was
26641                specified.  The system crashed.
26642 
26643      Action:   Contact the system programming staff.  Contact the
26644                system programming staff._sa
26645 
26646 
26647 
26648                [ocdcm_.pl1]
26649                ocdcm_    (esd_reset):     No    active   consoles
26650                configured.
26651 
26652 
26653      Stream:   Logged in SYSERR log.
26654 
26655      Time:     While system is running.
26656 
26657      Meaning:  During ESD there were no consoles in service.  ESD
26658                messages will be sent to the syserr log.
26659 
26660      Action:   Contact the system programming staff.
26661 
26662 
26663                [ocdcm_.pl1]
26664                ocdcm_ (init_all_consoles):  Assigned console OPCx
26665                as TYPE device.
26666 
26667 
26668      Stream:   $announce
26669 
26670      Time:     System Intialization.
26671 
26672      Meaning:  This  message  appears  as  the  system configures
26673                consoles found  in the config file.   This message
26674                will  only appear if  the CLST parameter  has been
26675                specified on  the PARM card.  Values  for TYPE are
26676                "bootload", "alternate",  "I/O", "inoperative" and
26677                "off".
26678 
26679      Action:   No operator action is required.
26680 
26681 
26682                [ocdcm_.pl1]
26683                ocdcm_  (init_all_consoles):   Changing  state  of
26684                OPCx to alt.
26685 
26686 
26687      Stream:   BOS Typewriter (sounds beeper)
26688 
26689      Time:     System Intialization.
26690 
26691 
26692 
26693 
26694 ocdcm_ (init_all_consoles)     461            08/03/23     MR12.7^L
26695 
26696 
26697      Meaning:  During   console  initialization  more   than  one
26698                console was found to have  a state of "on".  Since
26699                only one bootload console  is allowed the software
26700                reconfigures    additional   "on"    consoles   as
26701                alternates.
26702 
26703      Action:   $config
26704 
26705 
26706                [ocdcm_.pl1]
26707                ocdcm_   (init_all_consoles):    Console   channel
26708                assignment failed.
26709 
26710 
26711      Stream:   BOS Typewriter (Crashes system)
26712 
26713      Time:     While system is running.
26714 
26715      Meaning:  Attachment  of  the   specified  bootload  console
26716                failed during initialization.
26717 
26718      Action:   This  is most  likely  a  hardware failure  of the
26719                console channel adapter.
26720 
26721 
26722 
26723                [ocdcm_.pl1]
26724                ocdcm_ (init_all_consoles):   Illegal console name
26725                (NAME) specified.  It will be ignored.
26726 
26727 
26728 
26729      Stream:   BOS Typewriter (sounds beeper)
26730 
26731      Time:     System Intialization.
26732 
26733      Meaning:  An illegal console name  was found.  Console names
26734                must be values of "opca" through "opcz".
26735 
26736      Action:   $config
26737 
26738 
26739                [ocdcm_.pl1]
26740                ocdcm_   (init_all_consoles):    Invalid   channel
26741                specified for OPCx.
26742 
26743 
26744      Stream:   BOS Typewriter (Crashes system)
26745 
26746      Time:     System Intialization.
26747 
26748      Meaning:  The  console channel  as specified  in the  config
26749                file for the specified device is illegal.
26750 
26751 
26752 ocdcm_ (init_all_consoles)     462            08/03/23     MR12.7^L
26753 
26754 
26755      Action:   $config
26756 
26757 
26758                [ocdcm_.pl1]
26759                ocdcm_  (init_all_consoles):    Invalid  state  of
26760                STATE      for      console      OPCx.      ocdcm_
26761                (init_all_consoles):   This  console  will  not be
26762                configured.
26763 
26764 
26765 
26766      Stream:   BOS Typewriter (sounds beeper)
26767 
26768      Time:     System Intialization.
26769 
26770      Meaning:  An   unrecognizable  state   was  found   for  the
26771                specified  console.   That  console  will  not  be
26772                configured.   Only valid  states are  "on", "alt",
26773                "io", "inop" and "off".
26774 
26775      Action:   $config
26776 
26777 
26778                [ocdcm_.pl1]
26779                ocdcm_ (init_all_consoles):  Maximum console count
26780                exceeded.  ocdcm_ (init_all_consoles):  Additional
26781                consoles will not be configured.
26782 
26783 
26784 
26785      Stream:   BOS Typewriter (sounds beeper)
26786 
26787      Time:     System Intialization.
26788 
26789      Meaning:  Too  many  consoles  have  been  specified  in the
26790                config  file.  Only  the maximum  number allowable
26791                will be configured.
26792 
26793      Action:   $config
26794 
26795 
26796                [ocdcm_.pl1]
26797                ocdcm_  (init_all_consoles):    Missing  prph  opc
26798                card.
26799 
26800 
26801      Stream:   BOS Typewriter (Crashes system)
26802 
26803      Time:     System Intialization.
26804 
26805      Meaning:  At least one PRPH OPCx  card must be in the config
26806                file.
26807 
26808 
26809 
26810 ocdcm_ (init_all_consoles)     463            08/03/23     MR12.7^L
26811 
26812 
26813      Action:   $config
26814 
26815 
26816                [ocdcm_.pl1]
26817                ocdcm_  (init_all_consoles):   No  active  console
26818                configured.
26819 
26820 
26821      Stream:   BOS Typewriter (Crashes system)
26822 
26823      Time:     System Intialization.
26824 
26825      Meaning:  None of the consoles  specified in the config file
26826                has a state of "on".
26827 
26828      Action:   $config
26829 
26830 
26831                [ocdcm_.pl1]
26832                ocdcm_  (init_all_consoles):  Unable  to determine
26833                absolute memory address of oc_data.
26834 
26835 
26836 
26837      Stream:   BOS Typewriter (Crashes system)
26838 
26839      Time:     While system is running.
26840 
26841      Meaning:  The absloute  memory address of oc_data  could not
26842                be determined during console initialization.
26843 
26844      Action:   This  is a very  serious error.  Ensure  that your
26845                MST is good and then consider hardware.
26846 
26847 
26848 
26849                [ocdcm_.pl1]
26850                ocdcm_ (init_all_consoles):   Unknown model, NNNN,
26851                specified for OPCx.  It will not be configured.
26852 
26853 
26854 
26855      Stream:   BOS Typewriter (sounds beeper)
26856 
26857      Time:     System Intialization.
26858 
26859      Meaning:  The console  model number specified in  the config
26860                file  is not supported  by this software  and will
26861                not be configured.
26862 
26863      Action:   $config
26864 
26865 
26866 
26867 
26868 ocdcm_ (interrupt_handler)     464            08/03/23     MR12.7^L
26869 
26870 
26871 
26872 
26873                [ocdcm_.pl1]
26874                ocdcm_ (interrupt_handler):  System Fault.
26875 
26876 
26877      Stream:   Logged in SYSERR log.
26878 
26879      Time:     While system is running.
26880 
26881      Meaning:  A  system fault  interrupt was  received from  the
26882                IOM.  The fault is logged and ignored.
26883 
26884      Action:   Contact the system programming staff.
26885 
26886 
26887                [ocdcm_.pl1]
26888                ocdcm_ (lock_oc_data):  Lock wait timer expired.
26889 
26890 
26891      Stream:   BOS Typewriter (Crashes system)
26892 
26893      Time:     While system is running.
26894 
26895      Meaning:  A process waiting on the  lock was not able to get
26896                the  lock  before  the  wait  timer expired.  This
26897                timer  is calculated as  the maximum time  that it
26898                should  take  a  READ  I/O  to  complete times the
26899                number of CPUs specified  in the config file.  Any
26900                process waiting  on the lock should  never have to
26901                wait more than that amount of time for the lock to
26902                become  available without   there being  a serious
26903                problem  with  the  hardcore  process  holding the
26904                lock.
26905 
26906      Action:   Contact the system programming staff.
26907 
26908 
26909                [ocdcm_.pl1]
26910                ocdcm_ (lock_oc_data):  Mylock error.
26911 
26912 
26913      Stream:   BOS Typewriter (Crashes system)
26914 
26915      Time:     While system is running.
26916 
26917      Meaning:  The offending process found  its own process_id in
26918                the lock.
26919 
26920      Action:   Contact the system programming staff.
26921 
26922 
26923                [ocdcm_.pl1]
26924 
26925 
26926 ocdcm_ (log_console_error)     465            08/03/23     MR12.7^L
26927 
26928 
26929                ocdcm_  (log_console_error):  I/O  [timeout] error
26930                on  OPCx; status  = SSSSSS  oc_data flags:   FLAGS
26931                oc_entry flags:  FLAGS console_io flags:  FLAGS
26932 
26933 
26934 
26935      Stream:   Logged in SYSERR log.
26936 
26937      Time:     While system is running.
26938 
26939      Meaning:  An I/O error occurred.  The status is the returned
26940                IOM status  for the I/O in question  and the flags
26941                denote the  state of the oc_data,  the console and
26942                the I/O,  respectively, at the time  of the error.
26943                The flag values are interpreted.
26944 
26945      Action:   Too  many  of  these  errors  will  result  in the
26946                invocation of console  recovery.  Have the console
26947                fixed.
26948 
26949 
26950 
26951                [ocdcm_.pl1]
26952                ocdcm_   (reconfigure):   Assigned   OPCx  as   an
26953                alternate console for PERSON.PROJ.T.
26954 
26955 
26956      Stream:   BOS Typewriter (sounds beeper)
26957 
26958      Time:     While system is running.
26959 
26960      Meaning:  The specified process has configured the specified
26961                console as an alternate.
26962 
26963      Action:   No operator action is required.
26964 
26965 
26966                [ocdcm_.pl1]
26967                ocdcm_   (reconfigure):   Assigned  OPCx   as  the
26968                bootload console for PERSON.PROJ.T.
26969 
26970 
26971      Stream:   BOS Typewriter (sounds beeper)
26972 
26973      Time:     While system is running.
26974 
26975      Meaning:  The specified process has configured the specified
26976                console  as the   bootload console.   The bootload
26977                console  at  the  time  of  the reconfiguration is
26978                reconfigured as an alternate device.
26979 
26980      Action:   No operator action is required.
26981 
26982 
26983 
26984 ocdcm_ (reconfigure)           466            08/03/23     MR12.7^L
26985 
26986 
26987 
26988 
26989                [ocdcm_.pl1]
26990                ocdcm_     (reconfigure):     Bootload     console
26991                deconfigured with CCRF set.
26992 
26993 
26994      Stream:   BOS Typewriter (Crashes system)
26995 
26996      Time:     During console reconfiguration.
26997 
26998      Meaning:  The  bootload console  was deconfigured  by use of
26999                the  set_system_console command  and the  site had
27000                specified the CCRF parameter in the config file.
27001 
27002      Action:   Follow normal recovery procedures.
27003 
27004 
27005                [ocdcm_.pl1]
27006                ocdcm_  (reconfigure):  Consigned  OPCx as  an I/O
27007                device for PERSON.PROJ.T.
27008 
27009 
27010      Stream:   BOS Typewriter (sounds beeper)
27011 
27012      Time:     While system is running.
27013 
27014      Meaning:  The specified process has configured the specified
27015                console as an I/O device.
27016 
27017      Action:   No operator action is required.
27018 
27019 
27020                [ocdcm_.pl1]
27021                ocdcm_   (reconfigure):    Marked   OPCx   as   an
27022                inoperative device for PERSON.PROJ.T.
27023 
27024 
27025      Stream:   BOS Typewriter (sounds beeper)
27026 
27027      Time:     While system is running.
27028 
27029      Meaning:  The specified process has configured the specified
27030                console as an inoperative device.
27031 
27032      Action:   No operator action is required.
27033 
27034 
27035                [ocdcm_.pl1]
27036                ocdcm_  (reconfigure):   MCA  input  through OPCx,
27037                disabled by PERSON.PROJ.T.
27038 
27039 
27040 
27041 
27042 ocdcm_ (reconfigure)           467            08/03/23     MR12.7^L
27043 
27044 
27045      Stream:   Logged in SYSERR log.
27046 
27047      Time:     While system is running.
27048 
27049      Meaning:  The input to the  MCA (Maint.  Channel Adapter) in
27050                the IMU (Interrupt  Multiplexer Unit) from special
27051                keyboard  sequences  has  been  LOCKed (disabled).
27052                Input  to  the  MCA  can  now  only  come from the
27053                on-line, Multics controlled, channel 03 interface.
27054 
27055      Action:   No operator action is required.
27056 
27057 
27058                [ocdcm_.pl1]
27059                ocdcm_ (reconfigure):  MCA(nn) input through OPCx,
27060                enabled by PERSON.PROJ.T.
27061 
27062 
27063      Stream:   Logged in SYSERR log.
27064 
27065      Time:     While system is running.
27066 
27067      Meaning:  The input to MCA(nn)  via special console keyboard
27068                sequences has been enabled (UNLOCKed).
27069 
27070      Action:   No operator action is required.
27071 
27072 
27073                [ocdcm_.pl1]
27074                ocdcm_ (reconfigure):  Timeout  executing MCA LOCK
27075                on OPCx for PERSON.PROJ.T.
27076 
27077 
27078      Stream:   Logged in SYSERR log.
27079 
27080      Time:     While system is running.
27081 
27082      Meaning:  The I/O to LOCK the MCA interface through OPCx did
27083                not complete within a given time.
27084 
27085      Action:   This  is most  likely  a  hardware failure  of the
27086                console channel adapter or the IMU central.
27087 
27088 
27089 
27090                [ocdcm_.pl1]
27091                ocdcm_  (reconfigure):  Timeout  executing MCA(nn)
27092                UNLOCK on OPCx for PERSON.PROJ.T.
27093 
27094 
27095      Stream:   Logged in SYSERR log.
27096 
27097      Time:     While system is running.
27098 
27099 
27100 ocdcm_ (reconfigure)           468            08/03/23     MR12.7^L
27101 
27102 
27103      Meaning:  The  I/O to  UNLOCK the  MCA(nn) interface through
27104                OPCx did not complete within a given time.
27105 
27106      Action:   This  is most  likely  a  hardware failure  of the
27107                console channel adapter or the IMU central.
27108 
27109 
27110 
27111                [ocdcm_.pl1]
27112                ocdcm_  (reset_console):   Reset  bootload console
27113                for PERSON.PROJ.T.
27114 
27115 
27116      Stream:   BOS Typewriter (sounds beeper)
27117 
27118      Time:     While system is running.
27119 
27120      Meaning:  The  bootload  console  has   been  reset  by  the
27121                specified process.
27122 
27123      Action:   No operator action is required.
27124 
27125 
27126                [ocdcm_.pl1]
27127                ocdcm_ (unlock_oc_data):  Lock not mine.
27128 
27129 
27130      Stream:   BOS Typewriter (Crashes system)
27131 
27132      Time:     While system is running.
27133 
27134      Meaning:  A  process attempting  to unlock  oc_data found  a
27135                non-zero lock that was not its own.
27136 
27137      Action:   Contact the system programming staff.
27138 
27139 
27140                [on_line_salvager.pl1]
27141                on_line_salvager:   cannot get activation  info on
27142                PPPPP ERRORMESSAGE
27143 
27144 
27145      Stream:   BOS Typewriter.
27146 
27147      Time:     While system is running.
27148 
27149      Meaning:  The  on  line  salvager  could  not  determine the
27150                length of a directory to be salvaged.  A truncated
27151                copy will be made in >dumps.
27152 
27153      Action:   Contact the system programming staff.
27154 
27155 
27156 
27157 
27158 on_line_salvager               469            08/03/23     MR12.7^L
27159 
27160 
27161                [on_line_salvager.pl1]
27162                on_line_salvager:    error  from   sum  on   PPPPP
27163                ERRORMESSAGE
27164 
27165 
27166      Stream:   BOS Typewriter (Crashes system)
27167 
27168      Time:     While system is running.
27169 
27170      Meaning:  The on  line salvager could not  access the branch
27171                for a sdirectory to be salvaged.  This indicates a
27172                logic  error in the  supervisor, or CPU  or memory
27173                hardware problems.
27174 
27175      Action:   Contact  the  system  programming  staff.   Follow
27176                normal recovery procedures.
27177 
27178 
27179 
27180                [on_line_salvager.pl1]
27181                on_line_salvager:  Getting pathname of PPPPP
27182 
27183 
27184      Stream:   BOS Typewriter (Crashes system)
27185 
27186      Time:     While system is running.
27187 
27188      Meaning:  The on line salvager cannot obtain the pathname of
27189                a  directory  to  be  salvaged.   This indicates a
27190                logic  error in the  supervisor, or CPU  or memory
27191                hardware problems.
27192 
27193      Action:   Take  a  dump.   Contact  the  system  programming
27194                staff.  Follow normal recovery procedures.
27195 
27196 
27197 
27198                [on_line_salvager.pl1]
27199                on_line_salvager:  lock error ERROMESSAGE
27200 
27201 
27202      Stream:   BOS Typewriter (Crashes system)
27203 
27204      Time:     While system is running.
27205 
27206      Meaning:  The on line salvager could not lock its data base.
27207                This indicates a logic error in the supervisor, or
27208                CPU or memory hardware problems.
27209 
27210      Action:   Contact  the  system  programming  staff.   Follow
27211                normal recovery  procedures.  Be sure that  a dump
27212                is taken.
27213 
27214 
27215 
27216 OPER                           470            08/03/23     MR12.7^L
27217 
27218 
27219 
27220 
27221                [mc_tty_.pl1]
27222                OPER:
27223 
27224 
27225      Stream:   Initializer terminal.
27226 
27227      Time:     While system is running.
27228 
27229      Meaning:  This  message is  typed if  the operator  enters a
27230                blank line on a  message coordinator terminal.  It
27231                indicates that input is  expected on the terminal,
27232                and that output will be inhibited for 30 seconds.
27233 
27234      Action:   Type a system control command.
27235 
27236 
27237                [operator_mc_cmds_.pl1]
27238                operator_mc_cmds_:    accept:    CHANNEL   set  to
27239                "full".
27240 
27241 
27242      Stream:   as (severity 1)
27243 
27244      Time:     In response to an operator accept command.
27245 
27246      Meaning:  CHANNEL  is  already   in  use  and  authorization
27247                request has not changed from it's current state.
27248 
27249      Action:   Enter a corrected command line.
27250 
27251 
27252                [operator_mc_cmds_.pl1]
27253                operator_mc_cmds_:  accept:  channel not available
27254 
27255 
27256      Stream:   as (severity 1)
27257 
27258      Time:     In response to an operator accept command.
27259 
27260      Meaning:  Channel  cannot be  used as  a message coordinator
27261                channel.
27262 
27263      Action:   Enter a corrected command line.
27264 
27265 
27266                [operator_mc_cmds_.pl1]
27267                operator_mc_cmds_:   accept:  channel  not defined
27268                in cdt.
27269 
27270 
27271      Stream:   as (severity 1)
27272 
27273 
27274 operator_mc_cmds_              471            08/03/23     MR12.7^L
27275 
27276 
27277      Time:     In response to an operator accept command.
27278 
27279      Meaning:  Channel  is  not  found  in  the  system  cdt  and
27280                therefore cannot be used.
27281 
27282      Action:   Enter a corrected command line.
27283 
27284 
27285                [operator_mc_cmds_.pl1]
27286                operator_mc_cmds_:    accept:    error:    unknown
27287                privilege code
27288 
27289 
27290      Stream:   as (severity 1)
27291 
27292      Time:     In response to an operator accept command.
27293 
27294      Meaning:  The  operator has  typed accept  CHANNEL PRIVILEGE
27295                but PRIVILEGE is not a known privilege code.
27296 
27297      Action:   Enter a corrected command line.
27298 
27299 
27300                [operator_mc_cmds_.pl1]
27301                operator_mc_cmds_:   accept:   ERROR_TABLE_MESSAGE
27302                accept unsuccessful.
27303 
27304 
27305      Stream:   as (severity 1)
27306 
27307      Time:     In response to an operator accept command.
27308 
27309      Meaning:  The  error was returned  from mc_commands_$new_tty
27310                causing the accept to abort.
27311 
27312      Action:   Enter a corrected command line.
27313 
27314 
27315                [operator_mc_cmds_.pl1]
27316                operator_mc_cmds_:   accept:   ERROR_TABLE_MESSAGE
27317                Channel  CHANNEL  is  not  in  Message Coordinator
27318                service.
27319 
27320 
27321 
27322      Stream:   as (severity 1)
27323 
27324      Time:     In response to an operator accept command.
27325 
27326      Meaning:  CHANNEL   cannot   be   accepted   as   a  message
27327                coordinator terminal.
27328 
27329      Action:   Enter a corrected command line.
27330 
27331 
27332 operator_mc_cmds_              472            08/03/23     MR12.7^L
27333 
27334 
27335 
27336 
27337                [operator_mc_cmds_.pl1]
27338                operator_mc_cmds_:   accept:   ERROR_TABLE_MESSAGE
27339                Failed to accept CHANNEL.
27340 
27341 
27342      Stream:   as (severity 1)
27343 
27344      Time:     In response to an operator accept command.
27345 
27346      Meaning:  The operator has issued an accept CHANNEL command,
27347                but CHANNEL cannot be accepted.
27348 
27349      Action:   Enter a corrected command line.
27350 
27351 
27352                [operator_mc_cmds_.pl1]
27353                operator_mc_cmds_:   accept:   ERROR_TABLE_MESSAGE
27354                Failed to reset restriction.
27355 
27356 
27357      Stream:   as (severity 1)
27358 
27359      Time:     In response to an operator accept command.
27360 
27361      Meaning:  Failed to reset the reply restriction.
27362 
27363      Action:   Enter a corrected command line.
27364 
27365 
27366                [operator_mc_cmds_.pl1]
27367                operator_mc_cmds_:   accept:   ERROR_TABLE_MESSAGE
27368                Failed to set broadcast list to BROADCAST_LIST.
27369 
27370 
27371      Stream:   as (severity 1)
27372 
27373      Time:     In response to an operator accept command.
27374 
27375      Meaning:  Failed to set the broadcast list BROADCAST_LIST.
27376 
27377      Action:   Enter a corrected command line.
27378 
27379 
27380                [operator_mc_cmds_.pl1]
27381                operator_mc_cmds_:   accept:   ERROR_TABLE_MESSAGE
27382                Failed to set restriction to RESTRICTION.
27383 
27384 
27385      Stream:   as (severity 1)
27386 
27387      Time:     In response to an operator accept command.
27388 
27389 
27390 operator_mc_cmds_              473            08/03/23     MR12.7^L
27391 
27392 
27393      Meaning:  Failed to set the reply restriction.
27394 
27395      Action:   Enter a corrected command line.
27396 
27397 
27398                [operator_mc_cmds_.pl1]
27399                operator_mc_cmds_:   accept:   ERROR_TABLE_MESSAGE
27400                This name is reserved for the system console.
27401 
27402 
27403      Stream:   as (severity 1)
27404 
27405      Time:     In response to an operator accept command.
27406 
27407      Meaning:  Attempt to  accept identifier "otw_" which  is THE
27408                identifier  for  the   master  console,  which  is
27409                automatically accepted on bootload.
27410 
27411      Action:   Enter a corrected command line.
27412 
27413 
27414                [operator_mc_cmds_.pl1]
27415                operator_mc_cmds_:   accept:   ERROR_TABLE_MESSAGE
27416                Usage:   accept  channel_id  {authority}  {target}
27417                {broadcast_list}
27418 
27419 
27420      Stream:   as (severity 1)
27421 
27422      Time:     In response to an operator accept command.
27423 
27424      Meaning:  The operator has issued  an accept command without
27425                any arguments.
27426 
27427      Action:   Enter a corrected command line.
27428 
27429 
27430                [operator_mc_cmds_.pl1]
27431                operator_mc_cmds_:    accept:     Ioname   already
27432                attached and active.  accept unsuccessful.
27433 
27434 
27435      Stream:   as (severity 1)
27436 
27437      Time:     In response to an operator accept command.
27438 
27439      Meaning:  The  error was returned  from mc_commands_$new_tty
27440                causing the accept to abort.
27441 
27442      Action:   Enter a corrected command line.
27443 
27444 
27445                [operator_mc_cmds_.pl1]
27446 
27447 
27448 operator_mc_cmds_              474            08/03/23     MR12.7^L
27449 
27450 
27451                operator_mc_cmds_:   accept:   Ioname  not  found.
27452                accept unsuccessful.
27453 
27454 
27455      Stream:   as (severity 1)
27456 
27457      Time:     In response to an operator accept command.
27458 
27459      Meaning:  The  error was returned  from mc_commands_$new_tty
27460                causing the accept to abort.  Channel not found in
27461                the cdt or pre-accepted as a virtual channel.
27462 
27463      Action:   Enter a corrected command line.
27464 
27465 
27466                [operator_mc_cmds_.pl1]
27467                operator_mc_cmds_:                    accept_vchn:
27468                ERROR_TABLE_MESSAGE Failed to accept VCHANNEL
27469 
27470 
27471      Stream:   as (severity 1)
27472 
27473      Time:     In response to an operator accept_vchn command.
27474 
27475      Meaning:  Unable to pre-accept VCHANNEL as a virtual channel
27476                identifier.
27477 
27478      Action:   Enter a corrected command line.
27479 
27480 
27481                [operator_mc_cmds_.pl1]
27482                operator_mc_cmds_:                    accept_vchn:
27483                ERROR_TABLE_MESSAGE Failed to reset restriction.
27484 
27485 
27486      Stream:   as (severity 1)
27487 
27488      Time:     In response to an operator accept command.
27489 
27490      Meaning:  Failed to reset the reply restriction.
27491 
27492      Action:   Enter a corrected command line.
27493 
27494 
27495                [operator_mc_cmds_.pl1]
27496                operator_mc_cmds_:                    accept_vchn:
27497                ERROR_TABLE_MESSAGE  Failed to set  broadcast list
27498                to BROADCAST_LIST.
27499 
27500 
27501      Stream:   as (severity 1)
27502 
27503      Time:     In response to an operator accept command.
27504 
27505 
27506 operator_mc_cmds_              475            08/03/23     MR12.7^L
27507 
27508 
27509      Meaning:  Failed   to    set   the   broadcast    list   for
27510                BROADCAST_LIST.
27511 
27512      Action:   Enter a corrected command line.
27513 
27514 
27515                [operator_mc_cmds_.pl1]
27516                operator_mc_cmds_:                    accept_vchn:
27517                ERROR_TABLE_MESSAGE  Failed to set  restriction to
27518                REPLY_TARGET
27519 
27520 
27521      Stream:   as (severity 1)
27522 
27523      Time:     In response to an operator accept command.
27524 
27525      Meaning:  Failed   to   set   the   reply   restriction  for
27526                REPLY_TARGET.
27527 
27528      Action:   Enter a corrected command line.
27529 
27530 
27531                [operator_mc_cmds_.pl1]
27532                operator_mc_cmds_:                    accept_vchn:
27533                ERROR_TABLE_MESSAGE Usage:  accept_vchn channel_id
27534                -auth  authority   -target  reply_target  -bc_list
27535                input_broadcast_list
27536 
27537 
27538 
27539      Stream:   as (severity 1)
27540 
27541      Time:     In response to an operator accept_vchn command.
27542 
27543      Meaning:  Incorrect number of arguments supplied.
27544 
27545      Action:   Enter a corrected command line.
27546 
27547 
27548                [operator_mc_cmds_.pl1]
27549                operator_mc_cmds_:   accept_vchn:    Incorrect  IO
27550                channel specification.  This  name is reserved for
27551                the system console.
27552 
27553 
27554 
27555      Stream:   as (severity 1)
27556 
27557      Time:     In response to an operator accept_vchn command.
27558 
27559      Meaning:  The  specified  virtual  channel  name  given  was
27560                "otw_".   This  identifier  cannot  be  used as it
27561                identifies the system console.
27562 
27563 
27564 operator_mc_cmds_              476            08/03/23     MR12.7^L
27565 
27566 
27567      Action:   Enter a corrected command line.
27568 
27569 
27570                [operator_mc_cmds_.pl1]
27571                operator_mc_cmds_:   accept_vchn:    Incorrect  IO
27572                channel specification.  DOT  Virtual channel names
27573                may not contain a DOT
27574 
27575 
27576      Stream:   as (severity 1)
27577 
27578      Time:     In response to an operator accept_vchn command.
27579 
27580      Meaning:  The  DOT (".")  character  cannot  be used  in the
27581                virtual channel specifier.
27582 
27583      Action:   Enter a corrected command line.
27584 
27585 
27586                [operator_mc_cmds_.pl1]
27587                operator_mc_cmds_:  accept_vchn:  Invalid argument
27588                -auth  may be  followed by  one of  the following:
27589                full, none, reply, daemon, query
27590 
27591 
27592 
27593      Stream:   as (severity 1)
27594 
27595      Time:     In response to an operator accept_vchn command.
27596 
27597      Meaning:  An  incorrect   argument  to  the   -auth  control
27598                argument was supplied.
27599 
27600      Action:   Enter a corrected command line.
27601 
27602 
27603                [operator_mc_cmds_.pl1]
27604                operator_mc_cmds_:  accept_vchn:  Invalid argument
27605                Bad broadcast list:  BROADCAST_LIST
27606 
27607 
27608      Stream:   as (severity 1)
27609 
27610      Time:     In response to an operator accept_vchn command.
27611 
27612      Meaning:  Incorrect   argument  supplied  to   the  -bc_list
27613                control argument.
27614 
27615      Action:   Enter a corrected command line.
27616 
27617 
27618                [operator_mc_cmds_.pl1]
27619 
27620 
27621 
27622 operator_mc_cmds_              477            08/03/23     MR12.7^L
27623 
27624 
27625                operator_mc_cmds_:  accept_vchn:  Invalid argument
27626                Bad reply target:  TARGET
27627 
27628 
27629      Stream:   as (severity 1)
27630 
27631      Time:     In response to an operator accept_vchn command.
27632 
27633      Meaning:  An  incorrect  argument   to  the  -reply  control
27634                argument was supplied.
27635 
27636      Action:   Enter a corrected command line.
27637 
27638 
27639                [operator_mc_cmds_.pl1]
27640                operator_mc_cmds_:   accept_vchn:  Ioname  already
27641                attached and active.  VCHANNEL set to full.
27642 
27643 
27644 
27645      Stream:   as (severity 1)
27646 
27647      Time:     In response to an operator accept_vchn command.
27648 
27649      Meaning:  VCHANNEL already active  and authorization request
27650                is same.
27651 
27652      Action:   Enter a corrected command line.
27653 
27654 
27655                [operator_mc_cmds_.pl1]
27656                operator_mc_cmds_:      accept_vchn:     Specified
27657                control  argument  is  not  accpeted  Argument not
27658                accepted:  ARGUMENT
27659 
27660 
27661 
27662      Stream:   as (severity 1)
27663 
27664      Time:     In response to an operator accept_vchn command.
27665 
27666      Meaning:  An incorrect control argument  was supplied to the
27667                accept_vchn request.
27668 
27669      Action:   Enter a corrected command line.
27670 
27671 
27672                [operator_mc_cmds_.pl1]
27673                operator_mc_cmds_:   COMMAND:  ERROR_TABLE_MESSAGE
27674                SYSDIR>answer_table
27675 
27676 
27677      Stream:   as (severity 1)
27678 
27679 
27680 operator_mc_cmds_              478            08/03/23     MR12.7^L
27681 
27682 
27683      Time:     In response to an operator command, COMMAND.
27684 
27685      Meaning:  The system  was unable to access  the answer_table
27686                in SYSDIR.
27687 
27688      Action:   Contact the system programming staff.
27689 
27690 
27691                [operator_mc_cmds_.pl1]
27692                operator_mc_cmds_:   COMMAND:  ERROR_TABLE_MESSAGE
27693                SYSDIR>cdt
27694 
27695 
27696      Stream:   as (severity 1)
27697 
27698      Time:     In response to an operator command, COMMAND.
27699 
27700      Meaning:  The system was unable to access the cdt in SYSDIR.
27701 
27702      Action:   Contact the system programming staff.
27703 
27704 
27705                [operator_mc_cmds_.pl1]
27706                operator_mc_cmds_:   COMMAND:  ERROR_TABLE_MESSAGE
27707                SYSDIR>installation_parms
27708 
27709 
27710      Stream:   as (severity 1)
27711 
27712      Time:     In response to an operator command, COMMAND.
27713 
27714      Meaning:  The    system   was    unable   to    access   the
27715                installation_parms in SYSDIR.
27716 
27717      Action:   Contact the system programming staff.
27718 
27719 
27720                [operator_mc_cmds_.pl1]
27721                operator_mc_cmds_:   COMMAND:  ERROR_TABLE_MESSAGE
27722                SYSDIR>whotab
27723 
27724 
27725      Stream:   as (severity 1)
27726 
27727      Time:     In response to an operator command, COMMAND.
27728 
27729      Meaning:  The  system was  unable  to  access the  whotab in
27730                SYSDIR.
27731 
27732      Action:   Contact the system programming staff.
27733 
27734 
27735                [operator_mc_cmds_.pl1]
27736 
27737 
27738 operator_mc_cmds_              479            08/03/23     MR12.7^L
27739 
27740 
27741                operator_mc_cmds_:   COMMAND:  ERROR_TABLE_MESSAGE
27742                Incorrect number of arguments.
27743 
27744 
27745      Stream:   as (severity 1)
27746 
27747      Time:     In response to an operator command COMMAND.
27748 
27749      Meaning:  Insufficient number of arguments supplied with the
27750                command.
27751 
27752      Action:   Enter a corrected command line.
27753 
27754 
27755                [operator_mc_cmds_.pl1]
27756                operator_mc_cmds_:   COMMAND:  ERROR_TABLE_MESSAGE
27757                removing user (no proc) on channel CHANNEL
27758 
27759 
27760      Stream:   as (severity 1)
27761 
27762      Time:     In response to an operator command.
27763 
27764      Meaning:  An error described  by ERROR_TABLE_MESSAGE occured
27765                while attempting the operator command, COMMAND.
27766 
27767      Action:   Contact the system programming staff.
27768 
27769 
27770                [operator_mc_cmds_.pl1]
27771                operator_mc_cmds_:   COMMAND:  ERROR_TABLE_MESSAGE
27772                trying to access SYSDIR>mc_anstbl
27773 
27774 
27775      Stream:   as (severity 1)
27776 
27777      Time:     In response to an operator command, COMMAND.
27778 
27779      Meaning:  The system was not able to access the mc_anstbl in
27780                SYSDIR.
27781 
27782      Action:   Contact the system programming staff.
27783 
27784 
27785                [operator_mc_cmds_.pl1]
27786                operator_mc_cmds_:  define:  Action not performed.
27787                define unsuccessful.
27788 
27789 
27790      Stream:   as (severity 1)
27791 
27792      Time:     In response to an operator define command.
27793 
27794 
27795 
27796 operator_mc_cmds_              480            08/03/23     MR12.7^L
27797 
27798 
27799      Meaning:  An  error  was  returned  from mc_commands_$define
27800                causing the define to abort.  Target channel found
27801                requiring an accept in mc_anstbl.
27802 
27803      Action:   Enter a corrected command line.
27804 
27805 
27806                [operator_mc_cmds_.pl1]
27807                operator_mc_cmds_:   define:   ERROR_TABLE_MESSAGE
27808                define unsuccessful.
27809 
27810 
27811      Stream:   as (severity 1)
27812 
27813      Time:     In response to an operator define command.
27814 
27815      Meaning:  An  error  was  returned  from mc_commands_$define
27816                causing the define to abort.
27817 
27818      Action:   Enter a corrected command line.
27819 
27820 
27821                [operator_mc_cmds_.pl1]
27822                operator_mc_cmds_:   define:   Ioname  not active.
27823                define unsuccessful.
27824 
27825 
27826      Stream:   as (severity 1)
27827 
27828      Time:     In response to an operator define command.
27829 
27830      Meaning:  An  error  was  returned  from mc_commands_$define
27831                causing the  define to abort.  Target  channel not
27832                active in the mc_anstbl.
27833 
27834      Action:   Enter a corrected command line.
27835 
27836 
27837                [operator_mc_cmds_.pl1]
27838                operator_mc_cmds_:   define:   Ioname  not  found.
27839                define unsuccessful.
27840 
27841 
27842      Stream:   as (severity 1)
27843 
27844      Time:     In response to an operator define command.
27845 
27846      Meaning:  An  error  was  returned  from mc_commands_$define
27847                causing  the define  to abort.   Could not  locate
27848                VCONS in vcons_tab.
27849 
27850      Action:   Enter a corrected command line.
27851 
27852 
27853 
27854 operator_mc_cmds_              481            08/03/23     MR12.7^L
27855 
27856 
27857 
27858 
27859                [operator_mc_cmds_.pl1]
27860                operator_mc_cmds_:  define:   There is no  room to
27861                make requested allocations.
27862 
27863 
27864      Stream:   as (severity 1)
27865 
27866      Time:     In response to an operator define command.
27867 
27868      Meaning:  The  operator has  issued a  define SOURCE  STREAM
27869                VCONS  command but the  system could not  make the
27870                new entry in the message routing table.  No action
27871                was taken.
27872 
27873      Action:   Enter a corrected command line.
27874 
27875 
27876                [operator_mc_cmds_.pl1]
27877                operator_mc_cmds_:   define:  Typename  not found.
27878                define unsuccessful.
27879 
27880 
27881      Stream:   as (severity 1)
27882 
27883      Time:     In response to an operator define command.
27884 
27885      Meaning:  An  error  was  returned  from mc_commands_$define
27886                causing  the define  to abort.   Target VCONS type
27887                not known.
27888 
27889      Action:   Enter a corrected command line.
27890 
27891 
27892                [operator_mc_cmds_.pl1]
27893                operator_mc_cmds_:   deroute:  ERROR_TABLE_MESSAGE
27894                reroute unsuccessful.
27895 
27896 
27897      Stream:   as (severity 1)
27898 
27899      Time:     In response to an operator deroute command.
27900 
27901      Meaning:  An  error was  returned from  mc_commands_$deroute
27902                causing the deroute to abort.
27903 
27904      Action:   Enter a corrected command line.
27905 
27906 
27907                [operator_mc_cmds_.pl1]
27908                operator_mc_cmds_:  deroute:  There  is no room to
27909                make requested allocations.
27910 
27911 
27912 operator_mc_cmds_              482            08/03/23     MR12.7^L
27913 
27914 
27915      Stream:   as (severity 1)
27916 
27917      Time:     In response to an operator deroute command.
27918 
27919      Meaning:  The  operator has  issued a  deroute SOURCE STREAM
27920                VCONS command  but the system had no  room to make
27921                the new entry in the message routing table.  There
27922                may be up to 16  sources, each with 8 streams, and
27923                each stream may have up to 8 virtual consoles.  No
27924                action was taken.
27925 
27926      Action:   Enter a corrected command line.
27927 
27928 
27929                [operator_mc_cmds_.pl1]
27930                operator_mc_cmds_:  drop:  error:  Channel CHANNEL
27931                not a message coordinator terminal.
27932 
27933 
27934      Stream:   as (severity 1)
27935 
27936      Time:     In response to an operator command.
27937 
27938      Meaning:  Cannot drop CHANNEL as it cannot be found attached
27939                to the message coordinator.
27940 
27941      Action:   Contact the system programming staff.
27942 
27943 
27944                [operator_mc_cmds_.pl1]
27945                operator_mc_cmds_:  drop:  error:  Channel CHANNEL
27946                not configured.
27947 
27948 
27949      Stream:   as (severity 1)
27950 
27951      Time:     In response to an operator command.
27952 
27953      Meaning:  Channel CHANNEL is not defined in the system cdt.
27954 
27955      Action:   Contact the system programming staff.
27956 
27957 
27958                [operator_mc_cmds_.pl1]
27959                operator_mc_cmds_:  drop:  error:  Channel CHANNEL
27960                not dialed to initializer.
27961 
27962 
27963      Stream:   as (severity 1)
27964 
27965      Time:     In response to an operator command.
27966 
27967 
27968 
27969 
27970 operator_mc_cmds_              483            08/03/23     MR12.7^L
27971 
27972 
27973      Meaning:  CHANNEL must  be dialed to the  initializer before
27974                being dropped.
27975 
27976      Action:   Contact the system programming staff.
27977 
27978 
27979                [operator_mc_cmds_.pl1]
27980                operator_mc_cmds_:    drop:    ERROR_TABLE_MESSAGE
27981                drop unsuccessful.
27982 
27983 
27984      Stream:   as (severity 1)
27985 
27986      Time:     In response to an operator drop command.
27987 
27988      Meaning:  An error was returned from mc_commands_$remove_tty
27989                causing the drop to abort.
27990 
27991      Action:   Enter a corrected command line.
27992 
27993 
27994                [operator_mc_cmds_.pl1]
27995                operator_mc_cmds_:     redefine:     Action    not
27996                performed.  redefine unsuccessful.
27997 
27998 
27999      Stream:   as (severity 1)
28000 
28001      Time:     In response to an operator redefine command.
28002 
28003      Meaning:  An  error was returned  from mc_commands_$redefine
28004                causing  the redefine   to abort.   Target channel
28005                found requiring an accept in mc_anstbl.
28006 
28007      Action:   Enter a corrected command line.
28008 
28009 
28010                [operator_mc_cmds_.pl1]
28011                operator_mc_cmds_:   redefine:   Allocation  could
28012                not be performed.  redefine unsuccessful.
28013 
28014 
28015      Stream:   as (severity 1)
28016 
28017      Time:     In response to an operator redefine command.
28018 
28019      Meaning:  The  operator has  issued a  redefine VCONS SOURCE
28020                STREAM VCONS command but the system could not make
28021                the  new entry in  the message routing  table.  No
28022                action was taken.
28023 
28024      Action:   Enter a corrected command line.
28025 
28026 
28027 
28028 operator_mc_cmds_              484            08/03/23     MR12.7^L
28029 
28030 
28031 
28032 
28033                [operator_mc_cmds_.pl1]
28034                operator_mc_cmds_:  redefine:  ERROR_TABLE_MESSAGE
28035                redefine unsuccessful.
28036 
28037 
28038      Stream:   as (severity 1)
28039 
28040      Time:     In response to an operator redefine command.
28041 
28042      Meaning:  An  error was returned  from mc_commands_$redefine
28043                causing the redefine to abort.
28044 
28045      Action:   Enter a corrected command line.
28046 
28047 
28048                [operator_mc_cmds_.pl1]
28049                operator_mc_cmds_:  redefine:   Ioname not active.
28050                redefine unsuccessful.
28051 
28052 
28053      Stream:   as (severity 1)
28054 
28055      Time:     In response to an operator redefine command.
28056 
28057      Meaning:  An  error was returned  from mc_commands_$redefine
28058                causing the redefine to abort.  Target channel not
28059                active in the mc_anstbl.
28060 
28061      Action:   Enter a corrected command line.
28062 
28063 
28064                [operator_mc_cmds_.pl1]
28065                operator_mc_cmds_:   redefine:  Ioname  not found.
28066                redefine unsuccessful.
28067 
28068 
28069      Stream:   as (severity 1)
28070 
28071      Time:     In response to an operator redefine command.
28072 
28073      Meaning:  An  error was returned  from mc_commands_$redefine
28074                causing the  redefine to abort.  Could  not locate
28075                VCONS in vcons_tab.
28076 
28077      Action:   Enter a corrected command line.
28078 
28079 
28080                [operator_mc_cmds_.pl1]
28081                operator_mc_cmds_:  redefine:  Typename not found.
28082                redefine unsuccessful.
28083 
28084 
28085 
28086 operator_mc_cmds_              485            08/03/23     MR12.7^L
28087 
28088 
28089      Stream:   as (severity 1)
28090 
28091      Time:     In response to an operator redefine command.
28092 
28093      Meaning:  An  error was returned  from mc_commands_$redefine
28094                causing the redefine to  abort.  Target VCONS type
28095                not known.
28096 
28097      Action:   Enter a corrected command line.
28098 
28099 
28100                [operator_mc_cmds_.pl1]
28101                operator_mc_cmds_:   reroute:  ERROR_TABLE_MESSAGE
28102                reroute unsuccessful.
28103 
28104 
28105      Stream:   as (severity 1)
28106 
28107      Time:     In response to an operator reroute command.
28108 
28109      Meaning:  An  error was  returned from  mc_commands_$reroute
28110                causing the reroute to abort.
28111 
28112      Action:   Enter a corrected command line.
28113 
28114 
28115                [operator_mc_cmds_.pl1]
28116                operator_mc_cmds_:  reroute:  There  is no room to
28117                make requested allocations.
28118 
28119 
28120      Stream:   as (severity 1)
28121 
28122      Time:     In response to an operator reroute command.
28123 
28124      Meaning:  The  operator has  issued a  reroute SOURCE STREAM
28125                OLD_VCONS NEW_VCONS command but  the system had no
28126                room to make the new  entry in the message routing
28127                table.  There may be up to 16 sources, each with 8
28128                streams, and each stream may  have up to 8 virtual
28129                consoles.  No action was taken.
28130 
28131      Action:   Enter a corrected command line.
28132 
28133 
28134                [operator_mc_cmds_.pl1]
28135                operator_mc_cmds_:    route:   ERROR_TABLE_MESSAGE
28136                route unsuccessful.
28137 
28138 
28139      Stream:   as (severity 1)
28140 
28141      Time:     In response to an operator route command.
28142 
28143 
28144 operator_mc_cmds_              486            08/03/23     MR12.7^L
28145 
28146 
28147      Meaning:  An  error  was  returned  from  mc_commands_$route
28148                causing the route to abort.
28149 
28150      Action:   Enter a corrected command line.
28151 
28152 
28153                [operator_mc_cmds_.pl1]
28154                operator_mc_cmds_:   route:    Ioname  not  found.
28155                route unsuccessful.
28156 
28157 
28158      Stream:   as (severity 1)
28159 
28160      Time:     In response to an operator route command.
28161 
28162      Meaning:  An  error  was  returned  from  mc_commands_$route
28163                causing the route to  abort.  VCONS not located in
28164                vcons_tab.
28165 
28166      Action:   Enter a corrected command line.
28167 
28168 
28169                [operator_mc_cmds_.pl1]
28170                operator_mc_cmds_:   route:  There  is no  room to
28171                make requested allocations.
28172 
28173 
28174      Stream:   as (severity 1)
28175 
28176      Time:     In response to an operator route command.
28177 
28178      Meaning:  The  operator  has  issued  a  route SOURCE STREAM
28179                VCONS command  but the system had no  room to make
28180                the new entry in the message routing table.  There
28181                may be up to 16  sources, each with 8 streams, and
28182                each stream may have up to 8 virtual consoles.  No
28183                action was taken.
28184 
28185      Action:   Enter a corrected command line.
28186 
28187 
28188                [operator_mc_cmds_.pl1]
28189                operator_mc_cmds_:   substty:  ERROR_TABLE_MESSAGE
28190                removing channel CHANNEL
28191 
28192 
28193      Stream:   as (severity 1)
28194 
28195      Time:     In response to an operator substty command.
28196 
28197      Meaning:  Unable to remove CHANNEL  designated as the source
28198                of the substitution.
28199 
28200 
28201 
28202 operator_mc_cmds_              487            08/03/23     MR12.7^L
28203 
28204 
28205      Action:   Enter a corrected command line.
28206 
28207 
28208                [operator_mc_cmds_.pl1]
28209                operator_mc_cmds_:  substty:   Channel CHANNEL not
28210                configured.
28211 
28212 
28213      Stream:   as (severity 1)
28214 
28215      Time:     In response to an operator substty command.
28216 
28217      Meaning:  Channel CHANNEL is not found in the system cdt.
28218 
28219      Action:   Enter a corrected command line.
28220 
28221 
28222                [operator_mc_cmds_.pl1]
28223                operator_mc_cmds_:  substty:   Channel CHANNEL not
28224                dialed to initializer
28225 
28226 
28227      Stream:   as (severity 1)
28228 
28229      Time:     In response to an operator substty command.
28230 
28231      Meaning:  Channel CHANNEL  was not previously dialed  to the
28232                initializer and thus cannot be substituted.
28233 
28234      Action:   Enter a corrected command line.
28235 
28236 
28237                [operator_mc_cmds_.pl1]
28238                operator_mc_cmds_:    substty:    error:    cannot
28239                substty for same channel
28240 
28241 
28242      Stream:   as (severity 1)
28243 
28244      Time:     In response to an operator substty command.
28245 
28246      Meaning:  The  operator  has  attempted  to  use  substty to
28247                substitute a channel for itself.
28248 
28249      Action:   Enter a corrected command line.
28250 
28251 
28252                [operator_mc_cmds_.pl1]
28253                operator_mc_cmds_:  substty:   error:  channel not
28254                available
28255 
28256 
28257      Stream:   as (severity 1)
28258 
28259 
28260 operator_mc_cmds_              488            08/03/23     MR12.7^L
28261 
28262 
28263      Time:     In response to an operator accept command.
28264 
28265      Meaning:  Channel  cannot be  used as  a message coordinator
28266                channel.
28267 
28268      Action:   Enter a corrected command line.
28269 
28270 
28271                [operator_mc_cmds_.pl1]
28272                operator_mc_cmds_:  substty:   error:  channel not
28273                defined in cdt.
28274 
28275 
28276      Stream:   as (severity 1)
28277 
28278      Time:     In response to an operator accept command.
28279 
28280      Meaning:  Channel  is  not  found  in  the  system  cdt  and
28281                therefore cannot be used.
28282 
28283      Action:   Enter a corrected command line.
28284 
28285 
28286                [operator_mc_cmds_.pl1]
28287                operator_mc_cmds_:   substty:  ERROR_TABLE_MESSAGE
28288                substty unsuccessful.
28289 
28290 
28291      Stream:   as (severity 1)
28292 
28293      Time:     In response to an operator substty command.
28294 
28295      Meaning:  An  error was  returned from  mc_commands_$substty
28296                causing the substty to abort.
28297 
28298      Action:   Enter a corrected command line.
28299 
28300 
28301                [operator_mc_cmds_.pl1]
28302                operator_mc_cmds_:   substty:   Ioname  not found.
28303                substty unsuccessful.
28304 
28305 
28306      Stream:   as (severity 1)
28307 
28308      Time:     In response to an operator substty command.
28309 
28310      Meaning:  An  error was  returned from  mc_commands_$substty
28311                causing  the substty  to abort.   Could not locate
28312                source channel in mc_anstbl.
28313 
28314      Action:   Enter a corrected command line.
28315 
28316 
28317 
28318 operator_mc_cmds_              489            08/03/23     MR12.7^L
28319 
28320 
28321 
28322 
28323                [operator_mc_cmds_.pl1]
28324                operator_mc_cmds_:   substty:   Ioname  not found.
28325                substty unsuccessful.
28326 
28327 
28328      Stream:   as (severity 1)
28329 
28330      Time:     In response to an operator substty command.
28331 
28332      Meaning:  The  error was returned  from mc_commands_$new_tty
28333                causing the substty to  abort.  The target channel
28334                not found in the cdt  or pre-accepted as a virtual
28335                channel.
28336 
28337      Action:   Enter a corrected command line.
28338 
28339 
28340                [operator_mc_cmds_.pl1]
28341                operator_mc_cmds_:  substty:  The requested action
28342                was not performed.  substty unsuccessful.
28343 
28344 
28345      Stream:   as (severity 1)
28346 
28347      Time:     In response to an operator substty command.
28348 
28349      Meaning:  An  error was  returned from  mc_commands_$substty
28350                causing the substty to  abort.  The target channel
28351                is in  a "pending" state,  which means it  has not
28352                been accepted yet.
28353 
28354      Action:   Enter a corrected command line.
28355 
28356 
28357                [operator_mc_cmds_.pl1]
28358                operator_mc_cmds_:  undefine:  ERROR_TABLE_MESSAGE
28359                undefine unsuccessful.
28360 
28361 
28362      Stream:   as (severity 1)
28363 
28364      Time:     In response to an operator undefine command.
28365 
28366      Meaning:  An  error was returned  from mc_commands_$undefine
28367                causing the undefine to abort.
28368 
28369      Action:   Enter a corrected command line.
28370 
28371 
28372                [operator_mc_cmds_.pl1]
28373 
28374 
28375 
28376 operator_mc_cmds_              490            08/03/23     MR12.7^L
28377 
28378 
28379                operator_mc_cmds_:   undefine:  Ioname  not found.
28380                undefine unsuccessful.
28381 
28382 
28383      Stream:   as (severity 1)
28384 
28385      Time:     In response to an operator undefine command.
28386 
28387      Meaning:  An  error was returned  from mc_commands_$undefine
28388                causing the  undefine to abort.  Could  not locate
28389                VCONS in vcons_tab.
28390 
28391      Action:   Enter a corrected command line.
28392 
28393 
28394                [operator_process_cmds_.pl1]
28395                operator_process_cmds_:   bump:   error:   invalid
28396                arguments
28397 
28398 
28399      Stream:   as (severity 1)
28400 
28401      Time:     In response to an operator command.
28402 
28403      Meaning:  A bad argument has been typed to the bump command.
28404                No action was taken.
28405 
28406      Action:   Enter a corrected command line.
28407 
28408 
28409                [operator_process_cmds_.pl1]
28410                operator_process_cmds_:  bump:  NAME.PROJ bumped
28411 
28412 
28413      Stream:   as (severity 1)
28414 
28415      Time:     In response to an operator command.
28416 
28417      Meaning:  This is the response  to an operator bump command.
28418                The user affected is named.
28419 
28420      Action:   No operator action is required.
28421 
28422 
28423                [operator_process_cmds_.pl1]
28424                operator_process_cmds_:    bump:   NAME.PROJ   has
28425                "nobump"
28426 
28427 
28428      Stream:   as (severity 1)
28429 
28430      Time:     While system is running.
28431 
28432 
28433 
28434 operator_process_cmds_         491            08/03/23     MR12.7^L
28435 
28436 
28437      Meaning:  This is the response to the command bump NAME PROJ
28438                if  the user has  the nobump privilege.   The user
28439                was not bumped.
28440 
28441      Action:   If it is imperative to bump the user, for instance
28442                at system shutdown time, do  a who to find out his
28443                channel number, then type "bump CHANNEL".
28444 
28445 
28446 
28447                [operator_process_cmds_.pl1]
28448                operator_process_cmds_:  bump:   no bump signalled
28449                to NAME PROJ
28450 
28451 
28452      Stream:   as (severity 1)
28453 
28454      Time:     In response to an operator command.
28455 
28456      Meaning:  An operator  bump command specified  a nonexistent
28457                channel name or user  name and project.  No action
28458                was taken on the command.
28459 
28460      Action:   Enter a corrected command  line.  This message may
28461                be printed as a result of trying to bump a user by
28462                name  when he has  nobump privilege.  Bump  him by
28463                channel name instead.
28464 
28465 
28466 
28467                [operator_process_cmds_.pl1]
28468                operator_process_cmds_:  COMMAND:  error:  Invalid
28469                FNP tag:  FNP
28470 
28471 
28472      Stream:   as (severity 1)
28473 
28474      Time:     In response to an operator command COMMAND.
28475 
28476      Meaning:  The  FNP tag following  COMMAND was more  than one
28477                character in  length.  FNP specifiers can  only be
28478                one character long (ie:  a, b, c, etc.).
28479 
28480      Action:   Enter a corrected command line.
28481 
28482 
28483                [operator_process_cmds_.pl1]
28484                operator_process_cmds_:  COMMAND:   error:  No FNP
28485                tag specified
28486 
28487 
28488      Stream:   as (severity 1)
28489 
28490 
28491 
28492 operator_process_cmds_         492            08/03/23     MR12.7^L
28493 
28494 
28495      Time:     In response to an operator command COMMAND.
28496 
28497      Meaning:  Expected   a  FNP   designator,  but   none  typed
28498                following COMMAND.
28499 
28500      Action:   Enter a corrected command line.
28501 
28502 
28503                [operator_process_cmds_.pl1]
28504                operator_process_cmds_:    COMMAND:   error:    No
28505                multiplexer specified
28506 
28507 
28508      Stream:   as (severity 1)
28509 
28510      Time:     In response to an operator command COMMAND.
28511 
28512      Meaning:  Expected a multiplexer  designator, but none typed
28513                following COMMAND.
28514 
28515      Action:   Enter a corrected command line.
28516 
28517 
28518                [operator_process_cmds_.pl1]
28519                operator_process_cmds_:  COMMAND:   error:  Usage:
28520                COMMAND  (Person.Project|CHANNEL|mpx   MPX)  {TIME
28521                MESSAGE} The "Person Project" format is obsolete.
28522 
28523 
28524 
28525      Stream:   as (severity 1)
28526 
28527      Time:     In response to an operator command COMMAND.
28528 
28529      Meaning:  The  character "."  was  not found on  the request
28530                line and COMMAND was not followed by a process id.
28531                If  argument  following  COMMAND  is  personid and
28532                projectid, the correct  syntax is "Person.Project"
28533                not "Person Project".
28534 
28535      Action:   Enter a corrected command line.
28536 
28537 
28538                [operator_process_cmds_.pl1]
28539                operator_process_cmds_:  COMMAND:   error:  Usage:
28540                COMMAND    (Person.Project|CHANNEL|mpx   MPX|-pid)
28541                {TIME MESSAGE}
28542 
28543 
28544      Stream:   as (severity 1)
28545 
28546      Time:     In response to an operator command COMMAND.
28547 
28548 
28549 
28550 operator_process_cmds_         493            08/03/23     MR12.7^L
28551 
28552 
28553      Meaning:  Insufficient number of arguments supplied with the
28554                command.
28555 
28556      Action:   Enter a corrected command line.
28557 
28558 
28559                [operator_process_cmds_.pl1]
28560                operator_process_cmds_:                   COMMAND:
28561                ERROR_TABLE_MESSAGE SYSDIR>answer_table
28562 
28563 
28564      Stream:   as (severity 1)
28565 
28566      Time:     In response to an operator command, COMMAND.
28567 
28568      Meaning:  The system  was unable to access  the answer_table
28569                in SYSDIR.
28570 
28571      Action:   Contact the system programming staff.
28572 
28573 
28574                [operator_process_cmds_.pl1]
28575                operator_process_cmds_:                   COMMAND:
28576                ERROR_TABLE_MESSAGE SYSDIR>cdt
28577 
28578 
28579      Stream:   as (severity 1)
28580 
28581      Time:     In response to an operator command, COMMAND.
28582 
28583      Meaning:  The system was unable to access the cdt in SYSDIR.
28584 
28585      Action:   Contact the system programming staff.
28586 
28587 
28588                [operator_process_cmds_.pl1]
28589                operator_process_cmds_:                   COMMAND:
28590                ERROR_TABLE_MESSAGE SYSDIR>installation_parms
28591 
28592 
28593      Stream:   as (severity 1)
28594 
28595      Time:     In response to an operator command, COMMAND.
28596 
28597      Meaning:  The    system   was    unable   to    access   the
28598                installation_parms in SYSDIR.
28599 
28600      Action:   Contact the system programming staff.
28601 
28602 
28603                [operator_process_cmds_.pl1]
28604                operator_process_cmds_:                   COMMAND:
28605                ERROR_TABLE_MESSAGE SYSDIR>whotab
28606 
28607 
28608 operator_process_cmds_         494            08/03/23     MR12.7^L
28609 
28610 
28611      Stream:   as (severity 1)
28612 
28613      Time:     In response to an operator command, COMMAND.
28614 
28615      Meaning:  The  system was  unable  to  access the  whotab in
28616                SYSDIR.
28617 
28618      Action:   Contact the system programming staff.
28619 
28620 
28621                [operator_process_cmds_.pl1]
28622                operator_process_cmds_:                   COMMAND:
28623                ERROR_TABLE_MESSAGE Error recieved from AS.
28624 
28625 
28626      Stream:   as (severity 1)
28627 
28628      Time:     In response to an operator command COMMAND.
28629 
28630      Meaning:  Recieved   an   error   from   answering   service
28631                attempting  to remove  the terminal  user from the
28632                system  answer table.   User's process  state will
28633                remain unchanged.
28634 
28635      Action:   Enter a corrected command line.
28636 
28637 
28638                [operator_process_cmds_.pl1]
28639                operator_process_cmds_:                   COMMAND:
28640                ERROR_TABLE_MESSAGE From hcs_$wakeup for CHANNEL
28641 
28642 
28643      Stream:   as (severity 1)
28644 
28645      Time:     In response to an operator command COMMAND.
28646 
28647      Meaning:  Recieved  an  error  from  answering  service when
28648                attempting  to  process  the  command  COMMAND for
28649                channel CHANNEL.
28650 
28651      Action:   Enter a corrected command line.
28652 
28653 
28654                [operator_process_cmds_.pl1]
28655                operator_process_cmds_:                   COMMAND:
28656                ERROR_TABLE_MESSAGE Incorrect number of arguments.
28657 
28658 
28659      Stream:   as (severity 1)
28660 
28661      Time:     In response to an operator command COMMAND.
28662 
28663 
28664 
28665 
28666 operator_process_cmds_         495            08/03/23     MR12.7^L
28667 
28668 
28669      Meaning:  Insufficient number of arguments supplied with the
28670                command.
28671 
28672      Action:   Enter a corrected command line.
28673 
28674 
28675                [operator_process_cmds_.pl1]
28676                operator_process_cmds_:                   COMMAND:
28677                ERROR_TABLE_MESSAGE     Invalid    process     id:
28678                PROCESS_ID.  Use  the first 6 or all  12 digits of
28679                the pid.
28680 
28681 
28682 
28683      Stream:   as (severity 1)
28684 
28685      Time:     In response to an operator command COMMAND.
28686 
28687      Meaning:  The typed length of the PROCESS_ID was incorrect.
28688 
28689      Action:   Enter a corrected command line.
28690 
28691 
28692                [operator_process_cmds_.pl1]
28693                operator_process_cmds_:  detach:   Channel CHANNEL
28694                is not currently active and cannot be detached.
28695 
28696 
28697      Stream:   as (severity 1)
28698 
28699      Time:     In response to an operator command.
28700 
28701      Meaning:  An  operator detach   command specified  a channel
28702                that is not attached.  No action was taken.
28703 
28704      Action:   Enter a corrected command line
28705 
28706 
28707                [operator_process_cmds_.pl1]
28708                operator_process_cmds_:   detach:   CHANNEL  is in
28709                use  by the  message  coordinator  and can  not be
28710                detached.
28711 
28712 
28713      Stream:   as (severity 1)
28714 
28715      Time:     In response to an operator command.
28716 
28717      Meaning:  An  operator detach   command specified  a message
28718                coordinator   channel.    The   channel   was  not
28719                detached.
28720 
28721 
28722 
28723 
28724 operator_process_cmds_         496            08/03/23     MR12.7^L
28725 
28726 
28727      Action:   Enter  a  corrected  command  line.   Use the drop
28728                command  to take a  channel away from  the message
28729                coordinator.
28730 
28731 
28732 
28733                [operator_process_cmds_.pl1]
28734                operator_process_cmds_:  detach:   error:  invalid
28735                arguments
28736 
28737 
28738      Stream:   as (severity 1)
28739 
28740      Time:     In response to an operator command.
28741 
28742      Meaning:  A  bad  argument  has  been  typed  to  the detach
28743                command.  No action was taken.
28744 
28745      Action:   Enter a corrected command line.
28746 
28747 
28748                [operator_process_cmds_.pl1]
28749                operator_process_cmds_:    detach:   ERROR_MESSAGE
28750                CHANNEL
28751 
28752 
28753      Stream:   as (severity 1)
28754 
28755      Time:     In response to an operator command.
28756 
28757      Meaning:  The operator  has issued a detach  CHANNEL command
28758                and the error  described by ERROR_MESSAGE occurred
28759                during the attempt to detach it.
28760 
28761      Action:   Enter a corrected command line.
28762 
28763 
28764                [operator_process_cmds_.pl1]
28765                operator_process_cmds_:      detach:     NAME.PROJ
28766                detached
28767 
28768 
28769      Stream:   as (severity 1)
28770 
28771      Time:     In response to an operator command.
28772 
28773      Meaning:  This  is  the  response   to  an  operator  detach
28774                command.  The user affected is named.
28775 
28776      Action:   No operator action is required.
28777 
28778 
28779                [operator_process_cmds_.pl1]
28780 
28781 
28782 operator_process_cmds_         497            08/03/23     MR12.7^L
28783 
28784 
28785                operator_process_cmds_:    detach:     no   detach
28786                signalled to NAME PROJ
28787 
28788 
28789      Stream:   as (severity 1)
28790 
28791      Time:     In response to an operator command.
28792 
28793      Meaning:  An operator detach command specified a nonexistent
28794                channel name or user  name and project.  No action
28795                was taken on the command.
28796 
28797      Action:   Enter a corrected command line.
28798 
28799 
28800                [operator_process_cmds_.pl1]
28801                operator_process_cmds_:    disconnect:   NAME.PROJ
28802                disconnected.
28803 
28804 
28805      Stream:   as (severity 1)
28806 
28807      Time:     In response to an operator command.
28808 
28809      Meaning:  This  is the  response to  an operator  disconnect
28810                command.  The user affected is named.
28811 
28812      Action:   No operator action is required.
28813 
28814 
28815                [operator_process_cmds_.pl1]
28816                operator_process_cmds_:    terminate:    NAME.PROJ
28817                terminated
28818 
28819 
28820      Stream:   as (severity 1)
28821 
28822      Time:     In response to an operator command.
28823 
28824      Meaning:  This  is  the  response  to  an operator terminate
28825                command.  The user affected is named.
28826 
28827      Action:   No operator action is required.
28828 
28829 
28830                [operator_process_cmds_.pl1]
28831                operator_process_cmds_:  terminate:   no terminate
28832                signalled to NAME PROJ
28833 
28834 
28835      Stream:   as (severity 1)
28836 
28837      Time:     In response to an operator command.
28838 
28839 
28840 operator_process_cmds_         498            08/03/23     MR12.7^L
28841 
28842 
28843      Meaning:  An   operator   terminate   command   specified  a
28844                nonexistent channel name or user name and project.
28845                No action was taken on the command.
28846 
28847      Action:   Enter a corrected command line.
28848 
28849 
28850                [operator_process_cmds_.pl1]
28851                operator_process_cmds_:  unbump:   error:  invalid
28852                arguments
28853 
28854 
28855      Stream:   as (severity 1)
28856 
28857      Time:     In response to an operator command.
28858 
28859      Meaning:  A  bad  argument  has  been  typed  to  the unbump
28860                command.  No action was taken.
28861 
28862      Action:   Enter a corrected command line.
28863 
28864 
28865                [operator_process_cmds_.pl1]
28866                operator_process_cmds_:      unbump:     NAME.PROJ
28867                unbumped
28868 
28869 
28870      Stream:   as (severity 1)
28871 
28872      Time:     In response to an operator command.
28873 
28874      Meaning:  This  is  the  response   to  an  operator  unbump
28875                command.  The user affected is named.
28876 
28877      Action:   No operator action is required.
28878 
28879 
28880                [operator_process_cmds_.pl1]
28881                operator_process_cmds_:    unbump:     no   unbump
28882                signalled to NAME PROJ
28883 
28884 
28885      Stream:   as (severity 1)
28886 
28887      Time:     In response to an operator command.
28888 
28889      Meaning:  An operator unbump command specified a nonexistent
28890                channel name or user name and project, or the user
28891                specified  was not in  a bumped state.   No action
28892                was taken on the command.
28893 
28894      Action:   Enter a corrected command line.
28895 
28896 
28897 
28898 page_fault                     499            08/03/23     MR12.7^L
28899 
28900 
28901 
28902 
28903                [page_error.alm]
28904                page_fault:   Deleting main   memory at  AAAA, SCU
28905                TAG, due to parity errors.
28906 
28907 
28908 
28909      Stream:   BOS Typewriter (sounds beeper)
28910 
28911      Time:     While system is running.
28912 
28913      Meaning:  Due  to main memory  parity errors, the  system is
28914                automatically removing a page  of main memory from
28915                the  memory  in  SCU  TAG,  preventing further use
28916                during this bootload.
28917 
28918      Action:   Inform Field Engineering  personnel about possible
28919                problems with this SCU.
28920 
28921 
28922 
28923                [page_error.alm]
28924                page_fault:   device read not  complete DSKX_NN{S}
28925                DDDD
28926 
28927 
28928      Stream:   BOS Typewriter (Crashes system)
28929 
28930      Time:     While system is running.
28931 
28932      Meaning:  This message is used for program debugging only.
28933 
28934      Action:   Follow  normal recovery  procedures.  Contact  the
28935                system programming staff.
28936 
28937 
28938 
28939                [page_error.alm]
28940                page_fault:  fatal error at loc AAAA
28941 
28942 
28943      Stream:   BOS Typewriter (Crashes system)
28944 
28945      Time:     While system is running.
28946 
28947      Meaning:  This indicates a logic error in the supervisor, or
28948                CPU or memory hardware problems.
28949 
28950      Action:   Follow normal recovery procedures.
28951 
28952 
28953 
28954 
28955 
28956 page_fault                     500            08/03/23     MR12.7^L
28957 
28958 
28959 
28960 
28961                [page_error.alm]
28962                page_fault:  fatal error in done, ptp ZZZZ
28963 
28964 
28965      Stream:   BOS Typewriter (Crashes system)
28966 
28967      Time:     While system is running.
28968 
28969      Meaning:  While posting an I/O  completion, the system found
28970                a page  table pointer of  zero, or found  that the
28971                page  was not  out of  service.  This  indicates a
28972                logic  error in the  supervisor, or CPU  or memory
28973                hardware problems.
28974 
28975      Action:   Follow normal recovery procedures.
28976 
28977 
28978                [page_error.alm]
28979                page_fault:  mylock on global lock
28980 
28981 
28982      Stream:   BOS Typewriter (Crashes system)
28983 
28984      Time:     While system is running.
28985 
28986      Meaning:  When page_fault attempted to  lock the global page
28987                control  lock, it found  it already locked  to the
28988                same process.  This indicates a logic error in the
28989                supervisor, or CPU or memory hardware problems.
28990 
28991      Action:   Follow normal recovery procedures.
28992 
28993 
28994                [page_error.alm]
28995                page_fault:  nonfatal error at loc AAAA
28996 
28997 
28998      Stream:   BOS Typewriter.
28999 
29000      Time:     While system is running.
29001 
29002      Meaning:  This indicates a logic error in the supervisor, or
29003                CPU  or  memory  hardware  problems.   The  system
29004                attempts to keep running.
29005 
29006      Action:   No operator action is required.
29007 
29008 
29009                [page_error.alm]
29010                page_fault:  out of main memory
29011 
29012 
29013 
29014 page_fault                     501            08/03/23     MR12.7^L
29015 
29016 
29017      Stream:   BOS Typewriter (Crashes system)
29018 
29019      Time:     While system is running.
29020 
29021      Meaning:  The  page removal algorithm  was unable to  find a
29022                removable   page.   Incorrect   system  programmer
29023                action,  damage to  the AST,  or an  error in  the
29024                supervisor  or  the   hardware  could  cause  this
29025                symptom.
29026 
29027      Action:   Follow normal recovery procedures.
29028 
29029 
29030                [page_error.alm]
29031                page_fault:  Reverting page on DSKX_NN{S}
29032 
29033 
29034      Stream:   BOS Typewriter.
29035 
29036      Time:     While system is running.
29037 
29038      Meaning:  A  segment residing on  DSKX_NN{S} has had  one of
29039                its pages reverted to an  earlier copy of the same
29040                page.  The damaged switch is set.  This can happen
29041                due  to  device  error   or  main  memory  errors.
29042                Subsequent user  processes attempting to  use this
29043                segment will receive  an error indication.  Binary
29044                information  identifying  the  damaged  segment is
29045                encoded into this message for subsequent automatic
29046                processing.  The  pathname of the  damaged segment
29047                will appear in a  message in the answering service
29048                log,  bearing the  syserr log  sequence number  of
29049                this message, shortly after this message occurs.
29050 
29051      Action:   Attempt to identify the damaged segment and inform
29052                its owner.
29053 
29054 
29055                [page_error.alm]
29056                page_fault:  Zeroing page on DSKX_NN{S}
29057 
29058 
29059      Stream:   BOS Typewriter.
29060 
29061      Time:     While system is running.
29062 
29063      Meaning:  A segment residing on  DSKX_NN{S} has been damaged
29064                due to a device error.  The segment damaged switch
29065                is set and a page  of zeros is introduced into the
29066                segment.  Subsequent user  processes attempting to
29067                use this segment will receive an error indication.
29068                Binary information identifying the damaged segment
29069                is  encoded  into   this  message  for  subsequent
29070 
29071 
29072 page_fault                     502            08/03/23     MR12.7^L
29073 
29074 
29075                automatic processing.  The pathname of the damaged
29076                segment will appear in  a message in the answering
29077                service  log,  bearing   the  syserr_log  sequence
29078                number of this message, shortly after this message
29079                occurs.
29080 
29081      Action:   Attempt  to  identify  the  damaged  segment,  and
29082                inform its owner.
29083 
29084 
29085 
29086                [page_error.alm]
29087                page_synch:  dm_journal_seg_ inconsistent.
29088 
29089 
29090      Time:     While system is running.
29091 
29092      Stream:   BOS Typewriter (Crashes system)
29093 
29094      Meaning:  This indicates a logic error in the supervisor, or
29095                CPU or memory hardware problems.
29096 
29097      Action:   Follow normal recovery procedures.
29098 
29099 
29100                [page_error.alm]
29101                page_synch:     Out    of    free    entries    in
29102                dm_journal_seg_.
29103 
29104 
29105      Time:     While system is running.
29106 
29107      Stream:   BOS Typewriter (Crashes system)
29108 
29109      Meaning:  This indicates a logic error in the supervisor, or
29110                CPU or memory hardware problems.
29111 
29112      Action:   Follow normal recovery procedures.
29113 
29114 
29115                [pc.pl1.pmac]
29116                pc:   truncate_deposit_all call  on VTOCed  seg at
29117                ASTEP
29118 
29119 
29120      Stream:   BOS Typewriter (Crashes system)
29121 
29122      Time:     While system is running.
29123 
29124      Meaning:  A call to pc$truncate_deposit_all has been made on
29125                a segment for which this operation is not allowed.
29126                The AST  entry at ASTEP should have  a zero unique
29127                ID but it does not.   This indicates a logic error
29128 
29129 
29130 pc                             503            08/03/23     MR12.7^L
29131 
29132 
29133                in  the  supervisor,  or  CPU  or  memory hardware
29134                problems.  BOS Typewriter (Crashes system)es
29135 
29136      Action:   Follow normal recovery procedures.
29137 
29138 
29139                [pc.pl1.pmac]
29140                pc:  unprotected address DDDDD in DSKX_NN VTOCX
29141 
29142 
29143      Stream:   BOS Typewriter.
29144 
29145      Time:     While system is running.
29146 
29147      Meaning:  The disk address DDDDD  is not marked as protected
29148                in the record usage map  for the volume mounted on
29149                DSKX_NN.  This condition has been discovered while
29150                activating the segment with VTOC index VTOCX.  The
29151                segment's damaged switch is  turned on, and a page
29152                of  zeros  will  replace  the  bad  address.  This
29153                condition  may  be  symptomatic  of  disk or other
29154                hardware failure.
29155 
29156      Action:   Contact the system programming staff.
29157 
29158 
29159                [pc_abs.pl1.pmac]
29160                pc_abs$unwire_abs:  Attempt to unwire inconsistent
29161                CME at CMEP.
29162 
29163 
29164      Stream:   BOS Typewriter (Crashes system)
29165 
29166      Time:     While system is running.
29167 
29168      Meaning:  The core map entry for  the page being abs unwired
29169                did  not have the  abs_w flag on,  which indicates
29170                that it was properly  abs wired.  This indicates a
29171                logic  error in the  supervisor, or CPU  or memory
29172                hardware problems.
29173 
29174      Action:   Contact  the  system  programming  staff.   Follow
29175                normal recovery procedures.
29176 
29177 
29178 
29179                [pc_abs.pl1.pmac]
29180                pc_abs$unwire_abs:  Attempt to unwire inconsistent
29181                PTW at PTP.
29182 
29183 
29184      Stream:   BOS Typewriter (Crashes system)
29185 
29186 
29187 
29188 pc_abs$unwire_abs              504            08/03/23     MR12.7^L
29189 
29190 
29191      Time:     While system is running.
29192 
29193      Meaning:  A  page at  PTP, within  the range  of pages being
29194                unwired for,  was found to either not  be wired or
29195                no longer in memory.  This indicates a logic error
29196                in  the  supervisor,  or  CPU  or  memory hardware
29197                problems.
29198 
29199      Action:   Contact  the  system  programming  staff.   Follow
29200                normal recovery procedures.
29201 
29202 
29203 
29204                [pc_abs.pl1.pmac]
29205                pc_abs$unwire_abs:  Called with NULL astep.
29206 
29207 
29208      Stream:   BOS Typewriter (Crashes system)
29209 
29210      Time:     While system is running.
29211 
29212      Meaning:  This indicates a logic error in the supervisor, or
29213                CPU or memory hardware problems.
29214 
29215      Action:   Contact  the  system  programming  staff.   Follow
29216                normal recovery procedures.
29217 
29218 
29219 
29220                [pc_abs.pl1.pmac]
29221                pc_abs:  Parity error in I/O buffer.
29222 
29223 
29224      Stream:   BOS Typewriter (Crashes system)
29225 
29226      Time:     While system is running.
29227 
29228      Meaning:  This indicates a logic error in the supervisor, or
29229                CPU or memory hardware problems.
29230 
29231      Action:   Follow normal recovery procedures.
29232 
29233 
29234                [pc_deposit.pl1]
29235                pc_deposit:  Address  XXXXXX out of  paging region
29236                on dskX_NN{s}.
29237 
29238 
29239      Stream:   BOS Typewriter (Crashes system)
29240 
29241      Time:     While system is running.
29242 
29243 
29244 
29245 
29246 pc_deposit                     505            08/03/23     MR12.7^L
29247 
29248 
29249      Meaning:  An attempt was made  to return disk address XXXXXX
29250                on  device  dskX_NN{s}  to  the  free  pool.   The
29251                address is not in the paging region.
29252 
29253      Action:   Follow  normal  recovery  procedures.   It  may be
29254                necessary to  run the physical volume  salvager on
29255                the device.
29256 
29257 
29258 
29259                [pc_deposit.pl1]
29260                pc_deposit:   Deposit  in-use  address  XXXXXX  on
29261                dskX_NN{s}.
29262 
29263 
29264      Stream:   BOS Typewriter (sounds beeper)
29265 
29266      Time:     While system is running.
29267 
29268      Meaning:  An  attempt was made  to return address  XXXXXX on
29269                device dskX_NN{s} to the free record pool, but the
29270                address   was  already   marked  as   free.   This
29271                indicates  damage  to  control  structures  on the
29272                device.   This  damage  can   be  corrected  by  a
29273                physical volume salvage.
29274 
29275      Action:   Contact the system programming staff.
29276 
29277 
29278                [pc_deposit.pl1]
29279                pc_deposit:  Invalid address XXXXXX on dskX_NN{s}.
29280 
29281 
29282      Stream:   BOS Typewriter (Crashes system)
29283 
29284      Time:     While system is running.
29285 
29286      Meaning:  In attempting to deposit  address XXXXXX on device
29287                dskX_NN{s},  an  invalid  volume  map  offset  was
29288                computed.
29289 
29290      Action:   Follow  normal  recovery  procedures.   It  may be
29291                necessary to  run the physical volume  salvager on
29292                the device.
29293 
29294 
29295 
29296                [pc_deposit.pl1]
29297                pc_deposit:   Unrecoverable  I/O  error  on Volmap
29298                page M of dskX_NN{s}.  Addresses lost.
29299 
29300 
29301      Stream:   BOS Typewriter (sounds beeper)
29302 
29303 
29304 pc_deposit                     506            08/03/23     MR12.7^L
29305 
29306 
29307      Time:     While system is running.
29308 
29309      Meaning:  There was an unrecoverable I/O  error on a page of
29310                the  Volume Map,  which describes  free records of
29311                the  volume.  All  free records  described by that
29312                page have been lost.
29313 
29314      Action:   It may  be possible to recover  the lost addresses
29315                by a  volume salvage.  If  there is a  hard device
29316                error,  the  volume  salvage  will  fail.  In this
29317                case, it  will be necessary to  recover the volume
29318                onto a good pack.
29319 
29320 
29321 
29322                [ring_0_peek.pl1]
29323                PERSON.PROJ.T:  MESSAGE
29324 
29325 
29326      Stream:   BOS Typewriter (sounds beeper)
29327 
29328      Time:     While system is running.
29329 
29330      Meaning:  A privileged user has sent a message to be printed
29331                on the SYSERR console.
29332 
29333      Action:   Read the message and take appropriate action.
29334 
29335 
29336                [ring_0_peek.pl1]
29337                PERSON.PROJ.T:  NN words @ SSS|XXX
29338                XXX WWWWWWWWWWWW to YYYYYYYYYYYY
29339                XXX WWWWWWWWWWWW to YYYYYYYYYYYY
29340 
29341 
29342 
29343      Stream:   BOS Typewriter (sounds beeper)
29344 
29345      Time:     While system is running.
29346 
29347      Meaning:  A  privileged   user  has  patched   the  hardcore
29348                supervisor.
29349 
29350      Action:   No operator action is required.
29351 
29352 
29353                [prds_init.pl1]
29354                prds_init:         Invalid         size        for
29355                prds$fast_connect_code
29356 
29357 
29358      Stream:   BOS Typewriter (Crashes system)
29359 
29360 
29361 
29362 prds_init                      507            08/03/23     MR12.7^L
29363 
29364 
29365      Time:     System Intialization.
29366 
29367      Meaning:  There is an inconsistency between modules prds and
29368                fast_connect_init on the boot tape.  Specifically,
29369                the  amount of  space allocated  for fast  connect
29370                code in the  prds does not agree with  the size of
29371                the  code in  fast_connect_init.  The  most likely
29372                cause is  that one of  these modules is  not up to
29373                date.
29374 
29375      Action:   Contact  the system   programming staff._sa  A new
29376                boot  tape  must  be  generated  with  the  proper
29377                versions of modules prds and fast_connect_init.
29378 
29379 
29380 
29381                [priv_delete_vtoce.pl1]
29382                priv_delete_vtoce:    failed    to   lock   WWWWWW
29383                ERROR_MESSAGE
29384 
29385 
29386      Stream:   BOS Typewriter (Crashes system)
29387 
29388      Time:     While system is running.
29389 
29390      Meaning:  An attempt  to lock a directory  has failed.  This
29391                indicates a logic error  in the supervisor, or CPU
29392                or memory hardware problems.
29393 
29394      Action:   Follow normal recovery procedures.  $boot_tape
29395 
29396 
29397 
29398                [proc_int_handler.pl1]
29399                proc_int_handler:    Invalid    IPS   interrupt(s)
29400                IPS_BITS for USERNAME.
29401 
29402 
29403      Stream:   BOS Typewriter.
29404 
29405      Time:     While system is running.
29406 
29407      Meaning:  One or more undefined IPS messages as indicated by
29408                IPS_BITS  have been  sent to  user USERNAME.  They
29409                are ignored.
29410 
29411      Action:   Contact the system programming staff.
29412 
29413 
29414                [pxss.alm]
29415                pxss:  APT not locked
29416 
29417 
29418 
29419 
29420 pxss                           508            08/03/23     MR12.7^L
29421 
29422 
29423      Stream:   BOS Typewriter (Crashes system)
29424 
29425      Time:     While system is running.
29426 
29427      Meaning:  This indicates a logic error in the supervisor, or
29428                CPU or memory hardware problems.
29429 
29430      Action:   Follow normal recovery procedures.
29431 
29432 
29433 
29434                [pxss.alm]
29435                pxss:  APTE disdains all processors
29436 
29437 
29438 
29439      Stream:   BOS Typewriter (Crashes system)
29440 
29441      Time:     While system is running.
29442 
29443      Meaning:  This indicates a logic error in the supervisor, or
29444                CPU or  memory hardware problems.  "  There are no
29445                processors-required set for this APTE.
29446 
29447      Action:   Follow normal recovery procedures.
29448 
29449 
29450 
29451                [pxss.alm]
29452                pxss:  APTE not locked
29453 
29454 
29455 
29456      Stream:   BOS Typewriter (Crashes system)
29457 
29458      Time:     While system is running.
29459 
29460      Meaning:  This indicates a logic error in the supervisor, or
29461                CPU or memory hardware problems.
29462 
29463      Action:   Follow normal recovery procedures.
29464 
29465 
29466 
29467                [pxss.alm]
29468                pxss:  apte.state ^= ready
29469 
29470 
29471 
29472      Stream:   BOS Typewriter (Crashes system)
29473 
29474      Time:     While system is running.
29475 
29476 
29477 
29478 pxss                           509            08/03/23     MR12.7^L
29479 
29480 
29481      Meaning:  This indicates a logic error in the supervisor, or
29482                CPU or memory hardware problems.
29483 
29484      Action:   Follow normal recovery procedures.
29485 
29486 
29487 
29488                [pxss.alm]
29489                pxss:  empty_t APTE not stopped or empty
29490 
29491 
29492 
29493      Stream:   BOS Typewriter (Crashes system)
29494 
29495      Time:     While system is running.
29496 
29497      Meaning:  This indicates a logic error in the supervisor, or
29498                CPU or memory hardware problems.  " an attempt was
29499                made to clear  an APTE that of a  process that was
29500                neither " stopped nor empty.
29501 
29502      Action:   Follow normal recovery procedures.
29503 
29504 
29505 
29506                [pxss.alm]
29507                pxss:  freeing unknown stack_0
29508 
29509 
29510 
29511      Stream:   BOS Typewriter (Crashes system)
29512 
29513      Time:     While system is running.
29514 
29515      Meaning:  This indicates a logic error in the supervisor, or
29516                CPU  or memory  hardware problems.   " the stack_0
29517                being returned  could not be found in  the list of
29518                stack_0s.
29519 
29520      Action:   Follow normal recovery procedures.
29521 
29522 
29523 
29524                [pxss.alm]
29525                pxss:  ITT overflows
29526 
29527 
29528 
29529      Stream:   BOS Typewriter (Crashes system)
29530 
29531      Time:     While system is running.
29532 
29533 
29534 
29535 
29536 pxss                           510            08/03/23     MR12.7^L
29537 
29538 
29539      Meaning:  This indicates a logic error in the supervisor, or
29540                CPU or memory hardware problems.
29541 
29542      Action:   Follow normal recovery procedures.
29543 
29544 
29545 
29546                [pxss.alm]
29547                pxss:  lock_stack_queue stac failed
29548 
29549 
29550 
29551      Stream:   BOS Typewriter (Crashes system)
29552 
29553      Time:     While system is running.
29554 
29555      Meaning:  This indicates a logic error in the supervisor, or
29556                CPU or memory hardware problems.  " This indicates
29557                a hardware error.
29558 
29559      Action:   Follow normal recovery procedures.
29560 
29561 
29562 
29563                [pxss.alm]
29564                pxss:  mylock on stack queue
29565 
29566 
29567 
29568      Stream:   BOS Typewriter (Crashes system)
29569 
29570      Time:     While system is running.
29571 
29572      Meaning:  This indicates a logic error in the supervisor, or
29573                CPU or memory hardware problems.
29574 
29575      Action:   Follow normal recovery procedures.
29576 
29577 
29578 
29579                [pxss.alm]
29580                pxss:  no available stack_0
29581 
29582 
29583 
29584      Stream:   BOS Typewriter (Crashes system)
29585 
29586      Time:     While system is running.
29587 
29588      Meaning:  This indicates a logic error in the supervisor, or
29589                CPU or memory hardware problems.
29590 
29591      Action:   Follow normal recovery procedures.
29592 
29593 
29594 pxss                           511            08/03/23     MR12.7^L
29595 
29596 
29597 
29598 
29599                [pxss.alm]
29600                pxss:  no stack_0 sdw
29601 
29602 
29603 
29604      Stream:   BOS Typewriter (Crashes system)
29605 
29606      Time:     While system is running.
29607 
29608      Meaning:  This indicates a logic error in the supervisor, or
29609                CPU or memory hardware problems.
29610 
29611      Action:   Follow normal recovery procedures.
29612 
29613 
29614 
29615                [pxss.alm]
29616                pxss:  No term_processid
29617 
29618 
29619 
29620      Stream:   BOS Typewriter (Crashes system)
29621 
29622      Time:     While system is running.
29623 
29624      Meaning:  This indicates a logic error in the supervisor, or
29625                CPU or  memory hardware problems.  "  As a process
29626                was  about to  indicate its  demise to  the master
29627                process, " it discovered,  to its chagrin, that it
29628                had forgotten who that was.
29629 
29630      Action:   Follow normal recovery procedures.
29631 
29632 
29633 
29634                [pxss.alm]
29635                pxss:    notify  time   out:   event=ZZZZZZZZZZZZ.
29636                During init/shutdown.
29637 
29638 
29639      Stream:   BOS Typewriter.
29640 
29641      Time:     System Intialization.
29642 
29643      Meaning:  A  hardcore  event  has   not  occurred  within  a
29644                reasonable  time during  system initialization  or
29645                shutdown.  This may be due to hardware problems or
29646                to  a programming  error.  The  system attempts to
29647                continue initialization or shutdown.
29648 
29649 
29650 
29651 
29652 pxss                           512            08/03/23     MR12.7^L
29653 
29654 
29655      Action:   If   this   message   persists,   contact   system
29656                programmers.
29657 
29658 
29659                [pxss.alm]
29660                pxss:    notify  time   out:   event=ZZZZZZZZZZZZ,
29661                pid=XXXXXXXXXXXX
29662 
29663 
29664      Stream:   BOS Typewriter.
29665 
29666      Time:     While system is running.
29667 
29668      Meaning:  A  hardcore  event  has   not  occurred  within  a
29669                reasonable  time.   This  may  be  due to hardware
29670                problems  or to  a programming  error.  The system
29671                attempts to continue operation.
29672 
29673      Action:   If   this   message   persists,   contact   system
29674                programmers.
29675 
29676 
29677                [pxss.alm]
29678                pxss:  sprq already on prds
29679 
29680 
29681 
29682      Stream:   BOS Typewriter (Crashes system)
29683 
29684      Time:     While system is running.
29685 
29686      Meaning:  This indicates a logic error in the supervisor, or
29687                CPU or memory hardware problems.
29688 
29689      Action:   Follow normal recovery procedures.
29690 
29691 
29692 
29693                [pxss.alm]
29694                pxss:  stack_0 page 0 wired
29695 
29696 
29697 
29698      Stream:   BOS Typewriter (Crashes system)
29699 
29700      Time:     While system is running.
29701 
29702      Meaning:  This indicates a logic error in the supervisor, or
29703                CPU  or  memory   hardware  problems.   "  process
29704                loading was  about to wire  the first page  of the
29705                ring 0 stack when " it discovered that it had been
29706                beaten to the punch.
29707 
29708 
29709 
29710 pxss                           513            08/03/23     MR12.7^L
29711 
29712 
29713      Action:   Follow normal recovery procedures.
29714 
29715 
29716 
29717                [pxss.alm]
29718                pxss:  Stop returned from getwork
29719 
29720 
29721 
29722      Stream:   BOS Typewriter (Crashes system)
29723 
29724      Time:     While system is running.
29725 
29726      Meaning:  This indicates a logic error in the supervisor, or
29727                CPU or memory hardware problems.
29728 
29729      Action:   Follow normal recovery procedures.
29730 
29731 
29732 
29733                [pxss.alm]
29734                pxss:  subroutine_save stack overflow
29735 
29736 
29737 
29738      Stream:   BOS Typewriter (Crashes system)
29739 
29740      Time:     While system is running.
29741 
29742      Meaning:  This indicates a logic error in the supervisor, or
29743                CPU or memory hardware problems.
29744 
29745      Action:   Follow normal recovery procedures.
29746 
29747 
29748 
29749                [pxss.alm]
29750                pxss:   System  default  procs  required  reset to
29751                ABCDEFGH
29752 
29753 
29754      Stream:   BOS Typewriter (sounds beeper)
29755 
29756      Time:     During CPU deconfiguration.
29757 
29758      Meaning:  Due to the deletion of a CPU, there were no online
29759                CPUs remaining in the  default set of CPUs.  These
29760                CPUs are the only CPUs  on which processes can run
29761                which  have not  requested to  be run  on specific
29762                CPUs.  The default set of CPUs has been changed to
29763                all online CPUs.
29764 
29765      Action:   Contact the system programming staff._sa
29766 
29767 
29768 pxss                           514            08/03/23     MR12.7^L
29769 
29770 
29771 
29772 
29773                [pxss.alm]
29774                pxss:  thread_him_in already threaded
29775 
29776 
29777 
29778      Stream:   BOS Typewriter (Crashes system)
29779 
29780      Time:     While system is running.
29781 
29782      Meaning:  This indicates a logic error in the supervisor, or
29783                CPU or memory hardware problems.
29784 
29785      Action:   Follow normal recovery procedures.
29786 
29787 
29788 
29789                [pxss.alm]
29790                pxss:  thread_him_in x0 zero
29791 
29792 
29793 
29794      Stream:   BOS Typewriter (Crashes system)
29795 
29796      Time:     While system is running.
29797 
29798      Meaning:  This indicates a logic error in the supervisor, or
29799                CPU or memory hardware problems.
29800 
29801      Action:   Follow normal recovery procedures.
29802 
29803 
29804 
29805                [pxss.alm]
29806                pxss:  thread_him_in x1 zero
29807 
29808 
29809 
29810      Stream:   BOS Typewriter (Crashes system)
29811 
29812      Time:     While system is running.
29813 
29814      Meaning:  This indicates a logic error in the supervisor, or
29815                CPU or memory hardware problems.
29816 
29817      Action:   Follow normal recovery procedures.
29818 
29819 
29820 
29821                [pxss.alm]
29822                pxss:  thread_him_in x4 zero
29823 
29824 
29825 
29826 pxss                           515            08/03/23     MR12.7^L
29827 
29828 
29829      Stream:   BOS Typewriter (Crashes system)
29830 
29831      Time:     While system is running.
29832 
29833      Meaning:  This indicates a logic error in the supervisor, or
29834                CPU or memory hardware problems.
29835 
29836      Action:   Follow normal recovery procedures.
29837 
29838 
29839 
29840                [pxss.alm]
29841                pxss:  thread_him_in x4->apte.fp ^= x1
29842 
29843 
29844 
29845      Stream:   BOS Typewriter (Crashes system)
29846 
29847      Time:     While system is running.
29848 
29849      Meaning:  This indicates a logic error in the supervisor, or
29850                CPU or memory hardware problems.
29851 
29852      Action:   Follow normal recovery procedures.
29853 
29854 
29855 
29856                [pxss.alm]
29857                pxss:  unlock apt read lock bad count
29858 
29859 
29860 
29861      Stream:   BOS Typewriter (Crashes system)
29862 
29863      Time:     While system is running.
29864 
29865      Meaning:  This indicates a logic error in the supervisor, or
29866                CPU or memory hardware problems.
29867 
29868      Action:   Follow normal recovery procedures.
29869 
29870 
29871 
29872                [pxss.alm]
29873                pxss:  UNLOCK_bp not locked
29874 
29875 
29876 
29877      Stream:   BOS Typewriter (Crashes system)
29878 
29879      Time:     While system is running.
29880 
29881 
29882 
29883 
29884 pxss                           516            08/03/23     MR12.7^L
29885 
29886 
29887      Meaning:  This indicates a logic error in the supervisor, or
29888                CPU or memory hardware problems.
29889 
29890      Action:   Follow normal recovery procedures.
29891 
29892 
29893 
29894                [pxss.alm]
29895                pxss:  unlock_stack_queue not my lock
29896 
29897 
29898 
29899      Stream:   BOS Typewriter (Crashes system)
29900 
29901      Time:     While system is running.
29902 
29903      Meaning:  This indicates a logic error in the supervisor, or
29904                CPU or memory hardware problems.
29905 
29906      Action:   Follow normal recovery procedures.
29907 
29908 
29909 
29910                [pxss.alm]
29911                pxss:  unlock_stack_queue stacq failed
29912 
29913 
29914 
29915      Stream:   BOS Typewriter (Crashes system)
29916 
29917      Time:     While system is running.
29918 
29919      Meaning:  This indicates a logic error in the supervisor, or
29920                CPU or memory hardware problems.  " This indicates
29921                a hardware error.
29922 
29923      Action:   Follow normal recovery procedures.
29924 
29925 
29926 
29927                [pxss.alm]
29928                pxss:  UNLOCK_X2 not locked
29929 
29930 
29931 
29932      Stream:   BOS Typewriter (Crashes system)
29933 
29934      Time:     While system is running.
29935 
29936      Meaning:  This indicates a logic error in the supervisor, or
29937                CPU or memory hardware problems.
29938 
29939      Action:   Follow normal recovery procedures.
29940 
29941 
29942 pxss                           517            08/03/23     MR12.7^L
29943 
29944 
29945 
29946 
29947                [pxss.alm]
29948                pxss:  UNLOCK_x3 not locked
29949 
29950 
29951 
29952      Stream:   BOS Typewriter (Crashes system)
29953 
29954      Time:     While system is running.
29955 
29956      Meaning:  This indicates a logic error in the supervisor, or
29957                CPU or memory hardware problems.
29958 
29959      Action:   Follow normal recovery procedures.
29960 
29961 
29962 
29963                [pxss.alm]
29964                pxss:  untenable blocked APTE
29965 
29966 
29967 
29968      Stream:   BOS Typewriter (Crashes system)
29969 
29970      Time:     While system is running.
29971 
29972      Meaning:  This indicates a logic error in the supervisor, or
29973                CPU or memory hardware problems.
29974 
29975      Action:   Follow normal recovery procedures.
29976 
29977 
29978 
29979                [pxss.alm]
29980                pxss:  untenable empty APTE
29981 
29982 
29983 
29984      Stream:   BOS Typewriter (Crashes system)
29985 
29986      Time:     While system is running.
29987 
29988      Meaning:  This indicates a logic error in the supervisor, or
29989                CPU or memory hardware problems.
29990 
29991      Action:   Follow normal recovery procedures.
29992 
29993 
29994 
29995                [pxss.alm]
29996                pxss:  untenable stopped APTE
29997 
29998 
29999 
30000 pxss                           518            08/03/23     MR12.7^L
30001 
30002 
30003      Stream:   BOS Typewriter (Crashes system)
30004 
30005      Time:     While system is running.
30006 
30007      Meaning:  This indicates a logic error in the supervisor, or
30008                CPU or memory hardware problems.
30009 
30010      Action:   Follow normal recovery procedures.
30011 
30012 
30013 
30014                [pxss.alm]
30015                pxss:  unthread null back ptr
30016 
30017 
30018 
30019      Stream:   BOS Typewriter (Crashes system)
30020 
30021      Time:     While system is running.
30022 
30023      Meaning:  This indicates a logic error in the supervisor, or
30024                CPU or memory hardware problems.
30025 
30026      Action:   Follow normal recovery procedures.
30027 
30028 
30029 
30030                [pxss.alm]
30031                pxss:  unthread null cur.fp
30032 
30033 
30034 
30035      Stream:   BOS Typewriter (Crashes system)
30036 
30037      Time:     While system is running.
30038 
30039      Meaning:  This indicates a logic error in the supervisor, or
30040                CPU or memory hardware problems.
30041 
30042      Action:   Follow normal recovery procedures.
30043 
30044 
30045 
30046                [pxss.alm]
30047                pxss:  unthread prev.fp ^= cur
30048 
30049 
30050 
30051      Stream:   BOS Typewriter (Crashes system)
30052 
30053      Time:     While system is running.
30054 
30055 
30056 
30057 
30058 pxss                           519            08/03/23     MR12.7^L
30059 
30060 
30061      Meaning:  This indicates a logic error in the supervisor, or
30062                CPU or memory hardware problems.
30063 
30064      Action:   Follow normal recovery procedures.
30065 
30066 
30067 
30068                [pxss.alm]
30069                pxss:  write_to_read bad lock count
30070 
30071 
30072 
30073      Stream:   BOS Typewriter (Crashes system)
30074 
30075      Time:     While system is running.
30076 
30077      Meaning:  This indicates a logic error in the supervisor, or
30078                CPU or memory hardware problems.
30079 
30080      Action:   Follow normal recovery procedures.
30081 
30082 
30083 
30084                [pxss.alm]
30085                pxss:  write_to_read ldac failed
30086 
30087 
30088 
30089      Stream:   BOS Typewriter (Crashes system)
30090 
30091      Time:     While system is running.
30092 
30093      Meaning:  This indicates a logic error in the supervisor, or
30094                CPU or memory hardware problems.  " This indicates
30095                a hardware error.
30096 
30097      Action:   Follow normal recovery procedures.
30098 
30099 
30100 
30101                [rcp_control_.pl1]
30102                RCP:  Acquired DEVICE from storage system.
30103 
30104 
30105      Stream:   BOS Typewriter.
30106 
30107      Time:     In response to an operator command.
30108 
30109      Meaning:  The operator has  used the set_drive_usage command
30110                to make DRIVE an IO drive.
30111 
30112      Action:   No operator action is required.
30113 
30114 
30115 
30116 RCP                            520            08/03/23     MR12.7^L
30117 
30118 
30119 
30120 
30121                [rcp_control_.pl1]
30122                RCP:  Added device DEVICE
30123 
30124 
30125      Stream:   BOS Typewriter.
30126 
30127      Time:     In response to an operator command.
30128 
30129      Meaning:  The operator has added a  user I/O disk drive with
30130                adddev.
30131 
30132      Action:   No operator action is required.
30133 
30134 
30135                [rcp_reserve_.pl1]
30136                RCP:   An error  locking rcpd  for reservation for
30137                RESERVED_FOR by RESERVER [if they're not the same]
30138                (id=RES_ID).
30139 
30140 
30141 
30142      Stream:   Logged in SYSERR log.
30143 
30144      Time:     While system is running.
30145 
30146      Meaning:  An  error was  found in  the locking  data for the
30147                resource.
30148 
30149      Action:   No operator action is required.
30150 
30151 
30152                [rcp_control_.pl1]
30153                RCP:  Assigned DEVICE to PERSON.PROJ.T
30154 
30155 
30156      Stream:   Logged in SYSERR log.
30157 
30158      Time:     While system is running.
30159 
30160      Meaning:  DEVICE has been assigned to a user process.
30161 
30162      Action:   No operator action is required.
30163 
30164 
30165                [rcp_ioi_attach_.pl1]
30166                RCP:  Attached DEVICE for PERSON.PROJ.T
30167 
30168 
30169      Stream:   BOS Typewriter.
30170 
30171      Time:     While system is running.
30172 
30173 
30174 RCP                            521            08/03/23     MR12.7^L
30175 
30176 
30177      Meaning:  The  device DEVICE has  been attached by  the user
30178                process.
30179 
30180      Action:   No operator action is required.
30181 
30182 
30183                [rcp_disk_.pl1]
30184                RCP:  Authenticate DRIVE for PERSON.PROJ.T.
30185                RCP:  It has LABEL_TYPE label NAME.
30186               (RCP:  All N subvolume labels are unreadable.)
30187               (RCP:  VOL_NAME on subvol  a, VOL_NAME on subvol b,
30188                VOL_NAME on subvol c.)
30189               (RCP:  User requested volume DIFFERENT_NAME.)
30190 
30191 
30192 
30193      Stream:   BOS Typewriter (sounds beeper)
30194 
30195      Time:     While system is running.
30196 
30197      Meaning:  The operator must verify  that the correct pack is
30198                mounted on  DRIVE.  If the  DIFFERENT_NAME message
30199                indicates  that the  label on  the pack  (NAME) is
30200                different  from the   user's request  then special
30201                instructions from the system administrator must be
30202                followed.
30203 
30204      Action:   If  the pack  is correct   then use  the "x  auth"
30205                function to input the DRIVE and the authentication
30206                code which matches  LABEL_TYPE:  "ss" for "Storage
30207                System"  or  "copy  of  Storage  System"; "io" for
30208                "IO";  "urd"   for  "UnReaDable";  or   "urg"  for
30209                "UnReGistered".  If the wrong pack is mounted then
30210                use the authentication code "no".
30211 
30212 
30213 
30214                [rcp_tape_.pl1]
30215                RCP:  Authenticate DRIVE.  It has LABEL_TYPE label
30216                LABEL and is UNREGISTERED.
30217 
30218 
30219      Stream:   BOS Typewriter (sounds beeper)
30220 
30221      Time:     While system is running.
30222 
30223      Meaning:  The tape volume requested is not a registered tape
30224                volume.   In addittion,  the system  may not  have
30225                been able  to determine that the  volume loaded is
30226                in  fact the one  requested.  The label  read from
30227                the tape on DEVICE was  of type LABEL_TYPE and was
30228                LABEL.  If LABEL is "(Manual Halt)" this indicates
30229                that  the tape  drive was  found in  standby while
30230 
30231 
30232 RCP                            522            08/03/23     MR12.7^L
30233 
30234 
30235                trying    to   read/verify    the   label.     Any
30236                non-printable   characters   in   the   label  are
30237                represented by ".".
30238 
30239      Action:   If the  volume is correct and is  to be registered
30240                to the user requesting  this attachment use the "x
30241                auth" function  to input the DRIVE  number and the
30242                authentication code  on the tape volume,  or "***"
30243                if   there   is   no   authentication   code.   If
30244                authentication  was  requested  due  to  the drive
30245                being  in  standby,  the  tape  should  be rewound
30246                manually  and  rereadied  manually  and  the above
30247                procedure for authentication followed.
30248 
30249 
30250 
30251                [rcp_tape_.pl1]
30252                RCP:  Authenticate DRIVE.  It has LABEL_TYPE label
30253                LABEL.
30254 
30255 
30256      Stream:   BOS Typewriter (sounds beeper)
30257 
30258      Time:     While system is running.
30259 
30260      Meaning:  The  system cannot  determine that  the volume  on
30261                DRIVE  is the  one requested.   The operator  must
30262                authenticate the volume.  The  label read from the
30263                tape  on DEVICE  was  of  type LABEL_TYPE  and was
30264                LABEL.  If LABEL is "(Manual Halt)" this indicates
30265                that  the tape  drive was  found in  standby while
30266                trying to read/verify the label.  If LABEL_TYPE is
30267                ANSI  and   LABEL  is  "<label>   (with  non-blank
30268                accessibility code)" this indicates that the label
30269                is an ANSI label with a non-blank character in the
30270                accessibility field, the operator must consult the
30271                site  standards  for   authenticating  such  tapes
30272                before    doing     the    authentication.     Any
30273                non-printable   characters   in   the   label  are
30274                represented by ".".
30275 
30276      Action:   If  the volume  is correct  then use  the "x auth"
30277                function  to  input  the   DRIVE  number  and  the
30278                authentication code  on the tape volume,  or "***"
30279                if   there   is   no   authentication   code.   If
30280                authentication  was  requested  due  to  the drive
30281                being  in  standby,  the  tape  should  be rewound
30282                manually  and  rereadied  manually  and  the above
30283                procedure for authentication followed.
30284 
30285 
30286 
30287                [rcp_tape_.pl1]
30288 
30289 
30290 RCP                            523            08/03/23     MR12.7^L
30291 
30292 
30293                RCP:   Authentication  code  for  DRIVE  does  not
30294                match.
30295 
30296 
30297      Stream:   BOS Typewriter.
30298 
30299      Time:     While system is running.
30300 
30301      Meaning:  The  authentication code  typed for  the volume on
30302                DRIVE  does  no  match  the  user specified volume
30303                name.
30304 
30305      Action:   No operator action is required.
30306 
30307 
30308                [rcp_disk_.pl1]
30309                RCP:  Authentication denied for DRIVE
30310 
30311 
30312      Stream:   BOS Typewriter (sounds beeper)
30313 
30314      Time:     While system is running.
30315 
30316      Meaning:  The operator has denied authentication for DRIVE.
30317 
30318      Action:   No operator action is required.
30319 
30320 
30321                [rcp_ring1_init_.pl1]
30322                RCP:  Auto  Registration is enabled  without Exact
30323                Authentication  required.   This   could  lead  to
30324                errors in automatic registration of volumes.
30325 
30326 
30327      Stream:   BOS Typewriter (sounds beeper)
30328 
30329      Time:     While system is running.
30330 
30331      Meaning:  This is a warning.  If the system is operated with
30332                auto registration enabled and exact authentication
30333                of tape volumes is not required, there is a better
30334                chance of errors occurring  in the registration of
30335                tape volumes.  Again, it is very important to make
30336                sure the volume mounted is  the proper one for the
30337                request if auto registration is enabled.
30338 
30339      Action:   No operator action is required.
30340 
30341 
30342                [rcp_cancel_id_.pl1]
30343                RCP:    Cancelled   device   devX_MM   for  GRP_ID
30344                (id=RES_ID)
30345 
30346 
30347 
30348 RCP                            524            08/03/23     MR12.7^L
30349 
30350 
30351      Stream:   Logged in SYSERR log.
30352 
30353      Time:     While system is running.
30354 
30355      Meaning:  A  device reservation  has been  cancelled by  the
30356                operator, the absentee manager or the Initializer.
30357 
30358      Action:   No operator action is required.
30359 
30360 
30361                [rcp_reserve_.pl1]
30362                RCP:    Cancelled   device   devX_MM   for  GRP_ID
30363                (id=RES_ID)
30364 
30365 
30366      Stream:   Logged in SYSERR log.
30367 
30368      Time:     While system is running.
30369 
30370      Meaning:  The  reservation  for  the  named  device has been
30371                cancelled.
30372 
30373      Action:   No operator action is required.
30374 
30375 
30376                [rcp_cancel_id_.pl1]
30377                RCP:   Cancelled  volume  volume_name  for  GRP_ID
30378                (id=RES_ID)
30379 
30380 
30381      Stream:   Logged in SYSERR log.
30382 
30383      Time:     While system is running.
30384 
30385      Meaning:  A  volume reservation  has been  cancelled by  the
30386                operator, the absentee manager or the Initializer.
30387 
30388      Action:   No operator action is required.
30389 
30390 
30391                [rcp_reserve_.pl1]
30392                RCP:   Cancelled  volume  volume_name  for  GRP_ID
30393                (id=RES_ID)
30394 
30395 
30396      Stream:   Logged in SYSERR log.
30397 
30398      Time:     While system is running.
30399 
30400      Meaning:  The  reservation  for  the  named  volume has been
30401                cancelled.
30402 
30403      Action:   No operator action is required.
30404 
30405 
30406 RCP                            525            08/03/23     MR12.7^L
30407 
30408 
30409 
30410 
30411                [rcprm_journalize_.pl1]
30412                RCP:  Cannot initiate journal PATH.  ERROR_CODE
30413 
30414 
30415      Stream:   BOS Typewriter (sounds beeper)
30416 
30417      Time:     While system is running.
30418 
30419      Meaning:  The  RCP journal  at PATH  has been  damaged or is
30420                missing.
30421 
30422      Action:   Contact the system programming staff.
30423 
30424 
30425                [wdx.pl1]
30426                RCP:   Check mount  of logical  volume LVNAME  for
30427                PROCESSNAME PVNAME1(DRIVE1) ...
30428 
30429 
30430 
30431      Stream:   BOS Typewriter (sounds beeper)
30432 
30433      Time:     While system is running.
30434 
30435      Meaning:  A  user  (PROCESSNAME)  previously  requested  the
30436                attachment  of logical  volume LVNAME.   The mount
30437                has  not been  accomplished in  a 4  minutes.  All
30438                required physical volumes  are specified (PVNAMEi,
30439                DRIVEi).
30440 
30441      Action:   Mount  the required   physical volumes,  using the
30442                add_vol  command to  indicate when  each has  been
30443                made ready.   The user process will  continue when
30444                the last  volume has been mounted.   If the volume
30445                cannot  be  mounted,  use  the  del_lv  command to
30446                indicate  this  fact,  and  the  user process will
30447                receive an error indication.
30448 
30449 
30450 
30451                [rcp_mount_timer_.pl1]
30452                RCP:  Check Mount of REELID {for writing} on DRIVE
30453                for PERSON.PROJ.T
30454 
30455 
30456      Stream:   BOS Typewriter (sounds beeper)
30457 
30458      Time:     While system is running.
30459 
30460      Meaning:  The  request to  mount tape  reel REELID  has been
30461                unsatisfied for over 4 minutes.
30462 
30463 
30464 RCP                            526            08/03/23     MR12.7^L
30465 
30466 
30467      Action:   Mount the reel or use  "x deny" to inform the user
30468                that the reel cannot be mounted.
30469 
30470 
30471                [rcp_control_.pl1]
30472                RCP:  Consigned DEVICE to storage system.
30473 
30474 
30475      Stream:   BOS Typewriter.
30476 
30477      Time:     In response to an operator command.
30478 
30479      Meaning:  The operator has  used the set_drive_usage command
30480                to make DRIVE a storage system drive.
30481 
30482      Action:   No operator action is required.
30483 
30484 
30485                [rcp_ring1_init_.pl1]
30486                RCP:  Created DIR with default access.
30487 
30488 
30489      Stream:   BOS Typewriter (sounds beeper)
30490 
30491      Time:     While system is running.
30492 
30493      Meaning:  The directory  (usually >system_control_1>rcp) was
30494                created because  it was not found  at startup.  It
30495                may have been destroyed  in a crash.  This message
30496                is  normal  during  a  cold  boot  of  the Multics
30497                hierarchy.
30498 
30499      Action:   If users  other than system processes  should have
30500                access to the  directory, the system administrator
30501                must set the ACL appropriately.
30502 
30503 
30504 
30505                [rcp_ring1_init_.pl1]
30506                RCP:  Created DIR>DEVICE.acs with default access.
30507 
30508 
30509      Stream:   BOS Typewriter (sounds beeper)
30510 
30511      Time:     While system is running.
30512 
30513      Meaning:  The system  has created an access  control segment
30514                for DEVICE  because one was not  found at startup.
30515                It  may  have  been  destroyed  in  a crash.  This
30516                message is normal during the first use of a device
30517                on the system, and at cold boot.
30518 
30519 
30520 
30521 
30522 RCP                            527            08/03/23     MR12.7^L
30523 
30524 
30525      Action:   If users  other than system processes  should have
30526                access  to DEVICE,  the system  administrator must
30527                set the ACL of DEVICE.acs appropriately.
30528 
30529 
30530 
30531                [rcprm_journalize_.pl1]
30532                RCP:  Creating DIRNAME>rcprm.journal
30533 
30534 
30535      Stream:   BOS Typewriter.
30536 
30537      Time:     While system is running.
30538 
30539      Meaning:  Printed  by  RCP  Resource  Management  when first
30540                enabled.
30541 
30542      Action:   No operator action is required.
30543 
30544 
30545                [rcp_control_.pl1]
30546                RCP:  Deleted device DEVICE
30547 
30548 
30549      Stream:   BOS Typewriter.
30550 
30551      Time:     In response to an operator command.
30552 
30553      Meaning:  The operator has deleted  user I/O disk DRIVE with
30554                deldev.
30555 
30556      Action:   No operator action is required.
30557 
30558 
30559                [rcp_detach_.pl1]
30560                RCP:  Detached DEVICE from PERSON.PROJ.T
30561 
30562 
30563      Stream:   BOS Typewriter.
30564 
30565      Time:     While system is running.
30566 
30567      Meaning:  The user of DEVICE has detached it.
30568 
30569      Action:   If DEVICE  is a disk drive, demount  the volume on
30570                it and store it in the library.
30571 
30572 
30573                [rcp_control_.pl1]
30574                RCP:  DEVICE  is not operational and  has not been
30575                added.
30576 
30577 
30578 
30579 
30580 RCP                            528            08/03/23     MR12.7^L
30581 
30582 
30583      Stream:   BOS Typewriter.
30584 
30585      Time:     In response to an operator command.
30586 
30587      Meaning:  An  attempt  was  made  to  add  a non-operational
30588                device with adddev.
30589 
30590      Action:   Ready the device and add it again.
30591 
30592 
30593                [rcp_ring1_init_.pl1]
30594                RCP:      Error    creating     ACS    DEVICE.acs:
30595                ERROR_MESSAGE
30596 
30597 
30598      Stream:   BOS Typewriter (sounds beeper)
30599 
30600      Time:     While system is running.
30601 
30602      Meaning:  The system was unable  to create an access control
30603                segment  for  DEVICE.   No  user  will  be able to
30604                attach it.
30605 
30606      Action:   Contact the system programming staff.
30607 
30608 
30609                [rcp_ring1_init_.pl1]
30610                RCP:  Error creating DIR:  ERROR_MESSAGE
30611 
30612 
30613      Stream:   BOS Typewriter (sounds beeper)
30614 
30615      Time:     While system is running.
30616 
30617      Meaning:  The system was unable to create the ACS directory.
30618                It  should be  >system_control_1>acs.  The  system
30619                may be unable to use I/O devices.
30620 
30621      Action:   Contact the system programming staff.
30622 
30623 
30624                [rcprm_journalize_.pl1]
30625                RCP:   Error  during  registry  reconstruction for
30626                USERID.   RCP:  Could not  OPERATION RESOURCE_TYPE
30627                RESOURCE_NAME {may occur multiple times} RCP:  End
30628                of reconstruction operation.
30629 
30630 
30631 
30632      Stream:   BOS Typewriter (sounds beeper)
30633 
30634 
30635 
30636 
30637 
30638 RCP                            529            08/03/23     MR12.7^L
30639 
30640 
30641      Time:     This  message should  only occur  during a special
30642                session.   The second  message in  the series  may
30643                occur multiple times.
30644 
30645      Meaning:  The  specified  RCP  Resource  Management activity
30646                failed  to be  re-performed during  an attempt  to
30647                reconstruct   the   registries   by   the   System
30648                Administrator.   This indicates  a logic  error in
30649                the   supervisor,  or   CPU  or   memory  hardware
30650                problems.
30651 
30652      Action:   Contact the system programming staff._sa
30653 
30654 
30655                [rcp_ring1_init_.pl1]
30656                RCP:  Error expanding DIR:  ERROR_MESSAGE
30657 
30658 
30659      Stream:   BOS Typewriter (sounds beeper)
30660 
30661      Time:     While system is running.
30662 
30663      Meaning:  The  pathname of  the acs  directory is incorrect.
30664                It   should    be   >system_control_1>acs.    This
30665                indicates a logic error  in the supervisor, or CPU
30666                or  memory hardware  problems.  The  system may be
30667                unable to use I/O devices.
30668 
30669      Action:   Contact the system programming staff.
30670 
30671 
30672                [rcp_ring1_init_.pl1]
30673                RCP:   Error  setting  max  length  of DEVICE.acs:
30674                ERROR_MESSAGE
30675 
30676 
30677      Stream:   BOS Typewriter (sounds beeper)
30678 
30679      Time:     While system is running.
30680 
30681      Meaning:  This indicates a logic error in the supervisor, or
30682                CPU or memory hardware problems.
30683 
30684      Action:   Contact the system programming staff.
30685 
30686 
30687                [rcp_detach_.pl1]
30688                RCP:  Errors (DEVICE) = NN
30689 
30690 
30691      Stream:   BOS Typewriter.
30692 
30693      Time:     While system is running.
30694 
30695 
30696 RCP                            530            08/03/23     MR12.7^L
30697 
30698 
30699      Meaning:  When  DEVICE was  detached, its  error counter was
30700                nonzero.  This may be due to a problem with DEVICE
30701                or with the user program.
30702 
30703      Action:   No operator action is required.
30704 
30705 
30706                [rcp_detach_.pl1]
30707                RCP:  Errors (DEVICE, volume VOL) = NN
30708 
30709 
30710      Stream:   BOS Typewriter.
30711 
30712      Time:     While system is running.
30713 
30714      Meaning:  When  DEVICE was  detached, its  error counter was
30715                nonzero.  The errors may be  due to a problem with
30716                DEVICE, with  the volume VOLUME, or  with the user
30717                program.
30718 
30719      Action:   No operator action is required.
30720 
30721 
30722                [rcp_detach_.pl1]
30723                RCP:  Force Detached DEVICE from PERSON.PROJ.T
30724 
30725 
30726      Stream:   BOS Typewriter.
30727 
30728      Time:     While system is running.
30729 
30730      Meaning:  The user PERSON.PROJ.T  has terminated abnormally.
30731                This  may  be  due  to  an  automatic  logout or a
30732                process termination.
30733 
30734      Action:   If DEVICE  is a disk drive, demount  the volume on
30735                it and store it in the library.
30736 
30737 
30738                [rcp_control_.pl1]
30739                RCP:  Force Unassigned DEVICE from PERSON.PROJ.T
30740 
30741 
30742      Stream:   BOS Typewriter.
30743 
30744      Time:     While system is running.
30745 
30746      Meaning:  The user process PERSON.PROJ.T has terminated, and
30747                its resources  have been freed.  Or,  the operator
30748                may have forced the unassignment of DRIVE.
30749 
30750      Action:   No operator action is required.
30751 
30752 
30753 
30754 RCP                            531            08/03/23     MR12.7^L
30755 
30756 
30757 
30758 
30759                [rcprm_journalize_.pl1]
30760                RCP:   Journal  could  not  be  forcibly  written.
30761                ERROR CODE
30762 
30763 
30764      Stream:   BOS Typewriter.
30765 
30766      Time:     While system is running.
30767 
30768      Meaning:  A   force-write  to   disk  of   the  RCP  journal
30769                failed.This  indicates   a  logic  error   in  the
30770                supervisor, or CPU or memory hardware problems.
30771 
30772      Action:   Contact the system programming staff.
30773 
30774 
30775                [rcprm_journalize_.pl1]
30776                RCP:    Journal  lost   transaction  for   USERID.
30777                ERROR_CODE
30778 
30779 
30780      Stream:   BOS Typewriter (sounds beeper)
30781 
30782      Time:     While system is running.
30783 
30784      Meaning:  Some  RCP  Resource   Management  activity,  while
30785                successfully    completed,   was    not   properly
30786                journalized for  recovery purposes.  Subsequently,
30787                if the  registries become damaged before  they are
30788                safely  copied by  the System  Administrator, this
30789                activity will be lost.
30790 
30791      Action:   Contact the system programming staff._sa
30792 
30793 
30794                [rcp_detach_.pl1]
30795                RCP:   Manually unload  volume VOLUME  from device
30796                DEVICE
30797 
30798 
30799      Stream:   BOS Typewriter (sounds beeper)
30800 
30801      Time:     While system is running.
30802 
30803      Meaning:  RCP could not unload the specified volume from the
30804                device on which it was loaded.
30805 
30806      Action:   Manually  unload the  volume from  the device  and
30807                return the volume to the library for storage.
30808 
30809 
30810 
30811 
30812 RCP                            532            08/03/23     MR12.7^L
30813 
30814 
30815                [rcp_unload_.pl1]
30816                RCP:   Manually unload  volume VOLUME  from device
30817                DEVICE
30818 
30819 
30820      Stream:   BOS Typewriter (sounds beeper)
30821 
30822      Time:     While system is running.
30823 
30824      Meaning:  RCP could not unload the specified volume from the
30825                device on which it was loaded.
30826 
30827      Action:   Manually  unload the  volume from  the device  and
30828                return the volume to the library for storage.
30829 
30830 
30831                [wdx.pl1]
30832                RCP:  Mount logical volume LVNAME for PROCESSNAME
30833 
30834 
30835      Stream:   BOS Typewriter (sounds beeper)
30836 
30837      Time:     While system is running.
30838 
30839      Meaning:  A user (PROCESSNAME)  has requested the attachment
30840                of logical volume LVNAME.   It is not now mounted.
30841                The initializer will issue  mount messages for all
30842                physical volumes needed.
30843 
30844      Action:   Mount  the required   physical volumes,  using the
30845                add_vol  command to  indicate when  each has  been
30846                made ready.   The user process will  continue when
30847                the last  volume has been mounted.   If the volume
30848                cannot  be  mounted,  use  the  del_lv  command to
30849                indicate  this  fact,  and  the  user process will
30850                receive an error indication.
30851 
30852 
30853 
30854                [rcp_disk_.pl1]
30855                RCP:  Mount Pack PACK on DRIVE for PERSON.PROJ.T
30856 
30857 
30858      Stream:   BOS Typewriter (sounds beeper)
30859 
30860      Time:     While system is running.
30861 
30862      Meaning:  The user PERSON.PROJ.T  has requested the mounting
30863                of  the user  I/O pack  named PACK  on disk  drive
30864                DRIVE.
30865 
30866      Action:   Mount the pack and make it ready.
30867 
30868 
30869 
30870 RCP                            533            08/03/23     MR12.7^L
30871 
30872 
30873 
30874 
30875                [rcp_disk_.pl1]
30876                RCP:  Mount  Pack PACK with(out) protect  on DRIVE
30877                for PERSON.PROJ.T
30878 
30879 
30880      Stream:   BOS Typewriter (sounds beeper)
30881 
30882      Time:     While system is running.
30883 
30884      Meaning:  The user PERSON.PROJ.T  has requested the mounting
30885                of  the user  I/O pack  named PACK  on disk  drive
30886                DRIVE.
30887 
30888      Action:   Mount the pack and make it ready.  Set the PROTECT
30889                status as specified in the message.
30890 
30891 
30892 
30893                [rcp_message_.pl1]
30894                RCP:   Mount Reel  REELID with(out)  ring on DRIVE
30895                for PERSON.PROJ.T (switching volumes).
30896 
30897 
30898      Stream:   BOS Typewriter (sounds beeper)
30899 
30900      Time:     While system is running.
30901 
30902      Meaning:  A user process has  requested the mounting of tape
30903                reel REELID on drive DRIVE.
30904 
30905      Action:   Locate  the requested  reel.  Check  to make  sure
30906                that  the user PERSON.PROJ  is allowed to  use the
30907                reel.  Insert or remove a write ring as specified.
30908                Mount the reel on the specified drive.
30909 
30910                If the  reel cannot be mounted,  either because it
30911                cannot  be located,  access is  incorrect, or  the
30912                drive is down, use the "x deny" function to reject
30913                the mount request.
30914 
30915 
30916 
30917                [rcp_tape_.pl1]
30918                RCP:   Mount Reel  REELID with(out)  ring on DRIVE
30919                for PERSON.PROJ.T.
30920 
30921 
30922      Stream:   BOS Typewriter (sounds beeper)
30923 
30924      Time:     While system is running.
30925 
30926 
30927 
30928 RCP                            534            08/03/23     MR12.7^L
30929 
30930 
30931      Meaning:  A user process has  requested the mounting of tape
30932                reel REELID on drive DRIVE.
30933 
30934      Action:   Locate  the requested  reel.  Check  to make  sure
30935                that  the user PERSON.PROJ  is allowed to  use the
30936                reel.  Insert or remove a write ring as specified.
30937                Mount the reel on the specified drive.
30938 
30939                If the  reel cannot be mounted,  either because it
30940                cannot  be located,  access is  incorrect, or  the
30941                drive is down, use the "x deny" function to reject
30942                the mount request.
30943 
30944 
30945 
30946                [rcp_disk_.pl1]
30947                RCP:  Mounted LABEL_TYPE volume  NAME on DRIVE for
30948                user I/O.
30949 
30950 
30951      Stream:   BOS Typewriter.
30952 
30953      Time:     While system is running.
30954 
30955      Meaning:  A  user has  mounted LABEL_TYPE  volume NAME  as a
30956                user  I/O   disk  on  DRIVE.   The   operator  has
30957                authenticated the mount.
30958 
30959      Action:   No operator action is required.
30960 
30961 
30962                [rcp_comment_.pl1]
30963                RCP:  Note (DEVICE) - COMMENT
30964 
30965 
30966      Stream:   BOS Typewriter.
30967 
30968      Time:     While system is running.
30969 
30970      Meaning:  The user requesting the mounting of a tape or disk
30971                pack on device specified a comment string.
30972 
30973      Action:   Read  the   comment.   It  may   describe  special
30974                operator action, such as where to find or send the
30975                volume.
30976 
30977 
30978 
30979                [rcprm_find_resource_.pl1]
30980                RCP:    Operator  certified  manual   clearing  of
30981                VOLUME.  RCP:  USERID certified manual clearing of
30982                VOLUME.
30983 
30984 
30985 
30986 RCP                            535            08/03/23     MR12.7^L
30987 
30988 
30989      Stream:   BOS Typewriter.
30990 
30991      Time:     In  response  to   an  operator  or  administrator
30992                command.
30993 
30994      Meaning:  This message is printed for auditing purposes when
30995                site-madated destruction of data is accomplished.
30996 
30997      Action:   No operator action is required.
30998 
30999 
31000                [rcp_preload_.pl1]
31001                RCP:  Preload volume VOLUME on device DEVICE
31002 
31003 
31004      Stream:   BOS Typewriter.
31005 
31006      Time:     While system is running.
31007 
31008      Meaning:  The operator request to  preload has been accepted
31009                by RCP.
31010 
31011      Action:   Preload  the volume  in question  on the specified
31012                device.
31013 
31014 
31015                [rcprm_find_resource_.pl1]
31016                RCP:  Registries may be  in an inconsistent state.
31017                ERROR_CODE
31018 
31019 
31020      Stream:   BOS Typewriter (sounds beeper)
31021 
31022      Time:     While system is running.
31023 
31024      Meaning:  An  RCP Resource   Management transaction  was not
31025                properly   committed    to   the   registries.This
31026                indicates a logic error  in the supervisor, or CPU
31027                or memory hardware problems.
31028 
31029      Action:   Contact the system programming staff.
31030 
31031 
31032                [rcp_disk_.pl1]
31033                RCP:  Rejected mount of LABEL_TYPE volume NAME for
31034                PERSON.PROJ.T
31035 
31036 
31037      Stream:   BOS Typewriter.
31038 
31039      Time:     While system is running.
31040 
31041 
31042 
31043 
31044 RCP                            536            08/03/23     MR12.7^L
31045 
31046 
31047      Meaning:  A  user has  attempted to  mount a  storage-system
31048                format  or unreadable  (LABEL_TYPE) disk  pack for
31049                user I/O,  without specifying the  -sys parameter.
31050                Because  this might  interfere with  later storage
31051                system  use  of  the  pack  or  compromise  system
31052                security,  this  action  is  not  permitted.   The
31053                user's  request  is  rejected.   This  error could
31054                arise  if an   operator inadvertently  mounted the
31055                wrong pack.
31056 
31057      Action:   No operator action is required.
31058 
31059 
31060                [rcp_tape_.pl1]
31061                RCP:  Remount Reel REELID with(out) ring on DRIVE.
31062 
31063 
31064      Stream:   BOS Typewriter (sounds beeper)
31065 
31066      Time:     While system is running.
31067 
31068      Meaning:  The  system found  a write  ring when  one was not
31069                required, or did not find one when one was needed.
31070                Or  the authentication  code did  not match.   The
31071                tape is unloaded.
31072 
31073      Action:   Correct the write ring status or mount the correct
31074                tape and reready the tape.
31075 
31076 
31077                [rcp_disk_.pl1]
31078                RCP:  Reready DRIVE
31079 
31080 
31081      Stream:   BOS Typewriter (sounds beeper)
31082 
31083      Time:     While system is running.
31084 
31085      Meaning:  DRIVE is not ready.
31086 
31087      Action:   Make the drive ready.
31088 
31089 
31090                [rcp_disk_.pl1]
31091                RCP:  Reready DRIVE with(out) protect
31092 
31093 
31094      Stream:   BOS Typewriter (sounds beeper)
31095 
31096      Time:     While system is running.
31097 
31098      Meaning:  DRIVE is not ready.
31099 
31100 
31101 
31102 RCP                            537            08/03/23     MR12.7^L
31103 
31104 
31105      Action:   Make the drive ready.
31106 
31107 
31108                [rcp_tape_.pl1]
31109                RCP:  Reready DRIVE.
31110 
31111 
31112      Stream:   BOS Typewriter (sounds beeper)
31113 
31114      Time:     While system is running.
31115 
31116      Meaning:  DRIVE has dropped out of ready status.
31117 
31118      Action:   Reready it.
31119 
31120 
31121                [rcp_tape_.pl1]
31122                RCP:    Reready   Reel   REELID   on   DRIVE   for
31123                PERSON.PROJ.T.
31124 
31125 
31126      Stream:   BOS Typewriter (sounds beeper)
31127 
31128      Time:     While system is running.
31129 
31130      Meaning:  A preloaded volume was not ready.
31131 
31132      Action:   Make the volume ready.
31133 
31134 
31135                [rcp_reserve_.pl1]
31136                RCP:    Reserved  device   devX_MM  for   RESERVER
31137                (id=RES_ID)
31138 
31139 
31140      Stream:   Logged in SYSERR log.
31141 
31142      Time:     While system is running.
31143 
31144      Meaning:  Device devX_MM has been reserved for RESERVER.
31145 
31146      Action:   No operator action is required.
31147 
31148 
31149                [rcp_reserve_.pl1]
31150                RCP:   Reserved  volume  volume_name  for RESERVER
31151                (id=RES_ID)
31152 
31153 
31154      Stream:   Logged in SYSERR log.
31155 
31156      Time:     While system is running.
31157 
31158 
31159 
31160 RCP                            538            08/03/23     MR12.7^L
31161 
31162 
31163      Meaning:  Volume volume_name has been reserved for RESERVER.
31164 
31165      Action:   No operator action is required.
31166 
31167 
31168                [rcp_auto_register_.pl1]
31169                RCP:   RESOURCE_TYPE RESOURCE_NAME  registered and
31170                acquired to USER.
31171 
31172 
31173      Stream:   BOS Typewriter.
31174 
31175      Time:     While system is running.
31176 
31177      Meaning:  The resource RESOURCE_NAME  has been automatically
31178                registered and acquired to USER.  It is a resource
31179                of the type RESCOURCE_TYPE.
31180 
31181      Action:   No operator action is required.
31182 
31183 
31184                [rcprm_find_resource_.pl1]
31185                RCP:  Schedule VOLUME for manual clearing.
31186 
31187 
31188      Stream:   BOS Typewriter (sounds beeper)
31189 
31190      Time:     While system is running.
31191 
31192      Meaning:  The data contained on VOLUME is to be destroyed by
31193                the operator via degaussing or other site-mandated
31194                method.
31195 
31196      Action:   The  operator must  erase the  specified resource,
31197                and  must acknowledge when  this has been  done by
31198                issuing   the   clear_resource   command   or  the
31199                appropriate site-defined "x" Initializer request.
31200 
31201 
31202 
31203                [rcp_disk_.pl1]
31204                RCP:   Turn protect  switch ON/OFF  on drive DRIVE
31205                and then push Operator Interrupt on MPC
31206 
31207 
31208      Stream:   BOS Typewriter (sounds beeper)
31209 
31210      Time:     While system is running.
31211 
31212      Meaning:  The PROTECT status was wrong for DRIVE.
31213 
31214      Meaning:  Correct the  PROTECT status and push  the Operator
31215                Interrupt button on the MPC.
31216 
31217 
31218 RCP                            539            08/03/23     MR12.7^L
31219 
31220 
31221 
31222 
31223                [rcp_control_.pl1]
31224                RCP:  Unassigned DEVICE from PERSON.PROJ.T
31225 
31226 
31227      Stream:   Logged in SYSERR log.
31228 
31229      Time:     While system is running.
31230 
31231      Meaning:  PERSON.PROJ.T has released DRIVE normally.
31232 
31233      Action:   No operator action is required.
31234 
31235 
31236                [rcp_detach_.pl1]
31237                RCP:  Unloading volume VOLUME from device DEVICE
31238 
31239 
31240      Stream:   BOS Typewriter.
31241 
31242      Time:     While system is running.
31243 
31244      Meaning:  The specified VOLUME is being demounted by RCP.
31245 
31246      Action:   Return the specified VOLUME to the library.
31247 
31248 
31249                [rcp_unload_.pl1]
31250                RCP:  Unloading volume VOLUME from device DEVICE
31251 
31252 
31253      Stream:   BOS Typewriter.
31254 
31255      Time:     While system is running.
31256 
31257      Meaning:  The specified VOLUME is being demounted by RCP.
31258 
31259      Action:   Return the specified VOLUME to the library.
31260 
31261 
31262                [rcp_tape_.pl1]
31263                RCP:    Using    Reel   REELID   on    DRIVE   for
31264                PERSON.PROJ.T.
31265 
31266 
31267      Stream:   BOS Typewriter.
31268 
31269      Time:     While system is running.
31270 
31271      Meaning:  Using a preloaded volume.
31272 
31273      Action:   No operator action is required.
31274 
31275 
31276 RCP                            540            08/03/23     MR12.7^L
31277 
31278 
31279 
31280 
31281                [rcp_disk_.pl1]
31282                RCP:  WARNING!!  IF  YOU AUTHENTICATE THIS REQUEST
31283                <USER> WILL OWN VOLUME <VOLUME>!
31284 
31285 
31286      Stream:   BOS Typewriter (sounds beeper)
31287 
31288      Time:     While system is running.
31289 
31290      Meaning:  This is  a warning to the operator.   He should be
31291                very  careful to check  the physical label  of the
31292                volume before authenticating this request.  As the
31293                message  states, if  the request  is autheticated,
31294                <VOLUME>  will  be   registered  and  acquired  to
31295                <USER>.
31296 
31297      Action:   Check the physical label of  the disk pack.  If it
31298                is  the  property   of  <USER>,  authenticate  the
31299                request.  If it is not the property of <USER> deny
31300                the request by typing "x auth no".
31301 
31302 
31303 
31304                [rcp_tape_.pl1]
31305                RCP:  WARNING!!  IF  YOU AUTHENTICATE THIS REQUEST
31306                <USER> WILL OWN VOLUME <VOLUME>!
31307 
31308 
31309      Stream:   BOS Typewriter (sounds beeper)
31310 
31311      Time:     While system is running.
31312 
31313      Meaning:  This is a warning to  the operator.  IHe should be
31314                very  careful to check  the physical label  of the
31315                volume before authenticating this request.  As the
31316                message  states, if  the request  is autheticated,
31317                <VOLUME>  will  be   registered  and  acquired  to
31318                <USER>.
31319 
31320      Action:   Check the  physical label of the  tape volume.  If
31321                it  is the  property of  <USER>, authenticate  the
31322                request.  If it is not the property of <USER> deny
31323                the request by typing "x auth no".
31324 
31325 
31326 
31327                [rcp_disk_.pl1]
31328                RCP:  Wrong  pack (NAME) mounted on  DRIVE.  Mount
31329                pack PACK on DRIVE.
31330 
31331 
31332 
31333 
31334 RCP                            541            08/03/23     MR12.7^L
31335 
31336 
31337      Stream:   BOS Typewriter (sounds beeper)
31338 
31339      Time:     While system is running.
31340 
31341      Meaning:  The  operator  has  denied  authentication  for  a
31342                removable  disk pack  (NAME) on  drive DRIVE.  The
31343                disk drive is put in standby.
31344 
31345      Action:   Mount  the  correct  pack  PACK  with  protect  as
31346                specified and ready drive.
31347 
31348 
31349                [rcp_disk_.pl1]
31350                RCP:  Wrong  pack (NAME) mounted on  DRIVE.  Mount
31351                pack PACK with(out) protect on DRIVE.
31352 
31353 
31354      Stream:   BOS Typewriter (sounds beeper)
31355 
31356      Time:     While system is running.
31357 
31358      Meaning:  The  operator  has  denied  authentication  for  a
31359                removable  disk pack  (NAME) on  drive DRIVE.  The
31360                disk drive is put in standby.
31361 
31362      Action:   Mount  the  correct  pack  PACK  with  protect  as
31363                specified and ready drive.
31364 
31365 
31366                [rcp_control_.pl1]
31367                rcp_control_:  Error surveying DEVICE.  MESSAGE
31368 
31369 
31370      Stream:   BOS Typewriter.
31371 
31372      Time:     In response to an operator command.
31373 
31374      Meaning:  An error occurred while surveying the device.
31375 
31376      Action:   Contact the system programming staff.
31377 
31378 
31379                [rcp_init.pl1]
31380                rcp_init:  DDDD cannot be used for user I/O.
31381 
31382 
31383      Stream:   BOS Typewriter (Crashes system)
31384 
31385      Time:     System Intialization.
31386 
31387      Meaning:  An attempt was made to configure a device for user
31388                I/O which  is being used by the  system for system
31389                storage.
31390 
31391 
31392 rcp_init                       542            08/03/23     MR12.7^L
31393 
31394 
31395      Action:   Follow normal recovery procedures.
31396 
31397 
31398                [rcp_init.pl1]
31399                rcp_init:  DDDD deleted.
31400 
31401 
31402      Stream:   BOS Typewriter.
31403 
31404      Time:     System Intialization.
31405 
31406      Meaning:  Device DDDD could not be  found or accessed and it
31407                will be deleted.
31408 
31409      Action:   Contact the system programming staff.
31410 
31411 
31412                [rcp_init.pl1]
31413                rcp_init:  Device DEVICE defined more than once
31414 
31415 
31416      Stream:   BOS Typewriter (Crashes system)
31417 
31418      Time:     System Intialization.
31419 
31420      Meaning:  The configuration  deck defines the  device DEVICE
31421                more than once.
31422 
31423      Action:   Perform  an emergency   shutdown, and  correct the
31424                configuration   deck.    Follow   normal  recovery
31425                procedures.
31426 
31427 
31428 
31429                [rcp_init.pl1]
31430                rcp_init:  Error surveying DDDD.  ERRORMESSAGE
31431 
31432 
31433      Stream:   BOS Typewriter.
31434 
31435      Time:     System Intialization.
31436 
31437      Meaning:  Attempted to access device  DDDD but could not due
31438                to ERRORMESSAGE.
31439 
31440      Action:   Contact the system programming staff.
31441 
31442 
31443                [rcp_init.pl1]
31444                rcp_init:  ndrives  not specified with  last model
31445                number for PRPH DDDD.  Assuming 0.
31446 
31447 
31448 
31449 
31450 rcp_init                       543            08/03/23     MR12.7^L
31451 
31452 
31453      Stream:   BOS Typewriter.
31454 
31455      Time:     System Intialization.
31456 
31457      Meaning:  Detected  a MODEL  value at  the end  of PRPH card
31458                PPPP.   Each  MODEL  value  should  paired with an
31459                NDRIVE  value.   The  last  model  value  will  be
31460                assigned zero devices.  It  is possible that there
31461                is  another error elsewhere  on this card  to have
31462                caused this message.
31463 
31464      Action:   Contact the system programming staff.
31465 
31466 
31467                [rcp_init.pl1]
31468                rcp_init:     Trying    to    create   rcp_com_seg
31469                ERRORMESSAGE
31470 
31471 
31472      Stream:   BOS Typewriter (Crashes system)
31473 
31474      Time:     System Intialization.
31475 
31476      Meaning:  This indicates a logic error in the supervisor, or
31477                CPU or memory hardware problems.
31478 
31479      Action:   Follow normal recovery procedures.
31480 
31481 
31482                [rcp_init.pl1]
31483                rcp_init:  Trying to create rcp_data ERRORMESSAGE
31484 
31485 
31486      Stream:   BOS Typewriter (Crashes system)
31487 
31488      Time:     System Intialization.
31489 
31490      Meaning:  This indicates a logic error in the supervisor, or
31491                CPU or memory hardware problems.
31492 
31493      Action:   Follow normal recovery procedures.
31494 
31495 
31496                [rcp_init.pl1]
31497                rcp_init:  Trying to init mca_data.  ERRORMESSAGE
31498 
31499 
31500      Stream:   BOS Typewriter (Crashes system)
31501 
31502      Time:     System Intialization.
31503 
31504      Meaning:  This indicates a logic error in the supervisor, or
31505                CPU or memory hardware problems.
31506 
31507 
31508 rcp_init                       544            08/03/23     MR12.7^L
31509 
31510 
31511      Action:   Follow normal recovery procedures.
31512 
31513 
31514                [rcp_init.pl1]
31515                rcp_init:    Trying   to   reclassify  rcp_com_seg
31516                ERRORMESSAGE
31517 
31518 
31519      Stream:   BOS Typewriter (Crashes system)
31520 
31521      Time:     System Intialization.
31522 
31523      Meaning:  This indicates a logic error in the supervisor, or
31524                CPU or memory hardware problems.
31525 
31526      Action:   Follow normal recovery procedures.
31527 
31528 
31529                [rcp_init.pl1]
31530                rcp_init:     Trying   to    reclassify   rcp_data
31531                ERRORMESSAGE
31532 
31533 
31534      Stream:   BOS Typewriter (Crashes system)
31535 
31536      Time:     System Intialization.
31537 
31538      Meaning:  This indicates a logic error in the supervisor, or
31539                CPU or memory hardware problems.
31540 
31541      Action:   Follow normal recovery procedures.
31542 
31543 
31544                [rcp_tape_survey_.pl1]
31545                rcp_tape_survey_:    Error  surveying   controller
31546                CONTROLLER:  ERROR_STATUS
31547 
31548 
31549      Stream:   BOS Typewriter (sounds beeper)
31550 
31551      Time:     System Intialization.
31552 
31553      Meaning:  An error was received from IOI while attempting to
31554                survey the tape controller DEVICE.  This indicates
31555                a logic error in the  supervisor, or CPU or memory
31556                hardware problems.
31557 
31558      Action:   Contact  the  system  programming  staff.   Follow
31559                normal recovery procedures.
31560 
31561 
31562 
31563                [rcp_tape_survey_.pl1]
31564 
31565 
31566 rcp_tape_survey_               545            08/03/23     MR12.7^L
31567 
31568 
31569                rcp_tape_survey_:  Multiple  device NUMBER's found
31570                on CONTROLLER.
31571 
31572 
31573      Stream:   BOS Typewriter (sounds beeper)
31574 
31575      Time:     System Intialization.
31576 
31577      Meaning:  The  survey information  indicates that  there are
31578                multiple devices with the same device number.
31579 
31580      Action:   Contact field engineering personnel.
31581 
31582 
31583                [rcp_tape_survey_.pl1]
31584                rcp_tape_survey_:  Tape  controller CONTROLLER did
31585                not respond within one second.
31586 
31587 
31588      Stream:   BOS Typewriter (sounds beeper)
31589 
31590      Time:     System Intialization.
31591 
31592      Meaning:  The  tape controller or  IOM failed to  respond to
31593                the survey-devices command by sending an interrupt
31594                within one second.
31595 
31596      Action:   Contact field engineering personnel.
31597 
31598 
31599                [rcprm_registry_mgr_.pl1]
31600                rcprm_registry_mgr_$delete_registry:      Deleting
31601                (possibly bogus) registry PATH for USERID.
31602 
31603 
31604      Stream:   BOS Typewriter (sounds beeper)
31605 
31606      Time:     While system is running.
31607 
31608      Meaning:  The  segment at PATH  does not seem  to be an  RCP
31609                registry.  It may simply be a damaged registry, or
31610                a user may be attempting to use delete_registry to
31611                delete a non-registry object.
31612 
31613      Action:   Contact the system programming staff._sa
31614 
31615 
31616                [system_control_.pl1]
31617                Ready
31618 
31619 
31620      Stream:   BOS Typewriter.
31621 
31622 
31623 
31624 rcprm_registry_mgr_$delete_regis^H5t^H4r^H6y           08/03/23     MR12.7^L
31625 
31626 
31627      Time:     In response to an operator command.
31628 
31629      Meaning:  The Initializer  types Ready whenever it  is ready
31630                to accept an Initializer command in ring 4.
31631 
31632      Action:   Type the desired command.
31633 
31634 
31635                [reassign_work_classes_.pl1]
31636                reassign_work_classes_:  load  control group "XXX"
31637                not found in mgt for user PERSON.PROJECT.TAG.
31638                reassign_work_classes_:   mgt  clobbered,  contact
31639                system administrator.
31640 
31641 
31642 
31643      Stream:   as (severity2).
31644 
31645      Time:     At  shift  change  time,  or  after  a "maxu auto"
31646                command.
31647 
31648      Meaning:  Some  logged  in  user's  load  control  group has
31649                apparently disappeared from the  mgt.  If the load
31650                control group  specified in the message  is valid,
31651                then the  mgt has been destroyed.   Otherwise, the
31652                user's answer table entry has been destroyed.  All
31653                users will remain in their current work classes.
31654 
31655      Action:   Contact the system programming staff._sa
31656 
31657 
31658                [reassign_work_classes_.pl1]
31659                reassign_work_classes_:   no work  classes defined
31660                on current shift.
31661 
31662 
31663      Stream:   as (severity2)
31664 
31665      Time:     At  shift  change  time,  or  after  a "maxu auto"
31666                command.
31667 
31668      Meaning:  The table  in the mgt that should  define the work
31669                classes for the current  shift has not been filled
31670                in.  Probably  a new shift  has been added  to the
31671                installation_parms  segment, but the  work classes
31672                for that shift have not been specified in the mgt.
31673                All users will be placed in a single work class.
31674 
31675      Action:   No operator action is required.
31676 
31677 
31678                [reassign_work_classes_.pl1]
31679 
31680 
31681 
31682 reassign_work_classes_         547            08/03/23     MR12.7^L
31683 
31684 
31685                reassign_work_classes_:   process NNN  remained in
31686                work class NN
31687 
31688 
31689      Stream:   as (severity1)
31690 
31691      Time:     At  shift  change  time,  or  after  a "maxu auto"
31692                command.
31693 
31694      Meaning:  Some  privileged  user  has  interfered  with  the
31695                Answering Service's attempt to define a new set of
31696                work   classes.    The   Answering   Service  will
31697                automatically  retry  the   reassignment  of  work
31698                classes.
31699 
31700      Action:   No operator action is required.
31701 
31702 
31703                [reassign_work_classes_.pl1]
31704                reassign_work_classes_:   undefined work  class DD
31705                required by load control group XXX
31706                reassign_work_classes_:   mgt  clobbered,  contact
31707                system administrator.
31708 
31709 
31710 
31711      Stream:   as (severity2)
31712 
31713      Time:     At  shift  change  time,  or  after  a "maxu auto"
31714                command.
31715 
31716      Meaning:  There  is an  inconsistency in  the mgt.  Probably
31717                the mgt has been destroyed.  All users will remain
31718                in their current work class.
31719 
31720      Action:   Contact the system programming staff._sa
31721 
31722 
31723                [disk_rebuild_caller.pl1]
31724                rebuild_disk:   Error  XX  in  rebuild  of  volume
31725                PVNAME.
31726 
31727 
31728      Stream:   Initializer process output.
31729 
31730      Time:     In response to an operator command.
31731 
31732      Meaning:  An error has occurred  trying to rebuild the disk.
31733                The new copy should not be used.
31734 
31735      Action:   If the problem can be  repaired, repair it and try
31736                again.  Contact the system programming staff.
31737 
31738 
31739 
31740 rebuild_disk                   548            08/03/23     MR12.7^L
31741 
31742 
31743 
31744 
31745                [salv_caller.pl1]
31746                rebuild_disk:  Expected argument missing.
31747 
31748 
31749      Stream:   Initializer process output.
31750 
31751      Time:     In response to an operator command.
31752 
31753      Meaning:  Incorrect arguments were specified.
31754 
31755      Action:   Enter a corrected command line.
31756 
31757 
31758                [salv_caller.pl1]
31759                rebuild_disk:   Specified control argument  is not
31760                implemented by this command.  BLAH
31761 
31762 
31763      Stream:   Initializer process output.
31764 
31765      Time:     In response to an operator command.
31766 
31767      Meaning:  Incorrect arguments were specified.
31768 
31769      Action:   Enter a corrected command line.
31770 
31771 
31772                [disk_rebuild_caller.pl1]
31773                rebuild_disk:   volume  PVNAME  from  DSKA_XX onto
31774                DSKA_YY
31775                Current disk parameters:
31776                part NAME FREC NREC
31777                Vtoc size is XX, ave.  seg length = Y.ZZZ
31778                Current number of VTOCEs = XX
31779 
31780 
31781 
31782      Stream:   Initializer process output.
31783 
31784      Time:     In response to an operator command.
31785 
31786      Meaning:  This  is  the  response  to  the  operator command
31787                "rebuild_disk" issued in ring 1.
31788 
31789      Action:   No operator action is required.
31790 
31791 
31792                [disk_rebuild_caller.pl1]
31793                rebuild_disk:   Volume  PVNAME   must  be  mounted
31794                before rebuilding
31795 
31796 
31797 
31798 rebuild_disk                   549            08/03/23     MR12.7^L
31799 
31800 
31801      Stream:   Initializer process output.
31802 
31803      Time:     In response to an operator command.
31804 
31805      Meaning:  The rebuild_disk command was invoked on an mounted
31806                volume.   Only volumes  which are  mounted may  be
31807                rebuilt.  No action was taken.
31808 
31809      Action:   Salvage  the volume  first, and  then reissue  the
31810                rebuild_disk command.
31811 
31812 
31813 
31814                [reclassify.pl1]
31815                reclassify:  err locking parent.  ERROR_CODE
31816 
31817 
31818      Stream:   BOS Typewriter (Crashes system)
31819 
31820      Time:     While system is running.
31821 
31822      Meaning:  This indicates a logic error in the supervisor, or
31823                CPU or  memory hardware problems.   BOS Typewriter
31824                (Crashes system)es
31825 
31826      Action:   Follow normal recovery procedures.
31827 
31828 
31829                [reconfig.pl1]
31830                reconfig:      Assigned     CPU     <cputag>    to
31831                <Person.Project.instance> for testing
31832 
31833 
31834      Stream:   BOS Typewriter.
31835 
31836      Time:     While system is running.
31837 
31838      Meaning:  Successful   reconfiguration   of   the  indicated
31839                processor  has  been  performed  by  the processor
31840                testing (ISOLTS) subsystem.
31841 
31842      Action:   No operator action is required.
31843 
31844 
31845                [reconfig.pl1]
31846                reconfig:    Releasing  base  <req_mem>k   of  MEM
31847                <scutag>
31848 
31849 
31850      Stream:   BOS Typewriter.
31851 
31852      Time:     While system is running.
31853 
31854 
31855 
31856 reconfig                       550            08/03/23     MR12.7^L
31857 
31858 
31859      Meaning:  Processor  testing  has  been  terminated  and the
31860                indicated    memory   is    now   available    for
31861                reconfiguration.
31862 
31863      Action:   No operator action is required.
31864 
31865 
31866                [reconfig.pl1]
31867                reconfig:  trouble unlocking scs$reconfig_lock
31868 
31869 
31870      Stream:   BOS Typewriter.
31871 
31872      Time:     While system is running.
31873 
31874      Meaning:  The  reconfiguration lock  could not  be unlocked.
31875                It is left in its current state.  Further attempts
31876                at reconfiguration may fail.
31877 
31878      Action:   No operator action is required.
31879 
31880 
31881                [reconfig.pl1]
31882                reconfig:     Unassigned    CPU    <cputag>   from
31883                <Person.Project.instance>
31884 
31885 
31886      Stream:   BOS Typewriter.
31887 
31888      Time:     While system is running.
31889 
31890      Meaning:  Processor  testing  has  been  terminated  and the
31891                indicated   processor   is   now   available   for
31892                reconfiguration.
31893 
31894      Action:   No operator action is required.
31895 
31896 
31897                [reconfig.pl1]
31898                reconfig:  Using  base <req_mem>k of  MEM <scutag>
31899                for testing CPU cputag
31900 
31901 
31902      Stream:   BOS Typewriter.
31903 
31904      Time:     While system is running.
31905 
31906      Meaning:  Successful reconfiguration of the indicated memory
31907                has  been  performed   by  the  processor  testing
31908                (ISOLTS) subsystem.
31909 
31910      Action:   No operator action is required.
31911 
31912 
31913 
31914 reload_volume                  551            08/03/23     MR12.7^L
31915 
31916 
31917 
31918 
31919                [reloader.pl1]
31920                reload_volume:  An implementation restriction when
31921                using version  1 volume logs.  This  requires that
31922                the RPV be reloaded separately from other volumes.
31923 
31924 
31925 
31926      Stream:   $rld_out
31927 
31928      Time:     $reload
31929 
31930      Meaning:  Using version 1 volume  logs, all physical volumes
31931                must belong  to the mounted RPV.   An exception is
31932                when reloading the RPV itself, it must be reloaded
31933                separately,  then a  re-boot on  the new  RPV will
31934                allow the other volumes to be reloaded.
31935 
31936      Action:   Enter a corrected command line.
31937 
31938 
31939                [reloader.pl1]
31940                reload_volume:  arg err:  ERROR_MESS
31941 
31942 
31943      Stream:   $rld_out
31944 
31945      Time:     $reload
31946 
31947      Meaning:  Invalid input was given.
31948 
31949      Action:   Enter a corrected command line.
31950 
31951 
31952                [reloader.pl1]
31953                reload_volume:   Begin reload   of volume  NAME at
31954                TIME
31955 
31956 
31957      Stream:   $rld_on
31958 
31959      Time:     $reload
31960 
31961      Meaning:  A volume reload is beginning.
31962 
31963      Action:   No operator action is required.
31964 
31965 
31966                [reloader.pl1]
31967                reload_volume:   Could not enable  256KW segments:
31968                ERORR_MESS
31969 
31970 
31971 
31972 reload_volume                  552            08/03/23     MR12.7^L
31973 
31974 
31975      Stream:   $rld_out
31976 
31977      Time:     $reload
31978 
31979      Meaning:  The call to hcs_$set_256K_switch failed.
31980 
31981      Action:   Contact the system programming staff.
31982 
31983 
31984                [reloader.pl1]
31985                reload_volume:  End reload of volume NAME at TIME
31986                reload_volume:  Reloaded on volume NAME XX records
31987                of  XX directories and  XX records of  XX segments
31988                and XX null vtoces
31989 
31990 
31991 
31992      Stream:   $rld_on
31993 
31994      Time:     $reload
31995 
31996      Meaning:  A  volume reload   has completed.   The statistics
31997                printed indicate how many records were reloaded.
31998 
31999      Action:   No operator action is required.
32000 
32001 
32002                [reloader.pl1]
32003                reload_volume:    error   closing   volume  label:
32004                ERROR_MESS
32005 
32006 
32007      Stream:   $rld_out
32008 
32009      Time:     $reload
32010 
32011      Meaning:  An error occurred while reloading.
32012 
32013      Action:   Contact the system programming staff.
32014 
32015 
32016                [reloader.pl1]
32017                reload_volume:    error    closing   volume   map:
32018                ERROR_MESS
32019 
32020 
32021      Stream:   $rld_out
32022 
32023      Time:     $reload
32024 
32025      Meaning:  An error occurred while reloading.
32026 
32027      Action:   Contact the system programming staff.
32028 
32029 
32030 reload_volume                  553            08/03/23     MR12.7^L
32031 
32032 
32033 
32034 
32035                [reloader.pl1]
32036                reload_volume:    error   closing   vtoc   header:
32037                ERROR_MESS
32038 
32039 
32040      Stream:   $rld_out
32041 
32042      Time:     $reload
32043 
32044      Meaning:  An error occurred while reloading.
32045 
32046      Action:   Contact the system programming staff.
32047 
32048 
32049                [reloader.pl1]
32050                reload_volume:    error   creating   control  seg:
32051                ERROR_MESS
32052 
32053 
32054      Stream:   $rld_out
32055 
32056      Time:     $reload
32057 
32058      Meaning:  An error occurred while reloading.
32059 
32060      Action:   Contact the system programming staff.
32061 
32062 
32063                [reloader.pl1]
32064                reload_volume:    error    creating   temp   segs:
32065                ERROR_MESS
32066 
32067 
32068      Stream:   $rld_out
32069 
32070      Time:     $reload
32071 
32072      Meaning:  An error occurred while reloading.
32073 
32074      Action:   Contact the system programming staff.
32075 
32076 
32077                [reloader.pl1]
32078                reload_volume:   error  initializing  input volume
32079                list:  ERROR_MESS
32080 
32081 
32082      Stream:   $rld_out
32083 
32084      Time:     $reload
32085 
32086 
32087 
32088 reload_volume                  554            08/03/23     MR12.7^L
32089 
32090 
32091      Meaning:  An error occurred while reloading.
32092 
32093      Action:   Contact the system programming staff.
32094 
32095 
32096                [reloader.pl1]
32097                reload_volume:  error  initializing output medium:
32098                ERROR_MESS
32099 
32100 
32101      Stream:   $rld_out
32102 
32103      Time:     $reload
32104 
32105      Meaning:  An error occurred while reloading.
32106 
32107      Action:   Contact the system programming staff.
32108 
32109 
32110                [reloader.pl1]
32111                reload_volume:    error    opening   volume   map:
32112                ERROR_MESS
32113 
32114 
32115      Stream:   $rld_out
32116 
32117      Time:     $reload
32118 
32119      Meaning:  An error occurred while reloading.
32120 
32121      Action:   Contact the system programming staff.
32122 
32123 
32124                [reloader.pl1]
32125                reload_volume:    error  reloading   volume  NAME:
32126                ERROR_MESS
32127 
32128 
32129      Stream:   $rld_out
32130 
32131      Time:     $reload
32132 
32133      Meaning:  An error occurred while reloading.
32134 
32135      Action:   Contact the system programming staff.
32136 
32137 
32138                [reloader.pl1]
32139                reload_volume:  label check failed:  ERROR_MESS
32140 
32141 
32142      Stream:   $rld_out
32143 
32144 
32145 
32146 reload_volume                  555            08/03/23     MR12.7^L
32147 
32148 
32149      Time:     $reload
32150 
32151      Meaning:  An error occurred while reloading.
32152 
32153      Action:   Contact the system programming staff.
32154 
32155 
32156                [reloader.pl1]
32157                reload_volume:  Operator name  and physical volume
32158                name not specified
32159 
32160 
32161      Stream:   $rld_out
32162 
32163      Time:     $reload
32164 
32165      Meaning:  Invalid input was typed.
32166 
32167      Action:   Enter a corrected command line.
32168 
32169 
32170                [reloader.pl1]
32171                reload_volume:  Operator name not specified.
32172 
32173 
32174      Stream:   $rld_out
32175 
32176      Time:     $reload
32177 
32178      Meaning:  Missing input.
32179 
32180      Action:   Enter a corrected command line.
32181 
32182 
32183                [reloader.pl1]
32184                reload_volume:     Physical   volume    name   not
32185                specified.
32186 
32187 
32188      Stream:   $rld_out
32189 
32190      Time:     $reload
32191 
32192      Meaning:  Missing input.
32193 
32194      Action:   Enter a corrected command line.
32195 
32196 
32197                [reloader.pl1]
32198                reload_volume:   Please start volume  log recovery
32199                procedure.
32200 
32201 
32202 
32203 
32204 reload_volume                  556            08/03/23     MR12.7^L
32205 
32206 
32207      Stream:   $rld_out
32208 
32209      Time:     $reload
32210 
32211      Meaning:  Use the recover_volume_log  command to recover the
32212                specified physical volumes volume log.
32213 
32214      Action:   Enter a corrected command line.
32215 
32216 
32217                [reloader.pl1]
32218                reload_volume:  The  RPV pvid for  physical volume
32219                NAME does not match the determined RPV pvid.
32220 
32221 
32222 
32223      Stream:   $rld_out
32224 
32225      Time:     $reload
32226 
32227      Meaning:  The  backup_volume_log.rpv_pvid for NAME  does not
32228                match  the  reloader  determined  RPV  pvid.  This
32229                could be  an invalid attempt to  reload a stranger
32230                physical volume.
32231 
32232      Action:   Contact the system programming staff.
32233 
32234 
32235                [reloader.pl1]
32236                reload_volume:    unable   to   build   VTOC  map:
32237                ERROR_MESS
32238 
32239 
32240      Stream:   $rld_out
32241 
32242      Time:     $reload
32243 
32244      Meaning:  An error occurred while reloading.
32245 
32246      Action:   Contact the system programming staff.
32247 
32248 
32249                [reloader.pl1]
32250                reload_volume:  unable to determine pvid for NAME:
32251                ERROR_MESS
32252 
32253 
32254      Stream:   $rld_out
32255 
32256      Time:     $reload
32257 
32258      Meaning:  The  volume  registration   information  does  not
32259                contain the  physical volume NAME.  This  could be
32260 
32261 
32262 reload_volume                  557            08/03/23     MR12.7^L
32263 
32264 
32265                an invalid  attempt to reload a  stranger physical
32266                volume.
32267 
32268      Action:   Contact the system programming staff.
32269 
32270 
32271                [reloader.pl1]
32272                reload_volume:   unable  to  get  info  about rpv:
32273                ERROR_MESS
32274 
32275 
32276      Stream:   $rld_out
32277 
32278      Time:     $reload
32279 
32280      Meaning:  An error occurred while reloading.
32281 
32282      Action:   Contact the system programming staff.
32283 
32284 
32285                [reloader.pl1]
32286                reload_volume:   Unable to  locate a  valid volume
32287                log for PATH:  ERROR_MESS
32288 
32289 
32290      Stream:   $rld_out
32291 
32292      Time:     $reload
32293 
32294      Meaning:  The volue log at PATH was not found.  This message
32295                will always cause the reload to be aborted.
32296 
32297      Action:   Enter a corrected command line.
32298 
32299 
32300                [reloader.pl1]
32301                reload_volume:    unable  to  open   vtoc  header:
32302                ERROR_MESS
32303 
32304 
32305      Stream:   $rld_out
32306 
32307      Time:     $reload
32308 
32309      Meaning:  An error occurred while reloading.
32310 
32311      Action:   Contact the system programming staff.
32312 
32313 
32314                [reload_volume_.pl1]
32315                reload_volume_:   Abandoning  the   reload  of  pv
32316                PVNAME
32317 
32318 
32319 
32320 reload_volume_                 558            08/03/23     MR12.7^L
32321 
32322 
32323      Stream:   $rld_out
32324 
32325      Time:     $reload
32326 
32327      Meaning:  Some fatal error has occurred during the reload of
32328                the specified physical volume.
32329 
32330      Action:   Take  the  action  required   by  the  error  just
32331                previous to  this one and retry the  reload of the
32332                physical volume.
32333 
32334 
32335 
32336                [reload_volume_.pl1]
32337                reload_volume_:    All  physical  volumes   to  be
32338                reloaded have been abandoned.
32339 
32340 
32341      Stream:   $rld_out
32342 
32343      Time:     $reload
32344 
32345      Meaning:  Some fatal error has occurred during the reload of
32346                ALL the specified physical volumes.
32347 
32348      Action:   No operator action is required.
32349 
32350 
32351                [reload_volume_.pl1]
32352                reload_volume_:  Bad disk page PAGE_ADDRESS for pv
32353                PVNAME
32354 
32355 
32356      Stream:   $rld_out
32357 
32358      Time:     $reload
32359 
32360      Meaning:  An  I/O  error  occurred  during  a  reload.  This
32361                message  indicates  the  bad  disk  address on the
32362                volume being reloaded.
32363 
32364      Action:   No operator action is required.
32365 
32366 
32367                [reload_volume_.pl1]
32368                reload_volume_:  Error depositing  old vtoce VTOCX
32369                for pv PVNAME:  ERROR_MESS
32370 
32371 
32372      Stream:   $rld_out
32373 
32374      Time:     $reload
32375 
32376 
32377 
32378 reload_volume_                 559            08/03/23     MR12.7^L
32379 
32380 
32381      Meaning:  The reloader was unable to release pages of an old
32382                object.   This  indicates  a  logic  error  in the
32383                supervisor,  or CPU  or memory  hardware problems.
32384                The input medium is abandoned.
32385 
32386      Action:   No operator action is required.
32387 
32388 
32389                [reload_volume_.pl1]
32390                reload_volume_:   Error depositing page  PAGENO of
32391                vtoce VTOCX for pv PVNAME:  ERROR_MESS
32392 
32393 
32394      Stream:   $rld_out
32395 
32396      Time:     $reload
32397 
32398      Meaning:  The  reloader was  unable to  release page  PAGENO
32399                (decimal)  of the new  object.  This is  only done
32400                when an incomplete object is detected.
32401 
32402      Action:   No operator action is required.
32403 
32404 
32405                [reload_volume_.pl1]
32406                reload_volume_:  Error reading input:  ERROR_MESS
32407 
32408 
32409      Stream:   $rld_out
32410 
32411      Time:     $reload
32412 
32413      Meaning:  An error occurred while  reading input.  The input
32414                medium is abandoned.
32415 
32416      Action:   No operator action is required.
32417 
32418 
32419                [reload_volume_.pl1]
32420                reload_volume_:  Error reading old vtoce VTOCX for
32421                pv PVNAME:  ERROR_MESS
32422 
32423 
32424      Stream:   $rld_out
32425 
32426      Time:     $reload
32427 
32428      Meaning:  An I/O error occurred  during a reload.  The input
32429                medium is abandoned.
32430 
32431      Action:   No operator action is required.
32432 
32433 
32434 
32435 
32436 reload_volume_                 560            08/03/23     MR12.7^L
32437 
32438 
32439                [reload_volume_.pl1]
32440                reload_volume_:  Error writing new vtoce VTOCX for
32441                pv PVNAME:  ERROR_MESS
32442 
32443 
32444      Stream:   $rld_out
32445 
32446      Time:     $reload
32447 
32448      Meaning:  An I/O error occurred  during a reload.  The input
32449                medium is abandoned.
32450 
32451      Action:   No operator action is required.
32452 
32453 
32454                [reload_volume_.pl1]
32455                reload_volume_:  Unable to  set damaged switch for
32456                vtoce VTOCX on pv PVNAME:  ERROR_MESS
32457 
32458 
32459      Stream:   $rld_out
32460 
32461      Time:     $reload
32462 
32463      Meaning:  An I/O error has occured while attempting to write
32464                out  the new vtoce,  which has the  damaged switch
32465                turned on.
32466 
32467      Action:   No operator action is required.
32468 
32469 
32470                [reload_volume_.pl1]
32471                reload_volume_:  Unable  to withdraw for  bad page
32472                on pv PVNAME:  ERROR_MESS
32473 
32474 
32475      Stream:   $rld_out
32476 
32477      Time:     $reload
32478 
32479      Meaning:  After  an  I/O  error,  the  reloader attempted to
32480                allocate a  new page, and failed.   The volume may
32481                be full.
32482 
32483      Action:   If  the volume  is full,  it may  be necessary  to
32484                clean  it up  with sweep_pv  -gc before restarting
32485                the reload.
32486 
32487 
32488 
32489                [reload_volume_.pl1]
32490                reload_volume_:  Unable to  withdraw for new vtoce
32491                VTOCX for pv PVNAME:  ERROR_MESS
32492 
32493 
32494 reload_volume_                 561            08/03/23     MR12.7^L
32495 
32496 
32497      Stream:   $rld_out
32498 
32499      Time:     $reload
32500 
32501      Meaning:  The  reloader is unable  to allocate a  new VTOCE.
32502                The  volume  may  be  full.   The  input medium is
32503                abandoned.
32504 
32505      Action:   No operator action is  required.  If the volume is
32506                full,  it may  be necessary  to clean  it up  with
32507                sweep_pv with the -gc  option and then to continue
32508                reloading.
32509 
32510 
32511 
32512                [operator_com_channel_cmds_.pl1]
32513                remove:  bad arg "AAAA"
32514 
32515 
32516      Stream:   as (severity1).
32517 
32518      Time:     In response to an operator command.
32519 
32520      Meaning:  A  bad  argument  was  furnished  with  an  remove
32521                command.  The argument is skipped.
32522 
32523      Action:   Enter a corrected command.
32524 
32525 
32526                [operator_com_channel_cmds_.pl1]
32527                remove:  error:  not done
32528 
32529 
32530      Stream:   as (severity1).
32531 
32532      Time:     In response to an operator command.
32533 
32534      Meaning:  Bad arguments were given to an remove command.  No
32535                action resulted.
32536 
32537      Action:   Enter a corrected command line.
32538 
32539 
32540                [operator_com_channel_cmds_.pl1]
32541                remove:    ttyXXX  is   in  use   by  the  message
32542                coordinator and can not be removed.
32543 
32544 
32545      Stream:   as (severity1).
32546 
32547      Time:     In response to an operator command.
32548 
32549 
32550 
32551 
32552 remove                         562            08/03/23     MR12.7^L
32553 
32554 
32555      Meaning:  An  operator remove   command specified  a message
32556                coordinator channel.  The channel was not removed.
32557 
32558      Action:   Enter  a  corrected  command  line.   Use the drop
32559                command  to take a  channel away from  the message
32560                coordinator.
32561 
32562 
32563 
32564                [operator_com_channel_cmds_.pl1]
32565                remove:  ttyXXX removed
32566 
32567 
32568      Stream:   as (severity1).
32569 
32570      Time:     In response to an operator remove command.
32571 
32572      Meaning:  This  response  to  the  operator  command  remove
32573                TTYxxx   indicates  the   channel  is   no  longer
32574                available  for  dialups.   If  a  user  was on the
32575                channel,  he   is  bumped  with  no   message  but
32576                "hangup".  Note  that if a  user calls in  on this
32577                channel,  and the modem  answers, the user  gets a
32578                carriage return, but no welcoming message from the
32579                system, and he cannot log in.
32580 
32581      Action:   Remember to busy out the modem so that no user can
32582                call the channel.
32583 
32584 
32585 
32586                [obs_reconfigure.pl1]
32587                Removed frame XXX.
32588 
32589 
32590      Stream:   Initializer process output.
32591 
32592      Time:     In response to an operator command.
32593 
32594      Meaning:  This is  the response to a  successful delmain XXX
32595                command.
32596 
32597      Action:   No operator action is required.
32598 
32599 
32600                [obs_reconfigure.pl1]
32601                Removed frames XXX thru YYY.
32602 
32603 
32604      Stream:   Initializer process output.
32605 
32606      Time:     In response to an operator command.
32607 
32608 
32609 
32610 Removed                        563            08/03/23     MR12.7^L
32611 
32612 
32613      Meaning:  This is the response to a successful delmain XXX N
32614                command.
32615 
32616      Action:   No operator action is required.
32617 
32618 
32619                [obs_reconfigure.pl1]
32620                Removed SCU X and its memory.
32621 
32622 
32623      Stream:   Initializer process output.
32624 
32625      Time:     In response to an operator command.
32626 
32627      Meaning:  This  is the  response  to  a successful  delmem X
32628                command.
32629 
32630      Action:   No operator action is required.
32631 
32632 
32633                [obs_reconfigure.pl1]
32634                Removed  SCU's  X  and  Y  (interlaced)  and their
32635                memory.
32636 
32637 
32638      Stream:   Initializer process output.
32639 
32640      Time:     In response to an operator command.
32641 
32642      Meaning:  This  is the  response  to  a successful  delmem X
32643                command, when SCU's X and Y are interlaced.
32644 
32645      Action:   No operator action is required.
32646 
32647 
32648                [bce_save.pl1]
32649                restore(check_status):      Special     Interrupt:
32650                STATUS_WORD
32651 
32652 
32653      Stream:   BOS Typewriter.
32654 
32655      Time:     System Intialization.
32656 
32657      Meaning:  An unexpected special interrupt has been detected.
32658 
32659      Action:   No operator action is required.
32660 
32661 
32662                [bce_save.pl1]
32663                restore(check_status):  Time-Out on TAPE_DEV
32664 
32665 
32666 
32667 
32668 restore(check_status)          564            08/03/23     MR12.7^L
32669 
32670 
32671      Stream:   BOS Typewriter.
32672 
32673      Time:     System Intialization.
32674 
32675      Meaning:  An  I/O that  was issued  to the  tape device  has
32676                timed-out.
32677 
32678      Action:   Follow normal recovery procedures.
32679 
32680 
32681                [bce_save.pl1]
32682                restore(TAPE_SET):    "Info"  tape   on  TAPE_DEV,
32683                created DATE_TIME
32684 
32685 
32686      Stream:   BOS Typewriter.
32687 
32688      Time:     System Intialization.
32689 
32690      Meaning:  Just an informative message.
32691 
32692      Action:   No operator action is required.
32693 
32694 
32695                [bce_save.pl1]
32696                restore(TAPE_SET):   (Unrecoverable) MAJOR_STATUS,
32697                SUB_STATUS on TAPE_DEV.
32698 
32699 
32700      Stream:   BOS Typewriter.
32701 
32702      Time:     System Intialization.
32703 
32704      Meaning:  An   unrecoverable   error   has   occured   while
32705                attempting to do I/O to the tape device.
32706 
32707      Action:   Follow normal recovery procedures.
32708 
32709 
32710                [bce_save.pl1]
32711                restore(TAPE_SET):   Abnormal tape  termination of
32712                tape# TAPE_NUMBER on TAPE_DEV.
32713 
32714 
32715      Stream:   BOS Typewriter.
32716 
32717      Time:     System Intialization.
32718 
32719      Meaning:  While  reading  the  save  tape  an invalid record
32720                header  was found.   BCE save  tapes are  normally
32721                terminated   with  a   End-of-Reel  (EOR)   record
32722                followed by  three End-of-File (EOF)  marks.  This
32723                one most likely was not properly terminated.
32724 
32725 
32726 restore(TAPE_SET)              565            08/03/23     MR12.7^L
32727 
32728 
32729      Action:   No operator action is required.  Unless it is felt
32730                that  the tape  is properly  terminated, in  which
32731                case  the restore can  be restarted and  this tape
32732                re-read.
32733 
32734 
32735 
32736                [bce_save.pl1]
32737                restore(TAPE_SET):   Clearing  unused  VTOC region
32738                (records BEGIN_REC - END_REC) on PV_NAME.
32739 
32740 
32741      Stream:   BOS Typewriter.
32742 
32743      Time:     System Intialization.
32744 
32745      Meaning:  Just an  informative message.  The  unused records
32746                in  the  VTOC  region  are  zero  cleared to avoid
32747                having erroneous VTOCEs left laying around.
32748 
32749      Action:   No operator action is required.
32750 
32751 
32752                [bce_save.pl1]
32753                restore(TAPE_SET):    Device  TAPE_DEV   is  being
32754                removed from the tape device list.
32755 
32756 
32757      Stream:   BOS Typewriter.
32758 
32759      Time:     System Intialization.
32760 
32761      Meaning:  The TAPE_DEV has returned a status indicating that
32762                it is unable to be used.
32763 
32764      Action:   No operator action is required.
32765 
32766 
32767                [bce_save_util_.pl1]
32768                restore(TAPE_SET):     Device   type    mis-match.
32769                PV_NAME  is on  a DEV_TYPE,  but was  saved from a
32770                DEV_TYPE.
32771 
32772 
32773 
32774      Stream:   BOS Typewriter.
32775 
32776      Time:     System Intialization.
32777 
32778      Meaning:  The program  is unable to restore  the contents of
32779                the  PV because  the disk  device currently  being
32780                used is different than the  one in use when the PV
32781 
32782 
32783 
32784 restore(TAPE_SET)              566            08/03/23     MR12.7^L
32785 
32786 
32787                was saved.  Only partitions can be restored to PVs
32788                mounted on different devices.
32789 
32790      Action:   Follow normal recovery procedures.
32791 
32792 
32793                [bce_save.pl1]
32794                restore(TAPE_SET):   End  of  Information  without
32795                detecting TAPE_EOR record.
32796 
32797 
32798      Stream:   BOS Typewriter.
32799 
32800      Time:     System Intialization.
32801 
32802      Meaning:  Multiple   End-of-File  (EOF)   marks  have   been
32803                detected,    without    previously    reading   an
32804                End-of-Reel (EOR) record.
32805 
32806      Action:   No operator action is required.  Unless it is felt
32807                that  the tape  is properly  terminated, in  which
32808                case  the restore can  be restarted and  this tape
32809                re-read.
32810 
32811 
32812 
32813                [bce_save.pl1]
32814                restore(TAPE_SET):   Error,  tape  on  TAPE_DEV is
32815                part of the "OTHER_TAPE_SET" set.
32816 
32817 
32818      Stream:   BOS Typewriter.
32819 
32820      Time:     System Intialization.
32821 
32822      Meaning:  The tape just read is not part of this tape set.
32823 
32824      Action:   Mount a  tape on the  device that is  part of this
32825                tape set.
32826 
32827 
32828                [bce_save.pl1]
32829                restore(TAPE_SET):     Incorrect   tape    number.
32830                Expected tape# TAPE_NUMBER.
32831 
32832 
32833      Stream:   BOS Typewriter.
32834 
32835      Time:     System Intialization.
32836 
32837      Meaning:  An internal tape number tracking mechanism is used
32838                and  the tape  that was  just read  does not match
32839                what the program expects to be on the device.
32840 
32841 
32842 restore(TAPE_SET)              567            08/03/23     MR12.7^L
32843 
32844 
32845      Action:   Mount the correct tape on the device.
32846 
32847 
32848                [bce_save.pl1]
32849                restore(TAPE_SET):   MAJOR_STATUS,  SUB_STATUS  on
32850                TAPE_DEV.
32851 
32852 
32853      Stream:   BOS Typewriter.
32854 
32855      Time:     System Intialization.
32856 
32857      Meaning:  An error has occured while attempting to do I/O to
32858                the tape device.
32859 
32860      Action:   Follow normal recovery procedures.
32861 
32862 
32863                [bce_save_util_.pl1]
32864                restore(TAPE_SET):    MULTICS_VOL_ID  PV_NAME   on
32865                DISK_DEV Last updated:  DATE_TIME
32866 
32867 
32868 
32869      Stream:   BOS Typewriter.
32870 
32871      Time:     System Intialization.
32872 
32873      Meaning:  Just an informative message.
32874 
32875      Action:   No operator action is required.
32876 
32877 
32878                [bce_save_util_.pl1]
32879                restore(TAPE_SET):   No partitions were  saved for
32880                volume PV_NAME.  Removing from PV list.
32881 
32882 
32883      Stream:   BOS Typewriter.
32884 
32885      Time:     System Intialization.
32886 
32887      Meaning:  A  request has  been made  to restore  one or more
32888                partitions on PV_NAME, but the save tape indicates
32889                that no partitions were saved.
32890 
32891      Action:   Remove  the partition  reference from  the control
32892                file.
32893 
32894 
32895                [bce_save.pl1]
32896                restore(TAPE_SET):   No Physical  Volumes left  to
32897                restore.
32898 
32899 
32900 restore(TAPE_SET)              568            08/03/23     MR12.7^L
32901 
32902 
32903      Stream:   BOS Typewriter.
32904 
32905      Time:     System Intialization.
32906 
32907      Meaning:  For  various reasons  all of  the physical volumes
32908                have been removed from the list of volumes.
32909 
32910      Action:   No operator action is required.
32911 
32912 
32913                [bce_save.pl1]
32914                restore(TAPE_SET):  No room to describe PV PV_NAME
32915                for part PARTITION_NAME.
32916 
32917 
32918      Stream:   BOS Typewriter.
32919 
32920      Time:     System Intialization.
32921 
32922      Meaning:  The maximum number of physical volumes that can be
32923                handled by the program has been exceeded.
32924 
32925      Action:   The  number  of  physical  volumes  defined in the
32926                control file(s) must be reduced.
32927 
32928 
32929 
32930                [bce_save.pl1]
32931                restore(TAPE_SET):  No usable tape devices left in
32932                list.
32933 
32934 
32935      Stream:   BOS Typewriter.
32936 
32937      Time:     System Intialization.
32938 
32939      Meaning:  For various  reasons all of the  tape devices have
32940                been  removed from  the list  of available devices
32941                for this tape set.
32942 
32943      Action:   Follow normal recovery procedures.
32944 
32945 
32946                [bce_save.pl1]
32947                restore(TAPE_SET):  No usable tape drives left.
32948 
32949 
32950      Stream:   BOS Typewriter.
32951 
32952      Time:     System Intialization.
32953 
32954 
32955 
32956 
32957 
32958 restore(TAPE_SET)              569            08/03/23     MR12.7^L
32959 
32960 
32961      Meaning:  For various  reasons all of the  tape devices have
32962                been  removed from  the list  of available devices
32963                for this tape set.
32964 
32965      Action:   Follow normal recovery procedures.
32966 
32967 
32968                [bce_save_util_.pl1]
32969                restore(TAPE_SET):  Only partitions were saved for
32970                volume PV_NAME.
32971 
32972 
32973      Stream:   BOS Typewriter.
32974 
32975      Time:     System Intialization.
32976 
32977      Meaning:  A request to restore the contents of a PV has been
32978                made,  but when the  PV was saved  only partitions
32979                were included.
32980 
32981      Action:   Correct the control file(s) accordingly.
32982 
32983 
32984                [bce_save_util_.pl1]
32985                restore(TAPE_SET):   Partition  PARTITION_NAME  is
32986                not defined on PV_NAME.
32987 
32988 
32989      Stream:   BOS Typewriter.
32990 
32991      Time:     System Intialization.
32992 
32993      Meaning:  A request  to restore specific partition  has been
32994                made, but the partition does not exist of the PV.
32995 
32996      Action:   Correct the control file(s) accordingly.
32997 
32998 
32999                [bce_save_util_.pl1]
33000                restore(TAPE_SET):   Partition  PARTITION_NAME  on
33001                PV_NAME was not saved.
33002 
33003 
33004      Stream:   BOS Typewriter.
33005 
33006      Time:     System Intialization.
33007 
33008      Meaning:  A request  was made to restore a  partition from a
33009                PV,  but the  partition was  not saved  as part of
33010                this tape set.
33011 
33012      Action:   Correct the control file(s) accordingly.
33013 
33014 
33015 
33016 restore(TAPE_SET)              570            08/03/23     MR12.7^L
33017 
33018 
33019 
33020 
33021                [bce_save.pl1]
33022                restore(TAPE_SET):   Partition  PARTITION_NAME  on
33023                PV_NAME,  record  REC_NUM,  on  tape#  TAPE_NUMBER
33024                (TAPE_DEV)
33025 
33026 
33027      Stream:   BOS Typewriter.
33028 
33029      Time:     System Intialization.
33030 
33031      Meaning:  Just an informative message.
33032 
33033      Action:   No operator action is required.
33034 
33035 
33036                [bce_save.pl1]
33037                restore(TAPE_SET):   Partition PARTITION_NAME  was
33038                not defined when PV_NAME was saved.
33039 
33040 
33041      Stream:   BOS Typewriter.
33042 
33043      Time:     System Intialization.
33044 
33045      Meaning:  A restore of a partition has been requested in the
33046                control file, but the  partition was not requested
33047                to be saved when the tape was made.
33048 
33049      Action:   Remove  the partition  reference from  the control
33050                file.
33051 
33052 
33053                [bce_save.pl1]
33054                restore(TAPE_SET):     Partition   PARTITION_NAME,
33055                record REC_NUM, on tape# TAPE_NUMBER (TAPE_DEV)
33056 
33057 
33058      Stream:   BOS Typewriter.
33059 
33060      Time:     System Intialization.
33061 
33062      Meaning:  Just an informative message.
33063 
33064      Action:   No operator action is required.
33065 
33066 
33067                [bce_save.pl1]
33068                restore(TAPE_SET):  Please mount tape# TAPE_NUMBER
33069                on TAPE_DEV.
33070 
33071 
33072 
33073 
33074 restore(TAPE_SET)              571            08/03/23     MR12.7^L
33075 
33076 
33077      Stream:   BOS Typewriter (sounds beeper)
33078 
33079      Time:     System Intialization.
33080 
33081      Meaning:  Just an informative message.
33082 
33083      Action:   Mount tape on the device.
33084 
33085 
33086                [bce_save.pl1]
33087                restore(TAPE_SET):   Please mount the  "Info" tape
33088                on TAPE_DEV.
33089 
33090 
33091      Stream:   BOS Typewriter (sounds beeper)
33092 
33093      Time:     System Intialization.
33094 
33095      Meaning:  Just an informative message.
33096 
33097      Action:   Mount the tape on the device.
33098 
33099 
33100                [bce_save.pl1]
33101                restore(TAPE_SET):   Please  mount  the  "restart"
33102                tape on TAPE_DEV.
33103 
33104 
33105      Stream:   BOS Typewriter (sounds beeper)
33106 
33107      Time:     System Intialization.
33108 
33109      Meaning:  Just an informative message.
33110 
33111      Action:   Mount the tape on the device.
33112 
33113 
33114                [bce_save_util_.pl1]
33115                restore(TAPE_SET):     Please   pre-mount    tape#
33116                TAPE_NUMBER on TAPE_DEV.
33117 
33118 
33119      Stream:   BOS Typewriter.
33120 
33121      Time:     System Intialization.
33122 
33123      Meaning:  The  program is  able to  look ahead  and find the
33124                tape  that  will  be  required  next.   This is an
33125                informative  message that   allows the  restore to
33126                move at a faster pace.
33127 
33128      Action:   Mount the specified tape on the specified device.
33129 
33130 
33131 
33132 restore(TAPE_SET)              572            08/03/23     MR12.7^L
33133 
33134 
33135 
33136 
33137                [bce_save.pl1]
33138                restore(TAPE_SET):  Readjusting tape sequence # to
33139                REC_NUM.
33140 
33141 
33142      Stream:   BOS Typewriter.
33143 
33144      Time:     System Intialization.
33145 
33146      Meaning:  The  missing  record  previously  reported  by the
33147                "Record  sequence error  ..."  message  can not be
33148                found.   The  internal  tape  sequence  counter is
33149                corrected and processing continues as normal.
33150 
33151      Action:   No operator action is required.
33152 
33153 
33154                [bce_save.pl1]
33155                restore(TAPE_SET):  Record sequence error on tape#
33156                TAPE_NUMBER   (TAPE_DEV),  should   be  record   #
33157                REC_NUM, was record # REC_NUM.
33158 
33159 
33160 
33161      Stream:   BOS Typewriter.
33162 
33163      Time:     System Intialization.
33164 
33165      Meaning:  Informative  message that  the sequence  number on
33166                the  tape is  out of  sync with  what the  program
33167                expects.  If the WAS is  only one record more than
33168                the S/B then the  program will attempt to relocate
33169                the missing record by  backspacing two records and
33170                rereading the records.
33171 
33172      Action:   No operator action is required.
33173 
33174 
33175                [bce_save.pl1]
33176                restore(TAPE_SET):   Relocated   tape  sequence  #
33177                REC_NUM
33178 
33179 
33180      Stream:   BOS Typewriter.
33181 
33182      Time:     System Intialization.
33183 
33184      Meaning:  The  missing  record  previously  reported  by the
33185                "Record  sequence  error  ..."   message  has been
33186                found.  Processing continues as normal.
33187 
33188 
33189 
33190 restore(TAPE_SET)              573            08/03/23     MR12.7^L
33191 
33192 
33193      Action:   No operator action is required.
33194 
33195 
33196                [bce_save_util_.pl1]
33197                restore(TAPE_SET):   Removing volume  PV_NAME from
33198                PV list, because all partitions were removed.
33199 
33200 
33201 
33202      Stream:   BOS Typewriter.
33203 
33204      Time:     System Intialization.
33205 
33206      Meaning:  It is  nolonger necessary for the  program to keep
33207                track  of  the  PV,  since  all  of  the partition
33208                requests have been removed.
33209 
33210      Action:   Correct the control files accordingly.
33211 
33212 
33213                [bce_save.pl1]
33214                restore(TAPE_SET):  restore complete...
33215 
33216 
33217      Stream:   BOS Typewriter.
33218 
33219      Time:     System Intialization.
33220 
33221      Meaning:  Just an informative message.
33222 
33223      Action:   No operator action is required.
33224 
33225 
33226                [bce_save.pl1]
33227                restore(TAPE_SET):   Restore of volume  PV_NAME on
33228                DISK_DEV complete.
33229 
33230 
33231      Stream:   BOS Typewriter.
33232 
33233      Time:     System Intialization.
33234 
33235      Meaning:  Just an informative message.
33236 
33237      Action:   No operator action is required.
33238 
33239 
33240                [bce_save.pl1]
33241                restore(TAPE_SET):   Skipping  volume  PV_NAME  on
33242                DISK_DEV, restore complete.
33243 
33244 
33245      Stream:   BOS Typewriter.
33246 
33247 
33248 restore(TAPE_SET)              574            08/03/23     MR12.7^L
33249 
33250 
33251      Time:     System Intialization.
33252 
33253      Meaning:  Just an informative message.
33254 
33255      Action:   No operator action is required.
33256 
33257 
33258                [bce_save.pl1]
33259                restore(TAPE_SET):   Starting from  volume PV_NAME
33260                on DISK_DEV.
33261 
33262 
33263      Stream:   BOS Typewriter.
33264 
33265      Time:     System Intialization.
33266 
33267      Meaning:  Just an informative message.
33268 
33269      Action:   No operator action is required.
33270 
33271 
33272                [bce_save.pl1]
33273                restore(TAPE_SET):   Tape  on  TAPE_DEV  does  not
33274                contain a supported tape label version.
33275 
33276 
33277      Stream:   BOS Typewriter.
33278 
33279      Time:     System Intialization.
33280 
33281      Meaning:  The tape  contains a tape version  identifier that
33282                is nolonger supported.
33283 
33284      Action:   Use   the  "restore   -display_info_tape  tapX_NN"
33285                option to display the tape.
33286 
33287 
33288 
33289                [bce_save.pl1]
33290                restore(TAPE_SET):   Tape  on  TAPE_DEV  does  not
33291                contain a valid label.
33292 
33293 
33294      Stream:   BOS Typewriter.
33295 
33296      Time:     System Intialization.
33297 
33298      Meaning:  The  tape just  read is  not a  valid save/restore
33299                tape.
33300 
33301      Action:   Follow normal recovery procedures.
33302 
33303 
33304 
33305 
33306 restore(TAPE_SET)              575            08/03/23     MR12.7^L
33307 
33308 
33309                [bce_save.pl1]
33310                restore(TAPE_SET):  Tape  on TAPE_DEV is  not part
33311                of this set.
33312 
33313 
33314      Stream:   BOS Typewriter.
33315 
33316      Time:     System Intialization.
33317 
33318      Meaning:  The tape  just read contains a  different tape set
33319                name than what is currently being handled, via the
33320                control file.
33321 
33322      Action:   Follow normal recovery procedures.
33323 
33324 
33325                [bce_save_util_.pl1]
33326                restore(TAPE_SET):   Tape  subsystem  "SUB_SYS" is
33327                not defined in the config.
33328 
33329 
33330      Stream:   BOS Typewriter.
33331 
33332      Time:     System Intialization.
33333 
33334      Meaning:  No  "prph"  entry  could  be  found  for  the tape
33335                subsystem.
33336 
33337      Action:   Correct   config_deck   or   save/restore  control
33338                file(s) to indicate proper tape subsystem.
33339 
33340 
33341 
33342                [bce_save.pl1]
33343                restore(TAPE_SET):  Tape# TAPE_NUMBER on TAPE_DEV,
33344                created DATE_TIME
33345 
33346 
33347      Stream:   BOS Typewriter.
33348 
33349      Time:     System Intialization.
33350 
33351      Meaning:  Just an informative message.
33352 
33353      Action:   No operator action is required.
33354 
33355 
33356                [bce_save.pl1]
33357                restore(TAPE_SET):   The following  tape device(s)
33358                will be used:
33359 
33360 
33361      Stream:   BOS Typewriter.
33362 
33363 
33364 restore(TAPE_SET)              576            08/03/23     MR12.7^L
33365 
33366 
33367      Time:     System Intialization.
33368 
33369      Meaning:  Just an informative message.
33370 
33371      Action:   No operator action is required.
33372 
33373 
33374                [bce_save.pl1]
33375                restore(TAPE_SET):   Time-out waiting  for special
33376                interrupt.
33377 
33378 
33379      Stream:   BOS Typewriter.
33380 
33381      Time:     System Intialization.
33382 
33383      Meaning:  The program was waiting for a special to come from
33384                the device,  but none was recieved  in the alloted
33385                time.
33386 
33387      Action:   Follow normal recovery procedures.
33388 
33389 
33390                [bce_save_util_.pl1]
33391                restore(TAPE_SET):      Unable      to     restore
33392                "PARTITION_NAME"  partition.   Internal  partition
33393                list full.
33394 
33395 
33396 
33397      Stream:   BOS Typewriter.
33398 
33399      Time:     System Intialization.
33400 
33401      Meaning:  More  partitions  have  been  requested  than  the
33402                program can handle.
33403 
33404      Action:   Change control files to reduce the number defined,
33405                possibly  by breaking  them up  into seperate tape
33406                sets.
33407 
33408 
33409 
33410                [bce_save_util_.pl1]
33411                restore(TAPE_SET):      Unable      to     restore
33412                "PARTITION_NAME" partition.   N partitions already
33413                defined
33414 
33415 
33416 
33417      Stream:   BOS Typewriter.
33418 
33419      Time:     System Intialization.
33420 
33421 
33422 restore(TAPE_SET)              577            08/03/23     MR12.7^L
33423 
33424 
33425      Meaning:  An attempt has been made  to restore more than the
33426                N maximum partitions allowed.
33427 
33428      Action:   Change  control  files(s)  to  reduce  the  number
33429                requested.
33430 
33431 
33432                [bce_save_util_.pl1]
33433                restore(TAPE_SET):    Unable   to   restore   only
33434                partitions.
33435 
33436 
33437      Stream:   BOS Typewriter.
33438 
33439      Time:     System Intialization.
33440 
33441      Meaning:  A request to restore partition information on this
33442                PV was made,  but the PV does not  contain a vaild
33443                label to locate the partition information.  The PV
33444                is removed from the restore list.
33445 
33446      Action:   Follow normal recovery procedures.
33447 
33448 
33449                [bce_save.pl1]
33450                restore(TAPE_SET):   Unable  to   set  density  on
33451                TAPE_DEV.
33452 
33453 
33454      Stream:   BOS Typewriter.
33455 
33456      Time:     System Intialization.
33457 
33458      Meaning:  The program was unable to set the required density
33459                of the tape device.
33460 
33461      Action:   Follow normal recovery procedures.
33462 
33463 
33464                [bce_save.pl1]
33465                restore(TAPE_SET):   Unloading  "Info"  tape  from
33466                TAPE_DEV, REC_CNT records (ERR_CNT errors)
33467 
33468 
33469      Stream:   BOS Typewriter.
33470 
33471      Time:     System Intialization.
33472 
33473      Meaning:  Just an informative message.
33474 
33475      Action:   No operator action is required.
33476 
33477 
33478 
33479 
33480 restore(TAPE_SET)              578            08/03/23     MR12.7^L
33481 
33482 
33483                [bce_save.pl1]
33484                restore(TAPE_SET):   Unloading  tape#  TAPE_NUMBER
33485                from TAPE_DEV, REC_CNT records (ERR_CNT errors)
33486 
33487 
33488      Stream:   BOS Typewriter.
33489 
33490      Time:     System Intialization.
33491 
33492      Meaning:  Just an informative message.
33493 
33494      Action:   No operator action is required.
33495 
33496 
33497                [bce_save.pl1]
33498                restore(TAPE_SET):   Unloading  TAPE_DEV,  REC_CNT
33499                records (ERR_CNT errors)
33500 
33501 
33502      Stream:   BOS Typewriter.
33503 
33504      Time:     System Intialization.
33505 
33506      Meaning:  Just an informative message.
33507 
33508      Action:   No operator action is required.
33509 
33510 
33511                [bce_save_util_.pl1]
33512                restore(TAPE_SET):   Volume on  DISK_DEV is  not a
33513                MULTICS_VOL_ID.
33514 
33515 
33516      Stream:   BOS Typewriter.
33517 
33518      Time:     System Intialization.
33519 
33520      Meaning:  Informative message to let  the operator know that
33521                the  volume  does  not  currently  contain a valid
33522                Multics label.
33523 
33524      Action:   No operator action is required.
33525 
33526 
33527                [bce_save_util_.pl1]
33528                restore(TAPE_SET):   Volume PV_NAME  not found  in
33529                tape label.  Removing from PV list.
33530 
33531 
33532 
33533      Stream:   BOS Typewriter.
33534 
33535      Time:     System Intialization.
33536 
33537 
33538 restore(TAPE_SET)              579            08/03/23     MR12.7^L
33539 
33540 
33541      Meaning:  A request was made to restore a PV, but the PV was
33542                not saved as part of this tape set.
33543 
33544      Action:   Correct the control file(s) accordingly.
33545 
33546 
33547                [bce_save_util_.pl1]
33548                restore(TAPE_SET):   Volume  PV_NAME  will  become
33549                NEW_PV_NAME, as requested.
33550 
33551 
33552      Stream:   BOS Typewriter.
33553 
33554      Time:     System Intialization.
33555 
33556      Meaning:  The  PV to be  restored currently has  a dirrerent
33557                label than  that to be restored.  This  is only an
33558                informative message to make  the user aware of the
33559                change.
33560 
33561      Action:   No operator action is required.
33562 
33563 
33564                [bce_save.pl1]
33565                restore(TAPE_SET):     Volume   PV_NAME,    record
33566                REC_NUM, on tape# TAPE_NUMBER (TAPE_DEV)
33567 
33568 
33569      Stream:   BOS Typewriter.
33570 
33571      Time:     System Intialization.
33572 
33573      Meaning:  Just an informative message.
33574 
33575      Action:   No operator action is required.
33576 
33577 
33578                [bce_save.pl1]
33579                restore(TAPE_SET):    Waiting   for   special   on
33580                TAPE_DEV.
33581 
33582 
33583      Stream:   BOS Typewriter.
33584 
33585      Time:     System Intialization.
33586 
33587      Meaning:  Just an informative message.
33588 
33589      Action:   No operator action is required.
33590 
33591 
33592                [bce_save.pl1]
33593 
33594 
33595 
33596 restore(TAPE_SET)              580            08/03/23     MR12.7^L
33597 
33598 
33599                restore(TAPE_SET):         Zeroing       partition
33600                PARTITION_NAME on PV_NAME, record REC_NUM.
33601 
33602 
33603      Stream:   BOS Typewriter.
33604 
33605      Time:     System Intialization.
33606 
33607      Meaning:  Just an informative message.
33608 
33609      Action:   No operator action is required.
33610 
33611 
33612                [bce_save_util_.pl1]
33613                restore:  Attaching TAPE_DEV.  ERR_MESSAGE
33614 
33615 
33616      Stream:   BOS Typewriter (sounds beeper)
33617 
33618      Time:     System Intialization.
33619 
33620      Meaning:  IOI has returned a non-zero error code in response
33621                to a request to assign TAPE_DEV.
33622 
33623      Action:   Follow normal recovery procedures.
33624 
33625 
33626                [bce_save.pl1]
33627                restore:  bce_ioi_post_seg.  ERR_MESSAGE
33628 
33629 
33630      Stream:   BOS Typewriter (sounds beeper)
33631 
33632      Time:     System Intialization.
33633 
33634      Meaning:  The  program was  unable to  get a  pointer to the
33635                above  segment.  This  indicates a  logic error in
33636                the   supervisor,  or   CPU  or   memory  hardware
33637                problems.
33638 
33639      Action:   Contact the system programming staff.
33640 
33641 
33642                [bce_save.pl1]
33643                restore:  bootload_disk_post_seg.  ERR_MESSAGE
33644 
33645 
33646      Stream:   BOS Typewriter (sounds beeper)
33647 
33648      Time:     System Intialization.
33649 
33650      Meaning:  The  program was  unable to  get a  pointer to the
33651                above  segment.  This  indicates a  logic error in
33652 
33653 
33654 restore                        581            08/03/23     MR12.7^L
33655 
33656 
33657                the   supervisor,  or   CPU  or   memory  hardware
33658                problems.
33659 
33660      Action:   Contact the system programming staff.
33661 
33662 
33663                [bce_save_util_.pl1]
33664                restore:   Could  not  read  label  of  PV_NAME on
33665                DISK_DEV.  ERR_MESSAGE
33666 
33667 
33668      Stream:   BOS Typewriter (sounds beeper)
33669 
33670      Time:     System Intialization.
33671 
33672      Meaning:  The volume label  of the PV could not  be read due
33673                to the error given in ERR_MESSAGE.
33674 
33675      Action:   A operator query  is done to find out  if the read
33676                should be retried or the PV removed from the list.
33677 
33678 
33679 
33680                [bce_save.pl1]
33681                restore:    Getting  tape   label  temp   segment.
33682                ERR_MESSAGE
33683 
33684 
33685      Stream:   BOS Typewriter (sounds beeper)
33686 
33687      Time:     System Intialization.
33688 
33689      Meaning:  An  error  occured  while   attempting  to  get  a
33690                temporary   segment  to    hold  the   tape  label
33691                information.
33692 
33693      Action:   Contact the system programming staff.
33694 
33695 
33696                [bce_save_util_.pl1]
33697                restore:     Initiating   CONTROL_FILE_NAME    for
33698                set-TAPE_SET_IDX ERR_MESSAGE
33699 
33700 
33701      Stream:   BOS Typewriter (sounds beeper)
33702 
33703      Time:     System Intialization.
33704 
33705      Meaning:  An error was detected while initiating the restore
33706                control file.
33707 
33708      Action:   Contact the system programming staff.  $recover
33709 
33710 
33711 
33712 restore                        582            08/03/23     MR12.7^L
33713 
33714 
33715 
33716 
33717                [bce_save.pl1]
33718                restore:  PV_NAME ERR_MESSAGE
33719 
33720 
33721      Stream:   BOS Typewriter (sounds beeper)
33722 
33723      Time:     System Intialization.
33724 
33725      Meaning:  The   call   to   bootload_disk_io$test_done   has
33726                returned a non-zero error code.
33727 
33728      Action:   Contact the system programming staff.  $recover
33729 
33730 
33731                [bce_save.pl1]
33732                restore:  pvt.  ERR_MESSAGE
33733 
33734 
33735      Stream:   BOS Typewriter (sounds beeper)
33736 
33737      Time:     System Intialization.
33738 
33739      Meaning:  The  program was  unable to  get a  pointer to the
33740                above  segment.  This  indicates a  logic error in
33741                the   supervisor,  or   CPU  or   memory  hardware
33742                problems.
33743 
33744      Action:   Contact the system programming staff.
33745 
33746 
33747                [bce_save.pl1]
33748                restore:  Restarting restore  of set "TAPE_SET" on
33749                TAPE_DEV.
33750 
33751 
33752      Stream:   BOS Typewriter.
33753 
33754      Time:     System Intialization.
33755 
33756      Meaning:  Just an informative message.
33757 
33758      Action:   No operator action is required.
33759 
33760 
33761                [bce_save_util_.pl1]
33762                restore:   Setting  max  workspace  for  TAPE_DEV.
33763                ERR_MESSAGE
33764 
33765 
33766      Stream:   BOS Typewriter (sounds beeper)
33767 
33768 
33769 
33770 restore                        583            08/03/23     MR12.7^L
33771 
33772 
33773      Time:     System Intialization.
33774 
33775      Meaning:  IOI has returned a non-zero error code in response
33776                to  a request  to set  the max  workspace size for
33777                TAPE_DEV.
33778 
33779      Action:   Contact the system programming staff.
33780 
33781 
33782                [bce_save.pl1]
33783                restore:   Setting  status   index  for  TAPE_DEV.
33784                ERR_MESSAGE
33785 
33786 
33787      Stream:   BOS Typewriter (sounds beeper)
33788 
33789      Time:     System Intialization.
33790 
33791      Meaning:  IOI has returned a  non-zero error, which has been
33792                expanded in ERR_MESSAGE.
33793 
33794      Action:   Contact the system programming staff.
33795 
33796 
33797                [bce_save_util_.pl1]
33798                restore:   Setting  up   workspace  for  TAPE_DEV.
33799                ERR_MESSAGE
33800 
33801 
33802      Stream:   BOS Typewriter (sounds beeper)
33803 
33804      Time:     System Intialization.
33805 
33806      Meaning:  IOI  has returned a  non-zero error code  from the
33807                request to create a workspace for TAPE_DEV.
33808 
33809      Action:   Contact the system programming staff.
33810 
33811 
33812                [bce_save_util_.pl1]
33813                restore:  si ERR_MESSAGE
33814 
33815 
33816      Stream:   BOS Typewriter (sounds beeper)
33817 
33818      Time:     System Intialization.
33819 
33820      Meaning:  An  error has  been found  with the  internal "si"
33821                structure.This  indicates  a  logic  error  in the
33822                supervisor, or CPU or memory hardware problems.
33823 
33824      Action:   Contact the system programming staff.
33825 
33826 
33827 
33828 restore                        584            08/03/23     MR12.7^L
33829 
33830 
33831 
33832 
33833                [bce_save_util_.pl1]
33834                restore:  sri ERR_MESSAGE
33835 
33836 
33837      Stream:   BOS Typewriter (sounds beeper)
33838 
33839      Time:     System Intialization.
33840 
33841      Meaning:  An  error has been  found with the  internal "sri"
33842                structure.This  indicates  a  logic  error  in the
33843                supervisor, or CPU or memory hardware problems.
33844 
33845      Action:   Contact the system programming staff.
33846 
33847 
33848                [bce_save.pl1]
33849                restore:  Stopping restore of set "TAPE_SET".
33850 
33851 
33852      Stream:   BOS Typewriter.
33853 
33854      Time:     System Intialization.
33855 
33856      Meaning:  Just an informative message.
33857 
33858      Action:   No operator action is required.
33859 
33860 
33861                [bce_save_util_.pl1]
33862                restore:  TAPE_DEV ERR_MESSAGE
33863 
33864 
33865      Stream:   BOS Typewriter (sounds beeper)
33866 
33867      Time:     System Intialization.
33868 
33869      Meaning:  An error occured while scanning the tape subsystem
33870                survey data.
33871 
33872      Action:   Follow normal recovery procedures.
33873 
33874 
33875                [bce_save.pl1]
33876                restore:  tape_error_data.  ERR_MESSAGE
33877 
33878 
33879      Stream:   BOS Typewriter (sounds beeper)
33880 
33881      Time:     System Intialization.
33882 
33883 
33884 
33885 
33886 restore                        585            08/03/23     MR12.7^L
33887 
33888 
33889      Meaning:  The  program was  unable to  get a  pointer to the
33890                above  segment.  This  indicates a  logic error in
33891                the   supervisor,  or   CPU  or   memory  hardware
33892                problems.
33893 
33894      Action:   Contact the system programming staff.
33895 
33896 
33897                [bce_save.pl1]
33898                restore:  Unassigning TAPE_DEV.  ERR_MESSAGE
33899 
33900 
33901      Stream:   BOS Typewriter (sounds beeper)
33902 
33903      Time:     System Intialization.
33904 
33905      Meaning:  IOI has returned a  non-zero error, which has been
33906                expanded in ERR_MESSAGE.
33907 
33908      Action:   Contact the system programming staff.
33909 
33910 
33911                [retv_copy.pl1]
33912                retv_copy:    deleting  PATH   without  recovering
33913                resources ERROR_MESSAGE
33914 
33915 
33916      Stream:   Logged in SYSERR log.
33917 
33918      Time:     Volume retrieval
33919 
33920      Meaning:  While   retrieving   a   segment,   the  retriever
33921                attempted  to  delete  an  old  copy  of a segment
33922                before  using a  newer one.   The deletion attempt
33923                failed.  Space may be wasted on the volume until a
33924                sweep_pv -gc is done.
33925 
33926      Action:   Note for volume administrator.
33927 
33928 
33929                [ring_alarm.pl1]
33930                ring_alarm$fault:  Reset admin privileges.
33931 
33932 
33933      Stream:   Logged in SYSERR log.
33934 
33935      Time:     While system is running.
33936 
33937      Meaning:  On exit from ring one,  one or more AIM privileges
33938                were still  set by privileged ring  1 code.  These
33939                are  reset,  and  the  following  log message from
33940                set_privileges  lists  them.    This  indicates  a
33941 
33942 
33943 
33944 ring_alarm$fault               586            08/03/23     MR12.7^L
33945 
33946 
33947                benign  bug  in  the  ring  one  program  that was
33948                running.
33949 
33950      Action:   Contact the system programming staff.
33951 
33952 
33953                [ring_alarm.pl1]
33954                ring_alarm$poll:  Mysterious ring alarm.
33955 
33956 
33957      Stream:   BOS Typewriter (Crashes system)
33958 
33959      Time:     While system is running.
33960 
33961      Meaning:  The ring alarm register was  set on exit from ring
33962                zero, but  no reason for  it was recorded  for the
33963                process.
33964 
33965      Action:   Contact the system programming staff.
33966 
33967 
33968                [ring_alarm.pl1]
33969                ring_alarm:   Fixed  validation  level  {on fault}
33970                from OLD to NEW.
33971 
33972 
33973      Stream:   BOS Typewriter (sounds beeper)
33974 
33975      Time:     While system is running.
33976 
33977      Meaning:  On exit  from ring zero, the  validation level was
33978                less than the ring that is being returned to.  The
33979                validation level is corrected to its value when it
33980                called  into  the  inner  ring.   This indicates a
33981                benign bug in the inner ring entry called.
33982 
33983      Action:   Contact the system programming staff.
33984 
33985 
33986                [rldr_arg_reader_.pl1]
33987                rldr_arg_reader_:  ARG:  ERROR_MESS
33988 
33989 
33990      Stream:   BOS Typewriter.
33991 
33992      Time:     While system is running.
33993 
33994      Meaning:  Invalid arguments were given to the reloader.
33995 
33996      Action:   Enter a corrected command line.
33997 
33998 
33999 
34000 
34001 
34002 rldr_check_pvol_               587            08/03/23     MR12.7^L
34003 
34004 
34005 
34006 
34007                [rldr_check_pvol_.pl1]
34008                rldr_check_pvol_:  Maximum access class mismatch
34009                rldr_check_pvol_:  Have  ACCESS_CLASS; Volog label
34010                requires ACCESS_CLASS
34011 
34012 
34013 
34014      Stream:   $rld_on
34015 
34016      Time:     $reload
34017 
34018      Meaning:  The maximum  access class for the  volume does not
34019                match the volume log.
34020 
34021      Action:   Enter a corrected command line.
34022 
34023 
34024                [rldr_check_pvol_.pl1]
34025                rldr_check_pvol_:  Minimum access class mismatch
34026                rldr_check_pvol_:  Have  ACCESS_CLASS; Volog label
34027                requires ACCESS_CLASS
34028 
34029 
34030 
34031      Stream:   $rld_on
34032 
34033      Time:     $reload
34034 
34035      Meaning:  The minimum  access class for the  volume does not
34036                match the volume log.
34037 
34038      Action:   Enter a corrected command line.
34039 
34040 
34041                [rldr_check_pvol_.pl1]
34042                rldr_check_pvol_:   Partition  NAME  not  found on
34043                physical volume
34044 
34045 
34046      Stream:   $rld_on
34047 
34048      Time:     $reload
34049 
34050      Meaning:  The  partition  NAME  is  missing  from the volume
34051                label.
34052 
34053      Action:   Reinitialize the volume correctly.
34054 
34055 
34056                [rldr_check_pvol_.pl1]
34057                rldr_check_pvol_:  Partition NAME size mismatch
34058 
34059 
34060 rldr_check_pvol_               588            08/03/23     MR12.7^L
34061 
34062 
34063                rldr_check_pvol_:   Have NN  records; Volog  label
34064                requires MM
34065 
34066 
34067 
34068      Stream:   $rld_on
34069 
34070      Time:     $reload
34071 
34072      Meaning:  The size for partition NAME does not match.
34073 
34074      Action:   Reinitialize the volume correctly.
34075 
34076 
34077                [rldr_check_pvol_.pl1]
34078                rldr_check_pvol_:  Reload may overflow volume
34079                rldr_check_pvol_:   Have NN  records; Volog  label
34080                requires NN records
34081 
34082 
34083 
34084      Stream:   $rld_on
34085 
34086      Time:     $reload
34087 
34088      Meaning:  The output volume is too small.
34089 
34090      Action:   Reinitialize it correctly with init_vol.
34091 
34092 
34093                [rldr_check_pvol_.pl1]
34094                rldr_check_pvol_:  Reload may overflow vtoc
34095                rldr_check_pvol_:   Have  NN  vtoce;  Volog  label
34096                requires NN vtoce
34097 
34098 
34099 
34100      Stream:   $rld_on
34101 
34102      Time:     $reload
34103 
34104      Meaning:  The output volume has too small a VTOC.
34105 
34106      Action:   Reinitialize the output volume with init_vol.
34107 
34108 
34109                [rldr_check_pvol_.pl1]
34110                rldr_check_pvol_:  Unitialized output volume
34111 
34112 
34113      Stream:   $rld_on
34114 
34115      Time:     $reload
34116 
34117 
34118 rldr_check_pvol_               589            08/03/23     MR12.7^L
34119 
34120 
34121      Meaning:  The  output   volume  must  be   initialized  with
34122                init_vol before use.
34123 
34124      Action:   Switch the output  volume to storage-system status
34125                with the sdu command and  then use init_vol to set
34126                it up.
34127 
34128 
34129 
34130                [rldr_check_pvol_.pl1]
34131                rldr_check_pvol_:  Volume mismatch
34132                rldr_check_pvol_:   Have PVNAME,pvid =  WWW; Volog
34133                label requires PVNAME,pvid = WWW
34134 
34135 
34136 
34137      Stream:   $rld_on
34138 
34139      Time:     $reload
34140 
34141      Meaning:  The output volume label  disagrees with the volume
34142                log.
34143 
34144      Action:   Reinitialize  the  output  volume  correctly  with
34145                init_vol.
34146 
34147 
34148                [rldr_label_.pl1]
34149                rldr_label_:   Incorrect  output  medium  mounted:
34150                ERROR_MESS
34151 
34152 
34153      Stream:   $rld_out
34154 
34155      Time:     $reload
34156 
34157      Meaning:  Someting is wrong with a reloader output volume.
34158 
34159      Action:   Mount a correct volume and try again.
34160 
34161 
34162                [rldr_label_.pl1]
34163                rldr_label_:  Label position failed:  ERROR_MESS
34164 
34165 
34166      Stream:   $rld_out
34167 
34168      Time:     $reload
34169 
34170      Meaning:  Someting is wrong with a reloader output volume.
34171 
34172      Action:   Mount a correct volume and try again.
34173 
34174 
34175 
34176 rldr_label_                    590            08/03/23     MR12.7^L
34177 
34178 
34179 
34180 
34181                [rldr_label_.pl1]
34182                rldr_label_:  Label read failed:  ERROR_MESS
34183 
34184 
34185      Stream:   $rld_out
34186 
34187      Time:     $reload
34188 
34189      Meaning:  Someting is wrong with a reloader output volume.
34190 
34191      Action:   Mount a correct volume and try again.
34192 
34193 
34194                [rldr_label_.pl1]
34195                rldr_label_:  Label write failed:  ERROR_MESS
34196 
34197 
34198      Stream:   $rld_out
34199 
34200      Time:     $reload
34201 
34202      Meaning:  Someting is wrong with a reloader output volume.
34203 
34204      Action:   Mount a correct volume and try again.
34205 
34206 
34207                [rldr_label_.pl1]
34208                rldr_label_:  Output volume  pvid MMMMMMMMMMMM not
34209                equal to online pvid NNNNNNNNNNNN for pv PPPPPPPP.
34210                Invalid volume identifier.
34211 
34212 
34213 
34214      Stream:   $rld_out
34215 
34216      Time:     $reload
34217 
34218      Meaning:  The PVID on the output  disk volume does not match
34219                the PVID  as recorded in  the pvolog for  the disk
34220                volume.  This  indicates that either the  label on
34221                the  PV  is  incorrect  or  the  pvolog segment is
34222                corrupted.
34223 
34224      Action:   Verify   the   PVID    using   output   from   the
34225                display_disk_label command.  If  the PVID from ddl
34226                output  is differnet  from that  reported for  the
34227                output volume,  use change_volume_registration and
34228                init_vol to correct the disk label.  If the online
34229                PVID  does not  match, use  the recover_volume_log
34230                command  to  retrieve  a  correct  pvolog segment.
34231                Retry the reload.
34232 
34233 
34234 rldr_label_                    591            08/03/23     MR12.7^L
34235 
34236 
34237 
34238 
34239                [rldr_output_.pl1]
34240                rldr_output_:   Output  volume  attachment failed:
34241                ERROR_MESS
34242 
34243 
34244      Stream:   $rld_out
34245 
34246      Time:     $reload
34247 
34248      Meaning:  This indicates a logic error in the supervisor, or
34249                CPU or memory hardware problems.
34250 
34251      Action:   Mount a different output volume and try again.
34252 
34253 
34254                [rldr_output_.pl1]
34255                rldr_output_:    Output  volume   opening  failed:
34256                ERROR_MESS
34257 
34258 
34259      Stream:   $rld_out
34260 
34261      Time:     $reload
34262 
34263      Meaning:  This indicates a logic error in the supervisor, or
34264                CPU or memory hardware problems.
34265 
34266      Action:   Mount a different output volume and try again.
34267 
34268 
34269                [rldr_report_.pl1]
34270                rldr_report_:  Error file NAME created
34271 
34272 
34273      Stream:   $rld_on
34274 
34275      Time:     $reload
34276 
34277      Meaning:  The reloader attempted to create an error file.
34278 
34279      Action:   No operator action is required.
34280 
34281 
34282                [rldr_report_.pl1]
34283                rldr_report_:     Error   opening    error   file:
34284                ERROR_MESS
34285 
34286 
34287      Stream:   $rld_on
34288 
34289      Time:     $reload
34290 
34291 
34292 rldr_report_                   592            08/03/23     MR12.7^L
34293 
34294 
34295      Meaning:  The reloader attempted to create an error file.
34296 
34297      Action:   No operator action is required.
34298 
34299 
34300                [rldr_report_.pl1]
34301                rldr_report_:    Unable  to  attach   error  file:
34302                ERROR_MESS
34303 
34304 
34305      Stream:   $rld_on
34306 
34307      Time:     $reload
34308 
34309      Meaning:  The reloader attempted to create an error file.
34310 
34311      Action:   No operator action is required.
34312 
34313 
34314                [rldr_volume_map_.pl1]
34315                rldr_volume_map_:  Attempt to deposit free record
34316 
34317 
34318      Stream:   $rld_out
34319 
34320      Time:     $reload
34321 
34322      Meaning:  An error was encountered  during reload volume map
34323                construction.  Reloading continues.
34324 
34325      Action:   No operator action is required.
34326 
34327 
34328                [rldr_volume_map_.pl1]
34329                rldr_volume_map_:  Attempt to deposit out of range
34330                address WWW
34331 
34332 
34333      Stream:   $rld_out
34334 
34335      Time:     $reload
34336 
34337      Meaning:  An error was encountered  during reload volume map
34338                construction.  Reloading continues.
34339 
34340      Action:   No operator action is required.
34341 
34342 
34343                [rldr_volume_map_.pl1]
34344                rldr_volume_map_:    Error  reading   volume  map:
34345                ERROR_MESS
34346 
34347 
34348 
34349 
34350 rldr_volume_map_               593            08/03/23     MR12.7^L
34351 
34352 
34353      Stream:   $rld_out
34354 
34355      Time:     $reload
34356 
34357      Meaning:  An error was encountered  during reload volume map
34358                construction.  Reloading continues.
34359 
34360      Action:   No operator action is required.
34361 
34362 
34363                [rldr_volume_map_.pl1]
34364                rldr_volume_map_:    Error  writing   volume  map:
34365                ERROR_MESS
34366 
34367 
34368      Stream:   $rld_out
34369 
34370      Time:     $reload
34371 
34372      Meaning:  An error was encountered  during reload volume map
34373                construction.  Reloading continues.
34374 
34375      Action:   No operator action is required.
34376 
34377 
34378                [rldr_volume_map_.pl1]
34379                rldr_volume_map_:      Map    position     failed:
34380                ERROR_MESS
34381 
34382 
34383      Stream:   $rld_out
34384 
34385      Time:     $reload
34386 
34387      Meaning:  An error was encountered  during reload volume map
34388                construction.  Reloading continues.
34389 
34390      Action:   No operator action is required.
34391 
34392 
34393                [rldr_volume_map_.pl1]
34394                rldr_volume_map_:      Map    position     failed:
34395                ERROR_MESS
34396 
34397 
34398      Stream:   $rld_out
34399 
34400      Time:     $reload
34401 
34402      Meaning:  An error was encountered  during reload volume map
34403                construction.  Reloading continues.
34404 
34405      Action:   No operator action is required.
34406 
34407 
34408 rldr_vtoc_buffer_              594            08/03/23     MR12.7^L
34409 
34410 
34411 
34412 
34413                [rldr_vtoc_buffer_.pl1]
34414                rldr_vtoc_buffer_:   Unable to  update vtoce  WWW:
34415                ERROR_MESS
34416 
34417 
34418      Stream:   $rld_out
34419 
34420      Time:     $reload
34421 
34422      Meaning:  An  error occurred   updating a  VTOCE.  Reloading
34423                continues.
34424 
34425      Action:   No operator action is required.
34426 
34427 
34428                [rldr_vtoc_header_.pl1]
34429                rldr_vtoc_header_:  VTOC header position failed
34430 
34431 
34432      Stream:   $rld_out
34433 
34434      Time:     $reload
34435 
34436      Meaning:  An error occurred writing  out the VTOC header for
34437                an output volume.
34438 
34439      Action:   Contact the system programming staff.
34440 
34441 
34442                [rldr_vtoc_header_.pl1]
34443                rldr_vtoc_header_:  VTOC header position failed
34444 
34445 
34446      Stream:   $rld_out
34447 
34448      Time:     $reload
34449 
34450      Meaning:  An error occurred writing  out the VTOC header for
34451                an output volume.
34452 
34453      Action:   Contact the system programming staff.
34454 
34455 
34456                [rldr_vtoc_header_.pl1]
34457                rldr_vtoc_header_:  VTOC header read failed
34458 
34459 
34460      Stream:   $rld_out
34461 
34462      Time:     $reload
34463 
34464 
34465 
34466 rldr_vtoc_header_              595            08/03/23     MR12.7^L
34467 
34468 
34469      Meaning:  An error occurred writing  out the VTOC header for
34470                an output volume.
34471 
34472      Action:   Contact the system programming staff.
34473 
34474 
34475                [rldr_vtoc_header_.pl1]
34476                rldr_vtoc_header_:  VTOC header write failed
34477 
34478 
34479      Stream:   $rld_out
34480 
34481      Time:     $reload
34482 
34483      Meaning:  An error occurred writing  out the VTOC header for
34484                an output volume.
34485 
34486      Action:   Contact the system programming staff.
34487 
34488 
34489                [rldr_vtoc_header_.pl1]
34490                rldr_vtoc_header_:  VTOC map position failed
34491 
34492 
34493      Stream:   $rld_out
34494 
34495      Time:     $reload
34496 
34497      Meaning:  An error occurred writing out  the VTOC map for an
34498                output volume.
34499 
34500      Action:   Contact the system programming staff.
34501 
34502 
34503                [rldr_vtoc_header_.pl1]
34504                rldr_vtoc_header_:  VTOC map read failed
34505 
34506 
34507      Stream:   $rld_out
34508 
34509      Time:     $reload
34510 
34511      Meaning:  An  error occurred  reading  the  VTOC map  for an
34512                output volume.
34513 
34514      Action:   Contact the system programming staff.
34515 
34516 
34517                [rldr_vtoc_header_.pl1]
34518                rldr_vtoc_header_:  VTOC map write failed
34519 
34520 
34521      Stream:   $rld_out
34522 
34523 
34524 rldr_vtoc_header_              596            08/03/23     MR12.7^L
34525 
34526 
34527      Time:     $reload
34528 
34529      Meaning:  An error occurred writing out  the VTOC map for an
34530                output volume.
34531 
34532      Action:   Contact the system programming staff.
34533 
34534 
34535                [salv_check_vtoce_.pl1]
34536                salv_check_vtoce_:  ERROR_MESSAGE.
34537 
34538 
34539      Stream:   Logged in SYSERR log.
34540 
34541      Time:     Salvaging
34542 
34543      Meaning:  An error occurred while checking VTOCEs.
34544 
34545      Action:   Contact the system programming staff.
34546 
34547 
34548                [salv_dir_checker_.pl1]
34549                salv_dir_checker_:  MESSAGE.
34550 
34551 
34552      Stream:   Logged in SYSERR log.
34553 
34554      Time:     Salvaging
34555 
34556      Meaning:  Various messages are  printed by salv_dir_checker_
34557                indicating  what  salvaging  is  taking place--ACL
34558                counts being changed,  entry counts being changed,
34559                unique  names supplied  for segments  with invalid
34560                names, etc.
34561 
34562      Action:   No operator action is required.
34563 
34564 
34565                [salv_dump_copy.pl1]
34566                salv_dump_copy:    Appending   SEGNAME   to   dump
34567                directory ERRORMESSAGE
34568 
34569 
34570      Stream:   Logged in SYSERR log.
34571 
34572      Time:     While system is running.
34573 
34574      Meaning:  The directory salvager could  not append a copy of
34575                a  directory being  salvaged or  the stack  at the
34576                time of salvage to the system dump directory.
34577 
34578 
34579 
34580 
34581 
34582 salv_dump_copy                 597            08/03/23     MR12.7^L
34583 
34584 
34585      Action:   Check  the ACL on  the system dump  directory, and
34586                site exec_coms  which set it.  Contact  the system
34587                programming staff._sa
34588 
34589 
34590 
34591                [salv_dump_copy.pl1]
34592                salv_dump_copy:  Initiating SEGNAME ERRORMESSAGE
34593 
34594 
34595      Stream:   Logged in SYSERR log.
34596 
34597      Time:     While system is running.
34598 
34599      Meaning:  The directory  salvager could not initiate  a copy
34600                of a  ring 0 stack or directory  being salvaged in
34601                the  system  dump  directory.   There  may  be ACL
34602                problems in the system dump directory.
34603 
34604      Action:   Contact the system programming staff._sa
34605 
34606 
34607                [salv_dump_copy.pl1]
34608                salv_dump_copy:  seg_fault_error copying PPPP into
34609                >dumps>SEGNAME
34610 
34611 
34612      Stream:   Logged in SYSERR log.
34613 
34614      Time:     While system is running.
34615 
34616      Meaning:  The directory salvager attempted  to create a copy
34617                of  a   segment  in  >dumps,  but   encountered  a
34618                seg_fault_error condition while attempting to copy
34619                it.  This is probably  caused by quota problems in
34620                >dumps  or  insufficient   space  on  the  logical
34621                volume.
34622 
34623      Action:   Contact the system programming staff._sa
34624 
34625 
34626                [salv_caller.pl1]
34627                salvage_dirs:  decimal number  required for level,
34628                not BLAH
34629 
34630 
34631      Stream:   Initializer process output.
34632 
34633      Time:     In response to an operator command.
34634 
34635      Meaning:  Incorrect arguments were specified.
34636 
34637      Action:   Enter a corrected command line.
34638 
34639 
34640 salvage_dirs                   598            08/03/23     MR12.7^L
34641 
34642 
34643 
34644 
34645                [salv_caller.pl1]
34646                salvage_dirs:  depth must be between 0 and 15
34647 
34648 
34649      Stream:   Initializer process output.
34650 
34651      Time:     In response to an operator command.
34652 
34653      Meaning:  Incorrect arguments were specified.
34654 
34655      Action:   Enter a corrected command line.
34656 
34657 
34658                [salv_caller.pl1]
34659                salvage_dirs:  ERROR_MESSAGE
34660 
34661 
34662      Stream:   Initializer process output.
34663 
34664      Time:     In response to an operator command.
34665 
34666      Meaning:  Incorrect arguments were specified.
34667 
34668      Action:   Enter a corrected command line.
34669 
34670 
34671                [salv_caller.pl1]
34672                salvage_dirs:    ERROR_MESSAGE.     level   number
34673                required
34674 
34675 
34676      Stream:   Initializer process output.
34677 
34678      Time:     In response to an operator command.
34679 
34680      Meaning:  Incorrect arguments were specified.
34681 
34682      Action:   Enter a corrected command line.
34683 
34684 
34685                [salv_caller.pl1]
34686                salvage_dirs:   Inconsistent  arguments  have been
34687                specified
34688 
34689 
34690      Stream:   Initializer process output.
34691 
34692      Time:     In response to an operator command.
34693 
34694      Meaning:  Incorrect arguments were specified.
34695 
34696 
34697 
34698 salvage_dirs                   599            08/03/23     MR12.7^L
34699 
34700 
34701      Action:   Enter a corrected command line.
34702 
34703 
34704                [salv_caller.pl1]
34705                salvage_dirs:  must be in ring 1 for dir salv
34706 
34707 
34708      Stream:   Initializer process output.
34709 
34710      Time:     In response to an operator command.
34711 
34712      Meaning:  Incorrect arguments were specified.
34713 
34714      Action:   Enter a corrected command line.
34715 
34716 
34717                [salv_caller.pl1]
34718                salvage_dirs:   Specified control argument  is not
34719                implemented by this command.  BLAH
34720 
34721 
34722      Stream:   Initializer process output.
34723 
34724      Time:     In response to an operator command.
34725 
34726      Meaning:  Incorrect arguments were specified.
34727 
34728      Action:   Enter a corrected command line.
34729 
34730 
34731                [salv_caller.pl1]
34732                salvage_dirs:   VTOC  checking   is  required  for
34733                connection failure deletion.
34734 
34735 
34736      Stream:   Initializer process output.
34737 
34738      Time:     In response to an operator command.
34739 
34740      Meaning:  An attempt  was made to specify  directory salvage
34741                with  connection  failure  deletion,  but  no VTOC
34742                checking.
34743 
34744      Action:   Enter a corrected command line.
34745 
34746 
34747                [salv_caller.pl1]
34748                salvage_dirs:  Will not salvage
34749 
34750 
34751      Stream:   Initializer process output.
34752 
34753      Time:     In response to an operator command.
34754 
34755 
34756 salvage_dirs                   600            08/03/23     MR12.7^L
34757 
34758 
34759      Meaning:  Incorrect arguments were specified.
34760 
34761      Action:   Enter a corrected command line.
34762 
34763 
34764                [salv_caller.pl1]
34765                salvage_dirs:    will  not   salvage  until   root
34766                complete
34767 
34768 
34769      Stream:   Initializer process output.
34770 
34771      Time:     In response to an operator command.
34772 
34773      Meaning:  Incorrect arguments were specified.
34774 
34775      Action:   Enter a corrected command line.
34776 
34777 
34778                [salvage_pv.pl1]
34779                salvage_pv:  Bit map size is DD.  (WWo) words, s/b
34780                EE.  (FFo), changing to latter.
34781 
34782 
34783      Stream:   $salvout
34784 
34785      Time:     $salvt
34786 
34787      Meaning:  The bit map size in the volume label was incorrect
34788                and has been corrected.
34789 
34790      Action:   No operator action is required.
34791 
34792 
34793                [salvage_pv.pl1]
34794                salvage_pv:   damaged  switch  found  on  for UUUU
34795                vtocx XXXo:  NAME
34796 
34797 
34798      Stream:   $salvout
34799 
34800      Time:     $salvt
34801 
34802      Meaning:  The segment  originally named NAME with  unique ID
34803                UUUU  at vtoc  index XXXo  was found  to have  its
34804                damaged switch on.  The  damaged switch can be set
34805                during the  running of the system  if page control
34806                encounters an I/O  error.  Damaged segments cannot
34807                be used until the damaged switch is reset.
34808 
34809      Action:   No operator action is required.
34810 
34811 
34812 
34813 
34814 salvage_pv                     601            08/03/23     MR12.7^L
34815 
34816 
34817                [salvage_pv.pl1]
34818                salvage_pv:  DDD damaged segments on volume PVNAME
34819                (NNN damaged in this salvage).
34820 
34821 
34822      Stream:   BOS Typewriter.
34823 
34824      Time:     $salvt
34825 
34826      Meaning:  DDD  damaged  segments  were  found  on the volume
34827                PVNAME, which has  just been volume-salvaged.  The
34828                damaged switch  was set for NNN  of these segments
34829                during  this volume  salvage.  The  damaged switch
34830                for the  other segments had been set  prior to the
34831                salvage.
34832 
34833      Action:   Inspect  the syserr  and Answering  Service log to
34834                identify  damaged  segments.   Prepare  to recover
34835                them if necessary.
34836 
34837 
34838 
34839                [salvage_pv.pl1]
34840                salvage_pv:   dirsw  turned  off  for  vtocx XXXo:
34841                NAME
34842 
34843 
34844      Stream:   $salvout
34845 
34846      Time:     $salvt
34847 
34848      Meaning:  The  segment originally  named NAME  at vtoc index
34849                XXXo has had its directory switch turned off.
34850 
34851      Action:   No operator action is required.
34852 
34853 
34854                [salvage_pv.pl1]
34855                salvage_pv:   freeing UUUU  deciduous vtocx  XXXo:
34856                NAME
34857 
34858 
34859      Stream:   $salvout
34860 
34861      Time:     $salvt
34862 
34863      Meaning:  The segment  originally named NAME with  unique ID
34864                UUUU  at vtoc  index XXXo  was deciduous,  and has
34865                been  deleted  from  the  RPV.   This is debugging
34866                output  printed for  system programmers  if a SALV
34867                DEBG card is supplied.
34868 
34869      Action:   No operator action is required.
34870 
34871 
34872 salvage_pv                     602            08/03/23     MR12.7^L
34873 
34874 
34875 
34876 
34877                [salvage_pv.pl1]
34878                salvage_pv:  freeing UUUU  per process vtocx XXXo:
34879                NAME
34880 
34881 
34882      Stream:   $salvout
34883 
34884      Time:     $salvt
34885 
34886      Meaning:  The segment  originally named NAME with  unique ID
34887                UUUU  at vtoc index  XXXo was per-process  and has
34888                been  deleted.  This  is debugging  output printed
34889                for  system programmers  if  a  SALV DEBG  card is
34890                used.
34891 
34892      Action:   No operator action is required.
34893 
34894 
34895                [salvage_pv.pl1]
34896                salvage_pv:  freeing UUUU per-bootload vtocx XXXo:
34897                NAME
34898 
34899 
34900      Stream:   $salvout
34901 
34902      Time:     $salvt
34903 
34904      Meaning:  The segment  originally named NAME with  unique ID
34905                UUU at vtoc index  XXXo was per-bootload (inferior
34906                to a  prior >sl1), and has been  deleted.  This is
34907                debugging output printed for system programmers if
34908                a SALV DEBG card is supplied.
34909 
34910      Action:   No operator action is required.
34911 
34912 
34913                [salvage_pv.pl1]
34914                salvage_pv:   INIT_TABLES:   aste  pool  WWWo  too
34915                small.
34916 
34917 
34918      Stream:   BOS Typewriter.
34919 
34920      Time:     While system is running.
34921 
34922      Meaning:  The physical volume salvager  was unable to obtain
34923                a temporary  AST entry for segment  requiring WWWo
34924                ptws.  No salvaging was done.
34925 
34926      Action:   Shut  down,  manually  correct  the  SST card, and
34927                reboot.   Then  salvage  all  volumes,  since  the
34928 
34929 
34930 salvage_pv                     603            08/03/23     MR12.7^L
34931 
34932 
34933                indicator  that volumes   need salvaging  may have
34934                been lost.
34935 
34936 
34937 
34938                [salvage_pv.pl1]
34939                salvage_pv:  Label times in advance of clock.  The
34940                clock may be wrong.
34941 
34942 
34943      Stream:   $salvout
34944 
34945      Time:     $salvt
34946 
34947      Meaning:  The  label of  the volume  being salvaged contains
34948                one  or  more  clock  readings  in  advance of the
34949                current clock.  Salvaging will proceed.  The times
34950                are not corrected.  If  there is reason to believe
34951                that  the  system  clock  is  incorrect,  shut the
34952                system down as soon as  possible and take steps to
34953                recover that part of  the hierarchy which may have
34954                been contaminated with bad clock values.
34955 
34956      Action:   No operator action is required.
34957 
34958 
34959                [salvage_pv.pl1]
34960                salvage_pv:  map of assigned addresses changed.
34961 
34962 
34963      Stream:   $salvout
34964 
34965      Time:     $salvt
34966 
34967      Meaning:  If  any corrections  were made  to the  map on the
34968                volume  which shows  which addresses  are free and
34969                which are in use, this message is printed.  If the
34970                volume was not properly shut down, this message is
34971                to be expected.
34972 
34973      Action:   No operator action is required.
34974 
34975 
34976                [salvage_pv.pl1]
34977                salvage_pv:  NN free vtoces added to free list.
34978 
34979 
34980      Stream:   $salvout
34981 
34982      Time:     $salvt
34983 
34984 
34985 
34986 
34987 
34988 salvage_pv                     604            08/03/23     MR12.7^L
34989 
34990 
34991      Meaning:  NN  free VTOC  entries were  found while salvaging
34992                and added to the list  of free VTOC entries.  This
34993                is a normal message.
34994 
34995      Action:   No operator action is required.
34996 
34997 
34998                [salvage_pv.pl1]
34999                salvage_pv:  no.  of free recs changed from OLD to
35000                NEW (dec).
35001 
35002 
35003      Stream:   $salvout
35004 
35005      Time:     $salvt
35006 
35007      Meaning:  If the number of free  records in the volume label
35008                is  changed by a  volume salvage, this  message is
35009                printed.   If  the  volume  was  not properly shut
35010                down, this message is to be expected.
35011 
35012      Action:   No operator action is required.
35013 
35014 
35015                [salvage_pv.pl1]
35016                salvage_pv:  no.  of free  vtoces changed from OLD
35017                to NEW (dec).
35018 
35019 
35020      Stream:   $salvout
35021 
35022      Time:     $salvt
35023 
35024      Meaning:  If the  number of free VTOC entries  in the volume
35025                label is changed by a volume salvage, this message
35026                is printed.
35027 
35028      Action:   No operator action is required.
35029 
35030 
35031                [salvage_pv.pl1]
35032                salvage_pv:  setting damaged switch on PRIMARYNAME
35033                (VTOCXo) on pv PVNAME.
35034 
35035 
35036      Stream:   Logged in SYSERR log.
35037 
35038      Time:     $salvt
35039 
35040      Meaning:  The volume salvager has discovered possible damage
35041                to a segment and has turned on the damaged switch.
35042 
35043 
35044 
35045 
35046 salvage_pv                     605            08/03/23     MR12.7^L
35047 
35048 
35049      Action:   No operator  action is required.  This  message is
35050                logged in order to trigger automatic processing of
35051                damaged segments.
35052 
35053 
35054 
35055                [salvage_pv.pl1]
35056                salvage_pv:  Volume salvage finished with errors.
35057 
35058 
35059      Stream:   $salvout
35060 
35061      Time:     $salvt
35062 
35063      Meaning:  Volume salvage finished with errors.
35064 
35065      Action:   Contact the system programming staff.
35066 
35067 
35068                [salvage_pv.pl1]
35069                salvage_pv:  Volume salvage finished.
35070 
35071 
35072      Stream:   $salvout
35073 
35074      Time:     $salvt
35075 
35076      Meaning:  Volume salvage finished.
35077 
35078      Action:   No operator action is required.
35079 
35080 
35081                [salvage_pv.pl1]
35082                salvage_pv:  Volume salvage  of dskX_NN{s}, volume
35083                PVNAME of logical vol LVNAME.
35084 
35085 
35086      Stream:   $salvout
35087 
35088      Time:     $salvt
35089 
35090      Meaning:  This  message  is  printed  when  volume salvaging
35091                begins.
35092 
35093      Action:   No operator action is required.
35094 
35095 
35096                [salvage_pv.pl1]
35097                salvage_pv:  VTOC conversion finished with errors.
35098 
35099 
35100      Stream:   $salvout
35101 
35102 
35103 
35104 salvage_pv                     606            08/03/23     MR12.7^L
35105 
35106 
35107      Time:     $salvt
35108 
35109      Meaning:  VTOC conversion finished with errors.
35110 
35111      Action:   Contact the system programming staff.
35112 
35113 
35114                [salvage_pv.pl1]
35115                salvage_pv:  VTOC conversion finished.
35116 
35117 
35118      Stream:   $salvout
35119 
35120      Time:     $salvt
35121 
35122      Meaning:  VTOC conversion finished.
35123 
35124      Action:   No operator action is required.
35125 
35126 
35127                [salvage_pv.pl1]
35128                salvage_pv:  VTOC Conversion of dskX_NN{s}, volume
35129                PVNAME of logical vol LVNAME.
35130 
35131 
35132      Stream:   $salvout
35133 
35134      Time:     $salvt
35135 
35136      Meaning:  This message is printed  when a pre-MR10 disk pack
35137                is first mounted on an  MR10 or later system.  The
35138                equivalent  of a salvage  is being done  to create
35139                the VTOC Map, which did not exist prior to MR10.
35140 
35141      Action:   No operator action is required.
35142 
35143 
35144                [salvage_pv.pl1]
35145                salvage_pv:  vtoce NAME at  XXXo:  cur len changed
35146                from OLD to NEW (octal)
35147 
35148 
35149      Stream:   $salvout
35150 
35151      Time:     $salvt
35152 
35153      Meaning:  The  segment originally  named NAME  at vtoc index
35154                XXXo had a current length which did not agree with
35155                the  file map.   The current  length was corrected
35156                and the  damaged switch set on  the segment.  This
35157                message  usually  indicates  that  a  segment  was
35158                damaged before a crash by failure to write out its
35159 
35160 
35161 
35162 salvage_pv                     607            08/03/23     MR12.7^L
35163 
35164 
35165                pages to  disk before the crash.   The segment may
35166                have to be recovered.
35167 
35168      Action:   No operator action is required.
35169 
35170 
35171                [salvage_pv.pl1]
35172                salvage_pv:  vtoce NAME at  XXXo:  max len changed
35173                from OLD to NEW (octal).
35174 
35175 
35176      Stream:   $salvout
35177 
35178      Time:     $salvt
35179 
35180      Meaning:  The  segment originally  named NAME  at vtoc index
35181                XXXo  had a maximum  segment length which  did not
35182                agree  with the  file map   or was  less than  the
35183                current length.  The  maximum length was corrected
35184                and the damaged switch set.
35185 
35186      Action:   No operator action is required.
35187 
35188 
35189                [salvage_pv.pl1]
35190                salvage_pv:   vtoce  NAME   at  XXXo:   page  PPPo
35191                disk_addr DDDDo bad.
35192 
35193 
35194      Stream:   $salvout
35195 
35196      Time:     $salvt
35197 
35198      Meaning:  The  segment originally  named NAME  at vtoc index
35199                XXXo  had an invalid  disk address DDDDo  for page
35200                PPPo.   The address is  nulled, causing a  page of
35201                zeroes, and the damaged switch set.
35202 
35203      Action:   No operator action is required.
35204 
35205 
35206                [salvage_pv.pl1]
35207                salvage_pv:  vtoce NAME at XXXo:  rec used changed
35208                from OLD to NEW (octal).
35209 
35210 
35211      Stream:   $salvout
35212 
35213      Time:     $salvt
35214 
35215      Meaning:  The  segment originally  named NAME  at vtoc index
35216                XXXo had  a records used which did  not agree with
35217                the  file   map.   The  records  used   field  was
35218 
35219 
35220 salvage_pv                     608            08/03/23     MR12.7^L
35221 
35222 
35223                corrected  and  the   damaged  switch  set.   This
35224                message  usually  indicates  that  a  segment  was
35225                damaged before a crash by failure to write out its
35226                pages to  disk before the crash.   The segment may
35227                have to be recovered.
35228 
35229      Action:   No operator action is required.
35230 
35231 
35232                [salvage_pv.pl1]
35233                salvage_pv:   vtoce NAME  at XXXo:   ref to pageno
35234                PPo at addr DDDDo deleted, dirsw is X.
35235 
35236 
35237      Stream:   $salvout
35238 
35239      Time:     $salvt
35240 
35241      Meaning:  The  segment originally  named NAME  at vtoc index
35242                XXXo  had a  reused address  conflict with another
35243                segment.  The page reference  was determined to be
35244                incorrect,  and  a  null  address  placed  in  the
35245                segment's file map, causing  a page of zeroes, and
35246                the  damaged  switch  set.   This  message  may be
35247                symptomatic of disk or other hardware problems.
35248 
35249      Action:   No operator action is required.
35250 
35251 
35252                [salvage_pv.pl1]
35253                salvage_pv:       vtoce     NAME      at     XXXo:
35254                time-record-product reset to zero.
35255 
35256 
35257      Stream:   $salvout
35258 
35259      Time:     $salvt
35260 
35261      Meaning:  The  segment originally  named NAME  at vtoc index
35262                XXXo  had   an  invalid  value  for   one  of  the
35263                time-record-product          fields.           All
35264                time-record-product  fields  have  been  reset  to
35265                zero.
35266 
35267      Action:   No operator action is required.
35268 
35269 
35270                [salvage_pv.pl1]
35271                salvage_pv:  vtoce XXXo free but not zero.
35272 
35273 
35274      Stream:   $salvout
35275 
35276 
35277 
35278 salvage_pv                     609            08/03/23     MR12.7^L
35279 
35280 
35281      Time:     $salvt
35282 
35283      Meaning:  The VTOC entry with index XXXo was marked free but
35284                was not all zero.  It was zeroed and made free.
35285 
35286      Action:   No operator action is required.
35287 
35288 
35289                [salv_caller.pl1]
35290                salvage_vol:  -all  and -copy arguments  cannot be
35291                used together
35292 
35293 
35294      Stream:   Initializer process output.
35295 
35296      Time:     In response to an operator command.
35297 
35298      Meaning:  Incorrect arguments were specified.
35299 
35300      Action:   Enter a corrected command line.
35301 
35302 
35303                [salv_caller.pl1]
35304                salvage_vol:  ERROR_MESSAGE
35305 
35306 
35307      Stream:   Initializer process output.
35308 
35309      Time:     In response to an operator command.
35310 
35311      Meaning:  Incorrect arguments were specified.
35312 
35313      Action:   Enter a corrected command line.
35314 
35315 
35316                [salv_caller.pl1]
35317                salvage_vol:  ERROR_MESSAGE.  need copy drive name
35318 
35319 
35320      Stream:   Initializer process output.
35321 
35322      Time:     In response to an operator command.
35323 
35324      Meaning:  Incorrect arguments were specified.
35325 
35326      Action:   Enter a corrected command line.
35327 
35328 
35329                [salv_caller.pl1]
35330                salvage_vol:   Expected  argument  missing.  first
35331                two args must be phys vol name and drive name
35332 
35333 
35334 
35335 
35336 salvage_vol                    610            08/03/23     MR12.7^L
35337 
35338 
35339      Stream:   Initializer process output.
35340 
35341      Time:     In response to an operator command.
35342 
35343      Meaning:  Incorrect arguments were specified.
35344 
35345      Action:   Enter a corrected command line.
35346 
35347 
35348                [salv_caller.pl1]
35349                salvage_vol:   Inconsistent  arguments  have  been
35350                specified
35351 
35352 
35353      Stream:   Initializer process output.
35354 
35355      Time:     In response to an operator command.
35356 
35357      Meaning:  Incorrect arguments were specified.
35358 
35359      Action:   Enter a corrected command line.
35360 
35361 
35362                [salv_caller.pl1]
35363                salvage_vol:  no drive may be specified for -all
35364 
35365 
35366      Stream:   Initializer process output.
35367 
35368      Time:     In response to an operator command.
35369 
35370      Meaning:  Incorrect arguments were specified.
35371 
35372      Action:   Enter a corrected command line.
35373 
35374 
35375                [salv_caller.pl1]
35376                salvage_vol:   Specified control  argument is  not
35377                implemented by this command.  BLAH
35378 
35379 
35380      Stream:   Initializer process output.
35381 
35382      Time:     In response to an operator command.
35383 
35384      Meaning:  Incorrect arguments were specified.
35385 
35386      Action:   Enter a corrected command line.
35387 
35388 
35389                [bce_save.pl1]
35390                save(check_status):        Special      Interrupt:
35391                STATUS_WORD
35392 
35393 
35394 save(check_status)             611            08/03/23     MR12.7^L
35395 
35396 
35397      Stream:   BOS Typewriter.
35398 
35399      Time:     System Intialization.
35400 
35401      Meaning:  An unexpected special interrupt has been detected.
35402 
35403      Action:   No operator action is required.
35404 
35405 
35406                [bce_save.pl1]
35407                save(check_status):  Time-Out on TAPE_DEV
35408 
35409 
35410      Stream:   BOS Typewriter.
35411 
35412      Time:     System Intialization.
35413 
35414      Meaning:  An  I/O that  was issued  to the  tape device  has
35415                timed-out.
35416 
35417      Action:   Follow normal recovery procedures.
35418 
35419 
35420                [bce_save.pl1]
35421                save(TAPE_SET):    (Unrecoverable)   MAJOR_STATUS,
35422                SUB_STATUS on TAPE_DEV.
35423 
35424 
35425      Stream:   BOS Typewriter.
35426 
35427      Time:     System Intialization.
35428 
35429      Meaning:  An   unrecoverable   error   has   occured   while
35430                attempting to do I/O to the tape device.
35431 
35432      Action:   Follow normal recovery procedures.
35433 
35434 
35435                [bce_save.pl1]
35436                save(TAPE_SET):  Device TAPE_DEV  is being removed
35437                from the tape device list.
35438 
35439 
35440      Stream:   BOS Typewriter.
35441 
35442      Time:     System Intialization.
35443 
35444      Meaning:  The TAPE_DEV has returned a status indicating that
35445                it is unable to be used.
35446 
35447      Action:   No operator action is required.
35448 
35449 
35450 
35451 
35452 save(TAPE_SET)                 612            08/03/23     MR12.7^L
35453 
35454 
35455                [bce_save.pl1]
35456                save(TAPE_SET):  Error,  tape on TAPE_DEV  is part
35457                of the "OTHER_TAPE_SET" set.
35458 
35459 
35460      Stream:   BOS Typewriter.
35461 
35462      Time:     System Intialization.
35463 
35464      Meaning:  The tape just read is not part of this tape set.
35465 
35466      Action:   Mount a  tape on the  device that is  part of this
35467                tape set.
35468 
35469 
35470                [bce_save.pl1]
35471                save(TAPE_SET):   Incorrect  tape  sequence number
35472                detected.
35473                was REC_NUM, s/b REC_NUM.  Forcing restart of this
35474                tape set.
35475 
35476 
35477 
35478      Stream:   BOS Typewriter (sounds beeper)
35479 
35480      Time:     System Intialization.
35481 
35482      Meaning:  A sequence  error was detected in  the tape record
35483                number.   This  indicates  a  logic  error  in the
35484                supervisor, or CPU or memory hardware problems.
35485 
35486      Action:   Follow  normal save  restart procedures.   Contact
35487                the system programming staff.
35488 
35489 
35490 
35491                [bce_save.pl1]
35492                save(TAPE_SET):    MAJOR_STATUS,   SUB_STATUS   on
35493                TAPE_DEV.
35494 
35495 
35496      Stream:   BOS Typewriter.
35497 
35498      Time:     System Intialization.
35499 
35500      Meaning:  An error has occured while attempting to do I/O to
35501                the tape device.
35502 
35503      Action:   Follow normal recovery procedures.
35504 
35505 
35506                [bce_save_util_.pl1]
35507 
35508 
35509 
35510 save(TAPE_SET)                 613            08/03/23     MR12.7^L
35511 
35512 
35513                save(TAPE_SET):     MULTICS_VOL_ID   PV_NAME    on
35514                DISK_DEV Last updated:  DATE_TIME
35515 
35516 
35517 
35518      Stream:   BOS Typewriter.
35519 
35520      Time:     System Intialization.
35521 
35522      Meaning:  Just an informative message.
35523 
35524      Action:   No operator action is required.
35525 
35526 
35527                [bce_save.pl1]
35528                save(TAPE_SET):  No Physical Volumes left to save.
35529 
35530 
35531      Stream:   BOS Typewriter.
35532 
35533      Time:     System Intialization.
35534 
35535      Meaning:  For  various reasons  all of  the physical volumes
35536                have been removed from the list of volumes.
35537 
35538      Action:   No operator action is required.
35539 
35540 
35541                [bce_save.pl1]
35542                save(TAPE_SET):   No room  to describe  PV PV_NAME
35543                for part PARTITION_NAME.
35544 
35545 
35546      Stream:   BOS Typewriter.
35547 
35548      Time:     System Intialization.
35549 
35550      Meaning:  The maximum number of physical volumes that can be
35551                handled by the program has been exceeded.
35552 
35553      Action:   The  number  of  physical  volumes  defined in the
35554                control file(s) must be reduced.
35555 
35556 
35557 
35558                [bce_save.pl1]
35559                save(TAPE_SET):   No usable  tape devices  left in
35560                list.
35561 
35562 
35563      Stream:   BOS Typewriter.
35564 
35565      Time:     System Intialization.
35566 
35567 
35568 save(TAPE_SET)                 614            08/03/23     MR12.7^L
35569 
35570 
35571      Meaning:  For various  reasons all of the  tape devices have
35572                been  removed from  the list  of available devices
35573                for this tape set.
35574 
35575      Action:   Follow normal recovery procedures.
35576 
35577 
35578                [bce_save.pl1]
35579                save(TAPE_SET):  No usable tape drives left.
35580 
35581 
35582      Stream:   BOS Typewriter.
35583 
35584      Time:     System Intialization.
35585 
35586      Meaning:  For various  reasons all of the  tape devices have
35587                been  removed from  the list  of available devices
35588                for this tape set.
35589 
35590      Action:   Follow normal recovery procedures.
35591 
35592 
35593                [bce_save_util_.pl1]
35594                save(TAPE_SET):   Partition PARTITION_NAME  is not
35595                defined on PV_NAME.
35596 
35597 
35598      Stream:   BOS Typewriter.
35599 
35600      Time:     System Intialization.
35601 
35602      Meaning:  A  request  to  save  specific  partition has been
35603                made, but the partition does not exist of the PV.
35604 
35605      Action:   Correct the control file(s) accordingly.
35606 
35607 
35608                [bce_save_util_.pl1]
35609                save(TAPE_SET):    Partition   PARTITION_NAME   of
35610                volume PV_NAME is not  defined in the restart tape
35611                label.
35612 
35613 
35614 
35615      Stream:   BOS Typewriter.
35616 
35617      Time:     System Intialization.
35618 
35619      Meaning:  There is an inconsistency between the restart tape
35620                and the save control file(s).
35621 
35622      Action:   Either  correct the  control file(s)  or start the
35623                save over from the beginning.
35624 
35625 
35626 save(TAPE_SET)                 615            08/03/23     MR12.7^L
35627 
35628 
35629 
35630 
35631                [bce_save.pl1]
35632                save(TAPE_SET):    Partition   PARTITION_NAME   on
35633                PV_NAME,  record  REC_NUM,  on  tape#  TAPE_NUMBER
35634                (TAPE_DEV)
35635 
35636 
35637      Stream:   BOS Typewriter.
35638 
35639      Time:     System Intialization.
35640 
35641      Meaning:  Just an informative message.
35642 
35643      Action:   No operator action is required.
35644 
35645 
35646                [bce_save.pl1]
35647                save(TAPE_SET):  Partition  PARTITION_NAME, record
35648                REC_NUM, on tape# TAPE_NUMBER (TAPE_DEV)
35649 
35650 
35651      Stream:   BOS Typewriter.
35652 
35653      Time:     System Intialization.
35654 
35655      Meaning:  Just an informative message.
35656 
35657      Action:   No operator action is required.
35658 
35659 
35660                [bce_save.pl1]
35661                save(TAPE_SET):  Please mount tape# TAPE_NUMBER on
35662                TAPE_DEV.
35663 
35664 
35665      Stream:   BOS Typewriter (sounds beeper)
35666 
35667      Time:     System Intialization.
35668 
35669      Meaning:  Just an informative message.
35670 
35671      Action:   Mount tape on the device.
35672 
35673 
35674                [bce_save.pl1]
35675                save(TAPE_SET):  Please  mount the "Info"  tape on
35676                TAPE_DEV.
35677 
35678 
35679      Stream:   BOS Typewriter (sounds beeper)
35680 
35681      Time:     System Intialization.
35682 
35683 
35684 save(TAPE_SET)                 616            08/03/23     MR12.7^L
35685 
35686 
35687      Meaning:  Just an informative message.
35688 
35689      Action:   Mount the tape on the device.
35690 
35691 
35692                [bce_save.pl1]
35693                save(TAPE_SET):   Please mount the  "restart" tape
35694                on TAPE_DEV.
35695 
35696 
35697      Stream:   BOS Typewriter (sounds beeper)
35698 
35699      Time:     System Intialization.
35700 
35701      Meaning:  Just an informative message.
35702 
35703      Action:   Mount the tape on the device.
35704 
35705 
35706                [bce_save.pl1]
35707                save(TAPE_SET):   Remount  tape#  TAPE_NUMBER WITH
35708                write ring on TAPE_DEV.
35709 
35710 
35711      Stream:   BOS Typewriter (sounds beeper)
35712 
35713      Time:     System Intialization.
35714 
35715      Meaning:  The tape is currently mounted without a write ring
35716                present.
35717 
35718      Action:   Remount tape with write permit ring in place.
35719 
35720 
35721                [bce_save_util_.pl1]
35722                save(TAPE_SET):   Removing volume PV_NAME  from PV
35723                list, because all partitions were removed.
35724 
35725 
35726 
35727      Stream:   BOS Typewriter.
35728 
35729      Time:     System Intialization.
35730 
35731      Meaning:  It is  nolonger necessary for the  program to keep
35732                track  of  the  PV,  since  all  of  the partition
35733                requests have been removed.
35734 
35735      Action:   Correct the control files accordingly.
35736 
35737 
35738                [bce_save_util_.pl1]
35739 
35740 
35741 
35742 save(TAPE_SET)                 617            08/03/23     MR12.7^L
35743 
35744 
35745                save(TAPE_SET):   Removing volume PV_NAME  from PV
35746                list, because there are no partitions to save.
35747 
35748 
35749 
35750      Stream:   BOS Typewriter.
35751 
35752      Time:     System Intialization.
35753 
35754      Meaning:  Only partition requests were  made for this volume
35755                and now for various reasons there are none left to
35756                save.
35757 
35758      Action:   Follow normal recovery procedures.
35759 
35760 
35761                [bce_save_util_.pl1]
35762                save(TAPE_SET):    Reverting    "-all"   partition
35763                request for  volume PV_NAME, because there  are no
35764                partitions to save.
35765 
35766 
35767 
35768      Stream:   BOS Typewriter.
35769 
35770      Time:     System Intialization.
35771 
35772      Meaning:  This PV_NAME has no partitions defined.
35773 
35774      Action:   No operator action is required.
35775 
35776 
35777                [bce_save.pl1]
35778                save(TAPE_SET):  save complete...
35779 
35780 
35781      Stream:   BOS Typewriter.
35782 
35783      Time:     System Intialization.
35784 
35785      Meaning:  Just an informative message.
35786 
35787      Action:   No operator action is required.
35788 
35789 
35790                [bce_save.pl1]
35791                save(TAPE_SET):    Skipping   volume   PV_NAME  on
35792                DISK_DEV, save complete.
35793 
35794 
35795      Stream:   BOS Typewriter.
35796 
35797      Time:     System Intialization.
35798 
35799 
35800 save(TAPE_SET)                 618            08/03/23     MR12.7^L
35801 
35802 
35803      Meaning:  Just an informative message.
35804 
35805      Action:   No operator action is required.
35806 
35807 
35808                [bce_save.pl1]
35809                save(TAPE_SET):   Starting from volume  PV_NAME on
35810                DISK_DEV.
35811 
35812 
35813      Stream:   BOS Typewriter.
35814 
35815      Time:     System Intialization.
35816 
35817      Meaning:  Just an informative message.
35818 
35819      Action:   No operator action is required.
35820 
35821 
35822                [bce_save.pl1]
35823                save(TAPE_SET):  Tape on TAPE_DEV does not contain
35824                a supported tape label version.
35825 
35826 
35827      Stream:   BOS Typewriter.
35828 
35829      Time:     System Intialization.
35830 
35831      Meaning:  The tape  contains a tape version  identifier that
35832                is nolonger supported.
35833 
35834      Action:   Use   the  "restore   -display_info_tape  tapX_NN"
35835                option to display the tape.
35836 
35837 
35838 
35839                [bce_save.pl1]
35840                save(TAPE_SET):  Tape on TAPE_DEV does not contain
35841                a valid label.
35842 
35843 
35844      Stream:   BOS Typewriter.
35845 
35846      Time:     System Intialization.
35847 
35848      Meaning:  The  tape just  read is  not a  valid save/restore
35849                tape.
35850 
35851      Action:   Follow normal recovery procedures.
35852 
35853 
35854                [bce_save.pl1]
35855 
35856 
35857 
35858 save(TAPE_SET)                 619            08/03/23     MR12.7^L
35859 
35860 
35861                save(TAPE_SET):  Tape  on TAPE_DEV is not  part of
35862                this set.
35863 
35864 
35865      Stream:   BOS Typewriter.
35866 
35867      Time:     System Intialization.
35868 
35869      Meaning:  The tape  just read contains a  different tape set
35870                name than what is currently being handled, via the
35871                control file.
35872 
35873      Action:   Follow normal recovery procedures.
35874 
35875 
35876                [bce_save_util_.pl1]
35877                save(TAPE_SET):   Tape subsystem "SUB_SYS"  is not
35878                defined in the config.
35879 
35880 
35881      Stream:   BOS Typewriter.
35882 
35883      Time:     System Intialization.
35884 
35885      Meaning:  No  "prph"  entry  could  be  found  for  the tape
35886                subsystem.
35887 
35888      Action:   Correct   config_deck   or   save/restore  control
35889                file(s) to indicate proper tape subsystem.
35890 
35891 
35892 
35893                [bce_save.pl1]
35894                save(TAPE_SET):   Tape#  TAPE_NUMBER  on TAPE_DEV,
35895                created DATE_TIME
35896 
35897 
35898      Stream:   BOS Typewriter.
35899 
35900      Time:     System Intialization.
35901 
35902      Meaning:  Just an informative message.
35903 
35904      Action:   No operator action is required.
35905 
35906 
35907                [bce_save_util_.pl1]
35908                save(TAPE_SET):   The "conf"  partition of  rpv is
35909                not being saved.
35910 
35911 
35912      Stream:   BOS Typewriter.
35913 
35914 
35915 
35916 save(TAPE_SET)                 620            08/03/23     MR12.7^L
35917 
35918 
35919      Time:     System Intialization.
35920 
35921      Meaning:  Just an informative message.
35922 
35923      Action:   Add  the  request  to  the  save  control  file if
35924                desired.
35925 
35926 
35927                [bce_save_util_.pl1]
35928                save(TAPE_SET):   The "file"  partition of  rpv is
35929                not being saved.
35930 
35931 
35932      Stream:   BOS Typewriter.
35933 
35934      Time:     System Intialization.
35935 
35936      Meaning:  Just an informative message.
35937 
35938      Action:   Add  the  request  to  the  save  control  file if
35939                desired.
35940 
35941 
35942                [bce_save_util_.pl1]
35943                save(TAPE_SET):  The "log" partition of rpv is not
35944                being saved.
35945 
35946 
35947      Stream:   BOS Typewriter.
35948 
35949      Time:     System Intialization.
35950 
35951      Meaning:  Just an informative message.
35952 
35953      Action:   Add  the  request  to  the  save  control  file if
35954                desired.
35955 
35956 
35957                [bce_save.pl1]
35958                save(TAPE_SET):  The following tape device(s) will
35959                be used:
35960 
35961 
35962      Stream:   BOS Typewriter.
35963 
35964      Time:     System Intialization.
35965 
35966      Meaning:  Just an informative message.
35967 
35968      Action:   No operator action is required.
35969 
35970 
35971                [bce_save.pl1]
35972 
35973 
35974 save(TAPE_SET)                 621            08/03/23     MR12.7^L
35975 
35976 
35977                save(TAPE_SET):  This tape is older than one week.
35978                Tape rejected.
35979 
35980 
35981      Stream:   BOS Typewriter.
35982 
35983      Time:     System Intialization.
35984 
35985      Meaning:  A restart  of a save  is being attempted,  but the
35986                tape used  as the restart  tape is older  than one
35987                week.
35988 
35989      Action:   Restart with  a later tape or start  the save from
35990                the beginning.
35991 
35992 
35993                [bce_save.pl1]
35994                save(TAPE_SET):   This  tape  starts  with  volume
35995                PV_NAME, which was not defined.  Tape rejected.
35996 
35997 
35998 
35999      Stream:   BOS Typewriter.
36000 
36001      Time:     System Intialization.
36002 
36003      Meaning:  A save restart is being attempted with a tape that
36004                begins with a PV that  has not been defined in the
36005                save control file(s).
36006 
36007      Action:   Follow normal recovery procedures.
36008 
36009 
36010                [bce_save.pl1]
36011                save(TAPE_SET):   Time-out   waiting  for  special
36012                interrupt.
36013 
36014 
36015      Stream:   BOS Typewriter.
36016 
36017      Time:     System Intialization.
36018 
36019      Meaning:  The program was waiting for a special to come from
36020                the device,  but none was recieved  in the alloted
36021                time.
36022 
36023      Action:   Follow normal recovery procedures.
36024 
36025 
36026                [bce_save_util_.pl1]
36027                save(TAPE_SET):   Type  of  data  being  saved for
36028                volume  PV_NAME does  not  match  the type  in the
36029                restart tape label.
36030 
36031 
36032 save(TAPE_SET)                 622            08/03/23     MR12.7^L
36033 
36034 
36035      Stream:   BOS Typewriter.
36036 
36037      Time:     System Intialization.
36038 
36039      Meaning:  There is an inconsistency between the restart tape
36040                and the save control file(s).
36041 
36042      Action:   Either  correct the  control file(s)  or start the
36043                save over from the beginning.
36044 
36045 
36046 
36047                [bce_save_util_.pl1]
36048                save(TAPE_SET):   Unable to  save "PARTITION_NAME"
36049                partition.  Internal partition list full.
36050 
36051 
36052 
36053      Stream:   BOS Typewriter.
36054 
36055      Time:     System Intialization.
36056 
36057      Meaning:  More  partitions  have  been  requested  than  the
36058                program can handle.
36059 
36060      Action:   Change control files to reduce the number defined,
36061                possibly  by breaking  them up  into seperate tape
36062                sets.
36063 
36064 
36065 
36066                [bce_save_util_.pl1]
36067                save(TAPE_SET):   Unable to  save "PARTITION_NAME"
36068                partition.  N partitions already defined
36069 
36070 
36071 
36072      Stream:   BOS Typewriter.
36073 
36074      Time:     System Intialization.
36075 
36076      Meaning:  An attempt has  been made to save more  than the N
36077                maximum partitions allowed.
36078 
36079      Action:   Change  control  files(s)  to  reduce  the  number
36080                requested.
36081 
36082 
36083                [bce_save.pl1]
36084                save(TAPE_SET):    Unable   to   set   density  on
36085                TAPE_DEV.
36086 
36087 
36088 
36089 
36090 save(TAPE_SET)                 623            08/03/23     MR12.7^L
36091 
36092 
36093      Stream:   BOS Typewriter.
36094 
36095      Time:     System Intialization.
36096 
36097      Meaning:  The program was unable to set the required density
36098                of the tape device.
36099 
36100      Action:   Follow normal recovery procedures.
36101 
36102 
36103                [bce_save.pl1]
36104                save(TAPE_SET):    Unloading   "Info"   tape  from
36105                TAPE_DEV, REC_CNT records (ERR_CNT errors)
36106 
36107 
36108      Stream:   BOS Typewriter.
36109 
36110      Time:     System Intialization.
36111 
36112      Meaning:  Just an informative message.
36113 
36114      Action:   No operator action is required.
36115 
36116 
36117                [bce_save.pl1]
36118                save(TAPE_SET):  Unloading  tape# TAPE_NUMBER from
36119                TAPE_DEV, REC_CNT records (ERR_CNT errors)
36120 
36121 
36122      Stream:   BOS Typewriter.
36123 
36124      Time:     System Intialization.
36125 
36126      Meaning:  Just an informative message.
36127 
36128      Action:   No operator action is required.
36129 
36130 
36131                [bce_save.pl1]
36132                save(TAPE_SET):    Unloading   TAPE_DEV,   REC_CNT
36133                records (ERR_CNT errors)
36134 
36135 
36136      Stream:   BOS Typewriter.
36137 
36138      Time:     System Intialization.
36139 
36140      Meaning:  Just an informative message.
36141 
36142      Action:   No operator action is required.
36143 
36144 
36145                [bce_save_util_.pl1]
36146 
36147 
36148 save(TAPE_SET)                 624            08/03/23     MR12.7^L
36149 
36150 
36151                save(TAPE_SET):   Volume  on  DISK_DEV  is  not  a
36152                MULTICS_VOL_ID.
36153 
36154 
36155      Stream:   BOS Typewriter.
36156 
36157      Time:     System Intialization.
36158 
36159      Meaning:  The  volume to  be saved  is not  a valid  Multics
36160                volume and therefore cannot be saved.
36161 
36162      Action:   Follow normal recovery procedures.
36163 
36164 
36165                [bce_save_util_.pl1]
36166                save(TAPE_SET):   Volume  PV_NAME   not  found  in
36167                restart tape label.
36168 
36169 
36170      Stream:   BOS Typewriter.
36171 
36172      Time:     System Intialization.
36173 
36174      Meaning:  There is an inconsistency between the restart tape
36175                and the save control file(s).
36176 
36177      Action:   Either  correct the  control file(s)  or start the
36178                save over from the beginning.
36179 
36180 
36181 
36182                [bce_save_util_.pl1]
36183                save(TAPE_SET):     Volume     PV_NAME    requires
36184                salvaging.   Setting  -all   to  save  all  paging
36185                records on the volume.
36186 
36187 
36188 
36189      Stream:   BOS Typewriter.
36190 
36191      Time:     System Intialization.
36192 
36193      Meaning:  Just an informative message.
36194 
36195      Action:   No operator action is required.
36196 
36197 
36198                [bce_save_util_.pl1]
36199                save(TAPE_SET):   Volume PV_NAME's  PVID does  not
36200                match the one in the restart tape label.
36201 
36202 
36203 
36204 
36205 
36206 save(TAPE_SET)                 625            08/03/23     MR12.7^L
36207 
36208 
36209      Stream:   BOS Typewriter.
36210 
36211      Time:     System Intialization.
36212 
36213      Meaning:  There is  an inconsistency between what  is on the
36214                restart tape and what  is currently defined on the
36215                PV's disk label.
36216 
36217      Action:   Start the save over from the beginning.
36218 
36219 
36220                [bce_save.pl1]
36221                save(TAPE_SET):   Volume PV_NAME,  record REC_NUM,
36222                on tape# TAPE_NUMBER (TAPE_DEV)
36223 
36224 
36225      Stream:   BOS Typewriter.
36226 
36227      Time:     System Intialization.
36228 
36229      Meaning:  Just an informative message.
36230 
36231      Action:   No operator action is required.
36232 
36233 
36234                [bce_save_util_.pl1]
36235                save(TAPE_SET):    Volume  was   expected  to   be
36236                PV_NAME.
36237 
36238 
36239      Stream:   BOS Typewriter.
36240 
36241      Time:     System Intialization.
36242 
36243      Meaning:  The  PV name  read from  the disk  label does  not
36244                match  the PV  name that  was defined  in the save
36245                control file(s).
36246 
36247      Action:   Correct  the control  file to  show the  proper PV
36248                name mounted on the device.
36249 
36250 
36251 
36252                [bce_save.pl1]
36253                save(TAPE_SET):  Waiting for special on TAPE_DEV.
36254 
36255 
36256      Stream:   BOS Typewriter.
36257 
36258      Time:     System Intialization.
36259 
36260      Meaning:  Just an informative message.
36261 
36262 
36263 
36264 save(TAPE_SET)                 626            08/03/23     MR12.7^L
36265 
36266 
36267      Action:   No operator action is required.
36268 
36269 
36270                [bce_save_util_.pl1]
36271                save:  Attaching TAPE_DEV.  ERR_MESSAGE
36272 
36273 
36274      Stream:   BOS Typewriter (sounds beeper)
36275 
36276      Time:     System Intialization.
36277 
36278      Meaning:  IOI has returned a non-zero error code in response
36279                to a request to assign TAPE_DEV.
36280 
36281      Action:   Follow normal recovery procedures.
36282 
36283 
36284                [bce_save.pl1]
36285                save:  bce_ioi_post_seg.  ERR_MESSAGE
36286 
36287 
36288      Stream:   BOS Typewriter (sounds beeper)
36289 
36290      Time:     System Intialization.
36291 
36292      Meaning:  The  program was  unable to  get a  pointer to the
36293                above  segment.  This  indicates a  logic error in
36294                the   supervisor,  or   CPU  or   memory  hardware
36295                problems.
36296 
36297      Action:   Contact the system programming staff.
36298 
36299 
36300                [bce_save.pl1]
36301                save:  bootload_disk_post_seg.  ERR_MESSAGE
36302 
36303 
36304      Stream:   BOS Typewriter (sounds beeper)
36305 
36306      Time:     System Intialization.
36307 
36308      Meaning:  The  program was  unable to  get a  pointer to the
36309                above  segment.  This  indicates a  logic error in
36310                the   supervisor,  or   CPU  or   memory  hardware
36311                problems.
36312 
36313      Action:   Contact the system programming staff.
36314 
36315 
36316                [bce_save_util_.pl1]
36317                save:   Could   not  read  label  of   PV_NAME  on
36318                DISK_DEV.  ERR_MESSAGE
36319 
36320 
36321 
36322 save                           627            08/03/23     MR12.7^L
36323 
36324 
36325      Stream:   BOS Typewriter (sounds beeper)
36326 
36327      Time:     System Intialization.
36328 
36329      Meaning:  The volume label  of the PV could not  be read due
36330                to the error given in ERR_MESSAGE.
36331 
36332      Action:   A operator query  is done to find out  if the read
36333                should be retried or the PV removed from the list.
36334 
36335 
36336 
36337                [bce_save.pl1]
36338                save:    Getting   tape    label   temp   segment.
36339                ERR_MESSAGE
36340 
36341 
36342      Stream:   BOS Typewriter (sounds beeper)
36343 
36344      Time:     System Intialization.
36345 
36346      Meaning:  An  error  occured  while   attempting  to  get  a
36347                temporary   segment  to    hold  the   tape  label
36348                information.
36349 
36350      Action:   Contact the system programming staff.
36351 
36352 
36353                [bce_save_util_.pl1]
36354                save:      Initiating    CONTROL_FILE_NAME     for
36355                set-TAPE_SET_IDX ERR_MESSAGE
36356 
36357 
36358      Stream:   BOS Typewriter (sounds beeper)
36359 
36360      Time:     System Intialization.
36361 
36362      Meaning:  An  error was  detected while  initiating the save
36363                control file.
36364 
36365      Action:   Contact the system programming staff.  $recover
36366 
36367 
36368                [bce_save.pl1]
36369                save:  PV_NAME ERR_MESSAGE
36370 
36371 
36372      Stream:   BOS Typewriter (sounds beeper)
36373 
36374      Time:     System Intialization.
36375 
36376      Meaning:  The   call   to   bootload_disk_io$test_done   has
36377                returned a non-zero error code.
36378 
36379 
36380 save                           628            08/03/23     MR12.7^L
36381 
36382 
36383      Action:   Contact the system programming staff.  $recover
36384 
36385 
36386                [bce_save.pl1]
36387                save:  pvt.  ERR_MESSAGE
36388 
36389 
36390      Stream:   BOS Typewriter (sounds beeper)
36391 
36392      Time:     System Intialization.
36393 
36394      Meaning:  The  program was  unable to  get a  pointer to the
36395                above  segment.  This  indicates a  logic error in
36396                the   supervisor,  or   CPU  or   memory  hardware
36397                problems.
36398 
36399      Action:   Contact the system programming staff.
36400 
36401 
36402                [bce_save.pl1]
36403                save:   Restarting  save   of  set  "TAPE_SET"  on
36404                TAPE_DEV.
36405 
36406 
36407      Stream:   BOS Typewriter.
36408 
36409      Time:     System Intialization.
36410 
36411      Meaning:  Just an informative message.
36412 
36413      Action:   No operator action is required.
36414 
36415 
36416                [bce_save_util_.pl1]
36417                save:    Setting  max   workspace  for   TAPE_DEV.
36418                ERR_MESSAGE
36419 
36420 
36421      Stream:   BOS Typewriter (sounds beeper)
36422 
36423      Time:     System Intialization.
36424 
36425      Meaning:  IOI has returned a non-zero error code in response
36426                to  a request  to set  the max  workspace size for
36427                TAPE_DEV.
36428 
36429      Action:   Contact the system programming staff.
36430 
36431 
36432                [bce_save.pl1]
36433                save:    Setting   status   index   for  TAPE_DEV.
36434                ERR_MESSAGE
36435 
36436 
36437 
36438 save                           629            08/03/23     MR12.7^L
36439 
36440 
36441      Stream:   BOS Typewriter (sounds beeper)
36442 
36443      Time:     System Intialization.
36444 
36445      Meaning:  IOI has returned a  non-zero error, which has been
36446                expanded in ERR_MESSAGE.
36447 
36448      Action:   Contact the system programming staff.
36449 
36450 
36451                [bce_save_util_.pl1]
36452                save:    Setting   up   workspace   for  TAPE_DEV.
36453                ERR_MESSAGE
36454 
36455 
36456      Stream:   BOS Typewriter (sounds beeper)
36457 
36458      Time:     System Intialization.
36459 
36460      Meaning:  IOI  has returned a  non-zero error code  from the
36461                request to create a workspace for TAPE_DEV.
36462 
36463      Action:   Contact the system programming staff.
36464 
36465 
36466                [bce_save_util_.pl1]
36467                save:  si ERR_MESSAGE
36468 
36469 
36470      Stream:   BOS Typewriter (sounds beeper)
36471 
36472      Time:     System Intialization.
36473 
36474      Meaning:  An  error has  been found  with the  internal "si"
36475                structure.This  indicates  a  logic  error  in the
36476                supervisor, or CPU or memory hardware problems.
36477 
36478      Action:   Contact the system programming staff.
36479 
36480 
36481                [bce_save_util_.pl1]
36482                save:  sri ERR_MESSAGE
36483 
36484 
36485      Stream:   BOS Typewriter (sounds beeper)
36486 
36487      Time:     System Intialization.
36488 
36489      Meaning:  An  error has been  found with the  internal "sri"
36490                structure.This  indicates  a  logic  error  in the
36491                supervisor, or CPU or memory hardware problems.
36492 
36493      Action:   Contact the system programming staff.
36494 
36495 
36496 save                           630            08/03/23     MR12.7^L
36497 
36498 
36499 
36500 
36501                [bce_save.pl1]
36502                save:  Stopping save of set "TAPE_SET".
36503 
36504 
36505      Stream:   BOS Typewriter.
36506 
36507      Time:     System Intialization.
36508 
36509      Meaning:  Just an informative message.
36510 
36511      Action:   No operator action is required.
36512 
36513 
36514                [bce_save_util_.pl1]
36515                save:  TAPE_DEV ERR_MESSAGE
36516 
36517 
36518      Stream:   BOS Typewriter (sounds beeper)
36519 
36520      Time:     System Intialization.
36521 
36522      Meaning:  An error occured while scanning the tape subsystem
36523                survey data.
36524 
36525      Action:   Follow normal recovery procedures.
36526 
36527 
36528                [bce_save.pl1]
36529                save:  tape_error_data.  ERR_MESSAGE
36530 
36531 
36532      Stream:   BOS Typewriter (sounds beeper)
36533 
36534      Time:     System Intialization.
36535 
36536      Meaning:  The  program was  unable to  get a  pointer to the
36537                above  segment.  This  indicates a  logic error in
36538                the   supervisor,  or   CPU  or   memory  hardware
36539                problems.
36540 
36541      Action:   Contact the system programming staff.
36542 
36543 
36544                [bce_save.pl1]
36545                save:  Unassigning TAPE_DEV.  ERR_MESSAGE
36546 
36547 
36548      Stream:   BOS Typewriter (sounds beeper)
36549 
36550      Time:     System Intialization.
36551 
36552 
36553 
36554 save                           631            08/03/23     MR12.7^L
36555 
36556 
36557      Meaning:  IOI has returned a  non-zero error, which has been
36558                expanded in ERR_MESSAGE.
36559 
36560      Action:   Contact the system programming staff.
36561 
36562 
36563                [sc_admin_command_.pl1]
36564                sc_admin_command_:  Denied  send_admin_command for
36565                USER in ring RING.
36566 
36567 
36568      Stream:   $sc
36569 
36570      Time:     While system is running.
36571 
36572      Meaning:  User USER requested the system to execute an admin
36573                command,      but       lacked      access      to
36574                >sc1>admin_acs>admin_command.acs.
36575 
36576      Action:   No operator action is required.
36577 
36578 
36579                [sc_admin_command_.pl1]
36580                sc_admin_command_:   Failed  to  check  access for
36581                USER.
36582 
36583 
36584      Stream:   $sc
36585 
36586      Time:     While system is running.
36587 
36588      Meaning:  User USER requested the system to execute an admin
36589                command, but the system  cound not determine their
36590                access to the admin_command acs.
36591 
36592      Action:   No operator action is required.
36593 
36594 
36595                [sc_admin_command_.pl1]
36596                sc_admin_command_:  PERSON:  COMMANDLINE
36597 
36598 
36599      Stream:   $sc
36600 
36601      Time:     While system is running.
36602 
36603      Meaning:  A system administrator has  sent a special command
36604                to  the Initializer,  which executes  it in  admin
36605                mode.
36606 
36607      Action:   No operator action is required.
36608 
36609 
36610 
36611 
36612 sc_init_                       632            08/03/23     MR12.7^L
36613 
36614 
36615                [sc_init_.pl1]
36616                sc_init_:  ERROR_MESSAGE.   Error from iox_$attach
36617                master_i/o ATD
36618 
36619 
36620      Stream:   BOS Typewriter (Crashes system)
36621 
36622      Time:     System Intialization.
36623 
36624      Meaning:  Some  error  was   detected  while  attaching  the
36625                master_i/o switch.  ATD is  the text of the attach
36626                description.   This error  is usually  caused by a
36627                hardware   failure  in  the   operator's  console.
36628                Correct the failure and reboot the system.
36629 
36630      Action:   Contact the system programming staff.
36631 
36632 
36633                [sc_init_.pl1]
36634                sc_init_:  ERROR_MESSAGE.   Error from iox_$attach
36635                user_i/o syn_ master_i/o
36636 
36637 
36638      Stream:   BOS Typewriter (Crashes system)
36639 
36640      Time:     System Intialization.
36641 
36642      Meaning:  Some error  was detected while  attaching user_i/o
36643                as  a synonym  for  the  master_i/o switch  in the
36644                Initializer process.  This is  usually caused by a
36645                hardware   failure  in  the   operator's  console.
36646                Correct the failure and reboot the system.
36647 
36648      Action:   Contact the system programming staff.
36649 
36650 
36651                [sc_init_.pl1]
36652                sc_init_:   ERROR_MESSAGE.   Error  from iox_$open
36653                master_i/o stream_input_output
36654 
36655 
36656      Stream:   BOS Typewriter (Crashes system)
36657 
36658      Time:     System Intialization.
36659 
36660      Meaning:  Some   error  was   detected  while   opening  the
36661                master_i/o  switch.  This  is usually  caused by a
36662                hardware   failure  in  the   operator's  console.
36663                Correct the failure and reboot the system.
36664 
36665      Action:   Contact the system programming staff.
36666 
36667 
36668 
36669 
36670 sc_init_                       633            08/03/23     MR12.7^L
36671 
36672 
36673                [sc_init_.pl1]
36674                sc_init_:    ERROR_MESSAGE.     Failed   to   open
36675                admin_log log.
36676 
36677 
36678      Stream:   BOS Typewriter (sounds beeper)
36679 
36680      Time:     System Intialization.
36681 
36682      Meaning:  The system  failed to iox open the  switch for the
36683                log    >sc1>as_logs>admin_log.      The    segment
36684                >sc1>as_logs>admin_log may be damaged.  The system
36685                enters  a   primitive  Multics  listener   on  the
36686                bootload console.
36687 
36688      Action:   Repair  the problem.   You may  need to  rename or
36689                delete  the segment  >sc1>as_logs>admin_log.  Then
36690                shutdown and reboot.
36691 
36692 
36693 
36694                [sc_init_.pl1]
36695                sc_init_:   Invoking  emergency  listener  because
36696                "nosc" parameter specified.
36697 
36698 
36699      Stream:   BOS Typewriter.
36700 
36701      Time:     System Intialization.
36702 
36703      Meaning:  The  parm config  card specified  nosc (no  system
36704                control).    This  parameter   requests  that   an
36705                emergency listener  be entered to allow  repair of
36706                >sc1 or other parts of the system hierarchy at the
36707                earliest    possible     point    during    system
36708                initialization.    Once  the  repairs   are  made,
36709                shutdown the system  by typing:  "hphcs_$shutdown"
36710                and then reboot the system.
36711 
36712      Action:   Repair  the  problem,  shutdown  the  system, then
36713                reboot.
36714 
36715 
36716                [sc_init_.pl1]
36717                sc_init_:    Messages   from    log   salvage   of
36718                LOG_PATHNAME:
36719 
36720 
36721      Stream:   BOS Typewriter.
36722 
36723      Time:     System Intialization.
36724 
36725 
36726 
36727 
36728 sc_init_                       634            08/03/23     MR12.7^L
36729 
36730 
36731      Meaning:  Some  error was detected  in opening the  admin or
36732                answering  service log specified  by LOG_PATHNAME.
36733                A salvage was invoked to attempt correction of the
36734                problem.  One  or more messages will  succeed this
36735                message  which describe  inconsistancies found  in
36736                the  log, repairs  which were  made, or conditions
36737                which prevent automatic repair.   These will be of
36738                the form "sc_init_:  (log_salvage_) MESSAGE".
36739 
36740      Action:   Contact the system programming staff.
36741 
36742 
36743                [sc_init_.pl1]
36744                sc_init_:   Cound  not  initiate  the  PIT for the
36745                Initializer.
36746 
36747 
36748      Stream:   BOS Typewriter (Crashes system)
36749 
36750      Time:     System Intialization.
36751 
36752      Meaning:  The Initializer has failed to initiate the segment
36753                "pit"  in  its   process  directory.   This  could
36754                indicate  problems  with  the  bootload  tape, the
36755                online libraries, or the hardware.
36756 
36757      Action:   Contact the system programming staff.
36758 
36759 
36760                [sc_init_.pl1]
36761                sc_init_:  Created >system_control_dir>as_logs
36762 
36763 
36764      Stream:   BOS Typewriter (sounds beeper)
36765 
36766      Time:     System Intialization.
36767 
36768      Meaning:  The   system  has   successfully  created   a  new
36769                directory >sc1>as_logs.
36770 
36771      Action:   No  operator action is  required.  If this  is not
36772                the  first bootload  of the  system under  MR11 or
36773                later, you may need  to retrieve log segments lost
36774                in a crash into the new directory.
36775 
36776 
36777 
36778                [sc_init_.pl1]
36779                sc_init_:                           ERROR_MESSAGE.
36780                >system_control_dir>as_logs  does not exist  or is
36781                not a directory.
36782 
36783 
36784 
36785 
36786 sc_init_                       635            08/03/23     MR12.7^L
36787 
36788 
36789      Stream:   BOS Typewriter (sounds beeper)
36790 
36791      Time:     System Intialization.
36792 
36793      Meaning:  The directory >sc1>as_logs must exist for the ring
36794                4 environment to be set up.
36795 
36796      Action:   The system  continues operation, trying  to repair
36797                the  situation.  Subsequent messages  indicate the
36798                success or failure of repairs.
36799 
36800 
36801 
36802                [sc_init_.pl1]
36803                sc_init_:   ERROR_MESSAGE.  Could not  set working
36804                directory to PATH.
36805 
36806 
36807      Stream:   BOS Typewriter (sounds beeper)
36808 
36809      Time:     System Intialization.
36810 
36811      Meaning:  Either some program is  in error, or the directory
36812                PATH does not exist.
36813 
36814      Action:   Contact the system programming staff.  Correct the
36815                problem, shut down, and reboot.
36816 
36817 
36818 
36819                [sc_init_.pl1]
36820                sc_init_:      ERROR_MESSAGE.       Error     from
36821                initiate_search_rules.
36822 
36823 
36824      Stream:   BOS Typewriter (sounds beeper)
36825 
36826      Time:     System Intialization.
36827 
36828      Meaning:  The  Initializer is  attempting to  set its search
36829                rules and has encountered  an error.  This message
36830                may occur if an error has been introduced into the
36831                system tape,  or it may  indicate that one  of the
36832                directories searched  by the Initializer  has been
36833                destroyed.
36834 
36835      Action:   Contact the system programming staff.
36836 
36837 
36838                [sc_init_.pl1]
36839                sc_init_:    ERROR_MESSAGE.    Failed   to  attach
36840                admin_log log.
36841 
36842 
36843 
36844 sc_init_                       636            08/03/23     MR12.7^L
36845 
36846 
36847      Stream:   BOS Typewriter (sounds beeper)
36848 
36849      Time:     System Intialization.
36850 
36851      Meaning:  The  system failed  to  attach  a switch  to write
36852                information      to       the      admin      log,
36853                >sc1>as_logs>admin_log.         The        segment
36854                >sc1>as_logs>admin_log may be damaged.  The system
36855                enters  a   primitive  Multics  listener   on  the
36856                bootload console.
36857 
36858      Action:   Repair  the problem.   You may  have to  delete or
36859                rename  the segment  >sc1>as_logs>admin_log.  Then
36860                shutdown and reboot.
36861 
36862 
36863 
36864                [sc_init_.pl1]
36865                sc_init_:     ERROR_MESSAGE.    Failed    to   get
36866                log_write_ ptr for admin_log.
36867 
36868 
36869      Stream:   BOS Typewriter (sounds beeper)
36870 
36871      Time:     System Intialization.
36872 
36873      Meaning:  This indicated an internal programming error.  The
36874                online libraries may be damaged.
36875 
36876      Action:   Contact the system programming staff.
36877 
36878 
36879                [sc_init_.pl1]
36880                sc_init_:  ERROR_MESSAGE.   Failed to open  the AS
36881                log (>system_control_dir>as_logs>log).
36882 
36883 
36884      Stream:   BOS Typewriter (sounds beeper)
36885 
36886      Time:     System Intialization.
36887 
36888      Meaning:  The   system   was   unable   to   open   the  log
36889                >sc1>as_logs>log.  This may indicate damage to the
36890                segment  >sc1>as_logs>log.   The  system  enters a
36891                primitive   Multics  listener   on  the   bootload
36892                console.
36893 
36894      Action:   Repair  the problem.   You may  have to  rename or
36895                delete   >sc1>as_logs>log.    Then   shutdown  and
36896                reboot.
36897 
36898 
36899 
36900 
36901 
36902 sc_init_                       637            08/03/23     MR12.7^L
36903 
36904 
36905                [sc_init_.pl1]
36906                sc_init_:  Failed  to attach one of  the severityN
36907                (1, 2, 3) switches.
36908 
36909 
36910      Stream:   BOS Typewriter.
36911 
36912      Time:     System Intialization.
36913 
36914      Meaning:  The Initializer  failed to make a syn_  for one of
36915                the   three  switches  severity1,   severity2,  or
36916                severity3.  There may be a problem with the system
36917                tape, the libraries, or the hardware.
36918 
36919      Action:   The system attempts to  enter a primitive listener
36920                environment on  the bootload console.   You should
36921                diagnose  and/or  correct  the  problem  and  then
36922                reboot the system.
36923 
36924 
36925                Message:    sc_init_:    A   serious   error   was
36926                encountered   setting   up   the   system  control
36927                environment.  The system will attempt to establish
36928                a Multics  listener level.  You should  repair the
36929                problem,  and then  type:  "hphcs_$shutdown",  and
36930                reboot the system.
36931 
36932      Stream:   BOS Typewriter.
36933 
36934      Time:     System Intialization.
36935 
36936      Action:   Contact the system programming staff.
36937 
36938 
36939                [sc_init_.pl1]
36940                sc_init_:   Failed to   create ssu  invocation for
36941                system control.
36942 
36943 
36944      Stream:   BOS Typewriter (sounds beeper)
36945 
36946      Time:     System Intialization.
36947 
36948      Meaning:  The  system failed  to set  up the  subsystem data
36949                structure   for   the   bootload   console.   This
36950                indicates a programming error  or trouble with the
36951                system libraries.
36952 
36953      Action:   Contact the system programming staff.
36954 
36955 
36956                [sc_init_.pl1]
36957 
36958 
36959 
36960 sc_init_                       638            08/03/23     MR12.7^L
36961 
36962 
36963                sc_init_:      Renamed    non-directory     object
36964                >system_control_dir>as_logs.
36965 
36966 
36967      Stream:   BOS Typewriter (sounds beeper)
36968 
36969      Time:     System Intialization.
36970 
36971      Meaning:  The  system   found  something  that  was   not  a
36972                directory   in   the   place   of   the  directory
36973                >sc1>as_logs,  and  renamed  it  to  permit  a new
36974                directory to be created.
36975 
36976      Action:   No operator action is required.
36977 
36978 
36979                [sc_process_command_line_.pl1]
36980                sc_process_command_line_:  Error while reattaching
36981                critical I/O switches.
36982 
36983 
36984      Stream:   $sc
36985 
36986      Time:     In response to an operator command.
36987 
36988      Meaning:  $crashesThis  indicates  a   logic  error  in  the
36989                supervisor, or CPU or memory hardware problems.
36990 
36991      Action:   Contact the system programming staff.
36992 
36993 
36994                [sc_process_command_line_.pl1]
36995                sc_process_command_line_:   ERROR_MESSAGE.   Could
36996                not  attach  switch  NAME  (@  LOC)  using  attach
36997                description DESCRIP.
36998 
36999 
37000 
37001      Stream:   $sc
37002 
37003      Time:     In response to an operator command.
37004 
37005      Meaning:  $crashesThis  indicates  a   logic  error  in  the
37006                supervisor,  or CPU  or memory  hardware problems.
37007                ERROR_MESSAGE  is  the  expansion  of  the  system
37008                status  code  describing  the  attach  error.  LOC
37009                gives  the  location  of  the  I/O  Control  Block
37010                (IOCB).
37011 
37012      Action:   Contact the system programming staff.
37013 
37014 
37015                [sc_process_command_line_.pl1]
37016 
37017 
37018 sc_process_command_line_       639            08/03/23     MR12.7^L
37019 
37020 
37021                sc_process_command_line_:   ERROR_MESSAGE.   Could
37022                not open switch NAME for stream_input_output.
37023 
37024 
37025 
37026      Stream:   $sc
37027 
37028      Time:     In response to an operator command.
37029 
37030      Meaning:  $crashesThis  indicates  a   logic  error  in  the
37031                supervisor,  or CPU  or memory  hardware problems.
37032                ERROR_MESSAGE  is  the  expansion  of  the  system
37033                status code describing the open error.
37034 
37035      Action:   Contact the system programming staff.
37036 
37037 
37038                [sc_process_command_line_.pl1]
37039                sc_process_command_line_:   ERROR_MESSAGE.   Could
37040                not restore attachment to switch NAME.
37041 
37042 
37043 
37044      Stream:   $sc
37045 
37046      Time:     In response to an operator command.
37047 
37048      Meaning:  $crashesThis  indicates  a   logic  error  in  the
37049                supervisor,  or CPU  or memory  hardware problems.
37050                ERROR_MESSAGE  is  the  expansion  of  the  system
37051                status code describing the move_attach error.
37052 
37053      Action:   Contact the system programming staff.
37054 
37055 
37056                [sc_process_command_line_.pl1]
37057                sc_process_command_line_:   ERROR_MESSAGE.  Failed
37058                to find save iocb NAME.
37059 
37060 
37061      Stream:   $sc
37062 
37063      Time:     In response to an operator command.
37064 
37065      Meaning:  $crashesThis  indicates  a   logic  error  in  the
37066                supervisor,  or CPU  or memory  hardware problems.
37067                ERROR_MESSAGE  is  the  expansion  of  the  system
37068                status code describing the actual error.
37069 
37070      Action:   Contact the system programming staff.
37071 
37072 
37073                [sc_process_command_line_.pl1]
37074 
37075 
37076 sc_process_command_line_       640            08/03/23     MR12.7^L
37077 
37078 
37079                sc_process_command_line_:   ERROR_MESSAGE.  Failed
37080                to move_attach iocb NAME.
37081 
37082 
37083      Stream:   $sc
37084 
37085      Time:     In response to an operator command.
37086 
37087      Meaning:  $crashesThis  indicates  a   logic  error  in  the
37088                supervisor,  or CPU  or memory  hardware problems.
37089                ERROR_MESSAGE  is  the  expansion  of  the  system
37090                status code describing the actual error.
37091 
37092      Action:   Contact the system programming staff.
37093 
37094 
37095                [sc_process_command_line_.pl1]
37096                sc_process_command_line_:    Terminal  SOURCE_NAME
37097                hung up during execution of command.
37098 
37099 
37100 
37101      Stream:   as (severity 2)
37102 
37103      Time:     In response to an operator command.
37104 
37105      Meaning:  Reports that  execution of an  Initializer command
37106                was  interrupted  when   the  message  coordinator
37107                terminal identified by SOURCE_NAME hung.
37108 
37109      Action:   No operator action is required.
37110 
37111 
37112                [sc_requests_.pl1]
37113                sc_requests_  (set_time_zone):  Changed  time zone
37114                from OLD_ZONE to NEW_ZONE.
37115 
37116 
37117      Stream:   $sc
37118 
37119      Time:     While system is running.
37120 
37121      Meaning:  This  messages  records   that  the  set_time_zone
37122                operator  request was  given, and  that the system
37123                default  time   zone  was  thereby   changed  from
37124                OLD_ZONE to NEW_ZONE.
37125 
37126      Action:   No operator action is required.
37127 
37128 
37129                [sc_signal_handler_.pl1]
37130                sc_signal_handler_:  error:  CONDITION_NAME
37131 
37132 
37133 
37134 sc_signal_handler_             641            08/03/23     MR12.7^L
37135 
37136 
37137      Stream:   as (severity2)
37138 
37139      Time:     While system is running.
37140 
37141      Meaning:  A CONDITION_NAME condition  occurred while running
37142                an  operator command.   An answering  service dump
37143                has  been taken to  further describe the  cause of
37144                the condition.
37145 
37146      Action:   Contact the system programming staff._sa
37147 
37148 
37149                [scas_init.pl1]
37150                scas_init:  Bootload CPU  has no system controller
37151                mask assigned.
37152 
37153 
37154      Stream:   BOS Typewriter (Crashes system)
37155 
37156      Time:     System Intialization.
37157 
37158      Meaning:  No memory assigns a  mask register to the bootload
37159                CPU.
37160 
37161      Action:   Correct the configuration and reboot.
37162 
37163 
37164                [scas_init.pl1]
37165                scas_init:  Bootload CPU may not be on an expander
37166                port.
37167 
37168 
37169      Stream:   BOS Typewriter (Crashes system)
37170 
37171      Time:     System Intialization.
37172 
37173      Meaning:  The CPU config card for the bootload CPU indicates
37174                that  the bootload  CPU  is  on an  expanded port.
37175                This is not permitted.
37176 
37177      Action:   Correct  the  configuration  or  the configuration
37178                deck, and reboot.
37179 
37180 
37181                [scas_init.pl1]
37182                scas_init:  Config card for bootload CPU indicates
37183                unit is offline.
37184 
37185 
37186      Stream:   BOS Typewriter (Crashes system)
37187 
37188      Time:     System Intialization.
37189 
37190 
37191 
37192 scas_init                      642            08/03/23     MR12.7^L
37193 
37194 
37195      Meaning:  The configuration deck is incorrect.
37196 
37197      Action:   Correct  the  configuration  or  the configuration
37198                deck, and reboot.
37199 
37200 
37201                [scas_init.pl1]
37202                scas_init:  Config card for bootload MEM indicates
37203                unit is offline.
37204 
37205 
37206      Stream:   BOS Typewriter (Crashes system)
37207 
37208      Time:     System Intialization.
37209 
37210      Meaning:  The configuration deck is incorrect.
37211 
37212      Action:   Correct the the configuration deck and reboot.
37213 
37214 
37215                [scas_init.pl1]
37216                scas_init:   Config card for  CPU X is  neither on
37217                nor off.
37218 
37219 
37220      Stream:   BOS Typewriter (Crashes system)
37221 
37222      Time:     System Intialization.
37223 
37224      Meaning:  The configuration deck is incorrect.
37225 
37226      Action:   Correct the the configuration deck and reboot.
37227 
37228 
37229                [scas_init.pl1]
37230                scas_init:   Config card for  MEM Y is  neither on
37231                nor off.
37232 
37233 
37234      Stream:   BOS Typewriter (Crashes system)
37235 
37236      Time:     System Intialization.
37237 
37238      Meaning:  The configuration deck is incorrect.
37239 
37240      Action:   Correct the the configuration deck and reboot.
37241 
37242 
37243                [scas_init.pl1]
37244                scas_init:    CPU  config  card   specifies  wrong
37245                controller port number.
37246 
37247 
37248 
37249 
37250 scas_init                      643            08/03/23     MR12.7^L
37251 
37252 
37253      Stream:   BOS Typewriter (Crashes system)
37254 
37255      Time:     System Intialization.
37256 
37257      Meaning:  The configuration deck is incorrect.
37258 
37259      Action:   Correct  the  configuration  or  the configuration
37260                deck, and reboot.
37261 
37262 
37263                [scas_init.pl1]
37264                scas_init:   CPU data  switches are  XXXXXXXXXXXX,
37265                should be YYYYYYYYYYYY
37266 
37267 
37268      Stream:   BOS Typewriter.
37269 
37270      Time:     System Intialization.
37271 
37272      Meaning:  The CPU  data switches are not  set properly.  The
37273                proper values are displayed.
37274 
37275      Action:   The incorrect value will  prevent returning to bce
37276                on that CPU by means of EXECUTE SWITCHES.  Certain
37277                incorrect values will  activate software debugging
37278                traps.   The switches  should be  corrected.  This
37279                can be done while the CPU is running.
37280 
37281 
37282 
37283                [scas_init.pl1]
37284                scas_init:   CPU X and  CPU Y both  configured for
37285                port P subport S
37286 
37287 
37288      Stream:   BOS Typewriter (Crashes system)
37289 
37290      Time:     System Intialization.
37291 
37292      Meaning:  The  CPU  CONFIG  cards  for  CPU's  X  and Y both
37293                indicate that  they are connected to  subport S of
37294                expanded SCU port P.  This is clearly impossible.
37295 
37296      Action:   Correct the configuration deck and reboot.
37297 
37298 
37299                [scas_init.pl1]
37300                scas_init:  CPU X appears twice in config deck.
37301 
37302 
37303      Stream:   BOS Typewriter (Crashes system)
37304 
37305      Time:     System Intialization.
37306 
37307 
37308 scas_init                      644            08/03/23     MR12.7^L
37309 
37310 
37311      Meaning:  The configuration deck is incorrect.
37312 
37313      Action:   Correct the the configuration deck and reboot.
37314 
37315 
37316                [scas_init.pl1]
37317                scas_init:  Illegal expander subport  tag on CPU X
37318                config card.
37319 
37320 
37321      Stream:   BOS Typewriter (Crashes system)
37322 
37323      Time:     System Intialization.
37324 
37325      Meaning:  A CPU config card, for CPU X, specifies an illegal
37326                value for a port-expander subport.  The only legal
37327                values for expander subports are A, B, C, and D.
37328 
37329      Action:   Correct the config deck and reboot.
37330 
37331 
37332                [scas_init.pl1]
37333                scas_init:  Illegal tag on CPU config card.
37334 
37335 
37336      Stream:   BOS Typewriter (Crashes system)
37337 
37338      Time:     System Intialization.
37339 
37340      Meaning:  One or  more CPU cards is incorrect.   Tag must be
37341                one of A, B, C, D, E, F, G, H.
37342 
37343      Action:   Correct  the  configuration  or  the configuration
37344                deck, and reboot.
37345 
37346 
37347                [scas_init.pl1]
37348                scas_init:  Illegal tag on MEM config card.
37349 
37350 
37351      Stream:   BOS Typewriter (Crashes system)
37352 
37353      Time:     System Intialization.
37354 
37355      Meaning:  The configuration deck is  incorrect.  Tag must be
37356                one of A, B, C, D, E, F, G, H.
37357 
37358      Action:   Correct the the configuration deck and reboot.
37359 
37360 
37361                [scas_init.pl1]
37362                scas_init:  MEM X is an old SCU with port expander
37363 
37364 
37365 
37366 scas_init                      645            08/03/23     MR12.7^L
37367 
37368 
37369      Stream:   BOS Typewriter (Crashes system)
37370 
37371      Time:     System Intialization.
37372 
37373      Meaning:  System  controller  X  is  an  old-style  SCU, but
37374                configuration cards indicate that  it has at least
37375                one expanded  port, because there  is a CPU  on an
37376                expanded  port in   the system.   Old-style system
37377                controllers may not have expanded ports.
37378 
37379      Action:   The  configuration deck is  in error.  Fix  it and
37380                reboot.
37381 
37382 
37383                [scas_init.pl1]
37384                scas_init:  MEM X is not enabled.
37385 
37386 
37387      Stream:   BOS Typewriter (Crashes system)
37388 
37389      Time:     System Intialization.
37390 
37391      Meaning:  The bootload CPU does not have MEM X enabled.
37392 
37393      Action:   Correct  the  configuration  or  the configuration
37394                deck, and reboot.
37395 
37396 
37397                [scas_init.pl1]
37398                scas_init:   MEM  Y  address  assignment disagrees
37399                with config deck.
37400 
37401 
37402      Stream:   BOS Typewriter (Crashes system)
37403 
37404      Time:     System Intialization.
37405 
37406      Meaning:  The address  assignment of memory Y,  as read from
37407                the address assignment switches on the maintenance
37408                panel  of  the  bootload  CPU,  disagrees with the
37409                address assignment of this  memory as indicated by
37410                the  relative  position  of  its  MEM  card in the
37411                configuration deck.
37412 
37413      Action:   If the configuration deck is wrong, correct it and
37414                reboot.   If the   configuration deck  is correct,
37415                check   all   address   assignment   switches   on
37416                processors, IOMs,  and the Bulk  Store Controller,
37417                correct them, reboot bce, and reboot.
37418 
37419 
37420 
37421 
37422 
37423 
37424 scas_init                      646            08/03/23     MR12.7^L
37425 
37426 
37427 
37428 
37429                [scas_init.pl1]
37430                scas_init:  MEM Y appears twice in config deck.
37431 
37432 
37433      Stream:   BOS Typewriter (Crashes system)
37434 
37435      Time:     System Intialization.
37436 
37437      Meaning:  The configuration deck is incorrect.
37438 
37439      Action:   Correct the the configuration deck and reboot.
37440 
37441 
37442                [scas_init.pl1]
37443                scas_init:  MEM  Y has duplicate  mask assignments
37444                to CPU X.
37445 
37446 
37447      Stream:   BOS Typewriter (Crashes system)
37448 
37449      Time:     System Intialization.
37450 
37451      Meaning:  The EXECUTE INTERRUPT MASK ASSIGNMENT or MASK/PORT
37452                ASSIGNMENT on memory Y is incorrect.
37453 
37454      Action:   Correct the configuration and reboot.
37455 
37456 
37457                [scas_init.pl1]
37458                scas_init:    MEM  Y   has  mask   Z  assigned  to
37459                non-processor port.
37460 
37461 
37462      Stream:   BOS Typewriter (Crashes system)
37463 
37464      Time:     System Intialization.
37465 
37466      Meaning:  The EXECUTE INTERRUPT MASK ASSIGNMENT or MASK/PORT
37467                ASSIGNMENT on memory Y is incorrect.
37468 
37469      Action:   Correct the configuration and reboot.
37470 
37471 
37472                [scas_init.pl1]
37473                scas_init:  MEM  Y has more memory  than indicated
37474                by CPU switches.
37475 
37476 
37477      Stream:   BOS Typewriter (Crashes system)
37478 
37479      Time:     System Intialization.
37480 
37481 
37482 scas_init                      647            08/03/23     MR12.7^L
37483 
37484 
37485      Meaning:  The  PORT SIZE  plug on  the free  edge of  the PQ
37486                board of the bootload CPU  does not agree with the
37487                STORE SIZE switch on MEM Y.
37488 
37489      Action:   Correct the configuration and reboot.
37490 
37491 
37492                [scas_init.pl1]
37493                scas_init:  MEM Y has no mask assigned to CPU X.
37494 
37495 
37496      Stream:   BOS Typewriter (Crashes system)
37497 
37498      Time:     System Intialization.
37499 
37500      Meaning:  The EXECUTE INTERRUPT MASK ASSIGNMENT or MASK/PORT
37501                ASSIGNMENT on memory Y is incorrect.
37502 
37503      Action:   Correct the configuration and reboot.
37504 
37505 
37506                [scas_init.pl1]
37507                scas_init:  MEM Y is not in PROGRAM mode.
37508 
37509 
37510      Stream:   BOS Typewriter (Crashes system)
37511 
37512      Time:     System Intialization.
37513 
37514      Meaning:  The MODE switch for memory Y is incorrect.
37515 
37516      Action:   Correct the configuration and reboot.
37517 
37518 
37519                [scas_init.pl1]
37520                scas_init:  MEM Y is not in the configuration, but
37521                is enabled by the CPU switches.
37522 
37523 
37524      Stream:   BOS Typewriter (Crashes system)
37525 
37526      Time:     System Intialization.
37527 
37528      Meaning:  The bootload  CPU enables memory Y.   But there is
37529                no MEM card for this memory.
37530 
37531      Action:   Correct  the  configuration  or  the configuration
37532                deck, and reboot.
37533 
37534 
37535                [scas_init.pl1]
37536                scas_init:  More than one low-order MEM.
37537 
37538 
37539 
37540 scas_init                      648            08/03/23     MR12.7^L
37541 
37542 
37543      Stream:   BOS Typewriter (Crashes system)
37544 
37545      Time:     System Intialization.
37546 
37547      Meaning:  The configuration deck is incorrect.
37548 
37549      Action:   Correct the the configuration deck and reboot.
37550 
37551 
37552                [scas_init.pl1]
37553                scas_init:  No config card for bootload CPU.
37554 
37555 
37556      Stream:   BOS Typewriter (Crashes system)
37557 
37558      Time:     System Intialization.
37559 
37560      Meaning:  The configuration deck is incorrect.
37561 
37562      Action:   Correct  the  configuration  or  the configuration
37563                deck, and reboot.
37564 
37565 
37566                [scas_init.pl1]
37567                scas_init:  No config card for bootload MEM
37568 
37569 
37570      Stream:   BOS Typewriter (Crashes system)
37571 
37572      Time:     System Intialization.
37573 
37574      Meaning:  The configuration deck is incorrect.
37575 
37576      Action:   Correct the the configuration deck and reboot.
37577 
37578 
37579                [scas_init.pl1]
37580                scas_init:  No CPU config card.
37581 
37582 
37583      Stream:   BOS Typewriter (Crashes system)
37584 
37585      Time:     System Intialization.
37586 
37587      Meaning:  The configuration deck is incorrect.
37588 
37589      Action:   Correct the the configuration deck and reboot.
37590 
37591 
37592                [scas_init.pl1]
37593                scas_init:  No MEM config card.
37594 
37595 
37596 
37597 
37598 scas_init                      649            08/03/23     MR12.7^L
37599 
37600 
37601      Stream:   BOS Typewriter (Crashes system)
37602 
37603      Time:     System Intialization.
37604 
37605      Meaning:  The configuration deck is incorrect.
37606 
37607      Action:   Correct the the configuration deck and reboot.
37608 
37609 
37610                [scas_init.pl1]
37611                scas_init:  Possible memory address overlap in MEM
37612                Y.
37613 
37614 
37615      Stream:   BOS Typewriter (Crashes system)
37616 
37617      Time:     System Intialization.
37618 
37619      Meaning:  This indicates that the  lower store size does not
37620                agree  with  the  actual  memory  available in the
37621                store  unit.  A possible  example of this  is when
37622                the lower store is actually  in two store units (A
37623                and  A1)  and  the  secondary  unit  (A1)  is  not
37624                enabled.
37625 
37626      Action:   Correct the configuration and reboot.
37627 
37628 
37629                [scas_init.pl1]
37630                scas_init:  SCU port P configured as both expanded
37631                and non-expanded.
37632 
37633 
37634      Stream:   BOS Typewriter (Crashes system)
37635 
37636      Time:     System Intialization.
37637 
37638      Meaning:  CPU configuration cards imply that Port P on SCU's
37639                (P  is the port  number, from 0  to 7) is  both an
37640                expander port (by being named as the CPU port in a
37641                CPU card with an  expander_port field), and not an
37642                expander  port (by  being  named  in one  that has
37643                none).
37644 
37645      Action:   Correct the configuratin deck and reboot.
37646 
37647 
37648                [scas_init.pl1]
37649                scas_init:  Size too large  on config card for MEM
37650                Y.
37651 
37652 
37653      Stream:   BOS Typewriter (Crashes system)
37654 
37655 
37656 scas_init                      650            08/03/23     MR12.7^L
37657 
37658 
37659      Time:     System Intialization.
37660 
37661      Meaning:  Either the PORT SIZE plug  on the free edge of the
37662                PQ board  of the bootload CPU does  not agree with
37663                the  configuration deck,  or the  actual amount of
37664                memory present  in MEM Y  does not agree  with the
37665                config deck.
37666 
37667 
37668      Action:   Correct  the  configuration  or  the configuration
37669                deck, and reboot.
37670 
37671 
37672                [scavenge_volume.pl1]
37673                scavenge_volume:  damaged switch found on for NAME
37674                at VTOCX (dskX_NN{S})
37675 
37676 
37677      Stream:   Logged in SYSERR log.
37678 
37679      Time:     During a physical volume scavenge of dskX_NN{S}
37680 
37681      Meaning:  The  damaged switch in  the VTOCEwas set  prior to
37682                the scavenge.
37683 
37684      Action:   Recover the segment.
37685 
37686 
37687                [scavenge_volume.pl1]
37688                scavenge_volume:      Damaged      vtoce     VTOCX
37689                (dskX_NN{S}).
37690 
37691 
37692      Stream:   Logged in SYSERR log.
37693 
37694      Time:     During a physical volume scavenge of dskX_NN{S}
37695 
37696      Meaning:  The VTOCE image before correction is recorded into
37697                the  syserr log  if scavenge_vol  was invoked with
37698                the -dump control argument.
37699 
37700      Action:   No operator action is required.
37701 
37702 
37703                [scavenge_volume.pl1]
37704                scavenge_volume:    Debug  Trap  on   scavenge  of
37705                dskX_NN{S}
37706 
37707 
37708      Stream:   BOS Typewriter (Crashes system)
37709 
37710      Time:     At  the   completion  of  a  volume   scavenge  of
37711                dskX_NN{S}
37712 
37713 
37714 scavenge_volume                651            08/03/23     MR12.7^L
37715 
37716 
37717      Meaning:  This  is  a  debugging  trap  which  results  when
37718                scavenge_vol  is  used   with  the  -trap  control
37719                argument.
37720 
37721      Action:   Type GO to resume Multics operation.
37722 
37723 
37724                [scavenge_volume.pl1]
37725                scavenge_volume:   dirsw turned   off for  NAME at
37726                VTOCX (dskX_NN{S})
37727 
37728 
37729      Stream:   Logged in SYSERR log.
37730 
37731      Time:     During a physical volume scavenge of dskX_NN{S}
37732 
37733      Meaning:  The directory switch in the VTOCE was found on for
37734                a non-directory segment.  It  has been turned off.
37735                The segment has been damaged.
37736 
37737      Action:   Recover the segment.
37738 
37739 
37740                [scavenge_volume.pl1]
37741                scavenge_volume:   Error freeing TYPE  vtocx VTOCX
37742                on dskX_NN{S}.  ERRORMESSAGE
37743 
37744 
37745      Stream:   Logged in SYSERR log.
37746 
37747      Time:     During a physical volume scavenge of dskX_NN{S}.
37748 
37749      Meaning:  The VTOCE indicated could not  be freed due to the
37750                error indicated.
37751 
37752      Action:   No operator action is required.
37753 
37754 
37755                [scavenge_volume.pl1]
37756                scavenge_volume:   Error  reading  vtocx  NNNN  on
37757                dskX_NN{S}.  ERRORMESSAGE
37758 
37759 
37760      Stream:   Logged in SYSERR log.
37761 
37762      Time:     During a physical volume scavenge of dskX_NN{S}
37763 
37764      Meaning:  An  error was  encountered attempting  to read the
37765                VTOCE indicated.   The VTOCE is skipped,  and lost
37766                records  are not  recovered.  The  count of volume
37767                inconsistencies is not reset to zero.
37768 
37769 
37770 
37771 
37772 scavenge_volume                652            08/03/23     MR12.7^L
37773 
37774 
37775      Action:   After  the  problems  with  the  volume  have been
37776                repaired, run the scavenger  again to recover lost
37777                records.
37778 
37779 
37780 
37781                [scavenge_volume.pl1]
37782                scavenge_volume:   Error  writing  vtocx  NNNNN on
37783                dskX_NN{S}.  ERRORMESSAGE
37784 
37785 
37786      Stream:   Logged in SYSERR log.
37787 
37788      Time:     During a physical volume scavenge of dskX_NN{S}
37789 
37790      Meaning:  The  error  indicated  was  encountered  writing a
37791                VTOCE.
37792 
37793      Action:   No operator action is required.
37794 
37795 
37796                [scavenge_volume.pl1]
37797                scavenge_volume:   Faulting  under  the  LOCK  for
37798                debugging for USER
37799 
37800 
37801      Stream:   BOS Typewriter (sounds beeper)
37802 
37803      Time:     During a physical volume salvage.
37804 
37805      Meaning:  A fault tag three fault is taken to exercise fault
37806                recovery.
37807 
37808      Action:   No operator action is required.
37809 
37810 
37811                [scavenge_volume.pl1]
37812                scavenge_volume:  Freed NNN VTOCEs on dskX_NN{S}
37813 
37814 
37815      Stream:   Logged in SYSERR log.
37816 
37817      Time:     During a physical volume scavenge of dskX_NN{S}
37818 
37819      Meaning:  NNN  VTOCEs were  added to  the free  pool.  These
37820                VTOCEs  are VTOCEs  found free  but not  marked as
37821                free  in the VTOC  map, per-process VTOCEs  from a
37822                prior  bootload, and   per-bootload VTOCEs  from a
37823                prior bootload.
37824 
37825                Message:   scavenge_volume:  vtoce  NAME at  VTOCX
37826                (dskX_NN{S}) disk addr RRR bad
37827 
37828 
37829 
37830 scavenge_volume                653            08/03/23     MR12.7^L
37831 
37832 
37833      Stream:   Logged in SYSERR log.
37834 
37835      Time:     During a physical volume scavenge of dskX_NN{S}
37836 
37837      Meaning:  Record  address  RRR  in  the  VTOCE  indicated is
37838                outside of the paging  region for the volume.  The
37839                segment has been damaged.
37840 
37841      Action:   Recover the segment.
37842 
37843 
37844                [scavenge_volume.pl1]
37845                scavenge_volume:  Freed NNNN records on dskX_NN{S}
37846 
37847 
37848      Stream:   Logged in SYSERR log.
37849 
37850      Time:     During a physical volume scavenge of dskX_NN{S}
37851 
37852      Meaning:  NNNN  records were  not claimed  by any  VTOCE and
37853                were not listed as free  in the volume map.  These
37854                records have been freed.
37855 
37856      Action:   No operator action is required.
37857 
37858 
37859                [scavenge_volume.pl1]
37860                scavenge_volume:  freeing TYPE VTOCE NAME at VTOCX
37861                (dskX_NN{S})
37862 
37863 
37864      Stream:   Logged in SYSERR log.
37865 
37866      Time:     During a physical volume scavenge of dskX_NN{S}
37867 
37868      Meaning:  The  message  appears  for  each  VTOCE  freed  if
37869                scavenge_vol was  invoked with the  -debug control
37870                argument.
37871 
37872      Action:   No operator action is required.
37873 
37874 
37875                [scavenge_volume.pl1]
37876                scavenge_volume:   Invalid File  Map Checksum  for
37877                NAME at VTOCX (dskX_NN{S}).
37878 
37879 
37880      Stream:   Logged in SYSERR log.
37881 
37882      Time:     During a physical volume scavenge of dskX_NN{S}.
37883 
37884 
37885 
37886 
37887 
37888 scavenge_volume                654            08/03/23     MR12.7^L
37889 
37890 
37891      Meaning:  The  filemap  checksum  was  incorrect, indicating
37892                damage to  the VTOCE.  The checksum  is corrected.
37893                Other damage, if found, is reported.
37894 
37895      Action:   No operator action is required.
37896 
37897 
37898                [scavenge_volume.pl1]
37899                scavenge_volume:   NNN  errors  reading  VTOCEs on
37900                dskX_NN{S}
37901 
37902 
37903      Stream:   BOS Typewriter.
37904 
37905      Time:     During a physical volume scavenge of dskX_NN{S}
37906 
37907      Meaning:  Errors were encountered reading VTOCEs.  A message
37908                describing each error was recorded into the syserr
37909                log.  The VTOCEs with errors are skipped, and lost
37910                records are not recovered.
37911 
37912      Action:   When  the  volume  has  been  repaired,  rerun the
37913                scavenger to recover the lost records.
37914 
37915 
37916 
37917                [scavenge_volume.pl1]
37918                scavenge_volume:    NNN   VTOCEs   on   dskX_NN{S}
37919                damaged.  MMM damaged during this scavenge.
37920 
37921 
37922      Stream:   BOS Typewriter.
37923 
37924      Time:     At  the   completion  of  a  volume   scavenge  of
37925                dskX_NN{S}
37926 
37927      Meaning:  The  scavenger  found  a   total  of  NNN  damaged
37928                segments  on  the  volume.   Of  these,  MMM  were
37929                damaged by the scavenger due to inconsistencies in
37930                the VTOCEs for these segments.  A message for each
37931                was recorded into the syserr log.
37932 
37933      Action:   Examine  the  syserr  log   to  find  the  damaged
37934                segments and recover them.
37935 
37936 
37937                [scavenge_volume.pl1]
37938                scavenge_volume:  Out-of-service  address in stock
37939                for dskX_NN{S}
37940 
37941 
37942      Stream:   BOS Typewriter (Crashes system)
37943 
37944 
37945 
37946 scavenge_volume                655            08/03/23     MR12.7^L
37947 
37948 
37949      Time:     During a scavenge of dskX_NN{S}
37950 
37951      Meaning:  While    examining   the    record   stock,    and
37952                out-of-service  address was  encountered.  Due  to
37953                the volume map locking protocols used, this should
37954                never happen.   It indicates hardware  or software
37955                malfunction.
37956 
37957      Action:   Follow   normal  recovery   procedures.   Message:
37958                scavenge_volume:    Processing   vtocx   NNNNN  on
37959                dskX_NN{S}
37960 
37961      Stream:   BOS Typewriter.
37962 
37963      Time:     During a volume scavenge of dskX_NN{S}
37964 
37965      Meaning:  This message is printed  every 2000 (octal) VTOCEs
37966                during the  scan of the  VTOC by the  scavenger if
37967                scavenge_vol was invoked with the -debug option.
37968 
37969      Action:   No operator action is required.
37970 
37971 
37972                [scavenge_volume.pl1]
37973                scavenge_volume:    Overflow    on   scavenge   of
37974                dskX_NN{S}.  Restarting.
37975 
37976 
37977      Stream:   BOS Typewriter.
37978 
37979      Time:     During a physical volume scavenge of dskX_NN{S}.
37980 
37981      Meaning:  An  internal  table  which  tracks  reused  record
37982                addresses  overflowed.  All conflicts  detected so
37983                far  are resolved,  and the  scavenge is restarted
37984                from the beginning.
37985 
37986      Action:   No operator action is required.
37987 
37988 
37989                [scavenge_volume.pl1]
37990                scavenge_volume:   setting damaged switch  on NAME
37991                at VTOCX (dskX_NN{S}).
37992 
37993 
37994      Stream:   Logged in SYSERR log.
37995 
37996      Time:     During a physical volume scavenge of dskX_NN{S}
37997 
37998      Meaning:  An  inconsistency has  been detected  in the VTOCE
37999                and  the damaged switch  has been set.   A message
38000                describing the inconsistency  has been recorded in
38001 
38002 
38003 
38004 scavenge_volume                656            08/03/23     MR12.7^L
38005 
38006 
38007                the syserr log.  The binary information associated
38008                with this message includes the segment UID-path.
38009 
38010      Action:   Recover the segment.
38011 
38012 
38013                [scavenge_volume.pl1]
38014                scavenge_volume:   Unable to resolve  conflict for
38015                address RRR on dskX_NN{S}.  astep=PTR
38016 
38017 
38018      Stream:   Logged in SYSERR log.
38019 
38020      Time:     During a physical volume scavenge of dskX_NN{S}
38021 
38022      Meaning:  During the  scan of the VTOC,  the scavenger found
38023                several  VTOCEs  which  claimed  the  same  record
38024                address RRR.   It could not resolve  the conflict,
38025                since  the  segment  with  the  ASTE indicated was
38026                active and could not be deactivated.
38027 
38028      Action:   Rerun the  scavenger at a  later time.  It  may be
38029                necessary to wait until the next bootload.
38030 
38031 
38032 
38033                [scavenge_volume.pl1]
38034                scavenge_volume:   Unable to resolve  conflict for
38035                address RRR  on dskX_NN{S}.  Error at  vtocx NNNN.
38036                ERRORMESSAGE.
38037 
38038 
38039      Stream:   Logged in SYSERR log.
38040 
38041      Time:     During a physical volume scavenge of dskX_NN{S}
38042 
38043      Meaning:  During the VTOC walk,  the scavenger found several
38044                VTOCEs  claiming  the  save  address  RRR.  It was
38045                unable to resolve the conflict due to a VTOCE read
38046                error.
38047 
38048      Action:   After  the  volume  has  been  repaired, rerun the
38049                scavenger.
38050 
38051 
38052                [scavenge_volume.pl1]
38053                scavenge_volume:     vtoce     NAME    at    VTOCX
38054                (dskX_NN{S}).  cur len changed from X to Y
38055 
38056 
38057      Stream:   Logged in SYSERR log.
38058 
38059      Time:     During a physical volume scavenge of dskX_NN{S}
38060 
38061 
38062 scavenge_volume                657            08/03/23     MR12.7^L
38063 
38064 
38065      Meaning:  The current segment length  field in the VTOCE has
38066                been corrected.  The segment has been damaged.
38067 
38068      Action:   Recover the segment.
38069 
38070 
38071                [scavenge_volume.pl1]
38072                scavenge_volume:     vtoce     NAME    at    VTOCX
38073                (dskX_NN{S}).  max len changed from X to Y
38074 
38075 
38076      Stream:   Logged in SYSERR log.
38077 
38078      Time:     During a physical volume scavenge of dskX_NN{S}
38079 
38080      Meaning:  The  max  length  field  in  the  VTOCE  has  been
38081                corrected.  The segment has been damaged.
38082 
38083      Action:   Recover the segment.
38084 
38085 
38086                [scavenge_volume.pl1]
38087                scavenge_volume:     vtoce     NAME    at    VTOCX
38088                (dskX_NN{S}).  rec used changed from X to Y
38089 
38090 
38091      Stream:   Logged in SYSERR log.
38092 
38093      Time:     During a physical volume scavenge of dskX_NN{S}
38094 
38095      Meaning:  The  records  used  field  in  the  VTOCE has been
38096                corrected.  The segment has been damaged.
38097 
38098      Action:   Recover the segment.
38099 
38100 
38101                [scavenge_volume.pl1]
38102                scavenge_volume:     vtoce     NAME    at    VTOCX
38103                (dskX_NN{S}).   ref  to  pageno  PPP  at  addr RRR
38104                deleted
38105 
38106 
38107      Stream:   Logged in SYSERR log.
38108 
38109      Time:     During a physical volume scavenge of dskX_NN{S}
38110 
38111      Meaning:  Address  RRR was claimed  by more than  one VTOCE.
38112                The  page indicated  has  been  changed to  a null
38113                page, and the segment has been damaged.
38114 
38115      Action:   Recover the segment.
38116 
38117 
38118 
38119 
38120 scavenge_volume                658            08/03/23     MR12.7^L
38121 
38122 
38123                [scavenge_volume.pl1]
38124                scavenge_volume:     vtoce     NAME    at    VTOCX
38125                (dskX_NN{S}).  time-record-product reset to zero
38126 
38127 
38128      Stream:   Logged in SYSERR log.
38129 
38130      Time:     During a physical volume scavenge of dskX_NN{S}
38131 
38132      Meaning:  An    invalid    value    was    found    in   the
38133                time-record-product field of  the VTOCE indicated.
38134                This field has been reset to zero.
38135 
38136      Action:   No operator action is required.
38137 
38138 
38139                [scavenger.pl1]
38140                scavenger:    Begin  scavenge  of   dskX_NN{s}  by
38141                PERSON.PROJECT.TAG
38142 
38143 
38144      Stream:   BOS Typewriter.
38145 
38146      Time:     When a physical volume is being scavenged
38147 
38148      Meaning:  This is an informational  message at the beginning
38149                of a volume scavenge.
38150 
38151      Action:   No operator action is required.
38152 
38153 
38154                [scavenger.pl1]
38155                scavenger:  Invalid block reset.
38156 
38157 
38158      Stream:   BOS Typewriter (Crashes system)
38159 
38160      Time:     When a physical volume is being scavenged.
38161 
38162      Meaning:  A process attempted to  clean up a scavenger block
38163                which  was not assigned  to it.  This  indicates a
38164                software malfunction.
38165 
38166      Action:   Follow normal recovery procedures.
38167 
38168 
38169                [scavenger.pl1]
38170                scavenger:   Meters from  scavenge of  dskX_NN{s}.
38171                METERINGDATA.
38172 
38173 
38174      Stream:   Logged in SYSERR log.
38175 
38176 
38177 
38178 scavenger                      659            08/03/23     MR12.7^L
38179 
38180 
38181      Time:     When a physical volume is being scavenged.
38182 
38183      Meaning:  Various  peformance measurements  of the  scavenge
38184                are recorded if  the appropriate scavenger control
38185                flag is set.
38186 
38187      Action:   No operator action is required.
38188 
38189 
38190                [scavenger.pl1]
38191                scavenger:  Process table entry  not owned by this
38192                process.
38193 
38194 
38195      Stream:   BOS Typewriter (Crashes system)
38196 
38197      Time:     When a physical volume is being scavenged.
38198 
38199      Meaning:  The scavenger attempted to release a process table
38200                entry which did not  belong to this process.  This
38201                indicates a software malfunction.
38202 
38203      Action:   Follow normal recovery procedures.
38204 
38205 
38206                [scavenger.pl1]
38207                scavenger:     Scavenge     of    dskX_NN{s}    by
38208                PERSON.PROJECT.TAG    completed     with    error.
38209                ERRORMESSAGE.
38210 
38211 
38212      Stream:   BOS Typewriter.
38213 
38214      Time:     When a physical volume is being scavenged.
38215 
38216      Meaning:  Scavenging could  not be completed because  of the
38217                error indicated.
38218 
38219      Action:   Contact the system programming staff.
38220 
38221 
38222                [scavenger.pl1]
38223                scavenger:     Scavenge     of    dskX_NN{s}    by
38224                PERSON.PROJECT.TAG completed.
38225 
38226 
38227      Stream:   BOS Typewriter.
38228 
38229      Time:     When a physical volume is being scavenged.
38230 
38231      Meaning:  This  is  an  informational  message  to  indicate
38232                successful completion of a scavenge.
38233 
38234 
38235 
38236 scavenger                      660            08/03/23     MR12.7^L
38237 
38238 
38239      Action:   No operator action is required.
38240 
38241 
38242                [scavenger.pl1]
38243                scavenger:  Scavenge of dskX_NN{s} stopped.
38244 
38245 
38246      Stream:   BOS Typewriter.
38247 
38248      Time:     During system shutdown.
38249 
38250      Meaning:  The  system is being  shutdown, and a  scavenge of
38251                dskX_NN{s}  is  in   progress.   The  scavenge  is
38252                terminated and likely had no effect.
38253 
38254      Action:   Rerun the scavenge.
38255 
38256 
38257                [scavenger.pl1]
38258                scavenger:   XXXXXX   condition  signalled  during
38259                scavenge of dskX_NN{s} by PERSON.PROJECT.TAG
38260 
38261 
38262      Stream:   BOS Typewriter.
38263 
38264      Time:     When a physical volume is being scavenged.
38265 
38266      Meaning:  An  unexpected  XXXXXX   condition  was  signalled
38267                during   a  volume   scavenge,  causing   abnormal
38268                termination of the scavenge.
38269 
38270      Action:   Contact the system programming staff.
38271 
38272 
38273                [scr_util.pl1]
38274                scr_util:   error setting  configuration register.
38275                SCU  X must  be set  manually.  Set  the following
38276                switches  on SCU  X <  Diagram of  SCU Maintenance
38277                Panel is Printed Here>  After setting the switches
38278                for SCU  X place SCU  S into Manual  Mode and then
38279                into Program Mode
38280 
38281 
38282 
38283      Stream:   BOS Typewriter (sounds beeper)
38284 
38285      Time:     Reconfiguration (e.g., adding or deleting a CPU)
38286 
38287      Meaning:  The supervisor was unable to set the configuration
38288                register in  the SCU indicated after  10 attempts.
38289                To avoid  a system crash, the SCU  must be cleared
38290                manually.   In this  message, the  supervisor will
38291 
38292 
38293 
38294 scr_util                       661            08/03/23     MR12.7^L
38295 
38296 
38297                print  a  diagram  of  the  SCU Maintenance Panel,
38298                indicating how each switch should be set.
38299 
38300      Action:   The  operator should copy  the diagram of  the SCU
38301                Maintenance  Panel printed  by the  supervisor (or
38302                take the copy printed, if possible).  The operator
38303                should then go to the Maintenance Panel of the SCU
38304                indicated  and set each  switch on the  diagram to
38305                the indicated position, and  then verify that each
38306                switch  is  in  the  correct  position.  Following
38307                this, the  operator should set  the Program/Manual
38308                switch into the Manual  position briefly, and then
38309                return  it  to  the  Program  position.   If  this
38310                procedure does not remedy the problem, the message
38311                will be repeated, and the System Programming Staff
38312                should be contacted.
38313 
38314 
38315 
38316                [scs_and_clock_init.pl1]
38317                scs_and_clock_init:  No CLOK card.
38318 
38319 
38320      Stream:   BOS Typewriter (Crashes system)
38321 
38322      Time:     System Intialization.
38323 
38324      Meaning:  No CLOK card was found in the config deck.  One is
38325                required.
38326 
38327      Action:   Add a CLOK card to the config deck.
38328 
38329 
38330                [scs_and_clock_init.pl1]
38331                scs_and_clock_init:   No  SCU   port  is  assigned
38332                address zero.
38333 
38334 
38335      Stream:   BOS Typewriter (Crashes system)
38336 
38337      Time:     System Intialization.
38338 
38339      Meaning:  None of the system  controllers in the config deck
38340                appear to have a base address of zero.
38341 
38342      Action:   Check the config deck  and bootload processor port
38343                assignment and address switches.
38344 
38345 
38346 
38347                [scs_and_clock_init.pl1]
38348                scs_and_clock_init:   SCU  clock  on  port  NUMBER
38349                MALFUNCTION.
38350 
38351 
38352 scs_and_clock_init             662            08/03/23     MR12.7^L
38353 
38354 
38355      Stream:   BOS Typewriter.
38356 
38357      Time:     System Intialization.
38358 
38359      Meaning:  The calendar clock in the bootload SCU seems to be
38360                malfunctioning, as specified by MALFUNCTION.
38361 
38362      Action:   Fix  the  SCU,  or  configure  another  SCU as low
38363                order.
38364 
38365 
38366                [scs_and_clock_init.pl1]
38367                scs_and_clock_init:  The zone on  the CLOK card is
38368                not in time_info_.
38369 
38370 
38371      Stream:   BOS Typewriter (Crashes system)
38372 
38373      Time:     System Intialization.
38374 
38375      Meaning:  The zone  named on the  CLOK card is  not found in
38376                time_info_,   the    system's   time   information
38377                database.   The system  cannot run  unless a known
38378                zone is specified.
38379 
38380      Action:   Update the CLOK card so  that it contains a proper
38381                zone name.  If  the zone you need is  not known to
38382                the  system,   time_info_.cds  will  have   to  be
38383                updated,  a new  system tape  generated, and  then
38384                booting  from that  tape.  time_info_  contains at
38385                least 1 name for each  hour around the world.  You
38386                may  select a  named zone  near the  one you need,
38387                just  to get the  system up to  be able to  change
38388                time_info_.
38389 
38390 
38391 
38392 
38393                [scas_init.pl1]
38394                scs_init:   CPU/IOM  port  range  overlap.   Using
38395                manual settings for cycle port priority.
38396 
38397 
38398      Stream:   BOS Typewriter.
38399 
38400      Time:     System Intialization.
38401 
38402      Meaning:  The cycle port priority on  the SCUs cannot be set
38403                optimally  because the  range of  port numbers for
38404                CPUs and IOMs overlap.  The manual settings of the
38405                cycle port  priority switches on the  SCUs will be
38406                used instead.  The  system may experience problems
38407                as  a  result,  with  the  typical  symptom  being
38408 
38409 
38410 scs_init                       663            08/03/23     MR12.7^L
38411 
38412 
38413                op-not-complete  faults at   random times  by CPUs
38414                with   higher  port    numbers  (lower   SCU  port
38415                priority).
38416 
38417      Action:   Continue  to  operate  the  system  normally,  but
38418                consult  with  Field  Engineering  personnel.   If
38419                possible,  the system   should be  reconfigured so
38420                that the range of port  numbers of IOMs and CPU do
38421                not   overlap.    Further,   CPU   should   be  on
38422                higher-numbered ports than IOMs and Bulk Stores.
38423 
38424 
38425 
38426                [alm_syserr_caller.pl1]
38427                search_ast:   double  uid  UID.   vtocx  VTOCX  on
38428                DRIVE(PVID).      active    vtocx     VTOCX2    on
38429                DRIVE2(PVID2).
38430 
38431 
38432      Stream:   Logged in SYSERR log.
38433 
38434      Time:     While system is running.
38435 
38436      Meaning:  A  mismatch has  been detected  between the branch
38437                and  the ASTE  for  a  segment.  The  two segments
38438                indicated  by  VTOCE  index  and  physical  volume
38439                location/identifier  claim to  have the  same file
38440                system  unique identifier.   The operation  either
38441                proceeds  or returns  a connection  failure to the
38442                user  process, as   appropriate.  This  message is
38443                logged for the use of system programmers.
38444 
38445                This  error can  occur  if  damage to  a directory
38446                branch  has   caused  its  unique  ID   to  become
38447                incorrect, and if the  incorrect unique ID happens
38448                to  be identical  to the  unique ID  of a  segment
38449                already active.
38450 
38451      Action:   Contact the system programming staff.
38452 
38453 
38454                [alm_syserr_caller.pl1]
38455                search_ast:  hash error
38456 
38457 
38458      Stream:   BOS Typewriter (Crashes system)
38459 
38460      Time:     While system is running.
38461 
38462      Meaning:  This indicates a logic error in the supervisor, or
38463                CPU or memory hardware problems.
38464 
38465      Action:   Follow normal recovery procedures.
38466 
38467 
38468 seg_fault                      664            08/03/23     MR12.7^L
38469 
38470 
38471 
38472 
38473                [seg_fault.pl1]
38474                seg_fault:  illegal segfault on cpu X
38475 
38476 
38477      Stream:   BOS Typewriter.
38478 
38479      Time:     While system is running.
38480 
38481      Meaning:  The SCU data stored  by processor X indicates that
38482                a segment fault has occurred but the SDW indicated
38483                by the  SCU data has no  directed fault indicator.
38484                This indicates a logic error in the supervisor, or
38485                CPU  or  memory  hardware  problems.   The  system
38486                attempts to retry the faulting instruction.
38487 
38488      Action:   Inform  field  engineering   personnel.   If  this
38489                message persists, attempt to delete the CPU.
38490 
38491 
38492 
38493                [seg_fault.pl1]
38494                seg_fault:  trailer list trap
38495 
38496 
38497      Stream:   BOS Typewriter (Crashes system)
38498 
38499      Time:     While system is running.
38500 
38501      Meaning:  An  attempt was  made to  set sst$tfreep  to zero.
38502                The  supervisor  checks  for  this  situation  and
38503                crashes here when one entry remains in the trailer
38504                segment in order to trap an elusive bug which used
38505                to cause "trailer  storage area exhausted" crashes
38506                when  the  trailer  segment  was  not  full.  This
38507                indicates a logic error  in the supervisor, or CPU
38508                or  memory  hardware   problems.   BOS  Typewriter
38509                (Crashes system)es
38510 
38511      Action:   Follow normal recovery procedures.  Be sure to get
38512                a dump.
38513 
38514 
38515 
38516                [seg_fault.pl1]
38517                seg_fault:  trailer storage area exhausted
38518 
38519 
38520      Stream:   BOS Typewriter (Crashes system)
38521 
38522      Time:     While system is running.
38523 
38524 
38525 
38526 seg_fault                      665            08/03/23     MR12.7^L
38527 
38528 
38529      Meaning:  There  are no more  free entries available  in the
38530                system  trailer  segment,  str_seg.   This  may be
38531                indicative of software- or hardware-induced damage
38532                to the SST  or str_seg, or may be  indicative of a
38533                number of logged-in processes  which is vastly too
38534                large.   A  more  likely  cause  is insufficiently
38535                large  str_seg.  The  size of  the str_seg  can be
38536                changed by  the TBLS STR card in  the config deck.
38537                This indicates a logic error in the supervisor, or
38538                CPU or  memory hardware problems.   BOS Typewriter
38539                (Crashes system)es
38540 
38541      Action:   Follow  normal  recovery  procedures.   It  may be
38542                necessary to  increase the size of  the str_seg by
38543                the TBLS STR card in  the config deck.  Be sure to
38544                get a dump.
38545 
38546 
38547 
38548                [segment_loader.pl1]
38549                segment_loader:  bad header size:  SSS
38550 
38551 
38552      Stream:   BOS Typewriter (Crashes system)
38553 
38554      Time:     System Intialization.
38555 
38556      Meaning:  A bad segment header was found in the mst source.
38557 
38558      Action:   Follow normal recovery procedures.  $boot_tape
38559 
38560 
38561 
38562                [segment_loader.pl1]
38563                segment_loader:              error            from
38564                slt_manager$build_entry
38565 
38566 
38567      Stream:   BOS Typewriter (Crashes system)
38568 
38569      Time:     System Intialization.
38570 
38571      Meaning:  This indicates a logic error in the supervisor, or
38572                CPU or memory hardware problems.
38573 
38574      Action:   Follow normal recovery procedures.  $boot_tape
38575 
38576 
38577 
38578                [segment_loader.pl1]
38579                segment_loader:  Missing linkage or defs.
38580 
38581 
38582 
38583 
38584 segment_loader                 666            08/03/23     MR12.7^L
38585 
38586 
38587      Stream:   BOS Typewriter (Crashes system)
38588 
38589      Time:     System Intialization.
38590 
38591      Meaning:  A linkage  or definitions section which  should be
38592                in the mst source appears to be missing.
38593 
38594      Action:   Follow normal recovery procedures.  $boot_tape
38595 
38596 
38597 
38598                [segment_loader.pl1]
38599                segment_loader:  unexpected control type:  TTT
38600 
38601 
38602      Stream:   BOS Typewriter (Crashes system)
38603 
38604      Time:     System Intialization.
38605 
38606      Meaning:  A segment  control word was found  out of sequence
38607                in the mst source.
38608 
38609      Action:   Follow normal recovery procedures.  $boot_tape
38610 
38611 
38612 
38613                [segment_loader.pl1]
38614                segment_loader:  Unexpected DEFS/LINKAGE
38615 
38616 
38617      Stream:   BOS Typewriter (Crashes system)
38618 
38619      Time:     System Intialization.
38620 
38621      Meaning:  A linkage or definitions  section was found out of
38622                sequence in the mst source.
38623 
38624      Action:   Follow normal recovery procedures.  $boot_tape
38625 
38626 
38627 
38628                [segment_loader.pl1]
38629                segment_loader:  unknown control type TTT
38630 
38631 
38632      Stream:   BOS Typewriter (Crashes system)
38633 
38634      Time:     System Intialization.
38635 
38636      Meaning:  A bad  segment control word  was found in  the mst
38637                source.
38638 
38639      Action:   Follow normal recovery procedures.  $boot_tape
38640 
38641 
38642 segment_loader                 667            08/03/23     MR12.7^L
38643 
38644 
38645 
38646 
38647                [segment_mover.pl1]
38648                segment_mover:   critical segment  out of  disk on
38649                DRIVENAME, segno/astep = sss/aaa
38650 
38651 
38652      Stream:   BOS Typewriter.
38653 
38654      Time:     While system is running.
38655 
38656      Meaning:  There  are  no  more  free  pages  on the physical
38657                volume  where a  critical segment  resides, and an
38658                extra  page can  not  be  found for  that segment.
38659                Such a  critical segment may be  a physical buffer
38660                segment for a peripheral  device attached via IOI.
38661                The   user  process  receives   a  seg_fault_error
38662                signal.
38663 
38664      Action:   The logical volume containing the pack residing on
38665                DRIVENAME may be too full, or may need rebalancing
38666                with  the  sweep_pv   tool.   Contact  the  system
38667                programming staff._sa
38668 
38669 
38670 
38671                [segment_mover.pl1]
38672                segment_mover:  Failed to  seg move UUU(ENTRYNAME)
38673                from DRIVENAME1 to DRIVENAME2 for USERNAME
38674 
38675 
38676      Stream:   Logged in SYSERR log.
38677 
38678      Time:     While system is running.
38679 
38680      Meaning:  The system could not  perform a cross-pack segment
38681                move  because no  pack in  the logical  volume had
38682                enough  space to  hold the  segment.  UUUU  is the
38683                unique  ID  of  the  segment,  and  ENTRYNAME  its
38684                primary name.
38685 
38686      Action:   If  this  message  persists,  the  logical  volume
38687                containing the  packs on the drives  noted is near
38688                full.    In   this   case,   contact   the  system
38689                administrator.
38690 
38691 
38692 
38693                [segment_mover.pl1]
38694                segment_mover:   finishing truncation of  pvtx PPP
38695                vtocx VVV
38696 
38697 
38698 
38699 
38700 segment_mover                  668            08/03/23     MR12.7^L
38701 
38702 
38703      Stream:   BOS Typewriter.
38704 
38705      Time:     While system is running.
38706 
38707      Meaning:  The segment mover  encountered an unexpected error
38708                in  truncating either  the old  copy of  a segment
38709                being moved cross-packs or in a new copy which was
38710                aborted for lack of space.  This may be a physical
38711                device  error, or  may  be  indicative of  a logic
38712                problem in  the supervisor, or may  be symptomatic
38713                of main memory or CPU problems.
38714 
38715      Action:   Contact the system programming staff.
38716 
38717 
38718                [segment_mover.pl1]
38719                segment_mover:  freeing vtocx VVV on new pvtx PPP.
38720                ERRORMESSAGE
38721 
38722 
38723      Stream:   BOS Typewriter.
38724 
38725      Time:     While system is running.
38726 
38727      Meaning:  The segment mover  encountered an unexpected error
38728                in freeing the VTOC entry of a segment being moved
38729                on a  volume to which an abortive  attempt to move
38730                the  segment was  made.   This  may be  a physical
38731                device error.
38732 
38733      Action:   Contact the system programming staff.
38734 
38735 
38736                [segment_mover.pl1]
38737                segment_mover:  freeing vtocx VVV  on old pvtx PPP
38738                ERRORMESSAGE
38739 
38740 
38741      Stream:   BOS Typewriter.
38742 
38743      Time:     While system is running.
38744 
38745      Meaning:  During  a  cross-pack  segment  move,  the  system
38746                encountered  an unexpected   error in  freeing the
38747                VTOC entry of the segment on the old pack This may
38748                be a  physical device error, or  may be indicative
38749                of  a logic  problem  in  the supervisor,  or main
38750                memory or CPU problems.
38751 
38752      Action:   Contact the system programming staff.
38753 
38754 
38755                [segment_mover.pl1]
38756 
38757 
38758 segment_mover                  669            08/03/23     MR12.7^L
38759 
38760 
38761                segment_mover:   get_pvtx  (PPP)  fails  under ast
38762                lock
38763 
38764 
38765      Stream:   BOS Typewriter (Crashes system)
38766 
38767      Time:     While system is running.
38768 
38769      Meaning:  The  segment mover  found that  a physical  volume
38770                appears  to have  been demounted  during the  time
38771                that the segment mover  has had the active segment
38772                table locked.This  indicates a logic error  in the
38773                supervisor, or CPU or memory hardware problems.
38774 
38775      Action:   Follow normal recovery procedures.
38776 
38777 
38778                [segment_mover.pl1]
38779                segment_mover:     Moved   UUUU(ENTRYNAME)    from
38780                DRIVENAME1 to DRIVENAME2 for USERNAME
38781 
38782 
38783      Stream:   Logged in SYSERR log.
38784 
38785      Time:     While system is running.
38786 
38787      Meaning:  The system  has successfully moved a  segment from
38788                the pack on DRIVENAME1  to the pack on DRIVENAME2,
38789                on a request for a new  page on behalf of the user
38790                whose process  group ID is USERNAME.   UUUU is the
38791                unique  ID  of  the  segment,  and  ENTRYNAME  its
38792                primary name.
38793 
38794      Action:   If  a large  number of  these messages  occur, the
38795                logical volume  containing the packs  specified by
38796                the  drive  names  may  be  nearly  full or poorly
38797                balanced.  If these  messages persist, contact the
38798                system administrator.
38799 
38800 
38801 
38802                [segment_mover.pl1]
38803                segment_mover:   Moving  QUOTA-TYPE  quota account
38804                from pvtx PPP, vtocx VVV ERRORMESSAGE
38805 
38806 
38807 
38808      Stream:   Logged in SYSERR log.
38809 
38810      Time:     While system is running.
38811 
38812      Meaning:  An  error   code  was  returned  from   the  entry
38813                vtoc_attributes$get_quota  when attempting  to get
38814 
38815 
38816 segment_mover                  670            08/03/23     MR12.7^L
38817 
38818 
38819                terminal  quota  information  from  the  old vtoce
38820                before  new vtoce  is created.   In this  case the
38821                terminal  quota  attributes  for  this  QUOTA-TYPE
38822                (either  segment or   directory) quota  account is
38823                lost.
38824 
38825      Action:   If this occurs, the  quota account for the segment
38826                that has been moved  must be corrected manually by
38827                the System  Administrator or other  qualified site
38828                personell.
38829 
38830 
38831 
38832                [segment_mover.pl1]
38833                segment_mover:  threading error
38834 
38835 
38836      Stream:   BOS Typewriter (Crashes system)
38837 
38838      Time:     While system is running.
38839 
38840      Meaning:  The  segment mover  encountered bad  threads while
38841                rethreading  the  old  or  new  AST  entries  of a
38842                segment  involved in   a cross-pack  segment move.
38843                This indicates a logic error in the supervisor, or
38844                CPU or memory hardware problems.
38845 
38846      Action:   Follow normal recovery procedures.
38847 
38848 
38849                [segment_mover.pl1]
38850                segment_mover:  unexpected segfault
38851 
38852 
38853      Stream:   BOS Typewriter (Crashes system)
38854 
38855      Time:     While system is running.
38856 
38857      Meaning:  A  segment  fault  occured  during  the cross-pack
38858                moving  of a segment,  but this segment  fault was
38859                not on the segment on  which the segment mover was
38860                expecting one.This indicates a  logic error in the
38861                supervisor, or CPU or memory hardware problems.
38862 
38863      Action:   Follow normal  recovery procedures.  There  may be
38864                inconsistencies in the  physical volumes involved.
38865                These  can  be  corrected  by  a  physical  volume
38866                salvage.
38867 
38868 
38869 
38870                [set_procs_required.pl1]
38871 
38872 
38873 
38874 set_procs_required             671            08/03/23     MR12.7^L
38875 
38876 
38877                set_procs_required:  Changing  system default CPUs
38878                required from XXXX to YYYY for PERSON.PROJECT.TAG
38879 
38880 
38881      Stream:   BOS Typewriter.
38882 
38883      Time:     While system is running.
38884 
38885      Meaning:  The default set of CPUs has been changed from XXXX
38886                (CPU    tags)    to    YYYY    (CPU    tags)    by
38887                PERSON.PROJECT.TAG.   These are  the only  CPUs on
38888                which processes will run  which have not requested
38889                to be run on specific CPUs.
38890 
38891      Action:   No operator action is required.
38892 
38893 
38894                [set_procs_required.pl1]
38895                set_procs_required:   Failed to  check access  for
38896                USER.
38897 
38898 
38899      Stream:   Logged in SYSERR log.
38900 
38901      Time:     While system is running.
38902 
38903      Meaning:  Access   on   >sc1>admin_acs>set_proc_required.acs
38904                could not be checked.
38905 
38906      Action:   Verify that the ACS seg exists.
38907 
38908 
38909                [setfaults.pl1]
38910                setfaults:  deleted trailer
38911 
38912 
38913      Stream:   BOS Typewriter (Crashes system)
38914 
38915      Time:     While system is running.
38916 
38917      Meaning:  A trailer entry (record  of a process's connection
38918                to  a  segment)  for  some  segment  was marked as
38919                free.This   indicates  a    logic  error   in  the
38920                supervisor, or CPU or memory hardware problems.
38921 
38922 
38923      Action:   Follow  normal recovery  procedures.  Contact  the
38924                system programming staff.
38925 
38926 
38927 
38928                [setfaults.pl1]
38929                setfaults:  illegal cache access trailer
38930 
38931 
38932 setfaults                      672            08/03/23     MR12.7^L
38933 
38934 
38935      Stream:   BOS Typewriter (Crashes system)
38936 
38937      Time:     While system is running.
38938 
38939      Meaning:  It was found that no record of processes connected
38940                to   a  segment    (trailers)  existed   when  the
38941                encacheability  state  of  a  segment  had  to  be
38942                changed.  Such change can  only occur if processes
38943                are  connected  to  the  segment.This  indicates a
38944                logic  error in the  supervisor, or CPU  or memory
38945                hardware problems.
38946 
38947      Action:   Be  sure  to  get  a  dump.Follow  normal recovery
38948                procedures.  Contact the system programming staff.
38949 
38950 
38951 
38952                [setfaults.pl1]
38953                setfaults:  illegal trailer
38954 
38955 
38956      Stream:   BOS Typewriter (Crashes system)
38957 
38958      Time:     While system is running.
38959 
38960      Meaning:  A trailer entry (record  of a process's connection
38961                to a segment) for  some segment specifies a second
38962                segment as the descriptor segment for some process
38963                connected to that segment, but that second segment
38964                does  not have  certain bits  on in  its AST entry
38965                which would be on in the AST entry of a descriptor
38966                segment.   This  indicates  a  logic  error in the
38967                supervisor, or CPU or memory hardware problems.
38968 
38969      Action:   Follow  normal recovery  procedures.  Contact  the
38970                system programming staff.
38971 
38972 
38973 
38974                [setfaults.pl1]
38975                setfaults:  missing trailer
38976 
38977 
38978      Stream:   BOS Typewriter (Crashes system)
38979 
38980      Time:     While system is running.
38981 
38982      Meaning:  Upon terminating  a segment, it was  found that no
38983                record of the process's connection to that segment
38984                (trailer)  existed, even  though an  SDW for  that
38985                segment  appeared  in   the  process's  descriptor
38986                segment (i.e.,  the process was connected  to it).
38987 
38988 
38989 
38990 setfaults                      673            08/03/23     MR12.7^L
38991 
38992 
38993                This indicates a logic error in the supervisor, or
38994                CPU or memory hardware problems.
38995 
38996      Action:   Follow  normal recovery  procedures.  Contact  the
38997                system programming staff.
38998 
38999 
39000 
39001                [wired_shutdown.pl1]
39002                shutdown complete
39003 
39004 
39005      Stream:   BOS Typewriter.
39006 
39007      Time:     Emergency shutdown
39008 
39009      Meaning:  Emergency shutdown  is complete; this  message was
39010                preceded  by  either  "esd  before  fs enabled" or
39011                "system already shut down":  no ESD was necessary.
39012 
39013      Action:   Reboot the system.
39014 
39015 
39016                [shutdown_file_system.pl1]
39017                shutdown complete
39018 
39019 
39020      Stream:   BOS Typewriter.
39021 
39022      Time:     System shutdown
39023 
39024      Meaning:  System   shutdown,  emergency   or  regular,   has
39025                completed successfully.  The system will return to
39026                bce.  If  any problem arises such  that the system
39027                does not return to  bce, or other error condition,
39028                the storage system will  probably not be affected.
39029                If such problem arises,  attempt ESD.  The message
39030                "system  already  shut  down"  will  be printed if
39031                there is no problem.  When the "shutdown complete"
39032                message  is  issued,  there  is  no  more  Multics
39033                information in main memory.
39034 
39035 
39036 
39037                [shutdown_file_system.pl1]
39038                shutdown complete except for devices suspended.
39039 
39040 
39041      Stream:   BOS Typewriter (sounds beeper)
39042 
39043      Time:     System shutdown
39044 
39045 
39046 
39047 
39048 shutdown                       674            08/03/23     MR12.7^L
39049 
39050 
39051      Meaning:  Some disks could not be  shut down due to hardware
39052                problems.   Messages   have  occurred  identifying
39053                these drives  and the problems.  All  other drives
39054                have  been shut  down- their  contents are  not in
39055                main memory or on the  paging device.  The RPV has
39056                not been shut down either, so that the system will
39057                perform some salvaging when it comes up.
39058 
39059      Action:   Attempt to ready those  drives that are not ready.
39060                When this has been done, retry ESD.  If the drives
39061                have been made accessible, ESD will succeed with a
39062                normal  "shutdown  complete"   message.   If  they
39063                cannot be  made ready, the paging  device (if any)
39064                is   unflushed.   See   the  description   of  the
39065                "warning:  paging device unflushed" message.
39066 
39067 
39068 
39069                [shutdown.pl1]
39070                shutdown:   Cannot run  on CPU  X (bootload  CPU).
39071                Dump and try ESD.  ERRORMESSAGE
39072 
39073 
39074      Stream:   BOS Typewriter (Crashes system)
39075 
39076      Time:     System shutdown
39077 
39078      Meaning:  During  an attempt  to shut  down the  system, the
39079                system  could not run  on the bootload  CPU.  This
39080                problem  may  be  due   to  hardware  or  software
39081                problems.  The system will attempt to crash, which
39082                it may not complete.
39083 
39084      Action:   If  the system  does not  complete its  attempt to
39085                crash, it  should be crashed manually.   It may be
39086                necessary  to change   the bootload  CPU manually.
39087                This  can be  done by  putting all  CPUs into STEP
39088                mode, manually assigning an  interrupt mask to the
39089                new bootload CPU from the bootload SCU maintenance
39090                panel,  taking only  the new  bootload CPU  out of
39091                STEP mode,  and doing an EXECUTE  SWITCHES on that
39092                CPU.  Once the system has crashed successfully, an
39093                ESD  should be  attempted.  This  will most likely
39094                succeed.
39095 
39096 
39097 
39098                [shutdown.pl1]
39099                shutdown:    Condition   CCCC   signalled   during
39100                shutdown.   Normal shutdown  failed.  Get  a dump,
39101                and try an ESD.
39102 
39103 
39104 
39105 
39106 shutdown                       675            08/03/23     MR12.7^L
39107 
39108 
39109      Stream:   BOS Typewriter (Crashes system)
39110 
39111      Time:     System shutdown
39112 
39113      Meaning:  During  the attempt  to shut  down the  system, an
39114                unexpected condition has been signalled.  This may
39115                result from hardware problems, or a logic error in
39116                the supervisor.  The system crashes and returns to
39117                BCE, whereupon an ESD should be attempted in order
39118                to finish  flushing Multics information  from main
39119                memory.     Because   of    the   difference    in
39120                implementation between normal shutdown and ESD, it
39121                is possible  that ESD will not  encounter the same
39122                problem, and instead be successful.
39123 
39124 
39125 
39126                [shutdown.pl1]
39127                shutdown:  Could not stop CPU TAG.
39128 
39129 
39130      Stream:   BOS Typewriter.
39131 
39132      Time:     System shutdown.
39133 
39134      Meaning:  Shutdown  stops all   but the  bootload processor.
39135                The CPU whose tag is TAG could not be stopped.
39136 
39137      Action:   Note  for system  programmer action.   If shutdown
39138                fails,  put  all  CPU's  other  than  the bootload
39139                processor  in step,  return to  BCE manually,  and
39140                attempt an ESD.
39141 
39142 
39143 
39144                [shutdown_file_system.pl1]
39145                shutdown_file_system:  Error  deactivating.  Quota
39146                may be bad.
39147 
39148 
39149      Stream:   BOS Typewriter.
39150 
39151      Time:     System shutdown
39152 
39153      Meaning:  The attempt to deactivate all segments in the file
39154                system  by a  tree-walk of  threaded ASTEs failed,
39155                likely due  to inconsistent threading in  the SST.
39156                The segments will be  deactivated by a linear walk
39157                of   the  SST.    Quota  inconsistencies   may  be
39158                introduced by  this.  These can be  corrected by a
39159                quota salvage of the hierarchy.
39160 
39161 
39162 
39163 
39164 shutdown_file_system           676            08/03/23     MR12.7^L
39165 
39166 
39167      Action:   At a  convenient time, run a quota  salvage of the
39168                hierarchy.
39169 
39170 
39171                [shutdown_file_system.pl1]
39172                shutdown_file_system:   from  demount_pv  on  PVTX
39173                ERROR_MESSAGE
39174 
39175 
39176      Stream:   BOS Typewriter.
39177 
39178      Time:     System shutdown
39179 
39180      Meaning:  A  problem was  encountered in  shutting down  the
39181                disk whose PVT index  is PVTX.  Most likely, other
39182                messages  identifying  the   pack,  drive,  and/or
39183                problem have preceded this message.
39184 
39185      Action:   Note  for  system  programmer  action.   If  other
39186                messages have preceded this message, take remedial
39187                action  as necessary.  Attempt  emergency shutdown
39188                after readying appropriate disk drives, if this is
39189                the problem.
39190 
39191 
39192 
39193                [shutdown_file_system.pl1]
39194                shutdown_file_system:  NN locks set
39195 
39196 
39197      Stream:   BOS Typewriter.
39198 
39199      Time:     System shutdown
39200 
39201      Meaning:  Not  all  data  base   and  directory  locks  were
39202                unlocked  by the  system before  shutdown started.
39203                During emergency shutdown, this is to be expected.
39204                During normal shutdown, this may be symptomatic of
39205                software problems.
39206 
39207      Action:   If  this message   occurs during  normal shutdown,
39208                note for system programming staff.
39209 
39210 
39211 
39212                [start_cpu.pl1]
39213                start_cpu:  Added CPU CPUTAG
39214 
39215 
39216      Stream:   BOS Typewriter.
39217 
39218      Time:     In  response to an  operator "rcf add  cpu CPUTAG"
39219                command, or at bootload time.
39220 
39221 
39222 start_cpu                      677            08/03/23     MR12.7^L
39223 
39224 
39225      Meaning:  The  system has  successfully added  the CPU whose
39226                tag is CPUTAG to the configuration.
39227 
39228      Action:   No operator action is required.
39229 
39230 
39231                [start_cpu.pl1]
39232                start_cpu:    CPU   CPUTAG   data   switches   are
39233                XXXXXXXXXXXX, should be YYYYYYYYYYYY
39234 
39235 
39236      Stream:   BOS Typewriter.
39237 
39238      Time:     In response to an "rcf add cpu CPUTAG" command
39239 
39240      Meaning:  The data switches on the CPU indicated are not set
39241                properly.  The proper value is given.
39242 
39243      Action:   The incorrect value will  prevent returning to BCE
39244                on that CPU by means of EXECUTE SWITCHES.  Certain
39245                incorrect values will  activate software debugging
39246                traps.   The switches  should be  corrected.  This
39247                can be done while the CPU is running.
39248 
39249 
39250 
39251                [start_cpu.pl1]
39252                start_cpu:  CPU  CPUTAG:  Model #:   MODEL; Serial
39253                #:  SERIAL; Ship date:  YY/MM/DD.
39254 
39255 
39256      Stream:   Logged in SYSERR log.
39257 
39258      Time:     When a DPS8  CPU, whose tag is CPUTAG  is added to
39259                the system.
39260 
39261      Meaning:  The MODEL, SERIAL and YY/MM/DD information is read
39262                from the DPS8 cpu's ID PROM.  It is intended to be
39263                used  as  historical  information  for  identifing
39264                CPUs,  regardless  of  what  their  current tag is
39265                assigned as.
39266 
39267      Action:   No operator action is required.
39268 
39269 
39270                [start_cpu.pl1]
39271                start_cpu:  Unable to run on CPU x ERRORMESSAGE
39272 
39273 
39274      Stream:   BOS Typewriter (Crashes system)
39275 
39276      Time:     In response to an "rcf  add cpu CPUTAG" command or
39277                at bootload
39278 
39279 
39280 start_cpu                      678            08/03/23     MR12.7^L
39281 
39282 
39283      Meaning:  After adding  a CPU, the system was  unable to run
39284                on that CPU.  This  indicates hardware or software
39285                failure.
39286 
39287      Action:   Follow normal recovery procedures.
39288 
39289 
39290                [page_error.alm]
39291                stock:  deposit zero address.
39292 
39293 
39294      Stream:   BOS Typewriter (Crashes system)
39295 
39296      Time:     While system is running.
39297 
39298      Meaning:  An attempt was made to deposit address zero into a
39299                record stock.  This is  an invalid address, and it
39300                indicates hardware or software failure.
39301 
39302      Action:   Follow normal recovery procedures.
39303 
39304 
39305                [stock_man.pl1]
39306                stock_man:   Attempt to   free non-empty  stock on
39307                dskX_NN:                          pvtep=XXX|XXXXXX
39308                record_stockp=YYY|YYYYYY
39309 
39310 
39311      Stream:   BOS Typewriter (Crashes system)
39312 
39313      Time:     During initialization immediately  before the File
39314                System is activated, or when demounting a physical
39315                disk volume.
39316 
39317      Meaning:  Not all free addresses  have been deposited to the
39318                Volume  Map  successfully   for  the  disk  volume
39319                indicated.   This  is  indicative  of  a  software
39320                malfunction.  The  pointers printed are  useful to
39321                site system programmers in analyzing the problem.
39322 
39323      Action:   Follow  normal  recovery   procedures.   The  free
39324                addresses  which are  lost may  be recovered  by a
39325                physical volume salvage.
39326 
39327 
39328 
39329                [stock_man.pl1]
39330                stock_man:   Attempt to   free non-empty  stock on
39331                dskX_NN:  pvtep=XXX|XXXXXX vtoce_stockp=YYY|YYYYYY
39332 
39333 
39334      Stream:   BOS Typewriter (Crashes system)
39335 
39336 
39337 
39338 stock_man                      679            08/03/23     MR12.7^L
39339 
39340 
39341      Time:     When demounting a physical disk volume.
39342 
39343      Meaning:  Not  all free  VTOCEs have  been deposited  to the
39344                VTOC   Map  successfully   for  the   disk  volume
39345                indicated.   This  is  indicative  of  a  software
39346                malfunction.  The  pointers printed are  useful to
39347                site system programmers in analyzing the problem.
39348 
39349      Action:   Follow  normal  recovery   procedures.   The  free
39350                VTOCEs  which  are  lost  may  be  recovered  by a
39351                physical volume salvage.
39352 
39353 
39354 
39355                [stock_man.pl1]
39356                stock_man:  PVTE out of synch with record stock on
39357                dskX_NN:   pvtep  =   XXX|XXXXXX  record_stockp  =
39358                YYY|YYYYYY
39359 
39360 
39361      Stream:   BOS Typewriter (Crashes system)
39362 
39363      Time:     During initialization immediately  before the File
39364                System is activated, or when demounting a physical
39365                disk volume.
39366 
39367      Meaning:  The supervisor databases pvt and stock_seg are not
39368                in  proper synchronization.  The  pointers printed
39369                are  the locations  of the  databasse elements for
39370                which  this condition   has been  detected.  These
39371                pointers are useful to the site system programmers
39372                for  analyzing the  problem, which  is probably  a
39373                software  malfunction.   dskX_NN  is  the physical
39374                volume whose tables are affected.
39375 
39376      Action:   Follow  normal  recovery   procedures.   The  free
39377                addresses  which are  lost may  be recovered  by a
39378                physical volume salvage.
39379 
39380 
39381 
39382                [stock_man.pl1]
39383                stock_man:  PVTE out of  synch with VTOCE stock on
39384                dskX_NN:    pvtep  =  XXX|XXXXXX   vtoce_stockp  =
39385                YYY|YYYYYY
39386 
39387 
39388      Stream:   BOS Typewriter (Crashes system)
39389 
39390      Time:     When demounting a physical disk volume.
39391 
39392      Meaning:  The supervisor databases pvt and stock_seg are not
39393                in  proper synchronization.  The  pointers printed
39394 
39395 
39396 stock_man                      680            08/03/23     MR12.7^L
39397 
39398 
39399                are  the locations  of the  databasse elements for
39400                which  this condition   has been  detected.  These
39401                pointers are useful to the site system programmers
39402                for  analyzing the  problem, which  is probably  a
39403                software  malfunction.   dskX_NN  is  the physical
39404                volume  whose  tables  are  affected.   Some  free
39405                VTOCEs may be lost.
39406 
39407      Action:   Follow  normal  recovery   procedures.   The  lost
39408                VTOCEs  can  be  recovered  by  a  physical volume
39409                salvage.
39410 
39411 
39412 
39413                [stop_cpu.pl1]
39414                stop_cpu:  Removed CPU CPUTAG.
39415 
39416 
39417      Stream:   BOS Typewriter.
39418 
39419      Time:     In  response to  an operator  "rcf dl  cpu CPUTAG"
39420                command.
39421 
39422      Meaning:  The system has successfully  deleted the CPU whose
39423                tag is CPUTAG from  the configuration.  The CPU is
39424                now halted at a DIS instruction.
39425 
39426      Action:   The operator can, but  need not, physically remove
39427                the  CPU  from   the  configuration  by  disabling
39428                appropriate ports if desired.
39429 
39430 
39431 
39432                [stop_cpu.pl1]
39433                stop_cpu:  Unable to run on CPU X ERRORMESSAGE
39434 
39435 
39436      Stream:   BOS Typewriter (Crashes system)
39437 
39438      Time:     When deleting a CPU.
39439 
39440      Meaning:  The system  has just deleted a CPU  which owned an
39441                interrupt mask.  In trying to assign the mask to a
39442                different CPU  (X), it was  unable to run  on that
39443                CPU.    This   indicates   hardware   or  software
39444                malfunction.
39445 
39446      Action:   Follow normal recovery procedures.
39447 
39448 
39449                [stop_cpu.pl1]
39450                stop_mpx:    CPU  CPUTAG   is  now   the  bootload
39451                processor.
39452 
39453 
39454 stop_mpx                       681            08/03/23     MR12.7^L
39455 
39456 
39457      Stream:   BOS Typewriter.
39458 
39459      Time:     In  response to  an operator  "rcf dl  cpu CPUTAG"
39460                command.
39461 
39462      Meaning:  The CPU  whose tag is CPUTAG is  now the processor
39463                on which BCE will run  at system shutdown or crash
39464                time, unless some other processor is so designated
39465                in  this way  before  the  next shutdown  or crash
39466                time.  Unless BCE is rebooted after shutdown, that
39467                CPU  will be  the bootload  processor of  the next
39468                bootload.
39469 
39470      Action:   No operator action is required.
39471 
39472 
39473                [stop_process.pl1]
39474                stop_process:  attempt to stop initializer process
39475 
39476 
39477      Stream:   BOS Typewriter (Crashes system)
39478 
39479      Time:     While system is running.
39480 
39481      Meaning:  This indicates a logic error in the supervisor, or
39482                CPU or memory hardware problems.
39483 
39484      Action:   Follow normal recovery procedures.
39485 
39486 
39487                [sum.pl1]
39488                sum:  dirmod failed to activate XXX|0
39489 
39490 
39491      Stream:   BOS Typewriter (Crashes system)
39492 
39493      Time:     While system is running.
39494 
39495      Meaning:  Directory control could  not activate a directory.
39496                This indicates a logic error in the supervisor, or
39497                CPU or  memory hardware problems.  It  is possible
39498                that the AST is damaged.
39499 
39500      Action:   Follow normal recovery procedures.
39501 
39502 
39503                [sum.pl1]
39504                sum:  mylock error on XXX|0
39505 
39506 
39507      Stream:   BOS Typewriter (Crashes system)
39508 
39509      Time:     While system is running.
39510 
39511 
39512 sum                            682            08/03/23     MR12.7^L
39513 
39514 
39515      Meaning:  A  directory which should  not be locked  is found
39516                locked.   This  indicates  a  logic  error  in the
39517                supervisor, or CPU or memory hardware problems.
39518 
39519      Action:   Follow normal recovery procedures.
39520 
39521 
39522                [sys_trouble.alm]
39523                sys_trouble:  Out-of-Segment-Bounds on prds.
39524 
39525 
39526 
39527      Stream:   BOS Typewriter (Crashes system)
39528 
39529      Time:     While system is running.
39530 
39531      Meaning:  While running with the prds as a stack, an attempt
39532                was  " made  to reference  beyond the  end of  the
39533                prds.  The likely "  cause was stack overflow, due
39534                either  to a  recursive loop  " in  the procedures
39535                running  on  the  prds  or  insufficient  "  space
39536                allocated for  the prds.  If the  latter, the size
39537                of " the prds should  be increased by means of the
39538                TBLS Configuration " Card.
39539 
39540      Action:   Follow normal recovery procedures.
39541 
39542 
39543                [sys_trouble.alm]
39544                sys_trouble:  Execute fault by operator.
39545 
39546 
39547 
39548      Stream:   BOS Typewriter (Crashes system)
39549 
39550      Time:     While system is running.
39551 
39552      Meaning:  Operator    depressed   execute    pushbutton   on
39553                processor.
39554 
39555      Action:   $recov
39556 
39557 
39558                [sys_trouble.alm]
39559                sys_trouble:  Fault in bound_interceptors.
39560 
39561 
39562 
39563      Stream:   BOS Typewriter (Crashes system)
39564 
39565      Time:     While system is running.
39566 
39567      Meaning:  A fault occured while handling another fault.
39568 
39569 
39570 sys_trouble                    683            08/03/23     MR12.7^L
39571 
39572 
39573      Action:   $recov
39574 
39575 
39576                [sys_trouble.alm]
39577                sys_trouble:  Fault in idle process.
39578 
39579 
39580 
39581      Stream:   BOS Typewriter (Crashes system)
39582 
39583      Time:     While system is running.
39584 
39585      Meaning:  This indicates a logic error in the supervisor, or
39586                CPU or memory hardware problems.
39587 
39588      Action:   $recov
39589 
39590 
39591                [sys_trouble.alm]
39592                sys_trouble:  Fault/interrupt while on prds.
39593 
39594 
39595 
39596      Stream:   BOS Typewriter (Crashes system)
39597 
39598      Time:     While system is running.
39599 
39600      Meaning:  This indicates a logic error in the supervisor, or
39601                CPU or memory hardware problems.
39602 
39603      Action:   $recov
39604 
39605 
39606                [sys_trouble.alm]
39607                sys_trouble:  Fault/interrupt with ptl set.
39608 
39609 
39610 
39611      Stream:   BOS Typewriter (Crashes system)
39612 
39613      Time:     While system is running.
39614 
39615      Meaning:  This indicates a logic error in the supervisor, or
39616                CPU or memory hardware problems.
39617 
39618      Action:   $recov
39619 
39620 
39621                [sys_trouble.alm]
39622                sys_trouble:  Interrupts Masked in User Ring.
39623 
39624 
39625 
39626 
39627 
39628 sys_trouble                    684            08/03/23     MR12.7^L
39629 
39630 
39631      Stream:   BOS Typewriter (Crashes system)
39632 
39633      Time:     While system is running.
39634 
39635      Meaning:  During processing of a  fault, it was noticed that
39636                interrupts " were masked  in user-ring, an invalid
39637                condition.  This is a  " debug trap crash, enabled
39638                by     the    hidden     tuning    parameter     "
39639                trap_invalid_masked.
39640 
39641      Action:   Contact the Multics System Development staff.
39642 
39643 
39644                [sys_trouble.alm]
39645                sys_trouble:  Page fault while on prds.
39646 
39647 
39648 
39649      Stream:   BOS Typewriter (Crashes system)
39650 
39651      Time:     While system is running.
39652 
39653      Meaning:  This indicates a logic error in the supervisor, or
39654                CPU or memory hardware problems.
39655 
39656      Action:   $recov
39657 
39658 
39659                [sys_trouble.alm]
39660                sys_trouble:  Ring 0 derail.  {MESSAGE}
39661 
39662 
39663 
39664      Stream:   BOS Typewriter (Crashes system)
39665 
39666      Time:     While system is running.
39667 
39668      Meaning:  A   supervisor  software   module  discovered   an
39669                untenable situation,  and " crashed the  system by
39670                executing  a  derail   (DRL)  instruction.   "  If
39671                MESSAGE is  also present, it will be  of the form:
39672                "module:  explanation", and further details can be
39673                found in  " this documentation in  the description
39674                of "module".
39675 
39676      Action:   $recov
39677 
39678 
39679                [sys_trouble.alm]
39680                sys_trouble:  Unexpected fault.
39681 
39682 
39683 
39684 
39685 
39686 sys_trouble                    685            08/03/23     MR12.7^L
39687 
39688 
39689      Stream:   BOS Typewriter (Crashes system)
39690 
39691      Time:     System Intialization.
39692 
39693      Meaning:  This indicates a logic error in the supervisor, or
39694                CPU or memory hardware problems.
39695 
39696      Action:   $recov
39697 
39698 
39699                [sys_trouble.alm]
39700                sys_trouble:  Unrecognized fault.
39701 
39702 
39703 
39704      Stream:   BOS Typewriter (Crashes system)
39705 
39706      Time:     While system is running.
39707 
39708      Meaning:  Unexpected or unrecognized  fault subcondition.  "
39709                Probable hardware malfunction.
39710 
39711      Action:   Contact the system programming staff.
39712 
39713 
39714                [syserr_log_man_.pl1]
39715                Syserr msg #NNNNN:  MESSAGE-TEXT
39716                Segment:  PATHNAME
39717                Volume:  VOLUME-NAME
39718 
39719 
39720 
39721      Stream:   as (severity0)
39722 
39723      Time:     While system is running.
39724 
39725      Meaning:  This  message  is  a  repetition  of  a syserr log
39726                message  which reported damage  to a segment  or a
39727                physical  volume.  There  will always  be two such
39728                messages  in  sequence,   a  "Syserr  msg.   #XXX"
39729                message  and  either  a  "Volume:"  or  "Segment:"
39730                message.   The  first  message  is  a  copy of the
39731                logged  syserr message  of the  given number;  the
39732                second  message identifies  the volume  or segment
39733                mentioned.  This allows segments damaged by system
39734                action, or  segments in which the  physical volume
39735                salvager   observed  damage,   to  be   identified
39736                unambiguously.  These  messages are logged  in the
39737                Answering Service log at answering service startup
39738                time and every accounting update.
39739 
39740      Action:   Correlate  volume salvager messages  with previous
39741                printed  volume  salvager  output  to  obtain more
39742 
39743 
39744 Syserr msg #NNNNN              686            08/03/23     MR12.7^L
39745 
39746 
39747                information about  segment damage detected  by the
39748                volume  salvager.  For   those segments  which are
39749                mentioned, which have not been deleted, or are not
39750                in  deleted  directories  (the  "Segment:" message
39751                says  if   this  is  the  case)   contact  persons
39752                responsible for the ownership of that segment, and
39753                undertake recovery procedures if needed.
39754 
39755 
39756 
39757                [syserr_real.pl1]
39758                syserr:  Bad ring 1 call.
39759 
39760 
39761      Stream:   Logged in SYSERR log.
39762 
39763      Time:     While system is running.
39764 
39765      Meaning:  A bad  call to syserr  was made from  ring 1.  The
39766                system keeps running.
39767 
39768      Action:   No operator action is required.
39769 
39770 
39771                [syserr_real.pl1]
39772                syserr:  Mylock error.
39773 
39774 
39775      Stream:   BOS Typewriter (Crashes system)
39776 
39777      Time:     While system is running.
39778 
39779      Meaning:  This indicates a logic error in the supervisor, or
39780                CPU or memory hardware problems.
39781 
39782      Action:   Follow normal recovery procedures.
39783 
39784 
39785                [alm_syserr_caller.pl1]
39786                syserr_caller$search_ast_double_uid spurious call,
39787                aste=desired,       uid=UID,       pv=DRIVE(PVID),
39788                vtocx=VTOCX.
39789 
39790 
39791      Stream:   Logged in SYSERR log.
39792 
39793      Time:     While system is running.
39794 
39795      Meaning:  A  call was made  to indicate a  double unique_id,
39796                but it was not  possible to reconstruct the error.
39797                The      unique      id,      physical      volume
39798                location/identifier, and vtoce index are provided.
39799 
39800 
39801 
39802 syserr_caller$search_ast_double_^H6u^H8i^H7d           08/03/23     MR12.7^L
39803 
39804 
39805      Action:   No operator action is required.
39806 
39807 
39808                [alm_syserr_caller.pl1]
39809                syserr_caller$search_ast_double_uid spurious call,
39810                astep=null, uid=UID, pv=DRIVE(PVID), vtocx=VTOCX.
39811 
39812 
39813      Stream:   Logged in SYSERR log.
39814 
39815      Time:     While system is running.
39816 
39817      Meaning:  A  call was made  to indicate a  double unique_id,
39818                but it was not  possible to reconstruct the error.
39819                The        unique_id,       physical        volume
39820                location/identifier, and VTOCE index are provided.
39821 
39822      Action:   No operator action is required.
39823 
39824 
39825                [syserr_copy.pl1]
39826                syserr_copy:  Cannot  add message to  paged syserr
39827                log PTR.  ERROR-MESSAGE
39828 
39829 
39830      Stream:   BOS Typewriter (Crashes system)
39831 
39832      Time:     While system is running.
39833 
39834      Meaning:  This indicates a logic error in the supervisor, or
39835                CPU  or   memory  hardware  problems.    This  may
39836                indicate  that the  syserr log  partition has been
39837                damaged.  If  this is the case,  the LOG partition
39838                should  be reinitialized  using the  BCE test_disk
39839                command.   Some  messages  will  be  lost  if this
39840                happens.
39841 
39842      Action:   Re-boot   the   system.    Reinitialize   the  LOG
39843                partition if necessary.
39844 
39845 
39846                [syserr_copy.pl1]
39847                syserr_copy:  LOG partition full.  Further copying
39848                temporarily disabled.
39849 
39850 
39851      Stream:   BOS Typewriter (Crashes system)
39852 
39853      Time:     While system is running.
39854 
39855      Meaning:  Both halves of the ring zero syserr log buffer are
39856                full.  This generally indicates that the Answering
39857                Service  is not  copying messages  from ring  zero
39858 
39859 
39860 syserr_copy                    688            08/03/23     MR12.7^L
39861 
39862 
39863                into  >sc1>syserr_log;  there  will  have  been  a
39864                previous message left in the Answering Service log
39865                describing why.
39866 
39867      Action:   If the  problem is correctable, copying  from ring
39868                zero  should be  restarted (see  the documentation
39869                for   "syserr_log_man_:   Automatic   log  copying
39870                disabled"  for instructions);  otherwise, messages
39871                will be lost.
39872 
39873 
39874 
39875                [syserr_copy.pl1]
39876                syserr_copy:  LOG partition mostly full.  Severity
39877                5 messages will be lost.
39878 
39879 
39880      Stream:   BOS Typewriter (sounds beeper)
39881 
39882      Time:     While system is running.
39883 
39884      Meaning:  Both halves of the ring zero syserr log buffer are
39885                nearly  full.  This  generally indicates  that the
39886                Answering  Service is   not copying  messages from
39887                ring  zero into  >sc1>syserr_log; there  will have
39888                been  a  previous  message  left  in the Answering
39889                Service log describing why.
39890 
39891      Action:   If the  problem is correctable, copying  from ring
39892                zero  should be  restarted (see  the documentation
39893                for   "syserr_log_man_:   Automatic   log  copying
39894                disabled"  for instructions);  otherwise, messages
39895                will be lost.
39896 
39897 
39898 
39899                [syserr_copy_wired_log.pl1]
39900                syserr_copy_wired_log:   Bad lock  WWWWWWWWWWWW at
39901                SSS|OOOOOO
39902 
39903 
39904      Stream:   BOS Typewriter (Crashes system)
39905 
39906      Time:     While system is running.
39907 
39908      Meaning:  This indicates a logic error in the supervisor, or
39909                CPU or memory hardware  problems.  The contents of
39910                the lock  word and its address are  printed, as an
39911                aid for debugging.
39912 
39913      Action:   Follow normal recovery procedures.
39914 
39915 
39916 
39917 
39918 syserr_copy_wired_log          689            08/03/23     MR12.7^L
39919 
39920 
39921                [syserr_copy_wired_log.pl1]
39922                syserr_copy_wired_log:    Fault   occurred   while
39923                copying into LOG partition.  Messages NNNN to NNNN
39924                may be lost.
39925 
39926 
39927      Stream:   BOS Typewriter (Crashes system)
39928 
39929      Time:     While system is running.
39930 
39931      Meaning:  This indicates a logic error in the supervisor, or
39932                CPU  or  memory  hardware  problems.   A fault has
39933                occurred while copying data  from the wired syserr
39934                log buffer to the  paged syserr log.  This usually
39935                results  from a disk  error on the  LOG partition,
39936                which  would also   generate disk  error messages.
39937                The sequence numbers of  the affected messages are
39938                given because those messages may not appear in the
39939                LOG partition.
39940 
39941      Action:   Follow normal recovery procedures.
39942 
39943 
39944                [syserr_copy_wired_log.pl1]
39945                syserr_copy_wired_log:    Too  many   faults,  log
39946                copying disabled.
39947 
39948 
39949      Stream:   BOS Typewriter (sounds beeper)
39950 
39951      Time:     While system is running.
39952 
39953      Meaning:  This indicates a logic error in the supervisor, or
39954                CPU  or  memory  hardware  problems.   If too many
39955                errors  occur  updating  the  LOG  partition,  log
39956                copying will be disabled, which causes all further
39957                messages  to be  printed  on  the console  but not
39958                entered in the log.
39959 
39960      Action:   Contact the system programming staff.
39961 
39962 
39963                [syserr_log_man_.pl1]
39964                syserr_log_man_:   Attempting to  swap syserr  log
39965                segments.  ERROR MESSAGE
39966 
39967 
39968      Stream:   as (severity1)
39969 
39970      Time:     System Intialization.
39971 
39972      Meaning:  This indicates a logic error in the supervisor, or
39973                CPU or memory hardware problems.
39974 
39975 
39976 syserr_log_man_                690            08/03/23     MR12.7^L
39977 
39978 
39979      Action:   Contact the system programming staff.
39980 
39981 
39982                [syserr_log_man_.pl1]
39983                syserr_log_man_:   Automatic  syserr  log  copying
39984                disabled.
39985 
39986 
39987      Stream:   as (severity1)
39988 
39989      Time:     While system is running.
39990 
39991      Meaning:  Automatic   copying   of   syserr   messages  into
39992                >sc1>syserr_log has been stopped,  due to an error
39993                in the copying process.  Another message will have
39994                been  printed prior  to this  one, describing  the
39995                problem.  An  Answering Service dump  usually will
39996                have been created, as well.
39997 
39998      Action:   If the error is recoverable (temporary disk error,
39999                record  quota overflow,   etc.-- see  the previous
40000                message(s) to make  that decision), syserr copying
40001                can be restarted by  issuing the following command
40002                in admin mode (ur using send_admin_command):
40003 
40004                     syserr_log_man_$restart_copying
40005 
40006                If the problem persists,  delete the first segment
40007                (first in  the list produced by  the list command)
40008                in >sc1>syserr_log,  and restart copying.   If the
40009                problem   still   persists,   rename   or   delete
40010                >sc1>syserr_log and reboot;  the directory will be
40011                re-created automatically.
40012 
40013                The  display_log_segment command   can be  used to
40014                examine individual log segments for damage.
40015 
40016 
40017 
40018                [syserr_log_man_.pl1]
40019                syserr_log_man_:   Bad syserr_copy_interval  value
40020                NNN seconds, using 3600 seconds instead.
40021 
40022 
40023      Stream:   as (severity1)
40024 
40025      Time:     System Intialization.
40026 
40027      Meaning:  The syserr copy  interval in installation_parms is
40028                invalid.
40029 
40030      Action:   Use   ed_installation_parms  to  correct   it.   A
40031                default will be used until then.
40032 
40033 
40034 syserr_log_man_                691            08/03/23     MR12.7^L
40035 
40036 
40037 
40038 
40039                [syserr_log_man_.pl1]
40040                syserr_log_man_:  Called too early.
40041 
40042 
40043      Stream:   as (severity2)
40044 
40045      Time:     System Intialization.
40046 
40047      Meaning:  This indicates a logic error in the supervisor, or
40048                CPU or memory hardware problems.
40049 
40050      Action:   Contact the system programming staff.
40051 
40052 
40053                [syserr_log_man_.pl1]
40054                syserr_log_man_:                           Calling
40055                hphcs_$new_syserr_reuse_log ERROR MESSAGE
40056 
40057 
40058      Stream:   as (severity1)
40059 
40060      Time:     System Intialization.
40061 
40062      Meaning:  This indicates a logic error in the supervisor, or
40063                CPU or memory hardware problems.
40064 
40065      Action:   Contact the system programming staff.
40066 
40067 
40068                [syserr_log_man_.pl1]
40069                syserr_log_man_:      Cannot      initiate     log
40070                LOG-PATHNAME.  ERROR MESSAGE
40071 
40072 
40073      Stream:   as (severity1)
40074 
40075      Time:     System Intialization.
40076 
40077      Meaning:  This indicates a logic error in the supervisor, or
40078                CPU or memory hardware problems.
40079 
40080      Action:   Contact the system programming staff.
40081 
40082 
40083                [syserr_log_man_.pl1]
40084                syserr_log_man_:    Cannot    open   history   log
40085                LOG-PATHNAME.  ERROR MESSAGE
40086 
40087 
40088      Stream:   as (severity1)
40089 
40090 
40091 
40092 syserr_log_man_                692            08/03/23     MR12.7^L
40093 
40094 
40095      Time:     System Intialization.
40096 
40097      Meaning:  This indicates a logic error in the supervisor, or
40098                CPU or memory hardware problems.
40099 
40100      Action:   Contact the system programming staff.
40101 
40102                Message:  syserr_log_man_:  Cannot migrate message
40103                #NNNNNNN
40104 
40105      Stream:   as (severity1)
40106 
40107      Time:     System Intialization.
40108 
40109      Meaning:  This indicates a logic error in the supervisor, or
40110                CPU or memory hardware problems.
40111 
40112      Action:   Contact the system programming staff.
40113 
40114 
40115                [syserr_log_man_.pl1]
40116                syserr_log_man_:    Cannot   rename   PATHNAME  to
40117                NEW-NAME.  ERROR MESSAGE
40118 
40119 
40120      Stream:   as (severity1)
40121 
40122      Time:     System Intialization.
40123 
40124      Meaning:  This indicates a logic error in the supervisor, or
40125                CPU or memory hardware problems.
40126 
40127      Action:   Contact the system programming staff.
40128 
40129 
40130                [syserr_log_man_.pl1]
40131                syserr_log_man_:     Cannot    replace    ACL   on
40132                >sc1>syserr_log.  ERROR MESSAGE
40133 
40134 
40135      Stream:   as (severity1)
40136 
40137      Time:     System Intialization.
40138 
40139      Meaning:  This indicates a logic error in the supervisor, or
40140                CPU or memory hardware problems.
40141 
40142      Action:   Contact the system programming staff.
40143 
40144 
40145                [syserr_log_man_.pl1]
40146                syserr_log_man_:   Cannot replace  initial ACL  on
40147                >sc1>syserr_log.  ERROR MESSAGE
40148 
40149 
40150 syserr_log_man_                693            08/03/23     MR12.7^L
40151 
40152 
40153      Stream:   as (severity1)
40154 
40155      Time:     System Intialization.
40156 
40157      Meaning:  This indicates a logic error in the supervisor, or
40158                CPU or memory hardware problems.
40159 
40160      Action:   Contact the system programming staff.
40161 
40162 
40163                [syserr_log_man_.pl1]
40164                syserr_log_man_:       Could       not      create
40165                >sc1>syserr_log.  Automatic syserr log copying not
40166                initialized.  ERROR MESSAGE
40167 
40168 
40169 
40170      Stream:   as (severity1)
40171 
40172      Time:     System Intialization.
40173 
40174      Meaning:  The  syserr  history  directory  was  found  to be
40175                missing during initialization, and a new one could
40176                not  be  created;  this  probably  indicates  file
40177                system damage.
40178 
40179      Action:   Contact the system programming staff.
40180 
40181 
40182                [syserr_log_man_.pl1]
40183                syserr_log_man_:  Could not  create event channel.
40184                Automatic  syserr  log  copying  not  initialized.
40185                ERROR MESSAGE
40186 
40187 
40188 
40189      Stream:   as (severity1)
40190 
40191      Time:     System Intialization.
40192 
40193      Meaning:  This indicates a logic error in the supervisor, or
40194                CPU or memory hardware problems.
40195 
40196      Action:   Contact the system programming staff.
40197 
40198 
40199                [syserr_log_man_.pl1]
40200                syserr_log_man_:  Could not use old syserr history
40201                dir:  >sc1>syserr_log ERROR MESSAGE
40202 
40203 
40204      Stream:   as (severity1)
40205 
40206 
40207 
40208 syserr_log_man_                694            08/03/23     MR12.7^L
40209 
40210 
40211      Time:     System Intialization.
40212 
40213      Meaning:  The syserr log history directory (>sc1>syserr_log)
40214                cannot  be used;  the reason  is indicated  by the
40215                error message.  The system  will attempt to rename
40216                it and create a new one; any existing log segments
40217                may be  moved from the old directory  into the new
40218                (current)  one once  the  system  comes up  if the
40219                renaming is successful.
40220 
40221      Action:   Contact   the  system   programming  staff.    The
40222                condition causing  the error should  be corrected,
40223                and the system re-booted.
40224 
40225 
40226 
40227                [syserr_log_man_.pl1]
40228                syserr_log_man_:  Created >sc1>syserr_log
40229 
40230 
40231      Stream:   as (severity0)
40232 
40233      Time:     System Intialization.
40234 
40235      Meaning:  The syserr history directory, >sc1>syserr_log, was
40236                created  automatically when  it was  found missing
40237                during  initialization.  This  is normal  during a
40238                cold boot, but an error  at all other times, since
40239                it indicates that the directory was missing.
40240 
40241      Action:   Contact the system programming staff.
40242 
40243 
40244                [syserr_log_man_.pl1]
40245                syserr_log_man_:    Error  obtaining   syserr  log
40246                history.  MESSAGE
40247 
40248 
40249      Stream:   as (severity2)
40250 
40251      Time:     System Intialization.
40252 
40253      Meaning:  To  verify syserr   message sequence  numbers will
40254                continue to  increase despite clearing of  the log
40255                partition,  the AS must  look at the  existing log
40256                segments.   However,  some  inconsistancy  in  the
40257                first    history    directory    prevented   this.
40258                (>sc1>syserr_log).
40259 
40260      Action:   Fix   any   problems   and   issue   the   command
40261                "syserr_log_man_$restart_copying" from  admin mode
40262                in the initializer process.
40263 
40264 
40265 
40266 syserr_log_man_                695            08/03/23     MR12.7^L
40267 
40268 
40269 
40270 
40271                [syserr_log_man_.pl1]
40272                syserr_log_man_:   Error  verifying  log partition
40273                sequence numbers.
40274 
40275 
40276      Stream:   as (severity2)
40277 
40278      Time:     System Intialization.
40279 
40280      Meaning:  This indicates a logic error in the supervisor, or
40281                CPU  or memory  hardware problems.   There is some
40282                error   in  the   log  partition   which  prevents
40283                adjustment of the sequence numbers.
40284 
40285      Action:   Contact the system programming staff.
40286 
40287 
40288                [syserr_log_man_.pl1]
40289                syserr_log_man_:    Renamed   >sc1>syserr_log   to
40290                NEW-NAME
40291 
40292 
40293      Stream:   as (severity1)
40294 
40295      Time:     System Intialization.
40296 
40297      Meaning:  Indicates  that  the  history  directory  has been
40298                renamed  after an error  in attempting to  use it.
40299                Old log segments can be  moved from here back into
40300                >sc1>syserr_log.
40301 
40302      Action:   Contact the system programming staff.
40303 
40304 
40305                [syserr_log_man_.pl1]
40306                syserr_log_man_:   Syserr  thresholds:   NNN pages
40307                (COMMENT), NNN seconds (COMMENT)
40308 
40309 
40310      Stream:   as (severity0)
40311 
40312      Time:     System Intialization.
40313 
40314      Meaning:  These  are  the   thresholds  for  when  Answering
40315                Service  syserr copying  will be  performed.  Each
40316                value  may be followed  by a comment;  the comment
40317                "(default)" indicates  that the installation_parms
40318                value was zero, indicating that a default value is
40319                used.  The comment "(disabled)" indicates that the
40320                installation_parms value  was set to  disable this
40321                log     copying     mechanism.      The    comment
40322 
40323 
40324 syserr_log_man_                696            08/03/23     MR12.7^L
40325 
40326 
40327                "(installation_parms  value  invalid)"  means just
40328                that;  the  value  in  installation_parms  must be
40329                updated, and meantime, a default is applied.
40330 
40331      Action:   Note for system programmer action.
40332 
40333 
40334                [syserr_log_man_.pl1]
40335                syserr_log_man_:   Unable to   open syserr  log in
40336                PATH.
40337 
40338 
40339      Stream:   as (severity2)
40340 
40341      Time:     System Intialization.
40342 
40343      Meaning:  To  verify syserr   message sequence  numbers will
40344                continue to  increase despite clearing of  the log
40345                partition,  the AS must  look at the  existing log
40346                segments.   However,  some  inconsistancy  in  the
40347                first    history    directory    prevented   this.
40348                (>sc1>syserr_log).
40349 
40350      Action:   Contact  the system   programming staff.   Fix any
40351                problems in  the syserr log history  dir and issue
40352                the command "syserr_log_man_$restart_copying" from
40353                admin mode in the initializer process.
40354 
40355 
40356 
40357                [syserr_seg_manager.pl1]
40358                syserr_seg_manager:  Attempt to rename invalid log
40359                index NNNN
40360 
40361 
40362      Stream:   BOS Typewriter (Crashes system)
40363 
40364      Time:     While system is running.
40365 
40366      Meaning:  This indicates a logic error in the supervisor, or
40367                CPU or memory hardware problems.
40368 
40369      Action:   Follow  normal recovery  procedures.  Reinitialize
40370                the LOG  partition with the BCE  test_disk command
40371                if this persists
40372 
40373 
40374 
40375                [syserr_seg_manager.pl1]
40376                syserr_seg_manager:   Attempt to rename  log #NNNN
40377                already named NAME
40378 
40379 
40380 
40381 
40382 syserr_seg_manager             697            08/03/23     MR12.7^L
40383 
40384 
40385      Stream:   BOS Typewriter.
40386 
40387      Time:     While system is running.
40388 
40389      Meaning:  This indicates a logic error in the supervisor, or
40390                CPU or memory hardware problems.
40391 
40392      Action:   Note for system programmer action.
40393 
40394 
40395                [syserr_seg_manager.pl1]
40396                syserr_seg_manager:   Cannot   rename  syserr  log
40397                #NNNN from OLD-NAME to NEW-NAME for USER-NAME
40398 
40399 
40400      Stream:   BOS Typewriter.
40401 
40402      Time:     While system is running.
40403 
40404      Meaning:  This indicates a logic error in the supervisor, or
40405                CPU or memory hardware problems.
40406 
40407      Action:   Note for system programmer action.
40408 
40409 
40410                [syserr_seg_manager.pl1]
40411                syserr_seg_manager:   Crawlout   with  syserr  log
40412                locked.  Automatic syserr log copying disabled.
40413 
40414 
40415      Stream:   BOS Typewriter (sounds beeper)
40416 
40417      Time:     While system is running.
40418 
40419      Meaning:  An  fault has  occurred in  the Answering  Service
40420                while copying syserr messages  from ring zero, and
40421                copying  from ring  zero has  been disabled.  This
40422                probably indicates a supervisor logic error.  This
40423                will  be followed  by a  message from  verify_lock
40424                identifying the fault.
40425 
40426      Action:   Attempt to restart copying, or re-boot the system.
40427 
40428 
40429                [syserr_seg_manager.pl1]
40430                syserr_seg_manager:   No messages  in live  syserr
40431                log PTR.
40432 
40433 
40434      Stream:   BOS Typewriter (Crashes system)
40435 
40436      Time:     System Intialization.
40437 
40438 
40439 
40440 syserr_seg_manager             698            08/03/23     MR12.7^L
40441 
40442 
40443      Meaning:  This indicates a logic error in the supervisor, or
40444                CPU or memory  hardware problems.  When attempting
40445                to verify the message sequence numbers in the live
40446                syserr  log, it  was found  that no  messages were
40447                present.   This  should  not  hapen  at this point
40448                because       syserr      log       initialization
40449                (init_syserr_log) always  places a message  in the
40450                log.
40451 
40452      Action:   Contact the system programming staff.
40453 
40454                Messaage:    syserr_seg_manager:     Log   message
40455                sequence  numbers adjusted  (in PTR)  beginning at
40456                SEQUENCE.
40457 
40458      Stream:   BOS Typewriter.
40459 
40460      Time:     System Intialization.
40461 
40462      Meaning:  The  sequence numbers  in the  log partition  were
40463                found to preceed the sequence numbers found in the
40464                log history.   Thus, the numbers in  the partition
40465                (and the  wired log) were  adjusted appropriately.
40466                This  message indicates   the new  sequence number
40467                where the  adjustment started for each  of the two
40468                ring 0 paged logs.  (This will occur after the log
40469                partition has been damaged or manually cleared).
40470 
40471      Action:   Contact the system programming staff.
40472 
40473 
40474                [wired_shutdown.pl1]
40475                system already shut down
40476 
40477 
40478      Stream:   BOS Typewriter.
40479 
40480      Time:     Emergency shutdown
40481 
40482      Meaning:  An attempt to perform  emergency shutdown was made
40483                after  a  previous  attempt,  or  normal shutdown,
40484                succeeded.  No ESD is necessary in this case.  The
40485                "shutdown complete" message follows.
40486 
40487      Action:   No operator action is required.
40488 
40489 
40490                [system_control_.pl1]
40491                system_control_:  fault during init
40492 
40493 
40494      Stream:   ring 4 system control.
40495 
40496 
40497 
40498 system_control_                699            08/03/23     MR12.7^L
40499 
40500 
40501      Time:     System Intialization.
40502 
40503      Meaning:  Some  error  condition  has  occurred unexpectedly
40504                while   starting  up    the  ring   4  initializer
40505                environment.  The system will return to bce.
40506 
40507      Action:   Contact  the  system  programming  staff.   Follow
40508                normal recovery procedures.
40509 
40510 
40511 
40512 
40513 
40514                [system_startup_.pl1]
40515                system_startup_ Renamed >XXXXX to >XXXXX.!BBB.....
40516 
40517 
40518      Stream:   BOS Typewriter.
40519 
40520      Time:     System Intialization.
40521 
40522      Meaning:  The segment  >disk_table or the directory  >lv (as
40523                specified by XXXXX in  the message) was renamed in
40524                response to the "nodt" or "nolv" option on the bce
40525                "boot" command line.
40526 
40527      Action:   No operator action is required.
40528 
40529 
40530                [system_startup_.pl1]
40531                system_startup_:  error on initializer io streams
40532 
40533 
40534      Stream:   BOS Typewriter (Crashes system)
40535 
40536      Time:     System Intialization.
40537 
40538      Meaning:  BOS Typewriter (Crashes  system)es The system will
40539                return to bce.
40540 
40541      Action:   Follow  normal recovery  procedures.  Try  another
40542                boot tape  and check that the  hardware is running
40543                correctly.
40544 
40545 
40546 
40547                [system_startup_.pl1]
40548                system_startup_:  Recursive error condition.
40549 
40550 
40551      Stream:   BOS Typewriter (Crashes system)
40552 
40553      Time:     System Intialization.
40554 
40555 
40556 system_startup_                700            08/03/23     MR12.7^L
40557 
40558 
40559      Meaning:  BOS Typewriter (Crashes  system)es The system will
40560                return to bce.
40561 
40562      Action:   Follow  normal recovery procedures.   Boot another
40563                system, and examine the dump.
40564 
40565 
40566 
40567                [system_startup_.pl1]
40568                system_startup_:  The config deck is empty.
40569 
40570 
40571      Stream:   BOS Typewriter (Crashes system)
40572 
40573      Time:     System Intialization.
40574 
40575      Meaning:  BOS Typewriter (Crashes  system)es The system will
40576                return  to  bce.   This  error  should  not occur,
40577                because  earlier  steps  in  initialization depend
40578                upon the  config deck.  If it  does, however, type
40579                GO after putting a config deck in place.
40580 
40581 
40582      Action:   Follow  normal recovery  procedures.  Use  another
40583                boot tape, or check that the hardware is operating
40584                correctly.
40585 
40586 
40587 
40588                [system_startup_.pl1]
40589                system_startup_:    The  config_deck   segment  is
40590                missing.
40591 
40592 
40593      Stream:   BOS Typewriter (Crashes system)
40594 
40595      Time:     System Intialization.
40596 
40597      Meaning:  BOS  Typewriter  (Crashes  system)es  The  segment
40598                config_deck  is missing.    This error  should not
40599                occur,  because  earlier  steps  in initialization
40600                depend upon the config deck.
40601 
40602      Action:   Follow  normal recovery  procedures.  Use  another
40603                boot tape, or check that the hardware is operating
40604                correctly.
40605 
40606 
40607 
40608                [system_startup_.pl1]
40609                system_startup_:  The  root logical volume  is not
40610                complete.  "boot  rlvs" level 2  directory salvage
40611                aborted.
40612 
40613 
40614 system_startup_                701            08/03/23     MR12.7^L
40615 
40616 
40617      Stream:   BOS Typewriter.
40618 
40619      Time:     System Intialization.
40620 
40621      Meaning:  One or  more physical volumes of  the Root Logical
40622                Volume (RLV) registered in the volume registration
40623                database  are  not  specified  on  the root config
40624                card,  and  are  therefore  not  mounted.  Level 2
40625                directory  salvage  cannot   take  place  with  an
40626                incomplete RLV.
40627 
40628      Action:   Mount the missing packs  with the add_vol command,
40629                and then use the salvage_dirs command.
40630 
40631 
40632 
40633                [system_startup_.pl1]
40634                system_startup_:  unclaimed COND
40635                (machine conditions in octal)
40636 
40637 
40638 
40639      Stream:   BOS Typewriter (sounds beeper)
40640 
40641      Time:     System Intialization.
40642 
40643      Meaning:  Some  error  condition  has  occurred unexpectedly
40644                inside   the  ring   1  environment.    Diagnostic
40645                information is typed after  this line.  The system
40646                should return to  Initializer command level, still
40647                in ring 1, and be able to continue running.
40648 
40649      Action:   Contact the system programming staff.
40650 
40651 
40652                [system_startup_.pl1]
40653                system_startup_:     unclaimed    {condition-name}
40654                condition.
40655 
40656 
40657      Stream:   BOS Typewriter (sounds beeper)
40658 
40659      Time:     System Intialization.
40660 
40661      Meaning:  An error has occurred  while executing in the ring
40662                1 Initializer environment.   The system returns to
40663                ring  1 command  level.  For  some errors  machine
40664                conditions are displayed in subsequent messages.
40665 
40666      Action:   Contact the system programming staff.
40667 
40668 
40669 
40670 
40671 
40672 system_startup_                702            08/03/23     MR12.7^L
40673 
40674 
40675 
40676 
40677                [system_startup_.pl1]
40678                system_startup_:  Will not reload
40679 
40680 
40681      Stream:   BOS Typewriter.
40682 
40683      Time:     Response to operator reload command.
40684 
40685      Meaning:  One or more volumes  cannot be mounted.  Reloading
40686                cannot  proceed.   The  system  returns  to ring 1
40687                command level.
40688 
40689      Action:   Correct the problem and try again.
40690 
40691 
40692                [system_startup_.pl1]
40693                system_startup_:   XYZ  is  not  a  legal command.
40694                Type help for a list of commands.
40695 
40696 
40697      Stream:   BOS Typewriter.
40698 
40699      Time:     System Intialization.
40700 
40701      Meaning:  The operator  has issued a  command to the  ring 1
40702                environment  that cannot  be executed.   No action
40703                was taken on the illegal command.
40704 
40705      Action:   If the command is misspelled, retype it correctly.
40706                If  the  command  is   intended  for  the  ring  4
40707                Answering Service, type  "standard" first to leave
40708                the ring 1 environment and then retype the desired
40709                command.
40710 
40711 
40712 
40713                [tape_reader.pl1]
40714                tape_reader:  bad_major_status:  SSS
40715 
40716 
40717      Stream:   BOS Typewriter (Crashes system)
40718 
40719      Time:     System Intialization.
40720 
40721      Meaning:  The bootload tape is unreadable.
40722 
40723      Action:   $boot_tape Try another tape drive.
40724 
40725 
40726 
40727 
40728 
40729 
40730 tape_reader                    703            08/03/23     MR12.7^L
40731 
40732 
40733 
40734 
40735                [tape_reader.pl1]
40736                tape_reader:  unable to read system tape
40737 
40738 
40739      Stream:   BOS Typewriter (Crashes system)
40740 
40741      Time:     System Intialization.
40742 
40743      Meaning:  The bootload tape is unreadable.
40744 
40745      Action:   $boot_tape
40746 
40747 
40748                [tc_init.pl1]
40749                tc_init:  cannot create  cpu_X.prds.  This CPU may
40750                not be added.  ERROR_MESSAGE
40751 
40752 
40753      Stream:   BOS Typewriter.
40754 
40755      Time:     System Intialization.
40756 
40757      Meaning:  A difficulty was encountered  in creating the PRDS
40758                for  a configurable  CPU.  Later  attempts to  add
40759                this CPU will fail.  It will be marked as "off" in
40760                the CONFIG deck.
40761 
40762      Action:   Contact  the system  programming staff.   When the
40763                problem has  been remedied, shut down  and reboot,
40764                and then add this CPU.
40765 
40766 
40767 
40768                [tc_init.pl1]
40769                tc_init:   Cannot  start  up  first  idle process.
40770                Check switches.
40771 
40772 
40773      Stream:   BOS Typewriter (Crashes system)
40774 
40775      Time:     System Intialization.
40776 
40777      Meaning:  The idle process for the bootload CPU could not be
40778                started.   This  may  be  an  error  in setting of
40779                configuration switches, or may  be indicative of a
40780                logic problem in the supervisor.
40781 
40782      Action:   Perform  an emergency   shutdown.  Check  all main
40783                module configuration  switches.  If a  problem was
40784                corrected,  reboot.  Otherwise,  be sure  to get a
40785                dump and contact the systems programming staff.
40786 
40787 
40788 tc_init                        704            08/03/23     MR12.7^L
40789 
40790 
40791 
40792 
40793                [tc_init.pl1]
40794                tc_init:    Could   not   delete   old   PRDSNAME.
40795                ERRORMESSAGE
40796 
40797 
40798      Stream:   BOS Typewriter.
40799 
40800      Time:     System Intialization.
40801 
40802      Meaning:  The old PRDS PRDSNAME  from the previous bootload,
40803                in >system_library_1, could  not be deleted.  When
40804                the CPU  whose tag is  part of PRDSNAME  is added,
40805                the  old PRDS  will  be  used.  ERRORMESSAGE  is a
40806                standard error_table_ message.
40807 
40808      Action:   Contact the system programming staff.
40809 
40810 
40811                [tc_init.pl1]
40812                tc_init:   Could  not  rename  prds  to  PRDSNAME.
40813                ERRORMESSAGE
40814 
40815 
40816      Stream:   BOS Typewriter.
40817 
40818      Time:     System Intialization.
40819 
40820      Meaning:  The segment "prds"  in >system_library_1 could not
40821                be renamed to PRDSNAME,  which is the correct name
40822                for   the  PRDS    for  the   bootload  processor.
40823                ERRORMESSAGE is a standard error_table_ message.
40824 
40825      Action:   Notify  the  system   programming  staff.   Action
40826                should be taken by the programming staff to rename
40827                this  segment.  If  the problem  cannot be  sorted
40828                out, avoid  reconfiguring the bootload  CPU during
40829                this bootload.
40830 
40831 
40832 
40833                [tc_init.pl1]
40834                tc_init:  Could not start CPU CPUTAG.
40835 
40836 
40837      Stream:   BOS Typewriter.
40838 
40839      Time:     System Intialization.
40840 
40841      Meaning:  The  CPU   whose  tag  is  CPUTAG   could  not  be
40842                automatically started by system bootload.
40843 
40844 
40845 
40846 tc_init                        705            08/03/23     MR12.7^L
40847 
40848 
40849      Action:   Check all  configuration switches on CPU  and main
40850                memory modules, especially the  CPU STEP switch on
40851                the  CPU which  could not  be added,  and its port
40852                enable  switches.  If  all switches  were correct,
40853                add the CPU via the addcpu command.
40854 
40855 
40856 
40857                [tc_init.pl1]
40858                tc_init:  Inconsistent SCHD config card values.
40859 
40860 
40861      Stream:   BOS Typewriter (Crashes system)
40862 
40863      Time:     System Intialization.
40864 
40865      Meaning:  The SCHD config card is not in the correct format,
40866                or  some values are  out of acceptable  range.  In
40867                particular,  the  value   of  min_eligible  cannot
40868                exceed  that of  max_eligible; also,  the value of
40869                max_eligible  plus  the   max  number  of  stopped
40870                stack_0's    (default   =    4)   cannot    exceed
40871                max_max_eligible.
40872 
40873      Action:   Check the SCHD config card  (refer to the MOH) and
40874                correct.  Re-boot the system.
40875 
40876 
40877 
40878                [tc_init.pl1]
40879                tc_init:  No valid processor tags on CPU cards.
40880 
40881 
40882      Stream:   BOS Typewriter (Crashes system)
40883 
40884      Time:     System Intialization.
40885 
40886      Meaning:  No CPU  CONFIG cards contained  valid (A -  H) CPU
40887                tags.   Normally this  message will  not appear if
40888                the bootload  CPU is mis-specified, as  this error
40889                will be  detected by scas_init, and  thus this may
40890                be indicative of a supervisor logic problem.
40891 
40892      Action:   Check that  all CPU CONFIG cards  are correct.  If
40893                not, perform an  emergency shutdown, correct them,
40894                and  reboot.  If  so, be  sure to  get a  dump and
40895                contact system programming personnel.
40896 
40897 
40898 
40899                [tc_init.pl1]
40900                tc_init:  Size of PRDS on TBLS card too small; XXX
40901                KW will be used.
40902 
40903 
40904 tc_init                        706            08/03/23     MR12.7^L
40905 
40906 
40907      Stream:   BOS Typewriter.
40908 
40909      Time:     System Intialization.
40910 
40911      Meaning:  The size of the PRDS specified on the TBLS card in
40912                the Configuration Deck is smaller than the size of
40913                the PRDS  defined in the MST header.   The size of
40914                the PRDS  will be that defined in  the MST header.
40915                Further, the  TBLS card in the  Configuration Deck
40916                has  been changed to  reflect the minimum  size of
40917                the PRDS
40918 
40919 
40920 
40921                [verify_lock.pl1]
40922                Terminating user process NAME:  Fatal salvaging of
40923                process directory.
40924 
40925 
40926      Stream:   BOS Typewriter (Terminates user process)
40927 
40928      Time:     While system is running.
40929 
40930      Meaning:  A process is attempting  to crawl out.  The system
40931                discovered that the  process was interrupted while
40932                its process directory was locked, and has salvaged
40933                the  process  directory.   Salvaging  the  process
40934                directory may delete critical process segments and
40935                cause the process to  terminate, so the process is
40936                terminated cleanly instead.
40937 
40938      Action:   No   operator   action   is   required.   Message:
40939                verify_lock:    COND  condition   by  USER   while
40940                salvaging directory.
40941 
40942      Stream:   $announce
40943 
40944      Time:     $salvt
40945 
40946      Meaning:  A fault occurred while salvaging a directory found
40947                locked  at  crawlout.   This  indicates  a serious
40948                problem with the directory.
40949 
40950      Action:   Contact the system programming staff.
40951 
40952 
40953                [truncate_vtoce.pl1]
40954                truncate_vtoce:   attempt  to  destroy  hc_sdw seg
40955                astep PPP
40956 
40957 
40958      Stream:   BOS Typewriter (Crashes system)
40959 
40960 
40961 
40962 truncate_vtoce                 707            08/03/23     MR12.7^L
40963 
40964 
40965      Time:     While system is running.
40966 
40967      Meaning:  An attempt has been  made to truncate a supervisor
40968                segment.  The  AST entry is located  at PPP.  This
40969                indicates a logic error  in the supervisor, or CPU
40970                or memory hardware problems.
40971 
40972      Action:   Follow normal recovery procedures.
40973 
40974 
40975                [tty_index.pl1]
40976                tty_index:  USER  (ACCESS_CLASS) attempted invalid
40977                attachment of CHANNEL (ACCESS_CLASS)
40978 
40979 
40980      Stream:   BOS Typewriter.
40981 
40982      Time:     While system is running.
40983 
40984      Meaning:  A    process   of    USER   (with    authorization
40985                ACCESS_CLASS)  attempted to  use a  communications
40986                channel  which does  not correspond  to the user's
40987                authorization  and  the  user  does  not  have the
40988                communications privilege enabled.  The request was
40989                refused.  This may indicate a system error.
40990 
40991      Action:   Contact the system programming staff._ssa
40992 
40993 
40994                [tty_interrupt.pl1]
40995                tty_interrupt:   unrecognized  interrupt  type (N)
40996                for devx D
40997 
40998 
40999      Stream:   BOS Typewriter (Crashes system)
41000 
41001      Time:     While system is running.
41002 
41003      Meaning:  An unrecognized  interrupt type has  been reported
41004                for the nonmultiplexed  channel whose device index
41005                is D.
41006 
41007      Action:   Contact the system programming staff.
41008 
41009 
41010                [tty_lock.pl1]
41011                tty_lock$verify:   attempted  crawlout  with queue
41012                lock set.
41013 
41014 
41015      Stream:   BOS Typewriter (Crashes system)
41016 
41017      Time:     While system is running.
41018 
41019 
41020 tty_lock$verify                708            08/03/23     MR12.7^L
41021 
41022 
41023      Meaning:  There was  an attempt to  crawl out while  the tty
41024                queue lock was locked.
41025 
41026      Action:   Contact the system programming staff.
41027 
41028 
41029                [tty_lock.pl1]
41030                tty_lock$verify:  attempted  crawlout with special
41031                channel lock set.
41032 
41033 
41034      Stream:   BOS Typewriter (Crashes system)
41035 
41036      Time:     While system is running.
41037 
41038      Meaning:  There was an attempt to  crawl out while a channel
41039                lock that is also a processor lock was locked.
41040 
41041      Action:   Contact the system programming staff.
41042 
41043 
41044                [tty_lock.pl1]
41045                tty_lock$verify:  attempted  crawlout with tty_buf
41046                lock set.
41047 
41048 
41049      Stream:   BOS Typewriter (Crashes system)
41050 
41051      Time:     While system is running.
41052 
41053      Meaning:  There  was  an  attempt  to  crawl  out  while the
41054                tty_buf lock used by tty_space_man was locked.
41055 
41056      Action:   Contact the system programming staff.
41057 
41058 
41059                [tty_lock.pl1]
41060                tty_lock:  attempt to  lock channel already locked
41061                by same process.
41062 
41063 
41064      Stream:   BOS Typewriter (Crashes system)
41065 
41066      Time:     While system is running.
41067 
41068      Meaning:  A locking error was  detected when a process tried
41069                to lock a channel that it had already locked.
41070 
41071      Action:   Contact the system programming staff.
41072 
41073 
41074                [tty_lock.pl1]
41075 
41076 
41077 
41078 tty_lock                       709            08/03/23     MR12.7^L
41079 
41080 
41081                tty_lock:   attempt  to  lock  unused  channel for
41082                interrupt.
41083 
41084 
41085      Stream:   BOS Typewriter (Crashes system)
41086 
41087      Time:     While system is running.
41088 
41089      Meaning:  A  locking error  was detected  when an  interrupt
41090                handler tried to lock an ununsed channel.
41091 
41092      Action:   Contact the system programming staff.
41093 
41094 
41095                [tty_lock.pl1]
41096                tty_lock:  attempt to unlock channel not locked by
41097                same process.
41098 
41099 
41100      Stream:   BOS Typewriter (Crashes system)
41101 
41102      Time:     While system is running.
41103 
41104      Meaning:  A locking error was  detected when a process tried
41105                to unlock a channel that  was either not locked or
41106                locked by another process.
41107 
41108      Action:   Contact the system programming staff.
41109 
41110 
41111                [tty_lock.pl1]
41112                tty_lock:  attempt  to unlock queue not  locked by
41113                same process.
41114 
41115 
41116      Stream:   BOS Typewriter (Crashes system)
41117 
41118      Time:     While system is running.
41119 
41120      Meaning:  A locking error was  detected when a process tried
41121                to unlock  the global queue lock  which was either
41122                not locked or was locked by another process.
41123 
41124 
41125 
41126                [tty_lock.pl1]
41127                tty_lock:   Cannot  get  space  for  queue  entry.
41128                (devx = N)
41129 
41130 
41131      Stream:   BOS Typewriter (sounds beeper)
41132 
41133      Time:     While system is running.
41134 
41135 
41136 tty_lock                       710            08/03/23     MR12.7^L
41137 
41138 
41139      Meaning:  An attempt  to queue an interrupt  for the channel
41140                with  devx N  failed due  to lack  of space.   The
41141                interrupt was lost which may cause loss of data or
41142                improper channel operation.
41143 
41144      Action:   Contact the system programming staff.
41145 
41146 
41147                [tty_space_man.pl1]
41148                tty_space_man:  Address not in buffer pool.
41149 
41150 
41151      Stream:   BOS Typewriter (Crashes system)
41152 
41153      Time:     While system is running.
41154 
41155      Meaning:  An attempt  was made to  free space at  an address
41156                not included in the free space pool of tty_buf.
41157 
41158      Action:   Contact the system programming staff.
41159 
41160 
41161                [tty_space_man.pl1]
41162                tty_space_man:  Lock already locked to process.
41163 
41164 
41165      Stream:   BOS Typewriter (Crashes system)
41166 
41167      Time:     While system is running.
41168 
41169      Meaning:  A process that had  the global tty_buf lock locked
41170                attempted to lock it again.
41171 
41172      Action:   Contact the system programming staff.
41173 
41174 
41175                [tty_space_man.pl1]
41176                tty_space_man:  Lock not locked to process.
41177 
41178 
41179      Stream:   BOS Typewriter (Crashes system)
41180 
41181      Time:     While system is running.
41182 
41183      Meaning:  A process  attempted to unlock the  global tty_buf
41184                lock when that process did not have it locked.
41185 
41186      Action:   Contact the system programming staff.
41187 
41188 
41189                [tty_space_man.pl1]
41190                tty_space_man:  Tried to free space already free.
41191 
41192 
41193 
41194 tty_space_man                  711            08/03/23     MR12.7^L
41195 
41196 
41197      Stream:   BOS Typewriter (Crashes system)
41198 
41199      Time:     While system is running.
41200 
41201      Meaning:  An attempt was made to  free space in tty_buf that
41202                was  included  in  or  overlapped  space  that was
41203                already free.
41204 
41205      Action:   Contact the system programming staff.
41206 
41207 
41208                [tty_tables_mgr.pl1]
41209                tty_tables_mgr$add:  Invalid table type.  N
41210 
41211 
41212      Stream:   BOS Typewriter (Crashes system)
41213 
41214      Time:     While system is running.
41215 
41216      Meaning:  An  attempt  to  add  a  table  to  the tty_tables
41217                segment has failed due to an invalid table type of
41218                N.
41219 
41220      Action:   Contact the system programming staff.
41221 
41222 
41223                [tty_tables_mgr.pl1]
41224                tty_tables_mgr$delete:  Invalid table offset.  N
41225 
41226 
41227      Stream:   BOS Typewriter (Crashes system)
41228 
41229      Time:     While system is running.
41230 
41231      Meaning:  An attempt  to delete a table  from the tty_tables
41232                segment has failed due  to an invalid table offset
41233                of N.
41234 
41235      Action:   Contact the system programming staff.
41236 
41237 
41238                [turn_on_mc_.pl1]
41239                turn_on_mc_:  MESSAGE.  attach STREAM
41240 
41241 
41242      Stream:   sc (error_output).
41243 
41244      Time:     System Intialization.
41245 
41246      Meaning:  The   system  attempted   to  start   the  Message
41247                Coordinator  but  the   stream  STREAM  cannot  be
41248                attached to  the message routing dim.   The system
41249                continues to  operate but the  Message Coordinator
41250 
41251 
41252 turn_on_mc_                    712            08/03/23     MR12.7^L
41253 
41254 
41255                is not used.  Probably,  the daemon processes will
41256                also encounter trouble.
41257 
41258      Action:   Contact the system programming staff.
41259 
41260 
41261                [turn_on_mc_.pl1]
41262                turn_on_mc_:  MESSAGE.  detach STREAM
41263 
41264 
41265      Stream:   sc (error_output).
41266 
41267      Time:     System Intialization.
41268 
41269      Meaning:  The   system  attempted   to  start   the  Message
41270                Coordinator  but the  stream STREAM  could not  be
41271                detached  from   its  initial  dim.    The  system
41272                continues to  operate but the  Message Coordinator
41273                is not used.  Probably,  the daemon processes will
41274                also encounter trouble.
41275 
41276      Action:   Contact the system programming staff.
41277 
41278 
41279                [turn_on_mc_.pl1]
41280                turn_on_mc_:  MESSAGE.  error from mc_init
41281 
41282 
41283      Stream:   sc (error_output).
41284 
41285      Time:     System Intialization.
41286 
41287      Meaning:  The   system  attempted   to  start   the  Message
41288                Coordinator  but it   cannot be  initialized.  The
41289                system  continues  to   operate  but  the  Message
41290                Coordinator  is not   used.  The  daemon processes
41291                will probably also encounter trouble.
41292 
41293      Action:   Contact the system programming staff.
41294 
41295 
41296                [turn_on_mc_.pl1]
41297                turn_on_mc_:  MESSAGE.  open STREAM
41298 
41299 
41300      Stream:   sc (error_output).
41301 
41302      Time:     System Intialization.
41303 
41304      Meaning:  The   system  attempted   to  start   the  Message
41305                Coordinator but the stream STREAM cannot be opened
41306                by the message routing  dim.  The system continues
41307                to  operate  but  the  Message  Coordinator is not
41308 
41309 
41310 turn_on_mc_                    713            08/03/23     MR12.7^L
41311 
41312 
41313                used.   Probably, the  daemon processes  will also
41314                encounter trouble.
41315 
41316      Action:   Contact the system programming staff.
41317 
41318 
41319                [mc_commands_.pl1]
41320                Unable  to  locate  a  CDT  entry  for  XXXX while
41321                attempting to drop it.
41322 
41323 
41324      Stream:   as (severity 1)
41325 
41326      Time:     In response to a drop operator command.
41327 
41328      Meaning:  Notification that the CDT entry cannot be found to
41329                free it  as a result  of dropping the  tty channel
41330                from the message coordinator.  The mc_anstbl entry
41331                is freed at this point however.
41332 
41333      Action:   No operator action is required.
41334 
41335 
41336                [obs_reconfigure.pl1]
41337                unlock:     Reconfiguration    data    locked   by
41338                PERSON.PROJ.T
41339 
41340 
41341      Stream:   Initializer process output.
41342 
41343      Time:     In response to an operator command.
41344 
41345      Meaning:  This message is  typed by reconfigure$force_unlock
41346                if the reconfiguration data base was locked.
41347 
41348      Action:   No operator action is required.
41349 
41350 
41351                [obs_reconfigure.pl1]
41352                unlock:  Reconfiguration data not locked.
41353 
41354 
41355      Stream:   Initializer process output.
41356 
41357      Time:     In response to an operator command.
41358 
41359      Meaning:  This message is  typed by reconfigure$force_unlock
41360                if the reconfiguration data base was not locked.
41361 
41362      Action:   No operator action is required.
41363 
41364 
41365 
41366 
41367 
41368 Unrecognized                   714            08/03/23     MR12.7^L
41369 
41370 
41371 
41372 
41373                [dn355_boot_interrupt.pl1]
41374                Unrecognized bootload status N for FNP X
41375 
41376 
41377      Stream:   BOS Typewriter.
41378 
41379      Time:     When bootloading an FNP
41380 
41381      Meaning:  The  status reported  by an  FNP in  response to a
41382                bootload   attempt  was   not  one   of  the  ones
41383                recognized.  N is the reported status (in octal).
41384 
41385      Action:   Contact the system programming staff.
41386 
41387 
41388                [up_mgt_.pl1]
41389                up_mgt_:    ERROR_MESSAGE    During   work   class
41390                reassignment
41391 
41392 
41393      Stream:   as (severity2)
41394 
41395      Time:     While system is running.
41396 
41397      Meaning:  The  error  described  by  ERROR_MESSAGE  occurred
41398                while  a system   administrator was  attempting to
41399                install a new mgt.   The operation was tried twice
41400                and failed both times.   More detailed reasons for
41401                the  failure  are  given  in  messages immediately
41402                preceding  this   one.   The  new  mgt   has  been
41403                installed.   Hardcore is  operating with  a set of
41404                parameters inconsistent with the new mgt.
41405 
41406      Action:   Contact the system programming staff._sa
41407 
41408 
41409                [up_pdt_.pl1]
41410                up_pdt_:  bumping NAME.PROJ, omitted from new pdt
41411 
41412 
41413      Stream:   as (severity1)
41414 
41415      Time:     While system is running.
41416 
41417      Meaning:  The  supervisor of  project PROJ  has removed  the
41418                user  named NAME  from  the  project while  he was
41419                logged  in.   He  is  no  longer  authorized to be
41420                logged in on that project and is bumped.
41421 
41422      Action:   No operator action is required.
41423 
41424 
41425 
41426 up_pdt_                        715            08/03/23     MR12.7^L
41427 
41428 
41429 
41430 
41431                [up_pdt_.pl1]
41432                up_pdt_:   bumping  NAME.PROJ,  user authorization
41433                now outside range.
41434 
41435 
41436      Stream:   as (severity1)
41437 
41438      Time:     While system is running.
41439 
41440      Meaning:  A  project administrator  has installed  a new pdt
41441                that changes the authorization  range for the user
41442                identified  by  NAME  on  project  PROJ.  The user
41443                NAME.PROJ   is  currently    logged  in   with  an
41444                authorization  outside the new  range.  Therefore,
41445                the user is being bumped from the system.
41446 
41447      Action:   No operator action is required.
41448 
41449 
41450                [up_pdt_.pl1]
41451                up_pdt_:    ERROR_MESSAGE.    PROJ.pdt   will   be
41452                installed with no hash table
41453 
41454 
41455      Stream:   as (severity2)
41456 
41457      Time:     While system is running.
41458 
41459      Meaning:  A new PDT is being installed for project PROJ.  An
41460                error  described by  ERROR_MESSAGE occurred  while
41461                its hash  table was being built.  The  PDT will be
41462                installed  without a  hash table.   Logins on that
41463                project will  take longer and place  an extra load
41464                on the system.
41465 
41466      Action:   Contact the system programming staff.
41467 
41468 
41469                [up_pdt_.pl1]
41470                up_pdt_:    PROJ.pdt   has    N   users,   leaving
41471                insufficient room for a hash table.
41472 
41473 
41474      Stream:   as (severity1)
41475 
41476      Time:     While system is running.
41477 
41478      Meaning:  A new  project definition table (PDT)  for project
41479                PROJ  is being  installed.  It  has so  many users
41480                that there is no room in it for a hash table.  The
41481                PDT  will  be  installed  without  a  hash  table.
41482 
41483 
41484 up_pdt_                        716            08/03/23     MR12.7^L
41485 
41486 
41487                Logins on that project  will take longer and place
41488                an extra load on the system.
41489 
41490      Action:   Contact the system programming staff.
41491 
41492 
41493                [up_pdt_.pl1]
41494                up_pdt_:  PROJ.pdt NAME on free list state nonzero
41495 
41496 
41497      Stream:   as (severity2)
41498 
41499      Time:     While system is running.
41500 
41501      Meaning:  A new  project definition table for  PROJ is being
41502                installed.  The thread of  free entries appears to
41503                include  some user whose  state is not  zero.  The
41504                program abandons the free chain and continues.
41505 
41506      Action:   Contact the system programming staff._sa
41507 
41508 
41509                [up_pdt_.pl1]
41510                up_pdt_:  synch error NAME.PROJ
41511 
41512 
41513      Stream:   as (severity2)
41514 
41515      Time:     While system is running.
41516 
41517      Meaning:  A new  project definition table for  PROJ is being
41518                installed.  The  answer table entry  for NAME.PROJ
41519                should contain  a pointer to the  user's PDT entry
41520                but the pointer  is incorrect.  Accounting figures
41521                may be scrambled.  The system continues operation.
41522 
41523      Action:   Contact the system programming staff._sa
41524 
41525 
41526                [up_rtdt_.pl1]
41527                up_rtdt_:   Adding resource type  RESOURCE_TYPE to
41528                the system.
41529 
41530 
41531      Stream:   as (severity1)
41532 
41533      Time:     While system is running.
41534 
41535      Meaning:  The named resource type has been newly defined and
41536                will  be accessible by  system users.  This  is an
41537                advisory message.
41538 
41539      Action:   None.
41540 
41541 
41542 up_rtdt_                       717            08/03/23     MR12.7^L
41543 
41544 
41545 
41546 
41547                [up_rtdt_.pl1]
41548                up_rtdt_:   Deleting  resource  type RESOURCE_TYPE
41549                from the system.
41550 
41551 
41552      Stream:   as (severity1)
41553 
41554      Time:     While system is running.
41555 
41556      Meaning:  The named resource type is no longer accessible by
41557                system users.  This is an advisory message.
41558 
41559      Action:   None.
41560 
41561 
41562                [up_rtdt_.pl1]
41563                up_rtdt_:    ERROR_MESSAGE   Cannot   create   RCP
41564                registry for RESOURCE_NAME.
41565 
41566 
41567      Stream:   as (severity2)
41568 
41569      Time:     While system is running.
41570 
41571      Meaning:  The  error  described  by  ERROR_MESSAGE  occurred
41572                while  a system   administrator was  attempting to
41573                install  a new  rtdt.   The  rtdt contained  a new
41574                resource   type,  but   the  resource   management
41575                registry  for  that  resource  type  could  not be
41576                created.  The  rtdt is not installed.   Some other
41577                registries   may   already   have   been  modified
41578                according to information in the new rtdt.
41579 
41580      Action:   Notify the system administrator.
41581 
41582 
41583                [up_rtdt_.pl1]
41584                up_rtdt_:    ERROR_MESSAGE   Cannot   recover   by
41585                renaming old RTDT either.
41586 
41587 
41588      Stream:   as (severity2)
41589 
41590      Time:     While system is running.
41591 
41592      Meaning:  The  program that  installs rtdt's  cannot recover
41593                correctly from  an earlier error in  renaming, for
41594                which an error message  is also printed.  Although
41595                the current rtdt is not destroyed, it is no longer
41596                accessible  to   users.   This  will   affect  the
41597                operation of resource management and RCP.
41598 
41599 
41600 up_rtdt_                       718            08/03/23     MR12.7^L
41601 
41602 
41603      Action:   Notify the system administrator.
41604 
41605 
41606                [up_rtdt_.pl1]
41607                up_rtdt_:  ERROR_MESSAGE Cannot rename new rtdt.
41608 
41609 
41610      Stream:   as (severity2)
41611 
41612      Time:     While system is running.
41613 
41614      Meaning:  The new rtdt being  installed could not be renamed
41615                to "rtdt".  The rtdt is not installed.
41616 
41617      Action:   Notify the system administrator.
41618 
41619 
41620                [up_rtdt_.pl1]
41621                up_rtdt_:  ERROR_MESSAGE Cannot rename old RTDT.
41622 
41623 
41624      Stream:   as (severity2)
41625 
41626      Time:     While system is running.
41627 
41628      Meaning:  The   current  rtdt   could  not   be  renamed  to
41629                accomodate the installation of a new rtdt.
41630 
41631      Action:   Notify the system administrator.
41632 
41633 
41634                [up_rtdt_.pl1]
41635                up_rtdt_:    ERROR_MESSAGE   Cannot   update   RCP
41636                registry for RESOURCE_NAME.
41637 
41638 
41639      Stream:   as (severity2)
41640 
41641      Time:     While system is running.
41642 
41643      Meaning:  The  error  described  by  ERROR_MESSAGE  occurred
41644                while  a system   administrator was  attempting to
41645                install a new rtdt.  The rtdt contained changes to
41646                a  resource  type,  but  the  resource  management
41647                registry  for  that  resource  type  could  not be
41648                modified.  The rtdt is  not installed.  Some other
41649                registries   may   already   have   been  modified
41650                according to information in the new rtdt.
41651 
41652      Action:   Notify the system administrator.
41653 
41654 
41655                [up_sat_.pl1]
41656 
41657 
41658 up_sat_                        719            08/03/23     MR12.7^L
41659 
41660 
41661                up_sat_:   adding PROJ project  with authorization
41662                AUTH
41663 
41664 
41665      Stream:   as (severity0)
41666 
41667      Time:     While system is running.
41668 
41669      Meaning:  A  system  security  administrator  has  added the
41670                project  PROJ with  an authorization  greater than
41671                system low.
41672 
41673      Action:   No operator action is required.
41674 
41675 
41676                [up_sat_.pl1]
41677                up_sat_:   bumping NAME.PROJ,   over max  users on
41678                project
41679 
41680 
41681      Stream:   as (severity1)
41682 
41683      Time:     While system is running.
41684 
41685      Meaning:  The user named has  been bumped because the system
41686                administrator  has reduced  the maximum  number of
41687                users that can be logged in on the project PROJ.
41688 
41689      Action:   No operator action is required.
41690 
41691 
41692                [up_sat_.pl1]
41693                up_sat_:  bumping NAME.PROJ, project authorization
41694                reduced
41695 
41696 
41697      Stream:   as (severity1)
41698 
41699      Time:     While system is running.
41700 
41701      Meaning:  A  system security  administrator has  installed a
41702                new  SAT that  reduces the  authorization for  the
41703                user identified by NAME  on the project PROJ below
41704                the  current  value   assigned  to  this  project.
41705                Therefore,  the  user  is  being  bumped  from the
41706                system.
41707 
41708      Action:   No operator action is required.
41709 
41710 
41711                [up_sat_.pl1]
41712                up_sat_:  bumping NAME.PROJ, project deleted
41713 
41714 
41715 
41716 up_sat_                        720            08/03/23     MR12.7^L
41717 
41718 
41719      Stream:   as (severity1)
41720 
41721      Time:     While system is running.
41722 
41723      Meaning:  The system  administrator has deleted  the project
41724                PROJ.  All of its users are bumped.
41725 
41726      Action:   No operator action is required.
41727 
41728 
41729                [up_sat_.pl1]
41730                up_sat_:   changing authorization of  PROJ project
41731                from OLD to NEW
41732 
41733 
41734      Stream:   as (severity0)
41735 
41736      Time:     While system is running.
41737 
41738      Meaning:  A  system security  administrator has  installed a
41739                new  SAT  that  changes  the  authorization of the
41740                project PROJ.   OLD is the  previous authorization
41741                for  the  project;  NEW  is  the authorization now
41742                assigned to the project.
41743 
41744      Action:   No operator action is required.
41745 
41746 
41747                [up_sat_.pl1]
41748                up_sat_:  ERROR_MESSAGE.  cannot make temp
41749 
41750 
41751      Stream:   as (severity1)
41752 
41753      Time:     While system is running.
41754 
41755      Meaning:  A  temporary segment  could not  be created  while
41756                attempting to install a new system administrator's
41757                table.  The system attempts to proceed.
41758 
41759      Action:   Contact the system programming staff.
41760 
41761 
41762                [up_sat_.pl1]
41763                up_sat_:  ERROR_MESSAGE.  sat.ht
41764 
41765 
41766      Stream:   as (severity2)
41767 
41768      Time:     While system is running.
41769 
41770      Meaning:  The  system was  unable  to  replace the  SAT hash
41771                table, during installation of  a new SAT.  The new
41772 
41773 
41774 up_sat_                        721            08/03/23     MR12.7^L
41775 
41776 
41777                SAT has been installed, but  the old hash table is
41778                still in use, so any new projects are unusable.
41779 
41780      Action:   Contact the system programming staff.
41781 
41782 
41783                [up_sat_.pl1]
41784                up_sat_:  ERROR_MESSAGE.  sat.ht.temp
41785 
41786 
41787      Stream:   as (severity2)
41788 
41789      Time:     While system is running.
41790 
41791      Meaning:  A  temporary segment  could not  be created  while
41792                attempting to build a hash  table for a new system
41793                administrator's table (SAT).  The new SAT has been
41794                installed, but the old hash table is still in use,
41795                so any new projects are unusable.
41796 
41797      Action:   Contact the system programming staff.
41798 
41799 
41800                [up_sat_.pl1]
41801                up_sat_:  project PROJ on free list state nonzero
41802 
41803 
41804      Stream:   as (severity2)
41805 
41806      Time:     While system is running.
41807 
41808      Meaning:  The  free chain  for the  SAT seems  to include  a
41809                project that does not have state zero.  The system
41810                abandons the free chain and attempts to proceed.
41811 
41812      Action:   Contact the system programming staff._sa
41813 
41814 
41815                [up_sysctl_.pl1]
41816                up_sysctl_$check_acs:  MESSAGE.   Unable to create
41817                PATHNAME.
41818 
41819 
41820      Stream:   as (severity1)
41821 
41822      Time:     While system is running.
41823 
41824      Meaning:  The named  segment does not exist, and  it was not
41825                possible  to create  it.  Any  table installations
41826                controlled by this segment  will be ignored.  (The
41827                table submitted for installation will be deleted.)
41828 
41829 
41830 
41831 
41832 up_sysctl_$check_acs           722            08/03/23     MR12.7^L
41833 
41834 
41835      Action:   Contact the system  programming staff.  Notify the
41836                system  administrator.  Normal servicing  of table
41837                installations   will   not   proceed   until  this
41838                situation is rectified.
41839 
41840 
41841 
41842                [up_sysctl_.pl1]
41843                up_sysctl_$check_acs:   PATHNAME  not  found.   It
41844                will be created.
41845 
41846 
41847      Stream:   as (severity1)
41848 
41849      Time:     While system is running.
41850 
41851      Meaning:  The   named  segment,   which  controls   a  table
41852                installation  operation,  does   not  exist.   The
41853                segment  will  be  created  with  an  ACL allowing
41854                *.SysDaemon.*  and  *.SysAdmin.*  to  perform  the
41855                appropriate table installation.
41856 
41857      Action:   Contact the system  programming staff.  The system
41858                administrator should be notified,  so that the ACL
41859                of  the segment may  be adjusted to  reflect those
41860                users that may install the table.
41861 
41862 
41863 
41864                [up_sysctl_.pl1]
41865                up_sysctl_$init:       ERROR_MESSAGE.       cannot
41866                find/create >system_control_1>update
41867 
41868 
41869      Stream:   as (severity2)
41870 
41871      Time:     System Intialization.
41872 
41873      Meaning:  The  directory  used  to  update  system tables is
41874                missing and  cannot be created.   No installations
41875                of new  system tables cannot be  done.  Logins and
41876                logouts can go on as usual.
41877 
41878      Action:   Contact the system programming staff._sa
41879 
41880 
41881                [up_sysctl_.pl1]
41882                up_sysctl_$init:  ERROR_MESSAGE.   Cannot make IPC
41883                channel.
41884 
41885 
41886      Stream:   as (severity2)
41887 
41888 
41889 
41890 up_sysctl_$init                723            08/03/23     MR12.7^L
41891 
41892 
41893      Time:     System Intialization.
41894 
41895      Meaning:  It was  not possible to establish  the IPC channel
41896                which is  used to allow users to  indicate that an
41897                Answering  Service  table  installation  is  to be
41898                performed.  Installations will not occur.
41899 
41900      Action:   Contact the system programming staff._sa
41901 
41902 
41903                [up_sysctl_.pl1]
41904                up_sysctl_:  CONDITION installing TABLE for USER
41905 
41906 
41907      Stream:   as (severity1)
41908 
41909      Time:     While system is running.
41910 
41911      Meaning:  Some unexpected error  occurred while installing a
41912                system  table.   An  Answering  Service  dump  was
41913                performed.   Further  attempts  to  install system
41914                tables may  fail until a  reset or force  is done,
41915                but logins  and logouts should be  able to proceed
41916                normally.
41917 
41918      Action:   Contact the system programming staff._sa
41919 
41920 
41921                [up_sysctl_.pl1]
41922                up_sysctl_:  error - event calls were masked
41923 
41924 
41925      Stream:   sc (error_output)
41926 
41927      Time:     While system is running.
41928 
41929      Meaning:  This indicates a logic error in the supervisor, or
41930                CPU  or  memory  hardware  problems.   The  system
41931                attempts to recover and keep running.
41932 
41933      Action:   Contact the system programming staff.
41934 
41935 
41936                [up_sysctl_.pl1]
41937                up_sysctl_:  Error:  REASON
41938 
41939 
41940      Stream:   as (severity2)
41941 
41942      Time:     While system is running.
41943 
41944      Meaning:  Some  error  occurred  while  installing  a system
41945                table.  An  Answering Service dump  was performed.
41946 
41947 
41948 up_sysctl_                     724            08/03/23     MR12.7^L
41949 
41950 
41951                Further attempts to install system tables may fail
41952                until  a force  or reset  is done,  but logins and
41953                logouts should be able to proceed as usual.
41954 
41955      Action:   Contact the system programming staff._sa
41956 
41957 
41958                [up_sysctl_.pl1]
41959                up_sysctl_:  installed TABLE for USERID
41960 
41961 
41962      Stream:   as (severity1)
41963 
41964      Time:     While system is running.
41965 
41966      Meaning:  An mgt, sat, cdt, pdt, or rtdt has been installed.
41967 
41968      Action:   No operator action is required.
41969 
41970 
41971                [up_sysctl_.pl1]
41972                up_sysctl_:  NAME  wakeup with N  installs pending
41973                up_sysctl_:  NAME wakeup  from PERSON.PROJECT with
41974                N installs pending
41975 
41976 
41977 
41978      Stream:   as (severity0)
41979 
41980      Time:     While system is running.
41981 
41982      Meaning:  A  request  to  perform  a  table installation was
41983                received.   There were  N tables  found ready  for
41984                installation at  the time of the wakeup.   If N is
41985                0,  the PERSON.PROJECT  of the  originator of  the
41986                request is also logged.   This message is normally
41987                severity0, but  the administrator may cause  it to
41988                be severity1.
41989 
41990      Action:   Contact   the  system   programming  staff.    The
41991                administrator may  request that he be  notified if
41992                this occurs.  If a  large number of these messages
41993                are logged with N = 0, it may indicate that a user
41994                is harassing the installation mechanism.
41995 
41996 
41997 
41998                [up_sysctl_.pl1]
41999                up_sysctl_:  Unable  to install TABLE  for USERID.
42000                TEXT
42001 
42002 
42003      Stream:   as (severity1)
42004 
42005 
42006 up_sysctl_                     725            08/03/23     MR12.7^L
42007 
42008 
42009      Time:     While system is running.
42010 
42011      Meaning:  The  user USERID  attempted to  change the  system
42012                table TABLE  but something was wrong.   The reason
42013                is given by TEXT.
42014 
42015      Action:   No operator action is required.
42016 
42017 
42018                [up_sysctl_.pl1]
42019                up_sysctl_:  Unable  to install TABLE  for USERID.
42020                userid should be USERID1
42021 
42022 
42023      Stream:   as (severity1)
42024 
42025      Time:     While system is running.
42026 
42027      Meaning:  A  user attempted  to  install  a system  table by
42028                pretending to be some other user.
42029 
42030      Action:   Contact the system programming staff._sa
42031 
42032 
42033                [validate_cpu_card.pl1]
42034                validate_cpu_card:  CPU cache  size for CPU CPUTAG
42035                is incorrect, should be "CACHE_SIZE."
42036 
42037 
42038      Stream:   BOS Typewriter (sounds beeper)
42039 
42040      Time:     While system is running.
42041 
42042      Meaning:  The CACHE_SIZE  as determined from  cpu registers,
42043                did not match the CACHE_SIZE in the cpu cache size
42044                field of the config card image for CPU CPUTAG.
42045 
42046      Action:   No operator action is required.
42047 
42048 
42049                [validate_cpu_card.pl1]
42050                validate_cpu_card:   CPU model  for CPU  CPUTAG is
42051                incorrect, should be "CPUMODEL."
42052 
42053 
42054      Stream:   BOS Typewriter (sounds beeper)
42055 
42056      Time:     While system is running.
42057 
42058      Meaning:  The   CPUMODEL   as   determined   from   RSW  (2)
42059                information, did not match the CPUMODEL in the cpu
42060                model  field  of  the  config  card  image for CPU
42061                CPUTAG.
42062 
42063 
42064 validate_cpu_card              726            08/03/23     MR12.7^L
42065 
42066 
42067      Action:   No operator action is required.
42068 
42069 
42070                [validate_cpu_card.pl1]
42071                validate_cpu_card:   CPU type   for CPU  CPUTAG is
42072                incorrect, should be "CPUTYPE"
42073 
42074 
42075      Stream:   BOS Typewriter (sounds beeper)
42076 
42077      Time:     While system is running.
42078 
42079      Meaning:  The   CPUTYPE   as   determined   from   RSW   (2)
42080                information, did not match  the CPUTYPE in the cpu
42081                type  field  of  the  config  card  image  for CPU
42082                CPUTAG.
42083 
42084      Action:   No operator action is required.
42085 
42086 
42087                [validate_cpu_card.pl1]
42088                validate_cpu_card:  CPU type,  model, and/or cache
42089                size discrepencies will be corrected
42090 
42091 
42092      Stream:   BOS Typewriter.
42093 
42094      Time:     While system is running.
42095 
42096      Meaning:  The  indicated  discrepencies  in  the  cpu  type,
42097                model, and cache size fields, will be corrected by
42098                validate_cpu_card.
42099 
42100      Action:   The type,  model, and/or cache size  fields of the
42101                indicated   cpu  config   card  image   should  be
42102                corrected at BCE, before the next bootload.
42103 
42104 
42105 
42106                [verify_lock.pl1]
42107                verify_lock:  block_lock_count XX, should be 0
42108 
42109 
42110      Stream:   BOS Typewriter (Crashes system)
42111 
42112      Time:     While system is running.
42113 
42114      Meaning:  A process  has encountered a condition  in ring 0,
42115                and  is in the  process of attempting  a crawlout.
42116                The  system  must  unlock   all  locks  before  it
42117                performs the  crawlout; all known locks  have been
42118                unlocked  but the  process' lock  counter is still
42119                nonzero.   This  indicates  a  logic  error in the
42120 
42121 
42122 verify_lock                    727            08/03/23     MR12.7^L
42123 
42124 
42125                supervisor,  or CPU  or memory  hardware problems.
42126                BOS Typewriter (Crashes system)es
42127 
42128      Action:   Follow normal recovery procedures.
42129 
42130 
42131                [verify_lock.pl1]
42132                verify_lock:  Crawlout error on directory cleanup.
42133 
42134 
42135      Stream:   BOS Typewriter (Crashes system)
42136 
42137      Time:     While system is running.
42138 
42139      Meaning:  A process  encountered a signalled  condition with
42140                one or more directories locked.  Before the system
42141                causes  a crawlout,  it unlocks  and salvages  all
42142                locked directories for  the process.  This process
42143                of  cleanup  encountered  an  unrecoverable error.
42144                BOS Typewriter (Crashes system)es
42145 
42146      Action:   Follow normal recovery procedures.
42147 
42148 
42149                [verify_lock.pl1]
42150                verify_lock:   Crawlout  stop  specified  on  PARM
42151                card.
42152 
42153 
42154      Stream:   BOS Typewriter (Crashes system)
42155 
42156      Time:     While system is running.
42157 
42158      Meaning:  The system PARM card specified the CRWL parameter.
42159                A  process  is  attempting  to  crawl  out.   This
42160                message will occur so  that system programmers can
42161                take a dump.
42162 
42163      Action:   Take  a dump.   Issuing  the  BCE go  command will
42164                cause the system to continue.
42165 
42166 
42167 
42168                [verify_lock.pl1]
42169                verify_lock:    Crawlout    while   in   directory
42170                salvager, dir (UID,PTR).
42171 
42172 
42173      Stream:   Logged in SYSERR log.
42174 
42175      Time:     While system is running.
42176 
42177 
42178 
42179 
42180 verify_lock                    728            08/03/23     MR12.7^L
42181 
42182 
42183      Meaning:  A  process  faulted  while   salvaging  a  dir  on
42184                crawlout.
42185 
42186      Action:   No operator action is required.
42187 
42188 
42189                [verify_lock.pl1]
42190                verify_lock:  Crawlout while masked.
42191 
42192 
42193      Stream:   BOS Typewriter (Crashes system)
42194 
42195      Time:     While system is running.
42196 
42197      Meaning:  BOS Typewriter (Crashes system)es
42198 
42199      Action:   Contact the system programming staff.
42200 
42201 
42202                [verify_lock.pl1]
42203                verify_lock:  Crawlout with AST lock set.
42204 
42205 
42206      Stream:   BOS Typewriter (Crashes system)
42207 
42208      Time:     While system is running.
42209 
42210      Meaning:  A  user  process  encountered  a  condition  while
42211                processing  with the  AST locked.   This condition
42212                may  have  been  due  to  a  hardware  or software
42213                failure.  BOS Typewriter (Crashes system)es
42214 
42215      Action:   Follow normal recovery procedures.
42216 
42217 
42218                [verify_lock.pl1]
42219                verify_lock:  dir.modify PPPP WWWW ^^= processid.
42220 
42221 
42222      Stream:   BOS Typewriter (Crashes system)
42223 
42224      Time:     While system is running.
42225 
42226      Meaning:  A process is attempting  to crawl out.  The system
42227                has  discovered that  a directory  which is marked
42228                locked to  the process has its  "modify" field not
42229                equal  to  the  processid  of  the  process.  This
42230                indicates a logic error  in the supervisor, or CPU
42231                or  memory  hardware   problems.   BOS  Typewriter
42232                (Crashes system)es
42233 
42234      Action:   Follow normal recovery procedures.
42235 
42236 
42237 
42238 verify_lock                    729            08/03/23     MR12.7^L
42239 
42240 
42241 
42242 
42243                [verify_lock.pl1]
42244                verify_lock:  Force unlocked Volmap lock (dskX_NN)
42245                on crawlout for PERSON.PROJECT.TAG
42246 
42247 
42248      Stream:   Logged in SYSERR log.
42249 
42250      Time:     While system is running.
42251 
42252      Meaning:  The Volmap Lock for the device indicated was found
42253                locked  to a  process on  crawlout.  The  lock has
42254                been    reset,   and    the   count    of   volume
42255                inconsistencies   for   the    device   has   been
42256                incremented by one.
42257 
42258      Action:   Any  free records  or VTOCEs  lost because  of the
42259                crawlout can be recovered by a volume salvage.
42260 
42261 
42262 
42263                [verify_lock.pl1]
42264                verify_lock:    Force  unlocked   VTOC  Map   lock
42265                (dskX_NN) on crawlout for PERSON.PROJECT.TAG
42266 
42267 
42268      Stream:   Logged in SYSERR log.
42269 
42270      Time:     While system is running.
42271 
42272      Meaning:  The  VTOC Map  lock for  the device  indicated was
42273                found locked to the process on crawlout.  The lock
42274                has   been  reset,   and  the   count  of   volume
42275                inconsistencies has been incremented by one.
42276 
42277      Action:   Any  free records  or VTOCEs  lost because  of the
42278                crawlout can be recovered by a volume salvage.
42279 
42280 
42281 
42282                [verify_lock.pl1]
42283                verify_lock:  more  than N directory  locks locked
42284                to process.
42285 
42286 
42287      Stream:   BOS Typewriter (Crashes system)
42288 
42289      Time:     While system is running.
42290 
42291      Meaning:  The process  held more dir locks  than verify lock
42292                could store for later salvaging.  This indicates a
42293                logic error in the supervisor.
42294 
42295 
42296 verify_lock                    730            08/03/23     MR12.7^L
42297 
42298 
42299      Action:   BOS  Typewriter (Crashes  system)es Follow  normal
42300                recovery procedures.
42301 
42302 
42303 
42304                [verify_lock.pl1]
42305                verify_lock:  NAME condition by PERS.PROJ
42306 
42307 
42308      Stream:   Logged in SYSERR log.
42309 
42310      Time:     While system is running.
42311 
42312      Meaning:  User  PERS.PROJ encountered   a NAME  condition in
42313                ring 0.   The system attempts to  unlock and reset
42314                all ring 0 data bases locked by the process.
42315 
42316      Action:   These  messages  almost   always  indicate  benign
42317                errors   in  the   supervisor.   They   should  be
42318                reported,  nonetheless.  They  are accompanied  by
42319                the  binary machine  condition information.   This
42320                message is logged only  when the condition occured
42321                while  some  ring-0  lock  was  set.   One or more
42322                messages preceeding  this one will  indicate which
42323                locks were held by the process and forcibly reset.
42324 
42325 
42326 
42327                [verify_lock.pl1]
42328                verify_lock:  Salvaging dir PTR UID on crawlout.
42329 
42330 
42331      Stream:   Logged in SYSERR log.
42332 
42333      Time:     While system is running.
42334 
42335      Meaning:  This message is displayed for each directory found
42336                locked on a crawlout.  The online salvager will be
42337                called and the directory unlocked.
42338 
42339      Action:   No operator action is required.
42340 
42341 
42342                [verify_lock.pl1]
42343                verify_lock:  Unlocked LOCK.
42344 
42345 
42346      Stream:   Logged in SYSERR log.
42347 
42348      Time:     While system is running.
42349 
42350      Meaning:  The  lock LOCK  was found  locked at  crawlout and
42351                unlocked.
42352 
42353 
42354 verify_lock                    731            08/03/23     MR12.7^L
42355 
42356 
42357      Action:   No operator action is required.
42358 
42359 
42360                [verify_lock.pl1]
42361                verify_lock:  Unlocking  dir UUUUUUUUUUUU.  Locked
42362                for READ_OR_WRITE {,salvage}.
42363 
42364 
42365      Stream:   Logged in SYSERR log.
42366 
42367      Time:     While system is running.
42368 
42369      Meaning:  The  directory  with  UID  UUUUUUUUUUUU  was found
42370                locked at crawl-out time.  It is salvaged and then
42371                unlocked.
42372 
42373      Action:   Contact the system programming staff.
42374 
42375 
42376                [vm_vio.pl1]
42377                vm_vio:  get_vtocep:  invalid pvtx:  PPPo
42378 
42379 
42380      Stream:   BOS Typewriter.
42381 
42382      Time:     Volume salvaging or disk rebuilding.
42383 
42384      Meaning:  The  Volume Salvager   virtual access  package has
42385                been given  a bad PVT index  parameter, PPP (shown
42386                in  octal).  This indicates  a logic error  in the
42387                supervisor, or CPU or memory hardware problems.
42388 
42389      Action:   Salvaging will not proceed.  $boot_tape
42390 
42391 
42392 
42393                [vm_vio.pl1]
42394                vm_vio:  get_vtocep:   invalid vtocx VVVo  on pvtx
42395                PPPo
42396 
42397 
42398      Stream:   BOS Typewriter.
42399 
42400      Time:     Volume salvaging or disk rebuilding.
42401 
42402      Meaning:  An out-of-range VTOC index (VVV) has been given to
42403                the Volume  Salvager virtual access  package while
42404                processing PV at pvtx PPP.  The vtocx and pvtx are
42405                shown in  octal.  This indicates a  logic error in
42406                the   supervisor,  or   CPU  or   memory  hardware
42407                problems.
42408 
42409 
42410 
42411 
42412 vm_vio                         732            08/03/23     MR12.7^L
42413 
42414 
42415      Action:   Salvaging  may fail.   Note for  system programmer
42416                action.
42417 
42418 
42419 
42420                [vm_vio.pl1]
42421                vm_vio:  no AST pointer at readahead.
42422 
42423 
42424      Stream:   BOS Typewriter (Crashes system)
42425 
42426      Time:     Volume salvaging or disk rebuilding.
42427 
42428      Meaning:  No   AST   entry   pointer   was   found   for   a
42429                VTOC-addressing   segment  used   by  the   Volume
42430                Salvager virtual access package.  This indicates a
42431                logic  error in the  supervisor, or CPU  or memory
42432                hardware problems.
42433 
42434      Action:   Follow  normal  recovery   procedures.   Note  for
42435                system programmer action.
42436 
42437 
42438 
42439                [page_error.alm]
42440                volmap:  Attempt to  deposit in-use address YYYYYY
42441                on dskX_NN{S}.
42442 
42443 
42444      Stream:   BOS Typewriter.
42445 
42446      Time:     While system is running.
42447 
42448      Meaning:  An attempt was made  to return disk address YYYYYY
42449                to  the free pool  on dskX_NN{S}, but  the address
42450                was already marked as free.  This indicates damage
42451                of some  sort to the Volume Map.   This damage can
42452                be repaired by a volume salvage.
42453 
42454      Action:   Contact the system programming staff.
42455 
42456 
42457                [page_error.alm]
42458                volmap:   Invalid Volume  Map address  computation
42459                for YYYYYY on dskX_NN{S}.
42460 
42461 
42462      Stream:   BOS Typewriter (Crashes system)
42463 
42464      Time:     While system is running.
42465 
42466      Meaning:  In  attempting to  place the  disk address  YYYYYY
42467                into  the  free  pool  for  dskX_NN{S},  an  error
42468 
42469 
42470 volmap                         733            08/03/23     MR12.7^L
42471 
42472 
42473                occurred  in   translating  the  address   into  a
42474                location within the Volume  Map.  This indicates a
42475                software error.
42476 
42477 
42478 
42479                [page_error.alm]
42480                volmap:  Invalid volume map word on dskX_NN{S}.
42481 
42482 
42483      Stream:   BOS Typewriter (Crashes system)
42484 
42485      Time:     While system is running.
42486 
42487      Meaning:  An  attempt to  withdraw a  disk address  from the
42488                pool of  free addresses on dskX_NN{S}  resulted in
42489                finding  a volume  map word  with at  least one of
42490                bits 0, 33, 34, and 35 on.  These bits are invalid
42491                for volume map words.   This indicates hardware or
42492                software failure.
42493 
42494      Action:   Perform an  ESD.  Reboot the system  and perform a
42495                volume salvage (not a scavenge) of the disk volume
42496                dskX_NN{S}.  This may  be performed at Initializer
42497                ring-1  or  ring-4  command  level.   Perform  the
42498                salvage  before adding  the storage  system volume
42499                back to the system.  The volume scavenger will not
42500                detect volume map words with invalid bits enabled,
42501                so the salvager must be used.  Once the salvage is
42502                complete,  the volume  may  be  added back  to the
42503                system.
42504 
42505 
42506 
42507                [page_error.alm]
42508                volmap:  record stock  inconsistent on dskX_NN{S}.
42509                stockp=YYY|YYYYY.
42510 
42511 
42512      Stream:   BOS Typewriter (Crashes system)
42513 
42514      Time:     While system is running.
42515 
42516      Meaning:  An  attempt to deposit  a record address  from the
42517                Volume   Map   to    the   record   stock   failed
42518                unaccountably.   This indicates  probably software
42519                failure.
42520 
42521      Action:   Follow normal recovery procedures.
42522 
42523 
42524                [page_error.alm]
42525                volmap:  Volume Map inconsistent on dskX_NN{S}.
42526 
42527 
42528 volmap                         734            08/03/23     MR12.7^L
42529 
42530 
42531      Stream:   BOS Typewriter (Crashes system)
42532 
42533      Time:     While system is running.
42534 
42535      Meaning:  An  attempt to  withdraw a  disk address  from the
42536                pool  of  free  addresses  on  dskX_NN{S}  failed,
42537                although  the  control  structures  describing the
42538                Volume   Map   indicated   that   addresses   were
42539                available.   This indicates  hardware or  software
42540                failure.
42541 
42542      Action:   Follow normal recovery procedures.
42543 
42544 
42545                [page_error.alm]
42546                volmap_page:  Async error for dskX_NN{S}.
42547 
42548 
42549      Stream:   BOS Typewriter (Crashes system)
42550 
42551      Time:     While system is running.
42552 
42553      Meaning:  When  attempting to write  an updated page  of the
42554                Volume Map  on dskX_NN{S}, it was found  not to be
42555                in memory.  This indicates a software failure.
42556 
42557      Action:   Follow normal recovery procedures.
42558 
42559 
42560                [page_error.alm]
42561                volmap_page:  Async state on dskX_NN{S} changed to
42562                S on poll.
42563 
42564 
42565      Stream:   Logged in SYSERR log.
42566 
42567      Time:     While system is running.
42568 
42569      Meaning:  An interrupt for a volume map I/O was lost and was
42570                recovered by a periodic polling routine.
42571 
42572      Action:   No operator action is required.
42573 
42574 
42575                [page_error.alm]
42576                volmap_page:  Invalid async state on dskX_NN{S}.
42577 
42578 
42579      Stream:   BOS Typewriter (Crashes system)
42580 
42581      Time:     While system is running.
42582 
42583 
42584 
42585 
42586 volmap_page                    735            08/03/23     MR12.7^L
42587 
42588 
42589      Meaning:  An    inconsistency   was   discovered    in   the
42590                asynchronous  update state  of the  Volume Map  on
42591                dskX_NN{S}.  This is likely a software error.
42592 
42593      Action:   Follow normal recovery procedures.
42594 
42595 
42596                [page_error.alm]
42597                volmap_page:  Invalid call.
42598 
42599 
42600      Stream:   BOS Typewriter (Crashes system)
42601 
42602      Time:     While system is running.
42603 
42604      Meaning:  One  of the  conditions required  for a  call to a
42605                volmap_page  entry point   was not  present.  This
42606                indicates  a  software  failure  in  the caller of
42607                volmap_page.
42608 
42609      Action:   Follow normal recovery procedures.
42610 
42611 
42612                [page_error.alm]
42613                volmap_page:  PTL not locked to process.
42614 
42615 
42616      Stream:   BOS Typewriter (Crashes system)
42617 
42618      Time:     While system is running.
42619 
42620      Meaning:  An entry in volmap_page  was called which required
42621                that  the Global  Page Table  lock be  held by the
42622                calling process.  It was not held by that process,
42623                indicating software failure.
42624 
42625      Action:   Follow normal recovery procedures.
42626 
42627 
42628                [page_error.alm]
42629                volmap_page:   Unrecoverable I/O  error on  Volmap
42630                page M of dskX_NN{S}.  Addresses lost.
42631 
42632 
42633      Stream:   BOS Typewriter (sounds beeper)
42634 
42635      Time:     While system is running.
42636 
42637      Meaning:  There was  an unrecoverable I/O  on a page  of the
42638                Volume  Map, which  describes free  records on the
42639                volume.  As  a result, all free  records described
42640                by that page of the Volume Map have been lost.
42641 
42642 
42643 
42644 volmap_page                    736            08/03/23     MR12.7^L
42645 
42646 
42647      Action:   It may  be possible to recover  the lost addresses
42648                by a volume salvage.  However, a hard device error
42649                will prevent  the volume salvage  from succeeding.
42650                In this case, it will  be necessary to recover the
42651                volume to a good pack.
42652 
42653 
42654 
42655                [volmap_util.pl1]
42656                volmap_util:  Address XXXXXX  out of paging region
42657                on dskX_NN.
42658 
42659 
42660      Stream:   BOS Typewriter (Crashes system)
42661 
42662      Time:     During a physical volume scavenge
42663 
42664      Meaning:  The  scavenger  attempted  to  remove  an  invalid
42665                address from the volume map.
42666 
42667      Action:   Follow normal recovery procedures.
42668 
42669 
42670                [volmap_util.pl1]
42671                volmap_util:  Invalid address XXXXXX on dskX_NN.
42672 
42673 
42674      Stream:   BOS Typewriter (Crashes system)
42675 
42676      Time:     During a physical volume scavenge
42677 
42678      Meaning:  In attempting to deposit  address XXXXXX on device
42679                dskX_NN,   an  invalid   volume  map   offset  was
42680                computed.
42681 
42682      Action:   Follow normal recovery procedures.
42683 
42684 
42685                [init_disk_pack_.pl1]
42686                volume PVNAME XX records
42687 
42688 
42689      Stream:   Initializer process output.
42690 
42691      Time:     In response to an operator command.
42692 
42693      Meaning:  The physical  volume PVNAME has  been successfully
42694                initialized.   There are  XX (decimal)  records in
42695                the paging area.
42696 
42697      Action:   No operator action is required.
42698 
42699 
42700 
42701 
42702 volume_registration_mgr_$add_lvr^H737            08/03/23     MR12.7^L
42703 
42704 
42705                [volume_registration_mgr_.pl1]
42706                volume_registration_mgr_$add_lvr:   Added  new  LV
42707                "LVNAME".  (GROUP_ID)
42708 
42709 
42710      Stream:   Logged in SYSERR log.
42711 
42712      Time:     While system is running.
42713 
42714      Meaning:  A  new  storage  system  logical  volume  has been
42715                registered on the system.
42716 
42717      Action:   No operator action is required.
42718 
42719 
42720                [volume_registration_mgr_.pl1]
42721                volume_registration_mgr_$add_lvr:   Added  new  PV
42722                "PVNAME" to LV "LVNAME".  (GROUP_ID)
42723 
42724 
42725      Stream:   Logged in SYSERR log.
42726 
42727      Time:     While system is running.
42728 
42729      Meaning:  A  new  storage  system  physical  volume has been
42730                registered on the system.
42731 
42732      Action:   No operator action is required.
42733 
42734 
42735                [volume_registration_mgr_.pl1]
42736                volume_registration_mgr_$add_lvr:     Could    not
42737                append link for {LV name | LVID | PV name | PVID}.
42738                (GROUP_ID) ERROR_MESSAGE
42739 
42740 
42741      Stream:   BOS Typewriter.
42742 
42743      Time:     While system is running.
42744 
42745      Meaning:  A link could not be added into >lv whose target is
42746                a   database  segment   located  under   the  root
42747                directory.  Future database  references may not be
42748                possible.
42749 
42750      Action:   Contact the system programming staff.
42751 
42752 
42753                [volume_registration_mgr_.pl1]
42754                volume_registration_mgr_$add_lvr:  Unable  to back
42755                out     database      "lv.LVNAME".      (GROUP_ID)
42756                ERROR_MESSAGE
42757 
42758 
42759 
42760 volume_registration_mgr_$add_lvr^H738            08/03/23     MR12.7^L
42761 
42762 
42763      Stream:   BOS Typewriter.
42764 
42765      Time:     While system is running.
42766 
42767      Meaning:  When attempting to register  a new logical volume,
42768                some error occurred.  The  entry then attempted to
42769                remove  the database  segment just  created.  This
42770                removal failed.
42771 
42772      Action:   Contact the system programming staff.
42773 
42774 
42775                [volume_registration_mgr_.pl1]
42776                volume_registration_mgr_$add_pvr:   Added  new  PV
42777                "PVNAME" to LV "LVNAME".  (GROUP_ID) -log-
42778 
42779 
42780      Stream:   Logged in SYSERR log.
42781 
42782      Time:     While system is running.
42783 
42784      Meaning:  A  new  storage  system  physical  volume has been
42785                registered on the system.
42786 
42787      Action:   No operator action is required.
42788 
42789 
42790                [volume_registration_mgr_.pl1]
42791                volume_registration_mgr_$add_pvr:     Could    not
42792                append  link  for  {PV  name|  PVID}.   (GROUP_ID)
42793                ERROR_MESSAGE
42794 
42795 
42796      Stream:   BOS Typewriter.
42797 
42798      Time:     While system is running.
42799 
42800      Meaning:  A link could not be added into >lv whose target is
42801                a   database  segment   located  under   the  root
42802                directory.  Future database  references may not be
42803                possible.
42804 
42805      Action:   Contact the system programming staff.
42806 
42807 
42808                [volume_registration_mgr_.pl1]
42809                volume_registration_mgr_$add_pvr:  Extra  PV entry
42810                "PVNAME" in database "lv.LVNAME".  (GROUP_ID)
42811 
42812 
42813      Stream:   BOS Typewriter.
42814 
42815      Time:     While system is running.
42816 
42817 
42818 volume_registration_mgr_$add_pvr^H739            08/03/23     MR12.7^L
42819 
42820 
42821      Meaning:  This indicates a logic error in the supervisor, or
42822                CPU or memory hardware problems.  An entry for the
42823                specified PV was found in the database segment for
42824                the   specified  LV   where  no   segment  addname
42825                indicated its existance.
42826 
42827      Action:   Contact the system programming staff.
42828 
42829 
42830                [volume_registration_mgr_.pl1]
42831                volume_registration_mgr_$add_pvr:  Unable  to back
42832                out  database   addname  "pv.PVNAME".   (GROUP_ID)
42833                ERROR_MESSAGE
42834 
42835 
42836      Stream:   BOS Typewriter.
42837 
42838      Time:     While system is running.
42839 
42840      Meaning:  An error occurred while registering a new PV.  The
42841                entry attmpts to undo all  work up to the point of
42842                the error.   In this case,  it was unable  to undo
42843                its  manipulations  and  left  a  spurious addname
42844                "pv.PVNAME" on the database segment.
42845 
42846      Action:   Contact the system programming staff.
42847 
42848 
42849                [volume_registration_mgr_.pl1]
42850                volume_registration_mgr_$change_lvr:   Changed ACS
42851                pathname for LV "LVNAME" to "PATH".  (GROUP_ID)
42852 
42853 
42854      Stream:   Logged in SYSERR log.
42855 
42856      Time:     While system is running.
42857 
42858      Meaning:  The  registered ACS  pathname of  a storage system
42859                logical volume has been changed as indicated.
42860 
42861      Action:   No operator action is required.
42862 
42863 
42864                [volume_registration_mgr_.pl1]
42865                volume_registration_mgr_$change_lvr:   Changed  LV
42866                "LVNAME" to {PRIVATE | PUBLIC}.  (GROUP_ID)
42867 
42868 
42869      Stream:   Logged in SYSERR log.
42870 
42871      Time:     While system is running.
42872 
42873 
42874 
42875 
42876 volume_registration_mgr_$change_^H7l^H4v^H0r           08/03/23     MR12.7^L
42877 
42878 
42879      Meaning:  The  access type  of the  specified logical volume
42880                has been changed.
42881 
42882      Action:   No operator action is required.
42883 
42884 
42885                [volume_registration_mgr_.pl1]
42886                volume_registration_mgr_$change_lvr:  Changed LVID
42887                of   LV   "LVNAME"   from   "LVID1"   to  "LVID2".
42888                (GROUP_ID)
42889 
42890 
42891      Stream:   Logged in SYSERR log.
42892 
42893      Time:     While system is running.
42894 
42895      Meaning:  The registered  logical volume unique ID  has been
42896                changed for the specified LV.
42897 
42898      Action:   No operator action is required.
42899 
42900 
42901                [volume_registration_mgr_.pl1]
42902                volume_registration_mgr_$change_lvr:  Changed name
42903                of LV "LVNAME1" to "LVNAME2".  (GROUP_ID)
42904 
42905 
42906      Stream:   Logged in SYSERR log.
42907 
42908      Time:     While system is running.
42909 
42910      Meaning:  The  registered name  of a  storage system logical
42911                volume has been changed as indicated.
42912 
42913      Action:   No operator action is required.
42914 
42915 
42916                [volume_registration_mgr_.pl1]
42917                volume_registration_mgr_$change_lvr:       Changed
42918                owner  of LV  "LVNAME" from  "Person1.Project1" to
42919                "Person2.Project2".  (GROUP_ID)
42920 
42921 
42922      Stream:   Logged in SYSERR log.
42923 
42924      Time:     While system is running.
42925 
42926      Meaning:  The owner  of a storage system  logical volume has
42927                been changed as indicated.
42928 
42929      Action:   No operator action is required.
42930 
42931 
42932 
42933 
42934 volume_registration_mgr_$change_^H7l^H4v^H1r           08/03/23     MR12.7^L
42935 
42936 
42937                [volume_registration_mgr_.pl1]
42938                volume_registration_mgr_$change_lvr:  Changed {max
42939                |   min}  access   class  of   LV  "LVNAME"   from
42940                "AUTH_STR1" to "AUTH_STR2".  (GROUP_ID)
42941 
42942 
42943      Stream:   Logged in SYSERR log.
42944 
42945      Time:     While system is running.
42946 
42947      Meaning:  The  access  class  of  a  storage  system logical
42948                volume has been changed as indicated.
42949 
42950      Action:   No operator action is required.
42951 
42952 
42953                [volume_registration_mgr_.pl1]
42954                volume_registration_mgr_$change_lvr:      Couldn't
42955                {delete | create} link for  {old | new} {LV name |
42956                LVID}.  (GROUP_ID) ERROR_MESSAGE
42957 
42958 
42959      Stream:   BOS Typewriter.
42960 
42961      Time:     While system is running.
42962 
42963      Meaning:  A link for the specified database segment residing
42964                under the  root directory could not  be created in
42965                >lv.
42966 
42967      Action:   Contact the system programming staff.
42968 
42969 
42970                [volume_registration_mgr_.pl1]
42971                volume_registration_mgr_$change_lvr:    Unable  to
42972                back out LVID change to "LVNAME.mdcs".  (GROUP_ID)
42973                ERROR_MESSAGE
42974 
42975 
42976      Stream:   BOS Typewriter.
42977 
42978      Time:     While system is running.
42979 
42980      Meaning:  This indicates a logic error in the supervisor, or
42981                CPU or  memory hardware problems.   While changing
42982                attributes of the logical  volume LVNAME, an error
42983                was  encountered.   The  entry  then  attempted to
42984                remove   some   changes   already   made   to  the
42985                registration database.  In this case, it could not
42986                remove  the LVID  change to  the master  directory
42987                control database LVNAME.mdcs.
42988 
42989      Action:   Contact the system programming staff.
42990 
42991 
42992 volume_registration_mgr_$change_^H7l^H4v^H2r           08/03/23     MR12.7^L
42993 
42994 
42995 
42996 
42997                [volume_registration_mgr_.pl1]
42998                volume_registration_mgr_$change_lvr:    Unable  to
42999                change  name  "lv.LVNAME1"  back  to  "lv.LVNAME2"
43000                (GROUP_ID) ERROR_MESSAGE
43001 
43002 
43003      Stream:   BOS Typewriter.
43004 
43005      Time:     While system is running.
43006 
43007      Meaning:  This indicates a logic error in the supervisor, or
43008                CPU or  memory hardware problems.   While changing
43009                attributes ot the logical  volume LVNAME, an error
43010                was  encountered.   The  entry  then  attempted to
43011                remove   some   changes   already   made   to  the
43012                registration database.  In this case, it could not
43013                remove theLV name change.
43014 
43015      Action:   Contact the system programming staff.
43016 
43017 
43018                [volume_registration_mgr_.pl1]
43019                volume_registration_mgr_$change_lvr:    Unable  to
43020                change name "lvid.UNIQUE1" back to "lvid.UNIQUE2".
43021                (GROUP_ID) ERROR_MESSAGE
43022 
43023 
43024      Stream:   BOS Typewriter.
43025 
43026      Time:     While system is running.
43027 
43028      Meaning:  This indicates a logic error in the supervisor, or
43029                CPU or  memory hardware problems.   While changing
43030                attributes ot the logical  volume LVNAME, an error
43031                was  encountered.   The  entry  then  attempted to
43032                remove   some   changes   already   made   to  the
43033                registration database.  In this case, it could not
43034                remove LVID name change.
43035 
43036      Action:   Contact the system programming staff.
43037 
43038 
43039                [volume_registration_mgr_.pl1]
43040                volume_registration_mgr_$change_lvr:    Unable  to
43041                convert   {max  |    min}  auth   to  name_string.
43042                (GROUP_ID) ERROR_MESSAGE
43043 
43044 
43045      Stream:   BOS Typewriter.
43046 
43047      Time:     While system is running.
43048 
43049 
43050 volume_registration_mgr_$change_^H7l^H4v^H3r           08/03/23     MR12.7^L
43051 
43052 
43053      Meaning:  This indicates a logic error in the supervisor, or
43054                CPU  or   memory  hardware  problems.    A  binary
43055                authorization string could not be converted to its
43056                readable representation.
43057 
43058      Action:   Contact the system programming staff.
43059 
43060 
43061                [volume_registration_mgr_.pl1]
43062                volume_registration_mgr_$change_lvr:    Unexpected
43063                error  changing name  on "lv.LVNAME".   (GROUP_ID)
43064                ERROR_MESSAGE
43065 
43066 
43067      Stream:   BOS Typewriter.
43068 
43069      Time:     While system is running.
43070 
43071      Meaning:  This indicates a logic error in the supervisor, or
43072                CPU  or memory  hardware problems.   An unexpected
43073                error  occured while  changing the  name on  an LV
43074                registration  data segment.  The  message explains
43075                the trouble.
43076 
43077      Action:   Contact the system programming staff.
43078 
43079 
43080                [volume_registration_mgr_.pl1]
43081                volume_registration_mgr_$change_lvr:    Unexpected
43082                trouble  changing name  "lvid.UNIQUE".  (GROUP_ID)
43083                ERROR_MESSAGE
43084 
43085 
43086      Stream:   BOS Typewriter.
43087 
43088      Time:     While system is running.
43089 
43090      Meaning:  This indicates a logic error in the supervisor, or
43091                CPU  or memory  hardware problems.   An unexpected
43092                error  occured while  changing the  name on  an LV
43093                registration  data segment.  The  message explains
43094                the trouble.
43095 
43096      Action:   Contact the system programming staff.
43097 
43098 
43099                [volume_registration_mgr_.pl1]
43100                volume_registration_mgr_$change_pvr:       Changed
43101                date_registered  of  PV  "PVNAME"  from  "DT1"  to
43102                "DT2".  (GROUP_ID)
43103 
43104 
43105      Stream:   Logged in SYSERR log.
43106 
43107 
43108 volume_registration_mgr_$change_^H7p^H4v^H4r           08/03/23     MR12.7^L
43109 
43110 
43111      Time:     While system is running.
43112 
43113      Meaning:  The registered date for  the specified PV has been
43114                changed as indicated.
43115 
43116      Action:   No operator action is required.
43117 
43118 
43119                [volume_registration_mgr_.pl1]
43120                volume_registration_mgr_$change_pvr:       Changed
43121                location  of PV  "PVNAME" from  "LOC1" to  "LOC2".
43122                (GROUP_ID)
43123 
43124 
43125      Stream:   Logged in SYSERR log.
43126 
43127      Time:     While system is running.
43128 
43129      Meaning:  The  registered location  of the  specified PV has
43130                been changed as indicated.
43131 
43132      Action:   No operator action is required.
43133 
43134 
43135                [volume_registration_mgr_.pl1]
43136                volume_registration_mgr_$change_pvr:       Changed
43137                mfg_serial of  PV "PVNAME" from "STR1"  to "STR2".
43138                (GROUP_ID)
43139 
43140 
43141      Stream:   Logged in SYSERR log.
43142 
43143      Time:     While system is running.
43144 
43145      Meaning:  The registered serial of the specified PV has been
43146                changed as indicated.
43147 
43148      Action:   No operator action is required.
43149 
43150 
43151                [volume_registration_mgr_.pl1]
43152                volume_registration_mgr_$change_pvr:       Changed
43153                model  of  PV  "PVNAME"  from  "TYPE1" to "TYPE2".
43154                (GROUP_ID)
43155 
43156 
43157      Stream:   Logged in SYSERR log.
43158 
43159      Time:     While system is running.
43160 
43161      Meaning:  The  registered model  number of  the specified PV
43162                has been changed as indicated.
43163 
43164 
43165 
43166 volume_registration_mgr_$change_^H7p^H4v^H5r           08/03/23     MR12.7^L
43167 
43168 
43169      Action:   No operator action is required.
43170 
43171 
43172                [volume_registration_mgr_.pl1]
43173                volume_registration_mgr_$change_pvr:  Changed name
43174                of PV "PVNAME1" to "PVNAME2".  (GROUP_ID)
43175 
43176 
43177      Stream:   Logged in SYSERR log.
43178 
43179      Time:     While system is running.
43180 
43181      Meaning:  The registered  name of the specified  PV has been
43182                changed as indicated.
43183 
43184      Action:   No operator action is required.
43185 
43186 
43187                [volume_registration_mgr_.pl1]
43188                volume_registration_mgr_$change_pvr:       Changed
43189                password of PV "PVNAME".  (GROUP_ID)
43190 
43191 
43192      Stream:   Logged in SYSERR log.
43193 
43194      Time:     While system is running.
43195 
43196      Meaning:  The  registered password  of the  specified PV has
43197                been changed as indicated.
43198 
43199      Action:   No operator action is required.
43200 
43201 
43202                [volume_registration_mgr_.pl1]
43203                volume_registration_mgr_$change_pvr:  Changed PVID
43204                of PV "PVNAME" from "PVID1" to "PVID2" (GROUP_ID)
43205 
43206 
43207      Stream:   Logged in SYSERR log.
43208 
43209      Time:     While system is running.
43210 
43211      Meaning:  The registered physical volume unique IFD has been
43212                changed as indicated.
43213 
43214      Action:   No operator action is required.
43215 
43216 
43217                [volume_registration_mgr_.pl1]
43218                volume_registration_mgr_$change_pvr:      Couldn't
43219                {delete | create} link for  {old | new} {PV name |
43220                PVID}.  (GROUP_ID) ERROR_MESSAGE
43221 
43222 
43223 
43224 volume_registration_mgr_$change_^H7p^H4v^H6r           08/03/23     MR12.7^L
43225 
43226 
43227      Stream:   BOS Typewriter.
43228 
43229      Time:     While system is running.
43230 
43231      Meaning:  A link for a database segment residing in the root
43232                directory could  not be created in  >lv.  This may
43233                make some registration data inaccessible.
43234 
43235      Action:   Contact the system programming staff.
43236 
43237 
43238                [volume_registration_mgr_.pl1]
43239                volume_registration_mgr_$change_pvr:    PV   entry
43240                missing from database "pv.PVNAME".  (GROUP_ID)
43241 
43242 
43243      Stream:   BOS Typewriter.
43244 
43245      Time:     While system is running.
43246 
43247      Meaning:  This indicates a logic error in the supervisor, or
43248                CPU or memory hardware problems.  An entry for the
43249                specified  PV  could  not  be  found  in  the data
43250                segment although an addname  for that PV exists on
43251                the segment entry.
43252 
43253      Action:   Contact the system programming staff.
43254 
43255 
43256                [volume_registration_mgr_.pl1]
43257                volume_registration_mgr_$change_pvr:    Unable  to
43258                back out PVID change.  (GROUP_ID) ERROR_MESSAGE
43259 
43260 
43261      Stream:   BOS Typewriter.
43262 
43263      Time:     While system is running.
43264 
43265      Meaning:  While   making  changes   to  the   registered  PV
43266                attributes an  error was encountered.   The module
43267                attempts to remove any  work already done on other
43268                attributes.   For reasons  given in  ERROR_MESSAGE
43269                the PVID change could not be removed.
43270 
43271      Action:   Contact the system programming staff.
43272 
43273 
43274                [volume_registration_mgr_.pl1]
43275                volume_registration_mgr_$change_pvr:    Unexpected
43276                trouble  changing  name  "pv.PVNAME".   (GROUP_ID)
43277                ERROR_MESSAGE
43278 
43279 
43280 
43281 
43282 volume_registration_mgr_$change_^H7p^H4v^H7r           08/03/23     MR12.7^L
43283 
43284 
43285      Stream:   BOS Typewriter.
43286 
43287      Time:     While system is running.
43288 
43289      Meaning:  While   making  changes   to  the   registered  PV
43290                attributes an  error was encountered.   The module
43291                attempts to remove any  work already done on other
43292                attributes.   For reasons  given in  ERROR_MESSAGE
43293                the PV name change could not be removed.
43294 
43295      Action:   Contact the system programming staff.
43296 
43297 
43298                [volume_registration_mgr_.pl1]
43299                volume_registration_mgr_$change_pvr:    Unexpected
43300                trouble  changing name  "pvid.UNIQUE".  (GROUP_ID)
43301                ERROR_MESSAGE
43302 
43303 
43304      Stream:   BOS Typewriter.
43305 
43306      Time:     While system is running.
43307 
43308      Meaning:  An  unexpected state  made the  program unable  to
43309                change  the database  name associated  with the PV
43310                unique ID.
43311 
43312      Action:   Contact the system programming staff.
43313 
43314 
43315                [volume_registration_mgr_.pl1]
43316                volume_registration_mgr_$check_volume_registration:
43317                ERROR_MESSAGE.  PATH
43318 
43319 
43320      Stream:   BOS Typewriter.
43321 
43322      Time:     System Intialization.
43323 
43324      Meaning:  An error occurred when  trying to reclassify a new
43325                lv.** seg as a multi-class system segment.
43326 
43327      Action:   Contact the system programming staff.
43328 
43329 
43330                [volume_registration_mgr_.pl1]
43331                volume_registration_mgr_$check_volume_registration:
43332                Code N.  lv.LVNAME  disagreed with disk_table.  It
43333                was rebuilt.
43334 
43335 
43336      Stream:   BOS Typewriter.
43337 
43338 
43339 
43340 volume_registration_mgr_$check_v^H7o^H48^Hlume_registrat^H08^Hio^H/n^H03/23     MR12.7^L
43341 
43342 
43343      Time:     System Intialization.
43344 
43345      Meaning:  When the system is  bootloaded, it checks the list
43346                of  packs  which  were  mounted  during  the  last
43347                bootload to  make sure that  each one has  a valid
43348                logical  and  physical  volume  registration.  The
43349                registration   file   lv.LVNAME   was   found  but
43350                disagreed  with  the  disk_table_,  and  so it was
43351                corrected.   The  meaning  of  the  codes  can  be
43352                determined      from      the      listing      of
43353                volume_registration_mgr_; it is rarely important.
43354 
43355      Action:   Use  list_vol_registration to  examine the  remade
43356                registration,     and      correct     it     with
43357                change_vol_registration if necessary.
43358 
43359 
43360 
43361                [volume_registration_mgr_.pl1]
43362                volume_registration_mgr_$check_volume_registration:
43363                ERROR_MESSAGE.  Cannot add SysAdmin access to >lv.
43364 
43365 
43366      Stream:   BOS Typewriter.
43367 
43368      Time:     System Intialization.
43369 
43370      Meaning:  After creating a new  >lv directory, an attempt is
43371                made to  add "sma" access for  *.SysAdmin.*.  This
43372                failed.
43373 
43374      Action:   Contact the system programming staff.
43375 
43376 
43377                [volume_registration_mgr_.pl1]
43378                volume_registration_mgr_$check_volume_registration:
43379                ERROR_MESSAGE.  Cannot make mdcs for LVNAME
43380 
43381 
43382      Stream:   BOS Typewriter.
43383 
43384      Time:     System Intialization.
43385 
43386      Meaning:  When the system is  bootloaded, it checks the list
43387                of  packs  which  were  mounted  during  the  last
43388                bootload to  make sure that  each one has  a valid
43389                logical  and  physical  volume  registration.   An
43390                error  occurred while  reconstructing LVNAME.mdcs.
43391                Operation  on master   directories for  LVNAME may
43392                encounter problems.
43393 
43394      Action:   Contact the system programming staff._sa
43395 
43396 
43397 
43398 volume_registration_mgr_$check_v^H7o^H49^Hlume_registrat^H08^Hio^H/n^H03/23     MR12.7^L
43399 
43400 
43401 
43402 
43403                [volume_registration_mgr_.pl1]
43404                volume_registration_mgr_$check_volume_registration:
43405                ERROR_MESSAGE.  cannot re-create >lv
43406 
43407 
43408      Stream:   BOS Typewriter.
43409 
43410      Time:     System Intialization.
43411 
43412      Meaning:  When the system is  bootloaded, it checks the list
43413                of  packs  which  were  mounted  during  the  last
43414                bootload to  make sure that  each one has  a valid
43415                logical and physical  volume registration.  If the
43416                registration  does  not  exist,  the  registration
43417                files are reconstructed.  These registration files
43418                reside in the directory  >lv, which is also remade
43419                if it was lost or did not exist.
43420 
43421                This message indicates that  there is a problem in
43422                re-creating >lv.  Other error messages will follow
43423                and reregistration will fail.
43424 
43425      Action:   Contact the system programming staff.
43426 
43427 
43428                [volume_registration_mgr_.pl1]
43429                volume_registration_mgr_$check_volume_registration:
43430                ERROR_MESSAGE.  Cannot reregister lv LVNAME
43431 
43432 
43433      Stream:   BOS Typewriter.
43434 
43435      Time:     System Intialization.
43436 
43437      Meaning:  When the system is  bootloaded, it checks the list
43438                of  packs  which  were  mounted  during  the  last
43439                bootload to  make sure that  each one has  a valid
43440                logical and physical volume registration.
43441 
43442                The  system  was  unable  to  append  a branch for
43443                >lv>lv.LVNAME.  The logical volume will have to be
43444                re-registered manually.
43445 
43446      Action:   Use    the    add_vol_registration    command   to
43447                re-register the volume manually.
43448 
43449 
43450 
43451                [volume_registration_mgr_.pl1]
43452                volume_registration_mgr_$check_volume_registration:
43453                ERROR_MESSAGE.  Cannot reregister pv PVNAME
43454 
43455 
43456 volume_registration_mgr_$check_v^H7o^H50^Hlume_registrat^H08^Hio^H/n^H03/23     MR12.7^L
43457 
43458 
43459      Stream:   BOS Typewriter.
43460 
43461      Time:     System Intialization.
43462 
43463      Meaning:  When the system is  bootloaded, it checks the list
43464                of  packs  which  were  mounted  during  the  last
43465                bootload to  make sure that  each one has  a valid
43466                logical and physical volume registration.
43467 
43468                The system was unable  to re-register the physical
43469                volume  PVNAME because   its logical  volume entry
43470                could not be located in the old disk_table and its
43471                physical  volume registration   file could  not be
43472                found.  The  volume will have to  be re-registered
43473                manually.
43474 
43475      Action:   If  PVNAME   is  garbage,  ignore   this  message.
43476                Otherwise, use add_vol_registration to re-register
43477                the volume.
43478 
43479 
43480 
43481                [volume_registration_mgr_.pl1]
43482                volume_registration_mgr_$check_volume_registration:
43483                ERROR_MESSAGE.   Cant  add   name  lvid.UNIQUE  to
43484                lv.LVNAME
43485 
43486 
43487      Stream:   BOS Typewriter.
43488 
43489      Time:     System Intialization.
43490 
43491      Meaning:  When the system is  bootloaded, it checks the list
43492                of  packs  which  were  mounted  during  the  last
43493                bootload to  make sure that  each one has  a valid
43494                logical  and  physical  volume  registration.  The
43495                registration  file  for  LVNAME  did  not have the
43496                additional name constructed from the volume unique
43497                ID, and an error was  discovered trying to add it.
43498                If this name is on another segment, confusion will
43499                result.
43500 
43501      Action:   Contact the system programming staff.  Enter admin
43502                mode and do a "list >lv>**" command.
43503 
43504 
43505 
43506                [volume_registration_mgr_.pl1]
43507                volume_registration_mgr_$check_volume_registration:
43508                ERROR_MESSAGE.  Cant add name pv.PVNAME to LVNAME
43509 
43510 
43511      Stream:   BOS Typewriter.
43512 
43513 
43514 volume_registration_mgr_$check_v^H7o^H51^Hlume_registrat^H08^Hio^H/n^H03/23     MR12.7^L
43515 
43516 
43517      Time:     System Intialization.
43518 
43519      Meaning:  When the system is  bootloaded, it checks the list
43520                of  packs  which  were  mounted  during  the  last
43521                bootload to  make sure that  each one has  a valid
43522                logical and physical volume registration.
43523 
43524                An  error occurred  adding the  name pv.PVNAME  to
43525                >lv>lv.LVNAME.   If  this  name  is  missing or on
43526                another segment, confusion will result.
43527 
43528      Action:   Contact the system programming staff.  Enter admin
43529                mode and do a "list >lv>**" command.
43530 
43531 
43532 
43533                [volume_registration_mgr_.pl1]
43534                volume_registration_mgr_$check_volume_registration:
43535                ERROR_MESSAGE.   Cant  add   name  pvid.UNIQUE  to
43536                LVNAME
43537 
43538 
43539      Stream:   BOS Typewriter.
43540 
43541      Time:     System Intialization.
43542 
43543      Meaning:  When the system is  bootloaded, it checks the list
43544                of  packs  which  were  mounted  during  the  last
43545                bootload to  make sure that  each one has  a valid
43546                logical  and  physical  volume  registration.   An
43547                error  occurred  adding  the  name  pvid.UNIQUE to
43548                >lv>lv.LVNAME.  If  this name is missing  or is on
43549                another segment, confusion will result.
43550 
43551      Action:   Contact the system programming staff.  Enter admin
43552                mode and do a "list >lv>**" command.
43553 
43554 
43555 
43556                [volume_registration_mgr_.pl1]
43557                volume_registration_mgr_$check_volume_registration:
43558                ERROR_MESSAGE.  Putting LV dir on RPV
43559 
43560 
43561      Stream:   BOS Typewriter.
43562 
43563      Time:     System Intialization.
43564 
43565      Meaning:  When the system is  bootloaded, it checks the list
43566                of  packs  which  were  mounted  during  the  last
43567                bootload to  make sure that  each one has  a valid
43568                logical  and physical volume  registration.  While
43569                re-creating >lv,  the system attempted to  set the
43570 
43571 
43572 volume_registration_mgr_$check_v^H7o^H52^Hlume_registrat^H08^Hio^H/n^H03/23     MR12.7^L
43573 
43574 
43575                directory flag  which means "RPV only"  and failed
43576                to do so.
43577 
43578      Action:   Contact the system programming staff.
43579 
43580 
43581                [volume_registration_mgr_.pl1]
43582                volume_registration_mgr_$check_volume_registration:
43583                Registration   for  PVNAME   was  different   from
43584                disk_table
43585 
43586 
43587      Stream:   BOS Typewriter.
43588 
43589      Time:     System Intialization.
43590 
43591      Meaning:  When the system is  bootloaded, it checks the list
43592                of  packs  which  were  mounted  during  the  last
43593                bootload to  make sure that  each one has  a valid
43594                logical  and  physical  volume  registration.  The
43595                physical volume  ID or model number  of PVNAME was
43596                wrong in the registration files and was corrected.
43597 
43598      Action:   Contact the system programming staff._sa
43599 
43600 
43601                [volume_registration_mgr_.pl1]
43602                volume_registration_mgr_$check_volume_registration:
43603                Reregistered pv PVNAME pvid WWWW in lv LVNAME
43604 
43605 
43606      Stream:   BOS Typewriter.
43607 
43608      Time:     System Intialization.
43609 
43610      Meaning:  When the system is  bootloaded, it checks the list
43611                of  packs  which  were  mounted  during  the  last
43612                bootload to  make sure that  each one has  a valid
43613                logical   and    physical   volume   registration.
43614                Registration   for  PVNAME    was  added   to  the
43615                registration file for LVNAME.
43616 
43617                This  message  is  always  produced  for  the root
43618                physical  volume, rpv, during  a cold boot  of the
43619                Multics hierarchy.
43620 
43621      Action:   Use the list_vol_registration command to check the
43622                registration.   If  necessary,   correct  it  with
43623                change_vol_registration.
43624 
43625 
43626 
43627                [volume_registration_mgr_.pl1]
43628 
43629 
43630 volume_registration_mgr_$check_v^H7o^H53^Hlume_registrat^H08^Hio^H/n^H03/23     MR12.7^L
43631 
43632 
43633                volume_registration_mgr_$check_volume_registration:
43634                Reregistered TYPE lv LVNAME lvid WWWW
43635 
43636 
43637      Stream:   BOS Typewriter.
43638 
43639      Time:     System Intialization.
43640 
43641      Meaning:  When the system is  bootloaded, it checks the list
43642                of  packs  which  were  mounted  during  the  last
43643                bootload to  make sure that  each one has  a valid
43644                logical  and  physical  volume  registration.  The
43645                registration file for LVNAME did not exist and was
43646                reconstructed.
43647 
43648                This  message  is  always  produced  for  the root
43649                logical volume  during a cold boot  of the Multics
43650                hierarchy.
43651 
43652      Action:   Use the list_vol_registration  command to list the
43653                registration and  check it against  the re-created
43654                copy.  Correct it  with change_vol_registration if
43655                necessary.
43656 
43657 
43658 
43659                [volume_registration_mgr_.pl1]
43660                volume_registration_mgr_$delete_lvr:    Could  not
43661                remove {PV name | PVID  | LV name | LVID} database
43662                link.  (GROUP_ID) ERROR_MESSAGE
43663 
43664 
43665      Stream:   BOS Typewriter.
43666 
43667      Time:     While system is running.
43668 
43669      Meaning:  An  unexpected state   prevented the  program from
43670                removing the database links  associated with an LV
43671                just  deleted.   The  links  (in  >lv)  should  be
43672                removed by hand using Ring_1_Repair.
43673 
43674      Action:   Contact the system programming staff.
43675 
43676 
43677                [volume_registration_mgr_.pl1]
43678                volume_registration_mgr_$delete_lvr:   Deleted  LV
43679                "LVNAME".  (GROUP_ID)
43680 
43681 
43682      Stream:   Logged in SYSERR log.
43683 
43684      Time:     While system is running.
43685 
43686 
43687 
43688 volume_registration_mgr_$delete_^H7l^H5v^H4r           08/03/23     MR12.7^L
43689 
43690 
43691      Meaning:  The registration  for the spcified  logical volume
43692                has been removed.
43693 
43694      Action:   No operator action is required.
43695 
43696 
43697                [volume_registration_mgr_.pl1]
43698                volume_registration_mgr_$delete_lvr:   Deleted  PV
43699                "PVNAME" from LV "LVNAME".  (GROUP_ID)
43700 
43701 
43702      Stream:   Logged in SYSERR log.
43703 
43704      Time:     While system is running.
43705 
43706      Meaning:  The registration for the specified physical volume
43707                was  removed  while  removing  the  entire logical
43708                volume registration.
43709 
43710      Action:   No operator action is required.
43711 
43712 
43713                [volume_registration_mgr_.pl1]
43714                volume_registration_mgr_$delete_lvr:    Unable  to
43715                delete     MDCS     "LVNAME.mdcs".      (GROUP_ID)
43716                ERROR_MESSAGE
43717 
43718 
43719      Stream:   BOS Typewriter.
43720 
43721      Time:     While system is running.
43722 
43723      Meaning:  After  deleting  the  registration  for  a logical
43724                volume  the  module  was   unable  to  delete  the
43725                corresponding  master  directory  control database
43726                indicated in the message.
43727 
43728      Action:   Contact the system programming staff.
43729 
43730 
43731                [volume_registration_mgr_.pl1]
43732                volume_registration_mgr_$delete_pvr:    Could  not
43733                remove {PV name | PVID} database link.  (GROUP_ID)
43734                ERROR_MESSAGE
43735 
43736 
43737      Stream:   BOS Typewriter.
43738 
43739      Time:     While system is running.
43740 
43741      Meaning:  An  unexpected  state  prevented  the  removal  of
43742                database links  associated with a  PV registration
43743 
43744 
43745 
43746 volume_registration_mgr_$delete_^H7p^H5v^H5r           08/03/23     MR12.7^L
43747 
43748 
43749                that  was  just  deleted.   The  links  should  be
43750                deleted by hand using Ring_1_Repair.
43751 
43752      Action:   Contact the system programming staff.
43753 
43754 
43755                [volume_registration_mgr_.pl1]
43756                volume_registration_mgr_$delete_pvr:   Deleted  PV
43757                "PVNAME" from LV "LVNAME".  (GROUP_ID)
43758 
43759 
43760      Stream:   Logged in SYSERR log.
43761 
43762      Time:     While system is running.
43763 
43764      Meaning:  The  registration  fo  the  specified  PV has been
43765                deleted.
43766 
43767      Action:   No operator action is required.
43768 
43769 
43770                [volume_registration_mgr_.pl1]
43771                volume_registration_mgr_$delete_pvr:    PV   entry
43772                missing from database "pv.PVNAME".  (GROUP_ID)
43773 
43774 
43775      Stream:   BOS Typewriter.
43776 
43777      Time:     While system is running.
43778 
43779      Meaning:  This indicates a logic error in the supervisor, or
43780                CPU  or memory  hardware problems.   The entry for
43781                the  specified  PV  could  not  be  located in the
43782                database segment although its  name appears on the
43783                segment entry.
43784 
43785      Action:   Contact the system programming staff.
43786 
43787 
43788                [volume_registration_mgr_.pl1]
43789                volume_registration_mgr_$delete_pvr:      Trimming
43790                registration.  (GROUP_ID) ERROR_MESSAGE
43791 
43792 
43793      Stream:   BOS Typewriter.
43794 
43795      Time:     While system is running.
43796 
43797      Meaning:  An  unexpected state  prevented the  trimming of a
43798                registration  database  segment.   This  will  not
43799                hinder subsystem performance.
43800 
43801      Action:   Contact the system programming staff.
43802 
43803 
43804 volume_registration_mgr_$delete_^H7p^H5v^H6r           08/03/23     MR12.7^L
43805 
43806 
43807 
43808 
43809                [volume_registration_mgr_.pl1]
43810                volume_registration_mgr_$delete_pvr:    Unable  to
43811                replace  database  name  "pv.PVNAME".   (GROUP_ID)
43812                ERROR_MESSAGE
43813 
43814 
43815      Stream:   BOS Typewriter.
43816 
43817      Time:     While system is running.
43818 
43819      Meaning:  This indicates a logic error in the supervisor, or
43820                CPU or  memory hardware problems.   While deleting
43821                the  registration for  the specified  PV an  error
43822                occurred.   The  program   attempts  to  undo  any
43823                changes  to  "leave  things  as  they  were."  The
43824                attempt to put back  the database segment name (as
43825                indicated) failed.
43826 
43827      Action:   Contact the system programming staff.
43828 
43829 
43830                [volume_registration_mgr_.pl1]
43831                volume_registration_mgr_$ENTRY:  Attempting to get
43832                second temp segment.  (GROUP_ID)
43833 
43834 
43835      Stream:   BOS Typewriter.
43836 
43837      Time:     While system is running.
43838 
43839      Meaning:  This indicates a logic error in the supervisor, or
43840                CPU or memory  hardware problems.  All entrypoints
43841                to  volume_registration_mgr_ require  at most  one
43842                temporary segment.
43843 
43844      Action:   Contact the system programming staff.
43845 
43846 
43847                [volume_registration_mgr_.pl1]
43848                volume_registration_mgr_$ENTRY:      Database    -
43849                {lvid.UNIQUE   |   lv.LVNAME   |   pvid.UNIQUE   |
43850                pv.PVNAME}.   (GROUP_ID) Segment already  known to
43851                process.
43852 
43853 
43854      Stream:   BOS Typewriter.
43855 
43856      Time:     While system is running.
43857 
43858      Meaning:  This indicates a logic error in the supervisor, or
43859                CPU or  memory hardware problems.  The  inner ring
43860 
43861 
43862 volume_registration_mgr_$ENTRY 757            08/03/23     MR12.7^L
43863 
43864 
43865                module   always  trerminates  references   to  the
43866                database segments  upon return to its  caller.  It
43867                found the specified segment already initiated upon
43868                entry to the specified routine.
43869 
43870      Action:   Contact the system programming staff.
43871 
43872 
43873                [volume_registration_mgr_.pl1]
43874                volume_registration_mgr_$ENTRY:  Unable to release
43875                temp segment.  (GROUP_ID) ERROR_MESSAGE
43876 
43877 
43878      Stream:   BOS Typewriter.
43879 
43880      Time:     While system is running.
43881 
43882      Meaning:  This indicates a logic error in the supervisor, or
43883                CPU or memory  hardware problems.  Some unexpected
43884                state is preventing the  module from releasing its
43885                temporary segment.
43886 
43887      Action:   Contact the system programming staff.
43888 
43889 
43890                [volume_registration_mgr_.pl1]
43891                volume_registration_mgr_$ENTRY:      Unable     to
43892                terminate    database    reference.     (GROUP_ID)
43893                ERROR_MESSAGE
43894 
43895 
43896      Stream:   BOS Typewriter.
43897 
43898      Time:     While system is running.
43899 
43900      Meaning:  This indicates a logic error in the supervisor, or
43901                CPU or memory  hardware problems.  Some unexpected
43902                state  is preventing  the module  from terminating
43903                reference to a database segment.
43904 
43905      Action:   Contact the system programming staff.
43906 
43907 
43908                [volume_registration_mgr_.pl1]
43909                volume_registration_mgr_$ENTRY:   Unexpected error
43910                occurred.   Database  may  be  in  an inconsistant
43911                state.  (GROUP_ID)
43912 
43913 
43914      Stream:   BOS Typewriter.
43915 
43916      Time:     While system is running.
43917 
43918 
43919 
43920 volume_registration_mgr_$ENTRY 758            08/03/23     MR12.7^L
43921 
43922 
43923      Meaning:  This indicates a logic error in the supervisor, or
43924                CPU or memory  hardware problems.  Some unexpected
43925                condition  was  signalled  while  the  module  was
43926                executing.
43927 
43928      Action:   Contact the system programming staff.
43929 
43930 
43931                [volume_registration_mgr_.pl1]
43932                volume_registration_mgr_$find:   PV entry  missing
43933                from "pv.PVNAME".  (GROUP_ID)
43934 
43935 
43936      Stream:   BOS Typewriter.
43937 
43938      Time:     While system is running.
43939 
43940      Meaning:  This indicates a logic error in the supervisor, or
43941                CPU  or memory  hardware problems.   The entry for
43942                the  specified  PV  could  not  be  found  in  the
43943                registration  database segment  although the  name
43944                appears on the segment's entry.
43945 
43946      Action:   Contact the system programming staff.
43947 
43948 
43949                [volume_registration_mgr_.pl1]
43950                volume_registration_mgr_$find_volname:   PV  entry
43951                not found in database "pvid.UNIQUE".  (GROUP_ID)
43952 
43953 
43954      Stream:   BOS Typewriter.
43955 
43956      Time:     While system is running.
43957 
43958      Meaning:  This indicates a logic error in the supervisor, or
43959                CPU  or memory  hardware problems.   The entry for
43960                the  specified  PV  could  not  be  found  in  the
43961                registration  database segment  although the  name
43962                appears on the segment's entry.
43963 
43964      Action:   Contact the system programming staff.
43965 
43966 
43967                [volume_registration_mgr_.pl1]
43968                volume_registration_mgr_$get_access:     ACS   not
43969                segment - "PATH".  (GROUP_ID)
43970 
43971 
43972      Stream:   BOS Typewriter.
43973 
43974      Time:     While system is running.
43975 
43976 
43977 
43978 volume_registration_mgr_$get_acc^H7e^H5s^H9s           08/03/23     MR12.7^L
43979 
43980 
43981      Meaning:  The   ACS   indicated   in   the   logical  volume
43982                registration  database  is  not  a  segment.   The
43983                database   entry   should   be   corrected   using
43984                "change_volume_registration".
43985 
43986      Action:   Contact the system programming staff._sa
43987 
43988 
43989                [volume_registration_mgr_.pl1]
43990                volume_registration_mgr_$get_access:  Bad ACS path
43991                in database "lv.LVNAME".  (GROUP_ID) ERROR_MESSAGE
43992 
43993 
43994      Stream:   BOS Typewriter.
43995 
43996      Time:     While system is running.
43997 
43998      Meaning:  This indicates a logic error in the supervisor, or
43999                CPU or memory hardware problems.  The ACS pathname
44000                entry  in the  LVNAME database  is illegal.   This
44001                should  not  happen  normally  because  the ring-1
44002                primitives  check all  paths before  entering them
44003                into the database.
44004 
44005      Action:   Contact the system programming staff.
44006 
44007 
44008                [volume_registration_mgr_.pl1]
44009                volume_registration_mgr_$pvname_info:    PV  entry
44010                not found in database "pv.PVNAME".  (GROUP_ID)
44011 
44012 
44013      Stream:   BOS Typewriter.
44014 
44015      Time:     While system is running.
44016 
44017      Meaning:  This indicates a logic error in the supervisor, or
44018                CPU  or memory  hardware problems.   The entry for
44019                the  specified  PV  could  not  be  found  in  the
44020                registration  database segment  although the  name
44021                appears on the segment's entry.
44022 
44023      Action:   Contact the system programming staff.
44024 
44025 
44026                [volume_registration_mgr_.pl1]
44027                volume_registration_mgr_$read_pvr:     PV    entry
44028                missing from database "pv.PVNAME".  (GROUP_ID)
44029 
44030 
44031      Stream:   BOS Typewriter.
44032 
44033      Time:     While system is running.
44034 
44035 
44036 volume_registration_mgr_$read_pv^H7r^H60            08/03/23     MR12.7^L
44037 
44038 
44039      Meaning:  This indicates a logic error in the supervisor, or
44040                CPU  or memory  hardware problems.   The entry for
44041                the  specified  PV  could  not  be  found  in  the
44042                registration  database segment  although the  name
44043                appears on the segment's entry.
44044 
44045      Action:   Contact the system programming staff.
44046 
44047 
44048                [vrm_lock_.pl1]
44049                vrm_lock_$lock:  LOCK ERROR MESSAGE.
44050 
44051 
44052      Stream:   Logged in SYSERR log.
44053 
44054      Time:     While system is running.
44055 
44056      Meaning:  A  logical  volume  registration  operation failed
44057                because of a problem with the vrm control lock.
44058 
44059      Action:   No operator action is required.
44060 
44061 
44062                [vrm_lock_.pl1]
44063                vrm_lock_$unlock:  LOCK ERROR MESSAGE.
44064 
44065 
44066      Stream:   Logged in SYSERR log.
44067 
44068      Time:     While system is running.
44069 
44070      Meaning:  At the  completion ofa logical  volume registratin
44071                operation,  some error  occured unlocking  the vrm
44072                control lock.
44073 
44074      Action:   No operator action is required.
44075 
44076 
44077                [vrm_lock_.pl1]
44078                vrm_lock_$vrm_data_init:     Unable   to    create
44079                PATHNAME.  REASON.
44080 
44081 
44082      Stream:   BOS Typewriter.
44083 
44084      Time:     System Intialization.
44085 
44086      Meaning:  Logical  volume  registration  control  (vrm)  was
44087                unable to create the  segment PATHNAME, to be used
44088                for  the vrm control  lock, for the  REASON given.
44089                Subsequent  logical  volume  registration  control
44090                operations may fail.
44091 
44092 
44093 
44094 vrm_lock_$vrm_data_init        761            08/03/23     MR12.7^L
44095 
44096 
44097      Action:   No operator action is required.
44098 
44099 
44100                [vrm_lock_.pl1]
44101                vrm_lock_$vrm_data_init:   Unable   to  reclassify
44102                PATHNAME.  REASON.
44103 
44104 
44105      Stream:   BOS Typewriter.
44106 
44107      Time:     System Intialization.
44108 
44109      Meaning:  Logical volume registration  control was unable to
44110                reclassify  the  segment  PATHNAME  to  its proper
44111                access class  for the REASON given.   This segment
44112                is to be used  for the logical volume registration
44113                control    lock.    Subsequent    logical   volume
44114                registration control operations may fail.
44115 
44116 
44117 
44118                [vrm_lock_.pl1]
44119                vrm_lock_$vrm_data_init:    Unable   to   truncate
44120                PATHNAME.  REASON.
44121 
44122 
44123      Stream:   BOS Typewriter.
44124 
44125      Time:     System Intialization.
44126 
44127      Meaning:  Logical volume registration  control was unable to
44128                truncate  the  segment  PATHNAME  for  the  REASON
44129                given.  This segment is to be used for the logical
44130                volume  registration   control  lock.   Subsequent
44131                logical volume registration control operations may
44132                fail.
44133 
44134      Action:   No operator action is required.
44135 
44136 
44137                [vrm_lock_.pl1]
44138                vrm_lock_:  Unable to initiate PATHNAME.  REASON.
44139 
44140 
44141      Stream:   Logged in SYSERR log.
44142 
44143      Time:     While system is running.
44144 
44145      Meaning:  Logical  volume  registration  control  (vrm)  was
44146                unable  to initiate  PATHNAME, which  contains the
44147                vrm control lock, because  of REASON.  The logical
44148                volume  registration  control  operation requested
44149                was not performed.
44150 
44151 
44152 vrm_lock_                      762            08/03/23     MR12.7^L
44153 
44154 
44155      Action:   No operator action is required.
44156 
44157 
44158                [vtoc_interrupt.pl1]
44159                vtoc_interrupt:  bad core address
44160 
44161 
44162      Stream:   BOS Typewriter (Crashes system)
44163 
44164      Time:     While system is running.
44165 
44166      Meaning:  The disk dim reported a main memory address to the
44167                VTOC  manager which  was  not  in the  VTOC buffer
44168                segment,  or was  not designating  a legal  buffer
44169                boundary.   This indicates  a logic  error in  the
44170                supervisor, or CPU or memory hardware problems.
44171 
44172      Action:   Follow normal recovery procedures.
44173 
44174 
44175                [vtoc_interrupt.pl1]
44176                vtoc_interrupt:  Buffer not os at interrupt
44177 
44178 
44179      Stream:   BOS Typewriter (Crashes system)
44180 
44181      Time:     While system is running.
44182 
44183      Meaning:  An I/O  completion was received for  a VTOC buffer
44184                which  was apparently   not undergoing  I/O.  This
44185                indicates a logic error  in the supervisor, or CPU
44186                or memory hardware problems.
44187 
44188      Action:   Follow normal recovery procedures.
44189 
44190 
44191                [vtoc_interrupt.pl1]
44192                vtoc_interrupt:   Write  error  on  dskX_NN  vtocx
44193                XXXXXX
44194 
44195 
44196      Stream:   Logged in SYSERR log.
44197 
44198      Time:     While system is running.
44199 
44200      Meaning:  A bad I/O status was  received by the VTOC manager
44201                for a  write operation.  The  unwritten vtoce-part
44202                will remain in main  memory until the next attempt
44203                is made  to write it  out, or demount  or shutdown
44204                time.  Too  many of these can cause  the system to
44205                crash.
44206 
44207      Action:   No operator action is required.
44208 
44209 
44210 vtoc_man                       763            08/03/23     MR12.7^L
44211 
44212 
44213 
44214 
44215                [vtoc_man.pl1]
44216                vtoc_man:  Attempt to write less than entire VTOCE
44217                to MODEL device.
44218 
44219 
44220      Stream:   BOS Typewriter (Crashes system)
44221 
44222      Time:     While system is running.
44223 
44224      Meaning:  An attempt  has been made  to write less  than the
44225                entire VTOCE to a  device MODEL that only supports
44226                a 512_word  sector.  For these devices  the entire
44227                192  word VTOCE  must be  written at  one time.  A
44228                likely software error n VTOC buffer management.
44229 
44230      Action:   Follow normal recovery procedures.
44231 
44232 
44233                [vtoc_man.pl1]
44234                vtoc_man:  Buffer out-of-service during cleanup
44235 
44236 
44237      Stream:   BOS Typewriter (Crashes system)
44238 
44239      Time:     When a volume is  being demounted or during system
44240                shutdown.
44241 
44242      Meaning:  A likely software error  in VTOC buffer management
44243                which caused an inconsistency in the VTOC buffer.
44244 
44245      Action:   Follow normal recovery procedures.
44246 
44247 
44248                [vtoc_man.pl1]
44249                vtoc_man:  buffer out-of-service on write
44250 
44251 
44252      Stream:   BOS Typewriter (Crashes system)
44253 
44254      Time:     While system is running.
44255 
44256      Meaning:  A   likely   software   problem   has   caused  an
44257                inconsistency in the VTOC buffer.
44258 
44259      Action:   Follow normal recovery procedures.
44260 
44261 
44262                [vtoc_man.pl1]
44263                vtoc_man:   Hot  buffer  abandoned  during cleanup
44264                vtocx XXXXX dskX_NN{s}
44265 
44266 
44267 
44268 vtoc_man                       764            08/03/23     MR12.7^L
44269 
44270 
44271      Stream:   Logged in SYSERR log.
44272 
44273      Time:     When a volume is  being demounted or during system
44274                shutdown.
44275 
44276      Meaning:  An update  to VTOCE XXXXX on  dskX_NN{s} could not
44277                be completed due to I/O  errors.  The VTOCE may be
44278                inconsistent or damaged.
44279 
44280      Action:   The   VTOCE  should   be  examined   by  means  of
44281                dump_vtoce  the next  time the  volume is  online.
44282                Any  inconsistency can  be corrected  by a  volume
44283                salvage.
44284 
44285 
44286 
44287                [vtoc_man.pl1]
44288                vtoc_man:  Invalid free vtocx XXXXX on dskX_NN{s}
44289 
44290 
44291      Stream:   Logged in SYSERR log.
44292 
44293      Time:     While system is running.
44294 
44295      Meaning:  A  free VTOCE was  allocated which has  an invalid
44296                VTOCE index for the volume.  This is indicative of
44297                damage to volume  control structures.  This damage
44298                can be corrected by a volume salvage.
44299 
44300      Action:   No operator action is required.
44301 
44302 
44303                [vtoc_man.pl1]
44304                vtoc_man:  Invalid write
44305 
44306 
44307      Stream:   BOS Typewriter (Crashes system)
44308 
44309      Time:     While system is running.
44310 
44311      Meaning:  A  likely software  error in  the calling sequence
44312                for output of a VTOCE.
44313 
44314      Action:   Follow normal recovery procedures.
44315 
44316 
44317                [vtoc_man.pl1]
44318                vtoc_man:  Out of buffers try number N
44319 
44320 
44321      Stream:   BOS Typewriter.
44322 
44323      Time:     While system is running.
44324 
44325 
44326 vtoc_man                       765            08/03/23     MR12.7^L
44327 
44328 
44329      Meaning:  There  may be  a disk  problem which  prevents the
44330                vtoc buffers from being  written to disk, or there
44331                may  be a  disk  tuning  problem.  The  system may
44332                crash within the next few minutes.
44333 
44334      Action:   Contact the system programming staff._sa
44335 
44336 
44337                [vtoc_man.pl1]
44338                vtoc_man:     read    reset    of    crawlout   by
44339                PERSON.PROJECT.TAG for dskX_NN{s} vtocx XXXXXX
44340 
44341 
44342      Stream:   Logged in SYSERR log.
44343 
44344      Time:     While system is running.
44345 
44346      Meaning:  The process  of PERSON.PROJECT.TAG crawled  out of
44347                ring-0  or terminated  with the  VTOC buffer  lock
44348                held.  A buffer was marked out-of-service for read
44349                to VTOCE XXXXX on dskX_NN{s}  for which no I/O had
44350                been queued.  The read I/O was abandoned.
44351 
44352      Action:   No operator action is required.
44353 
44354 
44355                [vtoc_man.pl1]
44356                vtoc_man:   UID ^=  0  in  free VTOCE  vtocx XXXXX
44357                dskX_NN{s}
44358 
44359 
44360      Stream:   Logged in SYSERR log.
44361 
44362      Time:     While system is running.
44363 
44364      Meaning:  The  contents  of  VTOCE  XXXXX  on dskX_NN{s} are
44365                incorrect, as free VTOCEs  should have a zero UID.
44366                The  system attempts  to find  another free VTOCE.
44367                This  may   indicate  damage  to   volume  control
44368                structures.   This damage  can be  corrected by  a
44369                volume salvage.
44370 
44371      Action:   No operator action is required.
44372 
44373 
44374                [vtoc_man.pl1]
44375                vtoc_man:   Update  in  progress  on  crawlout  by
44376                PERSON.PROJECT.TAG dskX_NN{s}
44377 
44378 
44379      Stream:   Logged in SYSERR log.
44380 
44381      Time:     While system is running.
44382 
44383 
44384 vtoc_man                       766            08/03/23     MR12.7^L
44385 
44386 
44387      Meaning:  The process  of PERSON.PROJECT.TAG crawled  out of
44388                ring-0  or terminated  with the  vtoc buffer  lock
44389                held  and an  update in  progress for  a VTOCE  on
44390                dskX_NN{s}.  The  VTOCE may be  inconsistent.  Any
44391                inconsistency  can   be  corrected  by   a  volume
44392                salvage.
44393 
44394      Action:   No operator action is required.
44395 
44396 
44397                [vtoc_man.pl1]
44398                vtoc_man:     Write   I/O    being   retried    by
44399                PERSON.PROJECT.TAG for dskX_NN{s} vtocx XXXXX
44400 
44401 
44402      Stream:   Logged in SYSERR log.
44403 
44404      Time:     While system is running.
44405 
44406      Meaning:  A  buffer  previously  marked  as  "hot"  is being
44407                requeued for I/O.
44408 
44409      Action:   No operator action is required.
44410 
44411 
44412                [vtoc_man.pl1]
44413                vtoc_man:   write  I/O  recovered  on  crawlout by
44414                PERSON.PROJECT.TAG for dskX_NN{s} vtocx XXXXX
44415 
44416 
44417      Stream:   Logged in SYSERR log.
44418 
44419      Time:     While system is running.
44420 
44421      Meaning:  The process  of PERSON.PROJECT.TAG crawled  out of
44422                ring-0  or terminated  with the  VTOC buffer  lock
44423                held.   A  buffer  was  marked  out-of-service for
44424                write  to VTOCE XXXXX  on dskX_NN{s} for  which no
44425                I/O had been queued.  The write I/O was requeued.
44426 
44427      Action:   No operator action is required.
44428 
44429 
44430                [vtoce_stock_man.pl1]
44431                vtoce_stock_man:   Attempt to  deposit free  vtocx
44432                YYYYYY on dskX_NN
44433 
44434 
44435      Stream:   BOS Typewriter.
44436 
44437      Time:     While system is running.
44438 
44439 
44440 
44441 
44442 vtoce_stock_man                767            08/03/23     MR12.7^L
44443 
44444 
44445      Meaning:  A VTOCE was returned to the free pool of VTOCEs on
44446                the  device indicated,  but the  VTOCE was already
44447                marked  as free.   This indicates  possible device
44448                damage.   This  damage  can   be  corrected  by  a
44449                physical volume salvage.
44450 
44451      Action:   Contact the system programming staff.
44452 
44453 
44454                [vtoce_stock_man.pl1]
44455                vtoce_stock_man:  Attempt to deposit invalid vtocx
44456                YYYYYY on dskX_NN
44457 
44458 
44459      Stream:   BOS Typewriter.
44460 
44461      Time:     While system is running.
44462 
44463      Meaning:  There was an attempt to return a free VTOCE to the
44464                pool of free VTOCEs  for the device indicated, but
44465                the  index  of  the  VTOCE  was  not  valid.  This
44466                indicates  possible damage   to the  device.  Such
44467                damage  can  be  corrected  by  a  physical volume
44468                salvage.
44469 
44470      Action:   Contact the system programming staff.
44471 
44472 
44473                [vtoce_stock_man.pl1]
44474                vtoce_stock_man:  MYLOCK of VTOC Map for dskX_NN
44475 
44476 
44477      Stream:   BOS Typewriter (Crashes system)
44478 
44479      Time:     While system is running.
44480 
44481      Meaning:  A process attempted to acquire  a lock on the VTOC
44482                Map for the device  indicated while already owning
44483                the lock.  This is probably a software error.
44484 
44485      Action:   Follow normal recovery procedures.
44486 
44487 
44488                [vtoce_stock_man.pl1]
44489                vtoce_stock_man:     PVTE    and    VTOCE    stock
44490                out-of-synch on dskX_NN
44491 
44492 
44493      Stream:   BOS Typewriter (Crashes system)
44494 
44495      Time:     While system is running.
44496 
44497 
44498 
44499 
44500 vtoce_stock_man                768            08/03/23     MR12.7^L
44501 
44502 
44503      Meaning:  There  is an   inconsistency between  the Physical
44504                Volume  Table Entry  and the  VTOCE Stock  for the
44505                device  indicated.  This   is probably  a software
44506                error.
44507 
44508      Action:   Follow normal recovery procedures.
44509 
44510 
44511                [vtoce_stock_man.pl1]
44512                vtoce_stock_man:  STACQ fails for VTOC Map lock on
44513                dskX_NN
44514 
44515 
44516      Stream:   BOS Typewriter (Crashes system)
44517 
44518      Time:     While system is running.
44519 
44520      Meaning:  A process  was unable to unlock the  VTOC Map lock
44521                for  the  device  indicated.   This  is probably a
44522                hardware  failure, either  in the  CPU or  in main
44523                memory.
44524 
44525      Action:   Follow normal recovery procedures.
44526 
44527 
44528                [vtoce_stock_man.pl1]
44529                vtoce_stock_man:   VTOCE   stock  inconsistent  on
44530                dskX_NN
44531 
44532 
44533      Stream:   BOS Typewriter (Crashes system)
44534 
44535      Time:     While system is running.
44536 
44537      Meaning:  There is an internal inconsistency in the stock of
44538                free  VTOCES  on  the  device  indicated.  This is
44539                probably a software malfunction.
44540 
44541      Action:   Follow normal recovery procedures.
44542 
44543 
44544                [tc_init.pl1]
44545                Warning:   You are running  an old version  of the
44546                DPS8M  simulator.   Please  update  to  VERSION or
44547                later.  See https://dps8m.gitlab.io/ for details.
44548 
44549 
44550 
44551      Stream:   BOS Typewriter (sounds beeper)
44552 
44553      Time:     When the bootload CPU is  a DPS8 is "added" to the
44554                system.
44555 
44556 
44557 
44558 Warning                        769            08/03/23     MR12.7^L
44559 
44560 
44561      Meaning:  VERSION specifies the version of a DPS8M simulator
44562                that is  known to work correctly  with the running
44563                version of Multics.
44564 
44565      Action:   No operator action is required.
44566 
44567 
44568                [wdx.pl1]
44569                wdx:   ERRORCODE Unable  to send  wakeup on master
44570                channel.
44571 
44572 
44573      Stream:   BOS Typewriter.
44574 
44575      Time:     While system is running.
44576 
44577      Meaning:  The  ring-1  logical  volume  mount  software  was
44578                unable to send a wakeup to the ring-4 software for
44579                the  reason indicated.    Some mount  requests may
44580                have been lost.
44581 
44582      Action:   Contact the system programming staff._sa
44583 
44584 
44585                [wire_proc.pl1]
44586                wire_proc:  lock not locked
44587 
44588 
44589      Stream:   BOS Typewriter (Crashes system)
44590 
44591      Time:     While system is running.
44592 
44593      Meaning:  The  lock  on  temp-wiring  in  the  SST was found
44594                unlocked at the time an attempt was made to unlock
44595                it.   The SST  may be  damaged.  This  indicates a
44596                logic  error in the  supervisor, or CPU  or memory
44597                hardware problems.
44598 
44599      Action:   Follow normal recovery procedures.
44600 
44601 
44602                [wire_proc.pl1]
44603                wire_proc:  too many temp wired segments.
44604 
44605 
44606      Stream:   BOS Typewriter (Crashes system)
44607 
44608      Time:     While system is running.
44609 
44610      Meaning:  A  request  has  been  made  to  the supervisor to
44611                temp-wire an eighth  hardcore segment.  Only seven
44612                are allowed.   Temp-wiring is used  for supervisor
44613                programs, not I/O buffers.  This indicates a logic
44614 
44615 
44616 wire_proc                      770            08/03/23     MR12.7^L
44617 
44618 
44619                error in the supervisor, or CPU or memory hardware
44620                problems.
44621 
44622      Action:   Follow normal recovery procedures.  $boot_tape
44623 
44624 
44625 
44626                [wired_shutdown.pl1]
44627                wired_shutdown:    FFF   fault   during  emergency
44628                shutdown
44629 
44630 
44631      Stream:   BOS Typewriter (Crashes system)
44632 
44633      Time:     Emergency shutdown
44634 
44635      Meaning:  An unexpected  fault has occured  during emergency
44636                shutdown.  Emergency shutdown cannot complete.
44637 
44638      Action:   Get  a dump  for system  programmers.  If  an disk
44639                dump was taken of the  preceding crash, get a dump
44640                to  paper via  the bce  dump facility.  Re-attempt
44641                ESD as many times as necessary.
44642 
44643 
44644 
44645                [x25_mpx.pl1]
44646                x25_mpx(CHN):  Call Confirm in state STATE.
44647 
44648 
44649      Stream:   Logged in SYSERR log.
44650 
44651      Time:     While system is running.
44652 
44653      Meaning:  An  unexpected Call  Confirm packet  was received.
44654                The call is cleared.
44655 
44656      Action:   Contact the system programming staff.
44657 
44658 
44659                [x25_mpx.pl1]
44660                x25_mpx(CHN):  Clear Confirm in state STATE.
44661 
44662 
44663      Stream:   Logged in SYSERR log.
44664 
44665      Time:     While system is running.
44666 
44667      Meaning:  An  unexpected  Clear   Confirm  packet  has  been
44668                received.  The call is cleared.
44669 
44670      Action:   Contact the system programming staff.
44671 
44672 
44673 
44674 x25_mpx(CHN)                   771            08/03/23     MR12.7^L
44675 
44676 
44677 
44678 
44679                [x25_mpx.pl1]
44680                x25_mpx(CHN):  Clear Indication CAUSE/DIAGNOSTIC.
44681 
44682 
44683      Stream:   Logged in SYSERR log.
44684 
44685      Time:     While system is running.
44686 
44687      Meaning:  A   Clear  Indication   with  non-zero   cause  or
44688                diagnostic fields has been  received.  The call is
44689                cleared.
44690 
44691      Action:   No operator action is required.
44692 
44693 
44694                [x25_mpx.pl1]
44695                x25_mpx(CHN):   Data  packet   received  in  state
44696                STATE.
44697 
44698 
44699      Stream:   Logged in SYSERR log.
44700 
44701      Time:     While system is running.
44702 
44703      Meaning:  An unexpected data packet  was received.  The call
44704                is cleared.
44705 
44706      Action:   Contact the system programming staff.
44707 
44708 
44709                [x25_mpx.pl1]
44710                x25_mpx(CHN):  Diagnostic type TYPE.
44711 
44712 
44713      Stream:   Logged in SYSERR log.
44714 
44715      Time:     While system is running.
44716 
44717      Meaning:  A  diagnostic packet  of type  TYPE was  received.
44718                Normal processing continues.
44719 
44720      Action:   Contact the system programming staff.
44721 
44722 
44723                [x25_mpx.pl1]
44724                x25_mpx(CHN):  Error CODE from write.
44725 
44726 
44727      Stream:   Logged in SYSERR log.
44728 
44729      Time:     While system is running.
44730 
44731 
44732 x25_mpx(CHN)                   772            08/03/23     MR12.7^L
44733 
44734 
44735      Meaning:  An error occurred writing to the LAP channel.  The
44736                LAP channel will be disconnected.
44737 
44738      Action:   Contact the system programming staff.
44739 
44740 
44741                [lap_simplex.pl1]
44742                x25_mpx(CHN):   Error  from  write  of  XXX chars.
44743                ERROR
44744 
44745 
44746      Stream:   Logged in SYSERR log.
44747 
44748      Time:     While system is running.
44749 
44750      Meaning:  The ERROR  occurred writing XXX characters  to the
44751                LAP   channel.    The    LAP   channel   will   be
44752                disconnected.
44753 
44754      Action:   Contact the system programming staff.
44755 
44756 
44757                [x25_mpx.pl1]
44758                x25_mpx(CHN):    Failure,   Link   state:   STATE,
44759                Current  Action:   FUNCTION,  in  ESTATE,  Primary
44760                state:  PSTATE, Secondary state:  SSTATE.
44761 
44762 
44763      Stream:   Logged in SYSERR log.
44764 
44765      Time:     While system is running.
44766 
44767      Meaning:  Normal request to crash the line when the link has
44768                been disconnected  by the FNP.  STATE  is the main
44769                state of the link.   FUNCTION is the last function
44770                the link  processed.  The ESTATE is  the execution
44771                state of the last function.  PSTATE and SSTATE are
44772                the link up substate.
44773 
44774      Action:   Contact the system programming staff.
44775 
44776 
44777                [x25_mpx.pl1]
44778                x25_mpx(CHN):  Invalid channel number LCN.
44779 
44780 
44781      Stream:   Logged in SYSERR log.
44782 
44783      Time:     While system is running.
44784 
44785      Meaning:  An  X.25 packet  with an  invalid logical  channel
44786                group  number or  logical channel  number has been
44787                received.  The packet is ignored.
44788 
44789 
44790 x25_mpx(CHN)                   773            08/03/23     MR12.7^L
44791 
44792 
44793      Action:   Contact the system programming staff.
44794 
44795 
44796                [x25_mpx.pl1]
44797                x25_mpx(CHN):  Invalid packet type TYPE on LC 0.
44798 
44799 
44800      Stream:   Logged in SYSERR log.
44801 
44802      Time:     While system is running.
44803 
44804      Meaning:  An  invalid packet  of type  TYPE was  received on
44805                logical channel zero.  The packet will be ignored.
44806 
44807      Action:   Contact the system programming staff.
44808 
44809 
44810                [x25_mpx.pl1]
44811                x25_mpx(CHN):  Invalid X.29 command CMD.
44812 
44813 
44814      Stream:   Logged in SYSERR log.
44815 
44816      Time:     While system is running.
44817 
44818      Meaning:  An  invalid X.29  command was  received.  An error
44819                indication is returned to the sender.
44820 
44821      Action:   Contact the system programming staff.
44822 
44823 
44824                [x25_mpx.pl1]
44825                x25_mpx(CHN):     Link    disconnected    due   to
44826                mis-matched frame sizes.  CMDR/FRMR frame:  FRAME.
44827 
44828 
44829      Stream:   Logged in SYSERR log.
44830 
44831      Time:     While system is running.
44832 
44833      Meaning:  The  FNP has received  a command reject  (LAPB) or
44834                frame  reject (LAP)  which specified  a reason  of
44835                "wide frame"  on channel CHN.  The  actual level 2
44836                command is  FRAME.  This means the  frame received
44837                by the other end was too long.  Instead of looping
44838                continuously trying  to send this frame,  the link
44839                will be  disconnected.  The maximum frame  size in
44840                the  Multics TTF for  this link should  be checked
44841                against the size expected by  the other end of the
44842                link, and corrected.
44843 
44844      Action:   Contact the system programming staff.
44845 
44846 
44847 
44848 x25_mpx(CHN)                   774            08/03/23     MR12.7^L
44849 
44850 
44851 
44852 
44853                [x25_mpx.pl1]
44854                x25_mpx(CHN):  No buffers available.
44855 
44856 
44857      Stream:   Logged in SYSERR log.
44858 
44859      Time:     While system is running.
44860 
44861      Meaning:  x25_mpx  was unable  to  allocate  a buffer  for a
44862                protocol  packet.  This  indicates a  severe space
44863                problem  in tty_buf.   The multiplexer  will sends
44864                itself a "hangup" order after freeing any space it
44865                has  for  protocol  packets  in  tty_buf.  If this
44866                multiplexer is  not the cause of  the problem then
44867                the system is likely to crash soon.
44868 
44869      Action:   Contact the system programming staff.
44870 
44871 
44872                [x25_mpx.pl1]
44873                x25_mpx(CHN):  Packet INOUT:  PACKET
44874 
44875 
44876      Stream:   Logged in SYSERR log.
44877 
44878      Time:     While system is running.
44879 
44880      Meaning:  A packet has been received  or sent and is logged.
44881                This  occurs when  the packet  tracing facility is
44882                turned on.   INOUT is the direction  and PACKET is
44883                the packet octets dumped in hexadecimal.
44884 
44885      Action:   No operator action is required.
44886 
44887 
44888                [x25_mpx.pl1]
44889                x25_mpx(CHN):  Packet too short.
44890 
44891 
44892      Stream:   Logged in SYSERR log.
44893 
44894      Time:     While system is running.
44895 
44896      Meaning:  A packet less then 3 characters long was received.
44897 
44898      Action:   Contact the system programming staff.
44899 
44900 
44901                [x25_mpx.pl1]
44902                x25_mpx(CHN):  Received REJ packet.
44903 
44904 
44905 
44906 x25_mpx(CHN)                   775            08/03/23     MR12.7^L
44907 
44908 
44909      Stream:   Logged in SYSERR log.
44910 
44911      Time:     While system is running.
44912 
44913      Meaning:  An X.25 REJ packet was received.  Multics does not
44914                support  this  feature.   The  virtual  circuit is
44915                reset.
44916 
44917      Action:   Contact the system programming staff.
44918 
44919 
44920                [x25_mpx.pl1]
44921                x25_mpx(CHN):  Reset Confirm in state STATE.
44922 
44923 
44924      Stream:   Logged in SYSERR log.
44925 
44926      Time:     While system is running.
44927 
44928      Meaning:  An  unexpected  Reset   Confirm  packet  has  been
44929                received.  The call is reset.
44930 
44931      Action:   Contact the system programming staff.
44932 
44933 
44934                [x25_mpx.pl1]
44935                x25_mpx(CHN):  Reset received CAUSE/DIAGNOSTIC.
44936 
44937 
44938      Stream:   Logged in SYSERR log.
44939 
44940      Time:     While system is running.
44941 
44942      Meaning:  A RESET REQUEST packet has been received.
44943 
44944      Action:   No operator action is required.
44945 
44946 
44947                [x25_mpx.pl1]
44948                x25_mpx(CHN):  Sequence error P(S) = N, V(R) = N.
44949 
44950 
44951      Stream:   Logged in SYSERR log.
44952 
44953      Time:     While system is running.
44954 
44955      Meaning:  An  X.25  packet  was  received  with an incorrect
44956                value for P(S).  The logical channel is reset.
44957 
44958      Action:   Contact the system programming staff.
44959 
44960 
44961                [x25_mpx.pl1]
44962 
44963 
44964 x25_mpx(CHN)                   776            08/03/23     MR12.7^L
44965 
44966 
44967                x25_mpx(CHN):  Sequence error:  P(R)  (= N) is not
44968                between previous P(R) (= N) and V(S) (= N).
44969 
44970 
44971      Stream:   Logged in SYSERR log.
44972 
44973      Time:     While system is running.
44974 
44975      Meaning:  An  X.25  packet  was  received  with an incorrect
44976                value for P(R).  The logical channel is reset.
44977 
44978      Action:   Contact the system programming staff.
44979 
44980 
44981                [x25_mpx.pl1]
44982                x25_mpx(CHN):  Unexpected Interrupt Confirm.
44983 
44984 
44985      Stream:   Logged in SYSERR log.
44986 
44987      Time:     While system is running.
44988 
44989      Meaning:  An  unexpected Interrupt  Confirm packet  has been
44990                received.  The call is reset.
44991 
44992      Action:   Contact the system programming staff.
44993 
44994 
44995                [x25_mpx.pl1]
44996                x25_mpx(CHN):   Unexpected   interrupt  TYPE  DATA
44997                received.
44998 
44999 
45000      Stream:   Logged in SYSERR log.
45001 
45002      Time:     While system is running.
45003 
45004      Meaning:  An unexpected MCM interrupt was processed.
45005 
45006      Action:   Contact the system programming staff.
45007 
45008 
45009                [x25_mpx.pl1]
45010                x25_mpx(CHN):  Unexpected packet type TYPE on idle
45011                VC.
45012 
45013 
45014      Stream:   Logged in SYSERR log.
45015 
45016      Time:     While system is running.
45017 
45018      Meaning:  An unexpected packet has  been received on an idle
45019                channel.  The channel is cleared.
45020 
45021 
45022 x25_mpx(CHN)                   777            08/03/23     MR12.7^L
45023 
45024 
45025      Action:   Contact the system programming staff.
45026 
45027 
45028                [x25_mpx.pl1]
45029                x25_mpx(CHN):  Unexpected packet type TYPE.
45030 
45031 
45032      Stream:   Logged in SYSERR log.
45033 
45034      Time:     While system is running.
45035 
45036      Meaning:  An  unexpected  packet  has  been  received.   The
45037                packet is ignored.
45038 
45039      Action:   Contact the system programming staff.
45040 
45041 
45042                [x25_mpx.pl1]
45043                x25_mpx(CHN):   Unrecognized   general  format  ID
45044                GFID.
45045 
45046 
45047      Stream:   Logged in SYSERR log.
45048 
45049      Time:     While system is running.
45050 
45051      Meaning:  A packet  with a bad format ID  was received.  The
45052                packet will be ignored.
45053 
45054      Action:   Contact the system programming staff.
45055 
45056 
45057                [x25_mpx.pl1]
45058                x25_mpx(CHN):  X.29 ERROR CODE/REASON.
45059 
45060 
45061      Stream:   Logged in SYSERR log.
45062 
45063      Time:     While system is running.
45064 
45065      Meaning:  An  X.29 ERROR  packet  with  error code  CODE and
45066                reason  REASON   was  received.   The   packet  is
45067                ignored.
45068 
45069      Action:   Contact the system programming staff.
45070 
45071 
45072                [x25_mpx.pl1]
45073                x25_mpx(CHN/LC):  Call Request in state STATE.
45074 
45075 
45076      Stream:   Logged in SYSERR log.
45077 
45078 
45079 
45080 x25_mpx(CHN/LC)                778            08/03/23     MR12.7^L
45081 
45082 
45083      Time:     While system is running.
45084 
45085      Meaning:  An unexpected Call Request has been received.  The
45086                call is cleared.
45087 
45088 
45089                [x25_mpx.pl1]
45090                x25_mpx(CHN/LC):          Clear         Indication
45091                CAUSE/DIAGNOSTIC in idle VC.
45092 
45093 
45094      Stream:   Logged in SYSERR log.
45095 
45096      Time:     While system is running.
45097 
45098      Meaning:  A Clear Indication has  been received on a channel
45099                with  no call  in  progress.   A Clear  Confirm is
45100                returned.
45101 
45102      Action:   No operator action is required.
45103 
45104 
45105                [x25_mpx.pl1]
45106                x25_mpx(CHN/LC):  No listening channels.
45107 
45108 
45109      Stream:   Logged in SYSERR log.
45110 
45111      Time:     While system is running.
45112 
45113      Meaning:  There were  no listening channels available  for a
45114                network call.  The call is refused.
45115 
45116      Action:   Contact the system programming staff.
45117 
45118 
45119                [x25_mpx.pl1]
45120                x25_mpx(CHN/LC):  Time out in state STATE.
45121 
45122 
45123      Stream:   Logged in SYSERR log.
45124 
45125      Time:     While system is running.
45126 
45127      Meaning:  The network  did not respond to a  call, reset, or
45128                clear request.  The call will be cleared.
45129 
45130      Action:   Contact the system programming staff.
45131 
45132 
45133 
45134 
45135 
45136 
45137 
45138 x25_mpx(CHN/LC)                779            08/03/23     MR12.7^L