1
2
3
4
5
6
7
8
9
10
11
12 MULTICS MR12.7 ERROR MESSAGE DOCUMENTATION
13
14 February 17, 2020^L
15
16
17 INTRODUCTION
18
19 This document has been prepared automatically from the
20 system source by Multics Software Support. Every effort has been
21 made to supply documentation for each and every message that
22 could appear either on the system console, or in the system logs.
23 However, some of the system messages are not provided in this
24 document due to the messages developed prior to the development
25 of the error messages document, or omitted in error. The
26 following is a list of modules that are known to be missing from
27 this document:
28
29
30 as_access_audit_.pl1 monitor_cache.pl1
31 as_any_other_handler_.pl1 mos_edac_summary.pl1
32 as_ibm3270_mpx_.pl1 mos_edac_summary.pl1
33 as_send_user_mail_.pl1 mpc_data_summary.pl1
34 as_send_user_message_.pl1 mseg_error_v3_.pl1
35 as_uncp_mpx_.pl1 mseg_error_v4_.pl1
36 as_vip7760_mpx_.pl1 multiplexer_mgr_.pl1
37 asr_com_channel_info_srvr_.pl1 pc_recover_sst.pl1
38 asum_error_.pl1 pdir_volume_manager_.pl1
39 bootload_fs_.pl1 poll_fnp.pl1
40 cancel_abs_request.pl1 poll_mpc.pl1
41 dir_dump.pl1 polled_vip_mpx.pl1
42 display_cpu_error.pl1 print_syserr_msg_.pl1
43 display_cpu_error.pl1 print_syserr_msg_.pl1
44 ec_shift_config_change_.pl1 protocol_mpx.pl1
45 emergency_shutdown.alm rcp_mount_timer_poll_.pl1
46 extract_msg_doc_.pl1 rcp_pre_claim_.pl1
47 find_rpv_subsystem.pl1 rcprm_verify_registries_.pl1
48 fnp_data_summary.pl1 read_disk_label.pl1
49 hc_device_acct_.pl1 salv_directory.pl1
50 hc_tune.pl1.pmac salv_err_msg.pl1
51 hc_tune.pl1.pmac salvager.pl1
52 heals_collect_data_.pl1 sc_admin_mode_.pl1
53 initial_error_handler.pl1 sys_log_.pl1
54 initial_error_handler.pl1 syserr.alm
55 install_ttt_.pl1 syserr_log_daemon.pl1
56 io_error_summary.pl1 tty_read.pl1
57 io_error_summary.pl1 uc_create_process_.pl1
58 io_reconfig.pl1 uc_create_process_check_.pl1
59 ioi_page_table.pl1 uc_dial_.pl1
60 iom_switches.pl1 uc_list_disconnected_procs_.pl1
61 level_error.pl1 uc_login_.pl1
62 list_abs_requests.pl1 uc_logout_.pl1
63 ls_request_server_.pl1 uc_ls_create_request_.pl1
64 mc_check_acs_.pl1 uc_ls_destroy_request_.pl1
65 mc_con_rec_.pl1 uc_ls_dial_request_.pl1
66 mc_wakeups_.pl1 uc_ls_disconnect_request_.pl1
67 mcs_timer_daemon.pl1 uc_ls_list_request_.pl1
68 mdc_check_mdcs_.pl1 uc_ls_logout_request_.pl1
69 monitor_cache.pl1 uc_ls_new_proc_request_.pl1
70
71
72 2 08/03/23 MR12.7^L
73
74
75 uc_ls_operator_request_.pl1 uc_setup_process_connect_.pl1
76 uc_ls_process_request_.pl1 uncp.pl1
77 uc_ls_rq_server_wakeup_.pl1 uncp_boot_interrupt.pl1
78 uc_ls_validate_request_.pl1 uncp_multiplexer.pl1
79 uc_proc_term_handler_.pl1 uncp_util.pl1
80 uc_send_ls_response_.pl1 up_cdt_.pl1
81 uc_set_pit_tty_info_.pl1 user_table_mgr_.pl1
82
83 EXPLANATION OF ERROR MESSAGES
84
85 For each message, an example of the text of the message is
86 provided, followed by four paragraphs: Severity, Time, Meaning,
87 and Action.
88
89 Message Example
90
91 The message example is a literal copy of the message, with
92 substitutable fields shown in all capitals. Each substitutable
93 field is described in the Meaning paragraph.
94
95 Output
96
97 The output field describes how the message is output. For
98 hardcore messages it shows the interpretation of the first
99 argument to SYSERR, which determines whether the system crashes,
100 sounds the beeper, etc. For answering service messages, it
101 describes the output stream and source.
102
103 Time
104
105 The time section describes the time when the message is
106 possible.
107
108 Meaning
109
110 The meaning paragraph describes the situation that prompted
111 the message and the probable cause of the situation. It then
112 describes the consequences of the situation. Substitutable
113 parameters in the message example are explained here.
114
115 Action
116
117 The action paragraph describes what operator action is
118 required when the message occurs.
119
120
121
122
123
124
125
126
127
128
129
130 3 08/03/23 MR12.7^L
131
132
133 rldr_arg_reader_.pl1
134 rldr_arg_reader_: Implementation Restriction, the
135 RPV must be reloaded separately to obtain the
136 required physical volume information.
137
138
139
140 Stream: BOS Typewriter.
141
142 Time: While system is running.
143
144 Meaning: Due to an implementation restriction, the RPV must
145 be reloaded separately from the other physical
146 volumes. Reload the RPV first, then re-invoke the
147 reload_volue command with the other physical
148 volume names to be reloaded.
149
150 Action: Enter a corrected command line.
151
152
153 scas_init.pl1
154 "scas_init: MEM Y. Tags greater than "D" not
155 supported by DPS8 CPUs",
156
157
158 Stream: BOS Typewriter Crashes system
159
160 Time: System Intialization.
161
162 Meaning: The physical configuration or the configuration
163 deck is incorrect. DPS8 CPUs have only 4 memory
164 ports, therefore Multics systems comprised of DPS8
165 cpus or mixed systems of DPS, L68 and DPS8 cpus
166 can only have 4 memories configured. i.e.
167 Memory tags A B C and D.
168
169 Action: Correct the physical configuration and/or the
170 configuration deck and reboot.
171
172
173 sc_process_command_line_.pl1
174 input on SWITCH_NAME REQUEST_LINE
175
176
177 Stream: as severity 0
178
179 Time: In response to an operator command.
180
181 Meaning: Logs a REQUEST_LINE typed by the operator, or by
182 another user via the send_admin_command or
183 send_initializer_command commands.
184
185 Action: No operator action is required.
186
187
188 abs ACTION 4 08/03/23 MR12.7^L
189
190
191
192
193 absentee_utility_.pl1
194 abs ACTION: N requests ACTIONed.
195
196
197 Stream: as severity1
198
199 Time: In response to an abs defer or abs release
200 command.
201
202 Meaning: Indicates success or failure of the command.
203 ACTION can be defer or release, and N can be "no"
204 or the number of requests acted upon.
205
206 Action: Confirm that the expected results were obtained.
207
208
209 absentee_utility_.pl1
210 abs run: job selection arguments matched N
211 requests; be more specific.
212
213
214 Stream: as severity1
215
216 Time: In response to an abs run command.
217
218 Meaning: The specified arguments matched either zero, or
219 more than one, request, and so no job was run.
220
221 Action: Re-enter the command with correct arguments, to
222 select exactly one job for running.
223
224
225
226 absentee_utility_.pl1
227 abs run: request PATH ID is already running.
228
229
230 Stream: as severity1
231
232 Time: In response to an abs run command.
233
234 Meaning: The specified job is already running.
235
236 Action: If a mistake was made, repeat the command,
237 specifying the correct job.
238
239
240 absentee_user_manager_.pl1
241 absentee_user_manager_ abs run: System too
242 full; no absentee jobs can be started now.
243
244
245
246 absentee_user_manager_ abs run5 08/03/23 MR12.7^L
247
248
249 Stream: as severity1
250
251 Time: In response to an abs run command.
252
253 Meaning: The system is too near the upper limit on logged
254 in users to start any absentee jobs.
255
256 Action: If the immediate running of the job is essential,
257 use "abs stop queue all" to halt all other
258 absentee logins, change the login word to halt all
259 interactive logins, and either wait for a process
260 to log out, or bump one, before repeating the abs
261 run command.
262
263
264
265 absentee_user_manager_.pl1
266 absentee_user_manager_$init: MESSAGE. Cannot
267 truncate absentee_user_table.
268
269
270 Stream: as severity1
271
272 Time: System Intialization.
273
274 Meaning: It was not possible to clear the
275 absentee_user_table segment.
276
277 Action: Contact the system programming staff.
278
279
280 absentee_user_manager_.pl1
281 absentee_user_manager_: ERROR attempting to
282 cancel reservation R for USER.PROJ absN
283
284
285 Stream: as severity1
286
287 Time: While system is running.
288
289 Meaning: The system was unable to cancel a resource
290 reservation for an absentee process that is being
291 destroyed. The resources might remain
292 unavailable to other users. There is some problem
293 in the resource reservation mechanism.
294
295 Action: Contact the system programming staff.
296
297
298 absentee_user_manager_.pl1
299 absentee_user_manager_: ERROR attempting to
300 pre-claim reservation R for USER.PROJ absN
301
302
303
304 absentee_user_manager_ 6 08/03/23 MR12.7^L
305
306
307 Stream: as severity1
308
309 Time: While system is running.
310
311 Meaning: The system was unable to assign a resource
312 reservation to an absentee job that is being
313 logged in. The job will be run, but it might fail
314 if the resources it needs happen to be unavailable
315 when it requests them. There is some problem in
316 the resource reservation mechanism.
317
318 Action: Contact the system programming staff.
319
320
321 absentee_user_manager_.pl1
322 absentee_user_manager_: Error in initializing
323 absentee. Don't bring up absentee facility
324
325
326 Stream: as severity1
327
328 Time: While system is running.
329
330 Meaning: The absentee mechanism will not initialize.
331
332 Action: Contact the system programming staff. Do _^Hn_^Ho_^Ht try
333 to initialize the absentee facility.
334
335
336
337 absentee_user_manager_.pl1
338 absentee_user_manager_: Error: CONDITION
339
340
341 Stream: as severity2
342
343 Time: While system is running.
344
345 Meaning: An unexpected fault has occurred while performing
346 some absentee function such as logging in a new
347 absentee user. The system automatically performs
348 an Answering Service dump and attempts to recover.
349
350 Action: No action is required unless the condition
351 persists. If this message occurs repeatedly, try
352 stopping the absentee facility; inform the
353 programming staff.
354
355
356
357 absentee_user_manager_.pl1
358 absentee_user_manager_: ERROR_MESSAGE. Cannot
359 create absentee event channel
360
361
362 absentee_user_manager_ 7 08/03/23 MR12.7^L
363
364
365 Stream: as severity2
366
367 Time: System Intialization.
368
369 Meaning: The absentee facility could not create part of its
370 communications mechanism. No absentee process can
371 be logged in.
372
373 Action: Try the abs start command again. If the absentee
374 facility still fails, inform the programming
375 staff.
376
377
378
379 absentee_user_manager_.pl1
380 absentee_user_manager_: ERROR_MESSAGE. Creating
381 proc for NAME.PROJ
382
383
384 Stream: as severity2
385
386 Time: While system is running.
387
388 Meaning: A storage system error prevented the absentee user
389 from logging in. This is due to some error in the
390 process creating mechanism. The user is not
391 logged in.
392
393 Action: Contact the system programming staff. Shut down
394 the absentee facility with an abs bump * * and an
395 abs stop if this message occurs repeatedly.
396
397
398
399 absentee_user_manager_.pl1
400 absentee_user_manager_: ERROR_MESSAGE. Trying to
401 wakeup PERSON.PROJECT.TAG process after abs
402 release.
403
404
405
406 Stream: as severity 0
407
408 Time: Called in response to an operator abs release
409 command.
410
411 Meaning: A failure occurred while sending a wakeup to the
412 absentee process being released. ERROR_MESSAGE is
413 the text associated with the error code returned
414 by hcs_$wakeup.
415
416 Action: No operator action is required.
417
418
419
420 absentee_user_manager_ 8 08/03/23 MR12.7^L
421
422
423
424
425 absentee_user_manager_.pl1
426 absentee_user_manager_: event calls were masked.
427
428
429 Stream: sc user_output
430
431 Time: While system is running.
432
433 Meaning: This message indicates a serious error in the
434 Initializer programs. The system attempts to
435 recover and keep running.
436
437 Action: Contact the system programming staff.
438
439
440 absentee_user_manager_.pl1
441 absentee_user_manager_: Premature stopstop for ID
442
443
444 Stream: as severity0
445
446 Time: While system is running.
447
448 Meaning: An error has occurred while trying to destroy the
449 absentee process ID. The system recovers and
450 continues.
451
452 Action: No operator action is required.
453
454
455 absentee_user_manager_.pl1
456 absentee_user_manager_: Process terminated
457 USER.PROJ ID MESSAGE.
458
459
460 Stream: as severity0
461
462 Time: While system is running.
463
464 Meaning: The absentee process ID of USER.PROJ has
465 terminated for the reason specified, and will be
466 logged out.
467
468 Action: No operator action is required.
469
470
471 absentee_user_manager_.pl1
472 absentee_user_manager_: Strange event message
473 WWWWWWWWWWWW WWWWWWWWWWWW from user proc
474 WWWWWWWWWWWW
475
476
477
478 absentee_user_manager_ 9 08/03/23 MR12.7^L
479
480
481 Stream: as severity1
482
483 Time: While system is running.
484
485 Meaning: This message is similar to the preceding message
486 described above, except that the signal does not
487 come from the Initializer but from some other
488 process. The process ID of the sending process is
489 printed in octal. The event message was not a
490 valid item. The system ignores the signal and
491 goes on.
492
493 Action: If absentee jobs will no longer run, try an abs
494 stop and an abs start. Inform the system
495 programming staff.
496
497
498
499 absentee_user_manager_.pl1
500 absentee_user_manager_: Strange event message
501 WWWWWWWWWWWW WWWWWWWWWWWW from Initializer
502
503
504 Stream: as severity1
505
506 Time: While system is running.
507
508 Meaning: An unrecognizable event message has been received
509 from the Answering Service. Its value is printed
510 in octal. Usually, the first word is the function
511 code and the second word is the index in the
512 absentee user table. This condition is due to a
513 error in the Answering Service or absentee
514 programs. The system ignores the signal and goes
515 on. The absentee facility may cease to operate.
516
517 Action: If absentee jobs will no longer run, try an abs
518 stop and an abs start. Inform the system
519 programming staff.
520
521
522
523 absentee_user_manager_.pl1
524 absentee_user_manager_: Strange event message
525 WWWWWWWWWWWW WWWWWWWWWWWW from NAME.PROJ TTY
526
527
528 Stream: as severity1
529
530 Time: While system is running.
531
532 Meaning: This message is similar to the preceding message,
533 except that the name, project, and tty name of the
534
535
536 absentee_user_manager_ 10 08/03/23 MR12.7^L
537
538
539 user sending the wakeup are printed. The system
540 ignores the signal and goes on.
541
542 Action: No operator action is required.
543
544
545 absentee_user_manager_.pl1
546 absentee_user_manager_: Trace ....
547
548
549 Stream: as severity1
550
551 Time: While system is running.
552
553 Meaning: This is trace output. It begins coming out about
554 every five minutes after
555 absentee_user_manager_$aum_trace_on is called.
556
557 Action: No operator action is required. To shut this
558 message off, type:
559 absentee_user_manager_$aum_trace_off while in
560 admin mode.
561
562
563
564 absentee_utility_.pl1
565 absentee_utility_ abs run: Request PATH ID will
566 be run in spite of unavailable resources:
567 RESOURCE
568
569
570 Stream: as severity1
571
572 Time: In response to an abs run command.
573
574 Meaning: The job selected by the abs run command needs
575 RESOURCE, which is unavailable. The job will be
576 logged in anyway.
577
578 Action: If the job is critical, the resource could be made
579 available by force detaching it from some other
580 process. This is a drastic action, and should not
581 be taken without the System Administrator's
582 approval.
583
584
585
586 absentee_utility_.pl1
587 absentee_utility_ setup_queue: Invalid queue
588 number: QUEUE
589
590
591 Stream: as severity2
592
593
594 absentee_utility_ setup_queue 11 08/03/23 MR12.7^L
595
596
597 Time: While system is running.
598
599 Meaning: The internal queue number in absentee_utility_ was
600 invalid when trying to find an absentee to login.
601 If this occurs, there is a logic error in
602 absentee_utility_.
603
604 Action: Contact the system programming staff.
605
606
607 absentee_utility_.pl1
608 absentee_utility_: >sc1>absentee_data has
609 overflowed its limit of N entries.
610
611
612 Stream: as severity2
613
614 Time: While system is running.
615
616 Meaning: The absentee facility keeps a list of absentee
617 jobs that are either deferred or currently
618 running. This list has a capacity of about 13,000
619 entries. It is extremely unlikely that this data
620 area will fill up unless some user program has
621 entered a loop and is submitting requests for jobs
622 faster than the jobs are being run.
623
624 Action: Contact the system programming staff.
625
626
627 absentee_utility_.pl1
628 absentee_utility_: >sc1>absentee_data will be
629 rebuilt.
630
631
632 Stream: as severity1
633
634 Time: While system is running.
635
636 Meaning: An attempt will be made to rebuild the request
637 lists in absentee_data to correct the error
638 reported by the previous message.
639
640 Action: Note for system programmer action.
641
642
643 absentee_utility_.pl1
644 absentee_utility_: Absentee processing suspended.
645 Contact system programmer.
646
647
648 Stream: as severity2
649
650
651
652 absentee_utility_ 12 08/03/23 MR12.7^L
653
654
655 Time: While system is running.
656
657 Meaning: Absentee processing has been suspended because of
658 the error described in the previous message. No
659 more jobs will be started, but logged in jobs will
660 continue running. The absentee facility has not
661 been stopped, and an "abs start" command will be
662 rejected. After the error has been corrected, the
663 "abs start queue N" command may be used to resume
664 the processing of requests from queues unaffected
665 by the error.
666
667 Action: Contact the system programming staff.
668
669
670 absentee_utility_.pl1
671 absentee_utility_: Attempt to set defer timer to
672 time in past TIME. Setting it to a minute from
673 now.
674
675
676 Stream: as severity0
677
678 Time: While system is running.
679
680 Meaning: An attempt was made to set the absentee deferred
681 request timer to a time in the past.
682
683 Action: No operator action is required.
684
685
686 absentee_utility_.pl1
687 absentee_utility_: Attempting to reserve RESOURCE
688 for PERS.PROJ PATH
689
690
691 Stream: as severity2
692
693 Time: While system is running.
694
695 Meaning: An error occurred during the attempt to reserve a
696 resource for an absentee job. The job is deferred
697 and the attempt to reserve the resource is
698 repeated at some later time. The absentee
699 facility continues to operate. There is something
700 wrong with the resource reservation mechanism or
701 with some other part of RCP.
702
703 Action: Contact the system programming staff.
704
705
706 absentee_utility_.pl1
707
708
709
710 absentee_utility_ 13 08/03/23 MR12.7^L
711
712
713 absentee_utility_: BUG: lc ineligible INDEX
714 not at head of resource list.
715
716
717 Stream: as severity2
718
719 Time: While system is running.
720
721 Meaning: The current absentee request, which would be
722 deferred by load control, is not at the head of
723 the absentee list. If this occurs, there is a
724 logic error in absentee_utility_.
725
726 Action: Contact the system programming staff.
727
728
729 absentee_utility_.pl1
730 absentee_utility_: Entry not found. Creating new
731 >sc1>absentee_data
732
733
734 Stream: as severity1
735
736 Time: During startup of the absentee facility.
737
738 Meaning: The absentee data segment was missing and a new
739 one has been created.
740
741 Action: Note for system programmer action.
742
743
744 absentee_utility_.pl1
745 absentee_utility_: Entry not found. Creating new
746 >sc1>absentee_N.ms
747
748
749 Stream: as severity1
750
751 Time: During startup of the absentee facility.
752
753 Meaning: The absentee message segment for queue N was
754 missing, and a new one has been created. Any
755 previously submitted absentee jobs in queue N are
756 not executed.
757
758 Action: If the absentee queues never existed or were
759 deliberately deleted or removed, this message
760 should be ignored. Otherwise, it may be necessary
761 to inform users via the message of the day that
762 the absentee requests for queue N were lost.
763 Contact the system programming staff for help in
764 recovering the queue.
765
766
767
768 absentee_utility_ 14 08/03/23 MR12.7^L
769
770
771
772
773 absentee_utility_.pl1
774 absentee_utility_: ERROR_MESSAGE Dropping queue
775 >sc1>absentee_N.ms due to M consecutive errors
776
777
778 Stream: as severity2
779
780 Time: While system is running.
781
782 Meaning: This message is printed when a series of errors
783 prevents the absentee facility from reading jobs
784 from a given queue. Absentee requests in queue N
785 are ignored until the absentee facility is stopped
786 and restarted, or the command abs start queue N is
787 used to restart the dropped queue.
788
789 Action: Note for system programmer action.
790
791
792 absentee_utility_.pl1
793 absentee_utility_: ERROR_MESSAGE Truncating
794 absentee_data.
795
796
797 Stream: as severity2
798
799 Time: While system is running.
800
801 Meaning: An error occurred during the attempt to truncate
802 absentee_data prior to rebuilding it. It will not
803 be possible to rebuild it.
804
805 Action: Contact the system programming staff.
806
807
808 absentee_utility_.pl1
809 absentee_utility_: ERROR_MESSAGE. Error in
810 creating defer event channel
811
812
813 Stream: as severity2
814
815 Time: During startup of the absentee facility.
816
817 Meaning: The event channel used in processing absentee
818 requests that are deferred until a later time
819 cannot be created. No deferred requests are
820 activated.
821
822 Action: Issue an abs stop command and wait until all
823 absentees run to completion. Then, issue an abs
824
825
826 absentee_utility_ 15 08/03/23 MR12.7^L
827
828
829 start command. If this same message recurs,
830 contact the system programming staff.
831
832
833
834 absentee_utility_.pl1
835 absentee_utility_: ERROR_MESSAGE. Unable to
836 create >sc1>absentee_data
837
838
839 Stream: as severity2
840
841 Time: During startup of the absentee facility.
842
843 Meaning: The absentee data segment could not be created.
844 Faults will probably occur in the absentee
845 facility if the system attempts to run absentee
846 jobs.
847
848 Action: Notify the system programming staff. Do _^Hn_^Ho_^Ht
849 attempt to run absentee jobs.
850
851
852
853 absentee_utility_.pl1
854 absentee_utility_: ERROR_MESSAGE. Unable to
855 create >sc1>absentee_N.ms
856
857
858 Stream: as severity1
859
860 Time: During startup of the absentee facility.
861
862 Meaning: The absentee message segment for queue N cannot be
863 created. Users cannot queue jobs in queue N, and
864 jobs in queue N cannot be executed.
865
866 Action: Contact the system programming staff.
867
868
869 absentee_utility_.pl1
870 absentee_utility_: ERROR_MESSAGE. Unable to open
871 new >sc1>absentee_N.ms
872
873
874 Stream: as severity1
875
876 Time: During startup of the absentee facility.
877
878 Meaning: The absentee message segment for queue N just
879 created cannot be found. No absentee jobs are
880 run.
881
882
883
884 absentee_utility_ 16 08/03/23 MR12.7^L
885
886
887 Action: Contact the system programming staff.
888
889
890 absentee_utility_.pl1
891 absentee_utility_: ERROR_MESSAGE. Unable to set
892 access on >sc1>absentee_data
893
894
895 Stream: as severity1
896
897 Time: During startup of the absentee facility.
898
899 Meaning: The newly-created segment absentee_data cannot be
900 given correct access. The system should continue
901 to run.
902
903 Action: Note for system programmer action.
904
905
906 absentee_utility_.pl1
907 absentee_utility_: ERROR_MESSAGE. Unable to
908 terminate >sc1>absentee_data
909
910
911 Stream: as severity1
912
913 Time: During shutdown of the absentee facility.
914
915 Meaning: While shutting down the absentee facility, the
916 system attempted to terminate the segment
917 absentee_data and received an error. This
918 condition is not serious.
919
920 Action: Note for system programmer action.
921
922
923 absentee_utility_.pl1
924 absentee_utility_: ERROR_MESSAGE. Attempting to
925 cancel reservation REQUEST for USER ABSENTEE
926
927
928 Stream: Logged in SYSERR log.
929
930 Time: While system is running.
931
932 Meaning: An error occurred while cancelling an RCP
933 reservation for an absentee being deferred.
934
935 Action: No operator action is required.
936
937
938 absentee_utility_.pl1
939
940
941
942 absentee_utility_ 17 08/03/23 MR12.7^L
943
944
945 absentee_utility_: ERROR_MESSAGE. Closing
946 >sc1>absentee_N.ms
947
948
949 Stream: as severity1
950
951 Time: While shutting down the absentee facility.
952
953 Meaning: A storage system error occurred as part of the
954 processing of "abs stop" while attempting to
955 terminate the absentee message segment for queue
956 N. Absentee requests for queue N may have been
957 lost.
958
959 Action: If you are shutting down the absentee facility
960 because of some previous message-segment error,
961 contact the system programming staff and do not
962 try to restart the absentee facility. If this
963 absentee shutdown is a normally scheduled one,
964 notify the system programmers of the message and
965 do not try to restart the absentee facility again
966 until they have looked at the problem.
967
968
969
970 absentee_utility_.pl1
971 absentee_utility_: ERROR_MESSAGE. queue N
972 >sc1>absentee_N.ms
973
974
975 Stream: as severity1
976
977 Time: While system is running.
978
979 Meaning: An error occurred while reading, rewriting, or
980 deleting a request from queue N. An attempt is
981 made to correct the error and retry the operation.
982 Additional messages are printed if this attempt
983 fails.
984
985 Action: Contact the system programming staff.
986
987
988 absentee_utility_.pl1
989 absentee_utility_: ERROR_MESSAGE. Searching
990 queue QUEUE skip list for USER ABSENTEE
991
992
993 Stream: Logged in SYSERR log.
994
995 Time: While system is running.
996
997
998
999
1000 absentee_utility_ 18 08/03/23 MR12.7^L
1001
1002
1003 Meaning: An error occurred while searching the skip list
1004 for an absentee request.
1005
1006 Action: No operator action is required.
1007
1008
1009 absentee_utility_.pl1
1010 absentee_utility_: ERROR_MESSAGE. Searching skip
1011 list for USER ABSENTEE
1012
1013
1014 Stream: Logged in SYSERR log.
1015
1016 Time: While system is running.
1017
1018 Meaning: An error occurred while searching the skip list
1019 for an absentee request.
1020
1021 Action: No operator action is required.
1022
1023
1024 absentee_utility_.pl1
1025 absentee_utility_: ERROR_MESSAGE. Sending TYPE
1026 wakeup to PROCID ABS-EVENT
1027
1028
1029 Stream: Logged in SYSERR log.
1030
1031 Time: While system is running.
1032
1033 Meaning: An error occurred while sending an "aum_ctl" or
1034 "login" wakeup to the specified absentee process.
1035
1036 Action: No operator action is required.
1037
1038
1039 absentee_utility_.pl1
1040 absentee_utility_: ERROR_MESSAGE. Unable to
1041 delete request for USER ABSENTEE; queue: QUEUE;
1042 index: QUEUE_INDEX
1043
1044
1045 Stream: as severity0
1046
1047 Time: While system is running.
1048
1049 Meaning: An error occurred while deleting a request from
1050 the absentee queue.
1051
1052 Action: No operator action is required.
1053
1054
1055 absentee_utility_.pl1
1056
1057
1058 absentee_utility_ 19 08/03/23 MR12.7^L
1059
1060
1061 absentee_utility_: ERROR_MESSAGE. Unable to
1062 notify user USER of absentee event.
1063
1064
1065 Stream: Logged in SYSERR log.
1066
1067 Time: While system is running.
1068
1069 Meaning: An error occurred while sending a message to USER
1070 as notification of an absentee event.
1071
1072
1073
1074 absentee_utility_.pl1
1075 absentee_utility_: ERROR_MESSAGE. Unable to set
1076 extended access on >sc1>absentee_N.ms
1077
1078
1079 Stream: as severity1
1080
1081 Time: During startup of the absentee facility.
1082
1083 Meaning: The absentee message segment for queue N just
1084 created cannot be set up so that users can access
1085 it properly. Users will not be able to submit
1086 absentee requests.
1087
1088 Action: Contact the system programming staff.
1089
1090
1091 absentee_utility_.pl1
1092 absentee_utility_: ERROR_MESSAGE. While reading
1093 message MESSAGE from USER ABSENTEE to be
1094 rewritten.
1095
1096
1097 Stream: Logged in SYSERR log.
1098
1099 Time: While system is running.
1100
1101 Meaning: An error occurred while reading a request from the
1102 absentee queue.
1103
1104 Action: No operator action is required.
1105
1106
1107 absentee_utility_.pl1
1108 absentee_utility_: ERROR_MESSAGE. While reading
1109 message MESSAGE to be rewritten.
1110
1111
1112 Stream: Logged in SYSERR log.
1113
1114
1115
1116 absentee_utility_ 20 08/03/23 MR12.7^L
1117
1118
1119 Time: While system is running.
1120
1121 Meaning: An error occurred while reading an absentee
1122 request to be marked as "running".
1123
1124 Action: No operator action is required.
1125
1126
1127 absentee_utility_.pl1
1128 absentee_utility_: Illegal proxy for NAME.PROJ
1129 from NAME1.PROJ1 for job JJJJ
1130
1131
1132 Stream: as severity1
1133
1134 Time: While system is running.
1135
1136 Meaning: This message is printed whenever a proxy absentee
1137 job is submitted by some user who is not allowed
1138 to submit a proxy. User NAME1.PROJ1 submitted job
1139 JJJJ to be run with the user ID NAME.PROJ, but the
1140 absentee facility will not do so and ignores the
1141 request.
1142
1143 Action: Note for system programmer action.
1144
1145
1146 absentee_utility_.pl1
1147 absentee_utility_: Illegal queue number QUEUE
1148 for USER ABSENTEE
1149
1150
1151 Stream: as severity0
1152
1153 Time: While system is running.
1154
1155 Meaning: The queue number specified for the absentee job in
1156 the absentee user table has an illegal value.
1157
1158 Action: No operator action is required.
1159
1160
1161 absentee_utility_.pl1
1162 absentee_utility_: Loop in PROC, searching NAME
1163 list for queue N.
1164
1165
1166 Stream: as severity1
1167
1168 Time: While system is running.
1169
1170 Meaning: A software error has damaged the list of requests
1171 in absentee_data. The error was detected by the
1172
1173
1174 absentee_utility_ 21 08/03/23 MR12.7^L
1175
1176
1177 internal procedure, PROC, while searching the NAME
1178 list belonging to queue N. The system makes one
1179 attempt to rebuild the list. Additional messages
1180 are printed if this attempt fails.
1181
1182 Action: Contact the system programming staff.
1183
1184
1185 absentee_utility_.pl1
1186 absentee_utility_: Loop occurred while rebuilding
1187 absentee_data after previous loop.
1188
1189
1190 Stream: as severity2
1191
1192 Time: While system is running.
1193
1194 Meaning: The error reported by the previous message
1195 occurred while absentee_data was being rebuilt
1196 following an earlier error. The rebuild attempt
1197 will not be repeated.
1198
1199 Action: Contact the system programming staff.
1200
1201
1202 absentee_utility_.pl1
1203 absentee_utility_: rejected request ID PATH in
1204 queue N from PERS.PROJ: REASON
1205
1206
1207 Stream: as severity1
1208
1209 Time: While system is running.
1210
1211 Meaning: This message is printed if a message that appears
1212 to be garbled or meaningless is found in absentee
1213 queue N. The garbled message is ignored. This
1214 condition may be evidence of damage to absentee
1215 queue N, unless REASON indicates otherwise.
1216
1217 Action: Note for system programmer action.
1218
1219
1220 absentee_utility_.pl1
1221 absentee_utility_: Timer rang and no deferred
1222 request found.
1223
1224
1225 Stream: as severity0
1226
1227 Time: While system is running.
1228
1229
1230
1231
1232 absentee_utility_ 22 08/03/23 MR12.7^L
1233
1234
1235 Meaning: The deferred request timer went off and no
1236 deferred absentee jobs were found.
1237
1238 Action: No operator action is required.
1239
1240
1241 accept_fs_disk.pl1
1242 accept_fs_disk: part NAME on PVNAME dskX_NNS
1243 from AAA for BBB overlaps pages from CCC
1244
1245
1246 Stream: BOS Typewriter.
1247
1248 Time: When accepting a disk volume.
1249
1250 Meaning: The supervisor checks the partitions defined in
1251 the volume label against the beginning of the
1252 paging partition when it accepts a volume. The
1253 partition NAME overlaps the paging area. The
1254 volume label may have been damaged.
1255
1256 Action: Be careful not to destroy the contents of part
1257 NAME, since this will destory the contents of user
1258 segments. Note for system programmer action.
1259
1260
1261
1262 accept_rpv.pl1
1263 accept_rpv: Error ERRORMESSAGE accepting RPV
1264
1265
1266 Stream: BOS Typewriter Crashes system
1267
1268 Time: System Intialization.
1269
1270 Meaning: Some problem was encountered trying to set up the
1271 use of the RPV for normal segment creation and
1272 activation. The label of the RPV may have been
1273 damaged, or encountered disk errors, as indicated
1274 by the ERRORMESSAGE.
1275
1276 Action: Make sure that the RPV label area first eight
1277 records, or a dump of it, is available for system
1278 programmer inspection. Note for system programmer
1279 action.
1280
1281 Message: accept_rpv: HC part on dskX_NN used XXX
1282 out of YYY records.
1283
1284 Stream: This message is printed on the console if an HCPT
1285 card is in the config deck. Otherwise, it is
1286 logged into the syserr_log.
1287
1288
1289
1290 accept_rpv 23 08/03/23 MR12.7^L
1291
1292
1293 Time: System Intialization.
1294
1295 Meaning: The message appears for each disk volume which
1296 contains a Hardcore Partition PART HC. It
1297 indicates how many records were actually used
1298 XXX in the partition, which had size YYY.
1299
1300 Action: No operator action is required.
1301
1302
1303 accept_rpv.pl1
1304 accept_rpv: pv PVNAME lv LVNAME DSKX_NN is not
1305 part of root.
1306
1307
1308 Stream: BOS Typewriter Crashes system
1309
1310 Time: System Intialization.
1311
1312 Meaning: The pack on the drive DSKX_NN, with pv name and lv
1313 name as read from its label, is specified on the
1314 ROOT CONFIG card, but is not part of the same
1315 logical volume as the RPV.
1316
1317 Action: Check the ROOT CONFIG card for errors. Check for
1318 the proper packs. Reboot the system.
1319
1320
1321
1322 access_audit_.pl1
1323 access_audit_$ENTRY: USER_ID Called with
1324 insufficient arguments #args= ^d.
1325 Caller=""CALLING_PROC".
1326
1327
1328 Stream: BOS Typewriter.
1329
1330 Time: While system is running.
1331
1332 Meaning: This indicates a logic error in the supervisor, or
1333 CPU or memory hardware problems. access_audit_
1334 was invoked with an improper calling sequence.
1335 There may have been enough arguments to display
1336 the offending caller name.
1337
1338 Action: Contact the system programming staff.
1339
1340
1341 access_audit_.pl1
1342 access_audit_$ENTRY: USER_ID Encountered
1343 illegal meter index. OperCode=XXXXXXXXXXXX
1344 EventFlags=YYYYYYYYYYYY. Caller="CALLING_PROC".
1345
1346
1347
1348 access_audit_$ENTRY 24 08/03/23 MR12.7^L
1349
1350
1351 Stream: Logged in SYSERR log.
1352
1353 Time: While system is running.
1354
1355 Meaning: This indicates a logic error in the supervisor, or
1356 CPU or memory hardware problems. The access audit
1357 meters in active_hardcore_data are inconsistant
1358 with the format of the process access flags or the
1359 supplied operation code and/or event flags.
1360
1361 Action: Contact the system programming staff.
1362
1363
1364 access_audit_.pl1
1365 access_audit_$ENTRY: USER_ID Encountered
1366 illegal parameter combination.
1367 OperCode=XXXXXXXXXXXX EventFlags=YYYYYYYYYYYY.
1368 Caller="CALLING_PROC".
1369
1370
1371 Stream: BOS Typewriter.
1372
1373 Time: While system is running.
1374
1375 Meaning: This indicates a logic error in the supervisor, or
1376 CPU or memory hardware problems. There is an
1377 error in the access_operations_ entry or the
1378 eventflags passed to access audit. The error was
1379 detected in the code which decides whether the
1380 caller needs to audit its event. Because of the
1381 error, the event will be audited regardless of the
1382 process audit flags.
1383
1384 Action: Contact the system programming staff.
1385
1386
1387 access_audit_.pl1
1388 access_audit_$ENTRY: USER_ID Improper calling
1389 sequence from "get_entry_pointer_and_class".
1390 Caller="CALLING_PROC".
1391
1392
1393 Stream: BOS Typewriter.
1394
1395 Time: While system is running.
1396
1397 Meaning: This indicates a logic error in the supervisor, or
1398 CPU or memory hardware problems. The entry was
1399 called with an improper argument combination.
1400 Most likely the entry will be log
1401 check_obj_ptr_user and the obj_ptr supplied
1402 will be null.
1403
1404
1405
1406 access_audit_$ENTRY 25 08/03/23 MR12.7^L
1407
1408
1409 Action: Contact the system programming staff.
1410
1411
1412 access_audit_.pl1
1413 access_audit_$ENTRY: USER_ID Unable to generate
1414 path for entry at PTR due to "MESSAGE".
1415 Caller="CALLING_PROC".
1416
1417
1418 Stream: Logged in SYSERR log.
1419
1420 Time: While system is running.
1421
1422 Meaning: This indicates a logic error in the supervisor, or
1423 CPU or memory hardware problems. A call to
1424 get_pathname_ returned an unexpected error code.
1425
1426 Action: Contact the system programming staff.
1427
1428
1429 access_audit_.pl1
1430 access_audit_$ENTRY: USER_ID Unable to get
1431 entry pointer for seg #N | PATH due to
1432 "MESSAGE".
1433
1434
1435 Stream: Logged in SYSERR log.
1436
1437 Time: While system is running.
1438
1439 Meaning: This indicates a logic error in the supervisor, or
1440 CPU or memory hardware problems. A call to
1441 sum$getbranch_root_my or dc_find$obj_for_audit
1442 returned an unexpected error code.
1443
1444 Action: Contact the system programming staff.
1445
1446
1447 access_audit_.pl1
1448 access_audit_$ENTRY: USER_ID Unable to get raw
1449 access modes for entry PTR due to "MESSAGE".
1450 Caller="CALLER_PROC".
1451
1452
1453 Stream: Logged in SYSERR log.
1454
1455 Time: While system is running.
1456
1457 Meaning: This indicates a logic error in the supervisor, or
1458 CPU or memory hardware problems. Although the
1459 directory is locked a failure occurred in
1460 access_mode$raw.
1461
1462
1463
1464 access_audit_$ENTRY 26 08/03/23 MR12.7^L
1465
1466
1467 Action: Contact the system programming staff.
1468
1469
1470 access_audit_.pl1
1471 access_audit_$ENTRY: USER_ID Unable to get UID
1472 path for directory seg #N due to "MESSAGE".
1473 Caller="CALLER_PROC".
1474
1475
1476 Stream: Logged in SYSERR log.
1477
1478 Time: While system is running.
1479
1480 Meaning: This indicates a logic error in the supervisor, or
1481 CPU or memory hardware problems. Although the
1482 directory is locked, a failure occurred in
1483 uid_path_util$get.
1484
1485 Action: Contact the system programming staff.
1486
1487
1488 access_audit_.pl1
1489 access_audit_$ENTRY: USER_ID Unexpected error
1490 obtaining caller text pointer.
1491 Caller="CALLING_PROC".
1492
1493
1494 Stream: BOS Typewriter.
1495
1496 Time: While system is running.
1497
1498 Meaning: This indicates a logic error in the supervisor, or
1499 CPU or memory hardware problems. An error exists
1500 in the calling sequence to access_audit_.
1501
1502 Action: Contact the system programming staff.
1503
1504
1505 access_audit_.pl1
1506 access_audit_$UNKNOWN: USER_ID Illegal
1507 entrypoint index "N" detected in
1508 form_audit_message_text. Caller="CALLING_PROC".
1509
1510
1511 Stream: BOS Typewriter.
1512
1513 Time: While system is running.
1514
1515 Meaning: This indicates a logic error in the supervisor, or
1516 CPU or memory hardware problems. There is a
1517 coding error in access_audit_ where the entrypoint
1518 index is uninitialized or set to an incorrect
1519 value.
1520
1521
1522 access_audit_$UNKNOWN 27 08/03/23 MR12.7^L
1523
1524
1525 Action: Contact the system programming staff.
1526
1527
1528 access_audit_.pl1
1529 access_audit_: Insufficient room to allocate
1530 ssobj|link data.
1531
1532
1533 Stream: BOS Typewriter.
1534
1535 Time: While system is running.
1536
1537 Meaning: This indicates a logic error in the supervisor, or
1538 CPU or memory hardware problems. An automatic
1539 data area is too small to accomodate the storage
1540 system object or link binary info.
1541
1542 Action: Contact the system programming staff.
1543
1544
1545 access_audit_log_fault_.pl1
1546 access_audit_log_fault_: USER_ID Unable to get
1547 path of seg #N due to "MESSAGE".
1548
1549
1550 Stream: BOS Typewriter.
1551
1552 Time: While system is running.
1553
1554 Meaning: This indicates a logic error in the supervisor or
1555 CPU or memory hardware problems. A call to
1556 get_pathname_ returned an unexpected error code.
1557
1558 Action: Contact the system programming staff.
1559
1560
1561 access_audit_log_fault_.pl1
1562 access_audit_log_fault_: USER_ID Called with
1563 bad machine conditions.
1564
1565
1566 Stream: BOS Typewriter.
1567
1568 Time: While system is running.
1569
1570 Meaning: This indicates a logic error in the supervisor or
1571 CPU or memory hardware problems.
1572 access_audit_log_fault_ was given machine
1573 conditions for a fault which was neither an
1574 illegal_procedure or an access_violation.
1575
1576 Action: Contact the system programming staff.
1577
1578
1579
1580 access_audit_log_fault_ 28 08/03/23 MR12.7^L
1581
1582
1583
1584
1585 access_audit_log_fault_.pl1
1586 access_audit_log_fault_: USER_ID Encountered
1587 illegal meter index value.
1588
1589
1590 Stream: BOS Typewriter.
1591
1592 Time: While system is running.
1593
1594 Meaning: This indicates a logic error in the supervisor or
1595 CPU or memory hardware problems. The access audit
1596 meters in active_hardcore_data are inconsistant
1597 with the format of the process access flags.
1598
1599 Action: Contact the system programming staff.
1600
1601
1602 access_audit_log_fault_.pl1
1603 access_audit_log_fault_: USER_ID Unable to get
1604 access mode for data seg #N due to "MESSAGE".
1605
1606
1607 Stream: BOS Typewriter.
1608
1609 Time: While system is running.
1610
1611 Meaning: This indicates a logic error in the supervisor or
1612 CPU or memory hardware problems. A call to
1613 fs_modes failed unexpectedly. The AUDIT message
1614 text will show the modes as "???" and ring
1615 brackets of 777. The message binary will
1616 reflect null access mode and ring bracket of
1617 777.
1618
1619 Action: Contact the system programming staff.
1620
1621
1622 access_audit_log_fault_.pl1
1623 access_audit_log_fault_: USER_ID Unable to get
1624 entry pointer for seg #N due to "MESSAGE".
1625
1626
1627 Stream: BOS Typewriter.
1628
1629 Time: While system is running.
1630
1631 Meaning: This indicates a logic error in the supervisor or
1632 CPU or memory hardware problems. A call to
1633 sum$getbranch_root_my returned an unexpected error
1634 code.
1635
1636
1637
1638 access_audit_log_fault_ 29 08/03/23 MR12.7^L
1639
1640
1641 Action: Contact the system programming staff.
1642
1643
1644 access_audit_log_fault_.pl1
1645 access_audit_log_fault_: USER_ID Unable to get
1646 raw access modes for entry PTR due to "MESSAGE".
1647
1648
1649 Stream: BOS Typewriter.
1650
1651 Time: While system is running.
1652
1653 Meaning: This indicates a logic error in the supervisor or
1654 CPU or memory hardware problems. Although the
1655 directory is locked a failure occurred in
1656 access_mode$raw.
1657
1658 Action: Contact the system programming staff.
1659
1660
1661 access_audit_log_fault_.pl1
1662 access_audit_log_fault_: USER_ID Unable to get
1663 UID path for directory seg #N due to "MESSAGE".
1664
1665
1666 Stream: BOS Typewriter.
1667
1668 Time: While system is running.
1669
1670 Meaning: This indicates a logic error in the supervisor or
1671 CPU or memory hardware problems. Although the
1672 directory is locked a failure occurred in
1673 uid_path_util$get.
1674
1675 Action: Contact the system programming staff.
1676
1677
1678 access_audit_log_fault_.pl1
1679 access_audit_log_fault_: Link entry where branch
1680 expected ep=PTR.
1681
1682
1683 Stream: BOS Typewriter Crashes system
1684
1685 Time: While system is running.
1686
1687 Meaning: This indicates a logic error in the supervisor or
1688 CPU or memory hardware problems. After getting a
1689 directory entry for a specific segno the branch
1690 switch in the entry was found to be off.
1691
1692 Action: Follow normal recovery procedures.
1693
1694
1695
1696 access_viol 30 08/03/23 MR12.7^L
1697
1698
1699
1700
1701 access_viol.pl1
1702 access_viol: associative memory fault.
1703
1704
1705 Stream: BOS Typewriter Crashes system
1706
1707 Time: While system is running.
1708
1709 Meaning: The processor associative memory has detected a
1710 usage count error.
1711
1712 Action: Notify Field Engineering personnel.
1713
1714
1715 act_ctl_.pl1
1716 act_ctl_$dp: Net accounting array version
1717 VERSION_RETURNED not supported. Expected
1718 version VERSION_SUPPORTED
1719
1720
1721
1722 Stream: as severity2.
1723
1724 Time: While system is running.
1725
1726 Meaning: network_accounting_gate_$read_and_reset_table
1727 returned a structure version which act_ctl_ does
1728 not support.This indicates a logic error in the
1729 supervisor or CPU or memory hardware problems.
1730
1731 Action: Contact the system programming staff._sm
1732
1733
1734 act_ctl_.pl1
1735 act_ctl_$init: cannot locate
1736 Initializer.SysDaemon pdt entry
1737
1738
1739 Stream: as severity2
1740
1741 Time: System Intialization.
1742
1743 Meaning: The accounting system requires the entry for
1744 Initializer in the project SysDaemon to be present
1745 because certain system metering figures are kept
1746 there. This entry cannot be found either because
1747 SysDaemon.pdt has been lost or because its
1748 contents have been destroyed. The system will
1749 probably encounter a simfault_xxx error and be
1750 unable to start up.
1751
1752
1753
1754 act_ctl_$init 31 08/03/23 MR12.7^L
1755
1756
1757 Action: Contact the system programming staff. Do not
1758 attempt to run the system until this problem has
1759 been fixed.
1760
1761
1762
1763 act_ctl_.pl1
1764 act_ctl_$init: ERROR_MESSAGE. Cannot unlock PDT
1765 PATHNAME.
1766
1767
1768 Stream: as severity2
1769
1770 Time: System Intialization.
1771
1772 Meaning: This message occurs during answering service
1773 initialization when attempting to unlock all PDTs.
1774 ERROR_MESSAGE specifies the the reason for the
1775 problem. The PDT is skipped. Later problems may
1776 arise because of this error.
1777
1778 Action: Contact the system programming staff.
1779
1780
1781 act_ctl_.pl1
1782 act_ctl_$init: ERROR_MESSAGE. creating update
1783 channel
1784
1785
1786 Stream: as severity2
1787
1788 Time: System Intialization.
1789
1790 Meaning: The timer channel that causes accounting updates
1791 to be performed could not be created. All
1792 accounting updates will be manual triggered by a
1793 user logging out.
1794
1795 Action: Contact the system programming staff.
1796
1797
1798 act_ctl_.pl1
1799 act_ctl_$init: illegal value DD for accounting
1800 update interval in installation_parms.
1801
1802
1803 Stream: as severity2
1804
1805 Time: System Intialization.
1806
1807 Meaning: The value given in installation_parms.acct_update
1808 is less than or equal to zero. The
1809 installation_parms file is probabily damaged.
1810
1811
1812 act_ctl_$init 32 08/03/23 MR12.7^L
1813
1814
1815 Action: Contact the system programming staff. Do not
1816 attempt to run the system until this problem has
1817 been fixed.
1818
1819
1820
1821 act_ctl_.pl1
1822 act_ctl_$init: The PDT is damaged. Cannot unlock
1823 PATHNAME.
1824
1825
1826 Stream: as severity2
1827
1828 Time: System Intialization.
1829
1830 Meaning: This message occurs during answering service
1831 initialization when attempting to unlock all PDTs.
1832 The specified PDT had its damaged switch turned
1833 on. Because of this it was not unlocked from the
1834 previous bootload. It is skipped. Later problems
1835 may arise when an attempt is made to reference
1836 this PDT.
1837
1838 Action: Contact the system programming staff.
1839
1840
1841 act_ctl_.pl1
1842 act_ctl_$update: Error from ROUTINE: MESSAGE
1843
1844
1845 Stream: as severity2.
1846
1847 Time: While system is running.
1848
1849 Meaning: The system encountered problems while referencing
1850 the network_accounting_table. The
1851 network_accounting_ ROUTINE being called and
1852 MESSAGE text further describe the error.
1853
1854 Action: Contact the system programming staff.
1855
1856
1857 act_ctl_.pl1
1858 act_ctl_$update: Net accounting array version
1859 VERSION_RETURNED not supported. Expected
1860 version VERSION_SUPPORTED
1861
1862
1863
1864 Stream: as severity2.
1865
1866 Time: While system is running.
1867
1868
1869
1870 act_ctl_$update 33 08/03/23 MR12.7^L
1871
1872
1873 Meaning: network_accounting_gate_$read_and_reset_table
1874 returned a structure version which act_ctl_ does
1875 not support.This indicates a logic error in the
1876 supervisor or CPU or memory hardware problems.
1877
1878 Action: Contact the system programming staff._sm
1879
1880
1881 act_ctl_.pl1
1882 act_ctl_$update: Processid XXXXXXXX missing. Not
1883 charged for XX pkt YY byte and ZZ seconds;
1884 was/was not purged.
1885
1886
1887
1888 Stream: as severity2
1889
1890 Time: While system is running.
1891
1892 Meaning: After charging network accounting usage for all
1893 users on the system an entry was found for
1894 processid XXXXXXXX. The XX YY and ZZ are counts
1895 of the usage which the process had. If the entry
1896 was for a process which is no longer logged in
1897 the accounting record was purged from the network
1898 accounting file.
1899
1900 Action: Note for system programmer action.
1901
1902
1903 act_ctl_.pl1
1904 act_ctl_: accounting disabled
1905
1906
1907 Stream: as severity1
1908
1909 Time: May occur at any time.
1910
1911 Meaning: The accounting system has been disabled by a call
1912 to act_ctl_$act_ctl_disable.
1913
1914 Action: No operator action is required.
1915
1916
1917 act_ctl_.pl1
1918 act_ctl_: accounting enabled.
1919
1920
1921 Stream: as severity1
1922
1923 Time: May occur at any time.
1924
1925
1926
1927
1928 act_ctl_ 34 08/03/23 MR12.7^L
1929
1930
1931 Meaning: The accounting system has been enabled probably
1932 after a special session by a call to
1933 act_ctl_$act_ctl_reable.
1934
1935 Action: No operator action is required.
1936
1937
1938 act_ctl_.pl1
1939 act_ctl_: alarm clock late or failing by XX.XX
1940 mins
1941
1942
1943 Stream: as severity1
1944
1945 Time: While system is running.
1946
1947 Meaning: The alarm clock channel has not caused an
1948 accounting update to be performed when it was due.
1949 The time between updates is stored in the segment
1950 installation_parms. The system performs a manual
1951 accounting update. This message may appear if the
1952 system has entered BOS and Multics has then been
1953 restarted by the GO command. In such case the
1954 message can be ignored.
1955
1956 Action: Note for system programmer action.
1957
1958
1959 act_ctl_.pl1
1960 act_ctl_: bumping absNN NAME.PROJ - inactive too
1961 long
1962
1963
1964 Stream: as severity1
1965
1966 Time: While system is running.
1967
1968 Meaning: The absentee job on absentee slot NN for user
1969 NAME.PROJ has remained blocked too long. The
1970 inactive time limit is stored in the segment
1971 installation_parms. The absentee job is bumped.
1972
1973 Action: No operator action is required.
1974
1975
1976 act_ctl_.pl1
1977 act_ctl_: bumping absXX NAME.PROJ - too much time
1978
1979
1980 Stream: as severity1
1981
1982 Time: While system is running.
1983
1984
1985
1986 act_ctl_ 35 08/03/23 MR12.7^L
1987
1988
1989 Meaning: The absentee job on absentee slot XX for the user
1990 NAME.PROJ has exceeded the CPU time limit for the
1991 queue. This limit is stored in the segment
1992 installation_parms. The absentee job is bumped.
1993
1994 Action: No operator action is required.
1995
1996
1997 act_ctl_.pl1
1998 act_ctl_: bumping NAME.PROJ for inactivity
1999
2000
2001 Stream: as severity1
2002
2003 Time: While system is running.
2004
2005 Meaning: The user with name NAME and project PROJ has been
2006 inactive too long and is bumped off the system.
2007 The maximum inactive time is stored in the segment
2008 installation_parms.
2009
2010 Action: No operator action is required.
2011
2012
2013 act_ctl_.pl1
2014 act_ctl_: bumping NAME.PROJ. REASON
2015
2016
2017 Stream: as severity1
2018
2019 Time: While system is running.
2020
2021 Meaning: The user with name NAME and project PROJ has been
2022 bumped because some per-user limit has been
2023 exceeded. REASON tells what was wrong; it will be
2024 a message such as "User resource limit of $100
2025 monthly exceeded" depending on which user limit
2026 has been exceeded.
2027
2028 Action: No operator action is required.
2029
2030
2031 act_ctl_.pl1
2032 act_ctl_: changing shift from x to y
2033
2034
2035 Stream: as severity1
2036
2037 Time: While system is running.
2038
2039 Meaning: The current accounting shift has changed. The
2040 table that tells the beginning time for each shift
2041 is stored in the segment installation_parms.
2042
2043
2044 act_ctl_ 36 08/03/23 MR12.7^L
2045
2046
2047 Action: No operator action is required.
2048
2049
2050 act_ctl_.pl1
2051 act_ctl_: charged X available Y mins
2052
2053
2054 Stream: as severity0
2055
2056 Time: While system is running.
2057
2058 Meaning: X is the sum of virtual CPU time charged to all
2059 processes and Y is the total virtual CPU time used
2060 by all processes. This message logs detailed
2061 accounting information and appears whenever the
2062 message "act_ctl_: discrepancy of XX.XX mins"
2063 appears.
2064
2065 Action: No operator action is required.
2066
2067
2068 act_ctl_.pl1
2069 act_ctl_: discrepancy of XX.XX mins
2070
2071
2072 Stream: as severity1
2073
2074 Time: While system is running.
2075
2076 Meaning: The total time available from traffic control does
2077 not agree with the total time charged to users
2078 plus the Initializer time plus the idle time.
2079 Some process has escaped being accounted for.
2080
2081 Action: Contact the system programming staff._sa
2082
2083
2084 act_ctl_.pl1
2085 act_ctl_: Lock wait time exceeded. While
2086 destroying proc for NAME.PROJ
2087
2088
2089 Stream: as severity2
2090
2091 Time: While system is running.
2092
2093 Meaning: The accounting system was unable to lock the PDT
2094 entry for the user NAME in the project PROJ within
2095 its time limit usually five minutes This user
2096 attempted to log out or destroy a process. The
2097 entry was probably locked because a system
2098 administrator or daemon process locked the entry
2099 and then failed. The system attempts to continue.
2100
2101
2102 act_ctl_ 37 08/03/23 MR12.7^L
2103
2104
2105 Action: Contact the system programming staff._sa
2106
2107
2108 act_ctl_.pl1
2109 act_ctl_: MODE update: users = NN pf=XX
2110 vcpu=YY.Y rt=ZZ.Z MESSAGE
2111
2112
2113 Stream: as severity1
2114
2115 Time: While system is running.
2116
2117 Meaning: Periodically the accounting programs read and
2118 store the CPU usage for each user. This message
2119 is printed when the update completes. MODE may be
2120 'Automatic' in which case the update occurred at
2121 the normal system parameter time; 'Manual' where
2122 the normal update didn't occur; or 'Shift Cmnd'
2123 where the update occurred due to a shift command.
2124 XX is the number of page faults taken by
2125 Initializer for update. YY.Y is the virtual CPU
2126 time taken by Initializer for update. ZZ.Z is the
2127 real time taken by Initializer for update.
2128 MESSAGE may be one or both of the following
2129 strings: 'answer table locked' or 'installs
2130 pending'
2131
2132 Action: No operator action is required. The number of
2133 seconds between accounting updates is a system
2134 parameter that an installation may change; it is
2135 stored in the segment installation_parms.
2136
2137
2138
2139 act_ctl_.pl1
2140 act_ctl_: process XXXXXXXXXXXX for NAME.PROJ
2141 vanished
2142
2143
2144 Stream: as severity2
2145
2146 Time: While system is running.
2147
2148 Meaning: Traffic control cannot locate a process for a user
2149 who should have one according to accounting. The
2150 system attempts to run normally but this user is
2151 not charged. An attempt is made to bump the user
2152 in question. This may be the first indication
2153 that the segment >system_control_1>answer_table
2154 has been damaged.
2155
2156 Action: Note for system programmer action.
2157
2158
2159
2160 act_ctl_ 38 08/03/23 MR12.7^L
2161
2162
2163
2164
2165 act_ctl_.pl1
2166 act_ctl_: shutdown NNN WW.WW XX.XX YY.YY ZZ.ZZ
2167 HH:MM:SS $DDD.DD
2168
2169
2170 Stream: as severity1
2171
2172 Time: System shutdown.
2173
2174 Meaning: A successful shutdown of the accounting portion of
2175 the system has been accomplished. NNN logins were
2176 recorded for a total usage of HH:MM:SS of CPU
2177 time charged. The other numbers are of interest
2178 to system administrators and programmers. WW.WW
2179 is the average queue length XX.XX is the average
2180 eligible YY.YY is the thrashing index ZZ.ZZ is
2181 the average response and DDD.DD is the total
2182 dollar charge since startup. A shutdown of the
2183 hardcore system follows this message.
2184
2185 Action: No operator action is required.
2186
2187
2188 act_ctl_.pl1
2189 act_ctl_: STRING for USER.PROJ is negative NUM
2190 at logout; set it to zero.
2191
2192
2193
2194 Stream: as severity2
2195
2196 Time: While system is running.
2197
2198 Meaning: A counter value of STRING was decremented by 1 and
2199 went negative. It was noticed when attempting to
2200 log out USER on the PROJ project. This is a sign
2201 of possible damage to the PROJ pdt.
2202
2203 Action: Note for system programmer action.
2204
2205
2206 act_proc.pl1
2207 act_proc: from grab_aste ERRORMESSAGE
2208
2209
2210 Stream: BOS Typewriter Crashes system
2211
2212 Time: While system is running.
2213
2214 Meaning: In attempting to create a process the system
2215 could not force the PDS or descriptor segment of
2216
2217
2218 act_proc 39 08/03/23 MR12.7^L
2219
2220
2221 that process to be activated and held active.
2222 ERRORMESSAGE is an error_table_ message. This
2223 indicates a logic error in the supervisor or CPU
2224 or memory hardware problems.
2225
2226 Action: Follow normal recovery procedures.
2227
2228
2229 act_proc.pl1
2230 act_proc: KST size specified SIZE less than
2231 minimum MIN_SIZE. Creating process for GROUPID.
2232
2233
2234
2235 Stream: Logged in SYSERR log.
2236
2237 Time: While system is running.
2238
2239 Meaning: The project administrator or system
2240 administrator for user GROUPID set the kst_size
2241 parameter in the PDT to SIZE which is less than
2242 the valid minimum MIN_SIZE. The process is not
2243 created. Note that a process with MINIMUM KST
2244 size will probably not be of any use. The minimum
2245 useful KST size is on the order of MINIMUM + 50.
2246
2247 Action: Change the PMF/PDT.
2248
2249
2250 activate.pl1
2251 activate: activating into father PPPP
2252
2253
2254 Stream: BOS Typewriter Crashes system
2255
2256 Time: While system is running.
2257
2258 Meaning: The AST entry pointer returned by get_aste is
2259 identical to the AST entry pointer for the parent
2260 of the segment being activated. This indicates a
2261 logic error in the supervisor or CPU or memory
2262 hardware problems. BOS Typewriter Crashes
2263 systemes
2264
2265 Action: Follow normal recovery procedures.
2266
2267
2268 activate.pl1
2269 activate: error on deciduous dir NAME
2270
2271
2272 Stream: Logged in SYSERR log.
2273
2274
2275
2276 activate 40 08/03/23 MR12.7^L
2277
2278
2279 Time: While system is running.
2280
2281 Meaning: An attempt has been made to activate a deciduous
2282 segment or to activate a segment when the VTOCE's
2283 directory switch did not match the branch. A
2284 connection failure is returned to the user
2285 process. This information is logged for the use
2286 of system programmers.
2287
2288 Action: No operator action is required.
2289
2290
2291 activate.pl1
2292 activate: Setting damaged switch on NAME at VTOCX
2293 dskX_NNs. Filemap damaged.
2294
2295
2296 Stream: Logged in SYSERR log.
2297
2298 Time: While system is running.
2299
2300 Meaning: The segment's File Map in the VTOCE had an invalid
2301 checksum which indicates likely damage to the
2302 File Map. The segment is marked as damaged. It
2303 is possible that there is other damage on the
2304 physical volume due to invalid or reused disk
2305 addresses. The count of volume inconsistencies is
2306 incremented by 1.
2307
2308 Action: Examine the VTOCE for damage using dump_vtoce. If
2309 other damage is evident delete it using
2310 hp_delete_vtoce -clear and recover the segment.
2311 Run the physical volume scavenger as soon as
2312 possible to detect and correct other damage on the
2313 physical volume.
2314
2315
2316
2317 obs_reconfigure.pl1
2318 addcpu: Associative memories not enabled on CPU
2319 X.
2320
2321
2322 Stream: Initializer process output.
2323
2324 Time: In response to an operator command.
2325
2326 Meaning: The SDWAM and/or PTWAM on CPU X is not enabled.
2327 CPU X was not added.
2328
2329 Action: Set the appropriate associative memory switch on
2330 and try addcpu again.
2331
2332
2333
2334 addcpu 41 08/03/23 MR12.7^L
2335
2336
2337
2338
2339 obs_reconfigure.pl1
2340 addcpu: CPU X is already online.
2341
2342
2343 Stream: Initializer process output.
2344
2345 Time: In response to an operator command.
2346
2347 Meaning: A redundant addcpu X command was issued. No
2348 action was taken.
2349
2350 Action: Enter a corrected command line.
2351
2352
2353 obs_reconfigure.pl1
2354 addcpu: CPU X is not configured.
2355
2356
2357 Stream: Initializer process output.
2358
2359 Time: In response to an operator command.
2360
2361 Meaning: There is no CPU card for CPU X in the
2362 configuration deck. The CPU cannot be added.
2363
2364 Action: If the CPU name was mistyped enter a corrected
2365 command. If the configuration deck omitted the
2366 CPU card that CPU cannot be added until the
2367 system is shut down and the deck corrected.
2368
2369
2370
2371 obs_reconfigure.pl1
2372 addcpu: CPU X is not enabled at MEM Y.
2373
2374
2375 Stream: Initializer process output.
2376
2377 Time: In response to an operator command.
2378
2379 Meaning: CPU X cannot be added because the PORT ENABLE
2380 switch at MEM Y does not enable it.
2381
2382 Action: Fix the switches and try addcpu again.
2383
2384
2385 obs_reconfigure.pl1
2386 addcpu: CPU X is not in Multics mode.
2387
2388
2389 Stream: Initializer process output.
2390
2391
2392 addcpu 42 08/03/23 MR12.7^L
2393
2394
2395 Time: In response to an operator command.
2396
2397 Meaning: CPU X cannot be added because its mode switch is
2398 wrong.
2399
2400 Action: Fix the switch and try again.
2401
2402
2403 obs_reconfigure.pl1
2404 addcpu: Illegal command or subroutine argument.
2405 BLAH
2406
2407
2408 Stream: Initializer process output.
2409
2410 Time: In response to an operator command.
2411
2412 Meaning: Invalid input was typed.
2413
2414 Action: Enter a corrected command line.
2415
2416
2417 obs_reconfigure.pl1
2418 addcpu: Lockup fault trying to start CPU X.
2419
2420
2421 Stream: Initializer process output.
2422
2423 Time: In response to an operator command.
2424
2425 Meaning: This happens occasionally. The reason for it is
2426 unknown.
2427
2428 Action: Try addcpu a few more times.
2429
2430
2431 obs_reconfigure.pl1
2432 addcpu: No response from CPU X.
2433
2434
2435 Stream: Initializer process output.
2436
2437 Time: In response to an operator command.
2438
2439 Meaning: CPU X did not start up when commanded. It may be
2440 malfunctioning or in STEP.
2441
2442 Action: Check the switches. If any are wrong correct
2443 them and retry addcpu. Otherwise notify Field
2444 Engineering.
2445
2446
2447
2448
2449
2450 addcpu 43 08/03/23 MR12.7^L
2451
2452
2453
2454
2455 obs_reconfigure.pl1
2456 addcpu: Reconfiguration database is locked.
2457
2458
2459 Stream: Initializer process output.
2460
2461 Time: In response to an operator command.
2462
2463 Meaning: Another process is performing reconfiguration
2464 currently or a fault during reconfiguration has
2465 left the reconfiguration tables locked.
2466
2467 Action: If it is certain that no other process is
2468 reconfiguring and that the fault which
2469 interrupted reconfiguration has been cured the
2470 reconfigure$force_unlock command may be used to
2471 clear the lock at the direction of system staff.
2472
2473
2474
2475 obs_reconfigure.pl1
2476 addcpu: Startup fault trying to start CPU X.
2477
2478
2479 Stream: Initializer process output.
2480
2481 Time: In response to an operator command.
2482
2483 Meaning: This happens sometimes. Nobody knows why.
2484
2485 Action: Try again a few times.
2486
2487
2488 obs_reconfigure.pl1
2489 addcpu: The following switches on CPU X are set
2490 incorrectly:
2491 Fault Base
2492 Processor Number
2493 Port Assignment MEM Y
2494 Port Enable MEM Y
2495 Interlace MEM Y
2496 Size MEM Y
2497 Half/Full MEM Y
2498
2499
2500
2501 Stream: Initializer process output.
2502
2503 Time: In response to an operator command.
2504
2505 Meaning: The listed switches are set incorrectly.
2506
2507
2508 addcpu 44 08/03/23 MR12.7^L
2509
2510
2511 Action: Correct the switches and try addcpu again.
2512
2513
2514 obs_reconfigure.pl1
2515 addcpu: Trouble fault trying to start CPU X.
2516
2517
2518 Stream: Initializer process output.
2519
2520 Time: In response to an operator command.
2521
2522 Meaning: This happens sometimes. Nobody knows why.
2523
2524 Action: Try again a few times.
2525
2526
2527 obs_reconfigure.pl1
2528 addcpu: Wrong number of arguments supplied.
2529
2530
2531 Stream: Initializer process output.
2532
2533 Time: In response to an operator command.
2534
2535 Meaning: Invalid input was typed.
2536
2537 Action: Enter a corrected command line.
2538
2539
2540 obs_reconfigure.pl1
2541 Added frame XXX.
2542
2543
2544 Stream: Initializer process output.
2545
2546 Time: In response to an operator command.
2547
2548 Meaning: This is the response to a successful addmain XXX
2549 command.
2550
2551 Action: No operator action is required.
2552
2553
2554 obs_reconfigure.pl1
2555 Added frames XXX thru YYY.
2556
2557
2558 Stream: Initializer process output.
2559
2560 Time: In response to an operator command.
2561
2562 Meaning: This is the response to a successful addmain XXX N
2563 command.
2564
2565
2566 Added 45 08/03/23 MR12.7^L
2567
2568
2569 Action: No operator action is required.
2570
2571
2572 disk_table_.pl1
2573 added pv PVNAME to mounted lv LVNAME.
2574
2575
2576 Stream: Initializer process output.
2577
2578 Time: While system is running.
2579
2580 Meaning: An av command was used to increase the size of a
2581 mounted volume.
2582
2583 Action: No operator action is required.
2584
2585
2586 obs_reconfigure.pl1
2587 Added SCU X and its memory.
2588
2589
2590 Stream: Initializer process output.
2591
2592 Time: In response to an operator command.
2593
2594 Meaning: This is the response to a successful addmem X
2595 command.
2596
2597 Action: No operator action is required.
2598
2599
2600 obs_reconfigure.pl1
2601 Added SCU's X and Y interlaced and their memory.
2602
2603
2604 Stream: Initializer process output.
2605
2606 Time: In response to an operator command.
2607
2608 Meaning: This is the response to a successful addmem X
2609 command when SCU's X and Y have their memories
2610 interlaced.
2611
2612 Action: No operator action is required.
2613
2614
2615 obs_reconfigure.pl1
2616 addmain: Illegal command or subroutine argument.
2617 BLAH
2618
2619
2620 Stream: Initializer process output.
2621
2622
2623
2624 addmain 46 08/03/23 MR12.7^L
2625
2626
2627 Time: In response to an operator command.
2628
2629 Meaning: Invalid input was typed.
2630
2631 Action: Enter a corrected command line.
2632
2633
2634 obs_reconfigure.pl1
2635 addmain: Reconfiguration database is locked.
2636
2637
2638 Stream: Initializer process output.
2639
2640 Time: In response to an operator command.
2641
2642 Meaning: Another process is performing reconfiguration
2643 currently or a fault during reconfiguration has
2644 left the reconfiguration tables locked.
2645
2646 Action: If it is certain that no other process is
2647 reconfiguring and that the fault which
2648 interrupted reconfiguration has been cured the
2649 reconfigure$force_unlock command may be used to
2650 clear the lock at the direction of system staff.
2651
2652
2653
2654 obs_reconfigure.pl1
2655 addmain: Request is not within range of a single
2656 controller. MAIN XXX
2657
2658
2659 Stream: Initializer process output.
2660
2661 Time: In response to an operator command.
2662
2663 Meaning: An addmain command must specify memory completely
2664 within the range of a single controller.
2665
2666 Action: Enter a corrected command line.
2667
2668
2669 obs_reconfigure.pl1
2670 addmain: Wrong number of arguments supplied.
2671
2672
2673 Stream: Initializer process output.
2674
2675 Time: In response to an operator command.
2676
2677 Meaning: Invalid input was typed.
2678
2679 Action: Enter a corrected command line.
2680
2681
2682 addmem 47 08/03/23 MR12.7^L
2683
2684
2685
2686
2687 add_scu.pl1
2688 addmem: Added MEM X.
2689
2690
2691 Stream: BOS Typewriter.
2692
2693 Time: In response to an operator command.
2694
2695 Meaning: The system control unit X has been added.
2696
2697 Action: No operator action is required.
2698
2699
2700 obs_reconfigure.pl1
2701 addmem: Illegal command or subroutine argument.
2702 BLAH
2703
2704
2705 Stream: Initializer process output.
2706
2707 Time: In response to an operator command.
2708
2709 Meaning: Invalid input was typed.
2710
2711 Action: Enter a corrected command line.
2712
2713
2714 obs_reconfigure.pl1
2715 addmem: MEM Y cannot be accessed by CPU X.
2716
2717
2718 Stream: Initializer process output.
2719
2720 Time: In response to an operator command.
2721
2722 Meaning: CPU X is unable to access MEM Y. The
2723 configuration deck may be incorrect or the CPU
2724 and SCU switches may be in the wrong settings.
2725
2726 Action: Check the switches and make sure that they agree
2727 with the configuration deck. Then try addmem
2728 again.
2729
2730
2731
2732 obs_reconfigure.pl1
2733 addmem: MEM Y does not have mask assigned to CPU
2734 X.
2735
2736
2737 Stream: Initializer process output.
2738
2739
2740 addmem 48 08/03/23 MR12.7^L
2741
2742
2743 Time: In response to an operator command.
2744
2745 Meaning: The MASK/PORT ASSIGNMENT 4MW SCU or EXECUTE
2746 INTERRUPT MASK ASSIGNMENT 6000 SCU switches on
2747 SCU Y are incorrect.
2748
2749 Action: Fix the switches and try addmem again.
2750
2751
2752 obs_reconfigure.pl1
2753 addmem: MEM Y has duplicate mask assignments to
2754 CPU X.
2755
2756
2757 Stream: Initializer process output.
2758
2759 Time: In response to an operator command.
2760
2761 Meaning: The MASK/PORT ASSIGNMENT 4MW SCU or EXECUTE
2762 INTERRUPT MASK ASSIGNMENT 6000 SCU switches on
2763 SCU Y are incorrect.
2764
2765 Action: Fix the switches and try addmem again.
2766
2767
2768 obs_reconfigure.pl1
2769 addmem: MEM Y has mask Z assigned to non-CPU
2770 port.
2771
2772
2773 Stream: Initializer process output.
2774
2775 Time: In response to an operator command.
2776
2777 Meaning: The MASK/PORT ASSIGNMENT 4MW SCU or EXECUTE
2778 INTERRUPT MASK ASSIGNMENT 6000 SCU switches on
2779 SCU Y are incorrect.
2780
2781 Action: Fix the switches and try addmem again.
2782
2783
2784 obs_reconfigure.pl1
2785 addmem: MEM Y is already online.
2786
2787
2788 Stream: Initializer process output.
2789
2790 Time: In response to an operator command.
2791
2792 Meaning: An addmem Y command was typed when SCU Y was
2793 already online.
2794
2795 Action: No operator action is required.
2796
2797
2798 addmem 49 08/03/23 MR12.7^L
2799
2800
2801
2802
2803 obs_reconfigure.pl1
2804 addmem: MEM Y is not configured.
2805
2806
2807 Stream: Initializer process output.
2808
2809 Time: In response to an operator command.
2810
2811 Meaning: There is no MEM card in the configuration for MEM
2812 y. The SCU cannot be added.
2813
2814 Action: If the SCU name was mistyped enter a corrected
2815 command. If the configuration deck omitted the
2816 MEM card the SCU cannot be added until the system
2817 is shut down and the deck corrected.
2818
2819
2820
2821 obs_reconfigure.pl1
2822 addmem: MEM Y is not enabled on CPU X.
2823
2824
2825 Stream: Initializer process output.
2826
2827 Time: In response to an operator command.
2828
2829 Meaning: The ENABLE switch on the CONFIGURATION panel of
2830 CPU X does not enable SCU Y. The memory cannot be
2831 added.
2832
2833 Action: Fix the switches and try addmem again.
2834
2835
2836 obs_reconfigure.pl1
2837 addmem: MEM Y is not in PROGRAM mode.
2838
2839
2840 Stream: Initializer process output.
2841
2842 Time: In response to an operator command.
2843
2844 Meaning: The MODE switch on 4MW SCU Y is not in PROGRAM
2845 mode. The SCU cannot be added.
2846
2847 Action: Fix the switches and try addmem again.
2848
2849 Action: No operator action is required.
2850
2851
2852 obs_reconfigure.pl1
2853 addmem: Reconfiguration database is locked.
2854
2855
2856 addmem 50 08/03/23 MR12.7^L
2857
2858
2859 Stream: Initializer process output.
2860
2861 Time: In response to an operator command.
2862
2863 Meaning: Another process is performing reconfiguration
2864 currently or a fault during reconfiguration has
2865 left the reconfiguration tables locked.
2866
2867 Action: If it is certain that no other process is
2868 reconfiguring and that the fault which
2869 interrupted reconfiguration has been cured the
2870 reconfigure$force_unlock command may be used to
2871 clear the lock at the direction of system staff.
2872
2873
2874
2875 obs_reconfigure.pl1
2876 addmem: Size of MEM Y disagrees with CPU
2877 switches.
2878
2879
2880 Stream: Initializer process output.
2881
2882 Time: In response to an operator command.
2883
2884 Meaning: The memory size on the configuration card for MEM
2885 Y disagrees with the size on the CPU switches.
2886
2887 Action: If the switches are incorrect fix them and try
2888 addmem again. If the configuration deck is
2889 incorrect the system must be shut down and the
2890 deck corrected before the SCU can be added.
2891
2892
2893
2894 obs_reconfigure.pl1
2895 addmem: Switches for MEM Y set improperly on CPU
2896 X.
2897
2898
2899 Stream: Initializer process output.
2900
2901 Time: In response to an operator command.
2902
2903 Meaning: The ADDRESS ASSIGNMENT switches for SCU Y are
2904 incorrect on CPU X.
2905
2906 Action: Correct the switches and try addmem again.
2907
2908
2909 obs_reconfigure.pl1
2910 addmem: Wrong number of arguments supplied.
2911
2912
2913
2914 addmem 51 08/03/23 MR12.7^L
2915
2916
2917 Stream: Initializer process output.
2918
2919 Time: In response to an operator command.
2920
2921 Meaning: Invalid input was typed.
2922
2923 Action: Enter a corrected command line.
2924
2925
2926 admin_.pl1
2927 admin_: abs ABS_FUNCTION: Expected argument
2928 missing. After PREV_ARG.
2929
2930
2931 Stream: as severity 1
2932
2933 Time: In response to an operator abs command.
2934
2935 Meaning: A required value to a control argument supplied in
2936 the "abs" command line is missing.
2937
2938 Action: Reenter corrected command line.
2939
2940
2941 admin_.pl1
2942 admin_: abs: ABS_FUNCT: error: absentee not up
2943
2944
2945 Stream: as severity 1
2946
2947 Time: In response to an operator command.
2948
2949 Meaning: An abs command was given but the absentee
2950 facility had never been started up. No action was
2951 taken on the command.
2952
2953 Action: Type abs start to start up the absentee facility.
2954
2955
2956 admin_.pl1
2957 admin_: abs: ABS_FUNCT: error: Invalid abs job
2958 selection argument: SSSS
2959
2960
2961 Stream: as severity 1
2962
2963 Time: In response to an operator command.
2964
2965 Meaning: The job selection argument SSSS is not recognized
2966 as valid.
2967
2968 Action: Type "help abs" for details of the abs command
2969 usage and try again.
2970
2971
2972 admin_ 52 08/03/23 MR12.7^L
2973
2974
2975
2976
2977 admin_.pl1
2978 admin_: abs: ABS_FUNCT: error: Job in absentee
2979 slot X does not match absin entry name SSSS
2980
2981
2982 Stream: as severity 1
2983
2984 Time: In response to an operator command.
2985
2986 Meaning: The entry name SSSS of the absin of the job
2987 running in specified absentee slot of absX does
2988 not match the specified absin entry name.
2989
2990 Action: Recheck job specifications and try again.
2991
2992
2993 admin_.pl1
2994 admin_: abs: ABS_FUNCT: error: Job in absentee
2995 slot X does not match absin path
2996 DIR_PATH>ENTRY_NAME
2997
2998
2999 Stream: as severity 1
3000
3001 Time: In response to an operator command.
3002
3003 Meaning: The pathname of the absin of the job running in
3004 specified absentee slot of absX does not match the
3005 specified absin pathname.
3006
3007 Action: Recheck job specifications and try again.
3008
3009
3010 admin_.pl1
3011 admin_: abs: ABS_FUNCT: error: Job in absentee
3012 slot X does not match request ID YYYY
3013
3014
3015 Stream: as severity 1
3016
3017 Time: In response to an operator command.
3018
3019 Meaning: The ID of the job running in specified absentee
3020 slot of absX does not match the specified ID of
3021 YYYY.
3022
3023 Action: Recheck job specifications and try again.
3024
3025
3026 admin_.pl1
3027
3028
3029
3030 admin_ 53 08/03/23 MR12.7^L
3031
3032
3033 admin_: abs: ABS_FUNCT: error: Job in absentee
3034 slot X is not from queue DDDD
3035
3036
3037 Stream: as severity 1
3038
3039 Time: In response to an operator command.
3040
3041 Meaning: The queue of the absin of the job running in
3042 specified absentee slot of absX does not match the
3043 queue number DDDD.
3044
3045 Action: Recheck job specifications and try again.
3046
3047
3048 admin_.pl1
3049 admin_: abs: ABS_FUNCT: error: Job in absentee
3050 slot X is not from sender SSSS
3051
3052
3053 Stream: as severity 1
3054
3055 Time: In response to an operator command.
3056
3057 Meaning: The sender of the absin of the job running in
3058 specified absentee slot of absX does not match the
3059 specified sender SSSS.
3060
3061 Action: Recheck job specifications and try again.
3062
3063
3064 admin_.pl1
3065 admin_: abs: ABS_FUNCT: error: Job in absentee
3066 slot X is not from user NAME.PROJ
3067
3068
3069 Stream: as severity 1
3070
3071 Time: In response to an operator command.
3072
3073 Meaning: The job running in specified absentee slot of absX
3074 is not from specified user NAME.PROJ.
3075
3076 Action: Recheck job specifications and try again.
3077
3078
3079 admin_.pl1
3080 admin_: abs: ABS_FUNCT: error: More than one
3081 specification of an attribute is present: SSSS
3082
3083
3084 Stream: as severity 1
3085
3086
3087
3088 admin_ 54 08/03/23 MR12.7^L
3089
3090
3091 Time: In response to an operator command.
3092
3093 Meaning: The SSSS attribute has already been specified to
3094 select an absentee job on the operator abs
3095 command. An attribute can only be used once.
3096
3097 Action: Enter a corrected command line.
3098
3099
3100 admin_.pl1
3101 admin_: abs: ABS_FUNCT: error: No job in
3102 absentee slot X status= SSSS.
3103
3104
3105 Stream: as severity 1
3106
3107 Time: In response to an operator command.
3108
3109 Meaning: The absentee slot absX has an entry status of SSSS
3110 indicating that no user is using it.
3111
3112 Action: Enter a corrected command line.
3113
3114
3115 admin_.pl1
3116 admin_: abs: ABS_FUNCT: error: Personid NAME >
3117 22 characters.
3118
3119
3120 Stream: as severity 1
3121
3122 Time: In response to an operator command.
3123
3124 Meaning: The "abs ABS_FUNCT" operator command specified a
3125 user name that is longer than 22 characters.
3126
3127 Action: Enter a corrected command line.
3128
3129
3130 admin_.pl1
3131 admin_: abs: ABS_FUNCT: error: Projectid SSSS
3132 is longer than 9 characters.
3133
3134
3135 Stream: as severity 1
3136
3137 Time: In response to an operator command.
3138
3139 Meaning: The "abs ABS_FUNCT" operator command incorrectly
3140 specified a project name that is longer than 9
3141 characters.
3142
3143 Action: Enter a corrected command line.
3144
3145
3146 admin_ 55 08/03/23 MR12.7^L
3147
3148
3149
3150
3151 admin_.pl1
3152 admin_: abs: ABS_FUNCT: error: Relative
3153 pathnames not allowed: SSSS
3154
3155
3156 Stream: as severity 1
3157
3158 Time: In response to an operator command.
3159
3160 Meaning: The pathname of the absin was expected and it must
3161 be an absolute pathname starting with a ">"
3162 character.
3163
3164 Action: Enter a corrected command line.
3165
3166
3167 admin_.pl1
3168 admin_: abs: ABS_FUNCT: error: Selection
3169 arguments matched no running absentee jobs.
3170
3171
3172 Stream: as severity 1
3173
3174 Time: In response to an operator command.
3175
3176 Meaning: No running job was found that matched the
3177 selection arguments supplied on the abs command
3178 line.
3179
3180 Action: Recheck job specifications and try again.
3181
3182
3183 admin_.pl1
3184 admin_: abs: ABS_FUNCT: error: SSSS is not a
3185 valid Person.Project.
3186
3187
3188 Stream: as severity 1
3189
3190 Time: In response to an operator command.
3191
3192 Meaning: The "abs ABS_FUNCT" operator command did not
3193 specify a valid Person.Project in the string SSSS.
3194
3195 Action: Enter a corrected command line.
3196
3197
3198 admin_.pl1
3199 admin_: abs: ABS_FUNCT: error: The absN
3200 argument is not valid.
3201
3202
3203
3204 admin_ 56 08/03/23 MR12.7^L
3205
3206
3207 Stream: as severity 1
3208
3209 Time: In response to an operator command.
3210
3211 Meaning: The "abs ABS_FUNCT" operator command cannot allow
3212 use of the absN argument for job selection.
3213
3214 Action: Enter a corrected command line.
3215
3216
3217 admin_.pl1
3218 admin_: abs: ABS_FUNCT: error: User name not
3219 ""*"" must be given.
3220
3221
3222 Stream: as severity 1
3223
3224 Time: In response to an operator command.
3225
3226 Meaning: The "abs ABS_FUNCT" operator command requires that
3227 a user name be supplied. Cannot use "*".
3228
3229 Action: Enter a corrected command line.
3230
3231
3232 admin_.pl1
3233 admin_: abs: ABS_FUNCT: error: User name must
3234 be given.
3235
3236
3237 Stream: as severity 1
3238
3239 Time: In response to an operator command.
3240
3241 Meaning: The "abs ABS_FUNCT" operator command requires that
3242 a user name be supplied.
3243
3244 Action: Enter a corrected command line.
3245
3246
3247 admin_.pl1
3248 admin_: abs: ABS_FUNCT: Invalid queue number
3249 DDDD
3250
3251
3252 Stream: as severity 1
3253
3254 Time: In response to an operator command.
3255
3256 Meaning: The value after the -queue job selection argument
3257 is invalid. It must be the strings "fg" or
3258 "foreground" or a between the values of 1 and 4
3259 inclusive.
3260
3261
3262 admin_ 57 08/03/23 MR12.7^L
3263
3264
3265 Action: Enter a corrected command line.
3266
3267
3268 admin_.pl1
3269 admin_: abs: ABS_FUNCT: No job selection
3270 arguments given.
3271
3272
3273 Stream: as severity 1
3274
3275 Time: In response to an operator command.
3276
3277 Meaning: After processing the arguments on the "abs
3278 abs_funct" operator command no job selection
3279 arguments were encountered.
3280
3281 Action: Type "help abs" for details of the abs command
3282 usage and try again.
3283
3284
3285 admin_.pl1
3286 admin_: abs: absentee not up and will not be
3287 started automatically
3288
3289
3290 Stream: as severity 1
3291
3292 Time: When operator entered "abs stop" before absentee
3293 facility was started.
3294
3295 Meaning: The command can be entered at standard to prevent
3296 the absentee facility from starting up
3297 automatically after a "startup" command is used.
3298
3299 Action: No operator action is required.
3300
3301
3302 admin_.pl1
3303 admin_: abs: All absentee processes have run to
3304 completion.
3305
3306
3307 Stream: as severity 1
3308
3309 Time: When shutting down the absentee facility.
3310
3311 Meaning: This message is printed after the operator has
3312 issued an abs stop command or the system has
3313 issued an automatic abs stop prior to shutdown.
3314 The system allows 30 minutes for all absentee jobs
3315 to finish before logging them out then prints the
3316 message.
3317
3318
3319
3320 admin_ 58 08/03/23 MR12.7^L
3321
3322
3323 Action: It is now safe to proceed with the shutdown.
3324
3325
3326 admin_.pl1
3327 admin_: abs: auto abs stop will be at MM/DD/YY
3328 HHMM.T
3329
3330
3331 Stream: as severity 1
3332
3333 Time: In response to an operator down command or at
3334 startup.
3335
3336 Meaning: This is the response to a down command if the
3337 absentee facility is running or to an abs start
3338 command if the absentee is brought up after a down
3339 time has been set. The time for an automatic abs
3340 stop is 20 minutes before the system is to shut
3341 down. An "abs stop now" is done 10 minutes after
3342 the scheduled shutdown. Refer also to the stop
3343 command description.
3344
3345 Action: No operator action is required.
3346
3347
3348 admin_.pl1
3349 admin_: abs: Bumping all remaining absentee
3350 processes.
3351
3352
3353 Stream: as severity 1
3354
3355 Time: System shutdown.
3356
3357 Meaning: The absentee facility waits 30 minutes for all
3358 absentee jobs to run to completion after the abs
3359 stop command has been issued. Then it types this
3360 message and bumps them all. Refer also to the
3361 stop command description.
3362
3363 Action: No operator action is required.
3364
3365
3366 admin_.pl1
3367 admin_: abs: cpu_limit MMMM queues 1-4: WW
3368 XX YY ZZ seconds
3369
3370
3371 Stream: as severity 1
3372
3373 Time: In response to "abs cpu_limit" command without
3374 arguments.
3375
3376
3377
3378 admin_ 59 08/03/23 MR12.7^L
3379
3380
3381 Meaning: Informative message indicating current values of
3382 cpu_limit for each absentee queue. MMM is the
3383 mode "auto" or "manual".
3384
3385 Action: No operator action is required.
3386
3387
3388 admin_.pl1
3389 admin_: abs: cpu_limit: error: Usage is: "abs
3390 cpu_limit l1l2l3l4" limits in seconds
3391
3392
3393 Stream: as severity 1
3394
3395 Time: In response to an operator command.
3396
3397 Meaning: Informative message that is displayed when an
3398 operator "abs cpu_limit" command without arguments
3399 is entered.
3400
3401 Action: Enter a corrected command line.
3402
3403
3404 admin_.pl1
3405 admin_: abs: error: The abs CCCC command can
3406 not be used before answering service startup.
3407
3408
3409 Stream: as severity 1
3410
3411 Time: In response to an operator abs command.
3412
3413 Meaning: Only the "abs stop" command may be given before
3414 the answering service starts up. This allows the
3415 operator to stop the absentee facility before the
3416 system finishes initialzation.
3417
3418 Action: Enter a corrected command line.
3419
3420
3421 admin_.pl1
3422 admin_: abs: error: unknown absentee command
3423 WXYZ
3424
3425
3426 Stream: as severity 1
3427
3428 Time: In response to an operator command.
3429
3430 Meaning: The operator typed abs WXYZ where WXYZ was
3431 unrecognizable to the system. No action was
3432 taken.
3433
3434
3435
3436 admin_ 60 08/03/23 MR12.7^L
3437
3438
3439 Action: Enter a corrected command line.
3440
3441
3442 admin_.pl1
3443 admin_: abs: ERROR_TABLE_MESSAGE PATHNAME
3444
3445
3446 Stream: as severity 1
3447
3448 Time: In response to the operator abs command.
3449
3450 Meaning: The ERROR_TABLE_MESSAGE was encountered when
3451 trying to expand the PATHNAME supplied in the
3452 operator abs command line.
3453
3454 Action: Enter a corrected command line.
3455
3456
3457 admin_.pl1
3458 admin_: abs: list: error: No job in absentee
3459 slot X.
3460
3461
3462 Stream: as severity 1
3463
3464 Time: In response to an operator command.
3465
3466 Meaning: The absentee slot absX does not exist.
3467
3468 Action: Enter a corrected command line.
3469
3470
3471 admin_.pl1
3472 admin_: abs: list: error: The absN argument
3473 cannot be used when absentee is not up.
3474
3475
3476 Stream: as severity 1
3477
3478 Time: $reponse
3479
3480 Meaning: Cannot use the "absN" argument to select absentee
3481 jobs to list until the absentee facility has been
3482 started.
3483
3484 Action: Use other job selection criteria or type "abs
3485 start" and try again.
3486
3487
3488 admin_.pl1
3489 admin_: abs: maxq MMMM: Q
3490
3491
3492
3493
3494 admin_ 61 08/03/23 MR12.7^L
3495
3496
3497 Stream: as severity 1
3498
3499 Time: In response to "abs maxq" without arguments.
3500
3501 Meaning: Informative message indicating current status of
3502 maxq and queue last searched Q. MMMM is the
3503 mode "auto" or "manual".
3504
3505 Action: No operator action is required.
3506
3507
3508 admin_.pl1
3509 admin_: abs: maxq: error: abs maxqueue has
3510 invalid value: XXX
3511
3512
3513 Stream: as severity 1
3514
3515 Time: In response to an operator command.
3516
3517 Meaning: An abs maxq or abs start command had as an
3518 argument something that was not a number or was
3519 too big or was a negative number. No action is
3520 taken.
3521
3522 Action: Enter a corrected command line.
3523
3524
3525 admin_.pl1
3526 admin_: abs: maxu MMMM: UUUU
3527
3528
3529 Stream: as severity 1
3530
3531 Time: In response to "abs maxu" operator command without
3532 arguments.
3533
3534 Meaning: Informative message indicating current status of
3535 maxu and maximum absentee users allowed. MMMM is
3536 the mode "auto" or "manual". UUUU is the
3537 load_units.
3538
3539 Action: No operator action is required.
3540
3541
3542 admin_.pl1
3543 admin_: abs: maxu: error: abs maxusers may not
3544 be greater than system maxusers: SSSS
3545
3546
3547 Stream: as severity 1
3548
3549 Time: In response to an operator command.
3550
3551
3552 admin_ 62 08/03/23 MR12.7^L
3553
3554
3555 Meaning: The argument SSSS to the operator "abs maxu"
3556 command cannot be greater than the maximum allowed
3557 users that can be on the system.
3558
3559 Action: Enter a corrected command line.
3560
3561
3562 admin_.pl1
3563 admin_: abs: maxu: error: abs maxusers may not
3564 be negative: SSSS
3565
3566
3567 Stream: as severity 1
3568
3569 Time: In response to an operator command.
3570
3571 Meaning: The argument SSSS to the operator "abs maxu"
3572 command was not a positive numeric or the string
3573 "auto". The numeric value is in tenths of a load
3574 unit.
3575
3576 Action: Enter a corrected command line.
3577
3578
3579 admin_.pl1
3580 admin_: abs: maxu: error: abs maxusers must be
3581 numeric or "auto": SSSS
3582
3583
3584 Stream: as severity 1
3585
3586 Time: In response to an operator command.
3587
3588 Meaning: The argument SSSS to the operator "abs maxu"
3589 command was not a positive numeric or the string
3590 "auto". The numeric value is in tenths of a load
3591 unit.
3592
3593 Action: Enter a corrected command line.
3594
3595
3596 admin_.pl1
3597 admin_: abs: qres MMMM: WW XX YY ZZ
3598
3599
3600 Stream: as severity 1
3601
3602 Time: In response to "abs maxq" without arguments.
3603
3604 Meaning: Informative message indicating current status of
3605 absentee queue reservation for each queue. MMMM
3606 is the mode "auto" or "manual".
3607
3608
3609
3610 admin_ 63 08/03/23 MR12.7^L
3611
3612
3613 Action: No operator action is required.
3614
3615
3616 admin_.pl1
3617 admin_: abs: qres: error: abs qres has invalid
3618 value: DDDD
3619
3620
3621 Stream: as severity 1
3622
3623 Time: In response to an operator command.
3624
3625 Meaning: An invalid qres argument was detected in an
3626 operator "abs qres" command. The argument must be
3627 "auto" or a positive decimal number.
3628
3629 Action: Enter a corrected command line.
3630
3631
3632 admin_.pl1
3633 admin_: abs: queue limits: WW XX YY ZZ
3634
3635
3636 Stream: as severity 1
3637
3638 Time: In response to "abs qres" operator command.
3639
3640 Meaning: Informative message indicating the current queue
3641 reservation limits.
3642
3643 Action: No operator action is required.
3644
3645
3646 admin_.pl1
3647 admin_: abs: Queue errors *=dropped:
3648 admin_: abs: FG 0 1 2 3 4
3649 admin_: abs: TT VV WW XX YY ZZ
3650 admin_: abs: * * * * * *
3651
3652
3653
3654 Stream: as severity 1
3655
3656 Time: In response to "abs queue" operator command.
3657
3658 Meaning: Displays the errors for each queue and indicates
3659 which one has been dropped. If none have been
3660 dropped the last line will not be displayed nor
3661 will the string "*=dropped" appear in the first
3662 line.
3663
3664 Action: Contact the system programming staff.
3665
3666
3667
3668 admin_ 64 08/03/23 MR12.7^L
3669
3670
3671
3672
3673 admin_.pl1
3674 admin_: abs: release: error: Job in absentee
3675 slot X is not suspended.
3676
3677
3678 Stream: as severity 1
3679
3680 Time: In response to an operator command.
3681
3682 Meaning: The specified job running in absentee slot of absX
3683 is not suspended so a release does not apply.
3684
3685 Action: Recheck job specifications and try again.
3686
3687
3688 admin_.pl1
3689 admin_: abs: release: error: Selection
3690 arguments matched no deferred or suspended
3691 absentee requests.
3692
3693
3694 Stream: as severity 1
3695
3696 Time: In response to an operator command.
3697
3698 Meaning: No suspended or deferred job was found to release
3699 with the arguments supplied on the abs release
3700 command line.
3701
3702 Action: Recheck job specifications and try again.
3703
3704
3705 admin_.pl1
3706 admin_: abs: resetting auto abs stop
3707
3708
3709 Stream: as severity 1
3710
3711 Time: In response to an operator abs stop command.
3712
3713 Meaning: An abs stop command overrides an automatic abs
3714 stop that was set up by a down command.
3715
3716 Action: No operator action is required.
3717
3718
3719 admin_.pl1
3720 admin_: abs: start: error: absentee already up
3721
3722
3723 Stream: as severity 1
3724
3725
3726 admin_ 65 08/03/23 MR12.7^L
3727
3728
3729 Time: In response to an operator abs start command.
3730
3731 Meaning: abs start was typed twice. No action was taken on
3732 the second issuance of the command.
3733
3734 Action: No operator action is required.
3735
3736
3737 admin_.pl1
3738 admin_: abs: start: error: absentee not up.
3739 cannot restart queue X
3740
3741
3742 Stream: as severity 1
3743
3744 Time: In response to an operator command.
3745
3746 Meaning: Cannot use the "abs start queue" command until the
3747 absentee facility has been started.
3748
3749 Action: Issue the "abs start" command and try again.
3750
3751
3752 admin_.pl1
3753 admin_: abs: start: error: invalid queue to be
3754 restarted X
3755
3756
3757 Stream: as severity 1
3758
3759 Time: In response to an operator command.
3760
3761 Meaning: An invalid queue number was specified in an
3762 operator "abs start queue" command line. It must
3763 be between 1 and 4 inclusive.
3764
3765 Action: Enter a corrected command line.
3766
3767
3768 admin_.pl1
3769 admin_: abs: start: error: system coming down
3770 soon: no abs start
3771
3772
3773 Stream: as severity 1
3774
3775 Time: In response to an operator command.
3776
3777 Meaning: The system is shutting down within 30 minutes so
3778 the absentee facility will not be started.
3779
3780 Action: No operator action is required.
3781
3782
3783
3784 admin_ 66 08/03/23 MR12.7^L
3785
3786
3787
3788
3789 admin_.pl1
3790 admin_: abs: stop: error: abs stop queue only
3791 works after answering service startup
3792
3793
3794 Stream: as severity 1
3795
3796 Time: In response to an operator abs stop queue command.
3797
3798 Meaning: The answering service must complete initialization
3799 before the "abs stop queue" command can be used.
3800
3801 Action: Allow the system to complete initialization and
3802 try again.
3803
3804
3805 admin_.pl1
3806 admin_: abs: stop: error: absentee stop in
3807 progress
3808
3809
3810 Stream: as severity 1
3811
3812 Time: In response to an operator command.
3813
3814 Meaning: An abs start abs stop abs maxu abs maxq or
3815 down command was issued while the absentee
3816 facility was in the process of shutting down.
3817
3818 Action: Wait for the message that all absentee processes
3819 have run to completion then reissue the command.
3820
3821
3822
3823 admin_.pl1
3824 admin_: abs: stop: error: invalid queue to be
3825 stopped: DDDD
3826
3827
3828 Stream: as severity 1
3829
3830 Time: In response to an operator "abs stop queue"
3831 command.
3832
3833 Meaning: The value of the queue number was not within the
3834 values of 1 and 4 inclusive.
3835
3836 Action: Enter a corrected command line.
3837
3838
3839 admin_.pl1
3840
3841
3842 admin_ 67 08/03/23 MR12.7^L
3843
3844
3845 admin_: abs: stop: error: missing argument:
3846 queue to be stopped
3847
3848
3849 Stream: as severity 1
3850
3851 Time: In response to an operator "abs stop queue"
3852 command.
3853
3854 Meaning: The "abs stop queue" command was entered without
3855 supplying the number of the queue to be stopped.
3856
3857 Action: Enter a corrected command line.
3858
3859
3860 admin_.pl1
3861 admin_: abs: stop: error: unknown argument
3862 SSSS
3863
3864
3865 Stream: as severity 1
3866
3867 Time: In response to an operator "abs stop" command.
3868
3869 Meaning: An unknown argument SSSS was supplied to the
3870 "abs stop" command.
3871
3872 Action: Type "help abs" for details of the abs command and
3873 try again.
3874
3875
3876 admin_.pl1
3877 admin_: abs: suspend: error: Job in absentee
3878 slot X is already suspended.
3879
3880
3881 Stream: as severity 1
3882
3883 Time: In response to an operator command.
3884
3885 Meaning: The specified job running in absentee slot of absX
3886 is already suspended and cannot be suspended
3887 again.
3888
3889 Action: Recheck job specifications and try again.
3890
3891
3892 admin_.pl1
3893 admin_: abs: Warning: cpu limits are in
3894 seconds. You just set queue QQ limit to LLLL
3895 seconds.
3896
3897
3898
3899
3900 admin_ 68 08/03/23 MR12.7^L
3901
3902
3903 Stream: as severity 1
3904
3905 Time: In response to "abs cpu_limit" command with
3906 arguments.
3907
3908 Meaning: The cpu_limit LLLL for queue QQ is below 60
3909 seconds which is likely to be a mistake. The
3910 value already given will be still be accepted.
3911
3912 Action: Reenter the command with corrected values if
3913 originally incorrect.
3914
3915
3916 admin_.pl1
3917 admin_: abs: Zero errors on all absentee queues.
3918
3919
3920 Stream: as severity 1
3921
3922 Time: In response to "abs queue" operator command.
3923
3924 Meaning: Informative message which indicates that no queue
3925 has been dropped and no errors recorded for any
3926 queue.
3927
3928 Action: No operator action is required.
3929
3930
3931 admin_.pl1
3932 admin_: bump: USER.PROJECT bumped.
3933
3934
3935 Stream: as severity 1
3936
3937 Time: In response to the bump command or a system
3938 shutdown.
3939
3940 Meaning: The specified user has been notified that he or
3941 she must get off the system. If a grace time was
3942 specified the user is allowed that amount of time
3943 to logout. Otherwise the user is removed from
3944 the system immediately.
3945
3946 Action: No operator action is required.
3947
3948
3949 admin_.pl1
3950 admin_: COMMAND: error: Invalid FNP tag: X
3951
3952
3953 Stream: as severity 1
3954
3955
3956
3957
3958 admin_ 69 08/03/23 MR12.7^L
3959
3960
3961 Time: Response to an operator "load_fnp" "fdump_fnp"
3962 "dump_fnp" "start_fnp" or "stop_fnp" command.
3963
3964 Meaning: The supplied FNP tag was more than one character
3965 or was not between a-h inclusive.
3966
3967 Action: Enter a corrected command line.
3968
3969
3970 admin_.pl1
3971 admin_: COMMAND: error: No FNP tag specified.
3972
3973
3974 Stream: as severity 1
3975
3976 Time: Response to an operator "load_fnp" "fdump_fnp"
3977 "dump_fnp" "start_fnp" or "stop_fnp" command.
3978
3979 Meaning: The operator did not supply an FNP identifier.
3980
3981 Action: Enter a corrected command line.
3982
3983
3984 admin_.pl1
3985 admin_: COMMAND: error: No multiplexer
3986 specified.
3987
3988
3989 Stream: as severity 1
3990
3991 Time: Response to an operator "load_mpx" "dump_mpx"
3992 "start_mpx" "shutdown_mpx" or "stop_mpx" command.
3993
3994 Meaning: The operator did not supply a multiplexer name.
3995
3996 Action: Enter a corrected command line.
3997
3998
3999 admin_.pl1
4000 admin_: COMMAND: ERROR_TABLE_MESSAGE
4001
4002
4003 Stream: as severity 1
4004
4005 Time: In response to operator command COMMAND.
4006
4007 Meaning: The ERROR_TABLE_MESSAGE error was encounted when
4008 processing the operator command COMMAND.
4009
4010 Action: Type "help COMMAND" for details of the command's
4011 usage.
4012
4013
4014
4015
4016 admin_ 70 08/03/23 MR12.7^L
4017
4018
4019
4020
4021 admin_.pl1
4022 admin_: COMMAND: PERSON.PROJECT has "nobump"
4023
4024
4025 Stream: as severity 1
4026
4027 Time: System shutdown.
4028
4029 Meaning: The PERSON.PROJECT user cannot be bumped by the
4030 automatic shutdown or in response to the stop
4031 command. The nobump attribute is normally only
4032 used by system administrator users.
4033
4034 Action: Try to contact the user to arrange a time to
4035 actually shutdown. If necessary the user can be
4036 bumped by specifying the channel name in the bump
4037 command. This will only work if the process has
4038 not been disconnected. Otherwise you will have
4039 to answer "yes" to the shutdown command.
4040
4041
4042
4043 admin_.pl1
4044 admin_: down: auto shutdown will be at MM/DD/YY
4045 HHMM.T
4046
4047
4048 Stream: as severity 1
4049
4050 Time: In response to an operator down command or at
4051 startup.
4052
4053 Meaning: This is the response to the down command. It
4054 indicates the scheduled shutdown time. A down
4055 command is issued automatically at system startup
4056 time after a crash; if a down command was given
4057 before the crash occurred and the time of the
4058 scheduled shutdown is more than 30 minutes in the
4059 future.
4060
4061 Action: If the value shown in the message is correct
4062 proceed. If not correct reset the shutdown by
4063 typing down 0 and then try again.
4064
4065
4066
4067 admin_.pl1
4068 admin_: down: error: no system shutdown
4069 scheduled
4070
4071
4072
4073
4074 admin_ 71 08/03/23 MR12.7^L
4075
4076
4077 Stream: as severity 1
4078
4079 Time: In response to operator entering "down 0".
4080
4081 Meaning: The "down 0" command line cancels a down but no
4082 system shutdown was scheduled. No action was
4083 taken.
4084
4085 Action: No operator action is required.
4086
4087
4088 admin_.pl1
4089 admin_: down: error: uptime is earlier than
4090 downtime.
4091
4092
4093 Stream: as severity 1
4094
4095 Time: In response to an operator down command.
4096
4097 Meaning: The operator down command specifies that the
4098 expected time that the system will be up is before
4099 the time that it is scheduled to be shutdown. No
4100 action was taken.
4101
4102 Action: Enter a corrected command line.
4103
4104
4105 admin_.pl1
4106 admin_: down: error: XXX invalid clock time.
4107
4108
4109 Stream: as severity 1
4110
4111 Time: In response to an operator down command.
4112
4113 Meaning: The time arguments of a down command must be
4114 specified in 4-digit time or some form acceptable
4115 to convert_date_to_binary_. No action was taken.
4116 If the second time argument is an invalid time it
4117 is considered part of the message. This message
4118 is also displayed if the first time argument is
4119 not in the future.
4120
4121 Action: Enter a corrected command line.
4122
4123
4124 admin_.pl1
4125 admin_: down: Next shutdown from DATE_TIME to
4126 DATE_TIME1 REASON
4127
4128
4129 Stream: as severity 1
4130
4131
4132 admin_ 72 08/03/23 MR12.7^L
4133
4134
4135 Time: Response to an operator "down" command.
4136
4137 Meaning: This message tells when the next scheduled
4138 shutdown is.
4139
4140 Action: No operator action is required.
4141
4142
4143 admin_.pl1
4144 admin_: down: No shutdown is scheduled.
4145
4146
4147 Stream: as severity 1
4148
4149 Time: In response to an operator down command.
4150
4151 Meaning: The operator issued a down 0 command to reset a
4152 scheduled automatic shutdown when none was in
4153 effect. No action was taken on the command.
4154
4155 Action: No operator action is required.
4156
4157
4158 admin_.pl1
4159 admin_: down: resetting previous shutdown at
4160 MM/DD/YY HHMM.T
4161
4162
4163 Stream: as severity 1
4164
4165 Time: In response to an operator down command.
4166
4167 Meaning: A second down command has been issued before a
4168 previously issued down command has been executed.
4169 The new shutdown time is honored instead of the
4170 previous one.
4171
4172 Action: No operator action is required.
4173
4174
4175 admin_.pl1
4176 admin_: dump_fnp: error: unknown argument AAAA
4177
4178
4179 Stream: as severity 1
4180
4181 Time: In response to an operator dump_fnp command.
4182
4183 Meaning: An unknown argument AAAA was encountered in the
4184 dump_fnp command line. This is an obsolete
4185 command. No action was taken.
4186
4187
4188
4189
4190 admin_ 73 08/03/23 MR12.7^L
4191
4192
4193 Action: Type "help dump_mpx" for details of the dump_mpx
4194 command and try again.
4195
4196
4197
4198 admin_.pl1
4199 admin_: dump_mpx: error: unknown argument AAAA
4200
4201
4202 Stream: as severity 1
4203
4204 Time: In response to an operator dump_mpx command.
4205
4206 Meaning: An unknown argument AAAA was encountered in the
4207 dump_mpx command line. No action was taken.
4208
4209 Action: Type "help dump_mpx" for details of the dump_mpx
4210 command and try again.
4211
4212
4213
4214 admin_.pl1
4215 admin_: ERROR_MESSAGE SYSDIR>absentee_user_table
4216
4217
4218 Stream: as severity 1
4219
4220 Time: When operator entered abs command.
4221
4222 Meaning: The ERROR_MESSAGE gives reason why system was not
4223 able to find or access the absentee_user_table in
4224 the SYSDIR directory. Execution of the command
4225 was not completed.
4226
4227 Action: %inform
4228
4229
4230 admin_.pl1
4231 admin_: ERROR_MESSAGE SYSDIR>answer_table
4232
4233
4234 Stream: as severity 2
4235
4236 Time: In response to operator commands that require
4237 access to the system answer_table.
4238
4239 Meaning: The ERROR_MESSAGE gives reason why system was not
4240 able to find or access the answer_table in the
4241 SYSDIR directory. Execution of the command was
4242 not completed.
4243
4244 Action: Contact the system programming staff.
4245
4246
4247
4248 admin_ 74 08/03/23 MR12.7^L
4249
4250
4251
4252
4253 admin_.pl1
4254 admin_: ERROR_MESSAGE SYSDIR>cdt
4255
4256
4257 Stream: as severity 2
4258
4259 Time: In response to operator commands that require
4260 access to the system cdt.
4261
4262 Meaning: The ERROR_MESSAGE gives reason why system was not
4263 able to find or access the cdt in the SYSDIR
4264 directory. Execution of the command was not
4265 completed.
4266
4267 Action: Contact the system programming staff.
4268
4269
4270 admin_.pl1
4271 admin_: ERROR_MESSAGE SYSDIR>installation_parms
4272
4273
4274 Stream: as severity 2
4275
4276 Time: In response to operator commands that require
4277 access to the system installation_parms.
4278
4279 Meaning: The ERROR_MESSAGE gives reason why system was not
4280 able to find or access the installation_parms in
4281 the SYSDIR directory. Execution of the command
4282 was not completed.
4283
4284 Action: Contact the system programming staff.
4285
4286
4287 admin_.pl1
4288 admin_: ERROR_MESSAGE SYSDIR>whotab
4289
4290
4291 Stream: as severity 2
4292
4293 Time: In response to operator commands that require
4294 access to the system whotab.
4295
4296 Meaning: The ERROR_MESSAGE gives reason why system was not
4297 able to find or access the whotab in the SYSDIR
4298 directory. Execution of the command was not
4299 completed.
4300
4301 Action: Contact the system programming staff.
4302
4303
4304
4305
4306 admin_ 75 08/03/23 MR12.7^L
4307
4308
4309
4310
4311 admin_.pl1
4312 admin_: fdump_fnp: error: unknown argument AAAA
4313
4314
4315 Stream: as severity 1
4316
4317 Time: In response to an operator fdump_fnp command.
4318
4319 Meaning: An unknown argument AAAA was encountered in the
4320 fdump_fnp command. This is an obsolete command.
4321 No action was taken.
4322
4323 Action: Type "help dump_mpx" for details of the dump_mpx
4324 command and try again.
4325
4326
4327
4328 admin_.pl1
4329 admin_: load_fnp: unknown argument AAAA
4330
4331
4332 Stream: as severity 1
4333
4334 Time: In response to an operator load_fnp command.
4335
4336 Meaning: An unknown argument AAAA was encountered in the
4337 load_fnp command line. This is an obsolete
4338 command. No action was taken.
4339
4340 Action: Type "help load_mpx" for details of the load_mpx
4341 command and try again.
4342
4343
4344
4345 admin_.pl1
4346 admin_: load_mpx: error: unknown argument AAAA
4347
4348
4349 Stream: as severity 1
4350
4351 Time: In response to an operator load_mpx command.
4352
4353 Meaning: An unknown argument AAAA was encountered in the
4354 load_mpx command line. No action was taken.
4355
4356 Action: Type "help load_mpx" for details of the load_mpx
4357 command and try again.
4358
4359
4360
4361
4362
4363
4364 admin_ 76 08/03/23 MR12.7^L
4365
4366
4367
4368
4369 admin_.pl1
4370 admin_: load_mpx: error: unknown argument AAAA
4371
4372
4373 Stream: as severity 1
4374
4375 Time: In response to an operator load_mpx command.
4376
4377 Meaning: An unknown argument AAAA was encountered in the
4378 load_mpx command line. No action was taken.
4379
4380 Action: Type "help load_mpx" for use of the load_mpx
4381 command and try again.
4382
4383
4384 admin_.pl1
4385 admin_: log: MESSAGE
4386
4387
4388 Stream: as severity 0
4389
4390 Time: While system is running.
4391
4392 Meaning: The log command simply enters its arguments in the
4393 system log. It is occasionally used by operators
4394 and system programmers to record events.
4395
4396 Action: No operator action is required.
4397
4398
4399 admin_.pl1
4400 admin_: login: Entry not found. No MC ACS
4401 segment for the source SSSS.
4402
4403
4404 Stream: as severity 1
4405
4406 Time: In response to operator login command.
4407
4408 Meaning: An MC ACS was not found in >sc1>mc_acs directory
4409 for the source identifier SSSS.
4410
4411 Action: Contact the system programming staff.
4412
4413
4414 admin_.pl1
4415 admin_: login: error: Usage: login
4416 Person.Project SOURCE -control_args
4417
4418
4419 Stream: as severity 1
4420
4421
4422 admin_ 77 08/03/23 MR12.7^L
4423
4424
4425 Time: In response to operator login command with no
4426 arguments.
4427
4428 Meaning: Informative message to operator when the login
4429 command was entered without arguments.
4430
4431 Action: Also type "help login" for further details of
4432 command line syntax.
4433
4434
4435 admin_.pl1
4436 admin_: login: ERROR_TABLE_MESSAGE Login not
4437 permitted for message coordinator source SSSS.
4438
4439
4440 Stream: as severity 1
4441
4442 Time: In response to operator login command.
4443
4444 Meaning: The error identified by ERROR_TABLE_MESSAGE was
4445 encountered attempting to check the access to
4446 login the daemon whose source identifier is SSSS.
4447
4448
4449
4450 admin_.pl1
4451 admin_: logout: error: Usage: logout
4452 Person.Project SOURCE
4453
4454
4455 Stream: as severity 1
4456
4457 Time: In response to operator logout command when
4458 entered without arguments.
4459
4460 Meaning: Informative message indicating usage of the logout
4461 command.
4462
4463 Action: Type "help logout" for further details of command
4464 usage.
4465
4466
4467 admin_.pl1
4468 admin_: maxu: MMMM: UUUU DDDD normal users
4469
4470
4471
4472 Stream: as severity 1
4473
4474 Time: When operator entered "maxu" command.
4475
4476 Meaning: This is an informative message indicating the
4477 current values manipulated by the maxu command.
4478
4479
4480 admin_ 78 08/03/23 MR12.7^L
4481
4482
4483 MMMM is the mode "auto" or "level". UUUU is the
4484 load units in tenths. DDDD is the load units in
4485 whole numbers.
4486
4487 Action: No operator action is required.
4488
4489
4490 admin_.pl1
4491 admin_: maxu: Warning: maxunits are in tenths
4492 of load units.
4493 You just set maxu to UUUU or DDDD normal users.
4494
4495
4496
4497 Stream: as severity 1
4498
4499 Time: When operator entered a maxu command line that
4500 specified < 200 load units or 20 normal users.
4501
4502 Meaning: This message is a warning to the operator that he
4503 may have made a mistake in setting the load units
4504 of the system. A normal system is not likely to
4505 set its maximum load units to less than 200.
4506
4507 Action: Take corrective action reenter the command with
4508 corrected arguments.
4509
4510
4511
4512 admin_.pl1
4513 admin_: maxunits: error: XXX invalid value for
4514 maxunits
4515
4516
4517 Stream: as severity 1
4518
4519 Time: In response to an operator maxunits command.
4520
4521 Meaning: The argument of the maxunits command was not a
4522 number or was zero or negative. No action was
4523 taken.
4524
4525 Action: Enter a corrected command line.
4526
4527
4528 admin_.pl1
4529 admin_: rcp: error: unknown rcp command RRRR
4530
4531
4532 Stream: as severity 1
4533
4534 Time: In response to an operator rcp command.
4535
4536
4537
4538 admin_ 79 08/03/23 MR12.7^L
4539
4540
4541 Meaning: The operator has entered an unknown rcp operator
4542 on the command line.
4543
4544 Action: Type "help rcp" for further details on rcp command
4545 usage.
4546
4547
4548 admin_.pl1
4549 admin_: shift: error: CCCC invalid clock time.
4550
4551
4552 Stream: as severity 1
4553
4554 Time: In response to an operator shift command.
4555
4556 Meaning: The time argument of the shift command is not a
4557 valid clock time acceptable to
4558 convert_date_to_binary_.
4559
4560 Action: Enter a corrected command line.
4561
4562
4563 admin_.pl1
4564 admin_: shift: error: CCCC is not within the
4565 next week.
4566
4567
4568 Stream: as severity 1
4569
4570 Time: In response to an operator shift command.
4571
4572 Meaning: The time argument of the shift command cannot
4573 specify a time stamp that is over a week in the
4574 future.
4575
4576 Action: Enter a corrected command line.
4577
4578
4579 admin_.pl1
4580 admin_: shift: error: XXXX is not a legal shift
4581 number.
4582
4583
4584 Stream: as severity 1
4585
4586 Time: In response to an operator shift command.
4587
4588 Meaning: A shift argument to the shift command was not a
4589 valid decimal number between 1 and 6 inclusive.
4590
4591 Action: Enter a corrected command line.
4592
4593
4594
4595
4596 admin_ 80 08/03/23 MR12.7^L
4597
4598
4599
4600
4601 admin_.pl1
4602 admin_: shift: N until DATE_TIME
4603
4604
4605 Stream: as severity 1
4606
4607 Time: response to an operator "shift" command.
4608
4609 Meaning: The operator has issued the shift command. If
4610 issued with no arguments this command types the
4611 current setting. If issued with arguments the
4612 command changes the shift and types the new value.
4613
4614 Action: No operator action is required.
4615
4616
4617 admin_.pl1
4618 admin_: shutdown_mpx: error: unknown argument
4619 AAAA
4620
4621
4622 Stream: as severity 1
4623
4624 Time: In response to an operator shutdown_mpx command.
4625
4626 Meaning: An unknown argument AAAA was encountered in the
4627 shutdown_mpx command line. No action was taken.
4628
4629 Action: The shutdown_mpx command is the same as the
4630 dump_mpx command except that no dump is created.
4631 Type "help dump_mpx" for command usage details and
4632 try again.
4633
4634
4635
4636 admin_.pl1
4637 admin_: stop: All users are out. You may shut
4638 down.
4639
4640
4641 Stream: as severity 1
4642
4643 Time: System shutdown.
4644
4645 Meaning: This is the response to the stop command if all
4646 users have been logged out. This message provides
4647 a quick check of whether all users have been
4648 bumped since it does not adversely affect system
4649 operation to issue the stop command repeatedly.
4650
4651 Action: Proceed with the shutdown.
4652
4653
4654 admin_ 81 08/03/23 MR12.7^L
4655
4656
4657
4658
4659 admin_.pl1
4660 admin_: stop: all users have been given XXXX
4661 minutes to logout
4662
4663
4664 Stream: as severity 1
4665
4666 Time: System shutdown.
4667
4668 Meaning: A stop command either manual or automatic has
4669 been initiated. All users have been warned that
4670 they have XXXX minutes to finish up and logout.
4671 After XXXX minutes all users will be bumped
4672 except those with the nobump attribute. The login
4673 word has been set so that no more users may log
4674 in. To cancel this shutdown issue a word login
4675 command and an unbump * * command.
4676
4677 Action: No operator action is required.
4678
4679
4680 admin_.pl1
4681 admin_: stop: auto abs stop
4682
4683
4684 Stream: as severity 1
4685
4686 Time: While system is running.
4687
4688 Meaning: It is 30 minutes before an automatic stop so an
4689 automatic abs stop command is being issued. This
4690 is the result of a previous down command. Refer
4691 also to the stop command description.
4692
4693 Action: No operator action is required.
4694
4695
4696 admin_.pl1
4697 admin_: stop: Automatic shutdown
4698
4699
4700 Stream: as severity 1
4701
4702 Time: System shutdown.
4703
4704 Meaning: A down command issued earlier has taken effect.
4705 An automatic stop command is executed. All users
4706 are bumped in three minutes.
4707
4708 Action: Prepare to shut down the system.
4709
4710
4711
4712 admin_ 82 08/03/23 MR12.7^L
4713
4714
4715
4716
4717 admin_.pl1
4718 admin_: stop: error: no arguments are allowed
4719 for "stop"
4720
4721
4722 Stream: as severity 1
4723
4724 Time: In response to an operator stop command.
4725
4726 Meaning: The operator has given an argument to the stop
4727 command. No arguments are allowed. No action was
4728 taken.
4729
4730 Action: If abs stop was meant type that command. If stop
4731 was meant type that command instead. If "down
4732 ...." was meant type in that command.
4733
4734
4735
4736 admin_.pl1
4737 admin_: stop: There were no active users to be
4738 bumped.
4739
4740
4741 Stream: as severity 1
4742
4743 Time: System shutdown.
4744
4745 Meaning: The system did not find any active users to be
4746 bumped.
4747
4748 Action: No operator action is required.
4749
4750
4751 admin_.pl1
4752 admin_: stop_fnp: error: unknown argument AAAA
4753
4754
4755 Stream: as severity 1
4756
4757 Time: In response to an operator stop_mpx command.
4758
4759 Meaning: An unknown argument AAAA was encountered in the
4760 stop_fnp command line. This is an obsolete
4761 command. No action was taken.
4762
4763 Action: Type "help stop_mpx" for details of the stop_mpx
4764 command and try again.
4765
4766
4767
4768
4769
4770 admin_ 83 08/03/23 MR12.7^L
4771
4772
4773
4774
4775 admin_.pl1
4776 admin_: stop_mpx: error: unknown argument AAAA
4777
4778
4779 Stream: as severity 1
4780
4781 Time: In response to an operator stop_mpx command.
4782
4783 Meaning: An unknown argument AAAA was encountered in the
4784 stop_mpx command line. No action was taken.
4785
4786 Action: Type "help stop_mpx" for details of the stop_mpx
4787 command and try again.
4788
4789
4790
4791 admin_.pl1
4792 admin_: warn: error: Usage: warn
4793 Person.Project MESSAGE
4794
4795
4796 Stream: as severity 1
4797
4798 Time: In response to an operator warn command without
4799 any arguments.
4800
4801 Meaning: Informative message indicating usage of the warn
4802 command.
4803
4804 Action: Also type "help warn" for more details on warn
4805 command usage.
4806
4807
4808 admin_.pl1
4809 admin_: warn: NAME.PROJ has "no_warning"
4810
4811
4812 Stream: as severity 1
4813
4814 Time: Response to operator warn command.
4815
4816 Meaning: This is the response to the command "warn NAME
4817 PROJ Message..." if the user has specified the
4818 -no_warning argument at login. The message is not
4819 sent to the user.
4820
4821 Action: Attempt to contact the user by other means.
4822
4823
4824 admin_.pl1
4825 admin_: warn: NAME.PROJ not found.
4826
4827
4828 admin_ 84 08/03/23 MR12.7^L
4829
4830
4831 Stream: as severity 1
4832
4833 Time: In response to an operator warn command.
4834
4835 Meaning: The warn command was issued for a nonexistent
4836 user. No action was taken.
4837
4838 Action: The user is probably not logged in. Check the
4839 spelling of the name.Enter a corrected command
4840 line.
4841
4842
4843
4844 admin_.pl1
4845 admin_: warn: USER.PROJ not connected to a
4846 channel
4847
4848
4849 Stream: as sevreity1
4850
4851 Time: Response to operator warn command.
4852
4853 Meaning: This is the response to the command "warn NAME
4854 PROJ Message" if the pointer to the channel table
4855 entry in the user table entry for the named user
4856 ute.cdtep is not set null. The message cannot
4857 be sent to the user.
4858
4859 Action: Attempt to contact the user by other means.
4860
4861
4862 admin_.pl1
4863 admin_: word: length of login-word must not
4864 exceed 8 characters
4865
4866
4867 Stream: as severity 1
4868
4869 Time: In response to an operator word command.
4870
4871 Meaning: The operator tried to set the login word with the
4872 word command but the first argument was too long.
4873 No action was taken on the command.
4874
4875 Action: Enter a corrected command line.
4876
4877
4878 admin_.pl1
4879 admin_: word: message truncated; maximum length
4880 is CCCC characters
4881
4882
4883 Stream: as severity 1
4884
4885
4886 admin_ 85 08/03/23 MR12.7^L
4887
4888
4889 Time: In response to an operator word command.
4890
4891 Meaning: The operator issued the command "word XXXX TEXT".
4892 The message TEXT was too long to fit in the dialup
4893 message buffer. The login word has been changed
4894 and the dialup message has been set to the first
4895 CCCC characters of the given message.
4896
4897 Action: Reword the message to fit within the
4898 CCCC-character limit and retype the command.
4899
4900
4901
4902 admin_.pl1
4903 admin_: word: TYPE message: TEXT
4904
4905
4906 Stream: as severity 1
4907
4908 Time: In response to an operator word command.
4909
4910 Meaning: The operator issued the command "word XXXX TEXT".
4911 The login word was set to XXXX and a special
4912 buffer was loaded with the message TEXT so that it
4913 is typed out whenever a user dials up. The type
4914 of system session is TYPE; this may be special
4915 normal or shutdown.
4916
4917 Action: Check the message for accuracy.
4918
4919
4920 admin_.pl1
4921 admin_: word: XXXX is a reserved word.
4922
4923
4924 Stream: as severity 1
4925
4926 Time: In response to an operator word command.
4927
4928 Meaning: The operator attempted to set the system login
4929 word to enter enterp e ep dial or d. No
4930 action was taken.
4931
4932 Action: Pick another word and type it in.
4933
4934
4935 admin_.pl1
4936 admin_: word: XXXX; TYPE message: TEXT
4937
4938
4939 Stream: as severity 1
4940
4941 Time: In response to an operator word command.
4942
4943
4944 admin_ 86 08/03/23 MR12.7^L
4945
4946
4947 Meaning: The operator issued the word command with no
4948 arguments and the current values were typed. The
4949 login word is XXXX the message is TEXT and the
4950 type of session is TYPE. The TEXT is displayed as
4951 the first line of the greeting banner to
4952 interactive users making the banner 3 lines long.
4953 If TEXT is "" NO MESSAGE then nothing is added
4954 to the normal 2 line greeting banner.
4955
4956 Action: Check the word type and message for accuracy.
4957
4958
4959 salv_dir_checker_.pl1
4960 ADUIT salv_dir_checker_: GRANTED modification
4961 of security out-of-service ADDED_INFO
4962
4963
4964 Stream: $access_audit
4965
4966 Time: Salvaging
4967
4968 Meaning: The security-out-of-service switch has been set on
4969 a directory because of an AIM error. The access
4970 class of a branch was not equal to that of the
4971 containing directory or the access class in the
4972 directory's branch was not equal to the access
4973 class stored in its header.
4974
4975 Action: Contact the system programming staff._ssa
4976
4977
4978 announce_chwm.pl1
4979 announce_chwm: WWW pages wired UUU pages usable.
4980
4981
4982 Stream: BOS Typewriter.
4983
4984 Time: System Intialization.
4985
4986 Meaning: This message is produced when the CHWM paramter is
4987 specified on the PARM CONFIG card. WWW is the
4988 number of wired pages in collection one. UUU is
4989 the number of available main memory frames
4990 including those occupied by wired pages but not
4991 those occupied by unpaged segments.
4992
4993 Action: No operator action is required.
4994
4995
4996 announce_chwm.pl1
4997 announce_chwm: WWW. pages used of XXX. in wired
4998 environment.
4999
5000
5001
5002 announce_chwm 87 08/03/23 MR12.7^L
5003
5004
5005 Stream: BOS Typewriter.
5006
5007 Time: System Intialization.
5008
5009 Meaning: This message is produced when the CHWM parameter
5010 is specified on the PARM CONFIG card. WWW is the
5011 number of pages of memory which remain unused out
5012 of a maximum of XXX after all the segments in
5013 collection one have been loaded and all the
5014 segments constructed by collection one have been
5015 created.
5016
5017 Action: No operator action is required.
5018
5019
5020 announce_chwm.pl1
5021 announce_chwm: WWW. words used of XXX. in
5022 int_unpaged_page_tables.
5023
5024
5025 Stream: BOS Typewriter.
5026
5027 Time: System Intialization.
5028
5029 Meaning: This message is produced when the CHWM parameter
5030 is specified on the PARM CONFIG card. WWW is the
5031 number of words of the XXX word long segment
5032 int_unpaged_page_tables used to hold page tables
5033 for temporary collection 1 segments.
5034
5035 Action: No operator action is required.
5036
5037
5038 announce_chwm.pl1
5039 announce_chwm: WWW. words used of XXX. in
5040 unpaged_page_tables.
5041
5042
5043 Stream: BOS Typewriter.
5044
5045 Time: System Intialization.
5046
5047 Meaning: This message is produced when the CHWM parameter
5048 is specified on the PARM CONFIG card. WWW is the
5049 number of words of the XXX word long segment
5050 unpaged_page_tables used to hold page tables for
5051 permanent "unpaged" segments.
5052
5053 Action: No operator action is required.
5054
5055
5056 append.pl1
5057
5058
5059
5060 append 88 08/03/23 MR12.7^L
5061
5062
5063 append: error from delete_vtoce for PATH:
5064 ERROR_MESSAGE
5065
5066
5067 Stream: Logged in SYSERR log.
5068
5069 Time: While system is running.
5070
5071 Meaning: While deleting a VTOC entry to clean up an
5072 unsuccessful attempt to create an branch append
5073 got an error. This indicates a logic error in the
5074 supervisor or CPU or memory hardware problems.
5075
5076 Action: Note for system programmer action.
5077
5078
5079 append.pl1
5080 append: error from hash$out for PATH: ERROR_CODE
5081
5082
5083 Stream: Logged in SYSERR log.
5084
5085 Time: While system is running.
5086
5087 Meaning: While removing a name to clean up an unsuccessful
5088 attempt to create a branch append got an error.
5089 This indicates a logic error in the supervisor or
5090 CPU or memory hardware problems.
5091
5092 Action: Note for system programmer action.
5093
5094
5095 append.pl1
5096 append: error from makeunknown_ for PATH:
5097 ERROR_CODE
5098
5099
5100 Stream: Logged in SYSERR log.
5101
5102 Time: While system is running.
5103
5104 Meaning: Append made the new directory PATH unknown after
5105 initializing its header. While doing so it
5106 encountered an error. This indicates a logic
5107 error in the supervisor or CPU or memory hardware
5108 problems.
5109
5110 Action: Note for system programmer action.
5111
5112
5113 append.pl1
5114 append: makeunknown_ err after quota err for
5115 PATH: ERROR_CODE
5116
5117
5118 append 89 08/03/23 MR12.7^L
5119
5120
5121 Stream: Logged in SYSERR log.
5122
5123 Time: While system is running.
5124
5125 Meaning: During the creation of a new directory append
5126 encountered an error moving quota. While cleaning
5127 up from this error a further error was
5128 encountered. The system continues to operate.
5129 This indicates a logic error in the supervisor or
5130 CPU or memory hardware problems.
5131
5132 Action: Note for system programmer action.
5133
5134
5135 as_add_admin_acl_.pl1
5136 as_add_admin_acl_: ERROR_MESSAGE. Could not add
5137 PGID to ACL of PATH.
5138
5139
5140 Stream: as severity2
5141
5142 Time: Answering Service initialization or while the
5143 system is running.
5144
5145 Meaning: An error occurred while trying to rebuild the
5146 access control list ACL on PATH where:
5147 ERROR_MESSAGE is an error_table_ message
5148 PGID is a process group id
5149 PATH is a full pathname
5150
5151 Action: Manually give PGID read access or status
5152 permission to PATH.
5153
5154
5155 as_add_admin_acl_.pl1
5156 as_add_admin_acl_: ERROR_MESSAGE. Could not add
5157 to ACL of PATH.
5158
5159
5160 Stream: as severity2
5161
5162 Time: Answering Service initialization or while the
5163 system is running.
5164
5165 Meaning: Some fatal error occurred while rebuilding the
5166 access control list ACL of PATH. ERROR_MESSAGE
5167 is an error_table_ message and PATH is the full
5168 pathname of a segment or a directory.
5169
5170 Action: Contact the system programming staff. The
5171 operation that caused the error must be determined
5172 and the operation repeated after correction.
5173
5174
5175
5176 as_add_admin_acl_ 90 08/03/23 MR12.7^L
5177
5178
5179
5180
5181 as_dump_.pl1
5182 as_dump_: Answering service dump created in
5183 segment >sc1>asdump.-.MM/DD/YY-HHMM
5184
5185
5186 Stream: as severity1
5187
5188 Time: While system is running.
5189
5190 Meaning: Some program has encountered an unexpected fault
5191 and has called for a dump of the Answering
5192 Service. This segment is automatically dprinted.
5193
5194 Action: No operator action is required.
5195
5196
5197 as_dump_.pl1
5198 as_dump_: Cannot attach I/O switch. No dump NAME
5199
5200
5201 Stream: as severity2
5202
5203 Time: While system is running.
5204
5205 Meaning: An error occurred while dumping. No dump was
5206 taken.
5207
5208 Action: Contact the system programming staff.
5209
5210
5211 as_dump_.pl1
5212 as_dump_: Cannot obtain quota dump aborted.
5213 NAME
5214
5215
5216 Stream: as severity2
5217
5218 Time: While system is running.
5219
5220 Meaning: An error occurred while dumping. No dump was
5221 taken.
5222
5223 Action: Contact the system programming staff.
5224
5225
5226 as_dump_.pl1
5227 as_dump_: CONDITION while dumping. Dump aborted
5228
5229
5230 Stream: as severity1
5231
5232
5233
5234 as_dump_ 91 08/03/23 MR12.7^L
5235
5236
5237 Time: While system is running.
5238
5239 Meaning: During the attempt to perform an Answering Service
5240 dump some unexpected fault occurred. The dump is
5241 stopped and the system tries to continue.
5242
5243 Action: Notify the system programming staff.
5244
5245
5246 as_dump_.pl1
5247 as_dump_: ERROR_MESSAGE. Cannot attach
5248 as_dump_stream_ to FILENAME. No dump
5249 asdump.MM/DD/YY-HHMM
5250
5251
5252 Stream: as severity1
5253
5254 Time: While system is running.
5255
5256 Meaning: The Answering Service dump program could not
5257 attach a file for the Answering Service dump. The
5258 dump will abort and the system will continue.
5259
5260 Action: Contact the system programming staff.
5261
5262
5263 as_dump_.pl1
5264 as_dump_: ERROR_MESSAGE. Cannot obtain quota of
5265 >sc1 dump aborted. DUMPID
5266
5267
5268 Stream: as severity2
5269
5270 Time: While system is running.
5271
5272 Meaning: An error occurred while dumping. No dump was
5273 taken.
5274
5275 Action: Contact the system programming staff.
5276
5277
5278 as_dump_.pl1
5279 as_dump_: Message coordinator dump created in
5280 segment >sc1>asdump.-.MM/DD/YY-HHMM
5281
5282
5283 Stream: BOS Typewriter.
5284
5285 Time: While system is running.
5286
5287 Meaning: Some program has encountered an unexpected fault
5288 and has called for a dump of the message
5289
5290
5291
5292 as_dump_ 92 08/03/23 MR12.7^L
5293
5294
5295 coordinator. This segment is automatically
5296 dprinted.
5297
5298 Action: No operator action is required.
5299
5300
5301 as_dump_.pl1
5302 as_dump_: Out of room for dump DUMPID
5303
5304
5305 Stream: as severity2
5306
5307 Time: While system is running.
5308
5309 Meaning: An error occurred while dumping. No dump was
5310 taken.
5311
5312 Action: Contact the system programming staff.
5313
5314
5315 as_hasp_mpx_.pl1
5316 as_hasp_mpx_: Crash signalled for multiplexer
5317 TTY.
5318
5319
5320 Stream: as severity 1
5321
5322 Time: While system is running.
5323
5324 Meaning: The physical connection for the HASP multiplexer
5325 on channel TTY has been broken either because of
5326 an error or or because of a request from the
5327 remote host/workstation.
5328
5329 Action: Check the console for a message concerning this
5330 channel from hasp_mpx. If such a message is
5331 found refer to its documentation for further
5332 action; otherwise the remote host/workstation has
5333 requested termination of the connection and the
5334 I/O daemons using this channel should be logged
5335 out.
5336
5337
5338
5339 as_hasp_mpx_.pl1
5340 as_hasp_mpx_: Duplicate subchannel name NAME for
5341 HASP multiplexer TTY.
5342
5343
5344 Stream: as severity 1
5345
5346 Time: In response to a load_mpx operator command or
5347 during system initialization.
5348
5349
5350 as_hasp_mpx_ 93 08/03/23 MR12.7^L
5351
5352
5353 Meaning: The same name has been used for two or more
5354 subchannels of the HASP multiplexer on channel
5355 TTY.
5356
5357 Action: Correct the CDT entry for this multiplexer and
5358 reload it.
5359
5360
5361 as_hasp_mpx_.pl1
5362 as_hasp_mpx_: ERROR_MESSAGE. Cannot get
5363 additional info from terminal type NAME for
5364 multiplexer TTY.
5365
5366
5367 Stream: as severity 1
5368
5369 Time: In response to a load_mpx operator command or
5370 during system initialization.
5371
5372 Meaning: The terminal type specified by NAME was not given
5373 an additional_info string in its TTT entry. This
5374 string is required to specify the configuration
5375 parameters for the HASP multiplexer on channel
5376 TTY.
5377
5378 Action: Check both the CDT entry for this multiplexer and
5379 the TTT entry for the terminal type. Either the
5380 wrong terminal type was specified in the CDT or
5381 the terminal type's definition is incomplete.
5382 Correct whichever table is in error and reload the
5383 multiplexer.
5384
5385
5386
5387 as_hasp_mpx_.pl1
5388 as_hasp_mpx_: ERROR_MESSAGE. Creating event
5389 channel for multiplexer TTY.
5390
5391
5392 Stream: as severity 1
5393
5394 Time: In response to a load_mpx operator command or
5395 during system initialization.
5396
5397 Meaning: A system error arose during the initialization of
5398 the HASP multiplexer on channel TTY.
5399
5400 Action: Contact the system programming staff.
5401
5402
5403 as_hasp_mpx_.pl1
5404 as_hasp_mpx_: Invalid PARM specification in
5405 terminal type NAME for multiplexer TTY.
5406
5407
5408 as_hasp_mpx_ 94 08/03/23 MR12.7^L
5409
5410
5411 Stream: as severity 1
5412
5413 Time: In response to a load_mpx operator command or
5414 during system initialization.
5415
5416 Meaning: The value specified for the configuration
5417 parameter PARM in the additional info string of
5418 the terminal type NAME used for the HASP
5419 multiplexer on channel TTY is not acceptable to
5420 the system.
5421
5422 Action: Correct the value of the parameter in the TTT and
5423 reload the multiplexer.
5424
5425
5426 as_hasp_mpx_.pl1
5427 as_hasp_mpx_: Invalid subchannel name NAME for
5428 HASP multiplexer TTY.
5429
5430
5431 Stream: as severity 1
5432
5433 Time: In response to a load_mpx operator command or
5434 during system initialization.
5435
5436 Meaning: The name specified for a subchannel of the HASP
5437 multiplexer on channel TTY does not conform to the
5438 conventions defined in MAM Communications for
5439 naming such channels.
5440
5441 Action: Correct the CDT entry for this multiplexer and
5442 reload it.
5443
5444
5445 as_hasp_mpx_.pl1
5446 as_hasp_mpx_: Line type for hasp operator console
5447 on multiplexer TTY must be "HASP_OPR" when
5448 configured for login service.
5449
5450
5451
5452 Stream: as severity 1
5453
5454 Time: In response to a load_mpx operator command or
5455 during system initialization.
5456
5457 Meaning: The line type must be set for HASP_OPR on a hasp
5458 operator console subchannel when it is configured
5459 for login service.
5460
5461 Action: Correct the CDT entry for this multiplexer and
5462 reload it.
5463
5464
5465
5466 as_hasp_mpx_ 95 08/03/23 MR12.7^L
5467
5468
5469
5470
5471 as_hasp_mpx_.pl1
5472 as_hasp_mpx_: Load signalled for multiplexer TTY.
5473
5474
5475 Stream: as severity 1
5476
5477 Time: While system is running.
5478
5479 Meaning: The physical connection and initial connection
5480 protocl for the HASP multiplexer on channel TTY
5481 has been completed successfully. The multiplexer
5482 is now ready for use.
5483
5484 Action: Start the appropriate I/O daemon processes for the
5485 multiplexer as indicated by the system
5486 administrators or by the user who requested the
5487 multiplexer be loaded.
5488
5489
5490
5491 as_hasp_mpx_.pl1
5492 as_hasp_mpx_: More than 17 subchannels specified
5493 for HASP multiplexer TTY COUNT.
5494
5495
5496 Stream: as severity 1
5497
5498 Time: In response to a load_mpx operator command or
5499 during system initialization.
5500
5501 Meaning: The definition of the HASP multiplexer on channel
5502 TTY contains too many subchannels.
5503
5504 Action: Correct the CDT entry for this multiplexer and
5505 reload it.
5506
5507
5508 as_hasp_mpx_.pl1
5509 as_hasp_mpx_: Subchannel NAME of multiplexer TTY
5510 does not have TYPE service type.
5511
5512
5513 Stream: as severity 1
5514
5515 Time: In response to a load_mpx operator command or
5516 during system initialization.
5517
5518 Meaning: The specified subchannel of the HASP multiplexer
5519 on channel TTY was not given the slave service
5520 type or in the case of operator console
5521 subchannels slave or login.
5522
5523
5524 as_hasp_mpx_ 96 08/03/23 MR12.7^L
5525
5526
5527 Action: Correct the CDT entry for this multiplexer and
5528 reload it.
5529
5530
5531 as_hasp_mpx_.pl1
5532 as_hasp_mpx_: Too many printers and punches
5533 configured for HASP multiplexer TTY.
5534
5535
5536 Stream: as severity 1
5537
5538 Time: In response to a load_mpx operator command or
5539 during system initialization.
5540
5541 Meaning: More than 8 card punches and line printers have
5542 been specified for the HASP multiplexer on channel
5543 TTY or a card punch and line printer which use the
5544 same flow control flag have been specified. See
5545 MAM Communications for a description of the rules
5546 for naming card punches and line printers.
5547
5548 Action: Correct the CDT entry for this multiplexer and
5549 reload it.
5550
5551
5552 as_hasp_mpx_.pl1
5553 as_hasp_mpx_: Unexpected wakeup DATA1 DATA2
5554 from process ID.
5555
5556
5557 Stream: as severity 1
5558
5559 Time: While system is running.
5560
5561 Meaning: A message was received from the process whose
5562 processid is the 12-digit octal value ID; the
5563 contents of the message are given by the two
5564 12-digit octal values DATA1 and DATA2. No message
5565 was expected at this time. The wakeup is ignored.
5566
5567 Action: No operator action is required.
5568
5569
5570 as_hasp_mpx_.pl1
5571 as_hasp_mpx_: Wakeup from multiplexer TTY has
5572 invalid state code VALUE.
5573
5574
5575 Stream: as severity 1
5576
5577 Time: While system is running.
5578
5579
5580
5581
5582 as_hasp_mpx_ 97 08/03/23 MR12.7^L
5583
5584
5585 Meaning: A message was received indicating a change of
5586 state for the multiplexer on channel TTY; however
5587 the new state of the multiplexer given by the
5588 decimal number VALUE is not recognized by this
5589 module.
5590
5591 Action: Contact the system programming staff.
5592
5593
5594 as_init_.pl1
5595 as_init_: Answering Service initialization
5596 failed.
5597
5598
5599 Stream: as severity 2
5600
5601 Time: System Intialization.
5602
5603 Meaning: This indicates a logic error in the supervisor or
5604 CPU or memory hardware problems. Answering
5605 Service initialization failed. Normally this
5606 message is preceded by a more specific indication
5607 of the reason for failure.
5608
5609 Action: Contact the system programming staff. Attempt to
5610 correct the problem and try startup again.
5611
5612
5613
5614 as_init_.pl1
5615 as_init_: CDT rethreading complete.
5616
5617
5618 Stream: as severity 1
5619
5620 Time: System Intialization.
5621
5622 Meaning: Rethreading of Channel Definition Table CDT
5623 entries into a multiplexer/subchannel hierarchy
5624 completed successfully. System initialization
5625 continues.
5626
5627 Action: Contact the system programming staff._sa
5628
5629
5630 as_init_.pl1
5631 as_init_: CDT threading inconsistency found.
5632 Rethreading.
5633
5634
5635 Stream: as severity 1
5636
5637 Time: System Intialization.
5638
5639
5640 as_init_ 98 08/03/23 MR12.7^L
5641
5642
5643 Meaning: An error was detected while tracing the threading
5644 of Channel Definition Table CDT entries into a
5645 hierarchy of multiplexer and subchannel
5646 entries.This indicates a logic error in the
5647 supervisor or CPU or memory hardware problems.
5648 The entire channel hierarchy will be rethreaded.
5649
5650 Action: Contact the system programming staff._sa
5651
5652
5653 as_init_.pl1
5654 as_init_: Condition COND signalled during
5655 startup. Taking AS dump. CONDITION_INFO
5656
5657
5658
5659 S. as severity 1
5660
5661 Time: System Intialization.
5662
5663 Meaning: An unexpected condition COND occurred during
5664 system initialization. An answering service dump
5665 is taken. The stack trace information in this
5666 dump further describes the error. Some steps of
5667 Answering Service initialization were not
5668 performed. This may cause the system to operate
5669 incorrectly. CONDITION_INFO if optionally present
5670 if further information about the condition is
5671 available.
5672
5673 Action: Contact the system programming staff.
5674
5675
5676 as_init_.pl1
5677 as_init_: Condition was signalled while
5678 processing another condition. CONDITION
5679
5680
5681 Stream: BOS Typewriter sounds beeper
5682
5683 Time: System Intialization.
5684
5685 Meaning: This indicates a logic error in the supervisor or
5686 CPU or memory hardware problems. During Answering
5687 Service initialization a CONDITION was raised
5688 while as_init_ was already processing some
5689 condition. It may be that the error occured while
5690 making an as_dump for the first condition.
5691 as_init_ will not attempt to make an as_dump but
5692 will instead abort the initialization.
5693
5694 Action: Contact the system programming staff.
5695
5696
5697
5698 as_init_ 99 08/03/23 MR12.7^L
5699
5700
5701
5702
5703 as_init_.pl1
5704 as_init_: ERROR_MESSAGE.
5705
5706
5707 Stream: as severity 1
5708
5709 Time: System Intialization.
5710
5711 Meaning: A fatal error occurred during Answering Service
5712 initialization. Previous messages describe the
5713 error in more detail.
5714
5715 Action: Contact the system programming staff._sa
5716
5717
5718 as_init_.pl1
5719 as_init_: ERROR_MESSAGE. Calling
5720 multiplexer_mgr_$ENTRYPOINT.
5721
5722
5723 Stream: as severity 1
5724
5725 Time: System Intialization.
5726
5727 Meaning: The multiplexer_mgr_ failed when accessing the
5728 Channel Definition Table CDT in >sc1
5729 initializing the CDT or loading the FNPs.
5730 ERROR_MESSAGE is the text associated with the
5731 error code returned by multiplexer_mgr_.
5732 Answering service initialization fails. The
5733 system administrator must enter admin mode and
5734 correct the problem. Then reboot the system.
5735
5736 Action: Contact the system programming staff._sa
5737
5738
5739 as_init_.pl1
5740 as_init_: ERROR_MESSAGE. Calling ROUTINE.
5741
5742
5743 Stream: as severity 1
5744
5745 Time: System Intialization.
5746
5747 Meaning: An error occurred when calling ROUTINE during
5748 Answering Service initialization. ERROR_MESSAGE
5749 is the text associated with the error code
5750 returned by ROUTINE. Answering service
5751 initialization fails. The system administrator
5752 must enter admin mode and correct the problem.
5753 Then reboot the system.
5754
5755
5756 as_init_ 100 08/03/23 MR12.7^L
5757
5758
5759 Action: Contact the system programming staff._sa
5760
5761
5762 as_init_.pl1
5763 as_init_: ERROR_MESSAGE. Cannot create pit_temp_
5764
5765
5766 Stream: as severity 1
5767
5768 Time: System Intialization.
5769
5770 Meaning: The system could not create a temporary segment in
5771 the Answering Service process's process directory.
5772 This is a fatal error that will cause answering
5773 service startup to fail.
5774
5775 Action: Contact the system programming staff._sa
5776
5777
5778 as_init_.pl1
5779 as_init_: ERROR_MESSAGE. Cannot create sat.ht.
5780 REASON
5781
5782
5783 Stream: as severity 1
5784
5785 Time: System Intialization.
5786
5787 Meaning: This message indicates that the sat is damaged or
5788 that a storage system error prevented the creation
5789 of a new hash table for the sat. Answering
5790 Service startup will fail.
5791
5792 Action: Contact the system programming staff._sa
5793
5794
5795 as_init_.pl1
5796 as_init_: ERROR_MESSAGE. cdt_mgr_$thread:
5797 ADDED_INFO
5798
5799
5800 Stream: as severity 1
5801
5802 Time: System Intialization.
5803
5804 Meaning: as_init_ called cdt_mgr_$thread to rethread the
5805 Channel Definition Table CDT entries into a
5806 multiplexer/subchannel hierarchy. cdt_mgr_
5807 encountered an unexpected error. ERROR_MESSAGE is
5808 the text associated with the error code returned
5809 by cdt_mgr_. ADDED_INFO further describes the
5810 error and whether or not further rethreading is
5811 attempted.
5812
5813
5814 as_init_ 101 08/03/23 MR12.7^L
5815
5816
5817 Action: Contact the system programming staff._sa
5818
5819
5820 as_init_.pl1
5821 as_init_: ERROR_MESSAGE. Could not create
5822 SYSTEM_CONTROL_DIR>TABLE.
5823
5824
5825 Stream: as severity 1
5826
5827 Time: System Intialization.
5828
5829 Meaning: The Initializer could not create a new segment
5830 TABLE in SYSTEM_CONTROL_DIR. Answering service
5831 initialization fails. The system administrator
5832 must enter admin mode and type "create TABLE"
5833 where TABLE is the name given above. Then reboot
5834 the system.
5835
5836 Action: Contact the system programming staff._sa
5837
5838
5839 as_init_.pl1
5840 as_init_: ERROR_MESSAGE. Could not force access
5841 on SYSTEM_CONTROL_DIR>TABLE.
5842
5843
5844 Stream: as severity 1
5845
5846 Time: System Intialization.
5847
5848 Meaning: The Initializer could not change the ACL on the
5849 TABLE segment in SYSTEM_CONTROL_DIR. Answering
5850 service initialization fails. The system
5851 administrator must enter admin mode and correct
5852 the problem. Then reboot the system.
5853
5854 Action: Contact the system programming staff._sa
5855
5856
5857
5858
5859
5860 as_init_.pl1
5861 as_init_: ERROR_MESSAGE. Could not initiate
5862 SYSTEM_CONTROL_DIR>TABLE.
5863
5864
5865 Stream: as severity 1
5866
5867 Time: System Intialization.
5868
5869
5870
5871
5872 as_init_ 102 08/03/23 MR12.7^L
5873
5874
5875 Meaning: The Initializer could not initiate the TABLE
5876 segment in SYSTEM_CONTROL_DIR. Answering service
5877 initialization fails. The system administrator
5878 must enter admin mode and correct the problem.
5879 Then reboot the system.
5880
5881 Action: Contact the system programming staff._sa
5882
5883
5884 as_init_.pl1
5885 as_init_: ERROR_MESSAGE. Could not set priority
5886 for IPC wait channels.
5887
5888
5889 Stream: as severity 1
5890
5891 Time: System Intialization.
5892
5893 Meaning: A call to ipc_$set_wait_prior failed.This
5894 indicates a logic error in the supervisor or CPU
5895 or memory hardware problems.
5896
5897 Action: Contact the system programming staff._sa
5898
5899
5900 as_init_.pl1
5901 as_init_: ERROR_MESSAGE. Could not set RW access
5902 on SYSTEM_CONTROL_DIR>TABLE.
5903
5904
5905 Stream: as severity 1
5906
5907 Time: System Intialization.
5908
5909 Meaning: An error occurred attempting to add ACL entries to
5910 TABLE in SYSTEM_CONTROL_DIR. Answering Service
5911 initialization fails. The system administrator
5912 must enter admin mode and correct the problem.
5913 Then reboot the system.
5914
5915 Action: Contact the system programming staff._sa
5916
5917
5918 as_init_.pl1
5919 as_init_: ERROR_MESSAGE. Error while defining
5920 initial work classes.
5921
5922
5923 Stream: as severity 1
5924
5925 Time: System Intialization.
5926
5927
5928
5929
5930 as_init_ 103 08/03/23 MR12.7^L
5931
5932
5933 Meaning: This indicates a logic error in the supervisor or
5934 CPU or memory hardware problems. Answering
5935 Service initialization fails. The system
5936 administrator must enter admin mode and correct
5937 the problem. Then reboot the system.
5938
5939 Action: Contact the system programming staff._sa
5940
5941
5942 as_init_.pl1
5943 as_init_: ERROR_MESSAGE. Initialization of
5944 MODULE failed. ADDED_INFO.
5945
5946
5947 Stream: as severity 1
5948
5949 Time: System Intialization.
5950
5951 Meaning: MODULE was being initialized when it detected a
5952 problem. It called sub_err_ to report the error
5953 to as_init_. ERROR_MESSAGE gives the text
5954 associated with the error code MODULE returned to
5955 as_init_. If present ADDED_INFO gives further
5956 details about the problem. Some steps of
5957 Answering Service initialization were not
5958 performed. This may cause the system to operate
5959 incorrectly.
5960
5961 Action: Contact the system programming staff.
5962
5963
5964 as_init_.pl1
5965 as_init_: ERROR_MESSAGE. MODULE signalled
5966 sub_error_; initialization continues.
5967 ADDED_INFO.
5968
5969
5970
5971 Stream: as severity 1
5972
5973 Time: System Intialization.
5974
5975 Meaning: MODULE was being initialized when it detected a
5976 problem. It called sub_err_ to report the error
5977 to as_init_. ERROR_MESSAGE gives the text
5978 associated with the error code MODULE returned to
5979 as_init_. If present ADDED_INFO gives further
5980 details about the problem. Initialization of the
5981 module continues.
5982
5983 Action: Contact the system programming staff..
5984
5985
5986
5987
5988 as_init_ 104 08/03/23 MR12.7^L
5989
5990
5991 as_init_.pl1
5992 as_init_: ERROR_MESSAGE. Repeated CDT threading
5993 inconsistencies.
5994
5995
5996 Stream: as severity 1
5997
5998 Time: System Intialization.
5999
6000 Meaning: Channel Definition Table CDT entry threads were
6001 found to be damaged even after rethreading
6002 completed successfully.This indicates a logic
6003 error in the supervisor or CPU or memory hardware
6004 problems.
6005
6006 Action: Contact the system programming staff._sa
6007
6008
6009 as_init_.pl1
6010 as_init_: ERROR_MESSAGE. Shutting down the login
6011 server request mechanism.
6012
6013
6014 Stream: as severity 1
6015
6016 Time: System shutdown.
6017
6018 Meaning: An error occurred while shutting down the login
6019 server request mechanism. The ERROR_MESSAGE gives
6020 the text associated with the error code returned
6021 from ls_request_server_$shutdown.
6022
6023 Action: No operator action is required.
6024
6025
6026 as_init_.pl1
6027 as_init_: ERROR_MESSAGE.
6028 SYSTEM_CONTROL_DIR>TABLE. Forcing access.
6029
6030
6031 Stream: as severity 1
6032
6033 Time: System Intialization.
6034
6035 Meaning: During system initialization TABLE in
6036 SYSTEM_CONTROL_DIR was found to have an incorrect
6037 ACL. Access was set for Initializer.SysDaemon.
6038
6039 Action: No operator action is required.
6040
6041
6042
6043
6044
6045
6046 as_init_ 105 08/03/23 MR12.7^L
6047
6048
6049 as_init_.pl1
6050 as_init_: installation_parms damaged. N rate
6051 structures defined; from I to J allowed.
6052
6053
6054
6055 Stream: as severity 1
6056
6057 Time: System Intialization.
6058
6059 Meaning: The installation_parms table claims to declare an
6060 unallowed number of rate structures. This
6061 indicates that the table has been damaged. The
6062 system administrator must rectify the problem
6063 using ed_installation_parms from admin mode
6064 before the Answering Service will initialize. It
6065 will be necessary to re-boot Multics to retry
6066 Answering Service initialization.
6067
6068 Action: Contact the system programming staff._sa
6069
6070
6071 as_init_.pl1
6072 as_init_: Multics SYSID; Answering Service
6073 VERSION
6074
6075
6076 Stream: as severity 1
6077
6078 Time: System Intialization.
6079
6080 Meaning: Answering Service initialization is complete and
6081 users may now log in. The current system version
6082 number from the system tape is SYSID. The
6083 current Answering Service version number is
6084 VERSION.
6085
6086 Action: Proceed with startup.
6087
6088
6089 as_init_.pl1
6090 as_init_: No "tcd" card in the config deck.
6091 Assuming APT size of 1000.
6092
6093
6094 Stream: as severity 1
6095
6096 Time: System Intialization.
6097
6098 Meaning: This message indicates that there is no TCD card
6099 in the config deck. The system will operate
6100 normally but it is recommended that an explicit
6101 TCD card be added at the first convenience.
6102
6103
6104 as_init_ 106 08/03/23 MR12.7^L
6105
6106
6107 Action: Contact the system programming staff._sa
6108
6109
6110 as_init_.pl1
6111 as_init_: rebuilding SAT hash table.
6112
6113
6114 Stream: as severity 1
6115
6116 Time: System Intialization.
6117
6118 Meaning: The hash table for the SAT was corrupted. The
6119 hash table is regenerated.
6120
6121 Action: No operator action is required.
6122
6123
6124 as_init_.pl1
6125 as_init_: Resource management is disabled;
6126 >sc1>rtdt needs it enabled.
6127
6128
6129 Stream: as severity 1
6130
6131 Time: System Intialization.
6132
6133 Meaning: The copy of installation_parms encountered by
6134 system startup claims that RCP resource management
6135 is disabled. This disagrees with information in
6136 the RTDT. If startup were to continue all
6137 information in resource registries would be lost.
6138 Answering Service initialization fails. The
6139 system administrator must use
6140 ed_installation_parms from admin mode to repair
6141 the damage. Then reboot the system.
6142
6143 Action: Contact the system programming staff._sa
6144
6145
6146 as_init_.pl1
6147 as_init_: SAT version inconsistent with
6148 declarations used in this program.
6149
6150
6151 Stream: as severity 1
6152
6153 Time: System Intialization.
6154
6155 Meaning: The version number stored in the SAT does not
6156 match the expected version number which is a
6157 constant in the Answering Service programs. This
6158 may be because the SAT has been destroyed or
6159 because an incorrect version of the Answering
6160
6161
6162 as_init_ 107 08/03/23 MR12.7^L
6163
6164
6165 Service programs is being used. BOS Typewriter
6166 Crashes systemes
6167
6168 Action: Contact the system programming staff._sa The
6169 System Administrator must either generate a new
6170 SAT or install the correct version of the
6171 Answering Service. If the System Administrator is
6172 not available enter admin mode and attempt to
6173 retrieve a recent copy of the SAT. Then exit from
6174 admin mode and try startup again.
6175
6176
6177
6178 as_init_.pl1
6179 as_init_: SYSTEM_CONTROL_DIR>TABLE missing.
6180 Creating new one.
6181
6182
6183 Stream: as severity 1
6184
6185 Time: System Intialization.
6186
6187 Meaning: A new version of TABLE was created in
6188 SYSTEM_CONTROL_DIR as part of system
6189 initialization.
6190
6191 Action: No operator action is required.
6192
6193
6194 as_init_.pl1
6195 as_init_: The requested action was not performed.
6196 Cannot type go twice.
6197
6198
6199 Stream: as severity 1
6200
6201 Time: System Intialization.
6202
6203 Meaning: The operator typed go when Multics was already in
6204 operation. No action was taken.
6205
6206 Action: No operator action is required.
6207
6208
6209 as_init_.pl1
6210 as_init_: The requested action was not performed.
6211 Type multics first.
6212
6213
6214 Stream: as severity 1
6215
6216 Time: System Intialization.
6217
6218
6219
6220 as_init_ 108 08/03/23 MR12.7^L
6221
6222
6223 Meaning: The operator typed go without typing multics. No
6224 action was taken.
6225
6226 Action: Type multics first or startup.
6227
6228
6229 as_init_.pl1
6230 as_init_: The requested action was not performed.
6231 Multics already initialized.
6232
6233
6234 Stream: as severity 1
6235
6236 Time: System Intialization.
6237
6238 Meaning: The operator typed startup multics or go when
6239 Multics was already in operation. No action was
6240 taken.
6241
6242 Action: No operator action is required.
6243
6244
6245 as_init_.pl1
6246 as_init_: This procedure does not implement the
6247 requested version. installation_parms version N.
6248
6249
6250
6251 Stream: as severity 1
6252
6253 Time: System Intialization.
6254
6255 Meaning: This indicates a logic error in the supervisor or
6256 CPU or memory hardware problems. The
6257 installation_parms segment has been damaged or is
6258 not up-to-date. The system administrator must
6259 rectify the problem using ed_installation_parms
6260 from admin mode before the Answering Service will
6261 initialize. It will be necessary to re-boot
6262 Multics to retry Answering Serviceinitialization.
6263
6264 Action: Contact the system programming staff._sa
6265
6266
6267 as_lap_mpx_.pl1
6268 as_lap_mpx: Unexpected signal for multiplexer
6269 MPX.
6270
6271
6272 Stream: as severity1
6273
6274 Time: While system is running.
6275
6276
6277
6278 as_lap_mpx 109 08/03/23 MR12.7^L
6279
6280
6281 Meaning: An unknown type event was signaled for multiplexer
6282 MPX. It will be ignored.
6283
6284 Action: Contact the system programming staff.
6285
6286
6287 as_lap_mpx_.pl1
6288 as_lap_mpx_: Bad argument to parm PPPP should be
6289 XXXX or YYYY
6290
6291
6292 Stream: as severity1
6293
6294 Time: In response to an operator load_mpx command for
6295 during system startup.
6296
6297 Meaning: A bad value was specified for the PPPP parameter
6298 in the TTF entry for this muliplexer. Its value
6299 must be either XXXX or YYYY.
6300
6301 Action: Check the contents of the TTF entry for the
6302 terminal_type associated with the multiplexer for
6303 errors.
6304
6305
6306
6307 as_lap_mpx_.pl1
6308 as_lap_mpx_: Crash signalled for multiplexer MPX.
6309
6310
6311 Stream: as severity1
6312
6313 Time: While system is running.
6314
6315 Meaning: The multiplexer has crashed. The LAP link has
6316 entered the disconnected state.
6317
6318 Action: Contact the system programming staff.
6319
6320
6321 as_lap_mpx_.pl1
6322 as_lap_mpx_: Error in conversion. Converting
6323 FIELD VALUE to a number for multiplexer MPX.
6324
6325
6326 Stream: as severity1
6327
6328 Time: In response to an operator load_mpx command or
6329 during system start up.
6330
6331 Meaning: It was impossible to convert a numeric parameter
6332 from the terminal_type additional_info string to
6333 its internal form. FIELD is the name of the
6334
6335
6336 as_lap_mpx_ 110 08/03/23 MR12.7^L
6337
6338
6339 parameter in error. VALUE is the string which
6340 could not be converted.
6341
6342 Action: Check the contents of the TTF entry for the
6343 terminal_type associated with the multiplexer for
6344 errors.
6345
6346
6347
6348 as_lap_mpx_.pl1
6349 as_lap_mpx_: ERROR. Cannot get additional info
6350 for terminal type TTP for multiplexer MPX.
6351
6352
6353 Stream: as severity1
6354
6355 Time: In response to an operator load_mpx command or
6356 during system start up.
6357
6358 Meaning: An error occurred while retrieving the parameters
6359 of the multiplexer from the TTT. Either the
6360 terminal type specified in the CDT does not exist
6361 or it does not contain the required
6362 additional_info field.
6363
6364 Action: Check that the CMF and TTF contain the proper
6365 information.
6366
6367
6368 as_lap_mpx_.pl1
6369 as_lap_mpx_: ERROR. Creating event channel for
6370 multiplexer MPX.
6371
6372
6373 Stream: as severity1
6374
6375 Time: In response to an operator load_mpx command or
6376 during system start up.
6377
6378 Meaning: An ipc_ error occurred while trying to initialize
6379 the multiplexer.
6380
6381 Action: Contact the system programming staff.
6382
6383
6384 as_lap_mpx_.pl1
6385 as_lap_mpx_: Load failed for multiplexer MPX.
6386
6387
6388 Stream: as severity1
6389
6390 Time: In response to an operator load_mpx command or
6391 during system start up.
6392
6393
6394 as_lap_mpx_ 111 08/03/23 MR12.7^L
6395
6396
6397 Meaning: The attempt to load the multiplexer failed. This
6398 should never happen.
6399
6400 Action: Contact the system programming staff.
6401
6402
6403 as_lap_mpx_.pl1
6404 as_lap_mpx_: Load signalled for multiplexer MPX.
6405
6406
6407 Stream: as severity1
6408
6409 Time: In response to an operator load_mpx command or
6410 during system start up.
6411
6412 Meaning: The multiplexer has been successfully loaded. It
6413 will be started unless the -no_start control
6414 argument was given when the load_mpx command was
6415 typed.
6416
6417 Action: No operator action is required.
6418
6419
6420 as_lap_mpx_.pl1
6421 as_lap_mpx_: Unexpected wakeup DATA from
6422 process PRCID.
6423
6424
6425 Stream: as severity1
6426
6427 Time: While system is running.
6428
6429 Meaning: The multiplexer manager received a wakeup from an
6430 unexpected source. The wakeup is ignored.
6431
6432 Action: No operator action is required.
6433
6434
6435 as_lap_mpx_.pl1
6436 as_lap_mpx_: Wakeup for multiplexer MPX has
6437 invalid state code STATE.
6438
6439
6440 Stream: as severity1
6441
6442 Time: While system is running.
6443
6444 Meaning: A wakeup with invalid data was received by the
6445 multiplexer manager. The wakeup is ignored.
6446
6447 Action: Contact the system programming staff.
6448
6449
6450
6451
6452 as_mcs_mpx_ trace 112 08/03/23 MR12.7^L
6453
6454
6455 as_mcs_mpx_.pl1
6456 as_mcs_mpx_ trace: FNP FNP_NUMBER MPXE state
6457 MPX_STATE FNP state FNP_STATE deconfigured.
6458
6459
6460
6461 Stream: as severity 1
6462
6463 Time: While system is running.
6464
6465 Meaning: This is a tracing message which displays some
6466 values of variables that describe the status of
6467 the FNP.
6468
6469 Action: Contact the system programming staff.
6470
6471
6472 as_mcs_mpx_.pl1
6473 as_mcs_mpx_: Crash signalled for FNP TAG.
6474
6475
6476 Stream: as severity 1
6477
6478 Time: While system is running.
6479
6480 Meaning: FNP TAG has crashed. A reload of the FNP will be
6481 attempted if it is not in a crash loop or not
6482 inactive.
6483
6484 Action: Contact the system programming staff.
6485
6486
6487 as_mcs_mpx_.pl1
6488 as_mcs_mpx_: ERROR_CODE_MESSAGE
6489 >sc1>fnp_crash_notify.ec does not exist.
6490
6491
6492 Stream: as severity 1
6493
6494 Time: While system is running.
6495
6496 Meaning: An error occured ERROR_CODE_MESSAGE when
6497 checking for the existence of fnp_crash_notify.ec
6498 in the system_control_1 directory.
6499
6500 Action: Contact the system programming staff.
6501
6502
6503 as_mcs_mpx_.pl1
6504 as_mcs_mpx_: ERROR_CODE_MESSAGE Creating event
6505 channel for FNP TAG.
6506
6507
6508
6509
6510 as_mcs_mpx_ 113 08/03/23 MR12.7^L
6511
6512
6513 Stream: as severity 1
6514
6515 Time: While system is running.
6516
6517 Meaning: An error occured ERROR_CODE_MESSAGE when an
6518 attempt was made to create an event channel for
6519 FNP TAG. The load attempt has been aborted. This
6520 message can also be logged if an error occured
6521 when changing the just created event-wait channel
6522 into an event-call channel.
6523
6524 Action: Contact the system programming staff.
6525
6526
6527 as_mcs_mpx_.pl1
6528 as_mcs_mpx_: ERROR_CODE_MESSAGE Failed to
6529 establish an SCI environment.
6530
6531
6532 Stream: as severity 1
6533
6534 Time: While system is running.
6535
6536 Meaning: An error occured ERROR_CODE_MESSAGE when trying
6537 to create an system control subsystem environment
6538 pointer.
6539
6540 Action: Contact the system programming staff.
6541
6542
6543 as_mcs_mpx_.pl1
6544 as_mcs_mpx_: ERROR_CODE_MESSAGE Reading event
6545 channel for FNP TAG.
6546
6547
6548 Stream: as severity 1
6549
6550 Time: While system is running.
6551
6552 Meaning: An error occured ERROR_CODE_MESSAGE when an
6553 attempt was made to read the bootload event
6554 channel for FNP TAG.
6555
6556 Action: Contact the system programming staff.
6557
6558
6559 as_mcs_mpx_.pl1
6560 as_mcs_mpx_: ERROR_CODE_MESSAGE Resetting event
6561 channel for FNP TAG.
6562
6563
6564 Stream: as severity 1
6565
6566
6567
6568 as_mcs_mpx_ 114 08/03/23 MR12.7^L
6569
6570
6571 Time: While system is running.
6572
6573 Meaning: An error occured ERROR_CODE_MESSAGE when an
6574 attempt was made to drain all events from the FNP
6575 boot event channel.
6576
6577 Action: Contact the system programming staff.
6578
6579
6580 as_mcs_mpx_.pl1
6581 as_mcs_mpx_: ERROR_CODE_MESSAGE Taking dump of
6582 FNP TAG. FNP_DUMP_ENTRY_NAME
6583
6584
6585 Stream: as severity 1
6586
6587 Time: While system is running.
6588
6589 Meaning: An error occured ERROR_CODE_MESSAGE when an
6590 attempt was made to dump FNP TAG into the
6591 FNP_DUMP_ENTRY_NAME segment in >dumps.
6592
6593 Action: Contact the system programming staff.
6594
6595
6596 as_mcs_mpx_.pl1
6597 as_mcs_mpx_: FDUMP of FNP TAG created in
6598 >dumps>FNP_DUMP_ENTRY_NAME
6599
6600
6601 Stream: as severity 1
6602
6603 Time: While system is running.
6604
6605 Meaning: FNP TAG has been dumped successfully into the
6606 >dumps>FNP_DUMP_ENTRY_NAME segment after it
6607 crashed.
6608
6609 Action: Contact the system programming staff.
6610
6611
6612 as_mcs_mpx_.pl1
6613 as_mcs_mpx_: Inconsistent wakeup received from
6614 FNP TAG. FNP state = FNP_STATE msg state =
6615 MSG_STATE.
6616
6617
6618
6619 Stream: as severity 1
6620
6621 Time: While system is running.
6622
6623
6624
6625
6626 as_mcs_mpx_ 115 08/03/23 MR12.7^L
6627
6628
6629 Meaning: The data in the message from the bootload event
6630 channel for FNP TAG indicates that the FNP was in
6631 an inconsistant state MSG_STATE with the current
6632 state FNP_STATE of the FNP in the CDT.
6633
6634 Action: Contact the system programming staff.
6635
6636
6637 as_mcs_mpx_.pl1
6638 as_mcs_mpx_: Invalid wakeup received for FNP TAG.
6639 Wakeup appears to be for FNP OTHER_TAG
6640 #FNP_NUMBER.
6641
6642
6643
6644 Stream: as severity 1
6645
6646 Time: While system is running.
6647
6648 Meaning: Invalid wakeup received on bootload event channel
6649 for FNP TAG. Wakeup data indicates it is for FNP
6650 OTHER_TAG whose number is FNP_NUMBER.
6651
6652 Action: Contact the system programming staff.
6653
6654
6655 as_mcs_mpx_.pl1
6656 as_mcs_mpx_: Load failed for FNP TAG.
6657
6658
6659 Stream: as severity 1
6660
6661 Time: While system is running.
6662
6663 Meaning: The FNP TAG failed to load successfully.
6664
6665 Action: Try the bootload attempt again. If problem
6666 persists contact the programing staff.
6667
6668
6669
6670 as_mcs_mpx_.pl1
6671 as_mcs_mpx_: Load of FNP TAG did not complete
6672 within X minutes.
6673
6674
6675 Stream: as severity 2
6676
6677 Time: While system is running.
6678
6679 Meaning: FNP TAG did not signal that it had completed the
6680 load attempt within the required X minutes from
6681 the time that the image was sent to the FNP.
6682
6683
6684 as_mcs_mpx_ 116 08/03/23 MR12.7^L
6685
6686
6687 Action: Try to load the FNP again. If problem persists
6688 contact system programing staff.
6689
6690
6691
6692 as_mcs_mpx_.pl1
6693 as_mcs_mpx_: Load signalled for FNP TAG.
6694
6695
6696 Stream: as severity 1
6697
6698 Time: While system is running.
6699
6700 Meaning: FNP TAG bootloaded successfully.
6701
6702 Action: No operator action is required.
6703
6704
6705 as_mcs_mpx_.pl1
6706 as_mcs_mpx_: Procedure called with bad fnpep into
6707 cdt: POINTER
6708
6709
6710 Stream: as severity 1
6711
6712 Time: While system is running.
6713
6714 Meaning: The compute_fnp_no internal procedure detected
6715 that as_mcs_mpx_ was supplied with a prointer
6716 value POINTER that should point to an FNP entry
6717 in the CDT but doesn't. Current operation has
6718 been aborted.
6719
6720 Action: Contact the system programming staff.
6721
6722
6723 as_mcs_mpx_.pl1
6724 as_mcs_mpx_: Tracing off.
6725
6726
6727 Stream: as severity 1
6728
6729 Time: While system is running.
6730
6731 Meaning: The trace_off entry point has been called and now
6732 tracing has been disabled.
6733
6734 Action: Contact the system programming staff.
6735
6736
6737 as_mcs_mpx_.pl1
6738 as_mcs_mpx_: Tracing on.
6739
6740
6741
6742 as_mcs_mpx_ 117 08/03/23 MR12.7^L
6743
6744
6745 Stream: as severity 1
6746
6747 Time: While system is running.
6748
6749 Meaning: The trace_on entry point has been called so that
6750 as_mcs_mpx_ trace data will now be displayed.
6751
6752 Action: Contact the system programming staff.
6753
6754
6755 as_mcs_mpx_.pl1
6756 as_mcs_mpx_: Unexpected wakeup EV_MSG_WORD_1
6757 EV_MSG_WORD_2 from process PROC_ID.
6758
6759
6760
6761 Stream: as severity 1
6762
6763 Time: While system is running.
6764
6765 Meaning: An unexpected wakeup occured on an FNP bootload
6766 event channel from process PROC_ID. The event
6767 message data is in EV_MSG_WORD_1 and
6768 EV_MSG_WORD_2. Unable to determine FNP tag.
6769
6770 Action: Contact the system programming staff.
6771
6772
6773 as_mcs_mpx_.pl1
6774 as_mcs_mpx_: Wakeup for FNP TAG has invalid state
6775 code: CODE.
6776
6777
6778 Stream: as severity 1
6779
6780 Time: While system is running.
6781
6782 Meaning: Wakeup message data received on bootload event
6783 channel for FNP TAG contains an invalid state code
6784 value of CODE. Valid values for mpxe.state are
6785 defined in the cdt.incl.pl1 include file by the
6786 FNP_* variables.
6787
6788 Action: Contact the system programming staff.
6789
6790
6791 as_mcs_mpx_.pl1
6792 as_mcs_mpx_: Wakeup with bad data pointer
6793 ignored: POINTER
6794
6795
6796 Stream: as severity 1
6797
6798
6799
6800 as_mcs_mpx_ 118 08/03/23 MR12.7^L
6801
6802
6803 Time: While system is running.
6804
6805 Meaning: A wakeup was received on an FNP bootload event
6806 channel with which a bad data pointer was
6807 supplied. Unable to determine FNP tag.
6808
6809 Action: Contact the system programming staff.
6810
6811
6812 as_meter_.pl1
6813 as_meter_: FDUMP number is NNN
6814
6815
6816 Stream: as severity1
6817
6818 Time: System Intialization.
6819
6820 Meaning: The system is coming up after a crash. There is a
6821 dump created by the bce dump command in the DUMP
6822 partition. Usually system_start_up.ec copies
6823 this dump into the directory >dumps.
6824
6825 Action: Follow site instructions concerning the processing
6826 of online dumps. The normal procedure is to log
6827 in Print_Dump.SysDaemon and request that it
6828 process the dump.
6829
6830
6831
6832 as_meter_.pl1
6833 as_meter_: Problem getting "ITEM". Metering
6834 disabled.
6835
6836
6837 Stream: as severity2
6838
6839 Time: System Intialization.
6840
6841 Meaning: The metering module cannot obtain a pointer to the
6842 ring 0 hardcore data item ITEM used in
6843 calculating system usage. Metering figures are
6844 scrambled but the system should be able to run.
6845
6846 Action: Contact the system programming staff.
6847
6848
6849 as_request_bump_user_.pl1
6850 as_request_bump_user_: BUMPING PERS.PROJ.TAG
6851 PROCESSID for requestor REQ_PERS.REQ_PROJ.REQ_TAG.
6852
6853
6854
6855 Stream: as severity 0
6856
6857
6858 as_request_bump_user_ 119 08/03/23 MR12.7^L
6859
6860
6861 Time: While system is running.
6862
6863 Meaning: An answering service request from
6864 REQ_PERS.REQ_PROJ.REQ_TAG to bump the process
6865 PERS.PROJ.TAG PROCESSID has been initiated.
6866
6867 Action: No operator action is required.
6868
6869
6870 as_request_bump_user_.pl1
6871 as_request_bump_user_: ERROR_MSG. Rejected
6872 BUMP_USER request from PERS.PROJ.TAG to bump
6873 process PROCESS_ID. REASON
6874
6875
6876
6877 Stream: as severity 0
6878
6879 Time: While system is running.
6880
6881 Meaning: The answering service request from PERS.PROJ.TAG
6882 to bump the process identified by PROCESSID failed
6883 for the given REASON and ERROR_MSG.
6884
6885 Action: Contact the system programming staff._sa
6886
6887
6888 as_request_note_pnt_change_.pl1
6889 as_request_note_pnt_change_: Bumping user
6890 PERS.PROJ.TAG PROCESSID on channel CHN. REASON
6891
6892
6893
6894 Stream: as severity 0
6895
6896 Time: While system is running.
6897
6898 Meaning: Process PERS.PROJ.TAG on channel CHN was bumped by
6899 a change to the PNT entry for PERS. REASON
6900 describes the type of PNT change.
6901
6902 Action: No operator action is required.
6903
6904
6905
6906 as_request_note_pnt_change_.pl1
6907 as_request_note_pnt_change_: ERROR_MSG. Rejected
6908 NOTE_PNT_CHANGE request from PERS.PROJ. REASON
6909
6910
6911
6912 Stream: as severity 0
6913
6914
6915
6916 as_request_note_pnt_change_ 120 08/03/23 MR12.7^L
6917
6918
6919 Time: While system is running.
6920
6921 Meaning: An answering service request to note a change to
6922 the PNT sent by PERS.PROJ failed because of
6923 REASON.This indicates a logic error in the
6924 supervisor or CPU or memory hardware problems.
6925
6926 Action: Contact the system programming staff.
6927
6928
6929
6930 as_request_note_pnt_change_.pl1
6931 as_request_note_pnt_change_: Lowered maximum
6932 authorization for PERS.PROJ.TAG on channel CHN
6933 from OLD_MAX_AUTH to NEW_MAX_AUTH. PNT change.
6934
6935
6936
6937 Stream: as severity 0
6938
6939 Time: While system is running.
6940
6941 Meaning: A change to the PNT entry for PERS lowered the
6942 maximum authorization associated with the process
6943 PERS.PROJ.TAG on channel CHN. The authorization
6944 was changed from OLD_MAX_AUTH to NEW_MAX_AUTH.
6945
6946 Action: No operator action is required.
6947
6948
6949
6950 as_request_note_pnt_change_.pl1
6951 as_request_note_pnt_change_: Raised minimum
6952 authorization for PERS.PROJ.TAG on channel CHN
6953 from OLD_MIN_AUTH to NEW_MIN_AUTH. PNT change.
6954
6955
6956
6957 Stream: as severity 0
6958
6959 Time: While system is running.
6960
6961 Meaning: A change to the PNT entry for PERS raised the
6962 minimum authorization associated with the process
6963 PERS.PROJ.TAG on channel CHN. The authorization
6964 was changed from OLD_MIN_AUTH to NEW_MIN_AUTH.
6965
6966 Action: No operator action is required.
6967
6968
6969
6970 as_request_note_pnt_change_.pl1
6971 as_request_note_pnt_change_: User has "nobump"
6972
6973
6974 as_request_note_pnt_change_ 121 08/03/23 MR12.7^L
6975
6976
6977 attribute. Did not bump PERS.PROJ.TAG PROCESSID
6978 on channel CHN. REASON
6979
6980
6981
6982 Stream: as severity 0
6983
6984 Time: While system is running.
6985
6986 Meaning: Bump attempt for process PERS.PROJ.TAG with
6987 PROCESSID on channel CHN failed because the user
6988 has the nobump attribute. REASON indicates why
6989 bumping was attempted.
6990
6991 Action: Contact the system programming staff._sa
6992
6993
6994
6995 as_request_server_.pl1
6996 as_request_sender_: MSG. Could not delete
6997 message MID for PERS.PROJ.
6998
6999
7000 Stream: as severity0
7001
7002 Time: While system is running.
7003
7004 Meaning: MSG is an error_table_ message MID is a message
7005 ID PERS.PROJ is the group ID of the AS request
7006 sender. The AS request message could not be
7007 deleted after executing the AS request.
7008
7009 Action: No operator action is required.
7010
7011
7012 as_request_server_.pl1
7013 as_request_sender_: PERS.PROJ PID set fatal
7014 process error logout|new_proc.
7015
7016
7017 Stream: as severity0
7018
7019 Time: While system is running.
7020
7021 Meaning: The process group id PERS.PROJ process id PID
7022 has set the AS flag which indicates that fatal
7023 process errors will cause a logout|new_proc.
7024
7025 Action: No operator action is required.
7026
7027
7028 as_request_server_.pl1
7029
7030
7031
7032 as_request_server_$init 122 08/03/23 MR12.7^L
7033
7034
7035 as_request_server_$init: MSG. Deleting
7036 >sc1>as_request_.ms.
7037
7038
7039 Stream: as severity1
7040
7041 Time: Answering Service initialization.
7042
7043 Meaning: MSG is an error_table_ message. An error was
7044 encountered while attempting to delete the
7045 as_request message segment prior to re-creating
7046 it. as_request_server_$init continues and
7047 attempts to create the message segment.
7048
7049 Action: No operator action is required.
7050
7051
7052 as_request_server_.pl1
7053 as_request_server_$init: MSG. Manipulating
7054 >sc1>as_request_.ms or IPC channels.
7055
7056
7057 Stream: as severity1
7058
7059 Time: Answering Service initialization.
7060
7061 Meaning: MSG is an error_table_ message. A programming
7062 error has been encountered.
7063
7064 Action: Contact the system programming staff. After the
7065 problem is corrected repeat the bootload
7066 operation.
7067
7068
7069
7070 as_request_server_.pl1
7071 as_request_server_: ERROR_MESSAGE. Can't find
7072 message from PGID
7073
7074
7075 Stream: as severity0
7076
7077 Time: While system is running.
7078
7079 Meaning: MSG is an error_table_ message and PGID is a
7080 process group id. A process sent a wakeup to the
7081 Answering Service but did not put a message in
7082 as_request.ms.
7083
7084 Action: No operator action is required.
7085
7086
7087 as_request_server_.pl1
7088
7089
7090 as_request_server_ 123 08/03/23 MR12.7^L
7091
7092
7093 as_request_server_: Message for "REQUEST NAME"
7094 type N too short from PERS.PROJ.
7095
7096
7097 Stream: as severity0
7098
7099 Time: While system is running.
7100
7101 Meaning: A request of type N sent by the process group id
7102 specified by PERS.PROJ was in error. The request
7103 is ignored. If the request is shorter than the
7104 standard request header which precedes all
7105 requests then the request type is not present in
7106 the message.
7107
7108 Action: No operator action is required.
7109
7110
7111 as_request_server_.pl1
7112 as_request_server_: MSG. Process no longer
7113 active for request from PERS.PROJ.
7114
7115
7116 Stream: as severity0
7117
7118 Time: While system is running.
7119
7120 Meaning: MSG is an error_table_ message and PERS.PROJ isthe
7121 sender id. A process sent a wakeup to the
7122 Answering Service but then logged out before the
7123 Answering Service handled the wakeup.
7124
7125 Action: No operator action is required.
7126
7127
7128 as_request_server_.pl1
7129 as_request_server_: MSG. Error reading message
7130 from message segment.
7131
7132
7133 Stream: as severity0
7134
7135 Time: While system is running.
7136
7137 Meaning: MSG is an error_table_ message. An error occurred
7138 while reading an AS message from the AS request
7139 queue.
7140
7141 Action: No operator action is required.
7142
7143
7144 as_request_server_.pl1
7145
7146
7147
7148 as_request_server_ 124 08/03/23 MR12.7^L
7149
7150
7151 as_request_server_: Rejected invalid type XX
7152 message from PERS.PROJ PID.
7153
7154
7155 Stream: as severity0
7156
7157 Time: While system is running.
7158
7159 Meaning: An invalid wakeup request has been sent to
7160 as_request_server_. The sending process ID is
7161 PID and the sender name in the message is
7162 PERS.PROJ. The request is a type XX request. No
7163 action was taken.
7164
7165 Action: No operator action is required.
7166
7167
7168 as_request_server_.pl1
7169 as_request_server_: Request message segment not
7170 initialized or shutdown has been typed.
7171
7172
7173 Stream: as severity1
7174
7175 Time: While system is running.
7176
7177 Meaning: A request is being ignored because the AS request
7178 queue has not been initialized or the the operator
7179 has typed the shutdown command.
7180
7181 Action: No operator action is required.
7182
7183
7184 as_x25_mpx_.pl1
7185 as_x25_mpx_: Bad argument to parm PARM should be
7186 THIS or THAT but was VALUE for multiplexer MPX.
7187
7188
7189 Stream: as severity1
7190
7191 Time: In response to an operator load_mpx command or
7192 during system start up.
7193
7194 Meaning: A bad value was specified for parameter PARM in
7195 the additional_info field of the TTF entry for the
7196 multiplexer MPX. The choices are THIS or THAT
7197 but VALUE was specified.
7198
7199 Action: Check the contents of the TTF entry for the
7200 terminal_type associated with the multiplexer for
7201 an improper parameter value. Correct and reload
7202 mpx.
7203
7204
7205
7206 as_x25_mpx_ 125 08/03/23 MR12.7^L
7207
7208
7209
7210
7211 as_x25_mpx_.pl1
7212 as_x25_mpx_: Bad argument to parm PARM. Must
7213 have: LOW <= value <= HIGH but value = VALUE
7214 for multiplexer MPX.
7215
7216
7217 Stream: as severity1
7218
7219 Time: In response to an operator load_mpx command or
7220 during system start up.
7221
7222 Meaning: A bad value was specified for parameter PARM in
7223 the additional_info field of the TTF entry for the
7224 multiplexer MPX. The value must be between LOW
7225 and HIGH but VALUE was specified.
7226
7227 Action: Check the contents of the TTF entry for the
7228 terminal_type associated with the multiplexer for
7229 an improper parameter value. Correct and reload
7230 mpx.
7231
7232
7233
7234 as_x25_mpx_.pl1
7235 as_x25_mpx_: Crash signalled for multiplexer MPX.
7236
7237
7238 Stream: as severity1
7239
7240 Time: While system is running.
7241
7242 Meaning: The multiplexer has crashed. The LAP link has
7243 entered the disconnected state.
7244
7245 Action: Contact the system programming staff.
7246
7247
7248 as_x25_mpx_.pl1
7249 as_x25_mpx_: Error in conversion. Converting
7250 FIELD VALUE to a number for multiplexer MPX.
7251
7252
7253 Stream: as severity1
7254
7255 Time: In response to an operator load_mpx command or
7256 during system start up.
7257
7258 Meaning: It was impossible to convert a numeric parameter
7259 from the terminal_type additional_info string to
7260 its internal form. FIELD is the name of the
7261
7262
7263
7264 as_x25_mpx_ 126 08/03/23 MR12.7^L
7265
7266
7267 parameter in error. VALUE is the string which
7268 could not be converted.
7269
7270 Action: Check the contents of the TTF entry for the
7271 terminal_type associated with the multiplexer for
7272 errors.
7273
7274
7275
7276 as_x25_mpx_.pl1
7277 as_x25_mpx_: ERROR. Cannot get additional info
7278 for terminal type TTP for multiplexer MPX.
7279
7280
7281 Stream: as severity1
7282
7283 Time: In response to an operator load_mpx command or
7284 during system start up.
7285
7286 Meaning: An error occurred while retrieving the parameters
7287 of the multiplexer from the TTT. Either the
7288 terminal type specified in the CDT does not exist
7289 or it does not contain the required
7290 additional_info field.
7291
7292 Action: Check that the CMF and TTF contain the proper
7293 information.
7294
7295
7296 as_x25_mpx_.pl1
7297 as_x25_mpx_: ERROR. Creating event channel for
7298 multiplexer MPX.
7299
7300
7301 Stream: as severity1
7302
7303 Time: In response to an operator load_mpx command or
7304 during system start up.
7305
7306 Meaning: An ipc_ error occurred while trying to initialize
7307 the multiplexer.
7308
7309 Action: Contact the system programming staff.
7310
7311
7312 as_x25_mpx_.pl1
7313 as_x25_mpx_: Load failed for multiplexer MPX.
7314
7315
7316 Stream: as severity1
7317
7318 Time: In response to an operator load_mpx command or
7319 during system start up.
7320
7321
7322 as_x25_mpx_ 127 08/03/23 MR12.7^L
7323
7324
7325 Meaning: The attempt to load the multiplexer failed. This
7326 should never happen.
7327
7328 Action: Contact the system programming staff.
7329
7330
7331 as_x25_mpx_.pl1
7332 as_x25_mpx_: Load signalled for multiplexer MPX.
7333
7334
7335 Stream: as severity1
7336
7337 Time: In response to an operator load_mpx command or
7338 during system start up.
7339
7340 Meaning: The multiplexer has been successfully loaded. It
7341 will be started unless the -no_start control
7342 argument was given when the load_mpx command was
7343 typed.
7344
7345 Action: No operator action is required.
7346
7347
7348 as_x25_mpx_.pl1
7349 as_x25_mpx_: MPX: n_lc must be specified.
7350
7351
7352 Stream: as severity1
7353
7354 Time: In response to an operator load_mpx command for
7355 during system startup.
7356
7357 Meaning: The TTF entry for the X.25 multiplexer does not
7358 specify the number of logical channels.
7359
7360 Action: Correct the TTF and reload the multiplexer.
7361
7362
7363 as_x25_mpx_.pl1
7364 as_x25_mpx_: Unexpected signal NUM in state
7365 STATE.
7366
7367
7368 Stream: as severity1
7369
7370 Time: While system is running.
7371
7372 Meaning: A signal NUM was received unexpectedly in state
7373 STATE. The signal is ignored.
7374
7375 Action: Contact the system programming staff.
7376
7377
7378
7379
7380 as_x25_mpx_ 128 08/03/23 MR12.7^L
7381
7382
7383 as_x25_mpx_.pl1
7384 as_x25_mpx_: Unexpected wakeup DATA from
7385 process PRCID.
7386
7387
7388 Stream: as severity1
7389
7390 Time: While system is running.
7391
7392 Meaning: The multiplexer manager received a wakeup from an
7393 unexpected source. The wakeup is ignored.
7394
7395 Action: No operator action is required.
7396
7397
7398 as_x25_mpx_.pl1
7399 as_x25_mpx_: Wakeup for multiplexer MPX has
7400 invalid state code STATE.
7401
7402
7403 Stream: as severity1
7404
7405 Time: While system is running.
7406
7407 Meaning: A wakeup with invalid data was received by the
7408 multiplexer manager. The wakeup is ignored.
7409
7410 Action: Contact the system programming staff.
7411
7412
7413 asr_abs_command_server_.pl1
7414 asr_abs_command_server_: Request REQUEST not
7415 found could not cancel for USER.
7416
7417
7418 Stream: as severity0
7419
7420 Time: While system is running.
7421
7422 Meaning: User USER requested cancellation of absentee job
7423 REQUEST which did not exist.
7424
7425 Action: No operator action is required.
7426
7427
7428 asr_daemon_command_server_.pl1
7429 asr_daemon_command_server_: Denied
7430 send_daemon_command for USER in ring RING.
7431
7432
7433 Stream: $sc
7434
7435 Time: While system is running.
7436
7437
7438 asr_daemon_command_server_ 129 08/03/23 MR12.7^L
7439
7440
7441 Meaning: User USER requested the system to execute a daemon
7442 command but lacked access to
7443 >sc1>admin_acs>send_admin_command.acs or the
7444 appropriate daemon source ACS.
7445
7446 Action: No operator action is required.
7447
7448
7449 asr_daemon_command_server_.pl1
7450 asr_daemon_command_server_: Failed to check
7451 access for USER.
7452
7453
7454 Stream: $sc
7455
7456 Time: While system is running.
7457
7458 Meaning: User USER requested the system to execute a daemon
7459 command but validate_daemon_commands was not
7460 enabled and the system could not determine their
7461 access to the send_daemon_command acs.
7462
7463 Action: No operator action is required.
7464
7465
7466 asr_daemon_command_server_.pl1
7467 asr_daemon_command_server_: PERSON: COMMAND INFO
7468
7469
7470 Stream: $sc
7471
7472 Time: While system is running.
7473
7474 Meaning: A system administrator has sent a for a daemon to
7475 the Initializer which executes it.
7476
7477 Action: No operator action is required.
7478
7479
7480 astty_.pl1
7481 astty_: ERROR_TABLE_MESSAGE CHANNEL has undefined
7482 terminal type TERM_TYPE for set_term_type order.
7483
7484
7485 Stream: as severity 0 or $as1
7486
7487 Time: While system is running.
7488
7489 Meaning: The system received the ERROR_TABLE_MESSAGE when
7490 an attempt was made to set the terminal type of
7491 CHANNEL to TERM_TYPE. Suspect the terminal type
7492 is not known on to the system. The set_term_type
7493 control order was ignored.
7494
7495
7496 astty_ 130 08/03/23 MR12.7^L
7497
7498
7499 Action: Contact the system programming staff.
7500
7501
7502 astty_.pl1
7503 astty_: ERROR_TABLE_MESSAGE CHANNEL NN TEXT
7504
7505
7506 Stream: as severity 0 or $as1
7507
7508 Time: While system is running.
7509
7510 Meaning: This is tracing or error logging output. This
7511 output may appear in the AS log or be printed on
7512 the severity1 stream as directed by astty_ trace
7513 and log_error requests described below.
7514
7515 Action: No operator action is required. Tracing and
7516 logging is controlled by the following entries
7517 which may be typed as commands in admin mode.
7518 astty_$trace - causes tracing of all calls to
7519 astty_
7520 astty_$notrace - disables tracing
7521 astty_$log_error - logs calls to astty_ that get
7522 errors. does not print.
7523 astty_$log_error_1 - logs and prints calls to
7524 astty_ that get errors.
7525 astty_$no_log_error - disables error logging.
7526
7527
7528
7529 astty_.pl1
7530 astty_: ERROR_TABLE_MESSAGE CHANNEL SSSS
7531 line_status failed after line_status_pending
7532
7533
7534 Stream: as severity 0 or $as1
7535
7536 Time: While system is running.
7537
7538 Meaning: System received the ERROR_TABLE_MESSAGE when it
7539 tried to do a line status control order on CHANNEL
7540 in state SSSS after it received a
7541 line_status_pending error code. The error code
7542 for ERROR_TABLE_MESSAGE was returned back to the
7543 caller.
7544
7545 Action: Contact the system programming staff.
7546
7547
7548 astty_.pl1
7549 astty_: ERROR_TABLE_MESSAGE CHANNEL state SSSS >
7550 TTY_HUNG on hung-up error code.
7551
7552
7553
7554 astty_ 131 08/03/23 MR12.7^L
7555
7556
7557 Stream: as severity 0 or $as1
7558
7559 Time: While system is running.
7560
7561 Meaning: An error code of ERROR_TABLE_MESSAGE was returned
7562 while servicing CHANNEL indicating that the
7563 channel is not useable. However the state SSSS
7564 of the channel indicates that the channel was
7565 active thus the CHANNEL state is inconsistant.
7566 The channel will be hungup.
7567
7568 Action: Contact the system programming staff.
7569
7570
7571 astty_.pl1
7572 astty_: ERROR_TABLE_MESSAGE error attaching IOCB
7573 for channel CCCC.
7574
7575
7576 Stream: as severity 0 or $as1
7577
7578 Time: While system is running.
7579
7580 Meaning: The system received the ERROR_TABLE_MESSAGE
7581 attempting to attach to channel CCCC using an
7582 IOCB. The channel was then hungup.
7583
7584 Action: Contact the system programming staff.
7585
7586
7587 astty_.pl1
7588 astty_: ERROR_TABLE_MESSAGE error finding an IOCB
7589 for channel CCCC.
7590
7591
7592 Stream: as severity 0 or $as1
7593
7594 Time: While system is running.
7595
7596 Meaning: The system received the ERROR_TABLE_MESSAGE when
7597 it attempted to find an IOCB for channel CCCC.
7598 The channel was then hungup.
7599
7600 Action: Contact the system programming staff.
7601
7602
7603 astty_.pl1
7604 astty_: ERROR_TABLE_MESSAGE error opening IOCB
7605 for channel CCCC.
7606
7607
7608 Stream: as severity 0 or $as1
7609
7610
7611
7612 astty_ 132 08/03/23 MR12.7^L
7613
7614
7615 Time: While system is running.
7616
7617 Meaning: The system received the ERROR_TALE_MESSAGE
7618 attemping to open the channel CCCC using an IOCB.
7619 The channel was then hungup.
7620
7621 Action: Contact the system programming staff.
7622
7623
7624 astty_.pl1
7625 astty_: tty_state returned SSSS for hung-up line
7626 CHANNEL.
7627
7628
7629 Stream: as severity 0 or $as1
7630
7631 Time: While system is running.
7632
7633 Meaning: In processing the astty_$tty_state entry a call
7634 to hcs_$tty_state returned a state value of SSSS
7635 for hung-up CHANNEL which indicates that the
7636 channel is active. However the returned error
7637 code indicated that the channel is hung-up. The
7638 channel will be hungup.
7639
7640 Action: Contact the system programming staff.
7641
7642
7643 asu_.pl1
7644 asu_$release_ate: bad cdte.process LOCATION for
7645 CHANNEL
7646
7647
7648 Stream: as severity 0
7649
7650 Time: While system is running.
7651
7652 Meaning: This indicates a logic error in the supervisor or
7653 CPU or memory hardware problems. When asked to
7654 release a User Table Entry UTE for an
7655 interactive process the cdte.process pointer
7656 LOCATION did not point into the answer table.
7657 The UTE was not released.
7658
7659 Action: No operator action is required.
7660
7661
7662 asu_.pl1
7663 asu_$release_suspended_process: PERSON.PROJECT
7664 CHANNEL is not suspended
7665
7666
7667 Stream: as severity 0
7668
7669
7670 asu_$release_suspended_process 133 08/03/23 MR12.7^L
7671
7672
7673 Time: Called in response to an operator "abs release"
7674 command or in response to a user reconnecting to
7675 an interactive process.
7676
7677 Meaning: One of the process termination handlers is
7678 incorrectly calling to release a process which is
7679 not currently suspended.
7680
7681 Action: No operator action is required.
7682
7683
7684 asu_.pl1
7685 asu_$remote_cdte: ERROR_MESSAGE. cdte CCC|XXX
7686 error from tty_state
7687
7688
7689 Stream: as severity0
7690
7691 Time: While system is running.
7692
7693 Meaning: Remove_cdte is trying to get rid of a channel. It
7694 cannot obtain the line state.
7695
7696 Action: No operator action is required.
7697
7698
7699 asu_.pl1
7700 asu_$suspend_process: PERSON.PROJECT CHANNEL is
7701 already suspended
7702
7703
7704 Stream: as severity 1
7705
7706 Time: asu_$suspend_process was called by one of the
7707 process termination handlers to suspend an
7708 interactive process whose terminal disconnected
7709 or to suspend an absentee process via the operator
7710 "abs suspend" command.
7711
7712 Meaning: The process is already suspended. The current
7713 request will be ignored.
7714
7715 Action: No operator action is required.
7716
7717
7718 asu_.pl1
7719 asu_: attach channel not done on CHANNEL; service
7720 type = TYPE
7721
7722
7723 Stream: as severity 0
7724
7725 Time: When attaching channels to the Answering Service.
7726
7727
7728 asu_ 134 08/03/23 MR12.7^L
7729
7730
7731 Meaning: The CHANNEL was found in an inactive state TYPE =
7732 INACTIVE or was found to be a multiplexer
7733 channel TYPE = MULTIPLEXER. It was not
7734 attached.This indicates a logic error in the
7735 supervisor or CPU or memory hardware problems.
7736
7737 Action: No operator action is required.
7738
7739
7740 asu_.pl1
7741 asu_: listen not done on CHANNEL; current service
7742 type = TYPE
7743
7744
7745 Stream: as severity 0
7746
7747 Time: When the Answering Service tried to listen to the
7748 channel.
7749
7750 Meaning: The CHANNEL was found in an inactive state TYPE =
7751 INACTIVE was found to be a multiplexer channel
7752 TYPE = MULTIPLEXER was found to be in use by
7753 the message coordinator TYPE = MC or was found
7754 to be attached for Testing and Diagnostics TYPE =
7755 TANDD_SERVICE. The attempt to listen on the
7756 channel failed.This indicates a logic error in the
7757 supervisor or CPU or memory hardware problems.
7758
7759 Action: No operator action is required.
7760
7761
7762 asu_.pl1
7763 asu_: called by PROCEDURE USER PROJ CHN is not
7764 stopped state = S even though destroy flag = D;
7765 it might not be possible to destroy this process
7766
7767
7768
7769 Stream: as severity1
7770
7771 Time: In response to an operator command to bump or log
7772 out an interactive absentee or daemon user.
7773
7774 Meaning: The process being bumped or logged out was found
7775 to be partially logged out already but not in the
7776 stopped state. An attempt will be made to destroy
7777 this process but it might fail.
7778
7779 Action: Contact the system programming staff.
7780
7781
7782 asu_.pl1
7783 asu_: called by PROCEDURE USER.PROJ CHN was
7784
7785
7786 asu_ 135 08/03/23 MR12.7^L
7787
7788
7789 already stopped and will be destroyed stopstop
7790 wakeup was lost
7791
7792
7793 Stream: as severity1
7794
7795 Time: In response to an operator command to bump or log
7796 out an interactive absentee or daemon user.
7797
7798 Meaning: The process being bumped or logged out was found
7799 to be in the stopped state partially logged out.
7800 A wakeup from ring zero indicating that the
7801 process was stopped and could be destroyed was
7802 apparently lost. Destruction of the process will
7803 be completed.
7804
7805 Action: Contact the system programming staff.
7806
7807
7808 asu_.pl1
7809 asu_: cdte CCC|XXX CHANNEL hung up
7810
7811
7812 Stream: as severity0
7813
7814 Time: While system is running.
7815
7816 Meaning: Remove_cdte is trying to get rid of a channel.
7817 The indicated CHANNEL is in the hung up state.
7818
7819 Action: No operator action is required.
7820
7821
7822 asu_.pl1
7823 asu_: cdte CCC|XXX CHANNEL state A in use B tra
7824 vec C
7825
7826
7827 Stream: as severity0
7828
7829 Time: While system is running.
7830
7831 Meaning: Remove_cdte is trying to get rid of a channel. It
7832 first logs the state of the line.
7833
7834 Action: No operator action is required.
7835
7836
7837 asu_.pl1
7838 asu_: cdtep CCC|ZZZ not cdt YYY|0
7839
7840
7841 Stream: as severity0
7842
7843
7844 asu_ 136 08/03/23 MR12.7^L
7845
7846
7847 Time: While system is running.
7848
7849 Meaning: This indicates a logic error in the supervisor or
7850 CPU or memory hardware problems. Remove_cdte is
7851 trying to get rid of a channel which is no good.
7852
7853 Action: No operator action is required.
7854
7855
7856 asu_.pl1
7857 asu_: CHANNEL cannot be attached because its
7858 service type is TYPE N.
7859
7860
7861 Stream: as severity1
7862
7863 Time: While system is running.
7864
7865 Meaning: An attach command specified a CHANNEL whose
7866 service type does not permit it to be attached.
7867 No action was taken.
7868
7869 Action: Enter a correct command.
7870
7871
7872 asu_.pl1
7873 asu_: CHANNEL has been deleted by a CDT
7874 installation and so cannot be attached.
7875
7876
7877
7878 Stream: as severity1
7879
7880 Time: While system is running.
7881
7882 Meaning: An attach command specified a CHANNEL that has
7883 been deleted. No action was taken.
7884
7885 Action: Enter a correct command.
7886
7887
7888 asu_.pl1
7889 asu_: CHANNEL has in_use = N current state = S
7890 CDTE.state was OS
7891
7892
7893 Stream: as severity 1
7894
7895 Time: When the operator attempts to attach the channel.
7896
7897 Meaning: The Channel Definition Table CDT entry for
7898 CHANNEL is in an inconsistent state. See
7899 dialup_values.incl.pl1 for a description of the
7900
7901
7902 asu_ 137 08/03/23 MR12.7^L
7903
7904
7905 in_use and state values. The old state value OS
7906 is displayed only if it differs from the current
7907 state.
7908
7909 Action: Enter a corrected command line.
7910
7911
7912 asu_.pl1
7913 asu_: CHANNEL in use as a multiplexer and cannot
7914 be attached.
7915
7916
7917 Stream: as severity 0
7918
7919 Time: When issuing an operator attach command for a
7920 channel.
7921
7922 Meaning: CHANNEL is operating as a multiplexer supporting
7923 one or more channels. It cannot be attached
7924 directly. The attach operation fails.
7925
7926 Action: Enter a corrected command line.
7927
7928
7929 asu_.pl1
7930 asu_: CHANNEL in use for T & D and cannot be
7931 attached.
7932
7933
7934 Stream: as severity1
7935
7936 Time: While system is running.
7937
7938 Meaning: An operator attach command specified a CHANNEL
7939 being tested via Test and Diagnostic routines.
7940 The channel was not attached.
7941
7942 Action: Enter a corrected command line.
7943
7944
7945 asu_.pl1
7946 asu_: CHANNEL is a multiplexer and cannot be
7947 removed.
7948
7949
7950 Stream: as severity 1
7951
7952 Time: When the operator attempts to remove a channel.
7953
7954 Meaning: CHANNEL is a multiplexer channel which handles
7955 data for one or more subchannels. Such
7956 multiplexers are not attached by the Answering
7957 Service and therefore cannot be removed.
7958
7959
7960 asu_ 138 08/03/23 MR12.7^L
7961
7962
7963 Action: Enter a corrected command line.
7964
7965 Message: asu_$bump_user: ERROR_MESSAGE.
7966 BLAST_MESSAGE. Sending blast message to
7967 PERSON.PROJECT on CHANNEL
7968
7969 Stream: as severity 0
7970
7971 Time: While system is running.
7972
7973 Meaning: An error occurred while attempting to send an
7974 operator warning message to PERSON.PROJECT on
7975 CHANNEL. ERROR_MESSAGE is the text associated
7976 with the error which occurred. BLAST_MESSAGE is
7977 the undelivered operator warning.
7978
7979 Action: No operator action is required.
7980
7981
7982 asu_.pl1
7983 asu_: CHANNEL is already attached; will try to
7984 listen to it again
7985
7986
7987 Stream: as severity 1
7988
7989 Time: When the operator attempts to attach a channel.
7990
7991 Meaning: The CHANNEL was already attached by the Answering
7992 Service but was not dialed up. The Answering
7993 Service will attempt to listen for dialups on the
7994 channel.
7995
7996 Action: Enter a corrected command line.
7997
7998
7999 asu_.pl1
8000 asu_: CHANNEL is in use by the message
8001 coordinator and cannot be attached.
8002
8003
8004 Stream: as severity1
8005
8006 Time: While system is running.
8007
8008 Meaning: An operator attach command specified a message
8009 coordinator CHANNEL. The channel was not
8010 attached.
8011
8012 Action: Enter a correct command.
8013
8014
8015 asu_.pl1
8016
8017
8018 asu_ 139 08/03/23 MR12.7^L
8019
8020
8021 asu_: CHANNEL is not in CDT and so cannot be
8022 attached
8023
8024
8025 Stream: as severity1
8026
8027 Time: While system is running.
8028
8029 Meaning: An attach command specified an unknown CHANNEL.
8030 No action was taken.
8031
8032 Action: Enter a correct command.
8033
8034
8035 asu_.pl1
8036 asu_: CHANNEL was not configured at bootload
8037 time and so cannot be attached.
8038
8039
8040
8041 Stream: as severity1
8042
8043 Time: While system is running.
8044
8045 Meaning: An attach command specified a CHANNEL that cannot
8046 be used until the next bootload. No action was
8047 taken.
8048
8049 Action: Enter a correct command.
8050
8051
8052 asu_.pl1
8053 asu_: ENTRYPOINT called with null UTE ptr.
8054
8055
8056 Stream: as severity0
8057
8058 Time: ENTRYPOINT may be suspend_process or
8059 setup_login_server_handle. suspend_process was
8060 called by one of the process termination handlers
8061 to suspend an interactive process whose terminal
8062 disconnected or to suspend an absentee process
8063 via the operator "abs suspend" command.
8064 setup_login_server_handler was called in response
8065 to a validate connect new_proc or destroy
8066 request from a login server.
8067
8068 Meaning: Programming error in the process termination
8069 handlers or the login server support of the
8070 Answering Service.
8071
8072 Action: Contact the system programming staff.
8073
8074
8075
8076 asu_ 140 08/03/23 MR12.7^L
8077
8078
8079
8080
8081 asu_.pl1
8082 asu_: ERROR_MESSAGE. ENTRY OPERATION error; will
8083 remove channel CHANNEL DESC
8084
8085
8086
8087 Stream: as severity1
8088
8089 Time: While system is running.
8090
8091 Meaning: A channel error has occurred on CHANNEL. DESC is
8092 the comment field for the channel given in its
8093 Channel Definition Table CDT entry.
8094 ERROR_MESSAGE gives the text describing the error
8095 code returned by the operation in progress.
8096 OPERATION may be create_ev_chn
8097 decl_event_call_chn listen set_term_type
8098 tty_event or tty_index dependent upon the
8099 operation in progress when the error occurred.
8100 ENTRY specifies the asu_ entrypoint that was
8101 running when the operation was performed on the
8102 channel. It may be asu_listen or attach_channel.
8103 The channel will be removed from use.
8104
8105 Action: It may be necessary to busy out the modem for the
8106 channel.
8107
8108
8109 asu_.pl1
8110 asu_: ERROR_MESSAGE. Sending initial wakeup to
8111 PROCESS_ID PERSON.PROJECT
8112
8113
8114 Stream: as severity 0
8115
8116 Time: Called at process creation to start the process
8117 running.
8118
8119 Meaning: ERROR_MESSAGE is the text of an error which
8120 occurred attempting to send a wakeup to
8121 PERSON.PROJECT. As a result of this error
8122 process creation will fail.
8123
8124 Action: No operator action is required.
8125
8126
8127 asu_.pl1
8128 asu_: ERROR_MESSAGE. Retrieving the values of
8129 R-0ffset and R-Factor for PROCESS_ID
8130 PERSON.PROJECT.
8131
8132
8133
8134 asu_ 141 08/03/23 MR12.7^L
8135
8136
8137 Stream: as severity 0
8138
8139 Time: Called at process creation.
8140
8141 Meaning: asu_$start_process called hphcs_$get_ipc_operands.
8142 This call failed with an error whose text is shown
8143 as ERROR_MESSAGE. As a result the process will
8144 not be started.
8145
8146 Action: No operator action is required.
8147
8148
8149 asu_.pl1
8150 asu_: listen failed on CHANNEL: state = N
8151
8152
8153 Stream: as severity 0
8154
8155 Time: When attempting to listen for dialups on the
8156 channel.
8157
8158 Meaning: The Channel Definition Table CDT entry for
8159 CHANNEL has an invalid state value N. Channel
8160 listening will not occur.
8161
8162 Action: No operator action is required.
8163
8164
8165 asu_.pl1
8166 asu_: listen not done on CHANNEL: IN_USE with
8167 state = STATE in_use = IN_USE tra_vec =
8168 CURRENT_OPERATION
8169
8170
8171
8172 Stream: as severity 0
8173
8174 Time: When the Answering Service tries to listen to the
8175 channel.
8176
8177 Meaning: The Channel Definition Table CDT entry for
8178 CHANNEL is in an inconsistent state. See
8179 dialup_values.incl.pl1 for a description of the
8180 state in_use and tra_vec values.
8181
8182 Action: No operator action is required.
8183
8184
8185 asu_.pl1
8186 asu_: lock was N ev call mask was M ips mask
8187 was ZZZZZZ
8188
8189
8190
8191
8192 asu_ 142 08/03/23 MR12.7^L
8193
8194
8195 Stream: as severity1
8196
8197 Time: In response to an operator reset command.
8198
8199 Meaning: N is the value of anstbl.lock_value M is the
8200 value of event call masking. ZZZZZZ was the ips
8201 mask. This message verifies that the reset
8202 command was given and what effect it had.
8203
8204 Action: No operator action is required.
8205
8206
8207 asu_.pl1
8208 asu_: MESSAGE. unable to unmask channel CHANNEL.
8209
8210
8211 Stream: as severity1
8212
8213 Time: In response to an operator command to attach a
8214 channel which had been masked by MCS.
8215
8216 Meaning: The CHANNEL could not be unmasked.
8217
8218 Action: Contact the system programming staff.
8219
8220
8221 asu_.pl1
8222 asu_: Unable to create event channel for new UTE
8223 LOCATION
8224
8225
8226 Stream: as severity 2
8227
8228 Time: While system is running.
8229
8230 Meaning: This indicates a logic error in the supervisor or
8231 CPU or memory hardware problems.
8232
8233 Action: Contact the system programming staff.
8234
8235
8236 asu_.pl1
8237 asu_: unmasking channel CHANNEL.
8238
8239
8240 Stream: as severity1
8241
8242 Time: In response to an operator command to attach a
8243 channel which has been masked by MCS.
8244
8245 Meaning: A special order is issued to MCS to unmask
8246 CHANNEL and the channel should then be available
8247 for regular use.
8248
8249
8250 asu_ 143 08/03/23 MR12.7^L
8251
8252
8253 Action: No operator action is required.
8254
8255
8256 asum_inner_ring_caller_.pl1
8257 asum_inner_ring_caller_: ASUM database found
8258 locked after return from call by GROUP_ID
8259
8260
8261
8262 Stream: BOS Typewriter.
8263
8264 Time: While system is running.
8265
8266 Meaning: This indicates a logic error in the supervisor or
8267 CPU or memory hardware problems. The AS user
8268 message facility was called and upon return from
8269 the call the transfer routine
8270 asum_inner_ring_caller_ detected that the ASUM
8271 database
8272 >sc1>user_messages>as_user_message_system was
8273 left locked. The lock has been unlocked but the
8274 database may be inconsistent. This should never
8275 happen and if it does indicates a coding error in
8276 the AS user message facility.
8277
8278 Action: Contact the system programming staff.
8279
8280
8281 operator_com_channel_cmds_.pl1
8282 attach: Action not performed. ttyXXX
8283
8284
8285 Stream: as severity1.
8286
8287 Time: In response to an operator attach command.
8288
8289 Meaning: This is the response to attach TTYxxx if no more
8290 room is available in the answer table for channel
8291 entries. The line is not attached.
8292
8293 Action: Contact the system programming staff.
8294
8295
8296 operator_com_channel_cmds_.pl1
8297 attach: bad arg "AAAA"
8298
8299
8300 Stream: as severity1.
8301
8302 Time: In response to an operator command.
8303
8304 Meaning: A bad argument was furnished with an attach
8305 command. The argument is skipped.
8306
8307
8308 attach 144 08/03/23 MR12.7^L
8309
8310
8311 Action: Enter a corrected command.
8312
8313
8314 operator_com_channel_cmds_.pl1
8315 attach: error: not done
8316
8317
8318 Stream: as severity1.
8319
8320 Time: In response to an operator command.
8321
8322 Meaning: Bad arguments were given to an attach command. No
8323 action resulted.
8324
8325 Action: Enter a corrected command line.
8326
8327
8328 operator_com_channel_cmds_.pl1
8329 attach: TTYxxx attached
8330
8331
8332 Stream: as severity1.
8333
8334 Time: In response to an operator attach command.
8335
8336 Meaning: This is the response to an attach TTYxxx command.
8337 The device channel is now connected to the
8338 Answering Service and ready for dialups.
8339
8340 Action: No operator action is required.
8341
8342
8343 terminate_proc.pl1
8344 attempt to terminate an idle process
8345
8346
8347 Stream: BOS Typewriter Crashes system
8348
8349 Time: While system is running.
8350
8351 Meaning: This indicates a logic error in the supervisor or
8352 CPU or memory hardware problems.
8353
8354 Action: Follow normal recovery procedures.
8355
8356
8357 terminate_proc.pl1
8358 attempt to terminate initializer process
8359
8360
8361 Stream: BOS Typewriter Crashes system
8362
8363 Time: While system is running.
8364
8365
8366 attempt 145 08/03/23 MR12.7^L
8367
8368
8369 Meaning: This indicates a logic error in the supervisor or
8370 CPU or memory hardware problems.
8371
8372 Action: Follow normal recovery procedures.
8373
8374
8375 terminate_proc.pl1
8376 attempt to terminate process with TYPE lock set
8377
8378
8379 Stream: BOS Typewriter Crashes system
8380
8381 Time: While system is running.
8382
8383 Meaning: This indicates a logic error in the supervisor or
8384 CPU or memory hardware problems.
8385
8386 Action: Follow normal recovery procedures.
8387
8388
8389 access_audit_util_.pl1
8390 AUDIT access_audit_util_: GRANTED modification
8391 of process audit flags ADDED_INFO
8392
8393
8394 Stream: $access_audit
8395
8396 Time: While system is running.
8397
8398 Meaning: The specified user has invoked a privileged
8399 operation to change the process audit flags. This
8400 may result in more or less audit messages for that
8401 user.
8402
8403 Action: Contact the system programming staff._ssa
8404
8405
8406 access_class_check.pl1
8407 AUDIT access_class_check: GRANTED modification
8408 of security out_of_service ADDED_INFO
8409
8410
8411 Stream: $access_audit
8412
8413 Time: While system is running.
8414
8415 Meaning: The soos switch for the specified path has been
8416 turned on or off by the security administrator as
8417 indicated.
8418
8419 Action: No operator action is required.
8420
8421
8422
8423
8424 AUDIT create_vtoce 146 08/03/23 MR12.7^L
8425
8426
8427 create_vtoce.pl1
8428 AUDIT create_vtoce: DENIED creation of file
8429 system object ADDED_INFO entry class range outside
8430 LV CLASS_RANGE lvid LVID
8431
8432
8433 Stream: $access_audit
8434
8435 Time: While system is running.
8436
8437 Meaning: The specified user attempted to create a segment
8438 whose access class is outside the range accepted
8439 by the logical volume.
8440
8441 Action: Contact the system programming staff._ssa
8442
8443
8444 fim.alm
8445 AUDIT fim: access violation fault - mode
8446 ADDED_INFO
8447
8448
8449
8450 Stream: $access_audit
8451
8452 Time: While system is running.
8453
8454 Meaning: The specified process took an access violation
8455 fault " because the access mode was inconsistant
8456 with the operation.
8457
8458 Action: No operator action is required.
8459
8460
8461 fim.alm
8462 AUDIT fim: access violation fault - ring
8463 ADDED_INFO
8464
8465
8466
8467 Stream: $access_audit
8468
8469 Time: While system is running.
8470
8471 Meaning: The specified process took an access violation
8472 fault " due to ring brackets inconsistant with the
8473 operation.
8474
8475 Action: No operator action is required.
8476
8477
8478 fim.alm
8479 AUDIT fim: illegal procedure fault ADDED_INFO
8480
8481
8482 AUDIT fim 147 08/03/23 MR12.7^L
8483
8484
8485 Stream: $access_audit
8486
8487 Time: While system is running.
8488
8489 Meaning: The specified process took an illegal procedure
8490 fault.
8491
8492 Action: No operator action is required.
8493
8494
8495 mseg_message_.pl1
8496 Audit mseg_$add_message: DENIED addition of a
8497 message to a message segment ADDED_INFO <Message
8498 segment is full.>
8499
8500
8501
8502 Stream: $access_audit
8503
8504 Time: While system is running.
8505
8506 Meaning: A message was not added to a mailbox or message
8507 segment because there is not enough room for the
8508 message in the segment. Repeated occurences of
8509 this event over a short period of time could
8510 indicate an attempt to exploit a moderate
8511 bandwidth covert channel. ADDED_INFO will
8512 identify the user and segment in question.
8513
8514 Action: Contact the system programming staff._ssa
8515
8516
8517 mseg_segment_.pl1
8518 Audit mseg_$reset_salvaged_flag_seg: GRANTED
8519 modifying message segment attributes ADDED_INFO
8520 <Message segment salvage flag reset.>
8521
8522
8523
8524 Stream: $access_audit
8525
8526 Time: While system is running.
8527
8528 Meaning: The salvaged indicator of a message segment or
8529 mailbox was reset at the user's request. Repeated
8530 occurences of this event over a short period of
8531 time could indicate an attempt to exploit a
8532 moderate bandwidth covert channel. ADDED_INFO
8533 will identify the user and segment in question.
8534
8535 Action: Contact the system programming staff._ssa
8536
8537
8538
8539
8540 Audit mseg_check_access_ 148 08/03/23 MR12.7^L
8541
8542
8543
8544
8545 mseg_check_access_.pl1
8546 Audit mseg_check_access_: GRANTED | DENIED
8547 OPERATION_DESCRIPTION ADDED_INFO
8548
8549
8550 Stream: $access_audit
8551
8552 Time: While system is running.
8553
8554 Meaning: An access control decision has been made by the
8555 mseg_ primitives. The OPERATION_DESCRIPTION
8556 specifies the operation requested by the user.
8557 GRANTED or DENIED indicates whether access was
8558 granted or not. the ADDED_INFO describes the user
8559 and the message segment or mailbox. The
8560 associated binary info describes the message in
8561 the segment if a specific message was involved.
8562
8563 Action: Contact the system programming staff._ssa
8564
8565
8566 page_error.alm
8567 AUDIT page_fault: GRANTED excessive segment
8568 state changes Moderate_cc for PROCESS_GROUP_ID
8569 AUTHORIZATION
8570
8571
8572
8573 Time: While system is running.
8574
8575 Stream: $security_log
8576
8577 Meaning: An attempt to use the modification of various
8578 segment " attributes as a covert channel was
8579 detected.
8580
8581
8582
8583 pnt_db_util_.pl1
8584 AUDIT pnt_db_util_: GRANTED addition of pnt
8585 entry Admin_op for PERSON.PROJECT.TAG AUTH
8586 Level=1 to PNT entry USERID no access class.
8587
8588
8589 Stream: $access_audit
8590
8591 Time: While system is running.
8592
8593 Meaning: The user PERSON.PROJECT.TAG added a new PNT
8594 entry for USERID
8595
8596
8597
8598 AUDIT pnt_db_util_ 149 08/03/23 MR12.7^L
8599
8600
8601 Action: No operator action is required.
8602
8603
8604 pnt_db_util_.pl1
8605 AUDIT pnt_db_util_: GRANTED deletion of pnt
8606 entry Admin_op for PERSON.PROJECT.TAG AUTH
8607 Level=1 to PNT entry USERID no access class.
8608
8609
8610 Stream: $access_audit
8611
8612 Time: While system is running.
8613
8614 Meaning: The user PERSON.PROJECT.TAG deleted the PNT entry
8615 for USERID.
8616
8617 Action: No operator action is required.
8618
8619
8620 pnt_db_util_.pl1
8621 AUDIT pnt_db_util_: GRANTED modification of pnt
8622 entry Admin_op for PERSON.PROJECT.TAG AUTH
8623 Level=1 to PNT entry USERID: CHANGES no access
8624 class.
8625
8626
8627 Stream: $access_audit
8628
8629 Time: While system is running.
8630
8631 Meaning: The user PERSON.PROJECT.TAG modified the PNT entry
8632 for USERID. CHANGES describes in brief format
8633 what security relevant changes were made. See the
8634 binary information in the audit message for
8635 further details.
8636
8637 Action: No operator action is required.
8638
8639
8640 reclassify.pl1
8641 AUDIT reclassify$ENTRY: GRANTED modification of
8642 security out-of-service ADDED_INFO
8643
8644
8645 Stream: $access_audit
8646
8647 Time: While system is running.
8648
8649 Meaning: An AIM error was found in respect to the specified
8650 directory. There was a disagreement in access
8651 class between the directory and one of it's sons
8652 or there was an upgraded directory with
8653 non-terminal quota.
8654
8655
8656 AUDIT reclassify$ENTRY 150 08/03/23 MR12.7^L
8657
8658
8659 Action: No operator action is required.
8660
8661
8662 reclassify.pl1
8663 AUDIT reclassify$ENTRY: GRANTED|DENIED
8664 modification of fs_obj access class ADDED_INFO
8665
8666
8667 Stream: $access_audit
8668
8669 Time: While system is running.
8670
8671 Meaning: Indicates whether an attempt to reclassify the
8672 specified file system object was granted or
8673 denied. In the case of reclassify$node a message
8674 will be generated for each entry in the directory
8675 being reclassified.
8676
8677 Action: No operator action is required.
8678
8679
8680 salv_check_vtoce_.pl1
8681 AUDIT salv_check_vtoce_: GRANTED modification
8682 of security out-of-service ADDED_INFO
8683
8684
8685 Stream: $access_audit
8686
8687 Time: While system is running.
8688
8689 Meaning: Security out-of-service switch was set because
8690 vtoce access class did not match the entry access
8691 class for the specified file system entry.
8692
8693 Action: Contact the system programming staff._ssa
8694
8695
8696 salv_dir_checker_.pl1
8697 AUDIT salv_dir_checker_: GRANTED modification
8698 of fs_obj access ADDED_INFO
8699
8700
8701 Stream: $access_audit
8702
8703 Time: Salvaging
8704
8705 Meaning: The salvager has truncated the ACL of a branch.
8706
8707 Action: Contact the system programming staff._ssa
8708
8709
8710 set_privileges.pl1
8711
8712
8713
8714 AUDIT set_privileges 151 08/03/23 MR12.7^L
8715
8716
8717 AUDIT set_privileges: GRANTED modification of
8718 system AIM privilege ADDED_INFO
8719
8720
8721 Stream: $access_audit
8722
8723 Time: While system is running.
8724
8725 Meaning: The specified user made a privileged call for
8726 modifying the process AIM privileges
8727
8728 Action: No operator action is required.
8729
8730
8731 set_sys_audit_thresholds_.pl1
8732 AUDIT set_sys_audit_thresholds_: GRANTED|DENIED
8733 modification of system audit flags and thresholds
8734 ADDED_INFO
8735
8736
8737 Stream: $access_audit
8738
8739 Time: While system is running.
8740
8741 Meaning: Indicates that the system wide audit enable flags
8742 and the thresholds have been changed as indicated.
8743
8744 Action: No operator action is required.
8745
8746
8747 bce_abs_seg.pl1
8748 bce_abs_seg: Too many bce abs-segs.
8749
8750
8751 Stream: BOS Typewriter Crashes system
8752
8753 Time: System Intialization.
8754
8755 Meaning: More per-bce pass abs-segs were encountered than
8756 fit in the abs-seg array. This is a software
8757 error.
8758
8759
8760
8761 bce_ioi_post.pl1
8762 bce_ioi_post: Error posting i/o completion.
8763 ioi_event_channel: CCCCCCCCCCCC ioi_message:
8764 MMMMMMMMMMMM
8765
8766
8767
8768 Stream: BOS Typewriter Crashes system
8769
8770
8771
8772 bce_ioi_post 152 08/03/23 MR12.7^L
8773
8774
8775 Time: System Intialization.
8776
8777 Meaning: No posting buffer was found in an "I/O
8778 outstanding" state for the above event channel.
8779 This indicates a logic error in the supervisor or
8780 CPU or memory hardware problems.
8781
8782 Action: Contact the system programming staff.
8783
8784
8785 bce_ioi_post.pl1
8786 bce_ioi_post: System not at correct level to post
8787 I/O completion.
8788
8789
8790 Stream: BOS Typewriter Crashes system
8791
8792 Time: System Intialization.
8793
8794 Meaning: The flag sys_info$service_system indicates that
8795 the system is up and should be posting I/O
8796 completions via pxss$io_wakeup not this program.
8797 This indicates a logic error in the supervisor or
8798 CPU or memory hardware problems.
8799
8800 Action: Contact the system programming staff.
8801
8802
8803 bce_ioi_post.pl1
8804 bce_ioi_post: Unexpected System Fault.
8805 ioi_event_channel: CCCCCCCCCCCC ioi_message:
8806 MMMMMMMMMMMM
8807
8808
8809
8810 Stream: BOS Typewriter Crashes system
8811
8812 Time: System Intialization.
8813
8814 Meaning: This indicates a logic error in the supervisor or
8815 CPU or memory hardware problems.
8816
8817 Action: Contact the system programming staff.
8818
8819
8820 bce_save.pl1
8821 bce_save: Error issuing tape connect for TAPE_DEV
8822 TAPE_SET. ERR_MESSAGE
8823
8824
8825 Stream: BOS Typewriter Crashes system
8826
8827 Time: System Intialization.
8828
8829
8830 bce_save 153 08/03/23 MR12.7^L
8831
8832
8833 Meaning: IOI has returned a non-zero error which has been
8834 expanded in ERR_MESSAGE.This indicates a logic
8835 error in the supervisor or CPU or memory hardware
8836 problems.
8837
8838 Action: Contact the system programming staff.
8839
8840
8841 bce_save.pl1
8842 bce_save: Internal bit map for PV_NAME TAPE_SET
8843 contains no in use pages.
8844
8845
8846 Stream: BOS Typewriter Crashes system
8847
8848 Time: System Intialization.
8849
8850 Meaning: The copied/packed internal version of the PV's
8851 volume bit map contains no used pages OFF
8852 bits.This indicates a logic error in the
8853 supervisor or CPU or memory hardware problems.
8854
8855 Action: Contact the system programming staff.
8856
8857
8858 bce_save.pl1
8859 bce_save: IO complete but NO status returned for
8860 TAPE_SET.
8861
8862
8863 Stream: BOS Typewriter Crashes system
8864
8865 Time: System Intialization.
8866
8867 Meaning: An I/O has been posted but there was no
8868 indication of status being returned.This indicates
8869 a logic error in the supervisor or CPU or memory
8870 hardware problems.
8871
8872 Action: Contact the system programming staff.
8873
8874
8875 bce_save.pl1
8876 bce_save: Out of disk buffers for TAPE_SET.
8877
8878
8879 Stream: BOS Typewriter Crashes system
8880
8881 Time: System Intialization.
8882
8883 Meaning: This indicates a logic error in the supervisor or
8884 CPU or memory hardware problems.
8885
8886
8887
8888 bce_save 154 08/03/23 MR12.7^L
8889
8890
8891 Action: Contact the system programming staff.
8892
8893
8894 bce_save.pl1
8895 bce_save: Out of tape buffers for TAPE_SET.
8896
8897
8898 Stream: BOS Typewriter Crashes system
8899
8900 Time: System Intialization.
8901
8902 Meaning: This indicates a logic error in the supervisor or
8903 CPU or memory hardware problems.
8904
8905 Action: Contact the system programming staff.
8906
8907
8908 bce_save_util_.pl1
8909 bce_save_util_: Out of disk buffers for TAPE_SET.
8910
8911
8912 Stream: BOS Typewriter Crashes system
8913
8914 Time: System Intialization.
8915
8916 Meaning: This indicates a logic error in the supervisor or
8917 CPU or memory hardware problems.
8918
8919 Action: Contact the system programming staff.
8920
8921
8922 wired_shutdown.pl1
8923 begin emergency shutdown part 1
8924
8925
8926 Stream: BOS Typewriter.
8927
8928 Time: Emergency shutdown
8929
8930 Meaning: The system emergency shutdown environment has been
8931 successfully established. An attempt will be made
8932 to write out all of memory and flush the paging
8933 device.
8934
8935 Action: No operator action is required.
8936
8937
8938 boot_tape_io.pl1
8939 boot_tape_io: Code CODE from absadr.
8940
8941
8942 Stream: BOS Typewriter Crashes system
8943
8944
8945
8946 boot_tape_io 155 08/03/23 MR12.7^L
8947
8948
8949 Time: System Intialization.
8950
8951 Meaning: boot_tape_io was unable to find the address of its
8952 buffer. This indicates a logic error in the
8953 supervisor or CPU or memory hardware problems.
8954
8955 Action: $boot_tape
8956
8957
8958 boot_tape_io.pl1
8959 boot_tape_io: Code CODE from io_manager$assign
8960
8961
8962 Stream: BOS Typewriter Crashes system
8963
8964 Time: System Intialization.
8965
8966 Meaning: The bootload tape reading package could not assign
8967 the bootload tape drive to itself. This indicates
8968 a logic error in the supervisor or CPU or memory
8969 hardware problems.
8970
8971 Action: $boot_tape
8972
8973
8974 boot_tape_io.pl1
8975 boot_tape_io: Unable to allocate buffer.
8976
8977
8978 Stream: BOS Typewriter Crashes system
8979
8980 Time: System Intialization.
8981
8982 Meaning: The bootload tape reading package could not
8983 allocate a wired-down buffer into which to read
8984 the bootload tape. This indicates a logic error
8985 in the supervisor or CPU or memory hardware
8986 problems.
8987
8988 Action: $boot_tape
8989
8990
8991 bootload_error.alm
8992 bootload_0: An unpaged page table overflowed for
8993 seg N.
8994
8995
8996 Stream: BOS Typewriter Crashes system
8997
8998 Time: System Intialization.
8999
9000
9001
9002
9003
9004 bootload_0 156 08/03/23 MR12.7^L
9005
9006
9007 Meaning: The size of the page table needed for "unpaged"
9008 segment N exceeded the area left for such page
9009 tables.
9010
9011 Action: The system tape was generated improperly; use
9012 another copy of the system tape.
9013
9014
9015
9016 bootload_error.alm
9017 bootload_0: Bad MST format.
9018
9019
9020 Stream: BOS Typewriter Crashes system
9021
9022 Time: System Intialization.
9023
9024 Meaning: The records on the MST tape were out of sequence.
9025
9026 Action: Try another tape.
9027
9028
9029 bootload_error.alm
9030 bootload_0: Booted tape MPC.
9031
9032
9033 Stream: BOS Typewriter.
9034
9035 Time: System Intialization.
9036
9037 Meaning: The system succeeded in booting the bootload tape
9038 mpc.
9039
9040
9041 bootload_error.alm
9042 bootload_0: Booting FWNAME IOM CHAN with FWID
9043 FWREV firmware.
9044
9045
9046 Stream: BOS Typewriter.
9047
9048 Time: System Intialization.
9049
9050 Meaning: The system is about to boot firmware into the
9051 bootload tape mpc.
9052
9053
9054
9055 bootload_error.alm
9056 bootload_0: Booting system SYSID generated
9057 CREATION_TIME
9058
9059
9060
9061
9062 bootload_0 157 08/03/23 MR12.7^L
9063
9064
9065 Stream: BOS Typewriter.
9066
9067 Time: System Intialization.
9068
9069 Meaning: This is the first message printed by Multics
9070 announcing the sysid and creation date/time of the
9071 system tape.
9072
9073
9074
9075 bootload_error.alm
9076 bootload_0: Console status WORD1 WORD2
9077
9078
9079 Stream: BOS Typewriter Crashes system
9080
9081 Time: System Intialization.
9082
9083 Meaning: An I/O error was encountered on the console.
9084 WORD1 and WORD2 are the two words of the status
9085 returned.
9086
9087 Action: Run T&D on the console.
9088
9089
9090 bootload_error.alm
9091 bootload_0: Enter boot tape MPC model:
9092
9093
9094 Stream: BOS Typewriter.
9095
9096 Time: System Intialization.
9097
9098 Meaning: This query requests the operator to identify the
9099 bootload tape mpc so that firmware may be loaded.
9100 Refer to the MOH for details.
9101
9102
9103
9104 bootload_error.alm
9105 bootload_0: Enter tape drive number for memory
9106 dump:
9107
9108
9109 Stream: BOS Typewriter.
9110
9111 Time: BOS Typewriter Crashes system
9112
9113 Meaning: An initialization failure occured when the toehold
9114 was not active. The system is requesting the
9115 number of a tape drive on the bootload tape mpc on
9116 which to write a dump of memory.
9117
9118
9119
9120 bootload_0 158 08/03/23 MR12.7^L
9121
9122
9123
9124
9125 bootload_error.alm
9126 bootload_0: Error status WORD1 WORD2 booting
9127 FWTYPE firmware.
9128
9129
9130 Stream: BOS Typewriter.
9131
9132 Time: System Intialization.
9133
9134 Meaning: An error occured when attempting to boot firmware
9135 into the bootload tape mpc. WORD1 and WORD2 are
9136 the status returned.
9137
9138 Action: Try another firmware identifier.
9139
9140
9141 bootload_error.alm
9142 bootload_0: Excessive tape errors: status WORD1
9143 WORD2.
9144
9145
9146 Stream: BOS Typewriter.
9147
9148 Time: BOS Typewriter Crashes system
9149
9150 Meaning: An excessive number of write errors occured when
9151 trying to write an early dump tape. The dump to
9152 this tape will be aborted.
9153
9154 Action: Try another tape.
9155
9156
9157 bootload_error.alm
9158 bootload_0: External symbol not found: SEG$ENTRY
9159
9160
9161 Stream: BOS Typewriter.
9162
9163 Time: System Intialization.
9164
9165 Meaning: The entrypoint ENTRY was not found within the
9166 existant segment SEG during pre-linking of
9167 collection 1. This may indicate that the system
9168 tape was generated improperly.
9169
9170
9171
9172 bootload_error.alm
9173 bootload_0: Improper text/link/def sequence.
9174
9175
9176
9177
9178 bootload_0 159 08/03/23 MR12.7^L
9179
9180
9181 Stream: BOS Typewriter Crashes system
9182
9183 Time: System Intialization.
9184
9185 Meaning: Text linkage or definitions appeared out of
9186 proper sequence " on the Multics system tape.
9187
9188 Action: The system tape was generated improperly; use
9189 another copy " of the system tape.
9190
9191
9192
9193 bootload_error.alm
9194 bootload_0: Out of main memory.
9195
9196
9197 Stream: BOS Typewriter Crashes system
9198
9199 Time: System Intialization.
9200
9201 Meaning: Not enough main memory is configured in order to
9202 load " collection 1.
9203
9204 Action: Configure more main memory and boot again.
9205
9206
9207 bootload_error.alm
9208 bootload_0: Shutdown
9209
9210
9211 Stream: BOS Typewriter Crashes system
9212
9213 Time: System Intialization.
9214
9215 Meaning: The operator answered "shut" when asked for the
9216 bootload tape mpc information.
9217
9218 Action: $reboot
9219
9220
9221 bootload_error.alm
9222 bootload_0: Tape read error: WORD1 WORD2
9223
9224
9225 Stream: BOS Typewriter Crashes system
9226
9227 Time: System Intialization.
9228
9229 Meaning: An I/O error was encountered when reading the MST
9230 tape. WORD1 and WORD2 are the two words of the
9231 status returned.
9232
9233 Action: $reboot
9234
9235
9236 bootload_0 160 08/03/23 MR12.7^L
9237
9238
9239
9240
9241 bootload_error.alm
9242 bootload_0: Too many supervisor segments.
9243
9244
9245 Stream: BOS Typewriter Crashes system
9246
9247 Time: System Intialization.
9248
9249 Meaning: More than 256 supervisor segments were declared on
9250 the MST.
9251
9252 Action: The system tape was generated improperly; use
9253 another copy of the system tape.
9254
9255
9256
9257 bootload_error.alm
9258 bootload_0: Unexpected control word on tape
9259 CONTROL_WORD.
9260
9261
9262 Stream: BOS Typewriter Crashes system
9263
9264 Time: System Intialization.
9265
9266 Meaning: An unexpected Multics system tape control word was
9267 encountered.
9268
9269 Action: The system tape was generated improperly; use
9270 another copy of the system tape.
9271
9272
9273
9274 bootload_error.alm
9275 bootload_0: Unknown tape MPC model NAME.
9276
9277
9278 Stream: BOS Typewriter.
9279
9280 Time: System Intialization.
9281
9282 Meaning: The operator entered an unrecognizable mpc
9283 identifier.
9284
9285 Action: Try another mpc identifier.
9286
9287
9288 bootload_disk_post.pl1
9289 bootload_disk_post: Attempt to post non-requested
9290 i/o completion.
9291
9292
9293
9294 bootload_disk_post 161 08/03/23 MR12.7^L
9295
9296
9297 Stream: BOS Typewriter Crashes system
9298
9299 Time: System Intialization.
9300
9301 Meaning: disk_control detected an i/o completion that
9302 Bootload Multics does not believe it requested.
9303
9304 Action: Reboot.
9305
9306
9307 boundfault.pl1
9308 boundfault: activating into father XXX|YYY
9309
9310
9311 Stream: BOS Typewriter Crashes system
9312
9313 Time: While system is running.
9314
9315 Meaning: While activating a segment the parent directory
9316 for the segment became deactivated. This
9317 indicates a logic error in the supervisor or CPU
9318 or memory hardware problems.
9319
9320 Action: Follow normal recovery procedures.
9321
9322
9323 boundfault.pl1
9324 boundfault: on the root
9325
9326
9327 Stream: BOS Typewriter Terminates user process
9328
9329 Time: While system is running.
9330
9331 Meaning: A boundfault on the root directory has been
9332 encountered. This indicates a logic error in the
9333 supervisor or CPU or memory hardware problems.
9334
9335 Action: Contact the system programming staff.
9336
9337
9338 cache_tester.pl1
9339 cache_tester: cache parity error detected on CPU
9340 <TAG> bit failures at level W column XXX in
9341 cache: YYYYYYYYYYYYYYYYYYYYYYYY in memory:
9342 ZZZZZZZZZZZZZZZZZZZZZZZZ.
9343
9344
9345
9346 Stream: BOS Typewriter.
9347
9348 Time: While system is running.
9349
9350
9351
9352 cache_tester 162 08/03/23 MR12.7^L
9353
9354
9355 Meaning: This message is the result of a multiple bit cache
9356 failure detected and cache data and its
9357 corresponding memory data captured by the fim. It
9358 should be noted that when a cache parity error is
9359 detected by the fim there is a window of time
9360 before the address in cache and in main store can
9361 be determined. Although the cache error data is
9362 frozen cache is turned off unconditionaly when
9363 the parity retry of the fim is called the
9364 corresponding address in main store might have
9365 been changed through paging migration from other
9366 processors. This message then might not be a
9367 multiple error but rather the result of this
9368 window condition. If this message was the only
9369 diagnostic displayed i.e. the static test found
9370 no errors the cache will be turned back on. The
9371 values of W XXX YYY...Y and ZZZ...Z are as
9372 explained above.
9373
9374 Action: Contact Field Engineering
9375
9376
9377 cache_tester.pl1
9378 cache_tester: cache parity error detected on CPU
9379 <TAG> at: board XXXX chip YY.
9380
9381
9382
9383 Stream: BOS Typewriter.
9384
9385 Time: While system is running.
9386
9387 Meaning: This message is the result of a single bit cache
9388 failure detected and cache data and its
9389 corresponding memory data captured by the fim.
9390 This message will be displayed if the diagnostic
9391 error data from the fim is valid. The board and
9392 chip callout are as explained above.
9393
9394 Action: Contact field Engineering.
9395
9396
9397 cache_tester.pl1
9398 cache_tester: cache parity error detected on CPU
9399 <TAG> cache data is equal to the memory data.
9400 parity generation problem for level <L>.
9401
9402
9403
9404 Stream: BOS Typewriter.
9405
9406 Time: While system is running.
9407
9408
9409
9410 cache_tester 163 08/03/23 MR12.7^L
9411
9412
9413 Meaning: This message is the result of a cache failure
9414 detected and cache data and its corresponding
9415 memory data captured by the fim. This message
9416 will be displayed if the diagnostic error data
9417 from the fim is valid.
9418
9419 Action: Contact field Engineering.
9420
9421
9422 cache_tester.pl1
9423 cache_tester: Entire cache memory for CPU <TAG>
9424 has been disabled.
9425
9426
9427 Stream: BOS Typewriter sounds beeper
9428
9429 Time: While system is running.
9430
9431 Meaning: The static test of cache memory for CPU <TAG>
9432 detected repeatable errors in both halfs of cache.
9433 or one half of cache had previously been disabled
9434 and the static test of the other half detected
9435 repeatable errors.
9436
9437 Action: Contact field Engineering
9438
9439
9440 cache_tester.pl1
9441 cache_tester: LLUU cache memory csh<n> for CPU
9442 <TAG> has been turned off OTHER was AA and has not
9443 been changed.
9444
9445
9446
9447 Stream: BOS Typewriter sounds beeper
9448
9449 Time: While system is running.
9450
9451 Meaning: Either the lower half LLUU = Lower <n> = 1 or
9452 the upper half LLUU = Upper <n> = 2 of cache
9453 memory for CPU <TAG> has been turned off as the
9454 result of the static cache test finding a
9455 repeatable cache failure. The OTHER Upper or
9456 Lower was in state AA. If AA is off this half of
9457 cache was not tested. If AA is on this half of
9458 cache had no errors.
9459
9460 Action: Contact Field Engineering
9461
9462
9463 cache_tester.pl1
9464 cache_tester: No errors found in cache memory for
9465 CPU <TAG> cache will remain on.
9466
9467
9468 cache_tester 164 08/03/23 MR12.7^L
9469
9470
9471 Stream: BOS Typewriter.
9472
9473 Time: While system is running.
9474
9475 Meaning: The static test of cache memory for CPU <TAG>
9476 found no errors and no cache error information was
9477 captured by the fim.
9478
9479 Action: cache is turned back on
9480
9481
9482 cache_tester.pl1
9483 cache_tester: repeatable cache parity error
9484 detected on CPU <TAG> cache data is equal to the
9485 memory data. parity generation problem for level
9486 <L>.
9487
9488
9489
9490 Stream: BOS Typewriter.
9491
9492 Time: While system is running.
9493
9494 Meaning: The static test of cache memory for CPU <TAG>
9495 detected a cache failure but the data and its
9496 corresponding memory data are equal.
9497
9498 Action: Contact field Engineering.
9499
9500
9501 cache_tester.pl1
9502 cache_tester: repeatable cache parity errors
9503 detected on CPU <TAG> bit failures at level W
9504 column XXX in cache: YYYYYYYYYYYYYYYYYYYYYYYY in
9505 memory: ZZZZZZZZZZZZZZZZZZZZZZZZ.
9506
9507
9508
9509 Stream: BOS Typewriter.
9510
9511 Time: While system is running.
9512
9513 Meaning: The static test of cache memory for CPU <TAG>
9514 indicated a multiple bit error between the
9515 contents of cache and the contents of the wired
9516 test buffer. The multiple bit failure is further
9517 broken down to the failing cache level W 0 - 3
9518 and column XXX address. The data read from
9519 cache YYY...Y and the expected data ZZZ...Z is
9520 displayed as an aid for the field engineer. Since
9521 the failure happened during the static test of
9522 cache it is assumed to be a solid failure and
9523 that segment of cache memory csh1 or csh2 is
9524
9525
9526 cache_tester 165 08/03/23 MR12.7^L
9527
9528
9529 turned off. There could be up to 3 multiple
9530 messages or some combination of multiple bit error
9531 messages and board and chip callouts since
9532 diagnostic data for the first 3 cache errors is
9533 captured.
9534
9535 Action: Contact Field Engineering personnel.
9536
9537
9538 cache_tester.pl1
9539 cache_tester: repeatable cache parity errors
9540 detected on CPU <TAG> at: board XXXX chip YY.
9541
9542
9543
9544 Stream: BOS Typewriter.
9545
9546 Time: While system is running.
9547
9548 Meaning: The static test of cache memory for CPU <TAG>
9549 indicated a single bit error between the contents
9550 of cache and the contents of the wired test
9551 buffer. The single bit failure is further broken
9552 down to the failing wire wrapped board board
9553 XXXX and integrated circuit chip chip YY that
9554 failed. Since it happened during the static test
9555 of cache it is assumed to be a solid failure and
9556 that segment of cache memory csh1 or csh2 is
9557 turned off. There could be up to 3 board and chip
9558 callouts since diagnostic data for the first 3
9559 cache errors is captured. These additional board
9560 and chip callouts will only be displayed if the
9561 single bit failure was a different bit or
9562 different cache level than the board and chip
9563 diagnostic already displayed.
9564
9565 Action: Contact Field Engineering personnel.
9566
9567
9568 cache_tester.pl1
9569 cache_tester: Unable to allocate wired buffer.
9570
9571
9572 Stream: BOS Typewriter.
9573
9574 Time: While system is running.
9575
9576 Meaning: Attempted to allocate wired contiguous buffer for
9577 cache testing and pc_contig could not find enough
9578 pages available.
9579
9580
9581
9582
9583
9584 cache_tester 166 08/03/23 MR12.7^L
9585
9586
9587 Action: If cache error information was captured in the fim
9588 this information is displayed. Cache memory is
9589 turned back on.
9590
9591
9592
9593 cache_tester.pl1
9594 cache_tester: Unable to run on CPU <TAG> to EEDD
9595 cache ERRORMESSAGE.
9596
9597
9598 Stream: BOS Typewriter sounds beeper
9599
9600 Time: While system is running.
9601
9602 Meaning: The attempt to run on CPU <TAG> to either enable
9603 EEDD - enable or disable EEDD = disable cache
9604 memory failed.
9605
9606 Action: CPU <TAG> should be taken offline if the attempt
9607 was to disable cache memory.
9608
9609
9610
9611 cache_tester.pl1
9612 cache_tester: Unable to set CPU required to <TAG>
9613 cache is off ERRORMESSAGE.
9614
9615
9616 Stream: BOS Typewriter.
9617
9618 Time: While system is running.
9619
9620 Meaning: Attempted to run on CPU <TAG> for cache testing
9621 and could not set CPU required to that CPU.
9622
9623 Action: Cache memory is turned back on.
9624
9625
9626 call_bce.pl1
9627 call_bce: bce called from Multics.
9628
9629
9630 Stream: BOS Typewriter.
9631
9632 Time: While system is running.
9633
9634 Meaning: An outer ring program has called hphcs_$call_bce.
9635 This is usually done after printing an explanatory
9636 message. The system will resume operation if
9637 continue is typed.
9638
9639 Action: Follow normal recovery procedures.
9640
9641
9642 Cannot 167 08/03/23 MR12.7^L
9643
9644
9645
9646
9647 disk_rebuild_caller.pl1
9648 Cannot shrink VTOC from XX to YY VTOCEs.
9649 Respecify parameters.
9650
9651
9652 Stream: Initializer process output.
9653
9654 Time: In response to an operator command.
9655
9656 Meaning: An attempt has been made to shrink the VTOC which
9657 is illegal.
9658
9659 Action: Respecify the parameters.
9660
9661
9662 mc_tty_.pl1
9663 Channel CHANNEL_NAME attached by Message
9664 Coordinator.
9665
9666
9667 Stream: Initializer terminal.
9668
9669 Time: While system is running.
9670
9671 Meaning: The terminal has been attached by the message
9672 coordinator in response to an accept or substty
9673 command.
9674
9675 Action: Proceed to use the terminal.
9676
9677
9678 channel_manager.pl1
9679 channel_manager: Cleanup while processing
9680 interrupt for devx N.
9681
9682
9683 Stream: BOS Typewriter Crashes system
9684
9685 Time: While system is running.
9686
9687 Meaning: The cleanup condition was signalled while
9688 processing an interrupt for the channel with devx
9689 N.
9690
9691 Action: Contact the system programming staff.
9692
9693
9694 channel_manager.pl1
9695 channel_manager: Error while processing interrupt
9696 for devx N. REASON
9697
9698
9699
9700 channel_manager 168 08/03/23 MR12.7^L
9701
9702
9703 Stream: BOS Typewriter Crashes system
9704
9705 Time: While system is running.
9706
9707 Meaning: An error occurred while processing an interrupt
9708 for the channel with devx N. The specific kind of
9709 error is explained by REASON.
9710
9711
9712
9713 dn355_boot_interrupt.pl1
9714 checksum error in core image for FNP X
9715
9716
9717 Stream: BOS Typewriter.
9718
9719 Time: When bootloading an FNP
9720
9721 Meaning: The core image received for loading in the FNP had
9722 a checksum error.
9723
9724 Action: Try to load the FNP again. If the error recurs
9725 either the DIA hardware is failing or the core
9726 image in the Multics hierarchy is damaged. In the
9727 latter case the core image must be rebound.
9728
9729
9730
9731 system_startup_.pl1
9732 Command:
9733
9734
9735 Stream: BOS Typewriter.
9736
9737 Time: System Intialization.
9738
9739 Meaning: The Initializer types this message whenever it is
9740 waiting for a ring 1 command.
9741
9742 Action: Type the desired command. The normal command to
9743 type when bringing the system up is startup.
9744
9745
9746
9747 config_.pl1
9748 config_$find_table: TBLS card specifies no value
9749 for NAME.
9750
9751
9752 Stream: BOS Typewriter sounds beeper
9753
9754 Meaning: The config deck does not specify a value for NAME.
9755
9756
9757
9758 config_$find_table 169 08/03/23 MR12.7^L
9759
9760
9761 Action: One should be added. Message: config_$ENTRY:
9762 the config deck is full.
9763
9764 Stream: BOS Typewriter Crashes system
9765
9766 Meaning: No space remained in the config deck for
9767 additional cards.
9768
9769 Action: If this recurs try another boot tape. Remove
9770 unneccessary config cards.
9771
9772
9773
9774 dn355_boot_interrupt.pl1
9775 configuration error reported by bootloading
9776 program for FNP X
9777
9778
9779 Stream: BOS Typewriter.
9780
9781 Time: When bootloading an FNP
9782
9783 Meaning: The FNP bootload program gicb found an
9784 inconsistency in the FNP configuration.
9785
9786 Action: Contact the system programming staff.
9787
9788
9789 dn355_boot_interrupt.pl1
9790 configuration error reported by FNP X: DETAILS
9791
9792
9793 Stream: BOS Typewriter.
9794
9795 Time: When bootloading an FNP
9796
9797 Meaning: The FNP initialization program detected an error
9798 or inconsistency in the FNP configuration.
9799 DETAILS is a more specific description of the
9800 error.
9801
9802 Action: If possible correct the error either by updating
9803 the CDT to reflect the actual configuration or
9804 recabling the FNP. If the error cannot be
9805 corrected or is not understood inform the systems
9806 programming staff.
9807
9808
9809
9810 configure_test_cpu.pl1
9811 configure_test_cpu: Unable to run on CPU X
9812 ERRORMESSAGE
9813
9814
9815
9816 configure_test_cpu 170 08/03/23 MR12.7^L
9817
9818
9819 Stream: BOS Typewriter Crashes system
9820
9821 Time: When ISOLTS is terminating
9822
9823 Meaning: The system is attempting to restore the ISOLTS CPU
9824 to service. In attempting to reassign its
9825 interrupt mask it was unable to run on that CPU.
9826 This indicates hardware or software malfunction.
9827
9828 Action: Follow normal recovery procedures.
9829
9830
9831 disk_table_.pl1
9832 continuing demount of lv LVNAME
9833
9834
9835 Stream: Initializer process output.
9836
9837 Time: While system is running. The operator issued a
9838 dlv command for a logical volume for which a
9839 previous dlv command failed.
9840
9841 Action: No operator action is required.
9842
9843
9844 copy_fdump.pl1
9845 copy_fdump: Copied fdump image of erf NNN
9846 MM/DD/YY HHMM.M for USERNAME
9847
9848
9849 Stream: BOS Typewriter.
9850
9851 Time: While system is running.
9852
9853 Meaning: The user identified by USERNAME has successfully
9854 copied the FDUMP image for the specified ERF out
9855 of the DUMP partition. The time the FDUMP was
9856 taken is also included in the message. This
9857 message is informational only and is intended
9858 only as an aid in tracking system progress by
9859 perusing the syserr log.
9860
9861 Action: No operator action is required.
9862
9863
9864 copy_fdump.pl1
9865 copy_fdump: unexpected NAME signal.
9866
9867
9868 Stream: BOS Typewriter.
9869
9870 Time: While system is running.
9871
9872
9873
9874 copy_fdump 171 08/03/23 MR12.7^L
9875
9876
9877 Meaning: An attempt to copy the dump from the DUMP
9878 partition with copy_fdump resulted in an unclaimed
9879 signal. This may be due to damage to the DUMP
9880 partition contents a malfunction of the BCE dump
9881 command a supervisor error or a simple
9882 difficulty like running out of space in >dumps.
9883 The system continues operation. The copied dump
9884 may be only partly valid.
9885
9886 Action: Contact the system programming staff.
9887
9888
9889 correct_qused.pl1
9890 correct_qused: hash error
9891
9892
9893 Stream: BOS Typewriter Crashes system
9894
9895 Time: While system is running.
9896
9897 Meaning: Multiple entries within a directory undergoing
9898 quota correction have the same UID.
9899
9900
9901
9902 cpg_.pl1
9903 cpg_: Error: CONDITION attempting to create
9904 process for NAME.PROJ
9905
9906
9907 Stream: as severity1
9908
9909 Time: While system is running.
9910
9911 Meaning: A supervisor error prevented creation of a process
9912 for the user NAME.PROJ. An Answering Service dump
9913 was performed and the user was logged out if
9914 possible.
9915
9916 Action: Note for system programmer action. If this
9917 message is printed at every login it is probably
9918 wise to shut the system down and perform a
9919 bootload operation.
9920
9921
9922
9923 cpg_.pl1
9924 cpg_: ERROR_MESSAGE. Assigning pdir volume for
9925 USER
9926
9927
9928 Stream: as severity2
9929
9930
9931
9932 cpg_ 172 08/03/23 MR12.7^L
9933
9934
9935 Time: While system is running.
9936
9937 Meaning: The system was unable to assign a logical volume
9938 on which to place the process directory of a user.
9939 The user might not be able to log in
9940
9941 Action: Contact the system programming staff.
9942
9943
9944 cpg_.pl1
9945 cpg_: ERROR_MESSAGE. Cannot truncate pit_temp_
9946
9947
9948 Stream: as severity2
9949
9950 Time: While system is running.
9951
9952 Meaning: The system was unable to clear its temporary
9953 segment while attempting to log in a user. The
9954 user will be unable to log in.
9955
9956 Action: Contact the system programming staff.
9957
9958
9959 tc_init.pl1
9960 CPU CPUTAG: Model #: MODEL; Serial #: SERIAL;
9961 Ship date: YYMMDD.
9962
9963
9964 Stream: BOS Typewriter.
9965
9966 Time: When the bootload CPU is a DPS8 whose tag is
9967 CPUTAG is "added" to the system.
9968
9969 Meaning: The MODEL SERIAL and YY/MM/DD information is read
9970 from the DPS8 cpu's ID PROM. It is intended to be
9971 used as historical information for identifing
9972 CPUs regardless of what their current tag is
9973 assigned as.
9974
9975 Action: No operator action is required.
9976
9977
9978 tc_init.pl1
9979 CPU CPUTAG: Model #: MODEL; Serial #: SERIAL;
9980 Ship date: YYMMDD; PROM Layout Version: LAYOUT;
9981 Simulator Release: VERSION; Build Number: BUILD;
9982 Build Arch: BARCH; Build OS: BOS; Target Arch:
9983 TARCH; Target OS: TOS.
9984
9985
9986
9987 Stream: BOS Typewriter.
9988
9989
9990 CPU CPUTAG 173 08/03/23 MR12.7^L
9991
9992
9993 Time: When the bootload CPU is a DPS8 whose tag is
9994 CPUTAG is "added" to the system.
9995
9996 Meaning: The MODEL SERIAL YYMMDD LAYOUT VERSION BUILD
9997 BARCH BOS TARCH and TOS information is read
9998 from the DPS8 cpu's ID PROM. It is intended to be
9999 used as historical information for identifing
10000 CPUs regardless of what their current tag is
10001 assigned as. The LAYOUT VERSION BUILD BARCH
10002 BOS TARCH and TOS fields are only found in DPS8
10003 PROMs of the DPS8M simulator.
10004
10005 Action: No operator action is required.
10006
10007
10008 obs_reconfigure.pl1
10009 CPU X is now running.
10010
10011
10012 Stream: Initializer process output.
10013
10014 Time: In response to an operator command.
10015
10016 Meaning: This is the response to a successful addcpu X
10017 command.
10018
10019 Action: No operator action is required.
10020
10021
10022 create_homedir_.pl1
10023 create_homedir_: Bad syntax in pathname. DIRNAME
10024 NAME.PROJ
10025
10026
10027 Stream: as severity0.
10028
10029 Time: While system is running.
10030
10031 Meaning: Typically caused by a homedir specification
10032 starting with other than >user_dir_dir or >udd.
10033 It may also occur while attempting to create the
10034 home directory for the user with name NAME and
10035 project PROJ.
10036
10037 Action: Note for system programmer action._sa
10038
10039
10040 bound_as_install_ctl_.s.archiv.1
10041 create_homedir_: Bad syntax in pathname. DIRNAME
10042 NAME.PROJ
10043
10044
10045 Stream: as severity0.
10046
10047
10048 create_homedir_ 174 08/03/23 MR12.7^L
10049
10050
10051 Time: While system is running.
10052
10053 Meaning: Typically caused by a homedir specification
10054 starting with other than >user_dir_dir or >udd.
10055 It may also occur while attempting to create the
10056 home directory for the user with name NAME and
10057 project PROJ.
10058
10059 Action: Note for system programmer action._sa
10060
10061
10062 create_homedir_.pl1
10063 create_homedir_: creating "DIRNAME" for "USERID"
10064
10065
10066 Stream: as severity0.
10067
10068 Time: While system is running.
10069
10070 Meaning: The user USERID did not have a home directory. It
10071 was created for him during login or when his
10072 project's PDT was installed. This is reasonable
10073 if this is the first time he has logged in.
10074 However his directory may have been destroyed by
10075 the Salvager in which case you have to retrieve
10076 his files.
10077
10078 Action: A retrieval of the user's directory may be
10079 necessary.
10080
10081
10082 bound_as_install_ctl_.s.archiv.1
10083 create_homedir_: creating "DIRNAME" for "USERID"
10084
10085
10086 Stream: as severity0.
10087
10088 Time: While system is running.
10089
10090 Meaning: The user USERID did not have a home directory. It
10091 was created for him during login or when his
10092 project's PDT was installed. This is reasonable
10093 if this is the first time he has logged in.
10094 However his directory may have been destroyed by
10095 the Salvager in which case you have to retrieve
10096 his files.
10097
10098 Action: A retrieval of the user's directory may be
10099 necessary.
10100
10101
10102 create_homedir_.pl1
10103
10104
10105
10106 create_homedir_ 175 08/03/23 MR12.7^L
10107
10108
10109 create_homedir_: ERROR_MESSAGE. DIRNAME
10110 NAME.PROJ
10111
10112
10113 Stream: as severity0.
10114
10115 Time: While system is running.
10116
10117 Meaning: An error occurred while attempting to create the
10118 home directory for the user with name NAME and
10119 project PROJ.
10120
10121 Action: Note for system programmer action._sa
10122
10123
10124 bound_as_install_ctl_.s.archiv.1
10125 create_homedir_: ERROR_MESSAGE. DIRNAME
10126 NAME.PROJ
10127
10128
10129 Stream: as severity0.
10130
10131 Time: While system is running.
10132
10133 Meaning: An error occurred while attempting to create the
10134 home directory for the user with name NAME and
10135 project PROJ.
10136
10137 Action: Note for system programmer action._sa
10138
10139
10140 create_root_dir.pl1
10141 create_root_dir: allocating hash table
10142 ERROR_MESSAGE
10143
10144
10145 Stream: BOS Typewriter Crashes system
10146
10147 Time: Cold boot of Multics hierarchy.
10148
10149 Meaning: This indicates a logic error in the supervisor or
10150 CPU or memory hardware problems. An error has
10151 occurred allocating the hash table for the root
10152 directory.
10153
10154 Action: Reboot with a different version of the system.
10155
10156
10157 create_root_dir.pl1
10158 create_root_dir: lock error on PPP
10159
10160
10161 Stream: BOS Typewriter Crashes system
10162
10163
10164 create_root_dir 176 08/03/23 MR12.7^L
10165
10166
10167 Time: System Intialization.
10168
10169 Meaning: The supervisor was unable to lock the root. This
10170 indicates a logic error in the supervisor or CPU
10171 or memory hardware problems.
10172
10173 Action: Follow normal recovery procedures. $boot_tape
10174
10175
10176
10177 create_root_vtoce.pl1
10178 create_root_vtoce: Cannot alloc-write root vtoce
10179 ERROR_MESSAGE
10180
10181
10182 Stream: BOS Typewriter Crashes system
10183
10184 Time: Cold boot of Multics hierarchy.
10185
10186 Meaning: The system is unable to write out the VTOC entry
10187 for the root directory.
10188
10189 Action: Correct the disk problem if one exists and reboot.
10190 Otherwise reboot with a different version of the
10191 system.
10192
10193
10194
10195 create_root_vtoce.pl1
10196 create_root_vtoce: Cannot set dmpr bit map for
10197 root ERROR_MESSAGE
10198
10199
10200 Stream: BOS Typewriter.
10201
10202 Time: Cold boot of Multics hierarchy.
10203
10204 Meaning: This indicates a logic error in the supervisor or
10205 CPU or memory hardware problems.
10206
10207 Action: Contact the system programming staff.
10208
10209 Message: create_root_vtoce: Cannot set
10210 root_vtocx in RPV label.
10211
10212 Stream: BOS Typewriter Crashes system
10213
10214 Time: Cold boot of Multics hierarchy.
10215
10216 Meaning: The system is unable to update the RPV label for
10217 the root directory.
10218
10219
10220
10221
10222 create_root_vtoce 177 08/03/23 MR12.7^L
10223
10224
10225 Action: Correct the disk problem if one exists and reboot.
10226 Otherwise reboot with a different version of the
10227 system.
10228
10229 Message: create_root_vtoce: Root vtoce not
10230 allocated at 0 RPV not initialized.
10231
10232 Stream: BOS Typewriter Crashes system
10233
10234 Time: Cold boot of Multics hierarchy.
10235
10236 Meaning: A boot -cold was attempted without init_vol for
10237 RPV.
10238
10239 Action: Reboot system answering the find_rpv_subsystem
10240 with cold instead of rpv.
10241
10242
10243 create_rpv_partition.pl1
10244 create_rpv_partition: Error accessing record NNN.
10245
10246
10247 Stream: BOS Typewriter Crashes system
10248
10249 Time: System Intialization.
10250
10251 Meaning: An i/o error occured when accessing record NNN of
10252 the rpv while attempting to add a new partition.
10253
10254 Action: Try again. IF the error persists the rpv will
10255 need to be rebuilt.
10256
10257
10258 create_rpv_partition.pl1
10259 create_rpv_partition: No room in partition map
10260 for NAME.
10261
10262
10263 Stream: BOS Typewriter Crashes system
10264
10265 Time: System Intialization.
10266
10267 Meaning: The partition map of the rpv was full. The
10268 partition could not be added.
10269
10270 Action: The rpv will need to be rebuilt.
10271
10272
10273 create_rpv_partition.pl1
10274 create_rpv_partition: Out of disk.
10275
10276
10277 Stream: BOS Typewriter Crashes system
10278
10279
10280 create_rpv_partition 178 08/03/23 MR12.7^L
10281
10282
10283 Time: System Intialization.
10284
10285 Meaning: Not enough free space existed on the rpv to add
10286 the new partition.
10287
10288 Action: The rlv will have to be rebuilt.
10289
10290
10291 create_rpv_partition.pl1
10292 create_rpv_partition: Paging region ends past
10293 start of high partitions.
10294
10295
10296 Stream: BOS Typewriter Crashes system
10297
10298 Time: System Intialization.
10299
10300 Meaning: An inconsistency was found in the partition map
10301 when adding a new partition to the rpv.
10302
10303 Action: The rpv will need to be rebuilt.
10304
10305
10306 create_rpv_partition.pl1
10307 create_rpv_partition: Paging region starts below
10308 end of low partitions.
10309
10310
10311 Stream: BOS Typewriter Crashes system
10312
10313 Time: System Intialization.
10314
10315 Meaning: An inconsistency was found in the partition map
10316 when adding a new partition to the rpv.
10317
10318 Action: The rpv will need to be rebuilt.
10319
10320
10321 create_rpv_partition.pl1
10322 create_rpv_partition: vtoce NNN's file map is
10323 damaged. Volume will need salvaging.
10324
10325
10326 Stream: BOS Typewriter Crashes system
10327
10328 Time: System Intialization.
10329
10330 Meaning: The vtoce named was found to be damaged when
10331 adding a new partition to the rpv.
10332
10333 Action: Salvage the rpv using a boot of the previous
10334 release.
10335
10336
10337
10338 daemon_user_manager_ 179 08/03/23 MR12.7^L
10339
10340
10341
10342
10343 daemon_user_manager_.pl1
10344 daemon_user_manager_: Command sent to
10345 daemon_user_manager_ before it was initialized
10346
10347
10348 Stream: as severity1
10349
10350 Time: In response to an operator command.
10351
10352 Meaning: This message indicates an error in the Answering
10353 Service or an incorrect installation. No daemon
10354 users can log in.
10355
10356 Action: Contact the system programming staff.
10357
10358
10359 daemon_user_manager_.pl1
10360 daemon_user_manager_: Daemon init error. NAME
10361 PROJ SOURCE REASON
10362
10363
10364 Stream: as severity2
10365
10366 Time: In response to an operator command.
10367
10368 Meaning: The daemon user NAME PROJ on SOURCE was logged in
10369 correctly but his process could not be started.
10370 The daemon will be logged out.
10371
10372 Action: Contact the system programming staff.
10373
10374
10375 daemon_user_manager_.pl1
10376 daemon_user_manager_: Daemon will be logged out.
10377
10378
10379 Stream: as severity1
10380
10381 Time: While system is running.
10382
10383 Meaning: An error in a daemon process has caused it to
10384 terminate. The daemon suffered a fatal process
10385 error during initialization or it has set the
10386 option which causes it to be logged out when a
10387 fatal process error occurs.
10388
10389 Action: Attempt to log in the daemon again and proceed.
10390
10391
10392 daemon_user_manager_.pl1
10393
10394
10395
10396 daemon_user_manager_ 180 08/03/23 MR12.7^L
10397
10398
10399 daemon_user_manager_: Error: CONDITION during OP
10400 for NAME.PROJ SOURCE
10401
10402
10403 Stream: as severity2
10404
10405 Time: While system is running.
10406
10407 Meaning: An unexpected fault has occurred while the daemon
10408 user manager was performing an operation of type
10409 OP for the named daemon process. An Answering
10410 Service dump was performed and the system attempts
10411 to continue but the daemon process may be in an
10412 unusable state.
10413
10414 Action: Contact the system programming staff.
10415
10416
10417 daemon_user_manager_.pl1
10418 daemon_user_manager_: ERROR_MESSAGE. Logout not
10419 permitted for message coordinator source SOURCE.
10420
10421
10422 Stream: as severity1
10423
10424 Time: In response to an operator command.
10425
10426 Meaning: The message coordinator access control segment
10427 >system_control_1>mc_acs>SOURCE.mcacs does not
10428 permit the operator to logout the daemon.
10429 Therefore the operator cannot logout the daemon.
10430
10431 Action: Contact the system programming staff._sa
10432
10433
10434 daemon_user_manager_.pl1
10435 daemon_user_manager_: ERROR_MESSAGE. NAME.PROJ
10436 SOURCE terminated.
10437
10438
10439 Stream: as severity1
10440
10441 Time: While system is running.
10442
10443 Meaning: An error in a daemon process has caused it to
10444 terminate. A following message will indicate
10445 whether a new process has been automatically
10446 created.
10447
10448 Action: If the daemon is logged out reinitialize the
10449 daemon and continue. Otherwise a new daemon
10450 process is created automatically and you can
10451 continue from there.
10452
10453
10454 daemon_user_manager_ 181 08/03/23 MR12.7^L
10455
10456
10457
10458
10459 daemon_user_manager_.pl1
10460 daemon_user_manager_: ERROR_MESSAGE. No MC ACS
10461 segment for message coordinator source SOURCE
10462
10463
10464 Stream: as severity1
10465
10466 Time: In response to an operator command.
10467
10468 Meaning: The message coordinator access control segment
10469 >system_control_1>mc_acs>SOURCE.mcacs was not
10470 found. It must be created and given an ACL which
10471 permits the operator to logout the daemon.
10472 Therefore the operator cannot logout the daemon.
10473
10474 Action: Contact the system programming staff._sa
10475
10476
10477 daemon_user_manager_.pl1
10478 daemon_user_manager_: Event entry called with
10479 null ev_msg_ptr
10480
10481
10482 Stream: as severity2
10483
10484 Time: While system is running.
10485
10486 Meaning: This indicates an error in the Answering Service.
10487
10488 Action: Contact the system programming staff.
10489
10490
10491 daemon_user_manager_.pl1
10492 daemon_user_manager_: Fatal process error loop
10493 for NAME.PROJ SOURCE.
10494 Daemon will be logged out.
10495
10496
10497
10498 Stream: as severity1
10499
10500 Time: While system is running.
10501
10502 Meaning: An error in a daemon process has caused it to
10503 terminate repeatedly within the last few minutes.
10504 Detection of the loop causes the daemon to be
10505 logged out.
10506
10507 Action: Try to login the daemon again. If it still fails
10508 notify your System Administrator of the problem.
10509
10510
10511
10512 daemon_user_manager_ 182 08/03/23 MR12.7^L
10513
10514
10515
10516
10517 daemon_user_manager_.pl1
10518 daemon_user_manager_: Invalid signal from NAME
10519 PROJ SOURCE
10520 daemon_user_manager_: signal was "XXXXXXXX"
10521 YYY|ZZZZ
10522
10523
10524
10525 Stream: as severity2
10526
10527 Time: While system is running.
10528
10529 Meaning: This message may result from an error in the
10530 Answering Service an error in one of the daemon
10531 processes or an attempt by an unauthorized user
10532 to signal the daemon user manager. If the NAME
10533 PROJ and SOURCE cannot be determined the process
10534 ID of the sender is shown instead. The DUT
10535 daemon user table entry affected is located at
10536 YYY|ZZZZ in the Answering Service.
10537
10538 The signal is ignored and the Answering Service
10539 attempts to continue. If a daemon user is named
10540 on the first line of the message this user will
10541 probably be unable to continue.
10542
10543 Action: Contact the system programming staff. If the user
10544 named in the message is a daemon user try typing
10545 "logout NAME PROJ SOURCE" and if this succeeds
10546 log the user in again if necessary.
10547
10548
10549
10550 daemon_user_manager_.pl1
10551 daemon_user_manager_: NAME PROJ SOURCE
10552 terminated. Daemon will be logged out.
10553
10554
10555 Stream: as severity2
10556
10557 Time: While system is running.
10558
10559 Meaning: NAME is the Person_id of the daemon PROJ is the
10560 Project_id of the daemon and SOURCE is the
10561 Message Coordinator source id of the daemon. The
10562 daemon encountered a fatal process error and was
10563 logged out to prevent the system from getting into
10564 a loop.
10565
10566 Action: Contact the system programming staff. You can try
10567 logging the daemon in again but if the process
10568
10569
10570 daemon_user_manager_ 183 08/03/23 MR12.7^L
10571
10572
10573 error is recurrent the problem must be corrected
10574 before the daemon will operate successfully.
10575
10576
10577
10578 daemon_user_manager_.pl1
10579 daemon_user_manager_: New process created.
10580
10581
10582 Stream: as severity1
10583
10584 Time: While system is running.
10585
10586 Meaning: An error in a daemon process has caused it to
10587 terminate. A new process has been created.
10588
10589 Action: A new daemon process is created automatically and
10590 you can continue from there.
10591
10592
10593
10594 daemon_user_manager_.pl1
10595 daemon_user_manager_: premature STOPSTOP for
10596 NAME.PROJ SOURCE
10597
10598
10599 Stream: as severity0
10600
10601 Time: While system is running.
10602
10603 Meaning: This indicates a logic error in the supervisor or
10604 CPU or memory hardware problems.
10605
10606 Action: No operator action is required.
10607
10608
10609 daemon_user_manager_.pl1
10610 daemon_user_manager_: process PERSON.PROJECT
10611 SOURCE ignored trm_ signal.
10612
10613
10614 Stream: as severity 1
10615
10616 Time: While system is running.
10617
10618 Meaning: The daemon process PERSON.PROJECT using message
10619 coordinator SOURCE had been sent a trm_ signal to
10620 cause process termination but the process did not
10621 respond to the signal. The answering service
10622 proceeds with the bump new_proc log out etc
10623 operation.
10624
10625 Action: No operator action is required.
10626
10627
10628 daemon_user_manager_ 184 08/03/23 MR12.7^L
10629
10630
10631
10632
10633 daemon_user_manager_.pl1
10634 daemon_user_manager_: process PERSON.PROJECT
10635 SOURCE ignored wakeup EVENT_MSG from
10636 SENDER_PROCESS_ID
10637
10638
10639 Stream: as severity 1
10640
10641 Time: While system is running.
10642
10643 Meaning: The daemon process PERSON.PROJECT using message
10644 coordinator SOURCE had been sent a wakeup with
10645 EVENT_MSG by the process with process_id
10646 SENDER_PROCESS_ID. This event message is unknown
10647 and will be ignored.
10648
10649 Action: No operator action is required.
10650
10651
10652 daemon_user_manager_.pl1
10653 daemon_user_manager_: You cannot new_proc to the
10654 requested authorization.
10655 Cannot new_proc to an authorization outside the
10656 daemon's allowed range.
10657
10658
10659
10660 Stream: as severity1
10661
10662 Time: While system is running.
10663
10664 Meaning: A daemon executed an improper new_proc command
10665 trying to change to an authorization greater than
10666 its maximum allowed authorization or less than
10667 its minimum allowed authorization as specified in
10668 the Person Name Table PNT System
10669 Administrator's Table SAT and Project Master
10670 File PMF. The new_proc is performed at the
10671 original authorization of the process.
10672
10673 Action: Contact the system programming staff._sa
10674
10675
10676 dbm_man.pl1
10677 dbm_man: attempt to initialize already
10678 initialized map for PV on dskX_NNS
10679
10680
10681 Stream: BOS Typewriter Crashes system
10682
10683 Time: While system is running.
10684
10685
10686 dbm_man 185 08/03/23 MR12.7^L
10687
10688
10689 Meaning: This indicates a logic error in the supervisor or
10690 CPU or memory hardware problems.
10691
10692 Action: Follow normal recovery procedures.
10693
10694
10695 dbm_man.pl1
10696 dbm_man: bit map relp not set in pvte for PV on
10697 dskX_NNS
10698
10699
10700 Stream: BOS Typewriter Crashes system
10701
10702 Time: While system is running.
10703
10704 Meaning: This indicates a logic error in the supervisor or
10705 CPU or memory hardware problems.
10706
10707 Action: Follow normal recovery procedures.
10708
10709
10710 dbm_man.pl1
10711 dbm_man: Cannot get ASTE for dbm_seg
10712
10713
10714 Stream: BOS Typewriter Crashes system
10715
10716 Time: System Intialization.
10717
10718 Meaning: The system was unable to create the dbm_seg and
10719 obtain an ASTE for this segment.
10720
10721 Action: Contact the system programming staff._sa
10722
10723
10724 dbm_man.pl1
10725 dbm_man: csl failure
10726
10727
10728 Stream: Logged in SYSERR log.
10729
10730 Time: While system is running.
10731
10732 Meaning: The CSL instruction appears to have failed on one
10733 of the processors.
10734
10735 Action: No operator action is required.
10736
10737
10738 dbm_man.pl1
10739 dbm_man: unable to allocate dumper bit map for PV
10740 on dskX_NNS
10741
10742
10743
10744 dbm_man 186 08/03/23 MR12.7^L
10745
10746
10747 Stream: BOS Typewriter Crashes system
10748
10749 Time: While system is running.
10750
10751 Meaning: The system was unable to allocate a dumper bit map
10752 in dbm_seg for the volume on dskX_NNS. Too many
10753 volumes are online or there is something wrong
10754 with the volume header.
10755
10756 Action: Follow normal recovery procedures.
10757
10758
10759 dbm_man.pl1
10760 dbm_man: unable to initialize area: ERROR_MESS
10761
10762
10763 Stream: BOS Typewriter Crashes system
10764
10765 Time: While system is running.
10766
10767 Meaning: This indicates a logic error in the supervisor or
10768 CPU or memory hardware problems.
10769
10770 Action: Follow normal recovery procedures.
10771
10772
10773 deactivate_for_demount.pl1
10774 deactivate_for_demount: Error freeing vtocx OOOO
10775 on dskX_NN for UID. ERRORMESSAGE.
10776
10777
10778 Stream: Logged in SYSERR log.
10779
10780 Time: During system shutdown.
10781
10782 Meaning: The VTOCE for a deciduous segment could not be
10783 freed for the reason indicated. The VTOCE will be
10784 freed by the next volume salvage or by
10785 delete_old_pdds.
10786
10787 Action: No operator action is required.
10788
10789
10790 deactivate_segs.pl1
10791 deactivate_segs: unflushed trailer
10792
10793
10794 Stream: BOS Typewriter Crashes system
10795
10796 Time: While system is running.
10797
10798 Meaning: After destroying a process the system found that
10799 some system trailer specifying connection of that
10800
10801
10802 deactivate_segs 187 08/03/23 MR12.7^L
10803
10804
10805 process to some segment still exists for that
10806 process in str_seg. This indicates that some
10807 segment was improperly disconnected from the
10808 process at some time.This indicates a logic error
10809 in the supervisor or CPU or memory hardware
10810 problems.
10811
10812 Action: Follow normal recovery procedures.
10813
10814
10815 debug_check.pl1
10816 debug_check: too many parameters on parm cards
10817
10818
10819 Stream: BOS Typewriter.
10820
10821 Time: System Intialization.
10822
10823 Meaning: A total of 14 options may be specified on PARM
10824 cards. This limit has been exceeded. Options
10825 after the 14th will be ignored.
10826
10827 Action: Correct the configuration deck before the next
10828 bootload.
10829
10830
10831
10832 obs_reconfigure.pl1
10833 delcpu: Cannot stop CPU X.
10834
10835
10836 Stream: Initializer process output.
10837
10838 Time: In response to an operator command.
10839
10840 Meaning: CPU X did not respond to a command to stop within
10841 the expected time. The CPU may be malfunctioning
10842 or in STEP or it may be in a very tight loop.
10843
10844 Action: Check the CPU panel. If the processor appears to
10845 be in a loop it may be possible to break it out
10846 by placing zeros in the processor switches and
10847 using the EXECUTE button to cause a fault; but
10848 this action sometimes causes the system to crash
10849 depending on where the loop is.
10850
10851
10852
10853 obs_reconfigure.pl1
10854 delcpu: CPU X is not online.
10855
10856
10857 Stream: Initializer process output.
10858
10859
10860 delcpu 188 08/03/23 MR12.7^L
10861
10862
10863 Time: In response to an operator command.
10864
10865 Meaning: A delcpu X command finds that CPU X is already
10866 deleted.
10867
10868 Action: No operator action is required.
10869
10870
10871 obs_reconfigure.pl1
10872 delcpu: CPU X is the only CPU.
10873
10874
10875 Stream: Initializer process output.
10876
10877 Time: In response to an operator command.
10878
10879 Meaning: A delcpu X command attempted to delete the last
10880 CPU. No action was taken.
10881
10882 Action: No operator action is required.
10883
10884
10885 obs_reconfigure.pl1
10886 delcpu: Illegal command or subroutine argument.
10887 BLAH
10888
10889
10890 Stream: Initializer process output.
10891
10892 Time: In response to an operator command.
10893
10894 Meaning: Invalid input was typed.
10895
10896 Action: Enter a corrected command line.
10897
10898
10899 obs_reconfigure.pl1
10900 delcpu: Reconfiguration database is locked.
10901
10902
10903 Stream: Initializer process output.
10904
10905 Time: In response to an operator command.
10906
10907 Meaning: Another process is performing reconfiguration
10908 currently or a fault during reconfiguration has
10909 left the reconfiguration tables locked.
10910
10911 Action: If it is certain that no other process is
10912 reconfiguring and that the fault which
10913 interrupted reconfiguration has been cured the
10914 reconfigure$force_unlock command may be used to
10915 clear the lock at the direction of system staff.
10916
10917
10918 delcpu 189 08/03/23 MR12.7^L
10919
10920
10921
10922
10923 obs_reconfigure.pl1
10924 delcpu: Wrong number of arguments supplied.
10925
10926
10927 Stream: Initializer process output.
10928
10929 Time: In response to an operator command.
10930
10931 Meaning: Invalid input was typed.
10932
10933 Action: Enter a corrected command line.
10934
10935
10936 delentry.pl1
10937 delentry: deleting damaged dir PATH for USERID
10938
10939
10940 Stream: Logged in SYSERR log.
10941
10942 Time: While system is running.
10943
10944 Meaning: An attempt to delete a directory found that the
10945 directory header had a zero UID. The directory
10946 was deleted anyway.
10947
10948 Action: No operator action is required.
10949
10950
10951 delentry.pl1
10952 delentry: error from hash$out on "NAME" for
10953 USERID. ERROR_CODE
10954
10955
10956 Stream: Logged in SYSERR log.
10957
10958 Time: While system is running.
10959
10960 Meaning: An attempt to delete the entry name NAME from the
10961 directory hash table failed. This indicates a
10962 logic error in the supervisor or CPU or memory
10963 hardware problems.
10964
10965 Action: No operator action is required.
10966
10967
10968 delentry.pl1
10969 delentry: error from terminate_ for USERID.
10970 ERROR_CODE
10971
10972
10973 Stream: Logged in SYSERR log.
10974
10975
10976 delentry 190 08/03/23 MR12.7^L
10977
10978
10979 Time: While system is running.
10980
10981 Meaning: An error code was returned while trying to make a
10982 directory unknown while deleting it. This
10983 indicates a logic error in the supervisor or CPU
10984 or memory hardware problems.
10985
10986 Action: No operator action is required.
10987
10988
10989 delentry.pl1
10990 delentry: priv_dfile error deleting vtoce for
10991 PATH for USERID. ERROR_CODE
10992
10993
10994 Stream: Logged in SYSERR log.
10995
10996 Time: While system is running.
10997
10998 Meaning: A privileged call to delete a segment discovered a
10999 branch with not VTOC entry. This situation is
11000 called a "connection failure." The branch was
11001 deleted anyway.
11002
11003 Action: No operator action is required.
11004
11005
11006 delete_vtoce.pl1
11007 delete_vtoce: cannot add time/page product
11008 SEGTPP DIRTPP to pvid PPP vtocx VVV uid UUU
11009 ERRORMESSAGE
11010
11011
11012
11013 Stream: Logged in SYSERR log.
11014
11015 Time: While system is running.
11016
11017 Meaning: During the deletion of a directory which had a
11018 quota account a difficulty was encountered in
11019 reflecting its time/page product upward. SEGTPP
11020 and DIRTPP are the time/page product for segments
11021 and directories respectively.
11022
11023 Action: Contact the system programming staff._sa
11024
11025
11026 delete_vtoce.pl1
11027 delete_vtoce: from quotaw pvid PPP. vtocx VVV
11028 ERRORMESSAGE
11029
11030
11031 Stream: Logged in SYSERR log.
11032
11033
11034 delete_vtoce 191 08/03/23 MR12.7^L
11035
11036
11037 Time: While system is running.
11038
11039 Meaning: While deleting a directory which had a quota
11040 account a quota handling problem usually record
11041 quota overflow was encountered.
11042
11043 Action: No operator action is required.
11044
11045
11046 obs_reconfigure.pl1
11047 Deleted CPU X.
11048
11049
11050 Stream: Initializer process output.
11051
11052 Time: In response to an operator command.
11053
11054 Meaning: This is the response to a successful delcpu X
11055 command.
11056
11057 Action: No operator action is required.
11058
11059
11060 obs_reconfigure.pl1
11061 delmain: Abs wired pages in memory.
11062
11063
11064 Stream: Initializer process output.
11065
11066 Time: In response to an operator command.
11067
11068 Meaning: A delmain command attempted to delete a range of
11069 pages which included some pages which cannot be
11070 deleted. No action was taken.
11071
11072 Action: Enter a corrected command line.
11073
11074
11075 obs_reconfigure.pl1
11076 delmain: Illegal command or subroutine argument.
11077 BLAH
11078
11079
11080 Stream: Initializer process output.
11081
11082 Time: In response to an operator command.
11083
11084 Meaning: Invalid input was typed.
11085
11086 Action: Enter a corrected command line.
11087
11088
11089
11090
11091
11092 delmain 192 08/03/23 MR12.7^L
11093
11094
11095
11096
11097 obs_reconfigure.pl1
11098 delmain: Not enough main memory left.
11099
11100
11101 Stream: Initializer process output.
11102
11103 Time: In response to an operator command.
11104
11105 Meaning: A delmain command attempted to delete so much
11106 memory that the system would be unable to function
11107 correctly. No action was taken.
11108
11109 Action: Enter a corrected command line.
11110
11111
11112 obs_reconfigure.pl1
11113 delmain: Reconfiguration database is locked.
11114
11115
11116 Stream: Initializer process output.
11117
11118 Time: In response to an operator command.
11119
11120 Meaning: Another process is performing reconfiguration
11121 currently or a fault during reconfiguration has
11122 left the reconfiguration tables locked.
11123
11124 Action: If it is certain that no other process is
11125 reconfiguring and that the fault which
11126 interrupted reconfiguration has been cured the
11127 reconfigure$force_unlock command may be used to
11128 clear the lock at the direction of system staff.
11129
11130
11131
11132 obs_reconfigure.pl1
11133 delmain: Request is not within range of a single
11134 controller. MAIN XXX
11135
11136
11137 Stream: Initializer process output.
11138
11139 Time: In response to an operator command.
11140
11141 Meaning: A delmain command must specify a range of pages
11142 which lies completely within one controller. No
11143 action was taken.
11144
11145 Action: Enter a corrected command line.
11146
11147
11148
11149
11150 delmain 193 08/03/23 MR12.7^L
11151
11152
11153
11154
11155 obs_reconfigure.pl1
11156 delmain: Wrong number of arguments supplied.
11157
11158
11159 Stream: Initializer process output.
11160
11161 Time: In response to an operator command.
11162
11163 Meaning: Invalid input was typed.
11164
11165 Action: Enter a corrected command line.
11166
11167
11168 obs_reconfigure.pl1
11169 delmem: Abs wired pages in MEM Y.
11170
11171
11172 Stream: Initializer process output.
11173
11174 Time: In response to an operator command.
11175
11176 Meaning: An attempt was made to delete a memory which
11177 included some pages which cannot be deleted. No
11178 action was taken.
11179
11180 Action: The memory cannot be deleted.
11181
11182
11183 obs_reconfigure.pl1
11184 delmem: Illegal command or subroutine argument.
11185 BLAH
11186
11187
11188 Stream: Initializer process output.
11189
11190 Time: In response to an operator command.
11191
11192 Meaning: Invalid input was typed.
11193
11194 Action: Enter a corrected command line.
11195
11196
11197 obs_reconfigure.pl1
11198 delmem: MEM Y is not online.
11199
11200
11201 Stream: Initializer process output.
11202
11203 Time: In response to an operator command.
11204
11205
11206
11207
11208 delmem 194 08/03/23 MR12.7^L
11209
11210
11211 Meaning: A delmem Y command was typed but no such memory is
11212 in use.
11213
11214 Action: No operator action is required.
11215
11216
11217 obs_reconfigure.pl1
11218 delmem: Not enough main memory to remove MEM Y.
11219
11220
11221 Stream: Initializer process output.
11222
11223 Time: In response to an operator command.
11224
11225 Meaning: The system would be unable to function correctly
11226 if SCU Y and its memory were deleted. No action
11227 was taken.
11228
11229 Action: Try something else.
11230
11231
11232 obs_reconfigure.pl1
11233 delmem: Reconfiguration database is locked.
11234
11235
11236 Stream: Initializer process output.
11237
11238 Time: In response to an operator command.
11239
11240 Meaning: Another process is performing reconfiguration
11241 currently or a fault during reconfiguration has
11242 left the reconfiguration tables locked.
11243
11244 Action: If it is certain that no other process is
11245 reconfiguring and that the fault which
11246 interrupted reconfiguration has been cured the
11247 reconfigure$force_unlock command may be used to
11248 clear the lock at the direction of system staff.
11249
11250
11251
11252 add_scu.pl1
11253 delmem: Removed MEM X.
11254
11255
11256 Stream: BOS Typewriter.
11257
11258 Time: In response to an operator command.
11259
11260 Meaning: The system control unit X has been deleted.
11261
11262 Action: No operator action is required.
11263
11264
11265
11266 delmem 195 08/03/23 MR12.7^L
11267
11268
11269
11270
11271 obs_reconfigure.pl1
11272 delmem: Wrong number of arguments supplied.
11273
11274
11275 Stream: Initializer process output.
11276
11277 Time: In response to an operator command.
11278
11279 Meaning: Invalid input was typed.
11280
11281 Action: Enter a corrected command line.
11282
11283
11284 demount_pv.pl1
11285 demount_pv: ast out of sync
11286
11287
11288 Stream: BOS Typewriter Crashes system
11289
11290 Time: Volume demounting or system shutdown.
11291
11292 Meaning: The volume demounter has detected irreparable
11293 damage to the system segment table SST.
11294
11295 Action: Emergency shutdown will fail and need not be
11296 attempted. Follow normal recovery procedures for
11297 ESD failure.
11298
11299
11300
11301 demount_pv.pl1
11302 demount_pv: ioi_PROGNAME for DRIVENAME:
11303 ERRORMESSAGE
11304
11305
11306 Stream: BOS Typewriter.
11307
11308 Time: Volume demounting.
11309
11310 Meaning: In attempting to cycle down drive DRIVENAME an
11311 unexpected error was received from the I/O
11312 Interfacer. The drive may not be cycled down.
11313
11314 Action: Notify the system programming staff. Cycle down
11315 the drive if it was not cycled down.
11316
11317
11318 demount_pv.pl1
11319 demount_pv: vtoc cleanup of DRIVENAME:
11320 ERRORMESSAGE
11321
11322
11323
11324 demount_pv 196 08/03/23 MR12.7^L
11325
11326
11327 Stream: BOS Typewriter.
11328
11329 Time: Volume demounting or shutdown.
11330
11331 Meaning: An unexpected error was encountered in flushing
11332 VTOC information out to a volume being shut down
11333 or demounted. The volume will not be demounted.
11334 message.
11335
11336 Action: Contact the system programming staff. Attempt to
11337 repeat the demount of the logical volume if this
11338 is not during shutdown. The physical volume
11339 involved may have to be salvaged.
11340
11341
11342
11343 demount_pv.pl1
11344 demounted DRIVENAME
11345
11346
11347 Stream: BOS Typewriter.
11348
11349 Time: Volume demounting in response to delete_lv
11350 command or user action.
11351
11352 Meaning: The disk pack on drive DRIVENAME was successfully
11353 demounted.
11354
11355 Action: No operator action is required.
11356
11357
11358 disk_table_.pl1
11359 demounted lv LVNAME
11360
11361
11362 Stream: Initializer process output.
11363
11364 Time: While system is running.
11365
11366 Meaning: The demount of the logical volume LVNAME is
11367 complete.
11368
11369 Action: No operator action is required.
11370
11371
11372 device_acct_.pl1
11373 device_acct_$init: ERROR_MESSAGE. device_table
11374
11375
11376 Stream: as severity 2
11377
11378 Time: System Intialization.
11379
11380
11381
11382 device_acct_$init 197 08/03/23 MR12.7^L
11383
11384
11385 Meaning: An error occurred which initializing the
11386 device_table. ERROR_MESSAGE is the text
11387 associated with the error code describing the
11388 error. Device accounting is disabled and system
11389 initialization fails.
11390
11391 Action: Contact the system programming staff.
11392
11393
11394 device_acct_.pl1
11395 device_acct_$off: device N ACCT_TYPE_NAME
11396 DEV_NAME not in device table for PERSON.PROJECT
11397
11398
11399 Stream: as severity 0
11400
11401 Time: While system is running.
11402
11403 Meaning: Device DEV_NAME which has device accounting type
11404 number N associated with ACCT_TYPE_NAME devices
11405 was not found in PERSON.PROJECT's device table
11406 entries. Probable cause is damage to the device
11407 table.
11408
11409 Action: Contact the system programming staff._sa
11410
11411
11412 device_acct_.pl1
11413 device_acct_: deve.pdtep PTR1 not = ute.pdtep
11414 PTR2 for PERSON.PROJECT.
11415
11416
11417 Action: as severity 2
11418
11419 Time: While system is running.
11420
11421 Meaning: The Project Definition Table entry pointer PTR1
11422 stored in the device table for PERSON.PROJECT
11423 differs from the PDT entry pointer stored in that
11424 user's User Table Entry UTE.This indicates a
11425 logic error in the supervisor or CPU or memory
11426 hardware problems.
11427
11428 Action: Contact the system programming staff.
11429
11430
11431 device_acct_.pl1
11432 device_acct_: ERROR_MESSAGE. Attempting to lock
11433 PDT entry of PERSON.PROJECT
11434
11435
11436 Stream: as severity 2
11437
11438
11439
11440 device_acct_ 198 08/03/23 MR12.7^L
11441
11442
11443 Time: While system is running.
11444
11445 Meaning: An attempt was made to lock the Project Definition
11446 Table PDT entry for PERSON.PROJECT to update
11447 device usage charges for the user. Locking did
11448 not succeed within 15 seconds so the charges were
11449 not updated. If the attempt occurred during an
11450 accounting update the charges will continue to
11451 accrue until the next update at which time
11452 locking the PDT entry is again attempted. If the
11453 original attempt occurred as part of a logout or
11454 new_proc operation the device charges are lost.
11455
11456 Action: Contact the system programming staff._sa
11457
11458
11459 page_error.alm
11460 device_control: invalid pvtx XX
11461
11462
11463 Stream: BOS Typewriter Crashes system
11464
11465 Time: While system is running.
11466
11467 Meaning: An invalid PVT index XX was found by device
11468 control or an invalid device type appeared in the
11469 PVT entry of that index. This indicates a logic
11470 error in the supervisor or CPU or memory hardware
11471 problems.
11472
11473 Action: Follow normal recovery procedures.
11474
11475
11476 dial_ctl_.pl1
11477 dial_ctl_: Autocall channel CHANNEL declared
11478 multi-class but does not support
11479 set_required_access_class.
11480
11481
11482 Stream: as severity2
11483
11484 Time: While system is running._
11485
11486 Meaning: The autocall channel CHANNEL has been declared
11487 multi-class in the CDT but the underlying
11488 multiplexer does not support the
11489 set_required_access_class control order. The
11490 channel should be defined as single class. The
11491 user's dial out request was refused.
11492
11493 Action: Contact the system programming staff._sa
11494
11495
11496
11497
11498 dial_ctl_ 199 08/03/23 MR12.7^L
11499
11500
11501
11502
11503 dial_ctl_.pl1
11504 dial_ctl_: Can't find process WWWWWWWWWWW
11505
11506
11507 Stream: as severity0
11508
11509 Time: While system is running.
11510
11511 Meaning: An invalid signal was received by the secondary
11512 terminal manager.
11513
11514 Action: Note for system programmer action.
11515
11516
11517 dial_ctl_.pl1
11518 dial_ctl_: Channel CHANNEL AIM_CLASS SERV_TYPE
11519 hung up on Initializer
11520
11521
11522 Stream: as severity1
11523
11524 Time: While system is running.
11525
11526 Meaning: The channel CHANNEL with access class AIM_CLASS
11527 and service type SERV_TYPE hung up. It had
11528 previously been dialed to the Initializer.
11529
11530 Action: No operator action is required.
11531
11532
11533 dial_ctl_.pl1
11534 dial_ctl_: Channel CHANNEL AIM_CLASS SERV_TYPE
11535 hung up on missing process WWWWWWWWWWWW
11536
11537
11538 Stream: as severity1
11539
11540 Time: While system is running.
11541
11542 Meaning: The channel CHANNEL with access class AIM_CLASS
11543 and service type SERV_TYPE hung up. It had been
11544 dialed to a process but the system cannot
11545 determine what process it had been connected to.
11546 The process may have terminated before the hangup
11547 was detected.
11548
11549 Action: If this happens often inform the programming
11550 staff.
11551
11552
11553 dial_ctl_.pl1
11554
11555
11556 dial_ctl_ 200 08/03/23 MR12.7^L
11557
11558
11559 dial_ctl_: Channel CHANNEL dialed to Initializer
11560 PERSON.PROJECT
11561
11562
11563 Stream: as severity2
11564
11565 Time: While system is running.
11566
11567 Meaning: An additional secondary terminal has been attached
11568 to the Initializer process as a result of a dial
11569 system command. CHANNEL specifies which terminal
11570 dialed Initializer.
11571
11572 Action: If this terminal has been connected to the
11573 Initializer by an authorized operations staff
11574 member proceed to use it by issuing an "accept"
11575 command and possibly the "substty" command. If
11576 this is an invalid attempt to connect to the
11577 system type "drop CHANNEL" to disconnect the
11578 terminal.
11579
11580
11581
11582 dial_ctl_.pl1
11583 dial_ctl_: Channel CHANNEL hung up after dial_out
11584 for PERSON.PROJECT
11585
11586
11587 Stream: as severity0
11588
11589 Time: While system is running.
11590
11591 Meaning: During a dial_out of channel CHANNEL by
11592 PERSON.PROJECT the channel hung up. The dial_out
11593 attempt was aborted.
11594
11595 Action: No operator action is required.
11596
11597
11598 dial_ctl_.pl1
11599 dial_ctl_: Dialing channel CHANNEL ACC_CLASS to
11600 DESTINATION for PERSON.PROJECT using comm
11601 privilege
11602
11603
11604 Stream: as severity0
11605
11606 Time: While system is running.
11607
11608 Meaning: The user PERSON.PROJECT is dialing out on dial
11609 channel CHANNEL with access class ACC_CLASS to the
11610 destination DESTINATION. If this log message ends
11611 with "using comm privilege" then the process
11612
11613
11614 dial_ctl_ 201 08/03/23 MR12.7^L
11615
11616
11617 dialing out has used the comm privilege to
11618 circumvent AIM restrictions.
11619
11620 Action: No operator action is required.
11621
11622
11623 dial_ctl_.pl1
11624 dial_ctl_: ERROR_MESSAGE From
11625 get_required_access_class control order on channel
11626 CHANNEL.
11627
11628
11629 Stream: as severity0
11630
11631 Time: While system is running.
11632
11633 Meaning: While attempting to determine whether the channel
11634 CHANNEL had any access class restrictions imposed
11635 on it by the hardcore ERROR_MESSAGE was returned.
11636 The request in progress was aborted.
11637
11638 Action: Note for system programmer action.
11639
11640
11641 dial_ctl_.pl1
11642 dial_ctl_: ERROR_MESSAGE. Can't find PNT entry:
11643 PERSON_ID
11644
11645
11646 Stream: as severity2
11647
11648 Time: While system is running.
11649
11650 Meaning: An attempt was made to find the Person Name Table
11651 entry of the PERSON_ID specified in a dial
11652 preaccess command. However an error occurred
11653 which searching in the PNT.
11654
11655 Action: Contact the system programming staff._sa
11656
11657
11658 dial_ctl_.pl1
11659 dial_ctl_: ERROR_MESSAGE. dial_out CHANNEL for
11660 PERSON.PROJECT failed.
11661
11662
11663 Stream: as severity0
11664
11665 Time: While system is running.
11666
11667 Meaning: While attempting to dial_out channel CHANNEL for
11668 PERSON.PROJECT the error ERROR_MESSAGE occured.
11669 The dial_out attempt was aborted.
11670
11671
11672 dial_ctl_ 202 08/03/23 MR12.7^L
11673
11674
11675 Action: No operator action is required.
11676
11677
11678 dial_ctl_.pl1
11679 dial_ctl_: ERROR_MESSAGE. after dial_out order
11680 CHANNEL for PERSON.PROJECT
11681
11682
11683 Stream: as severity0
11684
11685 Time: While system is running.
11686
11687 Meaning: The user PERSON.PROJECT is attempting a dial_out
11688 of channel CHANNEL. The dial_out control order
11689 produced the error ERROR_MESSAGE. The dial_out
11690 attempt is aborted.
11691
11692 Action: Note for system programmer action.
11693
11694
11695 dial_ctl_.pl1
11696 dial_ctl_: ERROR_MESSAGE. Attempting to detach
11697 CHANNEL from PERSON.PROJECT
11698
11699
11700 Stream: as severity0
11701
11702 Time: While system is running.
11703
11704 Meaning: An attempt to disconnect channel CHANNEL from
11705 PERSON.PROJECT failed. ERROR_MESSAGE explains
11706 why.
11707
11708 Action: Note for system programmer action.
11709
11710
11711 dial_ctl_.pl1
11712 dial_ctl_: ERROR_MESSAGE. call to
11713 astty_$tty_new_proc of CHANNEL for PERSON.PROJECT
11714 failed
11715
11716
11717 Stream: as severity0
11718
11719 Time: While system is running.
11720
11721 Meaning: An attempt to connect the channel CHANNEL to
11722 PERSON.PROJECT failed. ERROR_MESSAGE indicates
11723 why.
11724
11725 Action: Contact the system programming staff._sa
11726
11727
11728
11729
11730 dial_ctl_ 203 08/03/23 MR12.7^L
11731
11732
11733 dial_ctl_.pl1
11734 dial_ctl_: ERROR_MESSAGE. Could not check access
11735 to >sc1>admin_acs>tandd.acs for PERSON.PROJECT.
11736
11737
11738 Stream: as severity0
11739
11740 Time: While system is running.
11741
11742 Meaning: The user PERSON.PROJECT attempted to tandd_attach
11743 a communications channel. This operation is
11744 controlled by rw access to the ACS segment
11745 specified. For the reason ERROR_MESSAGE the
11746 answering service could not check access to the
11747 segment. The user tandd_attach request was
11748 refused.
11749
11750 Action: Contact the system programming staff._sa
11751
11752
11753 dial_ctl_.pl1
11754 dial_ctl_: ERROR_MESSAGE. getting
11755 dial_out_status or tty info CHANNEL for
11756 PERSON.PROJECT
11757
11758
11759 Stream: as severity0
11760
11761 Time: While system is running.
11762
11763 Meaning: During a dial_out of channel CHANNEL by
11764 PERSON.PROJECT the error ERROR_MESSAGE was
11765 returned while attempting to determine if the
11766 dial_out control order succeeded or failed.
11767
11768 Action: No operator action is required.
11769
11770
11771 dial_ctl_.pl1
11772 dial_ctl_: ERROR_MESSAGE. Issuing tandd_attach
11773 control order for channel CHAN
11774
11775
11776 Stream: as severity0
11777
11778 Time: While system is running.
11779
11780 Meaning: The user PERSON.PROJECT attempted to tandd_attach
11781 a communications channel which failed for the
11782 reason given by ERROR_MESSAGE. The user
11783 tandd_attach request was refused.
11784
11785 Action: Contact the system programming staff._sa
11786
11787
11788 dial_ctl_ 204 08/03/23 MR12.7^L
11789
11790
11791
11792
11793 dial_ctl_.pl1
11794 dial_ctl_: ndialed negative CHANNEL
11795
11796
11797 Stream: as severity0
11798
11799 Time: While system is running.
11800
11801 Meaning: The count of secondary consoles for a user is in
11802 error. A terminal is hanging up which claims to
11803 be attached to a user but his count of attached
11804 terminals is zero.
11805
11806 Action: Note for system programmer action.
11807
11808
11809 dial_ctl_.pl1
11810 dial_ctl_: Program error.
11811 as_request_sender.version N not correct in dial
11812 request. Should be M.
11813
11814
11815 Stream: as severity1
11816
11817 Time: While system is running.
11818
11819 Meaning: There is a mismatch in the version number used by
11820 the the programs as_request_server_ and dial_ctl_
11821 for the as_request_sender_ structure.
11822
11823 Action: Contact the system programming staff.
11824
11825
11826 dial_ctl_.pl1
11827 dial_ctl_: Refused unknown request from
11828 PERSON.PROJECT; ERROR_MESSAGE REASON
11829
11830
11831 Stream: as severity0
11832
11833 Time: While system is running.
11834
11835 Meaning: PERSON.PROJECT send a dial_server request to the
11836 Initializer of unknown format. It was rejected
11837 for the reasons specified in ERROR_MESSAGE and
11838 REASON.
11839
11840
11841
11842 dial_ctl_.pl1
11843 dial_ctl_: Rejected unknown request from
11844
11845
11846 dial_ctl_ 205 08/03/23 MR12.7^L
11847
11848
11849 PERSON.PROJECT. No request flags set in
11850 dial_server_request.
11851
11852
11853 Stream: as severity0
11854
11855 Time: While system is running.
11856
11857 Meaning: The user PERSON.PROJECT attempted to send an
11858 dial_server request to the Initializer but failed
11859 to specify what type of request he/she wanted.
11860
11861 Action: No operator action is required.
11862
11863
11864 dial_ctl_.pl1
11865 dial_ctl_: sat.ht has PROJECT_ID sat has
11866 OTHER_PROJECT_ID at LOC.
11867
11868
11869 Stream: as severity2
11870
11871 Time: While system is running.
11872
11873 Meaning: The System Administrator's Table is inconsistent
11874 with the location information in its hash table.
11875
11876 Action: Contact the system programming staff._sa
11877
11878
11879 dial_ctl_.pl1
11880 dial_ctl_: Tracing turned off
11881
11882
11883 Stream: as severity1
11884
11885 Time: While system is running.
11886
11887 Meaning: A system administrator has disabled dial_ctl_
11888 tracing.
11889
11890 Action: No operator action is required.
11891
11892
11893 dial_ctl_.pl1
11894 dial_ctl_: Tracing turned on.
11895
11896
11897 Stream: as severity1
11898
11899 Time: While system is running.
11900
11901
11902
11903
11904 dial_ctl_ 206 08/03/23 MR12.7^L
11905
11906
11907 Meaning: A system administrator had enabled tracing of the
11908 dial_ctl_ program. Many status messages will be
11909 logged and printed on the console.
11910
11911 Action: No operator action is required.
11912
11913
11914 dial_ctl_.pl1
11915 DIALIN PERSON1.PROJECT1 CHANNEL to QUALIFIER
11916 PERSON2.PROJECT2
11917
11918
11919 Stream: as severity0
11920
11921 Time: While system is running.
11922
11923 Meaning: A user on channel CHANNEL has used the "dial"
11924 preaccess command to dial the dial qualifier
11925 QUALIFIER owned by PERSON2.PROJECT2. If the
11926 check_acs "slave_dial" flags was on for the
11927 channel then PERSON1.PROJECT1 specifies the
11928 identified user.
11929
11930 Action: No operator action is required.
11931
11932
11933 dial_ctl_.pl1
11934 DIALIN DENIED PERSON1.PROJECT1 CHANNEL to
11935 QUALIFIER PERSON2.PROJECT2 REASON
11936
11937
11938 Stream: as severity0
11939
11940 Time: While system is running.
11941
11942 Meaning: A user on channel CHANNEL attempted to use the
11943 "dial" preaccess command to dial to QUALIFIER
11944 owned by PERSON2.PROJECT2. The attempt was
11945 rejected for REASON. If the channel check_acs
11946 "slave_dial" flag was on then PERSON1.PROJECT1
11947 specifies the identified user on this channel.
11948
11949 Action: Note for system programmer action.
11950
11951
11952 dialup_.pl1
11953 dialup_: answer table damaged at UTEP
11954 tra_vec=TTTT
11955
11956
11957 Stream: as severity 2
11958
11959 Time: While system is running.
11960
11961
11962 dialup_ 207 08/03/23 MR12.7^L
11963
11964
11965 Meaning: The tra_vec value was found to be invalid for an
11966 answer table wakeup. Damage to the answer table
11967 is indicated.
11968
11969 Action: Contact the system programming staff.
11970
11971
11972 dialup_.pl1
11973 dialup_: called while ansp = null
11974
11975
11976 Stream: as severity 2
11977
11978 Time: While system is running.
11979
11980 Meaning: A programming error in the Answering Service or an
11981 incorrect library installation has caused the
11982 Answering Service to be called before being
11983 initialized. The system will ignore the error and
11984 attempt to continue.
11985
11986 Action: Shut down the system and perform a bootload
11987 operation.
11988
11989
11990 dialup_.pl1
11991 dialup_: called with bad ptr EVENT_MSG_PTR by
11992 WWWWWWWWWWWW
11993
11994
11995 Stream: as severity 2
11996
11997 Time: While system is running.
11998
11999 Meaning: A programming error in the interprocess
12000 communication system the network software or the
12001 Answering Service itself has occurred. An invalid
12002 message pointer has been passed to the Answering
12003 Service. The system ignores the message and
12004 attempts to continue. This message may be the
12005 result of an incorrect library installation.
12006
12007 Action: Shut down the system and perform a bootload
12008 operation.
12009
12010
12011 dialup_.pl1
12012 dialup_: called with null message ptr
12013
12014
12015 Stream: as severity 2
12016
12017 Time: While system is running.
12018
12019
12020 dialup_ 208 08/03/23 MR12.7^L
12021
12022
12023 Meaning: A programming error in the interprocess
12024 communication system the network software or the
12025 Answering Service itself has occurred. An invalid
12026 message pointer has been passed to the Answering
12027 Service. The system ignores the message and
12028 attempts to continue. This message may be the
12029 result of an incorrect library installation.
12030
12031 Action: Shut down the system and perform a bootload
12032 operation. Inform the system programming staff.
12033
12034
12035
12036 dialup_.pl1
12037 dialup_: cancelling inactivity bump of
12038 PERSON.PROJECT
12039
12040
12041 Stream: as severity 1
12042
12043 Time: While system is running.
12044
12045 Meaning: This is a logging message indicating that the
12046 PERSON.PROJECT process that had been previously
12047 bumped due to inactivity has become active. The
12048 automatic logout was therefore cancelled. The
12049 user will receive a message to this effect.
12050
12051 Action: No operator action is required.
12052
12053
12054 dialup_.pl1
12055 dialup_: CDT damaged at CDTEP tra_vec=TTTT
12056
12057
12058 Stream: as severity 2
12059
12060 Time: While system is running.
12061
12062 Meaning: The tra_vec value was found to be invalid for a
12063 channel wakeup. Damage to the CDT is indicated.
12064
12065 Action: Contact the system programming staff.
12066
12067
12068 dialup_.pl1
12069 dialup_: cdte CDTEP CHANNEL state M in use N -
12070 notify system programmer"
12071
12072
12073 Stream: as severity 0
12074
12075 Time: While system is running.
12076
12077
12078 dialup_ 209 08/03/23 MR12.7^L
12079
12080
12081 Meaning: This indicates a logic error in the supervisor or
12082 CPU or memory hardware problems.
12083
12084 Action: Contact the system programming staff.
12085
12086
12087 dialup_.pl1
12088 dialup_: cdtep = null and ate.active = DDDD for
12089 UTEP
12090
12091
12092 Stream: as severity 2
12093
12094 Time: While system is running.
12095
12096 Meaning: This indicates a logic error in the supervisor or
12097 CPU or memory hardware problems.
12098
12099 Action: Contact the system programming staff.
12100
12101
12102 dialup_.pl1
12103 dialup_: channel_error called with cdte in
12104 functional state.
12105
12106
12107 Stream: as severity 1
12108
12109 Time: While system is running.
12110
12111 Meaning: This indicates a logic error in the supervisor or
12112 CPU or memory hardware problems.
12113
12114 Action: Contact the system programming staff.
12115
12116
12117 dialup_.pl1
12118 dialup_: error - event calls were masked
12119
12120
12121 Stream: as severity 1
12122
12123 Time: While system is running.
12124
12125 Meaning: This message indicates a serious error in the
12126 Initializer programs. The system attempts to
12127 recover and keep running.
12128
12129 Action: Contact the system programming staff.
12130
12131
12132 dialup_.pl1
12133
12134
12135
12136 dialup_ 210 08/03/23 MR12.7^L
12137
12138
12139 dialup_: ERROR_MESSAGE Getting pointer to help
12140 file SYS_DIR>ENTRY_NAME
12141
12142
12143 Stream: as severity 2
12144
12145 Time: While system is running.
12146
12147 Meaning: An ERROR_MESSAGE was returned when an attempt was
12148 made to find the login_help or connect_help
12149 segment in the SYS_DIR usually >sc1.
12150
12151 Action: Contact the system programming staff.
12152
12153
12154 dialup_.pl1
12155 dialup_: ERROR_MESSAGE setting new tty info for
12156 CHANNEL
12157
12158
12159 Stream: as severity 0
12160
12161 Time: While system is running.
12162
12163 Meaning: An ERROR_MESSAGE was returned by a call to
12164 cpg_$set_pit_tty_info when setting new terminal
12165 attributes in a reconnected process on channel
12166 CHANNEL.
12167
12168 Action: Contact the system programming staff.
12169
12170
12171 dialup_.pl1
12172 dialup_: ERROR_MESSAGE Unable to declare handler
12173 for ev chn EVENT_CHN for ate UTEP for CDT_CHANNEL
12174
12175
12176 Stream: as severity 2
12177
12178 Time: While system is running.
12179
12180 Meaning: An ERROR_MESSAGE was returned when an attempt was
12181 made to declare an event call channel for new
12182 process UTEP on EVENT_CHN attached to
12183 CDT_CHANNEL.
12184
12185 Action: Contact the system programming staff.
12186
12187
12188 dialup_.pl1
12189 dialup_: ERROR_MESSAGE attempting to allocate a
12190 user table entry for CHANNEL
12191
12192
12193
12194 dialup_ 211 08/03/23 MR12.7^L
12195
12196
12197 Stream: as severity 1
12198
12199 Time: While system is running.
12200
12201 Meaning: An ERROR_MESSAGE was returned from a call to
12202 asu_$attach_ate which allocates a user table
12203 entry.
12204
12205 Action: Contact the system programming staff.
12206
12207
12208 dialup_.pl1
12209 dialup_: ERROR_MESSAGE creating process for
12210 PERSON.PROJECT
12211
12212
12213 Stream: as severity 2
12214
12215 Time: While system is running.
12216
12217 Meaning: An ERROR_MESSAGE was returned and the system was
12218 unable to create a user process for
12219 PERSON.PROJECT.
12220
12221 Action: If possible get in touch with the user. He got
12222 a message to contact you. Ask him to try again
12223 and to tell you of any peculiarities of his login.
12224 Note all particulars and contact the programming
12225 staff.
12226
12227
12228
12229 dialup_.pl1
12230 dialup_: ERROR_MESSAGE From write_status order on
12231 CHANNEL
12232
12233
12234 Stream: as severity 1
12235
12236 Time: While system is running.
12237
12238 Meaning: This is a debugging message that will only appear
12239 if tracing has been enabled. An ERROR_MESSAGE by
12240 a call to astty_$tty_order with a "write_status"
12241 order.
12242
12243 Action: Contact the system programming staff.
12244
12245
12246 dialup_.pl1
12247 dialup_: ERROR_MESSAGE get_required_access_class
12248 order failed for CHANNEL
12249
12250
12251
12252 dialup_ 212 08/03/23 MR12.7^L
12253
12254
12255 Stream: as severity 1
12256
12257 Time: While system is running.
12258
12259 Meaning: An ERROR_MESSAGE was returned by a call to
12260 astty_$tty_order with a get_required_access_class
12261 order for CHANNEL. The channel will be hungup.
12262
12263 Action: Contact the system programming staff._ssa
12264
12265
12266 dialup_.pl1
12267 dialup_: ERROR_MESSAGE ttt error removing
12268 channel CHANNEL COMMENT
12269
12270
12271 Stream: as severity 2
12272
12273 Time: While system is running.
12274
12275 Meaning: An ERROR_MESSAGE resulting from accessing the TTT
12276 has caused the CHANNEL with COMMENT to be unusable
12277 when attempting to set the default terminal type
12278 based on line-type/baud-rate. The channel has
12279 been removed from known channels.
12280
12281 Action: Contact the system programming staff. An attach
12282 of the CHANNEL can be tried. If the channel is to
12283 be left detached busy out the modem.
12284
12285
12286
12287 dialup_.pl1
12288 dialup_: ERROR_MESSAGE tty_dim error removing
12289 channel CHANNEL COMMENT
12290
12291
12292 Stream: as severity 2
12293
12294 Time: While system is running.
12295
12296 Meaning: An ERROR_MESSAGE caused the CHANNEL to be
12297 unusable. The CHANNEL with COMMENT will be
12298 removed from service.
12299
12300 Action: You may try to attach the channel. If that fails
12301 notify the system programmers. If the channel is
12302 to be left detached busy out the modem.
12303
12304
12305
12306 dialup_.pl1
12307
12308
12309
12310 dialup_ 213 08/03/23 MR12.7^L
12311
12312
12313 dialup_: ERROR_MESSAGE when attempting to notify
12314 user PERSON.PROJECT of dialup event
12315
12316
12317 Stream: as severity 0
12318
12319 Time: While system is running.
12320
12321 Meaning: An ERROR_MESSAGE was returned when an attempt was
12322 made to send a message to PERSON.PROJECT about a
12323 dialup event.
12324
12325 Action: Contact the system programming staff.
12326
12327
12328 dialup_.pl1
12329 dialup_: ERROR_MESSAGE. Trying to wakeup process
12330 after reconnection for PERSON.PROJECT.TAG
12331
12332
12333
12334 Stream: as severity 0
12335
12336 Time: Called in response to a user reconnecting to an
12337 interactive process.
12338
12339 Meaning: A failure occurred while sending a wakeup to the
12340 process being connected to the terminal.
12341 ERROR_MESSAGE is the text associated with the
12342 error code returned by hcs_$wakeup.
12343
12344 Action: No operator action is required.
12345
12346
12347 dialup_.pl1
12348 dialup_: fatal error during process creation for
12349 PERSON.PROJECT CHANNEL
12350
12351
12352 Stream: as severity 1
12353
12354 Time: While system is running.
12355
12356 Meaning: A fatal error occurred during process creation for
12357 PERSON.PROJECT on CHANNEL. Reason is given in
12358 previous log entry. This may be due to a user
12359 error: incorrect segments in the user's home
12360 directory or bad login arguments can cause this
12361 problem.
12362
12363 Action: No operator action is required.
12364
12365
12366
12367
12368 dialup_