Sablime® v5.2 Release Notes Sablime® v5.2 Release NotesCurrent Supported Releases: Sablime® v6.0 & v5.2
The Sablime® release v5.2 includes many MR fixes and minor enhancements, in addition to the following more significant enhancements:
For more information about these features, see the section New Features and Major Enhancements, below.
See the Sablime® Home Page for information about availability, pricing, porting, etc. Also see the new Sablime® Newsletter for more information about v5.2.
The X Window GUI (Graphical User Interface) is based on the Motif standard. All required X utilities are provided with the Sablime® v5.2 executables. All X commands work on Tier 1 platforms under:
| Please Note: | With the introduction and enhancements of the Web Sablime® interface, we are no longer actively working on the PC interface to Sablime. We encourage customers using the PC interface to move to the Web interface. The PC interface is not included in the v5.2 release. |
You can download the Sablime® executables and documentation from our download page. Once you download the Sablime® executables, you will need to contact the STC business group to obtain the necessary licenses. You can contact the business group by sending email to software@lucent.com or calling them at +1 908 582-5880.
The above includes the core Sablime® product, including the Command Line, Curses, and X interfaces. For Web Sablime®, visit the Web Sablime page. To obtain builder, visit the builder page.
Sablime® versions prior to v5.0, patch 04, are not Y2K compliant and are not supported. With the availability of Sablime® v5.2, support for version v5.0 is limited and may be discontinued in the near future.
Detailed conversion instructions for converting your current Sablime® databases to the 5.2 schema, are available.
$ cat bugdata a;b;c;; $ cut -d';' -f2- bugdata b;c; #oops, missing final semicolon $ cut -d';' -f2-5 bugdata b;c; #ditto
Changes are made to the ES, GRP, GRPM, FTD, and PTS relations of the Sablime® database when converting to Sablime® v5.2.
Instructions for installing the Sablime® executables are included in the README.download file which is included in the files you download. The section below deals with some details of installation for the X Window Interface.
Installation instructions for Web Sablime and for builder are on their respective web pages.
All software for the Sablime® X Window commands is installed with the rest of the Sablime® system software; no special installation is required. The sections below discuss certain installation details that may be required for proper functioning of the Sablime® X Window interface.
Sablime® is delivered with an app-defaults file called XSab. This file is found in the xbin directory under the Sablime® bin. The XSab file supplies default values controlling the appearance of the Sablime® windows. For these defaults to take effect, this file must be available to the xsab command when it starts up. There are several ways to accomplish this.
The preferred method is to put XSab where other app-defaults files are kept at installation time, normally in the /user/lib/X11/app-defaults directory. Putting XSab in this location makes the standard defaults automatically available to individual users without any action on their part.
The next-best method, and one which is necessary if the person installing Sablime® is not a system administrator, is to leave XSab in $sabLCB/xbin and change the dot sablime script to set the XUSERFILESEARCHPATH environment variable to the full path of that directory, as follows:
export XUSERFILESEARCHPATH=\
$sabLCB/xbin/%N:$USERFILESEARCHPATH
In some cases, individual users may want (or need) to override the Sablime® application defaults. To do this, users must put an XSab file directly in their login directory and then either add the login directory to XUSERFILESEARCHPATH or unset XUSERFILESEARCHPATH. The default XSab file contains some suggestions for changes the user might want (or need) to make.
The user must set the environment variable DISPLAY by entering
export DISPLAY=localhost:0.0
or, if you rlogin on another machine, run
xhost + remotehost
on your local machine.
To access XSablime® help, you must set the environment variable LD_LIBRARY_PATH to include the path to the file libXmu.so.4. For example, if the libXmu.so.4 is in /usr/openwin/lib, you would set LD_LIBRARY_PATH as follows:
export LD_LIBRARY_PATH=/usr/openwin/lib:$LD_LIBRARY_PATH.
There are three other variables that may need to be set for the Sablime® X Window interface to function properly; XKEYSYMDB, XNLSPATH, and XLIBI18N.
XKEYSYMDB points to the location of a keyboard symbol table. If you are getting a lot of warning messages when the Sablime® X Window commands are executed, you may need to set this variable. If you are using the OpenLook window manager on any platform, you must set this variable. The typical location for this file is
/usr/lib/X11/XKeysymDB or $OPENWINHOME/lib/XKeysymDB.
If the messages still persist, set the variable to point to the default XKeysymDB file in $sabLCB/xbin.
XNLSPATH is set to the location of the X Window NLS files. By default, these files are located in /usr/lib/X11/nls. If this directory does not exist on your system, you must set XNLSPATH to point to the Sablime® v5.1 bin/C directory, as follows:
export XNLSPATH=$sabLCB/C
This variable must be set only if you are using a Sparc 4 X server.
Make sure your font is supported on your host machine; otherwise, it may cause unexpected results.
Make sure your color map is set to 256 if the xsab command
exits with no good reason.
Otherwise, you need to use xsab -logo instead of xsab
To install the Web interface to Sablime®, you must do the following:
export sabMAIL=/var/spool/mail/sabmail
The new features in Sablime® v5.2 are listed in the Introduction. The following sections provide brief descriptions of each of them. For more details, see the relevant sections in the manuals listed under Documentation.
Enhancements to the email system: improved subject line, contents, and handling.
With Sablime® v5.2, the subject line of the Sablime-generated email has been enhanced to mention the MR being addressed, and if appropriate, the generic as well. In general, the subject lines will be longer but more informative. For example, instead of saying "Approved MR", it would now say "Approve MR [proj990001] in Generic [proj]".
The contents of the email have been improved by including information about the command just issued. If, for example, an MR is being "proposed", the email contents will contain the proposal.
The email handling has also been improved, which should eliminate the occasional mis-attributed or grossly delayed email that has occasionally been noticed with Sablime.
Faster, more flexible audits including new PTS audit and report feature
The audits have been redone in perl, greatly improving their performance. They can now also audit individual generics. This is especially helpful for those projects that have huge databases and/or lots of non-active generics.
Enhancement to the reject command: reject to any previous state
The reject command now allows the user to reject an MR back to assigned, submitted, or to any other state previous to the current state. Now, for example, a tester may reject an MR from stpassed to prestpassed if further testing (but not necessarily code changes) is required.
Enhancement to the testpass command: promote MRs through multiple states.
The testpass command now permits the user to promote an MR through multiple states to any higher state, including approved. This may be especially handy for "addsrc" MRs or other administrative MRs that don't require actual testing at the various test levels.
New command: unaccept
The unaccept command permits users to undo an "accept". In fact, given the "unedput" command, and the "unassign" (assign to no one) capability, it is now possible to go so far as to kill an MR even after it has been used to change source. Most commonly, though, this command is expected to be used to undo mistaken accepts (rather than having to "nochange" them).
Enhancement to external MR system: status updates on spawned MRs.
The External Communications capability of Sablime® can now notify other systems when the status of a spawned MR changes.
Enhancement to addisrc command: can infer file type from file extension.
The addisrc command can now be told to look at a file's extension and use it to determine the "file type".
Enhancements to curses screens: arrows and tab navigation, and better navigation help
The arrow and tab keys now work, making screen navigation more intuitive. The curses interface has also been fitted out with navigational help, so getting stuck in a form or help window because you've forgotten the right keystroke should be next to impossible now.
General enhancement: more fields hideable.
Many Sablime® commands have been enhanced to permit administrators to make more fields hideable. These are non-critical fields that your project may or may not be actually using.
Enhancement to ssql command: now usable from TCP/IP clients
Now TCP/IP clients can use the ssql command in the same manner that the host and NFS clients have always been able to.
Web Sablime® - a new version; a more intuitive approach to using Sablime
The new Web Sablime® includes the "MyMRs" interface, where you can work with the MRs that are assigned to you (for development and/or testing), in a more natural "work flow" approach.
builder - a build management suite for Sablime/nmake users
Builder is a tool to manage Sablime/nmake build scenarios. Builder is a portable, flexible, configurable build script designed - not to tell you how to do builds - but to support your various build needs; without modifications to the tool itself.
These are a few of the MR fixes and lesser enhancements included in the v5.2 release.
Complete documentation for Sablime® v5.2 is contained in the following books:
These are included as part of the Sablime® download, and should be present under the Sablime® bin/doc as usr_bk.pdf, referen_bk.pdf, and adm_bk.pdf. These files are in Adobe PDF format. Users are free to print and copy these for their own use. The manuals are also available from the Sablime® Web Site.
Copyright © 2003
Lucent Technologies