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/21/20 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/21/20 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/21/20 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 run5 08/21/20 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 resources 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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 resources:
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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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 777. The message binary will
1616 reflect null access mode and ring bracket of
1617 777.
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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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 'installs
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/21/20 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/21/20 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 systemes
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/21/20 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_NNs. 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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 l1l2l3l4" 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 MR12.7^L
6163
6164
6165 Service programs is being used. BOS Typewriter
6166 Crashes systemes
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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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/21/20 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 page_error.alm
8584 AUDIT page_fault: GRANTED excessive segment
8585 state changes Moderate_cc for PROCESS_GROUP_ID
8586 AUTHORIZATION
8587
8588
8589
8590 Time: While system is running.
8591
8592 Stream: $security_log
8593
8594
8595
8596
8597
8598 AUDIT page_fault 149 08/21/20 MR12.7^L
8599
8600
8601 Meaning: An attempt to use the modification of various
8602 segment " attributes as a covert channel was
8603 detected.
8604
8605
8606
8607 pnt_db_util_.pl1
8608 AUDIT pnt_db_util_: GRANTED addition of pnt
8609 entry Admin_op for PERSON.PROJECT.TAG AUTH
8610 Level=1 to PNT entry USERID no access class.
8611
8612
8613 Stream: $access_audit
8614
8615 Time: While system is running.
8616
8617 Meaning: The user PERSON.PROJECT.TAG added a new PNT
8618 entry for USERID
8619
8620 Action: No operator action is required.
8621
8622
8623 pnt_db_util_.pl1
8624 AUDIT pnt_db_util_: GRANTED deletion of pnt
8625 entry Admin_op for PERSON.PROJECT.TAG AUTH
8626 Level=1 to PNT entry USERID no access class.
8627
8628
8629 Stream: $access_audit
8630
8631 Time: While system is running.
8632
8633 Meaning: The user PERSON.PROJECT.TAG deleted the PNT entry
8634 for USERID.
8635
8636 Action: No operator action is required.
8637
8638
8639 pnt_db_util_.pl1
8640 AUDIT pnt_db_util_: GRANTED modification of pnt
8641 entry Admin_op for PERSON.PROJECT.TAG AUTH
8642 Level=1 to PNT entry USERID: CHANGES no access
8643 class.
8644
8645
8646 Stream: $access_audit
8647
8648 Time: While system is running.
8649
8650 Meaning: The user PERSON.PROJECT.TAG modified the PNT entry
8651 for USERID. CHANGES describes in brief format
8652 what security relevant changes were made. See the
8653
8654
8655
8656 AUDIT pnt_db_util_ 150 08/21/20 MR12.7^L
8657
8658
8659 binary information in the audit message for
8660 further details.
8661
8662 Action: No operator action is required.
8663
8664
8665 reclassify.pl1
8666 AUDIT reclassify$ENTRY: GRANTED modification of
8667 security out-of-service ADDED_INFO
8668
8669
8670 Stream: $access_audit
8671
8672 Time: While system is running.
8673
8674 Meaning: An AIM error was found in respect to the specified
8675 directory. There was a disagreement in access
8676 class between the directory and one of it's sons
8677 or there was an upgraded directory with
8678 non-terminal quota.
8679
8680 Action: No operator action is required.
8681
8682
8683 reclassify.pl1
8684 AUDIT reclassify$ENTRY: GRANTED|DENIED
8685 modification of fs_obj access class ADDED_INFO
8686
8687
8688 Stream: $access_audit
8689
8690 Time: While system is running.
8691
8692 Meaning: Indicates whether an attempt to reclassify the
8693 specified file system object was granted or
8694 denied. In the case of reclassify$node a message
8695 will be generated for each entry in the directory
8696 being reclassified.
8697
8698 Action: No operator action is required.
8699
8700
8701 salv_check_vtoce_.pl1
8702 AUDIT salv_check_vtoce_: GRANTED modification
8703 of security out-of-service ADDED_INFO
8704
8705
8706 Stream: $access_audit
8707
8708 Time: While system is running.
8709
8710
8711
8712
8713
8714 AUDIT salv_check_vtoce_ 151 08/21/20 MR12.7^L
8715
8716
8717 Meaning: Security out-of-service switch was set because
8718 vtoce access class did not match the entry access
8719 class for the specified file system entry.
8720
8721 Action: Contact the system programming staff._ssa
8722
8723
8724 salv_dir_checker_.pl1
8725 AUDIT salv_dir_checker_: GRANTED modification
8726 of fs_obj access ADDED_INFO
8727
8728
8729 Stream: $access_audit
8730
8731 Time: Salvaging
8732
8733 Meaning: The salvager has truncated the ACL of a branch.
8734
8735 Action: Contact the system programming staff._ssa
8736
8737
8738 set_privileges.pl1
8739 AUDIT set_privileges: GRANTED modification of
8740 system AIM privilege ADDED_INFO
8741
8742
8743 Stream: $access_audit
8744
8745 Time: While system is running.
8746
8747 Meaning: The specified user made a privileged call for
8748 modifying the process AIM privileges
8749
8750 Action: No operator action is required.
8751
8752
8753 set_sys_audit_thresholds_.pl1
8754 AUDIT set_sys_audit_thresholds_: GRANTED|DENIED
8755 modification of system audit flags and thresholds
8756 ADDED_INFO
8757
8758
8759 Stream: $access_audit
8760
8761 Time: While system is running.
8762
8763 Meaning: Indicates that the system wide audit enable flags
8764 and the thresholds have been changed as indicated.
8765
8766 Action: No operator action is required.
8767
8768
8769
8770
8771
8772 bce_abs_seg 152 08/21/20 MR12.7^L
8773
8774
8775
8776
8777 bce_abs_seg.pl1
8778 bce_abs_seg: Too many bce abs-segs.
8779
8780
8781 Stream: BOS Typewriter Crashes system
8782
8783 Time: System Intialization.
8784
8785 Meaning: More per-bce pass abs-segs were encountered than
8786 fit in the abs-seg array. This is a software
8787 error.
8788
8789
8790
8791 bce_ioi_post.pl1
8792 bce_ioi_post: Error posting i/o completion.
8793 ioi_event_channel: CCCCCCCCCCCC ioi_message:
8794 MMMMMMMMMMMM
8795
8796
8797
8798 Stream: BOS Typewriter Crashes system
8799
8800 Time: System Intialization.
8801
8802 Meaning: No posting buffer was found in an "I/O
8803 outstanding" state for the above event channel.
8804 This indicates a logic error in the supervisor or
8805 CPU or memory hardware problems.
8806
8807 Action: Contact the system programming staff.
8808
8809
8810 bce_ioi_post.pl1
8811 bce_ioi_post: System not at correct level to post
8812 I/O completion.
8813
8814
8815 Stream: BOS Typewriter Crashes system
8816
8817 Time: System Intialization.
8818
8819 Meaning: The flag sys_info$service_system indicates that
8820 the system is up and should be posting I/O
8821 completions via pxss$io_wakeup not this program.
8822 This indicates a logic error in the supervisor or
8823 CPU or memory hardware problems.
8824
8825 Action: Contact the system programming staff.
8826
8827
8828
8829
8830 bce_ioi_post 153 08/21/20 MR12.7^L
8831
8832
8833 bce_ioi_post.pl1
8834 bce_ioi_post: Unexpected System Fault.
8835 ioi_event_channel: CCCCCCCCCCCC ioi_message:
8836 MMMMMMMMMMMM
8837
8838
8839
8840 Stream: BOS Typewriter Crashes system
8841
8842 Time: System Intialization.
8843
8844 Meaning: This indicates a logic error in the supervisor or
8845 CPU or memory hardware problems.
8846
8847 Action: Contact the system programming staff.
8848
8849
8850 bce_save.pl1
8851 bce_save: Error issuing tape connect for TAPE_DEV
8852 TAPE_SET. ERR_MESSAGE
8853
8854
8855 Stream: BOS Typewriter Crashes system
8856
8857 Time: System Intialization.
8858
8859 Meaning: IOI has returned a non-zero error which has been
8860 expanded in ERR_MESSAGE.This indicates a logic
8861 error in the supervisor or CPU or memory hardware
8862 problems.
8863
8864 Action: Contact the system programming staff.
8865
8866
8867 bce_save.pl1
8868 bce_save: Internal bit map for PV_NAME TAPE_SET
8869 contains no in use pages.
8870
8871
8872 Stream: BOS Typewriter Crashes system
8873
8874 Time: System Intialization.
8875
8876 Meaning: The copied/packed internal version of the PV's
8877 volume bit map contains no used pages OFF
8878 bits.This indicates a logic error in the
8879 supervisor or CPU or memory hardware problems.
8880
8881 Action: Contact the system programming staff.
8882
8883
8884 bce_save.pl1
8885
8886
8887
8888 bce_save 154 08/21/20 MR12.7^L
8889
8890
8891 bce_save: IO complete but NO status returned for
8892 TAPE_SET.
8893
8894
8895 Stream: BOS Typewriter Crashes system
8896
8897 Time: System Intialization.
8898
8899 Meaning: An I/O has been posted but there was no
8900 indication of status being returned.This indicates
8901 a logic error in the supervisor or CPU or memory
8902 hardware problems.
8903
8904 Action: Contact the system programming staff.
8905
8906
8907 bce_save.pl1
8908 bce_save: Out of disk buffers for TAPE_SET.
8909
8910
8911 Stream: BOS Typewriter Crashes system
8912
8913 Time: System Intialization.
8914
8915 Meaning: This indicates a logic error in the supervisor or
8916 CPU or memory hardware problems.
8917
8918 Action: Contact the system programming staff.
8919
8920
8921 bce_save.pl1
8922 bce_save: Out of tape buffers for TAPE_SET.
8923
8924
8925 Stream: BOS Typewriter Crashes system
8926
8927 Time: System Intialization.
8928
8929 Meaning: This indicates a logic error in the supervisor or
8930 CPU or memory hardware problems.
8931
8932 Action: Contact the system programming staff.
8933
8934
8935 bce_save_util_.pl1
8936 bce_save_util_: Out of disk buffers for TAPE_SET.
8937
8938
8939 Stream: BOS Typewriter Crashes system
8940
8941 Time: System Intialization.
8942
8943
8944
8945
8946 bce_save_util_ 155 08/21/20 MR12.7^L
8947
8948
8949 Meaning: This indicates a logic error in the supervisor or
8950 CPU or memory hardware problems.
8951
8952 Action: Contact the system programming staff.
8953
8954
8955 wired_shutdown.pl1
8956 begin emergency shutdown part 1
8957
8958
8959 Stream: BOS Typewriter.
8960
8961 Time: Emergency shutdown
8962
8963 Meaning: The system emergency shutdown environment has been
8964 successfully established. An attempt will be made
8965 to write out all of memory and flush the paging
8966 device.
8967
8968 Action: No operator action is required.
8969
8970
8971 boot_tape_io.pl1
8972 boot_tape_io: Code CODE from absadr.
8973
8974
8975 Stream: BOS Typewriter Crashes system
8976
8977 Time: System Intialization.
8978
8979 Meaning: boot_tape_io was unable to find the address of its
8980 buffer. This indicates a logic error in the
8981 supervisor or CPU or memory hardware problems.
8982
8983 Action: $boot_tape
8984
8985
8986 boot_tape_io.pl1
8987 boot_tape_io: Code CODE from io_manager$assign
8988
8989
8990 Stream: BOS Typewriter Crashes system
8991
8992 Time: System Intialization.
8993
8994 Meaning: The bootload tape reading package could not assign
8995 the bootload tape drive to itself. This indicates
8996 a logic error in the supervisor or CPU or memory
8997 hardware problems.
8998
8999 Action: $boot_tape
9000
9001
9002
9003
9004 boot_tape_io 156 08/21/20 MR12.7^L
9005
9006
9007
9008
9009 boot_tape_io.pl1
9010 boot_tape_io: Unable to allocate buffer.
9011
9012
9013 Stream: BOS Typewriter Crashes system
9014
9015 Time: System Intialization.
9016
9017 Meaning: The bootload tape reading package could not
9018 allocate a wired-down buffer into which to read
9019 the bootload tape. This indicates a logic error
9020 in the supervisor or CPU or memory hardware
9021 problems.
9022
9023 Action: $boot_tape
9024
9025
9026 bootload_error.alm
9027 bootload_0: An unpaged page table overflowed for
9028 seg N.
9029
9030
9031 Stream: BOS Typewriter Crashes system
9032
9033 Time: System Intialization.
9034
9035 Meaning: The size of the page table needed for "unpaged"
9036 segment N exceeded the area left for such page
9037 tables.
9038
9039 Action: The system tape was generated improperly; use
9040 another copy of the system tape.
9041
9042
9043
9044 bootload_error.alm
9045 bootload_0: Bad MST format.
9046
9047
9048 Stream: BOS Typewriter Crashes system
9049
9050 Time: System Intialization.
9051
9052 Meaning: The records on the MST tape were out of sequence.
9053
9054 Action: Try another tape.
9055
9056
9057 bootload_error.alm
9058 bootload_0: Booted tape MPC.
9059
9060
9061
9062 bootload_0 157 08/21/20 MR12.7^L
9063
9064
9065 Stream: BOS Typewriter.
9066
9067 Time: System Intialization.
9068
9069 Meaning: The system succeeded in booting the bootload tape
9070 mpc.
9071
9072
9073 bootload_error.alm
9074 bootload_0: Booting FWNAME IOM CHAN with FWID
9075 FWREV firmware.
9076
9077
9078 Stream: BOS Typewriter.
9079
9080 Time: System Intialization.
9081
9082 Meaning: The system is about to boot firmware into the
9083 bootload tape mpc.
9084
9085
9086
9087 bootload_error.alm
9088 bootload_0: Booting system SYSID generated
9089 CREATION_TIME
9090
9091
9092 Stream: BOS Typewriter.
9093
9094 Time: System Intialization.
9095
9096 Meaning: This is the first message printed by Multics
9097 announcing the sysid and creation date/time of the
9098 system tape.
9099
9100
9101
9102 bootload_error.alm
9103 bootload_0: Console status WORD1 WORD2
9104
9105
9106 Stream: BOS Typewriter Crashes system
9107
9108 Time: System Intialization.
9109
9110 Meaning: An I/O error was encountered on the console.
9111 WORD1 and WORD2 are the two words of the status
9112 returned.
9113
9114 Action: Run T&D on the console.
9115
9116
9117
9118
9119
9120 bootload_0 158 08/21/20 MR12.7^L
9121
9122
9123
9124
9125 bootload_error.alm
9126 bootload_0: Enter boot tape MPC model:
9127
9128
9129 Stream: BOS Typewriter.
9130
9131 Time: System Intialization.
9132
9133 Meaning: This query requests the operator to identify the
9134 bootload tape mpc so that firmware may be loaded.
9135 Refer to the MOH for details.
9136
9137
9138
9139 bootload_error.alm
9140 bootload_0: Enter tape drive number for memory
9141 dump:
9142
9143
9144 Stream: BOS Typewriter.
9145
9146 Time: BOS Typewriter Crashes system
9147
9148 Meaning: An initialization failure occured when the toehold
9149 was not active. The system is requesting the
9150 number of a tape drive on the bootload tape mpc on
9151 which to write a dump of memory.
9152
9153
9154
9155 bootload_error.alm
9156 bootload_0: Error status WORD1 WORD2 booting
9157 FWTYPE firmware.
9158
9159
9160 Stream: BOS Typewriter.
9161
9162 Time: System Intialization.
9163
9164 Meaning: An error occured when attempting to boot firmware
9165 into the bootload tape mpc. WORD1 and WORD2 are
9166 the status returned.
9167
9168 Action: Try another firmware identifier.
9169
9170
9171 bootload_error.alm
9172 bootload_0: Excessive tape errors: status WORD1
9173 WORD2.
9174
9175
9176
9177
9178 bootload_0 159 08/21/20 MR12.7^L
9179
9180
9181 Stream: BOS Typewriter.
9182
9183 Time: BOS Typewriter Crashes system
9184
9185 Meaning: An excessive number of write errors occured when
9186 trying to write an early dump tape. The dump to
9187 this tape will be aborted.
9188
9189 Action: Try another tape.
9190
9191
9192 bootload_error.alm
9193 bootload_0: External symbol not found: SEG$ENTRY
9194
9195
9196 Stream: BOS Typewriter.
9197
9198 Time: System Intialization.
9199
9200 Meaning: The entrypoint ENTRY was not found within the
9201 existant segment SEG during pre-linking of
9202 collection 1. This may indicate that the system
9203 tape was generated improperly.
9204
9205
9206
9207 bootload_error.alm
9208 bootload_0: Improper text/link/def sequence.
9209
9210
9211 Stream: BOS Typewriter Crashes system
9212
9213 Time: System Intialization.
9214
9215 Meaning: Text linkage or definitions appeared out of
9216 proper sequence " on the Multics system tape.
9217
9218 Action: The system tape was generated improperly; use
9219 another copy " of the system tape.
9220
9221
9222
9223 bootload_error.alm
9224 bootload_0: Out of main memory.
9225
9226
9227 Stream: BOS Typewriter Crashes system
9228
9229 Time: System Intialization.
9230
9231 Meaning: Not enough main memory is configured in order to
9232 load " collection 1.
9233
9234
9235
9236 bootload_0 160 08/21/20 MR12.7^L
9237
9238
9239 Action: Configure more main memory and boot again.
9240
9241
9242 bootload_error.alm
9243 bootload_0: Shutdown
9244
9245
9246 Stream: BOS Typewriter Crashes system
9247
9248 Time: System Intialization.
9249
9250 Meaning: The operator answered "shut" when asked for the
9251 bootload tape mpc information.
9252
9253 Action: $reboot
9254
9255
9256 bootload_error.alm
9257 bootload_0: Tape read error: WORD1 WORD2
9258
9259
9260 Stream: BOS Typewriter Crashes system
9261
9262 Time: System Intialization.
9263
9264 Meaning: An I/O error was encountered when reading the MST
9265 tape. WORD1 and WORD2 are the two words of the
9266 status returned.
9267
9268 Action: $reboot
9269
9270
9271 bootload_error.alm
9272 bootload_0: Too many supervisor segments.
9273
9274
9275 Stream: BOS Typewriter Crashes system
9276
9277 Time: System Intialization.
9278
9279 Meaning: More than 256 supervisor segments were declared on
9280 the MST.
9281
9282 Action: The system tape was generated improperly; use
9283 another copy of the system tape.
9284
9285
9286
9287 bootload_error.alm
9288 bootload_0: Unexpected control word on tape
9289 CONTROL_WORD.
9290
9291
9292
9293
9294 bootload_0 161 08/21/20 MR12.7^L
9295
9296
9297 Stream: BOS Typewriter Crashes system
9298
9299 Time: System Intialization.
9300
9301 Meaning: An unexpected Multics system tape control word was
9302 encountered.
9303
9304 Action: The system tape was generated improperly; use
9305 another copy of the system tape.
9306
9307
9308
9309 bootload_error.alm
9310 bootload_0: Unknown tape MPC model NAME.
9311
9312
9313 Stream: BOS Typewriter.
9314
9315 Time: System Intialization.
9316
9317 Meaning: The operator entered an unrecognizable mpc
9318 identifier.
9319
9320 Action: Try another mpc identifier.
9321
9322
9323 bootload_disk_post.pl1
9324 bootload_disk_post: Attempt to post non-requested
9325 i/o completion.
9326
9327
9328 Stream: BOS Typewriter Crashes system
9329
9330 Time: System Intialization.
9331
9332 Meaning: disk_control detected an i/o completion that
9333 Bootload Multics does not believe it requested.
9334
9335 Action: Reboot.
9336
9337
9338 bootload_disk_post.pl1
9339 bootload_disk_post: Attempt to post non-requested
9340 i/o completion.
9341
9342
9343 Stream: BOS Typewriter Crashes system
9344
9345 Time: System Intialization.
9346
9347 Meaning: disk_control detected an i/o completion that
9348 Bootload Multics does not believe it requested.
9349
9350
9351
9352 bootload_disk_post 162 08/21/20 MR12.7^L
9353
9354
9355 Action: Reboot.
9356
9357
9358 boundfault.pl1
9359 boundfault: activating into father XXX|YYY
9360
9361
9362 Stream: BOS Typewriter Crashes system
9363
9364 Time: While system is running.
9365
9366 Meaning: While activating a segment the parent directory
9367 for the segment became deactivated. This
9368 indicates a logic error in the supervisor or CPU
9369 or memory hardware problems.
9370
9371 Action: Follow normal recovery procedures.
9372
9373
9374 boundfault.pl1
9375 boundfault: on the root
9376
9377
9378 Stream: BOS Typewriter Terminates user process
9379
9380 Time: While system is running.
9381
9382 Meaning: A boundfault on the root directory has been
9383 encountered. This indicates a logic error in the
9384 supervisor or CPU or memory hardware problems.
9385
9386 Action: Contact the system programming staff.
9387
9388
9389 cache_tester.pl1
9390 cache_tester: cache parity error detected on CPU
9391 <TAG> bit failures at level W column XXX in
9392 cache: YYYYYYYYYYYYYYYYYYYYYYYY in memory:
9393 ZZZZZZZZZZZZZZZZZZZZZZZZ.
9394
9395
9396
9397 Stream: BOS Typewriter.
9398
9399 Time: While system is running.
9400
9401 Meaning: This message is the result of a multiple bit cache
9402 failure detected and cache data and its
9403 corresponding memory data captured by the fim. It
9404 should be noted that when a cache parity error is
9405 detected by the fim there is a window of time
9406 before the address in cache and in main store can
9407 be determined. Although the cache error data is
9408
9409
9410 cache_tester 163 08/21/20 MR12.7^L
9411
9412
9413 frozen cache is turned off unconditionaly when
9414 the parity retry of the fim is called the
9415 corresponding address in main store might have
9416 been changed through paging migration from other
9417 processors. This message then might not be a
9418 multiple error but rather the result of this
9419 window condition. If this message was the only
9420 diagnostic displayed i.e. the static test found
9421 no errors the cache will be turned back on. The
9422 values of W XXX YYY...Y and ZZZ...Z are as
9423 explained above.
9424
9425 Action: Contact Field Engineering
9426
9427
9428 cache_tester.pl1
9429 cache_tester: cache parity error detected on CPU
9430 <TAG> at: board XXXX chip YY.
9431
9432
9433
9434 Stream: BOS Typewriter.
9435
9436 Time: While system is running.
9437
9438 Meaning: This message is the result of a single bit cache
9439 failure detected and cache data and its
9440 corresponding memory data captured by the fim.
9441 This message will be displayed if the diagnostic
9442 error data from the fim is valid. The board and
9443 chip callout are as explained above.
9444
9445 Action: Contact field Engineering.
9446
9447
9448 cache_tester.pl1
9449 cache_tester: cache parity error detected on CPU
9450 <TAG> cache data is equal to the memory data.
9451 parity generation problem for level <L>.
9452
9453
9454
9455 Stream: BOS Typewriter.
9456
9457 Time: While system is running.
9458
9459 Meaning: This message is the result of a cache failure
9460 detected and cache data and its corresponding
9461 memory data captured by the fim. This message
9462 will be displayed if the diagnostic error data
9463 from the fim is valid.
9464
9465 Action: Contact field Engineering.
9466
9467
9468 cache_tester 164 08/21/20 MR12.7^L
9469
9470
9471
9472
9473 cache_tester.pl1
9474 cache_tester: Entire cache memory for CPU <TAG>
9475 has been disabled.
9476
9477
9478 Stream: BOS Typewriter sounds beeper
9479
9480 Time: While system is running.
9481
9482 Meaning: The static test of cache memory for CPU <TAG>
9483 detected repeatable errors in both halfs of cache.
9484 or one half of cache had previously been disabled
9485 and the static test of the other half detected
9486 repeatable errors.
9487
9488 Action: Contact field Engineering
9489
9490
9491 cache_tester.pl1
9492 cache_tester: LLUU cache memory csh<n> for CPU
9493 <TAG> has been turned off OTHER was AA and has not
9494 been changed.
9495
9496
9497
9498 Stream: BOS Typewriter sounds beeper
9499
9500 Time: While system is running.
9501
9502 Meaning: Either the lower half LLUU = Lower <n> = 1 or
9503 the upper half LLUU = Upper <n> = 2 of cache
9504 memory for CPU <TAG> has been turned off as the
9505 result of the static cache test finding a
9506 repeatable cache failure. The OTHER Upper or
9507 Lower was in state AA. If AA is off this half of
9508 cache was not tested. If AA is on this half of
9509 cache had no errors.
9510
9511 Action: Contact Field Engineering
9512
9513
9514 cache_tester.pl1
9515 cache_tester: No errors found in cache memory for
9516 CPU <TAG> cache will remain on.
9517
9518
9519 Stream: BOS Typewriter.
9520
9521 Time: While system is running.
9522
9523
9524
9525
9526 cache_tester 165 08/21/20 MR12.7^L
9527
9528
9529 Meaning: The static test of cache memory for CPU <TAG>
9530 found no errors and no cache error information was
9531 captured by the fim.
9532
9533 Action: cache is turned back on
9534
9535
9536 cache_tester.pl1
9537 cache_tester: repeatable cache parity error
9538 detected on CPU <TAG> cache data is equal to the
9539 memory data. parity generation problem for level
9540 <L>.
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 detected a cache failure but the data and its
9550 corresponding memory data are equal.
9551
9552 Action: Contact field Engineering.
9553
9554
9555 cache_tester.pl1
9556 cache_tester: repeatable cache parity errors
9557 detected on CPU <TAG> bit failures at level W
9558 column XXX in cache: YYYYYYYYYYYYYYYYYYYYYYYY in
9559 memory: ZZZZZZZZZZZZZZZZZZZZZZZZ.
9560
9561
9562
9563 Stream: BOS Typewriter.
9564
9565 Time: While system is running.
9566
9567 Meaning: The static test of cache memory for CPU <TAG>
9568 indicated a multiple bit error between the
9569 contents of cache and the contents of the wired
9570 test buffer. The multiple bit failure is further
9571 broken down to the failing cache level W 0 - 3
9572 and column XXX address. The data read from
9573 cache YYY...Y and the expected data ZZZ...Z is
9574 displayed as an aid for the field engineer. Since
9575 the failure happened during the static test of
9576 cache it is assumed to be a solid failure and
9577 that segment of cache memory csh1 or csh2 is
9578 turned off. There could be up to 3 multiple
9579 messages or some combination of multiple bit error
9580 messages and board and chip callouts since
9581
9582
9583
9584 cache_tester 166 08/21/20 MR12.7^L
9585
9586
9587 diagnostic data for the first 3 cache errors is
9588 captured.
9589
9590 Action: Contact Field Engineering personnel.
9591
9592
9593 cache_tester.pl1
9594 cache_tester: repeatable cache parity errors
9595 detected on CPU <TAG> at: board XXXX chip YY.
9596
9597
9598
9599 Stream: BOS Typewriter.
9600
9601 Time: While system is running.
9602
9603 Meaning: The static test of cache memory for CPU <TAG>
9604 indicated a single bit error between the contents
9605 of cache and the contents of the wired test
9606 buffer. The single bit failure is further broken
9607 down to the failing wire wrapped board board
9608 XXXX and integrated circuit chip chip YY that
9609 failed. Since it happened during the static test
9610 of cache it is assumed to be a solid failure and
9611 that segment of cache memory csh1 or csh2 is
9612 turned off. There could be up to 3 board and chip
9613 callouts since diagnostic data for the first 3
9614 cache errors is captured. These additional board
9615 and chip callouts will only be displayed if the
9616 single bit failure was a different bit or
9617 different cache level than the board and chip
9618 diagnostic already displayed.
9619
9620 Action: Contact Field Engineering personnel.
9621
9622
9623 cache_tester.pl1
9624 cache_tester: Unable to allocate wired buffer.
9625
9626
9627 Stream: BOS Typewriter.
9628
9629 Time: While system is running.
9630
9631 Meaning: Attempted to allocate wired contiguous buffer for
9632 cache testing and pc_contig could not find enough
9633 pages available.
9634
9635 Action: If cache error information was captured in the fim
9636 this information is displayed. Cache memory is
9637 turned back on.
9638
9639
9640
9641
9642 cache_tester 167 08/21/20 MR12.7^L
9643
9644
9645
9646
9647 cache_tester.pl1
9648 cache_tester: Unable to run on CPU <TAG> to EEDD
9649 cache ERRORMESSAGE.
9650
9651
9652 Stream: BOS Typewriter sounds beeper
9653
9654 Time: While system is running.
9655
9656 Meaning: The attempt to run on CPU <TAG> to either enable
9657 EEDD - enable or disable EEDD = disable cache
9658 memory failed.
9659
9660 Action: CPU <TAG> should be taken offline if the attempt
9661 was to disable cache memory.
9662
9663
9664
9665 cache_tester.pl1
9666 cache_tester: Unable to set CPU required to <TAG>
9667 cache is off ERRORMESSAGE.
9668
9669
9670 Stream: BOS Typewriter.
9671
9672 Time: While system is running.
9673
9674 Meaning: Attempted to run on CPU <TAG> for cache testing
9675 and could not set CPU required to that CPU.
9676
9677 Action: Cache memory is turned back on.
9678
9679
9680 call_bce.pl1
9681 call_bce: bce called from Multics.
9682
9683
9684 Stream: BOS Typewriter.
9685
9686 Time: While system is running.
9687
9688 Meaning: An outer ring program has called hphcs_$call_bce.
9689 This is usually done after printing an explanatory
9690 message. The system will resume operation if
9691 continue is typed.
9692
9693 Action: Follow normal recovery procedures.
9694
9695
9696 disk_rebuild_caller.pl1
9697
9698
9699
9700 Cannot 168 08/21/20 MR12.7^L
9701
9702
9703 Cannot shrink VTOC from XX to YY VTOCEs.
9704 Respecify parameters.
9705
9706
9707 Stream: Initializer process output.
9708
9709 Time: In response to an operator command.
9710
9711 Meaning: An attempt has been made to shrink the VTOC which
9712 is illegal.
9713
9714 Action: Respecify the parameters.
9715
9716
9717 mc_tty_.pl1
9718 Channel CHANNEL_NAME attached by Message
9719 Coordinator.
9720
9721
9722 Stream: Initializer terminal.
9723
9724 Time: While system is running.
9725
9726 Meaning: The terminal has been attached by the message
9727 coordinator in response to an accept or substty
9728 command.
9729
9730 Action: Proceed to use the terminal.
9731
9732
9733 channel_manager.pl1
9734 channel_manager: Cleanup while processing
9735 interrupt for devx N.
9736
9737
9738 Stream: BOS Typewriter Crashes system
9739
9740 Time: While system is running.
9741
9742 Meaning: The cleanup condition was signalled while
9743 processing an interrupt for the channel with devx
9744 N.
9745
9746 Action: Contact the system programming staff.
9747
9748
9749 channel_manager.pl1
9750 channel_manager: Error while processing interrupt
9751 for devx N. REASON
9752
9753
9754 Stream: BOS Typewriter Crashes system
9755
9756
9757
9758 channel_manager 169 08/21/20 MR12.7^L
9759
9760
9761 Time: While system is running.
9762
9763 Meaning: An error occurred while processing an interrupt
9764 for the channel with devx N. The specific kind of
9765 error is explained by REASON.
9766
9767
9768
9769 dn355_boot_interrupt.pl1
9770 checksum error in core image for FNP X
9771
9772
9773 Stream: BOS Typewriter.
9774
9775 Time: When bootloading an FNP
9776
9777 Meaning: The core image received for loading in the FNP had
9778 a checksum error.
9779
9780 Action: Try to load the FNP again. If the error recurs
9781 either the DIA hardware is failing or the core
9782 image in the Multics hierarchy is damaged. In the
9783 latter case the core image must be rebound.
9784
9785
9786
9787 system_startup_.pl1
9788 Command:
9789
9790
9791 Stream: BOS Typewriter.
9792
9793 Time: System Intialization.
9794
9795 Meaning: The Initializer types this message whenever it is
9796 waiting for a ring 1 command.
9797
9798 Action: Type the desired command. The normal command to
9799 type when bringing the system up is startup.
9800
9801
9802
9803 config_.pl1
9804 config_$find_table: TBLS card specifies no value
9805 for NAME.
9806
9807
9808 Stream: BOS Typewriter sounds beeper
9809
9810 Meaning: The config deck does not specify a value for NAME.
9811
9812 Action: One should be added. Message: config_$ENTRY:
9813 the config deck is full.
9814
9815
9816 config_$find_table 170 08/21/20 MR12.7^L
9817
9818
9819 Stream: BOS Typewriter Crashes system
9820
9821 Meaning: No space remained in the config deck for
9822 additional cards.
9823
9824 Action: If this recurs try another boot tape. Remove
9825 unneccessary config cards.
9826
9827
9828
9829 dn355_boot_interrupt.pl1
9830 configuration error reported by bootloading
9831 program for FNP X
9832
9833
9834 Stream: BOS Typewriter.
9835
9836 Time: When bootloading an FNP
9837
9838 Meaning: The FNP bootload program gicb found an
9839 inconsistency in the FNP configuration.
9840
9841 Action: Contact the system programming staff.
9842
9843
9844 dn355_boot_interrupt.pl1
9845 configuration error reported by FNP X: DETAILS
9846
9847
9848 Stream: BOS Typewriter.
9849
9850 Time: When bootloading an FNP
9851
9852 Meaning: The FNP initialization program detected an error
9853 or inconsistency in the FNP configuration.
9854 DETAILS is a more specific description of the
9855 error.
9856
9857 Action: If possible correct the error either by updating
9858 the CDT to reflect the actual configuration or
9859 recabling the FNP. If the error cannot be
9860 corrected or is not understood inform the systems
9861 programming staff.
9862
9863
9864
9865 configure_test_cpu.pl1
9866 configure_test_cpu: Unable to run on CPU X
9867 ERRORMESSAGE
9868
9869
9870 Stream: BOS Typewriter Crashes system
9871
9872
9873
9874 configure_test_cpu 171 08/21/20 MR12.7^L
9875
9876
9877 Time: When ISOLTS is terminating
9878
9879 Meaning: The system is attempting to restore the ISOLTS CPU
9880 to service. In attempting to reassign its
9881 interrupt mask it was unable to run on that CPU.
9882 This indicates hardware or software malfunction.
9883
9884 Action: Follow normal recovery procedures.
9885
9886
9887 disk_table_.pl1
9888 continuing demount of lv LVNAME
9889
9890
9891 Stream: Initializer process output.
9892
9893 Time: While system is running. The operator issued a
9894 dlv command for a logical volume for which a
9895 previous dlv command failed.
9896
9897 Action: No operator action is required.
9898
9899
9900 copy_fdump.pl1
9901 copy_fdump: Copied fdump image of erf NNN
9902 MM/DD/YY HHMM.M for USERNAME
9903
9904
9905 Stream: BOS Typewriter.
9906
9907 Time: While system is running.
9908
9909 Meaning: The user identified by USERNAME has successfully
9910 copied the FDUMP image for the specified ERF out
9911 of the DUMP partition. The time the FDUMP was
9912 taken is also included in the message. This
9913 message is informational only and is intended
9914 only as an aid in tracking system progress by
9915 perusing the syserr log.
9916
9917 Action: No operator action is required.
9918
9919
9920 copy_fdump.pl1
9921 copy_fdump: unexpected NAME signal.
9922
9923
9924 Stream: BOS Typewriter.
9925
9926 Time: While system is running.
9927
9928 Meaning: An attempt to copy the dump from the DUMP
9929 partition with copy_fdump resulted in an unclaimed
9930
9931
9932 copy_fdump 172 08/21/20 MR12.7^L
9933
9934
9935 signal. This may be due to damage to the DUMP
9936 partition contents a malfunction of the BCE dump
9937 command a supervisor error or a simple
9938 difficulty like running out of space in >dumps.
9939 The system continues operation. The copied dump
9940 may be only partly valid.
9941
9942 Action: Contact the system programming staff.
9943
9944
9945 correct_qused.pl1
9946 correct_qused: hash error
9947
9948
9949 Stream: BOS Typewriter Crashes system
9950
9951 Time: While system is running.
9952
9953 Meaning: Multiple entries within a directory undergoing
9954 quota correction have the same UID.
9955
9956
9957
9958 cpg_.pl1
9959 cpg_: Error: CONDITION attempting to create
9960 process for NAME.PROJ
9961
9962
9963 Stream: as severity1
9964
9965 Time: While system is running.
9966
9967 Meaning: A supervisor error prevented creation of a process
9968 for the user NAME.PROJ. An Answering Service dump
9969 was performed and the user was logged out if
9970 possible.
9971
9972 Action: Note for system programmer action. If this
9973 message is printed at every login it is probably
9974 wise to shut the system down and perform a
9975 bootload operation.
9976
9977
9978
9979 cpg_.pl1
9980 cpg_: ERROR_MESSAGE. Assigning pdir volume for
9981 USER
9982
9983
9984 Stream: as severity2
9985
9986 Time: While system is running.
9987
9988
9989
9990 cpg_ 173 08/21/20 MR12.7^L
9991
9992
9993 Meaning: The system was unable to assign a logical volume
9994 on which to place the process directory of a user.
9995 The user might not be able to log in
9996
9997 Action: Contact the system programming staff.
9998
9999
10000 cpg_.pl1
10001 cpg_: ERROR_MESSAGE. Cannot truncate pit_temp_
10002
10003
10004 Stream: as severity2
10005
10006 Time: While system is running.
10007
10008 Meaning: The system was unable to clear its temporary
10009 segment while attempting to log in a user. The
10010 user will be unable to log in.
10011
10012 Action: Contact the system programming staff.
10013
10014
10015 tc_init.pl1
10016 CPU CPUTAG: Model #: MODEL; Serial #: SERIAL;
10017 Ship date: YY/MM/DD.
10018
10019
10020 Stream: Logged in SYSERR log.
10021
10022 Time: When the bootload CPU is a DPS8 whose tag is
10023 CPUTAG is "added" to the system.
10024
10025 Meaning: The MODEL SERIAL and YY/MM/DD information is read
10026 from the DPS8 cpu's ID PROM. It is intended to be
10027 used as historical information for identifing
10028 CPUs regardless of what their current tag is
10029 assigned as.
10030
10031 Action: No operator action is required.
10032
10033
10034 tc_init.pl1
10035 CPU CPUTAG: Model #: MODEL; Serial #: SERIAL;
10036 Ship date: YY/MM/DD.
10037
10038
10039 Stream: Logged in SYSERR log.
10040
10041 Time: When the bootload CPU is a DPS8 whose tag is
10042 CPUTAG is "added" to the system.
10043
10044 Meaning: The MODEL SERIAL and YY/MM/DD information is read
10045 from the DPS8 cpu's ID PROM. It is intended to be
10046
10047
10048 CPU CPUTAG 174 08/21/20 MR12.7^L
10049
10050
10051 used as historical information for identifing
10052 CPUs regardless of what their current tag is
10053 assigned as.
10054
10055 Action: No operator action is required.
10056
10057
10058 obs_reconfigure.pl1
10059 CPU X is now running.
10060
10061
10062 Stream: Initializer process output.
10063
10064 Time: In response to an operator command.
10065
10066 Meaning: This is the response to a successful addcpu X
10067 command.
10068
10069 Action: No operator action is required.
10070
10071
10072 create_homedir_.pl1
10073 create_homedir_: Bad syntax in pathname. DIRNAME
10074 NAME.PROJ
10075
10076
10077 Stream: as severity0.
10078
10079 Time: While system is running.
10080
10081 Meaning: Typically caused by a homedir specification
10082 starting with other than >user_dir_dir or >udd.
10083 It may also occur while attempting to create the
10084 home directory for the user with name NAME and
10085 project PROJ.
10086
10087 Action: Note for system programmer action._sa
10088
10089
10090 create_homedir_.pl1
10091 create_homedir_: creating "DIRNAME" for "USERID"
10092
10093
10094 Stream: as severity0.
10095
10096 Time: While system is running.
10097
10098 Meaning: The user USERID did not have a home directory. It
10099 was created for him during login or when his
10100 project's PDT was installed. This is reasonable
10101 if this is the first time he has logged in.
10102 However his directory may have been destroyed by
10103
10104
10105
10106 create_homedir_ 175 08/21/20 MR12.7^L
10107
10108
10109 the Salvager in which case you have to retrieve
10110 his files.
10111
10112 Action: A retrieval of the user's directory may be
10113 necessary.
10114
10115
10116 create_homedir_.pl1
10117 create_homedir_: ERROR_MESSAGE. DIRNAME
10118 NAME.PROJ
10119
10120
10121 Stream: as severity0.
10122
10123 Time: While system is running.
10124
10125 Meaning: An error occurred while attempting to create the
10126 home directory for the user with name NAME and
10127 project PROJ.
10128
10129 Action: Note for system programmer action._sa
10130
10131
10132 create_root_dir.pl1
10133 create_root_dir: allocating hash table
10134 ERROR_MESSAGE
10135
10136
10137 Stream: BOS Typewriter Crashes system
10138
10139 Time: Cold boot of Multics hierarchy.
10140
10141 Meaning: This indicates a logic error in the supervisor or
10142 CPU or memory hardware problems. An error has
10143 occurred allocating the hash table for the root
10144 directory.
10145
10146 Action: Reboot with a different version of the system.
10147
10148
10149 create_root_dir.pl1
10150 create_root_dir: lock error on PPP
10151
10152
10153 Stream: BOS Typewriter Crashes system
10154
10155 Time: System Intialization.
10156
10157 Meaning: The supervisor was unable to lock the root. This
10158 indicates a logic error in the supervisor or CPU
10159 or memory hardware problems.
10160
10161 Action: Follow normal recovery procedures. $boot_tape
10162
10163
10164 create_root_dir 176 08/21/20 MR12.7^L
10165
10166
10167
10168
10169 create_root_vtoce.pl1
10170 create_root_vtoce: Cannot alloc-write root vtoce
10171 ERROR_MESSAGE
10172
10173
10174 Stream: BOS Typewriter Crashes system
10175
10176 Time: Cold boot of Multics hierarchy.
10177
10178 Meaning: The system is unable to write out the VTOC entry
10179 for the root directory.
10180
10181 Action: Correct the disk problem if one exists and reboot.
10182 Otherwise reboot with a different version of the
10183 system.
10184
10185
10186
10187 create_root_vtoce.pl1
10188 create_root_vtoce: Cannot set dmpr bit map for
10189 root ERROR_MESSAGE
10190
10191
10192 Stream: BOS Typewriter.
10193
10194 Time: Cold boot of Multics hierarchy.
10195
10196 Meaning: This indicates a logic error in the supervisor or
10197 CPU or memory hardware problems.
10198
10199 Action: Contact the system programming staff.
10200
10201 Message: create_root_vtoce: Cannot set
10202 root_vtocx in RPV label.
10203
10204 Stream: BOS Typewriter Crashes system
10205
10206 Time: Cold boot of Multics hierarchy.
10207
10208 Meaning: The system is unable to update the RPV label for
10209 the root directory.
10210
10211 Action: Correct the disk problem if one exists and reboot.
10212 Otherwise reboot with a different version of the
10213 system.
10214
10215 Message: create_root_vtoce: Root vtoce not
10216 allocated at 0 RPV not initialized.
10217
10218 Stream: BOS Typewriter Crashes system
10219
10220
10221
10222 create_root_vtoce 177 08/21/20 MR12.7^L
10223
10224
10225 Time: Cold boot of Multics hierarchy.
10226
10227 Meaning: A boot -cold was attempted without init_vol for
10228 RPV.
10229
10230 Action: Reboot system answering the find_rpv_subsystem
10231 with cold instead of rpv.
10232
10233
10234 create_rpv_partition.pl1
10235 create_rpv_partition: Error accessing record NNN.
10236
10237
10238 Stream: BOS Typewriter Crashes system
10239
10240 Time: System Intialization.
10241
10242 Meaning: An i/o error occured when accessing record NNN of
10243 the rpv while attempting to add a new partition.
10244
10245 Action: Try again. IF the error persists the rpv will
10246 need to be rebuilt.
10247
10248
10249 create_rpv_partition.pl1
10250 create_rpv_partition: No room in partition map
10251 for NAME.
10252
10253
10254 Stream: BOS Typewriter Crashes system
10255
10256 Time: System Intialization.
10257
10258 Meaning: The partition map of the rpv was full. The
10259 partition could not be added.
10260
10261 Action: The rpv will need to be rebuilt.
10262
10263
10264 create_rpv_partition.pl1
10265 create_rpv_partition: Out of disk.
10266
10267
10268 Stream: BOS Typewriter Crashes system
10269
10270 Time: System Intialization.
10271
10272 Meaning: Not enough free space existed on the rpv to add
10273 the new partition.
10274
10275 Action: The rlv will have to be rebuilt.
10276
10277
10278
10279
10280 create_rpv_partition 178 08/21/20 MR12.7^L
10281
10282
10283 create_rpv_partition.pl1
10284 create_rpv_partition: Paging region ends past
10285 start of high partitions.
10286
10287
10288 Stream: BOS Typewriter Crashes system
10289
10290 Time: System Intialization.
10291
10292 Meaning: An inconsistency was found in the partition map
10293 when adding a new partition to the rpv.
10294
10295 Action: The rpv will need to be rebuilt.
10296
10297
10298 create_rpv_partition.pl1
10299 create_rpv_partition: Paging region starts below
10300 end of low partitions.
10301
10302
10303 Stream: BOS Typewriter Crashes system
10304
10305 Time: System Intialization.
10306
10307 Meaning: An inconsistency was found in the partition map
10308 when adding a new partition to the rpv.
10309
10310 Action: The rpv will need to be rebuilt.
10311
10312
10313 create_rpv_partition.pl1
10314 create_rpv_partition: vtoce NNN's file map is
10315 damaged. Volume will need salvaging.
10316
10317
10318 Stream: BOS Typewriter Crashes system
10319
10320 Time: System Intialization.
10321
10322 Meaning: The vtoce named was found to be damaged when
10323 adding a new partition to the rpv.
10324
10325 Action: Salvage the rpv using a boot of the previous
10326 release.
10327
10328
10329 daemon_user_manager_.pl1
10330 daemon_user_manager_: Command sent to
10331 daemon_user_manager_ before it was initialized
10332
10333
10334 Stream: as severity1
10335
10336
10337
10338 daemon_user_manager_ 179 08/21/20 MR12.7^L
10339
10340
10341 Time: In response to an operator command.
10342
10343 Meaning: This message indicates an error in the Answering
10344 Service or an incorrect installation. No daemon
10345 users can log in.
10346
10347 Action: Contact the system programming staff.
10348
10349
10350 daemon_user_manager_.pl1
10351 daemon_user_manager_: Daemon init error. NAME
10352 PROJ SOURCE REASON
10353
10354
10355 Stream: as severity2
10356
10357 Time: In response to an operator command.
10358
10359 Meaning: The daemon user NAME PROJ on SOURCE was logged in
10360 correctly but his process could not be started.
10361 The daemon will be logged out.
10362
10363 Action: Contact the system programming staff.
10364
10365
10366 daemon_user_manager_.pl1
10367 daemon_user_manager_: Daemon will be logged out.
10368
10369
10370 Stream: as severity1
10371
10372 Time: While system is running.
10373
10374 Meaning: An error in a daemon process has caused it to
10375 terminate. The daemon suffered a fatal process
10376 error during initialization or it has set the
10377 option which causes it to be logged out when a
10378 fatal process error occurs.
10379
10380 Action: Attempt to log in the daemon again and proceed.
10381
10382
10383 daemon_user_manager_.pl1
10384 daemon_user_manager_: Error: CONDITION during OP
10385 for NAME.PROJ SOURCE
10386
10387
10388 Stream: as severity2
10389
10390 Time: While system is running.
10391
10392 Meaning: An unexpected fault has occurred while the daemon
10393 user manager was performing an operation of type
10394
10395
10396 daemon_user_manager_ 180 08/21/20 MR12.7^L
10397
10398
10399 OP for the named daemon process. An Answering
10400 Service dump was performed and the system attempts
10401 to continue but the daemon process may be in an
10402 unusable state.
10403
10404 Action: Contact the system programming staff.
10405
10406
10407 daemon_user_manager_.pl1
10408 daemon_user_manager_: ERROR_MESSAGE. Logout not
10409 permitted for message coordinator source SOURCE.
10410
10411
10412 Stream: as severity1
10413
10414 Time: In response to an operator command.
10415
10416 Meaning: The message coordinator access control segment
10417 >system_control_1>mc_acs>SOURCE.mcacs does not
10418 permit the operator to logout the daemon.
10419 Therefore the operator cannot logout the daemon.
10420
10421 Action: Contact the system programming staff._sa
10422
10423
10424 daemon_user_manager_.pl1
10425 daemon_user_manager_: ERROR_MESSAGE. NAME.PROJ
10426 SOURCE terminated.
10427
10428
10429 Stream: as severity1
10430
10431 Time: While system is running.
10432
10433 Meaning: An error in a daemon process has caused it to
10434 terminate. A following message will indicate
10435 whether a new process has been automatically
10436 created.
10437
10438 Action: If the daemon is logged out reinitialize the
10439 daemon and continue. Otherwise a new daemon
10440 process is created automatically and you can
10441 continue from there.
10442
10443
10444
10445 daemon_user_manager_.pl1
10446 daemon_user_manager_: ERROR_MESSAGE. No MC ACS
10447 segment for message coordinator source SOURCE
10448
10449
10450 Stream: as severity1
10451
10452
10453
10454 daemon_user_manager_ 181 08/21/20 MR12.7^L
10455
10456
10457 Time: In response to an operator command.
10458
10459 Meaning: The message coordinator access control segment
10460 >system_control_1>mc_acs>SOURCE.mcacs was not
10461 found. It must be created and given an ACL which
10462 permits the operator to logout the daemon.
10463 Therefore the operator cannot logout the daemon.
10464
10465 Action: Contact the system programming staff._sa
10466
10467
10468 daemon_user_manager_.pl1
10469 daemon_user_manager_: Event entry called with
10470 null ev_msg_ptr
10471
10472
10473 Stream: as severity2
10474
10475 Time: While system is running.
10476
10477 Meaning: This indicates an error in the Answering Service.
10478
10479 Action: Contact the system programming staff.
10480
10481
10482 daemon_user_manager_.pl1
10483 daemon_user_manager_: Fatal process error loop
10484 for NAME.PROJ SOURCE.
10485 Daemon will be logged out.
10486
10487
10488
10489 Stream: as severity1
10490
10491 Time: While system is running.
10492
10493 Meaning: An error in a daemon process has caused it to
10494 terminate repeatedly within the last few minutes.
10495 Detection of the loop causes the daemon to be
10496 logged out.
10497
10498 Action: Try to login the daemon again. If it still fails
10499 notify your System Administrator of the problem.
10500
10501
10502
10503 daemon_user_manager_.pl1
10504 daemon_user_manager_: Invalid signal from NAME
10505 PROJ SOURCE
10506 daemon_user_manager_: signal was "XXXXXXXX"
10507 YYY|ZZZZ
10508
10509
10510
10511
10512 daemon_user_manager_ 182 08/21/20 MR12.7^L
10513
10514
10515 Stream: as severity2
10516
10517 Time: While system is running.
10518
10519 Meaning: This message may result from an error in the
10520 Answering Service an error in one of the daemon
10521 processes or an attempt by an unauthorized user
10522 to signal the daemon user manager. If the NAME
10523 PROJ and SOURCE cannot be determined the process
10524 ID of the sender is shown instead. The DUT
10525 daemon user table entry affected is located at
10526 YYY|ZZZZ in the Answering Service.
10527
10528 The signal is ignored and the Answering Service
10529 attempts to continue. If a daemon user is named
10530 on the first line of the message this user will
10531 probably be unable to continue.
10532
10533 Action: Contact the system programming staff. If the user
10534 named in the message is a daemon user try typing
10535 "logout NAME PROJ SOURCE" and if this succeeds
10536 log the user in again if necessary.
10537
10538
10539
10540 daemon_user_manager_.pl1
10541 daemon_user_manager_: NAME PROJ SOURCE
10542 terminated. Daemon will be logged out.
10543
10544
10545 Stream: as severity2
10546
10547 Time: While system is running.
10548
10549 Meaning: NAME is the Person_id of the daemon PROJ is the
10550 Project_id of the daemon and SOURCE is the
10551 Message Coordinator source id of the daemon. The
10552 daemon encountered a fatal process error and was
10553 logged out to prevent the system from getting into
10554 a loop.
10555
10556 Action: Contact the system programming staff. You can try
10557 logging the daemon in again but if the process
10558 error is recurrent the problem must be corrected
10559 before the daemon will operate successfully.
10560
10561
10562
10563 daemon_user_manager_.pl1
10564 daemon_user_manager_: New process created.
10565
10566
10567 Stream: as severity1
10568
10569
10570 daemon_user_manager_ 183 08/21/20 MR12.7^L
10571
10572
10573 Time: While system is running.
10574
10575 Meaning: An error in a daemon process has caused it to
10576 terminate. A new process has been created.
10577
10578 Action: A new daemon process is created automatically and
10579 you can continue from there.
10580
10581
10582
10583 daemon_user_manager_.pl1
10584 daemon_user_manager_: premature STOPSTOP for
10585 NAME.PROJ SOURCE
10586
10587
10588 Stream: as severity0
10589
10590 Time: While system is running.
10591
10592 Meaning: This indicates a logic error in the supervisor or
10593 CPU or memory hardware problems.
10594
10595 Action: No operator action is required.
10596
10597
10598 daemon_user_manager_.pl1
10599 daemon_user_manager_: process PERSON.PROJECT
10600 SOURCE ignored trm_ signal.
10601
10602
10603 Stream: as severity 1
10604
10605 Time: While system is running.
10606
10607 Meaning: The daemon process PERSON.PROJECT using message
10608 coordinator SOURCE had been sent a trm_ signal to
10609 cause process termination but the process did not
10610 respond to the signal. The answering service
10611 proceeds with the bump new_proc log out etc
10612 operation.
10613
10614 Action: No operator action is required.
10615
10616
10617 daemon_user_manager_.pl1
10618 daemon_user_manager_: process PERSON.PROJECT
10619 SOURCE ignored wakeup EVENT_MSG from
10620 SENDER_PROCESS_ID
10621
10622
10623 Stream: as severity 1
10624
10625 Time: While system is running.
10626
10627
10628 daemon_user_manager_ 184 08/21/20 MR12.7^L
10629
10630
10631 Meaning: The daemon process PERSON.PROJECT using message
10632 coordinator SOURCE had been sent a wakeup with
10633 EVENT_MSG by the process with process_id
10634 SENDER_PROCESS_ID. This event message is unknown
10635 and will be ignored.
10636
10637 Action: No operator action is required.
10638
10639
10640 daemon_user_manager_.pl1
10641 daemon_user_manager_: You cannot new_proc to the
10642 requested authorization.
10643 Cannot new_proc to an authorization outside the
10644 daemon's allowed range.
10645
10646
10647
10648 Stream: as severity1
10649
10650 Time: While system is running.
10651
10652 Meaning: A daemon executed an improper new_proc command
10653 trying to change to an authorization greater than
10654 its maximum allowed authorization or less than
10655 its minimum allowed authorization as specified in
10656 the Person Name Table PNT System
10657 Administrator's Table SAT and Project Master
10658 File PMF. The new_proc is performed at the
10659 original authorization of the process.
10660
10661 Action: Contact the system programming staff._sa
10662
10663
10664 dbm_man.pl1
10665 dbm_man: attempt to initialize already
10666 initialized map for PV on dskX_NNS
10667
10668
10669 Stream: BOS Typewriter Crashes system
10670
10671 Time: While system is running.
10672
10673 Meaning: This indicates a logic error in the supervisor or
10674 CPU or memory hardware problems.
10675
10676 Action: Follow normal recovery procedures.
10677
10678
10679 dbm_man.pl1
10680 dbm_man: bit map relp not set in pvte for PV on
10681 dskX_NNS
10682
10683
10684
10685
10686 dbm_man 185 08/21/20 MR12.7^L
10687
10688
10689 Stream: BOS Typewriter Crashes system
10690
10691 Time: While system is running.
10692
10693 Meaning: This indicates a logic error in the supervisor or
10694 CPU or memory hardware problems.
10695
10696 Action: Follow normal recovery procedures.
10697
10698
10699 dbm_man.pl1
10700 dbm_man: Cannot get ASTE for dbm_seg
10701
10702
10703 Stream: BOS Typewriter Crashes system
10704
10705 Time: System Intialization.
10706
10707 Meaning: The system was unable to create the dbm_seg and
10708 obtain an ASTE for this segment.
10709
10710 Action: Contact the system programming staff._sa
10711
10712
10713 dbm_man.pl1
10714 dbm_man: csl failure
10715
10716
10717 Stream: Logged in SYSERR log.
10718
10719 Time: While system is running.
10720
10721 Meaning: The CSL instruction appears to have failed on one
10722 of the processors.
10723
10724 Action: No operator action is required.
10725
10726
10727 dbm_man.pl1
10728 dbm_man: unable to allocate dumper bit map for PV
10729 on dskX_NNS
10730
10731
10732 Stream: BOS Typewriter Crashes system
10733
10734 Time: While system is running.
10735
10736 Meaning: The system was unable to allocate a dumper bit map
10737 in dbm_seg for the volume on dskX_NNS. Too many
10738 volumes are online or there is something wrong
10739 with the volume header.
10740
10741 Action: Follow normal recovery procedures.
10742
10743
10744 dbm_man 186 08/21/20 MR12.7^L
10745
10746
10747
10748
10749 dbm_man.pl1
10750 dbm_man: unable to initialize area: ERROR_MESS
10751
10752
10753 Stream: BOS Typewriter Crashes system
10754
10755 Time: While system is running.
10756
10757 Meaning: This indicates a logic error in the supervisor or
10758 CPU or memory hardware problems.
10759
10760 Action: Follow normal recovery procedures.
10761
10762
10763 deactivate_for_demount.pl1
10764 deactivate_for_demount: Error freeing vtocx OOOO
10765 on dskX_NN for UID. ERRORMESSAGE.
10766
10767
10768 Stream: Logged in SYSERR log.
10769
10770 Time: During system shutdown.
10771
10772 Meaning: The VTOCE for a deciduous segment could not be
10773 freed for the reason indicated. The VTOCE will be
10774 freed by the next volume salvage or by
10775 delete_old_pdds.
10776
10777 Action: No operator action is required.
10778
10779
10780 deactivate_segs.pl1
10781 deactivate_segs: unflushed trailer
10782
10783
10784 Stream: BOS Typewriter Crashes system
10785
10786 Time: While system is running.
10787
10788 Meaning: After destroying a process the system found that
10789 some system trailer specifying connection of that
10790 process to some segment still exists for that
10791 process in str_seg. This indicates that some
10792 segment was improperly disconnected from the
10793 process at some time.This indicates a logic error
10794 in the supervisor or CPU or memory hardware
10795 problems.
10796
10797 Action: Follow normal recovery procedures.
10798
10799
10800
10801
10802 debug_check 187 08/21/20 MR12.7^L
10803
10804
10805
10806
10807 debug_check.pl1
10808 debug_check: too many parameters on parm cards
10809
10810
10811 Stream: BOS Typewriter.
10812
10813 Time: System Intialization.
10814
10815 Meaning: A total of 14 options may be specified on PARM
10816 cards. This limit has been exceeded. Options
10817 after the 14th will be ignored.
10818
10819 Action: Correct the configuration deck before the next
10820 bootload.
10821
10822
10823
10824 obs_reconfigure.pl1
10825 delcpu: Cannot stop CPU X.
10826
10827
10828 Stream: Initializer process output.
10829
10830 Time: In response to an operator command.
10831
10832 Meaning: CPU X did not respond to a command to stop within
10833 the expected time. The CPU may be malfunctioning
10834 or in STEP or it may be in a very tight loop.
10835
10836 Action: Check the CPU panel. If the processor appears to
10837 be in a loop it may be possible to break it out
10838 by placing zeros in the processor switches and
10839 using the EXECUTE button to cause a fault; but
10840 this action sometimes causes the system to crash
10841 depending on where the loop is.
10842
10843
10844
10845 obs_reconfigure.pl1
10846 delcpu: CPU X is not online.
10847
10848
10849 Stream: Initializer process output.
10850
10851 Time: In response to an operator command.
10852
10853 Meaning: A delcpu X command finds that CPU X is already
10854 deleted.
10855
10856 Action: No operator action is required.
10857
10858
10859
10860 delcpu 188 08/21/20 MR12.7^L
10861
10862
10863
10864
10865 obs_reconfigure.pl1
10866 delcpu: CPU X is the only CPU.
10867
10868
10869 Stream: Initializer process output.
10870
10871 Time: In response to an operator command.
10872
10873 Meaning: A delcpu X command attempted to delete the last
10874 CPU. No action was taken.
10875
10876 Action: No operator action is required.
10877
10878
10879 obs_reconfigure.pl1
10880 delcpu: Illegal command or subroutine argument.
10881 BLAH
10882
10883
10884 Stream: Initializer process output.
10885
10886 Time: In response to an operator command.
10887
10888 Meaning: Invalid input was typed.
10889
10890 Action: Enter a corrected command line.
10891
10892
10893 obs_reconfigure.pl1
10894 delcpu: Reconfiguration database is locked.
10895
10896
10897 Stream: Initializer process output.
10898
10899 Time: In response to an operator command.
10900
10901 Meaning: Another process is performing reconfiguration
10902 currently or a fault during reconfiguration has
10903 left the reconfiguration tables locked.
10904
10905 Action: If it is certain that no other process is
10906 reconfiguring and that the fault which
10907 interrupted reconfiguration has been cured the
10908 reconfigure$force_unlock command may be used to
10909 clear the lock at the direction of system staff.
10910
10911
10912
10913 obs_reconfigure.pl1
10914 delcpu: Wrong number of arguments supplied.
10915
10916
10917
10918 delcpu 189 08/21/20 MR12.7^L
10919
10920
10921 Stream: Initializer process output.
10922
10923 Time: In response to an operator command.
10924
10925 Meaning: Invalid input was typed.
10926
10927 Action: Enter a corrected command line.
10928
10929
10930 delentry.pl1
10931 delentry: deleting damaged dir PATH for USERID
10932
10933
10934 Stream: Logged in SYSERR log.
10935
10936 Time: While system is running.
10937
10938 Meaning: An attempt to delete a directory found that the
10939 directory header had a zero UID. The directory
10940 was deleted anyway.
10941
10942 Action: No operator action is required.
10943
10944
10945 delentry.pl1
10946 delentry: error from hash$out on "NAME" for
10947 USERID. ERROR_CODE
10948
10949
10950 Stream: Logged in SYSERR log.
10951
10952 Time: While system is running.
10953
10954 Meaning: An attempt to delete the entry name NAME from the
10955 directory hash table failed. This indicates a
10956 logic error in the supervisor or CPU or memory
10957 hardware problems.
10958
10959 Action: No operator action is required.
10960
10961
10962 delentry.pl1
10963 delentry: error from terminate_ for USERID.
10964 ERROR_CODE
10965
10966
10967 Stream: Logged in SYSERR log.
10968
10969 Time: While system is running.
10970
10971 Meaning: An error code was returned while trying to make a
10972 directory unknown while deleting it. This
10973
10974
10975
10976 delentry 190 08/21/20 MR12.7^L
10977
10978
10979 indicates a logic error in the supervisor or CPU
10980 or memory hardware problems.
10981
10982 Action: No operator action is required.
10983
10984
10985 delentry.pl1
10986 delentry: priv_dfile error deleting vtoce for
10987 PATH for USERID. ERROR_CODE
10988
10989
10990 Stream: Logged in SYSERR log.
10991
10992 Time: While system is running.
10993
10994 Meaning: A privileged call to delete a segment discovered a
10995 branch with not VTOC entry. This situation is
10996 called a "connection failure." The branch was
10997 deleted anyway.
10998
10999 Action: No operator action is required.
11000
11001
11002 delete_vtoce.pl1
11003 delete_vtoce: cannot add time/page product
11004 SEGTPP DIRTPP to pvid PPP vtocx VVV uid UUU
11005 ERRORMESSAGE
11006
11007
11008
11009 Stream: Logged in SYSERR log.
11010
11011 Time: While system is running.
11012
11013 Meaning: During the deletion of a directory which had a
11014 quota account a difficulty was encountered in
11015 reflecting its time/page product upward. SEGTPP
11016 and DIRTPP are the time/page product for segments
11017 and directories respectively.
11018
11019 Action: Contact the system programming staff._sa
11020
11021
11022 delete_vtoce.pl1
11023 delete_vtoce: from quotaw pvid PPP. vtocx VVV
11024 ERRORMESSAGE
11025
11026
11027 Stream: Logged in SYSERR log.
11028
11029 Time: While system is running.
11030
11031
11032
11033
11034 delete_vtoce 191 08/21/20 MR12.7^L
11035
11036
11037 Meaning: While deleting a directory which had a quota
11038 account a quota handling problem usually record
11039 quota overflow was encountered.
11040
11041 Action: No operator action is required.
11042
11043
11044 obs_reconfigure.pl1
11045 Deleted CPU X.
11046
11047
11048 Stream: Initializer process output.
11049
11050 Time: In response to an operator command.
11051
11052 Meaning: This is the response to a successful delcpu X
11053 command.
11054
11055 Action: No operator action is required.
11056
11057
11058 obs_reconfigure.pl1
11059 delmain: Abs wired pages in memory.
11060
11061
11062 Stream: Initializer process output.
11063
11064 Time: In response to an operator command.
11065
11066 Meaning: A delmain command attempted to delete a range of
11067 pages which included some pages which cannot be
11068 deleted. No action was taken.
11069
11070 Action: Enter a corrected command line.
11071
11072
11073 obs_reconfigure.pl1
11074 delmain: Illegal command or subroutine argument.
11075 BLAH
11076
11077
11078 Stream: Initializer process output.
11079
11080 Time: In response to an operator command.
11081
11082 Meaning: Invalid input was typed.
11083
11084 Action: Enter a corrected command line.
11085
11086
11087 obs_reconfigure.pl1
11088 delmain: Not enough main memory left.
11089
11090
11091
11092 delmain 192 08/21/20 MR12.7^L
11093
11094
11095 Stream: Initializer process output.
11096
11097 Time: In response to an operator command.
11098
11099 Meaning: A delmain command attempted to delete so much
11100 memory that the system would be unable to function
11101 correctly. No action was taken.
11102
11103 Action: Enter a corrected command line.
11104
11105
11106 obs_reconfigure.pl1
11107 delmain: Reconfiguration database is locked.
11108
11109
11110 Stream: Initializer process output.
11111
11112 Time: In response to an operator command.
11113
11114 Meaning: Another process is performing reconfiguration
11115 currently or a fault during reconfiguration has
11116 left the reconfiguration tables locked.
11117
11118 Action: If it is certain that no other process is
11119 reconfiguring and that the fault which
11120 interrupted reconfiguration has been cured the
11121 reconfigure$force_unlock command may be used to
11122 clear the lock at the direction of system staff.
11123
11124
11125
11126 obs_reconfigure.pl1
11127 delmain: Request is not within range of a single
11128 controller. MAIN XXX
11129
11130
11131 Stream: Initializer process output.
11132
11133 Time: In response to an operator command.
11134
11135 Meaning: A delmain command must specify a range of pages
11136 which lies completely within one controller. No
11137 action was taken.
11138
11139 Action: Enter a corrected command line.
11140
11141
11142 obs_reconfigure.pl1
11143 delmain: Wrong number of arguments supplied.
11144
11145
11146 Stream: Initializer process output.
11147
11148
11149
11150 delmain 193 08/21/20 MR12.7^L
11151
11152
11153 Time: In response to an operator command.
11154
11155 Meaning: Invalid input was typed.
11156
11157 Action: Enter a corrected command line.
11158
11159
11160 obs_reconfigure.pl1
11161 delmem: Abs wired pages in MEM Y.
11162
11163
11164 Stream: Initializer process output.
11165
11166 Time: In response to an operator command.
11167
11168 Meaning: An attempt was made to delete a memory which
11169 included some pages which cannot be deleted. No
11170 action was taken.
11171
11172 Action: The memory cannot be deleted.
11173
11174
11175 obs_reconfigure.pl1
11176 delmem: Illegal command or subroutine argument.
11177 BLAH
11178
11179
11180 Stream: Initializer process output.
11181
11182 Time: In response to an operator command.
11183
11184 Meaning: Invalid input was typed.
11185
11186 Action: Enter a corrected command line.
11187
11188
11189 obs_reconfigure.pl1
11190 delmem: MEM Y is not online.
11191
11192
11193 Stream: Initializer process output.
11194
11195 Time: In response to an operator command.
11196
11197 Meaning: A delmem Y command was typed but no such memory is
11198 in use.
11199
11200 Action: No operator action is required.
11201
11202
11203 obs_reconfigure.pl1
11204 delmem: Not enough main memory to remove MEM Y.
11205
11206
11207
11208 delmem 194 08/21/20 MR12.7^L
11209
11210
11211 Stream: Initializer process output.
11212
11213 Time: In response to an operator command.
11214
11215 Meaning: The system would be unable to function correctly
11216 if SCU Y and its memory were deleted. No action
11217 was taken.
11218
11219 Action: Try something else.
11220
11221
11222 obs_reconfigure.pl1
11223 delmem: Reconfiguration database is locked.
11224
11225
11226 Stream: Initializer process output.
11227
11228 Time: In response to an operator command.
11229
11230 Meaning: Another process is performing reconfiguration
11231 currently or a fault during reconfiguration has
11232 left the reconfiguration tables locked.
11233
11234 Action: If it is certain that no other process is
11235 reconfiguring and that the fault which
11236 interrupted reconfiguration has been cured the
11237 reconfigure$force_unlock command may be used to
11238 clear the lock at the direction of system staff.
11239
11240
11241
11242 add_scu.pl1
11243 delmem: Removed MEM X.
11244
11245
11246 Stream: BOS Typewriter.
11247
11248 Time: In response to an operator command.
11249
11250 Meaning: The system control unit X has been deleted.
11251
11252 Action: No operator action is required.
11253
11254
11255 obs_reconfigure.pl1
11256 delmem: Wrong number of arguments supplied.
11257
11258
11259 Stream: Initializer process output.
11260
11261 Time: In response to an operator command.
11262
11263 Meaning: Invalid input was typed.
11264
11265
11266 delmem 195 08/21/20 MR12.7^L
11267
11268
11269 Action: Enter a corrected command line.
11270
11271
11272 demount_pv.pl1
11273 demount_pv: ast out of sync
11274
11275
11276 Stream: BOS Typewriter Crashes system
11277
11278 Time: Volume demounting or system shutdown.
11279
11280 Meaning: The volume demounter has detected irreparable
11281 damage to the system segment table SST.
11282
11283 Action: Emergency shutdown will fail and need not be
11284 attempted. Follow normal recovery procedures for
11285 ESD failure.
11286
11287
11288
11289 demount_pv.pl1
11290 demount_pv: ioi_PROGNAME for DRIVENAME:
11291 ERRORMESSAGE
11292
11293
11294 Stream: BOS Typewriter.
11295
11296 Time: Volume demounting.
11297
11298 Meaning: In attempting to cycle down drive DRIVENAME an
11299 unexpected error was received from the I/O
11300 Interfacer. The drive may not be cycled down.
11301
11302 Action: Notify the system programming staff. Cycle down
11303 the drive if it was not cycled down.
11304
11305
11306 demount_pv.pl1
11307 demount_pv: vtoc cleanup of DRIVENAME:
11308 ERRORMESSAGE
11309
11310
11311 Stream: BOS Typewriter.
11312
11313 Time: Volume demounting or shutdown.
11314
11315 Meaning: An unexpected error was encountered in flushing
11316 VTOC information out to a volume being shut down
11317 or demounted. The volume will not be demounted.
11318 message.
11319
11320 Action: Contact the system programming staff. Attempt to
11321 repeat the demount of the logical volume if this
11322
11323
11324 demount_pv 196 08/21/20 MR12.7^L
11325
11326
11327 is not during shutdown. The physical volume
11328 involved may have to be salvaged.
11329
11330
11331
11332 demount_pv.pl1
11333 demounted DRIVENAME
11334
11335
11336 Stream: BOS Typewriter.
11337
11338 Time: Volume demounting in response to delete_lv
11339 command or user action.
11340
11341 Meaning: The disk pack on drive DRIVENAME was successfully
11342 demounted.
11343
11344 Action: No operator action is required.
11345
11346
11347 disk_table_.pl1
11348 demounted lv LVNAME
11349
11350
11351 Stream: Initializer process output.
11352
11353 Time: While system is running.
11354
11355 Meaning: The demount of the logical volume LVNAME is
11356 complete.
11357
11358 Action: No operator action is required.
11359
11360
11361 device_acct_.pl1
11362 device_acct_$init: ERROR_MESSAGE. device_table
11363
11364
11365 Stream: as severity 2
11366
11367 Time: System Intialization.
11368
11369 Meaning: An error occurred which initializing the
11370 device_table. ERROR_MESSAGE is the text
11371 associated with the error code describing the
11372 error. Device accounting is disabled and system
11373 initialization fails.
11374
11375 Action: Contact the system programming staff.
11376
11377
11378 device_acct_.pl1
11379
11380
11381
11382 device_acct_$off 197 08/21/20 MR12.7^L
11383
11384
11385 device_acct_$off: device N ACCT_TYPE_NAME
11386 DEV_NAME not in device table for PERSON.PROJECT
11387
11388
11389 Stream: as severity 0
11390
11391 Time: While system is running.
11392
11393 Meaning: Device DEV_NAME which has device accounting type
11394 number N associated with ACCT_TYPE_NAME devices
11395 was not found in PERSON.PROJECT's device table
11396 entries. Probable cause is damage to the device
11397 table.
11398
11399 Action: Contact the system programming staff._sa
11400
11401
11402 device_acct_.pl1
11403 device_acct_: deve.pdtep PTR1 not = ute.pdtep
11404 PTR2 for PERSON.PROJECT.
11405
11406
11407 Action: as severity 2
11408
11409 Time: While system is running.
11410
11411 Meaning: The Project Definition Table entry pointer PTR1
11412 stored in the device table for PERSON.PROJECT
11413 differs from the PDT entry pointer stored in that
11414 user's User Table Entry UTE.This indicates a
11415 logic error in the supervisor or CPU or memory
11416 hardware problems.
11417
11418 Action: Contact the system programming staff.
11419
11420
11421 device_acct_.pl1
11422 device_acct_: ERROR_MESSAGE. Attempting to lock
11423 PDT entry of PERSON.PROJECT
11424
11425
11426 Stream: as severity 2
11427
11428 Time: While system is running.
11429
11430 Meaning: An attempt was made to lock the Project Definition
11431 Table PDT entry for PERSON.PROJECT to update
11432 device usage charges for the user. Locking did
11433 not succeed within 15 seconds so the charges were
11434 not updated. If the attempt occurred during an
11435 accounting update the charges will continue to
11436 accrue until the next update at which time
11437 locking the PDT entry is again attempted. If the
11438
11439
11440 device_acct_ 198 08/21/20 MR12.7^L
11441
11442
11443 original attempt occurred as part of a logout or
11444 new_proc operation the device charges are lost.
11445
11446 Action: Contact the system programming staff._sa
11447
11448
11449 page_error.alm
11450 device_control: invalid pvtx XX
11451
11452
11453 Stream: BOS Typewriter Crashes system
11454
11455 Time: While system is running.
11456
11457 Meaning: An invalid PVT index XX was found by device
11458 control or an invalid device type appeared in the
11459 PVT entry of that index. This indicates a logic
11460 error in the supervisor or CPU or memory hardware
11461 problems.
11462
11463 Action: Follow normal recovery procedures.
11464
11465
11466 page_error.alm
11467 device_control: invalid pvtx XX
11468
11469
11470 Stream: BOS Typewriter Crashes system
11471
11472 Time: While system is running.
11473
11474 Meaning: An invalid PVT index XX was found by device
11475 control or an invalid device type appeared in the
11476 PVT entry of that index. This indicates a logic
11477 error in the supervisor or CPU or memory hardware
11478 problems.
11479
11480 Action: Follow normal recovery procedures.
11481
11482
11483 dial_ctl_.pl1
11484 dial_ctl_: Autocall channel CHANNEL declared
11485 multi-class but does not support
11486 set_required_access_class.
11487
11488
11489 Stream: as severity2
11490
11491 Time: While system is running._
11492
11493 Meaning: The autocall channel CHANNEL has been declared
11494 multi-class in the CDT but the underlying
11495 multiplexer does not support the
11496
11497
11498 dial_ctl_ 199 08/21/20 MR12.7^L
11499
11500
11501 set_required_access_class control order. The
11502 channel should be defined as single class. The
11503 user's dial out request was refused.
11504
11505 Action: Contact the system programming staff._sa
11506
11507
11508 dial_ctl_.pl1
11509 dial_ctl_: Can't find process WWWWWWWWWWW
11510
11511
11512 Stream: as severity0
11513
11514 Time: While system is running.
11515
11516 Meaning: An invalid signal was received by the secondary
11517 terminal manager.
11518
11519 Action: Note for system programmer action.
11520
11521
11522 dial_ctl_.pl1
11523 dial_ctl_: Channel CHANNEL AIM_CLASS SERV_TYPE
11524 hung up on Initializer
11525
11526
11527 Stream: as severity1
11528
11529 Time: While system is running.
11530
11531 Meaning: The channel CHANNEL with access class AIM_CLASS
11532 and service type SERV_TYPE hung up. It had
11533 previously been dialed to the Initializer.
11534
11535 Action: No operator action is required.
11536
11537
11538 dial_ctl_.pl1
11539 dial_ctl_: Channel CHANNEL AIM_CLASS SERV_TYPE
11540 hung up on missing process WWWWWWWWWWWW
11541
11542
11543 Stream: as severity1
11544
11545 Time: While system is running.
11546
11547 Meaning: The channel CHANNEL with access class AIM_CLASS
11548 and service type SERV_TYPE hung up. It had been
11549 dialed to a process but the system cannot
11550 determine what process it had been connected to.
11551 The process may have terminated before the hangup
11552 was detected.
11553
11554
11555
11556 dial_ctl_ 200 08/21/20 MR12.7^L
11557
11558
11559 Action: If this happens often inform the programming
11560 staff.
11561
11562
11563 dial_ctl_.pl1
11564 dial_ctl_: Channel CHANNEL dialed to Initializer
11565 PERSON.PROJECT
11566
11567
11568 Stream: as severity2
11569
11570 Time: While system is running.
11571
11572 Meaning: An additional secondary terminal has been attached
11573 to the Initializer process as a result of a dial
11574 system command. CHANNEL specifies which terminal
11575 dialed Initializer.
11576
11577 Action: If this terminal has been connected to the
11578 Initializer by an authorized operations staff
11579 member proceed to use it by issuing an "accept"
11580 command and possibly the "substty" command. If
11581 this is an invalid attempt to connect to the
11582 system type "drop CHANNEL" to disconnect the
11583 terminal.
11584
11585
11586
11587 dial_ctl_.pl1
11588 dial_ctl_: Channel CHANNEL hung up after dial_out
11589 for PERSON.PROJECT
11590
11591
11592 Stream: as severity0
11593
11594 Time: While system is running.
11595
11596 Meaning: During a dial_out of channel CHANNEL by
11597 PERSON.PROJECT the channel hung up. The dial_out
11598 attempt was aborted.
11599
11600 Action: No operator action is required.
11601
11602
11603 dial_ctl_.pl1
11604 dial_ctl_: Dialing channel CHANNEL ACC_CLASS to
11605 DESTINATION for PERSON.PROJECT using comm
11606 privilege
11607
11608
11609 Stream: as severity0
11610
11611 Time: While system is running.
11612
11613
11614 dial_ctl_ 201 08/21/20 MR12.7^L
11615
11616
11617 Meaning: The user PERSON.PROJECT is dialing out on dial
11618 channel CHANNEL with access class ACC_CLASS to the
11619 destination DESTINATION. If this log message ends
11620 with "using comm privilege" then the process
11621 dialing out has used the comm privilege to
11622 circumvent AIM restrictions.
11623
11624 Action: No operator action is required.
11625
11626
11627 dial_ctl_.pl1
11628 dial_ctl_: ERROR_MESSAGE From
11629 get_required_access_class control order on channel
11630 CHANNEL.
11631
11632
11633 Stream: as severity0
11634
11635 Time: While system is running.
11636
11637 Meaning: While attempting to determine whether the channel
11638 CHANNEL had any access class restrictions imposed
11639 on it by the hardcore ERROR_MESSAGE was returned.
11640 The request in progress was aborted.
11641
11642 Action: Note for system programmer action.
11643
11644
11645 dial_ctl_.pl1
11646 dial_ctl_: ERROR_MESSAGE. Can't find PNT entry:
11647 PERSON_ID
11648
11649
11650 Stream: as severity2
11651
11652 Time: While system is running.
11653
11654 Meaning: An attempt was made to find the Person Name Table
11655 entry of the PERSON_ID specified in a dial
11656 preaccess command. However an error occurred
11657 which searching in the PNT.
11658
11659 Action: Contact the system programming staff._sa
11660
11661
11662 dial_ctl_.pl1
11663 dial_ctl_: ERROR_MESSAGE. dial_out CHANNEL for
11664 PERSON.PROJECT failed.
11665
11666
11667 Stream: as severity0
11668
11669 Time: While system is running.
11670
11671
11672 dial_ctl_ 202 08/21/20 MR12.7^L
11673
11674
11675 Meaning: While attempting to dial_out channel CHANNEL for
11676 PERSON.PROJECT the error ERROR_MESSAGE occured.
11677 The dial_out attempt was aborted.
11678
11679 Action: No operator action is required.
11680
11681
11682 dial_ctl_.pl1
11683 dial_ctl_: ERROR_MESSAGE. after dial_out order
11684 CHANNEL for PERSON.PROJECT
11685
11686
11687 Stream: as severity0
11688
11689 Time: While system is running.
11690
11691 Meaning: The user PERSON.PROJECT is attempting a dial_out
11692 of channel CHANNEL. The dial_out control order
11693 produced the error ERROR_MESSAGE. The dial_out
11694 attempt is aborted.
11695
11696 Action: Note for system programmer action.
11697
11698
11699 dial_ctl_.pl1
11700 dial_ctl_: ERROR_MESSAGE. Attempting to detach
11701 CHANNEL from PERSON.PROJECT
11702
11703
11704 Stream: as severity0
11705
11706 Time: While system is running.
11707
11708 Meaning: An attempt to disconnect channel CHANNEL from
11709 PERSON.PROJECT failed. ERROR_MESSAGE explains
11710 why.
11711
11712 Action: Note for system programmer action.
11713
11714
11715 dial_ctl_.pl1
11716 dial_ctl_: ERROR_MESSAGE. call to
11717 astty_$tty_new_proc of CHANNEL for PERSON.PROJECT
11718 failed
11719
11720
11721 Stream: as severity0
11722
11723 Time: While system is running.
11724
11725 Meaning: An attempt to connect the channel CHANNEL to
11726 PERSON.PROJECT failed. ERROR_MESSAGE indicates
11727 why.
11728
11729
11730 dial_ctl_ 203 08/21/20 MR12.7^L
11731
11732
11733 Action: Contact the system programming staff._sa
11734
11735
11736 dial_ctl_.pl1
11737 dial_ctl_: ERROR_MESSAGE. Could not check access
11738 to >sc1>admin_acs>tandd.acs for PERSON.PROJECT.
11739
11740
11741 Stream: as severity0
11742
11743 Time: While system is running.
11744
11745 Meaning: The user PERSON.PROJECT attempted to tandd_attach
11746 a communications channel. This operation is
11747 controlled by rw access to the ACS segment
11748 specified. For the reason ERROR_MESSAGE the
11749 answering service could not check access to the
11750 segment. The user tandd_attach request was
11751 refused.
11752
11753 Action: Contact the system programming staff._sa
11754
11755
11756 dial_ctl_.pl1
11757 dial_ctl_: ERROR_MESSAGE. getting
11758 dial_out_status or tty info CHANNEL for
11759 PERSON.PROJECT
11760
11761
11762 Stream: as severity0
11763
11764 Time: While system is running.
11765
11766 Meaning: During a dial_out of channel CHANNEL by
11767 PERSON.PROJECT the error ERROR_MESSAGE was
11768 returned while attempting to determine if the
11769 dial_out control order succeeded or failed.
11770
11771 Action: No operator action is required.
11772
11773
11774 dial_ctl_.pl1
11775 dial_ctl_: ERROR_MESSAGE. Issuing tandd_attach
11776 control order for channel CHAN
11777
11778
11779 Stream: as severity0
11780
11781 Time: While system is running.
11782
11783 Meaning: The user PERSON.PROJECT attempted to tandd_attach
11784 a communications channel which failed for the
11785
11786
11787
11788 dial_ctl_ 204 08/21/20 MR12.7^L
11789
11790
11791 reason given by ERROR_MESSAGE. The user
11792 tandd_attach request was refused.
11793
11794 Action: Contact the system programming staff._sa
11795
11796
11797 dial_ctl_.pl1
11798 dial_ctl_: ndialed negative CHANNEL
11799
11800
11801 Stream: as severity0
11802
11803 Time: While system is running.
11804
11805 Meaning: The count of secondary consoles for a user is in
11806 error. A terminal is hanging up which claims to
11807 be attached to a user but his count of attached
11808 terminals is zero.
11809
11810 Action: Note for system programmer action.
11811
11812
11813 dial_ctl_.pl1
11814 dial_ctl_: Program error.
11815 as_request_sender.version N not correct in dial
11816 request. Should be M.
11817
11818
11819 Stream: as severity1
11820
11821 Time: While system is running.
11822
11823 Meaning: There is a mismatch in the version number used by
11824 the the programs as_request_server_ and dial_ctl_
11825 for the as_request_sender_ structure.
11826
11827 Action: Contact the system programming staff.
11828
11829
11830 dial_ctl_.pl1
11831 dial_ctl_: Refused unknown request from
11832 PERSON.PROJECT; ERROR_MESSAGE REASON
11833
11834
11835 Stream: as severity0
11836
11837 Time: While system is running.
11838
11839 Meaning: PERSON.PROJECT send a dial_server request to the
11840 Initializer of unknown format. It was rejected
11841 for the reasons specified in ERROR_MESSAGE and
11842 REASON.
11843
11844
11845
11846 dial_ctl_ 205 08/21/20 MR12.7^L
11847
11848
11849
11850
11851 dial_ctl_.pl1
11852 dial_ctl_: Rejected unknown request from
11853 PERSON.PROJECT. No request flags set in
11854 dial_server_request.
11855
11856
11857 Stream: as severity0
11858
11859 Time: While system is running.
11860
11861 Meaning: The user PERSON.PROJECT attempted to send an
11862 dial_server request to the Initializer but failed
11863 to specify what type of request he/she wanted.
11864
11865 Action: No operator action is required.
11866
11867
11868 dial_ctl_.pl1
11869 dial_ctl_: sat.ht has PROJECT_ID sat has
11870 OTHER_PROJECT_ID at LOC.
11871
11872
11873 Stream: as severity2
11874
11875 Time: While system is running.
11876
11877 Meaning: The System Administrator's Table is inconsistent
11878 with the location information in its hash table.
11879
11880 Action: Contact the system programming staff._sa
11881
11882
11883 dial_ctl_.pl1
11884 dial_ctl_: Tracing turned off
11885
11886
11887 Stream: as severity1
11888
11889 Time: While system is running.
11890
11891 Meaning: A system administrator has disabled dial_ctl_
11892 tracing.
11893
11894 Action: No operator action is required.
11895
11896
11897 dial_ctl_.pl1
11898 dial_ctl_: Tracing turned on.
11899
11900
11901 Stream: as severity1
11902
11903
11904 dial_ctl_ 206 08/21/20 MR12.7^L
11905
11906
11907 Time: While system is running.
11908
11909 Meaning: A system administrator had enabled tracing of the
11910 dial_ctl_ program. Many status messages will be
11911 logged and printed on the console.
11912
11913 Action: No operator action is required.
11914
11915
11916 dial_ctl_.pl1
11917 DIALIN PERSON1.PROJECT1 CHANNEL to QUALIFIER
11918 PERSON2.PROJECT2
11919
11920
11921 Stream: as severity0
11922
11923 Time: While system is running.
11924
11925 Meaning: A user on channel CHANNEL has used the "dial"
11926 preaccess command to dial the dial qualifier
11927 QUALIFIER owned by PERSON2.PROJECT2. If the
11928 check_acs "slave_dial" flags was on for the
11929 channel then PERSON1.PROJECT1 specifies the
11930 identified user.
11931
11932 Action: No operator action is required.
11933
11934
11935 dial_ctl_.pl1
11936 DIALIN DENIED PERSON1.PROJECT1 CHANNEL to
11937 QUALIFIER PERSON2.PROJECT2 REASON
11938
11939
11940 Stream: as severity0
11941
11942 Time: While system is running.
11943
11944 Meaning: A user on channel CHANNEL attempted to use the
11945 "dial" preaccess command to dial to QUALIFIER
11946 owned by PERSON2.PROJECT2. The attempt was
11947 rejected for REASON. If the channel check_acs
11948 "slave_dial" flag was on then PERSON1.PROJECT1
11949 specifies the identified user on this channel.
11950
11951 Action: Note for system programmer action.
11952
11953
11954 dialup_.pl1
11955 dialup_: answer table damaged at UTEP
11956 tra_vec=TTTT
11957
11958
11959 Stream: as severity 2
11960
11961
11962 dialup_ 207 08/21/20 MR12.7^L
11963
11964
11965 Time: While system is running.
11966
11967 Meaning: The tra_vec value was found to be invalid for an
11968 answer table wakeup. Damage to the answer table
11969 is indicated.
11970
11971 Action: Contact the system programming staff.
11972
11973
11974 dialup_.pl1
11975 dialup_: called while ansp = null
11976
11977
11978 Stream: as severity 2
11979
11980 Time: While system is running.
11981
11982 Meaning: A programming error in the Answering Service or an
11983 incorrect library installation has caused the
11984 Answering Service to be called before being
11985 initialized. The system will ignore the error and
11986 attempt to continue.
11987
11988 Action: Shut down the system and perform a bootload
11989 operation.
11990
11991
11992 dialup_.pl1
11993 dialup_: called with bad ptr EVENT_MSG_PTR by
11994 WWWWWWWWWWWW
11995
11996
11997 Stream: as severity 2
11998
11999 Time: While system is running.
12000
12001 Meaning: A programming error in the interprocess
12002 communication system the network software or the
12003 Answering Service itself has occurred. An invalid
12004 message pointer has been passed to the Answering
12005 Service. The system ignores the message and
12006 attempts to continue. This message may be the
12007 result of an incorrect library installation.
12008
12009 Action: Shut down the system and perform a bootload
12010 operation.
12011
12012
12013 dialup_.pl1
12014 dialup_: called with null message ptr
12015
12016
12017 Stream: as severity 2
12018
12019
12020 dialup_ 208 08/21/20 MR12.7^L
12021
12022
12023 Time: While system is running.
12024
12025 Meaning: A programming error in the interprocess
12026 communication system the network software or the
12027 Answering Service itself has occurred. An invalid
12028 message pointer has been passed to the Answering
12029 Service. The system ignores the message and
12030 attempts to continue. This message may be the
12031 result of an incorrect library installation.
12032
12033 Action: Shut down the system and perform a bootload
12034 operation. Inform the system programming staff.
12035
12036
12037
12038 dialup_.pl1
12039 dialup_: cancelling inactivity bump of
12040 PERSON.PROJECT
12041
12042
12043 Stream: as severity 1
12044
12045 Time: While system is running.
12046
12047 Meaning: This is a logging message indicating that the
12048 PERSON.PROJECT process that had been previously
12049 bumped due to inactivity has become active. The
12050 automatic logout was therefore cancelled. The
12051 user will receive a message to this effect.
12052
12053 Action: No operator action is required.
12054
12055
12056 dialup_.pl1
12057 dialup_: CDT damaged at CDTEP tra_vec=TTTT
12058
12059
12060 Stream: as severity 2
12061
12062 Time: While system is running.
12063
12064 Meaning: The tra_vec value was found to be invalid for a
12065 channel wakeup. Damage to the CDT is indicated.
12066
12067 Action: Contact the system programming staff.
12068
12069
12070 dialup_.pl1
12071 dialup_: cdte CDTEP CHANNEL state M in use N -
12072 notify system programmer"
12073
12074
12075 Stream: as severity 0
12076
12077
12078 dialup_ 209 08/21/20 MR12.7^L
12079
12080
12081 Time: While system is running.
12082
12083 Meaning: This indicates a logic error in the supervisor or
12084 CPU or memory hardware problems.
12085
12086 Action: Contact the system programming staff.
12087
12088
12089 dialup_.pl1
12090 dialup_: cdtep = null and ate.active = DDDD for
12091 UTEP
12092
12093
12094 Stream: as severity 2
12095
12096 Time: While system is running.
12097
12098 Meaning: This indicates a logic error in the supervisor or
12099 CPU or memory hardware problems.
12100
12101 Action: Contact the system programming staff.
12102
12103
12104 dialup_.pl1
12105 dialup_: channel_error called with cdte in
12106 functional state.
12107
12108
12109 Stream: as severity 1
12110
12111 Time: While system is running.
12112
12113 Meaning: This indicates a logic error in the supervisor or
12114 CPU or memory hardware problems.
12115
12116 Action: Contact the system programming staff.
12117
12118
12119 dialup_.pl1
12120 dialup_: error - event calls were masked
12121
12122
12123 Stream: as severity 1
12124
12125 Time: While system is running.
12126
12127 Meaning: This message indicates a serious error in the
12128 Initializer programs. The system attempts to
12129 recover and keep running.
12130
12131 Action: Contact the system programming staff.
12132
12133
12134
12135
12136 dialup_ 210 08/21/20 MR12.7^L
12137
12138
12139 dialup_.pl1
12140 dialup_: ERROR_MESSAGE Getting pointer to help
12141 file SYS_DIR>ENTRY_NAME
12142
12143
12144 Stream: as severity 2
12145
12146 Time: While system is running.
12147
12148 Meaning: An ERROR_MESSAGE was returned when an attempt was
12149 made to find the login_help or connect_help
12150 segment in the SYS_DIR usually >sc1.
12151
12152 Action: Contact the system programming staff.
12153
12154
12155 dialup_.pl1
12156 dialup_: ERROR_MESSAGE setting new tty info for
12157 CHANNEL
12158
12159
12160 Stream: as severity 0
12161
12162 Time: While system is running.
12163
12164 Meaning: An ERROR_MESSAGE was returned by a call to
12165 cpg_$set_pit_tty_info when setting new terminal
12166 attributes in a reconnected process on channel
12167 CHANNEL.
12168
12169 Action: Contact the system programming staff.
12170
12171
12172 dialup_.pl1
12173 dialup_: ERROR_MESSAGE Unable to declare handler
12174 for ev chn EVENT_CHN for ate UTEP for CDT_CHANNEL
12175
12176
12177 Stream: as severity 2
12178
12179 Time: While system is running.
12180
12181 Meaning: An ERROR_MESSAGE was returned when an attempt was
12182 made to declare an event call channel for new
12183 process UTEP on EVENT_CHN attached to
12184 CDT_CHANNEL.
12185
12186 Action: Contact the system programming staff.
12187
12188
12189 dialup_.pl1
12190 dialup_: ERROR_MESSAGE attempting to allocate a
12191 user table entry for CHANNEL
12192
12193
12194 dialup_ 211 08/21/20 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/21/20 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/21/20 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/21/20 MR12.7^L
12369
12370
12371 dialup_.pl1
12372 dialup_: ignored SSSS for CHANNEL
12373 st=DDDDinuse=UUUUtv=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=DDDDinuse=UUUUtv=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 CDTEPCHANNEL tv=TRAVECinuse=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/21/20 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/21/20 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/21/20 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=XXdisc_com=YYdisc_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/21/20 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 CDTEPCHANNEL 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/21/20 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/21/20 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/21/20 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 CDTEPCHANNEL
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/21/20 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/21/20 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: Adding channel ICC.
12933
12934
12935 Stream: BOS Typewriter.
12936
12937 Time: While system is running.
12938
12939 Meaning: A message to confirm that channel ICC has been
12940 added to the system in response to a reconfigure
12941 command.
12942
12943 Action: No operator action is required.
12944
12945
12946
12947
12948 disk_control 224 08/21/20 MR12.7^L
12949
12950
12951
12952
12953 disk_control.pl1
12954 disk_control: dskX_NN now operational.
12955
12956
12957 Stream: BOS Typewriter.
12958
12959 Time: While system is running.
12960
12961 Meaning: A disk drive which required intervention has
12962 successfully completed an I/O operation. The
12963 system will again use its contents.
12964
12965 Action: No operator action is required.
12966
12967
12968 disk_control.pl1
12969 disk_control: dskX_NN now operational.
12970
12971
12972 Stream: BOS Typewriter.
12973
12974 Time: While system is running.
12975
12976 Meaning: A disk drive which required intervention has
12977 successfully completed an I/O operation. The
12978 system will again use its contents.
12979
12980 Action: No operator action is required.
12981
12982
12983 disk_control.pl1
12984 disk_control: dskX_NN requires intervention.
12985
12986
12987 Stream: BOS Typewriter sounds beeper
12988
12989 Time: While system is running.
12990
12991 Meaning: A disk error has occurred which could have been
12992 caused by the pack or drive being broken or
12993 requiring operator attention. The system has
12994 retried the operation an appropriate number of
12995 times without success. The system will try the
12996 device periodically to check if it has been
12997 repaired.
12998
12999 Action: Inspect the device. If it is not ready ready it.
13000 If it is ready try unreadying and re-readying it.
13001 If the drive cannot be made ready contact
13002 Customer Service personnel.
13003
13004
13005
13006 disk_control 225 08/21/20 MR12.7^L
13007
13008
13009
13010
13011 disk_control.pl1
13012 disk_control: dskX_NN requires intervention.
13013
13014
13015 Stream: BOS Typewriter sounds beeper
13016
13017 Time: While system is running.
13018
13019 Meaning: A disk error has occurred which could have been
13020 caused by the pack or drive being broken or
13021 requiring operator attention. The system has
13022 retried the operation an appropriate number of
13023 times without success. The system will try the
13024 device periodically to check if it has been
13025 repaired.
13026
13027 Action: Inspect the device. If it is not ready ready it.
13028 If it is ready try unreadying and re-readying it.
13029 If the drive cannot be made ready contact
13030 Customer Service personnel.
13031
13032
13033
13034 disk_control.pl1
13035 disk_control: MAJOR_STAT SUBSTAT for dskX_NN
13036 channel ICC.
13037 rec RRRR sect SSSS main AAAA
13038 detailed status: XX XX XX XX XX XX XX XX
13039
13040
13041
13042 Stream: BOS Typewriter.
13043
13044 Time: While system is running.
13045
13046 Meaning: A disk error has occurred on drive dskX_NN. The
13047 major status and substatus are interpreted as
13048 character strings. The disk address is given both
13049 as a Multics record address in octal and as an
13050 absolute sector number in octal. The main store
13051 address being used was AAAA octal. The third line
13052 gives the hexadecimal value of the detailed status
13053 in cases where this data is useful. See manual
13054 AN87 System Formats for interpretation of this
13055 information.
13056
13057 Action: Note for Customer Service action. The segment
13058 involved in a disk error can often be identified
13059 by an application of the "record_to_vtocx" tool to
13060 the Multics record number given in the message.
13061
13062
13063
13064 disk_control 226 08/21/20 MR12.7^L
13065
13066
13067
13068
13069 disk_control.pl1
13070 disk_control: MAJOR_STAT SUBSTAT for dskX_NN
13071 channel ICC.
13072 rec RRRR sect SSSS main AAAA
13073 detailed status: XX XX XX XX XX XX XX XX
13074
13075
13076
13077 Stream: BOS Typewriter.
13078
13079 Time: While system is running.
13080
13081 Meaning: A disk error has occurred on drive dskX_NN. The
13082 major status and substatus are interpreted as
13083 character strings. The disk address is given both
13084 as a Multics record address in octal and as an
13085 absolute sector number in octal. The main store
13086 address being used was AAAA octal. The third line
13087 gives the hexadecimal value of the detailed status
13088 in cases where this data is useful. See manual
13089 AN87 System Formats for interpretation of this
13090 information.
13091
13092 Action: Note for Customer Service action. The segment
13093 involved in a disk error can often be identified
13094 by an application of the "record_to_vtocx" tool to
13095 the Multics record number given in the message.
13096
13097
13098
13099 disk_control.pl1
13100 disk_control: MAJOR_STAT SUBSTAT for dskX_NN
13101 channel ICC.
13102 rec RRRR sect SSSS main AAAA
13103 subvol V logical rec OOOO logical sect TTTT
13104 detailed status: XX XX XX XX XX XX XX XX
13105
13106
13107
13108 Stream: BOS Typewriter.
13109
13110 Time: While system is running.
13111
13112 Meaning: A disk error has occurred on drive dskX_NN. The
13113 major status and substatus are interpreted as
13114 character strings. The disk address is given both
13115 as a Multics record address in octal and as an
13116 absolute sector number in octal. The main store
13117 address being used was AAAA octal. The subvolume
13118 name is V the logical device name is dskX_NNV
13119 the logical record address is OOOO octal and the
13120
13121
13122 disk_control 227 08/21/20 MR12.7^L
13123
13124
13125 logical sector number is TTTT octal. The fourth
13126 line gives the hexadecimal value of the detailed
13127 status in cases where this data is useful. See
13128 manual AN87 System Formats for interpretation of
13129 this information.
13130
13131 Action: Note for Customer Service action. The segment
13132 involved in a disk error can often be identified
13133 by an application of the "record_to_vtocx" tool to
13134 the Multics logical record number given in the
13135 message.
13136
13137
13138
13139 disk_control.pl1
13140 disk_control: MAJOR_STAT SUBSTAT for dskX_NN
13141 channel ICC.
13142 rec RRRR sect SSSS main AAAA
13143 subvol V logical rec OOOO logical sect TTTT
13144 detailed status: XX XX XX XX XX XX XX XX
13145
13146
13147
13148 Stream: BOS Typewriter.
13149
13150 Time: While system is running.
13151
13152 Meaning: A disk error has occurred on drive dskX_NN. The
13153 major status and substatus are interpreted as
13154 character strings. The disk address is given both
13155 as a Multics record address in octal and as an
13156 absolute sector number in octal. The main store
13157 address being used was AAAA octal. The subvolume
13158 name is V the logical device name is dskX_NNV
13159 the logical record address is OOOO octal and the
13160 logical sector number is TTTT octal. The fourth
13161 line gives the hexadecimal value of the detailed
13162 status in cases where this data is useful. See
13163 manual AN87 System Formats for interpretation of
13164 this information.
13165
13166 Action: Note for Customer Service action. The segment
13167 involved in a disk error can often be identified
13168 by an application of the "record_to_vtocx" tool to
13169 the Multics logical record number given in the
13170 message.
13171
13172
13173
13174 disk_control.pl1
13175 disk_control: Placing dskX_NN in operation.
13176
13177
13178
13179
13180 disk_control 228 08/21/20 MR12.7^L
13181
13182
13183 Stream: BOS Typewriter.
13184
13185 Time: While system is running.
13186
13187 Meaning: A special interrupt has been received for a disk
13188 drive marked as broken. The system will attempt
13189 to use the device.
13190
13191 Action: No operator action is required.
13192
13193
13194 disk_control.pl1
13195 disk_control: Placing dskX_NN in operation.
13196
13197
13198 Stream: BOS Typewriter.
13199
13200 Time: While system is running.
13201
13202 Meaning: A special interrupt has been received for a disk
13203 drive marked as broken. The system will attempt
13204 to use the device.
13205
13206 Action: No operator action is required.
13207
13208
13209 disk_control.pl1
13210 disk_control: Queuing error.
13211
13212
13213 Stream: BOS Typewriter Crashes system
13214
13215 Time: While system is running.
13216
13217 Meaning: This indicates a logic error in the supervisor or
13218 CPU or memory hardware problems.
13219
13220 Action: Follow normal recovery procedures.
13221
13222
13223 disk_control.pl1
13224 disk_control: Queuing error.
13225
13226
13227 Stream: BOS Typewriter Crashes system
13228
13229 Time: While system is running.
13230
13231 Meaning: This indicates a logic error in the supervisor or
13232 CPU or memory hardware problems.
13233
13234 Action: Follow normal recovery procedures.
13235
13236
13237
13238 disk_control 229 08/21/20 MR12.7^L
13239
13240
13241
13242
13243 disk_control.pl1
13244 disk_control: Reconnected IO_TYPE I/O on dskX_NN
13245 channel ICC.
13246
13247
13248 Stream: BOS Typewriter. and/or $log
13249
13250 Time: While system is running.
13251
13252 Meaning: A disk interrupt was apparently lost. Status for
13253 the disk did not arrive within the expected time.
13254 This may be an indication of a channel or
13255 controller malfunction. The system restarts the
13256 disk operation.
13257
13258 Action: No operator action is required. Unless these
13259 messages persist which may indicate a hardware
13260 malfunction that needs investigation. Some types
13261 of channel adapters and/or disk controllers can be
13262 "reset" in an attempt to correct the condition.
13263
13264
13265
13266 disk_control.pl1
13267 disk_control: Reconnected IO_TYPE I/O on dskX_NN
13268 channel ICC.
13269
13270
13271 Stream: BOS Typewriter. and/or $log
13272
13273 Time: While system is running.
13274
13275 Meaning: A disk interrupt was apparently lost. Status for
13276 the disk did not arrive within the expected time.
13277 This may be an indication of a channel or
13278 controller malfunction. The system restarts the
13279 disk operation.
13280
13281 Action: No operator action is required. Unless these
13282 messages persist which may indicate a hardware
13283 malfunction that needs investigation. Some types
13284 of channel adapters and/or disk controllers can be
13285 "reset" in an attempt to correct the condition.
13286
13287
13288
13289 disk_control.pl1
13290 disk_control: Removing channel ICC.
13291
13292
13293 Stream: BOS Typewriter sounds beeper
13294
13295
13296 disk_control 230 08/21/20 MR12.7^L
13297
13298
13299 Time: While system is running.
13300
13301 Meaning: Errors occurred indicative of a defective disk
13302 channel or MPC. The channel receiving the errors
13303 is placed offline.
13304
13305 Action: Contact the system programming staff. Also inform
13306 Customer Service personnel.
13307
13308
13309
13310 disk_control.pl1
13311 disk_control: Removing channel ICC.
13312
13313
13314 Stream: BOS Typewriter sounds beeper
13315
13316 Time: While system is running.
13317
13318 Meaning: Errors occurred indicative of a defective disk
13319 channel or MPC. The channel receiving the errors
13320 is placed offline.
13321
13322 Action: Contact the system programming staff. Also inform
13323 Customer Service personnel.
13324
13325
13326
13327 disk_control.pl1
13328 disk_control: Unexpected IOM status SSSS for
13329 dskX_NN channel ICC.
13330
13331
13332 Stream: BOS Typewriter.
13333
13334 Time: While system is running.
13335
13336 Meaning: Status has been received from a channel which was
13337 not marked active. This is due to a disk
13338 subsystem or IOM problem or to a logic error in
13339 the supervisor. See manual AN87 System Formats
13340 for an interpretation of the status SSSS. The
13341 system ignores the status and attempts to continue
13342 operation.
13343
13344 Action: No operator action is required.
13345
13346
13347 disk_control.pl1
13348 disk_control: Unexpected IOM status SSSS for
13349 dskX_NN channel ICC.
13350
13351
13352
13353
13354 disk_control 231 08/21/20 MR12.7^L
13355
13356
13357 Stream: BOS Typewriter.
13358
13359 Time: While system is running.
13360
13361 Meaning: Status has been received from a channel which was
13362 not marked active. This is due to a disk
13363 subsystem or IOM problem or to a logic error in
13364 the supervisor. See manual AN87 System Formats
13365 for an interpretation of the status SSSS. The
13366 system ignores the status and attempts to continue
13367 operation.
13368
13369 Action: No operator action is required.
13370
13371
13372 disk_emergency.pl1
13373 disk_emergency: DSKX_NN inoperative; shutdown of
13374 DSKX_NN suspended
13375
13376
13377 Stream: BOS Typewriter sounds beeper
13378
13379 Time: Emergency shutdown.
13380
13381 Meaning: During emergency shutdown DSKX_NN was found
13382 inoperative. Data in main memory or on the paging
13383 device which need to be flushed to the pack on
13384 DSKX_NN cannot be written out. The data remain
13385 where they were and ESD may be tried again.
13386
13387 Action: If the drive can be made ready make it ready and
13388 try ESD again. Do NOT move packs before trying
13389 ESD unless address plugs are changed so that the
13390 same pack appears to have the same address. If
13391 this action is performed the MPC must be halted
13392 and restarted with a reset and branch. If the
13393 pack is not successfully shut down the system
13394 will volume salvage it when it is next brought up
13395 and data from main memory which belongs on the
13396 pack will be lost.
13397
13398
13399
13400 disk_init.pl1
13401 disk_init: Devices D1 and D2 of DSKn must have
13402 the same model number.
13403
13404
13405 Stream: BOS Typewriter Crashes system
13406
13407 Time: System Intialization.
13408
13409
13410
13411
13412 disk_init 232 08/21/20 MR12.7^L
13413
13414
13415 Meaning: Two devices that share a common spindle have been
13416 configured with different model numbers.
13417
13418 Action: Correct the config deck and reboot.
13419
13420
13421 disk_init.pl1
13422 disk_init: Disk model XXXX not found in
13423 config_data_.
13424
13425
13426 Stream: BOS Typewriter Crashes system
13427
13428 Time: System Intialization.
13429
13430 Meaning: This indicates a logic error in the supervisor or
13431 CPU or memory hardware problems.
13432
13433 Action: Follow normal recovery procedures. Fix the
13434 configuration deck and reboot.
13435
13436
13437
13438 disk_init.pl1
13439 disk_init: DSKn D1 must be configured if DSKn D2
13440 is configured.
13441
13442
13443 Stream: BOS Typewriter Crashes system
13444
13445 Time: System Intialization.
13446
13447 Meaning: Only one of a pair of devices that share a common
13448 spindle has been configured.
13449
13450 Action: Change the config deck to include the missing
13451 device and reboot.
13452
13453
13454 disk_init.pl1
13455 disk_init: error WWWW from absadr for DSKX iom N
13456 ch ZZ.
13457
13458
13459 Stream: BOS Typewriter Crashes system
13460
13461 Time: System Intialization.
13462
13463 Meaning: This indicates a logic error in the supervisor or
13464 CPU or memory hardware problems.
13465
13466 Action: Follow normal recovery procedures. $boot_tape
13467
13468
13469
13470 disk_init 233 08/21/20 MR12.7^L
13471
13472
13473
13474
13475 disk_init.pl1
13476 disk_init: Invalid channel on CHNL DSKx card.
13477
13478
13479 Stream: BOS Typewriter Crashes system
13480
13481 Time: System Intialization.
13482
13483 Meaning: An invalid channel specification was found on the
13484 CHNL card for DSKx.
13485
13486
13487 disk_init.pl1
13488 disk_init: Invalid channel on PRPH DSKx card.
13489
13490
13491
13492 Stream: BOS Typewriter Crashes system
13493
13494 Time: System Intialization.
13495
13496 Meaning: An invalid channel specification was found on the
13497 PRPH DSKx card.
13498
13499
13500 disk_init.pl1
13501 disk_init: Invalid format for XXXX card.
13502
13503
13504 Stream: BOS Typewriter Crashes system
13505
13506 Time: System Intialization.
13507
13508 Meaning: A required field on the XXXX card is not present.
13509
13510 Action: Follow normal recovery procedures. Fix the
13511 configuration deck and reboot.
13512
13513
13514
13515 disk_init.pl1
13516 disk_init: No valid disk models found on PRPH
13517 DSKx card.
13518
13519
13520 Stream: BOS Typewriter Crashes system
13521
13522 Time: System Intialization.
13523
13524 Meaning: All disk model fields were found to be zero.
13525
13526
13527
13528 disk_init 234 08/21/20 MR12.7^L
13529
13530
13531 Action: Fix the configuration deck and reboot.
13532
13533
13534 disk_init.pl1
13535 disk_init: Too many channels configured for DSKn.
13536 Limit is N.
13537
13538
13539 Stream: BOS Typewriter Crashes system
13540
13541 Time: System Intialization.
13542
13543 Meaning: The per subsystem software limit for logical
13544 channels has been exceeded.
13545
13546 Action: Fix the config deck and reboot. If more channels
13547 are needed split the configuration into more
13548 subsystems in the config deck.
13549
13550
13551
13552 disk_init.pl1
13553 disk_init: Too many devices configured for DSKn.
13554 Max device is N.
13555
13556
13557 Stream: BOS Typewriter Crashes system
13558
13559 Time: System Intialization.
13560
13561 Meaning: The software limit for devices per subsystem has
13562 been exceeded.
13563
13564 Action: Fix the config deck and reboot.
13565
13566
13567 disk_init.pl1
13568 disk_init: Unable to assign CCCC for DSKx.
13569
13570
13571 Stream: BOS Typewriter Crashes system
13572
13573 Time: System Intialization.
13574
13575 Meaning: An error has occurred trying to assign an IOM
13576 channel for the disk subsystem DSKX.
13577
13578 Action: Follow normal recovery procedures. Check the
13579 configuration deck and the operability of the
13580 hardware before rebooting.
13581
13582
13583
13584
13585
13586 disk_init 235 08/21/20 MR12.7^L
13587
13588
13589 disk_init.pl1
13590 disk_init: Unknown model number NNNN on PRPH
13591 dskN.
13592
13593
13594 Stream: BOS Typewriter Crashes system
13595
13596 Time: System Intialization.
13597
13598 Meaning: The model number NNNN on the prph card for disk
13599 subsystem N is invalid.
13600
13601 Action: Correct the config deck and reboot.
13602
13603
13604 disk_reader.pl1
13605 disk_reader: Attempt to read past end of mst
13606 area.
13607
13608
13609 Stream: BOS Typewriter Crashes system
13610
13611 Time: System Intialization.
13612
13613 Meaning: An attempt was made to read more data from the mst
13614 area of disk than was placed there from the MST.
13615 This is most likely the result of an MST misformed
13616 originally.
13617
13618 Action: Follow normal recovery procedures. $boot_tape
13619
13620
13621
13622 disk_reader.pl1
13623 disk_reader: Attempt to read past end of mst
13624 area.
13625
13626
13627 Stream: BOS Typewriter Crashes system
13628
13629 Time: System Intialization.
13630
13631 Meaning: An attempt was made to read more data from the mst
13632 area of disk than was placed there from the MST.
13633 This is most likely the result of an MST misformed
13634 originally.
13635
13636 Action: Follow normal recovery procedures. $boot_tape
13637
13638
13639
13640 disk_rebuild.pl1
13641
13642
13643
13644 disk_rebuild 236 08/21/20 MR12.7^L
13645
13646
13647 disk_rebuild: Disk rebuild finished with errors:
13648 ERRORMESS
13649
13650
13651 Stream: $salvout
13652
13653 Time: $dskr
13654
13655 Meaning: The disk rebuild has been aborted due to the
13656 indicated ERRORMESS.
13657
13658 Action: Contact the system programming staff.
13659
13660
13661 disk_rebuild.pl1
13662 disk_rebuild: base of paging region changed from
13663 XXX. to YYY.
13664
13665
13666 Stream: $salvout
13667
13668 Time: $dskr
13669
13670 Meaning: The base of the paging region for the new pack is
13671 different from that for the old one.
13672
13673 Action: No operator action is required.
13674
13675
13676 disk_rebuild.pl1
13677 disk_rebuild: Begin disk rebuild of DSKX_NNs
13678 onto DSKY_MMs
13679
13680
13681 Stream: $salvout
13682
13683 Time: $dskr
13684
13685 Meaning: This message is printed when disk rebuilding
13686 begins.
13687
13688 Action: No operator action is required.
13689
13690
13691 disk_rebuild.pl1
13692 disk_rebuild: Cannot compress VTOC on dskX_NNs
13693 because active VTOCEs in the truncated region.
13694
13695
13696
13697 Stream: $salvout
13698
13699 Time: $dskr
13700
13701
13702 disk_rebuild 237 08/21/20 MR12.7^L
13703
13704
13705 Meaning: A rebuild was requested in which the number of
13706 VTOCEs on the new volume was smaller than the
13707 number of VTOCEs on the old volume. This is
13708 permitted only if there are no active VTOCEs in
13709 the truncated region that is no active VTOCEs on
13710 the old volume have VTOCE indices which would be
13711 too high for the new volume.
13712
13713 Action: Run sweep_pv -from num_vtoces to remove these
13714 VTOCEs from the old volume and retry the rebuild.
13715 It may be necessary to salvage the volume to
13716 recover lost VTOCEs in the truncated region.
13717
13718
13719
13720 disk_rebuild.pl1
13721 disk_rebuild: copying XXX. rec of part NAME
13722
13723
13724 Stream: $salvout
13725
13726 Time: $dskr
13727
13728 Meaning: A disk rebuild is reformatting a pack which
13729 contains non-paging partitions. The contents of
13730 these partitions are copied exactly.
13731
13732 Action: No operator action is required.
13733
13734
13735 disk_rebuild.pl1
13736 disk_rebuild: Disk rebuild finished.
13737
13738
13739 Stream: $salvout
13740
13741 Time: $dskr
13742
13743 Meaning: The disk rebuild has completed.
13744
13745 Action: No operator action is required.
13746
13747
13748 disk_rebuild.pl1
13749 disk_rebuild: dskX_NNs must be mounted for
13750 rebuild.
13751
13752
13753 Stream: $salvout
13754
13755 Time: $dskr
13756
13757 Meaning: The "from" volume must be mounted for the rebuild.
13758
13759
13760 disk_rebuild 238 08/21/20 MR12.7^L
13761
13762
13763 Action: Mount the logical volume to which the "from"
13764 volume belongs and try the rebuild abain.
13765
13766
13767
13768 disk_rebuild.pl1
13769 disk_rebuild: dskX_NNs must not be mounted for
13770 rebuild.
13771
13772
13773 Stream: $salvout
13774
13775 Time: $dskr
13776
13777 Meaning: The "to" volume must not be mounted to the Storage
13778 System for a rebuild.
13779
13780 Action: Demount the logical volume to which the volume
13781 belongs and retry the rebuild.
13782
13783
13784
13785 disk_rebuild.pl1
13786 disk_rebuild: End of rebuilding. New summary
13787 report follows:
13788
13789
13790 Stream: $salvout
13791
13792 Time: $dskr
13793
13794 Meaning: Rebuilding has completed. A summary report of the
13795 new volume parameter is printed.
13796
13797 Action: No operator action is required.
13798
13799
13800 disk_rebuild.pl1
13801 disk_rebuild: Error from read_disk aborting:
13802 ERRORMESS
13803
13804
13805 Stream: $salvout
13806
13807 Time: $dskr
13808
13809 Meaning: This indicates a logic error in the supervisor or
13810 CPU or memory hardware problems. The disk rebuild
13811 is aborted.
13812
13813 Action: Contact the system programming staff.
13814
13815
13816
13817
13818 disk_rebuild 239 08/21/20 MR12.7^L
13819
13820
13821 disk_rebuild.pl1
13822 disk_rebuild: Error from write_disk aborting:
13823 ERRORMESS
13824
13825
13826 Stream: $salvout
13827
13828 Time: $dskr
13829
13830 Meaning: This indicates a logic error in the supervisor or
13831 CPU or memory hardware problems. The disk rebuild
13832 is aborted.
13833
13834 Action: Contact the system programming staff.
13835
13836
13837 disk_rebuild.pl1
13838 disk_rebuild: Error writing label: ERRORMESS
13839
13840
13841 Stream: $salvout
13842
13843 Time: $dskr
13844
13845 Meaning: A disk error has occurred writing the new label
13846 during a disk rebuild. The disk rebuild is
13847 aborted.
13848
13849 Action: Correct the problem and issue a new command.
13850
13851
13852 disk_rebuild.pl1
13853 disk_rebuild: freeing deciduous vtocx XXXo: NAME
13854
13855
13856 Stream: $salvout
13857
13858 Time: $dskr
13859
13860 Meaning: The segment originally named NAME at vtoc index
13861 XXXo was deciduous and has been deleted from the
13862 RPV. This is debugging output printed for system
13863 programmers if a SALV DEBG card is supplied.
13864
13865 Action: No operator action is required.
13866
13867
13868 disk_rebuild.pl1
13869 disk_rebuild: freeing process vtocx XXXo: NAME
13870
13871
13872 Stream: $salvout
13873
13874
13875
13876 disk_rebuild 240 08/21/20 MR12.7^L
13877
13878
13879 Time: $dskr
13880
13881 Meaning: The segment originally named NAME at vtoc index
13882 XXXo was per-process and has been deleted. This
13883 is debugging output printed for system programmers
13884 if a SALV DEBG card is used.
13885
13886 Action: No operator action is required.
13887
13888
13889 disk_rebuild.pl1
13890 disk_rebuild: INIT_TABLES: aste pool WWWo too
13891 small
13892
13893
13894 Stream: BOS Typewriter.
13895
13896 Time: While system is running.
13897
13898 Meaning: The physical volume salvager was unable to obtain
13899 the necessary temporary AST entries for its work
13900 segments. No salvaging was done.
13901
13902 Action: Shut down manually correct the SST card and
13903 reboot. Then salvage all volumes since the
13904 indicator that volumes need salvaging may have
13905 been lost.
13906
13907
13908
13909 disk_rebuild.pl1
13910 disk_rebuild: Map of assigned addresses changed
13911
13912
13913 Stream: $salvout
13914
13915 Time: $dskr
13916
13917 Meaning: If any corrections were made to the map on the
13918 volume which shows which addresses are free and
13919 which are in use this message is printed. If the
13920 volume was not properly shut down this message is
13921 to be expected.
13922
13923 Action: No operator action is required.
13924
13925
13926 disk_rebuild.pl1
13927 disk_rebuild: NN vtoces added to list of free
13928 vtoces.
13929
13930
13931 Stream: $salvout
13932
13933
13934 disk_rebuild 241 08/21/20 MR12.7^L
13935
13936
13937 Time: $dskr
13938
13939 Meaning: NN free VTOC entries were found while salvaging
13940 and added to the list of free VTOC entries. This
13941 is a normal message.
13942
13943 Action: No operator action is required.
13944
13945
13946 disk_rebuild.pl1
13947 disk_rebuild: no. of free recs changed from OLD.
13948 to NEW.
13949
13950
13951 Stream: $salvout
13952
13953 Time: $dskr
13954
13955 Meaning: If The number of free records in the volume label
13956 is changed by a volume salvage this message is
13957 printed. If the volume was not properly shut
13958 down this message is to be expected.
13959
13960 Action: No operator action is required.
13961
13962
13963 disk_rebuild.pl1
13964 disk_rebuild: no. of free vtoces changed from
13965 OLD. to NEW.
13966
13967
13968 Stream: $salvout
13969
13970 Time: $dskr
13971
13972 Meaning: If the number of free VTOC entries in the volume
13973 label is changed by a volume salvage this message
13974 is printed.
13975
13976 Action: No operator action is required.
13977
13978
13979 disk_rebuild.pl1
13980 disk_rebuild: not enough free records only XXX.
13981 for increase need YYY.
13982
13983
13984 Stream: $salvout
13985
13986 Time: $dskr
13987
13988 Meaning: An attempt was made to increase the size of some
13989 partitions or of the VTOC. This required a
13990
13991
13992 disk_rebuild 242 08/21/20 MR12.7^L
13993
13994
13995 decrease in the size of the paging region. The
13996 paging region is too full to be shrunk as
13997 required. The disk rebuild is aborted.
13998
13999 Action: Issue a different disk_rebuild command or bring
14000 up Multics and delete some segments from the pack
14001 before trying again.
14002
14003
14004
14005 disk_rebuild.pl1
14006 disk_rebuild: out of room on vtocx XXXo page
14007 YYYo
14008
14009
14010 Stream: $salvout
14011
14012 Time: $dskr
14013
14014 Meaning: This indicates a logic error in the supervisor or
14015 CPU or memory hardware problems. The disk rebuild
14016 is aborted.
14017
14018 Action: Contact the system programming staff.
14019
14020
14021 disk_rebuild.pl1
14022 disk_rebuild: processing VTOCE #XXX.
14023
14024
14025 Stream: BOS Typewriter.
14026
14027 Time: $dskr
14028
14029 Meaning: This message indicates that a disk rebuild is
14030 progressing normally. It is printed every 1000.
14031 VTOC entries.
14032
14033 Action: No operator action is required.
14034
14035
14036 disk_rebuild.pl1
14037 disk_rebuild: Read error accessing VTOC Map of
14038 dskX_NNs
14039
14040
14041 Stream: $salvout
14042
14043 Time: $dskr
14044
14045 Meaning: This indicates a logic error in the supervisor or
14046 CPU or memory hardware problems. The rebuild is
14047 aborted.
14048
14049
14050 disk_rebuild 243 08/21/20 MR12.7^L
14051
14052
14053 Action: Contact the system programming staff.
14054
14055
14056 disk_rebuild.pl1
14057 disk_rebuild: reading vtocx XXXo: ERRORMESS
14058
14059
14060 Stream: $salvout
14061
14062 Time: $dskr
14063
14064 Meaning: This indicates a logic error in the supervisor or
14065 CPU or memory hardware problems.
14066
14067 Action: Contact the system programming staff.
14068
14069
14070 disk_rebuild.pl1
14071 disk_rebuild: salv cleanup debugging stop dump
14072 and type go
14073
14074
14075 Stream: BOS Typewriter Crashes system
14076
14077 Time: During disk rebuild
14078
14079 Meaning: A disk rebuild has aborted due to a crawlout and
14080 the debug switch is set. This message causes the
14081 system to return to BCE so that a dump can be
14082 taken.
14083
14084 Action: Follow programmer instructions.
14085
14086
14087 disk_rebuild.pl1
14088 disk_rebuild: same drive specified for source and
14089 copy aborting
14090
14091
14092 Stream: $salvout
14093
14094 Time: During disk rebuilding
14095
14096 Meaning: The operator attempted to specify the same drive
14097 as input and output. No action was taken.
14098
14099 Action: Enter a corrected command.
14100
14101
14102 disk_rebuild.pl1
14103 disk_rebuild: Summary of original disk contents
14104 follows:
14105
14106
14107
14108 disk_rebuild 244 08/21/20 MR12.7^L
14109
14110
14111 Stream: $salvout
14112
14113 Time: $dskr
14114
14115 Meaning: A summary report of the volume parameters before
14116 rebuilding is printed.
14117
14118 Action: No operator action is required.
14119
14120
14121 disk_rebuild.pl1
14122 disk_rebuild: Summary Report
14123 Volume PVNAME of logical volume LVNAME.
14124
14125 Paging region begins at record DD. WWo for LL.
14126 XXo records.
14127 DD. WWo free records therein.
14128 Label/VTOC size is RR. records MM. VTOCEs.
14129 VTOC version X. TTT. free VTOCEs.
14130
14131 Partition Map
14132 Name Start Length
14133
14134 NAME DDD. WWWo DDD. WWWo
14135 ______ _______
14136 DDD. WWWo
14137
14138 Volume size is DDDD. YYYYo records total.
14139
14140 DD. damaged segments.
14141
14142
14143
14144 Stream: $salvout
14145
14146 Time: During disk rebuilding.
14147
14148 Meaning: This is a report summarizing physical volume
14149 parameters printed by the disk rebuilder both
14150 before and after rebuilding. The partition map is
14151 omitted if no partitions are defined on the
14152 volume.
14153
14154 Action: No operator action is required.
14155
14156
14157 disk_rebuild.pl1
14158 disk_rebuild: vtocx XXXo NAME branch unconnected
14159 due to YYYo
14160
14161
14162 Stream: $salvout
14163
14164
14165
14166 disk_rebuild 245 08/21/20 MR12.7^L
14167
14168
14169 Time: $dskr
14170
14171 Meaning: This is debugging output produced only if the
14172 debug switch is on during a disk rebuild with
14173 branch checking. It informs the system
14174 programmers of the reasons for connection failure.
14175
14176 Action: No operator action is required.
14177
14178
14179 disk_table_.pl1
14180 disk_table_: "KEY" is not "io" "storage_system"
14181 or "ss".
14182
14183
14184 Stream: Initializer process output.
14185
14186 Time: While system is running.
14187
14188 Meaning: The operator issued an set_drive_usage DRIVE KEY
14189 command. KEY is invalid.
14190
14191 Action: Enter a corrected command line.
14192
14193
14194 mdx.pl1
14195 disk_table_: accepted PV PVNAME on DSKX_NN
14196
14197
14198 Stream: Logged in SYSERR log.
14199
14200 Time: In response to an operator command. System
14201 Intialization.
14202
14203 Meaning: A storage system physical volume has been placed
14204 in use. The volume and drive name are identified.
14205
14206 Action: No operator action is required. This message is
14207 provided for the benefit of automatic error
14208 analysis and logging.
14209
14210
14211
14212 mdx.pl1
14213 disk_table_: Added drive DSKX_NN
14214
14215
14216 Stream: BOS Typewriter.
14217
14218 Time: In response to an operator command.
14219
14220 Meaning: The operator has added a storage system disk drive
14221 with adddev.
14222
14223
14224 disk_table_ 246 08/21/20 MR12.7^L
14225
14226
14227 Action: No operator action is required.
14228
14229
14230 disk_table_.pl1
14231 disk_table_: cannot locate DRIVE
14232
14233
14234 Stream: Initializer process output.
14235
14236 Time: While system is running.
14237
14238 Meaning: A del_vol DRIVE command was issued but there is no
14239 such drive in the configuration.
14240
14241 Action: Enter a corrected command line.
14242
14243
14244 disk_table_.pl1
14245 disk_table_: cannot locate DRIVE
14246
14247
14248 Stream: Initializer process output.
14249
14250 Time: While system is running.
14251
14252 Meaning: A command specifying DRIVE was issued but no such
14253 drive can be found.
14254
14255 Action: Enter a corrected command line.
14256
14257
14258 disk_table_.pl1
14259 disk_table_: cannot locate DRIVE
14260
14261
14262 Stream: Initializer process output.
14263
14264 Time: While system is running.
14265
14266 Meaning: A disk_rebuild command cannot locate the output
14267 drive.
14268
14269 Action: Enter a corrected command line.
14270
14271
14272 disk_table_.pl1
14273 disk_table_: cannot reregister from ring 4
14274
14275
14276 Stream: Initializer process output.
14277
14278 Time: While system is running.
14279
14280
14281
14282 disk_table_ 247 08/21/20 MR12.7^L
14283
14284
14285 Meaning: A reregister command was issued from ring 4.
14286
14287 Action: Enter a corrected command line.
14288
14289
14290 disk_table_.pl1
14291 disk_table_: Cannot verify label of DRIVE:
14292 REASON
14293
14294
14295 Stream: Initializer process output.
14296
14297 Time: While system is running.
14298
14299 Meaning: An error occurred checking the label of DRIVE.
14300 Usually either the drive is not ready or the pack
14301 label does not match the required pack label.
14302
14303 Action: Enter a corrected command line.
14304
14305
14306 disk_table_.pl1
14307 disk_table_: Could not finish demount of lv
14308 LVNAME
14309
14310
14311 Stream: Initializer process output.
14312
14313 Time: While system is running.
14314
14315 Meaning: The system encountered a problem trying to delete
14316 the logical volume LVNAME.
14317
14318 Action: Contact the system programming staff.
14319
14320
14321 mdx.pl1
14322 disk_table_: Deleted drive DSKX_NN
14323
14324
14325 Stream: BOS Typewriter.
14326
14327 Time: In response to an operator command.
14328
14329 Meaning: The operator has deleted a storage system disk
14330 drive with deldev.
14331
14332 Action: No operator action is required.
14333
14334
14335 mdx.pl1
14336 disk_table_: Deleted root PV "PV_NAME" on
14337 DSKX_NN.
14338
14339
14340 disk_table_ 248 08/21/20 MR12.7^L
14341
14342
14343 Stream: BOS Typewriter sounds beeper
14344
14345 Time: System Intialization.
14346
14347 Meaning: The specified drive did not appear in the ROOT
14348 config card. Thus it was removed from the
14349 disk_table_. This will also occur when the volume
14350 is intentionally deleted.
14351
14352 Action: Contact the system programming staff.
14353
14354
14355 disk_table_.pl1
14356 disk_table_: demounting partially mounted volume
14357 LVNAME
14358
14359
14360 Stream: Initializer process output.
14361
14362 Time: While system is running.
14363
14364 Meaning: The operator issued a dlv LVNAME command for a
14365 logical volume for which a previous dlv command
14366 did not succeed.
14367
14368 Action: No operator action is required.
14369
14370
14371 disk_table_.pl1
14372 disk_table_: DRIVE in use with PVNAME
14373
14374
14375 Stream: Initializer process output.
14376
14377 Time: While system is running.
14378
14379 Meaning: A del_vol DRIVE command was issued but the drive
14380 is currently in use.
14381
14382 Action: Enter a corrected command line. To demount the
14383 pack use the dlv command.
14384
14385
14386
14387 disk_table_.pl1
14388 disk_table_: DRIVE in use: contains PVNAME
14389
14390
14391 Stream: Initializer process output.
14392
14393 Time: While system is running.
14394
14395 Meaning: An attempt to use DRIVE finds it already in use.
14396
14397
14398 disk_table_ 249 08/21/20 MR12.7^L
14399
14400
14401 Action: Enter a corrected command line.
14402
14403
14404 disk_table_.pl1
14405 disk_table_: DRIVE is an IO drive
14406
14407
14408 Stream: Initializer process output.
14409
14410 Time: While system is running.
14411
14412 Meaning: A command has been issued to affect DRIVE but it
14413 is currently in use as an IO drive.
14414
14415 Action: Enter a corrected command line. Use the
14416 set_drive_usage command to change it if necessary.
14417
14418
14419
14420 disk_table_.pl1
14421 disk_table_: DRIVE is deleted
14422
14423
14424 Stream: Initializer process output.
14425
14426 Time: While system is running.
14427
14428 Meaning: The drive named is deleted.
14429
14430 Action: Enter a corrected command line.
14431
14432
14433 disk_table_.pl1
14434 disk_table_: DRIVE not found.
14435
14436
14437 Stream: Initializer process output.
14438
14439 Time: While system is running.
14440
14441 Meaning: The operator issued an set_drive_usage DRIVE KEY
14442 command but DRIVE is not in the current
14443 configuration.
14444
14445 Action: Enter a corrected command line.
14446
14447
14448 disk_table_.pl1
14449 disk_table_: DRIVE not in use.
14450
14451
14452 Stream: Initializer process output.
14453
14454
14455
14456 disk_table_ 250 08/21/20 MR12.7^L
14457
14458
14459 Time: While system is running.
14460
14461 Meaning: A del_vol command was issued but nothing is on the
14462 drive.
14463
14464 Action: Enter a corrected command line.
14465
14466
14467 disk_table_.pl1
14468 disk_table_: DRIVENAME is an IO drive
14469
14470
14471 Stream: Initializer process output.
14472
14473 Time: While system is running.
14474
14475 Meaning: The operator issued a del_vol command but the
14476 drive is an IO drive.
14477
14478 Action: Enter a corrected command line.
14479
14480
14481 disk_table_.pl1
14482 disk_table_: DRIVENAME is deleted
14483
14484
14485 Stream: Initializer process output.
14486
14487 Time: While system is running.
14488
14489 Meaning: A del_vol command was issued but the drive has
14490 been deleted.
14491
14492 Action: Enter a corrected command line.
14493
14494
14495 disk_table_.pl1
14496 disk_table_: ERROR_MESSAGE.
14497
14498
14499 Stream: Initializer process output.
14500
14501 Time: System Intialization.
14502
14503 Meaning: An error has been returned from
14504 initializer_mdc_$init. This indicates a logic
14505 error in the supervisor or CPU or memory hardware
14506 problems. Subsequent attempts to mount volumes
14507 may malfunction.
14508
14509 Action: Contact the system programming staff.
14510
14511
14512
14513
14514 disk_table_ 251 08/21/20 MR12.7^L
14515
14516
14517
14518
14519 disk_table_.pl1
14520 disk_table_: ERROR_MESSAGE.
14521
14522
14523 Stream: Initializer process output.
14524
14525 Time: While system is running.
14526
14527 Meaning: An error has occurred in a storage system disk
14528 manipulation command.
14529
14530 Action: Enter a corrected command line.
14531
14532
14533 disk_table_.pl1
14534 disk_table_: ERROR_MESSAGE. Cannot demount lv
14535 LVNAME
14536
14537
14538 Stream: Initializer process output.
14539
14540 Time: While system is running.
14541
14542 Meaning: A dlv LVNAME command was issued but an error
14543 prevents the dlv from working.
14544
14545 Action: Enter a corrected command line.
14546
14547
14548 disk_table_.pl1
14549 disk_table_: ERROR_MESSAGE. Cannot get volume
14550 registration for the root logical volume.
14551 Shutdown and reboot with "boot nolv".
14552
14553
14554
14555 Stream: Initializer process output.
14556
14557 Time: System Intialization.
14558
14559 Meaning: The system is unable to read the volume
14560 registration for the root logical volume and
14561 cannot therefore determine if the root is
14562 complete.
14563
14564 Action: Shutdown. If you can mount the entire root do
14565 so describe all volumes on the root config card
14566 "boot stan nosc" and fix the registration. If
14567 this fails shutdown and "boot nolv".
14568
14569
14570
14571
14572 disk_table_ 252 08/21/20 MR12.7^L
14573
14574
14575
14576
14577 disk_table_.pl1
14578 disk_table_: ERROR_MESSAGE. cannot stop mount of
14579 LVNAME
14580
14581
14582 Stream: Initializer process output.
14583
14584 Time: While system is running.
14585
14586 Meaning: A dlv LVNAME command was issued but an error
14587 prevents the dlv from working.
14588
14589 Action: Enter a corrected command line.
14590
14591
14592 disk_table_.pl1
14593 disk_table_: ERROR_MESSAGE. Cannot verify label
14594 of DRIVE
14595
14596
14597 Stream: Initializer process output.
14598
14599 Time: While system is running.
14600
14601 Meaning: An error occurred checking the label of the pack
14602 on DRIVE. Usually either the drive is not ready
14603 or the pack label does not match the required pack
14604 label.
14605
14606 Action: Enter a corrected command line.
14607
14608
14609 disk_table_.pl1
14610 disk_table_: ERROR_MESSAGE. Could not demount pv
14611 PVNAME of lv LVNAME DRIVE
14612
14613
14614 Stream: Initializer process output.
14615
14616 Time: While system is running.
14617
14618 Meaning: An error occurred when trying to demount a
14619 physical volume. This may be due to process
14620 directory or wired segments being on this physical
14621 volume. The del_lv command will be partially
14622 successful when this happens.
14623
14624 Action: Determine which processes if any have process
14625 directories on this logical volume and bump or
14626 terminate them. Use list_disks to determine which
14627
14628
14629
14630 disk_table_ 253 08/21/20 MR12.7^L
14631
14632
14633 volumes are still mounted and try dlv again.
14634 Contact the system programming staff.
14635
14636
14637
14638 disk_table_.pl1
14639 disk_table_: ERROR_MESSAGE. error reregistering
14640 DRIVE
14641
14642
14643 Stream: Initializer process output.
14644
14645 Time: While system is running.
14646
14647 Meaning: The reregister DRIVE command did not succeed.
14648
14649 Action: Enter a corrected command line.
14650
14651
14652 disk_table_.pl1
14653 disk_table_: ERROR_MESSAGE. LVNAME
14654
14655
14656 Stream: Initializer process output.
14657
14658 Time: While system is running.
14659
14660 Meaning: An error occurred trying to get the list of
14661 physical volumes which comprise LVNAME.
14662
14663 Action: Enter a corrected command line.
14664
14665
14666 disk_table_.pl1
14667 disk_table_: ERROR_MESSAGE. New disk_table
14668 created
14669
14670
14671 Stream: Initializer process output.
14672
14673 Time: System Intialization.
14674
14675 Meaning: The system has created a new copy of the segment
14676 >disk_table at initialization time. The copy from
14677 the previous bootload could not be found. The
14678 position of all previously mounted volumes has
14679 been forgotten.
14680
14681 Action: Use the av command to specify the position of all
14682 volumes and the alv command to mount them.
14683
14684
14685
14686
14687
14688 disk_table_ 254 08/21/20 MR12.7^L
14689
14690
14691 disk_table_.pl1
14692 disk_table_: ERROR_MESSAGE. salvaging PVNAME on
14693 DRIVE
14694
14695
14696 Stream: Initializer process output.
14697
14698 Time: While system is running.
14699
14700 Meaning: An error occurred while doing a salvage_vol -all.
14701
14702 Action: Enter a corrected command line.
14703
14704
14705 disk_table_.pl1
14706 disk_table_: invalid drive id "ARG"
14707
14708
14709 Stream: Initializer process output.
14710
14711 Time: While system is running.
14712
14713 Meaning: The drive id ARG does not have the form dskX_NN.
14714
14715 Action: Enter a corrected command line.
14716
14717
14718 disk_table_.pl1
14719 disk_table_: lv LVNAME cannot be mounted in
14720 process of demount.
14721
14722
14723 Stream: Initializer process output.
14724
14725 Time: While system is running.
14726
14727 Meaning: An alv LVNAME command was issued but the logical
14728 volume is in the process of demounting.
14729
14730 Action: Enter a corrected command line.
14731
14732
14733 disk_table_.pl1
14734 disk_table_: lv LVNAME already mounted
14735
14736
14737 Stream: Initializer process output.
14738
14739 Time: While system is running.
14740
14741 Meaning: An alv LVNAME command finds LVNAME already
14742 mounted.
14743
14744
14745
14746 disk_table_ 255 08/21/20 MR12.7^L
14747
14748
14749 Action: Enter a corrected command line.
14750
14751
14752 disk_table_.pl1
14753 disk_table_: lv LVNAME not found
14754
14755
14756 Stream: Initializer process output.
14757
14758 Time: While system is running.
14759
14760 Meaning: A dlv LVNAME command was issued but no such
14761 logical volume is mounted.
14762
14763 Action: Enter a corrected command line.
14764
14765
14766 disk_table_.pl1
14767 disk_table_: no drive available for PVNAME LVNAME
14768
14769
14770 Stream: Initializer process output.
14771
14772 Time: While system is running.
14773
14774 Meaning: An alv LVNAME command was unable to allocate a
14775 drive for PVNAME.
14776
14777 Action: Demount some un-needed logical volume and try
14778 again.
14779
14780
14781 disk_table_.pl1
14782 disk_table_: PVNAME already in use on DRIVE.
14783
14784
14785 Stream: Initializer process output.
14786
14787 Time: While system is running.
14788
14789 Meaning: An attempt to add a physical volume finds the
14790 volume already in use on another drive.
14791
14792 Action: Enter a corrected command line.
14793
14794
14795 disk_table_.pl1
14796 disk_table_: PVNAME currently known to be on
14797 DRIVE
14798
14799
14800 Stream: Initializer process output.
14801
14802
14803
14804 disk_table_ 256 08/21/20 MR12.7^L
14805
14806
14807 Time: While system is running.
14808
14809 Meaning: An attempt to specify that PVNAME is on a certain
14810 drive finds it on another drive.
14811
14812 Action: Enter a corrected command line. Use the del_vol
14813 command if necessary to cause the system to forget
14814 DRIVE's old contents if a pack has been moved.
14815
14816
14817
14818 disk_table_.pl1
14819 disk_table_: PVNAME not found.
14820
14821
14822 Stream: Initializer process output.
14823
14824 Time: While system is running.
14825
14826 Meaning: An initialize_disk -copy command could not find
14827 the source volume.
14828
14829 Action: Enter a corrected command line.
14830
14831
14832 mdx.pl1
14833 disk_table_: Root PV "PV_NAME" moved from DSKX_NN
14834 to DSKX_NN.
14835
14836
14837 Stream: BOS Typewriter.
14838
14839 Time: System Intialization.
14840
14841 Meaning: The specified root volume has been moved to a
14842 different drive since the last shutdown.
14843
14844 Action: No operator action is required.
14845
14846
14847 disk_table_.pl1
14848 disk_table_: Some volumes are incomplete.
14849 Complete or demount them.
14850
14851
14852 Stream: Initializer process output.
14853
14854 Time: System Intialization.
14855
14856 Meaning: Initialization has failed to remount all the
14857 volumes which were previously known in response
14858 to a startup command.
14859
14860
14861
14862 disk_table_ 257 08/21/20 MR12.7^L
14863
14864
14865 Action: Use the list_disks command to find out which
14866 volumes are incomplete. Use the av or dlv
14867 commands to rectify the situation and try startup
14868 again.
14869
14870
14871
14872 disk_table_.pl1
14873 disk_table_: The root logical volume is
14874 incomplete.
14875
14876
14877 Stream: Initializer process output.
14878
14879 Time: System Intialization.
14880
14881 Meaning: Some registered physical volumes of the root
14882 logical volume are not mounted but the operator
14883 has attempted to execute a command that requires
14884 the root to be completely mounted. This message
14885 is followed by mount messages for the missing
14886 volumes.
14887
14888
14889 Action: Mount the missing volumes and notify the system
14890 of their location with the add_vol command.
14891
14892
14893
14894 dn355.pl1
14895 dn355: attempted crawlout with FNP queue locked
14896
14897
14898 Stream: BOS Typewriter Crashes system
14899
14900 Time: While system is running.
14901
14902 Meaning: An attempt was made to crawl out while an FNP
14903 queue lock a processor lock was locked.
14904
14905 Action: Contact the system programming staff.
14906
14907
14908 dn355.pl1
14909 dn355: emergency interrupt from FNP X: FAULT
14910 FNP instruction counter = IC
14911 channel CHN fault status = FS
14912 FNP_MODULE: REASON_FOR_CRASH
14913
14914
14915
14916 Stream: BOS Typewriter sounds beeper
14917
14918
14919
14920 dn355 258 08/21/20 MR12.7^L
14921
14922
14923 Time: While system is running.
14924
14925 Meaning: An emergency interrupt has been received from FNP
14926 X indicating it has crashed. All lines dialed to
14927 FNP X will be hung up. The crash was nominally
14928 caused by a fault of type FAULT. Lines following
14929 the first line of the message appear only in
14930 certain cases and provide additional information
14931 about the nature of the crash.
14932
14933 Action: The system will automatically attempt to reboot
14934 the crashed FNP. Subsequent messages will
14935 indicate the success or failure of this attempt.
14936 No action is required now but action may be
14937 required if the automatic reboot fails.
14938
14939
14940
14941 dn355.pl1
14942 dn355: Error sending mailbox interrupt to FNP X
14943 will retry.
14944
14945
14946 Stream: BOS Typewriter.
14947
14948 Time: While system is running.
14949
14950 Meaning: An error has been detected in the transmission of
14951 a mailbox interrupt to the FNP. The transmission
14952 will be retried once.
14953
14954 Action: None required.
14955
14956
14957 dn355.pl1
14958 dn355: FNP masked channel NAME for excessive
14959 interrupts
14960
14961
14962 Stream: BOS Typewriter.
14963
14964 Time: While system is running.
14965
14966 Meaning: The FNP has masked the channel whose name is NAME
14967 because it was generating interrupts faster than
14968 they could be handled.
14969
14970 Action: The interruptions can be caused by any number of
14971 problems. This can be caused by the dataset leads
14972 changing too fast for the FNP software to handle
14973 properly; disconnecting or connecting FNP cables
14974 powering off or on a hardwired terminal a bad
14975 modem etc. It is also possible that the FNP
14976
14977
14978 dn355 259 08/21/20 MR12.7^L
14979
14980
14981 channel hardware is defective. Future attempts to
14982 use this channel may possibly crash the FNP. CS
14983 representatives may need to be called to
14984 investigate. An "attach" command will be
14985 necessary to put the channel back in service.
14986
14987
14988
14989 dn355.pl1
14990 dn355: FNP X did not respond to mailbox interrupt
14991
14992
14993 Stream: BOS Typewriter sounds beeper
14994
14995 Time: While system is running.
14996
14997 Meaning: An attempt to interrupt FNP X was unsuccessful.
14998 The FNP is assumed to be down.
14999
15000 Action: The system will automatically attempt to reboot
15001 the crashed FNP. Subsequent messages will
15002 indicate the success or failure of this attempt.
15003 No action is required now but action may be
15004 required if the automatic reboot fails.
15005
15006
15007
15008 dn355.pl1
15009 dn355: FNP X invalid interrupt level N
15010
15011
15012 Stream: BOS Typewriter sounds beeper
15013
15014 Time: While system is running.
15015
15016 Meaning: An FNP interrupt has been received from frontend X
15017 with an invalid interrupt level of octal value N
15018 and will be ignored. If this message is displayed
15019 when a DN6670 is being powered up this message
15020 can be ignored. If this message occurs under any
15021 other circumstances there might be something
15022 wrong with the system's interface with the FNP and
15023 should be investigated by FE representatives.
15024
15025 Action: Contact the system programming staff.
15026
15027
15028 dn355.pl1
15029 dn355: FNP X level L status S STATE
15030
15031
15032 Stream: BOS Typewriter.
15033
15034
15035
15036 dn355 260 08/21/20 MR12.7^L
15037
15038
15039 Time: While system is running.
15040
15041 Meaning: An interrupt at a level other than 3 or possibly
15042 at level 3 if the FNP is not running was received
15043 from FNP X. S is an octal representation of the
15044 status accompanying the interrupt. STATE
15045 indicates the current state of the FNP: running
15046 bootloading or in T&D. This message only appears
15047 if tracing is enabled for the specified FNP.
15048
15049 Action: None required.
15050
15051
15052 dn355.pl1
15053 dn355: inconsistent queue lock
15054
15055
15056 Stream: BOS Typewriter Crashes system
15057
15058 Time: While system is running.
15059
15060 Meaning: A process attempted to unlock the interrupt queue
15061 lock without having it locked.
15062
15063 Action: Contact the system programming staff.
15064
15065
15066 dn355.pl1
15067 dn355: LCTE lock ^= processid
15068
15069
15070 Stream: BOS Typewriter Crashes system
15071
15072 Time: While system is running.
15073
15074 Meaning: The FNP channel lock did not contain the processid
15075 of the process attempting to unlock it.
15076
15077
15078
15079 dn355.pl1
15080 dn355: line number of 0 with non-global opcode in
15081 submbx N FNP X
15082
15083
15084 Stream: BOS Typewriter sounds beeperer
15085
15086 Time: While system is running.
15087
15088 Meaning: Mailbox N from FNP X contained a non-global opcode
15089 which requires a non-zero line number.
15090
15091
15092
15093
15094 dn355 261 08/21/20 MR12.7^L
15095
15096
15097
15098
15099 dn355.pl1
15100 dn355: Message from FNP X: MESSAGE
15101
15102
15103 Stream: BOS Typewriter.
15104
15105 Time: While system is running.
15106
15107 Meaning: An error has been detected by FNP X as explained
15108 by MESSAGE.
15109
15110 Action: No action is required by the operator to deal with
15111 the error mentioned in the message. Action may be
15112 required by appropriate personnel to correct the
15113 problem that caused the error and undo what the
15114 FNP may have done to continue operation. This may
15115 require shutting down the FNP for repairs by Field
15116 Engineering and reboot of the FNP to restore full
15117 operation.
15118
15119
15120
15121 dn355.pl1
15122 dn355: no slot number match for sub mbx N FNP X
15123
15124
15125 Stream: BOS Typewriter sounds beeperer
15126
15127 Time: While system is running.
15128
15129 Meaning: An error has occurred processing submailbox N for
15130 FNP X. The submailbox indicates a line number for
15131 which no match could be found.
15132
15133 Action: Contact the system programming staff.
15134
15135
15136 dn355.pl1
15137 dn355: output buffer at N has zero tally
15138
15139
15140 Stream: BOS Typewriter Crashes system
15141
15142 Time: While system is running.
15143
15144 Meaning: An output buffer with a zero tally has been found
15145 at offset N in the segment tty_buf.
15146
15147 Action: Contact the system programming staff.
15148
15149
15150
15151
15152 dn355 262 08/21/20 MR12.7^L
15153
15154
15155 dn355.pl1
15156 dn355: Timeout sending mailbox interrupt to FNP
15157 X will retry.
15158
15159
15160 Stream: BOS Typewriter.
15161
15162 Time: While system is running.
15163
15164 Meaning: The FNP did not respond within 2 seconds to the
15165 previously sent mailbox interrupt. The
15166 transmission will be retried once.
15167
15168 Action: None required.
15169
15170
15171 dn355.pl1
15172 dn355: unable to allocate block for delay queue
15173
15174
15175 Stream: BOS Typewriter Crashes system
15176
15177 Time: While system is running.
15178
15179 Meaning: There was insufficient space left in tty_buf to
15180 allocate a block in which to build a delay queue.
15181
15182 Action: Contact the system programming staff.
15183
15184
15185 dn355.pl1
15186 dn355: unrecognized io command C from FNP X for
15187 line N
15188
15189
15190 Stream: BOS Typewriter sounds beeperer
15191
15192 Time: While system is running.
15193
15194 Meaning: An invalid io command was received from FNP X for
15195 line N. C is the octal representation of the
15196 command.
15197
15198 Action: Contact the system programming staff.
15199
15200
15201 dn355.pl1
15202 dn355: unrecognized op code OPCODE with rcd from
15203 FNP X for devx N
15204
15205
15206 Stream: BOS Typewriter sounds beeperer
15207
15208
15209
15210 dn355 263 08/21/20 MR12.7^L
15211
15212
15213 Time: While system is running.
15214
15215 Meaning: An invalid op code OPCODE has been received from
15216 FNP X for device index N in a mailbox containing
15217 an rcd read control data command.
15218
15219 Action: Contact the system programming staff.
15220
15221
15222 dpg_.pl1
15223 dpg_: COND condition signalled while copying
15224 stack_0 into >pdd>DIRNAME
15225
15226
15227 Stream: as severity0
15228
15229 Time: While system is running.
15230
15231 Meaning: An error occurred while copying the ring-0 stack
15232 of the defunct process from ring-0 into the saved
15233 process directory. This error caused the COND
15234 condition to be signalled. The ring-0 stack will
15235 not be copied into the saved process directory.
15236
15237 Action: No operator action is required.
15238
15239
15240 dpg_.pl1
15241 dpg_: ERROR_MESSAGE. Attempting to rename pdir
15242 for NAME.PROJ CHN after fatal process error.
15243
15244
15245 Stream: as severity1
15246
15247 Time: While system is running.
15248
15249 Meaning: The error described by ERROR_MESSAGE occurred
15250 while attempting to save the process directory
15251 belonging to the user PERS.PROJ after a fatal
15252 process error. The directory was not saved. A
15253 typical cause of this is that the user already has
15254 a saved process directory from a previous fatal
15255 process error in this bootload.
15256
15257 Action: Contact the system programming staff.
15258
15259
15260 dpg_.pl1
15261 dpg_: ERROR_MESSAGE. Calling
15262 hphcs_$destroy_process_begin for
15263 PERSON.PROJECT.TAG on channel CHN process_id PID.
15264
15265
15266
15267
15268 dpg_ 264 08/21/20 MR12.7^L
15269
15270
15271 Stream: as severity 1
15272
15273 Time: While system is running.
15274
15275 Meaning: An error has occurred while destroying a process
15276 belonging to the user PERSON.PROJECT.TAG connected
15277 to terminal channel CHN. This process probably
15278 cannot be destroyed. ERROR_MESSAGE is the text
15279 associated with the error returned by
15280 hphcs_$destroy_process_begin.
15281
15282 Action: Contact the system programming staff.
15283
15284
15285 dpg_.pl1
15286 dpg_: ERROR_MESSAGE. Creating saved stack_0 for
15287 PERS.PROJ PROCESSID.
15288
15289
15290 Stream: as severity0
15291
15292 Time: While system is running.
15293
15294 Meaning: An error has occurred while attempting to create a
15295 segment in the saved process directory for copying
15296 the ring-0 stack of the defunct process. The
15297 ring-0 stack will not be copied into the saved
15298 process directory.
15299
15300 Action: No operator action is required.
15301
15302
15303 dpg_.pl1
15304 dpg_: ERROR_MESSAGE. destroying process
15305 WWWWWWWWWWWW for NAME.PROJ
15306
15307
15308 Stream: as severity2
15309
15310 Time: While system is running.
15311
15312 Meaning: An error has occurred while destroying a process
15313 belonging to the user NAME.PROJ. He was not
15314 charged for his CPU usage.
15315
15316 Action: Contact the system programming staff.
15317
15318
15319 dpg_.pl1
15320 dpg_: removed USER PROCESSID process
15321 termination monitor.
15322
15323
15324
15325
15326 dpg_ 265 08/21/20 MR12.7^L
15327
15328
15329 Stream: as severity0
15330
15331 Time: While system is running.
15332
15333 Meaning: Process termination monitoring for USER process
15334 id PROCESSID has been terminated by user request
15335 IPC error or the destruction of the process.
15336
15337 Action: No operator action is required.
15338
15339
15340 dpg_.pl1
15341 dpg_: Saved >pdd>PERS.PROJ.f.CHN after fatal
15342 process error.
15343
15344
15345 Stream: as severity1
15346
15347 Time: While system is running.
15348
15349 Meaning: The process directory belonging to user PERS.PROJ
15350 has been saved after a fatal process error. It
15351 has been renamed to the name shown in the message.
15352 It will be saved until the next shutdown. System
15353 programmers might want to examine its contents to
15354 determine the cause of the fatal process error.
15355
15356 Action: Inform the system programming staff. Do so well
15357 in advance of the next shutdown.
15358
15359
15360 dpg_.pl1
15361 dpg_: USER PROCESSID set/replaced process
15362 termination monitor.
15363
15364
15365 Stream: as severity0
15366
15367 Time: While system is running.
15368
15369 Meaning: USER processid PROCESSID will receive
15370 notifications of all process destructions from the
15371 Answering Service. 'set' indicates that the
15372 process was not already monitoring processes;
15373 'replaced' indicates that the process already had
15374 a monitor established and that it has been
15375 replaced by this request.
15376
15377 Action: No operator action is required.
15378
15379
15380 wired_shutdown.pl1
15381 emergency shutdown part 1 complete
15382
15383
15384 emergency 266 08/21/20 MR12.7^L
15385
15386
15387 Stream: BOS Typewriter.
15388
15389 Time: Emergency shutdown
15390
15391 Meaning: All of memory has been written out once and those
15392 pages on the paging device which could be written
15393 out to operative drives flushed. All segments and
15394 directories will now be deactivated and all
15395 drives shut down.
15396
15397 Action: No operator action is required.
15398
15399
15400 dn355_boot_interrupt.pl1
15401 error reading core image for FNP X
15402
15403
15404 Stream: BOS Typewriter.
15405
15406 Time: When bootloading an FNP
15407
15408 Meaning: An I/O error was detected by the FNP bootload
15409 program while attempting to read the core image
15410 into FNP memory. A hardware failure of either the
15411 DIA or the Multics IOM is indicated.
15412
15413 Action: Try the FNP load again. If it fails again
15414 consult Field Engineering.
15415
15416
15417 mrd_util_.pl1
15418 Error: CONDITION in mrd_util_$ENTRY
15419
15420
15421 Stream: BOS Typewriter sounds beeper
15422
15423 Time: While system is running.
15424
15425 Meaning: CONDITION was signalled during a call to the
15426 entrypoint ENTRY in mrd_util_. A message
15427 coordinator dump is taken. If the calling process
15428 had a message coordinator segment locked that
15429 segment is checked for consistency and the lock
15430 is unlocked. mrd_util_ then returns to its caller
15431 without retrying the operation that failed. This
15432 indicates a logic error in the supervisor or CPU
15433 or memory hardware problems.
15434
15435 Action: Contact the system programming staff. Save all
15436 console and message coordinator terminal output.
15437
15438
15439
15440
15441
15442 esd 267 08/21/20 MR12.7^L
15443
15444
15445
15446
15447 wired_shutdown.pl1
15448 esd before fs enabled
15449
15450
15451 Stream: BOS Typewriter.
15452
15453 Time: Emergency shutdown
15454
15455 Meaning: The system crashed before the storage system was
15456 accessed by Multics. An ESD was attempted but no
15457 ESD is necessary. The "shutdown complete" message
15458 will always follow.
15459
15460 Action: Reboot the system.
15461
15462
15463 page_error.alm
15464 evict_page: fatal parity error moving page frame
15465 at AAA SCU TAG.
15466
15467
15468 Stream: BOS Typewriter Crashes system
15469
15470 Time: While system is running.
15471
15472 Meaning: A parity error was encountered while moving a
15473 wired page around memory. The page may not be
15474 usable.
15475
15476 Action: Contact Field Engineering personnel about possible
15477 problems with SCU TAG. Follow normal recovery
15478 procedures.
15479
15480
15481
15482 page_error.alm
15483 evict_page: fatal parity error moving page frame
15484 at AAA SCU TAG.
15485
15486
15487 Stream: BOS Typewriter Crashes system
15488
15489 Time: While system is running.
15490
15491 Meaning: A parity error was encountered while moving a
15492 wired page around memory. The page may not be
15493 usable.
15494
15495 Action: Contact Field Engineering personnel about possible
15496 problems with SCU TAG. Follow normal recovery
15497 procedures.
15498
15499
15500 evict_page 268 08/21/20 MR12.7^L
15501
15502
15503
15504
15505 page_error.alm
15506 evict_page: parity error moving page frame at
15507 AAA SCU TAG.
15508
15509
15510 Stream: BOS Typewriter.
15511
15512 Time: While system is running.
15513
15514 Meaning: A parity error was encountered while moving a page
15515 within main memory. This may occur as part of an
15516 attempt to delete that main memory or use it as
15517 an I/O buffer.
15518
15519 Action: Inform Field Engineering personnel about possible
15520 problems with this SCU.
15521
15522
15523
15524 page_error.alm
15525 evict_page: parity error moving page frame at
15526 AAA SCU TAG.
15527
15528
15529 Stream: BOS Typewriter.
15530
15531 Time: While system is running.
15532
15533 Meaning: A parity error was encountered while moving a page
15534 within main memory. This may occur as part of an
15535 attempt to delete that main memory or use it as
15536 an I/O buffer.
15537
15538 Action: Inform Field Engineering personnel about possible
15539 problems with this SCU.
15540
15541
15542
15543 find_file_partition.pl1
15544 find_file_partition: file partition is NNN
15545 records not between 30 and 255.
15546
15547
15548 Stream: BOS Typewriter Crashes system
15549
15550 Time: System Intialization.
15551
15552 Meaning: The partition holding the bce file system is of an
15553 invalid size. The rpv was either mal-formatted or
15554 damaged.
15555
15556
15557
15558 find_file_partition 269 08/21/20 MR12.7^L
15559
15560
15561 Action: The rpv will need to be rebuilt.
15562
15563
15564 find_file_partition.pl1
15565 find_file_partition: Initting file partition.
15566
15567
15568 Stream: BOS Typewriter.
15569
15570 Time: System Intialization.
15571
15572 Meaning: The bce file system was found to be damaged or
15573 never initialized. Any previous contents are
15574 discarded.
15575
15576
15577
15578 find_file_partition.pl1
15579 find_file_partition: No file partition defined on
15580 RPV.
15581
15582
15583 Stream: BOS Typewriter Crashes system
15584
15585 Time: System Intialization.
15586
15587 Meaning: The partition used to hold the bce file system is
15588 missing from the rpv. Suspect damage of the rpv.
15589
15590 Action: The rpv will need to be rebuilt.
15591
15592
15593 fnp_util.pl1
15594 FNP T deleted from configuration^ by ^a^.
15595
15596
15597
15598
15599
15600
15601 dn355_boot_interrupt.pl1
15602 FNP X loaded successfully
15603
15604
15605 Stream: BOS Typewriter.
15606
15607 Time: When bootloading an FNP
15608
15609 Meaning: The FNP bootload has completed successfully.
15610
15611 Action: This message is for informational purposes only.
15612
15613
15614
15615
15616 FNP 270 08/21/20 MR12.7^L
15617
15618
15619
15620
15621 dn355_boot_interrupt.pl1
15622 FNP X not loaded.
15623
15624
15625 Stream: BOS Typewriter.
15626
15627 Time: When bootloading an FNP
15628
15629 Meaning: The attempted bootload was not successful. This
15630 message is always preceded by one of the above
15631 error messages.
15632
15633 Action: This message is for informational purposes only.
15634
15635
15636 fnp_init.pl1
15637 fnp_init: FNP number N > max allowed number MAX
15638 of FNPs
15639
15640
15641 Stream: BOS Typewriter Crashes system
15642
15643 Time: System Intialization.
15644
15645 Meaning: An fnp card from the config deck specifies an FNP
15646 tag other than A B C D E F G or H.
15647
15648 Action: Replace the bad fnp card and reboot.
15649
15650
15651 fnp_init.pl1
15652 fnp_init: inconsistent fnp cards.
15653
15654
15655 Stream: BOS Typewriter Crashes system
15656
15657 Time: System Intialization.
15658
15659 Meaning: Two or more fnp cards from the config deck specify
15660 the same FNP tag.
15661
15662 Action: Replace or remove the bad fnp cards and reboot.
15663
15664
15665 fnp_init.pl1
15666 fnp_init: Invalid model # MODELN on prph fnpX
15667 card.
15668
15669
15670 Stream: BOS Typewriter Crashes system
15671
15672
15673
15674 fnp_init 271 08/21/20 MR12.7^L
15675
15676
15677 Time: System Intialization.
15678
15679 Meaning: The current fnp model number MODELN is not a
15680 supported number.
15681
15682 Action: Contact the system programming staff.
15683
15684
15685 fnp_init.pl1
15686 fnp_init: Invalid state on prph fnpX card.
15687
15688
15689 Stream: BOS Typewriter Crashes system
15690
15691 Time: System Intialization.
15692
15693 Meaning: The only valid states are "on" or "off".
15694
15695 Action: Contact the system programming staff.
15696
15697
15698 fnp_init.pl1
15699 fnp_init: Less than 256 words of free space in
15700 tty_buf: N
15701
15702
15703 Stream: BOS Typewriter Crashes system
15704
15705 Time: System Intialization.
15706
15707 Meaning: Only N words of free space remain in tty_buf after
15708 allocating the header and circular queue. A
15709 minimum of 256 words is required and ordinarily
15710 more free space is desirable. Either the size of
15711 tty_buf as specified by the PARM TTYB config
15712 card must be increased or the circular queue
15713 size as specified by the PARM TTYQ config card
15714 must be decreased.
15715
15716 Action: Correct the config deck and reboot the system.
15717
15718
15719 fnp_init.pl1
15720 fnp_init: no fnp cards in config deck
15721
15722
15723 Stream: BOS Typewriter.
15724
15725 Time: System Intialization.
15726
15727 Meaning: There are no fnp cards in the config deck and
15728 therefore no FNP will be initialized. Usually
15729
15730
15731
15732 fnp_init 272 08/21/20 MR12.7^L
15733
15734
15735 this indicates an error although it is possible
15736 to run Multics without an FNP.
15737
15738 Action: If an FNP is wanted reboot the system with an
15739 appropriate config deck.
15740
15741
15742
15743 fnp_init.pl1
15744 fnp_init: The number of configured protocol
15745 channels of N exceeds the maximum allowed of N.
15746
15747
15748
15749 Stream: BOS Typewriter Crashes system
15750
15751 Time: System Intialization.
15752
15753 Meaning: The prot parm from the config deck specifies too
15754 many protocol channels.
15755
15756 Action: Contact the system programming staff.
15757
15758
15759 fnp_init.pl1
15760 fnp_init: Unable to abs_wire tty_buf.
15761 ERROR_CODE_MESSAGE
15762
15763
15764 Stream: BOS Typewriter Crashes system
15765
15766 Time: System Intialization.
15767
15768 Meaning: The call to allocate memory in the bootload memory
15769 controller for tty_buf failed.
15770
15771 Action: Contact the system programming staff.
15772
15773
15774 fnp_multiplexer.pl1
15775 fnp_multiplexer$assign_channel: Assignment of FNP
15776 X succeeded | failed.
15777
15778
15779 Stream: BOS Typewriter.
15780
15781 Time: While system is running.
15782
15783 Meaning: Indicates the result of a call to
15784 io_manager$assign for FNP X. This message only
15785 appears if tracing is enabled for the specified
15786 FNP.
15787
15788
15789
15790 fnp_multiplexer$assign_channel 273 08/21/20 MR12.7^L
15791
15792
15793 Action: none required.
15794
15795
15796 fnp_multiplexer.pl1
15797 fnp_multiplexer$ENTRY: Tracing call.
15798
15799
15800 Stream: BOS Typewriter.
15801
15802 Time: While system is running.
15803
15804 Meaning: A call was made to the ENTRY entry. This message
15805 only appears if tracing is enabled for the
15806 specified FNP.
15807
15808 Action: none required.
15809
15810
15811 fnp_multiplexer.pl1
15812 fnp_multiplexer$ENTRY: Tracing error. ERROR.
15813
15814
15815 Stream: BOS Typewriter.
15816
15817 Time: While system is running.
15818
15819 Meaning: The error code represented by ERROR was
15820 encountered by ENTRY. This message only appears
15821 if tracing is enabled for the specified FNP.
15822
15823 Action: none required.
15824
15825
15826 fnp_multiplexer.pl1
15827 fnp_multiplexer$shutdown: Called with FNP wired.
15828
15829
15830 Stream: BOS Typewriter.
15831
15832 Time: While system is running.
15833
15834 Meaning: A call was made to the shutdown entry while the
15835 pages for I/O for an FNP were still wired. This
15836 message only appears if tracing is enabled for the
15837 specified FNP.
15838
15839 Action: none required.
15840
15841
15842 fnp_multiplexer.pl1
15843 fnp_multiplexer$shutdown: Called with null
15844 fnp_ptr
15845
15846
15847
15848 fnp_multiplexer$shutdown 274 08/21/20 MR12.7^L
15849
15850
15851 Stream: BOS Typewriter.
15852
15853 Time: While system is running.
15854
15855 Meaning: A call was made to the shutdown entry with a null
15856 pointer to fnp_info. This message only appears if
15857 tracing is enabled for the specified FNP.
15858
15859 Action: Contact the system programming staff.
15860
15861
15862 fnp_multiplexer.pl1
15863 fnp_multiplexer$shutdown: Failed to unwire fnp.
15864 ERROR.
15865
15866
15867 Stream: BOS Typewriter.
15868
15869 Time: While system is running.
15870
15871 Meaning: An attempt to unwire the pages used for I/O to an
15872 FNP failed at FNP shutdown. ERROR contains the
15873 message derived from a standard system error code.
15874
15875 Action: Contact the system programming staff.
15876
15877
15878 fnp_multiplexer.pl1
15879 fnp_multiplexer$unassign_channel: Unassignment of
15880 FNP X succeeded | failed.
15881
15882
15883 Stream: BOS Typewriter.
15884
15885 Time: While system is running.
15886
15887 Meaning: Indicates the result of a call to
15888 io_manager$unassign for FNP X. This message only
15889 appears if tracing is enabled for the specified
15890 FNP.
15891
15892 Action: none required.
15893
15894
15895 fnp_multiplexer.pl1
15896 fnp_multiplexer: debugging stop type go to
15897 continue.
15898
15899
15900 Stream: BOS Typewriter Crashes system
15901
15902 Time: While system is running.
15903
15904
15905
15906 fnp_multiplexer 275 08/21/20 MR12.7^L
15907
15908
15909 Meaning: An error has been encountered in setting up an
15910 FNP and debugging mode is turned on.
15911
15912 Action: Use BCE commands to analyze the condition if
15913 necessary; type "go" to resume system operation.
15914
15915
15916
15917 fnp_multiplexer.pl1
15918 fnp_multiplexer: get_meters order for FNP X line
15919 N timed out.
15920
15921
15922 Stream: BOS Typewriter.
15923
15924 Time: While system is running.
15925
15926 Meaning: A get_meters order for line N of FNP X failed to
15927 complete within 10 seconds. The buffer space
15928 associated with the order has been abandoned and
15929 get_meters dump and patch orders to that FNP are
15930 disabled until the FNP is reloaded.
15931
15932
15933
15934 fnp_multiplexer.pl1
15935 fnp_multiplexer: mylock error
15936
15937
15938 Stream: BOS Typewriter Crashes system
15939
15940 Time: While system is running.
15941
15942 Meaning: An attempt has been made to lock an FNP channel
15943 lock to a process that already has it locked.
15944
15945 Action: Contact the system programming staff.
15946
15947
15948 fnp_multiplexer.pl1
15949 fnp_multiplexer: NAME order to FNP X timed out.
15950
15951
15952 Stream: BOS Typewriter.
15953
15954 Time: While system is running.
15955
15956 Meaning: NAME is "get_meters" "dump_fnp" or "patch_fnp".
15957 The named order to FNP X failed to complete within
15958 10 seconds. The buffer space associated with the
15959 order has been abandoned and get_meters dump
15960 and patch orders to that FNP are disabled until
15961 the FNP is reloaded.
15962
15963
15964 fnp_multiplexer 276 08/21/20 MR12.7^L
15965
15966
15967 Action: Contact the system programming staff.
15968
15969
15970 fnp_multiplexer.pl1
15971 fnp_multiplexer: patching FNP X for USER: ADDR
15972 from XXX to YYY
15973
15974
15975
15976 Stream: BOS Typewriter.
15977
15978 Time: While system is running.
15979
15980 Meaning: The memory of FNP X is being patched by the
15981 privileged user whose user_id is USER. ADDR is
15982 the absolute location in FNP memory that is being
15983 patched in octal; XXX and YYY are the old and
15984 new values of the location respectively also in
15985 octal. The second line may be repeated with
15986 different values if more than one word is being
15987 patched.
15988
15989 Action: This information is for logging purposes.
15990
15991
15992 fnp_util.pl1
15993 fnp_util$configure: FNP T already configured.
15994
15995
15996
15997
15998
15999
16000 fnp_util.pl1
16001 fnp_util$ENTRY: Debugging stop type go to
16002 continue.
16003
16004
16005
16006
16007
16008
16009 fnp_util.pl1
16010 fnp_util$ENTRY: Invalid call for FNP INDEX. not
16011 in cdeck
16012
16013
16014
16015
16016
16017
16018 fnp_util.pl1
16019 fnp_util$ENTRY: Invalid call. trace
16020
16021
16022 fnp_util$ENTRY 277 08/21/20 MR12.7^L
16023
16024
16025
16026
16027 fnp_util.pl1
16028 fnp_util$ENTRY: Tracing call for fnp T.
16029
16030
16031
16032
16033
16034
16035 fnp_util.pl1
16036 fnp_util$fdump_seg_io: IO_OP for CALLER trace
16037
16038
16039
16040
16041
16042
16043 fnp_util.pl1
16044 fnp_util$load: Error loading FNP T. REASON
16045 trace
16046
16047
16048
16049
16050
16051
16052 fnp_util.pl1
16053 fnp_util$load: FNP load already in progress for
16054 FNP T.
16055
16056
16057
16058
16059
16060
16061 fnp_util.pl1
16062 fnp_util$load: FNP T is running T&D.
16063
16064
16065
16066
16067
16068
16069 fnp_util.pl1
16070 fnp_util$load: FNP T is running. trace
16071
16072
16073
16074
16075
16076
16077
16078
16079
16080 fnp_util$load 278 08/21/20 MR12.7^L
16081
16082
16083
16084
16085 fnp_util.pl1
16086 fnp_util$load: FNP T not wired.
16087
16088
16089
16090
16091
16092
16093 fnp_util.pl1
16094 fnp_util$unwire: Unwire failed for FNP T. REASON
16095
16096
16097
16098
16099
16100
16101 fnp_util.pl1
16102 fnp_util$validate_assigned_ret CALLER: IO
16103 manager assignment lacking. trace
16104
16105
16106
16107
16108
16109
16110 fnp_util.pl1
16111 fnp_util$wire: failed. REASON trace
16112
16113
16114
16115
16116
16117
16118 fnp_util.pl1
16119 fnp_util$wire: FNP T already wired trace
16120
16121
16122
16123
16124
16125
16126 fnp_util.pl1
16127 fnp_util: assigned FNP T to NAME for T & D.
16128
16129
16130
16131
16132
16133
16134 fnp_util.pl1
16135
16136
16137
16138 fnp_util 279 08/21/20 MR12.7^L
16139
16140
16141 fnp_util: channel assignment failed for FNP ^T
16142 REASON. tandd
16143
16144
16145
16146
16147
16148
16149 fnp_util.pl1
16150 fnp_util: Could not unassign FNP T at
16151 reassign_interrupt.
16152
16153
16154
16155
16156
16157
16158 fnp_util.pl1
16159 fnp_util: FNP T added to configuration^ by
16160 NAME^.
16161
16162
16163
16164
16165
16166
16167 fnp_util.pl1
16168 fnp_util: force detaching FNP T from process PID.
16169
16170
16171
16172
16173
16174
16175 fnp_util.pl1
16176 fnp_util: io channel unassignment failed for FNP
16177 T. tandd
16178
16179
16180
16181 Message: fnp_util: releasing FNP T from NAME tandd
16182
16183
16184
16185 fnp_util.pl1
16186 fnp_util: io channel unassignment failed for FNP
16187 T. tandd
16188
16189
16190
16191
16192
16193
16194
16195
16196 fnp_util 280 08/21/20 MR12.7^L
16197
16198
16199 fnp_util.pl1
16200 fnp_util: ioam_$assign failed for FNP T. REASON
16201 tandd
16202
16203
16204
16205
16206
16207
16208 fnp_util.pl1
16209 fnp_util: lock_fnp called with lock locked.
16210
16211
16212
16213
16214
16215
16216 page_error.alm
16217 free_store: Deposit non-disk address XXXXXXXXXXXX
16218 on dskX_NNS
16219
16220
16221 Stream: BOS Typewriter Crashes system
16222
16223 Time: While system is running.
16224
16225 Meaning: free_store was called to return an address to the
16226 free pool for dskX_NNS but the address type was
16227 not disk. This probably indicates a software
16228 error.
16229
16230 Action: Follow normal recovery procedures.
16231
16232
16233 page_error.alm
16234 free_store: Deposit non-disk address XXXXXXXXXXXX
16235 on dskX_NNS
16236
16237
16238 Stream: BOS Typewriter Crashes system
16239
16240 Time: While system is running.
16241
16242 Meaning: free_store was called to return an address to the
16243 free pool for dskX_NNS but the address type was
16244 not disk. This probably indicates a software
16245 error.
16246
16247 Action: Follow normal recovery procedures.
16248
16249
16250 page_error.alm
16251
16252
16253
16254 free_store 281 08/21/20 MR12.7^L
16255
16256
16257 free_store: Deposit/withdraw address XXXXXX out
16258 of paging region on dskX_NNS.
16259
16260
16261 Stream: BOS Typewriter Crashes system
16262
16263 Time: While system is running.
16264
16265 Meaning: Address XXXXXX was being deposited to or wtihdrawn
16266 from the pool of free addresses for dskX_NNS
16267 but the address is not within the Paging Region
16268 for the device. This probably indicates a
16269 software error.
16270
16271 Action: Follow normal recovery procedures.
16272
16273
16274 page_error.alm
16275 free_store: Deposit/withdraw address XXXXXX out
16276 of paging region on dskX_NNS.
16277
16278
16279 Stream: BOS Typewriter Crashes system
16280
16281 Time: While system is running.
16282
16283 Meaning: Address XXXXXX was being deposited to or wtihdrawn
16284 from the pool of free addresses for dskX_NNS
16285 but the address is not within the Paging Region
16286 for the device. This probably indicates a
16287 software error.
16288
16289 Action: Follow normal recovery procedures.
16290
16291
16292 page_error.alm
16293 free_store: Invalid call to
16294 free_store$deposit_list.
16295
16296
16297 Stream: BOS Typewriter Crashes system
16298
16299 Time: While system is running.
16300
16301 Meaning: free_store$deposit_list was called with the wrong
16302 number of arguments. This is a software error.
16303
16304 Action: Follow normal recovery procedures.
16305
16306
16307 page_error.alm
16308 free_store: Invalid call to
16309 free_store$deposit_list.
16310
16311
16312 free_store 282 08/21/20 MR12.7^L
16313
16314
16315 Stream: BOS Typewriter Crashes system
16316
16317 Time: While system is running.
16318
16319 Meaning: free_store$deposit_list was called with the wrong
16320 number of arguments. This is a software error.
16321
16322 Action: Follow normal recovery procedures.
16323
16324
16325 page_error.alm
16326 free_store: out of room in hardcore partition.
16327
16328
16329 Stream: BOS Typewriter Crashes system
16330
16331 Time: While system is running.
16332
16333 Meaning: During bootload the PART HC on the RLV became
16334 full. This indicates a logic error in the
16335 supervisor or CPU or memory hardware problems.
16336
16337 Action: Follow normal recovery procedures. It may be
16338 necessary to boot with another tape. If this
16339 error occurs with a new version of the system boot
16340 tape the system programming staff may determine
16341 that the size of the hardcore partition must be
16342 increased by using the rebuild_disk command on a
16343 copy of the RPV.
16344
16345
16346
16347 page_error.alm
16348 free_store: out of room in hardcore partition.
16349
16350
16351 Stream: BOS Typewriter Crashes system
16352
16353 Time: While system is running.
16354
16355 Meaning: During bootload the PART HC on the RLV became
16356 full. This indicates a logic error in the
16357 supervisor or CPU or memory hardware problems.
16358
16359 Action: Follow normal recovery procedures. It may be
16360 necessary to boot with another tape. If this
16361 error occurs with a new version of the system boot
16362 tape the system programming staff may determine
16363 that the size of the hardcore partition must be
16364 increased by using the rebuild_disk command on a
16365 copy of the RPV.
16366
16367
16368
16369
16370 free_store 283 08/21/20 MR12.7^L
16371
16372
16373
16374
16375 page_error.alm
16376 free_store: PVTE/Stock out of synch on
16377 dskX_NNS. stockp=YYY|YYYYY.
16378
16379
16380 Stream: BOS Typewriter Crashes system
16381
16382 Time: While system is running.
16383
16384 Meaning: The PVTE and record stock for dskX_NNS do not
16385 point to each other. This indicates a hardware or
16386 software error.
16387
16388 Action: Follow normal recovery procedures.
16389
16390
16391 page_error.alm
16392 free_store: PVTE/Stock out of synch on
16393 dskX_NNS. stockp=YYY|YYYYY.
16394
16395
16396 Stream: BOS Typewriter Crashes system
16397
16398 Time: While system is running.
16399
16400 Meaning: The PVTE and record stock for dskX_NNS do not
16401 point to each other. This indicates a hardware or
16402 software error.
16403
16404 Action: Follow normal recovery procedures.
16405
16406
16407 page_error.alm
16408 free_store: Scavenger STACQ fails on dskX_NNS.
16409
16410
16411 Stream: BOS Typewriter Crashes system
16412
16413 Time: During a physical volume scavenge of dskX_NNS.
16414
16415 Meaning: A STACQ instruction used to unlock a record
16416 address during a volume scavenge did not operate
16417 correctly. This indicates processor or memory
16418 malfunction.
16419
16420 Action: Follow normal recovery procedures.
16421
16422
16423 page_error.alm
16424 free_store: Scavenger STACQ fails on dskX_NNS.
16425
16426
16427
16428 free_store 284 08/21/20 MR12.7^L
16429
16430
16431 Stream: BOS Typewriter Crashes system
16432
16433 Time: During a physical volume scavenge of dskX_NNS.
16434
16435 Meaning: A STACQ instruction used to unlock a record
16436 address during a volume scavenge did not operate
16437 correctly. This indicates processor or memory
16438 malfunction.
16439
16440 Action: Follow normal recovery procedures.
16441
16442
16443 page_error.alm
16444 free_store: volmap_seg async error for dskX_NNS
16445
16446
16447 Stream: BOS Typewriter Crashes system
16448
16449 Time: While system is running.
16450
16451 Meaning: When attempting to write a page of the Volume Map
16452 to dskX_NNS the page was found not to be in
16453 memory. This probably indicates a software error.
16454
16455 Action: Follow normal recovery procedures.
16456
16457
16458 page_error.alm
16459 free_store: volmap_seg async error for dskX_NNS
16460
16461
16462 Stream: BOS Typewriter Crashes system
16463
16464 Time: While system is running.
16465
16466 Meaning: When attempting to write a page of the Volume Map
16467 to dskX_NNS the page was found not to be in
16468 memory. This probably indicates a software error.
16469
16470 Action: Follow normal recovery procedures.
16471
16472
16473 freecore.pl1
16474 freecore: parity error in frame XXX of memory.
16475
16476
16477 Stream: BOS Typewriter.
16478
16479 Time: System Intialization.
16480
16481 Meaning: A memory parity error has been detected in page
16482 XXX of memory. The page will not be put in use.
16483
16484
16485
16486 freecore 285 08/21/20 MR12.7^L
16487
16488
16489 Action: No operator action is required.
16490
16491
16492 fs_search.pl1
16493 fs_search: Fatal damage detected to WHAT in ring
16494 RING for USER.
16495
16496
16497 Stream: Logged in SYSERR log.
16498
16499 Time: While system is running.
16500
16501 Meaning: Some object crucial to the operation of the
16502 dynamic linker in ring RING was detected damaged.
16503 Since the dynamic linker cannot operate in the
16504 process it is terminated.
16505
16506 Action: No operator action is required.
16507
16508
16509 fsout_vol.pl1
16510 fsout_vol: Discarding old dumper bit maps for
16511 dskX_NNS.
16512
16513
16514 Stream: BOS Typewriter.
16515
16516 Time: System shutdown and volume demounting.
16517
16518 Meaning: An error occurred attempting to read the VTOC
16519 header from physical volume on dskX_NNS. Writing
16520 of the dumper bit maps to disk will be bypassed.
16521 The dumper bit maps will be freed and the system
16522 will attempt to continue however the dumper bit
16523 maps may not be accurate on disk.
16524
16525 Action: Contact the system programming staff.
16526
16527
16528 fsout_vol.pl1
16529 fsout_vol: label for PVNAME dskX_NNS uid does
16530 not match pvt.
16531
16532
16533 Stream: BOS Typewriter.
16534
16535 Time: System shutdown volume mounting and demounting.
16536
16537 Meaning: The unique physical volume ID in the label of the
16538 pack on dskX_NNS PVNAME does not compare with
16539 the value it had when the pack was first mounted.
16540 Damage to the pack has probably occurred.
16541
16542
16543
16544 fsout_vol 286 08/21/20 MR12.7^L
16545
16546
16547 Action: Attempt to demount the volume if this has not
16548 already been done. Save the pack for inspection
16549 and dumping by the system programming staff.
16550 Initiate volume recovery procedures.
16551
16552
16553
16554 fsout_vol.pl1
16555 fsout_vol: XXX volume inconsistenices on PVNAME
16556 dskX_NNS. YYYYY free records. ZZZZZ free
16557 VTOCEs.
16558
16559
16560 Stream: Logged only if the number of free records and the
16561 number of free VTOCEs are both above threshold
16562 values. Printed and logged if either is below
16563 threshold.
16564
16565 Time: Volume demounting and system shutdown time.
16566
16567 Meaning: At some time during the use of volume PVNAME on
16568 drive dskX_NNS the system encountered problems
16569 which left the volume in an inconsistent state.
16570 The effect of this is that some free records
16571 and/or free VTOCEs are unavailable lost to the
16572 system. These inconsistencies can be corrected by
16573 a volume salvage. The number of unused records
16574 and VTOCEs which are available for use is printed.
16575
16576 Action: If the number of free records or free vtoces is
16577 low a physical volume salvage should be done on
16578 the volume prior to mounting it again to recover
16579 the lost items.
16580
16581
16582
16583 fsout_vol.pl1
16584 fsout_vol: REASON Error OPERATION OBJECT_TYPE
16585 for dskX_NNS PVNAME
16586
16587
16588 Stream: BOS Typewriter.
16589
16590 Time: System shutdown and volume mounting and
16591 demounting.
16592
16593 Meaning: A physical device error has occured while
16594 attempting to read or write OPERATION volume
16595 header information OBJECT_TYPE of the pack
16596 PVNAME on dskX_NNS.
16597
16598 Action: If this message occurs at volume mounting time
16599 check the drive specified for write-protect or
16600
16601
16602 fsout_vol 287 08/21/20 MR12.7^L
16603
16604
16605 standby status and retry the add_lv command for
16606 the logical volume. If this message occurs at
16607 shutdown or demount time the volume may contain
16608 inconsistencies lost free records or free
16609 VTOCEs. These inconsistencies can be corrected
16610 by a physical volume salvage.
16611
16612
16613
16614 ftp_dialup_.pl1
16615 ftp_dialup_: answer table damaged at UTEP
16616 tra_vec=TTTT
16617
16618
16619 Stream: as severity 2
16620
16621 Time: While system is running.
16622
16623 Meaning: The tra_vec value was found to be invalid for an
16624 answer table wakeup. Damage to the answer table
16625 is indicated.
16626
16627 Action: Contact the system programming staff.
16628
16629
16630 ftp_dialup_.pl1
16631 ftp_dialup_: called while ansp = null
16632
16633
16634 Stream: as severity 2
16635
16636 Time: While system is running.
16637
16638 Meaning: A programming error in the Answering Service or an
16639 incorrect library installation has caused the
16640 Answering Service to be called before being
16641 initialized. The system will ignore the error and
16642 attempt to continue.
16643
16644 Action: Shut down the system and perform a bootload
16645 operation.
16646
16647
16648 ftp_dialup_.pl1
16649 ftp_dialup_: called with bad ptr EVENT_MSG_PTR by
16650 WWWWWWWWWWWW
16651
16652
16653 Stream: as severity 2
16654
16655 Time: While system is running.
16656
16657
16658
16659
16660 ftp_dialup_ 288 08/21/20 MR12.7^L
16661
16662
16663 Meaning: A programming error in the interprocess
16664 communication system the network software or the
16665 Answering Service itself has occurred. An invalid
16666 message pointer has been passed to the Answering
16667 Service. The system ignores the message and
16668 attempts to continue. This message may be the
16669 result of an incorrect library installation.
16670
16671 Action: Shut down the system and perform a bootload
16672 operation.
16673
16674
16675 ftp_dialup_.pl1
16676 ftp_dialup_: called with null message ptr
16677
16678
16679 Stream: as severity 2
16680
16681 Time: While system is running.
16682
16683 Meaning: A programming error in the interprocess
16684 communication system the network software or the
16685 Answering Service itself has occurred. An invalid
16686 message pointer has been passed to the Answering
16687 Service. The system ignores the message and
16688 attempts to continue. This message may be the
16689 result of an incorrect library installation.
16690
16691 Action: Shut down the system and perform a bootload
16692 operation. Inform the system programming staff.
16693
16694
16695
16696 ftp_dialup_.pl1
16697 ftp_dialup_: CDT damaged at CDTEP tra_vec=TTTT
16698
16699
16700 Stream: as severity 2
16701
16702 Time: While system is running.
16703
16704 Meaning: The tra_vec value was found to be invalid for a
16705 channel wakeup. Damage to the CDT is indicated.
16706
16707 Action: Contact the system programming staff.
16708
16709
16710 ftp_dialup_.pl1
16711 ftp_dialup_: cdte CDTEP CHANNEL state M in use
16712 N - notify system programmer"
16713
16714
16715 Stream: as severity 0
16716
16717
16718 ftp_dialup_ 289 08/21/20 MR12.7^L
16719
16720
16721 Time: While system is running.
16722
16723 Meaning: This indicates a logic error in the supervisor or
16724 CPU or memory hardware problems.
16725
16726 Action: Contact the system programming staff.
16727
16728
16729 ftp_dialup_.pl1
16730 ftp_dialup_: cdtep = null and ate.active = DDDD
16731 for UTEP
16732
16733
16734 Stream: as severity 2
16735
16736 Time: While system is running.
16737
16738 Meaning: This indicates a logic error in the supervisor or
16739 CPU or memory hardware problems.
16740
16741 Action: Contact the system programming staff.
16742
16743
16744 ftp_dialup_.pl1
16745 ftp_dialup_: ERROR_MESSAGE attempting to allocate
16746 a user table entry for CHANNEL
16747
16748
16749 Stream: as severity 1
16750
16751 Time: While system is running.
16752
16753 Meaning: An ERROR_MESSAGE was returned from a call to
16754 asu_$attach_ate which allocates a user table
16755 entry.
16756
16757 Action: Contact the system programming staff.
16758
16759
16760 ftp_dialup_.pl1
16761 ftp_dialup_: ERROR_MESSAGE new_proc of
16762 PERSON.PROJECT denied by channel AIM restriction.
16763
16764
16765 Stream: as severity 0
16766
16767 Time: While system is running.
16768
16769 Meaning: A user attempted to issue a new_proc an specify an
16770 AIM authorization which is not allowed by the
16771 terminal channel in use.
16772
16773 Action: No operator action is required.
16774
16775
16776 ftp_dialup_ 290 08/21/20 MR12.7^L
16777
16778
16779
16780
16781 ftp_dialup_.pl1
16782 ftp_dialup_: ERROR_MESSAGE occurred attempting to
16783 declare handler for ev chn EVENT_CHN for ate UTEP
16784 for CDT_CHANNEL
16785
16786
16787 Stream: as severity 2
16788
16789 Time: While system is running.
16790
16791 Meaning: An ERROR_MESSAGE was returned when an attempt was
16792 made to declare an event call channel for new
16793 process UTEP on EVENT_CHN attached to
16794 CDT_CHANNEL.
16795
16796 Action: Contact the system programming staff.
16797
16798
16799 ftp_dialup_.pl1
16800 ftp_dialup_: ERROR_MESSAGE tty_dim error
16801 removing channel CHANNEL COMMENT
16802
16803
16804 Stream: as severity 2
16805
16806 Time: While system is running.
16807
16808 Meaning: An ERROR_MESSAGE caused the CHANNEL to be
16809 unusable. The CHANNEL with COMMENT will be
16810 removed from service.
16811
16812 Action: You may try to attach the channel. If that fails
16813 notify the system programmers. If the channel is
16814 to be left detached busy out the modem.
16815
16816
16817
16818 ftp_dialup_.pl1
16819 ftp_dialup_: ERROR_MESSAGE when creating process
16820 for PERSON.PROJECT
16821
16822
16823 Stream: as severity 2
16824
16825 Time: While system is running.
16826
16827 Meaning: An ERROR_MESSAGE was returned and the system was
16828 unable to create a user process for
16829 PERSON.PROJECT.
16830
16831
16832
16833
16834 ftp_dialup_ 291 08/21/20 MR12.7^L
16835
16836
16837 Action: If possible get in touch with the user. He got
16838 a message to contact you. Ask him to try again
16839 and to tell you of any peculiarities of his login.
16840 Note all particulars and contact the programming
16841 staff.
16842
16843
16844
16845 ftp_dialup_.pl1
16846 ftp_dialup_: fatal error during process creation
16847 for PERSON.PROJECT CHANNEL
16848
16849
16850 Stream: as severity 1
16851
16852 Time: While system is running.
16853
16854 Meaning: A fatal error occurred during process creation for
16855 PERSON.PROJECT on CHANNEL. Reason is given in
16856 previous log entry. This may be due to a user
16857 error: incorrect segments in the user's home
16858 directory or bad login arguments can cause this
16859 problem.
16860
16861 Action: No operator action is required.
16862
16863
16864 ftp_dialup_.pl1
16865 ftp_dialup_: ignored SSSS from PERSON.PROJECT for
16866 CHANNEL state=DDDDinuse=UUUUtv=TTTT
16867
16868
16869 Stream: as severity 2
16870
16871 Time: While system is running.
16872
16873 Meaning: A spurious signal SSSS from user PERSON.PROJECT
16874 has arrived for CHANNEL. The state of the channel
16875 is DDD inuse is UUUU and tra_vec is TTTT.
16876
16877 Action: This may be some user trying to disrupt the
16878 system. Do a who and save it for the programming
16879 staff.
16880
16881
16882
16883 ftp_dialup_.pl1
16884 ftp_dialup_: non-null atep UTEP for cdte
16885 CDTEPCHANNEL tv=TRAVECinuse=INUSE
16886
16887
16888 Stream: as severity 0
16889
16890
16891
16892 ftp_dialup_ 292 08/21/20 MR12.7^L
16893
16894
16895 Time: While system is running.
16896
16897 Meaning: A wakeup occurred for CHANNEL whose user table
16898 entry pointer UTEP was non-null. A test on the
16899 above information determined that the state of the
16900 channel to be inconsistant. The system will null
16901 the UTEP pointer in the CDT for the above channel.
16902
16903 Action: Contact the system programming staff.
16904
16905
16906 ftp_dialup_.pl1
16907 ftp_dialup_: premature stopstop for
16908 PERSON.PROJECT CHANNEL
16909
16910
16911 Stream: as severity 0
16912
16913 Time: While system is running.
16914
16915 Meaning: This indicates a logic error in the supervisor or
16916 CPU or memory hardware problems.
16917
16918 Action: Contact the system programming staff.
16919
16920
16921 ftp_dialup_.pl1
16922 ftp_dialup_: process did not respond properly to
16923 trm_ signal. PERSON.PROJECT CHANNEL
16924
16925
16926 Stream: as severity 0
16927
16928 Time: While system is running.
16929
16930 Meaning: The PERSON.PROJECT process on CHANNEL was being
16931 terminated and had been sent the trm_ signal but
16932 it did not respond. User process will be bumped
16933 logged out or new_proced. It is possible that the
16934 user can cause this message.
16935
16936 Action: No operator action is required.
16937
16938
16939 ftp_dialup_.pl1
16940 ftp_dialup_: process ignored term signal
16941 PERSON.PROJECT CHANNEL
16942
16943
16944 Stream: as severity 1
16945
16946 Time: While system is running.
16947
16948
16949
16950 ftp_dialup_ 293 08/21/20 MR12.7^L
16951
16952
16953 Meaning: The PERSON.PROJECT process on CHANNEL had been
16954 sent a trm_ signal but the process did not respond
16955 to it. The process will be handled as was
16956 intended to be; bumped logged out etc.
16957
16958 Action: No operator action is required.
16959
16960
16961 ftp_dialup_.pl1
16962 ftp_dialup_: process terminated PERSON.PROJECT
16963 CHANNEL TERM_MESSAGE
16964
16965
16966 Stream: as severity 0
16967
16968 Time: While system is running.
16969
16970 Meaning: The process for PERSON.PROJECT on CHANNEL was
16971 terminated abnormally due to reason in
16972 TERM_MESSAGE.
16973
16974 Action: No operator action is required.
16975
16976
16977 ftp_dialup_.pl1
16978 ftp_dialup_: Program error: null atep with
16979 per-process tra_vec value
16980
16981
16982 Stream: as severity 2
16983
16984 Time: While system is running.
16985
16986 Meaning: A system programming error in the answering
16987 service has occurred as a wakeup occurred when
16988 tra_vec indicated to expect a process termination
16989 but the ate pointer was null.
16990
16991 Action: Contact the system programming staff.
16992
16993
16994 ftp_dialup_.pl1
16995 ftp_dialup_: Program error: null cdtep with
16996 per-channel tra_vec value
16997
16998
16999 Stream: as severity 2
17000
17001 Time: While system is running.
17002
17003 Meaning: A wakeup was received when the tra_vec value
17004 indicated a channel operation was required but the
17005
17006
17007
17008 ftp_dialup_ 294 08/21/20 MR12.7^L
17009
17010
17011 cdtep was null. This is considered to be a
17012 programming error.
17013
17014 Action: Contact the system programming staff.
17015
17016
17017 ftp_dialup_.pl1
17018 ftp_dialup_: Program error: per-process wakeup
17019 with per-channel-only tra_vec value
17020
17021
17022 Stream: as severity 2
17023
17024 Time: While system is running.
17025
17026 Meaning: A process wakeup occurred when the tra_vec value
17027 indicated it should be a channel wakeup. This is
17028 considered a programing error.
17029
17030 Action: Contact the system programming staff.
17031
17032
17033 ftp_dialup_.pl1
17034 ftp_dialup_: re-used cdte CDTEPCHANNEL by ate
17035 UTEP destroy_flag=DDDD
17036
17037
17038 Stream: as severity 0
17039
17040 Time: While system is running.
17041
17042 Meaning: An ate wakeup occurred which pointed to a CDTEP
17043 that was already in use by another process.
17044
17045 Action: Contact the system programming staff.
17046
17047
17048 ftp_dialup_.pl1
17049 ftp_dialup_: re-used cdte CDTEPCHANNEL by ate
17050 UTEP destroy_flag=DDDD
17051
17052
17053 Stream: as severity 0
17054
17055 Time: While system is running.
17056
17057 Meaning: An ate wakeup occurred which pointed to a CDTEP
17058 that was already in use by another process.
17059
17060 Action: Contact the system programming staff.
17061
17062
17063 ftp_dialup_.pl1
17064
17065
17066 ftp_dialup_ 295 08/21/20 MR12.7^L
17067
17068
17069 ftp_dialup_: terminating fatal process error loop
17070 for PERSON.PROJECT CHANNEL
17071
17072
17073 Stream: as severity 1
17074
17075 Time: While system is running.
17076
17077 Meaning: The process for PERSON.PROJECT on CHANNEL has
17078 taken too many fatal process errors. This is
17079 governed by fatal_error_loop_seconds and
17080 fatal_error_loop_count in the installation_parms.
17081 The user will not get a new process. The channel
17082 will not be hungup but will get a message
17083 indicating this condition. This message may be
17084 due to a user error.
17085
17086 Action: No operator action is required.
17087
17088
17089 ftp_dialup_.pl1
17090 ftp_dialup_: The answer table is full MAX
17091 entries.
17092
17093
17094 Stream: as severity 1
17095
17096 Time: While system is running.
17097
17098 Meaning: The system answer table is full and has MAX
17099 entries. No more users will be able to login.
17100
17101 Action: Contact the system programming staff.
17102
17103
17104 ftp_dialup_.pl1
17105 ftp_dialup_: trace event CHANNEL FFFFFFFF
17106 WWWWWWWWWWWW RRRRRRDDDDDD SS XXXX st N wp M
17107
17108
17109 Stream: as severity 1
17110
17111 Time: While system is running.
17112
17113 Meaning: This is trace output. When
17114 ftp_dialup_$ftp_dial_loud is called these
17115 messages are printed out for every signal
17116 concerning a device channel. FFFFFFFF is the
17117 function being performed. WWWWWWWWWWWW is the
17118 sending process ID. RRRRRR is the ring origin of
17119 the signal. DDDDDD is the device signal
17120 information. The pointer SS XXXX locates the
17121
17122
17123
17124 ftp_dialup_ 296 08/21/20 MR12.7^L
17125
17126
17127 answer table entry for CHANNEL. The channel state
17128 is N and the wait point transaction vector is M.
17129
17130 Action: No operator action is required. To turn these
17131 messages off type ftp_dialup_$ftp_dial_soft while
17132 in admin mode.
17133
17134
17135
17136 ftp_dialup_.pl1
17137 ftp_dialup_: turning off disconnected flag for
17138 ate UTEP cdte CDTEPCHANNEL
17139
17140
17141 Stream: as severity 0
17142
17143 Time: While system is running.
17144
17145 Meaning: If processing an ate wakeup the CHANNEL is known
17146 and the process is disconnected the disconnected
17147 flag for the ate will be turned off.
17148
17149 Action: Contact the system programming staff.
17150
17151
17152 ftp_dialup_.pl1
17153 ftp_dialup_: Unable to determine initial terminal
17154 type for channel CHANNEL
17155
17156
17157 Stream: as severity 2
17158
17159 Time: While system is running.
17160
17161 Meaning: Unable to determine the default terminal type
17162 based on line-type/baud-rate in the TTT. The
17163 channel has been removed from known channels.
17164
17165 Action: Contact the system programming staff.
17166
17167
17168 ftp_dialup_.pl1
17169 ftp_dialup_: unexpected state SSSS for channel
17170 definition table at CDTEP
17171
17172
17173 Stream: as severity 2
17174
17175 Time: While system is running.
17176
17177 Meaning: This indicates a logic error in the supervisor or
17178 CPU or memory hardware problems.
17179
17180
17181
17182 ftp_dialup_ 297 08/21/20 MR12.7^L
17183
17184
17185 Action: Contact the system programming staff.
17186
17187
17188 ftp_dialup_.pl1
17189 ftp_dialup_: Unexpected termsgnl for
17190 PERSON.PROJECT CHANNEL preempted=DDDD.
17191
17192
17193 Stream: as severity 0
17194
17195 Time: While system is running.
17196
17197 Meaning: A "termsgnl" wakeup was received for the
17198 PERSON.PROJECT process on CHANNEL whose
17199 ute.preempted value DDDD did not indicate one was
17200 allowed. This is considered to be a program
17201 error. User will be given a new process.
17202
17203 Action: Contact the system programming staff.
17204
17205
17206 ftp_dialup_.pl1
17207 ftp_dialup_: wrong answerback on CHANNEL
17208 COMMENT; expected "ID1" got "ID2".
17209
17210
17211 Stream: as severity 2
17212
17213 Time: While system is running.
17214
17215 Meaning: A terminal attempted to connect on CHANNEL whose
17216 CDT comment is COMMENT that is restricted to a
17217 specific answerback and did not return the
17218 expected value. ID1 is the answerback expected;
17219 ID2 is the answerback actually received. The
17220 terminal is hung up.
17221
17222 Action: No operator action is required.
17223
17224
17225 get_aste.pl1
17226 get_aste: Error deactivating UUUU vtoc V of pvt
17227 PV to free XXXk ASTE for USERNAME.
17228
17229
17230 Stream: Logged in SYSERR log.
17231
17232 Time: While system is running.
17233
17234 Meaning: The system encountered an error deactivating an
17235 AST entry which was selected for deactivation by
17236 the AST replacement algorithm. The AST on which
17237 the error was encountered will be flagged to be
17238
17239
17240 get_aste 298 08/21/20 MR12.7^L
17241
17242
17243 ingored by further passes of the algorithm; this
17244 flag will be reset during the next run of
17245 flush_ast_pool.
17246
17247 Action: If the problem persists contact the system
17248 programming staff.
17249
17250
17251 get_aste.pl1
17252 get_aste: Invalid csl x
17253
17254
17255 Stream: Logged in SYSERR log.
17256
17257 Time: While system is running.
17258
17259 Meaning: get_aste was called to activate a segment with x
17260 pages which is larger than the maximum segment
17261 size. This is indicative of hardware or software
17262 failure a typical problem is an invalid VTOCE.
17263
17264 Action: If the problem persists contact the system
17265 programming staff.
17266
17267
17268 get_aste.pl1
17269 get_aste: no removable XXXk ast entries
17270
17271
17272 Stream: BOS Typewriter.
17273
17274 Time: While system is running.
17275
17276 Meaning: An AST entry was needed for a segment of size XXX
17277 k but no free entries of that size were present
17278 and no segments occupying such entries could be
17279 deactivated. This could be symptomatic of a logic
17280 problem but may also indicate a grossly mistuned
17281 AST.
17282
17283 Action:
17284 Substantially increase the number of AST entries
17285 of this size as given on the SST CONFIG card. If
17286 the problem persists contact the system
17287 programming staff.
17288
17289
17290
17291 get_aste.pl1
17292 get_aste: no removable XXXk synchronized AST
17293 entries
17294
17295
17296
17297
17298 get_aste 299 08/21/20 MR12.7^L
17299
17300
17301 Stream: Logged in SYSERR log.
17302
17303 Time: While system is running.
17304
17305 Meaning: An AST entry was needed for a synchronized segment
17306 of size XXX k and the per-ASTE-pool limit on
17307 synchronized segments was reached. No
17308 synchronized segments in that pool could be
17309 deactivated.
17310
17311 Action: Contact the system programming staff.
17312
17313
17314 get_io_segs.pl1
17315 get_io_segs: DSKQ mmm. < xxx. per drive
17316 forcing DSKQ nnn.
17317
17318
17319 Stream: BOS Typewriter sounds beeper
17320
17321 Time: System Intialization.
17322
17323 Meaning: The dskq card specifies less than 5 queue entries
17324 per configured drive. This is considered too few
17325 for efficient operation and is forced to 5 entries
17326 per drive.
17327
17328 Action: $config
17329
17330
17331 get_io_segs.pl1
17332 get_io_segs: DSKQ mmm. > xxx. per drive
17333 forcing DSKQ nnn.
17334
17335
17336 Stream: BOS Typewriter sounds beeper
17337
17338 Time: System Intialization.
17339
17340 Meaning: The dskq card specifies an excess of queue entries
17341 beyond that reasonably required for efficient
17342 operation. The free queue will be limited to 100
17343 entries per drive.
17344
17345 Action: $config
17346
17347
17348 get_io_segs.pl1
17349 get_io_segs: Missing ndrives field on config card
17350 prph NAME.
17351
17352
17353 Stream: BOS Typewriter Crashes system
17354
17355
17356 get_io_segs 300 08/21/20 MR12.7^L
17357
17358
17359 Time: System Intialization.
17360
17361 Meaning: The prph card for the NAME subsystem is missing an
17362 ndrives field.
17363
17364 Action: $config
17365
17366
17367 get_main.pl1
17368 get_main: insufficient storage available for NAME
17369
17370
17371 Stream: BOS Typewriter Crashes system
17372
17373 Time: System Intialization.
17374
17375 Meaning: Insufficient wired memory was available to create
17376 the segment NAME during initialization. The
17377 system tape may be bad or the configuration may
17378 be too small or the system parameters specified
17379 in the configuration deck may be incorrect or
17380 inconsistent with the amount of main storage
17381 available.
17382
17383 Action: Follow normal recovery procedures. Check the
17384 configuration and the CONFIG deck. $boot_tape
17385
17386
17387
17388 get_main.pl1
17389 get_main: not enough room to allocate unpaged
17390 page table for NAME.
17391
17392
17393 Stream: BOS Typewriter Crashes system
17394
17395 Time: System Intialization.
17396
17397 Meaning: Either the segment unpaged_page_tables or
17398 int_unpaged_page_tables was not big enough so as
17399 to have the page table for segment NAME allocated
17400 within it. The system tape may be bad or changes
17401 made to the mst require bigger unpaged page
17402 tables.
17403
17404 Action: Follow normal recovery procedures. Try another
17405 tape. If bigger unpaged page tables are in order
17406 a change must be made to bootload_equs.incl.alm
17407 and collection 0 recompiled. $boot_tape
17408
17409
17410
17411 get_pvtx.pl1
17412
17413
17414 get_pvtx$cleanup 301 08/21/20 MR12.7^L
17415
17416
17417 get_pvtx$cleanup: Force released hold on pvtx ^d
17418 for USER_ID.
17419
17420
17421 Stream: BOS Typewriter.
17422
17423 Time: While system is running.
17424
17425 Meaning: This indicates a logic error in the supervisor or
17426 CPU or memory hardware problems. A condition was
17427 signalled in ring-0 which caused a crawlout.
17428 get_pvtx$cleanup will release all PV holds for the
17429 process.
17430
17431 Action: Contact the system programming staff.
17432
17433
17434 get_pvtx.pl1
17435 get_pvtx: drain_pvtx: pvte.being_demounted
17436 should be on.
17437
17438
17439 Stream: BOS Typewriter Crashes system
17440
17441 Time: While system is running.
17442
17443 Meaning: The entry to the physical volume demount
17444 protection mechanism which awaits all use of the
17445 volume to cease is being called improperly. A
17446 necessary precondition for its proper operation
17447 pvte.being_demounted is not met. This indicates
17448 a logic error in the supervisor or CPU or memory
17449 hardware problems.
17450
17451 Action: Follow normal recovery procedures.
17452
17453
17454 get_pvtx.pl1
17455 get_pvtx: hold_pvtx finds table full
17456
17457
17458 Stream: BOS Typewriter Crashes system
17459
17460 Time: While system is running.
17461
17462 Meaning: There are no free entries in the physical volume
17463 hold table. There should never be more than twice
17464 the number of eligible processes of used entries.
17465 This indicates a logic error in the supervisor or
17466 CPU or memory hardware problems.
17467
17468 Action: Follow normal recovery procedures.
17469
17470
17471
17472 get_pvtx 302 08/21/20 MR12.7^L
17473
17474
17475
17476
17477 get_pvtx.pl1
17478 get_pvtx: release_pvtx: mark not found
17479
17480
17481 Stream: BOS Typewriter Crashes system
17482
17483 Time: While system is running.
17484
17485 Meaning: While attempting to release a physical volume from
17486 demount protection the mark made by the
17487 protection could not be found in the physical
17488 volume hold table. This message can also occur if
17489 somehow the physical volume was demounted in spite
17490 of this protection or this entry point is being
17491 used improperly. This indicates a logic error in
17492 the supervisor or CPU or memory hardware
17493 problems.
17494
17495 Action: Follow normal recovery procedures.
17496
17497
17498 get_pvtx.pl1
17499 get_pvtx: ZERO_ENTRY fails
17500
17501
17502 Stream: BOS Typewriter Crashes system
17503
17504 Time: While system is running.
17505
17506 Meaning: The STACQ instruction has failed to clear an entry
17507 in the physical volume hold table. This indicates
17508 a logic error in the supervisor or CPU or memory
17509 hardware problems.
17510
17511 Action: Follow normal recovery procedures.
17512
17513
17514 grab_aste.pl1
17515 grab_aste: Attempt to reuse segno SSS
17516
17517
17518 Stream: BOS Typewriter Crashes system
17519
17520 Time: While system is running.
17521
17522 Meaning: A call has been made to force active a segment
17523 already forced active. This indicates an
17524 inconsistency in the programming of the
17525 supervisor. This indicates a logic error in the
17526 supervisor or CPU or memory hardware problems.
17527
17528
17529
17530 grab_aste 303 08/21/20 MR12.7^L
17531
17532
17533 Action: Follow normal recovery procedures. Contact the
17534 system programming staff.
17535
17536
17537
17538 grab_aste.pl1
17539 grab_aste: failed to reactivate PPPP ERRORMESSAGE
17540
17541
17542 Stream: BOS Typewriter Crashes system
17543
17544 Time: While system is running.
17545
17546 Meaning: This indicates a logic error in the supervisor or
17547 CPU or memory hardware problems.
17548
17549 Action: Follow normal recovery procedures. Contact the
17550 system programming staff.
17551
17552
17553
17554 grab_aste.pl1
17555 grab_aste: Unprotected segment: astep = AAA
17556
17557
17558 Stream: BOS Typewriter Crashes system
17559
17560 Time: While system is running.
17561
17562 Meaning: An attempt was made to release from forced
17563 activity a segment whose AST entry is at AAA
17564 which was not even in a state of forced activity.
17565 This indicates a logic error in the supervisor or
17566 CPU or memory hardware problems.
17567
17568 Action: Contact the system programming staff. Follow
17569 normal recovery procedures.
17570
17571
17572
17573 bootload_error.alm
17574 HALT with octal 5's in the upper half of the AQ.
17575
17576
17577 Stream: BOS Typewriter Crashes system
17578
17579 Time: System Intialization.
17580
17581 Meaning: The collection zero call stack has overflowed.
17582 This indicates a logic error in the collection
17583 zero supervisor or a hardware problem possibly
17584 with id or di modifiers.
17585
17586
17587
17588 HALT 304 08/21/20 MR12.7^L
17589
17590
17591 Action: Try another tape and/or look for a CPU bug.
17592
17593
17594 bootload_error.alm
17595 HALT with octal 6's in the upper half of the AQ.
17596
17597
17598 Stream: BOS Typewriter Crashes system
17599
17600 Time: System Intialization.
17601
17602 Meaning: A recursive error condition was encountered: that
17603 is the collection zero error handler was called
17604 recursively. The low half of the A contains the
17605 unique error number of the recursive error. See
17606 the listing of bootload_error.alm for error
17607 numbers. bootload_error$disaster_AQ contains the
17608 AQ at the time of recursive entry.
17609
17610 Action: This error indicates a logic error or a hardware
17611 problem. Use execute switches to return to BOS.
17612 Try a different tape. Failing that look for a
17613 CPU problem.
17614
17615
17616
17617 bootload_io.alm
17618 HALT with octal 777777000001 in the A register.
17619
17620
17621 Stream: BOS Typewriter Crashes system
17622
17623 Time: System Intialization.
17624
17625 Meaning: The interrupt base set on the bootload IOM is not
17626 1200 octal.
17627
17628 Action: Set the switches correctly.
17629
17630
17631 bootload_io.alm
17632 HALT with octal 777777000002 in the A register.
17633
17634
17635 Stream: BOS Typewriter Crashes system
17636
17637 Time: System Intialization.
17638
17639 Meaning: The iom base set on the bootload IOM is not
17640 correct. I.e. for IOM's 0 1 2 and 3 it should
17641 be 1400 2000 2400 and 3000 octal respectively.
17642
17643 Action: Set the switches correctly.
17644
17645
17646 HALT 305 08/21/20 MR12.7^L
17647
17648
17649
17650
17651 bootload_tape_label.alm
17652 HALT with only the first MST tape record read.
17653
17654
17655
17656 Stream: BOS Typewriter Crashes system
17657
17658 Time: System Intialization.
17659
17660 Meaning: If the high-order bit of the AQ register is on
17661 the pattern in the AQ register is the bad status
17662 returned by the IOM while reading a tape record.
17663 If the high order bit is not on the A register
17664 contains the flags word from a MST header record
17665 indicating that this record is bad.
17666
17667 Action: Try booting on a different drive or with a
17668 different tape.
17669
17670
17671 hardware_fault.pl1
17672 hardware_fault: Deleting frame at WWW from SCU X
17673 due to parity errors
17674
17675
17676 Stream: BOS Typewriter sounds beeper
17677
17678 Time: While system is running.
17679
17680 Meaning: A parity error was detected at main storage
17681 address WWWW. The main memory frame with the
17682 error was removed from service via delmain. The
17683 user process encountering the parity fault cannot
17684 be restarted at the point of error because the
17685 processor state is imprecise. If the parity error
17686 could have damaged user data the damaged switch
17687 is set on the segment and the user is given the
17688 best version we can come up with for the page.
17689
17690 Action: Contact Field Engineering personnel. The memory
17691 page will remain out of service until added back
17692 by addmain.
17693
17694
17695
17696 hardware_fault.pl1
17697 hardware_fault: FFF fault on CPU CPUTAG by
17698 PROCESSNAME.
17699
17700
17701 Stream: BOS Typewriter.
17702
17703
17704 hardware_fault 306 08/21/20 MR12.7^L
17705
17706
17707 Time: While system is running.
17708
17709 Meaning: A fault indicating processor or main memory
17710 malfunction has occurred on CPU CPUTAG. FFF is
17711 the name of the fault. Complete binary data about
17712 the fault is logged for automatic processing.
17713
17714 Action: Contact Field engineering personnel.
17715
17716
17717 hasp_mpx.pl1
17718 hasp_mpx line TTY: Bad block line status from
17719 FNP; line will be hungup.
17720
17721
17722 Stream: Note for system programmer action.
17723
17724 Time: While system is running.
17725
17726 Meaning: A block generated by the HASP multiplexer on
17727 channel TTY for transmission was malformed. The
17728 connection to the remote host/workstation is
17729 broken as communications cannot continue under
17730 these conditions.
17731
17732 Action: Contact the system programming staff.
17733
17734
17735 hasp_mpx.pl1
17736 hasp_mpx line TTY: Block received out of
17737 sequence: expected = N recevied = M; line will
17738 be hungup.
17739
17740
17741 Stream: Note for system programmer action.
17742
17743 Time: While system is running.
17744
17745 Meaning: One or more data blocks from the remote
17746 host/workstation for the HASP multiplexer on
17747 channel TTY were lost. The connection to the
17748 remote host/workstation is broken as
17749 communications cannot continue under these
17750 conditions.
17751
17752 Action: There are two possible causes for this message:
17753 communications equipment failures or problems in
17754 the remote host/workstation itself. The operator
17755 should contact the appropriate personnel before
17756 reusing the multiplexer.
17757
17758
17759
17760
17761
17762 hasp_mpx line TTY 307 08/21/20 MR12.7^L
17763
17764
17765 hasp_mpx.pl1
17766 hasp_mpx line TTY: Block recevied out of
17767 sequence: expected = N received = M; block
17768 ignored.
17769
17770
17771 Stream: Logged in SYSERR log.
17772
17773 Time: While system is running.
17774
17775 Meaning: A duplicate data block was received by the HASP
17776 multiplexer on channel TTY from the foreign
17777 host/workstation.
17778
17779 Action: The operator should ignore this message unless it
17780 occurs quite frequently. Frequent occurences of
17781 this message indicate possible problems in the
17782 communications equipment which should be
17783 investigated by the appropriate personnel.
17784
17785
17786
17787 hasp_mpx.pl1
17788 hasp_mpx line TTY: Block transmitted out of
17789 sequence: expected = N received = M; line will
17790 be hungup.
17791
17792
17793 Stream: Note for system programmer action.
17794
17795 Time: While system is running.
17796
17797 Meaning: One or more data blocks transmitted by the HASP
17798 multiplexer on channel TTY were not received by
17799 the remote host/workstation. The connection to
17800 the remote host/workstation is broken as
17801 communications cannot continue under these
17802 conditions.
17803
17804 Action: Contact the system programming staff. The HASP
17805 software is designed to prevent this situation
17806 even if the communications equipment is not
17807 functioning properly.
17808
17809
17810
17811 hasp_mpx.pl1
17812 hasp_mpx line TTY: Duplicate loopback block
17813 received: BCB = NNN
17814
17815
17816 Stream: Note for system programmer action.
17817
17818
17819
17820 hasp_mpx line TTY 308 08/21/20 MR12.7^L
17821
17822
17823 Time: While system is running.
17824
17825 Meaning: The output block identified by the 3-digit octal
17826 sequence NNN was returned to Multics twice by the
17827 FNP for reprocessing.
17828
17829 Action: Contact the system programming staff.
17830
17831
17832 hasp_mpx.pl1
17833 hasp_mpx line TTY: Invalid input block
17834 header/trailer; line will be hungup.
17835
17836
17837 Stream: Note for system programmer action.
17838
17839 Time: While system is running.
17840
17841 Meaning: A data block whose format does not conform to the
17842 HASP protocol was received from the remote
17843 host/workstation by the HASP multiplexer on
17844 channel TTY. The connection to the remote
17845 host/workstation is broken as communications
17846 cannot continue under these conditions.
17847
17848 Action: Frequent occurences of this message indicate that
17849 hardware or software problems may exist in the
17850 remote host/workstation. The operator should
17851 contact the appropriate personnel before reusing
17852 the multiplexer.
17853
17854
17855
17856 hasp_mpx.pl1
17857 hasp_mpx line TTY: No space available to
17858 preserve minor state; line will be hungup.
17859
17860
17861 Stream: BOS Typewriter.
17862
17863 Meaning: Insufficient space was available in tty_buf to
17864 perform part of the critical input processing of
17865 the HASP multiplexer on channel TTY. The
17866 connection to the remote host/workstation is
17867 broken as communications cannot continue under
17868 these conditions.
17869
17870 Action: Contact the system programming staff. It may be
17871 necessary to increase the size of tty_buf as
17872 specified on the PARM config card before using
17873 this multiplexer again.
17874
17875
17876
17877
17878 hasp_mpx line TTY 309 08/21/20 MR12.7^L
17879
17880
17881
17882
17883 hasp_mpx.pl1
17884 hasp_mpx line TTY: No space available to save
17885 loopback chain; line will be hungup.
17886
17887
17888 Stream: BOS Typewriter.
17889
17890 Meaning: Insufficient space was available in tty_buf to
17891 perform part of the critical input processing of
17892 the HASP multiplexer on channel TTY. The
17893 connection to the remote host/workstation is
17894 broken as communications cannot continue under
17895 these conditions.
17896
17897 Action: Contact the system programming staff. It may be
17898 necessary to increase the size of tty_buf as
17899 specified on the PARM config card before using
17900 this multiplexer again.
17901
17902
17903
17904 hasp_mpx.pl1
17905 hasp_mpx line TTY: Too many NAKs; line will be
17906 hungup.
17907
17908
17909 Stream: Note for system programmer action.
17910
17911 Time: While system is running.
17912
17913 Meaning: A block could not be transmitted or received by
17914 the HASP multiplexer on channel TTY because of
17915 excessive line noise. The connection to the
17916 remote host/workstation is broken as
17917 communications cannot continue under these
17918 conditions.
17919
17920 Action: The operator should contact the appropriate
17921 personnel to check the communications equipment
17922 used by the line before attempting to reuse this
17923 multiplexer.
17924
17925
17926
17927 hc_dmpr_primitives.pl1
17928 hc_dmpr_primitives: bad uid pathname detected at
17929 pvid WWWW vtocx XXXX
17930
17931
17932 Stream: Logged in SYSERR log.
17933
17934
17935
17936 hc_dmpr_primitives 310 08/21/20 MR12.7^L
17937
17938
17939 Time: While system is running.
17940
17941 Meaning: Part 3 of the indicated VTOCE is bad. The dumper
17942 will treat the vtoce as a null vtoce and continue.
17943
17944 Action: No operator action is required.
17945
17946
17947 hc_dmpr_primitives.pl1
17948 hc_dmpr_primitives: trailer storage area
17949 exhausted
17950
17951
17952 Stream: BOS Typewriter Crashes system
17953
17954 Time: While system is running.
17955
17956 Meaning: This indicates a logic error in the supervisor or
17957 CPU or memory hardware problems.
17958
17959 Action: Follow normal recovery procedures.
17960
17961
17962 hc_dmpr_primitives.pl1
17963 hc_dmpr_primitives: Unable to set label time.
17964 PVID = wwwwwwwwwwww
17965
17966
17967 Stream: BOS Typewriter.
17968
17969 Time: While system is running.
17970
17971 Meaning: A disk error prevented the updating of the
17972 time-last-dumped field in the volume label. The
17973 physical volume identifier is wwwwwwwwwwww.
17974
17975 Action: Contact the system programming staff.
17976
17977
17978 hc_initlzr_auxl_init_.pl1
17979 hc_initlrz_auxl_init_: MESSAGE. From
17980 hc_device_acct_$init.
17981
17982
17983 Stream: as severity2
17984
17985 Time: System Intialization.
17986
17987 Meaning: An error was detected while initializing device
17988 accounting.
17989
17990 Action: Contact the system programming staff.
17991
17992
17993
17994 hc_ipc 311 08/21/20 MR12.7^L
17995
17996
17997
17998
17999 hc_ipc.pl1
18000 hc_ipc: ITT overflow caused by NAME.PROJ
18001
18002
18003 Stream: BOS Typewriter.
18004
18005 Time: While system is running.
18006
18007 Meaning: When wakeups are sent from one process to another
18008 or from a device like a tape drive to a process
18009 the wakeups are stored temporarily in the
18010 Interprocess Transmission Table ITT. If wakeups
18011 are sent too fast or if the receiving process
18012 never calls block to read its wakeups the ITT may
18013 overflow. When the ITT is full this message is
18014 printed for each lost wakeup. The message
18015 identifies the sender of the wakeup who may be
18016 innocent of any error or wrongdoing.
18017
18018 If a critical system function cannot send a
18019 wakeup the system may crash.
18020
18021 Action: If the ITT overflow is a transient condition this
18022 message will stop coming out after a few minutes.
18023 If so system operation may return to normal. If
18024 the message comes out repeatedly the system will
18025 have to be crashed since user terminal operation
18026 daemon operations and the message coordinator
18027 depend on wakeups. Follow normal recovery
18028 procedures.
18029
18030
18031
18032 hc_ipc.pl1
18033 hc_ipc: Unable to allocate in ring RINGNO ECT for
18034 NAME.PROJ
18035
18036
18037 Stream: Logged in SYSERR log.
18038
18039 Time: While system is running.
18040
18041 Meaning: When a process recieves wakeups they are copied
18042 from the Interprocess Transmission Table to an
18043 Event Channel Table ECT. A process owns one ECT
18044 per ring. If for any reason an entry for a
18045 wakeup cannot be allocated in a process' ECT that
18046 process is terminated.
18047
18048
18049
18050
18051
18052 hc_ipc 312 08/21/20 MR12.7^L
18053
18054
18055 Action: If the process is a daemon process it must be
18056 reinitialized. If the process is the initializer
18057 process the system will crash.
18058
18059
18060
18061 hc_load_mpc.pl1
18062 hc_load_mpc: Booting channel CHNL with FWID
18063 Revision REV hc_load_mpc: Booting channel CHNL
18064 with FWID Revision REV Overlay FWOVERLAY
18065
18066
18067
18068 Stream: BOS Typewriter.
18069
18070 Time: System Intialization.
18071
18072 Meaning: No operator action is required.
18073
18074 Action: $config
18075
18076
18077 hc_load_mpc.pl1
18078 hc_load_mpc: Booting channel CHNL with FWID
18079 Revision REV hc_load_mpc: Booting channel CHNL
18080 with FWID Revision REV Overlay FWOVERLAY
18081
18082
18083
18084 Stream: BOS Typewriter.
18085
18086 Time: System Intialization.
18087
18088 Meaning: No operator action is required.
18089
18090 Action: $config
18091
18092
18093 hc_load_mpc.pl1
18094 hc_load_mpc: Could not abs_wire buffer.
18095
18096
18097 Stream: BOS Typewriter Crashes system
18098
18099 Time: System Intialization.
18100
18101 Meaning: This indicates a logic error in the supervisor or
18102 CPU or memory hardware problems.
18103
18104 Action: Contact the system programming staff.
18105
18106
18107
18108
18109
18110 hc_load_mpc 313 08/21/20 MR12.7^L
18111
18112
18113
18114
18115 hc_load_mpc.pl1
18116 hc_load_mpc: Could not abs_wire buffer.
18117
18118
18119 Stream: BOS Typewriter Crashes system
18120
18121 Time: System Intialization.
18122
18123 Meaning: This indicates a logic error in the supervisor or
18124 CPU or memory hardware problems.
18125
18126 Action: Contact the system programming staff.
18127
18128
18129 hc_load_mpc.pl1
18130 hc_load_mpc: data buffer not in low 256K
18131
18132
18133 Stream: BOS Typewriter Crashes system
18134
18135 Time: System Intialization.
18136
18137 Meaning: This indicates a logic error in the supervisor or
18138 CPU or memory hardware problems.
18139
18140 Action: Contact the system programming staff.
18141
18142
18143
18144
18145 hc_load_mpc.pl1
18146 hc_load_mpc: data buffer not in low 256K
18147
18148
18149 Stream: BOS Typewriter Crashes system
18150
18151 Time: System Intialization.
18152
18153 Meaning: This indicates a logic error in the supervisor or
18154 CPU or memory hardware problems.
18155
18156 Action: Contact the system programming staff.
18157
18158
18159
18160
18161 hc_page_trace.pl1
18162 hc_page_trace: pds$trace.threshold found zero for
18163 USER.
18164
18165
18166
18167
18168 hc_page_trace 314 08/21/20 MR12.7^L
18169
18170
18171 Meaning: The signalling threshold for page tracing was
18172 found to be zero for USER. This indicates that
18173 the user's pds has been damaged.
18174
18175 Stream: BOS Typewriter Terminates user process
18176
18177 Time: While system is running.
18178
18179 Action: Investigate the saved dead process.
18180
18181
18182 ibm3270_mpx.pl1
18183 ibm3270_mpx: Attempt to queue write while write
18184 queued CHANNEL.SUBCHANNEL
18185
18186
18187 Stream: Logged in SYSERR log.
18188
18189 Time: While system is running.
18190
18191 Meaning: An attempt was made to queue a write while a
18192 previous write was still queued. A dump of the
18193 subchannel entry as defined by the mde structure
18194 in ibm3270_mpx_data.incl.pl1 is included with this
18195 message.
18196
18197 Action: No operator action is required.
18198
18199
18200 ibm3270_mpx.pl1
18201 ibm3270_mpx: Buffer tally error on CHANNEL.
18202
18203
18204 Stream: BOS Typewriter Crashes system
18205
18206 Time: While system is running.
18207
18208 Meaning: An attempt was made to add characters to a buffer
18209 which should have fit but couldn't.
18210
18211 Action: Contact the system programming staff.
18212
18213
18214 ibm3270_mpx.pl1
18215 ibm3270_mpx: Could not find queued write on
18216 CHANNEL.
18217
18218
18219 Stream: BOS Typewriter sounds beeper
18220
18221 Time: While system is running.
18222
18223
18224
18225
18226 ibm3270_mpx 315 08/21/20 MR12.7^L
18227
18228
18229 Meaning: The reset_channel internal procedure could not
18230 find a queued write on CHANNEL or it detected
18231 itself looping in releasing queued writes for
18232 CHANNEL. Will attempt to continue.
18233
18234 Action: Contact the system programming staff.
18235
18236
18237 ibm3270_mpx.pl1
18238 ibm3270_mpx: Error trimming buffer chain for
18239 CHANNEL
18240
18241
18242 Stream: BOS Typewriter Crashes system
18243
18244 Time: While system is running.
18245
18246 Meaning: An inconsistency was found while trimming the
18247 buffer chain for CHANNEL which is stored in
18248 tty_buf.
18249
18250 Action: Contact the system programming staff.
18251
18252
18253 ibm3270_mpx.pl1
18254 ibm3270_mpx: Input for illegal device address
18255 DEV_ADDRESS on CHANNEL
18256
18257
18258 Stream: BOS Typewriter.
18259
18260 Time: While system is running.
18261
18262 Meaning: Received input for a device whose address
18263 DEV_ADDRESS is not in the channel map for
18264 CHANNEL.
18265
18266 Action: Contact the system programming staff.
18267
18268
18269 ibm3270_mpx.pl1
18270 ibm3270_mpx: Input for unconfigured device
18271 DEV_ADDRESS on CHANNEL
18272
18273
18274 Stream: BOS Typewriter.
18275
18276 Time: While system is running.
18277
18278 Meaning: Received input for a device DEV_ADDRESS whose
18279 subchannel was <= 0 in the channel map for
18280 CHANNEL.
18281
18282
18283
18284 ibm3270_mpx 316 08/21/20 MR12.7^L
18285
18286
18287 Action: Contact the system programming staff.
18288
18289
18290 ibm3270_mpx.pl1
18291 ibm3270_mpx: Unrecognized input for CHANNEL:
18292 DATA
18293
18294
18295 Stream: BOS Typewriter.
18296
18297 Time: While system is running.
18298
18299 Meaning: DATA received from CHANNEL does not meet certain
18300 format requirements. This message is only
18301 displayed if in debug mode.
18302
18303 Action: Contact the system programming staff.
18304
18305
18306 ibm3270_mpx.pl1
18307 ibm3270_mpx: Unrecognized interrupt for CHANNEL.
18308 INT_TYPE INTERRUPT_INFO
18309
18310
18311 Stream: BOS Typewriter.
18312
18313 Time: While system is running.
18314
18315 Meaning: An interrupt was received from the FNP which does
18316 not have a defined action. The type of interrupt
18317 received is INT_TYPE and the information supplied
18318 with the interrupt is INTERRUPT_INFO.
18319
18320 Action: Contact the system programming staff.
18321
18322
18323 init_branches.pl1
18324 init_branches: $branch From asd_: ERRORMESSAGE
18325
18326
18327 Stream: BOS Typewriter.
18328
18329 Time: System Intialization.
18330
18331 Meaning: This indicates a logic error in the supervisor or
18332 CPU or memory hardware problems. Initialization
18333 continues.
18334
18335 Action: Contact the system programming staff.
18336
18337
18338 init_branches.pl1
18339
18340
18341
18342 init_branches 317 08/21/20 MR12.7^L
18343
18344
18345 init_branches: couldn't add name pdd to
18346 process_dir_dir: ERRORMESSAGE
18347
18348
18349 Stream: BOS Typewriter.
18350
18351 Time: System Intialization.
18352
18353 Meaning: This indicates a logic error in the supervisor or
18354 CPU or memory hardware problems. Initialization
18355 continues. Certain application programs may fail
18356 to work.
18357
18358 Action: Contact the system programming staff.
18359
18360
18361 init_branches.pl1
18362 init_branches: couldn't add name sl1 to
18363 system_library_1: ERRORMESSAGE
18364
18365
18366 Stream: BOS Typewriter.
18367
18368 Time: System Intialization.
18369
18370 Meaning: This indicates a logic error in the supervisor or
18371 CPU or memory hardware problems. Initialization
18372 continues. Certain application programs may fail
18373 to work.
18374
18375 Action: Contact the system programming staff.
18376
18377
18378 init_branches.pl1
18379 init_branches: couldn't set dirquota on >pdd to
18380 XXXX: ERRORMESSAGE
18381
18382
18383 Stream: BOS Typewriter.
18384
18385 Time: System Intialization.
18386
18387 Meaning: This indicates a logic error in the supervisor or
18388 CPU or memory hardware problems. Initialization
18389 continues. The answering service may encounter
18390 trouble in creating processes.
18391
18392 Action: Contact the system programming staff.
18393
18394
18395 init_branches.pl1
18396 init_branches: deleting old pdd: ERRORMESSAGE
18397
18398
18399
18400 init_branches 318 08/21/20 MR12.7^L
18401
18402
18403 Stream: BOS Typewriter Crashes system
18404
18405 Time: System Intialization.
18406
18407 Meaning: The name pdd could not be removed from >pdd. This
18408 indicates a logic error in the supervisor or CPU
18409 or memory hardware problems.
18410
18411 Action: Follow normal recovery procedures.
18412
18413
18414 init_branches.pl1
18415 init_branches: error from initiate. ERRORMESSAGE
18416
18417
18418 Stream: BOS Typewriter Crashes system
18419
18420 Time: System Intialization.
18421
18422 Meaning: A deciduous segment could not be made known. This
18423 indicates a logic error in the supervisor or CPU
18424 or memory hardware problems.
18425
18426 Action: Follow normal recovery procedures.
18427
18428
18429 init_branches.pl1
18430 init_branches: error from set$max_length
18431 ERRORMESSAGE
18432
18433
18434 Stream: BOS Typewriter Crashes system
18435
18436 Time: System Intialization.
18437
18438 Meaning: This indicates a logic error in the supervisor or
18439 CPU or memory hardware problems.
18440
18441 Action: Follow normal recovery procedures.
18442
18443
18444 init_branches.pl1
18445 init_branches: error from terminate_:
18446 ERRORMESSAGE
18447
18448
18449 Stream: BOS Typewriter Crashes system
18450
18451 Time: System Intialization.
18452
18453 Meaning: This indicates a logic error in the supervisor or
18454 CPU or memory hardware problems.
18455
18456
18457
18458 init_branches 319 08/21/20 MR12.7^L
18459
18460
18461 Action: Follow normal recovery procedures.
18462
18463
18464 init_branches.pl1
18465 init_branches: error in adding acl of dumps:
18466 ERRORMESSAGE
18467
18468
18469 Stream: BOS Typewriter.
18470
18471 Time: System Intialization.
18472
18473 Meaning: This indicates a logic error in the supervisor or
18474 CPU or memory hardware problems. Initialization
18475 continues. The copy_fdump command may fail. The
18476 online salvager may fail to make stack and
18477 directory copies in >dumps.
18478
18479 Action: Contact the system programming staff.
18480
18481
18482 init_branches.pl1
18483 init_branches: error in replacing acl of >sl1.
18484 ERRORMESSAGE
18485
18486
18487 Stream: BOS Typewriter.
18488
18489 Time: System Intialization.
18490
18491 Meaning: This indicates a logic error in the supervisor or
18492 CPU or memory hardware problems. Initialization
18493 continues. User and daemon processes may
18494 malfunction.
18495
18496 Action: Contact the system programming staff.
18497
18498
18499 init_branches.pl1
18500 init_branches: From set$max_length: ERRORMESSAGE
18501
18502
18503 Stream: BOS Typewriter Crashes system
18504
18505 Time: System Intialization.
18506
18507 Meaning: This indicates a logic error in the supervisor or
18508 CPU or memory hardware problems.
18509
18510 Action: Follow normal recovery procedures.
18511
18512
18513
18514
18515
18516 init_branches 320 08/21/20 MR12.7^L
18517
18518
18519
18520
18521 init_branches.pl1
18522 init_branches: From status_$long: ERRORMESSAGE
18523
18524
18525 Stream: BOS Typewriter Crashes system
18526
18527 Time: System Intialization.
18528
18529 Meaning: This indicates a logic error in the supervisor or
18530 CPU or memory hardware problems.
18531
18532 Action: Follow normal recovery procedures.
18533
18534
18535 init_branches.pl1
18536 init_branches: getting dir entry pointer:
18537 ERRORMESSAGE
18538
18539
18540 Stream: BOS Typewriter Crashes system
18541
18542 Time: System Intialization.
18543
18544 Meaning: This indicates a logic error in the supervisor or
18545 CPU or memory hardware problems.
18546
18547 Action: Follow normal recovery procedures.
18548
18549
18550 init_branches.pl1
18551 init_branches: Mysterious directory deactivation
18552
18553
18554 Stream: BOS Typewriter Crashes system
18555
18556 Time: System Intialization.
18557
18558 Meaning: This indicates a logic error in the supervisor or
18559 CPU or memory hardware problems.
18560
18561 Action: Follow normal recovery procedures.
18562
18563
18564 init_branches.pl1
18565 init_branches: renaming old pdd: ERRORMESSAGE
18566
18567
18568 Stream: BOS Typewriter Crashes system
18569
18570 Time: System Intialization.
18571
18572
18573
18574 init_branches 321 08/21/20 MR12.7^L
18575
18576
18577 Meaning: This indicates a logic error in the supervisor or
18578 CPU or memory hardware problems.
18579
18580 Action: Follow normal recovery procedures.
18581
18582
18583 init_branches.pl1
18584 init_branches: renaming process_dir_dir:
18585 ERRORMESSAGE
18586
18587
18588 Stream: BOS Typewriter Crashes system
18589
18590 Time: System Intialization.
18591
18592 Meaning: This indicates a logic error in the supervisor or
18593 CPU or memory hardware problems.
18594
18595 Action: Follow normal recovery procedures.
18596
18597
18598 init_branches.pl1
18599 init_branches: replacing >pdd acl: ERRORMESSAGE
18600
18601
18602 Stream: BOS Typewriter.
18603
18604 Time: System Intialization.
18605
18606 Meaning: This indicates a logic error in the supervisor or
18607 CPU or memory hardware problems. Initialization
18608 continues.
18609
18610 Action: Contact the system programming staff.
18611
18612
18613 init_branches.pl1
18614 init_branches: replacing acl of >pdd for
18615 Initializer: ERRORMESSAGE
18616
18617
18618 Stream: BOS Typewriter.
18619
18620 Time: System Intialization.
18621
18622 Meaning: This indicates a logic error in the supervisor or
18623 CPU or memory hardware problems. Initialization
18624 continues.
18625
18626 Action: Contact the system programming staff.
18627
18628
18629 init_branches.pl1
18630
18631
18632 init_branches 322 08/21/20 MR12.7^L
18633
18634
18635 init_branches: unable to append dumps directory.
18636 ERRORMESSAGE
18637
18638
18639 Stream: BOS Typewriter sounds beeper
18640
18641 Time: System Intialization.
18642
18643 Meaning: This indicates a logic error in the supervisor or
18644 CPU or memory hardware problems. Initialization
18645 continues.
18646
18647 Action: Contact the system programming staff.
18648
18649
18650 init_branches.pl1
18651 init_branches: unable to initiate >DIRNAME:
18652 ERRORMESSAGE
18653
18654
18655 Stream: BOS Typewriter Crashes system
18656
18657 Time: System Intialization.
18658
18659 Meaning: This indicates a logic error in the supervisor or
18660 CPU or memory hardware problems.
18661
18662 Action: Follow normal recovery procedures.
18663
18664
18665 init_branches.pl1
18666 init_branches: unable to make >system_library_1:
18667 ERRORMESSAGE
18668
18669
18670 Stream: BOS Typewriter Crashes system
18671
18672 Time: System Intialization.
18673
18674 Meaning: This indicates a logic error in the supervisor or
18675 CPU or memory hardware problems.
18676
18677 Action: Follow normal recovery procedures.
18678
18679
18680 init_branches.pl1
18681 init_branches: unable to make process_dir_dir:
18682 ERRORMESSAGE
18683
18684
18685 Stream: BOS Typewriter Crashes system
18686
18687 Time: System Intialization.
18688
18689
18690 init_branches 323 08/21/20 MR12.7^L
18691
18692
18693 Meaning: This indicates a logic error in the supervisor or
18694 CPU or memory hardware problems.
18695
18696 Action: Follow normal recovery procedures.
18697
18698
18699 init_branches.pl1
18700 init_branches: dirquotas for pdir:
18701 ERRORMESSAGE
18702
18703
18704 Stream: BOS Typewriter.
18705
18706 Time: System Intialization.
18707
18708 Meaning: This indicates a logic error in the supervisor or
18709 CPU or memory hardware problems. Initialization
18710 continues.
18711
18712 Action: Contact the system programming staff.
18713
18714
18715 init_disk_pack_.pl1
18716 init_disk_pack_: Specified control argument not
18717 accepted. "-rlv" allowed only at ring-1 during a
18718 cold boot.
18719
18720
18721
18722 Stream: Initializer process output.
18723
18724 Time: In response to an operator command.
18725
18726 Meaning: Automatic registration of root PVs is allowed only
18727 during a cold boot of Multics.
18728
18729 Action: Use the "add_volume_registration" administrative
18730 command to register the PV before attempting to
18731 initialize it.
18732
18733
18734
18735 init_disk_pack_.pl1
18736 init_disk_pack_: Cannot read current label of
18737 DRIVE: ERROR_MESSAGE
18738
18739
18740 Stream: Initializer process output.
18741
18742 Time: In response to an operator command.
18743
18744
18745
18746
18747
18748 init_disk_pack_ 324 08/21/20 MR12.7^L
18749
18750
18751 Meaning: A disk error prevents checking the label of the
18752 pack on DRIVE. The pack may need to be formatted
18753 before it can be initialized.
18754
18755 Action: Take appropriate action.
18756
18757
18758 init_disk_pack_.pl1
18759 init_disk_pack_: DRIVE PVNAME disk err WWWW on
18760 ITEM
18761
18762
18763 Stream: Initializer process output.
18764
18765 Time: In response to an operator command.
18766
18767 Meaning: A disk error prevents writing the ITEM section of
18768 the disk volume PVNAME.
18769
18770 Action: Fix the drive or use a new pack.
18771
18772
18773 init_disk_pack_.pl1
18774 init_disk_pack_: INTK card missing from config
18775 deck.
18776
18777
18778 Stream: Initializer process output.
18779
18780 Time: In response to an operator command.
18781
18782 Meaning: When the operator specifies the "-rlv" control
18783 argument to "init_vol" this program attempts to
18784 verify that the system is in cold boot by
18785 inspecting the INTK card in the config deck. When
18786 this message appears there is some difficulty in
18787 locating that card.
18788
18789 Action: If really trying to boot cold try again.
18790
18791
18792 init_disk_pack_.pl1
18793 init_disk_pack_: unrecognized argument: BLAH
18794
18795
18796 Stream: Initializer process output.
18797
18798 Time: In response to an operator command.
18799
18800 Meaning: Illegal input was typed.
18801
18802 Action: Enter a corrected command line.
18803
18804
18805
18806 init_disk_pack_ 325 08/21/20 MR12.7^L
18807
18808
18809
18810
18811 init_disk_pack_.pl1
18812 init_disk_pack_: Volume on DRIVE is a copy of
18813 Multics Storage System Volume "PVNAME"
18814 last used DATE_TIME. Do you wish to overwrite it?
18815
18816
18817
18818 Stream: Initializer process output.
18819
18820 Time: In response to an operator command.
18821
18822 Meaning: The init_disk command specifed a disk pack which
18823 has a valid Multics label. Another copy of PVNAME
18824 is currently in use. Initializing this pack will
18825 destroy all data contained on it.
18826
18827 Action: Do not answer yes unless you are sure that the
18828 pack contents should be destroyed. Check the pack
18829 serial number.
18830
18831
18832
18833 init_disk_pack_.pl1
18834 init_disk_pack_: Volume on DRIVE is a copy of pv
18835 "PVNAME"
18836 last used DATE_TIME. Do you wish to overwrite it?
18837
18838
18839
18840 Stream: Initializer process output.
18841
18842 Time: In response to an operator command.
18843
18844 Meaning: The init_disk command specifed a disk pack which
18845 has a valid Multics label. It appears to be a
18846 copy of a mounted pack. Initializing this pack
18847 will destroy all data contained on it.
18848
18849 Action: Do not answer yes unless you are sure that the
18850 pack contents should be destroyed. Check the pack
18851 serial number.
18852
18853
18854
18855 init_disk_pack_.pl1
18856 init_disk_pack_: Volume on DRIVE is an earlier
18857 instance of pv "PVNAME"
18858 last used DATE_TIME. Do you wish to overwrite it?
18859
18860
18861
18862
18863
18864 init_disk_pack_ 326 08/21/20 MR12.7^L
18865
18866
18867 Stream: Initializer process output.
18868
18869 Time: In response to an operator command.
18870
18871 Meaning: The init_disk command specifed a disk pack which
18872 has a valid Multics label. Initializing this pack
18873 will destroy all data contained on it.
18874
18875 Action: Do not answer yes unless you are sure that the
18876 pack contents should be destroyed. Check the pack
18877 serial number.
18878
18879
18880
18881 init_disk_pack_.pl1
18882 init_disk_pack_: Volume on DRIVE is an
18883 unregistered pack named "PVNAME"
18884 last used DATE_TIME. Do you wish to overwrite it?
18885
18886
18887
18888 Stream: Initializer process output.
18889
18890 Time: In response to an operator command.
18891
18892 Meaning: The init_disk command specifed a disk pack which
18893 has a valid Multics label. Initializing this pack
18894 will destroy all data contained on it.
18895
18896 Action: Do not answer yes unless you are sure that the
18897 pack contents should be destroyed. Check the pack
18898 serial number.
18899
18900
18901
18902 init_disk_pack_.pl1
18903 init_disk_pack_: Volume on DRIVE is Multics
18904 Storage System Volume "PVNAME"
18905 last used DATE_TIME. Do you wish to overwrite it?
18906
18907
18908
18909 Stream: Initializer process output.
18910
18911 Time: In response to an operator command.
18912
18913 Meaning: The init_disk command specifed a disk pack which
18914 has a valid Multics label. Initializing this pack
18915 will destroy all data contained on it.
18916
18917 Action: Do not answer yes unless you are sure that the
18918 pack contents should be destroyed. Check the pack
18919 serial number.
18920
18921
18922 init_disk_pack_ 327 08/21/20 MR12.7^L
18923
18924
18925
18926
18927 init_dm_journal_seg.pl1
18928 init_dm_journal_seg: Invalid DBMJ config card.
18929
18930
18931 Stream: BOS Typewriter Crashes system
18932
18933 Time: System Intialization.
18934
18935 Meaning: The DBMJ configuration card is not in proper
18936 format. This could be a format error or one of
18937 the following criteria may not be satisfied. The
18938 limit on active segments for a pool must be
18939 smaller than the pool size.
18940
18941 Action: Correct the configuration deck and reboot.
18942
18943
18944 init_dm_journal_seg.pl1
18945 init_dm_journal_seg: make_sdw failed for
18946 dm_journal_seg_
18947
18948
18949 Stream: BOS Typewriter Crashes system
18950
18951 Time: System Intialization.
18952
18953 Meaning: The ASTE for dm_journal_seg_ could not be created.
18954
18955 Action: Contact the system programming staff.
18956
18957
18958 init_early_config.pl1
18959 init_early_config: Cannot add card to config
18960 deck: CARD.
18961
18962
18963 Stream: BOS Typewriter Crashes system
18964
18965 Time: System Intialization.
18966
18967 Meaning: The config_deck being generated during the early
18968 hardware inspection pass of bce is damaged.
18969 This can be either a hardware or software problem.
18970
18971 Action: $reboot
18972
18973
18974 init_hc_part.pl1
18975 init_hc_part: HC PART on dskX_NN too small
18976
18977
18978
18979
18980 init_hc_part 328 08/21/20 MR12.7^L
18981
18982
18983 Stream: BOS Typewriter Crashes system
18984
18985 Time: System Intialization.
18986
18987 Meaning: The Hardcore Partition on the device indicated is
18988 unreasonably small as it does not contain
18989 sufficient space to hold the bit map describing
18990 it.
18991
18992 Action: Recreate the partition and reboot.
18993
18994
18995 init_hc_part.pl1
18996 init_hc_part: HC PART on dskX_NN too small
18997
18998
18999 Stream: BOS Typewriter Crashes system
19000
19001 Time: System Intialization.
19002
19003 Meaning: The Hardcore Partition on the device indicated is
19004 unreasonably small as it does not contain
19005 sufficient space to hold the bit map describing
19006 it.
19007
19008 Action: Recreate the partition and reboot.
19009
19010
19011 init_hc_part.pl1
19012 init_hc_part: volmap_abs_seg size too small
19013
19014
19015 Time: System Intialization.
19016
19017 Stream: BOS Typewriter Crashes system
19018
19019 Meaning: The maximum length of volmap_abs_seg on the MST
19020 header is not sufficient to access an entire
19021 Volume Map.
19022
19023 Action: Recreate the MST with a larger maximum length for
19024 volmap_abs_seg and reboot.
19025
19026
19027
19028 init_hc_part.pl1
19029 init_hc_part: volmap_abs_seg size too small
19030
19031
19032 Time: System Intialization.
19033
19034 Stream: BOS Typewriter Crashes system
19035
19036
19037
19038 init_hc_part 329 08/21/20 MR12.7^L
19039
19040
19041 Meaning: The maximum length of volmap_abs_seg on the MST
19042 header is not sufficient to access an entire
19043 Volume Map.
19044
19045 Action: Recreate the MST with a larger maximum length for
19046 volmap_abs_seg and reboot.
19047
19048
19049
19050 init_lvt.pl1
19051 init_lvt: unable to define RLV code = WWWW
19052
19053
19054 Stream: BOS Typewriter Crashes system
19055
19056 Time: System Intialization.
19057
19058 Meaning: This indicates a logic error in the supervisor or
19059 CPU or memory hardware problems.
19060
19061 Action: Follow normal recovery procedures. $boot_tape
19062
19063
19064
19065 init_lvt.pl1
19066 init_lvt: unable to read RPV label code = WWWW
19067
19068
19069 Stream: BOS Typewriter Crashes system
19070
19071 Time: System Intialization.
19072
19073 Meaning: The RPV label which was successfully read a few
19074 seconds ago cannot be read.
19075
19076 Action: Follow normal recovery procedures. $boot_tape
19077
19078
19079
19080 init_partitions.pl1
19081 init_partition: part PART_NAME for part PART_ID
19082 not in label of DISK_DRIVE pvtx PVTX.
19083
19084
19085 Stream: BOS Typewriter Crashes system
19086
19087 Time: System Intialization.
19088
19089 Meaning: A PART card specified DISK_DRIVE as the location
19090 of partition PART_NAME but the label of
19091 DISK_DRIVE does not define it.
19092
19093 Action: Fix the config deck.
19094
19095
19096 init_partition 330 08/21/20 MR12.7^L
19097
19098
19099
19100
19101 init_partitions.pl1
19102 init_partition: part PART_NAME not in label of
19103 DISK_DRIVE pvtx PVTX.
19104
19105
19106 Stream: BOS Typewriter Crashes system
19107
19108 Time: System Intialization.
19109
19110 Meaning: A PART card specified DISK_DRIVE as the location
19111 of partition PART_NAME but the label of
19112 DISK_DRIVE does not define it.
19113
19114 Action: Fix the config deck.
19115
19116
19117 init_partitions.pl1
19118 init_partition: There are no partitions in the
19119 label for DISK_DRIVE pvtx PVTX.
19120
19121
19122 Stream: BOS Typewriter Crashes system
19123
19124 Time: System Intialization.
19125
19126 Meaning: DISK_DRIVE has been specified on a part card but
19127 has no partitions defined in its label.
19128
19129 Action: Fix the config deck.
19130
19131
19132 init_partitions.pl1
19133 init_partitions: Error reading DISK_DRIVE label.
19134 PROBLEM ERROR_MESSAGE
19135
19136
19137 Stream: BOS Typewriter Crashes system
19138
19139 Time: System Intialization.
19140
19141 Meaning: An error has been detected attempting to read the
19142 label of DISK_DRIVE.
19143
19144 Action: Correct problem and type "go" to retry the read.
19145
19146
19147 init_partitions.pl1
19148 init_partitions: Ignoring COLD_SPEC on PART_NAME
19149 part card.
19150
19151
19152
19153
19154 init_partitions 331 08/21/20 MR12.7^L
19155
19156
19157 Stream: BOS Typewriter sounds beeper
19158
19159 Time: System Intialization.
19160
19161 Meaning: Cold boot partition specifications were found for
19162 partition PART_NAME and will be ignored.
19163
19164
19165
19166 init_partitions.pl1
19167 init_partitions: Invalid device DISK_DRIVE on
19168 PART_NAME part card.
19169
19170
19171 Stream: BOS Typewriter Crashes system
19172
19173 Time: System Intialization.
19174
19175 Meaning: An invalid drive definition has been found for the
19176 PART_NAME part card.
19177
19178 Action: Fix PART card.
19179
19180
19181 init_partitions.pl1
19182 init_partitions: Unable to locate DISK_DRIVE for
19183 PART_NAME partition.
19184
19185
19186 Stream: BOS Typewriter Crashes system
19187
19188 Time: System Intialization.
19189
19190 Meaning: Partition PART_NAME is specified in the config
19191 deck for a non existent DISK_DRIVE.
19192
19193 Action: Fix PART and/or PRPH DSK cards.
19194
19195
19196 init_proc.pl1
19197 init_proc: bad process type N given for
19198 PERSON.PROJ.T
19199
19200
19201 Stream: BOS Typewriter sounds beeper
19202
19203 Time: While system is running.
19204
19205 Meaning: The answering service has specified an unknown
19206 integer in the process type field. Incorrect
19207 arguments were passed to hphcs_$create_proc. The
19208 user cannot be logged in.
19209
19210
19211
19212 init_proc 332 08/21/20 MR12.7^L
19213
19214
19215 Action: Contact the system programming staff.
19216
19217
19218 init_proc.pl1
19219 init_proc: bad syntax in initial procedure name:
19220 STRING for PERSON.PROJ.T
19221
19222
19223 Stream: Logged in SYSERR log.
19224
19225 Time: While system is running.
19226
19227 Meaning: An illegal initial procedure name was specified
19228 for the user. The user may have given an
19229 incorrect -po argument or the project's PDT may
19230 be wrong. No process is created.
19231
19232 Action: No operator action is required.
19233
19234
19235 init_proc.pl1
19236 init_proc: can not call out to initial procedure:
19237 NAME for PERSON.PROJ.T ERROR_MESSAGE
19238
19239
19240 Stream: Logged in SYSERR log.
19241
19242 Time: While system is running.
19243
19244 Meaning: The supervisor could not snap a link to NAME$NAME.
19245 The process overseer may be in invalid form
19246 inaccessible or missing. The user may have given
19247 an incorrect -po argument or the project's PDT
19248 may be incorrect.
19249
19250 Action: No operator action is required.
19251
19252
19253 init_proc.pl1
19254 init_proc: can not get pointer to initial
19255 procedure: PATH for PERSON.PROJ.T ERROR_MESSAGE
19256
19257
19258 Stream: Logged in SYSERR log.
19259
19260 Time: While system is running.
19261
19262 Meaning: The supervisor could not initiate the specified
19263 initial procedure PATH. The process overseer may
19264 be in invalid form inaccessible or missing. The
19265 user may have given an incorrect -po argument or
19266 the project's PDT may be incorrect.
19267
19268
19269
19270 init_proc 333 08/21/20 MR12.7^L
19271
19272
19273 Action: No operator action is required.
19274
19275
19276 init_proc.pl1
19277 init_proc: could not get pointer to pit for
19278 PERSON.PROJ.T ERROR_MESSAGE
19279
19280
19281 Stream: BOS Typewriter sounds beeper
19282
19283 Time: While system is running.
19284
19285 Meaning: The answering service has created the process
19286 directory for a new process incorrectly. The user
19287 cannot be logged in.
19288
19289 Action: Contact the system programming staff.
19290
19291
19292 init_pvt.pl1
19293 init_pvt: Duplicate prph DISK_NAME card.
19294
19295
19296 Stream: BOS Typewriter Crashes system
19297
19298 Time: System Intialization.
19299
19300 Meaning: Two different PRPH cards define DISK_NAME.
19301
19302 Action: Fix the config deck.
19303
19304
19305 init_pvt.pl1
19306 init_pvt: Invalid parm wlim value WLIM. Default
19307 of DEFAULT used.
19308
19309
19310 Stream: BOS Typewriter sounds beeper
19311
19312 Time: System Intialization.
19313
19314 Meaning: An unreasonable value WLIM was found on a PARM
19315 WLIM card. DEFAULT has be substituted.
19316
19317 Action: Fix the config deck.
19318
19319
19320 init_pvt.pl1
19321 init_pvt: Missing model MODEL on PRPH DISK.
19322
19323
19324 Stream: BOS Typewriter Crashes system
19325
19326
19327
19328 init_pvt 334 08/21/20 MR12.7^L
19329
19330
19331 Time: System Intialization.
19332
19333 Meaning: There was no model number specified on the prph
19334 DISK card.
19335
19336 Action: Fix the config deck.
19337
19338
19339 init_pvt.pl1
19340 init_pvt: Missing ndrives field on config card
19341 for DISK subsystem.
19342
19343
19344 Stream: BOS Typewriter Crashes system
19345
19346 Time: System Intialization.
19347
19348 Meaning: The PRPH DSK card for DISK lacks the ndrives
19349 parameter for some model.
19350
19351 Action: Fix the config deck.
19352
19353
19354 init_pvt.pl1
19355 init_pvt: More than N drives defined for XXXX.
19356
19357
19358 Stream: BOS Typewriter Crashes system
19359
19360 Time: System Intialization.
19361
19362 Meaning: The PRPH card for disk subsystem XXXX specified
19363 more than the maximum allowable number of disk
19364 drives.
19365
19366 Action: Follow normal recovery procedures. Correct the
19367 configuration deck and reboot.
19368
19369
19370
19371 init_pvt.pl1
19372 init_pvt: no PRPH DSKn cards
19373
19374
19375 Stream: BOS Typewriter Crashes system
19376
19377 Time: System Intialization.
19378
19379 Meaning: No PRPH cards describing disk subsystems were
19380 found in the CONFIG deck.
19381
19382
19383
19384
19385
19386 init_pvt 335 08/21/20 MR12.7^L
19387
19388
19389 Action: Correct the CONFIG deck to include the correct
19390 PRPH cards to describe the disk subsystems
19391 present and reboot.
19392
19393
19394
19395 init_pvt.pl1
19396 init_pvt: Too many disk subsystems configured.
19397 Limit is NUMBER.
19398
19399
19400 Stream: BOS Typewriter Crashes system
19401
19402 Time: System Intialization.
19403
19404 Meaning: More than NUMBER subsystems are defined. Only
19405 NUMBER are allowed.
19406
19407 Action: Rearrange the config deck for disks and try again.
19408
19409
19410 init_pvt.pl1
19411 init_pvt: Unknown model MODEL on PRPH DISK.
19412
19413
19414 Stream: BOS Typewriter Crashes system
19415
19416 Time: System Intialization.
19417
19418 Meaning: The model number MODEL specified somewhere on the
19419 prph DISK card is not a legal model number.
19420
19421 Action: Fix the config deck.
19422
19423
19424 init_pvt.pl1
19425 init_pvt: XXXX contains a drive number higher
19426 than N.
19427
19428
19429 Stream: BOS Typewriter Crashes system
19430
19431 Time: System Intialization.
19432
19433 Meaning: The PRPH card for disk subsystem XXXX specified
19434 disks with addresses larger than tha maximum
19435 allowable device number N.
19436
19437 Action: Follow normal recovery procedures. Correct the
19438 configuration deck and reboot.
19439
19440
19441
19442
19443
19444 init_root_dir 336 08/21/20 MR12.7^L
19445
19446
19447 init_root_dir.pl1
19448 init_root_dir: Error from makeknown on root
19449 ERROR_MESSAGE
19450
19451
19452 Stream: BOS Typewriter Crashes system
19453
19454 Time: System Intialization.
19455
19456 Meaning: This indicates a logic error in the supervisor or
19457 CPU or memory hardware problems.
19458
19459 Action: Reboot with a different version of the system.
19460
19461
19462 init_root_dir.pl1
19463 init_root_dir: Error on root vtoce ERROR_MESSAGE
19464
19465
19466 Stream: BOS Typewriter Crashes system
19467
19468 Time: System Intialization.
19469
19470 Meaning: The supervisor cannot locate the VTOC entry for
19471 the root directory. The RPV may have been
19472 damaged.
19473
19474 Action: Follow normal recovery procedures. A recovery of
19475 the RPV may be required.
19476
19477
19478
19479 init_root_dir.pl1
19480 init_root_dir: Root damaged.
19481
19482
19483 Stream: BOS Typewriter Crashes system
19484
19485 Time: System Intialization.
19486
19487 Meaning: The unique ID of the root directory in the
19488 directory header is incorrect. The contents of
19489 the RPV may have been damaged.
19490
19491 Action: Follow normal recovery procedures. A recovery of
19492 the RPV may be required.
19493
19494
19495
19496 init_root_vols.pl1
19497 init_root_vols: Adding config conf partition to
19498 rpv.
19499
19500
19501
19502 init_root_vols 337 08/21/20 MR12.7^L
19503
19504
19505 Stream: BOS Typewriter.
19506
19507 Time: System Intialization.
19508
19509 Meaning: No conf partition was found on the rpv. It will
19510 be created by extracting 4 records from the hc
19511 partition.
19512
19513 Action: No operator action is required.
19514
19515
19516 init_root_vols.pl1
19517 init_root_vols: Adding bce file log
19518 partitions to rpv.
19519
19520
19521 Stream: BOS Typewriter.
19522
19523 Time: System Intialization.
19524
19525 Meaning: The rpv does not contain the listed partitions.
19526 The pages of the rpv are being arranged to add
19527 these partitions. This operation takes several
19528 minutes.
19529
19530 Action: No operator action is required.
19531
19532
19533 init_root_vols.pl1
19534 init_root_vols: bce partition is XXX records
19535 must be YYY.
19536
19537
19538 Stream: BOS Typewriter Crashes system
19539
19540 Time: System Intialization.
19541
19542 Meaning: The bce partition defined on the rpv is not
19543 sufficiently large.
19544
19545 Action: Rebuild the rpv to have a large enough bce
19546 partition. Contact the system programming staff.
19547
19548
19549
19550 init_root_vols.pl1
19551 init_root_vols: DISK_VOL appears twice on root
19552 cards.
19553
19554
19555 Stream: BOS Typewriter Crashes system
19556
19557 Time: System Intialization.
19558
19559
19560 init_root_vols 338 08/21/20 MR12.7^L
19561
19562
19563 Meaning: The volume DISK_VOL appears more than once on the
19564 ROOT config cards.
19565
19566 Action: Fix the config deck and try again.
19567
19568
19569 init_root_vols.pl1
19570 init_root_vols: DISK_VOL is not the rpv but
19571 rather is VOLUME.
19572
19573
19574 Stream: BOS Typewriter Crashes system
19575
19576 Time: System Intialization.
19577
19578 Meaning: The label for the RPV is inconsistent.
19579 label.root.here does not agree with other data or
19580 an incorrect pack is mounted on the first drive
19581 specified by the "root" card.
19582
19583 Action: Reload/restore or patch the RPV label back
19584 together or correctly mount the RPV.
19585
19586
19587
19588 init_root_vols.pl1
19589 init_root_vols: Error adding partitions to rpv on
19590 DISK_VOL. ERROR_MESSAGE
19591
19592
19593 Stream: BOS Typewriter Crashes system
19594
19595 Time: System Intialization.
19596
19597 Meaning: It was not possible to add the new partitions to
19598 the rpv. This message will be preceeded by a more
19599 informative message.
19600
19601 Action: Depending on the previous message either a reboot
19602 should be attempted or the rpv will need to be
19603 rebuilt.
19604
19605
19606
19607 init_root_vols.pl1
19608 init_root_vols: Error reading DISK_VOL label.
19609 PROBLEM ERROR_MESSAGE
19610
19611
19612 Stream: BOS Typewriter Crashes system
19613
19614 Time: System Intialization.
19615
19616
19617
19618 init_root_vols 339 08/21/20 MR12.7^L
19619
19620
19621 Meaning: An error has been detected attempting to read the
19622 label of DISK_VOL.
19623
19624 Action: Correct problem and type "go" to retry the read.
19625
19626
19627 init_root_vols.pl1
19628 init_root_vols: Error reading RPV label on
19629 DISK_VOL. PROBLEM ERROR_MESSAGE
19630
19631
19632 Stream: BOS Typewriter Crashes system
19633
19634 Time: System Intialization.
19635
19636 Meaning: An error has been detected attempting to read the
19637 label of the RPV.
19638
19639 Action: Correct problem and type "go" to retry the read.
19640
19641
19642 init_root_vols.pl1
19643 init_root_vols: Error writing rpv label on
19644 DISK_VOL. ERROR_MESSAGE
19645
19646
19647 Stream: BOS Typewriter Crashes system
19648
19649 Time: System Intialization.
19650
19651 Meaning: An i/o prevented updating the rpv label to show
19652 the new partitions.
19653
19654 Action: Correct problem and type "go" to retry the write.
19655
19656
19657 init_root_vols.pl1
19658 init_root_vols: Invalid device on root card
19659 DISK_VOL.
19660
19661
19662 Stream: BOS Typewriter Crashes system
19663
19664 Time: System Intialization.
19665
19666 Meaning: A root card has been found with an invalid
19667 DISK_VOL.
19668
19669 Action: Change the config deck and try again.
19670
19671
19672 init_root_vols.pl1
19673
19674
19675
19676 init_root_vols 340 08/21/20 MR12.7^L
19677
19678
19679 init_root_vols: Maximum of LIMIT RLV vols has
19680 been exceeded.
19681
19682
19683 Stream: BOS Typewriter Crashes system
19684
19685 Time: System Intialization.
19686
19687 Meaning: The "root" card in the config deck specified more
19688 RLV volumes than the system can handle.
19689
19690 Action: Change the config deck and try again.
19691
19692
19693 init_root_vols.pl1
19694 init_root_vols: No part hc on RPV volume
19695 DISK_VOL.
19696
19697
19698 Stream: BOS Typewriter Crashes system
19699
19700 Time: System Intialization.
19701
19702 Meaning: Disk DISK_VOL was specified on a "root" card as
19703 the RPV but does not have a hardcore hc
19704 partition.
19705
19706 Action: The "root" card is incorrect or the wrong pack is
19707 mounted on the first drive described by the "root"
19708 cards.
19709
19710
19711
19712 init_root_vols.pl1
19713 init_root_vols: No room in rpv label for conf
19714 partition.
19715
19716
19717 Stream: BOS Typewriter Crashes system
19718
19719 Time: BOS Typewriter.
19720
19721 Meaning: The partition map for the rpv did not have
19722 sufficient room to add the conf partition.
19723
19724 Action: The rpv will need to be rebuilt. Contact the
19725 system programming staff.
19726
19727
19728
19729 init_root_vols.pl1
19730 init_root_vols: No room in rpv label for
19731 partitions.
19732
19733
19734 init_root_vols 341 08/21/20 MR12.7^L
19735
19736
19737 Stream: BOS Typewriter Crashes system
19738
19739 Time: System Intialization.
19740
19741 Meaning: The rpv label does not have enough room in the
19742 partition map for the new bce file or log
19743 partitions.
19744
19745 Action: The rpv will need to be rebuilt. Contact the
19746 system programming staff.
19747
19748
19749
19750 init_root_vols.pl1
19751 init_root_vols: No root card.
19752
19753
19754 Stream: BOS Typewriter Crashes system
19755
19756 Time: System Intialization.
19757
19758 Meaning: No "root" cards were found in the config deck.
19759 At least one must be present defining the RPV and
19760 other RLV volumes.
19761
19762 Action: Fix the config deck and reboot.
19763
19764
19765 init_root_vols.pl1
19766 init_root_vols: root card specifies nonexistent
19767 drive DISK_VOL.
19768
19769
19770 Stream: BOS Typewriter Crashes system
19771
19772 Time: System Intialization.
19773
19774 Meaning: The volume DISK_VOL specified in the config deck
19775 is not defined by the prph dskX cards.
19776
19777 Action: Fix the config deck and reboot.
19778
19779
19780 init_root_vols.pl1
19781 init_root_vols: RPV not found.
19782
19783
19784 Stream: BOS Typewriter Crashes system
19785
19786 Time: System Intialization.
19787
19788 Meaning: None of the disk volumes specified in the "root"
19789 cards admitted to being the RPV.
19790
19791
19792 init_root_vols 342 08/21/20 MR12.7^L
19793
19794
19795 Action: Check to be sure the drive on which the RPV is
19796 mounted is specified first on the "root" cards.
19797
19798
19799
19800 init_root_vols.pl1
19801 init_root_vols: RPV specified in the
19802 configuration deck DRIVE does not match
19803 sys_boot_info DRIVE.
19804
19805
19806 Stream: BOS Typewriter Crashes system
19807
19808 Time: System Intialization.
19809
19810 Meaning: The RPV defined on the root card is not the same
19811 as the RPV that is currently being used.
19812
19813 Action: Fix the config deck and try again.
19814
19815
19816 init_scavenger_data.pl1
19817 init_scavenger_data: scavenger_data
19818 inconsistency.
19819
19820
19821 Time: System Intialization.
19822
19823 Stream: BOS Typewriter Crashes system
19824
19825 Meaning: An error was encountered initializing the
19826 scavenger's data base.
19827
19828 Action: Contact the system programming staff.
19829
19830
19831 init_scavenger_data.pl1
19832 init_scavenger_data: scavenger_data too small.
19833
19834
19835 Stream: BOS Typewriter Crashes system
19836
19837 Time: System Intialization.
19838
19839 Meaning: The size of the scavenger_data segment is too
19840 small. It can be increased by the TBLS SCAV
19841 config card. It must be at least 68KW with an
19842 additional 67KW for each additional process
19843 beyond 1 which is to be scavenging
19844 simultaneously.
19845
19846 Action: Correct the configuration deck and reboot.
19847
19848
19849
19850 init_scu 343 08/21/20 MR12.7^L
19851
19852
19853
19854
19855 init_scu.pl1
19856 init_scu: Warning - Not all of MEM Y will be
19857 used.
19858
19859
19860 Stream: BOS Typewriter.
19861
19862 Time: System Intialization.
19863
19864 Meaning: The actual amount of memory present in MEM Y does
19865 not agree with the config deck. Only as much as
19866 the configuration deck specifies will be used.
19867
19868 Action: If this is an unintentional error correct the
19869 configuration deck before the next bootload.
19870
19871
19872
19873 init_sst.pl1
19874 init_sst: insufficient storage available for
19875 sst_seg and core map.
19876
19877
19878 Stream: BOS Typewriter Crashes system
19879
19880 Time: System Intialization.
19881
19882 Meaning: Not enough main storage was available to create
19883 the sst_seg during initialization. The system
19884 tape may be bad or the configuration may be too
19885 small or the system parameters specified in the
19886 configuration deck may be incorrect or
19887 inconsistent with the amount of main storage
19888 available.
19889
19890 Action: Follow normal recovery procedures. Check the
19891 configuration and the CONFIG deck $boot_tape
19892
19893
19894
19895 init_sst.pl1
19896 init_sst: No SST card in config deck. One has
19897 been added: SST N N N N
19898
19899
19900 Stream: BOS Typewriter sounds beeper
19901
19902 Time: System Intialization.
19903
19904 Meaning: No SST card was found in the config deck. ASTE
19905 pool sizes of N N N N have been set as defaults.
19906
19907
19908 init_sst 344 08/21/20 MR12.7^L
19909
19910
19911
19912
19913 init_stack_0.pl1
19914 init_stack_0: Error creating >sl1>XXXXXX from
19915 YYYYY. Retrying.
19916
19917
19918 Stream: BOS Typewriter.
19919
19920 Time: System Intialization.
19921
19922 Meaning: An error was encountered in creating the stack_0
19923 segment XXXXXX. The error was returned by module
19924 YYYYYY and is described in detail in the
19925 following message. init_stack_0 will attempt to
19926 correct the problem by renaming the segment XXXXXX
19927 to stack_0.<unique name> deleting it and
19928 retrying the creation of segment XXXXXX once.
19929
19930 Action: No action is required if the above actions correct
19931 the problem. If the message persists it may be
19932 symptomatic of hardware or software problems and
19933 it should be brought to the attention of the
19934 System Programming Staff.
19935
19936
19937
19938 init_stack_0.pl1
19939 init_stack_0: Error creating >sl1>XXXXXX from
19940 YYYYYY. Stack skipped.
19941
19942
19943 Stream: BOS Typewriter.
19944
19945 Time: System Intialization.
19946
19947 Meaning: An error was encountered in creating the stack_0
19948 segment XXXXXX. The error was returned by module
19949 YYYYYY and is described in detail in the
19950 following message. This error could not be
19951 corrected by renaming the segment XXXXXX to
19952 stack_0.<unique name> deleting it and retrying
19953 the creation of segment XXXXXX once. The stack_0
19954 represented by segment XXXXXX is skipped and
19955 there will be one fewer stack_0 than specified by
19956 the max_max_eligible tuning parameter for each
19957 message of this sort.
19958
19959 Action: This message may be symptomatic of hardware or
19960 software problems. It should be brought to the
19961 attention of the System Programming Staff.
19962
19963
19964
19965
19966 init_sys_var 345 08/21/20 MR12.7^L
19967
19968
19969
19970
19971 init_sys_var.pl1
19972 init_sys_var: max_hproc_segno < hcscnt of XXX
19973
19974
19975 Stream: BOS Typewriter Crashes system
19976
19977 Time: System Intialization.
19978
19979 Meaning: The upper bound of the descriptor segment for
19980 hardcore processes is too small. This indicates a
19981 logic error in the supervisor or CPU or memory
19982 hardware problems.
19983
19984 Action: Follow normal recovery procedures. $boot_tape
19985
19986
19987
19988 init_syserr_log.pl1
19989 init_syserr_log: Cannot create logger process.
19990 ERROR-MESSAGE
19991
19992
19993 Stream: BOS Typewriter.
19994
19995 Time: System Intialization.
19996
19997 Meaning: This indicates a logic error in the supervisor or
19998 CPU or memory hardware problems. No syserr
19999 messages will be logged during this bootload.
20000
20001 Action: Follow normal recovery procedures.
20002
20003
20004 init_syserr_log.pl1
20005 init_syserr_log: Cannot get last message info
20006 from paged syserr log PTR. ERROR-MESSAGE
20007
20008
20009 Stream: BOS Typewriter.
20010
20011 Time: System Intialization.
20012
20013 Meaning: This indicates a logic error in the supervisor or
20014 CPU or memory hardware problems.
20015
20016 Action: Follow normal recovery procedures. It may be
20017 necessary to reinitialize the LOG partition with
20018 the BCE test_disk command after this error.
20019
20020
20021
20022
20023
20024 init_syserr_log 346 08/21/20 MR12.7^L
20025
20026
20027 init_syserr_log.pl1
20028 init_syserr_log: Cannot get service bit from
20029 paged syserr log PTR. MESSAGE
20030
20031
20032 Stream: BOS Typewriter.
20033
20034 Time: System Intialization.
20035
20036 Meaning: This indicates a logic error in the supervisor or
20037 CPU or memory hardware problems. Some error
20038 occurred when attempting to check the in service
20039 bit for the specified ring 0 paged log segment.
20040
20041 Action: No operator action is required. The log partition
20042 will be automatically reinitialized.
20043
20044
20045
20046 init_syserr_log.pl1
20047 init_syserr_log: Cannot initialize paged syserr
20048 log PTR.
20049
20050
20051 Stream: BOS Typewriter Crashes system
20052
20053 Time: System Intialization.
20054
20055 Meaning: This indicates a logic error in the supervisor or
20056 CPU or memory hardware problems.
20057
20058 Action: Follow normal recovery procedures.
20059
20060
20061 init_syserr_log.pl1
20062 init_syserr_log: Cannot write initial message to
20063 paged syserr log PTR. ERROR-MESSAGE
20064
20065
20066 Stream: BOS Typewriter Crashes system
20067
20068 Time: System Intialization.
20069
20070 Meaning: This indicates a logic error in the supervisor or
20071 CPU or memory hardware problems.
20072
20073 Action: Follow normal recovery procedures. It may be
20074 necessary to reinitialize the LOG partition with
20075 the BCE test_disk command after this error.
20076
20077
20078
20079 init_syserr_log.pl1
20080
20081
20082 init_syserr_log 347 08/21/20 MR12.7^L
20083
20084
20085 init_syserr_log: Converting MR10.2 syserr
20086 partition.
20087
20088
20089 Stream: BOS Typewriter.
20090
20091 Time: System Intialization.
20092
20093 Meaning: This message occurs during the first bootload with
20094 an MR11.0 system tape and indicates that the LOG
20095 partition is now in the new format.
20096
20097 Action: No operator action is required.
20098
20099
20100 init_syserr_log.pl1
20101 init_syserr_log: LOG partition damaged.
20102 Reinitializing.
20103
20104
20105 Stream: BOS Typewriter sounds beeper
20106
20107 Time: System Intialization.
20108
20109 Meaning: The LOG partition has been damaged. Some messages
20110 may be lost if the previous shutdown was caused by
20111 a crash. The partition is automatically
20112 reinitialized.
20113
20114 Action: Follow normal recovery procedures.
20115
20116
20117 init_syserr_log.pl1
20118 init_syserr_log: No LOG partition found syserr
20119 logging disabled.
20120
20121
20122 Stream: BOS Typewriter Crashes system
20123
20124 Time: System Intialization.
20125
20126 Meaning: The system requires a LOG partition on the RPV
20127 disk to hold syserr messages before they are
20128 copied into >sc1>syserr_log. This partition must
20129 exist on the volume and be defined by a "PART
20130 LOG" card in the config deck.
20131
20132 Action: Create a LOG partition on the RPV and define it in
20133 the config deck then re-boot. The LOG partition
20134 should be at least 200 records long and may be as
20135 large as 513.
20136
20137
20138
20139
20140 init_syserr_log 348 08/21/20 MR12.7^L
20141
20142
20143
20144
20145 init_syserr_log.pl1
20146 init_syserr_log: Service bit off for live paged
20147 syserr log PTR.
20148
20149
20150 Stream: BOS Typewriter.
20151
20152 Time: System Intialization.
20153
20154 Meaning: The in service flag for the specified ring 0 paged
20155 log segment was found off. Being this is supposed
20156 to be the live log an error is indicated. This
20157 may occur when booting after a system crash.
20158
20159 Action: No operator action is required. The syserr log
20160 partition will be automatically reinitialized.
20161
20162
20163
20164 init_syserr_log.pl1
20165 init_syserr_log: Size of PTR larger on disk than
20166 in header.
20167
20168
20169 Stream: BOS Typewriter Crashes system
20170
20171 Time: System Intialization.
20172
20173 Meaning: The LOG partition has been damaged. Some messages
20174 may be lost if the previous shutdown was caused by
20175 a crash.
20176
20177 Action: Reinitialize the LOG partition with the BCE
20178 test_disk command and re-boot.
20179
20180
20181 init_syserr_log.pl1
20182 init_syserr_log: Size of wired log is
20183 inconsistent.
20184
20185
20186 Stream: BOS Typewriter Crashes system
20187
20188 Time: System Intialization.
20189
20190 Meaning: The definitions in syserr_data.cds are
20191 inconsistent with those in syserr_data.incl.pl1.
20192 This indicates a programming error.
20193
20194 Action: Follow normal recovery procedures.
20195
20196
20197
20198 init_syserr_log 349 08/21/20 MR12.7^L
20199
20200
20201
20202
20203 init_syserr_log.pl1
20204 init_syserr_log: Unable to retrieve IPC operands
20205 from APTE. Syserr log copying disabled.
20206
20207
20208 Stream: BOS Typewriter.
20209
20210 Time: System Intialization.
20211
20212 Meaning: This indicates a logic error in the supervisor or
20213 CPU or memory hardware problems. No syserr
20214 messages will be logged during this bootload.
20215
20216 Action: Follow normal recovery procedures.
20217
20218
20219 init_toehold.pl1
20220 init_toehold: No "bce" partition on rpv. Rebuild
20221 the RPV to add one.
20222
20223
20224 Stream: BOS Typewriter Crashes system
20225
20226 Time: System Intialization.
20227
20228 Meaning: The partition used to hold the bootload command
20229 environment is missing from the rpv.
20230
20231 Action: A rebuild of the rpv is necessary.
20232
20233
20234 init_toehold.pl1
20235 init_toehold: Unable to save bootload Multics
20236 image to disk.
20237
20238
20239 Stream: BOS Typewriter Crashes system
20240
20241 Time: System Intialization.
20242
20243 Meaning: An i/o error prevented the establishment of the
20244 bce crash handler.
20245
20246
20247 init_toehold.pl1
20248 init_toehold: Unable to save safe_config_deck to
20249 disk.
20250
20251
20252 Stream: BOS Typewriter sounds beeper
20253
20254
20255
20256 init_toehold 350 08/21/20 MR12.7^L
20257
20258
20259 Time: System Intialization.
20260
20261 Meaning: The safe_config_deck used to re-establish bce
20262 when a failure of bce itself occurs could not be
20263 updated to disk. A future failure of bce may be
20264 catastrophic.
20265
20266 Action: Try performing a reinitialize operation making
20267 sure that the config deck is perfect.
20268
20269
20270
20271 init_volmap_seg.pl1
20272 init_volmap_seg: Records left on dskX_NNPVNAME
20273 changed from X to Y.
20274
20275
20276 Stream: Logged in SYSERR log.
20277
20278 Time: During system initialization as physical volumes
20279 of the Root Logical Volume RLV are accepted
20280 during system start_up as physical volumes which
20281 were mounted at the last shutdown are accepted or
20282 when a physical volume is mounted and accepted.
20283
20284 Meaning: A VTOC header was encountered which did not agree
20285 with the Volume Map. This will occur when a
20286 volume which was not shut down properly is
20287 mounted.
20288
20289 Action: Contact the system programming staff.
20290
20291
20292 init_volmap_seg.pl1
20293 init_volmap_seg: Unable to get NK ASTE for
20294 volmap_seg.
20295
20296
20297 Stream: BOS Typewriter Crashes system
20298
20299 Time: During system initialization as physical volumes
20300 of the Root Logical Volume RLV are accepted
20301 during system start_up as physical volumes which
20302 were mounted at the last shutdown are accepted or
20303 when a physical volume is mounted and accepted.
20304
20305 Meaning: An NK ASTE was not available for accessing the
20306 Volume Map. The most likely cause is an ASTE pool
20307 size which is too small.
20308
20309 Action: Follow normal recovery procedures. Increase the
20310 number of ASTEs in the appropriate pool by means
20311 of the SST configuration card.
20312
20313
20314 init_volmap_seg 351 08/21/20 MR12.7^L
20315
20316
20317
20318
20319 init_volmap_seg.pl1
20320 init_volmap_seg: Unable to get NK ASTE for VTOC
20321 header.
20322
20323
20324 Stream: BOS Typewriter Crashes system
20325
20326 Time: During system initialization as physical volumes
20327 of the Root Logical Volume RLV are accepted
20328 during system start_up as physical volumes which
20329 were mounted at the last shutdown are accepted or
20330 when a physical volume is mounted and accepted.
20331
20332 Meaning: An NK ASTE was not available for accessing the
20333 VTOC header. The most likely cause is an ASTE
20334 pool size which is too small.
20335
20336 Action: Follow normal recovery procedures. Increase the
20337 number of ASTEs in the appropriate pool by means
20338 of the SST configuration card.
20339
20340
20341
20342 init_volmap_seg.pl1
20343 init_volmap_seg: Unable to initialize dumper map
20344 for dskX_NNPVNAME
20345
20346
20347 Stream: BOS Typewriter.
20348
20349 Time: During system initialization as physical volumes
20350 of the Root Logical Volume RLV are accepted
20351 during system start_up as physical volumes which
20352 were mounted at the last shutdown are accepted or
20353 when a physical volume is mounted and accepted.
20354
20355 Meaning: An unexpected error was encountered in
20356 initializing the backup queue bit map for the
20357 Physical Volume Dumper. The volume on which the
20358 error occurred cannot be backed up with the
20359 Physical Volume Dumper.
20360
20361 Action: Contact the system programming staff.
20362
20363
20364 init_volmap_seg.pl1
20365 init_volmap_seg: VTOCEs left on dskX_NNPVNAME
20366 changed from X to Y.
20367
20368
20369 Stream: Logged in SYSERR log.
20370
20371
20372 init_volmap_seg 352 08/21/20 MR12.7^L
20373
20374
20375 Time: During system initialization as physical volumes
20376 of the Root Logical Volume RLV are accepted
20377 during system start_up as physical volumes which
20378 were mounted at the last shutdown are accepted or
20379 when a physical volume is mounted and accepted.
20380
20381 Meaning: A VTOC header was encountered which did not agree
20382 with the VTOC Map. This will occur when a volume
20383 which was not shut down properly is mounted.
20384
20385 Action: Contact the system programming staff.
20386
20387
20388 init_volmap_seg.pl1
20389 init_volmap_seg: YYYY volume inconsistencies on
20390 dskX_NNPVNAME. UUUU records left. VVVV VTOCEs
20391 left.
20392
20393
20394 Stream: Logged only if the number of free records and the
20395 number of free VTOCEs are both above thresholds.
20396 Logged and printed on the console if either is
20397 below threshold.
20398
20399 Time: During system initialization as physical volumes
20400 of the Root Logical Volume RLV are accepted
20401 during system start_up as physical volumes which
20402 were mounted at the last shutdown are accepted or
20403 when a physical volume is mounted and accepted.
20404
20405 Meaning: The volume was not shut down properly or
20406 inconsistencies were detected while the volume was
20407 mounted. The effect of these inconsistencies is
20408 that free records and free VTOCEs are lost to the
20409 system. Lost records and VTOCEs can be recovered
20410 by a volume salvage.
20411
20412 Action: Contact the system programming staff.
20413
20414
20415 init_vtoc_man.pl1
20416 init_vtoc_man: Unexpected error from absadr.
20417 Code XX.
20418
20419
20420 Stream: BOS Typewriter Crashes system
20421
20422 Time: System Intialization.
20423
20424 Meaning: The absolute address of vtoc_buffer_seg could not
20425 be determined. This indicates hardware or
20426 software malfunction.
20427
20428
20429
20430 init_vtoc_man 353 08/21/20 MR12.7^L
20431
20432
20433 Action: Follow normal recovery procedures.
20434
20435
20436 real_initializer.pl1.pmac
20437 initializer: Bad root volume.
20438
20439
20440 Stream: BOS Typewriter Crashes system
20441
20442 Time: System Intialization.
20443
20444 Meaning: A volume specified on a ROOT card was found ill
20445 formatted by init_root_vols.
20446
20447 Action: Follow normal recovery procedures.
20448
20449
20450 real_initializer.pl1.pmac
20451 initializer: Bad root volume.
20452
20453
20454 Stream: BOS Typewriter Crashes system
20455
20456 Time: System Intialization.
20457
20458 Meaning: A volume specified on a ROOT card was found ill
20459 formatted by init_root_vols.
20460
20461 Action: Follow normal recovery procedures.
20462
20463
20464 real_initializer.pl1.pmac
20465 initializer: bad_dir_ signal raised
20466
20467
20468 Stream: BOS Typewriter Crashes system
20469
20470 Time: System Intialization.
20471
20472 Meaning: During system bootload directory control has
20473 encountered an invalid directory. This usually
20474 occurs due to damage to the root or to
20475 >system_control_1. The RPV is automatically
20476 scheduled for volume salvage.
20477
20478 Action: Follow normal recovery procedures.
20479
20480
20481 real_initializer.pl1.pmac
20482 initializer: bad_dir_ signal raised
20483
20484
20485 Stream: BOS Typewriter Crashes system
20486
20487
20488 initializer 354 08/21/20 MR12.7^L
20489
20490
20491 Time: System Intialization.
20492
20493 Meaning: During system bootload directory control has
20494 encountered an invalid directory. This usually
20495 occurs due to damage to the root or to
20496 >system_control_1. The RPV is automatically
20497 scheduled for volume salvage.
20498
20499 Action: Follow normal recovery procedures.
20500
20501
20502 real_initializer.pl1.pmac
20503 initializer: ENTRY_TO_CALL check_stop.
20504
20505
20506 Stream: BOS Typewriter sounds beeper
20507
20508 Time: System Intialization.
20509
20510 Meaning: The initializer has detected that the first nine
20511 data switches on the CPU contain an octal "123"
20512 and the STOP number of the entry to be called and
20513 the current collection_1_phase match the other CPU
20514 data switches. The initializer calls BCE after
20515 displaying this message but before actually
20516 calling the entry. The CPU data switches have the
20517 following usage:
20518
20519 0 - 8: must be set to an octal "123" for any
20520 other switches to be valid.
20521 9 - 14: area for the BCD value of the
20522 collection_1_phase to stop in.
20523 15 - 20: area for the BCD hundreds digit of the
20524 STOP number.
20525 21 - 26: area for the BCD tens digit of the STOP
20526 number.
20527 27 - 32: area for the BCD ones digit of the STOP
20528 number.
20529 33 - 35: not used or checked.
20530
20531 Action: Execute any BCE functions desired. Modify the
20532 setting of the CPU data switches as required.
20533 Execute the BCE "go" function to resume
20534 initialization.
20535
20536
20537
20538 real_initializer.pl1.pmac
20539 initializer: ENTRY_TO_CALL check_stop.
20540
20541
20542 Stream: BOS Typewriter sounds beeper
20543
20544
20545
20546 initializer 355 08/21/20 MR12.7^L
20547
20548
20549 Time: System Intialization.
20550
20551 Meaning: The initializer has detected that the first nine
20552 data switches on the CPU contain an octal "123"
20553 and the STOP number of the entry to be called and
20554 the current collection_1_phase match the other CPU
20555 data switches. The initializer calls BCE after
20556 displaying this message but before actually
20557 calling the entry. The CPU data switches have the
20558 following usage:
20559
20560 0 - 8: must be set to an octal "123" for any
20561 other switches to be valid.
20562 9 - 14: area for the BCD value of the
20563 collection_1_phase to stop in.
20564 15 - 20: area for the BCD hundreds digit of the
20565 STOP number.
20566 21 - 26: area for the BCD tens digit of the STOP
20567 number.
20568 27 - 32: area for the BCD ones digit of the STOP
20569 number.
20570 33 - 35: not used or checked.
20571
20572 Action: Execute any BCE functions desired. Modify the
20573 setting of the CPU data switches as required.
20574 Execute the BCE "go" function to resume
20575 initialization.
20576
20577
20578
20579 real_initializer.pl1.pmac
20580 initializer: intk card missing.
20581
20582
20583 Stream: BOS Typewriter Crashes system
20584
20585 Time: System Intialization.
20586
20587 Meaning: No "intk" card was found in the config deck.
20588
20589 Action: $config
20590
20591
20592 real_initializer.pl1.pmac
20593 initializer: intk card missing.
20594
20595
20596 Stream: BOS Typewriter Crashes system
20597
20598 Time: System Intialization.
20599
20600 Meaning: No "intk" card was found in the config deck.
20601
20602
20603
20604 initializer 356 08/21/20 MR12.7^L
20605
20606
20607 Action: $config
20608
20609
20610 real_initializer.pl1.pmac
20611 initializer: Multics SYSID VERSION syserr
20612 logging initialized.
20613
20614
20615 Stream: Logged in SYSERR log.
20616
20617 Time: System Intialization.
20618
20619 Meaning: This is the first syserr message produced by every
20620 bootload. It is produced as soon as the syserr
20621 logging mechanism is made operative which insures
20622 that it is the first message logged for every
20623 bootload. It identifies the system ID and version
20624 of the running system.
20625
20626 Action: No operator action is required.
20627
20628
20629 real_initializer.pl1.pmac
20630 initializer: Multics SYSID VERSION syserr
20631 logging initialized.
20632
20633
20634 Stream: Logged in SYSERR log.
20635
20636 Time: System Intialization.
20637
20638 Meaning: This is the first syserr message produced by every
20639 bootload. It is produced as soon as the syserr
20640 logging mechanism is made operative which insures
20641 that it is the first message logged for every
20642 bootload. It identifies the system ID and version
20643 of the running system.
20644
20645 Action: No operator action is required.
20646
20647
20648 real_initializer.pl1.pmac
20649 initializer: Segment fault error by PPPP
20650 referencing PPPP: ERROR
20651
20652
20653 Stream: BOS Typewriter Crashes system
20654
20655 Time: System Intialization.
20656
20657 Meaning: During system bootload a segment fault error has
20658 occurred. This usually indicates running out of
20659 room on the RLV. A BOOT RPVS may recover some of
20660
20661
20662 initializer 357 08/21/20 MR12.7^L
20663
20664
20665 this space. The procedure causing the error and
20666 the segment being referenced are identified along
20667 with the error message.
20668
20669 Action: Follow normal recovery procedures.
20670
20671
20672 real_initializer.pl1.pmac
20673 initializer: Segment fault error by PPPP
20674 referencing PPPP: ERROR
20675
20676
20677 Stream: BOS Typewriter Crashes system
20678
20679 Time: System Intialization.
20680
20681 Meaning: During system bootload a segment fault error has
20682 occurred. This usually indicates running out of
20683 room on the RLV. A BOOT RPVS may recover some of
20684 this space. The procedure causing the error and
20685 the segment being referenced are identified along
20686 with the error message.
20687
20688 Action: Follow normal recovery procedures.
20689
20690
20691 real_initializer.pl1.pmac
20692 initializer: STOP_NUM ENTRY_TO_CALL state ISTATE
20693 phase CPHASE.
20694
20695
20696 Stream: BOS Typewriter sounds beeper
20697
20698 Time: System Intialization.
20699
20700 Meaning: The "loud" config parm is currently enabled. This
20701 message gives the current stop number STOP_NUM
20702 that can be used to stop the initialization
20703 process and return to BCE before calling
20704 ENTRY_TO_CALL. The current values of
20705 sys_infoSystem Intialization.ialization_state
20706 ISTATE and sys_info$collection_1_phase CPHASE
20707 are also given.
20708
20709 Action: No operator action is required.
20710
20711
20712 real_initializer.pl1.pmac
20713 initializer: STOP_NUM ENTRY_TO_CALL state ISTATE
20714 phase CPHASE.
20715
20716
20717 Stream: BOS Typewriter sounds beeper
20718
20719
20720 initializer 358 08/21/20 MR12.7^L
20721
20722
20723 Time: System Intialization.
20724
20725 Meaning: The "loud" config parm is currently enabled. This
20726 message gives the current stop number STOP_NUM
20727 that can be used to stop the initialization
20728 process and return to BCE before calling
20729 ENTRY_TO_CALL. The current values of
20730 sys_infoSystem Intialization.ialization_state
20731 ISTATE and sys_info$collection_1_phase CPHASE
20732 are also given.
20733
20734 Action: No operator action is required.
20735
20736
20737 dn355_boot_interrupt.pl1
20738 Invalid bootload interrupt for FNP X status N
20739
20740
20741 Stream: BOS Typewriter.
20742
20743 Time: When bootloading an FNP
20744
20745 Meaning: The FNP responded to the bootload attempt with an
20746 interrupt but the high-order bit of the reported
20747 status was not on. N is the reported status in
20748 octal.
20749
20750 Action: Contact the system programming staff.
20751
20752
20753 io_config_init.pl1
20754 io_config_init: Invalid iom or channel number on
20755 prph NAME card.
20756
20757
20758 Stream: BOS Typewriter Crashes system
20759
20760 Time: System Intialization.
20761
20762 Meaning: The iom number or the channel number is invalid on
20763 the prph card that defines NAME.
20764
20765 Action: Fix the config deck.
20766
20767
20768 io_error.pl1
20769 io_error: Illegal address value in call to
20770 io_manager.
20771
20772
20773 Stream: BOS Typewriter Crashes system
20774
20775 Time: While system is running.
20776
20777
20778 io_error 359 08/21/20 MR12.7^L
20779
20780
20781 Meaning: An address that was not in the required part of
20782 memory or was not aligned properly was passed in a
20783 call to io_manager. This indicates a logic error
20784 in the supervisor or CPU or memory hardware
20785 problems.
20786
20787 Action: Follow normal recovery procedures. Contact the
20788 system programming staff.
20789
20790
20791
20792 io_error.pl1
20793 io_error: Invalid channel index in call to
20794 io_manager.
20795
20796
20797 Stream: BOS Typewriter Crashes system
20798
20799 Time: While system is running.
20800
20801 Meaning: A channel index which did not correspond to an
20802 assigned logical channel was passed to io_manager.
20803 This indicates a logic error in the supervisor or
20804 CPU or memory hardware problems.
20805
20806 Action: Follow normal recovery procedures. Contact the
20807 system programming staff.
20808
20809
20810
20811 ioam_.pl1
20812 ioam_: The IOAT is too small use TBLS config
20813 card to increase size.
20814
20815
20816 Stream: BOS Typewriter sounds beeper
20817
20818 Time: System Intialization.
20819
20820 Meaning: The system was unable to make an entry in the IO
20821 Assignment Table. One or more devices may be
20822 unattachable.
20823
20824 Action: Contact the system programming staff. Correct the
20825 configuration deck before the next bootload.
20826
20827
20828
20829 ioi_init.pl1
20830 ioi_init: Duplicate "prph NAME" card found.
20831
20832
20833 Stream: BOS Typewriter Crashes system
20834
20835
20836 ioi_init 360 08/21/20 MR12.7^L
20837
20838
20839 Time: System Intialization.
20840
20841 Meaning: $msg
20842
20843 Action: $config
20844
20845
20846 ioi_init.pl1
20847 ioi_init: ERROR_CODE Unable to assign channel
20848 CHANID.
20849
20850
20851 Stream: BOS Typewriter Crashes system
20852
20853 Time: System Intialization.
20854
20855 Meaning: A logical channel could not be assigned to IOI.
20856 This indicates a logic error in the supervisor or
20857 CPU or memory hardware problems.
20858
20859 Action: Contact the system programming staff.
20860
20861
20862 ioi_init.pl1
20863 ioi_init: ERROR_CODE Unable to get the name of
20864 name of iom IOMNO channel CHANNO.
20865
20866
20867 Stream: BOS Typewriter Crashes system
20868
20869 Time: System Intialization.
20870
20871 Meaning: An attempt to generate the name of logical channel
20872 CHANNO of iom IOMNO failed.
20873
20874 Action: $config
20875
20876
20877 ioi_init.pl1
20878 ioi_init: Multiple definitions of channel CHANID
20879 found for subsystem NAME.
20880
20881
20882 Stream: BOS Typewriter Crashes system
20883
20884 Time: System Intialization.
20885
20886 Meaning: $msg
20887
20888 Action: $config
20889
20890
20891 ioi_init.pl1
20892
20893
20894 ioi_init 361 08/21/20 MR12.7^L
20895
20896
20897 ioi_init: Multiple definitions of device NAME
20898 found.
20899
20900
20901 Stream: BOS Typewriter Crashes system
20902
20903 Time: System Intialization.
20904
20905 Meaning: $msg
20906
20907 Action: $config
20908
20909
20910 ioi_init.pl1
20911 ioi_init: No cte found for channel CHANID.
20912
20913
20914 Stream: BOS Typewriter Crashes system
20915
20916 Time: System Intialization.
20917
20918 Meaning: This indicates a logic error in the supervisor or
20919 CPU or memory hardware problems.
20920
20921 Action: Contact the system programming staff.
20922
20923
20924 ioi_init.pl1
20925 ioi_init: No entry for NAME found in disk_data.
20926
20927
20928 Stream: BOS Typewriter Crashes system
20929
20930 Time: System Intialization.
20931
20932 Meaning: This indicates a logic error in the supervisor or
20933 CPU or memory hardware problems.
20934
20935 Action: Contact the system programming staff.
20936
20937
20938 ioi_init.pl1
20939 ioi_init: No matching "prph NAME" found for "chnl
20940 NAME".
20941
20942
20943 Stream: BOS Typewriter Crashes system
20944
20945 Time: System Intialization.
20946
20947 Meaning: $msg
20948
20949 Action: $config
20950
20951
20952 ioi_masked$interrupt 362 08/21/20 MR12.7^L
20953
20954
20955
20956
20957 ioi_masked.pl1
20958 ioi_masked$interrupt: absadr failed.
20959
20960
20961 Stream: BOS Typewriter Crashes system
20962
20963 Time: While system is running.
20964
20965 Meaning: A call to the absadr function returned a non-zero
20966 error code indicating that the absolute address
20967 of the workspace could not be obtained. Since the
20968 workspace is wired this error should never have
20969 occurred.
20970
20971 Action: Contact the system programming staff. Follow
20972 normal recovery procedures.
20973
20974
20975
20976 ioi_masked.pl1
20977 ioi_masked$interrupt: I/O error.
20978
20979
20980 Stream: Logged in SYSERR log.
20981
20982 Time: While system is running.
20983
20984 Meaning: An error or accumulation of like errors has
20985 occured. All needed information is contained in
20986 the binary portion of the entry.
20987
20988 Action: No operator action is required.
20989
20990
20991 ioi_masked.pl1
20992 ioi_masked$interrupt: Interrupt for inactive
20993 device device DEVID. Type go to continue.
20994
20995
20996
20997 Stream: BOS Typewriter Crashes system
20998
20999 Time: While system is running.
21000
21001 Meaning: An interrupt has been received over a channel for
21002 which the device is not marked "active". This
21003 could indicate an error in the I/O hardware or in
21004 the setting/checking of the device active flag.
21005
21006
21007
21008
21009
21010 ioi_masked$interrupt 363 08/21/20 MR12.7^L
21011
21012
21013 Action: Typing "go" at BCE will cause Multics to be
21014 reentered and ioi_masked to dismiss this error and
21015 properly cleanup.
21016
21017
21018
21019 ioi_masked.pl1
21020 ioi_masked$interrupt: Special.
21021
21022
21023 Stream: Logged in SYSERR log.
21024
21025 Time: While system is running.
21026
21027 Meaning: A special interrupt or accumulation of special
21028 interrupts has occured. All needed information
21029 is contained in the binary portion of the entry.
21030
21031 Action: No operator action is required.
21032
21033
21034 ioi_masked.pl1
21035 ioi_masked$timer: Attempt to unwire NULL
21036 workspace. device DEVID.
21037
21038
21039 Stream: BOS Typewriter.
21040
21041 Time: While system is running.
21042
21043 Meaning: Device entry flag and time stamp indicated that
21044 its workspace required unwiring. However the
21045 pointer to the ASTE for the workspace was null.
21046 This indicates a logic error in the supervisor or
21047 CPU or memory hardware problems.
21048
21049 Action: Contact the system programming staff. Follow
21050 normal recovery procedures.
21051
21052
21053
21054 ioi_masked.pl1
21055 ioi_masked$timer: Timeout on channel CHANID
21056 device DEVID.
21057
21058
21059 Stream: BOS Typewriter.
21060
21061 Time: While system is running.
21062
21063 Meaning: The time limit has expired waiting for status from
21064 CHANID for a previous connect. The channel will
21065 be masked "OFF" then unmasked if multiple devices
21066
21067
21068 ioi_masked$timer 364 08/21/20 MR12.7^L
21069
21070
21071 exist i.e. tapes and disks so that special
21072 interrupts can be received.
21073
21074 Action: Contact your Customer Service Account
21075 Representative if the errors persist.
21076
21077
21078
21079 ioi_masked.pl1
21080 ioi_masked$timer: Timeout on channel CHANID no
21081 device.
21082
21083
21084 Stream: BOS Typewriter.
21085
21086 Time: While system is running.
21087
21088 Meaning: The time limit has expired waiting for status from
21089 CHANID for the connect to unmask the channel. The
21090 channel will be masked "OFF" then then unmask
21091 will be tried again.
21092
21093 Action: Contact your Customer Service Account
21094 Representative if the errors persist.
21095
21096
21097
21098 ioi_masked.pl1
21099 ioi_masked: Channel CHANID not responding will
21100 remain masked.
21101
21102
21103 Stream: BOS Typewriter.
21104
21105 Time: While system is running.
21106
21107 Meaning: The time limit has expired waiting for status from
21108 a previous unmask connect reset-status idcw. It
21109 is apparent that the channel is inoperative. No
21110 further attempt will be made to re-open the
21111 channel.
21112
21113 Action: Contact your Customer Service Account
21114 Representative if the errors persist.
21115
21116
21117
21118 ioi_masked.pl1
21119 ioi_masked: Lock for subsystem SUBSYSTEM not
21120 locked to process OOOOOO.
21121
21122
21123 Stream: BOS Typewriter Crashes system
21124
21125
21126 ioi_masked 365 08/21/20 MR12.7^L
21127
21128
21129 Time: While system is running.
21130
21131 Meaning: An unlock of the subsystem lock was attempted but
21132 is was not locked by this process. This indicates
21133 a logic error in the supervisor or CPU or memory
21134 hardware problems.
21135
21136 Action: Contact the system programming staff. Follow
21137 normal recovery procedures.
21138
21139
21140
21141 ioi_masked.pl1
21142 ioi_masked: Mylock error on subsystem SUBSYSTEM.
21143
21144
21145 Stream: BOS Typewriter Crashes system
21146
21147 Time: While system is running.
21148
21149 Meaning: An lock of the subsystem lock was attempted but
21150 is was already locked by this process. This
21151 indicates a logic error in the supervisor or CPU
21152 or memory hardware problems.
21153
21154 Action: Contact the system programming staff. Follow
21155 normal recovery procedures.
21156
21157
21158
21159 ioi_masked.pl1
21160 ioi_masked: No Ext. Stat. with MAJOR/SUB status
21161 on chnl CHANID DEVID.
21162
21163
21164 Stream: Logged in SYSERR log.
21165
21166 Time: While system is running.
21167
21168 Meaning: An error status has occured that requires detailed
21169 status. This CHANID should have supplied this
21170 with the status but did not. This CHANID is also
21171 not capable of requesting the detailed status. An
21172 octal dump of the status_entry area will be
21173 displayed along with the error message.
21174
21175 Action: No operator action is required.
21176
21177
21178 ioi_verify_lock.pl1
21179 ioi_verify_lock: Force unlocked device entry lock
21180 #N for USERID.
21181
21182
21183
21184 ioi_verify_lock 366 08/21/20 MR12.7^L
21185
21186
21187 Stream: BOS Typewriter.
21188
21189 Time: While system is running.
21190
21191 Meaning: This indicates a logic error in the supervisor or
21192 CPU or memory hardware problems. The process
21193 encountered a condition in ring-0 which forced a
21194 crawlout. IOI unlocks all locks for the process.
21195
21196 Action: Contact the system programming staff.
21197
21198
21199 ioi_verify_lock.pl1
21200 ioi_verify_lock: Force unlocked group entry lock
21201 for USERID.
21202
21203
21204 Stream: BOS Typewriter.
21205
21206 Time: While system is running.
21207
21208 Meaning: This indicates a logic error in the supervisor or
21209 CPU or memory hardware problems. The process
21210 encountered a condition in ring-0 which forced a
21211 crawlout. IOI unlocks all locks for the process.
21212
21213 Action: Contact the system programming staff.
21214
21215
21216 ioi_verify_lock.pl1
21217 ioi_verify_lock: Force unlocked reconfigure lock
21218 for USERID.
21219
21220
21221 Stream: BOS Typewriter.
21222
21223 Time: While system is running.
21224
21225 Meaning: This indicates a logic error in the supervisor or
21226 CPU or memory hardware problems. The process
21227 encountered a condition in ring-0 which forced a
21228 crawlout. IOI unlocks all locks for the process.
21229
21230 Action: Contact the system programming staff.
21231
21232
21233 iom_data_init.pl1
21234 IOM model of "nsa" for IOM TAG will be changed to
21235 "iom".
21236
21237
21238 Stream: $announce
21239
21240
21241
21242 IOM 367 08/21/20 MR12.7^L
21243
21244
21245 Time: System Intialization.
21246
21247 Meaning: The model field of this IOM card should be "iom".
21248 The system will correct it for this boot.
21249
21250 Action: Correct configuration deck before next boot.
21251
21252
21253 iom_data_init.pl1
21254 iom_data_init: Bad IOM tag TAG. IOM card
21255 ignored.
21256
21257
21258 Stream: BOS Typewriter Crashes system
21259
21260 Time: System Intialization.
21261
21262 Meaning: An IOM card contained an IOM tag other than A B
21263 C or D.
21264
21265 Action: Correct configuration deck and reboot.
21266
21267
21268 iom_data_init.pl1
21269 iom_data_init: Bad model MODEL for IOM TAG. IOM
21270 card ignored.
21271
21272
21273 Stream: BOS Typewriter Crashes system
21274
21275 Time: System Intialization.
21276
21277 Meaning: The model field for IOM TAG was not recognized.
21278
21279 Action: Correct configuration deck and reboot.
21280
21281
21282 iom_data_init.pl1
21283 iom_data_init: Bad state STATE for IOM TAG. IOM
21284 card ignored.
21285
21286
21287 Stream: BOS Typewriter Crashes system
21288
21289 Time: System Intialization.
21290
21291 Meaning: The state for IOM TAG was neither "on" or "off".
21292
21293 Action: Correct configuration deck and reboot.
21294
21295
21296 iom_data_init.pl1
21297 iom_data_init: Data not in low 256K.
21298
21299
21300 iom_data_init 368 08/21/20 MR12.7^L
21301
21302
21303 Stream: BOS Typewriter Crashes system
21304
21305 Time: System Intialization.
21306
21307 Meaning: The IOM data bases are not located in the low 256K
21308 of memory. This indicates a logic error in the
21309 supervisor or CPU or memory hardware problems.
21310
21311 Action: Correct configuration deck and reboot.
21312
21313
21314 iom_data_init.pl1
21315 iom_data_init: Duplicate IOM TAG in config deck.
21316
21317
21318 Stream: BOS Typewriter Crashes system
21319
21320 Time: System Intialization.
21321
21322 Meaning: Two IOM cards specifying IOM tag TAG were found in
21323 the configuration deck.
21324
21325 Action: Correct configuration deck and reboot.
21326
21327
21328 iom_data_init.pl1
21329 iom_data_init: Error from absadr.
21330
21331
21332 Stream: BOS Typewriter Crashes system
21333
21334 Time: System Intialization.
21335
21336 Meaning: This indicates a logic error in the supervisor or
21337 CPU or memory hardware problems.
21338
21339 Action: Contact the system programming staff.
21340
21341
21342 iom_data_init.pl1
21343 iom_data_init: Illegal port number PORT for IOM
21344 TAG.
21345
21346
21347 Stream: BOS Typewriter Crashes system
21348
21349 Time: System Intialization.
21350
21351 Meaning: The IOM card for IOM TAG contained an illegal port
21352 number. The port number must be between 0 and 7.
21353
21354 Action: Correct configuration deck and reboot.
21355
21356
21357
21358 iom_data_init 369 08/21/20 MR12.7^L
21359
21360
21361
21362
21363 iom_data_init.pl1
21364 iom_data_init: IOM TAG reuses port PORT.
21365
21366
21367 Stream: BOS Typewriter Crashes system
21368
21369 Time: System Intialization.
21370
21371 Meaning: IOM TAG has been given the same port as some other
21372 active module CPU or IOM.
21373
21374 Action: Correct configuration deck and reboot.
21375
21376
21377 iom_data_init.pl1
21378 iom_data_init: No valid IOM cards found.
21379
21380
21381 Stream: BOS Typewriter Crashes system
21382
21383 Time: System Intialization.
21384
21385 Meaning: There were no valid IOM cards in the configuration
21386 deck.
21387
21388 Action: Correct configuration deck and reboot.
21389
21390
21391 iom_data_init.pl1
21392 iom_data_init: Unable to assign overhead channel
21393 for IOM TAG.
21394
21395
21396 Stream: BOS Typewriter Crashes system
21397
21398 Time: System Intialization.
21399
21400 Meaning: Could not set up overhead channel handlers for IOM
21401 TAG. This indicates a logic error in the
21402 supervisor or CPU or memory hardware problems.
21403
21404 Action: Contact the system programming staff.
21405
21406
21407 iom_error.pl1
21408 iom_error: Unexpected level LEVEL_NUM interrupt
21409 from channel CHNL Status word - OOOOOOOOOOOO~
21410
21411
21412 Stream: BOS Typewriter.
21413
21414
21415
21416 iom_error 370 08/21/20 MR12.7^L
21417
21418
21419 Time: While system is running.
21420
21421 Meaning: The specified level interrupt has occured on
21422 channel CHNL either no channel assignment was
21423 found for the specified channel or there was no
21424 handler specified for the channel. If CHNL is a
21425 "?" this indicates an error occured converting
21426 the iom and channel numbers which are displayed
21427 in parenthesis "iom N chan_no N" after the
21428 question mark. The status word associated with
21429 the interrupt will be displayed when non-zero.
21430
21431 Action: Contact the system programming staff.
21432
21433
21434 iom_overhead.pl1
21435 iom_overhead: IOM TAG System fault status STATUS.
21436
21437
21438 Stream: BOS Typewriter.
21439
21440 Time: While system is running.
21441
21442 Meaning: An IOM system fault has occurred. This indicates
21443 a problem in either hardware or system software.
21444
21445 Action: Contact the system programming staff.
21446
21447
21448 iom_overhead.pl1
21449 iom_overhead: Status queue overrun for IOM TAG
21450 channel CHANNEL.
21451
21452
21453 Stream: BOS Typewriter.
21454
21455 Time: While system is running.
21456
21457 Meaning: The IOM has failed to refresh the DCW for an
21458 overhead channel. This indicates a hardware
21459 problem.
21460
21461 Action: Contact the system programming staff.
21462
21463
21464 lap_simplex.pl1
21465 lap_simplexCHN: Attempt to write overlength
21466 frame.
21467
21468
21469 Stream: Logged in SYSERR log.
21470
21471 Time: While system is running.
21472
21473
21474 lap_simplexCHN 371 08/21/20 MR12.7^L
21475
21476
21477 Meaning: An attempt was made to add a buffer to a frame
21478 which didn't have room for it. The connection
21479 will be crashed.
21480
21481 Action: Contact the system programming staff.
21482
21483
21484 lap_simplex.pl1
21485 lap_simplexCHN: Failure Link state: STATE
21486 Current Action: FUNCTION in ESTATE Primary
21487 state: PSTATE Secondary state: SSTATE.
21488
21489
21490 Stream: Logged in SYSERR log.
21491
21492 Time: While system is running.
21493
21494 Meaning: Normal request to crash the line when the link has
21495 been disconnected by the FNP. STATE is the main
21496 state of the link. FUNCTION is the last function
21497 the link processed. The ESTATE is the execution
21498 state of the last function. PSTATE and SSTATE are
21499 the link up substate.
21500
21501 Action: Contact the system programming staff.
21502
21503
21504 lap_simplex.pl1
21505 lap_simplexCHN: Invalid subchannel index XXX
21506
21507
21508 Stream: $alarm
21509
21510 Time: While system is running.
21511
21512 Meaning: Some call which attempted to write process a
21513 control order or process a modes operation
21514 specified a subchannel other than 1.
21515
21516 Action: Contact the system programming staff.
21517
21518
21519 lap_simplex.pl1
21520 lap_simplexCHN: Link disconnected due to
21521 mis-matched frame sizes. CMDR/FRMR frame: FRAME.
21522
21523
21524 Stream: Logged in SYSERR log.
21525
21526 Time: While system is running.
21527
21528 Meaning: The FNP has received a command reject LAPB or
21529 frame reject LAP which specified a reason of
21530
21531
21532 lap_simplexCHN 372 08/21/20 MR12.7^L
21533
21534
21535 "wide frame" on channel CHN. The actual level 2
21536 command is FRAME. This means the frame received
21537 by the other end was too long. Instead of looping
21538 continuously trying to send this frame the link
21539 will be disconnected. The maximum frame size in
21540 the Multics TTF for this link should be checked
21541 against the size expected by the other end of the
21542 link and corrected.
21543
21544 Action: Contact the system programming staff.
21545
21546
21547 lap_simplex.pl1
21548 lap_simplexCHN: Unexpected interrupt TYPE DATA
21549 received.
21550
21551
21552 Stream: Logged in SYSERR log.
21553
21554 Time: While system is running.
21555
21556 Meaning: An unexpected MCM interrupt was processed.
21557
21558 Action: Contact the system programming staff.
21559
21560
21561 lap_simplex.pl1
21562 lap_simplexCHN: Write failed to take whole
21563 frame discarding rest.
21564
21565
21566 Stream: Logged in SYSERR log.
21567
21568 Time: While system is running.
21569
21570 Meaning: A attempt to write a whole frame failed only a
21571 part of it was taken. An attempt will be made to
21572 continue.
21573
21574 Action: Contact the system programming staff.
21575
21576
21577 lg_ctl_.pl1
21578 lg_ctl_$logout: called with
21579 active=N^proc_create_ok for NAME.PROJ TTY ute
21580 MM||NN
21581
21582
21583 Stream: as severity0
21584
21585 Time: While system is running.
21586
21587
21588
21589
21590 lg_ctl_$logout 373 08/21/20 MR12.7^L
21591
21592
21593 Meaning: At attempt was made to logout a process which was
21594 not logged in. This is most likely the cause of a
21595 login error in the answering service.
21596
21597 Action: Contact the system programming staff._sa
21598
21599
21600 lg_ctl_.pl1
21601 lg_ctl_: lowered max ring for PERSON.PROJECT from
21602 N in PDTE to M in SATE
21603
21604
21605 Stream: as severity0
21606
21607 Time: While system is running.
21608
21609 Meaning: The value for the max ring specified in the PDT
21610 entry for PERSON on project PROJECT was lower than
21611 the maximum allowed ring in the SAT for the
21612 project. The SAT value was used for this login.
21613 The project administrator should change the PDT
21614 value to conform to the limits imposed by the
21615 system administrator.
21616
21617
21618
21619 lg_ctl_.pl1
21620 lg_ctl_: breach of physical security by NAME.PROJ
21621 from CHANNEL TYPE terminal "ID".
21622 lg_ctl_: person authorization is AUTH_NUM
21623 AUTH_STRING
21624 lg_ctl_: terminal access class is AUTH_NUM
21625 AUTH_STRING
21626
21627
21628
21629 Stream: as severity2
21630
21631 Time: While system is running.
21632
21633 Meaning: The user identified in the first message by NAME
21634 on the project PROJ has somehow gotten access to a
21635 terminal with an access class higher than his own
21636 authorization. The next two messages give
21637 additional information where AUTH_NUM is an
21638 encoding of the authorization or access class in
21639 numeric form and AUTH_STRING is the mnemonic form.
21640 The login is refused and the terminal is hung up.
21641
21642 Action: Notify the system security administrator.
21643
21644
21645 lg_ctl_.pl1
21646
21647
21648 lg_ctl_ 374 08/21/20 MR12.7^L
21649
21650
21651 lg_ctl_: disconnected count for USER is N1 in
21652 cdte N2 in pdte n_processes=N3.
21653
21654
21655 Stream: as severity1
21656
21657 Time: While system is running.
21658
21659 Meaning: The PDT entry for the user indicates that the user
21660 has a different number of disconnected processes
21661 than could actually be found in the answer_table.
21662 The PDT count is forced to the count of
21663 disconnected processes found in the answer_table.
21664 If this message occurs repeatedly for a given
21665 user notify the system administrator.
21666
21667 Action: No operator action is required.
21668
21669
21670 lg_ctl_.pl1
21671 lg_ctl_: ERROR_MESSAGE. Error updating PNT entry
21672 of USER.
21673
21674
21675 Stream: as severity2
21676
21677 Time: While system is running.
21678
21679 Meaning: The system was unable to update the PNT for the
21680 user. Login for the user was refused.
21681
21682 Action: Contact the system programming staff._sa
21683
21684
21685 lg_ctl_.pl1
21686 lg_ctl_: ERROR_MESSAGE. >sc1>pdt>PROJ.pdt
21687
21688
21689 Stream: as severity2
21690
21691 Time: While system is running.
21692
21693 Meaning: All users on project PROJ are unable to log in
21694 because the project's pdt cannot be accessed for
21695 the reason ERROR_MESSAGE.
21696
21697 Action: Contact the system programming staff._sa If the
21698 file was lost due to a crash it may be possible
21699 to retrieve it. If the file cannot be retrieved
21700 the person in charge of the project or the system
21701 administrator has to regenerate the file.
21702
21703
21704
21705
21706 lg_ctl_ 375 08/21/20 MR12.7^L
21707
21708
21709
21710
21711 lg_ctl_.pl1
21712 lg_ctl_: ERROR_MESSAGE. Changing Mail Table
21713 default project for USER to PROJ
21714
21715
21716 Stream: as severity2
21717
21718 Time: While system is running.
21719
21720 Meaning: USER.PROJ logged in with the
21721 -change_default_project control argument but it
21722 was not possible to change his Mail Table entry
21723 for the reason noted in ERROR_MESSAGE. USER's
21724 default project was changed though but the Mail
21725 Table and the PNT are now inconsistent.
21726
21727 Action: Contact the system programming staff._sa
21728
21729
21730 lg_ctl_.pl1
21731 lg_ctl_: ERROR_MESSAGE. Checksum failure reading
21732 PNT entry of USER.
21733
21734
21735 Stream: as severity2
21736
21737 Time: While system is running.
21738
21739 Meaning: The PNT entry for USER is damaged. It may have to
21740 be recreated or the entire PNT may have to be
21741 retrieved in special session. This can occur as a
21742 result of a damaged PNT or due to a logic error
21743 in the answering service.
21744
21745 Action: Contact the system programming staff._sa
21746
21747
21748 lg_ctl_.pl1
21749 lg_ctl_: ERROR_MESSAGE. Error reading PNT entry
21750 of USER.
21751
21752
21753 Stream: as severity2
21754
21755 Time: While system is running.
21756
21757 Meaning: This indicates that the system was unable to
21758 access the PNT. Login for the user was refused.
21759
21760 Action: Contact the system programming staff._sa Some or
21761 all users will be unable to log in.
21762
21763
21764 lg_ctl_ 376 08/21/20 MR12.7^L
21765
21766
21767
21768
21769 lg_ctl_.pl1
21770 lg_ctl_: ERROR_MESSAGE. Unable to check access
21771 for channel CHANNEL.
21772
21773
21774 Stream: as severity 1
21775
21776 Time: While system is running.
21777
21778 Meaning: The channel CHANNEL has the check_acs attribute
21779 set. However it was not possible to examine the
21780 Access Control Segment for the reason noted in
21781 ERROR_MESSAGE. Login for the user attempting to
21782 use this channel was refused.
21783
21784 Action: Contact the system programming staff._sa
21785
21786
21787 lg_ctl_.pl1
21788 lg_ctl_: ERROR_MESSAGE. unable to rehash sat.ht:
21789 REASON
21790
21791
21792 Stream: as severity2
21793
21794 Time: While system is running.
21795
21796 Meaning: An attempt to recreate the SAT hash table failed.
21797 The user attempting to log in was denied login.
21798 In all probably no users will be able to log in
21799 until the situation is repaired.
21800
21801 Action: Contact the system programming staff._sa
21802
21803
21804 lg_ctl_.pl1
21805 lg_ctl_: hash table of PROJ.pdt has PERS pdt has
21806 PERS2 at MM|NN
21807
21808
21809 Stream: as severity2
21810
21811 Time: While system is running.
21812
21813 Meaning: The PDT for PROJ is out of step with its hash
21814 table. The system attempts to log the user in.
21815 The PDT must be re-installed in order to correct
21816 the problem.
21817
21818 Action: Contact the system programming staff._sa
21819
21820
21821
21822 lg_ctl_ 377 08/21/20 MR12.7^L
21823
21824
21825
21826
21827 lg_ctl_.pl1
21828 lg_ctl_: login word is "QQQQ"
21829
21830
21831 Stream: as severity1
21832
21833 Time: System Intialization.
21834
21835 Meaning: If multics is typed a random 4-digit login word
21836 is made up.
21837
21838 Action: If any system programmers are to be allowed access
21839 to the system during this special session inform
21840 them of the login word. To allow normal use of
21841 Multics type "word login". In order to start the
21842 absentee facility which special sessions disable
21843 type "abs start".
21844
21845
21846
21847 lg_ctl_.pl1
21848 lg_ctl_: no hash table at WWWWWW of PROJ.pdt
21849
21850
21851 Stream: as severity2
21852
21853 Time: While system is running.
21854
21855 Meaning: A user is logging in to project PROJ. The
21856 project's pdt does not have a hash table even
21857 though the pdt header says it does. The system
21858 attempts to log the user in anyway. Possibly the
21859 PDT has been damaged.
21860
21861 Action: Contact the system programming staff.
21862
21863
21864 lg_ctl_.pl1
21865 lg_ctl_: password used PERS.PROJ CHANNEL
21866 TERM_TYPE ID
21867
21868
21869 Stream: as severity2
21870
21871 Time: While system is running.
21872
21873 Meaning: The system administrator has set a password trap
21874 on the password for the person PERS. This message
21875 is typed when the person tries to log in. The
21876 login was attempted from a TERM_TYPE terminal with
21877 identification code ID using channel CHANNEL.
21878
21879
21880 lg_ctl_ 378 08/21/20 MR12.7^L
21881
21882
21883 Action: Unless the system administrator has asked you to
21884 watch for this message ignore it. The system
21885 administrator can locate this message in the log
21886 and is presumably watching for it.
21887
21888
21889
21890 lg_ctl_.pl1
21891 lg_ctl_: PDT for project PROJECTID has its damage
21892 switch set. Login for user PERSONID refused.
21893
21894
21895
21896 Stream: as severity 2
21897
21898 Time: Contact the system programming staff.
21899
21900 Meaning: During a login attempt of user PERSONID on project
21901 PROJECTID the system noticed the damage switch
21902 set on the PDT for this project. The login was
21903 denied. A system administrator should determine
21904 whether the PDT is in fact damaged. If not
21905 he/she should turn off the damage switch for the
21906 PDT i.e. switch_off damage
21907 >sc1>pdt>PROJECTID.pdt If the PDT appears
21908 damaged then it should be retrieved from backup
21909 tape or re-installed when the system is in special
21910 session.
21911
21912
21913
21914 lg_ctl_.pl1
21915 lg_ctl_: PDT for project PROJECTID has its damage
21916 switch set. Login for user PERSONID refused.
21917
21918
21919
21920 Stream: as severity2
21921
21922 Time: Contact the system programming staff.
21923
21924 Meaning: During a login attempt of user PERSONID on project
21925 PROJECTID the system noticed the damage switch
21926 set on the PDT for this project. The login was
21927 denied. A system administrator should determine
21928 whether the PDT is in fact damaged. If not
21929 he/she should turn off the damage switch for the
21930 PDT i.e. switch_off damage
21931 >sc1>pdt>PROJECTID.pdt If the PDT appears
21932 damaged then it should be retrieved from backup
21933 tape or re-installed when the system is in special
21934 session.
21935
21936
21937
21938 lg_ctl_ 379 08/21/20 MR12.7^L
21939
21940
21941
21942
21943 lg_ctl_.pl1
21944 lg_ctl_: project PROJ state N still in sat.ht
21945
21946
21947 Stream: as severity2
21948
21949 Time: While system is running.
21950
21951 Meaning: A user on a deleted project attempted to log in
21952 and the supposedly deleted project was still in
21953 the SAT hash table. The user is refused login.
21954 The SAT and its hash table are out of step. The
21955 system continues operating.
21956
21957 Action: Contact the system programming staff.
21958
21959
21960 lg_ctl_.pl1
21961 lg_ctl_: project PROJECT has invalid
21962 rate_structure number N. Using rate_structure 0.
21963
21964
21965 Stream: as severity2
21966
21967 Time: While system is running.
21968
21969 Meaning: The SAT entry for the project has an invalid
21970 rate_structure number. The user is allowed to log
21971 in but is charged at the default rate i.e.
21972 according to rate_structure 0 Notify the system
21973 administrator so that the SAT entry may be
21974 corrected. This message will occur for each login
21975 using project PROJECT.
21976
21977 Action: Contact the system programming staff._sa
21978
21979
21980 lg_ctl_.pl1
21981 lg_ctl_: project.n_users = N for PROJ logout
21982 PERSON
21983
21984
21985 Stream: as severity0
21986
21987 Time: While system is running.
21988
21989 Meaning: The count of the active users on a project went
21990 negative when attempting to logout PERSON. This
21991 is most likely the result of a logic error in the
21992 answering service or a damaged PDT.
21993
21994
21995
21996 lg_ctl_ 380 08/21/20 MR12.7^L
21997
21998
21999 Action: Contact the system programming staff._sa
22000
22001
22002 lg_ctl_.pl1
22003 lg_ctl_: project.n_users = N for PROJECT login
22004 PERSON
22005
22006
22007 Stream: as severity0
22008
22009 Time: While system is running.
22010
22011 Meaning: The value of project.n_users for project PROJECT
22012 went negative while attempting to login PERSON.
22013 The user was permitted login but there may be
22014 discrepancies which may affect future operations.
22015
22016 Action: Contact the system programming staff._sa
22017
22018
22019 lg_ctl_.pl1
22020 lg_ctl_: raised initial ring for PERSON.PROJECT
22021 from N in PDTE to M in SATE
22022
22023
22024 Stream: as severity0
22025
22026 Time: While system is running.
22027
22028 Meaning: The value for the initial ring specified in the
22029 PDT entry for PERSON on project PROJECT was lower
22030 than than allowed for the project in the SAT. The
22031 value in the SAT was used in logging in this user.
22032 The project adminstrator should change the value
22033 in the PDT to conform to the limits imposed by the
22034 system adminstrator.
22035
22036 Action: No operator action is required.
22037
22038
22039 lg_ctl_.pl1
22040 lg_ctl_: reduced pdir quota for PERSON.PROJECT
22041 from N in PDTE to M in SATE
22042
22043
22044 Stream: as severity0
22045
22046 Time: While system is running.
22047
22048 Meaning: The value for process directory quota specified in
22049 the PDT entry for PERSON on project PROJECT was
22050 greater than the maximum allowed process directory
22051 quota specified in the SAT entry for PROJECT. The
22052
22053
22054 lg_ctl_ 381 08/21/20 MR12.7^L
22055
22056
22057 SAT value was used for this login. The project
22058 administrator for the project should set the value
22059 within the limits imposed by the system
22060 administrator.
22061
22062 Action: No operator action is required.
22063
22064
22065 lg_ctl_.pl1
22066 lg_ctl_: sat.ht has "WWWW" SAT has "xxxx" at
22067 MM|NN.
22068
22069
22070 Stream: as severity2
22071
22072 Time: While system is running.
22073
22074 Meaning: The SAT and its hash table are out of step or a
22075 storage system error has occurred. This could be
22076 the result of an incomplete reload. The system
22077 attempts to rehash the table and continue.
22078
22079 Action: Contact the system programming staff._sa
22080
22081
22082 lg_ctl_.pl1
22083 lg_ctl_: too many bad passwords for NAME.PROJ
22084 from CHANNEL TYPE terminal "ID".
22085
22086
22087 Stream: as severity2
22088
22089 Time: While system is running.
22090
22091 Meaning: The user identified by NAME on the project PROJ
22092 has either forgotten his password or someone else
22093 is trying to guess it. The system has refused the
22094 login for an installation-specified number of
22095 times before this message is printed. The maximum
22096 number of times the password can be used
22097 incorrectly before this message is printed is
22098 stored in the segment installation_parms.
22099
22100 Action: Contact the system programming staff._sa
22101
22102
22103 lg_ctl_.pl1
22104 lg_ctl_: tracing turned off.
22105
22106
22107 Stream: as severity1
22108
22109 Time: While system is running.
22110
22111
22112 lg_ctl_ 382 08/21/20 MR12.7^L
22113
22114
22115 Meaning: A system adminstrator has disabled tracing of the
22116 module lg_ctl_.
22117
22118 Action: No operator action is required.
22119
22120
22121 lg_ctl_.pl1
22122 lg_ctl_: tracing turned on.
22123
22124
22125 Stream: as severity1
22126
22127 Time: While system is running.
22128
22129 Meaning: A system administrator has enabled tracing of the
22130 module lg_ctl_. Debugging information will appear
22131 on the console.
22132
22133 Action: No operator action is required.
22134
22135
22136 lg_ctl_.pl1
22137 lg_ctl_: TYPE access to channel CHANNEL by
22138 NAME.PROJ denied by ACS.
22139
22140
22141 Stream: as severity 0
22142
22143 Time: While system is running.
22144
22145 Meaning: The user NAME.PROJ attempted to use the TYPE
22146 command while dialed-up on channel CHANNEL.
22147 However the access to the channel is restricted
22148 by Access Control Segment and the user is not
22149 permitted to use the channel.
22150
22151 Action: No operator action is required.
22152
22153
22154 lg_ctl_.pl1
22155 lg_ctl_: user PERSON state N still in hash
22156 table of PROJ.pdt
22157
22158
22159 Stream: as severity2
22160
22161 Time: While system is running.
22162
22163 Meaning: A deleted user attempted to log in to project
22164 PROJ and his name was still in the hash table of
22165 the project's PDT. The user is refused login.
22166 The PDT has probably been damaged by a software
22167 malfunction.
22168
22169
22170 lg_ctl_ 383 08/21/20 MR12.7^L
22171
22172
22173 Action: Contact the system programming staff.
22174
22175
22176 load_ctl_.pl1
22177 load_ctl_: bumping NAME1.PROJ for NAME2.PROJ:
22178 REASON
22179
22180
22181 Stream: as severity1
22182
22183 Time: While system is running.
22184
22185 Meaning: This message is typed out when a user is bumped.
22186 A user may be bumped by another member of his load
22187 control group in which case REASON is pr_grp
22188 which means group preemption. If a secondary user
22189 is bumped by a primary user either from the same
22190 group or from another group REASON is pr_sec
22191 meaning secondary user preemption. If REASON is
22192 pr_emrg meaning emergency preemption a system
22193 programmer was logging in and had to bump some
22194 user. A user is usually given three minutes after
22195 this message to clean up and log out before being
22196 automatically logged out.
22197
22198 Action: No operator action is required.
22199
22200
22201 load_ctl_.pl1
22202 load_ctl_: configuration not in tables. X cpu Y
22203 mem W bulk shift Z using configuartion XX cpu
22204 YY mem WW bulk shift ZZ
22205
22206
22207
22208 Stream: as severity2
22209
22210 Time: May occur at any time.
22211
22212 Meaning: The automatic setting of maxunits by the load
22213 control facility was attempted but the
22214 configuration tables did not have a configuration
22215 defined that matched the current configuration.
22216 No change was made to the system parameters. The
22217 system continues operation selecting the last
22218 entry in the config tables which should
22219 correspond to the largest system described by the
22220 system administrator. The values assumed by
22221 automatic load control are given in the second
22222 line of the message.
22223
22224
22225
22226
22227
22228 load_ctl_ 384 08/21/20 MR12.7^L
22229
22230
22231 Action: Set maxunits and the absentee max manually.
22232 Inform the system administrator so that he can
22233 update the load control tables.
22234
22235
22236
22237 load_ctl_.pl1
22238 load_ctl_: demote NAME.PROJ GROUP NNN
22239
22240
22241 Stream: as severity1
22242
22243 Time: While system is running.
22244
22245 Meaning: This is trace output. This user has been demoted
22246 to secondary status.
22247
22248 Action: No operator action is required. To turn off this
22249 output type load_ctl_$lctraceoff from admin mode.
22250
22251
22252
22253 load_ctl_.pl1
22254 load_ctl_: Entry not found. master_group_table
22255
22256
22257 Stream: as severity2
22258
22259 Time: System Intialization.
22260
22261 Meaning: load_ctl_ cannot find the master_group_table. The
22262 system will probably not be able to perform the
22263 bootload operation.
22264
22265 Action: Contact the system programming staff.
22266
22267
22268 load_ctl_.pl1
22269 load_ctl_: ERROR_MESSAGE During work class
22270 redefinition
22271
22272
22273 Stream: as severity2
22274
22275 Time: While the system is running or during system
22276 startup.
22277
22278 Meaning: Either some system table has been damaged or a
22279 system administrator was changing work class
22280 definitions at the time of a shift change or when
22281 a "maxu auto" command was issued. Error messages
22282 immediately preceding this one contain more
22283 information about the exact nature of the problem.
22284
22285
22286 load_ctl_ 385 08/21/20 MR12.7^L
22287
22288
22289 Action: Contact the system programming staff._sa He may
22290 want you to type the "maxu auto" command to retry
22291 the operation that failed. If that command
22292 produces no error messages the problem has been
22293 eliminated.
22294
22295
22296
22297 load_ctl_.pl1
22298 load_ctl_: group GRPID missing at logout
22299
22300
22301 Stream: as severity2
22302
22303 Time: While system is running.
22304
22305 Meaning: The master_group_table entry for GRPID has
22306 vanished. The system is attempting to logout a
22307 user from that group but cannot find the table
22308 entry for the group. The system will attempt to
22309 continue.
22310
22311 Action: Contact the system programming staff._sa
22312
22313
22314 load_ctl_.pl1
22315 load_ctl_: group GRPID missing at preempt
22316
22317
22318 Stream: as severity2
22319
22320 Time: While system is running.
22321
22322 Meaning: The master_group_table entry for GRPID has
22323 vanished. The system is attempting to preempt a
22324 user from that group but cannot find the table
22325 entry for the group. The system will attempt to
22326 continue.
22327
22328 Action: Contact the system programming staff._sa
22329
22330
22331 load_ctl_.pl1
22332 load_ctl_: Group GRPID missing for NAME.PROJ
22333
22334
22335 Stream: as severity2
22336
22337 Time: While system is running.
22338
22339 Meaning: The system administrator has designated that the
22340 project PROJ should be in the load control group
22341 GRPID but the entry in the master_group_table for
22342
22343
22344 load_ctl_ 386 08/21/20 MR12.7^L
22345
22346
22347 that load control group is missing. The user
22348 cannot log in. This may be an indication that the
22349 segment master_group_table has been damaged.
22350
22351 Action: Contact the system programming staff._sa
22352
22353
22354 load_ctl_.pl1
22355 load_ctl_: group GRPID not authorized for project
22356 PROJ
22357
22358
22359 Stream: as severity2
22360
22361 Time: While system is running.
22362
22363 Meaning: A project administrator has designated that one of
22364 the users in project PROJ should be in the load
22365 control group GRPID but the system administrator
22366 has not authorized that project to be in that
22367 group. An attempt will be made to log the user
22368 in using the default group for his project.
22369 Subsequent messages will indicate the success or
22370 failure of this attempt.
22371
22372 Action: Contact the system programming staff._sa
22373
22374
22375 load_ctl_.pl1
22376 load_ctl_: group GRPID not found in mgt for
22377 NAME.PROJ
22378
22379
22380 Stream: as severity2
22381
22382 Time: While system is running.
22383
22384 Meaning: A system or project administrator has designated
22385 that the user NAME.PROJ should be in the load
22386 control group GRPID but the master_group_table
22387 mgt has no entry for that group. An attempt
22388 will be made to log the user in using the default
22389 group for his project. Subsequent messages will
22390 indicate the success or failure of this attempt.
22391
22392 Action: Contact the system programming staff._sa
22393
22394
22395 load_ctl_.pl1
22396 load_ctl_: maxu too small XX YY units for
22397 group GRPID
22398
22399
22400
22401
22402 load_ctl_ 387 08/21/20 MR12.7^L
22403
22404
22405 Stream: as severity2
22406
22407 Time: While system is running.
22408
22409 Meaning: The system administrator has specified that the
22410 load control group GRPID is to have "all the rest"
22411 of the primary load units after all other groups
22412 have taken their allocations from maxunits.
22413 However maxunits is less than the sum of the
22414 primary allocations giving the group GRPID the
22415 negative allocation of YY units. The system
22416 proceeds attempting to log the user in anyway.
22417 Of course the user is allowed secondary status
22418 only if he is allowed to log in at all. This is
22419 often the result of the operator typing maxu 30
22420 instead of maxu 300 or some similar error.
22421
22422 Action: Check the value of maxunits and if a mistake was
22423 made correct it. If the maxunits value is
22424 correct note this situation for the system
22425 administrator.
22426
22427
22428
22429 load_ctl_.pl1
22430 load_ctl_: more than one group has -1 max: GRPID
22431
22432
22433 Stream: as severity2
22434
22435 Time: System Intialization.
22436
22437 Meaning: The system administrator has accidentally given
22438 more than one group a "take all the rest" maximum
22439 primary unit allocation. The user control package
22440 cannot handle this situation. The second group
22441 with a -1 maxprim is listed. The system completes
22442 startup and users can log in but maxunits may not
22443 be obeyed.
22444
22445 Action: Contact the system programming staff._sa
22446
22447
22448 load_ctl_.pl1
22449 load_ctl_: promote NAME.PROJ GROUP NNN
22450
22451
22452 Stream: as severity1
22453
22454 Time: While system is running.
22455
22456 Meaning: This is trace output. This user has been promoted
22457 to primary status.
22458
22459
22460 load_ctl_ 388 08/21/20 MR12.7^L
22461
22462
22463 Action: No operator action is required. To turn off this
22464 output type load_ctl_$lctraceoff from admin mode.
22465
22466
22467
22468 load_ctl_.pl1
22469 load_ctl_: reduced grace for PERSON.PROJECT from
22470 MINUTES1 in PDTE to MINUTES2 in SATE
22471
22472
22473 Stream: as severity 0
22474
22475 Time: While system is running.
22476
22477 Meaning: The Project Definition Table PDT entry for
22478 PERSON.PROJECT specifies a larger grace time time
22479 during which a process is protected from
22480 preemption than does the System Administrator's
22481 Table SAT entry for the project. The time given
22482 in the SAT entry is used.
22483
22484 Action: No operator action is required.
22485
22486
22487 load_ctl_.pl1
22488 load_ctl_: Too many primes. NAME.PROJ GROUP
22489 MM/NN
22490
22491
22492 Stream: as severity0
22493
22494 Time: While system is running.
22495
22496 Meaning: This is trace output. The system has been
22497 committed to allow a certain number of users from
22498 group GROUP to be logged in at one time. In order
22499 to log this user in some other user must be
22500 bumped but all users have primary status and
22501 cannot be bumped. This situation may be a
22502 consequence of system programmers with the
22503 overloading privilege logging in when the system
22504 is full. The user is allowed to log in anyway.
22505
22506 Action: No operator action is required.
22507
22508
22509 load_ctl_.pl1
22510 load_ctl_: Unknown mgt version number: NUMBER
22511
22512
22513 Stream: as severity2
22514
22515 Time: System Intialization.
22516
22517
22518 load_ctl_ 389 08/21/20 MR12.7^L
22519
22520
22521 Meaning: Either the master_group_table mgt has been
22522 damaged or its format is incompatible with the
22523 current Answering Service. The system cannot be
22524 brought up until a correct mgt is provided.
22525
22526 Action: Contact the system programming staff._sa
22527
22528
22529 load_disk_mpcs.pl1
22530 load_disk_mpcs: Disk mpcs: NAMES appear not to
22531 be operating.
22532
22533
22534
22535 Stream: $announce
22536
22537 Time: System Intialization.
22538
22539 Meaning: The named disk mpcs listed in the config deck
22540 did not respond to a "request status" control
22541 order. They are believed not to be operating; in
22542 particular firmware should probably be loaded
22543 into them.
22544
22545
22546
22547 load_disk_mpcs.pl1
22548 load_disk_mpcs: Operator aborted disk MPC
22549 loading.
22550
22551
22552 Stream: BOS Typewriter Crashes system
22553
22554 Time: System Intialization.
22555
22556 Meaning: The operator answered "abort" when requested to
22557 supply disk mpcs to be loaded. This will cause a
22558 return to the previous bce command level.
22559
22560
22561
22562 load_fnp_.pl1
22563 load_fnp_: Core image for FNP X will not support
22564 HSLA #N; <core image pathname>
22565
22566
22567 Stream: BOS Typewriter.
22568
22569 Time: While system is running.
22570
22571 Meaning: The CDT specifies that a channel should be used
22572 but the MCS core image for FNP X does not contain
22573 support for the indicated HSLA. Either the MCS
22574
22575
22576 load_fnp_ 390 08/21/20 MR12.7^L
22577
22578
22579 core image or the CDT must be modified. The FNP
22580 cannot be loaded.
22581
22582 Action: Contact the system programming staff._sa
22583
22584
22585 load_fnp_.pl1
22586 load_fnp_: Core image for FNP X will not support
22587 LSLA #N; <core image pathname>
22588
22589
22590 Stream: BOS Typewriter.
22591
22592 Time: While system is running.
22593
22594 Meaning: The CDT specifies that a channel should be used
22595 but the MCS core image for FNP X does not contain
22596 support for the indicated LSLA. Either the MCS
22597 core image or the CDT must be modified. The FNP
22598 cannot be loaded.
22599
22600 Action: Contact the system programming staff._sa
22601
22602
22603 load_fnp_.pl1
22604 load_fnp_: ERROR_MESSAGE. Creating boot segment
22605 in process directory for FNP X.
22606
22607
22608 Stream: BOS Typewriter.
22609
22610 Time: While system is running.
22611
22612 Meaning: Ths system was unable to create a temporary
22613 segment in the initializer's process directory to
22614 hold core image for FNP X. This indicates a logic
22615 error in the supervisor or CPU or memory hardware
22616 problems. The FNP cannot be loaded.
22617
22618 Action: Contact the system programming staff.
22619
22620
22621 load_fnp_.pl1
22622 load_fnp_: ERROR_MESSAGE. During FNP X bootload
22623 attempt.
22624
22625
22626 Stream: BOS Typewriter.
22627
22628 Time: While system is running.
22629
22630 Meaning: An error occurred while sending the new core image
22631 to FNP X. The FNP cannot be loaded.
22632
22633
22634 load_fnp_ 391 08/21/20 MR12.7^L
22635
22636
22637 Action: Contact the system programming staff.
22638
22639
22640 load_fnp_.pl1
22641 load_fnp_: ERROR_MESSAGE. expand_pathname_ on
22642 IMAGE_PATH for FNP X.
22643
22644
22645 Stream: BOS Typewriter.
22646
22647 Time: While system is running.
22648
22649 Meaning: The CDT entry for FNP X specifies a bad path for
22650 its core image. The FNP cannot be loaded.
22651
22652 Action: Contact the system programming staff._sa
22653
22654
22655 load_fnp_.pl1
22656 load_fnp_: ERROR_MESSAGE. Getting FNP info for
22657 FNP X.
22658
22659
22660 Stream: BOS Typewriter.
22661
22662 Time: While system is running.
22663
22664 Meaning: The system could not obtain information about FNP
22665 X from the hardcore. The CDT may disagree with
22666 the CONFIG deck. The FNP cannot be loaded.
22667
22668 Action: Contact the system programming staff._sa
22669
22670
22671 load_fnp_.pl1
22672 load_fnp_: ERROR_MESSAGE. Locating IMAGE_PATH
22673 for FNP X.
22674
22675
22676 Stream: BOS Typewriter.
22677
22678 Time: While system is running.
22679
22680 Meaning: The system cannot locate the core image for FNP X.
22681 The CDT entry for the FNP may be incorrect or the
22682 copy of the MCS may have been deleted. The FNP
22683 cannot be loaded.
22684
22685 Action: Contact the system programming staff._sa
22686
22687
22688 load_fnp_.pl1
22689
22690
22691
22692 load_fnp_ 392 08/21/20 MR12.7^L
22693
22694
22695 load_fnp_: ERROR_MESSAGE. Wiring memory for FNP
22696 X bootload.
22697
22698
22699 Stream: BOS Typewriter.
22700
22701 Time: While system is running.
22702
22703 Meaning: The system cannot wire down the process directory
22704 segment which will be used to boot FNP X. This
22705 indicates a logic error in the supervisor or CPU
22706 or memory hardware problems. The FNP cannot be
22707 loaded.
22708
22709 Action: Contact the system programming staff.
22710
22711
22712 load_fnp_.pl1
22713 load_fnp_: Invalid core image for FNP X .crldt
22714 exceeds current time <core image pathname>
22715
22716
22717 Stream: BOS Typewriter.
22718
22719 Time: While system is running.
22720
22721 Meaning: The creation date of the MCS core image for FNP X
22722 is past the current time. The MCS core image is
22723 probably damaged and will have to be recreated.
22724 The FNP cannot be loaded.
22725
22726 Action: Contact the system programming staff.
22727
22728
22729 load_fnp_.pl1
22730 load_fnp_: Invalid core image for FNP X bad
22731 .crmem value of N in image <core image pathname>
22732
22733
22734 Stream: BOS Typewriter.
22735
22736 Time: While system is running.
22737
22738 Meaning: The value of .crmem should be 24575 32767 or
22739 65535 in a valid fnp core image. The MCS core
22740 image for FNP X will have to be modified. The FNP
22741 cannot be loaded.
22742
22743 Action: Contact the system programming staff.
22744
22745
22746 load_fnp_.pl1
22747
22748
22749
22750 load_fnp_ 393 08/21/20 MR12.7^L
22751
22752
22753 load_fnp_: Invalid core image for FNP X bad
22754 module chain <core image pathname>
22755
22756
22757 Stream: BOS Typewriter.
22758
22759 Time: While system is running.
22760
22761 Meaning: An inconsistency was found in tracing through the
22762 module chain of the MCS core image for FNP X. The
22763 MCS core image is probably damaged and will have
22764 to be recreated. The FNP cannot be loaded.
22765
22766 Action: Contact the system programming staff.
22767
22768
22769 load_fnp_.pl1
22770 load_fnp_: Invalid core image for FNP X binding
22771 of image was done over N years ago <core image
22772 pathname>
22773
22774
22775 Stream: BOS Typewriter.
22776
22777 Time: While system is running.
22778
22779 Meaning: The creation date of the MCS core image for FNP X
22780 indicates the image is over N years old. The MCS
22781 core image is probably damaged and will have to be
22782 recreated. The FNP cannot be loaded.
22783
22784 Action: Contact the system programming staff.
22785
22786
22787 load_fnp_.pl1
22788 load_fnp_: Invalid core image for FNP X found
22789 only N modules minimum required is M <core
22790 image pathname>
22791
22792
22793 Stream: BOS Typewriter.
22794
22795 Time: While system is running.
22796
22797 Meaning: Only N program modules were found in the MCS core
22798 image for FNP X out of a minimum of M modules.
22799 The minimum number of modules is based on the
22800 number required to support the smallest FNP
22801 configuration. The MCS core image is probably
22802 damaged and will have to be recreated. The FNP
22803 cannot be loaded.
22804
22805 Action: Contact the system programming staff.
22806
22807
22808 load_fnp_ 394 08/21/20 MR12.7^L
22809
22810
22811
22812
22813 load_fnp_.pl1
22814 load_fnp_: Invalid core image for FNP X image
22815 length error <core image pathname>
22816
22817
22818 Stream: BOS Typewriter.
22819
22820 Time: While system is running.
22821
22822 Meaning: The bit count of the image was adjusted and did
22823 not compare with the image length found in the
22824 core image for FNP X. The first 36 bits of the
22825 image segment contains the image length set by
22826 bind_fnp_load_. The MCS core image is probably
22827 damaged and will have to be recreated. The FNP
22828 cannot be loaded.
22829
22830 Action: Contact the system programming staff.
22831
22832
22833 load_fnp_.pl1
22834 load_fnp_: Invalid core image for FNP X init
22835 module is not last in the module chain <core
22836 image pathname>
22837
22838
22839 Stream: BOS Typewriter.
22840
22841 Time: While system is running.
22842
22843 Meaning: In tracing through the module chain the last
22844 module in the core image for FNP X was not found
22845 to be the init module. The init module has to be
22846 the last module in the module chain because the
22847 init module releases itself and the rest of memory
22848 for buffer space when it is finished executing.
22849 The MCS core image is probably damaged and will
22850 have to be recreated. The FNP cannot be loaded.
22851
22852 Action: Contact the system programming staff.
22853
22854
22855 load_fnp_.pl1
22856 load_fnp_: Memory size of MK in image does not
22857 agree with memory size of NK in CDT for FNP X.
22858 Memory size of <minM N> from <CDT or image>
22859 will be used.
22860
22861
22862
22863 Stream: BOS Typewriter.
22864
22865
22866 load_fnp_ 395 08/21/20 MR12.7^L
22867
22868
22869 Time: While system is running.
22870
22871 Meaning: The memory size specified in the MCS core image
22872 does not match the memory size specified in the
22873 CDT. The memory size in the MCS core image that
22874 is loaded will be set to the minimum value. The
22875 FNP load attempt will continue.
22876
22877 Action: The memory size value in the MCS bind_fnp segment
22878 or CDT should be modified by site personnel.
22879
22880
22881 load_fnp_.pl1
22882 load_fnp_: Unable to load core image into FNP X.
22883 Core image <core image pathname> will not fit in
22884 32K.
22885
22886
22887 Stream: BOS Typewriter.
22888
22889 Time: While system is running.
22890
22891 Meaning: The MCS core image to be loaded into FNP X larger
22892 than 32K. The MCS image is incorrectly
22893 constructed or damaged. The FNP cannot be loaded.
22894
22895 Action: Contact the system programming staff.
22896
22897
22898 load_mst.pl1
22899 load_mst: bad header size SSS
22900
22901
22902 Stream: BOS Typewriter Crashes system
22903
22904 Time: System Intialization.
22905
22906 Meaning: A bad segment header was found on the bootload
22907 tape.
22908
22909 Action: Follow normal recovery procedures. $boot_tape
22910
22911
22912
22913 load_mst.pl1
22914 load_mst: error from slt_manager$build_entry
22915
22916
22917 Stream: BOS Typewriter Crashes system
22918
22919 Time: System Intialization.
22920
22921
22922
22923
22924 load_mst 396 08/21/20 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. $boot_tape
22931
22932
22933
22934 load_mst.pl1
22935 load_mst: Missing linkage or defs.
22936
22937
22938 Stream: BOS Typewriter Crashes system
22939
22940 Time: System Intialization.
22941
22942 Meaning: A linkage or definitions section which should be
22943 in the mst source appears to be missing.
22944
22945 Action: Follow normal recovery procedures. $boot_tape
22946
22947
22948
22949 load_mst.pl1
22950 load_mst: NAME can't be placed into file
22951 partition.
22952
22953
22954 Stream: BOS Typewriter Crashes system
22955
22956 Time: System Intialization.
22957
22958 Meaning: An error occurred while adding the named file from
22959 the mst into the bootload Multics file system.
22960
22961 Action: Follow normal recovery procedures. $boot_tape
22962
22963
22964
22965 load_mst.pl1
22966 load_mst: Out of space in mst area of bce
22967 partition.
22968
22969
22970 Stream: BOS Typewriter Crashes system
22971
22972 Time: System Intialization.
22973
22974 Meaning: There is not enough room in the mst area of the
22975 bce partition to hold collections 2.0 and 3.0.
22976
22977 Action: The size of this area will need to be increased.
22978 $boot_tape
22979
22980
22981
22982 load_mst 397 08/21/20 MR12.7^L
22983
22984
22985
22986
22987 load_mst.pl1
22988 load_mst: too many bce command segments.
22989
22990
22991 Stream: BOS Typewriter Crashes system
22992
22993 Time: System Intialization.
22994
22995 Meaning: An exceptionally large number of segments appeared
22996 in collection 1.5. This probably indicates an
22997 error in the mst.
22998
22999 Action: Follow normal recovery procedures. $boot_tape
23000
23001
23002
23003 load_mst.pl1
23004 load_mst: unexpected control type TTT
23005
23006
23007 Stream: BOS Typewriter Crashes system
23008
23009 Time: System Intialization.
23010
23011 Meaning: A segment control word was found out of sequence
23012 on the bootload tape.
23013
23014 Action: Follow normal recovery procedures. $boot_tape
23015
23016
23017
23018 load_mst.pl1
23019 load_mst: Unexpected DEFS/LINKAGE
23020
23021
23022 Stream: BOS Typewriter Crashes system
23023
23024 Time: System Intialization.
23025
23026 Meaning: A linkage or definitions section was found out of
23027 sequence in the mst source.
23028
23029 Action: Follow normal recovery procedures. $boot_tape
23030
23031
23032
23033 load_mst.pl1
23034 load_mst: unknown control type TTT
23035
23036
23037 Stream: BOS Typewriter Crashes system
23038
23039
23040 load_mst 398 08/21/20 MR12.7^L
23041
23042
23043 Time: System Intialization.
23044
23045 Meaning: A bad segment control word was found on the
23046 bootload tape.
23047
23048 Action: Follow normal recovery procedures. $boot_tape
23049
23050
23051
23052 load_mst.pl1
23053 load_mst: XXX. out of WWW. pages used in disk
23054 mst area.
23055
23056
23057 Stream: BOS Typewriter.
23058
23059 Meaning: This message shows the amount of the mst area of
23060 the bce partition that is used to hold the mst.
23061
23062 Action: No operator action is required. $boot_tape
23063
23064
23065
23066 load_system.pl1
23067 load_system: error from asd_$add_sentries The
23068 system could not remove the write access it had
23069 set to load the contents of a segment from the mst
23070 source.
23071
23072
23073
23074 Stream: BOS Typewriter Crashes system
23075
23076 Time: System Intialization.
23077
23078 Meaning: This indicates a logic error in the supervisor or
23079 CPU or memory hardware problems.
23080
23081 Action: Follow normal recovery procedures. $boot_tape
23082
23083
23084
23085 load_system.pl1
23086 load_system: error from set$entry_bound_ptr
23087
23088
23089 Stream: BOS Typewriter Crashes system
23090
23091 Time: System Intialization.
23092
23093 Meaning: This indicates a logic error in the supervisor or
23094 CPU or memory hardware problems.
23095
23096
23097
23098 load_system 399 08/21/20 MR12.7^L
23099
23100
23101 Action: Follow normal recovery procedures. $boot_tape
23102
23103
23104
23105 load_system.pl1
23106 load_system: illegal header length in mst source
23107
23108
23109 Stream: BOS Typewriter Crashes system
23110
23111 Time: System Intialization.
23112
23113 Meaning: This indicates a logic error in the supervisor or
23114 CPU or memory hardware problems.
23115
23116 Action: Follow normal recovery procedures. $boot_tape
23117
23118
23119
23120 load_system.pl1
23121 load_system: illegal type in mst source
23122
23123
23124 Stream: BOS Typewriter Crashes system
23125
23126 Time: System Intialization.
23127
23128 Meaning: This indicates a logic error in the supervisor or
23129 CPU or memory hardware problems.
23130
23131 Action: Follow normal recovery procedures. $boot_tape
23132
23133
23134
23135 load_system.pl1
23136 load_system: illegal type in mst source
23137
23138
23139 Stream: BOS Typewriter Crashes system
23140
23141 Time: System Intialization.
23142
23143 Meaning: This indicates a logic error in the supervisor or
23144 CPU or memory hardware problems.
23145
23146 Action: Follow normal recovery procedures. $boot_tape
23147
23148
23149
23150 fnp_util.pl1
23151 Loading FNP X CORE_IMAGE VERSION
23152
23153
23154
23155
23156 Loading 400 08/21/20 MR12.7^L
23157
23158
23159 Stream: BOS Typewriter.
23160
23161 Time: Answering service initialization and each
23162 subsequent FNP bootload.
23163
23164 Meaning: Loading of FNP X has begun with a core image named
23165 CORE_IMAGE normally "mcs" of version number
23166 VERSION.
23167
23168 Action: No operator action is required.
23169
23170
23171 lock.pl1
23172 lock: AST lock set at dir unlock time.
23173
23174
23175 Stream: BOS Typewriter Crashes system
23176
23177 Time: While system is running.
23178
23179 Meaning: The AST was found locked to this process at
23180 directory unlock time. This indicates a
23181 supervisor programming error.
23182
23183 Action: $reboot
23184
23185
23186 lock.pl1
23187 lock: dir_lock_read mylock err. dp =PTR
23188
23189
23190 Stream: BOS Typewriter Crashes system
23191
23192 Time: While system is running.
23193
23194 Meaning: An attempt to lock a directory for reading found
23195 the directory already locked to this process.
23196 This indicates a supervisor programming error.
23197
23198 Action: $reboot
23199
23200
23201 lock.pl1
23202 lock: dir_lock_write mylock err. dp =PTR
23203
23204
23205 Stream: BOS Typewriter Crashes system
23206
23207 Time: While system is running.
23208
23209 Meaning: An attempt to lock a directory for writing found
23210 the directory already locked to this process.
23211 This indicates a supervisor programming error.
23212
23213
23214 lock 401 08/21/20 MR12.7^L
23215
23216
23217 Action: $reboot
23218
23219
23220 lock.pl1
23221 lock: lock PTR not equal to processid. caller =
23222 PTR
23223
23224
23225 Stream: $lock_severity
23226
23227 Time: While system is running.
23228
23229 Meaning: An attempt was made to unlock a lock found not to
23230 be held by this process. This indicates a
23231 supervisor programming error.
23232
23233 Action: $reboot
23234
23235
23236 lock.pl1
23237 lock: LOCK_DIR: dir_lock_seg full.
23238
23239
23240 Stream: BOS Typewriter Crashes system
23241
23242 Time: While system is running.
23243
23244 Meaning: The segment used to record all locked directories
23245 overflowed. This may be a hardware problem.
23246
23247 Action: $reboot
23248
23249
23250 lock.pl1
23251 lock: LOCK_DIR: Too many readers.
23252
23253
23254 Stream: BOS Typewriter Crashes system
23255
23256 Time: While system is running.
23257
23258 Meaning: Too many processes attempted to request a read
23259 lock on a given directory. This may indicate a
23260 hardware problem.
23261
23262 Action: $reboot
23263
23264
23265 lock.pl1
23266 lock: LOCK_DIR: write lock call with read lock
23267 held. dp = PTR uid = UID.
23268
23269
23270
23271
23272 lock 402 08/21/20 MR12.7^L
23273
23274
23275 Stream: BOS Typewriter Terminates user process
23276
23277 Time: While system is running.
23278
23279 Meaning: A request was made to lock a directory for writing
23280 when the process already possessed a read lock on
23281 that directory. This indicates a supervisor
23282 programming error.
23283
23284 Action: $reboot
23285
23286
23287 lock.pl1
23288 lock: lock_fast mylock err PTR
23289
23290
23291 Stream: BOS Typewriter Crashes system
23292
23293 Time: While system is running.
23294
23295 Meaning: An attempt to lock a fast lock found the lock
23296 already locked to the requesting process. This
23297 indicates a supervisor programming error.
23298
23299 Action: $reboot
23300
23301
23302 lock.pl1
23303 lock: pds$block_lock_count <= 0. caller = PTR
23304
23305
23306 Stream: $lock_severity
23307
23308 Time: While system is running.
23309
23310 Meaning: An attempt to unlock a lock found that the process
23311 was holding no locks. This indicates a supervisor
23312 programming error.
23313
23314 Action: $reboot
23315
23316
23317 lock.pl1
23318 lock: stacq hardware failure on PTR
23319
23320
23321 Stream: BOS Typewriter Crashes system
23322
23323 Time: While system is running.
23324
23325 Meaning: The hardware failed to unlock the specified lock
23326 using a stacq instruction.
23327
23328
23329
23330 lock 403 08/21/20 MR12.7^L
23331
23332
23333 Action: Fix the hardware.
23334
23335
23336 lock.pl1
23337 lock: unlock_dir with dir.modify - uid = UID -
23338 callerp = PTR
23339
23340
23341 Stream: Logged in SYSERR log.
23342
23343 Time: While system is running.
23344
23345 Meaning: A directory being unlocked appears to have been
23346 undergoing a modification sequence that has not
23347 completed.
23348
23349 Action: The next reference to the directory will force a
23350 directory salvage.
23351
23352
23353 lock.pl1
23354 lock: UNLOCK_DIR: dir DIR_LOCK_IND not locked.
23355 caller = PTR.
23356
23357
23358 Stream: $lock_severity
23359
23360 Time: While system is running.
23361
23362 Meaning: A request to unlock a directory found that the
23363 dir_lock_seg entry does not show that the
23364 directory was locked.
23365
23366
23367 A: $reboot
23368
23369
23370
23371 lock.pl1
23372 lock: UNLOCK_DIR: dir DIR_LOCK_IND unlock called
23373 with bad uid caller = PTR
23374
23375
23376 Stream: Logged in SYSERR log.
23377
23378 Time: While system is running.
23379
23380 Meaning: A request to unlock a directory found that the UID
23381 of the directory does not match the UID at the
23382 time the directory was locked. However the UID
23383 does match that in the KST. This normally
23384 indicates that the directory was salvaged during
23385 the time that it was locked.
23386
23387
23388 lock 404 08/21/20 MR12.7^L
23389
23390
23391
23392
23393 lock.pl1
23394 lock: UNLOCK_DIR: lock count 0.
23395
23396
23397 Stream: $lock_severity
23398
23399 Time: While system is running.
23400
23401 Meaning: An attempt to unlock a directory found the
23402 dir_lock_seg entry for the directory not listing
23403 the directory as locked.
23404
23405 Action: $reboot
23406
23407
23408 lock.pl1
23409 lock: UNLOCK_DIR: lock not read locked to
23410 process.
23411
23412
23413 Stream: $lock_severity
23414
23415 Time: While system is running.
23416
23417 Meaning: A request to unlock a directory locked for reading
23418 found that the requesting process was not holding
23419 the directory locked.
23420
23421 Action: $reboot
23422
23423
23424 lock.pl1
23425 lock: UNLOCK_DIR: lock not write locked to
23426 process.
23427
23428
23429 Stream: $lock_severity
23430
23431 Time: While system is running.
23432
23433 Meaning: A request to unlock a directory that was found to
23434 be locked for writing was not locked to this
23435 process.
23436
23437 Action: $reboot
23438
23439
23440 lock.pl1
23441 lock: UNLOCK_DIR: UID Mismatch.
23442
23443
23444
23445
23446 lock 405 08/21/20 MR12.7^L
23447
23448
23449 Stream: $lock_severity
23450
23451 Time: While system is running.
23452
23453 Meaning: When attempting to unlock a directory the UID for
23454 the directory found in the dir_lock_seg entry did
23455 not match that of the directory.
23456
23457 Action: $reboot
23458
23459
23460 lock.pl1
23461 lock: unlock_fast lock PTR not locked to process.
23462 caller = PTR
23463
23464
23465 Stream: $lock_severity
23466
23467 Time: While system is running.
23468
23469 Meaning: An attempt to unlock a fast lock found that the
23470 lock was not held by the requesting process. This
23471 indicates a supervisor programming error.
23472
23473 Action: $reboot
23474
23475
23476 lock.pl1
23477 lock: VALIDATE_CACHE: FAILED running on cpu N
23478 memory address OOOOOOOO oct.
23479
23480
23481 Stream: BOS Typewriter.
23482
23483 Time: While system is running.
23484
23485 Meaning: This is most likely a cache write notify problem
23486 with the 8/70m processor "CPU N" or the System
23487 Control Unit containing the "memory address
23488 OOOOOOOO."
23489
23490 Action: Contact the system programming staff._sa
23491
23492
23493 page_error.alm
23494 lock_volmap: MYLOCK on volmap lock for
23495 dskX_NNS.
23496
23497
23498 Stream: BOS Typewriter Crashes system
23499
23500 Time: While system is running.
23501
23502
23503
23504 lock_volmap 406 08/21/20 MR12.7^L
23505
23506
23507 Meaning: A process attempted to lock the Volume Map lock
23508 for dskX_NNS while already owning the lock.
23509 This indicates a software malfunction.
23510
23511 Action: Follow normal recovery procedures.
23512
23513
23514 page_error.alm
23515 lock_volmap: MYLOCK on volmap lock for
23516 dskX_NNS.
23517
23518
23519 Stream: BOS Typewriter Crashes system
23520
23521 Time: While system is running.
23522
23523 Meaning: A process attempted to lock the Volume Map lock
23524 for dskX_NNS while already owning the lock.
23525 This indicates a software malfunction.
23526
23527 Action: Follow normal recovery procedures.
23528
23529
23530 page_error.alm
23531 lock_volmap: STACQ fails on dskX_NNS.
23532
23533
23534 Stream: BOS Typewriter Crashes system
23535
23536 Time: While system is running.
23537
23538 Meaning: The stacq instruction used to lock the Volume Map
23539 on dskX_NNS did not operate correctly. This
23540 indicates processor or memory malfunction.
23541
23542 Action: Follow normal recovery procedures.
23543
23544
23545 page_error.alm
23546 lock_volmap: STACQ fails on dskX_NNS.
23547
23548
23549 Stream: BOS Typewriter Crashes system
23550
23551 Time: While system is running.
23552
23553 Meaning: The stacq instruction used to lock the Volume Map
23554 on dskX_NNS did not operate correctly. This
23555 indicates processor or memory malfunction.
23556
23557 Action: Follow normal recovery procedures.
23558
23559
23560
23561
23562 logical_volume_manager 407 08/21/20 MR12.7^L
23563
23564
23565 logical_volume_manager.pl1
23566 logical_volume_manager: nonzero brother pvt
23567 thread
23568
23569
23570 Stream: BOS Typewriter Crashes system
23571
23572 Time: While system is running.
23573
23574 Meaning: This indicates a logic error in the supervisor or
23575 CPU or memory hardware problems.
23576
23577 Action: Follow normal recovery procedures.
23578
23579
23580 lg_ctl_.pl1
23581 LOGIN PERSON.PROJECT PROC_TYPE CHANNEL STATE
23582
23583
23584 Stream: as severity1
23585
23586 Time: While system is running.
23587
23588 Meaning: The user PERSON.PROJECT was successfully
23589 identified and authenticated on channel CHANNEL.
23590 The process type PROC_TYPE indicates the type of
23591 login and can be either "int" "dmn" "opr" or "Q
23592 N". These correspond to "interactive" "daemon"
23593 "operator" or "absentee" logins. "Q N"
23594 designates the absentee queue. STATE indicates
23595 the state of the login. It can either be
23596 "create" indicating that a process was created
23597 for the user; "connect loop" indicating that the
23598 user was queried as to what he/she wanted to do
23599 with respect to disconnected processes; or some
23600 other value indicating what was done to the user's
23601 disconnected processes.
23602
23603
23604
23605 lg_ctl_.pl1
23606 LOGIN DENIED PERSON.PROJECT PROC_TYPE CHANNEL
23607 REASON
23608
23609
23610 Stream: as severity1
23611
23612 Time: While system is running.
23613
23614 Meaning: An operator login was denied for PERSON.PROJECT on
23615 channel CHANNEL for the reason specified in
23616 REASON. The process type is opr for operator
23617 login attempts.
23618
23619
23620 LOGIN 408 08/21/20 MR12.7^L
23621
23622
23623
23624
23625 daemon_user_manager_.pl1
23626 login: Cannot login NAME.PROJ SOURCE
23627 ERROR_MESSAGE
23628
23629
23630
23631 Stream: as severity1
23632
23633 Time: While system is running.
23634
23635 Meaning: Illegal login arguments have been given when
23636 attempting to log in a daemon user. No action was
23637 taken.
23638
23639 Action: Enter a corrected command.
23640
23641
23642 daemon_user_manager_.pl1
23643 login: ERROR_MESSAGE. creating event channel for
23644 NAME PROJ SOURCE
23645
23646
23647 Stream: as severity2
23648
23649 Time: In response to an operator command.
23650
23651 Meaning: This message indicates a system error in setting
23652 up a daemon user. The daemon cannot be logged in.
23653
23654 Action: Contact the system programming staff. Try again.
23655
23656
23657
23658 daemon_user_manager_.pl1
23659 login: ERROR_MESSAGE. creating proc for NAME
23660 PROJ SOURCE
23661
23662
23663 Stream: as severity2
23664
23665 Time: In response to an operator command.
23666
23667 Meaning: A daemon process cannot be created. This is
23668 probably due to a serious system bug. The daemon
23669 is not logged in.
23670
23671 Action: Contact the system programming staff.
23672
23673
23674 daemon_user_manager_.pl1
23675
23676
23677
23678 login 409 08/21/20 MR12.7^L
23679
23680
23681 login: ERROR_MESSAGE. declaring ev_call_chn for
23682 NAME PROJ SOURCE
23683
23684
23685 Stream: as severity2
23686
23687 Time: In response to an operator command.
23688
23689 Meaning: This message indicates a system error in setting
23690 up a daemon user. The daemon cannot be logged in.
23691
23692 Action: Contact the system programming staff.
23693
23694
23695 daemon_user_manager_.pl1
23696 login: NAME.PROJ already logged in on SOURCE
23697
23698
23699 Stream: as severity1
23700
23701 Time: In response to an operator command.
23702
23703 Meaning: This is the response to the login command if the
23704 source specified by SOURCE is already in use.
23705 Each daemon process must have a different source
23706 name. The daemon user is not logged in. Usually
23707 this message is the result of attempting to
23708 perform an operation that has already been done.
23709
23710 Action: Reissue the command with another source or
23711 continue.
23712
23713
23714 daemon_user_manager_.pl1
23715 login: no login NAME.PROJ SOURCE REASON
23716
23717
23718 Stream: as severity1
23719
23720 Time: In response to an operator command.
23721
23722 Meaning: The operator issued a login NAME PROJ SOURCE
23723 command but the daemon user named cannot be logged
23724 in for the reason given. If REASON is badpers or
23725 bad_proj the NAME or PROJ was probably
23726 misspelled. If REASON is non_daem the user
23727 NAME.PROJ is not authorized to be a daemon user.
23728
23729 Action: Correct the command if misspelled and try to log
23730 in again.
23731
23732
23733
23734
23735
23736 LOGOUT 410 08/21/20 MR12.7^L
23737
23738
23739
23740
23741 lg_ctl_.pl1
23742 LOGOUT PERSON.PROJECT PROC_TYPE CHANNEL REASON
23743
23744
23745 Stream: as severity1
23746
23747 Time: While system is running.
23748
23749 Meaning: The user PERSON.PROJECT on channel CHANNEL with
23750 process type PROC_TYPE either logged out or was
23751 logged out. The reason is specified in REASON.
23752 This user/channel logout did not affect a process.
23753 This can occur for slave dialed channels or
23754 channels dropped from message coordinator service.
23755
23756
23757
23758 daemon_user_manager_.pl1
23759 logout: Entry not found. NAME PROJ SOURCE
23760
23761
23762 Stream: as severity1
23763
23764 Time: In response to an operator logout command.
23765
23766 Meaning: This is a response to an incorrect logout command.
23767 There is no entry in the daemon user table for
23768 NAME.PROJ.
23769
23770 Action: Check the spelling for accuracy and try again.
23771
23772
23773 disk_table_.pl1
23774 lv LVNAME is not mounted
23775
23776
23777 Stream: Initializer process output.
23778
23779 Time: While system is running.
23780
23781 Meaning: The operator issued a dlv LVNAME command but
23782 LVNAME was not mounted.
23783
23784 Action: Enter a corrected command line.
23785
23786
23787 disk_table_.pl1
23788 lv LVNAME mounted
23789
23790
23791 Stream: Initializer process output.
23792
23793
23794 lv 411 08/21/20 MR12.7^L
23795
23796
23797 Time: While system is running.
23798
23799 Meaning: The mounting of LVNAME is complete.
23800
23801 Action: Enter a corrected command line.
23802
23803
23804 lv_request_.pl1
23805 lv_request_: Beginning mount of LV LVNAME for
23806 PERSON.PROJECT.TAG PROCESSID
23807
23808
23809 Stream: as severity 0
23810
23811 Time: When processing a disk mount/demount interrupt.
23812
23813 Meaning: The volumes associated with LVNAME are now being
23814 mounted for the process identified by
23815 PERSON.PROJECT.TAG and PROCESSID.
23816
23817 Action: No operator action is required.
23818
23819
23820 lv_request_.pl1
23821 lv_request_: ERROR_MESSAGE. Masking event calls.
23822
23823
23824 Stream: as severity 2
23825
23826 Time: When processing a disk mount/demount interrupt.
23827
23828 Meaning: An error occurred while attempting to mask event
23829 call wakeups. ERROR_MESSAGE is the text
23830 associated with the error code returned by
23831 ipc_$mask_ev_calls.This indicates a logic error in
23832 the supervisor or CPU or memory hardware
23833 problems.
23834
23835 Action: Contact the system programming staff._sa
23836
23837
23838 lv_request_.pl1
23839 lv_request_: ATTACHED LV LVNAME to
23840 PERSON.PROJECT.TAG PROCESSID.
23841
23842
23843 Stream: as severity 0
23844
23845 Time: When processing a disk mount/demount interrupt.
23846
23847 Meaning: This message records attachment of logical volume
23848 LVNAME to the process identified by
23849 PERSON.PROJECT.TAG and PROCESSID.
23850
23851
23852 lv_request_ 412 08/21/20 MR12.7^L
23853
23854
23855 Action: No operator action is required.
23856
23857
23858 lv_request_.pl1
23859 lv_request_: bad LV attach table index N in
23860 DEMOUNT request
23861
23862
23863 Stream: as severity 2
23864
23865 Time: When processing a disk mount/demount interrupt.
23866
23867 Meaning: The Logical Volume attach table index given in the
23868 event message associated with the mount or demount
23869 interrupt is invalid.This indicates a logic error
23870 in the supervisor or CPU or memory hardware
23871 problems.
23872
23873 Action: Contact the system programming staff._sa
23874
23875
23876 lv_request_.pl1
23877 lv_request_: bad transmission: EVENT_MESSAGE
23878
23879
23880 Stream: as severity 2
23881
23882 Time: When processing a disk mount/demount interrupt.
23883
23884 Meaning: An unexpected EVENT_MESSAGE was received by the
23885 mount/demount interrupt handler.This indicates a
23886 logic error in the supervisor or CPU or memory
23887 hardware problems.
23888
23889 Action: Contact the system programming staff._sa
23890
23891
23892 lv_request_.pl1
23893 lv_request_: Cannot send message to
23894 PERSON.PROJECT.TAG PROCESSID: ADDED_INFO
23895
23896
23897 Stream: as severity 2
23898
23899 Time: When processing a disk mount/demount interrupt.
23900
23901 Meaning: The Initializer is attempting to respond to a
23902 request to mount or demount a logical volume but
23903 is unable to send a wakeup to the user process.
23904 The process may have logged out.This indicates a
23905 logic error in the supervisor or CPU or memory
23906 hardware problems.
23907
23908
23909
23910 lv_request_ 413 08/21/20 MR12.7^L
23911
23912
23913 Action: Contact the system programming staff._sa
23914
23915
23916 lv_request_.pl1
23917 lv_request_: Denied LV LVNAME to
23918 PERSON.PROJECT.TAG PROCESSID
23919
23920
23921 Stream: as severity 0
23922
23923 Time: When dismounting a logical volume.
23924
23925 Meaning: The user process identified by PERSON.PROJECT.TAG
23926 and PROCESSID was waiting to mount a logical
23927 volume LVNAME which is being dismounted by the
23928 operator. The mount request was therefore denied.
23929
23930 Action: No operator action is required.
23931
23932
23933 lv_request_.pl1
23934 lv_request_: DETACHED LV LVNAME from
23935 PERSON.PROJECT.TAG PROCESSID.
23936
23937
23938 Stream: as severity 0
23939
23940 Time: When processing a disk mount/demount interrupt.
23941
23942 Meaning: This message records detachment of logical volume
23943 LVNAME from the process identified by
23944 PERSON.PROJECT.TAG and PROCESSID.
23945
23946 Action: No operator action is required.
23947
23948
23949 lv_request_.pl1
23950 lv_request_: ERROR_MESSAGE. Cannot initialize
23951 logical volume mounting software.
23952
23953
23954
23955 Stream: as severity 2
23956
23957 Time: System Intialization.
23958
23959 Meaning: Initialization of the logical volume attach table
23960 failed. ERROR_MESSAGE is the text associated with
23961 the error code returned by
23962 initializer_mdc_$init_lvat.
23963
23964 Action: Contact the system programming staff._sa
23965
23966
23967
23968 lv_request_ 414 08/21/20 MR12.7^L
23969
23970
23971
23972
23973 lv_request_.pl1
23974 lv_request_: No drives available to mount LV
23975 LVNAME for PERSON.PROJECT.TAG PROCESSID
23976
23977
23978
23979 Stream: as severity 0
23980
23981 Time: When processing a disk mount/demount interrupt.
23982
23983 Meaning: Drives needed to mount the volumes of LVNAME were
23984 in use or deleted. The logical volume could not
23985 be mounted for the process identified by
23986 PERSON.PROJECT.TAG and PROCESSID.
23987
23988 Action: No operator action is required.
23989
23990
23991 lv_request_.pl1
23992 lv_request_: Spurious wakeup EVENT_MESSAGE
23993 received from PERSON.PROJECT.TAG PROCESSID RINGNO
23994
23995
23996
23997 Stream: as severity 0
23998
23999 Time: When processing a disk mount/demount interrupt.
24000
24001 Meaning: A wakeup was received on the lv_request_ interrupt
24002 event channel with event data EVENT_MESSAGE from
24003 the process with PERSON.PROJECT.TAG PROCESSID and
24004 RINGNO. This message is invalid because it did
24005 not come from the Initializer ring 1 environment.
24006
24007 Action: No operator action is required.
24008
24009
24010 lv_request_.pl1
24011 lv_request_: Unexpected condition CONDNAME
24012 occurred.
24013
24014
24015 Stream: as severity 2
24016
24017 Time: When processing a disk mount/demount interrupt.
24018
24019 Meaning: Condition CONDNAME was signalled unexpectedly
24020 during a mount or demount request. An answering
24021 service dump is created to further document the
24022 cause of the error.
24023
24024
24025
24026 lv_request_ 415 08/21/20 MR12.7^L
24027
24028
24029 Action: Contact the system programming staff._sa.
24030
24031
24032 lv_request_communicator_.pl1
24033 lv_request_communicator_: code CCC from wakeup
24034
24035
24036 Stream: BOS Typewriter.
24037
24038 Time: While system is running.
24039
24040 Meaning: A wakeup could not be sent to the initializer
24041 process in order to perform communication about
24042 attachment/detachment of logical volumes.
24043
24044 Action: Contact the system programming staff.
24045
24046
24047 lv_request_communicator_.pl1
24048 lv_request_communicator_: lock ^= processid lvate
24049 PPP
24050
24051
24052 Stream: BOS Typewriter.
24053
24054 Time: In response to a user's detach_lv command
24055
24056 Meaning: A logical volume attachment table entry became
24057 disassociated from a user to whom it had been
24058 assigned. This indicates a logic error in the
24059 supervisor or CPU or memory hardware problems.
24060
24061 Action: Contact the system programming staff. Be prepared
24062 to demount logical volumes manually which might
24063 otherwise have been demounted automatically.
24064
24065
24066
24067 make_branches.pl1
24068 make_branches: bad path name PATH
24069
24070
24071 Stream: BOS Typewriter Crashes system
24072
24073 Time: System Intialization.
24074
24075 Meaning: This indicates a logic error in the supervisor or
24076 CPU or memory hardware problems.
24077
24078 Action: Follow normal recovery procedures. $boot_tape
24079
24080
24081
24082
24083
24084 make_branches 416 08/21/20 MR12.7^L
24085
24086
24087 make_branches.pl1
24088 make_branches: could not delete PATH:
24089 ERROR_MESSAGE
24090
24091
24092 Stream: BOS Typewriter Crashes system
24093
24094 Time: System Intialization.
24095
24096 Meaning: This indicates a logic error in the supervisor or
24097 CPU or memory hardware problems.
24098
24099 Action: Follow normal recovery procedures. $boot_tape
24100
24101
24102
24103 make_branches.pl1
24104 make_branches: delete: could not turn PATH
24105 safety switch off: ERROR_MESSAGE
24106
24107
24108 Stream: BOS Typewriter Crashes system
24109
24110 Time: System Intialization.
24111
24112 Meaning: This indicates a logic error in the supervisor or
24113 CPU or memory hardware problems.
24114
24115 Action: Follow normal recovery procedures. $boot_tape
24116
24117
24118
24119 make_branches.pl1
24120 make_branches: delete: failed to rename
24121
24122
24123 Stream: BOS Typewriter Crashes system
24124
24125 Time: System Intialization.
24126
24127 Meaning: This indicates a logic error in the supervisor or
24128 CPU or memory hardware problems.
24129
24130 Action: Follow normal recovery procedures. $boot_tape
24131
24132
24133
24134 make_branches.pl1
24135 make_branches: delete: renaming NAME to UNIQUE
24136 in DIRNAME
24137
24138
24139 Stream: BOS Typewriter.
24140
24141
24142 make_branches 417 08/21/20 MR12.7^L
24143
24144
24145 Time: System Intialization.
24146
24147 Meaning: A segment which is being loaded from the system
24148 tape encountered a previous copy on a physical
24149 volume which is not now mounted. The old version
24150 of the segment is being renamed so that the new
24151 copy can be loaded.
24152
24153 Action: Note for system programmer action. The system
24154 programmers will want to delete the unique-named
24155 segment.
24156
24157
24158
24159 make_branches.pl1
24160 make_branches: error from append on PATH:
24161 ERROR_MESSAGE
24162
24163
24164 Stream: BOS Typewriter Crashes system
24165
24166 Time: System Intialization.
24167
24168 Meaning: This indicates a logic error in the supervisor or
24169 CPU or memory hardware problems.
24170
24171 Action: Follow normal recovery procedures. $boot_tape
24172
24173
24174
24175 make_branches.pl1
24176 make_branches: error from asd_$replace_sall on
24177 PATH: ERROR_MESSAGE
24178
24179
24180 Stream: BOS Typewriter Crashes system
24181
24182 Time: System Intialization.
24183
24184 Meaning: This indicates a logic error in the supervisor or
24185 CPU or memory hardware problems.
24186
24187 Action: Follow normal recovery procedures. $boot_tape
24188
24189
24190
24191 make_branches.pl1
24192 make_branches: error from chname on PATH:
24193 ERROR_MESSAGE
24194
24195
24196 Stream: BOS Typewriter Crashes system
24197
24198
24199
24200 make_branches 418 08/21/20 MR12.7^L
24201
24202
24203 Time: System Intialization.
24204
24205 Meaning: This indicates a logic error in the supervisor or
24206 CPU or memory hardware problems.
24207
24208 Action: Follow normal recovery procedures. $boot_tape
24209
24210
24211
24212 make_sdw.pl1
24213 make_sdw: no hardcore partitions available.
24214
24215
24216 Stream: BOS Typewriter Crashes system
24217
24218 Time: System Intialization.
24219
24220 Meaning: No hardcore partitions were defined on any of the
24221 packs on the drives specified by the ROOT CONFIG
24222 card. At least the RPV must have a hardcore
24223 partition. Supervisor segments cannot be created.
24224
24225 Action: If this is a cold boot which is most likely the
24226 RPV was initialized without a hardcore partition.
24227 It must be reinitialized. Check the PART HC
24228 CONFIG card one of which must describe the RPV
24229 during a cold boot and reboot. If this is not a
24230 cold boot the RPV has been damaged and volume
24231 recovery must be undertaken.
24232
24233
24234
24235 make_sdw.pl1
24236 make_sdw: no hardcore partitions available.
24237
24238
24239 Stream: BOS Typewriter Crashes system
24240
24241 Time: System Intialization.
24242
24243 Meaning: No hardcore partitions were defined on any of the
24244 packs on the drives specified by the ROOT CONFIG
24245 card. At least the RPV must have a hardcore
24246 partition. Supervisor segments cannot be created.
24247
24248 Action: If this is a cold boot which is most likely the
24249 RPV was initialized without a hardcore partition.
24250 It must be reinitialized. Check the PART HC
24251 CONFIG card one of which must describe the RPV
24252 during a cold boot and reboot. If this is not a
24253 cold boot the RPV has been damaged and volume
24254 recovery must be undertaken.
24255
24256
24257
24258 make_sdw 419 08/21/20 MR12.7^L
24259
24260
24261
24262
24263 make_sdw.pl1
24264 make_sdw: out of hardcore partition for SEGNAME.
24265
24266
24267 Stream: BOS Typewriter Crashes system
24268
24269 Time: System Intialization.
24270
24271 Meaning: In attempting to allocate space for hardcore
24272 segment SEGNAME no more room could be found in
24273 any of the defined hardcore partitions.
24274
24275 Action: If this is a cold boot redefine the hardcore
24276 partition of the RPV to be larger. At least 1000
24277 decimal records is recommended. Change the PART
24278 HC CONFIG card describing the RPV to indicate
24279 this and reboot. If this is not a cold boot
24280 this situation is highly unlikely and indicates
24281 damage to one or more RLV volume labels. Volume
24282 recovery for part or all of the RLV should be
24283 undertaken.
24284
24285
24286
24287 make_sdw.pl1
24288 make_sdw: out of hardcore partition for SEGNAME.
24289
24290
24291 Stream: BOS Typewriter Crashes system
24292
24293 Time: System Intialization.
24294
24295 Meaning: In attempting to allocate space for hardcore
24296 segment SEGNAME no more room could be found in
24297 any of the defined hardcore partitions.
24298
24299 Action: If this is a cold boot redefine the hardcore
24300 partition of the RPV to be larger. At least 1000
24301 decimal records is recommended. Change the PART
24302 HC CONFIG card describing the RPV to indicate
24303 this and reboot. If this is not a cold boot
24304 this situation is highly unlikely and indicates
24305 damage to one or more RLV volume labels. Volume
24306 recovery for part or all of the RLV should be
24307 undertaken.
24308
24309
24310
24311 make_sdw.pl1
24312 make_sdw: XXXk ast pool to small.
24313
24314
24315
24316 make_sdw 420 08/21/20 MR12.7^L
24317
24318
24319 Stream: BOS Typewriter Crashes system
24320
24321 Time: System Intialization.
24322
24323 Meaning: There were not enough AST entries of size XXX k to
24324 allocate the permanent AST entries of the
24325 supervisor.
24326
24327 Action: Increase the number of AST entries of that size
24328 as specified on the SST CONFIG card
24329 substantially and reboot.
24330
24331
24332
24333 make_sdw.pl1
24334 make_sdw: XXXk ast pool to small.
24335
24336
24337 Stream: BOS Typewriter Crashes system
24338
24339 Time: System Intialization.
24340
24341 Meaning: There were not enough AST entries of size XXX k to
24342 allocate the permanent AST entries of the
24343 supervisor.
24344
24345 Action: Increase the number of AST entries of that size
24346 as specified on the SST CONFIG card
24347 substantially and reboot.
24348
24349
24350
24351 make_segs_paged.pl1
24352 make_segs_paged: sorted_segs array overflowed.
24353
24354
24355 Stream: BOS Typewriter Crashes system
24356
24357 Time: System Intialization.
24358
24359 Meaning: The number of paged segments in collection 1 is
24360 larger than the internal buffer in the program
24361 make_segs_paged required to sort them by main
24362 memory address. This indicates an error in
24363 construction of the system i.e. too many header
24364 entries or may be symptomatic of main memory or
24365 CPU hardware problems.
24366
24367 Action: If this recurs revert to a previous system tape.
24368 No emergency shutdown is needed.
24369
24370
24371
24372
24373
24374 makestack 421 08/21/20 MR12.7^L
24375
24376
24377
24378
24379 makestack.pl1
24380 makestack: error appending STACKNAME
24381
24382
24383 Stream: BOS Typewriter Terminates user process
24384
24385 Time: System Intialization. Process/ring
24386 initialization. Just prior to using a new ring.
24387
24388 Meaning: The process directory is probably messed up.
24389
24390 Action: Ignore unless it's the initializer in which case
24391 bring the system back up. If problem persists
24392 contact the system administrator.
24393
24394
24395
24396 makestack.pl1
24397 makestack: error finding DIRNAME>ENAME for
24398 STACKNAME.
24399
24400
24401 Stream: BOS Typewriter Terminates user process
24402
24403 Time: System Intialization. Process/ring
24404 initialization.
24405
24406 Action: Ignore unless it's the initializer in which case
24407 bring the system back up. If problem persists
24408 contact the system administrator.
24409
24410
24411
24412 makestack.pl1
24413 makestack: error from initiate_search_rules.
24414
24415
24416 Stream: BOS Typewriter Terminates user process
24417
24418 Time: Process/ring initialization. Just prior to using
24419 new ring.
24420
24421 Meaning: The default search rules are missing from ahd
24422 active hardcore data. These are usually loaded
24423 by the command set_system_search_rules.
24424
24425 Action: Contact the system programming staff._sa
24426
24427
24428 makestack.pl1
24429
24430
24431
24432 makestack 422 08/21/20 MR12.7^L
24433
24434
24435 makestack: error from set$max_length_ptr on
24436 STACKNAME.
24437
24438
24439 Stream: BOS Typewriter Terminates user process
24440
24441 Time: System Intialization. Process/ring
24442 initialization. Just prior to using a new ring.
24443
24444 Meaning: The process directory is probably messed up.
24445
24446 Action: Ignore unless it's the initializer in which case
24447 bring the system back up. If problem persists
24448 contact the system administrator.
24449
24450
24451
24452 makestack.pl1
24453 makestack: error getting bit count for original
24454 prelinked STACK_NAME
24455
24456
24457 Stream: BOS Typewriter Terminates user process
24458
24459 Time: System Intialization. Process/ring
24460 initialization. Just prior to using a new ring.
24461
24462 Meaning: A directory containing a prelinked subsystem is
24463 probably messed up.
24464
24465 Action: The directory should be prelinked again.
24466
24467
24468 makestack.pl1
24469 makestack: error initiating STACKNAME
24470
24471
24472 Stream: BOS Typewriter Terminates user process
24473
24474 Time: System Intialization. Process/ring
24475 initialization. Just prior to using a new ring.
24476
24477 Action: Ignore unless it's the initializer in which case
24478 bring the system back up. If problem persists
24479 contact the system administrator.
24480
24481
24482
24483 mc_commands_.pl1
24484 mc_commands_$mc_login: Channel XXXX dialed to
24485 Initializer NAME ACCEPTED.
24486
24487
24488
24489
24490 mc_commands_$mc_login 423 08/21/20 MR12.7^L
24491
24492
24493 Stream: as severity 1
24494
24495 Time: In response to a message coordinator dial request.
24496
24497 Meaning: Informative message indicating that a successful
24498 dialin occured on the specified channel by the
24499 named operator.
24500
24501 Action: No operator action is required.
24502
24503
24504 mc_commands_.pl1
24505 mc_commands_$mc_login: Channel XXXX dialed to
24506 Initializer NAME.
24507
24508
24509 Stream: as severity 1
24510
24511 Time: In response to a message coordinator dial request.
24512
24513 Meaning: Informative message indicating that a successful
24514 dialin occured on the specified channel by the
24515 named operator. A subsequent accept is required
24516 by an authenticated operator to complete the
24517 attachment.
24518
24519 Action: No operator action is required.
24520
24521
24522 mc_commands_.pl1
24523 mc_commands_$mc_login: Channel XXXX vchannel
24524 YYYY dialed to Initializer NAME ACCEPTED.
24525
24526
24527 Stream: as severity 1
24528
24529 Time: In response to a message coordinator dial request.
24530
24531 Meaning: Informative message indicating that a successful
24532 dialin occured on the specified channel by the
24533 named operator.
24534
24535 Action: No operator action is required.
24536
24537
24538 mc_commands_.pl1
24539 mc_commands_$mc_login: Channel XXXX vchannel
24540 YYYY dialed to Initializer NAME.
24541
24542
24543 Stream: as severity 1
24544
24545 Time: In response to a message coordinator dial request.
24546
24547
24548 mc_commands_$mc_login 424 08/21/20 MR12.7^L
24549
24550
24551 Meaning: Informative message indicating that a successful
24552 dialin occured on the specified channel by the
24553 named operator. A subsequent accept is required
24554 by an authenticated operator to complete the
24555 attachment.
24556
24557 Action: No operator action is required.
24558
24559
24560 mc_commands_.pl1
24561 mc_commands_$mc_login: error: Channel XXXX
24562 already in use.
24563
24564
24565 Stream: sc error_output
24566
24567 Time: In response to an operator command.
24568
24569 Meaning: The channel specified for MNA attachment is
24570 already in use by the message coordinator.
24571
24572 Action: Enter a corrected command line.
24573
24574
24575 mc_tty_.pl1
24576 mc_tty_: called with bad pointer
24577
24578
24579 Stream: BOS typewriter.
24580
24581 Time: While system is running.
24582
24583 Meaning: This message indicates a bug in system_control_ or
24584 in the Message Coordinator. An illegal signal has
24585 been received by the attached terminal handler in
24586 system_control_; the data pointer that should
24587 point to an entry in the mc_anstbl does not point
24588 to the correct segment. The signal is ignored.
24589
24590 Action: Contact the system programming staff.
24591
24592
24593 mc_tty_.pl1
24594 mc_tty_: called with null ptr
24595
24596
24597 Stream: BOS typewriter.
24598
24599 Time: While system is running.
24600
24601 Meaning: This message indicates a bug in system_control_ or
24602 in the Message Coordinator. An illegal signal has
24603
24604
24605
24606 mc_tty_ 425 08/21/20 MR12.7^L
24607
24608
24609 been received by the attached terminal handler in
24610 system_control_. The signal is ignored.
24611
24612 Action: Contact the system programming staff.
24613
24614
24615 mc_tty_.pl1
24616 mc_tty_: channel CHAN hung up.
24617
24618
24619 Stream: BOS Typewriter sounds beeper
24620
24621 Time: While system is running.
24622
24623 Meaning: This message indicates that an attempt has been
24624 made to read input from a terminal device channel
24625 attached to the Message Coordinator and that the
24626 channel is not active. This condition may be due
24627 to a transient line condition a terminal failure
24628 or a communications line failure. The system
24629 attempts to proceed.
24630
24631 Action: If the terminal is a hardwired device and can be
24632 reconnected do so. If this is a dialup channel
24633 that has failed use the substty or drop commands
24634 to remove the channel.
24635
24636
24637
24638 mc_tty_.pl1
24639 mc_tty_: channel CHAN masked by FNP.
24640
24641
24642 Stream: BOS Typewriter sounds beeper
24643
24644 Time: While system is running.
24645
24646 Meaning: The channel CHAN has just been masked by the
24647 FNP. This is usually due to some hardware problem
24648 with the channel.
24649
24650 Action: Fix the problem before re-using the channel.
24651
24652
24653 mc_tty_.pl1
24654 mc_tty_: Channel CHANNEL vchannel VCHANNEL
24655 received TIMEOUT while awaiting DIALUP wakeup.
24656
24657
24658 Stream: BOS Typewriter.
24659
24660 Time: While system is running.
24661
24662
24663
24664 mc_tty_ 426 08/21/20 MR12.7^L
24665
24666
24667 Meaning: Wakeup was not acted on soon enough by AS.
24668
24669 Action: Contact the system programming staff.
24670
24671
24672 mc_tty_.pl1
24673 mc_tty_: Channel CHANNEL vchannel VCHANNEL
24674 received WAKEUP_TYPE wakeup while awaiting DIALUP.
24675
24676
24677 Stream: BOS Typewriter.
24678
24679 Time: While system is running.
24680
24681 Meaning: Received an unexpected WAKEUP_TYPE wakeup while
24682 waiting for a DIALUP wakeup. Dialup will not
24683 succeed.
24684
24685 Action: Contact the system programming staff.
24686
24687
24688 mc_tty_.pl1
24689 mc_tty_: Channel CHANNEL received TIMEOUT while
24690 awaiting DIALUP wakeup.
24691
24692
24693 Stream: BOS Typewriter.
24694
24695 Time: While system is running.
24696
24697 Meaning: Wakeup was not acted on soon enough by AS.
24698
24699 Action: Contact the system programming staff.
24700
24701
24702 mc_tty_.pl1
24703 mc_tty_: Channel CHANNEL received WAKEUP_TYPE
24704 wakeup while awaiting DIALUP.
24705
24706
24707 Stream: BOS Typewriter.
24708
24709 Time: While system is running.
24710
24711 Meaning: Did not receive a DIALUP wakeup WAKEUP_TYPE when
24712 should have. Recieved an unexpected WAKEUP_TYPE.
24713
24714 Action: Contact the system programming staff.
24715
24716
24717 mc_tty_.pl1
24718 mc_tty_: ERROR_TABLE_MESSAGE Connecting to
24719 CHANNEL vchannel VCHANNEL.
24720
24721
24722 mc_tty_ 427 08/21/20 MR12.7^L
24723
24724
24725 Stream: BOS Typewriter.
24726
24727 Time: While system is running.
24728
24729 Meaning: Error creating an IOCB while attempting to connect
24730 channel CHANNEL as message coordinator terminal.
24731 Channel cannot be accepted as MC terminal. Cannot
24732 attach and open I/O switches.
24733
24734 Action: Contact the system programming staff.
24735
24736
24737 mc_tty_.pl1
24738 mc_tty_: ERROR_TABLE_MESSAGE Connecting to
24739 CHANNEL.
24740
24741
24742 Stream: BOS Typewriter.
24743
24744 Time: While system is running.
24745
24746 Meaning: Error creating an IOCB while attempting to connect
24747 channel CHANNEL as message coordinator terminal.
24748 Channel cannot be accepted as MC terminal. Cannot
24749 attach and open I/O switches.
24750
24751 Action: Contact the system programming staff.
24752
24753
24754 mc_tty_.pl1
24755 mc_tty_: ERROR_TABLE_MESSAGE Could not get
24756 channel CHAN back from MC.
24757
24758
24759 Stream: BOS Typewriter.
24760
24761 Time: While system is running.
24762
24763 Meaning: An error described by ERROR_TABLE_MESSAGE was
24764 returned from astty_$tty_event while trying to
24765 give channel CHAN back to the AS after a hangup.
24766
24767 Action: Contact the system programming staff.
24768
24769
24770 mc_tty_.pl1
24771 mc_tty_: ERROR_TABLE_MESSAGE Could not notify
24772 answering service of new login channel CHAN.
24773
24774
24775
24776 Stream: BOS Typewriter.
24777
24778
24779
24780 mc_tty_ 428 08/21/20 MR12.7^L
24781
24782
24783 Time: While system is running.
24784
24785 Meaning: An error described by ERROR_TABLE_MESSAGE was
24786 returned from hcs_$wakeup while trying to notify
24787 the AS about the new login channel CHAN after a
24788 hangup.
24789
24790 Action: Contact the system programming staff.
24791
24792
24793 mc_tty_.pl1
24794 mc_tty_: ERROR_TABLE_MESSAGE Could not remove
24795 CHAN from MC use.
24796
24797
24798 Stream: BOS Typewriter.
24799
24800 Time: While system is running.
24801
24802 Meaning: An error described by ERROR_TABLE_MESSAGE was
24803 returned from mc_commands_$remove_tty while tring
24804 to remove channel CHAN from MC service after a
24805 hangup.
24806
24807 Action: Contact the system programming staff.
24808
24809
24810 mc_tty_.pl1
24811 mc_tty_: ERROR_TABLE_MESSAGE Failed to set
24812 terminal type for CHAN.
24813
24814
24815 Stream: BOS Typewriter.
24816
24817 Time: While system is running.
24818
24819 Meaning: An error described ty ERROR_TABLE_MESSAGE was
24820 returned while trying to set the terminal type on
24821 channel CHAN.
24822
24823 Action: Depending on the error it may be ignored or the
24824 channel may be hungup. If the channel is hungup
24825 an attempt should be made to fix the error before
24826 connecting the terminal again.
24827
24828
24829
24830 mc_tty_.pl1
24831 mc_tty_: ERROR_TABLE_MESSAGE wru failed for CHAN.
24832
24833
24834 Stream: BOS Typewriter.
24835
24836
24837
24838 mc_tty_ 429 08/21/20 MR12.7^L
24839
24840
24841 Time: While system is running.
24842
24843 Meaning: The CDT entry for channel CHAN requires an
24844 answerback but an error was returned while trying
24845 to read it. The returned error is described by
24846 ERROR_TABLE_MESSAGE.
24847
24848 Action: Verify that the channel is configured correctly in
24849 the CDT.
24850
24851
24852 mc_tty_.pl1
24853 mc_tty_: Event sent from incorrect ring. event
24854 channel = N event message = M event sender = S
24855 device signal = D ring = R event data ptr = P
24856
24857
24858
24859 Stream: BOS Typewriter.
24860
24861 Time: While system is running.
24862
24863 Meaning: An event was sent from a ring higher than the
24864 specified MNA ring 2.
24865
24866 Action: Contact the system programming staff.
24867
24868
24869 mc_tty_.pl1
24870 mc_tty_: Invalid argument. Invalid DSA wakeup
24871 event type TYPE.
24872
24873
24874 Stream: as severity 0
24875
24876 Time: While system is running.
24877
24878 Meaning: A DSA wakeup event type TYPE was received which is
24879 out of the range of known event types. The wakeup
24880 was ignored.
24881
24882 Action: No operator action is required.
24883
24884
24885 mc_tty_.pl1
24886 mc_tty_: Invalid argument. Invalid MCS wakeup
24887 event type TYPE.
24888
24889
24890 Stream: as severity 0
24891
24892 Time: While system is running.
24893
24894
24895
24896 mc_tty_ 430 08/21/20 MR12.7^L
24897
24898
24899 Meaning: An MCS wakeup event type TYPE was received which
24900 is out of the range of known event types. The
24901 wakeup was ignored.
24902
24903 Action: No operator action is required.
24904
24905
24906 mc_tty_.pl1
24907 mc_tty_: Invalid argument. Unexpected DSA wakeup
24908 event type TYPE.
24909
24910
24911 Stream: as severity 0
24912
24913 Time: While system is running.
24914
24915 Meaning: A known DSA wakeup event type TYPE was received
24916 but was not expected for a message coordinator
24917 terminal. The wakeup was ignored.
24918
24919 Action: No operator action is required.
24920
24921
24922 mc_tty_.pl1
24923 mc_tty_: Invalid argument. Unexpected MCS wakeup
24924 event type TYPE.
24925
24926
24927 Stream: as severity 0
24928
24929 Time: While system is running.
24930
24931 Meaning: A known MCS wakeup event type TYPE was received
24932 but was not expected for a message coordinator
24933 terminal. The wakeup was ignored.
24934
24935
24936
24937 mc_tty_.pl1
24938 mc_tty_: Invalid argument. Unexpected network
24939 type TYPE in event message.
24940
24941
24942 Stream: as severity 0
24943
24944 Time: While system is running.
24945
24946 Meaning: An unknown network ident in wakeup event message
24947 was received. The wakeup was ignored.
24948
24949 Action: No operator action is required.
24950
24951
24952
24953
24954 mc_tty_ 431 08/21/20 MR12.7^L
24955
24956
24957
24958
24959 mc_tty_.pl1
24960 mc_tty_: Line CHAN hung up.
24961
24962
24963 Stream: as severity 0
24964
24965 Time: While system is running.
24966
24967 Meaning: Channel CHAN has been hungup during a system
24968 shutdown.
24969
24970 Action: No operator action is required.
24971
24972
24973 mc_tty_.pl1
24974 mc_tty_: No default ttp for CHANNEL line LINE
24975 baud BAUD.
24976
24977
24978 Stream: BOS Typewriter sounds beeper
24979
24980 Time: While system is running.
24981
24982 Meaning: Could not get default terminal type for terminal
24983 on CHANNEL which has a line type of LINE. Hangup
24984 will follow.
24985
24986 Action: Contact the system programming staff.
24987
24988
24989 mc_tty_.pl1
24990 mc_tty_: sc_stat_$mc_ansp is null
24991
24992
24993 Stream: BOS Typewriter.
24994
24995 Time: While system is running.
24996
24997 Meaning: This message indicates a bug in system_control_ or
24998 in the Message Coordinator. A signal has been
24999 received by the attached terminal handler in
25000 system_control_ but the signal cannot be handled
25001 because the mc_anstbl cannot be located. The
25002 signal is ignored.
25003
25004 Action: Contact the system programming staff.
25005
25006
25007 mca_attach_.pl1
25008 MCA: IO not released on DEVICE ipcNN in IMU-X
25009 PERSON.PROJ.T.
25010
25011
25012 MCA 432 08/21/20 MR12.7^L
25013
25014
25015 Stream: $warn
25016
25017 Time: While system is running.
25018
25019 Meaning: The user is detaching the IPC but does not want
25020 the IO to be resumed.
25021
25022 Action: This is normally because the IPC is defective or
25023 no longer capable of handling normal I/O.
25024
25025
25026
25027 mca_attach_.pl1
25028 MCA: IO released on DEVICE ipcNN in IMU-X
25029 PERSON.PROJ.T.
25030
25031
25032 Stream: Logged in SYSERR log.
25033
25034 Time: While system is running.
25035
25036 Meaning: This message is stating that the normal flow of
25037 I/O for this device is being resumed.
25038
25039 Action: No operator action is required.
25040
25041
25042 mca_attach_.pl1
25043 MCA: IO suspended on DEVICE ipcNN in IMU-X for
25044 PERSON.PROJ.T.
25045
25046
25047 Stream: Logged in SYSERR log.
25048
25049 Time: While system is running.
25050
25051 Meaning: This message is stating that the normal flow of
25052 I/O for this device is being suspended. This
25053 allows the user to stop or alter/reload an IPC
25054 without affecting the system.
25055
25056 Action: No operator action is required.
25057
25058
25059 mcs_timer.pl1
25060 mcs_timer: Cannot get space to set timer NNN for
25061 devxsubchan DDDSSS.
25062
25063
25064 Stream: Logged in SYSERR log.
25065
25066 Time: While system is running.
25067
25068
25069
25070 mcs_timer 433 08/21/20 MR12.7^L
25071
25072
25073 Meaning: An attempt was made to set an MCS timer with the
25074 specified timer ID but it was not possible to
25075 allocate the necessary space in tty_buf to hold
25076 timer data block. The call is ignored.
25077
25078 Action: Contact the system programming staff.
25079
25080
25081 mcs_timer.pl1
25082 mcs_timer: Channel not locked by this process.
25083 Devx = DDDD.
25084
25085
25086 Stream: BOS Typewriter Crashes system
25087
25088 Time: While system is running.
25089
25090 Meaning: A process called to perform an MCS timer
25091 operation but the channel it specified devx
25092 DDDD was not locked by the calling process. by
25093 the calling process.
25094
25095 Action: Contact the system programming staff.
25096
25097
25098 mcs_timer.pl1
25099 mcs_timer: Duplicate timer ID. Cannot set timer
25100 NNN for devxsubchan DDDSSS.
25101
25102
25103 Stream: Logged in SYSERR log.
25104
25105 Time: While system is running.
25106
25107 Meaning: An attempt was made to set an MCS timer with the
25108 specified timer ID but the channel already had an
25109 outstanding timer or queued timer interrupt with
25110 that ID. The call is ignored.
25111
25112 Action: Contact the system programming staff.
25113
25114
25115 mcs_timer.pl1
25116 mcs_timer: Timer lock already locked to this
25117 process.
25118
25119
25120 Stream: BOS Typewriter Crashes system
25121
25122 Time: While system is running.
25123
25124 Meaning: A process that had the MCS timer lock locked tried
25125 to lock it again.
25126
25127
25128 mcs_timer 434 08/21/20 MR12.7^L
25129
25130
25131 Action: Contact the system programming staff.
25132
25133
25134 mcs_timer.pl1
25135 mcs_timer: Timer lock not locked by this process.
25136
25137
25138 Stream: BOS Typewriter Crashes system
25139
25140 Time: While system is running.
25141
25142 Meaning: A process called to unlock the MCS timer lock but
25143 did not have it locked.
25144
25145 Action: Contact the system programming staff.
25146
25147
25148 mcs_timer.pl1
25149 mcs_timer: Timer not found. Cannot OOOOO timer
25150 NNN for devxsubchan DDDSSS.
25151
25152
25153 Stream: Logged in SYSERR log.
25154
25155 Time: While system is running.
25156
25157 Meaning: An attempt was made to perform operation OOOOO
25158 reset or change on an MCS timer when no timer or
25159 queued timer interrupt with the specified ID could
25160 be found for the requesting channel. The call is
25161 ignored.
25162
25163 Action: Contact the system programming staff.
25164
25165
25166 mdc_create_.pl1
25167 mdc_create_$delete: No MDCS for DIRNAME.
25168
25169
25170 Stream: Logged in SYSERR log.
25171
25172 Time: While system is running.
25173
25174 Meaning: When deleting master directory DIRNAME the master
25175 directory control segment MDCS could not found.
25176 The directory was deleted anyway.
25177
25178 Action: No operator action is required.
25179
25180
25181 mdc_create_.pl1
25182 mdc_create_$delete: TRP for DIRNAME on LVNAME
25183 negative.
25184
25185
25186 mdc_create_$delete 435 08/21/20 MR12.7^L
25187
25188
25189 Stream: Logged in SYSERR log.
25190
25191 Time: While system is running.
25192
25193 Meaning: While deleting master directory DIRNAME an
25194 invalid negative time-record product was found.
25195 The invalid number has been ignored but volume
25196 accounting data may have been lost.
25197
25198 Action: No operator action is required.
25199
25200
25201 mdc_lock_.pl1
25202 mdc_lock_$lock: LOCK ERROR MESSAGE.
25203
25204
25205 Stream: Logged in SYSERR log.
25206
25207 Time: While system is running.
25208
25209 Meaning: A master directory operation failed because of a
25210 problem with the master directory control lock.
25211
25212 Action: No operator action is required.
25213
25214
25215 mdc_lock_.pl1
25216 mdc_lock_$mdc_data_init: Unable to create
25217 PATHNAME. REASON.
25218
25219
25220 Stream: BOS Typewriter.
25221
25222 Time: System Intialization.
25223
25224 Meaning: Master directory control was unable to create the
25225 segment PATHNAME to be used for the master
25226 directory control lock for the REASON given.
25227 Subsequent master directory control operations may
25228 fail.
25229
25230 Action: ignore
25231
25232
25233 mdc_lock_.pl1
25234 mdc_lock_$mdc_data_init: Unable to reclassify
25235 PATHNAME. REASON.
25236
25237
25238 Stream: BOS Typewriter.
25239
25240 Time: System Intialization.
25241
25242
25243
25244 mdc_lock_$mdc_data_init 436 08/21/20 MR12.7^L
25245
25246
25247 Meaning: Master directory control was unable to reclassify
25248 the segment PATHNAME to its proper access class
25249 for the REASON given. This segment is to be used
25250 for the master directory control lock. Subsequent
25251 master directory control operations may fail.
25252
25253
25254
25255 mdc_lock_.pl1
25256 mdc_lock_$mdc_data_init: Unable to truncate
25257 PATHNAME. REASON.
25258
25259
25260 Stream: BOS Typewriter.
25261
25262 Time: System Intialization.
25263
25264 Meaning: Master directory control was unable to truncate
25265 the segment PATHNAME for the REASON given. This
25266 segment is to be used for the master directory
25267 control lock. Subsequent master directory control
25268 operations may fail.
25269
25270 Action: No operator action is required.
25271
25272
25273 mdc_lock_.pl1
25274 mdc_lock_$unlock: LOCK ERROR MESSAGE.
25275
25276
25277 Stream: Logged in SYSERR log.
25278
25279 Time: While system is running.
25280
25281 Meaning: At the completion of a master directory control
25282 operation some error occured unlocking the master
25283 directory control lock.
25284
25285 Action: No operator action is required.
25286
25287
25288 mdc_lock_.pl1
25289 mdc_lock_: Unable to initiate PATHNAME. REASON.
25290
25291
25292 Stream: Logged in SYSERR log.
25293
25294 Time: While system is running.
25295
25296 Meaning: Master directory control was unable to initiate
25297 PATHNAME which contains the master directory
25298 control lock because of REASON. The master
25299
25300
25301
25302 mdc_lock_ 437 08/21/20 MR12.7^L
25303
25304
25305 directory control operation requested was not
25306 performed.
25307
25308 Action: No operator action is required.
25309
25310
25311 mdc_repair_.pl1
25312 mdc_repair_$register_mdir: DIRNAME registered on
25313 LVNAME quota=N.
25314
25315
25316 Stream: Logged in SYSERR log.
25317
25318 Time: While system is running.
25319
25320 Meaning: The master directory DIRNAME has been found which
25321 had not been recorded in the MDCS for volume
25322 LVNAME. The master directory has been registered
25323 and the quota of N has been charged to the
25324 Initializer.SysDaemon quota account. This problem
25325 may have been caused by the loss and subsequent
25326 retreival of the master directory control segment
25327 or by retreving a master directory. This message
25328 can only appear as a result of a register_mdir
25329 command performed by a system administrator.
25330
25331 Action: No operator action is required.
25332
25333
25334 mdc_repair_.pl1
25335 mdc_repair_$register_mdir: Quota for DIRNAME on
25336 LVNAME changed from OLD to NEW.
25337
25338
25339 Stream: Logged in SYSERR log.
25340
25341 Time: While system is running.
25342
25343 Meaning: The quota of master directory DIRNAME was found be
25344 different from the quota recorded in the MDCS.
25345 The real quota is assumed to be correct and the
25346 MDCS is updated to reflect this quota. This may
25347 happen if a set_quota command had been used on a
25348 master directory. This message can only appear as
25349 a result of a register_mdir command performed by a
25350 system administrator.
25351
25352 Action: No operator action is required.
25353
25354
25355 mdc_repair_.pl1
25356 mdc_repair_$register_mdir: Quota of N reported by
25357 ring 0 for DIRNAME on LVNAME. 1 assumed.
25358
25359
25360 mdc_repair_$register_mdir 438 08/21/20 MR12.7^L
25361
25362
25363 Stream: Logged in SYSERR log.
25364
25365 Time: While system is running.
25366
25367 Meaning: The master directory DIRNAME for volume LVNAME has
25368 been found to have an invalid quota. The quota
25369 has been assumed to be 1. The message can only
25370 appear as a result of a register_mdir command
25371 performed by a system administrator.
25372
25373 Action: No operator action is required.
25374
25375
25376 mdc_repair_.pl1
25377 mdc_repair_:validate_uidpaths: Master directory
25378 entry with bad uidpath deleted from LVNAME.
25379 PARTIAL-PATHNAME.
25380
25381
25382 Stream: Logged in SYSERR log.
25383
25384 Time: While system is running.
25385
25386 Meaning: The master directory control segment for LVNAME
25387 contains an entry for a mastr directory which no
25388 longer exists. The entry has been deleted and the
25389 quota is returned to the account from which it was
25390 drawn. This can happen if a master directory
25391 control segment has been lost and retreived or if
25392 a mastr directory has been lost.
25393
25394 Action: No operator action is required.
25395
25396
25397 mos_memory_check.pl1
25398 mos_memory_check: EDAC error on mem X store Y.
25399
25400
25401 Stream: $warn
25402
25403 Time: While system is running.
25404
25405 Meaning: MOS memory polling has found that the maintenance
25406 register in the system controller shows a nonzero
25407 syndrome. The data is logged for use by HEALS or
25408 mos_edac_summary. Only the first occurrence of
25409 this error is printed online for each box.
25410
25411 Action: No operator action is required.
25412
25413
25414 mos_memory_check.pl1
25415 mos_memory_check: Lock error.
25416
25417
25418 mos_memory_check 439 08/21/20 MR12.7^L
25419
25420
25421 Stream: BOS Typewriter.
25422
25423 Time: While system is running.
25424
25425 Meaning: After checking the memory controllers for errors
25426 the program mos_memory check attempted to unlock
25427 the reconfiguration lock and found it unlocked.
25428 The system continues to run.
25429
25430 Action: No operator action is required.
25431
25432
25433 mos_memory_check.pl1
25434 mos_memory_check: MOS polling disabled
25435
25436
25437 Stream: Logged in SYSERR log.
25438
25439 Time: While system is running.
25440
25441 Meaning: A system administrator has disabled MOS memory
25442 polling.
25443
25444 Action: No operator action is required.
25445
25446
25447 mos_memory_check.pl1
25448 mos_memory_check: MOS polling time NN minutes.
25449
25450
25451 Stream: Logged in SYSERR log.
25452
25453 Time: While system is running.
25454
25455 Meaning: A system administrator has set the MOS memory
25456 polling time to NN minutes.
25457
25458 Action: No operator action is required.
25459
25460
25461 disk_table_.pl1
25462 mount of LVNAME stopped
25463
25464
25465 Stream: Initializer process output.
25466
25467 Time: While system is running.
25468
25469 Meaning: The operator issued a dlv LVNAME command for a
25470 volume which was being mounted.
25471
25472 Action: No operator action is required.
25473
25474
25475
25476 mount 440 08/21/20 MR12.7^L
25477
25478
25479
25480
25481 disk_table_.pl1
25482 mount pack PVNAME on DRIVE
25483
25484
25485 Stream: Initializer process output.
25486
25487 Time: While system is running.
25488
25489 Meaning: This message occurs when the system is attempting
25490 to mount a logical volume and finds one or more
25491 physical volumes have not been made known via the
25492 add_vol command. If the pack is a non-demountable
25493 volume a DRIVE will only be printed if the system
25494 knows the drive on which the pack was previously
25495 mounted. If the pack is a demountable volume
25496 then a DRIVE will be printed always. If the
25497 system does not know the drive on which the pack
25498 was last mounted then it chooses a drive where
25499 the pack should be mounted and prints this
25500 message.
25501
25502 Action: Mount the pack specified. If it is not convenient
25503 to use the specified DRIVE use another. Then use
25504 the add_vol command to tell the system that the
25505 physical volume has been mounted. When all packs
25506 have been mounted and either accepted via add_vol
25507 or are on the drives where the system called for
25508 them issue a "alv LVNAME" command to accept them
25509 all at once. The logical volume will be put in
25510 use.
25511
25512
25513
25514 move_non_perm_wired_segs.pl1
25515 move_non_perm_wired_segs: mem TAG on in config
25516 deck but port off.
25517
25518
25519 Stream: BOS Typewriter Crashes system
25520
25521 Time: System Intialization.
25522
25523 Meaning: Memory controller TAG is specified ON on its MEM
25524 card but its port is disabled on the bootload
25525 CPU.
25526
25527 Action: Enable the port or set the MEM OFF and reboot.
25528
25529
25530 move_non_perm_wired_segs.pl1
25531
25532
25533
25534 move_non_perm_wired_segs 441 08/21/20 MR12.7^L
25535
25536
25537 move_non_perm_wired_segs: mem TAG size nK in
25538 config mK on port.
25539
25540
25541 Stream: BOS Typewriter Crashes system
25542
25543 Time: System Intialization.
25544
25545 Meaning: Memory controller TAG has a size of nK in the
25546 config deck but the address assignment and port
25547 size switches specify mK.
25548
25549 Action: Fix the switches or config deck and reboot.
25550
25551
25552 move_non_perm_wired_segs.pl1
25553 move_non_perm_wired_segs: no main memory
25554 configured.
25555
25556
25557 Stream: BOS Typewriter Crashes system
25558
25559 Time: System Intialization.
25560
25561 Meaning: No MEM cards were found ON in the config deck.
25562
25563 Action: Fix the config deck and reboot.
25564
25565
25566 mrd_util_.pl1
25567 mrd_util_$ENTRY: CALL_CODE MESSAGE in ENAME
25568
25569
25570 Stream: BOS Typewriter sounds beeper
25571
25572 Time: While system is running.
25573
25574 Meaning: A problem has been discovered in the threading of
25575 the message coordinator segment ENAME. CALL_CODE
25576 identifies the particular call that failed and
25577 MESSAGE identifies the reason for the failure.
25578 Entry identifies the entrypoint in mrd_util_ that
25579 was called. All pending messages in ENAME are
25580 discarded. Debugging information is written into
25581 ENAME and may be displayed using the
25582 dump_syscon_mseg tool. The message coordinator
25583 recovers from these errors and continues possibly
25584 with the loss of some input or output. If ENAME
25585 is mc.message some daemon output may be lost. If
25586 ENAME is anything else some input to that daemon
25587 may be lost and the operator should communicate
25588 with the daemon immediately in case this has
25589
25590
25591
25592 mrd_util_$ENTRY 442 08/21/20 MR12.7^L
25593
25594
25595 happened. This indicates a logic error in the
25596 supervisor or CPU or memory hardware problems.
25597
25598 Action: Contact the system programming staff. Save all
25599 console and message coordinator terminal output.
25600
25601
25602
25603 mrd_util_.pl1
25604 mrd_util_$ENTRY: had to blast lock in ENAME
25605
25606
25607 Stream: BOS Typewriter sounds beeper
25608
25609 Time: While system is running.
25610
25611 Meaning: The lock in the message coordinator segment ENAME
25612 did not unlock within thirty seconds. The lock is
25613 reset forcibly and locked to the calling process.
25614 ENTRY identifies the entrypoint in mrd_util_ that
25615 was called. Debugging information is written into
25616 ENAME and may be displayed using the
25617 dump_syscon_mseg tool. Further errors may result
25618 if the process that originally locked the segment
25619 left it in an inconsistent state or if it later
25620 starts up again.
25621
25622 Action: Contact the system programming staff. Save all
25623 console and message coordinator terminal output.
25624
25625
25626
25627 mrd_util_.pl1
25628 mrd_util_$ENTRY: inconsistent threads in ENAME
25629
25630
25631 Stream: BOS Typewriter sounds beeper
25632
25633 Time: While system is running.
25634
25635 Meaning: While trying to add unused blocks to the free
25636 chain in the message coordinator segment ENAME an
25637 error was discovered. ENTRY identifies the
25638 entrypoint in mrd_util_ that was called.
25639 Debugging information is written into ENAME and
25640 may be displayed using the dump_syscon_mseg tool.
25641 This indicates a logic error in the supervisor or
25642 CPU or memory hardware problems.
25643
25644 Action: Contact the system programming staff. Save all
25645 console and message coordinator terminal output.
25646
25647
25648
25649
25650 mrd_util_$ENTRY 443 08/21/20 MR12.7^L
25651
25652
25653
25654
25655 mrd_util_.pl1
25656 mrd_util_$ENTRY: killing process due to mylock
25657 error in ENAME
25658
25659
25660 Stream: BOS Typewriter Terminates user process
25661
25662 Time: While system is running.
25663
25664 Meaning: While trying to lock the message coordinator
25665 segment ENAME the lock was found to already be
25666 locked to the calling process. ENTRY identifies
25667 the entrypoint in mrd_util_ that was called.
25668 Debugging information is written into ENAME and
25669 may be displayed using the dump_syscon_mseg tool.
25670 This indicates a logic error in the supervisor or
25671 CPU or memory hardware problems.
25672
25673 Action: Contact the system programming staff. Save all
25674 console and message coordinator terminal output.
25675
25676
25677
25678 mrd_util_.pl1
25679 mrd_util_$ENTRY: reset bad lock in ENAME
25680
25681
25682 Stream: BOS Typewriter sounds beeper
25683
25684 Time: While system is running.
25685
25686 Meaning: The message coordinator segment ENAME was locked
25687 to a nonexistent process. The lock is reset and
25688 locked to the calling process. ENTRY identifies
25689 the entrypoint in mrd_util_ that was called.
25690 Debugging information is written into ENAME and
25691 may be displayed using the dump_syscon_mseg tool.
25692 Further errors may be reported if ENAME was in an
25693 inconsistent state.
25694
25695 Action: Contact the system programming staff. Save all
25696 console and message coordinator terminal output.
25697
25698
25699
25700 mseg_index_.pl1
25701 mseg_$initiate_seg: The ACL for PATH is
25702 inconsistent -- USER_ID does not have "rw" access.
25703
25704
25705
25706
25707
25708 mseg_$initiate_seg 444 08/21/20 MR12.7^L
25709
25710
25711 Stream: Logged in SYSERR log.
25712
25713 Time: While system is running.
25714
25715 Meaning: This indicates a logic error in the supervisor or
25716 CPU or memory hardware problems. For proper
25717 operation of the message segment primitives all
25718 ACL terms of a message segment or mailbox must
25719 specify "rw" access to the segment when running in
25720 ring 1. One or more ACL terms for the segment
25721 PATH do not provide the required access. USER_ID
25722 identifies one of the user whose access to the
25723 segment is incorrect.
25724
25725 Action: Contact the system programming staff.
25726
25727
25728 mseg_utils_.pl1
25729 mseg_$OPERATION: Beginning salvage of PATH for
25730 USER_ID. REASON
25731
25732
25733 Stream: Logged in SYSERR log.
25734
25735 Time: While system is running.
25736
25737 Meaning: The message segment primitives operation OPERATION
25738 detected an internal inconsistency in the message
25739 segment or mailbox PATH and has requested that the
25740 segment be salvaged. REASON provides an
25741 explanation of why the operation invoked the
25742 salvager.
25743
25744 Action: No operator action is required.
25745
25746
25747 mseg_utils_.pl1
25748 mseg_$OPERATION: Completed salvage of PATH for
25749 USER_ID. N out of M possible messages
25750 recovered.
25751
25752
25753
25754 Stream: Logged in SYSERR log.
25755
25756 Time: While system is running.
25757
25758 Meaning: The salvage of the message segment or mailbox PATH
25759 requested by the message segment primitives
25760 operation OPERATION has been completed. Of the M
25761 messages which might have been in the segment
25762 only N could be recovered; the others have been
25763 deleted. If all possible messages were recovered
25764
25765
25766 mseg_$OPERATION 445 08/21/20 MR12.7^L
25767
25768
25769 the "out of M possible" phrase is omitted from the
25770 message.
25771
25772 Action: Contact the system programming staff._sa The
25773 administrator may wish to notify the owner of the
25774 segment that some of his messages have been lost.
25775
25776
25777
25778 mseg_utils_.pl1
25779 mseg_$OPERATION: Unable to salvage PATH for
25780 USER_ID. REASON
25781
25782
25783 Stream: Logged in SYSERR log.
25784
25785 Time: While system is running.
25786
25787 Meaning: This indicates a logic error in the supervisor or
25788 CPU or memory hardware problems. OPERATION
25789 identifies the message segment primitives
25790 operation which provoked the attempted salvage.
25791 PATH is the pathname of the message segment or
25792 mailbox which could not be salvaged. REASON
25793 provides additional information about the failure
25794 of the attempted salvage.
25795
25796 Action: Contact the system programming staff.
25797
25798
25799 mseg_utils_.pl1
25800 mseg_$OPERATION: Unable to salvage PATH for
25801 USER_ID. Rebuilding the contents of the message
25802 segment -- Record quota overflow.
25803
25804
25805
25806 Stream: Logged in SYSERR log.
25807
25808 Time: While system is running.
25809
25810 Meaning: The salvage of the message segment or mailbox PATH
25811 requested by the message segment primitives
25812 operation OPERATION failed due to a lack of quota.
25813 The segment in question will remain inaccessible
25814 until the salvage can be successfully completed.
25815
25816 Action: Contact the system programming staff._sa In order
25817 to make the message segment or mailbox accessible
25818 again the administrator must increase the quota
25819 available to the segment to any value greater than
25820 the current length of the segment. The
25821 administrator should then attempt to use the
25822
25823
25824 mseg_$OPERATION 446 08/21/20 MR12.7^L
25825
25826
25827 segment to allow the salvager to be run to
25828 completion.
25829
25830
25831
25832 mseg_utils_.pl1
25833 mseg_$OPERATION: Unable to salvage PTR pathname
25834 unknown for USER_ID. Call to
25835 hcs_$get_access_info_seg failed. REASON
25836
25837
25838
25839 Stream: Logged in SYSERR log.
25840
25841 Time: While system is running.
25842
25843 Meaning: This indicates a logic error in the supervisor or
25844 CPU or memory hardware problems. OPERATION
25845 identifies the message segment primitives
25846 operation which provoked the attempted salvage.
25847 PTR is USER_ID's pointer to the message segment or
25848 mailbox which could not be salvaged. REASON
25849 provides additional information about the failure
25850 of the call to hcs_$get_access_info_seg.
25851
25852 Action: Contact the system programming staff.
25853
25854
25855 mseg_utils_.pl1
25856 mseg_$OPERATION: Unable to upgrade PATH from
25857 version N to version 5 for USER_ID. REASON
25858
25859
25860
25861 Stream: Logged in SYSERR log.
25862
25863 Time: While system is running.
25864
25865 Meaning: This indicates a logic error in the supervisor or
25866 CPU or memory hardware problems. OPERATION
25867 identifies the message segment primitives
25868 operation which required that the segment be
25869 upgraded. PATH is the pathname of the message
25870 segment or mailbox which could not be upgraded.
25871 REASON provides additional information about the
25872 failure of the attempted upgrade.
25873
25874 Action: Contact the system programming staff.
25875
25876
25877 mseg_utils_.pl1
25878 mseg_$OPERATION: Unable to upgrade PTR pathname
25879
25880
25881
25882 mseg_$OPERATION 447 08/21/20 MR12.7^L
25883
25884
25885 unknown from version N to version 5 for USER_ID.
25886 Call to hcs_$get_access_info_seg failed. REASON
25887
25888
25889
25890 Stream: Logged in SYSERR log.
25891
25892 Time: While system is running.
25893
25894 Meaning: This indicates a logic error in the supervisor or
25895 CPU or memory hardware problems. OPERATION
25896 identifies the message segment primitives
25897 operation which required that the segment be
25898 upgraded. PTR is USER_ID's pointer to the message
25899 segment or mailbox which could not be upgraded.
25900 REASON provides additional information about the
25901 failure of the call to hcs_$get_access_info_seg.
25902
25903 Action: Contact the system programming staff.
25904
25905
25906 mseg_utils_.pl1
25907 mseg_$OPERATION: Upgraded PATH from version N to
25908 version 5 for USER_ID. M messages were deleted.
25909
25910
25911
25912 Stream: Logged in SYSERR log.
25913
25914 Time: While system is running.
25915
25916 Meaning: The format of the message segment or mailbox PATH
25917 was upgraded from the old format known as "version
25918 N" to the latest format. However M messages in
25919 the segment could not be upgraded to the current
25920 format because there was no room for them in the
25921 segment. As a consequence these messages were
25922 deleted. OPERATION identifies the message segment
25923 primitives operation which required that the
25924 segment be upgraded.
25925
25926 Action: Contact the system programming staff._sa The
25927 administrator may wish to notify the owner of the
25928 segment that some of his messages have been lost.
25929
25930
25931
25932 syserr_real.pl1
25933 Multics not in operation; control process:
25934 PERSON.PROJ.
25935
25936
25937 Stream: BOS Typewriter Crashes system
25938
25939
25940 Multics not in operation; contro^H4l^H48process 08/21/20 MR12.7^L
25941
25942
25943 Time: While system is running.
25944
25945 Meaning: This message is always preceded by an explanation
25946 of the error which crashed the system.
25947
25948 Action: Follow normal recovery procedures.
25949
25950
25951 system_startup_.pl1
25952 Multics SYSID: DATE TIME
25953
25954
25955 Stream: BOS Typewriter.
25956
25957 Time: System Intialization.
25958
25959 Meaning: This is the first message that will be typed when
25960 the system is started up. It indicates that the
25961 Initializer process is ready to go. The system ID
25962 on the tape is SYSID.
25963
25964 Action: Check the date and time to ensure both are
25965 correct. If the clock reading is wrong shut down
25966 and correct the clock.
25967
25968
25969
25970 disk_rebuild_caller.pl1
25971 New starting parameters no partitions defined:
25972
25973
25974 Stream: Initializer process output.
25975
25976 Time: In response to an operator command.
25977
25978 Meaning: This message requests the input of new disk
25979 parameters.
25980
25981 Action: Input the new disk parameters. Use the "end"
25982 request when done.
25983
25984
25985 syserr_real.pl1
25986 Now terminating user process: PERSON.PROJ.
25987
25988
25989 Stream: BOS Typewriter.
25990
25991 Time: While system is running.
25992
25993 Meaning: This line is always preceded by an explanation of
25994 the error which required the terminaation of the
25995 user process PERSON.PROJ.
25996
25997
25998 Now terminating user process 449 08/21/20 MR12.7^L
25999
26000
26001 Action: No operator action is required.
26002
26003
26004 ocdcm_.pl1
26005 ocdcm_ bump_io_to_mc: Console recovery failure.
26006
26007
26008 Stream: BOS Typewriter Crashes system
26009
26010 Time: While system is running.
26011
26012 Meaning: The software detected Message Coordinator failure
26013 while the Message Coordinator was being used in
26014 place of a functioning console. Since the CCRF
26015 parameter was specified the system crashed.
26016
26017 Action: Contact the system programming staff. Contact the
26018 system programming staff._sa
26019
26020
26021
26022 ocdcm_.pl1
26023 ocdcm_ bump_io_to_mc: Message Coordinator
26024 failure.
26025
26026
26027 Stream: Logged in SYSERR log.
26028
26029 Time: While system is running.
26030
26031 Meaning: The Message Coordinator is no longer able to
26032 handle console traffic.
26033
26034 Action: Attempt to get an active console online as soon as
26035 possible and reset the Message Coordinator.
26036
26037
26038
26039 ocdcm_.pl1
26040 ocdcm_ console_recovery: Console failed
26041 assignment of alternate OPCx failed.
26042
26043
26044 Stream: Logged in SYSERR log.
26045
26046 Time: While system is running.
26047
26048 Meaning: The console software detected a failure of the
26049 bootload console and found an alternate to
26050 utilize. However when it tried to attach the
26051 alternate it too was found to be inoperative. The
26052 search continues for a usable console.
26053
26054
26055
26056 ocdcm_ console_recovery 450 08/21/20 MR12.7^L
26057
26058
26059 Action: Attempt to determine why the alternate console
26060 failed to come online. If it can be repaired
26061 configure it with the set_system_console command
26062 from a highly priviliged process.
26063
26064
26065
26066 ocdcm_.pl1
26067 ocdcm_ console_recovery: Console inoperative
26068 alternate OPCx assigned.
26069
26070
26071 Stream: Logged in SYSERR log.
26072
26073 Time: While system is running.
26074
26075 Meaning: The software has detected a bootload console
26076 failure and has assigned the specifed alternate to
26077 take over. The inoperative console is flagged as
26078 such.
26079
26080 Action: Contact the system programming staff.
26081
26082
26083 ocdcm_.pl1
26084 ocdcm_ console_recovery: Console inoperative
26085 no alternates available.
26086
26087
26088 Stream: Logged in SYSERR log.
26089
26090 Time: While system is running.
26091
26092 Meaning: The software dected failure of the bootload
26093 console but no alternates are configured. It
26094 will direct subsequent console traffic to the
26095 Message Coordinator.
26096
26097 Action: Attempt to get a running console online via the
26098 set_system_console command as soon as possible.
26099
26100
26101
26102 ocdcm_.pl1
26103 ocdcm_ console_recovery: Console inoperative
26104 no alternates no MC.
26105
26106
26107 Stream: Logged in SYSERR log.
26108
26109 Time: While system is running.
26110
26111
26112
26113
26114 ocdcm_ console_recovery 451 08/21/20 MR12.7^L
26115
26116
26117 Meaning: The software detected failure of the bootload
26118 console but no alternates are configured and the
26119 Message Coordinator is not functioning. All
26120 subsequent console traffic will be sent to the
26121 syserr log.
26122
26123 Action: Attempt to get a running console online via the
26124 set_system_console command as soon as possible.
26125
26126
26127
26128 ocdcm_.pl1
26129 ocdcm_ console_recovery: Console recovery
26130 failure.
26131
26132
26133 Stream: BOS Typewriter Crashes system
26134
26135 Time: While system is running.
26136
26137 Meaning: The software detected console failure and was
26138 unable to continue because the CCRF parameter was
26139 specified. The system crashed.
26140
26141 Action: Contact the system programming staff. Contact the
26142 system programming staff._sa
26143
26144
26145
26146 ocdcm_.pl1
26147 ocdcm_ esd_reset: No active consoles
26148 configured.
26149
26150
26151 Stream: Logged in SYSERR log.
26152
26153 Time: While system is running.
26154
26155 Meaning: During ESD there were no consoles in service. ESD
26156 messages will be sent to the syserr log.
26157
26158 Action: Contact the system programming staff.
26159
26160
26161 ocdcm_.pl1
26162 ocdcm_ init_all_consoles: Assigned console OPCx
26163 as TYPE device.
26164
26165
26166 Stream: $announce
26167
26168 Time: System Intialization.
26169
26170
26171
26172 ocdcm_ init_all_consoles 452 08/21/20 MR12.7^L
26173
26174
26175 Meaning: This message appears as the system configures
26176 consoles found in the config file. This message
26177 will only appear if the CLST parameter has been
26178 specified on the PARM card. Values for TYPE are
26179 "bootload" "alternate" "I/O" "inoperative" and
26180 "off".
26181
26182 Action: No operator action is required.
26183
26184
26185 ocdcm_.pl1
26186 ocdcm_ init_all_consoles: Changing state of
26187 OPCx to alt.
26188
26189
26190 Stream: BOS Typewriter sounds beeper
26191
26192 Time: System Intialization.
26193
26194 Meaning: During console initialization more than one
26195 console was found to have a state of "on". Since
26196 only one bootload console is allowed the software
26197 reconfigures additional "on" consoles as
26198 alternates.
26199
26200 Action: $config
26201
26202
26203 ocdcm_.pl1
26204 ocdcm_ init_all_consoles: Console channel
26205 assignment failed.
26206
26207
26208 Stream: BOS Typewriter Crashes system
26209
26210 Time: While system is running.
26211
26212 Meaning: Attachment of the specified bootload console
26213 failed during initialization.
26214
26215 Action: This is most likely a hardware failure of the
26216 console channel adapter.
26217
26218
26219
26220 ocdcm_.pl1
26221 ocdcm_ init_all_consoles: Illegal console name
26222 NAME specified. It will be ignored.
26223
26224
26225
26226 Stream: BOS Typewriter sounds beeper
26227
26228
26229
26230 ocdcm_ init_all_consoles 453 08/21/20 MR12.7^L
26231
26232
26233 Time: System Intialization.
26234
26235 Meaning: An illegal console name was found. Console names
26236 must be values of "opca" through "opcz".
26237
26238 Action: $config
26239
26240
26241 ocdcm_.pl1
26242 ocdcm_ init_all_consoles: Invalid channel
26243 specified for OPCx.
26244
26245
26246 Stream: BOS Typewriter Crashes system
26247
26248 Time: System Intialization.
26249
26250 Meaning: The console channel as specified in the config
26251 file for the specified device is illegal.
26252
26253 Action: $config
26254
26255
26256 ocdcm_.pl1
26257 ocdcm_ init_all_consoles: Invalid state of
26258 STATE for console OPCx. ocdcm_
26259 init_all_consoles: This console will not be
26260 configured.
26261
26262
26263
26264 Stream: BOS Typewriter sounds beeper
26265
26266 Time: System Intialization.
26267
26268 Meaning: An unrecognizable state was found for the
26269 specified console. That console will not be
26270 configured. Only valid states are "on" "alt"
26271 "io" "inop" and "off".
26272
26273 Action: $config
26274
26275
26276 ocdcm_.pl1
26277 ocdcm_ init_all_consoles: Maximum console count
26278 exceeded. ocdcm_ init_all_consoles: Additional
26279 consoles will not be configured.
26280
26281
26282
26283 Stream: BOS Typewriter sounds beeper
26284
26285 Time: System Intialization.
26286
26287
26288 ocdcm_ init_all_consoles 454 08/21/20 MR12.7^L
26289
26290
26291 Meaning: Too many consoles have been specified in the
26292 config file. Only the maximum number allowable
26293 will be configured.
26294
26295 Action: $config
26296
26297
26298 ocdcm_.pl1
26299 ocdcm_ init_all_consoles: Missing prph opc
26300 card.
26301
26302
26303 Stream: BOS Typewriter Crashes system
26304
26305 Time: System Intialization.
26306
26307 Meaning: At least one PRPH OPCx card must be in the config
26308 file.
26309
26310 Action: $config
26311
26312
26313 ocdcm_.pl1
26314 ocdcm_ init_all_consoles: No active console
26315 configured.
26316
26317
26318 Stream: BOS Typewriter Crashes system
26319
26320 Time: System Intialization.
26321
26322 Meaning: None of the consoles specified in the config file
26323 has a state of "on".
26324
26325 Action: $config
26326
26327
26328 ocdcm_.pl1
26329 ocdcm_ init_all_consoles: Unable to determine
26330 absolute memory address of oc_data.
26331
26332
26333
26334 Stream: BOS Typewriter Crashes system
26335
26336 Time: While system is running.
26337
26338 Meaning: The absloute memory address of oc_data could not
26339 be determined during console initialization.
26340
26341 Action: This is a very serious error. Ensure that your
26342 MST is good and then consider hardware.
26343
26344
26345
26346 ocdcm_ init_all_consoles 455 08/21/20 MR12.7^L
26347
26348
26349
26350
26351 ocdcm_.pl1
26352 ocdcm_ init_all_consoles: Unknown model NNNN
26353 specified for OPCx. It will not be configured.
26354
26355
26356
26357 Stream: BOS Typewriter sounds beeper
26358
26359 Time: System Intialization.
26360
26361 Meaning: The console model number specified in the config
26362 file is not supported by this software and will
26363 not be configured.
26364
26365 Action: $config
26366
26367
26368 ocdcm_.pl1
26369 ocdcm_ interrupt_handler: System Fault.
26370
26371
26372 Stream: Logged in SYSERR log.
26373
26374 Time: While system is running.
26375
26376 Meaning: A system fault interrupt was received from the
26377 IOM. The fault is logged and ignored.
26378
26379 Action: Contact the system programming staff.
26380
26381
26382 ocdcm_.pl1
26383 ocdcm_ lock_oc_data: Lock wait timer expired.
26384
26385
26386 Stream: BOS Typewriter Crashes system
26387
26388 Time: While system is running.
26389
26390 Meaning: A process waiting on the lock was not able to get
26391 the lock before the wait timer expired. This
26392 timer is calculated as the maximum time that it
26393 should take a READ I/O to complete times the
26394 number of CPUs specified in the config file. Any
26395 process waiting on the lock should never have to
26396 wait more than that amount of time for the lock to
26397 become available without there being a serious
26398 problem with the hardcore process holding the
26399 lock.
26400
26401 Action: Contact the system programming staff.
26402
26403
26404 ocdcm_ lock_oc_data 456 08/21/20 MR12.7^L
26405
26406
26407
26408
26409 ocdcm_.pl1
26410 ocdcm_ lock_oc_data: Mylock error.
26411
26412
26413 Stream: BOS Typewriter Crashes system
26414
26415 Time: While system is running.
26416
26417 Meaning: The offending process found its own process_id in
26418 the lock.
26419
26420 Action: Contact the system programming staff.
26421
26422
26423 ocdcm_.pl1
26424 ocdcm_ log_console_error: I/O timeout error
26425 on OPCx; status = SSSSSS oc_data flags: FLAGS
26426 oc_entry flags: FLAGS console_io flags: FLAGS
26427
26428
26429
26430 Stream: Logged in SYSERR log.
26431
26432 Time: While system is running.
26433
26434 Meaning: An I/O error occurred. The status is the returned
26435 IOM status for the I/O in question and the flags
26436 denote the state of the oc_data the console and
26437 the I/O respectively at the time of the error.
26438 The flag values are interpreted.
26439
26440 Action: Too many of these errors will result in the
26441 invocation of console recovery. Have the console
26442 fixed.
26443
26444
26445
26446 ocdcm_.pl1
26447 ocdcm_ reconfigure: Assigned OPCx as an
26448 alternate console for PERSON.PROJ.T.
26449
26450
26451 Stream: BOS Typewriter sounds beeper
26452
26453 Time: While system is running.
26454
26455 Meaning: The specified process has configured the specified
26456 console as an alternate.
26457
26458 Action: No operator action is required.
26459
26460
26461
26462 ocdcm_ reconfigure 457 08/21/20 MR12.7^L
26463
26464
26465
26466
26467 ocdcm_.pl1
26468 ocdcm_ reconfigure: Assigned OPCx as the
26469 bootload console for PERSON.PROJ.T.
26470
26471
26472 Stream: BOS Typewriter sounds beeper
26473
26474 Time: While system is running.
26475
26476 Meaning: The specified process has configured the specified
26477 console as the bootload console. The bootload
26478 console at the time of the reconfiguration is
26479 reconfigured as an alternate device.
26480
26481 Action: No operator action is required.
26482
26483
26484 ocdcm_.pl1
26485 ocdcm_ reconfigure: Bootload console
26486 deconfigured with CCRF set.
26487
26488
26489 Stream: BOS Typewriter Crashes system
26490
26491 Time: During console reconfiguration.
26492
26493 Meaning: The bootload console was deconfigured by use of
26494 the set_system_console command and the site had
26495 specified the CCRF parameter in the config file.
26496
26497 Action: Follow normal recovery procedures.
26498
26499
26500 ocdcm_.pl1
26501 ocdcm_ reconfigure: Consigned OPCx as an I/O
26502 device for PERSON.PROJ.T.
26503
26504
26505 Stream: BOS Typewriter sounds beeper
26506
26507 Time: While system is running.
26508
26509 Meaning: The specified process has configured the specified
26510 console as an I/O device.
26511
26512 Action: No operator action is required.
26513
26514
26515 ocdcm_.pl1
26516 ocdcm_ reconfigure: Marked OPCx as an
26517 inoperative device for PERSON.PROJ.T.
26518
26519
26520 ocdcm_ reconfigure 458 08/21/20 MR12.7^L
26521
26522
26523 Stream: BOS Typewriter sounds beeper
26524
26525 Time: While system is running.
26526
26527 Meaning: The specified process has configured the specified
26528 console as an inoperative device.
26529
26530 Action: No operator action is required.
26531
26532
26533 ocdcm_.pl1
26534 ocdcm_ reconfigure: MCA input through OPCx
26535 disabled by PERSON.PROJ.T.
26536
26537
26538 Stream: Logged in SYSERR log.
26539
26540 Time: While system is running.
26541
26542 Meaning: The input to the MCA Maint. Channel Adapter in
26543 the IMU Interrupt Multiplexer Unit from special
26544 keyboard sequences has been LOCKed disabled.
26545 Input to the MCA can now only come from the
26546 on-line Multics controlled channel 03 interface.
26547
26548 Action: No operator action is required.
26549
26550
26551 ocdcm_.pl1
26552 ocdcm_ reconfigure: MCAnn input through OPCx
26553 enabled by PERSON.PROJ.T.
26554
26555
26556 Stream: Logged in SYSERR log.
26557
26558 Time: While system is running.
26559
26560 Meaning: The input to MCAnn via special console keyboard
26561 sequences has been enabled UNLOCKed.
26562
26563 Action: No operator action is required.
26564
26565
26566 ocdcm_.pl1
26567 ocdcm_ reconfigure: Timeout executing MCA LOCK
26568 on OPCx for PERSON.PROJ.T.
26569
26570
26571 Stream: Logged in SYSERR log.
26572
26573 Time: While system is running.
26574
26575
26576
26577
26578 ocdcm_ reconfigure 459 08/21/20 MR12.7^L
26579
26580
26581 Meaning: The I/O to LOCK the MCA interface through OPCx did
26582 not complete within a given time.
26583
26584 Action: This is most likely a hardware failure of the
26585 console channel adapter or the IMU central.
26586
26587
26588
26589 ocdcm_.pl1
26590 ocdcm_ reconfigure: Timeout executing MCAnn
26591 UNLOCK on OPCx for PERSON.PROJ.T.
26592
26593
26594 Stream: Logged in SYSERR log.
26595
26596 Time: While system is running.
26597
26598 Meaning: The I/O to UNLOCK the MCAnn interface through
26599 OPCx did not complete within a given time.
26600
26601 Action: This is most likely a hardware failure of the
26602 console channel adapter or the IMU central.
26603
26604
26605
26606 ocdcm_.pl1
26607 ocdcm_ reset_console: Reset bootload console
26608 for PERSON.PROJ.T.
26609
26610
26611 Stream: BOS Typewriter sounds beeper
26612
26613 Time: While system is running.
26614
26615 Meaning: The bootload console has been reset by the
26616 specified process.
26617
26618 Action: No operator action is required.
26619
26620
26621 ocdcm_.pl1
26622 ocdcm_ unlock_oc_data: Lock not mine.
26623
26624
26625 Stream: BOS Typewriter Crashes system
26626
26627 Time: While system is running.
26628
26629 Meaning: A process attempting to unlock oc_data found a
26630 non-zero lock that was not its own.
26631
26632 Action: Contact the system programming staff.
26633
26634
26635
26636 on_line_salvager 460 08/21/20 MR12.7^L
26637
26638
26639
26640
26641 on_line_salvager.pl1
26642 on_line_salvager: cannot get activation info on
26643 PPPPP ERRORMESSAGE
26644
26645
26646 Stream: BOS Typewriter.
26647
26648 Time: While system is running.
26649
26650 Meaning: The on line salvager could not determine the
26651 length of a directory to be salvaged. A truncated
26652 copy will be made in >dumps.
26653
26654 Action: Contact the system programming staff.
26655
26656
26657 on_line_salvager.pl1
26658 on_line_salvager: error from sum on PPPPP
26659 ERRORMESSAGE
26660
26661
26662 Stream: BOS Typewriter Crashes system
26663
26664 Time: While system is running.
26665
26666 Meaning: The on line salvager could not access the branch
26667 for a sdirectory to be salvaged. This indicates a
26668 logic error in the supervisor or CPU or memory
26669 hardware problems.
26670
26671 Action: Contact the system programming staff. Follow
26672 normal recovery procedures.
26673
26674
26675
26676 on_line_salvager.pl1
26677 on_line_salvager: Getting pathname of PPPPP
26678
26679
26680 Stream: BOS Typewriter Crashes system
26681
26682 Time: While system is running.
26683
26684 Meaning: The on line salvager cannot obtain the pathname of
26685 a directory to be salvaged. This indicates a
26686 logic error in the supervisor or CPU or memory
26687 hardware problems.
26688
26689 Action: Take a dump. Contact the system programming
26690 staff. Follow normal recovery procedures.
26691
26692
26693
26694 on_line_salvager 461 08/21/20 MR12.7^L
26695
26696
26697
26698
26699 on_line_salvager.pl1
26700 on_line_salvager: lock error ERROMESSAGE
26701
26702
26703 Stream: BOS Typewriter Crashes system
26704
26705 Time: While system is running.
26706
26707 Meaning: The on line salvager could not lock its data base.
26708 This indicates a logic error in the supervisor or
26709 CPU or memory hardware problems.
26710
26711 Action: Contact the system programming staff. Follow
26712 normal recovery procedures. Be sure that a dump
26713 is taken.
26714
26715
26716
26717 mc_tty_.pl1
26718 OPER:
26719
26720
26721 Stream: Initializer terminal.
26722
26723 Time: While system is running.
26724
26725 Meaning: This message is typed if the operator enters a
26726 blank line on a message coordinator terminal. It
26727 indicates that input is expected on the terminal
26728 and that output will be inhibited for 30 seconds.
26729
26730 Action: Type a system control command.
26731
26732
26733 operator_mc_cmds_.pl1
26734 operator_mc_cmds_: accept: CHANNEL set to
26735 "full".
26736
26737
26738 Stream: as severity 1
26739
26740 Time: In response to an operator accept command.
26741
26742 Meaning: CHANNEL is already in use and authorization
26743 request has not changed from it's current state.
26744
26745 Action: Enter a corrected command line.
26746
26747
26748 operator_mc_cmds_.pl1
26749 operator_mc_cmds_: accept: channel not available
26750
26751
26752 operator_mc_cmds_ 462 08/21/20 MR12.7^L
26753
26754
26755 Stream: as severity 1
26756
26757 Time: In response to an operator accept command.
26758
26759 Meaning: Channel cannot be used as a message coordinator
26760 channel.
26761
26762 Action: Enter a corrected command line.
26763
26764
26765 operator_mc_cmds_.pl1
26766 operator_mc_cmds_: accept: channel not defined
26767 in cdt.
26768
26769
26770 Stream: as severity 1
26771
26772 Time: In response to an operator accept command.
26773
26774 Meaning: Channel is not found in the system cdt and
26775 therefore cannot be used.
26776
26777 Action: Enter a corrected command line.
26778
26779
26780 operator_mc_cmds_.pl1
26781 operator_mc_cmds_: accept: error: unknown
26782 privilege code
26783
26784
26785 Stream: as severity 1
26786
26787 Time: In response to an operator accept command.
26788
26789 Meaning: The operator has typed accept CHANNEL PRIVILEGE
26790 but PRIVILEGE is not a known privilege code.
26791
26792 Action: Enter a corrected command line.
26793
26794
26795 operator_mc_cmds_.pl1
26796 operator_mc_cmds_: accept: ERROR_TABLE_MESSAGE
26797 accept unsuccessful.
26798
26799
26800 Stream: as severity 1
26801
26802 Time: In response to an operator accept command.
26803
26804 Meaning: The error was returned from mc_commands_$new_tty
26805 causing the accept to abort.
26806
26807 Action: Enter a corrected command line.
26808
26809
26810 operator_mc_cmds_ 463 08/21/20 MR12.7^L
26811
26812
26813
26814
26815 operator_mc_cmds_.pl1
26816 operator_mc_cmds_: accept: ERROR_TABLE_MESSAGE
26817 Channel CHANNEL is not in Message Coordinator
26818 service.
26819
26820
26821
26822 Stream: as severity 1
26823
26824 Time: In response to an operator accept command.
26825
26826 Meaning: CHANNEL cannot be accepted as a message
26827 coordinator terminal.
26828
26829 Action: Enter a corrected command line.
26830
26831
26832 operator_mc_cmds_.pl1
26833 operator_mc_cmds_: accept: ERROR_TABLE_MESSAGE
26834 Failed to accept CHANNEL.
26835
26836
26837 Stream: as severity 1
26838
26839 Time: In response to an operator accept command.
26840
26841 Meaning: The operator has issued an accept CHANNEL command
26842 but CHANNEL cannot be accepted.
26843
26844 Action: Enter a corrected command line.
26845
26846
26847 operator_mc_cmds_.pl1
26848 operator_mc_cmds_: accept: ERROR_TABLE_MESSAGE
26849 Failed to reset restriction.
26850
26851
26852 Stream: as severity 1
26853
26854 Time: In response to an operator accept command.
26855
26856 Meaning: Failed to reset the reply restriction.
26857
26858 Action: Enter a corrected command line.
26859
26860
26861 operator_mc_cmds_.pl1
26862 operator_mc_cmds_: accept: ERROR_TABLE_MESSAGE
26863 Failed to set broadcast list to BROADCAST_LIST.
26864
26865
26866
26867
26868 operator_mc_cmds_ 464 08/21/20 MR12.7^L
26869
26870
26871 Stream: as severity 1
26872
26873 Time: In response to an operator accept command.
26874
26875 Meaning: Failed to set the broadcast list BROADCAST_LIST.
26876
26877 Action: Enter a corrected command line.
26878
26879
26880 operator_mc_cmds_.pl1
26881 operator_mc_cmds_: accept: ERROR_TABLE_MESSAGE
26882 Failed to set restriction to RESTRICTION.
26883
26884
26885 Stream: as severity 1
26886
26887 Time: In response to an operator accept command.
26888
26889 Meaning: Failed to set the reply restriction.
26890
26891 Action: Enter a corrected command line.
26892
26893
26894 operator_mc_cmds_.pl1
26895 operator_mc_cmds_: accept: ERROR_TABLE_MESSAGE
26896 This name is reserved for the system console.
26897
26898
26899 Stream: as severity 1
26900
26901 Time: In response to an operator accept command.
26902
26903 Meaning: Attempt to accept identifier "otw_" which is THE
26904 identifier for the master console which is
26905 automatically accepted on bootload.
26906
26907 Action: Enter a corrected command line.
26908
26909
26910 operator_mc_cmds_.pl1
26911 operator_mc_cmds_: accept: ERROR_TABLE_MESSAGE
26912 Usage: accept channel_id authority target
26913 broadcast_list
26914
26915
26916 Stream: as severity 1
26917
26918 Time: In response to an operator accept command.
26919
26920 Meaning: The operator has issued an accept command without
26921 any arguments.
26922
26923 Action: Enter a corrected command line.
26924
26925
26926 operator_mc_cmds_ 465 08/21/20 MR12.7^L
26927
26928
26929
26930
26931 operator_mc_cmds_.pl1
26932 operator_mc_cmds_: accept: Ioname already
26933 attached and active. accept unsuccessful.
26934
26935
26936 Stream: as severity 1
26937
26938 Time: In response to an operator accept command.
26939
26940 Meaning: The error was returned from mc_commands_$new_tty
26941 causing the accept to abort.
26942
26943 Action: Enter a corrected command line.
26944
26945
26946 operator_mc_cmds_.pl1
26947 operator_mc_cmds_: accept: Ioname not found.
26948 accept unsuccessful.
26949
26950
26951 Stream: as severity 1
26952
26953 Time: In response to an operator accept command.
26954
26955 Meaning: The error was returned from mc_commands_$new_tty
26956 causing the accept to abort. Channel not found in
26957 the cdt or pre-accepted as a virtual channel.
26958
26959 Action: Enter a corrected command line.
26960
26961
26962 operator_mc_cmds_.pl1
26963 operator_mc_cmds_: accept_vchn:
26964 ERROR_TABLE_MESSAGE Failed to accept VCHANNEL
26965
26966
26967 Stream: as severity 1
26968
26969 Time: In response to an operator accept_vchn command.
26970
26971 Meaning: Unable to pre-accept VCHANNEL as a virtual channel
26972 identifier.
26973
26974 Action: Enter a corrected command line.
26975
26976
26977 operator_mc_cmds_.pl1
26978 operator_mc_cmds_: accept_vchn:
26979 ERROR_TABLE_MESSAGE Failed to reset restriction.
26980
26981
26982
26983
26984 operator_mc_cmds_ 466 08/21/20 MR12.7^L
26985
26986
26987 Stream: as severity 1
26988
26989 Time: In response to an operator accept command.
26990
26991 Meaning: Failed to reset the reply restriction.
26992
26993 Action: Enter a corrected command line.
26994
26995
26996 operator_mc_cmds_.pl1
26997 operator_mc_cmds_: accept_vchn:
26998 ERROR_TABLE_MESSAGE Failed to set broadcast list
26999 to BROADCAST_LIST.
27000
27001
27002 Stream: as severity 1
27003
27004 Time: In response to an operator accept command.
27005
27006 Meaning: Failed to set the broadcast list for
27007 BROADCAST_LIST.
27008
27009 Action: Enter a corrected command line.
27010
27011
27012 operator_mc_cmds_.pl1
27013 operator_mc_cmds_: accept_vchn:
27014 ERROR_TABLE_MESSAGE Failed to set restriction to
27015 REPLY_TARGET
27016
27017
27018 Stream: as severity 1
27019
27020 Time: In response to an operator accept command.
27021
27022 Meaning: Failed to set the reply restriction for
27023 REPLY_TARGET.
27024
27025 Action: Enter a corrected command line.
27026
27027
27028 operator_mc_cmds_.pl1
27029 operator_mc_cmds_: accept_vchn:
27030 ERROR_TABLE_MESSAGE Usage: accept_vchn channel_id
27031 -auth authority -target reply_target -bc_list
27032 input_broadcast_list
27033
27034
27035
27036 Stream: as severity 1
27037
27038 Time: In response to an operator accept_vchn command.
27039
27040
27041
27042 operator_mc_cmds_ 467 08/21/20 MR12.7^L
27043
27044
27045 Meaning: Incorrect number of arguments supplied.
27046
27047 Action: Enter a corrected command line.
27048
27049
27050 operator_mc_cmds_.pl1
27051 operator_mc_cmds_: accept_vchn: Incorrect IO
27052 channel specification. This name is reserved for
27053 the system console.
27054
27055
27056
27057 Stream: as severity 1
27058
27059 Time: In response to an operator accept_vchn command.
27060
27061 Meaning: The specified virtual channel name given was
27062 "otw_". This identifier cannot be used as it
27063 identifies the system console.
27064
27065 Action: Enter a corrected command line.
27066
27067
27068 operator_mc_cmds_.pl1
27069 operator_mc_cmds_: accept_vchn: Incorrect IO
27070 channel specification. DOT Virtual channel names
27071 may not contain a DOT
27072
27073
27074 Stream: as severity 1
27075
27076 Time: In response to an operator accept_vchn command.
27077
27078 Meaning: The DOT "." character cannot be used in the
27079 virtual channel specifier.
27080
27081 Action: Enter a corrected command line.
27082
27083
27084 operator_mc_cmds_.pl1
27085 operator_mc_cmds_: accept_vchn: Invalid argument
27086 -auth may be followed by one of the following:
27087 full none reply daemon query
27088
27089
27090
27091 Stream: as severity 1
27092
27093 Time: In response to an operator accept_vchn command.
27094
27095 Meaning: An incorrect argument to the -auth control
27096 argument was supplied.
27097
27098
27099
27100 operator_mc_cmds_ 468 08/21/20 MR12.7^L
27101
27102
27103 Action: Enter a corrected command line.
27104
27105
27106 operator_mc_cmds_.pl1
27107 operator_mc_cmds_: accept_vchn: Invalid argument
27108 Bad broadcast list: BROADCAST_LIST
27109
27110
27111 Stream: as severity 1
27112
27113 Time: In response to an operator accept_vchn command.
27114
27115 Meaning: Incorrect argument supplied to the -bc_list
27116 control argument.
27117
27118 Action: Enter a corrected command line.
27119
27120
27121 operator_mc_cmds_.pl1
27122 operator_mc_cmds_: accept_vchn: Invalid argument
27123 Bad reply target: TARGET
27124
27125
27126 Stream: as severity 1
27127
27128 Time: In response to an operator accept_vchn command.
27129
27130 Meaning: An incorrect argument to the -reply control
27131 argument was supplied.
27132
27133 Action: Enter a corrected command line.
27134
27135
27136 operator_mc_cmds_.pl1
27137 operator_mc_cmds_: accept_vchn: Ioname already
27138 attached and active. VCHANNEL set to full.
27139
27140
27141
27142 Stream: as severity 1
27143
27144 Time: In response to an operator accept_vchn command.
27145
27146 Meaning: VCHANNEL already active and authorization request
27147 is same.
27148
27149 Action: Enter a corrected command line.
27150
27151
27152 operator_mc_cmds_.pl1
27153 operator_mc_cmds_: accept_vchn: Specified
27154 control argument is not accpeted Argument not
27155 accepted: ARGUMENT
27156
27157
27158 operator_mc_cmds_ 469 08/21/20 MR12.7^L
27159
27160
27161 Stream: as severity 1
27162
27163 Time: In response to an operator accept_vchn command.
27164
27165 Meaning: An incorrect control argument was supplied to the
27166 accept_vchn request.
27167
27168 Action: Enter a corrected command line.
27169
27170
27171 operator_mc_cmds_.pl1
27172 operator_mc_cmds_: COMMAND: ERROR_TABLE_MESSAGE
27173 SYSDIR>answer_table
27174
27175
27176 Stream: as severity 1
27177
27178 Time: In response to an operator command COMMAND.
27179
27180 Meaning: The system was unable to access the answer_table
27181 in SYSDIR.
27182
27183 Action: Contact the system programming staff.
27184
27185
27186 operator_mc_cmds_.pl1
27187 operator_mc_cmds_: COMMAND: ERROR_TABLE_MESSAGE
27188 SYSDIR>cdt
27189
27190
27191 Stream: as severity 1
27192
27193 Time: In response to an operator command COMMAND.
27194
27195 Meaning: The system was unable to access the cdt in SYSDIR.
27196
27197 Action: Contact the system programming staff.
27198
27199
27200 operator_mc_cmds_.pl1
27201 operator_mc_cmds_: COMMAND: ERROR_TABLE_MESSAGE
27202 SYSDIR>installation_parms
27203
27204
27205 Stream: as severity 1
27206
27207 Time: In response to an operator command COMMAND.
27208
27209 Meaning: The system was unable to access the
27210 installation_parms in SYSDIR.
27211
27212 Action: Contact the system programming staff.
27213
27214
27215
27216 operator_mc_cmds_ 470 08/21/20 MR12.7^L
27217
27218
27219
27220
27221 operator_mc_cmds_.pl1
27222 operator_mc_cmds_: COMMAND: ERROR_TABLE_MESSAGE
27223 SYSDIR>whotab
27224
27225
27226 Stream: as severity 1
27227
27228 Time: In response to an operator command COMMAND.
27229
27230 Meaning: The system was unable to access the whotab in
27231 SYSDIR.
27232
27233 Action: Contact the system programming staff.
27234
27235
27236 operator_mc_cmds_.pl1
27237 operator_mc_cmds_: COMMAND: ERROR_TABLE_MESSAGE
27238 Incorrect number of arguments.
27239
27240
27241 Stream: as severity 1
27242
27243 Time: In response to an operator command COMMAND.
27244
27245 Meaning: Insufficient number of arguments supplied with the
27246 command.
27247
27248 Action: Enter a corrected command line.
27249
27250
27251 operator_mc_cmds_.pl1
27252 operator_mc_cmds_: COMMAND: ERROR_TABLE_MESSAGE
27253 removing user no proc on channel CHANNEL
27254
27255
27256 Stream: as severity 1
27257
27258 Time: In response to an operator command.
27259
27260 Meaning: An error described by ERROR_TABLE_MESSAGE occured
27261 while attempting the operator command COMMAND.
27262
27263 Action: Contact the system programming staff.
27264
27265
27266 operator_mc_cmds_.pl1
27267 operator_mc_cmds_: COMMAND: ERROR_TABLE_MESSAGE
27268 trying to access SYSDIR>mc_anstbl
27269
27270
27271 Stream: as severity 1
27272
27273
27274 operator_mc_cmds_ 471 08/21/20 MR12.7^L
27275
27276
27277 Time: In response to an operator command COMMAND.
27278
27279 Meaning: The system was not able to access the mc_anstbl in
27280 SYSDIR.
27281
27282 Action: Contact the system programming staff.
27283
27284
27285 operator_mc_cmds_.pl1
27286 operator_mc_cmds_: define: Action not performed.
27287 define unsuccessful.
27288
27289
27290 Stream: as severity 1
27291
27292 Time: In response to an operator define command.
27293
27294 Meaning: An error was returned from mc_commands_$define
27295 causing the define to abort. Target channel found
27296 requiring an accept in mc_anstbl.
27297
27298 Action: Enter a corrected command line.
27299
27300
27301 operator_mc_cmds_.pl1
27302 operator_mc_cmds_: define: ERROR_TABLE_MESSAGE
27303 define unsuccessful.
27304
27305
27306 Stream: as severity 1
27307
27308 Time: In response to an operator define command.
27309
27310 Meaning: An error was returned from mc_commands_$define
27311 causing the define to abort.
27312
27313 Action: Enter a corrected command line.
27314
27315
27316 operator_mc_cmds_.pl1
27317 operator_mc_cmds_: define: Ioname not active.
27318 define unsuccessful.
27319
27320
27321 Stream: as severity 1
27322
27323 Time: In response to an operator define command.
27324
27325 Meaning: An error was returned from mc_commands_$define
27326 causing the define to abort. Target channel not
27327 active in the mc_anstbl.
27328
27329 Action: Enter a corrected command line.
27330
27331
27332 operator_mc_cmds_ 472 08/21/20 MR12.7^L
27333
27334
27335
27336
27337 operator_mc_cmds_.pl1
27338 operator_mc_cmds_: define: Ioname not found.
27339 define unsuccessful.
27340
27341
27342 Stream: as severity 1
27343
27344 Time: In response to an operator define command.
27345
27346 Meaning: An error was returned from mc_commands_$define
27347 causing the define to abort. Could not locate
27348 VCONS in vcons_tab.
27349
27350 Action: Enter a corrected command line.
27351
27352
27353 operator_mc_cmds_.pl1
27354 operator_mc_cmds_: define: There is no room to
27355 make requested allocations.
27356
27357
27358 Stream: as severity 1
27359
27360 Time: In response to an operator define command.
27361
27362 Meaning: The operator has issued a define SOURCE STREAM
27363 VCONS command but the system could not make the
27364 new entry in the message routing table. No action
27365 was taken.
27366
27367 Action: Enter a corrected command line.
27368
27369
27370 operator_mc_cmds_.pl1
27371 operator_mc_cmds_: define: Typename not found.
27372 define unsuccessful.
27373
27374
27375 Stream: as severity 1
27376
27377 Time: In response to an operator define command.
27378
27379 Meaning: An error was returned from mc_commands_$define
27380 causing the define to abort. Target VCONS type
27381 not known.
27382
27383 Action: Enter a corrected command line.
27384
27385
27386 operator_mc_cmds_.pl1
27387
27388
27389
27390 operator_mc_cmds_ 473 08/21/20 MR12.7^L
27391
27392
27393 operator_mc_cmds_: deroute: ERROR_TABLE_MESSAGE
27394 reroute unsuccessful.
27395
27396
27397 Stream: as severity 1
27398
27399 Time: In response to an operator deroute command.
27400
27401 Meaning: An error was returned from mc_commands_$deroute
27402 causing the deroute to abort.
27403
27404 Action: Enter a corrected command line.
27405
27406
27407 operator_mc_cmds_.pl1
27408 operator_mc_cmds_: deroute: There is no room to
27409 make requested allocations.
27410
27411
27412 Stream: as severity 1
27413
27414 Time: In response to an operator deroute command.
27415
27416 Meaning: The operator has issued a deroute SOURCE STREAM
27417 VCONS command but the system had no room to make
27418 the new entry in the message routing table. There
27419 may be up to 16 sources each with 8 streams and
27420 each stream may have up to 8 virtual consoles. No
27421 action was taken.
27422
27423 Action: Enter a corrected command line.
27424
27425
27426 operator_mc_cmds_.pl1
27427 operator_mc_cmds_: drop: error: Channel CHANNEL
27428 not a message coordinator terminal.
27429
27430
27431 Stream: as severity 1
27432
27433 Time: In response to an operator command.
27434
27435 Meaning: Cannot drop CHANNEL as it cannot be found attached
27436 to the message coordinator.
27437
27438 Action: Contact the system programming staff.
27439
27440
27441 operator_mc_cmds_.pl1
27442 operator_mc_cmds_: drop: error: Channel CHANNEL
27443 not configured.
27444
27445
27446
27447
27448 operator_mc_cmds_ 474 08/21/20 MR12.7^L
27449
27450
27451 Stream: as severity 1
27452
27453 Time: In response to an operator command.
27454
27455 Meaning: Channel CHANNEL is not defined in the system cdt.
27456
27457 Action: Contact the system programming staff.
27458
27459
27460 operator_mc_cmds_.pl1
27461 operator_mc_cmds_: drop: error: Channel CHANNEL
27462 not dialed to initializer.
27463
27464
27465 Stream: as severity 1
27466
27467 Time: In response to an operator command.
27468
27469 Meaning: CHANNEL must be dialed to the initializer before
27470 being dropped.
27471
27472 Action: Contact the system programming staff.
27473
27474
27475 operator_mc_cmds_.pl1
27476 operator_mc_cmds_: drop: ERROR_TABLE_MESSAGE
27477 drop unsuccessful.
27478
27479
27480 Stream: as severity 1
27481
27482 Time: In response to an operator drop command.
27483
27484 Meaning: An error was returned from mc_commands_$remove_tty
27485 causing the drop to abort.
27486
27487 Action: Enter a corrected command line.
27488
27489
27490 operator_mc_cmds_.pl1
27491 operator_mc_cmds_: redefine: Action not
27492 performed. redefine unsuccessful.
27493
27494
27495 Stream: as severity 1
27496
27497 Time: In response to an operator redefine command.
27498
27499 Meaning: An error was returned from mc_commands_$redefine
27500 causing the redefine to abort. Target channel
27501 found requiring an accept in mc_anstbl.
27502
27503 Action: Enter a corrected command line.
27504
27505
27506 operator_mc_cmds_ 475 08/21/20 MR12.7^L
27507
27508
27509
27510
27511 operator_mc_cmds_.pl1
27512 operator_mc_cmds_: redefine: Allocation could
27513 not be performed. redefine unsuccessful.
27514
27515
27516 Stream: as severity 1
27517
27518 Time: In response to an operator redefine command.
27519
27520 Meaning: The operator has issued a redefine VCONS SOURCE
27521 STREAM VCONS command but the system could not make
27522 the new entry in the message routing table. No
27523 action was taken.
27524
27525 Action: Enter a corrected command line.
27526
27527
27528 operator_mc_cmds_.pl1
27529 operator_mc_cmds_: redefine: ERROR_TABLE_MESSAGE
27530 redefine unsuccessful.
27531
27532
27533 Stream: as severity 1
27534
27535 Time: In response to an operator redefine command.
27536
27537 Meaning: An error was returned from mc_commands_$redefine
27538 causing the redefine to abort.
27539
27540 Action: Enter a corrected command line.
27541
27542
27543 operator_mc_cmds_.pl1
27544 operator_mc_cmds_: redefine: Ioname not active.
27545 redefine unsuccessful.
27546
27547
27548 Stream: as severity 1
27549
27550 Time: In response to an operator redefine command.
27551
27552 Meaning: An error was returned from mc_commands_$redefine
27553 causing the redefine to abort. Target channel not
27554 active in the mc_anstbl.
27555
27556 Action: Enter a corrected command line.
27557
27558
27559 operator_mc_cmds_.pl1
27560 operator_mc_cmds_: redefine: Ioname not found.
27561 redefine unsuccessful.
27562
27563
27564 operator_mc_cmds_ 476 08/21/20 MR12.7^L
27565
27566
27567 Stream: as severity 1
27568
27569 Time: In response to an operator redefine command.
27570
27571 Meaning: An error was returned from mc_commands_$redefine
27572 causing the redefine to abort. Could not locate
27573 VCONS in vcons_tab.
27574
27575 Action: Enter a corrected command line.
27576
27577
27578 operator_mc_cmds_.pl1
27579 operator_mc_cmds_: redefine: Typename not found.
27580 redefine unsuccessful.
27581
27582
27583 Stream: as severity 1
27584
27585 Time: In response to an operator redefine command.
27586
27587 Meaning: An error was returned from mc_commands_$redefine
27588 causing the redefine to abort. Target VCONS type
27589 not known.
27590
27591 Action: Enter a corrected command line.
27592
27593
27594 operator_mc_cmds_.pl1
27595 operator_mc_cmds_: reroute: ERROR_TABLE_MESSAGE
27596 reroute unsuccessful.
27597
27598
27599 Stream: as severity 1
27600
27601 Time: In response to an operator reroute command.
27602
27603 Meaning: An error was returned from mc_commands_$reroute
27604 causing the reroute to abort.
27605
27606 Action: Enter a corrected command line.
27607
27608
27609 operator_mc_cmds_.pl1
27610 operator_mc_cmds_: reroute: There is no room to
27611 make requested allocations.
27612
27613
27614 Stream: as severity 1
27615
27616 Time: In response to an operator reroute command.
27617
27618 Meaning: The operator has issued a reroute SOURCE STREAM
27619 OLD_VCONS NEW_VCONS command but the system had no
27620
27621
27622 operator_mc_cmds_ 477 08/21/20 MR12.7^L
27623
27624
27625 room to make the new entry in the message routing
27626 table. There may be up to 16 sources each with 8
27627 streams and each stream may have up to 8 virtual
27628 consoles. No action was taken.
27629
27630 Action: Enter a corrected command line.
27631
27632
27633 operator_mc_cmds_.pl1
27634 operator_mc_cmds_: route: ERROR_TABLE_MESSAGE
27635 route unsuccessful.
27636
27637
27638 Stream: as severity 1
27639
27640 Time: In response to an operator route command.
27641
27642 Meaning: An error was returned from mc_commands_$route
27643 causing the route to abort.
27644
27645 Action: Enter a corrected command line.
27646
27647
27648 operator_mc_cmds_.pl1
27649 operator_mc_cmds_: route: Ioname not found.
27650 route unsuccessful.
27651
27652
27653 Stream: as severity 1
27654
27655 Time: In response to an operator route command.
27656
27657 Meaning: An error was returned from mc_commands_$route
27658 causing the route to abort. VCONS not located in
27659 vcons_tab.
27660
27661 Action: Enter a corrected command line.
27662
27663
27664 operator_mc_cmds_.pl1
27665 operator_mc_cmds_: route: There is no room to
27666 make requested allocations.
27667
27668
27669 Stream: as severity 1
27670
27671 Time: In response to an operator route command.
27672
27673 Meaning: The operator has issued a route SOURCE STREAM
27674 VCONS command but the system had no room to make
27675 the new entry in the message routing table. There
27676 may be up to 16 sources each with 8 streams and
27677
27678
27679
27680 operator_mc_cmds_ 478 08/21/20 MR12.7^L
27681
27682
27683 each stream may have up to 8 virtual consoles. No
27684 action was taken.
27685
27686 Action: Enter a corrected command line.
27687
27688
27689 operator_mc_cmds_.pl1
27690 operator_mc_cmds_: substty: ERROR_TABLE_MESSAGE
27691 removing channel CHANNEL
27692
27693
27694 Stream: as severity 1
27695
27696 Time: In response to an operator substty command.
27697
27698 Meaning: Unable to remove CHANNEL designated as the source
27699 of the substitution.
27700
27701 Action: Enter a corrected command line.
27702
27703
27704 operator_mc_cmds_.pl1
27705 operator_mc_cmds_: substty: Channel CHANNEL not
27706 configured.
27707
27708
27709 Stream: as severity 1
27710
27711 Time: In response to an operator substty command.
27712
27713 Meaning: Channel CHANNEL is not found in the system cdt.
27714
27715 Action: Enter a corrected command line.
27716
27717
27718 operator_mc_cmds_.pl1
27719 operator_mc_cmds_: substty: Channel CHANNEL not
27720 dialed to initializer
27721
27722
27723 Stream: as severity 1
27724
27725 Time: In response to an operator substty command.
27726
27727 Meaning: Channel CHANNEL was not previously dialed to the
27728 initializer and thus cannot be substituted.
27729
27730 Action: Enter a corrected command line.
27731
27732
27733 operator_mc_cmds_.pl1
27734 operator_mc_cmds_: substty: error: cannot
27735 substty for same channel
27736
27737
27738 operator_mc_cmds_ 479 08/21/20 MR12.7^L
27739
27740
27741 Stream: as severity 1
27742
27743 Time: In response to an operator substty command.
27744
27745 Meaning: The operator has attempted to use substty to
27746 substitute a channel for itself.
27747
27748 Action: Enter a corrected command line.
27749
27750
27751 operator_mc_cmds_.pl1
27752 operator_mc_cmds_: substty: error: channel not
27753 available
27754
27755
27756 Stream: as severity 1
27757
27758 Time: In response to an operator accept command.
27759
27760 Meaning: Channel cannot be used as a message coordinator
27761 channel.
27762
27763 Action: Enter a corrected command line.
27764
27765
27766 operator_mc_cmds_.pl1
27767 operator_mc_cmds_: substty: error: channel not
27768 defined in cdt.
27769
27770
27771 Stream: as severity 1
27772
27773 Time: In response to an operator accept command.
27774
27775 Meaning: Channel is not found in the system cdt and
27776 therefore cannot be used.
27777
27778 Action: Enter a corrected command line.
27779
27780
27781 operator_mc_cmds_.pl1
27782 operator_mc_cmds_: substty: ERROR_TABLE_MESSAGE
27783 substty unsuccessful.
27784
27785
27786 Stream: as severity 1
27787
27788 Time: In response to an operator substty command.
27789
27790 Meaning: An error was returned from mc_commands_$substty
27791 causing the substty to abort.
27792
27793 Action: Enter a corrected command line.
27794
27795
27796 operator_mc_cmds_ 480 08/21/20 MR12.7^L
27797
27798
27799
27800
27801 operator_mc_cmds_.pl1
27802 operator_mc_cmds_: substty: Ioname not found.
27803 substty unsuccessful.
27804
27805
27806 Stream: as severity 1
27807
27808 Time: In response to an operator substty command.
27809
27810 Meaning: An error was returned from mc_commands_$substty
27811 causing the substty to abort. Could not locate
27812 source channel in mc_anstbl.
27813
27814 Action: Enter a corrected command line.
27815
27816
27817 operator_mc_cmds_.pl1
27818 operator_mc_cmds_: substty: Ioname not found.
27819 substty unsuccessful.
27820
27821
27822 Stream: as severity 1
27823
27824 Time: In response to an operator substty command.
27825
27826 Meaning: The error was returned from mc_commands_$new_tty
27827 causing the substty to abort. The target channel
27828 not found in the cdt or pre-accepted as a virtual
27829 channel.
27830
27831 Action: Enter a corrected command line.
27832
27833
27834 operator_mc_cmds_.pl1
27835 operator_mc_cmds_: substty: The requested action
27836 was not performed. substty unsuccessful.
27837
27838
27839 Stream: as severity 1
27840
27841 Time: In response to an operator substty command.
27842
27843 Meaning: An error was returned from mc_commands_$substty
27844 causing the substty to abort. The target channel
27845 is in a "pending" state which means it has not
27846 been accepted yet.
27847
27848 Action: Enter a corrected command line.
27849
27850
27851 operator_mc_cmds_.pl1
27852
27853
27854 operator_mc_cmds_ 481 08/21/20 MR12.7^L
27855
27856
27857 operator_mc_cmds_: undefine: ERROR_TABLE_MESSAGE
27858 undefine unsuccessful.
27859
27860
27861 Stream: as severity 1
27862
27863 Time: In response to an operator undefine command.
27864
27865 Meaning: An error was returned from mc_commands_$undefine
27866 causing the undefine to abort.
27867
27868 Action: Enter a corrected command line.
27869
27870
27871 operator_mc_cmds_.pl1
27872 operator_mc_cmds_: undefine: Ioname not found.
27873 undefine unsuccessful.
27874
27875
27876 Stream: as severity 1
27877
27878 Time: In response to an operator undefine command.
27879
27880 Meaning: An error was returned from mc_commands_$undefine
27881 causing the undefine to abort. Could not locate
27882 VCONS in vcons_tab.
27883
27884 Action: Enter a corrected command line.
27885
27886
27887 operator_process_cmds_.pl1
27888 operator_process_cmds_: bump: error: invalid
27889 arguments
27890
27891
27892 Stream: as severity 1
27893
27894 Time: In response to an operator command.
27895
27896 Meaning: A bad argument has been typed to the bump command.
27897 No action was taken.
27898
27899 Action: Enter a corrected command line.
27900
27901
27902 operator_process_cmds_.pl1
27903 operator_process_cmds_: bump: NAME.PROJ bumped
27904
27905
27906 Stream: as severity 1
27907
27908 Time: In response to an operator command.
27909
27910
27911
27912 operator_process_cmds_ 482 08/21/20 MR12.7^L
27913
27914
27915 Meaning: This is the response to an operator bump command.
27916 The user affected is named.
27917
27918 Action: No operator action is required.
27919
27920
27921 operator_process_cmds_.pl1
27922 operator_process_cmds_: bump: NAME.PROJ has
27923 "nobump"
27924
27925
27926 Stream: as severity 1
27927
27928 Time: While system is running.
27929
27930 Meaning: This is the response to the command bump NAME PROJ
27931 if the user has the nobump privilege. The user
27932 was not bumped.
27933
27934 Action: If it is imperative to bump the user for instance
27935 at system shutdown time do a who to find out his
27936 channel number then type "bump CHANNEL".
27937
27938
27939
27940 operator_process_cmds_.pl1
27941 operator_process_cmds_: bump: no bump signalled
27942 to NAME PROJ
27943
27944
27945 Stream: as severity 1
27946
27947 Time: In response to an operator command.
27948
27949 Meaning: An operator bump command specified a nonexistent
27950 channel name or user name and project. No action
27951 was taken on the command.
27952
27953 Action: Enter a corrected command line. This message may
27954 be printed as a result of trying to bump a user by
27955 name when he has nobump privilege. Bump him by
27956 channel name instead.
27957
27958
27959
27960 operator_process_cmds_.pl1
27961 operator_process_cmds_: COMMAND: error: Invalid
27962 FNP tag: FNP
27963
27964
27965 Stream: as severity 1
27966
27967 Time: In response to an operator command COMMAND.
27968
27969
27970 operator_process_cmds_ 483 08/21/20 MR12.7^L
27971
27972
27973 Meaning: The FNP tag following COMMAND was more than one
27974 character in length. FNP specifiers can only be
27975 one character long ie: a b c etc..
27976
27977 Action: Enter a corrected command line.
27978
27979
27980 operator_process_cmds_.pl1
27981 operator_process_cmds_: COMMAND: error: No FNP
27982 tag specified
27983
27984
27985 Stream: as severity 1
27986
27987 Time: In response to an operator command COMMAND.
27988
27989 Meaning: Expected a FNP designator but none typed
27990 following COMMAND.
27991
27992 Action: Enter a corrected command line.
27993
27994
27995 operator_process_cmds_.pl1
27996 operator_process_cmds_: COMMAND: error: No
27997 multiplexer specified
27998
27999
28000 Stream: as severity 1
28001
28002 Time: In response to an operator command COMMAND.
28003
28004 Meaning: Expected a multiplexer designator but none typed
28005 following COMMAND.
28006
28007 Action: Enter a corrected command line.
28008
28009
28010 operator_process_cmds_.pl1
28011 operator_process_cmds_: COMMAND: error: Usage:
28012 COMMAND Person.Project|CHANNEL|mpx MPX TIME
28013 MESSAGE The "Person Project" format is obsolete.
28014
28015
28016
28017 Stream: as severity 1
28018
28019 Time: In response to an operator command COMMAND.
28020
28021 Meaning: The character "." was not found on the request
28022 line and COMMAND was not followed by a process id.
28023 If argument following COMMAND is personid and
28024 projectid the correct syntax is "Person.Project"
28025 not "Person Project".
28026
28027
28028 operator_process_cmds_ 484 08/21/20 MR12.7^L
28029
28030
28031 Action: Enter a corrected command line.
28032
28033
28034 operator_process_cmds_.pl1
28035 operator_process_cmds_: COMMAND: error: Usage:
28036 COMMAND Person.Project|CHANNEL|mpx MPX|-pid
28037 TIME MESSAGE
28038
28039
28040 Stream: as severity 1
28041
28042 Time: In response to an operator command COMMAND.
28043
28044 Meaning: Insufficient number of arguments supplied with the
28045 command.
28046
28047 Action: Enter a corrected command line.
28048
28049
28050 operator_process_cmds_.pl1
28051 operator_process_cmds_: COMMAND:
28052 ERROR_TABLE_MESSAGE SYSDIR>answer_table
28053
28054
28055 Stream: as severity 1
28056
28057 Time: In response to an operator command COMMAND.
28058
28059 Meaning: The system was unable to access the answer_table
28060 in SYSDIR.
28061
28062 Action: Contact the system programming staff.
28063
28064
28065 operator_process_cmds_.pl1
28066 operator_process_cmds_: COMMAND:
28067 ERROR_TABLE_MESSAGE SYSDIR>cdt
28068
28069
28070 Stream: as severity 1
28071
28072 Time: In response to an operator command COMMAND.
28073
28074 Meaning: The system was unable to access the cdt in SYSDIR.
28075
28076 Action: Contact the system programming staff.
28077
28078
28079 operator_process_cmds_.pl1
28080 operator_process_cmds_: COMMAND:
28081 ERROR_TABLE_MESSAGE SYSDIR>installation_parms
28082
28083
28084
28085
28086 operator_process_cmds_ 485 08/21/20 MR12.7^L
28087
28088
28089 Stream: as severity 1
28090
28091 Time: In response to an operator command COMMAND.
28092
28093 Meaning: The system was unable to access the
28094 installation_parms in SYSDIR.
28095
28096 Action: Contact the system programming staff.
28097
28098
28099 operator_process_cmds_.pl1
28100 operator_process_cmds_: COMMAND:
28101 ERROR_TABLE_MESSAGE SYSDIR>whotab
28102
28103
28104 Stream: as severity 1
28105
28106 Time: In response to an operator command COMMAND.
28107
28108 Meaning: The system was unable to access the whotab in
28109 SYSDIR.
28110
28111 Action: Contact the system programming staff.
28112
28113
28114 operator_process_cmds_.pl1
28115 operator_process_cmds_: COMMAND:
28116 ERROR_TABLE_MESSAGE Error recieved from AS.
28117
28118
28119 Stream: as severity 1
28120
28121 Time: In response to an operator command COMMAND.
28122
28123 Meaning: Recieved an error from answering service
28124 attempting to remove the terminal user from the
28125 system answer table. User's process state will
28126 remain unchanged.
28127
28128 Action: Enter a corrected command line.
28129
28130
28131 operator_process_cmds_.pl1
28132 operator_process_cmds_: COMMAND:
28133 ERROR_TABLE_MESSAGE From hcs_$wakeup for CHANNEL
28134
28135
28136 Stream: as severity 1
28137
28138 Time: In response to an operator command COMMAND.
28139
28140
28141
28142
28143
28144 operator_process_cmds_ 486 08/21/20 MR12.7^L
28145
28146
28147 Meaning: Recieved an error from answering service when
28148 attempting to process the command COMMAND for
28149 channel CHANNEL.
28150
28151 Action: Enter a corrected command line.
28152
28153
28154 operator_process_cmds_.pl1
28155 operator_process_cmds_: COMMAND:
28156 ERROR_TABLE_MESSAGE Incorrect number of arguments.
28157
28158
28159 Stream: as severity 1
28160
28161 Time: In response to an operator command COMMAND.
28162
28163 Meaning: Insufficient number of arguments supplied with the
28164 command.
28165
28166 Action: Enter a corrected command line.
28167
28168
28169 operator_process_cmds_.pl1
28170 operator_process_cmds_: COMMAND:
28171 ERROR_TABLE_MESSAGE Invalid process id:
28172 PROCESS_ID. Use the first 6 or all 12 digits of
28173 the pid.
28174
28175
28176
28177 Stream: as severity 1
28178
28179 Time: In response to an operator command COMMAND.
28180
28181 Meaning: The typed length of the PROCESS_ID was incorrect.
28182
28183 Action: Enter a corrected command line.
28184
28185
28186 operator_process_cmds_.pl1
28187 operator_process_cmds_: detach: Channel CHANNEL
28188 is not currently active and cannot be detached.
28189
28190
28191 Stream: as severity 1
28192
28193 Time: In response to an operator command.
28194
28195 Meaning: An operator detach command specified a channel
28196 that is not attached. No action was taken.
28197
28198 Action: Enter a corrected command line
28199
28200
28201
28202 operator_process_cmds_ 487 08/21/20 MR12.7^L
28203
28204
28205
28206
28207 operator_process_cmds_.pl1
28208 operator_process_cmds_: detach: CHANNEL is in
28209 use by the message coordinator and can not be
28210 detached.
28211
28212
28213 Stream: as severity 1
28214
28215 Time: In response to an operator command.
28216
28217 Meaning: An operator detach command specified a message
28218 coordinator channel. The channel was not
28219 detached.
28220
28221 Action: Enter a corrected command line. Use the drop
28222 command to take a channel away from the message
28223 coordinator.
28224
28225
28226
28227 operator_process_cmds_.pl1
28228 operator_process_cmds_: detach: error: invalid
28229 arguments
28230
28231
28232 Stream: as severity 1
28233
28234 Time: In response to an operator command.
28235
28236 Meaning: A bad argument has been typed to the detach
28237 command. No action was taken.
28238
28239 Action: Enter a corrected command line.
28240
28241
28242 operator_process_cmds_.pl1
28243 operator_process_cmds_: detach: ERROR_MESSAGE
28244 CHANNEL
28245
28246
28247 Stream: as severity 1
28248
28249 Time: In response to an operator command.
28250
28251 Meaning: The operator has issued a detach CHANNEL command
28252 and the error described by ERROR_MESSAGE occurred
28253 during the attempt to detach it.
28254
28255 Action: Enter a corrected command line.
28256
28257
28258
28259
28260 operator_process_cmds_ 488 08/21/20 MR12.7^L
28261
28262
28263 operator_process_cmds_.pl1
28264 operator_process_cmds_: detach: NAME.PROJ
28265 detached
28266
28267
28268 Stream: as severity 1
28269
28270 Time: In response to an operator command.
28271
28272 Meaning: This is the response to an operator detach
28273 command. The user affected is named.
28274
28275 Action: No operator action is required.
28276
28277
28278 operator_process_cmds_.pl1
28279 operator_process_cmds_: detach: no detach
28280 signalled to NAME PROJ
28281
28282
28283 Stream: as severity 1
28284
28285 Time: In response to an operator command.
28286
28287 Meaning: An operator detach command specified a nonexistent
28288 channel name or user name and project. No action
28289 was taken on the command.
28290
28291 Action: Enter a corrected command line.
28292
28293
28294 operator_process_cmds_.pl1
28295 operator_process_cmds_: disconnect: NAME.PROJ
28296 disconnected.
28297
28298
28299 Stream: as severity 1
28300
28301 Time: In response to an operator command.
28302
28303 Meaning: This is the response to an operator disconnect
28304 command. The user affected is named.
28305
28306 Action: No operator action is required.
28307
28308
28309 operator_process_cmds_.pl1
28310 operator_process_cmds_: terminate: NAME.PROJ
28311 terminated
28312
28313
28314 Stream: as severity 1
28315
28316
28317
28318 operator_process_cmds_ 489 08/21/20 MR12.7^L
28319
28320
28321 Time: In response to an operator command.
28322
28323 Meaning: This is the response to an operator terminate
28324 command. The user affected is named.
28325
28326 Action: No operator action is required.
28327
28328
28329 operator_process_cmds_.pl1
28330 operator_process_cmds_: terminate: no terminate
28331 signalled to NAME PROJ
28332
28333
28334 Stream: as severity 1
28335
28336 Time: In response to an operator command.
28337
28338 Meaning: An operator terminate command specified a
28339 nonexistent channel name or user name and project.
28340 No action was taken on the command.
28341
28342 Action: Enter a corrected command line.
28343
28344
28345 operator_process_cmds_.pl1
28346 operator_process_cmds_: unbump: error: invalid
28347 arguments
28348
28349
28350 Stream: as severity 1
28351
28352 Time: In response to an operator command.
28353
28354 Meaning: A bad argument has been typed to the unbump
28355 command. No action was taken.
28356
28357 Action: Enter a corrected command line.
28358
28359
28360 operator_process_cmds_.pl1
28361 operator_process_cmds_: unbump: NAME.PROJ
28362 unbumped
28363
28364
28365 Stream: as severity 1
28366
28367 Time: In response to an operator command.
28368
28369 Meaning: This is the response to an operator unbump
28370 command. The user affected is named.
28371
28372 Action: No operator action is required.
28373
28374
28375
28376 operator_process_cmds_ 490 08/21/20 MR12.7^L
28377
28378
28379
28380
28381 operator_process_cmds_.pl1
28382 operator_process_cmds_: unbump: no unbump
28383 signalled to NAME PROJ
28384
28385
28386 Stream: as severity 1
28387
28388 Time: In response to an operator command.
28389
28390 Meaning: An operator unbump command specified a nonexistent
28391 channel name or user name and project or the user
28392 specified was not in a bumped state. No action
28393 was taken on the command.
28394
28395 Action: Enter a corrected command line.
28396
28397
28398 page_error.alm
28399 page_fault: Deleting main memory at AAAA SCU
28400 TAG due to parity errors.
28401
28402
28403
28404 Stream: BOS Typewriter sounds beeper
28405
28406 Time: While system is running.
28407
28408 Meaning: Due to main memory parity errors the system is
28409 automatically removing a page of main memory from
28410 the memory in SCU TAG preventing further use
28411 during this bootload.
28412
28413 Action: Inform Field Engineering personnel about possible
28414 problems with this SCU.
28415
28416
28417
28418 page_error.alm
28419 page_fault: Deleting main memory at AAAA SCU
28420 TAG due to parity errors.
28421
28422
28423
28424 Stream: BOS Typewriter sounds beeper
28425
28426 Time: While system is running.
28427
28428 Meaning: Due to main memory parity errors the system is
28429 automatically removing a page of main memory from
28430 the memory in SCU TAG preventing further use
28431 during this bootload.
28432
28433
28434 page_fault 491 08/21/20 MR12.7^L
28435
28436
28437 Action: Inform Field Engineering personnel about possible
28438 problems with this SCU.
28439
28440
28441
28442 page_error.alm
28443 page_fault: device read not complete DSKX_NNS
28444 DDDD
28445
28446
28447 Stream: BOS Typewriter Crashes system
28448
28449 Time: While system is running.
28450
28451 Meaning: This message is used for program debugging only.
28452
28453 Action: Follow normal recovery procedures. Contact the
28454 system programming staff.
28455
28456
28457
28458 page_error.alm
28459 page_fault: device read not complete DSKX_NNS
28460 DDDD
28461
28462
28463 Stream: BOS Typewriter Crashes system
28464
28465 Time: While system is running.
28466
28467 Meaning: This message is used for program debugging only.
28468
28469 Action: Follow normal recovery procedures. Contact the
28470 system programming staff.
28471
28472
28473
28474 page_error.alm
28475 page_fault: fatal error at loc AAAA
28476
28477
28478 Stream: BOS Typewriter Crashes system
28479
28480 Time: While system is running.
28481
28482 Meaning: This indicates a logic error in the supervisor or
28483 CPU or memory hardware problems.
28484
28485 Action: Follow normal recovery procedures.
28486
28487
28488 page_error.alm
28489 page_fault: fatal error at loc AAAA
28490
28491
28492 page_fault 492 08/21/20 MR12.7^L
28493
28494
28495 Stream: BOS Typewriter Crashes system
28496
28497 Time: While system is running.
28498
28499 Meaning: This indicates a logic error in the supervisor or
28500 CPU or memory hardware problems.
28501
28502 Action: Follow normal recovery procedures.
28503
28504
28505 page_error.alm
28506 page_fault: fatal error in done ptp ZZZZ
28507
28508
28509 Stream: BOS Typewriter Crashes system
28510
28511 Time: While system is running.
28512
28513 Meaning: While posting an I/O completion the system found
28514 a page table pointer of zero or found that the
28515 page was not out of service. This indicates a
28516 logic error in the supervisor or CPU or memory
28517 hardware problems.
28518
28519 Action: Follow normal recovery procedures.
28520
28521
28522 page_error.alm
28523 page_fault: fatal error in done ptp ZZZZ
28524
28525
28526 Stream: BOS Typewriter Crashes system
28527
28528 Time: While system is running.
28529
28530 Meaning: While posting an I/O completion the system found
28531 a page table pointer of zero or found that the
28532 page was not out of service. This indicates a
28533 logic error in the supervisor or CPU or memory
28534 hardware problems.
28535
28536 Action: Follow normal recovery procedures.
28537
28538
28539 page_error.alm
28540 page_fault: mylock on global lock
28541
28542
28543 Stream: BOS Typewriter Crashes system
28544
28545 Time: While system is running.
28546
28547
28548
28549
28550 page_fault 493 08/21/20 MR12.7^L
28551
28552
28553 Meaning: When page_fault attempted to lock the global page
28554 control lock it found it already locked to the
28555 same process. This indicates a logic error in the
28556 supervisor or CPU or memory hardware problems.
28557
28558 Action: Follow normal recovery procedures.
28559
28560
28561 page_error.alm
28562 page_fault: mylock on global lock
28563
28564
28565 Stream: BOS Typewriter Crashes system
28566
28567 Time: While system is running.
28568
28569 Meaning: When page_fault attempted to lock the global page
28570 control lock it found it already locked to the
28571 same process. This indicates a logic error in the
28572 supervisor or CPU or memory hardware problems.
28573
28574 Action: Follow normal recovery procedures.
28575
28576
28577 page_error.alm
28578 page_fault: nonfatal error at loc AAAA
28579
28580
28581 Stream: BOS Typewriter.
28582
28583 Time: While system is running.
28584
28585 Meaning: This indicates a logic error in the supervisor or
28586 CPU or memory hardware problems. The system
28587 attempts to keep running.
28588
28589 Action: No operator action is required.
28590
28591
28592 page_error.alm
28593 page_fault: nonfatal error at loc AAAA
28594
28595
28596 Stream: BOS Typewriter.
28597
28598 Time: While system is running.
28599
28600 Meaning: This indicates a logic error in the supervisor or
28601 CPU or memory hardware problems. The system
28602 attempts to keep running.
28603
28604 Action: No operator action is required.
28605
28606
28607
28608 page_fault 494 08/21/20 MR12.7^L
28609
28610
28611
28612
28613 page_error.alm
28614 page_fault: out of main memory
28615
28616
28617 Stream: BOS Typewriter Crashes system
28618
28619 Time: While system is running.
28620
28621 Meaning: The page removal algorithm was unable to find a
28622 removable page. Incorrect system programmer
28623 action damage to the AST or an error in the
28624 supervisor or the hardware could cause this
28625 symptom.
28626
28627 Action: Follow normal recovery procedures.
28628
28629
28630 page_error.alm
28631 page_fault: out of main memory
28632
28633
28634 Stream: BOS Typewriter Crashes system
28635
28636 Time: While system is running.
28637
28638 Meaning: The page removal algorithm was unable to find a
28639 removable page. Incorrect system programmer
28640 action damage to the AST or an error in the
28641 supervisor or the hardware could cause this
28642 symptom.
28643
28644 Action: Follow normal recovery procedures.
28645
28646
28647 page_error.alm
28648 page_fault: Reverting page on DSKX_NNS
28649
28650
28651 Stream: BOS Typewriter.
28652
28653 Time: While system is running.
28654
28655 Meaning: A segment residing on DSKX_NNS has had one of
28656 its pages reverted to an earlier copy of the same
28657 page. The damaged switch is set. This can happen
28658 due to device error or main memory errors.
28659 Subsequent user processes attempting to use this
28660 segment will receive an error indication. Binary
28661 information identifying the damaged segment is
28662 encoded into this message for subsequent automatic
28663 processing. The pathname of the damaged segment
28664
28665
28666 page_fault 495 08/21/20 MR12.7^L
28667
28668
28669 will appear in a message in the answering service
28670 log bearing the syserr log sequence number of
28671 this message shortly after this message occurs.
28672
28673 Action: Attempt to identify the damaged segment and inform
28674 its owner.
28675
28676
28677 page_error.alm
28678 page_fault: Reverting page on DSKX_NNS
28679
28680
28681 Stream: BOS Typewriter.
28682
28683 Time: While system is running.
28684
28685 Meaning: A segment residing on DSKX_NNS has had one of
28686 its pages reverted to an earlier copy of the same
28687 page. The damaged switch is set. This can happen
28688 due to device error or main memory errors.
28689 Subsequent user processes attempting to use this
28690 segment will receive an error indication. Binary
28691 information identifying the damaged segment is
28692 encoded into this message for subsequent automatic
28693 processing. The pathname of the damaged segment
28694 will appear in a message in the answering service
28695 log bearing the syserr log sequence number of
28696 this message shortly after this message occurs.
28697
28698 Action: Attempt to identify the damaged segment and inform
28699 its owner.
28700
28701
28702 page_error.alm
28703 page_fault: Zeroing page on DSKX_NNS
28704
28705
28706 Stream: BOS Typewriter.
28707
28708 Time: While system is running.
28709
28710 Meaning: A segment residing on DSKX_NNS has been damaged
28711 due to a device error. The segment damaged switch
28712 is set and a page of zeros is introduced into the
28713 segment. Subsequent user processes attempting to
28714 use this segment will receive an error indication.
28715 Binary information identifying the damaged segment
28716 is encoded into this message for subsequent
28717 automatic processing. The pathname of the damaged
28718 segment will appear in a message in the answering
28719 service log bearing the syserr_log sequence
28720 number of this message shortly after this message
28721 occurs.
28722
28723
28724 page_fault 496 08/21/20 MR12.7^L
28725
28726
28727 Action: Attempt to identify the damaged segment and
28728 inform its owner.
28729
28730
28731
28732 page_error.alm
28733 page_fault: Zeroing page on DSKX_NNS
28734
28735
28736 Stream: BOS Typewriter.
28737
28738 Time: While system is running.
28739
28740 Meaning: A segment residing on DSKX_NNS has been damaged
28741 due to a device error. The segment damaged switch
28742 is set and a page of zeros is introduced into the
28743 segment. Subsequent user processes attempting to
28744 use this segment will receive an error indication.
28745 Binary information identifying the damaged segment
28746 is encoded into this message for subsequent
28747 automatic processing. The pathname of the damaged
28748 segment will appear in a message in the answering
28749 service log bearing the syserr_log sequence
28750 number of this message shortly after this message
28751 occurs.
28752
28753 Action: Attempt to identify the damaged segment and
28754 inform its owner.
28755
28756
28757
28758 page_error.alm
28759 page_synch: dm_journal_seg_ inconsistent.
28760
28761
28762 Time: While system is running.
28763
28764 Stream: BOS Typewriter Crashes system
28765
28766 Meaning: This indicates a logic error in the supervisor or
28767 CPU or memory hardware problems.
28768
28769 Action: Follow normal recovery procedures.
28770
28771
28772 page_error.alm
28773 page_synch: dm_journal_seg_ inconsistent.
28774
28775
28776 Time: While system is running.
28777
28778 Stream: BOS Typewriter Crashes system
28779
28780
28781
28782 page_synch 497 08/21/20 MR12.7^L
28783
28784
28785 Meaning: This indicates a logic error in the supervisor or
28786 CPU or memory hardware problems.
28787
28788 Action: Follow normal recovery procedures.
28789
28790
28791 page_error.alm
28792 page_synch: Out of free entries in
28793 dm_journal_seg_.
28794
28795
28796 Time: While system is running.
28797
28798 Stream: BOS Typewriter Crashes system
28799
28800 Meaning: This indicates a logic error in the supervisor or
28801 CPU or memory hardware problems.
28802
28803 Action: Follow normal recovery procedures.
28804
28805
28806 page_error.alm
28807 page_synch: Out of free entries in
28808 dm_journal_seg_.
28809
28810
28811 Time: While system is running.
28812
28813 Stream: BOS Typewriter Crashes system
28814
28815 Meaning: This indicates a logic error in the supervisor or
28816 CPU or memory hardware problems.
28817
28818 Action: Follow normal recovery procedures.
28819
28820
28821 pc.pl1.pmac
28822 pc: truncate_deposit_all call on VTOCed seg at
28823 ASTEP
28824
28825
28826 Stream: BOS Typewriter Crashes system
28827
28828 Time: While system is running.
28829
28830 Meaning: A call to pc$truncate_deposit_all has been made on
28831 a segment for which this operation is not allowed.
28832 The AST entry at ASTEP should have a zero unique
28833 ID but it does not. This indicates a logic error
28834 in the supervisor or CPU or memory hardware
28835 problems. BOS Typewriter Crashes systemes
28836
28837 Action: Follow normal recovery procedures.
28838
28839
28840 pc 498 08/21/20 MR12.7^L
28841
28842
28843
28844
28845 pc.pl1.pmac
28846 pc: truncate_deposit_all call on VTOCed seg at
28847 ASTEP
28848
28849
28850 Stream: BOS Typewriter Crashes system
28851
28852 Time: While system is running.
28853
28854 Meaning: A call to pc$truncate_deposit_all has been made on
28855 a segment for which this operation is not allowed.
28856 The AST entry at ASTEP should have a zero unique
28857 ID but it does not. This indicates a logic error
28858 in the supervisor or CPU or memory hardware
28859 problems. BOS Typewriter Crashes systemes
28860
28861 Action: Follow normal recovery procedures.
28862
28863
28864 pc.pl1.pmac
28865 pc: unprotected address DDDDD in DSKX_NN VTOCX
28866
28867
28868 Stream: BOS Typewriter.
28869
28870 Time: While system is running.
28871
28872 Meaning: The disk address DDDDD is not marked as protected
28873 in the record usage map for the volume mounted on
28874 DSKX_NN. This condition has been discovered while
28875 activating the segment with VTOC index VTOCX. The
28876 segment's damaged switch is turned on and a page
28877 of zeros will replace the bad address. This
28878 condition may be symptomatic of disk or other
28879 hardware failure.
28880
28881 Action: Contact the system programming staff.
28882
28883
28884 pc.pl1.pmac
28885 pc: unprotected address DDDDD in DSKX_NN VTOCX
28886
28887
28888 Stream: BOS Typewriter.
28889
28890 Time: While system is running.
28891
28892 Meaning: The disk address DDDDD is not marked as protected
28893 in the record usage map for the volume mounted on
28894 DSKX_NN. This condition has been discovered while
28895 activating the segment with VTOC index VTOCX. The
28896
28897
28898 pc 499 08/21/20 MR12.7^L
28899
28900
28901 segment's damaged switch is turned on and a page
28902 of zeros will replace the bad address. This
28903 condition may be symptomatic of disk or other
28904 hardware failure.
28905
28906 Action: Contact the system programming staff.
28907
28908
28909 pc_abs.pl1.pmac
28910 pc_abs$unwire_abs: Attempt to unwire inconsistent
28911 CME at CMEP.
28912
28913
28914 Stream: BOS Typewriter Crashes system
28915
28916 Time: While system is running.
28917
28918 Meaning: The core map entry for the page being abs unwired
28919 did not have the abs_w flag on which indicates
28920 that it was properly abs wired. This indicates a
28921 logic error in the supervisor or CPU or memory
28922 hardware problems.
28923
28924 Action: Contact the system programming staff. Follow
28925 normal recovery procedures.
28926
28927
28928
28929 pc_abs.pl1.pmac
28930 pc_abs$unwire_abs: Attempt to unwire inconsistent
28931 CME at CMEP.
28932
28933
28934 Stream: BOS Typewriter Crashes system
28935
28936 Time: While system is running.
28937
28938 Meaning: The core map entry for the page being abs unwired
28939 did not have the abs_w flag on which indicates
28940 that it was properly abs wired. This indicates a
28941 logic error in the supervisor or CPU or memory
28942 hardware problems.
28943
28944 Action: Contact the system programming staff. Follow
28945 normal recovery procedures.
28946
28947
28948
28949 pc_abs.pl1.pmac
28950 pc_abs$unwire_abs: Attempt to unwire inconsistent
28951 PTW at PTP.
28952
28953
28954
28955
28956 pc_abs$unwire_abs 500 08/21/20 MR12.7^L
28957
28958
28959 Stream: BOS Typewriter Crashes system
28960
28961 Time: While system is running.
28962
28963 Meaning: A page at PTP within the range of pages being
28964 unwired for was found to either not be wired or
28965 no longer in memory. This indicates a logic error
28966 in the supervisor or CPU or memory hardware
28967 problems.
28968
28969 Action: Contact the system programming staff. Follow
28970 normal recovery procedures.
28971
28972
28973
28974 pc_abs.pl1.pmac
28975 pc_abs$unwire_abs: Attempt to unwire inconsistent
28976 PTW at PTP.
28977
28978
28979 Stream: BOS Typewriter Crashes system
28980
28981 Time: While system is running.
28982
28983 Meaning: A page at PTP within the range of pages being
28984 unwired for was found to either not be wired or
28985 no longer in memory. This indicates a logic error
28986 in the supervisor or CPU or memory hardware
28987 problems.
28988
28989 Action: Contact the system programming staff. Follow
28990 normal recovery procedures.
28991
28992
28993
28994 pc_abs.pl1.pmac
28995 pc_abs$unwire_abs: Called with NULL astep.
28996
28997
28998 Stream: BOS Typewriter Crashes system
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.
29004
29005 Action: Contact the system programming staff. Follow
29006 normal recovery procedures.
29007
29008
29009
29010 pc_abs.pl1.pmac
29011 pc_abs$unwire_abs: Called with NULL astep.
29012
29013
29014 pc_abs$unwire_abs 501 08/21/20 MR12.7^L
29015
29016
29017 Stream: BOS Typewriter Crashes system
29018
29019 Time: While system is running.
29020
29021 Meaning: This indicates a logic error in the supervisor or
29022 CPU or memory hardware problems.
29023
29024 Action: Contact the system programming staff. Follow
29025 normal recovery procedures.
29026
29027
29028
29029 pc_abs.pl1.pmac
29030 pc_abs: Parity error in I/O buffer.
29031
29032
29033 Stream: BOS Typewriter Crashes system
29034
29035 Time: While system is running.
29036
29037 Meaning: This indicates a logic error in the supervisor or
29038 CPU or memory hardware problems.
29039
29040 Action: Follow normal recovery procedures.
29041
29042
29043 pc_abs.pl1.pmac
29044 pc_abs: Parity error in I/O buffer.
29045
29046
29047 Stream: BOS Typewriter Crashes system
29048
29049 Time: While system is running.
29050
29051 Meaning: This indicates a logic error in the supervisor or
29052 CPU or memory hardware problems.
29053
29054 Action: Follow normal recovery procedures.
29055
29056
29057 pc_deposit.pl1
29058 pc_deposit: Address XXXXXX out of paging region
29059 on dskX_NNs.
29060
29061
29062 Stream: BOS Typewriter Crashes system
29063
29064 Time: While system is running.
29065
29066 Meaning: An attempt was made to return disk address XXXXXX
29067 on device dskX_NNs to the free pool. The
29068 address is not in the paging region.
29069
29070
29071
29072 pc_deposit 502 08/21/20 MR12.7^L
29073
29074
29075 Action: Follow normal recovery procedures. It may be
29076 necessary to run the physical volume salvager on
29077 the device.
29078
29079
29080
29081 pc_deposit.pl1
29082 pc_deposit: Address XXXXXX out of paging region
29083 on dskX_NNs.
29084
29085
29086 Stream: BOS Typewriter Crashes system
29087
29088 Time: While system is running.
29089
29090 Meaning: An attempt was made to return disk address XXXXXX
29091 on device dskX_NNs to the free pool. The
29092 address is not in the paging region.
29093
29094 Action: Follow normal recovery procedures. It may be
29095 necessary to run the physical volume salvager on
29096 the device.
29097
29098
29099
29100 pc_deposit.pl1
29101 pc_deposit: Deposit in-use address XXXXXX on
29102 dskX_NNs.
29103
29104
29105 Stream: BOS Typewriter sounds beeper
29106
29107 Time: While system is running.
29108
29109 Meaning: An attempt was made to return address XXXXXX on
29110 device dskX_NNs to the free record pool but the
29111 address was already marked as free. This
29112 indicates damage to control structures on the
29113 device. This damage can be corrected by a
29114 physical volume salvage.
29115
29116 Action: Contact the system programming staff.
29117
29118
29119 pc_deposit.pl1
29120 pc_deposit: Deposit in-use address XXXXXX on
29121 dskX_NNs.
29122
29123
29124 Stream: BOS Typewriter sounds beeper
29125
29126 Time: While system is running.
29127
29128
29129
29130 pc_deposit 503 08/21/20 MR12.7^L
29131
29132
29133 Meaning: An attempt was made to return address XXXXXX on
29134 device dskX_NNs to the free record pool but the
29135 address was already marked as free. This
29136 indicates damage to control structures on the
29137 device. This damage can be corrected by a
29138 physical volume salvage.
29139
29140 Action: Contact the system programming staff.
29141
29142
29143 pc_deposit.pl1
29144 pc_deposit: Invalid address XXXXXX on dskX_NNs.
29145
29146
29147 Stream: BOS Typewriter Crashes system
29148
29149 Time: While system is running.
29150
29151 Meaning: In attempting to deposit address XXXXXX on device
29152 dskX_NNs an invalid volume map offset was
29153 computed.
29154
29155 Action: Follow normal recovery procedures. It may be
29156 necessary to run the physical volume salvager on
29157 the device.
29158
29159
29160
29161 pc_deposit.pl1
29162 pc_deposit: Invalid address XXXXXX on dskX_NNs.
29163
29164
29165 Stream: BOS Typewriter Crashes system
29166
29167 Time: While system is running.
29168
29169 Meaning: In attempting to deposit address XXXXXX on device
29170 dskX_NNs an invalid volume map offset was
29171 computed.
29172
29173 Action: Follow normal recovery procedures. It may be
29174 necessary to run the physical volume salvager on
29175 the device.
29176
29177
29178
29179 pc_deposit.pl1
29180 pc_deposit: Unrecoverable I/O error on Volmap
29181 page M of dskX_NNs. Addresses lost.
29182
29183
29184 Stream: BOS Typewriter sounds beeper
29185
29186
29187
29188 pc_deposit 504 08/21/20 MR12.7^L
29189
29190
29191 Time: While system is running.
29192
29193 Meaning: There was an unrecoverable I/O error on a page of
29194 the Volume Map which describes free records of
29195 the volume. All free records described by that
29196 page have been lost.
29197
29198 Action: It may be possible to recover the lost addresses
29199 by a volume salvage. If there is a hard device
29200 error the volume salvage will fail. In this
29201 case it will be necessary to recover the volume
29202 onto a good pack.
29203
29204
29205
29206 pc_deposit.pl1
29207 pc_deposit: Unrecoverable I/O error on Volmap
29208 page M of dskX_NNs. Addresses lost.
29209
29210
29211 Stream: BOS Typewriter sounds beeper
29212
29213 Time: While system is running.
29214
29215 Meaning: There was an unrecoverable I/O error on a page of
29216 the Volume Map which describes free records of
29217 the volume. All free records described by that
29218 page have been lost.
29219
29220 Action: It may be possible to recover the lost addresses
29221 by a volume salvage. If there is a hard device
29222 error the volume salvage will fail. In this
29223 case it will be necessary to recover the volume
29224 onto a good pack.
29225
29226
29227
29228 ring_0_peek.pl1
29229 PERSON.PROJ.T: MESSAGE
29230
29231
29232 Stream: BOS Typewriter sounds beeper
29233
29234 Time: While system is running.
29235
29236 Meaning: A privileged user has sent a message to be printed
29237 on the SYSERR console.
29238
29239 Action: Read the message and take appropriate action.
29240
29241
29242 ring_0_peek.pl1
29243 PERSON.PROJ.T: NN words @ SSS|XXX
29244
29245
29246 PERSON.PROJ.T 505 08/21/20 MR12.7^L
29247
29248
29249 XXX WWWWWWWWWWWW to YYYYYYYYYYYY
29250 XXX WWWWWWWWWWWW to YYYYYYYYYYYY
29251
29252
29253
29254 Stream: BOS Typewriter sounds beeper
29255
29256 Time: While system is running.
29257
29258 Meaning: A privileged user has patched the hardcore
29259 supervisor.
29260
29261 Action: No operator action is required.
29262
29263
29264 prds_init.pl1
29265 prds_init: Invalid size for
29266 prds$fast_connect_code
29267
29268
29269 Stream: BOS Typewriter Crashes system
29270
29271 Time: System Intialization.
29272
29273 Meaning: There is an inconsistency between modules prds and
29274 fast_connect_init on the boot tape. Specifically
29275 the amount of space allocated for fast connect
29276 code in the prds does not agree with the size of
29277 the code in fast_connect_init. The most likely
29278 cause is that one of these modules is not up to
29279 date.
29280
29281 Action: Contact the system programming staff._sa A new
29282 boot tape must be generated with the proper
29283 versions of modules prds and fast_connect_init.
29284
29285
29286
29287 priv_delete_vtoce.pl1
29288 priv_delete_vtoce: failed to lock WWWWWW
29289 ERROR_MESSAGE
29290
29291
29292 Stream: BOS Typewriter Crashes system
29293
29294 Time: While system is running.
29295
29296 Meaning: An attempt to lock a directory has failed. This
29297 indicates a logic error in the supervisor or CPU
29298 or memory hardware problems.
29299
29300 Action: Follow normal recovery procedures. $boot_tape
29301
29302
29303
29304 proc_int_handler 506 08/21/20 MR12.7^L
29305
29306
29307
29308
29309 proc_int_handler.pl1
29310 proc_int_handler: Invalid IPS interrupts
29311 IPS_BITS for USERNAME.
29312
29313
29314 Stream: BOS Typewriter.
29315
29316 Time: While system is running.
29317
29318 Meaning: One or more undefined IPS messages as indicated by
29319 IPS_BITS have been sent to user USERNAME. They
29320 are ignored.
29321
29322 Action: Contact the system programming staff.
29323
29324
29325 proc_int_handler.pl1
29326 proc_int_handler: Invalid IPS interrupts
29327 IPS_BITS for USERNAME.
29328
29329
29330 Stream: BOS Typewriter.
29331
29332 Time: While system is running.
29333
29334 Meaning: One or more undefined IPS messages as indicated by
29335 IPS_BITS have been sent to user USERNAME. They
29336 are ignored.
29337
29338 Action: Contact the system programming staff.
29339
29340
29341 pxss.alm
29342 pxss: APT not locked
29343
29344
29345
29346 Stream: BOS Typewriter Crashes system
29347
29348 Time: While system is running.
29349
29350 Meaning: This indicates a logic error in the supervisor or
29351 CPU or memory hardware problems.
29352
29353 Action: Follow normal recovery procedures.
29354
29355
29356
29357 pxss.alm
29358 pxss: APT not locked
29359
29360
29361
29362 pxss 507 08/21/20 MR12.7^L
29363
29364
29365 Stream: BOS Typewriter Crashes system
29366
29367 Time: While system is running.
29368
29369 Meaning: This indicates a logic error in the supervisor or
29370 CPU or memory hardware problems.
29371
29372 Action: Follow normal recovery procedures.
29373
29374
29375
29376 pxss.alm
29377 pxss: APT not locked
29378
29379
29380
29381 Stream: BOS Typewriter Crashes system
29382
29383 Time: While system is running.
29384
29385 Meaning: This indicates a logic error in the supervisor or
29386 CPU or memory hardware problems.
29387
29388 Action: Follow normal recovery procedures.
29389
29390
29391
29392 pxss.alm
29393 pxss: APTE disdains all processors
29394
29395
29396
29397 Stream: BOS Typewriter Crashes system
29398
29399 Time: While system is running.
29400
29401 Meaning: This indicates a logic error in the supervisor or
29402 CPU or memory hardware problems. " There are no
29403 processors-required set for this APTE.
29404
29405 Action: Follow normal recovery procedures.
29406
29407
29408
29409 pxss.alm
29410 pxss: APTE disdains all processors
29411
29412
29413
29414 Stream: BOS Typewriter Crashes system
29415
29416 Time: While system is running.
29417
29418
29419
29420 pxss 508 08/21/20 MR12.7^L
29421
29422
29423 Meaning: This indicates a logic error in the supervisor or
29424 CPU or memory hardware problems. " There are no
29425 processors-required set for this APTE.
29426
29427 Action: Follow normal recovery procedures.
29428
29429
29430
29431 pxss.alm
29432 pxss: APTE disdains all processors
29433
29434
29435
29436 Stream: BOS Typewriter Crashes system
29437
29438 Time: While system is running.
29439
29440 Meaning: This indicates a logic error in the supervisor or
29441 CPU or memory hardware problems. " There are no
29442 processors-required set for this APTE.
29443
29444 Action: Follow normal recovery procedures.
29445
29446
29447
29448 pxss.alm
29449 pxss: APTE not locked
29450
29451
29452
29453 Stream: BOS Typewriter Crashes system
29454
29455 Time: While system is running.
29456
29457 Meaning: This indicates a logic error in the supervisor or
29458 CPU or memory hardware problems.
29459
29460 Action: Follow normal recovery procedures.
29461
29462
29463
29464 pxss.alm
29465 pxss: APTE not locked
29466
29467
29468
29469 Stream: BOS Typewriter Crashes system
29470
29471 Time: While system is running.
29472
29473 Meaning: This indicates a logic error in the supervisor or
29474 CPU or memory hardware problems.
29475
29476
29477
29478 pxss 509 08/21/20 MR12.7^L
29479
29480
29481 Action: Follow normal recovery procedures.
29482
29483
29484
29485 pxss.alm
29486 pxss: APTE not locked
29487
29488
29489
29490 Stream: BOS Typewriter Crashes system
29491
29492 Time: While system is running.
29493
29494 Meaning: This indicates a logic error in the supervisor or
29495 CPU or memory hardware problems.
29496
29497 Action: Follow normal recovery procedures.
29498
29499
29500
29501 pxss.alm
29502 pxss: apte.state ^= ready
29503
29504
29505
29506 Stream: BOS Typewriter Crashes system
29507
29508 Time: While system is running.
29509
29510 Meaning: This indicates a logic error in the supervisor or
29511 CPU or memory hardware problems.
29512
29513 Action: Follow normal recovery procedures.
29514
29515
29516
29517 pxss.alm
29518 pxss: apte.state ^= ready
29519
29520
29521
29522 Stream: BOS Typewriter Crashes system
29523
29524 Time: While system is running.
29525
29526 Meaning: This indicates a logic error in the supervisor or
29527 CPU or memory hardware problems.
29528
29529 Action: Follow normal recovery procedures.
29530
29531
29532
29533
29534
29535
29536 pxss 510 08/21/20 MR12.7^L
29537
29538
29539
29540
29541 pxss.alm
29542 pxss: apte.state ^= ready
29543
29544
29545
29546 Stream: BOS Typewriter Crashes system
29547
29548 Time: While system is running.
29549
29550 Meaning: This indicates a logic error in the supervisor or
29551 CPU or memory hardware problems.
29552
29553 Action: Follow normal recovery procedures.
29554
29555
29556
29557 pxss.alm
29558 pxss: empty_t APTE not stopped or empty
29559
29560
29561
29562 Stream: BOS Typewriter Crashes system
29563
29564 Time: While system is running.
29565
29566 Meaning: This indicates a logic error in the supervisor or
29567 CPU or memory hardware problems. " an attempt was
29568 made to clear an APTE that of a process that was
29569 neither " stopped nor empty.
29570
29571 Action: Follow normal recovery procedures.
29572
29573
29574
29575 pxss.alm
29576 pxss: empty_t APTE not stopped or empty
29577
29578
29579
29580 Stream: BOS Typewriter Crashes system
29581
29582 Time: While system is running.
29583
29584 Meaning: This indicates a logic error in the supervisor or
29585 CPU or memory hardware problems. " an attempt was
29586 made to clear an APTE that of a process that was
29587 neither " stopped nor empty.
29588
29589 Action: Follow normal recovery procedures.
29590
29591
29592
29593
29594 pxss 511 08/21/20 MR12.7^L
29595
29596
29597
29598
29599 pxss.alm
29600 pxss: empty_t APTE not stopped or empty
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. " an attempt was
29610 made to clear an APTE that of a process that was
29611 neither " stopped nor empty.
29612
29613 Action: Follow normal recovery procedures.
29614
29615
29616
29617 pxss.alm
29618 pxss: freeing unknown stack_0
29619
29620
29621
29622 Stream: BOS Typewriter Crashes system
29623
29624 Time: While system is running.
29625
29626 Meaning: This indicates a logic error in the supervisor or
29627 CPU or memory hardware problems. " the stack_0
29628 being returned could not be found in the list of
29629 stack_0s.
29630
29631 Action: Follow normal recovery procedures.
29632
29633
29634
29635 pxss.alm
29636 pxss: freeing unknown stack_0
29637
29638
29639
29640 Stream: BOS Typewriter Crashes system
29641
29642 Time: While system is running.
29643
29644 Meaning: This indicates a logic error in the supervisor or
29645 CPU or memory hardware problems. " the stack_0
29646 being returned could not be found in the list of
29647 stack_0s.
29648
29649 Action: Follow normal recovery procedures.
29650
29651
29652 pxss 512 08/21/20 MR12.7^L
29653
29654
29655
29656
29657 pxss.alm
29658 pxss: freeing unknown stack_0
29659
29660
29661
29662 Stream: BOS Typewriter Crashes system
29663
29664 Time: While system is running.
29665
29666 Meaning: This indicates a logic error in the supervisor or
29667 CPU or memory hardware problems. " the stack_0
29668 being returned could not be found in the list of
29669 stack_0s.
29670
29671 Action: Follow normal recovery procedures.
29672
29673
29674
29675 pxss.alm
29676 pxss: ITT overflows
29677
29678
29679
29680 Stream: BOS Typewriter Crashes system
29681
29682 Time: While system is running.
29683
29684 Meaning: This indicates a logic error in the supervisor or
29685 CPU or memory hardware problems.
29686
29687 Action: Follow normal recovery procedures.
29688
29689
29690
29691 pxss.alm
29692 pxss: ITT overflows
29693
29694
29695
29696 Stream: BOS Typewriter Crashes system
29697
29698 Time: While system is running.
29699
29700 Meaning: This indicates a logic error in the supervisor or
29701 CPU or memory hardware problems.
29702
29703 Action: Follow normal recovery procedures.
29704
29705
29706
29707
29708
29709
29710 pxss 513 08/21/20 MR12.7^L
29711
29712
29713
29714
29715 pxss.alm
29716 pxss: ITT overflows
29717
29718
29719
29720 Stream: BOS Typewriter Crashes system
29721
29722 Time: While system is running.
29723
29724 Meaning: This indicates a logic error in the supervisor or
29725 CPU or memory hardware problems.
29726
29727 Action: Follow normal recovery procedures.
29728
29729
29730
29731 pxss.alm
29732 pxss: lock_stack_queue stac failed
29733
29734
29735
29736 Stream: BOS Typewriter Crashes system
29737
29738 Time: While system is running.
29739
29740 Meaning: This indicates a logic error in the supervisor or
29741 CPU or memory hardware problems. " This indicates
29742 a hardware error.
29743
29744 Action: Follow normal recovery procedures.
29745
29746
29747
29748 pxss.alm
29749 pxss: lock_stack_queue stac failed
29750
29751
29752
29753 Stream: BOS Typewriter Crashes system
29754
29755 Time: While system is running.
29756
29757 Meaning: This indicates a logic error in the supervisor or
29758 CPU or memory hardware problems. " This indicates
29759 a hardware error.
29760
29761 Action: Follow normal recovery procedures.
29762
29763
29764
29765
29766
29767
29768 pxss 514 08/21/20 MR12.7^L
29769
29770
29771
29772
29773 pxss.alm
29774 pxss: lock_stack_queue stac failed
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. " This indicates
29784 a hardware error.
29785
29786 Action: Follow normal recovery procedures.
29787
29788
29789
29790 pxss.alm
29791 pxss: mylock on stack queue
29792
29793
29794
29795 Stream: BOS Typewriter Crashes system
29796
29797 Time: While system is running.
29798
29799 Meaning: This indicates a logic error in the supervisor or
29800 CPU or memory hardware problems.
29801
29802 Action: Follow normal recovery procedures.
29803
29804
29805
29806 pxss.alm
29807 pxss: mylock on stack queue
29808
29809
29810
29811 Stream: BOS Typewriter Crashes system
29812
29813 Time: While system is running.
29814
29815 Meaning: This indicates a logic error in the supervisor or
29816 CPU or memory hardware problems.
29817
29818 Action: Follow normal recovery procedures.
29819
29820
29821
29822 pxss.alm
29823 pxss: mylock on stack queue
29824
29825
29826 pxss 515 08/21/20 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: no available stack_0
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: no available stack_0
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: no available stack_0
29874
29875
29876
29877 Stream: BOS Typewriter Crashes system
29878
29879 Time: While system is running.
29880
29881
29882
29883
29884 pxss 516 08/21/20 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: no stack_0 sdw
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: no stack_0 sdw
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.
29921
29922 Action: Follow normal recovery procedures.
29923
29924
29925
29926 pxss.alm
29927 pxss: no stack_0 sdw
29928
29929
29930
29931 Stream: BOS Typewriter Crashes system
29932
29933 Time: While system is running.
29934
29935 Meaning: This indicates a logic error in the supervisor or
29936 CPU or memory hardware problems.
29937
29938 Action: Follow normal recovery procedures.
29939
29940
29941
29942 pxss 517 08/21/20 MR12.7^L
29943
29944
29945
29946
29947 pxss.alm
29948 pxss: No term_processid
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. " As a process
29958 was about to indicate its demise to the master
29959 process " it discovered to its chagrin that it
29960 had forgotten who that was.
29961
29962 Action: Follow normal recovery procedures.
29963
29964
29965
29966 pxss.alm
29967 pxss: No term_processid
29968
29969
29970
29971 Stream: BOS Typewriter Crashes system
29972
29973 Time: While system is running.
29974
29975 Meaning: This indicates a logic error in the supervisor or
29976 CPU or memory hardware problems. " As a process
29977 was about to indicate its demise to the master
29978 process " it discovered to its chagrin that it
29979 had forgotten who that was.
29980
29981 Action: Follow normal recovery procedures.
29982
29983
29984
29985 pxss.alm
29986 pxss: No term_processid
29987
29988
29989
29990 Stream: BOS Typewriter Crashes system
29991
29992 Time: While system is running.
29993
29994 Meaning: This indicates a logic error in the supervisor or
29995 CPU or memory hardware problems. " As a process
29996 was about to indicate its demise to the master
29997
29998
29999
30000 pxss 518 08/21/20 MR12.7^L
30001
30002
30003 process " it discovered to its chagrin that it
30004 had forgotten who that was.
30005
30006 Action: Follow normal recovery procedures.
30007
30008
30009
30010 pxss.alm
30011 pxss: notify time out: event=ZZZZZZZZZZZZ.
30012 During init/shutdown.
30013
30014
30015 Stream: BOS Typewriter.
30016
30017 Time: System Intialization.
30018
30019 Meaning: A hardcore event has not occurred within a
30020 reasonable time during system initialization or
30021 shutdown. This may be due to hardware problems or
30022 to a programming error. The system attempts to
30023 continue initialization or shutdown.
30024
30025 Action: If this message persists contact system
30026 programmers.
30027
30028
30029 pxss.alm
30030 pxss: notify time out: event=ZZZZZZZZZZZZ.
30031 During init/shutdown.
30032
30033
30034 Stream: BOS Typewriter.
30035
30036 Time: System Intialization.
30037
30038 Meaning: A hardcore event has not occurred within a
30039 reasonable time during system initialization or
30040 shutdown. This may be due to hardware problems or
30041 to a programming error. The system attempts to
30042 continue initialization or shutdown.
30043
30044 Action: If this message persists contact system
30045 programmers.
30046
30047
30048 pxss.alm
30049 pxss: notify time out: event=ZZZZZZZZZZZZ.
30050 During init/shutdown.
30051
30052
30053 Stream: BOS Typewriter.
30054
30055 Time: System Intialization.
30056
30057
30058 pxss 519 08/21/20 MR12.7^L
30059
30060
30061 Meaning: A hardcore event has not occurred within a
30062 reasonable time during system initialization or
30063 shutdown. This may be due to hardware problems or
30064 to a programming error. The system attempts to
30065 continue initialization or shutdown.
30066
30067 Action: If this message persists contact system
30068 programmers.
30069
30070
30071 pxss.alm
30072 pxss: notify time out: event=ZZZZZZZZZZZZ
30073 pid=XXXXXXXXXXXX
30074
30075
30076 Stream: BOS Typewriter.
30077
30078 Time: While system is running.
30079
30080 Meaning: A hardcore event has not occurred within a
30081 reasonable time. This may be due to hardware
30082 problems or to a programming error. The system
30083 attempts to continue operation.
30084
30085 Action: If this message persists contact system
30086 programmers.
30087
30088
30089 pxss.alm
30090 pxss: notify time out: event=ZZZZZZZZZZZZ
30091 pid=XXXXXXXXXXXX
30092
30093
30094 Stream: BOS Typewriter.
30095
30096 Time: While system is running.
30097
30098 Meaning: A hardcore event has not occurred within a
30099 reasonable time. This may be due to hardware
30100 problems or to a programming error. The system
30101 attempts to continue operation.
30102
30103 Action: If this message persists contact system
30104 programmers.
30105
30106
30107 pxss.alm
30108 pxss: notify time out: event=ZZZZZZZZZZZZ
30109 pid=XXXXXXXXXXXX
30110
30111
30112 Stream: BOS Typewriter.
30113
30114
30115
30116 pxss 520 08/21/20 MR12.7^L
30117
30118
30119 Time: While system is running.
30120
30121 Meaning: A hardcore event has not occurred within a
30122 reasonable time. This may be due to hardware
30123 problems or to a programming error. The system
30124 attempts to continue operation.
30125
30126 Action: If this message persists contact system
30127 programmers.
30128
30129
30130 pxss.alm
30131 pxss: sprq already on prds
30132
30133
30134
30135 Stream: BOS Typewriter Crashes system
30136
30137 Time: While system is running.
30138
30139 Meaning: This indicates a logic error in the supervisor or
30140 CPU or memory hardware problems.
30141
30142 Action: Follow normal recovery procedures.
30143
30144
30145
30146 pxss.alm
30147 pxss: sprq already on prds
30148
30149
30150
30151 Stream: BOS Typewriter Crashes system
30152
30153 Time: While system is running.
30154
30155 Meaning: This indicates a logic error in the supervisor or
30156 CPU or memory hardware problems.
30157
30158 Action: Follow normal recovery procedures.
30159
30160
30161
30162 pxss.alm
30163 pxss: sprq already on prds
30164
30165
30166
30167 Stream: BOS Typewriter Crashes system
30168
30169 Time: While system is running.
30170
30171
30172
30173
30174 pxss 521 08/21/20 MR12.7^L
30175
30176
30177 Meaning: This indicates a logic error in the supervisor or
30178 CPU or memory hardware problems.
30179
30180 Action: Follow normal recovery procedures.
30181
30182
30183
30184 pxss.alm
30185 pxss: stack_0 page 0 wired
30186
30187
30188
30189 Stream: BOS Typewriter Crashes system
30190
30191 Time: While system is running.
30192
30193 Meaning: This indicates a logic error in the supervisor or
30194 CPU or memory hardware problems. " process
30195 loading was about to wire the first page of the
30196 ring 0 stack when " it discovered that it had been
30197 beaten to the punch.
30198
30199 Action: Follow normal recovery procedures.
30200
30201
30202
30203 pxss.alm
30204 pxss: stack_0 page 0 wired
30205
30206
30207
30208 Stream: BOS Typewriter Crashes system
30209
30210 Time: While system is running.
30211
30212 Meaning: This indicates a logic error in the supervisor or
30213 CPU or memory hardware problems. " process
30214 loading was about to wire the first page of the
30215 ring 0 stack when " it discovered that it had been
30216 beaten to the punch.
30217
30218 Action: Follow normal recovery procedures.
30219
30220
30221
30222 pxss.alm
30223 pxss: stack_0 page 0 wired
30224
30225
30226
30227 Stream: BOS Typewriter Crashes system
30228
30229 Time: While system is running.
30230
30231
30232 pxss 522 08/21/20 MR12.7^L
30233
30234
30235 Meaning: This indicates a logic error in the supervisor or
30236 CPU or memory hardware problems. " process
30237 loading was about to wire the first page of the
30238 ring 0 stack when " it discovered that it had been
30239 beaten to the punch.
30240
30241 Action: Follow normal recovery procedures.
30242
30243
30244
30245 pxss.alm
30246 pxss: Stop returned from getwork
30247
30248
30249
30250 Stream: BOS Typewriter Crashes system
30251
30252 Time: While system is running.
30253
30254 Meaning: This indicates a logic error in the supervisor or
30255 CPU or memory hardware problems.
30256
30257 Action: Follow normal recovery procedures.
30258
30259
30260
30261 pxss.alm
30262 pxss: Stop returned from getwork
30263
30264
30265
30266 Stream: BOS Typewriter Crashes system
30267
30268 Time: While system is running.
30269
30270 Meaning: This indicates a logic error in the supervisor or
30271 CPU or memory hardware problems.
30272
30273 Action: Follow normal recovery procedures.
30274
30275
30276
30277 pxss.alm
30278 pxss: Stop returned from getwork
30279
30280
30281
30282 Stream: BOS Typewriter Crashes system
30283
30284 Time: While system is running.
30285
30286 Meaning: This indicates a logic error in the supervisor or
30287 CPU or memory hardware problems.
30288
30289
30290 pxss 523 08/21/20 MR12.7^L
30291
30292
30293 Action: Follow normal recovery procedures.
30294
30295
30296
30297 pxss.alm
30298 pxss: subroutine_save stack overflow
30299
30300
30301
30302 Stream: BOS Typewriter Crashes system
30303
30304 Time: While system is running.
30305
30306 Meaning: This indicates a logic error in the supervisor or
30307 CPU or memory hardware problems.
30308
30309 Action: Follow normal recovery procedures.
30310
30311
30312
30313 pxss.alm
30314 pxss: subroutine_save stack overflow
30315
30316
30317
30318 Stream: BOS Typewriter Crashes system
30319
30320 Time: While system is running.
30321
30322 Meaning: This indicates a logic error in the supervisor or
30323 CPU or memory hardware problems.
30324
30325 Action: Follow normal recovery procedures.
30326
30327
30328
30329 pxss.alm
30330 pxss: subroutine_save stack overflow
30331
30332
30333
30334 Stream: BOS Typewriter Crashes system
30335
30336 Time: While system is running.
30337
30338 Meaning: This indicates a logic error in the supervisor or
30339 CPU or memory hardware problems.
30340
30341 Action: Follow normal recovery procedures.
30342
30343
30344
30345 pxss.alm
30346
30347
30348 pxss 524 08/21/20 MR12.7^L
30349
30350
30351 pxss: System default procs required reset to
30352 ABCDEFGH
30353
30354
30355 Stream: BOS Typewriter sounds beeper
30356
30357 Time: During CPU deconfiguration.
30358
30359 Meaning: Due to the deletion of a CPU there were no online
30360 CPUs remaining in the default set of CPUs. These
30361 CPUs are the only CPUs on which processes can run
30362 which have not requested to be run on specific
30363 CPUs. The default set of CPUs has been changed to
30364 all online CPUs.
30365
30366 Action: Contact the system programming staff._sa
30367
30368
30369 pxss.alm
30370 pxss: System default procs required reset to
30371 ABCDEFGH
30372
30373
30374 Stream: BOS Typewriter sounds beeper
30375
30376 Time: During CPU deconfiguration.
30377
30378 Meaning: Due to the deletion of a CPU there were no online
30379 CPUs remaining in the default set of CPUs. These
30380 CPUs are the only CPUs on which processes can run
30381 which have not requested to be run on specific
30382 CPUs. The default set of CPUs has been changed to
30383 all online CPUs.
30384
30385 Action: Contact the system programming staff._sa
30386
30387
30388 pxss.alm
30389 pxss: System default procs required reset to
30390 ABCDEFGH
30391
30392
30393 Stream: BOS Typewriter sounds beeper
30394
30395 Time: During CPU deconfiguration.
30396
30397 Meaning: Due to the deletion of a CPU there were no online
30398 CPUs remaining in the default set of CPUs. These
30399 CPUs are the only CPUs on which processes can run
30400 which have not requested to be run on specific
30401 CPUs. The default set of CPUs has been changed to
30402 all online CPUs.
30403
30404
30405
30406 pxss 525 08/21/20 MR12.7^L
30407
30408
30409 Action: Contact the system programming staff._sa
30410
30411
30412 pxss.alm
30413 pxss: thread_him_in already threaded
30414
30415
30416
30417 Stream: BOS Typewriter Crashes system
30418
30419 Time: While system is running.
30420
30421 Meaning: This indicates a logic error in the supervisor or
30422 CPU or memory hardware problems.
30423
30424 Action: Follow normal recovery procedures.
30425
30426
30427
30428 pxss.alm
30429 pxss: thread_him_in already threaded
30430
30431
30432
30433 Stream: BOS Typewriter Crashes system
30434
30435 Time: While system is running.
30436
30437 Meaning: This indicates a logic error in the supervisor or
30438 CPU or memory hardware problems.
30439
30440 Action: Follow normal recovery procedures.
30441
30442
30443
30444 pxss.alm
30445 pxss: thread_him_in already threaded
30446
30447
30448
30449 Stream: BOS Typewriter Crashes system
30450
30451 Time: While system is running.
30452
30453 Meaning: This indicates a logic error in the supervisor or
30454 CPU or memory hardware problems.
30455
30456 Action: Follow normal recovery procedures.
30457
30458
30459
30460 pxss.alm
30461 pxss: thread_him_in x0 zero
30462
30463
30464 pxss 526 08/21/20 MR12.7^L
30465
30466
30467 Stream: BOS Typewriter Crashes system
30468
30469 Time: While system is running.
30470
30471 Meaning: This indicates a logic error in the supervisor or
30472 CPU or memory hardware problems.
30473
30474 Action: Follow normal recovery procedures.
30475
30476
30477
30478 pxss.alm
30479 pxss: thread_him_in x0 zero
30480
30481
30482
30483 Stream: BOS Typewriter Crashes system
30484
30485 Time: While system is running.
30486
30487 Meaning: This indicates a logic error in the supervisor or
30488 CPU or memory hardware problems.
30489
30490 Action: Follow normal recovery procedures.
30491
30492
30493
30494 pxss.alm
30495 pxss: thread_him_in x0 zero
30496
30497
30498
30499 Stream: BOS Typewriter Crashes system
30500
30501 Time: While system is running.
30502
30503 Meaning: This indicates a logic error in the supervisor or
30504 CPU or memory hardware problems.
30505
30506 Action: Follow normal recovery procedures.
30507
30508
30509
30510 pxss.alm
30511 pxss: thread_him_in x1 zero
30512
30513
30514
30515 Stream: BOS Typewriter Crashes system
30516
30517 Time: While system is running.
30518
30519
30520
30521
30522 pxss 527 08/21/20 MR12.7^L
30523
30524
30525 Meaning: This indicates a logic error in the supervisor or
30526 CPU or memory hardware problems.
30527
30528 Action: Follow normal recovery procedures.
30529
30530
30531
30532 pxss.alm
30533 pxss: thread_him_in x1 zero
30534
30535
30536
30537 Stream: BOS Typewriter Crashes system
30538
30539 Time: While system is running.
30540
30541 Meaning: This indicates a logic error in the supervisor or
30542 CPU or memory hardware problems.
30543
30544 Action: Follow normal recovery procedures.
30545
30546
30547
30548 pxss.alm
30549 pxss: thread_him_in x1 zero
30550
30551
30552
30553 Stream: BOS Typewriter Crashes system
30554
30555 Time: While system is running.
30556
30557 Meaning: This indicates a logic error in the supervisor or
30558 CPU or memory hardware problems.
30559
30560 Action: Follow normal recovery procedures.
30561
30562
30563
30564 pxss.alm
30565 pxss: thread_him_in x4 zero
30566
30567
30568
30569 Stream: BOS Typewriter Crashes system
30570
30571 Time: While system is running.
30572
30573 Meaning: This indicates a logic error in the supervisor or
30574 CPU or memory hardware problems.
30575
30576 Action: Follow normal recovery procedures.
30577
30578
30579
30580 pxss 528 08/21/20 MR12.7^L
30581
30582
30583
30584
30585 pxss.alm
30586 pxss: thread_him_in x4 zero
30587
30588
30589
30590 Stream: BOS Typewriter Crashes system
30591
30592 Time: While system is running.
30593
30594 Meaning: This indicates a logic error in the supervisor or
30595 CPU or memory hardware problems.
30596
30597 Action: Follow normal recovery procedures.
30598
30599
30600
30601 pxss.alm
30602 pxss: thread_him_in x4 zero
30603
30604
30605
30606 Stream: BOS Typewriter Crashes system
30607
30608 Time: While system is running.
30609
30610 Meaning: This indicates a logic error in the supervisor or
30611 CPU or memory hardware problems.
30612
30613 Action: Follow normal recovery procedures.
30614
30615
30616
30617 pxss.alm
30618 pxss: thread_him_in x4->apte.fp ^= x1
30619
30620
30621
30622 Stream: BOS Typewriter Crashes system
30623
30624 Time: While system is running.
30625
30626 Meaning: This indicates a logic error in the supervisor or
30627 CPU or memory hardware problems.
30628
30629 Action: Follow normal recovery procedures.
30630
30631
30632
30633 pxss.alm
30634 pxss: thread_him_in x4->apte.fp ^= x1
30635
30636
30637
30638 pxss 529 08/21/20 MR12.7^L
30639
30640
30641 Stream: BOS Typewriter Crashes system
30642
30643 Time: While system is running.
30644
30645 Meaning: This indicates a logic error in the supervisor or
30646 CPU or memory hardware problems.
30647
30648 Action: Follow normal recovery procedures.
30649
30650
30651
30652 pxss.alm
30653 pxss: thread_him_in x4->apte.fp ^= x1
30654
30655
30656
30657 Stream: BOS Typewriter Crashes system
30658
30659 Time: While system is running.
30660
30661 Meaning: This indicates a logic error in the supervisor or
30662 CPU or memory hardware problems.
30663
30664 Action: Follow normal recovery procedures.
30665
30666
30667
30668 pxss.alm
30669 pxss: unlock apt read lock bad count
30670
30671
30672
30673 Stream: BOS Typewriter Crashes system
30674
30675 Time: While system is running.
30676
30677 Meaning: This indicates a logic error in the supervisor or
30678 CPU or memory hardware problems.
30679
30680 Action: Follow normal recovery procedures.
30681
30682
30683
30684 pxss.alm
30685 pxss: unlock apt read lock bad count
30686
30687
30688
30689 Stream: BOS Typewriter Crashes system
30690
30691 Time: While system is running.
30692
30693
30694
30695
30696 pxss 530 08/21/20 MR12.7^L
30697
30698
30699 Meaning: This indicates a logic error in the supervisor or
30700 CPU or memory hardware problems.
30701
30702 Action: Follow normal recovery procedures.
30703
30704
30705
30706 pxss.alm
30707 pxss: unlock apt read lock bad count
30708
30709
30710
30711 Stream: BOS Typewriter Crashes system
30712
30713 Time: While system is running.
30714
30715 Meaning: This indicates a logic error in the supervisor or
30716 CPU or memory hardware problems.
30717
30718 Action: Follow normal recovery procedures.
30719
30720
30721
30722 pxss.alm
30723 pxss: UNLOCK_bp not locked
30724
30725
30726
30727 Stream: BOS Typewriter Crashes system
30728
30729 Time: While system is running.
30730
30731 Meaning: This indicates a logic error in the supervisor or
30732 CPU or memory hardware problems.
30733
30734 Action: Follow normal recovery procedures.
30735
30736
30737
30738 pxss.alm
30739 pxss: UNLOCK_bp not locked
30740
30741
30742
30743 Stream: BOS Typewriter Crashes system
30744
30745 Time: While system is running.
30746
30747 Meaning: This indicates a logic error in the supervisor or
30748 CPU or memory hardware problems.
30749
30750 Action: Follow normal recovery procedures.
30751
30752
30753
30754 pxss 531 08/21/20 MR12.7^L
30755
30756
30757
30758
30759 pxss.alm
30760 pxss: UNLOCK_bp not locked
30761
30762
30763
30764 Stream: BOS Typewriter Crashes system
30765
30766 Time: While system is running.
30767
30768 Meaning: This indicates a logic error in the supervisor or
30769 CPU or memory hardware problems.
30770
30771 Action: Follow normal recovery procedures.
30772
30773
30774
30775 pxss.alm
30776 pxss: unlock_stack_queue not my lock
30777
30778
30779
30780 Stream: BOS Typewriter Crashes system
30781
30782 Time: While system is running.
30783
30784 Meaning: This indicates a logic error in the supervisor or
30785 CPU or memory hardware problems.
30786
30787 Action: Follow normal recovery procedures.
30788
30789
30790
30791 pxss.alm
30792 pxss: unlock_stack_queue not my lock
30793
30794
30795
30796 Stream: BOS Typewriter Crashes system
30797
30798 Time: While system is running.
30799
30800 Meaning: This indicates a logic error in the supervisor or
30801 CPU or memory hardware problems.
30802
30803 Action: Follow normal recovery procedures.
30804
30805
30806
30807 pxss.alm
30808 pxss: unlock_stack_queue not my lock
30809
30810
30811
30812 pxss 532 08/21/20 MR12.7^L
30813
30814
30815 Stream: BOS Typewriter Crashes system
30816
30817 Time: While system is running.
30818
30819 Meaning: This indicates a logic error in the supervisor or
30820 CPU or memory hardware problems.
30821
30822 Action: Follow normal recovery procedures.
30823
30824
30825
30826 pxss.alm
30827 pxss: unlock_stack_queue stacq failed
30828
30829
30830
30831 Stream: BOS Typewriter Crashes system
30832
30833 Time: While system is running.
30834
30835 Meaning: This indicates a logic error in the supervisor or
30836 CPU or memory hardware problems. " This indicates
30837 a hardware error.
30838
30839 Action: Follow normal recovery procedures.
30840
30841
30842
30843 pxss.alm
30844 pxss: unlock_stack_queue stacq failed
30845
30846
30847
30848 Stream: BOS Typewriter Crashes system
30849
30850 Time: While system is running.
30851
30852 Meaning: This indicates a logic error in the supervisor or
30853 CPU or memory hardware problems. " This indicates
30854 a hardware error.
30855
30856 Action: Follow normal recovery procedures.
30857
30858
30859
30860 pxss.alm
30861 pxss: unlock_stack_queue stacq failed
30862
30863
30864
30865 Stream: BOS Typewriter Crashes system
30866
30867 Time: While system is running.
30868
30869
30870 pxss 533 08/21/20 MR12.7^L
30871
30872
30873 Meaning: This indicates a logic error in the supervisor or
30874 CPU or memory hardware problems. " This indicates
30875 a hardware error.
30876
30877 Action: Follow normal recovery procedures.
30878
30879
30880
30881 pxss.alm
30882 pxss: UNLOCK_X2 not locked
30883
30884
30885
30886 Stream: BOS Typewriter Crashes system
30887
30888 Time: While system is running.
30889
30890 Meaning: This indicates a logic error in the supervisor or
30891 CPU or memory hardware problems.
30892
30893 Action: Follow normal recovery procedures.
30894
30895
30896
30897 pxss.alm
30898 pxss: UNLOCK_X2 not locked
30899
30900
30901
30902 Stream: BOS Typewriter Crashes system
30903
30904 Time: While system is running.
30905
30906 Meaning: This indicates a logic error in the supervisor or
30907 CPU or memory hardware problems.
30908
30909 Action: Follow normal recovery procedures.
30910
30911
30912
30913 pxss.alm
30914 pxss: UNLOCK_X2 not locked
30915
30916
30917
30918 Stream: BOS Typewriter Crashes system
30919
30920 Time: While system is running.
30921
30922 Meaning: This indicates a logic error in the supervisor or
30923 CPU or memory hardware problems.
30924
30925 Action: Follow normal recovery procedures.
30926
30927
30928 pxss 534 08/21/20 MR12.7^L
30929
30930
30931
30932
30933 pxss.alm
30934 pxss: UNLOCK_x3 not locked
30935
30936
30937
30938 Stream: BOS Typewriter Crashes system
30939
30940 Time: While system is running.
30941
30942 Meaning: This indicates a logic error in the supervisor or
30943 CPU or memory hardware problems.
30944
30945 Action: Follow normal recovery procedures.
30946
30947
30948
30949 pxss.alm
30950 pxss: UNLOCK_x3 not locked
30951
30952
30953
30954 Stream: BOS Typewriter Crashes system
30955
30956 Time: While system is running.
30957
30958 Meaning: This indicates a logic error in the supervisor or
30959 CPU or memory hardware problems.
30960
30961 Action: Follow normal recovery procedures.
30962
30963
30964
30965 pxss.alm
30966 pxss: UNLOCK_x3 not locked
30967
30968
30969
30970 Stream: BOS Typewriter Crashes system
30971
30972 Time: While system is running.
30973
30974 Meaning: This indicates a logic error in the supervisor or
30975 CPU or memory hardware problems.
30976
30977 Action: Follow normal recovery procedures.
30978
30979
30980
30981 pxss.alm
30982 pxss: untenable blocked APTE
30983
30984
30985
30986 pxss 535 08/21/20 MR12.7^L
30987
30988
30989 Stream: BOS Typewriter Crashes system
30990
30991 Time: While system is running.
30992
30993 Meaning: This indicates a logic error in the supervisor or
30994 CPU or memory hardware problems.
30995
30996 Action: Follow normal recovery procedures.
30997
30998
30999
31000 pxss.alm
31001 pxss: untenable blocked APTE
31002
31003
31004
31005 Stream: BOS Typewriter Crashes system
31006
31007 Time: While system is running.
31008
31009 Meaning: This indicates a logic error in the supervisor or
31010 CPU or memory hardware problems.
31011
31012 Action: Follow normal recovery procedures.
31013
31014
31015
31016 pxss.alm
31017 pxss: untenable blocked APTE
31018
31019
31020
31021 Stream: BOS Typewriter Crashes system
31022
31023 Time: While system is running.
31024
31025 Meaning: This indicates a logic error in the supervisor or
31026 CPU or memory hardware problems.
31027
31028 Action: Follow normal recovery procedures.
31029
31030
31031
31032 pxss.alm
31033 pxss: untenable empty APTE
31034
31035
31036
31037 Stream: BOS Typewriter Crashes system
31038
31039 Time: While system is running.
31040
31041
31042
31043
31044 pxss 536 08/21/20 MR12.7^L
31045
31046
31047 Meaning: This indicates a logic error in the supervisor or
31048 CPU or memory hardware problems.
31049
31050 Action: Follow normal recovery procedures.
31051
31052
31053
31054 pxss.alm
31055 pxss: untenable empty APTE
31056
31057
31058
31059 Stream: BOS Typewriter Crashes system
31060
31061 Time: While system is running.
31062
31063 Meaning: This indicates a logic error in the supervisor or
31064 CPU or memory hardware problems.
31065
31066 Action: Follow normal recovery procedures.
31067
31068
31069
31070 pxss.alm
31071 pxss: untenable empty APTE
31072
31073
31074
31075 Stream: BOS Typewriter Crashes system
31076
31077 Time: While system is running.
31078
31079 Meaning: This indicates a logic error in the supervisor or
31080 CPU or memory hardware problems.
31081
31082 Action: Follow normal recovery procedures.
31083
31084
31085
31086 pxss.alm
31087 pxss: untenable stopped APTE
31088
31089
31090
31091 Stream: BOS Typewriter Crashes system
31092
31093 Time: While system is running.
31094
31095 Meaning: This indicates a logic error in the supervisor or
31096 CPU or memory hardware problems.
31097
31098 Action: Follow normal recovery procedures.
31099
31100
31101
31102 pxss 537 08/21/20 MR12.7^L
31103
31104
31105
31106
31107 pxss.alm
31108 pxss: untenable stopped APTE
31109
31110
31111
31112 Stream: BOS Typewriter Crashes system
31113
31114 Time: While system is running.
31115
31116 Meaning: This indicates a logic error in the supervisor or
31117 CPU or memory hardware problems.
31118
31119 Action: Follow normal recovery procedures.
31120
31121
31122
31123 pxss.alm
31124 pxss: untenable stopped APTE
31125
31126
31127
31128 Stream: BOS Typewriter Crashes system
31129
31130 Time: While system is running.
31131
31132 Meaning: This indicates a logic error in the supervisor or
31133 CPU or memory hardware problems.
31134
31135 Action: Follow normal recovery procedures.
31136
31137
31138
31139 pxss.alm
31140 pxss: unthread null back ptr
31141
31142
31143
31144 Stream: BOS Typewriter Crashes system
31145
31146 Time: While system is running.
31147
31148 Meaning: This indicates a logic error in the supervisor or
31149 CPU or memory hardware problems.
31150
31151 Action: Follow normal recovery procedures.
31152
31153
31154
31155 pxss.alm
31156 pxss: unthread null back ptr
31157
31158
31159
31160 pxss 538 08/21/20 MR12.7^L
31161
31162
31163 Stream: BOS Typewriter Crashes system
31164
31165 Time: While system is running.
31166
31167 Meaning: This indicates a logic error in the supervisor or
31168 CPU or memory hardware problems.
31169
31170 Action: Follow normal recovery procedures.
31171
31172
31173
31174 pxss.alm
31175 pxss: unthread null back ptr
31176
31177
31178
31179 Stream: BOS Typewriter Crashes system
31180
31181 Time: While system is running.
31182
31183 Meaning: This indicates a logic error in the supervisor or
31184 CPU or memory hardware problems.
31185
31186 Action: Follow normal recovery procedures.
31187
31188
31189
31190 pxss.alm
31191 pxss: unthread null cur.fp
31192
31193
31194
31195 Stream: BOS Typewriter Crashes system
31196
31197 Time: While system is running.
31198
31199 Meaning: This indicates a logic error in the supervisor or
31200 CPU or memory hardware problems.
31201
31202 Action: Follow normal recovery procedures.
31203
31204
31205
31206 pxss.alm
31207 pxss: unthread null cur.fp
31208
31209
31210
31211 Stream: BOS Typewriter Crashes system
31212
31213 Time: While system is running.
31214
31215
31216
31217
31218 pxss 539 08/21/20 MR12.7^L
31219
31220
31221 Meaning: This indicates a logic error in the supervisor or
31222 CPU or memory hardware problems.
31223
31224 Action: Follow normal recovery procedures.
31225
31226
31227
31228 pxss.alm
31229 pxss: unthread null cur.fp
31230
31231
31232
31233 Stream: BOS Typewriter Crashes system
31234
31235 Time: While system is running.
31236
31237 Meaning: This indicates a logic error in the supervisor or
31238 CPU or memory hardware problems.
31239
31240 Action: Follow normal recovery procedures.
31241
31242
31243
31244 pxss.alm
31245 pxss: unthread prev.fp ^= cur
31246
31247
31248
31249 Stream: BOS Typewriter Crashes system
31250
31251 Time: While system is running.
31252
31253 Meaning: This indicates a logic error in the supervisor or
31254 CPU or memory hardware problems.
31255
31256 Action: Follow normal recovery procedures.
31257
31258
31259
31260 pxss.alm
31261 pxss: unthread prev.fp ^= cur
31262
31263
31264
31265 Stream: BOS Typewriter Crashes system
31266
31267 Time: While system is running.
31268
31269 Meaning: This indicates a logic error in the supervisor or
31270 CPU or memory hardware problems.
31271
31272 Action: Follow normal recovery procedures.
31273
31274
31275
31276 pxss 540 08/21/20 MR12.7^L
31277
31278
31279
31280
31281 pxss.alm
31282 pxss: unthread prev.fp ^= cur
31283
31284
31285
31286 Stream: BOS Typewriter Crashes system
31287
31288 Time: While system is running.
31289
31290 Meaning: This indicates a logic error in the supervisor or
31291 CPU or memory hardware problems.
31292
31293 Action: Follow normal recovery procedures.
31294
31295
31296
31297 pxss.alm
31298 pxss: write_to_read bad lock count
31299
31300
31301
31302 Stream: BOS Typewriter Crashes system
31303
31304 Time: While system is running.
31305
31306 Meaning: This indicates a logic error in the supervisor or
31307 CPU or memory hardware problems.
31308
31309 Action: Follow normal recovery procedures.
31310
31311
31312
31313 pxss.alm
31314 pxss: write_to_read bad lock count
31315
31316
31317
31318 Stream: BOS Typewriter Crashes system
31319
31320 Time: While system is running.
31321
31322 Meaning: This indicates a logic error in the supervisor or
31323 CPU or memory hardware problems.
31324
31325 Action: Follow normal recovery procedures.
31326
31327
31328
31329 pxss.alm
31330 pxss: write_to_read bad lock count
31331
31332
31333
31334 pxss 541 08/21/20 MR12.7^L
31335
31336
31337 Stream: BOS Typewriter Crashes system
31338
31339 Time: While system is running.
31340
31341 Meaning: This indicates a logic error in the supervisor or
31342 CPU or memory hardware problems.
31343
31344 Action: Follow normal recovery procedures.
31345
31346
31347
31348 pxss.alm
31349 pxss: write_to_read ldac failed
31350
31351
31352
31353 Stream: BOS Typewriter Crashes system
31354
31355 Time: While system is running.
31356
31357 Meaning: This indicates a logic error in the supervisor or
31358 CPU or memory hardware problems. " This indicates
31359 a hardware error.
31360
31361 Action: Follow normal recovery procedures.
31362
31363
31364
31365 pxss.alm
31366 pxss: write_to_read ldac failed
31367
31368
31369
31370 Stream: BOS Typewriter Crashes system
31371
31372 Time: While system is running.
31373
31374 Meaning: This indicates a logic error in the supervisor or
31375 CPU or memory hardware problems. " This indicates
31376 a hardware error.
31377
31378 Action: Follow normal recovery procedures.
31379
31380
31381
31382 pxss.alm
31383 pxss: write_to_read ldac failed
31384
31385
31386
31387 Stream: BOS Typewriter Crashes system
31388
31389 Time: While system is running.
31390
31391
31392 pxss 542 08/21/20 MR12.7^L
31393
31394
31395 Meaning: This indicates a logic error in the supervisor or
31396 CPU or memory hardware problems. " This indicates
31397 a hardware error.
31398
31399 Action: Follow normal recovery procedures.
31400
31401
31402
31403 rcp_control_.pl1
31404 RCP: Acquired DEVICE from storage system.
31405
31406
31407 Stream: BOS Typewriter.
31408
31409 Time: In response to an operator command.
31410
31411 Meaning: The operator has used the set_drive_usage command
31412 to make DRIVE an IO drive.
31413
31414 Action: No operator action is required.
31415
31416
31417 rcp_control_.pl1
31418 RCP: Added device DEVICE
31419
31420
31421 Stream: BOS Typewriter.
31422
31423 Time: In response to an operator command.
31424
31425 Meaning: The operator has added a user I/O disk drive with
31426 adddev.
31427
31428 Action: No operator action is required.
31429
31430
31431 rcp_reserve_.pl1
31432 RCP: An error locking rcpd for reservation for
31433 RESERVED_FOR by RESERVER if they're not the same
31434 id=RES_ID.
31435
31436
31437
31438 Stream: Logged in SYSERR log.
31439
31440 Time: While system is running.
31441
31442 Meaning: An error was found in the locking data for the
31443 resource.
31444
31445 Action: No operator action is required.
31446
31447
31448
31449
31450 RCP 543 08/21/20 MR12.7^L
31451
31452
31453
31454
31455 rcp_control_.pl1
31456 RCP: Assigned DEVICE to PERSON.PROJ.T
31457
31458
31459 Stream: Logged in SYSERR log.
31460
31461 Time: While system is running.
31462
31463 Meaning: DEVICE has been assigned to a user process.
31464
31465 Action: No operator action is required.
31466
31467
31468 rcp_ioi_attach_.pl1
31469 RCP: Attached DEVICE for PERSON.PROJ.T
31470
31471
31472 Stream: BOS Typewriter.
31473
31474 Time: While system is running.
31475
31476 Meaning: The device DEVICE has been attached by the user
31477 process.
31478
31479 Action: No operator action is required.
31480
31481
31482 rcp_disk_.pl1
31483 RCP: Authenticate DRIVE for PERSON.PROJ.T.
31484 RCP: It has LABEL_TYPE label NAME.
31485 RCP: All N subvolume labels are unreadable.
31486 RCP: VOL_NAME on subvol a VOL_NAME on subvol b
31487 VOL_NAME on subvol c.
31488 RCP: User requested volume DIFFERENT_NAME.
31489
31490
31491
31492 Stream: BOS Typewriter sounds beeper
31493
31494 Time: While system is running.
31495
31496 Meaning: The operator must verify that the correct pack is
31497 mounted on DRIVE. If the DIFFERENT_NAME message
31498 indicates that the label on the pack NAME is
31499 different from the user's request then special
31500 instructions from the system administrator must be
31501 followed.
31502
31503 Action: If the pack is correct then use the "x auth"
31504 function to input the DRIVE and the authentication
31505 code which matches LABEL_TYPE: "ss" for "Storage
31506
31507
31508 RCP 544 08/21/20 MR12.7^L
31509
31510
31511 System" or "copy of Storage System"; "io" for
31512 "IO"; "urd" for "UnReaDable"; or "urg" for
31513 "UnReGistered". If the wrong pack is mounted then
31514 use the authentication code "no".
31515
31516
31517
31518 rcp_tape_.pl1
31519 RCP: Authenticate DRIVE. It has LABEL_TYPE label
31520 LABEL and is UNREGISTERED.
31521
31522
31523 Stream: BOS Typewriter sounds beeper
31524
31525 Time: While system is running.
31526
31527 Meaning: The tape volume requested is not a registered tape
31528 volume. In addittion the system may not have
31529 been able to determine that the volume loaded is
31530 in fact the one requested. The label read from
31531 the tape on DEVICE was of type LABEL_TYPE and was
31532 LABEL. If LABEL is "Manual Halt" this indicates
31533 that the tape drive was found in standby while
31534 trying to read/verify the label. Any
31535 non-printable characters in the label are
31536 represented by ".".
31537
31538 Action: If the volume is correct and is to be registered
31539 to the user requesting this attachment use the "x
31540 auth" function to input the DRIVE number and the
31541 authentication code on the tape volume or "***"
31542 if there is no authentication code. If
31543 authentication was requested due to the drive
31544 being in standby the tape should be rewound
31545 manually and rereadied manually and the above
31546 procedure for authentication followed.
31547
31548
31549
31550 rcp_tape_.pl1
31551 RCP: Authenticate DRIVE. It has LABEL_TYPE label
31552 LABEL.
31553
31554
31555 Stream: BOS Typewriter sounds beeper
31556
31557 Time: While system is running.
31558
31559 Meaning: The system cannot determine that the volume on
31560 DRIVE is the one requested. The operator must
31561 authenticate the volume. The label read from the
31562 tape on DEVICE was of type LABEL_TYPE and was
31563 LABEL. If LABEL is "Manual Halt" this indicates
31564
31565
31566 RCP 545 08/21/20 MR12.7^L
31567
31568
31569 that the tape drive was found in standby while
31570 trying to read/verify the label. If LABEL_TYPE is
31571 ANSI and LABEL is "<label> with non-blank
31572 accessibility code" this indicates that the label
31573 is an ANSI label with a non-blank character in the
31574 accessibility field the operator must consult the
31575 site standards for authenticating such tapes
31576 before doing the authentication. Any
31577 non-printable characters in the label are
31578 represented by ".".
31579
31580 Action: If the volume is correct then use the "x auth"
31581 function to input the DRIVE number and the
31582 authentication code on the tape volume or "***"
31583 if there is no authentication code. If
31584 authentication was requested due to the drive
31585 being in standby the tape should be rewound
31586 manually and rereadied manually and the above
31587 procedure for authentication followed.
31588
31589
31590
31591 rcp_tape_.pl1
31592 RCP: Authentication code for DRIVE does not
31593 match.
31594
31595
31596 Stream: BOS Typewriter.
31597
31598 Time: While system is running.
31599
31600 Meaning: The authentication code typed for the volume on
31601 DRIVE does no match the user specified volume
31602 name.
31603
31604 Action: No operator action is required.
31605
31606
31607 rcp_disk_.pl1
31608 RCP: Authentication denied for DRIVE
31609
31610
31611 Stream: BOS Typewriter sounds beeper
31612
31613 Time: While system is running.
31614
31615 Meaning: The operator has denied authentication for DRIVE.
31616
31617 Action: No operator action is required.
31618
31619
31620 rcp_ring1_init_.pl1
31621 RCP: Auto Registration is enabled without Exact
31622
31623
31624 RCP 546 08/21/20 MR12.7^L
31625
31626
31627 Authentication required. This could lead to
31628 errors in automatic registration of volumes.
31629
31630
31631 Stream: BOS Typewriter sounds beeper
31632
31633 Time: While system is running.
31634
31635 Meaning: This is a warning. If the system is operated with
31636 auto registration enabled and exact authentication
31637 of tape volumes is not required there is a better
31638 chance of errors occurring in the registration of
31639 tape volumes. Again it is very important to make
31640 sure the volume mounted is the proper one for the
31641 request if auto registration is enabled.
31642
31643 Action: No operator action is required.
31644
31645
31646 rcp_cancel_id_.pl1
31647 RCP: Cancelled device devX_MM for GRP_ID
31648 id=RES_ID
31649
31650
31651 Stream: Logged in SYSERR log.
31652
31653 Time: While system is running.
31654
31655 Meaning: A device reservation has been cancelled by the
31656 operator the absentee manager or the Initializer.
31657
31658 Action: No operator action is required.
31659
31660
31661 rcp_reserve_.pl1
31662 RCP: Cancelled device devX_MM for GRP_ID
31663 id=RES_ID
31664
31665
31666 Stream: Logged in SYSERR log.
31667
31668 Time: While system is running.
31669
31670 Meaning: The reservation for the named device has been
31671 cancelled.
31672
31673 Action: No operator action is required.
31674
31675
31676 rcp_cancel_id_.pl1
31677 RCP: Cancelled volume volume_name for GRP_ID
31678 id=RES_ID
31679
31680
31681
31682 RCP 547 08/21/20 MR12.7^L
31683
31684
31685 Stream: Logged in SYSERR log.
31686
31687 Time: While system is running.
31688
31689 Meaning: A volume reservation has been cancelled by the
31690 operator the absentee manager or the Initializer.
31691
31692 Action: No operator action is required.
31693
31694
31695 rcp_reserve_.pl1
31696 RCP: Cancelled volume volume_name for GRP_ID
31697 id=RES_ID
31698
31699
31700 Stream: Logged in SYSERR log.
31701
31702 Time: While system is running.
31703
31704 Meaning: The reservation for the named volume has been
31705 cancelled.
31706
31707 Action: No operator action is required.
31708
31709
31710 rcprm_journalize_.pl1
31711 RCP: Cannot initiate journal PATH. ERROR_CODE
31712
31713
31714 Stream: BOS Typewriter sounds beeper
31715
31716 Time: While system is running.
31717
31718 Meaning: The RCP journal at PATH has been damaged or is
31719 missing.
31720
31721 Action: Contact the system programming staff.
31722
31723
31724 wdx.pl1
31725 RCP: Check mount of logical volume LVNAME for
31726 PROCESSNAME PVNAME1DRIVE1 ...
31727
31728
31729
31730 Stream: BOS Typewriter sounds beeper
31731
31732 Time: While system is running.
31733
31734 Meaning: A user PROCESSNAME previously requested the
31735 attachment of logical volume LVNAME. The mount
31736 has not been accomplished in a 4 minutes. All
31737
31738
31739
31740 RCP 548 08/21/20 MR12.7^L
31741
31742
31743 required physical volumes are specified PVNAMEi
31744 DRIVEi.
31745
31746 Action: Mount the required physical volumes using the
31747 add_vol command to indicate when each has been
31748 made ready. The user process will continue when
31749 the last volume has been mounted. If the volume
31750 cannot be mounted use the del_lv command to
31751 indicate this fact and the user process will
31752 receive an error indication.
31753
31754
31755
31756 rcp_mount_timer_.pl1
31757 RCP: Check Mount of REELID for writing on DRIVE
31758 for PERSON.PROJ.T
31759
31760
31761 Stream: BOS Typewriter sounds beeper
31762
31763 Time: While system is running.
31764
31765 Meaning: The request to mount tape reel REELID has been
31766 unsatisfied for over 4 minutes.
31767
31768 Action: Mount the reel or use "x deny" to inform the user
31769 that the reel cannot be mounted.
31770
31771
31772 rcp_control_.pl1
31773 RCP: Consigned DEVICE to storage system.
31774
31775
31776 Stream: BOS Typewriter.
31777
31778 Time: In response to an operator command.
31779
31780 Meaning: The operator has used the set_drive_usage command
31781 to make DRIVE a storage system drive.
31782
31783 Action: No operator action is required.
31784
31785
31786 rcp_ring1_init_.pl1
31787 RCP: Created DIR with default access.
31788
31789
31790 Stream: BOS Typewriter sounds beeper
31791
31792 Time: While system is running.
31793
31794 Meaning: The directory usually >system_control_1>rcp was
31795 created because it was not found at startup. It
31796
31797
31798 RCP 549 08/21/20 MR12.7^L
31799
31800
31801 may have been destroyed in a crash. This message
31802 is normal during a cold boot of the Multics
31803 hierarchy.
31804
31805 Action: If users other than system processes should have
31806 access to the directory the system administrator
31807 must set the ACL appropriately.
31808
31809
31810
31811 rcp_ring1_init_.pl1
31812 RCP: Created DIR>DEVICE.acs with default access.
31813
31814
31815 Stream: BOS Typewriter sounds beeper
31816
31817 Time: While system is running.
31818
31819 Meaning: The system has created an access control segment
31820 for DEVICE because one was not found at startup.
31821 It may have been destroyed in a crash. This
31822 message is normal during the first use of a device
31823 on the system and at cold boot.
31824
31825 Action: If users other than system processes should have
31826 access to DEVICE the system administrator must
31827 set the ACL of DEVICE.acs appropriately.
31828
31829
31830
31831 rcprm_journalize_.pl1
31832 RCP: Creating DIRNAME>rcprm.journal
31833
31834
31835 Stream: BOS Typewriter.
31836
31837 Time: While system is running.
31838
31839 Meaning: Printed by RCP Resource Management when first
31840 enabled.
31841
31842 Action: No operator action is required.
31843
31844
31845 rcp_control_.pl1
31846 RCP: Deleted device DEVICE
31847
31848
31849 Stream: BOS Typewriter.
31850
31851 Time: In response to an operator command.
31852
31853
31854
31855
31856 RCP 550 08/21/20 MR12.7^L
31857
31858
31859 Meaning: The operator has deleted user I/O disk DRIVE with
31860 deldev.
31861
31862 Action: No operator action is required.
31863
31864
31865 rcp_detach_.pl1
31866 RCP: Detached DEVICE from PERSON.PROJ.T
31867
31868
31869 Stream: BOS Typewriter.
31870
31871 Time: While system is running.
31872
31873 Meaning: The user of DEVICE has detached it.
31874
31875 Action: If DEVICE is a disk drive demount the volume on
31876 it and store it in the library.
31877
31878
31879 rcp_control_.pl1
31880 RCP: DEVICE is not operational and has not been
31881 added.
31882
31883
31884 Stream: BOS Typewriter.
31885
31886 Time: In response to an operator command.
31887
31888 Meaning: An attempt was made to add a non-operational
31889 device with adddev.
31890
31891 Action: Ready the device and add it again.
31892
31893
31894 rcp_ring1_init_.pl1
31895 RCP: Error creating ACS DEVICE.acs:
31896 ERROR_MESSAGE
31897
31898
31899 Stream: BOS Typewriter sounds beeper
31900
31901 Time: While system is running.
31902
31903 Meaning: The system was unable to create an access control
31904 segment for DEVICE. No user will be able to
31905 attach it.
31906
31907 Action: Contact the system programming staff.
31908
31909
31910 rcp_ring1_init_.pl1
31911 RCP: Error creating DIR: ERROR_MESSAGE
31912
31913
31914 RCP 551 08/21/20 MR12.7^L
31915
31916
31917 Stream: BOS Typewriter sounds beeper
31918
31919 Time: While system is running.
31920
31921 Meaning: The system was unable to create the ACS directory.
31922 It should be >system_control_1>acs. The system
31923 may be unable to use I/O devices.
31924
31925 Action: Contact the system programming staff.
31926
31927
31928 rcprm_journalize_.pl1
31929 RCP: Error during registry reconstruction for
31930 USERID. RCP: Could not OPERATION RESOURCE_TYPE
31931 RESOURCE_NAME may occur multiple times RCP: End
31932 of reconstruction operation.
31933
31934
31935
31936 Stream: BOS Typewriter sounds beeper
31937
31938 Time: This message should only occur during a special
31939 session. The second message in the series may
31940 occur multiple times.
31941
31942 Meaning: The specified RCP Resource Management activity
31943 failed to be re-performed during an attempt to
31944 reconstruct the registries by the System
31945 Administrator. This indicates a logic error in
31946 the supervisor or CPU or memory hardware
31947 problems.
31948
31949 Action: Contact the system programming staff._sa
31950
31951
31952 rcp_ring1_init_.pl1
31953 RCP: Error expanding DIR: ERROR_MESSAGE
31954
31955
31956 Stream: BOS Typewriter sounds beeper
31957
31958 Time: While system is running.
31959
31960 Meaning: The pathname of the acs directory is incorrect.
31961 It should be >system_control_1>acs. This
31962 indicates a logic error in the supervisor or CPU
31963 or memory hardware problems. The system may be
31964 unable to use I/O devices.
31965
31966 Action: Contact the system programming staff.
31967
31968
31969 rcp_ring1_init_.pl1
31970
31971
31972 RCP 552 08/21/20 MR12.7^L
31973
31974
31975 RCP: Error setting max length of DEVICE.acs:
31976 ERROR_MESSAGE
31977
31978
31979 Stream: BOS Typewriter sounds beeper
31980
31981 Time: While system is running.
31982
31983 Meaning: This indicates a logic error in the supervisor or
31984 CPU or memory hardware problems.
31985
31986 Action: Contact the system programming staff.
31987
31988
31989 rcp_detach_.pl1
31990 RCP: Errors DEVICE = NN
31991
31992
31993 Stream: BOS Typewriter.
31994
31995 Time: While system is running.
31996
31997 Meaning: When DEVICE was detached its error counter was
31998 nonzero. This may be due to a problem with DEVICE
31999 or with the user program.
32000
32001 Action: No operator action is required.
32002
32003
32004 rcp_detach_.pl1
32005 RCP: Errors DEVICE volume VOL = NN
32006
32007
32008 Stream: BOS Typewriter.
32009
32010 Time: While system is running.
32011
32012 Meaning: When DEVICE was detached its error counter was
32013 nonzero. The errors may be due to a problem with
32014 DEVICE with the volume VOLUME or with the user
32015 program.
32016
32017 Action: No operator action is required.
32018
32019
32020 rcp_detach_.pl1
32021 RCP: Force Detached DEVICE from PERSON.PROJ.T
32022
32023
32024 Stream: BOS Typewriter.
32025
32026 Time: While system is running.
32027
32028
32029
32030 RCP 553 08/21/20 MR12.7^L
32031
32032
32033 Meaning: The user PERSON.PROJ.T has terminated abnormally.
32034 This may be due to an automatic logout or a
32035 process termination.
32036
32037 Action: If DEVICE is a disk drive demount the volume on
32038 it and store it in the library.
32039
32040
32041 rcp_control_.pl1
32042 RCP: Force Unassigned DEVICE from PERSON.PROJ.T
32043
32044
32045 Stream: BOS Typewriter.
32046
32047 Time: While system is running.
32048
32049 Meaning: The user process PERSON.PROJ.T has terminated and
32050 its resources have been freed. Or the operator
32051 may have forced the unassignment of DRIVE.
32052
32053 Action: No operator action is required.
32054
32055
32056 rcprm_journalize_.pl1
32057 RCP: Journal could not be forcibly written.
32058 ERROR CODE
32059
32060
32061 Stream: BOS Typewriter.
32062
32063 Time: While system is running.
32064
32065 Meaning: A force-write to disk of the RCP journal
32066 failed.This indicates a logic error in the
32067 supervisor or CPU or memory hardware problems.
32068
32069 Action: Contact the system programming staff.
32070
32071
32072 rcprm_journalize_.pl1
32073 RCP: Journal lost transaction for USERID.
32074 ERROR_CODE
32075
32076
32077 Stream: BOS Typewriter sounds beeper
32078
32079 Time: While system is running.
32080
32081 Meaning: Some RCP Resource Management activity while
32082 successfully completed was not properly
32083 journalized for recovery purposes. Subsequently
32084 if the registries become damaged before they are
32085
32086
32087
32088 RCP 554 08/21/20 MR12.7^L
32089
32090
32091 safely copied by the System Administrator this
32092 activity will be lost.
32093
32094 Action: Contact the system programming staff._sa
32095
32096
32097 rcp_detach_.pl1
32098 RCP: Manually unload volume VOLUME from device
32099 DEVICE
32100
32101
32102 Stream: BOS Typewriter sounds beeper
32103
32104 Time: While system is running.
32105
32106 Meaning: RCP could not unload the specified volume from the
32107 device on which it was loaded.
32108
32109 Action: Manually unload the volume from the device and
32110 return the volume to the library for storage.
32111
32112
32113 rcp_unload_.pl1
32114 RCP: Manually unload volume VOLUME from device
32115 DEVICE
32116
32117
32118 Stream: BOS Typewriter sounds beeper
32119
32120 Time: While system is running.
32121
32122 Meaning: RCP could not unload the specified volume from the
32123 device on which it was loaded.
32124
32125 Action: Manually unload the volume from the device and
32126 return the volume to the library for storage.
32127
32128
32129 wdx.pl1
32130 RCP: Mount logical volume LVNAME for PROCESSNAME
32131
32132
32133 Stream: BOS Typewriter sounds beeper
32134
32135 Time: While system is running.
32136
32137 Meaning: A user PROCESSNAME has requested the attachment
32138 of logical volume LVNAME. It is not now mounted.
32139 The initializer will issue mount messages for all
32140 physical volumes needed.
32141
32142 Action: Mount the required physical volumes using the
32143 add_vol command to indicate when each has been
32144
32145
32146 RCP 555 08/21/20 MR12.7^L
32147
32148
32149 made ready. The user process will continue when
32150 the last volume has been mounted. If the volume
32151 cannot be mounted use the del_lv command to
32152 indicate this fact and the user process will
32153 receive an error indication.
32154
32155
32156
32157 rcp_disk_.pl1
32158 RCP: Mount Pack PACK on DRIVE for PERSON.PROJ.T
32159
32160
32161 Stream: BOS Typewriter sounds beeper
32162
32163 Time: While system is running.
32164
32165 Meaning: The user PERSON.PROJ.T has requested the mounting
32166 of the user I/O pack named PACK on disk drive
32167 DRIVE.
32168
32169 Action: Mount the pack and make it ready.
32170
32171
32172 rcp_disk_.pl1
32173 RCP: Mount Pack PACK without protect on DRIVE
32174 for PERSON.PROJ.T
32175
32176
32177 Stream: BOS Typewriter sounds beeper
32178
32179 Time: While system is running.
32180
32181 Meaning: The user PERSON.PROJ.T has requested the mounting
32182 of the user I/O pack named PACK on disk drive
32183 DRIVE.
32184
32185 Action: Mount the pack and make it ready. Set the PROTECT
32186 status as specified in the message.
32187
32188
32189
32190 rcp_message_.pl1
32191 RCP: Mount Reel REELID without ring on DRIVE
32192 for PERSON.PROJ.T switching volumes.
32193
32194
32195 Stream: BOS Typewriter sounds beeper
32196
32197 Time: While system is running.
32198
32199 Meaning: A user process has requested the mounting of tape
32200 reel REELID on drive DRIVE.
32201
32202
32203
32204 RCP 556 08/21/20 MR12.7^L
32205
32206
32207 Action: Locate the requested reel. Check to make sure
32208 that the user PERSON.PROJ is allowed to use the
32209 reel. Insert or remove a write ring as specified.
32210 Mount the reel on the specified drive.
32211
32212 If the reel cannot be mounted either because it
32213 cannot be located access is incorrect or the
32214 drive is down use the "x deny" function to reject
32215 the mount request.
32216
32217
32218
32219 rcp_tape_.pl1
32220 RCP: Mount Reel REELID without ring on DRIVE
32221 for PERSON.PROJ.T.
32222
32223
32224 Stream: BOS Typewriter sounds beeper
32225
32226 Time: While system is running.
32227
32228 Meaning: A user process has requested the mounting of tape
32229 reel REELID on drive DRIVE.
32230
32231 Action: Locate the requested reel. Check to make sure
32232 that the user PERSON.PROJ is allowed to use the
32233 reel. Insert or remove a write ring as specified.
32234 Mount the reel on the specified drive.
32235
32236 If the reel cannot be mounted either because it
32237 cannot be located access is incorrect or the
32238 drive is down use the "x deny" function to reject
32239 the mount request.
32240
32241
32242
32243 rcp_disk_.pl1
32244 RCP: Mounted LABEL_TYPE volume NAME on DRIVE for
32245 user I/O.
32246
32247
32248 Stream: BOS Typewriter.
32249
32250 Time: While system is running.
32251
32252 Meaning: A user has mounted LABEL_TYPE volume NAME as a
32253 user I/O disk on DRIVE. The operator has
32254 authenticated the mount.
32255
32256 Action: No operator action is required.
32257
32258
32259
32260
32261
32262 RCP 557 08/21/20 MR12.7^L
32263
32264
32265
32266
32267 rcp_comment_.pl1
32268 RCP: Note DEVICE - COMMENT
32269
32270
32271 Stream: BOS Typewriter.
32272
32273 Time: While system is running.
32274
32275 Meaning: The user requesting the mounting of a tape or disk
32276 pack on device specified a comment string.
32277
32278 Action: Read the comment. It may describe special
32279 operator action such as where to find or send the
32280 volume.
32281
32282
32283
32284 rcprm_find_resource_.pl1
32285 RCP: Operator certified manual clearing of
32286 VOLUME. RCP: USERID certified manual clearing of
32287 VOLUME.
32288
32289
32290
32291 Stream: BOS Typewriter.
32292
32293 Time: In response to an operator or administrator
32294 command.
32295
32296 Meaning: This message is printed for auditing purposes when
32297 site-madated destruction of data is accomplished.
32298
32299 Action: No operator action is required.
32300
32301
32302 rcp_preload_.pl1
32303 RCP: Preload volume VOLUME on device DEVICE
32304
32305
32306 Stream: BOS Typewriter.
32307
32308 Time: While system is running.
32309
32310 Meaning: The operator request to preload has been accepted
32311 by RCP.
32312
32313 Action: Preload the volume in question on the specified
32314 device.
32315
32316
32317 rcprm_find_resource_.pl1
32318
32319
32320 RCP 558 08/21/20 MR12.7^L
32321
32322
32323 RCP: Registries may be in an inconsistent state.
32324 ERROR_CODE
32325
32326
32327 Stream: BOS Typewriter sounds beeper
32328
32329 Time: While system is running.
32330
32331 Meaning: An RCP Resource Management transaction was not
32332 properly committed to the registries.This
32333 indicates a logic error in the supervisor or CPU
32334 or memory hardware problems.
32335
32336 Action: Contact the system programming staff.
32337
32338
32339 rcp_disk_.pl1
32340 RCP: Rejected mount of LABEL_TYPE volume NAME for
32341 PERSON.PROJ.T
32342
32343
32344 Stream: BOS Typewriter.
32345
32346 Time: While system is running.
32347
32348 Meaning: A user has attempted to mount a storage-system
32349 format or unreadable LABEL_TYPE disk pack for
32350 user I/O without specifying the -sys parameter.
32351 Because this might interfere with later storage
32352 system use of the pack or compromise system
32353 security this action is not permitted. The
32354 user's request is rejected. This error could
32355 arise if an operator inadvertently mounted the
32356 wrong pack.
32357
32358 Action: No operator action is required.
32359
32360
32361 rcp_tape_.pl1
32362 RCP: Remount Reel REELID without ring on DRIVE.
32363
32364
32365 Stream: BOS Typewriter sounds beeper
32366
32367 Time: While system is running.
32368
32369 Meaning: The system found a write ring when one was not
32370 required or did not find one when one was needed.
32371 Or the authentication code did not match. The
32372 tape is unloaded.
32373
32374 Action: Correct the write ring status or mount the correct
32375 tape and reready the tape.
32376
32377
32378 RCP 559 08/21/20 MR12.7^L
32379
32380
32381
32382
32383 rcp_disk_.pl1
32384 RCP: Reready DRIVE
32385
32386
32387 Stream: BOS Typewriter sounds beeper
32388
32389 Time: While system is running.
32390
32391 Meaning: DRIVE is not ready.
32392
32393 Action: Make the drive ready.
32394
32395
32396 rcp_disk_.pl1
32397 RCP: Reready DRIVE without protect
32398
32399
32400 Stream: BOS Typewriter sounds beeper
32401
32402 Time: While system is running.
32403
32404 Meaning: DRIVE is not ready.
32405
32406 Action: Make the drive ready.
32407
32408
32409 rcp_tape_.pl1
32410 RCP: Reready DRIVE.
32411
32412
32413 Stream: BOS Typewriter sounds beeper
32414
32415 Time: While system is running.
32416
32417 Meaning: DRIVE has dropped out of ready status.
32418
32419 Action: Reready it.
32420
32421
32422 rcp_tape_.pl1
32423 RCP: Reready Reel REELID on DRIVE for
32424 PERSON.PROJ.T.
32425
32426
32427 Stream: BOS Typewriter sounds beeper
32428
32429 Time: While system is running.
32430
32431 Meaning: A preloaded volume was not ready.
32432
32433 Action: Make the volume ready.
32434
32435
32436 RCP 560 08/21/20 MR12.7^L
32437
32438
32439
32440
32441 rcp_reserve_.pl1
32442 RCP: Reserved device devX_MM for RESERVER
32443 id=RES_ID
32444
32445
32446 Stream: Logged in SYSERR log.
32447
32448 Time: While system is running.
32449
32450 Meaning: Device devX_MM has been reserved for RESERVER.
32451
32452 Action: No operator action is required.
32453
32454
32455 rcp_reserve_.pl1
32456 RCP: Reserved volume volume_name for RESERVER
32457 id=RES_ID
32458
32459
32460 Stream: Logged in SYSERR log.
32461
32462 Time: While system is running.
32463
32464 Meaning: Volume volume_name has been reserved for RESERVER.
32465
32466 Action: No operator action is required.
32467
32468
32469 rcp_auto_register_.pl1
32470 RCP: RESOURCE_TYPE RESOURCE_NAME registered and
32471 acquired to USER.
32472
32473
32474 Stream: BOS Typewriter.
32475
32476 Time: While system is running.
32477
32478 Meaning: The resource RESOURCE_NAME has been automatically
32479 registered and acquired to USER. It is a resource
32480 of the type RESCOURCE_TYPE.
32481
32482 Action: No operator action is required.
32483
32484
32485 rcprm_find_resource_.pl1
32486 RCP: Schedule VOLUME for manual clearing.
32487
32488
32489 Stream: BOS Typewriter sounds beeper
32490
32491 Time: While system is running.
32492
32493
32494 RCP 561 08/21/20 MR12.7^L
32495
32496
32497 Meaning: The data contained on VOLUME is to be destroyed by
32498 the operator via degaussing or other site-mandated
32499 method.
32500
32501 Action: The operator must erase the specified resource
32502 and must acknowledge when this has been done by
32503 issuing the clear_resource command or the
32504 appropriate site-defined "x" Initializer request.
32505
32506
32507
32508 rcp_disk_.pl1
32509 RCP: Turn protect switch ON/OFF on drive DRIVE
32510 and then push Operator Interrupt on MPC
32511
32512
32513 Stream: BOS Typewriter sounds beeper
32514
32515 Time: While system is running.
32516
32517 Meaning: The PROTECT status was wrong for DRIVE.
32518
32519 Meaning: Correct the PROTECT status and push the Operator
32520 Interrupt button on the MPC.
32521
32522
32523 rcp_control_.pl1
32524 RCP: Unassigned DEVICE from PERSON.PROJ.T
32525
32526
32527 Stream: Logged in SYSERR log.
32528
32529 Time: While system is running.
32530
32531 Meaning: PERSON.PROJ.T has released DRIVE normally.
32532
32533 Action: No operator action is required.
32534
32535
32536 rcp_detach_.pl1
32537 RCP: Unloading volume VOLUME from device DEVICE
32538
32539
32540 Stream: BOS Typewriter.
32541
32542 Time: While system is running.
32543
32544 Meaning: The specified VOLUME is being demounted by RCP.
32545
32546 Action: Return the specified VOLUME to the library.
32547
32548
32549
32550
32551
32552 RCP 562 08/21/20 MR12.7^L
32553
32554
32555
32556
32557 rcp_unload_.pl1
32558 RCP: Unloading volume VOLUME from device DEVICE
32559
32560
32561 Stream: BOS Typewriter.
32562
32563 Time: While system is running.
32564
32565 Meaning: The specified VOLUME is being demounted by RCP.
32566
32567 Action: Return the specified VOLUME to the library.
32568
32569
32570 rcp_tape_.pl1
32571 RCP: Using Reel REELID on DRIVE for
32572 PERSON.PROJ.T.
32573
32574
32575 Stream: BOS Typewriter.
32576
32577 Time: While system is running.
32578
32579 Meaning: Using a preloaded volume.
32580
32581 Action: No operator action is required.
32582
32583
32584 rcp_disk_.pl1
32585 RCP: WARNING!! IF YOU AUTHENTICATE THIS REQUEST
32586 <USER> WILL OWN VOLUME <VOLUME>!
32587
32588
32589 Stream: BOS Typewriter sounds beeper
32590
32591 Time: While system is running.
32592
32593 Meaning: This is a warning to the operator. He should be
32594 very careful to check the physical label of the
32595 volume before authenticating this request. As the
32596 message states if the request is autheticated
32597 <VOLUME> will be registered and acquired to
32598 <USER>.
32599
32600 Action: Check the physical label of the disk pack. If it
32601 is the property of <USER> authenticate the
32602 request. If it is not the property of <USER> deny
32603 the request by typing "x auth no".
32604
32605
32606
32607 rcp_tape_.pl1
32608
32609
32610 RCP 563 08/21/20 MR12.7^L
32611
32612
32613 RCP: WARNING!! IF YOU AUTHENTICATE THIS REQUEST
32614 <USER> WILL OWN VOLUME <VOLUME>!
32615
32616
32617 Stream: BOS Typewriter sounds beeper
32618
32619 Time: While system is running.
32620
32621 Meaning: This is a warning to the operator. IHe should be
32622 very careful to check the physical label of the
32623 volume before authenticating this request. As the
32624 message states if the request is autheticated
32625 <VOLUME> will be registered and acquired to
32626 <USER>.
32627
32628 Action: Check the physical label of the tape volume. If
32629 it is the property of <USER> authenticate the
32630 request. If it is not the property of <USER> deny
32631 the request by typing "x auth no".
32632
32633
32634
32635 rcp_disk_.pl1
32636 RCP: Wrong pack NAME mounted on DRIVE. Mount
32637 pack PACK on DRIVE.
32638
32639
32640 Stream: BOS Typewriter sounds beeper
32641
32642 Time: While system is running.
32643
32644 Meaning: The operator has denied authentication for a
32645 removable disk pack NAME on drive DRIVE. The
32646 disk drive is put in standby.
32647
32648 Action: Mount the correct pack PACK with protect as
32649 specified and ready drive.
32650
32651
32652 rcp_disk_.pl1
32653 RCP: Wrong pack NAME mounted on DRIVE. Mount
32654 pack PACK without protect on DRIVE.
32655
32656
32657 Stream: BOS Typewriter sounds beeper
32658
32659 Time: While system is running.
32660
32661 Meaning: The operator has denied authentication for a
32662 removable disk pack NAME on drive DRIVE. The
32663 disk drive is put in standby.
32664
32665
32666
32667
32668 RCP 564 08/21/20 MR12.7^L
32669
32670
32671 Action: Mount the correct pack PACK with protect as
32672 specified and ready drive.
32673
32674
32675 rcp_control_.pl1
32676 rcp_control_: Error surveying DEVICE. MESSAGE
32677
32678
32679 Stream: BOS Typewriter.
32680
32681 Time: In response to an operator command.
32682
32683 Meaning: An error occurred while surveying the device.
32684
32685 Action: Contact the system programming staff.
32686
32687
32688 rcp_init.pl1
32689 rcp_init: DDDD cannot be used for user I/O.
32690
32691
32692 Stream: BOS Typewriter Crashes system
32693
32694 Time: System Intialization.
32695
32696 Meaning: An attempt was made to configure a device for user
32697 I/O which is being used by the system for system
32698 storage.
32699
32700 Action: Follow normal recovery procedures.
32701
32702
32703 bound_system_startup_.s.archiv.1
32704 rcp_init: DDDD cannot be used for user I/O.
32705
32706
32707 Stream: BOS Typewriter Crashes system
32708
32709 Time: System Intialization.
32710
32711 Meaning: An attempt was made to configure a device for user
32712 I/O which is being used by the system for system
32713 storage.
32714
32715 Action: Follow normal recovery procedures.
32716
32717
32718 rcp_init.pl1
32719 rcp_init: DDDD deleted.
32720
32721
32722 Stream: BOS Typewriter.
32723
32724
32725
32726 rcp_init 565 08/21/20 MR12.7^L
32727
32728
32729 Time: System Intialization.
32730
32731 Meaning: Device DDDD could not be found or accessed and it
32732 will be deleted.
32733
32734 Action: Contact the system programming staff.
32735
32736
32737 bound_system_startup_.s.archiv.1
32738 rcp_init: DDDD deleted.
32739
32740
32741 Stream: BOS Typewriter.
32742
32743 Time: System Intialization.
32744
32745 Meaning: Device DDDD could not be found or accessed and it
32746 will be deleted.
32747
32748 Action: Contact the system programming staff.
32749
32750
32751 rcp_init.pl1
32752 rcp_init: Device DEVICE defined more than once
32753
32754
32755 Stream: BOS Typewriter Crashes system
32756
32757 Time: System Intialization.
32758
32759 Meaning: The configuration deck defines the device DEVICE
32760 more than once.
32761
32762 Action: Perform an emergency shutdown and correct the
32763 configuration deck. Follow normal recovery
32764 procedures.
32765
32766
32767
32768 bound_system_startup_.s.archiv.1
32769 rcp_init: Device DEVICE defined more than once
32770
32771
32772 Stream: BOS Typewriter Crashes system
32773
32774 Time: System Intialization.
32775
32776 Meaning: The configuration deck defines the device DEVICE
32777 more than once.
32778
32779 Action: Perform an emergency shutdown and correct the
32780 configuration deck. Follow normal recovery
32781 procedures.
32782
32783
32784 rcp_init 566 08/21/20 MR12.7^L
32785
32786
32787
32788
32789 rcp_init.pl1
32790 rcp_init: Error surveying DDDD. ERRORMESSAGE
32791
32792
32793 Stream: BOS Typewriter.
32794
32795 Time: System Intialization.
32796
32797 Meaning: Attempted to access device DDDD but could not due
32798 to ERRORMESSAGE.
32799
32800 Action: Contact the system programming staff.
32801
32802
32803 bound_system_startup_.s.archiv.1
32804 rcp_init: Error surveying DDDD. ERRORMESSAGE
32805
32806
32807 Stream: BOS Typewriter.
32808
32809 Time: System Intialization.
32810
32811 Meaning: Attempted to access device DDDD but could not due
32812 to ERRORMESSAGE.
32813
32814 Action: Contact the system programming staff.
32815
32816
32817 rcp_init.pl1
32818 rcp_init: ndrives not specified with last model
32819 number for PRPH DDDD. Assuming 0.
32820
32821
32822 Stream: BOS Typewriter.
32823
32824 Time: System Intialization.
32825
32826 Meaning: Detected a MODEL value at the end of PRPH card
32827 PPPP. Each MODEL value should paired with an
32828 NDRIVE value. The last model value will be
32829 assigned zero devices. It is possible that there
32830 is another error elsewhere on this card to have
32831 caused this message.
32832
32833 Action: Contact the system programming staff.
32834
32835
32836 bound_system_startup_.s.archiv.1
32837 rcp_init: ndrives not specified with last model
32838 number for PRPH DDDD. Assuming 0.
32839
32840
32841
32842 rcp_init 567 08/21/20 MR12.7^L
32843
32844
32845 Stream: BOS Typewriter.
32846
32847 Time: System Intialization.
32848
32849 Meaning: Detected a MODEL value at the end of PRPH card
32850 PPPP. Each MODEL value should paired with an
32851 NDRIVE value. The last model value will be
32852 assigned zero devices. It is possible that there
32853 is another error elsewhere on this card to have
32854 caused this message.
32855
32856 Action: Contact the system programming staff.
32857
32858
32859 rcp_init.pl1
32860 rcp_init: Trying to create rcp_com_seg
32861 ERRORMESSAGE
32862
32863
32864 Stream: BOS Typewriter Crashes system
32865
32866 Time: System Intialization.
32867
32868 Meaning: This indicates a logic error in the supervisor or
32869 CPU or memory hardware problems.
32870
32871 Action: Follow normal recovery procedures.
32872
32873
32874 bound_system_startup_.s.archiv.1
32875 rcp_init: Trying to create rcp_com_seg
32876 ERRORMESSAGE
32877
32878
32879 Stream: BOS Typewriter Crashes system
32880
32881 Time: System Intialization.
32882
32883 Meaning: This indicates a logic error in the supervisor or
32884 CPU or memory hardware problems.
32885
32886 Action: Follow normal recovery procedures.
32887
32888
32889 rcp_init.pl1
32890 rcp_init: Trying to create rcp_data ERRORMESSAGE
32891
32892
32893 Stream: BOS Typewriter Crashes system
32894
32895 Time: System Intialization.
32896
32897
32898
32899
32900 rcp_init 568 08/21/20 MR12.7^L
32901
32902
32903 Meaning: This indicates a logic error in the supervisor or
32904 CPU or memory hardware problems.
32905
32906 Action: Follow normal recovery procedures.
32907
32908
32909 bound_system_startup_.s.archiv.1
32910 rcp_init: Trying to create rcp_data ERRORMESSAGE
32911
32912
32913 Stream: BOS Typewriter Crashes system
32914
32915 Time: System Intialization.
32916
32917 Meaning: This indicates a logic error in the supervisor or
32918 CPU or memory hardware problems.
32919
32920 Action: Follow normal recovery procedures.
32921
32922
32923 rcp_init.pl1
32924 rcp_init: Trying to init mca_data. ERRORMESSAGE
32925
32926
32927 Stream: BOS Typewriter Crashes system
32928
32929 Time: System Intialization.
32930
32931 Meaning: This indicates a logic error in the supervisor or
32932 CPU or memory hardware problems.
32933
32934 Action: Follow normal recovery procedures.
32935
32936
32937 bound_system_startup_.s.archiv.1
32938 rcp_init: Trying to init mca_data. ERRORMESSAGE
32939
32940
32941 Stream: BOS Typewriter Crashes system
32942
32943 Time: System Intialization.
32944
32945 Meaning: This indicates a logic error in the supervisor or
32946 CPU or memory hardware problems.
32947
32948 Action: Follow normal recovery procedures.
32949
32950
32951 rcp_init.pl1
32952 rcp_init: Trying to reclassify rcp_com_seg
32953 ERRORMESSAGE
32954
32955
32956
32957
32958 rcp_init 569 08/21/20 MR12.7^L
32959
32960
32961 Stream: BOS Typewriter Crashes system
32962
32963 Time: System Intialization.
32964
32965 Meaning: This indicates a logic error in the supervisor or
32966 CPU or memory hardware problems.
32967
32968 Action: Follow normal recovery procedures.
32969
32970
32971 bound_system_startup_.s.archiv.1
32972 rcp_init: Trying to reclassify rcp_com_seg
32973 ERRORMESSAGE
32974
32975
32976 Stream: BOS Typewriter Crashes system
32977
32978 Time: System Intialization.
32979
32980 Meaning: This indicates a logic error in the supervisor or
32981 CPU or memory hardware problems.
32982
32983 Action: Follow normal recovery procedures.
32984
32985
32986 rcp_init.pl1
32987 rcp_init: Trying to reclassify rcp_data
32988 ERRORMESSAGE
32989
32990
32991 Stream: BOS Typewriter Crashes system
32992
32993 Time: System Intialization.
32994
32995 Meaning: This indicates a logic error in the supervisor or
32996 CPU or memory hardware problems.
32997
32998 Action: Follow normal recovery procedures.
32999
33000
33001 bound_system_startup_.s.archiv.1
33002 rcp_init: Trying to reclassify rcp_data
33003 ERRORMESSAGE
33004
33005
33006 Stream: BOS Typewriter Crashes system
33007
33008 Time: System Intialization.
33009
33010 Meaning: This indicates a logic error in the supervisor or
33011 CPU or memory hardware problems.
33012
33013 Action: Follow normal recovery procedures.
33014
33015
33016 rcp_tape_survey_ 570 08/21/20 MR12.7^L
33017
33018
33019
33020
33021 rcp_tape_survey_.pl1
33022 rcp_tape_survey_: Error surveying controller
33023 CONTROLLER: ERROR_STATUS
33024
33025
33026 Stream: BOS Typewriter sounds beeper
33027
33028 Time: System Intialization.
33029
33030 Meaning: An error was received from IOI while attempting to
33031 survey the tape controller DEVICE. This indicates
33032 a logic error in the supervisor or CPU or memory
33033 hardware problems.
33034
33035 Action: Contact the system programming staff. Follow
33036 normal recovery procedures.
33037
33038
33039
33040 rcp_tape_survey_.pl1
33041 rcp_tape_survey_: Multiple device NUMBER's found
33042 on CONTROLLER.
33043
33044
33045 Stream: BOS Typewriter sounds beeper
33046
33047 Time: System Intialization.
33048
33049 Meaning: The survey information indicates that there are
33050 multiple devices with the same device number.
33051
33052 Action: Contact field engineering personnel.
33053
33054
33055 rcp_tape_survey_.pl1
33056 rcp_tape_survey_: Tape controller CONTROLLER did
33057 not respond within one second.
33058
33059
33060 Stream: BOS Typewriter sounds beeper
33061
33062 Time: System Intialization.
33063
33064 Meaning: The tape controller or IOM failed to respond to
33065 the survey-devices command by sending an interrupt
33066 within one second.
33067
33068 Action: Contact field engineering personnel.
33069
33070
33071 rcprm_registry_mgr_.pl1
33072
33073
33074 rcprm_registry_mgr_$delete_regis^H5t^H7r^H1y 08/21/20 MR12.7^L
33075
33076
33077 rcprm_registry_mgr_$delete_registry: Deleting
33078 possibly bogus registry PATH for USERID.
33079
33080
33081 Stream: BOS Typewriter sounds beeper
33082
33083 Time: While system is running.
33084
33085 Meaning: The segment at PATH does not seem to be an RCP
33086 registry. It may simply be a damaged registry or
33087 a user may be attempting to use delete_registry to
33088 delete a non-registry object.
33089
33090 Action: Contact the system programming staff._sa
33091
33092
33093 system_control_.pl1
33094 Ready
33095
33096
33097 Stream: BOS Typewriter.
33098
33099 Time: In response to an operator command.
33100
33101 Meaning: The Initializer types Ready whenever it is ready
33102 to accept an Initializer command in ring 4.
33103
33104 Action: Type the desired command.
33105
33106
33107 reassign_work_classes_.pl1
33108 reassign_work_classes_: load control group "XXX"
33109 not found in mgt for user PERSON.PROJECT.TAG.
33110 reassign_work_classes_: mgt clobbered contact
33111 system administrator.
33112
33113
33114
33115 Stream: as severity2.
33116
33117 Time: At shift change time or after a "maxu auto"
33118 command.
33119
33120 Meaning: Some logged in user's load control group has
33121 apparently disappeared from the mgt. If the load
33122 control group specified in the message is valid
33123 then the mgt has been destroyed. Otherwise the
33124 user's answer table entry has been destroyed. All
33125 users will remain in their current work classes.
33126
33127 Action: Contact the system programming staff._sa
33128
33129
33130
33131
33132 reassign_work_classes_ 572 08/21/20 MR12.7^L
33133
33134
33135 reassign_work_classes_.pl1
33136 reassign_work_classes_: no work classes defined
33137 on current shift.
33138
33139
33140 Stream: as severity2
33141
33142 Time: At shift change time or after a "maxu auto"
33143 command.
33144
33145 Meaning: The table in the mgt that should define the work
33146 classes for the current shift has not been filled
33147 in. Probably a new shift has been added to the
33148 installation_parms segment but the work classes
33149 for that shift have not been specified in the mgt.
33150 All users will be placed in a single work class.
33151
33152 Action: No operator action is required.
33153
33154
33155 reassign_work_classes_.pl1
33156 reassign_work_classes_: process NNN remained in
33157 work class NN
33158
33159
33160 Stream: as severity1
33161
33162 Time: At shift change time or after a "maxu auto"
33163 command.
33164
33165 Meaning: Some privileged user has interfered with the
33166 Answering Service's attempt to define a new set of
33167 work classes. The Answering Service will
33168 automatically retry the reassignment of work
33169 classes.
33170
33171 Action: No operator action is required.
33172
33173
33174 reassign_work_classes_.pl1
33175 reassign_work_classes_: undefined work class DD
33176 required by load control group XXX
33177 reassign_work_classes_: mgt clobbered contact
33178 system administrator.
33179
33180
33181
33182 Stream: as severity2
33183
33184 Time: At shift change time or after a "maxu auto"
33185 command.
33186
33187
33188
33189
33190 reassign_work_classes_ 573 08/21/20 MR12.7^L
33191
33192
33193 Meaning: There is an inconsistency in the mgt. Probably
33194 the mgt has been destroyed. All users will remain
33195 in their current work class.
33196
33197 Action: Contact the system programming staff._sa
33198
33199
33200 disk_rebuild_caller.pl1
33201 rebuild_disk: Error XX in rebuild of volume
33202 PVNAME.
33203
33204
33205 Stream: Initializer process output.
33206
33207 Time: In response to an operator command.
33208
33209 Meaning: An error has occurred trying to rebuild the disk.
33210 The new copy should not be used.
33211
33212 Action: If the problem can be repaired repair it and try
33213 again. Contact the system programming staff.
33214
33215
33216
33217 salv_caller.pl1
33218 rebuild_disk: Expected argument missing.
33219
33220
33221 Stream: Initializer process output.
33222
33223 Time: In response to an operator command.
33224
33225 Meaning: Incorrect arguments were specified.
33226
33227 Action: Enter a corrected command line.
33228
33229
33230 salv_caller.pl1
33231 rebuild_disk: Specified control argument is not
33232 implemented by this command. BLAH
33233
33234
33235 Stream: Initializer process output.
33236
33237 Time: In response to an operator command.
33238
33239 Meaning: Incorrect arguments were specified.
33240
33241 Action: Enter a corrected command line.
33242
33243
33244 disk_rebuild_caller.pl1
33245
33246
33247
33248 rebuild_disk 574 08/21/20 MR12.7^L
33249
33250
33251 rebuild_disk: volume PVNAME from DSKA_XX onto
33252 DSKA_YY
33253 Current disk parameters:
33254 part NAME FREC NREC
33255 Vtoc size is XX ave. seg length = Y.ZZZ
33256 Current number of VTOCEs = XX
33257
33258
33259
33260 Stream: Initializer process output.
33261
33262 Time: In response to an operator command.
33263
33264 Meaning: This is the response to the operator command
33265 "rebuild_disk" issued in ring 1.
33266
33267 Action: No operator action is required.
33268
33269
33270 disk_rebuild_caller.pl1
33271 rebuild_disk: Volume PVNAME must be mounted
33272 before rebuilding
33273
33274
33275 Stream: Initializer process output.
33276
33277 Time: In response to an operator command.
33278
33279 Meaning: The rebuild_disk command was invoked on an mounted
33280 volume. Only volumes which are mounted may be
33281 rebuilt. No action was taken.
33282
33283 Action: Salvage the volume first and then reissue the
33284 rebuild_disk command.
33285
33286
33287
33288 reclassify.pl1
33289 reclassify: err locking parent. ERROR_CODE
33290
33291
33292 Stream: BOS Typewriter Crashes system
33293
33294 Time: While system is running.
33295
33296 Meaning: This indicates a logic error in the supervisor or
33297 CPU or memory hardware problems. BOS Typewriter
33298 Crashes systemes
33299
33300 Action: Follow normal recovery procedures.
33301
33302
33303 reconfig.pl1
33304
33305
33306 reconfig 575 08/21/20 MR12.7^L
33307
33308
33309 reconfig: Assigned CPU <cputag> to
33310 <Person.Project.instance> for testing
33311
33312
33313 Stream: BOS Typewriter.
33314
33315 Time: While system is running.
33316
33317 Meaning: Successful reconfiguration of the indicated
33318 processor has been performed by the processor
33319 testing ISOLTS subsystem.
33320
33321 Action: No operator action is required.
33322
33323
33324 reconfig.pl1
33325 reconfig: Releasing base <req_mem>k of MEM
33326 <scutag>
33327
33328
33329 Stream: BOS Typewriter.
33330
33331 Time: While system is running.
33332
33333 Meaning: Processor testing has been terminated and the
33334 indicated memory is now available for
33335 reconfiguration.
33336
33337 Action: No operator action is required.
33338
33339
33340 reconfig.pl1
33341 reconfig: trouble unlocking scs$reconfig_lock
33342
33343
33344 Stream: BOS Typewriter.
33345
33346 Time: While system is running.
33347
33348 Meaning: The reconfiguration lock could not be unlocked.
33349 It is left in its current state. Further attempts
33350 at reconfiguration may fail.
33351
33352 Action: No operator action is required.
33353
33354
33355 reconfig.pl1
33356 reconfig: Unassigned CPU <cputag> from
33357 <Person.Project.instance>
33358
33359
33360 Stream: BOS Typewriter.
33361
33362
33363
33364 reconfig 576 08/21/20 MR12.7^L
33365
33366
33367 Time: While system is running.
33368
33369 Meaning: Processor testing has been terminated and the
33370 indicated processor is now available for
33371 reconfiguration.
33372
33373 Action: No operator action is required.
33374
33375
33376 reconfig.pl1
33377 reconfig: Using base <req_mem>k of MEM <scutag>
33378 for testing CPU cputag
33379
33380
33381 Stream: BOS Typewriter.
33382
33383 Time: While system is running.
33384
33385 Meaning: Successful reconfiguration of the indicated memory
33386 has been performed by the processor testing
33387 ISOLTS subsystem.
33388
33389 Action: No operator action is required.
33390
33391
33392 reloader.pl1
33393 reload_volume: An implementation restriction when
33394 using version 1 volume logs. This requires that
33395 the RPV be reloaded separately from other volumes.
33396
33397
33398
33399 Stream: $rld_out
33400
33401 Time: $reload
33402
33403 Meaning: Using version 1 volume logs all physical volumes
33404 must belong to the mounted RPV. An exception is
33405 when reloading the RPV itself it must be reloaded
33406 separately then a re-boot on the new RPV will
33407 allow the other volumes to be reloaded.
33408
33409 Action: Enter a corrected command line.
33410
33411
33412 reloader.pl1
33413 reload_volume: arg err: ERROR_MESS
33414
33415
33416 Stream: $rld_out
33417
33418 Time: $reload
33419
33420
33421
33422 reload_volume 577 08/21/20 MR12.7^L
33423
33424
33425 Meaning: Invalid input was given.
33426
33427 Action: Enter a corrected command line.
33428
33429
33430 reloader.pl1
33431 reload_volume: Begin reload of volume NAME at
33432 TIME
33433
33434
33435 Stream: $rld_on
33436
33437 Time: $reload
33438
33439 Meaning: A volume reload is beginning.
33440
33441 Action: No operator action is required.
33442
33443
33444 reloader.pl1
33445 reload_volume: Could not enable 256KW segments:
33446 ERORR_MESS
33447
33448
33449 Stream: $rld_out
33450
33451 Time: $reload
33452
33453 Meaning: The call to hcs_$set_256K_switch failed.
33454
33455 Action: Contact the system programming staff.
33456
33457
33458 reloader.pl1
33459 reload_volume: End reload of volume NAME at TIME
33460 reload_volume: Reloaded on volume NAME XX records
33461 of XX directories and XX records of XX segments
33462 and XX null vtoces
33463
33464
33465
33466 Stream: $rld_on
33467
33468 Time: $reload
33469
33470 Meaning: A volume reload has completed. The statistics
33471 printed indicate how many records were reloaded.
33472
33473 Action: No operator action is required.
33474
33475
33476 reloader.pl1
33477
33478
33479
33480 reload_volume 578 08/21/20 MR12.7^L
33481
33482
33483 reload_volume: error closing volume label:
33484 ERROR_MESS
33485
33486
33487 Stream: $rld_out
33488
33489 Time: $reload
33490
33491 Meaning: An error occurred while reloading.
33492
33493 Action: Contact the system programming staff.
33494
33495
33496 reloader.pl1
33497 reload_volume: error closing volume map:
33498 ERROR_MESS
33499
33500
33501 Stream: $rld_out
33502
33503 Time: $reload
33504
33505 Meaning: An error occurred while reloading.
33506
33507 Action: Contact the system programming staff.
33508
33509
33510 reloader.pl1
33511 reload_volume: error closing vtoc header:
33512 ERROR_MESS
33513
33514
33515 Stream: $rld_out
33516
33517 Time: $reload
33518
33519 Meaning: An error occurred while reloading.
33520
33521 Action: Contact the system programming staff.
33522
33523
33524 reloader.pl1
33525 reload_volume: error creating control seg:
33526 ERROR_MESS
33527
33528
33529 Stream: $rld_out
33530
33531 Time: $reload
33532
33533 Meaning: An error occurred while reloading.
33534
33535 Action: Contact the system programming staff.
33536
33537
33538 reload_volume 579 08/21/20 MR12.7^L
33539
33540
33541
33542
33543 reloader.pl1
33544 reload_volume: error creating temp segs:
33545 ERROR_MESS
33546
33547
33548 Stream: $rld_out
33549
33550 Time: $reload
33551
33552 Meaning: An error occurred while reloading.
33553
33554 Action: Contact the system programming staff.
33555
33556
33557 reloader.pl1
33558 reload_volume: error initializing input volume
33559 list: ERROR_MESS
33560
33561
33562 Stream: $rld_out
33563
33564 Time: $reload
33565
33566 Meaning: An error occurred while reloading.
33567
33568 Action: Contact the system programming staff.
33569
33570
33571 reloader.pl1
33572 reload_volume: error initializing output medium:
33573 ERROR_MESS
33574
33575
33576 Stream: $rld_out
33577
33578 Time: $reload
33579
33580 Meaning: An error occurred while reloading.
33581
33582 Action: Contact the system programming staff.
33583
33584
33585 reloader.pl1
33586 reload_volume: error opening volume map:
33587 ERROR_MESS
33588
33589
33590 Stream: $rld_out
33591
33592 Time: $reload
33593
33594
33595
33596 reload_volume 580 08/21/20 MR12.7^L
33597
33598
33599 Meaning: An error occurred while reloading.
33600
33601 Action: Contact the system programming staff.
33602
33603
33604 reloader.pl1
33605 reload_volume: error reloading volume NAME:
33606 ERROR_MESS
33607
33608
33609 Stream: $rld_out
33610
33611 Time: $reload
33612
33613 Meaning: An error occurred while reloading.
33614
33615 Action: Contact the system programming staff.
33616
33617
33618 reloader.pl1
33619 reload_volume: label check failed: ERROR_MESS
33620
33621
33622 Stream: $rld_out
33623
33624 Time: $reload
33625
33626 Meaning: An error occurred while reloading.
33627
33628 Action: Contact the system programming staff.
33629
33630
33631 reloader.pl1
33632 reload_volume: Operator name and physical volume
33633 name not specified
33634
33635
33636 Stream: $rld_out
33637
33638 Time: $reload
33639
33640 Meaning: Invalid input was typed.
33641
33642 Action: Enter a corrected command line.
33643
33644
33645 reloader.pl1
33646 reload_volume: Operator name not specified.
33647
33648
33649 Stream: $rld_out
33650
33651 Time: $reload
33652
33653
33654 reload_volume 581 08/21/20 MR12.7^L
33655
33656
33657 Meaning: Missing input.
33658
33659 Action: Enter a corrected command line.
33660
33661
33662 reloader.pl1
33663 reload_volume: Physical volume name not
33664 specified.
33665
33666
33667 Stream: $rld_out
33668
33669 Time: $reload
33670
33671 Meaning: Missing input.
33672
33673 Action: Enter a corrected command line.
33674
33675
33676 reloader.pl1
33677 reload_volume: Please start volume log recovery
33678 procedure.
33679
33680
33681 Stream: $rld_out
33682
33683 Time: $reload
33684
33685 Meaning: Use the recover_volume_log command to recover the
33686 specified physical volumes volume log.
33687
33688 Action: Enter a corrected command line.
33689
33690
33691 reloader.pl1
33692 reload_volume: The RPV pvid for physical volume
33693 NAME does not match the determined RPV pvid.
33694
33695
33696
33697 Stream: $rld_out
33698
33699 Time: $reload
33700
33701 Meaning: The backup_volume_log.rpv_pvid for NAME does not
33702 match the reloader determined RPV pvid. This
33703 could be an invalid attempt to reload a stranger
33704 physical volume.
33705
33706 Action: Contact the system programming staff.
33707
33708
33709 reloader.pl1
33710
33711
33712 reload_volume 582 08/21/20 MR12.7^L
33713
33714
33715 reload_volume: unable to build VTOC map:
33716 ERROR_MESS
33717
33718
33719 Stream: $rld_out
33720
33721 Time: $reload
33722
33723 Meaning: An error occurred while reloading.
33724
33725 Action: Contact the system programming staff.
33726
33727
33728 reloader.pl1
33729 reload_volume: unable to determine pvid for NAME:
33730 ERROR_MESS
33731
33732
33733 Stream: $rld_out
33734
33735 Time: $reload
33736
33737 Meaning: The volume registration information does not
33738 contain the physical volume NAME. This could be
33739 an invalid attempt to reload a stranger physical
33740 volume.
33741
33742 Action: Contact the system programming staff.
33743
33744
33745 reloader.pl1
33746 reload_volume: unable to get info about rpv:
33747 ERROR_MESS
33748
33749
33750 Stream: $rld_out
33751
33752 Time: $reload
33753
33754 Meaning: An error occurred while reloading.
33755
33756 Action: Contact the system programming staff.
33757
33758
33759 reloader.pl1
33760 reload_volume: Unable to locate a valid volume
33761 log for PATH: ERROR_MESS
33762
33763
33764 Stream: $rld_out
33765
33766 Time: $reload
33767
33768
33769
33770 reload_volume 583 08/21/20 MR12.7^L
33771
33772
33773 Meaning: The volue log at PATH was not found. This message
33774 will always cause the reload to be aborted.
33775
33776 Action: Enter a corrected command line.
33777
33778
33779 reloader.pl1
33780 reload_volume: unable to open vtoc header:
33781 ERROR_MESS
33782
33783
33784 Stream: $rld_out
33785
33786 Time: $reload
33787
33788 Meaning: An error occurred while reloading.
33789
33790 Action: Contact the system programming staff.
33791
33792
33793 reload_volume_.pl1
33794 reload_volume_: Abandoning the reload of pv
33795 PVNAME
33796
33797
33798 Stream: $rld_out
33799
33800 Time: $reload
33801
33802 Meaning: Some fatal error has occurred during the reload of
33803 the specified physical volume.
33804
33805 Action: Take the action required by the error just
33806 previous to this one and retry the reload of the
33807 physical volume.
33808
33809
33810
33811 reload_volume_.pl1
33812 reload_volume_: All physical volumes to be
33813 reloaded have been abandoned.
33814
33815
33816 Stream: $rld_out
33817
33818 Time: $reload
33819
33820 Meaning: Some fatal error has occurred during the reload of
33821 ALL the specified physical volumes.
33822
33823 Action: No operator action is required.
33824
33825
33826
33827
33828 reload_volume_ 584 08/21/20 MR12.7^L
33829
33830
33831 reload_volume_.pl1
33832 reload_volume_: Bad disk page PAGE_ADDRESS for pv
33833 PVNAME
33834
33835
33836 Stream: $rld_out
33837
33838 Time: $reload
33839
33840 Meaning: An I/O error occurred during a reload. This
33841 message indicates the bad disk address on the
33842 volume being reloaded.
33843
33844 Action: No operator action is required.
33845
33846
33847 reload_volume_.pl1
33848 reload_volume_: Error depositing old vtoce VTOCX
33849 for pv PVNAME: ERROR_MESS
33850
33851
33852 Stream: $rld_out
33853
33854 Time: $reload
33855
33856 Meaning: The reloader was unable to release pages of an old
33857 object. This indicates a logic error in the
33858 supervisor or CPU or memory hardware problems.
33859 The input medium is abandoned.
33860
33861 Action: No operator action is required.
33862
33863
33864 reload_volume_.pl1
33865 reload_volume_: Error depositing page PAGENO of
33866 vtoce VTOCX for pv PVNAME: ERROR_MESS
33867
33868
33869 Stream: $rld_out
33870
33871 Time: $reload
33872
33873 Meaning: The reloader was unable to release page PAGENO
33874 decimal of the new object. This is only done
33875 when an incomplete object is detected.
33876
33877 Action: No operator action is required.
33878
33879
33880 reload_volume_.pl1
33881 reload_volume_: Error reading input: ERROR_MESS
33882
33883
33884
33885
33886 reload_volume_ 585 08/21/20 MR12.7^L
33887
33888
33889 Stream: $rld_out
33890
33891 Time: $reload
33892
33893 Meaning: An error occurred while reading input. The input
33894 medium is abandoned.
33895
33896 Action: No operator action is required.
33897
33898
33899 reload_volume_.pl1
33900 reload_volume_: Error reading old vtoce VTOCX for
33901 pv PVNAME: ERROR_MESS
33902
33903
33904 Stream: $rld_out
33905
33906 Time: $reload
33907
33908 Meaning: An I/O error occurred during a reload. The input
33909 medium is abandoned.
33910
33911 Action: No operator action is required.
33912
33913
33914 reload_volume_.pl1
33915 reload_volume_: Error writing new vtoce VTOCX for
33916 pv PVNAME: ERROR_MESS
33917
33918
33919 Stream: $rld_out
33920
33921 Time: $reload
33922
33923 Meaning: An I/O error occurred during a reload. The input
33924 medium is abandoned.
33925
33926 Action: No operator action is required.
33927
33928
33929 reload_volume_.pl1
33930 reload_volume_: Unable to set damaged switch for
33931 vtoce VTOCX on pv PVNAME: ERROR_MESS
33932
33933
33934 Stream: $rld_out
33935
33936 Time: $reload
33937
33938 Meaning: An I/O error has occured while attempting to write
33939 out the new vtoce which has the damaged switch
33940 turned on.
33941
33942
33943
33944 reload_volume_ 586 08/21/20 MR12.7^L
33945
33946
33947 Action: No operator action is required.
33948
33949
33950 reload_volume_.pl1
33951 reload_volume_: Unable to withdraw for bad page
33952 on pv PVNAME: ERROR_MESS
33953
33954
33955 Stream: $rld_out
33956
33957 Time: $reload
33958
33959 Meaning: After an I/O error the reloader attempted to
33960 allocate a new page and failed. The volume may
33961 be full.
33962
33963 Action: If the volume is full it may be necessary to
33964 clean it up with sweep_pv -gc before restarting
33965 the reload.
33966
33967
33968
33969 reload_volume_.pl1
33970 reload_volume_: Unable to withdraw for new vtoce
33971 VTOCX for pv PVNAME: ERROR_MESS
33972
33973
33974 Stream: $rld_out
33975
33976 Time: $reload
33977
33978 Meaning: The reloader is unable to allocate a new VTOCE.
33979 The volume may be full. The input medium is
33980 abandoned.
33981
33982 Action: No operator action is required. If the volume is
33983 full it may be necessary to clean it up with
33984 sweep_pv with the -gc option and then to continue
33985 reloading.
33986
33987
33988
33989 operator_com_channel_cmds_.pl1
33990 remove: bad arg "AAAA"
33991
33992
33993 Stream: as severity1.
33994
33995 Time: In response to an operator command.
33996
33997 Meaning: A bad argument was furnished with an remove
33998 command. The argument is skipped.
33999
34000
34001
34002 remove 587 08/21/20 MR12.7^L
34003
34004
34005 Action: Enter a corrected command.
34006
34007
34008 operator_com_channel_cmds_.pl1
34009 remove: error: not done
34010
34011
34012 Stream: as severity1.
34013
34014 Time: In response to an operator command.
34015
34016 Meaning: Bad arguments were given to an remove command. No
34017 action resulted.
34018
34019 Action: Enter a corrected command line.
34020
34021
34022 operator_com_channel_cmds_.pl1
34023 remove: ttyXXX is in use by the message
34024 coordinator and can not be removed.
34025
34026
34027 Stream: as severity1.
34028
34029 Time: In response to an operator command.
34030
34031 Meaning: An operator remove command specified a message
34032 coordinator channel. The channel was not removed.
34033
34034 Action: Enter a corrected command line. Use the drop
34035 command to take a channel away from the message
34036 coordinator.
34037
34038
34039
34040 operator_com_channel_cmds_.pl1
34041 remove: ttyXXX removed
34042
34043
34044 Stream: as severity1.
34045
34046 Time: In response to an operator remove command.
34047
34048 Meaning: This response to the operator command remove
34049 TTYxxx indicates the channel is no longer
34050 available for dialups. If a user was on the
34051 channel he is bumped with no message but
34052 "hangup". Note that if a user calls in on this
34053 channel and the modem answers the user gets a
34054 carriage return but no welcoming message from the
34055 system and he cannot log in.
34056
34057
34058
34059
34060 remove 588 08/21/20 MR12.7^L
34061
34062
34063 Action: Remember to busy out the modem so that no user can
34064 call the channel.
34065
34066
34067
34068 obs_reconfigure.pl1
34069 Removed frame XXX.
34070
34071
34072 Stream: Initializer process output.
34073
34074 Time: In response to an operator command.
34075
34076 Meaning: This is the response to a successful delmain XXX
34077 command.
34078
34079 Action: No operator action is required.
34080
34081
34082 obs_reconfigure.pl1
34083 Removed frames XXX thru YYY.
34084
34085
34086 Stream: Initializer process output.
34087
34088 Time: In response to an operator command.
34089
34090 Meaning: This is the response to a successful delmain XXX N
34091 command.
34092
34093 Action: No operator action is required.
34094
34095
34096 obs_reconfigure.pl1
34097 Removed SCU X and its memory.
34098
34099
34100 Stream: Initializer process output.
34101
34102 Time: In response to an operator command.
34103
34104 Meaning: This is the response to a successful delmem X
34105 command.
34106
34107 Action: No operator action is required.
34108
34109
34110 obs_reconfigure.pl1
34111 Removed SCU's X and Y interlaced and their
34112 memory.
34113
34114
34115 Stream: Initializer process output.
34116
34117
34118 Removed 589 08/21/20 MR12.7^L
34119
34120
34121 Time: In response to an operator command.
34122
34123 Meaning: This is the response to a successful delmem X
34124 command when SCU's X and Y are interlaced.
34125
34126 Action: No operator action is required.
34127
34128
34129 bce_save.pl1
34130 restorecheck_status: Special Interrupt:
34131 STATUS_WORD
34132
34133
34134 Stream: BOS Typewriter.
34135
34136 Time: System Intialization.
34137
34138 Meaning: An unexpected special interrupt has been detected.
34139
34140 Action: No operator action is required.
34141
34142
34143 bce_save.pl1
34144 restorecheck_status: Time-Out on TAPE_DEV
34145
34146
34147 Stream: BOS Typewriter.
34148
34149 Time: System Intialization.
34150
34151 Meaning: An I/O that was issued to the tape device has
34152 timed-out.
34153
34154 Action: Follow normal recovery procedures.
34155
34156
34157 bce_save.pl1
34158 restoreTAPE_SET: "Info" tape on TAPE_DEV
34159 created DATE_TIME
34160
34161
34162 Stream: BOS Typewriter.
34163
34164 Time: System Intialization.
34165
34166 Meaning: Just an informative message.
34167
34168 Action: No operator action is required.
34169
34170
34171 bce_save.pl1
34172 restoreTAPE_SET: Unrecoverable MAJOR_STATUS
34173 SUB_STATUS on TAPE_DEV.
34174
34175
34176 restoreTAPE_SET 590 08/21/20 MR12.7^L
34177
34178
34179 Stream: BOS Typewriter.
34180
34181 Time: System Intialization.
34182
34183 Meaning: An unrecoverable error has occured while
34184 attempting to do I/O to the tape device.
34185
34186 Action: Follow normal recovery procedures.
34187
34188
34189 bce_save.pl1
34190 restoreTAPE_SET: Abnormal tape termination of
34191 tape# TAPE_NUMBER on TAPE_DEV.
34192
34193
34194 Stream: BOS Typewriter.
34195
34196 Time: System Intialization.
34197
34198 Meaning: While reading the save tape an invalid record
34199 header was found. BCE save tapes are normally
34200 terminated with a End-of-Reel EOR record
34201 followed by three End-of-File EOF marks. This
34202 one most likely was not properly terminated.
34203
34204 Action: No operator action is required. Unless it is felt
34205 that the tape is properly terminated in which
34206 case the restore can be restarted and this tape
34207 re-read.
34208
34209
34210
34211 bce_save.pl1
34212 restoreTAPE_SET: Clearing unused VTOC region
34213 records BEGIN_REC - END_REC on PV_NAME.
34214
34215
34216 Stream: BOS Typewriter.
34217
34218 Time: System Intialization.
34219
34220 Meaning: Just an informative message. The unused records
34221 in the VTOC region are zero cleared to avoid
34222 having erroneous VTOCEs left laying around.
34223
34224 Action: No operator action is required.
34225
34226
34227 bce_save.pl1
34228 restoreTAPE_SET: Device TAPE_DEV is being
34229 removed from the tape device list.
34230
34231
34232
34233
34234 restoreTAPE_SET 591 08/21/20 MR12.7^L
34235
34236
34237 Stream: BOS Typewriter.
34238
34239 Time: System Intialization.
34240
34241 Meaning: The TAPE_DEV has returned a status indicating that
34242 it is unable to be used.
34243
34244 Action: No operator action is required.
34245
34246
34247 bce_save_util_.pl1
34248 restoreTAPE_SET: Device type mis-match.
34249 PV_NAME is on a DEV_TYPE but was saved from a
34250 DEV_TYPE.
34251
34252
34253
34254 Stream: BOS Typewriter.
34255
34256 Time: System Intialization.
34257
34258 Meaning: The program is unable to restore the contents of
34259 the PV because the disk device currently being
34260 used is different than the one in use when the PV
34261 was saved. Only partitions can be restored to PVs
34262 mounted on different devices.
34263
34264 Action: Follow normal recovery procedures.
34265
34266
34267 bce_save.pl1
34268 restoreTAPE_SET: End of Information without
34269 detecting TAPE_EOR record.
34270
34271
34272 Stream: BOS Typewriter.
34273
34274 Time: System Intialization.
34275
34276 Meaning: Multiple End-of-File EOF marks have been
34277 detected without previously reading an
34278 End-of-Reel EOR record.
34279
34280 Action: No operator action is required. Unless it is felt
34281 that the tape is properly terminated in which
34282 case the restore can be restarted and this tape
34283 re-read.
34284
34285
34286
34287 bce_save.pl1
34288 restoreTAPE_SET: Error tape on TAPE_DEV is
34289 part of the "OTHER_TAPE_SET" set.
34290
34291
34292 restoreTAPE_SET 592 08/21/20 MR12.7^L
34293
34294
34295 Stream: BOS Typewriter.
34296
34297 Time: System Intialization.
34298
34299 Meaning: The tape just read is not part of this tape set.
34300
34301 Action: Mount a tape on the device that is part of this
34302 tape set.
34303
34304
34305 bce_save.pl1
34306 restoreTAPE_SET: Incorrect tape number.
34307 Expected tape# TAPE_NUMBER.
34308
34309
34310 Stream: BOS Typewriter.
34311
34312 Time: System Intialization.
34313
34314 Meaning: An internal tape number tracking mechanism is used
34315 and the tape that was just read does not match
34316 what the program expects to be on the device.
34317
34318 Action: Mount the correct tape on the device.
34319
34320
34321 bce_save.pl1
34322 restoreTAPE_SET: MAJOR_STATUS SUB_STATUS on
34323 TAPE_DEV.
34324
34325
34326 Stream: BOS Typewriter.
34327
34328 Time: System Intialization.
34329
34330 Meaning: An error has occured while attempting to do I/O to
34331 the tape device.
34332
34333 Action: Follow normal recovery procedures.
34334
34335
34336 bce_save_util_.pl1
34337 restoreTAPE_SET: MULTICS_VOL_ID PV_NAME on
34338 DISK_DEV Last updated: DATE_TIME
34339
34340
34341
34342 Stream: BOS Typewriter.
34343
34344 Time: System Intialization.
34345
34346 Meaning: Just an informative message.
34347
34348
34349
34350 restoreTAPE_SET 593 08/21/20 MR12.7^L
34351
34352
34353 Action: No operator action is required.
34354
34355
34356 bce_save_util_.pl1
34357 restoreTAPE_SET: No partitions were saved for
34358 volume PV_NAME. Removing from PV list.
34359
34360
34361 Stream: BOS Typewriter.
34362
34363 Time: System Intialization.
34364
34365 Meaning: A request has been made to restore one or more
34366 partitions on PV_NAME but the save tape indicates
34367 that no partitions were saved.
34368
34369 Action: Remove the partition reference from the control
34370 file.
34371
34372
34373 bce_save.pl1
34374 restoreTAPE_SET: No Physical Volumes left to
34375 restore.
34376
34377
34378 Stream: BOS Typewriter.
34379
34380 Time: System Intialization.
34381
34382 Meaning: For various reasons all of the physical volumes
34383 have been removed from the list of volumes.
34384
34385 Action: No operator action is required.
34386
34387
34388 bce_save.pl1
34389 restoreTAPE_SET: No room to describe PV PV_NAME
34390 for part PARTITION_NAME.
34391
34392
34393 Stream: BOS Typewriter.
34394
34395 Time: System Intialization.
34396
34397 Meaning: The maximum number of physical volumes that can be
34398 handled by the program has been exceeded.
34399
34400 Action: The number of physical volumes defined in the
34401 control files must be reduced.
34402
34403
34404
34405 bce_save.pl1
34406
34407
34408 restoreTAPE_SET 594 08/21/20 MR12.7^L
34409
34410
34411 restoreTAPE_SET: No usable tape devices left in
34412 list.
34413
34414
34415 Stream: BOS Typewriter.
34416
34417 Time: System Intialization.
34418
34419 Meaning: For various reasons all of the tape devices have
34420 been removed from the list of available devices
34421 for this tape set.
34422
34423 Action: Follow normal recovery procedures.
34424
34425
34426 bce_save.pl1
34427 restoreTAPE_SET: No usable tape drives left.
34428
34429
34430 Stream: BOS Typewriter.
34431
34432 Time: System Intialization.
34433
34434 Meaning: For various reasons all of the tape devices have
34435 been removed from the list of available devices
34436 for this tape set.
34437
34438 Action: Follow normal recovery procedures.
34439
34440
34441 bce_save_util_.pl1
34442 restoreTAPE_SET: Only partitions were saved for
34443 volume PV_NAME.
34444
34445
34446 Stream: BOS Typewriter.
34447
34448 Time: System Intialization.
34449
34450 Meaning: A request to restore the contents of a PV has been
34451 made but when the PV was saved only partitions
34452 were included.
34453
34454 Action: Correct the control files accordingly.
34455
34456
34457 bce_save_util_.pl1
34458 restoreTAPE_SET: Partition PARTITION_NAME is
34459 not defined on PV_NAME.
34460
34461
34462 Stream: BOS Typewriter.
34463
34464
34465
34466 restoreTAPE_SET 595 08/21/20 MR12.7^L
34467
34468
34469 Time: System Intialization.
34470
34471 Meaning: A request to restore specific partition has been
34472 made but the partition does not exist of the PV.
34473
34474 Action: Correct the control files accordingly.
34475
34476
34477 bce_save_util_.pl1
34478 restoreTAPE_SET: Partition PARTITION_NAME on
34479 PV_NAME was not saved.
34480
34481
34482 Stream: BOS Typewriter.
34483
34484 Time: System Intialization.
34485
34486 Meaning: A request was made to restore a partition from a
34487 PV but the partition was not saved as part of
34488 this tape set.
34489
34490 Action: Correct the control files accordingly.
34491
34492
34493 bce_save.pl1
34494 restoreTAPE_SET: Partition PARTITION_NAME on
34495 PV_NAME record REC_NUM on tape# TAPE_NUMBER
34496 TAPE_DEV
34497
34498
34499 Stream: BOS Typewriter.
34500
34501 Time: System Intialization.
34502
34503 Meaning: Just an informative message.
34504
34505 Action: No operator action is required.
34506
34507
34508 bce_save.pl1
34509 restoreTAPE_SET: Partition PARTITION_NAME was
34510 not defined when PV_NAME was saved.
34511
34512
34513 Stream: BOS Typewriter.
34514
34515 Time: System Intialization.
34516
34517 Meaning: A restore of a partition has been requested in the
34518 control file but the partition was not requested
34519 to be saved when the tape was made.
34520
34521
34522
34523
34524 restoreTAPE_SET 596 08/21/20 MR12.7^L
34525
34526
34527 Action: Remove the partition reference from the control
34528 file.
34529
34530
34531 bce_save.pl1
34532 restoreTAPE_SET: Partition PARTITION_NAME
34533 record REC_NUM on tape# TAPE_NUMBER TAPE_DEV
34534
34535
34536 Stream: BOS Typewriter.
34537
34538 Time: System Intialization.
34539
34540 Meaning: Just an informative message.
34541
34542 Action: No operator action is required.
34543
34544
34545 bce_save.pl1
34546 restoreTAPE_SET: Please mount tape# TAPE_NUMBER
34547 on TAPE_DEV.
34548
34549
34550 Stream: BOS Typewriter sounds beeper
34551
34552 Time: System Intialization.
34553
34554 Meaning: Just an informative message.
34555
34556 Action: Mount tape on the device.
34557
34558
34559 bce_save.pl1
34560 restoreTAPE_SET: Please mount the "Info" tape
34561 on TAPE_DEV.
34562
34563
34564 Stream: BOS Typewriter sounds beeper
34565
34566 Time: System Intialization.
34567
34568 Meaning: Just an informative message.
34569
34570 Action: Mount the tape on the device.
34571
34572
34573 bce_save.pl1
34574 restoreTAPE_SET: Please mount the "restart"
34575 tape on TAPE_DEV.
34576
34577
34578 Stream: BOS Typewriter sounds beeper
34579
34580
34581
34582 restoreTAPE_SET 597 08/21/20 MR12.7^L
34583
34584
34585 Time: System Intialization.
34586
34587 Meaning: Just an informative message.
34588
34589 Action: Mount the tape on the device.
34590
34591
34592 bce_save_util_.pl1
34593 restoreTAPE_SET: Please pre-mount tape#
34594 TAPE_NUMBER on TAPE_DEV.
34595
34596
34597 Stream: BOS Typewriter.
34598
34599 Time: System Intialization.
34600
34601 Meaning: The program is able to look ahead and find the
34602 tape that will be required next. This is an
34603 informative message that allows the restore to
34604 move at a faster pace.
34605
34606 Action: Mount the specified tape on the specified device.
34607
34608
34609 bce_save.pl1
34610 restoreTAPE_SET: Readjusting tape sequence # to
34611 REC_NUM.
34612
34613
34614 Stream: BOS Typewriter.
34615
34616 Time: System Intialization.
34617
34618 Meaning: The missing record previously reported by the
34619 "Record sequence error ..." message can not be
34620 found. The internal tape sequence counter is
34621 corrected and processing continues as normal.
34622
34623 Action: No operator action is required.
34624
34625
34626 bce_save.pl1
34627 restoreTAPE_SET: Record sequence error on tape#
34628 TAPE_NUMBER TAPE_DEV should be record #
34629 REC_NUM was record # REC_NUM.
34630
34631
34632
34633 Stream: BOS Typewriter.
34634
34635 Time: System Intialization.
34636
34637
34638
34639
34640 restoreTAPE_SET 598 08/21/20 MR12.7^L
34641
34642
34643 Meaning: Informative message that the sequence number on
34644 the tape is out of sync with what the program
34645 expects. If the WAS is only one record more than
34646 the S/B then the program will attempt to relocate
34647 the missing record by backspacing two records and
34648 rereading the records.
34649
34650 Action: No operator action is required.
34651
34652
34653 bce_save.pl1
34654 restoreTAPE_SET: Relocated tape sequence #
34655 REC_NUM
34656
34657
34658 Stream: BOS Typewriter.
34659
34660 Time: System Intialization.
34661
34662 Meaning: The missing record previously reported by the
34663 "Record sequence error ..." message has been
34664 found. Processing continues as normal.
34665
34666 Action: No operator action is required.
34667
34668
34669 bce_save_util_.pl1
34670 restoreTAPE_SET: Removing volume PV_NAME from
34671 PV list because all partitions were removed.
34672
34673
34674
34675 Stream: BOS Typewriter.
34676
34677 Time: System Intialization.
34678
34679 Meaning: It is nolonger necessary for the program to keep
34680 track of the PV since all of the partition
34681 requests have been removed.
34682
34683 Action: Correct the control files accordingly.
34684
34685
34686 bce_save.pl1
34687 restoreTAPE_SET: restore complete...
34688
34689
34690 Stream: BOS Typewriter.
34691
34692 Time: System Intialization.
34693
34694 Meaning: Just an informative message.
34695
34696
34697
34698 restoreTAPE_SET 599 08/21/20 MR12.7^L
34699
34700
34701 Action: No operator action is required.
34702
34703
34704 bce_save.pl1
34705 restoreTAPE_SET: Restore of volume PV_NAME on
34706 DISK_DEV complete.
34707
34708
34709 Stream: BOS Typewriter.
34710
34711 Time: System Intialization.
34712
34713 Meaning: Just an informative message.
34714
34715 Action: No operator action is required.
34716
34717
34718 bce_save.pl1
34719 restoreTAPE_SET: Skipping volume PV_NAME on
34720 DISK_DEV restore complete.
34721
34722
34723 Stream: BOS Typewriter.
34724
34725 Time: System Intialization.
34726
34727 Meaning: Just an informative message.
34728
34729 Action: No operator action is required.
34730
34731
34732 bce_save.pl1
34733 restoreTAPE_SET: Starting from volume PV_NAME
34734 on DISK_DEV.
34735
34736
34737 Stream: BOS Typewriter.
34738
34739 Time: System Intialization.
34740
34741 Meaning: Just an informative message.
34742
34743 Action: No operator action is required.
34744
34745
34746 bce_save.pl1
34747 restoreTAPE_SET: Tape on TAPE_DEV does not
34748 contain a supported tape label version.
34749
34750
34751 Stream: BOS Typewriter.
34752
34753 Time: System Intialization.
34754
34755
34756 restoreTAPE_SET 600 08/21/20 MR12.7^L
34757
34758
34759 Meaning: The tape contains a tape version identifier that
34760 is nolonger supported.
34761
34762 Action: Use the "restore -display_info_tape tapX_NN"
34763 option to display the tape.
34764
34765
34766
34767 bce_save.pl1
34768 restoreTAPE_SET: Tape on TAPE_DEV does not
34769 contain a valid label.
34770
34771
34772 Stream: BOS Typewriter.
34773
34774 Time: System Intialization.
34775
34776 Meaning: The tape just read is not a valid save/restore
34777 tape.
34778
34779 Action: Follow normal recovery procedures.
34780
34781
34782 bce_save.pl1
34783 restoreTAPE_SET: Tape on TAPE_DEV is not part
34784 of this set.
34785
34786
34787 Stream: BOS Typewriter.
34788
34789 Time: System Intialization.
34790
34791 Meaning: The tape just read contains a different tape set
34792 name than what is currently being handled via the
34793 control file.
34794
34795 Action: Follow normal recovery procedures.
34796
34797
34798 bce_save_util_.pl1
34799 restoreTAPE_SET: Tape subsystem "SUB_SYS" is
34800 not defined in the config.
34801
34802
34803 Stream: BOS Typewriter.
34804
34805 Time: System Intialization.
34806
34807 Meaning: No "prph" entry could be found for the tape
34808 subsystem.
34809
34810 Action: Correct config_deck or save/restore control
34811 files to indicate proper tape subsystem.
34812
34813
34814 restoreTAPE_SET 601 08/21/20 MR12.7^L
34815
34816
34817
34818
34819 bce_save.pl1
34820 restoreTAPE_SET: Tape# TAPE_NUMBER on TAPE_DEV
34821 created DATE_TIME
34822
34823
34824 Stream: BOS Typewriter.
34825
34826 Time: System Intialization.
34827
34828 Meaning: Just an informative message.
34829
34830 Action: No operator action is required.
34831
34832
34833 bce_save.pl1
34834 restoreTAPE_SET: The following tape devices
34835 will be used:
34836
34837
34838 Stream: BOS Typewriter.
34839
34840 Time: System Intialization.
34841
34842 Meaning: Just an informative message.
34843
34844 Action: No operator action is required.
34845
34846
34847 bce_save.pl1
34848 restoreTAPE_SET: Time-out waiting for special
34849 interrupt.
34850
34851
34852 Stream: BOS Typewriter.
34853
34854 Time: System Intialization.
34855
34856 Meaning: The program was waiting for a special to come from
34857 the device but none was recieved in the alloted
34858 time.
34859
34860 Action: Follow normal recovery procedures.
34861
34862
34863 bce_save_util_.pl1
34864 restoreTAPE_SET: Unable to restore
34865 "PARTITION_NAME" partition. Internal partition
34866 list full.
34867
34868
34869
34870
34871
34872 restoreTAPE_SET 602 08/21/20 MR12.7^L
34873
34874
34875 Stream: BOS Typewriter.
34876
34877 Time: System Intialization.
34878
34879 Meaning: More partitions have been requested than the
34880 program can handle.
34881
34882 Action: Change control files to reduce the number defined
34883 possibly by breaking them up into seperate tape
34884 sets.
34885
34886
34887
34888 bce_save_util_.pl1
34889 restoreTAPE_SET: Unable to restore
34890 "PARTITION_NAME" partition. N partitions already
34891 defined
34892
34893
34894
34895 Stream: BOS Typewriter.
34896
34897 Time: System Intialization.
34898
34899 Meaning: An attempt has been made to restore more than the
34900 N maximum partitions allowed.
34901
34902 Action: Change control filess to reduce the number
34903 requested.
34904
34905
34906 bce_save_util_.pl1
34907 restoreTAPE_SET: Unable to restore only
34908 partitions.
34909
34910
34911 Stream: BOS Typewriter.
34912
34913 Time: System Intialization.
34914
34915 Meaning: A request to restore partition information on this
34916 PV was made but the PV does not contain a vaild
34917 label to locate the partition information. The PV
34918 is removed from the restore list.
34919
34920 Action: Follow normal recovery procedures.
34921
34922
34923 bce_save.pl1
34924 restoreTAPE_SET: Unable to set density on
34925 TAPE_DEV.
34926
34927
34928
34929
34930 restoreTAPE_SET 603 08/21/20 MR12.7^L
34931
34932
34933 Stream: BOS Typewriter.
34934
34935 Time: System Intialization.
34936
34937 Meaning: The program was unable to set the required density
34938 of the tape device.
34939
34940 Action: Follow normal recovery procedures.
34941
34942
34943 bce_save.pl1
34944 restoreTAPE_SET: Unloading "Info" tape from
34945 TAPE_DEV REC_CNT records ERR_CNT errors
34946
34947
34948 Stream: BOS Typewriter.
34949
34950 Time: System Intialization.
34951
34952 Meaning: Just an informative message.
34953
34954 Action: No operator action is required.
34955
34956
34957 bce_save.pl1
34958 restoreTAPE_SET: Unloading tape# TAPE_NUMBER
34959 from TAPE_DEV REC_CNT records ERR_CNT errors
34960
34961
34962 Stream: BOS Typewriter.
34963
34964 Time: System Intialization.
34965
34966 Meaning: Just an informative message.
34967
34968 Action: No operator action is required.
34969
34970
34971 bce_save.pl1
34972 restoreTAPE_SET: Unloading TAPE_DEV REC_CNT
34973 records ERR_CNT errors
34974
34975
34976 Stream: BOS Typewriter.
34977
34978 Time: System Intialization.
34979
34980 Meaning: Just an informative message.
34981
34982 Action: No operator action is required.
34983
34984
34985 bce_save_util_.pl1
34986
34987
34988 restoreTAPE_SET 604 08/21/20 MR12.7^L
34989
34990
34991 restoreTAPE_SET: Volume on DISK_DEV is not a
34992 MULTICS_VOL_ID.
34993
34994
34995 Stream: BOS Typewriter.
34996
34997 Time: System Intialization.
34998
34999 Meaning: Informative message to let the operator know that
35000 the volume does not currently contain a valid
35001 Multics label.
35002
35003 Action: No operator action is required.
35004
35005
35006 bce_save_util_.pl1
35007 restoreTAPE_SET: Volume PV_NAME not found in
35008 tape label. Removing from PV list.
35009
35010
35011
35012 Stream: BOS Typewriter.
35013
35014 Time: System Intialization.
35015
35016 Meaning: A request was made to restore a PV but the PV was
35017 not saved as part of this tape set.
35018
35019 Action: Correct the control files accordingly.
35020
35021
35022 bce_save_util_.pl1
35023 restoreTAPE_SET: Volume PV_NAME will become
35024 NEW_PV_NAME as requested.
35025
35026
35027 Stream: BOS Typewriter.
35028
35029 Time: System Intialization.
35030
35031 Meaning: The PV to be restored currently has a dirrerent
35032 label than that to be restored. This is only an
35033 informative message to make the user aware of the
35034 change.
35035
35036 Action: No operator action is required.
35037
35038
35039 bce_save.pl1
35040 restoreTAPE_SET: Volume PV_NAME record
35041 REC_NUM on tape# TAPE_NUMBER TAPE_DEV
35042
35043
35044
35045
35046 restoreTAPE_SET 605 08/21/20 MR12.7^L
35047
35048
35049 Stream: BOS Typewriter.
35050
35051 Time: System Intialization.
35052
35053 Meaning: Just an informative message.
35054
35055 Action: No operator action is required.
35056
35057
35058 bce_save.pl1
35059 restoreTAPE_SET: Waiting for special on
35060 TAPE_DEV.
35061
35062
35063 Stream: BOS Typewriter.
35064
35065 Time: System Intialization.
35066
35067 Meaning: Just an informative message.
35068
35069 Action: No operator action is required.
35070
35071
35072 bce_save.pl1
35073 restoreTAPE_SET: Zeroing partition
35074 PARTITION_NAME on PV_NAME record REC_NUM.
35075
35076
35077 Stream: BOS Typewriter.
35078
35079 Time: System Intialization.
35080
35081 Meaning: Just an informative message.
35082
35083 Action: No operator action is required.
35084
35085
35086 bce_save_util_.pl1
35087 restore: Attaching TAPE_DEV. ERR_MESSAGE
35088
35089
35090 Stream: BOS Typewriter sounds beeper
35091
35092 Time: System Intialization.
35093
35094 Meaning: IOI has returned a non-zero error code in response
35095 to a request to assign TAPE_DEV.
35096
35097 Action: Follow normal recovery procedures.
35098
35099
35100 bce_save.pl1
35101 restore: bce_ioi_post_seg. ERR_MESSAGE
35102
35103
35104 restore 606 08/21/20 MR12.7^L
35105
35106
35107 Stream: BOS Typewriter sounds beeper
35108
35109 Time: System Intialization.
35110
35111 Meaning: The program was unable to get a pointer to the
35112 above segment. This indicates a logic error in
35113 the supervisor or CPU or memory hardware
35114 problems.
35115
35116 Action: Contact the system programming staff.
35117
35118
35119 bce_save.pl1
35120 restore: bootload_disk_post_seg. ERR_MESSAGE
35121
35122
35123 Stream: BOS Typewriter sounds beeper
35124
35125 Time: System Intialization.
35126
35127 Meaning: The program was unable to get a pointer to the
35128 above segment. This indicates a logic error in
35129 the supervisor or CPU or memory hardware
35130 problems.
35131
35132 Action: Contact the system programming staff.
35133
35134
35135 bce_save_util_.pl1
35136 restore: Could not read label of PV_NAME on
35137 DISK_DEV. ERR_MESSAGE
35138
35139
35140 Stream: BOS Typewriter sounds beeper
35141
35142 Time: System Intialization.
35143
35144 Meaning: The volume label of the PV could not be read due
35145 to the error given in ERR_MESSAGE.
35146
35147 Action: A operator query is done to find out if the read
35148 should be retried or the PV removed from the list.
35149
35150
35151
35152 bce_save.pl1
35153 restore: Getting tape label temp segment.
35154 ERR_MESSAGE
35155
35156
35157 Stream: BOS Typewriter sounds beeper
35158
35159 Time: System Intialization.
35160
35161
35162 restore 607 08/21/20 MR12.7^L
35163
35164
35165 Meaning: An error occured while attempting to get a
35166 temporary segment to hold the tape label
35167 information.
35168
35169 Action: Contact the system programming staff.
35170
35171
35172 bce_save_util_.pl1
35173 restore: Initiating CONTROL_FILE_NAME for
35174 set-TAPE_SET_IDX ERR_MESSAGE
35175
35176
35177 Stream: BOS Typewriter sounds beeper
35178
35179 Time: System Intialization.
35180
35181 Meaning: An error was detected while initiating the restore
35182 control file.
35183
35184 Action: Contact the system programming staff. $recover
35185
35186
35187 bce_save.pl1
35188 restore: PV_NAME ERR_MESSAGE
35189
35190
35191 Stream: BOS Typewriter sounds beeper
35192
35193 Time: System Intialization.
35194
35195 Meaning: The call to bootload_disk_io$test_done has
35196 returned a non-zero error code.
35197
35198 Action: Contact the system programming staff. $recover
35199
35200
35201 bce_save.pl1
35202 restore: pvt. ERR_MESSAGE
35203
35204
35205 Stream: BOS Typewriter sounds beeper
35206
35207 Time: System Intialization.
35208
35209 Meaning: The program was unable to get a pointer to the
35210 above segment. This indicates a logic error in
35211 the supervisor or CPU or memory hardware
35212 problems.
35213
35214 Action: Contact the system programming staff.
35215
35216
35217 bce_save.pl1
35218
35219
35220 restore 608 08/21/20 MR12.7^L
35221
35222
35223 restore: Restarting restore of set "TAPE_SET" on
35224 TAPE_DEV.
35225
35226
35227 Stream: BOS Typewriter.
35228
35229 Time: System Intialization.
35230
35231 Meaning: Just an informative message.
35232
35233 Action: No operator action is required.
35234
35235
35236 bce_save_util_.pl1
35237 restore: Setting max workspace for TAPE_DEV.
35238 ERR_MESSAGE
35239
35240
35241 Stream: BOS Typewriter sounds beeper
35242
35243 Time: System Intialization.
35244
35245 Meaning: IOI has returned a non-zero error code in response
35246 to a request to set the max workspace size for
35247 TAPE_DEV.
35248
35249 Action: Contact the system programming staff.
35250
35251
35252 bce_save.pl1
35253 restore: Setting status index for TAPE_DEV.
35254 ERR_MESSAGE
35255
35256
35257 Stream: BOS Typewriter sounds beeper
35258
35259 Time: System Intialization.
35260
35261 Meaning: IOI has returned a non-zero error which has been
35262 expanded in ERR_MESSAGE.
35263
35264 Action: Contact the system programming staff.
35265
35266
35267 bce_save_util_.pl1
35268 restore: Setting up workspace for TAPE_DEV.
35269 ERR_MESSAGE
35270
35271
35272 Stream: BOS Typewriter sounds beeper
35273
35274 Time: System Intialization.
35275
35276
35277
35278 restore 609 08/21/20 MR12.7^L
35279
35280
35281 Meaning: IOI has returned a non-zero error code from the
35282 request to create a workspace for TAPE_DEV.
35283
35284 Action: Contact the system programming staff.
35285
35286
35287 bce_save_util_.pl1
35288 restore: si ERR_MESSAGE
35289
35290
35291 Stream: BOS Typewriter sounds beeper
35292
35293 Time: System Intialization.
35294
35295 Meaning: An error has been found with the internal "si"
35296 structure.This indicates a logic error in the
35297 supervisor or CPU or memory hardware problems.
35298
35299 Action: Contact the system programming staff.
35300
35301
35302 bce_save_util_.pl1
35303 restore: sri ERR_MESSAGE
35304
35305
35306 Stream: BOS Typewriter sounds beeper
35307
35308 Time: System Intialization.
35309
35310 Meaning: An error has been found with the internal "sri"
35311 structure.This indicates a logic error in the
35312 supervisor or CPU or memory hardware problems.
35313
35314 Action: Contact the system programming staff.
35315
35316
35317 bce_save.pl1
35318 restore: Stopping restore of set "TAPE_SET".
35319
35320
35321 Stream: BOS Typewriter.
35322
35323 Time: System Intialization.
35324
35325 Meaning: Just an informative message.
35326
35327 Action: No operator action is required.
35328
35329
35330 bce_save_util_.pl1
35331 restore: TAPE_DEV ERR_MESSAGE
35332
35333
35334
35335
35336 restore 610 08/21/20 MR12.7^L
35337
35338
35339 Stream: BOS Typewriter sounds beeper
35340
35341 Time: System Intialization.
35342
35343 Meaning: An error occured while scanning the tape subsystem
35344 survey data.
35345
35346 Action: Follow normal recovery procedures.
35347
35348
35349 bce_save.pl1
35350 restore: tape_error_data. ERR_MESSAGE
35351
35352
35353 Stream: BOS Typewriter sounds beeper
35354
35355 Time: System Intialization.
35356
35357 Meaning: The program was unable to get a pointer to the
35358 above segment. This indicates a logic error in
35359 the supervisor or CPU or memory hardware
35360 problems.
35361
35362 Action: Contact the system programming staff.
35363
35364
35365 bce_save.pl1
35366 restore: Unassigning TAPE_DEV. ERR_MESSAGE
35367
35368
35369 Stream: BOS Typewriter sounds beeper
35370
35371 Time: System Intialization.
35372
35373 Meaning: IOI has returned a non-zero error which has been
35374 expanded in ERR_MESSAGE.
35375
35376 Action: Contact the system programming staff.
35377
35378
35379 retv_copy.pl1
35380 retv_copy: deleting PATH without recovering
35381 resources ERROR_MESSAGE
35382
35383
35384 Stream: Logged in SYSERR log.
35385
35386 Time: Volume retrieval
35387
35388 Meaning: While retrieving a segment the retriever
35389 attempted to delete an old copy of a segment
35390 before using a newer one. The deletion attempt
35391
35392
35393
35394 retv_copy 611 08/21/20 MR12.7^L
35395
35396
35397 failed. Space may be wasted on the volume until a
35398 sweep_pv -gc is done.
35399
35400 Action: Note for volume administrator.
35401
35402
35403 ring_alarm.pl1
35404 ring_alarm$fault: Reset admin privileges.
35405
35406
35407 Stream: Logged in SYSERR log.
35408
35409 Time: While system is running.
35410
35411 Meaning: On exit from ring one one or more AIM privileges
35412 were still set by privileged ring 1 code. These
35413 are reset and the following log message from
35414 set_privileges lists them. This indicates a
35415 benign bug in the ring one program that was
35416 running.
35417
35418 Action: Contact the system programming staff.
35419
35420
35421 ring_alarm.pl1
35422 ring_alarm$fault: Reset admin privileges.
35423
35424
35425 Stream: Logged in SYSERR log.
35426
35427 Time: While system is running.
35428
35429 Meaning: On exit from ring one one or more AIM privileges
35430 were still set by privileged ring 1 code. These
35431 are reset and the following log message from
35432 set_privileges lists them. This indicates a
35433 benign bug in the ring one program that was
35434 running.
35435
35436 Action: Contact the system programming staff.
35437
35438
35439 ring_alarm.pl1
35440 ring_alarm$poll: Mysterious ring alarm.
35441
35442
35443 Stream: BOS Typewriter Crashes system
35444
35445 Time: While system is running.
35446
35447 Meaning: The ring alarm register was set on exit from ring
35448 zero but no reason for it was recorded for the
35449 process.
35450
35451
35452 ring_alarm$poll 612 08/21/20 MR12.7^L
35453
35454
35455 Action: Contact the system programming staff.
35456
35457
35458 ring_alarm.pl1
35459 ring_alarm$poll: Mysterious ring alarm.
35460
35461
35462 Stream: BOS Typewriter Crashes system
35463
35464 Time: While system is running.
35465
35466 Meaning: The ring alarm register was set on exit from ring
35467 zero but no reason for it was recorded for the
35468 process.
35469
35470 Action: Contact the system programming staff.
35471
35472
35473 ring_alarm.pl1
35474 ring_alarm: Fixed validation level on fault
35475 from OLD to NEW.
35476
35477
35478 Stream: BOS Typewriter sounds beeper
35479
35480 Time: While system is running.
35481
35482 Meaning: On exit from ring zero the validation level was
35483 less than the ring that is being returned to. The
35484 validation level is corrected to its value when it
35485 called into the inner ring. This indicates a
35486 benign bug in the inner ring entry called.
35487
35488 Action: Contact the system programming staff.
35489
35490
35491 ring_alarm.pl1
35492 ring_alarm: Fixed validation level on fault
35493 from OLD to NEW.
35494
35495
35496 Stream: BOS Typewriter sounds beeper
35497
35498 Time: While system is running.
35499
35500 Meaning: On exit from ring zero the validation level was
35501 less than the ring that is being returned to. The
35502 validation level is corrected to its value when it
35503 called into the inner ring. This indicates a
35504 benign bug in the inner ring entry called.
35505
35506 Action: Contact the system programming staff.
35507
35508
35509
35510 rldr_arg_reader_ 613 08/21/20 MR12.7^L
35511
35512
35513
35514
35515 rldr_arg_reader_.pl1
35516 rldr_arg_reader_: ARG: ERROR_MESS
35517
35518
35519 Stream: BOS Typewriter.
35520
35521 Time: While system is running.
35522
35523 Meaning: Invalid arguments were given to the reloader.
35524
35525 Action: Enter a corrected command line.
35526
35527
35528 rldr_check_pvol_.pl1
35529 rldr_check_pvol_: Maximum access class mismatch
35530 rldr_check_pvol_: Have ACCESS_CLASS; Volog label
35531 requires ACCESS_CLASS
35532
35533
35534
35535 Stream: $rld_on
35536
35537 Time: $reload
35538
35539 Meaning: The maximum access class for the volume does not
35540 match the volume log.
35541
35542 Action: Enter a corrected command line.
35543
35544
35545 rldr_check_pvol_.pl1
35546 rldr_check_pvol_: Minimum access class mismatch
35547 rldr_check_pvol_: Have ACCESS_CLASS; Volog label
35548 requires ACCESS_CLASS
35549
35550
35551
35552 Stream: $rld_on
35553
35554 Time: $reload
35555
35556 Meaning: The minimum access class for the volume does not
35557 match the volume log.
35558
35559 Action: Enter a corrected command line.
35560
35561
35562 rldr_check_pvol_.pl1
35563 rldr_check_pvol_: Partition NAME not found on
35564 physical volume
35565
35566
35567
35568 rldr_check_pvol_ 614 08/21/20 MR12.7^L
35569
35570
35571 Stream: $rld_on
35572
35573 Time: $reload
35574
35575 Meaning: The partition NAME is missing from the volume
35576 label.
35577
35578 Action: Reinitialize the volume correctly.
35579
35580
35581 rldr_check_pvol_.pl1
35582 rldr_check_pvol_: Partition NAME size mismatch
35583 rldr_check_pvol_: Have NN records; Volog label
35584 requires MM
35585
35586
35587
35588 Stream: $rld_on
35589
35590 Time: $reload
35591
35592 Meaning: The size for partition NAME does not match.
35593
35594 Action: Reinitialize the volume correctly.
35595
35596
35597 rldr_check_pvol_.pl1
35598 rldr_check_pvol_: Reload may overflow volume
35599 rldr_check_pvol_: Have NN records; Volog label
35600 requires NN records
35601
35602
35603
35604 Stream: $rld_on
35605
35606 Time: $reload
35607
35608 Meaning: The output volume is too small.
35609
35610 Action: Reinitialize it correctly with init_vol.
35611
35612
35613 rldr_check_pvol_.pl1
35614 rldr_check_pvol_: Reload may overflow vtoc
35615 rldr_check_pvol_: Have NN vtoce; Volog label
35616 requires NN vtoce
35617
35618
35619
35620 Stream: $rld_on
35621
35622 Time: $reload
35623
35624
35625
35626 rldr_check_pvol_ 615 08/21/20 MR12.7^L
35627
35628
35629 Meaning: The output volume has too small a VTOC.
35630
35631 Action: Reinitialize the output volume with init_vol.
35632
35633
35634 rldr_check_pvol_.pl1
35635 rldr_check_pvol_: Unitialized output volume
35636
35637
35638 Stream: $rld_on
35639
35640 Time: $reload
35641
35642 Meaning: The output volume must be initialized with
35643 init_vol before use.
35644
35645 Action: Switch the output volume to storage-system status
35646 with the sdu command and then use init_vol to set
35647 it up.
35648
35649
35650
35651 rldr_check_pvol_.pl1
35652 rldr_check_pvol_: Volume mismatch
35653 rldr_check_pvol_: Have PVNAMEpvid = WWW; Volog
35654 label requires PVNAMEpvid = WWW
35655
35656
35657
35658 Stream: $rld_on
35659
35660 Time: $reload
35661
35662 Meaning: The output volume label disagrees with the volume
35663 log.
35664
35665 Action: Reinitialize the output volume correctly with
35666 init_vol.
35667
35668
35669 rldr_label_.pl1
35670 rldr_label_: Incorrect output medium mounted:
35671 ERROR_MESS
35672
35673
35674 Stream: $rld_out
35675
35676 Time: $reload
35677
35678 Meaning: Someting is wrong with a reloader output volume.
35679
35680 Action: Mount a correct volume and try again.
35681
35682
35683
35684 rldr_label_ 616 08/21/20 MR12.7^L
35685
35686
35687
35688
35689 rldr_label_.pl1
35690 rldr_label_: Label position failed: ERROR_MESS
35691
35692
35693 Stream: $rld_out
35694
35695 Time: $reload
35696
35697 Meaning: Someting is wrong with a reloader output volume.
35698
35699 Action: Mount a correct volume and try again.
35700
35701
35702 rldr_label_.pl1
35703 rldr_label_: Label read failed: ERROR_MESS
35704
35705
35706 Stream: $rld_out
35707
35708 Time: $reload
35709
35710 Meaning: Someting is wrong with a reloader output volume.
35711
35712 Action: Mount a correct volume and try again.
35713
35714
35715 rldr_label_.pl1
35716 rldr_label_: Label write failed: ERROR_MESS
35717
35718
35719 Stream: $rld_out
35720
35721 Time: $reload
35722
35723 Meaning: Someting is wrong with a reloader output volume.
35724
35725 Action: Mount a correct volume and try again.
35726
35727
35728 rldr_label_.pl1
35729 rldr_label_: Output volume pvid MMMMMMMMMMMM not
35730 equal to online pvid NNNNNNNNNNNN for pv PPPPPPPP.
35731 Invalid volume identifier.
35732
35733
35734
35735 Stream: $rld_out
35736
35737 Time: $reload
35738
35739
35740
35741
35742 rldr_label_ 617 08/21/20 MR12.7^L
35743
35744
35745 Meaning: The PVID on the output disk volume does not match
35746 the PVID as recorded in the pvolog for the disk
35747 volume. This indicates that either the label on
35748 the PV is incorrect or the pvolog segment is
35749 corrupted.
35750
35751 Action: Verify the PVID using output from the
35752 display_disk_label command. If the PVID from ddl
35753 output is differnet from that reported for the
35754 output volume use change_volume_registration and
35755 init_vol to correct the disk label. If the online
35756 PVID does not match use the recover_volume_log
35757 command to retrieve a correct pvolog segment.
35758 Retry the reload.
35759
35760
35761
35762 rldr_output_.pl1
35763 rldr_output_: Output volume attachment failed:
35764 ERROR_MESS
35765
35766
35767 Stream: $rld_out
35768
35769 Time: $reload
35770
35771 Meaning: This indicates a logic error in the supervisor or
35772 CPU or memory hardware problems.
35773
35774 Action: Mount a different output volume and try again.
35775
35776
35777 rldr_output_.pl1
35778 rldr_output_: Output volume opening failed:
35779 ERROR_MESS
35780
35781
35782 Stream: $rld_out
35783
35784 Time: $reload
35785
35786 Meaning: This indicates a logic error in the supervisor or
35787 CPU or memory hardware problems.
35788
35789 Action: Mount a different output volume and try again.
35790
35791
35792 rldr_report_.pl1
35793 rldr_report_: Error file NAME created
35794
35795
35796 Stream: $rld_on
35797
35798
35799
35800 rldr_report_ 618 08/21/20 MR12.7^L
35801
35802
35803 Time: $reload
35804
35805 Meaning: The reloader attempted to create an error file.
35806
35807 Action: No operator action is required.
35808
35809
35810 rldr_report_.pl1
35811 rldr_report_: Error opening error file:
35812 ERROR_MESS
35813
35814
35815 Stream: $rld_on
35816
35817 Time: $reload
35818
35819 Meaning: The reloader attempted to create an error file.
35820
35821 Action: No operator action is required.
35822
35823
35824 rldr_report_.pl1
35825 rldr_report_: Unable to attach error file:
35826 ERROR_MESS
35827
35828
35829 Stream: $rld_on
35830
35831 Time: $reload
35832
35833 Meaning: The reloader attempted to create an error file.
35834
35835 Action: No operator action is required.
35836
35837
35838 rldr_volume_map_.pl1
35839 rldr_volume_map_: Attempt to deposit free record
35840
35841
35842 Stream: $rld_out
35843
35844 Time: $reload
35845
35846 Meaning: An error was encountered during reload volume map
35847 construction. Reloading continues.
35848
35849 Action: No operator action is required.
35850
35851
35852 rldr_volume_map_.pl1
35853 rldr_volume_map_: Attempt to deposit out of range
35854 address WWW
35855
35856
35857
35858 rldr_volume_map_ 619 08/21/20 MR12.7^L
35859
35860
35861 Stream: $rld_out
35862
35863 Time: $reload
35864
35865 Meaning: An error was encountered during reload volume map
35866 construction. Reloading continues.
35867
35868 Action: No operator action is required.
35869
35870
35871 rldr_volume_map_.pl1
35872 rldr_volume_map_: Error reading volume map:
35873 ERROR_MESS
35874
35875
35876 Stream: $rld_out
35877
35878 Time: $reload
35879
35880 Meaning: An error was encountered during reload volume map
35881 construction. Reloading continues.
35882
35883 Action: No operator action is required.
35884
35885
35886 rldr_volume_map_.pl1
35887 rldr_volume_map_: Error writing volume map:
35888 ERROR_MESS
35889
35890
35891 Stream: $rld_out
35892
35893 Time: $reload
35894
35895 Meaning: An error was encountered during reload volume map
35896 construction. Reloading continues.
35897
35898 Action: No operator action is required.
35899
35900
35901 rldr_volume_map_.pl1
35902 rldr_volume_map_: Map position failed:
35903 ERROR_MESS
35904
35905
35906 Stream: $rld_out
35907
35908 Time: $reload
35909
35910 Meaning: An error was encountered during reload volume map
35911 construction. Reloading continues.
35912
35913 Action: No operator action is required.
35914
35915
35916 rldr_volume_map_ 620 08/21/20 MR12.7^L
35917
35918
35919
35920
35921 rldr_volume_map_.pl1
35922 rldr_volume_map_: Map position failed:
35923 ERROR_MESS
35924
35925
35926 Stream: $rld_out
35927
35928 Time: $reload
35929
35930 Meaning: An error was encountered during reload volume map
35931 construction. Reloading continues.
35932
35933 Action: No operator action is required.
35934
35935
35936 rldr_vtoc_buffer_.pl1
35937 rldr_vtoc_buffer_: Unable to update vtoce WWW:
35938 ERROR_MESS
35939
35940
35941 Stream: $rld_out
35942
35943 Time: $reload
35944
35945 Meaning: An error occurred updating a VTOCE. Reloading
35946 continues.
35947
35948 Action: No operator action is required.
35949
35950
35951 rldr_vtoc_header_.pl1
35952 rldr_vtoc_header_: VTOC header position failed
35953
35954
35955 Stream: $rld_out
35956
35957 Time: $reload
35958
35959 Meaning: An error occurred writing out the VTOC header for
35960 an output volume.
35961
35962 Action: Contact the system programming staff.
35963
35964
35965 rldr_vtoc_header_.pl1
35966 rldr_vtoc_header_: VTOC header position failed
35967
35968
35969 Stream: $rld_out
35970
35971 Time: $reload
35972
35973
35974 rldr_vtoc_header_ 621 08/21/20 MR12.7^L
35975
35976
35977 Meaning: An error occurred writing out the VTOC header for
35978 an output volume.
35979
35980 Action: Contact the system programming staff.
35981
35982
35983 rldr_vtoc_header_.pl1
35984 rldr_vtoc_header_: VTOC header read failed
35985
35986
35987 Stream: $rld_out
35988
35989 Time: $reload
35990
35991 Meaning: An error occurred writing out the VTOC header for
35992 an output volume.
35993
35994 Action: Contact the system programming staff.
35995
35996
35997 rldr_vtoc_header_.pl1
35998 rldr_vtoc_header_: VTOC header write failed
35999
36000
36001 Stream: $rld_out
36002
36003 Time: $reload
36004
36005 Meaning: An error occurred writing out the VTOC header for
36006 an output volume.
36007
36008 Action: Contact the system programming staff.
36009
36010
36011 rldr_vtoc_header_.pl1
36012 rldr_vtoc_header_: VTOC map position failed
36013
36014
36015 Stream: $rld_out
36016
36017 Time: $reload
36018
36019 Meaning: An error occurred writing out the VTOC map for an
36020 output volume.
36021
36022 Action: Contact the system programming staff.
36023
36024
36025 rldr_vtoc_header_.pl1
36026 rldr_vtoc_header_: VTOC map read failed
36027
36028
36029 Stream: $rld_out
36030
36031
36032 rldr_vtoc_header_ 622 08/21/20 MR12.7^L
36033
36034
36035 Time: $reload
36036
36037 Meaning: An error occurred reading the VTOC map for an
36038 output volume.
36039
36040 Action: Contact the system programming staff.
36041
36042
36043 rldr_vtoc_header_.pl1
36044 rldr_vtoc_header_: VTOC map write failed
36045
36046
36047 Stream: $rld_out
36048
36049 Time: $reload
36050
36051 Meaning: An error occurred writing out the VTOC map for an
36052 output volume.
36053
36054 Action: Contact the system programming staff.
36055
36056
36057 salv_check_vtoce_.pl1
36058 salv_check_vtoce_: ERROR_MESSAGE.
36059
36060
36061 Stream: Logged in SYSERR log.
36062
36063 Time: Salvaging
36064
36065 Meaning: An error occurred while checking VTOCEs.
36066
36067 Action: Contact the system programming staff.
36068
36069
36070 salv_dir_checker_.pl1
36071 salv_dir_checker_: MESSAGE.
36072
36073
36074 Stream: Logged in SYSERR log.
36075
36076 Time: Salvaging
36077
36078 Meaning: Various messages are printed by salv_dir_checker_
36079 indicating what salvaging is taking place--ACL
36080 counts being changed entry counts being changed
36081 unique names supplied for segments with invalid
36082 names etc.
36083
36084 Action: No operator action is required.
36085
36086
36087 salv_dump_copy.pl1
36088
36089
36090 salv_dump_copy 623 08/21/20 MR12.7^L
36091
36092
36093 salv_dump_copy: Appending SEGNAME to dump
36094 directory ERRORMESSAGE
36095
36096
36097 Stream: Logged in SYSERR log.
36098
36099 Time: While system is running.
36100
36101 Meaning: The directory salvager could not append a copy of
36102 a directory being salvaged or the stack at the
36103 time of salvage to the system dump directory.
36104
36105 Action: Check the ACL on the system dump directory and
36106 site exec_coms which set it. Contact the system
36107 programming staff._sa
36108
36109
36110
36111 salv_dump_copy.pl1
36112 salv_dump_copy: Initiating SEGNAME ERRORMESSAGE
36113
36114
36115 Stream: Logged in SYSERR log.
36116
36117 Time: While system is running.
36118
36119 Meaning: The directory salvager could not initiate a copy
36120 of a ring 0 stack or directory being salvaged in
36121 the system dump directory. There may be ACL
36122 problems in the system dump directory.
36123
36124 Action: Contact the system programming staff._sa
36125
36126
36127 salv_dump_copy.pl1
36128 salv_dump_copy: seg_fault_error copying PPPP into
36129 >dumps>SEGNAME
36130
36131
36132 Stream: Logged in SYSERR log.
36133
36134 Time: While system is running.
36135
36136 Meaning: The directory salvager attempted to create a copy
36137 of a segment in >dumps but encountered a
36138 seg_fault_error condition while attempting to copy
36139 it. This is probably caused by quota problems in
36140 >dumps or insufficient space on the logical
36141 volume.
36142
36143 Action: Contact the system programming staff._sa
36144
36145
36146
36147
36148 salvage_dirs 624 08/21/20 MR12.7^L
36149
36150
36151 salv_caller.pl1
36152 salvage_dirs: decimal number required for level
36153 not BLAH
36154
36155
36156 Stream: Initializer process output.
36157
36158 Time: In response to an operator command.
36159
36160 Meaning: Incorrect arguments were specified.
36161
36162 Action: Enter a corrected command line.
36163
36164
36165 salv_caller.pl1
36166 salvage_dirs: depth must be between 0 and 15
36167
36168
36169 Stream: Initializer process output.
36170
36171 Time: In response to an operator command.
36172
36173 Meaning: Incorrect arguments were specified.
36174
36175 Action: Enter a corrected command line.
36176
36177
36178 salv_caller.pl1
36179 salvage_dirs: ERROR_MESSAGE
36180
36181
36182 Stream: Initializer process output.
36183
36184 Time: In response to an operator command.
36185
36186 Meaning: Incorrect arguments were specified.
36187
36188 Action: Enter a corrected command line.
36189
36190
36191 salv_caller.pl1
36192 salvage_dirs: ERROR_MESSAGE. level number
36193 required
36194
36195
36196 Stream: Initializer process output.
36197
36198 Time: In response to an operator command.
36199
36200 Meaning: Incorrect arguments were specified.
36201
36202 Action: Enter a corrected command line.
36203
36204
36205
36206 salvage_dirs 625 08/21/20 MR12.7^L
36207
36208
36209
36210
36211 salv_caller.pl1
36212 salvage_dirs: Inconsistent arguments have been
36213 specified
36214
36215
36216 Stream: Initializer process output.
36217
36218 Time: In response to an operator command.
36219
36220 Meaning: Incorrect arguments were specified.
36221
36222 Action: Enter a corrected command line.
36223
36224
36225 salv_caller.pl1
36226 salvage_dirs: must be in ring 1 for dir salv
36227
36228
36229 Stream: Initializer process output.
36230
36231 Time: In response to an operator command.
36232
36233 Meaning: Incorrect arguments were specified.
36234
36235 Action: Enter a corrected command line.
36236
36237
36238 salv_caller.pl1
36239 salvage_dirs: Specified control argument is not
36240 implemented by this command. BLAH
36241
36242
36243 Stream: Initializer process output.
36244
36245 Time: In response to an operator command.
36246
36247 Meaning: Incorrect arguments were specified.
36248
36249 Action: Enter a corrected command line.
36250
36251
36252 salv_caller.pl1
36253 salvage_dirs: VTOC checking is required for
36254 connection failure deletion.
36255
36256
36257 Stream: Initializer process output.
36258
36259 Time: In response to an operator command.
36260
36261
36262
36263
36264 salvage_dirs 626 08/21/20 MR12.7^L
36265
36266
36267 Meaning: An attempt was made to specify directory salvage
36268 with connection failure deletion but no VTOC
36269 checking.
36270
36271 Action: Enter a corrected command line.
36272
36273
36274 salv_caller.pl1
36275 salvage_dirs: Will not salvage
36276
36277
36278 Stream: Initializer process output.
36279
36280 Time: In response to an operator command.
36281
36282 Meaning: Incorrect arguments were specified.
36283
36284 Action: Enter a corrected command line.
36285
36286
36287 salv_caller.pl1
36288 salvage_dirs: will not salvage until root
36289 complete
36290
36291
36292 Stream: Initializer process output.
36293
36294 Time: In response to an operator command.
36295
36296 Meaning: Incorrect arguments were specified.
36297
36298 Action: Enter a corrected command line.
36299
36300
36301 salvage_pv.pl1
36302 salvage_pv: Bit map size is DD. WWo words s/b
36303 EE. FFo changing to latter.
36304
36305
36306 Stream: $salvout
36307
36308 Time: $salvt
36309
36310 Meaning: The bit map size in the volume label was incorrect
36311 and has been corrected.
36312
36313 Action: No operator action is required.
36314
36315
36316 salvage_pv.pl1
36317 salvage_pv: damaged switch found on for UUUU
36318 vtocx XXXo: NAME
36319
36320
36321
36322 salvage_pv 627 08/21/20 MR12.7^L
36323
36324
36325 Stream: $salvout
36326
36327 Time: $salvt
36328
36329 Meaning: The segment originally named NAME with unique ID
36330 UUUU at vtoc index XXXo was found to have its
36331 damaged switch on. The damaged switch can be set
36332 during the running of the system if page control
36333 encounters an I/O error. Damaged segments cannot
36334 be used until the damaged switch is reset.
36335
36336 Action: No operator action is required.
36337
36338
36339 salvage_pv.pl1
36340 salvage_pv: DDD damaged segments on volume PVNAME
36341 NNN damaged in this salvage.
36342
36343
36344 Stream: BOS Typewriter.
36345
36346 Time: $salvt
36347
36348 Meaning: DDD damaged segments were found on the volume
36349 PVNAME which has just been volume-salvaged. The
36350 damaged switch was set for NNN of these segments
36351 during this volume salvage. The damaged switch
36352 for the other segments had been set prior to the
36353 salvage.
36354
36355 Action: Inspect the syserr and Answering Service log to
36356 identify damaged segments. Prepare to recover
36357 them if necessary.
36358
36359
36360
36361 salvage_pv.pl1
36362 salvage_pv: dirsw turned off for vtocx XXXo:
36363 NAME
36364
36365
36366 Stream: $salvout
36367
36368 Time: $salvt
36369
36370 Meaning: The segment originally named NAME at vtoc index
36371 XXXo has had its directory switch turned off.
36372
36373 Action: No operator action is required.
36374
36375
36376 salvage_pv.pl1
36377
36378
36379
36380 salvage_pv 628 08/21/20 MR12.7^L
36381
36382
36383 salvage_pv: freeing UUUU deciduous vtocx XXXo:
36384 NAME
36385
36386
36387 Stream: $salvout
36388
36389 Time: $salvt
36390
36391 Meaning: The segment originally named NAME with unique ID
36392 UUUU at vtoc index XXXo was deciduous and has
36393 been deleted from the RPV. This is debugging
36394 output printed for system programmers if a SALV
36395 DEBG card is supplied.
36396
36397 Action: No operator action is required.
36398
36399
36400 salvage_pv.pl1
36401 salvage_pv: freeing UUUU per process vtocx XXXo:
36402 NAME
36403
36404
36405 Stream: $salvout
36406
36407 Time: $salvt
36408
36409 Meaning: The segment originally named NAME with unique ID
36410 UUUU at vtoc index XXXo was per-process and has
36411 been deleted. This is debugging output printed
36412 for system programmers if a SALV DEBG card is
36413 used.
36414
36415 Action: No operator action is required.
36416
36417
36418 salvage_pv.pl1
36419 salvage_pv: freeing UUUU per-bootload vtocx XXXo:
36420 NAME
36421
36422
36423 Stream: $salvout
36424
36425 Time: $salvt
36426
36427 Meaning: The segment originally named NAME with unique ID
36428 UUU at vtoc index XXXo was per-bootload inferior
36429 to a prior >sl1 and has been deleted. This is
36430 debugging output printed for system programmers if
36431 a SALV DEBG card is supplied.
36432
36433 Action: No operator action is required.
36434
36435
36436
36437
36438 salvage_pv 629 08/21/20 MR12.7^L
36439
36440
36441 salvage_pv.pl1
36442 salvage_pv: INIT_TABLES: aste pool WWWo too
36443 small.
36444
36445
36446 Stream: BOS Typewriter.
36447
36448 Time: While system is running.
36449
36450 Meaning: The physical volume salvager was unable to obtain
36451 a temporary AST entry for segment requiring WWWo
36452 ptws. No salvaging was done.
36453
36454 Action: Shut down manually correct the SST card and
36455 reboot. Then salvage all volumes since the
36456 indicator that volumes need salvaging may have
36457 been lost.
36458
36459
36460
36461 salvage_pv.pl1
36462 salvage_pv: Label times in advance of clock. The
36463 clock may be wrong.
36464
36465
36466 Stream: $salvout
36467
36468 Time: $salvt
36469
36470 Meaning: The label of the volume being salvaged contains
36471 one or more clock readings in advance of the
36472 current clock. Salvaging will proceed. The times
36473 are not corrected. If there is reason to believe
36474 that the system clock is incorrect shut the
36475 system down as soon as possible and take steps to
36476 recover that part of the hierarchy which may have
36477 been contaminated with bad clock values.
36478
36479 Action: No operator action is required.
36480
36481
36482 salvage_pv.pl1
36483 salvage_pv: map of assigned addresses changed.
36484
36485
36486 Stream: $salvout
36487
36488 Time: $salvt
36489
36490 Meaning: If any corrections were made to the map on the
36491 volume which shows which addresses are free and
36492 which are in use this message is printed. If the
36493
36494
36495
36496 salvage_pv 630 08/21/20 MR12.7^L
36497
36498
36499 volume was not properly shut down this message is
36500 to be expected.
36501
36502 Action: No operator action is required.
36503
36504
36505 salvage_pv.pl1
36506 salvage_pv: NN free vtoces added to free list.
36507
36508
36509 Stream: $salvout
36510
36511 Time: $salvt
36512
36513 Meaning: NN free VTOC entries were found while salvaging
36514 and added to the list of free VTOC entries. This
36515 is a normal message.
36516
36517 Action: No operator action is required.
36518
36519
36520 salvage_pv.pl1
36521 salvage_pv: no. of free recs changed from OLD to
36522 NEW dec.
36523
36524
36525 Stream: $salvout
36526
36527 Time: $salvt
36528
36529 Meaning: If the number of free records in the volume label
36530 is changed by a volume salvage this message is
36531 printed. If the volume was not properly shut
36532 down this message is to be expected.
36533
36534 Action: No operator action is required.
36535
36536
36537 salvage_pv.pl1
36538 salvage_pv: no. of free vtoces changed from OLD
36539 to NEW dec.
36540
36541
36542 Stream: $salvout
36543
36544 Time: $salvt
36545
36546 Meaning: If the number of free VTOC entries in the volume
36547 label is changed by a volume salvage this message
36548 is printed.
36549
36550 Action: No operator action is required.
36551
36552
36553
36554 salvage_pv 631 08/21/20 MR12.7^L
36555
36556
36557
36558
36559 salvage_pv.pl1
36560 salvage_pv: setting damaged switch on PRIMARYNAME
36561 VTOCXo on pv PVNAME.
36562
36563
36564 Stream: Logged in SYSERR log.
36565
36566 Time: $salvt
36567
36568 Meaning: The volume salvager has discovered possible damage
36569 to a segment and has turned on the damaged switch.
36570
36571 Action: No operator action is required. This message is
36572 logged in order to trigger automatic processing of
36573 damaged segments.
36574
36575
36576
36577 salvage_pv.pl1
36578 salvage_pv: Volume salvage finished with errors.
36579
36580
36581 Stream: $salvout
36582
36583 Time: $salvt
36584
36585 Meaning: Volume salvage finished with errors.
36586
36587 Action: Contact the system programming staff.
36588
36589
36590 salvage_pv.pl1
36591 salvage_pv: Volume salvage finished.
36592
36593
36594 Stream: $salvout
36595
36596 Time: $salvt
36597
36598 Meaning: Volume salvage finished.
36599
36600 Action: No operator action is required.
36601
36602
36603 salvage_pv.pl1
36604 salvage_pv: Volume salvage of dskX_NNs volume
36605 PVNAME of logical vol LVNAME.
36606
36607
36608 Stream: $salvout
36609
36610
36611
36612 salvage_pv 632 08/21/20 MR12.7^L
36613
36614
36615 Time: $salvt
36616
36617 Meaning: This message is printed when volume salvaging
36618 begins.
36619
36620 Action: No operator action is required.
36621
36622
36623 salvage_pv.pl1
36624 salvage_pv: VTOC conversion finished with errors.
36625
36626
36627 Stream: $salvout
36628
36629 Time: $salvt
36630
36631 Meaning: VTOC conversion finished with errors.
36632
36633 Action: Contact the system programming staff.
36634
36635
36636 salvage_pv.pl1
36637 salvage_pv: VTOC conversion finished.
36638
36639
36640 Stream: $salvout
36641
36642 Time: $salvt
36643
36644 Meaning: VTOC conversion finished.
36645
36646 Action: No operator action is required.
36647
36648
36649 salvage_pv.pl1
36650 salvage_pv: VTOC Conversion of dskX_NNs volume
36651 PVNAME of logical vol LVNAME.
36652
36653
36654 Stream: $salvout
36655
36656 Time: $salvt
36657
36658 Meaning: This message is printed when a pre-MR10 disk pack
36659 is first mounted on an MR10 or later system. The
36660 equivalent of a salvage is being done to create
36661 the VTOC Map which did not exist prior to MR10.
36662
36663 Action: No operator action is required.
36664
36665
36666 salvage_pv.pl1
36667
36668
36669
36670 salvage_pv 633 08/21/20 MR12.7^L
36671
36672
36673 salvage_pv: vtoce NAME at XXXo: cur len changed
36674 from OLD to NEW octal
36675
36676
36677 Stream: $salvout
36678
36679 Time: $salvt
36680
36681 Meaning: The segment originally named NAME at vtoc index
36682 XXXo had a current length which did not agree with
36683 the file map. The current length was corrected
36684 and the damaged switch set on the segment. This
36685 message usually indicates that a segment was
36686 damaged before a crash by failure to write out its
36687 pages to disk before the crash. The segment may
36688 have to be recovered.
36689
36690 Action: No operator action is required.
36691
36692
36693 salvage_pv.pl1
36694 salvage_pv: vtoce NAME at XXXo: max len changed
36695 from OLD to NEW octal.
36696
36697
36698 Stream: $salvout
36699
36700 Time: $salvt
36701
36702 Meaning: The segment originally named NAME at vtoc index
36703 XXXo had a maximum segment length which did not
36704 agree with the file map or was less than the
36705 current length. The maximum length was corrected
36706 and the damaged switch set.
36707
36708 Action: No operator action is required.
36709
36710
36711 salvage_pv.pl1
36712 salvage_pv: vtoce NAME at XXXo: page PPPo
36713 disk_addr DDDDo bad.
36714
36715
36716 Stream: $salvout
36717
36718 Time: $salvt
36719
36720 Meaning: The segment originally named NAME at vtoc index
36721 XXXo had an invalid disk address DDDDo for page
36722 PPPo. The address is nulled causing a page of
36723 zeroes and the damaged switch set.
36724
36725 Action: No operator action is required.
36726
36727
36728 salvage_pv 634 08/21/20 MR12.7^L
36729
36730
36731
36732
36733 salvage_pv.pl1
36734 salvage_pv: vtoce NAME at XXXo: rec used changed
36735 from OLD to NEW octal.
36736
36737
36738 Stream: $salvout
36739
36740 Time: $salvt
36741
36742 Meaning: The segment originally named NAME at vtoc index
36743 XXXo had a records used which did not agree with
36744 the file map. The records used field was
36745 corrected and the damaged switch set. This
36746 message usually indicates that a segment was
36747 damaged before a crash by failure to write out its
36748 pages to disk before the crash. The segment may
36749 have to be recovered.
36750
36751 Action: No operator action is required.
36752
36753
36754 salvage_pv.pl1
36755 salvage_pv: vtoce NAME at XXXo: ref to pageno
36756 PPo at addr DDDDo deleted dirsw is X.
36757
36758
36759 Stream: $salvout
36760
36761 Time: $salvt
36762
36763 Meaning: The segment originally named NAME at vtoc index
36764 XXXo had a reused address conflict with another
36765 segment. The page reference was determined to be
36766 incorrect and a null address placed in the
36767 segment's file map causing a page of zeroes and
36768 the damaged switch set. This message may be
36769 symptomatic of disk or other hardware problems.
36770
36771 Action: No operator action is required.
36772
36773
36774 salvage_pv.pl1
36775 salvage_pv: vtoce NAME at XXXo:
36776 time-record-product reset to zero.
36777
36778
36779 Stream: $salvout
36780
36781 Time: $salvt
36782
36783
36784
36785
36786 salvage_pv 635 08/21/20 MR12.7^L
36787
36788
36789 Meaning: The segment originally named NAME at vtoc index
36790 XXXo had an invalid value for one of the
36791 time-record-product fields. All
36792 time-record-product fields have been reset to
36793 zero.
36794
36795 Action: No operator action is required.
36796
36797
36798 salvage_pv.pl1
36799 salvage_pv: vtoce XXXo free but not zero.
36800
36801
36802 Stream: $salvout
36803
36804 Time: $salvt
36805
36806 Meaning: The VTOC entry with index XXXo was marked free but
36807 was not all zero. It was zeroed and made free.
36808
36809 Action: No operator action is required.
36810
36811
36812 salv_caller.pl1
36813 salvage_vol: -all and -copy arguments cannot be
36814 used together
36815
36816
36817 Stream: Initializer process output.
36818
36819 Time: In response to an operator command.
36820
36821 Meaning: Incorrect arguments were specified.
36822
36823 Action: Enter a corrected command line.
36824
36825
36826 salv_caller.pl1
36827 salvage_vol: ERROR_MESSAGE
36828
36829
36830 Stream: Initializer process output.
36831
36832 Time: In response to an operator command.
36833
36834 Meaning: Incorrect arguments were specified.
36835
36836 Action: Enter a corrected command line.
36837
36838
36839 salv_caller.pl1
36840 salvage_vol: ERROR_MESSAGE. need copy drive name
36841
36842
36843
36844 salvage_vol 636 08/21/20 MR12.7^L
36845
36846
36847 Stream: Initializer process output.
36848
36849 Time: In response to an operator command.
36850
36851 Meaning: Incorrect arguments were specified.
36852
36853 Action: Enter a corrected command line.
36854
36855
36856 salv_caller.pl1
36857 salvage_vol: Expected argument missing. first
36858 two args must be phys vol name and drive name
36859
36860
36861 Stream: Initializer process output.
36862
36863 Time: In response to an operator command.
36864
36865 Meaning: Incorrect arguments were specified.
36866
36867 Action: Enter a corrected command line.
36868
36869
36870 salv_caller.pl1
36871 salvage_vol: Inconsistent arguments have been
36872 specified
36873
36874
36875 Stream: Initializer process output.
36876
36877 Time: In response to an operator command.
36878
36879 Meaning: Incorrect arguments were specified.
36880
36881 Action: Enter a corrected command line.
36882
36883
36884 salv_caller.pl1
36885 salvage_vol: no drive may be specified for -all
36886
36887
36888 Stream: Initializer process output.
36889
36890 Time: In response to an operator command.
36891
36892 Meaning: Incorrect arguments were specified.
36893
36894 Action: Enter a corrected command line.
36895
36896
36897 salv_caller.pl1
36898 salvage_vol: Specified control argument is not
36899 implemented by this command. BLAH
36900
36901
36902 salvage_vol 637 08/21/20 MR12.7^L
36903
36904
36905 Stream: Initializer process output.
36906
36907 Time: In response to an operator command.
36908
36909 Meaning: Incorrect arguments were specified.
36910
36911 Action: Enter a corrected command line.
36912
36913
36914 bce_save.pl1
36915 savecheck_status: Special Interrupt:
36916 STATUS_WORD
36917
36918
36919 Stream: BOS Typewriter.
36920
36921 Time: System Intialization.
36922
36923 Meaning: An unexpected special interrupt has been detected.
36924
36925 Action: No operator action is required.
36926
36927
36928 bce_save.pl1
36929 savecheck_status: Time-Out on TAPE_DEV
36930
36931
36932 Stream: BOS Typewriter.
36933
36934 Time: System Intialization.
36935
36936 Meaning: An I/O that was issued to the tape device has
36937 timed-out.
36938
36939 Action: Follow normal recovery procedures.
36940
36941
36942 bce_save.pl1
36943 saveTAPE_SET: Unrecoverable MAJOR_STATUS
36944 SUB_STATUS on TAPE_DEV.
36945
36946
36947 Stream: BOS Typewriter.
36948
36949 Time: System Intialization.
36950
36951 Meaning: An unrecoverable error has occured while
36952 attempting to do I/O to the tape device.
36953
36954 Action: Follow normal recovery procedures.
36955
36956
36957 bce_save.pl1
36958
36959
36960 saveTAPE_SET 638 08/21/20 MR12.7^L
36961
36962
36963 saveTAPE_SET: Device TAPE_DEV is being removed
36964 from the tape device list.
36965
36966
36967 Stream: BOS Typewriter.
36968
36969 Time: System Intialization.
36970
36971 Meaning: The TAPE_DEV has returned a status indicating that
36972 it is unable to be used.
36973
36974 Action: No operator action is required.
36975
36976
36977 bce_save.pl1
36978 saveTAPE_SET: Error tape on TAPE_DEV is part
36979 of the "OTHER_TAPE_SET" set.
36980
36981
36982 Stream: BOS Typewriter.
36983
36984 Time: System Intialization.
36985
36986 Meaning: The tape just read is not part of this tape set.
36987
36988 Action: Mount a tape on the device that is part of this
36989 tape set.
36990
36991
36992 bce_save.pl1
36993 saveTAPE_SET: Incorrect tape sequence number
36994 detected.
36995 was REC_NUM s/b REC_NUM. Forcing restart of this
36996 tape set.
36997
36998
36999
37000 Stream: BOS Typewriter sounds beeper
37001
37002 Time: System Intialization.
37003
37004 Meaning: A sequence error was detected in the tape record
37005 number. This indicates a logic error in the
37006 supervisor or CPU or memory hardware problems.
37007
37008 Action: Follow normal save restart procedures. Contact
37009 the system programming staff.
37010
37011
37012
37013 bce_save.pl1
37014 saveTAPE_SET: MAJOR_STATUS SUB_STATUS on
37015 TAPE_DEV.
37016
37017
37018 saveTAPE_SET 639 08/21/20 MR12.7^L
37019
37020
37021 Stream: BOS Typewriter.
37022
37023 Time: System Intialization.
37024
37025 Meaning: An error has occured while attempting to do I/O to
37026 the tape device.
37027
37028 Action: Follow normal recovery procedures.
37029
37030
37031 bce_save_util_.pl1
37032 saveTAPE_SET: MULTICS_VOL_ID PV_NAME on
37033 DISK_DEV Last updated: DATE_TIME
37034
37035
37036
37037 Stream: BOS Typewriter.
37038
37039 Time: System Intialization.
37040
37041 Meaning: Just an informative message.
37042
37043 Action: No operator action is required.
37044
37045
37046 bce_save.pl1
37047 saveTAPE_SET: No Physical Volumes left to save.
37048
37049
37050 Stream: BOS Typewriter.
37051
37052 Time: System Intialization.
37053
37054 Meaning: For various reasons all of the physical volumes
37055 have been removed from the list of volumes.
37056
37057 Action: No operator action is required.
37058
37059
37060 bce_save.pl1
37061 saveTAPE_SET: No room to describe PV PV_NAME
37062 for part PARTITION_NAME.
37063
37064
37065 Stream: BOS Typewriter.
37066
37067 Time: System Intialization.
37068
37069 Meaning: The maximum number of physical volumes that can be
37070 handled by the program has been exceeded.
37071
37072 Action: The number of physical volumes defined in the
37073 control files must be reduced.
37074
37075
37076 saveTAPE_SET 640 08/21/20 MR12.7^L
37077
37078
37079
37080
37081 bce_save.pl1
37082 saveTAPE_SET: No usable tape devices left in
37083 list.
37084
37085
37086 Stream: BOS Typewriter.
37087
37088 Time: System Intialization.
37089
37090 Meaning: For various reasons all of the tape devices have
37091 been removed from the list of available devices
37092 for this tape set.
37093
37094 Action: Follow normal recovery procedures.
37095
37096
37097 bce_save.pl1
37098 saveTAPE_SET: No usable tape drives left.
37099
37100
37101 Stream: BOS Typewriter.
37102
37103 Time: System Intialization.
37104
37105 Meaning: For various reasons all of the tape devices have
37106 been removed from the list of available devices
37107 for this tape set.
37108
37109 Action: Follow normal recovery procedures.
37110
37111
37112 bce_save_util_.pl1
37113 saveTAPE_SET: Partition PARTITION_NAME is not
37114 defined on PV_NAME.
37115
37116
37117 Stream: BOS Typewriter.
37118
37119 Time: System Intialization.
37120
37121 Meaning: A request to save specific partition has been
37122 made but the partition does not exist of the PV.
37123
37124 Action: Correct the control files accordingly.
37125
37126
37127 bce_save_util_.pl1
37128 saveTAPE_SET: Partition PARTITION_NAME of
37129 volume PV_NAME is not defined in the restart tape
37130 label.
37131
37132
37133
37134 saveTAPE_SET 641 08/21/20 MR12.7^L
37135
37136
37137 Stream: BOS Typewriter.
37138
37139 Time: System Intialization.
37140
37141 Meaning: There is an inconsistency between the restart tape
37142 and the save control files.
37143
37144 Action: Either correct the control files or start the
37145 save over from the beginning.
37146
37147
37148
37149 bce_save.pl1
37150 saveTAPE_SET: Partition PARTITION_NAME on
37151 PV_NAME record REC_NUM on tape# TAPE_NUMBER
37152 TAPE_DEV
37153
37154
37155 Stream: BOS Typewriter.
37156
37157 Time: System Intialization.
37158
37159 Meaning: Just an informative message.
37160
37161 Action: No operator action is required.
37162
37163
37164 bce_save.pl1
37165 saveTAPE_SET: Partition PARTITION_NAME record
37166 REC_NUM on tape# TAPE_NUMBER TAPE_DEV
37167
37168
37169 Stream: BOS Typewriter.
37170
37171 Time: System Intialization.
37172
37173 Meaning: Just an informative message.
37174
37175 Action: No operator action is required.
37176
37177
37178 bce_save.pl1
37179 saveTAPE_SET: Please mount tape# TAPE_NUMBER on
37180 TAPE_DEV.
37181
37182
37183 Stream: BOS Typewriter sounds beeper
37184
37185 Time: System Intialization.
37186
37187 Meaning: Just an informative message.
37188
37189 Action: Mount tape on the device.
37190
37191
37192 saveTAPE_SET 642 08/21/20 MR12.7^L
37193
37194
37195
37196
37197 bce_save.pl1
37198 saveTAPE_SET: Please mount the "Info" tape on
37199 TAPE_DEV.
37200
37201
37202 Stream: BOS Typewriter sounds beeper
37203
37204 Time: System Intialization.
37205
37206 Meaning: Just an informative message.
37207
37208 Action: Mount the tape on the device.
37209
37210
37211 bce_save.pl1
37212 saveTAPE_SET: Please mount the "restart" tape
37213 on TAPE_DEV.
37214
37215
37216 Stream: BOS Typewriter sounds beeper
37217
37218 Time: System Intialization.
37219
37220 Meaning: Just an informative message.
37221
37222 Action: Mount the tape on the device.
37223
37224
37225 bce_save.pl1
37226 saveTAPE_SET: Remount tape# TAPE_NUMBER WITH
37227 write ring on TAPE_DEV.
37228
37229
37230 Stream: BOS Typewriter sounds beeper
37231
37232 Time: System Intialization.
37233
37234 Meaning: The tape is currently mounted without a write ring
37235 present.
37236
37237 Action: Remount tape with write permit ring in place.
37238
37239
37240 bce_save_util_.pl1
37241 saveTAPE_SET: Removing volume PV_NAME from PV
37242 list because all partitions were removed.
37243
37244
37245
37246 Stream: BOS Typewriter.
37247
37248
37249
37250 saveTAPE_SET 643 08/21/20 MR12.7^L
37251
37252
37253 Time: System Intialization.
37254
37255 Meaning: It is nolonger necessary for the program to keep
37256 track of the PV since all of the partition
37257 requests have been removed.
37258
37259 Action: Correct the control files accordingly.
37260
37261
37262 bce_save_util_.pl1
37263 saveTAPE_SET: Removing volume PV_NAME from PV
37264 list because there are no partitions to save.
37265
37266
37267
37268 Stream: BOS Typewriter.
37269
37270 Time: System Intialization.
37271
37272 Meaning: Only partition requests were made for this volume
37273 and now for various reasons there are none left to
37274 save.
37275
37276 Action: Follow normal recovery procedures.
37277
37278
37279 bce_save_util_.pl1
37280 saveTAPE_SET: Reverting "-all" partition
37281 request for volume PV_NAME because there are no
37282 partitions to save.
37283
37284
37285
37286 Stream: BOS Typewriter.
37287
37288 Time: System Intialization.
37289
37290 Meaning: This PV_NAME has no partitions defined.
37291
37292 Action: No operator action is required.
37293
37294
37295 bce_save.pl1
37296 saveTAPE_SET: save complete...
37297
37298
37299 Stream: BOS Typewriter.
37300
37301 Time: System Intialization.
37302
37303 Meaning: Just an informative message.
37304
37305 Action: No operator action is required.
37306
37307
37308 saveTAPE_SET 644 08/21/20 MR12.7^L
37309
37310
37311
37312
37313 bce_save.pl1
37314 saveTAPE_SET: Skipping volume PV_NAME on
37315 DISK_DEV save complete.
37316
37317
37318 Stream: BOS Typewriter.
37319
37320 Time: System Intialization.
37321
37322 Meaning: Just an informative message.
37323
37324 Action: No operator action is required.
37325
37326
37327 bce_save.pl1
37328 saveTAPE_SET: Starting from volume PV_NAME on
37329 DISK_DEV.
37330
37331
37332 Stream: BOS Typewriter.
37333
37334 Time: System Intialization.
37335
37336 Meaning: Just an informative message.
37337
37338 Action: No operator action is required.
37339
37340
37341 bce_save.pl1
37342 saveTAPE_SET: Tape on TAPE_DEV does not contain
37343 a supported tape label version.
37344
37345
37346 Stream: BOS Typewriter.
37347
37348 Time: System Intialization.
37349
37350 Meaning: The tape contains a tape version identifier that
37351 is nolonger supported.
37352
37353 Action: Use the "restore -display_info_tape tapX_NN"
37354 option to display the tape.
37355
37356
37357
37358 bce_save.pl1
37359 saveTAPE_SET: Tape on TAPE_DEV does not contain
37360 a valid label.
37361
37362
37363 Stream: BOS Typewriter.
37364
37365
37366 saveTAPE_SET 645 08/21/20 MR12.7^L
37367
37368
37369 Time: System Intialization.
37370
37371 Meaning: The tape just read is not a valid save/restore
37372 tape.
37373
37374 Action: Follow normal recovery procedures.
37375
37376
37377 bce_save.pl1
37378 saveTAPE_SET: Tape on TAPE_DEV is not part of
37379 this set.
37380
37381
37382 Stream: BOS Typewriter.
37383
37384 Time: System Intialization.
37385
37386 Meaning: The tape just read contains a different tape set
37387 name than what is currently being handled via the
37388 control file.
37389
37390 Action: Follow normal recovery procedures.
37391
37392
37393 bce_save_util_.pl1
37394 saveTAPE_SET: Tape subsystem "SUB_SYS" is not
37395 defined in the config.
37396
37397
37398 Stream: BOS Typewriter.
37399
37400 Time: System Intialization.
37401
37402 Meaning: No "prph" entry could be found for the tape
37403 subsystem.
37404
37405 Action: Correct config_deck or save/restore control
37406 files to indicate proper tape subsystem.
37407
37408
37409
37410 bce_save.pl1
37411 saveTAPE_SET: Tape# TAPE_NUMBER on TAPE_DEV
37412 created DATE_TIME
37413
37414
37415 Stream: BOS Typewriter.
37416
37417 Time: System Intialization.
37418
37419 Meaning: Just an informative message.
37420
37421 Action: No operator action is required.
37422
37423
37424 saveTAPE_SET 646 08/21/20 MR12.7^L
37425
37426
37427
37428
37429 bce_save_util_.pl1
37430 saveTAPE_SET: The "conf" partition of rpv is
37431 not being saved.
37432
37433
37434 Stream: BOS Typewriter.
37435
37436 Time: System Intialization.
37437
37438 Meaning: Just an informative message.
37439
37440 Action: Add the request to the save control file if
37441 desired.
37442
37443
37444 bce_save_util_.pl1
37445 saveTAPE_SET: The "file" partition of rpv is
37446 not being saved.
37447
37448
37449 Stream: BOS Typewriter.
37450
37451 Time: System Intialization.
37452
37453 Meaning: Just an informative message.
37454
37455 Action: Add the request to the save control file if
37456 desired.
37457
37458
37459 bce_save_util_.pl1
37460 saveTAPE_SET: The "log" partition of rpv is not
37461 being saved.
37462
37463
37464 Stream: BOS Typewriter.
37465
37466 Time: System Intialization.
37467
37468 Meaning: Just an informative message.
37469
37470 Action: Add the request to the save control file if
37471 desired.
37472
37473
37474 bce_save.pl1
37475 saveTAPE_SET: The following tape devices will
37476 be used:
37477
37478
37479 Stream: BOS Typewriter.
37480
37481
37482 saveTAPE_SET 647 08/21/20 MR12.7^L
37483
37484
37485 Time: System Intialization.
37486
37487 Meaning: Just an informative message.
37488
37489 Action: No operator action is required.
37490
37491
37492 bce_save.pl1
37493 saveTAPE_SET: This tape is older than one week.
37494 Tape rejected.
37495
37496
37497 Stream: BOS Typewriter.
37498
37499 Time: System Intialization.
37500
37501 Meaning: A restart of a save is being attempted but the
37502 tape used as the restart tape is older than one
37503 week.
37504
37505 Action: Restart with a later tape or start the save from
37506 the beginning.
37507
37508
37509 bce_save.pl1
37510 saveTAPE_SET: This tape starts with volume
37511 PV_NAME which was not defined. Tape rejected.
37512
37513
37514
37515 Stream: BOS Typewriter.
37516
37517 Time: System Intialization.
37518
37519 Meaning: A save restart is being attempted with a tape that
37520 begins with a PV that has not been defined in the
37521 save control files.
37522
37523 Action: Follow normal recovery procedures.
37524
37525
37526 bce_save.pl1
37527 saveTAPE_SET: Time-out waiting for special
37528 interrupt.
37529
37530
37531 Stream: BOS Typewriter.
37532
37533 Time: System Intialization.
37534
37535 Meaning: The program was waiting for a special to come from
37536 the device but none was recieved in the alloted
37537 time.
37538
37539
37540 saveTAPE_SET 648 08/21/20 MR12.7^L
37541
37542
37543 Action: Follow normal recovery procedures.
37544
37545
37546 bce_save_util_.pl1
37547 saveTAPE_SET: Type of data being saved for
37548 volume PV_NAME does not match the type in the
37549 restart tape label.
37550
37551
37552
37553 Stream: BOS Typewriter.
37554
37555 Time: System Intialization.
37556
37557 Meaning: There is an inconsistency between the restart tape
37558 and the save control files.
37559
37560 Action: Either correct the control files or start the
37561 save over from the beginning.
37562
37563
37564
37565 bce_save_util_.pl1
37566 saveTAPE_SET: Unable to save "PARTITION_NAME"
37567 partition. Internal partition list full.
37568
37569
37570
37571 Stream: BOS Typewriter.
37572
37573 Time: System Intialization.
37574
37575 Meaning: More partitions have been requested than the
37576 program can handle.
37577
37578 Action: Change control files to reduce the number defined
37579 possibly by breaking them up into seperate tape
37580 sets.
37581
37582
37583
37584 bce_save_util_.pl1
37585 saveTAPE_SET: Unable to save "PARTITION_NAME"
37586 partition. N partitions already defined
37587
37588
37589
37590 Stream: BOS Typewriter.
37591
37592 Time: System Intialization.
37593
37594 Meaning: An attempt has been made to save more than the N
37595 maximum partitions allowed.
37596
37597
37598 saveTAPE_SET 649 08/21/20 MR12.7^L
37599
37600
37601 Action: Change control filess to reduce the number
37602 requested.
37603
37604
37605 bce_save.pl1
37606 saveTAPE_SET: Unable to set density on
37607 TAPE_DEV.
37608
37609
37610 Stream: BOS Typewriter.
37611
37612 Time: System Intialization.
37613
37614 Meaning: The program was unable to set the required density
37615 of the tape device.
37616
37617 Action: Follow normal recovery procedures.
37618
37619
37620 bce_save.pl1
37621 saveTAPE_SET: Unloading "Info" tape from
37622 TAPE_DEV REC_CNT records ERR_CNT errors
37623
37624
37625 Stream: BOS Typewriter.
37626
37627 Time: System Intialization.
37628
37629 Meaning: Just an informative message.
37630
37631 Action: No operator action is required.
37632
37633
37634 bce_save.pl1
37635 saveTAPE_SET: Unloading tape# TAPE_NUMBER from
37636 TAPE_DEV REC_CNT records ERR_CNT errors
37637
37638
37639 Stream: BOS Typewriter.
37640
37641 Time: System Intialization.
37642
37643 Meaning: Just an informative message.
37644
37645 Action: No operator action is required.
37646
37647
37648 bce_save.pl1
37649 saveTAPE_SET: Unloading TAPE_DEV REC_CNT
37650 records ERR_CNT errors
37651
37652
37653 Stream: BOS Typewriter.
37654
37655
37656 saveTAPE_SET 650 08/21/20 MR12.7^L
37657
37658
37659 Time: System Intialization.
37660
37661 Meaning: Just an informative message.
37662
37663 Action: No operator action is required.
37664
37665
37666 bce_save_util_.pl1
37667 saveTAPE_SET: Volume on DISK_DEV is not a
37668 MULTICS_VOL_ID.
37669
37670
37671 Stream: BOS Typewriter.
37672
37673 Time: System Intialization.
37674
37675 Meaning: The volume to be saved is not a valid Multics
37676 volume and therefore cannot be saved.
37677
37678 Action: Follow normal recovery procedures.
37679
37680
37681 bce_save_util_.pl1
37682 saveTAPE_SET: Volume PV_NAME not found in
37683 restart tape label.
37684
37685
37686 Stream: BOS Typewriter.
37687
37688 Time: System Intialization.
37689
37690 Meaning: There is an inconsistency between the restart tape
37691 and the save control files.
37692
37693 Action: Either correct the control files or start the
37694 save over from the beginning.
37695
37696
37697
37698 bce_save_util_.pl1
37699 saveTAPE_SET: Volume PV_NAME requires
37700 salvaging. Setting -all to save all paging
37701 records on the volume.
37702
37703
37704
37705 Stream: BOS Typewriter.
37706
37707 Time: System Intialization.
37708
37709 Meaning: Just an informative message.
37710
37711 Action: No operator action is required.
37712
37713
37714 saveTAPE_SET 651 08/21/20 MR12.7^L
37715
37716
37717
37718
37719 bce_save_util_.pl1
37720 saveTAPE_SET: Volume PV_NAME's PVID does not
37721 match the one in the restart tape label.
37722
37723
37724
37725 Stream: BOS Typewriter.
37726
37727 Time: System Intialization.
37728
37729 Meaning: There is an inconsistency between what is on the
37730 restart tape and what is currently defined on the
37731 PV's disk label.
37732
37733 Action: Start the save over from the beginning.
37734
37735
37736 bce_save.pl1
37737 saveTAPE_SET: Volume PV_NAME record REC_NUM
37738 on tape# TAPE_NUMBER TAPE_DEV
37739
37740
37741 Stream: BOS Typewriter.
37742
37743 Time: System Intialization.
37744
37745 Meaning: Just an informative message.
37746
37747 Action: No operator action is required.
37748
37749
37750 bce_save_util_.pl1
37751 saveTAPE_SET: Volume was expected to be
37752 PV_NAME.
37753
37754
37755 Stream: BOS Typewriter.
37756
37757 Time: System Intialization.
37758
37759 Meaning: The PV name read from the disk label does not
37760 match the PV name that was defined in the save
37761 control files.
37762
37763 Action: Correct the control file to show the proper PV
37764 name mounted on the device.
37765
37766
37767
37768 bce_save.pl1
37769 saveTAPE_SET: Waiting for special on TAPE_DEV.
37770
37771
37772 saveTAPE_SET 652 08/21/20 MR12.7^L
37773
37774
37775 Stream: BOS Typewriter.
37776
37777 Time: System Intialization.
37778
37779 Meaning: Just an informative message.
37780
37781 Action: No operator action is required.
37782
37783
37784 bce_save_util_.pl1
37785 save: Attaching TAPE_DEV. ERR_MESSAGE
37786
37787
37788 Stream: BOS Typewriter sounds beeper
37789
37790 Time: System Intialization.
37791
37792 Meaning: IOI has returned a non-zero error code in response
37793 to a request to assign TAPE_DEV.
37794
37795 Action: Follow normal recovery procedures.
37796
37797
37798 bce_save.pl1
37799 save: bce_ioi_post_seg. ERR_MESSAGE
37800
37801
37802 Stream: BOS Typewriter sounds beeper
37803
37804 Time: System Intialization.
37805
37806 Meaning: The program was unable to get a pointer to the
37807 above segment. This indicates a logic error in
37808 the supervisor or CPU or memory hardware
37809 problems.
37810
37811 Action: Contact the system programming staff.
37812
37813
37814 bce_save.pl1
37815 save: bootload_disk_post_seg. ERR_MESSAGE
37816
37817
37818 Stream: BOS Typewriter sounds beeper
37819
37820 Time: System Intialization.
37821
37822 Meaning: The program was unable to get a pointer to the
37823 above segment. This indicates a logic error in
37824 the supervisor or CPU or memory hardware
37825 problems.
37826
37827 Action: Contact the system programming staff.
37828
37829
37830 save 653 08/21/20 MR12.7^L
37831
37832
37833
37834
37835 bce_save_util_.pl1
37836 save: Could not read label of PV_NAME on
37837 DISK_DEV. ERR_MESSAGE
37838
37839
37840 Stream: BOS Typewriter sounds beeper
37841
37842 Time: System Intialization.
37843
37844 Meaning: The volume label of the PV could not be read due
37845 to the error given in ERR_MESSAGE.
37846
37847 Action: A operator query is done to find out if the read
37848 should be retried or the PV removed from the list.
37849
37850
37851
37852 bce_save.pl1
37853 save: Getting tape label temp segment.
37854 ERR_MESSAGE
37855
37856
37857 Stream: BOS Typewriter sounds beeper
37858
37859 Time: System Intialization.
37860
37861 Meaning: An error occured while attempting to get a
37862 temporary segment to hold the tape label
37863 information.
37864
37865 Action: Contact the system programming staff.
37866
37867
37868 bce_save_util_.pl1
37869 save: Initiating CONTROL_FILE_NAME for
37870 set-TAPE_SET_IDX ERR_MESSAGE
37871
37872
37873 Stream: BOS Typewriter sounds beeper
37874
37875 Time: System Intialization.
37876
37877 Meaning: An error was detected while initiating the save
37878 control file.
37879
37880 Action: Contact the system programming staff. $recover
37881
37882
37883 bce_save.pl1
37884 save: PV_NAME ERR_MESSAGE
37885
37886
37887
37888 save 654 08/21/20 MR12.7^L
37889
37890
37891 Stream: BOS Typewriter sounds beeper
37892
37893 Time: System Intialization.
37894
37895 Meaning: The call to bootload_disk_io$test_done has
37896 returned a non-zero error code.
37897
37898 Action: Contact the system programming staff. $recover
37899
37900
37901 bce_save.pl1
37902 save: pvt. ERR_MESSAGE
37903
37904
37905 Stream: BOS Typewriter sounds beeper
37906
37907 Time: System Intialization.
37908
37909 Meaning: The program was unable to get a pointer to the
37910 above segment. This indicates a logic error in
37911 the supervisor or CPU or memory hardware
37912 problems.
37913
37914 Action: Contact the system programming staff.
37915
37916
37917 bce_save.pl1
37918 save: Restarting save of set "TAPE_SET" on
37919 TAPE_DEV.
37920
37921
37922 Stream: BOS Typewriter.
37923
37924 Time: System Intialization.
37925
37926 Meaning: Just an informative message.
37927
37928 Action: No operator action is required.
37929
37930
37931 bce_save_util_.pl1
37932 save: Setting max workspace for TAPE_DEV.
37933 ERR_MESSAGE
37934
37935
37936 Stream: BOS Typewriter sounds beeper
37937
37938 Time: System Intialization.
37939
37940 Meaning: IOI has returned a non-zero error code in response
37941 to a request to set the max workspace size for
37942 TAPE_DEV.
37943
37944
37945
37946 save 655 08/21/20 MR12.7^L
37947
37948
37949 Action: Contact the system programming staff.
37950
37951
37952 bce_save.pl1
37953 save: Setting status index for TAPE_DEV.
37954 ERR_MESSAGE
37955
37956
37957 Stream: BOS Typewriter sounds beeper
37958
37959 Time: System Intialization.
37960
37961 Meaning: IOI has returned a non-zero error which has been
37962 expanded in ERR_MESSAGE.
37963
37964 Action: Contact the system programming staff.
37965
37966
37967 bce_save_util_.pl1
37968 save: Setting up workspace for TAPE_DEV.
37969 ERR_MESSAGE
37970
37971
37972 Stream: BOS Typewriter sounds beeper
37973
37974 Time: System Intialization.
37975
37976 Meaning: IOI has returned a non-zero error code from the
37977 request to create a workspace for TAPE_DEV.
37978
37979 Action: Contact the system programming staff.
37980
37981
37982 bce_save_util_.pl1
37983 save: si ERR_MESSAGE
37984
37985
37986 Stream: BOS Typewriter sounds beeper
37987
37988 Time: System Intialization.
37989
37990 Meaning: An error has been found with the internal "si"
37991 structure.This indicates a logic error in the
37992 supervisor or CPU or memory hardware problems.
37993
37994 Action: Contact the system programming staff.
37995
37996
37997 bce_save_util_.pl1
37998 save: sri ERR_MESSAGE
37999
38000
38001 Stream: BOS Typewriter sounds beeper
38002
38003
38004 save 656 08/21/20 MR12.7^L
38005
38006
38007 Time: System Intialization.
38008
38009 Meaning: An error has been found with the internal "sri"
38010 structure.This indicates a logic error in the
38011 supervisor or CPU or memory hardware problems.
38012
38013 Action: Contact the system programming staff.
38014
38015
38016 bce_save.pl1
38017 save: Stopping save of set "TAPE_SET".
38018
38019
38020 Stream: BOS Typewriter.
38021
38022 Time: System Intialization.
38023
38024 Meaning: Just an informative message.
38025
38026 Action: No operator action is required.
38027
38028
38029 bce_save_util_.pl1
38030 save: TAPE_DEV ERR_MESSAGE
38031
38032
38033 Stream: BOS Typewriter sounds beeper
38034
38035 Time: System Intialization.
38036
38037 Meaning: An error occured while scanning the tape subsystem
38038 survey data.
38039
38040 Action: Follow normal recovery procedures.
38041
38042
38043 bce_save.pl1
38044 save: tape_error_data. ERR_MESSAGE
38045
38046
38047 Stream: BOS Typewriter sounds beeper
38048
38049 Time: System Intialization.
38050
38051 Meaning: The program was unable to get a pointer to the
38052 above segment. This indicates a logic error in
38053 the supervisor or CPU or memory hardware
38054 problems.
38055
38056 Action: Contact the system programming staff.
38057
38058
38059
38060
38061
38062 save 657 08/21/20 MR12.7^L
38063
38064
38065
38066
38067 bce_save.pl1
38068 save: Unassigning TAPE_DEV. ERR_MESSAGE
38069
38070
38071 Stream: BOS Typewriter sounds beeper
38072
38073 Time: System Intialization.
38074
38075 Meaning: IOI has returned a non-zero error which has been
38076 expanded in ERR_MESSAGE.
38077
38078 Action: Contact the system programming staff.
38079
38080
38081 sc_admin_command_.pl1
38082 sc_admin_command_: Denied send_admin_command for
38083 USER in ring RING.
38084
38085
38086 Stream: $sc
38087
38088 Time: While system is running.
38089
38090 Meaning: User USER requested the system to execute an admin
38091 command but lacked access to
38092 >sc1>admin_acs>admin_command.acs.
38093
38094 Action: No operator action is required.
38095
38096
38097 sc_admin_command_.pl1
38098 sc_admin_command_: Failed to check access for
38099 USER.
38100
38101
38102 Stream: $sc
38103
38104 Time: While system is running.
38105
38106 Meaning: User USER requested the system to execute an admin
38107 command but the system cound not determine their
38108 access to the admin_command acs.
38109
38110 Action: No operator action is required.
38111
38112
38113 sc_admin_command_.pl1
38114 sc_admin_command_: PERSON: COMMANDLINE
38115
38116
38117 Stream: $sc
38118
38119
38120 sc_admin_command_ 658 08/21/20 MR12.7^L
38121
38122
38123 Time: While system is running.
38124
38125 Meaning: A system administrator has sent a special command
38126 to the Initializer which executes it in admin
38127 mode.
38128
38129 Action: No operator action is required.
38130
38131
38132 sc_init_.pl1
38133 sc_init_: ERROR_MESSAGE. Error from iox_$attach
38134 master_i/o ATD
38135
38136
38137 Stream: BOS Typewriter Crashes system
38138
38139 Time: System Intialization.
38140
38141 Meaning: Some error was detected while attaching the
38142 master_i/o switch. ATD is the text of the attach
38143 description. This error is usually caused by a
38144 hardware failure in the operator's console.
38145 Correct the failure and reboot the system.
38146
38147 Action: Contact the system programming staff.
38148
38149
38150 sc_init_.pl1
38151 sc_init_: ERROR_MESSAGE. Error from iox_$attach
38152 user_i/o syn_ master_i/o
38153
38154
38155 Stream: BOS Typewriter Crashes system
38156
38157 Time: System Intialization.
38158
38159 Meaning: Some error was detected while attaching user_i/o
38160 as a synonym for the master_i/o switch in the
38161 Initializer process. This is usually caused by a
38162 hardware failure in the operator's console.
38163 Correct the failure and reboot the system.
38164
38165 Action: Contact the system programming staff.
38166
38167
38168 sc_init_.pl1
38169 sc_init_: ERROR_MESSAGE. Error from iox_$open
38170 master_i/o stream_input_output
38171
38172
38173 Stream: BOS Typewriter Crashes system
38174
38175 Time: System Intialization.
38176
38177
38178 sc_init_ 659 08/21/20 MR12.7^L
38179
38180
38181 Meaning: Some error was detected while opening the
38182 master_i/o switch. This is usually caused by a
38183 hardware failure in the operator's console.
38184 Correct the failure and reboot the system.
38185
38186 Action: Contact the system programming staff.
38187
38188
38189 sc_init_.pl1
38190 sc_init_: ERROR_MESSAGE. Failed to open
38191 admin_log log.
38192
38193
38194 Stream: BOS Typewriter sounds beeper
38195
38196 Time: System Intialization.
38197
38198 Meaning: The system failed to iox open the switch for the
38199 log >sc1>as_logs>admin_log. The segment
38200 >sc1>as_logs>admin_log may be damaged. The system
38201 enters a primitive Multics listener on the
38202 bootload console.
38203
38204 Action: Repair the problem. You may need to rename or
38205 delete the segment >sc1>as_logs>admin_log. Then
38206 shutdown and reboot.
38207
38208
38209
38210 sc_init_.pl1
38211 sc_init_: Invoking emergency listener because
38212 "nosc" parameter specified.
38213
38214
38215 Stream: BOS Typewriter.
38216
38217 Time: System Intialization.
38218
38219 Meaning: The parm config card specified nosc no system
38220 control. This parameter requests that an
38221 emergency listener be entered to allow repair of
38222 >sc1 or other parts of the system hierarchy at the
38223 earliest possible point during system
38224 initialization. Once the repairs are made
38225 shutdown the system by typing: "hphcs_$shutdown"
38226 and then reboot the system.
38227
38228 Action: Repair the problem shutdown the system then
38229 reboot.
38230
38231
38232 sc_init_.pl1
38233
38234
38235
38236 sc_init_ 660 08/21/20 MR12.7^L
38237
38238
38239 sc_init_: Messages from log salvage of
38240 LOG_PATHNAME:
38241
38242
38243 Stream: BOS Typewriter.
38244
38245 Time: System Intialization.
38246
38247 Meaning: Some error was detected in opening the admin or
38248 answering service log specified by LOG_PATHNAME.
38249 A salvage was invoked to attempt correction of the
38250 problem. One or more messages will succeed this
38251 message which describe inconsistancies found in
38252 the log repairs which were made or conditions
38253 which prevent automatic repair. These will be of
38254 the form "sc_init_: log_salvage_ MESSAGE".
38255
38256 Action: Contact the system programming staff.
38257
38258
38259 sc_init_.pl1
38260 sc_init_: Cound not initiate the PIT for the
38261 Initializer.
38262
38263
38264 Stream: BOS Typewriter Crashes system
38265
38266 Time: System Intialization.
38267
38268 Meaning: The Initializer has failed to initiate the segment
38269 "pit" in its process directory. This could
38270 indicate problems with the bootload tape the
38271 online libraries or the hardware.
38272
38273 Action: Contact the system programming staff.
38274
38275
38276 sc_init_.pl1
38277 sc_init_: Created >system_control_dir>as_logs
38278
38279
38280 Stream: BOS Typewriter sounds beeper
38281
38282 Time: System Intialization.
38283
38284 Meaning: The system has successfully created a new
38285 directory >sc1>as_logs.
38286
38287 Action: No operator action is required. If this is not
38288 the first bootload of the system under MR11 or
38289 later you may need to retrieve log segments lost
38290 in a crash into the new directory.
38291
38292
38293
38294 sc_init_ 661 08/21/20 MR12.7^L
38295
38296
38297
38298
38299 sc_init_.pl1
38300 sc_init_: ERROR_MESSAGE.
38301 >system_control_dir>as_logs does not exist or is
38302 not a directory.
38303
38304
38305 Stream: BOS Typewriter sounds beeper
38306
38307 Time: System Intialization.
38308
38309 Meaning: The directory >sc1>as_logs must exist for the ring
38310 4 environment to be set up.
38311
38312 Action: The system continues operation trying to repair
38313 the situation. Subsequent messages indicate the
38314 success or failure of repairs.
38315
38316
38317
38318 sc_init_.pl1
38319 sc_init_: ERROR_MESSAGE. Could not set working
38320 directory to PATH.
38321
38322
38323 Stream: BOS Typewriter sounds beeper
38324
38325 Time: System Intialization.
38326
38327 Meaning: Either some program is in error or the directory
38328 PATH does not exist.
38329
38330 Action: Contact the system programming staff. Correct the
38331 problem shut down and reboot.
38332
38333
38334
38335 sc_init_.pl1
38336 sc_init_: ERROR_MESSAGE. Error from
38337 initiate_search_rules.
38338
38339
38340 Stream: BOS Typewriter sounds beeper
38341
38342 Time: System Intialization.
38343
38344 Meaning: The Initializer is attempting to set its search
38345 rules and has encountered an error. This message
38346 may occur if an error has been introduced into the
38347 system tape or it may indicate that one of the
38348 directories searched by the Initializer has been
38349 destroyed.
38350
38351
38352 sc_init_ 662 08/21/20 MR12.7^L
38353
38354
38355 Action: Contact the system programming staff.
38356
38357
38358 sc_init_.pl1
38359 sc_init_: ERROR_MESSAGE. Failed to attach
38360 admin_log log.
38361
38362
38363 Stream: BOS Typewriter sounds beeper
38364
38365 Time: System Intialization.
38366
38367 Meaning: The system failed to attach a switch to write
38368 information to the admin log
38369 >sc1>as_logs>admin_log. The segment
38370 >sc1>as_logs>admin_log may be damaged. The system
38371 enters a primitive Multics listener on the
38372 bootload console.
38373
38374 Action: Repair the problem. You may have to delete or
38375 rename the segment >sc1>as_logs>admin_log. Then
38376 shutdown and reboot.
38377
38378
38379
38380 sc_init_.pl1
38381 sc_init_: ERROR_MESSAGE. Failed to get
38382 log_write_ ptr for admin_log.
38383
38384
38385 Stream: BOS Typewriter sounds beeper
38386
38387 Time: System Intialization.
38388
38389 Meaning: This indicated an internal programming error. The
38390 online libraries may be damaged.
38391
38392 Action: Contact the system programming staff.
38393
38394
38395 sc_init_.pl1
38396 sc_init_: ERROR_MESSAGE. Failed to open the AS
38397 log >system_control_dir>as_logs>log.
38398
38399
38400 Stream: BOS Typewriter sounds beeper
38401
38402 Time: System Intialization.
38403
38404 Meaning: The system was unable to open the log
38405 >sc1>as_logs>log. This may indicate damage to the
38406 segment >sc1>as_logs>log. The system enters a
38407
38408
38409
38410 sc_init_ 663 08/21/20 MR12.7^L
38411
38412
38413 primitive Multics listener on the bootload
38414 console.
38415
38416 Action: Repair the problem. You may have to rename or
38417 delete >sc1>as_logs>log. Then shutdown and
38418 reboot.
38419
38420
38421
38422 sc_init_.pl1
38423 sc_init_: Failed to attach one of the severityN
38424 1 2 3 switches.
38425
38426
38427 Stream: BOS Typewriter.
38428
38429 Time: System Intialization.
38430
38431 Meaning: The Initializer failed to make a syn_ for one of
38432 the three switches severity1 severity2 or
38433 severity3. There may be a problem with the system
38434 tape the libraries or the hardware.
38435
38436 Action: The system attempts to enter a primitive listener
38437 environment on the bootload console. You should
38438 diagnose and/or correct the problem and then
38439 reboot the system.
38440
38441
38442 Message: sc_init_: A serious error was
38443 encountered setting up the system control
38444 environment. The system will attempt to establish
38445 a Multics listener level. You should repair the
38446 problem and then type: "hphcs_$shutdown" and
38447 reboot the system.
38448
38449 Stream: BOS Typewriter.
38450
38451 Time: System Intialization.
38452
38453 Action: Contact the system programming staff.
38454
38455
38456 sc_init_.pl1
38457 sc_init_: Failed to create ssu invocation for
38458 system control.
38459
38460
38461 Stream: BOS Typewriter sounds beeper
38462
38463 Time: System Intialization.
38464
38465
38466
38467
38468 sc_init_ 664 08/21/20 MR12.7^L
38469
38470
38471 Meaning: The system failed to set up the subsystem data
38472 structure for the bootload console. This
38473 indicates a programming error or trouble with the
38474 system libraries.
38475
38476 Action: Contact the system programming staff.
38477
38478
38479 sc_init_.pl1
38480 sc_init_: Renamed non-directory object
38481 >system_control_dir>as_logs.
38482
38483
38484 Stream: BOS Typewriter sounds beeper
38485
38486 Time: System Intialization.
38487
38488 Meaning: The system found something that was not a
38489 directory in the place of the directory
38490 >sc1>as_logs and renamed it to permit a new
38491 directory to be created.
38492
38493 Action: No operator action is required.
38494
38495
38496 sc_process_command_line_.pl1
38497 sc_process_command_line_: Error while reattaching
38498 critical I/O switches.
38499
38500
38501 Stream: $sc
38502
38503 Time: In response to an operator command.
38504
38505 Meaning: $crashesThis indicates a logic error in the
38506 supervisor or CPU or memory hardware problems.
38507
38508 Action: Contact the system programming staff.
38509
38510
38511 sc_process_command_line_.pl1
38512 sc_process_command_line_: ERROR_MESSAGE. Could
38513 not attach switch NAME @ LOC using attach
38514 description DESCRIP.
38515
38516
38517
38518 Stream: $sc
38519
38520 Time: In response to an operator command.
38521
38522 Meaning: $crashesThis indicates a logic error in the
38523 supervisor or CPU or memory hardware problems.
38524
38525
38526 sc_process_command_line_ 665 08/21/20 MR12.7^L
38527
38528
38529 ERROR_MESSAGE is the expansion of the system
38530 status code describing the attach error. LOC
38531 gives the location of the I/O Control Block
38532 IOCB.
38533
38534 Action: Contact the system programming staff.
38535
38536
38537 sc_process_command_line_.pl1
38538 sc_process_command_line_: ERROR_MESSAGE. Could
38539 not open switch NAME for stream_input_output.
38540
38541
38542
38543 Stream: $sc
38544
38545 Time: In response to an operator command.
38546
38547 Meaning: $crashesThis indicates a logic error in the
38548 supervisor or CPU or memory hardware problems.
38549 ERROR_MESSAGE is the expansion of the system
38550 status code describing the open error.
38551
38552 Action: Contact the system programming staff.
38553
38554
38555 sc_process_command_line_.pl1
38556 sc_process_command_line_: ERROR_MESSAGE. Could
38557 not restore attachment to switch NAME.
38558
38559
38560
38561 Stream: $sc
38562
38563 Time: In response to an operator command.
38564
38565 Meaning: $crashesThis indicates a logic error in the
38566 supervisor or CPU or memory hardware problems.
38567 ERROR_MESSAGE is the expansion of the system
38568 status code describing the move_attach error.
38569
38570 Action: Contact the system programming staff.
38571
38572
38573 sc_process_command_line_.pl1
38574 sc_process_command_line_: ERROR_MESSAGE. Failed
38575 to find save iocb NAME.
38576
38577
38578 Stream: $sc
38579
38580 Time: In response to an operator command.
38581
38582
38583
38584 sc_process_command_line_ 666 08/21/20 MR12.7^L
38585
38586
38587 Meaning: $crashesThis indicates a logic error in the
38588 supervisor or CPU or memory hardware problems.
38589 ERROR_MESSAGE is the expansion of the system
38590 status code describing the actual error.
38591
38592 Action: Contact the system programming staff.
38593
38594
38595 sc_process_command_line_.pl1
38596 sc_process_command_line_: ERROR_MESSAGE. Failed
38597 to move_attach iocb NAME.
38598
38599
38600 Stream: $sc
38601
38602 Time: In response to an operator command.
38603
38604 Meaning: $crashesThis indicates a logic error in the
38605 supervisor or CPU or memory hardware problems.
38606 ERROR_MESSAGE is the expansion of the system
38607 status code describing the actual error.
38608
38609 Action: Contact the system programming staff.
38610
38611
38612 sc_process_command_line_.pl1
38613 sc_process_command_line_: Terminal SOURCE_NAME
38614 hung up during execution of command.
38615
38616
38617
38618 Stream: as severity 2
38619
38620 Time: In response to an operator command.
38621
38622 Meaning: Reports that execution of an Initializer command
38623 was interrupted when the message coordinator
38624 terminal identified by SOURCE_NAME hung.
38625
38626 Action: No operator action is required.
38627
38628
38629 sc_requests_.pl1
38630 sc_requests_ set_time_zone: Changed time zone
38631 from OLD_ZONE to NEW_ZONE.
38632
38633
38634 Stream: $sc
38635
38636 Time: While system is running.
38637
38638 Meaning: This messages records that the set_time_zone
38639 operator request was given and that the system
38640
38641
38642 sc_requests_ set_time_zone 667 08/21/20 MR12.7^L
38643
38644
38645 default time zone was thereby changed from
38646 OLD_ZONE to NEW_ZONE.
38647
38648 Action: No operator action is required.
38649
38650
38651 sc_signal_handler_.pl1
38652 sc_signal_handler_: error: CONDITION_NAME
38653
38654
38655 Stream: as severity2
38656
38657 Time: While system is running.
38658
38659 Meaning: A CONDITION_NAME condition occurred while running
38660 an operator command. An answering service dump
38661 has been taken to further describe the cause of
38662 the condition.
38663
38664 Action: Contact the system programming staff._sa
38665
38666
38667 scas_init.pl1
38668 scas_init: Bootload CPU has no system controller
38669 mask assigned.
38670
38671
38672 Stream: BOS Typewriter Crashes system
38673
38674 Time: System Intialization.
38675
38676 Meaning: No memory assigns a mask register to the bootload
38677 CPU.
38678
38679 Action: Correct the configuration and reboot.
38680
38681
38682 scas_init.pl1
38683 scas_init: Bootload CPU may not be on an expander
38684 port.
38685
38686
38687 Stream: BOS Typewriter Crashes system
38688
38689 Time: System Intialization.
38690
38691 Meaning: The CPU config card for the bootload CPU indicates
38692 that the bootload CPU is on an expanded port.
38693 This is not permitted.
38694
38695 Action: Correct the configuration or the configuration
38696 deck and reboot.
38697
38698
38699
38700 scas_init 668 08/21/20 MR12.7^L
38701
38702
38703
38704
38705 scas_init.pl1
38706 scas_init: Config card for bootload CPU indicates
38707 unit is offline.
38708
38709
38710 Stream: BOS Typewriter Crashes system
38711
38712 Time: System Intialization.
38713
38714 Meaning: The configuration deck is incorrect.
38715
38716 Action: Correct the configuration or the configuration
38717 deck and reboot.
38718
38719
38720 scas_init.pl1
38721 scas_init: Config card for bootload MEM indicates
38722 unit is offline.
38723
38724
38725 Stream: BOS Typewriter Crashes system
38726
38727 Time: System Intialization.
38728
38729 Meaning: The configuration deck is incorrect.
38730
38731 Action: Correct the the configuration deck and reboot.
38732
38733
38734 scas_init.pl1
38735 scas_init: Config card for CPU X is neither on
38736 nor off.
38737
38738
38739 Stream: BOS Typewriter Crashes system
38740
38741 Time: System Intialization.
38742
38743 Meaning: The configuration deck is incorrect.
38744
38745 Action: Correct the the configuration deck and reboot.
38746
38747
38748 scas_init.pl1
38749 scas_init: Config card for MEM Y is neither on
38750 nor off.
38751
38752
38753 Stream: BOS Typewriter Crashes system
38754
38755 Time: System Intialization.
38756
38757
38758 scas_init 669 08/21/20 MR12.7^L
38759
38760
38761 Meaning: The configuration deck is incorrect.
38762
38763 Action: Correct the the configuration deck and reboot.
38764
38765
38766 scas_init.pl1
38767 scas_init: CPU config card specifies wrong
38768 controller port number.
38769
38770
38771 Stream: BOS Typewriter Crashes system
38772
38773 Time: System Intialization.
38774
38775 Meaning: The configuration deck is incorrect.
38776
38777 Action: Correct the configuration or the configuration
38778 deck and reboot.
38779
38780
38781 scas_init.pl1
38782 scas_init: CPU data switches are XXXXXXXXXXXX
38783 should be YYYYYYYYYYYY
38784
38785
38786 Stream: BOS Typewriter.
38787
38788 Time: System Intialization.
38789
38790 Meaning: The CPU data switches are not set properly. The
38791 proper values are displayed.
38792
38793 Action: The incorrect value will prevent returning to bce
38794 on that CPU by means of EXECUTE SWITCHES. Certain
38795 incorrect values will activate software debugging
38796 traps. The switches should be corrected. This
38797 can be done while the CPU is running.
38798
38799
38800
38801 scas_init.pl1
38802 scas_init: CPU X and CPU Y both configured for
38803 port P subport S
38804
38805
38806 Stream: BOS Typewriter Crashes system
38807
38808 Time: System Intialization.
38809
38810 Meaning: The CPU CONFIG cards for CPU's X and Y both
38811 indicate that they are connected to subport S of
38812 expanded SCU port P. This is clearly impossible.
38813
38814
38815
38816 scas_init 670 08/21/20 MR12.7^L
38817
38818
38819 Action: Correct the configuration deck and reboot.
38820
38821
38822 scas_init.pl1
38823 scas_init: CPU X appears twice in config deck.
38824
38825
38826 Stream: BOS Typewriter Crashes system
38827
38828 Time: System Intialization.
38829
38830 Meaning: The configuration deck is incorrect.
38831
38832 Action: Correct the the configuration deck and reboot.
38833
38834
38835 scas_init.pl1
38836 scas_init: Illegal expander subport tag on CPU X
38837 config card.
38838
38839
38840 Stream: BOS Typewriter Crashes system
38841
38842 Time: System Intialization.
38843
38844 Meaning: A CPU config card for CPU X specifies an illegal
38845 value for a port-expander subport. The only legal
38846 values for expander subports are A B C and D.
38847
38848 Action: Correct the config deck and reboot.
38849
38850
38851 scas_init.pl1
38852 scas_init: Illegal tag on CPU config card.
38853
38854
38855 Stream: BOS Typewriter Crashes system
38856
38857 Time: System Intialization.
38858
38859 Meaning: One or more CPU cards is incorrect. Tag must be
38860 one of A B C D E F G H.
38861
38862 Action: Correct the configuration or the configuration
38863 deck and reboot.
38864
38865
38866 scas_init.pl1
38867 scas_init: Illegal tag on MEM config card.
38868
38869
38870 Stream: BOS Typewriter Crashes system
38871
38872
38873
38874 scas_init 671 08/21/20 MR12.7^L
38875
38876
38877 Time: System Intialization.
38878
38879 Meaning: The configuration deck is incorrect. Tag must be
38880 one of A B C D E F G H.
38881
38882 Action: Correct the the configuration deck and reboot.
38883
38884
38885 scas_init.pl1
38886 scas_init: MEM X is an old SCU with port expander
38887
38888
38889 Stream: BOS Typewriter Crashes system
38890
38891 Time: System Intialization.
38892
38893 Meaning: System controller X is an old-style SCU but
38894 configuration cards indicate that it has at least
38895 one expanded port because there is a CPU on an
38896 expanded port in the system. Old-style system
38897 controllers may not have expanded ports.
38898
38899 Action: The configuration deck is in error. Fix it and
38900 reboot.
38901
38902
38903 scas_init.pl1
38904 scas_init: MEM X is not enabled.
38905
38906
38907 Stream: BOS Typewriter Crashes system
38908
38909 Time: System Intialization.
38910
38911 Meaning: The bootload CPU does not have MEM X enabled.
38912
38913 Action: Correct the configuration or the configuration
38914 deck and reboot.
38915
38916
38917 scas_init.pl1
38918 scas_init: MEM Y address assignment disagrees
38919 with config deck.
38920
38921
38922 Stream: BOS Typewriter Crashes system
38923
38924 Time: System Intialization.
38925
38926 Meaning: The address assignment of memory Y as read from
38927 the address assignment switches on the maintenance
38928 panel of the bootload CPU disagrees with the
38929 address assignment of this memory as indicated by
38930
38931
38932 scas_init 672 08/21/20 MR12.7^L
38933
38934
38935 the relative position of its MEM card in the
38936 configuration deck.
38937
38938 Action: If the configuration deck is wrong correct it and
38939 reboot. If the configuration deck is correct
38940 check all address assignment switches on
38941 processors IOMs and the Bulk Store Controller
38942 correct them reboot bce and reboot.
38943
38944
38945
38946 scas_init.pl1
38947 scas_init: MEM Y appears twice in config deck.
38948
38949
38950 Stream: BOS Typewriter Crashes system
38951
38952 Time: System Intialization.
38953
38954 Meaning: The configuration deck is incorrect.
38955
38956 Action: Correct the the configuration deck and reboot.
38957
38958
38959 scas_init.pl1
38960 scas_init: MEM Y has duplicate mask assignments
38961 to CPU X.
38962
38963
38964 Stream: BOS Typewriter Crashes system
38965
38966 Time: System Intialization.
38967
38968 Meaning: The EXECUTE INTERRUPT MASK ASSIGNMENT or MASK/PORT
38969 ASSIGNMENT on memory Y is incorrect.
38970
38971 Action: Correct the configuration and reboot.
38972
38973
38974 scas_init.pl1
38975 scas_init: MEM Y has mask Z assigned to
38976 non-processor port.
38977
38978
38979 Stream: BOS Typewriter Crashes system
38980
38981 Time: System Intialization.
38982
38983 Meaning: The EXECUTE INTERRUPT MASK ASSIGNMENT or MASK/PORT
38984 ASSIGNMENT on memory Y is incorrect.
38985
38986 Action: Correct the configuration and reboot.
38987
38988
38989
38990 scas_init 673 08/21/20 MR12.7^L
38991
38992
38993
38994
38995 scas_init.pl1
38996 scas_init: MEM Y has more memory than indicated
38997 by CPU switches.
38998
38999
39000 Stream: BOS Typewriter Crashes system
39001
39002 Time: System Intialization.
39003
39004 Meaning: The PORT SIZE plug on the free edge of the PQ
39005 board of the bootload CPU does not agree with the
39006 STORE SIZE switch on MEM Y.
39007
39008 Action: Correct the configuration and reboot.
39009
39010
39011 scas_init.pl1
39012 scas_init: MEM Y has no mask assigned to CPU X.
39013
39014
39015 Stream: BOS Typewriter Crashes system
39016
39017 Time: System Intialization.
39018
39019 Meaning: The EXECUTE INTERRUPT MASK ASSIGNMENT or MASK/PORT
39020 ASSIGNMENT on memory Y is incorrect.
39021
39022 Action: Correct the configuration and reboot.
39023
39024
39025 scas_init.pl1
39026 scas_init: MEM Y is not in PROGRAM mode.
39027
39028
39029 Stream: BOS Typewriter Crashes system
39030
39031 Time: System Intialization.
39032
39033 Meaning: The MODE switch for memory Y is incorrect.
39034
39035 Action: Correct the configuration and reboot.
39036
39037
39038 scas_init.pl1
39039 scas_init: MEM Y is not in the configuration but
39040 is enabled by the CPU switches.
39041
39042
39043 Stream: BOS Typewriter Crashes system
39044
39045 Time: System Intialization.
39046
39047
39048 scas_init 674 08/21/20 MR12.7^L
39049
39050
39051 Meaning: The bootload CPU enables memory Y. But there is
39052 no MEM card for this memory.
39053
39054 Action: Correct the configuration or the configuration
39055 deck and reboot.
39056
39057
39058 scas_init.pl1
39059 scas_init: More than one low-order MEM.
39060
39061
39062 Stream: BOS Typewriter Crashes system
39063
39064 Time: System Intialization.
39065
39066 Meaning: The configuration deck is incorrect.
39067
39068 Action: Correct the the configuration deck and reboot.
39069
39070
39071 scas_init.pl1
39072 scas_init: No config card for bootload CPU.
39073
39074
39075 Stream: BOS Typewriter Crashes system
39076
39077 Time: System Intialization.
39078
39079 Meaning: The configuration deck is incorrect.
39080
39081 Action: Correct the configuration or the configuration
39082 deck and reboot.
39083
39084
39085 scas_init.pl1
39086 scas_init: No config card for bootload MEM
39087
39088
39089 Stream: BOS Typewriter Crashes system
39090
39091 Time: System Intialization.
39092
39093 Meaning: The configuration deck is incorrect.
39094
39095 Action: Correct the the configuration deck and reboot.
39096
39097
39098 scas_init.pl1
39099 scas_init: No CPU config card.
39100
39101
39102 Stream: BOS Typewriter Crashes system
39103
39104
39105
39106 scas_init 675 08/21/20 MR12.7^L
39107
39108
39109 Time: System Intialization.
39110
39111 Meaning: The configuration deck is incorrect.
39112
39113 Action: Correct the the configuration deck and reboot.
39114
39115
39116 scas_init.pl1
39117 scas_init: No MEM config card.
39118
39119
39120 Stream: BOS Typewriter Crashes system
39121
39122 Time: System Intialization.
39123
39124 Meaning: The configuration deck is incorrect.
39125
39126 Action: Correct the the configuration deck and reboot.
39127
39128
39129 scas_init.pl1
39130 scas_init: Possible memory address overlap in MEM
39131 Y.
39132
39133
39134 Stream: BOS Typewriter Crashes system
39135
39136 Time: System Intialization.
39137
39138 Meaning: This indicates that the lower store size does not
39139 agree with the actual memory available in the
39140 store unit. A possible example of this is when
39141 the lower store is actually in two store units A
39142 and A1 and the secondary unit A1 is not
39143 enabled.
39144
39145 Action: Correct the configuration and reboot.
39146
39147
39148 scas_init.pl1
39149 scas_init: SCU port P configured as both expanded
39150 and non-expanded.
39151
39152
39153 Stream: BOS Typewriter Crashes system
39154
39155 Time: System Intialization.
39156
39157 Meaning: CPU configuration cards imply that Port P on SCU's
39158 P is the port number from 0 to 7 is both an
39159 expander port by being named as the CPU port in a
39160 CPU card with an expander_port field and not an
39161
39162
39163
39164 scas_init 676 08/21/20 MR12.7^L
39165
39166
39167 expander port by being named in one that has
39168 none.
39169
39170 Action: Correct the configuratin deck and reboot.
39171
39172
39173 scas_init.pl1
39174 scas_init: Size too large on config card for MEM
39175 Y.
39176
39177
39178 Stream: BOS Typewriter Crashes system
39179
39180 Time: System Intialization.
39181
39182 Meaning: Either the PORT SIZE plug on the free edge of the
39183 PQ board of the bootload CPU does not agree with
39184 the configuration deck or the actual amount of
39185 memory present in MEM Y does not agree with the
39186 config deck.
39187
39188
39189 Action: Correct the configuration or the configuration
39190 deck and reboot.
39191
39192
39193 scavenge_volume.pl1
39194 scavenge_volume: damaged switch found on for NAME
39195 at VTOCX dskX_NNS
39196
39197
39198 Stream: Logged in SYSERR log.
39199
39200 Time: During a physical volume scavenge of dskX_NNS
39201
39202 Meaning: The damaged switch in the VTOCEwas set prior to
39203 the scavenge.
39204
39205 Action: Recover the segment.
39206
39207
39208 scavenge_volume.pl1
39209 scavenge_volume: Damaged vtoce VTOCX
39210 dskX_NNS.
39211
39212
39213 Stream: Logged in SYSERR log.
39214
39215 Time: During a physical volume scavenge of dskX_NNS
39216
39217 Meaning: The VTOCE image before correction is recorded into
39218 the syserr log if scavenge_vol was invoked with
39219 the -dump control argument.
39220
39221
39222 scavenge_volume 677 08/21/20 MR12.7^L
39223
39224
39225 Action: No operator action is required.
39226
39227
39228 scavenge_volume.pl1
39229 scavenge_volume: Debug Trap on scavenge of
39230 dskX_NNS
39231
39232
39233 Stream: BOS Typewriter Crashes system
39234
39235 Time: At the completion of a volume scavenge of
39236 dskX_NNS
39237
39238 Meaning: This is a debugging trap which results when
39239 scavenge_vol is used with the -trap control
39240 argument.
39241
39242 Action: Type GO to resume Multics operation.
39243
39244
39245 scavenge_volume.pl1
39246 scavenge_volume: dirsw turned off for NAME at
39247 VTOCX dskX_NNS
39248
39249
39250 Stream: Logged in SYSERR log.
39251
39252 Time: During a physical volume scavenge of dskX_NNS
39253
39254 Meaning: The directory switch in the VTOCE was found on for
39255 a non-directory segment. It has been turned off.
39256 The segment has been damaged.
39257
39258 Action: Recover the segment.
39259
39260
39261 scavenge_volume.pl1
39262 scavenge_volume: Error freeing TYPE vtocx VTOCX
39263 on dskX_NNS. ERRORMESSAGE
39264
39265
39266 Stream: Logged in SYSERR log.
39267
39268 Time: During a physical volume scavenge of dskX_NNS.
39269
39270 Meaning: The VTOCE indicated could not be freed due to the
39271 error indicated.
39272
39273 Action: No operator action is required.
39274
39275
39276 scavenge_volume.pl1
39277
39278
39279
39280 scavenge_volume 678 08/21/20 MR12.7^L
39281
39282
39283 scavenge_volume: Error reading vtocx NNNN on
39284 dskX_NNS. ERRORMESSAGE
39285
39286
39287 Stream: Logged in SYSERR log.
39288
39289 Time: During a physical volume scavenge of dskX_NNS
39290
39291 Meaning: An error was encountered attempting to read the
39292 VTOCE indicated. The VTOCE is skipped and lost
39293 records are not recovered. The count of volume
39294 inconsistencies is not reset to zero.
39295
39296 Action: After the problems with the volume have been
39297 repaired run the scavenger again to recover lost
39298 records.
39299
39300
39301
39302 scavenge_volume.pl1
39303 scavenge_volume: Error writing vtocx NNNNN on
39304 dskX_NNS. ERRORMESSAGE
39305
39306
39307 Stream: Logged in SYSERR log.
39308
39309 Time: During a physical volume scavenge of dskX_NNS
39310
39311 Meaning: The error indicated was encountered writing a
39312 VTOCE.
39313
39314 Action: No operator action is required.
39315
39316
39317 scavenge_volume.pl1
39318 scavenge_volume: Faulting under the LOCK for
39319 debugging for USER
39320
39321
39322 Stream: BOS Typewriter sounds beeper
39323
39324 Time: During a physical volume salvage.
39325
39326 Meaning: A fault tag three fault is taken to exercise fault
39327 recovery.
39328
39329 Action: No operator action is required.
39330
39331
39332 scavenge_volume.pl1
39333 scavenge_volume: Freed NNN VTOCEs on dskX_NNS
39334
39335
39336
39337
39338 scavenge_volume 679 08/21/20 MR12.7^L
39339
39340
39341 Stream: Logged in SYSERR log.
39342
39343 Time: During a physical volume scavenge of dskX_NNS
39344
39345 Meaning: NNN VTOCEs were added to the free pool. These
39346 VTOCEs are VTOCEs found free but not marked as
39347 free in the VTOC map per-process VTOCEs from a
39348 prior bootload and per-bootload VTOCEs from a
39349 prior bootload.
39350
39351 Message: scavenge_volume: vtoce NAME at VTOCX
39352 dskX_NNS disk addr RRR bad
39353
39354 Stream: Logged in SYSERR log.
39355
39356 Time: During a physical volume scavenge of dskX_NNS
39357
39358 Meaning: Record address RRR in the VTOCE indicated is
39359 outside of the paging region for the volume. The
39360 segment has been damaged.
39361
39362 Action: Recover the segment.
39363
39364
39365 scavenge_volume.pl1
39366 scavenge_volume: Freed NNNN records on dskX_NNS
39367
39368
39369 Stream: Logged in SYSERR log.
39370
39371 Time: During a physical volume scavenge of dskX_NNS
39372
39373 Meaning: NNNN records were not claimed by any VTOCE and
39374 were not listed as free in the volume map. These
39375 records have been freed.
39376
39377 Action: No operator action is required.
39378
39379
39380 scavenge_volume.pl1
39381 scavenge_volume: freeing TYPE VTOCE NAME at VTOCX
39382 dskX_NNS
39383
39384
39385 Stream: Logged in SYSERR log.
39386
39387 Time: During a physical volume scavenge of dskX_NNS
39388
39389 Meaning: The message appears for each VTOCE freed if
39390 scavenge_vol was invoked with the -debug control
39391 argument.
39392
39393 Action: No operator action is required.
39394
39395
39396 scavenge_volume 680 08/21/20 MR12.7^L
39397
39398
39399
39400
39401 scavenge_volume.pl1
39402 scavenge_volume: Invalid File Map Checksum for
39403 NAME at VTOCX dskX_NNS.
39404
39405
39406 Stream: Logged in SYSERR log.
39407
39408 Time: During a physical volume scavenge of dskX_NNS.
39409
39410 Meaning: The filemap checksum was incorrect indicating
39411 damage to the VTOCE. The checksum is corrected.
39412 Other damage if found is reported.
39413
39414 Action: No operator action is required.
39415
39416
39417 scavenge_volume.pl1
39418 scavenge_volume: NNN errors reading VTOCEs on
39419 dskX_NNS
39420
39421
39422 Stream: BOS Typewriter.
39423
39424 Time: During a physical volume scavenge of dskX_NNS
39425
39426 Meaning: Errors were encountered reading VTOCEs. A message
39427 describing each error was recorded into the syserr
39428 log. The VTOCEs with errors are skipped and lost
39429 records are not recovered.
39430
39431 Action: When the volume has been repaired rerun the
39432 scavenger to recover the lost records.
39433
39434
39435
39436 scavenge_volume.pl1
39437 scavenge_volume: NNN VTOCEs on dskX_NNS
39438 damaged. MMM damaged during this scavenge.
39439
39440
39441 Stream: BOS Typewriter.
39442
39443 Time: At the completion of a volume scavenge of
39444 dskX_NNS
39445
39446 Meaning: The scavenger found a total of NNN damaged
39447 segments on the volume. Of these MMM were
39448 damaged by the scavenger due to inconsistencies in
39449 the VTOCEs for these segments. A message for each
39450 was recorded into the syserr log.
39451
39452
39453
39454 scavenge_volume 681 08/21/20 MR12.7^L
39455
39456
39457 Action: Examine the syserr log to find the damaged
39458 segments and recover them.
39459
39460
39461 scavenge_volume.pl1
39462 scavenge_volume: Out-of-service address in stock
39463 for dskX_NNS
39464
39465
39466 Stream: BOS Typewriter Crashes system
39467
39468 Time: During a scavenge of dskX_NNS
39469
39470 Meaning: While examining the record stock and
39471 out-of-service address was encountered. Due to
39472 the volume map locking protocols used this should
39473 never happen. It indicates hardware or software
39474 malfunction.
39475
39476 Action: Follow normal recovery procedures. Message:
39477 scavenge_volume: Processing vtocx NNNNN on
39478 dskX_NNS
39479
39480 Stream: BOS Typewriter.
39481
39482 Time: During a volume scavenge of dskX_NNS
39483
39484 Meaning: This message is printed every 2000 octal VTOCEs
39485 during the scan of the VTOC by the scavenger if
39486 scavenge_vol was invoked with the -debug option.
39487
39488 Action: No operator action is required.
39489
39490
39491 scavenge_volume.pl1
39492 scavenge_volume: Overflow on scavenge of
39493 dskX_NNS. Restarting.
39494
39495
39496 Stream: BOS Typewriter.
39497
39498 Time: During a physical volume scavenge of dskX_NNS.
39499
39500 Meaning: An internal table which tracks reused record
39501 addresses overflowed. All conflicts detected so
39502 far are resolved and the scavenge is restarted
39503 from the beginning.
39504
39505 Action: No operator action is required.
39506
39507
39508 scavenge_volume.pl1
39509
39510
39511
39512 scavenge_volume 682 08/21/20 MR12.7^L
39513
39514
39515 scavenge_volume: setting damaged switch on NAME
39516 at VTOCX dskX_NNS.
39517
39518
39519 Stream: Logged in SYSERR log.
39520
39521 Time: During a physical volume scavenge of dskX_NNS
39522
39523 Meaning: An inconsistency has been detected in the VTOCE
39524 and the damaged switch has been set. A message
39525 describing the inconsistency has been recorded in
39526 the syserr log. The binary information associated
39527 with this message includes the segment UID-path.
39528
39529 Action: Recover the segment.
39530
39531
39532 scavenge_volume.pl1
39533 scavenge_volume: Unable to resolve conflict for
39534 address RRR on dskX_NNS. astep=PTR
39535
39536
39537 Stream: Logged in SYSERR log.
39538
39539 Time: During a physical volume scavenge of dskX_NNS
39540
39541 Meaning: During the scan of the VTOC the scavenger found
39542 several VTOCEs which claimed the same record
39543 address RRR. It could not resolve the conflict
39544 since the segment with the ASTE indicated was
39545 active and could not be deactivated.
39546
39547 Action: Rerun the scavenger at a later time. It may be
39548 necessary to wait until the next bootload.
39549
39550
39551
39552 scavenge_volume.pl1
39553 scavenge_volume: Unable to resolve conflict for
39554 address RRR on dskX_NNS. Error at vtocx NNNN.
39555 ERRORMESSAGE.
39556
39557
39558 Stream: Logged in SYSERR log.
39559
39560 Time: During a physical volume scavenge of dskX_NNS
39561
39562 Meaning: During the VTOC walk the scavenger found several
39563 VTOCEs claiming the save address RRR. It was
39564 unable to resolve the conflict due to a VTOCE read
39565 error.
39566
39567
39568
39569
39570 scavenge_volume 683 08/21/20 MR12.7^L
39571
39572
39573 Action: After the volume has been repaired rerun the
39574 scavenger.
39575
39576
39577 scavenge_volume.pl1
39578 scavenge_volume: vtoce NAME at VTOCX
39579 dskX_NNS. cur len changed from X to Y
39580
39581
39582 Stream: Logged in SYSERR log.
39583
39584 Time: During a physical volume scavenge of dskX_NNS
39585
39586 Meaning: The current segment length field in the VTOCE has
39587 been corrected. The segment has been damaged.
39588
39589 Action: Recover the segment.
39590
39591
39592 scavenge_volume.pl1
39593 scavenge_volume: vtoce NAME at VTOCX
39594 dskX_NNS. max len changed from X to Y
39595
39596
39597 Stream: Logged in SYSERR log.
39598
39599 Time: During a physical volume scavenge of dskX_NNS
39600
39601 Meaning: The max length field in the VTOCE has been
39602 corrected. The segment has been damaged.
39603
39604 Action: Recover the segment.
39605
39606
39607 scavenge_volume.pl1
39608 scavenge_volume: vtoce NAME at VTOCX
39609 dskX_NNS. rec used changed from X to Y
39610
39611
39612 Stream: Logged in SYSERR log.
39613
39614 Time: During a physical volume scavenge of dskX_NNS
39615
39616 Meaning: The records used field in the VTOCE has been
39617 corrected. The segment has been damaged.
39618
39619 Action: Recover the segment.
39620
39621
39622 scavenge_volume.pl1
39623 scavenge_volume: vtoce NAME at VTOCX
39624 dskX_NNS. ref to pageno PPP at addr RRR
39625 deleted
39626
39627
39628 scavenge_volume 684 08/21/20 MR12.7^L
39629
39630
39631 Stream: Logged in SYSERR log.
39632
39633 Time: During a physical volume scavenge of dskX_NNS
39634
39635 Meaning: Address RRR was claimed by more than one VTOCE.
39636 The page indicated has been changed to a null
39637 page and the segment has been damaged.
39638
39639 Action: Recover the segment.
39640
39641
39642 scavenge_volume.pl1
39643 scavenge_volume: vtoce NAME at VTOCX
39644 dskX_NNS. time-record-product reset to zero
39645
39646
39647 Stream: Logged in SYSERR log.
39648
39649 Time: During a physical volume scavenge of dskX_NNS
39650
39651 Meaning: An invalid value was found in the
39652 time-record-product field of the VTOCE indicated.
39653 This field has been reset to zero.
39654
39655 Action: No operator action is required.
39656
39657
39658 scavenger.pl1
39659 scavenger: Begin scavenge of dskX_NNs by
39660 PERSON.PROJECT.TAG
39661
39662
39663 Stream: BOS Typewriter.
39664
39665 Time: When a physical volume is being scavenged
39666
39667 Meaning: This is an informational message at the beginning
39668 of a volume scavenge.
39669
39670 Action: No operator action is required.
39671
39672
39673 scavenger.pl1
39674 scavenger: Invalid block reset.
39675
39676
39677 Stream: BOS Typewriter Crashes system
39678
39679 Time: When a physical volume is being scavenged.
39680
39681 Meaning: A process attempted to clean up a scavenger block
39682 which was not assigned to it. This indicates a
39683 software malfunction.
39684
39685
39686 scavenger 685 08/21/20 MR12.7^L
39687
39688
39689 Action: Follow normal recovery procedures.
39690
39691
39692 scavenger.pl1
39693 scavenger: Meters from scavenge of dskX_NNs.
39694 METERINGDATA.
39695
39696
39697 Stream: Logged in SYSERR log.
39698
39699 Time: When a physical volume is being scavenged.
39700
39701 Meaning: Various peformance measurements of the scavenge
39702 are recorded if the appropriate scavenger control
39703 flag is set.
39704
39705 Action: No operator action is required.
39706
39707
39708 scavenger.pl1
39709 scavenger: Process table entry not owned by this
39710 process.
39711
39712
39713 Stream: BOS Typewriter Crashes system
39714
39715 Time: When a physical volume is being scavenged.
39716
39717 Meaning: The scavenger attempted to release a process table
39718 entry which did not belong to this process. This
39719 indicates a software malfunction.
39720
39721 Action: Follow normal recovery procedures.
39722
39723
39724 scavenger.pl1
39725 scavenger: Scavenge of dskX_NNs by
39726 PERSON.PROJECT.TAG completed with error.
39727 ERRORMESSAGE.
39728
39729
39730 Stream: BOS Typewriter.
39731
39732 Time: When a physical volume is being scavenged.
39733
39734 Meaning: Scavenging could not be completed because of the
39735 error indicated.
39736
39737 Action: Contact the system programming staff.
39738
39739
39740 scavenger.pl1
39741
39742
39743
39744 scavenger 686 08/21/20 MR12.7^L
39745
39746
39747 scavenger: Scavenge of dskX_NNs by
39748 PERSON.PROJECT.TAG completed.
39749
39750
39751 Stream: BOS Typewriter.
39752
39753 Time: When a physical volume is being scavenged.
39754
39755 Meaning: This is an informational message to indicate
39756 successful completion of a scavenge.
39757
39758 Action: No operator action is required.
39759
39760
39761 scavenger.pl1
39762 scavenger: Scavenge of dskX_NNs stopped.
39763
39764
39765 Stream: BOS Typewriter.
39766
39767 Time: During system shutdown.
39768
39769 Meaning: The system is being shutdown and a scavenge of
39770 dskX_NNs is in progress. The scavenge is
39771 terminated and likely had no effect.
39772
39773 Action: Rerun the scavenge.
39774
39775
39776 scavenger.pl1
39777 scavenger: XXXXXX condition signalled during
39778 scavenge of dskX_NNs by PERSON.PROJECT.TAG
39779
39780
39781 Stream: BOS Typewriter.
39782
39783 Time: When a physical volume is being scavenged.
39784
39785 Meaning: An unexpected XXXXXX condition was signalled
39786 during a volume scavenge causing abnormal
39787 termination of the scavenge.
39788
39789 Action: Contact the system programming staff.
39790
39791
39792 scr_util.pl1
39793 scr_util: error setting configuration register.
39794 SCU X must be set manually. Set the following
39795 switches on SCU X < Diagram of SCU Maintenance
39796 Panel is Printed Here> After setting the switches
39797 for SCU X place SCU S into Manual Mode and then
39798 into Program Mode
39799
39800
39801
39802 scr_util 687 08/21/20 MR12.7^L
39803
39804
39805 Stream: BOS Typewriter sounds beeper
39806
39807 Time: Reconfiguration e.g. adding or deleting a CPU
39808
39809 Meaning: The supervisor was unable to set the configuration
39810 register in the SCU indicated after 10 attempts.
39811 To avoid a system crash the SCU must be cleared
39812 manually. In this message the supervisor will
39813 print a diagram of the SCU Maintenance Panel
39814 indicating how each switch should be set.
39815
39816 Action: The operator should copy the diagram of the SCU
39817 Maintenance Panel printed by the supervisor or
39818 take the copy printed if possible. The operator
39819 should then go to the Maintenance Panel of the SCU
39820 indicated and set each switch on the diagram to
39821 the indicated position and then verify that each
39822 switch is in the correct position. Following
39823 this the operator should set the Program/Manual
39824 switch into the Manual position briefly and then
39825 return it to the Program position. If this
39826 procedure does not remedy the problem the message
39827 will be repeated and the System Programming Staff
39828 should be contacted.
39829
39830
39831
39832 scs_and_clock_init.pl1
39833 scs_and_clock_init: No CLOK card.
39834
39835
39836 Stream: BOS Typewriter Crashes system
39837
39838 Time: System Intialization.
39839
39840 Meaning: No CLOK card was found in the config deck. One is
39841 required.
39842
39843 Action: Add a CLOK card to the config deck.
39844
39845
39846 scs_and_clock_init.pl1
39847 scs_and_clock_init: No SCU port is assigned
39848 address zero.
39849
39850
39851 Stream: BOS Typewriter Crashes system
39852
39853 Time: System Intialization.
39854
39855 Meaning: None of the system controllers in the config deck
39856 appear to have a base address of zero.
39857
39858
39859
39860 scs_and_clock_init 688 08/21/20 MR12.7^L
39861
39862
39863 Action: Check the config deck and bootload processor port
39864 assignment and address switches.
39865
39866
39867
39868 scs_and_clock_init.pl1
39869 scs_and_clock_init: SCU clock on port NUMBER
39870 MALFUNCTION.
39871
39872
39873 Stream: BOS Typewriter.
39874
39875 Time: System Intialization.
39876
39877 Meaning: The calendar clock in the bootload SCU seems to be
39878 malfunctioning as specified by MALFUNCTION.
39879
39880 Action: Fix the SCU or configure another SCU as low
39881 order.
39882
39883
39884 scs_and_clock_init.pl1
39885 scs_and_clock_init: The zone on the CLOK card is
39886 not in time_info_.
39887
39888
39889 Stream: BOS Typewriter Crashes system
39890
39891 Time: System Intialization.
39892
39893 Meaning: The zone named on the CLOK card is not found in
39894 time_info_ the system's time information
39895 database. The system cannot run unless a known
39896 zone is specified.
39897
39898 Action: Update the CLOK card so that it contains a proper
39899 zone name. If the zone you need is not known to
39900 the system time_info_.cds will have to be
39901 updated a new system tape generated and then
39902 booting from that tape. time_info_ contains at
39903 least 1 name for each hour around the world. You
39904 may select a named zone near the one you need
39905 just to get the system up to be able to change
39906 time_info_.
39907
39908
39909
39910
39911 scas_init.pl1
39912 scs_init: CPU/IOM port range overlap. Using
39913 manual settings for cycle port priority.
39914
39915
39916
39917
39918 scs_init 689 08/21/20 MR12.7^L
39919
39920
39921 Stream: BOS Typewriter.
39922
39923 Time: System Intialization.
39924
39925 Meaning: The cycle port priority on the SCUs cannot be set
39926 optimally because the range of port numbers for
39927 CPUs and IOMs overlap. The manual settings of the
39928 cycle port priority switches on the SCUs will be
39929 used instead. The system may experience problems
39930 as a result with the typical symptom being
39931 op-not-complete faults at random times by CPUs
39932 with higher port numbers lower SCU port
39933 priority.
39934
39935 Action: Continue to operate the system normally but
39936 consult with Field Engineering personnel. If
39937 possible the system should be reconfigured so
39938 that the range of port numbers of IOMs and CPU do
39939 not overlap. Further CPU should be on
39940 higher-numbered ports than IOMs and Bulk Stores.
39941
39942
39943
39944 alm_syserr_caller.pl1
39945 search_ast: double uid UID. vtocx VTOCX on
39946 DRIVEPVID. active vtocx VTOCX2 on
39947 DRIVE2PVID2.
39948
39949
39950 Stream: Logged in SYSERR log.
39951
39952 Time: While system is running.
39953
39954 Meaning: A mismatch has been detected between the branch
39955 and the ASTE for a segment. The two segments
39956 indicated by VTOCE index and physical volume
39957 location/identifier claim to have the same file
39958 system unique identifier. The operation either
39959 proceeds or returns a connection failure to the
39960 user process as appropriate. This message is
39961 logged for the use of system programmers.
39962
39963 This error can occur if damage to a directory
39964 branch has caused its unique ID to become
39965 incorrect and if the incorrect unique ID happens
39966 to be identical to the unique ID of a segment
39967 already active.
39968
39969 Action: Contact the system programming staff.
39970
39971
39972 alm_syserr_caller.pl1
39973 search_ast: hash error
39974
39975
39976 search_ast 690 08/21/20 MR12.7^L
39977
39978
39979 Stream: BOS Typewriter Crashes system
39980
39981 Time: While system is running.
39982
39983 Meaning: This indicates a logic error in the supervisor or
39984 CPU or memory hardware problems.
39985
39986 Action: Follow normal recovery procedures.
39987
39988
39989 seg_fault.pl1
39990 seg_fault: illegal segfault on cpu X
39991
39992
39993 Stream: BOS Typewriter.
39994
39995 Time: While system is running.
39996
39997 Meaning: The SCU data stored by processor X indicates that
39998 a segment fault has occurred but the SDW indicated
39999 by the SCU data has no directed fault indicator.
40000 This indicates a logic error in the supervisor or
40001 CPU or memory hardware problems. The system
40002 attempts to retry the faulting instruction.
40003
40004 Action: Inform field engineering personnel. If this
40005 message persists attempt to delete the CPU.
40006
40007
40008
40009 seg_fault.pl1
40010 seg_fault: trailer list trap
40011
40012
40013 Stream: BOS Typewriter Crashes system
40014
40015 Time: While system is running.
40016
40017 Meaning: An attempt was made to set sst$tfreep to zero.
40018 The supervisor checks for this situation and
40019 crashes here when one entry remains in the trailer
40020 segment in order to trap an elusive bug which used
40021 to cause "trailer storage area exhausted" crashes
40022 when the trailer segment was not full. This
40023 indicates a logic error in the supervisor or CPU
40024 or memory hardware problems. BOS Typewriter
40025 Crashes systemes
40026
40027 Action: Follow normal recovery procedures. Be sure to get
40028 a dump.
40029
40030
40031
40032
40033
40034 seg_fault 691 08/21/20 MR12.7^L
40035
40036
40037
40038
40039 seg_fault.pl1
40040 seg_fault: trailer storage area exhausted
40041
40042
40043 Stream: BOS Typewriter Crashes system
40044
40045 Time: While system is running.
40046
40047 Meaning: There are no more free entries available in the
40048 system trailer segment str_seg. This may be
40049 indicative of software- or hardware-induced damage
40050 to the SST or str_seg or may be indicative of a
40051 number of logged-in processes which is vastly too
40052 large. A more likely cause is insufficiently
40053 large str_seg. The size of the str_seg can be
40054 changed by the TBLS STR card in the config deck.
40055 This indicates a logic error in the supervisor or
40056 CPU or memory hardware problems. BOS Typewriter
40057 Crashes systemes
40058
40059 Action: Follow normal recovery procedures. It may be
40060 necessary to increase the size of the str_seg by
40061 the TBLS STR card in the config deck. Be sure to
40062 get a dump.
40063
40064
40065
40066 segment_loader.pl1
40067 segment_loader: bad header size: SSS
40068
40069
40070 Stream: BOS Typewriter Crashes system
40071
40072 Time: System Intialization.
40073
40074 Meaning: A bad segment header was found in the mst source.
40075
40076 Action: Follow normal recovery procedures. $boot_tape
40077
40078
40079
40080 segment_loader.pl1
40081 segment_loader: bad header size: SSS
40082
40083
40084 Stream: BOS Typewriter Crashes system
40085
40086 Time: System Intialization.
40087
40088 Meaning: A bad segment header was found in the mst source.
40089
40090
40091
40092 segment_loader 692 08/21/20 MR12.7^L
40093
40094
40095 Action: Follow normal recovery procedures. $boot_tape
40096
40097
40098
40099 segment_loader.pl1
40100 segment_loader: error from
40101 slt_manager$build_entry
40102
40103
40104 Stream: BOS Typewriter Crashes system
40105
40106 Time: System Intialization.
40107
40108 Meaning: This indicates a logic error in the supervisor or
40109 CPU or memory hardware problems.
40110
40111 Action: Follow normal recovery procedures. $boot_tape
40112
40113
40114
40115 segment_loader.pl1
40116 segment_loader: error from
40117 slt_manager$build_entry
40118
40119
40120 Stream: BOS Typewriter Crashes system
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: Follow normal recovery procedures. $boot_tape
40128
40129
40130
40131 segment_loader.pl1
40132 segment_loader: Missing linkage or defs.
40133
40134
40135 Stream: BOS Typewriter Crashes system
40136
40137 Time: System Intialization.
40138
40139 Meaning: A linkage or definitions section which should be
40140 in the mst source appears to be missing.
40141
40142 Action: Follow normal recovery procedures. $boot_tape
40143
40144
40145
40146 segment_loader.pl1
40147 segment_loader: Missing linkage or defs.
40148
40149
40150 segment_loader 693 08/21/20 MR12.7^L
40151
40152
40153 Stream: BOS Typewriter Crashes system
40154
40155 Time: System Intialization.
40156
40157 Meaning: A linkage or definitions section which should be
40158 in the mst source appears to be missing.
40159
40160 Action: Follow normal recovery procedures. $boot_tape
40161
40162
40163
40164 segment_loader.pl1
40165 segment_loader: unexpected control type: TTT
40166
40167
40168 Stream: BOS Typewriter Crashes system
40169
40170 Time: System Intialization.
40171
40172 Meaning: A segment control word was found out of sequence
40173 in the mst source.
40174
40175 Action: Follow normal recovery procedures. $boot_tape
40176
40177
40178
40179 segment_loader.pl1
40180 segment_loader: unexpected control type: TTT
40181
40182
40183 Stream: BOS Typewriter Crashes system
40184
40185 Time: System Intialization.
40186
40187 Meaning: A segment control word was found out of sequence
40188 in the mst source.
40189
40190 Action: Follow normal recovery procedures. $boot_tape
40191
40192
40193
40194 segment_loader.pl1
40195 segment_loader: Unexpected DEFS/LINKAGE
40196
40197
40198 Stream: BOS Typewriter Crashes system
40199
40200 Time: System Intialization.
40201
40202 Meaning: A linkage or definitions section was found out of
40203 sequence in the mst source.
40204
40205 Action: Follow normal recovery procedures. $boot_tape
40206
40207
40208 segment_loader 694 08/21/20 MR12.7^L
40209
40210
40211
40212
40213 segment_loader.pl1
40214 segment_loader: Unexpected DEFS/LINKAGE
40215
40216
40217 Stream: BOS Typewriter Crashes system
40218
40219 Time: System Intialization.
40220
40221 Meaning: A linkage or definitions section was found out of
40222 sequence in the mst source.
40223
40224 Action: Follow normal recovery procedures. $boot_tape
40225
40226
40227
40228 segment_loader.pl1
40229 segment_loader: unknown control type TTT
40230
40231
40232 Stream: BOS Typewriter Crashes system
40233
40234 Time: System Intialization.
40235
40236 Meaning: A bad segment control word was found in the mst
40237 source.
40238
40239 Action: Follow normal recovery procedures. $boot_tape
40240
40241
40242
40243 segment_loader.pl1
40244 segment_loader: unknown control type TTT
40245
40246
40247 Stream: BOS Typewriter Crashes system
40248
40249 Time: System Intialization.
40250
40251 Meaning: A bad segment control word was found in the mst
40252 source.
40253
40254 Action: Follow normal recovery procedures. $boot_tape
40255
40256
40257
40258 segment_mover.pl1
40259 segment_mover: critical segment out of disk on
40260 DRIVENAME segno/astep = sss/aaa
40261
40262
40263 Stream: BOS Typewriter.
40264
40265
40266 segment_mover 695 08/21/20 MR12.7^L
40267
40268
40269 Time: While system is running.
40270
40271 Meaning: There are no more free pages on the physical
40272 volume where a critical segment resides and an
40273 extra page can not be found for that segment.
40274 Such a critical segment may be a physical buffer
40275 segment for a peripheral device attached via IOI.
40276 The user process receives a seg_fault_error
40277 signal.
40278
40279 Action: The logical volume containing the pack residing on
40280 DRIVENAME may be too full or may need rebalancing
40281 with the sweep_pv tool. Contact the system
40282 programming staff._sa
40283
40284
40285
40286 segment_mover.pl1
40287 segment_mover: Failed to seg move UUUENTRYNAME
40288 from DRIVENAME1 to DRIVENAME2 for USERNAME
40289
40290
40291 Stream: Logged in SYSERR log.
40292
40293 Time: While system is running.
40294
40295 Meaning: The system could not perform a cross-pack segment
40296 move because no pack in the logical volume had
40297 enough space to hold the segment. UUUU is the
40298 unique ID of the segment and ENTRYNAME its
40299 primary name.
40300
40301 Action: If this message persists the logical volume
40302 containing the packs on the drives noted is near
40303 full. In this case contact the system
40304 administrator.
40305
40306
40307
40308 segment_mover.pl1
40309 segment_mover: finishing truncation of pvtx PPP
40310 vtocx VVV
40311
40312
40313 Stream: BOS Typewriter.
40314
40315 Time: While system is running.
40316
40317 Meaning: The segment mover encountered an unexpected error
40318 in truncating either the old copy of a segment
40319 being moved cross-packs or in a new copy which was
40320 aborted for lack of space. This may be a physical
40321 device error or may be indicative of a logic
40322
40323
40324 segment_mover 696 08/21/20 MR12.7^L
40325
40326
40327 problem in the supervisor or may be symptomatic
40328 of main memory or CPU problems.
40329
40330 Action: Contact the system programming staff.
40331
40332
40333 segment_mover.pl1
40334 segment_mover: freeing vtocx VVV on new pvtx PPP.
40335 ERRORMESSAGE
40336
40337
40338 Stream: BOS Typewriter.
40339
40340 Time: While system is running.
40341
40342 Meaning: The segment mover encountered an unexpected error
40343 in freeing the VTOC entry of a segment being moved
40344 on a volume to which an abortive attempt to move
40345 the segment was made. This may be a physical
40346 device error.
40347
40348 Action: Contact the system programming staff.
40349
40350
40351 segment_mover.pl1
40352 segment_mover: freeing vtocx VVV on old pvtx PPP
40353 ERRORMESSAGE
40354
40355
40356 Stream: BOS Typewriter.
40357
40358 Time: While system is running.
40359
40360 Meaning: During a cross-pack segment move the system
40361 encountered an unexpected error in freeing the
40362 VTOC entry of the segment on the old pack This may
40363 be a physical device error or may be indicative
40364 of a logic problem in the supervisor or main
40365 memory or CPU problems.
40366
40367 Action: Contact the system programming staff.
40368
40369
40370 segment_mover.pl1
40371 segment_mover: get_pvtx PPP fails under ast
40372 lock
40373
40374
40375 Stream: BOS Typewriter Crashes system
40376
40377 Time: While system is running.
40378
40379
40380
40381
40382 segment_mover 697 08/21/20 MR12.7^L
40383
40384
40385 Meaning: The segment mover found that a physical volume
40386 appears to have been demounted during the time
40387 that the segment mover has had the active segment
40388 table locked.This indicates a logic error in the
40389 supervisor or CPU or memory hardware problems.
40390
40391 Action: Follow normal recovery procedures.
40392
40393
40394 segment_mover.pl1
40395 segment_mover: Moved UUUUENTRYNAME from
40396 DRIVENAME1 to DRIVENAME2 for USERNAME
40397
40398
40399 Stream: Logged in SYSERR log.
40400
40401 Time: While system is running.
40402
40403 Meaning: The system has successfully moved a segment from
40404 the pack on DRIVENAME1 to the pack on DRIVENAME2
40405 on a request for a new page on behalf of the user
40406 whose process group ID is USERNAME. UUUU is the
40407 unique ID of the segment and ENTRYNAME its
40408 primary name.
40409
40410 Action: If a large number of these messages occur the
40411 logical volume containing the packs specified by
40412 the drive names may be nearly full or poorly
40413 balanced. If these messages persist contact the
40414 system administrator.
40415
40416
40417
40418 segment_mover.pl1
40419 segment_mover: Moving QUOTA-TYPE quota account
40420 from pvtx PPP vtocx VVV ERRORMESSAGE
40421
40422
40423
40424 Stream: Logged in SYSERR log.
40425
40426 Time: While system is running.
40427
40428 Meaning: An error code was returned from the entry
40429 vtoc_attributes$get_quota when attempting to get
40430 terminal quota information from the old vtoce
40431 before new vtoce is created. In this case the
40432 terminal quota attributes for this QUOTA-TYPE
40433 either segment or directory quota account is
40434 lost.
40435
40436 Action: If this occurs the quota account for the segment
40437 that has been moved must be corrected manually by
40438
40439
40440 segment_mover 698 08/21/20 MR12.7^L
40441
40442
40443 the System Administrator or other qualified site
40444 personell.
40445
40446
40447
40448 segment_mover.pl1
40449 segment_mover: threading error
40450
40451
40452 Stream: BOS Typewriter Crashes system
40453
40454 Time: While system is running.
40455
40456 Meaning: The segment mover encountered bad threads while
40457 rethreading the old or new AST entries of a
40458 segment involved in a cross-pack segment move.
40459 This indicates a logic error in the supervisor or
40460 CPU or memory hardware problems.
40461
40462 Action: Follow normal recovery procedures.
40463
40464
40465 segment_mover.pl1
40466 segment_mover: unexpected segfault
40467
40468
40469 Stream: BOS Typewriter Crashes system
40470
40471 Time: While system is running.
40472
40473 Meaning: A segment fault occured during the cross-pack
40474 moving of a segment but this segment fault was
40475 not on the segment on which the segment mover was
40476 expecting one.This indicates a logic error in the
40477 supervisor or CPU or memory hardware problems.
40478
40479 Action: Follow normal recovery procedures. There may be
40480 inconsistencies in the physical volumes involved.
40481 These can be corrected by a physical volume
40482 salvage.
40483
40484
40485
40486 set_procs_required.pl1
40487 set_procs_required: Changing system default CPUs
40488 required from XXXX to YYYY for PERSON.PROJECT.TAG
40489
40490
40491 Stream: BOS Typewriter.
40492
40493 Time: While system is running.
40494
40495
40496
40497
40498 set_procs_required 699 08/21/20 MR12.7^L
40499
40500
40501 Meaning: The default set of CPUs has been changed from XXXX
40502 CPU tags to YYYY CPU tags by
40503 PERSON.PROJECT.TAG. These are the only CPUs on
40504 which processes will run which have not requested
40505 to be run on specific CPUs.
40506
40507 Action: No operator action is required.
40508
40509
40510 set_procs_required.pl1
40511 set_procs_required: Changing system default CPUs
40512 required from XXXX to YYYY for PERSON.PROJECT.TAG
40513
40514
40515 Stream: BOS Typewriter.
40516
40517 Time: While system is running.
40518
40519 Meaning: The default set of CPUs has been changed from XXXX
40520 CPU tags to YYYY CPU tags by
40521 PERSON.PROJECT.TAG. These are the only CPUs on
40522 which processes will run which have not requested
40523 to be run on specific CPUs.
40524
40525 Action: No operator action is required.
40526
40527
40528 set_procs_required.pl1
40529 set_procs_required: Failed to check access for
40530 USER.
40531
40532
40533 Stream: Logged in SYSERR log.
40534
40535 Time: While system is running.
40536
40537 Meaning: Access on >sc1>admin_acs>set_proc_required.acs
40538 could not be checked.
40539
40540 Action: Verify that the ACS seg exists.
40541
40542
40543 set_procs_required.pl1
40544 set_procs_required: Failed to check access for
40545 USER.
40546
40547
40548 Stream: Logged in SYSERR log.
40549
40550 Time: While system is running.
40551
40552 Meaning: Access on >sc1>admin_acs>set_proc_required.acs
40553 could not be checked.
40554
40555
40556 set_procs_required 700 08/21/20 MR12.7^L
40557
40558
40559 Action: Verify that the ACS seg exists.
40560
40561
40562 setfaults.pl1
40563 setfaults: deleted trailer
40564
40565
40566 Stream: BOS Typewriter Crashes system
40567
40568 Time: While system is running.
40569
40570 Meaning: A trailer entry record of a process's connection
40571 to a segment for some segment was marked as
40572 free.This indicates a logic error in the
40573 supervisor or CPU or memory hardware problems.
40574
40575
40576 Action: Follow normal recovery procedures. Contact the
40577 system programming staff.
40578
40579
40580
40581 setfaults.pl1
40582 setfaults: illegal cache access trailer
40583
40584
40585 Stream: BOS Typewriter Crashes system
40586
40587 Time: While system is running.
40588
40589 Meaning: It was found that no record of processes connected
40590 to a segment trailers existed when the
40591 encacheability state of a segment had to be
40592 changed. Such change can only occur if processes
40593 are connected to the segment.This indicates a
40594 logic error in the supervisor or CPU or memory
40595 hardware problems.
40596
40597 Action: Be sure to get a dump.Follow normal recovery
40598 procedures. Contact the system programming staff.
40599
40600
40601
40602 setfaults.pl1
40603 setfaults: illegal trailer
40604
40605
40606 Stream: BOS Typewriter Crashes system
40607
40608 Time: While system is running.
40609
40610 Meaning: A trailer entry record of a process's connection
40611 to a segment for some segment specifies a second
40612
40613
40614 setfaults 701 08/21/20 MR12.7^L
40615
40616
40617 segment as the descriptor segment for some process
40618 connected to that segment but that second segment
40619 does not have certain bits on in its AST entry
40620 which would be on in the AST entry of a descriptor
40621 segment. This indicates a logic error in the
40622 supervisor or CPU or memory hardware problems.
40623
40624 Action: Follow normal recovery procedures. Contact the
40625 system programming staff.
40626
40627
40628
40629 setfaults.pl1
40630 setfaults: missing trailer
40631
40632
40633 Stream: BOS Typewriter Crashes system
40634
40635 Time: While system is running.
40636
40637 Meaning: Upon terminating a segment it was found that no
40638 record of the process's connection to that segment
40639 trailer existed even though an SDW for that
40640 segment appeared in the process's descriptor
40641 segment i.e. the process was connected to it.
40642 This indicates a logic error in the supervisor or
40643 CPU or memory hardware problems.
40644
40645 Action: Follow normal recovery procedures. Contact the
40646 system programming staff.
40647
40648
40649
40650 wired_shutdown.pl1
40651 shutdown complete
40652
40653
40654 Stream: BOS Typewriter.
40655
40656 Time: Emergency shutdown
40657
40658 Meaning: Emergency shutdown is complete; this message was
40659 preceded by either "esd before fs enabled" or
40660 "system already shut down": no ESD was necessary.
40661
40662 Action: Reboot the system.
40663
40664
40665 shutdown_file_system.pl1
40666 shutdown complete
40667
40668
40669 Stream: BOS Typewriter.
40670
40671
40672 shutdown 702 08/21/20 MR12.7^L
40673
40674
40675 Time: System shutdown
40676
40677 Meaning: System shutdown emergency or regular has
40678 completed successfully. The system will return to
40679 bce. If any problem arises such that the system
40680 does not return to bce or other error condition
40681 the storage system will probably not be affected.
40682 If such problem arises attempt ESD. The message
40683 "system already shut down" will be printed if
40684 there is no problem. When the "shutdown complete"
40685 message is issued there is no more Multics
40686 information in main memory.
40687
40688
40689
40690 shutdown_file_system.pl1
40691 shutdown complete except for devices suspended.
40692
40693
40694 Stream: BOS Typewriter sounds beeper
40695
40696 Time: System shutdown
40697
40698 Meaning: Some disks could not be shut down due to hardware
40699 problems. Messages have occurred identifying
40700 these drives and the problems. All other drives
40701 have been shut down- their contents are not in
40702 main memory or on the paging device. The RPV has
40703 not been shut down either so that the system will
40704 perform some salvaging when it comes up.
40705
40706 Action: Attempt to ready those drives that are not ready.
40707 When this has been done retry ESD. If the drives
40708 have been made accessible ESD will succeed with a
40709 normal "shutdown complete" message. If they
40710 cannot be made ready the paging device if any
40711 is unflushed. See the description of the
40712 "warning: paging device unflushed" message.
40713
40714
40715
40716 shutdown.pl1
40717 shutdown: Cannot run on CPU X bootload CPU.
40718 Dump and try ESD. ERRORMESSAGE
40719
40720
40721 Stream: BOS Typewriter Crashes system
40722
40723 Time: System shutdown
40724
40725 Meaning: During an attempt to shut down the system the
40726 system could not run on the bootload CPU. This
40727 problem may be due to hardware or software
40728
40729
40730 shutdown 703 08/21/20 MR12.7^L
40731
40732
40733 problems. The system will attempt to crash which
40734 it may not complete.
40735
40736 Action: If the system does not complete its attempt to
40737 crash it should be crashed manually. It may be
40738 necessary to change the bootload CPU manually.
40739 This can be done by putting all CPUs into STEP
40740 mode manually assigning an interrupt mask to the
40741 new bootload CPU from the bootload SCU maintenance
40742 panel taking only the new bootload CPU out of
40743 STEP mode and doing an EXECUTE SWITCHES on that
40744 CPU. Once the system has crashed successfully an
40745 ESD should be attempted. This will most likely
40746 succeed.
40747
40748
40749
40750 shutdown.pl1
40751 shutdown: Condition CCCC signalled during
40752 shutdown. Normal shutdown failed. Get a dump
40753 and try an ESD.
40754
40755
40756
40757 Stream: BOS Typewriter Crashes system
40758
40759 Time: System shutdown
40760
40761 Meaning: During the attempt to shut down the system an
40762 unexpected condition has been signalled. This may
40763 result from hardware problems or a logic error in
40764 the supervisor. The system crashes and returns to
40765 BCE whereupon an ESD should be attempted in order
40766 to finish flushing Multics information from main
40767 memory. Because of the difference in
40768 implementation between normal shutdown and ESD it
40769 is possible that ESD will not encounter the same
40770 problem and instead be successful.
40771
40772
40773
40774 shutdown.pl1
40775 shutdown: Could not stop CPU TAG.
40776
40777
40778 Stream: BOS Typewriter.
40779
40780 Time: System shutdown.
40781
40782 Meaning: Shutdown stops all but the bootload processor.
40783 The CPU whose tag is TAG could not be stopped.
40784
40785
40786
40787
40788 shutdown 704 08/21/20 MR12.7^L
40789
40790
40791 Action: Note for system programmer action. If shutdown
40792 fails put all CPU's other than the bootload
40793 processor in step return to BCE manually and
40794 attempt an ESD.
40795
40796
40797
40798 shutdown_file_system.pl1
40799 shutdown_file_system: Error deactivating. Quota
40800 may be bad.
40801
40802
40803 Stream: BOS Typewriter.
40804
40805 Time: System shutdown
40806
40807 Meaning: The attempt to deactivate all segments in the file
40808 system by a tree-walk of threaded ASTEs failed
40809 likely due to inconsistent threading in the SST.
40810 The segments will be deactivated by a linear walk
40811 of the SST. Quota inconsistencies may be
40812 introduced by this. These can be corrected by a
40813 quota salvage of the hierarchy.
40814
40815 Action: At a convenient time run a quota salvage of the
40816 hierarchy.
40817
40818
40819 shutdown_file_system.pl1
40820 shutdown_file_system: from demount_pv on PVTX
40821 ERROR_MESSAGE
40822
40823
40824 Stream: BOS Typewriter.
40825
40826 Time: System shutdown
40827
40828 Meaning: A problem was encountered in shutting down the
40829 disk whose PVT index is PVTX. Most likely other
40830 messages identifying the pack drive and/or
40831 problem have preceded this message.
40832
40833 Action: Note for system programmer action. If other
40834 messages have preceded this message take remedial
40835 action as necessary. Attempt emergency shutdown
40836 after readying appropriate disk drives if this is
40837 the problem.
40838
40839
40840
40841 shutdown_file_system.pl1
40842 shutdown_file_system: NN locks set
40843
40844
40845
40846 shutdown_file_system 705 08/21/20 MR12.7^L
40847
40848
40849 Stream: BOS Typewriter.
40850
40851 Time: System shutdown
40852
40853 Meaning: Not all data base and directory locks were
40854 unlocked by the system before shutdown started.
40855 During emergency shutdown this is to be expected.
40856 During normal shutdown this may be symptomatic of
40857 software problems.
40858
40859 Action: If this message occurs during normal shutdown
40860 note for system programming staff.
40861
40862
40863
40864 start_cpu.pl1
40865 start_cpu: Added CPU CPUTAG
40866
40867
40868 Stream: BOS Typewriter.
40869
40870 Time: In response to an operator "rcf add cpu CPUTAG"
40871 command or at bootload time.
40872
40873 Meaning: The system has successfully added the CPU whose
40874 tag is CPUTAG to the configuration.
40875
40876 Action: No operator action is required.
40877
40878
40879 start_cpu.pl1
40880 start_cpu: CPU CPUTAG data switches are
40881 XXXXXXXXXXXX should be YYYYYYYYYYYY
40882
40883
40884 Stream: BOS Typewriter.
40885
40886 Time: In response to an "rcf add cpu CPUTAG" command
40887
40888 Meaning: The data switches on the CPU indicated are not set
40889 properly. The proper value is given.
40890
40891 Action: The incorrect value will prevent returning to BCE
40892 on that CPU by means of EXECUTE SWITCHES. Certain
40893 incorrect values will activate software debugging
40894 traps. The switches should be corrected. This
40895 can be done while the CPU is running.
40896
40897
40898
40899 start_cpu.pl1
40900 start_cpu: CPU CPUTAG: Model #: MODEL; Serial
40901 #: SERIAL; Ship date: YY/MM/DD.
40902
40903
40904 start_cpu 706 08/21/20 MR12.7^L
40905
40906
40907 Stream: Logged in SYSERR log.
40908
40909 Time: When a DPS8 CPU whose tag is CPUTAG is added to
40910 the system.
40911
40912 Meaning: The MODEL SERIAL and YY/MM/DD information is read
40913 from the DPS8 cpu's ID PROM. It is intended to be
40914 used as historical information for identifing
40915 CPUs regardless of what their current tag is
40916 assigned as.
40917
40918 Action: No operator action is required.
40919
40920
40921 start_cpu.pl1
40922 start_cpu: Unable to run on CPU x ERRORMESSAGE
40923
40924
40925 Stream: BOS Typewriter Crashes system
40926
40927 Time: In response to an "rcf add cpu CPUTAG" command or
40928 at bootload
40929
40930 Meaning: After adding a CPU the system was unable to run
40931 on that CPU. This indicates hardware or software
40932 failure.
40933
40934 Action: Follow normal recovery procedures.
40935
40936
40937 page_error.alm
40938 stock: deposit zero address.
40939
40940
40941 Stream: BOS Typewriter Crashes system
40942
40943 Time: While system is running.
40944
40945 Meaning: An attempt was made to deposit address zero into a
40946 record stock. This is an invalid address and it
40947 indicates hardware or software failure.
40948
40949 Action: Follow normal recovery procedures.
40950
40951
40952 page_error.alm
40953 stock: deposit zero address.
40954
40955
40956 Stream: BOS Typewriter Crashes system
40957
40958 Time: While system is running.
40959
40960
40961
40962 stock 707 08/21/20 MR12.7^L
40963
40964
40965 Meaning: An attempt was made to deposit address zero into a
40966 record stock. This is an invalid address and it
40967 indicates hardware or software failure.
40968
40969 Action: Follow normal recovery procedures.
40970
40971
40972 stock_man.pl1
40973 stock_man: Attempt to free non-empty stock on
40974 dskX_NN: pvtep=XXX|XXXXXX
40975 record_stockp=YYY|YYYYYY
40976
40977
40978 Stream: BOS Typewriter Crashes system
40979
40980 Time: During initialization immediately before the File
40981 System is activated or when demounting a physical
40982 disk volume.
40983
40984 Meaning: Not all free addresses have been deposited to the
40985 Volume Map successfully for the disk volume
40986 indicated. This is indicative of a software
40987 malfunction. The pointers printed are useful to
40988 site system programmers in analyzing the problem.
40989
40990 Action: Follow normal recovery procedures. The free
40991 addresses which are lost may be recovered by a
40992 physical volume salvage.
40993
40994
40995
40996 stock_man.pl1
40997 stock_man: Attempt to free non-empty stock on
40998 dskX_NN: pvtep=XXX|XXXXXX vtoce_stockp=YYY|YYYYYY
40999
41000
41001 Stream: BOS Typewriter Crashes system
41002
41003 Time: When demounting a physical disk volume.
41004
41005 Meaning: Not all free VTOCEs have been deposited to the
41006 VTOC Map successfully for the disk volume
41007 indicated. This is indicative of a software
41008 malfunction. The pointers printed are useful to
41009 site system programmers in analyzing the problem.
41010
41011 Action: Follow normal recovery procedures. The free
41012 VTOCEs which are lost may be recovered by a
41013 physical volume salvage.
41014
41015
41016
41017 stock_man.pl1
41018
41019
41020 stock_man 708 08/21/20 MR12.7^L
41021
41022
41023 stock_man: PVTE out of synch with record stock on
41024 dskX_NN: pvtep = XXX|XXXXXX record_stockp =
41025 YYY|YYYYYY
41026
41027
41028 Stream: BOS Typewriter Crashes system
41029
41030 Time: During initialization immediately before the File
41031 System is activated or when demounting a physical
41032 disk volume.
41033
41034 Meaning: The supervisor databases pvt and stock_seg are not
41035 in proper synchronization. The pointers printed
41036 are the locations of the databasse elements for
41037 which this condition has been detected. These
41038 pointers are useful to the site system programmers
41039 for analyzing the problem which is probably a
41040 software malfunction. dskX_NN is the physical
41041 volume whose tables are affected.
41042
41043 Action: Follow normal recovery procedures. The free
41044 addresses which are lost may be recovered by a
41045 physical volume salvage.
41046
41047
41048
41049 stock_man.pl1
41050 stock_man: PVTE out of synch with VTOCE stock on
41051 dskX_NN: pvtep = XXX|XXXXXX vtoce_stockp =
41052 YYY|YYYYYY
41053
41054
41055 Stream: BOS Typewriter Crashes system
41056
41057 Time: When demounting a physical disk volume.
41058
41059 Meaning: The supervisor databases pvt and stock_seg are not
41060 in proper synchronization. The pointers printed
41061 are the locations of the databasse elements for
41062 which this condition has been detected. These
41063 pointers are useful to the site system programmers
41064 for analyzing the problem which is probably a
41065 software malfunction. dskX_NN is the physical
41066 volume whose tables are affected. Some free
41067 VTOCEs may be lost.
41068
41069 Action: Follow normal recovery procedures. The lost
41070 VTOCEs can be recovered by a physical volume
41071 salvage.
41072
41073
41074
41075
41076
41077
41078 stop_cpu 709 08/21/20 MR12.7^L
41079
41080
41081
41082
41083 stop_cpu.pl1
41084 stop_cpu: Removed CPU CPUTAG.
41085
41086
41087 Stream: BOS Typewriter.
41088
41089 Time: In response to an operator "rcf dl cpu CPUTAG"
41090 command.
41091
41092 Meaning: The system has successfully deleted the CPU whose
41093 tag is CPUTAG from the configuration. The CPU is
41094 now halted at a DIS instruction.
41095
41096 Action: The operator can but need not physically remove
41097 the CPU from the configuration by disabling
41098 appropriate ports if desired.
41099
41100
41101
41102 stop_cpu.pl1
41103 stop_cpu: Unable to run on CPU X ERRORMESSAGE
41104
41105
41106 Stream: BOS Typewriter Crashes system
41107
41108 Time: When deleting a CPU.
41109
41110 Meaning: The system has just deleted a CPU which owned an
41111 interrupt mask. In trying to assign the mask to a
41112 different CPU X it was unable to run on that
41113 CPU. This indicates hardware or software
41114 malfunction.
41115
41116 Action: Follow normal recovery procedures.
41117
41118
41119 stop_cpu.pl1
41120 stop_mpx: CPU CPUTAG is now the bootload
41121 processor.
41122
41123
41124 Stream: BOS Typewriter.
41125
41126 Time: In response to an operator "rcf dl cpu CPUTAG"
41127 command.
41128
41129 Meaning: The CPU whose tag is CPUTAG is now the processor
41130 on which BCE will run at system shutdown or crash
41131 time unless some other processor is so designated
41132 in this way before the next shutdown or crash
41133 time. Unless BCE is rebooted after shutdown that
41134
41135
41136 stop_mpx 710 08/21/20 MR12.7^L
41137
41138
41139 CPU will be the bootload processor of the next
41140 bootload.
41141
41142 Action: No operator action is required.
41143
41144
41145 stop_process.pl1
41146 stop_process: attempt to stop initializer process
41147
41148
41149 Stream: BOS Typewriter Crashes system
41150
41151 Time: While system is running.
41152
41153 Meaning: This indicates a logic error in the supervisor or
41154 CPU or memory hardware problems.
41155
41156 Action: Follow normal recovery procedures.
41157
41158
41159 sum.pl1
41160 sum: dirmod failed to activate XXX|0
41161
41162
41163 Stream: BOS Typewriter Crashes system
41164
41165 Time: While system is running.
41166
41167 Meaning: Directory control could not activate a directory.
41168 This indicates a logic error in the supervisor or
41169 CPU or memory hardware problems. It is possible
41170 that the AST is damaged.
41171
41172 Action: Follow normal recovery procedures.
41173
41174
41175 sum.pl1
41176 sum: mylock error on XXX|0
41177
41178
41179 Stream: BOS Typewriter Crashes system
41180
41181 Time: While system is running.
41182
41183 Meaning: A directory which should not be locked is found
41184 locked. This indicates a logic error in the
41185 supervisor or CPU or memory hardware problems.
41186
41187 Action: Follow normal recovery procedures.
41188
41189
41190 sys_trouble.alm
41191 sys_trouble: Out-of-Segment-Bounds on prds.
41192
41193
41194 sys_trouble 711 08/21/20 MR12.7^L
41195
41196
41197 Stream: BOS Typewriter Crashes system
41198
41199 Time: While system is running.
41200
41201 Meaning: While running with the prds as a stack an attempt
41202 was " made to reference beyond the end of the
41203 prds. The likely " cause was stack overflow due
41204 either to a recursive loop " in the procedures
41205 running on the prds or insufficient " space
41206 allocated for the prds. If the latter the size
41207 of " the prds should be increased by means of the
41208 TBLS Configuration " Card.
41209
41210 Action: Follow normal recovery procedures.
41211
41212
41213 sys_trouble.alm
41214 sys_trouble: Execute fault by operator.
41215
41216
41217
41218 Stream: BOS Typewriter Crashes system
41219
41220 Time: While system is running.
41221
41222 Meaning: Operator depressed execute pushbutton on
41223 processor.
41224
41225 Action: $recov
41226
41227
41228 sys_trouble.alm
41229 sys_trouble: Fault in bound_interceptors.
41230
41231
41232
41233 Stream: BOS Typewriter Crashes system
41234
41235 Time: While system is running.
41236
41237 Meaning: A fault occured while handling another fault.
41238
41239 Action: $recov
41240
41241
41242 sys_trouble.alm
41243 sys_trouble: Fault in idle process.
41244
41245
41246
41247 Stream: BOS Typewriter Crashes system
41248
41249 Time: While system is running.
41250
41251
41252 sys_trouble 712 08/21/20 MR12.7^L
41253
41254
41255 Meaning: This indicates a logic error in the supervisor or
41256 CPU or memory hardware problems.
41257
41258 Action: $recov
41259
41260
41261 sys_trouble.alm
41262 sys_trouble: Fault/interrupt while on prds.
41263
41264
41265
41266 Stream: BOS Typewriter Crashes system
41267
41268 Time: While system is running.
41269
41270 Meaning: This indicates a logic error in the supervisor or
41271 CPU or memory hardware problems.
41272
41273 Action: $recov
41274
41275
41276 sys_trouble.alm
41277 sys_trouble: Fault/interrupt with ptl set.
41278
41279
41280
41281 Stream: BOS Typewriter Crashes system
41282
41283 Time: While system is running.
41284
41285 Meaning: This indicates a logic error in the supervisor or
41286 CPU or memory hardware problems.
41287
41288 Action: $recov
41289
41290
41291 sys_trouble.alm
41292 sys_trouble: Interrupts Masked in User Ring.
41293
41294
41295
41296 Stream: BOS Typewriter Crashes system
41297
41298 Time: While system is running.
41299
41300 Meaning: During processing of a fault it was noticed that
41301 interrupts " were masked in user-ring an invalid
41302 condition. This is a " debug trap crash enabled
41303 by the hidden tuning parameter "
41304 trap_invalid_masked.
41305
41306 Action: Contact the Multics System Development staff.
41307
41308
41309
41310 sys_trouble 713 08/21/20 MR12.7^L
41311
41312
41313
41314
41315 sys_trouble.alm
41316 sys_trouble: Page fault while on prds.
41317
41318
41319
41320 Stream: BOS Typewriter Crashes system
41321
41322 Time: While system is running.
41323
41324 Meaning: This indicates a logic error in the supervisor or
41325 CPU or memory hardware problems.
41326
41327 Action: $recov
41328
41329
41330 sys_trouble.alm
41331 sys_trouble: Ring 0 derail. MESSAGE
41332
41333
41334
41335 Stream: BOS Typewriter Crashes system
41336
41337 Time: While system is running.
41338
41339 Meaning: A supervisor software module discovered an
41340 untenable situation and " crashed the system by
41341 executing a derail DRL instruction. " If
41342 MESSAGE is also present it will be of the form:
41343 "module: explanation" and further details can be
41344 found in " this documentation in the description
41345 of "module".
41346
41347 Action: $recov
41348
41349
41350 sys_trouble.alm
41351 sys_trouble: Unexpected fault.
41352
41353
41354
41355 Stream: BOS Typewriter Crashes system
41356
41357 Time: System Intialization.
41358
41359 Meaning: This indicates a logic error in the supervisor or
41360 CPU or memory hardware problems.
41361
41362 Action: $recov
41363
41364
41365
41366
41367
41368 sys_trouble 714 08/21/20 MR12.7^L
41369
41370
41371
41372
41373 sys_trouble.alm
41374 sys_trouble: Unrecognized fault.
41375
41376
41377
41378 Stream: BOS Typewriter Crashes system
41379
41380 Time: While system is running.
41381
41382 Meaning: Unexpected or unrecognized fault subcondition. "
41383 Probable hardware malfunction.
41384
41385 Action: Contact the system programming staff.
41386
41387
41388 syserr_log_man_.pl1
41389 Syserr msg #NNNNN: MESSAGE-TEXT
41390 Segment: PATHNAME
41391 Volume: VOLUME-NAME
41392
41393
41394
41395 Stream: as severity0
41396
41397 Time: While system is running.
41398
41399 Meaning: This message is a repetition of a syserr log
41400 message which reported damage to a segment or a
41401 physical volume. There will always be two such
41402 messages in sequence a "Syserr msg. #XXX"
41403 message and either a "Volume:" or "Segment:"
41404 message. The first message is a copy of the
41405 logged syserr message of the given number; the
41406 second message identifies the volume or segment
41407 mentioned. This allows segments damaged by system
41408 action or segments in which the physical volume
41409 salvager observed damage to be identified
41410 unambiguously. These messages are logged in the
41411 Answering Service log at answering service startup
41412 time and every accounting update.
41413
41414 Action: Correlate volume salvager messages with previous
41415 printed volume salvager output to obtain more
41416 information about segment damage detected by the
41417 volume salvager. For those segments which are
41418 mentioned which have not been deleted or are not
41419 in deleted directories the "Segment:" message
41420 says if this is the case contact persons
41421 responsible for the ownership of that segment and
41422 undertake recovery procedures if needed.
41423
41424
41425
41426 syserr 715 08/21/20 MR12.7^L
41427
41428
41429
41430
41431 syserr_real.pl1
41432 syserr: Bad ring 1 call.
41433
41434
41435 Stream: Logged in SYSERR log.
41436
41437 Time: While system is running.
41438
41439 Meaning: A bad call to syserr was made from ring 1. The
41440 system keeps running.
41441
41442 Action: No operator action is required.
41443
41444
41445 syserr_real.pl1
41446 syserr: Mylock error.
41447
41448
41449 Stream: BOS Typewriter Crashes system
41450
41451 Time: While system is running.
41452
41453 Meaning: This indicates a logic error in the supervisor or
41454 CPU or memory hardware problems.
41455
41456 Action: Follow normal recovery procedures.
41457
41458
41459 alm_syserr_caller.pl1
41460 syserr_caller$search_ast_double_uid spurious call
41461 aste=desired uid=UID pv=DRIVEPVID
41462 vtocx=VTOCX.
41463
41464
41465 Stream: Logged in SYSERR log.
41466
41467 Time: While system is running.
41468
41469 Meaning: A call was made to indicate a double unique_id
41470 but it was not possible to reconstruct the error.
41471 The unique id physical volume
41472 location/identifier and vtoce index are provided.
41473
41474 Action: No operator action is required.
41475
41476
41477 alm_syserr_caller.pl1
41478 syserr_caller$search_ast_double_uid spurious call
41479 astep=null uid=UID pv=DRIVEPVID vtocx=VTOCX.
41480
41481
41482
41483
41484 syserr_caller$search_ast_double_^H7u^H1i^H6d 08/21/20 MR12.7^L
41485
41486
41487 Stream: Logged in SYSERR log.
41488
41489 Time: While system is running.
41490
41491 Meaning: A call was made to indicate a double unique_id
41492 but it was not possible to reconstruct the error.
41493 The unique_id physical volume
41494 location/identifier and VTOCE index are provided.
41495
41496 Action: No operator action is required.
41497
41498
41499 syserr_copy.pl1
41500 syserr_copy: Cannot add message to paged syserr
41501 log PTR. ERROR-MESSAGE
41502
41503
41504 Stream: BOS Typewriter Crashes system
41505
41506 Time: While system is running.
41507
41508 Meaning: This indicates a logic error in the supervisor or
41509 CPU or memory hardware problems. This may
41510 indicate that the syserr log partition has been
41511 damaged. If this is the case the LOG partition
41512 should be reinitialized using the BCE test_disk
41513 command. Some messages will be lost if this
41514 happens.
41515
41516 Action: Re-boot the system. Reinitialize the LOG
41517 partition if necessary.
41518
41519
41520 syserr_copy.pl1
41521 syserr_copy: LOG partition full. Further copying
41522 temporarily disabled.
41523
41524
41525 Stream: BOS Typewriter Crashes system
41526
41527 Time: While system is running.
41528
41529 Meaning: Both halves of the ring zero syserr log buffer are
41530 full. This generally indicates that the Answering
41531 Service is not copying messages from ring zero
41532 into >sc1>syserr_log; there will have been a
41533 previous message left in the Answering Service log
41534 describing why.
41535
41536 Action: If the problem is correctable copying from ring
41537 zero should be restarted see the documentation
41538 for "syserr_log_man_: Automatic log copying
41539
41540
41541
41542 syserr_copy 717 08/21/20 MR12.7^L
41543
41544
41545 disabled" for instructions; otherwise messages
41546 will be lost.
41547
41548
41549
41550 syserr_copy.pl1
41551 syserr_copy: LOG partition mostly full. Severity
41552 5 messages will be lost.
41553
41554
41555 Stream: BOS Typewriter sounds beeper
41556
41557 Time: While system is running.
41558
41559 Meaning: Both halves of the ring zero syserr log buffer are
41560 nearly full. This generally indicates that the
41561 Answering Service is not copying messages from
41562 ring zero into >sc1>syserr_log; there will have
41563 been a previous message left in the Answering
41564 Service log describing why.
41565
41566 Action: If the problem is correctable copying from ring
41567 zero should be restarted see the documentation
41568 for "syserr_log_man_: Automatic log copying
41569 disabled" for instructions; otherwise messages
41570 will be lost.
41571
41572
41573
41574 syserr_copy_wired_log.pl1
41575 syserr_copy_wired_log: Bad lock WWWWWWWWWWWW at
41576 SSS|OOOOOO
41577
41578
41579 Stream: BOS Typewriter Crashes system
41580
41581 Time: While system is running.
41582
41583 Meaning: This indicates a logic error in the supervisor or
41584 CPU or memory hardware problems. The contents of
41585 the lock word and its address are printed as an
41586 aid for debugging.
41587
41588 Action: Follow normal recovery procedures.
41589
41590
41591 syserr_copy_wired_log.pl1
41592 syserr_copy_wired_log: Fault occurred while
41593 copying into LOG partition. Messages NNNN to NNNN
41594 may be lost.
41595
41596
41597 Stream: BOS Typewriter Crashes system
41598
41599
41600 syserr_copy_wired_log 718 08/21/20 MR12.7^L
41601
41602
41603 Time: While system is running.
41604
41605 Meaning: This indicates a logic error in the supervisor or
41606 CPU or memory hardware problems. A fault has
41607 occurred while copying data from the wired syserr
41608 log buffer to the paged syserr log. This usually
41609 results from a disk error on the LOG partition
41610 which would also generate disk error messages.
41611 The sequence numbers of the affected messages are
41612 given because those messages may not appear in the
41613 LOG partition.
41614
41615 Action: Follow normal recovery procedures.
41616
41617
41618 syserr_copy_wired_log.pl1
41619 syserr_copy_wired_log: Too many faults log
41620 copying disabled.
41621
41622
41623 Stream: BOS Typewriter sounds beeper
41624
41625 Time: While system is running.
41626
41627 Meaning: This indicates a logic error in the supervisor or
41628 CPU or memory hardware problems. If too many
41629 errors occur updating the LOG partition log
41630 copying will be disabled which causes all further
41631 messages to be printed on the console but not
41632 entered in the log.
41633
41634 Action: Contact the system programming staff.
41635
41636
41637 syserr_log_man_.pl1
41638 syserr_log_man_: Attempting to swap syserr log
41639 segments. ERROR MESSAGE
41640
41641
41642 Stream: as severity1
41643
41644 Time: System Intialization.
41645
41646 Meaning: This indicates a logic error in the supervisor or
41647 CPU or memory hardware problems.
41648
41649 Action: Contact the system programming staff.
41650
41651
41652 syserr_log_man_.pl1
41653 syserr_log_man_: Automatic syserr log copying
41654 disabled.
41655
41656
41657
41658 syserr_log_man_ 719 08/21/20 MR12.7^L
41659
41660
41661 Stream: as severity1
41662
41663 Time: While system is running.
41664
41665 Meaning: Automatic copying of syserr messages into
41666 >sc1>syserr_log has been stopped due to an error
41667 in the copying process. Another message will have
41668 been printed prior to this one describing the
41669 problem. An Answering Service dump usually will
41670 have been created as well.
41671
41672 Action: If the error is recoverable temporary disk error
41673 record quota overflow etc.-- see the previous
41674 messages to make that decision syserr copying
41675 can be restarted by issuing the following command
41676 in admin mode ur using send_admin_command:
41677
41678 syserr_log_man_$restart_copying
41679
41680 If the problem persists delete the first segment
41681 first in the list produced by the list command
41682 in >sc1>syserr_log and restart copying. If the
41683 problem still persists rename or delete
41684 >sc1>syserr_log and reboot; the directory will be
41685 re-created automatically.
41686
41687 The display_log_segment command can be used to
41688 examine individual log segments for damage.
41689
41690
41691
41692 syserr_log_man_.pl1
41693 syserr_log_man_: Bad syserr_copy_interval value
41694 NNN seconds using 3600 seconds instead.
41695
41696
41697 Stream: as severity1
41698
41699 Time: System Intialization.
41700
41701 Meaning: The syserr copy interval in installation_parms is
41702 invalid.
41703
41704 Action: Use ed_installation_parms to correct it. A
41705 default will be used until then.
41706
41707
41708
41709 syserr_log_man_.pl1
41710 syserr_log_man_: Called too early.
41711
41712
41713 Stream: as severity2
41714
41715
41716 syserr_log_man_ 720 08/21/20 MR12.7^L
41717
41718
41719 Time: System Intialization.
41720
41721 Meaning: This indicates a logic error in the supervisor or
41722 CPU or memory hardware problems.
41723
41724 Action: Contact the system programming staff.
41725
41726
41727 syserr_log_man_.pl1
41728 syserr_log_man_: Calling
41729 hphcs_$new_syserr_reuse_log ERROR MESSAGE
41730
41731
41732 Stream: as severity1
41733
41734 Time: System Intialization.
41735
41736 Meaning: This indicates a logic error in the supervisor or
41737 CPU or memory hardware problems.
41738
41739 Action: Contact the system programming staff.
41740
41741
41742 syserr_log_man_.pl1
41743 syserr_log_man_: Cannot initiate log
41744 LOG-PATHNAME. ERROR MESSAGE
41745
41746
41747 Stream: as severity1
41748
41749 Time: System Intialization.
41750
41751 Meaning: This indicates a logic error in the supervisor or
41752 CPU or memory hardware problems.
41753
41754 Action: Contact the system programming staff.
41755
41756
41757 syserr_log_man_.pl1
41758 syserr_log_man_: Cannot open history log
41759 LOG-PATHNAME. ERROR MESSAGE
41760
41761
41762 Stream: as severity1
41763
41764 Time: System Intialization.
41765
41766 Meaning: This indicates a logic error in the supervisor or
41767 CPU or memory hardware problems.
41768
41769 Action: Contact the system programming staff.
41770
41771
41772
41773
41774 syserr_log_man_ 721 08/21/20 MR12.7^L
41775
41776
41777 Message: syserr_log_man_: Cannot migrate message
41778 #NNNNNNN
41779
41780 Stream: as severity1
41781
41782 Time: System Intialization.
41783
41784 Meaning: This indicates a logic error in the supervisor or
41785 CPU or memory hardware problems.
41786
41787 Action: Contact the system programming staff.
41788
41789
41790 syserr_log_man_.pl1
41791 syserr_log_man_: Cannot rename PATHNAME to
41792 NEW-NAME. ERROR MESSAGE
41793
41794
41795 Stream: as severity1
41796
41797 Time: System Intialization.
41798
41799 Meaning: This indicates a logic error in the supervisor or
41800 CPU or memory hardware problems.
41801
41802 Action: Contact the system programming staff.
41803
41804
41805 syserr_log_man_.pl1
41806 syserr_log_man_: Cannot replace ACL on
41807 >sc1>syserr_log. ERROR MESSAGE
41808
41809
41810 Stream: as severity1
41811
41812 Time: System Intialization.
41813
41814 Meaning: This indicates a logic error in the supervisor or
41815 CPU or memory hardware problems.
41816
41817 Action: Contact the system programming staff.
41818
41819
41820 syserr_log_man_.pl1
41821 syserr_log_man_: Cannot replace initial ACL on
41822 >sc1>syserr_log. ERROR MESSAGE
41823
41824
41825 Stream: as severity1
41826
41827 Time: System Intialization.
41828
41829
41830
41831
41832 syserr_log_man_ 722 08/21/20 MR12.7^L
41833
41834
41835 Meaning: This indicates a logic error in the supervisor or
41836 CPU or memory hardware problems.
41837
41838 Action: Contact the system programming staff.
41839
41840
41841 syserr_log_man_.pl1
41842 syserr_log_man_: Could not create
41843 >sc1>syserr_log. Automatic syserr log copying not
41844 initialized. ERROR MESSAGE
41845
41846
41847
41848 Stream: as severity1
41849
41850 Time: System Intialization.
41851
41852 Meaning: The syserr history directory was found to be
41853 missing during initialization and a new one could
41854 not be created; this probably indicates file
41855 system damage.
41856
41857 Action: Contact the system programming staff.
41858
41859
41860 syserr_log_man_.pl1
41861 syserr_log_man_: Could not create event channel.
41862 Automatic syserr log copying not initialized.
41863 ERROR MESSAGE
41864
41865
41866
41867 Stream: as severity1
41868
41869 Time: System Intialization.
41870
41871 Meaning: This indicates a logic error in the supervisor or
41872 CPU or memory hardware problems.
41873
41874 Action: Contact the system programming staff.
41875
41876
41877 syserr_log_man_.pl1
41878 syserr_log_man_: Could not use old syserr history
41879 dir: >sc1>syserr_log ERROR MESSAGE
41880
41881
41882 Stream: as severity1
41883
41884 Time: System Intialization.
41885
41886 Meaning: The syserr log history directory >sc1>syserr_log
41887 cannot be used; the reason is indicated by the
41888
41889
41890 syserr_log_man_ 723 08/21/20 MR12.7^L
41891
41892
41893 error message. The system will attempt to rename
41894 it and create a new one; any existing log segments
41895 may be moved from the old directory into the new
41896 current one once the system comes up if the
41897 renaming is successful.
41898
41899 Action: Contact the system programming staff. The
41900 condition causing the error should be corrected
41901 and the system re-booted.
41902
41903
41904
41905 syserr_log_man_.pl1
41906 syserr_log_man_: Created >sc1>syserr_log
41907
41908
41909 Stream: as severity0
41910
41911 Time: System Intialization.
41912
41913 Meaning: The syserr history directory >sc1>syserr_log was
41914 created automatically when it was found missing
41915 during initialization. This is normal during a
41916 cold boot but an error at all other times since
41917 it indicates that the directory was missing.
41918
41919 Action: Contact the system programming staff.
41920
41921
41922 syserr_log_man_.pl1
41923 syserr_log_man_: Error obtaining syserr log
41924 history. MESSAGE
41925
41926
41927 Stream: as severity2
41928
41929 Time: System Intialization.
41930
41931 Meaning: To verify syserr message sequence numbers will
41932 continue to increase despite clearing of the log
41933 partition the AS must look at the existing log
41934 segments. However some inconsistancy in the
41935 first history directory prevented this.
41936 >sc1>syserr_log.
41937
41938 Action: Fix any problems and issue the command
41939 "syserr_log_man_$restart_copying" from admin mode
41940 in the initializer process.
41941
41942
41943
41944 syserr_log_man_.pl1
41945
41946
41947
41948 syserr_log_man_ 724 08/21/20 MR12.7^L
41949
41950
41951 syserr_log_man_: Error verifying log partition
41952 sequence numbers.
41953
41954
41955 Stream: as severity2
41956
41957 Time: System Intialization.
41958
41959 Meaning: This indicates a logic error in the supervisor or
41960 CPU or memory hardware problems. There is some
41961 error in the log partition which prevents
41962 adjustment of the sequence numbers.
41963
41964 Action: Contact the system programming staff.
41965
41966
41967 syserr_log_man_.pl1
41968 syserr_log_man_: Renamed >sc1>syserr_log to
41969 NEW-NAME
41970
41971
41972 Stream: as severity1
41973
41974 Time: System Intialization.
41975
41976 Meaning: Indicates that the history directory has been
41977 renamed after an error in attempting to use it.
41978 Old log segments can be moved from here back into
41979 >sc1>syserr_log.
41980
41981 Action: Contact the system programming staff.
41982
41983
41984 syserr_log_man_.pl1
41985 syserr_log_man_: Syserr thresholds: NNN pages
41986 COMMENT NNN seconds COMMENT
41987
41988
41989 Stream: as severity0
41990
41991 Time: System Intialization.
41992
41993 Meaning: These are the thresholds for when Answering
41994 Service syserr copying will be performed. Each
41995 value may be followed by a comment; the comment
41996 "default" indicates that the installation_parms
41997 value was zero indicating that a default value is
41998 used. The comment "disabled" indicates that the
41999 installation_parms value was set to disable this
42000 log copying mechanism. The comment
42001 "installation_parms value invalid" means just
42002 that; the value in installation_parms must be
42003 updated and meantime a default is applied.
42004
42005
42006 syserr_log_man_ 725 08/21/20 MR12.7^L
42007
42008
42009 Action: Note for system programmer action.
42010
42011
42012 syserr_log_man_.pl1
42013 syserr_log_man_: Unable to open syserr log in
42014 PATH.
42015
42016
42017 Stream: as severity2
42018
42019 Time: System Intialization.
42020
42021 Meaning: To verify syserr message sequence numbers will
42022 continue to increase despite clearing of the log
42023 partition the AS must look at the existing log
42024 segments. However some inconsistancy in the
42025 first history directory prevented this.
42026 >sc1>syserr_log.
42027
42028 Action: Contact the system programming staff. Fix any
42029 problems in the syserr log history dir and issue
42030 the command "syserr_log_man_$restart_copying" from
42031 admin mode in the initializer process.
42032
42033
42034
42035 syserr_seg_manager.pl1
42036 syserr_seg_manager: Attempt to rename invalid log
42037 index NNNN
42038
42039
42040 Stream: BOS Typewriter Crashes system
42041
42042 Time: While system is running.
42043
42044 Meaning: This indicates a logic error in the supervisor or
42045 CPU or memory hardware problems.
42046
42047 Action: Follow normal recovery procedures. Reinitialize
42048 the LOG partition with the BCE test_disk command
42049 if this persists
42050
42051
42052
42053 syserr_seg_manager.pl1
42054 syserr_seg_manager: Attempt to rename log #NNNN
42055 already named NAME
42056
42057
42058 Stream: BOS Typewriter.
42059
42060 Time: While system is running.
42061
42062
42063
42064 syserr_seg_manager 726 08/21/20 MR12.7^L
42065
42066
42067 Meaning: This indicates a logic error in the supervisor or
42068 CPU or memory hardware problems.
42069
42070 Action: Note for system programmer action.
42071
42072
42073 syserr_seg_manager.pl1
42074 syserr_seg_manager: Cannot rename syserr log
42075 #NNNN from OLD-NAME to NEW-NAME for USER-NAME
42076
42077
42078 Stream: BOS Typewriter.
42079
42080 Time: While system is running.
42081
42082 Meaning: This indicates a logic error in the supervisor or
42083 CPU or memory hardware problems.
42084
42085 Action: Note for system programmer action.
42086
42087
42088 syserr_seg_manager.pl1
42089 syserr_seg_manager: Crawlout with syserr log
42090 locked. Automatic syserr log copying disabled.
42091
42092
42093 Stream: BOS Typewriter sounds beeper
42094
42095 Time: While system is running.
42096
42097 Meaning: An fault has occurred in the Answering Service
42098 while copying syserr messages from ring zero and
42099 copying from ring zero has been disabled. This
42100 probably indicates a supervisor logic error. This
42101 will be followed by a message from verify_lock
42102 identifying the fault.
42103
42104 Action: Attempt to restart copying or re-boot the system.
42105
42106
42107 syserr_seg_manager.pl1
42108 syserr_seg_manager: No messages in live syserr
42109 log PTR.
42110
42111
42112 Stream: BOS Typewriter Crashes system
42113
42114 Time: System Intialization.
42115
42116 Meaning: This indicates a logic error in the supervisor or
42117 CPU or memory hardware problems. When attempting
42118 to verify the message sequence numbers in the live
42119 syserr log it was found that no messages were
42120
42121
42122 syserr_seg_manager 727 08/21/20 MR12.7^L
42123
42124
42125 present. This should not hapen at this point
42126 because syserr log initialization
42127 init_syserr_log always places a message in the
42128 log.
42129
42130 Action: Contact the system programming staff.
42131
42132 Messaage: syserr_seg_manager: Log message
42133 sequence numbers adjusted in PTR beginning at
42134 SEQUENCE.
42135
42136 Stream: BOS Typewriter.
42137
42138 Time: System Intialization.
42139
42140 Meaning: The sequence numbers in the log partition were
42141 found to preceed the sequence numbers found in the
42142 log history. Thus the numbers in the partition
42143 and the wired log were adjusted appropriately.
42144 This message indicates the new sequence number
42145 where the adjustment started for each of the two
42146 ring 0 paged logs. This will occur after the log
42147 partition has been damaged or manually cleared.
42148
42149 Action: Contact the system programming staff.
42150
42151
42152 wired_shutdown.pl1
42153 system already shut down
42154
42155
42156 Stream: BOS Typewriter.
42157
42158 Time: Emergency shutdown
42159
42160 Meaning: An attempt to perform emergency shutdown was made
42161 after a previous attempt or normal shutdown
42162 succeeded. No ESD is necessary in this case. The
42163 "shutdown complete" message follows.
42164
42165 Action: No operator action is required.
42166
42167
42168 system_control_.pl1
42169 system_control_: fault during init
42170
42171
42172 Stream: ring 4 system control.
42173
42174 Time: System Intialization.
42175
42176
42177
42178
42179
42180 system_control_ 728 08/21/20 MR12.7^L
42181
42182
42183 Meaning: Some error condition has occurred unexpectedly
42184 while starting up the ring 4 initializer
42185 environment. The system will return to bce.
42186
42187 Action: Contact the system programming staff. Follow
42188 normal recovery procedures.
42189
42190
42191
42192
42193
42194 system_startup_.pl1
42195 system_startup_ Renamed >XXXXX to >XXXXX.!BBB.....
42196
42197
42198 Stream: BOS Typewriter.
42199
42200 Time: System Intialization.
42201
42202 Meaning: The segment >disk_table or the directory >lv as
42203 specified by XXXXX in the message was renamed in
42204 response to the "nodt" or "nolv" option on the bce
42205 "boot" command line.
42206
42207 Action: No operator action is required.
42208
42209
42210 system_startup_.pl1
42211 system_startup_: error on initializer io streams
42212
42213
42214 Stream: BOS Typewriter Crashes system
42215
42216 Time: System Intialization.
42217
42218 Meaning: BOS Typewriter Crashes systemes The system will
42219 return to bce.
42220
42221 Action: Follow normal recovery procedures. Try another
42222 boot tape and check that the hardware is running
42223 correctly.
42224
42225
42226
42227 system_startup_.pl1
42228 system_startup_: Recursive error condition.
42229
42230
42231 Stream: BOS Typewriter Crashes system
42232
42233 Time: System Intialization.
42234
42235
42236
42237
42238 system_startup_ 729 08/21/20 MR12.7^L
42239
42240
42241 Meaning: BOS Typewriter Crashes systemes The system will
42242 return to bce.
42243
42244 Action: Follow normal recovery procedures. Boot another
42245 system and examine the dump.
42246
42247
42248
42249 system_startup_.pl1
42250 system_startup_: The config deck is empty.
42251
42252
42253 Stream: BOS Typewriter Crashes system
42254
42255 Time: System Intialization.
42256
42257 Meaning: BOS Typewriter Crashes systemes The system will
42258 return to bce. This error should not occur
42259 because earlier steps in initialization depend
42260 upon the config deck. If it does however type
42261 GO after putting a config deck in place.
42262
42263
42264 Action: Follow normal recovery procedures. Use another
42265 boot tape or check that the hardware is operating
42266 correctly.
42267
42268
42269
42270 system_startup_.pl1
42271 system_startup_: The config_deck segment is
42272 missing.
42273
42274
42275 Stream: BOS Typewriter Crashes system
42276
42277 Time: System Intialization.
42278
42279 Meaning: BOS Typewriter Crashes systemes The segment
42280 config_deck is missing. This error should not
42281 occur because earlier steps in initialization
42282 depend upon the config deck.
42283
42284 Action: Follow normal recovery procedures. Use another
42285 boot tape or check that the hardware is operating
42286 correctly.
42287
42288
42289
42290 system_startup_.pl1
42291 system_startup_: The root logical volume is not
42292 complete. "boot rlvs" level 2 directory salvage
42293 aborted.
42294
42295
42296 system_startup_ 730 08/21/20 MR12.7^L
42297
42298
42299 Stream: BOS Typewriter.
42300
42301 Time: System Intialization.
42302
42303 Meaning: One or more physical volumes of the Root Logical
42304 Volume RLV registered in the volume registration
42305 database are not specified on the root config
42306 card and are therefore not mounted. Level 2
42307 directory salvage cannot take place with an
42308 incomplete RLV.
42309
42310 Action: Mount the missing packs with the add_vol command
42311 and then use the salvage_dirs command.
42312
42313
42314
42315 system_startup_.pl1
42316 system_startup_: unclaimed COND
42317 machine conditions in octal
42318
42319
42320
42321 Stream: BOS Typewriter sounds beeper
42322
42323 Time: System Intialization.
42324
42325 Meaning: Some error condition has occurred unexpectedly
42326 inside the ring 1 environment. Diagnostic
42327 information is typed after this line. The system
42328 should return to Initializer command level still
42329 in ring 1 and be able to continue running.
42330
42331 Action: Contact the system programming staff.
42332
42333
42334 system_startup_.pl1
42335 system_startup_: unclaimed condition-name
42336 condition.
42337
42338
42339 Stream: BOS Typewriter sounds beeper
42340
42341 Time: System Intialization.
42342
42343 Meaning: An error has occurred while executing in the ring
42344 1 Initializer environment. The system returns to
42345 ring 1 command level. For some errors machine
42346 conditions are displayed in subsequent messages.
42347
42348 Action: Contact the system programming staff.
42349
42350
42351
42352
42353
42354 system_startup_ 731 08/21/20 MR12.7^L
42355
42356
42357
42358
42359 system_startup_.pl1
42360 system_startup_: Will not reload
42361
42362
42363 Stream: BOS Typewriter.
42364
42365 Time: Response to operator reload command.
42366
42367 Meaning: One or more volumes cannot be mounted. Reloading
42368 cannot proceed. The system returns to ring 1
42369 command level.
42370
42371 Action: Correct the problem and try again.
42372
42373
42374 system_startup_.pl1
42375 system_startup_: XYZ is not a legal command.
42376 Type help for a list of commands.
42377
42378
42379 Stream: BOS Typewriter.
42380
42381 Time: System Intialization.
42382
42383 Meaning: The operator has issued a command to the ring 1
42384 environment that cannot be executed. No action
42385 was taken on the illegal command.
42386
42387 Action: If the command is misspelled retype it correctly.
42388 If the command is intended for the ring 4
42389 Answering Service type "standard" first to leave
42390 the ring 1 environment and then retype the desired
42391 command.
42392
42393
42394
42395 tape_reader.pl1
42396 tape_reader: bad_major_status: SSS
42397
42398
42399 Stream: BOS Typewriter Crashes system
42400
42401 Time: System Intialization.
42402
42403 Meaning: The bootload tape is unreadable.
42404
42405 Action: $boot_tape Try another tape drive.
42406
42407
42408
42409
42410
42411
42412 tape_reader 732 08/21/20 MR12.7^L
42413
42414
42415
42416
42417 tape_reader.pl1
42418 tape_reader: unable to read system tape
42419
42420
42421 Stream: BOS Typewriter Crashes system
42422
42423 Time: System Intialization.
42424
42425 Meaning: The bootload tape is unreadable.
42426
42427 Action: $boot_tape
42428
42429
42430 tc_init.pl1
42431 tc_init: cannot create cpu_X.prds. This CPU may
42432 not be added. ERROR_MESSAGE
42433
42434
42435 Stream: BOS Typewriter.
42436
42437 Time: System Intialization.
42438
42439 Meaning: A difficulty was encountered in creating the PRDS
42440 for a configurable CPU. Later attempts to add
42441 this CPU will fail. It will be marked as "off" in
42442 the CONFIG deck.
42443
42444 Action: Contact the system programming staff. When the
42445 problem has been remedied shut down and reboot
42446 and then add this CPU.
42447
42448
42449
42450 tc_init.pl1
42451 tc_init: cannot create cpu_X.prds. This CPU may
42452 not be added. ERROR_MESSAGE
42453
42454
42455 Stream: BOS Typewriter.
42456
42457 Time: System Intialization.
42458
42459 Meaning: A difficulty was encountered in creating the PRDS
42460 for a configurable CPU. Later attempts to add
42461 this CPU will fail. It will be marked as "off" in
42462 the CONFIG deck.
42463
42464 Action: Contact the system programming staff. When the
42465 problem has been remedied shut down and reboot
42466 and then add this CPU.
42467
42468
42469
42470 tc_init 733 08/21/20 MR12.7^L
42471
42472
42473
42474
42475 tc_init.pl1
42476 tc_init: Cannot start up first idle process.
42477 Check switches.
42478
42479
42480 Stream: BOS Typewriter Crashes system
42481
42482 Time: System Intialization.
42483
42484 Meaning: The idle process for the bootload CPU could not be
42485 started. This may be an error in setting of
42486 configuration switches or may be indicative of a
42487 logic problem in the supervisor.
42488
42489 Action: Perform an emergency shutdown. Check all main
42490 module configuration switches. If a problem was
42491 corrected reboot. Otherwise be sure to get a
42492 dump and contact the systems programming staff.
42493
42494
42495
42496 tc_init.pl1
42497 tc_init: Cannot start up first idle process.
42498 Check switches.
42499
42500
42501 Stream: BOS Typewriter Crashes system
42502
42503 Time: System Intialization.
42504
42505 Meaning: The idle process for the bootload CPU could not be
42506 started. This may be an error in setting of
42507 configuration switches or may be indicative of a
42508 logic problem in the supervisor.
42509
42510 Action: Perform an emergency shutdown. Check all main
42511 module configuration switches. If a problem was
42512 corrected reboot. Otherwise be sure to get a
42513 dump and contact the systems programming staff.
42514
42515
42516
42517 tc_init.pl1
42518 tc_init: Could not delete old PRDSNAME.
42519 ERRORMESSAGE
42520
42521
42522 Stream: BOS Typewriter.
42523
42524 Time: System Intialization.
42525
42526
42527
42528 tc_init 734 08/21/20 MR12.7^L
42529
42530
42531 Meaning: The old PRDS PRDSNAME from the previous bootload
42532 in >system_library_1 could not be deleted. When
42533 the CPU whose tag is part of PRDSNAME is added
42534 the old PRDS will be used. ERRORMESSAGE is a
42535 standard error_table_ message.
42536
42537 Action: Contact the system programming staff.
42538
42539
42540 tc_init.pl1
42541 tc_init: Could not delete old PRDSNAME.
42542 ERRORMESSAGE
42543
42544
42545 Stream: BOS Typewriter.
42546
42547 Time: System Intialization.
42548
42549 Meaning: The old PRDS PRDSNAME from the previous bootload
42550 in >system_library_1 could not be deleted. When
42551 the CPU whose tag is part of PRDSNAME is added
42552 the old PRDS will be used. ERRORMESSAGE is a
42553 standard error_table_ message.
42554
42555 Action: Contact the system programming staff.
42556
42557
42558 tc_init.pl1
42559 tc_init: Could not rename prds to PRDSNAME.
42560 ERRORMESSAGE
42561
42562
42563 Stream: BOS Typewriter.
42564
42565 Time: System Intialization.
42566
42567 Meaning: The segment "prds" in >system_library_1 could not
42568 be renamed to PRDSNAME which is the correct name
42569 for the PRDS for the bootload processor.
42570 ERRORMESSAGE is a standard error_table_ message.
42571
42572 Action: Notify the system programming staff. Action
42573 should be taken by the programming staff to rename
42574 this segment. If the problem cannot be sorted
42575 out avoid reconfiguring the bootload CPU during
42576 this bootload.
42577
42578
42579
42580 tc_init.pl1
42581 tc_init: Could not rename prds to PRDSNAME.
42582 ERRORMESSAGE
42583
42584
42585
42586 tc_init 735 08/21/20 MR12.7^L
42587
42588
42589 Stream: BOS Typewriter.
42590
42591 Time: System Intialization.
42592
42593 Meaning: The segment "prds" in >system_library_1 could not
42594 be renamed to PRDSNAME which is the correct name
42595 for the PRDS for the bootload processor.
42596 ERRORMESSAGE is a standard error_table_ message.
42597
42598 Action: Notify the system programming staff. Action
42599 should be taken by the programming staff to rename
42600 this segment. If the problem cannot be sorted
42601 out avoid reconfiguring the bootload CPU during
42602 this bootload.
42603
42604
42605
42606 tc_init.pl1
42607 tc_init: Could not start CPU CPUTAG.
42608
42609
42610 Stream: BOS Typewriter.
42611
42612 Time: System Intialization.
42613
42614 Meaning: The CPU whose tag is CPUTAG could not be
42615 automatically started by system bootload.
42616
42617 Action: Check all configuration switches on CPU and main
42618 memory modules especially the CPU STEP switch on
42619 the CPU which could not be added and its port
42620 enable switches. If all switches were correct
42621 add the CPU via the addcpu command.
42622
42623
42624
42625 tc_init.pl1
42626 tc_init: Could not start CPU CPUTAG.
42627
42628
42629 Stream: BOS Typewriter.
42630
42631 Time: System Intialization.
42632
42633 Meaning: The CPU whose tag is CPUTAG could not be
42634 automatically started by system bootload.
42635
42636 Action: Check all configuration switches on CPU and main
42637 memory modules especially the CPU STEP switch on
42638 the CPU which could not be added and its port
42639 enable switches. If all switches were correct
42640 add the CPU via the addcpu command.
42641
42642
42643
42644 tc_init 736 08/21/20 MR12.7^L
42645
42646
42647
42648
42649 tc_init.pl1
42650 tc_init: Inconsistent SCHD config card values.
42651
42652
42653 Stream: BOS Typewriter Crashes system
42654
42655 Time: System Intialization.
42656
42657 Meaning: The SCHD config card is not in the correct format
42658 or some values are out of acceptable range. In
42659 particular the value of min_eligible cannot
42660 exceed that of max_eligible; also the value of
42661 max_eligible plus the max number of stopped
42662 stack_0's default = 4 cannot exceed
42663 max_max_eligible.
42664
42665 Action: Check the SCHD config card refer to the MOH and
42666 correct. Re-boot the system.
42667
42668
42669
42670 tc_init.pl1
42671 tc_init: Inconsistent SCHD config card values.
42672
42673
42674 Stream: BOS Typewriter Crashes system
42675
42676 Time: System Intialization.
42677
42678 Meaning: The SCHD config card is not in the correct format
42679 or some values are out of acceptable range. In
42680 particular the value of min_eligible cannot
42681 exceed that of max_eligible; also the value of
42682 max_eligible plus the max number of stopped
42683 stack_0's default = 4 cannot exceed
42684 max_max_eligible.
42685
42686 Action: Check the SCHD config card refer to the MOH and
42687 correct. Re-boot the system.
42688
42689
42690
42691 tc_init.pl1
42692 tc_init: No valid processor tags on CPU cards.
42693
42694
42695 Stream: BOS Typewriter Crashes system
42696
42697 Time: System Intialization.
42698
42699
42700
42701
42702 tc_init 737 08/21/20 MR12.7^L
42703
42704
42705 Meaning: No CPU CONFIG cards contained valid A - H CPU
42706 tags. Normally this message will not appear if
42707 the bootload CPU is mis-specified as this error
42708 will be detected by scas_init and thus this may
42709 be indicative of a supervisor logic problem.
42710
42711 Action: Check that all CPU CONFIG cards are correct. If
42712 not perform an emergency shutdown correct them
42713 and reboot. If so be sure to get a dump and
42714 contact system programming personnel.
42715
42716
42717
42718 tc_init.pl1
42719 tc_init: No valid processor tags on CPU cards.
42720
42721
42722 Stream: BOS Typewriter Crashes system
42723
42724 Time: System Intialization.
42725
42726 Meaning: No CPU CONFIG cards contained valid A - H CPU
42727 tags. Normally this message will not appear if
42728 the bootload CPU is mis-specified as this error
42729 will be detected by scas_init and thus this may
42730 be indicative of a supervisor logic problem.
42731
42732 Action: Check that all CPU CONFIG cards are correct. If
42733 not perform an emergency shutdown correct them
42734 and reboot. If so be sure to get a dump and
42735 contact system programming personnel.
42736
42737
42738
42739 tc_init.pl1
42740 tc_init: Size of PRDS on TBLS card too small; XXX
42741 KW will be used.
42742
42743
42744 Stream: BOS Typewriter.
42745
42746 Time: System Intialization.
42747
42748 Meaning: The size of the PRDS specified on the TBLS card in
42749 the Configuration Deck is smaller than the size of
42750 the PRDS defined in the MST header. The size of
42751 the PRDS will be that defined in the MST header.
42752 Further the TBLS card in the Configuration Deck
42753 has been changed to reflect the minimum size of
42754 the PRDS
42755
42756
42757
42758
42759
42760 tc_init 738 08/21/20 MR12.7^L
42761
42762
42763 tc_init.pl1
42764 tc_init: Size of PRDS on TBLS card too small; XXX
42765 KW will be used.
42766
42767
42768 Stream: BOS Typewriter.
42769
42770 Time: System Intialization.
42771
42772 Meaning: The size of the PRDS specified on the TBLS card in
42773 the Configuration Deck is smaller than the size of
42774 the PRDS defined in the MST header. The size of
42775 the PRDS will be that defined in the MST header.
42776 Further the TBLS card in the Configuration Deck
42777 has been changed to reflect the minimum size of
42778 the PRDS
42779
42780
42781
42782 verify_lock.pl1
42783 Terminating user process NAME: Fatal salvaging of
42784 process directory.
42785
42786
42787 Stream: BOS Typewriter Terminates user process
42788
42789 Time: While system is running.
42790
42791 Meaning: A process is attempting to crawl out. The system
42792 discovered that the process was interrupted while
42793 its process directory was locked and has salvaged
42794 the process directory. Salvaging the process
42795 directory may delete critical process segments and
42796 cause the process to terminate so the process is
42797 terminated cleanly instead.
42798
42799 Action: No operator action is required. Message:
42800 verify_lock: COND condition by USER while
42801 salvaging directory.
42802
42803 Stream: $announce
42804
42805 Time: $salvt
42806
42807 Meaning: A fault occurred while salvaging a directory found
42808 locked at crawlout. This indicates a serious
42809 problem with the directory.
42810
42811 Action: Contact the system programming staff.
42812
42813
42814 truncate_vtoce.pl1
42815
42816
42817
42818 truncate_vtoce 739 08/21/20 MR12.7^L
42819
42820
42821 truncate_vtoce: attempt to destroy hc_sdw seg
42822 astep PPP
42823
42824
42825 Stream: BOS Typewriter Crashes system
42826
42827 Time: While system is running.
42828
42829 Meaning: An attempt has been made to truncate a supervisor
42830 segment. The AST entry is located at PPP. This
42831 indicates a logic error in the supervisor or CPU
42832 or memory hardware problems.
42833
42834 Action: Follow normal recovery procedures.
42835
42836
42837 tty_index.pl1
42838 tty_index: USER ACCESS_CLASS attempted invalid
42839 attachment of CHANNEL ACCESS_CLASS
42840
42841
42842 Stream: BOS Typewriter.
42843
42844 Time: While system is running.
42845
42846 Meaning: A process of USER with authorization
42847 ACCESS_CLASS attempted to use a communications
42848 channel which does not correspond to the user's
42849 authorization and the user does not have the
42850 communications privilege enabled. The request was
42851 refused. This may indicate a system error.
42852
42853 Action: Contact the system programming staff._ssa
42854
42855
42856 tty_interrupt.pl1
42857 tty_interrupt: unrecognized interrupt type N
42858 for devx D
42859
42860
42861 Stream: BOS Typewriter Crashes system
42862
42863 Time: While system is running.
42864
42865 Meaning: An unrecognized interrupt type has been reported
42866 for the nonmultiplexed channel whose device index
42867 is D.
42868
42869 Action: Contact the system programming staff.
42870
42871
42872 tty_lock.pl1
42873
42874
42875
42876 tty_lock$verify 740 08/21/20 MR12.7^L
42877
42878
42879 tty_lock$verify: attempted crawlout with queue
42880 lock set.
42881
42882
42883 Stream: BOS Typewriter Crashes system
42884
42885 Time: While system is running.
42886
42887 Meaning: There was an attempt to crawl out while the tty
42888 queue lock was locked.
42889
42890 Action: Contact the system programming staff.
42891
42892
42893 tty_lock.pl1
42894 tty_lock$verify: attempted crawlout with special
42895 channel lock set.
42896
42897
42898 Stream: BOS Typewriter Crashes system
42899
42900 Time: While system is running.
42901
42902 Meaning: There was an attempt to crawl out while a channel
42903 lock that is also a processor lock was locked.
42904
42905 Action: Contact the system programming staff.
42906
42907
42908 tty_lock.pl1
42909 tty_lock$verify: attempted crawlout with tty_buf
42910 lock set.
42911
42912
42913 Stream: BOS Typewriter Crashes system
42914
42915 Time: While system is running.
42916
42917 Meaning: There was an attempt to crawl out while the
42918 tty_buf lock used by tty_space_man was locked.
42919
42920 Action: Contact the system programming staff.
42921
42922
42923 tty_lock.pl1
42924 tty_lock: attempt to lock channel already locked
42925 by same process.
42926
42927
42928 Stream: BOS Typewriter Crashes system
42929
42930 Time: While system is running.
42931
42932
42933
42934 tty_lock 741 08/21/20 MR12.7^L
42935
42936
42937 Meaning: A locking error was detected when a process tried
42938 to lock a channel that it had already locked.
42939
42940 Action: Contact the system programming staff.
42941
42942
42943 tty_lock.pl1
42944 tty_lock: attempt to lock unused channel for
42945 interrupt.
42946
42947
42948 Stream: BOS Typewriter Crashes system
42949
42950 Time: While system is running.
42951
42952 Meaning: A locking error was detected when an interrupt
42953 handler tried to lock an ununsed channel.
42954
42955 Action: Contact the system programming staff.
42956
42957
42958 tty_lock.pl1
42959 tty_lock: attempt to unlock channel not locked by
42960 same process.
42961
42962
42963 Stream: BOS Typewriter Crashes system
42964
42965 Time: While system is running.
42966
42967 Meaning: A locking error was detected when a process tried
42968 to unlock a channel that was either not locked or
42969 locked by another process.
42970
42971 Action: Contact the system programming staff.
42972
42973
42974 tty_lock.pl1
42975 tty_lock: attempt to unlock queue not locked by
42976 same process.
42977
42978
42979 Stream: BOS Typewriter Crashes system
42980
42981 Time: While system is running.
42982
42983 Meaning: A locking error was detected when a process tried
42984 to unlock the global queue lock which was either
42985 not locked or was locked by another process.
42986
42987
42988
42989 tty_lock.pl1
42990
42991
42992 tty_lock 742 08/21/20 MR12.7^L
42993
42994
42995 tty_lock: Cannot get space for queue entry.
42996 devx = N
42997
42998
42999 Stream: BOS Typewriter sounds beeper
43000
43001 Time: While system is running.
43002
43003 Meaning: An attempt to queue an interrupt for the channel
43004 with devx N failed due to lack of space. The
43005 interrupt was lost which may cause loss of data or
43006 improper channel operation.
43007
43008 Action: Contact the system programming staff.
43009
43010
43011 tty_space_man.pl1
43012 tty_space_man: Address not in buffer pool.
43013
43014
43015 Stream: BOS Typewriter Crashes system
43016
43017 Time: While system is running.
43018
43019 Meaning: An attempt was made to free space at an address
43020 not included in the free space pool of tty_buf.
43021
43022 Action: Contact the system programming staff.
43023
43024
43025 tty_space_man.pl1
43026 tty_space_man: Lock already locked to process.
43027
43028
43029 Stream: BOS Typewriter Crashes system
43030
43031 Time: While system is running.
43032
43033 Meaning: A process that had the global tty_buf lock locked
43034 attempted to lock it again.
43035
43036 Action: Contact the system programming staff.
43037
43038
43039 tty_space_man.pl1
43040 tty_space_man: Lock not locked to process.
43041
43042
43043 Stream: BOS Typewriter Crashes system
43044
43045 Time: While system is running.
43046
43047
43048
43049
43050 tty_space_man 743 08/21/20 MR12.7^L
43051
43052
43053 Meaning: A process attempted to unlock the global tty_buf
43054 lock when that process did not have it locked.
43055
43056 Action: Contact the system programming staff.
43057
43058
43059 tty_space_man.pl1
43060 tty_space_man: Tried to free space already free.
43061
43062
43063 Stream: BOS Typewriter Crashes system
43064
43065 Time: While system is running.
43066
43067 Meaning: An attempt was made to free space in tty_buf that
43068 was included in or overlapped space that was
43069 already free.
43070
43071 Action: Contact the system programming staff.
43072
43073
43074 tty_tables_mgr.pl1
43075 tty_tables_mgr$add: Invalid table type. N
43076
43077
43078 Stream: BOS Typewriter Crashes system
43079
43080 Time: While system is running.
43081
43082 Meaning: An attempt to add a table to the tty_tables
43083 segment has failed due to an invalid table type of
43084 N.
43085
43086 Action: Contact the system programming staff.
43087
43088
43089 tty_tables_mgr.pl1
43090 tty_tables_mgr$delete: Invalid table offset. N
43091
43092
43093 Stream: BOS Typewriter Crashes system
43094
43095 Time: While system is running.
43096
43097 Meaning: An attempt to delete a table from the tty_tables
43098 segment has failed due to an invalid table offset
43099 of N.
43100
43101 Action: Contact the system programming staff.
43102
43103
43104 turn_on_mc_.pl1
43105 turn_on_mc_: MESSAGE. attach STREAM
43106
43107
43108 turn_on_mc_ 744 08/21/20 MR12.7^L
43109
43110
43111 Stream: sc error_output.
43112
43113 Time: System Intialization.
43114
43115 Meaning: The system attempted to start the Message
43116 Coordinator but the stream STREAM cannot be
43117 attached to the message routing dim. The system
43118 continues to operate but the Message Coordinator
43119 is not used. Probably the daemon processes will
43120 also encounter trouble.
43121
43122 Action: Contact the system programming staff.
43123
43124
43125 turn_on_mc_.pl1
43126 turn_on_mc_: MESSAGE. detach STREAM
43127
43128
43129 Stream: sc error_output.
43130
43131 Time: System Intialization.
43132
43133 Meaning: The system attempted to start the Message
43134 Coordinator but the stream STREAM could not be
43135 detached from its initial dim. The system
43136 continues to operate but the Message Coordinator
43137 is not used. Probably the daemon processes will
43138 also encounter trouble.
43139
43140 Action: Contact the system programming staff.
43141
43142
43143 turn_on_mc_.pl1
43144 turn_on_mc_: MESSAGE. error from mc_init
43145
43146
43147 Stream: sc error_output.
43148
43149 Time: System Intialization.
43150
43151 Meaning: The system attempted to start the Message
43152 Coordinator but it cannot be initialized. The
43153 system continues to operate but the Message
43154 Coordinator is not used. The daemon processes
43155 will probably also encounter trouble.
43156
43157 Action: Contact the system programming staff.
43158
43159
43160 turn_on_mc_.pl1
43161 turn_on_mc_: MESSAGE. open STREAM
43162
43163
43164
43165
43166 turn_on_mc_ 745 08/21/20 MR12.7^L
43167
43168
43169 Stream: sc error_output.
43170
43171 Time: System Intialization.
43172
43173 Meaning: The system attempted to start the Message
43174 Coordinator but the stream STREAM cannot be opened
43175 by the message routing dim. The system continues
43176 to operate but the Message Coordinator is not
43177 used. Probably the daemon processes will also
43178 encounter trouble.
43179
43180 Action: Contact the system programming staff.
43181
43182
43183 mc_commands_.pl1
43184 Unable to locate a CDT entry for XXXX while
43185 attempting to drop it.
43186
43187
43188 Stream: as severity 1
43189
43190 Time: In response to a drop operator command.
43191
43192 Meaning: Notification that the CDT entry cannot be found to
43193 free it as a result of dropping the tty channel
43194 from the message coordinator. The mc_anstbl entry
43195 is freed at this point however.
43196
43197 Action: No operator action is required.
43198
43199
43200 obs_reconfigure.pl1
43201 unlock: Reconfiguration data locked by
43202 PERSON.PROJ.T
43203
43204
43205 Stream: Initializer process output.
43206
43207 Time: In response to an operator command.
43208
43209 Meaning: This message is typed by reconfigure$force_unlock
43210 if the reconfiguration data base was locked.
43211
43212 Action: No operator action is required.
43213
43214
43215 obs_reconfigure.pl1
43216 unlock: Reconfiguration data not locked.
43217
43218
43219 Stream: Initializer process output.
43220
43221 Time: In response to an operator command.
43222
43223
43224 unlock 746 08/21/20 MR12.7^L
43225
43226
43227 Meaning: This message is typed by reconfigure$force_unlock
43228 if the reconfiguration data base was not locked.
43229
43230 Action: No operator action is required.
43231
43232
43233 dn355_boot_interrupt.pl1
43234 Unrecognized bootload status N for FNP X
43235
43236
43237 Stream: BOS Typewriter.
43238
43239 Time: When bootloading an FNP
43240
43241 Meaning: The status reported by an FNP in response to a
43242 bootload attempt was not one of the ones
43243 recognized. N is the reported status in octal.
43244
43245 Action: Contact the system programming staff.
43246
43247
43248 up_mgt_.pl1
43249 up_mgt_: ERROR_MESSAGE During work class
43250 reassignment
43251
43252
43253 Stream: as severity2
43254
43255 Time: While system is running.
43256
43257 Meaning: The error described by ERROR_MESSAGE occurred
43258 while a system administrator was attempting to
43259 install a new mgt. The operation was tried twice
43260 and failed both times. More detailed reasons for
43261 the failure are given in messages immediately
43262 preceding this one. The new mgt has been
43263 installed. Hardcore is operating with a set of
43264 parameters inconsistent with the new mgt.
43265
43266 Action: Contact the system programming staff._sa
43267
43268
43269 up_pdt_.pl1
43270 up_pdt_: bumping NAME.PROJ omitted from new pdt
43271
43272
43273 Stream: as severity1
43274
43275 Time: While system is running.
43276
43277 Meaning: The supervisor of project PROJ has removed the
43278 user named NAME from the project while he was
43279
43280
43281
43282 up_pdt_ 747 08/21/20 MR12.7^L
43283
43284
43285 logged in. He is no longer authorized to be
43286 logged in on that project and is bumped.
43287
43288 Action: No operator action is required.
43289
43290
43291 up_pdt_.pl1
43292 up_pdt_: bumping NAME.PROJ user authorization
43293 now outside range.
43294
43295
43296 Stream: as severity1
43297
43298 Time: While system is running.
43299
43300 Meaning: A project administrator has installed a new pdt
43301 that changes the authorization range for the user
43302 identified by NAME on project PROJ. The user
43303 NAME.PROJ is currently logged in with an
43304 authorization outside the new range. Therefore
43305 the user is being bumped from the system.
43306
43307 Action: No operator action is required.
43308
43309
43310 up_pdt_.pl1
43311 up_pdt_: ERROR_MESSAGE. PROJ.pdt will be
43312 installed with no hash table
43313
43314
43315 Stream: as severity2
43316
43317 Time: While system is running.
43318
43319 Meaning: A new PDT is being installed for project PROJ. An
43320 error described by ERROR_MESSAGE occurred while
43321 its hash table was being built. The PDT will be
43322 installed without a hash table. Logins on that
43323 project will take longer and place an extra load
43324 on the system.
43325
43326 Action: Contact the system programming staff.
43327
43328
43329 up_pdt_.pl1
43330 up_pdt_: PROJ.pdt has N users leaving
43331 insufficient room for a hash table.
43332
43333
43334 Stream: as severity1
43335
43336 Time: While system is running.
43337
43338
43339
43340 up_pdt_ 748 08/21/20 MR12.7^L
43341
43342
43343 Meaning: A new project definition table PDT for project
43344 PROJ is being installed. It has so many users
43345 that there is no room in it for a hash table. The
43346 PDT will be installed without a hash table.
43347 Logins on that project will take longer and place
43348 an extra load on the system.
43349
43350 Action: Contact the system programming staff.
43351
43352
43353 up_pdt_.pl1
43354 up_pdt_: PROJ.pdt NAME on free list state nonzero
43355
43356
43357 Stream: as severity2
43358
43359 Time: While system is running.
43360
43361 Meaning: A new project definition table for PROJ is being
43362 installed. The thread of free entries appears to
43363 include some user whose state is not zero. The
43364 program abandons the free chain and continues.
43365
43366 Action: Contact the system programming staff._sa
43367
43368
43369 up_pdt_.pl1
43370 up_pdt_: synch error NAME.PROJ
43371
43372
43373 Stream: as severity2
43374
43375 Time: While system is running.
43376
43377 Meaning: A new project definition table for PROJ is being
43378 installed. The answer table entry for NAME.PROJ
43379 should contain a pointer to the user's PDT entry
43380 but the pointer is incorrect. Accounting figures
43381 may be scrambled. The system continues operation.
43382
43383 Action: Contact the system programming staff._sa
43384
43385
43386 up_rtdt_.pl1
43387 up_rtdt_: Adding resource type RESOURCE_TYPE to
43388 the system.
43389
43390
43391 Stream: as severity1
43392
43393 Time: While system is running.
43394
43395
43396
43397
43398 up_rtdt_ 749 08/21/20 MR12.7^L
43399
43400
43401 Meaning: The named resource type has been newly defined and
43402 will be accessible by system users. This is an
43403 advisory message.
43404
43405 Action: None.
43406
43407
43408 up_rtdt_.pl1
43409 up_rtdt_: Deleting resource type RESOURCE_TYPE
43410 from the system.
43411
43412
43413 Stream: as severity1
43414
43415 Time: While system is running.
43416
43417 Meaning: The named resource type is no longer accessible by
43418 system users. This is an advisory message.
43419
43420 Action: None.
43421
43422
43423 up_rtdt_.pl1
43424 up_rtdt_: ERROR_MESSAGE Cannot create RCP
43425 registry for RESOURCE_NAME.
43426
43427
43428 Stream: as severity2
43429
43430 Time: While system is running.
43431
43432 Meaning: The error described by ERROR_MESSAGE occurred
43433 while a system administrator was attempting to
43434 install a new rtdt. The rtdt contained a new
43435 resource type but the resource management
43436 registry for that resource type could not be
43437 created. The rtdt is not installed. Some other
43438 registries may already have been modified
43439 according to information in the new rtdt.
43440
43441 Action: Notify the system administrator.
43442
43443
43444 up_rtdt_.pl1
43445 up_rtdt_: ERROR_MESSAGE Cannot recover by
43446 renaming old RTDT either.
43447
43448
43449 Stream: as severity2
43450
43451 Time: While system is running.
43452
43453
43454
43455
43456 up_rtdt_ 750 08/21/20 MR12.7^L
43457
43458
43459 Meaning: The program that installs rtdt's cannot recover
43460 correctly from an earlier error in renaming for
43461 which an error message is also printed. Although
43462 the current rtdt is not destroyed it is no longer
43463 accessible to users. This will affect the
43464 operation of resource management and RCP.
43465
43466 Action: Notify the system administrator.
43467
43468
43469 up_rtdt_.pl1
43470 up_rtdt_: ERROR_MESSAGE Cannot rename new rtdt.
43471
43472
43473 Stream: as severity2
43474
43475 Time: While system is running.
43476
43477 Meaning: The new rtdt being installed could not be renamed
43478 to "rtdt". The rtdt is not installed.
43479
43480 Action: Notify the system administrator.
43481
43482
43483 up_rtdt_.pl1
43484 up_rtdt_: ERROR_MESSAGE Cannot rename old RTDT.
43485
43486
43487 Stream: as severity2
43488
43489 Time: While system is running.
43490
43491 Meaning: The current rtdt could not be renamed to
43492 accomodate the installation of a new rtdt.
43493
43494 Action: Notify the system administrator.
43495
43496
43497 up_rtdt_.pl1
43498 up_rtdt_: ERROR_MESSAGE Cannot update RCP
43499 registry for RESOURCE_NAME.
43500
43501
43502 Stream: as severity2
43503
43504 Time: While system is running.
43505
43506 Meaning: The error described by ERROR_MESSAGE occurred
43507 while a system administrator was attempting to
43508 install a new rtdt. The rtdt contained changes to
43509 a resource type but the resource management
43510 registry for that resource type could not be
43511 modified. The rtdt is not installed. Some other
43512
43513
43514 up_rtdt_ 751 08/21/20 MR12.7^L
43515
43516
43517 registries may already have been modified
43518 according to information in the new rtdt.
43519
43520 Action: Notify the system administrator.
43521
43522
43523 up_sat_.pl1
43524 up_sat_: adding PROJ project with authorization
43525 AUTH
43526
43527
43528 Stream: as severity0
43529
43530 Time: While system is running.
43531
43532 Meaning: A system security administrator has added the
43533 project PROJ with an authorization greater than
43534 system low.
43535
43536 Action: No operator action is required.
43537
43538
43539 up_sat_.pl1
43540 up_sat_: bumping NAME.PROJ over max users on
43541 project
43542
43543
43544 Stream: as severity1
43545
43546 Time: While system is running.
43547
43548 Meaning: The user named has been bumped because the system
43549 administrator has reduced the maximum number of
43550 users that can be logged in on the project PROJ.
43551
43552 Action: No operator action is required.
43553
43554
43555 up_sat_.pl1
43556 up_sat_: bumping NAME.PROJ project authorization
43557 reduced
43558
43559
43560 Stream: as severity1
43561
43562 Time: While system is running.
43563
43564 Meaning: A system security administrator has installed a
43565 new SAT that reduces the authorization for the
43566 user identified by NAME on the project PROJ below
43567 the current value assigned to this project.
43568 Therefore the user is being bumped from the
43569 system.
43570
43571
43572 up_sat_ 752 08/21/20 MR12.7^L
43573
43574
43575 Action: No operator action is required.
43576
43577
43578 up_sat_.pl1
43579 up_sat_: bumping NAME.PROJ project deleted
43580
43581
43582 Stream: as severity1
43583
43584 Time: While system is running.
43585
43586 Meaning: The system administrator has deleted the project
43587 PROJ. All of its users are bumped.
43588
43589 Action: No operator action is required.
43590
43591
43592 up_sat_.pl1
43593 up_sat_: changing authorization of PROJ project
43594 from OLD to NEW
43595
43596
43597 Stream: as severity0
43598
43599 Time: While system is running.
43600
43601 Meaning: A system security administrator has installed a
43602 new SAT that changes the authorization of the
43603 project PROJ. OLD is the previous authorization
43604 for the project; NEW is the authorization now
43605 assigned to the project.
43606
43607 Action: No operator action is required.
43608
43609
43610 up_sat_.pl1
43611 up_sat_: ERROR_MESSAGE. cannot make temp
43612
43613
43614 Stream: as severity1
43615
43616 Time: While system is running.
43617
43618 Meaning: A temporary segment could not be created while
43619 attempting to install a new system administrator's
43620 table. The system attempts to proceed.
43621
43622 Action: Contact the system programming staff.
43623
43624
43625 up_sat_.pl1
43626 up_sat_: ERROR_MESSAGE. sat.ht
43627
43628
43629
43630 up_sat_ 753 08/21/20 MR12.7^L
43631
43632
43633 Stream: as severity2
43634
43635 Time: While system is running.
43636
43637 Meaning: The system was unable to replace the SAT hash
43638 table during installation of a new SAT. The new
43639 SAT has been installed but the old hash table is
43640 still in use so any new projects are unusable.
43641
43642 Action: Contact the system programming staff.
43643
43644
43645 up_sat_.pl1
43646 up_sat_: ERROR_MESSAGE. sat.ht.temp
43647
43648
43649 Stream: as severity2
43650
43651 Time: While system is running.
43652
43653 Meaning: A temporary segment could not be created while
43654 attempting to build a hash table for a new system
43655 administrator's table SAT. The new SAT has been
43656 installed but the old hash table is still in use
43657 so any new projects are unusable.
43658
43659 Action: Contact the system programming staff.
43660
43661
43662 up_sat_.pl1
43663 up_sat_: project PROJ on free list state nonzero
43664
43665
43666 Stream: as severity2
43667
43668 Time: While system is running.
43669
43670 Meaning: The free chain for the SAT seems to include a
43671 project that does not have state zero. The system
43672 abandons the free chain and attempts to proceed.
43673
43674 Action: Contact the system programming staff._sa
43675
43676
43677 up_sysctl_.pl1
43678 up_sysctl_$check_acs: MESSAGE. Unable to create
43679 PATHNAME.
43680
43681
43682 Stream: as severity1
43683
43684 Time: While system is running.
43685
43686
43687
43688 up_sysctl_$check_acs 754 08/21/20 MR12.7^L
43689
43690
43691 Meaning: The named segment does not exist and it was not
43692 possible to create it. Any table installations
43693 controlled by this segment will be ignored. The
43694 table submitted for installation will be deleted.
43695
43696 Action: Contact the system programming staff. Notify the
43697 system administrator. Normal servicing of table
43698 installations will not proceed until this
43699 situation is rectified.
43700
43701
43702
43703 up_sysctl_.pl1
43704 up_sysctl_$check_acs: PATHNAME not found. It
43705 will be created.
43706
43707
43708 Stream: as severity1
43709
43710 Time: While system is running.
43711
43712 Meaning: The named segment which controls a table
43713 installation operation does not exist. The
43714 segment will be created with an ACL allowing
43715 *.SysDaemon.* and *.SysAdmin.* to perform the
43716 appropriate table installation.
43717
43718 Action: Contact the system programming staff. The system
43719 administrator should be notified so that the ACL
43720 of the segment may be adjusted to reflect those
43721 users that may install the table.
43722
43723
43724
43725 up_sysctl_.pl1
43726 up_sysctl_$init: ERROR_MESSAGE. cannot
43727 find/create >system_control_1>update
43728
43729
43730 Stream: as severity2
43731
43732 Time: System Intialization.
43733
43734 Meaning: The directory used to update system tables is
43735 missing and cannot be created. No installations
43736 of new system tables cannot be done. Logins and
43737 logouts can go on as usual.
43738
43739 Action: Contact the system programming staff._sa
43740
43741
43742 up_sysctl_.pl1
43743
43744
43745
43746 up_sysctl_$init 755 08/21/20 MR12.7^L
43747
43748
43749 up_sysctl_$init: ERROR_MESSAGE. Cannot make IPC
43750 channel.
43751
43752
43753 Stream: as severity2
43754
43755 Time: System Intialization.
43756
43757 Meaning: It was not possible to establish the IPC channel
43758 which is used to allow users to indicate that an
43759 Answering Service table installation is to be
43760 performed. Installations will not occur.
43761
43762 Action: Contact the system programming staff._sa
43763
43764
43765 up_sysctl_.pl1
43766 up_sysctl_: CONDITION installing TABLE for USER
43767
43768
43769 Stream: as severity1
43770
43771 Time: While system is running.
43772
43773 Meaning: Some unexpected error occurred while installing a
43774 system table. An Answering Service dump was
43775 performed. Further attempts to install system
43776 tables may fail until a reset or force is done
43777 but logins and logouts should be able to proceed
43778 normally.
43779
43780 Action: Contact the system programming staff._sa
43781
43782
43783 up_sysctl_.pl1
43784 up_sysctl_: error - event calls were masked
43785
43786
43787 Stream: sc error_output
43788
43789 Time: While system is running.
43790
43791 Meaning: This indicates a logic error in the supervisor or
43792 CPU or memory hardware problems. The system
43793 attempts to recover and keep running.
43794
43795 Action: Contact the system programming staff.
43796
43797
43798 up_sysctl_.pl1
43799 up_sysctl_: Error: REASON
43800
43801
43802
43803
43804 up_sysctl_ 756 08/21/20 MR12.7^L
43805
43806
43807 Stream: as severity2
43808
43809 Time: While system is running.
43810
43811 Meaning: Some error occurred while installing a system
43812 table. An Answering Service dump was performed.
43813 Further attempts to install system tables may fail
43814 until a force or reset is done but logins and
43815 logouts should be able to proceed as usual.
43816
43817 Action: Contact the system programming staff._sa
43818
43819
43820 up_sysctl_.pl1
43821 up_sysctl_: installed TABLE for USERID
43822
43823
43824 Stream: as severity1
43825
43826 Time: While system is running.
43827
43828 Meaning: An mgt sat cdt pdt or rtdt has been installed.
43829
43830 Action: No operator action is required.
43831
43832
43833 up_sysctl_.pl1
43834 up_sysctl_: NAME wakeup with N installs pending
43835 up_sysctl_: NAME wakeup from PERSON.PROJECT with
43836 N installs pending
43837
43838
43839
43840 Stream: as severity0
43841
43842 Time: While system is running.
43843
43844 Meaning: A request to perform a table installation was
43845 received. There were N tables found ready for
43846 installation at the time of the wakeup. If N is
43847 0 the PERSON.PROJECT of the originator of the
43848 request is also logged. This message is normally
43849 severity0 but the administrator may cause it to
43850 be severity1.
43851
43852 Action: Contact the system programming staff. The
43853 administrator may request that he be notified if
43854 this occurs. If a large number of these messages
43855 are logged with N = 0 it may indicate that a user
43856 is harassing the installation mechanism.
43857
43858
43859
43860
43861
43862 up_sysctl_ 757 08/21/20 MR12.7^L
43863
43864
43865 up_sysctl_.pl1
43866 up_sysctl_: Unable to install TABLE for USERID.
43867 TEXT
43868
43869
43870 Stream: as severity1
43871
43872 Time: While system is running.
43873
43874 Meaning: The user USERID attempted to change the system
43875 table TABLE but something was wrong. The reason
43876 is given by TEXT.
43877
43878 Action: No operator action is required.
43879
43880
43881 up_sysctl_.pl1
43882 up_sysctl_: Unable to install TABLE for USERID.
43883 userid should be USERID1
43884
43885
43886 Stream: as severity1
43887
43888 Time: While system is running.
43889
43890 Meaning: A user attempted to install a system table by
43891 pretending to be some other user.
43892
43893 Action: Contact the system programming staff._sa
43894
43895
43896 validate_cpu_card.pl1
43897 validate_cpu_card: CPU cache size for CPU CPUTAG
43898 is incorrect should be "CACHE_SIZE."
43899
43900
43901 Stream: BOS Typewriter sounds beeper
43902
43903 Time: While system is running.
43904
43905 Meaning: The CACHE_SIZE as determined from cpu registers
43906 did not match the CACHE_SIZE in the cpu cache size
43907 field of the config card image for CPU CPUTAG.
43908
43909 Action: No operator action is required.
43910
43911
43912 validate_cpu_card.pl1
43913 validate_cpu_card: CPU model for CPU CPUTAG is
43914 incorrect should be "CPUMODEL."
43915
43916
43917 Stream: BOS Typewriter sounds beeper
43918
43919
43920 validate_cpu_card 758 08/21/20 MR12.7^L
43921
43922
43923 Time: While system is running.
43924
43925 Meaning: The CPUMODEL as determined from RSW 2
43926 information did not match the CPUMODEL in the cpu
43927 model field of the config card image for CPU
43928 CPUTAG.
43929
43930 Action: No operator action is required.
43931
43932
43933 validate_cpu_card.pl1
43934 validate_cpu_card: CPU type for CPU CPUTAG is
43935 incorrect should be "CPUTYPE"
43936
43937
43938 Stream: BOS Typewriter sounds beeper
43939
43940 Time: While system is running.
43941
43942 Meaning: The CPUTYPE as determined from RSW 2
43943 information did not match the CPUTYPE in the cpu
43944 type field of the config card image for CPU
43945 CPUTAG.
43946
43947 Action: No operator action is required.
43948
43949
43950 validate_cpu_card.pl1
43951 validate_cpu_card: CPU type model and/or cache
43952 size discrepencies will be corrected
43953
43954
43955 Stream: BOS Typewriter.
43956
43957 Time: While system is running.
43958
43959 Meaning: The indicated discrepencies in the cpu type
43960 model and cache size fields will be corrected by
43961 validate_cpu_card.
43962
43963 Action: The type model and/or cache size fields of the
43964 indicated cpu config card image should be
43965 corrected at BCE before the next bootload.
43966
43967
43968
43969 verify_lock.pl1
43970 verify_lock: block_lock_count XX should be 0
43971
43972
43973 Stream: BOS Typewriter Crashes system
43974
43975 Time: While system is running.
43976
43977
43978 verify_lock 759 08/21/20 MR12.7^L
43979
43980
43981 Meaning: A process has encountered a condition in ring 0
43982 and is in the process of attempting a crawlout.
43983 The system must unlock all locks before it
43984 performs the crawlout; all known locks have been
43985 unlocked but the process' lock counter is still
43986 nonzero. This indicates a logic error in the
43987 supervisor or CPU or memory hardware problems.
43988 BOS Typewriter Crashes systemes
43989
43990 Action: Follow normal recovery procedures.
43991
43992
43993 verify_lock.pl1
43994 verify_lock: Crawlout error on directory cleanup.
43995
43996
43997 Stream: BOS Typewriter Crashes system
43998
43999 Time: While system is running.
44000
44001 Meaning: A process encountered a signalled condition with
44002 one or more directories locked. Before the system
44003 causes a crawlout it unlocks and salvages all
44004 locked directories for the process. This process
44005 of cleanup encountered an unrecoverable error.
44006 BOS Typewriter Crashes systemes
44007
44008 Action: Follow normal recovery procedures.
44009
44010
44011 verify_lock.pl1
44012 verify_lock: Crawlout stop specified on PARM
44013 card.
44014
44015
44016 Stream: BOS Typewriter Crashes system
44017
44018 Time: While system is running.
44019
44020 Meaning: The system PARM card specified the CRWL parameter.
44021 A process is attempting to crawl out. This
44022 message will occur so that system programmers can
44023 take a dump.
44024
44025 Action: Take a dump. Issuing the BCE go command will
44026 cause the system to continue.
44027
44028
44029
44030 verify_lock.pl1
44031 verify_lock: Crawlout while in directory
44032 salvager dir UIDPTR.
44033
44034
44035
44036 verify_lock 760 08/21/20 MR12.7^L
44037
44038
44039 Stream: Logged in SYSERR log.
44040
44041 Time: While system is running.
44042
44043 Meaning: A process faulted while salvaging a dir on
44044 crawlout.
44045
44046 Action: No operator action is required.
44047
44048
44049 verify_lock.pl1
44050 verify_lock: Crawlout while masked.
44051
44052
44053 Stream: BOS Typewriter Crashes system
44054
44055 Time: While system is running.
44056
44057 Meaning: BOS Typewriter Crashes systemes
44058
44059 Action: Contact the system programming staff.
44060
44061
44062 verify_lock.pl1
44063 verify_lock: Crawlout with AST lock set.
44064
44065
44066 Stream: BOS Typewriter Crashes system
44067
44068 Time: While system is running.
44069
44070 Meaning: A user process encountered a condition while
44071 processing with the AST locked. This condition
44072 may have been due to a hardware or software
44073 failure. BOS Typewriter Crashes systemes
44074
44075 Action: Follow normal recovery procedures.
44076
44077
44078 verify_lock.pl1
44079 verify_lock: dir.modify PPPP WWWW ^^= processid.
44080
44081
44082 Stream: BOS Typewriter Crashes system
44083
44084 Time: While system is running.
44085
44086 Meaning: A process is attempting to crawl out. The system
44087 has discovered that a directory which is marked
44088 locked to the process has its "modify" field not
44089 equal to the processid of the process. This
44090 indicates a logic error in the supervisor or CPU
44091
44092
44093
44094 verify_lock 761 08/21/20 MR12.7^L
44095
44096
44097 or memory hardware problems. BOS Typewriter
44098 Crashes systemes
44099
44100 Action: Follow normal recovery procedures.
44101
44102
44103 verify_lock.pl1
44104 verify_lock: Force unlocked Volmap lock dskX_NN
44105 on crawlout for PERSON.PROJECT.TAG
44106
44107
44108 Stream: Logged in SYSERR log.
44109
44110 Time: While system is running.
44111
44112 Meaning: The Volmap Lock for the device indicated was found
44113 locked to a process on crawlout. The lock has
44114 been reset and the count of volume
44115 inconsistencies for the device has been
44116 incremented by one.
44117
44118 Action: Any free records or VTOCEs lost because of the
44119 crawlout can be recovered by a volume salvage.
44120
44121
44122
44123 verify_lock.pl1
44124 verify_lock: Force unlocked VTOC Map lock
44125 dskX_NN on crawlout for PERSON.PROJECT.TAG
44126
44127
44128 Stream: Logged in SYSERR log.
44129
44130 Time: While system is running.
44131
44132 Meaning: The VTOC Map lock for the device indicated was
44133 found locked to the process on crawlout. The lock
44134 has been reset and the count of volume
44135 inconsistencies has been incremented by one.
44136
44137 Action: Any free records or VTOCEs lost because of the
44138 crawlout can be recovered by a volume salvage.
44139
44140
44141
44142 verify_lock.pl1
44143 verify_lock: more than N directory locks locked
44144 to process.
44145
44146
44147 Stream: BOS Typewriter Crashes system
44148
44149 Time: While system is running.
44150
44151
44152 verify_lock 762 08/21/20 MR12.7^L
44153
44154
44155 Meaning: The process held more dir locks than verify lock
44156 could store for later salvaging. This indicates a
44157 logic error in the supervisor.
44158
44159 Action: BOS Typewriter Crashes systemes Follow normal
44160 recovery procedures.
44161
44162
44163
44164 verify_lock.pl1
44165 verify_lock: NAME condition by PERS.PROJ
44166
44167
44168 Stream: Logged in SYSERR log.
44169
44170 Time: While system is running.
44171
44172 Meaning: User PERS.PROJ encountered a NAME condition in
44173 ring 0. The system attempts to unlock and reset
44174 all ring 0 data bases locked by the process.
44175
44176 Action: These messages almost always indicate benign
44177 errors in the supervisor. They should be
44178 reported nonetheless. They are accompanied by
44179 the binary machine condition information. This
44180 message is logged only when the condition occured
44181 while some ring-0 lock was set. One or more
44182 messages preceeding this one will indicate which
44183 locks were held by the process and forcibly reset.
44184
44185
44186
44187 verify_lock.pl1
44188 verify_lock: Salvaging dir PTR UID on crawlout.
44189
44190
44191 Stream: Logged in SYSERR log.
44192
44193 Time: While system is running.
44194
44195 Meaning: This message is displayed for each directory found
44196 locked on a crawlout. The online salvager will be
44197 called and the directory unlocked.
44198
44199 Action: No operator action is required.
44200
44201
44202 verify_lock.pl1
44203 verify_lock: Unlocked LOCK.
44204
44205
44206 Stream: Logged in SYSERR log.
44207
44208
44209
44210 verify_lock 763 08/21/20 MR12.7^L
44211
44212
44213 Time: While system is running.
44214
44215 Meaning: The lock LOCK was found locked at crawlout and
44216 unlocked.
44217
44218 Action: No operator action is required.
44219
44220
44221 verify_lock.pl1
44222 verify_lock: Unlocking dir UUUUUUUUUUUU. Locked
44223 for READ_OR_WRITE salvage.
44224
44225
44226 Stream: Logged in SYSERR log.
44227
44228 Time: While system is running.
44229
44230 Meaning: The directory with UID UUUUUUUUUUUU was found
44231 locked at crawl-out time. It is salvaged and then
44232 unlocked.
44233
44234 Action: Contact the system programming staff.
44235
44236
44237 vm_vio.pl1
44238 vm_vio: get_vtocep: invalid pvtx: PPPo
44239
44240
44241 Stream: BOS Typewriter.
44242
44243 Time: Volume salvaging or disk rebuilding.
44244
44245 Meaning: The Volume Salvager virtual access package has
44246 been given a bad PVT index parameter PPP shown
44247 in octal. This indicates a logic error in the
44248 supervisor or CPU or memory hardware problems.
44249
44250 Action: Salvaging will not proceed. $boot_tape
44251
44252
44253
44254 vm_vio.pl1
44255 vm_vio: get_vtocep: invalid vtocx VVVo on pvtx
44256 PPPo
44257
44258
44259 Stream: BOS Typewriter.
44260
44261 Time: Volume salvaging or disk rebuilding.
44262
44263 Meaning: An out-of-range VTOC index VVV has been given to
44264 the Volume Salvager virtual access package while
44265 processing PV at pvtx PPP. The vtocx and pvtx are
44266
44267
44268 vm_vio 764 08/21/20 MR12.7^L
44269
44270
44271 shown in octal. This indicates a logic error in
44272 the supervisor or CPU or memory hardware
44273 problems.
44274
44275 Action: Salvaging may fail. Note for system programmer
44276 action.
44277
44278
44279
44280 vm_vio.pl1
44281 vm_vio: no AST pointer at readahead.
44282
44283
44284 Stream: BOS Typewriter Crashes system
44285
44286 Time: Volume salvaging or disk rebuilding.
44287
44288 Meaning: No AST entry pointer was found for a
44289 VTOC-addressing segment used by the Volume
44290 Salvager virtual access package. This indicates a
44291 logic error in the supervisor or CPU or memory
44292 hardware problems.
44293
44294 Action: Follow normal recovery procedures. Note for
44295 system programmer action.
44296
44297
44298
44299 page_error.alm
44300 volmap: Attempt to deposit in-use address YYYYYY
44301 on dskX_NNS.
44302
44303
44304 Stream: BOS Typewriter.
44305
44306 Time: While system is running.
44307
44308 Meaning: An attempt was made to return disk address YYYYYY
44309 to the free pool on dskX_NNS but the address
44310 was already marked as free. This indicates damage
44311 of some sort to the Volume Map. This damage can
44312 be repaired by a volume salvage.
44313
44314 Action: Contact the system programming staff.
44315
44316
44317 page_error.alm
44318 volmap: Attempt to deposit in-use address YYYYYY
44319 on dskX_NNS.
44320
44321
44322 Stream: BOS Typewriter.
44323
44324
44325
44326 volmap 765 08/21/20 MR12.7^L
44327
44328
44329 Time: While system is running.
44330
44331 Meaning: An attempt was made to return disk address YYYYYY
44332 to the free pool on dskX_NNS but the address
44333 was already marked as free. This indicates damage
44334 of some sort to the Volume Map. This damage can
44335 be repaired by a volume salvage.
44336
44337 Action: Contact the system programming staff.
44338
44339
44340 page_error.alm
44341 volmap: Invalid Volume Map address computation
44342 for YYYYYY on dskX_NNS.
44343
44344
44345 Stream: BOS Typewriter Crashes system
44346
44347 Time: While system is running.
44348
44349 Meaning: In attempting to place the disk address YYYYYY
44350 into the free pool for dskX_NNS an error
44351 occurred in translating the address into a
44352 location within the Volume Map. This indicates a
44353 software error.
44354
44355
44356
44357 page_error.alm
44358 volmap: Invalid Volume Map address computation
44359 for YYYYYY on dskX_NNS.
44360
44361
44362 Stream: BOS Typewriter Crashes system
44363
44364 Time: While system is running.
44365
44366 Meaning: In attempting to place the disk address YYYYYY
44367 into the free pool for dskX_NNS an error
44368 occurred in translating the address into a
44369 location within the Volume Map. This indicates a
44370 software error.
44371
44372
44373
44374 page_error.alm
44375 volmap: Invalid volume map word on dskX_NNS.
44376
44377
44378 Stream: BOS Typewriter Crashes system
44379
44380 Time: While system is running.
44381
44382
44383
44384 volmap 766 08/21/20 MR12.7^L
44385
44386
44387 Meaning: An attempt to withdraw a disk address from the
44388 pool of free addresses on dskX_NNS resulted in
44389 finding a volume map word with at least one of
44390 bits 0 33 34 and 35 on. These bits are invalid
44391 for volume map words. This indicates hardware or
44392 software failure.
44393
44394 Action: Perform an ESD. Reboot the system and perform a
44395 volume salvage not a scavenge of the disk volume
44396 dskX_NNS. This may be performed at Initializer
44397 ring-1 or ring-4 command level. Perform the
44398 salvage before adding the storage system volume
44399 back to the system. The volume scavenger will not
44400 detect volume map words with invalid bits enabled
44401 so the salvager must be used. Once the salvage is
44402 complete the volume may be added back to the
44403 system.
44404
44405
44406
44407 page_error.alm
44408 volmap: Invalid volume map word on dskX_NNS.
44409
44410
44411 Stream: BOS Typewriter Crashes system
44412
44413 Time: While system is running.
44414
44415 Meaning: An attempt to withdraw a disk address from the
44416 pool of free addresses on dskX_NNS resulted in
44417 finding a volume map word with at least one of
44418 bits 0 33 34 and 35 on. These bits are invalid
44419 for volume map words. This indicates hardware or
44420 software failure.
44421
44422 Action: Perform an ESD. Reboot the system and perform a
44423 volume salvage not a scavenge of the disk volume
44424 dskX_NNS. This may be performed at Initializer
44425 ring-1 or ring-4 command level. Perform the
44426 salvage before adding the storage system volume
44427 back to the system. The volume scavenger will not
44428 detect volume map words with invalid bits enabled
44429 so the salvager must be used. Once the salvage is
44430 complete the volume may be added back to the
44431 system.
44432
44433
44434
44435 page_error.alm
44436 volmap: record stock inconsistent on dskX_NNS.
44437 stockp=YYY|YYYYY.
44438
44439
44440
44441
44442 volmap 767 08/21/20 MR12.7^L
44443
44444
44445 Stream: BOS Typewriter Crashes system
44446
44447 Time: While system is running.
44448
44449 Meaning: An attempt to deposit a record address from the
44450 Volume Map to the record stock failed
44451 unaccountably. This indicates probably software
44452 failure.
44453
44454 Action: Follow normal recovery procedures.
44455
44456
44457 page_error.alm
44458 volmap: record stock inconsistent on dskX_NNS.
44459 stockp=YYY|YYYYY.
44460
44461
44462 Stream: BOS Typewriter Crashes system
44463
44464 Time: While system is running.
44465
44466 Meaning: An attempt to deposit a record address from the
44467 Volume Map to the record stock failed
44468 unaccountably. This indicates probably software
44469 failure.
44470
44471 Action: Follow normal recovery procedures.
44472
44473
44474 page_error.alm
44475 volmap: Volume Map inconsistent on dskX_NNS.
44476
44477
44478 Stream: BOS Typewriter Crashes system
44479
44480 Time: While system is running.
44481
44482 Meaning: An attempt to withdraw a disk address from the
44483 pool of free addresses on dskX_NNS failed
44484 although the control structures describing the
44485 Volume Map indicated that addresses were
44486 available. This indicates hardware or software
44487 failure.
44488
44489 Action: Follow normal recovery procedures.
44490
44491
44492 page_error.alm
44493 volmap: Volume Map inconsistent on dskX_NNS.
44494
44495
44496 Stream: BOS Typewriter Crashes system
44497
44498
44499
44500 volmap 768 08/21/20 MR12.7^L
44501
44502
44503 Time: While system is running.
44504
44505 Meaning: An attempt to withdraw a disk address from the
44506 pool of free addresses on dskX_NNS failed
44507 although the control structures describing the
44508 Volume Map indicated that addresses were
44509 available. This indicates hardware or software
44510 failure.
44511
44512 Action: Follow normal recovery procedures.
44513
44514
44515 page_error.alm
44516 volmap_page: Async error for dskX_NNS.
44517
44518
44519 Stream: BOS Typewriter Crashes system
44520
44521 Time: While system is running.
44522
44523 Meaning: When attempting to write an updated page of the
44524 Volume Map on dskX_NNS it was found not to be
44525 in memory. This indicates a software failure.
44526
44527 Action: Follow normal recovery procedures.
44528
44529
44530 page_error.alm
44531 volmap_page: Async error for dskX_NNS.
44532
44533
44534 Stream: BOS Typewriter Crashes system
44535
44536 Time: While system is running.
44537
44538 Meaning: When attempting to write an updated page of the
44539 Volume Map on dskX_NNS it was found not to be
44540 in memory. This indicates a software failure.
44541
44542 Action: Follow normal recovery procedures.
44543
44544
44545 page_error.alm
44546 volmap_page: Async state on dskX_NNS changed to
44547 S on poll.
44548
44549
44550 Stream: Logged in SYSERR log.
44551
44552 Time: While system is running.
44553
44554 Meaning: An interrupt for a volume map I/O was lost and was
44555 recovered by a periodic polling routine.
44556
44557
44558 volmap_page 769 08/21/20 MR12.7^L
44559
44560
44561 Action: No operator action is required.
44562
44563
44564 page_error.alm
44565 volmap_page: Async state on dskX_NNS changed to
44566 S on poll.
44567
44568
44569 Stream: Logged in SYSERR log.
44570
44571 Time: While system is running.
44572
44573 Meaning: An interrupt for a volume map I/O was lost and was
44574 recovered by a periodic polling routine.
44575
44576 Action: No operator action is required.
44577
44578
44579 page_error.alm
44580 volmap_page: Invalid async state on dskX_NNS.
44581
44582
44583 Stream: BOS Typewriter Crashes system
44584
44585 Time: While system is running.
44586
44587 Meaning: An inconsistency was discovered in the
44588 asynchronous update state of the Volume Map on
44589 dskX_NNS. This is likely a software error.
44590
44591 Action: Follow normal recovery procedures.
44592
44593
44594 page_error.alm
44595 volmap_page: Invalid async state on dskX_NNS.
44596
44597
44598 Stream: BOS Typewriter Crashes system
44599
44600 Time: While system is running.
44601
44602 Meaning: An inconsistency was discovered in the
44603 asynchronous update state of the Volume Map on
44604 dskX_NNS. This is likely a software error.
44605
44606 Action: Follow normal recovery procedures.
44607
44608
44609 page_error.alm
44610 volmap_page: Invalid call.
44611
44612
44613 Stream: BOS Typewriter Crashes system
44614
44615
44616 volmap_page 770 08/21/20 MR12.7^L
44617
44618
44619 Time: While system is running.
44620
44621 Meaning: One of the conditions required for a call to a
44622 volmap_page entry point was not present. This
44623 indicates a software failure in the caller of
44624 volmap_page.
44625
44626 Action: Follow normal recovery procedures.
44627
44628
44629 page_error.alm
44630 volmap_page: Invalid call.
44631
44632
44633 Stream: BOS Typewriter Crashes system
44634
44635 Time: While system is running.
44636
44637 Meaning: One of the conditions required for a call to a
44638 volmap_page entry point was not present. This
44639 indicates a software failure in the caller of
44640 volmap_page.
44641
44642 Action: Follow normal recovery procedures.
44643
44644
44645 page_error.alm
44646 volmap_page: PTL not locked to process.
44647
44648
44649 Stream: BOS Typewriter Crashes system
44650
44651 Time: While system is running.
44652
44653 Meaning: An entry in volmap_page was called which required
44654 that the Global Page Table lock be held by the
44655 calling process. It was not held by that process
44656 indicating software failure.
44657
44658 Action: Follow normal recovery procedures.
44659
44660
44661 page_error.alm
44662 volmap_page: PTL not locked to process.
44663
44664
44665 Stream: BOS Typewriter Crashes system
44666
44667 Time: While system is running.
44668
44669 Meaning: An entry in volmap_page was called which required
44670 that the Global Page Table lock be held by the
44671
44672
44673
44674 volmap_page 771 08/21/20 MR12.7^L
44675
44676
44677 calling process. It was not held by that process
44678 indicating software failure.
44679
44680 Action: Follow normal recovery procedures.
44681
44682
44683 page_error.alm
44684 volmap_page: Unrecoverable I/O error on Volmap
44685 page M of dskX_NNS. Addresses lost.
44686
44687
44688 Stream: BOS Typewriter sounds beeper
44689
44690 Time: While system is running.
44691
44692 Meaning: There was an unrecoverable I/O on a page of the
44693 Volume Map which describes free records on the
44694 volume. As a result all free records described
44695 by that page of the Volume Map have been lost.
44696
44697 Action: It may be possible to recover the lost addresses
44698 by a volume salvage. However a hard device error
44699 will prevent the volume salvage from succeeding.
44700 In this case it will be necessary to recover the
44701 volume to a good pack.
44702
44703
44704
44705 page_error.alm
44706 volmap_page: Unrecoverable I/O error on Volmap
44707 page M of dskX_NNS. Addresses lost.
44708
44709
44710 Stream: BOS Typewriter sounds beeper
44711
44712 Time: While system is running.
44713
44714 Meaning: There was an unrecoverable I/O on a page of the
44715 Volume Map which describes free records on the
44716 volume. As a result all free records described
44717 by that page of the Volume Map have been lost.
44718
44719 Action: It may be possible to recover the lost addresses
44720 by a volume salvage. However a hard device error
44721 will prevent the volume salvage from succeeding.
44722 In this case it will be necessary to recover the
44723 volume to a good pack.
44724
44725
44726
44727 volmap_util.pl1
44728 volmap_util: Address XXXXXX out of paging region
44729 on dskX_NN.
44730
44731
44732 volmap_util 772 08/21/20 MR12.7^L
44733
44734
44735 Stream: BOS Typewriter Crashes system
44736
44737 Time: During a physical volume scavenge
44738
44739 Meaning: The scavenger attempted to remove an invalid
44740 address from the volume map.
44741
44742 Action: Follow normal recovery procedures.
44743
44744
44745 volmap_util.pl1
44746 volmap_util: Address XXXXXX out of paging region
44747 on dskX_NN.
44748
44749
44750 Stream: BOS Typewriter Crashes system
44751
44752 Time: During a physical volume scavenge
44753
44754 Meaning: The scavenger attempted to remove an invalid
44755 address from the volume map.
44756
44757 Action: Follow normal recovery procedures.
44758
44759
44760 volmap_util.pl1
44761 volmap_util: Invalid address XXXXXX on dskX_NN.
44762
44763
44764 Stream: BOS Typewriter Crashes system
44765
44766 Time: During a physical volume scavenge
44767
44768 Meaning: In attempting to deposit address XXXXXX on device
44769 dskX_NN an invalid volume map offset was
44770 computed.
44771
44772 Action: Follow normal recovery procedures.
44773
44774
44775 volmap_util.pl1
44776 volmap_util: Invalid address XXXXXX on dskX_NN.
44777
44778
44779 Stream: BOS Typewriter Crashes system
44780
44781 Time: During a physical volume scavenge
44782
44783 Meaning: In attempting to deposit address XXXXXX on device
44784 dskX_NN an invalid volume map offset was
44785 computed.
44786
44787 Action: Follow normal recovery procedures.
44788
44789
44790 volume 773 08/21/20 MR12.7^L
44791
44792
44793
44794
44795 init_disk_pack_.pl1
44796 volume PVNAME XX records
44797
44798
44799 Stream: Initializer process output.
44800
44801 Time: In response to an operator command.
44802
44803 Meaning: The physical volume PVNAME has been successfully
44804 initialized. There are XX decimal records in
44805 the paging area.
44806
44807 Action: No operator action is required.
44808
44809
44810 volume_registration_mgr_.pl1
44811 volume_registration_mgr_$add_lvr: Added new LV
44812 "LVNAME". GROUP_ID
44813
44814
44815 Stream: Logged in SYSERR log.
44816
44817 Time: While system is running.
44818
44819 Meaning: A new storage system logical volume has been
44820 registered on the system.
44821
44822 Action: No operator action is required.
44823
44824
44825 volume_registration_mgr_.pl1
44826 volume_registration_mgr_$add_lvr: Added new PV
44827 "PVNAME" to LV "LVNAME". GROUP_ID
44828
44829
44830 Stream: Logged in SYSERR log.
44831
44832 Time: While system is running.
44833
44834 Meaning: A new storage system physical volume has been
44835 registered on the system.
44836
44837 Action: No operator action is required.
44838
44839
44840 volume_registration_mgr_.pl1
44841 volume_registration_mgr_$add_lvr: Could not
44842 append link for LV name | LVID | PV name | PVID.
44843 GROUP_ID ERROR_MESSAGE
44844
44845
44846
44847
44848 volume_registration_mgr_$add_lvr^H774 08/21/20 MR12.7^L
44849
44850
44851 Stream: BOS Typewriter.
44852
44853 Time: While system is running.
44854
44855 Meaning: A link could not be added into >lv whose target is
44856 a database segment located under the root
44857 directory. Future database references may not be
44858 possible.
44859
44860 Action: Contact the system programming staff.
44861
44862
44863 volume_registration_mgr_.pl1
44864 volume_registration_mgr_$add_lvr: Unable to back
44865 out database "lv.LVNAME". GROUP_ID
44866 ERROR_MESSAGE
44867
44868
44869 Stream: BOS Typewriter.
44870
44871 Time: While system is running.
44872
44873 Meaning: When attempting to register a new logical volume
44874 some error occurred. The entry then attempted to
44875 remove the database segment just created. This
44876 removal failed.
44877
44878 Action: Contact the system programming staff.
44879
44880
44881 volume_registration_mgr_.pl1
44882 volume_registration_mgr_$add_pvr: Added new PV
44883 "PVNAME" to LV "LVNAME". GROUP_ID -log-
44884
44885
44886 Stream: Logged in SYSERR log.
44887
44888 Time: While system is running.
44889
44890 Meaning: A new storage system physical volume has been
44891 registered on the system.
44892
44893 Action: No operator action is required.
44894
44895
44896 volume_registration_mgr_.pl1
44897 volume_registration_mgr_$add_pvr: Could not
44898 append link for PV name| PVID. GROUP_ID
44899 ERROR_MESSAGE
44900
44901
44902 Stream: BOS Typewriter.
44903
44904
44905
44906 volume_registration_mgr_$add_pvr^H775 08/21/20 MR12.7^L
44907
44908
44909 Time: While system is running.
44910
44911 Meaning: A link could not be added into >lv whose target is
44912 a database segment located under the root
44913 directory. Future database references may not be
44914 possible.
44915
44916 Action: Contact the system programming staff.
44917
44918
44919 volume_registration_mgr_.pl1
44920 volume_registration_mgr_$add_pvr: Extra PV entry
44921 "PVNAME" in database "lv.LVNAME". GROUP_ID
44922
44923
44924 Stream: BOS Typewriter.
44925
44926 Time: While system is running.
44927
44928 Meaning: This indicates a logic error in the supervisor or
44929 CPU or memory hardware problems. An entry for the
44930 specified PV was found in the database segment for
44931 the specified LV where no segment addname
44932 indicated its existance.
44933
44934 Action: Contact the system programming staff.
44935
44936
44937 volume_registration_mgr_.pl1
44938 volume_registration_mgr_$add_pvr: Unable to back
44939 out database addname "pv.PVNAME". GROUP_ID
44940 ERROR_MESSAGE
44941
44942
44943 Stream: BOS Typewriter.
44944
44945 Time: While system is running.
44946
44947 Meaning: An error occurred while registering a new PV. The
44948 entry attmpts to undo all work up to the point of
44949 the error. In this case it was unable to undo
44950 its manipulations and left a spurious addname
44951 "pv.PVNAME" on the database segment.
44952
44953 Action: Contact the system programming staff.
44954
44955
44956 volume_registration_mgr_.pl1
44957 volume_registration_mgr_$change_lvr: Changed ACS
44958 pathname for LV "LVNAME" to "PATH". GROUP_ID
44959
44960
44961 Stream: Logged in SYSERR log.
44962
44963
44964 volume_registration_mgr_$change_^H7l^H7v^H6r 08/21/20 MR12.7^L
44965
44966
44967 Time: While system is running.
44968
44969 Meaning: The registered ACS pathname of a storage system
44970 logical volume has been changed as indicated.
44971
44972 Action: No operator action is required.
44973
44974
44975 volume_registration_mgr_.pl1
44976 volume_registration_mgr_$change_lvr: Changed LV
44977 "LVNAME" to PRIVATE | PUBLIC. GROUP_ID
44978
44979
44980 Stream: Logged in SYSERR log.
44981
44982 Time: While system is running.
44983
44984 Meaning: The access type of the specified logical volume
44985 has been changed.
44986
44987 Action: No operator action is required.
44988
44989
44990 volume_registration_mgr_.pl1
44991 volume_registration_mgr_$change_lvr: Changed LVID
44992 of LV "LVNAME" from "LVID1" to "LVID2".
44993 GROUP_ID
44994
44995
44996 Stream: Logged in SYSERR log.
44997
44998 Time: While system is running.
44999
45000 Meaning: The registered logical volume unique ID has been
45001 changed for the specified LV.
45002
45003 Action: No operator action is required.
45004
45005
45006 volume_registration_mgr_.pl1
45007 volume_registration_mgr_$change_lvr: Changed name
45008 of LV "LVNAME1" to "LVNAME2". GROUP_ID
45009
45010
45011 Stream: Logged in SYSERR log.
45012
45013 Time: While system is running.
45014
45015 Meaning: The registered name of a storage system logical
45016 volume has been changed as indicated.
45017
45018 Action: No operator action is required.
45019
45020
45021
45022 volume_registration_mgr_$change_^H7l^H7v^H7r 08/21/20 MR12.7^L
45023
45024
45025
45026
45027 volume_registration_mgr_.pl1
45028 volume_registration_mgr_$change_lvr: Changed
45029 owner of LV "LVNAME" from "Person1.Project1" to
45030 "Person2.Project2". GROUP_ID
45031
45032
45033 Stream: Logged in SYSERR log.
45034
45035 Time: While system is running.
45036
45037 Meaning: The owner of a storage system logical volume has
45038 been changed as indicated.
45039
45040 Action: No operator action is required.
45041
45042
45043 volume_registration_mgr_.pl1
45044 volume_registration_mgr_$change_lvr: Changed max
45045 | min access class of LV "LVNAME" from
45046 "AUTH_STR1" to "AUTH_STR2". GROUP_ID
45047
45048
45049 Stream: Logged in SYSERR log.
45050
45051 Time: While system is running.
45052
45053 Meaning: The access class of a storage system logical
45054 volume has been changed as indicated.
45055
45056 Action: No operator action is required.
45057
45058
45059 volume_registration_mgr_.pl1
45060 volume_registration_mgr_$change_lvr: Couldn't
45061 delete | create link for old | new LV name |
45062 LVID. GROUP_ID ERROR_MESSAGE
45063
45064
45065 Stream: BOS Typewriter.
45066
45067 Time: While system is running.
45068
45069 Meaning: A link for the specified database segment residing
45070 under the root directory could not be created in
45071 >lv.
45072
45073 Action: Contact the system programming staff.
45074
45075
45076 volume_registration_mgr_.pl1
45077 volume_registration_mgr_$change_lvr: Unable to
45078
45079
45080 volume_registration_mgr_$change_^H7l^H7v^H8r 08/21/20 MR12.7^L
45081
45082
45083 back out LVID change to "LVNAME.mdcs". GROUP_ID
45084 ERROR_MESSAGE
45085
45086
45087 Stream: BOS Typewriter.
45088
45089 Time: While system is running.
45090
45091 Meaning: This indicates a logic error in the supervisor or
45092 CPU or memory hardware problems. While changing
45093 attributes of the logical volume LVNAME an error
45094 was encountered. The entry then attempted to
45095 remove some changes already made to the
45096 registration database. In this case it could not
45097 remove the LVID change to the master directory
45098 control database LVNAME.mdcs.
45099
45100 Action: Contact the system programming staff.
45101
45102
45103 volume_registration_mgr_.pl1
45104 volume_registration_mgr_$change_lvr: Unable to
45105 change name "lv.LVNAME1" back to "lv.LVNAME2"
45106 GROUP_ID ERROR_MESSAGE
45107
45108
45109 Stream: BOS Typewriter.
45110
45111 Time: While system is running.
45112
45113 Meaning: This indicates a logic error in the supervisor or
45114 CPU or memory hardware problems. While changing
45115 attributes ot the logical volume LVNAME an error
45116 was encountered. The entry then attempted to
45117 remove some changes already made to the
45118 registration database. In this case it could not
45119 remove theLV name change.
45120
45121 Action: Contact the system programming staff.
45122
45123
45124 volume_registration_mgr_.pl1
45125 volume_registration_mgr_$change_lvr: Unable to
45126 change name "lvid.UNIQUE1" back to "lvid.UNIQUE2".
45127 GROUP_ID ERROR_MESSAGE
45128
45129
45130 Stream: BOS Typewriter.
45131
45132 Time: While system is running.
45133
45134 Meaning: This indicates a logic error in the supervisor or
45135 CPU or memory hardware problems. While changing
45136
45137
45138 volume_registration_mgr_$change_^H7l^H7v^H9r 08/21/20 MR12.7^L
45139
45140
45141 attributes ot the logical volume LVNAME an error
45142 was encountered. The entry then attempted to
45143 remove some changes already made to the
45144 registration database. In this case it could not
45145 remove LVID name change.
45146
45147 Action: Contact the system programming staff.
45148
45149
45150 volume_registration_mgr_.pl1
45151 volume_registration_mgr_$change_lvr: Unable to
45152 convert max | min auth to name_string.
45153 GROUP_ID ERROR_MESSAGE
45154
45155
45156 Stream: BOS Typewriter.
45157
45158 Time: While system is running.
45159
45160 Meaning: This indicates a logic error in the supervisor or
45161 CPU or memory hardware problems. A binary
45162 authorization string could not be converted to its
45163 readable representation.
45164
45165 Action: Contact the system programming staff.
45166
45167
45168 volume_registration_mgr_.pl1
45169 volume_registration_mgr_$change_lvr: Unexpected
45170 error changing name on "lv.LVNAME". GROUP_ID
45171 ERROR_MESSAGE
45172
45173
45174 Stream: BOS Typewriter.
45175
45176 Time: While system is running.
45177
45178 Meaning: This indicates a logic error in the supervisor or
45179 CPU or memory hardware problems. An unexpected
45180 error occured while changing the name on an LV
45181 registration data segment. The message explains
45182 the trouble.
45183
45184 Action: Contact the system programming staff.
45185
45186
45187 volume_registration_mgr_.pl1
45188 volume_registration_mgr_$change_lvr: Unexpected
45189 trouble changing name "lvid.UNIQUE". GROUP_ID
45190 ERROR_MESSAGE
45191
45192
45193 Stream: BOS Typewriter.
45194
45195
45196 volume_registration_mgr_$change_^H7l^H8v^H0r 08/21/20 MR12.7^L
45197
45198
45199 Time: While system is running.
45200
45201 Meaning: This indicates a logic error in the supervisor or
45202 CPU or memory hardware problems. An unexpected
45203 error occured while changing the name on an LV
45204 registration data segment. The message explains
45205 the trouble.
45206
45207 Action: Contact the system programming staff.
45208
45209
45210 volume_registration_mgr_.pl1
45211 volume_registration_mgr_$change_pvr: Changed
45212 date_registered of PV "PVNAME" from "DT1" to
45213 "DT2". GROUP_ID
45214
45215
45216 Stream: Logged in SYSERR log.
45217
45218 Time: While system is running.
45219
45220 Meaning: The registered date for the specified PV has been
45221 changed as indicated.
45222
45223 Action: No operator action is required.
45224
45225
45226 volume_registration_mgr_.pl1
45227 volume_registration_mgr_$change_pvr: Changed
45228 location of PV "PVNAME" from "LOC1" to "LOC2".
45229 GROUP_ID
45230
45231
45232 Stream: Logged in SYSERR log.
45233
45234 Time: While system is running.
45235
45236 Meaning: The registered location of the specified PV has
45237 been changed as indicated.
45238
45239 Action: No operator action is required.
45240
45241
45242 volume_registration_mgr_.pl1
45243 volume_registration_mgr_$change_pvr: Changed
45244 mfg_serial of PV "PVNAME" from "STR1" to "STR2".
45245 GROUP_ID
45246
45247
45248 Stream: Logged in SYSERR log.
45249
45250 Time: While system is running.
45251
45252
45253
45254 volume_registration_mgr_$change_^H7p^H8v^H1r 08/21/20 MR12.7^L
45255
45256
45257 Meaning: The registered serial of the specified PV has been
45258 changed as indicated.
45259
45260 Action: No operator action is required.
45261
45262
45263 volume_registration_mgr_.pl1
45264 volume_registration_mgr_$change_pvr: Changed
45265 model of PV "PVNAME" from "TYPE1" to "TYPE2".
45266 GROUP_ID
45267
45268
45269 Stream: Logged in SYSERR log.
45270
45271 Time: While system is running.
45272
45273 Meaning: The registered model number of the specified PV
45274 has been changed as indicated.
45275
45276 Action: No operator action is required.
45277
45278
45279 volume_registration_mgr_.pl1
45280 volume_registration_mgr_$change_pvr: Changed name
45281 of PV "PVNAME1" to "PVNAME2". GROUP_ID
45282
45283
45284 Stream: Logged in SYSERR log.
45285
45286 Time: While system is running.
45287
45288 Meaning: The registered name of the specified PV has been
45289 changed as indicated.
45290
45291 Action: No operator action is required.
45292
45293
45294 volume_registration_mgr_.pl1
45295 volume_registration_mgr_$change_pvr: Changed
45296 password of PV "PVNAME". GROUP_ID
45297
45298
45299 Stream: Logged in SYSERR log.
45300
45301 Time: While system is running.
45302
45303 Meaning: The registered password of the specified PV has
45304 been changed as indicated.
45305
45306 Action: No operator action is required.
45307
45308
45309 volume_registration_mgr_.pl1
45310
45311
45312 volume_registration_mgr_$change_^H7p^H8v^H2r 08/21/20 MR12.7^L
45313
45314
45315 volume_registration_mgr_$change_pvr: Changed PVID
45316 of PV "PVNAME" from "PVID1" to "PVID2" GROUP_ID
45317
45318
45319 Stream: Logged in SYSERR log.
45320
45321 Time: While system is running.
45322
45323 Meaning: The registered physical volume unique IFD has been
45324 changed as indicated.
45325
45326 Action: No operator action is required.
45327
45328
45329 volume_registration_mgr_.pl1
45330 volume_registration_mgr_$change_pvr: Couldn't
45331 delete | create link for old | new PV name |
45332 PVID. GROUP_ID ERROR_MESSAGE
45333
45334
45335 Stream: BOS Typewriter.
45336
45337 Time: While system is running.
45338
45339 Meaning: A link for a database segment residing in the root
45340 directory could not be created in >lv. This may
45341 make some registration data inaccessible.
45342
45343 Action: Contact the system programming staff.
45344
45345
45346 volume_registration_mgr_.pl1
45347 volume_registration_mgr_$change_pvr: PV entry
45348 missing from database "pv.PVNAME". GROUP_ID
45349
45350
45351 Stream: BOS Typewriter.
45352
45353 Time: While system is running.
45354
45355 Meaning: This indicates a logic error in the supervisor or
45356 CPU or memory hardware problems. An entry for the
45357 specified PV could not be found in the data
45358 segment although an addname for that PV exists on
45359 the segment entry.
45360
45361 Action: Contact the system programming staff.
45362
45363
45364 volume_registration_mgr_.pl1
45365 volume_registration_mgr_$change_pvr: Unable to
45366 back out PVID change. GROUP_ID ERROR_MESSAGE
45367
45368
45369
45370 volume_registration_mgr_$change_^H7p^H8v^H3r 08/21/20 MR12.7^L
45371
45372
45373 Stream: BOS Typewriter.
45374
45375 Time: While system is running.
45376
45377 Meaning: While making changes to the registered PV
45378 attributes an error was encountered. The module
45379 attempts to remove any work already done on other
45380 attributes. For reasons given in ERROR_MESSAGE
45381 the PVID change could not be removed.
45382
45383 Action: Contact the system programming staff.
45384
45385
45386 volume_registration_mgr_.pl1
45387 volume_registration_mgr_$change_pvr: Unexpected
45388 trouble changing name "pv.PVNAME". GROUP_ID
45389 ERROR_MESSAGE
45390
45391
45392 Stream: BOS Typewriter.
45393
45394 Time: While system is running.
45395
45396 Meaning: While making changes to the registered PV
45397 attributes an error was encountered. The module
45398 attempts to remove any work already done on other
45399 attributes. For reasons given in ERROR_MESSAGE
45400 the PV name change could not be removed.
45401
45402 Action: Contact the system programming staff.
45403
45404
45405 volume_registration_mgr_.pl1
45406 volume_registration_mgr_$change_pvr: Unexpected
45407 trouble changing name "pvid.UNIQUE". GROUP_ID
45408 ERROR_MESSAGE
45409
45410
45411 Stream: BOS Typewriter.
45412
45413 Time: While system is running.
45414
45415 Meaning: An unexpected state made the program unable to
45416 change the database name associated with the PV
45417 unique ID.
45418
45419 Action: Contact the system programming staff.
45420
45421
45422 volume_registration_mgr_.pl1
45423 volume_registration_mgr_$check_volume_registration:
45424 ERROR_MESSAGE. PATH
45425
45426
45427
45428 volume_registration_mgr_$check_v^H7o^H84^Hlume_registrat^H08^Hio^H/n^H21/20 MR12.7^L
45429
45430
45431 Stream: BOS Typewriter.
45432
45433 Time: System Intialization.
45434
45435 Meaning: An error occurred when trying to reclassify a new
45436 lv.** seg as a multi-class system segment.
45437
45438 Action: Contact the system programming staff.
45439
45440
45441 volume_registration_mgr_.pl1
45442 volume_registration_mgr_$check_volume_registration:
45443 Code N. lv.LVNAME disagreed with disk_table. It
45444 was rebuilt.
45445
45446
45447 Stream: BOS Typewriter.
45448
45449 Time: System Intialization.
45450
45451 Meaning: When the system is bootloaded it checks the list
45452 of packs which were mounted during the last
45453 bootload to make sure that each one has a valid
45454 logical and physical volume registration. The
45455 registration file lv.LVNAME was found but
45456 disagreed with the disk_table_ and so it was
45457 corrected. The meaning of the codes can be
45458 determined from the listing of
45459 volume_registration_mgr_; it is rarely important.
45460
45461 Action: Use list_vol_registration to examine the remade
45462 registration and correct it with
45463 change_vol_registration if necessary.
45464
45465
45466
45467 volume_registration_mgr_.pl1
45468 volume_registration_mgr_$check_volume_registration:
45469 ERROR_MESSAGE. Cannot add SysAdmin access to >lv.
45470
45471
45472 Stream: BOS Typewriter.
45473
45474 Time: System Intialization.
45475
45476 Meaning: After creating a new >lv directory an attempt is
45477 made to add "sma" access for *.SysAdmin.*. This
45478 failed.
45479
45480 Action: Contact the system programming staff.
45481
45482
45483 volume_registration_mgr_.pl1
45484
45485
45486 volume_registration_mgr_$check_v^H7o^H85^Hlume_registrat^H08^Hio^H/n^H21/20 MR12.7^L
45487
45488
45489 volume_registration_mgr_$check_volume_registration:
45490 ERROR_MESSAGE. Cannot make mdcs for LVNAME
45491
45492
45493 Stream: BOS Typewriter.
45494
45495 Time: System Intialization.
45496
45497 Meaning: When the system is bootloaded it checks the list
45498 of packs which were mounted during the last
45499 bootload to make sure that each one has a valid
45500 logical and physical volume registration. An
45501 error occurred while reconstructing LVNAME.mdcs.
45502 Operation on master directories for LVNAME may
45503 encounter problems.
45504
45505 Action: Contact the system programming staff._sa
45506
45507
45508 volume_registration_mgr_.pl1
45509 volume_registration_mgr_$check_volume_registration:
45510 ERROR_MESSAGE. cannot re-create >lv
45511
45512
45513 Stream: BOS Typewriter.
45514
45515 Time: System Intialization.
45516
45517 Meaning: When the system is bootloaded it checks the list
45518 of packs which were mounted during the last
45519 bootload to make sure that each one has a valid
45520 logical and physical volume registration. If the
45521 registration does not exist the registration
45522 files are reconstructed. These registration files
45523 reside in the directory >lv which is also remade
45524 if it was lost or did not exist.
45525
45526 This message indicates that there is a problem in
45527 re-creating >lv. Other error messages will follow
45528 and reregistration will fail.
45529
45530 Action: Contact the system programming staff.
45531
45532
45533 volume_registration_mgr_.pl1
45534 volume_registration_mgr_$check_volume_registration:
45535 ERROR_MESSAGE. Cannot reregister lv LVNAME
45536
45537
45538 Stream: BOS Typewriter.
45539
45540 Time: System Intialization.
45541
45542
45543
45544 volume_registration_mgr_$check_v^H7o^H86^Hlume_registrat^H08^Hio^H/n^H21/20 MR12.7^L
45545
45546
45547 Meaning: When the system is bootloaded it checks the list
45548 of packs which were mounted during the last
45549 bootload to make sure that each one has a valid
45550 logical and physical volume registration.
45551
45552 The system was unable to append a branch for
45553 >lv>lv.LVNAME. The logical volume will have to be
45554 re-registered manually.
45555
45556 Action: Use the add_vol_registration command to
45557 re-register the volume manually.
45558
45559
45560
45561 volume_registration_mgr_.pl1
45562 volume_registration_mgr_$check_volume_registration:
45563 ERROR_MESSAGE. Cannot reregister pv PVNAME
45564
45565
45566 Stream: BOS Typewriter.
45567
45568 Time: System Intialization.
45569
45570 Meaning: When the system is bootloaded it checks the list
45571 of packs which were mounted during the last
45572 bootload to make sure that each one has a valid
45573 logical and physical volume registration.
45574
45575 The system was unable to re-register the physical
45576 volume PVNAME because its logical volume entry
45577 could not be located in the old disk_table and its
45578 physical volume registration file could not be
45579 found. The volume will have to be re-registered
45580 manually.
45581
45582 Action: If PVNAME is garbage ignore this message.
45583 Otherwise use add_vol_registration to re-register
45584 the volume.
45585
45586
45587
45588 volume_registration_mgr_.pl1
45589 volume_registration_mgr_$check_volume_registration:
45590 ERROR_MESSAGE. Cant add name lvid.UNIQUE to
45591 lv.LVNAME
45592
45593
45594 Stream: BOS Typewriter.
45595
45596 Time: System Intialization.
45597
45598 Meaning: When the system is bootloaded it checks the list
45599 of packs which were mounted during the last
45600
45601
45602 volume_registration_mgr_$check_v^H7o^H87^Hlume_registrat^H08^Hio^H/n^H21/20 MR12.7^L
45603
45604
45605 bootload to make sure that each one has a valid
45606 logical and physical volume registration. The
45607 registration file for LVNAME did not have the
45608 additional name constructed from the volume unique
45609 ID and an error was discovered trying to add it.
45610 If this name is on another segment confusion will
45611 result.
45612
45613 Action: Contact the system programming staff. Enter admin
45614 mode and do a "list >lv>**" command.
45615
45616
45617
45618 volume_registration_mgr_.pl1
45619 volume_registration_mgr_$check_volume_registration:
45620 ERROR_MESSAGE. Cant add name pv.PVNAME to LVNAME
45621
45622
45623 Stream: BOS Typewriter.
45624
45625 Time: System Intialization.
45626
45627 Meaning: When the system is bootloaded it checks the list
45628 of packs which were mounted during the last
45629 bootload to make sure that each one has a valid
45630 logical and physical volume registration.
45631
45632 An error occurred adding the name pv.PVNAME to
45633 >lv>lv.LVNAME. If this name is missing or on
45634 another segment confusion will result.
45635
45636 Action: Contact the system programming staff. Enter admin
45637 mode and do a "list >lv>**" command.
45638
45639
45640
45641 volume_registration_mgr_.pl1
45642 volume_registration_mgr_$check_volume_registration:
45643 ERROR_MESSAGE. Cant add name pvid.UNIQUE to
45644 LVNAME
45645
45646
45647 Stream: BOS Typewriter.
45648
45649 Time: System Intialization.
45650
45651 Meaning: When the system is bootloaded it checks the list
45652 of packs which were mounted during the last
45653 bootload to make sure that each one has a valid
45654 logical and physical volume registration. An
45655 error occurred adding the name pvid.UNIQUE to
45656 >lv>lv.LVNAME. If this name is missing or is on
45657 another segment confusion will result.
45658
45659
45660 volume_registration_mgr_$check_v^H7o^H88^Hlume_registrat^H08^Hio^H/n^H21/20 MR12.7^L
45661
45662
45663 Action: Contact the system programming staff. Enter admin
45664 mode and do a "list >lv>**" command.
45665
45666
45667
45668 volume_registration_mgr_.pl1
45669 volume_registration_mgr_$check_volume_registration:
45670 ERROR_MESSAGE. Putting LV dir on RPV
45671
45672
45673 Stream: BOS Typewriter.
45674
45675 Time: System Intialization.
45676
45677 Meaning: When the system is bootloaded it checks the list
45678 of packs which were mounted during the last
45679 bootload to make sure that each one has a valid
45680 logical and physical volume registration. While
45681 re-creating >lv the system attempted to set the
45682 directory flag which means "RPV only" and failed
45683 to do so.
45684
45685 Action: Contact the system programming staff.
45686
45687
45688 volume_registration_mgr_.pl1
45689 volume_registration_mgr_$check_volume_registration:
45690 Registration for PVNAME was different from
45691 disk_table
45692
45693
45694 Stream: BOS Typewriter.
45695
45696 Time: System Intialization.
45697
45698 Meaning: When the system is bootloaded it checks the list
45699 of packs which were mounted during the last
45700 bootload to make sure that each one has a valid
45701 logical and physical volume registration. The
45702 physical volume ID or model number of PVNAME was
45703 wrong in the registration files and was corrected.
45704
45705 Action: Contact the system programming staff._sa
45706
45707
45708 volume_registration_mgr_.pl1
45709 volume_registration_mgr_$check_volume_registration:
45710 Reregistered pv PVNAME pvid WWWW in lv LVNAME
45711
45712
45713 Stream: BOS Typewriter.
45714
45715 Time: System Intialization.
45716
45717
45718 volume_registration_mgr_$check_v^H7o^H89^Hlume_registrat^H08^Hio^H/n^H21/20 MR12.7^L
45719
45720
45721 Meaning: When the system is bootloaded it checks the list
45722 of packs which were mounted during the last
45723 bootload to make sure that each one has a valid
45724 logical and physical volume registration.
45725 Registration for PVNAME was added to the
45726 registration file for LVNAME.
45727
45728 This message is always produced for the root
45729 physical volume rpv during a cold boot of the
45730 Multics hierarchy.
45731
45732 Action: Use the list_vol_registration command to check the
45733 registration. If necessary correct it with
45734 change_vol_registration.
45735
45736
45737
45738 volume_registration_mgr_.pl1
45739 volume_registration_mgr_$check_volume_registration:
45740 Reregistered TYPE lv LVNAME lvid WWWW
45741
45742
45743 Stream: BOS Typewriter.
45744
45745 Time: System Intialization.
45746
45747 Meaning: When the system is bootloaded it checks the list
45748 of packs which were mounted during the last
45749 bootload to make sure that each one has a valid
45750 logical and physical volume registration. The
45751 registration file for LVNAME did not exist and was
45752 reconstructed.
45753
45754 This message is always produced for the root
45755 logical volume during a cold boot of the Multics
45756 hierarchy.
45757
45758 Action: Use the list_vol_registration command to list the
45759 registration and check it against the re-created
45760 copy. Correct it with change_vol_registration if
45761 necessary.
45762
45763
45764
45765 volume_registration_mgr_.pl1
45766 volume_registration_mgr_$delete_lvr: Could not
45767 remove PV name | PVID | LV name | LVID database
45768 link. GROUP_ID ERROR_MESSAGE
45769
45770
45771 Stream: BOS Typewriter.
45772
45773 Time: While system is running.
45774
45775
45776 volume_registration_mgr_$delete_^H7l^H9v^H0r 08/21/20 MR12.7^L
45777
45778
45779 Meaning: An unexpected state prevented the program from
45780 removing the database links associated with an LV
45781 just deleted. The links in >lv should be
45782 removed by hand using Ring_1_Repair.
45783
45784 Action: Contact the system programming staff.
45785
45786
45787 volume_registration_mgr_.pl1
45788 volume_registration_mgr_$delete_lvr: Deleted LV
45789 "LVNAME". GROUP_ID
45790
45791
45792 Stream: Logged in SYSERR log.
45793
45794 Time: While system is running.
45795
45796 Meaning: The registration for the spcified logical volume
45797 has been removed.
45798
45799 Action: No operator action is required.
45800
45801
45802 volume_registration_mgr_.pl1
45803 volume_registration_mgr_$delete_lvr: Deleted PV
45804 "PVNAME" from LV "LVNAME". GROUP_ID
45805
45806
45807 Stream: Logged in SYSERR log.
45808
45809 Time: While system is running.
45810
45811 Meaning: The registration for the specified physical volume
45812 was removed while removing the entire logical
45813 volume registration.
45814
45815 Action: No operator action is required.
45816
45817
45818 volume_registration_mgr_.pl1
45819 volume_registration_mgr_$delete_lvr: Unable to
45820 delete MDCS "LVNAME.mdcs". GROUP_ID
45821 ERROR_MESSAGE
45822
45823
45824 Stream: BOS Typewriter.
45825
45826 Time: While system is running.
45827
45828 Meaning: After deleting the registration for a logical
45829 volume the module was unable to delete the
45830 corresponding master directory control database
45831 indicated in the message.
45832
45833
45834 volume_registration_mgr_$delete_^H7l^H9v^H1r 08/21/20 MR12.7^L
45835
45836
45837 Action: Contact the system programming staff.
45838
45839
45840 volume_registration_mgr_.pl1
45841 volume_registration_mgr_$delete_pvr: Could not
45842 remove PV name | PVID database link. GROUP_ID
45843 ERROR_MESSAGE
45844
45845
45846 Stream: BOS Typewriter.
45847
45848 Time: While system is running.
45849
45850 Meaning: An unexpected state prevented the removal of
45851 database links associated with a PV registration
45852 that was just deleted. The links should be
45853 deleted by hand using Ring_1_Repair.
45854
45855 Action: Contact the system programming staff.
45856
45857
45858 volume_registration_mgr_.pl1
45859 volume_registration_mgr_$delete_pvr: Deleted PV
45860 "PVNAME" from LV "LVNAME". GROUP_ID
45861
45862
45863 Stream: Logged in SYSERR log.
45864
45865 Time: While system is running.
45866
45867 Meaning: The registration fo the specified PV has been
45868 deleted.
45869
45870 Action: No operator action is required.
45871
45872
45873 volume_registration_mgr_.pl1
45874 volume_registration_mgr_$delete_pvr: PV entry
45875 missing from database "pv.PVNAME". GROUP_ID
45876
45877
45878 Stream: BOS Typewriter.
45879
45880 Time: While system is running.
45881
45882 Meaning: This indicates a logic error in the supervisor or
45883 CPU or memory hardware problems. The entry for
45884 the specified PV could not be located in the
45885 database segment although its name appears on the
45886 segment entry.
45887
45888 Action: Contact the system programming staff.
45889
45890
45891
45892 volume_registration_mgr_$delete_^H7p^H9v^H2r 08/21/20 MR12.7^L
45893
45894
45895
45896
45897 volume_registration_mgr_.pl1
45898 volume_registration_mgr_$delete_pvr: Trimming
45899 registration. GROUP_ID ERROR_MESSAGE
45900
45901
45902 Stream: BOS Typewriter.
45903
45904 Time: While system is running.
45905
45906 Meaning: An unexpected state prevented the trimming of a
45907 registration database segment. This will not
45908 hinder subsystem performance.
45909
45910 Action: Contact the system programming staff.
45911
45912
45913 volume_registration_mgr_.pl1
45914 volume_registration_mgr_$delete_pvr: Unable to
45915 replace database name "pv.PVNAME". GROUP_ID
45916 ERROR_MESSAGE
45917
45918
45919 Stream: BOS Typewriter.
45920
45921 Time: While system is running.
45922
45923 Meaning: This indicates a logic error in the supervisor or
45924 CPU or memory hardware problems. While deleting
45925 the registration for the specified PV an error
45926 occurred. The program attempts to undo any
45927 changes to "leave things as they were." The
45928 attempt to put back the database segment name as
45929 indicated failed.
45930
45931 Action: Contact the system programming staff.
45932
45933
45934 volume_registration_mgr_.pl1
45935 volume_registration_mgr_$ENTRY: Attempting to get
45936 second temp segment. GROUP_ID
45937
45938
45939 Stream: BOS Typewriter.
45940
45941 Time: While system is running.
45942
45943 Meaning: This indicates a logic error in the supervisor or
45944 CPU or memory hardware problems. All entrypoints
45945 to volume_registration_mgr_ require at most one
45946 temporary segment.
45947
45948
45949
45950 volume_registration_mgr_$ENTRY 793 08/21/20 MR12.7^L
45951
45952
45953 Action: Contact the system programming staff.
45954
45955
45956 volume_registration_mgr_.pl1
45957 volume_registration_mgr_$ENTRY: Database -
45958 lvid.UNIQUE | lv.LVNAME | pvid.UNIQUE |
45959 pv.PVNAME. GROUP_ID Segment already known to
45960 process.
45961
45962
45963 Stream: BOS Typewriter.
45964
45965 Time: While system is running.
45966
45967 Meaning: This indicates a logic error in the supervisor or
45968 CPU or memory hardware problems. The inner ring
45969 module always trerminates references to the
45970 database segments upon return to its caller. It
45971 found the specified segment already initiated upon
45972 entry to the specified routine.
45973
45974 Action: Contact the system programming staff.
45975
45976
45977 volume_registration_mgr_.pl1
45978 volume_registration_mgr_$ENTRY: Unable to release
45979 temp segment. GROUP_ID ERROR_MESSAGE
45980
45981
45982 Stream: BOS Typewriter.
45983
45984 Time: While system is running.
45985
45986 Meaning: This indicates a logic error in the supervisor or
45987 CPU or memory hardware problems. Some unexpected
45988 state is preventing the module from releasing its
45989 temporary segment.
45990
45991 Action: Contact the system programming staff.
45992
45993
45994 volume_registration_mgr_.pl1
45995 volume_registration_mgr_$ENTRY: Unable to
45996 terminate database reference. GROUP_ID
45997 ERROR_MESSAGE
45998
45999
46000 Stream: BOS Typewriter.
46001
46002 Time: While system is running.
46003
46004 Meaning: This indicates a logic error in the supervisor or
46005 CPU or memory hardware problems. Some unexpected
46006
46007
46008 volume_registration_mgr_$ENTRY 794 08/21/20 MR12.7^L
46009
46010
46011 state is preventing the module from terminating
46012 reference to a database segment.
46013
46014 Action: Contact the system programming staff.
46015
46016
46017 volume_registration_mgr_.pl1
46018 volume_registration_mgr_$ENTRY: Unexpected error
46019 occurred. Database may be in an inconsistant
46020 state. GROUP_ID
46021
46022
46023 Stream: BOS Typewriter.
46024
46025 Time: While system is running.
46026
46027 Meaning: This indicates a logic error in the supervisor or
46028 CPU or memory hardware problems. Some unexpected
46029 condition was signalled while the module was
46030 executing.
46031
46032 Action: Contact the system programming staff.
46033
46034
46035 volume_registration_mgr_.pl1
46036 volume_registration_mgr_$find: PV entry missing
46037 from "pv.PVNAME". GROUP_ID
46038
46039
46040 Stream: BOS Typewriter.
46041
46042 Time: While system is running.
46043
46044 Meaning: This indicates a logic error in the supervisor or
46045 CPU or memory hardware problems. The entry for
46046 the specified PV could not be found in the
46047 registration database segment although the name
46048 appears on the segment's entry.
46049
46050 Action: Contact the system programming staff.
46051
46052
46053 volume_registration_mgr_.pl1
46054 volume_registration_mgr_$find_volname: PV entry
46055 not found in database "pvid.UNIQUE". GROUP_ID
46056
46057
46058 Stream: BOS Typewriter.
46059
46060 Time: While system is running.
46061
46062 Meaning: This indicates a logic error in the supervisor or
46063 CPU or memory hardware problems. The entry for
46064
46065
46066 volume_registration_mgr_$find_vo^H7l^H95^Hname 08/21/20 MR12.7^L
46067
46068
46069 the specified PV could not be found in the
46070 registration database segment although the name
46071 appears on the segment's entry.
46072
46073 Action: Contact the system programming staff.
46074
46075
46076 volume_registration_mgr_.pl1
46077 volume_registration_mgr_$get_access: ACS not
46078 segment - "PATH". GROUP_ID
46079
46080
46081 Stream: BOS Typewriter.
46082
46083 Time: While system is running.
46084
46085 Meaning: The ACS indicated in the logical volume
46086 registration database is not a segment. The
46087 database entry should be corrected using
46088 "change_volume_registration".
46089
46090 Action: Contact the system programming staff._sa
46091
46092
46093 volume_registration_mgr_.pl1
46094 volume_registration_mgr_$get_access: Bad ACS path
46095 in database "lv.LVNAME". GROUP_ID ERROR_MESSAGE
46096
46097
46098 Stream: BOS Typewriter.
46099
46100 Time: While system is running.
46101
46102 Meaning: This indicates a logic error in the supervisor or
46103 CPU or memory hardware problems. The ACS pathname
46104 entry in the LVNAME database is illegal. This
46105 should not happen normally because the ring-1
46106 primitives check all paths before entering them
46107 into the database.
46108
46109 Action: Contact the system programming staff.
46110
46111
46112 volume_registration_mgr_.pl1
46113 volume_registration_mgr_$pvname_info: PV entry
46114 not found in database "pv.PVNAME". GROUP_ID
46115
46116
46117 Stream: BOS Typewriter.
46118
46119 Time: While system is running.
46120
46121
46122
46123
46124 volume_registration_mgr_$pvname_^H79^Hin^H6fo 08/21/20 MR12.7^L
46125
46126
46127 Meaning: This indicates a logic error in the supervisor or
46128 CPU or memory hardware problems. The entry for
46129 the specified PV could not be found in the
46130 registration database segment although the name
46131 appears on the segment's entry.
46132
46133 Action: Contact the system programming staff.
46134
46135
46136 volume_registration_mgr_.pl1
46137 volume_registration_mgr_$read_pvr: PV entry
46138 missing from database "pv.PVNAME". GROUP_ID
46139
46140
46141 Stream: BOS Typewriter.
46142
46143 Time: While system is running.
46144
46145 Meaning: This indicates a logic error in the supervisor or
46146 CPU or memory hardware problems. The entry for
46147 the specified PV could not be found in the
46148 registration database segment although the name
46149 appears on the segment's entry.
46150
46151 Action: Contact the system programming staff.
46152
46153
46154 vrm_lock_.pl1
46155 vrm_lock_$lock: LOCK ERROR MESSAGE.
46156
46157
46158 Stream: Logged in SYSERR log.
46159
46160 Time: While system is running.
46161
46162 Meaning: A logical volume registration operation failed
46163 because of a problem with the vrm control lock.
46164
46165 Action: No operator action is required.
46166
46167
46168 vrm_lock_.pl1
46169 vrm_lock_$unlock: LOCK ERROR MESSAGE.
46170
46171
46172 Stream: Logged in SYSERR log.
46173
46174 Time: While system is running.
46175
46176 Meaning: At the completion ofa logical volume registratin
46177 operation some error occured unlocking the vrm
46178 control lock.
46179
46180
46181
46182 vrm_lock_$unlock 797 08/21/20 MR12.7^L
46183
46184
46185 Action: No operator action is required.
46186
46187
46188 vrm_lock_.pl1
46189 vrm_lock_$vrm_data_init: Unable to create
46190 PATHNAME. REASON.
46191
46192
46193 Stream: BOS Typewriter.
46194
46195 Time: System Intialization.
46196
46197 Meaning: Logical volume registration control vrm was
46198 unable to create the segment PATHNAME to be used
46199 for the vrm control lock for the REASON given.
46200 Subsequent logical volume registration control
46201 operations may fail.
46202
46203 Action: No operator action is required.
46204
46205
46206 vrm_lock_.pl1
46207 vrm_lock_$vrm_data_init: Unable to reclassify
46208 PATHNAME. REASON.
46209
46210
46211 Stream: BOS Typewriter.
46212
46213 Time: System Intialization.
46214
46215 Meaning: Logical volume registration control was unable to
46216 reclassify the segment PATHNAME to its proper
46217 access class for the REASON given. This segment
46218 is to be used for the logical volume registration
46219 control lock. Subsequent logical volume
46220 registration control operations may fail.
46221
46222
46223
46224 vrm_lock_.pl1
46225 vrm_lock_$vrm_data_init: Unable to truncate
46226 PATHNAME. REASON.
46227
46228
46229 Stream: BOS Typewriter.
46230
46231 Time: System Intialization.
46232
46233 Meaning: Logical volume registration control was unable to
46234 truncate the segment PATHNAME for the REASON
46235 given. This segment is to be used for the logical
46236 volume registration control lock. Subsequent
46237
46238
46239
46240 vrm_lock_$vrm_data_init 798 08/21/20 MR12.7^L
46241
46242
46243 logical volume registration control operations may
46244 fail.
46245
46246 Action: No operator action is required.
46247
46248
46249 vrm_lock_.pl1
46250 vrm_lock_: Unable to initiate PATHNAME. REASON.
46251
46252
46253 Stream: Logged in SYSERR log.
46254
46255 Time: While system is running.
46256
46257 Meaning: Logical volume registration control vrm was
46258 unable to initiate PATHNAME which contains the
46259 vrm control lock because of REASON. The logical
46260 volume registration control operation requested
46261 was not performed.
46262
46263 Action: No operator action is required.
46264
46265
46266 vtoc_interrupt.pl1
46267 vtoc_interrupt: bad core address
46268
46269
46270 Stream: BOS Typewriter Crashes system
46271
46272 Time: While system is running.
46273
46274 Meaning: The disk dim reported a main memory address to the
46275 VTOC manager which was not in the VTOC buffer
46276 segment or was not designating a legal buffer
46277 boundary. This indicates a logic error in the
46278 supervisor or CPU or memory hardware problems.
46279
46280 Action: Follow normal recovery procedures.
46281
46282
46283 vtoc_interrupt.pl1
46284 vtoc_interrupt: Buffer not os at interrupt
46285
46286
46287 Stream: BOS Typewriter Crashes system
46288
46289 Time: While system is running.
46290
46291 Meaning: An I/O completion was received for a VTOC buffer
46292 which was apparently not undergoing I/O. This
46293 indicates a logic error in the supervisor or CPU
46294 or memory hardware problems.
46295
46296
46297
46298 vtoc_interrupt 799 08/21/20 MR12.7^L
46299
46300
46301 Action: Follow normal recovery procedures.
46302
46303
46304 vtoc_interrupt.pl1
46305 vtoc_interrupt: Write error on dskX_NN vtocx
46306 XXXXXX
46307
46308
46309 Stream: Logged in SYSERR log.
46310
46311 Time: While system is running.
46312
46313 Meaning: A bad I/O status was received by the VTOC manager
46314 for a write operation. The unwritten vtoce-part
46315 will remain in main memory until the next attempt
46316 is made to write it out or demount or shutdown
46317 time. Too many of these can cause the system to
46318 crash.
46319
46320 Action: No operator action is required.
46321
46322
46323 vtoc_man.pl1
46324 vtoc_man: Attempt to write less than entire VTOCE
46325 to MODEL device.
46326
46327
46328 Stream: BOS Typewriter Crashes system
46329
46330 Time: While system is running.
46331
46332 Meaning: An attempt has been made to write less than the
46333 entire VTOCE to a device MODEL that only supports
46334 a 512_word sector. For these devices the entire
46335 192 word VTOCE must be written at one time. A
46336 likely software error n VTOC buffer management.
46337
46338 Action: Follow normal recovery procedures.
46339
46340
46341 vtoc_man.pl1
46342 vtoc_man: Buffer out-of-service during cleanup
46343
46344
46345 Stream: BOS Typewriter Crashes system
46346
46347 Time: When a volume is being demounted or during system
46348 shutdown.
46349
46350 Meaning: A likely software error in VTOC buffer management
46351 which caused an inconsistency in the VTOC buffer.
46352
46353 Action: Follow normal recovery procedures.
46354
46355
46356 vtoc_man 800 08/21/20 MR12.7^L
46357
46358
46359
46360
46361 vtoc_man.pl1
46362 vtoc_man: buffer out-of-service on write
46363
46364
46365 Stream: BOS Typewriter Crashes system
46366
46367 Time: While system is running.
46368
46369 Meaning: A likely software problem has caused an
46370 inconsistency in the VTOC buffer.
46371
46372 Action: Follow normal recovery procedures.
46373
46374
46375 vtoc_man.pl1
46376 vtoc_man: Hot buffer abandoned during cleanup
46377 vtocx XXXXX dskX_NNs
46378
46379
46380 Stream: Logged in SYSERR log.
46381
46382 Time: When a volume is being demounted or during system
46383 shutdown.
46384
46385 Meaning: An update to VTOCE XXXXX on dskX_NNs could not
46386 be completed due to I/O errors. The VTOCE may be
46387 inconsistent or damaged.
46388
46389 Action: The VTOCE should be examined by means of
46390 dump_vtoce the next time the volume is online.
46391 Any inconsistency can be corrected by a volume
46392 salvage.
46393
46394
46395
46396 vtoc_man.pl1
46397 vtoc_man: Invalid free vtocx XXXXX on dskX_NNs
46398
46399
46400 Stream: Logged in SYSERR log.
46401
46402 Time: While system is running.
46403
46404 Meaning: A free VTOCE was allocated which has an invalid
46405 VTOCE index for the volume. This is indicative of
46406 damage to volume control structures. This damage
46407 can be corrected by a volume salvage.
46408
46409 Action: No operator action is required.
46410
46411
46412
46413
46414 vtoc_man 801 08/21/20 MR12.7^L
46415
46416
46417
46418
46419 vtoc_man.pl1
46420 vtoc_man: Invalid write
46421
46422
46423 Stream: BOS Typewriter Crashes system
46424
46425 Time: While system is running.
46426
46427 Meaning: A likely software error in the calling sequence
46428 for output of a VTOCE.
46429
46430 Action: Follow normal recovery procedures.
46431
46432
46433 vtoc_man.pl1
46434 vtoc_man: Out of buffers try number N
46435
46436
46437 Stream: BOS Typewriter.
46438
46439 Time: While system is running.
46440
46441 Meaning: There may be a disk problem which prevents the
46442 vtoc buffers from being written to disk or there
46443 may be a disk tuning problem. The system may
46444 crash within the next few minutes.
46445
46446 Action: Contact the system programming staff._sa
46447
46448
46449 vtoc_man.pl1
46450 vtoc_man: read reset of crawlout by
46451 PERSON.PROJECT.TAG for dskX_NNs vtocx XXXXXX
46452
46453
46454 Stream: Logged in SYSERR log.
46455
46456 Time: While system is running.
46457
46458 Meaning: The process of PERSON.PROJECT.TAG crawled out of
46459 ring-0 or terminated with the VTOC buffer lock
46460 held. A buffer was marked out-of-service for read
46461 to VTOCE XXXXX on dskX_NNs for which no I/O had
46462 been queued. The read I/O was abandoned.
46463
46464 Action: No operator action is required.
46465
46466
46467 vtoc_man.pl1
46468 vtoc_man: UID ^= 0 in free VTOCE vtocx XXXXX
46469 dskX_NNs
46470
46471
46472 vtoc_man 802 08/21/20 MR12.7^L
46473
46474
46475 Stream: Logged in SYSERR log.
46476
46477 Time: While system is running.
46478
46479 Meaning: The contents of VTOCE XXXXX on dskX_NNs are
46480 incorrect as free VTOCEs should have a zero UID.
46481 The system attempts to find another free VTOCE.
46482 This may indicate damage to volume control
46483 structures. This damage can be corrected by a
46484 volume salvage.
46485
46486 Action: No operator action is required.
46487
46488
46489 vtoc_man.pl1
46490 vtoc_man: Update in progress on crawlout by
46491 PERSON.PROJECT.TAG dskX_NNs
46492
46493
46494 Stream: Logged in SYSERR log.
46495
46496 Time: While system is running.
46497
46498 Meaning: The process of PERSON.PROJECT.TAG crawled out of
46499 ring-0 or terminated with the vtoc buffer lock
46500 held and an update in progress for a VTOCE on
46501 dskX_NNs. The VTOCE may be inconsistent. Any
46502 inconsistency can be corrected by a volume
46503 salvage.
46504
46505 Action: No operator action is required.
46506
46507
46508 vtoc_man.pl1
46509 vtoc_man: Write I/O being retried by
46510 PERSON.PROJECT.TAG for dskX_NNs vtocx XXXXX
46511
46512
46513 Stream: Logged in SYSERR log.
46514
46515 Time: While system is running.
46516
46517 Meaning: A buffer previously marked as "hot" is being
46518 requeued for I/O.
46519
46520 Action: No operator action is required.
46521
46522
46523 vtoc_man.pl1
46524 vtoc_man: write I/O recovered on crawlout by
46525 PERSON.PROJECT.TAG for dskX_NNs vtocx XXXXX
46526
46527
46528
46529
46530 vtoc_man 803 08/21/20 MR12.7^L
46531
46532
46533 Stream: Logged in SYSERR log.
46534
46535 Time: While system is running.
46536
46537 Meaning: The process of PERSON.PROJECT.TAG crawled out of
46538 ring-0 or terminated with the VTOC buffer lock
46539 held. A buffer was marked out-of-service for
46540 write to VTOCE XXXXX on dskX_NNs for which no
46541 I/O had been queued. The write I/O was requeued.
46542
46543 Action: No operator action is required.
46544
46545
46546 vtoce_stock_man.pl1
46547 vtoce_stock_man: Attempt to deposit free vtocx
46548 YYYYYY on dskX_NN
46549
46550
46551 Stream: BOS Typewriter.
46552
46553 Time: While system is running.
46554
46555 Meaning: A VTOCE was returned to the free pool of VTOCEs on
46556 the device indicated but the VTOCE was already
46557 marked as free. This indicates possible device
46558 damage. This damage can be corrected by a
46559 physical volume salvage.
46560
46561 Action: Contact the system programming staff.
46562
46563
46564 vtoce_stock_man.pl1
46565 vtoce_stock_man: Attempt to deposit invalid vtocx
46566 YYYYYY on dskX_NN
46567
46568
46569 Stream: BOS Typewriter.
46570
46571 Time: While system is running.
46572
46573 Meaning: There was an attempt to return a free VTOCE to the
46574 pool of free VTOCEs for the device indicated but
46575 the index of the VTOCE was not valid. This
46576 indicates possible damage to the device. Such
46577 damage can be corrected by a physical volume
46578 salvage.
46579
46580 Action: Contact the system programming staff.
46581
46582
46583 vtoce_stock_man.pl1
46584 vtoce_stock_man: MYLOCK of VTOC Map for dskX_NN
46585
46586
46587
46588 vtoce_stock_man 804 08/21/20 MR12.7^L
46589
46590
46591 Stream: BOS Typewriter Crashes system
46592
46593 Time: While system is running.
46594
46595 Meaning: A process attempted to acquire a lock on the VTOC
46596 Map for the device indicated while already owning
46597 the lock. This is probably a software error.
46598
46599 Action: Follow normal recovery procedures.
46600
46601
46602 vtoce_stock_man.pl1
46603 vtoce_stock_man: PVTE and VTOCE stock
46604 out-of-synch on dskX_NN
46605
46606
46607 Stream: BOS Typewriter Crashes system
46608
46609 Time: While system is running.
46610
46611 Meaning: There is an inconsistency between the Physical
46612 Volume Table Entry and the VTOCE Stock for the
46613 device indicated. This is probably a software
46614 error.
46615
46616 Action: Follow normal recovery procedures.
46617
46618
46619 vtoce_stock_man.pl1
46620 vtoce_stock_man: STACQ fails for VTOC Map lock on
46621 dskX_NN
46622
46623
46624 Stream: BOS Typewriter Crashes system
46625
46626 Time: While system is running.
46627
46628 Meaning: A process was unable to unlock the VTOC Map lock
46629 for the device indicated. This is probably a
46630 hardware failure either in the CPU or in main
46631 memory.
46632
46633 Action: Follow normal recovery procedures.
46634
46635
46636 vtoce_stock_man.pl1
46637 vtoce_stock_man: VTOCE stock inconsistent on
46638 dskX_NN
46639
46640
46641 Stream: BOS Typewriter Crashes system
46642
46643 Time: While system is running.
46644
46645
46646 vtoce_stock_man 805 08/21/20 MR12.7^L
46647
46648
46649 Meaning: There is an internal inconsistency in the stock of
46650 free VTOCES on the device indicated. This is
46651 probably a software malfunction.
46652
46653 Action: Follow normal recovery procedures.
46654
46655
46656 wdx.pl1
46657 wdx: ERRORCODE Unable to send wakeup on master
46658 channel.
46659
46660
46661 Stream: BOS Typewriter.
46662
46663 Time: While system is running.
46664
46665 Meaning: The ring-1 logical volume mount software was
46666 unable to send a wakeup to the ring-4 software for
46667 the reason indicated. Some mount requests may
46668 have been lost.
46669
46670 Action: Contact the system programming staff._sa
46671
46672
46673 wire_proc.pl1
46674 wire_proc: lock not locked
46675
46676
46677 Stream: BOS Typewriter Crashes system
46678
46679 Time: While system is running.
46680
46681 Meaning: The lock on temp-wiring in the SST was found
46682 unlocked at the time an attempt was made to unlock
46683 it. The SST may be damaged. This indicates a
46684 logic error in the supervisor or CPU or memory
46685 hardware problems.
46686
46687 Action: Follow normal recovery procedures.
46688
46689
46690 wire_proc.pl1
46691 wire_proc: too many temp wired segments.
46692
46693
46694 Stream: BOS Typewriter Crashes system
46695
46696 Time: While system is running.
46697
46698 Meaning: A request has been made to the supervisor to
46699 temp-wire an eighth hardcore segment. Only seven
46700 are allowed. Temp-wiring is used for supervisor
46701 programs not I/O buffers. This indicates a logic
46702
46703
46704 wire_proc 806 08/21/20 MR12.7^L
46705
46706
46707 error in the supervisor or CPU or memory hardware
46708 problems.
46709
46710 Action: Follow normal recovery procedures. $boot_tape
46711
46712
46713
46714 wired_shutdown.pl1
46715 wired_shutdown: FFF fault during emergency
46716 shutdown
46717
46718
46719 Stream: BOS Typewriter Crashes system
46720
46721 Time: Emergency shutdown
46722
46723 Meaning: An unexpected fault has occured during emergency
46724 shutdown. Emergency shutdown cannot complete.
46725
46726 Action: Get a dump for system programmers. If an disk
46727 dump was taken of the preceding crash get a dump
46728 to paper via the bce dump facility. Re-attempt
46729 ESD as many times as necessary.
46730
46731
46732
46733 x25_mpx.pl1
46734 x25_mpxCHN: Call Confirm in state STATE.
46735
46736
46737 Stream: Logged in SYSERR log.
46738
46739 Time: While system is running.
46740
46741 Meaning: An unexpected Call Confirm packet was received.
46742 The call is cleared.
46743
46744 Action: Contact the system programming staff.
46745
46746
46747 x25_mpx.pl1
46748 x25_mpxCHN: Clear Confirm in state STATE.
46749
46750
46751 Stream: Logged in SYSERR log.
46752
46753 Time: While system is running.
46754
46755 Meaning: An unexpected Clear Confirm packet has been
46756 received. The call is cleared.
46757
46758 Action: Contact the system programming staff.
46759
46760
46761
46762 x25_mpxCHN 807 08/21/20 MR12.7^L
46763
46764
46765
46766
46767 x25_mpx.pl1
46768 x25_mpxCHN: Clear Indication CAUSE/DIAGNOSTIC.
46769
46770
46771 Stream: Logged in SYSERR log.
46772
46773 Time: While system is running.
46774
46775 Meaning: A Clear Indication with non-zero cause or
46776 diagnostic fields has been received. The call is
46777 cleared.
46778
46779 Action: No operator action is required.
46780
46781
46782 x25_mpx.pl1
46783 x25_mpxCHN: Data packet received in state
46784 STATE.
46785
46786
46787 Stream: Logged in SYSERR log.
46788
46789 Time: While system is running.
46790
46791 Meaning: An unexpected data packet was received. The call
46792 is cleared.
46793
46794 Action: Contact the system programming staff.
46795
46796
46797 x25_mpx.pl1
46798 x25_mpxCHN: Diagnostic type TYPE.
46799
46800
46801 Stream: Logged in SYSERR log.
46802
46803 Time: While system is running.
46804
46805 Meaning: A diagnostic packet of type TYPE was received.
46806 Normal processing continues.
46807
46808 Action: Contact the system programming staff.
46809
46810
46811 x25_mpx.pl1
46812 x25_mpxCHN: Error CODE from write.
46813
46814
46815 Stream: Logged in SYSERR log.
46816
46817 Time: While system is running.
46818
46819
46820 x25_mpxCHN 808 08/21/20 MR12.7^L
46821
46822
46823 Meaning: An error occurred writing to the LAP channel. The
46824 LAP channel will be disconnected.
46825
46826 Action: Contact the system programming staff.
46827
46828
46829 lap_simplex.pl1
46830 x25_mpxCHN: Error from write of XXX chars.
46831 ERROR
46832
46833
46834 Stream: Logged in SYSERR log.
46835
46836 Time: While system is running.
46837
46838 Meaning: The ERROR occurred writing XXX characters to the
46839 LAP channel. The LAP channel will be
46840 disconnected.
46841
46842 Action: Contact the system programming staff.
46843
46844
46845 x25_mpx.pl1
46846 x25_mpxCHN: Failure Link state: STATE
46847 Current Action: FUNCTION in ESTATE Primary
46848 state: PSTATE Secondary state: SSTATE.
46849
46850
46851 Stream: Logged in SYSERR log.
46852
46853 Time: While system is running.
46854
46855 Meaning: Normal request to crash the line when the link has
46856 been disconnected by the FNP. STATE is the main
46857 state of the link. FUNCTION is the last function
46858 the link processed. The ESTATE is the execution
46859 state of the last function. PSTATE and SSTATE are
46860 the link up substate.
46861
46862 Action: Contact the system programming staff.
46863
46864
46865 x25_mpx.pl1
46866 x25_mpxCHN: Invalid channel number LCN.
46867
46868
46869 Stream: Logged in SYSERR log.
46870
46871 Time: While system is running.
46872
46873 Meaning: An X.25 packet with an invalid logical channel
46874 group number or logical channel number has been
46875 received. The packet is ignored.
46876
46877
46878 x25_mpxCHN 809 08/21/20 MR12.7^L
46879
46880
46881 Action: Contact the system programming staff.
46882
46883
46884 x25_mpx.pl1
46885 x25_mpxCHN: Invalid packet type TYPE on LC 0.
46886
46887
46888 Stream: Logged in SYSERR log.
46889
46890 Time: While system is running.
46891
46892 Meaning: An invalid packet of type TYPE was received on
46893 logical channel zero. The packet will be ignored.
46894
46895 Action: Contact the system programming staff.
46896
46897
46898 x25_mpx.pl1
46899 x25_mpxCHN: Invalid X.29 command CMD.
46900
46901
46902 Stream: Logged in SYSERR log.
46903
46904 Time: While system is running.
46905
46906 Meaning: An invalid X.29 command was received. An error
46907 indication is returned to the sender.
46908
46909 Action: Contact the system programming staff.
46910
46911
46912 x25_mpx.pl1
46913 x25_mpxCHN: Link disconnected due to
46914 mis-matched frame sizes. CMDR/FRMR frame: FRAME.
46915
46916
46917 Stream: Logged in SYSERR log.
46918
46919 Time: While system is running.
46920
46921 Meaning: The FNP has received a command reject LAPB or
46922 frame reject LAP which specified a reason of
46923 "wide frame" on channel CHN. The actual level 2
46924 command is FRAME. This means the frame received
46925 by the other end was too long. Instead of looping
46926 continuously trying to send this frame the link
46927 will be disconnected. The maximum frame size in
46928 the Multics TTF for this link should be checked
46929 against the size expected by the other end of the
46930 link and corrected.
46931
46932 Action: Contact the system programming staff.
46933
46934
46935
46936 x25_mpxCHN 810 08/21/20 MR12.7^L
46937
46938
46939
46940
46941 x25_mpx.pl1
46942 x25_mpxCHN: No buffers available.
46943
46944
46945 Stream: Logged in SYSERR log.
46946
46947 Time: While system is running.
46948
46949 Meaning: x25_mpx was unable to allocate a buffer for a
46950 protocol packet. This indicates a severe space
46951 problem in tty_buf. The multiplexer will sends
46952 itself a "hangup" order after freeing any space it
46953 has for protocol packets in tty_buf. If this
46954 multiplexer is not the cause of the problem then
46955 the system is likely to crash soon.
46956
46957 Action: Contact the system programming staff.
46958
46959
46960 x25_mpx.pl1
46961 x25_mpxCHN: Packet INOUT: PACKET
46962
46963
46964 Stream: Logged in SYSERR log.
46965
46966 Time: While system is running.
46967
46968 Meaning: A packet has been received or sent and is logged.
46969 This occurs when the packet tracing facility is
46970 turned on. INOUT is the direction and PACKET is
46971 the packet octets dumped in hexadecimal.
46972
46973 Action: No operator action is required.
46974
46975
46976 x25_mpx.pl1
46977 x25_mpxCHN: Packet too short.
46978
46979
46980 Stream: Logged in SYSERR log.
46981
46982 Time: While system is running.
46983
46984 Meaning: A packet less then 3 characters long was received.
46985
46986 Action: Contact the system programming staff.
46987
46988
46989 x25_mpx.pl1
46990 x25_mpxCHN: Received REJ packet.
46991
46992
46993
46994 x25_mpxCHN 811 08/21/20 MR12.7^L
46995
46996
46997 Stream: Logged in SYSERR log.
46998
46999 Time: While system is running.
47000
47001 Meaning: An X.25 REJ packet was received. Multics does not
47002 support this feature. The virtual circuit is
47003 reset.
47004
47005 Action: Contact the system programming staff.
47006
47007
47008 x25_mpx.pl1
47009 x25_mpxCHN: Reset Confirm in state STATE.
47010
47011
47012 Stream: Logged in SYSERR log.
47013
47014 Time: While system is running.
47015
47016 Meaning: An unexpected Reset Confirm packet has been
47017 received. The call is reset.
47018
47019 Action: Contact the system programming staff.
47020
47021
47022 x25_mpx.pl1
47023 x25_mpxCHN: Reset received CAUSE/DIAGNOSTIC.
47024
47025
47026 Stream: Logged in SYSERR log.
47027
47028 Time: While system is running.
47029
47030 Meaning: A RESET REQUEST packet has been received.
47031
47032 Action: No operator action is required.
47033
47034
47035 x25_mpx.pl1
47036 x25_mpxCHN: Sequence error PS = N VR = N.
47037
47038
47039 Stream: Logged in SYSERR log.
47040
47041 Time: While system is running.
47042
47043 Meaning: An X.25 packet was received with an incorrect
47044 value for PS. The logical channel is reset.
47045
47046 Action: Contact the system programming staff.
47047
47048
47049 x25_mpx.pl1
47050
47051
47052 x25_mpxCHN 812 08/21/20 MR12.7^L
47053
47054
47055 x25_mpxCHN: Sequence error: PR = N is not
47056 between previous PR = N and VS = N.
47057
47058
47059 Stream: Logged in SYSERR log.
47060
47061 Time: While system is running.
47062
47063 Meaning: An X.25 packet was received with an incorrect
47064 value for PR. The logical channel is reset.
47065
47066 Action: Contact the system programming staff.
47067
47068
47069 x25_mpx.pl1
47070 x25_mpxCHN: Unexpected Interrupt Confirm.
47071
47072
47073 Stream: Logged in SYSERR log.
47074
47075 Time: While system is running.
47076
47077 Meaning: An unexpected Interrupt Confirm packet has been
47078 received. The call is reset.
47079
47080 Action: Contact the system programming staff.
47081
47082
47083 x25_mpx.pl1
47084 x25_mpxCHN: Unexpected interrupt TYPE DATA
47085 received.
47086
47087
47088 Stream: Logged in SYSERR log.
47089
47090 Time: While system is running.
47091
47092 Meaning: An unexpected MCM interrupt was processed.
47093
47094 Action: Contact the system programming staff.
47095
47096
47097 x25_mpx.pl1
47098 x25_mpxCHN: Unexpected packet type TYPE on idle
47099 VC.
47100
47101
47102 Stream: Logged in SYSERR log.
47103
47104 Time: While system is running.
47105
47106 Meaning: An unexpected packet has been received on an idle
47107 channel. The channel is cleared.
47108
47109
47110 x25_mpxCHN 813 08/21/20 MR12.7^L
47111
47112
47113 Action: Contact the system programming staff.
47114
47115
47116 x25_mpx.pl1
47117 x25_mpxCHN: Unexpected packet type TYPE.
47118
47119
47120 Stream: Logged in SYSERR log.
47121
47122 Time: While system is running.
47123
47124 Meaning: An unexpected packet has been received. The
47125 packet is ignored.
47126
47127 Action: Contact the system programming staff.
47128
47129
47130 x25_mpx.pl1
47131 x25_mpxCHN: Unrecognized general format ID
47132 GFID.
47133
47134
47135 Stream: Logged in SYSERR log.
47136
47137 Time: While system is running.
47138
47139 Meaning: A packet with a bad format ID was received. The
47140 packet will be ignored.
47141
47142 Action: Contact the system programming staff.
47143
47144
47145 x25_mpx.pl1
47146 x25_mpxCHN: X.29 ERROR CODE/REASON.
47147
47148
47149 Stream: Logged in SYSERR log.
47150
47151 Time: While system is running.
47152
47153 Meaning: An X.29 ERROR packet with error code CODE and
47154 reason REASON was received. The packet is
47155 ignored.
47156
47157 Action: Contact the system programming staff.
47158
47159
47160 x25_mpx.pl1
47161 x25_mpxCHN/LC: Call Request in state STATE.
47162
47163
47164 Stream: Logged in SYSERR log.
47165
47166
47167
47168 x25_mpxCHN/LC 814 08/21/20 MR12.7^L
47169
47170
47171 Time: While system is running.
47172
47173 Meaning: An unexpected Call Request has been received. The
47174 call is cleared.
47175
47176
47177 x25_mpx.pl1
47178 x25_mpxCHN/LC: Clear Indication
47179 CAUSE/DIAGNOSTIC in idle VC.
47180
47181
47182 Stream: Logged in SYSERR log.
47183
47184 Time: While system is running.
47185
47186 Meaning: A Clear Indication has been received on a channel
47187 with no call in progress. A Clear Confirm is
47188 returned.
47189
47190 Action: No operator action is required.
47191
47192
47193 x25_mpx.pl1
47194 x25_mpxCHN/LC: No listening channels.
47195
47196
47197 Stream: Logged in SYSERR log.
47198
47199 Time: While system is running.
47200
47201 Meaning: There were no listening channels available for a
47202 network call. The call is refused.
47203
47204 Action: Contact the system programming staff.
47205
47206
47207 x25_mpx.pl1
47208 x25_mpxCHN/LC: Time out in state STATE.
47209
47210
47211 Stream: Logged in SYSERR log.
47212
47213 Time: While system is running.
47214
47215 Meaning: The network did not respond to a call reset or
47216 clear request. The call will be cleared.
47217
47218 Action: Contact the system programming staff.
47219
47220
47221
47222
47223
47224
47225
47226 x25_mpxCHN/LC 815 08/21/20 MR12.7^L