3.8 Commands
Three command interfaces are used to control sources. These
are:
.
CMS
.
SRCCTL (minimum abbreviation SRC)
.
DEVTOOLS CMS (minimum abbreviation DEV CMS)
The last two are used to act as a front end for CMS. See
Table 3-3 for a list of CMS commands and the front ends
which will accept them.
If the SysWorks Developer CMS front end (SRCCTL or
DEVTOOLS CMS) is used, the appl _CMS_PATH and appl _
CMS_VARIANT logical names provide defaults for use with
the /PATH qualifier. The /PATH qualifier is not a CMS
qualifier, rather it is an extension provided by SysWorks to
element based CMS commands such as CREATE ELEMENT
to indicate that the element is to be placed in the indicated
class after being created in the CMS library.
By default, a command which supports the /PATH qualifier
will, if the qualifier is not specified, default to the equivalence
of the appl _CMS_PATH logical name.
By default, a command which supports the /VARIANT
qualifier will, if the qualifier is not specified, default to the
equivalence of the appl _CMS_VARIANT.
The SRCCTL method supplies a menu based front end which
ultimately uses the DEVTOOLS CMS command to per-
form the actual operation. If the SRCCTL command is
entered from DCL without any sub-command following or is
selected from the session manager Manage ) Sources pull-
down menu, its displays the menu illustrated in Figure 3-1
and prompts for a sub-command. If the SRCCTL com-
mand is followed by one of the sub-commands indicated in
Figure 3-1, the menu is not displayed and the sub-command
dialog is entered directly.
The DEVTOOLS CMS method is a foreign utility will a full
command line interface (i.e entering DEVTOOLS without
any sub-command causes a DEVTOOLS> prompt to appear).
At this time not all SRCCTL commands are fully supported
by DEVTOOLS CMS - some are still implemented by us-
ing CMS directly - so although DEVTOOLS CMS is faster,
SRCCTL is more complete. In a future version of SysWorks
Developer, the DEVTOOLS CMS command will support all
CMS commands and qualifiers.
Both of these front ends extend CMS by allowing lists of
elements and an indirect construction. For example, the
following command:
$ devtools cms reserve fin_main_prog.c,fin_other.c "Fix"
will reserve both elements. Also, the following command:
will reserve each of the files specified in T1.TXT. Another en-
hancement allows full file specifications to be given in place
of CMS element names. This becomes useful in the following
example:
$ search [-]*.com* old_sym/window=0/out=t1.txt
$ devtools cms reserve @t1 "Change OLD_SYM to NEW_SYM"
$ change *.com* old_sym new_sym/verify
In this example the search command with /WINDOW=0
produces only the file specifications of the files containing the
requested text. The output of this can then be fed into the
DEVTOOLS CMS RESERVE command, which will reserve
each of the elements which contain the text. The CHANGE
command will then change the text to a new value and dis-
play each of the lines thus changed in each file. Note the
use of the [-] construction in the SEARCH command. Given
a developers default directory will be of the form DISK_
envr :[ appl .WRK. user ], this construct results in searching the
common work directory, which would normally contain
copies of the appropriate generations (i.e. current or latest
from class) of all the elements associated with the application
environment's CMS class.
The following sub-sections describe the extra actions that the
front end command will perform above the base CMS op-
eration, and extra tasks provided by the SRCCTL front end.
They are presented in alphabetic order.
3.8.1 BUILD
One of the items on both the SRCCTL and VSNCTL menus
is BUILD. When selected, it asks a set of questions before
building the application's software. See Section 5.2 for a de-
scription of how BUILD works. It is also available from
DCL as a command. When used directly from DCL, the
BUILD command takes qualifiers much like any normal
DCL command. See the Command Dictionary or use HELP
BUILD for more details on using the BUILD command from
DCL.Intermediate Directories
3.8.2 CREATE
Examples
1.
$ srcctl report
Version [V2.0]: V1.0
Development environment [DEV]:
Development testing environment [DTST]:
Maintenance environment [MNT]:
Maintenance testing environment [MTST]:
Output [SYS$OUTPUT]:
Display (All/New/Unused) [All]: NEW,UNUSED
Execution (Batch/Detached/Online/Subprocess) [Batch]: ONLINE
This example generates a report listing elements which
are not in the release class or are not in any class. The
report is generated online.
3.8.10 RESERVE