id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
314	Some command_processor_ pipes don't work in subsystem request lines.  Others do.	Gary Dixon	Eric Swenson	"Inside an SSU subsystem like analyze_multics (azm), a request line using pipe syntax is supposed to
return the output of an azm request line as results of a pipe-capturing active request string.  Using azm
as an example:



{{{
azm

azm:  sld >dumps>gary_dumps>3
  ERF 3   in directory >dumps>gary_dumps dumped at 08/21/23  1019.4 pdt Mon.
  System-ID MR12.8 Version-ID MR12.8
Proc   0 DBR  17171450 running        on cpu a   Initializer.SysDaemon.z

azm:  d 234 -as stack_header.ect_ptr;
  ect_ptr = 340|16040 >pdd>!zzzzzzzbBBBBBB>!BBBKWznZHhplJH.area.linker|16040


azm:  sbag &1 ||[d 234 -as stack_header.ect_ptr;|]
azm: File does not exist.

azm:  sbag &1 ""  ect_ptr = 340|16040 >pdd>!zzzzzzzbBBBBBB>!BBBKWznZHhplJH.area.linker|16040""
  ect_ptr = 340|16040 >pdd>!zzzzzzzbBBBBBB>!BBBKWznZHhplJH.area.linker|16040

azm:  
}}}

An equivalent set of commands does work at Multics command level.  For example:


{{{
dump_segment 234 -as stack_header.ect_ptr
000000
  ect_ptr = 247|17240   [pd]>!BBBKXCDgBLglMZ.area.linker
r 11:27 0.172 0

string ||[dump_segment 234 -as stack_header.ect_ptr;|]
000000   ect_ptr = 247|17240   [pd]>!BBBKXCDgBLglMZ.area.linker
r 11:28 0.237 2

}}}
"	defect	new	minor	No Milestore	Hardcore	MR12.8