Order Number: SWRK-RN-351
This manual briefly describes the new and modified features provided in SysWorks V3.5.
Revision/Update Information: This manual supercedes the SysWorks V3.4-1 Release Notes
Operating System and Version:
OpenVMS VAX V7.2 or higher;
OpenVMS Alpha V7.2 or higher;
DECwindows/Motif V1.2-3 or higher
Software Version: SysWorks V3.5
Printed in Australia
The following are trademarks of Compaq Computer Corporation: ACMS, ALL-IN-1, AXP, BASIC, Bookreader, CDA, CI, DATATRIEVE, DBMS, DDIF, DEC, DEC ACCESSWORKS, DEC Ada, DEC C, DEC Fortran, DEC Pascal, DECdecision, DECdesign, DECdirect, DECdns, DECdocument, DECdtm, DECforms, DECimage, DECintact, DECmigrate, DECnet, DECnet/OSI, DECset, DECsupport, DECtp, DECwindows, Digital, DTIF, EDT, HSC, MASSBUS, MicroVAX, MicroVAX II, MSCP, OpenVMS, OpenVMS Cluster, RA, StorageWorks, TA, TMSCP, TURBOchannel, ULTRIX, VAX, VAX C, VAX MACRO, VAX-11/780, VAXcluster, VAXELN, VAXft, VAXstation, VIDA, VMS, VMScluster, VT100, and the DIGITAL logo.
PostScript is a registered trademark of Adobe Systems Inc.
Motif is a registered trademark of Open Software Foundation, Inc.
Oracle is a registered trademark, and Oracle CDD/Repository, Oracle CODASYL DBMS, Oracle Expert, Oracle Rally, Oracle Rdb, Oracle Trace and Rdb7 are trademarks of Oracle Corporation.
OSI is a registered trademark of CA Management, Inc
All other trademarks and registered trademarks are the property of their respective holders.
This document was prepared using DECdocument V3.3.
| Contents | Index |
We welcome your comments on this manual or any SysWorks manual. If you have suggestions for improvements or find any errors, please indicate the chapter, section and page number (if available). Your input is valuable in improving future releases of our documentation.
You can send comments to us in the following ways:
SysWorks Corpita Pty Ltd 15 Bedford Street Collingwood VIC 3066 Australia |
This manual provides release notes for SysWorks V3.5.
This manual is intended for general circulation to all SysWorks installers and users.
The following conventions are used in this document:
| Conventions | Description |
|---|---|
| [Ctrl/X] | A sequence such as [Ctrl/X] indicates that you must hold down the key labeled [Ctrl] while you press another key or a pointing device button. |
| [] |
In format descriptions, brackets indicate that whatever is enclosed is
optional; you can select none, one or all of the choices.
In system prompts indicates the default value which will be assumed if the Return key is pressed without first entering a value. |
| {} | In format descriptions, braces surround a required choice of options; you must choose one of the options listed. |
| | | In format descriptions, vertical bars separate the options. If the options are enclosed in brackets (i.e. []) you can select none, one or all of the choices. If the options are enclosed in braces (i.e. {}) you must choose one of the options listed. |
| () | In system prompts, parenthesis indicate the list of values one of which may be entered. The values are separated by a forward slash "/" |
| ... | An elipsis indicates that a value within a range may be chosen or a syntax repeated. A range may be indicated by a pair of end values, or an end value and an end keyword. For example Disk quota (0..unlimited) indicates that the keyword unlimited may be used to represent the highest possible disk quota. |
| italic text | Italicized words and letters indicate that you should substitute a word or value of your choice. |
| UPPERCASE TEXT | Uppercase letters indicate the name of a command or routine. |
| monospace text | Normal monospace text indicates system prompts and output. |
| bold monospace text | Bold monospace text indicates user responses to system prompts. |
| bold monospace italic text | Bold monospace italic text indicates user responses to system prompts which need approriate value substitution. |
| mouse | The term mouse is used to refer to any pointing device such as a mouse, a puck or a stylus. |
| MB1, MB2, MB3 | MB1 indicates the left mouse button, MB2 indicates the middle mouse button, and MB3 indicates the right mouse button. (The buttons can be redefined by the user.) |
Unless otherwise noted, all numeric values are represented in decimal notation.
1.1 Summary of Changes for V3.5
The following list provides a summary of changes made for V3.5:
The following list provides a summary of changes made for V3.4:
The following list provides a summary of changes made for V3.3:
The following list provides a summary of changes made for V3.2:
This chapter briefly descibes the new and modified features in SysWorks.
2.1 Documentation Updates
[V3.5]
A new document SWRK035.RELEASE_NOTES may be found in SWRK_DOC_DIR: and in SYS$HELP. These release notes now include a summary of changes for the current version in addition to the details of changes since V2.4-3.
Revised on-line help documents most SysWorks supported commands. Use HELP @SWDOCHLP for details.
SysWorks manuals are available using BNU and/or the Bookreader. If SysWorks Administrator is installed, a BNU/Bookreader replication utility is provided which scans BNU or Bookreader volumes and creates a master index in the SWADM_SFT_DIR: directory. This facility is used when SysWorks first mounts a BNU or Bookreader disk volume.
In light if this facility, there are now three ways to manage BNU/Bookreader access. These are:
In the traditional method, DECW$BOOK and DECW$BOOKSHELF logical names should be defined in the system startup procedures using commands such as:
$ DEFINE/SYSTEM DECW$BOOK - DISK$VAXDOCSEP961:[DECW$BOOK],- DISK$VAXDOCSEP962:[DECW$BOOK],- DISK$VAXDOCSEP963:[DECW$BOOK],- DISK$VAXDOCSEP963:[DECW$BOOK],- SWRK_DOC_DIR:,- SWEXA_DOC_DIR:,- SWPUB_DOC_DIR:,- SYS$SYSROOT:[DECW$BOOK] $ DEFINE/SYSTEM DECW$BOOKSHELF - DISK$VAXDOCSEP961:[DECW$BOOK]LIBRARY.DECW$BOOKSHELF;,- SWRK_DOC_DIR:LIBRARY.DECW$BOOKSHELF;,- SYS$SYSROOT:[DECW$BOOK]LIBRARY.DECW$BOOKSHELF; |
In the above example, the logical names DISK$VAXDOCSEP96n are the standard default logical names defined by a MOUNT command.
Note also that the trailing semi-colons on the DECW$BOOKSHELF
equivalences are required to stop the bookreader opening multiple
copies of the same library. Typically these commands may be placed in
the SWRK_LCL_DIR:site_PRE_STARTUP.COM command procedure.
2.1.2 Replicator Method
If SysWorks documentation replicator is used manually (either by using SWADM_SFT_DIR:SWADM_IMPORT_DISK_TAPE_INFO.COM or the DIRTOOLS DOCUMENTATION/REPLICATE command), the DECW$BOOK and DECW$BOOKSHELF logical names should be defined in the system startup procedures using commands such as:
$ DEFINE/SYSTEM DECW$BOOK - SWRK_DOC_DIR:,- SWEXA_DOC_DIR:,- SWPUB_DOC_DIR:,- SYS$SYSROOT:[DECW$BOOK] $ DEFINE/SYSTEM DECW$BOOKSHELF - SWADM_DAT_DIR:LIBRARY.DECW$BOOKSHELF;,- SWRK_DOC_DIR:LIBRARY.DECW$BOOKSHELF;,- SYS$SYSROOT:[DECW$BOOK]LIBRARY.DECW$BOOKSHELF; |
Note that using SysWorks at the turnkey level should generate the same
results as the above commands.
2.2 Concepts
This section briefly describes new and modified concepts provided in
SysWorks.
2.2.1 Alternative Installation Directory
[V2.5-1]
If SysWorks is installed at the public level, the installation
procedure will ask for an installation device. By default,
SYS$SYSDEVICE: is assumed which results in SysWorks being placed in the
standard system tree. If another disk is specified, the appropriate
directory structures are placed in the root of the indicated disk.
2.2.2 Application Environment Scope
[V2.4-3]
SysWorks now supports a private versus common scope for compilations
and builds. When an application environment scope is common, all
developers share the standard directories such as work, library and
software. When the environment is scope private, each developers
actions take place in their work and runtime directories. This is
achieved by making the logical names associated with the standard
directories into search lists, with the developers work or runtime
directory as the first equivalence, and the standard shared directory
as the second.
2.2.3 Error Handling
[V3.1]
SysWorks has significantly improved internal error handling. All crashes now generate a log file in addition to any output to the normal SYS$ERROR and SYS$OUTPUT files. The log file name is based on the image in which the error occurred. For example, if a DEVTOOLS command failed, a log file of the name SWDEV_DEVTOOLS.LOG would be created. If a problem occured within LSEDIT, an LSEDIT.LOG file would be created.
The log file output now includes a call frame dump for Alpha in addition to VAX. Earlier versions only did this on VAX. Note that this call frame dump is generated even if the image is linked /NODEBUG/NOTRACEBACK.
Applications can use these facilities within SysWorks by calling
SWRK_ESTABLISH
to establish a universal exception handler. This requires SysWorks to
be present on production systems. The SysWorks Base product includes
these facilities.
2.2.4 HTTP File Types
[V3.2]
SysWorks now supports various HTTP file types. Although these were supported using the _CPY and/or _SRC file type suffices, in practice use of these file types makes it difficult to develop HTTP pages. The file types currently supported include:
SysWorks supports using these file types for both source and target
files.
2.2.5 Installation Level
[V3.0]
SysWorks now supports three installation levels. These are:
SysWorks no longer supports the private installation level introduced
in V2.4-3. See the SysWorks Installation Guide for more details.
2.2.6 Library Module Deletion
[V3.0]
SysWorks now deletes modules in object, shareable image and text
libraries in addition to files as a consequence of appropriate /TIDY
qualifiers. See notes on the BUILD, DEVTOOLS CMS FETCH, DEVTOOLS CMS
RESERVE and DEVTOOLS DELETE commands for details.
2.2.7 Message Help Support
[V3.2]
SysWorks now supports HELP/MESSAGE sources and data files. The file types used are .HLPMSG and .HLPMSG$DATA respectively. Because the .MSGHLP$DATA file type is not an OpenVMS library, and hence MMS cannot directly support it, an intermediate tag file of file type .TAG_MSGHLP is used to indicate to MMS that the .MSGHLP source has been inserted into the .MSGHLP$DATA file.
An application logical name of the form appl_MSGHLP_LIB must be used to identify the application message help data file. The SysWorks convention for the specification of this file (i.e. the equivalence of the logical name) is:
appl_DOC_DIR:applMSGHLP.MSGHLP$DATA.
|
The SysWorks message help data file is now incorporated into the system
message help search list MSGHLP$LIBRARY
. If this logical is not defined, SysWorks defines it as a search list
of SYS$HELP:MSGHLP$LIBRARY.MSGHLP$DATA and SWRK_MSGHLP_LIB. If it is
already defined and SWRK_MSGHLP_LIB is not yet included, SysWorks adds
SWRK_MSGHLP_LIB as the last item in the search list.
2.2.8 Message Logging
[V3.2]
SysWorks now uses a utility to display messages from DCL command procedures rather than simply writing text to SYS$OUTPUT. This utility uses the SysWorks message logging routines which in turn use the conventional OpenVMS system service SYS$PUTMSG to access the SysWorks message shareable image in order to retrieve and display the text of the message.
This results in a much tighter integration of DCL command procedures
with executable images and produces more consistent error messages.
2.2.9 Multi-architecture Support
[V3.1]
SysWorks now supports a /COMBINED qualifier which allows a single BUILD task to generate software for both architectures. It also enhances various DEVTOOLS commands which deletes files and library modules by searching the directories associated with both architectures for items to delete. See notes on the BUILD, DEVTOOLS CMS FETCH, DEVTOOLS CMS RESERVE and DEVTOOLS DELETE commands for details.
[V3.0]
SysWorks now supports multi architecture development for OpenVMS on VAX and Alpha. In order to support this, various directories now have architecture dependent suffices. The following table indicates the old directories and the corresponing new directories:
| Old | New |
|---|---|
| LIB | LIB, LIB-ALPHA, LIB-VAX |
| SFT | SFT-ALPHA, SFT-VAX |
| TST | TST-ALPHA, TST-VAX |
The application logical names have equivalences which use the architecture specific directories. Note that the LIB directory is retained for architecture independent intermediate files such as CDD/Repository tag files. A new directory code of AIL is used for this architecture independent directory. Thus FIN_LIB_DIR might have an equivalence of DISK_DEV8:[FIN.LIB-ALPHA] whereas FIN_AIL_DIR might have an equivalence of DISK_DEV7:[FIN.LIB].
Another feature of multi-architecture support is architecture specific sources. These have a suffix of the form -ALPHA or -VAX in the file name. In order to comply with the MMS implicit rules convention, a copy of such sources are made into the library directory before any compilation or other build action takes place. For example the source FIN_SUB_PROG_A.COB causes an MMS commands such as the following to be generated:
FIN_LIB_DIR:FIN_SUB_PROG_A.OBJ depends_on -
FIN_WRK_DIR:FIN_SUB_PROG_A.COB
|
If the source was architecture specific (eg. was named FIN_SUB_PROG_A-ALPHA.COB) the following script would be generated:
FIN_LIB_DIR:FIN_SUB_PROG_A.COB depends_on -
FIN_WRK_DIR:FIN_SUB_PROG_A-ALPHA.COB
$(copy) $(mms$source) $(mms$target)
FIN_LIB_DIR:FIN_SUB_PROG_A.OBJ depends_on -
FIN_LIB_DIR:FIN_SUB_PROG_A.COB
|
In the case indicated above, the internal name (eg. for Cobol the
program-id) should remain without the architecure suffix.
2.2.10 Multi-variant Support
[V3.0]
SysWorks now supports multi variant environments for development and development testing. The CONTEXT command has been extended to incorporate version parameters on the APPLICATION and ENVIRONMENT sub-commands and a new VARIANT sub-command. A new conveniance command VARIANT has been addded.
The variant directory is placed between the application directory and the 'second level' directory. For example DISK_DEV:[FIN.WRK] would be the most stable and default development area, whereas DISK_MNT:[FIN.VAR-B.WORK] would be for developing new code referred to as variant B.
The CMS class has the version code appended with an underscore to the
primary class name. For example FIN_MNT would be the CMS class for the
latest and default version, whereas FIN_MNT_V021 would be for support
of the older V2.1 version.
2.2.11 Multi-version Support
[V2.5-1]
SysWorks now supports multi version environments for maintenance and maintenance testing. The CONTEXT command has been extended to incorporate version parameters on the APPLICATION and ENVIRONMENT sub-commands and a new VERSION sub-command. A new conveniance command VERSION has been addded.
At this time the format of version numbers is Vn.m. Note that some massaging of the version number takes place when converting it to a version code, for example V2.1 becomes V021.
The version directory is placed between the application directory and the 'second level' directory. For example DISK_MNT:[FIN.WORK] would be the latest and default maintenance version, whereas DISK_MNT:[FIN.V021.WORK] would be for support of the older V2.1 version.
The CMS class has the version code appended with an underscore to the primary class name. For example FIN_MNT would be the CMS class for the latest and default version, whereas FIN_MNT_V021 would be for support of the older V2.1 version.
| Next | Contents | Index |