[p4] OpenVMS question

[johan.nilsson@esrange.ssc.se]

Hi,

I'd like to keep the two latest versions of a VMS application online, let's
refer to them as TEST and PROD. They reside in two separate subdirectories
with a common structure, e.g. DISK$USER:[APP.TEST...] and
DISK$USER:[APP.PROD...] In my perforce client specification I refer to the
client root as DISK$USER:[APP] and do the following mapping:

//depot/app/main/...	//client-root/test/...
//depot/app/relX/...	//client-root/prod/...

The problem is, when I log in as APP I've set up a couple of DCL command
files to configure the environment for either TEST or PROD, within which I
define the the logical APP$ROOT as follows (when configuring for TEST):

define /nolog/trans=concealed APP$ROOT DISK$USER:[APP.TEST]
define /nolog APP$HOME APP$ROOT:[000000]
...etc etc...

This makes it easy to maintain the directory structures by referring to
subdirectories of the application simply using 'set def APP$ROOT:[PROC]'
independent of the current configuration selected. However, this brings me a
problem when using the perforce client: If a perform a 'set def
APP$ROOT:[PROC]', which refers to DISK$USER:[APP.TEST.PROC] when configured
for TEST mode and then perform e.g. 'p4 edit source_file.for', I get an
error indicating that the client directory is not mapped (sorry, I don't
remember the exact error message and the Alpha's are a floor down from
here). Naturally the perforce client does not understand that
APP$ROOT:[PROC] is actually a subdirecory of DISK$USER:[APP].

Has anyone else had a similar experience, and if so - how do you work around
it. I guess I could have separate client specifications depending on
configuration, or refer to all directories as e.g.
'DISK$USER:[APP.TEST.PROC]source_file.for'. How do you VMS users out there
handle this? All advice is welcome.


Regards // Johan


Oh yes, another thing: Is there any simpler way of adding a source code tree
using wildcards than (e.g.):

pipe DIR/NOTRAIL/NOHEAD/SELECT=FILE=NOVER [...]*.for; | p4 -x - add

(there seems to be a 'problem' with wildcard expansion under OpenVMS)