1.0 Overview

This document describes changes included within:

Note SysConf is used by TPS, PORF, Targetter, XUtil, WinUtil, PLI and PTE.

TPS is used by PORF, Targetter, XUtil, WinUtil, PLI and PTE.

XUtil and WinUtil are used by PLI and PTE.

PTE means both the Run-Time System (RTS) and the Simulator (SIM).

PTE, RTS, CEM and SIM mean all Platforms.

UPTE, URTS, UCEM and USIM mean UNIX Platforms only.

WPTE, WRTS, WCEM and WSIM mean MS-Windows Platforms only.

XPTE, XRTS and XSIM mean X-Window Platforms only.

This version of the RTS is compatible with CEM Modules built with CEM Files distributed with RTS Version 19980714 3.9.7 and later. You may install this version of the RTS without rebuilding your CEM Module. However, in order to make use of the new CEM capabilities, you MUST install this version of the RTS, and then you MUST recompile and relink your CEM Module(s) with the TYX-supplied CEM Files distributed with this version of the RTS.

As time goes on, RTS/CEM testing to provide error-free backwards-compatibility becomes increasingly difficult. Therefore, TYX Corporation very strongly recommends that CEM Users recompile and relink their CEM Modules after installing a new version of the RTS.

1.1 Enhancements

1.1.1 System Configuration – Major.

• New PAWS2000 Linux System (SYS15A).
• SYS04D Redefinition.

1.1.2 TYX Programming Support - Minor.

• Changes to Make Files.
• Support for SYS15A.
• Support for XUtil Version Date.

1.1.3 PAWS Output Report Formatter - Minor.

• Changes to Make Files.

1.1.4 ATLAS Program Targetter - Minor.

• Changes to Make Files.

1.1.5 TYX X-Window Utilities - Minor.

• Changes to Make Files.
• Support for Version Date.

1.1.6 TYX MS Windows Utilities - Minor.

• Changes to Make Files.

1.1.7 PAWS LAPS Interpreter - Minor.

• Changes to Make Files.

1.1.8 PAWS Test Executive - Minor.

• Changes to Make Files.
• Fix for Bad NAM Argument Stack Overflow.

1.2 Problem Reports.

• PR 00-052 - RTS Data Logger Extraneous Warning Message.

2.0 Detailed Description

2.1 Enhancements

2.1.1 System Configuration - Major.

2.1.1.1 New PAWS2000 Linux System (SYS15A).

In late 1999, TYX acquired and installed a new System consisting of a Pentium Computer running the Linux Operating System for the purpose of replacing the Software Development File Server functions of the PAWS486 System (SYS03G). This new System was assigned the TYX Local Area Network (LAN) Network Name of "paws2000" and the TYX System Identifier of "SYS15A".

Although TYX already had other Linux Systems running on the TYX LAN, TYX products (e.g., PLI and PTE) had not been ported to any Linux System because TYX has no Customers running Linux. The plan to have SYS15A become the new Software Development File Server required porting SysConf, TPS and TyxUtil (TYX Utilities). This port was relatively seamless, and, after preliminary testing, it was decided to port PLI (excluding the Source Debug Editor (SDE) capability) simply because the speed and disk storage capacity of SYS15A makes it useful when large UNIX Customer Files must be rebuilt for testing purposes. The PLI port was also relatively seamless.

SYS15A officially became the Software Development File Server on April 18, 2000 when the entire contents of Directories /usr/tyx, /usr/tyxtest, /fs9, /fs10, /fs11, /fs12 and /fs14 were transferred from SYS03G to SYS15A. Except for SYS03G Directory /fs14, all SYS03G Directories were transferred to the identical SYS15A Directories; SYS03G Directory /fs14 was transferred to SYS15A Directory /fs9. All Software Development Systems remotely accessing the SYS03G /fs?? Directories were changed to remotely access the SYS15A /fs?? Directories. SYS03G was changed to remotely access SYS15A Directories also.

C Language Software Development operations on UNIX Systems were not significantly changed; however, those on the Windows NT Server were because: previously, appropriate C Source Files were copied from SYS03G to the Windows NT Server; and, now, are remotely accessed on SYS15A. 16-Bit MS/DOS Programs see a "mangled" File Name when an "actual" File Name exceeds the MS/DOS 8.3 File Name format. All of the Marker Files (e.g., "LastInstall.12B" and "LastRelease") exceed this format. For readability purposes, this required that most (if not all) Make Files be modified to produce Marker Files (e.g., "LastInst.12B" and "LastRlse") that conform to the 8.3 format.

LAPS Language Software Development operations have been significantly changed. Previously, LAPS Language Software Development was done exclusively by TelNet’ing into SYS03G. Installed LAPS Binary/Text Files were then transferred to other UNIX Systems and the Windows NT Server. Now, LAPS Language Software Development: "editing" is done either by TelNet’ing to SYS15A or by running a Windows Text Editor that accesses SYS15A via the TYX LAN; and, "building" is done within an MS/DOS Window by running the "tmake.bat" Batch File. "editing" by TelNet’ing to SYS15A works fine. However, "editing" using a Windows Text Editor results in two minor annoyances: the case of SYS15A File Names are sometimes accidentally changed; and, SYS15A Files sometimes have Carriage Return ASCII Characters added or removed (depending on one’s viewpoint).

2.1.1.2 SYS04D Redefinition

Prior to this release, System Identifier SYS04D was defined to be "HP-715 HP/UX-9.0+".

With this release, System Identifier SYS04D is defined to be "HP-715 HP/UX-10.2+".

2.1.2 TYX Programming Support - Minor.

2.1.2.1 Changes to Make Files.

All appropriate Make Files were changed to conform to the MS-DOS 8.3 File Name format when creating Marker Files.

2.1.2.2 Support for SYS15A.

Support was added for most (but not all) SYS15A Operating System Subroutines (OSS) and for all SYS15A System Library Subroutines (SLS).

2.1.2.3 Support for XUtil Version Date.

Prior to this release, there was no way to determine what "version" of the XUtil Library was included in an executable program.

With this release, the XUtil Library Version Date is printed to the "log file" by the Log File Subroutines (LFS) in the same manner as the WinUtil Library Version Date is printed.

2.1.3 PAWS Output Report Formatter - Minor.

2.1.3.1 Changes to Make Files.

All appropriate Make Files were changed to conform to the MS-DOS 8.3 File Name format when creating Marker Files.

2.1.4 ATLAS Program Targetter - Minor.

2.1.4.1 Changes to Make Files.

All appropriate Make Files were changed to conform to the MS-DOS 8.3 File Name format when creating Marker Files.

2.1.5 TYX X-Window Utilities - Minor.

2.1.5.1 Changes to Make Files.

All appropriate Make Files were changed to conform to the MS-DOS 8.3 File Name format when creating Marker Files.

2.1.5.2 Support for Version Date.

Prior to this release, there was no way to determine what "version" of the XUtil Library was included in an executable program.

With this release, the XUtil Library Version Date is made available via a call to Function VerDateXUS() which returns a Version Date Character String.

2.1.6 TYX MS Windows Utilities - Minor.

2.1.6.1 Changes to Make Files.

All appropriate Make Files were changed to conform to the MS-DOS 8.3 File Name format when creating Marker Files.

2.1.7 PAWS LAPS Interpreter - Minor.

2.1.7.1 Changes to Make Files.

All appropriate Make Files were changed to conform to the MS-DOS 8.3 File Name format when creating Marker Files.

2.1.8 PAWS Test Executive - Minor.

2.1.8.1 Changes to Make Files.

All appropriate Make Files were changed to conform to the MS-DOS 8.3 File Name format when creating Marker Files. Also, the SYS04D Make Include File was changed as a result of the change from HP/UX 9.0 to HP/UX-10.2.

2.1.8.2 Fix for Bad NAM Argument Stack Overflow.

Prior to this release, the RTS Argument Stack was not being cleared when a Non-ATLAS Module File could not be found.

With this release, the RTS Argument Stack is cleared when a Non-ATLAS Module File can not be found.

2.2 Problem Reports.

2.2.1 PR 00-052 - RTS Data Logger Extraneous Warning Message.

The following sequence of relevant events occurs when the RTS Data Logger (RTSDL) runs a Non-ATLAS Module:

• RTSDL closes Data Logger File.
• RTSDL activates Non-ATLAS Module and waits for termination.
• RTSDL re-opens Data Logger File.
• RTSDL positions Data Logger File to Logical End-of-File (EOF).

Prior to this release, RTSDL would, when positioning to the Logical EOF of the Data Logger File:

• Seek to the start of the last "block" of the File.
• Read the last "block" into its Data Logger Buffer.
• Adjust its Data Logger Buffer Pointer to point at the Logical EOF.

However, if the Logical EOF is identical to the Physical EOF, the start of the last "block" would actually be the Physical EOF. Therefore, the subsequent read of the last "block" would fail and a Warning Message would be generated. Because the Data Logger File was correctly positioned, RTSDL processing continued correctly.

With this release, if the Logical EOF is identical to the Physical EOF, RTSDL does not perform the read and, therefore, does not generate an extraneous Warning Message.