Conference bulova::decw_jan-89_to_nov-90

2981.0. "CREATE/TERMINAL/PROCESS=x Problem" by AIKIDO::EZLIFE::YURCHAK (Mick Yurchak @VBE) Fri Jun 22 1990 10:55

	If I issue a CREATE/TERMINAL/PROCESS=<name>..., the specified
	process name does not take effect unless you already have a
	process with a name = your username.

	I.e., if I have some process running with the process name of
	YURCHAK and I create a new DECterm as above, then my newly
	created process has the process name that I specified.  However,
	if there are no processes with the process name of YURCHAK and
	I create a new DECterm, then the process name that I specified
	is ignored and the actual name assigned is YURCHAK.

	Is this a known problem?  If not, has anyone else seen this
	behavior or know what might be causing the problem.

	I should add that I'm creating a process on a remote system and
	directing the DECterm window to my workstation.  I haven't tried
	it locally since the session manager normally takes the username
	as its process name so that the above would always work.  All other
	qualifiers to the CREATE/TERM command seem to take effect in
	both situations.

	We're running VMS V5.3-1.

	The process name problem as outlined in .0 also occurs when
	creating a DECterm locally.  If I bring up the workstation
	specifying the session manager's process name in DECW$LOGIN.COM,
	then I end up with no processes with the process name = username.

	Then if I do a CREATE/TERMINAL/DETACH/PROCESS=foo, the process
	name given will be my username and not foo.

			-Mick-

    Please submit a QAR.

create/terminal/detatched/process="name"
does not set the new process's process_name to "name".


it seems to be an unpredictable problem.  i remember it working
once from dcl command line.  when it did work, it worked after i
reversed the order of the /deta and /proc qualifiers.

i never remember it working from SM menu.