Configuration
files - MultiUSE file (for PVCS Dimensions)
UD6/MultiUSE is March Hare's scripting mechanism for use
with PVCS Dimensions.
All
modern Configuration Management and Source Code Management
utilities provide some mechanism for users to be able to
'trigger' certain actions when events occur in the change
management system.
PVCS
Dimensions does this via a callable interface through low
level 'C' program code.
To
simplify the process of keeping the UD6 configuration files
in sync with the state of your PVCS Dimensions repository,
March Hare supply a pre-built DLL that performs the following
functions:
NOTE:
If any individual user requires simultaneous access to 2
different branches or versions of the source code they may
have to use usernames to distinguish the INUSE files, if
the branch cannot be uniquely determined by the combination
of the PVCS Product Id, Workset Id, Variant and PVCS Username.
A user can easily identify which PVCS User they wish to
'log in' as using the PVCS login dialog box on the client
machine.
Here
is a sample MULTIUSE file:
; Copyright 2000 March Hare Pty Ltd
;
; The location of this file is specified in the environment
; variable MULTIUSE, e.g.:
;
; SET MULTIUSE=c:\
;
+R¶¶PRODUCT:BRIDAL¶VARIANT:AAAA¶WORKSET:DEV¶¶c:\reference\bridal\aaaa\
+R¶¶PRODUCT:BRIDAL2¶VARIANT:AAAA¶WORKSET:DEV¶¶c:\reference\bridal2\aaaa\
+R¶¶PRODUCT:BRIDAL2¶¶WORKSET:DEV¶¶c:\reference\bridal2\other\
+I¶USER:ADMINISTRATOR¶PRODUCT:BRIDAL¶VARIANT:AAAA¶WORKSET:DEV¶¶c:\sandpit\cfg\adm-brd-a.inuse
+W¶USER:ADMINISTRATOR¶PRODUCT:BRIDAL¶VARIANT:AAAA¶WORKSET:DEV¶¶c:\sandpit\admin\bridal\aaaa\
+I¶¶PRODUCT:BRIDAL¶VARIANT:AAAA¶WORKSET:DEV¶¶c:\sandpit\cfg\dev-brd-a.inuse
+W¶¶PRODUCT:BRIDAL¶VARIANT:AAAA¶WORKSET:DEV¶¶c:\sandpit\dev\bridal\aaaa\
+I¶¶PRODUCT:BRIDAL¶¶WORKSET:DEV¶¶c:\sandpit\cfg\dev-brd-other.inuse
+W¶¶PRODUCT:BRIDAL¶¶WORKSET:DEV¶¶c:\sandpit\dev\bridal\other\
1st Field
R=Reference
|
Specifies
the root directory for the read-only copy of the source
code, with that product name, and variation.
|
I=Inuse
File |
Specifies
the name of the inuse file for that product name and
variation. |
W=Sandbox |
Optionally
specifies the root directory of the read-write copies
of source code that has been 'checked out'. |
NOTE:
'W' records are optional, in which case the root is assumed
to be the current working directory of the Uniface development
environment.
PRODUCT
or VARIATION may optionally be left blank which will refer
to ALL PRODUCTS or VARIATIONS. This is different to PRODUCT=
or VARIATION= which mean that the name of the Product is
"" or the name of the VARIATION is "".
2nd
Field
Username
or leave blank for any user.
3rd/4th/5th
Field
Some
useful identifier.
6th
Field
This
field can be used to pass additional options to the add2list/del2list
command, (only valid on 'I' type records).
Example:
+I¶USER:User1¶PRODUCT:PROD1¶VARIANT:VER4-SRC¶WORKSET:DEV¶-rC:\src¶c:\src\config\user1.inuse
7th
Field
INUSE
file (for I records)
Reference root directory (for R records)
Sandbox root directory (for W records)
This
topic will is covered again in the article Configure
MULTIUSE in the section 'Taking
Control'..
PVCS
Dimensions does this via a callable interface through low
level 'C' program code.
Configuration
files
|
- |
usys.asn
file |
|
- |
Joins
file |
|
- |
MultiUSE
file |
PVCS
Dimensions & UD6 guide