TYX Corporation

Productivity Enhancement Systems

PAWS Studio
Release Notes

Version 1.35.8
December 13, 2007

Table of contents

1 Paws Developer's Studio_ 3

1.1 Critical Items 3

1.2 Known Limitations 3

1.3 Enhancements 3

1.4 Problem Reports 3

2 Run Time System_ 4

2.1 Critical Items 4

2.2 Known Limitations 4

2.3 Enhancements 4

2.3.1 New Text Publisher Resource Functionality_ 4

2.3.2 Manual Intervention of the TPS Server made synchronous. 5

2.4 Problem Reports 5

2.4.1 PR 07086 5

1 Paws Developer's Studio

Version 1.35.8

Release date: December 13, 2007

1.1 Critical Items

1.2 Known Limitations

1.3 Enhancements

1.4 Problem Reports

2 Run Time System

Version 1.35.8

Release date: December 13, 2007

2.1 Critical Items

2.2 Known Limitations

2.3 Enhancements

2.3.1 New Text Publisher Resource Functionality

TYX TextPublisher Resources for ERROR, WARNING, INFO, DATALOG & DISPLAY is now enhanced to implement INPUT, so that ATLAS can retrieve any prior information sent to these respective resources form an earlier OUTPUT made to the Resource.

Example:

The above ATLAS sample code provides a technique to do the above.

Notice that in the sample above an INPUT is performed on the ‘ERROR’ TextPublisher Resource. Once an INPUT is performed to retrieve the data cached in the Resource from a prior OUTPUT call, it is no longer maintained in the Resource. As demonstrated above users may loop while NOT ‘EOF’(End of File) to retrieve all the information cached in the Resource.

By default no caching of the OUTPUT text to the resource is performed. To configure the required resource (ERROR/INFO/WARNING) PROGID “RtsIO.TextPublisher” to perform the ‘INPUT’ from Resource functionality, the Resource “Properties” are to be configured in the RTS IOSubsystem.

The following figure displays enabling the “Backup Data” check box of the ‘ERROR’ Resource via the ‘Rts’à’Options’ menu item.

2.3.2 Manual Intervention of the TPS Server made synchronous.

The Manual Intervention interface of the TPS Server is made synchronous. Additionally this allows for RTS Run() interface function to return immediately if a Manual Intervention ATLAS instruction is encountered by the RTS. Clients may continue to run the ATLAS (from the current wait location) subsequently by invoking ManualIntervention() interface function. This call to ManualIntervention() will not return until another Manual Intervention instruction is encountered in ATLAS or the RTS encounters a TERMINATE.

2.4 Problem Reports

2.4.1 PR 07086

This PR is fixed in lieu of the Text Publisher Resource enhancement.