id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
312	Clarify that -dupt is an argument to eor, not ear + clarification that the .absout file is not necessarily in the same directory as the .absin file	David Rosenberg	Eric Swenson	"I misread mention of -dupt (-defer_until_process_termination) in the description of the enter_abs_request command in the enter_abs_request info segment and in the ""Multics Commands and Active Functions"" manual on page 3-297 (which bears the date 11/86 and order number AG92-06A).

I mistakenly thought that it was a control argument to ear. It is actually a control argument to eor. My misreading was the result of my failing to notice a one letter difference.

I'd like to suggest a clarification of the documentation to reduce the likelihood of anyone else making the same error that I made. For one thing, the example 
{{{
eor -dupt [user absout]
}}}
could be changed to 
{{{
enter_output_request -dupt [user absout]
}}}
The point could made more forcefully by adding a note something like ""NOTE: This is an enter_output_request command, not an enter_abs_request command.""

----

There is a separate issue in the same paragraph dealing with the need for the -defer_until_process_termination control argument. It starts with the sentence
  All input and output that occurs in the absentee job is written to the segment STR.absout in the same directory as the absentee segment STR.absin.
I think that isn't true. I think that the ear -output_file control argument can cause the .absout file to be written to a different directory than the directory holding the absin file."	enhancement	new	minor		Documentation	MR12.8