Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site ucbvax.ARPA
Path: utzoo!linus!philabs!cmcl2!seismo!harvard!talcott!panda!genrad!decvax!decwrl!ucbvax!info-vax
From: info-vax@ucbvax.ARPA
Newsgroups: fa.info-vax
Subject: RSX changing process names
Message-ID: <9244@ucbvax.ARPA>
Date: Mon, 22-Jul-85 16:55:04 EDT
Article-I.D.: ucbvax.9244
Posted: Mon Jul 22 16:55:04 1985
Date-Received: Thu, 25-Jul-85 02:14:56 EDT
Sender: daemon@ucbvax.ARPA
Organization: University of California at Berkeley
Lines: 24

From: <#D15%DDATHD21.BITNET@WISCVM.ARPA>

The reasons why VAX-11 RSX changes the VMS process names are
explained in: "VAX-11 RSX Compatibility Mode Reference Manual"
chapter 2.3.2 and 2.3.3. I can give a short summary. VAX-11 RSX
changes the process name temporarily if:

 - the task hasn't a multiuser name (...xyz) in its task
   image label. The task name becomes the process name.
 - the task is running from a batch job with a default (BATCH_xxxxxx)
   process name. The name is changed to Bxxxxx. The first rule takes
   place over over this rule.
 - the name is longer than six characters or if there are any
   special characters in it.

All this name-changing is done to be COMPATIBLE with "NATIVE" RSX,
but the great ZAR is right: it's awfully slow.


Martin Knoblauch
TH-Darmstadt, HRZ
Petersenstrasse 30
D-6100 Darmstadt, West Germany
BITNET: #D15@DDATHD21 (The Number-sign is Part of my UID !!!!)