SysWorks©

SysWorks V3.5
Release Notes


Previous Contents Index

The BUILD/PHASE=ALL no longer includes the KIT phase. The BUILD/KIT qualifier now provides this functionality.

The new BUILD/TIDY qualifier cleans up a developers specific areas by taking the following steps:

This qualifier should be used after a BUILD/COMMON is performed to remove unnecessary duplicate specific objects and targets.

2.4.3 BUILD and COMPILE

[V3.2]

The BUILD and CHANGE commands now support the /[NO]CROSS_REFERENCE qualifier for appropriate compilers and the Linker. Refer to the compiler and Linker documentation for details.

[V3.0]

The BUILD and CHANGE commands now support the /[NO]MACHINE, /[NO]MEMBER_ALIGNMENT and /[NO]OPTIMIZE qualifiers for compilers which support them.

The /DEBUG qualifier now defined a C macro by applying a /DEFINE=DEBUG=1 qualifier to C and C++ commands.

2.4.4 BUILD, CONTEXT APPLICATION and CONTEXT ENVIRONMENT

[V2.4-3]

These commands now support /COMMON and /SPECIFIC qualifiers to override the default scope when entering an application environment.

2.4.5 CHANGE

[V2.5]

The CHANGE command is now a convenience command for DEVTOOLS CHANGE rather than being a standalone utility.

2.4.6 CHGCTL

[V2.6]

There is a totally new change control system. The existing change control system is now known as the version control system (see VSNCTL below). This menu includes options to goto the source, testing and version control menus. This menu is available as Manage => Change from the session manager menu bar.

2.4.7 COMMON

[V2.4-3]

Sets the application environment to the common scope which will cause compilations and builds to occur in the shared directories.

2.4.8 COMPARE

[V2.5]

The COMPARE command is now a convenience command for DEVTOOLS DIFFERENCES/DATE.

2.4.9 CONTEXT

[V3.2]

The CONTEXT command now supports a RESET sub-command which resets the current context. This is useful to ensure that standard procedures such as EXIT.COM, LOGICALS.COM and ENTER.COM have been executed. It is used by the default BUILD SETUP phase if any of these procedures have been updated.

[V2.6-1]

When an application environment or group logical name table does not exist, the CONTEXT command no longer uses process privileges to create a system wide logival name table for an application environment or group. In a future release of SysWorks the CONTEXT command will always create system wide logical name tables for applications environments and groups. Until this time, process logical name tables will always be created.

[V2.5-1]

The new CONTEXT command supercedes the existing APPLICATION, ENVIRONMENT, GROUP, HOME and USER commands. These commands are now convenience commands based on the CONTEXT command. The summary of convenience commands based aroung the CONTEXT command includes:
Command Equivalence
APPLICATION CONTEXT APPLICATION app-cod env-cod [vsn-cod]
ENVIRONMENT CONTEXT ENVIRONMENT env-cod [vsn-cod]
GROUP CONTEXT GROUP grp-cod
HOME CONTEXT HOME
USER CONTEXT USER [usr-cod]
VERSION CONTEXT VERSION vsn-cod

2.4.10 CVTMMS

[V3.0]

The CVTMMS convenience command is now implemented using the following command:


 
    DEVTOOLS CONVERT/GENERATE/DEFAULT=TARGET=.MMS_INC. 

2.4.11 CVTMMS

[V2.5]

The CVTMMS convenience command converts a source into an MMS script.

2.4.12 CVTRDB

[V2.5]

The CVTRDB convenience command converts an Rdb/OpenVMS database into a set of sources.

2.4.13 DEC Rdb Precompiler Commands

[V2.4-3]

The following is now the list of Rdb/VMS precompiler commands:
Command Equivalence
RBAS $RDBPRE/BASIC
RCOB $RDBPRE/COBOL
RDMLC $RDML/CC
RDMLPAS $RDML/PASCAL
RFOR $RDBPRE/FORTRAN
SADA $SQL$PRE/ADA
SBAS $SQL$PRE/BASIC
SCC $SQL$PRE/CC
SCOB $SQL$PRE/COBOL
SFOR $SQL$PRE/FORTRAN
SPAS $SQL$PRE/PASCAL
SPLI $SQL$PRE/PLI

The RDBCOBOL command has been removed.

2.4.14 DIRTOOLS

[V3.2]

The DIRTOOLS utility is provided with SysWorks Administrator.

It supports the following specific commands:

2.4.15 DO

[V2.5-1]

The DO command has the following new qualifiers:

It no longer supports the following qualifiers:

2.4.16 DEVTOOLS

This section briefly describes new and modified sub-sommands of the DEVTOOLS command.

[V2.6]

A series of new commands has been added to the DEVTOOLS utility. These commands are used for invoking and controlling the invoking of standard layered product utilities. At this time, ACMS (ADU), CDD/Repository (CDO) and TDMS (RDU) are supported. Specifically they are designed to allow a subprocess running the layered product utility to be kept. This has the advantage of eliminating the access or bind time normally associated with running these utilities. This functionality is now used by the BUILD command, and greatly increases the speed of building when many of the actions involve one of the layered products.

The CMS commands which supported the /CLASS qualifier no longer do so. This functionality is achived using the /GENERATION qualifier. Furthermore /GENERATION qualifier now supports a search list of generations where appropriate.

[V2.5]

SysWorks V2.5 introduces the DEVTOOLS utility. This utility provides enhanced functionality for DCL commands, CMS and some command of its own.

A typical enhenced DCL command is DEVTOOLS COPY/NODUPLICATES which appends a set of files into one output file, but does not duplicate any of the files copied. This is useful if a search list is used so that files from later areas are not copied if a file from an earlier area has been copied. This is used in the creation of the appl_APPENDS.MMS and assists when this is being built in a developer specific area.

The CMS front end provides SRCCTL like functionality in an image rather than a command procedure. Note that not all of the functionality in SRCCTL or CMS itself is yet provided. In a future release of SysWorks the DEVTOOLS utility will provide a complete set of CMS commands including those which it does not enhance.

Specific DEVTOOLS commands include DEVTOOLS DIFFERENCES/DATES which is used by the BUILD/FETCH command to fetch generations in the CMS library which are newer than those in an application's work directory.

The DEVTOOLS utility also provides a command mode with command recall etc.

2.4.16.1 ADU

[V2.6]

The DEVTOOLS ADU[/KEEP] command invokes the ACMS ADU utility.

2.4.16.2 ATTACH

[V3.2]

The DEVTOOLS ATTACH command switches the users terminal to another process in a similar fashion to the ATTACH command in most Digital utilities.

2.4.16.3 CDO

[V2.6]

The DEVTOOLS CDO[/KEEP] command invokes the CDD/Repository CDO utility.

2.4.16.4 CMS FETCH

[V2.6-1]

The DEVTOOLS CMS FETCH command now supports the /MERGE qualifier. See HELP DEVTOOLS CMS FETCH /MERGE for details.

2.4.16.5 CMS PROMOTE

[V2.6]

There is a new DEVTOOLS CMS PROMOTE command for promoting a generation between a developers private class and an environments command class. See HELP DEVTOOLS CMS for full details on the supported sub-sommands and qualifiers.

2.4.16.6 CMS REPORT

[V2.6-1]

There is a new DEVTOOLS CMS REPORT command for generating a report about a CMS library. See HELP DEVTOOLS CMS REPORT for full details on the supported qualifiers.

2.4.16.7 CMS RESERVE

[V2.6-1]

The DEVTOOLS CMS RESERVE command now supports the /PROMOTION_CHECK qualifier. See HELP DEVTOOLS CMS RESERVE /PROMOTION_CHECK for details.

2.4.16.8 CMS SHOW GENERATION

[V3.3]

The DEVTOOLS CMS SHOW GENERATION command now supports the /ANCESTORS and /DESCENDANTS qualifiers. The /FORMAT qualifier now supports #T to indicate substitution of the generation creation date and time. See HELP DEVTOOLS CMS SHOW GENERATION for details.

2.4.16.9 CONVERT/GENERATE

[V3.2]

The DEVTOOLS CONVERT/GENERATE command now supports a /CHECK_SUBCONTEXT qualifier (which is assumed by default). This qualifier indicates whether to check that the context directory subcontext is valid (eg. the library directory exists). The REDUCE convenience command now includes /NOCHECK_SUBCONTEXT to allow its use outside an application environment.

[V3.0]

The DEVTOOLS CONVERT/GENERATE command is now implemented. This is primary used to generate MMS scripts from application sources. Most converters are now implemented as code rather than TECO or TPU scripts, which has significantly improved their performance.

2.4.16.10 DELETE

[V3.1]

The DEVTOOLS DELETE command now supports the /COMBINED qualifier. See HELP DEVTOOLS DELETE /COMBINED for details.

[V3.0]

The DEVTOOLS DELETE command now supports the /TIDY and /SUBCONTEXT qualifiers. See HELP DEVTOOLS DELETE /TIDY for details.

2.4.16.11 DIFFERENCES/DATES

[V3.1]

The DEVTOOLS DIFFERENCES/DATES command can now pass on the /COMBINED qualifier on the DEVTOOLS DELETE commands it generates.

[V3.0]

The DEVTOOLS DIFFERENCES/DATES command can now pass on the /TIDY qualifier on the DEVTOOLS DELETE commands it generates.

[V2.6]

The DEVTOOLS DIFFERENCES/DATES command now supports the /SINCE qualifier which specifies that only objects revised since the indicated time should be checked. This qualifier effictively applies only to the first parameter, and cannot be used with the /BOTH parameter.

2.4.16.12 RDU

[V2.6]

The DEVTOOLS RDU[/KEEP] command invokes the TDMS RDU utility.

2.4.16.13 SET UTILITY/KEEP

[V2.6]

Specifies that the indicated utility is to be operated in kept mode. Utilities supported include ADU, CDO and RDU.

2.4.16.14 SET UTILITY/NOKEEP

[V2.6]

Specifies that the indicated utility is not to be operated in kept mode. If the utility is currently kept, it is topped.

2.4.16.15 SHOW CONTEXT

[V3.2]

The DEVTOOLS SHOW CONTEXT command is a synonym for the UTLTOOLS SHOW COMMAND which displays the current context.

2.4.17 EDIT

[V2.5]

If the default editor is LSEDIT, there is no sub-process editor and there is a DECwindows LSEDIT running in the appropriate application environment, group or user context, an EDIT command from a terminal window will push any file requested for editing across to the DECwindows LSEDIT window, and restore and focus it.

Note that an EDIT command without a file specification will continue to either start or attach to a sub-process style editor.

2.4.18 FDU

[V2.4-3]

The FDU command has been modified so that all terminal and DECwindows DECterm users will not need to set their terminal to VT100 format before using FDU. The command now invokes a command procedure which sets the terminal type to VT100 before invoking FDU and returns it to its prior type after FDU is finished.

Note also that EDITing a .FRM file now invokes FDU.

2.4.19 LADCP and LASTCP

[V2.4-3]

The LADCP and LASTCP commands are now defined for system managers.

2.4.20 LOGOUT

[V2.4-3]

A LOGOUT command has been implemented which checks to see if there are any sub-processes present below the current process, and if so issues a warning message rather than logging the user out. This prevents accidental deletion of a kept editor subprocess.

2.4.21 MAILBOX/DELETE

[V3.0]

The mailbox utility now provides a MAILBOX/DELETE command which deletes a mailbox.

2.4.22 REDUCE

[V2.6-1]

The REDUCE commands ignores many new errors codes. Use the following command to determine the complete set:


$ TYPE SWDEV_SFT_DIR:SWDEV_CVT_LOG_TO_ERR_EXCEPTIONS.TXT

[V2.5]

The REDUCE command removes general, success and selected informational messages from a log file. This is useful in tracking down actual errors in a large log file. In a future release of SysWorks this functionality will be placed in the DEVTOOLS utility.

2.4.23 SC

[V3.2]

The SC convenience command is now defined as UTLTOOLS SHOW CONTEXT.

[V2.5-1]

The SC (SHOW CONTEXT) convenience command no longer displays the saved DO command context since the DO command no longer supports memory and default qualifiers.

2.4.24 SPECIFIC

[V2.4-3]

Sets the application environment to the specific scope which will cause compilations and builds to occur in the developer private work and runtime directories.

2.4.25 SRCCTL

[V2.6-1]

The source control menu now includes an options to generate a report about the CMS library. This option is a front end to the DEVTOOLS CMS REPORT command.

[V2.6]

The source control menu now includes options to goto the change, testing and version control menus.

This menu is now available as Manage => Sources from the session manager menu bar.

2.4.26 TSTCTL

[V2.6]

The testing control menu now includes options to goto the change, source and version control menus.

This menu is now available as Manage => Testing from the session manager menu bar.

2.4.27 UTLTOOLS

This section briefly describes new and modified sub-sommands of the UTLTOOLS command.

2.4.27.1 DEFINE

[V3.3]

The UTLTOOLS DEFINE commands now support the /[NO]QUOTE qualifier which controls whther equivalence strings are quoted in generated command files.

2.4.27.2 General

[V3.2]

The UTLTOOLS utility is provided with SysWorks Base. Although it was provided is previous version of SysWorks, it was only used internally. In this release, it has become a generally available utility and will eventually be used to replace the DEFxxx commands.

The UTLTOOLS command is now documented. See online HELP or the SysWorks Command Reference Manual for details. The following list provides a command summary:

2.4.28 VSNCTL

[V2.6]

The version control menu has the same functionality as the previous change control menu. This menu now includes options to goto the change, source and testing control menus.

It is now available as Manage => Versions from the session manager menu bar.

2.4.28.1 TRIAL

[V2.5]

There is now a question in the TRIAL dialog allowing the check on CMS reservations to be overridden.

2.4.29 WHO

[V3.2]

A full show process utility named WHO is now provided. See HELP WHO for details.

2.5 Menus

This section briefly describes the new and modified menus provided in SysWorks.

2.5.1 CHGCTL, SRCCTL and TSTCTL Menu Help

[V2.4-3]

The CHGCTL, SRCCTL and TSTCTL menus now have menu specific help when the HELP selection is specified. It is the same as HELP @SWDOCHLP xxxCTL, where xxx is CHG, SRC or TST.

2.5.2 Environment Registration Menu

[V2.6]

Various tasks on the environment registration menu have had an option requesting the permitted environment scopes. By default, the environment scope is inherited from the environment type. If the inherited value is EITHER, an alternative scope value such as COMMON or SPECIFIC may be entered when adding or modifying the details about an environment.

2.6 Tasks

This section briefly describes SysWorks tasks which have been modified.

2.6.1 Merge maintenance into development

[V2.4-2]

The Merge maintenance into development task now asks whether to override the CMS library check like the VSNCTL TRIAL task.

2.7 Logical Names

This section briefly describes the logical names added or removed in various versions of SysWorks.

2.7.1 appl_ACMS_REPLACE

[V2.4-3]

The new appl_ACMS_REPLACE logical name in the application logical name table is used to indicate that ACMS sources (i.e. applications, menus, task groups and tasks) contain ADU utility commands such as create or replace, and that SysWorks should not issue these commands. By default, SysWorks issues these commands.

2.7.2 appl_APPLICATIONS

[V2.4-3]

The new appl_APPLICATIONS logical name in the application logical name table is used to place ACMS application definitions in a specific dictionary directory rather than CDD$DEFAULT.

2.7.3 appl_CMS_CLASS

[V2.6]

The appl_CMS_CLASS logical names are no longer supported. These have been deprecated since V2.5 of SysWorks. The appl_CMS_PATH logical name should be used instead of appl_CMS_CLASS.

[V2.4-3]

The new appl_CMS_CLASS logical name in the application logical name table is used to control access to an applications common CMS library.

2.7.4 appl_CMS_GENERATION

[V2.6]

The appl_CMS_GENERATION logical names are no longer supported. These have been deprecated since V2.5 of SysWorks. The appl_CMS_PATH logical name should be used instead of appl_CMS_GENERATION.

[V2.5]

The new appl_CMS_GENERATION logical name in the application logical name table is used to control access to an applications common CMS library. For CMS commands which would logically use the /GENERATION qualifier (such as RESERVE), the DEVTOOLS utility will default to using this logical rather than the old appl_CMS_CLASS logical. If this logical is not present, the appl_CMS_CLASS logical is used with an appended "+", indicating that the latest generations of the class are to be used.


Previous Next Contents Index