w
window
In
Data Management Systemn
(DMSll), the period in a user-language program between a begin transaction operation and an end transaction operation.(1) In the Communications Management System (COMS) architecture, the concept that enables a number of program environments' to be operated independently and simultaneously at one station. One of the program environments can be viewed while the others continue to operate. (2) In the Editor, a conceptual aperture through which any screen-sized group of lines in a work file can be viewed. The window is said to move forward in the file if lines of higher sequence numbers are being displayed, and backward iflines of lower sequence numbers are being displayed. (3) In the Forms Manager, a rectangular area in a form. (4) In data communications, a flow control mechanism, the size of which is equal to the number of frames, packets, or messages that can be sent from a transmitter to a receiver before any reverse acknowledgment is required. At the data terminal equipment (DTE)/data circuit terminating equipment (DCE) interface of a logical channel, a window is the maximum number of consecutive packets that can be transmitted. (5) A portion of a screen that has been allocated to display the contents of a specified area of memory.
Bibliography
A Series ALGOL Programming Reference Manual, Volume 1: Basic Implementation (form 86000098). Unisys Corporation.
A Series ALGOL Programming Reference Manual, Volume 2: Product Interfaces (form 8600 0734). Unisys Corporation.
A Series COBOLANSI-74 Programming Reference Manual, Volume 1: Basic Implementation (form 86000296). Unisys Corporation.
A Series COBOL ANSI-74 Programming Reference Manual, Volume 2: Product Interfaces (form 8600 0130). Unisys Corporation.
A Series Communications Management System (COMS) Capabilities Manual (form 86000627). Unisys Corporation.
A Series Communications Management System (COMS) Configuration Guide (form 86000312). Unisys Corporation.
A Series Communications Management System (COMS) Operations Guide (form 86000833). Unisys Corporation.
A Series Communications Management System (COMS) Programming Guide (form 8600 0650). Unisys Corporation.
A Series DCALGOL Programming Reference Manual (form 8600 0841). Unisys Corporation.
A Series Generalized Messag~ Control System (GEMCOS) Operations Guide (form 8600 0676). Unisys Corporation.
A Series I/O Subsystem Programming Guide (form 8600 0056). Unisys Corporation.
Formerly A Series I/O Subsystem Programming Reference Manual .
A Series Menu-Assisted Resource Control (MARC) Operations Guide (form 8600 0403).
Unisys Corporation.
A Series Mark 3.9 Software Release Capabilities Oueroiew (form 8600 0015). Unisys Corporation.
A Series Print System (PrintS/ReprintS) Administration, Operations, and Programming Guide (form 8600 1039). Unisys Corporation.
A Series System Commands Operations Reference Manual (form 8600 0395). Unisys Corporation.
A Series System Software Support Reference Manual (form 8600 0478). Unisys Corporation.
Index
A
agendas
defining to COMS, 3-8 in format support library, 3-5 input and output processing, 3-7 application program
c
amending to use COMS direct interface, 3-9
CANDE, (See Command and Edit (CANDE»
COBOL(68), 1-4 COBOL74, 1-4
Command and Edit (CANDE)
operating under MCS window, 1-3,1-5 remote-file handling
compared to COMS remote-file handling, 5-1
Communications Management System (COMS),I-1
CANDE window, 1-3 coexisting with SDF, 3-2 dial-out, 1-3
direct migration, 1-3 entities, 1-4
compared with GEMCOS entities, 1-4 required for format support library, 3-5 features, 1-1
GEMCOS features supported under COMS, 1-4, A-1
GEMCOS windows in, (See GEMCOS windows)
MARC window, 1-3
MCS window in, (See MCS window) versions of COMS
full-featured version, 1-1, 1-5,2-2 Kemel version, 1-5,2-2
windows
defined at system initialization, 1-2
MCS, 1-5 types of, 1-2
COMS, (See Communications Management System (COMS))
COMS Utility
defining the format support library, 3-1 use of, "1-2
controicommands, entering, 2-4 controlpagtng,3-5
conversation area
importance to format support library, 3-6 SDF and the format support library, 3-2 CP 2000
limitations to GEMCOS features with, 4-4 operating Wlder GEMCOS window, 1-6
D
D~s,2-1,2-4
error messages for, 2-9 fields handled by COMS, 2-11 fields in result messages, 2-12 formats of result messages, 2-12 handled by the operating system, 2-5 interpreted by COMS, 2-6
message formats, 2-10 not allowed by COMS, 2-9
resUlt messages given by COMS, 2-8 devices
defining to COMS, 3-6 in format support library, 3-5 dial-out, 1-3
direct I/O, 5-6 direct migration, 1-3 direct window, 1-3
Index
format support library, 3-1
ACTUALNAME,
3-7 as direct migration aid, 1-3 defining COMS entities, 3-5 formatting under COMS, 1-5 in agendas, 3-3logical flow
for forms request, 3-4
for input and output formatting, 3-4 for paging, 3-5
migration considerations, 3-1 order in agenda, 3-7
performance, 3-4
preparing GEMCOS TCL file, 3-9 required COMS entities, 3-5
require~ents,3-3
use with SDF, 3-2 format updating, 3-8 formatting
GEMCOS TCL file, 3-2
through format support library, 3-1 forms request, 3-2
logical flow for, 3-4
FS-LIB, (See format support library) full-featured version of COMB, 1-1, 1-5, 2-2
G
GEMCOS, (See Generalized Message Control System (GEMCOS»
GEMCOS windows, 1-3, 4-1
advantages of running GEMCOS through COMS,4-2
changing station names in TeL, 4-2 entering
controlcouunands,4-3
syste~ commands, 4-3
GEMCOS feature limitations with the CP 2000
due to loss of toggles and tallies, 4-4
other limitations, 4-5 operating under COMS, 1-5 GEMCOS/FORMATLIBRARY, 3-3 Generalized Message Control System
(GEMCOS)
counterparts for COMS entities and attributes
features supported under COMS, 1-4 format library, 3-3
formatting, 3-2 forms request, 3-2
installation for direct migration, 1-3 operating under GEMCOS window, 1-5 paging dialog, 3-3
paging messages, 3-3 TCL file of, (See TCL file)
windoWs, (See GEMCOS windows)
input formatting errors, recognizing, 3-9 InterPro
COMS, 1-1 SDF, 1-5,3-2
K
Kernel version of COMS, 1-2, 1-5, 2-2
L
libraries
in format support library, 3-5 logical I/O
for tanking, 5-5
for time-limit handling, 5-5
M
MARC, (See Menu-Assisted Resource Control (MARC))
MCS, (See message control system (MCS)) MCS window, 1-3,2-2
as used for any given MCS, 2-1 defining windows, 1-5
dialogs, 2-2
established through pseudostation feature, 2-2
maximwn number allowed at a station, 2-2
entering control commands, 2-4 handling DCWRITEs, 2-4
Menu-Assisted Resource Control (MARC) installation for direct migration, 1-3 MARC window, 1-3'
message control system (MCS)
requirements for functioning through COMS, 2-3
logicalfiow for, 3-5 messages, 3-3
process~iteDaS
defining to COMS, 3-7 processing-item libraries, 3-7 processing-item Iists '
creat~, 3-7 in agendas, 3-7
in format support library, 3-5 pseudostation
description ot; 2-2
naming convention for, 2-3
R
recogniz~ input formatting errors, 3-9 remote file, 5-1
closing under COMS, 5-4
declared, 5-2
defining and executing, 5-3 dynamic, 5-2
of declared remote-file program, 5-3 tanking
byCOMS,5-5 by logical I/O, 5-5
time limit on write operation inCOMS,5-5
remote-file window, 1-3 declared, 5-2,5-3 dynamic, 5-2
situations for using, 5-1 ReprintS, 1-3
Restart data set, 1-3
s
Screen Design Facility (SDF)
formatting for ET 1100-compatible devices, 1-5
use with format support library, 3-2, 3-7 SDF, (See Screen Design Facility (SDF)) steps to direct migration, 1-3
synchronized recovery, 1-3
T
TCL, (See transaction control language (TCL))
TCL file, 3-9
compiling for format support library, 3-9 establishing message formats, 3-1 TCL_FORMATTER, 3-1
trancodes
as feature ofCOMS, 1-1 defining to COMS, 3-6
Index
in format support library, 3-5
transaction control language (TCL), 3-1
u
user-created message formats, 3-3
w
windows
as
feature of COMS, 1-1 creating, 3-6GEMCOS, (See GEMCOS windows) in format support library, 3-5 operating under, 1-5
types of, 1-2