F.1. UNISCOPE 100/200 AND UTS 30 COMMUNICATION HANDLER DIFFERENCES
1. The UTS 30 cannot replace UNISCOPE 100/200 terminals that use the following interfaces:
a. IBM* synchronous interface b. IBM asynchronous interface c. SPERRY asynchronous interface d. MIL-STD-188 interface
e. Parallel (console) interface
2. If a UTS 30 is added to a multiplexed configuration containing UNISCOPE terminals, the multiplexer must be updated to provide the timing required by the UTS 30. Generally, the use of the latest multiplexer control board is required. Consult your Sperry representative for details.
3. Transmit operations on the UTS 30 are not sent directly from the keyboard; they are controlled through the (PARAM) field in the control page.
4. On the UTS 30, the US control character is not transmitted to the printer from the host.
5. Space suppression at the ends of lines does not occur during print transparent operation on the UTS 30.
6. UTS 30 timing considerations (NUL fill values) are different. See Appendix G.
7. The break-resume sequence is not supported on the UTS 30.
8. To prevent data loss, the UTS 30 keyboard is not unlocked on acknowledgment.
9. Communication timeout handlers must be lengthened to allow slower UTS 30 commit-time-on-transmit response. This is especially applicable to the host-initiated transmits DC1 and ESC DC1.
F-2
SPERRY UTS 30 SINGLE STATION
System Reference UP-9799 Rev. 1
10. The UTS 30 always sends the DLE 6 code (power-on confidence test completed) when it completes the POC test.
11. The program attention keys (Appendix B) may affect the handler in some cases, but for the most part, the handler can ignore these functions.
12. Cursor positioning sequences not properly terminated with an SI character will not be invoked on the UTS 30. If host sequences are operating without an SI character in the cursor positioning sequences, they must be updated. See 4.4.1 for proper sequences.
13. ESC SO and ESC SI sequences are not valid for protected/unprotected field definition in the UTS 30. If host programs use these sequences, they must be updated to use SO and SI sequences only.
14. BEL sequences within text messages will not be invoked on the UTS 30.
15. The EM control character in a text message will not be recognized by the UTS 30 as an end-of-medium character. The UTS 30 uses the EM character in the immediate FCC sequence.
16. UNISCOPE 100/200 programs that input protected fields will show an apparent extra character per field if they are used with UTS 30 single stations because the UNISCOPE 100/
200 terminals do not send the last character before a protected field; the UTS 30 does send that last character.
17. The UTS 30 can have a second screen. This second screen must be configured as a separate terminal on the host with its own SID address.
F.2. UTS 400 AND UTS 30 COMMUNICATION HANDLER DIFFERENCES
1. The UTS 30 cannot replace a UTS 400 which has an asynchronous interface.
2. The UTS 30 POC test response is always sent to the host, whereas the UTS 400 can omit the POC test response.
3. The UTS 30 sends a "no-traffic" response before disconnecting when the OLE EOT hangup sequence is received from the host.
4. By using all available FCC positions, the UTS 30 can generate a text message of more than 4096 bytes. When the message exceeds 4096 bytes, the UTS 30 uses the ETB code (3.5.1 and 3.5.2) to segment text messages and send them to the host in consecutive blocks.
5. The host should expect to handle throttling in the form of BUSY/THRU responses from a user program request.
6. The EM control character cannot be used in text as an end-of-medium character because the UTS 30 uses this character as part of an immediate FCC sequence (4.4.2).
7. An FCC code cannot be overwritten by an SO/SI character; an SO/SI-protected character cannot be the first character of an FCC-defined field.
8. The host must allow for differences in the error log format between UTS 400 and UTS 30 terminals (Table F-1).
UP-9799 Rev. 1
SPERRY UTS 30 SINGLE STATION System Reference
9. Peripheral buffering is not available on the UTS 30.
F-3
10. On the UTS 30, the program attention keys listed in Appendix B are always available for transmission to the host.
11. The UTS 30 has an FCC location for each screen display location.
12. The FCC character-protect feature is always active on the UTS 30.
13. The UTS 30 has a second screen instead of screen bypass. Both the primary screen and the second screen are displayable. The host can use the second screen to send data to a peripheral device without displaying it on the first screen.
14. The second screen must be configured as a separate terminal on the host if it is to be used online (3.2). UTS 30 terminal addressing (SID) must allow a separate SID designation for the second screen.
15. UTS 30 timing considerations (NUL fill values) are different (Appendix G).
16. The UTS 30 can be connected to a cascaded terminal multiplexer; the UTS 400 can be connected only to a primary terminal multiplexer.
F.3. UTS 40 AND UTS 30 COMMUNICATION HANDLER DIFFERENCES
1. The UTS 30 is compatible with UTS COBOL applications written for the UTS 40 with the following constraints:
a. The basic UTS 30 does not support UTS 40 file management and segmentation of programs.
b. On the programmable UTS 30, the storage space on the 5%-inch diskette (737 bytes) is not as large as on the 8-inch diskettes (1 M byte). Program size may be restricted.
c. UTS COBOL programs are limited to 56K bytes of RAM memory including the interpreter, plus SK bytes of RAM memory restricted to the UTS COBOL instructions area.
d. UTS 40 programs must be recompiled with the UTS 30-compatible COBOL compiler (release level 2R3) on the host.
2. The UTS 30 timing considerations (NUL fill values) are different (Appendix G).
F-4
UTS 400 Contents UTS 40 Contents UTS 30 Contents
BK RAM "3" parity error count Not used Receive overrun errors BK RAM "2" parity error count Not used Not used
BK RAM "1" parity error count Not used Not used B-bit peripheral parity error count Not used Not used 7-bit peripheral parity error count Not used Not used
Communications parity error count Not used Not used
ROM/switch parity error count Not used Not used
CPU parity errors Not used Not used
7 Not used Not used
6 Not used Not used
5 Not used Not used
4 parity errors per display control Not used Not used
3 (display control number) Not used Not used
2 Not used Not used
1 Not used Not used
Communications message received Communications message Communications message with bad character parity received with bad received with bad
character parity character parity
Communications message Communications message Communications message with wrong BCC received with wrong BCC received with wrong BCC received Communications reply request Communications reply Communications reply
issued request issued request issued
Expansion (communications Not used Queue overflow error
interface) log
7-bit peripheral interface Not used Not used
retries required
Expansion (7-bit peripheral) log Keyboard parity error Keyboard parity error B-bit peripheral interface retries B-bit peripheral B-bit peripheral
interface retries interface retries Expansion (B-bit peripheral) log Not used Not used
UP-9799 Rev. 1
G.1. NUL REQUIREMENTS
SPERRY UTS 30 SINGLE STATION
System Reference G-1