1
2
3
4 MULTICS MR12.5 ERROR MESSAGE DOCUMENTATION
5
6
7
8
9
10 October 27, 1992
11
12
13 _^HI_^HN_^HT_^HR_^HO_^HD_^HU_^HC_^HT_^HI_^HO_^HN
14
15 This document has been prepared automatically from the
16 system source by Multics Software Support. Every effort has been
17 made to supply documentation for each and every message that
18 could appear either on the system console, or in the system logs.
19 However, some of the system messages are not provided in this
20 document due to the messages developed prior to the development
21 of the error messages document, or omitted in error. The
22 following is a list of modules that are known to be missing from
23 this document:
24
25 bootload_fs_.pl1 protocol_mpx.pl1
26 dir_dump.pl1 rcp_mount_timer_poll_.pl1
27 emergency_shutdown.alm rcp_pre_claim_.pl1
28 extract_msg_doc_.pl1 rcprm_verify_registries_.pl1
29 find_rpv_subsystem.pl1 read_disk_label.pl1
30 hc_device_acct_.pl1 salv_directory.pl1
31 hc_tune.pl1.pmac salv_err_msg.pl1
32 hc_tune.pl1.pmac salvager.pl1
33 initial_error_handler.pl1 sc_admin_mode_.pl1
34 io_reconfig.pl1 sys_log_.pl1
35 ioi_page_table.pl1 syserr.alm
36 iom_switches.pl1 syserr_log_daemon.pl1
37 level_error.pl1 tty_read.pl1
38 mcs_timer_daemon.pl1 uncp.pl1
39 mdc_check_mdcs_.pl1 uncp_boot_interrupt.pl1
40 multiplexer_mgr_.pl1 uncp_multiplexer.pl1
41 pc_recover_sst.pl1 uncp_util.pl1
42 polled_vip_mpx.pl1
43
44
45
46 _^HE_^HX_^HP_^HL_^HA_^HN_^HA_^HT_^HI_^HO_^HN _^HO_^HF _^HE_^HR_^HR_^HO_^HR _^HM_^HE_^HS_^HS_^HA_^HG_^HE_^HS_^H.
47
48
49 For each message, an example of the text of the message is
50 provided, followed by four paragraphs: Severity, Time, Meaning,
51 and Action.
52
53
54
55
56
57
58
59 -1- MR12.5 10/27/92^L
60
61
62 _^HM_^He_^Hs_^Hs_^Ha_^Hg_^He _^HE_^Hx_^Ha_^Hm_^Hp_^Hl_^He
63
64 The message example is a literal copy of the message, with
65 substitutable fields shown in all capitals. Each substitutable
66 field is described in the Meaning paragraph.
67
68
69 _^HO_^Hu_^Ht_^Hp_^Hu_^Ht
70
71 The output field describes how the message is output. For
72 hardcore messages it shows the interpretation of the first
73 argument to SYSERR, which determines whether the system crashes,
74 sounds the beeper, etc. For answering service messages, it
75 describes the output stream and source.
76
77
78 _^HT_^Hi_^Hm_^He
79
80 The time section describes the time when the message is
81 possible.
82
83
84 _^HM_^He_^Ha_^Hn_^Hi_^Hn_^Hg
85
86 The meaning paragraph describes the situation that prompted
87 the message and the probable cause of the situation. It then
88 describes the consequences of the situation. Substitutable
89 parameters in the message example are explained here.
90
91
92 _^HA_^Hc_^Ht_^Hi_^Ho_^Hn
93
94 The action paragraph describes what operator action is
95 required when the message occurs.
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117 -2- MR12.5 10/27/92^L
118
119
120 scas_init.pl1
121 "scas_init: MEM Y. Tags greater than "D" not supported by DPS8
122 CPUs",
123
124
125 Stream: BOS Typewriter Crashes system
126
127 Time: System Intialization.
128
129 Meaning: The physical configuration or the configuration
130 deck is incorrect. DPS8 CPUs have only 4 memory
131 ports, therefore Multics systems comprised of DPS8
132 cpus or mixed systems of DPS, L68 and DPS8 cpus
133 can only have 4 memories configured. i.e.
134 Memory tags A B C and D.
135
136 Action: Correct the physical configuration and/or the
137 configuration deck and reboot.
138
139
140
141 sc_process_command_line_.pl1
142 input on SWITCH_NAME REQUEST_LINE
143
144
145 Stream: as severity 0
146
147 Time: In response to an operator command.
148
149 Meaning: Logs a REQUEST_LINE typed by the operator, or by
150 another user via the send_admin_command or
151 send_initializer_command commands.
152
153 Action: No operator action is required.
154
155
156
157 absentee_utility_.pl1
158 abs ACTION: N requests ACTIONed.
159
160
161 Stream: as severity1
162
163 Time: In response to an abs defer or abs release
164 command.
165
166 Meaning: Indicates success or failure of the command.
167 ACTION can be defer or release, and N can be "no"
168 or the number of requests acted upon.
169
170 Action: Confirm that the expected results were obtained.
171
172
173
174
175 abs ACTION -3- MR12.5 10/27/92^L
176
177
178 absentee_utility_.pl1
179 abs run: job selection arguments matched N
180 requests; be more specific.
181
182
183 Stream: as severity1
184
185 Time: In response to an abs run command.
186
187 Meaning: The specified arguments matched either zero, or
188 more than one, request, and so no job was run.
189
190 Action: Re-enter the command with correct arguments, to
191 select exactly one job for running.
192
193
194
195 absentee_utility_.pl1
196 abs run: request PATH ID is already running.
197
198
199 Stream: as severity1
200
201 Time: In response to an abs run command.
202
203 Meaning: The specified job is already running.
204
205 Action: If a mistake was made, repeat the command,
206 specifying the correct job.
207
208
209
210 absentee_user_manager_.pl1
211 absentee_user_manager_ abs run: System too
212 full; no absentee jobs can be started now.
213
214
215 Stream: as severity1
216
217 Time: In response to an abs run command.
218
219 Meaning: The system is too near the upper limit on logged
220 in users to start any absentee jobs.
221
222 Action: If the immediate running of the job is essential,
223 use "abs stop queue all" to halt all other
224 absentee logins, change the login word to halt all
225 interactive logins, and either wait for a process
226 to log out, or bump one, before repeating the abs
227 run command.
228
229
230
231
232
233 absentee_user_manager_ ab -4- MR12.5 10/27/92^L
234
235
236 absentee_user_manager_.pl1
237 absentee_user_manager_$init: MESSAGE. Cannot
238 truncate absentee_user_table.
239
240
241 Stream: as severity1
242
243 Time: System Intialization.
244
245 Meaning: It was not possible to clear the
246 absentee_user_table segment.
247
248 Action: Contact the system programming staff.
249
250
251
252 absentee_user_manager_.pl1
253 absentee_user_manager_: ERROR attempting to
254 cancel reservation R for USER.PROJ absN
255
256
257 Stream: as severity1
258
259 Time: While system is running.
260
261 Meaning: The system was unable to cancel a resource
262 reservation for an absentee process that is being
263 destroyed. The resources might remain
264 unavailable to other users. There is some problem
265 in the resource reservation mechanism.
266
267 Action: Contact the system programming staff.
268
269
270
271 absentee_user_manager_.pl1
272 absentee_user_manager_: ERROR attempting to
273 pre-claim reservation R for USER.PROJ absN
274
275
276 Stream: as severity1
277
278 Time: While system is running.
279
280 Meaning: The system was unable to assign a resource
281 reservation to an absentee job that is being
282 logged in. The job will be run but it might fail
283 if the resources it needs happen to be unavailable
284 when it requests them. There is some problem in
285 the resource reservation mechanism.
286
287 Action: Contact the system programming staff.
288
289
290
291 absentee_user_manager_ -5- MR12.5 10/27/92^L
292
293
294 absentee_user_manager_.pl1
295 absentee_user_manager_: Error in initializing
296 absentee. Don't bring up absentee facility
297
298
299 Stream: as severity1
300
301 Time: While system is running.
302
303 Meaning: The absentee mechanism will not initialize.
304
305 Action: Contact the system programming staff. Do _^Hn_^Ho_^Ht try
306 to initialize the absentee facility.
307
308
309
310 absentee_user_manager_.pl1
311 absentee_user_manager_: Error: CONDITION
312
313
314 Stream: as severity2
315
316 Time: While system is running.
317
318 Meaning: An unexpected fault has occurred while performing
319 some absentee function such as logging in a new
320 absentee user. The system automatically performs
321 an Answering Service dump and attempts to recover.
322
323 Action: No action is required unless the condition
324 persists. If this message occurs repeatedly try
325 stopping the absentee facility; inform the
326 programming staff.
327
328
329
330 absentee_user_manager_.pl1
331 absentee_user_manager_: ERROR_MESSAGE. Cannot
332 create absentee event channel
333
334
335 Stream: as severity2
336
337 Time: System Intialization.
338
339 Meaning: The absentee facility could not create part of its
340 communications mechanism. No absentee process can
341 be logged in.
342
343 Action: Try the abs start command again. If the absentee
344 facility still fails inform the programming
345 staff.
346
347
348
349 absentee_user_manager_ -6- MR12.5 10/27/92^L
350
351
352 absentee_user_manager_.pl1
353 absentee_user_manager_: ERROR_MESSAGE. Creating
354 proc for NAME.PROJ
355
356
357 Stream: as severity2
358
359 Time: While system is running.
360
361 Meaning: A storage system error prevented the absentee user
362 from logging in. This is due to some error in the
363 process creating mechanism. The user is not
364 logged in.
365
366 Action: Contact the system programming staff. Shut down
367 the absentee facility with an abs bump * * and an
368 abs stop if this message occurs repeatedly.
369
370
371
372 absentee_user_manager_.pl1
373 absentee_user_manager_: ERROR_MESSAGE. Trying to
374 wakeup PERSON.PROJECT.TAG process after abs
375 release.
376
377
378 Stream: $as0
379
380 Time: Called in response to an operator abs release
381 command.
382
383 Meaning: A failure occurred while sending a wakeup to the
384 absentee process being released. ERROR_MESSAGE is
385 the text associated with the error code returned
386 by hcs_$wakeup.
387
388 Action: No operator action is required.
389
390
391
392 absentee_user_manager_.pl1
393 absentee_user_manager_: event calls were masked.
394
395
396 Stream: sc user_output
397
398 Time: While system is running.
399
400 Meaning: This message indicates a serious error in the
401 Initializer programs. The system attempts to
402 recover and keep running.
403
404 Action: Contact the system programming staff.
405
406
407 absentee_user_manager_ -7- MR12.5 10/27/92^L
408
409
410 absentee_user_manager_.pl1
411 absentee_user_manager_: Premature stopstop for ID
412
413
414 Stream: as severity0
415
416 Time: While system is running.
417
418 Meaning: An error has occurred while trying to destroy the
419 absentee process ID. The system recovers and
420 continues.
421
422 Action: No operator action is required.
423
424
425
426 absentee_user_manager_.pl1
427 absentee_user_manager_: Process terminated
428 USER.PROJ ID MESSAGE.
429
430
431 Stream: as severity0
432
433 Time: While system is running.
434
435 Meaning: The absentee process ID of USER.PROJ has
436 terminated for the reason specified and will be
437 logged out.
438
439 Action: No operator action is required.
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465 absentee_user_manager_ -8- MR12.5 10/27/92^L
466
467
468 absentee_user_manager_.pl1
469 absentee_user_manager_: Strange event message
470 WWWWWWWWWWWW WWWWWWWWWWWW from user proc
471 WWWWWWWWWWWW
472
473
474 Stream: as severity1
475
476 Time: While system is running.
477
478 Meaning: This message is similar to the preceding message
479 described above except that the signal does not
480 come from the Initializer but from some other
481 process. The process ID of the sending process is
482 printed in octal. The event message was not a
483 valid item. The system ignores the signal and
484 goes on.
485
486 Action: If absentee jobs will no longer run try an abs
487 stop and an abs start. Inform the system
488 programming staff.
489
490
491
492 absentee_user_manager_.pl1
493 absentee_user_manager_: Strange event message
494 WWWWWWWWWWWW WWWWWWWWWWWW from Initializer
495
496
497 Stream: as severity1
498
499 Time: While system is running.
500
501 Meaning: An unrecognizable event message has been received
502 from the Answering Service. Its value is printed
503 in octal. Usually the first word is the function
504 code and the second word is the index in the
505 absentee user table. This condition is due to a
506 error in the Answering Service or absentee
507 programs. The system ignores the signal and goes
508 on. The absentee facility may cease to operate.
509
510 Action: If absentee jobs will no longer run try an abs
511 stop and an abs start. Inform the system
512 programming staff.
513
514
515
516
517
518
519
520
521
522
523 absentee_user_manager_ -9- MR12.5 10/27/92^L
524
525
526 absentee_user_manager_.pl1
527 absentee_user_manager_: Strange event message
528 WWWWWWWWWWWW WWWWWWWWWWWW from NAME.PROJ TTY
529
530
531 Stream: as severity1
532
533 Time: While system is running.
534
535 Meaning: This message is similar to the preceding message
536 except that the name project and tty name of the
537 user sending the wakeup are printed. The system
538 ignores the signal and goes on.
539
540 Action: No operator action is required.
541
542
543
544 absentee_user_manager_.pl1
545 absentee_user_manager_: Trace ....
546
547
548 Stream: as severity1
549
550 Time: While system is running.
551
552 Meaning: This is trace output. It begins coming out about
553 every five minutes after
554 absentee_user_manager_$aum_trace_on is called.
555
556 Action: No operator action is required. To shut this
557 message off type:
558 absentee_user_manager_$aum_trace_off while in
559 admin mode.
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581 absentee_user_manager_ -10- MR12.5 10/27/92^L
582
583
584 absentee_utility_.pl1
585 absentee_utility_ abs run: Request PATH ID will
586 be run in spite of unavailable resources:
587 RESOURCE
588
589
590 Stream: as severity1
591
592 Time: In response to an abs run command.
593
594 Meaning: The job selected by the abs run command needs
595 RESOURCE which is unavailable. The job will be
596 logged in anyway.
597
598 Action: If the job is critical the resource could be made
599 available by force detaching it from some other
600 process. This is a drastic action and should not
601 be taken without the System Administrator's
602 approval.
603
604
605
606 absentee_utility_.pl1
607 absentee_utility_ setup_queue: Invalid queue
608 number: QUEUE
609
610
611 Stream: as severity2
612
613 Time: While system is running.
614
615 Meaning: The internal queue number in absentee_utility_ was
616 invalid when trying to find an absentee to login.
617 If this occurs there is a logic error in
618 absentee_utility_.
619
620 Action: Contact the system programming staff.
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639 absentee_utility_ setup_q -11- MR12.5 10/27/92^L
640
641
642 absentee_utility_.pl1
643 absentee_utility_: >sc1>absentee_data has
644 overflowed its limit of N entries.
645
646
647 Stream: as severity2
648
649 Time: While system is running.
650
651 Meaning: The absentee facility keeps a list of absentee
652 jobs that are either deferred or currently
653 running. This list has a capacity of about 13000
654 entries. It is extremely unlikely that this data
655 area will fill up unless some user program has
656 entered a loop and is submitting requests for jobs
657 faster than the jobs are being run.
658
659 Action: Contact the system programming staff.
660
661
662
663 absentee_utility_.pl1
664 absentee_utility_: >sc1>absentee_data will be
665 rebuilt.
666
667
668 Stream: as severity1
669
670 Time: While system is running.
671
672 Meaning: An attempt will be made to rebuild the request
673 lists in absentee_data to correct the error
674 reported by the previous message.
675
676 Action: Note for system programmer action.
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697 absentee_utility_ -12- MR12.5 10/27/92^L
698
699
700 absentee_utility_.pl1
701 absentee_utility_: Absentee processing suspended.
702 Contact system programmer.
703
704
705 Stream: as severity2
706
707 Time: While system is running.
708
709 Meaning: Absentee processing has been suspended because of
710 the error described in the previous message. No
711 more jobs will be started but logged in jobs will
712 continue running. The absentee facility has not
713 been stopped and an "abs start" command will be
714 rejected. After the error has been corrected the
715 "abs start queue N" command may be used to resume
716 the processing of requests from queues unaffected
717 by the error.
718
719 Action: Contact the system programming staff.
720
721
722
723 absentee_utility_.pl1
724 absentee_utility_: Attempt to set defer timer to
725 time in past TIME. Setting it to a minute from
726 now.
727
728
729 Stream: as severity0
730
731 Time: While system is running.
732
733 Meaning: An attempt was made to set the absentee deferred
734 request timer to a time in the past.
735
736 Action: No operator action is required.
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755 absentee_utility_ -13- MR12.5 10/27/92^L
756
757
758 absentee_utility_.pl1
759 absentee_utility_: Attempting to reserve RESOURCE
760 for PERS.PROJ PATH
761
762
763 Stream: as severity2
764
765 Time: While system is running.
766
767 Meaning: An error occurred during the attempt to reserve a
768 resource for an absentee job. The job is deferred
769 and the attempt to reserve the resource is
770 repeated at some later time. The absentee
771 facility continues to operate. There is something
772 wrong with the resource reservation mechanism or
773 with some other part of RCP.
774
775 Action: Contact the system programming staff.
776
777
778
779 absentee_utility_.pl1
780 absentee_utility_: BUG: lc ineligible INDEX
781 not at head of resource list.
782
783
784 Stream: as severity2
785
786 Time: While system is running.
787
788 Meaning: The current absentee request which would be
789 deferred by load control is not at the head of
790 the absentee list. If this occurs there is a
791 logic error in absentee_utility_.
792
793 Action: Contact the system programming staff.
794
795
796
797 absentee_utility_.pl1
798 absentee_utility_: Entry not found. Creating new
799 >sc1>absentee_data
800
801
802 Stream: as severity1
803
804 Time: During startup of the absentee facility.
805
806 Meaning: The absentee data segment was missing and a new
807 one has been created.
808
809 Action: Note for system programmer action.
810
811
812
813 absentee_utility_ -14- MR12.5 10/27/92^L
814
815
816 absentee_utility_.pl1
817 absentee_utility_: Entry not found. Creating new
818 >sc1>absentee_N.ms
819
820
821 Stream: as severity1
822
823 Time: During startup of the absentee facility.
824
825 Meaning: The absentee message segment for queue N was
826 missing and a new one has been created. Any
827 previously submitted absentee jobs in queue N are
828 not executed.
829
830 Action: If the absentee queues never existed or were
831 deliberately deleted or removed this message
832 should be ignored. Otherwise it may be necessary
833 to inform users via the message of the day that
834 the absentee requests for queue N were lost.
835 Contact the system programming staff for help in
836 recovering the queue.
837
838
839
840 absentee_utility_.pl1
841 absentee_utility_: ERROR_MESSAGE Dropping queue
842 >sc1>absentee_N.ms due to M consecutive errors
843
844
845 Stream: as severity2
846
847 Time: While system is running.
848
849 Meaning: This message is printed when a series of errors
850 prevents the absentee facility from reading jobs
851 from a given queue. Absentee requests in queue N
852 are ignored until the absentee facility is stopped
853 and restarted or the command abs start queue N is
854 used to restart the dropped queue.
855
856 Action: Note for system programmer action.
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871 absentee_utility_ -15- MR12.5 10/27/92^L
872
873
874 absentee_utility_.pl1
875 absentee_utility_: ERROR_MESSAGE Truncating
876 absentee_data.
877
878
879 Stream: as severity2
880
881 Time: While system is running.
882
883 Meaning: An error occurred during the attempt to truncate
884 absentee_data prior to rebuilding it. It will not
885 be possible to rebuild it.
886
887 Action: Contact the system programming staff.
888
889
890
891 absentee_utility_.pl1
892 absentee_utility_: ERROR_MESSAGE. Error in
893 creating defer event channel
894
895
896 Stream: as severity2
897
898 Time: During startup of the absentee facility.
899
900 Meaning: The event channel used in processing absentee
901 requests that are deferred until a later time
902 cannot be created. No deferred requests are
903 activated.
904
905 Action: Issue an abs stop command and wait until all
906 absentees run to completion. Then issue an abs
907 start command. If this same message recurs
908 contact the system programming staff.
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929 absentee_utility_ -16- MR12.5 10/27/92^L
930
931
932 absentee_utility_.pl1
933 absentee_utility_: ERROR_MESSAGE. Unable to
934 create >sc1>absentee_data
935
936
937 Stream: as severity2
938
939 Time: During startup of the absentee facility.
940
941 Meaning: The absentee data segment could not be created.
942 Faults will probably occur in the absentee
943 facility if the system attempts to run absentee
944 jobs.
945
946 Action: Notify the system programming staff. Do _^Hn_^Ho_^Ht
947 attempt to run absentee jobs.
948
949
950
951 absentee_utility_.pl1
952 absentee_utility_: ERROR_MESSAGE. Unable to
953 create >sc1>absentee_N.ms
954
955
956 Stream: as severity1
957
958 Time: During startup of the absentee facility.
959
960 Meaning: The absentee message segment for queue N cannot be
961 created. Users cannot queue jobs in queue N and
962 jobs in queue N cannot be executed.
963
964 Action: Contact the system programming staff.
965
966
967
968 absentee_utility_.pl1
969 absentee_utility_: ERROR_MESSAGE. Unable to open
970 new >sc1>absentee_N.ms
971
972
973 Stream: as severity1
974
975 Time: During startup of the absentee facility.
976
977 Meaning: The absentee message segment for queue N just
978 created cannot be found. No absentee jobs are
979 run.
980
981 Action: Contact the system programming staff.
982
983
984
985
986
987 absentee_utility_ -17- MR12.5 10/27/92^L
988
989
990 absentee_utility_.pl1
991 absentee_utility_: ERROR_MESSAGE. Unable to set
992 access on >sc1>absentee_data
993
994
995 Stream: as severity1
996
997 Time: During startup of the absentee facility.
998
999 Meaning: The newly-created segment absentee_data cannot be
1000 given correct access. The system should continue
1001 to run.
1002
1003 Action: Note for system programmer action.
1004
1005
1006
1007 absentee_utility_.pl1
1008 absentee_utility_: ERROR_MESSAGE. Unable to
1009 terminate >sc1>absentee_data
1010
1011
1012 Stream: as severity1
1013
1014 Time: During shutdown of the absentee facility.
1015
1016 Meaning: While shutting down the absentee facility the
1017 system attempted to terminate the segment
1018 absentee_data and received an error. This
1019 condition is not serious.
1020
1021 Action: Note for system programmer action.
1022
1023
1024
1025 absentee_utility_.pl1
1026 absentee_utility_: ERROR_MESSAGE. Attempting to
1027 cancel reservation REQUEST for USER ABSENTEE
1028
1029
1030 Stream: Logged in SYSERR log.
1031
1032 Time: While system is running.
1033
1034 Meaning: An error occurred while cancelling an RCP
1035 reservation for an absentee being deferred.
1036
1037 Action: No operator action is required.
1038
1039
1040
1041
1042
1043
1044
1045 absentee_utility_ -18- MR12.5 10/27/92^L
1046
1047
1048 absentee_utility_.pl1
1049 absentee_utility_: ERROR_MESSAGE. Closing
1050 >sc1>absentee_N.ms
1051
1052
1053 Stream: as severity1
1054
1055 Time: While shutting down the absentee facility.
1056
1057 Meaning: A storage system error occurred as part of the
1058 processing of "abs stop" while attempting to
1059 terminate the absentee message segment for queue
1060 N. Absentee requests for queue N may have been
1061 lost.
1062
1063 Action: If you are shutting down the absentee facility
1064 because of some previous message-segment error
1065 contact the system programming staff and do not
1066 try to restart the absentee facility. If this
1067 absentee shutdown is a normally scheduled one
1068 notify the system programmers of the message and
1069 do not try to restart the absentee facility again
1070 until they have looked at the problem.
1071
1072
1073
1074 absentee_utility_.pl1
1075 absentee_utility_: ERROR_MESSAGE. queue N
1076 >sc1>absentee_N.ms
1077
1078
1079 Stream: as severity1
1080
1081 Time: While system is running.
1082
1083 Meaning: An error occurred while reading rewriting or
1084 deleting a request from queue N. An attempt is
1085 made to correct the error and retry the operation.
1086 Additional messages are printed if this attempt
1087 fails.
1088
1089 Action: Contact the system programming staff.
1090
1091
1092
1093
1094
1095
1096
1097
1098
1099
1100
1101
1102
1103 absentee_utility_ -19- MR12.5 10/27/92^L
1104
1105
1106 absentee_utility_.pl1
1107 absentee_utility_: ERROR_MESSAGE. Searching
1108 queue QUEUE skip list for USER ABSENTEE
1109
1110
1111 Stream: Logged in SYSERR log.
1112
1113 Time: While system is running.
1114
1115 Meaning: An error occurred while searching the skip list
1116 for an absentee request.
1117
1118 Action: No operator action is required.
1119
1120
1121
1122 absentee_utility_.pl1
1123 absentee_utility_: ERROR_MESSAGE. Searching skip
1124 list for USER ABSENTEE
1125
1126
1127 Stream: Logged in SYSERR log.
1128
1129 Time: While system is running.
1130
1131 Meaning: An error occurred while searching the skip list
1132 for an absentee request.
1133
1134 Action: No operator action is required.
1135
1136
1137
1138 absentee_utility_.pl1
1139 absentee_utility_: ERROR_MESSAGE. Sending TYPE
1140 wakeup to PROCID ABS-EVENT
1141
1142
1143 Stream: Logged in SYSERR log.
1144
1145 Time: While system is running.
1146
1147 Meaning: An error occurred while sending an "aum_ctl" or
1148 "login" wakeup to the specified absentee process.
1149
1150 Action: No operator action is required.
1151
1152
1153
1154
1155
1156
1157
1158
1159
1160
1161 absentee_utility_ -20- MR12.5 10/27/92^L
1162
1163
1164 absentee_utility_.pl1
1165 absentee_utility_: ERROR_MESSAGE. Unable to
1166 delete request for USER ABSENTEE; queue: QUEUE;
1167 index: QUEUE_INDEX
1168
1169
1170 Stream: as severity0
1171
1172 Time: While system is running.
1173
1174 Meaning: An error occurred while deleting a request from
1175 the absentee queue.
1176
1177 Action: No operator action is required.
1178
1179
1180
1181 absentee_utility_.pl1
1182 absentee_utility_: ERROR_MESSAGE. Unable to
1183 notify user USER of absentee event.
1184
1185
1186 Stream: Logged in SYSERR log.
1187
1188 Time: While system is running.
1189
1190 Meaning: An error occurred while sending a message to USER
1191 as notification of an absentee event.
1192
1193
1194
1195 absentee_utility_.pl1
1196 absentee_utility_: ERROR_MESSAGE. Unable to set
1197 extended access on >sc1>absentee_N.ms
1198
1199
1200 Stream: as severity1
1201
1202 Time: During startup of the absentee facility.
1203
1204 Meaning: The absentee message segment for queue N just
1205 created cannot be set up so that users can access
1206 it properly. Users will not be able to submit
1207 absentee requests.
1208
1209 Action: Contact the system programming staff.
1210
1211
1212
1213
1214
1215
1216
1217
1218
1219 absentee_utility_ -21- MR12.5 10/27/92^L
1220
1221
1222 absentee_utility_.pl1
1223 absentee_utility_: ERROR_MESSAGE. While reading
1224 message MESSAGE from USER ABSENTEE to be
1225 rewritten.
1226
1227
1228 Stream: Logged in SYSERR log.
1229
1230 Time: While system is running.
1231
1232 Meaning: An error occurred while reading a request from the
1233 absentee queue.
1234
1235 Action: No operator action is required.
1236
1237
1238
1239 absentee_utility_.pl1
1240 absentee_utility_: ERROR_MESSAGE. While reading
1241 message MESSAGE to be rewritten.
1242
1243
1244 Stream: Logged in SYSERR log.
1245
1246 Time: While system is running.
1247
1248 Meaning: An error occurred while reading an absentee
1249 request to be marked as "running".
1250
1251 Action: No operator action is required.
1252
1253
1254
1255 absentee_utility_.pl1
1256 absentee_utility_: Illegal proxy for NAME.PROJ
1257 from NAME1.PROJ1 for job JJJJ
1258
1259
1260 Stream: as severity1
1261
1262 Time: While system is running.
1263
1264 Meaning: This message is printed whenever a proxy absentee
1265 job is submitted by some user who is not allowed
1266 to submit a proxy. User NAME1.PROJ1 submitted job
1267 JJJJ to be run with the user ID NAME.PROJ but the
1268 absentee facility will not do so and ignores the
1269 request.
1270
1271 Action: Note for system programmer action.
1272
1273
1274
1275
1276
1277 absentee_utility_ -22- MR12.5 10/27/92^L
1278
1279
1280 absentee_utility_.pl1
1281 absentee_utility_: Illegal queue number QUEUE
1282 for USER ABSENTEE
1283
1284
1285 Stream: as severity0
1286
1287 Time: While system is running.
1288
1289 Meaning: The queue number specified for the absentee job in
1290 the absentee user table has an illegal value.
1291
1292 Action: No operator action is required.
1293
1294
1295
1296 absentee_utility_.pl1
1297 absentee_utility_: Loop in PROC searching NAME
1298 list for queue N.
1299
1300
1301 Stream: as severity1
1302
1303 Time: While system is running.
1304
1305 Meaning: A software error has damaged the list of requests
1306 in absentee_data. The error was detected by the
1307 internal procedure PROC while searching the NAME
1308 list belonging to queue N. The system makes one
1309 attempt to rebuild the list. Additional messages
1310 are printed if this attempt fails.
1311
1312 Action: Contact the system programming staff.
1313
1314
1315
1316 absentee_utility_.pl1
1317 absentee_utility_: Loop occurred while rebuilding
1318 absentee_data after previous loop.
1319
1320
1321 Stream: as severity2
1322
1323 Time: While system is running.
1324
1325 Meaning: The error reported by the previous message
1326 occurred while absentee_data was being rebuilt
1327 following an earlier error. The rebuild attempt
1328 will not be repeated.
1329
1330 Action: Contact the system programming staff.
1331
1332
1333
1334
1335 absentee_utility_ -23- MR12.5 10/27/92^L
1336
1337
1338 absentee_utility_.pl1
1339 absentee_utility_: rejected request ID PATH in
1340 queue N from PERS.PROJ: REASON
1341
1342
1343 Stream: as severity1
1344
1345 Time: While system is running.
1346
1347 Meaning: This message is printed if a message that appears
1348 to be garbled or meaningless is found in absentee
1349 queue N. The garbled message is ignored. This
1350 condition may be evidence of damage to absentee
1351 queue N unless REASON indicates otherwise.
1352
1353 Action: Note for system programmer action.
1354
1355
1356
1357 absentee_utility_.pl1
1358 absentee_utility_: Timer rang and no deferred
1359 request found.
1360
1361
1362 Stream: as severity0
1363
1364 Time: While system is running.
1365
1366 Meaning: The deferred request timer went off and no
1367 deferred absentee jobs were found.
1368
1369 Action: No operator action is required.
1370
1371
1372
1373 accept_fs_disk.pl1
1374 accept_fs_disk: part NAME on PVNAME dskX_NNS
1375 from AAA for BBB overlaps pages from CCC
1376
1377
1378 Stream: BOS Typewriter.
1379
1380 Time: When accepting a disk volume.
1381
1382 Meaning: The supervisor checks the partitions defined in
1383 the volume label against the beginning of the
1384 paging partition when it accepts a volume. The
1385 partition NAME overlaps the paging area. The
1386 volume label may have been damaged.
1387
1388 Action: Be careful not to destroy the contents of part
1389 NAME since this will destory the contents of user
1390 segments. Note for system programmer action.
1391
1392
1393 accept_fs_disk -24- MR12.5 10/27/92^L
1394
1395
1396 accept_rpv.pl1
1397 accept_rpv: Error ERRORMESSAGE accepting RPV
1398
1399
1400 Stream: BOS Typewriter Crashes system
1401
1402 Time: System Intialization.
1403
1404 Meaning: Some problem was encountered trying to set up the
1405 use of the RPV for normal segment creation and
1406 activation. The label of the RPV may have been
1407 damaged or encountered disk errors as indicated
1408 by the ERRORMESSAGE.
1409
1410 Action: Make sure that the RPV label area first eight
1411 records or a dump of it is available for system
1412 programmer inspection. Note for system programmer
1413 action.
1414
1415 Message: accept_rpv: HC part on dskX_NN used XXX
1416 out of YYY records.
1417
1418 Stream: This message is printed on the console if an HCPT
1419 card is in the config deck. Otherwise it is
1420 logged into the syserr_log.
1421
1422 Time: System Intialization.
1423
1424 Meaning: The message appears for each disk volume which
1425 contains a Hardcore Partition PART HC. It
1426 indicates how many records were actually used
1427 XXX in the partition which had size YYY.
1428
1429 Action: No operator action is required.
1430
1431
1432
1433 accept_rpv.pl1
1434 accept_rpv: pv PVNAME lv LVNAME DSKX_NN is not
1435 part of root.
1436
1437
1438 Stream: BOS Typewriter Crashes system
1439
1440 Time: System Intialization.
1441
1442 Meaning: The pack on the drive DSKX_NN with pv name and lv
1443 name as read from its label is specified on the
1444 ROOT CONFIG card but is not part of the same
1445 logical volume as the RPV.
1446
1447 Action: Check the ROOT CONFIG card for errors. Check for
1448 the proper packs. Reboot the system.
1449
1450
1451 accept_rpv -25- MR12.5 10/27/92^L
1452
1453
1454 access_audit_.pl1
1455 access_audit_$ENTRY: USER_ID Called with
1456 insufficient arguments #args= ^d.
1457 Caller=""CALLING_PROC".
1458
1459
1460 Stream: BOS Typewriter.
1461
1462 Time: While system is running.
1463
1464 Meaning: This indicates a logic error in the supervisor or
1465 CPU or memory hardware problems. access_audit_
1466 was invoked with an improper calling sequence.
1467 There may have been enough arguments to display
1468 the offending caller name.
1469
1470 Action: Contact the system programming staff.
1471
1472
1473
1474 access_audit_.pl1
1475 access_audit_$ENTRY: USER_ID Encountered
1476 illegal meter index. OperCode=XXXXXXXXXXXX
1477 EventFlags=YYYYYYYYYYYY. Caller="CALLING_PROC".
1478
1479
1480 Stream: Logged in SYSERR log.
1481
1482 Time: While system is running.
1483
1484 Meaning: This indicates a logic error in the supervisor or
1485 CPU or memory hardware problems. The access audit
1486 meters in active_hardcore_data are inconsistant
1487 with the format of the process access flags or the
1488 supplied operation code and/or event flags.
1489
1490 Action: Contact the system programming staff.
1491
1492
1493
1494
1495
1496
1497
1498
1499
1500
1501
1502
1503
1504
1505
1506
1507
1508
1509 access_audit_$ENTRY -26- MR12.5 10/27/92^L
1510
1511
1512 access_audit_.pl1
1513 access_audit_$ENTRY: USER_ID Encountered
1514 illegal parameter combination.
1515 OperCode=XXXXXXXXXXXX EventFlags=YYYYYYYYYYYY.
1516 Caller="CALLING_PROC".
1517
1518
1519 Stream: BOS Typewriter.
1520
1521 Time: While system is running.
1522
1523 Meaning: This indicates a logic error in the supervisor or
1524 CPU or memory hardware problems. There is an
1525 error in the access_operations_ entry or the
1526 eventflags passed to access audit. The error was
1527 detected in the code which decides whether the
1528 caller needs to audit its event. Because of the
1529 error the event will be audited regardless of the
1530 process audit flags.
1531
1532 Action: Contact the system programming staff.
1533
1534
1535
1536 access_audit_.pl1
1537 access_audit_$ENTRY: USER_ID Improper calling
1538 sequence from "get_entry_pointer_and_class".
1539 Caller="CALLING_PROC".
1540
1541
1542 Stream: BOS Typewriter.
1543
1544 Time: While system is running.
1545
1546 Meaning: This indicates a logic error in the supervisor or
1547 CPU or memory hardware problems. The entry was
1548 called with an improper argument combination.
1549 Most likely the entry will be log
1550 check_obj_ptr_user and the obj_ptr supplied
1551 will be null.
1552
1553 Action: Contact the system programming staff.
1554
1555
1556
1557
1558
1559
1560
1561
1562
1563
1564
1565
1566
1567 access_audit_$ENTRY -27- MR12.5 10/27/92^L
1568
1569
1570 access_audit_.pl1
1571 access_audit_$ENTRY: USER_ID Unable to generate
1572 path for entry at PTR due to "MESSAGE".
1573 Caller="CALLING_PROC".
1574
1575
1576 Stream: Logged in SYSERR log.
1577
1578 Time: While system is running.
1579
1580 Meaning: This indicates a logic error in the supervisor or
1581 CPU or memory hardware problems. A call to
1582 get_pathname_ returned an unexpected error code.
1583
1584 Action: Contact the system programming staff.
1585
1586
1587
1588 access_audit_.pl1
1589 access_audit_$ENTRY: USER_ID Unable to get
1590 entry pointer for seg #N | PATH due to
1591 "MESSAGE".
1592
1593
1594 Stream: Logged in SYSERR log.
1595
1596 Time: While system is running.
1597
1598 Meaning: This indicates a logic error in the supervisor or
1599 CPU or memory hardware problems. A call to
1600 sum$getbranch_root_my or dc_find$obj_for_audit
1601 returned an unexpected error code.
1602
1603 Action: Contact the system programming staff.
1604
1605
1606
1607 access_audit_.pl1
1608 access_audit_$ENTRY: USER_ID Unable to get raw
1609 access modes for entry PTR due to "MESSAGE".
1610 Caller="CALLER_PROC".
1611
1612
1613 Stream: Logged in SYSERR log.
1614
1615 Time: While system is running.
1616
1617 Meaning: This indicates a logic error in the supervisor or
1618 CPU or memory hardware problems. Although the
1619 directory is locked a failure occurred in
1620 access_mode$raw.
1621
1622 Action: Contact the system programming staff.
1623
1624
1625 access_audit_$ENTRY -28- MR12.5 10/27/92^L
1626
1627
1628 access_audit_.pl1
1629 access_audit_$ENTRY: USER_ID Unable to get UID
1630 path for directory seg #N due to "MESSAGE".
1631 Caller="CALLER_PROC".
1632
1633
1634 Stream: Logged in SYSERR log.
1635
1636 Time: While system is running.
1637
1638 Meaning: This indicates a logic error in the supervisor or
1639 CPU or memory hardware problems. Although the
1640 directory is locked a failure occurred in
1641 uid_path_util$get.
1642
1643 Action: Contact the system programming staff.
1644
1645
1646
1647 access_audit_.pl1
1648 access_audit_$ENTRY: USER_ID Unexpected error
1649 obtaining caller text pointer.
1650 Caller="CALLING_PROC".
1651
1652
1653 Stream: BOS Typewriter.
1654
1655 Time: While system is running.
1656
1657 Meaning: This indicates a logic error in the supervisor or
1658 CPU or memory hardware problems. An error exists
1659 in the calling sequence to access_audit_.
1660
1661 Action: Contact the system programming staff.
1662
1663
1664
1665
1666
1667
1668
1669
1670
1671
1672
1673
1674
1675
1676
1677
1678
1679
1680
1681
1682
1683 access_audit_$ENTRY -29- MR12.5 10/27/92^L
1684
1685
1686 access_audit_.pl1
1687 access_audit_$UNKNOWN: USER_ID Illegal
1688 entrypoint index "N" detected in
1689 form_audit_message_text. Caller="CALLING_PROC".
1690
1691
1692 Stream: BOS Typewriter.
1693
1694 Time: While system is running.
1695
1696 Meaning: This indicates a logic error in the supervisor or
1697 CPU or memory hardware problems. There is a
1698 coding error in access_audit_ where the entrypoint
1699 index is uninitialized or set to an incorrect
1700 value.
1701
1702 Action: Contact the system programming staff.
1703
1704
1705
1706 access_audit_.pl1
1707 access_audit_: Insufficient room to allocate
1708 ssobj|link data.
1709
1710
1711 Stream: BOS Typewriter.
1712
1713 Time: While system is running.
1714
1715 Meaning: This indicates a logic error in the supervisor or
1716 CPU or memory hardware problems. An automatic
1717 data area is too small to accomodate the storage
1718 system object or link binary info.
1719
1720 Action: Contact the system programming staff.
1721
1722
1723
1724 access_audit_log_fault_.pl1
1725 access_audit_log_fault_: USER_ID Unable to get
1726 path of seg #N due to "MESSAGE".
1727
1728
1729 Stream: BOS Typewriter.
1730
1731 Time: While system is running.
1732
1733 Meaning: This indicates a logic error in the supervisor or
1734 CPU or memory hardware problems. A call to
1735 get_pathname_ returned an unexpected error code.
1736
1737 Action: Contact the system programming staff.
1738
1739
1740
1741 access_audit_log_fault_ -30- MR12.5 10/27/92^L
1742
1743
1744 access_audit_log_fault_.pl1
1745 access_audit_log_fault_: USER_ID Called with
1746 bad machine conditions.
1747
1748
1749 Stream: BOS Typewriter.
1750
1751 Time: While system is running.
1752
1753 Meaning: This indicates a logic error in the supervisor or
1754 CPU or memory hardware problems.
1755 access_audit_log_fault_ was given machine
1756 conditions for a fault which was neither an
1757 illegal_procedure or an access_violation.
1758
1759 Action: Contact the system programming staff.
1760
1761
1762
1763 access_audit_log_fault_.pl1
1764 access_audit_log_fault_: USER_ID Encountered
1765 illegal meter index value.
1766
1767
1768 Stream: BOS Typewriter.
1769
1770 Time: While system is running.
1771
1772 Meaning: This indicates a logic error in the supervisor or
1773 CPU or memory hardware problems. The access audit
1774 meters in active_hardcore_data are inconsistant
1775 with the format of the process access flags.
1776
1777 Action: Contact the system programming staff.
1778
1779
1780
1781
1782
1783
1784
1785
1786
1787
1788
1789
1790
1791
1792
1793
1794
1795
1796
1797
1798
1799 access_audit_log_fault_ -31- MR12.5 10/27/92^L
1800
1801
1802 access_audit_log_fault_.pl1
1803 access_audit_log_fault_: USER_ID Unable to get
1804 access mode for data seg #N due to "MESSAGE".
1805
1806
1807 Stream: BOS Typewriter.
1808
1809 Time: While system is running.
1810
1811 Meaning: This indicates a logic error in the supervisor or
1812 CPU or memory hardware problems. A call to
1813 fs_modes failed unexpectedly. The AUDIT message
1814 text will show the modes as "???" and ring
1815 brackets of 777. The message binary will
1816 reflect null access mode and ring bracket of
1817 777.
1818
1819 Action: Contact the system programming staff.
1820
1821
1822
1823 access_audit_log_fault_.pl1
1824 access_audit_log_fault_: USER_ID Unable to get
1825 entry pointer for seg #N due to "MESSAGE".
1826
1827
1828 Stream: BOS Typewriter.
1829
1830 Time: While system is running.
1831
1832 Meaning: This indicates a logic error in the supervisor or
1833 CPU or memory hardware problems. A call to
1834 sum$getbranch_root_my returned an unexpected error
1835 code.
1836
1837 Action: Contact the system programming staff.
1838
1839
1840
1841
1842
1843
1844
1845
1846
1847
1848
1849
1850
1851
1852
1853
1854
1855
1856
1857 access_audit_log_fault_ -32- MR12.5 10/27/92^L
1858
1859
1860 access_audit_log_fault_.pl1
1861 access_audit_log_fault_: USER_ID Unable to get
1862 raw access modes for entry PTR due to "MESSAGE".
1863
1864
1865 Stream: BOS Typewriter.
1866
1867 Time: While system is running.
1868
1869 Meaning: This indicates a logic error in the supervisor or
1870 CPU or memory hardware problems. Although the
1871 directory is locked a failure occurred in
1872 access_mode$raw.
1873
1874 Action: Contact the system programming staff.
1875
1876
1877
1878 access_audit_log_fault_.pl1
1879 access_audit_log_fault_: USER_ID Unable to get
1880 UID path for directory seg #N due to "MESSAGE".
1881
1882
1883 Stream: BOS Typewriter.
1884
1885 Time: While system is running.
1886
1887 Meaning: This indicates a logic error in the supervisor or
1888 CPU or memory hardware problems. Although the
1889 directory is locked a failure occurred in
1890 uid_path_util$get.
1891
1892 Action: Contact the system programming staff.
1893
1894
1895
1896 access_audit_log_fault_.pl1
1897 access_audit_log_fault_: Link entry where branch
1898 expected ep=PTR.
1899
1900
1901 Stream: BOS Typewriter Crashes system
1902
1903 Time: While system is running.
1904
1905 Meaning: This indicates a logic error in the supervisor or
1906 CPU or memory hardware problems. After getting a
1907 directory entry for a specific segno the branch
1908 switch in the entry was found to be off.
1909
1910 Action: Follow normal recovery procedures.
1911
1912
1913
1914
1915 access_audit_log_fault_ -33- MR12.5 10/27/92^L
1916
1917
1918 access_viol.pl1
1919 access_viol: associative memory fault.
1920
1921
1922 Stream: BOS Typewriter Crashes system
1923
1924 Time: While system is running.
1925
1926 Meaning: The processor associative memory has detected a
1927 usage count error.
1928
1929 Action: Notify Field Engineering personnel.
1930
1931
1932
1933 bound_segment_control.s.archiv.1
1934 access_viol: associative memory fault.
1935
1936
1937 Stream: BOS Typewriter Crashes system
1938
1939 Time: While system is running.
1940
1941 Meaning: The processor associative memory has detected a
1942 usage count error.
1943
1944 Action: Notify Field Engineering personnel.
1945
1946
1947
1948 act_ctl_.pl1
1949 act_ctl_$dp: Net accounting array version
1950 VERSION_RETURNED not supported. Expected
1951 version VERSION_SUPPORTED
1952
1953
1954 Stream: as severity2.
1955
1956 Time: While system is running.
1957
1958 Meaning: network_accounting_gate_$read_and_reset_table
1959 returned a structure version which act_ctl_ does
1960 not support. This indicates a logic error in the
1961 supervisor or CPU or memory hardware problems.
1962
1963 Action: $contact_sm
1964
1965
1966
1967
1968
1969
1970
1971
1972
1973 act_ctl_$dp -34- MR12.5 10/27/92^L
1974
1975
1976 act_ctl_.pl1
1977 act_ctl_$init: cannot locate
1978 Initializer.SysDaemon pdt entry
1979
1980
1981 Stream: as severity2
1982
1983 Time: System Intialization.
1984
1985 Meaning: The accounting system requires the entry for
1986 Initializer in the project SysDaemon to be present
1987 because certain system metering figures are kept
1988 there. This entry cannot be found either because
1989 SysDaemon.pdt has been lost or because its
1990 contents have been destroyed. The system will
1991 probably encounter a simfault_xxx error and be
1992 unable to start up.
1993
1994 Action: Contact the system programming staff. Do not
1995 attempt to run the system until this problem has
1996 been fixed.
1997
1998
1999
2000 act_ctl_.pl1
2001 act_ctl_$init: ERROR_MESSAGE. Cannot unlock PDT
2002 PATHNAME.
2003
2004
2005 Stream: as severity2
2006
2007 Time: System Intialization.
2008
2009 Meaning: This message occurs during answering service
2010 initialization when attempting to unlock all PDTs.
2011 ERROR_MESSAGE specifies the the reason for the
2012 problem. The PDT is skipped. Later problems may
2013 arise because of this error.
2014
2015 Action: Contact the system programming staff.
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
2027
2028
2029
2030
2031 act_ctl_$init -35- MR12.5 10/27/92^L
2032
2033
2034 act_ctl_.pl1
2035 act_ctl_$init: ERROR_MESSAGE. creating update
2036 channel
2037
2038
2039 Stream: as severity2
2040
2041 Time: System Intialization.
2042
2043 Meaning: The timer channel that causes accounting updates
2044 to be performed could not be created. All
2045 accounting updates will be manual triggered by a
2046 user logging out.
2047
2048 Action: Contact the system programming staff.
2049
2050
2051
2052 act_ctl_.pl1
2053 act_ctl_$init: illegal value DD for accounting
2054 update interval in installation_parms.
2055
2056
2057 Stream: as severity2
2058
2059 Time: System Intialization.
2060
2061 Meaning: The value given in installation_parms.acct_update
2062 is less than or equal to zero. The
2063 installation_parms file is probabily damaged.
2064
2065 Action: Contact the system programming staff. Do not
2066 attempt to run the system until this problem has
2067 been fixed.
2068
2069
2070
2071
2072
2073
2074
2075
2076
2077
2078
2079
2080
2081
2082
2083
2084
2085
2086
2087
2088
2089 act_ctl_$init -36- MR12.5 10/27/92^L
2090
2091
2092 act_ctl_.pl1
2093 act_ctl_$init: The PDT is damaged. Cannot unlock
2094 PATHNAME.
2095
2096
2097 Stream: as severity2
2098
2099 Time: System Intialization.
2100
2101 Meaning: This message occurs during answering service
2102 initialization when attempting to unlock all PDTs.
2103 The specified PDT had its damaged switch turned
2104 on. Because of this it was not unlocked from the
2105 previous bootload. It is skipped. Later problems
2106 may arise when an attempt is made to reference
2107 this PDT.
2108
2109 Action: Contact the system programming staff.
2110
2111
2112
2113 act_ctl_.pl1
2114 act_ctl_$update: Error from ROUTINE: MESSAGE
2115
2116
2117 Stream: as severity2.
2118
2119 Time: While system is running.
2120
2121 Meaning: The system encountered problems while referencing
2122 the
2123 network_accounting_table. The
2124 network_accounting_ ROUTINE being
2125 called and MESSAGE text further describe
2126 the error.
2127
2128 Action: Contact the system programming staff.
2129
2130
2131
2132
2133
2134
2135
2136
2137
2138
2139
2140
2141
2142
2143
2144
2145
2146
2147 act_ctl_$update -37- MR12.5 10/27/92^L
2148
2149
2150 act_ctl_.pl1
2151 act_ctl_$update: Net accounting array version
2152 VERSION_RETURNED not supported. Expected
2153 version VERSION_SUPPORTED
2154
2155
2156 Stream: as severity2.
2157
2158 Time: While system is running.
2159
2160 Meaning: network_accounting_gate_$read_and_reset_table
2161 returned a structure version which act_ctl_ does
2162 not support. This indicates a logic error in the
2163 supervisor or CPU or memory hardware problems.
2164
2165 Action: $contact_sm
2166
2167
2168
2169 act_ctl_.pl1
2170 act_ctl_$update: Processid XXXXXXXX missing. Not
2171 charged for XX pkt YY byte and ZZ seconds;
2172 was/was not purged.
2173
2174
2175 Stream: as severity2
2176
2177 Time: While system is running.
2178
2179 Meaning: After charging network accounting usage for all
2180 users on the system an entry was found for
2181 processid XXXXXXXX. The XX YY and ZZ are counts
2182 of the usage which the process had. If the entry
2183 was for a process which is no longer logged in
2184 the accounting record was purged from the network
2185 accounting file.
2186
2187 Action: Note for system programmer action.
2188
2189
2190
2191 act_ctl_.pl1
2192 act_ctl_: accounting disabled
2193
2194
2195 Stream: as severity1
2196
2197 Time: May occur at any time.
2198
2199 Meaning: The accounting system has been disabled by a call
2200 to act_ctl_$act_ctl_disable.
2201
2202 Action: No operator action is required.
2203
2204
2205 act_ctl_ -38- MR12.5 10/27/92^L
2206
2207
2208 act_ctl_.pl1
2209 act_ctl_: accounting enabled.
2210
2211
2212 Stream: as severity1
2213
2214 Time: May occur at any time.
2215
2216 Meaning: The accounting system has been enabled probably
2217 after a special session by a call to
2218 act_ctl_$act_ctl_reable.
2219
2220 Action: No operator action is required.
2221
2222
2223
2224 act_ctl_.pl1
2225 act_ctl_: alarm clock late or failing by XX.XX
2226 mins
2227
2228
2229 Stream: as severity1
2230
2231 Time: While system is running.
2232
2233 Meaning: The alarm clock channel has not caused an
2234 accounting update to be performed when it was due.
2235 The time between updates is stored in the segment
2236 installation_parms. The system performs a manual
2237 accounting update. This message may appear if the
2238 system has entered BOS and Multics has then been
2239 restarted by the GO command. In such case the
2240 message can be ignored.
2241
2242 Action: Note for system programmer action.
2243
2244
2245
2246 act_ctl_.pl1
2247 act_ctl_: bumping absNN NAME.PROJ - inactive too
2248 long
2249
2250
2251 Stream: as severity1
2252
2253 Time: While system is running.
2254
2255 Meaning: The absentee job on absentee slot NN for user
2256 NAME.PROJ has remained blocked too long. The
2257 inactive time limit is stored in the segment
2258 installation_parms. The absentee job is bumped.
2259
2260 Action: No operator action is required.
2261
2262
2263 act_ctl_ -39- MR12.5 10/27/92^L
2264
2265
2266 act_ctl_.pl1
2267 act_ctl_: bumping absXX NAME.PROJ - too much time
2268
2269
2270 Stream: as severity1
2271
2272 Time: While system is running.
2273
2274 Meaning: The absentee job on absentee slot XX for the user
2275 NAME.PROJ has exceeded the CPU time limit for the
2276 queue. This limit is stored in the segment
2277 installation_parms. The absentee job is bumped.
2278
2279 Action: No operator action is required.
2280
2281
2282
2283 act_ctl_.pl1
2284 act_ctl_: bumping NAME.PROJ for inactivity
2285
2286
2287 Stream: as severity1
2288
2289 Time: While system is running.
2290
2291 Meaning: The user with name NAME and project PROJ has been
2292 inactive too long and is bumped off the system.
2293 The maximum inactive time is stored in the segment
2294 installation_parms.
2295
2296 Action: No operator action is required.
2297
2298
2299
2300 act_ctl_.pl1
2301 act_ctl_: bumping NAME.PROJ. REASON
2302
2303
2304 Stream: as severity1
2305
2306 Time: While system is running.
2307
2308 Meaning: The user with name NAME and project PROJ has been
2309 bumped because some per-user limit has been
2310 exceeded. REASON tells what was wrong; it will be
2311 a message such as "User resource limit of $100
2312 monthly exceeded" depending on which user limit
2313 has been exceeded.
2314
2315 Action: No operator action is required.
2316
2317
2318
2319
2320
2321 act_ctl_ -40- MR12.5 10/27/92^L
2322
2323
2324 act_ctl_.pl1
2325 act_ctl_: changing shift from x to y
2326
2327
2328 Stream: as severity1
2329
2330 Time: While system is running.
2331
2332 Meaning: The current accounting shift has changed. The
2333 table that tells the beginning time for each shift
2334 is stored in the segment installation_parms.
2335
2336 Action: No operator action is required.
2337
2338
2339
2340 act_ctl_.pl1
2341 act_ctl_: charged X available Y mins
2342
2343
2344 Stream: as severity0
2345
2346 Time: While system is running.
2347
2348 Meaning: X is the sum of virtual CPU time charged to all
2349 processes and Y is the total virtual CPU time used
2350 by all processes. This message logs detailed
2351 accounting information and appears whenever the
2352 message "act_ctl_: discrepancy of XX.XX mins"
2353 appears.
2354
2355 Action: No operator action is required.
2356
2357
2358
2359 act_ctl_.pl1
2360 act_ctl_: discrepancy of XX.XX mins
2361
2362
2363 Stream: as severity1
2364
2365 Time: While system is running.
2366
2367 Meaning: The total time available from traffic control does
2368 not agree with the total time charged to users
2369 plus the Initializer time plus the idle time.
2370 Some process has escaped being accounted for.
2371
2372 Action: Contact the system administrator.
2373
2374
2375
2376
2377
2378
2379 act_ctl_ -41- MR12.5 10/27/92^L
2380
2381
2382 act_ctl_.pl1
2383 act_ctl_: Lock wait time exceeded. While
2384 destroying proc for NAME.PROJ
2385
2386
2387 Stream: as severity2
2388
2389 Time: While system is running.
2390
2391 Meaning: The accounting system was unable to lock the PDT
2392 entry for the user NAME in the project PROJ within
2393 its time limit usually five minutes This user
2394 attempted to log out or destroy a process. The
2395 entry was probably locked because a system
2396 administrator or daemon process locked the entry
2397 and then failed. The system attempts to continue.
2398
2399 Action: Contact the system administrator.
2400
2401
2402
2403 act_ctl_.pl1
2404 act_ctl_: MODE update: users = NN pf=XX
2405 vcpu=YY.Y rt=ZZ.Z MESSAGE
2406
2407
2408 Stream: as severity1
2409
2410 Time: While system is running.
2411
2412 Meaning: Periodically the accounting programs read and
2413 store the CPU usage for each user. This message
2414 is printed when the update completes. MODE may be
2415 'Automatic' in which case the update occurred at
2416 the normal system parameter time; 'Manual' where
2417 the normal update didn't occur; or 'Shift Cmnd'
2418 where the update occurred due to a shift command.
2419 XX is the number of page faults taken by
2420 Initializer for update. YY.Y is the virtual CPU
2421 time taken by Initializer for update. ZZ.Z is the
2422 real time taken by Initializer for update.
2423 MESSAGE may be one or both of the following
2424 strings: 'answer table locked' or 'installs
2425 pending'
2426
2427 Action: No operator action is required. The number of
2428 seconds between accounting updates is a system
2429 parameter that an installation may change; it is
2430 stored in the segment installation_parms.
2431
2432
2433
2434
2435
2436
2437 act_ctl_ -42- MR12.5 10/27/92^L
2438
2439
2440 act_ctl_.pl1
2441 act_ctl_: process XXXXXXXXXXXX for NAME.PROJ
2442 vanished
2443
2444
2445 Stream: as severity2
2446
2447 Time: While system is running.
2448
2449 Meaning: Traffic control cannot locate a process for a user
2450 who should have one according to accounting. The
2451 system attempts to run normally but this user is
2452 not charged. An attempt is made to bump the user
2453 in question. This may be the first indication
2454 that the segment >system_control_1>answer_table
2455 has been damaged.
2456
2457 Action: Note for system programmer action.
2458
2459
2460
2461 act_ctl_.pl1
2462 act_ctl_: shutdown NNN WW.WW XX.XX YY.YY ZZ.ZZ
2463 HH:MM:SS $DDD.DD
2464
2465
2466 Stream: as severity1
2467
2468 Time: System shutdown.
2469
2470 Meaning: A successful shutdown of the accounting portion of
2471 the system has been accomplished. NNN logins were
2472 recorded for a total usage of HH:MM:SS of CPU
2473 time charged. The other numbers are of interest
2474 to system administrators and programmers. WW.WW
2475 is the average queue length XX.XX is the average
2476 eligible YY.YY is the thrashing index ZZ.ZZ is
2477 the average response and DDD.DD is the total
2478 dollar charge since startup. A shutdown of the
2479 hardcore system follows this message.
2480
2481 Action: No operator action is required.
2482
2483
2484
2485
2486
2487
2488
2489
2490
2491
2492
2493
2494
2495 act_ctl_ -43- MR12.5 10/27/92^L
2496
2497
2498 act_ctl_.pl1
2499 act_ctl_: STRING for USER.PROJ is negative NUM
2500 at logout;
2501 set it to zero.
2502
2503
2504 Stream: as severity2
2505
2506 Time: While system is running.
2507
2508 Meaning: A counter value of STRING was decremented by 1 and
2509 went negative. It was noticed when attempting to
2510 log out USER on the PROJ project. This is a sign
2511 of possible damage to the PROJ pdt.
2512
2513 Action: Note for system programmer action.
2514
2515
2516
2517 act_proc.pl1
2518 act_proc: from grab_aste ERRORMESSAGE
2519
2520
2521 Stream: BOS Typewriter Crashes system
2522
2523 Time: While system is running.
2524
2525 Meaning: In attempting to create a process the system
2526 could not force the PDS or descriptor segment of
2527 that process to be activated and held active.
2528 ERRORMESSAGE is an error_table_ message. This
2529 indicates a logic error in the supervisor or CPU
2530 or memory hardware problems.
2531
2532 Action: Follow normal recovery procedures.
2533
2534
2535
2536
2537
2538
2539
2540
2541
2542
2543
2544
2545
2546
2547
2548
2549
2550
2551
2552
2553 act_proc -44- MR12.5 10/27/92^L
2554
2555
2556 act_proc.pl1
2557 act_proc: KST size specified SIZE less than
2558 minimum MIN_SIZE. Creating process for GROUPID.
2559
2560
2561 Stream: Logged in SYSERR log.
2562
2563 Time: While system is running.
2564
2565 Meaning: The project administrator or system
2566 administrator for user GROUPID set the kst_size
2567 parameter in the PDT to SIZE which is less than
2568 the valid minimum MIN_SIZE. The process is not
2569 created. Note that a process with MINIMUM KST
2570 size will probably not be of any use. The minimum
2571 useful KST size is on the order of MINIMUM + 50.
2572
2573 Action: Change the PMF/PDT.
2574
2575
2576
2577 activate.pl1
2578 activate: activating into father PPPP
2579
2580
2581 Stream: BOS Typewriter Crashes system
2582
2583 Time: While system is running.
2584
2585 Meaning: The AST entry pointer returned by get_aste is
2586 identical to the AST entry pointer for the parent
2587 of the segment being activated. This indicates a
2588 logic error in the supervisor or CPU or memory
2589 hardware problems. This error crashes the system.
2590
2591 Action: Follow normal recovery procedures.
2592
2593
2594
2595
2596
2597
2598
2599
2600
2601
2602
2603
2604
2605
2606
2607
2608
2609
2610
2611 activate -45- MR12.5 10/27/92^L
2612
2613
2614 activate.pl1
2615 activate: error on deciduous dir NAME
2616
2617
2618 Stream: Logged in SYSERR log.
2619
2620 Time: While system is running.
2621
2622 Meaning: An attempt has been made to activate a deciduous
2623 segment or to activate a segment when the VTOCE's
2624 directory switch did not match the branch. A
2625 connection failure is returned to the user
2626 process. This information is logged for the use
2627 of system programmers.
2628
2629 Action: No operator action is required.
2630
2631
2632
2633 activate.pl1
2634 activate: Setting damaged switch on NAME at VTOCX
2635 dskX_NNs. Filemap damaged.
2636
2637
2638 Stream: Logged in SYSERR log.
2639
2640 Time: While system is running.
2641
2642 Meaning: The segment's File Map in the VTOCE had an invalid
2643 checksum which indicates likely damage to the
2644 File Map. The segment is marked as damaged. It
2645 is possible that there is other damage on the
2646 physical volume due to invalid or reused disk
2647 addresses. The count of volume inconsistencies is
2648 incremented by 1.
2649
2650 Action: Examine the VTOCE for damage using dump_vtoce. If
2651 other damage is evident delete it using
2652 hp_delete_vtoce -clear and recover the segment.
2653 Run the physical volume scavenger as soon as
2654 possible to detect and correct other damage on the
2655 physical volume.
2656
2657
2658
2659
2660
2661
2662
2663
2664
2665
2666
2667
2668
2669 activate -46- MR12.5 10/27/92^L
2670
2671
2672 obs_reconfigure.pl1
2673 addcpu: Associative memories not enabled on CPU
2674 X.
2675
2676
2677 Stream: Initializer process output.
2678
2679 Time: In response to an operator command.
2680
2681 Meaning: The SDWAM and/or PTWAM on CPU X is not enabled.
2682 CPU X was not added.
2683
2684 Action: Set the appropriate associative memory switch on
2685 and try addcpu again.
2686
2687
2688
2689 obs_reconfigure.pl1
2690 addcpu: CPU X is already online.
2691
2692
2693 Stream: Initializer process output.
2694
2695 Time: In response to an operator command.
2696
2697 Meaning: A redundant addcpu X command was issued. No
2698 action was taken.
2699
2700 Action: Enter a corrected command line.
2701
2702
2703
2704 obs_reconfigure.pl1
2705 addcpu: CPU X is not configured.
2706
2707
2708 Stream: Initializer process output.
2709
2710 Time: In response to an operator command.
2711
2712 Meaning: There is no CPU card for CPU X in the
2713 configuration deck. The CPU cannot be added.
2714
2715 Action: If the CPU name was mistyped enter a corrected
2716 command. If the configuration deck omitted the
2717 CPU card that CPU cannot be added until the
2718 system is shut down and the deck corrected.
2719
2720
2721
2722
2723
2724
2725
2726
2727 addcpu -47- MR12.5 10/27/92^L
2728
2729
2730 obs_reconfigure.pl1
2731 addcpu: CPU X is not enabled at MEM Y.
2732
2733
2734 Stream: Initializer process output.
2735
2736 Time: In response to an operator command.
2737
2738 Meaning: CPU X cannot be added because the PORT ENABLE
2739 switch at MEM Y does not enable it.
2740
2741 Action: Fix the switches and try addcpu again.
2742
2743
2744
2745 obs_reconfigure.pl1
2746 addcpu: CPU X is not in Multics mode.
2747
2748
2749 Stream: Initializer process output.
2750
2751 Time: In response to an operator command.
2752
2753 Meaning: CPU X cannot be added because its mode switch is
2754 wrong.
2755
2756 Action: Fix the switch and try again.
2757
2758
2759
2760 obs_reconfigure.pl1
2761 addcpu: Illegal command or subroutine argument.
2762 BLAH
2763
2764
2765 Stream: Initializer process output.
2766
2767 Time: In response to an operator command.
2768
2769 Meaning: Invalid input was typed.
2770
2771 Action: Enter a corrected command line.
2772
2773
2774
2775
2776
2777
2778
2779
2780
2781
2782
2783
2784
2785 addcpu -48- MR12.5 10/27/92^L
2786
2787
2788 obs_reconfigure.pl1
2789 addcpu: Lockup fault trying to start CPU X.
2790
2791
2792 Stream: Initializer process output.
2793
2794 Time: In response to an operator command.
2795
2796 Meaning: This happens occasionally. The reason for it is
2797 unknown.
2798
2799 Action: Try addcpu a few more times.
2800
2801
2802
2803 obs_reconfigure.pl1
2804 addcpu: No response from CPU X.
2805
2806
2807 Stream: Initializer process output.
2808
2809 Time: In response to an operator command.
2810
2811 Meaning: CPU X did not start up when commanded. It may be
2812 malfunctioning or in STEP.
2813
2814 Action: Check the switches. If any are wrong correct
2815 them and retry addcpu. Otherwise notify Field
2816 Engineering.
2817
2818
2819
2820 obs_reconfigure.pl1
2821 addcpu: Reconfiguration database is locked.
2822
2823
2824 Stream: Initializer process output.
2825
2826 Time: In response to an operator command.
2827
2828 Meaning: Another process is performing reconfiguration
2829 currently or a fault during reconfiguration has
2830 left the reconfiguration tables locked.
2831
2832 Action: If it is certain that no other process is
2833 reconfiguring and that the fault which
2834 interrupted reconfiguration has been cured the
2835 reconfigure$force_unlock command may be used to
2836 clear the lock at the direction of system staff.
2837
2838
2839
2840
2841
2842
2843 addcpu -49- MR12.5 10/27/92^L
2844
2845
2846 obs_reconfigure.pl1
2847 addcpu: Startup fault trying to start CPU X.
2848
2849
2850 Stream: Initializer process output.
2851
2852 Time: In response to an operator command.
2853
2854 Meaning: This happens sometimes. Nobody knows why.
2855
2856 Action: Try again a few times.
2857
2858
2859
2860 obs_reconfigure.pl1
2861 addcpu: The following switches on CPU X are set
2862 incorrectly:
2863 Fault Base
2864 Processor Number
2865 Port Assignment MEM Y
2866 Port Enable MEM Y
2867 Interlace MEM Y
2868 Size MEM Y
2869 Half/Full MEM Y
2870
2871
2872 Stream: Initializer process output.
2873
2874 Time: In response to an operator command.
2875
2876 Meaning: The listed switches are set incorrectly.
2877
2878 Action: Correct the switches and try addcpu again.
2879
2880
2881
2882 obs_reconfigure.pl1
2883 addcpu: Trouble fault trying to start CPU X.
2884
2885
2886 Stream: Initializer process output.
2887
2888 Time: In response to an operator command.
2889
2890 Meaning: This happens sometimes. Nobody knows why.
2891
2892 Action: Try again a few times.
2893
2894
2895
2896
2897
2898
2899
2900
2901 addcpu -50- MR12.5 10/27/92^L
2902
2903
2904 obs_reconfigure.pl1
2905 addcpu: Wrong number of arguments supplied.
2906
2907
2908 Stream: Initializer process output.
2909
2910 Time: In response to an operator command.
2911
2912 Meaning: Invalid input was typed.
2913
2914 Action: Enter a corrected command line.
2915
2916
2917
2918 obs_reconfigure.pl1
2919 Added frame XXX.
2920
2921
2922 Stream: Initializer process output.
2923
2924 Time: In response to an operator command.
2925
2926 Meaning: This is the response to a successful addmain XXX
2927 command.
2928
2929 Action: No operator action is required.
2930
2931
2932
2933 obs_reconfigure.pl1
2934 Added frames XXX thru YYY.
2935
2936
2937 Stream: Initializer process output.
2938
2939 Time: In response to an operator command.
2940
2941 Meaning: This is the response to a successful addmain XXX N
2942 command.
2943
2944 Action: No operator action is required.
2945
2946
2947
2948
2949
2950
2951
2952
2953
2954
2955
2956
2957
2958
2959 Added frames XXX thru YYY. -51- MR12.5 10/27/92^L
2960
2961
2962 disk_table_.pl1
2963 added pv PVNAME to mounted lv LVNAME.
2964
2965
2966 Stream: Initializer process output.
2967
2968 Time: While system is running.
2969
2970 Meaning: An av command was used to increase the size of a
2971 mounted volume.
2972
2973 Action: No operator action is required.
2974
2975
2976
2977 obs_reconfigure.pl1
2978 Added SCU X and its memory.
2979
2980
2981 Stream: Initializer process output.
2982
2983 Time: In response to an operator command.
2984
2985 Meaning: This is the response to a successful addmem X
2986 command.
2987
2988 Action: No operator action is required.
2989
2990
2991
2992 obs_reconfigure.pl1
2993 Added SCU's X and Y interlaced and their memory.
2994
2995
2996 Stream: Initializer process output.
2997
2998 Time: In response to an operator command.
2999
3000 Meaning: This is the response to a successful addmem X
3001 command when SCU's X and Y have their memories
3002 interlaced.
3003
3004 Action: No operator action is required.
3005
3006
3007
3008
3009
3010
3011
3012
3013
3014
3015
3016
3017 Added SCU's X and Y inter -52- MR12.5 10/27/92^L
3018
3019
3020 obs_reconfigure.pl1
3021 addmain: Illegal command or subroutine argument.
3022 BLAH
3023
3024
3025 Stream: Initializer process output.
3026
3027 Time: In response to an operator command.
3028
3029 Meaning: Invalid input was typed.
3030
3031 Action: Enter a corrected command line.
3032
3033
3034
3035 obs_reconfigure.pl1
3036 addmain: Reconfiguration database is locked.
3037
3038
3039 Stream: Initializer process output.
3040
3041 Time: In response to an operator command.
3042
3043 Meaning: Another process is performing reconfiguration
3044 currently or a fault during reconfiguration has
3045 left the reconfiguration tables locked.
3046
3047 Action: If it is certain that no other process is
3048 reconfiguring and that the fault which
3049 interrupted reconfiguration has been cured the
3050 reconfigure$force_unlock command may be used to
3051 clear the lock at the direction of system staff.
3052
3053
3054
3055 obs_reconfigure.pl1
3056 addmain: Request is not within range of a single
3057 controller. MAIN XXX
3058
3059
3060 Stream: Initializer process output.
3061
3062 Time: In response to an operator command.
3063
3064 Meaning: An addmain command must specify memory completely
3065 within the range of a single controller.
3066
3067 Action: Enter a corrected command line.
3068
3069
3070
3071
3072
3073
3074
3075 addmain -53- MR12.5 10/27/92^L
3076
3077
3078 obs_reconfigure.pl1
3079 addmain: Wrong number of arguments supplied.
3080
3081
3082 Stream: Initializer process output.
3083
3084 Time: In response to an operator command.
3085
3086 Meaning: Invalid input was typed.
3087
3088 Action: Enter a corrected command line.
3089
3090
3091
3092 add_scu.pl1
3093 addmem: Added MEM X.
3094
3095
3096 Stream: BOS Typewriter.
3097
3098 Time: In response to an operator command.
3099
3100 Meaning: The system control unit X has been added.
3101
3102 Action: No operator action is required.
3103
3104
3105
3106 obs_reconfigure.pl1
3107 addmem: Illegal command or subroutine argument.
3108 BLAH
3109
3110
3111 Stream: Initializer process output.
3112
3113 Time: In response to an operator command.
3114
3115 Meaning: Invalid input was typed.
3116
3117 Action: Enter a corrected command line.
3118
3119
3120
3121
3122
3123
3124
3125
3126
3127
3128
3129
3130
3131
3132
3133 addmem -54- MR12.5 10/27/92^L
3134
3135
3136 obs_reconfigure.pl1
3137 addmem: MEM Y cannot be accessed by CPU X.
3138
3139
3140 Stream: Initializer process output.
3141
3142 Time: In response to an operator command.
3143
3144 Meaning: CPU X is unable to access MEM Y. The
3145 configuration deck may be incorrect or the CPU
3146 and SCU switches may be in the wrong settings.
3147
3148 Action: Check the switches and make sure that they agree
3149 with the configuration deck. Then try addmem
3150 again.
3151
3152
3153
3154 obs_reconfigure.pl1
3155 addmem: MEM Y does not have mask assigned to CPU
3156 X.
3157
3158
3159 Stream: Initializer process output.
3160
3161 Time: In response to an operator command.
3162
3163 Meaning: The MASK/PORT ASSIGNMENT 4MW SCU or EXECUTE
3164 INTERRUPT MASK ASSIGNMENT 6000 SCU switches on
3165 SCU Y are incorrect.
3166
3167 Action: Fix the switches and try addmem again.
3168
3169
3170
3171 obs_reconfigure.pl1
3172 addmem: MEM Y has duplicate mask assignments to
3173 CPU X.
3174
3175
3176 Stream: Initializer process output.
3177
3178 Time: In response to an operator command.
3179
3180 Meaning: The MASK/PORT ASSIGNMENT 4MW SCU or EXECUTE
3181 INTERRUPT MASK ASSIGNMENT 6000 SCU switches on
3182 SCU Y are incorrect.
3183
3184 Action: Fix the switches and try addmem again.
3185
3186
3187
3188
3189
3190
3191 addmem -55- MR12.5 10/27/92^L
3192
3193
3194 obs_reconfigure.pl1
3195 addmem: MEM Y has mask Z assigned to non-CPU
3196 port.
3197
3198
3199 Stream: Initializer process output.
3200
3201 Time: In response to an operator command.
3202
3203 Meaning: The MASK/PORT ASSIGNMENT 4MW SCU or EXECUTE
3204 INTERRUPT MASK ASSIGNMENT 6000 SCU switches on
3205 SCU Y are incorrect.
3206
3207 Action: Fix the switches and try addmem again.
3208
3209
3210
3211 obs_reconfigure.pl1
3212 addmem: MEM Y is already online.
3213
3214
3215 Stream: Initializer process output.
3216
3217 Time: In response to an operator command.
3218
3219 Meaning: An addmem Y command was typed when SCU Y was
3220 already online.
3221
3222 Action: No operator action is required.
3223
3224
3225
3226 obs_reconfigure.pl1
3227 addmem: MEM Y is not configured.
3228
3229
3230 Stream: Initializer process output.
3231
3232 Time: In response to an operator command.
3233
3234 Meaning: There is no MEM card in the configuration for MEM
3235 y. The SCU cannot be added.
3236
3237 Action: If the SCU name was mistyped enter a corrected
3238 command. If the configuration deck omitted the
3239 MEM card the SCU cannot be added until the system
3240 is shut down and the deck corrected.
3241
3242
3243
3244
3245
3246
3247
3248
3249 addmem -56- MR12.5 10/27/92^L
3250
3251
3252 obs_reconfigure.pl1
3253 addmem: MEM Y is not enabled on CPU X.
3254
3255
3256 Stream: Initializer process output.
3257
3258 Time: In response to an operator command.
3259
3260 Meaning: The ENABLE switch on the CONFIGURATION panel of
3261 CPU X does not enable SCU Y. The memory cannot be
3262 added.
3263
3264 Action: Fix the switches and try addmem again.
3265
3266
3267
3268 obs_reconfigure.pl1
3269 addmem: MEM Y is not in PROGRAM mode.
3270
3271
3272 Stream: Initializer process output.
3273
3274 Time: In response to an operator command.
3275
3276 Meaning: The MODE switch on 4MW SCU Y is not in PROGRAM
3277 mode. The SCU cannot be added.
3278
3279 Action: Fix the switches and try addmem again.
3280
3281 Action: No operator action is required.
3282
3283
3284
3285 obs_reconfigure.pl1
3286 addmem: Reconfiguration database is locked.
3287
3288
3289 Stream: Initializer process output.
3290
3291 Time: In response to an operator command.
3292
3293 Meaning: Another process is performing reconfiguration
3294 currently or a fault during reconfiguration has
3295 left the reconfiguration tables locked.
3296
3297 Action: If it is certain that no other process is
3298 reconfiguring and that the fault which
3299 interrupted reconfiguration has been cured the
3300 reconfigure$force_unlock command may be used to
3301 clear the lock at the direction of system staff.
3302
3303
3304
3305
3306
3307 addmem -57- MR12.5 10/27/92^L
3308
3309
3310 obs_reconfigure.pl1
3311 addmem: Size of MEM Y disagrees with CPU
3312 switches.
3313
3314
3315 Stream: Initializer process output.
3316
3317 Time: In response to an operator command.
3318
3319 Meaning: The memory size on the configuration card for MEM
3320 Y disagrees with the size on the CPU switches.
3321
3322 Action: If the switches are incorrect fix them and try
3323 addmem again. If the configuration deck is
3324 incorrect the system must be shut down and the
3325 deck corrected before the SCU can be added.
3326
3327
3328
3329 obs_reconfigure.pl1
3330 addmem: Switches for MEM Y set improperly on CPU
3331 X.
3332
3333
3334 Stream: Initializer process output.
3335
3336 Time: In response to an operator command.
3337
3338 Meaning: The ADDRESS ASSIGNMENT switches for SCU Y are
3339 incorrect on CPU X.
3340
3341 Action: Correct the switches and try addmem again.
3342
3343
3344
3345 obs_reconfigure.pl1
3346 addmem: Wrong number of arguments supplied.
3347
3348
3349 Stream: Initializer process output.
3350
3351 Time: In response to an operator command.
3352
3353 Meaning: Invalid input was typed.
3354
3355 Action: Enter a corrected command line.
3356
3357
3358
3359
3360
3361
3362
3363
3364
3365 addmem -58- MR12.5 10/27/92^L
3366
3367
3368 admin_.pl1
3369 admin_: abs ABS_FUNCTION: Expected argument
3370 missing. After PREV_ARG.
3371
3372
3373 Stream: $as1
3374
3375 Time: In response to an operator abs command.
3376
3377 Meaning: A required value to a control argument supplied in
3378 the "abs" command line is missing.
3379
3380 Action: Reenter corrected command line.
3381
3382
3383
3384 admin_.pl1
3385 admin_: abs: ABS_FUNCT: error: absentee not up
3386
3387
3388 Stream: $as1
3389
3390 Time: In response to an operator command.
3391
3392 Meaning: An abs command was given but the absentee
3393 facility had never been started up. No action was
3394 taken on the command.
3395
3396 Action: Type abs start to start up the absentee facility.
3397
3398
3399
3400 admin_.pl1
3401 admin_: abs: ABS_FUNCT: error: Invalid abs job
3402 selection argument: SSSS
3403
3404
3405 Stream: $as1
3406
3407 Time: In response to an operator command.
3408
3409 Meaning: The job selection argument SSSS is not recognized
3410 as valid.
3411
3412 Action: Type "help abs" for details of the abs command
3413 usage and try again.
3414
3415
3416
3417
3418
3419
3420
3421
3422
3423 admin_ -59- MR12.5 10/27/92^L
3424
3425
3426 admin_.pl1
3427 admin_: abs: ABS_FUNCT: error: Job in absentee
3428 slot X does not match absin entry name SSSS
3429
3430
3431 Stream: $as1
3432
3433 Time: In response to an operator command.
3434
3435 Meaning: The entry name SSSS of the absin of the job
3436 running in specified absentee slot of absX does
3437 not match the specified absin entry name.
3438
3439 Action: Recheck job specifications and try again.
3440
3441
3442
3443 admin_.pl1
3444 admin_: abs: ABS_FUNCT: error: Job in absentee
3445 slot X does not match absin path
3446 DIR_PATH>ENTRY_NAME
3447
3448
3449 Stream: $as1
3450
3451 Time: In response to an operator command.
3452
3453 Meaning: The pathname of the absin of the job running in
3454 specified absentee slot of absX does not match the
3455 specified absin pathname.
3456
3457 Action: Recheck job specifications and try again.
3458
3459
3460
3461 admin_.pl1
3462 admin_: abs: ABS_FUNCT: error: Job in absentee
3463 slot X does not match request ID YYYY
3464
3465
3466 Stream: $as1
3467
3468 Time: In response to an operator command.
3469
3470 Meaning: The ID of the job running in specified absentee
3471 slot of absX does not match the specified ID of
3472 YYYY.
3473
3474 Action: Recheck job specifications and try again.
3475
3476
3477
3478
3479
3480
3481 admin_ -60- MR12.5 10/27/92^L
3482
3483
3484 admin_.pl1
3485 admin_: abs: ABS_FUNCT: error: Job in absentee
3486 slot X is not from queue DDDD
3487
3488
3489 Stream: $as1
3490
3491 Time: In response to an operator command.
3492
3493 Meaning: The queue of the absin of the job running in
3494 specified absentee slot of absX does not match the
3495 queue number DDDD.
3496
3497 Action: Recheck job specifications and try again.
3498
3499
3500
3501 admin_.pl1
3502 admin_: abs: ABS_FUNCT: error: Job in absentee
3503 slot X is not from sender SSSS
3504
3505
3506 Stream: $as1
3507
3508 Time: In response to an operator command.
3509
3510 Meaning: The sender of the absin of the job running in
3511 specified absentee slot of absX does not match the
3512 specified sender SSSS.
3513
3514 Action: Recheck job specifications and try again.
3515
3516
3517
3518 admin_.pl1
3519 admin_: abs: ABS_FUNCT: error: Job in absentee
3520 slot X is not from user NAME.PROJ
3521
3522
3523 Stream: $as1
3524
3525 Time: In response to an operator command.
3526
3527 Meaning: The job running in specified absentee slot of absX
3528 is not from specified user NAME.PROJ.
3529
3530 Action: Recheck job specifications and try again.
3531
3532
3533
3534
3535
3536
3537
3538
3539 admin_ -61- MR12.5 10/27/92^L
3540
3541
3542 admin_.pl1
3543 admin_: abs: ABS_FUNCT: error: More than one
3544 specification of an attribute is present: SSSS
3545
3546
3547 Stream: $as1
3548
3549 Time: In response to an operator command.
3550
3551 Meaning: The SSSS attribute has already been specified to
3552 select an absentee job on the operator abs
3553 command. An attribute can only be used once.
3554
3555 Action: Enter a corrected command line.
3556
3557
3558
3559 admin_.pl1
3560 admin_: abs: ABS_FUNCT: error: No job in
3561 absentee slot X status= SSSS.
3562
3563
3564 Stream: $as1
3565
3566 Time: In response to an operator command.
3567
3568 Meaning: The absentee slot absX has an entry status of SSSS
3569 indicating that no user is using it.
3570
3571 Action: Enter a corrected command line.
3572
3573
3574
3575 admin_.pl1
3576 admin_: abs: ABS_FUNCT: error: Personid NAME >
3577 22 characters.
3578
3579
3580 Stream: $as1
3581
3582 Time: In response to an operator command.
3583
3584 Meaning: The "abs ABS_FUNCT" operator command specified a
3585 user name that is longer than 22 characters.
3586
3587 Action: Enter a corrected command line.
3588
3589
3590
3591
3592
3593
3594
3595
3596
3597 admin_ -62- MR12.5 10/27/92^L
3598
3599
3600 admin_.pl1
3601 admin_: abs: ABS_FUNCT: error: Projectid SSSS
3602 is longer than 9 characters.
3603
3604
3605 Stream: $as1
3606
3607 Time: In response to an operator command.
3608
3609 Meaning: The "abs ABS_FUNCT" operator command incorrectly
3610 specified a project name that is longer than 9
3611 characters.
3612
3613 Action: Enter a corrected command line.
3614
3615
3616
3617 admin_.pl1
3618 admin_: abs: ABS_FUNCT: error: Relative
3619 pathnames not allowed: SSSS
3620
3621
3622 Stream: $as1
3623
3624 Time: In response to an operator command.
3625
3626 Meaning: The pathname of the absin was expected and it must
3627 be an absolute pathname starting with a ">"
3628 character.
3629
3630 Action: Enter a corrected command line.
3631
3632
3633
3634 admin_.pl1
3635 admin_: abs: ABS_FUNCT: error: Selection
3636 arguments matched no running absentee jobs.
3637
3638
3639 Stream: $as1
3640
3641 Time: In response to an operator command.
3642
3643 Meaning: No running job was found that matched the
3644 selection arguments supplied on the abs command
3645 line.
3646
3647 Action: Recheck job specifications and try again.
3648
3649
3650
3651
3652
3653
3654
3655 admin_ -63- MR12.5 10/27/92^L
3656
3657
3658 admin_.pl1
3659 admin_: abs: ABS_FUNCT: error: SSSS is not a
3660 valid Person.Project.
3661
3662
3663 Stream: $as1
3664
3665 Time: In response to an operator command.
3666
3667 Meaning: The "abs ABS_FUNCT" operator command did not
3668 specify a valid Person.Project in the string SSSS.
3669
3670 Action: Enter a corrected command line.
3671
3672
3673
3674 admin_.pl1
3675 admin_: abs: ABS_FUNCT: error: The absN
3676 argument is not valid.
3677
3678
3679 Stream: $as1
3680
3681 Time: In response to an operator command.
3682
3683 Meaning: The "abs ABS_FUNCT" operator command cannot allow
3684 use of the absN argument for job selection.
3685
3686 Action: Enter a corrected command line.
3687
3688
3689
3690 admin_.pl1
3691 admin_: abs: ABS_FUNCT: error: User name not
3692 ""*"" must be given.
3693
3694
3695 Stream: $as1
3696
3697 Time: In response to an operator command.
3698
3699 Meaning: The "abs ABS_FUNCT" operator command requires that
3700 a user name be supplied. Cannot use "*".
3701
3702 Action: Enter a corrected command line.
3703
3704
3705
3706
3707
3708
3709
3710
3711
3712
3713 admin_ -64- MR12.5 10/27/92^L
3714
3715
3716 admin_.pl1
3717 admin_: abs: ABS_FUNCT: error: User name must
3718 be given.
3719
3720
3721 Stream: $as1
3722
3723 Time: In response to an operator command.
3724
3725 Meaning: The "abs ABS_FUNCT" operator command requires that
3726 a user name be supplied.
3727
3728 Action: Enter a corrected command line.
3729
3730
3731
3732 admin_.pl1
3733 admin_: abs: ABS_FUNCT: Invalid queue number
3734 DDDD
3735
3736
3737 Stream: $as1
3738
3739 Time: In response to an operator command.
3740
3741 Meaning: The value after the -queue job selection argument
3742 is invalid. It must be the strings "fg" or
3743 "foreground" or a between the values of 1 and 4
3744 inclusive.
3745
3746 Action: Enter a corrected command line.
3747
3748
3749
3750 admin_.pl1
3751 admin_: abs: ABS_FUNCT: No job selection
3752 arguments given.
3753
3754
3755 Stream: $as1
3756
3757 Time: In response to an operator command.
3758
3759 Meaning: After processing the arguments on the "abs
3760 abs_funct" operator command no job selection
3761 arguments were encountered.
3762
3763 Action: Type "help abs" for details of the abs command
3764 usage and try again.
3765
3766
3767
3768
3769
3770
3771 admin_ -65- MR12.5 10/27/92^L
3772
3773
3774 admin_.pl1
3775 admin_: abs: absentee not up and will not be
3776 started automatically
3777
3778
3779 Stream: $as1
3780
3781 Time: When operator entered "abs stop" before absentee
3782 facility was started.
3783
3784 Meaning: The command can be entered at standard to prevent
3785 the absentee facility from starting up
3786 automatically after a "startup" command is used.
3787
3788 Action: No operator action is required.
3789
3790
3791
3792 admin_.pl1
3793 admin_: abs: All absentee processes have run to
3794 completion.
3795
3796
3797 Stream: $as1
3798
3799 Time: When shutting down the absentee facility.
3800
3801 Meaning: This message is printed after the operator has
3802 issued an abs stop command or the system has
3803 issued an automatic abs stop prior to shutdown.
3804 The system allows 30 minutes for all absentee jobs
3805 to finish before logging them out then prints the
3806 message.
3807
3808 Action: It is now safe to proceed with the shutdown.
3809
3810
3811
3812
3813
3814
3815
3816
3817
3818
3819
3820
3821
3822
3823
3824
3825
3826
3827
3828
3829 admin_ -66- MR12.5 10/27/92^L
3830
3831
3832 admin_.pl1
3833 admin_: abs: auto abs stop will be at MM/DD/YY
3834 HHMM.T
3835
3836
3837 Stream: $as1
3838
3839 Time: In response to an operator down command or at
3840 startup.
3841
3842 Meaning: This is the response to a down command if the
3843 absentee facility is running or to an abs start
3844 command if the absentee is brought up after a down
3845 time has been set. The time for an automatic abs
3846 stop is 20 minutes before the system is to shut
3847 down. An "abs stop now" is done 10 minutes after
3848 the scheduled shutdown. Refer also to the stop
3849 command description.
3850
3851 Action: No operator action is required.
3852
3853
3854
3855 admin_.pl1
3856 admin_: abs: Bumping all remaining absentee
3857 processes.
3858
3859
3860 Stream: $as1
3861
3862 Time: System shutdown.
3863
3864 Meaning: The absentee facility waits 30 minutes for all
3865 absentee jobs to run to completion after the abs
3866 stop command has been issued. Then it types this
3867 message and bumps them all. Refer also to the
3868 stop command description.
3869
3870 Action: No operator action is required.
3871
3872
3873
3874
3875
3876
3877
3878
3879
3880
3881
3882
3883
3884
3885
3886
3887 admin_ -67- MR12.5 10/27/92^L
3888
3889
3890 admin_.pl1
3891 admin_: abs: cpu_limit MMMM queues 1-4: WW
3892 XX YY ZZ seconds
3893
3894
3895 Stream: $as1
3896
3897 Time: In response to "abs cpu_limit" command without
3898 arguments.
3899
3900 Meaning: Informative message indicating current values of
3901 cpu_limit for each absentee queue. MMM is the
3902 mode "auto" or "manual".
3903
3904 Action: No operator action is required.
3905
3906
3907
3908 admin_.pl1
3909 admin_: abs: cpu_limit: error: Usage is: "abs
3910 cpu_limit l1l2l3l4" limits in seconds
3911
3912
3913 Stream: $as1
3914
3915 Time: In response to an operator command.
3916
3917 Meaning: Informative message that is displayed when an
3918 operator "abs cpu_limit" command without arguments
3919 is entered.
3920
3921 Action: Enter a corrected command line.
3922
3923
3924
3925 admin_.pl1
3926 admin_: abs: error: The abs CCCC command can
3927 not be used before answering service startup.
3928
3929
3930 Stream: $as1
3931
3932 Time: In response to an operator abs command.
3933
3934 Meaning: Only the "abs stop" command may be given before
3935 the answering service starts up. This allows the
3936 operator to stop the absentee facility before the
3937 system finishes initialzation.
3938
3939 Action: Enter a corrected command line.
3940
3941
3942
3943
3944
3945 admin_ -68- MR12.5 10/27/92^L
3946
3947
3948 admin_.pl1
3949 admin_: abs: error: unknown absentee command
3950 WXYZ
3951
3952
3953 Stream: $as1
3954
3955 Time: In response to an operator command.
3956
3957 Meaning: The operator typed abs WXYZ where WXYZ was
3958 unrecognizable to the system. No action was
3959 taken.
3960
3961 Action: Enter a corrected command line.
3962
3963
3964
3965 admin_.pl1
3966 admin_: abs: ERROR_TABLE_MESSAGE PATHNAME
3967
3968
3969 Stream: $as1
3970
3971 Time: In response to the operator abs command.
3972
3973 Meaning: The ERROR_TABLE_MESSAGE was encountered when
3974 trying to expand the PATHNAME supplied in the
3975 operator abs command line.
3976
3977 Action: Enter a corrected command line.
3978
3979
3980
3981 admin_.pl1
3982 admin_: abs: list: error: No job in absentee
3983 slot X.
3984
3985
3986 Stream: $as1
3987
3988 Time: In response to an operator command.
3989
3990 Meaning: The absentee slot absX does not exist.
3991
3992 Action: Enter a corrected command line.
3993
3994
3995
3996
3997
3998
3999
4000
4001
4002
4003 admin_ -69- MR12.5 10/27/92^L
4004
4005
4006 admin_.pl1
4007 admin_: abs: list: error: The absN argument
4008 cannot be used when absentee is not up.
4009
4010
4011 Stream: $as1
4012
4013 Time: $reponse
4014
4015 Meaning: Cannot use the "absN" argument to select absentee
4016 jobs to list until the absentee facility has been
4017 started.
4018
4019 Action: Use other job selection criteria or type "abs
4020 start" and try again.
4021
4022
4023
4024 admin_.pl1
4025 admin_: abs: maxq MMMM: Q
4026
4027
4028 Stream: $as1
4029
4030 Time: In response to "abs maxq" without arguments.
4031
4032 Meaning: Informative message indicating current status of
4033 maxq and queue last searched Q. MMMM is the
4034 mode "auto" or "manual".
4035
4036 Action: No operator action is required.
4037
4038
4039
4040 admin_.pl1
4041 admin_: abs: maxq: error: abs maxqueue has
4042 invalid value: XXX
4043
4044
4045 Stream: $as1
4046
4047 Time: In response to an operator command.
4048
4049 Meaning: An abs maxq or abs start command had as an
4050 argument something that was not a number or was
4051 too big or was a negative number. No action is
4052 taken.
4053
4054 Action: Enter a corrected command line.
4055
4056
4057
4058
4059
4060
4061 admin_ -70- MR12.5 10/27/92^L
4062
4063
4064 admin_.pl1
4065 admin_: abs: maxu MMMM: UUUU
4066
4067
4068 Stream: $as1
4069
4070 Time: In response to "abs maxu" operator command without
4071 arguments.
4072
4073 Meaning: Informative message indicating current status of
4074 maxu and maximum absentee users allowed. MMMM is
4075 the mode "auto" or "manual". UUUU is the
4076 load_units.
4077
4078 Action: No operator action is required.
4079
4080
4081
4082 admin_.pl1
4083 admin_: abs: maxu: error: abs maxusers may not
4084 be greater than system maxusers: SSSS
4085
4086
4087 Stream: $as1
4088
4089 Time: In response to an operator command.
4090
4091 Meaning: The argument SSSS to the operator "abs maxu"
4092 command cannot be greater than the maximum allowed
4093 users that can be on the system.
4094
4095 Action: Enter a corrected command line.
4096
4097
4098
4099 admin_.pl1
4100 admin_: abs: maxu: error: abs maxusers may not
4101 be negative: SSSS
4102
4103
4104 Stream: $as1
4105
4106 Time: In response to an operator command.
4107
4108 Meaning: The argument SSSS to the operator "abs maxu"
4109 command was not a positive numeric or the string
4110 "auto". The numeric value is in tenths of a load
4111 unit.
4112
4113 Action: Enter a corrected command line.
4114
4115
4116
4117
4118
4119 admin_ -71- MR12.5 10/27/92^L
4120
4121
4122 admin_.pl1
4123 admin_: abs: maxu: error: abs maxusers must be
4124 numeric or "auto": SSSS
4125
4126
4127 Stream: $as1
4128
4129 Time: In response to an operator command.
4130
4131 Meaning: The argument SSSS to the operator "abs maxu"
4132 command was not a positive numeric or the string
4133 "auto". The numeric value is in tenths of a load
4134 unit.
4135
4136 Action: Enter a corrected command line.
4137
4138
4139
4140 admin_.pl1
4141 admin_: abs: qres MMMM: WW XX YY ZZ
4142
4143
4144 Stream: $as1
4145
4146 Time: In response to "abs maxq" without arguments.
4147
4148 Meaning: Informative message indicating current status of
4149 absentee queue reservation for each queue. MMMM
4150 is the mode "auto" or "manual".
4151
4152 Action: No operator action is required.
4153
4154
4155
4156 admin_.pl1
4157 admin_: abs: qres: error: abs qres has invalid
4158 value: DDDD
4159
4160
4161 Stream: $as1
4162
4163 Time: In response to an operator command.
4164
4165 Meaning: An invalid qres argument was detected in an
4166 operator "abs qres" command. The argument must be
4167 "auto" or a positive decimal number.
4168
4169 Action: Enter a corrected command line.
4170
4171
4172
4173
4174
4175
4176
4177 admin_ -72- MR12.5 10/27/92^L
4178
4179
4180 admin_.pl1
4181 admin_: abs: queue limits: WW XX YY ZZ
4182
4183
4184 Stream: $as1
4185
4186 Time: In response to "abs qres" operator command.
4187
4188 Meaning: Informative message indicating the current queue
4189 reservation limits.
4190
4191 Action: No operator action is required.
4192
4193
4194
4195 admin_.pl1
4196 admin_: abs: Queue errors *=dropped:
4197 admin_: abs: FG 0 1 2 3 4
4198 admin_: abs: TT VV WW XX YY ZZ
4199 admin_: abs: * * * * * *
4200
4201
4202 Stream: $as1
4203
4204 Time: In response to "abs queue" operator command.
4205
4206 Meaning: Displays the errors for each queue and indicates
4207 which one has been dropped. If none have been
4208 dropped the last line will not be displayed nor
4209 will the string "*=dropped" appear in the first
4210 line.
4211
4212 Action: Contact the system programming staff.
4213
4214
4215
4216 admin_.pl1
4217 admin_: abs: release: error: Job in absentee
4218 slot X is not suspended.
4219
4220
4221 Stream: $as1
4222
4223 Time: In response to an operator command.
4224
4225 Meaning: The specified job running in absentee slot of absX
4226 is not suspended so a release does not apply.
4227
4228 Action: Recheck job specifications and try again.
4229
4230
4231
4232
4233
4234
4235 admin_ -73- MR12.5 10/27/92^L
4236
4237
4238 admin_.pl1
4239 admin_: abs: release: error: Selection
4240 arguments matched no deferred or suspended
4241 absentee requests.
4242
4243
4244 Stream: $as1
4245
4246 Time: In response to an operator command.
4247
4248 Meaning: No suspended or deferred job was found to release
4249 with the arguments supplied on the abs release
4250 command line.
4251
4252 Action: Recheck job specifications and try again.
4253
4254
4255
4256 admin_.pl1
4257 admin_: abs: resetting auto abs stop
4258
4259
4260 Stream: $as1
4261
4262 Time: In response to an operator abs stop command.
4263
4264 Meaning: An abs stop command overrides an automatic abs
4265 stop that was set up by a down command.
4266
4267 Action: No operator action is required.
4268
4269
4270
4271 admin_.pl1
4272 admin_: abs: start: error: absentee already up
4273
4274
4275 Stream: $as1
4276
4277 Time: In response to an operator abs start command.
4278
4279 Meaning: abs start was typed twice. No action was taken on
4280 the second issuance of the command.
4281
4282 Action: No operator action is required.
4283
4284
4285
4286
4287
4288
4289
4290
4291
4292
4293 admin_ -74- MR12.5 10/27/92^L
4294
4295
4296 admin_.pl1
4297 admin_: abs: start: error: absentee not up.
4298 cannot restart queue X
4299
4300
4301 Stream: $as1
4302
4303 Time: In response to an operator command.
4304
4305 Meaning: Cannot use the "abs start queue" command until the
4306 absentee facility has been started.
4307
4308 Action: Issue the "abs start" command and try again.
4309
4310
4311
4312 admin_.pl1
4313 admin_: abs: start: error: invalid queue to be
4314 restarted X
4315
4316
4317 Stream: $as1
4318
4319 Time: In response to an operator command.
4320
4321 Meaning: An invalid queue number was specified in an
4322 operator "abs start queue" command line. It must
4323 be between 1 and 4 inclusive.
4324
4325 Action: Enter a corrected command line.
4326
4327
4328
4329 admin_.pl1
4330 admin_: abs: start: error: system coming down
4331 soon: no abs start
4332
4333
4334 Stream: $as1
4335
4336 Time: In response to an operator command.
4337
4338 Meaning: The system is shutting down within 30 minutes so
4339 the absentee facility will not be started.
4340
4341 Action: No operator action is required.
4342
4343
4344
4345
4346
4347
4348
4349
4350
4351 admin_ -75- MR12.5 10/27/92^L
4352
4353
4354 admin_.pl1
4355 admin_: abs: stop: error: abs stop queue only
4356 works after answering service startup
4357
4358
4359 Stream: $as1
4360
4361 Time: In response to an operator abs stop queue command.
4362
4363 Meaning: The answering service must complete initialization
4364 before the "abs stop queue" command can be used.
4365
4366 Action: Allow the system to complete initialization and
4367 try again.
4368
4369
4370
4371 admin_.pl1
4372 admin_: abs: stop: error: absentee stop in
4373 progress
4374
4375
4376 Stream: $as1
4377
4378 Time: In response to an operator command.
4379
4380 Meaning: An abs start abs stop abs maxu abs maxq or
4381 down command was issued while the absentee
4382 facility was in the process of shutting down.
4383
4384 Action: Wait for the message that all absentee processes
4385 have run to completion then reissue the command.
4386
4387
4388
4389 admin_.pl1
4390 admin_: abs: stop: error: invalid queue to be
4391 stopped: DDDD
4392
4393
4394 Stream: $as1
4395
4396 Time: In response to an operator "abs stop queue"
4397 command.
4398
4399 Meaning: The value of the queue number was not within the
4400 values of 1 and 4 inclusive.
4401
4402 Action: Enter a corrected command line.
4403
4404
4405
4406
4407
4408
4409 admin_ -76- MR12.5 10/27/92^L
4410
4411
4412 admin_.pl1
4413 admin_: abs: stop: error: missing argument:
4414 queue to be stopped
4415
4416
4417 Stream: $as1
4418
4419 Time: In response to an operator "abs stop queue"
4420 command.
4421
4422 Meaning: The "abs stop queue" command was entered without
4423 supplying the number of the queue to be stopped.
4424
4425 Action: Enter a corrected command line.
4426
4427
4428
4429 admin_.pl1
4430 admin_: abs: stop: error: unknown argument
4431 SSSS
4432
4433
4434 Stream: $as1
4435
4436 Time: In response to an operator "abs stop" command.
4437
4438 Meaning: An unknown argument SSSS was supplied to the
4439 "abs stop" command.
4440
4441 Action: Type "help abs" for details of the abs command and
4442 try again.
4443
4444
4445
4446 admin_.pl1
4447 admin_: abs: suspend: error: Job in absentee
4448 slot X is already suspended.
4449
4450
4451 Stream: $as1
4452
4453 Time: In response to an operator command.
4454
4455 Meaning: The specified job running in absentee slot of absX
4456 is already suspended and cannot be suspended
4457 again.
4458
4459 Action: Recheck job specifications and try again.
4460
4461
4462
4463
4464
4465
4466
4467 admin_ -77- MR12.5 10/27/92^L
4468
4469
4470 admin_.pl1
4471 admin_: abs: Warning: cpu limits are in
4472 seconds. You just set queue QQ limit to LLLL
4473 seconds.
4474
4475
4476 Stream: $as1
4477
4478 Time: In response to "abs cpu_limit" command with
4479 arguments.
4480
4481 Meaning: The cpu_limit LLLL for queue QQ is below 60
4482 seconds which is likely to be a mistake. The
4483 value already given will be still be accepted.
4484
4485 Action: Reenter the command with corrected values if
4486 originally incorrect.
4487
4488
4489
4490 admin_.pl1
4491 admin_: abs: Zero errors on all absentee queues.
4492
4493
4494 Stream: $as1
4495
4496 Time: In response to "abs queue" operator command.
4497
4498 Meaning: Informative message which indicates that no queue
4499 has been dropped and no errors recorded for any
4500 queue.
4501
4502 Action: No operator action is required.
4503
4504
4505
4506 admin_.pl1
4507 admin_: bump: USER.PROJECT bumped.
4508
4509
4510 Stream: $as1
4511
4512 Time: In response to the bump command or a system
4513 shutdown.
4514
4515 Meaning: The specified user has been notified that he or
4516 she must get off the system. If a grace time was
4517 specified the user is allowed that amount of time
4518 to logout. Otherwise the user is removed from
4519 the system immediately.
4520
4521 Action: No operator action is required.
4522
4523
4524
4525 admin_ -78- MR12.5 10/27/92^L
4526
4527
4528 admin_.pl1
4529 admin_: COMMAND: error: Invalid FNP tag: X
4530
4531
4532 Stream: $as1
4533
4534 Time: Response to an operator "load_fnp" "fdump_fnp"
4535 "dump_fnp" "start_fnp" or "stop_fnp" command.
4536
4537 Meaning: The supplied FNP tag was more than one character
4538 or was not between a-h inclusive.
4539
4540 Action: Enter a corrected command line.
4541
4542
4543
4544 admin_.pl1
4545 admin_: COMMAND: error: No FNP tag specified.
4546
4547
4548 Stream: $as1
4549
4550 Time: Response to an operator "load_fnp" "fdump_fnp"
4551 "dump_fnp" "start_fnp" or "stop_fnp" command.
4552
4553 Meaning: The operator did not supply an FNP identifier.
4554
4555 Action: Enter a corrected command line.
4556
4557
4558
4559 admin_.pl1
4560 admin_: COMMAND: error: No multiplexer
4561 specified.
4562
4563
4564 Stream: $as1
4565
4566 Time: Response to an operator "load_mpx" "dump_mpx"
4567 "start_mpx" "shutdown_mpx" or "stop_mpx" command.
4568
4569 Meaning: The operator did not supply a multiplexer name.
4570
4571 Action: Enter a corrected command line.
4572
4573
4574
4575
4576
4577
4578
4579
4580
4581
4582
4583 admin_ -79- MR12.5 10/27/92^L
4584
4585
4586 admin_.pl1
4587 admin_: COMMAND: ERROR_TABLE_MESSAGE
4588
4589
4590 Stream: $as1
4591
4592 Time: In response to operator command COMMAND.
4593
4594 Meaning: The ERROR_TABLE_MESSAGE error was encounted when
4595 processing the operator command COMMAND.
4596
4597 Action: Type "help COMMAND" for details of the command's
4598 usage.
4599
4600
4601
4602 admin_.pl1
4603 admin_: COMMAND: PERSON.PROJECT has "nobump"
4604
4605
4606 Stream: $as1
4607
4608 Time: System shutdown.
4609
4610 Meaning: The PERSON.PROJECT user cannot be bumped by the
4611 automatic shutdown or in response to the stop
4612 command. The nobump attribute is normally only
4613 used by system administrator users.
4614
4615 Action: Try to contact the user to arrange a time to
4616 actually shutdown. If necessary the user can be
4617 bumped by specifying the channel name in the bump
4618 command. This will only work if the process has
4619 not been disconnected. Otherwise you will have
4620 to answer "yes" to the shutdown command.
4621
4622
4623
4624
4625
4626
4627
4628
4629
4630
4631
4632
4633
4634
4635
4636
4637
4638
4639
4640
4641 admin_ -80- MR12.5 10/27/92^L
4642
4643
4644 admin_.pl1
4645 admin_: down: auto shutdown will be at MM/DD/YY
4646 HHMM.T
4647
4648
4649 Stream: $as1
4650
4651 Time: In response to an operator down command or at
4652 startup.
4653
4654 Meaning: This is the response to the down command. It
4655 indicates the scheduled shutdown time. A down
4656 command is issued automatically at system startup
4657 time after a crash; if a down command was given
4658 before the crash occurred and the time of the
4659 scheduled shutdown is more than 30 minutes in the
4660 future.
4661
4662 Action: If the value shown in the message is correct
4663 proceed. If not correct reset the shutdown by
4664 typing down 0 and then try again.
4665
4666
4667
4668 admin_.pl1
4669 admin_: down: error: no system shutdown
4670 scheduled
4671
4672
4673 Stream: $as1
4674
4675 Time: In response to operator entering "down 0".
4676
4677 Meaning: The "down 0" command line cancels a down but no
4678 system shutdown was scheduled. No action was
4679 taken.
4680
4681 Action: No operator action is required.
4682
4683
4684
4685
4686
4687
4688
4689
4690
4691
4692
4693
4694
4695
4696
4697
4698
4699 admin_ -81- MR12.5 10/27/92^L
4700
4701
4702 admin_.pl1
4703 admin_: down: error: uptime is earlier than
4704 downtime.
4705
4706
4707 Stream: $as1
4708
4709 Time: In response to an operator down command.
4710
4711 Meaning: The operator down command specifies that the
4712 expected time that the system will be up is before
4713 the time that it is scheduled to be shutdown. No
4714 action was taken.
4715
4716 Action: Enter a corrected command line.
4717
4718
4719
4720 admin_.pl1
4721 admin_: down: error: XXX invalid clock time.
4722
4723
4724 Stream: $as1
4725
4726 Time: In response to an operator down command.
4727
4728 Meaning: The time arguments of a down command must be
4729 specified in 4-digit time or some form acceptable
4730 to convert_date_to_binary_. No action was taken.
4731 If the second time argument is an invalid time it
4732 is considered part of the message. This message
4733 is also displayed if the first time argument is
4734 not in the future.
4735
4736 Action: Enter a corrected command line.
4737
4738
4739
4740 admin_.pl1
4741 admin_: down: Next shutdown from DATE_TIME to
4742 DATE_TIME1 REASON
4743
4744
4745 Stream: $as1
4746
4747 Time: Response to an operator "down" command.
4748
4749 Meaning: This message tells when the next scheduled
4750 shutdown is.
4751
4752 Action: No operator action is required.
4753
4754
4755
4756
4757 admin_ -82- MR12.5 10/27/92^L
4758
4759
4760 admin_.pl1
4761 admin_: down: No shutdown is scheduled.
4762
4763
4764 Stream: $as1
4765
4766 Time: In response to an operator down command.
4767
4768 Meaning: The operator issued a down 0 command to reset a
4769 scheduled automatic shutdown when none was in
4770 effect. No action was taken on the command.
4771
4772 Action: No operator action is required.
4773
4774
4775
4776 admin_.pl1
4777 admin_: down: resetting previous shutdown at
4778 MM/DD/YY HHMM.T
4779
4780
4781 Stream: $as1
4782
4783 Time: In response to an operator down command.
4784
4785 Meaning: A second down command has been issued before a
4786 previously issued down command has been executed.
4787 The new shutdown time is honored instead of the
4788 previous one.
4789
4790 Action: No operator action is required.
4791
4792
4793
4794 admin_.pl1
4795 admin_: dump_fnp: error: unknown argument AAAA
4796
4797
4798 Stream: $as1
4799
4800 Time: In response to an operator dump_fnp command.
4801
4802 Meaning: An unknown argument AAAA was encountered in the
4803 dump_fnp command line. This is an obsolete
4804 command. No action was taken.
4805
4806 Action: Type "help dump_mpx" for details of the dump_mpx
4807 command and try again.
4808
4809
4810
4811
4812
4813
4814
4815 admin_ -83- MR12.5 10/27/92^L
4816
4817
4818 admin_.pl1
4819 admin_: dump_mpx: error: unknown argument AAAA
4820
4821
4822 Stream: $as1
4823
4824 Time: In response to an operator dump_mpx command.
4825
4826 Meaning: An unknown argument AAAA was encountered in the
4827 dump_mpx command line. No action was taken.
4828
4829 Action: Type "help dump_mpx" for details of the dump_mpx
4830 command and try again.
4831
4832
4833
4834 admin_.pl1
4835 admin_: ERROR_MESSAGE SYSDIR>absentee_user_table
4836
4837
4838 Stream: $as1
4839
4840 Time: When operator entered abs command.
4841
4842 Meaning: The ERROR_MESSAGE gives reason why system was not
4843 able to find or access the absentee_user_table in
4844 the SYSDIR directory. Execution of the command
4845 was not completed.
4846
4847 Action: %inform
4848
4849
4850
4851 admin_.pl1
4852 admin_: ERROR_MESSAGE SYSDIR>answer_table
4853
4854
4855 Stream: $as2
4856
4857 Time: In response to operator commands that require
4858 access to the system answer_table.
4859
4860 Meaning: The ERROR_MESSAGE gives reason why system was not
4861 able to find or access the answer_table in the
4862 SYSDIR directory. Execution of the command was
4863 not completed.
4864
4865 Action: Contact the system programming staff.
4866
4867
4868
4869
4870
4871
4872
4873 admin_ -84- MR12.5 10/27/92^L
4874
4875
4876 admin_.pl1
4877 admin_: ERROR_MESSAGE SYSDIR>cdt
4878
4879
4880 Stream: $as2
4881
4882 Time: In response to operator commands that require
4883 access to the system cdt.
4884
4885 Meaning: The ERROR_MESSAGE gives reason why system was not
4886 able to find or access the cdt in the SYSDIR
4887 directory. Execution of the command was not
4888 completed.
4889
4890 Action: Contact the system programming staff.
4891
4892
4893
4894 admin_.pl1
4895 admin_: ERROR_MESSAGE SYSDIR>installation_parms
4896
4897
4898 Stream: $as2
4899
4900 Time: In response to operator commands that require
4901 access to the system installation_parms.
4902
4903 Meaning: The ERROR_MESSAGE gives reason why system was not
4904 able to find or access the installation_parms in
4905 the SYSDIR directory. Execution of the command
4906 was not completed.
4907
4908 Action: Contact the system programming staff.
4909
4910
4911
4912 admin_.pl1
4913 admin_: ERROR_MESSAGE SYSDIR>whotab
4914
4915
4916 Stream: $as2
4917
4918 Time: In response to operator commands that require
4919 access to the system whotab.
4920
4921 Meaning: The ERROR_MESSAGE gives reason why system was not
4922 able to find or access the whotab in the SYSDIR
4923 directory. Execution of the command was not
4924 completed.
4925
4926 Action: Contact the system programming staff.
4927
4928
4929
4930
4931 admin_ -85- MR12.5 10/27/92^L
4932
4933
4934 admin_.pl1
4935 admin_: fdump_fnp: error: unknown argument AAAA
4936
4937
4938 Stream: $as1
4939
4940 Time: In response to an operator fdump_fnp command.
4941
4942 Meaning: An unknown argument AAAA was encountered in the
4943 fdump_fnp command. This is an obsolete command.
4944 No action was taken.
4945
4946 Action: Type "help dump_mpx" for details of the dump_mpx
4947 command and try again.
4948
4949
4950
4951 admin_.pl1
4952 admin_: load_fnp: unknown argument AAAA
4953
4954
4955 Stream: $as1
4956
4957 Time: In response to an operator load_fnp command.
4958
4959 Meaning: An unknown argument AAAA was encountered in the
4960 load_fnp command line. This is an obsolete
4961 command. No action was taken.
4962
4963 Action: Type "help load_mpx" for details of the load_mpx
4964 command and try again.
4965
4966
4967
4968 admin_.pl1
4969 admin_: load_mpx: error: unknown argument AAAA
4970
4971
4972 Stream: $as1
4973
4974 Time: In response to an operator load_mpx command.
4975
4976 Meaning: An unknown argument AAAA was encountered in the
4977 load_mpx command line. No action was taken.
4978
4979 Action: Type "help load_mpx" for details of the load_mpx
4980 command and try again.
4981
4982
4983
4984
4985
4986
4987
4988
4989 admin_ -86- MR12.5 10/27/92^L
4990
4991
4992 admin_.pl1
4993 admin_: load_mpx: error: unknown argument AAAA
4994
4995
4996 Stream: $as1
4997
4998 Time: In response to an operator load_mpx command.
4999
5000 Meaning: An unknown argument AAAA was encountered in the
5001 load_mpx command line. No action was taken.
5002
5003 Action: Type "help load_mpx" for use of the load_mpx
5004 command and try again.
5005
5006
5007
5008 admin_.pl1
5009 admin_: log: MESSAGE
5010
5011
5012 Stream: $as0
5013
5014 Time: While system is running.
5015
5016 Meaning: The log command simply enters its arguments in the
5017 system log. It is occasionally used by operators
5018 and system programmers to record events.
5019
5020 Action: No operator action is required.
5021
5022
5023
5024 admin_.pl1
5025 admin_: login: Entry not found. No MC ACS
5026 segment for the source SSSS.
5027
5028
5029 Stream: $as1
5030
5031 Time: In response to operator login command.
5032
5033 Meaning: An MC ACS was not found in >sc1>mc_acs directory
5034 for the source identifier SSSS.
5035
5036 Action: Contact the system programming staff.
5037
5038
5039
5040
5041
5042
5043
5044
5045
5046
5047 admin_ -87- MR12.5 10/27/92^L
5048
5049
5050 admin_.pl1
5051 admin_: login: error: Usage: login
5052 Person.Project SOURCE -control_args
5053
5054
5055 Stream: $as1
5056
5057 Time: In response to operator login command with no
5058 arguments.
5059
5060 Meaning: Informative message to operator when the login
5061 command was entered without arguments.
5062
5063 Action: Also type "help login" for further details of
5064 command line syntax.
5065
5066
5067
5068 admin_.pl1
5069 admin_: login: ERROR_TABLE_MESSAGE Login not
5070 permitted for message coordinator source SSSS.
5071
5072
5073 Stream: $as1
5074
5075 Time: In response to operator login command.
5076
5077 Meaning: The error identified by ERROR_TABLE_MESSAGE was
5078 encountered attempting to check the access to
5079 login the daemon whose source identifier is SSSS.
5080
5081
5082
5083 admin_.pl1
5084 admin_: logout: error: Usage: logout
5085 Person.Project SOURCE
5086
5087
5088 Stream: $as1
5089
5090 Time: In response to operator logout command when
5091 entered without arguments.
5092
5093 Meaning: Informative message indicating usage of the logout
5094 command.
5095
5096 Action: Type "help logout" for further details of command
5097 usage.
5098
5099
5100
5101
5102
5103
5104
5105 admin_ -88- MR12.5 10/27/92^L
5106
5107
5108 admin_.pl1
5109 admin_: maxu: MMMM: UUUU DDDD normal users
5110
5111 Stream: $as1
5112
5113
5114 Time: When operator entered "maxu" command.
5115
5116 Meaning: This is an informative message indicating the
5117 current values manipulated by the maxu command.
5118 MMMM is the mode "auto" or "level". UUUU is the
5119 load units in tenths. DDDD is the load units in
5120 whole numbers.
5121
5122 Action: No operator action is required.
5123
5124
5125
5126 admin_.pl1
5127 admin_: maxu: Warning: maxunits are in tenths
5128 of load units.
5129 You just set maxu to UUUU or DDDD
5130 normal users.
5131
5132
5133 Stream: $as1
5134
5135 Time: When operator entered a maxu command line that
5136 specified < 200 load units or 20 normal users.
5137
5138 Meaning: This message is a warning to the operator that he
5139 may have made a mistake in setting the load units
5140 of the system. A normal system is not likely to
5141 set its maximum load units to less than 200.
5142
5143 Action: Take corrective action reenter the command with
5144 corrected arguments.
5145
5146
5147
5148
5149
5150
5151
5152
5153
5154
5155
5156
5157
5158
5159
5160
5161
5162
5163 admin_ -89- MR12.5 10/27/92^L
5164
5165
5166 admin_.pl1
5167 admin_: maxunits: error: XXX invalid value for
5168 maxunits
5169
5170
5171 Stream: $as1
5172
5173 Time: In response to an operator maxunits command.
5174
5175 Meaning: The argument of the maxunits command was not a
5176 number or was zero or negative. No action was
5177 taken.
5178
5179 Action: Enter a corrected command line.
5180
5181
5182
5183 admin_.pl1
5184 admin_: rcp: error: unknown rcp command RRRR
5185
5186
5187 Stream: $as1
5188
5189 Time: In response to an operator rcp command.
5190
5191 Meaning: The operator has entered an unknown rcp operator
5192 on the command line.
5193
5194 Action: Type "help rcp" for further details on rcp command
5195 usage.
5196
5197
5198
5199 admin_.pl1
5200 admin_: shift: error: CCCC invalid clock time.
5201
5202
5203 Stream: $as1
5204
5205 Time: In response to an operator shift command.
5206
5207 Meaning: The time argument of the shift command is not a
5208 valid clock time acceptable to
5209 convert_date_to_binary_.
5210
5211 Action: Enter a corrected command line.
5212
5213
5214
5215
5216
5217
5218
5219
5220
5221 admin_ -90- MR12.5 10/27/92^L
5222
5223
5224 admin_.pl1
5225 admin_: shift: error: CCCC is not within the
5226 next week.
5227
5228
5229 Stream: $as1
5230
5231 Time: In response to an operator shift command.
5232
5233 Meaning: The time argument of the shift command cannot
5234 specify a time stamp that is over a week in the
5235 future.
5236
5237 Action: Enter a corrected command line.
5238
5239
5240
5241 admin_.pl1
5242 admin_: shift: error: XXXX is not a legal shift
5243 number.
5244
5245
5246 Stream: $as1
5247
5248 Time: In response to an operator shift command.
5249
5250 Meaning: A shift argument to the shift command was not a
5251 valid decimal number between 1 and 6 inclusive.
5252
5253 Action: Enter a corrected command line.
5254
5255
5256
5257 admin_.pl1
5258 admin_: shift: N until DATE_TIME
5259
5260
5261 Stream: $as1
5262
5263 Time: response to an operator "shift" command.
5264
5265 Meaning: The operator has issued the shift command. If
5266 issued with no arguments this command types the
5267 current setting. If issued with arguments the
5268 command changes the shift and types the new value.
5269
5270 Action: No operator action is required.
5271
5272
5273
5274
5275
5276
5277
5278
5279 admin_ -91- MR12.5 10/27/92^L
5280
5281
5282 admin_.pl1
5283 admin_: shutdown_mpx: error: unknown argument
5284 AAAA
5285
5286
5287 Stream: $as1
5288
5289 Time: In response to an operator shutdown_mpx command.
5290
5291 Meaning: An unknown argument AAAA was encountered in the
5292 shutdown_mpx command line. No action was taken.
5293
5294 Action: The shutdown_mpx command is the same as the
5295 dump_mpx command except that no dump is created.
5296 Type "help dump_mpx" for command usage details and
5297 try again.
5298
5299
5300
5301 admin_.pl1
5302 admin_: stop: All users are out. You may shut
5303 down.
5304
5305
5306 Stream: $as1
5307
5308 Time: System shutdown.
5309
5310 Meaning: This is the response to the stop command if all
5311 users have been logged out. This message provides
5312 a quick check of whether all users have been
5313 bumped since it does not adversely affect system
5314 operation to issue the stop command repeatedly.
5315
5316 Action: Proceed with the shutdown.
5317
5318
5319
5320
5321
5322
5323
5324
5325
5326
5327
5328
5329
5330
5331
5332
5333
5334
5335
5336
5337 admin_ -92- MR12.5 10/27/92^L
5338
5339
5340 admin_.pl1
5341 admin_: stop: all users have been given XXXX
5342 minutes to logout
5343
5344
5345 Stream: $as1
5346
5347 Time: System shutdown.
5348
5349 Meaning: A stop command either manual or automatic has
5350 been initiated. All users have been warned that
5351 they have XXXX minutes to finish up and logout.
5352 After XXXX minutes all users will be bumped
5353 except those with the nobump attribute. The login
5354 word has been set so that no more users may log
5355 in. To cancel this shutdown issue a word login
5356 command and an unbump * * command.
5357
5358 Action: No operator action is required.
5359
5360
5361
5362 admin_.pl1
5363 admin_: stop: auto abs stop
5364
5365
5366 Stream: $as1
5367
5368 Time: While system is running.
5369
5370 Meaning: It is 30 minutes before an automatic stop so an
5371 automatic abs stop command is being issued. This
5372 is the result of a previous down command. Refer
5373 also to the stop command description.
5374
5375 Action: No operator action is required.
5376
5377
5378
5379 admin_.pl1
5380 admin_: stop: Automatic shutdown
5381
5382
5383 Stream: $as1
5384
5385 Time: System shutdown.
5386
5387 Meaning: A down command issued earlier has taken effect.
5388 An automatic stop command is executed. All users
5389 are bumped in three minutes.
5390
5391 Action: Prepare to shut down the system.
5392
5393
5394
5395 admin_ -93- MR12.5 10/27/92^L
5396
5397
5398 admin_.pl1
5399 admin_: stop: error: no arguments are allowed
5400 for "stop"
5401
5402
5403 Stream: $as1
5404
5405 Time: In response to an operator stop command.
5406
5407 Meaning: The operator has given an argument to the stop
5408 command. No arguments are allowed. No action was
5409 taken.
5410
5411 Action: If abs stop was meant type that command. If stop
5412 was meant type that command instead. If "down
5413 ...." was meant type in that command.
5414
5415
5416
5417 admin_.pl1
5418 admin_: stop: There were no active users to be
5419 bumped.
5420
5421
5422 Stream: $as1
5423
5424 Time: System shutdown.
5425
5426 Meaning: The system did not find any active users to be
5427 bumped.
5428
5429 Action: No operator action is required.
5430
5431
5432
5433 admin_.pl1
5434 admin_: stop_fnp: error: unknown argument AAAA
5435
5436
5437 Stream: $as1
5438
5439 Time: In response to an operator stop_mpx command.
5440
5441 Meaning: An unknown argument AAAA was encountered in the
5442 stop_fnp command line. This is an obsolete
5443 command. No action was taken.
5444
5445 Action: Type "help stop_mpx" for details of the stop_mpx
5446 command and try again.
5447
5448
5449
5450
5451
5452
5453 admin_ -94- MR12.5 10/27/92^L
5454
5455
5456 admin_.pl1
5457 admin_: stop_mpx: error: unknown argument AAAA
5458
5459
5460 Stream: $as1
5461
5462 Time: In response to an operator stop_mpx command.
5463
5464 Meaning: An unknown argument AAAA was encountered in the
5465 stop_mpx command line. No action was taken.
5466
5467 Action: Type "help stop_mpx" for details of the stop_mpx
5468 command and try again.
5469
5470
5471
5472 admin_.pl1
5473 admin_: warn: error: Usage: warn
5474 Person.Project MESSAGE
5475
5476
5477 Stream: $as1
5478
5479 Time: In response to an operator warn command without
5480 any arguments.
5481
5482 Meaning: Informative message indicating usage of the warn
5483 command.
5484
5485 Action: Also type "help warn" for more details on warn
5486 command usage.
5487
5488
5489
5490 admin_.pl1
5491 admin_: warn: NAME.PROJ has "no_warning"
5492
5493
5494 Stream: $as1
5495
5496 Time: Response to operator warn command.
5497
5498 Meaning: This is the response to the command "warn NAME
5499 PROJ Message..." if the user has specified the
5500 -no_warning argument at login. The message is not
5501 sent to the user.
5502
5503 Action: Attempt to contact the user by other means.
5504
5505
5506
5507
5508
5509
5510
5511 admin_ -95- MR12.5 10/27/92^L
5512
5513
5514 admin_.pl1
5515 admin_: warn: NAME.PROJ not found.
5516
5517
5518 Stream: $as1
5519
5520 Time: In response to an operator warn command.
5521
5522 Meaning: The warn command was issued for a nonexistent
5523 user. No action was taken.
5524
5525 Action: The user is probably not logged in. Check the
5526 spelling of the name. Enter a corrected command
5527 line.
5528
5529
5530
5531 admin_.pl1
5532 admin_: warn: USER.PROJ not connected to a
5533 channel
5534
5535
5536 Stream: as sevreity1
5537
5538 Time: Response to operator warn command.
5539
5540 Meaning: This is the response to the command "warn NAME
5541 PROJ Message" if the pointer to the channel table
5542 entry in the user table entry for the named user
5543 ute.cdtep is not set null. The message cannot
5544 be sent to the user.
5545
5546 Action: Attempt to contact the user by other means.
5547
5548
5549
5550 admin_.pl1
5551 admin_: word: length of login-word must not
5552 exceed 8 characters
5553
5554
5555 Stream: $as1
5556
5557 Time: In response to an operator word command.
5558
5559 Meaning: The operator tried to set the login word with the
5560 word command but the first argument was too long.
5561 No action was taken on the command.
5562
5563 Action: Enter a corrected command line.
5564
5565
5566
5567
5568
5569 admin_ -96- MR12.5 10/27/92^L
5570
5571
5572 admin_.pl1
5573 admin_: word: message truncated; maximum length
5574 is CCCC characters
5575
5576
5577 Stream: $as1
5578
5579 Time: In response to an operator word command.
5580
5581 Meaning: The operator issued the command "word XXXX TEXT".
5582 The message TEXT was too long to fit in the dialup
5583 message buffer. The login word has been changed
5584 and the dialup message has been set to the first
5585 CCCC characters of the given message.
5586
5587 Action: Reword the message to fit within the
5588 CCCC-character limit and retype the command.
5589
5590
5591
5592 admin_.pl1
5593 admin_: word: TYPE message: TEXT
5594
5595
5596 Stream: $as1
5597
5598 Time: In response to an operator word command.
5599
5600 Meaning: The operator issued the command "word XXXX TEXT".
5601 The login word was set to XXXX and a special
5602 buffer was loaded with the message TEXT so that it
5603 is typed out whenever a user dials up. The type
5604 of system session is TYPE; this may be special
5605 normal or shutdown.
5606
5607 Action: Check the message for accuracy.
5608
5609
5610
5611 admin_.pl1
5612 admin_: word: XXXX is a reserved word.
5613
5614
5615 Stream: $as1
5616
5617 Time: In response to an operator word command.
5618
5619 Meaning: The operator attempted to set the system login
5620 word to enter enterp e ep dial or d. No
5621 action was taken.
5622
5623 Action: Pick another word and type it in.
5624
5625
5626
5627 admin_ -97- MR12.5 10/27/92^L
5628
5629
5630 admin_.pl1
5631 admin_: word: XXXX; TYPE message: TEXT
5632
5633
5634 Stream: $as1
5635
5636 Time: In response to an operator word command.
5637
5638 Meaning: The operator issued the word command with no
5639 arguments and the current values were typed. The
5640 login word is XXXX the message is TEXT and the
5641 type of session is TYPE. The TEXT is displayed as
5642 the first line of the greeting banner to
5643 interactive users making the banner 3 lines long.
5644 If TEXT is "" NO MESSAGE then nothing is added
5645 to the normal 2 line greeting banner.
5646
5647 Action: Check the word type and message for accuracy.
5648
5649
5650
5651 salv_dir_checker_.pl1
5652 ADUIT salv_dir_checker_: GRANTED modification
5653 of security out-of-service ADDED_INFO
5654
5655
5656 Stream: $access_audit
5657
5658 Time: Salvaging
5659
5660 Meaning: The security-out-of-service switch has been set on
5661 a directory because of an AIM error. The access
5662 class of a branch was not equal to that of the
5663 containing directory or the access class in the
5664 directory's branch was not equal to the access
5665 class stored in its header.
5666
5667 Action: Contact the system security administrator.
5668
5669
5670
5671
5672
5673
5674
5675
5676
5677
5678
5679
5680
5681
5682
5683
5684
5685 ADUIT salv_dir_checker_ -98- MR12.5 10/27/92^L
5686
5687
5688 announce_chwm.pl1
5689 announce_chwm: WWW pages wired UUU pages usable.
5690
5691
5692 Stream: BOS Typewriter.
5693
5694 Time: System Intialization.
5695
5696 Meaning: This message is produced when the CHWM paramter is
5697 specified on the PARM CONFIG card. WWW is the
5698 number of wired pages in collection one. UUU is
5699 the number of available main memory frames
5700 including those occupied by wired pages but not
5701 those occupied by unpaged segments.
5702
5703 Action: No operator action is required.
5704
5705
5706
5707 announce_chwm.pl1
5708 announce_chwm: WWW. pages used of XXX. in wired
5709 environment.
5710
5711
5712 Stream: BOS Typewriter.
5713
5714 Time: System Intialization.
5715
5716 Meaning: This message is produced when the CHWM parameter
5717 is specified on the PARM CONFIG card. WWW is the
5718 number of pages of memory which remain unused out
5719 of a maximum of XXX after all the segments in
5720 collection one have been loaded and all the
5721 segments constructed by collection one have been
5722 created.
5723
5724 Action: No operator action is required.
5725
5726
5727
5728
5729
5730
5731
5732
5733
5734
5735
5736
5737
5738
5739
5740
5741
5742
5743 announce_chwm -99- MR12.5 10/27/92^L
5744
5745
5746 announce_chwm.pl1
5747 announce_chwm: WWW. words used of XXX. in
5748 int_unpaged_page_tables.
5749
5750
5751 Stream: BOS Typewriter.
5752
5753 Time: System Intialization.
5754
5755 Meaning: This message is produced when the CHWM parameter
5756 is specified on the PARM CONFIG card. WWW is the
5757 number of words of the XXX word long segment
5758 int_unpaged_page_tables used to hold page tables
5759 for temporary collection 1 segments.
5760
5761 Action: No operator action is required.
5762
5763
5764
5765 announce_chwm.pl1
5766 announce_chwm: WWW. words used of XXX. in
5767 unpaged_page_tables.
5768
5769
5770 Stream: BOS Typewriter.
5771
5772 Time: System Intialization.
5773
5774 Meaning: This message is produced when the CHWM parameter
5775 is specified on the PARM CONFIG card. WWW is the
5776 number of words of the XXX word long segment
5777 unpaged_page_tables used to hold page tables for
5778 permanent "unpaged" segments.
5779
5780 Action: No operator action is required.
5781
5782
5783
5784 append.pl1
5785 append: error from delete_vtoce for PATH:
5786 ERROR_MESSAGE
5787
5788
5789 Stream: Logged in SYSERR log.
5790
5791 Time: While system is running.
5792
5793 Meaning: While deleting a VTOC entry to clean up an
5794 unsuccessful attempt to create an branch append
5795 got an error. This indicates a logic error in the
5796 supervisor or CPU or memory hardware problems.
5797
5798 Action: Note for system programmer action.
5799
5800
5801 append -100- MR12.5 10/27/92^L
5802
5803
5804 append.pl1
5805 append: error from hash$out for PATH: ERROR_CODE
5806
5807
5808 Stream: Logged in SYSERR log.
5809
5810 Time: While system is running.
5811
5812 Meaning: While removing a name to clean up an unsuccessful
5813 attempt to create a branch append got an error.
5814 This indicates a logic error in the supervisor or
5815 CPU or memory hardware problems.
5816
5817 Action: Note for system programmer action.
5818
5819
5820
5821 append.pl1
5822 append: error from makeunknown_ for PATH:
5823 ERROR_CODE
5824
5825
5826 Stream: Logged in SYSERR log.
5827
5828 Time: While system is running.
5829
5830 Meaning: Append made the new directory PATH unknown after
5831 initializing its header. While doing so it
5832 encountered an error. This indicates a logic
5833 error in the supervisor or CPU or memory hardware
5834 problems.
5835
5836 Action: Note for system programmer action.
5837
5838
5839
5840 append.pl1
5841 append: makeunknown_ err after quota err for
5842 PATH: ERROR_CODE
5843
5844
5845 Stream: Logged in SYSERR log.
5846
5847 Time: While system is running.
5848
5849 Meaning: During the creation of a new directory append
5850 encountered an error moving quota. While cleaning
5851 up from this error a further error was
5852 encountered. The system continues to operate.
5853 This indicates a logic error in the supervisor or
5854 CPU or memory hardware problems.
5855
5856 Action: Note for system programmer action.
5857
5858
5859 append -101- MR12.5 10/27/92^L
5860
5861
5862 as_add_admin_acl_.pl1
5863 as_add_admin_acl_: ERROR_MESSAGE. Could not add
5864 PGID to ACL of PATH.
5865
5866
5867 Stream: as severity2
5868
5869 Time: Answering Service initialization or while the
5870 system is running.
5871
5872 Meaning: An error occurred while trying to rebuild the
5873 access control list ACL on PATH where:
5874
5875 ERROR_MESSAGE is an error_table_ message
5876 PGID is a process group id
5877 PATH is a full pathname
5878
5879 Action: Manually give PGID read access or status
5880 permission to PATH.
5881
5882
5883
5884 as_add_admin_acl_.pl1
5885 as_add_admin_acl_: ERROR_MESSAGE. Could not add
5886 to ACL of PATH.
5887
5888
5889 Stream: as severity2
5890
5891 Time: Answering Service initialization or while the
5892 system is running.
5893
5894 Meaning: Some fatal error occurred while rebuilding the
5895 access control list ACL of PATH. ERROR_MESSAGE
5896 is an error_table_ message and PATH is the full
5897 pathname of a segment or a directory.
5898
5899 Action: Contact the system programming staff. The
5900 operation that caused the error must be determined
5901 and the operation repeated after correction.
5902
5903
5904
5905
5906
5907
5908
5909
5910
5911
5912
5913
5914
5915
5916
5917 as_add_admin_acl_ -102- MR12.5 10/27/92^L
5918
5919
5920 as_dump_.pl1
5921 as_dump_: Answering service dump created in
5922 segment >sc1>asdump.-.MM/DD/YY-HHMM
5923
5924
5925 Stream: as severity1
5926
5927 Time: While system is running.
5928
5929 Meaning: Some program has encountered an unexpected fault
5930 and has called for a dump of the Answering
5931 Service. This segment is automatically dprinted.
5932
5933 Action: No operator action is required.
5934
5935
5936
5937 as_dump_.pl1
5938 as_dump_: Cannot attach I/O switch. No dump NAME
5939
5940
5941 Stream: as severity2
5942
5943 Time: While system is running.
5944
5945 Meaning: An error occurred while dumping. No dump was
5946 taken.
5947
5948 Action: Contact the system programming staff.
5949
5950
5951
5952 as_dump_.pl1
5953 as_dump_: Cannot obtain quota dump aborted.
5954 NAME
5955
5956
5957 Stream: as severity2
5958
5959 Time: While system is running.
5960
5961 Meaning: An error occurred while dumping. No dump was
5962 taken.
5963
5964 Action: Contact the system programming staff.
5965
5966
5967
5968
5969
5970
5971
5972
5973
5974
5975 as_dump_ -103- MR12.5 10/27/92^L
5976
5977
5978 as_dump_.pl1
5979 as_dump_: CONDITION while dumping. Dump aborted
5980
5981
5982 Stream: as severity1
5983
5984 Time: While system is running.
5985
5986 Meaning: During the attempt to perform an Answering Service
5987 dump some unexpected fault occurred. The dump is
5988 stopped and the system tries to continue.
5989
5990 Action: Notify the system programming staff.
5991
5992
5993
5994 as_dump_.pl1
5995 as_dump_: ERROR_MESSAGE. Cannot attach
5996 as_dump_stream_ to FILENAME. No dump
5997 asdump.MM/DD/YY-HHMM
5998
5999
6000 Stream: as severity1
6001
6002 Time: While system is running.
6003
6004 Meaning: The Answering Service dump program could not
6005 attach a file for the Answering Service dump. The
6006 dump will abort and the system will continue.
6007
6008 Action: Contact the system programming staff.
6009
6010
6011
6012 as_dump_.pl1
6013 as_dump_: ERROR_MESSAGE. Cannot obtain quota of
6014 >sc1 dump aborted. DUMPID
6015
6016
6017 Stream: as severity2
6018
6019 Time: While system is running.
6020
6021 Meaning: An error occurred while dumping. No dump was
6022 taken.
6023
6024 Action: Contact the system programming staff.
6025
6026
6027
6028
6029
6030
6031
6032
6033 as_dump_ -104- MR12.5 10/27/92^L
6034
6035
6036 as_dump_.pl1
6037 as_dump_: Message coordinator dump created in
6038 segment >sc1>asdump.-.MM/DD/YY-HHMM
6039
6040
6041 Stream: BOS Typewriter.
6042
6043 Time: While system is running.
6044
6045 Meaning: Some program has encountered an unexpected fault
6046 and has called for a dump of the message
6047 coordinator. This segment is automatically
6048 dprinted.
6049
6050 Action: No operator action is required.
6051
6052
6053
6054 as_dump_.pl1
6055 as_dump_: Out of room for dump DUMPID
6056
6057
6058 Stream: as severity2
6059
6060 Time: While system is running.
6061
6062 Meaning: An error occurred while dumping. No dump was
6063 taken.
6064
6065 Action: Contact the system programming staff.
6066
6067
6068
6069
6070
6071
6072
6073
6074
6075
6076
6077
6078
6079
6080
6081
6082
6083
6084
6085
6086
6087
6088
6089
6090
6091 as_dump_ -105- MR12.5 10/27/92^L
6092
6093
6094 as_hasp_mpx_.pl1
6095 as_hasp_mpx_: Crash signalled for multiplexer
6096 TTY.
6097
6098
6099 Stream: $as1
6100
6101 Time: While system is running.
6102
6103 Meaning: The physical connection for the HASP multiplexer
6104 on channel TTY has been broken either because of
6105 an error or or because of a request from the
6106 remote host/workstation.
6107
6108 Action: Check the console for a message concerning this
6109 channel from hasp_mpx. If such a message is
6110 found refer to its documentation for further
6111 action; otherwise the remote host/workstation has
6112 requested termination of the connection and the
6113 I/O daemons using this channel should be logged
6114 out.
6115
6116
6117
6118 as_hasp_mpx_.pl1
6119 as_hasp_mpx_: Duplicate subchannel name NAME for
6120 HASP multiplexer TTY.
6121
6122
6123 Stream: $as1
6124
6125 Time: In response to a load_mpx operator command or
6126 during system initialization.
6127
6128 Meaning: The same name has been used for two or more
6129 subchannels of the HASP multiplexer on channel
6130 TTY.
6131
6132 Action: Correct the CDT entry for this multiplexer and
6133 reload it.
6134
6135
6136
6137
6138
6139
6140
6141
6142
6143
6144
6145
6146
6147
6148
6149 as_hasp_mpx_ -106- MR12.5 10/27/92^L
6150
6151
6152 as_hasp_mpx_.pl1
6153 as_hasp_mpx_: ERROR_MESSAGE. Cannot get
6154 additional info from terminal type NAME for
6155 multiplexer TTY.
6156
6157
6158 Stream: $as1
6159
6160 Time: In response to a load_mpx operator command or
6161 during system initialization.
6162
6163 Meaning: The terminal type specified by NAME was not given
6164 an additional_info string in its TTT entry. This
6165 string is required to specify the configuration
6166 parameters for the HASP multiplexer on channel
6167 TTY.
6168
6169 Action: Check both the CDT entry for this multiplexer and
6170 the TTT entry for the terminal type. Either the
6171 wrong terminal type was specified in the CDT or
6172 the terminal type's definition is incomplete.
6173 Correct whichever table is in error and reload the
6174 multiplexer.
6175
6176
6177
6178 as_hasp_mpx_.pl1
6179 as_hasp_mpx_: ERROR_MESSAGE. Creating event
6180 channel for multiplexer TTY.
6181
6182
6183 Stream: $as1
6184
6185 Time: In response to a load_mpx operator command or
6186 during system initialization.
6187
6188 Meaning: A system error arose during the initialization of
6189 the HASP multiplexer on channel TTY.
6190
6191 Action: Contact the system programming staff.
6192
6193
6194
6195
6196
6197
6198
6199
6200
6201
6202
6203
6204
6205
6206
6207 as_hasp_mpx_ -107- MR12.5 10/27/92^L
6208
6209
6210 as_hasp_mpx_.pl1
6211 as_hasp_mpx_: Invalid PARM specification in
6212 terminal type NAME for multiplexer TTY.
6213
6214
6215 Stream: $as1
6216
6217 Time: In response to a load_mpx operator command or
6218 during system initialization.
6219
6220 Meaning: The value specified for the configuration
6221 parameter PARM in the additional info string of
6222 the terminal type NAME used for the HASP
6223 multiplexer on channel TTY is not acceptable to
6224 the system.
6225
6226 Action: Correct the value of the parameter in the TTT and
6227 reload the multiplexer.
6228
6229
6230
6231 as_hasp_mpx_.pl1
6232 as_hasp_mpx_: Invalid subchannel name NAME for
6233 HASP multiplexer TTY.
6234
6235
6236 Stream: $as1
6237
6238 Time: In response to a load_mpx operator command or
6239 during system initialization.
6240
6241 Meaning: The name specified for a subchannel of the HASP
6242 multiplexer on channel TTY does not conform to the
6243 conventions defined in MAM Communications for
6244 naming such channels.
6245
6246 Action: Correct the CDT entry for this multiplexer and
6247 reload it.
6248
6249
6250
6251
6252
6253
6254
6255
6256
6257
6258
6259
6260
6261
6262
6263
6264
6265 as_hasp_mpx_ -108- MR12.5 10/27/92^L
6266
6267
6268 as_hasp_mpx_.pl1
6269 as_hasp_mpx_: Line type for hasp operator console
6270 on multiplexer TTY must be "HASP_OPR" when
6271 configured for login service.
6272
6273
6274 Stream: $as1
6275
6276 Time: In response to a load_mpx operator command or
6277 during system initialization.
6278
6279 Meaning: The line type must be set for HASP_OPR on a hasp
6280 operator console subchannel when it is configured
6281 for login service.
6282
6283 Action: Correct the CDT entry for this multiplexer and
6284 reload it.
6285
6286
6287
6288 as_hasp_mpx_.pl1
6289 as_hasp_mpx_: Load signalled for multiplexer TTY.
6290
6291
6292 Stream: $as1
6293
6294 Time: While system is running.
6295
6296 Meaning: The physical connection and initial connection
6297 protocl for the HASP multiplexer on channel TTY
6298 has been completed successfully. The multiplexer
6299 is now ready for use.
6300
6301 Action: Start the appropriate I/O daemon processes for the
6302 multiplexer as indicated by the system
6303 administrators or by the user who requested the
6304 multiplexer be loaded.
6305
6306
6307
6308
6309
6310
6311
6312
6313
6314
6315
6316
6317
6318
6319
6320
6321
6322
6323 as_hasp_mpx_ -109- MR12.5 10/27/92^L
6324
6325
6326 as_hasp_mpx_.pl1
6327 as_hasp_mpx_: More than 17 subchannels specified
6328 for HASP multiplexer TTY COUNT.
6329
6330
6331 Stream: $as1
6332
6333 Time: In response to a load_mpx operator command or
6334 during system initialization.
6335
6336 Meaning: The definition of the HASP multiplexer on channel
6337 TTY contains too many subchannels.
6338
6339 Action: Correct the CDT entry for this multiplexer and
6340 reload it.
6341
6342
6343
6344 as_hasp_mpx_.pl1
6345 as_hasp_mpx_: Subchannel NAME of multiplexer TTY
6346 does not have TYPE service type.
6347
6348
6349 Stream: $as1
6350
6351 Time: In response to a load_mpx operator command or
6352 during system initialization.
6353
6354 Meaning: The specified subchannel of the HASP multiplexer
6355 on channel TTY was not given the slave service
6356 type or in the case of operator console
6357 subchannels slave or login.
6358
6359 Action: Correct the CDT entry for this multiplexer and
6360 reload it.
6361
6362
6363
6364
6365
6366
6367
6368
6369
6370
6371
6372
6373
6374
6375
6376
6377
6378
6379
6380
6381 as_hasp_mpx_ -110- MR12.5 10/27/92^L
6382
6383
6384 as_hasp_mpx_.pl1
6385 as_hasp_mpx_: Too many printers and punches
6386 configured for HASP multiplexer TTY.
6387
6388
6389 Stream: $as1
6390
6391 Time: In response to a load_mpx operator command or
6392 during system initialization.
6393
6394 Meaning: More than 8 card punches and line printers have
6395 been specified for the HASP multiplexer on channel
6396 TTY or a card punch and line printer which use the
6397 same flow control flag have been specified. See
6398 MAM Communications for a description of the rules
6399 for naming card punches and line printers.
6400
6401 Action: Correct the CDT entry for this multiplexer and
6402 reload it.
6403
6404
6405
6406 as_hasp_mpx_.pl1
6407 as_hasp_mpx_: Unexpected wakeup DATA1 DATA2
6408 from process ID.
6409
6410
6411 Stream: $as1
6412
6413 Time: While system is running.
6414
6415 Meaning: A message was received from the process whose
6416 processid is the 12-digit octal value ID; the
6417 contents of the message are given by the two
6418 12-digit octal values DATA1 and DATA2. No message
6419 was expected at this time. The wakeup is ignored.
6420
6421 Action: No operator action is required.
6422
6423
6424
6425
6426
6427
6428
6429
6430
6431
6432
6433
6434
6435
6436
6437
6438
6439 as_hasp_mpx_ -111- MR12.5 10/27/92^L
6440
6441
6442 as_hasp_mpx_.pl1
6443 as_hasp_mpx_: Wakeup from multiplexer TTY has
6444 invalid state code VALUE.
6445
6446
6447 Stream: $as1
6448
6449 Time: While system is running.
6450
6451 Meaning: A message was received indicating a change of
6452 state for the multiplexer on channel TTY; however
6453 the new state of the multiplexer given by the
6454 decimal number VALUE is not recognized by this
6455 module.
6456
6457 Action: Contact the system programming staff.
6458
6459
6460
6461 as_init_.pl1
6462 as_init_: Answering Service initialization
6463 failed.
6464
6465
6466 Stream: $as2
6467
6468 Time: System Intialization.
6469
6470 Meaning: This indicates a logic error in the supervisor or
6471 CPU or memory hardware problems. Answering
6472 Service initialization failed. Normally this
6473 message is preceded by a more specific indication
6474 of the reason for failure.
6475
6476 Action: Contact the system programming staff. Attempt to
6477 correct the problem and try startup again.
6478
6479
6480
6481 as_init_.pl1
6482 as_init_: CDT rethreading complete.
6483
6484
6485 Stream: $as1
6486
6487 Time: System Intialization.
6488
6489 Meaning: Rethreading of Channel Definition Table CDT
6490 entries into a multiplexer/subchannel hierarchy
6491 completed successfully. System initialization
6492 continues.
6493
6494 Action: Contact the system administrator.
6495
6496
6497 as_init_ -112- MR12.5 10/27/92^L
6498
6499
6500 as_init_.pl1
6501 as_init_: CDT threading inconsistency found.
6502 Rethreading.
6503
6504
6505 Stream: $as1
6506
6507 Time: System Intialization.
6508
6509 Meaning: An error was detected while tracing the threading
6510 of Channel Definition Table CDT entries into a
6511 hierarchy of multiplexer and subchannel entries.
6512 $err The entire channel hierarchy will be
6513 rethreaded.
6514
6515 Action: Contact the system administrator.
6516
6517
6518
6519 as_init_.pl1
6520 as_init_: Condition COND signalled during
6521 startup. Taking AS dump. CONDITION_INFO
6522
6523
6524 S. $as1
6525
6526 Time: System Intialization.
6527
6528 Meaning: An unexpected condition COND occurred during
6529 system initialization. An answering service dump
6530 is taken. The stack trace information in this
6531 dump further describes the error. Some steps of
6532 Answering Service initialization were not
6533 performed. This may cause the system to operate
6534 incorrectly. CONDITION_INFO if optionally present
6535 if further information about the condition is
6536 available.
6537
6538 Action: Contact the system programming staff.
6539
6540
6541
6542
6543
6544
6545
6546
6547
6548
6549
6550
6551
6552
6553
6554
6555 as_init_ -113- MR12.5 10/27/92^L
6556
6557
6558 as_init_.pl1
6559 as_init_: Condition was signalled while
6560 processing another condition. CONDITION
6561
6562
6563 Stream: BOS Typewriter sounds beeper
6564
6565 Time: System Intialization.
6566
6567 Meaning: This indicates a logic error in the supervisor or
6568 CPU or memory hardware problems. During Answering
6569 Service initialization a CONDITION was raised
6570 while as_init_ was already processing some
6571 condition. It may be that the error occured while
6572 making an as_dump for the first condition.
6573 as_init_ will not attempt to make an as_dump but
6574 will instead abort the initialization.
6575
6576 Action: Contact the system programming staff.
6577
6578
6579
6580 as_init_.pl1
6581 as_init_: ERROR_MESSAGE.
6582
6583
6584 Stream: $as1
6585
6586 Time: System Intialization.
6587
6588 Meaning: A fatal error occurred during Answering Service
6589 initialization. Previous messages describe the
6590 error in more detail.
6591
6592 Action: Contact the system administrator.
6593
6594
6595
6596
6597
6598
6599
6600
6601
6602
6603
6604
6605
6606
6607
6608
6609
6610
6611
6612
6613 as_init_ -114- MR12.5 10/27/92^L
6614
6615
6616 as_init_.pl1
6617 as_init_: ERROR_MESSAGE. Calling
6618 multiplexer_mgr_$ENTRYPOINT.
6619
6620
6621 Stream: $as1
6622
6623 Time: System Intialization.
6624
6625 Meaning: The multiplexer_mgr_ failed when accessing the
6626 Channel Definition Table CDT in >sc1
6627 initializing the CDT or loading the FNPs.
6628 ERROR_MESSAGE is the text associated with the
6629 error code returned by multiplexer_mgr_.
6630 Answering service initialization fails. The
6631 system administrator must enter admin mode and
6632 correct the problem. Then reboot the system.
6633
6634 Action: Contact the system administrator.
6635
6636
6637
6638 as_init_.pl1
6639 as_init_: ERROR_MESSAGE. Calling ROUTINE.
6640
6641
6642 Stream: $as1
6643
6644 Time: System Intialization.
6645
6646 Meaning: An error occurred when calling ROUTINE during
6647 Answering Service initialization. ERROR_MESSAGE
6648 is the text associated with the error code
6649 returned by ROUTINE. Answering service
6650 initialization fails. The system administrator
6651 must enter admin mode and correct the problem.
6652 Then reboot the system.
6653
6654 Action: Contact the system administrator.
6655
6656
6657
6658
6659
6660
6661
6662
6663
6664
6665
6666
6667
6668
6669
6670
6671 as_init_ -115- MR12.5 10/27/92^L
6672
6673
6674 as_init_.pl1
6675 as_init_: ERROR_MESSAGE. Cannot create pit_temp_
6676
6677
6678 Stream: $as1
6679
6680 Time: System Intialization.
6681
6682 Meaning: The system could not create a temporary segment in
6683 the Answering Service process's process directory.
6684 This is a fatal error that will cause answering
6685 service startup to fail.
6686
6687 Action: Contact the system administrator.
6688
6689
6690
6691 as_init_.pl1
6692 as_init_: ERROR_MESSAGE. Cannot create sat.ht.
6693 REASON
6694
6695
6696 Stream: $as1
6697
6698 Time: System Intialization.
6699
6700 Meaning: This message indicates that the sat is damaged or
6701 that a storage system error prevented the creation
6702 of a new hash table for the sat. Answering
6703 Service startup will fail.
6704
6705 Action: Contact the system administrator.
6706
6707
6708
6709
6710
6711
6712
6713
6714
6715
6716
6717
6718
6719
6720
6721
6722
6723
6724
6725
6726
6727
6728
6729 as_init_ -116- MR12.5 10/27/92^L
6730
6731
6732 as_init_.pl1
6733 as_init_: ERROR_MESSAGE. cdt_mgr_$thread:
6734 ADDED_INFO
6735
6736
6737 Stream: $as1
6738
6739 Time: System Intialization.
6740
6741 Meaning: as_init_ called cdt_mgr_$thread to rethread the
6742 Channel Definition Table CDT entries into a
6743 multiplexer/subchannel hierarchy. cdt_mgr_
6744 encountered an unexpected error. ERROR_MESSAGE is
6745 the text associated with the error code returned
6746 by cdt_mgr_. ADDED_INFO further describes the
6747 error and whether or not further rethreading is
6748 attempted.
6749
6750 Action: Contact the system administrator.
6751
6752
6753
6754 as_init_.pl1
6755 as_init_: ERROR_MESSAGE. Could not create
6756 SYSTEM_CONTROL_DIR>TABLE.
6757
6758
6759 Stream: $as1
6760
6761 Time: System Intialization.
6762
6763 Meaning: The Initializer could not create a new segment
6764 TABLE in SYSTEM_CONTROL_DIR. Answering service
6765 initialization fails. The system administrator
6766 must enter admin mode and type "create TABLE"
6767 where TABLE is the name given above. Then reboot
6768 the system.
6769
6770 Action: Contact the system administrator.
6771
6772
6773
6774
6775
6776
6777
6778
6779
6780
6781
6782
6783
6784
6785
6786
6787 as_init_ -117- MR12.5 10/27/92^L
6788
6789
6790 as_init_.pl1
6791 as_init_: ERROR_MESSAGE. Could not force access
6792 on SYSTEM_CONTROL_DIR>TABLE.
6793
6794
6795 Stream: $as1
6796
6797 Time: System Intialization.
6798
6799 Meaning: The Initializer could not change the ACL on the
6800 TABLE segment in SYSTEM_CONTROL_DIR. Answering
6801 service initialization fails. The system
6802 administrator must enter admin mode and correct
6803 the problem. Then reboot the system.
6804
6805 Action: Contact the system administrator.
6806
6807
6808
6809
6810
6811
6812 as_init_.pl1
6813 as_init_: ERROR_MESSAGE. Could not initiate
6814 SYSTEM_CONTROL_DIR>TABLE.
6815
6816
6817 Stream: $as1
6818
6819 Time: System Intialization.
6820
6821 Meaning: The Initializer could not initiate the TABLE
6822 segment in SYSTEM_CONTROL_DIR. Answering service
6823 initialization fails. The system administrator
6824 must enter admin mode and correct the problem.
6825 Then reboot the system.
6826
6827 Action: Contact the system administrator.
6828
6829
6830
6831
6832
6833
6834
6835
6836
6837
6838
6839
6840
6841
6842
6843
6844
6845 as_init_ -118- MR12.5 10/27/92^L
6846
6847
6848 as_init_.pl1
6849 as_init_: ERROR_MESSAGE. Could not set priority
6850 for IPC wait channels.
6851
6852
6853 Stream: $as1
6854
6855 Time: System Intialization.
6856
6857 Meaning: A call to ipc_$set_wait_prior failed. This
6858 indicates a logic error in the supervisor or CPU
6859 or memory hardware problems.
6860
6861 Action: Contact the system administrator.
6862
6863
6864
6865 as_init_.pl1
6866 as_init_: ERROR_MESSAGE. Could not set RW access
6867 on SYSTEM_CONTROL_DIR>TABLE.
6868
6869
6870 Stream: $as1
6871
6872 Time: System Intialization.
6873
6874 Meaning: An error occurred attempting to add ACL entries to
6875 TABLE in SYSTEM_CONTROL_DIR. Answering Service
6876 initialization fails. The system administrator
6877 must enter admin mode and correct the problem.
6878 Then reboot the system.
6879
6880 Action: Contact the system administrator.
6881
6882
6883
6884 as_init_.pl1
6885 as_init_: ERROR_MESSAGE. Error while defining
6886 initial work classes.
6887
6888
6889 Stream: $as1
6890
6891 Time: System Intialization.
6892
6893 Meaning: This indicates a logic error in the supervisor or
6894 CPU or memory hardware problems. Answering
6895 Service initialization fails. The system
6896 administrator must enter admin mode and correct
6897 the problem. Then reboot the system.
6898
6899 Action: Contact the system administrator.
6900
6901
6902
6903 as_init_ -119- MR12.5 10/27/92^L
6904
6905
6906 as_init_.pl1
6907 as_init_: ERROR_MESSAGE. Initialization of
6908 MODULE failed. ADDED_INFO.
6909
6910
6911 Stream: $as1
6912
6913 Time: System Intialization.
6914
6915 Meaning: MODULE was being initialized when it detected a
6916 problem. It called sub_err_ to report the error
6917 to as_init_. ERROR_MESSAGE gives the text
6918 associated with the error code MODULE returned to
6919 as_init_. If present ADDED_INFO gives further
6920 details about the problem. Some steps of
6921 Answering Service initialization were not
6922 performed. This may cause the system to operate
6923 incorrectly.
6924
6925 Action: Contact the system programming staff.
6926
6927
6928
6929 as_init_.pl1
6930 as_init_: ERROR_MESSAGE. MODULE signalled
6931 sub_error_; initialization continues.
6932 ADDED_INFO.
6933
6934
6935 Stream: $as1
6936
6937 Time: System Intialization.
6938
6939 Meaning: MODULE was being initialized when it detected a
6940 problem. It called sub_err_ to report the error
6941 to as_init_. ERROR_MESSAGE gives the text
6942 associated with the error code MODULE returned to
6943 as_init_. If present ADDED_INFO gives further
6944 details about the problem. Initialization of the
6945 module continues.
6946
6947 Action: $contact.
6948
6949
6950
6951
6952
6953
6954
6955
6956
6957
6958
6959
6960
6961 as_init_ -120- MR12.5 10/27/92^L
6962
6963
6964 as_init_.pl1
6965 as_init_: ERROR_MESSAGE. Repeated CDT threading
6966 inconsistencies.
6967
6968
6969 Stream: $as1
6970
6971 Time: System Intialization.
6972
6973 Meaning: Channel Definition Table CDT entry threads were
6974 found to be damaged even after rethreading
6975 completed successfully. This indicates a logic
6976 error in the supervisor or CPU or memory hardware
6977 problems.
6978
6979 Action: Contact the system administrator.
6980
6981
6982
6983 as_init_.pl1
6984 as_init_: ERROR_MESSAGE. Shutting down the login
6985 server request mechanism.
6986
6987
6988 Stream: $as1
6989
6990 Time: System shutdown.
6991
6992 Meaning: An error occurred while shutting down the login
6993 server request mechanism. The ERROR_MESSAGE gives
6994 the text associated with the error code returned
6995 from ls_request_server_$shutdown.
6996
6997 Action: No operator action is required.
6998
6999
7000
7001 as_init_.pl1
7002 as_init_: ERROR_MESSAGE.
7003 SYSTEM_CONTROL_DIR>TABLE. Forcing access.
7004
7005
7006 Stream: $as1
7007
7008 Time: System Intialization.
7009
7010 Meaning: During system initialization TABLE in
7011 SYSTEM_CONTROL_DIR was found to have an incorrect
7012 ACL. Access was set for Initializer.SysDaemon.
7013
7014 Action: No operator action is required.
7015
7016
7017
7018
7019 as_init_ -121- MR12.5 10/27/92^L
7020
7021
7022 as_init_.pl1
7023 as_init_: installation_parms damaged. N rate
7024 structures defined; from I to J allowed.
7025
7026
7027 Stream: $as1
7028
7029 Time: System Intialization.
7030
7031 Meaning: The installation_parms table claims to declare an
7032 unallowed number of rate structures. This
7033 indicates that the table has been damaged. The
7034 system administrator must rectify the problem
7035 using ed_installation_parms from admin mode
7036 before the Answering Service will initialize. It
7037 will be necessary to re-boot Multics to retry
7038 Answering Service initialization.
7039
7040 Action: Contact the system administrator.
7041
7042
7043
7044 as_init_.pl1
7045 as_init_: Multics SYSID; Answering Service
7046 VERSION
7047
7048
7049 Stream: $as1
7050
7051 Time: System Intialization.
7052
7053 Meaning: Answering Service initialization is complete and
7054 users may now log in. The current system version
7055 number from the system tape is SYSID. The
7056 current Answering Service version number is
7057 VERSION.
7058
7059 Action: Proceed with startup.
7060
7061
7062
7063
7064
7065
7066
7067
7068
7069
7070
7071
7072
7073
7074
7075
7076
7077 as_init_ -122- MR12.5 10/27/92^L
7078
7079
7080 as_init_.pl1
7081 as_init_: No "tcd" card in the config deck.
7082 Assuming APT size of 1000.
7083
7084
7085 Stream: $as1
7086
7087 Time: System Intialization.
7088
7089 Meaning: This message indicates that there is no TCD card
7090 in the config deck. The system will operate
7091 normally but it is recommended that an explicit
7092 TCD card be added at the first convenience.
7093
7094 Action: Contact the system administrator.
7095
7096
7097
7098 as_init_.pl1
7099 as_init_: rebuilding SAT hash table.
7100
7101
7102 Stream: $as1
7103
7104 Time: System Intialization.
7105
7106 Meaning: The hash table for the SAT was corrupted. The
7107 hash table is regenerated.
7108
7109 Action: No operator action is required.
7110
7111
7112
7113 as_init_.pl1
7114 as_init_: Resource management is disabled;
7115 >sc1>rtdt needs it enabled.
7116
7117
7118 Stream: $as1
7119
7120 Time: System Intialization.
7121
7122 Meaning: The copy of installation_parms encountered by
7123 system startup claims that RCP resource management
7124 is disabled. This disagrees with information in
7125 the RTDT. If startup were to continue all
7126 information in resource registries would be lost.
7127 Answering Service initialization fails. The
7128 system administrator must use
7129 ed_installation_parms from admin mode to repair
7130 the damage. Then reboot the system.
7131
7132 Action: Contact the system administrator.
7133
7134
7135 as_init_ -123- MR12.5 10/27/92^L
7136
7137
7138 as_init_.pl1
7139 as_init_: SAT version inconsistent with
7140 declarations used in this program.
7141
7142
7143 Stream: $as1
7144
7145 Time: System Intialization.
7146
7147 Meaning: The version number stored in the SAT does not
7148 match the expected version number which is a
7149 constant in the Answering Service programs. This
7150 may be because the SAT has been destroyed or
7151 because an incorrect version of the Answering
7152 Service programs is being used. This error
7153 crashes the system.
7154
7155 Action: Contact the system administrator. The System
7156 Administrator must either generate a new SAT or
7157 install the correct version of the Answering
7158 Service. If the System Administrator is not
7159 available enter admin mode and attempt to
7160 retrieve a recent copy of the SAT. Then exit from
7161 admin mode and try startup again.
7162
7163
7164
7165 as_init_.pl1
7166 as_init_: SYSTEM_CONTROL_DIR>TABLE missing.
7167 Creating new one.
7168
7169
7170 Stream: $as1
7171
7172 Time: System Intialization.
7173
7174 Meaning: A new version of TABLE was created in
7175 SYSTEM_CONTROL_DIR as part of system
7176 initialization.
7177
7178 Action: No operator action is required.
7179
7180
7181
7182
7183
7184
7185
7186
7187
7188
7189
7190
7191
7192
7193 as_init_ -124- MR12.5 10/27/92^L
7194
7195
7196 as_init_.pl1
7197 as_init_: The requested action was not performed.
7198 Cannot type go twice.
7199
7200
7201 Stream: $as1
7202
7203 Time: System Intialization.
7204
7205 Meaning: The operator typed go when Multics was already in
7206 operation. No action was taken.
7207
7208 Action: No operator action is required.
7209
7210
7211
7212 as_init_.pl1
7213 as_init_: The requested action was not performed.
7214 Type multics first.
7215
7216
7217 Stream: $as1
7218
7219 Time: System Intialization.
7220
7221 Meaning: The operator typed go without typing multics. No
7222 action was taken.
7223
7224 Action: Type multics first or startup.
7225
7226
7227
7228 as_init_.pl1
7229 as_init_: The requested action was not performed.
7230 Multics already initialized.
7231
7232
7233 Stream: $as1
7234
7235 Time: System Intialization.
7236
7237 Meaning: The operator typed startup multics or go when
7238 Multics was already in operation. No action was
7239 taken.
7240
7241 Action: No operator action is required.
7242
7243
7244
7245
7246
7247
7248
7249
7250
7251 as_init_ -125- MR12.5 10/27/92^L
7252
7253
7254 as_init_.pl1
7255 as_init_: This procedure does not implement the
7256 requested version. installation_parms version N.
7257
7258
7259 Stream: $as1
7260
7261 Time: System Intialization.
7262
7263 Meaning: This indicates a logic error in the supervisor or
7264 CPU or memory hardware problems. The
7265 installation_parms segment has been damaged or is
7266 not up-to-date. The system administrator must
7267 rectify the problem using ed_installation_parms
7268 from admin mode before the Answering Service will
7269 initialize. It will be necessary to re-boot
7270 Multics to retry Answering Serviceinitialization.
7271
7272 Action: Contact the system administrator.
7273
7274
7275
7276 as_lap_mpx_.pl1
7277 as_lap_mpx: Unexpected signal for multiplexer
7278 MPX.
7279
7280
7281 Stream: as severity1
7282
7283 Time: While system is running.
7284
7285 Meaning: An unknown type event was signaled for multiplexer
7286 MPX. It will be ignored.
7287
7288 Action: Contact the system programming staff.
7289
7290
7291
7292
7293
7294
7295
7296
7297
7298
7299
7300
7301
7302
7303
7304
7305
7306
7307
7308
7309 as_lap_mpx -126- MR12.5 10/27/92^L
7310
7311
7312 as_lap_mpx_.pl1
7313 as_lap_mpx_: Bad argument to parm PPPP should be
7314 XXXX or YYYY
7315
7316
7317 Stream: as severity1
7318
7319 Time: In response to an operator load_mpx command for
7320 during system startup.
7321
7322 Meaning: A bad value was specified for the PPPP parameter
7323 in the TTF entry for this muliplexer. Its value
7324 must be either XXXX or YYYY.
7325
7326 Action: Check the contents of the TTF entry for the
7327 terminal_type associated with the multiplexer for
7328 errors.
7329
7330
7331
7332 as_lap_mpx_.pl1
7333 as_lap_mpx_: Crash signalled for multiplexer MPX.
7334
7335
7336 Stream: as severity1
7337
7338 Time: While system is running.
7339
7340 Meaning: The multiplexer has crashed. The LAP link has
7341 entered the disconnected state.
7342
7343 Action: Contact the system programming staff.
7344
7345
7346
7347
7348
7349
7350
7351
7352
7353
7354
7355
7356
7357
7358
7359
7360
7361
7362
7363
7364
7365
7366
7367 as_lap_mpx_ -127- MR12.5 10/27/92^L
7368
7369
7370 as_lap_mpx_.pl1
7371 as_lap_mpx_: Error in conversion. Converting
7372 FIELD VALUE to a number for multiplexer MPX.
7373
7374
7375 Stream: as severity1
7376
7377 Time: In response to an operator load_mpx command or
7378 during system start up.
7379
7380 Meaning: It was impossible to convert a numeric parameter
7381 from the terminal_type additional_info string to
7382 its internal form. FIELD is the name of the
7383 parameter in error. VALUE is the string which
7384 could not be converted.
7385
7386 Action: Check the contents of the TTF entry for the
7387 terminal_type associated with the multiplexer for
7388 errors.
7389
7390
7391
7392 as_lap_mpx_.pl1
7393 as_lap_mpx_: ERROR. Cannot get additional info
7394 for terminal type TTP for multiplexer MPX.
7395
7396
7397 Stream: as severity1
7398
7399 Time: In response to an operator load_mpx command or
7400 during system start up.
7401
7402 Meaning: An error occurred while retrieving the parameters
7403 of the multiplexer from the TTT. Either the
7404 terminal type specified in the CDT does not exist
7405 or it does not contain the required
7406 additional_info field.
7407
7408 Action: Check that the CMF and TTF contain the proper
7409 information.
7410
7411
7412
7413
7414
7415
7416
7417
7418
7419
7420
7421
7422
7423
7424
7425 as_lap_mpx_ -128- MR12.5 10/27/92^L
7426
7427
7428 as_lap_mpx_.pl1
7429 as_lap_mpx_: ERROR. Creating event channel for
7430 multiplexer MPX.
7431
7432
7433 Stream: as severity1
7434
7435 Time: In response to an operator load_mpx command or
7436 during system start up.
7437
7438 Meaning: An ipc_ error occurred while trying to initialize
7439 the multiplexer.
7440
7441 Action: Contact the system programming staff.
7442
7443
7444
7445 as_lap_mpx_.pl1
7446 as_lap_mpx_: Load failed for multiplexer MPX.
7447
7448
7449 Stream: as severity1
7450
7451 Time: In response to an operator load_mpx command or
7452 during system start up.
7453
7454 Meaning: The attempt to load the multiplexer failed. This
7455 should never happen.
7456
7457 Action: Contact the system programming staff.
7458
7459
7460
7461 as_lap_mpx_.pl1
7462 as_lap_mpx_: Load signalled for multiplexer MPX.
7463
7464
7465 Stream: as severity1
7466
7467 Time: In response to an operator load_mpx command or
7468 during system start up.
7469
7470 Meaning: The multiplexer has been successfully loaded. It
7471 will be started unless the -no_start control
7472 argument was given when the load_mpx command was
7473 typed.
7474
7475 Action: No operator action is required.
7476
7477
7478
7479
7480
7481
7482
7483 as_lap_mpx_ -129- MR12.5 10/27/92^L
7484
7485
7486 as_lap_mpx_.pl1
7487 as_lap_mpx_: Unexpected wakeup DATA from
7488 process PRCID.
7489
7490
7491 Stream: as severity1
7492
7493 Time: While system is running.
7494
7495 Meaning: The multiplexer manager received a wakeup from an
7496 unexpected source. The wakeup is ignored.
7497
7498 Action: No operator action is required.
7499
7500
7501
7502 as_lap_mpx_.pl1
7503 as_lap_mpx_: Wakeup for multiplexer MPX has
7504 invalid state code STATE.
7505
7506
7507 Stream: as severity1
7508
7509 Time: While system is running.
7510
7511 Meaning: A wakeup with invalid data was received by the
7512 multiplexer manager. The wakeup is ignored.
7513
7514 Action: Contact the system programming staff.
7515
7516
7517
7518 as_mcs_mpx_.pl1
7519 as_mcs_mpx_ trace: FNP FNP_NUMBER MPXE state
7520 MPX_STATE FNP state FNP_STATE deconfigured.
7521
7522
7523 Stream: $as1
7524
7525 Time: While system is running.
7526
7527 Meaning: This is a tracing message which displays some
7528 values of variables that describe the status of
7529 the FNP.
7530
7531 Action: Contact the system programming staff.
7532
7533
7534
7535
7536
7537
7538
7539
7540
7541 as_mcs_mpx_ trace -130- MR12.5 10/27/92^L
7542
7543
7544 as_mcs_mpx_.pl1
7545 as_mcs_mpx_: Crash signalled for FNP TAG.
7546
7547
7548 Stream: $as1
7549
7550 Time: While system is running.
7551
7552 Meaning: FNP TAG has crashed. A reload of the FNP will be
7553 attempted if it is not in a crash loop or not
7554 inactive.
7555
7556 Action: Contact the system programming staff.
7557
7558
7559
7560 as_mcs_mpx_.pl1
7561 as_mcs_mpx_: ERROR_CODE_MESSAGE
7562 >sc1>fnp_crash_notify.ec does not exist.
7563
7564
7565 Stream: $as1
7566
7567 Time: While system is running.
7568
7569 Meaning: An error occured ERROR_CODE_MESSAGE when
7570 checking for the existence of fnp_crash_notify.ec
7571 in the system_control_1 directory.
7572
7573 Action: Contact the system programming staff.
7574
7575
7576
7577 as_mcs_mpx_.pl1
7578 as_mcs_mpx_: ERROR_CODE_MESSAGE Creating event
7579 channel for FNP TAG.
7580
7581
7582 Stream: $as1
7583
7584 Time: While system is running.
7585
7586 Meaning: An error occured ERROR_CODE_MESSAGE when an
7587 attempt was made to create an event channel for
7588 FNP TAG. The load attempt has been aborted. This
7589 message can also be logged if an error occured
7590 when changing the just created event-wait channel
7591 into an event-call channel.
7592
7593 Action: Contact the system programming staff.
7594
7595
7596
7597
7598
7599 as_mcs_mpx_ -131- MR12.5 10/27/92^L
7600
7601
7602 as_mcs_mpx_.pl1
7603 as_mcs_mpx_: ERROR_CODE_MESSAGE Failed to
7604 establish an SCI environment.
7605
7606
7607 Stream: $as1
7608
7609 Time: While system is running.
7610
7611 Meaning: An error occured ERROR_CODE_MESSAGE when trying
7612 to create an system control subsystem environment
7613 pointer.
7614
7615 Action: Contact the system programming staff.
7616
7617
7618
7619 as_mcs_mpx_.pl1
7620 as_mcs_mpx_: ERROR_CODE_MESSAGE Reading event
7621 channel for FNP TAG.
7622
7623
7624 Stream: $as1
7625
7626 Time: While system is running.
7627
7628 Meaning: An error occured ERROR_CODE_MESSAGE when an
7629 attempt was made to read the bootload event
7630 channel for FNP TAG.
7631
7632 Action: Contact the system programming staff.
7633
7634
7635
7636 as_mcs_mpx_.pl1
7637 as_mcs_mpx_: ERROR_CODE_MESSAGE Resetting event
7638 channel for FNP TAG.
7639
7640
7641 Stream: $as1
7642
7643 Time: While system is running.
7644
7645 Meaning: An error occured ERROR_CODE_MESSAGE when an
7646 attempt was made to drain all events from the FNP
7647 boot event channel.
7648
7649 Action: Contact the system programming staff.
7650
7651
7652
7653
7654
7655
7656
7657 as_mcs_mpx_ -132- MR12.5 10/27/92^L
7658
7659
7660 as_mcs_mpx_.pl1
7661 as_mcs_mpx_: ERROR_CODE_MESSAGE Taking dump of
7662 FNP TAG. FNP_DUMP_ENTRY_NAME
7663
7664
7665 Stream: $as1
7666
7667 Time: While system is running.
7668
7669 Meaning: An error occured ERROR_CODE_MESSAGE when an
7670 attempt was made to dump FNP TAG into the
7671 FNP_DUMP_ENTRY_NAME segment in >dumps.
7672
7673 Action: Contact the system programming staff.
7674
7675
7676
7677 as_mcs_mpx_.pl1
7678 as_mcs_mpx_: FDUMP of FNP TAG created in
7679 >dumps>FNP_DUMP_ENTRY_NAME
7680
7681
7682 Stream: $as1
7683
7684 Time: While system is running.
7685
7686 Meaning: FNP TAG has been dumped successfully into the
7687 >dumps>FNP_DUMP_ENTRY_NAME segment after it
7688 crashed.
7689
7690 Action: Contact the system programming staff.
7691
7692
7693
7694 as_mcs_mpx_.pl1
7695 as_mcs_mpx_: Inconsistent wakeup received from
7696 FNP TAG. FNP state = FNP_STATE msg state =
7697 MSG_STATE.
7698
7699
7700 Stream: $as1
7701
7702 Time: While system is running.
7703
7704 Meaning: The data in the message from the bootload event
7705 channel for FNP TAG indicates that the FNP was in
7706 an inconsistant state MSG_STATE with the current
7707 state FNP_STATE of the FNP in the CDT.
7708
7709 Action: Contact the system programming staff.
7710
7711
7712
7713
7714
7715 as_mcs_mpx_ -133- MR12.5 10/27/92^L
7716
7717
7718 as_mcs_mpx_.pl1
7719 as_mcs_mpx_: Invalid wakeup received for FNP TAG.
7720 Wakeup appears to be for FNP OTHER_TAG
7721 #FNP_NUMBER.
7722
7723
7724 Stream: $as1
7725
7726 Time: While system is running.
7727
7728 Meaning: Invalid wakeup received on bootload event channel
7729 for FNP TAG. Wakeup data indicates it is for FNP
7730 OTHER_TAG whose number is FNP_NUMBER.
7731
7732 Action: Contact the system programming staff.
7733
7734
7735
7736 as_mcs_mpx_.pl1
7737 as_mcs_mpx_: Load failed for FNP TAG.
7738
7739
7740 Stream: $as1
7741
7742 Time: While system is running.
7743
7744 Meaning: The FNP TAG failed to load successfully.
7745
7746 Action: Try the bootload attempt again. If problem
7747 persists contact the programing staff.
7748
7749
7750
7751 as_mcs_mpx_.pl1
7752 as_mcs_mpx_: Load of FNP TAG did not complete
7753 within X minutes.
7754
7755
7756 Stream: $as2
7757
7758 Time: While system is running.
7759
7760 Meaning: FNP TAG did not signal that it had completed the
7761 load attempt within the required X minutes from
7762 the time that the image was sent to the FNP.
7763
7764 Action: Try to load the FNP again. If problem persists
7765 contact system programing staff.
7766
7767
7768
7769
7770
7771
7772
7773 as_mcs_mpx_ -134- MR12.5 10/27/92^L
7774
7775
7776 as_mcs_mpx_.pl1
7777 as_mcs_mpx_: Load signalled for FNP TAG.
7778
7779
7780 Stream: $as1
7781
7782 Time: While system is running.
7783
7784 Meaning: FNP TAG bootloaded successfully.
7785
7786 Action: No operator action is required.
7787
7788
7789
7790 as_mcs_mpx_.pl1
7791 as_mcs_mpx_: Procedure called with bad fnpep into
7792 cdt: POINTER
7793
7794
7795 Stream: $as1
7796
7797 Time: While system is running.
7798
7799 Meaning: The compute_fnp_no internal procedure detected
7800 that as_mcs_mpx_ was supplied with a prointer
7801 value POINTER that should point to an FNP entry
7802 in the CDT but doesn't. Current operation has
7803 been aborted.
7804
7805 Action: Contact the system programming staff.
7806
7807
7808
7809 as_mcs_mpx_.pl1
7810 as_mcs_mpx_: Tracing off.
7811
7812
7813 Stream: $as1
7814
7815 Time: While system is running.
7816
7817 Meaning: The trace_off entry point has been called and now
7818 tracing has been disabled.
7819
7820 Action: Contact the system programming staff.
7821
7822
7823
7824
7825
7826
7827
7828
7829
7830
7831 as_mcs_mpx_ -135- MR12.5 10/27/92^L
7832
7833
7834 as_mcs_mpx_.pl1
7835 as_mcs_mpx_: Tracing on.
7836
7837
7838 Stream: $as1
7839
7840 Time: While system is running.
7841
7842 Meaning: The trace_on entry point has been called so that
7843 as_mcs_mpx_ trace data will now be displayed.
7844
7845 Action: Contact the system programming staff.
7846
7847
7848
7849 as_mcs_mpx_.pl1
7850 as_mcs_mpx_: Unexpected wakeup EV_MSG_WORD_1
7851 EV_MSG_WORD_2 from process PROC_ID.
7852
7853
7854 Stream: $as1
7855
7856 Time: While system is running.
7857
7858 Meaning: An unexpected wakeup occured on an FNP bootload
7859 event channel from process PROC_ID. The event
7860 message data is in EV_MSG_WORD_1 and
7861 EV_MSG_WORD_2. Unable to determine FNP tag.
7862
7863 Action: Contact the system programming staff.
7864
7865
7866
7867 as_mcs_mpx_.pl1
7868 as_mcs_mpx_: Wakeup for FNP TAG has invalid state
7869 code: CODE.
7870
7871
7872 Stream: $as1
7873
7874 Time: While system is running.
7875
7876 Meaning: Wakeup message data received on bootload event
7877 channel for FNP TAG contains an invalid state code
7878 value of CODE. Valid values for mpxe.state are
7879 defined in the cdt.incl.pl1 include file by the
7880 FNP_* variables.
7881
7882 Action: Contact the system programming staff.
7883
7884
7885
7886
7887
7888
7889 as_mcs_mpx_ -136- MR12.5 10/27/92^L
7890
7891
7892 as_mcs_mpx_.pl1
7893 as_mcs_mpx_: Wakeup with bad data pointer
7894 ignored: POINTER
7895
7896
7897 Stream: $as1
7898
7899 Time: While system is running.
7900
7901 Meaning: A wakeup was received on an FNP bootload event
7902 channel with which a bad data pointer was
7903 supplied. Unable to determine FNP tag.
7904
7905 Action: Contact the system programming staff.
7906
7907
7908
7909 as_meter_.pl1
7910 as_meter_: FDUMP number is NNN
7911
7912
7913 Stream: as severity1
7914
7915 Time: System Intialization.
7916
7917 Meaning: The system is coming up after a crash. There is a
7918 dump created by the bce dump command in the DUMP
7919 partition. Usually system_start_up.ec copies
7920 this dump into the directory >dumps.
7921
7922 Action: Follow site instructions concerning the processing
7923 of online dumps. The normal procedure is to log
7924 in Print_Dump.SysDaemon and request that it
7925 process the dump.
7926
7927
7928
7929 as_meter_.pl1
7930 as_meter_: Problem getting "ITEM". Metering
7931 disabled.
7932
7933
7934 Stream: as severity2
7935
7936 Time: System Intialization.
7937
7938 Meaning: The metering module cannot obtain a pointer to the
7939 ring 0 hardcore data item ITEM used in
7940 calculating system usage. Metering figures are
7941 scrambled but the system should be able to run.
7942
7943 Action: Contact the system programming staff.
7944
7945
7946
7947 as_meter_ -137- MR12.5 10/27/92^L
7948
7949
7950 as_request_bump_user_.pl1
7951 as_request_bump_user_: BUMPING PERS.PROJ.TAG
7952 PROCESSID for requestor REQ_PERS.REQ_PROJ.REQ_TAG.
7953
7954
7955 Stream: as severity 0
7956
7957 Time: While system is running.
7958
7959 Meaning: An answering service request from
7960 REQ_PERS.REQ_PROJ.REQ_TAG to bump the process
7961 PERS.PROJ.TAG PROCESSID has been initiated.
7962
7963 Action: No operator action is required.
7964
7965
7966
7967 as_request_bump_user_.pl1
7968 as_request_bump_user_: ERROR_MSG. Rejected
7969 BUMP_USER request from PERS.PROJ.TAG to bump
7970 process PROCESS_ID. REASON
7971
7972
7973 Stream: as severity 0
7974
7975 Time: While system is running.
7976
7977 Meaning: The answering service request from PERS.PROJ.TAG
7978 to bump the process identified by PROCESSID failed
7979 for the given REASON and ERROR_MSG.
7980
7981 Action: Contact the system administrator.
7982
7983
7984
7985 as_request_note_pnt_change_.pl1
7986 as_request_note_pnt_change_: Bumping user
7987 PERS.PROJ.TAG PROCESSID on channel CHN. REASON
7988
7989 Stream: as severity 0
7990
7991 Time: While system is running.
7992
7993 Meaning: Process PERS.PROJ.TAG on channel CHN was bumped by
7994 a change to the PNT entry for PERS. REASON
7995 describes the type of PNT change.
7996
7997 Action: No operator action is required.
7998
7999
8000
8001
8002
8003
8004
8005 as_request_note_pnt_change -138- MR12.5 10/27/92^L
8006
8007
8008 as_request_note_pnt_change_.pl1
8009 as_request_note_pnt_change_: ERROR_MSG. Rejected
8010 NOTE_PNT_CHANGE request from PERS.PROJ. REASON
8011
8012 Stream: as severity 0
8013
8014 Time: While system is running.
8015
8016 Meaning: An answering service request to note a change to
8017 the PNT sent by PERS.PROJ failed because of
8018 REASON. This indicates a logic error in the
8019 supervisor or CPU or memory hardware problems.
8020
8021 Action: Contact the system programming staff.
8022
8023
8024
8025
8026
8027
8028 as_request_note_pnt_change_.pl1
8029 as_request_note_pnt_change_: Lowered maximum
8030 authorization for PERS.PROJ.TAG on channel CHN
8031 from OLD_MAX_AUTH to NEW_MAX_AUTH. PNT change.
8032
8033 Stream: as severity 0
8034
8035 Time: While system is running.
8036
8037 Meaning: A change to the PNT entry for PERS lowered the
8038 maximum authorization associated with the process
8039 PERS.PROJ.TAG on channel CHN. The authorization
8040 was changed from OLD_MAX_AUTH to NEW_MAX_AUTH.
8041
8042 Action: No operator action is required.
8043
8044
8045
8046
8047
8048
8049
8050
8051
8052
8053
8054
8055
8056
8057
8058
8059
8060
8061
8062
8063 as_request_note_pnt_change -139- MR12.5 10/27/92^L
8064
8065
8066 as_request_note_pnt_change_.pl1
8067 as_request_note_pnt_change_: Raised minimum
8068 authorization for PERS.PROJ.TAG on channel CHN
8069 from OLD_MIN_AUTH to NEW_MIN_AUTH. PNT change.
8070
8071 Stream: as severity 0
8072
8073 Time: While system is running.
8074
8075 Meaning: A change to the PNT entry for PERS raised the
8076 minimum authorization associated with the process
8077 PERS.PROJ.TAG on channel CHN. The authorization
8078 was changed from OLD_MIN_AUTH to NEW_MIN_AUTH.
8079
8080 Action: No operator action is required.
8081
8082
8083
8084
8085
8086
8087 as_request_note_pnt_change_.pl1
8088 as_request_note_pnt_change_: User has "nobump"
8089 attribute. Did not bump PERS.PROJ.TAG PROCESSID
8090 on channel CHN. REASON
8091
8092 Stream: as severity 0
8093
8094 Time: While system is running.
8095
8096 Meaning: Bump attempt for process PERS.PROJ.TAG with
8097 PROCESSID on channel CHN failed because the user
8098 has the nobump attribute. REASON indicates why
8099 bumping was attempted.
8100
8101 Action: Contact the system administrator.
8102
8103
8104
8105
8106
8107
8108
8109
8110
8111
8112
8113
8114
8115
8116
8117
8118
8119
8120
8121 as_request_note_pnt_change -140- MR12.5 10/27/92^L
8122
8123
8124 as_request_server_.pl1
8125 as_request_sender_: MSG. Could not delete
8126 message MID for PERS.PROJ.
8127
8128
8129 Stream: as severity0
8130
8131 Time: While system is running.
8132
8133 Meaning: MSG is an error_table_ message MID is a message
8134 ID PERS.PROJ is the group ID of the AS request
8135 sender. The AS request message could not be
8136 deleted after executing the AS request.
8137
8138 Action: No operator action is required.
8139
8140
8141
8142 as_request_server_.pl1
8143 as_request_sender_: PERS.PROJ PID set fatal
8144 process error logout|new_proc.
8145
8146
8147 Stream: as severity0
8148
8149 Time: While system is running.
8150
8151 Meaning: The process group id PERS.PROJ process id PID
8152 has set the AS flag which indicates that fatal
8153 process errors will cause a logout|new_proc.
8154
8155 Action: No operator action is required.
8156
8157
8158
8159 as_request_server_.pl1
8160 as_request_server_$init: MSG. Deleting
8161 >sc1>as_request_.ms.
8162
8163
8164 Stream: as severity1
8165
8166 Time: Answering Service initialization.
8167
8168 Meaning: MSG is an error_table_ message. An error was
8169 encountered while attempting to delete the
8170 as_request message segment prior to re-creating
8171 it. as_request_server_$init continues and
8172 attempts to create the message segment.
8173
8174 Action: No operator action is required.
8175
8176
8177
8178
8179 as_request_server_$init -141- MR12.5 10/27/92^L
8180
8181
8182 as_request_server_.pl1
8183 as_request_server_$init: MSG. Manipulating
8184 >sc1>as_request_.ms or IPC channels.
8185
8186
8187 Stream: as severity1
8188
8189 Time: Answering Service initialization.
8190
8191 Meaning: MSG is an error_table_ message. A programming
8192 error has been encountered.
8193
8194 Action: Contact the system programming staff. After the
8195 problem is corrected repeat the bootload
8196 operation.
8197
8198
8199
8200 as_request_server_.pl1
8201 as_request_server_: ERROR_MESSAGE. Can't find
8202 message from PGID
8203
8204
8205 Stream: as severity0
8206
8207 Time: While system is running.
8208
8209 Meaning: MSG is an error_table_ message and PGID is a
8210 process group id. A process sent a wakeup to the
8211 Answering Service but did not put a message in
8212 as_request.ms.
8213
8214 Action: No operator action is required.
8215
8216
8217
8218 as_request_server_.pl1
8219 as_request_server_: Message for "REQUEST NAME"
8220 type N too short from PERS.PROJ.
8221
8222
8223 Stream: as severity0
8224
8225 Time: While system is running.
8226
8227 Meaning: A request of type N sent by the process group id
8228 specified by PERS.PROJ was in error. The request
8229 is ignored. If the request is shorter than the
8230 standard request header which precedes all
8231 requests then the request type is not present in
8232 the message.
8233
8234 Action: No operator action is required.
8235
8236
8237 as_request_server_ -142- MR12.5 10/27/92^L
8238
8239
8240 as_request_server_.pl1
8241 as_request_server_: MSG. Process no longer
8242 active for request from PERS.PROJ.
8243
8244
8245 Stream: as severity0
8246
8247 Time: While system is running.
8248
8249 Meaning: MSG is an error_table_ message and PERS.PROJ isthe
8250 sender id. A process sent a wakeup to the
8251 Answering Service but then logged out before the
8252 Answering Service handled the wakeup.
8253
8254 Action: No operator action is required.
8255
8256
8257
8258 as_request_server_.pl1
8259 as_request_server_: MSG. Error reading message
8260 from message segment.
8261
8262
8263 Stream: as severity0
8264
8265 Time: While system is running.
8266
8267 Meaning: MSG is an error_table_ message. An error occurred
8268 while reading an AS message from the AS request
8269 queue.
8270
8271 Action: No operator action is required.
8272
8273
8274
8275 as_request_server_.pl1
8276 as_request_server_: Rejected invalid type XX
8277 message from PERS.PROJ PID.
8278
8279
8280 Stream: as severity0
8281
8282 Time: While system is running.
8283
8284 Meaning: An invalid wakeup request has been sent to
8285 as_request_server_. The sending process ID is
8286 PID and the sender name in the message is
8287 PERS.PROJ. The request is a type XX request. No
8288 action was taken.
8289
8290 Action: No operator action is required.
8291
8292
8293
8294
8295 as_request_server_ -143- MR12.5 10/27/92^L
8296
8297
8298 as_request_server_.pl1
8299 as_request_server_: Request message segment not
8300 initialized or shutdown has been typed.
8301
8302
8303 Stream: as severity1
8304
8305 Time: While system is running.
8306
8307 Meaning: A request is being ignored because the AS request
8308 queue has not been initialized or the the operator
8309 has typed the shutdown command.
8310
8311 Action: No operator action is required.
8312
8313
8314
8315 as_x25_mpx_.pl1
8316 as_x25_mpx_: Bad argument to parm PARM should be
8317 THIS or THAT but was VALUE for multiplexer MPX.
8318
8319
8320 Stream: as severity1
8321
8322 Time: In response to an operator load_mpx command or
8323 during system start up.
8324
8325 Meaning: A bad value was specified for parameter PARM in
8326 the additional_info field of the TTF entry for the
8327 multiplexer MPX. The choices are THIS or THAT
8328 but VALUE was specified.
8329
8330 Action: Check the contents of the TTF entry for the
8331 terminal_type associated with the multiplexer for
8332 an improper parameter value. Correct and reload
8333 mpx.
8334
8335
8336
8337
8338
8339
8340
8341
8342
8343
8344
8345
8346
8347
8348
8349
8350
8351
8352
8353 as_x25_mpx_ -144- MR12.5 10/27/92^L
8354
8355
8356 as_x25_mpx_.pl1
8357 as_x25_mpx_: Bad argument to parm PARM. Must
8358 have: LOW <= value <= HIGH but value = VALUE
8359 for multiplexer MPX.
8360
8361
8362 Stream: as severity1
8363
8364 Time: In response to an operator load_mpx command or
8365 during system start up.
8366
8367 Meaning: A bad value was specified for parameter PARM in
8368 the additional_info field of the TTF entry for the
8369 multiplexer MPX. The value must be between LOW
8370 and HIGH but VALUE was specified.
8371
8372 Action: Check the contents of the TTF entry for the
8373 terminal_type associated with the multiplexer for
8374 an improper parameter value. Correct and reload
8375 mpx.
8376
8377
8378
8379 as_x25_mpx_.pl1
8380 as_x25_mpx_: Crash signalled for multiplexer MPX.
8381
8382
8383 Stream: as severity1
8384
8385 Time: While system is running.
8386
8387 Meaning: The multiplexer has crashed. The LAP link has
8388 entered the disconnected state.
8389
8390 Action: Contact the system programming staff.
8391
8392
8393
8394
8395
8396
8397
8398
8399
8400
8401
8402
8403
8404
8405
8406
8407
8408
8409
8410
8411 as_x25_mpx_ -145- MR12.5 10/27/92^L
8412
8413
8414 as_x25_mpx_.pl1
8415 as_x25_mpx_: Error in conversion. Converting
8416 FIELD VALUE to a number for multiplexer MPX.
8417
8418
8419 Stream: as severity1
8420
8421 Time: In response to an operator load_mpx command or
8422 during system start up.
8423
8424 Meaning: It was impossible to convert a numeric parameter
8425 from the terminal_type additional_info string to
8426 its internal form. FIELD is the name of the
8427 parameter in error. VALUE is the string which
8428 could not be converted.
8429
8430 Action: Check the contents of the TTF entry for the
8431 terminal_type associated with the multiplexer for
8432 errors.
8433
8434
8435
8436 as_x25_mpx_.pl1
8437 as_x25_mpx_: ERROR. Cannot get additional info
8438 for terminal type TTP for multiplexer MPX.
8439
8440
8441 Stream: as severity1
8442
8443 Time: In response to an operator load_mpx command or
8444 during system start up.
8445
8446 Meaning: An error occurred while retrieving the parameters
8447 of the multiplexer from the TTT. Either the
8448 terminal type specified in the CDT does not exist
8449 or it does not contain the required
8450 additional_info field.
8451
8452 Action: Check that the CMF and TTF contain the proper
8453 information.
8454
8455
8456
8457
8458
8459
8460
8461
8462
8463
8464
8465
8466
8467
8468
8469 as_x25_mpx_ -146- MR12.5 10/27/92^L
8470
8471
8472 as_x25_mpx_.pl1
8473 as_x25_mpx_: ERROR. Creating event channel for
8474 multiplexer MPX.
8475
8476
8477 Stream: as severity1
8478
8479 Time: In response to an operator load_mpx command or
8480 during system start up.
8481
8482 Meaning: An ipc_ error occurred while trying to initialize
8483 the multiplexer.
8484
8485 Action: Contact the system programming staff.
8486
8487
8488
8489 as_x25_mpx_.pl1
8490 as_x25_mpx_: Load failed for multiplexer MPX.
8491
8492
8493 Stream: as severity1
8494
8495 Time: In response to an operator load_mpx command or
8496 during system start up.
8497
8498 Meaning: The attempt to load the multiplexer failed. This
8499 should never happen.
8500
8501 Action: Contact the system programming staff.
8502
8503
8504
8505 as_x25_mpx_.pl1
8506 as_x25_mpx_: Load signalled for multiplexer MPX.
8507
8508
8509 Stream: as severity1
8510
8511 Time: In response to an operator load_mpx command or
8512 during system start up.
8513
8514 Meaning: The multiplexer has been successfully loaded. It
8515 will be started unless the -no_start control
8516 argument was given when the load_mpx command was
8517 typed.
8518
8519 Action: No operator action is required.
8520
8521
8522
8523
8524
8525
8526
8527 as_x25_mpx_ -147- MR12.5 10/27/92^L
8528
8529
8530 as_x25_mpx_.pl1
8531 as_x25_mpx_: MPX: n_lc must be specified.
8532
8533
8534 Stream: as severity1
8535
8536 Time: In response to an operator load_mpx command for
8537 during system startup.
8538
8539 Meaning: The TTF entry for the X.25 multiplexer does not
8540 specify the number of logical channels.
8541
8542 Action: Correct the TTF and reload the multiplexer.
8543
8544
8545
8546 as_x25_mpx_.pl1
8547 as_x25_mpx_: Unexpected signal NUM in state
8548 STATE.
8549
8550
8551 Stream: as severity1
8552
8553 Time: While system is running.
8554
8555 Meaning: A signal NUM was received unexpectedly in state
8556 STATE. The signal is ignored.
8557
8558 Action: Contact the system programming staff.
8559
8560
8561
8562 as_x25_mpx_.pl1
8563 as_x25_mpx_: Unexpected wakeup DATA from
8564 process PRCID.
8565
8566
8567 Stream: as severity1
8568
8569 Time: While system is running.
8570
8571 Meaning: The multiplexer manager received a wakeup from an
8572 unexpected source. The wakeup is ignored.
8573
8574 Action: No operator action is required.
8575
8576
8577
8578
8579
8580
8581
8582
8583
8584
8585 as_x25_mpx_ -148- MR12.5 10/27/92^L
8586
8587
8588 as_x25_mpx_.pl1
8589 as_x25_mpx_: Wakeup for multiplexer MPX has
8590 invalid state code STATE.
8591
8592
8593 Stream: as severity1
8594
8595 Time: While system is running.
8596
8597 Meaning: A wakeup with invalid data was received by the
8598 multiplexer manager. The wakeup is ignored.
8599
8600 Action: Contact the system programming staff.
8601
8602
8603
8604 asr_abs_command_server_.pl1
8605 asr_abs_command_server_: Request REQUEST not
8606 found could not cancel for USER.
8607
8608
8609 Stream: as severity0
8610
8611 Time: While system is running.
8612
8613 Meaning: User USER requested cancellation of absentee job
8614 REQUEST which did
8615 not exist.
8616
8617 Action: No operator action is required.
8618
8619
8620
8621 asr_daemon_command_server_.pl1
8622 asr_daemon_command_server_: Denied
8623 send_daemon_command for USER in ring RING.
8624
8625
8626 Stream: $sc
8627
8628 Time: While system is running.
8629
8630 Meaning: User USER requested the system to execute a daemon
8631 command but lacked access to
8632 >sc1>admin_acs>send_admin_command.acs or the
8633 appropriate daemon source ACS.
8634
8635 Action: No operator action is required.
8636
8637
8638
8639
8640
8641
8642
8643 asr_daemon_command_server_ -149- MR12.5 10/27/92^L
8644
8645
8646 asr_daemon_command_server_.pl1
8647 asr_daemon_command_server_: Failed to check
8648 access for USER.
8649
8650
8651 Stream: $sc
8652
8653 Time: While system is running.
8654
8655 Meaning: User USER requested the system to execute a daemon
8656 command but validate_daemon_commands was not
8657 enabled and the system could not determine their
8658 access to the send_daemon_command acs.
8659
8660 Action: No operator action is required.
8661
8662
8663
8664 asr_daemon_command_server_.pl1
8665 asr_daemon_command_server_: PERSON: COMMAND INFO
8666
8667
8668 Stream: $sc
8669
8670 Time: While system is running.
8671
8672 Meaning: A system administrator has sent a for a daemon to
8673 the Initializer which executes it.
8674
8675 Action: No operator action is required.
8676
8677
8678
8679 astty_.pl1
8680 astty_: ERROR_TABLE_MESSAGE CHANNEL has undefined
8681 terminal type TERM_TYPE for set_term_type order.
8682
8683
8684 Stream: $as0 or $as1
8685
8686 Time: While system is running.
8687
8688 Meaning: The system received the ERROR_TABLE_MESSAGE when
8689 an attempt was made to set the terminal type of
8690 CHANNEL to TERM_TYPE. Suspect the terminal type
8691 is not known on to the system. The set_term_type
8692 control order was ignored.
8693
8694 Action: Contact the system programming staff.
8695
8696
8697
8698
8699
8700
8701 astty_ -150- MR12.5 10/27/92^L
8702
8703
8704 astty_.pl1
8705 astty_: ERROR_TABLE_MESSAGE CHANNEL NN TEXT
8706
8707
8708 Stream: $as0 or $as1
8709
8710 Time: While system is running.
8711
8712 Meaning: This is tracing or error logging output. This
8713 output may appear in the AS log or be printed on
8714 the severity1 stream as directed by astty_ trace
8715 and log_error requests described below.
8716
8717 Action: No operator action is required. Tracing and
8718 logging is controlled by the following entries
8719 which may be typed as commands in admin mode.
8720 astty_$trace - causes tracing of all calls to
8721 astty_
8722 astty_$notrace - disables tracing
8723 astty_$log_error - logs calls to astty_ that get
8724 errors. does not print.
8725 astty_$log_error_1 - logs and prints calls to
8726 astty_ that get errors.
8727 astty_$no_log_error - disables error logging.
8728
8729
8730
8731 astty_.pl1
8732 astty_: ERROR_TABLE_MESSAGE CHANNEL SSSS
8733 line_status failed after line_status_pending
8734
8735
8736 Stream: $as0 or $as1
8737
8738 Time: While system is running.
8739
8740 Meaning: System received the ERROR_TABLE_MESSAGE when it
8741 tried to do a line status control order on CHANNEL
8742 in state SSSS after it received a
8743 line_status_pending error code. The error code
8744 for ERROR_TABLE_MESSAGE was returned back to the
8745 caller.
8746
8747 Action: Contact the system programming staff.
8748
8749
8750
8751
8752
8753
8754
8755
8756
8757
8758
8759 astty_ -151- MR12.5 10/27/92^L
8760
8761
8762 astty_.pl1
8763 astty_: ERROR_TABLE_MESSAGE CHANNEL state SSSS >
8764 TTY_HUNG on hung-up error code.
8765
8766
8767 Stream: $as0 or $as1
8768
8769 Time: While system is running.
8770
8771 Meaning: An error code of ERROR_TABLE_MESSAGE was returned
8772 while servicing CHANNEL indicating that the
8773 channel is not useable. However the state SSSS
8774 of the channel indicates that the channel was
8775 active thus the CHANNEL state is inconsistant.
8776 The channel will be hungup.
8777
8778 Action: Contact the system programming staff.
8779
8780
8781
8782 astty_.pl1
8783 astty_: ERROR_TABLE_MESSAGE error attaching IOCB
8784 for channel CCCC.
8785
8786
8787 Stream: $as0 or $as1
8788
8789 Time: While system is running.
8790
8791 Meaning: The system received the ERROR_TABLE_MESSAGE
8792 attempting to attach to channel CCCC using an
8793 IOCB. The channel was then hungup.
8794
8795 Action: Contact the system programming staff.
8796
8797
8798
8799 astty_.pl1
8800 astty_: ERROR_TABLE_MESSAGE error finding an IOCB
8801 for channel CCCC.
8802
8803
8804 Stream: $as0 or $as1
8805
8806 Time: While system is running.
8807
8808 Meaning: The system received the ERROR_TABLE_MESSAGE when
8809 it attempted to find an IOCB for channel CCCC.
8810 The channel was then hungup.
8811
8812 Action: Contact the system programming staff.
8813
8814
8815
8816
8817 astty_ -152- MR12.5 10/27/92^L
8818
8819
8820 astty_.pl1
8821 astty_: ERROR_TABLE_MESSAGE error opening IOCB
8822 for channel CCCC.
8823
8824
8825 Stream: $as0 or $as1
8826
8827 Time: While system is running.
8828
8829 Meaning: The system received the ERROR_TALE_MESSAGE
8830 attemping to open the channel CCCC using an IOCB.
8831 The channel was then hungup.
8832
8833 Action: Contact the system programming staff.
8834
8835
8836
8837 astty_.pl1
8838 astty_: tty_state returned SSSS for hung-up line
8839 CHANNEL.
8840
8841
8842 Stream: $as0 or $as1
8843
8844 Time: While system is running.
8845
8846 Meaning: In processing the astty_$tty_state entry a call
8847 to hcs_$tty_state returned a state value of SSSS
8848 for hung-up CHANNEL which indicates that the
8849 channel is active. However the returned error
8850 code indicated that the channel is hung-up. The
8851 channel will be hungup.
8852
8853 Action: Contact the system programming staff.
8854
8855
8856
8857 asu_.pl1
8858 asu_$release_ate: bad cdte.process LOCATION for
8859 CHANNEL
8860
8861
8862 Stream: $as0
8863
8864 Time: While system is running.
8865
8866 Meaning: $err When asked to release a User Table Entry
8867 UTE for an interactive process the cdte.process
8868 pointer LOCATION did not point into the answer
8869 table. The UTE was not released.
8870
8871 Action: No operator action is required.
8872
8873
8874
8875 asu_$release_ate -153- MR12.5 10/27/92^L
8876
8877
8878 asu_.pl1
8879 asu_$release_suspended_process: PERSON.PROJECT
8880 CHANNEL is not suspended
8881
8882
8883 Stream: $as0
8884
8885 Time: Called in response to an operator "abs release"
8886 command or in response to a user reconnecting to
8887 an interactive process.
8888
8889 Meaning: One of the process termination handlers is
8890 incorrectly calling to release a process which is
8891 not currently suspended.
8892
8893 Action: No operator action is required.
8894
8895
8896
8897 asu_.pl1
8898 asu_$remote_cdte: ERROR_MESSAGE. cdte CCC|XXX
8899 error from tty_state
8900
8901
8902 Stream: as severity0
8903
8904 Time: While system is running.
8905
8906 Meaning: Remove_cdte is trying to get rid of a channel. It
8907 cannot obtain the line state.
8908
8909 Action: No operator action is required.
8910
8911
8912
8913 asu_.pl1
8914 asu_$suspend_process: PERSON.PROJECT CHANNEL is
8915 already suspended
8916
8917
8918 Stream: $as1
8919
8920 Time: asu_$suspend_process was called by one
8921 of the process termination handlers to suspend an
8922 interactive process whose terminal disconnected
8923 or to suspend an absentee process via the operator
8924 "abs suspend" command.
8925
8926 Meaning: The process is already suspended. The current
8927 request will be ignored.
8928
8929 Action: No operator action is required.
8930
8931
8932
8933 asu_$suspend_process -154- MR12.5 10/27/92^L
8934
8935
8936 asu_.pl1
8937 asu_: attach channel not done on CHANNEL; service
8938 type = TYPE
8939
8940
8941 Stream: $as0
8942
8943 Time: When attaching channels to the Answering Service.
8944
8945 Meaning: The CHANNEL was found in an inactive state TYPE =
8946 INACTIVE or was found to be a multiplexer
8947 channel TYPE = MULTIPLEXER. It was not
8948 attached. This indicates a logic error in the
8949 supervisor or CPU or memory hardware problems.
8950
8951 Action: No operator action is required.
8952
8953
8954
8955 asu_.pl1
8956 asu_: listen not done on CHANNEL; current service
8957 type = TYPE
8958
8959
8960 Stream: $as0
8961
8962 Time: When the Answering Service tried to listen to the
8963 channel.
8964
8965 Meaning: The CHANNEL was found in an inactive state TYPE =
8966 INACTIVE was found to be a multiplexer channel
8967 TYPE = MULTIPLEXER was found to be in use by
8968 the message coordinator TYPE = MC or was found
8969 to be attached for Testing and Diagnostics TYPE =
8970 TANDD_SERVICE. The attempt to listen on the
8971 channel failed. This indicates a logic error in
8972 the supervisor or CPU or memory hardware
8973 problems.
8974
8975 Action: No operator action is required.
8976
8977
8978
8979
8980
8981
8982
8983
8984
8985
8986
8987
8988
8989
8990
8991 asu_ -155- MR12.5 10/27/92^L
8992
8993
8994 asu_.pl1
8995 asu_: called by PROCEDURE USER PROJ CHN is not
8996 stopped state = S even though destroy flag = D;
8997 it might not be possible to destroy this process
8998
8999
9000 Stream: as severity1
9001
9002 Time: In response to an operator command to bump or log
9003 out an interactive absentee or daemon user.
9004
9005 Meaning: The process being bumped or logged out was found
9006 to be partially logged out already but not in the
9007 stopped state. An attempt will be made to destroy
9008 this process but it might fail.
9009
9010 Action: Contact the system programming staff.
9011
9012
9013
9014 asu_.pl1
9015 asu_: called by PROCEDURE USER.PROJ CHN was
9016 already stopped and will be destroyed stopstop
9017 wakeup was lost
9018
9019
9020 Stream: as severity1
9021
9022 Time: In response to an operator command to bump or log
9023 out an interactive absentee or daemon user.
9024
9025 Meaning: The process being bumped or logged out was found
9026 to be in the stopped state partially logged out.
9027 A wakeup from ring zero indicating that the
9028 process was stopped and could be destroyed was
9029 apparently lost. Destruction of the process will
9030 be completed.
9031
9032 Action: Contact the system programming staff.
9033
9034
9035
9036
9037
9038
9039
9040
9041
9042
9043
9044
9045
9046
9047
9048
9049 asu_ -156- MR12.5 10/27/92^L
9050
9051
9052 asu_.pl1
9053 asu_: cdte CCC|XXX CHANNEL hung up
9054
9055
9056 Stream: as severity0
9057
9058 Time: While system is running.
9059
9060 Meaning: Remove_cdte is trying to get rid of a channel.
9061 The indicated CHANNEL is in the hung up state.
9062
9063 Action: No operator action is required.
9064
9065
9066
9067 asu_.pl1
9068 asu_: cdte CCC|XXX CHANNEL state A in use B tra
9069 vec C
9070
9071
9072 Stream: as severity0
9073
9074 Time: While system is running.
9075
9076 Meaning: Remove_cdte is trying to get rid of a channel. It
9077 first logs the state of the line.
9078
9079 Action: No operator action is required.
9080
9081
9082
9083 asu_.pl1
9084 asu_: cdtep CCC|ZZZ not cdt YYY|0
9085
9086
9087 Stream: as severity0
9088
9089 Time: While system is running.
9090
9091 Meaning: This indicates a logic error in the supervisor or
9092 CPU or memory hardware problems. Remove_cdte is
9093 trying to get rid of a channel which is no good.
9094
9095 Action: No operator action is required.
9096
9097
9098
9099
9100
9101
9102
9103
9104
9105
9106
9107 asu_ -157- MR12.5 10/27/92^L
9108
9109
9110 asu_.pl1
9111 asu_: CHANNEL cannot be attached because its
9112 service type is TYPE N.
9113
9114
9115 Stream: as severity1
9116
9117 Time: While system is running.
9118
9119 Meaning: An attach command specified a CHANNEL whose
9120 service type does not permit it to be attached.
9121 No action was taken.
9122
9123 Action: Enter a correct command.
9124
9125
9126
9127 asu_.pl1
9128 asu_: CHANNEL has been deleted by a CDT
9129 installation and so cannot be attached.
9130
9131
9132 Stream: as severity1
9133
9134 Time: While system is running.
9135
9136 Meaning: An attach command specified a CHANNEL that has
9137 been deleted. No action was taken.
9138
9139 Action: Enter a correct command.
9140
9141
9142
9143 asu_.pl1
9144 asu_: CHANNEL has in_use = N current state = S
9145 CDTE.state was OS
9146
9147
9148 Stream: $as1
9149
9150 Time: When the operator attempts to attach the channel.
9151
9152 Meaning: The Channel Definition Table CDT entry for
9153 CHANNEL is in an inconsistent state. See
9154 dialup_values.incl.pl1 for a description of the
9155 in_use and state values. The old state value OS
9156 is displayed only if it differs from the current
9157 state.
9158
9159 Action: Enter a corrected command line.
9160
9161
9162
9163
9164
9165 asu_ -158- MR12.5 10/27/92^L
9166
9167
9168 asu_.pl1
9169 asu_: CHANNEL in use as a multiplexer and cannot
9170 be attached.
9171
9172
9173 Stream: $as0
9174
9175 Time: When issuing an operator attach command for a
9176 channel.
9177
9178 Meaning: CHANNEL is operating as a multiplexer supporting
9179 one or more channels. It cannot be attached
9180 directly. The attach operation fails.
9181
9182 Action: Enter a corrected command line.
9183
9184
9185
9186 asu_.pl1
9187 asu_: CHANNEL in use for T & D and cannot be
9188 attached.
9189
9190
9191 Stream: as severity1
9192
9193 Time: While system is running.
9194
9195 Meaning: An operator attach command specified a CHANNEL
9196 being tested via Test and Diagnostic routines.
9197 The channel was not attached.
9198
9199 Action: Enter a corrected command line.
9200
9201
9202
9203
9204
9205
9206
9207
9208
9209
9210
9211
9212
9213
9214
9215
9216
9217
9218
9219
9220
9221
9222
9223 asu_ -159- MR12.5 10/27/92^L
9224
9225
9226 asu_.pl1
9227 asu_: CHANNEL is a multiplexer and cannot be
9228 removed.
9229
9230
9231 Stream: $as1
9232
9233 Time: When the operator attempts to remove a channel.
9234
9235 Meaning: CHANNEL is a multiplexer channel which handles
9236 data for one or more subchannels. Such
9237 multiplexers are not attached by the Answering
9238 Service and therefore cannot be removed.
9239
9240 Action: Enter a corrected command line.
9241
9242
9243 Message: asu_$bump_user: ERROR_MESSAGE.
9244 BLAST_MESSAGE. Sending blast message to
9245 PERSON.PROJECT on CHANNEL
9246
9247 Stream: $as0
9248
9249 Time: While system is running.
9250
9251 Meaning: An error occurred while attempting to send an
9252 operator warning message to PERSON.PROJECT on
9253 CHANNEL. ERROR_MESSAGE is the text associated
9254 with the error which occurred. BLAST_MESSAGE is
9255 the undelivered operator warning.
9256
9257 Action: No operator action is required.
9258
9259
9260
9261 asu_.pl1
9262 asu_: CHANNEL is already attached; will try to
9263 listen to it again
9264
9265
9266 Stream: $as1
9267
9268 Time: When the operator attempts to attach a channel.
9269
9270 Meaning: The CHANNEL was already attached by the Answering
9271 Service but was not dialed up. The Answering
9272 Service will attempt to listen for dialups on the
9273 channel.
9274
9275 Action: Enter a corrected command line.
9276
9277
9278
9279
9280
9281 asu_ -160- MR12.5 10/27/92^L
9282
9283
9284 asu_.pl1
9285 asu_: CHANNEL is in use by the message
9286 coordinator and cannot be attached.
9287
9288
9289 Stream: as severity1
9290
9291 Time: While system is running.
9292
9293 Meaning: An operator attach command specified a message
9294 coordinator CHANNEL. The channel was not
9295 attached.
9296
9297 Action: Enter a correct command.
9298
9299
9300
9301 asu_.pl1
9302 asu_: CHANNEL is not in CDT and so cannot be
9303 attached
9304
9305
9306 Stream: as severity1
9307
9308 Time: While system is running.
9309
9310 Meaning: An attach command specified an unknown CHANNEL.
9311 No action was taken.
9312
9313 Action: Enter a correct command.
9314
9315
9316
9317 asu_.pl1
9318 asu_: CHANNEL was not configured at bootload
9319 time and so cannot be attached.
9320
9321
9322 Stream: as severity1
9323
9324 Time: While system is running.
9325
9326 Meaning: An attach command specified a CHANNEL that cannot
9327 be used until the next bootload. No action was
9328 taken.
9329
9330 Action: Enter a correct command.
9331
9332
9333
9334
9335
9336
9337
9338
9339 asu_ -161- MR12.5 10/27/92^L
9340
9341
9342 asu_.pl1
9343 asu_: ENTRYPOINT called with null UTE ptr.
9344
9345
9346 Stream: as severity0
9347
9348 Time: ENTRYPOINT may be suspend_process or
9349 setup_login_server_handle. suspend_process was
9350 called by one of the process termination handlers
9351 to suspend an interactive process whose terminal
9352 disconnected or to suspend an absentee process
9353 via the operator "abs suspend" command.
9354 setup_login_server_handler was called in response
9355 to a validate connect new_proc or destroy
9356 request from a login server.
9357
9358 Meaning: Programming error in the process termination
9359 handlers or the login server support of the
9360 Answering Service.
9361
9362 Action: Contact the system programming staff.
9363
9364
9365
9366 asu_.pl1
9367 asu_: ERROR_MESSAGE. ENTRY OPERATION error; will
9368 remove channel CHANNEL DESC
9369
9370
9371 Stream: as severity1
9372
9373 Time: While system is running.
9374
9375 Meaning: A channel error has occurred on CHANNEL. DESC is
9376 the comment field for the channel given in its
9377 Channel Definition Table CDT entry.
9378 ERROR_MESSAGE gives the text describing the error
9379 code returned by the operation in progress.
9380 OPERATION may be create_ev_chn
9381 decl_event_call_chn listen set_term_type
9382 tty_event or tty_index dependent upon the
9383 operation in progress when the error occurred.
9384 ENTRY specifies the asu_ entrypoint that was
9385 running when the operation was performed on the
9386 channel. It may be asu_listen or attach_channel.
9387 The channel will be removed from use.
9388
9389 Action: It may be necessary to busy out the modem for the
9390 channel.
9391
9392
9393
9394
9395
9396
9397 asu_ -162- MR12.5 10/27/92^L
9398
9399
9400 asu_.pl1
9401 asu_: ERROR_MESSAGE. Sending initial wakeup to
9402 PROCESS_ID PERSON.PROJECT
9403
9404
9405 Stream: $as0
9406
9407 Time: Called at process creation to start the process
9408 running.
9409
9410 Meaning: ERROR_MESSAGE is the text of an error
9411 which occurred attempting to send a wakeup to
9412 PERSON.PROJECT. As a result of this error
9413 process creation will fail.
9414
9415 Action: No operator action is required.
9416
9417
9418
9419 asu_.pl1
9420 asu_: ERROR_MESSAGE. Retrieving the values of
9421 R-0ffset and R-Factor for PROCESS_ID
9422 PERSON.PROJECT.
9423
9424
9425 Stream: $as0
9426
9427 Time: Called at process creation.
9428
9429 Meaning: asu_$start_process called hphcs_$get_ipc_operands.
9430 This call failed with an error whose text is shown
9431 as ERROR_MESSAGE. As a result the process will
9432 not be started.
9433
9434 Action: No operator action is required.
9435
9436
9437
9438 asu_.pl1
9439 asu_: listen failed on CHANNEL: state = N
9440
9441
9442 Stream: $as0
9443
9444 Time: When attempting to listen for dialups on the
9445 channel.
9446
9447 Meaning: The Channel Definition Table CDT entry for
9448 CHANNEL has an invalid state value N. Channel
9449 listening will not occur.
9450
9451 Action: No operator action is required.
9452
9453
9454
9455 asu_ -163- MR12.5 10/27/92^L
9456
9457
9458 asu_.pl1
9459 asu_: listen not done on CHANNEL: IN_USE with
9460 state = STATE in_use = IN_USE tra_vec =
9461 CURRENT_OPERATION
9462
9463
9464 Stream: $as0
9465
9466 Time: When the Answering Service tries to listen to the
9467 channel.
9468
9469 Meaning: The Channel Definition Table CDT entry for
9470 CHANNEL is in an inconsistent state. See
9471 dialup_values.incl.pl1 for a description of the
9472 state in_use and tra_vec values.
9473
9474 Action: No operator action is required.
9475
9476
9477
9478 asu_.pl1
9479 asu_: lock was N ev call mask was M ips mask
9480 was ZZZZZZ
9481
9482
9483 Stream: as severity1
9484
9485 Time: In response to an operator reset command.
9486
9487 Meaning: N is the value of anstbl.lock_value M is the
9488 value of event call masking. ZZZZZZ was the ips
9489 mask. This message verifies that the reset
9490 command was given and what effect it had.
9491
9492 Action: No operator action is required.
9493
9494
9495
9496 asu_.pl1
9497 asu_: MESSAGE. unable to unmask channel CHANNEL.
9498
9499
9500 Stream: as severity1
9501
9502 Time: In response to an operator command to attach a
9503 channel which had been masked by MCS.
9504
9505 Meaning: The CHANNEL could not be unmasked.
9506
9507 Action: Contact the system programming staff.
9508
9509
9510
9511
9512
9513 asu_ -164- MR12.5 10/27/92^L
9514
9515
9516 asu_.pl1
9517 asu_: Unable to create event channel for new UTE
9518 LOCATION
9519
9520
9521 Stream: $as2
9522
9523 Time: While system is running.
9524
9525 Meaning: This indicates a logic error in the supervisor or
9526 CPU or memory hardware problems.
9527
9528 Action: Contact the system programming staff.
9529
9530
9531
9532 asu_.pl1
9533 asu_: unmasking channel CHANNEL.
9534
9535
9536 Stream: as severity1
9537
9538 Time: In response to an operator command to attach a
9539 channel which has been masked by MCS.
9540
9541 Meaning: A special order is issued to MCS to unmask
9542 CHANNEL and the channel should then be available
9543 for regular use.
9544
9545 Action: No operator action is required.
9546
9547
9548
9549 operator_com_channel_cmds_.pl1
9550 attach: Action not performed. ttyXXX
9551
9552
9553 Stream: as severity1.
9554
9555 Time: In response to an operator attach command.
9556
9557 Meaning: This is the response to attach TTYxxx if no more
9558 room is available in the answer table for channel
9559 entries. The line is not attached.
9560
9561 Action: Contact the system programming staff.
9562
9563
9564
9565
9566
9567
9568
9569
9570
9571 attach -165- MR12.5 10/27/92^L
9572
9573
9574 operator_com_channel_cmds_.pl1
9575 attach: bad arg "AAAA"
9576
9577
9578 Stream: as severity1.
9579
9580 Time: In response to an operator command.
9581
9582 Meaning: A bad argument was furnished with an attach
9583 command. The argument is skipped.
9584
9585 Action: Enter a corrected command.
9586
9587
9588
9589 operator_com_channel_cmds_.pl1
9590 attach: error: not done
9591
9592
9593 Stream: as severity1.
9594
9595 Time: In response to an operator command.
9596
9597 Meaning: Bad arguments were given to an attach command. No
9598 action resulted.
9599
9600 Action: Enter a corrected command line.
9601
9602
9603
9604 operator_com_channel_cmds_.pl1
9605 attach: TTYxxx attached
9606
9607
9608 Stream: as severity1.
9609
9610 Time: In response to an operator attach command.
9611
9612 Meaning: This is the response to an attach TTYxxx command.
9613 The device channel is now connected to the
9614 Answering Service and ready for dialups.
9615
9616 Action: No operator action is required.
9617
9618
9619
9620
9621
9622
9623
9624
9625
9626
9627
9628
9629 attach -166- MR12.5 10/27/92^L
9630
9631
9632 terminate_proc.pl1
9633 attempt to terminate an idle process
9634
9635
9636 Stream: BOS Typewriter Crashes system
9637
9638 Time: While system is running.
9639
9640 Meaning: This indicates a logic error in the supervisor or
9641 CPU or memory hardware problems.
9642
9643 Action: Follow normal recovery procedures.
9644
9645
9646
9647 terminate_proc.pl1
9648 attempt to terminate initializer process
9649
9650
9651 Stream: BOS Typewriter Crashes system
9652
9653 Time: While system is running.
9654
9655 Meaning: This indicates a logic error in the supervisor or
9656 CPU or memory hardware problems.
9657
9658 Action: Follow normal recovery procedures.
9659
9660
9661
9662 terminate_proc.pl1
9663 attempt to terminate process with TYPE lock set
9664
9665
9666 Stream: BOS Typewriter Crashes system
9667
9668 Time: While system is running.
9669
9670 Meaning: This indicates a logic error in the supervisor or
9671 CPU or memory hardware problems.
9672
9673 Action: Follow normal recovery procedures.
9674
9675
9676
9677
9678
9679
9680
9681
9682
9683
9684
9685
9686
9687 attempt to terminate proce -167- MR12.5 10/27/92^L
9688
9689
9690 access_audit_util_.pl1
9691 AUDIT access_audit_util_: GRANTED modification
9692 of process audit flags ADDED_INFO
9693
9694
9695 Stream: $access_audit
9696
9697 Time: While system is running.
9698
9699 Meaning: The specified user has invoked a privileged
9700 operation to change the process audit flags. This
9701 may result in more or less audit messages for that
9702 user.
9703
9704 Action: $notify_ssa
9705
9706
9707
9708 access_class_check.pl1
9709 AUDIT access_class_check: GRANTED modification
9710 of security out_of_service ADDED_INFO
9711
9712
9713 Stream: $access_audit
9714
9715 Time: While system is running.
9716
9717 Meaning: The soos switch for the specified path has been
9718 turned on or off by the security administrator as
9719 indicated.
9720
9721 Action: No operator action is required.
9722
9723
9724
9725 create_vtoce.pl1
9726 AUDIT create_vtoce: DENIED creation of file
9727 system object ADDED_INFO entry class range outside
9728 LV CLASS_RANGE lvid LVID
9729
9730
9731 Stream: $access_audit
9732
9733 Time: While system is running.
9734
9735 Meaning: The specified user attempted to create a segment
9736 whose access class
9737 is outside the range accepted by the
9738 logical volume.
9739
9740 Action: Contact the system security administrator.
9741
9742
9743
9744
9745 AUDIT create_vtoce -168- MR12.5 10/27/92^L
9746
9747
9748 fim.alm
9749 AUDIT fim: access violation fault - mode
9750 ADDED_INFO
9751
9752
9753
9754 Stream: $access_audit
9755
9756 Time: While system is running.
9757
9758 Meaning: The specified process took an access violation
9759 fault " because the access mode was inconsistant
9760 with the operation.
9761
9762 Action: No operator action is required.
9763
9764
9765
9766 fim.alm
9767 AUDIT fim: access violation fault - ring
9768 ADDED_INFO
9769
9770
9771
9772 Stream: $access_audit
9773
9774 Time: While system is running.
9775
9776 Meaning: The specified process took an access violation
9777 fault " due to ring brackets inconsistant with the
9778 operation.
9779
9780 Action: No operator action is required.
9781
9782
9783
9784 fim.alm
9785 AUDIT fim: illegal procedure fault ADDED_INFO
9786
9787
9788
9789 Stream: $access_audit
9790
9791 Time: While system is running.
9792
9793 Meaning: The specified process took an illegal procedure
9794 fault.
9795
9796 Action: No operator action is required.
9797
9798
9799
9800
9801
9802
9803 AUDIT fim -169- MR12.5 10/27/92^L
9804
9805
9806 page_error.alm
9807 AUDIT page_fault: GRANTED excessive segment
9808 state changes Moderate_cc for PROCESS_GROUP_ID
9809 AUTHORIZATION
9810
9811
9812 Time: While system is running.
9813
9814 Stream: $security_log
9815
9816 Meaning: An attempt to use the modification of various
9817 segment " attributes as a covert channel was
9818 detected.
9819
9820
9821
9822 pnt_db_util_.pl1
9823 AUDIT pnt_db_util_: GRANTED addition of pnt
9824 entry Admin_op for PERSON.PROJECT.TAG AUTH
9825 Level=1 to PNT entry USERID no access class.
9826
9827
9828 Stream: $access_audit
9829
9830 Time: While system is running.
9831
9832 Meaning: The user PERSON.PROJECT.TAG added a new PNT
9833 entry for USERID
9834
9835 Action: No operator action is required.
9836
9837
9838
9839 pnt_db_util_.pl1
9840 AUDIT pnt_db_util_: GRANTED deletion of pnt
9841 entry Admin_op for PERSON.PROJECT.TAG AUTH
9842 Level=1 to PNT entry USERID no access class.
9843
9844
9845 Stream: $access_audit
9846
9847 Time: While system is running.
9848
9849 Meaning: The user PERSON.PROJECT.TAG deleted the PNT entry
9850 for USERID.
9851
9852 Action: No operator action is required.
9853
9854
9855
9856
9857
9858
9859
9860
9861 AUDIT pnt_db_util_ -170- MR12.5 10/27/92^L
9862
9863
9864 pnt_db_util_.pl1
9865 AUDIT pnt_db_util_: GRANTED modification of pnt
9866 entry Admin_op for PERSON.PROJECT.TAG AUTH
9867 Level=1 to PNT entry USERID: CHANGES no access
9868 class.
9869
9870
9871 Stream: $access_audit
9872
9873 Time: While system is running.
9874
9875 Meaning: The user PERSON.PROJECT.TAG modified the PNT entry
9876 for USERID. CHANGES describes in brief format
9877 what security relevant changes were made. See the
9878 binary information in the audit message for
9879 further details.
9880
9881 Action: No operator action is required.
9882
9883
9884
9885 reclassify.pl1
9886 AUDIT reclassify$ENTRY: GRANTED modification of
9887 security out-of-service ADDED_INFO
9888
9889
9890 Stream: $access_audit
9891
9892 Time: While system is running.
9893
9894 Meaning: An AIM error was found in respect to the specified
9895 directory. There was a disagreement in access
9896 class between the directory and one of it's sons
9897 or there was an upgraded directory with
9898 non-terminal quota.
9899
9900 Action: No operator action is required.
9901
9902
9903
9904
9905
9906
9907
9908
9909
9910
9911
9912
9913
9914
9915
9916
9917
9918
9919 AUDIT reclassify$ENTRY -171- MR12.5 10/27/92^L
9920
9921
9922 reclassify.pl1
9923 AUDIT reclassify$ENTRY: GRANTED|DENIED
9924 modification of fs_obj access class ADDED_INFO
9925
9926
9927 Stream: $access_audit
9928
9929 Time: While system is running.
9930
9931 Meaning: Indicates whether an attempt to reclassify the
9932 specified file system object was granted or
9933 denied. In the case of reclassify$node a message
9934 will be generated for each entry in the directory
9935 being reclassified.
9936
9937 Action: No operator action is required.
9938
9939
9940
9941 salv_check_vtoce_.pl1
9942 AUDIT salv_check_vtoce_: GRANTED modification
9943 of security out-of-service ADDED_INFO
9944
9945
9946 Stream: $access_audit
9947
9948 Time: While system is running.
9949
9950 Meaning: Security out-of-service switch was set because
9951 vtoce access class did not match the entry access
9952 class for the specified file system entry.
9953
9954 Action: Contact the system security administrator.
9955
9956
9957
9958 salv_dir_checker_.pl1
9959 AUDIT salv_dir_checker_: GRANTED modification
9960 of fs_obj access ADDED_INFO
9961
9962
9963 Stream: $access_audit
9964
9965 Time: Salvaging
9966
9967 Meaning: The salvager has truncated the ACL of a branch.
9968
9969 Action: Contact the system security administrator.
9970
9971
9972
9973
9974
9975
9976
9977 AUDIT salv_dir_checker_ -172- MR12.5 10/27/92^L
9978
9979
9980 set_privileges.pl1
9981 AUDIT set_privileges: GRANTED modification of
9982 system AIM privilege ADDED_INFO
9983
9984
9985 Stream: $access_audit
9986
9987 Time: While system is running.
9988
9989 Meaning: The specified user made a privileged call for
9990 modifying the process AIM privileges
9991
9992 Action: No operator action is required.
9993
9994
9995
9996 set_sys_audit_thresholds_.pl1
9997 AUDIT set_sys_audit_thresholds_: GRANTED|DENIED
9998 modification of system audit flags and thresholds
9999 ADDED_INFO
10000
10001
10002 Stream: $access_audit
10003
10004 Time: While system is running.
10005
10006 Meaning: Indicates that the system wide audit enable flags
10007 and the thresholds have been changed as indicated.
10008
10009 Action: No operator action is required.
10010
10011
10012
10013 bce_abs_seg.pl1
10014 bce_abs_seg: Too many bce abs-segs.
10015
10016
10017 Stream: BOS Typewriter Crashes system
10018
10019 Time: System Intialization.
10020
10021 Meaning: More per-bce pass abs-segs were encountered than
10022 fit in the abs-seg array. This is a software
10023 error.
10024
10025
10026
10027
10028
10029
10030
10031
10032
10033
10034
10035 bce_abs_seg -173- MR12.5 10/27/92^L
10036
10037
10038 bce_ioi_post.pl1
10039 bce_ioi_post: Error posting i/o completion.
10040 ioi_event_channel: CCCCCCCCCCCC ioi_message:
10041 MMMMMMMMMMMM
10042
10043
10044 Stream: BOS Typewriter Crashes system
10045
10046 Time: System Intialization.
10047
10048 Meaning: No posting buffer was found in an "I/O
10049 outstanding" state for the above event channel.
10050 This indicates a logic error in the supervisor or
10051 CPU or memory hardware problems.
10052
10053 Action: Contact the system programming staff.
10054
10055
10056
10057 bce_ioi_post.pl1
10058 bce_ioi_post: System not at correct level to post
10059 I/O completion.
10060
10061
10062 Stream: BOS Typewriter Crashes system
10063
10064 Time: System Intialization.
10065
10066 Meaning: The flag sys_info$service_system indicates that
10067 the system is up and should be posting I/O
10068 completions via pxss$io_wakeup not this program.
10069 This indicates a logic error in the supervisor or
10070 CPU or memory hardware problems.
10071
10072 Action: Contact the system programming staff.
10073
10074
10075
10076 bce_ioi_post.pl1
10077 bce_ioi_post: Unexpected System Fault.
10078 ioi_event_channel: CCCCCCCCCCCC ioi_message:
10079 MMMMMMMMMMMM
10080
10081
10082 Stream: BOS Typewriter Crashes system
10083
10084 Time: System Intialization.
10085
10086 Meaning: This indicates a logic error in the supervisor or
10087 CPU or memory hardware problems.
10088
10089 Action: Contact the system programming staff.
10090
10091
10092
10093 bce_ioi_post -174- MR12.5 10/27/92^L
10094
10095
10096 bce_save.pl1
10097 bce_save: Error issuing tape connect for TAPE_DEV
10098 TAPE_SET. ERR_MESSAGE
10099
10100
10101 Stream: BOS Typewriter Crashes system
10102
10103 Time: System Intialization.
10104
10105 Meaning: IOI has returned a non-zero error which has been
10106 expanded in ERR_MESSAGE. This indicates a logic
10107 error in the supervisor or CPU or memory hardware
10108 problems.
10109
10110 Action: Contact the system programming staff.
10111
10112
10113
10114 bce_save.pl1
10115 bce_save: Internal bit map for PV_NAME TAPE_SET
10116 contains no in use pages.
10117
10118
10119 Stream: BOS Typewriter Crashes system
10120
10121 Time: System Intialization.
10122
10123 Meaning: The copied/packed internal version of the PV's
10124 volume bit map contains no used pages OFF bits.
10125 This indicates a logic error in the supervisor or
10126 CPU or memory hardware problems.
10127
10128 Action: Contact the system programming staff.
10129
10130
10131
10132 bce_save.pl1
10133 bce_save: IO complete but NO status returned for
10134 TAPE_SET.
10135
10136
10137 Stream: BOS Typewriter Crashes system
10138
10139 Time: System Intialization.
10140
10141 Meaning: An I/O has been posted but there was no
10142 indication of status being returned. This
10143 indicates a logic error in the supervisor or CPU
10144 or memory hardware problems.
10145
10146 Action: Contact the system programming staff.
10147
10148
10149
10150
10151 bce_save -175- MR12.5 10/27/92^L
10152
10153
10154 bce_save.pl1
10155 bce_save: Out of disk buffers for TAPE_SET.
10156
10157
10158 Stream: BOS Typewriter Crashes system
10159
10160 Time: System Intialization.
10161
10162 Meaning: This indicates a logic error in the supervisor or
10163 CPU or memory hardware problems.
10164
10165 Action: Contact the system programming staff.
10166
10167
10168
10169 bce_save.pl1
10170 bce_save: Out of tape buffers for TAPE_SET.
10171
10172
10173 Stream: BOS Typewriter Crashes system
10174
10175 Time: System Intialization.
10176
10177 Meaning: This indicates a logic error in the supervisor or
10178 CPU or memory hardware problems.
10179
10180 Action: Contact the system programming staff.
10181
10182
10183
10184 bce_save_util_.pl1
10185 bce_save_util_: Out of disk buffers for TAPE_SET.
10186
10187
10188 Stream: BOS Typewriter Crashes system
10189
10190 Time: System Intialization.
10191
10192 Meaning: This indicates a logic error in the supervisor or
10193 CPU or memory hardware problems.
10194
10195 Action: Contact the system programming staff.
10196
10197
10198
10199
10200
10201
10202
10203
10204
10205
10206
10207
10208
10209 bce_save_util_ -176- MR12.5 10/27/92^L
10210
10211
10212 wired_shutdown.pl1
10213 begin emergency shutdown part 1
10214
10215
10216 Stream: BOS Typewriter.
10217
10218 Time: Emergency shutdown
10219
10220 Meaning: The system emergency shutdown environment has been
10221 successfully established. An attempt will be made
10222 to write out all of memory and flush the paging
10223 device.
10224
10225 Action: No operator action is required.
10226
10227
10228
10229 boot_tape_io.pl1
10230 boot_tape_io: Code CODE from absadr.
10231
10232
10233 Stream: BOS Typewriter Crashes system
10234
10235 Time: System Intialization.
10236
10237 Meaning: boot_tape_io was unable to find the address of its
10238 buffer. This indicates a logic error in the
10239 supervisor or CPU or memory hardware problems.
10240
10241 Action: The Multics System Tape may be incorrect. If the
10242 problem persists try another MST.
10243
10244
10245
10246 boot_tape_io.pl1
10247 boot_tape_io: Code CODE from io_manager$assign
10248
10249
10250 Stream: BOS Typewriter Crashes system
10251
10252 Time: System Intialization.
10253
10254 Meaning: The bootload tape reading package could not assign
10255 the bootload tape drive to itself. This indicates
10256 a logic error in the supervisor or CPU or memory
10257 hardware problems.
10258
10259 Action: The Multics System Tape may be incorrect. If the
10260 problem persists try another MST.
10261
10262
10263
10264
10265
10266
10267 boot_tape_io -177- MR12.5 10/27/92^L
10268
10269
10270 boot_tape_io.pl1
10271 boot_tape_io: Unable to allocate buffer.
10272
10273
10274 Stream: BOS Typewriter Crashes system
10275
10276 Time: System Intialization.
10277
10278 Meaning: The bootload tape reading package could not
10279 allocate a wired-down buffer into which to read
10280 the bootload tape. This indicates a logic error
10281 in the supervisor or CPU or memory hardware
10282 problems.
10283
10284 Action: The Multics System Tape may be incorrect. If the
10285 problem persists try another MST.
10286
10287
10288
10289 bootload_error.alm
10290 bootload_0: An unpaged page table overflowed for
10291 seg N.
10292
10293
10294 Stream: BOS Typewriter Crashes system
10295
10296 Time: System Intialization.
10297
10298 Meaning: The size of the page table needed for "unpaged"
10299 segment N exceeded the area left for such page
10300 tables.
10301
10302 Action: The system tape was generated improperly; use
10303 another copy of the system tape.
10304
10305
10306
10307 bootload_error.alm
10308 bootload_0: Bad MST format.
10309
10310
10311 Stream: BOS Typewriter Crashes system
10312
10313 Time: System Intialization.
10314
10315 Meaning: The records on the MST tape were out of sequence.
10316
10317 Action: Try another tape.
10318
10319
10320
10321
10322
10323
10324
10325 bootload_0 -178- MR12.5 10/27/92^L
10326
10327
10328 bootload_error.alm
10329 bootload_0: Booted tape MPC.
10330
10331
10332 Stream: BOS Typewriter.
10333
10334 Time: System Intialization.
10335
10336 Meaning: The system succeeded in booting the bootload tape
10337 mpc.
10338
10339
10340
10341 bootload_error.alm
10342 bootload_0: Booting FWNAME IOM CHAN with FWID
10343 FWREV firmware.
10344
10345
10346 Stream: BOS Typewriter.
10347
10348 Time: System Intialization.
10349
10350 Meaning: The system is about to boot firmware into the
10351 bootload tape mpc.
10352
10353
10354
10355 bootload_error.alm
10356 bootload_0: Booting system SYSID generated
10357 CREATION_TIME
10358
10359
10360 Stream: BOS Typewriter.
10361
10362 Time: System Intialization.
10363
10364 Meaning: This is the first message printed by Multics
10365 announcing the sysid and creation date/time of the
10366 system tape.
10367
10368
10369
10370
10371
10372
10373
10374
10375
10376
10377
10378
10379
10380
10381
10382
10383 bootload_0 -179- MR12.5 10/27/92^L
10384
10385
10386 bootload_error.alm
10387 bootload_0: Console status WORD1 WORD2
10388
10389
10390 Stream: BOS Typewriter Crashes system
10391
10392 Time: System Intialization.
10393
10394 Meaning: An I/O error was encountered on the console.
10395 WORD1 and WORD2 are the two words of the status
10396 returned.
10397
10398 Action: Run T&D on the console.
10399
10400
10401
10402 bootload_error.alm
10403 bootload_0: Enter boot tape MPC model:
10404
10405
10406 Stream: BOS Typewriter.
10407
10408 Time: System Intialization.
10409
10410 Meaning: This query requests the operator to identify the
10411 bootload tape mpc so that firmware may be loaded.
10412 Refer to the MOH for details.
10413
10414
10415
10416 bootload_error.alm
10417 bootload_0: Enter tape drive number for memory
10418 dump:
10419
10420
10421 Stream: BOS Typewriter.
10422
10423 Time: BOS Typewriter Crashes system
10424
10425 Meaning: An initialization failure occured when the toehold
10426 was not active. The system is requesting the
10427 number of a tape drive on the bootload tape mpc on
10428 which to write a dump of memory.
10429
10430
10431
10432
10433
10434
10435
10436
10437
10438
10439
10440
10441 bootload_0 -180- MR12.5 10/27/92^L
10442
10443
10444 bootload_error.alm
10445 bootload_0: Error status WORD1 WORD2 booting
10446 FWTYPE firmware.
10447
10448
10449 Stream: BOS Typewriter.
10450
10451 Time: System Intialization.
10452
10453 Meaning: An error occured when attempting to boot firmware
10454 into the bootload tape mpc. WORD1 and WORD2 are
10455 the status returned.
10456
10457 Action: Try another firmware identifier.
10458
10459
10460
10461 bootload_error.alm
10462 bootload_0: Excessive tape errors: status WORD1
10463 WORD2.
10464
10465
10466 Stream: BOS Typewriter.
10467
10468 Time: BOS Typewriter Crashes system
10469
10470 Meaning: An excessive number of write errors occured when
10471 trying to write an early dump tape. The dump to
10472 this tape will be aborted.
10473
10474 Action: Try another tape.
10475
10476
10477
10478 bootload_error.alm
10479 bootload_0: External symbol not found: SEG$ENTRY
10480
10481
10482 Stream: BOS Typewriter.
10483
10484 Time: System Intialization.
10485
10486 Meaning: The entrypoint ENTRY was not found within the
10487 existant segment SEG during pre-linking of
10488 collection 1. This may indicate that the system
10489 tape was generated improperly.
10490
10491
10492
10493
10494
10495
10496
10497
10498
10499 bootload_0 -181- MR12.5 10/27/92^L
10500
10501
10502 bootload_error.alm
10503 bootload_0: Improper text/link/def sequence.
10504
10505
10506 Stream: BOS Typewriter Crashes system
10507
10508 Time: System Intialization.
10509
10510 Meaning: Text linkage or definitions appeared out of
10511 proper sequence " on the Multics system tape.
10512
10513 Action: The system tape was generated improperly; use
10514 another copy " of the system tape.
10515
10516
10517
10518 bootload_error.alm
10519 bootload_0: Out of main memory.
10520
10521
10522 Stream: BOS Typewriter Crashes system
10523
10524 Time: System Intialization.
10525
10526 Meaning: Not enough main memory is configured in order to
10527 load " collection 1.
10528
10529 Action: Configure more main memory and boot again.
10530
10531
10532
10533 bootload_error.alm
10534 bootload_0: Shutdown
10535
10536
10537 Stream: BOS Typewriter Crashes system
10538
10539 Time: System Intialization.
10540
10541 Meaning: The operator answered "shut" when asked for the
10542 bootload tape mpc information.
10543
10544 Action: $reboot
10545
10546
10547
10548
10549
10550
10551
10552
10553
10554
10555
10556
10557 bootload_0 -182- MR12.5 10/27/92^L
10558
10559
10560 bootload_error.alm
10561 bootload_0: Tape read error: WORD1 WORD2
10562
10563
10564 Stream: BOS Typewriter Crashes system
10565
10566 Time: System Intialization.
10567
10568 Meaning: An I/O error was encountered when reading the MST
10569 tape. WORD1 and WORD2 are the two words of the
10570 status returned.
10571
10572 Action: $reboot
10573
10574
10575
10576 bootload_error.alm
10577 bootload_0: Too many supervisor segments.
10578
10579
10580 Stream: BOS Typewriter Crashes system
10581
10582 Time: System Intialization.
10583
10584 Meaning: More than 256 supervisor segments were declared on
10585 the MST.
10586
10587 Action: The system tape was generated improperly; use
10588 another copy of the system tape.
10589
10590
10591
10592 bootload_error.alm
10593 bootload_0: Unexpected control word on tape
10594 CONTROL_WORD.
10595
10596
10597 Stream: BOS Typewriter Crashes system
10598
10599 Time: System Intialization.
10600
10601 Meaning: An unexpected Multics system tape control word was
10602 encountered.
10603
10604 Action: The system tape was generated improperly; use
10605 another copy of the system tape.
10606
10607
10608
10609
10610
10611
10612
10613
10614
10615 bootload_0 -183- MR12.5 10/27/92^L
10616
10617
10618 bootload_error.alm
10619 bootload_0: Unknown tape MPC model NAME.
10620
10621
10622 Stream: BOS Typewriter.
10623
10624 Time: System Intialization.
10625
10626 Meaning: The operator entered an unrecognizable mpc
10627 identifier.
10628
10629 Action: Try another mpc identifier.
10630
10631
10632
10633 bootload_disk_post.pl1
10634 bootload_disk_post: Attempt to post non-requested
10635 i/o completion.
10636
10637
10638 Stream: BOS Typewriter Crashes system
10639
10640 Time: System Intialization.
10641
10642 Meaning: disk_control detected an i/o completion that
10643 Bootload Multics does not believe it requested.
10644
10645 Action: Reboot.
10646
10647
10648
10649 boundfault.pl1
10650 boundfault: activating into father XXX|YYY
10651
10652
10653 Stream: BOS Typewriter Crashes system
10654
10655 Time: While system is running.
10656
10657 Meaning: While activating a segment the parent directory
10658 for the segment became deactivated. This
10659 indicates a logic error in the supervisor or CPU
10660 or memory hardware problems.
10661
10662 Action: Follow normal recovery procedures.
10663
10664
10665
10666
10667
10668
10669
10670
10671
10672
10673 boundfault -184- MR12.5 10/27/92^L
10674
10675
10676 boundfault.pl1
10677 boundfault: on the root
10678
10679
10680 Stream: BOS Typewriter Terminates user process
10681
10682 Time: While system is running.
10683
10684 Meaning: A boundfault on the root directory has been
10685 encountered. This indicates a logic error in the
10686 supervisor or CPU or memory hardware problems.
10687
10688 Action: Contact the system programming staff.
10689
10690
10691
10692 cache_tester.pl1
10693 cache_tester: cache parity error detected on CPU
10694 <TAG> bit failures at level W column XXX in
10695 cache: YYYYYYYYYYYYYYYYYYYYYYYY in memory:
10696 ZZZZZZZZZZZZZZZZZZZZZZZZ.
10697
10698
10699 Stream: BOS Typewriter.
10700
10701 Time: While system is running.
10702
10703 Meaning: This message is the result of a multiple bit cache
10704 failure detected and cache data and its
10705 corresponding memory data captured by the fim. It
10706 should be noted that when a cache parity error is
10707 detected by the fim there is a window of time
10708 before the address in cache and in main store can
10709 be determined. Although the cache error data is
10710 frozen cache is turned off unconditionaly when
10711 the parity retry of the fim is called the
10712 corresponding address in main store might have
10713 been changed through paging migration from other
10714 processors. This message then might not be a
10715 multiple error but rather the result of this
10716 window condition. If this message was the only
10717 diagnostic displayed i.e. the static test found
10718 no errors the cache will be turned back on. The
10719 values of W XXX YYY...Y and ZZZ...Z are as
10720 explained above.
10721
10722 Action: Contact Field Engineering
10723
10724
10725
10726
10727
10728
10729
10730
10731 cache_tester -185- MR12.5 10/27/92^L
10732
10733
10734 cache_tester.pl1
10735 cache_tester: cache parity error detected on CPU
10736 <TAG> at: board XXXX chip YY.
10737
10738
10739 Stream: BOS Typewriter.
10740
10741 Time: While system is running.
10742
10743 Meaning: This message is the result of a single bit cache
10744 failure detected and cache data and its
10745 corresponding memory data captured by the fim.
10746 This message will be displayed if the diagnostic
10747 error data from the fim is valid. The board and
10748 chip callout are as explained above.
10749
10750 Action: Contact field Engineering.
10751
10752
10753
10754 cache_tester.pl1
10755 cache_tester: cache parity error detected on CPU
10756 <TAG> cache data is equal to the memory data.
10757 parity generation problem for level <L>.
10758
10759
10760 Stream: BOS Typewriter.
10761
10762 Time: While system is running.
10763
10764 Meaning: This message is the result of a cache failure
10765 detected and cache data and its corresponding
10766 memory data captured by the fim. This message
10767 will be displayed if the diagnostic error data
10768 from the fim is valid.
10769
10770 Action: Contact field Engineering.
10771
10772
10773
10774
10775
10776
10777
10778
10779
10780
10781
10782
10783
10784
10785
10786
10787
10788
10789 cache_tester -186- MR12.5 10/27/92^L
10790
10791
10792 cache_tester.pl1
10793 cache_tester: Entire cache memory for CPU <TAG>
10794 has been disabled.
10795
10796
10797 Stream: BOS Typewriter sounds beeper
10798
10799 Time: While system is running.
10800
10801 Meaning: The static test of cache memory for CPU <TAG>
10802 detected repeatable errors in both halfs of cache.
10803 or one half of cache had previously been disabled
10804 and the static test of the other half detected
10805 repeatable errors.
10806
10807 Action: Contact field Engineering
10808
10809
10810
10811 cache_tester.pl1
10812 cache_tester: LLUU cache memory csh<n> for CPU
10813 <TAG> has been turned off OTHER was AA and has not
10814 been changed.
10815
10816
10817 Stream: BOS Typewriter sounds beeper
10818
10819 Time: While system is running.
10820
10821 Meaning: Either the lower half LLUU = Lower <n> = 1 or
10822 the upper half LLUU = Upper <n> = 2 of cache
10823 memory for CPU <TAG> has been turned off as the
10824 result of the static cache test finding a
10825 repeatable cache failure. The OTHER Upper or
10826 Lower was in state AA. If AA is off this half of
10827 cache was not tested. If AA is on this half of
10828 cache had no errors.
10829
10830 Action: Contact Field Engineering
10831
10832
10833
10834
10835
10836
10837
10838
10839
10840
10841
10842
10843
10844
10845
10846
10847 cache_tester -187- MR12.5 10/27/92^L
10848
10849
10850 cache_tester.pl1
10851 cache_tester: No errors found in cache memory for
10852 CPU <TAG> cache will remain on.
10853
10854
10855 Stream: BOS Typewriter.
10856
10857 Time: While system is running.
10858
10859 Meaning: The static test of cache memory for CPU <TAG>
10860 found no errors and no cache error information was
10861 captured by the fim.
10862
10863 Action: cache is turned back on
10864
10865
10866
10867 cache_tester.pl1
10868 cache_tester: repeatable cache parity error
10869 detected on CPU <TAG> cache data is equal to the
10870 memory data. parity generation problem for level
10871 <L>.
10872
10873
10874 Stream: BOS Typewriter.
10875
10876 Time: While system is running.
10877
10878 Meaning: The static test of cache memory for CPU <TAG>
10879 detected a cache failure but the data and its
10880 corresponding memory data are equal.
10881
10882 Action: Contact field Engineering.
10883
10884
10885
10886
10887
10888
10889
10890
10891
10892
10893
10894
10895
10896
10897
10898
10899
10900
10901
10902
10903
10904
10905 cache_tester -188- MR12.5 10/27/92^L
10906
10907
10908 cache_tester.pl1
10909 cache_tester: repeatable cache parity errors
10910 detected on CPU <TAG> bit failures at level W
10911 column XXX in cache: YYYYYYYYYYYYYYYYYYYYYYYY in
10912 memory: ZZZZZZZZZZZZZZZZZZZZZZZZ.
10913
10914
10915 Stream: BOS Typewriter.
10916
10917 Time: While system is running.
10918
10919 Meaning: The static test of cache memory for CPU <TAG>
10920 indicated a multiple bit error between the
10921 contents of cache and the contents of the wired
10922 test buffer. The multiple bit failure is further
10923 broken down to the failing cache level W 0 - 3
10924 and column XXX address. The data read from
10925 cache YYY...Y and the expected data ZZZ...Z is
10926 displayed as an aid for the field engineer. Since
10927 the failure happened during the static test of
10928 cache it is assumed to be a solid failure and
10929 that segment of cache memory csh1 or csh2 is
10930 turned off. There could be up to 3 multiple
10931 messages or some combination of multiple bit error
10932 messages and board and chip callouts since
10933 diagnostic data for the first 3 cache errors is
10934 captured.
10935
10936 Action: Contact Field Engineering personnel.
10937
10938
10939
10940
10941
10942
10943
10944
10945
10946
10947
10948
10949
10950
10951
10952
10953
10954
10955
10956
10957
10958
10959
10960
10961
10962
10963 cache_tester -189- MR12.5 10/27/92^L
10964
10965
10966 cache_tester.pl1
10967 cache_tester: repeatable cache parity errors
10968 detected on CPU <TAG> at: board XXXX chip YY.
10969
10970
10971 Stream: BOS Typewriter.
10972
10973 Time: While system is running.
10974
10975 Meaning: The static test of cache memory for CPU <TAG>
10976 indicated a single bit error between the contents
10977 of cache and the contents of the wired test
10978 buffer. The single bit failure is further broken
10979 down to the failing wire wrapped board board
10980 XXXX and integrated circuit chip chip YY that
10981 failed. Since it happened during the static test
10982 of cache it is assumed to be a solid failure and
10983 that segment of cache memory csh1 or csh2 is
10984 turned off. There could be up to 3 board and chip
10985 callouts since diagnostic data for the first 3
10986 cache errors is captured. These additional board
10987 and chip callouts will only be displayed if the
10988 single bit failure was a different bit or
10989 different cache level than the board and chip
10990 diagnostic already displayed.
10991
10992 Action: Contact Field Engineering personnel.
10993
10994
10995
10996 cache_tester.pl1
10997 cache_tester: Unable to allocate wired buffer.
10998
10999
11000 Stream: BOS Typewriter.
11001
11002 Time: While system is running.
11003
11004 Meaning: Attempted to allocate wired contiguous buffer for
11005 cache testing and pc_contig could not find enough
11006 pages available.
11007
11008 Action: If cache error information was captured in the fim
11009 this information is displayed. Cache memory is
11010 turned back on.
11011
11012
11013
11014
11015
11016
11017
11018
11019
11020
11021 cache_tester -190- MR12.5 10/27/92^L
11022
11023
11024 cache_tester.pl1
11025 cache_tester: Unable to run on CPU <TAG> to EEDD
11026 cache ERRORMESSAGE.
11027
11028
11029 Stream: BOS Typewriter sounds beeper
11030
11031 Time: While system is running.
11032
11033 Meaning: The attempt to run on CPU <TAG> to either enable
11034 EEDD - enable or disable EEDD = disable cache
11035 memory failed.
11036
11037 Action: CPU <TAG> should be taken offline if the attempt
11038 was to disable cache memory.
11039
11040
11041
11042 cache_tester.pl1
11043 cache_tester: Unable to set CPU required to <TAG>
11044 cache is off ERRORMESSAGE.
11045
11046
11047 Stream: BOS Typewriter.
11048
11049 Time: While system is running.
11050
11051 Meaning: Attempted to run on CPU <TAG> for cache testing
11052 and could not set CPU required to that CPU.
11053
11054 Action: Cache memory is turned back on.
11055
11056
11057
11058 call_bce.pl1
11059 call_bce: bce called from Multics.
11060
11061
11062 Stream: BOS Typewriter.
11063
11064 Time: While system is running.
11065
11066 Meaning: An outer ring program has called hphcs_$call_bce.
11067 This is usually done after printing an explanatory
11068 message. The system will resume operation if
11069 continue is typed.
11070
11071 Action: Follow normal recovery procedures.
11072
11073
11074
11075
11076
11077
11078
11079 call_bce -191- MR12.5 10/27/92^L
11080
11081
11082 disk_rebuild_caller.pl1
11083 Cannot shrink VTOC from XX to YY VTOCEs.
11084 Respecify parameters.
11085
11086
11087 Stream: Initializer process output.
11088
11089 Time: In response to an operator command.
11090
11091 Meaning: An attempt has been made to shrink the VTOC which
11092 is illegal.
11093
11094 Action: Respecify the parameters.
11095
11096
11097
11098 mc_tty_.pl1
11099 Channel CHANNEL_NAME attached by Message
11100 Coordinator.
11101
11102
11103 Stream: Initializer terminal.
11104
11105 Time: While system is running.
11106
11107 Meaning: The terminal has been attached by the message
11108 coordinator in
11109 response to an accept or substty command.
11110
11111 Action: Proceed to use the terminal.
11112
11113
11114
11115 channel_manager.pl1
11116 channel_manager: Cleanup while processing
11117 interrupt for devx N.
11118
11119
11120 Stream: BOS Typewriter Crashes system
11121
11122 Time: While system is running.
11123
11124 Meaning: The cleanup condition was signalled while
11125 processing an interrupt for the channel with devx
11126 N.
11127
11128 Action: Contact the system programming staff.
11129
11130
11131
11132
11133
11134
11135
11136
11137 channel_manager -192- MR12.5 10/27/92^L
11138
11139
11140 channel_manager.pl1
11141 channel_manager: Error while processing interrupt
11142 for devx N. REASON
11143
11144
11145 Stream: BOS Typewriter Crashes system
11146
11147 Time: While system is running.
11148
11149 Meaning: An error occurred while processing an interrupt
11150 for the channel with devx N. The specific kind of
11151 error is explained by REASON.
11152
11153
11154
11155 dn355_boot_interrupt.pl1
11156 checksum error in core image for FNP X
11157
11158
11159 Stream: BOS Typewriter.
11160
11161 Time: When bootloading an FNP
11162
11163 Meaning: The core image received for loading in the FNP had
11164 a checksum error.
11165
11166 Action: Try to load the FNP again. If the error recurs
11167 either the DIA hardware is failing or the core
11168 image in the Multics hierarchy is damaged. In the
11169 latter case the core image must be rebound.
11170
11171
11172
11173 system_startup_.pl1
11174 Command:
11175
11176
11177 Stream: BOS Typewriter.
11178
11179 Time: System Intialization.
11180
11181 Meaning: The Initializer types this message whenever it is
11182 waiting for a ring 1 command.
11183
11184 Action: Type the desired command. The normal command to
11185 type when bringing the system up is startup.
11186
11187
11188
11189
11190
11191
11192
11193
11194
11195 Command -193- MR12.5 10/27/92^L
11196
11197
11198 config_.pl1
11199 config_$find_table: TBLS card specifies no value
11200 for NAME.
11201
11202
11203 Stream: BOS Typewriter sounds beeper
11204
11205 Meaning: The config deck does not specify a value for NAME.
11206
11207 Action: One should be added.
11208
11209 Message: config_$ENTRY: the config deck is full.
11210
11211 Stream: BOS Typewriter Crashes system
11212
11213 Meaning: No space remained in the config deck for
11214 additional cards.
11215
11216 Action: If this recurs try another boot tape. Remove
11217 unneccessary config cards.
11218
11219
11220
11221 dn355_boot_interrupt.pl1
11222 configuration error reported by bootloading
11223 program for FNP X
11224
11225
11226 Stream: BOS Typewriter.
11227
11228 Time: When bootloading an FNP
11229
11230 Meaning: The FNP bootload program gicb found an
11231 inconsistency in the FNP configuration.
11232
11233 Action: Contact the system programming staff.
11234
11235
11236
11237
11238
11239
11240
11241
11242
11243
11244
11245
11246
11247
11248
11249
11250
11251
11252
11253 configuration error report -194- MR12.5 10/27/92^L
11254
11255
11256 dn355_boot_interrupt.pl1
11257 configuration error reported by FNP X: DETAILS
11258
11259
11260 Stream: BOS Typewriter.
11261
11262 Time: When bootloading an FNP
11263
11264 Meaning: The FNP initialization program detected an error
11265 or inconsistency in the FNP configuration.
11266 DETAILS is a more specific description of the
11267 error.
11268
11269 Action: If possible correct the error either by updating
11270 the CDT to reflect the actual configuration or
11271 recabling the FNP. If the error cannot be
11272 corrected or is not understood inform the systems
11273 programming staff.
11274
11275
11276
11277 configure_test_cpu.pl1
11278 configure_test_cpu: Unable to run on CPU X
11279 ERRORMESSAGE
11280
11281
11282 Stream: BOS Typewriter Crashes system
11283
11284 Time: When ISOLTS is terminating
11285
11286 Meaning: The system is attempting to restore the ISOLTS CPU
11287 to service. In attempting to reassign its
11288 interrupt mask it was unable to run on that CPU.
11289 This indicates hardware or software malfunction.
11290
11291 Action: Follow normal recovery procedures.
11292
11293
11294
11295 disk_table_.pl1
11296 continuing demount of lv LVNAME
11297
11298
11299 Stream: Initializer process output.
11300
11301 Time: While system is running.
11302
11303 The operator issued a dlv command for a logical
11304 volume for which a previous dlv command failed.
11305
11306 Action: No operator action is required.
11307
11308
11309
11310
11311 continuing demount of lv L -195- MR12.5 10/27/92^L
11312
11313
11314 copy_fdump.pl1
11315 copy_fdump: Copied fdump image of erf NNN
11316 MM/DD/YY HHMM.M for USERNAME
11317
11318
11319 Stream: BOS Typewriter.
11320
11321 Time: While system is running.
11322
11323 Meaning: The user identified by USERNAME has successfully
11324 copied the FDUMP image for the specified ERF out
11325 of the DUMP partition. The time the FDUMP was
11326 taken is also included in the message. This
11327 message is informational only and is intended
11328 only as an aid in tracking system progress by
11329 perusing the syserr log.
11330
11331 Action: No operator action is required.
11332
11333
11334
11335 copy_fdump.pl1
11336 copy_fdump: unexpected NAME signal.
11337
11338
11339 Stream: BOS Typewriter.
11340
11341 Time: While system is running.
11342
11343 Meaning: An attempt to copy the dump from the DUMP
11344 partition with copy_fdump resulted in an unclaimed
11345 signal. This may be due to damage to the DUMP
11346 partition contents a malfunction of the BCE dump
11347 command a supervisor error or a simple
11348 difficulty like running out of space in >dumps.
11349 The system continues operation. The copied dump
11350 may be only partly valid.
11351
11352 Action: Contact the system programming staff.
11353
11354
11355
11356 correct_qused.pl1
11357 correct_qused: hash error
11358
11359
11360 Stream: BOS Typewriter Crashes system
11361
11362 Time: While system is running.
11363
11364 Meaning: Multiple entries within a directory undergoing
11365 quota correction have the same UID.
11366
11367
11368
11369 correct_qused -196- MR12.5 10/27/92^L
11370
11371
11372 cpg_.pl1
11373 cpg_: Error: CONDITION attempting to create
11374 process for NAME.PROJ
11375
11376
11377 Stream: as severity1
11378
11379 Time: While system is running.
11380
11381 Meaning: A supervisor error prevented creation of a process
11382 for the user NAME.PROJ. An Answering Service dump
11383 was performed and the user was logged out if
11384 possible.
11385
11386 Action: Note for system programmer action. If this
11387 message is printed at every login it is probably
11388 wise to shut the system down and perform a
11389 bootload operation.
11390
11391
11392
11393 cpg_.pl1
11394 cpg_: ERROR_MESSAGE. Assigning pdir volume for
11395 USER
11396
11397
11398 Stream: as severity2
11399
11400 Time: While system is running.
11401
11402 Meaning: The system was unable to assign a logical volume
11403 on which to place the process directory of a user.
11404 The user might not be able to log in
11405
11406 Action: Contact the system programming staff.
11407
11408
11409
11410 cpg_.pl1
11411 cpg_: ERROR_MESSAGE. Cannot truncate pit_temp_
11412
11413
11414 Stream: as severity2
11415
11416 Time: While system is running.
11417
11418 Meaning: The system was unable to clear its temporary
11419 segment while attempting to log in a user. The
11420 user will be unable to log in.
11421
11422 Action: Contact the system programming staff.
11423
11424
11425
11426
11427 cpg_ -197- MR12.5 10/27/92^L
11428
11429
11430 tc_init.pl1
11431 CPU CPUTAG: Model #: MODEL; Serial #: SERIAL;
11432 Ship date: YY/MM/DD.
11433
11434
11435 Stream: Logged in SYSERR log.
11436
11437 Time: When the bootload CPU is a DPS8 whose tag is
11438 CPUTAG is "added" to the system.
11439
11440 Meaning: The MODEL SERIAL and YY/MM/DD information is read
11441 from the DPS8 cpu's ID PROM. It is intended to be
11442 used as historical information for identifing
11443 CPUs regardless of what their current tag is
11444 assigned as.
11445
11446 Action: No operator action is required.
11447
11448
11449
11450 obs_reconfigure.pl1
11451 CPU X is now running.
11452
11453
11454 Stream: Initializer process output.
11455
11456 Time: In response to an operator command.
11457
11458 Meaning: This is the response to a successful addcpu X
11459 command.
11460
11461 Action: No operator action is required.
11462
11463
11464
11465 create_homedir_.pl1
11466 create_homedir_: Bad syntax in pathname. DIRNAME
11467 NAME.PROJ
11468
11469
11470 Stream: as severity0.
11471
11472 Time: While system is running.
11473
11474 Meaning: Typically caused by a homedir specification
11475 starting with other than >user_dir_dir or >udd.
11476 It may also occur while attempting to create the
11477 home directory for the user with name NAME and
11478 project PROJ.
11479
11480 Action: $note_sa
11481
11482
11483
11484
11485 create_homedir_ -198- MR12.5 10/27/92^L
11486
11487
11488 create_homedir_.pl1
11489 create_homedir_: creating "DIRNAME" for "USERID"
11490
11491
11492 Stream: as severity0.
11493
11494 Time: While system is running.
11495
11496 Meaning: The user USERID did not have a home directory. It
11497 was created for him during login or when his
11498 project's PDT was installed. This is reasonable
11499 if this is the first time he has logged in.
11500 However his directory may have been destroyed by
11501 the Salvager in which case you have to retrieve
11502 his files.
11503
11504 Action: A retrieval of the user's directory may be
11505 necessary.
11506
11507
11508
11509 create_homedir_.pl1
11510 create_homedir_: ERROR_MESSAGE. DIRNAME
11511 NAME.PROJ
11512
11513
11514 Stream: as severity0.
11515
11516 Time: While system is running.
11517
11518 Meaning: An error occurred while attempting to create the
11519 home directory for the user with name NAME and
11520 project PROJ.
11521
11522 Action: $note_sa
11523
11524
11525
11526 create_root_dir.pl1
11527 create_root_dir: allocating hash table
11528 ERROR_MESSAGE
11529
11530
11531 Stream: BOS Typewriter Crashes system
11532
11533 Time: Cold boot of Multics hierarchy.
11534
11535 Meaning: This indicates a logic error in the supervisor or
11536 CPU or memory hardware problems. An error has
11537 occurred allocating the hash table for the root
11538 directory.
11539
11540 Action: Reboot with a different version of the system.
11541
11542
11543 create_root_dir -199- MR12.5 10/27/92^L
11544
11545
11546 create_root_dir.pl1
11547 create_root_dir: lock error on PPP
11548
11549
11550 Stream: BOS Typewriter Crashes system
11551
11552 Time: System Intialization.
11553
11554 Meaning: The supervisor was unable to lock the root. This
11555 indicates a logic error in the supervisor or CPU
11556 or memory hardware problems.
11557
11558 Action: Follow normal recovery procedures. The Multics
11559 System Tape may be incorrect. If the problem
11560 persists try another MST.
11561
11562
11563
11564 create_root_vtoce.pl1
11565 create_root_vtoce: Cannot alloc-write root vtoce
11566 ERROR_MESSAGE
11567
11568
11569 Stream: BOS Typewriter Crashes system
11570
11571 Time: Cold boot of Multics hierarchy.
11572
11573 Meaning: The system is unable to write out the VTOC entry
11574 for the root directory.
11575
11576 Action: Correct the disk problem if one exists and reboot.
11577 Otherwise reboot with a different version of the
11578 system.
11579
11580
11581
11582
11583
11584
11585
11586
11587
11588
11589
11590
11591
11592
11593
11594
11595
11596
11597
11598
11599
11600
11601 create_root_vtoce -200- MR12.5 10/27/92^L
11602
11603
11604 create_root_vtoce.pl1
11605 create_root_vtoce: Cannot set dmpr bit map for
11606 root ERROR_MESSAGE
11607
11608
11609 Stream: BOS Typewriter.
11610
11611 Time: Cold boot of Multics hierarchy.
11612
11613 Meaning: This indicates a logic error in the supervisor or
11614 CPU or memory hardware problems.
11615
11616 Action: Contact the system programming staff.
11617
11618
11619 Message: create_root_vtoce: Cannot set
11620 root_vtocx in RPV label.
11621
11622 Stream: BOS Typewriter Crashes system
11623
11624 Time: Cold boot of Multics hierarchy.
11625
11626 Meaning: The system is unable to update the RPV label for
11627 the root directory.
11628
11629 Action: Correct the disk problem if one exists and reboot.
11630 Otherwise reboot with a different version of the
11631 system.
11632
11633 Message: create_root_vtoce: Root vtoce not
11634 allocated at 0 RPV not initialized.
11635
11636 Stream: BOS Typewriter Crashes system
11637
11638 Time: Cold boot of Multics hierarchy.
11639
11640 Meaning: A boot -cold was attempted without init_vol for
11641 RPV.
11642
11643 Action: Reboot system answering the find_rpv_subsystem
11644 with cold instead of rpv.
11645
11646
11647
11648
11649
11650
11651
11652
11653
11654
11655
11656
11657
11658
11659 create_root_vtoce -201- MR12.5 10/27/92^L
11660
11661
11662 create_rpv_partition.pl1
11663 create_rpv_partition: Error accessing record NNN.
11664
11665
11666 Stream: BOS Typewriter Crashes system
11667
11668 Time: System Intialization.
11669
11670 Meaning: An i/o error occured when accessing record NNN of
11671 the rpv while attempting to add a new partition.
11672
11673 Action: Try again. IF the error persists the rpv will
11674 need to be rebuilt.
11675
11676
11677
11678 create_rpv_partition.pl1
11679 create_rpv_partition: No room in partition map
11680 for NAME.
11681
11682
11683 Stream: BOS Typewriter Crashes system
11684
11685 Time: System Intialization.
11686
11687 Meaning: The partition map of the rpv was full. The
11688 partition could not be added.
11689
11690 Action: The rpv will need to be rebuilt.
11691
11692
11693
11694 create_rpv_partition.pl1
11695 create_rpv_partition: Out of disk.
11696
11697
11698 Stream: BOS Typewriter Crashes system
11699
11700 Time: System Intialization.
11701
11702 Meaning: Not enough free space existed on the rpv to add
11703 the new partition.
11704
11705 Action: The rlv will have to be rebuilt.
11706
11707
11708
11709
11710
11711
11712
11713
11714
11715
11716
11717 create_rpv_partition -202- MR12.5 10/27/92^L
11718
11719
11720 create_rpv_partition.pl1
11721 create_rpv_partition: Paging region ends past
11722 start of high partitions.
11723
11724
11725 Stream: BOS Typewriter Crashes system
11726
11727 Time: System Intialization.
11728
11729 Meaning: An inconsistency was found in the partition map
11730 when adding a new partition to the rpv.
11731
11732 Action: The rpv will need to be rebuilt.
11733
11734
11735
11736 create_rpv_partition.pl1
11737 create_rpv_partition: Paging region starts below
11738 end of low partitions.
11739
11740
11741 Stream: BOS Typewriter Crashes system
11742
11743 Time: System Intialization.
11744
11745 Meaning: An inconsistency was found in the partition map
11746 when adding a new partition to the rpv.
11747
11748 Action: The rpv will need to be rebuilt.
11749
11750
11751
11752 create_rpv_partition.pl1
11753 create_rpv_partition: vtoce NNN's file map is
11754 damaged. Volume will need salvaging.
11755
11756
11757 Stream: BOS Typewriter Crashes system
11758
11759 Time: System Intialization.
11760
11761 Meaning: The vtoce named was found to be damaged when
11762 adding a new partition to the rpv.
11763
11764 Action: Salvage the rpv using a boot of the previous
11765 release.
11766
11767
11768
11769
11770
11771
11772
11773
11774
11775 create_rpv_partition -203- MR12.5 10/27/92^L
11776
11777
11778 daemon_user_manager_.pl1
11779 daemon_user_manager_: Command sent to
11780 daemon_user_manager_ before it was initialized
11781
11782
11783 Stream: as severity1
11784
11785 Time: In response to an operator command.
11786
11787 Meaning: This message indicates an error in the Answering
11788 Service or an incorrect installation. No daemon
11789 users can log in.
11790
11791 Action: Contact the system programming staff.
11792
11793
11794
11795 daemon_user_manager_.pl1
11796 daemon_user_manager_: Daemon init error. NAME
11797 PROJ SOURCE REASON
11798
11799
11800 Stream: as severity2
11801
11802 Time: In response to an operator command.
11803
11804 Meaning: The daemon user NAME PROJ on SOURCE was logged in
11805 correctly but his process could not be started.
11806 The daemon will be logged out.
11807
11808 Action: Contact the system programming staff.
11809
11810
11811
11812 daemon_user_manager_.pl1
11813 daemon_user_manager_: Daemon will be logged out.
11814
11815
11816 Stream: as severity1
11817
11818 Time: While system is running.
11819
11820 Meaning: An error in a daemon process has caused it to
11821 terminate. The daemon suffered a fatal process
11822 error during initialization or it has set the
11823 option which causes it to be logged out when a
11824 fatal process error occurs.
11825
11826 Action: Attempt to log in the daemon again and proceed.
11827
11828
11829
11830
11831
11832
11833 daemon_user_manager_ -204- MR12.5 10/27/92^L
11834
11835
11836 daemon_user_manager_.pl1
11837 daemon_user_manager_: Error: CONDITION during OP
11838 for NAME.PROJ SOURCE
11839
11840
11841 Stream: as severity2
11842
11843 Time: While system is running.
11844
11845 Meaning: An unexpected fault has occurred while the daemon
11846 user manager was performing an operation of type
11847 OP for the named daemon process. An Answering
11848 Service dump was performed and the system attempts
11849 to continue but the daemon process may be in an
11850 unusable state.
11851
11852 Action: Contact the system programming staff.
11853
11854
11855
11856 daemon_user_manager_.pl1
11857 daemon_user_manager_: ERROR_MESSAGE. Logout not
11858 permitted for message coordinator source SOURCE.
11859
11860
11861 Stream: as severity1
11862
11863 Time: In response to an operator command.
11864
11865 Meaning: The message coordinator access control segment
11866 >system_control_1>mc_acs>SOURCE.mcacs does not
11867 permit the operator to logout the daemon.
11868 Therefore the operator cannot logout the daemon.
11869
11870 Action: Contact the system administrator.
11871
11872
11873
11874
11875
11876
11877
11878
11879
11880
11881
11882
11883
11884
11885
11886
11887
11888
11889
11890
11891 daemon_user_manager_ -205- MR12.5 10/27/92^L
11892
11893
11894 daemon_user_manager_.pl1
11895 daemon_user_manager_: ERROR_MESSAGE. NAME.PROJ
11896 SOURCE terminated.
11897
11898
11899 Stream: as severity1
11900
11901 Time: While system is running.
11902
11903 Meaning: An error in a daemon process has caused it to
11904 terminate. A following message will indicate
11905 whether a new process has been automatically
11906 created.
11907
11908 Action: If the daemon is logged out reinitialize the
11909 daemon and continue. Otherwise a new daemon
11910 process is created automatically and you can
11911 continue from there.
11912
11913
11914
11915 daemon_user_manager_.pl1
11916 daemon_user_manager_: ERROR_MESSAGE. No MC ACS
11917 segment for message coordinator source SOURCE
11918
11919
11920 Stream: as severity1
11921
11922 Time: In response to an operator command.
11923
11924 Meaning: The message coordinator access control segment
11925 >system_control_1>mc_acs>SOURCE.mcacs was not
11926 found. It must be created and given an ACL which
11927 permits the operator to logout the daemon.
11928 Therefore the operator cannot logout the daemon.
11929
11930 Action: Contact the system administrator.
11931
11932
11933
11934 daemon_user_manager_.pl1
11935 daemon_user_manager_: Event entry called with
11936 null ev_msg_ptr
11937
11938
11939 Stream: as severity2
11940
11941 Time: While system is running.
11942
11943 Meaning: This indicates an error in the Answering Service.
11944
11945 Action: Contact the system programming staff.
11946
11947
11948
11949 daemon_user_manager_ -206- MR12.5 10/27/92^L
11950
11951
11952 daemon_user_manager_.pl1
11953 daemon_user_manager_: Fatal process error loop
11954 for NAME.PROJ SOURCE.
11955 Daemon will be logged out.
11956
11957
11958 Stream: as severity1
11959
11960 Time: While system is running.
11961
11962 Meaning: An error in a daemon process has caused it to
11963 terminate repeatedly within the last few minutes.
11964 Detection of the loop causes the daemon to be
11965 logged out.
11966
11967 Action: Try to login the daemon again. If it still fails
11968 notify your System Administrator of the problem.
11969
11970
11971
11972 daemon_user_manager_.pl1
11973 daemon_user_manager_: Invalid signal from NAME
11974 PROJ SOURCE
11975 daemon_user_manager_: signal was "XXXXXXXX"
11976 YYY|ZZZZ
11977
11978
11979 Stream: as severity2
11980
11981 Time: While system is running.
11982
11983 Meaning: This message may result from an error in the
11984 Answering Service an error in one of the daemon
11985 processes or an attempt by an unauthorized user
11986 to signal the daemon user manager. If the NAME
11987 PROJ and SOURCE cannot be determined the process
11988 ID of the sender is shown instead. The DUT
11989 daemon user table entry affected is located at
11990 YYY|ZZZZ in the Answering Service.
11991
11992 The signal is ignored and the Answering Service
11993 attempts to continue. If a daemon user is named
11994 on the first line of the message this user will
11995 probably be unable to continue.
11996
11997 Action: Contact the system programming staff. If the user
11998 named in the message is a daemon user try typing
11999 "logout NAME PROJ SOURCE" and if this succeeds
12000 log the user in again if necessary.
12001
12002
12003
12004
12005
12006
12007 daemon_user_manager_ -207- MR12.5 10/27/92^L
12008
12009
12010 daemon_user_manager_.pl1
12011 daemon_user_manager_: NAME PROJ SOURCE
12012 terminated. Daemon will be logged out.
12013
12014
12015 Stream: as severity2
12016
12017 Time: While system is running.
12018
12019 Meaning: NAME is the Person_id of the daemon PROJ is the
12020 Project_id of the daemon and SOURCE is the
12021 Message Coordinator source id of the daemon. The
12022 daemon encountered a fatal process error and was
12023 logged out to prevent the system from getting into
12024 a loop.
12025
12026 Action: Contact the system programming staff. You can try
12027 logging the daemon in again but if the process
12028 error is recurrent the problem must be corrected
12029 before the daemon will operate successfully.
12030
12031
12032
12033 daemon_user_manager_.pl1
12034 daemon_user_manager_: New process created.
12035
12036
12037 Stream: as severity1
12038
12039 Time: While system is running.
12040
12041 Meaning: An error in a daemon process has caused it to
12042 terminate. A new process has been created.
12043
12044 Action: A new daemon process is created automatically and
12045 you can continue from there.
12046
12047
12048
12049 daemon_user_manager_.pl1
12050 daemon_user_manager_: premature STOPSTOP for
12051 NAME.PROJ SOURCE
12052
12053
12054 Stream: as severity0
12055
12056 Time: While system is running.
12057
12058 Meaning: This indicates a logic error in the supervisor or
12059 CPU or memory hardware problems.
12060
12061 Action: No operator action is required.
12062
12063
12064
12065 daemon_user_manager_ -208- MR12.5 10/27/92^L
12066
12067
12068 daemon_user_manager_.pl1
12069 daemon_user_manager_: process PERSON.PROJECT
12070 SOURCE ignored trm_ signal.
12071
12072
12073 Stream: $as1
12074
12075 Time: While system is running.
12076
12077 Meaning: The daemon process PERSON.PROJECT using message
12078 coordinator SOURCE had been sent a trm_ signal to
12079 cause process termination but the process did not
12080 respond to the signal. The answering service
12081 proceeds with the bump new_proc log out etc
12082 operation.
12083
12084 Action: No operator action is required.
12085
12086
12087
12088 daemon_user_manager_.pl1
12089 daemon_user_manager_: process PERSON.PROJECT
12090 SOURCE ignored wakeup EVENT_MSG from
12091 SENDER_PROCESS_ID
12092
12093
12094 Stream: $as1
12095
12096 Time: While system is running.
12097
12098 Meaning: The daemon process PERSON.PROJECT using message
12099 coordinator SOURCE had been sent a wakeup with
12100 EVENT_MSG by the process with process_id
12101 SENDER_PROCESS_ID. This event message is unknown
12102 and will be ignored.
12103
12104 Action: No operator action is required.
12105
12106
12107
12108
12109
12110
12111
12112
12113
12114
12115
12116
12117
12118
12119
12120
12121
12122
12123 daemon_user_manager_ -209- MR12.5 10/27/92^L
12124
12125
12126 daemon_user_manager_.pl1
12127 daemon_user_manager_: You cannot new_proc to the
12128 requested authorization.
12129 Cannot new_proc to an authorization outside the
12130 daemon's allowed range.
12131
12132
12133 Stream: as severity1
12134
12135 Time: While system is running.
12136
12137 Meaning: A daemon executed an improper new_proc command
12138 trying to change to
12139 an authorization greater than its
12140 maximum allowed authorization or
12141 less than its minimum allowed
12142 authorization as specified in the
12143 Person Name Table PNT System
12144 Administrator's Table SAT and
12145 Project Master File PMF. The new_proc
12146 is performed at the
12147 original authorization of the process.
12148
12149 Action: Contact the system administrator.
12150
12151
12152
12153 dbm_man.pl1
12154 dbm_man: attempt to initialize already
12155 initialized map for PV on dskX_NNS
12156
12157
12158 Stream: BOS Typewriter Crashes system
12159
12160 Time: While system is running.
12161
12162 Meaning: This indicates a logic error in the supervisor or
12163 CPU or memory hardware problems.
12164
12165 Action: Follow normal recovery procedures.
12166
12167
12168
12169
12170
12171
12172
12173
12174
12175
12176
12177
12178
12179
12180
12181 dbm_man -210- MR12.5 10/27/92^L
12182
12183
12184 dbm_man.pl1
12185 dbm_man: bit map relp not set in pvte for PV on
12186 dskX_NNS
12187
12188
12189 Stream: BOS Typewriter Crashes system
12190
12191 Time: While system is running.
12192
12193 Meaning: This indicates a logic error in the supervisor or
12194 CPU or memory hardware problems.
12195
12196 Action: Follow normal recovery procedures.
12197
12198
12199
12200 dbm_man.pl1
12201 dbm_man: Cannot get ASTE for dbm_seg
12202
12203
12204 Stream: BOS Typewriter Crashes system
12205
12206 Time: System Intialization.
12207
12208 Meaning: The system was unable to create the dbm_seg and
12209 obtain an ASTE for this segment.
12210
12211 Action: Contact the system administrator.
12212
12213
12214
12215 dbm_man.pl1
12216 dbm_man: csl failure
12217
12218
12219 Stream: Logged in SYSERR log.
12220
12221 Time: While system is running.
12222
12223 Meaning: The CSL instruction appears to have failed on one
12224 of the processors.
12225
12226 Action: No operator action is required.
12227
12228
12229
12230
12231
12232
12233
12234
12235
12236
12237
12238
12239 dbm_man -211- MR12.5 10/27/92^L
12240
12241
12242 dbm_man.pl1
12243 dbm_man: unable to allocate dumper bit map for PV
12244 on dskX_NNS
12245
12246
12247 Stream: BOS Typewriter Crashes system
12248
12249 Time: While system is running.
12250
12251 Meaning: The system was unable to allocate a dumper bit map
12252 in dbm_seg for the volume on dskX_NNS. Too many
12253 volumes are online or there is something wrong
12254 with the volume header.
12255
12256 Action: Follow normal recovery procedures.
12257
12258
12259
12260 dbm_man.pl1
12261 dbm_man: unable to initialize area: ERROR_MESS
12262
12263
12264 Stream: BOS Typewriter Crashes system
12265
12266 Time: While system is running.
12267
12268 Meaning: This indicates a logic error in the supervisor or
12269 CPU or memory hardware problems.
12270
12271 Action: Follow normal recovery procedures.
12272
12273
12274
12275 deactivate_for_demount.pl1
12276 deactivate_for_demount: Error freeing vtocx OOOO
12277 on dskX_NN for UID. ERRORMESSAGE.
12278
12279
12280 Stream: Logged in SYSERR log.
12281
12282 Time: During system shutdown.
12283
12284 Meaning: The VTOCE for a deciduous segment could not be
12285 freed for the reason indicated. The VTOCE will be
12286 freed by the next volume salvage or by
12287 delete_old_pdds.
12288
12289 Action: No operator action is required.
12290
12291
12292
12293
12294
12295
12296
12297 deactivate_for_demount -212- MR12.5 10/27/92^L
12298
12299
12300 deactivate_segs.pl1
12301 deactivate_segs: unflushed trailer
12302
12303
12304 Stream: BOS Typewriter Crashes system
12305
12306 Time: While system is running.
12307
12308 Meaning: After destroying a process the system found that
12309 some system trailer specifying connection of that
12310 process to some segment still exists for that
12311 process in str_seg. This indicates that some
12312 segment was improperly disconnected from the
12313 process at some time. This indicates a logic
12314 error in the supervisor or CPU or memory hardware
12315 problems.
12316
12317 Action: Follow normal recovery procedures.
12318
12319
12320
12321 debug_check.pl1
12322 debug_check: too many parameters on parm cards
12323
12324
12325 Stream: BOS Typewriter.
12326
12327 Time: System Intialization.
12328
12329 Meaning: A total of 14 options may be specified on PARM
12330 cards. This limit has been exceeded. Options
12331 after the 14th will be ignored.
12332
12333 Action: Correct the configuration deck before the next
12334 bootload.
12335
12336
12337
12338
12339
12340
12341
12342
12343
12344
12345
12346
12347
12348
12349
12350
12351
12352
12353
12354
12355 debug_check -213- MR12.5 10/27/92^L
12356
12357
12358 obs_reconfigure.pl1
12359 delcpu: Cannot stop CPU X.
12360
12361
12362 Stream: Initializer process output.
12363
12364 Time: In response to an operator command.
12365
12366 Meaning: CPU X did not respond to a command to stop within
12367 the expected time. The CPU may be malfunctioning
12368 or in STEP or it may be in a very tight loop.
12369
12370 Action: Check the CPU panel. If the processor appears to
12371 be in a loop it may be possible to break it out
12372 by placing zeros in the processor switches and
12373 using the EXECUTE button to cause a fault; but
12374 this action sometimes causes the system to crash
12375 depending on where the loop is.
12376
12377
12378
12379 obs_reconfigure.pl1
12380 delcpu: CPU X is not online.
12381
12382
12383 Stream: Initializer process output.
12384
12385 Time: In response to an operator command.
12386
12387 Meaning: A delcpu X command finds that CPU X is already
12388 deleted.
12389
12390 Action: No operator action is required.
12391
12392
12393
12394 obs_reconfigure.pl1
12395 delcpu: CPU X is the only CPU.
12396
12397
12398 Stream: Initializer process output.
12399
12400 Time: In response to an operator command.
12401
12402 Meaning: A delcpu X command attempted to delete the last
12403 CPU. No action was taken.
12404
12405 Action: No operator action is required.
12406
12407
12408
12409
12410
12411
12412
12413 delcpu -214- MR12.5 10/27/92^L
12414
12415
12416 obs_reconfigure.pl1
12417 delcpu: Illegal command or subroutine argument.
12418 BLAH
12419
12420
12421 Stream: Initializer process output.
12422
12423 Time: In response to an operator command.
12424
12425 Meaning: Invalid input was typed.
12426
12427 Action: Enter a corrected command line.
12428
12429
12430
12431 obs_reconfigure.pl1
12432 delcpu: Reconfiguration database is locked.
12433
12434
12435 Stream: Initializer process output.
12436
12437 Time: In response to an operator command.
12438
12439 Meaning: Another process is performing reconfiguration
12440 currently or a fault during reconfiguration has
12441 left the reconfiguration tables locked.
12442
12443 Action: If it is certain that no other process is
12444 reconfiguring and that the fault which
12445 interrupted reconfiguration has been cured the
12446 reconfigure$force_unlock command may be used to
12447 clear the lock at the direction of system staff.
12448
12449
12450
12451 obs_reconfigure.pl1
12452 delcpu: Wrong number of arguments supplied.
12453
12454
12455 Stream: Initializer process output.
12456
12457 Time: In response to an operator command.
12458
12459 Meaning: Invalid input was typed.
12460
12461 Action: Enter a corrected command line.
12462
12463
12464
12465
12466
12467
12468
12469
12470
12471 delcpu -215- MR12.5 10/27/92^L
12472
12473
12474 delentry.pl1
12475 delentry: deleting damaged dir PATH for USERID
12476
12477
12478 Stream: Logged in SYSERR log.
12479
12480 Time: While system is running.
12481
12482 Meaning: An attempt to delete a directory found that the
12483 directory header had a zero UID. The directory
12484 was deleted anyway.
12485
12486 Action: No operator action is required.
12487
12488
12489
12490 delentry.pl1
12491 delentry: error from hash$out on "NAME" for
12492 USERID. ERROR_CODE
12493
12494
12495 Stream: Logged in SYSERR log.
12496
12497 Time: While system is running.
12498
12499 Meaning: An attempt to delete the entry name NAME from the
12500 directory hash table failed. This indicates a
12501 logic error in the supervisor or CPU or memory
12502 hardware problems.
12503
12504 Action: No operator action is required.
12505
12506
12507
12508 delentry.pl1
12509 delentry: error from terminate_ for USERID.
12510 ERROR_CODE
12511
12512
12513 Stream: Logged in SYSERR log.
12514
12515 Time: While system is running.
12516
12517 Meaning: An error code was returned while trying to make a
12518 directory unknown while deleting it. This
12519 indicates a logic error in the supervisor or CPU
12520 or memory hardware problems.
12521
12522 Action: No operator action is required.
12523
12524
12525
12526
12527
12528
12529 delentry -216- MR12.5 10/27/92^L
12530
12531
12532 delentry.pl1
12533 delentry: priv_dfile error deleting vtoce for
12534 PATH for USERID. ERROR_CODE
12535
12536
12537 Stream: Logged in SYSERR log.
12538
12539 Time: While system is running.
12540
12541 Meaning: A privileged call to delete a segment discovered a
12542 branch with not VTOC entry. This situation is
12543 called a "connection failure." The branch was
12544 deleted anyway.
12545
12546 Action: No operator action is required.
12547
12548
12549
12550 delete_vtoce.pl1
12551 delete_vtoce: cannot add time/page product
12552 SEGTPP DIRTPP to pvid PPP vtocx VVV uid UUU
12553 ERRORMESSAGE
12554
12555
12556 Stream: Logged in SYSERR log.
12557
12558 Time: While system is running.
12559
12560 Meaning: During the deletion of a directory which had a
12561 quota account a difficulty was encountered in
12562 reflecting its time/page product upward. SEGTPP
12563 and DIRTPP are the time/page product for segments
12564 and directories respectively.
12565
12566 Action: Contact the system administrator.
12567
12568
12569
12570 delete_vtoce.pl1
12571 delete_vtoce: from quotaw pvid PPP. vtocx VVV
12572 ERRORMESSAGE
12573
12574
12575 Stream: Logged in SYSERR log.
12576
12577 Time: While system is running.
12578
12579 Meaning: While deleting a directory which had a quota
12580 account a quota handling problem usually record
12581 quota overflow was encountered.
12582
12583 Action: No operator action is required.
12584
12585
12586
12587 delete_vtoce -217- MR12.5 10/27/92^L
12588
12589
12590 obs_reconfigure.pl1
12591 Deleted CPU X.
12592
12593
12594 Stream: Initializer process output.
12595
12596 Time: In response to an operator command.
12597
12598 Meaning: This is the response to a successful delcpu X
12599 command.
12600
12601 Action: No operator action is required.
12602
12603
12604
12605 obs_reconfigure.pl1
12606 delmain: Abs wired pages in memory.
12607
12608
12609 Stream: Initializer process output.
12610
12611 Time: In response to an operator command.
12612
12613 Meaning: A delmain command attempted to delete a range of
12614 pages which included some pages which cannot be
12615 deleted. No action was taken.
12616
12617 Action: Enter a corrected command line.
12618
12619
12620
12621 obs_reconfigure.pl1
12622 delmain: Illegal command or subroutine argument.
12623 BLAH
12624
12625
12626 Stream: Initializer process output.
12627
12628 Time: In response to an operator command.
12629
12630 Meaning: Invalid input was typed.
12631
12632 Action: Enter a corrected command line.
12633
12634
12635
12636
12637
12638
12639
12640
12641
12642
12643
12644
12645 delmain -218- MR12.5 10/27/92^L
12646
12647
12648 obs_reconfigure.pl1
12649 delmain: Not enough main memory left.
12650
12651
12652 Stream: Initializer process output.
12653
12654 Time: In response to an operator command.
12655
12656 Meaning: A delmain command attempted to delete so much
12657 memory that the system would be unable to function
12658 correctly. No action was taken.
12659
12660 Action: Enter a corrected command line.
12661
12662
12663
12664 obs_reconfigure.pl1
12665 delmain: Reconfiguration database is locked.
12666
12667
12668 Stream: Initializer process output.
12669
12670 Time: In response to an operator command.
12671
12672 Meaning: Another process is performing reconfiguration
12673 currently or a fault during reconfiguration has
12674 left the reconfiguration tables locked.
12675
12676 Action: If it is certain that no other process is
12677 reconfiguring and that the fault which
12678 interrupted reconfiguration has been cured the
12679 reconfigure$force_unlock command may be used to
12680 clear the lock at the direction of system staff.
12681
12682
12683
12684 obs_reconfigure.pl1
12685 delmain: Request is not within range of a single
12686 controller. MAIN XXX
12687
12688
12689 Stream: Initializer process output.
12690
12691 Time: In response to an operator command.
12692
12693 Meaning: A delmain command must specify a range of pages
12694 which lies completely within one controller. No
12695 action was taken.
12696
12697 Action: Enter a corrected command line.
12698
12699
12700
12701
12702
12703 delmain -219- MR12.5 10/27/92^L
12704
12705
12706 obs_reconfigure.pl1
12707 delmain: Wrong number of arguments supplied.
12708
12709
12710 Stream: Initializer process output.
12711
12712 Time: In response to an operator command.
12713
12714 Meaning: Invalid input was typed.
12715
12716 Action: Enter a corrected command line.
12717
12718
12719
12720 obs_reconfigure.pl1
12721 delmem: Abs wired pages in MEM Y.
12722
12723
12724 Stream: Initializer process output.
12725
12726 Time: In response to an operator command.
12727
12728 Meaning: An attempt was made to delete a memory which
12729 included some pages which cannot be deleted. No
12730 action was taken.
12731
12732 Action: The memory cannot be deleted.
12733
12734
12735
12736 obs_reconfigure.pl1
12737 delmem: Illegal command or subroutine argument.
12738 BLAH
12739
12740
12741 Stream: Initializer process output.
12742
12743 Time: In response to an operator command.
12744
12745 Meaning: Invalid input was typed.
12746
12747 Action: Enter a corrected command line.
12748
12749
12750
12751
12752
12753
12754
12755
12756
12757
12758
12759
12760
12761 delmem -220- MR12.5 10/27/92^L
12762
12763
12764 obs_reconfigure.pl1
12765 delmem: MEM Y is not online.
12766
12767
12768 Stream: Initializer process output.
12769
12770 Time: In response to an operator command.
12771
12772 Meaning: A delmem Y command was typed but no such memory is
12773 in use.
12774
12775 Action: No operator action is required.
12776
12777
12778
12779 obs_reconfigure.pl1
12780 delmem: Not enough main memory to remove MEM Y.
12781
12782
12783 Stream: Initializer process output.
12784
12785 Time: In response to an operator command.
12786
12787 Meaning: The system would be unable to function correctly
12788 if SCU Y and its memory were deleted. No action
12789 was taken.
12790
12791 Action: Try something else.
12792
12793
12794
12795 obs_reconfigure.pl1
12796 delmem: Reconfiguration database is locked.
12797
12798
12799 Stream: Initializer process output.
12800
12801 Time: In response to an operator command.
12802
12803 Meaning: Another process is performing reconfiguration
12804 currently or a fault during reconfiguration has
12805 left the reconfiguration tables locked.
12806
12807 Action: If it is certain that no other process is
12808 reconfiguring and that the fault which
12809 interrupted reconfiguration has been cured the
12810 reconfigure$force_unlock command may be used to
12811 clear the lock at the direction of system staff.
12812
12813
12814
12815
12816
12817
12818
12819 delmem -221- MR12.5 10/27/92^L
12820
12821
12822 add_scu.pl1
12823 delmem: Removed MEM X.
12824
12825
12826 Stream: BOS Typewriter.
12827
12828 Time: In response to an operator command.
12829
12830 Meaning: The system control unit X has been deleted.
12831
12832 Action: No operator action is required.
12833
12834
12835
12836 obs_reconfigure.pl1
12837 delmem: Wrong number of arguments supplied.
12838
12839
12840 Stream: Initializer process output.
12841
12842 Time: In response to an operator command.
12843
12844 Meaning: Invalid input was typed.
12845
12846 Action: Enter a corrected command line.
12847
12848
12849
12850 demount_pv.pl1
12851 demount_pv: ast out of sync
12852
12853
12854 Stream: BOS Typewriter Crashes system
12855
12856 Time: Volume demounting or system shutdown.
12857
12858 Meaning: The volume demounter has detected irreparable
12859 damage to the system segment table SST.
12860
12861 Action: Emergency shutdown will fail and need not be
12862 attempted. Follow normal recovery procedures for
12863 ESD failure.
12864
12865
12866
12867
12868
12869
12870
12871
12872
12873
12874
12875
12876
12877 demount_pv -222- MR12.5 10/27/92^L
12878
12879
12880 demount_pv.pl1
12881 demount_pv: ioi_PROGNAME for DRIVENAME:
12882 ERRORMESSAGE
12883
12884
12885 Stream: BOS Typewriter.
12886
12887 Time: Volume demounting.
12888
12889 Meaning: In attempting to cycle down drive DRIVENAME an
12890 unexpected error was received from the I/O
12891 Interfacer. The drive may not be cycled down.
12892
12893 Action: Notify the system programming staff. Cycle down
12894 the drive if it was not cycled down.
12895
12896
12897
12898 demount_pv.pl1
12899 demount_pv: vtoc cleanup of DRIVENAME:
12900 ERRORMESSAGE
12901
12902
12903 Stream: BOS Typewriter.
12904
12905 Time: Volume demounting or shutdown.
12906
12907 Meaning: An unexpected error was encountered in flushing
12908 VTOC information out to a volume being shut down
12909 or demounted. The volume will not be demounted.
12910 message.
12911
12912 Action: Contact the system programming staff. Attempt to
12913 repeat the demount of the logical volume if this
12914 is not during shutdown. The physical volume
12915 involved may have to be salvaged.
12916
12917
12918
12919 demount_pv.pl1
12920 demounted DRIVENAME
12921
12922
12923 Stream: BOS Typewriter.
12924
12925 Time: Volume demounting in response to delete_lv
12926 command or user action.
12927
12928 Meaning: The disk pack on drive DRIVENAME was successfully
12929 demounted.
12930
12931 Action: No operator action is required.
12932
12933
12934
12935 demounted DRIVENAME -223- MR12.5 10/27/92^L
12936
12937
12938 disk_table_.pl1
12939 demounted lv LVNAME
12940
12941
12942 Stream: Initializer process output.
12943
12944 Time: While system is running.
12945
12946 Meaning: The demount of the logical volume LVNAME is
12947 complete.
12948
12949 Action: No operator action is required.
12950
12951
12952
12953 device_acct_.pl1
12954 device_acct_$init: ERROR_MESSAGE. device_table
12955
12956
12957 Stream: $as2
12958
12959 Time: System Intialization.
12960
12961 Meaning: An error occurred which initializing the
12962 device_table. ERROR_MESSAGE is the text
12963 associated with the error code describing the
12964 error. Device accounting is disabled and system
12965 initialization fails.
12966
12967 Action: Contact the system programming staff.
12968
12969
12970
12971 device_acct_.pl1
12972 device_acct_$off: device N ACCT_TYPE_NAME
12973 DEV_NAME not in device table for PERSON.PROJECT
12974
12975
12976 Stream: $as0
12977
12978 Time: While system is running.
12979
12980 Meaning: Device DEV_NAME which has device accounting type
12981 number N associated with ACCT_TYPE_NAME devices
12982 was not found in PERSON.PROJECT's device table
12983 entries. Probable cause is damage to the device
12984 table.
12985
12986 Action: Contact the system administrator.
12987
12988
12989
12990
12991
12992
12993 device_acct_$off -224- MR12.5 10/27/92^L
12994
12995
12996 device_acct_.pl1
12997 device_acct_: deve.pdtep PTR1 not = ute.pdtep
12998 PTR2 for PERSON.PROJECT.
12999
13000
13001 Action: $as2
13002
13003 Time: While system is running.
13004
13005 Meaning: The Project Definition Table entry pointer PTR1
13006 stored in the device table for PERSON.PROJECT
13007 differs from the PDT entry pointer stored in that
13008 user's User Table Entry UTE. This indicates a
13009 logic error in the supervisor or CPU or memory
13010 hardware problems.
13011
13012 Action: Contact the system programming staff.
13013
13014
13015
13016 device_acct_.pl1
13017 device_acct_: ERROR_MESSAGE. Attempting to lock
13018 PDT entry of PERSON.PROJECT
13019
13020
13021 Stream: $as2
13022
13023 Time: While system is running.
13024
13025 Meaning: An attempt was made to lock the Project Definition
13026 Table PDT entry for PERSON.PROJECT to update
13027 device usage charges for the user. Locking did
13028 not succeed within 15 seconds so the charges were
13029 not updated. If the attempt occurred during an
13030 accounting update the charges will continue to
13031 accrue until the next update at which time
13032 locking the PDT entry is again attempted. If the
13033 original attempt occurred as part of a logout or
13034 new_proc operation the device charges are lost.
13035
13036 Action: Contact the system administrator.
13037
13038
13039
13040
13041
13042
13043
13044
13045
13046
13047
13048
13049
13050
13051 device_acct_ -225- MR12.5 10/27/92^L
13052
13053
13054 page_error.alm
13055 device_control: invalid pvtx XX
13056
13057
13058 Stream: BOS Typewriter Crashes system
13059
13060 Time: While system is running.
13061
13062 Meaning: An invalid PVT index XX was found by device
13063 control or an invalid device type appeared in the
13064 PVT entry of that index. This indicates a logic
13065 error in the supervisor or CPU or memory hardware
13066 problems.
13067
13068 Action: Follow normal recovery procedures.
13069
13070
13071
13072 dial_ctl_.pl1
13073 dial_ctl_: Autocall channel CHANNEL declared
13074 multi-class but does not support
13075 set_required_access_class.
13076
13077
13078 Stream: as severity2
13079
13080 Time: $run_
13081
13082 Meaning: The autocall channel CHANNEL has been declared
13083 multi-class in the CDT but the underlying
13084 multiplexer does not support the
13085 set_required_access_class control order. The
13086 channel should be defined as single class. The
13087 user's dial out request was refused.
13088
13089 Action: Contact the system administrator.
13090
13091
13092
13093 dial_ctl_.pl1
13094 dial_ctl_: Can't find process WWWWWWWWWWW
13095
13096
13097 Stream: as severity0
13098
13099 Time: While system is running.
13100
13101 Meaning: An invalid signal was received by the secondary
13102 terminal manager.
13103
13104 Action: Note for system programmer action.
13105
13106
13107
13108
13109 dial_ctl_ -226- MR12.5 10/27/92^L
13110
13111
13112 dial_ctl_.pl1
13113 dial_ctl_: Channel CHANNEL AIM_CLASS SERV_TYPE
13114 hung up on Initializer
13115
13116
13117 Stream: as severity1
13118
13119 Time: While system is running.
13120
13121 Meaning: The channel CHANNEL with access class AIM_CLASS
13122 and service type SERV_TYPE hung up. It had
13123 previously been dialed to the Initializer.
13124
13125 Action: No operator action is required.
13126
13127
13128
13129 dial_ctl_.pl1
13130 dial_ctl_: Channel CHANNEL AIM_CLASS SERV_TYPE
13131 hung up on missing process WWWWWWWWWWWW
13132
13133
13134 Stream: as severity1
13135
13136 Time: While system is running.
13137
13138 Meaning: The channel CHANNEL with access class AIM_CLASS
13139 and service type SERV_TYPE hung up. It had been
13140 dialed to a process but the system cannot
13141 determine what process it had been connected to.
13142 The process may have terminated before the hangup
13143 was detected.
13144
13145 Action: If this happens often inform the programming
13146 staff.
13147
13148
13149
13150
13151
13152
13153
13154
13155
13156
13157
13158
13159
13160
13161
13162
13163
13164
13165
13166
13167 dial_ctl_ -227- MR12.5 10/27/92^L
13168
13169
13170 dial_ctl_.pl1
13171 dial_ctl_: Channel CHANNEL dialed to Initializer
13172 PERSON.PROJECT
13173
13174
13175 Stream: as severity2
13176
13177 Time: While system is running.
13178
13179 Meaning: An additional secondary terminal has been attached
13180 to the Initializer process as a result of a dial
13181 system command. CHANNEL specifies which terminal
13182 dialed Initializer.
13183
13184 Action: If this terminal has been connected to the
13185 Initializer by an authorized operations staff
13186 member proceed to use it by issuing an "accept"
13187 command and possibly the "substty" command. If
13188 this is an invalid attempt to connect to the
13189 system type "drop CHANNEL" to disconnect the
13190 terminal.
13191
13192
13193
13194 dial_ctl_.pl1
13195 dial_ctl_: Channel CHANNEL hung up after dial_out
13196 for PERSON.PROJECT
13197
13198
13199 Stream: as severity0
13200
13201 Time: While system is running.
13202
13203 Meaning: During a dial_out of channel CHANNEL by
13204 PERSON.PROJECT the channel hung up. The dial_out
13205 attempt was aborted.
13206
13207 Action: No operator action is required.
13208
13209
13210
13211
13212
13213
13214
13215
13216
13217
13218
13219
13220
13221
13222
13223
13224
13225 dial_ctl_ -228- MR12.5 10/27/92^L
13226
13227
13228 dial_ctl_.pl1
13229 dial_ctl_: Dialing channel CHANNEL ACC_CLASS to
13230 DESTINATION for PERSON.PROJECT using comm
13231 privilege
13232
13233
13234 Stream: as severity0
13235
13236 Time: While system is running.
13237
13238 Meaning: The user PERSON.PROJECT is dialing out on dial
13239 channel CHANNEL with access class ACC_CLASS to the
13240 destination DESTINATION. If this log message ends
13241 with "using comm privilege" then the process
13242 dialing out has used the comm privilege to
13243 circumvent AIM restrictions.
13244
13245 Action: No operator action is required.
13246
13247
13248
13249 dial_ctl_.pl1
13250 dial_ctl_: ERROR_MESSAGE From
13251 get_required_access_class control order on channel
13252 CHANNEL.
13253
13254
13255 Stream: as severity0
13256
13257 Time: While system is running.
13258
13259 Meaning: While attempting to determine whether the channel
13260 CHANNEL had any access class restrictions imposed
13261 on it by the hardcore ERROR_MESSAGE was returned.
13262 The request in progress was aborted.
13263
13264 Action: Note for system programmer action.
13265
13266
13267
13268
13269
13270
13271
13272
13273
13274
13275
13276
13277
13278
13279
13280
13281
13282
13283 dial_ctl_ -229- MR12.5 10/27/92^L
13284
13285
13286 dial_ctl_.pl1
13287 dial_ctl_: ERROR_MESSAGE. Can't find PNT entry:
13288 PERSON_ID
13289
13290
13291 Stream: as severity2
13292
13293 Time: While system is running.
13294
13295 Meaning: An attempt was made to find the Person Name Table
13296 entry of the PERSON_ID specified in a dial
13297 preaccess command. However an error occurred
13298 which searching in the PNT.
13299
13300 Action: Contact the system administrator.
13301
13302
13303
13304 dial_ctl_.pl1
13305 dial_ctl_: ERROR_MESSAGE. dial_out CHANNEL for
13306 PERSON.PROJECT failed.
13307
13308
13309 Stream: as severity0
13310
13311 Time: While system is running.
13312
13313 Meaning: While attempting to dial_out channel CHANNEL for
13314 PERSON.PROJECT the error ERROR_MESSAGE occured.
13315 The dial_out attempt was aborted.
13316
13317 Action: No operator action is required.
13318
13319
13320
13321 dial_ctl_.pl1
13322 dial_ctl_: ERROR_MESSAGE. after dial_out order
13323 CHANNEL for PERSON.PROJECT
13324
13325
13326 Stream: as severity0
13327
13328 Time: While system is running.
13329
13330 Meaning: The user PERSON.PROJECT is attempting a dial_out
13331 of channel CHANNEL. The dial_out control order
13332 produced the error ERROR_MESSAGE. The dial_out
13333 attempt is aborted.
13334
13335 Action: Note for system programmer action.
13336
13337
13338
13339
13340
13341 dial_ctl_ -230- MR12.5 10/27/92^L
13342
13343
13344 dial_ctl_.pl1
13345 dial_ctl_: ERROR_MESSAGE. Attempting to detach
13346 CHANNEL from PERSON.PROJECT
13347
13348
13349 Stream: as severity0
13350
13351 Time: While system is running.
13352
13353 Meaning: An attempt to disconnect channel CHANNEL from
13354 PERSON.PROJECT failed. ERROR_MESSAGE explains
13355 why.
13356
13357 Action: Note for system programmer action.
13358
13359
13360
13361 dial_ctl_.pl1
13362 dial_ctl_: ERROR_MESSAGE. call to
13363 astty_$tty_new_proc of CHANNEL for PERSON.PROJECT
13364 failed
13365
13366
13367 Stream: as severity0
13368
13369 Time: While system is running.
13370
13371 Meaning: An attempt to connect the channel CHANNEL to
13372 PERSON.PROJECT failed. ERROR_MESSAGE indicates
13373 why.
13374
13375 Action: Contact the system administrator.
13376
13377
13378
13379 dial_ctl_.pl1
13380 dial_ctl_: ERROR_MESSAGE. Could not check access
13381 to >sc1>admin_acs>tandd.acs for PERSON.PROJECT.
13382
13383
13384 Stream: as severity0
13385
13386 Time: While system is running.
13387
13388 Meaning: The user PERSON.PROJECT attempted to tandd_attach
13389 a communications channel. This operation is
13390 controlled by rw access to the ACS segment
13391 specified. For the reason ERROR_MESSAGE the
13392 answering service could not check access to the
13393 segment. The user tandd_attach request was
13394 refused.
13395
13396 Action: Contact the system administrator.
13397
13398
13399 dial_ctl_ -231- MR12.5 10/27/92^L
13400
13401
13402 dial_ctl_.pl1
13403 dial_ctl_: ERROR_MESSAGE. getting
13404 dial_out_status or tty info CHANNEL for
13405 PERSON.PROJECT
13406
13407
13408 Stream: as severity0
13409
13410 Time: While system is running.
13411
13412 Meaning: During a dial_out of channel CHANNEL by
13413 PERSON.PROJECT the error ERROR_MESSAGE was
13414 returned while attempting to determine if the
13415 dial_out control order succeeded or failed.
13416
13417 Action: No operator action is required.
13418
13419
13420
13421 dial_ctl_.pl1
13422 dial_ctl_: ERROR_MESSAGE. Issuing tandd_attach
13423 control order for channel CHAN
13424
13425
13426 Stream: as severity0
13427
13428 Time: While system is running.
13429
13430 Meaning: The user PERSON.PROJECT attempted to tandd_attach
13431 a communications channel which failed for the
13432 reason given by ERROR_MESSAGE. The user
13433 tandd_attach request was refused.
13434
13435 Action: Contact the system administrator.
13436
13437
13438
13439 dial_ctl_.pl1
13440 dial_ctl_: ndialed negative CHANNEL
13441
13442
13443 Stream: as severity0
13444
13445 Time: While system is running.
13446
13447 Meaning: The count of secondary consoles for a user is in
13448 error. A terminal is hanging up which claims to
13449 be attached to a user but his count of attached
13450 terminals is zero.
13451
13452 Action: Note for system programmer action.
13453
13454
13455
13456
13457 dial_ctl_ -232- MR12.5 10/27/92^L
13458
13459
13460 dial_ctl_.pl1
13461 dial_ctl_: Program error.
13462 as_request_sender.version N not correct in dial
13463 request. Should be M.
13464
13465
13466 Stream: as severity1
13467
13468 Time: While system is running.
13469
13470 Meaning: There is a mismatch in the version number used by
13471 the the programs as_request_server_ and dial_ctl_
13472 for the as_request_sender_ structure.
13473
13474 Action: Contact the system programming staff.
13475
13476
13477
13478 dial_ctl_.pl1
13479 dial_ctl_: Refused unknown request from
13480 PERSON.PROJECT; ERROR_MESSAGE REASON
13481
13482
13483 Stream: as severity0
13484
13485 Time: While system is running.
13486
13487 Meaning: PERSON.PROJECT send a dial_server request to the
13488 Initializer of unknown format. It was rejected
13489 for the reasons specified in ERROR_MESSAGE and
13490 REASON.
13491
13492
13493
13494 dial_ctl_.pl1
13495 dial_ctl_: Rejected unknown request from
13496 PERSON.PROJECT. No request flags set in
13497 dial_server_request.
13498
13499
13500 Stream: as severity0
13501
13502 Time: While system is running.
13503
13504 Meaning: The user PERSON.PROJECT attempted to send an
13505 dial_server request to the Initializer but failed
13506 to specify what type of request he/she wanted.
13507
13508 Action: No operator action is required.
13509
13510
13511
13512
13513
13514
13515 dial_ctl_ -233- MR12.5 10/27/92^L
13516
13517
13518 dial_ctl_.pl1
13519 dial_ctl_: sat.ht has PROJECT_ID sat has
13520 OTHER_PROJECT_ID at LOC.
13521
13522
13523 Stream: as severity2
13524
13525 Time: While system is running.
13526
13527 Meaning: The System Administrator's Table is inconsistent
13528 with the location information in its hash table.
13529
13530 Action: Contact the system administrator.
13531
13532
13533
13534 dial_ctl_.pl1
13535 dial_ctl_: Tracing turned off
13536
13537
13538 Stream: as severity1
13539
13540 Time: While system is running.
13541
13542 Meaning: A system administrator has disabled dial_ctl_
13543 tracing.
13544
13545 Action: No operator action is required.
13546
13547
13548
13549 dial_ctl_.pl1
13550 dial_ctl_: Tracing turned on.
13551
13552
13553 Stream: as severity1
13554
13555 Time: While system is running.
13556
13557 Meaning: A system administrator had enabled tracing of the
13558 dial_ctl_ program. Many status messages will be
13559 logged and printed on the console.
13560
13561 Action: No operator action is required.
13562
13563
13564
13565
13566
13567
13568
13569
13570
13571
13572
13573 dial_ctl_ -234- MR12.5 10/27/92^L
13574
13575
13576 dial_ctl_.pl1
13577 DIALIN PERSON1.PROJECT1 CHANNEL to QUALIFIER
13578 PERSON2.PROJECT2
13579
13580
13581 Stream: as severity0
13582
13583 Time: While system is running.
13584
13585 Meaning: A user on channel CHANNEL has used the "dial"
13586 preaccess command to dial the dial qualifier
13587 QUALIFIER owned by PERSON2.PROJECT2. If the
13588 check_acs "slave_dial" flags was on for the
13589 channel then PERSON1.PROJECT1 specifies the
13590 identified user.
13591
13592 Action: No operator action is required.
13593
13594
13595
13596 dial_ctl_.pl1
13597 DIALIN DENIED PERSON1.PROJECT1 CHANNEL to
13598 QUALIFIER PERSON2.PROJECT2 REASON
13599
13600
13601 Stream: as severity0
13602
13603 Time: While system is running.
13604
13605 Meaning: A user on channel CHANNEL attempted to use the
13606 "dial" preaccess command to dial to QUALIFIER
13607 owned by PERSON2.PROJECT2. The attempt was
13608 rejected for REASON. If the channel check_acs
13609 "slave_dial" flag was on then PERSON1.PROJECT1
13610 specifies the identified user on this channel.
13611
13612 Action: Note for system programmer action.
13613
13614
13615
13616
13617
13618
13619
13620
13621
13622
13623
13624
13625
13626
13627
13628
13629
13630
13631 DIALIN DENIED PERSON1.PRO -235- MR12.5 10/27/92^L
13632
13633
13634 dialup_.pl1
13635 dialup_: answer table damaged at UTEP
13636 tra_vec=TTTT
13637
13638
13639 Stream: $as2
13640
13641 Time: While system is running.
13642
13643 Meaning: The tra_vec value was found to be invalid for an
13644 answer table wakeup. Damage to the answer table
13645 is indicated.
13646
13647 Action: Contact the system programming staff.
13648
13649
13650
13651 dialup_.pl1
13652 dialup_: called while ansp = null
13653
13654
13655 Stream: $as2
13656
13657 Time: While system is running.
13658
13659 Meaning: A programming error in the Answering Service or an
13660 incorrect library installation has caused the
13661 Answering Service to be called before being
13662 initialized. The system will ignore the error and
13663 attempt to continue.
13664
13665 Action: Shut down the system and perform a bootload
13666 operation.
13667
13668
13669
13670
13671
13672
13673
13674
13675
13676
13677
13678
13679
13680
13681
13682
13683
13684
13685
13686
13687
13688
13689 dialup_ -236- MR12.5 10/27/92^L
13690
13691
13692 dialup_.pl1
13693 dialup_: called with bad ptr EVENT_MSG_PTR by
13694 WWWWWWWWWWWW
13695
13696
13697 Stream: $as2
13698
13699 Time: While system is running.
13700
13701 Meaning: A programming error in the interprocess
13702 communication system the network software or the
13703 Answering Service itself has occurred. An invalid
13704 message pointer has been passed to the Answering
13705 Service. The system ignores the message and
13706 attempts to continue. This message may be the
13707 result of an incorrect library installation.
13708
13709 Action: Shut down the system and perform a bootload
13710 operation.
13711
13712
13713
13714 dialup_.pl1
13715 dialup_: called with null message ptr
13716
13717
13718 Stream: $as2
13719
13720 Time: While system is running.
13721
13722 Meaning: A programming error in the interprocess
13723 communication system the network software or the
13724 Answering Service itself has occurred. An invalid
13725 message pointer has been passed to the Answering
13726 Service. The system ignores the message and
13727 attempts to continue. This message may be the
13728 result of an incorrect library installation.
13729
13730 Action: Shut down the system and perform a bootload
13731 operation. Inform the system programming staff.
13732
13733
13734
13735
13736
13737
13738
13739
13740
13741
13742
13743
13744
13745
13746
13747 dialup_ -237- MR12.5 10/27/92^L
13748
13749
13750 dialup_.pl1
13751 dialup_: cancelling inactivity bump of
13752 PERSON.PROJECT
13753
13754
13755 Stream: $as1
13756
13757 Time: While system is running.
13758
13759 Meaning: This is a logging message indicating that the
13760 PERSON.PROJECT process that had been previously
13761 bumped due to inactivity has become active. The
13762 automatic logout was therefore cancelled. The
13763 user will receive a message to this effect.
13764
13765 Action: No operator action is required.
13766
13767
13768
13769 dialup_.pl1
13770 dialup_: CDT damaged at CDTEP tra_vec=TTTT
13771
13772
13773 Stream: $as2
13774
13775 Time: While system is running.
13776
13777 Meaning: The tra_vec value was found to be invalid for a
13778 channel wakeup. Damage to the CDT is indicated.
13779
13780 Action: Contact the system programming staff.
13781
13782
13783
13784 dialup_.pl1
13785 dialup_: cdte CDTEP CHANNEL state M in use N -
13786 notify system programmer"
13787
13788
13789 Stream: $as0
13790
13791 Time: While system is running.
13792
13793 Meaning: This indicates a logic error in the supervisor or
13794 CPU or memory hardware problems.
13795
13796 Action: Contact the system programming staff.
13797
13798
13799
13800
13801
13802
13803
13804
13805 dialup_ -238- MR12.5 10/27/92^L
13806
13807
13808 dialup_.pl1
13809 dialup_: cdtep = null and ate.active = DDDD for
13810 UTEP
13811
13812
13813 Stream: $as2
13814
13815 Time: While system is running.
13816
13817 Meaning: This indicates a logic error in the supervisor or
13818 CPU or memory hardware problems.
13819
13820 Action: Contact the system programming staff.
13821
13822
13823
13824 dialup_.pl1
13825 dialup_: channel_error called with cdte in
13826 functional state.
13827
13828
13829 Stream: $as1
13830
13831 Time: While system is running.
13832
13833 Meaning: This indicates a logic error in the supervisor or
13834 CPU or memory hardware problems.
13835
13836 Action: Contact the system programming staff.
13837
13838
13839
13840 dialup_.pl1
13841 dialup_: error - event calls were masked
13842
13843
13844 Stream: $as1
13845
13846 Time: While system is running.
13847
13848 Meaning: This message indicates a serious error in the
13849 Initializer programs. The system attempts to
13850 recover and keep running.
13851
13852 Action: Contact the system programming staff.
13853
13854
13855
13856
13857
13858
13859
13860
13861
13862
13863 dialup_ -239- MR12.5 10/27/92^L
13864
13865
13866 dialup_.pl1
13867 dialup_: ERROR_MESSAGE Getting pointer to help
13868 file SYS_DIR>ENTRY_NAME
13869
13870
13871 Stream: $as2
13872
13873 Time: While system is running.
13874
13875 Meaning: An ERROR_MESSAGE was returned when an attempt was
13876 made to find the login_help or connect_help
13877 segment in the SYS_DIR usually >sc1.
13878
13879 Action: Contact the system programming staff.
13880
13881
13882
13883 dialup_.pl1
13884 dialup_: ERROR_MESSAGE setting new tty info for
13885 CHANNEL
13886
13887
13888 Stream: $as0
13889
13890 Time: While system is running.
13891
13892 Meaning: An ERROR_MESSAGE was returned by a call to
13893 cpg_$set_pit_tty_info when setting new terminal
13894 attributes in a reconnected process on channel
13895 CHANNEL.
13896
13897 Action: Contact the system programming staff.
13898
13899
13900
13901 dialup_.pl1
13902 dialup_: ERROR_MESSAGE Unable to declare handler
13903 for ev chn EVENT_CHN for ate UTEP for CDT_CHANNEL
13904
13905
13906 Stream: $as2
13907
13908 Time: While system is running.
13909
13910 Meaning: An ERROR_MESSAGE was returned when an attempt was
13911 made to declare an event call channel for new
13912 process UTEP on EVENT_CHN attached to
13913 CDT_CHANNEL.
13914
13915 Action: Contact the system programming staff.
13916
13917
13918
13919
13920
13921 dialup_ -240- MR12.5 10/27/92^L
13922
13923
13924 dialup_.pl1
13925 dialup_: ERROR_MESSAGE attempting to allocate a
13926 user table entry for CHANNEL
13927
13928
13929 Stream: $as1
13930
13931 Time: While system is running.
13932
13933 Meaning: An ERROR_MESSAGE was returned from a call to
13934 asu_$attach_ate which allocates a user table
13935 entry.
13936
13937 Action: Contact the system programming staff.
13938
13939
13940
13941 dialup_.pl1
13942 dialup_: ERROR_MESSAGE creating process for
13943 PERSON.PROJECT
13944
13945
13946 Stream: $as2
13947
13948 Time: While system is running.
13949
13950 Meaning: An ERROR_MESSAGE was returned and the system was
13951 unable to create a user process for
13952 PERSON.PROJECT.
13953
13954 Action: If possible get in touch with the user. He got
13955 a message to contact you. Ask him to try again
13956 and to tell you of any peculiarities of his login.
13957 Note all particulars and contact the programming
13958 staff.
13959
13960
13961
13962 dialup_.pl1
13963 dialup_: ERROR_MESSAGE From write_status order on
13964 CHANNEL
13965
13966
13967 Stream: $as1
13968
13969 Time: While system is running.
13970
13971 Meaning: This is a debugging message that will only appear
13972 if tracing has been enabled. An ERROR_MESSAGE by
13973 a call to astty_$tty_order with a "write_status"
13974 order.
13975
13976 Action: Contact the system programming staff.
13977
13978
13979 dialup_ -241- MR12.5 10/27/92^L
13980
13981
13982 dialup_.pl1
13983 dialup_: ERROR_MESSAGE get_required_access_class
13984 order failed for CHANNEL
13985
13986
13987 Stream: $as1
13988
13989 Time: While system is running.
13990
13991 Meaning: An ERROR_MESSAGE was returned by a call to
13992 astty_$tty_order with a get_required_access_class
13993 order for CHANNEL. The channel will be hungup.
13994
13995 Action: Contact the system security administrator.
13996
13997
13998
13999 dialup_.pl1
14000 dialup_: ERROR_MESSAGE ttt error removing
14001 channel CHANNEL COMMENT
14002
14003
14004 Stream: $as2
14005
14006 Time: While system is running.
14007
14008 Meaning: An ERROR_MESSAGE resulting from accessing the TTT
14009 has caused the CHANNEL with COMMENT to be unusable
14010 when attempting to set the default terminal type
14011 based on line-type/baud-rate. The channel has
14012 been removed from known channels.
14013
14014 Action: Contact the system programming staff. An attach
14015 of the CHANNEL can be tried. If the channel is to
14016 be left detached busy out the modem.
14017
14018
14019
14020
14021
14022
14023
14024
14025
14026
14027
14028
14029
14030
14031
14032
14033
14034
14035
14036
14037 dialup_ -242- MR12.5 10/27/92^L
14038
14039
14040 dialup_.pl1
14041 dialup_: ERROR_MESSAGE tty_dim error removing
14042 channel CHANNEL COMMENT
14043
14044
14045 Stream: $as2
14046
14047 Time: While system is running.
14048
14049 Meaning: An ERROR_MESSAGE caused the CHANNEL to be
14050 unusable. The CHANNEL with COMMENT will be
14051 removed from service.
14052
14053 Action: You may try to attach the channel. If that fails
14054 notify the system programmers. If the channel is
14055 to be left detached busy out the modem.
14056
14057
14058
14059 dialup_.pl1
14060 dialup_: ERROR_MESSAGE when attempting to notify
14061 user PERSON.PROJECT of dialup event
14062
14063
14064 Stream: $as0
14065
14066 Time: While system is running.
14067
14068 Meaning: An ERROR_MESSAGE was returned when an attempt was
14069 made to send a message to PERSON.PROJECT about a
14070 dialup event.
14071
14072 Action: Contact the system programming staff.
14073
14074
14075
14076 dialup_.pl1
14077 dialup_: ERROR_MESSAGE. Trying to wakeup process
14078 after reconnection for PERSON.PROJECT.TAG
14079
14080
14081 Stream: $as0
14082
14083 Time: Called in response to a user reconnecting to an
14084 interactive process.
14085
14086 Meaning: A failure occurred while sending a wakeup to the
14087 process being connected to the terminal.
14088 ERROR_MESSAGE is the text associated with the
14089 error code returned by hcs_$wakeup.
14090
14091 Action: No operator action is required.
14092
14093
14094
14095 dialup_ -243- MR12.5 10/27/92^L
14096
14097
14098 dialup_.pl1
14099 dialup_: fatal error during process creation for
14100 PERSON.PROJECT CHANNEL
14101
14102
14103 Stream: $as1
14104
14105 Time: While system is running.
14106
14107 Meaning: A fatal error occurred during process creation for
14108 PERSON.PROJECT on CHANNEL. Reason is given in
14109 previous log entry. This may be due to a user
14110 error: incorrect segments in the user's home
14111 directory or bad login arguments can cause this
14112 problem.
14113
14114 Action: No operator action is required.
14115
14116
14117
14118 dialup_.pl1
14119 dialup_: ignored SSSS for CHANNEL
14120 st=DDDDinuse=UUUUtv=TTTT
14121
14122
14123 Stream: $as2
14124
14125 Time: While system is running.
14126
14127 Meaning: A spurious signal SSSS has arrived for CHANNEL.
14128 The state of the channel is DDD inuse is UUUU and
14129 tra_vec is TTTT.
14130
14131 Action: This may be some user trying to disrupt the
14132 system. Notify the programming staff.
14133
14134
14135
14136
14137
14138
14139
14140
14141
14142
14143
14144
14145
14146
14147
14148
14149
14150
14151
14152
14153 dialup_ -244- MR12.5 10/27/92^L
14154
14155
14156 dialup_.pl1
14157 dialup_: ignored SSSS from PERSON.PROJECT for
14158 CHANNEL state=DDDDinuse=UUUUtv=TTTT
14159
14160
14161 Stream: $as2
14162
14163 Time: While system is running.
14164
14165 Meaning: A spurious signal SSSS from user PERSON.PROJECT
14166 has arrived for CHANNEL. The state of the channel
14167 is DDD inuse is UUUU and tra_vec is TTTT.
14168
14169 Action: This may be some user trying to disrupt the
14170 system. Do a who and save it for the programming
14171 staff.
14172
14173
14174
14175 dialup_.pl1
14176 dialup_: non-null atep UTEP for cdte
14177 CDTEPCHANNEL tv=TRAVECinuse=INUSE
14178
14179
14180 Stream: $as0
14181
14182 Time: While system is running.
14183
14184 Meaning: A wakeup occurred for CHANNEL whose user table
14185 entry pointer UTEP was non-null. A test on the
14186 above information determined that the state of the
14187 channel to be inconsistant. The system will null
14188 the UTEP pointer in the CDT for the above channel.
14189
14190 Action: Contact the system programming staff.
14191
14192
14193
14194 dialup_.pl1
14195 dialup_: premature stopstop for PERSON.PROJECT
14196 CHANNEL
14197
14198
14199 Stream: $as0
14200
14201 Time: While system is running.
14202
14203 Meaning: This indicates a logic error in the supervisor or
14204 CPU or memory hardware problems.
14205
14206 Action: Contact the system programming staff.
14207
14208
14209
14210
14211 dialup_ -245- MR12.5 10/27/92^L
14212
14213
14214 dialup_.pl1
14215 dialup_: process did not respond properly to trm_
14216 signal. PERSON.PROJECT CHANNEL
14217
14218
14219 Stream: $as0
14220
14221 Time: While system is running.
14222
14223 Meaning: The PERSON.PROJECT process on CHANNEL was being
14224 terminated and had been sent the trm_ signal but
14225 it did not respond. User process will be bumped
14226 logged out or new_proced. It is possible that the
14227 user can cause this message.
14228
14229 Action: No operator action is required.
14230
14231
14232
14233 dialup_.pl1
14234 dialup_: process ignored sus_ signal
14235 PERSON.PROJECT CHANNEL
14236
14237
14238 Stream: $as1
14239
14240 Time: While system is running.
14241
14242 Meaning: The PERSON.PROJECT process on CHANNEL ignored the
14243 sus_ signal that had been sent to it. The user
14244 can cause this message.
14245
14246 Action: No operator action is required.
14247
14248
14249
14250 dialup_.pl1
14251 dialup_: process ignored trm_ signal
14252 PERSON.PROJECT CHANNEL
14253
14254
14255 Stream: $as1
14256
14257 Time: While system is running.
14258
14259 Meaning: The PERSON.PROJECT process on CHANNEL had been
14260 sent a trm_ signal but the process did not respond
14261 to it. The process will be handled as was
14262 intended to be; bumped logged out etc.
14263
14264 Action: No operator action is required.
14265
14266
14267
14268
14269 dialup_ -246- MR12.5 10/27/92^L
14270
14271
14272 dialup_.pl1
14273 dialup_: process terminated PERSON.PROJECT
14274 CHANNEL TERM_MESSAGE
14275
14276
14277 Stream: $as0
14278
14279 Time: While system is running.
14280
14281 Meaning: The process for PERSON.PROJECT on CHANNEL was
14282 terminated abnormally due to reason in
14283 TERM_MESSAGE.
14284
14285 Action: No operator action is required.
14286
14287
14288
14289 dialup_.pl1
14290 dialup_: program error.
14291 cdte.current_access_class_valid = "0"b at
14292 disconnected process manipulation for
14293 PERSON.PROJECT channel CHANNEL.
14294
14295
14296 Stream: $as1
14297
14298 Time: While system is running.
14299
14300 Meaning: When the AIM authorization of the current process
14301 was to be checked the
14302 cdte.current_access_class_valid flag was found to
14303 be off. It should never be at this point in the
14304 software.
14305
14306 Action: Contact the system security administrator.
14307
14308
14309
14310
14311
14312
14313
14314
14315
14316
14317
14318
14319
14320
14321
14322
14323
14324
14325
14326
14327 dialup_ -247- MR12.5 10/27/92^L
14328
14329
14330 dialup_.pl1
14331 dialup_: program error: attempt to create
14332 process for PERSON.PROJECT CHANNEL
14333 with ate UTEP not filled in;
14334 n_disc=XXdisc_com=YYdisc_ate_ix=ZZ
14335
14336
14337 Stream: $as1
14338
14339 Time: While system is running.
14340
14341 Meaning: The lg_ctl_ program is supposed to have filled in
14342 process creation variables and set
14343 ute.uflags.proc_create_ok but apparently did not.
14344 This message in the log indicates a program error.
14345
14346 Action: Contact the system programming staff.
14347
14348
14349
14350 dialup_.pl1
14351 dialup_: program error: disconnected ate index
14352 no. CUR_IDX for PERSON.PROJECT is NEXT_IDX
14353
14354
14355 Stream: $as1
14356
14357 Time: While system is running.
14358
14359 Meaning: This indicates a logic error in the supervisor or
14360 CPU or memory hardware problems.
14361
14362 Action: Contact the system programming staff.
14363
14364
14365
14366 dialup_.pl1
14367 dialup_: Program error: null atep with
14368 per-process tra_vec value
14369
14370
14371 Stream: $as2
14372
14373 Time: While system is running.
14374
14375 Meaning: A system programming error in the answering
14376 service has occurred as a wakeup occurred when
14377 tra_vec indicated to expect a process termination
14378 but the ate pointer was null.
14379
14380 Action: Contact the system programming staff.
14381
14382
14383
14384
14385 dialup_ -248- MR12.5 10/27/92^L
14386
14387
14388 dialup_.pl1
14389 dialup_: Program error: null cdtep with
14390 per-channel tra_vec value
14391
14392
14393 Stream: $as2
14394
14395 Time: While system is running.
14396
14397 Meaning: A wakeup was received when the tra_vec value
14398 indicated a channel operation was required but the
14399 cdtep was null. This is considered to be a
14400 programming error.
14401
14402 Action: Contact the system programming staff.
14403
14404
14405
14406 dialup_.pl1
14407 dialup_: Program error: per-process wakeup with
14408 per-channel-only tra_vec value
14409
14410
14411 Stream: $as2
14412
14413 Time: While system is running.
14414
14415 Meaning: A process wakeup occurred when the tra_vec value
14416 indicated it should be a channel wakeup. This is
14417 considered a programing error.
14418
14419 Action: Contact the system programming staff.
14420
14421
14422
14423 dialup_.pl1
14424 dialup_: re-used cdte CDTEPCHANNEL by ate
14425 UTEP destroy_flag=DDDD
14426
14427
14428 Stream: $as0
14429
14430 Time: While system is running.
14431
14432 Meaning: An ate wakeup occurred which pointed to a CDTEP
14433 that was already in use by another process.
14434
14435 Action: Contact the system programming staff.
14436
14437
14438
14439
14440
14441
14442
14443 dialup_ -249- MR12.5 10/27/92^L
14444
14445
14446 dialup_.pl1
14447 dialup_: SLAVE CHANNEL
14448
14449
14450 Stream: $as0
14451
14452 Time: While system is running.
14453
14454 Meaning: Logging message indicating that the slave command
14455 has been entered in on channel CHANNEL which does
14456 not have the "slave_dial" keyword in its check_acs
14457 statement.
14458
14459 Action: No operator action is required.
14460
14461
14462
14463 dialup_.pl1
14464 dialup_: SLAVE PERSON.PROJECT CHANNEL
14465
14466
14467 Stream: $as0
14468
14469 Time: While system is running.
14470
14471 Meaning: Logging message indicating that the slave command
14472 has been entered in on channel CHANNEL which does
14473 have the "slave_dial" keyword in its check_acs
14474 statement.
14475
14476 Action: No operator action is required.
14477
14478
14479
14480 dialup_.pl1
14481 dialup_: terminating fatal process error loop for
14482 PERSON.PROJECT CHANNEL
14483
14484
14485 Stream: $as1
14486
14487 Time: While system is running.
14488
14489 Meaning: The process for PERSON.PROJECT on CHANNEL has
14490 taken too many fatal process errors. This is
14491 governed by fatal_error_loop_seconds and
14492 fatal_error_loop_count in the installation_parms.
14493 The user will not get a new process. The channel
14494 will not be hungup but will get a message
14495 indicating this condition. This message may be
14496 due to a user error.
14497
14498 Action: No operator action is required.
14499
14500
14501 dialup_ -250- MR12.5 10/27/92^L
14502
14503
14504 dialup_.pl1
14505 dialup_: The answer table is full MAX entries.
14506
14507
14508 Stream: $as1
14509
14510 Time: While system is running.
14511
14512 Meaning: The system answer table is full and has MAX
14513 entries. No more users will be able to login.
14514
14515 Action: Contact the system programming staff.
14516
14517
14518
14519 dialup_.pl1
14520 dialup_: trace event CHANNEL FFFFFFFF
14521 WWWWWWWWWWWW RRRRRRDDDDDD SS XXXX st N wp M
14522
14523
14524 Stream: $as1
14525
14526 Time: While system is running.
14527
14528 Meaning: This is trace output. When dialup_$trace_on is
14529 called these messages are printed out for every
14530 signal concerning a device channel. FFFFFFFF is
14531 the function being performed. WWWWWWWWWWWW is the
14532 sending process ID. RRRRRR is the ring origin of
14533 the signal. DDDDDD is the device signal
14534 information. The pointer SS XXXX locates the
14535 answer table entry for CHANNEL. The channel state
14536 is N and the wait point transaction vector is M.
14537
14538 Action: $ignore To turn these messages off type
14539 dialup_$trace_off while in admin mode.
14540
14541
14542
14543 dialup_.pl1
14544 dialup_: tracing turned off.
14545
14546
14547 Stream: $as1
14548
14549 Time: While system is running.
14550
14551 Meaning: The dialup_ tracing function has been turned off.
14552
14553 Action: No operator action is required.
14554
14555
14556
14557
14558
14559 dialup_ -251- MR12.5 10/27/92^L
14560
14561
14562 dialup_.pl1
14563 dialup_: tracing turned on for channel CHANNEL.
14564
14565
14566 Stream: $as1
14567
14568 Time: While system is running.
14569
14570 Meaning: The dialup_$trace_on entry point was called with
14571 an argument the begining part of a CDT channel
14572 name; to trace all channels on FNP a then supply
14573 "a"; to trace all channels on second hsla of FNP
14574 B supply "b.h1".
14575
14576 Action: $ignore If tracing is to be turned off type
14577 dialup_$trace_off in admin mode.
14578
14579
14580
14581 dialup_.pl1
14582 dialup_: tracing turned on.
14583
14584
14585 Stream: $as1
14586
14587 Time: While system is running.
14588
14589 Meaning: The dialup_$trace_on entry point was called
14590 without arguments. All channels will be traced.
14591
14592 Action: $ignore If tracing is to be turned off type
14593 dialup_$trace_off in admin mode.
14594
14595
14596
14597 dialup_.pl1
14598 dialup_: turning off disconnected flag for ate
14599 UTEP cdte CDTEPCHANNEL
14600
14601
14602 Stream: $as0
14603
14604 Time: While system is running.
14605
14606 Meaning: If processing an ate wakeup the CHANNEL is known
14607 and the process is disconnected the disconnected
14608 flag for the ate will be turned off.
14609
14610 Action: Contact the system programming staff.
14611
14612
14613
14614
14615
14616
14617 dialup_ -252- MR12.5 10/27/92^L
14618
14619
14620 dialup_.pl1
14621 dialup_: turning on disconnected flag for ate
14622 UTEP
14623
14624
14625 Stream: $as0
14626
14627 Time: While system is running.
14628
14629 Meaning: If after detecting a re-used cdte and the
14630 disconnected flag is not on the disconnected flag
14631 will be turned on and noted by this message.
14632
14633 Action: Contact the system programming staff.
14634
14635
14636
14637 dialup_.pl1
14638 dialup_: Unable to determine initial terminal
14639 type for channel CHAN
14640
14641
14642 Stream: $as2
14643
14644 Time: While system is running.
14645
14646 Meaning: cdte.initial_terminal_type is not set indicating
14647 CDT damage. Channel CHAN is removed from the
14648 system.
14649
14650 Action: Contact the system programming staff.
14651
14652
14653
14654 dialup_.pl1
14655 dialup_: Unexpected termsgnl for PERSON.PROJECT
14656 CHANNEL preempted=DDDD.
14657
14658
14659 Stream: $as0
14660
14661 Time: While system is running.
14662
14663 Meaning: A "termsgnl" wakeup was received for the
14664 PERSON.PROJECT process on CHANNEL whose
14665 ute.preempted value DDDD did not indicate one was
14666 allowed. This is considered to be a program
14667 error. User will be given a new process.
14668
14669 Action: Contact the system programming staff.
14670
14671
14672
14673
14674
14675 dialup_ -253- MR12.5 10/27/92^L
14676
14677
14678 dialup_.pl1
14679 dialup_: wrong answerback on CHANNEL COMMENT;
14680 expected "ID1" got "ID2".
14681
14682
14683 Stream: $as2
14684
14685 Time: While system is running.
14686
14687 Meaning: A terminal attempted to connect on CHANNEL whose
14688 CDT comment is COMMENT that is restricted to a
14689 specific answerback and did not return the
14690 expected value. ID1 is the answerback expected;
14691 ID2 is the answerback actually received. The
14692 terminal is hung up.
14693
14694 Action: No operator action is required.
14695
14696
14697
14698 dir_lock_init.pl1
14699 dir_lock_init: cannot get ASTE for dir_lock_seg.
14700
14701
14702 Stream: BOS Typewriter Crashes system
14703
14704 Time: System Intialization.
14705
14706 Meaning: No space could be obtained for dir_lock_seg. This
14707 can result from inadequate ASTE pools or hardcore
14708 partition.
14709
14710 Action: Follow normal recovery procedures. The Multics
14711 System Tape may be incorrect. If the problem
14712 persists try another MST.
14713
14714
14715
14716 disk_control.pl1
14717 disk_control: Adding channel ICC.
14718
14719
14720 Stream: BOS Typewriter.
14721
14722 Time: While system is running.
14723
14724 Meaning: A message to confirm that channel ICC has been
14725 added to the system in response to a reconfigure
14726 command.
14727
14728 Action: No operator action is required.
14729
14730
14731
14732
14733 disk_control -254- MR12.5 10/27/92^L
14734
14735
14736 disk_control.pl1
14737 disk_control: dskX_NN now operational.
14738
14739
14740 Stream: BOS Typewriter.
14741
14742 Time: While system is running.
14743
14744 Meaning: A disk drive which required intervention has
14745 successfully completed an I/O operation. The
14746 system will again use its contents.
14747
14748 Action: No operator action is required.
14749
14750
14751
14752 disk_control.pl1
14753 disk_control: dskX_NN requires intervention.
14754
14755
14756 Stream: BOS Typewriter sounds beeper
14757
14758 Time: While system is running.
14759
14760 Meaning: A disk error has occurred which could have been
14761 caused by the pack or drive being broken or
14762 requiring operator attention. The system has
14763 retried the operation an appropriate number of
14764 times without success. The system will try the
14765 device periodically to check if it has been
14766 repaired.
14767
14768 Action: Inspect the device. If it is not ready ready it.
14769 If it is ready try unreadying and re-readying it.
14770 If the drive cannot be made ready contact
14771 Customer Service personnel.
14772
14773
14774
14775
14776
14777
14778
14779
14780
14781
14782
14783
14784
14785
14786
14787
14788
14789
14790
14791 disk_control -255- MR12.5 10/27/92^L
14792
14793
14794 disk_control.pl1
14795 disk_control: MAJOR_STAT SUBSTAT for dskX_NN
14796 channel ICC.
14797 rec RRRR sect SSSS main AAAA
14798 detailed status: XX XX XX XX XX XX XX XX
14799
14800
14801 Stream: BOS Typewriter.
14802
14803 Time: While system is running.
14804
14805 Meaning: A disk error has occurred on drive dskX_NN. The
14806 major status and substatus are interpreted as
14807 character strings. The disk address is given both
14808 as a Multics record address in octal and as an
14809 absolute sector number in octal. The main store
14810 address being used was AAAA octal. The third line
14811 gives the hexadecimal value of the detailed status
14812 in cases where this data is useful. See manual
14813 AN87 System Formats for interpretation of this
14814 information.
14815
14816 Action: Note for Customer Service action. The segment
14817 involved in a disk error can often be identified
14818 by an application of the "record_to_vtocx" tool to
14819 the Multics record number given in the message.
14820
14821
14822
14823
14824
14825
14826
14827
14828
14829
14830
14831
14832
14833
14834
14835
14836
14837
14838
14839
14840
14841
14842
14843
14844
14845
14846
14847
14848
14849 disk_control -256- MR12.5 10/27/92^L
14850
14851
14852 disk_control.pl1
14853 disk_control: MAJOR_STAT SUBSTAT for dskX_NN
14854 channel ICC.
14855 rec RRRR sect SSSS main AAAA
14856 subvol V logical rec OOOO logical sect TTTT
14857 detailed status: XX XX XX XX XX XX XX XX
14858
14859
14860 Stream: BOS Typewriter.
14861
14862 Time: While system is running.
14863
14864 Meaning: A disk error has occurred on drive dskX_NN. The
14865 major status and substatus are interpreted as
14866 character strings. The disk address is given both
14867 as a Multics record address in octal and as an
14868 absolute sector number in octal. The main store
14869 address being used was AAAA octal. The subvolume
14870 name is V the logical device name is dskX_NNV
14871 the logical record address is OOOO octal and the
14872 logical sector number is TTTT octal. The fourth
14873 line gives the hexadecimal value of the detailed
14874 status in cases where this data is useful. See
14875 manual AN87 System Formats for interpretation of
14876 this information.
14877
14878 Action: Note for Customer Service action. The segment
14879 involved in a disk error can often be identified
14880 by an application of the "record_to_vtocx" tool to
14881 the Multics logical record number given in the
14882 message.
14883
14884
14885
14886 disk_control.pl1
14887 disk_control: Placing dskX_NN in operation.
14888
14889
14890 Stream: BOS Typewriter.
14891
14892 Time: While system is running.
14893
14894 Meaning: A special interrupt has been received for a disk
14895 drive marked as broken. The system will attempt
14896 to use the device.
14897
14898 Action: No operator action is required.
14899
14900
14901
14902
14903
14904
14905
14906
14907 disk_control -257- MR12.5 10/27/92^L
14908
14909
14910 disk_control.pl1
14911 disk_control: Queuing error.
14912
14913
14914 Stream: BOS Typewriter Crashes system
14915
14916 Time: While system is running.
14917
14918 Meaning: This indicates a logic error in the supervisor or
14919 CPU or memory hardware problems.
14920
14921 Action: Follow normal recovery procedures.
14922
14923
14924
14925 disk_control.pl1
14926 disk_control: Reconnected IO_TYPE I/O on dskX_NN
14927 channel ICC.
14928
14929
14930 Stream: $info and/or Logged in SYSERR log.
14931
14932 Time: While system is running.
14933
14934 Meaning: A disk interrupt was apparently lost. Status for
14935 the disk did not arrive within the expected time.
14936 This may be an indication of a channel or
14937 controller malfunction. The system restarts the
14938 disk operation.
14939
14940 Action: $ignore Unless these messages persist which may
14941 indicate a hardware malfunction that needs
14942 investigation. Some types of channel adapters
14943 and/or disk controllers can be "reset" in an
14944 attempt to correct the condition.
14945
14946
14947
14948 disk_control.pl1
14949 disk_control: Removing channel ICC.
14950
14951
14952 Stream: BOS Typewriter sounds beeper
14953
14954 Time: While system is running.
14955
14956 Meaning: Errors occurred indicative of a defective disk
14957 channel or MPC. The channel receiving the errors
14958 is placed offline.
14959
14960 Action: Contact the system programming staff. Also inform
14961 Customer Service personnel.
14962
14963
14964
14965 disk_control -258- MR12.5 10/27/92^L
14966
14967
14968 disk_control.pl1
14969 disk_control: Unexpected IOM status SSSS for
14970 dskX_NN channel ICC.
14971
14972
14973 Stream: BOS Typewriter.
14974
14975 Time: While system is running.
14976
14977 Meaning: Status has been received from a channel which was
14978 not marked active. This is due to a disk
14979 subsystem or IOM problem or to a logic error in
14980 the supervisor. See manual AN87 System Formats
14981 for an interpretation of the status SSSS. The
14982 system ignores the status and attempts to continue
14983 operation.
14984
14985 Action: No operator action is required.
14986
14987
14988
14989 disk_emergency.pl1
14990 disk_emergency: DSKX_NN inoperative; shutdown of
14991 DSKX_NN suspended
14992
14993
14994 Stream: BOS Typewriter sounds beeper
14995
14996 Time: Emergency shutdown.
14997
14998 Meaning: During emergency shutdown DSKX_NN was found
14999 inoperative. Data in main memory or on the paging
15000 device which need to be flushed to the pack on
15001 DSKX_NN cannot be written out. The data remain
15002 where they were and ESD may be tried again.
15003
15004 Action: If the drive can be made ready make it ready and
15005 try ESD again. Do NOT move packs before trying
15006 ESD unless address plugs are changed so that the
15007 same pack appears to have the same address. If
15008 this action is performed the MPC must be halted
15009 and restarted with a reset and branch. If the
15010 pack is not successfully shut down the system
15011 will volume salvage it when it is next brought up
15012 and data from main memory which belongs on the
15013 pack will be lost.
15014
15015
15016
15017
15018
15019
15020
15021
15022
15023 disk_emergency -259- MR12.5 10/27/92^L
15024
15025
15026 disk_init.pl1
15027 disk_init: Devices D1 and D2 of DSKn must have
15028 the same model number.
15029
15030
15031 Stream: BOS Typewriter Crashes system
15032
15033 Time: System Intialization.
15034
15035 Meaning: Two devices that share a common spindle have been
15036 configured with different model numbers.
15037
15038 Action: Correct the config deck and reboot.
15039
15040
15041
15042 disk_init.pl1
15043 disk_init: Disk model XXXX not found in
15044 config_data_.
15045
15046
15047 Stream: BOS Typewriter Crashes system
15048
15049 Time: System Intialization.
15050
15051 Meaning: This indicates a logic error in the supervisor or
15052 CPU or memory hardware problems.
15053
15054 Action: Follow normal recovery procedures. Fix the
15055 configuration deck and reboot.
15056
15057
15058
15059 disk_init.pl1
15060 disk_init: DSKn D1 must be configured if DSKn D2
15061 is configured.
15062
15063
15064 Stream: BOS Typewriter Crashes system
15065
15066 Time: System Intialization.
15067
15068 Meaning: Only one of a pair of devices that share a common
15069 spindle has been configured.
15070
15071 Action: Change the config deck to include the missing
15072 device and reboot.
15073
15074
15075
15076
15077
15078
15079
15080
15081 disk_init -260- MR12.5 10/27/92^L
15082
15083
15084 disk_init.pl1
15085 disk_init: error WWWW from absadr for DSKX iom N
15086 ch ZZ.
15087
15088
15089 Stream: BOS Typewriter Crashes system
15090
15091 Time: System Intialization.
15092
15093 Meaning: This indicates a logic error in the supervisor or
15094 CPU or memory hardware problems.
15095
15096 Action: Follow normal recovery procedures. The Multics
15097 System Tape may be incorrect. If the problem
15098 persists try another MST.
15099
15100
15101
15102 disk_init.pl1
15103 disk_init: Invalid channel on CHNL DSKx card.
15104
15105
15106 Stream: BOS Typewriter Crashes system
15107
15108 Time: System Intialization.
15109
15110 Meaning: An invalid channel specification was found on the
15111 CHNL card for DSKx.
15112
15113
15114
15115 disk_init.pl1
15116 disk_init: Invalid channel on PRPH DSKx card.
15117
15118 Stream: BOS Typewriter Crashes system
15119
15120
15121 Time: System Intialization.
15122
15123 Meaning: An invalid channel specification was found on the
15124 PRPH DSKx card.
15125
15126
15127
15128
15129
15130
15131
15132
15133
15134
15135
15136
15137
15138
15139 disk_init -261- MR12.5 10/27/92^L
15140
15141
15142 disk_init.pl1
15143 disk_init: Invalid format for XXXX card.
15144
15145
15146 Stream: BOS Typewriter Crashes system
15147
15148 Time: System Intialization.
15149
15150 Meaning: A required field on the XXXX card is not present.
15151
15152 Action: Follow normal recovery procedures. Fix the
15153 configuration deck and reboot.
15154
15155
15156
15157 disk_init.pl1
15158 disk_init: No valid disk models found on PRPH
15159 DSKx card.
15160
15161
15162 Stream: BOS Typewriter Crashes system
15163
15164 Time: System Intialization.
15165
15166 Meaning: All disk model fields were found to be zero.
15167
15168 Action: Fix the configuration deck and reboot.
15169
15170
15171
15172 disk_init.pl1
15173 disk_init: Too many channels configured for DSKn.
15174 Limit is N.
15175
15176
15177 Stream: BOS Typewriter Crashes system
15178
15179 Time: System Intialization.
15180
15181 Meaning: The per subsystem software limit for logical
15182 channels has been exceeded.
15183
15184 Action: Fix the config deck and reboot. If more channels
15185 are needed split the configuration into more
15186 subsystems in the config deck.
15187
15188
15189
15190
15191
15192
15193
15194
15195
15196
15197 disk_init -262- MR12.5 10/27/92^L
15198
15199
15200 disk_init.pl1
15201 disk_init: Too many devices configured for DSKn.
15202 Max device is N.
15203
15204
15205 Stream: BOS Typewriter Crashes system
15206
15207 Time: System Intialization.
15208
15209 Meaning: The software limit for devices per subsystem has
15210 been exceeded.
15211
15212 Action: Fix the config deck and reboot.
15213
15214
15215
15216 disk_init.pl1
15217 disk_init: Unable to assign CCCC for DSKx.
15218
15219
15220 Stream: BOS Typewriter Crashes system
15221
15222 Time: System Intialization.
15223
15224 Meaning: An error has occurred trying to assign an IOM
15225 channel for the disk subsystem DSKX.
15226
15227 Action: Follow normal recovery procedures. Check the
15228 configuration deck and the operability of the
15229 hardware before rebooting.
15230
15231
15232
15233 disk_init.pl1
15234 disk_init: Unknown model number NNNN on PRPH
15235 dskN.
15236
15237
15238 Stream: BOS Typewriter Crashes system
15239
15240 Time: System Intialization.
15241
15242 Meaning: The model number NNNN on the prph card for disk
15243 subsystem N is invalid.
15244
15245 Action: Correct the config deck and reboot.
15246
15247
15248
15249
15250
15251
15252
15253
15254
15255 disk_init -263- MR12.5 10/27/92^L
15256
15257
15258 disk_reader.pl1
15259 disk_reader: Attempt to read past end of mst
15260 area.
15261
15262
15263 Stream: BOS Typewriter Crashes system
15264
15265 Time: System Intialization.
15266
15267 Meaning: An attempt was made to read more data from the mst
15268 area of disk than was placed there from the MST.
15269 This is most likely the result of an MST misformed
15270 originally.
15271
15272 Action: Follow normal recovery procedures. The Multics
15273 System Tape may be incorrect. If the problem
15274 persists try another MST.
15275
15276
15277
15278 disk_rebuild.pl1
15279 disk_rebuild: Disk rebuild finished with errors:
15280 ERRORMESS
15281
15282
15283 Stream: Salvager output.
15284
15285 Time: During disk rebuilding.
15286
15287 Meaning: The disk rebuild has been aborted due to the
15288 indicated ERRORMESS.
15289
15290 Action: Contact the system programming staff.
15291
15292
15293
15294 disk_rebuild.pl1
15295 disk_rebuild: base of paging region changed from
15296 XXX. to YYY.
15297
15298
15299 Stream: Salvager output.
15300
15301 Time: During disk rebuilding.
15302
15303 Meaning: The base of the paging region for the new pack is
15304 different from that for the old one.
15305
15306 Action: No operator action is required.
15307
15308
15309
15310
15311
15312
15313 disk_rebuild -264- MR12.5 10/27/92^L
15314
15315
15316 disk_rebuild.pl1
15317 disk_rebuild: Begin disk rebuild of DSKX_NNs
15318 onto DSKY_MMs
15319
15320
15321 Stream: Salvager output.
15322
15323 Time: During disk rebuilding.
15324
15325 Meaning: This message is printed when disk rebuilding
15326 begins.
15327
15328 Action: No operator action is required.
15329
15330
15331
15332 disk_rebuild.pl1
15333 disk_rebuild: Cannot compress VTOC on dskX_NNs
15334 because active VTOCEs in the truncated region.
15335
15336
15337 Stream: Salvager output.
15338
15339 Time: During disk rebuilding.
15340
15341 Meaning: A rebuild was requested in which the number of
15342 VTOCEs on the new volume was smaller than the
15343 number of VTOCEs on the old volume. This is
15344 permitted only if there are no active VTOCEs in
15345 the truncated region that is no active VTOCEs on
15346 the old volume have VTOCE indices which would be
15347 too high for the new volume.
15348
15349 Action: Run sweep_pv -from num_vtoces to remove these
15350 VTOCEs from the old volume and retry the rebuild.
15351 It may be necessary to salvage the volume to
15352 recover lost VTOCEs in the truncated region.
15353
15354
15355
15356 disk_rebuild.pl1
15357 disk_rebuild: copying XXX. rec of part NAME
15358
15359
15360 Stream: Salvager output.
15361
15362 Time: During disk rebuilding.
15363
15364 Meaning: A disk rebuild is reformatting a pack which
15365 contains non-paging partitions. The contents of
15366 these partitions are copied exactly.
15367
15368 Action: No operator action is required.
15369
15370
15371 disk_rebuild -265- MR12.5 10/27/92^L
15372
15373
15374 disk_rebuild.pl1
15375 disk_rebuild: Disk rebuild finished.
15376
15377
15378 Stream: Salvager output.
15379
15380 Time: During disk rebuilding.
15381
15382 Meaning: The disk rebuild has completed.
15383
15384 Action: No operator action is required.
15385
15386
15387
15388 disk_rebuild.pl1
15389 disk_rebuild: dskX_NNs must be mounted for
15390 rebuild.
15391
15392
15393 Stream: Salvager output.
15394
15395 Time: During disk rebuilding.
15396
15397 Meaning: The "from" volume must be mounted for the rebuild.
15398
15399 Action: Mount the logical volume to which the "from"
15400 volume belongs and try the rebuild abain.
15401
15402
15403
15404 disk_rebuild.pl1
15405 disk_rebuild: dskX_NNs must not be mounted for
15406 rebuild.
15407
15408
15409 Stream: Salvager output.
15410
15411 Time: During disk rebuilding.
15412
15413 Meaning: The "to" volume must not be mounted to the Storage
15414 System for a rebuild.
15415
15416 Action: Demount the logical volume to which the volume
15417 belongs and retry the rebuild.
15418
15419
15420
15421
15422
15423
15424
15425
15426
15427
15428
15429 disk_rebuild -266- MR12.5 10/27/92^L
15430
15431
15432 disk_rebuild.pl1
15433 disk_rebuild: End of rebuilding. New summary
15434 report follows:
15435
15436
15437 Stream: Salvager output.
15438
15439 Time: During disk rebuilding.
15440
15441 Meaning: Rebuilding has completed. A summary report of the
15442 new volume parameter is printed.
15443
15444 Action: No operator action is required.
15445
15446
15447
15448 disk_rebuild.pl1
15449 disk_rebuild: Error from read_disk aborting:
15450 ERRORMESS
15451
15452
15453 Stream: Salvager output.
15454
15455 Time: During disk rebuilding.
15456
15457 Meaning: This indicates a logic error in the supervisor or
15458 CPU or memory hardware problems. The disk rebuild
15459 is aborted.
15460
15461 Action: Contact the system programming staff.
15462
15463
15464
15465 disk_rebuild.pl1
15466 disk_rebuild: Error from write_disk aborting:
15467 ERRORMESS
15468
15469
15470 Stream: Salvager output.
15471
15472 Time: During disk rebuilding.
15473
15474 Meaning: This indicates a logic error in the supervisor or
15475 CPU or memory hardware problems. The disk rebuild
15476 is aborted.
15477
15478 Action: Contact the system programming staff.
15479
15480
15481
15482
15483
15484
15485
15486
15487 disk_rebuild -267- MR12.5 10/27/92^L
15488
15489
15490 disk_rebuild.pl1
15491 disk_rebuild: Error writing label: ERRORMESS
15492
15493
15494 Stream: Salvager output.
15495
15496 Time: During disk rebuilding.
15497
15498 Meaning: A disk error has occurred writing the new label
15499 during a disk rebuild. The disk rebuild is
15500 aborted.
15501
15502 Action: Correct the problem and issue a new command.
15503
15504
15505
15506 disk_rebuild.pl1
15507 disk_rebuild: freeing deciduous vtocx XXXo: NAME
15508
15509
15510 Stream: Salvager output.
15511
15512 Time: During disk rebuilding.
15513
15514 Meaning: The segment originally named NAME at vtoc index
15515 XXXo was deciduous and has been deleted from the
15516 RPV. This is debugging output printed for system
15517 programmers if a SALV DEBG card is supplied.
15518
15519 Action: No operator action is required.
15520
15521
15522
15523 disk_rebuild.pl1
15524 disk_rebuild: freeing process vtocx XXXo: NAME
15525
15526
15527 Stream: Salvager output.
15528
15529 Time: During disk rebuilding.
15530
15531 Meaning: The segment originally named NAME at vtoc index
15532 XXXo was per-process and has been deleted. This
15533 is debugging output printed for system programmers
15534 if a SALV DEBG card is used.
15535
15536 Action: No operator action is required.
15537
15538
15539
15540
15541
15542
15543
15544
15545 disk_rebuild -268- MR12.5 10/27/92^L
15546
15547
15548 disk_rebuild.pl1
15549 disk_rebuild: INIT_TABLES: aste pool WWWo too
15550 small
15551
15552
15553 Stream: BOS Typewriter.
15554
15555 Time: While system is running.
15556
15557 Meaning: The physical volume salvager was unable to obtain
15558 the necessary temporary AST entries for its work
15559 segments. No salvaging was done.
15560
15561 Action: Shut down manually correct the SST card and
15562 reboot. Then salvage all volumes since the
15563 indicator that volumes need salvaging may have
15564 been lost.
15565
15566
15567
15568 disk_rebuild.pl1
15569 disk_rebuild: Map of assigned addresses changed
15570
15571
15572 Stream: Salvager output.
15573
15574 Time: During disk rebuilding.
15575
15576 Meaning: If any corrections were made to the map on the
15577 volume which shows which addresses are free and
15578 which are in use this message is printed. If the
15579 volume was not properly shut down this message is
15580 to be expected.
15581
15582 Action: No operator action is required.
15583
15584
15585
15586 disk_rebuild.pl1
15587 disk_rebuild: NN vtoces added to list of free
15588 vtoces.
15589
15590
15591 Stream: Salvager output.
15592
15593 Time: During disk rebuilding.
15594
15595 Meaning: NN free VTOC entries were found while salvaging
15596 and added to the list of free VTOC entries. This
15597 is a normal message.
15598
15599 Action: No operator action is required.
15600
15601
15602
15603 disk_rebuild -269- MR12.5 10/27/92^L
15604
15605
15606 disk_rebuild.pl1
15607 disk_rebuild: no. of free recs changed from OLD.
15608 to NEW.
15609
15610
15611 Stream: Salvager output.
15612
15613 Time: During disk rebuilding.
15614
15615 Meaning: If The number of free records in the volume label
15616 is changed by a volume salvage this message is
15617 printed. If the volume was not properly shut
15618 down this message is to be expected.
15619
15620 Action: No operator action is required.
15621
15622
15623
15624 disk_rebuild.pl1
15625 disk_rebuild: no. of free vtoces changed from
15626 OLD. to NEW.
15627
15628
15629 Stream: Salvager output.
15630
15631 Time: During disk rebuilding.
15632
15633 Meaning: If the number of free VTOC entries in the volume
15634 label is changed by a volume salvage this message
15635 is printed.
15636
15637 Action: No operator action is required.
15638
15639
15640
15641 disk_rebuild.pl1
15642 disk_rebuild: not enough free records only XXX.
15643 for increase need YYY.
15644
15645
15646 Stream: Salvager output.
15647
15648 Time: During disk rebuilding.
15649
15650 Meaning: An attempt was made to increase the size of some
15651 partitions or of the VTOC. This required a
15652 decrease in the size of the paging region. The
15653 paging region is too full to be shrunk as
15654 required. The disk rebuild is aborted.
15655
15656 Action: Issue a different disk_rebuild command or bring
15657 up Multics and delete some segments from the pack
15658 before trying again.
15659
15660
15661 disk_rebuild -270- MR12.5 10/27/92^L
15662
15663
15664 disk_rebuild.pl1
15665 disk_rebuild: out of room on vtocx XXXo page
15666 YYYo
15667
15668
15669 Stream: Salvager output.
15670
15671 Time: During disk rebuilding.
15672
15673 Meaning: This indicates a logic error in the supervisor or
15674 CPU or memory hardware problems. The disk rebuild
15675 is aborted.
15676
15677 Action: Contact the system programming staff.
15678
15679
15680
15681 disk_rebuild.pl1
15682 disk_rebuild: processing VTOCE #XXX.
15683
15684
15685 Stream: BOS Typewriter.
15686
15687 Time: During disk rebuilding.
15688
15689 Meaning: This message indicates that a disk rebuild is
15690 progressing normally. It is printed every 1000.
15691 VTOC entries.
15692
15693 Action: No operator action is required.
15694
15695
15696
15697 disk_rebuild.pl1
15698 disk_rebuild: Read error accessing VTOC Map of
15699 dskX_NNs
15700
15701
15702 Stream: Salvager output.
15703
15704 Time: During disk rebuilding.
15705
15706 Meaning: This indicates a logic error in the supervisor or
15707 CPU or memory hardware problems. The rebuild is
15708 aborted.
15709
15710 Action: Contact the system programming staff.
15711
15712
15713
15714
15715
15716
15717
15718
15719 disk_rebuild -271- MR12.5 10/27/92^L
15720
15721
15722 disk_rebuild.pl1
15723 disk_rebuild: reading vtocx XXXo: ERRORMESS
15724
15725
15726 Stream: Salvager output.
15727
15728 Time: During disk rebuilding.
15729
15730 Meaning: This indicates a logic error in the supervisor or
15731 CPU or memory hardware problems.
15732
15733 Action: Contact the system programming staff.
15734
15735
15736
15737 disk_rebuild.pl1
15738 disk_rebuild: salv cleanup debugging stop dump
15739 and type go
15740
15741
15742 Stream: BOS Typewriter Crashes system
15743
15744 Time: During disk rebuild
15745
15746 Meaning: A disk rebuild has aborted due to a crawlout and
15747 the debug switch is set. This message causes the
15748 system to return to BCE so that a dump can be
15749 taken.
15750
15751 Action: Follow programmer instructions.
15752
15753
15754
15755 disk_rebuild.pl1
15756 disk_rebuild: same drive specified for source and
15757 copy aborting
15758
15759
15760 Stream: Salvager output.
15761
15762 Time: During disk rebuilding
15763
15764 Meaning: The operator attempted to specify the same drive
15765 as input and output. No action was taken.
15766
15767 Action: Enter a corrected command.
15768
15769
15770
15771
15772
15773
15774
15775
15776
15777 disk_rebuild -272- MR12.5 10/27/92^L
15778
15779
15780 disk_rebuild.pl1
15781 disk_rebuild: Summary of original disk contents
15782 follows:
15783
15784
15785 Stream: Salvager output.
15786
15787 Time: During disk rebuilding.
15788
15789 Meaning: A summary report of the volume parameters before
15790 rebuilding is printed.
15791
15792 Action: No operator action is required.
15793
15794
15795
15796 disk_rebuild.pl1
15797 disk_rebuild: Summary Report
15798 Volume PVNAME of logical volume LVNAME.
15799
15800 Paging region begins at record DD. WWo for LL.
15801 XXo records.
15802 DD. WWo free records therein.
15803 Label/VTOC size is RR. records MM. VTOCEs.
15804 VTOC version X. TTT. free VTOCEs.
15805
15806 Partition Map
15807 Name Start Length
15808
15809 NAME DDD. WWWo DDD. WWWo
15810 ______ _______
15811 DDD. WWWo
15812
15813 Volume size is DDDD. YYYYo records total.
15814
15815 DD. damaged segments.
15816
15817
15818 Stream: Salvager output.
15819
15820 Time: During disk rebuilding.
15821
15822 Meaning: This is a report summarizing physical volume
15823 parameters printed by the disk rebuilder both
15824 before and after rebuilding. The partition map is
15825 omitted if no partitions are defined on the
15826 volume.
15827
15828 Action: No operator action is required.
15829
15830
15831
15832
15833
15834
15835 disk_rebuild -273- MR12.5 10/27/92^L
15836
15837
15838 disk_rebuild.pl1
15839 disk_rebuild: vtocx XXXo NAME branch unconnected
15840 due to YYYo
15841
15842
15843 Stream: Salvager output.
15844
15845 Time: During disk rebuilding.
15846
15847 Meaning: This is debugging output produced only if the
15848 debug switch is on during a disk rebuild with
15849 branch checking. It informs the system
15850 programmers of the reasons for connection failure.
15851
15852 Action: No operator action is required.
15853
15854
15855
15856 disk_table_.pl1
15857 disk_table_: "KEY" is not "io" "storage_system"
15858 or "ss".
15859
15860
15861 Stream: Initializer process output.
15862
15863 Time: While system is running.
15864
15865 Meaning: The operator issued an set_drive_usage DRIVE KEY
15866 command. KEY is invalid.
15867
15868 Action: Enter a corrected command line.
15869
15870
15871
15872 mdx.pl1
15873 disk_table_: accepted PV PVNAME on DSKX_NN
15874
15875
15876 Stream: Logged in SYSERR log.
15877
15878 Time: In response to an operator command. System
15879 Intialization.
15880
15881 Meaning: A storage system physical volume has been placed
15882 in use. The volume and drive name are identified.
15883
15884 Action: No operator action is required. This message is
15885 provided for the benefit of automatic error
15886 analysis and logging.
15887
15888
15889
15890
15891
15892
15893 disk_table_ -274- MR12.5 10/27/92^L
15894
15895
15896 mdx.pl1
15897 disk_table_: Added drive DSKX_NN
15898
15899
15900 Stream: BOS Typewriter.
15901
15902 Time: In response to an operator command.
15903
15904 Meaning: The operator has added a storage system disk drive
15905 with adddev.
15906
15907 Action: No operator action is required.
15908
15909
15910
15911 disk_table_.pl1
15912 disk_table_: cannot locate DRIVE
15913
15914
15915 Stream: Initializer process output.
15916
15917 Time: While system is running.
15918
15919 Meaning: A del_vol DRIVE command was issued but there is no
15920 such drive in the configuration.
15921
15922 Action: Enter a corrected command line.
15923
15924
15925
15926 disk_table_.pl1
15927 disk_table_: cannot locate DRIVE
15928
15929
15930 Stream: Initializer process output.
15931
15932 Time: While system is running.
15933
15934 Meaning: A command specifying DRIVE was issued but no such
15935 drive can be found.
15936
15937 Action: Enter a corrected command line.
15938
15939
15940
15941
15942
15943
15944
15945
15946
15947
15948
15949
15950
15951 disk_table_ -275- MR12.5 10/27/92^L
15952
15953
15954 disk_table_.pl1
15955 disk_table_: cannot locate DRIVE
15956
15957
15958 Stream: Initializer process output.
15959
15960 Time: While system is running.
15961
15962 Meaning: A disk_rebuild command cannot locate the output
15963 drive.
15964
15965 Action: Enter a corrected command line.
15966
15967
15968
15969 disk_table_.pl1
15970 disk_table_: cannot reregister from ring 4
15971
15972
15973 Stream: Initializer process output.
15974
15975 Time: While system is running.
15976
15977 Meaning: A reregister command was issued from ring 4.
15978
15979 Action: Enter a corrected command line.
15980
15981
15982
15983 disk_table_.pl1
15984 disk_table_: Cannot verify label of DRIVE:
15985 REASON
15986
15987
15988 Stream: Initializer process output.
15989
15990 Time: While system is running.
15991
15992 Meaning: An error occurred checking the label of DRIVE.
15993 Usually either the drive is not ready or the pack
15994 label does not match the required pack label.
15995
15996 Action: Enter a corrected command line.
15997
15998
15999
16000
16001
16002
16003
16004
16005
16006
16007
16008
16009 disk_table_ -276- MR12.5 10/27/92^L
16010
16011
16012 disk_table_.pl1
16013 disk_table_: Could not finish demount of lv
16014 LVNAME
16015
16016
16017 Stream: Initializer process output.
16018
16019 Time: While system is running.
16020
16021 Meaning: The system encountered a problem trying to delete
16022 the logical volume LVNAME.
16023
16024 Action: Contact the system programming staff.
16025
16026
16027
16028 mdx.pl1
16029 disk_table_: Deleted drive DSKX_NN
16030
16031
16032 Stream: BOS Typewriter.
16033
16034 Time: In response to an operator command.
16035
16036 Meaning: The operator has deleted a storage system disk
16037 drive with deldev.
16038
16039 Action: No operator action is required.
16040
16041
16042
16043 mdx.pl1
16044 disk_table_: Deleted root PV "PV_NAME" on
16045 DSKX_NN.
16046
16047
16048 Stream: BOS Typewriter sounds beeper
16049
16050 Time: System Intialization.
16051
16052 Meaning: The specified drive did not appear in the ROOT
16053 config card. Thus it was removed from the
16054 disk_table_. This will also occur when the volume
16055 is intentionally deleted.
16056
16057 Action: Contact the system programming staff.
16058
16059
16060
16061
16062
16063
16064
16065
16066
16067 disk_table_ -277- MR12.5 10/27/92^L
16068
16069
16070 disk_table_.pl1
16071 disk_table_: demounting partially mounted volume
16072 LVNAME
16073
16074
16075 Stream: Initializer process output.
16076
16077 Time: While system is running.
16078
16079 Meaning: The operator issued a dlv LVNAME command for a
16080 logical volume for which a previous dlv command
16081 did not succeed.
16082
16083 Action: No operator action is required.
16084
16085
16086
16087 disk_table_.pl1
16088 disk_table_: DRIVE in use with PVNAME
16089
16090
16091 Stream: Initializer process output.
16092
16093 Time: While system is running.
16094
16095 Meaning: A del_vol DRIVE command was issued but the drive
16096 is currently in use.
16097
16098 Action: Enter a corrected command line. To demount the
16099 pack use the dlv command.
16100
16101
16102
16103 disk_table_.pl1
16104 disk_table_: DRIVE in use: contains PVNAME
16105
16106
16107 Stream: Initializer process output.
16108
16109 Time: While system is running.
16110
16111 Meaning: An attempt to use DRIVE finds it already in use.
16112
16113 Action: Enter a corrected command line.
16114
16115
16116
16117
16118
16119
16120
16121
16122
16123
16124
16125 disk_table_ -278- MR12.5 10/27/92^L
16126
16127
16128 disk_table_.pl1
16129 disk_table_: DRIVE is an IO drive
16130
16131
16132 Stream: Initializer process output.
16133
16134 Time: While system is running.
16135
16136 Meaning: A command has been issued to affect DRIVE but it
16137 is currently in use as an IO drive.
16138
16139 Action: Enter a corrected command line. Use the
16140 set_drive_usage command to change it if necessary.
16141
16142
16143
16144 disk_table_.pl1
16145 disk_table_: DRIVE is deleted
16146
16147
16148 Stream: Initializer process output.
16149
16150 Time: While system is running.
16151
16152 Meaning: The drive named is deleted.
16153
16154 Action: Enter a corrected command line.
16155
16156
16157
16158 disk_table_.pl1
16159 disk_table_: DRIVE not found.
16160
16161
16162 Stream: Initializer process output.
16163
16164 Time: While system is running.
16165
16166 Meaning: The operator issued an set_drive_usage DRIVE KEY
16167 command but DRIVE is not in the current
16168 configuration.
16169
16170 Action: Enter a corrected command line.
16171
16172
16173
16174
16175
16176
16177
16178
16179
16180
16181
16182
16183 disk_table_ -279- MR12.5 10/27/92^L
16184
16185
16186 disk_table_.pl1
16187 disk_table_: DRIVE not in use.
16188
16189
16190 Stream: Initializer process output.
16191
16192 Time: While system is running.
16193
16194 Meaning: A del_vol command was issued but nothing is on the
16195 drive.
16196
16197 Action: Enter a corrected command line.
16198
16199
16200
16201 disk_table_.pl1
16202 disk_table_: DRIVENAME is an IO drive
16203
16204
16205 Stream: Initializer process output.
16206
16207 Time: While system is running.
16208
16209 Meaning: The operator issued a del_vol command but the
16210 drive is an IO drive.
16211
16212 Action: Enter a corrected command line.
16213
16214
16215
16216 disk_table_.pl1
16217 disk_table_: DRIVENAME is deleted
16218
16219
16220 Stream: Initializer process output.
16221
16222 Time: While system is running.
16223
16224 Meaning: A del_vol command was issued but the drive has
16225 been deleted.
16226
16227 Action: Enter a corrected command line.
16228
16229
16230
16231
16232
16233
16234
16235
16236
16237
16238
16239
16240
16241 disk_table_ -280- MR12.5 10/27/92^L
16242
16243
16244 disk_table_.pl1
16245 disk_table_: ERROR_MESSAGE.
16246
16247
16248 Stream: Initializer process output.
16249
16250 Time: System Intialization.
16251
16252 Meaning: An error has been returned from
16253 initializer_mdc_$init. This indicates a logic
16254 error in the supervisor or CPU or memory hardware
16255 problems. Subsequent attempts to mount volumes
16256 may malfunction.
16257
16258 Action: Contact the system programming staff.
16259
16260
16261
16262 disk_table_.pl1
16263 disk_table_: ERROR_MESSAGE.
16264
16265
16266 Stream: Initializer process output.
16267
16268 Time: While system is running.
16269
16270 Meaning: An error has occurred in a storage system disk
16271 manipulation command.
16272
16273 Action: Enter a corrected command line.
16274
16275
16276
16277 disk_table_.pl1
16278 disk_table_: ERROR_MESSAGE. Cannot demount lv
16279 LVNAME
16280
16281
16282 Stream: Initializer process output.
16283
16284 Time: While system is running.
16285
16286 Meaning: A dlv LVNAME command was issued but an error
16287 prevents the dlv from working.
16288
16289 Action: Enter a corrected command line.
16290
16291
16292
16293
16294
16295
16296
16297
16298
16299 disk_table_ -281- MR12.5 10/27/92^L
16300
16301
16302 disk_table_.pl1
16303 disk_table_: ERROR_MESSAGE. Cannot get volume
16304 registration for the root logical volume.
16305 Shutdown and reboot with "boot nolv".
16306
16307
16308 Stream: Initializer process output.
16309
16310 Time: System Intialization.
16311
16312 Meaning: The system is unable to read the volume
16313 registration for the root logical volume and
16314 cannot therefore determine if the root is
16315 complete.
16316
16317 Action: Shutdown. If you can mount the entire root do
16318 so describe all volumes on the root config card
16319 "boot stan nosc" and fix the registration. If
16320 this fails shutdown and "boot nolv".
16321
16322
16323
16324 disk_table_.pl1
16325 disk_table_: ERROR_MESSAGE. cannot stop mount of
16326 LVNAME
16327
16328
16329 Stream: Initializer process output.
16330
16331 Time: While system is running.
16332
16333 Meaning: A dlv LVNAME command was issued but an error
16334 prevents the dlv from working.
16335
16336 Action: Enter a corrected command line.
16337
16338
16339
16340 disk_table_.pl1
16341 disk_table_: ERROR_MESSAGE. Cannot verify label
16342 of DRIVE
16343
16344
16345 Stream: Initializer process output.
16346
16347 Time: While system is running.
16348
16349 Meaning: An error occurred checking the label of the pack
16350 on DRIVE. Usually either the drive is not ready
16351 or the pack label does not match the required pack
16352 label.
16353
16354 Action: Enter a corrected command line.
16355
16356
16357 disk_table_ -282- MR12.5 10/27/92^L
16358
16359
16360 disk_table_.pl1
16361 disk_table_: ERROR_MESSAGE. Could not demount pv
16362 PVNAME of lv LVNAME DRIVE
16363
16364
16365 Stream: Initializer process output.
16366
16367 Time: While system is running.
16368
16369 Meaning: An error occurred when trying to demount a
16370 physical volume. This may be due to process
16371 directory or wired segments being on this physical
16372 volume. The del_lv command will be partially
16373 successful when this happens.
16374
16375 Action: Determine which processes if any have process
16376 directories on this logical volume and bump or
16377 terminate them. Use list_disks to determine which
16378 volumes are still mounted and try dlv again.
16379 Contact the system programming staff.
16380
16381
16382
16383 disk_table_.pl1
16384 disk_table_: ERROR_MESSAGE. error reregistering
16385 DRIVE
16386
16387
16388 Stream: Initializer process output.
16389
16390 Time: While system is running.
16391
16392 Meaning: The reregister DRIVE command did not succeed.
16393
16394 Action: Enter a corrected command line.
16395
16396
16397
16398 disk_table_.pl1
16399 disk_table_: ERROR_MESSAGE. LVNAME
16400
16401
16402 Stream: Initializer process output.
16403
16404 Time: While system is running.
16405
16406 Meaning: An error occurred trying to get the list of
16407 physical volumes which comprise LVNAME.
16408
16409 Action: Enter a corrected command line.
16410
16411
16412
16413
16414
16415 disk_table_ -283- MR12.5 10/27/92^L
16416
16417
16418 disk_table_.pl1
16419 disk_table_: ERROR_MESSAGE. New disk_table
16420 created
16421
16422
16423 Stream: Initializer process output.
16424
16425 Time: System Intialization.
16426
16427 Meaning: The system has created a new copy of the segment
16428 >disk_table at initialization time. The copy from
16429 the previous bootload could not be found. The
16430 position of all previously mounted volumes has
16431 been forgotten.
16432
16433 Action: Use the av command to specify the position of all
16434 volumes and the alv command to mount them.
16435
16436
16437
16438 disk_table_.pl1
16439 disk_table_: ERROR_MESSAGE. salvaging PVNAME on
16440 DRIVE
16441
16442
16443 Stream: Initializer process output.
16444
16445 Time: While system is running.
16446
16447 Meaning: An error occurred while doing a salvage_vol -all.
16448
16449 Action: Enter a corrected command line.
16450
16451
16452
16453 disk_table_.pl1
16454 disk_table_: invalid drive id "ARG"
16455
16456
16457 Stream: Initializer process output.
16458
16459 Time: While system is running.
16460
16461 Meaning: The drive id ARG does not have the form dskX_NN.
16462
16463 Action: Enter a corrected command line.
16464
16465
16466
16467
16468
16469
16470
16471
16472
16473 disk_table_ -284- MR12.5 10/27/92^L
16474
16475
16476 disk_table_.pl1
16477 disk_table_: lv LVNAME cannot be mounted in
16478 process of demount.
16479
16480
16481 Stream: Initializer process output.
16482
16483 Time: While system is running.
16484
16485 Meaning: An alv LVNAME command was issued but the logical
16486 volume is in the process of demounting.
16487
16488 Action: Enter a corrected command line.
16489
16490
16491
16492 disk_table_.pl1
16493 disk_table_: lv LVNAME already mounted
16494
16495
16496 Stream: Initializer process output.
16497
16498 Time: While system is running.
16499
16500 Meaning: An alv LVNAME command finds LVNAME already
16501 mounted.
16502
16503 Action: Enter a corrected command line.
16504
16505
16506
16507 disk_table_.pl1
16508 disk_table_: lv LVNAME not found
16509
16510
16511 Stream: Initializer process output.
16512
16513 Time: While system is running.
16514
16515 Meaning: A dlv LVNAME command was issued but no such
16516 logical volume is mounted.
16517
16518 Action: Enter a corrected command line.
16519
16520
16521
16522
16523
16524
16525
16526
16527
16528
16529
16530
16531 disk_table_ -285- MR12.5 10/27/92^L
16532
16533
16534 disk_table_.pl1
16535 disk_table_: no drive available for PVNAME LVNAME
16536
16537
16538 Stream: Initializer process output.
16539
16540 Time: While system is running.
16541
16542 Meaning: An alv LVNAME command was unable to allocate a
16543 drive for PVNAME.
16544
16545 Action: Demount some un-needed logical volume and try
16546 again.
16547
16548
16549
16550 disk_table_.pl1
16551 disk_table_: PVNAME already in use on DRIVE.
16552
16553
16554 Stream: Initializer process output.
16555
16556 Time: While system is running.
16557
16558 Meaning: An attempt to add a physical volume finds the
16559 volume already in use on another drive.
16560
16561 Action: Enter a corrected command line.
16562
16563
16564
16565 disk_table_.pl1
16566 disk_table_: PVNAME currently known to be on
16567 DRIVE
16568
16569
16570 Stream: Initializer process output.
16571
16572 Time: While system is running.
16573
16574 Meaning: An attempt to specify that PVNAME is on a certain
16575 drive finds it on another drive.
16576
16577 Action: Enter a corrected command line. Use the del_vol
16578 command if necessary to cause the system to forget
16579 DRIVE's old contents if a pack has been moved.
16580
16581
16582
16583
16584
16585
16586
16587
16588
16589 disk_table_ -286- MR12.5 10/27/92^L
16590
16591
16592 disk_table_.pl1
16593 disk_table_: PVNAME not found.
16594
16595
16596 Stream: Initializer process output.
16597
16598 Time: While system is running.
16599
16600 Meaning: An initialize_disk -copy command could not find
16601 the source volume.
16602
16603 Action: Enter a corrected command line.
16604
16605
16606
16607 mdx.pl1
16608 disk_table_: Root PV "PV_NAME" moved from DSKX_NN
16609 to DSKX_NN.
16610
16611
16612 Stream: BOS Typewriter.
16613
16614 Time: System Intialization.
16615
16616 Meaning: The specified root volume has been moved to a
16617 different drive since the last shutdown.
16618
16619 Action: No operator action is required.
16620
16621
16622
16623 disk_table_.pl1
16624 disk_table_: Some volumes are incomplete.
16625 Complete or demount them.
16626
16627
16628 Stream: Initializer process output.
16629
16630 Time: System Intialization.
16631
16632 Meaning: Initialization has failed to remount all the
16633 volumes which were previously known in response
16634 to a startup command.
16635
16636 Action: Use the list_disks command to find out which
16637 volumes are incomplete. Use the av or dlv
16638 commands to rectify the situation and try startup
16639 again.
16640
16641
16642
16643
16644
16645
16646
16647 disk_table_ -287- MR12.5 10/27/92^L
16648
16649
16650 disk_table_.pl1
16651 disk_table_: The root logical volume is
16652 incomplete.
16653
16654
16655 Stream: Initializer process output.
16656
16657 Time: System Intialization.
16658
16659 Meaning: Some registered physical volumes of the root
16660 logical volume are not mounted but the operator
16661 has attempted to execute a command that requires
16662 the root to be completely mounted. This message
16663 is followed by mount messages for the missing
16664 volumes.
16665
16666
16667 Action: Mount the missing volumes and notify the system
16668 of their location with the add_vol command.
16669
16670
16671
16672 dn355.pl1
16673 dn355: attempted crawlout with FNP queue locked
16674
16675
16676 Stream: BOS Typewriter Crashes system
16677
16678 Time: While system is running.
16679
16680 Meaning: An attempt was made to crawl out while an FNP
16681 queue lock a processor lock was locked.
16682
16683 Action: Contact the system programming staff.
16684
16685
16686
16687
16688
16689
16690
16691
16692
16693
16694
16695
16696
16697
16698
16699
16700
16701
16702
16703
16704
16705 dn355 -288- MR12.5 10/27/92^L
16706
16707
16708 dn355.pl1
16709 dn355: emergency interrupt from FNP X: FAULT
16710 FNP instruction counter = IC
16711 channel CHN fault status = FS
16712 FNP_MODULE: REASON_FOR_CRASH
16713
16714
16715 Stream: BOS Typewriter sounds beeper
16716
16717 Time: While system is running.
16718
16719 Meaning: An emergency interrupt has been received from FNP
16720 X indicating it has crashed. All lines dialed to
16721 FNP X will be hung up. The crash was nominally
16722 caused by a fault of type FAULT. Lines following
16723 the first line of the message appear only in
16724 certain cases and provide additional information
16725 about the nature of the crash.
16726
16727 Action: The system will automatically attempt to reboot
16728 the crashed FNP. Subsequent messages will
16729 indicate the success or failure of this attempt.
16730 No action is required now but action may be
16731 required if the automatic reboot fails.
16732
16733
16734
16735 dn355.pl1
16736 dn355: Error sending mailbox interrupt to FNP X
16737 will retry.
16738
16739
16740 Stream: BOS Typewriter.
16741
16742 Time: While system is running.
16743
16744 Meaning: An error has been detected in the transmission of
16745 a mailbox interrupt to the FNP. The transmission
16746 will be retried once.
16747
16748 Action: None required.
16749
16750
16751
16752
16753
16754
16755
16756
16757
16758
16759
16760
16761
16762
16763 dn355 -289- MR12.5 10/27/92^L
16764
16765
16766 dn355.pl1
16767 dn355: FNP masked channel NAME for excessive
16768 interrupts
16769
16770
16771 Stream: BOS Typewriter.
16772
16773 Time: While system is running.
16774
16775 Meaning: The FNP has masked the channel whose name is NAME
16776 because it was generating interrupts faster than
16777 they could be handled.
16778
16779 Action: The interruptions can be caused by any number of
16780 problems. This can be caused by the dataset leads
16781 changing too fast for the FNP software to handle
16782 properly; disconnecting or connecting FNP cables
16783 powering off or on a hardwired terminal a bad
16784 modem etc. It is also possible that the FNP
16785 channel hardware is defective. Future attempts to
16786 use this channel may possibly crash the FNP. CS
16787 representatives may need to be called to
16788 investigate. An "attach" command will be
16789 necessary to put the channel back in service.
16790
16791
16792
16793 dn355.pl1
16794 dn355: FNP X did not respond to mailbox interrupt
16795
16796
16797 Stream: BOS Typewriter sounds beeper
16798
16799 Time: While system is running.
16800
16801 Meaning: An attempt to interrupt FNP X was unsuccessful.
16802 The FNP is assumed to be down.
16803
16804 Action: The system will automatically attempt to reboot
16805 the crashed FNP. Subsequent messages will
16806 indicate the success or failure of this attempt.
16807 No action is required now but action may be
16808 required if the automatic reboot fails.
16809
16810
16811
16812
16813
16814
16815
16816
16817
16818
16819
16820
16821 dn355 -290- MR12.5 10/27/92^L
16822
16823
16824 dn355.pl1
16825 dn355: FNP X invalid interrupt level N
16826
16827
16828 Stream: BOS Typewriter sounds beeper
16829
16830 Time: While system is running.
16831
16832 Meaning: An FNP interrupt has been received from frontend X
16833 with an invalid interrupt level of octal value N
16834 and will be ignored. If this message is displayed
16835 when a DN6670 is being powered up this message
16836 can be ignored. If this message occurs under any
16837 other circumstances there might be something
16838 wrong with the system's interface with the FNP and
16839 should be investigated by FE representatives.
16840
16841 Action: Contact the system programming staff.
16842
16843
16844
16845 dn355.pl1
16846 dn355: FNP X level L status S STATE
16847
16848
16849 Stream: BOS Typewriter.
16850
16851 Time: While system is running.
16852
16853 Meaning: An interrupt at a level other than 3 or possibly
16854 at level 3 if the FNP is not running was received
16855 from FNP X. S is an octal representation of the
16856 status accompanying the interrupt. STATE
16857 indicates the current state of the FNP: running
16858 bootloading or in T&D. This message only appears
16859 if tracing is enabled for the specified FNP.
16860
16861 Action: None required.
16862
16863
16864
16865 dn355.pl1
16866 dn355: inconsistent queue lock
16867
16868
16869 Stream: BOS Typewriter Crashes system
16870
16871 Time: While system is running.
16872
16873 Meaning: A process attempted to unlock the interrupt queue
16874 lock without having it locked.
16875
16876 Action: Contact the system programming staff.
16877
16878
16879 dn355 -291- MR12.5 10/27/92^L
16880
16881
16882 dn355.pl1
16883 dn355: LCTE lock ^= processid
16884
16885
16886 Stream: BOS Typewriter Crashes system
16887
16888 Time: While system is running.
16889
16890 Meaning: The FNP channel lock did not contain the processid
16891 of the process attempting to unlock it.
16892
16893
16894
16895 dn355.pl1
16896 dn355: line number of 0 with non-global opcode in
16897 submbx N FNP X
16898
16899
16900 Stream: BOS Typewriter sounds beeper
16901
16902 Time: While system is running.
16903
16904 Meaning: Mailbox N from FNP X contained a non-global opcode
16905 which requires a non-zero line number.
16906
16907
16908
16909 dn355.pl1
16910 dn355: Message from FNP X: MESSAGE
16911
16912
16913 Stream: BOS Typewriter.
16914
16915 Time: While system is running.
16916
16917 Meaning: An error has been detected by FNP X as explained
16918 by MESSAGE.
16919
16920 Action: No action is required by the operator to deal with
16921 the error mentioned in the message. Action may be
16922 required by appropriate personnel to correct the
16923 problem that caused the error and undo what the
16924 FNP may have done to continue operation. This may
16925 require shutting down the FNP for repairs by Field
16926 Engineering and reboot of the FNP to restore full
16927 operation.
16928
16929
16930
16931
16932
16933
16934
16935
16936
16937 dn355 -292- MR12.5 10/27/92^L
16938
16939
16940 dn355.pl1
16941 dn355: no slot number match for sub mbx N FNP X
16942
16943
16944 Stream: BOS Typewriter sounds beeper
16945
16946 Time: While system is running.
16947
16948 Meaning: An error has occurred processing submailbox N for
16949 FNP X. The submailbox indicates a line number for
16950 which no match could be found.
16951
16952 Action: Contact the system programming staff.
16953
16954
16955
16956 dn355.pl1
16957 dn355: output buffer at N has zero tally
16958
16959
16960 Stream: BOS Typewriter Crashes system
16961
16962 Time: While system is running.
16963
16964 Meaning: An output buffer with a zero tally has been found
16965 at offset N in the segment tty_buf.
16966
16967 Action: Contact the system programming staff.
16968
16969
16970
16971 dn355.pl1
16972 dn355: Timeout sending mailbox interrupt to FNP
16973 X will retry.
16974
16975
16976 Stream: BOS Typewriter.
16977
16978 Time: While system is running.
16979
16980 Meaning: The FNP did not respond within 2 seconds to the
16981 previously sent mailbox interrupt. The
16982 transmission will be retried once.
16983
16984 Action: None required.
16985
16986
16987
16988
16989
16990
16991
16992
16993
16994
16995 dn355 -293- MR12.5 10/27/92^L
16996
16997
16998 dn355.pl1
16999 dn355: unable to allocate block for delay queue
17000
17001
17002 Stream: BOS Typewriter Crashes system
17003
17004 Time: While system is running.
17005
17006 Meaning: There was insufficient space left in tty_buf to
17007 allocate a block in which to build a delay queue.
17008
17009 Action: Contact the system programming staff.
17010
17011
17012
17013 dn355.pl1
17014 dn355: unrecognized io command C from FNP X for
17015 line N
17016
17017
17018 Stream: BOS Typewriter sounds beeper
17019
17020 Time: While system is running.
17021
17022 Meaning: An invalid io command was received from FNP X for
17023 line N. C is the octal representation of the
17024 command.
17025
17026 Action: Contact the system programming staff.
17027
17028
17029
17030 dn355.pl1
17031 dn355: unrecognized op code OPCODE with rcd from
17032 FNP X for devx N
17033
17034
17035 Stream: BOS Typewriter sounds beeper
17036
17037 Time: While system is running.
17038
17039 Meaning: An invalid op code OPCODE has been received from
17040 FNP X for device index N in a mailbox containing
17041 an rcd read control data command.
17042
17043 Action: Contact the system programming staff.
17044
17045
17046
17047
17048
17049
17050
17051
17052
17053 dn355 -294- MR12.5 10/27/92^L
17054
17055
17056 dpg_.pl1
17057 dpg_: COND condition signalled while copying
17058 stack_0 into >pdd>DIRNAME
17059
17060
17061 Stream: as severity0
17062
17063 Time: While system is running.
17064
17065 Meaning: An error occurred while copying the ring-0 stack
17066 of the defunct process from ring-0 into the saved
17067 process directory. This error caused the COND
17068 condition to be signalled. The ring-0 stack will
17069 not be copied into the saved process directory.
17070
17071 Action: No operator action is required.
17072
17073
17074
17075 dpg_.pl1
17076 dpg_: ERROR_MESSAGE. Attempting to rename pdir
17077 for NAME.PROJ CHN after fatal process error.
17078
17079
17080 Stream: as severity1
17081
17082 Time: While system is running.
17083
17084 Meaning: The error described by ERROR_MESSAGE occurred
17085 while attempting to save the process directory
17086 belonging to the user PERS.PROJ after a fatal
17087 process error. The directory was not saved. A
17088 typical cause of this is that the user already has
17089 a saved process directory from a previous fatal
17090 process error in this bootload.
17091
17092 Action: Contact the system programming staff.
17093
17094
17095
17096
17097
17098
17099
17100
17101
17102
17103
17104
17105
17106
17107
17108
17109
17110
17111 dpg_ -295- MR12.5 10/27/92^L
17112
17113
17114 dpg_.pl1
17115 dpg_: ERROR_MESSAGE. Calling
17116 hphcs_$destroy_process_begin for
17117 PERSON.PROJECT.TAG on channel CHN process_id PID.
17118
17119
17120 Stream: $as1
17121
17122 Time: While system is running.
17123
17124 Meaning: An error has occurred while destroying a process
17125 belonging to the user PERSON.PROJECT.TAG connected
17126 to terminal channel CHN. This process probably
17127 cannot be destroyed. ERROR_MESSAGE is the text
17128 associated with the error returned by
17129 hphcs_$destroy_process_begin.
17130
17131 Action: Contact the system programming staff.
17132
17133
17134
17135 dpg_.pl1
17136 dpg_: ERROR_MESSAGE. Creating saved stack_0 for
17137 PERS.PROJ PROCESSID.
17138
17139
17140 Stream: as severity0
17141
17142 Time: While system is running.
17143
17144 Meaning: An error has occurred while attempting to create a
17145 segment in the saved process directory for copying
17146 the ring-0 stack of the defunct process. The
17147 ring-0 stack will not be copied into the saved
17148 process directory.
17149
17150 Action: No operator action is required.
17151
17152
17153
17154
17155
17156
17157
17158
17159
17160
17161
17162
17163
17164
17165
17166
17167
17168
17169 dpg_ -296- MR12.5 10/27/92^L
17170
17171
17172 dpg_.pl1
17173 dpg_: ERROR_MESSAGE. destroying process
17174 WWWWWWWWWWWW for NAME.PROJ
17175
17176
17177 Stream: as severity2
17178
17179 Time: While system is running.
17180
17181 Meaning: An error has occurred while destroying a process
17182 belonging to the user NAME.PROJ. He was not
17183 charged for his CPU usage.
17184
17185 Action: Contact the system programming staff.
17186
17187
17188
17189 dpg_.pl1
17190 dpg_: removed USER PROCESSID process
17191 termination monitor.
17192
17193
17194 Stream: as severity0
17195
17196 Time: While system is running.
17197
17198 Meaning: Process termination monitoring for USER process
17199 id PROCESSID has been terminated by user request
17200 IPC error or the destruction of the process.
17201
17202 Action: No operator action is required.
17203
17204
17205
17206 dpg_.pl1
17207 dpg_: Saved >pdd>PERS.PROJ.f.CHN after fatal
17208 process error.
17209
17210
17211 Stream: as severity1
17212
17213 Time: While system is running.
17214
17215 Meaning: The process directory belonging to user PERS.PROJ
17216 has been saved after a fatal process error. It
17217 has been renamed to the name shown in the message.
17218 It will be saved until the next shutdown. System
17219 programmers might want to examine its contents to
17220 determine the cause of the fatal process error.
17221
17222 Action: Inform the system programming staff. Do so well
17223 in advance of the next shutdown.
17224
17225
17226
17227 dpg_ -297- MR12.5 10/27/92^L
17228
17229
17230 dpg_.pl1
17231 dpg_: USER PROCESSID set/replaced process
17232 termination monitor.
17233
17234
17235 Stream: as severity0
17236
17237 Time: While system is running.
17238
17239 Meaning: USER processid PROCESSID will receive
17240 notifications of all process destructions from the
17241 Answering Service. 'set' indicates that the
17242 process was not already monitoring processes;
17243 'replaced' indicates that the process already had
17244 a monitor established and that it has been
17245 replaced by this request.
17246
17247 Action: No operator action is required.
17248
17249
17250
17251 wired_shutdown.pl1
17252 emergency shutdown part 1 complete
17253
17254
17255 Stream: BOS Typewriter.
17256
17257 Time: Emergency shutdown
17258
17259 Meaning: All of memory has been written out once and those
17260 pages on the paging device which could be written
17261 out to operative drives flushed. All segments and
17262 directories will now be deactivated and all
17263 drives shut down.
17264
17265 Action: No operator action is required.
17266
17267
17268
17269
17270
17271
17272
17273
17274
17275
17276
17277
17278
17279
17280
17281
17282
17283
17284
17285 emergency shutdown part 1 -298- MR12.5 10/27/92^L
17286
17287
17288 dn355_boot_interrupt.pl1
17289 error reading core image for FNP X
17290
17291
17292 Stream: BOS Typewriter.
17293
17294 Time: When bootloading an FNP
17295
17296 Meaning: An I/O error was detected by the FNP bootload
17297 program while attempting to read the core image
17298 into FNP memory. A hardware failure of either the
17299 DIA or the Multics IOM is indicated.
17300
17301 Action: Try the FNP load again. If it fails again
17302 consult Field Engineering.
17303
17304
17305
17306 mrd_util_.pl1
17307 Error: CONDITION in mrd_util_$ENTRY
17308
17309
17310 Stream: BOS Typewriter sounds beeper
17311
17312 Time: While system is running.
17313
17314 Meaning: CONDITION was signalled during a call to the
17315 entrypoint ENTRY in mrd_util_. A message
17316 coordinator dump is taken. If the calling process
17317 had a message coordinator segment locked that
17318 segment is checked for consistency and the lock
17319 is unlocked. mrd_util_ then returns to its caller
17320 without retrying the operation that failed. This
17321 indicates a logic error in the supervisor or CPU
17322 or memory hardware problems.
17323
17324 Action: Contact the system programming staff. Save all
17325 console and message coordinator terminal output.
17326
17327
17328
17329
17330
17331
17332
17333
17334
17335
17336
17337
17338
17339
17340
17341
17342
17343 Error -299- MR12.5 10/27/92^L
17344
17345
17346 wired_shutdown.pl1
17347 esd before fs enabled
17348
17349
17350 Stream: BOS Typewriter.
17351
17352 Time: Emergency shutdown
17353
17354 Meaning: The system crashed before the storage system was
17355 accessed by Multics. An ESD was attempted but no
17356 ESD is necessary. The "shutdown complete" message
17357 will always follow.
17358
17359 Action: Reboot the system.
17360
17361
17362
17363 page_error.alm
17364 evict_page: fatal parity error moving page frame
17365 at AAA SCU TAG.
17366
17367
17368 Stream: BOS Typewriter Crashes system
17369
17370 Time: While system is running.
17371
17372 Meaning: A parity error was encountered while moving a
17373 wired page around memory. The page may not be
17374 usable.
17375
17376 Action: Contact Field Engineering personnel about possible
17377 problems with SCU TAG. Follow normal recovery
17378 procedures.
17379
17380
17381
17382 page_error.alm
17383 evict_page: parity error moving page frame at
17384 AAA SCU TAG.
17385
17386
17387 Stream: BOS Typewriter.
17388
17389 Time: While system is running.
17390
17391 Meaning: A parity error was encountered while moving a page
17392 within main memory. This may occur as part of an
17393 attempt to delete that main memory or use it as
17394 an I/O buffer.
17395
17396 Action: Inform Field Engineering personnel about possible
17397 problems with this SCU.
17398
17399
17400
17401 evict_page -300- MR12.5 10/27/92^L
17402
17403
17404 find_file_partition.pl1
17405 find_file_partition: file partition is NNN
17406 records not between 30 and 255.
17407
17408
17409 Stream: BOS Typewriter Crashes system
17410
17411 Time: System Intialization.
17412
17413 Meaning: The partition holding the bce file system is of an
17414 invalid size. The rpv was either mal-formatted or
17415 damaged.
17416
17417 Action: The rpv will need to be rebuilt.
17418
17419
17420
17421 find_file_partition.pl1
17422 find_file_partition: Initting file partition.
17423
17424
17425 Stream: BOS Typewriter.
17426
17427 Time: System Intialization.
17428
17429 Meaning: The bce file system was found to be damaged or
17430 never initialized. Any previous contents are
17431 discarded.
17432
17433
17434
17435 find_file_partition.pl1
17436 find_file_partition: No file partition defined on
17437 RPV.
17438
17439
17440 Stream: BOS Typewriter Crashes system
17441
17442 Time: System Intialization.
17443
17444 Meaning: The partition used to hold the bce file system is
17445 missing from the rpv. Suspect damage of the rpv.
17446
17447 Action: The rpv will need to be rebuilt.
17448
17449
17450
17451 fnp_util.pl1
17452 FNP T deleted from configuration^ by ^a^.
17453
17454
17455
17456
17457
17458
17459 FNP T deleted from configu -301- MR12.5 10/27/92^L
17460
17461
17462 dn355_boot_interrupt.pl1
17463 FNP X loaded successfully
17464
17465
17466 Stream: BOS Typewriter.
17467
17468 Time: When bootloading an FNP
17469
17470 Meaning: The FNP bootload has completed successfully.
17471
17472 Action: This message is for informational purposes only.
17473
17474
17475
17476 dn355_boot_interrupt.pl1
17477 FNP X not loaded.
17478
17479
17480 Stream: BOS Typewriter.
17481
17482 Time: When bootloading an FNP
17483
17484 Meaning: The attempted bootload was not successful. This
17485 message is always preceded by one of the above
17486 error messages.
17487
17488 Action: This message is for informational purposes only.
17489
17490
17491
17492 fnp_init.pl1
17493 fnp_init: FNP number N > max allowed number MAX
17494 of FNPs
17495
17496
17497 Stream: BOS Typewriter Crashes system
17498
17499 Time: System Intialization.
17500
17501 Meaning: An fnp card from the config deck specifies an FNP
17502 tag other than A B C D E F G or H.
17503
17504 Action: Replace the bad fnp card and reboot.
17505
17506
17507
17508
17509
17510
17511
17512
17513
17514
17515
17516
17517 fnp_init -302- MR12.5 10/27/92^L
17518
17519
17520 fnp_init.pl1
17521 fnp_init: inconsistent fnp cards.
17522
17523
17524 Stream: BOS Typewriter Crashes system
17525
17526 Time: System Intialization.
17527
17528 Meaning: Two or more fnp cards from the config deck specify
17529 the same FNP tag.
17530
17531 Action: Replace or remove the bad fnp cards and reboot.
17532
17533
17534
17535 fnp_init.pl1
17536 fnp_init: Invalid model # MODELN on prph fnpX
17537 card.
17538
17539
17540 Stream: BOS Typewriter Crashes system
17541
17542 Time: System Intialization.
17543
17544 Meaning: The current fnp model number MODELN is not a
17545 supported number.
17546
17547 Action: Contact the system programming staff.
17548
17549
17550
17551 fnp_init.pl1
17552 fnp_init: Invalid state on prph fnpX card.
17553
17554
17555 Stream: BOS Typewriter Crashes system
17556
17557 Time: System Intialization.
17558
17559 Meaning: The only valid states are "on" or "off".
17560
17561 Action: Contact the system programming staff.
17562
17563
17564
17565
17566
17567
17568
17569
17570
17571
17572
17573
17574
17575 fnp_init -303- MR12.5 10/27/92^L
17576
17577
17578 fnp_init.pl1
17579 fnp_init: Less than 256 words of free space in
17580 tty_buf: N
17581
17582
17583 Stream: BOS Typewriter Crashes system
17584
17585 Time: System Intialization.
17586
17587 Meaning: Only N words of free space remain in tty_buf after
17588 allocating the header and circular queue. A
17589 minimum of 256 words is required and ordinarily
17590 more free space is desirable. Either the size of
17591 tty_buf as specified by the PARM TTYB config
17592 card must be increased or the circular queue
17593 size as specified by the PARM TTYQ config card
17594 must be decreased.
17595
17596 Action: Correct the config deck and reboot the system.
17597
17598
17599
17600 fnp_init.pl1
17601 fnp_init: no fnp cards in config deck
17602
17603
17604 Stream: BOS Typewriter.
17605
17606 Time: System Intialization.
17607
17608 Meaning: There are no fnp cards in the config deck and
17609 therefore no FNP will be initialized. Usually
17610 this indicates an error although it is possible
17611 to run Multics without an FNP.
17612
17613 Action: If an FNP is wanted reboot the system with an
17614 appropriate config deck.
17615
17616
17617
17618 fnp_init.pl1
17619 fnp_init: The number of configured protocol
17620 channels of N exceeds the maximum allowed of N.
17621
17622
17623 Stream: BOS Typewriter Crashes system
17624
17625 Time: System Intialization.
17626
17627 Meaning: The prot parm from the config deck specifies too
17628 many protocol channels.
17629
17630 Action: Contact the system programming staff.
17631
17632
17633 fnp_init -304- MR12.5 10/27/92^L
17634
17635
17636 fnp_init.pl1
17637 fnp_init: Unable to abs_wire tty_buf.
17638 ERROR_CODE_MESSAGE
17639
17640
17641 Stream: BOS Typewriter Crashes system
17642
17643 Time: System Intialization.
17644
17645 Meaning: The call to allocate memory in the bootload memory
17646 controller for tty_buf failed.
17647
17648 Action: Contact the system programming staff.
17649
17650
17651
17652 fnp_multiplexer.pl1
17653 fnp_multiplexer$assign_channel: Assignment of FNP
17654 X succeeded | failed.
17655
17656
17657 Stream: BOS Typewriter.
17658
17659 Time: While system is running.
17660
17661 Meaning: Indicates the result of a call to
17662 io_manager$assign for FNP X. This message only
17663 appears if tracing is enabled for the specified
17664 FNP.
17665
17666 Action: none required.
17667
17668
17669
17670 fnp_multiplexer.pl1
17671 fnp_multiplexer$ENTRY: Tracing call.
17672
17673
17674 Stream: BOS Typewriter.
17675
17676 Time: While system is running.
17677
17678 Meaning: A call was made to the ENTRY entry. This message
17679 only appears if tracing is enabled for the
17680 specified FNP.
17681
17682 Action: none required.
17683
17684
17685
17686
17687
17688
17689
17690
17691 fnp_multiplexer$ENTRY -305- MR12.5 10/27/92^L
17692
17693
17694 fnp_multiplexer.pl1
17695 fnp_multiplexer$ENTRY: Tracing error. ERROR.
17696
17697
17698 Stream: BOS Typewriter.
17699
17700 Time: While system is running.
17701
17702 Meaning: The error code represented by ERROR was
17703 encountered by ENTRY. This message only appears
17704 if tracing is enabled for the specified FNP.
17705
17706 Action: none required.
17707
17708
17709
17710 fnp_multiplexer.pl1
17711 fnp_multiplexer$shutdown: Called with FNP wired.
17712
17713
17714 Stream: BOS Typewriter.
17715
17716 Time: While system is running.
17717
17718 Meaning: A call was made to the shutdown entry while the
17719 pages for I/O for an FNP were still wired. This
17720 message only appears if tracing is enabled for the
17721 specified FNP.
17722
17723 Action: none required.
17724
17725
17726
17727 fnp_multiplexer.pl1
17728 fnp_multiplexer$shutdown: Called with null
17729 fnp_ptr
17730
17731
17732 Stream: BOS Typewriter.
17733
17734 Time: While system is running.
17735
17736 Meaning: A call was made to the shutdown entry with a null
17737 pointer to fnp_info. This message only appears if
17738 tracing is enabled for the specified FNP.
17739
17740 Action: Contact the system programming staff.
17741
17742
17743
17744
17745
17746
17747
17748
17749 fnp_multiplexer$shutdown -306- MR12.5 10/27/92^L
17750
17751
17752 fnp_multiplexer.pl1
17753 fnp_multiplexer$shutdown: Failed to unwire fnp.
17754 ERROR.
17755
17756
17757 Stream: BOS Typewriter.
17758
17759 Time: While system is running.
17760
17761 Meaning: An attempt to unwire the pages used for I/O to an
17762 FNP failed at FNP shutdown. ERROR contains the
17763 message derived from a standard system error code.
17764
17765 Action: Contact the system programming staff.
17766
17767
17768
17769 fnp_multiplexer.pl1
17770 fnp_multiplexer$unassign_channel: Unassignment of
17771 FNP X succeeded | failed.
17772
17773
17774 Stream: BOS Typewriter.
17775
17776 Time: While system is running.
17777
17778 Meaning: Indicates the result of a call to
17779 io_manager$unassign for FNP X. This message only
17780 appears if tracing is enabled for the specified
17781 FNP.
17782
17783 Action: none required.
17784
17785
17786
17787 fnp_multiplexer.pl1
17788 fnp_multiplexer: debugging stop type go to
17789 continue.
17790
17791
17792 Stream: BOS Typewriter Crashes system
17793
17794 Time: While system is running.
17795
17796 Meaning: An error has been encountered in setting up an
17797 FNP and debugging mode is turned on.
17798
17799 Action: Use BCE commands to analyze the condition if
17800 necessary; type "go" to resume system operation.
17801
17802
17803
17804
17805
17806
17807 fnp_multiplexer -307- MR12.5 10/27/92^L
17808
17809
17810 fnp_multiplexer.pl1
17811 fnp_multiplexer: get_meters order for FNP X line
17812 N timed out.
17813
17814
17815 Stream: BOS Typewriter.
17816
17817 Time: While system is running.
17818
17819 Meaning: A get_meters order for line N of FNP X failed to
17820 complete within 10 seconds. The buffer space
17821 associated with the order has been abandoned and
17822 get_meters dump and patch orders to that FNP are
17823 disabled until the FNP is reloaded.
17824
17825
17826
17827 fnp_multiplexer.pl1
17828 fnp_multiplexer: mylock error
17829
17830
17831 Stream: BOS Typewriter Crashes system
17832
17833 Time: While system is running.
17834
17835 Meaning: An attempt has been made to lock an FNP channel
17836 lock to a process that already has it locked.
17837
17838 Action: Contact the system programming staff.
17839
17840
17841
17842 fnp_multiplexer.pl1
17843 fnp_multiplexer: NAME order to FNP X timed out.
17844
17845
17846 Stream: BOS Typewriter.
17847
17848 Time: While system is running.
17849
17850 Meaning: NAME is "get_meters" "dump_fnp" or "patch_fnp".
17851 The named order to FNP X failed to complete within
17852 10 seconds. The buffer space associated with the
17853 order has been abandoned and get_meters dump
17854 and patch orders to that FNP are disabled until
17855 the FNP is reloaded.
17856
17857 Action: Contact the system programming staff.
17858
17859
17860
17861
17862
17863
17864
17865 fnp_multiplexer -308- MR12.5 10/27/92^L
17866
17867
17868 fnp_multiplexer.pl1
17869 fnp_multiplexer: patching FNP X for USER: ADDR
17870 from XXX to YYY
17871
17872
17873 Stream: BOS Typewriter.
17874
17875 Time: While system is running.
17876
17877 Meaning: The memory of FNP X is being patched by the
17878 privileged user whose user_id is USER. ADDR is
17879 the absolute location in FNP memory that is being
17880 patched in octal; XXX and YYY are the old and
17881 new values of the location respectively also in
17882 octal. The second line may be repeated with
17883 different values if more than one word is being
17884 patched.
17885
17886 Action: This information is for logging purposes.
17887
17888
17889
17890 fnp_util.pl1
17891 fnp_util$configure: FNP T already configured.
17892
17893
17894
17895
17896
17897
17898 fnp_util.pl1
17899 fnp_util$ENTRY: Debugging stop type go to
17900 continue.
17901
17902
17903
17904
17905
17906
17907 fnp_util.pl1
17908 fnp_util$ENTRY: Invalid call for FNP INDEX. not
17909 in cdeck
17910
17911
17912
17913
17914
17915
17916 fnp_util.pl1
17917 fnp_util$ENTRY: Invalid call. trace
17918
17919
17920
17921
17922
17923 fnp_util$ENTRY -309- MR12.5 10/27/92^L
17924
17925
17926 fnp_util.pl1
17927 fnp_util$ENTRY: Tracing call for fnp T.
17928
17929
17930
17931
17932
17933
17934 fnp_util.pl1
17935 fnp_util$fdump_seg_io: IO_OP for CALLER trace
17936
17937
17938
17939
17940
17941
17942 fnp_util.pl1
17943 fnp_util$load: Error loading FNP T. REASON
17944 trace
17945
17946
17947
17948
17949
17950
17951 fnp_util.pl1
17952 fnp_util$load: FNP load already in progress for
17953 FNP T.
17954
17955
17956
17957
17958
17959
17960 fnp_util.pl1
17961 fnp_util$load: FNP T is running T&D.
17962
17963
17964
17965
17966
17967
17968 fnp_util.pl1
17969 fnp_util$load: FNP T is running. trace
17970
17971
17972
17973
17974
17975
17976
17977
17978
17979
17980
17981 fnp_util$load -310- MR12.5 10/27/92^L
17982
17983
17984 fnp_util.pl1
17985 fnp_util$load: FNP T not wired.
17986
17987
17988
17989
17990
17991
17992 fnp_util.pl1
17993 fnp_util$unwire: Unwire failed for FNP T. REASON
17994
17995
17996
17997
17998
17999
18000 fnp_util.pl1
18001 fnp_util$validate_assigned_ret CALLER: IO
18002 manager assignment lacking. trace
18003
18004
18005
18006
18007
18008
18009 fnp_util.pl1
18010 fnp_util$wire: failed. REASON trace
18011
18012
18013
18014
18015
18016
18017 fnp_util.pl1
18018 fnp_util$wire: FNP T already wired trace
18019
18020
18021
18022
18023
18024
18025 fnp_util.pl1
18026 fnp_util: assigned FNP T to NAME for T & D.
18027
18028
18029
18030
18031
18032
18033
18034
18035
18036
18037
18038
18039 fnp_util -311- MR12.5 10/27/92^L
18040
18041
18042 fnp_util.pl1
18043 fnp_util: channel assignment failed for FNP ^T
18044 REASON. tandd
18045
18046
18047
18048
18049
18050
18051 fnp_util.pl1
18052 fnp_util: Could not unassign FNP T at
18053 reassign_interrupt.
18054
18055
18056
18057
18058
18059
18060 fnp_util.pl1
18061 fnp_util: FNP T added to configuration^ by
18062 NAME^.
18063
18064
18065
18066
18067
18068
18069 fnp_util.pl1
18070 fnp_util: force detaching FNP T from process PID.
18071
18072
18073
18074
18075
18076
18077 fnp_util.pl1
18078 fnp_util: io channel unassignment failed for FNP
18079 T. tandd
18080
18081
18082
18083 Message: fnp_util: releasing FNP T from NAME
18084 tandd
18085
18086
18087
18088 fnp_util.pl1
18089 fnp_util: io channel unassignment failed for FNP
18090 T. tandd
18091
18092
18093
18094
18095
18096
18097 fnp_util -312- MR12.5 10/27/92^L
18098
18099
18100 fnp_util.pl1
18101 fnp_util: ioam_$assign failed for FNP T. REASON
18102 tandd
18103
18104
18105
18106
18107
18108
18109 fnp_util.pl1
18110 fnp_util: lock_fnp called with lock locked.
18111
18112
18113
18114
18115
18116
18117 page_error.alm
18118 free_store: Deposit non-disk address XXXXXXXXXXXX
18119 on dskX_NNS
18120
18121
18122 Stream: BOS Typewriter Crashes system
18123
18124 Time: While system is running.
18125
18126 Meaning: free_store was called to return an address to the
18127 free pool for dskX_NNS but the address type was
18128 not disk. This probably indicates a software
18129 error.
18130
18131 Action: Follow normal recovery procedures.
18132
18133
18134
18135 page_error.alm
18136 free_store: Deposit/withdraw address XXXXXX out
18137 of paging region on dskX_NNS.
18138
18139
18140 Stream: BOS Typewriter Crashes system
18141
18142 Time: While system is running.
18143
18144 Meaning: Address XXXXXX was being deposited to or wtihdrawn
18145 from the pool of free addresses for dskX_NNS
18146 but the address is not within the Paging Region
18147 for the device. This probably indicates a
18148 software error.
18149
18150 Action: Follow normal recovery procedures.
18151
18152
18153
18154
18155 free_store -313- MR12.5 10/27/92^L
18156
18157
18158 page_error.alm
18159 free_store: Invalid call to
18160 free_store$deposit_list.
18161
18162
18163 Stream: BOS Typewriter Crashes system
18164
18165 Time: While system is running.
18166
18167 Meaning: free_store$deposit_list was called with the wrong
18168 number of arguments. This is a software error.
18169
18170 Action: Follow normal recovery procedures.
18171
18172
18173
18174 page_error.alm
18175 free_store: out of room in hardcore partition.
18176
18177
18178 Stream: BOS Typewriter Crashes system
18179
18180 Time: While system is running.
18181
18182 Meaning: During bootload the PART HC on the RLV became
18183 full. This indicates a logic error in the
18184 supervisor or CPU or memory hardware problems.
18185
18186 Action: Follow normal recovery procedures. It may be
18187 necessary to boot with another tape. If this
18188 error occurs with a new version of the system boot
18189 tape the system programming staff may determine
18190 that the size of the hardcore partition must be
18191 increased by using the rebuild_disk command on a
18192 copy of the RPV.
18193
18194
18195
18196 page_error.alm
18197 free_store: PVTE/Stock out of synch on
18198 dskX_NNS. stockp=YYY|YYYYY.
18199
18200
18201 Stream: BOS Typewriter Crashes system
18202
18203 Time: While system is running.
18204
18205 Meaning: The PVTE and record stock for dskX_NNS do not
18206 point to each other. This indicates a hardware or
18207 software error.
18208
18209 Action: Follow normal recovery procedures.
18210
18211
18212
18213 free_store -314- MR12.5 10/27/92^L
18214
18215
18216 page_error.alm
18217 free_store: Scavenger STACQ fails on dskX_NNS.
18218
18219
18220 Stream: BOS Typewriter Crashes system
18221
18222 Time: During a physical volume scavenge of dskX_NNS.
18223
18224 Meaning: A STACQ instruction used to unlock a record
18225 address during a volume scavenge did not operate
18226 correctly. This indicates processor or memory
18227 malfunction.
18228
18229 Action: Follow normal recovery procedures.
18230
18231
18232
18233 page_error.alm
18234 free_store: volmap_seg async error for dskX_NNS
18235
18236
18237 Stream: BOS Typewriter Crashes system
18238
18239 Time: While system is running.
18240
18241 Meaning: When attempting to write a page of the Volume Map
18242 to dskX_NNS the page was found not to be in
18243 memory. This probably indicates a software error.
18244
18245 Action: Follow normal recovery procedures.
18246
18247
18248
18249 freecore.pl1
18250 freecore: parity error in frame XXX of memory.
18251
18252
18253 Stream: BOS Typewriter.
18254
18255 Time: System Intialization.
18256
18257 Meaning: A memory parity error has been detected in page
18258 XXX of memory. The page will not be put in use.
18259
18260 Action: No operator action is required.
18261
18262
18263
18264
18265
18266
18267
18268
18269
18270
18271 freecore -315- MR12.5 10/27/92^L
18272
18273
18274 fs_search.pl1
18275 fs_search: Fatal damage detected to WHAT in ring
18276 RING for USER.
18277
18278
18279 Stream: Logged in SYSERR log.
18280
18281 Time: While system is running.
18282
18283 Meaning: Some object crucial to the operation of the
18284 dynamic linker in ring RING was detected damaged.
18285 Since the dynamic linker cannot operate in the
18286 process it is terminated.
18287
18288 Action: No operator action is required.
18289
18290
18291
18292 fsout_vol.pl1
18293 fsout_vol: Discarding old dumper bit maps for
18294 dskX_NNS.
18295
18296
18297 Stream: BOS Typewriter.
18298
18299 Time: System shutdown and volume demounting.
18300
18301 Meaning: An error occurred attempting to read the VTOC
18302 header from physical volume on dskX_NNS. Writing
18303 of the dumper bit maps to disk will be bypassed.
18304 The dumper bit maps will be freed and the system
18305 will attempt to continue however the dumper bit
18306 maps may not be accurate on disk.
18307
18308 Action: Contact the system programming staff.
18309
18310
18311
18312
18313
18314
18315
18316
18317
18318
18319
18320
18321
18322
18323
18324
18325
18326
18327
18328
18329 fsout_vol -316- MR12.5 10/27/92^L
18330
18331
18332 fsout_vol.pl1
18333 fsout_vol: label for PVNAME dskX_NNS uid does
18334 not match pvt.
18335
18336
18337 Stream: BOS Typewriter.
18338
18339 Time: System shutdown volume mounting and demounting.
18340
18341 Meaning: The unique physical volume ID in the label of the
18342 pack on dskX_NNS PVNAME does not compare with
18343 the value it had when the pack was first mounted.
18344 Damage to the pack has probably occurred.
18345
18346 Action: Attempt to demount the volume if this has not
18347 already been done. Save the pack for inspection
18348 and dumping by the system programming staff.
18349 Initiate volume recovery procedures.
18350
18351
18352
18353 fsout_vol.pl1
18354 fsout_vol: XXX volume inconsistenices on PVNAME
18355 dskX_NNS. YYYYY free records. ZZZZZ free
18356 VTOCEs.
18357
18358
18359 Stream: Logged only if the number of free records and the
18360 number of free VTOCEs are both above threshold
18361 values. Printed and logged if either is below
18362 threshold.
18363
18364 Time: Volume demounting and system shutdown time.
18365
18366 Meaning: At some time during the use of volume PVNAME on
18367 drive dskX_NNS the system encountered problems
18368 which left the volume in an inconsistent state.
18369 The effect of this is that some free records
18370 and/or free VTOCEs are unavailable lost to the
18371 system. These inconsistencies can be corrected by
18372 a volume salvage. The number of unused records
18373 and VTOCEs which are available for use is printed.
18374
18375 Action: If the number of free records or free vtoces is
18376 low a physical volume salvage should be done on
18377 the volume prior to mounting it again to recover
18378 the lost items.
18379
18380
18381
18382
18383
18384
18385
18386
18387 fsout_vol -317- MR12.5 10/27/92^L
18388
18389
18390 fsout_vol.pl1
18391 fsout_vol: REASON Error OPERATION OBJECT_TYPE
18392 for dskX_NNS PVNAME
18393
18394
18395 Stream: BOS Typewriter.
18396
18397 Time: System shutdown and volume mounting and
18398 demounting.
18399
18400 Meaning: A physical device error has occured while
18401 attempting to read or write OPERATION volume
18402 header information OBJECT_TYPE of the pack
18403 PVNAME on dskX_NNS.
18404
18405 Action: If this message occurs at volume mounting time
18406 check the drive specified for write-protect or
18407 standby status and retry the add_lv command for
18408 the logical volume. If this message occurs at
18409 shutdown or demount time the volume may contain
18410 inconsistencies lost free records or free
18411 VTOCEs. These inconsistencies can be corrected
18412 by a physical volume salvage.
18413
18414
18415
18416 ftp_dialup_.pl1
18417 ftp_dialup_: answer table damaged at UTEP
18418 tra_vec=TTTT
18419
18420
18421 Stream: $as2
18422
18423 Time: While system is running.
18424
18425 Meaning: The tra_vec value was found to be invalid for an
18426 answer table wakeup. Damage to the answer table
18427 is indicated.
18428
18429 Action: Contact the system programming staff.
18430
18431
18432
18433
18434
18435
18436
18437
18438
18439
18440
18441
18442
18443
18444
18445 ftp_dialup_ -318- MR12.5 10/27/92^L
18446
18447
18448 ftp_dialup_.pl1
18449 ftp_dialup_: called while ansp = null
18450
18451
18452 Stream: $as2
18453
18454 Time: While system is running.
18455
18456 Meaning: A programming error in the Answering Service or an
18457 incorrect library installation has caused the
18458 Answering Service to be called before being
18459 initialized. The system will ignore the error and
18460 attempt to continue.
18461
18462 Action: Shut down the system and perform a bootload
18463 operation.
18464
18465
18466
18467 ftp_dialup_.pl1
18468 ftp_dialup_: called with bad ptr EVENT_MSG_PTR by
18469 WWWWWWWWWWWW
18470
18471
18472 Stream: $as2
18473
18474 Time: While system is running.
18475
18476 Meaning: A programming error in the interprocess
18477 communication system the network software or the
18478 Answering Service itself has occurred. An invalid
18479 message pointer has been passed to the Answering
18480 Service. The system ignores the message and
18481 attempts to continue. This message may be the
18482 result of an incorrect library installation.
18483
18484 Action: Shut down the system and perform a bootload
18485 operation.
18486
18487
18488
18489
18490
18491
18492
18493
18494
18495
18496
18497
18498
18499
18500
18501
18502
18503 ftp_dialup_ -319- MR12.5 10/27/92^L
18504
18505
18506 ftp_dialup_.pl1
18507 ftp_dialup_: called with null message ptr
18508
18509
18510 Stream: $as2
18511
18512 Time: While system is running.
18513
18514 Meaning: A programming error in the interprocess
18515 communication system the network software or the
18516 Answering Service itself has occurred. An invalid
18517 message pointer has been passed to the Answering
18518 Service. The system ignores the message and
18519 attempts to continue. This message may be the
18520 result of an incorrect library installation.
18521
18522 Action: Shut down the system and perform a bootload
18523 operation. Inform the system programming staff.
18524
18525
18526
18527 ftp_dialup_.pl1
18528 ftp_dialup_: CDT damaged at CDTEP tra_vec=TTTT
18529
18530
18531 Stream: $as2
18532
18533 Time: While system is running.
18534
18535 Meaning: The tra_vec value was found to be invalid for a
18536 channel wakeup. Damage to the CDT is indicated.
18537
18538 Action: Contact the system programming staff.
18539
18540
18541
18542 ftp_dialup_.pl1
18543 ftp_dialup_: cdte CDTEP CHANNEL state M in use
18544 N - notify system programmer"
18545
18546
18547 Stream: $as0
18548
18549 Time: While system is running.
18550
18551 Meaning: This indicates a logic error in the supervisor or
18552 CPU or memory hardware problems.
18553
18554 Action: Contact the system programming staff.
18555
18556
18557
18558
18559
18560
18561 ftp_dialup_ -320- MR12.5 10/27/92^L
18562
18563
18564 ftp_dialup_.pl1
18565 ftp_dialup_: cdtep = null and ate.active = DDDD
18566 for UTEP
18567
18568
18569 Stream: $as2
18570
18571 Time: While system is running.
18572
18573 Meaning: This indicates a logic error in the supervisor or
18574 CPU or memory hardware problems.
18575
18576 Action: Contact the system programming staff.
18577
18578
18579
18580 ftp_dialup_.pl1
18581 ftp_dialup_: ERROR_MESSAGE attempting to allocate
18582 a user table entry for CHANNEL
18583
18584
18585 Stream: $as1
18586
18587 Time: While system is running.
18588
18589 Meaning: An ERROR_MESSAGE was returned from a call to
18590 asu_$attach_ate which allocates a user table
18591 entry.
18592
18593 Action: Contact the system programming staff.
18594
18595
18596
18597 ftp_dialup_.pl1
18598 ftp_dialup_: ERROR_MESSAGE new_proc of
18599 PERSON.PROJECT denied by channel AIM restriction.
18600
18601
18602 Stream: $as0
18603
18604 Time: While system is running.
18605
18606 Meaning: A user attempted to issue a new_proc an specify an
18607 AIM authorization which is not allowed by the
18608 terminal channel in use.
18609
18610 Action: No operator action is required.
18611
18612
18613
18614
18615
18616
18617
18618
18619 ftp_dialup_ -321- MR12.5 10/27/92^L
18620
18621
18622 ftp_dialup_.pl1
18623 ftp_dialup_: ERROR_MESSAGE occurred attempting to
18624 declare handler for ev chn EVENT_CHN for ate UTEP
18625 for CDT_CHANNEL
18626
18627
18628 Stream: $as2
18629
18630 Time: While system is running.
18631
18632 Meaning: An ERROR_MESSAGE was returned when an attempt was
18633 made to declare an event call channel for new
18634 process UTEP on EVENT_CHN attached to
18635 CDT_CHANNEL.
18636
18637 Action: Contact the system programming staff.
18638
18639
18640
18641 ftp_dialup_.pl1
18642 ftp_dialup_: ERROR_MESSAGE tty_dim error
18643 removing channel CHANNEL COMMENT
18644
18645
18646 Stream: $as2
18647
18648 Time: While system is running.
18649
18650 Meaning: An ERROR_MESSAGE caused the CHANNEL to be
18651 unusable. The CHANNEL with COMMENT will be
18652 removed from service.
18653
18654 Action: You may try to attach the channel. If that fails
18655 notify the system programmers. If the channel is
18656 to be left detached busy out the modem.
18657
18658
18659
18660
18661
18662
18663
18664
18665
18666
18667
18668
18669
18670
18671
18672
18673
18674
18675
18676
18677 ftp_dialup_ -322- MR12.5 10/27/92^L
18678
18679
18680 ftp_dialup_.pl1
18681 ftp_dialup_: ERROR_MESSAGE when creating process
18682 for PERSON.PROJECT
18683
18684
18685 Stream: $as2
18686
18687 Time: While system is running.
18688
18689 Meaning: An ERROR_MESSAGE was returned and the system was
18690 unable to create a user process for
18691 PERSON.PROJECT.
18692
18693 Action: If possible get in touch with the user. He got
18694 a message to contact you. Ask him to try again
18695 and to tell you of any peculiarities of his login.
18696 Note all particulars and contact the programming
18697 staff.
18698
18699
18700
18701 ftp_dialup_.pl1
18702 ftp_dialup_: fatal error during process creation
18703 for PERSON.PROJECT CHANNEL
18704
18705
18706 Stream: $as1
18707
18708 Time: While system is running.
18709
18710 Meaning: A fatal error occurred during process creation for
18711 PERSON.PROJECT on CHANNEL. Reason is given in
18712 previous log entry. This may be due to a user
18713 error: incorrect segments in the user's home
18714 directory or bad login arguments can cause this
18715 problem.
18716
18717 Action: No operator action is required.
18718
18719
18720
18721
18722
18723
18724
18725
18726
18727
18728
18729
18730
18731
18732
18733
18734
18735 ftp_dialup_ -323- MR12.5 10/27/92^L
18736
18737
18738 ftp_dialup_.pl1
18739 ftp_dialup_: ignored SSSS from PERSON.PROJECT for
18740 CHANNEL state=DDDDinuse=UUUUtv=TTTT
18741
18742
18743 Stream: $as2
18744
18745 Time: While system is running.
18746
18747 Meaning: A spurious signal SSSS from user PERSON.PROJECT
18748 has arrived for CHANNEL. The state of the channel
18749 is DDD inuse is UUUU and tra_vec is TTTT.
18750
18751 Action: This may be some user trying to disrupt the
18752 system. Do a who and save it for the programming
18753 staff.
18754
18755
18756
18757 ftp_dialup_.pl1
18758 ftp_dialup_: non-null atep UTEP for cdte
18759 CDTEPCHANNEL tv=TRAVECinuse=INUSE
18760
18761
18762 Stream: $as0
18763
18764 Time: While system is running.
18765
18766 Meaning: A wakeup occurred for CHANNEL whose user table
18767 entry pointer UTEP was non-null. A test on the
18768 above information determined that the state of the
18769 channel to be inconsistant. The system will null
18770 the UTEP pointer in the CDT for the above channel.
18771
18772 Action: Contact the system programming staff.
18773
18774
18775
18776 ftp_dialup_.pl1
18777 ftp_dialup_: premature stopstop for
18778 PERSON.PROJECT CHANNEL
18779
18780
18781 Stream: $as0
18782
18783 Time: While system is running.
18784
18785 Meaning: This indicates a logic error in the supervisor or
18786 CPU or memory hardware problems.
18787
18788 Action: Contact the system programming staff.
18789
18790
18791
18792
18793 ftp_dialup_ -324- MR12.5 10/27/92^L
18794
18795
18796 ftp_dialup_.pl1
18797 ftp_dialup_: process did not respond properly to
18798 trm_ signal. PERSON.PROJECT CHANNEL
18799
18800
18801 Stream: $as0
18802
18803 Time: While system is running.
18804
18805 Meaning: The PERSON.PROJECT process on CHANNEL was being
18806 terminated and had been sent the trm_ signal but
18807 it did not respond. User process will be bumped
18808 logged out or new_proced. It is possible that the
18809 user can cause this message.
18810
18811 Action: No operator action is required.
18812
18813
18814
18815 ftp_dialup_.pl1
18816 ftp_dialup_: process ignored term signal
18817 PERSON.PROJECT CHANNEL
18818
18819
18820 Stream: $as1
18821
18822 Time: While system is running.
18823
18824 Meaning: The PERSON.PROJECT process on CHANNEL had been
18825 sent a trm_ signal but the process did not respond
18826 to it. The process will be handled as was
18827 intended to be; bumped logged out etc.
18828
18829 Action: No operator action is required.
18830
18831
18832
18833 ftp_dialup_.pl1
18834 ftp_dialup_: process terminated PERSON.PROJECT
18835 CHANNEL TERM_MESSAGE
18836
18837
18838 Stream: $as0
18839
18840 Time: While system is running.
18841
18842 Meaning: The process for PERSON.PROJECT on CHANNEL was
18843 terminated abnormally due to reason in
18844 TERM_MESSAGE.
18845
18846 Action: No operator action is required.
18847
18848
18849
18850
18851 ftp_dialup_ -325- MR12.5 10/27/92^L
18852
18853
18854 ftp_dialup_.pl1
18855 ftp_dialup_: Program error: null atep with
18856 per-process tra_vec value
18857
18858
18859 Stream: $as2
18860
18861 Time: While system is running.
18862
18863 Meaning: A system programming error in the answering
18864 service has occurred as a wakeup occurred when
18865 tra_vec indicated to expect a process termination
18866 but the ate pointer was null.
18867
18868 Action: Contact the system programming staff.
18869
18870
18871
18872 ftp_dialup_.pl1
18873 ftp_dialup_: Program error: null cdtep with
18874 per-channel tra_vec value
18875
18876
18877 Stream: $as2
18878
18879 Time: While system is running.
18880
18881 Meaning: A wakeup was received when the tra_vec value
18882 indicated a channel operation was required but the
18883 cdtep was null. This is considered to be a
18884 programming error.
18885
18886 Action: Contact the system programming staff.
18887
18888
18889
18890 ftp_dialup_.pl1
18891 ftp_dialup_: Program error: per-process wakeup
18892 with per-channel-only tra_vec value
18893
18894
18895 Stream: $as2
18896
18897 Time: While system is running.
18898
18899 Meaning: A process wakeup occurred when the tra_vec value
18900 indicated it should be a channel wakeup. This is
18901 considered a programing error.
18902
18903 Action: Contact the system programming staff.
18904
18905
18906
18907
18908
18909 ftp_dialup_ -326- MR12.5 10/27/92^L
18910
18911
18912 ftp_dialup_.pl1
18913 ftp_dialup_: re-used cdte CDTEPCHANNEL by ate
18914 UTEP destroy_flag=DDDD
18915
18916
18917 Stream: $as0
18918
18919 Time: While system is running.
18920
18921 Meaning: An ate wakeup occurred which pointed to a CDTEP
18922 that was already in use by another process.
18923
18924 Action: Contact the system programming staff.
18925
18926
18927
18928 ftp_dialup_.pl1
18929 ftp_dialup_: re-used cdte CDTEPCHANNEL by ate
18930 UTEP destroy_flag=DDDD
18931
18932
18933 Stream: $as0
18934
18935 Time: While system is running.
18936
18937 Meaning: An ate wakeup occurred which pointed to a CDTEP
18938 that was already in use by another process.
18939
18940 Action: Contact the system programming staff.
18941
18942
18943
18944 ftp_dialup_.pl1
18945 ftp_dialup_: terminating fatal process error loop
18946 for PERSON.PROJECT CHANNEL
18947
18948
18949 Stream: $as1
18950
18951 Time: While system is running.
18952
18953 Meaning: The process for PERSON.PROJECT on CHANNEL has
18954 taken too many fatal process errors. This is
18955 governed by fatal_error_loop_seconds and
18956 fatal_error_loop_count in the installation_parms.
18957 The user will not get a new process. The channel
18958 will not be hungup but will get a message
18959 indicating this condition. This message may be
18960 due to a user error.
18961
18962 Action: No operator action is required.
18963
18964
18965
18966
18967 ftp_dialup_ -327- MR12.5 10/27/92^L
18968
18969
18970 ftp_dialup_.pl1
18971 ftp_dialup_: The answer table is full MAX
18972 entries.
18973
18974
18975 Stream: $as1
18976
18977 Time: While system is running.
18978
18979 Meaning: The system answer table is full and has MAX
18980 entries. No more users will be able to login.
18981
18982 Action: Contact the system programming staff.
18983
18984
18985
18986 ftp_dialup_.pl1
18987 ftp_dialup_: trace event CHANNEL FFFFFFFF
18988 WWWWWWWWWWWW RRRRRRDDDDDD SS XXXX st N wp M
18989
18990
18991 Stream: $as1
18992
18993 Time: While system is running.
18994
18995 Meaning: This is trace output. When
18996 ftp_dialup_$ftp_dial_loud is called these
18997 messages are printed out for every signal
18998 concerning a device channel. FFFFFFFF is the
18999 function being performed. WWWWWWWWWWWW is the
19000 sending process ID. RRRRRR is the ring origin of
19001 the signal. DDDDDD is the device signal
19002 information. The pointer SS XXXX locates the
19003 answer table entry for CHANNEL. The channel state
19004 is N and the wait point transaction vector is M.
19005
19006 Action: $ignore To turn these messages off type
19007 ftp_dialup_$ftp_dial_soft while in admin mode.
19008
19009
19010
19011
19012
19013
19014
19015
19016
19017
19018
19019
19020
19021
19022
19023
19024
19025 ftp_dialup_ -328- MR12.5 10/27/92^L
19026
19027
19028 ftp_dialup_.pl1
19029 ftp_dialup_: turning off disconnected flag for
19030 ate UTEP cdte CDTEPCHANNEL
19031
19032
19033 Stream: $as0
19034
19035 Time: While system is running.
19036
19037 Meaning: If processing an ate wakeup the CHANNEL is known
19038 and the process is disconnected the disconnected
19039 flag for the ate will be turned off.
19040
19041 Action: Contact the system programming staff.
19042
19043
19044
19045 ftp_dialup_.pl1
19046 ftp_dialup_: Unable to determine initial terminal
19047 type for channel CHANNEL
19048
19049
19050 Stream: $as2
19051
19052 Time: While system is running.
19053
19054 Meaning: Unable to determine the default terminal type
19055 based on line-type/baud-rate in the TTT. The
19056 channel has been removed from known channels.
19057
19058 Action: Contact the system programming staff.
19059
19060
19061
19062 ftp_dialup_.pl1
19063 ftp_dialup_: unexpected state SSSS for channel
19064 definition table at CDTEP
19065
19066
19067 Stream: $as2
19068
19069 Time: While system is running.
19070
19071 Meaning: This indicates a logic error in the supervisor or
19072 CPU or memory hardware problems.
19073
19074 Action: Contact the system programming staff.
19075
19076
19077
19078
19079
19080
19081
19082
19083 ftp_dialup_ -329- MR12.5 10/27/92^L
19084
19085
19086 ftp_dialup_.pl1
19087 ftp_dialup_: Unexpected termsgnl for
19088 PERSON.PROJECT CHANNEL preempted=DDDD.
19089
19090
19091 Stream: $as0
19092
19093 Time: While system is running.
19094
19095 Meaning: A "termsgnl" wakeup was received for the
19096 PERSON.PROJECT process on CHANNEL whose
19097 ute.preempted value DDDD did not indicate one was
19098 allowed. This is considered to be a program
19099 error. User will be given a new process.
19100
19101 Action: Contact the system programming staff.
19102
19103
19104
19105 ftp_dialup_.pl1
19106 ftp_dialup_: wrong answerback on CHANNEL
19107 COMMENT; expected "ID1" got "ID2".
19108
19109
19110 Stream: $as2
19111
19112 Time: While system is running.
19113
19114 Meaning: A terminal attempted to connect on CHANNEL whose
19115 CDT comment is COMMENT that is restricted to a
19116 specific answerback and did not return the
19117 expected value. ID1 is the answerback expected;
19118 ID2 is the answerback actually received. The
19119 terminal is hung up.
19120
19121 Action: No operator action is required.
19122
19123
19124
19125
19126
19127
19128
19129
19130
19131
19132
19133
19134
19135
19136
19137
19138
19139
19140
19141 ftp_dialup_ -330- MR12.5 10/27/92^L
19142
19143
19144 get_aste.pl1
19145 get_aste: Error deactivating UUUU vtoc V of pvt
19146 PV to free XXXk ASTE for USERNAME.
19147
19148
19149 Stream: Logged in SYSERR log.
19150
19151 Time: While system is running.
19152
19153 Meaning: The system encountered an error deactivating an
19154 AST entry which was selected for deactivation by
19155 the AST replacement algorithm. The AST on which
19156 the error was encountered will be flagged to be
19157 ingored by further passes of the algorithm; this
19158 flag will be reset during the next run of
19159 flush_ast_pool.
19160
19161 Action: If the problem persists contact the system
19162 programming staff.
19163
19164
19165
19166 get_aste.pl1
19167 get_aste: Invalid csl x
19168
19169
19170 Stream: Logged in SYSERR log.
19171
19172 Time: While system is running.
19173
19174 Meaning: get_aste was called to activate a segment with x
19175 pages which is larger than the maximum segment
19176 size. This is indicative of hardware or software
19177 failure a typical problem is an invalid VTOCE.
19178
19179 Action: If the problem persists contact the system
19180 programming staff.
19181
19182
19183
19184
19185
19186
19187
19188
19189
19190
19191
19192
19193
19194
19195
19196
19197
19198
19199 get_aste -331- MR12.5 10/27/92^L
19200
19201
19202 get_aste.pl1
19203 get_aste: no removable XXXk ast entries
19204
19205
19206 Stream: BOS Typewriter.
19207
19208 Time: While system is running.
19209
19210 Meaning: An AST entry was needed for a segment of size XXX
19211 k but no free entries of that size were present
19212 and no segments occupying such entries could be
19213 deactivated. This could be symptomatic of a logic
19214 problem but may also indicate a grossly mistuned
19215 AST.
19216
19217 Action: Substantially increase the number of AST entries of
19218 this size as given on the SST CONFIG card. If the
19219 problem persists contact the system programming
19220 staff.
19221
19222
19223
19224 get_aste.pl1
19225 get_aste: no removable XXXk synchronized AST
19226 entries
19227
19228
19229 Stream: Logged in SYSERR log.
19230
19231 Time: While system is running.
19232
19233 Meaning: An AST entry was needed for a synchronized segment
19234 of size XXX k and the per-ASTE-pool limit on
19235 synchronized segments was reached. No
19236 synchronized segments in that pool could be
19237 deactivated.
19238
19239 Action: Contact the system programming staff.
19240
19241
19242
19243
19244
19245
19246
19247
19248
19249
19250
19251
19252
19253
19254
19255
19256
19257 get_aste -332- MR12.5 10/27/92^L
19258
19259
19260 get_io_segs.pl1
19261 get_io_segs: DSKQ mmm. < xxx. per drive
19262 forcing DSKQ nnn.
19263
19264
19265 Stream: BOS Typewriter sounds beeper
19266
19267 Time: System Intialization.
19268
19269 Meaning: The dskq card specifies less than 5 queue entries
19270 per configured drive. This is considered too few
19271 for efficient operation and is forced to 5 entries
19272 per drive.
19273
19274 Action: $config
19275
19276
19277
19278 get_io_segs.pl1
19279 get_io_segs: DSKQ mmm. > xxx. per drive
19280 forcing DSKQ nnn.
19281 Stream: BOS Typewriter sounds beeper
19282
19283
19284 Time: System Intialization.
19285
19286 Meaning: The dskq card specifies an excess of queue entries
19287 beyond that reasonably required for efficient
19288 operation. The free queue will be limited to 100
19289 entries per drive.
19290
19291 Action: $config
19292
19293
19294
19295 get_io_segs.pl1
19296 get_io_segs: Missing ndrives field on config card
19297 prph NAME.
19298
19299
19300 Stream: BOS Typewriter Crashes system
19301
19302 Time: System Intialization.
19303
19304 Meaning: The prph card for the NAME subsystem is missing an
19305 ndrives field.
19306
19307 Action: $config
19308
19309
19310
19311
19312
19313
19314
19315 get_io_segs -333- MR12.5 10/27/92^L
19316
19317
19318 get_main.pl1
19319 get_main: insufficient storage available for NAME
19320
19321
19322 Stream: BOS Typewriter Crashes system
19323
19324 Time: System Intialization.
19325
19326 Meaning: Insufficient wired memory was available to create
19327 the segment NAME during initialization. The
19328 system tape may be bad or the configuration may
19329 be too small or the system parameters specified
19330 in the configuration deck may be incorrect or
19331 inconsistent with the amount of main storage
19332 available.
19333
19334 Action: Follow normal recovery procedures. Check the
19335 configuration and the CONFIG deck. The Multics
19336 System Tape may be incorrect. If the problem
19337 persists try another MST.
19338
19339
19340
19341 get_main.pl1
19342 get_main: not enough room to allocate unpaged
19343 page table for NAME.
19344
19345
19346 Stream: BOS Typewriter Crashes system
19347
19348 Time: System Intialization.
19349
19350 Meaning: Either the segment unpaged_page_tables or
19351 int_unpaged_page_tables was not big enough so as
19352 to have the page table for segment NAME allocated
19353 within it. The system tape may be bad or changes
19354 made to the mst require bigger unpaged page
19355 tables.
19356
19357 Action: Follow normal recovery procedures. Try another
19358 tape. If bigger unpaged page tables are in order
19359 a change must be made to bootload_equs.incl.alm
19360 and collection 0 recompiled. The Multics System
19361 Tape may be incorrect. If the problem persists
19362 try another MST.
19363
19364
19365
19366
19367
19368
19369
19370
19371
19372
19373 get_main -334- MR12.5 10/27/92^L
19374
19375
19376 get_pvtx.pl1
19377 get_pvtx$cleanup: Force released hold on pvtx ^d
19378 for USER_ID.
19379
19380
19381 Stream: BOS Typewriter.
19382
19383 Time: While system is running.
19384
19385 Meaning: This indicates a logic error in the supervisor or
19386 CPU or memory hardware problems. A condition was
19387 signalled in ring-0 which caused a crawlout.
19388 get_pvtx$cleanup will release all PV holds for the
19389 process.
19390
19391 Action: Contact the system programming staff.
19392
19393
19394
19395 get_pvtx.pl1
19396 get_pvtx: drain_pvtx: pvte.being_demounted
19397 should be on.
19398
19399
19400 Stream: BOS Typewriter Crashes system
19401
19402 Time: While system is running.
19403
19404 Meaning: The entry to the physical volume demount
19405 protection mechanism which awaits all use of the
19406 volume to cease is being called improperly. A
19407 necessary precondition for its proper operation
19408 pvte.being_demounted is not met. This indicates
19409 a logic error in the supervisor or CPU or memory
19410 hardware problems.
19411
19412 Action: Follow normal recovery procedures.
19413
19414
19415
19416
19417
19418
19419
19420
19421
19422
19423
19424
19425
19426
19427
19428
19429
19430
19431 get_pvtx -335- MR12.5 10/27/92^L
19432
19433
19434 get_pvtx.pl1
19435 get_pvtx: hold_pvtx finds table full
19436
19437
19438 Stream: BOS Typewriter Crashes system
19439
19440 Time: While system is running.
19441
19442 Meaning: There are no free entries in the physical volume
19443 hold table. There should never be more than twice
19444 the number of eligible processes of used entries.
19445 This indicates a logic error in the supervisor or
19446 CPU or memory hardware problems.
19447
19448 Action: Follow normal recovery procedures.
19449
19450
19451
19452 get_pvtx.pl1
19453 get_pvtx: release_pvtx: mark not found
19454
19455
19456 Stream: BOS Typewriter Crashes system
19457
19458 Time: While system is running.
19459
19460 Meaning: While attempting to release a physical volume from
19461 demount protection the mark made by the
19462 protection could not be found in the physical
19463 volume hold table. This message can also occur if
19464 somehow the physical volume was demounted in spite
19465 of this protection or this entry point is being
19466 used improperly. This indicates a logic error in
19467 the supervisor or CPU or memory hardware
19468 problems.
19469
19470 Action: Follow normal recovery procedures.
19471
19472
19473
19474
19475
19476
19477
19478
19479
19480
19481
19482
19483
19484
19485
19486
19487
19488
19489 get_pvtx -336- MR12.5 10/27/92^L
19490
19491
19492 get_pvtx.pl1
19493 get_pvtx: ZERO_ENTRY fails
19494
19495
19496 Stream: BOS Typewriter Crashes system
19497
19498 Time: While system is running.
19499
19500 Meaning: The STACQ instruction has failed to clear an entry
19501 in the physical volume hold table. This indicates
19502 a logic error in the supervisor or CPU or memory
19503 hardware problems.
19504
19505 Action: Follow normal recovery procedures.
19506
19507
19508
19509 grab_aste.pl1
19510 grab_aste: Attempt to reuse segno SSS
19511
19512
19513 Stream: BOS Typewriter Crashes system
19514
19515 Time: While system is running.
19516
19517 Meaning: A call has been made to force active a segment
19518 already forced active. This indicates an
19519 inconsistency in the programming of the
19520 supervisor. This indicates a logic error in the
19521 supervisor or CPU or memory hardware problems.
19522
19523 Action: Follow normal recovery procedures. Contact the
19524 system programming staff.
19525
19526
19527
19528 grab_aste.pl1
19529 grab_aste: failed to reactivate PPPP ERRORMESSAGE
19530
19531
19532 Stream: BOS Typewriter Crashes system
19533
19534 Time: While system is running.
19535
19536 Meaning: This indicates a logic error in the supervisor or
19537 CPU or memory hardware problems.
19538
19539 Action: Follow normal recovery procedures. Contact the
19540 system programming staff.
19541
19542
19543
19544
19545
19546
19547 grab_aste -337- MR12.5 10/27/92^L
19548
19549
19550 grab_aste.pl1
19551 grab_aste: Unprotected segment: astep = AAA
19552
19553
19554 Stream: BOS Typewriter Crashes system
19555
19556 Time: While system is running.
19557
19558 Meaning: An attempt was made to release from forced
19559 activity a segment whose AST entry is at AAA
19560 which was not even in a state of forced activity.
19561 This indicates a logic error in the supervisor or
19562 CPU or memory hardware problems.
19563
19564 Action: Contact the system programming staff. Follow
19565 normal recovery procedures.
19566
19567
19568
19569 bootload_error.alm
19570 HALT with octal 5's in the upper half of the AQ.
19571
19572
19573 Stream: BOS Typewriter Crashes system
19574
19575 Time: System Intialization.
19576
19577 Meaning: The collection zero call stack has overflowed.
19578 This indicates a logic error in the collection
19579 zero supervisor or a hardware problem possibly
19580 with id or di modifiers.
19581
19582 Action: Try another tape and/or look for a CPU bug.
19583
19584
19585
19586
19587
19588
19589
19590
19591
19592
19593
19594
19595
19596
19597
19598
19599
19600
19601
19602
19603
19604
19605 HALT with octal 5's in the -338- MR12.5 10/27/92^L
19606
19607
19608 bootload_error.alm
19609 HALT with octal 6's in the upper half of the AQ.
19610
19611
19612 Stream: BOS Typewriter Crashes system
19613
19614 Time: System Intialization.
19615
19616 Meaning: A recursive error condition was encountered: that
19617 is the collection zero error handler was called
19618 recursively. The low half of the A contains the
19619 unique error number of the recursive error. See
19620 the listing of bootload_error.alm for error
19621 numbers. bootload_error$disaster_AQ contains the
19622 AQ at the time of recursive entry.
19623
19624 Action: This error indicates a logic error or a hardware
19625 problem. Use execute switches to return to BOS.
19626 Try a different tape. Failing that look for a
19627 CPU problem.
19628
19629
19630
19631 bootload_io.alm
19632 HALT with octal 777777000001 in the A register.
19633
19634
19635 Stream: BOS Typewriter Crashes system
19636
19637 Time: System Intialization.
19638
19639 Meaning: The interrupt base set on the bootload IOM is not
19640 1200 octal.
19641
19642 Action: Set the switches correctly.
19643
19644
19645
19646 bootload_io.alm
19647 HALT with octal 777777000002 in the A register.
19648
19649
19650 Stream: BOS Typewriter Crashes system
19651
19652 Time: System Intialization.
19653
19654 Meaning: The iom base set on the bootload IOM is not
19655 correct. I.e. for IOM's 0 1 2 and 3 it should
19656 be 1400 2000 2400 and 3000 octal respectively.
19657
19658 Action: Set the switches correctly.
19659
19660
19661
19662
19663 HALT with octal 7777770000 -339- MR12.5 10/27/92^L
19664
19665
19666 bootload_tape_label.alm
19667 HALT with only the first MST tape record read.
19668
19669
19670
19671 Stream: BOS Typewriter Crashes system
19672
19673 Time: System Intialization.
19674
19675 Meaning: If the high-order bit of the AQ register is on
19676 the pattern in the AQ
19677 register is the bad status returned by the
19678 IOM while reading a tape
19679 record. If the high order bit is not on the A
19680 register contains the
19681 flags word from a MST header record indicating
19682 that this record is bad.
19683
19684 Action: Try booting on a different drive or with a
19685 different tape.
19686
19687
19688
19689 hardware_fault.pl1
19690 hardware_fault: Deleting frame at WWW from SCU X
19691 due to parity errors
19692
19693
19694 Stream: BOS Typewriter sounds beeper
19695
19696 Time: While system is running.
19697
19698 Meaning: A parity error was detected at main storage
19699 address WWWW. The main memory frame with the
19700 error was removed from service via delmain. The
19701 user process encountering the parity fault cannot
19702 be restarted at the point of error because the
19703 processor state is imprecise. If the parity error
19704 could have damaged user data the damaged switch
19705 is set on the segment and the user is given the
19706 best version we can come up with for the page.
19707
19708 Action: Contact Field Engineering personnel. The memory
19709 page will remain out of service until added back
19710 by addmain.
19711
19712
19713
19714
19715
19716
19717
19718
19719
19720
19721 hardware_fault -340- MR12.5 10/27/92^L
19722
19723
19724 hardware_fault.pl1
19725 hardware_fault: FFF fault on CPU CPUTAG by
19726 PROCESSNAME.
19727
19728
19729 Stream: BOS Typewriter.
19730
19731 Time: While system is running.
19732
19733 Meaning: A fault indicating processor or main memory
19734 malfunction has occurred on CPU CPUTAG. FFF is
19735 the name of the fault. Complete binary data about
19736 the fault is logged for automatic processing.
19737
19738 Action: Contact Field engineering personnel.
19739
19740
19741
19742 hasp_mpx.pl1
19743 hasp_mpx line TTY: Bad block line status from
19744 FNP; line will be hungup.
19745
19746
19747 Stream: Note for system programmer action.
19748
19749 Time: While system is running.
19750
19751 Meaning: A block generated by the HASP multiplexer on
19752 channel TTY for transmission was malformed. The
19753 connection to the remote host/workstation is
19754 broken as communications cannot continue under
19755 these conditions.
19756
19757 Action: Contact the system programming staff.
19758
19759
19760
19761
19762
19763
19764
19765
19766
19767
19768
19769
19770
19771
19772
19773
19774
19775
19776
19777
19778
19779 hasp_mpx line TTY -341- MR12.5 10/27/92^L
19780
19781
19782 hasp_mpx.pl1
19783 hasp_mpx line TTY: Block received out of
19784 sequence: expected = N recevied = M; line will
19785 be hungup.
19786
19787
19788 Stream: Note for system programmer action.
19789
19790 Time: While system is running.
19791
19792 Meaning: One or more data blocks from the remote
19793 host/workstation for the HASP multiplexer on
19794 channel TTY were lost. The connection to the
19795 remote host/workstation is broken as
19796 communications cannot continue under these
19797 conditions.
19798
19799 Action: There are two possible causes for this message:
19800 communications equipment failures or problems in
19801 the remote host/workstation itself. The operator
19802 should contact the appropriate personnel before
19803 reusing the multiplexer.
19804
19805
19806
19807 hasp_mpx.pl1
19808 hasp_mpx line TTY: Block recevied out of
19809 sequence: expected = N received = M; block
19810 ignored.
19811
19812
19813 Stream: Logged in SYSERR log.
19814
19815 Time: While system is running.
19816
19817 Meaning: A duplicate data block was received by the HASP
19818 multiplexer on channel TTY from the foreign
19819 host/workstation.
19820
19821 Action: The operator should ignore this message unless it
19822 occurs quite frequently. Frequent occurences of
19823 this message indicate possible problems in the
19824 communications equipment which should be
19825 investigated by the appropriate personnel.
19826
19827
19828
19829
19830
19831
19832
19833
19834
19835
19836
19837 hasp_mpx line TTY -342- MR12.5 10/27/92^L
19838
19839
19840 hasp_mpx.pl1
19841 hasp_mpx line TTY: Block transmitted out of
19842 sequence: expected = N received = M; line will
19843 be hungup.
19844
19845
19846 Stream: Note for system programmer action.
19847
19848 Time: While system is running.
19849
19850 Meaning: One or more data blocks transmitted by the HASP
19851 multiplexer on channel TTY were not received by
19852 the remote host/workstation. The connection to
19853 the remote host/workstation is broken as
19854 communications cannot continue under these
19855 conditions.
19856
19857 Action: Contact the system programming staff. The HASP
19858 software is designed to prevent this situation
19859 even if the communications equipment is not
19860 functioning properly.
19861
19862
19863
19864 hasp_mpx.pl1
19865 hasp_mpx line TTY: Duplicate loopback block
19866 received: BCB = NNN
19867
19868
19869 Stream: Note for system programmer action.
19870
19871 Time: While system is running.
19872
19873 Meaning: The output block identified by the 3-digit octal
19874 sequence NNN was returned to Multics twice by the
19875 FNP for reprocessing.
19876
19877 Action: Contact the system programming staff.
19878
19879
19880
19881
19882
19883
19884
19885
19886
19887
19888
19889
19890
19891
19892
19893
19894
19895 hasp_mpx line TTY -343- MR12.5 10/27/92^L
19896
19897
19898 hasp_mpx.pl1
19899 hasp_mpx line TTY: Invalid input block
19900 header/trailer; line will be hungup.
19901
19902
19903 Stream: Note for system programmer action.
19904
19905 Time: While system is running.
19906
19907 Meaning: A data block whose format does not conform to the
19908 HASP protocol was received from the remote
19909 host/workstation by the HASP multiplexer on
19910 channel TTY. The connection to the remote
19911 host/workstation is broken as communications
19912 cannot continue under these conditions.
19913
19914 Action: Frequent occurences of this message indicate that
19915 hardware or software problems may exist in the
19916 remote host/workstation. The operator should
19917 contact the appropriate personnel before reusing
19918 the multiplexer.
19919
19920
19921
19922 hasp_mpx.pl1
19923 hasp_mpx line TTY: No space available to
19924 preserve minor state; line will be hungup.
19925
19926
19927 Stream: BOS Typewriter.
19928
19929 Meaning: Insufficient space was available in tty_buf to
19930 perform part of the critical input processing of
19931 the HASP multiplexer on channel TTY. The
19932 connection to the remote host/workstation is
19933 broken as communications cannot continue under
19934 these conditions.
19935
19936 Action: Contact the system programming staff. It may be
19937 necessary to increase the size of tty_buf as
19938 specified on the PARM config card before using
19939 this multiplexer again.
19940
19941
19942
19943
19944
19945
19946
19947
19948
19949
19950
19951
19952
19953 hasp_mpx line TTY -344- MR12.5 10/27/92^L
19954
19955
19956 hasp_mpx.pl1
19957 hasp_mpx line TTY: No space available to save
19958 loopback chain; line will be hungup.
19959
19960
19961 Stream: BOS Typewriter.
19962
19963 Meaning: Insufficient space was available in tty_buf to
19964 perform part of the critical input processing of
19965 the HASP multiplexer on channel TTY. The
19966 connection to the remote host/workstation is
19967 broken as communications cannot continue under
19968 these conditions.
19969
19970 Action: Contact the system programming staff. It may be
19971 necessary to increase the size of tty_buf as
19972 specified on the PARM config card before using
19973 this multiplexer again.
19974
19975
19976
19977 hasp_mpx.pl1
19978 hasp_mpx line TTY: Too many NAKs; line will be
19979 hungup.
19980
19981
19982 Stream: Note for system programmer action.
19983
19984 Time: While system is running.
19985
19986 Meaning: A block could not be transmitted or received by
19987 the HASP multiplexer on channel TTY because of
19988 excessive line noise. The connection to the
19989 remote host/workstation is broken as
19990 communications cannot continue under these
19991 conditions.
19992
19993 Action: The operator should contact the appropriate
19994 personnel to check the communications equipment
19995 used by the line before attempting to reuse this
19996 multiplexer.
19997
19998
19999
20000
20001
20002
20003
20004
20005
20006
20007
20008
20009
20010
20011 hasp_mpx line TTY -345- MR12.5 10/27/92^L
20012
20013
20014 hc_dmpr_primitives.pl1
20015 hc_dmpr_primitives: bad uid pathname detected at
20016 pvid WWWW vtocx XXXX
20017
20018
20019 Stream: Logged in SYSERR log.
20020
20021 Time: While system is running.
20022
20023 Meaning: Part 3 of the indicated VTOCE is bad. The dumper
20024 will treat the vtoce as a null vtoce and continue.
20025
20026 Action: No operator action is required.
20027
20028
20029
20030 hc_dmpr_primitives.pl1
20031 hc_dmpr_primitives: trailer storage area
20032 exhausted
20033
20034
20035 Stream: BOS Typewriter Crashes system
20036
20037 Time: While system is running.
20038
20039 Meaning: This indicates a logic error in the supervisor or
20040 CPU or memory hardware problems.
20041
20042 Action: Follow normal recovery procedures.
20043
20044
20045
20046 hc_dmpr_primitives.pl1
20047 hc_dmpr_primitives: Unable to set label time.
20048 PVID = wwwwwwwwwwww
20049
20050
20051 Stream: BOS Typewriter.
20052
20053 Time: While system is running.
20054
20055 Meaning: A disk error prevented the updating of the
20056 time-last-dumped field in the volume label. The
20057 physical volume identifier is wwwwwwwwwwww.
20058
20059 Action: Contact the system programming staff.
20060
20061
20062
20063
20064
20065
20066
20067
20068
20069 hc_dmpr_primitives -346- MR12.5 10/27/92^L
20070
20071
20072 hc_initlzr_auxl_init_.pl1
20073 hc_initlrz_auxl_init_: MESSAGE. From
20074 hc_device_acct_$init.
20075
20076
20077 Stream: as severity2
20078
20079 Time: System Intialization.
20080
20081 Meaning: An error was detected while initializing device
20082 accounting.
20083
20084 Action: Contact the system programming staff.
20085
20086
20087
20088 hc_ipc.pl1
20089 hc_ipc: ITT overflow caused by NAME.PROJ
20090
20091
20092 Stream: BOS Typewriter.
20093
20094 Time: While system is running.
20095
20096 Meaning: When wakeups are sent from one process to another
20097 or from a device like a tape drive to a process
20098 the wakeups are stored temporarily in the
20099 Interprocess Transmission Table ITT. If wakeups
20100 are sent too fast or if the receiving process
20101 never calls block to read its wakeups the ITT may
20102 overflow. When the ITT is full this message is
20103 printed for each lost wakeup. The message
20104 identifies the sender of the wakeup who may be
20105 innocent of any error or wrongdoing.
20106
20107 If a critical system function cannot send a
20108 wakeup the system may crash.
20109
20110 Action: If the ITT overflow is a transient condition this
20111 message will stop coming out after a few minutes.
20112 If so system operation may return to normal. If
20113 the message comes out repeatedly the system will
20114 have to be crashed since user terminal operation
20115 daemon operations and the message coordinator
20116 depend on wakeups. Follow normal recovery
20117 procedures.
20118
20119
20120
20121
20122
20123
20124
20125
20126
20127 hc_ipc -347- MR12.5 10/27/92^L
20128
20129
20130 hc_ipc.pl1
20131 hc_ipc: Unable to allocate in ring RINGNO ECT for
20132 NAME.PROJ
20133
20134
20135 Stream: Logged in SYSERR log.
20136
20137 Time: While system is running.
20138
20139 Meaning: When a process recieves wakeups they are copied
20140 from the Interprocess Transmission Table to an
20141 Event Channel Table ECT. A process owns one ECT
20142 per ring. If for any reason an entry for a
20143 wakeup cannot be allocated in a process' ECT that
20144 process is terminated.
20145
20146 Action: If the process is a daemon process it must be
20147 reinitialized. If the process is the initializer
20148 process the system will crash.
20149
20150
20151
20152 hc_load_mpc.pl1
20153 hc_load_mpc: Booting channel CHNL with FWID
20154 Revision REV hc_load_mpc: Booting channel CHNL
20155 with FWID Revision REV Overlay FWOVERLAY
20156
20157
20158 Stream: BOS Typewriter.
20159
20160 Time: System Intialization.
20161
20162 Meaning: No operator action is required.
20163
20164 Action: $config
20165
20166
20167
20168 hc_load_mpc.pl1
20169 hc_load_mpc: Could not abs_wire buffer.
20170
20171
20172 Stream: BOS Typewriter Crashes system
20173
20174 Time: System Intialization.
20175
20176 Meaning: This indicates a logic error in the supervisor or
20177 CPU or memory hardware problems.
20178
20179 Action: Contact the system programming staff.
20180
20181
20182
20183
20184
20185 hc_load_mpc -348- MR12.5 10/27/92^L
20186
20187
20188 hc_load_mpc.pl1
20189 hc_load_mpc: data buffer not in low 256K
20190
20191
20192 Stream: BOS Typewriter Crashes system
20193
20194 Time: System Intialization.
20195
20196 Meaning: This indicates a logic error in the supervisor or
20197 CPU or memory hardware problems.
20198
20199 Action: Contact the system programming staff.
20200
20201
20202
20203
20204
20205 hc_page_trace.pl1
20206 hc_page_trace: pds$trace.threshold found zero for
20207 USER.
20208
20209
20210 Meaning: The signalling threshold for page tracing was
20211 found to be zero for USER. This indicates that
20212 the user's pds has been damaged.
20213
20214 Stream: BOS Typewriter Terminates user process
20215
20216 Time: While system is running.
20217
20218 Action: Investigate the saved dead process.
20219
20220
20221
20222 ibm3270_mpx.pl1
20223 ibm3270_mpx: Attempt to queue write while write
20224 queued CHANNEL.SUBCHANNEL
20225
20226
20227 Stream: Logged in SYSERR log.
20228
20229 Time: While system is running.
20230
20231 Meaning: An attempt was made to queue a write while a
20232 previous write was still queued. A dump of the
20233 subchannel entry as defined by the mde structure
20234 in ibm3270_mpx_data.incl.pl1 is included with this
20235 message.
20236
20237 Action: No operator action is required.
20238
20239
20240
20241
20242
20243 ibm3270_mpx -349- MR12.5 10/27/92^L
20244
20245
20246 ibm3270_mpx.pl1
20247 ibm3270_mpx: Buffer tally error on CHANNEL.
20248
20249
20250 Stream: BOS Typewriter Crashes system
20251
20252 Time: While system is running.
20253
20254 Meaning: An attempt was made to add characters to a buffer
20255 which should have fit but couldn't.
20256
20257 Action: Contact the system programming staff.
20258
20259
20260
20261 ibm3270_mpx.pl1
20262 ibm3270_mpx: Could not find queued write on
20263 CHANNEL.
20264
20265
20266 Stream: BOS Typewriter sounds beeper
20267
20268 Time: While system is running.
20269
20270 Meaning: The reset_channel internal procedure could not
20271 find a queued write on CHANNEL or it detected
20272 itself looping in releasing queued writes for
20273 CHANNEL. Will attempt to continue.
20274
20275 Action: Contact the system programming staff.
20276
20277
20278
20279 ibm3270_mpx.pl1
20280 ibm3270_mpx: Error trimming buffer chain for
20281 CHANNEL
20282
20283
20284 Stream: BOS Typewriter Crashes system
20285
20286 Time: While system is running.
20287
20288 Meaning: An inconsistency was found while trimming the
20289 buffer chain for CHANNEL which is stored in
20290 tty_buf.
20291
20292 Action: Contact the system programming staff.
20293
20294
20295
20296
20297
20298
20299
20300
20301 ibm3270_mpx -350- MR12.5 10/27/92^L
20302
20303
20304 ibm3270_mpx.pl1
20305 ibm3270_mpx: Input for illegal device address
20306 DEV_ADDRESS on CHANNEL
20307
20308
20309 Stream: BOS Typewriter.
20310
20311 Time: While system is running.
20312
20313 Meaning: Received input for a device whose address
20314 DEV_ADDRESS is not in the channel map for
20315 CHANNEL.
20316
20317 Action: Contact the system programming staff.
20318
20319
20320
20321 ibm3270_mpx.pl1
20322 ibm3270_mpx: Input for unconfigured device
20323 DEV_ADDRESS on CHANNEL
20324
20325
20326 Stream: BOS Typewriter.
20327
20328 Time: While system is running.
20329
20330 Meaning: Received input for a device DEV_ADDRESS whose
20331 subchannel was <= 0 in the channel map for
20332 CHANNEL.
20333
20334 Action: Contact the system programming staff.
20335
20336
20337
20338 ibm3270_mpx.pl1
20339 ibm3270_mpx: Unrecognized input for CHANNEL:
20340 DATA
20341
20342
20343 Stream: BOS Typewriter.
20344
20345 Time: While system is running.
20346
20347 Meaning: DATA received from CHANNEL does not meet certain
20348 format requirements. This message is only
20349 displayed if in debug mode.
20350
20351 Action: Contact the system programming staff.
20352
20353
20354
20355
20356
20357
20358
20359 ibm3270_mpx -351- MR12.5 10/27/92^L
20360
20361
20362 ibm3270_mpx.pl1
20363 ibm3270_mpx: Unrecognized interrupt for CHANNEL.
20364 INT_TYPE INTERRUPT_INFO
20365
20366
20367 Stream: BOS Typewriter.
20368
20369 Time: While system is running.
20370
20371 Meaning: An interrupt was received from the FNP which does
20372 not have a defined action. The type of interrupt
20373 received is INT_TYPE and the information supplied
20374 with the interrupt is INTERRUPT_INFO.
20375
20376 Action: Contact the system programming staff.
20377
20378
20379
20380 init_branches.pl1
20381 init_branches: $branch From asd_: ERRORMESSAGE
20382
20383
20384 Stream: BOS Typewriter.
20385
20386 Time: System Intialization.
20387
20388 Meaning: This indicates a logic error in the supervisor or
20389 CPU or memory hardware problems. Initialization
20390 continues.
20391
20392 Action: Contact the system programming staff.
20393
20394
20395
20396 init_branches.pl1
20397 init_branches: couldn't add name pdd to
20398 process_dir_dir: ERRORMESSAGE
20399
20400
20401 Stream: BOS Typewriter.
20402
20403 Time: System Intialization.
20404
20405 Meaning: This indicates a logic error in the supervisor or
20406 CPU or memory hardware problems. Initialization
20407 continues. Certain application programs may fail
20408 to work.
20409
20410 Action: Contact the system programming staff.
20411
20412
20413
20414
20415
20416
20417 init_branches -352- MR12.5 10/27/92^L
20418
20419
20420 init_branches.pl1
20421 init_branches: couldn't add name sl1 to
20422 system_library_1: ERRORMESSAGE
20423
20424
20425 Stream: BOS Typewriter.
20426
20427 Time: System Intialization.
20428
20429 Meaning: This indicates a logic error in the supervisor or
20430 CPU or memory hardware problems. Initialization
20431 continues. Certain application programs may fail
20432 to work.
20433
20434 Action: Contact the system programming staff.
20435
20436
20437
20438 init_branches.pl1
20439 init_branches: couldn't set dirquota on >pdd to
20440 XXXX: ERRORMESSAGE
20441
20442
20443 Stream: BOS Typewriter.
20444
20445 Time: System Intialization.
20446
20447 Meaning: This indicates a logic error in the supervisor or
20448 CPU or memory hardware problems. Initialization
20449 continues. The answering service may encounter
20450 trouble in creating processes.
20451
20452 Action: Contact the system programming staff.
20453
20454
20455
20456 init_branches.pl1
20457 init_branches: deleting old pdd: ERRORMESSAGE
20458
20459
20460 Stream: BOS Typewriter Crashes system
20461
20462 Time: System Intialization.
20463
20464 Meaning: The name pdd could not be removed from >pdd. This
20465 indicates a logic error in the supervisor or CPU
20466 or memory hardware problems.
20467
20468 Action: Follow normal recovery procedures.
20469
20470
20471
20472
20473
20474
20475 init_branches -353- MR12.5 10/27/92^L
20476
20477
20478 init_branches.pl1
20479 init_branches: error from initiate. ERRORMESSAGE
20480
20481
20482 Stream: BOS Typewriter Crashes system
20483
20484 Time: System Intialization.
20485
20486 Meaning: A deciduous segment could not be made known. This
20487 indicates a logic error in the supervisor or CPU
20488 or memory hardware problems.
20489
20490 Action: Follow normal recovery procedures.
20491
20492
20493
20494 init_branches.pl1
20495 init_branches: error from set$max_length
20496 ERRORMESSAGE
20497
20498
20499 Stream: BOS Typewriter Crashes system
20500
20501 Time: System Intialization.
20502
20503 Meaning: This indicates a logic error in the supervisor or
20504 CPU or memory hardware problems.
20505
20506 Action: Follow normal recovery procedures.
20507
20508
20509
20510 init_branches.pl1
20511 init_branches: error from terminate_:
20512 ERRORMESSAGE
20513
20514
20515 Stream: BOS Typewriter Crashes system
20516
20517 Time: System Intialization.
20518
20519 Meaning: This indicates a logic error in the supervisor or
20520 CPU or memory hardware problems.
20521
20522 Action: Follow normal recovery procedures.
20523
20524
20525
20526
20527
20528
20529
20530
20531
20532
20533 init_branches -354- MR12.5 10/27/92^L
20534
20535
20536 init_branches.pl1
20537 init_branches: error in adding acl of dumps:
20538 ERRORMESSAGE
20539
20540
20541 Stream: BOS Typewriter.
20542
20543 Time: System Intialization.
20544
20545 Meaning: This indicates a logic error in the supervisor or
20546 CPU or memory hardware problems. Initialization
20547 continues. The copy_fdump command may fail. The
20548 online salvager may fail to make stack and
20549 directory copies in >dumps.
20550
20551 Action: Contact the system programming staff.
20552
20553
20554
20555 init_branches.pl1
20556 init_branches: error in replacing acl of >sl1.
20557 ERRORMESSAGE
20558
20559
20560 Stream: BOS Typewriter.
20561
20562 Time: System Intialization.
20563
20564 Meaning: This indicates a logic error in the supervisor or
20565 CPU or memory hardware problems. Initialization
20566 continues. User and daemon processes may
20567 malfunction.
20568
20569 Action: Contact the system programming staff.
20570
20571
20572
20573 init_branches.pl1
20574 init_branches: From set$max_length: ERRORMESSAGE
20575
20576
20577 Stream: BOS Typewriter Crashes system
20578
20579 Time: System Intialization.
20580
20581 Meaning: This indicates a logic error in the supervisor or
20582 CPU or memory hardware problems.
20583
20584 Action: Follow normal recovery procedures.
20585
20586
20587
20588
20589
20590
20591 init_branches -355- MR12.5 10/27/92^L
20592
20593
20594 init_branches.pl1
20595 init_branches: From status_$long: ERRORMESSAGE
20596
20597
20598 Stream: BOS Typewriter Crashes system
20599
20600 Time: System Intialization.
20601
20602 Meaning: This indicates a logic error in the supervisor or
20603 CPU or memory hardware problems.
20604
20605 Action: Follow normal recovery procedures.
20606
20607
20608
20609 init_branches.pl1
20610 init_branches: getting dir entry pointer:
20611 ERRORMESSAGE
20612
20613
20614 Stream: BOS Typewriter Crashes system
20615
20616 Time: System Intialization.
20617
20618 Meaning: This indicates a logic error in the supervisor or
20619 CPU or memory hardware problems.
20620
20621 Action: Follow normal recovery procedures.
20622
20623
20624
20625 init_branches.pl1
20626 init_branches: Mysterious directory deactivation
20627
20628
20629 Stream: BOS Typewriter Crashes system
20630
20631 Time: System Intialization.
20632
20633 Meaning: This indicates a logic error in the supervisor or
20634 CPU or memory hardware problems.
20635
20636 Action: Follow normal recovery procedures.
20637
20638
20639
20640
20641
20642
20643
20644
20645
20646
20647
20648
20649 init_branches -356- MR12.5 10/27/92^L
20650
20651
20652 init_branches.pl1
20653 init_branches: renaming old pdd: ERRORMESSAGE
20654
20655
20656 Stream: BOS Typewriter Crashes system
20657
20658 Time: System Intialization.
20659
20660 Meaning: This indicates a logic error in the supervisor or
20661 CPU or memory hardware problems.
20662
20663 Action: Follow normal recovery procedures.
20664
20665
20666
20667 init_branches.pl1
20668 init_branches: renaming process_dir_dir:
20669 ERRORMESSAGE
20670
20671
20672 Stream: BOS Typewriter Crashes system
20673
20674 Time: System Intialization.
20675
20676 Meaning: This indicates a logic error in the supervisor or
20677 CPU or memory hardware problems.
20678
20679 Action: Follow normal recovery procedures.
20680
20681
20682
20683 init_branches.pl1
20684 init_branches: replacing >pdd acl: ERRORMESSAGE
20685
20686
20687 Stream: BOS Typewriter.
20688
20689 Time: System Intialization.
20690
20691 Meaning: This indicates a logic error in the supervisor or
20692 CPU or memory hardware problems. Initialization
20693 continues.
20694
20695 Action: Contact the system programming staff.
20696
20697
20698
20699
20700
20701
20702
20703
20704
20705
20706
20707 init_branches -357- MR12.5 10/27/92^L
20708
20709
20710 init_branches.pl1
20711 init_branches: replacing acl of >pdd for
20712 Initializer: ERRORMESSAGE
20713
20714
20715 Stream: BOS Typewriter.
20716
20717 Time: System Intialization.
20718
20719 Meaning: This indicates a logic error in the supervisor or
20720 CPU or memory hardware problems. Initialization
20721 continues.
20722
20723 Action: Contact the system programming staff.
20724
20725
20726
20727 init_branches.pl1
20728 init_branches: unable to append dumps directory.
20729 ERRORMESSAGE
20730
20731
20732 Stream: BOS Typewriter sounds beeper
20733
20734 Time: System Intialization.
20735
20736 Meaning: This indicates a logic error in the supervisor or
20737 CPU or memory hardware problems. Initialization
20738 continues.
20739
20740 Action: Contact the system programming staff.
20741
20742
20743
20744 init_branches.pl1
20745 init_branches: unable to initiate >DIRNAME:
20746 ERRORMESSAGE
20747
20748
20749 Stream: BOS Typewriter Crashes system
20750
20751 Time: System Intialization.
20752
20753 Meaning: This indicates a logic error in the supervisor or
20754 CPU or memory hardware problems.
20755
20756 Action: Follow normal recovery procedures.
20757
20758
20759
20760
20761
20762
20763
20764
20765 init_branches -358- MR12.5 10/27/92^L
20766
20767
20768 init_branches.pl1
20769 init_branches: unable to make >system_library_1:
20770 ERRORMESSAGE
20771
20772
20773 Stream: BOS Typewriter Crashes system
20774
20775 Time: System Intialization.
20776
20777 Meaning: This indicates a logic error in the supervisor or
20778 CPU or memory hardware problems.
20779
20780 Action: Follow normal recovery procedures.
20781
20782
20783
20784 init_branches.pl1
20785 init_branches: unable to make process_dir_dir:
20786 ERRORMESSAGE
20787
20788
20789 Stream: BOS Typewriter Crashes system
20790
20791 Time: System Intialization.
20792
20793 Meaning: This indicates a logic error in the supervisor or
20794 CPU or memory hardware problems.
20795
20796 Action: Follow normal recovery procedures.
20797
20798
20799
20800 init_branches.pl1
20801 init_branches: dirquotas for pdir:
20802 ERRORMESSAGE
20803
20804
20805 Stream: BOS Typewriter.
20806
20807 Time: System Intialization.
20808
20809 Meaning: This indicates a logic error in the supervisor or
20810 CPU or memory hardware problems. Initialization
20811 continues.
20812
20813 Action: Contact the system programming staff.
20814
20815
20816
20817
20818
20819
20820
20821
20822
20823 init_branches -359- MR12.5 10/27/92^L
20824
20825
20826 init_disk_pack_.pl1
20827 init_disk_pack_: Specified control argument not
20828 accepted. "-rlv" allowed only at ring-1 during a
20829 cold boot.
20830
20831
20832 Stream: Initializer process output.
20833
20834 Time: In response to an operator command.
20835
20836 Meaning: Automatic registration of root PVs is allowed only
20837 during a cold boot of Multics.
20838
20839 Action: Use the "add_volume_registration" administrative
20840 command to register the PV before attempting to
20841 initialize it.
20842
20843
20844
20845 init_disk_pack_.pl1
20846 init_disk_pack_: Cannot read current label of
20847 DRIVE: ERROR_MESSAGE
20848
20849
20850 Stream: Initializer process output.
20851
20852 Time: In response to an operator command.
20853
20854 Meaning: A disk error prevents checking the label of the
20855 pack on DRIVE. The pack may need to be formatted
20856 before it can be initialized.
20857
20858 Action: Take appropriate action.
20859
20860
20861
20862 init_disk_pack_.pl1
20863 init_disk_pack_: DRIVE PVNAME disk err WWWW on
20864 ITEM
20865
20866
20867 Stream: Initializer process output.
20868
20869 Time: In response to an operator command.
20870
20871 Meaning: A disk error prevents writing the ITEM section of
20872 the disk volume PVNAME.
20873
20874 Action: Fix the drive or use a new pack.
20875
20876
20877
20878
20879
20880
20881 init_disk_pack_ -360- MR12.5 10/27/92^L
20882
20883
20884 init_disk_pack_.pl1
20885 init_disk_pack_: INTK card missing from config
20886 deck.
20887
20888
20889 Stream: Initializer process output.
20890
20891 Time: In response to an operator command.
20892
20893 Meaning: When the operator specifies the "-rlv" control
20894 argument to "init_vol" this program attempts to
20895 verify that the system is in cold boot by
20896 inspecting the INTK card in the config deck. When
20897 this message appears there is some difficulty in
20898 locating that card.
20899
20900 Action: If really trying to boot cold try again.
20901
20902
20903
20904 init_disk_pack_.pl1
20905 init_disk_pack_: unrecognized argument: BLAH
20906
20907
20908 Stream: Initializer process output.
20909
20910 Time: In response to an operator command.
20911
20912 Meaning: Illegal input was typed.
20913
20914 Action: Enter a corrected command line.
20915
20916
20917
20918 init_disk_pack_.pl1
20919 init_disk_pack_: Volume on DRIVE is a copy of
20920 Multics Storage System Volume "PVNAME"
20921 last used DATE_TIME. Do you wish to overwrite it?
20922
20923
20924 Stream: Initializer process output.
20925
20926 Time: In response to an operator command.
20927
20928 Meaning: The init_disk command specifed a disk pack which
20929 has a valid Multics label. Another copy of PVNAME
20930 is currently in use. Initializing this pack will
20931 destroy all data contained on it.
20932
20933 Action: Do not answer yes unless you are sure that the
20934 pack contents should be destroyed. Check the pack
20935 serial number.
20936
20937
20938
20939 init_disk_pack_ -361- MR12.5 10/27/92^L
20940
20941
20942 init_disk_pack_.pl1
20943 init_disk_pack_: Volume on DRIVE is a copy of pv
20944 "PVNAME"
20945 last used DATE_TIME. Do you wish to overwrite it?
20946
20947
20948 Stream: Initializer process output.
20949
20950 Time: In response to an operator command.
20951
20952 Meaning: The init_disk command specifed a disk pack which
20953 has a valid Multics label. It appears to be a
20954 copy of a mounted pack. Initializing this pack
20955 will destroy all data contained on it.
20956
20957 Action: Do not answer yes unless you are sure that the
20958 pack contents should be destroyed. Check the pack
20959 serial number.
20960
20961
20962
20963 init_disk_pack_.pl1
20964 init_disk_pack_: Volume on DRIVE is an earlier
20965 instance of pv "PVNAME"
20966 last used DATE_TIME. Do you wish to overwrite it?
20967
20968
20969 Stream: Initializer process output.
20970
20971 Time: In response to an operator command.
20972
20973 Meaning: The init_disk command specifed a disk pack which
20974 has a valid Multics label. Initializing this pack
20975 will destroy all data contained on it.
20976
20977 Action: Do not answer yes unless you are sure that the
20978 pack contents should be destroyed. Check the pack
20979 serial number.
20980
20981
20982
20983
20984
20985
20986
20987
20988
20989
20990
20991
20992
20993
20994
20995
20996
20997 init_disk_pack_ -362- MR12.5 10/27/92^L
20998
20999
21000 init_disk_pack_.pl1
21001 init_disk_pack_: Volume on DRIVE is an
21002 unregistered pack named "PVNAME"
21003 last used DATE_TIME. Do you wish to overwrite it?
21004
21005
21006 Stream: Initializer process output.
21007
21008 Time: In response to an operator command.
21009
21010 Meaning: The init_disk command specifed a disk pack which
21011 has a valid Multics label. Initializing this pack
21012 will destroy all data contained on it.
21013
21014 Action: Do not answer yes unless you are sure that the
21015 pack contents should be destroyed. Check the pack
21016 serial number.
21017
21018
21019
21020 init_disk_pack_.pl1
21021 init_disk_pack_: Volume on DRIVE is Multics
21022 Storage System Volume "PVNAME"
21023 last used DATE_TIME. Do you wish to overwrite it?
21024
21025
21026 Stream: Initializer process output.
21027
21028 Time: In response to an operator command.
21029
21030 Meaning: The init_disk command specifed a disk pack which
21031 has a valid Multics label. Initializing this pack
21032 will destroy all data contained on it.
21033
21034 Action: Do not answer yes unless you are sure that the
21035 pack contents should be destroyed. Check the pack
21036 serial number.
21037
21038
21039
21040
21041
21042
21043
21044
21045
21046
21047
21048
21049
21050
21051
21052
21053
21054
21055 init_disk_pack_ -363- MR12.5 10/27/92^L
21056
21057
21058 init_dm_journal_seg.pl1
21059 init_dm_journal_seg: Invalid DBMJ config card.
21060
21061
21062 Stream: BOS Typewriter Crashes system
21063
21064 Time: System Intialization.
21065
21066 Meaning: The DBMJ configuration card is not in proper
21067 format. This could be a format error or one of
21068 the following criteria may not be satisfied. The
21069 limit on active segments for a pool must be
21070 smaller than the pool size.
21071
21072 Action: Correct the configuration deck and reboot.
21073
21074
21075
21076 init_dm_journal_seg.pl1
21077 init_dm_journal_seg: make_sdw failed for
21078 dm_journal_seg_
21079
21080
21081 Stream: BOS Typewriter Crashes system
21082
21083 Time: System Intialization.
21084
21085 Meaning: The ASTE for dm_journal_seg_ could not be created.
21086
21087 Action: Contact the system programming staff.
21088
21089
21090
21091 init_early_config.pl1
21092 init_early_config: Cannot add card to config
21093 deck: CARD.
21094
21095
21096 Stream: BOS Typewriter Crashes system
21097
21098 Time: System Intialization.
21099
21100 Meaning: The config_deck being generated during the early
21101 hardware inspection pass of bce is damaged.
21102 This can be either a hardware or software problem.
21103
21104 Action: $reboot
21105
21106
21107
21108
21109
21110
21111
21112
21113 init_early_config -364- MR12.5 10/27/92^L
21114
21115
21116 init_hc_part.pl1
21117 init_hc_part: HC PART on dskX_NN too small
21118
21119
21120 Stream: BOS Typewriter Crashes system
21121
21122 Time: System Intialization.
21123
21124 Meaning: The Hardcore Partition on the device indicated is
21125 unreasonably small as it does not contain
21126 sufficient space to hold the bit map describing
21127 it.
21128
21129 Action: Recreate the partition and reboot.
21130
21131
21132
21133 init_hc_part.pl1
21134 init_hc_part: volmap_abs_seg size too small
21135
21136
21137 Time: System Intialization.
21138
21139 Stream: BOS Typewriter Crashes system
21140
21141 Meaning: The maximum length of volmap_abs_seg on the MST
21142 header is not sufficient to access an entire
21143 Volume Map.
21144
21145 Action: Recreate the MST with a larger maximum length for
21146 volmap_abs_seg and reboot.
21147
21148
21149
21150 init_lvt.pl1
21151 init_lvt: unable to define RLV code = WWWW
21152
21153
21154 Stream: BOS Typewriter Crashes system
21155
21156 Time: System Intialization.
21157
21158 Meaning: This indicates a logic error in the supervisor or
21159 CPU or memory hardware problems.
21160
21161 Action: Follow normal recovery procedures. The Multics
21162 System Tape may be incorrect. If the problem
21163 persists try another MST.
21164
21165
21166
21167
21168
21169
21170
21171 init_lvt -365- MR12.5 10/27/92^L
21172
21173
21174 init_lvt.pl1
21175 init_lvt: unable to read RPV label code = WWWW
21176
21177
21178 Stream: BOS Typewriter Crashes system
21179
21180 Time: System Intialization.
21181
21182 Meaning: The RPV label which was successfully read a few
21183 seconds ago cannot be read.
21184
21185 Action: Follow normal recovery procedures. The Multics
21186 System Tape may be incorrect. If the problem
21187 persists try another MST.
21188
21189
21190
21191 init_partitions.pl1
21192 init_partition: part PART_NAME for part PART_ID
21193 not in label of DISK_DRIVE pvtx PVTX.
21194
21195
21196 Stream: BOS Typewriter Crashes system
21197
21198 Time: System Intialization.
21199
21200 Meaning: A PART card specified DISK_DRIVE as the location
21201 of partition PART_NAME but the label of
21202 DISK_DRIVE does not define it.
21203
21204 Action: Fix the config deck.
21205
21206
21207
21208 init_partitions.pl1
21209 init_partition: part PART_NAME not in label of
21210 DISK_DRIVE pvtx PVTX.
21211
21212
21213 Stream: BOS Typewriter Crashes system
21214
21215 Time: System Intialization.
21216
21217 Meaning: A PART card specified DISK_DRIVE as the location
21218 of partition PART_NAME but the label of
21219 DISK_DRIVE does not define it.
21220
21221 Action: Fix the config deck.
21222
21223
21224
21225
21226
21227
21228
21229 init_partition -366- MR12.5 10/27/92^L
21230
21231
21232 init_partitions.pl1
21233 init_partition: There are no partitions in the
21234 label for DISK_DRIVE pvtx PVTX.
21235
21236
21237 Stream: BOS Typewriter Crashes system
21238
21239 Time: System Intialization.
21240
21241 Meaning: DISK_DRIVE has been specified on a part card but
21242 has no partitions defined in its label.
21243
21244 Action: Fix the config deck.
21245
21246
21247
21248 init_partitions.pl1
21249 init_partitions: Error reading DISK_DRIVE label.
21250 PROBLEM ERROR_MESSAGE
21251
21252
21253 Stream: BOS Typewriter Crashes system
21254
21255 Time: System Intialization.
21256
21257 Meaning: An error has been detected attempting to read the
21258 label of DISK_DRIVE.
21259
21260 Action: Correct problem and type "go" to retry the read.
21261
21262
21263
21264 init_partitions.pl1
21265 init_partitions: Ignoring COLD_SPEC on PART_NAME
21266 part card.
21267
21268
21269 Stream: BOS Typewriter sounds beeper
21270
21271 Time: System Intialization.
21272
21273 Meaning: Cold boot partition specifications were found for
21274 partition PART_NAME and will be ignored.
21275
21276
21277
21278
21279
21280
21281
21282
21283
21284
21285
21286
21287 init_partitions -367- MR12.5 10/27/92^L
21288
21289
21290 init_partitions.pl1
21291 init_partitions: Invalid device DISK_DRIVE on
21292 PART_NAME part card.
21293
21294
21295 Stream: BOS Typewriter Crashes system
21296
21297 Time: System Intialization.
21298
21299 Meaning: An invalid drive definition has been found for the
21300 PART_NAME part card.
21301
21302 Action: Fix PART card.
21303
21304
21305
21306 init_partitions.pl1
21307 init_partitions: Unable to locate DISK_DRIVE for
21308 PART_NAME partition.
21309
21310
21311 Stream: BOS Typewriter Crashes system
21312
21313 Time: System Intialization.
21314
21315 Meaning: Partition PART_NAME is specified in the config
21316 deck for a non existent DISK_DRIVE.
21317
21318 Action: Fix PART and/or PRPH DSK cards.
21319
21320
21321
21322 init_proc.pl1
21323 init_proc: bad process type N given for
21324 PERSON.PROJ.T
21325
21326
21327 Stream: BOS Typewriter sounds beeper
21328
21329 Time: While system is running.
21330
21331 Meaning: The answering service has specified an unknown
21332 integer in the process type field. Incorrect
21333 arguments were passed to hphcs_$create_proc. The
21334 user cannot be logged in.
21335
21336 Action: Contact the system programming staff.
21337
21338
21339
21340
21341
21342
21343
21344
21345 init_proc -368- MR12.5 10/27/92^L
21346
21347
21348 init_proc.pl1
21349 init_proc: bad syntax in initial procedure name:
21350 STRING for PERSON.PROJ.T
21351
21352
21353 Stream: Logged in SYSERR log.
21354
21355 Time: While system is running.
21356
21357 Meaning: An illegal initial procedure name was specified
21358 for the user. The user may have given an
21359 incorrect -po argument or the project's PDT may
21360 be wrong. No process is created.
21361
21362 Action: No operator action is required.
21363
21364
21365
21366 init_proc.pl1
21367 init_proc: can not call out to initial procedure:
21368 NAME for PERSON.PROJ.T ERROR_MESSAGE
21369
21370
21371 Stream: Logged in SYSERR log.
21372
21373 Time: While system is running.
21374
21375 Meaning: The supervisor could not snap a link to NAME$NAME.
21376 The process overseer may be in invalid form
21377 inaccessible or missing. The user may have given
21378 an incorrect -po argument or the project's PDT
21379 may be incorrect.
21380
21381 Action: No operator action is required.
21382
21383
21384
21385 init_proc.pl1
21386 init_proc: can not get pointer to initial
21387 procedure: PATH for PERSON.PROJ.T ERROR_MESSAGE
21388
21389
21390 Stream: Logged in SYSERR log.
21391
21392 Time: While system is running.
21393
21394 Meaning: The supervisor could not initiate the specified
21395 initial procedure PATH. The process overseer may
21396 be in invalid form inaccessible or missing. The
21397 user may have given an incorrect -po argument or
21398 the project's PDT may be incorrect.
21399
21400 Action: No operator action is required.
21401
21402
21403 init_proc -369- MR12.5 10/27/92^L
21404
21405
21406 init_proc.pl1
21407 init_proc: could not get pointer to pit for
21408 PERSON.PROJ.T ERROR_MESSAGE
21409
21410
21411 Stream: BOS Typewriter sounds beeper
21412
21413 Time: While system is running.
21414
21415 Meaning: The answering service has created the process
21416 directory for a new process incorrectly. The user
21417 cannot be logged in.
21418
21419 Action: Contact the system programming staff.
21420
21421
21422
21423 init_pvt.pl1
21424 init_pvt: Duplicate prph DISK_NAME card.
21425
21426
21427 Stream: BOS Typewriter Crashes system
21428
21429 Time: System Intialization.
21430
21431 Meaning: Two different PRPH cards define DISK_NAME.
21432
21433 Action: Fix the config deck.
21434
21435
21436
21437 init_pvt.pl1
21438 init_pvt: Invalid parm wlim value WLIM. Default
21439 of DEFAULT used.
21440
21441
21442 Stream: BOS Typewriter sounds beeper
21443
21444 Time: System Intialization.
21445
21446 Meaning: An unreasonable value WLIM was found on a PARM
21447 WLIM card. DEFAULT has be substituted.
21448
21449 Action: Fix the config deck.
21450
21451
21452
21453
21454
21455
21456
21457
21458
21459
21460
21461 init_pvt -370- MR12.5 10/27/92^L
21462
21463
21464 init_pvt.pl1
21465 init_pvt: Missing model MODEL on PRPH DISK.
21466
21467
21468 Stream: BOS Typewriter Crashes system
21469
21470 Time: System Intialization.
21471
21472 Meaning: There was no model number specified on the prph
21473 DISK card.
21474
21475 Action: Fix the config deck.
21476
21477
21478
21479 init_pvt.pl1
21480 init_pvt: Missing ndrives field on config card
21481 for DISK subsystem.
21482
21483
21484 Stream: BOS Typewriter Crashes system
21485
21486 Time: System Intialization.
21487
21488 Meaning: The PRPH DSK card for DISK lacks the ndrives
21489 parameter for some model.
21490
21491 Action: Fix the config deck.
21492
21493
21494
21495 init_pvt.pl1
21496 init_pvt: More than N drives defined for XXXX.
21497
21498
21499 Stream: BOS Typewriter Crashes system
21500
21501 Time: System Intialization.
21502
21503 Meaning: The PRPH card for disk subsystem XXXX specified
21504 more than the maximum allowable number of disk
21505 drives.
21506
21507 Action: Follow normal recovery procedures. Correct the
21508 configuration deck and reboot.
21509
21510
21511
21512
21513
21514
21515
21516
21517
21518
21519 init_pvt -371- MR12.5 10/27/92^L
21520
21521
21522 init_pvt.pl1
21523 init_pvt: no PRPH DSKn cards
21524
21525
21526 Stream: BOS Typewriter Crashes system
21527
21528 Time: System Intialization.
21529
21530 Meaning: No PRPH cards describing disk subsystems were
21531 found in the CONFIG deck.
21532
21533 Action: Correct the CONFIG deck to include the correct
21534 PRPH cards to describe the disk subsystems
21535 present and reboot.
21536
21537
21538
21539 init_pvt.pl1
21540 init_pvt: Too many disk subsystems configured.
21541 Limit is NUMBER.
21542
21543
21544 Stream: BOS Typewriter Crashes system
21545
21546 Time: System Intialization.
21547
21548 Meaning: More than NUMBER subsystems are defined. Only
21549 NUMBER are allowed.
21550
21551 Action: Rearrange the config deck for disks and try again.
21552
21553
21554
21555 init_pvt.pl1
21556 init_pvt: Unknown model MODEL on PRPH DISK.
21557
21558
21559 Stream: BOS Typewriter Crashes system
21560
21561 Time: System Intialization.
21562
21563 Meaning: The model number MODEL specified somewhere on the
21564 prph DISK card is not a legal model number.
21565
21566 Action: Fix the config deck.
21567
21568
21569
21570
21571
21572
21573
21574
21575
21576
21577 init_pvt -372- MR12.5 10/27/92^L
21578
21579
21580 init_pvt.pl1
21581 init_pvt: XXXX contains a drive number higher
21582 than N.
21583
21584
21585 Stream: BOS Typewriter Crashes system
21586
21587 Time: System Intialization.
21588
21589 Meaning: The PRPH card for disk subsystem XXXX specified
21590 disks with addresses larger than tha maximum
21591 allowable device number N.
21592
21593 Action: Follow normal recovery procedures. Correct the
21594 configuration deck and reboot.
21595
21596
21597
21598 init_root_dir.pl1
21599 init_root_dir: Error from makeknown on root
21600 ERROR_MESSAGE
21601
21602
21603 Stream: BOS Typewriter Crashes system
21604
21605 Time: System Intialization.
21606
21607 Meaning: This indicates a logic error in the supervisor or
21608 CPU or memory hardware problems.
21609
21610 Action: Reboot with a different version of the system.
21611
21612
21613
21614 init_root_dir.pl1
21615 init_root_dir: Error on root vtoce ERROR_MESSAGE
21616
21617
21618 Stream: BOS Typewriter Crashes system
21619
21620 Time: System Intialization.
21621
21622 Meaning: The supervisor cannot locate the VTOC entry for
21623 the root directory. The RPV may have been
21624 damaged.
21625
21626 Action: Follow normal recovery procedures. A recovery of
21627 the RPV may be required.
21628
21629
21630
21631
21632
21633
21634
21635 init_root_dir -373- MR12.5 10/27/92^L
21636
21637
21638 init_root_dir.pl1
21639 init_root_dir: Root damaged.
21640
21641
21642 Stream: BOS Typewriter Crashes system
21643
21644 Time: System Intialization.
21645
21646 Meaning: The unique ID of the root directory in the
21647 directory header is incorrect. The contents of
21648 the RPV may have been damaged.
21649
21650 Action: Follow normal recovery procedures. A recovery of
21651 the RPV may be required.
21652
21653
21654
21655 init_root_vols.pl1
21656 init_root_vols: Adding config conf partition to
21657 rpv.
21658
21659
21660 Stream: BOS Typewriter.
21661
21662 Time: System Intialization.
21663
21664 Meaning: No conf partition was found on the rpv. It will
21665 be created by extracting 4 records from the hc
21666 partition.
21667
21668 Action: No operator action is required.
21669
21670
21671
21672 init_root_vols.pl1
21673 init_root_vols: Adding bce file log
21674 partitions to rpv.
21675
21676
21677 Stream: BOS Typewriter.
21678
21679 Time: System Intialization.
21680
21681 Meaning: The rpv does not contain the listed partitions.
21682 The pages of the rpv are being arranged to add
21683 these partitions. This operation takes several
21684 minutes.
21685
21686 Action: No operator action is required.
21687
21688
21689
21690
21691
21692
21693 init_root_vols -374- MR12.5 10/27/92^L
21694
21695
21696 init_root_vols.pl1
21697 init_root_vols: bce partition is XXX records
21698 must be YYY.
21699
21700
21701 Stream: BOS Typewriter Crashes system
21702
21703 Time: System Intialization.
21704
21705 Meaning: The bce partition defined on the rpv is not
21706 sufficiently large.
21707
21708 Action: Rebuild the rpv to have a large enough bce
21709 partition. Contact the system programming staff.
21710
21711
21712
21713 init_root_vols.pl1
21714 init_root_vols: DISK_VOL appears twice on root
21715 cards.
21716
21717
21718 Stream: BOS Typewriter Crashes system
21719
21720 Time: System Intialization.
21721
21722 Meaning: The volume DISK_VOL appears more than once on the
21723 ROOT config cards.
21724
21725 Action: Fix the config deck and try again.
21726
21727
21728
21729 init_root_vols.pl1
21730 init_root_vols: DISK_VOL is not the rpv but
21731 rather is VOLUME.
21732
21733
21734 Stream: BOS Typewriter Crashes system
21735
21736 Time: System Intialization.
21737
21738 Meaning: The label for the RPV is inconsistent.
21739 label.root.here does not agree with other data or
21740 an incorrect pack is mounted on the first drive
21741 specified by the "root" card.
21742
21743 Action: Reload/restore or patch the RPV label back
21744 together or correctly mount the RPV.
21745
21746
21747
21748
21749
21750
21751 init_root_vols -375- MR12.5 10/27/92^L
21752
21753
21754 init_root_vols.pl1
21755 init_root_vols: Error adding partitions to rpv on
21756 DISK_VOL. ERROR_MESSAGE
21757
21758
21759 Stream: BOS Typewriter Crashes system
21760
21761 Time: System Intialization.
21762
21763 Meaning: It was not possible to add the new partitions to
21764 the rpv. This message will be preceeded by a more
21765 informative message.
21766
21767 Action: Depending on the previous message either a reboot
21768 should be attempted or the rpv will need to be
21769 rebuilt.
21770
21771
21772
21773 init_root_vols.pl1
21774 init_root_vols: Error reading DISK_VOL label.
21775 PROBLEM ERROR_MESSAGE
21776
21777
21778 Stream: BOS Typewriter Crashes system
21779
21780 Time: System Intialization.
21781
21782 Meaning: An error has been detected attempting to read the
21783 label of DISK_VOL.
21784
21785 Action: Correct problem and type "go" to retry the read.
21786
21787
21788
21789 init_root_vols.pl1
21790 init_root_vols: Error reading RPV label on
21791 DISK_VOL. PROBLEM ERROR_MESSAGE
21792
21793
21794 Stream: BOS Typewriter Crashes system
21795
21796 Time: System Intialization.
21797
21798 Meaning: An error has been detected attempting to read the
21799 label of the RPV.
21800
21801 Action: Correct problem and type "go" to retry the read.
21802
21803
21804
21805
21806
21807
21808
21809 init_root_vols -376- MR12.5 10/27/92^L
21810
21811
21812 init_root_vols.pl1
21813 init_root_vols: Error writing rpv label on
21814 DISK_VOL. ERROR_MESSAGE
21815
21816
21817 Stream: BOS Typewriter Crashes system
21818
21819 Time: System Intialization.
21820
21821 Meaning: An i/o prevented updating the rpv label to show
21822 the new partitions.
21823
21824 Action: Correct problem and type "go" to retry the write.
21825
21826
21827
21828 init_root_vols.pl1
21829 init_root_vols: Invalid device on root card
21830 DISK_VOL.
21831
21832
21833 Stream: BOS Typewriter Crashes system
21834
21835 Time: System Intialization.
21836
21837 Meaning: A root card has been found with an invalid
21838 DISK_VOL.
21839
21840 Action: Change the config deck and try again.
21841
21842
21843
21844 init_root_vols.pl1
21845 init_root_vols: Maximum of LIMIT RLV vols has
21846 been exceeded.
21847
21848
21849 Stream: BOS Typewriter Crashes system
21850
21851 Time: System Intialization.
21852
21853 Meaning: The "root" card in the config deck specified more
21854 RLV volumes than the system can handle.
21855
21856 Action: Change the config deck and try again.
21857
21858
21859
21860
21861
21862
21863
21864
21865
21866
21867 init_root_vols -377- MR12.5 10/27/92^L
21868
21869
21870 init_root_vols.pl1
21871 init_root_vols: No part hc on RPV volume
21872 DISK_VOL.
21873
21874
21875 Stream: BOS Typewriter Crashes system
21876
21877 Time: System Intialization.
21878
21879 Meaning: Disk DISK_VOL was specified on a "root" card as
21880 the RPV but does not have a hardcore hc
21881 partition.
21882
21883 Action: The "root" card is incorrect or the wrong pack is
21884 mounted on the first drive described by the "root"
21885 cards.
21886
21887
21888
21889 init_root_vols.pl1
21890 init_root_vols: No room in rpv label for conf
21891 partition.
21892
21893
21894 Stream: BOS Typewriter Crashes system
21895
21896 Time: BOS Typewriter.
21897
21898 Meaning: The partition map for the rpv did not have
21899 sufficient room to add the conf partition.
21900
21901 Action: The rpv will need to be rebuilt. Contact the
21902 system programming staff.
21903
21904
21905
21906 init_root_vols.pl1
21907 init_root_vols: No room in rpv label for
21908 partitions.
21909
21910
21911 Stream: BOS Typewriter Crashes system
21912
21913 Time: System Intialization.
21914
21915 Meaning: The rpv label does not have enough room in the
21916 partition map for the new bce file or log
21917 partitions.
21918
21919 Action: The rpv will need to be rebuilt. Contact the
21920 system programming staff.
21921
21922
21923
21924
21925 init_root_vols -378- MR12.5 10/27/92^L
21926
21927
21928 init_root_vols.pl1
21929 init_root_vols: No root card.
21930
21931
21932 Stream: BOS Typewriter Crashes system
21933
21934 Time: System Intialization.
21935
21936 Meaning: No "root" cards were found in the config deck.
21937 At least one must be present defining the RPV and
21938 other RLV volumes.
21939
21940 Action: Fix the config deck and reboot.
21941
21942
21943
21944 init_root_vols.pl1
21945 init_root_vols: root card specifies nonexistent
21946 drive DISK_VOL.
21947
21948
21949 Stream: BOS Typewriter Crashes system
21950
21951 Time: System Intialization.
21952
21953 Meaning: The volume DISK_VOL specified in the config deck
21954 is not defined by the prph dskX cards.
21955
21956 Action: Fix the config deck and reboot.
21957
21958
21959
21960 init_root_vols.pl1
21961 init_root_vols: RPV not found.
21962
21963
21964 Stream: BOS Typewriter Crashes system
21965
21966 Time: System Intialization.
21967
21968 Meaning: None of the disk volumes specified in the "root"
21969 cards admitted to being the RPV.
21970
21971 Action: Check to be sure the drive on which the RPV is
21972 mounted is specified first on the "root" cards.
21973
21974
21975
21976
21977
21978
21979
21980
21981
21982
21983 init_root_vols -379- MR12.5 10/27/92^L
21984
21985
21986 init_root_vols.pl1
21987 init_root_vols: RPV specified in the
21988 configuration deck DRIVE does not match
21989 sys_boot_info DRIVE.
21990
21991
21992 Stream: BOS Typewriter Crashes system
21993
21994 Time: System Intialization.
21995
21996 Meaning: The RPV defined on the root card is not the same
21997 as the RPV that is currently being used.
21998
21999 Action: Fix the config deck and try again.
22000
22001
22002
22003 init_scavenger_data.pl1
22004 init_scavenger_data: scavenger_data
22005 inconsistency.
22006
22007
22008 Time: System Intialization.
22009
22010 Stream: BOS Typewriter Crashes system
22011
22012 Meaning: An error was encountered initializing the
22013 scavenger's data base.
22014
22015 Action: Contact the system programming staff.
22016
22017
22018
22019 init_scavenger_data.pl1
22020 init_scavenger_data: scavenger_data too small.
22021
22022
22023 Stream: BOS Typewriter Crashes system
22024
22025 Time: System Intialization.
22026
22027 Meaning: The size of the scavenger_data segment is too
22028 small. It can be increased by the TBLS SCAV
22029 config card. It must be at least 68KW with an
22030 additional 67KW for each additional process
22031 beyond 1 which is to be scavenging
22032 simultaneously.
22033
22034 Action: Correct the configuration deck and reboot.
22035
22036
22037
22038
22039
22040
22041 init_scavenger_data -380- MR12.5 10/27/92^L
22042
22043
22044 init_scu.pl1
22045 init_scu: Warning - Not all of MEM Y will be
22046 used.
22047
22048
22049 Stream: BOS Typewriter.
22050
22051 Time: System Intialization.
22052
22053 Meaning: The actual amount of memory present in MEM Y does
22054 not agree with the config deck. Only as much as
22055 the configuration deck specifies will be used.
22056
22057 Action: If this is an unintentional error correct the
22058 configuration deck before the next bootload.
22059
22060
22061
22062 init_sst.pl1
22063 init_sst: insufficient storage available for
22064 sst_seg and core map.
22065
22066
22067 Stream: BOS Typewriter Crashes system
22068
22069 Time: System Intialization.
22070
22071 Meaning: Not enough main storage was available to create
22072 the sst_seg during initialization. The system
22073 tape may be bad or the configuration may be too
22074 small or the system parameters specified in the
22075 configuration deck may be incorrect or
22076 inconsistent with the amount of main storage
22077 available.
22078
22079 Action: Follow normal recovery procedures. Check the
22080 configuration and the CONFIG deck The Multics
22081 System Tape may be incorrect. If the problem
22082 persists try another MST.
22083
22084
22085
22086 init_sst.pl1
22087 init_sst: No SST card in config deck. One has
22088 been added: SST N N N N
22089
22090
22091 Stream: BOS Typewriter sounds beeper
22092
22093 Time: System Intialization.
22094
22095 Meaning: No SST card was found in the config deck. ASTE
22096 pool sizes of N N N N have been set as defaults.
22097
22098
22099 init_sst -381- MR12.5 10/27/92^L
22100
22101
22102 init_stack_0.pl1
22103 init_stack_0: Error creating >sl1>XXXXXX from
22104 YYYYY. Retrying.
22105
22106
22107 Stream: BOS Typewriter.
22108
22109 Time: System Intialization.
22110
22111 Meaning: An error was encountered in creating the stack_0
22112 segment XXXXXX. The error was returned by module
22113 YYYYYY and is described in detail in the
22114 following message. init_stack_0 will attempt to
22115 correct the problem by renaming the segment XXXXXX
22116 to stack_0.<unique name> deleting it and
22117 retrying the creation of segment XXXXXX once.
22118
22119 Action: No action is required if the above actions correct
22120 the problem. If the message persists it may be
22121 symptomatic of hardware or software problems and
22122 it should be brought to the attention of the
22123 System Programming Staff.
22124
22125
22126
22127 init_stack_0.pl1
22128 init_stack_0: Error creating >sl1>XXXXXX from
22129 YYYYYY. Stack skipped.
22130
22131
22132 Stream: BOS Typewriter.
22133
22134 Time: System Intialization.
22135
22136 Meaning: An error was encountered in creating the stack_0
22137 segment XXXXXX. The error was returned by module
22138 YYYYYY and is described in detail in the
22139 following message. This error could not be
22140 corrected by renaming the segment XXXXXX to
22141 stack_0.<unique name> deleting it and retrying
22142 the creation of segment XXXXXX once. The stack_0
22143 represented by segment XXXXXX is skipped and
22144 there will be one fewer stack_0 than specified by
22145 the max_max_eligible tuning parameter for each
22146 message of this sort.
22147
22148 Action: This message may be symptomatic of hardware or
22149 software problems. It should be brought to the
22150 attention of the System Programming Staff.
22151
22152
22153
22154
22155
22156
22157 init_stack_0 -382- MR12.5 10/27/92^L
22158
22159
22160 init_sys_var.pl1
22161 init_sys_var: max_hproc_segno < hcscnt of XXX
22162
22163
22164 Stream: BOS Typewriter Crashes system
22165
22166 Time: System Intialization.
22167
22168 Meaning: The upper bound of the descriptor segment for
22169 hardcore processes is too small. This indicates a
22170 logic error in the supervisor or CPU or memory
22171 hardware problems.
22172
22173 Action: Follow normal recovery procedures. The Multics
22174 System Tape may be incorrect. If the problem
22175 persists try another MST.
22176
22177
22178
22179 init_syserr_log.pl1
22180 init_syserr_log: Cannot create logger process.
22181 ERROR-MESSAGE
22182
22183
22184 Stream: BOS Typewriter.
22185
22186 Time: System Intialization.
22187
22188 Meaning: This indicates a logic error in the supervisor or
22189 CPU or memory hardware problems. No syserr
22190 messages will be logged during this bootload.
22191
22192 Action: Follow normal recovery procedures.
22193
22194
22195
22196 init_syserr_log.pl1
22197 init_syserr_log: Cannot get last message info
22198 from paged syserr log PTR. ERROR-MESSAGE
22199
22200
22201 Stream: BOS Typewriter.
22202
22203 Time: System Intialization.
22204
22205 Meaning: This indicates a logic error in the supervisor or
22206 CPU or memory hardware problems.
22207
22208 Action: Follow normal recovery procedures. It may be
22209 necessary to reinitialize the LOG partition with
22210 the BCE test_disk command after this error.
22211
22212
22213
22214
22215 init_syserr_log -383- MR12.5 10/27/92^L
22216
22217
22218 init_syserr_log.pl1
22219 init_syserr_log: Cannot get service bit from
22220 paged syserr log PTR. MESSAGE
22221
22222
22223 Stream: BOS Typewriter.
22224
22225 Time: System Intialization.
22226
22227 Meaning: This indicates a logic error in the supervisor or
22228 CPU or memory hardware problems.
22229 Some error occurred when attempting to
22230 check the in service bit
22231 for the specified ring 0 paged log
22232 segment.
22233
22234 Action: No operator action is required.
22235 The log partition will be automatically
22236 reinitialized.
22237
22238
22239
22240 init_syserr_log.pl1
22241 init_syserr_log: Cannot initialize paged syserr
22242 log PTR.
22243
22244
22245 Stream: BOS Typewriter Crashes system
22246
22247 Time: System Intialization.
22248
22249 Meaning: This indicates a logic error in the supervisor or
22250 CPU or memory hardware problems.
22251
22252 Action: Follow normal recovery procedures.
22253
22254
22255
22256 init_syserr_log.pl1
22257 init_syserr_log: Cannot write initial message to
22258 paged syserr log PTR. ERROR-MESSAGE
22259
22260
22261 Stream: BOS Typewriter Crashes system
22262
22263 Time: System Intialization.
22264
22265 Meaning: This indicates a logic error in the supervisor or
22266 CPU or memory hardware problems.
22267
22268 Action: Follow normal recovery procedures. It may be
22269 necessary to reinitialize the LOG partition with
22270 the BCE test_disk command after this error.
22271
22272
22273 init_syserr_log -384- MR12.5 10/27/92^L
22274
22275
22276 init_syserr_log.pl1
22277 init_syserr_log: Converting MR10.2 syserr
22278 partition.
22279
22280
22281 Stream: BOS Typewriter.
22282
22283 Time: System Intialization.
22284
22285 Meaning: This message occurs during the first bootload with
22286 an MR11.0 system tape and indicates that the LOG
22287 partition is now in the new format.
22288
22289 Action: No operator action is required.
22290
22291
22292
22293 init_syserr_log.pl1
22294 init_syserr_log: LOG partition damaged.
22295 Reinitializing.
22296
22297
22298 Stream: BOS Typewriter sounds beeper
22299
22300 Time: System Intialization.
22301
22302 Meaning: The LOG partition has been damaged. Some messages
22303 may be lost if the previous shutdown was caused by
22304 a crash. The partition is automatically
22305 reinitialized.
22306
22307 Action: Follow normal recovery procedures.
22308
22309
22310
22311
22312
22313
22314
22315
22316
22317
22318
22319
22320
22321
22322
22323
22324
22325
22326
22327
22328
22329
22330
22331 init_syserr_log -385- MR12.5 10/27/92^L
22332
22333
22334 init_syserr_log.pl1
22335 init_syserr_log: No LOG partition found syserr
22336 logging disabled.
22337
22338
22339 Stream: BOS Typewriter Crashes system
22340
22341 Time: System Intialization.
22342
22343 Meaning: The system requires a LOG partition on the RPV
22344 disk to hold syserr messages before they are
22345 copied into >sc1>syserr_log. This partition must
22346 exist on the volume and be defined by a "PART
22347 LOG" card in the config deck.
22348
22349 Action: Create a LOG partition on the RPV and define it in
22350 the config deck then re-boot. The LOG partition
22351 should be at least 200 records long and may be as
22352 large as 513.
22353
22354
22355
22356 init_syserr_log.pl1
22357 init_syserr_log: Service bit off for live paged
22358 syserr log PTR.
22359
22360
22361 Stream: BOS Typewriter.
22362
22363 Time: System Intialization.
22364
22365 Meaning: The in service flag for the specified ring 0 paged
22366 log segment
22367 was found off. Being this is supposed
22368 to be the live log an
22369 error is indicated. This may occur when
22370 booting after a system
22371 crash.
22372
22373 Action: No operator action is required.
22374 The syserr log partition will be
22375 automatically reinitialized.
22376
22377
22378
22379
22380
22381
22382
22383
22384
22385
22386
22387
22388
22389 init_syserr_log -386- MR12.5 10/27/92^L
22390
22391
22392 init_syserr_log.pl1
22393 init_syserr_log: Size of PTR larger on disk than
22394 in header.
22395
22396
22397 Stream: BOS Typewriter Crashes system
22398
22399 Time: System Intialization.
22400
22401 Meaning: The LOG partition has been damaged. Some messages
22402 may be lost if the previous shutdown was caused by
22403 a crash.
22404
22405 Action: Reinitialize the LOG partition with the BCE
22406 test_disk command and re-boot.
22407
22408
22409
22410 init_syserr_log.pl1
22411 init_syserr_log: Size of wired log is
22412 inconsistent.
22413
22414
22415 Stream: BOS Typewriter Crashes system
22416
22417 Time: System Intialization.
22418
22419 Meaning: The definitions in syserr_data.cds are
22420 inconsistent with those in syserr_data.incl.pl1.
22421 This indicates a programming error.
22422
22423 Action: Follow normal recovery procedures.
22424
22425
22426
22427 init_syserr_log.pl1
22428 init_syserr_log: Unable to retrieve IPC operands
22429 from APTE. Syserr log copying disabled.
22430
22431
22432 Stream: BOS Typewriter.
22433
22434 Time: System Intialization.
22435
22436 Meaning: This indicates a logic error in the supervisor or
22437 CPU or memory hardware problems. No syserr
22438 messages will be logged during this bootload.
22439
22440 Action: Follow normal recovery procedures.
22441
22442
22443
22444
22445
22446
22447 init_syserr_log -387- MR12.5 10/27/92^L
22448
22449
22450 init_toehold.pl1
22451 init_toehold: No "bce" partition on rpv. Rebuild
22452 the RPV to add one.
22453
22454
22455 Stream: BOS Typewriter Crashes system
22456
22457 Time: System Intialization.
22458
22459 Meaning: The partition used to hold the bootload command
22460 environment is missing from the rpv.
22461
22462 Action: A rebuild of the rpv is necessary.
22463
22464
22465
22466 init_toehold.pl1
22467 init_toehold: Unable to save bootload Multics
22468 image to disk.
22469
22470
22471 Stream: BOS Typewriter Crashes system
22472
22473 Time: System Intialization.
22474
22475 Meaning: An i/o error prevented the establishment of the
22476 bce crash handler.
22477
22478
22479
22480 init_toehold.pl1
22481 init_toehold: Unable to save safe_config_deck to
22482 disk.
22483
22484
22485 Stream: BOS Typewriter sounds beeper
22486
22487 Time: System Intialization.
22488
22489 Meaning: The safe_config_deck used to re-establish bce
22490 when a failure of bce itself occurs could not be
22491 updated to disk. A future failure of bce may be
22492 catastrophic.
22493
22494 Action: Try performing a reinitialize operation making
22495 sure that the config deck is perfect.
22496
22497
22498
22499
22500
22501
22502
22503
22504
22505 init_toehold -388- MR12.5 10/27/92^L
22506
22507
22508 init_volmap_seg.pl1
22509 init_volmap_seg: Records left on dskX_NNPVNAME
22510 changed from X to Y.
22511
22512
22513 Stream: Logged in SYSERR log.
22514
22515 Time: During system initialization as physical volumes
22516 of the Root Logical Volume RLV are accepted
22517 during system start_up as physical volumes which
22518 were mounted at the last shutdown are accepted or
22519 when a physical volume is mounted and accepted.
22520
22521 Meaning: A VTOC header was encountered which did not agree
22522 with the Volume Map. This will occur when a
22523 volume which was not shut down properly is
22524 mounted.
22525
22526 Action: Contact the system programming staff.
22527
22528
22529
22530 init_volmap_seg.pl1
22531 init_volmap_seg: Unable to get NK ASTE for
22532 volmap_seg.
22533
22534
22535 Stream: BOS Typewriter Crashes system
22536
22537 Time: During system initialization as physical volumes
22538 of the Root Logical Volume RLV are accepted
22539 during system start_up as physical volumes which
22540 were mounted at the last shutdown are accepted or
22541 when a physical volume is mounted and accepted.
22542
22543 Meaning: An NK ASTE was not available for accessing the
22544 Volume Map. The most likely cause is an ASTE pool
22545 size which is too small.
22546
22547 Action: Follow normal recovery procedures. Increase the
22548 number of ASTEs in the appropriate pool by means
22549 of the SST configuration card.
22550
22551
22552
22553
22554
22555
22556
22557
22558
22559
22560
22561
22562
22563 init_volmap_seg -389- MR12.5 10/27/92^L
22564
22565
22566 init_volmap_seg.pl1
22567 init_volmap_seg: Unable to get NK ASTE for VTOC
22568 header.
22569
22570
22571 Stream: BOS Typewriter Crashes system
22572
22573 Time: During system initialization as physical volumes
22574 of the Root Logical Volume RLV are accepted
22575 during system start_up as physical volumes which
22576 were mounted at the last shutdown are accepted or
22577 when a physical volume is mounted and accepted.
22578
22579 Meaning: An NK ASTE was not available for accessing the
22580 VTOC header. The most likely cause is an ASTE
22581 pool size which is too small.
22582
22583 Action: Follow normal recovery procedures. Increase the
22584 number of ASTEs in the appropriate pool by means
22585 of the SST configuration card.
22586
22587
22588
22589 init_volmap_seg.pl1
22590 init_volmap_seg: Unable to initialize dumper map
22591 for dskX_NNPVNAME
22592
22593
22594 Stream: BOS Typewriter.
22595
22596 Time: During system initialization as physical volumes
22597 of the Root Logical Volume RLV are accepted
22598 during system start_up as physical volumes which
22599 were mounted at the last shutdown are accepted or
22600 when a physical volume is mounted and accepted.
22601
22602 Meaning: An unexpected error was encountered in
22603 initializing the backup queue bit map for the
22604 Physical Volume Dumper. The volume on which the
22605 error occurred cannot be backed up with the
22606 Physical Volume Dumper.
22607
22608 Action: Contact the system programming staff.
22609
22610
22611
22612
22613
22614
22615
22616
22617
22618
22619
22620
22621 init_volmap_seg -390- MR12.5 10/27/92^L
22622
22623
22624 init_volmap_seg.pl1
22625 init_volmap_seg: VTOCEs left on dskX_NNPVNAME
22626 changed from X to Y.
22627
22628
22629 Stream: Logged in SYSERR log.
22630
22631 Time: During system initialization as physical volumes
22632 of the Root Logical Volume RLV are accepted
22633 during system start_up as physical volumes which
22634 were mounted at the last shutdown are accepted or
22635 when a physical volume is mounted and accepted.
22636
22637 Meaning: A VTOC header was encountered which did not agree
22638 with the VTOC Map. This will occur when a volume
22639 which was not shut down properly is mounted.
22640
22641 Action: Contact the system programming staff.
22642
22643
22644
22645 init_volmap_seg.pl1
22646 init_volmap_seg: YYYY volume inconsistencies on
22647 dskX_NNPVNAME. UUUU records left. VVVV VTOCEs
22648 left.
22649
22650
22651 Stream: Logged only if the number of free records and the
22652 number of free VTOCEs are both above thresholds.
22653 Logged and printed on the console if either is
22654 below threshold.
22655
22656 Time: During system initialization as physical volumes
22657 of the Root Logical Volume RLV are accepted
22658 during system start_up as physical volumes which
22659 were mounted at the last shutdown are accepted or
22660 when a physical volume is mounted and accepted.
22661
22662 Meaning: The volume was not shut down properly or
22663 inconsistencies were detected while the volume was
22664 mounted. The effect of these inconsistencies is
22665 that free records and free VTOCEs are lost to the
22666 system. Lost records and VTOCEs can be recovered
22667 by a volume salvage.
22668
22669 Action: Contact the system programming staff.
22670
22671
22672
22673
22674
22675
22676
22677
22678
22679 init_volmap_seg -391- MR12.5 10/27/92^L
22680
22681
22682 init_vtoc_man.pl1
22683 init_vtoc_man: Unexpected error from absadr.
22684 Code XX.
22685
22686
22687 Stream: BOS Typewriter Crashes system
22688
22689 Time: System Intialization.
22690
22691 Meaning: The absolute address of vtoc_buffer_seg could not
22692 be determined. This indicates hardware or
22693 software malfunction.
22694
22695 Action: Follow normal recovery procedures.
22696
22697
22698
22699 real_initializer.pl1.pmac
22700 initializer: Bad root volume.
22701
22702
22703 Stream: BOS Typewriter Crashes system
22704
22705 Time: System Intialization.
22706
22707 Meaning: A volume specified on a ROOT card was found ill
22708 formatted by init_root_vols.
22709
22710 Action: Follow normal recovery procedures.
22711
22712
22713
22714 real_initializer.pl1.pmac
22715 initializer: bad_dir_ signal raised
22716
22717
22718 Stream: BOS Typewriter Crashes system
22719
22720 Time: System Intialization.
22721
22722 Meaning: During system bootload directory control has
22723 encountered an invalid directory. This usually
22724 occurs due to damage to the root or to
22725 >system_control_1. The RPV is automatically
22726 scheduled for volume salvage.
22727
22728 Action: Follow normal recovery procedures.
22729
22730
22731
22732
22733
22734
22735
22736
22737 initializer -392- MR12.5 10/27/92^L
22738
22739
22740 real_initializer.pl1.pmac
22741 initializer: ENTRY_TO_CALL check_stop.
22742
22743
22744 Stream: BOS Typewriter sounds beeper
22745
22746 Time: System Intialization.
22747
22748 Meaning: The initializer has detected that the first nine
22749 data switches on the CPU contain an octal "123"
22750 and the STOP number of the entry to be called and
22751 the current collection_1_phase match the other CPU
22752 data switches. The initializer calls BCE after
22753 displaying this message but before actually
22754 calling the entry. The CPU data switches have the
22755 following usage:
22756
22757 0 - 8: must be set to an octal "123" for any
22758 other switches to be valid.
22759 9 - 14: area for the BCD value of the
22760 collection_1_phase to stop in.
22761 15 - 20: area for the BCD hundreds digit of the
22762 STOP number.
22763 21 - 26: area for the BCD tens digit of the STOP
22764 number.
22765 27 - 32: area for the BCD ones digit of the STOP
22766 number.
22767 33 - 35: not used or checked.
22768
22769 Action: Execute any BCE functions desired. Modify the
22770 setting of the CPU data switches as required.
22771 Execute the BCE "go" function to resume
22772 initialization.
22773
22774
22775
22776 real_initializer.pl1.pmac
22777 initializer: intk card missing.
22778
22779
22780 Stream: BOS Typewriter Crashes system
22781
22782 Time: System Intialization.
22783
22784 Meaning: No "intk" card was found in the config deck.
22785
22786 Action: $config
22787
22788
22789
22790
22791
22792
22793
22794
22795 initializer -393- MR12.5 10/27/92^L
22796
22797
22798 real_initializer.pl1.pmac
22799 initializer: Multics SYSID VERSION syserr
22800 logging initialized.
22801
22802
22803 Stream: Logged in SYSERR log.
22804
22805 Time: System Intialization.
22806
22807 Meaning: This is the first syserr message produced by every
22808 bootload. It is produced as soon as the syserr
22809 logging mechanism is made operative which insures
22810 that it is the first message logged for every
22811 bootload. It identifies the system ID and version
22812 of the running system.
22813
22814 Action: No operator action is required.
22815
22816
22817
22818 real_initializer.pl1.pmac
22819 initializer: Segment fault error by PPPP
22820 referencing PPPP: ERROR
22821
22822
22823 Stream: BOS Typewriter Crashes system
22824
22825 Time: System Intialization.
22826
22827 Meaning: During system bootload a segment fault error has
22828 occurred. This usually indicates running out of
22829 room on the RLV. A BOOT RPVS may recover some of
22830 this space. The procedure causing the error and
22831 the segment being referenced are identified along
22832 with the error message.
22833
22834 Action: Follow normal recovery procedures.
22835
22836
22837
22838
22839
22840
22841
22842
22843
22844
22845
22846
22847
22848
22849
22850
22851
22852
22853 initializer -394- MR12.5 10/27/92^L
22854
22855
22856 real_initializer.pl1.pmac
22857 initializer: STOP_NUM ENTRY_TO_CALL state ISTATE
22858 phase CPHASE.
22859
22860
22861 Stream: BOS Typewriter sounds beeper
22862
22863 Time: System Intialization.
22864
22865 Meaning: The "loud" config parm is currently enabled. This
22866 message gives the current stop number STOP_NUM
22867 that can be used to stop the initialization
22868 process and return to BCE before calling
22869 ENTRY_TO_CALL. The current values of
22870 sys_info$initialization_state ISTATE and
22871 sys_info$collection_1_phase CPHASE are also
22872 given.
22873
22874 Action: No operator action is required.
22875
22876
22877
22878 dn355_boot_interrupt.pl1
22879 Invalid bootload interrupt for FNP X status N
22880
22881
22882 Stream: BOS Typewriter.
22883
22884 Time: When bootloading an FNP
22885
22886 Meaning: The FNP responded to the bootload attempt with an
22887 interrupt but the high-order bit of the reported
22888 status was not on. N is the reported status in
22889 octal.
22890
22891 Action: Contact the system programming staff.
22892
22893
22894
22895 io_config_init.pl1
22896 io_config_init: Invalid iom or channel number on
22897 prph NAME card.
22898
22899
22900 Stream: BOS Typewriter Crashes system
22901
22902 Time: System Intialization.
22903
22904 Meaning: The iom number or the channel number is invalid on
22905 the prph card that defines NAME.
22906
22907 Action: Fix the config deck.
22908
22909
22910
22911 io_config_init -395- MR12.5 10/27/92^L
22912
22913
22914 io_error.pl1
22915 io_error: Illegal address value in call to
22916 io_manager.
22917
22918
22919 Stream: BOS Typewriter Crashes system
22920
22921 Time: While system is running.
22922
22923 Meaning: An address that was not in the required part of
22924 memory or was not aligned properly was passed in a
22925 call to io_manager. This indicates a logic error
22926 in the supervisor or CPU or memory hardware
22927 problems.
22928
22929 Action: Follow normal recovery procedures. Contact the
22930 system programming staff.
22931
22932
22933
22934 io_error.pl1
22935 io_error: Invalid channel index in call to
22936 io_manager.
22937
22938
22939 Stream: BOS Typewriter Crashes system
22940
22941 Time: While system is running.
22942
22943 Meaning: A channel index which did not correspond to an
22944 assigned logical channel was passed to io_manager.
22945 This indicates a logic error in the supervisor or
22946 CPU or memory hardware problems.
22947
22948 Action: Follow normal recovery procedures. Contact the
22949 system programming staff.
22950
22951
22952
22953
22954
22955
22956
22957
22958
22959
22960
22961
22962
22963
22964
22965
22966
22967
22968
22969 io_error -396- MR12.5 10/27/92^L
22970
22971
22972 ioam_.pl1
22973 ioam_: The IOAT is too small use TBLS config
22974 card to increase size.
22975
22976
22977 Stream: BOS Typewriter sounds beeper
22978
22979 Time: System Intialization.
22980
22981 Meaning: The system was unable to make an entry in the IO
22982 Assignment Table. One or more devices may be
22983 unattachable.
22984
22985 Action: Contact the system programming staff. Correct the
22986 configuration deck before the next bootload.
22987
22988
22989
22990 ioi_init.pl1
22991 ioi_init: Duplicate "prph NAME" card found.
22992
22993
22994 Stream: BOS Typewriter Crashes system
22995
22996 Time: System Intialization.
22997
22998 Meaning: $msg
22999
23000 Action: $config
23001
23002
23003
23004 ioi_init.pl1
23005 ioi_init: ERROR_CODE Unable to assign channel
23006 CHANID.
23007
23008
23009 Stream: BOS Typewriter Crashes system
23010
23011 Time: System Intialization.
23012
23013 Meaning: A logical channel could not be assigned to IOI.
23014 This indicates a logic error in the supervisor or
23015 CPU or memory hardware problems.
23016
23017 Action: Contact the system programming staff.
23018
23019
23020
23021
23022
23023
23024
23025
23026
23027 ioi_init -397- MR12.5 10/27/92^L
23028
23029
23030 ioi_init.pl1
23031 ioi_init: ERROR_CODE Unable to get the name of
23032 name of iom IOMNO channel CHANNO.
23033
23034
23035 Stream: BOS Typewriter Crashes system
23036
23037 Time: System Intialization.
23038
23039 Meaning: An attempt to generate the name of logical channel
23040 CHANNO of iom IOMNO failed.
23041
23042 Action: $config
23043
23044
23045
23046 ioi_init.pl1
23047 ioi_init: Multiple definitions of channel CHANID
23048 found for subsystem NAME.
23049
23050
23051 Stream: BOS Typewriter Crashes system
23052
23053 Time: System Intialization.
23054
23055 Meaning: $msg
23056
23057 Action: $config
23058
23059
23060
23061 ioi_init.pl1
23062 ioi_init: Multiple definitions of device NAME
23063 found.
23064
23065
23066 Stream: BOS Typewriter Crashes system
23067
23068 Time: System Intialization.
23069
23070 Meaning: $msg
23071
23072 Action: $config
23073
23074
23075
23076
23077
23078
23079
23080
23081
23082
23083
23084
23085 ioi_init -398- MR12.5 10/27/92^L
23086
23087
23088 ioi_init.pl1
23089 ioi_init: No cte found for channel CHANID.
23090
23091
23092 Stream: BOS Typewriter Crashes system
23093
23094 Time: System Intialization.
23095
23096 Meaning: This indicates a logic error in the supervisor or
23097 CPU or memory hardware problems.
23098
23099 Action: Contact the system programming staff.
23100
23101
23102
23103 ioi_init.pl1
23104 ioi_init: No entry for NAME found in disk_data.
23105
23106
23107 Stream: BOS Typewriter Crashes system
23108
23109 Time: System Intialization.
23110
23111 Meaning: This indicates a logic error in the supervisor or
23112 CPU or memory hardware problems.
23113
23114 Action: Contact the system programming staff.
23115
23116
23117
23118 ioi_init.pl1
23119 ioi_init: No matching "prph NAME" found for "chnl
23120 NAME".
23121
23122
23123 Stream: BOS Typewriter Crashes system
23124
23125 Time: System Intialization.
23126
23127 Meaning: $msg
23128
23129 Action: $config
23130
23131
23132
23133
23134
23135
23136
23137
23138
23139
23140
23141
23142
23143 ioi_init -399- MR12.5 10/27/92^L
23144
23145
23146 ioi_masked.pl1
23147 ioi_masked$interrupt: absadr failed.
23148
23149
23150 Stream: BOS Typewriter Crashes system
23151
23152 Time: While system is running.
23153
23154 Meaning: A call to the absadr function returned a non-zero
23155 error code indicating that the absolute address
23156 of the workspace could not be obtained. Since the
23157 workspace is wired this error should never have
23158 occurred.
23159
23160 Action: Contact the system programming staff. Follow
23161 normal recovery procedures.
23162
23163
23164
23165 ioi_masked.pl1
23166 ioi_masked$interrupt: I/O error.
23167
23168
23169 Stream: Logged in SYSERR log.
23170
23171 Time: While system is running.
23172
23173 Meaning: An error or accumulation of like errors has
23174 occured. All needed information is contained in
23175 the binary portion of the entry.
23176
23177 Action: No operator action is required.
23178
23179
23180
23181 ioi_masked.pl1
23182 ioi_masked$interrupt: Interrupt for inactive
23183 device device DEVID. Type go to continue.
23184
23185
23186 Stream: BOS Typewriter Crashes system
23187
23188 Time: While system is running.
23189
23190 Meaning: An interrupt has been received over a channel for
23191 which the device is not marked "active". This
23192 could indicate an error in the I/O hardware or in
23193 the setting/checking of the device active flag.
23194
23195 Action: Typing "go" at BCE will cause Multics to be
23196 reentered and ioi_masked to dismiss this error and
23197 properly cleanup.
23198
23199
23200
23201 ioi_masked$interrupt -400- MR12.5 10/27/92^L
23202
23203
23204 ioi_masked.pl1
23205 ioi_masked$interrupt: Special.
23206
23207
23208 Stream: Logged in SYSERR log.
23209
23210 Time: While system is running.
23211
23212 Meaning: A special interrupt or accumulation of special
23213 interrupts has occured. All needed information
23214 is contained in the binary portion of the entry.
23215
23216 Action: No operator action is required.
23217
23218
23219
23220 ioi_masked.pl1
23221 ioi_masked$timer: Attempt to unwire NULL
23222 workspace. device DEVID.
23223
23224
23225 Stream: BOS Typewriter.
23226
23227 Time: While system is running.
23228
23229 Meaning: Device entry flag and time stamp indicated that
23230 its workspace required unwiring. However the
23231 pointer to the ASTE for the workspace was null.
23232 This indicates a logic error in the supervisor or
23233 CPU or memory hardware problems.
23234
23235 Action: Contact the system programming staff. Follow
23236 normal recovery procedures.
23237
23238
23239
23240 ioi_masked.pl1
23241 ioi_masked$timer: Timeout on channel CHANID
23242 device DEVID.
23243
23244
23245 Stream: BOS Typewriter.
23246
23247 Time: While system is running.
23248
23249 Meaning: The time limit has expired waiting for status from
23250 CHANID for a previous connect. The channel will
23251 be masked "OFF" then unmasked if multiple devices
23252 exist i.e. tapes and disks so that special
23253 interrupts can be received.
23254
23255 Action: Contact your Customer Service Account
23256 Representative if the errors persist.
23257
23258
23259 ioi_masked$timer -401- MR12.5 10/27/92^L
23260
23261
23262 ioi_masked.pl1
23263 ioi_masked$timer: Timeout on channel CHANID no
23264 device.
23265
23266
23267 Stream: BOS Typewriter.
23268
23269 Time: While system is running.
23270
23271 Meaning: The time limit has expired waiting for status from
23272 CHANID for the connect to unmask the channel. The
23273 channel will be masked "OFF" then then unmask
23274 will be tried again.
23275
23276 Action: Contact your Customer Service Account
23277 Representative if the errors persist.
23278
23279
23280
23281 ioi_masked.pl1
23282 ioi_masked: Channel CHANID not responding will
23283 remain masked.
23284
23285
23286 Stream: BOS Typewriter.
23287
23288 Time: While system is running.
23289
23290 Meaning: The time limit has expired waiting for status from
23291 a previous unmask connect reset-status idcw. It
23292 is apparent that the channel is inoperative. No
23293 further attempt will be made to re-open the
23294 channel.
23295
23296 Action: Contact your Customer Service Account
23297 Representative if the errors persist.
23298
23299
23300
23301
23302
23303
23304
23305
23306
23307
23308
23309
23310
23311
23312
23313
23314
23315
23316
23317 ioi_masked -402- MR12.5 10/27/92^L
23318
23319
23320 ioi_masked.pl1
23321 ioi_masked: Lock for subsystem SUBSYSTEM not
23322 locked to process OOOOOO.
23323
23324
23325 Stream: BOS Typewriter Crashes system
23326
23327 Time: While system is running.
23328
23329 Meaning: An unlock of the subsystem lock was attempted but
23330 is was not locked by this process. This indicates
23331 a logic error in the supervisor or CPU or memory
23332 hardware problems.
23333
23334 Action: Contact the system programming staff. Follow
23335 normal recovery procedures.
23336
23337
23338
23339 ioi_masked.pl1
23340 ioi_masked: Mylock error on subsystem SUBSYSTEM.
23341
23342
23343 Stream: BOS Typewriter Crashes system
23344
23345 Time: While system is running.
23346
23347 Meaning: An lock of the subsystem lock was attempted but
23348 is was already locked by this process. This
23349 indicates a logic error in the supervisor or CPU
23350 or memory hardware problems.
23351
23352 Action: Contact the system programming staff. Follow
23353 normal recovery procedures.
23354
23355
23356
23357
23358
23359
23360
23361
23362
23363
23364
23365
23366
23367
23368
23369
23370
23371
23372
23373
23374
23375 ioi_masked -403- MR12.5 10/27/92^L
23376
23377
23378 ioi_masked.pl1
23379 ioi_masked: No Ext. Stat. with MAJOR/SUB status
23380 on chnl CHANID DEVID.
23381
23382
23383 Stream: Logged in SYSERR log.
23384
23385 Time: While system is running.
23386
23387 Meaning: An error status has occured that requires detailed
23388 status. This CHANID should have supplied this
23389 with the status but did not. This CHANID is also
23390 not capable of requesting the detailed status. An
23391 octal dump of the status_entry area will be
23392 displayed along with the error message.
23393
23394 Action: No operator action is required.
23395
23396
23397
23398 ioi_verify_lock.pl1
23399 ioi_verify_lock: Force unlocked device entry lock
23400 #N for USERID.
23401
23402
23403 Stream: BOS Typewriter.
23404
23405 Time: While system is running.
23406
23407 Meaning: This indicates a logic error in the supervisor or
23408 CPU or memory hardware problems. The process
23409 encountered a condition in ring-0 which forced a
23410 crawlout. IOI unlocks all locks for the process.
23411
23412 Action: Contact the system programming staff.
23413
23414
23415
23416 ioi_verify_lock.pl1
23417 ioi_verify_lock: Force unlocked group entry lock
23418 for USERID.
23419
23420
23421 Stream: BOS Typewriter.
23422
23423 Time: While system is running.
23424
23425 Meaning: This indicates a logic error in the supervisor or
23426 CPU or memory hardware problems. The process
23427 encountered a condition in ring-0 which forced a
23428 crawlout. IOI unlocks all locks for the process.
23429
23430 Action: Contact the system programming staff.
23431
23432
23433 ioi_verify_lock -404- MR12.5 10/27/92^L
23434
23435
23436 ioi_verify_lock.pl1
23437 ioi_verify_lock: Force unlocked reconfigure lock
23438 for USERID.
23439
23440
23441 Stream: BOS Typewriter.
23442
23443 Time: While system is running.
23444
23445 Meaning: This indicates a logic error in the supervisor or
23446 CPU or memory hardware problems. The process
23447 encountered a condition in ring-0 which forced a
23448 crawlout. IOI unlocks all locks for the process.
23449
23450 Action: Contact the system programming staff.
23451
23452
23453
23454 iom_data_init.pl1
23455 IOM model of "nsa" for IOM TAG will be changed to
23456 "iom".
23457
23458
23459 Stream: $announce
23460
23461 Time: System Intialization.
23462
23463 Meaning: The model field of this IOM card should be "iom".
23464 The system will
23465 correct it for this boot.
23466
23467 Action: Correct configuration deck before next boot.
23468
23469
23470
23471 iom_data_init.pl1
23472 iom_data_init: Bad IOM tag TAG. IOM card
23473 ignored.
23474
23475
23476 Stream: BOS Typewriter Crashes system
23477
23478 Time: System Intialization.
23479
23480 Meaning: An IOM card contained an IOM tag other than A B
23481 C or D.
23482
23483 Action: Correct configuration deck and reboot.
23484
23485
23486
23487
23488
23489
23490
23491 iom_data_init -405- MR12.5 10/27/92^L
23492
23493
23494 iom_data_init.pl1
23495 iom_data_init: Bad model MODEL for IOM TAG. IOM
23496 card ignored.
23497
23498
23499 Stream: BOS Typewriter Crashes system
23500
23501 Time: System Intialization.
23502
23503 Meaning: The model field for IOM TAG was not recognized.
23504
23505 Action: Correct configuration deck and reboot.
23506
23507
23508
23509 iom_data_init.pl1
23510 iom_data_init: Bad state STATE for IOM TAG. IOM
23511 card ignored.
23512
23513
23514 Stream: BOS Typewriter Crashes system
23515
23516 Time: System Intialization.
23517
23518 Meaning: The state for IOM TAG was neither "on" or "off".
23519
23520 Action: Correct configuration deck and reboot.
23521
23522
23523
23524 iom_data_init.pl1
23525 iom_data_init: Data not in low 256K.
23526
23527
23528 Stream: BOS Typewriter Crashes system
23529
23530 Time: System Intialization.
23531
23532 Meaning: The IOM data bases are not located in the low 256K
23533 of memory. This indicates a logic error in the
23534 supervisor or CPU or memory hardware problems.
23535
23536 Action: Correct configuration deck and reboot.
23537
23538
23539
23540
23541
23542
23543
23544
23545
23546
23547
23548
23549 iom_data_init -406- MR12.5 10/27/92^L
23550
23551
23552 iom_data_init.pl1
23553 iom_data_init: Duplicate IOM TAG in config deck.
23554
23555
23556 Stream: BOS Typewriter Crashes system
23557
23558 Time: System Intialization.
23559
23560 Meaning: Two IOM cards specifying IOM tag TAG were found in
23561 the configuration deck.
23562
23563 Action: Correct configuration deck and reboot.
23564
23565
23566
23567 iom_data_init.pl1
23568 iom_data_init: Error from absadr.
23569
23570
23571 Stream: BOS Typewriter Crashes system
23572
23573 Time: System Intialization.
23574
23575 Meaning: This indicates a logic error in the supervisor or
23576 CPU or memory hardware problems.
23577
23578 Action: Contact the system programming staff.
23579
23580
23581
23582 iom_data_init.pl1
23583 iom_data_init: Illegal port number PORT for IOM
23584 TAG.
23585
23586
23587 Stream: BOS Typewriter Crashes system
23588
23589 Time: System Intialization.
23590
23591 Meaning: The IOM card for IOM TAG contained an illegal port
23592 number. The port number must be between 0 and 7.
23593
23594 Action: Correct configuration deck and reboot.
23595
23596
23597
23598
23599
23600
23601
23602
23603
23604
23605
23606
23607 iom_data_init -407- MR12.5 10/27/92^L
23608
23609
23610 iom_data_init.pl1
23611 iom_data_init: IOM TAG reuses port PORT.
23612
23613
23614 Stream: BOS Typewriter Crashes system
23615
23616 Time: System Intialization.
23617
23618 Meaning: IOM TAG has been given the same port as some other
23619 active module CPU or IOM.
23620
23621 Action: Correct configuration deck and reboot.
23622
23623
23624
23625 iom_data_init.pl1
23626 iom_data_init: No valid IOM cards found.
23627
23628
23629 Stream: BOS Typewriter Crashes system
23630
23631 Time: System Intialization.
23632
23633 Meaning: There were no valid IOM cards in the configuration
23634 deck.
23635
23636 Action: Correct configuration deck and reboot.
23637
23638
23639
23640 iom_data_init.pl1
23641 iom_data_init: Unable to assign overhead channel
23642 for IOM TAG.
23643
23644
23645 Stream: BOS Typewriter Crashes system
23646
23647 Time: System Intialization.
23648
23649 Meaning: Could not set up overhead channel handlers for IOM
23650 TAG. This indicates a logic error in the
23651 supervisor or CPU or memory hardware problems.
23652
23653 Action: Contact the system programming staff.
23654
23655
23656
23657
23658
23659
23660
23661
23662
23663
23664
23665 iom_data_init -408- MR12.5 10/27/92^L
23666
23667
23668 iom_error.pl1
23669 iom_error: Unexpected level LEVEL_NUM interrupt
23670 from channel CHNL Status word - OOOOOOOOOOOO
23671
23672
23673
23674 Stream: BOS Typewriter.
23675
23676 Time: While system is running.
23677
23678 Meaning: The specified level interrupt has occured on
23679 channel CHNL either no channel assignment was
23680 found for the specified channel or there was no
23681 handler specified for the channel. If CHNL is a
23682 "?" this indicates an error occured converting
23683 the iom and channel numbers which are displayed
23684 in parenthesis "iom N chan_no N" after the
23685 question mark. The status word associated with
23686 the interrupt will be displayed when non-zero.
23687
23688 Action: Contact the system programming staff.
23689
23690
23691
23692 iom_overhead.pl1
23693 iom_overhead: IOM TAG System fault status STATUS.
23694
23695
23696 Stream: BOS Typewriter.
23697
23698 Time: While system is running.
23699
23700 Meaning: An IOM system fault has occurred. This indicates
23701 a problem in either hardware or system software.
23702
23703 Action: Contact the system programming staff.
23704
23705
23706
23707 iom_overhead.pl1
23708 iom_overhead: Status queue overrun for IOM TAG
23709 channel CHANNEL.
23710
23711
23712 Stream: BOS Typewriter.
23713
23714 Time: While system is running.
23715
23716 Meaning: The IOM has failed to refresh the DCW for an
23717 overhead channel. This indicates a hardware
23718 problem.
23719
23720 Action: Contact the system programming staff.
23721
23722
23723 iom_overhead -409- MR12.5 10/27/92^L
23724
23725
23726 lap_simplex.pl1
23727 lap_simplexCHN: Attempt to write overlength
23728 frame.
23729
23730
23731 Stream: Logged in SYSERR log.
23732
23733 Time: While system is running.
23734
23735 Meaning: An attempt was made to add a buffer to a frame
23736 which didn't have room for it. The connection
23737 will be crashed.
23738
23739 Action: Contact the system programming staff.
23740
23741
23742
23743 lap_simplex.pl1
23744 lap_simplexCHN: Failure Link state: STATE
23745 Current Action: FUNCTION in ESTATE Primary
23746 state: PSTATE Secondary state: SSTATE.
23747
23748
23749 Stream: Logged in SYSERR log.
23750
23751 Time: While system is running.
23752
23753 Meaning: Normal request to crash the line when the link has
23754 been disconnected by the FNP. STATE is the main
23755 state of the link. FUNCTION is the last function
23756 the link processed. The ESTATE is the execution
23757 state of the last function. PSTATE and SSTATE are
23758 the link up substate.
23759
23760 Action: Contact the system programming staff.
23761
23762
23763
23764 lap_simplex.pl1
23765 lap_simplexCHN: Invalid subchannel index XXX
23766
23767
23768 Stream: $alarm
23769
23770 Time: While system is running.
23771
23772 Meaning: Some call which attempted to write process a
23773 control order or process a modes operation
23774 specified a subchannel other than 1.
23775
23776 Action: Contact the system programming staff.
23777
23778
23779
23780
23781 lap_simplexCHN -410- MR12.5 10/27/92^L
23782
23783
23784 lap_simplex.pl1
23785 lap_simplexCHN: Link disconnected due to
23786 mis-matched frame sizes. CMDR/FRMR frame: FRAME.
23787
23788
23789 Stream: Logged in SYSERR log.
23790
23791 Time: While system is running.
23792
23793 Meaning: The FNP has received a command reject LAPB or
23794 frame reject LAP which specified a reason of
23795 "wide frame" on channel CHN. The actual level 2
23796 command is FRAME. This means the frame received
23797 by the other end was too long. Instead of looping
23798 continuously trying to send this frame the link
23799 will be disconnected. The maximum frame size in
23800 the Multics TTF for this link should be checked
23801 against the size expected by the other end of the
23802 link and corrected.
23803
23804 Action: Contact the system programming staff.
23805
23806
23807
23808 lap_simplex.pl1
23809 lap_simplexCHN: Unexpected interrupt TYPE DATA
23810 received.
23811
23812
23813 Stream: Logged in SYSERR log.
23814
23815 Time: While system is running.
23816
23817 Meaning: An unexpected MCM interrupt was processed.
23818
23819 Action: Contact the system programming staff.
23820
23821
23822
23823 lap_simplex.pl1
23824 lap_simplexCHN: Write failed to take whole
23825 frame discarding rest.
23826
23827
23828 Stream: Logged in SYSERR log.
23829
23830 Time: While system is running.
23831
23832 Meaning: A attempt to write a whole frame failed only a
23833 part of it was taken. An attempt will be made to
23834 continue.
23835
23836 Action: Contact the system programming staff.
23837
23838
23839 lap_simplexCHN -411- MR12.5 10/27/92^L
23840
23841
23842 lg_ctl_.pl1
23843 lg_ctl_$logout: called with
23844 active=N^proc_create_ok for NAME.PROJ TTY ute
23845 MM||NN
23846
23847
23848 Stream: as severity0
23849
23850 Time: While system is running.
23851
23852 Meaning: At attempt was made to logout a process which was
23853 not logged in. This is most likely the cause of a
23854 login error in the answering service.
23855
23856 Action: Contact the system administrator.
23857
23858
23859
23860 lg_ctl_.pl1
23861 lg_ctl_: lowered max ring for PERSON.PROJECT from
23862 N in PDTE to M in SATE
23863
23864
23865 Stream: as severity0
23866
23867 Time: While system is running.
23868
23869 Meaning: The value for the max ring specified in the PDT
23870 entry for PERSON on project PROJECT was lower than
23871 the maximum allowed ring in the SAT for the
23872 project. The SAT value was used for this login.
23873 The project administrator should change the PDT
23874 value to conform to the limits imposed by the
23875 system administrator.
23876
23877
23878
23879
23880
23881
23882
23883
23884
23885
23886
23887
23888
23889
23890
23891
23892
23893
23894
23895
23896
23897 lg_ctl_ -412- MR12.5 10/27/92^L
23898
23899
23900 lg_ctl_.pl1
23901 lg_ctl_: breach of physical security by NAME.PROJ
23902 from CHANNEL TYPE terminal "ID".
23903 lg_ctl_: person authorization is AUTH_NUM
23904 AUTH_STRING
23905 lg_ctl_: terminal access class is AUTH_NUM
23906 AUTH_STRING
23907
23908
23909 Stream: as severity2
23910
23911 Time: While system is running.
23912
23913 Meaning: The user identified in the first message by NAME
23914 on the project PROJ has somehow gotten access to a
23915 terminal with an access class higher than his own
23916 authorization. The next two messages give
23917 additional information where AUTH_NUM is an
23918 encoding of the authorization or access class in
23919 numeric form and AUTH_STRING is the mnemonic form.
23920 The login is refused and the terminal is hung up.
23921
23922 Action: Notify the system security administrator.
23923
23924
23925
23926 lg_ctl_.pl1
23927 lg_ctl_: disconnected count for USER is N1 in
23928 cdte N2 in pdte n_processes=N3.
23929
23930
23931 Stream: as severity1
23932
23933 Time: While system is running.
23934
23935 Meaning: The PDT entry for the user indicates that the user
23936 has a different number of disconnected processes
23937 than could actually be found in the answer_table.
23938 The PDT count is forced to the count of
23939 disconnected processes found in the answer_table.
23940 If this message occurs repeatedly for a given
23941 user notify the system administrator.
23942
23943 Action: No operator action is required.
23944
23945
23946
23947
23948
23949
23950
23951
23952
23953
23954
23955 lg_ctl_ -413- MR12.5 10/27/92^L
23956
23957
23958 lg_ctl_.pl1
23959 lg_ctl_: ERROR_MESSAGE. Error updating PNT entry
23960 of USER.
23961
23962
23963 Stream: as severity2
23964
23965 Time: While system is running.
23966
23967 Meaning: The system was unable to update the PNT for the
23968 user. Login for the user was refused.
23969
23970 Action: Contact the system administrator.
23971
23972
23973
23974 lg_ctl_.pl1
23975 lg_ctl_: ERROR_MESSAGE. >sc1>pdt>PROJ.pdt
23976
23977
23978 Stream: as severity2
23979
23980 Time: While system is running.
23981
23982 Meaning: All users on project PROJ are unable to log in
23983 because the project's pdt cannot be accessed for
23984 the reason ERROR_MESSAGE.
23985
23986 Action: Contact the system administrator. If the file was
23987 lost due to a crash it may be possible to
23988 retrieve it. If the file cannot be retrieved the
23989 person in charge of the project or the system
23990 administrator has to regenerate the file.
23991
23992
23993
23994 lg_ctl_.pl1
23995 lg_ctl_: ERROR_MESSAGE. Changing Mail Table
23996 default project for USER to PROJ
23997
23998
23999 Stream: as severity2
24000
24001 Time: While system is running.
24002
24003 Meaning: USER.PROJ logged in with the
24004 -change_default_project control argument but it
24005 was not possible to change his Mail Table entry
24006 for the reason noted in ERROR_MESSAGE. USER's
24007 default project was changed though but the Mail
24008 Table and the PNT are now inconsistent.
24009
24010 Action: Contact the system administrator.
24011
24012
24013 lg_ctl_ -414- MR12.5 10/27/92^L
24014
24015
24016 lg_ctl_.pl1
24017 lg_ctl_: ERROR_MESSAGE. Checksum failure reading
24018 PNT entry of USER.
24019
24020
24021 Stream: as severity2
24022
24023 Time: While system is running.
24024
24025 Meaning: The PNT entry for USER is damaged. It may have to
24026 be recreated or the entire PNT may have to be
24027 retrieved in special session. This can occur as a
24028 result of a damaged PNT or due to a logic error
24029 in the answering service.
24030
24031 Action: Contact the system administrator.
24032
24033
24034
24035 lg_ctl_.pl1
24036 lg_ctl_: ERROR_MESSAGE. Error reading PNT entry
24037 of USER.
24038
24039
24040 Stream: as severity2
24041
24042 Time: While system is running.
24043
24044 Meaning: This indicates that the system was unable to
24045 access the PNT. Login for the user was refused.
24046
24047 Action: Contact the system administrator. Some or all
24048 users will be unable to log in.
24049
24050
24051
24052 lg_ctl_.pl1
24053 lg_ctl_: ERROR_MESSAGE. Unable to check access
24054 for channel CHANNEL.
24055
24056
24057 Stream: as severity 1
24058
24059 Time: While system is running.
24060
24061 Meaning: The channel CHANNEL has the check_acs attribute
24062 set. However it was not possible to examine the
24063 Access Control Segment for the reason noted in
24064 ERROR_MESSAGE. Login for the user attempting to
24065 use this channel was refused.
24066
24067 Action: Contact the system administrator.
24068
24069
24070
24071 lg_ctl_ -415- MR12.5 10/27/92^L
24072
24073
24074 lg_ctl_.pl1
24075 lg_ctl_: ERROR_MESSAGE. unable to rehash sat.ht:
24076 REASON
24077
24078
24079 Stream: as severity2
24080
24081 Time: While system is running.
24082
24083 Meaning: An attempt to recreate the SAT hash table failed.
24084 The user attempting to log in was denied login.
24085 In all probably no users will be able to log in
24086 until the situation is repaired.
24087
24088 Action: Contact the system administrator.
24089
24090
24091
24092 lg_ctl_.pl1
24093 lg_ctl_: hash table of PROJ.pdt has PERS pdt has
24094 PERS2 at MM|NN
24095
24096
24097 Stream: as severity2
24098
24099 Time: While system is running.
24100
24101 Meaning: The PDT for PROJ is out of step with its hash
24102 table. The system attempts to log the user in.
24103 The PDT must be re-installed in order to correct
24104 the problem.
24105
24106 Action: Contact the system administrator.
24107
24108
24109
24110 lg_ctl_.pl1
24111 lg_ctl_: login word is "QQQQ"
24112
24113
24114 Stream: as severity1
24115
24116 Time: System Intialization.
24117
24118 Meaning: If multics is typed a random 4-digit login word
24119 is made up.
24120
24121 Action: If any system programmers are to be allowed access
24122 to the system during this special session inform
24123 them of the login word. To allow normal use of
24124 Multics type "word login". In order to start the
24125 absentee facility which special sessions disable
24126 type "abs start".
24127
24128
24129 lg_ctl_ -416- MR12.5 10/27/92^L
24130
24131
24132 lg_ctl_.pl1
24133 lg_ctl_: no hash table at WWWWWW of PROJ.pdt
24134
24135
24136 Stream: as severity2
24137
24138 Time: While system is running.
24139
24140 Meaning: A user is logging in to project PROJ. The
24141 project's pdt does not have a hash table even
24142 though the pdt header says it does. The system
24143 attempts to log the user in anyway. Possibly the
24144 PDT has been damaged.
24145
24146 Action: Contact the system programming staff.
24147
24148
24149
24150 lg_ctl_.pl1
24151 lg_ctl_: password used PERS.PROJ CHANNEL
24152 TERM_TYPE ID
24153
24154
24155 Stream: as severity2
24156
24157 Time: While system is running.
24158
24159 Meaning: The system administrator has set a password trap
24160 on the password for the person PERS. This message
24161 is typed when the person tries to log in. The
24162 login was attempted from a TERM_TYPE terminal with
24163 identification code ID using channel CHANNEL.
24164
24165 Action: Unless the system administrator has asked you to
24166 watch for this message ignore it. The system
24167 administrator can locate this message in the log
24168 and is presumably watching for it.
24169
24170
24171
24172
24173
24174
24175
24176
24177
24178
24179
24180
24181
24182
24183
24184
24185
24186
24187 lg_ctl_ -417- MR12.5 10/27/92^L
24188
24189
24190 lg_ctl_.pl1
24191 lg_ctl_: PDT for project PROJECTID has its damage
24192 switch set. Login for user PERSONID refused.
24193
24194
24195 Stream: $as2
24196
24197 Time: Contact the system programming staff.
24198
24199 Meaning: During a login attempt of user PERSONID on project
24200 PROJECTID the system noticed the damage switch
24201 set on the PDT for this project. The login was
24202 denied. A system administrator should determine
24203 whether the PDT is in fact damaged. If not
24204 he/she should turn off the damage switch for the
24205 PDT i.e. switch_off damage
24206 >sc1>pdt>PROJECTID.pdt If the PDT appears
24207 damaged then it should be retrieved from backup
24208 tape or re-installed when the system is in special
24209 session.
24210
24211
24212
24213 lg_ctl_.pl1
24214 lg_ctl_: PDT for project PROJECTID has its damage
24215 switch set. Login for user PERSONID refused.
24216
24217
24218 Stream: as severity2
24219
24220 Time: Contact the system programming staff.
24221
24222 Meaning: During a login attempt of user PERSONID on project
24223 PROJECTID the system noticed the damage switch
24224 set on the PDT for this project. The login was
24225 denied. A system administrator should determine
24226 whether the PDT is in fact damaged. If not
24227 he/she should turn off the damage switch for the
24228 PDT i.e. switch_off damage
24229 >sc1>pdt>PROJECTID.pdt If the PDT appears
24230 damaged then it should be retrieved from backup
24231 tape or re-installed when the system is in special
24232 session.
24233
24234
24235
24236
24237
24238
24239
24240
24241
24242
24243
24244
24245 lg_ctl_ -418- MR12.5 10/27/92^L
24246
24247
24248 lg_ctl_.pl1
24249 lg_ctl_: project PROJ state N still in sat.ht
24250
24251
24252 Stream: as severity2
24253
24254 Time: While system is running.
24255
24256 Meaning: A user on a deleted project attempted to log in
24257 and the supposedly deleted project was still in
24258 the SAT hash table. The user is refused login.
24259 The SAT and its hash table are out of step. The
24260 system continues operating.
24261
24262 Action: Contact the system programming staff.
24263
24264
24265
24266 lg_ctl_.pl1
24267 lg_ctl_: project PROJECT has invalid
24268 rate_structure number N. Using rate_structure 0.
24269
24270
24271 Stream: as severity2
24272
24273 Time: While system is running.
24274
24275 Meaning: The SAT entry for the project has an invalid
24276 rate_structure number. The user is allowed to log
24277 in but is charged at the default rate i.e.
24278 according to rate_structure 0 Notify the system
24279 administrator so that the SAT entry may be
24280 corrected. This message will occur for each login
24281 using project PROJECT.
24282
24283 Action: Contact the system administrator.
24284
24285
24286
24287
24288
24289
24290
24291
24292
24293
24294
24295
24296
24297
24298
24299
24300
24301
24302
24303 lg_ctl_ -419- MR12.5 10/27/92^L
24304
24305
24306 lg_ctl_.pl1
24307 lg_ctl_: project.n_users = N for PROJ logout
24308 PERSON
24309
24310
24311 Stream: as severity0
24312
24313 Time: While system is running.
24314
24315 Meaning: The count of the active users on a project went
24316 negative when attempting to logout PERSON. This
24317 is most likely the result of a logic error in the
24318 answering service or a damaged PDT.
24319
24320 Action: Contact the system administrator.
24321
24322
24323
24324 lg_ctl_.pl1
24325 lg_ctl_: project.n_users = N for PROJECT login
24326 PERSON
24327
24328
24329 Stream: as severity0
24330
24331 Time: While system is running.
24332
24333 Meaning: The value of project.n_users for project PROJECT
24334 went negative while attempting to login PERSON.
24335 The user was permitted login but there may be
24336 discrepancies which may affect future operations.
24337
24338 Action: Contact the system administrator.
24339
24340
24341
24342
24343
24344
24345
24346
24347
24348
24349
24350
24351
24352
24353
24354
24355
24356
24357
24358
24359
24360
24361 lg_ctl_ -420- MR12.5 10/27/92^L
24362
24363
24364 lg_ctl_.pl1
24365 lg_ctl_: raised initial ring for PERSON.PROJECT
24366 from N in PDTE to M in SATE
24367
24368
24369 Stream: as severity0
24370
24371 Time: While system is running.
24372
24373 Meaning: The value for the initial ring specified in the
24374 PDT entry for PERSON on project PROJECT was lower
24375 than than allowed for the project in the SAT. The
24376 value in the SAT was used in logging in this user.
24377 The project adminstrator should change the value
24378 in the PDT to conform to the limits imposed by the
24379 system adminstrator.
24380
24381 Action: No operator action is required.
24382
24383
24384
24385 lg_ctl_.pl1
24386 lg_ctl_: reduced pdir quota for PERSON.PROJECT
24387 from N in PDTE to M in SATE
24388
24389
24390 Stream: as severity0
24391
24392 Time: While system is running.
24393
24394 Meaning: The value for process directory quota specified in
24395 the PDT entry for PERSON on project PROJECT was
24396 greater than the maximum allowed process directory
24397 quota specified in the SAT entry for PROJECT. The
24398 SAT value was used for this login. The project
24399 administrator for the project should set the value
24400 within the limits imposed by the system
24401 administrator.
24402
24403 Action: No operator action is required.
24404
24405
24406
24407
24408
24409
24410
24411
24412
24413
24414
24415
24416
24417
24418
24419 lg_ctl_ -421- MR12.5 10/27/92^L
24420
24421
24422 lg_ctl_.pl1
24423 lg_ctl_: sat.ht has "WWWW" SAT has "xxxx" at
24424 MM|NN.
24425
24426
24427 Stream: as severity2
24428
24429 Time: While system is running.
24430
24431 Meaning: The SAT and its hash table are out of step or a
24432 storage system error has occurred. This could be
24433 the result of an incomplete reload. The system
24434 attempts to rehash the table and continue.
24435
24436 Action: Contact the system administrator.
24437
24438
24439
24440 lg_ctl_.pl1
24441 lg_ctl_: too many bad passwords for NAME.PROJ
24442 from CHANNEL TYPE terminal "ID".
24443
24444
24445 Stream: as severity2
24446
24447 Time: While system is running.
24448
24449 Meaning: The user identified by NAME on the project PROJ
24450 has either forgotten his password or someone else
24451 is trying to guess it. The system has refused the
24452 login for an installation-specified number of
24453 times before this message is printed. The maximum
24454 number of times the password can be used
24455 incorrectly before this message is printed is
24456 stored in the segment installation_parms.
24457
24458 Action: Contact the system administrator.
24459
24460
24461
24462 lg_ctl_.pl1
24463 lg_ctl_: tracing turned off.
24464
24465
24466 Stream: as severity1
24467
24468 Time: While system is running.
24469
24470 Meaning: A system adminstrator has disabled tracing of the
24471 module lg_ctl_.
24472
24473 Action: No operator action is required.
24474
24475
24476
24477 lg_ctl_ -422- MR12.5 10/27/92^L
24478
24479
24480 lg_ctl_.pl1
24481 lg_ctl_: tracing turned on.
24482
24483
24484 Stream: as severity1
24485
24486 Time: While system is running.
24487
24488 Meaning: A system administrator has enabled tracing of the
24489 module lg_ctl_. Debugging information will appear
24490 on the console.
24491
24492 Action: No operator action is required.
24493
24494
24495
24496 lg_ctl_.pl1
24497 lg_ctl_: TYPE access to channel CHANNEL by
24498 NAME.PROJ denied by ACS.
24499
24500
24501 Stream: as severity 0
24502
24503 Time: While system is running.
24504
24505 Meaning: The user NAME.PROJ attempted to use the TYPE
24506 command while dialed-up on channel CHANNEL.
24507 However the access to the channel is restricted
24508 by Access Control Segment and the user is not
24509 permitted to use the channel.
24510
24511 Action: No operator action is required.
24512
24513
24514
24515 lg_ctl_.pl1
24516 lg_ctl_: user PERSON state N still in hash
24517 table of PROJ.pdt
24518
24519
24520 Stream: as severity2
24521
24522 Time: While system is running.
24523
24524 Meaning: A deleted user attempted to log in to project
24525 PROJ and his name was still in the hash table of
24526 the project's PDT. The user is refused login.
24527 The PDT has probably been damaged by a software
24528 malfunction.
24529
24530 Action: Contact the system programming staff.
24531
24532
24533
24534
24535 lg_ctl_ -423- MR12.5 10/27/92^L
24536
24537
24538 load_ctl_.pl1
24539 load_ctl_: bumping NAME1.PROJ for NAME2.PROJ:
24540 REASON
24541
24542
24543 Stream: as severity1
24544
24545 Time: While system is running.
24546
24547 Meaning: This message is typed out when a user is bumped.
24548 A user may be bumped by another member of his load
24549 control group in which case REASON is pr_grp
24550 which means group preemption. If a secondary user
24551 is bumped by a primary user either from the same
24552 group or from another group REASON is pr_sec
24553 meaning secondary user preemption. If REASON is
24554 pr_emrg meaning emergency preemption a system
24555 programmer was logging in and had to bump some
24556 user. A user is usually given three minutes after
24557 this message to clean up and log out before being
24558 automatically logged out.
24559
24560 Action: No operator action is required.
24561
24562
24563
24564 load_ctl_.pl1
24565 load_ctl_: configuration not in tables. X cpu Y
24566 mem W bulk shift Z
24567 using configuartion XX cpu YY mem WW
24568 bulk shift ZZ
24569
24570
24571 Stream: as severity2
24572
24573 Time: May occur at any time.
24574
24575 Meaning: The automatic setting of maxunits by the load
24576 control facility was attempted but the
24577 configuration tables did not have a configuration
24578 defined that matched the current configuration.
24579 No change was made to the system parameters. The
24580 system continues operation selecting the last
24581 entry in the config tables which should
24582 correspond to the largest system described by the
24583 system administrator. The values assumed by
24584 automatic load control are given in the second
24585 line of the message.
24586
24587 Action: Set maxunits and the absentee max manually.
24588 Inform the system administrator so that he can
24589 update the load control tables.
24590
24591
24592
24593 load_ctl_ -424- MR12.5 10/27/92^L
24594
24595
24596 load_ctl_.pl1
24597 load_ctl_: demote NAME.PROJ GROUP NNN
24598
24599
24600 Stream: as severity1
24601
24602 Time: While system is running.
24603
24604 Meaning: This is trace output. This user has been demoted
24605 to secondary status.
24606
24607 Action: No operator action is required. To turn off this
24608 output type load_ctl_$lctraceoff from admin mode.
24609
24610
24611
24612 load_ctl_.pl1
24613 load_ctl_: Entry not found. master_group_table
24614
24615
24616 Stream: as severity2
24617
24618 Time: System Intialization.
24619
24620 Meaning: load_ctl_ cannot find the master_group_table. The
24621 system will probably not be able to perform the
24622 bootload operation.
24623
24624 Action: Contact the system programming staff.
24625
24626
24627
24628
24629
24630
24631
24632
24633
24634
24635
24636
24637
24638
24639
24640
24641
24642
24643
24644
24645
24646
24647
24648
24649
24650
24651 load_ctl_ -425- MR12.5 10/27/92^L
24652
24653
24654 load_ctl_.pl1
24655 load_ctl_: ERROR_MESSAGE During work class
24656 redefinition
24657
24658
24659 Stream: as severity2
24660
24661 Time: While the system is running or during system
24662 startup.
24663
24664 Meaning: Either some system table has been damaged or a
24665 system administrator was changing work class
24666 definitions at the time of a shift change or when
24667 a "maxu auto" command was issued. Error messages
24668 immediately preceding this one contain more
24669 information about the exact nature of the problem.
24670
24671 Action: Contact the system administrator. He may want you
24672 to type the "maxu auto" command to retry the
24673 operation that failed. If that command produces
24674 no error messages the problem has been
24675 eliminated.
24676
24677
24678
24679 load_ctl_.pl1
24680 load_ctl_: group GRPID missing at logout
24681
24682
24683 Stream: as severity2
24684
24685 Time: While system is running.
24686
24687 Meaning: The master_group_table entry for GRPID has
24688 vanished. The system is attempting to logout a
24689 user from that group but cannot find the table
24690 entry for the group. The system will attempt to
24691 continue.
24692
24693 Action: Contact the system administrator.
24694
24695
24696
24697
24698
24699
24700
24701
24702
24703
24704
24705
24706
24707
24708
24709 load_ctl_ -426- MR12.5 10/27/92^L
24710
24711
24712 load_ctl_.pl1
24713 load_ctl_: group GRPID missing at preempt
24714
24715
24716 Stream: as severity2
24717
24718 Time: While system is running.
24719
24720 Meaning: The master_group_table entry for GRPID has
24721 vanished. The system is attempting to preempt a
24722 user from that group but cannot find the table
24723 entry for the group. The system will attempt to
24724 continue.
24725
24726 Action: Contact the system administrator.
24727
24728
24729
24730 load_ctl_.pl1
24731 load_ctl_: Group GRPID missing for NAME.PROJ
24732
24733
24734 Stream: as severity2
24735
24736 Time: While system is running.
24737
24738 Meaning: The system administrator has designated that the
24739 project PROJ should be in the load control group
24740 GRPID but the entry in the master_group_table for
24741 that load control group is missing. The user
24742 cannot log in. This may be an indication that the
24743 segment master_group_table has been damaged.
24744
24745 Action: Contact the system administrator.
24746
24747
24748
24749
24750
24751
24752
24753
24754
24755
24756
24757
24758
24759
24760
24761
24762
24763
24764
24765
24766
24767 load_ctl_ -427- MR12.5 10/27/92^L
24768
24769
24770 load_ctl_.pl1
24771 load_ctl_: group GRPID not authorized for project
24772 PROJ
24773
24774
24775 Stream: as severity2
24776
24777 Time: While system is running.
24778
24779 Meaning: A project administrator has designated that one of
24780 the users in project PROJ should be in the load
24781 control group GRPID but the system administrator
24782 has not authorized that project to be in that
24783 group. An attempt will be made to log the user
24784 in using the default group for his project.
24785 Subsequent messages will indicate the success or
24786 failure of this attempt.
24787
24788 Action: Contact the system administrator.
24789
24790
24791
24792 load_ctl_.pl1
24793 load_ctl_: group GRPID not found in mgt for
24794 NAME.PROJ
24795
24796
24797 Stream: as severity2
24798
24799 Time: While system is running.
24800
24801 Meaning: A system or project administrator has designated
24802 that the user NAME.PROJ should be in the load
24803 control group GRPID but the master_group_table
24804 mgt has no entry for that group. An attempt
24805 will be made to log the user in using the default
24806 group for his project. Subsequent messages will
24807 indicate the success or failure of this attempt.
24808
24809 Action: Contact the system administrator.
24810
24811
24812
24813
24814
24815
24816
24817
24818
24819
24820
24821
24822
24823
24824
24825 load_ctl_ -428- MR12.5 10/27/92^L
24826
24827
24828 load_ctl_.pl1
24829 load_ctl_: maxu too small XX YY units for
24830 group GRPID
24831
24832
24833 Stream: as severity2
24834
24835 Time: While system is running.
24836
24837 Meaning: The system administrator has specified that the
24838 load control group GRPID is to have "all the rest"
24839 of the primary load units after all other groups
24840 have taken their allocations from maxunits.
24841 However maxunits is less than the sum of the
24842 primary allocations giving the group GRPID the
24843 negative allocation of YY units. The system
24844 proceeds attempting to log the user in anyway.
24845 Of course the user is allowed secondary status
24846 only if he is allowed to log in at all. This is
24847 often the result of the operator typing maxu 30
24848 instead of maxu 300 or some similar error.
24849
24850 Action: Check the value of maxunits and if a mistake was
24851 made correct it. If the maxunits value is
24852 correct note this situation for the system
24853 administrator.
24854
24855
24856
24857 load_ctl_.pl1
24858 load_ctl_: more than one group has -1 max: GRPID
24859
24860
24861 Stream: as severity2
24862
24863 Time: System Intialization.
24864
24865 Meaning: The system administrator has accidentally given
24866 more than one group a "take all the rest" maximum
24867 primary unit allocation. The user control package
24868 cannot handle this situation. The second group
24869 with a -1 maxprim is listed. The system completes
24870 startup and users can log in but maxunits may not
24871 be obeyed.
24872
24873 Action: Contact the system administrator.
24874
24875
24876
24877
24878
24879
24880
24881
24882
24883 load_ctl_ -429- MR12.5 10/27/92^L
24884
24885
24886 load_ctl_.pl1
24887 load_ctl_: promote NAME.PROJ GROUP NNN
24888
24889
24890 Stream: as severity1
24891
24892 Time: While system is running.
24893
24894 Meaning: This is trace output. This user has been promoted
24895 to primary status.
24896
24897 Action: No operator action is required. To turn off this
24898 output type load_ctl_$lctraceoff from admin mode.
24899
24900
24901
24902 load_ctl_.pl1
24903 load_ctl_: reduced grace for PERSON.PROJECT from
24904 MINUTES1 in PDTE to MINUTES2 in SATE
24905
24906
24907 Stream: $as0
24908
24909 Time: While system is running.
24910
24911 Meaning: The Project Definition Table PDT entry for
24912 PERSON.PROJECT specifies a larger grace time time
24913 during which a process is protected from
24914 preemption than does the System Administrator's
24915 Table SAT entry for the project. The time given
24916 in the SAT entry is used.
24917
24918 Action: No operator action is required.
24919
24920
24921
24922
24923
24924
24925
24926
24927
24928
24929
24930
24931
24932
24933
24934
24935
24936
24937
24938
24939
24940
24941 load_ctl_ -430- MR12.5 10/27/92^L
24942
24943
24944 load_ctl_.pl1
24945 load_ctl_: Too many primes. NAME.PROJ GROUP
24946 MM/NN
24947
24948
24949 Stream: as severity0
24950
24951 Time: While system is running.
24952
24953 Meaning: This is trace output. The system has been
24954 committed to allow a certain number of users from
24955 group GROUP to be logged in at one time. In order
24956 to log this user in some other user must be
24957 bumped but all users have primary status and
24958 cannot be bumped. This situation may be a
24959 consequence of system programmers with the
24960 overloading privilege logging in when the system
24961 is full. The user is allowed to log in anyway.
24962
24963 Action: No operator action is required.
24964
24965
24966
24967 load_ctl_.pl1
24968 load_ctl_: Unknown mgt version number: NUMBER
24969
24970
24971 Stream: as severity2
24972
24973 Time: System Intialization.
24974
24975 Meaning: Either the master_group_table mgt has been
24976 damaged or its format is incompatible with the
24977 current Answering Service. The system cannot be
24978 brought up until a correct mgt is provided.
24979
24980 Action: Contact the system administrator.
24981
24982
24983
24984
24985
24986
24987
24988
24989
24990
24991
24992
24993
24994
24995
24996
24997
24998
24999 load_ctl_ -431- MR12.5 10/27/92^L
25000
25001
25002 load_disk_mpcs.pl1
25003 load_disk_mpcs: Disk mpcs: NAMES appear not to
25004 be operating.
25005
25006
25007 Stream: $announce
25008
25009 Time: System Intialization.
25010
25011 Meaning: The named disk mpcs listed in the config deck
25012 did not respond to a "request status" control
25013 order. They are believed not to be operating; in
25014 particular firmware should probably be loaded
25015 into them.
25016
25017
25018
25019 load_disk_mpcs.pl1
25020 load_disk_mpcs: Operator aborted disk MPC
25021 loading.
25022
25023
25024 Stream: BOS Typewriter Crashes system
25025
25026 Time: System Intialization.
25027
25028 Meaning: The operator answered "abort" when requested to
25029 supply disk mpcs to be loaded. This will cause a
25030 return to the previous bce command level.
25031
25032
25033
25034 load_mst.pl1
25035 load_mst: bad header size SSS
25036
25037
25038 Stream: BOS Typewriter Crashes system
25039
25040 Time: System Intialization.
25041
25042 Meaning: A bad segment header was found on the bootload
25043 tape.
25044
25045 Action: Follow normal recovery procedures. The Multics
25046 System Tape may be incorrect. If the problem
25047 persists try another MST.
25048
25049
25050
25051
25052
25053
25054
25055
25056
25057 load_mst -432- MR12.5 10/27/92^L
25058
25059
25060 load_mst.pl1
25061 load_mst: error from slt_manager$build_entry
25062
25063
25064 Stream: BOS Typewriter Crashes system
25065
25066 Time: System Intialization.
25067
25068 Meaning: This indicates a logic error in the supervisor or
25069 CPU or memory hardware problems.
25070
25071 Action: Follow normal recovery procedures. The Multics
25072 System Tape may be incorrect. If the problem
25073 persists try another MST.
25074
25075
25076
25077 load_mst.pl1
25078 load_mst: Missing linkage or defs.
25079
25080
25081 Stream: BOS Typewriter Crashes system
25082
25083 Time: System Intialization.
25084
25085 Meaning: A linkage or definitions section which should be
25086 in the mst source appears to be missing.
25087
25088 Action: Follow normal recovery procedures. The Multics
25089 System Tape may be incorrect. If the problem
25090 persists try another MST.
25091
25092
25093
25094 load_mst.pl1
25095 load_mst: NAME can't be placed into file
25096 partition.
25097
25098
25099 Stream: BOS Typewriter Crashes system
25100
25101 Time: System Intialization.
25102
25103 Meaning: An error occurred while adding the named file from
25104 the mst into the bootload Multics file system.
25105
25106 Action: Follow normal recovery procedures. The Multics
25107 System Tape may be incorrect. If the problem
25108 persists try another MST.
25109
25110
25111
25112
25113
25114
25115 load_mst -433- MR12.5 10/27/92^L
25116
25117
25118 load_mst.pl1
25119 load_mst: Out of space in mst area of bce
25120 partition.
25121
25122
25123 Stream: BOS Typewriter Crashes system
25124
25125 Time: System Intialization.
25126
25127 Meaning: There is not enough room in the mst area of the
25128 bce partition to hold collections 2.0 and 3.0.
25129
25130 Action: The size of this area will need to be increased.
25131 The Multics System Tape may be incorrect. If the
25132 problem persists try another MST.
25133
25134
25135
25136 load_mst.pl1
25137 load_mst: too many bce command segments.
25138
25139
25140 Stream: BOS Typewriter Crashes system
25141
25142 Time: System Intialization.
25143
25144 Meaning: An exceptionally large number of segments appeared
25145 in collection 1.5. This probably indicates an
25146 error in the mst.
25147
25148 Action: Follow normal recovery procedures. The Multics
25149 System Tape may be incorrect. If the problem
25150 persists try another MST.
25151
25152
25153
25154 load_mst.pl1
25155 load_mst: unexpected control type TTT
25156
25157
25158 Stream: BOS Typewriter Crashes system
25159
25160 Time: System Intialization.
25161
25162 Meaning: A segment control word was found out of sequence
25163 on the bootload tape.
25164
25165 Action: Follow normal recovery procedures. The Multics
25166 System Tape may be incorrect. If the problem
25167 persists try another MST.
25168
25169
25170
25171
25172
25173 load_mst -434- MR12.5 10/27/92^L
25174
25175
25176 load_mst.pl1
25177 load_mst: Unexpected DEFS/LINKAGE
25178
25179
25180 Stream: BOS Typewriter Crashes system
25181
25182 Time: System Intialization.
25183
25184 Meaning: A linkage or definitions section was found out of
25185 sequence in the mst source.
25186
25187 Action: Follow normal recovery procedures. The Multics
25188 System Tape may be incorrect. If the problem
25189 persists try another MST.
25190
25191
25192
25193 load_mst.pl1
25194 load_mst: unknown control type TTT
25195
25196
25197 Stream: BOS Typewriter Crashes system
25198
25199 Time: System Intialization.
25200
25201 Meaning: A bad segment control word was found on the
25202 bootload tape.
25203
25204 Action: Follow normal recovery procedures. The Multics
25205 System Tape may be incorrect. If the problem
25206 persists try another MST.
25207
25208
25209
25210 load_mst.pl1
25211 load_mst: XXX. out of WWW. pages used in disk
25212 mst area.
25213
25214
25215 Stream: BOS Typewriter.
25216
25217 Meaning: This message shows the amount of the mst area of
25218 the bce partition that is used to hold the mst.
25219
25220 Action: No operator action is required. The Multics
25221 System Tape may be incorrect. If the problem
25222 persists try another MST.
25223
25224
25225
25226
25227
25228
25229
25230
25231 load_mst -435- MR12.5 10/27/92^L
25232
25233
25234 load_system.pl1
25235 load_system: error from asd_$add_sentries The
25236 system could not remove the write access it had
25237 set to load the contents of a segment from the mst
25238 source.
25239
25240
25241 Stream: BOS Typewriter Crashes system
25242
25243 Time: System Intialization.
25244
25245 Meaning: This indicates a logic error in the supervisor or
25246 CPU or memory hardware problems.
25247
25248 Action: Follow normal recovery procedures. The Multics
25249 System Tape may be incorrect. If the problem
25250 persists try another MST.
25251
25252
25253
25254 load_system.pl1
25255 load_system: error from set$entry_bound_ptr
25256
25257
25258 Stream: BOS Typewriter Crashes system
25259
25260 Time: System Intialization.
25261
25262 Meaning: This indicates a logic error in the supervisor or
25263 CPU or memory hardware problems.
25264
25265 Action: Follow normal recovery procedures. The Multics
25266 System Tape may be incorrect. If the problem
25267 persists try another MST.
25268
25269
25270
25271 load_system.pl1
25272 load_system: illegal header length in mst source
25273
25274
25275 Stream: BOS Typewriter Crashes system
25276
25277 Time: System Intialization.
25278
25279 Meaning: This indicates a logic error in the supervisor or
25280 CPU or memory hardware problems.
25281
25282 Action: Follow normal recovery procedures. The Multics
25283 System Tape may be incorrect. If the problem
25284 persists try another MST.
25285
25286
25287
25288
25289 load_system -436- MR12.5 10/27/92^L
25290
25291
25292 load_system.pl1
25293 load_system: illegal type in mst source
25294
25295
25296 Stream: BOS Typewriter Crashes system
25297
25298 Time: System Intialization.
25299
25300 Meaning: This indicates a logic error in the supervisor or
25301 CPU or memory hardware problems.
25302
25303 Action: Follow normal recovery procedures. The Multics
25304 System Tape may be incorrect. If the problem
25305 persists try another MST.
25306
25307
25308
25309 load_system.pl1
25310 load_system: illegal type in mst source
25311
25312
25313 Stream: BOS Typewriter Crashes system
25314
25315 Time: System Intialization.
25316
25317 Meaning: This indicates a logic error in the supervisor or
25318 CPU or memory hardware problems.
25319
25320 Action: Follow normal recovery procedures. The Multics
25321 System Tape may be incorrect. If the problem
25322 persists try another MST.
25323
25324
25325
25326 fnp_util.pl1
25327 Loading FNP X CORE_IMAGE VERSION
25328
25329
25330 Stream: BOS Typewriter.
25331
25332 Time: Answering service initialization and each
25333 subsequent FNP bootload.
25334
25335 Meaning: Loading of FNP X has begun with a core image named
25336 CORE_IMAGE normally "mcs" of version number
25337 VERSION.
25338
25339 Action: No operator action is required.
25340
25341
25342
25343
25344
25345
25346
25347 Loading FNP X CORE_IMAGE -437- MR12.5 10/27/92^L
25348
25349
25350 lock.pl1
25351 lock: AST lock set at dir unlock time.
25352
25353
25354 Stream: BOS Typewriter Crashes system
25355
25356 Time: While system is running.
25357
25358 Meaning: The AST was found locked to this process at
25359 directory unlock time. This indicates a
25360 supervisor programming error.
25361
25362 Action: $reboot
25363
25364
25365
25366 lock.pl1
25367 lock: dir_lock_read mylock err. dp =PTR
25368
25369
25370 Stream: BOS Typewriter Crashes system
25371
25372 Time: While system is running.
25373
25374 Meaning: An attempt to lock a directory for reading found
25375 the directory already locked to this process.
25376 This indicates a supervisor programming error.
25377
25378 Action: $reboot
25379
25380
25381
25382 lock.pl1
25383 lock: dir_lock_write mylock err. dp =PTR
25384
25385
25386 Stream: BOS Typewriter Crashes system
25387
25388 Time: While system is running.
25389
25390 Meaning: An attempt to lock a directory for writing found
25391 the directory already locked to this process.
25392 This indicates a supervisor programming error.
25393
25394 Action: $reboot
25395
25396
25397
25398
25399
25400
25401
25402
25403
25404
25405 lock -438- MR12.5 10/27/92^L
25406
25407
25408 lock.pl1
25409 lock: lock PTR not equal to processid. caller =
25410 PTR
25411
25412
25413 Stream: $lock_severity
25414
25415 Time: While system is running.
25416
25417 Meaning: An attempt was made to unlock a lock found not to
25418 be held by this process. This indicates a
25419 supervisor programming error.
25420
25421 Action: $reboot
25422
25423
25424
25425 lock.pl1
25426 lock: LOCK_DIR: dir_lock_seg full.
25427
25428
25429 Stream: BOS Typewriter Crashes system
25430
25431 Time: While system is running.
25432
25433 Meaning: The segment used to record all locked directories
25434 overflowed. This may be a hardware problem.
25435
25436 Action: $reboot
25437
25438
25439
25440 lock.pl1
25441 lock: LOCK_DIR: Too many readers.
25442
25443
25444 Stream: BOS Typewriter Crashes system
25445
25446 Time: While system is running.
25447
25448 Meaning: Too many processes attempted to request a read
25449 lock on a given directory. This may indicate a
25450 hardware problem.
25451
25452 Action: $reboot
25453
25454
25455
25456
25457
25458
25459
25460
25461
25462
25463 lock -439- MR12.5 10/27/92^L
25464
25465
25466 lock.pl1
25467 lock: LOCK_DIR: write lock call with read lock
25468 held. dp = PTR uid = UID.
25469
25470
25471 Stream: BOS Typewriter Terminates user process
25472
25473 Time: While system is running.
25474
25475 Meaning: A request was made to lock a directory for writing
25476 when the process already possessed a read lock on
25477 that directory. This indicates a supervisor
25478 programming error.
25479
25480 Action: $reboot
25481
25482
25483
25484 lock.pl1
25485 lock: lock_fast mylock err PTR
25486
25487
25488 Stream: BOS Typewriter Crashes system
25489
25490 Time: While system is running.
25491
25492 Meaning: An attempt to lock a fast lock found the lock
25493 already locked to the requesting process. This
25494 indicates a supervisor programming error.
25495
25496 Action: $reboot
25497
25498
25499
25500 lock.pl1
25501 lock: pds$block_lock_count <= 0. caller = PTR
25502
25503
25504 Stream: $lock_severity
25505
25506 Time: While system is running.
25507
25508 Meaning: An attempt to unlock a lock found that the process
25509 was holding no locks. This indicates a supervisor
25510 programming error.
25511
25512 Action: $reboot
25513
25514
25515
25516
25517
25518
25519
25520
25521 lock -440- MR12.5 10/27/92^L
25522
25523
25524 lock.pl1
25525 lock: stacq hardware failure on PTR
25526
25527
25528 Stream: BOS Typewriter Crashes system
25529
25530 Time: While system is running.
25531
25532 Meaning: The hardware failed to unlock the specified lock
25533 using a stacq instruction.
25534
25535 Action: Fix the hardware.
25536
25537
25538
25539 lock.pl1
25540 lock: unlock_dir with dir.modify - uid = UID -
25541 callerp = PTR
25542
25543
25544 Stream: Logged in SYSERR log.
25545
25546 Time: While system is running.
25547
25548 Meaning: A directory being unlocked appears to have been
25549 undergoing a modification sequence that has not
25550 completed.
25551
25552 Action: The next reference to the directory will force a
25553 directory salvage.
25554
25555
25556
25557 lock.pl1
25558 lock: UNLOCK_DIR: dir DIR_LOCK_IND not locked.
25559 caller = PTR.
25560
25561
25562 Stream: $lock_severity
25563
25564 Time: While system is running.
25565
25566 Meaning: A request to unlock a directory found that the
25567 dir_lock_seg entry does not show that the
25568 directory was locked.
25569
25570
25571 A: $reboot
25572
25573
25574
25575
25576
25577
25578
25579 lock -441- MR12.5 10/27/92^L
25580
25581
25582 lock.pl1
25583 lock: UNLOCK_DIR: dir DIR_LOCK_IND unlock called
25584 with bad uid caller = PTR
25585
25586
25587 Stream: Logged in SYSERR log.
25588
25589 Time: While system is running.
25590
25591 Meaning: A request to unlock a directory found that the UID
25592 of the directory does not match the UID at the
25593 time the directory was locked. However the UID
25594 does match that in the KST. This normally
25595 indicates that the directory was salvaged during
25596 the time that it was locked.
25597
25598
25599
25600 lock.pl1
25601 lock: UNLOCK_DIR: lock count 0.
25602
25603
25604 Stream: $lock_severity
25605
25606 Time: While system is running.
25607
25608 Meaning: An attempt to unlock a directory found the
25609 dir_lock_seg entry for the directory not listing
25610 the directory as locked.
25611
25612 Action: $reboot
25613
25614
25615
25616 lock.pl1
25617 lock: UNLOCK_DIR: lock not read locked to
25618 process.
25619
25620
25621 Stream: $lock_severity
25622
25623 Time: While system is running.
25624
25625 Meaning: A request to unlock a directory locked for reading
25626 found that the requesting process was not holding
25627 the directory locked.
25628
25629 Action: $reboot
25630
25631
25632
25633
25634
25635
25636
25637 lock -442- MR12.5 10/27/92^L
25638
25639
25640 lock.pl1
25641 lock: UNLOCK_DIR: lock not write locked to
25642 process.
25643
25644
25645 Stream: $lock_severity
25646
25647 Time: While system is running.
25648
25649 Meaning: A request to unlock a directory that was found to
25650 be locked for writing was not locked to this
25651 process.
25652
25653 Action: $reboot
25654
25655
25656
25657 lock.pl1
25658 lock: UNLOCK_DIR: UID Mismatch.
25659
25660
25661 Stream: $lock_severity
25662
25663 Time: While system is running.
25664
25665 Meaning: When attempting to unlock a directory the UID for
25666 the directory found in the dir_lock_seg entry did
25667 not match that of the directory.
25668
25669 Action: $reboot
25670
25671
25672
25673 lock.pl1
25674 lock: unlock_fast lock PTR not locked to process.
25675 caller = PTR
25676
25677
25678 Stream: $lock_severity
25679
25680 Time: While system is running.
25681
25682 Meaning: An attempt to unlock a fast lock found that the
25683 lock was not held by the requesting process. This
25684 indicates a supervisor programming error.
25685
25686 Action: $reboot
25687
25688
25689
25690
25691
25692
25693
25694
25695 lock -443- MR12.5 10/27/92^L
25696
25697
25698 lock.pl1
25699 lock: VALIDATE_CACHE: FAILED running on cpu N
25700 memory address OOOOOOOO oct.
25701
25702
25703 Stream: BOS Typewriter.
25704
25705 Time: While system is running.
25706
25707 Meaning: This is most likely a cache write notify problem
25708 with the 8/70m processor "CPU N" or the System
25709 Control Unit containing the "memory address
25710 OOOOOOOO."
25711
25712 Action: Contact the system administrator.
25713
25714
25715
25716 page_error.alm
25717 lock_volmap: MYLOCK on volmap lock for
25718 dskX_NNS.
25719
25720
25721 Stream: BOS Typewriter Crashes system
25722
25723 Time: While system is running.
25724
25725 Meaning: A process attempted to lock the Volume Map lock
25726 for dskX_NNS while already owning the lock.
25727 This indicates a software malfunction.
25728
25729 Action: Follow normal recovery procedures.
25730
25731
25732
25733 page_error.alm
25734 lock_volmap: STACQ fails on dskX_NNS.
25735
25736
25737 Stream: BOS Typewriter Crashes system
25738
25739 Time: While system is running.
25740
25741 Meaning: The stacq instruction used to lock the Volume Map
25742 on dskX_NNS did not operate correctly. This
25743 indicates processor or memory malfunction.
25744
25745 Action: Follow normal recovery procedures.
25746
25747
25748
25749
25750
25751
25752
25753 lock_volmap -444- MR12.5 10/27/92^L
25754
25755
25756 logical_volume_manager.pl1
25757 logical_volume_manager: nonzero brother pvt
25758 thread
25759
25760
25761 Stream: BOS Typewriter Crashes system
25762
25763 Time: While system is running.
25764
25765 Meaning: This indicates a logic error in the supervisor or
25766 CPU or memory hardware problems.
25767
25768 Action: Follow normal recovery procedures.
25769
25770
25771
25772 lg_ctl_.pl1
25773 LOGIN PERSON.PROJECT PROC_TYPE CHANNEL STATE
25774
25775
25776 Stream: as severity1
25777
25778 Time: While system is running.
25779
25780 Meaning: The user PERSON.PROJECT was successfully
25781 identified and authenticated on channel CHANNEL.
25782 The process type PROC_TYPE indicates the type of
25783 login and can be either "int" "dmn" "opr" or "Q
25784 N". These correspond to "interactive" "daemon"
25785 "operator" or "absentee" logins. "Q N"
25786 designates the absentee queue. STATE indicates
25787 the state of the login. It can either be
25788 "create" indicating that a process was created
25789 for the user; "connect loop" indicating that the
25790 user was queried as to what he/she wanted to do
25791 with respect to disconnected processes; or some
25792 other value indicating what was done to the user's
25793 disconnected processes.
25794
25795
25796
25797
25798
25799
25800
25801
25802
25803
25804
25805
25806
25807
25808
25809
25810
25811 LOGIN PERSON.PROJECT -445- MR12.5 10/27/92^L
25812
25813
25814 lg_ctl_.pl1
25815 LOGIN DENIED PERSON.PROJECT PROC_TYPE CHANNEL
25816 REASON
25817
25818
25819 Stream: as severity1
25820
25821 Time: While system is running.
25822
25823 Meaning: An operator login was denied for PERSON.PROJECT on
25824 channel CHANNEL for the reason specified in
25825 REASON. The process type is opr for operator
25826 login attempts.
25827
25828
25829
25830 daemon_user_manager_.pl1
25831 login: Cannot login NAME.PROJ SOURCE
25832 ERROR_MESSAGE
25833
25834
25835 Stream: as severity1
25836
25837 Time: While system is running.
25838
25839 Meaning: Illegal login arguments have been given when
25840 attempting to log in a daemon user. No action was
25841 taken.
25842
25843 Action: Enter a corrected command.
25844
25845
25846
25847 daemon_user_manager_.pl1
25848 login: ERROR_MESSAGE. creating event channel for
25849 NAME PROJ SOURCE
25850
25851
25852 Stream: as severity2
25853
25854 Time: In response to an operator command.
25855
25856 Meaning: This message indicates a system error in setting
25857 up a daemon user. The daemon cannot be logged in.
25858
25859 Action: Contact the system programming staff. Try again.
25860
25861
25862
25863
25864
25865
25866
25867
25868
25869 login -446- MR12.5 10/27/92^L
25870
25871
25872 daemon_user_manager_.pl1
25873 login: ERROR_MESSAGE. creating proc for NAME
25874 PROJ SOURCE
25875
25876
25877 Stream: as severity2
25878
25879 Time: In response to an operator command.
25880
25881 Meaning: A daemon process cannot be created. This is
25882 probably due to a serious system bug. The daemon
25883 is not logged in.
25884
25885 Action: Contact the system programming staff.
25886
25887
25888
25889 daemon_user_manager_.pl1
25890 login: ERROR_MESSAGE. declaring ev_call_chn for
25891 NAME PROJ SOURCE
25892
25893
25894 Stream: as severity2
25895
25896 Time: In response to an operator command.
25897
25898 Meaning: This message indicates a system error in setting
25899 up a daemon user. The daemon cannot be logged in.
25900
25901 Action: Contact the system programming staff.
25902
25903
25904
25905 daemon_user_manager_.pl1
25906 login: NAME.PROJ already logged in on SOURCE
25907
25908
25909 Stream: as severity1
25910
25911 Time: In response to an operator command.
25912
25913 Meaning: This is the response to the login command if the
25914 source specified by SOURCE is already in use.
25915 Each daemon process must have a different source
25916 name. The daemon user is not logged in. Usually
25917 this message is the result of attempting to
25918 perform an operation that has already been done.
25919
25920 Action: Reissue the command with another source or
25921 continue.
25922
25923
25924
25925
25926
25927 login -447- MR12.5 10/27/92^L
25928
25929
25930 daemon_user_manager_.pl1
25931 login: no login NAME.PROJ SOURCE REASON
25932
25933
25934 Stream: as severity1
25935
25936 Time: In response to an operator command.
25937
25938 Meaning: The operator issued a login NAME PROJ SOURCE
25939 command but the daemon user named cannot be logged
25940 in for the reason given. If REASON is badpers or
25941 bad_proj the NAME or PROJ was probably
25942 misspelled. If REASON is non_daem the user
25943 NAME.PROJ is not authorized to be a daemon user.
25944
25945 Action: Correct the command if misspelled and try to log
25946 in again.
25947
25948
25949
25950 lg_ctl_.pl1
25951 LOGOUT PERSON.PROJECT PROC_TYPE CHANNEL REASON
25952
25953
25954 Stream: as severity1
25955
25956 Time: While system is running.
25957
25958 Meaning: The user PERSON.PROJECT on channel CHANNEL with
25959 process type PROC_TYPE either logged out or was
25960 logged out. The reason is specified in REASON.
25961 This user/channel logout did not affect a process.
25962 This can occur for slave dialed channels or
25963 channels dropped from message coordinator service.
25964
25965
25966
25967 daemon_user_manager_.pl1
25968 logout: Entry not found. NAME PROJ SOURCE
25969
25970
25971 Stream: as severity1
25972
25973 Time: In response to an operator logout command.
25974
25975 Meaning: This is a response to an incorrect logout command.
25976 There is no entry in the daemon user table for
25977 NAME.PROJ.
25978
25979 Action: Check the spelling for accuracy and try again.
25980
25981
25982
25983
25984
25985 logout -448- MR12.5 10/27/92^L
25986
25987
25988 disk_table_.pl1
25989 lv LVNAME is not mounted
25990
25991
25992 Stream: Initializer process output.
25993
25994 Time: While system is running.
25995
25996 Meaning: The operator issued a dlv LVNAME command but
25997 LVNAME was not mounted.
25998
25999 Action: Enter a corrected command line.
26000
26001
26002
26003 disk_table_.pl1
26004 lv LVNAME mounted
26005
26006
26007 Stream: Initializer process output.
26008
26009 Time: While system is running.
26010
26011 Meaning: The mounting of LVNAME is complete.
26012
26013 Action: Enter a corrected command line.
26014
26015
26016
26017 lv_request_.pl1
26018 lv_request_: Beginning mount of LV LVNAME for
26019 PERSON.PROJECT.TAG PROCESSID
26020
26021
26022 Stream: $as0
26023
26024 Time: When processing a disk mount/demount interrupt.
26025
26026 Meaning: The volumes associated with LVNAME are now being
26027 mounted for the process identified by
26028 PERSON.PROJECT.TAG and PROCESSID.
26029
26030 Action: No operator action is required.
26031
26032
26033
26034
26035
26036
26037
26038
26039
26040
26041
26042
26043 lv_request_ -449- MR12.5 10/27/92^L
26044
26045
26046 lv_request_.pl1
26047 lv_request_: ERROR_MESSAGE. Masking event calls.
26048
26049
26050 Stream: $as2
26051
26052 Time: When processing a disk mount/demount interrupt.
26053
26054 Meaning: An error occurred while attempting to mask event
26055 call wakeups. ERROR_MESSAGE is the text
26056 associated with the error code returned by
26057 ipc_$mask_ev_calls. This indicates a logic error
26058 in the supervisor or CPU or memory hardware
26059 problems.
26060
26061 Action: Contact the system administrator.
26062
26063
26064
26065 lv_request_.pl1
26066 lv_request_: ATTACHED LV LVNAME to
26067 PERSON.PROJECT.TAG PROCESSID.
26068
26069
26070 Stream: $as0
26071
26072 Time: When processing a disk mount/demount interrupt.
26073
26074 Meaning: This message records attachment of logical volume
26075 LVNAME to the process identified by
26076 PERSON.PROJECT.TAG and PROCESSID.
26077
26078 Action: No operator action is required.
26079
26080
26081
26082 lv_request_.pl1
26083 lv_request_: bad LV attach table index N in
26084 DEMOUNT request
26085
26086
26087 Stream: $as2
26088
26089 Time: When processing a disk mount/demount interrupt.
26090
26091 Meaning: The Logical Volume attach table index given in the
26092 event message associated with the mount or demount
26093 interrupt is invalid. This indicates a logic
26094 error in the supervisor or CPU or memory hardware
26095 problems.
26096
26097 Action: Contact the system administrator.
26098
26099
26100
26101 lv_request_ -450- MR12.5 10/27/92^L
26102
26103
26104 lv_request_.pl1
26105 lv_request_: bad transmission: EVENT_MESSAGE
26106
26107
26108 Stream: $as2
26109
26110 Time: When processing a disk mount/demount interrupt.
26111
26112 Meaning: An unexpected EVENT_MESSAGE was received by the
26113 mount/demount interrupt handler. This indicates a
26114 logic error in the supervisor or CPU or memory
26115 hardware problems.
26116
26117 Action: Contact the system administrator.
26118
26119
26120
26121 lv_request_.pl1
26122 lv_request_: Cannot send message to
26123 PERSON.PROJECT.TAG PROCESSID: ADDED_INFO
26124
26125
26126 Stream: $as2
26127
26128 Time: When processing a disk mount/demount interrupt.
26129
26130 Meaning: The Initializer is attempting to respond to a
26131 request to mount or demount a logical volume but
26132 is unable to send a wakeup to the user process.
26133 The process may have logged out. This indicates a
26134 logic error in the supervisor or CPU or memory
26135 hardware problems.
26136
26137 Action: Contact the system administrator.
26138
26139
26140
26141 lv_request_.pl1
26142 lv_request_: Denied LV LVNAME to
26143 PERSON.PROJECT.TAG PROCESSID
26144
26145
26146 Stream: $as0
26147
26148 Time: When dismounting a logical volume.
26149
26150 Meaning: The user process identified by PERSON.PROJECT.TAG
26151 and PROCESSID was waiting to mount a logical
26152 volume LVNAME which is being dismounted by the
26153 operator. The mount request was therefore denied.
26154
26155 Action: No operator action is required.
26156
26157
26158
26159 lv_request_ -451- MR12.5 10/27/92^L
26160
26161
26162 lv_request_.pl1
26163 lv_request_: DETACHED LV LVNAME from
26164 PERSON.PROJECT.TAG PROCESSID.
26165
26166
26167 Stream: $as0
26168
26169 Time: When processing a disk mount/demount interrupt.
26170
26171 Meaning: This message records detachment of logical volume
26172 LVNAME from the process identified by
26173 PERSON.PROJECT.TAG and PROCESSID.
26174
26175 Action: No operator action is required.
26176
26177
26178
26179 lv_request_.pl1
26180 lv_request_: ERROR_MESSAGE. Cannot initialize
26181 logical volume mounting software.
26182
26183
26184 Stream: $as2
26185
26186 Time: System Intialization.
26187
26188 Meaning: Initialization of the logical volume attach table
26189 failed. ERROR_MESSAGE is the text associated with
26190 the error code returned by
26191 initializer_mdc_$init_lvat.
26192
26193 Action: Contact the system administrator.
26194
26195
26196
26197 lv_request_.pl1
26198 lv_request_: No drives available to mount LV
26199 LVNAME for PERSON.PROJECT.TAG PROCESSID
26200
26201
26202 Stream: $as0
26203
26204 Time: When processing a disk mount/demount interrupt.
26205
26206 Meaning: Drives needed to mount the volumes of LVNAME were
26207 in use or deleted. The logical volume could not
26208 be mounted for the process identified by
26209 PERSON.PROJECT.TAG and PROCESSID.
26210
26211 Action: No operator action is required.
26212
26213
26214
26215
26216
26217 lv_request_ -452- MR12.5 10/27/92^L
26218
26219
26220 lv_request_.pl1
26221 lv_request_: Spurious wakeup EVENT_MESSAGE
26222 received from PERSON.PROJECT.TAG PROCESSID RINGNO
26223
26224 Stream: $as0
26225
26226
26227 Time: When processing a disk mount/demount interrupt.
26228
26229 Meaning: A wakeup was received on the lv_request_ interrupt
26230 event channel with event data EVENT_MESSAGE from
26231 the process with PERSON.PROJECT.TAG PROCESSID and
26232 RINGNO. This message is invalid because it did
26233 not come from the Initializer ring 1 environment.
26234
26235 Action: No operator action is required.
26236
26237
26238
26239 lv_request_.pl1
26240 lv_request_: Unexpected condition CONDNAME
26241 occurred.
26242
26243
26244 Stream: $as2
26245
26246 Time: When processing a disk mount/demount interrupt.
26247
26248 Meaning: Condition CONDNAME was signalled unexpectedly
26249 during a mount or demount request. An answering
26250 service dump is created to further document the
26251 cause of the error.
26252
26253 Action: $notify_sa.
26254
26255
26256
26257 lv_request_communicator_.pl1
26258 lv_request_communicator_: code CCC from wakeup
26259
26260
26261 Stream: BOS Typewriter.
26262
26263 Time: While system is running.
26264
26265 Meaning: A wakeup could not be sent to the initializer
26266 process in order to perform communication about
26267 attachment/detachment of logical volumes.
26268
26269 Action: Contact the system programming staff.
26270
26271
26272
26273
26274
26275 lv_request_communicator_ -453- MR12.5 10/27/92^L
26276
26277
26278 lv_request_communicator_.pl1
26279 lv_request_communicator_: lock ^= processid lvate
26280 PPP
26281
26282
26283 Stream: BOS Typewriter.
26284
26285 Time: In response to a user's detach_lv command
26286
26287 Meaning: A logical volume attachment table entry became
26288 disassociated from a user to whom it had been
26289 assigned. This indicates a logic error in the
26290 supervisor or CPU or memory hardware problems.
26291
26292 Action: Contact the system programming staff. Be prepared
26293 to demount logical volumes manually which might
26294 otherwise have been demounted automatically.
26295
26296
26297
26298 make_branches.pl1
26299 make_branches: bad path name PATH
26300
26301
26302 Stream: BOS Typewriter Crashes system
26303
26304 Time: System Intialization.
26305
26306 Meaning: This indicates a logic error in the supervisor or
26307 CPU or memory hardware problems.
26308
26309 Action: Follow normal recovery procedures. The Multics
26310 System Tape may be incorrect. If the problem
26311 persists try another MST.
26312
26313
26314
26315 make_branches.pl1
26316 make_branches: could not delete PATH:
26317 ERROR_MESSAGE
26318
26319
26320 Stream: BOS Typewriter Crashes system
26321
26322 Time: System Intialization.
26323
26324 Meaning: This indicates a logic error in the supervisor or
26325 CPU or memory hardware problems.
26326
26327 Action: Follow normal recovery procedures. The Multics
26328 System Tape may be incorrect. If the problem
26329 persists try another MST.
26330
26331
26332
26333 make_branches -454- MR12.5 10/27/92^L
26334
26335
26336 make_branches.pl1
26337 make_branches: delete: could not turn PATH
26338 safety switch off: ERROR_MESSAGE
26339
26340
26341 Stream: BOS Typewriter Crashes system
26342
26343 Time: System Intialization.
26344
26345 Meaning: This indicates a logic error in the supervisor or
26346 CPU or memory hardware problems.
26347
26348 Action: Follow normal recovery procedures. The Multics
26349 System Tape may be incorrect. If the problem
26350 persists try another MST.
26351
26352
26353
26354 make_branches.pl1
26355 make_branches: delete: failed to rename
26356
26357
26358 Stream: BOS Typewriter Crashes system
26359
26360 Time: System Intialization.
26361
26362 Meaning: This indicates a logic error in the supervisor or
26363 CPU or memory hardware problems.
26364
26365 Action: Follow normal recovery procedures. The Multics
26366 System Tape may be incorrect. If the problem
26367 persists try another MST.
26368
26369
26370
26371 make_branches.pl1
26372 make_branches: delete: renaming NAME to UNIQUE
26373 in DIRNAME
26374
26375
26376 Stream: BOS Typewriter.
26377
26378 Time: System Intialization.
26379
26380 Meaning: A segment which is being loaded from the system
26381 tape encountered a previous copy on a physical
26382 volume which is not now mounted. The old version
26383 of the segment is being renamed so that the new
26384 copy can be loaded.
26385
26386 Action: Note for system programmer action. The system
26387 programmers will want to delete the unique-named
26388 segment.
26389
26390
26391 make_branches -455- MR12.5 10/27/92^L
26392
26393
26394 make_branches.pl1
26395 make_branches: error from append on PATH:
26396 ERROR_MESSAGE
26397
26398
26399 Stream: BOS Typewriter Crashes system
26400
26401 Time: System Intialization.
26402
26403 Meaning: This indicates a logic error in the supervisor or
26404 CPU or memory hardware problems.
26405
26406 Action: Follow normal recovery procedures. The Multics
26407 System Tape may be incorrect. If the problem
26408 persists try another MST.
26409
26410
26411
26412 make_branches.pl1
26413 make_branches: error from asd_$replace_sall on
26414 PATH: ERROR_MESSAGE
26415
26416
26417 Stream: BOS Typewriter Crashes system
26418
26419 Time: System Intialization.
26420
26421 Meaning: This indicates a logic error in the supervisor or
26422 CPU or memory hardware problems.
26423
26424 Action: Follow normal recovery procedures. The Multics
26425 System Tape may be incorrect. If the problem
26426 persists try another MST.
26427
26428
26429
26430 make_branches.pl1
26431 make_branches: error from chname on PATH:
26432 ERROR_MESSAGE
26433
26434
26435 Stream: BOS Typewriter Crashes system
26436
26437 Time: System Intialization.
26438
26439 Meaning: This indicates a logic error in the supervisor or
26440 CPU or memory hardware problems.
26441
26442 Action: Follow normal recovery procedures. The Multics
26443 System Tape may be incorrect. If the problem
26444 persists try another MST.
26445
26446
26447
26448
26449 make_branches -456- MR12.5 10/27/92^L
26450
26451
26452 make_sdw.pl1
26453 make_sdw: no hardcore partitions available.
26454
26455
26456 Stream: BOS Typewriter Crashes system
26457
26458 Time: System Intialization.
26459
26460 Meaning: No hardcore partitions were defined on any of the
26461 packs on the drives specified by the ROOT CONFIG
26462 card. At least the RPV must have a hardcore
26463 partition. Supervisor segments cannot be created.
26464
26465 Action: If this is a cold boot which is most likely the
26466 RPV was initialized without a hardcore partition.
26467 It must be reinitialized. Check the PART HC
26468 CONFIG card one of which must describe the RPV
26469 during a cold boot and reboot. If this is not a
26470 cold boot the RPV has been damaged and volume
26471 recovery must be undertaken.
26472
26473
26474
26475 make_sdw.pl1
26476 make_sdw: out of hardcore partition for SEGNAME.
26477
26478
26479 Stream: BOS Typewriter Crashes system
26480
26481 Time: System Intialization.
26482
26483 Meaning: In attempting to allocate space for hardcore
26484 segment SEGNAME no more room could be found in
26485 any of the defined hardcore partitions.
26486
26487 Action: If this is a cold boot redefine the hardcore
26488 partition of the RPV to be larger. At least 1000
26489 decimal records is recommended. Change the PART
26490 HC CONFIG card describing the RPV to indicate
26491 this and reboot. If this is not a cold boot
26492 this situation is highly unlikely and indicates
26493 damage to one or more RLV volume labels. Volume
26494 recovery for part or all of the RLV should be
26495 undertaken.
26496
26497
26498
26499
26500
26501
26502
26503
26504
26505
26506
26507 make_sdw -457- MR12.5 10/27/92^L
26508
26509
26510 make_sdw.pl1
26511 make_sdw: XXXk ast pool to small.
26512
26513
26514 Stream: BOS Typewriter Crashes system
26515
26516 Time: System Intialization.
26517
26518 Meaning: There were not enough AST entries of size XXX k to
26519 allocate the permanent AST entries of the
26520 supervisor.
26521
26522 Action: Increase the number of AST entries of that size
26523 as specified on the SST CONFIG card
26524 substantially and reboot.
26525
26526
26527
26528 make_segs_paged.pl1
26529 make_segs_paged: sorted_segs array overflowed.
26530
26531
26532 Stream: BOS Typewriter Crashes system
26533
26534 Time: System Intialization.
26535
26536 Meaning: The number of paged segments in collection 1 is
26537 larger than the internal buffer in the program
26538 make_segs_paged required to sort them by main
26539 memory address. This indicates an error in
26540 construction of the system i.e. too many header
26541 entries or may be symptomatic of main memory or
26542 CPU hardware problems.
26543
26544 Action: If this recurs revert to a previous system tape.
26545 No emergency shutdown is needed.
26546
26547
26548
26549 makestack.pl1
26550 makestack: error appending STACKNAME
26551
26552
26553 Stream: BOS Typewriter Terminates user process
26554
26555 Time: System Intialization. Process/ring
26556 initialization. Just prior to using a new ring.
26557
26558 Meaning: The process directory is probably messed up.
26559
26560 Action: Ignore unless it's the initializer in which case
26561 bring the system back up. If problem persists
26562 contact the system administrator.
26563
26564
26565 makestack -458- MR12.5 10/27/92^L
26566
26567
26568 makestack.pl1
26569 makestack: error finding DIRNAME>ENAME for
26570 STACKNAME.
26571
26572
26573 Stream: BOS Typewriter Terminates user process
26574
26575 Time: System Intialization. Process/ring
26576 initialization.
26577
26578 Action: Ignore unless it's the initializer in which case
26579 bring the system back up. If problem persists
26580 contact the system administrator.
26581
26582
26583
26584 makestack.pl1
26585 makestack: error from initiate_search_rules.
26586
26587
26588 Stream: BOS Typewriter Terminates user process
26589
26590 Time: Process/ring initialization. Just prior to using
26591 new ring.
26592
26593 Meaning: The default search rules are missing from ahd
26594 active hardcore data. These are usually loaded
26595 by the command set_system_search_rules.
26596
26597 Action: Contact the system administrator.
26598
26599
26600
26601 makestack.pl1
26602 makestack: error from set$max_length_ptr on
26603 STACKNAME.
26604
26605
26606 Stream: BOS Typewriter Terminates user process
26607
26608 Time: System Intialization. Process/ring
26609 initialization. Just prior to using a new ring.
26610
26611 Meaning: The process directory is probably messed up.
26612
26613 Action: Ignore unless it's the initializer in which case
26614 bring the system back up. If problem persists
26615 contact the system administrator.
26616
26617
26618
26619
26620
26621
26622
26623 makestack -459- MR12.5 10/27/92^L
26624
26625
26626 makestack.pl1
26627 makestack: error getting bit count for original
26628 prelinked STACK_NAME
26629
26630
26631 Stream: BOS Typewriter Terminates user process
26632
26633 Time: System Intialization. Process/ring
26634 initialization. Just prior to using a new ring.
26635
26636 Meaning: A directory containing a prelinked subsystem is
26637 probably messed up.
26638
26639 Action: The directory should be prelinked again.
26640
26641
26642
26643 makestack.pl1
26644 makestack: error initiating STACKNAME
26645
26646
26647 Stream: BOS Typewriter Terminates user process
26648
26649 Time: System Intialization. Process/ring
26650 initialization. Just prior to using a new ring.
26651
26652 Action: Ignore unless it's the initializer in which case
26653 bring the system back up. If problem persists
26654 contact the system administrator.
26655
26656
26657
26658 mc_commands_.pl1
26659 mc_commands_$mc_login: Channel XXXX dialed to
26660 Initializer NAME ACCEPTED.
26661
26662
26663 Stream: as severity 1
26664
26665 Time: In response to a message coordinator dial request.
26666
26667 Meaning: Informative message indicating that a successful
26668 dialin occured on the specified channel by the
26669 named operator.
26670
26671 Action: No operator action is required.
26672
26673
26674
26675
26676
26677
26678
26679
26680
26681 mc_commands_$mc_login -460- MR12.5 10/27/92^L
26682
26683
26684 mc_commands_.pl1
26685 mc_commands_$mc_login: Channel XXXX dialed to
26686 Initializer NAME.
26687
26688
26689 Stream: as severity 1
26690
26691 Time: In response to a message coordinator dial request.
26692
26693 Meaning: Informative message indicating that a successful
26694 dialin occured on the specified channel by the
26695 named operator. A subsequent accept is required
26696 by an authenticated operator to complete the
26697 attachment.
26698
26699 Action: No operator action is required.
26700
26701
26702
26703 mc_commands_.pl1
26704 mc_commands_$mc_login: Channel XXXX vchannel
26705 YYYY dialed to Initializer NAME ACCEPTED.
26706
26707
26708 Stream: as severity 1
26709
26710 Time: In response to a message coordinator dial request.
26711
26712 Meaning: Informative message indicating that a successful
26713 dialin occured on the specified channel by the
26714 named operator.
26715
26716 Action: No operator action is required.
26717
26718
26719
26720 mc_commands_.pl1
26721 mc_commands_$mc_login: Channel XXXX vchannel
26722 YYYY dialed to Initializer NAME.
26723
26724
26725 Stream: as severity 1
26726
26727 Time: In response to a message coordinator dial request.
26728
26729 Meaning: Informative message indicating that a successful
26730 dialin occured on the specified channel by the
26731 named operator. A subsequent accept is required
26732 by an authenticated operator to complete the
26733 attachment.
26734
26735 Action: No operator action is required.
26736
26737
26738
26739 mc_commands_$mc_login -461- MR12.5 10/27/92^L
26740
26741
26742 mc_commands_.pl1
26743 mc_commands_$mc_login: error: Channel XXXX
26744 already in use.
26745
26746
26747 Stream: sc error_output
26748
26749 Time: In response to an operator command.
26750
26751 Meaning: The channel specified for MNA attachment is
26752 already in use by the message coordinator.
26753
26754 Action: Enter a corrected command line.
26755
26756
26757
26758 mc_tty_.pl1
26759 mc_tty_: called with bad pointer
26760
26761
26762 Stream: BOS typewriter.
26763
26764 Time: While system is running.
26765
26766 Meaning: This message indicates a bug in system_control_ or
26767 in the Message Coordinator. An illegal signal has
26768 been received by the attached terminal handler in
26769 system_control_; the data pointer that should
26770 point to an entry in the mc_anstbl does not point
26771 to the correct segment. The signal is ignored.
26772
26773 Action: Contact the system programming staff.
26774
26775
26776
26777 mc_tty_.pl1
26778 mc_tty_: called with null ptr
26779
26780
26781 Stream: BOS typewriter.
26782
26783 Time: While system is running.
26784
26785 Meaning: This message indicates a bug in system_control_ or
26786 in the Message Coordinator. An illegal signal has
26787 been received by the attached terminal handler in
26788 system_control_. The signal is ignored.
26789
26790 Action: Contact the system programming staff.
26791
26792
26793
26794
26795
26796
26797 mc_tty_ -462- MR12.5 10/27/92^L
26798
26799
26800 mc_tty_.pl1
26801 mc_tty_: channel CHAN hung up.
26802
26803
26804 Stream: BOS Typewriter sounds beeper
26805
26806 Time: While system is running.
26807
26808 Meaning: This message indicates that an attempt has been
26809 made to read input from a terminal device channel
26810 attached to the Message Coordinator and that the
26811 channel is not active. This condition may be due
26812 to a transient line condition a terminal failure
26813 or a communications line failure. The system
26814 attempts to proceed.
26815
26816 Action: If the terminal is a hardwired device and can be
26817 reconnected do so. If this is a dialup channel
26818 that has failed use the substty or drop commands
26819 to remove the channel.
26820
26821
26822
26823 mc_tty_.pl1
26824 mc_tty_: channel CHAN masked by FNP.
26825
26826
26827 Stream: BOS Typewriter sounds beeper
26828
26829 Time: While system is running.
26830
26831 Meaning: The channel CHAN has just been masked by the
26832 FNP. This is usually due to some hardware problem
26833 with the channel.
26834
26835 Action: Fix the problem before re-using the channel.
26836
26837
26838
26839 mc_tty_.pl1
26840 mc_tty_: Channel CHANNEL vchannel VCHANNEL
26841 received TIMEOUT while awaiting DIALUP wakeup.
26842
26843
26844 Stream: BOS Typewriter.
26845
26846 Time: While system is running.
26847
26848 Meaning: Wakeup was not acted on soon enough by AS.
26849
26850 Action: Contact the system programming staff.
26851
26852
26853
26854
26855 mc_tty_ -463- MR12.5 10/27/92^L
26856
26857
26858 mc_tty_.pl1
26859 mc_tty_: Channel CHANNEL vchannel VCHANNEL
26860 received WAKEUP_TYPE wakeup while awaiting DIALUP.
26861
26862
26863 Stream: BOS Typewriter.
26864
26865 Time: While system is running.
26866
26867 Meaning: Received an unexpected WAKEUP_TYPE wakeup while
26868 waiting for a DIALUP wakeup. Dialup will not
26869 succeed.
26870
26871 Action: Contact the system programming staff.
26872
26873
26874
26875 mc_tty_.pl1
26876 mc_tty_: Channel CHANNEL received TIMEOUT while
26877 awaiting DIALUP wakeup.
26878
26879
26880 Stream: BOS Typewriter.
26881
26882 Time: While system is running.
26883
26884 Meaning: Wakeup was not acted on soon enough by AS.
26885
26886 Action: Contact the system programming staff.
26887
26888
26889
26890 mc_tty_.pl1
26891 mc_tty_: Channel CHANNEL received WAKEUP_TYPE
26892 wakeup while awaiting DIALUP.
26893
26894
26895 Stream: BOS Typewriter.
26896
26897 Time: While system is running.
26898
26899 Meaning: Did not receive a DIALUP wakeup WAKEUP_TYPE when
26900 should have. Recieved an unexpected WAKEUP_TYPE.
26901
26902 Action: Contact the system programming staff.
26903
26904
26905
26906
26907
26908
26909
26910
26911
26912
26913 mc_tty_ -464- MR12.5 10/27/92^L
26914
26915
26916 mc_tty_.pl1
26917 mc_tty_: ERROR_TABLE_MESSAGE Connecting to
26918 CHANNEL vchannel VCHANNEL.
26919
26920
26921 Stream: BOS Typewriter.
26922
26923 Time: While system is running.
26924
26925 Meaning: Error creating an IOCB while attempting to connect
26926 channel CHANNEL as message coordinator terminal.
26927 Channel cannot be accepted as MC terminal. Cannot
26928 attach and open I/O switches.
26929
26930 Action: Contact the system programming staff.
26931
26932
26933
26934 mc_tty_.pl1
26935 mc_tty_: ERROR_TABLE_MESSAGE Connecting to
26936 CHANNEL.
26937
26938
26939 Stream: BOS Typewriter.
26940
26941 Time: While system is running.
26942
26943 Meaning: Error creating an IOCB while attempting to connect
26944 channel CHANNEL as message coordinator terminal.
26945 Channel cannot be accepted as MC terminal. Cannot
26946 attach and open I/O switches.
26947
26948 Action: Contact the system programming staff.
26949
26950
26951
26952 mc_tty_.pl1
26953 mc_tty_: ERROR_TABLE_MESSAGE Could not get
26954 channel CHAN back from MC.
26955
26956
26957 Stream: BOS Typewriter.
26958
26959 Time: While system is running.
26960
26961 Meaning: An error described by ERROR_TABLE_MESSAGE was
26962 returned from astty_$tty_event while trying to
26963 give channel CHAN back to the AS after a hangup.
26964
26965 Action: Contact the system programming staff.
26966
26967
26968
26969
26970
26971 mc_tty_ -465- MR12.5 10/27/92^L
26972
26973
26974 mc_tty_.pl1
26975 mc_tty_: ERROR_TABLE_MESSAGE Could not notify
26976 answering service of new login channel CHAN.
26977
26978
26979 Stream: BOS Typewriter.
26980
26981 Time: While system is running.
26982
26983 Meaning: An error described by ERROR_TABLE_MESSAGE was
26984 returned from hcs_$wakeup while trying to notify
26985 the AS about the new login channel CHAN after a
26986 hangup.
26987
26988 Action: Contact the system programming staff.
26989
26990
26991
26992 mc_tty_.pl1
26993 mc_tty_: ERROR_TABLE_MESSAGE Could not remove
26994 CHAN from MC use.
26995
26996
26997 Stream: BOS Typewriter.
26998
26999 Time: While system is running.
27000
27001 Meaning: An error described by ERROR_TABLE_MESSAGE was
27002 returned from mc_commands_$remove_tty while tring
27003 to remove channel CHAN from MC service after a
27004 hangup.
27005
27006 Action: Contact the system programming staff.
27007
27008
27009
27010 mc_tty_.pl1
27011 mc_tty_: ERROR_TABLE_MESSAGE Failed to set
27012 terminal type for CHAN.
27013
27014
27015 Stream: BOS Typewriter.
27016
27017 Time: While system is running.
27018
27019 Meaning: An error described ty ERROR_TABLE_MESSAGE was
27020 returned while trying to set the terminal type on
27021 channel CHAN.
27022
27023 Action: Depending on the error it may be ignored or the
27024 channel may be hungup. If the channel is hungup
27025 an attempt should be made to fix the error before
27026 connecting the terminal again.
27027
27028
27029 mc_tty_ -466- MR12.5 10/27/92^L
27030
27031
27032 mc_tty_.pl1
27033 mc_tty_: ERROR_TABLE_MESSAGE wru failed for CHAN.
27034
27035
27036 Stream: BOS Typewriter.
27037
27038 Time: While system is running.
27039
27040 Meaning: The CDT entry for channel CHAN requires an
27041 answerback but an error was returned while trying
27042 to read it. The returned error is described by
27043 ERROR_TABLE_MESSAGE.
27044
27045 Action: Verify that the channel is configured correctly in
27046 the CDT.
27047
27048
27049
27050 mc_tty_.pl1
27051 mc_tty_: Event sent from incorrect ring. event
27052 channel = N event message = M event sender = S
27053 device signal = D ring = R event data ptr = P
27054
27055
27056 Stream: BOS Typewriter.
27057
27058 Time: While system is running.
27059
27060 Meaning: An event was sent from a ring higher than the
27061 specified MNA ring 2.
27062
27063 Action: Contact the system programming staff.
27064
27065
27066
27067 mc_tty_.pl1
27068 mc_tty_: Invalid argument. Invalid DSA wakeup
27069 event type TYPE.
27070
27071
27072 Stream: $as0
27073
27074 Time: While system is running.
27075
27076 Meaning: A DSA wakeup event type TYPE was received which is
27077 out of the range of known event types. The wakeup
27078 was ignored.
27079
27080 Action: No operator action is required.
27081
27082
27083
27084
27085
27086
27087 mc_tty_ -467- MR12.5 10/27/92^L
27088
27089
27090 mc_tty_.pl1
27091 mc_tty_: Invalid argument. Invalid MCS wakeup
27092 event type TYPE.
27093
27094
27095 Stream: $as0
27096
27097 Time: While system is running.
27098
27099 Meaning: An MCS wakeup event type TYPE was received which
27100 is out of the range of known event types. The
27101 wakeup was ignored.
27102
27103 Action: No operator action is required.
27104
27105
27106
27107 mc_tty_.pl1
27108 mc_tty_: Invalid argument. Unexpected DSA wakeup
27109 event type TYPE.
27110
27111
27112 Stream: $as0
27113
27114 Time: While system is running.
27115
27116 Meaning: A known DSA wakeup event type TYPE was received
27117 but was not expected for a message coordinator
27118 terminal. The wakeup was ignored.
27119
27120 Action: No operator action is required.
27121
27122
27123
27124 mc_tty_.pl1
27125 mc_tty_: Invalid argument. Unexpected MCS wakeup
27126 event type TYPE.
27127
27128
27129 Stream: $as0
27130
27131 Time: While system is running.
27132
27133 Meaning: A known MCS wakeup event type TYPE was received
27134 but was not expected for a message coordinator
27135 terminal. The wakeup was ignored.
27136
27137
27138
27139
27140
27141
27142
27143
27144
27145 mc_tty_ -468- MR12.5 10/27/92^L
27146
27147
27148 mc_tty_.pl1
27149 mc_tty_: Invalid argument. Unexpected network
27150 type TYPE in event message.
27151
27152
27153 Stream: $as0
27154
27155 Time: While system is running.
27156
27157 Meaning: An unknown network ident in wakeup event message
27158 was received. The wakeup was ignored.
27159
27160 Action: No operator action is required.
27161
27162
27163
27164 mc_tty_.pl1
27165 mc_tty_: Line CHAN hung up.
27166
27167
27168 Stream: as severity 0
27169
27170 Time: While system is running.
27171
27172 Meaning: Channel CHAN has been hungup during a system
27173 shutdown.
27174
27175 Action: No operator action is required.
27176
27177
27178
27179 mc_tty_.pl1
27180 mc_tty_: No default ttp for CHANNEL line LINE
27181 baud BAUD.
27182
27183
27184 Stream: BOS Typewriter sounds beeper
27185
27186 Time: While system is running.
27187
27188 Meaning: Could not get default terminal type for terminal
27189 on CHANNEL which has a line type of LINE. Hangup
27190 will follow.
27191
27192 Action: Contact the system programming staff.
27193
27194
27195
27196
27197
27198
27199
27200
27201
27202
27203 mc_tty_ -469- MR12.5 10/27/92^L
27204
27205
27206 mc_tty_.pl1
27207 mc_tty_: sc_stat_$mc_ansp is null
27208
27209
27210 Stream: BOS Typewriter.
27211
27212 Time: While system is running.
27213
27214 Meaning: This message indicates a bug in system_control_ or
27215 in the Message Coordinator. A signal has been
27216 received by the attached terminal handler in
27217 system_control_ but the signal cannot be handled
27218 because the mc_anstbl cannot be located. The
27219 signal is ignored.
27220
27221 Action: Contact the system programming staff.
27222
27223
27224
27225 mca_attach_.pl1
27226 MCA: IO not released on DEVICE ipcNN in IMU-X
27227 PERSON.PROJ.T.
27228
27229
27230 Stream: Warning message.
27231
27232 Time: While system is running.
27233
27234 Meaning: The user is detaching the IPC but does not want
27235 the IO to be resumed.
27236
27237 Action: This is normally because the IPC is defective or
27238 no longer capable of handling normal I/O.
27239
27240
27241
27242 mca_attach_.pl1
27243 MCA: IO released on DEVICE ipcNN in IMU-X
27244 PERSON.PROJ.T.
27245
27246
27247 Stream: Logged in SYSERR log.
27248
27249 Time: While system is running.
27250
27251 Meaning: This message is stating that the normal flow of
27252 I/O for this device is being resumed.
27253
27254 Action: No operator action is required.
27255
27256
27257
27258
27259
27260
27261 MCA -470- MR12.5 10/27/92^L
27262
27263
27264 mca_attach_.pl1
27265 MCA: IO suspended on DEVICE ipcNN in IMU-X for
27266 PERSON.PROJ.T.
27267
27268
27269 Stream: Logged in SYSERR log.
27270
27271 Time: While system is running.
27272
27273 Meaning: This message is stating that the normal flow of
27274 I/O for this device is being suspended. This
27275 allows the user to stop or alter/reload an IPC
27276 without affecting the system.
27277
27278 Action: No operator action is required.
27279
27280
27281
27282 mcs_timer.pl1
27283 mcs_timer: Cannot get space to set timer NNN for
27284 devxsubchan DDDSSS.
27285
27286
27287 Stream: Logged in SYSERR log.
27288
27289 Time: While system is running.
27290
27291 Meaning: An attempt was made to set an MCS timer with the
27292 specified timer ID but it was not possible to
27293 allocate the necessary space in tty_buf to hold
27294 timer data block. The call is ignored.
27295
27296 Action: Contact the system programming staff.
27297
27298
27299
27300 mcs_timer.pl1
27301 mcs_timer: Channel not locked by this process.
27302 Devx = DDDD.
27303
27304
27305 Stream: BOS Typewriter Crashes system
27306
27307 Time: While system is running.
27308
27309 Meaning: A process called to perform an MCS timer
27310 operation but the channel it specified devx
27311 DDDD was not locked by the calling process. by
27312 the calling process.
27313
27314 Action: Contact the system programming staff.
27315
27316
27317
27318
27319 mcs_timer -471- MR12.5 10/27/92^L
27320
27321
27322 mcs_timer.pl1
27323 mcs_timer: Duplicate timer ID. Cannot set timer
27324 NNN for devxsubchan DDDSSS.
27325
27326
27327 Stream: Logged in SYSERR log.
27328
27329 Time: While system is running.
27330
27331 Meaning: An attempt was made to set an MCS timer with the
27332 specified timer ID but the channel already had an
27333 outstanding timer or queued timer interrupt with
27334 that ID. The call is ignored.
27335
27336 Action: Contact the system programming staff.
27337
27338
27339
27340 mcs_timer.pl1
27341 mcs_timer: Timer lock already locked to this
27342 process.
27343
27344
27345 Stream: BOS Typewriter Crashes system
27346
27347 Time: While system is running.
27348
27349 Meaning: A process that had the MCS timer lock locked tried
27350 to lock it again.
27351
27352 Action: Contact the system programming staff.
27353
27354
27355
27356 mcs_timer.pl1
27357 mcs_timer: Timer lock not locked by this process.
27358
27359
27360 Stream: BOS Typewriter Crashes system
27361
27362 Time: While system is running.
27363
27364 Meaning: A process called to unlock the MCS timer lock but
27365 did not have it locked.
27366
27367 Action: Contact the system programming staff.
27368
27369
27370
27371
27372
27373
27374
27375
27376
27377 mcs_timer -472- MR12.5 10/27/92^L
27378
27379
27380 mcs_timer.pl1
27381 mcs_timer: Timer not found. Cannot OOOOO timer
27382 NNN for devxsubchan DDDSSS.
27383
27384
27385 Stream: Logged in SYSERR log.
27386
27387 Time: While system is running.
27388
27389 Meaning: An attempt was made to perform operation OOOOO
27390 reset or change on an MCS timer when no timer or
27391 queued timer interrupt with the specified ID could
27392 be found for the requesting channel. The call is
27393 ignored.
27394
27395 Action: Contact the system programming staff.
27396
27397
27398
27399 mdc_create_.pl1
27400 mdc_create_$delete: No MDCS for DIRNAME.
27401
27402
27403 Stream: Logged in SYSERR log.
27404
27405 Time: While system is running.
27406
27407 Meaning: When deleting master directory DIRNAME the master
27408 directory control segment MDCS could not found.
27409 The directory was deleted anyway.
27410
27411 Action: No operator action is required.
27412
27413
27414
27415 mdc_create_.pl1
27416 mdc_create_$delete: TRP for DIRNAME on LVNAME
27417 negative.
27418
27419
27420 Stream: Logged in SYSERR log.
27421
27422 Time: While system is running.
27423
27424 Meaning: While deleting master directory DIRNAME an
27425 invalid negative time-record product was found.
27426 The invalid number has been ignored but volume
27427 accounting data may have been lost.
27428
27429 Action: No operator action is required.
27430
27431
27432
27433
27434
27435 mdc_create_$delete -473- MR12.5 10/27/92^L
27436
27437
27438 mdc_lock_.pl1
27439 mdc_lock_$lock: LOCK ERROR MESSAGE.
27440
27441
27442 Stream: Logged in SYSERR log.
27443
27444 Time: While system is running.
27445
27446 Meaning: A master directory operation failed because of a
27447 problem with the master directory control lock.
27448
27449 Action: No operator action is required.
27450
27451
27452
27453 mdc_lock_.pl1
27454 mdc_lock_$mdc_data_init: Unable to create
27455 PATHNAME. REASON.
27456
27457
27458 Stream: BOS Typewriter.
27459
27460 Time: System Intialization.
27461
27462 Meaning: Master directory control was unable to create the
27463 segment PATHNAME to be used for the master
27464 directory control lock for the REASON given.
27465 Subsequent master directory control operations may
27466 fail.
27467
27468 Action: ignore
27469
27470
27471
27472 mdc_lock_.pl1
27473 mdc_lock_$mdc_data_init: Unable to reclassify
27474 PATHNAME. REASON.
27475
27476
27477 Stream: BOS Typewriter.
27478
27479 Time: System Intialization.
27480
27481 Meaning: Master directory control was unable to reclassify
27482 the segment PATHNAME to its proper access class
27483 for the REASON given. This segment is to be used
27484 for the master directory control lock. Subsequent
27485 master directory control operations may fail.
27486
27487
27488
27489
27490
27491
27492
27493 mdc_lock_$mdc_data_init -474- MR12.5 10/27/92^L
27494
27495
27496 mdc_lock_.pl1
27497 mdc_lock_$mdc_data_init: Unable to truncate
27498 PATHNAME. REASON.
27499
27500
27501 Stream: BOS Typewriter.
27502
27503 Time: System Intialization.
27504
27505 Meaning: Master directory control was unable to truncate
27506 the segment PATHNAME for the REASON given. This
27507 segment is to be used for the master directory
27508 control lock. Subsequent master directory control
27509 operations may fail.
27510
27511 Action: No operator action is required.
27512
27513
27514
27515 mdc_lock_.pl1
27516 mdc_lock_$unlock: LOCK ERROR MESSAGE.
27517
27518
27519 Stream: Logged in SYSERR log.
27520
27521 Time: While system is running.
27522
27523 Meaning: At the completion of a master directory control
27524 operation some error occured unlocking the master
27525 directory control lock.
27526
27527 Action: No operator action is required.
27528
27529
27530
27531 mdc_lock_.pl1
27532 mdc_lock_: Unable to initiate PATHNAME. REASON.
27533
27534
27535 Stream: Logged in SYSERR log.
27536
27537 Time: While system is running.
27538
27539 Meaning: Master directory control was unable to initiate
27540 PATHNAME which contains the master directory
27541 control lock because of REASON. The master
27542 directory control operation requested was not
27543 performed.
27544
27545 Action: No operator action is required.
27546
27547
27548
27549
27550
27551 mdc_lock_ -475- MR12.5 10/27/92^L
27552
27553
27554 mdc_repair_.pl1
27555 mdc_repair_$register_mdir: DIRNAME registered on
27556 LVNAME quota=N.
27557
27558
27559 Stream: Logged in SYSERR log.
27560
27561 Time: While system is running.
27562
27563 Meaning: The master directory DIRNAME has been found which
27564 had not been recorded in the MDCS for volume
27565 LVNAME. The master directory has been registered
27566 and the quota of N has been charged to the
27567 Initializer.SysDaemon quota account. This problem
27568 may have been caused by the loss and subsequent
27569 retreival of the master directory control segment
27570 or by retreving a master directory. This message
27571 can only appear as a result of a register_mdir
27572 command performed by a system administrator.
27573
27574 Action: No operator action is required.
27575
27576
27577
27578 mdc_repair_.pl1
27579 mdc_repair_$register_mdir: Quota for DIRNAME on
27580 LVNAME changed from OLD to NEW.
27581
27582
27583 Stream: Logged in SYSERR log.
27584
27585 Time: While system is running.
27586
27587 Meaning: The quota of master directory DIRNAME was found be
27588 different from the quota recorded in the MDCS.
27589 The real quota is assumed to be correct and the
27590 MDCS is updated to reflect this quota. This may
27591 happen if a set_quota command had been used on a
27592 master directory. This message can only appear as
27593 a result of a register_mdir command performed by a
27594 system administrator.
27595
27596 Action: No operator action is required.
27597
27598
27599
27600
27601
27602
27603
27604
27605
27606
27607
27608
27609 mdc_repair_$register_mdir -476- MR12.5 10/27/92^L
27610
27611
27612 mdc_repair_.pl1
27613 mdc_repair_$register_mdir: Quota of N reported by
27614 ring 0 for DIRNAME on LVNAME. 1 assumed.
27615
27616
27617 Stream: Logged in SYSERR log.
27618
27619 Time: While system is running.
27620
27621 Meaning: The master directory DIRNAME for volume LVNAME has
27622 been found to have an invalid quota. The quota
27623 has been assumed to be 1. The message can only
27624 appear as a result of a register_mdir command
27625 performed by a system administrator.
27626
27627 Action: No operator action is required.
27628
27629
27630
27631 mdc_repair_.pl1
27632 mdc_repair_:validate_uidpaths: Master directory
27633 entry with bad uidpath deleted from LVNAME.
27634 PARTIAL-PATHNAME.
27635
27636
27637 Stream: Logged in SYSERR log.
27638
27639 Time: While system is running.
27640
27641 Meaning: The master directory control segment for LVNAME
27642 contains an entry for a mastr directory which no
27643 longer exists. The entry has been deleted and the
27644 quota is returned to the account from which it was
27645 drawn. This can happen if a master directory
27646 control segment has been lost and retreived or if
27647 a mastr directory has been lost.
27648
27649 Action: No operator action is required.
27650
27651
27652
27653
27654
27655
27656
27657
27658
27659
27660
27661
27662
27663
27664
27665
27666
27667 mdc_repair_ -477- MR12.5 10/27/92^L
27668
27669
27670 mos_memory_check.pl1
27671 mos_memory_check: EDAC error on mem X store Y.
27672
27673
27674 Stream: Warning message.
27675
27676 Time: While system is running.
27677
27678 Meaning: MOS memory polling has found that the maintenance
27679 register in the system controller shows a nonzero
27680 syndrome. The data is logged for use by HEALS or
27681 mos_edac_summary. Only the first occurrence of
27682 this error is printed online for each box.
27683
27684 Action: No operator action is required.
27685
27686
27687
27688 mos_memory_check.pl1
27689 mos_memory_check: Lock error.
27690
27691
27692 Stream: BOS Typewriter.
27693
27694 Time: While system is running.
27695
27696 Meaning: After checking the memory controllers for errors
27697 the program mos_memory check attempted to unlock
27698 the reconfiguration lock and found it unlocked.
27699 The system continues to run.
27700
27701 Action: No operator action is required.
27702
27703
27704
27705 mos_memory_check.pl1
27706 mos_memory_check: MOS polling disabled
27707
27708
27709 Stream: Logged in SYSERR log.
27710
27711 Time: While system is running.
27712
27713 Meaning: A system administrator has disabled MOS memory
27714 polling.
27715
27716 Action: No operator action is required.
27717
27718
27719
27720
27721
27722
27723
27724
27725 mos_memory_check -478- MR12.5 10/27/92^L
27726
27727
27728 mos_memory_check.pl1
27729 mos_memory_check: MOS polling time NN minutes.
27730
27731
27732 Stream: Logged in SYSERR log.
27733
27734 Time: While system is running.
27735
27736 Meaning: A system administrator has set the MOS memory
27737 polling time to NN minutes.
27738
27739 Action: No operator action is required.
27740
27741
27742
27743 disk_table_.pl1
27744 mount of LVNAME stopped
27745
27746
27747 Stream: Initializer process output.
27748
27749 Time: While system is running.
27750
27751 Meaning: The operator issued a dlv LVNAME command for a
27752 volume which was being mounted.
27753
27754 Action: No operator action is required.
27755
27756
27757
27758
27759
27760
27761
27762
27763
27764
27765
27766
27767
27768
27769
27770
27771
27772
27773
27774
27775
27776
27777
27778
27779
27780
27781
27782
27783 mount of LVNAME stopped -479- MR12.5 10/27/92^L
27784
27785
27786 disk_table_.pl1
27787 mount pack PVNAME on DRIVE
27788
27789
27790 Stream: Initializer process output.
27791
27792 Time: While system is running.
27793
27794 Meaning: This message occurs when the system is attempting
27795 to mount a logical volume and finds one or more
27796 physical volumes have not been made known via the
27797 add_vol command. If the pack is a non-demountable
27798 volume a DRIVE will only be printed if the system
27799 knows the drive on which the pack was previously
27800 mounted. If the pack is a demountable volume
27801 then a DRIVE will be printed always. If the
27802 system does not know the drive on which the pack
27803 was last mounted then it chooses a drive where
27804 the pack should be mounted and prints this
27805 message.
27806
27807 Action: Mount the pack specified. If it is not convenient
27808 to use the specified DRIVE use another. Then use
27809 the add_vol command to tell the system that the
27810 physical volume has been mounted. When all packs
27811 have been mounted and either accepted via add_vol
27812 or are on the drives where the system called for
27813 them issue a "alv LVNAME" command to accept them
27814 all at once. The logical volume will be put in
27815 use.
27816
27817
27818
27819 move_non_perm_wired_segs.pl1
27820 move_non_perm_wired_segs: mem TAG on in config
27821 deck but port off.
27822
27823
27824 Stream: BOS Typewriter Crashes system
27825
27826 Time: System Intialization.
27827
27828 Meaning: Memory controller TAG is specified ON on its MEM
27829 card but its port is disabled on the bootload
27830 CPU.
27831
27832 Action: Enable the port or set the MEM OFF and reboot.
27833
27834
27835
27836
27837
27838
27839
27840
27841 move_non_perm_wired_segs -480- MR12.5 10/27/92^L
27842
27843
27844 move_non_perm_wired_segs.pl1
27845 move_non_perm_wired_segs: mem TAG size nK in
27846 config mK on port.
27847
27848
27849 Stream: BOS Typewriter Crashes system
27850
27851 Time: System Intialization.
27852
27853 Meaning: Memory controller TAG has a size of nK in the
27854 config deck but the address assignment and port
27855 size switches specify mK.
27856
27857 Action: Fix the switches or config deck and reboot.
27858
27859
27860
27861 move_non_perm_wired_segs.pl1
27862 move_non_perm_wired_segs: no main memory
27863 configured.
27864
27865
27866 Stream: BOS Typewriter Crashes system
27867
27868 Time: System Intialization.
27869
27870 Meaning: No MEM cards were found ON in the config deck.
27871
27872 Action: Fix the config deck and reboot.
27873
27874
27875
27876
27877
27878
27879
27880
27881
27882
27883
27884
27885
27886
27887
27888
27889
27890
27891
27892
27893
27894
27895
27896
27897
27898
27899 move_non_perm_wired_segs -481- MR12.5 10/27/92^L
27900
27901
27902 mrd_util_.pl1
27903 mrd_util_$ENTRY: CALL_CODE MESSAGE in ENAME
27904
27905
27906 Stream: BOS Typewriter sounds beeper
27907
27908 Time: While system is running.
27909
27910 Meaning: A problem has been discovered in the threading of
27911 the message coordinator segment ENAME. CALL_CODE
27912 identifies the particular call that failed and
27913 MESSAGE identifies the reason for the failure.
27914 Entry identifies the entrypoint in mrd_util_ that
27915 was called. All pending messages in ENAME are
27916 discarded. Debugging information is written into
27917 ENAME and may be displayed using the
27918 dump_syscon_mseg tool. The message coordinator
27919 recovers from these errors and continues possibly
27920 with the loss of some input or output. If ENAME
27921 is mc.message some daemon output may be lost. If
27922 ENAME is anything else some input to that daemon
27923 may be lost and the operator should communicate
27924 with the daemon immediately in case this has
27925 happened. This indicates a logic error in the
27926 supervisor or CPU or memory hardware problems.
27927
27928 Action: Contact the system programming staff. Save all
27929 console and message coordinator terminal output.
27930
27931
27932
27933 mrd_util_.pl1
27934 mrd_util_$ENTRY: had to blast lock in ENAME
27935
27936
27937 Stream: BOS Typewriter sounds beeper
27938
27939 Time: While system is running.
27940
27941 Meaning: The lock in the message coordinator segment ENAME
27942 did not unlock within thirty seconds. The lock is
27943 reset forcibly and locked to the calling process.
27944 ENTRY identifies the entrypoint in mrd_util_ that
27945 was called. Debugging information is written into
27946 ENAME and may be displayed using the
27947 dump_syscon_mseg tool. Further errors may result
27948 if the process that originally locked the segment
27949 left it in an inconsistent state or if it later
27950 starts up again.
27951
27952 Action: Contact the system programming staff. Save all
27953 console and message coordinator terminal output.
27954
27955
27956
27957 mrd_util_$ENTRY -482- MR12.5 10/27/92^L
27958
27959
27960 mrd_util_.pl1
27961 mrd_util_$ENTRY: inconsistent threads in ENAME
27962
27963
27964 Stream: BOS Typewriter sounds beeper
27965
27966 Time: While system is running.
27967
27968 Meaning: While trying to add unused blocks to the free
27969 chain in the message coordinator segment ENAME an
27970 error was discovered. ENTRY identifies the
27971 entrypoint in mrd_util_ that was called.
27972 Debugging information is written into ENAME and
27973 may be displayed using the dump_syscon_mseg tool.
27974 This indicates a logic error in the supervisor or
27975 CPU or memory hardware problems.
27976
27977 Action: Contact the system programming staff. Save all
27978 console and message coordinator terminal output.
27979
27980
27981
27982 mrd_util_.pl1
27983 mrd_util_$ENTRY: killing process due to mylock
27984 error in ENAME
27985
27986
27987 Stream: BOS Typewriter Terminates user process
27988
27989 Time: While system is running.
27990
27991 Meaning: While trying to lock the message coordinator
27992 segment ENAME the lock was found to already be
27993 locked to the calling process. ENTRY identifies
27994 the entrypoint in mrd_util_ that was called.
27995 Debugging information is written into ENAME and
27996 may be displayed using the dump_syscon_mseg tool.
27997 This indicates a logic error in the supervisor or
27998 CPU or memory hardware problems.
27999
28000 Action: Contact the system programming staff. Save all
28001 console and message coordinator terminal output.
28002
28003
28004
28005
28006
28007
28008
28009
28010
28011
28012
28013
28014
28015 mrd_util_$ENTRY -483- MR12.5 10/27/92^L
28016
28017
28018 mrd_util_.pl1
28019 mrd_util_$ENTRY: reset bad lock in ENAME
28020
28021
28022 Stream: BOS Typewriter sounds beeper
28023
28024 Time: While system is running.
28025
28026 Meaning: The message coordinator segment ENAME was locked
28027 to a nonexistent process. The lock is reset and
28028 locked to the calling process. ENTRY identifies
28029 the entrypoint in mrd_util_ that was called.
28030 Debugging information is written into ENAME and
28031 may be displayed using the dump_syscon_mseg tool.
28032 Further errors may be reported if ENAME was in an
28033 inconsistent state.
28034
28035 Action: Contact the system programming staff. Save all
28036 console and message coordinator terminal output.
28037
28038
28039
28040 syserr_real.pl1
28041 Multics not in operation; control process:
28042 PERSON.PROJ.
28043
28044
28045 Stream: BOS Typewriter Crashes system
28046
28047 Time: While system is running.
28048
28049 Meaning: This message is always preceded by an explanation
28050 of the error which crashed the system.
28051
28052 Action: Follow normal recovery procedures.
28053
28054
28055
28056
28057
28058
28059
28060
28061
28062
28063
28064
28065
28066
28067
28068
28069
28070
28071
28072
28073 Multics not in operation; -484- MR12.5 10/27/92^L
28074
28075
28076 system_startup_.pl1
28077 Multics SYSID: DATE TIME
28078
28079
28080 Stream: BOS Typewriter.
28081
28082 Time: System Intialization.
28083
28084 Meaning: This is the first message that will be typed when
28085 the system is started up. It indicates that the
28086 Initializer process is ready to go. The system ID
28087 on the tape is SYSID.
28088
28089 Action: Check the date and time to ensure both are
28090 correct. If the clock reading is wrong shut down
28091 and correct the clock.
28092
28093
28094
28095 disk_rebuild_caller.pl1
28096 New starting parameters no partitions defined:
28097
28098
28099 Stream: Initializer process output.
28100
28101 Time: In response to an operator command.
28102
28103 Meaning: This message requests the input of new disk
28104 parameters.
28105
28106 Action: Input the new disk parameters. Use the "end"
28107 request when done.
28108
28109
28110
28111 syserr_real.pl1
28112 Now terminating user process: PERSON.PROJ.
28113
28114
28115 Stream: BOS Typewriter.
28116
28117 Time: While system is running.
28118
28119 Meaning: This line is always preceded by an explanation of
28120 the error which required the terminaation of the
28121 user process PERSON.PROJ.
28122
28123 Action: No operator action is required.
28124
28125
28126
28127
28128
28129
28130
28131 Now terminating user proce -485- MR12.5 10/27/92^L
28132
28133
28134 ocdcm_.pl1
28135 ocdcm_ bump_io_to_mc: Console recovery failure.
28136
28137
28138 Stream: BOS Typewriter Crashes system
28139
28140 Time: While system is running.
28141
28142 Meaning: The software detected Message Coordinator failure
28143 while the Message Coordinator was being used in
28144 place of a functioning console. Since the CCRF
28145 parameter was specified the system crashed.
28146
28147 Action: Contact the system programming staff. Contact the
28148 system administrator.
28149
28150
28151
28152 ocdcm_.pl1
28153 ocdcm_ bump_io_to_mc: Message Coordinator
28154 failure.
28155
28156
28157 Stream: Logged in SYSERR log.
28158
28159 Time: While system is running.
28160
28161 Meaning: The Message Coordinator is no longer able to
28162 handle console traffic.
28163
28164 Action: Attempt to get an active console online as soon as
28165 possible and reset the Message Coordinator.
28166
28167
28168
28169
28170
28171
28172
28173
28174
28175
28176
28177
28178
28179
28180
28181
28182
28183
28184
28185
28186
28187
28188
28189 ocdcm_ bump_io_to_mc -486- MR12.5 10/27/92^L
28190
28191
28192 ocdcm_.pl1
28193 ocdcm_ console_recovery: Console failed
28194 assignment of alternate OPCx failed.
28195
28196
28197 Stream: Logged in SYSERR log.
28198
28199 Time: While system is running.
28200
28201 Meaning: The console software detected a failure of the
28202 bootload console and found an alternate to
28203 utilize. However when it tried to attach the
28204 alternate it too was found to be inoperative. The
28205 search continues for a usable console.
28206
28207 Action: Attempt to determine why the alternate console
28208 failed to come online. If it can be repaired
28209 configure it with the set_system_console command
28210 from a highly priviliged process.
28211
28212
28213
28214 ocdcm_.pl1
28215 ocdcm_ console_recovery: Console inoperative
28216 alternate OPCx assigned.
28217
28218
28219 Stream: Logged in SYSERR log.
28220
28221 Time: While system is running.
28222
28223 Meaning: The software has detected a bootload console
28224 failure and has assigned the specifed alternate to
28225 take over. The inoperative console is flagged as
28226 such.
28227
28228 Action: Contact the system programming staff.
28229
28230
28231
28232
28233
28234
28235
28236
28237
28238
28239
28240
28241
28242
28243
28244
28245
28246
28247 ocdcm_ console_recovery -487- MR12.5 10/27/92^L
28248
28249
28250 ocdcm_.pl1
28251 ocdcm_ console_recovery: Console inoperative
28252 no alternates available.
28253
28254
28255 Stream: Logged in SYSERR log.
28256
28257 Time: While system is running.
28258
28259 Meaning: The software dected failure of the bootload
28260 console but no alternates are configured. It
28261 will direct subsequent console traffic to the
28262 Message Coordinator.
28263
28264 Action: Attempt to get a running console online via the
28265 set_system_console command as soon as possible.
28266
28267
28268
28269 ocdcm_.pl1
28270 ocdcm_ console_recovery: Console inoperative
28271 no alternates no MC.
28272
28273
28274 Stream: Logged in SYSERR log.
28275
28276 Time: While system is running.
28277
28278 Meaning: The software detected failure of the bootload
28279 console but no alternates are configured and the
28280 Message Coordinator is not functioning. All
28281 subsequent console traffic will be sent to the
28282 syserr log.
28283
28284 Action: Attempt to get a running console online via the
28285 set_system_console command as soon as possible.
28286
28287
28288
28289
28290
28291
28292
28293
28294
28295
28296
28297
28298
28299
28300
28301
28302
28303
28304
28305 ocdcm_ console_recovery -488- MR12.5 10/27/92^L
28306
28307
28308 ocdcm_.pl1
28309 ocdcm_ console_recovery: Console recovery
28310 failure.
28311
28312
28313 Stream: BOS Typewriter Crashes system
28314
28315 Time: While system is running.
28316
28317 Meaning: The software detected console failure and was
28318 unable to continue because the CCRF parameter was
28319 specified. The system crashed.
28320
28321 Action: Contact the system programming staff. Contact the
28322 system administrator.
28323
28324
28325
28326 ocdcm_.pl1
28327 ocdcm_ esd_reset: No active consoles
28328 configured.
28329
28330
28331 Stream: Logged in SYSERR log.
28332
28333 Time: While system is running.
28334
28335 Meaning: During ESD there were no consoles in service. ESD
28336 messages will be sent to the syserr log.
28337
28338 Action: Contact the system programming staff.
28339
28340
28341
28342 ocdcm_.pl1
28343 ocdcm_ init_all_consoles: Assigned console OPCx
28344 as TYPE device.
28345
28346
28347 Stream: $announce
28348
28349 Time: System Intialization.
28350
28351 Meaning: This message appears as the system configures
28352 consoles found in the config file. This message
28353 will only appear if the CLST parameter has been
28354 specified on the PARM card. Values for TYPE are
28355 "bootload" "alternate" "I/O" "inoperative" and
28356 "off".
28357
28358 Action: No operator action is required.
28359
28360
28361
28362
28363 ocdcm_ init_all_consoles -489- MR12.5 10/27/92^L
28364
28365
28366 ocdcm_.pl1
28367 ocdcm_ init_all_consoles: Changing state of
28368 OPCx to alt.
28369
28370
28371 Stream: BOS Typewriter sounds beeper
28372
28373 Time: System Intialization.
28374
28375 Meaning: During console initialization more than one
28376 console was found to have a state of "on". Since
28377 only one bootload console is allowed the software
28378 reconfigures additional "on" consoles as
28379 alternates.
28380
28381 Action: $config
28382
28383
28384
28385 ocdcm_.pl1
28386 ocdcm_ init_all_consoles: Console channel
28387 assignment failed.
28388
28389
28390 Stream: BOS Typewriter Crashes system
28391
28392 Time: While system is running.
28393
28394 Meaning: Attachment of the specified bootload console
28395 failed during initialization.
28396
28397 Action: This is most likely a hardware failure of the
28398 console channel adapter.
28399
28400
28401
28402 ocdcm_.pl1
28403 ocdcm_ init_all_consoles: Illegal console name
28404 NAME specified. It will be ignored.
28405
28406
28407 Stream: BOS Typewriter sounds beeper
28408
28409 Time: System Intialization.
28410
28411 Meaning: An illegal console name was found. Console names
28412 must be values of "opca" through "opcz".
28413
28414 Action: $config
28415
28416
28417
28418
28419
28420
28421 ocdcm_ init_all_consoles -490- MR12.5 10/27/92^L
28422
28423
28424 ocdcm_.pl1
28425 ocdcm_ init_all_consoles: Invalid channel
28426 specified for OPCx.
28427
28428
28429 Stream: BOS Typewriter Crashes system
28430
28431 Time: System Intialization.
28432
28433 Meaning: The console channel as specified in the config
28434 file for the specified device is illegal.
28435
28436 Action: $config
28437
28438
28439
28440 ocdcm_.pl1
28441 ocdcm_ init_all_consoles: Invalid state of
28442 STATE for console OPCx. ocdcm_
28443 init_all_consoles: This console will not be
28444 configured.
28445
28446
28447 Stream: BOS Typewriter sounds beeper
28448
28449 Time: System Intialization.
28450
28451 Meaning: An unrecognizable state was found for the
28452 specified console. That console will not be
28453 configured. Only valid states are "on" "alt"
28454 "io" "inop" and "off".
28455
28456 Action: $config
28457
28458
28459
28460 ocdcm_.pl1
28461 ocdcm_ init_all_consoles: Maximum console count
28462 exceeded. ocdcm_ init_all_consoles: Additional
28463 consoles will not be configured.
28464
28465
28466 Stream: BOS Typewriter sounds beeper
28467
28468 Time: System Intialization.
28469
28470 Meaning: Too many consoles have been specified in the
28471 config file. Only the maximum number allowable
28472 will be configured.
28473
28474 Action: $config
28475
28476
28477
28478
28479 ocdcm_ init_all_consoles -491- MR12.5 10/27/92^L
28480
28481
28482 ocdcm_.pl1
28483 ocdcm_ init_all_consoles: Missing prph opc
28484 card.
28485
28486
28487 Stream: BOS Typewriter Crashes system
28488
28489 Time: System Intialization.
28490
28491 Meaning: At least one PRPH OPCx card must be in the config
28492 file.
28493
28494 Action: $config
28495
28496
28497
28498 ocdcm_.pl1
28499 ocdcm_ init_all_consoles: No active console
28500 configured.
28501
28502
28503 Stream: BOS Typewriter Crashes system
28504
28505 Time: System Intialization.
28506
28507 Meaning: None of the consoles specified in the config file
28508 has a state of "on".
28509
28510 Action: $config
28511
28512
28513
28514 ocdcm_.pl1
28515 ocdcm_ init_all_consoles: Unable to determine
28516 absolute memory address of
28517 oc_data.
28518
28519
28520 Stream: BOS Typewriter Crashes system
28521
28522 Time: While system is running.
28523
28524 Meaning: The absloute memory address of oc_data could not
28525 be determined during console initialization.
28526
28527 Action: This is a very serious error. Ensure that your
28528 MST is good and then consider hardware.
28529
28530
28531
28532
28533
28534
28535
28536
28537 ocdcm_ init_all_consoles -492- MR12.5 10/27/92^L
28538
28539
28540 ocdcm_.pl1
28541 ocdcm_ init_all_consoles: Unknown model NNNN
28542 specified for OPCx.
28543 It will not be configured.
28544
28545
28546 Stream: BOS Typewriter sounds beeper
28547
28548 Time: System Intialization.
28549
28550 Meaning: The console model number specified in the config
28551 file is not supported by this software and will
28552 not be configured.
28553
28554 Action: $config
28555
28556
28557
28558 ocdcm_.pl1
28559 ocdcm_ interrupt_handler: System Fault.
28560
28561
28562 Stream: Logged in SYSERR log.
28563
28564 Time: While system is running.
28565
28566 Meaning: A system fault interrupt was received from the
28567 IOM. The fault is logged and ignored.
28568
28569 Action: Contact the system programming staff.
28570
28571
28572
28573 ocdcm_.pl1
28574 ocdcm_ lock_oc_data: Lock wait timer expired.
28575
28576
28577 Stream: BOS Typewriter Crashes system
28578
28579 Time: While system is running.
28580
28581 Meaning: A process waiting on the lock was not able to get
28582 the lock before the wait timer expired. This
28583 timer is calculated as the maximum time that it
28584 should take a READ I/O to complete times the
28585 number of CPUs specified in the config file. Any
28586 process waiting on the lock should never have to
28587 wait more than that amount of time for the lock to
28588 become available without there being a serious
28589 problem with the hardcore process holding the
28590 lock.
28591
28592 Action: Contact the system programming staff.
28593
28594
28595 ocdcm_ lock_oc_data -493- MR12.5 10/27/92^L
28596
28597
28598 ocdcm_.pl1
28599 ocdcm_ lock_oc_data: Mylock error.
28600
28601
28602 Stream: BOS Typewriter Crashes system
28603
28604 Time: While system is running.
28605
28606 Meaning: The offending process found its own process_id in
28607 the lock.
28608
28609 Action: Contact the system programming staff.
28610
28611
28612
28613 ocdcm_.pl1
28614 ocdcm_ log_console_error: I/O timeout error
28615 on OPCx; status = SSSSSS
28616 oc_data flags: FLAGS
28617 oc_entry flags: FLAGS
28618 console_io flags: FLAGS
28619
28620
28621 Stream: Logged in SYSERR log.
28622
28623 Time: While system is running.
28624
28625 Meaning: An I/O error occurred. The status is the returned
28626 IOM status for the I/O in question and the flags
28627 denote the state of the oc_data the console and
28628 the I/O respectively at the time of the error.
28629 The flag values are interpreted.
28630
28631 Action: Too many of these errors will result in the
28632 invocation of console recovery. Have the console
28633 fixed.
28634
28635
28636
28637 ocdcm_.pl1
28638 ocdcm_ reconfigure: Assigned OPCx as an
28639 alternate console for PERSON.PROJ.T.
28640
28641
28642 Stream: BOS Typewriter sounds beeper
28643
28644 Time: While system is running.
28645
28646 Meaning: The specified process has configured the specified
28647 console as an alternate.
28648
28649 Action: No operator action is required.
28650
28651
28652
28653 ocdcm_ reconfigure -494- MR12.5 10/27/92^L
28654
28655
28656 ocdcm_.pl1
28657 ocdcm_ reconfigure: Assigned OPCx as the
28658 bootload console for PERSON.PROJ.T.
28659
28660
28661 Stream: BOS Typewriter sounds beeper
28662
28663 Time: While system is running.
28664
28665 Meaning: The specified process has configured the specified
28666 console as the bootload console. The bootload
28667 console at the time of the reconfiguration is
28668 reconfigured as an alternate device.
28669
28670 Action: No operator action is required.
28671
28672
28673
28674 ocdcm_.pl1
28675 ocdcm_ reconfigure: Bootload console
28676 deconfigured with CCRF set.
28677
28678
28679 Stream: BOS Typewriter Crashes system
28680
28681 Time: During console reconfiguration.
28682
28683 Meaning: The bootload console was deconfigured by use of
28684 the set_system_console command and the site had
28685 specified the CCRF parameter in the config file.
28686
28687 Action: Follow normal recovery procedures.
28688
28689
28690
28691 ocdcm_.pl1
28692 ocdcm_ reconfigure: Consigned OPCx as an I/O
28693 device for PERSON.PROJ.T.
28694
28695
28696 Stream: BOS Typewriter sounds beeper
28697
28698 Time: While system is running.
28699
28700 Meaning: The specified process has configured the specified
28701 console as an I/O device.
28702
28703 Action: No operator action is required.
28704
28705
28706
28707
28708
28709
28710
28711 ocdcm_ reconfigure -495- MR12.5 10/27/92^L
28712
28713
28714 ocdcm_.pl1
28715 ocdcm_ reconfigure: Marked OPCx as an
28716 inoperative device for PERSON.PROJ.T.
28717
28718
28719 Stream: BOS Typewriter sounds beeper
28720
28721 Time: While system is running.
28722
28723 Meaning: The specified process has configured the specified
28724 console as an inoperative device.
28725
28726 Action: No operator action is required.
28727
28728
28729
28730 ocdcm_.pl1
28731 ocdcm_ reconfigure: MCA input through OPCx
28732 disabled by PERSON.PROJ.T.
28733
28734
28735 Stream: Logged in SYSERR log.
28736
28737 Time: While system is running.
28738
28739 Meaning: The input to the MCA Maint. Channel Adapter in
28740 the IMU Interrupt Multiplexer Unit from special
28741 keyboard sequences has been LOCKed disabled.
28742 Input to the MCA can now only come from the
28743 on-line Multics controlled channel 03 interface.
28744
28745 Action: No operator action is required.
28746
28747
28748
28749 ocdcm_.pl1
28750 ocdcm_ reconfigure: MCAnn input through OPCx
28751 enabled by PERSON.PROJ.T.
28752
28753
28754 Stream: Logged in SYSERR log.
28755
28756 Time: While system is running.
28757
28758 Meaning: The input to MCAnn via special console keyboard
28759 sequences has been enabled UNLOCKed.
28760
28761 Action: No operator action is required.
28762
28763
28764
28765
28766
28767
28768
28769 ocdcm_ reconfigure -496- MR12.5 10/27/92^L
28770
28771
28772 ocdcm_.pl1
28773 ocdcm_ reconfigure: Timeout executing MCA LOCK
28774 on OPCx for PERSON.PROJ.T.
28775
28776
28777 Stream: Logged in SYSERR log.
28778
28779 Time: While system is running.
28780
28781 Meaning: The I/O to LOCK the MCA interface through OPCx did
28782 not complete within a given time.
28783
28784 Action: This is most likely a hardware failure of the
28785 console channel adapter or the IMU central.
28786
28787
28788
28789 ocdcm_.pl1
28790 ocdcm_ reconfigure: Timeout executing MCAnn
28791 UNLOCK on OPCx for PERSON.PROJ.T.
28792
28793
28794 Stream: Logged in SYSERR log.
28795
28796 Time: While system is running.
28797
28798 Meaning: The I/O to UNLOCK the MCAnn interface through
28799 OPCx did not complete within a given time.
28800
28801 Action: This is most likely a hardware failure of the
28802 console channel adapter or the IMU central.
28803
28804
28805
28806 ocdcm_.pl1
28807 ocdcm_ reset_console: Reset bootload console
28808 for PERSON.PROJ.T.
28809
28810
28811 Stream: BOS Typewriter sounds beeper
28812
28813 Time: While system is running.
28814
28815 Meaning: The bootload console has been reset by the
28816 specified process.
28817
28818 Action: No operator action is required.
28819
28820
28821
28822
28823
28824
28825
28826
28827 ocdcm_ reset_console -497- MR12.5 10/27/92^L
28828
28829
28830 ocdcm_.pl1
28831 ocdcm_ unlock_oc_data: Lock not mine.
28832
28833
28834 Stream: BOS Typewriter Crashes system
28835
28836 Time: While system is running.
28837
28838 Meaning: A process attempting to unlock oc_data found a
28839 non-zero lock that was not its own.
28840
28841 Action: Contact the system programming staff.
28842
28843
28844
28845 on_line_salvager.pl1
28846 on_line_salvager: cannot get activation info on
28847 PPPPP ERRORMESSAGE
28848
28849
28850 Stream: BOS Typewriter.
28851
28852 Time: While system is running.
28853
28854 Meaning: The on line salvager could not determine the
28855 length of a directory to be salvaged. A truncated
28856 copy will be made in >dumps.
28857
28858 Action: Contact the system programming staff.
28859
28860
28861
28862 on_line_salvager.pl1
28863 on_line_salvager: error from sum on PPPPP
28864 ERRORMESSAGE
28865
28866
28867 Stream: BOS Typewriter Crashes system
28868
28869 Time: While system is running.
28870
28871 Meaning: The on line salvager could not access the branch
28872 for a sdirectory to be salvaged. This indicates a
28873 logic error in the supervisor or CPU or memory
28874 hardware problems.
28875
28876 Action: Contact the system programming staff. Follow
28877 normal recovery procedures.
28878
28879
28880
28881
28882
28883
28884
28885 on_line_salvager -498- MR12.5 10/27/92^L
28886
28887
28888 on_line_salvager.pl1
28889 on_line_salvager: Getting pathname of PPPPP
28890
28891
28892 Stream: BOS Typewriter Crashes system
28893
28894 Time: While system is running.
28895
28896 Meaning: The on line salvager cannot obtain the pathname of
28897 a directory to be salvaged. This indicates a
28898 logic error in the supervisor or CPU or memory
28899 hardware problems.
28900
28901 Action: Take a dump. Contact the system programming
28902 staff. Follow normal recovery procedures.
28903
28904
28905
28906 on_line_salvager.pl1
28907 on_line_salvager: lock error ERROMESSAGE
28908
28909
28910 Stream: BOS Typewriter Crashes system
28911
28912 Time: While system is running.
28913
28914 Meaning: The on line salvager could not lock its data base.
28915 This indicates a logic error in the supervisor or
28916 CPU or memory hardware problems.
28917
28918 Action: Contact the system programming staff. Follow
28919 normal recovery procedures. Be sure that a dump
28920 is taken.
28921
28922
28923
28924 mc_tty_.pl1
28925 OPER:
28926
28927
28928 Stream: Initializer terminal.
28929
28930 Time: While system is running.
28931
28932 Meaning: This message is typed if the operator enters a
28933 blank line on a message coordinator terminal. It
28934 indicates that input is expected on the terminal
28935 and that output will be inhibited for 30 seconds.
28936
28937 Action: Type a system control command.
28938
28939
28940
28941
28942
28943 OPER -499- MR12.5 10/27/92^L
28944
28945
28946 operator_mc_cmds_.pl1
28947 operator_mc_cmds_: accept: CHANNEL set to
28948 "full".
28949
28950
28951 Stream: $as1
28952
28953 Time: In response to an operator accept command.
28954
28955 Meaning: CHANNEL is already in use and authorization
28956 request has not changed from it's current state.
28957
28958 Action: Enter a corrected command line.
28959
28960
28961
28962 operator_mc_cmds_.pl1
28963 operator_mc_cmds_: accept: channel not available
28964
28965
28966 Stream: $as1
28967
28968 Time: In response to an operator accept command.
28969
28970 Meaning: Channel cannot be used as a message coordinator
28971 channel.
28972
28973 Action: Enter a corrected command line.
28974
28975
28976
28977 operator_mc_cmds_.pl1
28978 operator_mc_cmds_: accept: channel not defined
28979 in cdt.
28980
28981
28982 Stream: $as1
28983
28984 Time: In response to an operator accept command.
28985
28986 Meaning: Channel is not found in the system cdt and
28987 therefore cannot be used.
28988
28989 Action: Enter a corrected command line.
28990
28991
28992
28993
28994
28995
28996
28997
28998
28999
29000
29001 operator_mc_cmds_ -500- MR12.5 10/27/92^L
29002
29003
29004 operator_mc_cmds_.pl1
29005 operator_mc_cmds_: accept: error: unknown
29006 privilege code
29007
29008
29009 Stream: $as1
29010
29011 Time: In response to an operator accept command.
29012
29013 Meaning: The operator has typed accept CHANNEL PRIVILEGE
29014 but PRIVILEGE is not a known privilege code.
29015
29016 Action: Enter a corrected command line.
29017
29018
29019
29020 operator_mc_cmds_.pl1
29021 operator_mc_cmds_: accept: ERROR_TABLE_MESSAGE
29022 accept unsuccessful.
29023
29024
29025 Stream: $as1
29026
29027 Time: In response to an operator accept command.
29028
29029 Meaning: The error was returned from mc_commands_$new_tty
29030 causing the accept to abort.
29031
29032 Action: Enter a corrected command line.
29033
29034
29035
29036 operator_mc_cmds_.pl1
29037 operator_mc_cmds_: accept: ERROR_TABLE_MESSAGE
29038 Channel CHANNEL is not in Message Coordinator
29039 service.
29040
29041
29042 Stream: $as1
29043
29044 Time: In response to an operator accept command.
29045
29046 Meaning: CHANNEL cannot be accepted as a message
29047 coordinator terminal.
29048
29049 Action: Enter a corrected command line.
29050
29051
29052
29053
29054
29055
29056
29057
29058
29059 operator_mc_cmds_ -501- MR12.5 10/27/92^L
29060
29061
29062 operator_mc_cmds_.pl1
29063 operator_mc_cmds_: accept: ERROR_TABLE_MESSAGE
29064 Failed to accept CHANNEL.
29065
29066
29067 Stream: $as1
29068
29069 Time: In response to an operator accept command.
29070
29071 Meaning: The operator has issued an accept CHANNEL command
29072 but CHANNEL cannot be accepted.
29073
29074 Action: Enter a corrected command line.
29075
29076
29077
29078 operator_mc_cmds_.pl1
29079 operator_mc_cmds_: accept: ERROR_TABLE_MESSAGE
29080 Failed to reset restriction.
29081
29082
29083 Stream: $as1
29084
29085 Time: In response to an operator accept command.
29086
29087 Meaning: Failed to reset the reply restriction.
29088
29089 Action: Enter a corrected command line.
29090
29091
29092
29093 operator_mc_cmds_.pl1
29094 operator_mc_cmds_: accept: ERROR_TABLE_MESSAGE
29095 Failed to set broadcast list to BROADCAST_LIST.
29096
29097
29098 Stream: $as1
29099
29100 Time: In response to an operator accept command.
29101
29102 Meaning: Failed to set the broadcast list BROADCAST_LIST.
29103
29104 Action: Enter a corrected command line.
29105
29106
29107
29108
29109
29110
29111
29112
29113
29114
29115
29116
29117 operator_mc_cmds_ -502- MR12.5 10/27/92^L
29118
29119
29120 operator_mc_cmds_.pl1
29121 operator_mc_cmds_: accept: ERROR_TABLE_MESSAGE
29122 Failed to set restriction to RESTRICTION.
29123
29124
29125 Stream: $as1
29126
29127 Time: In response to an operator accept command.
29128
29129 Meaning: Failed to set the reply restriction.
29130
29131 Action: Enter a corrected command line.
29132
29133
29134
29135 operator_mc_cmds_.pl1
29136 operator_mc_cmds_: accept: ERROR_TABLE_MESSAGE
29137 This name is reserved for the system console.
29138
29139
29140 Stream: $as1
29141
29142 Time: In response to an operator accept command.
29143
29144 Meaning: Attempt to accept identifier "otw_" which is THE
29145 identifier for the master console which is
29146 automatically accepted on bootload.
29147
29148 Action: Enter a corrected command line.
29149
29150
29151
29152 operator_mc_cmds_.pl1
29153 operator_mc_cmds_: accept: ERROR_TABLE_MESSAGE
29154 Usage: accept channel_id authority target
29155 broadcast_list
29156
29157
29158 Stream: $as1
29159
29160 Time: In response to an operator accept command.
29161
29162 Meaning: The operator has issued an accept command without
29163 any arguments.
29164
29165 Action: Enter a corrected command line.
29166
29167
29168
29169
29170
29171
29172
29173
29174
29175 operator_mc_cmds_ -503- MR12.5 10/27/92^L
29176
29177
29178 operator_mc_cmds_.pl1
29179 operator_mc_cmds_: accept: Ioname already
29180 attached and active. accept unsuccessful.
29181
29182
29183 Stream: $as1
29184
29185 Time: In response to an operator accept command.
29186
29187 Meaning: The error was returned from mc_commands_$new_tty
29188 causing the accept to abort.
29189
29190 Action: Enter a corrected command line.
29191
29192
29193
29194 operator_mc_cmds_.pl1
29195 operator_mc_cmds_: accept: Ioname not found.
29196 accept unsuccessful.
29197
29198
29199 Stream: $as1
29200
29201 Time: In response to an operator accept command.
29202
29203 Meaning: The error was returned from mc_commands_$new_tty
29204 causing the accept to abort. Channel not found in
29205 the cdt or pre-accepted as a virtual channel.
29206
29207 Action: Enter a corrected command line.
29208
29209
29210
29211 operator_mc_cmds_.pl1
29212 operator_mc_cmds_: accept_vchn:
29213 ERROR_TABLE_MESSAGE Failed to accept VCHANNEL
29214
29215
29216 Stream: $as1
29217
29218 Time: In response to an operator accept_vchn command.
29219
29220 Meaning: Unable to pre-accept VCHANNEL as a virtual channel
29221 identifier.
29222
29223 Action: Enter a corrected command line.
29224
29225
29226
29227
29228
29229
29230
29231
29232
29233 operator_mc_cmds_ -504- MR12.5 10/27/92^L
29234
29235
29236 operator_mc_cmds_.pl1
29237 operator_mc_cmds_: accept_vchn:
29238 ERROR_TABLE_MESSAGE Failed to reset restriction.
29239
29240
29241 Stream: $as1
29242
29243 Time: In response to an operator accept command.
29244
29245 Meaning: Failed to reset the reply restriction.
29246
29247 Action: Enter a corrected command line.
29248
29249
29250
29251 operator_mc_cmds_.pl1
29252 operator_mc_cmds_: accept_vchn:
29253 ERROR_TABLE_MESSAGE Failed to set broadcast list
29254 to BROADCAST_LIST.
29255
29256
29257 Stream: $as1
29258
29259 Time: In response to an operator accept command.
29260
29261 Meaning: Failed to set the broadcast list for
29262 BROADCAST_LIST.
29263
29264 Action: Enter a corrected command line.
29265
29266
29267
29268 operator_mc_cmds_.pl1
29269 operator_mc_cmds_: accept_vchn:
29270 ERROR_TABLE_MESSAGE Failed to set restriction to
29271 REPLY_TARGET
29272
29273
29274 Stream: $as1
29275
29276 Time: In response to an operator accept command.
29277
29278 Meaning: Failed to set the reply restriction for
29279 REPLY_TARGET.
29280
29281 Action: Enter a corrected command line.
29282
29283
29284
29285
29286
29287
29288
29289
29290
29291 operator_mc_cmds_ -505- MR12.5 10/27/92^L
29292
29293
29294 operator_mc_cmds_.pl1
29295 operator_mc_cmds_: accept_vchn:
29296 ERROR_TABLE_MESSAGE Usage: accept_vchn
29297 channel_id -auth authority -target reply_target
29298 -bc_list input_broadcast_list
29299
29300
29301 Stream: $as1
29302
29303 Time: In response to an operator accept_vchn command.
29304
29305 Meaning: Incorrect number of arguments supplied.
29306
29307 Action: Enter a corrected command line.
29308
29309
29310
29311 operator_mc_cmds_.pl1
29312 operator_mc_cmds_: accept_vchn: Incorrect IO
29313 channel specification. This name is reserved for
29314 the system console.
29315
29316
29317 Stream: $as1
29318
29319 Time: In response to an operator accept_vchn command.
29320
29321 Meaning: The specified virtual channel name given was
29322 "otw_". This identifier cannot be used as it
29323 identifies the system console.
29324
29325 Action: Enter a corrected command line.
29326
29327
29328
29329 operator_mc_cmds_.pl1
29330 operator_mc_cmds_: accept_vchn: Incorrect IO
29331 channel specification. DOT Virtual channel names
29332 may not contain a DOT
29333
29334
29335 Stream: $as1
29336
29337 Time: In response to an operator accept_vchn command.
29338
29339 Meaning: The DOT "." character cannot be used in the
29340 virtual channel specifier.
29341
29342 Action: Enter a corrected command line.
29343
29344
29345
29346
29347
29348
29349 operator_mc_cmds_ -506- MR12.5 10/27/92^L
29350
29351
29352 operator_mc_cmds_.pl1
29353 operator_mc_cmds_: accept_vchn: Invalid argument
29354 -auth may be followed by one of the following:
29355 full none reply daemon query
29356
29357
29358 Stream: $as1
29359
29360 Time: In response to an operator accept_vchn command.
29361
29362 Meaning: An incorrect argument to the -auth control
29363 argument was supplied.
29364
29365 Action: Enter a corrected command line.
29366
29367
29368
29369 operator_mc_cmds_.pl1
29370 operator_mc_cmds_: accept_vchn: Invalid argument
29371 Bad broadcast list: BROADCAST_LIST
29372
29373
29374 Stream: $as1
29375
29376 Time: In response to an operator accept_vchn command.
29377
29378 Meaning: Incorrect argument supplied to the -bc_list
29379 control argument.
29380
29381 Action: Enter a corrected command line.
29382
29383
29384
29385 operator_mc_cmds_.pl1
29386 operator_mc_cmds_: accept_vchn: Invalid argument
29387 Bad reply target: TARGET
29388
29389
29390 Stream: $as1
29391
29392 Time: In response to an operator accept_vchn command.
29393
29394 Meaning: An incorrect argument to the -reply control
29395 argument was supplied.
29396
29397 Action: Enter a corrected command line.
29398
29399
29400
29401
29402
29403
29404
29405
29406
29407 operator_mc_cmds_ -507- MR12.5 10/27/92^L
29408
29409
29410 operator_mc_cmds_.pl1
29411 operator_mc_cmds_: accept_vchn: Ioname already
29412 attached and active. VCHANNEL set to full.
29413
29414
29415 Stream: $as1
29416
29417 Time: In response to an operator accept_vchn command.
29418
29419 Meaning: VCHANNEL already active and authorization request
29420 is same.
29421
29422 Action: Enter a corrected command line.
29423
29424
29425
29426 operator_mc_cmds_.pl1
29427 operator_mc_cmds_: accept_vchn: Specified
29428 control argument is not accpeted Argument not
29429 accepted: ARGUMENT
29430
29431
29432 Stream: $as1
29433
29434 Time: In response to an operator accept_vchn command.
29435
29436 Meaning: An incorrect control argument was supplied to the
29437 accept_vchn request.
29438
29439 Action: Enter a corrected command line.
29440
29441
29442
29443 operator_mc_cmds_.pl1
29444 operator_mc_cmds_: COMMAND: ERROR_TABLE_MESSAGE
29445 SYSDIR>answer_table
29446
29447
29448 Stream: $as1
29449
29450 Time: In response to an operator command COMMAND.
29451
29452 Meaning: The system was unable to access the answer_table
29453 in SYSDIR.
29454
29455 Action: Contact the system programming staff.
29456
29457
29458
29459
29460
29461
29462
29463
29464
29465 operator_mc_cmds_ -508- MR12.5 10/27/92^L
29466
29467
29468 operator_mc_cmds_.pl1
29469 operator_mc_cmds_: COMMAND: ERROR_TABLE_MESSAGE
29470 SYSDIR>cdt
29471
29472
29473 Stream: $as1
29474
29475 Time: In response to an operator command COMMAND.
29476
29477 Meaning: The system was unable to access the cdt in SYSDIR.
29478
29479 Action: Contact the system programming staff.
29480
29481
29482
29483 operator_mc_cmds_.pl1
29484 operator_mc_cmds_: COMMAND: ERROR_TABLE_MESSAGE
29485 SYSDIR>installation_parms
29486
29487
29488 Stream: $as1
29489
29490 Time: In response to an operator command COMMAND.
29491
29492 Meaning: The system was unable to access the
29493 installation_parms in SYSDIR.
29494
29495 Action: Contact the system programming staff.
29496
29497
29498
29499 operator_mc_cmds_.pl1
29500 operator_mc_cmds_: COMMAND: ERROR_TABLE_MESSAGE
29501 SYSDIR>whotab
29502
29503
29504 Stream: $as1
29505
29506 Time: In response to an operator command COMMAND.
29507
29508 Meaning: The system was unable to access the whotab in
29509 SYSDIR.
29510
29511 Action: Contact the system programming staff.
29512
29513
29514
29515
29516
29517
29518
29519
29520
29521
29522
29523 operator_mc_cmds_ -509- MR12.5 10/27/92^L
29524
29525
29526 operator_mc_cmds_.pl1
29527 operator_mc_cmds_: COMMAND: ERROR_TABLE_MESSAGE
29528 Incorrect number of arguments.
29529
29530
29531 Stream: $as1
29532
29533 Time: In response to an operator command COMMAND.
29534
29535 Meaning: Insufficient number of arguments supplied with the
29536 command.
29537
29538 Action: Enter a corrected command line.
29539
29540
29541
29542 operator_mc_cmds_.pl1
29543 operator_mc_cmds_: COMMAND: ERROR_TABLE_MESSAGE
29544 removing user no proc on channel CHANNEL
29545
29546
29547 Stream: $as1
29548
29549 Time: In response to an operator command.
29550
29551 Meaning: An error described by ERROR_TABLE_MESSAGE occured
29552 while attempting the operator command COMMAND.
29553
29554 Action: Contact the system programming staff.
29555
29556
29557
29558 operator_mc_cmds_.pl1
29559 operator_mc_cmds_: COMMAND: ERROR_TABLE_MESSAGE
29560 trying to access SYSDIR>mc_anstbl
29561
29562
29563 Stream: $as1
29564
29565 Time: In response to an operator command COMMAND.
29566
29567 Meaning: The system was not able to access the mc_anstbl in
29568 SYSDIR.
29569
29570 Action: Contact the system programming staff.
29571
29572
29573
29574
29575
29576
29577
29578
29579
29580
29581 operator_mc_cmds_ -510- MR12.5 10/27/92^L
29582
29583
29584 operator_mc_cmds_.pl1
29585 operator_mc_cmds_: define: Action not performed.
29586 define unsuccessful.
29587
29588
29589 Stream: $as1
29590
29591 Time: In response to an operator define command.
29592
29593 Meaning: An error was returned from mc_commands_$define
29594 causing the define to abort. Target channel found
29595 requiring an accept in mc_anstbl.
29596
29597 Action: Enter a corrected command line.
29598
29599
29600
29601 operator_mc_cmds_.pl1
29602 operator_mc_cmds_: define: ERROR_TABLE_MESSAGE
29603 define unsuccessful.
29604
29605
29606 Stream: $as1
29607
29608 Time: In response to an operator define command.
29609
29610 Meaning: An error was returned from mc_commands_$define
29611 causing the define to abort.
29612
29613 Action: Enter a corrected command line.
29614
29615
29616
29617 operator_mc_cmds_.pl1
29618 operator_mc_cmds_: define: Ioname not active.
29619 define unsuccessful.
29620
29621
29622 Stream: $as1
29623
29624 Time: In response to an operator define command.
29625
29626 Meaning: An error was returned from mc_commands_$define
29627 causing the define to abort. Target channel not
29628 active in the mc_anstbl.
29629
29630 Action: Enter a corrected command line.
29631
29632
29633
29634
29635
29636
29637
29638
29639 operator_mc_cmds_ -511- MR12.5 10/27/92^L
29640
29641
29642 operator_mc_cmds_.pl1
29643 operator_mc_cmds_: define: Ioname not found.
29644 define unsuccessful.
29645
29646
29647 Stream: $as1
29648
29649 Time: In response to an operator define command.
29650
29651 Meaning: An error was returned from mc_commands_$define
29652 causing the define to abort. Could not locate
29653 VCONS in vcons_tab.
29654
29655 Action: Enter a corrected command line.
29656
29657
29658
29659 operator_mc_cmds_.pl1
29660 operator_mc_cmds_: define: There is no room to
29661 make requested allocations.
29662
29663
29664 Stream: $as1
29665
29666 Time: In response to an operator define command.
29667
29668 Meaning: The operator has issued a define SOURCE STREAM
29669 VCONS command but the system could not make the
29670 new entry in the message routing table. No action
29671 was taken.
29672
29673 Action: Enter a corrected command line.
29674
29675
29676
29677 operator_mc_cmds_.pl1
29678 operator_mc_cmds_: define: Typename not found.
29679 define unsuccessful.
29680
29681
29682 Stream: $as1
29683
29684 Time: In response to an operator define command.
29685
29686 Meaning: An error was returned from mc_commands_$define
29687 causing the define to abort. Target VCONS type
29688 not known.
29689
29690 Action: Enter a corrected command line.
29691
29692
29693
29694
29695
29696
29697 operator_mc_cmds_ -512- MR12.5 10/27/92^L
29698
29699
29700 operator_mc_cmds_.pl1
29701 operator_mc_cmds_: deroute: ERROR_TABLE_MESSAGE
29702 reroute unsuccessful.
29703
29704
29705 Stream: $as1
29706
29707 Time: In response to an operator deroute command.
29708
29709 Meaning: An error was returned from mc_commands_$deroute
29710 causing the deroute to abort.
29711
29712 Action: Enter a corrected command line.
29713
29714
29715
29716 operator_mc_cmds_.pl1
29717 operator_mc_cmds_: deroute: There is no room to
29718 make requested allocations.
29719
29720
29721 Stream: $as1
29722
29723 Time: In response to an operator deroute command.
29724
29725 Meaning: The operator has issued a deroute SOURCE STREAM
29726 VCONS command but the system had no room to make
29727 the new entry in the message routing table. There
29728 may be up to 16 sources each with 8 streams and
29729 each stream may have up to 8 virtual consoles. No
29730 action was taken.
29731
29732 Action: Enter a corrected command line.
29733
29734
29735
29736 operator_mc_cmds_.pl1
29737 operator_mc_cmds_: drop: error: Channel CHANNEL
29738 not a message coordinator terminal.
29739
29740
29741 Stream: $as1
29742
29743 Time: In response to an operator command.
29744
29745 Meaning: Cannot drop CHANNEL as it cannot be found attached
29746 to the message coordinator.
29747
29748 Action: Contact the system programming staff.
29749
29750
29751
29752
29753
29754
29755 operator_mc_cmds_ -513- MR12.5 10/27/92^L
29756
29757
29758 operator_mc_cmds_.pl1
29759 operator_mc_cmds_: drop: error: Channel CHANNEL
29760 not configured.
29761
29762
29763 Stream: $as1
29764
29765 Time: In response to an operator command.
29766
29767 Meaning: Channel CHANNEL is not defined in the system cdt.
29768
29769 Action: Contact the system programming staff.
29770
29771
29772
29773 operator_mc_cmds_.pl1
29774 operator_mc_cmds_: drop: error: Channel CHANNEL
29775 not dialed to initializer.
29776
29777
29778 Stream: $as1
29779
29780 Time: In response to an operator command.
29781
29782 Meaning: CHANNEL must be dialed to the initializer before
29783 being dropped.
29784
29785 Action: Contact the system programming staff.
29786
29787
29788
29789 operator_mc_cmds_.pl1
29790 operator_mc_cmds_: drop: ERROR_TABLE_MESSAGE
29791 drop unsuccessful.
29792
29793
29794 Stream: $as1
29795
29796 Time: In response to an operator drop command.
29797
29798 Meaning: An error was returned from mc_commands_$remove_tty
29799 causing the drop to abort.
29800
29801 Action: Enter a corrected command line.
29802
29803
29804
29805
29806
29807
29808
29809
29810
29811
29812
29813 operator_mc_cmds_ -514- MR12.5 10/27/92^L
29814
29815
29816 operator_mc_cmds_.pl1
29817 operator_mc_cmds_: redefine: Action not
29818 performed. redefine unsuccessful.
29819
29820
29821 Stream: $as1
29822
29823 Time: In response to an operator redefine command.
29824
29825 Meaning: An error was returned from mc_commands_$redefine
29826 causing the redefine to abort. Target channel
29827 found requiring an accept in mc_anstbl.
29828
29829 Action: Enter a corrected command line.
29830
29831
29832
29833 operator_mc_cmds_.pl1
29834 operator_mc_cmds_: redefine: Allocation could
29835 not be performed. redefine unsuccessful.
29836
29837
29838 Stream: $as1
29839
29840 Time: In response to an operator redefine command.
29841
29842 Meaning: The operator has issued a redefine VCONS SOURCE
29843 STREAM VCONS command but the system could not make
29844 the new entry in the message routing table. No
29845 action was taken.
29846
29847 Action: Enter a corrected command line.
29848
29849
29850
29851 operator_mc_cmds_.pl1
29852 operator_mc_cmds_: redefine: ERROR_TABLE_MESSAGE
29853 redefine unsuccessful.
29854
29855
29856 Stream: $as1
29857
29858 Time: In response to an operator redefine command.
29859
29860 Meaning: An error was returned from mc_commands_$redefine
29861 causing the redefine to abort.
29862
29863 Action: Enter a corrected command line.
29864
29865
29866
29867
29868
29869
29870
29871 operator_mc_cmds_ -515- MR12.5 10/27/92^L
29872
29873
29874 operator_mc_cmds_.pl1
29875 operator_mc_cmds_: redefine: Ioname not active.
29876 redefine unsuccessful.
29877
29878
29879 Stream: $as1
29880
29881 Time: In response to an operator redefine command.
29882
29883 Meaning: An error was returned from mc_commands_$redefine
29884 causing the redefine to abort. Target channel not
29885 active in the mc_anstbl.
29886
29887 Action: Enter a corrected command line.
29888
29889
29890
29891 operator_mc_cmds_.pl1
29892 operator_mc_cmds_: redefine: Ioname not found.
29893 redefine unsuccessful.
29894
29895
29896 Stream: $as1
29897
29898 Time: In response to an operator redefine command.
29899
29900 Meaning: An error was returned from mc_commands_$redefine
29901 causing the redefine to abort. Could not locate
29902 VCONS in vcons_tab.
29903
29904 Action: Enter a corrected command line.
29905
29906
29907
29908 operator_mc_cmds_.pl1
29909 operator_mc_cmds_: redefine: Typename not found.
29910 redefine unsuccessful.
29911
29912
29913 Stream: $as1
29914
29915 Time: In response to an operator redefine command.
29916
29917 Meaning: An error was returned from mc_commands_$redefine
29918 causing the redefine to abort. Target VCONS type
29919 not known.
29920
29921 Action: Enter a corrected command line.
29922
29923
29924
29925
29926
29927
29928
29929 operator_mc_cmds_ -516- MR12.5 10/27/92^L
29930
29931
29932 operator_mc_cmds_.pl1
29933 operator_mc_cmds_: reroute: ERROR_TABLE_MESSAGE
29934 reroute unsuccessful.
29935
29936
29937 Stream: $as1
29938
29939 Time: In response to an operator reroute command.
29940
29941 Meaning: An error was returned from mc_commands_$reroute
29942 causing the reroute to abort.
29943
29944 Action: Enter a corrected command line.
29945
29946
29947
29948 operator_mc_cmds_.pl1
29949 operator_mc_cmds_: reroute: There is no room to
29950 make requested allocations.
29951
29952
29953 Stream: $as1
29954
29955 Time: In response to an operator reroute command.
29956
29957 Meaning: The operator has issued a reroute SOURCE STREAM
29958 OLD_VCONS NEW_VCONS command but the system had no
29959 room to make the new entry in the message routing
29960 table. There may be up to 16 sources each with 8
29961 streams and each stream may have up to 8 virtual
29962 consoles. No action was taken.
29963
29964 Action: Enter a corrected command line.
29965
29966
29967
29968 operator_mc_cmds_.pl1
29969 operator_mc_cmds_: route: ERROR_TABLE_MESSAGE
29970 route unsuccessful.
29971
29972
29973 Stream: $as1
29974
29975 Time: In response to an operator route command.
29976
29977 Meaning: An error was returned from mc_commands_$route
29978 causing the route to abort.
29979
29980 Action: Enter a corrected command line.
29981
29982
29983
29984
29985
29986
29987 operator_mc_cmds_ -517- MR12.5 10/27/92^L
29988
29989
29990 operator_mc_cmds_.pl1
29991 operator_mc_cmds_: route: Ioname not found.
29992 route unsuccessful.
29993
29994
29995 Stream: $as1
29996
29997 Time: In response to an operator route command.
29998
29999 Meaning: An error was returned from mc_commands_$route
30000 causing the route to abort. VCONS not located in
30001 vcons_tab.
30002
30003 Action: Enter a corrected command line.
30004
30005
30006
30007 operator_mc_cmds_.pl1
30008 operator_mc_cmds_: route: There is no room to
30009 make requested allocations.
30010
30011
30012 Stream: $as1
30013
30014 Time: In response to an operator route command.
30015
30016 Meaning: The operator has issued a route SOURCE STREAM
30017 VCONS command but the system had no room to make
30018 the new entry in the message routing table. There
30019 may be up to 16 sources each with 8 streams and
30020 each stream may have up to 8 virtual consoles. No
30021 action was taken.
30022
30023 Action: Enter a corrected command line.
30024
30025
30026
30027 operator_mc_cmds_.pl1
30028 operator_mc_cmds_: substty: ERROR_TABLE_MESSAGE
30029 removing channel CHANNEL
30030
30031
30032 Stream: $as1
30033
30034 Time: In response to an operator substty command.
30035
30036 Meaning: Unable to remove CHANNEL designated as the source
30037 of the substitution.
30038
30039 Action: Enter a corrected command line.
30040
30041
30042
30043
30044
30045 operator_mc_cmds_ -518- MR12.5 10/27/92^L
30046
30047
30048 operator_mc_cmds_.pl1
30049 operator_mc_cmds_: substty: Channel CHANNEL not
30050 configured.
30051
30052
30053 Stream: $as1
30054
30055 Time: In response to an operator substty command.
30056
30057 Meaning: Channel CHANNEL is not found in the system cdt.
30058
30059 Action: Enter a corrected command line.
30060
30061
30062
30063 operator_mc_cmds_.pl1
30064 operator_mc_cmds_: substty: Channel CHANNEL not
30065 dialed to initializer
30066
30067
30068 Stream: $as1
30069
30070 Time: In response to an operator substty command.
30071
30072 Meaning: Channel CHANNEL was not previously dialed to the
30073 initializer and thus cannot be substituted.
30074
30075 Action: Enter a corrected command line.
30076
30077
30078
30079 operator_mc_cmds_.pl1
30080 operator_mc_cmds_: substty: error: cannot
30081 substty for same channel
30082
30083
30084 Stream: $as1
30085
30086 Time: In response to an operator substty command.
30087
30088 Meaning: The operator has attempted to use substty to
30089 substitute a channel for itself.
30090
30091 Action: Enter a corrected command line.
30092
30093
30094
30095
30096
30097
30098
30099
30100
30101
30102
30103 operator_mc_cmds_ -519- MR12.5 10/27/92^L
30104
30105
30106 operator_mc_cmds_.pl1
30107 operator_mc_cmds_: substty: error: channel not
30108 available
30109
30110
30111 Stream: $as1
30112
30113 Time: In response to an operator accept command.
30114
30115 Meaning: Channel cannot be used as a message coordinator
30116 channel.
30117
30118 Action: Enter a corrected command line.
30119
30120
30121
30122 operator_mc_cmds_.pl1
30123 operator_mc_cmds_: substty: error: channel not
30124 defined in cdt.
30125
30126
30127 Stream: $as1
30128
30129 Time: In response to an operator accept command.
30130
30131 Meaning: Channel is not found in the system cdt and
30132 therefore cannot be used.
30133
30134 Action: Enter a corrected command line.
30135
30136
30137
30138 operator_mc_cmds_.pl1
30139 operator_mc_cmds_: substty: ERROR_TABLE_MESSAGE
30140 substty unsuccessful.
30141
30142
30143 Stream: $as1
30144
30145 Time: In response to an operator substty command.
30146
30147 Meaning: An error was returned from mc_commands_$substty
30148 causing the substty to abort.
30149
30150 Action: Enter a corrected command line.
30151
30152
30153
30154
30155
30156
30157
30158
30159
30160
30161 operator_mc_cmds_ -520- MR12.5 10/27/92^L
30162
30163
30164 operator_mc_cmds_.pl1
30165 operator_mc_cmds_: substty: Ioname not found.
30166 substty unsuccessful.
30167
30168
30169 Stream: $as1
30170
30171 Time: In response to an operator substty command.
30172
30173 Meaning: An error was returned from mc_commands_$substty
30174 causing the substty to abort. Could not locate
30175 source channel in mc_anstbl.
30176
30177 Action: Enter a corrected command line.
30178
30179
30180
30181 operator_mc_cmds_.pl1
30182 operator_mc_cmds_: substty: Ioname not found.
30183 substty unsuccessful.
30184
30185
30186 Stream: $as1
30187
30188 Time: In response to an operator substty command.
30189
30190 Meaning: The error was returned from mc_commands_$new_tty
30191 causing the substty to abort. The target channel
30192 not found in the cdt or pre-accepted as a virtual
30193 channel.
30194
30195 Action: Enter a corrected command line.
30196
30197
30198
30199 operator_mc_cmds_.pl1
30200 operator_mc_cmds_: substty: The requested action
30201 was not performed. substty unsuccessful.
30202
30203
30204 Stream: $as1
30205
30206 Time: In response to an operator substty command.
30207
30208 Meaning: An error was returned from mc_commands_$substty
30209 causing the substty to abort. The target channel
30210 is in a "pending" state which means it has not
30211 been accepted yet.
30212
30213 Action: Enter a corrected command line.
30214
30215
30216
30217
30218
30219 operator_mc_cmds_ -521- MR12.5 10/27/92^L
30220
30221
30222 operator_mc_cmds_.pl1
30223 operator_mc_cmds_: undefine: ERROR_TABLE_MESSAGE
30224 undefine unsuccessful.
30225
30226
30227 Stream: $as1
30228
30229 Time: In response to an operator undefine command.
30230
30231 Meaning: An error was returned from mc_commands_$undefine
30232 causing the undefine to abort.
30233
30234 Action: Enter a corrected command line.
30235
30236
30237
30238 operator_mc_cmds_.pl1
30239 operator_mc_cmds_: undefine: Ioname not found.
30240 undefine unsuccessful.
30241
30242
30243 Stream: $as1
30244
30245 Time: In response to an operator undefine command.
30246
30247 Meaning: An error was returned from mc_commands_$undefine
30248 causing the undefine to abort. Could not locate
30249 VCONS in vcons_tab.
30250
30251 Action: Enter a corrected command line.
30252
30253
30254
30255 operator_process_cmds_.pl1
30256 operator_process_cmds_: bump: error: invalid
30257 arguments
30258
30259
30260 Stream: $as1
30261
30262 Time: In response to an operator command.
30263
30264 Meaning: A bad argument has been typed to the bump command.
30265 No action was taken.
30266
30267 Action: Enter a corrected command line.
30268
30269
30270
30271
30272
30273
30274
30275
30276
30277 operator_process_cmds_ -522- MR12.5 10/27/92^L
30278
30279
30280 operator_process_cmds_.pl1
30281 operator_process_cmds_: bump: NAME.PROJ bumped
30282
30283
30284 Stream: $as1
30285
30286 Time: In response to an operator command.
30287
30288 Meaning: This is the response to an operator bump command.
30289 The user affected is named.
30290
30291 Action: No operator action is required.
30292
30293
30294
30295 operator_process_cmds_.pl1
30296 operator_process_cmds_: bump: NAME.PROJ has
30297 "nobump"
30298
30299
30300 Stream: $as1
30301
30302 Time: While system is running.
30303
30304 Meaning: This is the response to the command bump NAME PROJ
30305 if the user has the nobump privilege. The user
30306 was not bumped.
30307
30308 Action: If it is imperative to bump the user for instance
30309 at system shutdown time do a who to find out his
30310 channel number then type "bump CHANNEL".
30311
30312
30313
30314 operator_process_cmds_.pl1
30315 operator_process_cmds_: bump: no bump signalled
30316 to NAME PROJ
30317
30318
30319 Stream: $as1
30320
30321 Time: In response to an operator command.
30322
30323 Meaning: An operator bump command specified a nonexistent
30324 channel name or user name and project. No action
30325 was taken on the command.
30326
30327 Action: Enter a corrected command line. This message may
30328 be printed as a result of trying to bump a user by
30329 name when he has nobump privilege. Bump him by
30330 channel name instead.
30331
30332
30333
30334
30335 operator_process_cmds_ -523- MR12.5 10/27/92^L
30336
30337
30338 operator_process_cmds_.pl1
30339 operator_process_cmds_: COMMAND: error: Invalid
30340 FNP tag: FNP
30341
30342
30343 Stream: $as1
30344
30345 Time: In response to an operator command COMMAND.
30346
30347 Meaning: The FNP tag following COMMAND was more than one
30348 character in length. FNP specifiers can only be
30349 one character long ie: a b c etc..
30350
30351 Action: Enter a corrected command line.
30352
30353
30354
30355 operator_process_cmds_.pl1
30356 operator_process_cmds_: COMMAND: error: No FNP
30357 tag specified
30358
30359
30360 Stream: $as1
30361
30362 Time: In response to an operator command COMMAND.
30363
30364 Meaning: Expected a FNP designator but none typed
30365 following COMMAND.
30366
30367 Action: Enter a corrected command line.
30368
30369
30370
30371 operator_process_cmds_.pl1
30372 operator_process_cmds_: COMMAND: error: No
30373 multiplexer specified
30374
30375
30376 Stream: $as1
30377
30378 Time: In response to an operator command COMMAND.
30379
30380 Meaning: Expected a multiplexer designator but none typed
30381 following COMMAND.
30382
30383 Action: Enter a corrected command line.
30384
30385
30386
30387
30388
30389
30390
30391
30392
30393 operator_process_cmds_ -524- MR12.5 10/27/92^L
30394
30395
30396 operator_process_cmds_.pl1
30397 operator_process_cmds_: COMMAND: error: Usage:
30398 COMMAND Person.Project|CHANNEL|mpx MPX TIME
30399 MESSAGE The "Person Project" format is obsolete.
30400
30401
30402 Stream: $as1
30403
30404 Time: In response to an operator command COMMAND.
30405
30406 Meaning: The character "." was not found on the request
30407 line and COMMAND was not followed by a process id.
30408 If argument following COMMAND is personid and
30409 projectid the correct syntax is "Person.Project"
30410 not "Person Project".
30411
30412 Action: Enter a corrected command line.
30413
30414
30415
30416 operator_process_cmds_.pl1
30417 operator_process_cmds_: COMMAND: error: Usage:
30418 COMMAND Person.Project|CHANNEL|mpx MPX|-pid
30419 TIME MESSAGE
30420
30421
30422 Stream: $as1
30423
30424 Time: In response to an operator command COMMAND.
30425
30426 Meaning: Insufficient number of arguments supplied with the
30427 command.
30428
30429 Action: Enter a corrected command line.
30430
30431
30432
30433 operator_process_cmds_.pl1
30434 operator_process_cmds_: COMMAND:
30435 ERROR_TABLE_MESSAGE SYSDIR>answer_table
30436
30437
30438 Stream: $as1
30439
30440 Time: In response to an operator command COMMAND.
30441
30442 Meaning: The system was unable to access the answer_table
30443 in SYSDIR.
30444
30445 Action: Contact the system programming staff.
30446
30447
30448
30449
30450
30451 operator_process_cmds_ -525- MR12.5 10/27/92^L
30452
30453
30454 operator_process_cmds_.pl1
30455 operator_process_cmds_: COMMAND:
30456 ERROR_TABLE_MESSAGE SYSDIR>cdt
30457
30458
30459 Stream: $as1
30460
30461 Time: In response to an operator command COMMAND.
30462
30463 Meaning: The system was unable to access the cdt in SYSDIR.
30464
30465 Action: Contact the system programming staff.
30466
30467
30468
30469 operator_process_cmds_.pl1
30470 operator_process_cmds_: COMMAND:
30471 ERROR_TABLE_MESSAGE SYSDIR>installation_parms
30472
30473
30474 Stream: $as1
30475
30476 Time: In response to an operator command COMMAND.
30477
30478 Meaning: The system was unable to access the
30479 installation_parms in SYSDIR.
30480
30481 Action: Contact the system programming staff.
30482
30483
30484
30485 operator_process_cmds_.pl1
30486 operator_process_cmds_: COMMAND:
30487 ERROR_TABLE_MESSAGE SYSDIR>whotab
30488
30489
30490 Stream: $as1
30491
30492 Time: In response to an operator command COMMAND.
30493
30494 Meaning: The system was unable to access the whotab in
30495 SYSDIR.
30496
30497 Action: Contact the system programming staff.
30498
30499
30500
30501
30502
30503
30504
30505
30506
30507
30508
30509 operator_process_cmds_ -526- MR12.5 10/27/92^L
30510
30511
30512 operator_process_cmds_.pl1
30513 operator_process_cmds_: COMMAND:
30514 ERROR_TABLE_MESSAGE Error recieved from AS.
30515
30516
30517 Stream: $as1
30518
30519 Time: In response to an operator command COMMAND.
30520
30521 Meaning: Recieved an error from answering service
30522 attempting to remove the terminal user from the
30523 system answer table. User's process state will
30524 remain unchanged.
30525
30526 Action: Enter a corrected command line.
30527
30528
30529
30530 operator_process_cmds_.pl1
30531 operator_process_cmds_: COMMAND:
30532 ERROR_TABLE_MESSAGE From hcs_$wakeup for CHANNEL
30533
30534
30535 Stream: $as1
30536
30537 Time: In response to an operator command COMMAND.
30538
30539 Meaning: Recieved an error from answering service when
30540 attempting to process the command COMMAND for
30541 channel CHANNEL.
30542
30543 Action: Enter a corrected command line.
30544
30545
30546
30547 operator_process_cmds_.pl1
30548 operator_process_cmds_: COMMAND:
30549 ERROR_TABLE_MESSAGE Incorrect number of arguments.
30550
30551
30552 Stream: $as1
30553
30554 Time: In response to an operator command COMMAND.
30555
30556 Meaning: Insufficient number of arguments supplied with the
30557 command.
30558
30559 Action: Enter a corrected command line.
30560
30561
30562
30563
30564
30565
30566
30567 operator_process_cmds_ -527- MR12.5 10/27/92^L
30568
30569
30570 operator_process_cmds_.pl1
30571 operator_process_cmds_: COMMAND:
30572 ERROR_TABLE_MESSAGE Invalid process id:
30573 PROCESS_ID. Use the first 6 or all 12 digits of
30574 the pid.
30575
30576
30577 Stream: $as1
30578
30579 Time: In response to an operator command COMMAND.
30580
30581 Meaning: The typed length of the PROCESS_ID was incorrect.
30582
30583 Action: Enter a corrected command line.
30584
30585
30586
30587 operator_process_cmds_.pl1
30588 operator_process_cmds_: detach: Channel CHANNEL
30589 is not currently active and cannot be detached.
30590
30591
30592 Stream: $as1
30593
30594 Time: In response to an operator command.
30595
30596 Meaning: An operator detach command specified a channel
30597 that is not attached. No action was taken.
30598
30599 Action: Enter a corrected command line
30600
30601
30602
30603 operator_process_cmds_.pl1
30604 operator_process_cmds_: detach: CHANNEL is in
30605 use by the message coordinator and can not be
30606 detached.
30607
30608
30609 Stream: $as1
30610
30611 Time: In response to an operator command.
30612
30613 Meaning: An operator detach command specified a message
30614 coordinator channel. The channel was not
30615 detached.
30616
30617 Action: Enter a corrected command line. Use the drop
30618 command to take a channel away from the message
30619 coordinator.
30620
30621
30622
30623
30624
30625 operator_process_cmds_ -528- MR12.5 10/27/92^L
30626
30627
30628 operator_process_cmds_.pl1
30629 operator_process_cmds_: detach: error: invalid
30630 arguments
30631
30632
30633 Stream: $as1
30634
30635 Time: In response to an operator command.
30636
30637 Meaning: A bad argument has been typed to the detach
30638 command. No action was taken.
30639
30640 Action: Enter a corrected command line.
30641
30642
30643
30644 operator_process_cmds_.pl1
30645 operator_process_cmds_: detach: ERROR_MESSAGE
30646 CHANNEL
30647
30648
30649 Stream: $as1
30650
30651 Time: In response to an operator command.
30652
30653 Meaning: The operator has issued a detach CHANNEL command
30654 and the error described by ERROR_MESSAGE occurred
30655 during the attempt to detach it.
30656
30657 Action: Enter a corrected command line.
30658
30659
30660
30661 operator_process_cmds_.pl1
30662 operator_process_cmds_: detach: NAME.PROJ
30663 detached
30664
30665
30666 Stream: $as1
30667
30668 Time: In response to an operator command.
30669
30670 Meaning: This is the response to an operator detach
30671 command. The user affected is named.
30672
30673 Action: No operator action is required.
30674
30675
30676
30677
30678
30679
30680
30681
30682
30683 operator_process_cmds_ -529- MR12.5 10/27/92^L
30684
30685
30686 operator_process_cmds_.pl1
30687 operator_process_cmds_: detach: no detach
30688 signalled to NAME PROJ
30689
30690
30691 Stream: $as1
30692
30693 Time: In response to an operator command.
30694
30695 Meaning: An operator detach command specified a nonexistent
30696 channel name or user name and project. No action
30697 was taken on the command.
30698
30699 Action: Enter a corrected command line.
30700
30701
30702
30703 operator_process_cmds_.pl1
30704 operator_process_cmds_: disconnect: NAME.PROJ
30705 disconnected.
30706
30707
30708 Stream: $as1
30709
30710 Time: In response to an operator command.
30711
30712 Meaning: This is the response to an operator disconnect
30713 command. The user affected is named.
30714
30715 Action: No operator action is required.
30716
30717
30718
30719 operator_process_cmds_.pl1
30720 operator_process_cmds_: terminate: NAME.PROJ
30721 terminated
30722
30723
30724 Stream: $as1
30725
30726 Time: In response to an operator command.
30727
30728 Meaning: This is the response to an operator terminate
30729 command. The user affected is named.
30730
30731 Action: No operator action is required.
30732
30733
30734
30735
30736
30737
30738
30739
30740
30741 operator_process_cmds_ -530- MR12.5 10/27/92^L
30742
30743
30744 operator_process_cmds_.pl1
30745 operator_process_cmds_: terminate: no terminate
30746 signalled to NAME PROJ
30747
30748
30749 Stream: $as1
30750
30751 Time: In response to an operator command.
30752
30753 Meaning: An operator terminate command specified a
30754 nonexistent channel name or user name and project.
30755 No action was taken on the command.
30756
30757 Action: Enter a corrected command line.
30758
30759
30760
30761 operator_process_cmds_.pl1
30762 operator_process_cmds_: unbump: error: invalid
30763 arguments
30764
30765
30766 Stream: $as1
30767
30768 Time: In response to an operator command.
30769
30770 Meaning: A bad argument has been typed to the unbump
30771 command. No action was taken.
30772
30773 Action: Enter a corrected command line.
30774
30775
30776
30777 operator_process_cmds_.pl1
30778 operator_process_cmds_: unbump: NAME.PROJ
30779 unbumped
30780
30781
30782 Stream: $as1
30783
30784 Time: In response to an operator command.
30785
30786 Meaning: This is the response to an operator unbump
30787 command. The user affected is named.
30788
30789 Action: No operator action is required.
30790
30791
30792
30793
30794
30795
30796
30797
30798
30799 operator_process_cmds_ -531- MR12.5 10/27/92^L
30800
30801
30802 operator_process_cmds_.pl1
30803 operator_process_cmds_: unbump: no unbump
30804 signalled to NAME PROJ
30805
30806
30807 Stream: $as1
30808
30809 Time: In response to an operator command.
30810
30811 Meaning: An operator unbump command specified a nonexistent
30812 channel name or user name and project or the user
30813 specified was not in a bumped state. No action
30814 was taken on the command.
30815
30816 Action: Enter a corrected command line.
30817
30818
30819
30820 page_error.alm
30821 page_fault: Deleting main memory at AAAA SCU
30822 TAG due to parity errors.
30823
30824
30825 Stream: BOS Typewriter sounds beeper
30826
30827 Time: While system is running.
30828
30829 Meaning: Due to main memory parity errors the system is
30830 automatically removing a page of main memory from
30831 the memory in SCU TAG preventing further use
30832 during this bootload.
30833
30834 Action: Inform Field Engineering personnel about possible
30835 problems with this SCU.
30836
30837
30838
30839 page_error.alm
30840 page_fault: device read not complete DSKX_NNS
30841 DDDD
30842
30843
30844 Stream: BOS Typewriter Crashes system
30845
30846 Time: While system is running.
30847
30848 Meaning: This message is used for program debugging only.
30849
30850 Action: Follow normal recovery procedures. Contact the
30851 system programming staff.
30852
30853
30854
30855
30856
30857 page_fault -532- MR12.5 10/27/92^L
30858
30859
30860 page_error.alm
30861 page_fault: fatal error at loc AAAA
30862
30863
30864 Stream: BOS Typewriter Crashes system
30865
30866 Time: While system is running.
30867
30868 Meaning: This indicates a logic error in the supervisor or
30869 CPU or memory hardware problems.
30870
30871 Action: Follow normal recovery procedures.
30872
30873
30874
30875 page_error.alm
30876 page_fault: fatal error in done ptp ZZZZ
30877
30878
30879 Stream: BOS Typewriter Crashes system
30880
30881 Time: While system is running.
30882
30883 Meaning: While posting an I/O completion the system found
30884 a page table pointer of zero or found that the
30885 page was not out of service. This indicates a
30886 logic error in the supervisor or CPU or memory
30887 hardware problems.
30888
30889 Action: Follow normal recovery procedures.
30890
30891
30892
30893 page_error.alm
30894 page_fault: mylock on global lock
30895
30896
30897 Stream: BOS Typewriter Crashes system
30898
30899 Time: While system is running.
30900
30901 Meaning: When page_fault attempted to lock the global page
30902 control lock it found it already locked to the
30903 same process. This indicates a logic error in the
30904 supervisor or CPU or memory hardware problems.
30905
30906 Action: Follow normal recovery procedures.
30907
30908
30909
30910
30911
30912
30913
30914
30915 page_fault -533- MR12.5 10/27/92^L
30916
30917
30918 page_error.alm
30919 page_fault: nonfatal error at loc AAAA
30920
30921
30922 Stream: BOS Typewriter.
30923
30924 Time: While system is running.
30925
30926 Meaning: This indicates a logic error in the supervisor or
30927 CPU or memory hardware problems. The system
30928 attempts to keep running.
30929
30930 Action: No operator action is required.
30931
30932
30933
30934 page_error.alm
30935 page_fault: out of main memory
30936
30937
30938 Stream: BOS Typewriter Crashes system
30939
30940 Time: While system is running.
30941
30942 Meaning: The page removal algorithm was unable to find a
30943 removable page. Incorrect system programmer
30944 action damage to the AST or an error in the
30945 supervisor or the hardware could cause this
30946 symptom.
30947
30948 Action: Follow normal recovery procedures.
30949
30950
30951
30952
30953
30954
30955
30956
30957
30958
30959
30960
30961
30962
30963
30964
30965
30966
30967
30968
30969
30970
30971
30972
30973 page_fault -534- MR12.5 10/27/92^L
30974
30975
30976 page_error.alm
30977 page_fault: Reverting page on DSKX_NNS
30978
30979
30980 Stream: BOS Typewriter.
30981
30982 Time: While system is running.
30983
30984 Meaning: A segment residing on DSKX_NNS has had one of
30985 its pages reverted to an earlier copy of the same
30986 page. The damaged switch is set. This can happen
30987 due to device error or main memory errors.
30988 Subsequent user processes attempting to use this
30989 segment will receive an error indication. Binary
30990 information identifying the damaged segment is
30991 encoded into this message for subsequent automatic
30992 processing. The pathname of the damaged segment
30993 will appear in a message in the answering service
30994 log bearing the syserr log sequence number of
30995 this message shortly after this message occurs.
30996
30997 Action: Attempt to identify the damaged segment and inform
30998 its owner.
30999
31000
31001
31002 page_error.alm
31003 page_fault: Zeroing page on DSKX_NNS
31004
31005
31006 Stream: BOS Typewriter.
31007
31008 Time: While system is running.
31009
31010 Meaning: A segment residing on DSKX_NNS has been damaged
31011 due to a device error. The segment damaged switch
31012 is set and a page of zeros is introduced into the
31013 segment. Subsequent user processes attempting to
31014 use this segment will receive an error indication.
31015 Binary information identifying the damaged segment
31016 is encoded into this message for subsequent
31017 automatic processing. The pathname of the damaged
31018 segment will appear in a message in the answering
31019 service log bearing the syserr_log sequence
31020 number of this message shortly after this message
31021 occurs.
31022
31023 Action: Attempt to identify the damaged segment and
31024 inform its owner.
31025
31026
31027
31028
31029
31030
31031 page_fault -535- MR12.5 10/27/92^L
31032
31033
31034 page_error.alm
31035 page_synch: dm_journal_seg_ inconsistent.
31036
31037
31038 Time: While system is running.
31039
31040 Stream: BOS Typewriter Crashes system
31041
31042 Meaning: This indicates a logic error in the supervisor or
31043 CPU or memory hardware problems.
31044
31045 Action: Follow normal recovery procedures.
31046
31047
31048
31049 page_error.alm
31050 page_synch: Out of free entries in
31051 dm_journal_seg_.
31052
31053
31054 Time: While system is running.
31055
31056 Stream: BOS Typewriter Crashes system
31057
31058 Meaning: This indicates a logic error in the supervisor or
31059 CPU or memory hardware problems.
31060
31061 Action: Follow normal recovery procedures.
31062
31063
31064
31065 pc.pl1.pmac
31066 pc: truncate_deposit_all call on VTOCed seg at
31067 ASTEP
31068
31069
31070 Stream: BOS Typewriter Crashes system
31071
31072 Time: While system is running.
31073
31074 Meaning: A call to pc$truncate_deposit_all has been made on
31075 a segment for which this operation is not allowed.
31076 The AST entry at ASTEP should have a zero unique
31077 ID but it does not. This indicates a logic error
31078 in the supervisor or CPU or memory hardware
31079 problems. This error crashes the system.
31080
31081 Action: Follow normal recovery procedures.
31082
31083
31084
31085
31086
31087
31088
31089 pc -536- MR12.5 10/27/92^L
31090
31091
31092 pc.pl1.pmac
31093 pc: unprotected address DDDDD in DSKX_NN VTOCX
31094
31095
31096 Stream: BOS Typewriter.
31097
31098 Time: While system is running.
31099
31100 Meaning: The disk address DDDDD is not marked as protected
31101 in the record usage map for the volume mounted on
31102 DSKX_NN. This condition has been discovered while
31103 activating the segment with VTOC index VTOCX. The
31104 segment's damaged switch is turned on and a page
31105 of zeros will replace the bad address. This
31106 condition may be symptomatic of disk or other
31107 hardware failure.
31108
31109 Action: Contact the system programming staff.
31110
31111
31112
31113 pc_abs.pl1.pmac
31114 pc_abs$unwire_abs: Attempt to unwire inconsistent
31115 CME at CMEP.
31116
31117
31118 Stream: BOS Typewriter Crashes system
31119
31120 Time: While system is running.
31121
31122 Meaning: The core map entry for the page being abs unwired
31123 did not have the abs_w flag on which indicates
31124 that it was properly abs wired. This indicates a
31125 logic error in the supervisor or CPU or memory
31126 hardware problems.
31127
31128 Action: Contact the system programming staff. Follow
31129 normal recovery procedures.
31130
31131
31132
31133
31134
31135
31136
31137
31138
31139
31140
31141
31142
31143
31144
31145
31146
31147 pc_abs$unwire_abs -537- MR12.5 10/27/92^L
31148
31149
31150 pc_abs.pl1.pmac
31151 pc_abs$unwire_abs: Attempt to unwire inconsistent
31152 PTW at PTP.
31153
31154
31155 Stream: BOS Typewriter Crashes system
31156
31157 Time: While system is running.
31158
31159 Meaning: A page at PTP within the range of pages being
31160 unwired for was found to either not be wired or
31161 no longer in memory. This indicates a logic error
31162 in the supervisor or CPU or memory hardware
31163 problems.
31164
31165 Action: Contact the system programming staff. Follow
31166 normal recovery procedures.
31167
31168
31169
31170 pc_abs.pl1.pmac
31171 pc_abs$unwire_abs: Called with NULL astep.
31172
31173
31174 Stream: BOS Typewriter Crashes system
31175
31176 Time: While system is running.
31177
31178 Meaning: This indicates a logic error in the supervisor or
31179 CPU or memory hardware problems.
31180
31181 Action: Contact the system programming staff. Follow
31182 normal recovery procedures.
31183
31184
31185
31186 pc_abs.pl1.pmac
31187 pc_abs: Parity error in I/O buffer.
31188
31189
31190 Stream: BOS Typewriter Crashes system
31191
31192 Time: While system is running.
31193
31194 Meaning: This indicates a logic error in the supervisor or
31195 CPU or memory hardware problems.
31196
31197 Action: Follow normal recovery procedures.
31198
31199
31200
31201
31202
31203
31204
31205 pc_abs -538- MR12.5 10/27/92^L
31206
31207
31208 pc_deposit.pl1
31209 pc_deposit: Address XXXXXX out of paging region
31210 on dskX_NNs.
31211
31212
31213 Stream: BOS Typewriter Crashes system
31214
31215 Time: While system is running.
31216
31217 Meaning: An attempt was made to return disk address XXXXXX
31218 on device dskX_NNs to the free pool. The
31219 address is not in the paging region.
31220
31221 Action: Follow normal recovery procedures. It may be
31222 necessary to run the physical volume salvager on
31223 the device.
31224
31225
31226
31227 pc_deposit.pl1
31228 pc_deposit: Deposit in-use address XXXXXX on
31229 dskX_NNs.
31230
31231
31232 Stream: BOS Typewriter sounds beeper
31233
31234 Time: While system is running.
31235
31236 Meaning: An attempt was made to return address XXXXXX on
31237 device dskX_NNs to the free record pool but the
31238 address was already marked as free. This
31239 indicates damage to control structures on the
31240 device. This damage can be corrected by a
31241 physical volume salvage.
31242
31243 Action: Contact the system programming staff.
31244
31245
31246
31247
31248
31249
31250
31251
31252
31253
31254
31255
31256
31257
31258
31259
31260
31261
31262
31263 pc_deposit -539- MR12.5 10/27/92^L
31264
31265
31266 pc_deposit.pl1
31267 pc_deposit: Invalid address XXXXXX on dskX_NNs.
31268
31269
31270 Stream: BOS Typewriter Crashes system
31271
31272 Time: While system is running.
31273
31274 Meaning: In attempting to deposit address XXXXXX on device
31275 dskX_NNs an invalid volume map offset was
31276 computed.
31277
31278 Action: Follow normal recovery procedures. It may be
31279 necessary to run the physical volume salvager on
31280 the device.
31281
31282
31283
31284 pc_deposit.pl1
31285 pc_deposit: Unrecoverable I/O error on Volmap
31286 page M of dskX_NNs. Addresses lost.
31287
31288
31289 Stream: BOS Typewriter sounds beeper
31290
31291 Time: While system is running.
31292
31293 Meaning: There was an unrecoverable I/O error on a page of
31294 the Volume Map which describes free records of
31295 the volume. All free records described by that
31296 page have been lost.
31297
31298 Action: It may be possible to recover the lost addresses
31299 by a volume salvage. If there is a hard device
31300 error the volume salvage will fail. In this
31301 case it will be necessary to recover the volume
31302 onto a good pack.
31303
31304
31305
31306 ring_0_peek.pl1
31307 PERSON.PROJ.T: MESSAGE
31308
31309
31310 Stream: BOS Typewriter sounds beeper
31311
31312 Time: While system is running.
31313
31314 Meaning: A privileged user has sent a message to be printed
31315 on the SYSERR console.
31316
31317 Action: Read the message and take appropriate action.
31318
31319
31320
31321 PERSON.PROJ.T -540- MR12.5 10/27/92^L
31322
31323
31324 ring_0_peek.pl1
31325 PERSON.PROJ.T: NN words @ SSS|XXX
31326 XXX WWWWWWWWWWWW to YYYYYYYYYYYY
31327 XXX WWWWWWWWWWWW to YYYYYYYYYYYY
31328
31329
31330 Stream: BOS Typewriter sounds beeper
31331
31332 Time: While system is running.
31333
31334 Meaning: A privileged user has patched the hardcore
31335 supervisor.
31336
31337 Action: No operator action is required.
31338
31339
31340
31341 prds_init.pl1
31342 prds_init: Invalid size for
31343 prds$fast_connect_code
31344
31345
31346 Stream: BOS Typewriter Crashes system
31347
31348 Time: System Intialization.
31349
31350 Meaning: There is an inconsistency between modules prds and
31351 fast_connect_init on the boot tape. Specifically
31352 the amount of space allocated for fast connect
31353 code in the prds does not agree with the size of
31354 the code in fast_connect_init. The most likely
31355 cause is that one of these modules is not up to
31356 date.
31357
31358 Action: Contact the system administrator. A new boot tape
31359 must be generated with the proper versions of
31360 modules prds and fast_connect_init.
31361
31362
31363
31364
31365
31366
31367
31368
31369
31370
31371
31372
31373
31374
31375
31376
31377
31378
31379 prds_init -541- MR12.5 10/27/92^L
31380
31381
31382 priv_delete_vtoce.pl1
31383 priv_delete_vtoce: failed to lock WWWWWW
31384 ERROR_MESSAGE
31385
31386
31387 Stream: BOS Typewriter Crashes system
31388
31389 Time: While system is running.
31390
31391 Meaning: An attempt to lock a directory has failed. This
31392 indicates a logic error in the supervisor or CPU
31393 or memory hardware problems.
31394
31395 Action: Follow normal recovery procedures. The Multics
31396 System Tape may be incorrect. If the problem
31397 persists try another MST.
31398
31399
31400
31401 proc_int_handler.pl1
31402 proc_int_handler: Invalid IPS interrupts
31403 IPS_BITS for USERNAME.
31404
31405
31406 Stream: BOS Typewriter.
31407
31408 Time: While system is running.
31409
31410 Meaning: One or more undefined IPS messages as indicated by
31411 IPS_BITS have been sent to user USERNAME. They
31412 are ignored.
31413
31414 Action: Contact the system programming staff.
31415
31416
31417
31418 pxss.alm
31419 pxss: APT not locked
31420
31421 Stream: BOS Typewriter Crashes system
31422
31423 Time: While system is running.
31424
31425 Meaning: This indicates a logic error in the supervisor or
31426 CPU or memory hardware problems.
31427
31428 Action: Follow normal recovery procedures.
31429
31430
31431
31432
31433
31434
31435
31436
31437 pxss -542- MR12.5 10/27/92^L
31438
31439
31440 pxss.alm
31441 pxss: APTE disdains all processors
31442
31443 Stream: BOS Typewriter Crashes system
31444
31445 Time: While system is running.
31446
31447 Meaning: This indicates a logic error in the supervisor or
31448 CPU or memory hardware problems. " There are no
31449 processors-required set for this APTE.
31450
31451 Action: Follow normal recovery procedures.
31452
31453
31454
31455
31456
31457
31458 pxss.alm
31459 pxss: APTE not locked
31460
31461 Stream: BOS Typewriter Crashes system
31462
31463 Time: While system is running.
31464
31465 Meaning: This indicates a logic error in the supervisor or
31466 CPU or memory hardware problems.
31467
31468 Action: Follow normal recovery procedures.
31469
31470
31471
31472
31473
31474
31475 pxss.alm
31476 pxss: apte.state ^= ready
31477
31478 Stream: BOS Typewriter Crashes system
31479
31480 Time: While system is running.
31481
31482 Meaning: This indicates a logic error in the supervisor or
31483 CPU or memory hardware problems.
31484
31485 Action: Follow normal recovery procedures.
31486
31487
31488
31489
31490
31491
31492
31493
31494
31495 pxss -543- MR12.5 10/27/92^L
31496
31497
31498 pxss.alm
31499 pxss: empty_t APTE not stopped or empty
31500
31501 Stream: BOS Typewriter Crashes system
31502
31503 Time: While system is running.
31504
31505 Meaning: This indicates a logic error in the supervisor or
31506 CPU or memory hardware problems. " an attempt was
31507 made to clear an APTE that of a process that was
31508 neither " stopped nor empty.
31509
31510 Action: Follow normal recovery procedures.
31511
31512
31513
31514
31515
31516
31517 pxss.alm
31518 pxss: freeing unknown stack_0
31519
31520 Stream: BOS Typewriter Crashes system
31521
31522 Time: While system is running.
31523
31524 Meaning: This indicates a logic error in the supervisor or
31525 CPU or memory hardware problems. " the stack_0
31526 being returned could not be found in the list of
31527 stack_0s.
31528
31529 Action: Follow normal recovery procedures.
31530
31531
31532
31533
31534
31535
31536 pxss.alm
31537 pxss: ITT overflows
31538
31539 Stream: BOS Typewriter Crashes system
31540
31541 Time: While system is running.
31542
31543 Meaning: This indicates a logic error in the supervisor or
31544 CPU or memory hardware problems.
31545
31546 Action: Follow normal recovery procedures.
31547
31548
31549
31550
31551
31552
31553 pxss -544- MR12.5 10/27/92^L
31554
31555
31556 pxss.alm
31557 pxss: lock_stack_queue stac failed
31558
31559 Stream: BOS Typewriter Crashes system
31560
31561 Time: While system is running.
31562
31563 Meaning: This indicates a logic error in the supervisor or
31564 CPU or memory hardware problems. " This indicates
31565 a hardware error.
31566
31567 Action: Follow normal recovery procedures.
31568
31569
31570
31571
31572
31573
31574 pxss.alm
31575 pxss: mylock on stack queue
31576
31577 Stream: BOS Typewriter Crashes system
31578
31579 Time: While system is running.
31580
31581 Meaning: This indicates a logic error in the supervisor or
31582 CPU or memory hardware problems.
31583
31584 Action: Follow normal recovery procedures.
31585
31586
31587
31588
31589
31590
31591 pxss.alm
31592 pxss: no available stack_0
31593
31594 Stream: BOS Typewriter Crashes system
31595
31596 Time: While system is running.
31597
31598 Meaning: This indicates a logic error in the supervisor or
31599 CPU or memory hardware problems.
31600
31601 Action: Follow normal recovery procedures.
31602
31603
31604
31605
31606
31607
31608
31609
31610
31611 pxss -545- MR12.5 10/27/92^L
31612
31613
31614 pxss.alm
31615 pxss: no stack_0 sdw
31616
31617 Stream: BOS Typewriter Crashes system
31618
31619 Time: While system is running.
31620
31621 Meaning: This indicates a logic error in the supervisor or
31622 CPU or memory hardware problems.
31623
31624 Action: Follow normal recovery procedures.
31625
31626
31627
31628
31629
31630
31631 pxss.alm
31632 pxss: No term_processid
31633
31634 Stream: BOS Typewriter Crashes system
31635
31636 Time: While system is running.
31637
31638 Meaning: This indicates a logic error in the supervisor or
31639 CPU or memory hardware problems. " As a process
31640 was about to indicate its demise to the master
31641 process " it discovered to its chagrin that it
31642 had forgotten who that was.
31643
31644 Action: Follow normal recovery procedures.
31645
31646
31647
31648
31649
31650
31651
31652
31653
31654
31655
31656
31657
31658
31659
31660
31661
31662
31663
31664
31665
31666
31667
31668
31669 pxss -546- MR12.5 10/27/92^L
31670
31671
31672 pxss.alm
31673 pxss: notify time out: event=ZZZZZZZZZZZZ.
31674 During init/shutdown.
31675
31676
31677 Stream: BOS Typewriter.
31678
31679 Time: System Intialization.
31680
31681 Meaning: A hardcore event has not occurred within a
31682 reasonable time during system initialization or
31683 shutdown. This may be due to hardware problems or
31684 to a programming error. The system attempts to
31685 continue initialization or shutdown.
31686
31687 Action: If this message persists contact system
31688 programmers.
31689
31690
31691
31692 pxss.alm
31693 pxss: notify time out: event=ZZZZZZZZZZZZ
31694 pid=XXXXXXXXXXXX
31695
31696
31697 Stream: BOS Typewriter.
31698
31699 Time: While system is running.
31700
31701 Meaning: A hardcore event has not occurred within a
31702 reasonable time. This may be due to hardware
31703 problems or to a programming error. The system
31704 attempts to continue operation.
31705
31706 Action: If this message persists contact system
31707 programmers.
31708
31709
31710
31711 pxss.alm
31712 pxss: sprq already on prds
31713
31714 Stream: BOS Typewriter Crashes system
31715
31716 Time: While system is running.
31717
31718 Meaning: This indicates a logic error in the supervisor or
31719 CPU or memory hardware problems.
31720
31721 Action: Follow normal recovery procedures.
31722
31723
31724
31725
31726
31727 pxss -547- MR12.5 10/27/92^L
31728
31729
31730 pxss.alm
31731 pxss: stack_0 page 0 wired
31732
31733 Stream: BOS Typewriter Crashes system
31734
31735 Time: While system is running.
31736
31737 Meaning: This indicates a logic error in the supervisor or
31738 CPU or memory hardware problems. " process
31739 loading was about to wire the first page of the
31740 ring 0 stack when " it discovered that it had been
31741 beaten to the punch.
31742
31743 Action: Follow normal recovery procedures.
31744
31745
31746
31747
31748
31749
31750 pxss.alm
31751 pxss: Stop returned from getwork
31752
31753 Stream: BOS Typewriter Crashes system
31754
31755 Time: While system is running.
31756
31757 Meaning: This indicates a logic error in the supervisor or
31758 CPU or memory hardware problems.
31759
31760 Action: Follow normal recovery procedures.
31761
31762
31763
31764
31765
31766
31767 pxss.alm
31768 pxss: subroutine_save stack overflow
31769
31770 Stream: BOS Typewriter Crashes system
31771
31772 Time: While system is running.
31773
31774 Meaning: This indicates a logic error in the supervisor or
31775 CPU or memory hardware problems.
31776
31777 Action: Follow normal recovery procedures.
31778
31779
31780
31781
31782
31783
31784
31785 pxss -548- MR12.5 10/27/92^L
31786
31787
31788 pxss.alm
31789 pxss: System default procs required reset to
31790 ABCDEFGH
31791
31792
31793 Stream: BOS Typewriter sounds beeper
31794
31795 Time: During CPU deconfiguration.
31796
31797 Meaning: Due to the deletion of a CPU there were no online
31798 CPUs remaining in the default set of CPUs. These
31799 CPUs are the only CPUs on which processes can run
31800 which have not requested to be run on specific
31801 CPUs. The default set of CPUs has been changed to
31802 all online CPUs.
31803
31804 Action: Contact the system administrator.
31805
31806
31807
31808 pxss.alm
31809 pxss: thread_him_in already threaded
31810
31811 Stream: BOS Typewriter Crashes system
31812
31813 Time: While system is running.
31814
31815 Meaning: This indicates a logic error in the supervisor or
31816 CPU or memory hardware problems.
31817
31818 Action: Follow normal recovery procedures.
31819
31820
31821
31822
31823
31824
31825 pxss.alm
31826 pxss: thread_him_in x0 zero
31827
31828 Stream: BOS Typewriter Crashes system
31829
31830 Time: While system is running.
31831
31832 Meaning: This indicates a logic error in the supervisor or
31833 CPU or memory hardware problems.
31834
31835 Action: Follow normal recovery procedures.
31836
31837
31838
31839
31840
31841
31842
31843 pxss -549- MR12.5 10/27/92^L
31844
31845
31846 pxss.alm
31847 pxss: thread_him_in x1 zero
31848
31849 Stream: BOS Typewriter Crashes system
31850
31851 Time: While system is running.
31852
31853 Meaning: This indicates a logic error in the supervisor or
31854 CPU or memory hardware problems.
31855
31856 Action: Follow normal recovery procedures.
31857
31858
31859
31860
31861
31862
31863 pxss.alm
31864 pxss: thread_him_in x4 zero
31865
31866 Stream: BOS Typewriter Crashes system
31867
31868 Time: While system is running.
31869
31870 Meaning: This indicates a logic error in the supervisor or
31871 CPU or memory hardware problems.
31872
31873 Action: Follow normal recovery procedures.
31874
31875
31876
31877
31878
31879
31880 pxss.alm
31881 pxss: thread_him_in x4->apte.fp ^= x1
31882
31883 Stream: BOS Typewriter Crashes system
31884
31885 Time: While system is running.
31886
31887 Meaning: This indicates a logic error in the supervisor or
31888 CPU or memory hardware problems.
31889
31890 Action: Follow normal recovery procedures.
31891
31892
31893
31894
31895
31896
31897
31898
31899
31900
31901 pxss -550- MR12.5 10/27/92^L
31902
31903
31904 pxss.alm
31905 pxss: unlock apt read lock bad count
31906
31907 Stream: BOS Typewriter Crashes system
31908
31909 Time: While system is running.
31910
31911 Meaning: This indicates a logic error in the supervisor or
31912 CPU or memory hardware problems.
31913
31914 Action: Follow normal recovery procedures.
31915
31916
31917
31918
31919
31920
31921 pxss.alm
31922 pxss: UNLOCK_bp not locked
31923
31924 Stream: BOS Typewriter Crashes system
31925
31926 Time: While system is running.
31927
31928 Meaning: This indicates a logic error in the supervisor or
31929 CPU or memory hardware problems.
31930
31931 Action: Follow normal recovery procedures.
31932
31933
31934
31935
31936
31937
31938 pxss.alm
31939 pxss: unlock_stack_queue not my lock
31940
31941 Stream: BOS Typewriter Crashes system
31942
31943 Time: While system is running.
31944
31945 Meaning: This indicates a logic error in the supervisor or
31946 CPU or memory hardware problems.
31947
31948 Action: Follow normal recovery procedures.
31949
31950
31951
31952
31953
31954
31955
31956
31957
31958
31959 pxss -551- MR12.5 10/27/92^L
31960
31961
31962 pxss.alm
31963 pxss: unlock_stack_queue stacq failed
31964
31965 Stream: BOS Typewriter Crashes system
31966
31967 Time: While system is running.
31968
31969 Meaning: This indicates a logic error in the supervisor or
31970 CPU or memory hardware problems. " This indicates
31971 a hardware error.
31972
31973 Action: Follow normal recovery procedures.
31974
31975
31976
31977
31978
31979
31980 pxss.alm
31981 pxss: UNLOCK_X2 not locked
31982
31983 Stream: BOS Typewriter Crashes system
31984
31985 Time: While system is running.
31986
31987 Meaning: This indicates a logic error in the supervisor or
31988 CPU or memory hardware problems.
31989
31990 Action: Follow normal recovery procedures.
31991
31992
31993
31994
31995
31996
31997 pxss.alm
31998 pxss: UNLOCK_x3 not locked
31999
32000 Stream: BOS Typewriter Crashes system
32001
32002 Time: While system is running.
32003
32004 Meaning: This indicates a logic error in the supervisor or
32005 CPU or memory hardware problems.
32006
32007 Action: Follow normal recovery procedures.
32008
32009
32010
32011
32012
32013
32014
32015
32016
32017 pxss -552- MR12.5 10/27/92^L
32018
32019
32020 pxss.alm
32021 pxss: untenable blocked APTE
32022
32023 Stream: BOS Typewriter Crashes system
32024
32025 Time: While system is running.
32026
32027 Meaning: This indicates a logic error in the supervisor or
32028 CPU or memory hardware problems.
32029
32030 Action: Follow normal recovery procedures.
32031
32032
32033
32034
32035
32036
32037 pxss.alm
32038 pxss: untenable empty APTE
32039
32040 Stream: BOS Typewriter Crashes system
32041
32042 Time: While system is running.
32043
32044 Meaning: This indicates a logic error in the supervisor or
32045 CPU or memory hardware problems.
32046
32047 Action: Follow normal recovery procedures.
32048
32049
32050
32051
32052
32053
32054 pxss.alm
32055 pxss: untenable stopped APTE
32056
32057 Stream: BOS Typewriter Crashes system
32058
32059 Time: While system is running.
32060
32061 Meaning: This indicates a logic error in the supervisor or
32062 CPU or memory hardware problems.
32063
32064 Action: Follow normal recovery procedures.
32065
32066
32067
32068
32069
32070
32071
32072
32073
32074
32075 pxss -553- MR12.5 10/27/92^L
32076
32077
32078 pxss.alm
32079 pxss: unthread null back ptr
32080
32081 Stream: BOS Typewriter Crashes system
32082
32083 Time: While system is running.
32084
32085 Meaning: This indicates a logic error in the supervisor or
32086 CPU or memory hardware problems.
32087
32088 Action: Follow normal recovery procedures.
32089
32090
32091
32092
32093
32094
32095 pxss.alm
32096 pxss: unthread null cur.fp
32097
32098 Stream: BOS Typewriter Crashes system
32099
32100 Time: While system is running.
32101
32102 Meaning: This indicates a logic error in the supervisor or
32103 CPU or memory hardware problems.
32104
32105 Action: Follow normal recovery procedures.
32106
32107
32108
32109
32110
32111
32112 pxss.alm
32113 pxss: unthread prev.fp ^= cur
32114
32115 Stream: BOS Typewriter Crashes system
32116
32117 Time: While system is running.
32118
32119 Meaning: This indicates a logic error in the supervisor or
32120 CPU or memory hardware problems.
32121
32122 Action: Follow normal recovery procedures.
32123
32124
32125
32126
32127
32128
32129
32130
32131
32132
32133 pxss -554- MR12.5 10/27/92^L
32134
32135
32136 pxss.alm
32137 pxss: write_to_read bad lock count
32138
32139 Stream: BOS Typewriter Crashes system
32140
32141 Time: While system is running.
32142
32143 Meaning: This indicates a logic error in the supervisor or
32144 CPU or memory hardware problems.
32145
32146 Action: Follow normal recovery procedures.
32147
32148
32149
32150
32151
32152
32153 pxss.alm
32154 pxss: write_to_read ldac failed
32155
32156 Stream: BOS Typewriter Crashes system
32157
32158 Time: While system is running.
32159
32160 Meaning: This indicates a logic error in the supervisor or
32161 CPU or memory hardware problems. " This indicates
32162 a hardware error.
32163
32164 Action: Follow normal recovery procedures.
32165
32166
32167
32168
32169
32170
32171 rcp_control_.pl1
32172 RCP: Acquired DEVICE from storage system.
32173
32174
32175 Stream: BOS Typewriter.
32176
32177 Time: In response to an operator command.
32178
32179 Meaning: The operator has used the set_drive_usage command
32180 to make DRIVE an IO drive.
32181
32182 Action: No operator action is required.
32183
32184
32185
32186
32187
32188
32189
32190
32191 RCP -555- MR12.5 10/27/92^L
32192
32193
32194 rcp_control_.pl1
32195 RCP: Added device DEVICE
32196
32197
32198 Stream: BOS Typewriter.
32199
32200 Time: In response to an operator command.
32201
32202 Meaning: The operator has added a user I/O disk drive with
32203 adddev.
32204
32205 Action: No operator action is required.
32206
32207
32208
32209 rcp_reserve_.pl1
32210 RCP: An error locking rcpd for reservation for
32211 RESERVED_FOR
32212 by RESERVER if they're not the same
32213 id=RES_ID.
32214
32215
32216 Stream: Logged in SYSERR log.
32217
32218 Time: While system is running.
32219
32220 Meaning: An error was found in the locking data for the
32221 resource.
32222
32223 Action: No operator action is required.
32224
32225
32226
32227 rcp_control_.pl1
32228 RCP: Assigned DEVICE to PERSON.PROJ.T
32229
32230
32231 Stream: Logged in SYSERR log.
32232
32233 Time: While system is running.
32234
32235 Meaning: DEVICE has been assigned to a user process.
32236
32237 Action: No operator action is required.
32238
32239
32240
32241
32242
32243
32244
32245
32246
32247
32248
32249 RCP -556- MR12.5 10/27/92^L
32250
32251
32252 rcp_ioi_attach_.pl1
32253 RCP: Attached DEVICE for PERSON.PROJ.T
32254
32255
32256 Stream: BOS Typewriter.
32257
32258 Time: While system is running.
32259
32260 Meaning: The device DEVICE has been attached by the user
32261 process.
32262
32263 Action: No operator action is required.
32264
32265
32266
32267 rcp_disk_.pl1
32268 RCP: Authenticate DRIVE for PERSON.PROJ.T.
32269 RCP: It has LABEL_TYPE label NAME.
32270 RCP: All N subvolume labels are unreadable.
32271 RCP: VOL_NAME on subvol a VOL_NAME on subvol b
32272 VOL_NAME on subvol c.
32273 RCP: User requested volume DIFFERENT_NAME.
32274
32275
32276 Stream: BOS Typewriter sounds beeper
32277
32278 Time: While system is running.
32279
32280 Meaning: The operator must verify that the correct pack is
32281 mounted on DRIVE. If the DIFFERENT_NAME message
32282 indicates that the label on the pack NAME is
32283 different from the user's request then special
32284 instructions from the system administrator must be
32285 followed.
32286
32287 Action: If the pack is correct then use the "x auth"
32288 function to input the DRIVE and the authentication
32289 code which matches LABEL_TYPE: "ss" for "Storage
32290 System" or "copy of Storage System"; "io" for
32291 "IO"; "urd" for "UnReaDable"; or "urg" for
32292 "UnReGistered". If the wrong pack is mounted then
32293 use the authentication code "no".
32294
32295
32296
32297
32298
32299
32300
32301
32302
32303
32304
32305
32306
32307 RCP -557- MR12.5 10/27/92^L
32308
32309
32310 rcp_tape_.pl1
32311 RCP: Authenticate DRIVE. It has LABEL_TYPE label
32312 LABEL and is UNREGISTERED.
32313
32314
32315 Stream: BOS Typewriter sounds beeper
32316
32317 Time: While system is running.
32318
32319 Meaning: The tape volume requested is not a registered tape
32320 volume. In addittion the system may not have
32321 been able to determine that the volume loaded is
32322 in fact the one requested. The label read from
32323 the tape on DEVICE was of type LABEL_TYPE and was
32324 LABEL. If LABEL is "Manual Halt" this indicates
32325 that the tape drive was found in standby while
32326 trying to read/verify the label. Any
32327 non-printable characters in the label are
32328 represented by ".".
32329
32330 Action: If the volume is correct and is to be registered
32331 to the user requesting this attachment use the "x
32332 auth" function to input the DRIVE number and the
32333 authentication code on the tape volume or "***"
32334 if there is no authentication code. If
32335 authentication was requested due to the drive
32336 being in standby the tape should be rewound
32337 manually and rereadied manually and the above
32338 procedure for authentication followed.
32339
32340
32341
32342
32343
32344
32345
32346
32347
32348
32349
32350
32351
32352
32353
32354
32355
32356
32357
32358
32359
32360
32361
32362
32363
32364
32365 RCP -558- MR12.5 10/27/92^L
32366
32367
32368 rcp_tape_.pl1
32369 RCP: Authenticate DRIVE. It has LABEL_TYPE label
32370 LABEL.
32371
32372
32373 Stream: BOS Typewriter sounds beeper
32374
32375 Time: While system is running.
32376
32377 Meaning: The system cannot determine that the volume on
32378 DRIVE is the one requested. The operator must
32379 authenticate the volume. The label read from the
32380 tape on DEVICE was of type LABEL_TYPE and was
32381 LABEL. If LABEL is "Manual Halt" this indicates
32382 that the tape drive was found in standby while
32383 trying to read/verify the label. If LABEL_TYPE is
32384 ANSI and LABEL is "<label> with non-blank
32385 accessibility code" this indicates that the label
32386 is an ANSI label with a non-blank character in the
32387 accessibility field the operator must consult the
32388 site standards for authenticating such tapes
32389 before doing the authentication. Any
32390 non-printable characters in the label are
32391 represented by ".".
32392
32393 Action: If the volume is correct then use the "x auth"
32394 function to input the DRIVE number and the
32395 authentication code on the tape volume or "***"
32396 if there is no authentication code. If
32397 authentication was requested due to the drive
32398 being in standby the tape should be rewound
32399 manually and rereadied manually and the above
32400 procedure for authentication followed.
32401
32402
32403
32404 rcp_tape_.pl1
32405 RCP: Authentication code for DRIVE does not
32406 match.
32407
32408
32409 Stream: BOS Typewriter.
32410
32411 Time: While system is running.
32412
32413 Meaning: The authentication code typed for the volume on
32414 DRIVE does no match the user specified volume
32415 name.
32416
32417 Action: No operator action is required.
32418
32419
32420
32421
32422
32423 RCP -559- MR12.5 10/27/92^L
32424
32425
32426 rcp_disk_.pl1
32427 RCP: Authentication denied for DRIVE
32428
32429
32430 Stream: BOS Typewriter sounds beeper
32431
32432 Time: While system is running.
32433
32434 Meaning: The operator has denied authentication for DRIVE.
32435
32436 Action: No operator action is required.
32437
32438
32439
32440 rcp_ring1_init_.pl1
32441 RCP: Auto Registration is enabled without Exact
32442 Authentication required. This could lead to
32443 errors in automatic registration of volumes.
32444
32445
32446 Stream: BOS Typewriter sounds beeper
32447
32448 Time: While system is running.
32449
32450 Meaning: This is a warning. If the system is operated with
32451 auto registration enabled and exact authentication
32452 of tape volumes is not required there is a better
32453 chance of errors occurring in the registration of
32454 tape volumes. Again it is very important to make
32455 sure the volume mounted is the proper one for the
32456 request if auto registration is enabled.
32457
32458 Action: No operator action is required.
32459
32460
32461
32462 rcp_cancel_id_.pl1
32463 RCP: Cancelled device devX_MM for GRP_ID
32464 id=RES_ID
32465
32466
32467 Stream: Logged in SYSERR log.
32468
32469 Time: While system is running.
32470
32471 Meaning: A device reservation has been cancelled by the
32472 operator the
32473 absentee manager or the Initializer.
32474
32475 Action: No operator action is required.
32476
32477
32478
32479
32480
32481 RCP -560- MR12.5 10/27/92^L
32482
32483
32484 rcp_reserve_.pl1
32485 RCP: Cancelled device devX_MM for GRP_ID
32486 id=RES_ID
32487
32488
32489 Stream: Logged in SYSERR log.
32490
32491 Time: While system is running.
32492
32493 Meaning: The reservation for the named device has been
32494 cancelled.
32495
32496 Action: No operator action is required.
32497
32498
32499
32500 rcp_cancel_id_.pl1
32501 RCP: Cancelled volume volume_name for GRP_ID
32502 id=RES_ID
32503
32504
32505 Stream: Logged in SYSERR log.
32506
32507 Time: While system is running.
32508
32509 Meaning: A volume reservation has been cancelled by the
32510 operator the
32511 absentee manager or the Initializer.
32512
32513 Action: No operator action is required.
32514
32515
32516
32517 rcp_reserve_.pl1
32518 RCP: Cancelled volume volume_name for GRP_ID
32519 id=RES_ID
32520
32521
32522 Stream: Logged in SYSERR log.
32523
32524 Time: While system is running.
32525
32526 Meaning: The reservation for the named volume has been
32527 cancelled.
32528
32529 Action: No operator action is required.
32530
32531
32532
32533
32534
32535
32536
32537
32538
32539 RCP -561- MR12.5 10/27/92^L
32540
32541
32542 rcprm_journalize_.pl1
32543 RCP: Cannot initiate journal PATH. ERROR_CODE
32544
32545
32546 Stream: BOS Typewriter sounds beeper
32547
32548 Time: While system is running.
32549
32550 Meaning: The RCP journal at PATH has been damaged or is
32551 missing.
32552
32553 Action: Contact the system programming staff.
32554
32555
32556
32557 wdx.pl1
32558 RCP: Check mount of logical volume LVNAME for
32559 PROCESSNAME
32560 PVNAME1DRIVE1 ...
32561
32562
32563 Stream: BOS Typewriter sounds beeper
32564
32565 Time: While system is running.
32566
32567 Meaning: A user PROCESSNAME previously requested the
32568 attachment of logical volume LVNAME. The mount
32569 has not been accomplished in a 4 minutes. All
32570 required physical volumes are specified PVNAMEi
32571 DRIVEi.
32572
32573 Action: Mount the required physical volumes using the
32574 add_vol command to indicate when each has been
32575 made ready. The user process will continue when
32576 the last volume has been mounted. If the volume
32577 cannot be mounted use the del_lv command to
32578 indicate this fact and the user process will
32579 receive an error indication.
32580
32581
32582
32583
32584
32585
32586
32587
32588
32589
32590
32591
32592
32593
32594
32595
32596
32597 RCP -562- MR12.5 10/27/92^L
32598
32599
32600 rcp_mount_timer_.pl1
32601 RCP: Check Mount of REELID for writing on DRIVE
32602 for PERSON.PROJ.T
32603
32604
32605 Stream: BOS Typewriter sounds beeper
32606
32607 Time: While system is running.
32608
32609 Meaning: The request to mount tape reel REELID has been
32610 unsatisfied for over 4 minutes.
32611
32612 Action: Mount the reel or use "x deny" to inform the user
32613 that the reel cannot be mounted.
32614
32615
32616
32617 rcp_control_.pl1
32618 RCP: Consigned DEVICE to storage system.
32619
32620
32621 Stream: BOS Typewriter.
32622
32623 Time: In response to an operator command.
32624
32625 Meaning: The operator has used the set_drive_usage command
32626 to make DRIVE a storage system drive.
32627
32628 Action: No operator action is required.
32629
32630
32631
32632 rcp_ring1_init_.pl1
32633 RCP: Created DIR with default access.
32634
32635
32636 Stream: BOS Typewriter sounds beeper
32637
32638 Time: While system is running.
32639
32640 Meaning: The directory usually >system_control_1>rcp was
32641 created because it was not found at startup. It
32642 may have been destroyed in a crash. This message
32643 is normal during a cold boot of the Multics
32644 hierarchy.
32645
32646 Action: If users other than system processes should have
32647 access to the directory the system administrator
32648 must set the ACL appropriately.
32649
32650
32651
32652
32653
32654
32655 RCP -563- MR12.5 10/27/92^L
32656
32657
32658 rcp_ring1_init_.pl1
32659 RCP: Created DIR>DEVICE.acs with default access.
32660
32661
32662 Stream: BOS Typewriter sounds beeper
32663
32664 Time: While system is running.
32665
32666 Meaning: The system has created an access control segment
32667 for DEVICE because one was not found at startup.
32668 It may have been destroyed in a crash. This
32669 message is normal during the first use of a device
32670 on the system and at cold boot.
32671
32672 Action: If users other than system processes should have
32673 access to DEVICE the system administrator must
32674 set the ACL of DEVICE.acs appropriately.
32675
32676
32677
32678 rcprm_journalize_.pl1
32679 RCP: Creating DIRNAME>rcprm.journal
32680
32681
32682 Stream: BOS Typewriter.
32683
32684 Time: While system is running.
32685
32686 Meaning: Printed by RCP Resource Management when first
32687 enabled.
32688
32689 Action: No operator action is required.
32690
32691
32692
32693 rcp_control_.pl1
32694 RCP: Deleted device DEVICE
32695
32696
32697 Stream: BOS Typewriter.
32698
32699 Time: In response to an operator command.
32700
32701 Meaning: The operator has deleted user I/O disk DRIVE with
32702 deldev.
32703
32704 Action: No operator action is required.
32705
32706
32707
32708
32709
32710
32711
32712
32713 RCP -564- MR12.5 10/27/92^L
32714
32715
32716 rcp_detach_.pl1
32717 RCP: Detached DEVICE from PERSON.PROJ.T
32718
32719
32720 Stream: BOS Typewriter.
32721
32722 Time: While system is running.
32723
32724 Meaning: The user of DEVICE has detached it.
32725
32726 Action: If DEVICE is a disk drive demount the volume on
32727 it and store it in the library.
32728
32729
32730
32731 rcp_control_.pl1
32732 RCP: DEVICE is not operational and has not been
32733 added.
32734
32735
32736 Stream: BOS Typewriter.
32737
32738 Time: In response to an operator command.
32739
32740 Meaning: An attempt was made to add a non-operational
32741 device with adddev.
32742
32743 Action: Ready the device and add it again.
32744
32745
32746
32747 rcp_ring1_init_.pl1
32748 RCP: Error creating ACS DEVICE.acs:
32749 ERROR_MESSAGE
32750
32751
32752 Stream: BOS Typewriter sounds beeper
32753
32754 Time: While system is running.
32755
32756 Meaning: The system was unable to create an access control
32757 segment for DEVICE. No user will be able to
32758 attach it.
32759
32760 Action: Contact the system programming staff.
32761
32762
32763
32764
32765
32766
32767
32768
32769
32770
32771 RCP -565- MR12.5 10/27/92^L
32772
32773
32774 rcp_ring1_init_.pl1
32775 RCP: Error creating DIR: ERROR_MESSAGE
32776
32777
32778 Stream: BOS Typewriter sounds beeper
32779
32780 Time: While system is running.
32781
32782 Meaning: The system was unable to create the ACS directory.
32783 It should be >system_control_1>acs. The system
32784 may be unable to use I/O devices.
32785
32786 Action: Contact the system programming staff.
32787
32788
32789
32790 rcprm_journalize_.pl1
32791 RCP: Error during registry reconstruction for
32792 USERID. RCP: Could not OPERATION RESOURCE_TYPE
32793 RESOURCE_NAME may occur multiple times RCP: End
32794 of reconstruction operation.
32795
32796
32797 Stream: BOS Typewriter sounds beeper
32798
32799
32800 Time: This message should only occur during a special
32801 session. The second message in the series may
32802 occur multiple times.
32803
32804 Meaning: The specified RCP Resource Management activity
32805 failed to be re-performed during an attempt to
32806 reconstruct the registries by the System
32807 Administrator. This indicates a logic error in
32808 the supervisor or CPU or memory hardware
32809 problems.
32810
32811 Action: Contact the system administrator.
32812
32813
32814
32815
32816
32817
32818
32819
32820
32821
32822
32823
32824
32825
32826
32827
32828
32829 RCP -566- MR12.5 10/27/92^L
32830
32831
32832 rcp_ring1_init_.pl1
32833 RCP: Error expanding DIR: ERROR_MESSAGE
32834
32835
32836 Stream: BOS Typewriter sounds beeper
32837
32838 Time: While system is running.
32839
32840 Meaning: The pathname of the acs directory is incorrect.
32841 It should be >system_control_1>acs. This
32842 indicates a logic error in the supervisor or CPU
32843 or memory hardware problems. The system may be
32844 unable to use I/O devices.
32845
32846 Action: Contact the system programming staff.
32847
32848
32849
32850 rcp_ring1_init_.pl1
32851 RCP: Error setting max length of DEVICE.acs:
32852 ERROR_MESSAGE
32853
32854
32855 Stream: BOS Typewriter sounds beeper
32856
32857 Time: While system is running.
32858
32859 Meaning: This indicates a logic error in the supervisor or
32860 CPU or memory hardware problems.
32861
32862 Action: Contact the system programming staff.
32863
32864
32865
32866 rcp_detach_.pl1
32867 RCP: Errors DEVICE = NN
32868
32869
32870 Stream: BOS Typewriter.
32871
32872 Time: While system is running.
32873
32874 Meaning: When DEVICE was detached its error counter was
32875 nonzero. This may be due to a problem with DEVICE
32876 or with the user program.
32877
32878 Action: No operator action is required.
32879
32880
32881
32882
32883
32884
32885
32886
32887 RCP -567- MR12.5 10/27/92^L
32888
32889
32890 rcp_detach_.pl1
32891 RCP: Errors DEVICE volume VOL = NN
32892
32893
32894 Stream: BOS Typewriter.
32895
32896 Time: While system is running.
32897
32898 Meaning: When DEVICE was detached its error counter was
32899 nonzero. The errors may be due to a problem with
32900 DEVICE with the volume VOLUME or with the user
32901 program.
32902
32903 Action: No operator action is required.
32904
32905
32906
32907 rcp_detach_.pl1
32908 RCP: Force Detached DEVICE from PERSON.PROJ.T
32909
32910
32911 Stream: BOS Typewriter.
32912
32913 Time: While system is running.
32914
32915 Meaning: The user PERSON.PROJ.T has terminated abnormally.
32916 This may be due to an automatic logout or a
32917 process termination.
32918
32919 Action: If DEVICE is a disk drive demount the volume on
32920 it and store it in the library.
32921
32922
32923
32924 rcp_control_.pl1
32925 RCP: Force Unassigned DEVICE from PERSON.PROJ.T
32926
32927
32928 Stream: BOS Typewriter.
32929
32930 Time: While system is running.
32931
32932 Meaning: The user process PERSON.PROJ.T has terminated and
32933 its resources have been freed. Or the operator
32934 may have forced the unassignment of DRIVE.
32935
32936 Action: No operator action is required.
32937
32938
32939
32940
32941
32942
32943
32944
32945 RCP -568- MR12.5 10/27/92^L
32946
32947
32948 rcprm_journalize_.pl1
32949 RCP: Journal could not be forcibly written.
32950 ERROR CODE
32951
32952
32953 Stream: BOS Typewriter.
32954
32955 Time: While system is running.
32956
32957 Meaning: A force-write to disk of the RCP journal failed.
32958 This indicates a logic error in the supervisor or
32959 CPU or memory hardware problems.
32960
32961 Action: Contact the system programming staff.
32962
32963
32964
32965 rcprm_journalize_.pl1
32966 RCP: Journal lost transaction for USERID.
32967 ERROR_CODE
32968
32969
32970 Stream: BOS Typewriter sounds beeper
32971
32972 Time: While system is running.
32973
32974 Meaning: Some RCP Resource Management activity while
32975 successfully completed was not properly
32976 journalized for recovery purposes. Subsequently
32977 if the registries become damaged before they are
32978 safely copied by the System Administrator this
32979 activity will be lost.
32980
32981 Action: Contact the system administrator.
32982
32983
32984
32985 rcp_detach_.pl1
32986 RCP: Manually unload volume VOLUME from device
32987 DEVICE
32988
32989
32990 Stream: BOS Typewriter sounds beeper
32991
32992 Time: While system is running.
32993
32994 Meaning: RCP could not unload the specified volume from the
32995 device on which it was loaded.
32996
32997 Action: Manually unload the volume from the device and
32998 return the volume to the library for storage.
32999
33000
33001
33002
33003 RCP -569- MR12.5 10/27/92^L
33004
33005
33006 rcp_unload_.pl1
33007 RCP: Manually unload volume VOLUME from device
33008 DEVICE
33009
33010
33011 Stream: BOS Typewriter sounds beeper
33012
33013 Time: While system is running.
33014
33015 Meaning: RCP could not unload the specified volume from the
33016 device on which it was loaded.
33017
33018 Action: Manually unload the volume from the device and
33019 return the volume to the library for storage.
33020
33021
33022
33023 wdx.pl1
33024 RCP: Mount logical volume LVNAME for PROCESSNAME
33025
33026
33027 Stream: BOS Typewriter sounds beeper
33028
33029 Time: While system is running.
33030
33031 Meaning: A user PROCESSNAME has requested the attachment
33032 of logical volume LVNAME. It is not now mounted.
33033 The initializer will issue mount messages for all
33034 physical volumes needed.
33035
33036 Action: Mount the required physical volumes using the
33037 add_vol command to indicate when each has been
33038 made ready. The user process will continue when
33039 the last volume has been mounted. If the volume
33040 cannot be mounted use the del_lv command to
33041 indicate this fact and the user process will
33042 receive an error indication.
33043
33044
33045
33046 rcp_disk_.pl1
33047 RCP: Mount Pack PACK on DRIVE for PERSON.PROJ.T
33048
33049
33050 Stream: BOS Typewriter sounds beeper
33051
33052 Time: While system is running.
33053
33054 Meaning: The user PERSON.PROJ.T has requested the mounting
33055 of the user I/O pack named PACK on disk drive
33056 DRIVE.
33057
33058 Action: Mount the pack and make it ready.
33059
33060
33061 RCP -570- MR12.5 10/27/92^L
33062
33063
33064 rcp_disk_.pl1
33065 RCP: Mount Pack PACK without protect on DRIVE
33066 for PERSON.PROJ.T
33067
33068
33069 Stream: BOS Typewriter sounds beeper
33070
33071 Time: While system is running.
33072
33073 Meaning: The user PERSON.PROJ.T has requested the mounting
33074 of the user I/O pack named PACK on disk drive
33075 DRIVE.
33076
33077 Action: Mount the pack and make it ready. Set the PROTECT
33078 status as specified in the message.
33079
33080
33081
33082 rcp_message_.pl1
33083 RCP: Mount Reel REELID without ring on DRIVE
33084 for PERSON.PROJ.T switching volumes.
33085
33086
33087 Stream: BOS Typewriter sounds beeper
33088
33089 Time: While system is running.
33090
33091 Meaning: A user process has requested the mounting of tape
33092 reel REELID on drive DRIVE.
33093
33094 Action: Locate the requested reel. Check to make sure
33095 that the user PERSON.PROJ is allowed to use the
33096 reel. Insert or remove a write ring as specified.
33097 Mount the reel on the specified drive.
33098
33099 If the reel cannot be mounted either because it
33100 cannot be located access is incorrect or the
33101 drive is down use the "x deny" function to reject
33102 the mount request.
33103
33104
33105
33106
33107
33108
33109
33110
33111
33112
33113
33114
33115
33116
33117
33118
33119 RCP -571- MR12.5 10/27/92^L
33120
33121
33122 rcp_tape_.pl1
33123 RCP: Mount Reel REELID without ring on DRIVE
33124 for PERSON.PROJ.T.
33125
33126
33127 Stream: BOS Typewriter sounds beeper
33128
33129 Time: While system is running.
33130
33131 Meaning: A user process has requested the mounting of tape
33132 reel REELID on drive DRIVE.
33133
33134 Action: Locate the requested reel. Check to make sure
33135 that the user PERSON.PROJ is allowed to use the
33136 reel. Insert or remove a write ring as specified.
33137 Mount the reel on the specified drive.
33138
33139 If the reel cannot be mounted either because it
33140 cannot be located access is incorrect or the
33141 drive is down use the "x deny" function to reject
33142 the mount request.
33143
33144
33145
33146 rcp_disk_.pl1
33147 RCP: Mounted LABEL_TYPE volume NAME on DRIVE for
33148 user I/O.
33149
33150
33151 Stream: BOS Typewriter.
33152
33153 Time: While system is running.
33154
33155 Meaning: A user has mounted LABEL_TYPE volume NAME as a
33156 user I/O disk on DRIVE. The operator has
33157 authenticated the mount.
33158
33159 Action: No operator action is required.
33160
33161
33162
33163
33164
33165
33166
33167
33168
33169
33170
33171
33172
33173
33174
33175
33176
33177 RCP -572- MR12.5 10/27/92^L
33178
33179
33180 rcp_comment_.pl1
33181 RCP: Note DEVICE - COMMENT
33182
33183
33184 Stream: BOS Typewriter.
33185
33186 Time: While system is running.
33187
33188 Meaning: The user requesting the mounting of a tape or disk
33189 pack on device specified a comment string.
33190
33191 Action: Read the comment. It may describe special
33192 operator action such as where to find or send the
33193 volume.
33194
33195
33196
33197 rcprm_find_resource_.pl1
33198 RCP: Operator certified manual clearing of
33199 VOLUME. RCP: USERID certified manual clearing of
33200 VOLUME.
33201
33202
33203 Stream: BOS Typewriter.
33204
33205 Time: In response to an operator or administrator
33206 command.
33207
33208 Meaning: This message is printed for auditing purposes when
33209 site-madated destruction of data is accomplished.
33210
33211 Action: No operator action is required.
33212
33213
33214
33215 rcp_preload_.pl1
33216 RCP: Preload volume VOLUME on device DEVICE
33217
33218
33219 Stream: BOS Typewriter.
33220
33221 Time: While system is running.
33222
33223 Meaning: The operator request to preload has been accepted
33224 by RCP.
33225
33226 Action: Preload the volume in question on the specified
33227 device.
33228
33229
33230
33231
33232
33233
33234
33235 RCP -573- MR12.5 10/27/92^L
33236
33237
33238 rcprm_find_resource_.pl1
33239 RCP: Registries may be in an inconsistent state.
33240 ERROR_CODE
33241
33242
33243 Stream: BOS Typewriter sounds beeper
33244
33245 Time: While system is running.
33246
33247 Meaning: An RCP Resource Management transaction was not
33248 properly committed to the registries. This
33249 indicates a logic error in the supervisor or CPU
33250 or memory hardware problems.
33251
33252 Action: Contact the system programming staff.
33253
33254
33255
33256 rcp_disk_.pl1
33257 RCP: Rejected mount of LABEL_TYPE volume NAME for
33258 PERSON.PROJ.T
33259
33260
33261 Stream: BOS Typewriter.
33262
33263 Time: While system is running.
33264
33265 Meaning: A user has attempted to mount a storage-system
33266 format or unreadable LABEL_TYPE disk pack for
33267 user I/O without specifying the -sys parameter.
33268 Because this might interfere with later storage
33269 system use of the pack or compromise system
33270 security this action is not permitted. The
33271 user's request is rejected. This error could
33272 arise if an operator inadvertently mounted the
33273 wrong pack.
33274
33275 Action: No operator action is required.
33276
33277
33278
33279
33280
33281
33282
33283
33284
33285
33286
33287
33288
33289
33290
33291
33292
33293 RCP -574- MR12.5 10/27/92^L
33294
33295
33296 rcp_tape_.pl1
33297 RCP: Remount Reel REELID without ring on DRIVE.
33298
33299
33300 Stream: BOS Typewriter sounds beeper
33301
33302 Time: While system is running.
33303
33304 Meaning: The system found a write ring when one was not
33305 required or did not find one when one was needed.
33306 Or the authentication code did not match. The
33307 tape is unloaded.
33308
33309 Action: Correct the write ring status or mount the correct
33310 tape and reready the tape.
33311
33312
33313
33314 rcp_disk_.pl1
33315 RCP: Reready DRIVE
33316
33317
33318 Stream: BOS Typewriter sounds beeper
33319
33320 Time: While system is running.
33321
33322 Meaning: DRIVE is not ready.
33323
33324
33325 Action: Make the drive ready.
33326
33327
33328
33329 rcp_disk_.pl1
33330 RCP: Reready DRIVE without protect
33331
33332
33333 Stream: BOS Typewriter sounds beeper
33334
33335 Time: While system is running.
33336
33337 Meaning: DRIVE is not ready.
33338
33339
33340 Action: Make the drive ready.
33341
33342
33343
33344
33345
33346
33347
33348
33349
33350
33351 RCP -575- MR12.5 10/27/92^L
33352
33353
33354 rcp_tape_.pl1
33355 RCP: Reready DRIVE.
33356
33357
33358 Stream: BOS Typewriter sounds beeper
33359
33360 Time: While system is running.
33361
33362 Meaning: DRIVE has dropped out of ready status.
33363
33364 Action: Reready it.
33365
33366
33367
33368 rcp_tape_.pl1
33369 RCP: Reready Reel REELID on DRIVE for
33370 PERSON.PROJ.T.
33371
33372
33373 Stream: BOS Typewriter sounds beeper
33374
33375 Time: While system is running.
33376
33377 Meaning: A preloaded volume was not ready.
33378
33379 Action: Make the volume ready.
33380
33381
33382
33383 rcp_reserve_.pl1
33384 RCP: Reserved device devX_MM for RESERVER
33385 id=RES_ID
33386
33387
33388 Stream: Logged in SYSERR log.
33389
33390 Time: While system is running.
33391
33392 Meaning: Device devX_MM has been reserved for RESERVER.
33393
33394 Action: No operator action is required.
33395
33396
33397
33398
33399
33400
33401
33402
33403
33404
33405
33406
33407
33408
33409 RCP -576- MR12.5 10/27/92^L
33410
33411
33412 rcp_reserve_.pl1
33413 RCP: Reserved volume volume_name for RESERVER
33414 id=RES_ID
33415
33416
33417 Stream: Logged in SYSERR log.
33418
33419 Time: While system is running.
33420
33421 Meaning: Volume volume_name has been reserved for RESERVER.
33422
33423 Action: No operator action is required.
33424
33425
33426
33427 rcp_auto_register_.pl1
33428 RCP: RESOURCE_TYPE RESOURCE_NAME registered and
33429 acquired to USER.
33430
33431
33432 Stream: BOS Typewriter.
33433
33434 Time: While system is running.
33435
33436 Meaning: The resource RESOURCE_NAME has been automatically
33437 registered and acquired to USER. It is a resource
33438 of the type RESCOURCE_TYPE.
33439
33440 Action: No operator action is required.
33441
33442
33443
33444 rcprm_find_resource_.pl1
33445 RCP: Schedule VOLUME for manual clearing.
33446
33447
33448 Stream: BOS Typewriter sounds beeper
33449
33450 Time: While system is running.
33451
33452 Meaning: The data contained on VOLUME is to be destroyed by
33453 the operator via degaussing or other site-mandated
33454 method.
33455
33456 Action: The operator must erase the specified resource
33457 and must acknowledge when this has been done by
33458 issuing the clear_resource command or the
33459 appropriate site-defined "x" Initializer request.
33460
33461
33462
33463
33464
33465
33466
33467 RCP -577- MR12.5 10/27/92^L
33468
33469
33470 rcp_disk_.pl1
33471 RCP: Turn protect switch ON/OFF on drive DRIVE
33472 and then push Operator Interrupt on MPC
33473
33474
33475 Stream: BOS Typewriter sounds beeper
33476
33477 Time: While system is running.
33478
33479 Meaning: The PROTECT status was wrong for DRIVE.
33480
33481 Meaning: Correct the PROTECT status and push the Operator
33482 Interrupt button on the MPC.
33483
33484
33485
33486 rcp_control_.pl1
33487 RCP: Unassigned DEVICE from PERSON.PROJ.T
33488
33489
33490 Stream: Logged in SYSERR log.
33491
33492 Time: While system is running.
33493
33494 Meaning: PERSON.PROJ.T has released DRIVE normally.
33495
33496 Action: No operator action is required.
33497
33498
33499
33500 rcp_detach_.pl1
33501 RCP: Unloading volume VOLUME from device DEVICE
33502
33503
33504 Stream: BOS Typewriter.
33505
33506 Time: While system is running.
33507
33508 Meaning: The specified VOLUME is being demounted by RCP.
33509
33510 Action: Return the specified VOLUME to the library.
33511
33512
33513
33514
33515
33516
33517
33518
33519
33520
33521
33522
33523
33524
33525 RCP -578- MR12.5 10/27/92^L
33526
33527
33528 rcp_unload_.pl1
33529 RCP: Unloading volume VOLUME from device DEVICE
33530
33531
33532 Stream: BOS Typewriter.
33533
33534 Time: While system is running.
33535
33536 Meaning: The specified VOLUME is being demounted by RCP.
33537
33538 Action: Return the specified VOLUME to the library.
33539
33540
33541
33542 rcp_tape_.pl1
33543 RCP: Using Reel REELID on DRIVE for
33544 PERSON.PROJ.T.
33545
33546
33547 Stream: BOS Typewriter.
33548
33549 Time: While system is running.
33550
33551 Meaning: Using a preloaded volume.
33552
33553 Action: No operator action is required.
33554
33555
33556
33557 rcp_disk_.pl1
33558 RCP: WARNING!! IF YOU AUTHENTICATE THIS REQUEST
33559 <USER> WILL OWN VOLUME <VOLUME>!
33560
33561
33562 Stream: BOS Typewriter sounds beeper
33563
33564 Time: While system is running.
33565
33566 Meaning: This is a warning to the operator. He should be
33567 very careful to check the physical label of the
33568 volume before authenticating this request. As the
33569 message states if the request is autheticated
33570 <VOLUME> will be registered and acquired to
33571 <USER>.
33572
33573 Action: Check the physical label of the disk pack. If it
33574 is the property of <USER> authenticate the
33575 request. If it is not the property of <USER> deny
33576 the request by typing "x auth no".
33577
33578
33579
33580
33581
33582
33583 RCP -579- MR12.5 10/27/92^L
33584
33585
33586 rcp_tape_.pl1
33587 RCP: WARNING!! IF YOU AUTHENTICATE THIS REQUEST
33588 <USER> WILL OWN VOLUME <VOLUME>!
33589
33590
33591 Stream: BOS Typewriter sounds beeper
33592
33593 Time: While system is running.
33594
33595 Meaning: This is a warning to the operator. IHe should be
33596 very careful to check the physical label of the
33597 volume before authenticating this request. As the
33598 message states if the request is autheticated
33599 <VOLUME> will be registered and acquired to
33600 <USER>.
33601
33602 Action: Check the physical label of the tape volume. If
33603 it is the property of <USER> authenticate the
33604 request. If it is not the property of <USER> deny
33605 the request by typing "x auth no".
33606
33607
33608
33609 rcp_disk_.pl1
33610 RCP: Wrong pack NAME mounted on DRIVE. Mount
33611 pack PACK on DRIVE.
33612
33613
33614 Stream: BOS Typewriter sounds beeper
33615
33616 Time: While system is running.
33617
33618 Meaning: The operator has denied authentication for a
33619 removable disk pack NAME on drive DRIVE. The
33620 disk drive is put in standby.
33621
33622 Action: Mount the correct pack PACK with protect as
33623 specified and ready drive.
33624
33625
33626
33627
33628
33629
33630
33631
33632
33633
33634
33635
33636
33637
33638
33639
33640
33641 RCP -580- MR12.5 10/27/92^L
33642
33643
33644 rcp_disk_.pl1
33645 RCP: Wrong pack NAME mounted on DRIVE. Mount
33646 pack PACK without protect on DRIVE.
33647
33648
33649 Stream: BOS Typewriter sounds beeper
33650
33651 Time: While system is running.
33652
33653 Meaning: The operator has denied authentication for a
33654 removable disk pack NAME on drive DRIVE. The
33655 disk drive is put in standby.
33656
33657 Action: Mount the correct pack PACK with protect as
33658 specified and ready drive.
33659
33660
33661
33662 rcp_control_.pl1
33663 rcp_control_: Error surveying DEVICE. MESSAGE
33664
33665
33666 Stream: BOS Typewriter.
33667
33668 Time: In response to an operator command.
33669
33670 Meaning: An error occurred while surveying the device.
33671
33672 Action: Contact the system programming staff.
33673
33674
33675
33676 rcp_init.pl1
33677 rcp_init: DDDD cannot be used for user I/O.
33678
33679
33680 Stream: BOS Typewriter Crashes system
33681
33682 Time: System Intialization.
33683
33684 Meaning: An attempt was made to configure a device for user
33685 I/O which is being used by the system for system
33686 storage.
33687
33688 Action: Follow normal recovery procedures.
33689
33690
33691
33692
33693
33694
33695
33696
33697
33698
33699 rcp_init -581- MR12.5 10/27/92^L
33700
33701
33702 rcp_init.pl1
33703 rcp_init: DDDD deleted.
33704
33705
33706 Stream: BOS Typewriter.
33707
33708 Time: System Intialization.
33709
33710 Meaning: Device DDDD could not be found or accessed and it
33711 will be deleted.
33712
33713 Action: Contact the system programming staff.
33714
33715
33716
33717 rcp_init.pl1
33718 rcp_init: Device DEVICE defined more than once
33719
33720
33721 Stream: BOS Typewriter Crashes system
33722
33723 Time: System Intialization.
33724
33725 Meaning: The configuration deck defines the device DEVICE
33726 more than once.
33727
33728 Action: Perform an emergency shutdown and correct the
33729 configuration deck. Follow normal recovery
33730 procedures.
33731
33732
33733
33734 rcp_init.pl1
33735 rcp_init: Error surveying DDDD. ERRORMESSAGE
33736
33737
33738 Stream: BOS Typewriter.
33739
33740 Time: System Intialization.
33741
33742 Meaning: Attempted to access device DDDD but could not due
33743 to ERRORMESSAGE.
33744
33745 Action: Contact the system programming staff.
33746
33747
33748
33749
33750
33751
33752
33753
33754
33755
33756
33757 rcp_init -582- MR12.5 10/27/92^L
33758
33759
33760 rcp_init.pl1
33761 rcp_init: ndrives not specified with last model
33762 number for PRPH DDDD. Assuming 0.
33763
33764
33765 Stream: BOS Typewriter.
33766
33767 Time: System Intialization.
33768
33769 Meaning: Detected a MODEL value at the end of PRPH card
33770 PPPP. Each MODEL value should paired with an
33771 NDRIVE value. The last model value will be
33772 assigned zero devices. It is possible that there
33773 is another error elsewhere on this card to have
33774 caused this message.
33775
33776 Action: Contact the system programming staff.
33777
33778
33779
33780 rcp_init.pl1
33781 rcp_init: Trying to create rcp_com_seg
33782 ERRORMESSAGE
33783
33784
33785 Stream: BOS Typewriter Crashes system
33786
33787 Time: System Intialization.
33788
33789 Meaning: This indicates a logic error in the supervisor or
33790 CPU or memory hardware problems.
33791
33792 Action: Follow normal recovery procedures.
33793
33794
33795
33796 rcp_init.pl1
33797 rcp_init: Trying to create rcp_data ERRORMESSAGE
33798
33799
33800 Stream: BOS Typewriter Crashes system
33801
33802 Time: System Intialization.
33803
33804 Meaning: This indicates a logic error in the supervisor or
33805 CPU or memory hardware problems.
33806
33807 Action: Follow normal recovery procedures.
33808
33809
33810
33811
33812
33813
33814
33815 rcp_init -583- MR12.5 10/27/92^L
33816
33817
33818 rcp_init.pl1
33819 rcp_init: Trying to init mca_data. ERRORMESSAGE
33820
33821
33822 Stream: BOS Typewriter Crashes system
33823
33824 Time: System Intialization.
33825
33826 Meaning: This indicates a logic error in the supervisor or
33827 CPU or memory hardware problems.
33828
33829 Action: Follow normal recovery procedures.
33830
33831
33832
33833 rcp_init.pl1
33834 rcp_init: Trying to reclassify rcp_com_seg
33835 ERRORMESSAGE
33836
33837
33838 Stream: BOS Typewriter Crashes system
33839
33840 Time: System Intialization.
33841
33842 Meaning: This indicates a logic error in the supervisor or
33843 CPU or memory hardware problems.
33844
33845 Action: Follow normal recovery procedures.
33846
33847
33848
33849 rcp_init.pl1
33850 rcp_init: Trying to reclassify rcp_data
33851 ERRORMESSAGE
33852
33853
33854 Stream: BOS Typewriter Crashes system
33855
33856 Time: System Intialization.
33857
33858 Meaning: This indicates a logic error in the supervisor or
33859 CPU or memory hardware problems.
33860
33861 Action: Follow normal recovery procedures.
33862
33863
33864
33865
33866
33867
33868
33869
33870
33871
33872
33873 rcp_init -584- MR12.5 10/27/92^L
33874
33875
33876 rcp_tape_survey_.pl1
33877 rcp_tape_survey_: Error surveying controller
33878 CONTROLLER: ERROR_STATUS
33879
33880
33881 Stream: BOS Typewriter sounds beeper
33882
33883 Time: System Intialization.
33884
33885 Meaning: An error was received from IOI while attempting to
33886 survey the tape controller DEVICE. This indicates
33887 a logic error in the supervisor or CPU or memory
33888 hardware problems.
33889
33890 Action: Contact the system programming staff. Follow
33891 normal recovery procedures.
33892
33893
33894
33895 rcp_tape_survey_.pl1
33896 rcp_tape_survey_: Multiple device NUMBER's found
33897 on CONTROLLER.
33898
33899
33900 Stream: BOS Typewriter sounds beeper
33901
33902 Time: System Intialization.
33903
33904 Meaning: The survey information indicates that there are
33905 multiple devices with the same device number.
33906
33907 Action: Contact field engineering personnel.
33908
33909
33910
33911 rcp_tape_survey_.pl1
33912 rcp_tape_survey_: Tape controller CONTROLLER did
33913 not respond within one second.
33914
33915
33916 Stream: BOS Typewriter sounds beeper
33917
33918 Time: System Intialization.
33919
33920 Meaning: The tape controller or IOM failed to respond to
33921 the survey-devices command by sending an interrupt
33922 within one second.
33923
33924 Action: Contact field engineering personnel.
33925
33926
33927
33928
33929
33930
33931 rcp_tape_survey_ -585- MR12.5 10/27/92^L
33932
33933
33934 rcprm_registry_mgr_.pl1
33935 rcprm_registry_mgr_$delete_registry: Deleting
33936 possibly bogus registry PATH for USERID.
33937
33938
33939 Stream: BOS Typewriter sounds beeper
33940
33941 Time: While system is running.
33942
33943 Meaning: The segment at PATH does not seem to be an RCP
33944 registry. It may simply be a damaged registry or
33945 a user may be attempting to use delete_registry to
33946 delete a non-registry object.
33947
33948 Action: Contact the system administrator.
33949
33950
33951
33952 system_control_.pl1
33953 Ready
33954
33955
33956 Stream: BOS Typewriter.
33957
33958 Time: In response to an operator command.
33959
33960 Meaning: The Initializer types Ready whenever it is ready
33961 to accept an Initializer command in ring 4.
33962
33963 Action: Type the desired command.
33964
33965
33966
33967 reassign_work_classes_.pl1
33968 reassign_work_classes_: load control group "XXX"
33969 not found in mgt for user PERSON.PROJECT.TAG.
33970 reassign_work_classes_: mgt clobbered contact
33971 system administrator.
33972
33973
33974 Stream: as severity2.
33975
33976 Time: At shift change time or after a "maxu auto"
33977 command.
33978
33979 Meaning: Some logged in user's load control group has
33980 apparently disappeared from the mgt. If the load
33981 control group specified in the message is valid
33982 then the mgt has been destroyed. Otherwise the
33983 user's answer table entry has been destroyed. All
33984 users will remain in their current work classes.
33985
33986 Action: Contact the system administrator.
33987
33988
33989 reassign_work_classes_ -586- MR12.5 10/27/92^L
33990
33991
33992 reassign_work_classes_.pl1
33993 reassign_work_classes_: no work classes defined
33994 on current shift.
33995
33996
33997 Stream: as severity2
33998
33999 Time: At shift change time or after a "maxu auto"
34000 command.
34001
34002 Meaning: The table in the mgt that should define the work
34003 classes for the current shift has not been filled
34004 in. Probably a new shift has been added to the
34005 installation_parms segment but the work classes
34006 for that shift have not been specified in the mgt.
34007 All users will be placed in a single work class.
34008
34009 Action: No operator action is required.
34010
34011
34012
34013 reassign_work_classes_.pl1
34014 reassign_work_classes_: process NNN remained in
34015 work class NN
34016
34017
34018 Stream: as severity1
34019
34020 Time: At shift change time or after a "maxu auto"
34021 command.
34022
34023 Meaning: Some privileged user has interfered with the
34024 Answering Service's attempt to define a new set of
34025 work classes. The Answering Service will
34026 automatically retry the reassignment of work
34027 classes.
34028
34029 Action: No operator action is required.
34030
34031
34032
34033
34034
34035
34036
34037
34038
34039
34040
34041
34042
34043
34044
34045
34046
34047 reassign_work_classes_ -587- MR12.5 10/27/92^L
34048
34049
34050 reassign_work_classes_.pl1
34051 reassign_work_classes_: undefined work class DD
34052 required by load control group XXX
34053 reassign_work_classes_: mgt clobbered contact
34054 system administrator.
34055
34056
34057 Stream: as severity2
34058
34059 Time: At shift change time or after a "maxu auto"
34060 command.
34061
34062 Meaning: There is an inconsistency in the mgt. Probably
34063 the mgt has been destroyed. All users will remain
34064 in their current work class.
34065
34066 Action: Contact the system administrator.
34067
34068
34069
34070 disk_rebuild_caller.pl1
34071 rebuild_disk: Error XX in rebuild of volume
34072 PVNAME.
34073
34074
34075 Stream: Initializer process output.
34076
34077 Time: In response to an operator command.
34078
34079 Meaning: An error has occurred trying to rebuild the disk.
34080 The new copy should not be used.
34081
34082 Action: If the problem can be repaired repair it and try
34083 again. Contact the system programming staff.
34084
34085
34086
34087 salv_caller.pl1
34088 rebuild_disk: Expected argument missing.
34089
34090
34091 Stream: Initializer process output.
34092
34093 Time: In response to an operator command.
34094
34095 Meaning: Incorrect arguments were specified.
34096
34097 Action: Enter a corrected command line.
34098
34099
34100
34101
34102
34103
34104
34105 rebuild_disk -588- MR12.5 10/27/92^L
34106
34107
34108 salv_caller.pl1
34109 rebuild_disk: Specified control argument is not
34110 implemented by this command. BLAH
34111
34112
34113 Stream: Initializer process output.
34114
34115 Time: In response to an operator command.
34116
34117 Meaning: Incorrect arguments were specified.
34118
34119 Action: Enter a corrected command line.
34120
34121
34122
34123 disk_rebuild_caller.pl1
34124 rebuild_disk: volume PVNAME from DSKA_XX onto
34125 DSKA_YY
34126 Current disk parameters:
34127 part NAME FREC NREC
34128 Vtoc size is XX ave. seg length = Y.ZZZ
34129 Current number of VTOCEs = XX
34130
34131
34132 Stream: Initializer process output.
34133
34134 Time: In response to an operator command.
34135
34136 Meaning: This is the response to the operator command
34137 "rebuild_disk" issued in ring 1.
34138
34139 Action: No operator action is required.
34140
34141
34142
34143 disk_rebuild_caller.pl1
34144 rebuild_disk: Volume PVNAME must be mounted
34145 before rebuilding
34146
34147
34148 Stream: Initializer process output.
34149
34150 Time: In response to an operator command.
34151
34152 Meaning: The rebuild_disk command was invoked on an mounted
34153 volume. Only volumes which are mounted may be
34154 rebuilt. No action was taken.
34155
34156 Action: Salvage the volume first and then reissue the
34157 rebuild_disk command.
34158
34159
34160
34161
34162
34163 rebuild_disk -589- MR12.5 10/27/92^L
34164
34165
34166 reclassify.pl1
34167 reclassify: err locking parent. ERROR_CODE
34168
34169
34170 Stream: BOS Typewriter Crashes system
34171
34172 Time: While system is running.
34173
34174 Meaning: This indicates a logic error in the supervisor or
34175 CPU or memory hardware problems. This error
34176 crashes the system.
34177
34178 Action: Follow normal recovery procedures.
34179
34180
34181
34182 reconfig.pl1
34183 reconfig: Assigned CPU <cputag> to
34184 <Person.Project.instance> for testing
34185
34186
34187 Stream: BOS Typewriter.
34188
34189 Time: While system is running.
34190
34191 Meaning: Successful reconfiguration of the indicated
34192 processor has been performed by the processor
34193 testing ISOLTS subsystem.
34194
34195 Action: No operator action is required.
34196
34197
34198
34199 reconfig.pl1
34200 reconfig: Releasing base <req_mem>k of MEM
34201 <scutag>
34202
34203
34204 Stream: BOS Typewriter.
34205
34206 Time: While system is running.
34207
34208 Meaning: Processor testing has been terminated and the
34209 indicated memory is now available for
34210 reconfiguration.
34211
34212 Action: No operator action is required.
34213
34214
34215
34216
34217
34218
34219
34220
34221 reconfig -590- MR12.5 10/27/92^L
34222
34223
34224 reconfig.pl1
34225 reconfig: trouble unlocking scs$reconfig_lock
34226
34227
34228 Stream: BOS Typewriter.
34229
34230 Time: While system is running.
34231
34232 Meaning: The reconfiguration lock could not be unlocked.
34233 It is left in its current state. Further attempts
34234 at reconfiguration may fail.
34235
34236 Action: No operator action is required.
34237
34238
34239
34240 reconfig.pl1
34241 reconfig: Unassigned CPU <cputag> from
34242 <Person.Project.instance>
34243
34244
34245 Stream: BOS Typewriter.
34246
34247 Time: While system is running.
34248
34249 Meaning: Processor testing has been terminated and the
34250 indicated processor is now available for
34251 reconfiguration.
34252
34253 Action: No operator action is required.
34254
34255
34256
34257 reconfig.pl1
34258 reconfig: Using base <req_mem>k of MEM <scutag>
34259 for testing CPU cputag
34260
34261
34262 Stream: BOS Typewriter.
34263
34264 Time: While system is running.
34265
34266 Meaning: Successful reconfiguration of the indicated memory
34267 has been performed by the processor testing
34268 ISOLTS subsystem.
34269
34270 Action: No operator action is required.
34271
34272
34273
34274
34275
34276
34277
34278
34279 reconfig -591- MR12.5 10/27/92^L
34280
34281
34282 reloader.pl1
34283 reload_volume: An implementation restriction when
34284 using version 1 volume logs. This requires that
34285 the RPV be reloaded separately from other volumes.
34286
34287
34288 Stream: Reloader output.
34289
34290 Time: During volume reloading.
34291
34292 Meaning: Using version 1 volume logs all physical volumes
34293 must belong to the mounted RPV. An exception is
34294 when reloading the RPV itself it must be reloaded
34295 separately then a re-boot on the new RPV will
34296 allow the other volumes to be reloaded.
34297
34298 Action: Enter a corrected command line.
34299
34300
34301
34302 reloader.pl1
34303 reload_volume: arg err: ERROR_MESS
34304
34305
34306 Stream: Reloader output.
34307
34308 Time: During volume reloading.
34309
34310 Meaning: Invalid input was given.
34311
34312 Action: Enter a corrected command line.
34313
34314
34315
34316 reloader.pl1
34317 reload_volume: Begin reload of volume NAME at
34318 TIME
34319
34320
34321 Stream: Reloader online output.
34322
34323 Time: During volume reloading.
34324
34325 Meaning: A volume reload is beginning.
34326
34327 Action: No operator action is required.
34328
34329
34330
34331
34332
34333
34334
34335
34336
34337 reload_volume -592- MR12.5 10/27/92^L
34338
34339
34340 reloader.pl1
34341 reload_volume: Could not enable 256KW segments:
34342 ERORR_MESS
34343
34344
34345 Stream: Reloader output.
34346
34347 Time: During volume reloading.
34348
34349 Meaning: The call to hcs_$set_256K_switch failed.
34350
34351 Action: Contact the system programming staff.
34352
34353
34354
34355 reloader.pl1
34356 reload_volume: End reload of volume NAME at TIME
34357 reload_volume: Reloaded on volume NAME XX records
34358 of XX directories and XX records of XX segments
34359 and XX null vtoces
34360
34361
34362 Stream: Reloader online output.
34363
34364 Time: During volume reloading.
34365
34366 Meaning: A volume reload has completed. The statistics
34367 printed indicate how many records were reloaded.
34368
34369 Action: No operator action is required.
34370
34371
34372
34373 reloader.pl1
34374 reload_volume: error closing volume label:
34375 ERROR_MESS
34376
34377
34378 Stream: Reloader output.
34379
34380 Time: During volume reloading.
34381
34382 Meaning: An error occurred while reloading.
34383
34384 Action: Contact the system programming staff.
34385
34386
34387
34388
34389
34390
34391
34392
34393
34394
34395 reload_volume -593- MR12.5 10/27/92^L
34396
34397
34398 reloader.pl1
34399 reload_volume: error closing volume map:
34400 ERROR_MESS
34401
34402
34403 Stream: Reloader output.
34404
34405 Time: During volume reloading.
34406
34407 Meaning: An error occurred while reloading.
34408
34409 Action: Contact the system programming staff.
34410
34411
34412
34413 reloader.pl1
34414 reload_volume: error closing vtoc header:
34415 ERROR_MESS
34416
34417
34418 Stream: Reloader output.
34419
34420 Time: During volume reloading.
34421
34422 Meaning: An error occurred while reloading.
34423
34424 Action: Contact the system programming staff.
34425
34426
34427
34428 reloader.pl1
34429 reload_volume: error creating control seg:
34430 ERROR_MESS
34431
34432
34433 Stream: Reloader output.
34434
34435 Time: During volume reloading.
34436
34437 Meaning: An error occurred while reloading.
34438
34439 Action: Contact the system programming staff.
34440
34441
34442
34443
34444
34445
34446
34447
34448
34449
34450
34451
34452
34453 reload_volume -594- MR12.5 10/27/92^L
34454
34455
34456 reloader.pl1
34457 reload_volume: error creating temp segs:
34458 ERROR_MESS
34459
34460
34461 Stream: Reloader output.
34462
34463 Time: During volume reloading.
34464
34465 Meaning: An error occurred while reloading.
34466
34467 Action: Contact the system programming staff.
34468
34469
34470
34471 reloader.pl1
34472 reload_volume: error initializing input volume
34473 list: ERROR_MESS
34474
34475
34476 Stream: Reloader output.
34477
34478 Time: During volume reloading.
34479
34480 Meaning: An error occurred while reloading.
34481
34482 Action: Contact the system programming staff.
34483
34484
34485
34486 reloader.pl1
34487 reload_volume: error initializing output medium:
34488 ERROR_MESS
34489
34490
34491 Stream: Reloader output.
34492
34493 Time: During volume reloading.
34494
34495 Meaning: An error occurred while reloading.
34496
34497 Action: Contact the system programming staff.
34498
34499
34500
34501
34502
34503
34504
34505
34506
34507
34508
34509
34510
34511 reload_volume -595- MR12.5 10/27/92^L
34512
34513
34514 reloader.pl1
34515 reload_volume: error opening volume map:
34516 ERROR_MESS
34517
34518
34519 Stream: Reloader output.
34520
34521 Time: During volume reloading.
34522
34523 Meaning: An error occurred while reloading.
34524
34525 Action: Contact the system programming staff.
34526
34527
34528
34529 reloader.pl1
34530 reload_volume: error reloading volume NAME:
34531 ERROR_MESS
34532
34533
34534 Stream: Reloader output.
34535
34536 Time: During volume reloading.
34537
34538 Meaning: An error occurred while reloading.
34539
34540 Action: Contact the system programming staff.
34541
34542
34543
34544 reloader.pl1
34545 reload_volume: label check failed: ERROR_MESS
34546
34547
34548 Stream: Reloader output.
34549
34550 Time: During volume reloading.
34551
34552 Meaning: An error occurred while reloading.
34553
34554 Action: Contact the system programming staff.
34555
34556
34557
34558
34559
34560
34561
34562
34563
34564
34565
34566
34567
34568
34569 reload_volume -596- MR12.5 10/27/92^L
34570
34571
34572 reloader.pl1
34573 reload_volume: Operator name and physical volume
34574 name not specified
34575
34576
34577 Stream: Reloader output.
34578
34579 Time: During volume reloading.
34580
34581 Meaning: Invalid input was typed.
34582
34583 Action: Enter a corrected command line.
34584
34585
34586
34587 reloader.pl1
34588 reload_volume: Operator name not specified.
34589
34590
34591 Stream: Reloader output.
34592
34593 Time: During volume reloading.
34594
34595 Meaning: Missing input.
34596
34597 Action: Enter a corrected command line.
34598
34599
34600
34601 reloader.pl1
34602 reload_volume: Physical volume name not
34603 specified.
34604
34605
34606 Stream: Reloader output.
34607
34608 Time: During volume reloading.
34609
34610 Meaning: Missing input.
34611
34612 Action: Enter a corrected command line.
34613
34614
34615
34616
34617
34618
34619
34620
34621
34622
34623
34624
34625
34626
34627 reload_volume -597- MR12.5 10/27/92^L
34628
34629
34630 reloader.pl1
34631 reload_volume: Please start volume log recovery
34632 procedure.
34633
34634
34635 Stream: Reloader output.
34636
34637 Time: During volume reloading.
34638
34639 Meaning: Use the recover_volume_log command to recover the
34640 specified physical volumes volume log.
34641
34642 Action: Enter a corrected command line.
34643
34644
34645
34646 reloader.pl1
34647 reload_volume: The RPV pvid for physical volume
34648 NAME does not match the determined RPV pvid.
34649
34650
34651 Stream: Reloader output.
34652
34653 Time: During volume reloading.
34654
34655 Meaning: The backup_volume_log.rpv_pvid for NAME does not
34656 match the reloader determined RPV pvid. This
34657 could be an invalid attempt to reload a stranger
34658 physical volume.
34659
34660 Action: Contact the system programming staff.
34661
34662
34663
34664 reloader.pl1
34665 reload_volume: unable to build VTOC map:
34666 ERROR_MESS
34667
34668
34669 Stream: Reloader output.
34670
34671 Time: During volume reloading.
34672
34673 Meaning: An error occurred while reloading.
34674
34675 Action: Contact the system programming staff.
34676
34677
34678
34679
34680
34681
34682
34683
34684
34685 reload_volume -598- MR12.5 10/27/92^L
34686
34687
34688 reloader.pl1
34689 reload_volume: unable to determine pvid for NAME:
34690 ERROR_MESS
34691
34692
34693 Stream: Reloader output.
34694
34695 Time: During volume reloading.
34696
34697 Meaning: The volume registration information does not
34698 contain the physical volume NAME. This could be
34699 an invalid attempt to reload a stranger physical
34700 volume.
34701
34702 Action: Contact the system programming staff.
34703
34704
34705
34706 reloader.pl1
34707 reload_volume: unable to get info about rpv:
34708 ERROR_MESS
34709
34710
34711 Stream: Reloader output.
34712
34713 Time: During volume reloading.
34714
34715 Meaning: An error occurred while reloading.
34716
34717 Action: Contact the system programming staff.
34718
34719
34720
34721 reloader.pl1
34722 reload_volume: Unable to locate a valid volume
34723 log for PATH: ERROR_MESS
34724
34725
34726 Stream: Reloader output.
34727
34728 Time: During volume reloading.
34729
34730 Meaning: The volue log at PATH was not found. This message
34731 will always cause the reload to be aborted.
34732
34733 Action: Enter a corrected command line.
34734
34735
34736
34737
34738
34739
34740
34741
34742
34743 reload_volume -599- MR12.5 10/27/92^L
34744
34745
34746 reloader.pl1
34747 reload_volume: unable to open vtoc header:
34748 ERROR_MESS
34749
34750
34751 Stream: Reloader output.
34752
34753 Time: During volume reloading.
34754
34755 Meaning: An error occurred while reloading.
34756
34757 Action: Contact the system programming staff.
34758
34759
34760
34761 reload_volume_.pl1
34762 reload_volume_: Abandoning the reload of pv
34763 PVNAME
34764
34765
34766 Stream: Reloader output.
34767
34768 Time: During volume reloading.
34769
34770 Meaning: Some fatal error has occurred during the reload of
34771 the specified physical volume.
34772
34773 Action: Take the action required by the error just
34774 previous to this one and retry the reload of the
34775 physical volume.
34776
34777
34778
34779 bound_volume_reloader_.s.archi.1
34780 reload_volume_: Abandoning the reload of pv
34781 PVNAME
34782
34783
34784 Stream: Reloader output.
34785
34786 Time: During volume reloading.
34787
34788 Meaning: Some fatal error has occurred during the reload of
34789 the specified physical volume.
34790
34791 Action: Take the action required by the error just
34792 previous to this one and retry the reload of the
34793 physical volume.
34794
34795
34796
34797
34798
34799
34800
34801 reload_volume_ -600- MR12.5 10/27/92^L
34802
34803
34804 bound_volume_reloader_.s.archi.2
34805 reload_volume_: Abandoning the reload of pv
34806 PVNAME
34807
34808
34809 Stream: Reloader output.
34810
34811 Time: During volume reloading.
34812
34813 Meaning: Some fatal error has occurred during the reload of
34814 the specified physical volume.
34815
34816 Action: Take the action required by the error just
34817 previous to this one and retry the reload of the
34818 physical volume.
34819
34820
34821
34822 bound_volume_reloader_.s.archi.3
34823 reload_volume_: Abandoning the reload of pv
34824 PVNAME
34825
34826
34827 Stream: Reloader output.
34828
34829 Time: During volume reloading.
34830
34831 Meaning: Some fatal error has occurred during the reload of
34832 the specified physical volume.
34833
34834 Action: Take the action required by the error just
34835 previous to this one and retry the reload of the
34836 physical volume.
34837
34838
34839
34840 reload_volume_.pl1
34841 reload_volume_: All physical volumes to be
34842 reloaded have been abandoned.
34843
34844
34845 Stream: Reloader output.
34846
34847 Time: During volume reloading.
34848
34849 Meaning: Some fatal error has occurred during the reload of
34850 ALL the specified physical volumes.
34851
34852 Action: No operator action is required.
34853
34854
34855
34856
34857
34858
34859 reload_volume_ -601- MR12.5 10/27/92^L
34860
34861
34862 bound_volume_reloader_.s.archi.1
34863 reload_volume_: All physical volumes to be
34864 reloaded have been abandoned.
34865
34866
34867 Stream: Reloader output.
34868
34869 Time: During volume reloading.
34870
34871 Meaning: Some fatal error has occurred during the reload of
34872 ALL the specified physical volumes.
34873
34874 Action: No operator action is required.
34875
34876
34877
34878 bound_volume_reloader_.s.archi.2
34879 reload_volume_: All physical volumes to be
34880 reloaded have been abandoned.
34881
34882
34883 Stream: Reloader output.
34884
34885 Time: During volume reloading.
34886
34887 Meaning: Some fatal error has occurred during the reload of
34888 ALL the specified physical volumes.
34889
34890 Action: No operator action is required.
34891
34892
34893
34894 bound_volume_reloader_.s.archi.3
34895 reload_volume_: All physical volumes to be
34896 reloaded have been abandoned.
34897
34898
34899 Stream: Reloader output.
34900
34901 Time: During volume reloading.
34902
34903 Meaning: Some fatal error has occurred during the reload of
34904 ALL the specified physical volumes.
34905
34906 Action: No operator action is required.
34907
34908
34909
34910
34911
34912
34913
34914
34915
34916
34917 reload_volume_ -602- MR12.5 10/27/92^L
34918
34919
34920 reload_volume_.pl1
34921 reload_volume_: Bad disk page PAGE_ADDRESS for pv
34922 PVNAME
34923
34924
34925 Stream: Reloader output.
34926
34927 Time: During volume reloading.
34928
34929 Meaning: An I/O error occurred during a reload. This
34930 message indicates the bad disk address on the
34931 volume being reloaded.
34932
34933 Action: No operator action is required.
34934
34935
34936
34937 bound_volume_reloader_.s.archi.1
34938 reload_volume_: Bad disk page PAGE_ADDRESS for pv
34939 PVNAME
34940
34941
34942 Stream: Reloader output.
34943
34944 Time: During volume reloading.
34945
34946 Meaning: An I/O error occurred during a reload. This
34947 message indicates the bad disk address on the
34948 volume being reloaded.
34949
34950 Action: No operator action is required.
34951
34952
34953
34954 bound_volume_reloader_.s.archi.2
34955 reload_volume_: Bad disk page PAGE_ADDRESS for pv
34956 PVNAME
34957
34958
34959 Stream: Reloader output.
34960
34961 Time: During volume reloading.
34962
34963 Meaning: An I/O error occurred during a reload. This
34964 message indicates the bad disk address on the
34965 volume being reloaded.
34966
34967 Action: No operator action is required.
34968
34969
34970
34971
34972
34973
34974
34975 reload_volume_ -603- MR12.5 10/27/92^L
34976
34977
34978 bound_volume_reloader_.s.archi.3
34979 reload_volume_: Bad disk page PAGE_ADDRESS for pv
34980 PVNAME
34981
34982
34983 Stream: Reloader output.
34984
34985 Time: During volume reloading.
34986
34987 Meaning: An I/O error occurred during a reload. This
34988 message indicates the bad disk address on the
34989 volume being reloaded.
34990
34991 Action: No operator action is required.
34992
34993
34994
34995 reload_volume_.pl1
34996 reload_volume_: Error depositing old vtoce VTOCX
34997 for pv PVNAME: ERROR_MESS
34998
34999
35000 Stream: Reloader output.
35001
35002 Time: During volume reloading.
35003
35004 Meaning: The reloader was unable to release pages of an old
35005 object. This indicates a logic error in the
35006 supervisor or CPU or memory hardware problems.
35007 The input medium is abandoned.
35008
35009 Action: No operator action is required.
35010
35011
35012
35013 bound_volume_reloader_.s.archi.1
35014 reload_volume_: Error depositing old vtoce VTOCX
35015 for pv PVNAME: ERROR_MESS
35016
35017
35018 Stream: Reloader output.
35019
35020 Time: During volume reloading.
35021
35022 Meaning: The reloader was unable to release pages of an old
35023 object. This indicates a logic error in the
35024 supervisor or CPU or memory hardware problems.
35025 The input medium is abandoned.
35026
35027 Action: No operator action is required.
35028
35029
35030
35031
35032
35033 reload_volume_ -604- MR12.5 10/27/92^L
35034
35035
35036 bound_volume_reloader_.s.archi.2
35037 reload_volume_: Error depositing old vtoce VTOCX
35038 for pv PVNAME: ERROR_MESS
35039
35040
35041 Stream: Reloader output.
35042
35043 Time: During volume reloading.
35044
35045 Meaning: The reloader was unable to release pages of an old
35046 object. This indicates a logic error in the
35047 supervisor or CPU or memory hardware problems.
35048 The input medium is abandoned.
35049
35050 Action: No operator action is required.
35051
35052
35053
35054 bound_volume_reloader_.s.archi.3
35055 reload_volume_: Error depositing old vtoce VTOCX
35056 for pv PVNAME: ERROR_MESS
35057
35058
35059 Stream: Reloader output.
35060
35061 Time: During volume reloading.
35062
35063 Meaning: The reloader was unable to release pages of an old
35064 object. This indicates a logic error in the
35065 supervisor or CPU or memory hardware problems.
35066 The input medium is abandoned.
35067
35068 Action: No operator action is required.
35069
35070
35071
35072 reload_volume_.pl1
35073 reload_volume_: Error depositing page PAGENO of
35074 vtoce VTOCX for pv PVNAME: ERROR_MESS
35075
35076
35077 Stream: Reloader output.
35078
35079 Time: During volume reloading.
35080
35081 Meaning: The reloader was unable to release page PAGENO
35082 decimal of the new object. This is only done
35083 when an incomplete object is detected.
35084
35085 Action: No operator action is required.
35086
35087
35088
35089
35090
35091 reload_volume_ -605- MR12.5 10/27/92^L
35092
35093
35094 bound_volume_reloader_.s.archi.1
35095 reload_volume_: Error depositing page PAGENO of
35096 vtoce VTOCX for pv PVNAME: ERROR_MESS
35097
35098
35099 Stream: Reloader output.
35100
35101 Time: During volume reloading.
35102
35103 Meaning: The reloader was unable to release page PAGENO
35104 decimal of the new object. This is only done
35105 when an incomplete object is detected.
35106
35107 Action: No operator action is required.
35108
35109
35110
35111 bound_volume_reloader_.s.archi.2
35112 reload_volume_: Error depositing page PAGENO of
35113 vtoce VTOCX for pv PVNAME: ERROR_MESS
35114
35115
35116 Stream: Reloader output.
35117
35118 Time: During volume reloading.
35119
35120 Meaning: The reloader was unable to release page PAGENO
35121 decimal of the new object. This is only done
35122 when an incomplete object is detected.
35123
35124 Action: No operator action is required.
35125
35126
35127
35128 bound_volume_reloader_.s.archi.3
35129 reload_volume_: Error depositing page PAGENO of
35130 vtoce VTOCX for pv PVNAME: ERROR_MESS
35131
35132
35133 Stream: Reloader output.
35134
35135 Time: During volume reloading.
35136
35137 Meaning: The reloader was unable to release page PAGENO
35138 decimal of the new object. This is only done
35139 when an incomplete object is detected.
35140
35141 Action: No operator action is required.
35142
35143
35144
35145
35146
35147
35148
35149 reload_volume_ -606- MR12.5 10/27/92^L
35150
35151
35152 reload_volume_.pl1
35153 reload_volume_: Error reading input: ERROR_MESS
35154
35155
35156 Stream: Reloader output.
35157
35158 Time: During volume reloading.
35159
35160 Meaning: An error occurred while reading input. The input
35161 medium is abandoned.
35162
35163 Action: No operator action is required.
35164
35165
35166
35167 bound_volume_reloader_.s.archi.1
35168 reload_volume_: Error reading input: ERROR_MESS
35169
35170
35171 Stream: Reloader output.
35172
35173 Time: During volume reloading.
35174
35175 Meaning: An error occurred while reading input. The input
35176 medium is abandoned.
35177
35178 Action: No operator action is required.
35179
35180
35181
35182 bound_volume_reloader_.s.archi.2
35183 reload_volume_: Error reading input: ERROR_MESS
35184
35185
35186 Stream: Reloader output.
35187
35188 Time: During volume reloading.
35189
35190 Meaning: An error occurred while reading input. The input
35191 medium is abandoned.
35192
35193 Action: No operator action is required.
35194
35195
35196
35197
35198
35199
35200
35201
35202
35203
35204
35205
35206
35207 reload_volume_ -607- MR12.5 10/27/92^L
35208
35209
35210 bound_volume_reloader_.s.archi.3
35211 reload_volume_: Error reading input: ERROR_MESS
35212
35213
35214 Stream: Reloader output.
35215
35216 Time: During volume reloading.
35217
35218 Meaning: An error occurred while reading input. The input
35219 medium is abandoned.
35220
35221 Action: No operator action is required.
35222
35223
35224
35225 reload_volume_.pl1
35226 reload_volume_: Error reading old vtoce VTOCX for
35227 pv PVNAME: ERROR_MESS
35228
35229
35230 Stream: Reloader output.
35231
35232 Time: During volume reloading.
35233
35234 Meaning: An I/O error occurred during a reload. The input
35235 medium is abandoned.
35236
35237 Action: No operator action is required.
35238
35239
35240
35241 bound_volume_reloader_.s.archi.1
35242 reload_volume_: Error reading old vtoce VTOCX for
35243 pv PVNAME: ERROR_MESS
35244
35245
35246 Stream: Reloader output.
35247
35248 Time: During volume reloading.
35249
35250 Meaning: An I/O error occurred during a reload. The input
35251 medium is abandoned.
35252
35253 Action: No operator action is required.
35254
35255
35256
35257
35258
35259
35260
35261
35262
35263
35264
35265 reload_volume_ -608- MR12.5 10/27/92^L
35266
35267
35268 bound_volume_reloader_.s.archi.2
35269 reload_volume_: Error reading old vtoce VTOCX for
35270 pv PVNAME: ERROR_MESS
35271
35272
35273 Stream: Reloader output.
35274
35275 Time: During volume reloading.
35276
35277 Meaning: An I/O error occurred during a reload. The input
35278 medium is abandoned.
35279
35280 Action: No operator action is required.
35281
35282
35283
35284 bound_volume_reloader_.s.archi.3
35285 reload_volume_: Error reading old vtoce VTOCX for
35286 pv PVNAME: ERROR_MESS
35287
35288
35289 Stream: Reloader output.
35290
35291 Time: During volume reloading.
35292
35293 Meaning: An I/O error occurred during a reload. The input
35294 medium is abandoned.
35295
35296 Action: No operator action is required.
35297
35298
35299
35300 reload_volume_.pl1
35301 reload_volume_: Error writing new vtoce VTOCX for
35302 pv PVNAME: ERROR_MESS
35303
35304
35305 Stream: Reloader output.
35306
35307 Time: During volume reloading.
35308
35309 Meaning: An I/O error occurred during a reload. The input
35310 medium is abandoned.
35311
35312 Action: No operator action is required.
35313
35314
35315
35316
35317
35318
35319
35320
35321
35322
35323 reload_volume_ -609- MR12.5 10/27/92^L
35324
35325
35326 bound_volume_reloader_.s.archi.1
35327 reload_volume_: Error writing new vtoce VTOCX for
35328 pv PVNAME: ERROR_MESS
35329
35330
35331 Stream: Reloader output.
35332
35333 Time: During volume reloading.
35334
35335 Meaning: An I/O error occurred during a reload. The input
35336 medium is abandoned.
35337
35338 Action: No operator action is required.
35339
35340
35341
35342 bound_volume_reloader_.s.archi.2
35343 reload_volume_: Error writing new vtoce VTOCX for
35344 pv PVNAME: ERROR_MESS
35345
35346
35347 Stream: Reloader output.
35348
35349 Time: During volume reloading.
35350
35351 Meaning: An I/O error occurred during a reload. The input
35352 medium is abandoned.
35353
35354 Action: No operator action is required.
35355
35356
35357
35358 bound_volume_reloader_.s.archi.3
35359 reload_volume_: Error writing new vtoce VTOCX for
35360 pv PVNAME: ERROR_MESS
35361
35362
35363 Stream: Reloader output.
35364
35365 Time: During volume reloading.
35366
35367 Meaning: An I/O error occurred during a reload. The input
35368 medium is abandoned.
35369
35370 Action: No operator action is required.
35371
35372
35373
35374
35375
35376
35377
35378
35379
35380
35381 reload_volume_ -610- MR12.5 10/27/92^L
35382
35383
35384 reload_volume_.pl1
35385 reload_volume_: Unable to set damaged switch for
35386 vtoce VTOCX on pv PVNAME: ERROR_MESS
35387
35388
35389 Stream: Reloader output.
35390
35391 Time: During volume reloading.
35392
35393 Meaning: An I/O error has occured while attempting to write
35394 out the new vtoce which has the damaged switch
35395 turned on.
35396
35397 Action: No operator action is required.
35398
35399
35400
35401 bound_volume_reloader_.s.archi.1
35402 reload_volume_: Unable to set damaged switch for
35403 vtoce VTOCX on pv PVNAME: ERROR_MESS
35404
35405
35406 Stream: Reloader output.
35407
35408 Time: During volume reloading.
35409
35410 Meaning: An I/O error has occured while attempting to write
35411 out the new vtoce which has the damaged switch
35412 turned on.
35413
35414 Action: No operator action is required.
35415
35416
35417
35418 bound_volume_reloader_.s.archi.2
35419 reload_volume_: Unable to set damaged switch for
35420 vtoce VTOCX on pv PVNAME: ERROR_MESS
35421
35422
35423 Stream: Reloader output.
35424
35425 Time: During volume reloading.
35426
35427 Meaning: An I/O error has occured while attempting to write
35428 out the new vtoce which has the damaged switch
35429 turned on.
35430
35431 Action: No operator action is required.
35432
35433
35434
35435
35436
35437
35438
35439 reload_volume_ -611- MR12.5 10/27/92^L
35440
35441
35442 bound_volume_reloader_.s.archi.3
35443 reload_volume_: Unable to set damaged switch for
35444 vtoce VTOCX on pv PVNAME: ERROR_MESS
35445
35446
35447 Stream: Reloader output.
35448
35449 Time: During volume reloading.
35450
35451 Meaning: An I/O error has occured while attempting to write
35452 out the new vtoce which has the damaged switch
35453 turned on.
35454
35455 Action: No operator action is required.
35456
35457
35458
35459 reload_volume_.pl1
35460 reload_volume_: Unable to withdraw for bad page
35461 on pv PVNAME: ERROR_MESS
35462
35463
35464 Stream: Reloader output.
35465
35466 Time: During volume reloading.
35467
35468 Meaning: After an I/O error the reloader attempted to
35469 allocate a new page and failed. The volume may
35470 be full.
35471
35472 Action: If the volume is full it may be necessary to
35473 clean it up with sweep_pv -gc before restarting
35474 the reload.
35475
35476
35477
35478 bound_volume_reloader_.s.archi.1
35479 reload_volume_: Unable to withdraw for bad page
35480 on pv PVNAME: ERROR_MESS
35481
35482
35483 Stream: Reloader output.
35484
35485 Time: During volume reloading.
35486
35487 Meaning: After an I/O error the reloader attempted to
35488 allocate a new page and failed. The volume may
35489 be full.
35490
35491 Action: If the volume is full it may be necessary to
35492 clean it up with sweep_pv -gc before restarting
35493 the reload.
35494
35495
35496
35497 reload_volume_ -612- MR12.5 10/27/92^L
35498
35499
35500 bound_volume_reloader_.s.archi.2
35501 reload_volume_: Unable to withdraw for bad page
35502 on pv PVNAME: ERROR_MESS
35503
35504
35505 Stream: Reloader output.
35506
35507 Time: During volume reloading.
35508
35509 Meaning: After an I/O error the reloader attempted to
35510 allocate a new page and failed. The volume may
35511 be full.
35512
35513 Action: If the volume is full it may be necessary to
35514 clean it up with sweep_pv -gc before restarting
35515 the reload.
35516
35517
35518
35519 bound_volume_reloader_.s.archi.3
35520 reload_volume_: Unable to withdraw for bad page
35521 on pv PVNAME: ERROR_MESS
35522
35523
35524 Stream: Reloader output.
35525
35526 Time: During volume reloading.
35527
35528 Meaning: After an I/O error the reloader attempted to
35529 allocate a new page and failed. The volume may
35530 be full.
35531
35532 Action: If the volume is full it may be necessary to
35533 clean it up with sweep_pv -gc before restarting
35534 the reload.
35535
35536
35537
35538
35539
35540
35541
35542
35543
35544
35545
35546
35547
35548
35549
35550
35551
35552
35553
35554
35555 reload_volume_ -613- MR12.5 10/27/92^L
35556
35557
35558 reload_volume_.pl1
35559 reload_volume_: Unable to withdraw for new vtoce
35560 VTOCX for pv PVNAME: ERROR_MESS
35561
35562
35563 Stream: Reloader output.
35564
35565 Time: During volume reloading.
35566
35567 Meaning: The reloader is unable to allocate a new VTOCE.
35568 The volume may be full. The input medium is
35569 abandoned.
35570
35571 Action: No operator action is required. If the volume is
35572 full it may be necessary to clean it up with
35573 sweep_pv with the -gc option and then to continue
35574 reloading.
35575
35576
35577
35578 bound_volume_reloader_.s.archi.1
35579 reload_volume_: Unable to withdraw for new vtoce
35580 VTOCX for pv PVNAME: ERROR_MESS
35581
35582
35583 Stream: Reloader output.
35584
35585 Time: During volume reloading.
35586
35587 Meaning: The reloader is unable to allocate a new VTOCE.
35588 The volume may be full. The input medium is
35589 abandoned.
35590
35591 Action: No operator action is required. If the volume is
35592 full it may be necessary to clean it up with
35593 sweep_pv with the -gc option and then to continue
35594 reloading.
35595
35596
35597
35598
35599
35600
35601
35602
35603
35604
35605
35606
35607
35608
35609
35610
35611
35612
35613 reload_volume_ -614- MR12.5 10/27/92^L
35614
35615
35616 bound_volume_reloader_.s.archi.2
35617 reload_volume_: Unable to withdraw for new vtoce
35618 VTOCX for pv PVNAME: ERROR_MESS
35619
35620
35621 Stream: Reloader output.
35622
35623 Time: During volume reloading.
35624
35625 Meaning: The reloader is unable to allocate a new VTOCE.
35626 The volume may be full. The input medium is
35627 abandoned.
35628
35629 Action: No operator action is required. If the volume is
35630 full it may be necessary to clean it up with
35631 sweep_pv with the -gc option and then to continue
35632 reloading.
35633
35634
35635
35636 bound_volume_reloader_.s.archi.3
35637 reload_volume_: Unable to withdraw for new vtoce
35638 VTOCX for pv PVNAME: ERROR_MESS
35639
35640
35641 Stream: Reloader output.
35642
35643 Time: During volume reloading.
35644
35645 Meaning: The reloader is unable to allocate a new VTOCE.
35646 The volume may be full. The input medium is
35647 abandoned.
35648
35649 Action: No operator action is required. If the volume is
35650 full it may be necessary to clean it up with
35651 sweep_pv with the -gc option and then to continue
35652 reloading.
35653
35654
35655
35656 operator_com_channel_cmds_.pl1
35657 remove: bad arg "AAAA"
35658
35659
35660 Stream: as severity1.
35661
35662 Time: In response to an operator command.
35663
35664 Meaning: A bad argument was furnished with an remove
35665 command. The argument is skipped.
35666
35667 Action: Enter a corrected command.
35668
35669
35670
35671 remove -615- MR12.5 10/27/92^L
35672
35673
35674 operator_com_channel_cmds_.pl1
35675 remove: error: not done
35676
35677
35678 Stream: as severity1.
35679
35680 Time: In response to an operator command.
35681
35682 Meaning: Bad arguments were given to an remove command. No
35683 action resulted.
35684
35685 Action: Enter a corrected command line.
35686
35687
35688
35689 operator_com_channel_cmds_.pl1
35690 remove: ttyXXX is in use by the message
35691 coordinator and can not be removed.
35692
35693
35694 Stream: as severity1.
35695
35696 Time: In response to an operator command.
35697
35698 Meaning: An operator remove command specified a message
35699 coordinator channel. The channel was not removed.
35700
35701 Action: Enter a corrected command line. Use the drop
35702 command to take a channel away from the message
35703 coordinator.
35704
35705
35706
35707 operator_com_channel_cmds_.pl1
35708 remove: ttyXXX removed
35709
35710
35711 Stream: as severity1.
35712
35713 Time: In response to an operator remove command.
35714
35715 Meaning: This response to the operator command remove
35716 TTYxxx indicates the channel is no longer
35717 available for dialups. If a user was on the
35718 channel he is bumped with no message but
35719 "hangup". Note that if a user calls in on this
35720 channel and the modem answers the user gets a
35721 carriage return but no welcoming message from the
35722 system and he cannot log in.
35723
35724 Action: Remember to busy out the modem so that no user can
35725 call the channel.
35726
35727
35728
35729 remove -616- MR12.5 10/27/92^L
35730
35731
35732 obs_reconfigure.pl1
35733 Removed frame XXX.
35734
35735
35736 Stream: Initializer process output.
35737
35738 Time: In response to an operator command.
35739
35740 Meaning: This is the response to a successful delmain XXX
35741 command.
35742
35743 Action: No operator action is required.
35744
35745
35746
35747 obs_reconfigure.pl1
35748 Removed frames XXX thru YYY.
35749
35750
35751 Stream: Initializer process output.
35752
35753 Time: In response to an operator command.
35754
35755 Meaning: This is the response to a successful delmain XXX N
35756 command.
35757
35758 Action: No operator action is required.
35759
35760
35761
35762 obs_reconfigure.pl1
35763 Removed SCU X and its memory.
35764
35765
35766 Stream: Initializer process output.
35767
35768 Time: In response to an operator command.
35769
35770 Meaning: This is the response to a successful delmem X
35771 command.
35772
35773 Action: No operator action is required.
35774
35775
35776
35777
35778
35779
35780
35781
35782
35783
35784
35785
35786
35787 Removed SCU X and its memo -617- MR12.5 10/27/92^L
35788
35789
35790 obs_reconfigure.pl1
35791 Removed SCU's X and Y interlaced and their
35792 memory.
35793
35794
35795 Stream: Initializer process output.
35796
35797 Time: In response to an operator command.
35798
35799 Meaning: This is the response to a successful delmem X
35800 command when SCU's X and Y are interlaced.
35801
35802 Action: No operator action is required.
35803
35804
35805
35806 bce_save.pl1
35807 restorecheck_status: Special Interrupt:
35808 STATUS_WORD
35809
35810
35811 Stream: BOS Typewriter.
35812
35813 Time: System Intialization.
35814
35815 Meaning: An unexpected special interrupt has been detected.
35816
35817 Action: No operator action is required.
35818
35819
35820
35821 bce_save.pl1
35822 restorecheck_status: Time-Out on TAPE_DEV
35823
35824
35825 Stream: BOS Typewriter.
35826
35827 Time: System Intialization.
35828
35829 Meaning: An I/O that was issued to the tape device has
35830 timed-out.
35831
35832 Action: Follow normal recovery procedures.
35833
35834
35835
35836
35837
35838
35839
35840
35841
35842
35843
35844
35845 restorecheck_status -618- MR12.5 10/27/92^L
35846
35847
35848 bce_save.pl1
35849 restoreTAPE_SET: "Info" tape on TAPE_DEV
35850 created DATE_TIME
35851
35852
35853 Stream: BOS Typewriter.
35854
35855 Time: System Intialization.
35856
35857 Meaning: Just an informative message.
35858
35859 Action: No operator action is required.
35860
35861
35862
35863 bce_save.pl1
35864 restoreTAPE_SET: Unrecoverable MAJOR_STATUS
35865 SUB_STATUS on TAPE_DEV.
35866
35867
35868 Stream: BOS Typewriter.
35869
35870 Time: System Intialization.
35871
35872 Meaning: An unrecoverable error has occured while
35873 attempting to do I/O to the tape device.
35874
35875 Action: Follow normal recovery procedures.
35876
35877
35878
35879 bce_save.pl1
35880 restoreTAPE_SET: Abnormal tape termination of
35881 tape# TAPE_NUMBER on TAPE_DEV.
35882
35883
35884 Stream: BOS Typewriter.
35885
35886 Time: System Intialization.
35887
35888 Meaning: While reading the save tape an invalid record
35889 header was found. BCE save tapes are normally
35890 terminated with a End-of-Reel EOR record
35891 followed by three End-of-File EOF marks. This
35892 one most likely was not properly terminated.
35893
35894 Action: $ignore Unless it is felt that the tape is
35895 properly terminated in which case the restore can
35896 be restarted and this tape re-read.
35897
35898
35899
35900
35901
35902
35903 restoreTAPE_SET -619- MR12.5 10/27/92^L
35904
35905
35906 bce_save.pl1
35907 restoreTAPE_SET: Clearing unused VTOC region
35908 records BEGIN_REC - END_REC on PV_NAME.
35909
35910
35911 Stream: BOS Typewriter.
35912
35913 Time: System Intialization.
35914
35915 Meaning: Just an informative message. The unused records
35916 in the VTOC region are zero cleared to avoid
35917 having erroneous VTOCEs left laying around.
35918
35919 Action: No operator action is required.
35920
35921
35922
35923 bce_save.pl1
35924 restoreTAPE_SET: Device TAPE_DEV is being
35925 removed from the tape device list.
35926
35927
35928 Stream: BOS Typewriter.
35929
35930 Time: System Intialization.
35931
35932 Meaning: The TAPE_DEV has returned a status indicating that
35933 it is unable to be used.
35934
35935 Action: No operator action is required.
35936
35937
35938
35939 bce_save_util_.pl1
35940 restoreTAPE_SET: Device type mis-match.
35941 PV_NAME is on a DEV_TYPE
35942 but was saved from a DEV_TYPE.
35943
35944
35945 Stream: BOS Typewriter.
35946
35947 Time: System Intialization.
35948
35949 Meaning: The program is unable to restore the contents of
35950 the PV because the disk device currently being
35951 used is different than the one in use when the PV
35952 was saved. Only partitions can be restored to PVs
35953 mounted on different devices.
35954
35955 Action: Follow normal recovery procedures.
35956
35957
35958
35959
35960
35961 restoreTAPE_SET -620- MR12.5 10/27/92^L
35962
35963
35964 bce_save.pl1
35965 restoreTAPE_SET: End of Information without
35966 detecting TAPE_EOR record.
35967
35968
35969 Stream: BOS Typewriter.
35970
35971 Time: System Intialization.
35972
35973 Meaning: Multiple End-of-File EOF marks have been
35974 detected without previously reading an
35975 End-of-Reel EOR record.
35976
35977 Action: $ignore Unless it is felt that the tape is
35978 properly terminated in which case the restore can
35979 be restarted and this tape re-read.
35980
35981
35982
35983 bce_save.pl1
35984 restoreTAPE_SET: Error tape on TAPE_DEV is
35985 part of the "OTHER_TAPE_SET" set.
35986
35987
35988 Stream: BOS Typewriter.
35989
35990 Time: System Intialization.
35991
35992 Meaning: The tape just read is not part of this tape set.
35993
35994 Action: Mount a tape on the device that is part of this
35995 tape set.
35996
35997
35998
35999 bce_save.pl1
36000 restoreTAPE_SET: Incorrect tape number.
36001 Expected tape# TAPE_NUMBER.
36002
36003
36004 Stream: BOS Typewriter.
36005
36006 Time: System Intialization.
36007
36008 Meaning: An internal tape number tracking mechanism is used
36009 and the tape that was just read does not match
36010 what the program expects to be on the device.
36011
36012 Action: Mount the correct tape on the device.
36013
36014
36015
36016
36017
36018
36019 restoreTAPE_SET -621- MR12.5 10/27/92^L
36020
36021
36022 bce_save.pl1
36023 restoreTAPE_SET: MAJOR_STATUS SUB_STATUS on
36024 TAPE_DEV.
36025
36026
36027 Stream: BOS Typewriter.
36028
36029 Time: System Intialization.
36030
36031 Meaning: An error has occured while attempting to do I/O to
36032 the tape device.
36033
36034 Action: Follow normal recovery procedures.
36035
36036
36037
36038 bce_save_util_.pl1
36039 restoreTAPE_SET: MULTICS_VOL_ID PV_NAME on
36040 DISK_DEV
36041 Last updated: DATE_TIME
36042
36043
36044 Stream: BOS Typewriter.
36045
36046 Time: System Intialization.
36047
36048 Meaning: Just an informative message.
36049
36050 Action: No operator action is required.
36051
36052
36053
36054 bce_save_util_.pl1
36055 restoreTAPE_SET: No partitions were saved for
36056 volume PV_NAME.
36057 Removing from PV list.
36058 Stream: BOS Typewriter.
36059
36060
36061 Time: System Intialization.
36062
36063 Meaning: A request has been made to restore one or more
36064 partitions on
36065
36066 PV_NAME but the save tape indicates that no
36067 partitions were saved.
36068
36069 Action: Remove the partition reference from the control
36070 file.
36071
36072
36073
36074
36075
36076
36077 restoreTAPE_SET -622- MR12.5 10/27/92^L
36078
36079
36080 bce_save.pl1
36081 restoreTAPE_SET: No Physical Volumes left to
36082 restore.
36083
36084
36085 Stream: BOS Typewriter.
36086
36087 Time: System Intialization.
36088
36089 Meaning: For various reasons all of the physical volumes
36090 have been removed from the list of volumes.
36091
36092 Action: No operator action is required.
36093
36094
36095
36096 bce_save.pl1
36097 restoreTAPE_SET: No room to describe PV PV_NAME
36098 for part PARTITION_NAME.
36099
36100
36101 Stream: BOS Typewriter.
36102
36103 Time: System Intialization.
36104
36105 Meaning: The maximum number of physical volumes that can be
36106 handled by the program has been exceeded.
36107
36108 Action: The number of physical volumes defined in the
36109 control files must be reduced.
36110
36111
36112
36113 bce_save.pl1
36114 restoreTAPE_SET: No usable tape devices left in
36115 list.
36116
36117
36118 Stream: BOS Typewriter.
36119
36120 Time: System Intialization.
36121
36122 Meaning: For various reasons all of the tape devices have
36123 been removed from the list of available devices
36124 for this tape set.
36125
36126 Action: Follow normal recovery procedures.
36127
36128
36129
36130
36131
36132
36133
36134
36135 restoreTAPE_SET -623- MR12.5 10/27/92^L
36136
36137
36138 bce_save.pl1
36139 restoreTAPE_SET: No usable tape drives left.
36140
36141
36142 Stream: BOS Typewriter.
36143
36144 Time: System Intialization.
36145
36146 Meaning: For various reasons all of the tape devices have
36147 been removed from the list of available devices
36148 for this tape set.
36149
36150 Action: Follow normal recovery procedures.
36151
36152
36153
36154 bce_save_util_.pl1
36155 restoreTAPE_SET: Only partitions were saved for
36156 volume PV_NAME.
36157
36158
36159 Stream: BOS Typewriter.
36160
36161 Time: System Intialization.
36162
36163 Meaning: A request to restore the contents of a PV has been
36164 made but when the PV was saved only partitions
36165 were included.
36166
36167 Action: Correct the control files accordingly.
36168
36169
36170
36171 bce_save_util_.pl1
36172 restoreTAPE_SET: Partition PARTITION_NAME is
36173 not defined on PV_NAME.
36174
36175
36176 Stream: BOS Typewriter.
36177
36178 Time: System Intialization.
36179
36180 Meaning: A request to restore specific partition has been
36181 made but the partition does not exist of the PV.
36182
36183 Action: Correct the control files accordingly.
36184
36185
36186
36187
36188
36189
36190
36191
36192
36193 restoreTAPE_SET -624- MR12.5 10/27/92^L
36194
36195
36196 bce_save_util_.pl1
36197 restoreTAPE_SET: Partition PARTITION_NAME on
36198 PV_NAME was not saved.
36199
36200
36201 Stream: BOS Typewriter.
36202
36203 Time: System Intialization.
36204
36205 Meaning: A request was made to restore a partition from a
36206 PV but the partition was not saved as part of
36207 this tape set.
36208
36209 Action: Correct the control files accordingly.
36210
36211
36212
36213 bce_save.pl1
36214 restoreTAPE_SET: Partition PARTITION_NAME on
36215 PV_NAME record REC_NUM on tape# TAPE_NUMBER
36216 TAPE_DEV
36217
36218
36219 Stream: BOS Typewriter.
36220
36221 Time: System Intialization.
36222
36223 Meaning: Just an informative message.
36224
36225 Action: No operator action is required.
36226
36227
36228
36229 bce_save.pl1
36230 restoreTAPE_SET: Partition PARTITION_NAME was
36231 not defined when PV_NAME was saved.
36232
36233
36234 Stream: BOS Typewriter.
36235
36236 Time: System Intialization.
36237
36238 Meaning: A restore of a partition has been requested in the
36239 control file but the partition was not requested
36240 to be saved when the tape was made.
36241
36242 Action: Remove the partition reference from the control
36243 file.
36244
36245
36246
36247
36248
36249
36250
36251 restoreTAPE_SET -625- MR12.5 10/27/92^L
36252
36253
36254 bce_save.pl1
36255 restoreTAPE_SET: Partition PARTITION_NAME
36256 record REC_NUM on tape# TAPE_NUMBER TAPE_DEV
36257
36258
36259 Stream: BOS Typewriter.
36260
36261 Time: System Intialization.
36262
36263 Meaning: Just an informative message.
36264
36265 Action: No operator action is required.
36266
36267
36268
36269 bce_save.pl1
36270 restoreTAPE_SET: Please mount tape# TAPE_NUMBER
36271 on TAPE_DEV.
36272
36273
36274 Stream: BOS Typewriter sounds beeper
36275
36276 Time: System Intialization.
36277
36278 Meaning: Just an informative message.
36279
36280 Action: Mount tape on the device.
36281
36282
36283
36284 bce_save.pl1
36285 restoreTAPE_SET: Please mount the "Info" tape
36286 on TAPE_DEV.
36287
36288
36289 Stream: BOS Typewriter sounds beeper
36290
36291 Time: System Intialization.
36292
36293 Meaning: Just an informative message.
36294
36295 Action: Mount the tape on the device.
36296
36297
36298
36299
36300
36301
36302
36303
36304
36305
36306
36307
36308
36309 restoreTAPE_SET -626- MR12.5 10/27/92^L
36310
36311
36312 bce_save.pl1
36313 restoreTAPE_SET: Please mount the "restart"
36314 tape on TAPE_DEV.
36315
36316
36317 Stream: BOS Typewriter sounds beeper
36318
36319 Time: System Intialization.
36320
36321 Meaning: Just an informative message.
36322
36323 Action: Mount the tape on the device.
36324
36325
36326
36327 bce_save_util_.pl1
36328 restoreTAPE_SET: Please pre-mount tape#
36329 TAPE_NUMBER on TAPE_DEV.
36330
36331
36332 Stream: BOS Typewriter.
36333
36334 Time: System Intialization.
36335
36336 Meaning: The program is able to look ahead and find the
36337 tape that will be required next. This is an
36338 informative message that allows the restore to
36339 move at a faster pace.
36340
36341 Action: Mount the specified tape on the specified device.
36342
36343
36344
36345 bce_save.pl1
36346 restoreTAPE_SET: Readjusting tape sequence # to
36347 REC_NUM.
36348
36349
36350 Stream: BOS Typewriter.
36351
36352 Time: System Intialization.
36353
36354 Meaning: The missing record previously reported by the
36355 "Record sequence error ..." message can not be
36356 found. The internal tape sequence counter is
36357 corrected and processing continues as normal.
36358
36359 Action: No operator action is required.
36360
36361
36362
36363
36364
36365
36366
36367 restoreTAPE_SET -627- MR12.5 10/27/92^L
36368
36369
36370 bce_save.pl1
36371 restoreTAPE_SET: Record sequence error on tape#
36372 TAPE_NUMBER TAPE_DEV should be record #
36373 REC_NUM was record # REC_NUM.
36374
36375
36376 Stream: BOS Typewriter.
36377
36378 Time: System Intialization.
36379
36380 Meaning: Informative message that the sequence number on
36381 the tape is out of sync with what the program
36382 expects. If the WAS is only one record more than
36383 the S/B then the program will attempt to relocate
36384 the missing record by backspacing two records and
36385 rereading the records.
36386
36387 Action: No operator action is required.
36388
36389
36390
36391 bce_save.pl1
36392 restoreTAPE_SET: Relocated tape sequence #
36393 REC_NUM
36394
36395
36396 Stream: BOS Typewriter.
36397
36398 Time: System Intialization.
36399
36400 Meaning: The missing record previously reported by the
36401 "Record sequence error ..." message has been
36402 found. Processing continues as normal.
36403
36404 Action: No operator action is required.
36405
36406
36407
36408 bce_save_util_.pl1
36409 restoreTAPE_SET: Removing volume PV_NAME from
36410 PV list
36411 because all partitions were removed.
36412
36413
36414 Stream: BOS Typewriter.
36415
36416 Time: System Intialization.
36417
36418 Meaning: It is nolonger necessary for the program to keep
36419 track of the PV since all of the partition
36420 requests have been removed.
36421
36422 Action: Correct the control files accordingly.
36423
36424
36425 restoreTAPE_SET -628- MR12.5 10/27/92^L
36426
36427
36428 bce_save.pl1
36429 restoreTAPE_SET: restore complete...
36430
36431
36432 Stream: BOS Typewriter.
36433
36434 Time: System Intialization.
36435
36436 Meaning: Just an informative message.
36437
36438 Action: No operator action is required.
36439
36440
36441
36442 bce_save.pl1
36443 restoreTAPE_SET: Restore of volume PV_NAME on
36444 DISK_DEV complete.
36445
36446
36447 Stream: BOS Typewriter.
36448
36449 Time: System Intialization.
36450
36451 Meaning: Just an informative message.
36452
36453 Action: No operator action is required.
36454
36455
36456
36457 bce_save.pl1
36458 restoreTAPE_SET: Skipping volume PV_NAME on
36459 DISK_DEV restore complete.
36460
36461
36462 Stream: BOS Typewriter.
36463
36464 Time: System Intialization.
36465
36466 Meaning: Just an informative message.
36467
36468 Action: No operator action is required.
36469
36470
36471
36472
36473
36474
36475
36476
36477
36478
36479
36480
36481
36482
36483 restoreTAPE_SET -629- MR12.5 10/27/92^L
36484
36485
36486 bce_save.pl1
36487 restoreTAPE_SET: Starting from volume PV_NAME
36488 on DISK_DEV.
36489
36490
36491 Stream: BOS Typewriter.
36492
36493 Time: System Intialization.
36494
36495 Meaning: Just an informative message.
36496
36497 Action: No operator action is required.
36498
36499
36500
36501 bce_save.pl1
36502 restoreTAPE_SET: Tape on TAPE_DEV does not
36503 contain a supported tape label version.
36504
36505
36506 Stream: BOS Typewriter.
36507
36508 Time: System Intialization.
36509
36510 Meaning: The tape contains a tape version identifier that
36511 is nolonger supported.
36512
36513 Action: Use the "restore -display_info_tape tapX_NN"
36514 option to display the tape.
36515
36516
36517
36518 bce_save.pl1
36519 restoreTAPE_SET: Tape on TAPE_DEV does not
36520 contain a valid label.
36521
36522
36523 Stream: BOS Typewriter.
36524
36525 Time: System Intialization.
36526
36527 Meaning: The tape just read is not a valid save/restore
36528 tape.
36529
36530 Action: Follow normal recovery procedures.
36531
36532
36533
36534
36535
36536
36537
36538
36539
36540
36541 restoreTAPE_SET -630- MR12.5 10/27/92^L
36542
36543
36544 bce_save.pl1
36545 restoreTAPE_SET: Tape on TAPE_DEV is not part
36546 of this set.
36547
36548
36549 Stream: BOS Typewriter.
36550
36551 Time: System Intialization.
36552
36553 Meaning: The tape just read contains a different tape set
36554 name than what is currently being handled via the
36555 control file.
36556
36557 Action: Follow normal recovery procedures.
36558
36559
36560
36561 bce_save_util_.pl1
36562 restoreTAPE_SET: Tape subsystem "SUB_SYS" is
36563 not defined in the config.
36564
36565
36566 Stream: BOS Typewriter.
36567
36568 Time: System Intialization.
36569
36570 Meaning: No "prph" entry could be found for the tape
36571 subsystem.
36572
36573 Action: Correct config_deck or save/restore control
36574 files to indicate proper tape subsystem.
36575
36576
36577
36578 bce_save.pl1
36579 restoreTAPE_SET: Tape# TAPE_NUMBER on TAPE_DEV
36580 created DATE_TIME
36581
36582
36583 Stream: BOS Typewriter.
36584
36585 Time: System Intialization.
36586
36587 Meaning: Just an informative message.
36588
36589 Action: No operator action is required.
36590
36591
36592
36593
36594
36595
36596
36597
36598
36599 restoreTAPE_SET -631- MR12.5 10/27/92^L
36600
36601
36602 bce_save.pl1
36603 restoreTAPE_SET: The following tape devices
36604 will be used:
36605
36606
36607 Stream: BOS Typewriter.
36608
36609 Time: System Intialization.
36610
36611 Meaning: Just an informative message.
36612
36613 Action: No operator action is required.
36614
36615
36616
36617 bce_save.pl1
36618 restoreTAPE_SET: Time-out waiting for special
36619 interrupt.
36620
36621
36622 Stream: BOS Typewriter.
36623
36624 Time: System Intialization.
36625
36626 Meaning: The program was waiting for a special to come from
36627 the device but none was recieved in the alloted
36628 time.
36629
36630 Action: Follow normal recovery procedures.
36631
36632
36633
36634 bce_save_util_.pl1
36635 restoreTAPE_SET: Unable to restore
36636 "PARTITION_NAME" partition.
36637 Internal partition list full.
36638
36639
36640 Stream: BOS Typewriter.
36641
36642 Time: System Intialization.
36643
36644 Meaning: More partitions have been requested than the
36645 program can handle.
36646
36647 Action: Change control files to reduce the number defined
36648 possibly by breaking them up into seperate tape
36649 sets.
36650
36651
36652
36653
36654
36655
36656
36657 restoreTAPE_SET -632- MR12.5 10/27/92^L
36658
36659
36660 bce_save_util_.pl1
36661 restoreTAPE_SET: Unable to restore
36662 "PARTITION_NAME" partition.
36663 N partitions already defined
36664
36665
36666 Stream: BOS Typewriter.
36667
36668 Time: System Intialization.
36669
36670 Meaning: An attempt has been made to restore more than the
36671 N maximum partitions allowed.
36672
36673 Action: Change control filess to reduce the number
36674 requested.
36675
36676
36677
36678 bce_save_util_.pl1
36679 restoreTAPE_SET: Unable to restore only
36680 partitions.
36681
36682
36683 Stream: BOS Typewriter.
36684
36685 Time: System Intialization.
36686
36687 Meaning: A request to restore partition information on this
36688 PV was made but the PV does not contain a vaild
36689 label to locate the partition information. The PV
36690 is removed from the restore list.
36691
36692 Action: Follow normal recovery procedures.
36693
36694
36695
36696 bce_save.pl1
36697 restoreTAPE_SET: Unable to set density on
36698 TAPE_DEV.
36699
36700
36701 Stream: BOS Typewriter.
36702
36703 Time: System Intialization.
36704
36705 Meaning: The program was unable to set the required density
36706 of the tape device.
36707
36708 Action: Follow normal recovery procedures.
36709
36710
36711
36712
36713
36714
36715 restoreTAPE_SET -633- MR12.5 10/27/92^L
36716
36717
36718 bce_save.pl1
36719 restoreTAPE_SET: Unloading "Info" tape from
36720 TAPE_DEV REC_CNT records ERR_CNT errors
36721
36722
36723 Stream: BOS Typewriter.
36724
36725 Time: System Intialization.
36726
36727 Meaning: Just an informative message.
36728
36729 Action: No operator action is required.
36730
36731
36732
36733 bce_save.pl1
36734 restoreTAPE_SET: Unloading tape# TAPE_NUMBER
36735 from TAPE_DEV REC_CNT records ERR_CNT errors
36736
36737
36738 Stream: BOS Typewriter.
36739
36740 Time: System Intialization.
36741
36742 Meaning: Just an informative message.
36743
36744 Action: No operator action is required.
36745
36746
36747
36748 bce_save.pl1
36749 restoreTAPE_SET: Unloading TAPE_DEV REC_CNT
36750 records ERR_CNT errors
36751
36752
36753 Stream: BOS Typewriter.
36754
36755 Time: System Intialization.
36756
36757 Meaning: Just an informative message.
36758
36759 Action: No operator action is required.
36760
36761
36762
36763
36764
36765
36766
36767
36768
36769
36770
36771
36772
36773 restoreTAPE_SET -634- MR12.5 10/27/92^L
36774
36775
36776 bce_save_util_.pl1
36777 restoreTAPE_SET: Volume on DISK_DEV is not a
36778 MULTICS_VOL_ID.
36779
36780
36781 Stream: BOS Typewriter.
36782
36783 Time: System Intialization.
36784
36785 Meaning: Informative message to let the operator know that
36786 the volume does not currently contain a valid
36787 Multics label.
36788
36789 Action: No operator action is required.
36790
36791
36792
36793 bce_save_util_.pl1
36794 restoreTAPE_SET: Volume PV_NAME not found in
36795 tape label.
36796 Removing from PV list.
36797
36798
36799 Stream: BOS Typewriter.
36800
36801 Time: System Intialization.
36802
36803 Meaning: A request was made to restore a PV but the PV was
36804 not saved as part of this tape set.
36805
36806 Action: Correct the control files accordingly.
36807
36808
36809
36810 bce_save_util_.pl1
36811 restoreTAPE_SET: Volume PV_NAME will become
36812 NEW_PV_NAME as requested.
36813
36814
36815 Stream: BOS Typewriter.
36816
36817 Time: System Intialization.
36818
36819 Meaning: The PV to be restored currently has a dirrerent
36820 label than that to be restored. This is only an
36821 informative message to make the user aware of the
36822 change.
36823
36824 Action: No operator action is required.
36825
36826
36827
36828
36829
36830
36831 restoreTAPE_SET -635- MR12.5 10/27/92^L
36832
36833
36834 bce_save.pl1
36835 restoreTAPE_SET: Volume PV_NAME record
36836 REC_NUM on tape# TAPE_NUMBER TAPE_DEV
36837
36838
36839 Stream: BOS Typewriter.
36840
36841 Time: System Intialization.
36842
36843 Meaning: Just an informative message.
36844
36845 Action: No operator action is required.
36846
36847
36848
36849 bce_save.pl1
36850 restoreTAPE_SET: Waiting for special on
36851 TAPE_DEV.
36852
36853
36854 Stream: BOS Typewriter.
36855
36856 Time: System Intialization.
36857
36858 Meaning: Just an informative message.
36859
36860 Action: No operator action is required.
36861
36862
36863
36864 bce_save.pl1
36865 restoreTAPE_SET: Zeroing partition
36866 PARTITION_NAME on PV_NAME record REC_NUM.
36867
36868
36869 Stream: BOS Typewriter.
36870
36871 Time: System Intialization.
36872
36873 Meaning: Just an informative message.
36874
36875 Action: No operator action is required.
36876
36877
36878
36879
36880
36881
36882
36883
36884
36885
36886
36887
36888
36889 restoreTAPE_SET -636- MR12.5 10/27/92^L
36890
36891
36892 bce_save_util_.pl1
36893 restore: Attaching TAPE_DEV. ERR_MESSAGE
36894
36895
36896 Stream: BOS Typewriter sounds beeper
36897
36898 Time: System Intialization.
36899
36900 Meaning: IOI has returned a non-zero error code in response
36901 to a request to assign TAPE_DEV.
36902
36903 Action: Follow normal recovery procedures.
36904
36905
36906
36907 bce_save.pl1
36908 restore: bce_ioi_post_seg. ERR_MESSAGE
36909
36910
36911 Stream: BOS Typewriter sounds beeper
36912
36913 Time: System Intialization.
36914
36915 Meaning: The program was unable to get a pointer to the
36916 above segment. This indicates a logic error in
36917 the supervisor or CPU or memory hardware
36918 problems.
36919
36920 Action: Contact the system programming staff.
36921
36922
36923
36924 bce_save.pl1
36925 restore: bootload_disk_post_seg. ERR_MESSAGE
36926
36927
36928 Stream: BOS Typewriter sounds beeper
36929
36930 Time: System Intialization.
36931
36932 Meaning: The program was unable to get a pointer to the
36933 above segment. This indicates a logic error in
36934 the supervisor or CPU or memory hardware
36935 problems.
36936
36937 Action: Contact the system programming staff.
36938
36939
36940
36941
36942
36943
36944
36945
36946
36947 restore -637- MR12.5 10/27/92^L
36948
36949
36950 bce_save_util_.pl1
36951 restore: Could not read label of PV_NAME on
36952 DISK_DEV. ERR_MESSAGE
36953
36954
36955 Stream: BOS Typewriter sounds beeper
36956
36957 Time: System Intialization.
36958
36959 Meaning: The volume label of the PV could not be read due
36960 to the error given in ERR_MESSAGE.
36961
36962 Action: A operator query is done to find out if the read
36963 should be retried or the PV removed from the list.
36964
36965
36966
36967 bce_save.pl1
36968 restore: Getting tape label temp segment.
36969 ERR_MESSAGE
36970
36971
36972 Stream: BOS Typewriter sounds beeper
36973
36974 Time: System Intialization.
36975
36976 Meaning: An error occured while attempting to get a
36977 temporary segment to hold the tape label
36978 information.
36979
36980 Action: Contact the system programming staff.
36981
36982
36983
36984 bce_save_util_.pl1
36985 restore: Initiating CONTROL_FILE_NAME for
36986 set-TAPE_SET_IDX ERR_MESSAGE
36987
36988
36989 Stream: BOS Typewriter sounds beeper
36990
36991 Time: System Intialization.
36992
36993 Meaning: An error was detected while initiating the restore
36994 control file.
36995
36996 Action: $inform Follow normal recovery procedures.
36997
36998
36999
37000
37001
37002
37003
37004
37005 restore -638- MR12.5 10/27/92^L
37006
37007
37008 bce_save.pl1
37009 restore: PV_NAME ERR_MESSAGE
37010
37011
37012 Stream: BOS Typewriter sounds beeper
37013
37014 Time: System Intialization.
37015
37016 Meaning: The call to bootload_disk_io$test_done has
37017 returned a non-zero error code.
37018
37019 Action: $inform Follow normal recovery procedures.
37020
37021
37022
37023 bce_save.pl1
37024 restore: pvt. ERR_MESSAGE
37025
37026
37027 Stream: BOS Typewriter sounds beeper
37028
37029 Time: System Intialization.
37030
37031 Meaning: The program was unable to get a pointer to the
37032 above segment. This indicates a logic error in
37033 the supervisor or CPU or memory hardware
37034 problems.
37035
37036 Action: Contact the system programming staff.
37037
37038
37039
37040 bce_save.pl1
37041 restore: Restarting restore of set "TAPE_SET" on
37042 TAPE_DEV.
37043
37044
37045 Stream: BOS Typewriter.
37046
37047 Time: System Intialization.
37048
37049 Meaning: Just an informative message.
37050
37051 Action: No operator action is required.
37052
37053
37054
37055
37056
37057
37058
37059
37060
37061
37062
37063 restore -639- MR12.5 10/27/92^L
37064
37065
37066 bce_save_util_.pl1
37067 restore: Setting max workspace for TAPE_DEV.
37068 ERR_MESSAGE
37069
37070
37071 Stream: BOS Typewriter sounds beeper
37072
37073 Time: System Intialization.
37074
37075 Meaning: IOI has returned a non-zero error code in response
37076 to a request to set the max workspace size for
37077 TAPE_DEV.
37078
37079 Action: Contact the system programming staff.
37080
37081
37082
37083 bce_save.pl1
37084 restore: Setting status index for TAPE_DEV.
37085 ERR_MESSAGE
37086
37087
37088 Stream: BOS Typewriter sounds beeper
37089
37090 Time: System Intialization.
37091
37092 Meaning: IOI has returned a non-zero error which has been
37093 expanded in ERR_MESSAGE.
37094
37095 Action: Contact the system programming staff.
37096
37097
37098
37099 bce_save_util_.pl1
37100 restore: Setting up workspace for TAPE_DEV.
37101 ERR_MESSAGE
37102
37103
37104 Stream: BOS Typewriter sounds beeper
37105
37106 Time: System Intialization.
37107
37108 Meaning: IOI has returned a non-zero error code from the
37109 request to create a workspace for TAPE_DEV.
37110
37111 Action: Contact the system programming staff.
37112
37113
37114
37115
37116
37117
37118
37119
37120
37121 restore -640- MR12.5 10/27/92^L
37122
37123
37124 bce_save_util_.pl1
37125 restore: si ERR_MESSAGE
37126
37127
37128 Stream: BOS Typewriter sounds beeper
37129
37130 Time: System Intialization.
37131
37132 Meaning: An error has been found with the internal "si"
37133 structure. This indicates a logic error in the
37134 supervisor or CPU or memory hardware problems.
37135
37136 Action: Contact the system programming staff.
37137
37138
37139
37140 bce_save_util_.pl1
37141 restore: sri ERR_MESSAGE
37142
37143
37144 Stream: BOS Typewriter sounds beeper
37145
37146 Time: System Intialization.
37147
37148 Meaning: An error has been found with the internal "sri"
37149 structure. This indicates a logic error in the
37150 supervisor or CPU or memory hardware problems.
37151
37152 Action: Contact the system programming staff.
37153
37154
37155
37156 bce_save.pl1
37157 restore: Stopping restore of set "TAPE_SET".
37158
37159
37160 Stream: BOS Typewriter.
37161
37162 Time: System Intialization.
37163
37164 Meaning: Just an informative message.
37165
37166 Action: No operator action is required.
37167
37168
37169
37170
37171
37172
37173
37174
37175
37176
37177
37178
37179 restore -641- MR12.5 10/27/92^L
37180
37181
37182 bce_save_util_.pl1
37183 restore: TAPE_DEV ERR_MESSAGE
37184
37185
37186 Stream: BOS Typewriter sounds beeper
37187
37188 Time: System Intialization.
37189
37190 Meaning: An error occured while scanning the tape subsystem
37191 survey data.
37192
37193 Action: Follow normal recovery procedures.
37194
37195
37196
37197 bce_save.pl1
37198 restore: tape_error_data. ERR_MESSAGE
37199
37200
37201 Stream: BOS Typewriter sounds beeper
37202
37203 Time: System Intialization.
37204
37205 Meaning: The program was unable to get a pointer to the
37206 above segment. This indicates a logic error in
37207 the supervisor or CPU or memory hardware
37208 problems.
37209
37210 Action: Contact the system programming staff.
37211
37212
37213
37214 bce_save.pl1
37215 restore: Unassigning TAPE_DEV. ERR_MESSAGE
37216
37217
37218 Stream: BOS Typewriter sounds beeper
37219
37220 Time: System Intialization.
37221
37222 Meaning: IOI has returned a non-zero error which has been
37223 expanded in ERR_MESSAGE.
37224
37225 Action: Contact the system programming staff.
37226
37227
37228
37229
37230
37231
37232
37233
37234
37235
37236
37237 restore -642- MR12.5 10/27/92^L
37238
37239
37240 retv_copy.pl1
37241 retv_copy: deleting PATH without recovering
37242 resources ERROR_MESSAGE
37243
37244
37245 Stream: Logged in SYSERR log.
37246
37247 Time: Volume retrieval
37248
37249 Meaning: While retrieving a segment the retriever
37250 attempted to delete an old copy of a segment
37251 before using a newer one. The deletion attempt
37252 failed. Space may be wasted on the volume until a
37253 sweep_pv -gc is done.
37254
37255 Action: Note for volume administrator.
37256
37257
37258
37259 ring_alarm.pl1
37260 ring_alarm$fault: Reset admin privileges.
37261
37262
37263 Stream: Logged in SYSERR log.
37264
37265 Time: While system is running.
37266
37267 Meaning: On exit from ring one one or more AIM privileges
37268 were still set by privileged ring 1 code. These
37269 are reset and the following log message from
37270 set_privileges lists them. This indicates a
37271 benign bug in the ring one program that was
37272 running.
37273
37274 Action: Contact the system programming staff.
37275
37276
37277
37278 ring_alarm.pl1
37279 ring_alarm$poll: Mysterious ring alarm.
37280
37281
37282 Stream: BOS Typewriter Crashes system
37283
37284 Time: While system is running.
37285
37286 Meaning: The ring alarm register was set on exit from ring
37287 zero but no reason for it was recorded for the
37288 process.
37289
37290 Action: Contact the system programming staff.
37291
37292
37293
37294
37295 ring_alarm$poll -643- MR12.5 10/27/92^L
37296
37297
37298 ring_alarm.pl1
37299 ring_alarm: Fixed validation level on fault
37300 from OLD to NEW.
37301
37302
37303 Stream: BOS Typewriter sounds beeper
37304
37305 Time: While system is running.
37306
37307 Meaning: On exit from ring zero the validation level was
37308 less than the ring that is being returned to. The
37309 validation level is corrected to its value when it
37310 called into the inner ring. This indicates a
37311 benign bug in the inner ring entry called.
37312
37313 Action: Contact the system programming staff.
37314
37315
37316
37317 rldr_arg_reader_.pl1
37318 rldr_arg_reader_: ARG: ERROR_MESS
37319
37320
37321 Stream: BOS Typewriter.
37322
37323 Time: While system is running.
37324
37325 Meaning: Invalid arguments were given to the reloader.
37326
37327 Action: Enter a corrected command line.
37328
37329
37330
37331 rldr_arg_reader_.pl1
37332 rldr_arg_reader_: Implementation Restriction the
37333 RPV must be reloaded
37334 separately to obtain the required physical volume
37335 information.
37336
37337
37338 Stream: BOS Typewriter.
37339
37340 Time: While system is running.
37341
37342 Meaning: Due to an implementation restriction the RPV must
37343 be reloaded
37344 separately from the other physical
37345 volumes. Reload the RPV first
37346 then re-invoke the reload_volue command
37347 with the other physical
37348 volume names to be reloaded.
37349
37350 Action: Enter a corrected command line.
37351
37352
37353 rldr_arg_reader_ -644- MR12.5 10/27/92^L
37354
37355
37356 rldr_check_pvol_.pl1
37357 rldr_check_pvol_: Maximum access class mismatch
37358 rldr_check_pvol_: Have ACCESS_CLASS; Volog label
37359 requires ACCESS_CLASS
37360
37361
37362 Stream: Reloader online output.
37363
37364 Time: During volume reloading.
37365
37366 Meaning: The maximum access class for the volume does not
37367 match the volume log.
37368
37369 Action: Enter a corrected command line.
37370
37371
37372
37373 rldr_check_pvol_.pl1
37374 rldr_check_pvol_: Minimum access class mismatch
37375 rldr_check_pvol_: Have ACCESS_CLASS; Volog label
37376 requires ACCESS_CLASS
37377
37378
37379 Stream: Reloader online output.
37380
37381 Time: During volume reloading.
37382
37383 Meaning: The minimum access class for the volume does not
37384 match the volume log.
37385
37386 Action: Enter a corrected command line.
37387
37388
37389
37390 rldr_check_pvol_.pl1
37391 rldr_check_pvol_: Partition NAME not found on
37392 physical volume
37393
37394
37395 Stream: Reloader online output.
37396
37397 Time: During volume reloading.
37398
37399 Meaning: The partition NAME is missing from the volume
37400 label.
37401
37402 Action: Reinitialize the volume correctly.
37403
37404
37405
37406
37407
37408
37409
37410
37411 rldr_check_pvol_ -645- MR12.5 10/27/92^L
37412
37413
37414 rldr_check_pvol_.pl1
37415 rldr_check_pvol_: Partition NAME size mismatch
37416 rldr_check_pvol_: Have NN records; Volog label
37417 requires MM
37418
37419
37420 Stream: Reloader online output.
37421
37422 Time: During volume reloading.
37423
37424 Meaning: The size for partition NAME does not match.
37425
37426 Action: Reinitialize the volume correctly.
37427
37428
37429
37430 rldr_check_pvol_.pl1
37431 rldr_check_pvol_: Reload may overflow volume
37432 rldr_check_pvol_: Have NN records; Volog label
37433 requires NN records
37434
37435
37436 Stream: Reloader online output.
37437
37438 Time: During volume reloading.
37439
37440 Meaning: The output volume is too small.
37441
37442 Action: Reinitialize it correctly with init_vol.
37443
37444
37445
37446 rldr_check_pvol_.pl1
37447 rldr_check_pvol_: Reload may overflow vtoc
37448 rldr_check_pvol_: Have NN vtoce; Volog label
37449 requires NN vtoce
37450
37451
37452 Stream: Reloader online output.
37453
37454 Time: During volume reloading.
37455
37456 Meaning: The output volume has too small a VTOC.
37457
37458 Action: Reinitialize the output volume with init_vol.
37459
37460
37461
37462
37463
37464
37465
37466
37467
37468
37469 rldr_check_pvol_ -646- MR12.5 10/27/92^L
37470
37471
37472 rldr_check_pvol_.pl1
37473 rldr_check_pvol_: Unitialized output volume
37474
37475
37476 Stream: Reloader online output.
37477
37478 Time: During volume reloading.
37479
37480 Meaning: The output volume must be initialized with
37481 init_vol before use.
37482
37483 Action: Switch the output volume to storage-system status
37484 with the sdu command and then use init_vol to set
37485 it up.
37486
37487
37488
37489 rldr_check_pvol_.pl1
37490 rldr_check_pvol_: Volume mismatch
37491 rldr_check_pvol_: Have PVNAMEpvid = WWW; Volog
37492 label requires PVNAMEpvid = WWW
37493
37494
37495 Stream: Reloader online output.
37496
37497 Time: During volume reloading.
37498
37499 Meaning: The output volume label disagrees with the volume
37500 log.
37501
37502 Action: Reinitialize the output volume correctly with
37503 init_vol.
37504
37505
37506
37507 rldr_label_.pl1
37508 rldr_label_: Incorrect output medium mounted:
37509 ERROR_MESS
37510
37511
37512 Stream: Reloader output.
37513
37514 Time: During volume reloading.
37515
37516 Meaning: Someting is wrong with a reloader output volume.
37517
37518 Action: Mount a correct volume and try again.
37519
37520
37521
37522
37523
37524
37525
37526
37527 rldr_label_ -647- MR12.5 10/27/92^L
37528
37529
37530 rldr_label_.pl1
37531 rldr_label_: Label position failed: ERROR_MESS
37532
37533
37534 Stream: Reloader output.
37535
37536 Time: During volume reloading.
37537
37538 Meaning: Someting is wrong with a reloader output volume.
37539
37540 Action: Mount a correct volume and try again.
37541
37542
37543
37544 rldr_label_.pl1
37545 rldr_label_: Label read failed: ERROR_MESS
37546
37547
37548 Stream: Reloader output.
37549
37550 Time: During volume reloading.
37551
37552 Meaning: Someting is wrong with a reloader output volume.
37553
37554 Action: Mount a correct volume and try again.
37555
37556
37557
37558 rldr_label_.pl1
37559 rldr_label_: Label write failed: ERROR_MESS
37560
37561
37562 Stream: Reloader output.
37563
37564 Time: During volume reloading.
37565
37566 Meaning: Someting is wrong with a reloader output volume.
37567
37568 Action: Mount a correct volume and try again.
37569
37570
37571
37572
37573
37574
37575
37576
37577
37578
37579
37580
37581
37582
37583
37584
37585 rldr_label_ -648- MR12.5 10/27/92^L
37586
37587
37588 rldr_label_.pl1
37589 rldr_label_: Output volume pvid MMMMMMMMMMMM not
37590 equal to online
37591 pvid NNNNNNNNNNNN for pv PPPPPPPP.
37592 Invalid volume identifier.
37593
37594
37595 Stream: Reloader output.
37596
37597 Time: During volume reloading.
37598
37599 Meaning: The PVID on the output disk volume does not match
37600 the PVID as
37601 recorded in the pvolog for the disk volume.
37602 This indicates that
37603 either the label on the PV is incorrect
37604 or the pvolog segment
37605 is corrupted.
37606
37607 Action: Verify the PVID using output from the
37608 display_disk_label command.
37609 If the PVID from ddl output is differnet
37610 from that reported for the
37611 output volume use
37612 change_volume_registration and init_vol to
37613 correct the disk label. If the online
37614 PVID does not match use the
37615 recover_volume_log command to retrieve a
37616 correct pvolog segment.
37617 Retry the reload.
37618
37619
37620
37621 rldr_output_.pl1
37622 rldr_output_: Output volume attachment failed:
37623 ERROR_MESS
37624
37625
37626 Stream: Reloader output.
37627
37628 Time: During volume reloading.
37629
37630 Meaning: This indicates a logic error in the supervisor or
37631 CPU or memory hardware problems.
37632
37633 Action: Mount a different output volume and try again.
37634
37635
37636
37637
37638
37639
37640
37641
37642
37643 rldr_output_ -649- MR12.5 10/27/92^L
37644
37645
37646 rldr_output_.pl1
37647 rldr_output_: Output volume opening failed:
37648 ERROR_MESS
37649
37650
37651 Stream: Reloader output.
37652
37653 Time: During volume reloading.
37654
37655 Meaning: This indicates a logic error in the supervisor or
37656 CPU or memory hardware problems.
37657
37658 Action: Mount a different output volume and try again.
37659
37660
37661
37662 rldr_report_.pl1
37663 rldr_report_: Error file NAME created
37664
37665
37666 Stream: Reloader online output.
37667
37668 Time: During volume reloading.
37669
37670 Meaning: The reloader attempted to create an error file.
37671
37672 Action: No operator action is required.
37673
37674
37675
37676 rldr_report_.pl1
37677 rldr_report_: Error opening error file:
37678 ERROR_MESS
37679
37680
37681 Stream: Reloader online output.
37682
37683 Time: During volume reloading.
37684
37685 Meaning: The reloader attempted to create an error file.
37686
37687 Action: No operator action is required.
37688
37689
37690
37691
37692
37693
37694
37695
37696
37697
37698
37699
37700
37701 rldr_report_ -650- MR12.5 10/27/92^L
37702
37703
37704 rldr_report_.pl1
37705 rldr_report_: Unable to attach error file:
37706 ERROR_MESS
37707
37708
37709 Stream: Reloader online output.
37710
37711 Time: During volume reloading.
37712
37713 Meaning: The reloader attempted to create an error file.
37714
37715 Action: No operator action is required.
37716
37717
37718
37719 rldr_volume_map_.pl1
37720 rldr_volume_map_: Attempt to deposit free record
37721
37722
37723 Stream: Reloader output.
37724
37725 Time: During volume reloading.
37726
37727 Meaning: An error was encountered during reload volume map
37728 construction. Reloading continues.
37729
37730 Action: No operator action is required.
37731
37732
37733
37734 rldr_volume_map_.pl1
37735 rldr_volume_map_: Attempt to deposit out of range
37736 address WWW
37737
37738
37739 Stream: Reloader output.
37740
37741 Time: During volume reloading.
37742
37743 Meaning: An error was encountered during reload volume map
37744 construction. Reloading continues.
37745
37746 Action: No operator action is required.
37747
37748
37749
37750
37751
37752
37753
37754
37755
37756
37757
37758
37759 rldr_volume_map_ -651- MR12.5 10/27/92^L
37760
37761
37762 rldr_volume_map_.pl1
37763 rldr_volume_map_: Error reading volume map:
37764 ERROR_MESS
37765
37766
37767 Stream: Reloader output.
37768
37769 Time: During volume reloading.
37770
37771 Meaning: An error was encountered during reload volume map
37772 construction. Reloading continues.
37773
37774 Action: No operator action is required.
37775
37776
37777
37778 rldr_volume_map_.pl1
37779 rldr_volume_map_: Error writing volume map:
37780 ERROR_MESS
37781
37782
37783 Stream: Reloader output.
37784
37785 Time: During volume reloading.
37786
37787 Meaning: An error was encountered during reload volume map
37788 construction. Reloading continues.
37789
37790 Action: No operator action is required.
37791
37792
37793
37794 rldr_volume_map_.pl1
37795 rldr_volume_map_: Map position failed:
37796 ERROR_MESS
37797
37798
37799 Stream: Reloader output.
37800
37801 Time: During volume reloading.
37802
37803 Meaning: An error was encountered during reload volume map
37804 construction. Reloading continues.
37805
37806 Action: No operator action is required.
37807
37808
37809
37810
37811
37812
37813
37814
37815
37816
37817 rldr_volume_map_ -652- MR12.5 10/27/92^L
37818
37819
37820 rldr_volume_map_.pl1
37821 rldr_volume_map_: Map position failed:
37822 ERROR_MESS
37823
37824
37825 Stream: Reloader output.
37826
37827 Time: During volume reloading.
37828
37829 Meaning: An error was encountered during reload volume map
37830 construction. Reloading continues.
37831
37832 Action: No operator action is required.
37833
37834
37835
37836 rldr_vtoc_buffer_.pl1
37837 rldr_vtoc_buffer_: Unable to update vtoce WWW:
37838 ERROR_MESS
37839
37840
37841 Stream: Reloader output.
37842
37843 Time: During volume reloading.
37844
37845 Meaning: An error occurred updating a VTOCE. Reloading
37846 continues.
37847
37848 Action: No operator action is required.
37849
37850
37851
37852 rldr_vtoc_header_.pl1
37853 rldr_vtoc_header_: VTOC header position failed
37854
37855
37856 Stream: Reloader output.
37857
37858 Time: During volume reloading.
37859
37860 Meaning: An error occurred writing out the VTOC header for
37861 an output volume.
37862
37863 Action: Contact the system programming staff.
37864
37865
37866
37867
37868
37869
37870
37871
37872
37873
37874
37875 rldr_vtoc_header_ -653- MR12.5 10/27/92^L
37876
37877
37878 rldr_vtoc_header_.pl1
37879 rldr_vtoc_header_: VTOC header position failed
37880
37881
37882 Stream: Reloader output.
37883
37884 Time: During volume reloading.
37885
37886 Meaning: An error occurred writing out the VTOC header for
37887 an output volume.
37888
37889 Action: Contact the system programming staff.
37890
37891
37892
37893 rldr_vtoc_header_.pl1
37894 rldr_vtoc_header_: VTOC header read failed
37895
37896
37897 Stream: Reloader output.
37898
37899 Time: During volume reloading.
37900
37901 Meaning: An error occurred writing out the VTOC header for
37902 an output volume.
37903
37904 Action: Contact the system programming staff.
37905
37906
37907
37908 rldr_vtoc_header_.pl1
37909 rldr_vtoc_header_: VTOC header write failed
37910
37911
37912 Stream: Reloader output.
37913
37914 Time: During volume reloading.
37915
37916 Meaning: An error occurred writing out the VTOC header for
37917 an output volume.
37918
37919 Action: Contact the system programming staff.
37920
37921
37922
37923
37924
37925
37926
37927
37928
37929
37930
37931
37932
37933 rldr_vtoc_header_ -654- MR12.5 10/27/92^L
37934
37935
37936 rldr_vtoc_header_.pl1
37937 rldr_vtoc_header_: VTOC map position failed
37938
37939
37940 Stream: Reloader output.
37941
37942 Time: During volume reloading.
37943
37944 Meaning: An error occurred writing out the VTOC map for an
37945 output volume.
37946
37947 Action: Contact the system programming staff.
37948
37949
37950
37951 rldr_vtoc_header_.pl1
37952 rldr_vtoc_header_: VTOC map read failed
37953
37954
37955 Stream: Reloader output.
37956
37957 Time: During volume reloading.
37958
37959 Meaning: An error occurred reading the VTOC map for an
37960 output volume.
37961
37962 Action: Contact the system programming staff.
37963
37964
37965
37966 rldr_vtoc_header_.pl1
37967 rldr_vtoc_header_: VTOC map write failed
37968
37969
37970 Stream: Reloader output.
37971
37972 Time: During volume reloading.
37973
37974 Meaning: An error occurred writing out the VTOC map for an
37975 output volume.
37976
37977 Action: Contact the system programming staff.
37978
37979
37980
37981
37982
37983
37984
37985
37986
37987
37988
37989
37990
37991 rldr_vtoc_header_ -655- MR12.5 10/27/92^L
37992
37993
37994 salv_check_vtoce_.pl1
37995 salv_check_vtoce_: ERROR_MESSAGE.
37996
37997
37998 Stream: Logged in SYSERR log.
37999
38000 Time: Salvaging
38001
38002 Meaning: An error occurred while checking VTOCEs.
38003
38004 Action: Contact the system programming staff.
38005
38006
38007
38008 salv_dir_checker_.pl1
38009 salv_dir_checker_: MESSAGE.
38010
38011
38012 Stream: Logged in SYSERR log.
38013
38014 Time: Salvaging
38015
38016 Meaning: Various messages are printed by salv_dir_checker_
38017 indicating what salvaging is taking place--ACL
38018 counts being changed entry counts being changed
38019 unique names supplied for segments with invalid
38020 names etc.
38021
38022 Action: No operator action is required.
38023
38024
38025
38026 salv_dump_copy.pl1
38027 salv_dump_copy: Appending SEGNAME to dump
38028 directory ERRORMESSAGE
38029
38030
38031 Stream: Logged in SYSERR log.
38032
38033 Time: While system is running.
38034
38035 Meaning: The directory salvager could not append a copy of
38036 a directory being salvaged or the stack at the
38037 time of salvage to the system dump directory.
38038
38039 Action: Check the ACL on the system dump directory and
38040 site exec_coms which set it. Contact the system
38041 administrator.
38042
38043
38044
38045
38046
38047
38048
38049 salv_dump_copy -656- MR12.5 10/27/92^L
38050
38051
38052 salv_dump_copy.pl1
38053 salv_dump_copy: Initiating SEGNAME ERRORMESSAGE
38054
38055
38056 Stream: Logged in SYSERR log.
38057
38058 Time: While system is running.
38059
38060 Meaning: The directory salvager could not initiate a copy
38061 of a ring 0 stack or directory being salvaged in
38062 the system dump directory. There may be ACL
38063 problems in the system dump directory.
38064
38065 Action: Contact the system administrator.
38066
38067
38068
38069 salv_dump_copy.pl1
38070 salv_dump_copy: seg_fault_error copying PPPP into
38071 >dumps>SEGNAME
38072
38073
38074 Stream: Logged in SYSERR log.
38075
38076 Time: While system is running.
38077
38078 Meaning: The directory salvager attempted to create a copy
38079 of a segment in >dumps but encountered a
38080 seg_fault_error condition while attempting to copy
38081 it. This is probably caused by quota problems in
38082 >dumps or insufficient space on the logical
38083 volume.
38084
38085 Action: Contact the system administrator.
38086
38087
38088
38089 salv_caller.pl1
38090 salvage_dirs: decimal number required for level
38091 not BLAH
38092
38093
38094 Stream: Initializer process output.
38095
38096 Time: In response to an operator command.
38097
38098 Meaning: Incorrect arguments were specified.
38099
38100 Action: Enter a corrected command line.
38101
38102
38103
38104
38105
38106
38107 salvage_dirs -657- MR12.5 10/27/92^L
38108
38109
38110 salv_caller.pl1
38111 salvage_dirs: depth must be between 0 and 15
38112
38113
38114 Stream: Initializer process output.
38115
38116 Time: In response to an operator command.
38117
38118 Meaning: Incorrect arguments were specified.
38119
38120 Action: Enter a corrected command line.
38121
38122
38123
38124 salv_caller.pl1
38125 salvage_dirs: ERROR_MESSAGE
38126
38127
38128 Stream: Initializer process output.
38129
38130 Time: In response to an operator command.
38131
38132 Meaning: Incorrect arguments were specified.
38133
38134 Action: Enter a corrected command line.
38135
38136
38137
38138 salv_caller.pl1
38139 salvage_dirs: ERROR_MESSAGE. level number
38140 required
38141
38142
38143 Stream: Initializer process output.
38144
38145 Time: In response to an operator command.
38146
38147 Meaning: Incorrect arguments were specified.
38148
38149 Action: Enter a corrected command line.
38150
38151
38152
38153
38154
38155
38156
38157
38158
38159
38160
38161
38162
38163
38164
38165 salvage_dirs -658- MR12.5 10/27/92^L
38166
38167
38168 salv_caller.pl1
38169 salvage_dirs: Inconsistent arguments have been
38170 specified
38171
38172
38173 Stream: Initializer process output.
38174
38175 Time: In response to an operator command.
38176
38177 Meaning: Incorrect arguments were specified.
38178
38179 Action: Enter a corrected command line.
38180
38181
38182
38183 salv_caller.pl1
38184 salvage_dirs: must be in ring 1 for dir salv
38185
38186
38187 Stream: Initializer process output.
38188
38189 Time: In response to an operator command.
38190
38191 Meaning: Incorrect arguments were specified.
38192
38193 Action: Enter a corrected command line.
38194
38195
38196
38197 salv_caller.pl1
38198 salvage_dirs: Specified control argument is not
38199 implemented by this command. BLAH
38200
38201
38202 Stream: Initializer process output.
38203
38204 Time: In response to an operator command.
38205
38206 Meaning: Incorrect arguments were specified.
38207
38208 Action: Enter a corrected command line.
38209
38210
38211
38212
38213
38214
38215
38216
38217
38218
38219
38220
38221
38222
38223 salvage_dirs -659- MR12.5 10/27/92^L
38224
38225
38226 salv_caller.pl1
38227 salvage_dirs: VTOC checking is required for
38228 connection failure deletion.
38229
38230
38231 Stream: Initializer process output.
38232
38233 Time: In response to an operator command.
38234
38235 Meaning: An attempt was made to specify directory salvage
38236 with connection failure
38237 deletion but no VTOC checking.
38238
38239 Action: Enter a corrected command line.
38240
38241
38242
38243 salv_caller.pl1
38244 salvage_dirs: Will not salvage
38245
38246
38247 Stream: Initializer process output.
38248
38249 Time: In response to an operator command.
38250
38251 Meaning: Incorrect arguments were specified.
38252
38253 Action: Enter a corrected command line.
38254
38255
38256
38257 salv_caller.pl1
38258 salvage_dirs: will not salvage until root
38259 complete
38260
38261
38262 Stream: Initializer process output.
38263
38264 Time: In response to an operator command.
38265
38266 Meaning: Incorrect arguments were specified.
38267
38268 Action: Enter a corrected command line.
38269
38270
38271
38272
38273
38274
38275
38276
38277
38278
38279
38280
38281 salvage_dirs -660- MR12.5 10/27/92^L
38282
38283
38284 salvage_pv.pl1
38285 salvage_pv: Bit map size is DD. WWo words s/b
38286 EE. FFo changing to latter.
38287
38288
38289 Stream: Salvager output.
38290
38291 Time: During salvaging.
38292
38293 Meaning: The bit map size in the volume label was incorrect
38294 and has been corrected.
38295
38296 Action: No operator action is required.
38297
38298
38299
38300 salvage_pv.pl1
38301 salvage_pv: damaged switch found on for UUUU
38302 vtocx XXXo: NAME
38303
38304
38305 Stream: Salvager output.
38306
38307 Time: During salvaging.
38308
38309 Meaning: The segment originally named NAME with unique ID
38310 UUUU at vtoc index XXXo was found to have its
38311 damaged switch on. The damaged switch can be set
38312 during the running of the system if page control
38313 encounters an I/O error. Damaged segments cannot
38314 be used until the damaged switch is reset.
38315
38316 Action: No operator action is required.
38317
38318
38319
38320
38321
38322
38323
38324
38325
38326
38327
38328
38329
38330
38331
38332
38333
38334
38335
38336
38337
38338
38339 salvage_pv -661- MR12.5 10/27/92^L
38340
38341
38342 salvage_pv.pl1
38343 salvage_pv: DDD damaged segments on volume PVNAME
38344 NNN damaged in this salvage.
38345
38346
38347 Stream: BOS Typewriter.
38348
38349 Time: During salvaging.
38350
38351 Meaning: DDD damaged segments were found on the volume
38352 PVNAME which has just been volume-salvaged. The
38353 damaged switch was set for NNN of these segments
38354 during this volume salvage. The damaged switch
38355 for the other segments had been set prior to the
38356 salvage.
38357
38358 Action: Inspect the syserr and Answering Service log to
38359 identify damaged segments. Prepare to recover
38360 them if necessary.
38361
38362
38363
38364 salvage_pv.pl1
38365 salvage_pv: dirsw turned off for vtocx XXXo:
38366 NAME
38367
38368
38369 Stream: Salvager output.
38370
38371 Time: During salvaging.
38372
38373 Meaning: The segment originally named NAME at vtoc index
38374 XXXo has had its directory switch turned off.
38375
38376 Action: No operator action is required.
38377
38378
38379
38380
38381
38382
38383
38384
38385
38386
38387
38388
38389
38390
38391
38392
38393
38394
38395
38396
38397 salvage_pv -662- MR12.5 10/27/92^L
38398
38399
38400 salvage_pv.pl1
38401 salvage_pv: freeing UUUU deciduous vtocx XXXo:
38402 NAME
38403
38404
38405 Stream: Salvager output.
38406
38407 Time: During salvaging.
38408
38409 Meaning: The segment originally named NAME with unique ID
38410 UUUU at vtoc index XXXo was deciduous and has
38411 been deleted from the RPV. This is debugging
38412 output printed for system programmers if a SALV
38413 DEBG card is supplied.
38414
38415 Action: No operator action is required.
38416
38417
38418
38419 salvage_pv.pl1
38420 salvage_pv: freeing UUUU per process vtocx XXXo:
38421 NAME
38422
38423
38424 Stream: Salvager output.
38425
38426 Time: During salvaging.
38427
38428 Meaning: The segment originally named NAME with unique ID
38429 UUUU at vtoc index XXXo was per-process and has
38430 been deleted. This is debugging output printed
38431 for system programmers if a SALV DEBG card is
38432 used.
38433
38434 Action: No operator action is required.
38435
38436
38437
38438
38439
38440
38441
38442
38443
38444
38445
38446
38447
38448
38449
38450
38451
38452
38453
38454
38455 salvage_pv -663- MR12.5 10/27/92^L
38456
38457
38458 salvage_pv.pl1
38459 salvage_pv: freeing UUUU per-bootload vtocx XXXo:
38460 NAME
38461
38462
38463 Stream: Salvager output.
38464
38465 Time: During salvaging.
38466
38467 Meaning: The segment originally named NAME with unique ID
38468 UUU at vtoc index XXXo was per-bootload inferior
38469 to a prior >sl1 and has been deleted. This is
38470 debugging output printed for system programmers if
38471 a SALV DEBG card is supplied.
38472
38473 Action: No operator action is required.
38474
38475
38476
38477 salvage_pv.pl1
38478 salvage_pv: INIT_TABLES: aste pool WWWo too
38479 small.
38480
38481
38482 Stream: BOS Typewriter.
38483
38484 Time: While system is running.
38485
38486 Meaning: The physical volume salvager was unable to obtain
38487 a temporary AST entry for segment requiring WWWo
38488 ptws. No salvaging was done.
38489
38490 Action: Shut down manually correct the SST card and
38491 reboot. Then salvage all volumes since the
38492 indicator that volumes need salvaging may have
38493 been lost.
38494
38495
38496
38497
38498
38499
38500
38501
38502
38503
38504
38505
38506
38507
38508
38509
38510
38511
38512
38513 salvage_pv -664- MR12.5 10/27/92^L
38514
38515
38516 salvage_pv.pl1
38517 salvage_pv: Label times in advance of clock. The
38518 clock may be wrong.
38519
38520
38521 Stream: Salvager output.
38522
38523 Time: During salvaging.
38524
38525 Meaning: The label of the volume being salvaged contains
38526 one or more clock readings in advance of the
38527 current clock. Salvaging will proceed. The times
38528 are not corrected. If there is reason to believe
38529 that the system clock is incorrect shut the
38530 system down as soon as possible and take steps to
38531 recover that part of the hierarchy which may have
38532 been contaminated with bad clock values.
38533
38534 Action: No operator action is required.
38535
38536
38537
38538 salvage_pv.pl1
38539 salvage_pv: map of assigned addresses changed.
38540
38541
38542 Stream: Salvager output.
38543
38544 Time: During salvaging.
38545
38546 Meaning: If any corrections were made to the map on the
38547 volume which shows which addresses are free and
38548 which are in use this message is printed. If the
38549 volume was not properly shut down this message is
38550 to be expected.
38551
38552 Action: No operator action is required.
38553
38554
38555
38556 salvage_pv.pl1
38557 salvage_pv: NN free vtoces added to free list.
38558
38559
38560 Stream: Salvager output.
38561
38562 Time: During salvaging.
38563
38564 Meaning: NN free VTOC entries were found while salvaging
38565 and added to the list of free VTOC entries. This
38566 is a normal message.
38567
38568 Action: No operator action is required.
38569
38570
38571 salvage_pv -665- MR12.5 10/27/92^L
38572
38573
38574 salvage_pv.pl1
38575 salvage_pv: no. of free recs changed from OLD to
38576 NEW dec.
38577
38578
38579 Stream: Salvager output.
38580
38581 Time: During salvaging.
38582
38583 Meaning: If the number of free records in the volume label
38584 is changed by a volume salvage this message is
38585 printed. If the volume was not properly shut
38586 down this message is to be expected.
38587
38588 Action: No operator action is required.
38589
38590
38591
38592 salvage_pv.pl1
38593 salvage_pv: no. of free vtoces changed from OLD
38594 to NEW dec.
38595
38596
38597 Stream: Salvager output.
38598
38599 Time: During salvaging.
38600
38601 Meaning: If the number of free VTOC entries in the volume
38602 label is changed by a volume salvage this message
38603 is printed.
38604
38605 Action: No operator action is required.
38606
38607
38608
38609 salvage_pv.pl1
38610 salvage_pv: setting damaged switch on PRIMARYNAME
38611 VTOCXo on pv PVNAME.
38612
38613
38614 Stream: Logged in SYSERR log.
38615
38616 Time: During salvaging.
38617
38618 Meaning: The volume salvager has discovered possible damage
38619 to a segment and has turned on the damaged switch.
38620
38621 Action: No operator action is required. This message is
38622 logged in order to trigger automatic processing of
38623 damaged segments.
38624
38625
38626
38627
38628
38629 salvage_pv -666- MR12.5 10/27/92^L
38630
38631
38632 salvage_pv.pl1
38633 salvage_pv: Volume salvage finished with errors.
38634
38635
38636 Stream: Salvager output.
38637
38638 Time: During salvaging.
38639
38640 Meaning: Volume salvage finished with errors.
38641
38642 Action: Contact the system programming staff.
38643
38644
38645
38646 salvage_pv.pl1
38647 salvage_pv: Volume salvage finished.
38648
38649
38650 Stream: Salvager output.
38651
38652 Time: During salvaging.
38653
38654 Meaning: Volume salvage finished.
38655
38656 Action: No operator action is required.
38657
38658
38659
38660 salvage_pv.pl1
38661 salvage_pv: Volume salvage of dskX_NNs volume
38662 PVNAME of logical vol LVNAME.
38663
38664
38665 Stream: Salvager output.
38666
38667 Time: During salvaging.
38668
38669 Meaning: This message is printed when volume salvaging
38670 begins.
38671
38672 Action: No operator action is required.
38673
38674
38675
38676
38677
38678
38679
38680
38681
38682
38683
38684
38685
38686
38687 salvage_pv -667- MR12.5 10/27/92^L
38688
38689
38690 salvage_pv.pl1
38691 salvage_pv: VTOC conversion finished with errors.
38692
38693
38694 Stream: Salvager output.
38695
38696 Time: During salvaging.
38697
38698 Meaning: VTOC conversion finished with errors.
38699
38700 Action: Contact the system programming staff.
38701
38702
38703
38704 salvage_pv.pl1
38705 salvage_pv: VTOC conversion finished.
38706
38707
38708 Stream: Salvager output.
38709
38710 Time: During salvaging.
38711
38712 Meaning: VTOC conversion finished.
38713
38714 Action: No operator action is required.
38715
38716
38717
38718 salvage_pv.pl1
38719 salvage_pv: VTOC Conversion of dskX_NNs volume
38720 PVNAME of logical vol LVNAME.
38721
38722
38723 Stream: Salvager output.
38724
38725 Time: During salvaging.
38726
38727 Meaning: This message is printed when a pre-MR10 disk pack
38728 is first mounted on an MR10 or later system. The
38729 equivalent of a salvage is being done to create
38730 the VTOC Map which did not exist prior to MR10.
38731
38732 Action: No operator action is required.
38733
38734
38735
38736
38737
38738
38739
38740
38741
38742
38743
38744
38745 salvage_pv -668- MR12.5 10/27/92^L
38746
38747
38748 salvage_pv.pl1
38749 salvage_pv: vtoce NAME at XXXo: cur len changed
38750 from OLD to NEW octal
38751
38752
38753 Stream: Salvager output.
38754
38755 Time: During salvaging.
38756
38757 Meaning: The segment originally named NAME at vtoc index
38758 XXXo had a current length which did not agree with
38759 the file map. The current length was corrected
38760 and the damaged switch set on the segment. This
38761 message usually indicates that a segment was
38762 damaged before a crash by failure to write out its
38763 pages to disk before the crash. The segment may
38764 have to be recovered.
38765
38766 Action: No operator action is required.
38767
38768
38769
38770 salvage_pv.pl1
38771 salvage_pv: vtoce NAME at XXXo: max len changed
38772 from OLD to NEW octal.
38773
38774
38775 Stream: Salvager output.
38776
38777 Time: During salvaging.
38778
38779 Meaning: The segment originally named NAME at vtoc index
38780 XXXo had a maximum segment length which did not
38781 agree with the file map or was less than the
38782 current length. The maximum length was corrected
38783 and the damaged switch set.
38784
38785 Action: No operator action is required.
38786
38787
38788
38789
38790
38791
38792
38793
38794
38795
38796
38797
38798
38799
38800
38801
38802
38803 salvage_pv -669- MR12.5 10/27/92^L
38804
38805
38806 salvage_pv.pl1
38807 salvage_pv: vtoce NAME at XXXo: page PPPo
38808 disk_addr DDDDo bad.
38809
38810
38811 Stream: Salvager output.
38812
38813 Time: During salvaging.
38814
38815 Meaning: The segment originally named NAME at vtoc index
38816 XXXo had an invalid disk address DDDDo for page
38817 PPPo. The address is nulled causing a page of
38818 zeroes and the damaged switch set.
38819
38820 Action: No operator action is required.
38821
38822
38823
38824 salvage_pv.pl1
38825 salvage_pv: vtoce NAME at XXXo: rec used changed
38826 from OLD to NEW octal.
38827
38828
38829 Stream: Salvager output.
38830
38831 Time: During salvaging.
38832
38833 Meaning: The segment originally named NAME at vtoc index
38834 XXXo had a records used which did not agree with
38835 the file map. The records used field was
38836 corrected and the damaged switch set. This
38837 message usually indicates that a segment was
38838 damaged before a crash by failure to write out its
38839 pages to disk before the crash. The segment may
38840 have to be recovered.
38841
38842 Action: No operator action is required.
38843
38844
38845
38846
38847
38848
38849
38850
38851
38852
38853
38854
38855
38856
38857
38858
38859
38860
38861 salvage_pv -670- MR12.5 10/27/92^L
38862
38863
38864 salvage_pv.pl1
38865 salvage_pv: vtoce NAME at XXXo: ref to pageno
38866 PPo at addr DDDDo deleted dirsw is X.
38867
38868
38869 Stream: Salvager output.
38870
38871 Time: During salvaging.
38872
38873 Meaning: The segment originally named NAME at vtoc index
38874 XXXo had a reused address conflict with another
38875 segment. The page reference was determined to be
38876 incorrect and a null address placed in the
38877 segment's file map causing a page of zeroes and
38878 the damaged switch set. This message may be
38879 symptomatic of disk or other hardware problems.
38880
38881 Action: No operator action is required.
38882
38883
38884
38885 salvage_pv.pl1
38886 salvage_pv: vtoce NAME at XXXo:
38887 time-record-product reset to zero.
38888
38889
38890 Stream: Salvager output.
38891
38892 Time: During salvaging.
38893
38894 Meaning: The segment originally named NAME at vtoc index
38895 XXXo had an invalid value for one of the
38896 time-record-product fields. All
38897 time-record-product fields have been reset to
38898 zero.
38899
38900 Action: No operator action is required.
38901
38902
38903
38904 salvage_pv.pl1
38905 salvage_pv: vtoce XXXo free but not zero.
38906
38907
38908 Stream: Salvager output.
38909
38910 Time: During salvaging.
38911
38912 Meaning: The VTOC entry with index XXXo was marked free but
38913 was not all zero. It was zeroed and made free.
38914
38915 Action: No operator action is required.
38916
38917
38918
38919 salvage_pv -671- MR12.5 10/27/92^L
38920
38921
38922 salv_caller.pl1
38923 salvage_vol: -all and -copy arguments cannot be
38924 used together
38925
38926
38927 Stream: Initializer process output.
38928
38929 Time: In response to an operator command.
38930
38931 Meaning: Incorrect arguments were specified.
38932
38933 Action: Enter a corrected command line.
38934
38935
38936
38937 salv_caller.pl1
38938 salvage_vol: ERROR_MESSAGE
38939
38940
38941 Stream: Initializer process output.
38942
38943 Time: In response to an operator command.
38944
38945 Meaning: Incorrect arguments were specified.
38946
38947 Action: Enter a corrected command line.
38948
38949
38950
38951 salv_caller.pl1
38952 salvage_vol: ERROR_MESSAGE. need copy drive name
38953
38954
38955 Stream: Initializer process output.
38956
38957 Time: In response to an operator command.
38958
38959 Meaning: Incorrect arguments were specified.
38960
38961 Action: Enter a corrected command line.
38962
38963
38964
38965
38966
38967
38968
38969
38970
38971
38972
38973
38974
38975
38976
38977 salvage_vol -672- MR12.5 10/27/92^L
38978
38979
38980 salv_caller.pl1
38981 salvage_vol: Expected argument missing. first
38982 two args must be phys vol name and drive name
38983
38984
38985 Stream: Initializer process output.
38986
38987 Time: In response to an operator command.
38988
38989 Meaning: Incorrect arguments were specified.
38990
38991 Action: Enter a corrected command line.
38992
38993
38994
38995 salv_caller.pl1
38996 salvage_vol: Inconsistent arguments have been
38997 specified
38998
38999
39000 Stream: Initializer process output.
39001
39002 Time: In response to an operator command.
39003
39004 Meaning: Incorrect arguments were specified.
39005
39006 Action: Enter a corrected command line.
39007
39008
39009
39010 salv_caller.pl1
39011 salvage_vol: no drive may be specified for -all
39012
39013
39014 Stream: Initializer process output.
39015
39016 Time: In response to an operator command.
39017
39018 Meaning: Incorrect arguments were specified.
39019
39020 Action: Enter a corrected command line.
39021
39022
39023
39024
39025
39026
39027
39028
39029
39030
39031
39032
39033
39034
39035 salvage_vol -673- MR12.5 10/27/92^L
39036
39037
39038 salv_caller.pl1
39039 salvage_vol: Specified control argument is not
39040 implemented by this command. BLAH
39041
39042
39043 Stream: Initializer process output.
39044
39045 Time: In response to an operator command.
39046
39047 Meaning: Incorrect arguments were specified.
39048
39049 Action: Enter a corrected command line.
39050
39051
39052
39053 bce_save.pl1
39054 savecheck_status: Special Interrupt:
39055 STATUS_WORD
39056
39057
39058 Stream: BOS Typewriter.
39059
39060 Time: System Intialization.
39061
39062 Meaning: An unexpected special interrupt has been detected.
39063
39064 Action: No operator action is required.
39065
39066
39067
39068 bce_save.pl1
39069 savecheck_status: Time-Out on TAPE_DEV
39070
39071
39072 Stream: BOS Typewriter.
39073
39074 Time: System Intialization.
39075
39076 Meaning: An I/O that was issued to the tape device has
39077 timed-out.
39078
39079 Action: Follow normal recovery procedures.
39080
39081
39082
39083
39084
39085
39086
39087
39088
39089
39090
39091
39092
39093 savecheck_status -674- MR12.5 10/27/92^L
39094
39095
39096 bce_save.pl1
39097 saveTAPE_SET: Unrecoverable MAJOR_STATUS
39098 SUB_STATUS on TAPE_DEV.
39099
39100
39101 Stream: BOS Typewriter.
39102
39103 Time: System Intialization.
39104
39105 Meaning: An unrecoverable error has occured while
39106 attempting to do I/O to the tape device.
39107
39108 Action: Follow normal recovery procedures.
39109
39110
39111
39112 bce_save.pl1
39113 saveTAPE_SET: Device TAPE_DEV is being removed
39114 from the tape device list.
39115
39116
39117 Stream: BOS Typewriter.
39118
39119 Time: System Intialization.
39120
39121 Meaning: The TAPE_DEV has returned a status indicating that
39122 it is unable to be used.
39123
39124 Action: No operator action is required.
39125
39126
39127
39128 bce_save.pl1
39129 saveTAPE_SET: Error tape on TAPE_DEV is part
39130 of the "OTHER_TAPE_SET" set.
39131
39132
39133 Stream: BOS Typewriter.
39134
39135 Time: System Intialization.
39136
39137 Meaning: The tape just read is not part of this tape set.
39138
39139 Action: Mount a tape on the device that is part of this
39140 tape set.
39141
39142
39143
39144
39145
39146
39147
39148
39149
39150
39151 saveTAPE_SET -675- MR12.5 10/27/92^L
39152
39153
39154 bce_save.pl1
39155 saveTAPE_SET: Incorrect tape sequence number
39156 detected.
39157 was REC_NUM s/b REC_NUM. Forcing restart of this
39158 tape set.
39159
39160
39161 Stream: BOS Typewriter sounds beeper
39162
39163 Time: System Intialization.
39164
39165 Meaning: A sequence error was detected in the tape record
39166 number. This indicates a logic error in the
39167 supervisor or CPU or memory hardware problems.
39168
39169 Action: Follow normal save restart procedures. Contact
39170 the system programming staff.
39171
39172
39173
39174 bce_save.pl1
39175 saveTAPE_SET: MAJOR_STATUS SUB_STATUS on
39176 TAPE_DEV.
39177
39178
39179 Stream: BOS Typewriter.
39180
39181 Time: System Intialization.
39182
39183 Meaning: An error has occured while attempting to do I/O to
39184 the tape device.
39185
39186 Action: Follow normal recovery procedures.
39187
39188
39189
39190 bce_save_util_.pl1
39191 saveTAPE_SET: MULTICS_VOL_ID PV_NAME on
39192 DISK_DEV
39193 Last updated: DATE_TIME
39194
39195
39196 Stream: BOS Typewriter.
39197
39198 Time: System Intialization.
39199
39200 Meaning: Just an informative message.
39201
39202 Action: No operator action is required.
39203
39204
39205
39206
39207
39208
39209 saveTAPE_SET -676- MR12.5 10/27/92^L
39210
39211
39212 bce_save.pl1
39213 saveTAPE_SET: No Physical Volumes left to save.
39214
39215
39216 Stream: BOS Typewriter.
39217
39218 Time: System Intialization.
39219
39220 Meaning: For various reasons all of the physical volumes
39221 have been removed from the list of volumes.
39222
39223 Action: No operator action is required.
39224
39225
39226
39227 bce_save.pl1
39228 saveTAPE_SET: No room to describe PV PV_NAME
39229 for part PARTITION_NAME.
39230
39231
39232 Stream: BOS Typewriter.
39233
39234 Time: System Intialization.
39235
39236 Meaning: The maximum number of physical volumes that can be
39237 handled by the program has been exceeded.
39238
39239 Action: The number of physical volumes defined in the
39240 control files must be reduced.
39241
39242
39243
39244 bce_save.pl1
39245 saveTAPE_SET: No usable tape devices left in
39246 list.
39247
39248
39249 Stream: BOS Typewriter.
39250
39251 Time: System Intialization.
39252
39253 Meaning: For various reasons all of the tape devices have
39254 been removed from the list of available devices
39255 for this tape set.
39256
39257 Action: Follow normal recovery procedures.
39258
39259
39260
39261
39262
39263
39264
39265
39266
39267 saveTAPE_SET -677- MR12.5 10/27/92^L
39268
39269
39270 bce_save.pl1
39271 saveTAPE_SET: No usable tape drives left.
39272
39273
39274 Stream: BOS Typewriter.
39275
39276 Time: System Intialization.
39277
39278 Meaning: For various reasons all of the tape devices have
39279 been removed from the list of available devices
39280 for this tape set.
39281
39282 Action: Follow normal recovery procedures.
39283
39284
39285
39286 bce_save_util_.pl1
39287 saveTAPE_SET: Partition PARTITION_NAME is not
39288 defined on PV_NAME.
39289
39290
39291 Stream: BOS Typewriter.
39292
39293 Time: System Intialization.
39294
39295 Meaning: A request to save specific partition has been
39296 made but the partition does not exist of the PV.
39297
39298 Action: Correct the control files accordingly.
39299
39300
39301
39302 bce_save_util_.pl1
39303 saveTAPE_SET: Partition PARTITION_NAME of
39304 volume PV_NAME
39305 is not defined in the restart tape
39306 label.
39307
39308
39309 Stream: BOS Typewriter.
39310
39311 Time: System Intialization.
39312
39313 Meaning: There is an inconsistency between the restart tape
39314 and the save control files.
39315
39316 Action: Either correct the control files or start the
39317 save over from the beginning.
39318
39319
39320
39321
39322
39323
39324
39325 saveTAPE_SET -678- MR12.5 10/27/92^L
39326
39327
39328 bce_save.pl1
39329 saveTAPE_SET: Partition PARTITION_NAME on
39330 PV_NAME record REC_NUM on tape# TAPE_NUMBER
39331 TAPE_DEV
39332
39333
39334 Stream: BOS Typewriter.
39335
39336 Time: System Intialization.
39337
39338 Meaning: Just an informative message.
39339
39340 Action: No operator action is required.
39341
39342
39343
39344 bce_save.pl1
39345 saveTAPE_SET: Partition PARTITION_NAME record
39346 REC_NUM on tape# TAPE_NUMBER TAPE_DEV
39347
39348
39349 Stream: BOS Typewriter.
39350
39351 Time: System Intialization.
39352
39353 Meaning: Just an informative message.
39354
39355 Action: No operator action is required.
39356
39357
39358
39359 bce_save.pl1
39360 saveTAPE_SET: Please mount tape# TAPE_NUMBER on
39361 TAPE_DEV.
39362
39363
39364 Stream: BOS Typewriter sounds beeper
39365
39366 Time: System Intialization.
39367
39368 Meaning: Just an informative message.
39369
39370 Action: Mount tape on the device.
39371
39372
39373
39374
39375
39376
39377
39378
39379
39380
39381
39382
39383 saveTAPE_SET -679- MR12.5 10/27/92^L
39384
39385
39386 bce_save.pl1
39387 saveTAPE_SET: Please mount the "Info" tape on
39388 TAPE_DEV.
39389
39390
39391 Stream: BOS Typewriter sounds beeper
39392
39393 Time: System Intialization.
39394
39395 Meaning: Just an informative message.
39396
39397 Action: Mount the tape on the device.
39398
39399
39400
39401 bce_save.pl1
39402 saveTAPE_SET: Please mount the "restart" tape
39403 on TAPE_DEV.
39404
39405
39406 Stream: BOS Typewriter sounds beeper
39407
39408 Time: System Intialization.
39409
39410 Meaning: Just an informative message.
39411
39412 Action: Mount the tape on the device.
39413
39414
39415
39416 bce_save.pl1
39417 saveTAPE_SET: Remount tape# TAPE_NUMBER WITH
39418 write ring on TAPE_DEV.
39419
39420
39421 Stream: BOS Typewriter sounds beeper
39422
39423 Time: System Intialization.
39424
39425 Meaning: The tape is currently mounted without a write ring
39426 present.
39427
39428 Action: Remount tape with write permit ring in place.
39429
39430
39431
39432
39433
39434
39435
39436
39437
39438
39439
39440
39441 saveTAPE_SET -680- MR12.5 10/27/92^L
39442
39443
39444 bce_save_util_.pl1
39445 saveTAPE_SET: Removing volume PV_NAME from PV
39446 list
39447 because all partitions were removed.
39448
39449
39450 Stream: BOS Typewriter.
39451
39452 Time: System Intialization.
39453
39454 Meaning: It is nolonger necessary for the program to keep
39455 track of the PV since all of the partition
39456 requests have been removed.
39457
39458 Action: Correct the control files accordingly.
39459
39460
39461
39462 bce_save_util_.pl1
39463 saveTAPE_SET: Removing volume PV_NAME from PV
39464 list
39465 because there are no partitions to save.
39466
39467
39468 Stream: BOS Typewriter.
39469
39470 Time: System Intialization.
39471
39472 Meaning: Only partition requests were made for this volume
39473 and now for various reasons there are none left to
39474 save.
39475
39476 Action: Follow normal recovery procedures.
39477
39478
39479
39480 bce_save_util_.pl1
39481 saveTAPE_SET: Reverting "-all" partition
39482 request
39483 for volume PV_NAME because there are no
39484 partitions to save.
39485
39486
39487 Stream: BOS Typewriter.
39488
39489 Time: System Intialization.
39490
39491 Meaning: This PV_NAME has no partitions defined.
39492
39493 Action: No operator action is required.
39494
39495
39496
39497
39498
39499 saveTAPE_SET -681- MR12.5 10/27/92^L
39500
39501
39502 bce_save.pl1
39503 saveTAPE_SET: save complete...
39504
39505
39506 Stream: BOS Typewriter.
39507
39508 Time: System Intialization.
39509
39510 Meaning: Just an informative message.
39511
39512 Action: No operator action is required.
39513
39514
39515
39516 bce_save.pl1
39517 saveTAPE_SET: Skipping volume PV_NAME on
39518 DISK_DEV save complete.
39519
39520
39521 Stream: BOS Typewriter.
39522
39523 Time: System Intialization.
39524
39525 Meaning: Just an informative message.
39526
39527 Action: No operator action is required.
39528
39529
39530
39531 bce_save.pl1
39532 saveTAPE_SET: Starting from volume PV_NAME on
39533 DISK_DEV.
39534
39535
39536 Stream: BOS Typewriter.
39537
39538 Time: System Intialization.
39539
39540 Meaning: Just an informative message.
39541
39542 Action: No operator action is required.
39543
39544
39545
39546
39547
39548
39549
39550
39551
39552
39553
39554
39555
39556
39557 saveTAPE_SET -682- MR12.5 10/27/92^L
39558
39559
39560 bce_save.pl1
39561 saveTAPE_SET: Tape on TAPE_DEV does not contain
39562 a supported tape label version.
39563
39564
39565 Stream: BOS Typewriter.
39566
39567 Time: System Intialization.
39568
39569 Meaning: The tape contains a tape version identifier that
39570 is nolonger supported.
39571
39572 Action: Use the "restore -display_info_tape tapX_NN"
39573 option to display the tape.
39574
39575
39576
39577 bce_save.pl1
39578 saveTAPE_SET: Tape on TAPE_DEV does not contain
39579 a valid label.
39580
39581
39582 Stream: BOS Typewriter.
39583
39584 Time: System Intialization.
39585
39586 Meaning: The tape just read is not a valid save/restore
39587 tape.
39588
39589 Action: Follow normal recovery procedures.
39590
39591
39592
39593 bce_save.pl1
39594 saveTAPE_SET: Tape on TAPE_DEV is not part of
39595 this set.
39596
39597
39598 Stream: BOS Typewriter.
39599
39600 Time: System Intialization.
39601
39602 Meaning: The tape just read contains a different tape set
39603 name than what is currently being handled via the
39604 control file.
39605
39606 Action: Follow normal recovery procedures.
39607
39608
39609
39610
39611
39612
39613
39614
39615 saveTAPE_SET -683- MR12.5 10/27/92^L
39616
39617
39618 bce_save_util_.pl1
39619 saveTAPE_SET: Tape subsystem "SUB_SYS" is not
39620 defined in the config.
39621
39622
39623 Stream: BOS Typewriter.
39624
39625 Time: System Intialization.
39626
39627 Meaning: No "prph" entry could be found for the tape
39628 subsystem.
39629
39630 Action: Correct config_deck or save/restore control
39631 files to indicate proper tape subsystem.
39632
39633
39634
39635 bce_save.pl1
39636 saveTAPE_SET: Tape# TAPE_NUMBER on TAPE_DEV
39637 created DATE_TIME
39638
39639
39640 Stream: BOS Typewriter.
39641
39642 Time: System Intialization.
39643
39644 Meaning: Just an informative message.
39645
39646 Action: No operator action is required.
39647
39648
39649
39650 bce_save_util_.pl1
39651 saveTAPE_SET: The "conf" partition of rpv is
39652 not being saved.
39653
39654
39655 Stream: BOS Typewriter.
39656
39657 Time: System Intialization.
39658
39659 Meaning: Just an informative message.
39660
39661 Action: Add the request to the save control file if
39662 desired.
39663
39664
39665
39666
39667
39668
39669
39670
39671
39672
39673 saveTAPE_SET -684- MR12.5 10/27/92^L
39674
39675
39676 bce_save_util_.pl1
39677 saveTAPE_SET: The "file" partition of rpv is
39678 not being saved.
39679
39680
39681 Stream: BOS Typewriter.
39682
39683 Time: System Intialization.
39684
39685 Meaning: Just an informative message.
39686
39687 Action: Add the request to the save control file if
39688 desired.
39689
39690
39691
39692 bce_save_util_.pl1
39693 saveTAPE_SET: The "log" partition of rpv is not
39694 being saved.
39695
39696
39697 Stream: BOS Typewriter.
39698
39699 Time: System Intialization.
39700
39701 Meaning: Just an informative message.
39702
39703 Action: Add the request to the save control file if
39704 desired.
39705
39706
39707
39708 bce_save.pl1
39709 saveTAPE_SET: The following tape devices will
39710 be used:
39711
39712
39713 Stream: BOS Typewriter.
39714
39715 Time: System Intialization.
39716
39717 Meaning: Just an informative message.
39718
39719 Action: No operator action is required.
39720
39721
39722
39723
39724
39725
39726
39727
39728
39729
39730
39731 saveTAPE_SET -685- MR12.5 10/27/92^L
39732
39733
39734 bce_save.pl1
39735 saveTAPE_SET: This tape is older than one week.
39736 Tape rejected.
39737
39738
39739 Stream: BOS Typewriter.
39740
39741 Time: System Intialization.
39742
39743 Meaning: A restart of a save is being attempted but the
39744 tape used as the restart tape is older than one
39745 week.
39746
39747 Action: Restart with a later tape or start the save from
39748 the beginning.
39749
39750
39751
39752 bce_save.pl1
39753 saveTAPE_SET: This tape starts with volume
39754 PV_NAME which was not defined. Tape rejected.
39755
39756
39757 Stream: BOS Typewriter.
39758
39759 Time: System Intialization.
39760
39761 Meaning: A save restart is being attempted with a tape that
39762 begins with a PV that has not been defined in the
39763 save control files.
39764
39765 Action: Follow normal recovery procedures.
39766
39767
39768
39769 bce_save.pl1
39770 saveTAPE_SET: Time-out waiting for special
39771 interrupt.
39772
39773
39774 Stream: BOS Typewriter.
39775
39776 Time: System Intialization.
39777
39778 Meaning: The program was waiting for a special to come from
39779 the device but none was recieved in the alloted
39780 time.
39781
39782 Action: Follow normal recovery procedures.
39783
39784
39785
39786
39787
39788
39789 saveTAPE_SET -686- MR12.5 10/27/92^L
39790
39791
39792 bce_save_util_.pl1
39793 saveTAPE_SET: Type of data being saved for
39794 volume PV_NAME
39795 does not match the type in the restart
39796 tape label.
39797
39798
39799 Stream: BOS Typewriter.
39800
39801 Time: System Intialization.
39802
39803 Meaning: There is an inconsistency between the restart tape
39804 and the save control files.
39805
39806 Action: Either correct the control files or start the
39807 save over from the beginning.
39808
39809
39810
39811 bce_save_util_.pl1
39812 saveTAPE_SET: Unable to save "PARTITION_NAME"
39813 partition.
39814 Internal partition list full.
39815
39816
39817 Stream: BOS Typewriter.
39818
39819 Time: System Intialization.
39820
39821 Meaning: More partitions have been requested than the
39822 program can handle.
39823
39824 Action: Change control files to reduce the number defined
39825 possibly by breaking them up into seperate tape
39826 sets.
39827
39828
39829
39830 bce_save_util_.pl1
39831 saveTAPE_SET: Unable to save "PARTITION_NAME"
39832 partition.
39833 N partitions already defined
39834
39835
39836 Stream: BOS Typewriter.
39837
39838 Time: System Intialization.
39839
39840 Meaning: An attempt has been made to save more than the N
39841 maximum partitions allowed.
39842
39843 Action: Change control filess to reduce the number
39844 requested.
39845
39846
39847 saveTAPE_SET -687- MR12.5 10/27/92^L
39848
39849
39850 bce_save.pl1
39851 saveTAPE_SET: Unable to set density on
39852 TAPE_DEV.
39853
39854
39855 Stream: BOS Typewriter.
39856
39857 Time: System Intialization.
39858
39859 Meaning: The program was unable to set the required density
39860 of the tape device.
39861
39862 Action: Follow normal recovery procedures.
39863
39864
39865
39866 bce_save.pl1
39867 saveTAPE_SET: Unloading "Info" tape from
39868 TAPE_DEV REC_CNT records ERR_CNT errors
39869
39870
39871 Stream: BOS Typewriter.
39872
39873 Time: System Intialization.
39874
39875 Meaning: Just an informative message.
39876
39877 Action: No operator action is required.
39878
39879
39880
39881 bce_save.pl1
39882 saveTAPE_SET: Unloading tape# TAPE_NUMBER from
39883 TAPE_DEV REC_CNT records ERR_CNT errors
39884
39885
39886 Stream: BOS Typewriter.
39887
39888 Time: System Intialization.
39889
39890 Meaning: Just an informative message.
39891
39892 Action: No operator action is required.
39893
39894
39895
39896
39897
39898
39899
39900
39901
39902
39903
39904
39905 saveTAPE_SET -688- MR12.5 10/27/92^L
39906
39907
39908 bce_save.pl1
39909 saveTAPE_SET: Unloading TAPE_DEV REC_CNT
39910 records ERR_CNT errors
39911
39912
39913 Stream: BOS Typewriter.
39914
39915 Time: System Intialization.
39916
39917 Meaning: Just an informative message.
39918
39919 Action: No operator action is required.
39920
39921
39922
39923 bce_save_util_.pl1
39924 saveTAPE_SET: Volume on DISK_DEV is not a
39925 MULTICS_VOL_ID.
39926
39927
39928 Stream: BOS Typewriter.
39929
39930 Time: System Intialization.
39931
39932 Meaning: The volume to be saved is not a valid Multics
39933 volume and therefore cannot be saved.
39934
39935 Action: Follow normal recovery procedures.
39936
39937
39938
39939 bce_save_util_.pl1
39940 saveTAPE_SET: Volume PV_NAME not found in
39941 restart tape label.
39942
39943
39944 Stream: BOS Typewriter.
39945
39946 Time: System Intialization.
39947
39948 Meaning: There is an inconsistency between the restart tape
39949 and the save control files.
39950
39951 Action: Either correct the control files or start the
39952 save over from the beginning.
39953
39954
39955
39956
39957
39958
39959
39960
39961
39962
39963 saveTAPE_SET -689- MR12.5 10/27/92^L
39964
39965
39966 bce_save_util_.pl1
39967 saveTAPE_SET: Volume PV_NAME requires
39968 salvaging.
39969 Setting -all to save all paging records
39970 on the volume.
39971
39972
39973 Stream: BOS Typewriter.
39974
39975 Time: System Intialization.
39976
39977 Meaning: Just an informative message.
39978
39979 Action: No operator action is required.
39980
39981
39982
39983 bce_save_util_.pl1
39984 saveTAPE_SET: Volume PV_NAME's PVID does not
39985 match
39986 the one in the restart tape label.
39987
39988
39989 Stream: BOS Typewriter.
39990
39991 Time: System Intialization.
39992
39993 Meaning: There is an inconsistency between what is on the
39994 restart tape and what is currently defined on the
39995 PV's disk label.
39996
39997 Action: Start the save over from the beginning.
39998
39999
40000
40001 bce_save.pl1
40002 saveTAPE_SET: Volume PV_NAME record REC_NUM
40003 on tape# TAPE_NUMBER TAPE_DEV
40004
40005
40006 Stream: BOS Typewriter.
40007
40008 Time: System Intialization.
40009
40010 Meaning: Just an informative message.
40011
40012 Action: No operator action is required.
40013
40014
40015
40016
40017
40018
40019
40020
40021 saveTAPE_SET -690- MR12.5 10/27/92^L
40022
40023
40024 bce_save_util_.pl1
40025 saveTAPE_SET: Volume was expected to be
40026 PV_NAME.
40027
40028
40029 Stream: BOS Typewriter.
40030
40031 Time: System Intialization.
40032
40033 Meaning: The PV name read from the disk label does not
40034 match the PV name that was defined in the save
40035 control files.
40036
40037 Action: Correct the control file to show the proper PV
40038 name mounted on the device.
40039
40040
40041
40042 bce_save.pl1
40043 saveTAPE_SET: Waiting for special on TAPE_DEV.
40044
40045
40046 Stream: BOS Typewriter.
40047
40048 Time: System Intialization.
40049
40050 Meaning: Just an informative message.
40051
40052 Action: No operator action is required.
40053
40054
40055
40056 bce_save_util_.pl1
40057 save: Attaching TAPE_DEV. ERR_MESSAGE
40058
40059
40060 Stream: BOS Typewriter sounds beeper
40061
40062 Time: System Intialization.
40063
40064 Meaning: IOI has returned a non-zero error code in response
40065 to a request to assign TAPE_DEV.
40066
40067 Action: Follow normal recovery procedures.
40068
40069
40070
40071
40072
40073
40074
40075
40076
40077
40078
40079 save -691- MR12.5 10/27/92^L
40080
40081
40082 bce_save.pl1
40083 save: bce_ioi_post_seg. ERR_MESSAGE
40084
40085
40086 Stream: BOS Typewriter sounds beeper
40087
40088 Time: System Intialization.
40089
40090 Meaning: The program was unable to get a pointer to the
40091 above segment. This indicates a logic error in
40092 the supervisor or CPU or memory hardware
40093 problems.
40094
40095 Action: Contact the system programming staff.
40096
40097
40098
40099 bce_save.pl1
40100 save: bootload_disk_post_seg. ERR_MESSAGE
40101
40102
40103 Stream: BOS Typewriter sounds beeper
40104
40105 Time: System Intialization.
40106
40107 Meaning: The program was unable to get a pointer to the
40108 above segment. This indicates a logic error in
40109 the supervisor or CPU or memory hardware
40110 problems.
40111
40112 Action: Contact the system programming staff.
40113
40114
40115
40116 bce_save_util_.pl1
40117 save: Could not read label of PV_NAME on
40118 DISK_DEV. ERR_MESSAGE
40119
40120
40121 Stream: BOS Typewriter sounds beeper
40122
40123 Time: System Intialization.
40124
40125 Meaning: The volume label of the PV could not be read due
40126 to the error given in ERR_MESSAGE.
40127
40128 Action: A operator query is done to find out if the read
40129 should be retried or the PV removed from the list.
40130
40131
40132
40133
40134
40135
40136
40137 save -692- MR12.5 10/27/92^L
40138
40139
40140 bce_save.pl1
40141 save: Getting tape label temp segment.
40142 ERR_MESSAGE
40143
40144
40145 Stream: BOS Typewriter sounds beeper
40146
40147 Time: System Intialization.
40148
40149 Meaning: An error occured while attempting to get a
40150 temporary segment to hold the tape label
40151 information.
40152
40153 Action: Contact the system programming staff.
40154
40155
40156
40157 bce_save_util_.pl1
40158 save: Initiating CONTROL_FILE_NAME for
40159 set-TAPE_SET_IDX ERR_MESSAGE
40160
40161
40162 Stream: BOS Typewriter sounds beeper
40163
40164 Time: System Intialization.
40165
40166 Meaning: An error was detected while initiating the save
40167 control file.
40168
40169 Action: $inform Follow normal recovery procedures.
40170
40171
40172
40173 bce_save.pl1
40174 save: PV_NAME ERR_MESSAGE
40175
40176
40177 Stream: BOS Typewriter sounds beeper
40178
40179 Time: System Intialization.
40180
40181 Meaning: The call to bootload_disk_io$test_done has
40182 returned a non-zero error code.
40183
40184 Action: $inform Follow normal recovery procedures.
40185
40186
40187
40188
40189
40190
40191
40192
40193
40194
40195 save -693- MR12.5 10/27/92^L
40196
40197
40198 bce_save.pl1
40199 save: pvt. ERR_MESSAGE
40200
40201
40202 Stream: BOS Typewriter sounds beeper
40203
40204 Time: System Intialization.
40205
40206 Meaning: The program was unable to get a pointer to the
40207 above segment. This indicates a logic error in
40208 the supervisor or CPU or memory hardware
40209 problems.
40210
40211 Action: Contact the system programming staff.
40212
40213
40214
40215 bce_save.pl1
40216 save: Restarting save of set "TAPE_SET" on
40217 TAPE_DEV.
40218
40219
40220 Stream: BOS Typewriter.
40221
40222 Time: System Intialization.
40223
40224 Meaning: Just an informative message.
40225
40226 Action: No operator action is required.
40227
40228
40229
40230 bce_save_util_.pl1
40231 save: Setting max workspace for TAPE_DEV.
40232 ERR_MESSAGE
40233
40234
40235 Stream: BOS Typewriter sounds beeper
40236
40237 Time: System Intialization.
40238
40239 Meaning: IOI has returned a non-zero error code in response
40240 to a request to set the max workspace size for
40241 TAPE_DEV.
40242
40243 Action: Contact the system programming staff.
40244
40245
40246
40247
40248
40249
40250
40251
40252
40253 save -694- MR12.5 10/27/92^L
40254
40255
40256 bce_save.pl1
40257 save: Setting status index for TAPE_DEV.
40258 ERR_MESSAGE
40259
40260
40261 Stream: BOS Typewriter sounds beeper
40262
40263 Time: System Intialization.
40264
40265 Meaning: IOI has returned a non-zero error which has been
40266 expanded in ERR_MESSAGE.
40267
40268 Action: Contact the system programming staff.
40269
40270
40271
40272 bce_save_util_.pl1
40273 save: Setting up workspace for TAPE_DEV.
40274 ERR_MESSAGE
40275
40276
40277 Stream: BOS Typewriter sounds beeper
40278
40279 Time: System Intialization.
40280
40281 Meaning: IOI has returned a non-zero error code from the
40282 request to create a workspace for TAPE_DEV.
40283
40284 Action: Contact the system programming staff.
40285
40286
40287
40288 bce_save_util_.pl1
40289 save: si ERR_MESSAGE
40290
40291
40292 Stream: BOS Typewriter sounds beeper
40293
40294 Time: System Intialization.
40295
40296 Meaning: An error has been found with the internal "si"
40297 structure. This indicates a logic error in the
40298 supervisor or CPU or memory hardware problems.
40299
40300 Action: Contact the system programming staff.
40301
40302
40303
40304
40305
40306
40307
40308
40309
40310
40311 save -695- MR12.5 10/27/92^L
40312
40313
40314 bce_save_util_.pl1
40315 save: sri ERR_MESSAGE
40316
40317
40318 Stream: BOS Typewriter sounds beeper
40319
40320 Time: System Intialization.
40321
40322 Meaning: An error has been found with the internal "sri"
40323 structure. This indicates a logic error in the
40324 supervisor or CPU or memory hardware problems.
40325
40326 Action: Contact the system programming staff.
40327
40328
40329
40330 bce_save.pl1
40331 save: Stopping save of set "TAPE_SET".
40332
40333
40334 Stream: BOS Typewriter.
40335
40336 Time: System Intialization.
40337
40338 Meaning: Just an informative message.
40339
40340 Action: No operator action is required.
40341
40342
40343
40344 bce_save_util_.pl1
40345 save: TAPE_DEV ERR_MESSAGE
40346
40347
40348 Stream: BOS Typewriter sounds beeper
40349
40350 Time: System Intialization.
40351
40352 Meaning: An error occured while scanning the tape subsystem
40353 survey data.
40354
40355 Action: Follow normal recovery procedures.
40356
40357
40358
40359
40360
40361
40362
40363
40364
40365
40366
40367
40368
40369 save -696- MR12.5 10/27/92^L
40370
40371
40372 bce_save.pl1
40373 save: tape_error_data. ERR_MESSAGE
40374
40375
40376 Stream: BOS Typewriter sounds beeper
40377
40378 Time: System Intialization.
40379
40380 Meaning: The program was unable to get a pointer to the
40381 above segment. This indicates a logic error in
40382 the supervisor or CPU or memory hardware
40383 problems.
40384
40385 Action: Contact the system programming staff.
40386
40387
40388
40389 bce_save.pl1
40390 save: Unassigning TAPE_DEV. ERR_MESSAGE
40391
40392
40393 Stream: BOS Typewriter sounds beeper
40394
40395 Time: System Intialization.
40396
40397 Meaning: IOI has returned a non-zero error which has been
40398 expanded in ERR_MESSAGE.
40399
40400 Action: Contact the system programming staff.
40401
40402
40403
40404 sc_admin_command_.pl1
40405 sc_admin_command_: Denied send_admin_command for
40406 USER in ring RING.
40407
40408
40409 Stream: $sc
40410
40411 Time: While system is running.
40412
40413 Meaning: User USER requested the system to execute an admin
40414 command but lacked access to
40415 >sc1>admin_acs>admin_command.acs.
40416
40417 Action: No operator action is required.
40418
40419
40420
40421
40422
40423
40424
40425
40426
40427 sc_admin_command_ -697- MR12.5 10/27/92^L
40428
40429
40430 bound_system_control_.s.archiv.1
40431 sc_admin_command_: Denied send_admin_command for
40432 USER in ring RING.
40433
40434
40435 Stream: $sc
40436
40437 Time: While system is running.
40438
40439 Meaning: User USER requested the system to execute an admin
40440 command but lacked access to
40441 >sc1>admin_acs>admin_command.acs.
40442
40443 Action: No operator action is required.
40444
40445
40446
40447 sc_admin_command_.pl1
40448 sc_admin_command_: Failed to check access for
40449 USER.
40450
40451
40452 Stream: $sc
40453
40454 Time: While system is running.
40455
40456 Meaning: User USER requested the system to execute an admin
40457 command but the system cound not determine their
40458 access to the admin_command acs.
40459
40460 Action: No operator action is required.
40461
40462
40463
40464 bound_system_control_.s.archiv.1
40465 sc_admin_command_: Failed to check access for
40466 USER.
40467
40468
40469 Stream: $sc
40470
40471 Time: While system is running.
40472
40473 Meaning: User USER requested the system to execute an admin
40474 command but the system cound not determine their
40475 access to the admin_command acs.
40476
40477 Action: No operator action is required.
40478
40479
40480
40481
40482
40483
40484
40485 sc_admin_command_ -698- MR12.5 10/27/92^L
40486
40487
40488 sc_admin_command_.pl1
40489 sc_admin_command_: PERSON: COMMANDLINE
40490
40491
40492 Stream: $sc
40493
40494 Time: While system is running.
40495
40496 Meaning: A system administrator has sent a special command
40497 to the Initializer which executes it in admin
40498 mode.
40499
40500 Action: No operator action is required.
40501
40502
40503
40504 bound_system_control_.s.archiv.1
40505 sc_admin_command_: PERSON: COMMANDLINE
40506
40507
40508 Stream: $sc
40509
40510 Time: While system is running.
40511
40512 Meaning: A system administrator has sent a special command
40513 to the Initializer which executes it in admin
40514 mode.
40515
40516 Action: No operator action is required.
40517
40518
40519
40520 sc_init_.pl1
40521 sc_init_: ERROR_MESSAGE. Error from iox_$attach
40522 master_i/o ATD
40523
40524
40525 Stream: BOS Typewriter Crashes system
40526
40527 Time: System Intialization.
40528
40529 Meaning: Some error was detected while attaching the
40530 master_i/o switch. ATD is the text of the attach
40531 description. This error is usually caused by a
40532 hardware failure in the operator's console.
40533 Correct the failure and reboot the system.
40534
40535 Action: Contact the system programming staff.
40536
40537
40538
40539
40540
40541
40542
40543 sc_init_ -699- MR12.5 10/27/92^L
40544
40545
40546 sc_init_.pl1
40547 sc_init_: ERROR_MESSAGE. Error from iox_$attach
40548 user_i/o syn_ master_i/o
40549
40550
40551 Stream: BOS Typewriter Crashes system
40552
40553 Time: System Intialization.
40554
40555 Meaning: Some error was detected while attaching user_i/o
40556 as a synonym for the master_i/o switch in the
40557 Initializer process. This is usually caused by a
40558 hardware failure in the operator's console.
40559 Correct the failure and reboot the system.
40560
40561 Action: Contact the system programming staff.
40562
40563
40564
40565 sc_init_.pl1
40566 sc_init_: ERROR_MESSAGE. Error from iox_$open
40567 master_i/o stream_input_output
40568
40569
40570 Stream: BOS Typewriter Crashes system
40571
40572 Time: System Intialization.
40573
40574 Meaning: Some error was detected while opening the
40575 master_i/o switch. This is usually caused by a
40576 hardware failure in the operator's console.
40577 Correct the failure and reboot the system.
40578
40579 Action: Contact the system programming staff.
40580
40581
40582
40583
40584
40585
40586
40587
40588
40589
40590
40591
40592
40593
40594
40595
40596
40597
40598
40599
40600
40601 sc_init_ -700- MR12.5 10/27/92^L
40602
40603
40604 sc_init_.pl1
40605 sc_init_: ERROR_MESSAGE. Failed to open
40606 admin_log log.
40607
40608
40609 Stream: BOS Typewriter sounds beeper
40610
40611 Time: System Intialization.
40612
40613 Meaning: The system failed to iox open the switch for the
40614 log >sc1>as_logs>admin_log. The segment
40615 >sc1>as_logs>admin_log may be damaged. The system
40616 enters a primitive Multics listener on the
40617 bootload console.
40618
40619 Action: Repair the problem. You may need to rename or
40620 delete the segment >sc1>as_logs>admin_log. Then
40621 shutdown and reboot.
40622
40623
40624
40625 sc_init_.pl1
40626 sc_init_: Invoking emergency listener because
40627 "nosc" parameter specified.
40628
40629
40630 Stream: BOS Typewriter.
40631
40632 Time: System Intialization.
40633
40634 Meaning: The parm config card specified nosc no system
40635 control. This parameter requests that an
40636 emergency listener be entered to allow repair of
40637 >sc1 or other parts of the system hierarchy at the
40638 earliest possible point during system
40639 initialization. Once the repairs are made
40640 shutdown the system by typing: "hphcs_$shutdown"
40641 and then reboot the system.
40642
40643 Action: Repair the problem shutdown the system then
40644 reboot.
40645
40646
40647
40648
40649
40650
40651
40652
40653
40654
40655
40656
40657
40658
40659 sc_init_ -701- MR12.5 10/27/92^L
40660
40661
40662 sc_init_.pl1
40663 sc_init_: Messages from log salvage of
40664 LOG_PATHNAME:
40665
40666
40667 Stream: BOS Typewriter.
40668
40669 Time: System Intialization.
40670
40671 Meaning: Some error was detected in opening the admin or
40672 answering service log specified by LOG_PATHNAME.
40673 A salvage was invoked to attempt correction of the
40674 problem. One or more messages will succeed this
40675 message which describe inconsistancies found in
40676 the log repairs which were made or conditions
40677 which prevent automatic repair. These will be of
40678 the form "sc_init_: log_salvage_ MESSAGE".
40679
40680 Action: Contact the system programming staff.
40681
40682
40683
40684 sc_init_.pl1
40685 sc_init_: Cound not initiate the PIT for the
40686 Initializer.
40687
40688
40689 Stream: BOS Typewriter Crashes system
40690
40691 Time: System Intialization.
40692
40693 Meaning: The Initializer has failed to initiate the segment
40694 "pit" in its process directory. This could
40695 indicate problems with the bootload tape the
40696 online libraries or the hardware.
40697
40698 Action: Contact the system programming staff.
40699
40700
40701
40702
40703
40704
40705
40706
40707
40708
40709
40710
40711
40712
40713
40714
40715
40716
40717 sc_init_ -702- MR12.5 10/27/92^L
40718
40719
40720 sc_init_.pl1
40721 sc_init_: Created >system_control_dir>as_logs
40722
40723
40724 Stream: BOS Typewriter sounds beeper
40725
40726 Time: System Intialization.
40727
40728 Meaning: The system has successfully created a new
40729 directory >sc1>as_logs.
40730
40731 Action: No operator action is required. If this is not
40732 the first bootload of the system under MR11 or
40733 later you may need to retrieve log segments lost
40734 in a crash into the new directory.
40735
40736
40737
40738 sc_init_.pl1
40739 sc_init_: ERROR_MESSAGE.
40740 >system_control_dir>as_logs does not exist or is
40741 not a directory.
40742
40743
40744 Stream: BOS Typewriter sounds beeper
40745
40746 Time: System Intialization.
40747
40748 Meaning: The directory >sc1>as_logs must exist for the ring
40749 4 environment to be set up.
40750
40751 Action: The system continues operation trying to repair
40752 the situation. Subsequent messages indicate the
40753 success or failure of repairs.
40754
40755
40756
40757 sc_init_.pl1
40758 sc_init_: ERROR_MESSAGE. Could not set working
40759 directory to PATH.
40760
40761
40762 Stream: BOS Typewriter sounds beeper
40763
40764 Time: System Intialization.
40765
40766 Meaning: Either some program is in error or the directory
40767 PATH does not exist.
40768
40769 Action: Contact the system programming staff. Correct the
40770 problem shut down and reboot.
40771
40772
40773
40774
40775 sc_init_ -703- MR12.5 10/27/92^L
40776
40777
40778 sc_init_.pl1
40779 sc_init_: ERROR_MESSAGE. Error from
40780 initiate_search_rules.
40781
40782
40783 Stream: BOS Typewriter sounds beeper
40784
40785 Time: System Intialization.
40786
40787 Meaning: The Initializer is attempting to set its search
40788 rules and has encountered an error. This message
40789 may occur if an error has been introduced into the
40790 system tape or it may indicate that one of the
40791 directories searched by the Initializer has been
40792 destroyed.
40793
40794 Action: Contact the system programming staff.
40795
40796
40797
40798 sc_init_.pl1
40799 sc_init_: ERROR_MESSAGE. Failed to attach
40800 admin_log log.
40801
40802
40803 Stream: BOS Typewriter sounds beeper
40804
40805 Time: System Intialization.
40806
40807 Meaning: The system failed to attach a switch to write
40808 information to the admin log
40809 >sc1>as_logs>admin_log. The segment
40810 >sc1>as_logs>admin_log may be damaged. The system
40811 enters a primitive Multics listener on the
40812 bootload console.
40813
40814 Action: Repair the problem. You may have to delete or
40815 rename the segment >sc1>as_logs>admin_log. Then
40816 shutdown and reboot.
40817
40818
40819
40820
40821
40822
40823
40824
40825
40826
40827
40828
40829
40830
40831
40832
40833 sc_init_ -704- MR12.5 10/27/92^L
40834
40835
40836 sc_init_.pl1
40837 sc_init_: ERROR_MESSAGE. Failed to get
40838 log_write_ ptr for admin_log.
40839
40840
40841 Stream: BOS Typewriter sounds beeper
40842
40843 Time: System Intialization.
40844
40845 Meaning: This indicated an internal programming error. The
40846 online libraries may be damaged.
40847
40848 Action: Contact the system programming staff.
40849
40850
40851
40852 sc_init_.pl1
40853 sc_init_: ERROR_MESSAGE. Failed to open the AS
40854 log >system_control_dir>as_logs>log.
40855
40856
40857 Stream: BOS Typewriter sounds beeper
40858
40859 Time: System Intialization.
40860
40861 Meaning: The system was unable to open the log
40862 >sc1>as_logs>log. This may indicate damage to the
40863 segment >sc1>as_logs>log. The system enters a
40864 primitive Multics listener on the bootload
40865 console.
40866
40867 Action: Repair the problem. You may have to rename or
40868 delete >sc1>as_logs>log. Then shutdown and
40869 reboot.
40870
40871
40872
40873
40874
40875
40876
40877
40878
40879
40880
40881
40882
40883
40884
40885
40886
40887
40888
40889
40890
40891 sc_init_ -705- MR12.5 10/27/92^L
40892
40893
40894 sc_init_.pl1
40895 sc_init_: Failed to attach one of the severityN
40896 1 2 3 switches.
40897
40898
40899 Stream: BOS Typewriter.
40900
40901 Time: System Intialization.
40902
40903 Meaning: The Initializer failed to make a syn_ for one of
40904 the three switches severity1 severity2 or
40905 severity3. There may be a problem with the system
40906 tape the libraries or the hardware.
40907
40908 Action: The system attempts to enter a primitive listener
40909 environment on the bootload console. You should
40910 diagnose and/or correct the problem and then
40911 reboot the system.
40912
40913
40914 Message: sc_init_: A serious error was
40915 encountered setting up the system control
40916 environment. The system will attempt to establish
40917 a Multics listener level. You should repair the
40918 problem and then type:
40919 "hphcs_$shutdown" and reboot the system.
40920
40921 Stream: BOS Typewriter.
40922
40923 Time: System Intialization.
40924
40925 Action: Contact the system programming staff.
40926
40927
40928
40929 sc_init_.pl1
40930 sc_init_: Failed to create ssu invocation for
40931 system control.
40932
40933
40934 Stream: BOS Typewriter sounds beeper
40935
40936 Time: System Intialization.
40937
40938 Meaning: The system failed to set up the subsystem data
40939 structure for the bootload console. This
40940 indicates a programming error or trouble with the
40941 system libraries.
40942
40943 Action: Contact the system programming staff.
40944
40945
40946
40947
40948
40949 sc_init_ -706- MR12.5 10/27/92^L
40950
40951
40952 sc_init_.pl1
40953 sc_init_: Renamed non-directory object
40954 >system_control_dir>as_logs.
40955
40956
40957 Stream: BOS Typewriter sounds beeper
40958
40959 Time: System Intialization.
40960
40961 Meaning: The system found something that was not a
40962 directory in the place of the directory
40963 >sc1>as_logs and renamed it to permit a new
40964 directory to be created.
40965
40966 Action: No operator action is required.
40967
40968
40969
40970 sc_process_command_line_.pl1
40971 sc_process_command_line_: Error while reattaching
40972 critical I/O switches.
40973
40974
40975 Stream: $sc
40976
40977 Time: In response to an operator command.
40978
40979 Meaning: $crashes This indicates a logic error in the
40980 supervisor or CPU or memory hardware problems.
40981
40982 Action: Contact the system programming staff.
40983
40984
40985
40986 sc_process_command_line_.pl1
40987 sc_process_command_line_: ERROR_MESSAGE. Could
40988 not attach switch NAME @ LOC using attach
40989 description DESCRIP.
40990
40991
40992 Stream: $sc
40993
40994 Time: In response to an operator command.
40995
40996 Meaning: $crashes $err ERROR_MESSAGE is the expansion of
40997 the system status code describing the attach
40998 error. LOC gives the location of the I/O Control
40999 Block IOCB.
41000
41001 Action: Contact the system programming staff.
41002
41003
41004
41005
41006
41007 sc_process_command_line_ -707- MR12.5 10/27/92^L
41008
41009
41010 sc_process_command_line_.pl1
41011 sc_process_command_line_: ERROR_MESSAGE. Could
41012 not open switch NAME for stream_input_output.
41013
41014
41015 Stream: $sc
41016
41017 Time: In response to an operator command.
41018
41019 Meaning: $crashes $err ERROR_MESSAGE is the expansion of
41020 the system status code describing the open error.
41021
41022 Action: Contact the system programming staff.
41023
41024
41025
41026 sc_process_command_line_.pl1
41027 sc_process_command_line_: ERROR_MESSAGE. Could
41028 not restore attachment to switch NAME.
41029
41030
41031 Stream: $sc
41032
41033 Time: In response to an operator command.
41034
41035 Meaning: $crashes $err ERROR_MESSAGE is the expansion of
41036 the system status code describing the move_attach
41037 error.
41038
41039 Action: Contact the system programming staff.
41040
41041
41042
41043 sc_process_command_line_.pl1
41044 sc_process_command_line_: ERROR_MESSAGE. Failed
41045 to find save iocb NAME.
41046
41047
41048 Stream: $sc
41049
41050 Time: In response to an operator command.
41051
41052 Meaning: $crashes $err ERROR_MESSAGE is the expansion of
41053 the system status code describing the actual
41054 error.
41055
41056 Action: Contact the system programming staff.
41057
41058
41059
41060
41061
41062
41063
41064
41065 sc_process_command_line_ -708- MR12.5 10/27/92^L
41066
41067
41068 sc_process_command_line_.pl1
41069 sc_process_command_line_: ERROR_MESSAGE. Failed
41070 to move_attach iocb NAME.
41071
41072
41073 Stream: $sc
41074
41075 Time: In response to an operator command.
41076
41077 Meaning: $crashes $err ERROR_MESSAGE is the expansion of
41078 the system status code describing the actual
41079 error.
41080
41081 Action: Contact the system programming staff.
41082
41083
41084
41085 sc_process_command_line_.pl1
41086 sc_process_command_line_: Terminal SOURCE_NAME
41087 hung up during execution of command.
41088
41089
41090 Stream: as severity 2
41091
41092 Time: In response to an operator command.
41093
41094 Meaning: Reports that execution of an Initializer command
41095 was interrupted when the message coordinator
41096 terminal identified by SOURCE_NAME hung.
41097
41098 Action: No operator action is required.
41099
41100
41101
41102 sc_requests_.pl1
41103 sc_requests_ set_time_zone: Changed time zone
41104 from OLD_ZONE to NEW_ZONE.
41105
41106
41107 Stream: $sc
41108
41109 Time: While system is running.
41110
41111 Meaning: This messages records that the set_time_zone
41112 operator request was
41113 given and that the system default time
41114 zone was thereby changed
41115 from OLD_ZONE to NEW_ZONE.
41116
41117 Action: No operator action is required.
41118
41119
41120
41121
41122
41123 sc_requests_ set_time_zon -709- MR12.5 10/27/92^L
41124
41125
41126 sc_signal_handler_.pl1
41127 sc_signal_handler_: error: CONDITION_NAME
41128
41129
41130 Stream: as severity2
41131
41132 Time: While system is running.
41133
41134 Meaning: A CONDITION_NAME condition occurred while running
41135 an operator
41136 command. An answering service dump has
41137 been taken to further
41138 describe the cause of the condition.
41139
41140 Action: Contact the system administrator.
41141
41142
41143
41144 scas_init.pl1
41145 scas_init: Bootload CPU has no system controller
41146 mask assigned.
41147
41148
41149 Stream: BOS Typewriter Crashes system
41150
41151 Time: System Intialization.
41152
41153 Meaning: No memory assigns a mask register to the bootload
41154 CPU.
41155
41156 Action: Correct the configuration and reboot.
41157
41158
41159
41160 scas_init.pl1
41161 scas_init: Bootload CPU may not be on an expander
41162 port.
41163
41164
41165 Stream: BOS Typewriter Crashes system
41166
41167 Time: System Intialization.
41168
41169 Meaning: The CPU config card for the bootload CPU indicates
41170 that the bootload CPU is on an expanded port.
41171 This is not permitted.
41172
41173 Action: Correct the configuration or the configuration
41174 deck and reboot.
41175
41176
41177
41178
41179
41180
41181 scas_init -710- MR12.5 10/27/92^L
41182
41183
41184 scas_init.pl1
41185 scas_init: Config card for bootload CPU indicates
41186 unit is offline.
41187
41188
41189 Stream: BOS Typewriter Crashes system
41190
41191 Time: System Intialization.
41192
41193 Meaning: The configuration deck is incorrect.
41194
41195 Action: Correct the configuration or the configuration
41196 deck and reboot.
41197
41198
41199
41200 scas_init.pl1
41201 scas_init: Config card for bootload MEM indicates
41202 unit is offline.
41203
41204
41205 Stream: BOS Typewriter Crashes system
41206
41207 Time: System Intialization.
41208
41209 Meaning: The configuration deck is incorrect.
41210
41211 Action: Correct the the configuration deck and reboot.
41212
41213
41214
41215 scas_init.pl1
41216 scas_init: Config card for CPU X is neither on
41217 nor off.
41218
41219
41220 Stream: BOS Typewriter Crashes system
41221
41222 Time: System Intialization.
41223
41224 Meaning: The configuration deck is incorrect.
41225
41226 Action: Correct the the configuration deck and reboot.
41227
41228
41229
41230
41231
41232
41233
41234
41235
41236
41237
41238
41239 scas_init -711- MR12.5 10/27/92^L
41240
41241
41242 scas_init.pl1
41243 scas_init: Config card for MEM Y is neither on
41244 nor off.
41245
41246
41247 Stream: BOS Typewriter Crashes system
41248
41249 Time: System Intialization.
41250
41251 Meaning: The configuration deck is incorrect.
41252
41253 Action: Correct the the configuration deck and reboot.
41254
41255
41256
41257 scas_init.pl1
41258 scas_init: CPU config card specifies wrong
41259 controller port number.
41260
41261
41262 Stream: BOS Typewriter Crashes system
41263
41264 Time: System Intialization.
41265
41266 Meaning: The configuration deck is incorrect.
41267
41268 Action: Correct the configuration or the configuration
41269 deck and reboot.
41270
41271
41272
41273 scas_init.pl1
41274 scas_init: CPU data switches are XXXXXXXXXXXX
41275 should be YYYYYYYYYYYY
41276
41277
41278 Stream: BOS Typewriter.
41279
41280 Time: System Intialization.
41281
41282 Meaning: The CPU data switches are not set properly. The
41283 proper values are displayed.
41284
41285 Action: The incorrect value will prevent returning to bce
41286 on that CPU by means of EXECUTE SWITCHES. Certain
41287 incorrect values will activate software debugging
41288 traps. The switches should be corrected. This
41289 can be done while the CPU is running.
41290
41291
41292
41293
41294
41295
41296
41297 scas_init -712- MR12.5 10/27/92^L
41298
41299
41300 scas_init.pl1
41301 scas_init: CPU X and CPU Y both configured for
41302 port P subport S
41303
41304
41305 Stream: BOS Typewriter Crashes system
41306
41307 Time: System Intialization.
41308
41309 Meaning: The CPU CONFIG cards for CPU's X and Y both
41310 indicate that they are connected to subport S of
41311 expanded SCU port P. This is clearly impossible.
41312
41313 Action: Correct the configuration deck and reboot.
41314
41315
41316
41317 scas_init.pl1
41318 scas_init: CPU X appears twice in config deck.
41319
41320
41321 Stream: BOS Typewriter Crashes system
41322
41323 Time: System Intialization.
41324
41325 Meaning: The configuration deck is incorrect.
41326
41327 Action: Correct the the configuration deck and reboot.
41328
41329
41330
41331 scas_init.pl1
41332 scas_init: Illegal expander subport tag on CPU X
41333 config card.
41334
41335
41336 Stream: BOS Typewriter Crashes system
41337
41338 Time: System Intialization.
41339
41340 Meaning: A CPU config card for CPU X specifies an illegal
41341 value for a port-expander subport. The only legal
41342 values for expander subports are A B C and D.
41343
41344 Action: Correct the config deck and reboot.
41345
41346
41347
41348
41349
41350
41351
41352
41353
41354
41355 scas_init -713- MR12.5 10/27/92^L
41356
41357
41358 scas_init.pl1
41359 scas_init: Illegal tag on CPU config card.
41360
41361
41362 Stream: BOS Typewriter Crashes system
41363
41364 Time: System Intialization.
41365
41366 Meaning: One or more CPU cards is incorrect. Tag must be
41367 one of A B C D E F G H.
41368
41369 Action: Correct the configuration or the configuration
41370 deck and reboot.
41371
41372
41373
41374 scas_init.pl1
41375 scas_init: Illegal tag on MEM config card.
41376
41377
41378 Stream: BOS Typewriter Crashes system
41379
41380 Time: System Intialization.
41381
41382 Meaning: The configuration deck is incorrect. Tag must be
41383 one of A B C D E F G H.
41384
41385 Action: Correct the the configuration deck and reboot.
41386
41387
41388
41389 scas_init.pl1
41390 scas_init: MEM X is an old SCU with port expander
41391
41392
41393 Stream: BOS Typewriter Crashes system
41394
41395 Time: System Intialization.
41396
41397 Meaning: System controller X is an old-style SCU but
41398 configuration cards indicate that it has at least
41399 one expanded port because there is a CPU on an
41400 expanded port in the system. Old-style system
41401 controllers may not have expanded ports.
41402
41403 Action: The configuration deck is in error. Fix it and
41404 reboot.
41405
41406
41407
41408
41409
41410
41411
41412
41413 scas_init -714- MR12.5 10/27/92^L
41414
41415
41416 scas_init.pl1
41417 scas_init: MEM X is not enabled.
41418
41419
41420 Stream: BOS Typewriter Crashes system
41421
41422 Time: System Intialization.
41423
41424 Meaning: The bootload CPU does not have MEM X enabled.
41425
41426 Action: Correct the configuration or the configuration
41427 deck and reboot.
41428
41429
41430
41431 scas_init.pl1
41432 scas_init: MEM Y address assignment disagrees
41433 with config deck.
41434
41435
41436 Stream: BOS Typewriter Crashes system
41437
41438 Time: System Intialization.
41439
41440 Meaning: The address assignment of memory Y as read from
41441 the address assignment switches on the maintenance
41442 panel of the bootload CPU disagrees with the
41443 address assignment of this memory as indicated by
41444 the relative position of its MEM card in the
41445 configuration deck.
41446
41447 Action: If the configuration deck is wrong correct it and
41448 reboot. If the configuration deck is correct
41449 check all address assignment switches on
41450 processors IOMs and the Bulk Store Controller
41451 correct them reboot bce and reboot.
41452
41453
41454
41455 scas_init.pl1
41456 scas_init: MEM Y appears twice in config deck.
41457
41458
41459 Stream: BOS Typewriter Crashes system
41460
41461 Time: System Intialization.
41462
41463 Meaning: The configuration deck is incorrect.
41464
41465 Action: Correct the the configuration deck and reboot.
41466
41467
41468
41469
41470
41471 scas_init -715- MR12.5 10/27/92^L
41472
41473
41474 scas_init.pl1
41475 scas_init: MEM Y has duplicate mask assignments
41476 to CPU X.
41477
41478
41479 Stream: BOS Typewriter Crashes system
41480
41481 Time: System Intialization.
41482
41483 Meaning: The EXECUTE INTERRUPT MASK ASSIGNMENT or MASK/PORT
41484 ASSIGNMENT on memory Y is incorrect.
41485
41486 Action: Correct the configuration and reboot.
41487
41488
41489
41490 scas_init.pl1
41491 scas_init: MEM Y has mask Z assigned to
41492 non-processor port.
41493
41494
41495 Stream: BOS Typewriter Crashes system
41496
41497 Time: System Intialization.
41498
41499 Meaning: The EXECUTE INTERRUPT MASK ASSIGNMENT or MASK/PORT
41500 ASSIGNMENT on memory Y is incorrect.
41501
41502 Action: Correct the configuration and reboot.
41503
41504
41505
41506 scas_init.pl1
41507 scas_init: MEM Y has more memory than indicated
41508 by CPU switches.
41509
41510
41511 Stream: BOS Typewriter Crashes system
41512
41513 Time: System Intialization.
41514
41515 Meaning: The PORT SIZE plug on the free edge of the PQ
41516 board of the bootload CPU does not agree with the
41517 STORE SIZE switch on MEM Y.
41518
41519 Action: Correct the configuration and reboot.
41520
41521
41522
41523
41524
41525
41526
41527
41528
41529 scas_init -716- MR12.5 10/27/92^L
41530
41531
41532 scas_init.pl1
41533 scas_init: MEM Y has no mask assigned to CPU X.
41534
41535
41536 Stream: BOS Typewriter Crashes system
41537
41538 Time: System Intialization.
41539
41540 Meaning: The EXECUTE INTERRUPT MASK ASSIGNMENT or MASK/PORT
41541 ASSIGNMENT on memory Y is incorrect.
41542
41543 Action: Correct the configuration and reboot.
41544
41545
41546
41547 scas_init.pl1
41548 scas_init: MEM Y is not in PROGRAM mode.
41549
41550
41551 Stream: BOS Typewriter Crashes system
41552
41553 Time: System Intialization.
41554
41555 Meaning: The MODE switch for memory Y is incorrect.
41556
41557 Action: Correct the configuration and reboot.
41558
41559
41560
41561 scas_init.pl1
41562 scas_init: MEM Y is not in the configuration but
41563 is enabled by the CPU switches.
41564
41565
41566 Stream: BOS Typewriter Crashes system
41567
41568 Time: System Intialization.
41569
41570 Meaning: The bootload CPU enables memory Y. But there is
41571 no MEM card for this memory.
41572
41573 Action: Correct the configuration or the configuration
41574 deck and reboot.
41575
41576
41577
41578
41579
41580
41581
41582
41583
41584
41585
41586
41587 scas_init -717- MR12.5 10/27/92^L
41588
41589
41590 scas_init.pl1
41591 scas_init: More than one low-order MEM.
41592
41593
41594 Stream: BOS Typewriter Crashes system
41595
41596 Time: System Intialization.
41597
41598 Meaning: The configuration deck is incorrect.
41599
41600 Action: Correct the the configuration deck and reboot.
41601
41602
41603
41604 scas_init.pl1
41605 scas_init: No config card for bootload CPU.
41606
41607
41608 Stream: BOS Typewriter Crashes system
41609
41610 Time: System Intialization.
41611
41612 Meaning: The configuration deck is incorrect.
41613
41614 Action: Correct the configuration or the configuration
41615 deck and reboot.
41616
41617
41618
41619 scas_init.pl1
41620 scas_init: No config card for bootload MEM
41621
41622
41623 Stream: BOS Typewriter Crashes system
41624
41625 Time: System Intialization.
41626
41627 Meaning: The configuration deck is incorrect.
41628
41629 Action: Correct the the configuration deck and reboot.
41630
41631
41632
41633
41634
41635
41636
41637
41638
41639
41640
41641
41642
41643
41644
41645 scas_init -718- MR12.5 10/27/92^L
41646
41647
41648 scas_init.pl1
41649 scas_init: No CPU config card.
41650
41651
41652 Stream: BOS Typewriter Crashes system
41653
41654 Time: System Intialization.
41655
41656 Meaning: The configuration deck is incorrect.
41657
41658 Action: Correct the the configuration deck and reboot.
41659
41660
41661
41662 scas_init.pl1
41663 scas_init: No MEM config card.
41664
41665
41666 Stream: BOS Typewriter Crashes system
41667
41668 Time: System Intialization.
41669
41670 Meaning: The configuration deck is incorrect.
41671
41672 Action: Correct the the configuration deck and reboot.
41673
41674
41675
41676 scas_init.pl1
41677 scas_init: Possible memory address overlap in MEM
41678 Y.
41679
41680
41681 Stream: BOS Typewriter Crashes system
41682
41683 Time: System Intialization.
41684
41685 Meaning: This indicates that the lower store size does not
41686 agree with the actual memory available in the
41687 store unit. A possible example of this is when
41688 the lower store is actually in two store units A
41689 and A1 and the secondary unit A1 is not
41690 enabled.
41691
41692 Action: Correct the configuration and reboot.
41693
41694
41695
41696
41697
41698
41699
41700
41701
41702
41703 scas_init -719- MR12.5 10/27/92^L
41704
41705
41706 scas_init.pl1
41707 scas_init: SCU port P configured as both expanded
41708 and non-expanded.
41709
41710
41711 Stream: BOS Typewriter Crashes system
41712
41713 Time: System Intialization.
41714
41715 Meaning: CPU configuration cards imply that Port P on SCU's
41716 P is the port number from 0 to 7 is both an
41717 expander port by being named as the CPU port in a
41718 CPU card with an expander_port field and not an
41719 expander port by being named in one that has
41720 none.
41721
41722 Action: Correct the configuratin deck and reboot.
41723
41724
41725
41726 scas_init.pl1
41727 scas_init: Size too large on config card for MEM
41728 Y.
41729
41730
41731 Stream: BOS Typewriter Crashes system
41732
41733 Time: System Intialization.
41734
41735 Meaning: Either the PORT SIZE plug on the free edge of the
41736 PQ board of the bootload CPU does not agree with
41737 the configuration deck or the actual amount of
41738 memory present in MEM Y does not agree with the
41739 config deck.
41740
41741
41742 Action: Correct the configuration or the configuration
41743 deck and reboot.
41744
41745
41746
41747
41748
41749
41750
41751
41752
41753
41754
41755
41756
41757
41758
41759
41760
41761 scas_init -720- MR12.5 10/27/92^L
41762
41763
41764 scavenge_volume.pl1
41765 scavenge_volume: damaged switch found on for NAME
41766 at VTOCX dskX_NNS
41767
41768
41769 Stream: Logged in SYSERR log.
41770
41771 Time: During a physical volume scavenge of dskX_NNS
41772
41773 Meaning: The damaged switch in the VTOCEwas set prior to
41774 the scavenge.
41775
41776 Action: Recover the segment.
41777
41778
41779
41780 scavenge_volume.pl1
41781 scavenge_volume: Damaged vtoce VTOCX
41782 dskX_NNS.
41783
41784
41785 Stream: Logged in SYSERR log.
41786
41787 Time: During a physical volume scavenge of dskX_NNS
41788
41789 Meaning: The VTOCE image before correction is recorded into
41790 the syserr log if scavenge_vol was invoked with
41791 the -dump control argument.
41792
41793 Action: No operator action is required.
41794
41795
41796
41797 scavenge_volume.pl1
41798 scavenge_volume: Debug Trap on scavenge of
41799 dskX_NNS
41800
41801
41802 Stream: BOS Typewriter Crashes system
41803
41804 Time: At the completion of a volume scavenge of
41805 dskX_NNS
41806
41807 Meaning: This is a debugging trap which results when
41808 scavenge_vol is used with the -trap control
41809 argument.
41810
41811 Action: Type GO to resume Multics operation.
41812
41813
41814
41815
41816
41817
41818
41819 scavenge_volume -721- MR12.5 10/27/92^L
41820
41821
41822 scavenge_volume.pl1
41823 scavenge_volume: dirsw turned off for NAME at
41824 VTOCX dskX_NNS
41825
41826
41827 Stream: Logged in SYSERR log.
41828
41829 Time: During a physical volume scavenge of dskX_NNS
41830
41831 Meaning: The directory switch in the VTOCE was found on for
41832 a non-directory segment. It has been turned off.
41833 The segment has been damaged.
41834
41835 Action: Recover the segment.
41836
41837
41838
41839 scavenge_volume.pl1
41840 scavenge_volume: Error freeing TYPE vtocx VTOCX
41841 on dskX_NNS. ERRORMESSAGE
41842
41843
41844 Stream: Logged in SYSERR log.
41845
41846 Time: During a physical volume scavenge of dskX_NNS.
41847
41848 Meaning: The VTOCE indicated could not be freed due to the
41849 error indicated.
41850
41851 Action: No operator action is required.
41852
41853
41854
41855 scavenge_volume.pl1
41856 scavenge_volume: Error reading vtocx NNNN on
41857 dskX_NNS. ERRORMESSAGE
41858
41859
41860 Stream: Logged in SYSERR log.
41861
41862 Time: During a physical volume scavenge of dskX_NNS
41863
41864 Meaning: An error was encountered attempting to read the
41865 VTOCE indicated. The VTOCE is skipped and lost
41866 records are not recovered. The count of volume
41867 inconsistencies is not reset to zero.
41868
41869 Action: After the problems with the volume have been
41870 repaired run the scavenger again to recover lost
41871 records.
41872
41873
41874
41875
41876
41877 scavenge_volume -722- MR12.5 10/27/92^L
41878
41879
41880 scavenge_volume.pl1
41881 scavenge_volume: Error writing vtocx NNNNN on
41882 dskX_NNS. ERRORMESSAGE
41883
41884
41885 Stream: Logged in SYSERR log.
41886
41887 Time: During a physical volume scavenge of dskX_NNS
41888
41889 Meaning: The error indicated was encountered writing a
41890 VTOCE.
41891
41892 Action: No operator action is required.
41893
41894
41895
41896 scavenge_volume.pl1
41897 scavenge_volume: Faulting under the LOCK for
41898 debugging for USER
41899
41900
41901 Stream: BOS Typewriter sounds beeper
41902
41903 Time: During a physical volume salvage.
41904
41905 Meaning: A fault tag three fault is taken to exercise fault
41906 recovery.
41907
41908 Action: No operator action is required.
41909
41910
41911
41912
41913
41914
41915
41916
41917
41918
41919
41920
41921
41922
41923
41924
41925
41926
41927
41928
41929
41930
41931
41932
41933
41934
41935 scavenge_volume -723- MR12.5 10/27/92^L
41936
41937
41938 scavenge_volume.pl1
41939 scavenge_volume: Freed NNN VTOCEs on dskX_NNS
41940
41941
41942 Stream: Logged in SYSERR log.
41943
41944 Time: During a physical volume scavenge of dskX_NNS
41945
41946 Meaning: NNN VTOCEs were added to the free pool. These
41947 VTOCEs are VTOCEs found free but not marked as
41948 free in the VTOC map per-process VTOCEs from a
41949 prior bootload and per-bootload VTOCEs from a
41950 prior bootload.
41951
41952 Message: scavenge_volume: vtoce NAME at VTOCX
41953 dskX_NNS disk addr RRR bad
41954
41955 Stream: Logged in SYSERR log.
41956
41957 Time: During a physical volume scavenge of dskX_NNS
41958
41959 Meaning: Record address RRR in the VTOCE indicated is
41960 outside of the paging region for the volume. The
41961 segment has been damaged.
41962
41963 Action: Recover the segment.
41964
41965
41966
41967 scavenge_volume.pl1
41968 scavenge_volume: Freed NNNN records on dskX_NNS
41969
41970
41971 Stream: Logged in SYSERR log.
41972
41973 Time: During a physical volume scavenge of dskX_NNS
41974
41975 Meaning: NNNN records were not claimed by any VTOCE and
41976 were not listed as free in the volume map. These
41977 records have been freed.
41978
41979 Action: No operator action is required.
41980
41981
41982
41983
41984
41985
41986
41987
41988
41989
41990
41991
41992
41993 scavenge_volume -724- MR12.5 10/27/92^L
41994
41995
41996 scavenge_volume.pl1
41997 scavenge_volume: freeing TYPE VTOCE NAME at VTOCX
41998 dskX_NNS
41999
42000
42001 Stream: Logged in SYSERR log.
42002
42003 Time: During a physical volume scavenge of dskX_NNS
42004
42005 Meaning: The message appears for each VTOCE freed if
42006 scavenge_vol was invoked with the -debug control
42007 argument.
42008
42009 Action: No operator action is required.
42010
42011
42012
42013 scavenge_volume.pl1
42014 scavenge_volume: Invalid File Map Checksum for
42015 NAME at VTOCX dskX_NNS.
42016
42017
42018 Stream: Logged in SYSERR log.
42019
42020 Time: During a physical volume scavenge of dskX_NNS.
42021
42022 Meaning: The filemap checksum was incorrect indicating
42023 damage to the VTOCE. The checksum is corrected.
42024 Other damage if found is reported.
42025
42026 Action: No operator action is required.
42027
42028
42029
42030 scavenge_volume.pl1
42031 scavenge_volume: NNN errors reading VTOCEs on
42032 dskX_NNS
42033
42034
42035 Stream: BOS Typewriter.
42036
42037 Time: During a physical volume scavenge of
42038 dskX_NNS
42039
42040 Meaning: Errors were encountered reading VTOCEs. A message
42041 describing each error was recorded into the syserr
42042 log. The VTOCEs with errors are skipped and lost
42043 records are not recovered.
42044
42045 Action: When the volume has been repaired rerun the
42046 scavenger to recover the lost records.
42047
42048
42049
42050
42051 scavenge_volume -725- MR12.5 10/27/92^L
42052
42053
42054 scavenge_volume.pl1
42055 scavenge_volume: NNN VTOCEs on dskX_NNS
42056 damaged. MMM damaged during this scavenge.
42057
42058
42059 Stream: BOS Typewriter.
42060
42061 Time: At the completion of a volume scavenge of
42062 dskX_NNS
42063
42064 Meaning: The scavenger found a total of NNN damaged
42065 segments on the volume. Of these MMM were
42066 damaged by the scavenger due to inconsistencies in
42067 the VTOCEs for these segments. A message for each
42068 was recorded into the syserr log.
42069
42070 Action: Examine the syserr log to find the damaged
42071 segments and recover them.
42072
42073
42074
42075 scavenge_volume.pl1
42076 scavenge_volume: Out-of-service address in stock
42077 for dskX_NNS
42078
42079
42080 Stream: BOS Typewriter Crashes system
42081
42082 Time: During a scavenge of dskX_NNS
42083
42084 Meaning: While examining the record stock and
42085 out-of-service address was encountered. Due to
42086 the volume map locking protocols used this should
42087 never happen. It indicates hardware or software
42088 malfunction.
42089
42090 Action: Follow normal recovery procedures.
42091
42092 Message: scavenge_volume: Processing vtocx NNNNN
42093 on dskX_NNS
42094
42095 Stream: BOS Typewriter.
42096
42097 Time: During a volume scavenge of dskX_NNS
42098
42099 Meaning: This message is printed every 2000 octal VTOCEs
42100 during the scan of the VTOC by the scavenger if
42101 scavenge_vol was invoked with the -debug option.
42102
42103 Action: No operator action is required.
42104
42105
42106
42107
42108
42109 scavenge_volume -726- MR12.5 10/27/92^L
42110
42111
42112 scavenge_volume.pl1
42113 scavenge_volume: Overflow on scavenge of
42114 dskX_NNS. Restarting.
42115
42116
42117 Stream: BOS Typewriter.
42118
42119 Time: During a physical volume scavenge of dskX_NNS.
42120
42121 Meaning: An internal table which tracks reused record
42122 addresses overflowed. All conflicts detected so
42123 far are resolved and the scavenge is restarted
42124 from the beginning.
42125
42126 Action: No operator action is required.
42127
42128
42129
42130 scavenge_volume.pl1
42131 scavenge_volume: setting damaged switch on NAME
42132 at VTOCX dskX_NNS.
42133
42134
42135 Stream: Logged in SYSERR log.
42136
42137 Time: During a physical volume scavenge of dskX_NNS
42138
42139 Meaning: An inconsistency has been detected in the VTOCE
42140 and the damaged switch has been set. A message
42141 describing the inconsistency has been recorded in
42142 the syserr log. The binary information associated
42143 with this message includes the segment UID-path.
42144
42145 Action: Recover the segment.
42146
42147
42148
42149
42150
42151
42152
42153
42154
42155
42156
42157
42158
42159
42160
42161
42162
42163
42164
42165
42166
42167 scavenge_volume -727- MR12.5 10/27/92^L
42168
42169
42170 scavenge_volume.pl1
42171 scavenge_volume: Unable to resolve conflict for
42172 address RRR on dskX_NNS. astep=PTR
42173
42174
42175 Stream: Logged in SYSERR log.
42176
42177 Time: During a physical volume scavenge of dskX_NNS
42178
42179 Meaning: During the scan of the VTOC the scavenger found
42180 several VTOCEs which claimed the same record
42181 address RRR. It could not resolve the conflict
42182 since the segment with the ASTE indicated was
42183 active and could not be deactivated.
42184
42185 Action: Rerun the scavenger at a later time. It may be
42186 necessary to wait until the next bootload.
42187
42188
42189
42190 scavenge_volume.pl1
42191 scavenge_volume: Unable to resolve conflict for
42192 address RRR on dskX_NNS. Error at vtocx NNNN.
42193 ERRORMESSAGE.
42194
42195
42196 Stream: Logged in SYSERR log.
42197
42198 Time: During a physical volume scavenge of dskX_NNS
42199
42200 Meaning: During the VTOC walk the scavenger found several
42201 VTOCEs claiming the save address RRR. It was
42202 unable to resolve the conflict due to a VTOCE read
42203 error.
42204
42205 Action: After the volume has been repaired rerun the
42206 scavenger.
42207
42208
42209
42210 scavenge_volume.pl1
42211 scavenge_volume: vtoce NAME at VTOCX
42212 dskX_NNS. cur len changed from X to Y
42213
42214
42215 Stream: Logged in SYSERR log.
42216
42217 Time: During a physical volume scavenge of dskX_NNS
42218
42219 Meaning: The current segment length field in the VTOCE has
42220 been corrected. The segment has been damaged.
42221
42222 Action: Recover the segment.
42223
42224
42225 scavenge_volume -728- MR12.5 10/27/92^L
42226
42227
42228 scavenge_volume.pl1
42229 scavenge_volume: vtoce NAME at VTOCX
42230 dskX_NNS. max len changed from X to Y
42231
42232
42233 Stream: Logged in SYSERR log.
42234
42235 Time: During a physical volume scavenge of dskX_NNS
42236
42237 Meaning: The max length field in the VTOCE has been
42238 corrected. The segment has been damaged.
42239
42240 Action: Recover the segment.
42241
42242
42243
42244 scavenge_volume.pl1
42245 scavenge_volume: vtoce NAME at VTOCX
42246 dskX_NNS. rec used changed from X to Y
42247
42248
42249 Stream: Logged in SYSERR log.
42250
42251 Time: During a physical volume scavenge of dskX_NNS
42252
42253 Meaning: The records used field in the VTOCE has been
42254 corrected. The segment has been damaged.
42255
42256 Action: Recover the segment.
42257
42258
42259
42260 scavenge_volume.pl1
42261 scavenge_volume: vtoce NAME at VTOCX
42262 dskX_NNS. ref to pageno PPP at addr RRR
42263 deleted
42264
42265
42266 Stream: Logged in SYSERR log.
42267
42268 Time: During a physical volume scavenge of dskX_NNS
42269
42270 Meaning: Address RRR was claimed by more than one VTOCE.
42271 The page indicated has been changed to a null
42272 page and the segment has been damaged.
42273
42274 Action: Recover the segment.
42275
42276
42277
42278
42279
42280
42281
42282
42283 scavenge_volume -729- MR12.5 10/27/92^L
42284
42285
42286 scavenge_volume.pl1
42287 scavenge_volume: vtoce NAME at VTOCX
42288 dskX_NNS. time-record-product reset to zero
42289
42290
42291 Stream: Logged in SYSERR log.
42292
42293 Time: During a physical volume scavenge of dskX_NNS
42294
42295 Meaning: An invalid value was found in the
42296 time-record-product field of the VTOCE indicated.
42297 This field has been reset to zero.
42298
42299 Action: No operator action is required.
42300
42301
42302
42303 scavenger.pl1
42304 scavenger: Begin scavenge of dskX_NNs by
42305 PERSON.PROJECT.TAG
42306
42307
42308 Stream: BOS Typewriter.
42309
42310 Time: When a physical volume is being scavenged
42311
42312 Meaning: This is an informational message at the beginning
42313 of a volume scavenge.
42314
42315 Action: No operator action is required.
42316
42317
42318
42319 scavenger.pl1
42320 scavenger: Invalid block reset.
42321
42322
42323 Stream: BOS Typewriter Crashes system
42324
42325 Time: When a physical volume is being scavenged.
42326
42327 Meaning: A process attempted to clean up a scavenger block
42328 which was not assigned to it. This indicates a
42329 software malfunction.
42330
42331 Action: Follow normal recovery procedures.
42332
42333
42334
42335
42336
42337
42338
42339
42340
42341 scavenger -730- MR12.5 10/27/92^L
42342
42343
42344 scavenger.pl1
42345 scavenger: Meters from scavenge of dskX_NNs.
42346 METERINGDATA.
42347
42348
42349 Stream: Logged in SYSERR log.
42350
42351 Time: When a physical volume is being scavenged.
42352
42353 Meaning: Various peformance measurements of the scavenge
42354 are recorded if the appropriate scavenger control
42355 flag is set.
42356
42357 Action: No operator action is required.
42358
42359
42360
42361 scavenger.pl1
42362 scavenger: Process table entry not owned by this
42363 process.
42364
42365
42366 Stream: BOS Typewriter Crashes system
42367
42368 Time: When a physical volume is being scavenged.
42369
42370 Meaning: The scavenger attempted to release a process table
42371 entry which did not belong to this process. This
42372 indicates a software malfunction.
42373
42374 Action: Follow normal recovery procedures.
42375
42376
42377
42378 scavenger.pl1
42379 scavenger: Scavenge of dskX_NNs by
42380 PERSON.PROJECT.TAG completed with error.
42381 ERRORMESSAGE.
42382
42383
42384 Stream: BOS Typewriter.
42385
42386 Time: When a physical volume is being scavenged.
42387
42388 Meaning: Scavenging could not be completed because of the
42389 error indicated.
42390
42391 Action: Contact the system programming staff.
42392
42393
42394
42395
42396
42397
42398
42399 scavenger -731- MR12.5 10/27/92^L
42400
42401
42402 scavenger.pl1
42403 scavenger: Scavenge of dskX_NNs by
42404 PERSON.PROJECT.TAG completed.
42405
42406
42407 Stream: BOS Typewriter.
42408
42409 Time: When a physical volume is being scavenged.
42410
42411 Meaning: This is an informational message to indicate
42412 successful completion of a scavenge.
42413
42414 Action: No operator action is required.
42415
42416
42417
42418 scavenger.pl1
42419 scavenger: Scavenge of dskX_NNs stopped.
42420
42421
42422 Stream: BOS Typewriter.
42423
42424 Time: During system shutdown.
42425
42426 Meaning: The system is being shutdown and a scavenge of
42427 dskX_NNs is in progress. The scavenge is
42428 terminated and likely had no effect.
42429
42430 Action: Rerun the scavenge.
42431
42432
42433
42434 scavenger.pl1
42435 scavenger: XXXXXX condition signalled during
42436 scavenge of dskX_NNs by PERSON.PROJECT.TAG
42437
42438
42439 Stream: BOS Typewriter.
42440
42441 Time: When a physical volume is being scavenged.
42442
42443 Meaning: An unexpected XXXXXX condition was signalled
42444 during a volume scavenge causing abnormal
42445 termination of the scavenge.
42446
42447 Action: Contact the system programming staff.
42448
42449
42450
42451
42452
42453
42454
42455
42456
42457 scavenger -732- MR12.5 10/27/92^L
42458
42459
42460 scr_util.pl1
42461 scr_util: error setting configuration register.
42462 SCU X must be set manually. Set the following
42463 switches on SCU X < Diagram of SCU Maintenance
42464 Panel is Printed Here> After setting the switches
42465 for SCU X place SCU S into Manual Mode and then
42466 into Program Mode
42467
42468 Stream: BOS Typewriter sounds beeper
42469
42470
42471 Time: Reconfiguration e.g. adding or deleting a CPU
42472
42473 Meaning: The supervisor was unable to set the configuration
42474 register in the SCU indicated after 10 attempts.
42475 To avoid a system crash the SCU must be cleared
42476 manually. In this message the supervisor will
42477 print a diagram of the SCU Maintenance Panel
42478 indicating how each switch should be set.
42479
42480 Action: The operator should copy the diagram of the SCU
42481 Maintenance Panel printed by the supervisor or
42482 take the copy printed if possible. The operator
42483 should then go to the Maintenance Panel of the SCU
42484 indicated and set each switch on the diagram to
42485 the indicated position and then verify that each
42486 switch is in the correct position. Following
42487 this the operator should set the Program/Manual
42488 switch into the Manual position briefly and then
42489 return it to the Program position. If this
42490 procedure does not remedy the problem the message
42491 will be repeated and the System Programming Staff
42492 should be contacted.
42493
42494
42495
42496 scs_and_clock_init.pl1
42497 scs_and_clock_init: No CLOK card.
42498
42499
42500 Stream: BOS Typewriter Crashes system
42501
42502 Time: System Intialization.
42503
42504 Meaning: No CLOK card was found in the config deck. One is
42505 required.
42506
42507 Action: Add a CLOK card to the config deck.
42508
42509
42510
42511
42512
42513
42514
42515 scs_and_clock_init -733- MR12.5 10/27/92^L
42516
42517
42518 scs_and_clock_init.pl1
42519 scs_and_clock_init: No SCU port is assigned
42520 address zero.
42521
42522
42523 Stream: BOS Typewriter Crashes system
42524
42525 Time: System Intialization.
42526
42527 Meaning: None of the system controllers in the config deck
42528 appear to have a base address of zero.
42529
42530 Action: Check the config deck and bootload processor port
42531 assignment and address switches.
42532
42533
42534
42535 scs_and_clock_init.pl1
42536 scs_and_clock_init: SCU clock on port NUMBER
42537 MALFUNCTION.
42538
42539
42540 Stream: BOS Typewriter Crashes system
42541
42542 Time: System Intialization.
42543
42544 Meaning: The calendar clock in the bootload SCU seems to be
42545 malfunctioning as specified by MALFUNCTION.
42546
42547 Action: Fix the SCU or configure another SCU as low
42548 order.
42549
42550
42551
42552
42553
42554
42555
42556
42557
42558
42559
42560
42561
42562
42563
42564
42565
42566
42567
42568
42569
42570
42571
42572
42573 scs_and_clock_init -734- MR12.5 10/27/92^L
42574
42575
42576 scs_and_clock_init.pl1
42577 scs_and_clock_init: The zone on the CLOK card is
42578 not in time_info_.
42579
42580
42581 Stream: BOS Typewriter Crashes system
42582
42583 Time: System Intialization.
42584
42585 Meaning: The zone named on the CLOK card is not found in
42586 time_info_ the system's time information
42587 database. The system cannot run unless a known
42588 zone is specified.
42589
42590 Action: Update the CLOK card so that it contains a proper
42591 zone name. If the zone you need is not known to
42592 the system time_info_.cds will have to be
42593 updated a new system tape generated and then
42594 booting from that tape. time_info_ contains at
42595 least 1 name for each hour around the world. You
42596 may select a named zone near the one you need
42597 just to get the system up to be able to change
42598 time_info_.
42599
42600
42601
42602
42603 scas_init.pl1
42604 scs_init: CPU/IOM port range overlap. Using
42605 manual settings for cycle port priority.
42606
42607
42608 Stream: BOS Typewriter.
42609
42610 Time: System Intialization.
42611
42612 Meaning: The cycle port priority on the SCUs cannot be set
42613 optimally because the range of port numbers for
42614 CPUs and IOMs overlap. The manual settings of the
42615 cycle port priority switches on the SCUs will be
42616 used instead. The system may experience problems
42617 as a result with the typical symptom being
42618 op-not-complete faults at random times by CPUs
42619 with higher port numbers lower SCU port
42620 priority.
42621
42622 Action: Continue to operate the system normally but
42623 consult with Field Engineering personnel. If
42624 possible the system should be reconfigured so
42625 that the range of port numbers of IOMs and CPU do
42626 not overlap. Further CPU should be on
42627 higher-numbered ports than IOMs and Bulk Stores.
42628
42629
42630
42631 scs_init -735- MR12.5 10/27/92^L
42632
42633
42634 alm_syserr_caller.pl1
42635 search_ast: double uid UID. vtocx VTOCX on
42636 DRIVEPVID. active vtocx VTOCX2 on
42637 DRIVE2PVID2.
42638
42639
42640 Stream: Logged in SYSERR log.
42641
42642 Time: While system is running.
42643
42644 Meaning: A mismatch has been detected between the branch
42645 and the ASTE for a segment. The two segments
42646 indicated by VTOCE index and physical volume
42647 location/identifier claim to have the same file
42648 system unique identifier. The operation either
42649 proceeds or returns a connection failure to the
42650 user process as appropriate. This message is
42651 logged for the use of system programmers.
42652
42653 This error can occur if damage to a directory
42654 branch has caused its unique ID to become
42655 incorrect and if the incorrect unique ID happens
42656 to be identical to the unique ID of a segment
42657 already active.
42658
42659 Action: Contact the system programming staff.
42660
42661
42662
42663 alm_syserr_caller.pl1
42664 search_ast: hash error
42665
42666
42667 Stream: BOS Typewriter Crashes system
42668
42669 Time: While system is running.
42670
42671 Meaning: This indicates a logic error in the supervisor or
42672 CPU or memory hardware problems.
42673
42674 Action: Follow normal recovery procedures.
42675
42676
42677
42678
42679
42680
42681
42682
42683
42684
42685
42686
42687
42688
42689 search_ast -736- MR12.5 10/27/92^L
42690
42691
42692 seg_fault.pl1
42693 seg_fault: illegal segfault on cpu X
42694
42695
42696 Stream: BOS Typewriter.
42697
42698 Time: While system is running.
42699
42700 Meaning: The SCU data stored by processor X indicates that
42701 a segment fault has occurred but the SDW indicated
42702 by the SCU data has no directed fault indicator.
42703 This indicates a logic error in the supervisor or
42704 CPU or memory hardware problems. The system
42705 attempts to retry the faulting instruction.
42706
42707 Action: Inform field engineering personnel. If this
42708 message persists attempt to delete the CPU.
42709
42710
42711
42712 seg_fault.pl1
42713 seg_fault: trailer list trap
42714
42715
42716 Stream: BOS Typewriter Crashes system
42717
42718 Time: While system is running.
42719
42720 Meaning: An attempt was made to set sst$tfreep to zero.
42721 The supervisor checks for this situation and
42722 crashes here when one entry remains in the trailer
42723 segment in order to trap an elusive bug which used
42724 to cause "trailer storage area exhausted" crashes
42725 when the trailer segment was not full. This
42726 indicates a logic error in the supervisor or CPU
42727 or memory hardware problems. This error crashes
42728 the system.
42729
42730 Action: Follow normal recovery procedures. Be sure to get
42731 a dump.
42732
42733
42734
42735
42736
42737
42738
42739
42740
42741
42742
42743
42744
42745
42746
42747 seg_fault -737- MR12.5 10/27/92^L
42748
42749
42750 seg_fault.pl1
42751 seg_fault: trailer storage area exhausted
42752
42753
42754 Stream: BOS Typewriter Crashes system
42755
42756 Time: While system is running.
42757
42758 Meaning: There are no more free entries available in the
42759 system trailer segment str_seg. This may be
42760 indicative of software- or hardware-induced damage
42761 to the SST or str_seg or may be indicative of a
42762 number of logged-in processes which is vastly too
42763 large. A more likely cause is insufficiently
42764 large str_seg. The size of the str_seg can be
42765 changed by the TBLS STR card in the config deck.
42766 This indicates a logic error in the supervisor or
42767 CPU or memory hardware problems. This error
42768 crashes the system.
42769
42770 Action: Follow normal recovery procedures. It may be
42771 necessary to increase the size of the str_seg by
42772 the TBLS STR card in the config deck. Be sure to
42773 get a dump.
42774
42775
42776
42777 segment_loader.pl1
42778 segment_loader: bad header size: SSS
42779
42780
42781 Stream: BOS Typewriter Crashes system
42782
42783 Time: System Intialization.
42784
42785 Meaning: A bad segment header was found in the mst source.
42786
42787 Action: Follow normal recovery procedures. The Multics
42788 System Tape may be incorrect. If the problem
42789 persists try another MST.
42790
42791
42792
42793
42794
42795
42796
42797
42798
42799
42800
42801
42802
42803
42804
42805 segment_loader -738- MR12.5 10/27/92^L
42806
42807
42808 segment_loader.pl1
42809 segment_loader: error from
42810 slt_manager$build_entry
42811
42812
42813 Stream: BOS Typewriter Crashes system
42814
42815 Time: System Intialization.
42816
42817 Meaning: This indicates a logic error in the supervisor or
42818 CPU or memory hardware problems.
42819
42820 Action: Follow normal recovery procedures. The Multics
42821 System Tape may be incorrect. If the problem
42822 persists try another MST.
42823
42824
42825
42826 segment_loader.pl1
42827 segment_loader: Missing linkage or defs.
42828
42829
42830 Stream: BOS Typewriter Crashes system
42831
42832 Time: System Intialization.
42833
42834 Meaning: A linkage or definitions section which should be
42835 in the mst source appears to be missing.
42836
42837 Action: Follow normal recovery procedures. The Multics
42838 System Tape may be incorrect. If the problem
42839 persists try another MST.
42840
42841
42842
42843 segment_loader.pl1
42844 segment_loader: unexpected control type: TTT
42845
42846
42847 Stream: BOS Typewriter Crashes system
42848
42849 Time: System Intialization.
42850
42851 Meaning: A segment control word was found out of sequence
42852 in the mst source.
42853
42854 Action: Follow normal recovery procedures. The Multics
42855 System Tape may be incorrect. If the problem
42856 persists try another MST.
42857
42858
42859
42860
42861
42862
42863 segment_loader -739- MR12.5 10/27/92^L
42864
42865
42866 segment_loader.pl1
42867 segment_loader: Unexpected DEFS/LINKAGE
42868
42869
42870 Stream: BOS Typewriter Crashes system
42871
42872 Time: System Intialization.
42873
42874 Meaning: A linkage or definitions section was found out of
42875 sequence in the mst source.
42876
42877 Action: Follow normal recovery procedures. The Multics
42878 System Tape may be incorrect. If the problem
42879 persists try another MST.
42880
42881
42882
42883 segment_loader.pl1
42884 segment_loader: unknown control type TTT
42885
42886
42887 Stream: BOS Typewriter Crashes system
42888
42889 Time: System Intialization.
42890
42891 Meaning: A bad segment control word was found in the mst
42892 source.
42893
42894 Action: Follow normal recovery procedures. The Multics
42895 System Tape may be incorrect. If the problem
42896 persists try another MST.
42897
42898
42899
42900
42901
42902
42903
42904
42905
42906
42907
42908
42909
42910
42911
42912
42913
42914
42915
42916
42917
42918
42919
42920
42921 segment_loader -740- MR12.5 10/27/92^L
42922
42923
42924 segment_mover.pl1
42925 segment_mover: critical segment out of disk on
42926 DRIVENAME segno/astep = sss/aaa
42927
42928
42929 Stream: BOS Typewriter.
42930
42931 Time: While system is running.
42932
42933 Meaning: There are no more free pages on the physical
42934 volume where a critical segment resides and an
42935 extra page can not be found for that segment.
42936 Such a critical segment may be a physical buffer
42937 segment for a peripheral device attached via IOI.
42938 The user process receives a seg_fault_error
42939 signal.
42940
42941 Action: The logical volume containing the pack residing on
42942 DRIVENAME may be too full or may need rebalancing
42943 with the sweep_pv tool. Contact the system
42944 administrator.
42945
42946
42947
42948 segment_mover.pl1
42949 segment_mover: Failed to seg move UUUENTRYNAME
42950 from DRIVENAME1 to DRIVENAME2 for USERNAME
42951
42952
42953 Stream: Logged in SYSERR log.
42954
42955 Time: While system is running.
42956
42957 Meaning: The system could not perform a cross-pack segment
42958 move because no pack in the logical volume had
42959 enough space to hold the segment. UUUU is the
42960 unique ID of the segment and ENTRYNAME its
42961 primary name.
42962
42963 Action: If this message persists the logical volume
42964 containing the packs on the drives noted is near
42965 full. In this case contact the system
42966 administrator.
42967
42968
42969
42970
42971
42972
42973
42974
42975
42976
42977
42978
42979 segment_mover -741- MR12.5 10/27/92^L
42980
42981
42982 segment_mover.pl1
42983 segment_mover: finishing truncation of pvtx PPP
42984 vtocx VVV
42985
42986
42987 Stream: BOS Typewriter.
42988
42989 Time: While system is running.
42990
42991 Meaning: The segment mover encountered an unexpected error
42992 in truncating either the old copy of a segment
42993 being moved cross-packs or in a new copy which was
42994 aborted for lack of space. This may be a physical
42995 device error or may be indicative of a logic
42996 problem in the supervisor or may be symptomatic
42997 of main memory or CPU problems.
42998
42999 Action: Contact the system programming staff.
43000
43001
43002
43003 segment_mover.pl1
43004 segment_mover: freeing vtocx VVV on new pvtx PPP.
43005 ERRORMESSAGE
43006
43007
43008 Stream: BOS Typewriter.
43009
43010 Time: While system is running.
43011
43012 Meaning: The segment mover encountered an unexpected error
43013 in freeing the VTOC entry of a segment being moved
43014 on a volume to which an abortive attempt to move
43015 the segment was made. This may be a physical
43016 device error.
43017
43018 Action: Contact the system programming staff.
43019
43020
43021
43022
43023
43024
43025
43026
43027
43028
43029
43030
43031
43032
43033
43034
43035
43036
43037 segment_mover -742- MR12.5 10/27/92^L
43038
43039
43040 segment_mover.pl1
43041 segment_mover: freeing vtocx VVV on old pvtx PPP
43042 ERRORMESSAGE
43043
43044
43045 Stream: BOS Typewriter.
43046
43047 Time: While system is running.
43048
43049 Meaning: During a cross-pack segment move the system
43050 encountered an unexpected error in freeing the
43051 VTOC entry of the segment on the old pack This may
43052 be a physical device error or may be indicative
43053 of a logic problem in the supervisor or main
43054 memory or CPU problems.
43055
43056 Action: Contact the system programming staff.
43057
43058
43059
43060 segment_mover.pl1
43061 segment_mover: get_pvtx PPP fails under ast
43062 lock
43063
43064
43065 Stream: BOS Typewriter Crashes system
43066
43067 Time: While system is running.
43068
43069 Meaning: The segment mover found that a physical volume
43070 appears to have been demounted during the time
43071 that the segment mover has had the active segment
43072 table locked. This indicates a logic error in the
43073 supervisor or CPU or memory hardware problems.
43074
43075 Action: Follow normal recovery procedures.
43076
43077
43078
43079
43080
43081
43082
43083
43084
43085
43086
43087
43088
43089
43090
43091
43092
43093
43094
43095 segment_mover -743- MR12.5 10/27/92^L
43096
43097
43098 segment_mover.pl1
43099 segment_mover: Moved UUUUENTRYNAME from
43100 DRIVENAME1 to DRIVENAME2 for USERNAME
43101
43102
43103 Stream: Logged in SYSERR log.
43104
43105 Time: While system is running.
43106
43107 Meaning: The system has successfully moved a segment from
43108 the pack on DRIVENAME1 to the pack on DRIVENAME2
43109 on a request for a new page on behalf of the user
43110 whose process group ID is USERNAME. UUUU is the
43111 unique ID of the segment and ENTRYNAME its
43112 primary name.
43113
43114 Action: If a large number of these messages occur the
43115 logical volume containing the packs specified by
43116 the drive names may be nearly full or poorly
43117 balanced. If these messages persist contact the
43118 system administrator.
43119
43120
43121
43122 segment_mover.pl1
43123 segment_mover: Moving QUOTA-TYPE quota account
43124 from pvtx PPP vtocx VVV ERRORMESSAGE
43125
43126
43127 Stream: Logged in SYSERR log.
43128
43129 Time: While system is running.
43130
43131 Meaning: An error code was returned from the entry
43132 vtoc_attributes$get_quota when attempting to get
43133 terminal quota information from the old vtoce
43134 before new vtoce is created. In this case the
43135 terminal quota attributes for this QUOTA-TYPE
43136 either segment or directory quota account is
43137 lost.
43138
43139 Action: If this occurs the quota account for the segment
43140 that has been moved must be corrected manually by
43141 the System Administrator or other qualified site
43142 personell.
43143
43144
43145
43146
43147
43148
43149
43150
43151
43152
43153 segment_mover -744- MR12.5 10/27/92^L
43154
43155
43156 segment_mover.pl1
43157 segment_mover: threading error
43158
43159
43160 Stream: BOS Typewriter Crashes system
43161
43162 Time: While system is running.
43163
43164 Meaning: The segment mover encountered bad threads while
43165 rethreading the old or new AST entries of a
43166 segment involved in a cross-pack segment move.
43167 This indicates a logic error in the supervisor or
43168 CPU or memory hardware problems.
43169
43170 Action: Follow normal recovery procedures.
43171
43172
43173
43174 segment_mover.pl1
43175 segment_mover: unexpected segfault
43176
43177
43178 Stream: BOS Typewriter Crashes system
43179
43180 Time: While system is running.
43181
43182 Meaning: A segment fault occured during the cross-pack
43183 moving of a segment but this segment fault was
43184 not on the segment on which the segment mover was
43185 expecting one. This indicates a logic error in
43186 the supervisor or CPU or memory hardware
43187 problems.
43188
43189 Action: Follow normal recovery procedures. There may be
43190 inconsistencies in the physical volumes involved.
43191 These can be corrected by a physical volume
43192 salvage.
43193
43194
43195
43196
43197
43198
43199
43200
43201
43202
43203
43204
43205
43206
43207
43208
43209
43210
43211 segment_mover -745- MR12.5 10/27/92^L
43212
43213
43214 set_procs_required.pl1
43215 set_procs_required: Changing system default CPUs
43216 required from XXXX to YYYY for PERSON.PROJECT.TAG
43217
43218
43219 Stream: BOS Typewriter.
43220
43221 Time: While system is running.
43222
43223 Meaning: The default set of CPUs has been changed from XXXX
43224 CPU tags to YYYY CPU tags by
43225 PERSON.PROJECT.TAG. These are the only CPUs on
43226 which processes will run which have not requested
43227 to be run on specific CPUs.
43228
43229 Action: No operator action is required.
43230
43231
43232
43233 set_procs_required.pl1
43234 set_procs_required: Changing system default CPUs
43235 required from XXXX to YYYY for PERSON.PROJECT.TAG
43236
43237
43238 Stream: BOS Typewriter.
43239
43240 Time: While system is running.
43241
43242 Meaning: The default set of CPUs has been changed from XXXX
43243 CPU tags to YYYY CPU tags by
43244 PERSON.PROJECT.TAG. These are the only CPUs on
43245 which processes will run which have not requested
43246 to be run on specific CPUs.
43247
43248 Action: No operator action is required.
43249
43250
43251
43252 set_procs_required.pl1
43253 set_procs_required: Failed to check access for
43254 USER.
43255
43256
43257 Stream: Logged in SYSERR log.
43258
43259 Time: While system is running.
43260
43261 Meaning: Access on >sc1>admin_acs>set_proc_required.acs
43262 could not be checked.
43263
43264 Action: Verify that the ACS seg exists.
43265
43266
43267
43268
43269 set_procs_required -746- MR12.5 10/27/92^L
43270
43271
43272 set_procs_required.pl1
43273 set_procs_required: Failed to check access for
43274 USER.
43275
43276
43277 Stream: Logged in SYSERR log.
43278
43279 Time: While system is running.
43280
43281 Meaning: Access on >sc1>admin_acs>set_proc_required.acs
43282 could not be checked.
43283
43284 Action: Verify that the ACS seg exists.
43285
43286
43287
43288 setfaults.pl1
43289 setfaults: deleted trailer
43290
43291
43292 Stream: BOS Typewriter Crashes system
43293
43294 Time: While system is running.
43295
43296 Meaning: A trailer entry record of a process's connection
43297 to a segment for some segment was marked as free.
43298 This indicates a logic error in the supervisor or
43299 CPU or memory hardware problems.
43300
43301
43302 Action: Follow normal recovery procedures. Contact the
43303 system programming staff.
43304
43305
43306
43307 setfaults.pl1
43308 setfaults: illegal cache access trailer
43309
43310
43311 Stream: BOS Typewriter Crashes system
43312
43313 Time: While system is running.
43314
43315 Meaning: It was found that no record of processes connected
43316 to a segment trailers existed when the
43317 encacheability state of a segment had to be
43318 changed. Such change can only occur if processes
43319 are connected to the segment. This indicates a
43320 logic error in the supervisor or CPU or memory
43321 hardware problems.
43322
43323 Action: Be sure to get a dump. Follow normal recovery
43324 procedures. Contact the system programming staff.
43325
43326
43327 setfaults -747- MR12.5 10/27/92^L
43328
43329
43330 setfaults.pl1
43331 setfaults: illegal trailer
43332
43333
43334 Stream: BOS Typewriter Crashes system
43335
43336 Time: While system is running.
43337
43338 Meaning: A trailer entry record of a process's connection
43339 to a segment for some segment specifies a second
43340 segment as the descriptor segment for some process
43341 connected to that segment but that second segment
43342 does not have certain bits on in its AST entry
43343 which would be on in the AST entry of a descriptor
43344 segment. This indicates a logic error in the
43345 supervisor or CPU or memory hardware problems.
43346
43347 Action: Follow normal recovery procedures. Contact the
43348 system programming staff.
43349
43350
43351
43352 setfaults.pl1
43353 setfaults: missing trailer
43354
43355
43356 Stream: BOS Typewriter Crashes system
43357
43358 Time: While system is running.
43359
43360 Meaning: Upon terminating a segment it was found that no
43361 record of the process's connection to that segment
43362 trailer existed even though an SDW for that
43363 segment appeared in the process's descriptor
43364 segment i.e. the process was connected to it.
43365 This indicates a logic error in the supervisor or
43366 CPU or memory hardware problems.
43367
43368 Action: Follow normal recovery procedures. Contact the
43369 system programming staff.
43370
43371
43372
43373
43374
43375
43376
43377
43378
43379
43380
43381
43382
43383
43384
43385 setfaults -748- MR12.5 10/27/92^L
43386
43387
43388 shutdown_file_system.pl1
43389 shutdown complete
43390
43391
43392 Stream: BOS Typewriter.
43393
43394 Time: System shutdown
43395
43396 Meaning: System shutdown emergency or regular has
43397 completed successfully. The system will return to
43398 bce. If any problem arises such that the system
43399 does not return to bce or other error condition
43400 the storage system will probably not be affected.
43401 If such problem arises attempt ESD. The message
43402 "system already shut down" will be printed if
43403 there is no problem. When the "shutdown complete"
43404 message is issued there is no more Multics
43405 information in main memory.
43406
43407
43408
43409 wired_shutdown.pl1
43410 shutdown complete
43411
43412
43413 Stream: BOS Typewriter.
43414
43415 Time: Emergency shutdown
43416
43417 Meaning: Emergency shutdown is complete; this message was
43418 preceded by either "esd before fs enabled" or
43419 "system already shut down": no ESD was necessary.
43420
43421 Action: Reboot the system.
43422
43423
43424
43425
43426
43427
43428
43429
43430
43431
43432
43433
43434
43435
43436
43437
43438
43439
43440
43441
43442
43443 shutdown complete -749- MR12.5 10/27/92^L
43444
43445
43446 shutdown_file_system.pl1
43447 shutdown complete except for devices suspended.
43448
43449
43450 Stream: BOS Typewriter sounds beeper
43451
43452 Time: System shutdown
43453
43454 Meaning: Some disks could not be shut down due to hardware
43455 problems. Messages have occurred identifying
43456 these drives and the problems. All other drives
43457 have been shut down- their contents are not in
43458 main memory or on the paging device. The RPV has
43459 not been shut down either so that the system will
43460 perform some salvaging when it comes up.
43461
43462 Action: Attempt to ready those drives that are not ready.
43463 When this has been done retry ESD. If the drives
43464 have been made accessible ESD will succeed with a
43465 normal "shutdown complete" message. If they
43466 cannot be made ready the paging device if any
43467 is unflushed. See the description of the
43468 "warning: paging device unflushed" message.
43469
43470
43471
43472 shutdown.pl1
43473 shutdown: Cannot run on CPU X bootload CPU.
43474 Dump and try ESD. ERRORMESSAGE
43475
43476
43477 Stream: BOS Typewriter Crashes system
43478
43479 Time: System shutdown
43480
43481 Meaning: During an attempt to shut down the system the
43482 system could not run on the bootload CPU. This
43483 problem may be due to hardware or software
43484 problems. The system will attempt to crash which
43485 it may not complete.
43486
43487 Action: If the system does not complete its attempt to
43488 crash it should be crashed manually. It may be
43489 necessary to change the bootload CPU manually.
43490 This can be done by putting all CPUs into STEP
43491 mode manually assigning an interrupt mask to the
43492 new bootload CPU from the bootload SCU maintenance
43493 panel taking only the new bootload CPU out of
43494 STEP mode and doing an EXECUTE SWITCHES on that
43495 CPU. Once the system has crashed successfully an
43496 ESD should be attempted. This will most likely
43497 succeed.
43498
43499
43500
43501 shutdown -750- MR12.5 10/27/92^L
43502
43503
43504 shutdown.pl1
43505 shutdown: Condition CCCC signalled during
43506 shutdown. Normal shutdown failed. Get a dump
43507 and try an ESD.
43508
43509
43510 Stream: BOS Typewriter Crashes system
43511
43512 Time: System shutdown
43513
43514 Meaning: During the attempt to shut down the system an
43515 unexpected condition has been signalled. This may
43516 result from hardware problems or a logic error in
43517 the supervisor. The system crashes and returns to
43518 BCE whereupon an ESD should be attempted in order
43519 to finish flushing Multics information from main
43520 memory. Because of the difference in
43521 implementation between normal shutdown and ESD it
43522 is possible that ESD will not encounter the same
43523 problem and instead be successful.
43524
43525
43526
43527 shutdown.pl1
43528 shutdown: Could not stop CPU TAG.
43529
43530
43531 Stream: BOS Typewriter.
43532
43533 Time: System shutdown.
43534
43535 Meaning: Shutdown stops all but the bootload processor.
43536 The CPU whose tag is TAG could not be stopped.
43537
43538 Action: Note for system programmer action. If shutdown
43539 fails put all CPU's other than the bootload
43540 processor in step return to BCE manually and
43541 attempt an ESD.
43542
43543
43544
43545
43546
43547
43548
43549
43550
43551
43552
43553
43554
43555
43556
43557
43558
43559 shutdown -751- MR12.5 10/27/92^L
43560
43561
43562 shutdown_file_system.pl1
43563 shutdown_file_system: Error deactivating. Quota
43564 may be bad.
43565
43566
43567 Stream: BOS Typewriter.
43568
43569 Time: System shutdown
43570
43571 Meaning: The attempt to deactivate all segments in the file
43572 system by a tree-walk of threaded ASTEs failed
43573 likely due to inconsistent threading in the SST.
43574 The segments will be deactivated by a linear walk
43575 of the SST. Quota inconsistencies may be
43576 introduced by this. These can be corrected by a
43577 quota salvage of the hierarchy.
43578
43579 Action: At a convenient time run a quota salvage of the
43580 hierarchy.
43581
43582
43583
43584 shutdown_file_system.pl1
43585 shutdown_file_system: from demount_pv on PVTX
43586 ERROR_MESSAGE
43587
43588
43589 Stream: BOS Typewriter.
43590
43591 Time: System shutdown
43592
43593 Meaning: A problem was encountered in shutting down the
43594 disk whose PVT index is PVTX. Most likely other
43595 messages identifying the pack drive and/or
43596 problem have preceded this message.
43597
43598 Action: Note for system programmer action. If other
43599 messages have preceded this message take remedial
43600 action as necessary. Attempt emergency shutdown
43601 after readying appropriate disk drives if this is
43602 the problem.
43603
43604
43605
43606
43607
43608
43609
43610
43611
43612
43613
43614
43615
43616
43617 shutdown_file_system -752- MR12.5 10/27/92^L
43618
43619
43620 shutdown_file_system.pl1
43621 shutdown_file_system: NN locks set
43622
43623
43624 Stream: BOS Typewriter.
43625
43626 Time: System shutdown
43627
43628 Meaning: Not all data base and directory locks were
43629 unlocked by the system before shutdown started.
43630 During emergency shutdown this is to be expected.
43631 During normal shutdown this may be symptomatic of
43632 software problems.
43633
43634 Action: If this message occurs during normal shutdown
43635 note for system programming staff.
43636
43637
43638
43639 start_cpu.pl1
43640 start_cpu: Added CPU CPUTAG
43641
43642
43643 Stream: BOS Typewriter.
43644
43645 Time: In response to an operator "rcf add cpu CPUTAG"
43646 command or at bootload time.
43647
43648 Meaning: The system has successfully added the CPU whose
43649 tag is CPUTAG to the configuration.
43650
43651 Action: No operator action is required.
43652
43653
43654
43655 start_cpu.pl1
43656 start_cpu: CPU CPUTAG data switches are
43657 XXXXXXXXXXXX should be YYYYYYYYYYYY
43658
43659
43660 Stream: BOS Typewriter.
43661
43662 Time: In response to an "rcf add cpu CPUTAG" command
43663
43664 Meaning: The data switches on the CPU indicated are not set
43665 properly. The proper value is given.
43666
43667 Action: The incorrect value will prevent returning to BCE
43668 on that CPU by means of EXECUTE SWITCHES. Certain
43669 incorrect values will activate software debugging
43670 traps. The switches should be corrected. This
43671 can be done while the CPU is running.
43672
43673
43674
43675 start_cpu -753- MR12.5 10/27/92^L
43676
43677
43678 start_cpu.pl1
43679 start_cpu: CPU CPUTAG: Model #: MODEL; Serial
43680 #: SERIAL; Ship date: YY/MM/DD.
43681
43682
43683 Stream: Logged in SYSERR log.
43684
43685 Time: When a DPS8 CPU whose tag is CPUTAG is added to
43686 the system.
43687
43688 Meaning: The MODEL SERIAL and YY/MM/DD information is read
43689 from the DPS8 cpu's ID PROM. It is intended to be
43690 used as historical information for identifing
43691 CPUs regardless of what their current tag is
43692 assigned as.
43693
43694 Action: No operator action is required.
43695
43696
43697
43698 start_cpu.pl1
43699 start_cpu: Unable to run on CPU x ERRORMESSAGE
43700
43701
43702 Stream: BOS Typewriter Crashes system
43703
43704 Time: In response to an "rcf add cpu CPUTAG" command or
43705 at bootload
43706
43707 Meaning: After adding a CPU the system was unable to run
43708 on that CPU. This indicates hardware or software
43709 failure.
43710
43711 Action: Follow normal recovery procedures.
43712
43713
43714
43715 page_error.alm
43716 stock: deposit zero address.
43717
43718
43719 Stream: BOS Typewriter Crashes system
43720
43721 Time: While system is running.
43722
43723 Meaning: An attempt was made to deposit address zero into a
43724 record stock. This is an invalid address and it
43725 indicates hardware or software failure.
43726
43727 Action: Follow normal recovery procedures.
43728
43729
43730
43731
43732
43733 stock -754- MR12.5 10/27/92^L
43734
43735
43736 stock_man.pl1
43737 stock_man: Attempt to free non-empty stock on
43738 dskX_NN: pvtep=XXX|XXXXXX
43739 record_stockp=YYY|YYYYYY
43740
43741
43742 Stream: BOS Typewriter Crashes system
43743
43744 Time: During initialization immediately before the File
43745 System is activated or when demounting a physical
43746 disk volume.
43747
43748 Meaning: Not all free addresses have been deposited to the
43749 Volume Map successfully for the disk volume
43750 indicated. This is indicative of a software
43751 malfunction. The pointers printed are useful to
43752 site system programmers in analyzing the problem.
43753
43754 Action: Follow normal recovery procedures. The free
43755 addresses which are lost may be recovered by a
43756 physical volume salvage.
43757
43758
43759
43760 stock_man.pl1
43761 stock_man: Attempt to free non-empty stock on
43762 dskX_NN: pvtep=XXX|XXXXXX vtoce_stockp=YYY|YYYYYY
43763
43764
43765 Stream: BOS Typewriter Crashes system
43766
43767 Time: When demounting a physical disk volume.
43768
43769 Meaning: Not all free VTOCEs have been deposited to the
43770 VTOC Map successfully for the disk volume
43771 indicated. This is indicative of a software
43772 malfunction. The pointers printed are useful to
43773 site system programmers in analyzing the problem.
43774
43775 Action: Follow normal recovery procedures. The free
43776 VTOCEs which are lost may be recovered by a
43777 physical volume salvage.
43778
43779
43780
43781
43782
43783
43784
43785
43786
43787
43788
43789
43790
43791 stock_man -755- MR12.5 10/27/92^L
43792
43793
43794 stock_man.pl1
43795 stock_man: PVTE out of synch with record stock on
43796 dskX_NN: pvtep = XXX|XXXXXX record_stockp =
43797 YYY|YYYYYY
43798
43799
43800 Stream: BOS Typewriter Crashes system
43801
43802 Time: During initialization immediately before the File
43803 System is activated or when demounting a physical
43804 disk volume.
43805
43806 Meaning: The supervisor databases pvt and stock_seg are not
43807 in proper synchronization. The pointers printed
43808 are the locations of the databasse elements for
43809 which this condition has been detected. These
43810 pointers are useful to the site system programmers
43811 for analyzing the problem which is probably a
43812 software malfunction. dskX_NN is the physical
43813 volume whose tables are affected.
43814
43815 Action: Follow normal recovery procedures. The free
43816 addresses which are lost may be recovered by a
43817 physical volume salvage.
43818
43819
43820
43821 stock_man.pl1
43822 stock_man: PVTE out of synch with VTOCE stock on
43823 dskX_NN: pvtep = XXX|XXXXXX vtoce_stockp =
43824 YYY|YYYYYY
43825
43826
43827 Stream: BOS Typewriter Crashes system
43828
43829 Time: When demounting a physical disk volume.
43830
43831 Meaning: The supervisor databases pvt and stock_seg are not
43832 in proper synchronization. The pointers printed
43833 are the locations of the databasse elements for
43834 which this condition has been detected. These
43835 pointers are useful to the site system programmers
43836 for analyzing the problem which is probably a
43837 software malfunction. dskX_NN is the physical
43838 volume whose tables are affected. Some free
43839 VTOCEs may be lost.
43840
43841 Action: Follow normal recovery procedures. The lost
43842 VTOCEs can be recovered by a physical volume
43843 salvage.
43844
43845
43846
43847
43848
43849 stock_man -756- MR12.5 10/27/92^L
43850
43851
43852 stop_cpu.pl1
43853 stop_cpu: Removed CPU CPUTAG.
43854
43855
43856 Stream: BOS Typewriter.
43857
43858 Time: In response to an operator "rcf dl cpu CPUTAG"
43859 command.
43860
43861 Meaning: The system has successfully deleted the CPU whose
43862 tag is CPUTAG from the configuration. The CPU is
43863 now halted at a DIS instruction.
43864
43865 Action: The operator can but need not physically remove
43866 the CPU from the configuration by disabling
43867 appropriate ports if desired.
43868
43869
43870
43871 stop_cpu.pl1
43872 stop_cpu: Unable to run on CPU X ERRORMESSAGE
43873
43874
43875 Stream: BOS Typewriter Crashes system
43876
43877 Time: When deleting a CPU.
43878
43879 Meaning: The system has just deleted a CPU which owned an
43880 interrupt mask. In trying to assign the mask to a
43881 different CPU X it was unable to run on that
43882 CPU. This indicates hardware or software
43883 malfunction.
43884
43885 Action: Follow normal recovery procedures.
43886
43887
43888
43889
43890
43891
43892
43893
43894
43895
43896
43897
43898
43899
43900
43901
43902
43903
43904
43905
43906
43907 stop_cpu -757- MR12.5 10/27/92^L
43908
43909
43910 stop_cpu.pl1
43911 stop_mpx: CPU CPUTAG is now the bootload
43912 processor.
43913
43914
43915 Stream: BOS Typewriter.
43916
43917 Time: In response to an operator "rcf dl cpu CPUTAG"
43918 command.
43919
43920 Meaning: The CPU whose tag is CPUTAG is now the processor
43921 on which BCE will run at system shutdown or crash
43922 time unless some other processor is so designated
43923 in this way before the next shutdown or crash
43924 time. Unless BCE is rebooted after shutdown that
43925 CPU will be the bootload processor of the next
43926 bootload.
43927
43928 Action: No operator action is required.
43929
43930
43931
43932 stop_process.pl1
43933 stop_process: attempt to stop initializer process
43934
43935
43936 Stream: BOS Typewriter Crashes system
43937
43938 Time: While system is running.
43939
43940 Meaning: This indicates a logic error in the supervisor or
43941 CPU or memory hardware problems.
43942
43943 Action: Follow normal recovery procedures.
43944
43945
43946
43947 sum.pl1
43948 sum: dirmod failed to activate XXX|0
43949
43950
43951 Stream: BOS Typewriter Crashes system
43952
43953 Time: While system is running.
43954
43955 Meaning: Directory control could not activate a directory.
43956 This indicates a logic error in the supervisor or
43957 CPU or memory hardware problems. It is possible
43958 that the AST is damaged.
43959
43960 Action: Follow normal recovery procedures.
43961
43962
43963
43964
43965 sum -758- MR12.5 10/27/92^L
43966
43967
43968 sum.pl1
43969 sum: mylock error on XXX|0
43970
43971
43972 Stream: BOS Typewriter Crashes system
43973
43974 Time: While system is running.
43975
43976 Meaning: A directory which should not be locked is found
43977 locked. This indicates a logic error in the
43978 supervisor or CPU or memory hardware problems.
43979
43980 Action: Follow normal recovery procedures.
43981
43982
43983
43984 sys_trouble.alm
43985 sys_trouble: Out-of-Segment-Bounds on prds.
43986
43987
43988
43989 Stream: BOS Typewriter Crashes system
43990
43991 Time: While system is running.
43992
43993 Meaning: While running with the prds as a stack an attempt
43994 was " made to reference beyond the end of the
43995 prds. The likely " cause was stack overflow due
43996 either to a recursive loop " in the procedures
43997 running on the prds or insufficient " space
43998 allocated for the prds. If the latter the size
43999 of " the prds should be increased by means of the
44000 TBLS Configuration " Card.
44001
44002 Action: Follow normal recovery procedures.
44003
44004
44005
44006 sys_trouble.alm
44007 sys_trouble: Execute fault by operator.
44008
44009
44010
44011 Stream: BOS Typewriter Crashes system
44012
44013 Time: While system is running.
44014
44015 Meaning: Operator depressed execute pushbutton on
44016 processor.
44017
44018 Action: $recov
44019
44020
44021
44022
44023 sys_trouble -759- MR12.5 10/27/92^L
44024
44025
44026 sys_trouble.alm
44027 sys_trouble: Fault in bound_interceptors.
44028
44029
44030
44031 Stream: BOS Typewriter Crashes system
44032
44033 Time: While system is running.
44034
44035 Meaning: A fault occured while handling another fault.
44036
44037 Action: $recov
44038
44039
44040
44041 sys_trouble.alm
44042 sys_trouble: Fault in idle process.
44043
44044
44045
44046 Stream: BOS Typewriter Crashes system
44047
44048 Time: While system is running.
44049
44050 Meaning: This indicates a logic error in the supervisor or
44051 CPU or memory hardware problems.
44052
44053 Action: $recov
44054
44055
44056
44057 sys_trouble.alm
44058 sys_trouble: Fault/interrupt while on prds.
44059
44060
44061
44062 Stream: BOS Typewriter Crashes system
44063
44064 Time: While system is running.
44065
44066 Meaning: This indicates a logic error in the supervisor or
44067 CPU or memory hardware problems.
44068
44069 Action: $recov
44070
44071
44072
44073
44074
44075
44076
44077
44078
44079
44080
44081 sys_trouble -760- MR12.5 10/27/92^L
44082
44083
44084 sys_trouble.alm
44085 sys_trouble: Fault/interrupt with ptl set.
44086
44087
44088
44089 Stream: BOS Typewriter Crashes system
44090
44091 Time: While system is running.
44092
44093 Meaning: This indicates a logic error in the supervisor or
44094 CPU or memory hardware problems.
44095
44096 Action: $recov
44097
44098
44099
44100 sys_trouble.alm
44101 sys_trouble: Interrupts Masked in User Ring.
44102
44103
44104
44105 Stream: BOS Typewriter Crashes system
44106
44107 Time: While system is running.
44108
44109 Meaning: During processing of a fault it was noticed that
44110 interrupts " were masked in user-ring an invalid
44111 condition. This is a " debug trap crash enabled
44112 by the hidden tuning parameter "
44113 trap_invalid_masked.
44114
44115 Action: Contact the Multics System Development staff.
44116
44117
44118
44119 sys_trouble.alm
44120 sys_trouble: Page fault while on prds.
44121
44122
44123
44124 Stream: BOS Typewriter Crashes system
44125
44126 Time: While system is running.
44127
44128 Meaning: This indicates a logic error in the supervisor or
44129 CPU or memory hardware problems.
44130
44131 Action: $recov
44132
44133
44134
44135
44136
44137
44138
44139 sys_trouble -761- MR12.5 10/27/92^L
44140
44141
44142 sys_trouble.alm
44143 sys_trouble: Ring 0 derail. MESSAGE
44144
44145
44146
44147 Stream: BOS Typewriter Crashes system
44148
44149 Time: While system is running.
44150
44151 Meaning: A supervisor software module discovered an
44152 untenable situation and " crashed the system by
44153 executing a derail DRL instruction. " If
44154 MESSAGE is also present it will be of the form:
44155 "module: explanation" and further
44156 details can be found in " this documentation in
44157 the description of "module".
44158
44159 Action: $recov
44160
44161
44162
44163 sys_trouble.alm
44164 sys_trouble: Unexpected fault.
44165
44166
44167
44168 Stream: BOS Typewriter Crashes system
44169
44170 Time: System Intialization.
44171
44172 Meaning: This indicates a logic error in the supervisor or
44173 CPU or memory hardware problems.
44174
44175 Action: $recov
44176
44177
44178
44179 sys_trouble.alm
44180 sys_trouble: Unrecognized fault.
44181
44182
44183
44184 Stream: BOS Typewriter Crashes system
44185
44186 Time: While system is running.
44187
44188 Meaning: Unexpected or unrecognized fault subcondition. "
44189 Probable hardware malfunction.
44190
44191 Action: Contact the system programming staff.
44192
44193
44194
44195
44196
44197 sys_trouble -762- MR12.5 10/27/92^L
44198
44199
44200 syserr_log_man_.pl1
44201 Syserr msg #NNNNN: MESSAGE-TEXT
44202 Segment: PATHNAME
44203 Volume: VOLUME-NAME
44204
44205
44206 Stream: as severity0
44207
44208 Time: While system is running.
44209
44210 Meaning: This message is a repetition of a syserr log
44211 message which reported damage to a segment or a
44212 physical volume. There will always be two such
44213 messages in sequence a "Syserr msg. #XXX"
44214 message and either a "Volume:" or "Segment:"
44215 message. The first message is a copy of the
44216 logged syserr message of the given number; the
44217 second message identifies the volume or segment
44218 mentioned. This allows segments damaged by system
44219 action or segments in which the physical volume
44220 salvager observed damage to be identified
44221 unambiguously. These messages are logged in the
44222 Answering Service log at answering service startup
44223 time and every accounting update.
44224
44225 Action: Correlate volume salvager messages with previous
44226 printed volume salvager output to obtain more
44227 information about segment damage detected by the
44228 volume salvager. For those segments which are
44229 mentioned which have not been deleted or are not
44230 in deleted directories the "Segment:" message
44231 says if this is the case contact persons
44232 responsible for the ownership of that segment and
44233 undertake recovery procedures if needed.
44234
44235
44236
44237 syserr_real.pl1
44238 syserr: Bad ring 1 call.
44239
44240
44241 Stream: Logged in SYSERR log.
44242
44243 Time: While system is running.
44244
44245 Meaning: A bad call to syserr was made from ring 1. The
44246 system keeps running.
44247
44248 Action: No operator action is required.
44249
44250
44251
44252
44253
44254
44255 syserr -763- MR12.5 10/27/92^L
44256
44257
44258 syserr_real.pl1
44259 syserr: Mylock error.
44260
44261
44262 Stream: BOS Typewriter Crashes system
44263
44264 Time: While system is running.
44265
44266 Meaning: This indicates a logic error in the supervisor or
44267 CPU or memory hardware problems.
44268
44269 Action: Follow normal recovery procedures.
44270
44271
44272
44273 alm_syserr_caller.pl1
44274 syserr_caller$search_ast_double_uid spurious call
44275 aste=desired uid=UID pv=DRIVEPVID
44276 vtocx=VTOCX.
44277
44278
44279 Stream: Logged in SYSERR log.
44280
44281 Time: While system is running.
44282
44283 Meaning: A call was made to indicate a double unique_id
44284 but it was not possible to reconstruct the error.
44285 The unique id physical volume
44286 location/identifier and vtoce index are provided.
44287
44288 Action: No operator action is required.
44289
44290
44291
44292 alm_syserr_caller.pl1
44293 syserr_caller$search_ast_double_uid spurious call
44294 astep=null uid=UID pv=DRIVEPVID vtocx=VTOCX.
44295
44296
44297 Stream: Logged in SYSERR log.
44298
44299 Time: While system is running.
44300
44301 Meaning: A call was made to indicate a double unique_id
44302 but it was not possible to reconstruct the error.
44303 The unique_id physical volume
44304 location/identifier and VTOCE index are provided.
44305
44306 Action: No operator action is required.
44307
44308
44309
44310
44311
44312
44313 syserr_caller$search_ast_d -764- MR12.5 10/27/92^L
44314
44315
44316 syserr_copy.pl1
44317 syserr_copy: Cannot add message to paged syserr
44318 log PTR. ERROR-MESSAGE
44319
44320
44321 Stream: BOS Typewriter Crashes system
44322
44323 Time: While system is running.
44324
44325 Meaning: This indicates a logic error in the supervisor or
44326 CPU or memory hardware problems. This may
44327 indicate that the syserr log partition has been
44328 damaged. If this is the case the LOG partition
44329 should be reinitialized using the BCE test_disk
44330 command. Some messages will be lost if this
44331 happens.
44332
44333 Action: Re-boot the system. Reinitialize the LOG
44334 partition if necessary.
44335
44336
44337
44338 syserr_copy.pl1
44339 syserr_copy: LOG partition full. Further copying
44340 temporarily disabled.
44341
44342
44343 Stream: BOS Typewriter Crashes system
44344
44345 Time: While system is running.
44346
44347 Meaning: Both halves of the ring zero syserr log buffer are
44348 full. This generally indicates that the Answering
44349 Service is not copying messages from ring zero
44350 into >sc1>syserr_log; there will have been a
44351 previous message left in the Answering Service log
44352 describing why.
44353
44354 Action: If the problem is correctable copying from ring
44355 zero should be restarted see the documentation
44356 for "syserr_log_man_: Automatic log copying
44357 disabled" for instructions; otherwise messages
44358 will be lost.
44359
44360
44361
44362
44363
44364
44365
44366
44367
44368
44369
44370
44371 syserr_copy -765- MR12.5 10/27/92^L
44372
44373
44374 syserr_copy.pl1
44375 syserr_copy: LOG partition mostly full. Severity
44376 5 messages will be lost.
44377
44378
44379 Stream: BOS Typewriter sounds beeper
44380
44381 Time: While system is running.
44382
44383 Meaning: Both halves of the ring zero syserr log buffer are
44384 nearly full. This generally indicates that the
44385 Answering Service is not copying messages from
44386 ring zero into >sc1>syserr_log; there will have
44387 been a previous message left in the Answering
44388 Service log describing why.
44389
44390 Action: If the problem is correctable copying from ring
44391 zero should be restarted see the documentation
44392 for "syserr_log_man_: Automatic log copying
44393 disabled" for instructions; otherwise messages
44394 will be lost.
44395
44396
44397
44398 syserr_copy_wired_log.pl1
44399 syserr_copy_wired_log: Bad lock WWWWWWWWWWWW at
44400 SSS|OOOOOO
44401
44402
44403 Stream: BOS Typewriter Crashes system
44404
44405 Time: While system is running.
44406
44407 Meaning: This indicates a logic error in the supervisor or
44408 CPU or memory hardware problems. The contents of
44409 the lock word and its address are printed as an
44410 aid for debugging.
44411
44412 Action: Follow normal recovery procedures.
44413
44414
44415
44416
44417
44418
44419
44420
44421
44422
44423
44424
44425
44426
44427
44428
44429 syserr_copy_wired_log -766- MR12.5 10/27/92^L
44430
44431
44432 syserr_copy_wired_log.pl1
44433 syserr_copy_wired_log: Fault occurred while
44434 copying into LOG partition. Messages NNNN to NNNN
44435 may be lost.
44436
44437
44438 Stream: BOS Typewriter Crashes system
44439
44440 Time: While system is running.
44441
44442 Meaning: This indicates a logic error in the supervisor or
44443 CPU or memory hardware problems. A fault has
44444 occurred while copying data from the wired syserr
44445 log buffer to the paged syserr log. This usually
44446 results from a disk error on the LOG partition
44447 which would also generate disk error messages.
44448 The sequence numbers of the affected messages are
44449 given because those messages may not appear in the
44450 LOG partition.
44451
44452 Action: Follow normal recovery procedures.
44453
44454
44455
44456 syserr_copy_wired_log.pl1
44457 syserr_copy_wired_log: Too many faults log
44458 copying disabled.
44459
44460
44461 Stream: BOS Typewriter sounds beeper
44462
44463 Time: While system is running.
44464
44465 Meaning: This indicates a logic error in the supervisor or
44466 CPU or memory hardware problems. If too many
44467 errors occur updating the LOG partition log
44468 copying will be disabled which causes all further
44469 messages to be printed on the console but not
44470 entered in the log.
44471
44472 Action: Contact the system programming staff.
44473
44474
44475
44476
44477
44478
44479
44480
44481
44482
44483
44484
44485
44486
44487 syserr_copy_wired_log -767- MR12.5 10/27/92^L
44488
44489
44490 syserr_log_man_.pl1
44491 syserr_log_man_: Attempting to swap syserr log
44492 segments. ERROR MESSAGE
44493
44494
44495 Stream: as severity1
44496
44497 Time: System Intialization.
44498
44499 Meaning: This indicates a logic error in the supervisor or
44500 CPU or memory hardware problems.
44501
44502 Action: Contact the system programming staff.
44503
44504
44505
44506 syserr_log_man_.pl1
44507 syserr_log_man_: Automatic syserr log copying
44508 disabled.
44509
44510
44511 Stream: as severity1
44512
44513 Time: While system is running.
44514
44515 Meaning: Automatic copying of syserr messages into
44516 >sc1>syserr_log has been stopped due to an error
44517 in the copying process. Another message will have
44518 been printed prior to this one describing the
44519 problem. An Answering Service dump usually will
44520 have been created as well.
44521
44522 Action: If the error is recoverable temporary disk error
44523 record quota overflow etc.-- see the previous
44524 messages to make that decision syserr copying
44525 can be restarted by issuing the following command
44526 in admin mode ur using send_admin_command:
44527
44528 syserr_log_man_$restart_copying
44529
44530 If the problem persists delete the first segment
44531 first in the list produced by the list command
44532 in >sc1>syserr_log and restart copying. If the
44533 problem still persists rename or delete
44534 >sc1>syserr_log and reboot; the directory will be
44535 re-created automatically.
44536
44537 The display_log_segment command can be used to
44538 examine individual log segments for damage.
44539
44540
44541
44542
44543
44544
44545 syserr_log_man_ -768- MR12.5 10/27/92^L
44546
44547
44548 syserr_log_man_.pl1
44549 syserr_log_man_: Bad syserr_copy_interval value
44550 NNN seconds using 3600 seconds instead.
44551
44552
44553 Stream: as severity1
44554
44555 Time: System Intialization.
44556
44557 Meaning: The syserr copy interval in installation_parms is
44558 invalid.
44559
44560 Action: Use ed_installation_parms to correct it. A
44561 default will be used until then.
44562
44563
44564
44565 syserr_log_man_.pl1
44566 syserr_log_man_: Called too early.
44567
44568
44569 Stream: as severity2
44570
44571 Time: System Intialization.
44572
44573 Meaning: This indicates a logic error in the supervisor or
44574 CPU or memory hardware problems.
44575
44576 Action: Contact the system programming staff.
44577
44578
44579
44580 syserr_log_man_.pl1
44581 syserr_log_man_: Calling
44582 hphcs_$new_syserr_reuse_log ERROR MESSAGE
44583
44584
44585 Stream: as severity1
44586
44587 Time: System Intialization.
44588
44589 Meaning: This indicates a logic error in the supervisor or
44590 CPU or memory hardware problems.
44591
44592 Action: Contact the system programming staff.
44593
44594
44595
44596
44597
44598
44599
44600
44601
44602
44603 syserr_log_man_ -769- MR12.5 10/27/92^L
44604
44605
44606 syserr_log_man_.pl1
44607 syserr_log_man_: Cannot initiate log
44608 LOG-PATHNAME. ERROR MESSAGE
44609
44610
44611 Stream: as severity1
44612
44613 Time: System Intialization.
44614
44615 Meaning: This indicates a logic error in the supervisor or
44616 CPU or memory hardware problems.
44617
44618 Action: Contact the system programming staff.
44619
44620
44621
44622 syserr_log_man_.pl1
44623 syserr_log_man_: Cannot open history log
44624 LOG-PATHNAME. ERROR MESSAGE
44625
44626
44627 Stream: as severity1
44628
44629 Time: System Intialization.
44630
44631 Meaning: This indicates a logic error in the supervisor or
44632 CPU or memory hardware problems.
44633
44634 Action: Contact the system programming staff.
44635
44636
44637 Message: syserr_log_man_: Cannot migrate message
44638 #NNNNNNN
44639
44640 Stream: as severity1
44641
44642 Time: System Intialization.
44643
44644 Meaning: This indicates a logic error in the supervisor or
44645 CPU or memory hardware problems.
44646
44647 Action: Contact the system programming staff.
44648
44649
44650
44651
44652
44653
44654
44655
44656
44657
44658
44659
44660
44661 syserr_log_man_ -770- MR12.5 10/27/92^L
44662
44663
44664 syserr_log_man_.pl1
44665 syserr_log_man_: Cannot rename PATHNAME to
44666 NEW-NAME. ERROR MESSAGE
44667
44668
44669 Stream: as severity1
44670
44671 Time: System Intialization.
44672
44673 Meaning: This indicates a logic error in the supervisor or
44674 CPU or memory hardware problems.
44675
44676 Action: Contact the system programming staff.
44677
44678
44679
44680 syserr_log_man_.pl1
44681 syserr_log_man_: Cannot replace ACL on
44682 >sc1>syserr_log. ERROR MESSAGE
44683
44684
44685 Stream: as severity1
44686
44687 Time: System Intialization.
44688
44689 Meaning: This indicates a logic error in the supervisor or
44690 CPU or memory hardware problems.
44691
44692 Action: Contact the system programming staff.
44693
44694
44695
44696 syserr_log_man_.pl1
44697 syserr_log_man_: Cannot replace initial ACL on
44698 >sc1>syserr_log. ERROR MESSAGE
44699
44700
44701 Stream: as severity1
44702
44703 Time: System Intialization.
44704
44705 Meaning: This indicates a logic error in the supervisor or
44706 CPU or memory hardware problems.
44707
44708 Action: Contact the system programming staff.
44709
44710
44711
44712
44713
44714
44715
44716
44717
44718
44719 syserr_log_man_ -771- MR12.5 10/27/92^L
44720
44721
44722 syserr_log_man_.pl1
44723 syserr_log_man_: Could not create
44724 >sc1>syserr_log. Automatic syserr log copying not
44725 initialized. ERROR MESSAGE
44726
44727
44728 Stream: as severity1
44729
44730 Time: System Intialization.
44731
44732 Meaning: The syserr history directory was found to be
44733 missing during initialization and a new one could
44734 not be created; this probably indicates file
44735 system damage.
44736
44737 Action: Contact the system programming staff.
44738
44739
44740
44741 syserr_log_man_.pl1
44742 syserr_log_man_: Could not create event channel.
44743 Automatic syserr log copying not initialized.
44744 ERROR MESSAGE
44745
44746
44747 Stream: as severity1
44748
44749 Time: System Intialization.
44750
44751 Meaning: This indicates a logic error in the supervisor or
44752 CPU or memory hardware problems.
44753
44754 Action: Contact the system programming staff.
44755
44756
44757
44758
44759
44760
44761
44762
44763
44764
44765
44766
44767
44768
44769
44770
44771
44772
44773
44774
44775
44776
44777 syserr_log_man_ -772- MR12.5 10/27/92^L
44778
44779
44780 syserr_log_man_.pl1
44781 syserr_log_man_: Could not use old syserr history
44782 dir: >sc1>syserr_log ERROR MESSAGE
44783
44784
44785 Stream: as severity1
44786
44787 Time: System Intialization.
44788
44789 Meaning: The syserr log history directory >sc1>syserr_log
44790 cannot be used; the reason is indicated by the
44791 error message. The system will attempt to rename
44792 it and create a new one; any existing log segments
44793 may be moved from the old directory into the new
44794 current one once the system comes up if the
44795 renaming is successful.
44796
44797 Action: Contact the system programming staff. The
44798 condition causing the error should be corrected
44799 and the system re-booted.
44800
44801
44802
44803 syserr_log_man_.pl1
44804 syserr_log_man_: Created >sc1>syserr_log
44805
44806
44807 Stream: as severity0
44808
44809 Time: System Intialization.
44810
44811 Meaning: The syserr history directory >sc1>syserr_log was
44812 created automatically when it was found missing
44813 during initialization. This is normal during a
44814 cold boot but an error at all other times since
44815 it indicates that the directory was missing.
44816
44817 Action: Contact the system programming staff.
44818
44819
44820
44821
44822
44823
44824
44825
44826
44827
44828
44829
44830
44831
44832
44833
44834
44835 syserr_log_man_ -773- MR12.5 10/27/92^L
44836
44837
44838 syserr_log_man_.pl1
44839 syserr_log_man_: Error obtaining syserr log
44840 history. MESSAGE
44841
44842
44843 Stream: as severity2
44844
44845 Time: System Intialization.
44846
44847 Meaning: To verify syserr message sequence numbers will
44848 continue to increase despite clearing of the log
44849 partition the AS must look at the existing log
44850 segments. However some inconsistancy in the
44851 first history directory prevented this.
44852 >sc1>syserr_log.
44853
44854 Action: Fix any problems and issue the command
44855 "syserr_log_man_$restart_copying" from admin mode
44856 in the initializer process.
44857
44858
44859
44860 syserr_log_man_.pl1
44861 syserr_log_man_: Error verifying log partition
44862 sequence numbers.
44863
44864
44865 Stream: as severity2
44866
44867 Time: System Intialization.
44868
44869 Meaning: This indicates a logic error in the supervisor or
44870 CPU or memory hardware problems. There is some
44871 error in the log partition which prevents
44872 adjustment of the sequence numbers.
44873
44874 Action: Contact the system programming staff.
44875
44876
44877
44878
44879
44880
44881
44882
44883
44884
44885
44886
44887
44888
44889
44890
44891
44892
44893 syserr_log_man_ -774- MR12.5 10/27/92^L
44894
44895
44896 syserr_log_man_.pl1
44897 syserr_log_man_: Renamed >sc1>syserr_log to
44898 NEW-NAME
44899
44900
44901 Stream: as severity1
44902
44903 Time: System Intialization.
44904
44905 Meaning: Indicates that the history directory has been
44906 renamed after an error in attempting to use it.
44907 Old log segments can be moved from here back into
44908 >sc1>syserr_log.
44909
44910 Action: Contact the system programming staff.
44911
44912
44913
44914 syserr_log_man_.pl1
44915 syserr_log_man_: Syserr thresholds: NNN pages
44916 COMMENT NNN seconds COMMENT
44917
44918
44919 Stream: as severity0
44920
44921 Time: System Intialization.
44922
44923 Meaning: These are the thresholds for when Answering
44924 Service syserr copying will be performed. Each
44925 value may be followed by a comment; the comment
44926 "default" indicates that the installation_parms
44927 value was zero indicating that a default value is
44928 used. The comment "disabled" indicates that the
44929 installation_parms value was set to disable this
44930 log copying mechanism. The comment
44931 "installation_parms value invalid" means just
44932 that; the value in installation_parms must be
44933 updated and meantime a default is applied.
44934
44935 Action: Note for system programmer action.
44936
44937
44938
44939
44940
44941
44942
44943
44944
44945
44946
44947
44948
44949
44950
44951 syserr_log_man_ -775- MR12.5 10/27/92^L
44952
44953
44954 syserr_log_man_.pl1
44955 syserr_log_man_: Unable to open syserr log in
44956 PATH.
44957
44958
44959 Stream: as severity2
44960
44961 Time: System Intialization.
44962
44963 Meaning: To verify syserr message sequence numbers will
44964 continue to increase despite clearing of the log
44965 partition the AS must look at the existing log
44966 segments. However some inconsistancy in the
44967 first history directory prevented this.
44968 >sc1>syserr_log.
44969
44970 Action: Contact the system programming staff. Fix any
44971 problems in the syserr log history dir and issue
44972 the command "syserr_log_man_$restart_copying" from
44973 admin mode in the initializer process.
44974
44975
44976
44977 syserr_seg_manager.pl1
44978 syserr_seg_manager: Attempt to rename invalid log
44979 index NNNN
44980
44981
44982 Stream: BOS Typewriter Crashes system
44983
44984 Time: While system is running.
44985
44986 Meaning: This indicates a logic error in the supervisor or
44987 CPU or memory hardware problems.
44988
44989 Action: Follow normal recovery procedures. Reinitialize
44990 the LOG partition with the BCE test_disk command
44991 if this persists
44992
44993
44994
44995
44996
44997
44998
44999
45000
45001
45002
45003
45004
45005
45006
45007
45008
45009 syserr_seg_manager -776- MR12.5 10/27/92^L
45010
45011
45012 syserr_seg_manager.pl1
45013 syserr_seg_manager: Attempt to rename log #NNNN
45014 already named NAME
45015
45016
45017 Stream: BOS Typewriter.
45018
45019 Time: While system is running.
45020
45021 Meaning: This indicates a logic error in the supervisor or
45022 CPU or memory hardware problems.
45023
45024 Action: Note for system programmer action.
45025
45026
45027
45028 syserr_seg_manager.pl1
45029 syserr_seg_manager: Cannot rename syserr log
45030 #NNNN from OLD-NAME to NEW-NAME for USER-NAME
45031
45032
45033 Stream: BOS Typewriter.
45034
45035 Time: While system is running.
45036
45037 Meaning: This indicates a logic error in the supervisor or
45038 CPU or memory hardware problems.
45039
45040 Action: Note for system programmer action.
45041
45042
45043
45044 syserr_seg_manager.pl1
45045 syserr_seg_manager: Crawlout with syserr log
45046 locked. Automatic syserr log copying disabled.
45047
45048
45049 Stream: BOS Typewriter sounds beeper
45050
45051 Time: While system is running.
45052
45053 Meaning: An fault has occurred in the Answering Service
45054 while copying syserr messages from ring zero and
45055 copying from ring zero has been disabled. This
45056 probably indicates a supervisor logic error. This
45057 will be followed by a message from verify_lock
45058 identifying the fault.
45059
45060 Action: Attempt to restart copying or re-boot the system.
45061
45062
45063
45064
45065
45066
45067 syserr_seg_manager -777- MR12.5 10/27/92^L
45068
45069
45070 syserr_seg_manager.pl1
45071 syserr_seg_manager: No messages in live syserr
45072 log PTR.
45073
45074
45075 Stream: BOS Typewriter Crashes system
45076
45077 Time: System Intialization.
45078
45079 Meaning: This indicates a logic error in the supervisor or
45080 CPU or memory hardware problems. When attempting
45081 to verify the message sequence numbers in the live
45082 syserr log it was found that no messages were
45083 present. This should not hapen at this point
45084 because syserr log initialization
45085 init_syserr_log always places a message in the
45086 log.
45087
45088 Action: Contact the system programming staff.
45089
45090
45091 Messaage: syserr_seg_manager: Log message
45092 sequence numbers adjusted in PTR beginning at
45093 SEQUENCE.
45094
45095 Stream: BOS Typewriter.
45096
45097 Time: System Intialization.
45098
45099 Meaning: The sequence numbers in the log partition were
45100 found to preceed the sequence numbers found in the
45101 log history. Thus the numbers in the partition
45102 and the wired log were adjusted appropriately.
45103 This message indicates the new sequence number
45104 where the adjustment started for each of the two
45105 ring 0 paged logs. This will occur after the log
45106 partition has been damaged or manually cleared.
45107
45108 Action: Contact the system programming staff.
45109
45110
45111
45112
45113
45114
45115
45116
45117
45118
45119
45120
45121
45122
45123
45124
45125 syserr_seg_manager -778- MR12.5 10/27/92^L
45126
45127
45128 wired_shutdown.pl1
45129 system already shut down
45130
45131
45132 Stream: BOS Typewriter.
45133
45134 Time: Emergency shutdown
45135
45136 Meaning: An attempt to perform emergency shutdown was made
45137 after a previous attempt or normal shutdown
45138 succeeded. No ESD is necessary in this case. The
45139 "shutdown complete" message follows.
45140
45141 Action: No operator action is required.
45142
45143
45144
45145 system_control_.pl1
45146 system_control_: fault during init
45147
45148
45149 Stream: ring 4 system control.
45150
45151 Time: System Intialization.
45152
45153 Meaning: Some error condition has occurred unexpectedly
45154 while starting up the ring 4 initializer
45155 environment. The system will return to bce.
45156
45157 Action: Contact the system programming staff. Follow
45158 normal recovery procedures.
45159
45160
45161
45162
45163
45164 system_startup_.pl1
45165 system_startup_ Renamed >XXXXX to >XXXXX.!BBB.....
45166
45167
45168 Stream: BOS Typewriter.
45169
45170 Time: System Intialization.
45171
45172 Meaning: The segment >disk_table or the directory >lv as
45173 specified by XXXXX in the message was renamed in
45174 response to the "nodt" or "nolv" option on the bce
45175 "boot" command line.
45176
45177 Action: No operator action is required.
45178
45179
45180
45181
45182
45183 system_startup_ Renamed >X -779- MR12.5 10/27/92^L
45184
45185
45186 system_startup_.pl1
45187 system_startup_: error on initializer io streams
45188
45189
45190 Stream: BOS Typewriter Crashes system
45191
45192 Time: System Intialization.
45193
45194 Meaning: This error crashes the system. The system will
45195 return to bce.
45196
45197 Action: Follow normal recovery procedures. Try another
45198 boot tape and check that the hardware is running
45199 correctly.
45200
45201
45202
45203 system_startup_.pl1
45204 system_startup_: Recursive error condition.
45205
45206
45207 Stream: BOS Typewriter Crashes system
45208
45209 Time: System Intialization.
45210
45211 Meaning: This error crashes the system. The system will
45212 return to bce.
45213
45214 Action: Follow normal recovery procedures. Boot another
45215 system and examine the dump.
45216
45217
45218
45219 system_startup_.pl1
45220 system_startup_: The config deck is empty.
45221
45222
45223 Stream: BOS Typewriter Crashes system
45224
45225 Time: System Intialization.
45226
45227 Meaning: This error crashes the system. The system will
45228 return to bce. This error should not occur
45229 because earlier steps in initialization depend
45230 upon the config deck. If it does however type
45231 GO after putting a config deck in place.
45232
45233
45234 Action: Follow normal recovery procedures. Use another
45235 boot tape or check that the hardware is operating
45236 correctly.
45237
45238
45239
45240
45241 system_startup_ -780- MR12.5 10/27/92^L
45242
45243
45244 system_startup_.pl1
45245 system_startup_: The config_deck segment is
45246 missing.
45247
45248
45249 Stream: BOS Typewriter Crashes system
45250
45251 Time: System Intialization.
45252
45253 Meaning: This error crashes the system. The segment
45254 config_deck is missing. This error should not
45255 occur because earlier steps in initialization
45256 depend upon the config deck.
45257
45258 Action: Follow normal recovery procedures. Use another
45259 boot tape or check that the hardware is operating
45260 correctly.
45261
45262
45263
45264 system_startup_.pl1
45265 system_startup_: The root logical volume is not
45266 complete. "boot rlvs" level 2 directory salvage
45267 aborted.
45268
45269
45270 Stream: BOS Typewriter.
45271
45272 Time: System Intialization.
45273
45274 Meaning: One or more physical volumes of the Root Logical
45275 Volume RLV registered in the volume registration
45276 database are not specified on the root config
45277 card and are therefore not mounted. Level 2
45278 directory salvage cannot take place with an
45279 incomplete RLV.
45280
45281 Action: Mount the missing packs with the add_vol command
45282 and then use the salvage_dirs command.
45283
45284
45285
45286
45287
45288
45289
45290
45291
45292
45293
45294
45295
45296
45297
45298
45299 system_startup_ -781- MR12.5 10/27/92^L
45300
45301
45302 system_startup_.pl1
45303 system_startup_: unclaimed COND
45304 machine conditions in octal
45305
45306
45307 Stream: BOS Typewriter sounds beeper
45308
45309 Time: System Intialization.
45310
45311 Meaning: Some error condition has occurred unexpectedly
45312 inside the ring 1 environment. Diagnostic
45313 information is typed after this line. The system
45314 should return to Initializer command level still
45315 in ring 1 and be able to continue running.
45316
45317 Action: Contact the system programming staff.
45318
45319
45320
45321 system_startup_.pl1
45322 system_startup_: unclaimed condition-name
45323 condition.
45324
45325
45326 Stream: BOS Typewriter sounds beeper
45327
45328 Time: System Intialization.
45329
45330 Meaning: An error has occurred while executing in the ring
45331 1 Initializer environment. The system returns to
45332 ring 1 command level. For some errors machine
45333 conditions are displayed in subsequent messages.
45334
45335 Action: Contact the system programming staff.
45336
45337
45338
45339 system_startup_.pl1
45340 system_startup_: Will not reload
45341
45342
45343 Stream: BOS Typewriter.
45344
45345 Time: Response to operator reload command.
45346
45347 Meaning: One or more volumes cannot be mounted. Reloading
45348 cannot proceed. The system returns to ring 1
45349 command level.
45350
45351 Action: Correct the problem and try again.
45352
45353
45354
45355
45356
45357 system_startup_ -782- MR12.5 10/27/92^L
45358
45359
45360 system_startup_.pl1
45361 system_startup_: XYZ is not a legal command.
45362 Type help for a list of commands.
45363
45364
45365 Stream: BOS Typewriter.
45366
45367 Time: System Intialization.
45368
45369 Meaning: The operator has issued a command to the ring 1
45370 environment that cannot be executed. No action
45371 was taken on the illegal command.
45372
45373 Action: If the command is misspelled retype it correctly.
45374 If the command is intended for the ring 4
45375 Answering Service type "standard" first to leave
45376 the ring 1 environment and then retype the desired
45377 command.
45378
45379
45380
45381 tape_reader.pl1
45382 tape_reader: bad_major_status: SSS
45383
45384
45385 Stream: BOS Typewriter Crashes system
45386
45387 Time: System Intialization.
45388
45389 Meaning: The bootload tape is unreadable.
45390
45391 Action: The Multics System Tape may be incorrect. If the
45392 problem persists try another MST. Try another
45393 tape drive.
45394
45395
45396
45397 tape_reader.pl1
45398 tape_reader: unable to read system tape
45399
45400
45401 Stream: BOS Typewriter Crashes system
45402
45403 Time: System Intialization.
45404
45405 Meaning: The bootload tape is unreadable.
45406
45407 Action: The Multics System Tape may be incorrect. If the
45408 problem persists try another MST.
45409
45410
45411
45412
45413
45414
45415 tape_reader -783- MR12.5 10/27/92^L
45416
45417
45418 tc_init.pl1
45419 tc_init: cannot create cpu_X.prds. This CPU may
45420 not be added. ERROR_MESSAGE
45421
45422
45423 Stream: BOS Typewriter.
45424
45425 Time: System Intialization.
45426
45427 Meaning: A difficulty was encountered in creating the PRDS
45428 for a configurable CPU. Later attempts to add
45429 this CPU will fail. It will be marked as "off" in
45430 the CONFIG deck.
45431
45432 Action: Contact the system programming staff. When the
45433 problem has been remedied shut down and reboot
45434 and then add this CPU.
45435
45436
45437
45438 tc_init.pl1
45439 tc_init: Cannot start up first idle process.
45440 Check switches.
45441
45442
45443 Stream: BOS Typewriter Crashes system
45444
45445 Time: System Intialization.
45446
45447 Meaning: The idle process for the bootload CPU could not be
45448 started. This may be an error in setting of
45449 configuration switches or may be indicative of a
45450 logic problem in the supervisor.
45451
45452 Action: Perform an emergency shutdown. Check all main
45453 module configuration switches. If a problem was
45454 corrected reboot. Otherwise be sure to get a
45455 dump and contact the systems programming staff.
45456
45457
45458
45459
45460
45461
45462
45463
45464
45465
45466
45467
45468
45469
45470
45471
45472
45473 tc_init -784- MR12.5 10/27/92^L
45474
45475
45476 tc_init.pl1
45477 tc_init: Could not delete old PRDSNAME.
45478 ERRORMESSAGE
45479
45480
45481 Stream: BOS Typewriter.
45482
45483 Time: System Intialization.
45484
45485 Meaning: The old PRDS PRDSNAME from the previous bootload
45486 in >system_library_1 could not be deleted. When
45487 the CPU whose tag is part of PRDSNAME is added
45488 the old PRDS will be used. ERRORMESSAGE is a
45489 standard error_table_ message.
45490
45491 Action: Contact the system programming staff.
45492
45493
45494
45495 tc_init.pl1
45496 tc_init: Could not rename prds to PRDSNAME.
45497 ERRORMESSAGE
45498
45499
45500 Stream: BOS Typewriter.
45501
45502 Time: System Intialization.
45503
45504 Meaning: The segment "prds" in >system_library_1 could not
45505 be renamed to PRDSNAME which is the correct name
45506 for the PRDS for the bootload processor.
45507 ERRORMESSAGE is a standard error_table_ message.
45508
45509 Action: Notify the system programming staff. Action
45510 should be taken by the programming staff to rename
45511 this segment. If the problem cannot be sorted
45512 out avoid reconfiguring the bootload CPU during
45513 this bootload.
45514
45515
45516
45517
45518
45519
45520
45521
45522
45523
45524
45525
45526
45527
45528
45529
45530
45531 tc_init -785- MR12.5 10/27/92^L
45532
45533
45534 tc_init.pl1
45535 tc_init: Could not start CPU CPUTAG.
45536
45537
45538 Stream: BOS Typewriter.
45539
45540 Time: System Intialization.
45541
45542 Meaning: The CPU whose tag is CPUTAG could not be
45543 automatically started by system bootload.
45544
45545 Action: Check all configuration switches on CPU and main
45546 memory modules especially the CPU STEP switch on
45547 the CPU which could not be added and its port
45548 enable switches. If all switches were correct
45549 add the CPU via the addcpu command.
45550
45551
45552
45553 tc_init.pl1
45554 tc_init: Inconsistent SCHD config card values.
45555
45556
45557 Stream: BOS Typewriter Crashes system
45558
45559 Time: System Intialization.
45560
45561 Meaning: The SCHD config card is not in the correct format
45562 or some values are out of acceptable range. In
45563 particular the value of min_eligible cannot
45564 exceed that of max_eligible; also the value of
45565 max_eligible plus the max number of stopped
45566 stack_0's default = 4 cannot exceed
45567 max_max_eligible.
45568
45569 Action: Check the SCHD config card refer to the MOH and
45570 correct. Re-boot the system.
45571
45572
45573
45574
45575
45576
45577
45578
45579
45580
45581
45582
45583
45584
45585
45586
45587
45588
45589 tc_init -786- MR12.5 10/27/92^L
45590
45591
45592 tc_init.pl1
45593 tc_init: No valid processor tags on CPU cards.
45594
45595
45596 Stream: BOS Typewriter Crashes system
45597
45598 Time: System Intialization.
45599
45600 Meaning: No CPU CONFIG cards contained valid A - H CPU
45601 tags. Normally this message will not appear if
45602 the bootload CPU is mis-specified as this error
45603 will be detected by scas_init and thus this may
45604 be indicative of a supervisor logic problem.
45605
45606 Action: Check that all CPU CONFIG cards are correct. If
45607 not perform an emergency shutdown correct them
45608 and reboot. If so be sure to get a dump and
45609 contact system programming personnel.
45610
45611
45612
45613 tc_init.pl1
45614 tc_init: Size of PRDS on TBLS card too small; XXX
45615 KW will be used.
45616
45617
45618 Stream: BOS Typewriter.
45619
45620 Time: System Intialization.
45621
45622 Meaning: The size of the PRDS specified on the TBLS card in
45623 the Configuration Deck is smaller than the size of
45624 the PRDS defined in the MST header. The size of
45625 the PRDS will be that defined in the MST header.
45626 Further the TBLS card in the Configuration Deck
45627 has been changed to reflect the minimum size of
45628 the PRDS
45629
45630
45631
45632
45633
45634
45635
45636
45637
45638
45639
45640
45641
45642
45643
45644
45645
45646
45647 tc_init -787- MR12.5 10/27/92^L
45648
45649
45650 verify_lock.pl1
45651 Terminating user process NAME: Fatal salvaging of
45652 process directory.
45653
45654
45655 Stream: BOS Typewriter Terminates user process
45656
45657 Time: While system is running.
45658
45659 Meaning: A process is attempting to crawl out. The system
45660 discovered that the process was interrupted while
45661 its process directory was locked and has salvaged
45662 the process directory. Salvaging the process
45663 directory may delete critical process segments and
45664 cause the process to terminate so the process is
45665 terminated cleanly instead.
45666
45667 Action: No operator action is required.
45668
45669 Message: verify_lock: COND condition by USER
45670 while salvaging directory.
45671
45672 Stream: $announce
45673
45674 Time: During salvaging.
45675
45676 Meaning: A fault occurred while salvaging a directory found
45677 locked at crawlout. This indicates a serious
45678 problem with the directory.
45679
45680 Action: Contact the system programming staff.
45681
45682
45683
45684 truncate_vtoce.pl1
45685 truncate_vtoce: attempt to destroy hc_sdw seg
45686 astep PPP
45687
45688
45689 Stream: BOS Typewriter Crashes system
45690
45691 Time: While system is running.
45692
45693 Meaning: An attempt has been made to truncate a supervisor
45694 segment. The AST entry is located at PPP. This
45695 indicates a logic error in the supervisor or CPU
45696 or memory hardware problems.
45697
45698 Action: Follow normal recovery procedures.
45699
45700
45701
45702
45703
45704
45705 truncate_vtoce -788- MR12.5 10/27/92^L
45706
45707
45708 tty_index.pl1
45709 tty_index: USER ACCESS_CLASS attempted invalid
45710 attachment of CHANNEL ACCESS_CLASS
45711
45712
45713 Stream: BOS Typewriter.
45714
45715 Time: While system is running.
45716
45717 Meaning: A process of USER with authorization
45718 ACCESS_CLASS attempted to use a communications
45719 channel which does not correspond to the user's
45720 authorization and the user does not have the
45721 communications privilege enabled. The request was
45722 refused. This may indicate a system error.
45723
45724 Action: Contact the system security administrator.
45725
45726
45727
45728 tty_interrupt.pl1
45729 tty_interrupt: unrecognized interrupt type N
45730 for devx D
45731
45732
45733 Stream: BOS Typewriter Crashes system
45734
45735 Time: While system is running.
45736
45737 Meaning: An unrecognized interrupt type has been reported
45738 for the nonmultiplexed channel whose device index
45739 is D.
45740
45741 Action: Contact the system programming staff.
45742
45743
45744
45745 tty_lock.pl1
45746 tty_lock$verify: attempted crawlout with queue
45747 lock set.
45748
45749
45750 Stream: BOS Typewriter Crashes system
45751
45752 Time: While system is running.
45753
45754 Meaning: There was an attempt to crawl out while the tty
45755 queue lock was locked.
45756
45757 Action: Contact the system programming staff.
45758
45759
45760
45761
45762
45763 tty_lock$verify -789- MR12.5 10/27/92^L
45764
45765
45766 tty_lock.pl1
45767 tty_lock$verify: attempted crawlout with special
45768 channel lock set.
45769
45770
45771 Stream: BOS Typewriter Crashes system
45772
45773 Time: While system is running.
45774
45775 Meaning: There was an attempt to crawl out while a channel
45776 lock that is also a processor lock was locked.
45777
45778 Action: Contact the system programming staff.
45779
45780
45781
45782 tty_lock.pl1
45783 tty_lock$verify: attempted crawlout with tty_buf
45784 lock set.
45785
45786
45787 Stream: BOS Typewriter Crashes system
45788
45789 Time: While system is running.
45790
45791 Meaning: There was an attempt to crawl out while the
45792 tty_buf lock used by tty_space_man was locked.
45793
45794 Action: Contact the system programming staff.
45795
45796
45797
45798 tty_lock.pl1
45799 tty_lock: attempt to lock channel already locked
45800 by same process.
45801
45802
45803 Stream: BOS Typewriter Crashes system
45804
45805 Time: While system is running.
45806
45807 Meaning: A locking error was detected when a process tried
45808 to lock a channel that it had already locked.
45809
45810 Action: Contact the system programming staff.
45811
45812
45813
45814
45815
45816
45817
45818
45819
45820
45821 tty_lock -790- MR12.5 10/27/92^L
45822
45823
45824 tty_lock.pl1
45825 tty_lock: attempt to lock unused channel for
45826 interrupt.
45827
45828
45829 Stream: BOS Typewriter Crashes system
45830
45831 Time: While system is running.
45832
45833 Meaning: A locking error was detected when an interrupt
45834 handler tried to lock an ununsed channel.
45835
45836 Action: Contact the system programming staff.
45837
45838
45839
45840 tty_lock.pl1
45841 tty_lock: attempt to unlock channel not locked by
45842 same process.
45843
45844
45845 Stream: BOS Typewriter Crashes system
45846
45847 Time: While system is running.
45848
45849 Meaning: A locking error was detected when a process tried
45850 to unlock a channel that was either not locked or
45851 locked by another process.
45852
45853 Action: Contact the system programming staff.
45854
45855
45856
45857 tty_lock.pl1
45858 tty_lock: attempt to unlock queue not locked by
45859 same process.
45860
45861
45862 Stream: BOS Typewriter Crashes system
45863
45864 Time: While system is running.
45865
45866 Meaning: A locking error was detected when a process tried
45867 to unlock the global queue lock which was either
45868 not locked or was locked by another process.
45869
45870
45871
45872
45873
45874
45875
45876
45877
45878
45879 tty_lock -791- MR12.5 10/27/92^L
45880
45881
45882 tty_lock.pl1
45883 tty_lock: Cannot get space for queue entry.
45884 devx = N
45885
45886
45887 Stream: BOS Typewriter sounds beeper
45888
45889 Time: While system is running.
45890
45891 Meaning: An attempt to queue an interrupt for the channel
45892 with devx N failed due to lack of space. The
45893 interrupt was lost which may cause loss of data or
45894 improper channel operation.
45895
45896 Action: Contact the system programming staff.
45897
45898
45899
45900 tty_space_man.pl1
45901 tty_space_man: Address not in buffer pool.
45902
45903
45904 Stream: BOS Typewriter Crashes system
45905
45906 Time: While system is running.
45907
45908 Meaning: An attempt was made to free space at an address
45909 not included in the free space pool of tty_buf.
45910
45911 Action: Contact the system programming staff.
45912
45913
45914
45915 tty_space_man.pl1
45916 tty_space_man: Lock already locked to process.
45917
45918
45919 Stream: BOS Typewriter Crashes system
45920
45921 Time: While system is running.
45922
45923 Meaning: A process that had the global tty_buf lock locked
45924 attempted to lock it again.
45925
45926 Action: Contact the system programming staff.
45927
45928
45929
45930
45931
45932
45933
45934
45935
45936
45937 tty_space_man -792- MR12.5 10/27/92^L
45938
45939
45940 tty_space_man.pl1
45941 tty_space_man: Lock not locked to process.
45942
45943
45944 Stream: BOS Typewriter Crashes system
45945
45946 Time: While system is running.
45947
45948 Meaning: A process attempted to unlock the global tty_buf
45949 lock when that process did not have it locked.
45950
45951 Action: Contact the system programming staff.
45952
45953
45954
45955 tty_space_man.pl1
45956 tty_space_man: Tried to free space already free.
45957
45958
45959 Stream: BOS Typewriter Crashes system
45960
45961 Time: While system is running.
45962
45963 Meaning: An attempt was made to free space in tty_buf that
45964 was included in or overlapped space that was
45965 already free.
45966
45967 Action: Contact the system programming staff.
45968
45969
45970
45971 tty_tables_mgr.pl1
45972 tty_tables_mgr$add: Invalid table type. N
45973
45974
45975 Stream: BOS Typewriter Crashes system
45976
45977 Time: While system is running.
45978
45979 Meaning: An attempt to add a table to the tty_tables
45980 segment has failed due to an invalid table type of
45981 N.
45982
45983 Action: Contact the system programming staff.
45984
45985
45986
45987
45988
45989
45990
45991
45992
45993
45994
45995 tty_tables_mgr$add -793- MR12.5 10/27/92^L
45996
45997
45998 tty_tables_mgr.pl1
45999 tty_tables_mgr$delete: Invalid table offset. N
46000
46001
46002 Stream: BOS Typewriter Crashes system
46003
46004 Time: While system is running.
46005
46006 Meaning: An attempt to delete a table from the tty_tables
46007 segment has failed due to an invalid table offset
46008 of N.
46009
46010 Action: Contact the system programming staff.
46011
46012
46013
46014 turn_on_mc_.pl1
46015 turn_on_mc_: MESSAGE. attach STREAM
46016
46017
46018 Stream: sc error_output.
46019
46020 Time: System Intialization.
46021
46022 Meaning: The system attempted to start the Message
46023 Coordinator but the stream STREAM cannot be
46024 attached to the message routing dim. The system
46025 continues to operate but the Message Coordinator
46026 is not used. Probably the daemon processes will
46027 also encounter trouble.
46028
46029 Action: Contact the system programming staff.
46030
46031
46032
46033 turn_on_mc_.pl1
46034 turn_on_mc_: MESSAGE. detach STREAM
46035
46036
46037 Stream: sc error_output.
46038
46039 Time: System Intialization.
46040
46041 Meaning: The system attempted to start the Message
46042 Coordinator but the stream STREAM could not be
46043 detached from its initial dim. The system
46044 continues to operate but the Message Coordinator
46045 is not used. Probably the daemon processes will
46046 also encounter trouble.
46047
46048 Action: Contact the system programming staff.
46049
46050
46051
46052
46053 turn_on_mc_ -794- MR12.5 10/27/92^L
46054
46055
46056 turn_on_mc_.pl1
46057 turn_on_mc_: MESSAGE. error from mc_init
46058
46059
46060 Stream: sc error_output.
46061
46062 Time: System Intialization.
46063
46064 Meaning: The system attempted to start the Message
46065 Coordinator but it cannot be initialized. The
46066 system continues to operate but the Message
46067 Coordinator is not used. The daemon processes
46068 will probably also encounter trouble.
46069
46070 Action: Contact the system programming staff.
46071
46072
46073
46074 turn_on_mc_.pl1
46075 turn_on_mc_: MESSAGE. open STREAM
46076
46077
46078 Stream: sc error_output.
46079
46080 Time: System Intialization.
46081
46082 Meaning: The system attempted to start the Message
46083 Coordinator but the stream STREAM cannot be opened
46084 by the message routing dim. The system continues
46085 to operate but the Message Coordinator is not
46086 used. Probably the daemon processes will also
46087 encounter trouble.
46088
46089 Action: Contact the system programming staff.
46090
46091
46092
46093 mc_commands_.pl1
46094 Unable to locate a CDT entry for XXXX while
46095 attempting to drop it.
46096
46097
46098 Stream: as severity 1
46099
46100 Time: In response to a drop operator command.
46101
46102 Meaning: Notification that the CDT entry cannot be found to
46103 free it as a result of dropping the tty channel
46104 from the message coordinator. The mc_anstbl entry
46105 is freed at this point however.
46106
46107 Action: No operator action is required.
46108
46109
46110
46111 Unable to locate a CDT ent -795- MR12.5 10/27/92^L
46112
46113
46114 obs_reconfigure.pl1
46115 unlock: Reconfiguration data locked by
46116 PERSON.PROJ.T
46117
46118
46119 Stream: Initializer process output.
46120
46121 Time: In response to an operator command.
46122
46123 Meaning: This message is typed by reconfigure$force_unlock
46124 if the reconfiguration data base was locked.
46125
46126 Action: No operator action is required.
46127
46128
46129
46130 obs_reconfigure.pl1
46131 unlock: Reconfiguration data not locked.
46132
46133
46134 Stream: Initializer process output.
46135
46136 Time: In response to an operator command.
46137
46138 Meaning: This message is typed by reconfigure$force_unlock
46139 if the reconfiguration data base was not locked.
46140
46141 Action: No operator action is required.
46142
46143
46144
46145 dn355_boot_interrupt.pl1
46146 Unrecognized bootload status N for FNP X
46147
46148
46149 Stream: BOS Typewriter.
46150
46151 Time: When bootloading an FNP
46152
46153 Meaning: The status reported by an FNP in response to a
46154 bootload attempt was not one of the ones
46155 recognized. N is the reported status in octal.
46156
46157 Action: Contact the system programming staff.
46158
46159
46160
46161
46162
46163
46164
46165
46166
46167
46168
46169 Unrecognized bootload stat -796- MR12.5 10/27/92^L
46170
46171
46172 up_mgt_.pl1
46173 up_mgt_: ERROR_MESSAGE During work class
46174 reassignment
46175
46176
46177 Stream: as severity2
46178
46179 Time: While system is running.
46180
46181 Meaning: The error described by ERROR_MESSAGE occurred
46182 while a system administrator was attempting to
46183 install a new mgt. The operation was tried twice
46184 and failed both times. More detailed reasons for
46185 the failure are given in messages immediately
46186 preceding this one. The new mgt has been
46187 installed. Hardcore is operating with a set of
46188 parameters inconsistent with the new mgt.
46189
46190 Action: Contact the system administrator.
46191
46192
46193
46194 up_pdt_.pl1
46195 up_pdt_: bumping NAME.PROJ omitted from new pdt
46196
46197
46198 Stream: as severity1
46199
46200 Time: While system is running.
46201
46202 Meaning: The supervisor of project PROJ has removed the
46203 user named NAME from the project while he was
46204 logged in. He is no longer authorized to be
46205 logged in on that project and is bumped.
46206
46207 Action: No operator action is required.
46208
46209
46210
46211
46212
46213
46214
46215
46216
46217
46218
46219
46220
46221
46222
46223
46224
46225
46226
46227 up_pdt_ -797- MR12.5 10/27/92^L
46228
46229
46230 up_pdt_.pl1
46231 up_pdt_: bumping NAME.PROJ user authorization
46232 now outside range.
46233
46234
46235 Stream: as severity1
46236
46237 Time: While system is running.
46238
46239 Meaning: A project administrator has installed a new pdt
46240 that changes the authorization range for the user
46241 identified by NAME on project PROJ. The user
46242 NAME.PROJ is currently logged in with an
46243 authorization outside the new range. Therefore
46244 the user is being bumped from the system.
46245
46246 Action: No operator action is required.
46247
46248
46249
46250 up_pdt_.pl1
46251 up_pdt_: ERROR_MESSAGE. PROJ.pdt will be
46252 installed with no hash table
46253
46254
46255 Stream: as severity2
46256
46257 Time: While system is running.
46258
46259 Meaning: A new PDT is being installed for project PROJ. An
46260 error described by ERROR_MESSAGE occurred while
46261 its hash table was being built. The PDT will be
46262 installed without a hash table. Logins on that
46263 project will take longer and place an extra load
46264 on the system.
46265
46266 Action: Contact the system programming staff.
46267
46268
46269
46270
46271
46272
46273
46274
46275
46276
46277
46278
46279
46280
46281
46282
46283
46284
46285 up_pdt_ -798- MR12.5 10/27/92^L
46286
46287
46288 up_pdt_.pl1
46289 up_pdt_: PROJ.pdt has N users leaving
46290 insufficient room for a hash table.
46291
46292
46293 Stream: as severity1
46294
46295 Time: While system is running.
46296
46297 Meaning: A new project definition table PDT for project
46298 PROJ is being installed. It has so many users
46299 that there is no room in it for a hash table. The
46300 PDT will be installed without a hash table.
46301 Logins on that project will take longer and place
46302 an extra load on the system.
46303
46304 Action: Contact the system programming staff.
46305
46306
46307
46308 up_pdt_.pl1
46309 up_pdt_: PROJ.pdt NAME on free list state nonzero
46310
46311
46312 Stream: as severity2
46313
46314 Time: While system is running.
46315
46316 Meaning: A new project definition table for PROJ is being
46317 installed. The thread of free entries appears to
46318 include some user whose state is not zero. The
46319 program abandons the free chain and continues.
46320
46321 Action: Contact the system administrator.
46322
46323
46324
46325 up_pdt_.pl1
46326 up_pdt_: synch error NAME.PROJ
46327
46328
46329 Stream: as severity2
46330
46331 Time: While system is running.
46332
46333 Meaning: A new project definition table for PROJ is being
46334 installed. The answer table entry for NAME.PROJ
46335 should contain a pointer to the user's PDT entry
46336 but the pointer is incorrect. Accounting figures
46337 may be scrambled. The system continues operation.
46338
46339 Action: Contact the system administrator.
46340
46341
46342
46343 up_pdt_ -799- MR12.5 10/27/92^L
46344
46345
46346 up_rtdt_.pl1
46347 up_rtdt_: Adding resource type RESOURCE_TYPE to
46348 the system.
46349
46350
46351 Stream: as severity1
46352
46353 Time: While system is running.
46354
46355 Meaning: The named resource type has been newly defined and
46356 will be accessible by system users. This is an
46357 advisory message.
46358
46359 Action: None.
46360
46361
46362
46363 up_rtdt_.pl1
46364 up_rtdt_: Deleting resource type RESOURCE_TYPE
46365 from the system.
46366
46367
46368 Stream: as severity1
46369
46370 Time: While system is running.
46371
46372 Meaning: The named resource type is no longer accessible by
46373 system users. This is an advisory message.
46374
46375 Action: None.
46376
46377
46378
46379 up_rtdt_.pl1
46380 up_rtdt_: ERROR_MESSAGE Cannot create RCP
46381 registry for RESOURCE_NAME.
46382
46383
46384 Stream: as severity2
46385
46386 Time: While system is running.
46387
46388 Meaning: The error described by ERROR_MESSAGE occurred
46389 while a system administrator was attempting to
46390 install a new rtdt. The rtdt contained a new
46391 resource type but the resource management
46392 registry for that resource type could not be
46393 created. The rtdt is not installed. Some other
46394 registries may already have been modified
46395 according to information in the new rtdt.
46396
46397 Action: Notify the system administrator.
46398
46399
46400
46401 up_rtdt_ -800- MR12.5 10/27/92^L
46402
46403
46404 up_rtdt_.pl1
46405 up_rtdt_: ERROR_MESSAGE Cannot recover by
46406 renaming old RTDT either.
46407
46408
46409 Stream: as severity2
46410
46411 Time: While system is running.
46412
46413 Meaning: The program that installs rtdt's cannot recover
46414 correctly from an earlier error in renaming for
46415 which an error message is also printed. Although
46416 the current rtdt is not destroyed it is no longer
46417 accessible to users. This will affect the
46418 operation of resource management and RCP.
46419
46420 Action: Notify the system administrator.
46421
46422
46423
46424 up_rtdt_.pl1
46425 up_rtdt_: ERROR_MESSAGE Cannot rename new rtdt.
46426
46427
46428 Stream: as severity2
46429
46430 Time: While system is running.
46431
46432 Meaning: The new rtdt being installed could not be renamed
46433 to "rtdt". The rtdt is not installed.
46434
46435 Action: Notify the system administrator.
46436
46437
46438
46439 up_rtdt_.pl1
46440 up_rtdt_: ERROR_MESSAGE Cannot rename old RTDT.
46441
46442
46443 Stream: as severity2
46444
46445 Time: While system is running.
46446
46447 Meaning: The current rtdt could not be renamed to
46448 accomodate the installation of a new rtdt.
46449
46450 Action: Notify the system administrator.
46451
46452
46453
46454
46455
46456
46457
46458
46459 up_rtdt_ -801- MR12.5 10/27/92^L
46460
46461
46462 up_rtdt_.pl1
46463 up_rtdt_: ERROR_MESSAGE Cannot update RCP
46464 registry for RESOURCE_NAME.
46465
46466
46467 Stream: as severity2
46468
46469 Time: While system is running.
46470
46471 Meaning: The error described by ERROR_MESSAGE occurred
46472 while a system administrator was attempting to
46473 install a new rtdt. The rtdt contained changes to
46474 a resource type but the resource management
46475 registry for that resource type could not be
46476 modified. The rtdt is not installed. Some other
46477 registries may already have been modified
46478 according to information in the new rtdt.
46479
46480 Action: Notify the system administrator.
46481
46482
46483
46484 up_sat_.pl1
46485 up_sat_: adding PROJ project with authorization
46486 AUTH
46487
46488
46489 Stream: as severity0
46490
46491 Time: While system is running.
46492
46493 Meaning: A system security administrator has added the
46494 project PROJ with an authorization greater than
46495 system low.
46496
46497 Action: No operator action is required.
46498
46499
46500
46501 up_sat_.pl1
46502 up_sat_: bumping NAME.PROJ over max users on
46503 project
46504
46505
46506 Stream: as severity1
46507
46508 Time: While system is running.
46509
46510 Meaning: The user named has been bumped because the system
46511 administrator has reduced the maximum number of
46512 users that can be logged in on the project PROJ.
46513
46514 Action: No operator action is required.
46515
46516
46517 up_sat_ -802- MR12.5 10/27/92^L
46518
46519
46520 up_sat_.pl1
46521 up_sat_: bumping NAME.PROJ project authorization
46522 reduced
46523
46524
46525 Stream: as severity1
46526
46527 Time: While system is running.
46528
46529 Meaning: A system security administrator has installed a
46530 new SAT that reduces the authorization for the
46531 user identified by NAME on the project PROJ below
46532 the current value assigned to this project.
46533 Therefore the user is being bumped from the
46534 system.
46535
46536 Action: No operator action is required.
46537
46538
46539
46540 up_sat_.pl1
46541 up_sat_: bumping NAME.PROJ project deleted
46542
46543
46544 Stream: as severity1
46545
46546 Time: While system is running.
46547
46548 Meaning: The system administrator has deleted the project
46549 PROJ. All of its users are bumped.
46550
46551 Action: No operator action is required.
46552
46553
46554
46555 up_sat_.pl1
46556 up_sat_: changing authorization of PROJ project
46557 from OLD to NEW
46558
46559
46560 Stream: as severity0
46561
46562 Time: While system is running.
46563
46564 Meaning: A system security administrator has installed a
46565 new SAT that changes the authorization of the
46566 project PROJ. OLD is the previous authorization
46567 for the project; NEW is the authorization now
46568 assigned to the project.
46569
46570 Action: No operator action is required.
46571
46572
46573
46574
46575 up_sat_ -803- MR12.5 10/27/92^L
46576
46577
46578 up_sat_.pl1
46579 up_sat_: ERROR_MESSAGE. cannot make temp
46580
46581
46582 Stream: as severity1
46583
46584 Time: While system is running.
46585
46586 Meaning: A temporary segment could not be created while
46587 attempting to install a new system administrator's
46588 table. The system attempts to proceed.
46589
46590 Action: Contact the system programming staff.
46591
46592
46593
46594 up_sat_.pl1
46595 up_sat_: ERROR_MESSAGE. sat.ht
46596
46597
46598 Stream: as severity2
46599
46600 Time: While system is running.
46601
46602 Meaning: The system was unable to replace the SAT hash
46603 table during installation of a new SAT. The new
46604 SAT has been installed but the old hash table is
46605 still in use so any new projects are unusable.
46606
46607 Action: Contact the system programming staff.
46608
46609
46610
46611 up_sat_.pl1
46612 up_sat_: ERROR_MESSAGE. sat.ht.temp
46613
46614
46615 Stream: as severity2
46616
46617 Time: While system is running.
46618
46619 Meaning: A temporary segment could not be created while
46620 attempting to build a hash table for a new system
46621 administrator's table SAT. The new SAT has been
46622 installed but the old hash table is still in use
46623 so any new projects are unusable.
46624
46625 Action: Contact the system programming staff.
46626
46627
46628
46629
46630
46631
46632
46633 up_sat_ -804- MR12.5 10/27/92^L
46634
46635
46636 up_sat_.pl1
46637 up_sat_: project PROJ on free list state nonzero
46638
46639
46640 Stream: as severity2
46641
46642 Time: While system is running.
46643
46644 Meaning: The free chain for the SAT seems to include a
46645 project that does not have state zero. The system
46646 abandons the free chain and attempts to proceed.
46647
46648 Action: Contact the system administrator.
46649
46650
46651
46652 up_sysctl_.pl1
46653 up_sysctl_$check_acs: MESSAGE. Unable to create
46654 PATHNAME.
46655
46656
46657 Stream: as severity1
46658
46659 Time: While system is running.
46660
46661 Meaning: The named segment does not exist and it was not
46662 possible to create it. Any table installations
46663 controlled by this segment will be ignored. The
46664 table submitted for installation will be deleted.
46665
46666 Action: Contact the system programming staff. Notify the
46667 system administrator. Normal servicing of table
46668 installations will not proceed until this
46669 situation is rectified.
46670
46671
46672
46673
46674
46675
46676
46677
46678
46679
46680
46681
46682
46683
46684
46685
46686
46687
46688
46689
46690
46691 up_sysctl_$check_acs -805- MR12.5 10/27/92^L
46692
46693
46694 up_sysctl_.pl1
46695 up_sysctl_$check_acs: PATHNAME not found. It
46696 will be created.
46697
46698
46699 Stream: as severity1
46700
46701 Time: While system is running.
46702
46703 Meaning: The named segment which controls a table
46704 installation operation does not exist. The
46705 segment will be created with an ACL allowing
46706 *.SysDaemon.* and *.SysAdmin.* to perform the
46707 appropriate table installation.
46708
46709 Action: Contact the system programming staff. The system
46710 administrator should be notified so that the ACL
46711 of the segment may be adjusted to reflect those
46712 users that may install the table.
46713
46714
46715
46716 up_sysctl_.pl1
46717 up_sysctl_$init: ERROR_MESSAGE. cannot
46718 find/create >system_control_1>update
46719
46720
46721 Stream: as severity2
46722
46723 Time: System Intialization.
46724
46725 Meaning: The directory used to update system tables is
46726 missing and cannot be created. No installations
46727 of new system tables cannot be done. Logins and
46728 logouts can go on as usual.
46729
46730 Action: Contact the system administrator.
46731
46732
46733
46734
46735
46736
46737
46738
46739
46740
46741
46742
46743
46744
46745
46746
46747
46748
46749 up_sysctl_$init -806- MR12.5 10/27/92^L
46750
46751
46752 up_sysctl_.pl1
46753 up_sysctl_$init: ERROR_MESSAGE. Cannot make IPC
46754 channel.
46755
46756
46757 Stream: as severity2
46758
46759 Time: System Intialization.
46760
46761 Meaning: It was not possible to establish the IPC channel
46762 which is used to allow users to indicate that an
46763 Answering Service table installation is to be
46764 performed. Installations will not occur.
46765
46766 Action: Contact the system administrator.
46767
46768
46769
46770 up_sysctl_.pl1
46771 up_sysctl_: CONDITION installing TABLE for USER
46772
46773
46774 Stream: as severity1
46775
46776 Time: While system is running.
46777
46778 Meaning: Some unexpected error occurred while installing a
46779 system table. An Answering Service dump was
46780 performed. Further attempts to install system
46781 tables may fail until a reset or force is done
46782 but logins and logouts should be able to proceed
46783 normally.
46784
46785 Action: Contact the system administrator.
46786
46787
46788
46789 up_sysctl_.pl1
46790 up_sysctl_: error - event calls were masked
46791
46792
46793 Stream: sc error_output
46794
46795 Time: While system is running.
46796
46797 Meaning: This indicates a logic error in the supervisor or
46798 CPU or memory hardware problems. The system
46799 attempts to recover and keep running.
46800
46801 Action: Contact the system programming staff.
46802
46803
46804
46805
46806
46807 up_sysctl_ -807- MR12.5 10/27/92^L
46808
46809
46810 up_sysctl_.pl1
46811 up_sysctl_: Error: REASON
46812
46813
46814 Stream: as severity2
46815
46816 Time: While system is running.
46817
46818 Meaning: Some error occurred while installing a system
46819 table. An Answering Service dump was performed.
46820 Further attempts to install system tables may fail
46821 until a force or reset is done but logins and
46822 logouts should be able to proceed as usual.
46823
46824 Action: Contact the system administrator.
46825
46826
46827
46828 up_sysctl_.pl1
46829 up_sysctl_: installed TABLE for USERID
46830
46831
46832 Stream: as severity1
46833
46834 Time: While system is running.
46835
46836 Meaning: An mgt sat cdt pdt or rtdt has been installed.
46837
46838 Action: No operator action is required.
46839
46840
46841
46842
46843
46844
46845
46846
46847
46848
46849
46850
46851
46852
46853
46854
46855
46856
46857
46858
46859
46860
46861
46862
46863
46864
46865 up_sysctl_ -808- MR12.5 10/27/92^L
46866
46867
46868 up_sysctl_.pl1
46869 up_sysctl_: NAME wakeup with N installs pending
46870 up_sysctl_: NAME wakeup from PERSON.PROJECT with
46871 N installs pending
46872
46873
46874 Stream: as severity0
46875
46876 Time: While system is running.
46877
46878 Meaning: A request to perform a table installation was
46879 received. There were N tables found ready for
46880 installation at the time of the wakeup. If N is
46881 0 the PERSON.PROJECT of the originator of the
46882 request is also logged. This message is normally
46883 severity0 but the administrator may cause it to
46884 be severity1.
46885
46886 Action: Contact the system programming staff. The
46887 administrator may request that he be notified if
46888 this occurs. If a large number of these messages
46889 are logged with N = 0 it may indicate that a user
46890 is harassing the installation mechanism.
46891
46892
46893
46894 up_sysctl_.pl1
46895 up_sysctl_: Unable to install TABLE for USERID.
46896 TEXT
46897
46898
46899 Stream: as severity1
46900
46901 Time: While system is running.
46902
46903 Meaning: The user USERID attempted to change the system
46904 table TABLE but something was wrong. The reason
46905 is given by TEXT.
46906
46907 Action: No operator action is required.
46908
46909
46910
46911
46912
46913
46914
46915
46916
46917
46918
46919
46920
46921
46922
46923 up_sysctl_ -809- MR12.5 10/27/92^L
46924
46925
46926 up_sysctl_.pl1
46927 up_sysctl_: Unable to install TABLE for USERID.
46928 userid should be USERID1
46929
46930
46931 Stream: as severity1
46932
46933 Time: While system is running.
46934
46935 Meaning: A user attempted to install a system table by
46936 pretending to be some other user.
46937
46938 Action: Contact the system administrator.
46939
46940
46941
46942 validate_cpu_card.pl1
46943 validate_cpu_card: CPU cache size for CPU CPUTAG
46944 is incorrect should be "CACHE_SIZE."
46945
46946
46947 Stream: BOS Typewriter sounds beeper
46948
46949 Time: While system is running.
46950
46951 Meaning: The CACHE_SIZE as determined from cpu registers
46952 did not match the CACHE_SIZE in the cpu cache size
46953 field of the config card image for CPU CPUTAG.
46954
46955 Action: No operator action is required.
46956
46957
46958
46959 validate_cpu_card.pl1
46960 validate_cpu_card: CPU model for CPU CPUTAG is
46961 incorrect should be "CPUMODEL."
46962
46963
46964 Stream: BOS Typewriter sounds beeper
46965
46966 Time: While system is running.
46967
46968 Meaning: The CPUMODEL as determined from RSW 2
46969 information did not match the CPUMODEL in the cpu
46970 model field of the config card image for CPU
46971 CPUTAG.
46972
46973 Action: No operator action is required.
46974
46975
46976
46977
46978
46979
46980
46981 validate_cpu_card -810- MR12.5 10/27/92^L
46982
46983
46984 validate_cpu_card.pl1
46985 validate_cpu_card: CPU type for CPU CPUTAG is
46986 incorrect should be "CPUTYPE"
46987
46988
46989 Stream: BOS Typewriter sounds beeper
46990
46991 Time: While system is running.
46992
46993 Meaning: The CPUTYPE as determined from RSW 2
46994 information did not match the CPUTYPE in the cpu
46995 type field of the config card image for CPU
46996 CPUTAG.
46997
46998 Action: No operator action is required.
46999
47000
47001
47002 validate_cpu_card.pl1
47003 validate_cpu_card: CPU type model and/or cache
47004 size discrepencies will be corrected
47005
47006
47007 Stream: BOS Typewriter.
47008
47009 Time: While system is running.
47010
47011 Meaning: The indicated discrepencies in the cpu type
47012 model and cache size fields will be corrected by
47013 validate_cpu_card.
47014
47015 Action: The type model and/or cache size fields of the
47016 indicated cpu config card image should be
47017 corrected at BCE before the next bootload.
47018
47019
47020
47021
47022
47023
47024
47025
47026
47027
47028
47029
47030
47031
47032
47033
47034
47035
47036
47037
47038
47039 validate_cpu_card -811- MR12.5 10/27/92^L
47040
47041
47042 verify_lock.pl1
47043 verify_lock: block_lock_count XX should be 0
47044
47045
47046 Stream: BOS Typewriter Crashes system
47047
47048 Time: While system is running.
47049
47050 Meaning: A process has encountered a condition in ring 0
47051 and is in the process of attempting a crawlout.
47052 The system must unlock all locks before it
47053 performs the crawlout; all known locks have been
47054 unlocked but the process' lock counter is still
47055 nonzero. This indicates a logic error in the
47056 supervisor or CPU or memory hardware problems.
47057 This error crashes the system.
47058
47059 Action: Follow normal recovery procedures.
47060
47061
47062
47063 verify_lock.pl1
47064 verify_lock: Crawlout error on directory cleanup.
47065
47066
47067 Stream: BOS Typewriter Crashes system
47068
47069 Time: While system is running.
47070
47071 Meaning: A process encountered a signalled condition with
47072 one or more directories locked. Before the system
47073 causes a crawlout it unlocks and salvages all
47074 locked directories for the process. This process
47075 of cleanup encountered an unrecoverable error.
47076 This error crashes the system.
47077
47078 Action: Follow normal recovery procedures.
47079
47080
47081
47082
47083
47084
47085
47086
47087
47088
47089
47090
47091
47092
47093
47094
47095
47096
47097 verify_lock -812- MR12.5 10/27/92^L
47098
47099
47100 verify_lock.pl1
47101 verify_lock: Crawlout stop specified on PARM
47102 card.
47103
47104
47105 Stream: BOS Typewriter Crashes system
47106
47107 Time: While system is running.
47108
47109 Meaning: The system PARM card specified the CRWL parameter.
47110 A process is attempting to crawl out. This
47111 message will occur so that system programmers can
47112 take a dump.
47113
47114 Action: Take a dump. Issuing the BCE go command will
47115 cause the system to continue.
47116
47117
47118
47119 verify_lock.pl1
47120 verify_lock: Crawlout while in directory
47121 salvager dir UIDPTR.
47122
47123
47124 Stream: Logged in SYSERR log.
47125
47126 Time: While system is running.
47127
47128 Meaning: A process faulted while salvaging a dir on
47129 crawlout.
47130
47131 Action: No operator action is required.
47132
47133
47134
47135 verify_lock.pl1
47136 verify_lock: Crawlout while masked.
47137
47138
47139 Stream: BOS Typewriter Crashes system
47140
47141 Time: While system is running.
47142
47143 Meaning: This error crashes the system.
47144
47145 Action: Contact the system programming staff.
47146
47147
47148
47149
47150
47151
47152
47153
47154
47155 verify_lock -813- MR12.5 10/27/92^L
47156
47157
47158 verify_lock.pl1
47159 verify_lock: Crawlout with AST lock set.
47160
47161
47162 Stream: BOS Typewriter Crashes system
47163
47164 Time: While system is running.
47165
47166 Meaning: A user process encountered a condition while
47167 processing with the AST locked. This condition
47168 may have been due to a hardware or software
47169 failure. This error crashes the system.
47170
47171 Action: Follow normal recovery procedures.
47172
47173
47174
47175 verify_lock.pl1
47176 verify_lock: dir.modify PPPP WWWW ^^= processid.
47177
47178
47179 Stream: BOS Typewriter Crashes system
47180
47181 Time: While system is running.
47182
47183 Meaning: A process is attempting to crawl out. The system
47184 has discovered that a directory which is marked
47185 locked to the process has its "modify" field not
47186 equal to the processid of the process. This
47187 indicates a logic error in the supervisor or CPU
47188 or memory hardware problems. This error crashes
47189 the system.
47190
47191 Action: Follow normal recovery procedures.
47192
47193
47194
47195
47196
47197
47198
47199
47200
47201
47202
47203
47204
47205
47206
47207
47208
47209
47210
47211
47212
47213 verify_lock -814- MR12.5 10/27/92^L
47214
47215
47216 verify_lock.pl1
47217 verify_lock: Force unlocked Volmap lock dskX_NN
47218 on crawlout for PERSON.PROJECT.TAG
47219
47220
47221 Stream: Logged in SYSERR log.
47222
47223 Time: While system is running.
47224
47225 Meaning: The Volmap Lock for the device indicated was found
47226 locked to a process on crawlout. The lock has
47227 been reset and the count of volume
47228 inconsistencies for the device has been
47229 incremented by one.
47230
47231 Action: Any free records or VTOCEs lost because of the
47232 crawlout can be recovered by a volume salvage.
47233
47234
47235
47236 verify_lock.pl1
47237 verify_lock: Force unlocked VTOC Map lock
47238 dskX_NN on crawlout for PERSON.PROJECT.TAG
47239
47240
47241 Stream: Logged in SYSERR log.
47242
47243 Time: While system is running.
47244
47245 Meaning: The VTOC Map lock for the device indicated was
47246 found locked to the process on crawlout. The lock
47247 has been reset and the count of volume
47248 inconsistencies has been incremented by one.
47249
47250 Action: Any free records or VTOCEs lost because of the
47251 crawlout can be recovered by a volume salvage.
47252
47253
47254
47255
47256
47257
47258
47259
47260
47261
47262
47263
47264
47265
47266
47267
47268
47269
47270
47271 verify_lock -815- MR12.5 10/27/92^L
47272
47273
47274 verify_lock.pl1
47275 verify_lock: more than N directory locks locked
47276 to process.
47277
47278
47279 Stream: BOS Typewriter Crashes system
47280
47281 Time: While system is running.
47282
47283 Meaning: The process held more dir locks than verify lock
47284 could store for later salvaging. This indicates a
47285 logic error in the supervisor.
47286
47287 Action: This error crashes the system. Follow normal
47288 recovery procedures.
47289
47290
47291
47292 verify_lock.pl1
47293 verify_lock: NAME condition by PERS.PROJ
47294
47295
47296 Stream: Logged in SYSERR log.
47297
47298 Time: While system is running.
47299
47300 Meaning: User PERS.PROJ encountered a NAME condition in
47301 ring 0. The system attempts to unlock and reset
47302 all ring 0 data bases locked by the process.
47303
47304 Action: These messages almost always indicate benign
47305 errors in the supervisor. They should be
47306 reported nonetheless. They are accompanied by
47307 the binary machine condition information. This
47308 message is logged only when the condition occured
47309 while some ring-0 lock was set. One or more
47310 messages preceeding this one will indicate which
47311 locks were held by the process and forcibly reset.
47312
47313
47314
47315
47316
47317
47318
47319
47320
47321
47322
47323
47324
47325
47326
47327
47328
47329 verify_lock -816- MR12.5 10/27/92^L
47330
47331
47332 verify_lock.pl1
47333 verify_lock: Salvaging dir PTR UID on crawlout.
47334
47335
47336 Stream: Logged in SYSERR log.
47337
47338 Time: While system is running.
47339
47340 Meaning: This message is displayed for each directory found
47341 locked on a crawlout. The online salvager will be
47342 called and the directory unlocked.
47343
47344 Action: No operator action is required.
47345
47346
47347
47348 verify_lock.pl1
47349 verify_lock: Unlocked LOCK.
47350
47351
47352 Stream: Logged in SYSERR log.
47353
47354 Time: While system is running.
47355
47356 Meaning: The lock LOCK was found locked at crawlout and
47357 unlocked.
47358
47359 Action: No operator action is required.
47360
47361
47362
47363 verify_lock.pl1
47364 verify_lock: Unlocking dir UUUUUUUUUUUU. Locked
47365 for READ_OR_WRITE salvage.
47366
47367
47368 Stream: Logged in SYSERR log.
47369
47370 Time: While system is running.
47371
47372 Meaning: The directory with UID UUUUUUUUUUUU was found
47373 locked at crawl-out time. It is salvaged and then
47374 unlocked.
47375
47376 Action: Contact the system programming staff.
47377
47378
47379
47380
47381
47382
47383
47384
47385
47386
47387 verify_lock -817- MR12.5 10/27/92^L
47388
47389
47390 vm_vio.pl1
47391 vm_vio: get_vtocep: invalid pvtx: PPPo
47392
47393
47394 Stream: BOS Typewriter.
47395
47396 Time: Volume salvaging or disk rebuilding.
47397
47398 Meaning: The Volume Salvager virtual access package has
47399 been given a bad PVT index parameter PPP shown
47400 in octal. This indicates a logic error in the
47401 supervisor or CPU or memory hardware problems.
47402
47403 Action: Salvaging will not proceed. The Multics System
47404 Tape may be incorrect. If the problem persists
47405 try another MST.
47406
47407
47408
47409 vm_vio.pl1
47410 vm_vio: get_vtocep: invalid vtocx VVVo on pvtx
47411 PPPo
47412
47413
47414 Stream: BOS Typewriter.
47415
47416 Time: Volume salvaging or disk rebuilding.
47417
47418 Meaning: An out-of-range VTOC index VVV has been given to
47419 the Volume Salvager virtual access package while
47420 processing PV at pvtx PPP. The vtocx and pvtx are
47421 shown in octal. This indicates a logic error in
47422 the supervisor or CPU or memory hardware
47423 problems.
47424
47425 Action: Salvaging may fail. Note for system programmer
47426 action.
47427
47428
47429
47430
47431
47432
47433
47434
47435
47436
47437
47438
47439
47440
47441
47442
47443
47444
47445 vm_vio -818- MR12.5 10/27/92^L
47446
47447
47448 vm_vio.pl1
47449 vm_vio: no AST pointer at readahead.
47450
47451
47452 Stream: BOS Typewriter Crashes system
47453
47454 Time: Volume salvaging or disk rebuilding.
47455
47456 Meaning: No AST entry pointer was found for a
47457 VTOC-addressing segment used by the Volume
47458 Salvager virtual access package. This indicates a
47459 logic error in the supervisor or CPU or memory
47460 hardware problems.
47461
47462 Action: Follow normal recovery procedures. Note for
47463 system programmer action.
47464
47465
47466
47467 page_error.alm
47468 volmap: Attempt to deposit in-use address YYYYYY
47469 on dskX_NNS.
47470
47471
47472 Stream: BOS Typewriter.
47473
47474 Time: While system is running.
47475
47476 Meaning: An attempt was made to return disk address YYYYYY
47477 to the free pool on dskX_NNS but the address
47478 was already marked as free. This indicates damage
47479 of some sort to the Volume Map. This damage can
47480 be repaired by a volume salvage.
47481
47482 Action: Contact the system programming staff.
47483
47484
47485
47486 page_error.alm
47487 volmap: Invalid Volume Map address computation
47488 for YYYYYY on dskX_NNS.
47489
47490
47491 Stream: BOS Typewriter Crashes system
47492
47493 Time: While system is running.
47494
47495 Meaning: In attempting to place the disk address YYYYYY
47496 into the free pool for dskX_NNS an error
47497 occurred in translating the address into a
47498 location within the Volume Map. This indicates a
47499 software error.
47500
47501
47502
47503 volmap -819- MR12.5 10/27/92^L
47504
47505
47506 page_error.alm
47507 volmap: Invalid volume map word on dskX_NNS.
47508
47509
47510 Stream: BOS Typewriter Crashes system
47511
47512 Time: While system is running.
47513
47514 Meaning: An attempt to withdraw a disk address from the
47515 pool of free addresses on dskX_NNS resulted in
47516 finding a volume map word with at least one of
47517 bits 0 33 34 and 35 on. These bits are invalid
47518 for volume map words. This indicates hardware or
47519 software failure.
47520
47521 Action: Perform an ESD. Reboot the system and perform a
47522 volume salvage not a scavenge of the disk volume
47523 dskX_NNS. This may be performed at Initializer
47524 ring-1 or ring-4 command level. Perform the
47525 salvage before adding the storage system volume
47526 back to the system. The volume scavenger will not
47527 detect volume map words with invalid bits enabled
47528 so the salvager must be used. Once the salvage is
47529 complete the volume may be added back to the
47530 system.
47531
47532
47533
47534 page_error.alm
47535 volmap: record stock inconsistent on dskX_NNS.
47536 stockp=YYY|YYYYY.
47537
47538
47539 Stream: BOS Typewriter Crashes system
47540
47541 Time: While system is running.
47542
47543 Meaning: An attempt to deposit a record address from the
47544 Volume Map to the record stock failed
47545 unaccountably. This indicates probably software
47546 failure.
47547
47548 Action: Follow normal recovery procedures.
47549
47550
47551
47552
47553
47554
47555
47556
47557
47558
47559
47560
47561 volmap -820- MR12.5 10/27/92^L
47562
47563
47564 page_error.alm
47565 volmap: Volume Map inconsistent on dskX_NNS.
47566
47567
47568 Stream: BOS Typewriter Crashes system
47569
47570 Time: While system is running.
47571
47572 Meaning: An attempt to withdraw a disk address from the
47573 pool of free addresses on dskX_NNS failed
47574 although the control structures describing the
47575 Volume Map indicated that addresses were
47576 available. This indicates hardware or software
47577 failure.
47578
47579 Action: Follow normal recovery procedures.
47580
47581
47582
47583 page_error.alm
47584 volmap_page: Async error for dskX_NNS.
47585
47586
47587 Stream: BOS Typewriter Crashes system
47588
47589 Time: While system is running.
47590
47591 Meaning: When attempting to write an updated page of the
47592 Volume Map on dskX_NNS it was found not to be
47593 in memory. This indicates a software failure.
47594
47595 Action: Follow normal recovery procedures.
47596
47597
47598
47599 page_error.alm
47600 volmap_page: Async state on dskX_NNS changed to
47601 S on poll.
47602
47603
47604 Stream: Logged in SYSERR log.
47605
47606 Time: While system is running.
47607
47608 Meaning: An interrupt for a volume map I/O was lost and was
47609 recovered by a periodic polling routine.
47610
47611 Action: No operator action is required.
47612
47613
47614
47615
47616
47617
47618
47619 volmap_page -821- MR12.5 10/27/92^L
47620
47621
47622 page_error.alm
47623 volmap_page: Invalid async state on dskX_NNS.
47624
47625
47626 Stream: BOS Typewriter Crashes system
47627
47628 Time: While system is running.
47629
47630 Meaning: An inconsistency was discovered in the
47631 asynchronous update state of the Volume Map on
47632 dskX_NNS. This is likely a software error.
47633
47634 Action: Follow normal recovery procedures.
47635
47636
47637
47638 page_error.alm
47639 volmap_page: Invalid call.
47640
47641
47642 Stream: BOS Typewriter Crashes system
47643
47644 Time: While system is running.
47645
47646 Meaning: One of the conditions required for a call to a
47647 volmap_page entry point was not present. This
47648 indicates a software failure in the caller of
47649 volmap_page.
47650
47651 Action: Follow normal recovery procedures.
47652
47653
47654
47655 page_error.alm
47656 volmap_page: PTL not locked to process.
47657
47658
47659 Stream: BOS Typewriter Crashes system
47660
47661 Time: While system is running.
47662
47663 Meaning: An entry in volmap_page was called which required
47664 that the Global Page Table lock be held by the
47665 calling process. It was not held by that process
47666 indicating software failure.
47667
47668 Action: Follow normal recovery procedures.
47669
47670
47671
47672
47673
47674
47675
47676
47677 volmap_page -822- MR12.5 10/27/92^L
47678
47679
47680 page_error.alm
47681 volmap_page: Unrecoverable I/O error on Volmap
47682 page M of dskX_NNS. Addresses lost.
47683
47684
47685 Stream: BOS Typewriter sounds beeper
47686
47687 Time: While system is running.
47688
47689 Meaning: There was an unrecoverable I/O on a page of the
47690 Volume Map which describes free records on the
47691 volume. As a result all free records described
47692 by that page of the Volume Map have been lost.
47693
47694 Action: It may be possible to recover the lost addresses
47695 by a volume salvage. However a hard device error
47696 will prevent the volume salvage from succeeding.
47697 In this case it will be necessary to recover the
47698 volume to a good pack.
47699
47700
47701
47702 volmap_util.pl1
47703 volmap_util: Address XXXXXX out of paging region
47704 on dskX_NN.
47705
47706
47707 Stream: BOS Typewriter Crashes system
47708
47709 Time: During a physical volume scavenge
47710
47711 Meaning: The scavenger attempted to remove an invalid
47712 address from the volume map.
47713
47714 Action: Follow normal recovery procedures.
47715
47716
47717
47718 volmap_util.pl1
47719 volmap_util: Invalid address XXXXXX on dskX_NN.
47720
47721
47722 Stream: BOS Typewriter Crashes system
47723
47724 Time: During a physical volume scavenge
47725
47726 Meaning: In attempting to deposit address XXXXXX on device
47727 dskX_NN an invalid volume map offset was
47728 computed.
47729
47730 Action: Follow normal recovery procedures.
47731
47732
47733
47734
47735 volmap_util -823- MR12.5 10/27/92^L
47736
47737
47738 init_disk_pack_.pl1
47739 volume PVNAME XX records
47740
47741
47742 Stream: Initializer process output.
47743
47744 Time: In response to an operator command.
47745
47746 Meaning: The physical volume PVNAME has been successfully
47747 initialized. There are XX decimal records in
47748 the paging area.
47749
47750 Action: No operator action is required.
47751
47752
47753
47754 volume_registration_mgr_.pl1
47755 volume_registration_mgr_$add_lvr: Added new LV
47756 "LVNAME". GROUP_ID
47757
47758
47759 Stream: Logged in SYSERR log.
47760
47761 Time: While system is running.
47762
47763 Meaning: A new storage system logical volume has been
47764 registered on the system.
47765
47766 Action: No operator action is required.
47767
47768
47769
47770 volume_registration_mgr_.pl1
47771 volume_registration_mgr_$add_lvr: Added new PV
47772 "PVNAME" to LV "LVNAME". GROUP_ID
47773
47774
47775 Stream: Logged in SYSERR log.
47776
47777 Time: While system is running.
47778
47779 Meaning: A new storage system physical volume has been
47780 registered on the system.
47781
47782 Action: No operator action is required.
47783
47784
47785
47786
47787
47788
47789
47790
47791
47792
47793 volume_registration_mgr_$a -824- MR12.5 10/27/92^L
47794
47795
47796 volume_registration_mgr_.pl1
47797 volume_registration_mgr_$add_lvr: Could not
47798 append link for LV name | LVID | PV name | PVID.
47799 GROUP_ID ERROR_MESSAGE
47800
47801
47802 Stream: BOS Typewriter.
47803
47804 Time: While system is running.
47805
47806 Meaning: A link could not be added into >lv whose target is
47807 a database segment located under the root
47808 directory. Future database references may not be
47809 possible.
47810
47811 Action: Contact the system programming staff.
47812
47813
47814
47815 volume_registration_mgr_.pl1
47816 volume_registration_mgr_$add_lvr: Unable to back
47817 out database "lv.LVNAME". GROUP_ID
47818 ERROR_MESSAGE
47819
47820
47821 Stream: BOS Typewriter.
47822
47823 Time: While system is running.
47824
47825 Meaning: When attempting to register a new logical volume
47826 some error occurred. The entry then attempted to
47827 remove the database segment just created. This
47828 removal failed.
47829
47830 Action: Contact the system programming staff.
47831
47832
47833
47834 volume_registration_mgr_.pl1
47835 volume_registration_mgr_$add_pvr: Added new PV
47836 "PVNAME" to LV "LVNAME". GROUP_ID -log-
47837
47838
47839 Stream: Logged in SYSERR log.
47840
47841 Time: While system is running.
47842
47843 Meaning: A new storage system physical volume has been
47844 registered on the system.
47845
47846 Action: No operator action is required.
47847
47848
47849
47850
47851 volume_registration_mgr_$a -825- MR12.5 10/27/92^L
47852
47853
47854 volume_registration_mgr_.pl1
47855 volume_registration_mgr_$add_pvr: Could not
47856 append link for PV name| PVID. GROUP_ID
47857 ERROR_MESSAGE
47858
47859
47860 Stream: BOS Typewriter.
47861
47862 Time: While system is running.
47863
47864 Meaning: A link could not be added into >lv whose target is
47865 a database segment located under the root
47866 directory. Future database references may not be
47867 possible.
47868
47869 Action: Contact the system programming staff.
47870
47871
47872
47873 volume_registration_mgr_.pl1
47874 volume_registration_mgr_$add_pvr: Extra PV entry
47875 "PVNAME" in database "lv.LVNAME". GROUP_ID
47876
47877
47878 Stream: BOS Typewriter.
47879
47880 Time: While system is running.
47881
47882 Meaning: This indicates a logic error in the supervisor or
47883 CPU or memory hardware problems. An entry for the
47884 specified PV was found in the database segment for
47885 the specified LV where no segment addname
47886 indicated its existance.
47887
47888 Action: Contact the system programming staff.
47889
47890
47891
47892
47893
47894
47895
47896
47897
47898
47899
47900
47901
47902
47903
47904
47905
47906
47907
47908
47909 volume_registration_mgr_$a -826- MR12.5 10/27/92^L
47910
47911
47912 volume_registration_mgr_.pl1
47913 volume_registration_mgr_$add_pvr: Unable to back
47914 out database addname "pv.PVNAME". GROUP_ID
47915 ERROR_MESSAGE
47916
47917
47918 Stream: BOS Typewriter.
47919
47920 Time: While system is running.
47921
47922 Meaning: An error occurred while registering a new PV. The
47923 entry attmpts to undo all work up to the point of
47924 the error. In this case it was unable to undo
47925 its manipulations and left a spurious addname
47926 "pv.PVNAME" on the database segment.
47927
47928 Action: Contact the system programming staff.
47929
47930
47931
47932 volume_registration_mgr_.pl1
47933 volume_registration_mgr_$change_lvr: Changed ACS
47934 pathname for LV "LVNAME" to "PATH". GROUP_ID
47935
47936
47937 Stream: Logged in SYSERR log.
47938
47939 Time: While system is running.
47940
47941 Meaning: The registered ACS pathname of a storage system
47942 logical volume has been changed as indicated.
47943
47944 Action: No operator action is required.
47945
47946
47947
47948 volume_registration_mgr_.pl1
47949 volume_registration_mgr_$change_lvr: Changed LV
47950 "LVNAME" to PRIVATE | PUBLIC. GROUP_ID
47951
47952
47953 Stream: Logged in SYSERR log.
47954
47955 Time: While system is running.
47956
47957 Meaning: The access type of the specified logical volume
47958 has been changed.
47959
47960 Action: No operator action is required.
47961
47962
47963
47964
47965
47966
47967 volume_registration_mgr_$c -827- MR12.5 10/27/92^L
47968
47969
47970 volume_registration_mgr_.pl1
47971 volume_registration_mgr_$change_lvr: Changed LVID
47972 of LV "LVNAME" from "LVID1" to "LVID2".
47973 GROUP_ID
47974
47975
47976 Stream: Logged in SYSERR log.
47977
47978 Time: While system is running.
47979
47980 Meaning: The registered logical volume unique ID has been
47981 changed for the specified LV.
47982
47983 Action: No operator action is required.
47984
47985
47986
47987 volume_registration_mgr_.pl1
47988 volume_registration_mgr_$change_lvr: Changed name
47989 of LV "LVNAME1" to "LVNAME2". GROUP_ID
47990
47991
47992 Stream: Logged in SYSERR log.
47993
47994 Time: While system is running.
47995
47996 Meaning: The registered name of a storage system logical
47997 volume has been changed as indicated.
47998
47999 Action: No operator action is required.
48000
48001
48002
48003 volume_registration_mgr_.pl1
48004 volume_registration_mgr_$change_lvr: Changed
48005 owner of LV "LVNAME" from "Person1.Project1" to
48006 "Person2.Project2". GROUP_ID
48007
48008
48009 Stream: Logged in SYSERR log.
48010
48011 Time: While system is running.
48012
48013 Meaning: The owner of a storage system logical volume has
48014 been changed as indicated.
48015
48016 Action: No operator action is required.
48017
48018
48019
48020
48021
48022
48023
48024
48025 volume_registration_mgr_$c -828- MR12.5 10/27/92^L
48026
48027
48028 volume_registration_mgr_.pl1
48029 volume_registration_mgr_$change_lvr: Changed max
48030 | min access class of LV "LVNAME" from
48031 "AUTH_STR1" to "AUTH_STR2". GROUP_ID
48032
48033
48034 Stream: Logged in SYSERR log.
48035
48036 Time: While system is running.
48037
48038 Meaning: The access class of a storage system logical
48039 volume has been changed as indicated.
48040
48041 Action: No operator action is required.
48042
48043
48044
48045 volume_registration_mgr_.pl1
48046 volume_registration_mgr_$change_lvr: Couldn't
48047 delete | create link for old | new LV name |
48048 LVID. GROUP_ID ERROR_MESSAGE
48049
48050
48051 Stream: BOS Typewriter.
48052
48053 Time: While system is running.
48054
48055 Meaning: A link for the specified database segment residing
48056 under the root directory could not be created in
48057 >lv.
48058
48059 Action: Contact the system programming staff.
48060
48061
48062
48063
48064
48065
48066
48067
48068
48069
48070
48071
48072
48073
48074
48075
48076
48077
48078
48079
48080
48081
48082
48083 volume_registration_mgr_$c -829- MR12.5 10/27/92^L
48084
48085
48086 volume_registration_mgr_.pl1
48087 volume_registration_mgr_$change_lvr: Unable to
48088 back out LVID change to "LVNAME.mdcs". GROUP_ID
48089 ERROR_MESSAGE
48090
48091
48092 Stream: BOS Typewriter.
48093
48094 Time: While system is running.
48095
48096 Meaning: This indicates a logic error in the supervisor or
48097 CPU or memory hardware problems. While changing
48098 attributes of the logical volume LVNAME an error
48099 was encountered. The entry then attempted to
48100 remove some changes already made to the
48101 registration database. In this case it could not
48102 remove the LVID change to the master directory
48103 control database LVNAME.mdcs.
48104
48105 Action: Contact the system programming staff.
48106
48107
48108
48109 volume_registration_mgr_.pl1
48110 volume_registration_mgr_$change_lvr: Unable to
48111 change name "lv.LVNAME1" back to "lv.LVNAME2"
48112 GROUP_ID ERROR_MESSAGE
48113
48114
48115 Stream: BOS Typewriter.
48116
48117 Time: While system is running.
48118
48119 Meaning: This indicates a logic error in the supervisor or
48120 CPU or memory hardware problems. While changing
48121 attributes ot the logical volume LVNAME an error
48122 was encountered. The entry then attempted to
48123 remove some changes already made to the
48124 registration database. In this case it could not
48125 remove theLV name change.
48126
48127 Action: Contact the system programming staff.
48128
48129
48130
48131
48132
48133
48134
48135
48136
48137
48138
48139
48140
48141 volume_registration_mgr_$c -830- MR12.5 10/27/92^L
48142
48143
48144 volume_registration_mgr_.pl1
48145 volume_registration_mgr_$change_lvr: Unable to
48146 change name "lvid.UNIQUE1" back to "lvid.UNIQUE2".
48147 GROUP_ID ERROR_MESSAGE
48148
48149
48150 Stream: BOS Typewriter.
48151
48152 Time: While system is running.
48153
48154 Meaning: This indicates a logic error in the supervisor or
48155 CPU or memory hardware problems. While changing
48156 attributes ot the logical volume LVNAME an error
48157 was encountered. The entry then attempted to
48158 remove some changes already made to the
48159 registration database. In this case it could not
48160 remove LVID name change.
48161
48162 Action: Contact the system programming staff.
48163
48164
48165
48166 volume_registration_mgr_.pl1
48167 volume_registration_mgr_$change_lvr: Unable to
48168 convert max | min auth to name_string.
48169 GROUP_ID ERROR_MESSAGE
48170
48171
48172 Stream: BOS Typewriter.
48173
48174 Time: While system is running.
48175
48176 Meaning: This indicates a logic error in the supervisor or
48177 CPU or memory hardware problems. A binary
48178 authorization string could not be converted to its
48179 readable representation.
48180
48181 Action: Contact the system programming staff.
48182
48183
48184
48185
48186
48187
48188
48189
48190
48191
48192
48193
48194
48195
48196
48197
48198
48199 volume_registration_mgr_$c -831- MR12.5 10/27/92^L
48200
48201
48202 volume_registration_mgr_.pl1
48203 volume_registration_mgr_$change_lvr: Unexpected
48204 error changing name on "lv.LVNAME". GROUP_ID
48205 ERROR_MESSAGE
48206
48207
48208 Stream: BOS Typewriter.
48209
48210 Time: While system is running.
48211
48212 Meaning: This indicates a logic error in the supervisor or
48213 CPU or memory hardware problems. An unexpected
48214 error occured while changing the name on an LV
48215 registration data segment. The message explains
48216 the trouble.
48217
48218 Action: Contact the system programming staff.
48219
48220
48221
48222 volume_registration_mgr_.pl1
48223 volume_registration_mgr_$change_lvr: Unexpected
48224 trouble changing name "lvid.UNIQUE". GROUP_ID
48225 ERROR_MESSAGE
48226
48227
48228 Stream: BOS Typewriter.
48229
48230 Time: While system is running.
48231
48232 Meaning: This indicates a logic error in the supervisor or
48233 CPU or memory hardware problems. An unexpected
48234 error occured while changing the name on an LV
48235 registration data segment. The message explains
48236 the trouble.
48237
48238 Action: Contact the system programming staff.
48239
48240
48241
48242
48243
48244
48245
48246
48247
48248
48249
48250
48251
48252
48253
48254
48255
48256
48257 volume_registration_mgr_$c -832- MR12.5 10/27/92^L
48258
48259
48260 volume_registration_mgr_.pl1
48261 volume_registration_mgr_$change_pvr: Changed
48262 date_registered of PV "PVNAME" from "DT1" to
48263 "DT2". GROUP_ID
48264
48265
48266 Stream: Logged in SYSERR log.
48267
48268 Time: While system is running.
48269
48270 Meaning: The registered date for the specified PV has been
48271 changed as indicated.
48272
48273 Action: No operator action is required.
48274
48275
48276
48277 volume_registration_mgr_.pl1
48278 volume_registration_mgr_$change_pvr: Changed
48279 location of PV "PVNAME" from "LOC1" to "LOC2".
48280 GROUP_ID
48281
48282
48283 Stream: Logged in SYSERR log.
48284
48285 Time: While system is running.
48286
48287 Meaning: The registered location of the specified PV has
48288 been changed as indicated.
48289
48290 Action: No operator action is required.
48291
48292
48293
48294 volume_registration_mgr_.pl1
48295 volume_registration_mgr_$change_pvr: Changed
48296 mfg_serial of PV "PVNAME" from "STR1" to "STR2".
48297 GROUP_ID
48298
48299
48300 Stream: Logged in SYSERR log.
48301
48302 Time: While system is running.
48303
48304 Meaning: The registered serial of the specified PV has been
48305 changed as indicated.
48306
48307 Action: No operator action is required.
48308
48309
48310
48311
48312
48313
48314
48315 volume_registration_mgr_$c -833- MR12.5 10/27/92^L
48316
48317
48318 volume_registration_mgr_.pl1
48319 volume_registration_mgr_$change_pvr: Changed
48320 model of PV "PVNAME" from "TYPE1" to "TYPE2".
48321 GROUP_ID
48322
48323
48324 Stream: Logged in SYSERR log.
48325
48326 Time: While system is running.
48327
48328 Meaning: The registered model number of the specified PV
48329 has been changed as indicated.
48330
48331 Action: No operator action is required.
48332
48333
48334
48335 volume_registration_mgr_.pl1
48336 volume_registration_mgr_$change_pvr: Changed name
48337 of PV "PVNAME1" to "PVNAME2". GROUP_ID
48338
48339
48340 Stream: Logged in SYSERR log.
48341
48342 Time: While system is running.
48343
48344 Meaning: The registered name of the specified PV has been
48345 changed as indicated.
48346
48347 Action: No operator action is required.
48348
48349
48350
48351 volume_registration_mgr_.pl1
48352 volume_registration_mgr_$change_pvr: Changed
48353 password of PV "PVNAME". GROUP_ID
48354
48355
48356 Stream: Logged in SYSERR log.
48357
48358 Time: While system is running.
48359
48360 Meaning: The registered password of the specified PV has
48361 been changed as indicated.
48362
48363 Action: No operator action is required.
48364
48365
48366
48367
48368
48369
48370
48371
48372
48373 volume_registration_mgr_$c -834- MR12.5 10/27/92^L
48374
48375
48376 volume_registration_mgr_.pl1
48377 volume_registration_mgr_$change_pvr: Changed PVID
48378 of PV "PVNAME" from "PVID1" to "PVID2" GROUP_ID
48379
48380
48381 Stream: Logged in SYSERR log.
48382
48383 Time: While system is running.
48384
48385 Meaning: The registered physical volume unique IFD has been
48386 changed as indicated.
48387
48388 Action: No operator action is required.
48389
48390
48391
48392 volume_registration_mgr_.pl1
48393 volume_registration_mgr_$change_pvr: Couldn't
48394 delete | create link for old | new PV name |
48395 PVID. GROUP_ID ERROR_MESSAGE
48396
48397
48398 Stream: BOS Typewriter.
48399
48400 Time: While system is running.
48401
48402 Meaning: A link for a database segment residing in the root
48403 directory could not be created in >lv. This may
48404 make some registration data inaccessible.
48405
48406 Action: Contact the system programming staff.
48407
48408
48409
48410 volume_registration_mgr_.pl1
48411 volume_registration_mgr_$change_pvr: PV entry
48412 missing from database "pv.PVNAME". GROUP_ID
48413
48414
48415 Stream: BOS Typewriter.
48416
48417 Time: While system is running.
48418
48419 Meaning: This indicates a logic error in the supervisor or
48420 CPU or memory hardware problems. An entry for the
48421 specified PV could not be found in the data
48422 segment although an addname for that PV exists on
48423 the segment entry.
48424
48425 Action: Contact the system programming staff.
48426
48427
48428
48429
48430
48431 volume_registration_mgr_$c -835- MR12.5 10/27/92^L
48432
48433
48434 volume_registration_mgr_.pl1
48435 volume_registration_mgr_$change_pvr: Unable to
48436 back out PVID change. GROUP_ID ERROR_MESSAGE
48437
48438
48439 Stream: BOS Typewriter.
48440
48441 Time: While system is running.
48442
48443 Meaning: While making changes to the registered PV
48444 attributes an error was encountered. The module
48445 attempts to remove any work already done on other
48446 attributes. For reasons given in ERROR_MESSAGE
48447 the PVID change could not be removed.
48448
48449 Action: Contact the system programming staff.
48450
48451
48452
48453 volume_registration_mgr_.pl1
48454 volume_registration_mgr_$change_pvr: Unexpected
48455 trouble changing name "pv.PVNAME". GROUP_ID
48456 ERROR_MESSAGE
48457
48458
48459 Stream: BOS Typewriter.
48460
48461 Time: While system is running.
48462
48463 Meaning: While making changes to the registered PV
48464 attributes an error was encountered. The module
48465 attempts to remove any work already done on other
48466 attributes. For reasons given in ERROR_MESSAGE
48467 the PV name change could not be removed.
48468
48469 Action: Contact the system programming staff.
48470
48471
48472
48473
48474
48475
48476
48477
48478
48479
48480
48481
48482
48483
48484
48485
48486
48487
48488
48489 volume_registration_mgr_$c -836- MR12.5 10/27/92^L
48490
48491
48492 volume_registration_mgr_.pl1
48493 volume_registration_mgr_$change_pvr: Unexpected
48494 trouble changing name "pvid.UNIQUE". GROUP_ID
48495 ERROR_MESSAGE
48496
48497
48498 Stream: BOS Typewriter.
48499
48500 Time: While system is running.
48501
48502 Meaning: An unexpected state made the program unable to
48503 change the database name associated with the PV
48504 unique ID.
48505
48506 Action: Contact the system programming staff.
48507
48508
48509
48510 volume_registration_mgr_.pl1
48511 volume_registration_mgr_$check_volume_registration:
48512 ERROR_MESSAGE. PATH
48513
48514
48515 Stream: BOS Typewriter.
48516
48517 Time: System Intialization.
48518
48519 Meaning: An error occurred when trying to reclassify a new
48520 lv.** seg as a multi-class system segment.
48521
48522 Action: Contact the system programming staff.
48523
48524
48525
48526
48527
48528
48529
48530
48531
48532
48533
48534
48535
48536
48537
48538
48539
48540
48541
48542
48543
48544
48545
48546
48547 volume_registration_mgr_$c -837- MR12.5 10/27/92^L
48548
48549
48550 volume_registration_mgr_.pl1
48551 volume_registration_mgr_$check_volume_registration:
48552 Code N. lv.LVNAME disagreed with disk_table. It
48553 was rebuilt.
48554
48555
48556 Stream: BOS Typewriter.
48557
48558 Time: System Intialization.
48559
48560 Meaning: When the system is bootloaded it checks the list
48561 of packs which were mounted during the last
48562 bootload to make sure that each one has a valid
48563 logical and physical volume registration. The
48564 registration file lv.LVNAME was found but
48565 disagreed with the disk_table_ and so it was
48566 corrected. The meaning of the codes can be
48567 determined from the listing of
48568 volume_registration_mgr_; it is rarely important.
48569
48570 Action: Use list_vol_registration to examine the remade
48571 registration and correct it with
48572 change_vol_registration if necessary.
48573
48574
48575
48576 volume_registration_mgr_.pl1
48577 volume_registration_mgr_$check_volume_registration:
48578 ERROR_MESSAGE. Cannot add SysAdmin access to >lv.
48579
48580
48581 Stream: BOS Typewriter.
48582
48583 Time: System Intialization.
48584
48585 Meaning: After creating a new >lv directory an attempt is
48586 made to add "sma" access for *.SysAdmin.*. This
48587 failed.
48588
48589 Action: Contact the system programming staff.
48590
48591
48592
48593
48594
48595
48596
48597
48598
48599
48600
48601
48602
48603
48604
48605 volume_registration_mgr_$c -838- MR12.5 10/27/92^L
48606
48607
48608 volume_registration_mgr_.pl1
48609 volume_registration_mgr_$check_volume_registration:
48610 ERROR_MESSAGE. Cannot make mdcs for LVNAME
48611
48612
48613 Stream: BOS Typewriter.
48614
48615 Time: System Intialization.
48616
48617 Meaning: When the system is bootloaded it checks the list
48618 of packs which were mounted during the last
48619 bootload to make sure that each one has a valid
48620 logical and physical volume registration. An
48621 error occurred while reconstructing LVNAME.mdcs.
48622 Operation on master directories for LVNAME may
48623 encounter problems.
48624
48625 Action: Contact the system administrator.
48626
48627
48628
48629 volume_registration_mgr_.pl1
48630 volume_registration_mgr_$check_volume_registration:
48631 ERROR_MESSAGE. cannot re-create >lv
48632
48633
48634 Stream: BOS Typewriter.
48635
48636 Time: System Intialization.
48637
48638 Meaning: When the system is bootloaded it checks the list
48639 of packs which were mounted during the last
48640 bootload to make sure that each one has a valid
48641 logical and physical volume registration. If the
48642 registration does not exist the registration
48643 files are reconstructed. These registration files
48644 reside in the directory >lv which is also remade
48645 if it was lost or did not exist.
48646
48647 This message indicates that there is a problem in
48648 re-creating >lv. Other error messages will follow
48649 and reregistration will fail.
48650
48651 Action: Contact the system programming staff.
48652
48653
48654
48655
48656
48657
48658
48659
48660
48661
48662
48663 volume_registration_mgr_$c -839- MR12.5 10/27/92^L
48664
48665
48666 volume_registration_mgr_.pl1
48667 volume_registration_mgr_$check_volume_registration:
48668 ERROR_MESSAGE. Cannot reregister lv LVNAME
48669
48670
48671 Stream: BOS Typewriter.
48672
48673 Time: System Intialization.
48674
48675 Meaning: When the system is bootloaded it checks the list
48676 of packs which were mounted during the last
48677 bootload to make sure that each one has a valid
48678 logical and physical volume registration.
48679
48680 The system was unable to append a branch for
48681 >lv>lv.LVNAME. The logical volume will have to be
48682 re-registered manually.
48683
48684 Action: Use the add_vol_registration command to
48685 re-register the volume manually.
48686
48687
48688
48689 volume_registration_mgr_.pl1
48690 volume_registration_mgr_$check_volume_registration:
48691 ERROR_MESSAGE. Cannot reregister pv PVNAME
48692
48693
48694 Stream: BOS Typewriter.
48695
48696 Time: System Intialization.
48697
48698 Meaning: When the system is bootloaded it checks the list
48699 of packs which were mounted during the last
48700 bootload to make sure that each one has a valid
48701 logical and physical volume registration.
48702
48703 The system was unable to re-register the physical
48704 volume PVNAME because its logical volume entry
48705 could not be located in the old disk_table and its
48706 physical volume registration file could not be
48707 found. The volume will have to be re-registered
48708 manually.
48709
48710 Action: If PVNAME is garbage ignore this message.
48711 Otherwise use add_vol_registration to re-register
48712 the volume.
48713
48714
48715
48716
48717
48718
48719
48720
48721 volume_registration_mgr_$c -840- MR12.5 10/27/92^L
48722
48723
48724 volume_registration_mgr_.pl1
48725 volume_registration_mgr_$check_volume_registration:
48726 ERROR_MESSAGE. Cant add name lvid.UNIQUE to
48727 lv.LVNAME
48728
48729
48730 Stream: BOS Typewriter.
48731
48732 Time: System Intialization.
48733
48734 Meaning: When the system is bootloaded it checks the list
48735 of packs which were mounted during the last
48736 bootload to make sure that each one has a valid
48737 logical and physical volume registration. The
48738 registration file for LVNAME did not have the
48739 additional name constructed from the volume unique
48740 ID and an error was discovered trying to add it.
48741 If this name is on another segment confusion will
48742 result.
48743
48744 Action: Contact the system programming staff. Enter admin
48745 mode and do a "list >lv>**" command.
48746
48747
48748
48749 volume_registration_mgr_.pl1
48750 volume_registration_mgr_$check_volume_registration:
48751 ERROR_MESSAGE. Cant add name pv.PVNAME to LVNAME
48752
48753
48754 Stream: BOS Typewriter.
48755
48756 Time: System Intialization.
48757
48758 Meaning: When the system is bootloaded it checks the list
48759 of packs which were mounted during the last
48760 bootload to make sure that each one has a valid
48761 logical and physical volume registration.
48762
48763 An error occurred adding the name pv.PVNAME to
48764 >lv>lv.LVNAME. If this name is missing or on
48765 another segment confusion will result.
48766
48767 Action: Contact the system programming staff. Enter admin
48768 mode and do a "list >lv>**" command.
48769
48770
48771
48772
48773
48774
48775
48776
48777
48778
48779 volume_registration_mgr_$c -841- MR12.5 10/27/92^L
48780
48781
48782 volume_registration_mgr_.pl1
48783 volume_registration_mgr_$check_volume_registration:
48784 ERROR_MESSAGE. Cant add name pvid.UNIQUE to
48785 LVNAME
48786
48787
48788 Stream: BOS Typewriter.
48789
48790 Time: System Intialization.
48791
48792 Meaning: When the system is bootloaded it checks the list
48793 of packs which were mounted during the last
48794 bootload to make sure that each one has a valid
48795 logical and physical volume registration. An
48796 error occurred adding the name pvid.UNIQUE to
48797 >lv>lv.LVNAME. If this name is missing or is on
48798 another segment confusion will result.
48799
48800 Action: Contact the system programming staff. Enter admin
48801 mode and do a "list >lv>**" command.
48802
48803
48804
48805 volume_registration_mgr_.pl1
48806 volume_registration_mgr_$check_volume_registration:
48807 ERROR_MESSAGE. Putting LV dir on RPV
48808
48809
48810 Stream: BOS Typewriter.
48811
48812 Time: System Intialization.
48813
48814 Meaning: When the system is bootloaded it checks the list
48815 of packs which were mounted during the last
48816 bootload to make sure that each one has a valid
48817 logical and physical volume registration. While
48818 re-creating >lv the system attempted to set the
48819 directory flag which means "RPV only" and failed
48820 to do so.
48821
48822 Action: Contact the system programming staff.
48823
48824
48825
48826
48827
48828
48829
48830
48831
48832
48833
48834
48835
48836
48837 volume_registration_mgr_$c -842- MR12.5 10/27/92^L
48838
48839
48840 volume_registration_mgr_.pl1
48841 volume_registration_mgr_$check_volume_registration:
48842 Registration for PVNAME was different from
48843 disk_table
48844
48845
48846 Stream: BOS Typewriter.
48847
48848 Time: System Intialization.
48849
48850 Meaning: When the system is bootloaded it checks the list
48851 of packs which were mounted during the last
48852 bootload to make sure that each one has a valid
48853 logical and physical volume registration. The
48854 physical volume ID or model number of PVNAME was
48855 wrong in the registration files and was corrected.
48856
48857 Action: Contact the system administrator.
48858
48859
48860
48861 volume_registration_mgr_.pl1
48862 volume_registration_mgr_$check_volume_registration:
48863 Reregistered pv PVNAME pvid WWWW in lv LVNAME
48864
48865
48866 Stream: BOS Typewriter.
48867
48868 Time: System Intialization.
48869
48870 Meaning: When the system is bootloaded it checks the list
48871 of packs which were mounted during the last
48872 bootload to make sure that each one has a valid
48873 logical and physical volume registration.
48874 Registration for PVNAME was added to the
48875 registration file for LVNAME.
48876
48877 This message is always produced for the root
48878 physical volume rpv during a cold boot of the
48879 Multics hierarchy.
48880
48881 Action: Use the list_vol_registration command to check the
48882 registration. If necessary correct it with
48883 change_vol_registration.
48884
48885
48886
48887
48888
48889
48890
48891
48892
48893
48894
48895 volume_registration_mgr_$c -843- MR12.5 10/27/92^L
48896
48897
48898 volume_registration_mgr_.pl1
48899 volume_registration_mgr_$check_volume_registration:
48900 Reregistered TYPE lv LVNAME lvid WWWW
48901
48902
48903 Stream: BOS Typewriter.
48904
48905 Time: System Intialization.
48906
48907 Meaning: When the system is bootloaded it checks the list
48908 of packs which were mounted during the last
48909 bootload to make sure that each one has a valid
48910 logical and physical volume registration. The
48911 registration file for LVNAME did not exist and was
48912 reconstructed.
48913
48914 This message is always produced for the root
48915 logical volume during a cold boot of the Multics
48916 hierarchy.
48917
48918 Action: Use the list_vol_registration command to list the
48919 registration and check it against the re-created
48920 copy. Correct it with change_vol_registration if
48921 necessary.
48922
48923
48924
48925 volume_registration_mgr_.pl1
48926 volume_registration_mgr_$delete_lvr: Could not
48927 remove PV name | PVID | LV name | LVID database
48928 link. GROUP_ID ERROR_MESSAGE
48929
48930
48931 Stream: BOS Typewriter.
48932
48933 Time: While system is running.
48934
48935 Meaning: An unexpected state prevented the program from
48936 removing the database links associated with an LV
48937 just deleted. The links in >lv should be
48938 removed by hand using Ring_1_Repair.
48939
48940 Action: Contact the system programming staff.
48941
48942
48943
48944
48945
48946
48947
48948
48949
48950
48951
48952
48953 volume_registration_mgr_$d -844- MR12.5 10/27/92^L
48954
48955
48956 volume_registration_mgr_.pl1
48957 volume_registration_mgr_$delete_lvr: Deleted LV
48958 "LVNAME". GROUP_ID
48959
48960
48961 Stream: Logged in SYSERR log.
48962
48963 Time: While system is running.
48964
48965 Meaning: The registration for the spcified logical volume
48966 has been removed.
48967
48968 Action: No operator action is required.
48969
48970
48971
48972 volume_registration_mgr_.pl1
48973 volume_registration_mgr_$delete_lvr: Deleted PV
48974 "PVNAME" from LV "LVNAME". GROUP_ID
48975
48976
48977 Stream: Logged in SYSERR log.
48978
48979 Time: While system is running.
48980
48981 Meaning: The registration for the specified physical volume
48982 was removed while removing the entire logical
48983 volume registration.
48984
48985 Action: No operator action is required.
48986
48987
48988
48989 volume_registration_mgr_.pl1
48990 volume_registration_mgr_$delete_lvr: Unable to
48991 delete MDCS "LVNAME.mdcs". GROUP_ID
48992 ERROR_MESSAGE
48993
48994
48995 Stream: BOS Typewriter.
48996
48997 Time: While system is running.
48998
48999 Meaning: After deleting the registration for a logical
49000 volume the module was unable to delete the
49001 corresponding master directory control database
49002 indicated in the message.
49003
49004 Action: Contact the system programming staff.
49005
49006
49007
49008
49009
49010
49011 volume_registration_mgr_$d -845- MR12.5 10/27/92^L
49012
49013
49014 volume_registration_mgr_.pl1
49015 volume_registration_mgr_$delete_pvr: Could not
49016 remove PV name | PVID database link. GROUP_ID
49017 ERROR_MESSAGE
49018
49019
49020 Stream: BOS Typewriter.
49021
49022 Time: While system is running.
49023
49024 Meaning: An unexpected state prevented the removal of
49025 database links associated with a PV registration
49026 that was just deleted. The links should be
49027 deleted by hand using Ring_1_Repair.
49028
49029 Action: Contact the system programming staff.
49030
49031
49032
49033 volume_registration_mgr_.pl1
49034 volume_registration_mgr_$delete_pvr: Deleted PV
49035 "PVNAME" from LV "LVNAME". GROUP_ID
49036
49037
49038 Stream: Logged in SYSERR log.
49039
49040 Time: While system is running.
49041
49042 Meaning: The registration fo the specified PV has been
49043 deleted.
49044
49045 Action: No operator action is required.
49046
49047
49048
49049 volume_registration_mgr_.pl1
49050 volume_registration_mgr_$delete_pvr: PV entry
49051 missing from database "pv.PVNAME". GROUP_ID
49052
49053
49054 Stream: BOS Typewriter.
49055
49056 Time: While system is running.
49057
49058 Meaning: This indicates a logic error in the supervisor or
49059 CPU or memory hardware problems. The entry for
49060 the specified PV could not be located in the
49061 database segment although its name appears on the
49062 segment entry.
49063
49064 Action: Contact the system programming staff.
49065
49066
49067
49068
49069 volume_registration_mgr_$d -846- MR12.5 10/27/92^L
49070
49071
49072 volume_registration_mgr_.pl1
49073 volume_registration_mgr_$delete_pvr: Trimming
49074 registration. GROUP_ID ERROR_MESSAGE
49075
49076
49077 Stream: BOS Typewriter.
49078
49079 Time: While system is running.
49080
49081 Meaning: An unexpected state prevented the trimming of a
49082 registration database segment. This will not
49083 hinder subsystem performance.
49084
49085 Action: Contact the system programming staff.
49086
49087
49088
49089 volume_registration_mgr_.pl1
49090 volume_registration_mgr_$delete_pvr: Unable to
49091 replace database name "pv.PVNAME". GROUP_ID
49092 ERROR_MESSAGE
49093
49094
49095 Stream: BOS Typewriter.
49096
49097 Time: While system is running.
49098
49099 Meaning: This indicates a logic error in the supervisor or
49100 CPU or memory hardware problems. While deleting
49101 the registration for the specified PV an error
49102 occurred. The program attempts to undo any
49103 changes to "leave things as they were." The
49104 attempt to put back the database segment name as
49105 indicated failed.
49106
49107 Action: Contact the system programming staff.
49108
49109
49110
49111
49112
49113
49114
49115
49116
49117
49118
49119
49120
49121
49122
49123
49124
49125
49126
49127 volume_registration_mgr_$d -847- MR12.5 10/27/92^L
49128
49129
49130 volume_registration_mgr_.pl1
49131 volume_registration_mgr_$ENTRY: Attempting to get
49132 second temp segment. GROUP_ID
49133
49134
49135 Stream: BOS Typewriter.
49136
49137 Time: While system is running.
49138
49139 Meaning: This indicates a logic error in the supervisor or
49140 CPU or memory hardware problems. All entrypoints
49141 to volume_registration_mgr_ require at most one
49142 temporary segment.
49143
49144 Action: Contact the system programming staff.
49145
49146
49147
49148 volume_registration_mgr_.pl1
49149 volume_registration_mgr_$ENTRY: Database -
49150 lvid.UNIQUE | lv.LVNAME | pvid.UNIQUE |
49151 pv.PVNAME. GROUP_ID Segment already known to
49152 process.
49153
49154
49155 Stream: BOS Typewriter.
49156
49157 Time: While system is running.
49158
49159 Meaning: This indicates a logic error in the supervisor or
49160 CPU or memory hardware problems. The inner ring
49161 module always trerminates references to the
49162 database segments upon return to its caller. It
49163 found the specified segment already initiated upon
49164 entry to the specified routine.
49165
49166 Action: Contact the system programming staff.
49167
49168
49169
49170
49171
49172
49173
49174
49175
49176
49177
49178
49179
49180
49181
49182
49183
49184
49185 volume_registration_mgr_$E -848- MR12.5 10/27/92^L
49186
49187
49188 volume_registration_mgr_.pl1
49189 volume_registration_mgr_$ENTRY: Unable to release
49190 temp segment. GROUP_ID ERROR_MESSAGE
49191
49192
49193 Stream: BOS Typewriter.
49194
49195 Time: While system is running.
49196
49197 Meaning: This indicates a logic error in the supervisor or
49198 CPU or memory hardware problems. Some unexpected
49199 state is preventing the module from releasing its
49200 temporary segment.
49201
49202 Action: Contact the system programming staff.
49203
49204
49205
49206 volume_registration_mgr_.pl1
49207 volume_registration_mgr_$ENTRY: Unable to
49208 terminate database reference. GROUP_ID
49209 ERROR_MESSAGE
49210
49211
49212 Stream: BOS Typewriter.
49213
49214 Time: While system is running.
49215
49216 Meaning: This indicates a logic error in the supervisor or
49217 CPU or memory hardware problems. Some unexpected
49218 state is preventing the module from terminating
49219 reference to a database segment.
49220
49221 Action: Contact the system programming staff.
49222
49223
49224
49225 volume_registration_mgr_.pl1
49226 volume_registration_mgr_$ENTRY: Unexpected error
49227 occurred. Database may be in an inconsistant
49228 state. GROUP_ID
49229
49230
49231 Stream: BOS Typewriter.
49232
49233 Time: While system is running.
49234
49235 Meaning: This indicates a logic error in the supervisor or
49236 CPU or memory hardware problems. Some unexpected
49237 condition was signalled while the module was
49238 executing.
49239
49240 Action: Contact the system programming staff.
49241
49242
49243 volume_registration_mgr_$E -849- MR12.5 10/27/92^L
49244
49245
49246 volume_registration_mgr_.pl1
49247 volume_registration_mgr_$find: PV entry missing
49248 from "pv.PVNAME". GROUP_ID
49249
49250
49251 Stream: BOS Typewriter.
49252
49253 Time: While system is running.
49254
49255 Meaning: This indicates a logic error in the supervisor or
49256 CPU or memory hardware problems. The entry for
49257 the specified PV could not be found in the
49258 registration database segment although the name
49259 appears on the segment's entry.
49260
49261 Action: Contact the system programming staff.
49262
49263
49264
49265 volume_registration_mgr_.pl1
49266 volume_registration_mgr_$find_volname: PV entry
49267 not found in database "pvid.UNIQUE". GROUP_ID
49268
49269
49270 Stream: BOS Typewriter.
49271
49272 Time: While system is running.
49273
49274 Meaning: This indicates a logic error in the supervisor or
49275 CPU or memory hardware problems. The entry for
49276 the specified PV could not be found in the
49277 registration database segment although the name
49278 appears on the segment's entry.
49279
49280 Action: Contact the system programming staff.
49281
49282
49283
49284 volume_registration_mgr_.pl1
49285 volume_registration_mgr_$get_access: ACS not
49286 segment - "PATH". GROUP_ID
49287
49288
49289 Stream: BOS Typewriter.
49290
49291 Time: While system is running.
49292
49293 Meaning: The ACS indicated in the logical volume
49294 registration database is not a segment. The
49295 database entry should be corrected using
49296 "change_volume_registration".
49297
49298 Action: Contact the system administrator.
49299
49300
49301 volume_registration_mgr_$g -850- MR12.5 10/27/92^L
49302
49303
49304 volume_registration_mgr_.pl1
49305 volume_registration_mgr_$get_access: Bad ACS path
49306 in database "lv.LVNAME". GROUP_ID ERROR_MESSAGE
49307
49308
49309 Stream: BOS Typewriter.
49310
49311 Time: While system is running.
49312
49313 Meaning: This indicates a logic error in the supervisor or
49314 CPU or memory hardware problems. The ACS pathname
49315 entry in the LVNAME database is illegal. This
49316 should not happen normally because the ring-1
49317 primitives check all paths before entering them
49318 into the database.
49319
49320 Action: Contact the system programming staff.
49321
49322
49323
49324 volume_registration_mgr_.pl1
49325 volume_registration_mgr_$pvname_info: PV entry
49326 not found in database "pv.PVNAME". GROUP_ID
49327
49328
49329 Stream: BOS Typewriter.
49330
49331 Time: While system is running.
49332
49333 Meaning: This indicates a logic error in the supervisor or
49334 CPU or memory hardware problems. The entry for
49335 the specified PV could not be found in the
49336 registration database segment although the name
49337 appears on the segment's entry.
49338
49339 Action: Contact the system programming staff.
49340
49341
49342
49343
49344
49345
49346
49347
49348
49349
49350
49351
49352
49353
49354
49355
49356
49357
49358
49359 volume_registration_mgr_$p -851- MR12.5 10/27/92^L
49360
49361
49362 volume_registration_mgr_.pl1
49363 volume_registration_mgr_$read_pvr: PV entry
49364 missing from database "pv.PVNAME". GROUP_ID
49365
49366
49367 Stream: BOS Typewriter.
49368
49369 Time: While system is running.
49370
49371 Meaning: This indicates a logic error in the supervisor or
49372 CPU or memory hardware problems. The entry for
49373 the specified PV could not be found in the
49374 registration database segment although the name
49375 appears on the segment's entry.
49376
49377 Action: Contact the system programming staff.
49378
49379
49380
49381 vrm_lock_.pl1
49382 vrm_lock_$lock: LOCK ERROR MESSAGE.
49383
49384
49385 Stream: Logged in SYSERR log.
49386
49387 Time: While system is running.
49388
49389 Meaning: A logical volume registration operation failed
49390 because of a problem with the vrm control lock.
49391
49392 Action: No operator action is required.
49393
49394
49395
49396 vrm_lock_.pl1
49397 vrm_lock_$unlock: LOCK ERROR MESSAGE.
49398
49399
49400 Stream: Logged in SYSERR log.
49401
49402 Time: While system is running.
49403
49404 Meaning: At the completion ofa logical volume registratin
49405 operation some error occured unlocking the vrm
49406 control lock.
49407
49408 Action: No operator action is required.
49409
49410
49411
49412
49413
49414
49415
49416
49417 vrm_lock_$unlock -852- MR12.5 10/27/92^L
49418
49419
49420 vrm_lock_.pl1
49421 vrm_lock_$vrm_data_init: Unable to create
49422 PATHNAME. REASON.
49423
49424
49425 Stream: BOS Typewriter.
49426
49427 Time: System Intialization.
49428
49429 Meaning: Logical volume registration control vrm was
49430 unable to create the segment PATHNAME to be used
49431 for the vrm control lock for the REASON given.
49432 Subsequent logical volume registration control
49433 operations may fail.
49434
49435 Action: No operator action is required.
49436
49437
49438
49439 vrm_lock_.pl1
49440 vrm_lock_$vrm_data_init: Unable to reclassify
49441 PATHNAME. REASON.
49442
49443
49444 Stream: BOS Typewriter.
49445
49446 Time: System Intialization.
49447
49448 Meaning: Logical volume registration control was unable to
49449 reclassify the segment PATHNAME to its proper
49450 access class for the REASON given. This segment
49451 is to be used for the logical volume registration
49452 control lock. Subsequent logical volume
49453 registration control operations may fail.
49454
49455
49456
49457
49458
49459
49460
49461
49462
49463
49464
49465
49466
49467
49468
49469
49470
49471
49472
49473
49474
49475 vrm_lock_$vrm_data_init -853- MR12.5 10/27/92^L
49476
49477
49478 vrm_lock_.pl1
49479 vrm_lock_$vrm_data_init: Unable to truncate
49480 PATHNAME. REASON.
49481
49482
49483 Stream: BOS Typewriter.
49484
49485 Time: System Intialization.
49486
49487 Meaning: Logical volume registration control was unable to
49488 truncate the segment PATHNAME for the REASON
49489 given. This segment is to be used for the logical
49490 volume registration control lock. Subsequent
49491 logical volume registration control operations may
49492 fail.
49493
49494 Action: No operator action is required.
49495
49496
49497
49498 vrm_lock_.pl1
49499 vrm_lock_: Unable to initiate PATHNAME. REASON.
49500
49501
49502 Stream: Logged in SYSERR log.
49503
49504 Time: While system is running.
49505
49506 Meaning: Logical volume registration control vrm was
49507 unable to initiate PATHNAME which contains the
49508 vrm control lock because of REASON. The logical
49509 volume registration control operation requested
49510 was not performed.
49511
49512 Action: No operator action is required.
49513
49514
49515
49516 vtoc_interrupt.pl1
49517 vtoc_interrupt: bad core address
49518
49519
49520 Stream: BOS Typewriter Crashes system
49521
49522 Time: While system is running.
49523
49524 Meaning: The disk dim reported a main memory address to the
49525 VTOC manager which was not in the VTOC buffer
49526 segment or was not designating a legal buffer
49527 boundary. This indicates a logic error in the
49528 supervisor or CPU or memory hardware problems.
49529
49530 Action: Follow normal recovery procedures.
49531
49532
49533 vtoc_interrupt -854- MR12.5 10/27/92^L
49534
49535
49536 vtoc_interrupt.pl1
49537 vtoc_interrupt: Buffer not os at interrupt
49538
49539
49540 Stream: BOS Typewriter Crashes system
49541
49542 Time: While system is running.
49543
49544 Meaning: An I/O completion was received for a VTOC buffer
49545 which was apparently not undergoing I/O. This
49546 indicates a logic error in the supervisor or CPU
49547 or memory hardware problems.
49548
49549 Action: Follow normal recovery procedures.
49550
49551
49552
49553 vtoc_interrupt.pl1
49554 vtoc_interrupt: Write error on dskX_NN vtocx
49555 XXXXXX
49556
49557
49558 Stream: Logged in SYSERR log.
49559
49560 Time: While system is running.
49561
49562 Meaning: A bad I/O status was received by the VTOC manager
49563 for a write operation. The unwritten vtoce-part
49564 will remain in main memory until the next attempt
49565 is made to write it out or demount or shutdown
49566 time. Too many of these can cause the system to
49567 crash.
49568
49569 Action: No operator action is required.
49570
49571
49572
49573 vtoc_man.pl1
49574 vtoc_man: Attempt to write less than entire VTOCE
49575 to MODEL device.
49576
49577
49578 Stream: BOS Typewriter Crashes system
49579
49580 Time: While system is running.
49581
49582 Meaning: An attempt has been made to write less than the
49583 entire VTOCE to a device MODEL that only supports
49584 a 512_word sector. For these devices the entire
49585 192 word VTOCE must be written at one time. A
49586 likely software error n VTOC buffer management.
49587
49588 Action: Follow normal recovery procedures.
49589
49590
49591 vtoc_man -855- MR12.5 10/27/92^L
49592
49593
49594 vtoc_man.pl1
49595 vtoc_man: Buffer out-of-service during cleanup
49596
49597
49598 Stream: BOS Typewriter Crashes system
49599
49600 Time: When a volume is being demounted or during system
49601 shutdown.
49602
49603 Meaning: A likely software error in VTOC buffer management
49604 which caused an inconsistency in the VTOC buffer.
49605
49606 Action: Follow normal recovery procedures.
49607
49608
49609
49610 vtoc_man.pl1
49611 vtoc_man: buffer out-of-service on write
49612
49613
49614 Stream: BOS Typewriter Crashes system
49615
49616 Time: While system is running.
49617
49618 Meaning: A likely software problem has caused an
49619 inconsistency in the VTOC buffer.
49620
49621 Action: Follow normal recovery procedures.
49622
49623
49624
49625 vtoc_man.pl1
49626 vtoc_man: Hot buffer abandoned during cleanup
49627 vtocx XXXXX dskX_NNs
49628
49629
49630 Stream: Logged in SYSERR log.
49631
49632 Time: When a volume is being demounted or during system
49633 shutdown.
49634
49635 Meaning: An update to VTOCE XXXXX on dskX_NNs could not
49636 be completed due to I/O errors. The VTOCE may be
49637 inconsistent or damaged.
49638
49639 Action: The VTOCE should be examined by means of
49640 dump_vtoce the next time the volume is online.
49641 Any inconsistency can be corrected by a volume
49642 salvage.
49643
49644
49645
49646
49647
49648
49649 vtoc_man -856- MR12.5 10/27/92^L
49650
49651
49652 vtoc_man.pl1
49653 vtoc_man: Invalid free vtocx XXXXX on dskX_NNs
49654
49655
49656 Stream: Logged in SYSERR log.
49657
49658 Time: While system is running.
49659
49660 Meaning: A free VTOCE was allocated which has an invalid
49661 VTOCE index for the volume. This is indicative of
49662 damage to volume control structures. This damage
49663 can be corrected by a volume salvage.
49664
49665 Action: No operator action is required.
49666
49667
49668
49669 vtoc_man.pl1
49670 vtoc_man: Invalid write
49671
49672
49673 Stream: BOS Typewriter Crashes system
49674
49675 Time: While system is running.
49676
49677 Meaning: A likely software error in the calling sequence
49678 for output of a VTOCE.
49679
49680 Action: Follow normal recovery procedures.
49681
49682
49683
49684 vtoc_man.pl1
49685 vtoc_man: Out of buffers try number N
49686
49687
49688 Stream: BOS Typewriter.
49689
49690 Time: While system is running.
49691
49692 Meaning: There may be a disk problem which prevents the
49693 vtoc buffers from being written to disk or there
49694 may be a disk tuning problem. The system may
49695 crash within the next few minutes.
49696
49697 Action: Contact the system administrator.
49698
49699
49700
49701
49702
49703
49704
49705
49706
49707 vtoc_man -857- MR12.5 10/27/92^L
49708
49709
49710 vtoc_man.pl1
49711 vtoc_man: read reset of crawlout by
49712 PERSON.PROJECT.TAG for dskX_NNs vtocx XXXXXX
49713
49714
49715 Stream: Logged in SYSERR log.
49716
49717 Time: While system is running.
49718
49719 Meaning: The process of PERSON.PROJECT.TAG crawled out of
49720 ring-0 or terminated with the VTOC buffer lock
49721 held. A buffer was marked out-of-service for read
49722 to VTOCE XXXXX on dskX_NNs for which no I/O had
49723 been queued. The read I/O was abandoned.
49724
49725 Action: No operator action is required.
49726
49727
49728
49729 vtoc_man.pl1
49730 vtoc_man: UID ^= 0 in free VTOCE vtocx XXXXX
49731 dskX_NNs
49732
49733
49734 Stream: Logged in SYSERR log.
49735
49736 Time: While system is running.
49737
49738 Meaning: The contents of VTOCE XXXXX on dskX_NNs are
49739 incorrect as free VTOCEs should have a zero UID.
49740 The system attempts to find another free VTOCE.
49741 This may indicate damage to volume control
49742 structures. This damage can be corrected by a
49743 volume salvage.
49744
49745 Action: No operator action is required.
49746
49747
49748
49749
49750
49751
49752
49753
49754
49755
49756
49757
49758
49759
49760
49761
49762
49763
49764
49765 vtoc_man -858- MR12.5 10/27/92^L
49766
49767
49768 vtoc_man.pl1
49769 vtoc_man: Update in progress on crawlout by
49770 PERSON.PROJECT.TAG dskX_NNs
49771
49772
49773 Stream: Logged in SYSERR log.
49774
49775 Time: While system is running.
49776
49777 Meaning: The process of PERSON.PROJECT.TAG crawled out of
49778 ring-0 or terminated with the vtoc buffer lock
49779 held and an update in progress for a VTOCE on
49780 dskX_NNs. The VTOCE may be inconsistent. Any
49781 inconsistency can be corrected by a volume
49782 salvage.
49783
49784 Action: No operator action is required.
49785
49786
49787
49788 vtoc_man.pl1
49789 vtoc_man: Write I/O being retried by
49790 PERSON.PROJECT.TAG for dskX_NNs vtocx XXXXX
49791
49792
49793 Stream: Logged in SYSERR log.
49794
49795 Time: While system is running.
49796
49797 Meaning: A buffer previously marked as "hot" is being
49798 requeued for I/O.
49799
49800 Action: No operator action is required.
49801
49802
49803
49804 vtoc_man.pl1
49805 vtoc_man: write I/O recovered on crawlout by
49806 PERSON.PROJECT.TAG for dskX_NNs vtocx XXXXX
49807
49808
49809 Stream: Logged in SYSERR log.
49810
49811 Time: While system is running.
49812
49813 Meaning: The process of PERSON.PROJECT.TAG crawled out of
49814 ring-0 or terminated with the VTOC buffer lock
49815 held. A buffer was marked out-of-service for
49816 write to VTOCE XXXXX on dskX_NNs for which no
49817 I/O had been queued. The write I/O was requeued.
49818
49819 Action: No operator action is required.
49820
49821
49822
49823 vtoc_man -859- MR12.5 10/27/92^L
49824
49825
49826 vtoce_stock_man.pl1
49827 vtoce_stock_man: Attempt to deposit free vtocx
49828 YYYYYY on dskX_NN
49829
49830
49831 Stream: BOS Typewriter.
49832
49833 Time: While system is running.
49834
49835 Meaning: A VTOCE was returned to the free pool of VTOCEs on
49836 the device indicated but the VTOCE was already
49837 marked as free. This indicates possible device
49838 damage. This damage can be corrected by a
49839 physical volume salvage.
49840
49841 Action: Contact the system programming staff.
49842
49843
49844
49845 vtoce_stock_man.pl1
49846 vtoce_stock_man: Attempt to deposit invalid vtocx
49847 YYYYYY on dskX_NN
49848
49849
49850 Stream: BOS Typewriter.
49851
49852 Time: While system is running.
49853
49854 Meaning: There was an attempt to return a free VTOCE to the
49855 pool of free VTOCEs for the device indicated but
49856 the index of the VTOCE was not valid. This
49857 indicates possible damage to the device. Such
49858 damage can be corrected by a physical volume
49859 salvage.
49860
49861 Action: Contact the system programming staff.
49862
49863
49864
49865 vtoce_stock_man.pl1
49866 vtoce_stock_man: MYLOCK of VTOC Map for dskX_NN
49867
49868
49869 Stream: BOS Typewriter Crashes system
49870
49871 Time: While system is running.
49872
49873 Meaning: A process attempted to acquire a lock on the VTOC
49874 Map for the device indicated while already owning
49875 the lock. This is probably a software error.
49876
49877 Action: Follow normal recovery procedures.
49878
49879
49880
49881 vtoce_stock_man -860- MR12.5 10/27/92^L
49882
49883
49884 vtoce_stock_man.pl1
49885 vtoce_stock_man: PVTE and VTOCE stock
49886 out-of-synch on dskX_NN
49887
49888
49889 Stream: BOS Typewriter Crashes system
49890
49891 Time: While system is running.
49892
49893 Meaning: There is an inconsistency between the Physical
49894 Volume Table Entry and the VTOCE Stock for the
49895 device indicated. This is probably a software
49896 error.
49897
49898 Action: Follow normal recovery procedures.
49899
49900
49901
49902 vtoce_stock_man.pl1
49903 vtoce_stock_man: STACQ fails for VTOC Map lock on
49904 dskX_NN
49905
49906
49907 Stream: BOS Typewriter Crashes system
49908
49909 Time: While system is running.
49910
49911 Meaning: A process was unable to unlock the VTOC Map lock
49912 for the device indicated. This is probably a
49913 hardware failure either in the CPU or in main
49914 memory.
49915
49916 Action: Follow normal recovery procedures.
49917
49918
49919
49920 vtoce_stock_man.pl1
49921 vtoce_stock_man: VTOCE stock inconsistent on
49922 dskX_NN
49923
49924
49925 Stream: BOS Typewriter Crashes system
49926
49927 Time: While system is running.
49928
49929 Meaning: There is an internal inconsistency in the stock of
49930 free VTOCES on the device indicated. This is
49931 probably a software malfunction.
49932
49933 Action: Follow normal recovery procedures.
49934
49935
49936
49937
49938
49939 vtoce_stock_man -861- MR12.5 10/27/92^L
49940
49941
49942 wdx.pl1
49943 wdx: ERRORCODE Unable to send wakeup on master
49944 channel.
49945
49946
49947 Stream: BOS Typewriter.
49948
49949 Time: While system is running.
49950
49951 Meaning: The ring-1 logical volume mount software was
49952 unable to send a wakeup to the ring-4 software for
49953 the reason indicated. Some mount requests may
49954 have been lost.
49955
49956 Action: Contact the system administrator.
49957
49958
49959
49960 wire_proc.pl1
49961 wire_proc: lock not locked
49962
49963
49964 Stream: BOS Typewriter Crashes system
49965
49966 Time: While system is running.
49967
49968 Meaning: The lock on temp-wiring in the SST was found
49969 unlocked at the time an attempt was made to unlock
49970 it. The SST may be damaged. This indicates a
49971 logic error in the supervisor or CPU or memory
49972 hardware problems.
49973
49974 Action: Follow normal recovery procedures.
49975
49976
49977
49978
49979
49980
49981
49982
49983
49984
49985
49986
49987
49988
49989
49990
49991
49992
49993
49994
49995
49996
49997 wire_proc -862- MR12.5 10/27/92^L
49998
49999
50000 wire_proc.pl1
50001 wire_proc: too many temp wired segments.
50002
50003
50004 Stream: BOS Typewriter Crashes system
50005
50006 Time: While system is running.
50007
50008 Meaning: A request has been made to the supervisor to
50009 temp-wire an eighth hardcore segment. Only seven
50010 are allowed. Temp-wiring is used for supervisor
50011 programs not I/O buffers. This indicates a logic
50012 error in the supervisor or CPU or memory hardware
50013 problems.
50014
50015 Action: Follow normal recovery procedures. The Multics
50016 System Tape may be incorrect. If the problem
50017 persists try another MST.
50018
50019
50020
50021 wired_shutdown.pl1
50022 wired_shutdown: FFF fault during emergency
50023 shutdown
50024
50025
50026 Stream: BOS Typewriter Crashes system
50027
50028 Time: Emergency shutdown
50029
50030 Meaning: An unexpected fault has occured during emergency
50031 shutdown. Emergency shutdown cannot complete.
50032
50033 Action: Get a dump for system programmers. If an disk
50034 dump was taken of the preceding crash get a dump
50035 to paper via the bce dump facility. Re-attempt
50036 ESD as many times as necessary.
50037
50038
50039
50040 x25_mpx.pl1
50041 x25_mpxCHN: Call Confirm in state STATE.
50042
50043
50044 Stream: Logged in SYSERR log.
50045
50046 Time: While system is running.
50047
50048 Meaning: An unexpected Call Confirm packet was received.
50049 The call is cleared.
50050
50051 Action: Contact the system programming staff.
50052
50053
50054
50055 x25_mpxCHN -863- MR12.5 10/27/92^L
50056
50057
50058 x25_mpx.pl1
50059 x25_mpxCHN: Clear Confirm in state STATE.
50060
50061
50062 Stream: Logged in SYSERR log.
50063
50064 Time: While system is running.
50065
50066 Meaning: An unexpected Clear Confirm packet has been
50067 received. The call is cleared.
50068
50069 Action: Contact the system programming staff.
50070
50071
50072
50073 x25_mpx.pl1
50074 x25_mpxCHN: Clear Indication CAUSE/DIAGNOSTIC.
50075
50076
50077 Stream: Logged in SYSERR log.
50078
50079 Time: While system is running.
50080
50081 Meaning: A Clear Indication with non-zero cause or
50082 diagnostic fields has been received. The call is
50083 cleared.
50084
50085 Action: No operator action is required.
50086
50087
50088
50089 x25_mpx.pl1
50090 x25_mpxCHN: Data packet received in state
50091 STATE.
50092
50093
50094 Stream: Logged in SYSERR log.
50095
50096 Time: While system is running.
50097
50098 Meaning: An unexpected data packet was received. The call
50099 is cleared.
50100
50101 Action: Contact the system programming staff.
50102
50103
50104
50105
50106
50107
50108
50109
50110
50111
50112
50113 x25_mpxCHN -864- MR12.5 10/27/92^L
50114
50115
50116 x25_mpx.pl1
50117 x25_mpxCHN: Diagnostic type TYPE.
50118
50119
50120 Stream: Logged in SYSERR log.
50121
50122 Time: While system is running.
50123
50124 Meaning: A diagnostic packet of type TYPE was received.
50125 Normal processing continues.
50126
50127 Action: Contact the system programming staff.
50128
50129
50130
50131 x25_mpx.pl1
50132 x25_mpxCHN: Error CODE from write.
50133
50134
50135 Stream: Logged in SYSERR log.
50136
50137 Time: While system is running.
50138
50139 Meaning: An error occurred writing to the LAP channel. The
50140 LAP channel will be disconnected.
50141
50142 Action: Contact the system programming staff.
50143
50144
50145
50146 lap_simplex.pl1
50147 x25_mpxCHN: Error from write of XXX chars.
50148 ERROR
50149
50150
50151 Stream: Logged in SYSERR log.
50152
50153 Time: While system is running.
50154
50155 Meaning: The ERROR occurred writing XXX characters to the
50156 LAP channel. The LAP channel will be
50157 disconnected.
50158
50159 Action: Contact the system programming staff.
50160
50161
50162
50163
50164
50165
50166
50167
50168
50169
50170
50171 x25_mpxCHN -865- MR12.5 10/27/92^L
50172
50173
50174 x25_mpx.pl1
50175 x25_mpxCHN: Failure Link state: STATE
50176 Current Action: FUNCTION in ESTATE Primary
50177 state: PSTATE Secondary state: SSTATE.
50178
50179
50180 Stream: Logged in SYSERR log.
50181
50182 Time: While system is running.
50183
50184 Meaning: Normal request to crash the line when the link has
50185 been disconnected by the FNP. STATE is the main
50186 state of the link. FUNCTION is the last function
50187 the link processed. The ESTATE is the execution
50188 state of the last function. PSTATE and SSTATE are
50189 the link up substate.
50190
50191 Action: Contact the system programming staff.
50192
50193
50194
50195 x25_mpx.pl1
50196 x25_mpxCHN: Invalid channel number LCN.
50197
50198
50199 Stream: Logged in SYSERR log.
50200
50201 Time: While system is running.
50202
50203 Meaning: An X.25 packet with an invalid logical channel
50204 group number or logical channel number has been
50205 received. The packet is ignored.
50206
50207 Action: Contact the system programming staff.
50208
50209
50210
50211 x25_mpx.pl1
50212 x25_mpxCHN: Invalid packet type TYPE on LC 0.
50213
50214
50215 Stream: Logged in SYSERR log.
50216
50217 Time: While system is running.
50218
50219 Meaning: An invalid packet of type TYPE was received on
50220 logical channel zero. The packet will be ignored.
50221
50222 Action: Contact the system programming staff.
50223
50224
50225
50226
50227
50228
50229 x25_mpxCHN -866- MR12.5 10/27/92^L
50230
50231
50232 x25_mpx.pl1
50233 x25_mpxCHN: Invalid X.29 command CMD.
50234
50235
50236 Stream: Logged in SYSERR log.
50237
50238 Time: While system is running.
50239
50240 Meaning: An invalid X.29 command was received. An error
50241 indication is returned to the sender.
50242
50243 Action: Contact the system programming staff.
50244
50245
50246
50247 x25_mpx.pl1
50248 x25_mpxCHN: Link disconnected due to
50249 mis-matched frame sizes. CMDR/FRMR frame: FRAME.
50250
50251
50252 Stream: Logged in SYSERR log.
50253
50254 Time: While system is running.
50255
50256 Meaning: The FNP has received a command reject LAPB or
50257 frame reject LAP which specified a reason of
50258 "wide frame" on channel CHN. The actual level 2
50259 command is FRAME. This means the frame received
50260 by the other end was too long. Instead of looping
50261 continuously trying to send this frame the link
50262 will be disconnected. The maximum frame size in
50263 the Multics TTF for this link should be checked
50264 against the size expected by the other end of the
50265 link and corrected.
50266
50267 Action: Contact the system programming staff.
50268
50269
50270
50271
50272
50273
50274
50275
50276
50277
50278
50279
50280
50281
50282
50283
50284
50285
50286
50287 x25_mpxCHN -867- MR12.5 10/27/92^L
50288
50289
50290 x25_mpx.pl1
50291 x25_mpxCHN: No buffers available.
50292
50293
50294 Stream: Logged in SYSERR log.
50295
50296 Time: While system is running.
50297
50298 Meaning: x25_mpx was unable to allocate a buffer for a
50299 protocol packet. This indicates a severe space
50300 problem in tty_buf. The multiplexer will sends
50301 itself a "hangup" order after freeing any space it
50302 has for protocol packets in tty_buf. If this
50303 multiplexer is not the cause of the problem then
50304 the system is likely to crash soon.
50305
50306 Action: Contact the system programming staff.
50307
50308
50309
50310 x25_mpx.pl1
50311 x25_mpxCHN: Packet INOUT: PACKET
50312
50313
50314 Stream: Logged in SYSERR log.
50315
50316 Time: While system is running.
50317
50318 Meaning: A packet has been received or sent and is logged.
50319 This occurs when the packet tracing facility is
50320 turned on. INOUT is the direction and PACKET is
50321 the packet octets dumped in hexadecimal.
50322
50323 Action: No operator action is required.
50324
50325
50326
50327 x25_mpx.pl1
50328 x25_mpxCHN: Packet too short.
50329
50330
50331 Stream: Logged in SYSERR log.
50332
50333 Time: While system is running.
50334
50335 Meaning: A packet less then 3 characters long was received.
50336
50337 Action: Contact the system programming staff.
50338
50339
50340
50341
50342
50343
50344
50345 x25_mpxCHN -868- MR12.5 10/27/92^L
50346
50347
50348 x25_mpx.pl1
50349 x25_mpxCHN: Received REJ packet.
50350
50351
50352 Stream: Logged in SYSERR log.
50353
50354 Time: While system is running.
50355
50356 Meaning: An X.25 REJ packet was received. Multics does not
50357 support this feature. The virtual circuit is
50358 reset.
50359
50360 Action: Contact the system programming staff.
50361
50362
50363
50364 x25_mpx.pl1
50365 x25_mpxCHN: Reset Confirm in state STATE.
50366
50367
50368 Stream: Logged in SYSERR log.
50369
50370 Time: While system is running.
50371
50372 Meaning: An unexpected Reset Confirm packet has been
50373 received. The call is reset.
50374
50375 Action: Contact the system programming staff.
50376
50377
50378
50379 x25_mpx.pl1
50380 x25_mpxCHN: Reset received CAUSE/DIAGNOSTIC.
50381
50382
50383 Stream: Logged in SYSERR log.
50384
50385 Time: While system is running.
50386
50387 Meaning: A RESET REQUEST packet has been received.
50388
50389 Action: No operator action is required.
50390
50391
50392
50393
50394
50395
50396
50397
50398
50399
50400
50401
50402
50403 x25_mpxCHN -869- MR12.5 10/27/92^L
50404
50405
50406 x25_mpx.pl1
50407 x25_mpxCHN: Sequence error PS = N VR = N.
50408
50409
50410 Stream: Logged in SYSERR log.
50411
50412 Time: While system is running.
50413
50414 Meaning: An X.25 packet was received with an incorrect
50415 value for PS. The logical channel is reset.
50416
50417 Action: Contact the system programming staff.
50418
50419
50420
50421 x25_mpx.pl1
50422 x25_mpxCHN: Sequence error: PR = N is not
50423 between previous PR = N and VS = N.
50424
50425
50426 Stream: Logged in SYSERR log.
50427
50428 Time: While system is running.
50429
50430 Meaning: An X.25 packet was received with an incorrect
50431 value for PR. The logical channel is reset.
50432
50433 Action: Contact the system programming staff.
50434
50435
50436
50437 x25_mpx.pl1
50438 x25_mpxCHN: Unexpected Interrupt Confirm.
50439
50440
50441 Stream: Logged in SYSERR log.
50442
50443 Time: While system is running.
50444
50445 Meaning: An unexpected Interrupt Confirm packet has been
50446 received. The call is reset.
50447
50448 Action: Contact the system programming staff.
50449
50450
50451
50452
50453
50454
50455
50456
50457
50458
50459
50460
50461 x25_mpxCHN -870- MR12.5 10/27/92^L
50462
50463
50464 x25_mpx.pl1
50465 x25_mpxCHN: Unexpected interrupt TYPE DATA
50466 received.
50467
50468
50469 Stream: Logged in SYSERR log.
50470
50471 Time: While system is running.
50472
50473 Meaning: An unexpected MCM interrupt was processed.
50474
50475 Action: Contact the system programming staff.
50476
50477
50478
50479 x25_mpx.pl1
50480 x25_mpxCHN: Unexpected packet type TYPE on idle
50481 VC.
50482
50483
50484 Stream: Logged in SYSERR log.
50485
50486 Time: While system is running.
50487
50488 Meaning: An unexpected packet has been received on an idle
50489 channel. The channel is cleared.
50490
50491 Action: Contact the system programming staff.
50492
50493
50494
50495 x25_mpx.pl1
50496 x25_mpxCHN: Unexpected packet type TYPE.
50497
50498
50499 Stream: Logged in SYSERR log.
50500
50501 Time: While system is running.
50502
50503 Meaning: An unexpected packet has been received. The
50504 packet is ignored.
50505
50506 Action: Contact the system programming staff.
50507
50508
50509
50510
50511
50512
50513
50514
50515
50516
50517
50518
50519 x25_mpxCHN -871- MR12.5 10/27/92^L
50520
50521
50522 x25_mpx.pl1
50523 x25_mpxCHN: Unrecognized general format ID
50524 GFID.
50525
50526
50527 Stream: Logged in SYSERR log.
50528
50529 Time: While system is running.
50530
50531 Meaning: A packet with a bad format ID was received. The
50532 packet will be ignored.
50533
50534 Action: Contact the system programming staff.
50535
50536
50537
50538 x25_mpx.pl1
50539 x25_mpxCHN: X.29 ERROR CODE/REASON.
50540
50541
50542 Stream: Logged in SYSERR log.
50543
50544 Time: While system is running.
50545
50546 Meaning: An X.29 ERROR packet with error code CODE and
50547 reason REASON was received. The packet is
50548 ignored.
50549
50550 Action: Contact the system programming staff.
50551
50552
50553
50554 x25_mpx.pl1
50555 x25_mpxCHN/LC: Call Request in state STATE.
50556
50557
50558 Stream: Logged in SYSERR log.
50559
50560 Time: While system is running.
50561
50562 Meaning: An unexpected Call Request has been received. The
50563 call is cleared.
50564
50565
50566
50567
50568
50569
50570
50571
50572
50573
50574
50575
50576
50577 x25_mpxCHN/LC -872- MR12.5 10/27/92^L
50578
50579
50580 x25_mpx.pl1
50581 x25_mpxCHN/LC: Clear Indication
50582 CAUSE/DIAGNOSTIC in idle VC.
50583
50584
50585 Stream: Logged in SYSERR log.
50586
50587 Time: While system is running.
50588
50589 Meaning: A Clear Indication has been received on a channel
50590 with no call in progress. A Clear Confirm is
50591 returned.
50592
50593 Action: No operator action is required.
50594
50595
50596
50597 x25_mpx.pl1
50598 x25_mpxCHN/LC: No listening channels.
50599
50600
50601 Stream: Logged in SYSERR log.
50602
50603 Time: While system is running.
50604
50605 Meaning: There were no listening channels available for a
50606 network call. The call is refused.
50607
50608 Action: Contact the system programming staff.
50609
50610
50611
50612 x25_mpx.pl1
50613 x25_mpxCHN/LC: Time out in state STATE.
50614
50615
50616 Stream: Logged in SYSERR log.
50617
50618 Time: While system is running.
50619
50620 Meaning: The network did not respond to a call reset or
50621 clear request. The call will be cleared.
50622
50623 Action: Contact the system programming staff.
50624
50625
50626
50627
50628
50629
50630
50631
50632
50633
50634
50635 x25_mpxCHN/LC -873- MR12.5 10/27/92^L