SysWorks©

SysWorks
Command Reference Manual


Previous Contents Index


VSNCTL

Invokes the version control menu.

Format

VSNCTL [sub-command]

The following sections provide information about each of the tasks which can be selected from the version control menu.


VSNCTL BUILD

Invoke an application build. This is similar to the BUILD command, except that a series of questions are asked rather than qualifiers being used.

VSNCTL CHGCTL

Invokes the change control menu.

See CHGCTL for more details.


Format

VSNCTL CHGCTL


VSNCTL CLEANUP

Cleanup an application environment after a build.

Removes the generations from a development, maintenance or testing class, and deletes the files in the environment's library and work directories. If used with a testing environment, the environment's state is set to `unsafe'.

This task is valid in development, maintenance and testing environments.


VSNCTL COMPARE

Compare the source library with the work directory.

VSNCTL DBCOMPARE

Compare the compilation database with the runtime.

VSNCTL DEVELOP

Setup development environment.

Takes the generations associated with a released class, creates new generations of them, and inserts the new generations into a development class. Only valid when used from a development environment.

If the development environment has its own CMS library, it is recreated from the development class in the common CMS library.

Optionally, the new development environment may be built from source.


VSNCTL EMPTY

Empty an environment prior to a build.

Cleans out the source associated with an application environment. and optionally builds a clean copy of the application there from source (eg. BUILD/FROM_SOURCES).


VSNCTL MAINTAIN

Setup maintenance environment.

Takes the generations associated with a released class, creates variant generations of them, and inserts the new variant generations into a maintenance class. Only valid when used from a maintenance environment.

If the maintenance environment has its own CMS library, it is recreated from the maintenance class in the common CMS library.

Optionally, the new maintenance environment may be built from source.


VSNCTL MERGE

Merge maintenance into development.

VSNCTL RELEASE

Release test into production.

Takes the generations from a testing class and places them into a released class. Copies the kit saveset(s) from the testing environment into the kit area. Removes all generations from the associated test and development or maintenance classes. A testing environment may only be released when it is in a `safe' state i.e. after a BUILD/FROM_SOURCES.


Actions

The following actions are executed during a release:
  1. If SysWorks was installed as a public layered product, the source testing environment must be in a safe state (i.e. a successful build from sources was completed).
  2. The generations associated with the testing class (with a name of the format appl_envr) in the application common CMS library are replicated in the version class (with a name of the format appl_vrsn).

VSNCTL SPLIT

Takes the generations associated with a released class, creates new and variant generations of them, and inserts the new generations into a development, development testing, maintenance and maintenance testing classes. Only valid when used from a development or maintenance environment.

Optionally, the new development and maintenance environment may each be built from source.


Actions

The following actions are executed during a split:
  1. If SysWorks was installed as a public layered product, the development, development testing, maintenance and maintenance testing application environments are locked i.e. no other jobs may be initiated from within those environments.
  2. The source generations associated with the specified released version (with a name of the format appl_vrsn are migrated to the four environment classes (with names of the format appl_envr within the application common CMS library. This is achieved by reserving each generation, and replacing it twice, once in the mainline and once as a variant. The new mainline generations are inserted into the development and development testing classes. The new variant generations are inserted into the maintenance and maintenance testing classes.
  3. For each of the four environments which has its own CMS library, that library is deleted and a new CMS library is created with generations from the appropriate class within the application common CMS library.
  4. Build the application in development and maintenance environments. This is achieved using the BUILD/FROM_SOURCES/KITBLD or BUILD/FETCH/PHASE=ALL/KITBLD command (see BUILD for more details).
    If the build was not requested, the development and maintenance application environments work, library, dictionary, software and documentation directories will be out of synchronization with their sources. A build from source would be needed prior to any work or trials. This option is available from the SPLIT task or the BUILD command.
  5. If SysWorks was installed as a public layered product, each environment is unlocked after it is successfully built. If the build for an application environment failed, it remains locked, and needs to be explicitly unlocked before further jobs may be initiated.

VSNCTL SRCCTL

Invokes the source control menu and CMS front end.

See SRCCTL for more details.


Format

VSNCTL SRCCTL


VSNCTL TRIAL

Move from development or maintenance into testing.

Forces the latest generations from a development or maintenance class into a testing class in the CMS library. If the source development or maintenance enviromnent has its own CMS library, the latest generations are transferred from that library into the common CMS library.

After the target environment CMS library and class have been updated, a build is performed in the target testing environment.

This task is valid from development and maintenance environments.


Actions

The following actions are executed during a trial:
  1. If SysWorks was installed as a public layered product, the source and target application environments are locked i.e. no other jobs may be initiated.
  2. Check that the source and target CMS libraries and classes have no outstanding reservations. If there were any such reservations, an error is issued, both environments are unlocked, and the trial fails.
  3. Migrate the latest generations from the source CMS library and class to the target CMS library and class. This is achived using the DEVTOOLS COMPARE/DATES command (also abbreviated to COMPARE).
  4. If SysWorks was installed as a public layered product, the source environment is unlocked if the build was successful. If the build failed, it remains locked, and needs to be explicitly unlocked before further jobs may be initiated.
  5. Build the application in the target environment. This is achieved using the BUILD/PHASE=ALL/CMS command (see BUILD for more details).
    If the build was not requested, the target application environments work, library, dictionary, software and documentation directories will be out of synchronization with its sources. A build from source should be considered prior to releasing the version into production. This option is available from the TRIAL task or the BUILD command.
  6. If SysWorks was installed as a public layered product, the target environment is unlocked. If the build was from sources and produced no errors, the terget environment is marked as safe, a requirement for releasing it into production.

VSNCTL TSTCTL

Invokes the test control menu if DEC Test Manager (DTM) is present and licensed.

See TSTCTL for more details.


Format

VSNCTL TSTCTL


WHO

Displays information about processes.

Format

WHO


Qualifiers

/ITEMS=(item[,...])

Specifies the items to be displayed by the WHO utility. The following table lists the valid item codes:
ACCOUNT APTCNT ASTACT
ASTCNT ASTEN ASTLM
AUTHPRI AUTHPRIV BIOCNT
BIOLM BUFIO BYTCNT
BYTLM CASE_LOOKUP_IMAGE CASE_LOOKUP_PERM
CHAIN CLASSIFICATION CLINAME
CPULIM CPUTIM CPU_ID
CREATOR CREPRC_FLAGS CURPRIV
CURRENT_AFFINITY_MASK CURRENT_CAP_MASK CURRENT_USERCAP_MASK
DEADLOCK_WAIT DFPFC DFWSCNT
DIOCNT DIOLM DIRIO
EFCS EFCU EFWM
ENQCNT ENQLM EXCVEC
EXECTIM FAST_VP_SWITCH FILCNT
FILLM FINALEXC FREP0VA
FREP1VA FREPTECNT GETJPI_CONTROL_FLAGS
GPGCNT GRP HOME_RAD
IMAGECOUNT IMAGE_AUTHPRIV IMAGE_PERMPRIV
IMAGE_RIGHTS IMAGE_WORKPRIV IMAGNAME
IMAGPRIV INITIAL_THREAD_PID INSTALL_RIGHTS
INSTALL_RIGHTS_SIZE JOBPRCCNT JOBTYPE
KRNLTIM KT_COUNT LASTADR
LASTCTL LASTPCB LASTPCBFLD
LASTPHD LASTPHDFLD LAST_LOGIN_I
LAST_LOGIN_N LOGINTIM LOGIN_FAILURES
LOGIN_FLAGS MASTER_PID MAXDETACH
MAXJOBS MEM MODE
MSGMASK MULTITHREAD NODENAME
NODE_CSID NODE_VERSION ORG_BYTLM
OWNER P0_FIRST_FREE_VA_64 P1_FIRST_FREE_VA_64
P2_FIRST_FREE_VA_64 PAGEFLTS PAGFILCNT
PAGFILLOC PARSE_STYLE_IMAGE PARSE_STYLE_PERM
PERMANENT_AFFINITY_MASK PERMANENT_CAP_MASK PERMANENT_USERCAP_MASK
PERSONA_AUTHPRIV PERSONA_ID PERSONA_PERMPRIV
PERSONA_RIGHTS PERSONA_RIGHTS_SIZE PERSONA_WORKPRIV
PGFLQUOTA PHDFLAGS PID
POSIX_PGID POSIX_SID PPGCNT
PRCCNT PRCLM PRCNAM
PRI PRIB PROCESS_RIGHTS
PROCPRIV PROC_INDEX RIGHTSLIST
RIGHTS_SIZE RMSD6 RMS_DFLRL
RMS_DFMBC RMS_DFMBFIDX RMS_DFMBFREL
RMS_DFMBFSDK RMS_DFMBFSMT RMS_DFMBFSUR
RMS_DFNBC RMS_EXTEND_SIZE RMS_FILEPROT
RMS_HEURISTIC RMS_PROLOGUE RMS_QUERY_LOCK
SCHED_CLASS_NAME SCHED_POLICY SHRFILLM
SITESPEC SLOW_VP_SWITCH STATE
STS STS2 SUBSYSTEM_RIGHTS
SUBSYSTEM_RIGHTS_SIZE SUPRTIM SWPFILLOC
SYSTEM_RIGHTS SYSTEM_RIGHTS_SIZE TABLENAME
TERMINAL THREAD_INDEX TMBU
TOKEN TQCNT TQLM
TT_ACCPORNAM TT_PHYDEVNAM UAF_FLAGS
UIC UNITS USERNAME
USERTIM VIRTPEAK VOLUMES
VP_CONSUMER VP_CPUTIM WSAUTH
WSAUTHEXT WSEXTENT WSPEAK
WSQUOTA WSSIZE  

/OUTPUT[=output-file-spec]

/NOOUTPUT

Specifies the output file specification for the command.

By default, /OUTPUT=SYS$OUTPUT is assumed. The /NOOUTPUT qualifier means that no output will be produced by the command.


Examples

#1

$ WHO
      

This lists all processes in the cluster in a format similar to SHOW SYSTEM/CLUSTER.


Chapter 2
Convenience Command Reference

This chapter provides the reference information for the DCL convenience commands provided by SysWorkstm.


APPLICATION

Changes the process context to the specified application environment including executing appropriate DCL procedures.

Description

The APPLICATION convenience command is equivalent to:


      CONTEXT APPLICATION 

See CONTEXT for more details.


CHKBLD

Checks a BUILD log file for progress and errors. This convenience command is equivalent to:


$ SEARCH BUILD.LOG -W-,-E-,-F-,STARTING,TRACEBACK


CHKTRL

Checks a TRIAL log file for progress and errors. This convenience command is equivalent to:


$ SEARCH TRIAL.LOG -W-,-E-,-F-,STARTING,TRACEBACK


ENVIRONMENT

Changes the process context to the specified environment of the current application including executing appropriate DCL procedures.

Description

The ENVIRONMENT convenience command is equivalent to:


      CONTEXT ENVIRONMENT 

See CONTEXT for more details.


GROUP

Changes the process context to the specified group including executing appropriate DCL procedures.

Description

The GROUP convenience command is equivalent to:


      CONTEXT GROUP 

See CONTEXT for more details.


SC

Show context. Short for UTLTOOLS SHOW CONTEXT. See HELP UTLTOOLS SHOW CONTEXT for more details.

SDF

Set default, or when there is no argument, show default.

SE

Show the users current environment. Same as the Utilities=>Show Environment pulldown from DECwindows/Motif.

SM

Show all the users processes within the cluster.

SMC

Same as SM except runs continually until Control-Y is pressed or the window is stopped. Same as the Utilities=>Show Me pulldown from DECwindows/Motif.

SQ

Show all the users jobs (both batch and print). Same as the Utilities=>Show Jobs pulldown from DECwindows/Motif.

SQB

Show all the users batch jobs.

VERSION

Changes the process context to the specified version of the current application environment including executing appropriate DCL procedures.

Description

The VERSION convenience command is equivalent to:


      CONTEXT VERSION 

See CONTEXT for more details.


Previous Next Contents Index