__group__	owner	status	ticket	summary	component	version	milestone	type	priority	created	_changetime	_description	_reporter	_sort_accepted	_sort_owned	_sort_reported	_sort_priority
Reported	Eric Swenson	new	11	ISOLTS misses test opportunity	Documentation			enhancement	major	2017-02-05T18:38:17Z	2020-04-03T22:56:11Z	"The ISOLTS process includes instructing the operator to ""depress the initialize and clear push button"", but fails to verify that memory was actually cleared.

Failure of the operator is clear memory will result in incorrect test behavior, so it is reasonable for ISOLTS to verify that memory was cleared.

Failure of memory being cleared if the button was pressed would be indicative of a configuration or hardware failure, so it is reasonable that ISOLTS verify that was memory was cleared when the opportunity presents itself.

Before loading the PFT tests into the test segment, ISOLTS should check that the test segment is indeed set to all zeros, and if not, report that memory was not zero, indicating operator error, CPU malfunction or SCU malfunction.

Additionally, it should zero the memory before proceeding with the tests.

"	anonymous	0	0	True	3
Reported	Eric Swenson	new	363	Add operator support for GCOS Daemon	Administration		MR12.9	enhancement	major	2025-05-17T16:07:39Z	2025-05-17T16:07:39Z	"Now that the GCOS Daemon is working, it would be helpful to have operator support from the console in starting and maintaining it.

For example, ""x io"" and ""x io1"" prepare the printers, punches, etc. for use. It would be nice to have a ""x gcos"" that would login the GCOS daemon.

In a similar fashion, ""x read_cards"" starts a read on the card reader, ""x gcos_read_cards"" could attach and start the GCOS Daemon card reading."	anonymous	0	0	True	3
Reported	Eric Swenson	new	104	The behavior of the backup_dump does not match documentation w.r.t. '-nohold'	Hardcore			defect	minor	2018-02-04T23:06:54Z	2018-02-04T23:06:54Z	"The backup utilities are documented as unloading tapes by default, but do not.

complete_dump.info, backup_dump.info, catchup_dump.info:

{{{
-nohold
   rewinds and unloads the hierarchy dump tape or tapes at the end of
   the current dump pass.  This is the default.

}}}

start_dump.info:

{{{
-nohold
   rewinds and unloads the hierarchy dump tape or tapes at the end of
   the current dump pass.  This is the default for all hierarchy dump
   modes except incremental.
}}}




{{{
bk_ss_.cds:       2 holdsw bit (1),				/* ON => do not unmount tape when done */
bk_ss_.cds:	bk_static.holdsw = ""0""b;

}}}

 bk_arg_reader_:


{{{
               else if op = ""hold"" then bk_ss_$holdsw = ""1""b; /* do not dismount */
               else if op = ""nohold"" then bk_ss_$holdsw = """"b; /* dismount, default */
}}}


then in start_dump.pl1, after 'examine_arguments:' (the ""join"" for complete_dump, catchup_dump, start_dump):


{{{
          bk_ss_$holdsw = ""1""b;
}}}

""-nohold"" is also the documented behavior for 'retreive' and 'reload', but I have not tested the actual behavior.

retrieve.info, reload.info:

{{{

The following defaults are in effect for the reloader and retriever
before any backup commands are given; they are not, however, reset to
these values at the start of each backup command, except as noted
below.

      -all                    -noquota
      -error_of               -primary
      -map                    -reload
      -nodebug                -setlvid
      -nohold                 -trim

}}}
"	anonymous	0	0	True	4
Reported	Eric Swenson	new	121	Newly created root disks need salvaging.	Install/Upgrade			defect	minor	2018-06-10T02:19:35Z	2018-06-10T02:19:35Z	"Doing ""boot star rvls"" on a newly built root disk results in many ""04  Corrected master directory UID in header"" messages in the SALV OUTPUT report. (Discussions with Olin Sibert about the messages indicate that this is a minor Multics issue related to the order of events in the cold boot rather then an emulator or cold boot process error).

Adding a salvage run at the end of the cold boot process would clean up the distributed disk image."	anonymous	0	0	True	4
Reported	Eric Swenson	new	168	Race condition in sys_trouble can block.	Hardcore			defect	minor	2019-05-15T03:09:15Z	2019-05-15T03:09:15Z	"If there is a problem in rcf add cpu, sometimes the sys_trouble broadcast is sent before the new CPU has got it's act together and it misses the broadcast.

The code in sys_trouble that loops until all CPUs have acknowledged the sys_touble should have code to timeout and rebroadcast; and to give up waiting if that times out.

The added CPU does not boot correctly; occasionally seen in LOCKLESS due to host thread scheduling causing start CPU handshake failure.  The added CPU takes too long to signal successful startup; rcf assumes that the CPU is not running and goes to sys_trouble. The added CPU sets the flags that it has started; sys_trouble tells all of the non-bootload CPUs to die; the added CPU has not finished setting up it's interrupt handlers and misses the message. sys_troulbe loops forever waiting for it to acknowledge the die message. 
"	anonymous	0	0	True	4