| Previous | Contents | Index |
[V3.0]
The Cobol MMS generator has been enhanced to allow a logical name to be used for a copy library. SysWorks performs one level of logical name translation in order to determine the actual location of the copy library for dependency purposes.
[V2.6]
The Cobol MMS generator has been enhanced to allow for transitive dependencies in copy statements. For example, if a copy file includes a call statement, the MMS scripts will ensure that the called routine will be compiled before any image using the Cobol program is linked.
There is a new MMS generator for Cobol and DECforms copy files and
libraries.. By default, the file type for these copy files is .TXT. The
alternative file type is .LIB.
2.10.11 DECdocument
[V3.2]
The MMS generator for DECdocument now detects the presence of <CONTENTS_FILE> and <INDEX_FILE> tags in order to control the addition of /CONTENTS and /INDEX qualifiers to the DOCUMENT command. This eliminates problems if a document which SysWorks previously expected to have a contents section and an index not having either or both. Note that this feature only applies to .SDML sources, not .SDML_INC include files. Thus, the <CONTENTS_FILE> and <INDEX_FILE> tags must be placed in the main .SDML source.
At this time, the COMPILE command continues to assume that certain document types have both contents and index.
[V2.6-1]
The MMS generator for DECdocument now uses the SysWorks design files and places them in the dependency list for each document.
[V2.6]
There is a new MMS generator variant for DECdocument sources with a file type of .SDML. Table 2-9 lists the targets for which dependencies will be created based on the end of the filename.
| File Name Suffix | Target File Types |
|---|---|
| _CVR | .PS, .TXT |
| _GDE | .DECW$BOOK, .PS, .TXT |
| _HLP | .HLP, applHLP.HLB |
| _REF | .DECW$BOOK, .PS |
All the targets will be placed in the applications documentation
directory.
2.10.12 DECdocument Graphics
[V3.0]
There is a new MMS generator for DECdocument graphics objects with a
file type of .GRA.
2.10.13 DECforms
[V3.1]
The DECforms MMS generator no longer defines depenencies on fields
within records in response to the field is clause. The
dependency is now on the record structure as a whole. This forces a
recompilation whenever the record changes rather than just the field,
which produces a more consistent build.
2.10.14 DECforms
[V2.6]
The DECforms MMS generator has been enhanced to allow for transitive
dependencies in copy statements. For example, if a copy file includes a
call statement, the MMS scripts will ensure that the called routine
will be compiled before any image using the DECforms form is linked.
2.10.15 Linker
[V3.1]
The %NODEBUG command indicates that this image is always linked /NODEBUG/NOTRACEBACK even when the /DEBUG or /TRACEBACK qualifier is used with the BUILD or COMPILE command.
The MMS generator for Linker options files now interprets some commands within comments to control the way in which an image is linked (similar to the %APPEND ability within DCL command procedure sources).
The %APPEND command indicates that an additional Linker options file should be included in the LINK command. This is useful when different syntax or options are used for Alpha and VAX images. For example, FIN_MAIN-ALPHA.OPT and FIN_MAIN-VAX.OPT might each have a set of separate options, but also include a %APPEND FIN_MAIN_COMMON.OPT_INC command which causes the MMS script to contain a syntax similar to:
$(link) FIN_LIB_DIR:FIN_MAIN.OPT/options,-
FIN_WRK_DIR:FIN_MAIN_COMMON.OPT_INC/options
|
Note that the Linker main source comes from the library directory since the original source has an architecture specific suffix which causes an unsuffixed copy to be made in the library directory.
There is a new feature in the MMS generator for Linker options files.
If the filename of the image ends in the suffix TOOLS, the image is
always linked /NODEBUG/NOTRACEBACK.
2.10.16 Macro
[V2.6]
The Macro MMS generator now differentiates between Macro sources which
generate code and those which purely define macros and symbols. If the
file name of a Macro source ends with _MAC, it is assumed to only
contain macros. Each macro within such a source which contains a
$defini directive, is assumed to define symbols. The resultant
MMS script reflects these attributes.
2.10.17 Pascal
[V2.6]
There is a new MMS generator variant for Pascal sources with a file
type of .PAS.
2.10.18 Linker
[V2.5-2]
The MMS generator for Linker options files has been enhanced.
2.11 Command Procedures
This section briefly describes the command procedures with modified
actions in SysWorks.
2.11.1 SYLOGIN.COM
[V2.6-1]
The SysWorks SYLOGIN.COM no longer executes a REPLY/ENABLE for
processes which are interactive, have a terminal (excluding DECwindows
terminals) as their input stream as posess the OPER or SETPRV privilege
as a default or authorised privilege.
2.12 DECwindows
This section briefly describes the modified DECwindows features
provided by SysWorks.
2.12.1 DECwindows Utilities Pulldown Menu
[V2.6]
The DECwindows Utilities pulldown menu will now include POSIX (POSIX
style), POSIX (OpenVMS style) and/or VUIT entries where appropriate.
2.12.2 SysWorks Manage Pulldown Menu
[V2.6]
The SysWorks Manage pulldown menu now has fewer items on it. Many items
now display a menu consisting only of other menus.
2.12.3 CPU Load and Eyes
[V2.5-2]
The CPU Load and Eyes items have been moved from the Backgrounds menu
to the Utilities menu.
2.12.4 DECwindows/Motif
[V2.5]
At this time only V1.0 of Motif should be used with SysWorks. There
have been significant problems when advanced SysWorks V2.5 and DECset
V11 menus and item lists have been used with Motif V1.2.
2.12.5 .DOC and .DOC_STYLE File Types
[V2.5]
The .DOC and .DOC_STYLE mouse button three file type handling has been
extended to support most actions that might be required from such a
file type.
2.13 Miscellaneous
This section briefly describes miscellaneous enhancements provided in
SysWorks.
2.13.1 SWDEV_VERY_OLD_FILE.TXT
[V2.6-1]
A new file has been provided with SysWorks which has very old creation
and modification dates of 01-Jan-1900. It is used by SysWorks as a
universal MMS source.
2.13.2 Message Symbol Code Prefix Change
[V3.0]
All SysWorks message symbols now start with a prefix of SWRK__.
2.13.3 Display of messages in hook files
[V2.5]
In previous versions of SysWorks, the various user and application hook files (eg. ENTER.COM, EXIT.COM and HOME.COM) displayed their own 'Executing ...' messages. These are now displayed by the various SysWorks command such as APPLICATION and HOME. In a future release of SysWorks this display will be controlled by a context variable (i.e symbol, logical name or SysWorks variable). For the time being, they will always be displayed.
As a result, users and developers should remove these messages from the hook procedures.
This chapter briefly descibes the problems with SysWorks which have
been fixed.
3.1 Commands
This section briefly descibes problems with commands which have been
fixed in SysWorks.
3.1.1 Many Commands
Many commands use the SWRK_EXTENDED_FILE_SEARCH routine which has had
the handling of /BEFORE and /SINCE fixed. Therefore all
SysWorkstm commands which use /BEFORE and /SINCE have
consequentially been fixed.
3.1.2 ACCEPT
[V3.2]
The ACCEPT command failed when the cursor was not at the end of the input when a terminator was pressed.
This has been fixed.
3.1.3 CONTEXT
[V2.6-1]
The CONTEXT command will attempt to create the appropriate logical name table when moving to a new context and the logical name table is not present. In previous versions of SysWorks if the user had privileges, the logical name table would be created in the system logical name table, but without the ACL necessary for other users of the context to have access.
This has been fixed by always creating such a logical name table in the process logical name table.
In a future version of SysWorks, all valid users of a context will be
able to create a system wide logical name table with the appropriate
ACL. This will improve login times considerably and give public
installation sites the same logical name table abilities as system and
turnkey installations.
3.1.4 DEVTOOLS
This section briefly describes problems with the DEVTOOLS utility which
have been fixed.
3.1.4.1 CMS CREATE ELEMENT
[V2.6-1]
The DEVTOOLS CMS CREATE ELEMENT command did not behave correctly when the element existed in the CMS library without a generation being a member of the environment or versions class.
This has been fixed.
3.1.4.2 CMS DELETE ELEMENT/[NO]CONFIRM
[V2.6]
The /[NO]CONFIRM qualifier is now correctly supported by the DEVTOOLS
CMS DELETE GENERATION command. This makes the output from a DEVTOOLS
DIFFERENCES/DATES (i.e. COMPARE) command work properly.
3.1.4.3 CMS FETCH
[V2.6-1]
The DEVTOOLS CMS RESERVE command did not behave correctly when attempting to reserve a generation which needed promotion.
This has been fixed.
3.1.4.4 CMS INSERT GENERATION
[V3.3]
The DEVTOOLS CMS INSERT GENERATION command didn't insert any
generations in a list when any generation wasn't found. The command now
correctly reports errors but still inserts generations where possible.
3.1.4.5 CMS REPLACE
[V2.6-1]
The DEVTOOLS CMS REPLACE command did not insert the new generation into the class specified by appl_CMS_PATH when use of the latest generation was indicated for the path (i.e. the path did not end with a plus sign).
This has been fixed.
The DEVTOOLS CMS REPLACE command failed to update the application
environment class when the translation of the
appl_CMS_GENERATION logical name did not include a trailing
plus which indicated that generations from the indicated class should
be used rather than the latest generations from the class. This has now
been fixed.
3.1.4.6 CMS RESERVE
[V3.3]
The DEVTOOLS RESERVE command wouldn't reserve a generation which needed promotion along its main line of descent when that generation didn't have a variant and the default for the reservation context did. A generation could be reserved in such a situation because a subsequent replace would have created a variant generation rather than a conflicting newer generation in the same line of descent.
The command will now reserve a generation in these circumstances.
3.1.4.7 CONVERT/GENERATE
[V3.2]
The DEVTOOLS CONVERT/GENERATE command caused an image failure when attempting to open a file for which the user did not have read access.
This has been fixed. An appropriate error message is now reported.
3.1.4.8 DIFFERENCES/DATES
[V2.6-1]
The DEVTOOLS DIFFERENCES/DATES command has problems when the /MERGE qualifier was used and there was no generation in the target class.
This has been fixed.
3.1.4.9 DIFFERENCES/DATES
[V2.5-1]
Some combinations of comparing a directory with a CMS library and
comparing two CMS libraries did not function properly. These have been
fixed.
3.1.5 CHGCTL
[V2.5-1]
Various CHGCTL sub-commands performed actions in application
environment contexts. When these commands were performed the default
directory was the users runtime directory rather than the users work
directory. This has now been fixed.
3.2 Menus
[V2.6-1]
When a SysWorks menu has more entries than can be displayed on the screen at one time, the menu is paged and supports the [Prev] and [Next] keys for navigation.
In earlier versions of SysWorks, this feature did not work properly.
This has been fixed.
3.3 Routines
The following routines have had problems fixed.
3.3.1 SWRK_HANDLE_QUALIFIERS
[V3.3]
This routine didn't provide or handle a default date value. This has
now been fixed.
3.3.2 SWRK_MOVE_FILE
[V3.3]
This routine didn't delete the input file when necessary if there
wasn't an explicit version. Also, when a copy was required, the output
file parse could fail on the second file. These problems have now been
fixed.
3.4 Tasks
This section briefly describes problems with tasks which have been
fixed in SysWorks.
3.4.1 Rename a disk volume
[V2.6]
The Rename a disk volume task failed when attempting to rename a non clusterwide disk volume from one of the computer nodes on which it is mounted when that computer node was not a cluster master computer node.
This has been fixed by allowing any computer node on which the disk is
mounted to rename the disk volume.
3.4.2 Merge maintenance into development
[V2.5-2]
Various problems with the Merge maintenance into development task have
been fixed.
3.5 MMS Generators
This section briefly describes problems with the SysWorks MMS generators which have been fixed. [V3.1]
3.5.1 ACMS Menu Definition
[V3.1]
The MMS generator now correctly parses menu is
cdd_path where the cdd_path starts with
a non symbol constituent character.
3.5.2 CDD/Repository
Various MMS generators (such as ACMS) which used the CDD had problems
when the CDD path started with a non symbolic character. These
generators should now generate the correct syntax.
3.5.3 CDD/Repository
[V3.1]
The MMS generator now correctly parses computed by clauses on field
definitions which include arithmetic and string operators, numeric or
string literals and parentheses.
3.5.4 Cobol
[V2.6-1]
The MMS generator now accepts single quotes as string bound in the same ways as double quotes.
The MMS generator now make dependencies on external (i.e. in another application) copy libraries use SWDEV_SFT_DIR:SWDEV_VERY_OLD_FILE.TXT as the source for the item. This file has a date which makes it older than any normal source so that no attempt is made to update the external copy library.
It also now accepts the copy ... of ... syntax as well as
copy ... in ....
3.5.5 DECforms
[V3.2]
The MMS generator now correctly handles copy statements which have the
from or in clauses on a separate line to the initial
copy statement.
3.5.6 DECforms
[V2.6-1]
The MMS generator now accepts single quotes as string bound in the same ways as double quotes.
The MMS generator now make dependencies on external copy libraries in
the same way as the Cobol MMS generator (see above for details).
3.5.7 ACMS Application
[V2.6]
If the server control attributes contained clauses before the server name in ... clause, the generator did not generate the correct dependency.
This has been fixed.
3.5.8 C
[V2.6]
If the main() routine had a prototype, the generator created a non-main style of dependencies.
This has been fixed.
3.5.9 Cobol
[V2.6]
If a call statement contained a space in the called routine name, this space appeared in the generated MMS script. This problem has been fixed.
If there were any complete strings (i.e. test between two double
quotes) before the call statement, the generator did not generate a
dependency. This problem has been fixed.
3.5.10 TDMS Request Library
[V2.6]
The use of .TAG_EP and .TAG_CDD was incorrect. This was left over from
when the generated MMS script attempted to distinguish bewteen when the
request library source needed to be replaced versus when it only needed
to be rebuilt. Since V2.5 of SysWorks, this distinctions has not been
made i.e. when either the request library source or the source of any
its requests was changed, the request library is both replaced and
built. This problem has been fixed.
3.5.11 CDO
[V2.5-2]
The MMS generator for CDO source file types has been enhanced to
support the use of fields outside the application.
3.5.12 DECforms
[V2.5-1]
The DECforms field is syntax was incorrectly interpreted by the MMS generator.
This has now been fixed.
3.5.13 TDMS Request Library
[V2.5-1]
3.5.14 C
[V2.4-3]
The MMS generator for the C, CXX, H, HXX, RC and SC source file types had several problems with data enclosed in quotes appearing like C code and also problems with outer level function recognition.
These have been fixed.
3.6 Command Procedures
This section briefly describes the command procedures fixed in SysWorks.
3.6.1 SWDEV_CVT_RDB_TO.COM
[V2.6-1]
This command procedure has a number of problems related to extended syntax in databases created by RDO rather than SQL.
These have now been fixed.
3.7 Miscellaneous
This section briefly describes miscellaneous problems which have been
fixed in SysWorks.
3.7.1 REPLY/ENABLE
[V2.6-1]
Earlier versions of SysWorks enabled OPCOM messages (i.e a REPLY/ENABLE
command was issued) for users with the OPERATOR
privilege. This feature is disabled for publis installations.
3.7.2 LSEDIT Buffer Initialization
[V2.4-3]
There was a problem when EVE or LSEDIT were started as a sub-process for the first time in a job which resulted in the $MAIN buffer being displayed rather than a specified file.
This has been fixed.
3.7.3 LSEDIT Initialization Files
[V2.4-3]
There was a problem when LSEDIT was started under DECwindows that resulted in the temporary initialization file remaining after LSEDIT had been initialized, and sometimes even after it had finished.
| Previous | Next | Contents | Index |