| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 123.1 | Exerciser | EICMFG::BURKE | Jim Burke, @UFC | Tue Oct 01 1991 19:10 | 11 |
| An automated Exerciser would be extremely useful.
Ideally, two processes would exchange data over a looped-back line.
One or other of these programs could also talk to the
Utility/Simulator, thus giving a semi-automated Exerciser.
Also note that these programs would make excellent examples for the
documentation.
Jim Burke
|
| 123.2 | Better quality diagrams for docs | EICMFG::BURKE | Jim Burke, @UFC | Tue Oct 01 1991 19:10 | 5 |
| Some of the line-art diagrams are a bit naff. Nice to have them done in
proper graphics.
Jim
|
| 123.3 | Bookreader format | EICMFG::BURKE | Jim Burke, @UFC | Tue Oct 01 1991 19:13 | 10 |
| Documentation in BOOKREADER format ?
------------------------------------
I've checked this out, and there's not much effort required to
knock them into Bookreader format.
So, this is a definite inclusion for the next release/update.
If anyone wants advance copies of the docs in this format, then let me
know.
Jim
|
| 123.4 | Network/Term-Server/Line setup problems | EICMFG::BURKE | Jim Burke, @UFC | Tue Oct 01 1991 19:17 | 11 |
| To date, almost all setup problems are connected with incorrect setup
of network, Terminal Server, or terminal Line characteristics.
Include a "Troubleshooting" Appendix ?
Expand the Installation Guide to give more detail on such setup ?
A little command file which retrieves and reports network/TS/line
parameters ?
Jim
|
| 123.5 | Demo Script difficult to follow | EICMFG::BURKE | Jim Burke, @UFC | Tue Oct 01 1991 19:57 | 7 |
| The Demo Script in the Delivery Guide (note, NOT a customer document)
is a bit difficult to follow.
References to Figures & fields in the Management Guide would be
helpful. (this has already been done for Teleperm V3.0)
Jim
|
| 123.6 | DE-installation/Cleanup | EICMFG::BURKE | Jim Burke, @UFC | Wed Oct 30 1991 10:47 | 6 |
|
A Kit DE-installation procedure should be provided.
Jim
|
| 123.7 | Vax Simatic 3964R sans Simatic | EICMFG::BURKE | Jim Burke, @UFC | Mon Nov 11 1991 19:12 | 18 |
|
An enquiry has been received regarding the capability to 'bypass'
the Simatic layer of the protocol, and talk ONLY 3964R.
Currently, this is not possible - the Simatic layer is embedded in
3964R layer, and they are inseparable.
Is there any interest in an enhancement to Vax Simatic 3964R, to
bypass the Simatic layer and talk only 3964R ?
For example; an extra VS5$QIO subfunction called "VS5$_3964R_MSG".
If so, then this will be considered for the next release.
Note that this applies also to the BaseStar DAS for Simatic - code
changes would be made to the Simatic Handler which is the 'engine'
of Simatic. The Handler is (currently) the same for both packages.
Jim
|
| 123.8 | Calling arguments. | EICMFG::BURKE | Jim Burke, @UFC | Tue Nov 12 1991 19:50 | 7 |
|
QIO dispatching in the Handler does not check for a sensible I/O
Function code. This should be checked and rejected appropriately.
Note: A customer's application sent an illegal I/O function code to
Simatic. It (ie. Simatic) simply crashed.
|
| 123.9 | Bug in Simulator utility | EICMFG::BURKE | Jim Burke, @UFC | Wed Apr 08 1992 19:51 | 13 |
| The Simulator Utility
=====================
There is a minor irritating bug in this; ie.
1. Application runs waiting for unsolicited messages.
2. The Simulator is used to send one message. This works fine.
3. Another message is sent shortly after the first. This
FAILS, with an error code of zero (!) and an OPCOM message
- "...maximum retries exceeded...".
4. If there is a delay between 2 & 3, then it works fine.
This affects ONLY the Simulator, note.
|