6.2.1 General
The PC UI software configuration for the 4635/4635 MX User Interface Dialog requires Microsoft Windows 3.1 and MS DOS 6.2. The required system software configuration is System UI - SU.20.19 and ESS SW V3A R8.3 software or later.
6.2.2 Hardware
Refer to Section 3.0, Hardware Configuration Requirements
6.2.3 Software
6.2.3.1 General
The following information is to clarify certain functionalities in the UI Dialog and are described for information only. These functionalities are not considered as problems (i.e., they are not “things to be fixed“).
Dialog will respond automatically to all “Enter RETURN to continue“ and “Enter RETURN to continue cluster display“ messages when data is going to a window object. Dialog will NOT respond to these messages when data is going to the Messages window.
The blinking caret will appear on the next line only after a “Ready for commands“ message has been displayed. It will remain on the same line after any other message.
“CTRL-X“ is currently used in dialog graphic windows to stop long data displays that issue the “Enter RETURN to continue“ prompt. “CTRL-X“ command is currently not supported in the Messages window.
Ellipses (...) after a menu entry or header target indicates that selection will cause a new window to open, or an existing one to come to the top and activate.
The TAB key is used to go between input fields in a window. The TAB key has no other function in dialog (i.e., cannot TAB in EDI, etc.).
If some window objects are displayed showing current system settings, (i.e., bin mode, bin full, etc.), and the operator enters new settings via the Messages window, the new settings will not be automatically updated in the corresponding window object. The window object must be closed and re-opened.
If the ”LOGON” command is executed in a single line from within the messages window, the password will be momentarily displayed when entered, but will clear when the command is executed by the ESS. The password will NOT appear in the console log.
In some menu objects, data is displayed that is not a selectable menu entry These entries are included to match the equivalent ”command line” display. Selecting these data lines and attempting to apply a command will result in an error message being displayed in the messages window.
In windows that contain input fields, hitting the ”Enter“ key will activate the target that contains the Enter Key Bitmap provided an input field has focus (the blinking cursor is within the input field).
Changing Log Levels closes all open windows and clears the Messages Window. Any work in progress in an open window is lost.
Exiting to DOS while implementing another task or function is not recommended. Unpredictable results will occur.
The Call for Service window is no longer displayed by Dialog. Messages which formerly caused this window to appear are now displayed in the Messages window. The Call for Service screen still appears on the IOT monitor for these conditions.
Due to DOS and Windows restrictions, the accepted range of years for dates using the SET DATE/TIME window and the SETTIME command is from 1980 to 2069, inclusive.
6.2.3.2 System Control/Restrict Command Usage
If the Clusters window is open and the ”Display No Replace Option ...” checkbox is selected, the Clusters window will be updated.
Tasks cannot be added through this window. The “Add / Run Tasks“ window in the Service module must be used to add tasks.
If the RCU window opens with a blank command list, close it and reopen. If the problem persists, i.e., you receive the message ”A Software Error Has Occurred“, executing a <CTRL-V> will solve the problem.
6.2.3.3 System Control/Console Log
The Stop Print target is only effective while SYSUI is transferring the log to the ESS - after that, the print operation is handled like any other Offline print job.
If the floppy door is opened during “Backup”, or any other time the floppy disk is being accessed (green light is on or blinking), unpredictable results can occur.
ESS messages displayed on the PC UI may differ from the console log messages. However, they relay the same information. Console log is the more technical message.
To avoid creating a software error that can prevent the Console Log from printing, do not enter a TEM task before the log has been printed.
6.2.3.4 System Control/Change Log Level
When the password for a new Class Level is typed in the ”Change Logon Class Level” window, the password will be displayed as ”*”. The Password is NOT logged in the Console Log. The ”Message” window refreshes after password has been entered.
6.2.3.5 Utilities/PC Editor
Replace is a “forward only” function and starts at the location of the cursor. Forward and Backward apply to search only.
Files retrieved from the ESS via the File Transfer function must be converted to ASCII prior to editing. Files retrieved from the ESS via the PC Editor are automatically converted.
The PC Editor does not support any SYS files from the ESS, whereas EDI supports selected SYS files.
When saving large files to the ESS in the PC Editor (using the Save target in the Open/Edit window), the user should allow ample time for the file transfer to complete before closing the window. Note that 10 - 15 seconds may be required to complete the transfer.
When using the PC Editor to edit an ESS file, it is recommended that the file first be either COPIED to a ’TMP’ file on the ESS for backup, or after editing the file, the ”SAVE AS” option be used. This will prevent the loss of data in the event that problems are encountered in the process of transferring the file between the ESS and PC.
Selecting EXIT TO DOS exits the UI and puts the PC in DOS mode. Any work in progress in an open window may be lost.
When listing a large number of files, it is recommended that filters (i.e. *.cmd, a*.jsl) be used. Besides being easier for the user to manage, this will prevent the possibility of MS Windows running out of resources and crashing.
6.2.3.6 Files/Display/Print
Extended Display/Print, Sorting, and Stringing are mutually exclusive options for disk devices. Sorting and Stringing are mutually exclusive options for tape devices. ”Paged Display” dumps the file listing in the Messages window in order to view by page (allows operator to answer “Enter RETURN to continue”) instead of waiting for all the information to be displayed in the graphic Display or Extended Display windows. CTRL-X cancels the file listing in the graphic Display or Extended Display window.
6.2.3.7 Files/Type
”Paged Display” dumps the file listing in the Messages window in order to view by page (allows operator to answer ”Enter RETURN to continue”) instead of waiting for all the information to be displayed in the graphic Type window. CTRL-X cancels the type listing in the graphic Type window.
6.2.3.8 Jobs Status
The queue data in the window will not automatically update. To get updated data, the desired target must be selected.
6.2.3.9 Message/Message Window
”CTRL-X” command is not supported in the Message window. ”CTRL-X” is used in dialog graphic windows to stop long data displays that issue the ”Enter RETURN to continue” prompt.
The ”PSTATUS” command is not supported in the Message window except when running command files.
Several messages will display ”SELECT” instead of ”ENTER”, because there are buttons in the User Interface display that are ”SELECTED” with the mouse and not ”ENTERED” via the keyboard. There are instances where additional words are added, such as, ”the”, ”is”, and ”are”. These words may not appear in CHARACTER MODE.
6.2.3.10 Job Control
The ”Graphics” option is not displayed in the window if the system is not configured with graphics.
The Sample Images menu entry will not be shown on a system that is not configured for graphics.
6.2.3.11 HIP
HIP is the menu entry following Start in the Printer Status menu. If you are not on a HIP system, this menu entry will not be displayed.
6.2.3.12 Audit Log
Audit Log and Audit Log Administration window unique stale dates display as **/**/**.
Audit Log Display and Audit Log Print window unique stale dates display as **/**/**.
Sequence errors are indicated by an asterisk ('*') to the left of the sheet count. Duplicate errors are indicated by a plus sign ('+') to the left of the sheet count. Both indicators appear if both errors occured on that sheet.
Audit Log Error Reporting
Operational details are logged to Audit Log. The PC UI logs all operator commands and ESS messages and PC UI error messages in the Console Log. Some of this data may be of relevance to an audited report. Therefore a subset of the data that appears in the Console Log may also appear in an Audit Log. Here are generalities regarding this subset.
1. It is not possible to determine which Audit Log the command or message applies to. Therefore, all open Audit Logs receive the command or message. Important note: An audited job that contains many small reports is likely to have many Audit Logs open at the same time. This can cause the PC UI to slow down and appear sluggish due to the logging of this data to many files.
2. It is not possible to determine which commands are relevant to auditing. Therefore, all operator commands, whether typed into the Messages window or emited by dialog windows, will be logged to all open Audit Logs.
3. ESS messages and PC UI error messages are filtered for Audit Log inclusion. The rule of selection is based on situations that probably have relevance to an audited report. For example, jam clearance advisory messages are logged, as are BTEXT syntax errors. ESS messages that warn of possible image problems are logged. Bar code messages are logged also.
6.3 SYS UI - points to note