TAF_Ver_1_Ref_Man_60459500C_Mar85 TAF Ver 1 Ref Man 60459500C Mar85
User Manual: Pdf TAF_Ver_1_Ref_Man_60459500C_Mar85
Open the PDF directly: View PDF 
.
Page Count: 226
| Download | |
| Open PDF In Browser | View PDF |
60459500
CONTRPL DATA
TAF
VERSION 1
REFERENCE MANUAL
J0&K
CDC® OPERATING SYSTEM:
NOS 2
REVISION RECORD
b / ^ w
REVISION
(04-26-82)
B
(01-27-83)
(03-29-85)
DESCRIPTION
Manual released. This manual reflects NOS 2.0 at PSR level 562. New TAF feature documented in this
manual is TAF automatic recovery. Features documented in the TAF/CRM Reference Manual that are
reflected in this manual are: TAF/CRM automatic recovery, TAF/CRM batch concurrency, TAF/CRM batch
recovery, and TAF/CRM MIP and AK support.
Manual updated to PSR level 580. New RMKDEF statements were added to the xxJ file for multiple index
file recovery and clarifications were made of LIBTASK and recovery descriptions. Addition of the
Login/Logout appendix, and revision of the Terminal Definition appendix and the Line Transmission
Key appendix. This edition obsoletes all previous editions.
Manual updated to NOS 2.4.1 at PSR level 630. This revision reflects the addition of the user
statement to the TAF configuration file and of the send message task (STASK). Appendix G, Terminal
Definition Commands, and appendix J, Accessing a Host, have been revised. The IBM 3270 terminal has
been added to the set of supported terminals. Several technical and editorial changes have been
made.
Publication No.
60459500
REVISION LETTERS 1, O. Q, S. X AND Z ARE NOT USED.
Address comments concerning this
manual to:
© 1982, 1983, 1985
by Control Data Corporation
All rights reserved
Printed in che United States of America
Control Data Corporation
Publications and Graphics Division
4201 North Lexington Avenue
S t . P a u l , M i n n e s o t a 5 5 11 2
or use Comment Sheet in che back of
this manual.
LIST OF EFFECTIVE PAGES
New features, as well as changes, deletions, and additions to information in this manual, are indicated by bars in the margins or by a dot
near the page number if the entire page is affected. A bar by the page number indicates pagination rather than content has changed.
PAGE
Front Cover
Inside Front
Cover
Title Page
2
3/4
5
6
7
8
9
10
1-1
1-2
1-3
1-4
1-5
2-1
2-2
2-3
2-4
2-5
2-6
2-7
2-8
2-9
2-10
2-11
2-12
2-13
2-14
2-15
2-16
2-17
2-18
2-19
2-20
2-21
2-22
2-23
2-24
2-25
2-26
2-27
2-28
2-29
2-30
2-30.1/2-30.2
2-31
2-32
2-33
2-34
2-35
2-36
2-37
2-38
2-39
2-40
2-41
60459500 C
REV
PAGE
2-42
3-1
4-1
4-2
4-3
4-4
4-4.1/4-4.2
4-5
4-6
4-7
4-8
4-9
5-1
5-2
5-3
5-4
6-1
6-2
6-3
6-4
6-5
7-1
7-2
7-3
7-4
7-5
8-1
8-2
8-3
8-4
8-5
8-6
9-1
9-2
10-1
10-2
10-3
10-4
10-5
10-6
10-7
10-8
11-1
11-2
12-1
12-2
12-3
12-4
12-5
A-l
A-2
B-l
B-2
B-3
B-4
B-5
B-6
B-7
B-8
REV
PAGE
B-9
B-10
B-ll
B-12
B-l 3
B-14
B-l 5
B-16
B-l 7
B-18
B-l 9
B-20
B-21
B-22
B-23
B-24
B-25
B-26
B-2 7
C-l
C-2
C-3
C-4
C-5
C-6
C-7
C-8
C-9
C-10
C-ll
C-l 2
D-l
E-l
E-2
F-l
F-2
F-3
F-4
F-5
G-l
G-2
G-3
G-4
G-5
G-6
G-7
G-8
G-9
G-10
G-ll
G-l 2
G-13
G-14
G-15
G-l 6
G-l 7
H-l
H-2
1-1
REV
PAGE
REV
PAGE
REV
J-l
J-2
J-3
J-4
J-5
J-6
J-7
J-8
J-9
J-10
J-ll
J-12
J-l 3
J-14
J-l 5
J-16
J-l 7
J-18
J-l 9
J-20
Index-1
Index-2
Index-3
Index-4
Comment
Sheet
Back Cover
...-;.
'1
3/4
/^^%
PREFACE
J^*
T h e C O N T R O L D ATA ® Tr a n s a c t i o n F a c i l i t y ( TA F ) ,
Ve r s i o n 1 . 3 , i s a n e t w o r k h o s t p r o d u c t . I t i s a
network application that requires the facilities of
the Network Access Method (NAM) and the 255x Series
Communications Control Program (CCP). TAF runs as a
subsystem of the Network Operating System (NOS),
Version 2, and may be used with COMPASS, FORTRAN, or
COBOL.
This manual documents the executive portion of TAF.
The three data managers available for use with TAF
are each documented in their respective reference
manuals. These are:
• CDC® CYBER Database Control System, Version
2 (CDCS)
• CDC TAF/CRM Data Manager Version 1 (CRM)
• CDC TOTAL Data Manager Version 2
the transaction executive imply the controlling
p o r t i o n o f T A F, t h e p o r t i o n d e s c r i b e d i n t h i s
manual. References to FORTRAN imply either FORTRAN
Extended Version 4 or FORTRAN Version 5; TS mode is
n o t a l l o w e d ( t h a t i s , t h e S E Q , T S , a n d O P T- O
parameters are not allowed on the FTN command).
References to COBOL imply Version 5.
Where brackets, [ ], are used in task request format
descriptions, they indicate optional parameters.
The term alphanumeric refers to any combination of
the letters A through Z and the numbers zero through
nine; special characters are not included.
Conventions for word formats are as follows:
• Crosshatching indicates a field is not used
by or is not applicable to TAF.
Refer to the list of related publications for full
titles and publication numbers of the respective
manuals.
• Reserved fields may contain information
useful to TAF internal processing. The user
should not expect them to contain any partic
ular values.
AUDIENCE
• Fields labeled with mnemonics indicate that
a specific parameter must be inserted (gener
ally described after the word format).
This manual is for the data administrator and
a p p l i c a t i o n s p r o g r a m m e r. T h e d a t a a d m i n i s t r a t o r
(DA) is a person or a group of people responsible
for installing and maintaining the transaction
subsystem. This person or group sets up the data
base and describes the relationships among the
various elements. The DA is concerned with the
internal design of the system and can modify many of
the system components to suit site requirements. An
applications programmer is a person who writes tasks
in FORTRAN, COBOL, or COMPASS to be used by the end
user (terminal operator). Using these tasks, the
terminal operator can access and update the data
base with little or no knowledge of TAF. New users
of TAF should consult the TAF I User's Guide as a
fi r s t s o u r c e o f i n f o r m a t i o n . I t i s a n i n t r o d u c t o r y
text for inexperienced users.
The user must be familiar with basic NOS operations
such as running a compilation job. The NOS 2
Reference Set, Volume 2, acquaints the new user with
the fundamentals of NOS. The NOS 2 Reference Set,
Volume 3, is for the high-level language applications
programmer who is already familiar with NOS. The
NOS 2 Reference Set, Volume 4, is for the COMPASS
applications programmer.
TERMINOLOGY AND CONVENTIONS
References in this manual to the transaction
subsystem imply every aspect of TAF. References to
60459500 C
• Fields with numeric identifiers indicate the
actual value that is used or returned for a
particular request.
Models 815, 825, 835, 845, and 855 of the CYBER 170
Computer Systems share many of the functional and
architectural attributes of the CYBER 180 computer
systems (models 810, 830, 835, 840, 845, 850, 855,
and 860). The term CYBER 180-class machines de
scribes these similar models collectively.
Extended memory for model 176 is large central
memory extended (LCME). Extended memory for models
865, 875 and CYBER 180-class machines is unified
extended memory (UEM). Extended memory for models
865 and 875 may also include either extended core
storage (ECS) or extended semiconductor memory
(ESM). Extended memory for all other NOS computer
systems is either ECS or ESM. ECS and ESM are the
only forms of extended memory that can be shared in
a linked shared device multimainframe complex and
can be accessed by a distributed data path (DDP).
In this manual, extended memory refers to all forms
of extended memory unless otherwise noted.
Programming information for the various forms of
extended memory can be found in the COMPASS 3
Reference Manual and in the appropriate computer
system hardware reference manual.
Publication
Control Data Publication Number
RELATED PUBLICATIONS
The following manuals contain additional information
for the user.
Publication
Control Data Publication Number
NOS Version 2 Reference Set,
Volume 2, Guide to Systeo Usage 60459670
NOS Version 2 Reference Set,
Vo l u m e 3 , S y s t e m C o m m a n d s 6 0 4 5 9 6 8 0
COBOL Version 5 Reference Manual 60497100
Common Memory Manager Version 1
Reference
Manual
COMPASS Version 3 Reference
Manual
CYBER Database Control System
Version 2 Data Administration
Reference
Manual
NOS Version 2 Reference Set,
Vo l u m e 4 , P r o g r a m I n t e r f a c e 6 0 4 5 9 6 9 0
60499200
60492600
TA F Ve r s i o n 1 U s e r ' s G u i d e 6 0 4 5 9 5 2 0
60485200
TAF/CRM Data Manager
Ve r s i o n 1 R e f e r e n c e M a n u a l 6 0 4 5 9 5 1 0
60485300
CYBER Loader Version 1
Reference
Manual
60429800
FORTRAN Extended Version 4
Reference
Manual
60497800
FORTRAN Version 5 Reference
Manual
60481300
Network Products Network Access
Method Version I Network Defini
tion Language Reference Manual 60480000
Network Products
Network Access Method Version 1/
Communications Control Program
Version 3 Host Applicaton
Programming Reference Manual 60499500
NOS Version 2 Network Terminal
User's
Instant
60459380
NOS Version 2 Installation
Handbook
60459320
NOS Version 2 Manual Abstracts 60485500
NOS Version 2 Operations
Handbook
60459310
CYBER Record Manager Advanced
Access Methods Version 2
Reference
Manual
60499300
60495700
Network Products
Network Access Methods Version 1/
Communications Control Program
Version 3 Terminal Interfaces
Reference
Manual
60480600
NOS Version 2 Reference Set,
Volume 1, Introduction to
Interactive
Usage
60459840
NOS Version 2 Analysis Handbook 60459300
CYBER Database Control System
Version 2 Application Program
ming Reference Manual
CYBER Record Manager Basic
Access Methods Version 1.5
Reference
Manual
NOS Version 2 Administration
Handbook
60459660
TOTAL - CDC Version 2
Reference
Manual
76070300
The NOS 2 Manual Abstracts is a pocket-sized manual
containing brief descriptions of the contents and
intended audience of all NOS and NOS product manuals.
The abstracts can be useful in determining the
manuals of greatest interest to a particular user.
Control Data also publishes a Software Publications
Release History, publication number 60481000, of all
software manuals and revisions packets it has issued.
This history lists the revision level of a particular
manual that corresponds to the level of software
installed at the site.
These manuals are available through Control Data
sales offices or Control Data Literature Distribution
Services (308 North Dale, St. Paul, Minnesota 55103).
SUBMITTING COMMENTS
The last page of this manual is a comment sheet.
Please use it to give your opinion on the manual's
usablility, to suggest specific improvements, and to
report any errors. If the comment sheet has already
been used, you can mail you comments to:
Control Data Corporation
Publications and Graphics Division ARH219
4201 Lexington Avenue North
St. Paul, MN 55112
A d d i t i o n a l l y, ' i f y o u h a v e a c c e s s t o S O LV E R , a n
online facility for reporting problems, you can use
it to submit comments about the manual. Declare
your problem type as DOC and use NS2 as the product
i d e n t i fi e r .
DISCLAIMER
This product is intended for use only as described in
this document. Control Data cannot be responsible
for the proper functioning of undescribed features
or parameters.
60459500 C
/^^K
J^V
CONTENTS
1.
r
INTRODUCTION
l-l
RERUN Request
RPUT and RGET Requests
RSECURE Request
SECURE Request
TSTAT Request
System Task Recovery Requests
CALLTRN Request
SRERUN Request
TINVOKE Request
WSTAT Request
2-32
2-33
2-34
2-35
2-37
2-38
2-38
2-40
2-40
2-41
O n - L i n e Tr a n s a c t i o n P r o c e s s i n g A d v a n t a g e s l - l
On-Line Transaction Processing Problems l-l
Batch
Interface
1-3
Network
Interface
1-3
Ta s k s
1-4
Transaction
Processing
1-4
TA F
Requests
1-4
Entering the Transaction Subsystem 1-4
Implementing
an
Application
1-5
Subcontrol
Points
1-5
Multimainframe
1-5
Extended
Memory
1-5
3. ACCESS AND USE OF CDCS BY TASKS
3-1
2.
4. SYSTEM FILES
4-1
xxJ File
CRM Data Manager xxJ File
TOTAL Data Manager xxJ File
CDCS or No Data Manager xxJ File
Creating an xxJ File
Journal Files
System Journal File
Data Base Journal Files
Journal File Entry Header
JOURNL Request
TAF Configuration File
DMS Statement
DISPLAY Statement
NETWORK Statement
RECOVER Statement
K. Statement
User Statement
Communication Recovery File
4-1
4-1
4-4
4-4
TASK/TRANSACTION EXECUTIVE
INTERFACE
Communication Block
Requests
Data Manager Requests
Journal File Requests
Memory Dump Requests
System Requests
Memory Requests (COMPASS Only)
Message Requests
Task Scheduling Requests
CALLRTN Request
CALLTSK Request
NEWTRAN Request (COMPASS Only)
TRANCHK Request
Input/Output Requests
WAITINP Request
LOADCB Request
SETCHT Request
BLDABH Request
GETABH Request
TERMDEF Request
SEND Request
RELSCB Request
TSIM Request
TARO Request
I10 Request
BWAITINP Request (COMPASS Only)
TPSTAT Request (COMPASS Only)
BEGIN Request
Task Control Requests
CEASE Request
ITL Request
LOGT Request (COMPASS Only)
KPOINT Request
WAIT Request
Task Utility Requests
LOGIN Request
EXTRACT Request
INSERT Request
Application Recovery Requests
60459500 C
2-1
2-1
2-3
2-3
2-3
2-3
2-3
2-3
2-4
2-4
2-4
2-6
2-7
2-8
2-8
2-9
2-10
2-11
2-12
2-14
2-16
2-17
2-23
2-23
2-26
2-27
2-28
2-28
2-28
2-28
2-28
2-29
2-29
2-30
2-30
2-30.1
2-31
2-31
2-32
2-32
4-4.1
4-5
4-5
4-5
4-5
4-5
4-7
4-7
4-7
4-8
4-8
4-8
4-8
4-8
5. BATCH/TRANSACTION SUBSYSTEM
INTERACTION
5-1
BTRAN Request
SUBMT Request
5-1
5-3
6. MEMORY DUMPS
6-1
Task Dump
DSDUMP Request
CMDUMP Request
K.DSDUMP Command
KTSDMP Utility
Task Dump Formats
TAF Dump
K.DUMP Command
K.DUMPLIM Command
6-1
6-1
6-3
6-4
6-4
6-4
6-4
6-5
6-5
7.
APPLICATIONS INTERFACE FOR AUTOMATIC
RECOVERY
Purpose
Concepts
Named-Transactions and Run Units
Data Base Recovery
Transaction Recovery
Coding
Coding Structures for Data Base Recovery
Only
Transactions Using CRM
TAF Transactions Using CDCS
Coding Structures for Transaction Recovery
Transactions Using CRM
TAF Transactions Using CDCS
Terminal Recovery Considerations
CALLTSK without CEASE and RECOVERY
Multiple Data Manager Use
TOTAL Data Manager Use
8.
DATA ADMINISTRATOR AND OPERATOR INTERFACE
FOR RECOVERY
7-1
7-1
7-1
7-1
7-1
7-1
7-2
7-2
7-2
7-2
7-3
7-3
7-3
7-4
7-5
7-5
7-5
8-1
Recovery Overview
Hardware Configuration Considerations
Installation
TAF K Display
Initial K Display
K.INT Command
K.ERO Command
K.REC Command
Restart K Display
TCF/CRF Recovery Considerations
TAF Configuration File
Communication Recovery File
Error Override
File Reformatting
Multiple Communication Recovery Files
Multimainframe Recovery
Recovery Processing Flow
TAF and System Failure
NAM Failure
Terminal Failure
CDCS Failure
Task Failure
TAF Termination
TAF Automatic Recovery Report
8-1
8-2
8-2
9. NETWORK FILES
9-1
Terminal Network Description File
Network File Origination
9-1
9-1
8-2
8-2
8-2
8-3
8-3
8-3
8-3
8-3
8-3
8-3
8-3
8-4
8-4
8-4
8-4
8-5
8-5
8-5
8-5
8-5
8-6
10.
TA S K
LIBRARY
10-1
L I B TA S K
Utility
Ta s k
Residency
and
Type
L I B TA S K
Command
Input
Directives
Named-Transaction Input Directive
Ta s k
Input
Directive
Scheduling
Priority
Creating
a
New
Ta s k
Library
U p d a t i n g a n E x i s t i n g Ta s k L i b r a r y
D e l e t i n g a Ta s k f r o m a Ta s k L i b r a r y
I g n o r i n g a Ta s k i n t h e R e p l a c e m e n t F i l e
10-1
10-1
10-2
10-5
10-5
10-5
10-7
10-7
10-7
10-7
10-8
11. REQUIRED SYSTEM TASKS AND TRANSACTIONS U-l
BTRAN
Recovery
Ta s k
( B TA S K )
D a t a B a s e R e c o v e r y Ta s k ( C TA S K )
Initial
Ta s k
( I TA S K )
K
Display
Ta s k
(KDIS)
Logout
Ta s k
(LOGT)
Message
Abort
(MSABT)
Inactive
Ta s k
( O F F TA S K )
CDCS
Rerun
Ta s k
( R C TA S K )
R u n U n i t R e c o v e r y Ta s k ( R TA S K )
Send Message Task (STASK)
System Message Task (SYSMSG)
Execute Named Task (XTASK)
XTRAN Transaction
11 11 11 11 11 11 11 - 2
11 - 2
11 - 2
11-2
11-2
11-2
11-2
12. ITASK SYSTEM TASK
12-1
Macros
TIMCNT Macro
TRAN Macro
STRAN Macro
ITASK Description
TAF-Originated Transactions
Conditions Requiring TAF-Originated
Transactions
Time Activation
K.IDLE Console Operator Command
Terminal Login
Terminal Break Conditions
Terminal Connection Broken
Network Normal Shutdown
Network Failure
Network Immediate Shutdown
Terminal Inactive
Logical Error
Block Not Delivered
Terminal Characteristic Change
Terminal Input Too Large
Terminal Type Ahead
User Status
12-1
12-1
12-1
12-1
12-2
12-3
12-3
12-3
12-3
12-4
12-4
12-4
12-4
12-4
12-4
12-4
12-4
12-5
12-5
12-5
12-5
12-5
APPENDIXES
A. CHARACTER SETS
A-l D. SAMPLE COMMAND LIST STRUCTURES
B. DIAGNOSTIC MESSAGES
B-l
COMPASS Task Command List Structure
FORTRAN Task Command List Structure
COBOL Task Command List Structure
C. GLOSSARY
C-l
E. FILES USED BY TAF
• 8
D-l
D-l
D-l
D-l
E-l
60459500 C
/rfS^ly
Jffev
JP^
F. INSTALLATION OVERVIEW
F-l
G. TERMINAL DEFINITION COMMANDS
G-l
Introduction
Terminal Definition Command Format
Restrictions
Terminal Definition Commands
(AB) - Abort Output Block Character
(AR) - Automatic Character Recognition
(BF) - Blocking Factor
(BR) - Break Key as User Break 1
(BS) - Backspace Character
(Bl) - Interruption or User Break 1
Character
(B2) - Termination or User Break 2
Character
(CH) - Display Terminal Characteristics
(CI) - Carriage Return Idle Count
(CN) - Cancel Character
(CP) - Cursor Positioning after Input
(CT) - Network Control Character
(DL) - Delimiters for Single-Message
Transparent Input Mode
(EB) - End-of-Block Character
(EL) - End-of-Line Character
(EP) - Echoplex Mode
(FA) - Full-ASCII Input Mode
(HC) - Host Connection
(HD) - Display of Host Nodes
(HN) - Host Node Selection
(HS) - Host Selection
(IC) - Flow Control for Input Devices
(IN) - Input Device and Transmission Mode
(LI) - Line Feed Idle Count
(LK) - Lockout of Unsolicited Messages
(MS) - Message to Network Operator
(OC) - Flow Control for Output Devices
(OP) - Output Device Selection
(PA) - Parity Processing
(PG) - Page Waiting
(PL) - Page Length
(PW) - Page Width
(SE) - Special Editing Mode
(TC) - Terminal Class Command
(TM) - Terminating a Terminal-Host
Connection
(XL) - Multimessage Transparent Mode
G-l
G-l
G-2
G-2
G-3
G-3
G-3
G-3
G-4
G-4
G-4
G-4
G-4
G-5
G-5
G-5
G-5
G-6
G-7
G-7
G-7
G-8
G-8
G-9
G-9
G-9
G-9
G-10
G-10
G-10
G-ll
G-ll
G-ll
G-l 2
G-12
G-12
G-12
G-12
G-13
G-13
H. DELIMITING AND TRANSMITTING TERMINAL INPUT H-l
Physical End-of-Line (Line Feed) H-l
Logical End-of-Line (Carriage Return) H-l
Message
Transmission
H-l
I. DETECTION OF POTENTIALLY BLOCKED TASKS I-I
J.
ACCESSING
Brief
Description
A
HOST
J-l
of
Access
J-l
Step 1 - Gathering Information J-i
S t e p 2 - S e t t i n g U p Yo u r Te r m i n a l J - l
Step 3 - Connecting Your Terminal to the
Network
J-l
Step 4 - Identifying Your Terminal to the
Network
J-3
Step
5
Selecting
a
Host
J-3
Step 6 - Connecting to the Selected Host J-3
Step 7 - Identifying Yourself and Your
Te r m i n a l
to
the
Host
J-4
Step 8 - Selecting a Network Application J-4
Detailed
Description
of
Access
J-4
Step 1 - Gathering Information J-4
S t e p 2 - S e t t i n g U p Yo u r Te r m i n a l J - 7
Step 3 - Connecting Your Terminal to the
Network
J-8
Step 4 - Identifying Your Terminal to the
Network
J-8
Procedure for Asynchronous Terminals J-8
P r o c e d u r e f o r H A S P Te r m i n a l s J - 9
P r o c e d u r e f o r M o d e 4 Te r m i n a l s J - 1 0
Procedure for Bisynchronous Terminals J-10
Step
5
Selecting
a
Host
J-10
Selecting
a
Host
J-10
S e l e c t i n g a S p e c i fi c H o s t P a t h J - i I
Controlling the Display of Host Paths J—11
Step 6 - Connecting to the Selected Host J-13
Step 7 - Identifying Yourself and Your
Te r m i n a l
to
the
Host
J-13
Automatic
Login
J-14
Login
Dialog
J-14
Step 8 - Selecting a Network Application J-15
Automatic
Connection
J-15
Manual
Connection
J-15
Abbreviated Login and Application
Connection
J-16
Switching to a Different Application J-16
Direct
Switches
J-16
Indirect
Switches
J-17
Dialog for Direct and Indirect Switches J-17
R e s t a r t i n g L o g i n I d e n t i fi c a t i o n J - 1 7
Direct
Restarts
J-17
Indirect
Restarts
J-17
Secure
Login
Restarts
J-17
Disconnecting
from
a
Host
J-18
Disconnecting with Application Commands J-18
Disconnecting with Host Commands J-18
Disconnecting with a Network Software
Command
J-18
Reconnecting to a Host or Connecting
to
a
Different
Host
J-18
Disconnecting from One Host and
Connecting to a Different Host J-18
Interruptions
J-19
Communicating with the Network Operator J-19
Receiving
Messages
J-19
Sending
Messages
J-19
Preventing
Messages
J-19
Suspensions of Communication J-19
Communication
Failures
J-19
Application
Failures
J-20
Disconnection from an Application
and/or
Host
J-20
Disconnection from the Network J-20
INDEX
0^
60459500 C
FIGURES
1-1 TAF Control Point for CDCS Data Manager
1-2 TAF Control Point for TAF/CRM
Data Manager
1-3 TAF Control Point for TOTAL
Data Manager
2-1 Communication Block Format
2-2 CALLRTN
2-3 CALLRTN (Chain)
2-4 CALLRTN (Multiple Chains)
2-5 CALLTSK with CEASE Request
2-6 CALLTSK without CEASE Request
2-7 NEWTRAN Parameter Table
2-8 TRANCHK Parameter Table
2-9 LOADCB Parameter Table
2-10 SETCHT Parameter Table
2-11 GETABH Parameter Table
2-12 TERMDEF Parameter Table
2-13 SEND Parameter Table
2-14 TSIM Parameter Table
2-15 TARO Parameter Table
2-16 IIO Parameter Table
2-17 ITL Parameter Table
4 - 1 J o u r n a l F i l e ( B u ff e r e d a n d
Nonbuffered Structure)
4-2 Journal File Entry Header
4-3 JOURNL Parameter Table
5-1 BTRAN Header Word
5-2 BTRAN Request
5-3 SUBMT Parameter Table
1-2
1-2
1-3
2-2
2-5
2-5
2-5
2-6
2-7
2-7
2-8
2-11
2-13
2-15
2-17
2-23
2-25
2-27
2-27
2-30
4-2
4-6
4-6
5-2
5-2
5-3
5-4
6-1
6-2
6-3
7-1
8-1
9-1
10-1
12-1
12-2
12-3
12-4
D-l
D-2
D-3
J-l
J-2
J-3
J-4
J-5
J-6
J-7
J-8
J-9
SUBMT
Request
5-4
DSDUMP
Parameter
Ta b l e
6-3
CMDUMP
Parameter
Ta b l e
6-4
KTSDMP
Format
6-5
Recoverable TAF Transaction
Using
CDCS
7-4
Format of Part Three of the TAF
Automatic Recovery Report 8-6
Communication Between a Terminal Status
Ta b l e a n d a C o m m u n i c a t i o n B l o c k 9 - 2
Ta s k
Library
Report
10-4
F o r m a t o f a T T O T Ta b l e E n t r y 1 2 - 1
F o r m a t o f a T R A N T Ta b l e E n t r y 1 2 - 2
F o r m a t o f a T R A N S Ta b l e E n t r y 1 2 - 2
Communication Block for TAFOriginated
Transactions
12-3
C O M PA S S C o m m a n d L i s t S t r u c t u r e D - l
FORTRAN Command List Structure D-l
COBOL Command List Structure D-l
Separate
Acoustic
Coupler
J-2
D a t a S e t B u i l t i n t o t h e Te r m i n a l J - 2
Data Sets with Switches and Buttons J-2
Terminal with Built-in Acoustic Coupler J-3
Interactive Display Console J-5
Interactive
Printer
Console
J-5
Remote
Batch
Te r m i n a l
J-6
Host
Availability
Display
J-ll
Sample Login from an Asynchronous
Te r m i n a l
J-13
TABLES
2-1 BLDABH Request Parameters
2-13
2-2 Application Block Header
2-15
2-3 COBOL SEND Request Parameters
2-18
2-4 FORTRAN SEND Request Parameters
2-20
2-5 COMPASS SEND Request Parameters
2-21
2-6 COMPASS SEND Parameter Interrelationships 2-24
2 - 7 T S AT K e y w o r d D e s c r i p t i o n s 2 - 3 9
2 - 8 W S TAT K e y w o r d D e s c r i p t i o n s 2 - 4 2
5-1
BTRAN
Status
Va l u e s
5-2
• 10
A-l
E-l
F-l
G-l
G-2
H-l
7-Bit ASCII Code Standard Print
63/64-Character Set
Files Used by TAF
Installation Overview
Default Terminal Definitions
Parameter Ranges for Terminal
Definition Commands
Default Message Delimiter and
Transmission Keys
A-l
E-l
F-2
G-l 5
/*S3l8v
G-16
H-2
60459500 C
/iS|!X
INTRODUCTION
/fp^>,
TAF is a network product that controls transaction
processing. Transaction processing consists of
taking an existing collection of information, called
a data base, and correcting old data or adding new
data to create an up-to-date data base. Such a
correction or addition is called a transaction.
In a transaction processing system, the data base
must be efficiently structured and easily accessible
to the user. A data manager provides these features.
Control Data offers the following data managers for
use with TAF.
• The CYBER Database Control System (CDCS).
• T h e C Y B E R R e c o r d M a n a g e r ( C R M ) . ( TA F
supports only those features documented In
the TAF/CRM Data Manager 1 Reference Manual.)
• The TOTAL Data Manager.
A l l d a t a m a n a g e r s c a n o p e r a t e c o n c u r r e n t l y.
However, a single transaction can use only:
• CDCS and one other data manager,
T h e m o s t i m p o r t a n t f e a t u r e o f TA F i s i t s e f fi c i e n t
s y s t e m r e s o u r c e u t i l i z a t i o n . TA F ' s t r a n s a c t i o n
processing differs from other modes of operation in
that a task only contains application code.
Terminal communications are handled by one terminal
communications interface. Data base communications
are handled by one copy of a data base manager.
When tasks need to be loaded, they are simply copied
from a task library to a subcontrol point; none of
the normal overhead of loading is incurred.
The TAF control point contains application tasks as
subcontrol points. When a task completes, one of
the following occurs:
• It may be immediately reused by other
waiting transactions (no reloading is
necessary).
• Another task may be loaded in its place.
• Other active tasks may be moved up in memory
and the remaining memory returned to the
system for use by non-TAF applications.
TAF will expand its memory to a maximum value as
needed.
or
J8*V
• CDCS alone,
or
• One other data manager alone.
T h e m a i n f u n c t i o n o f TA F i s o n - l i n e t r a n s a c t i o n
processing; that is, direct 'operator interface with
the data base through a terminal.
ON-LINE TRANSACTION PROCESSING
ADVANTAGES
Some advantages associated with on-line transaction
processing are:
• The operator submitting the data through TAF
can make immediate data corrections.
• The operator can verify that operations have
c o m p l e t e d s u c c e s s f u l l y. TA F a l l o w s t h e
operator to view additions or corrections to
the data base to verify their accuracy.
• T h e d a t a b a s e i s u p d a t e d i n s e c o n d s . TA F
p r o v i d e s i m m e d i a t e u p d a t i n g c a p a b i l i t y,
which allows other transactions to make use
of the updated data base.
60459500 A
W h e n t h e r e i s n o t r a n s a c t i o n a c t i v i t y, TA F s i z e i s
reduced to a small amount of memory. When input is
sensed, TAF rolls back in to service the request.
Figures 1-1, 1-2, and 1-3 summarize the TAF control
point and its operation.
ON-LINE TRANSACTION PROCESSING
PROBLEMS
Some problems associated with on-line transaction
p r o c e s s i n g a n d t h e m e t h o d s t h a t TA F u s e s t o
alleviate them include the following.
• It is difficult to schedule and control
m u l t i p l e j o b s . TA F s o l v e s t h e p r o b l e m o f
multiple job control scheduling by using
subcontrol points. Like the operating
system that controls and schedules jobs to
control points (where they are processed),
TA F c o n t r o l s a n d s c h e d u l e s t r a n s a c t i o n
processing programs to portions of its
control point called subcontrol points.
Subcontrol points are protected from each
other by CYBER hardware memory protection.
• T h e t e r m i n a l i n t e r f a c e i s c o m p l i c a t e d . TA F
minimizes terminal programming by using
simple input/output (I/O) commands that are
processed by the standard network terminal
interface.
1-1
D ATA
DESCRIPTION
COMMANDS
D ATA
BASE
D ATA
DEFINITION
TAF
^
COMMUNICA
TION
EXECUTIVE
^
D ATA
BASE
MANAGER
D ATA
DESCRIP
TION
TASKS
LIBTASK
TASK
LIBRARY
BATCH PROGRAM
Figure 1-1. TAF Control Point for CDCS Data Manager
TAF
TRANSACTIONS
COMMUNICA
TION
EXECUTIVE
EXECUTIVE
INTERACTIVE OR
BATCH PROGRAM
INTERACTIVE
OR BATCH
PROGRAM
TASK
LIBRARY
DATA
MANAGER
DATA
BASE
c
COMMANDS
Figure 1-2. TAF Control Point for TAF/CRM Data Manager
1-2
60459500 B
yrfSS^S.
D ATA
DESCRIPTION
J^s
TRANSACTIONS
COMMUNICA
TION
EXECUTIVE
EXECUTIVE
TASK
LIBRARY
OATA
BASE
x
DATA
MANAGER
r
COMMANOS
BATCH PROGRAM
Figure 1-3. TAF Control Point for TOTAL Data Manager
BATCH INTERFACE
A b a t c h i n t e r f a c e w i t h TA F i s a l s o a v a i l a b l e . T h e
batch interface can generate large reports without
tying up a terminal until the listing has been
printed. The report can be printed at a high-speed
central site printer. Batch mode can also be used
for testing and debugging. The batch interface is
described in section 5.
NETWORK INTERFACE
The network terminal interface uses NAM and 255x
communications processors. This interface is used
by all other network products (for example, Remote
Batch Facility and Interactive Facility). If
validated, terminal users may select these
applications as well as TAF. The network provides
the following features for transaction processing.
• Managing network protocol.
• Buffering and queuing data for regulating
data fl o w.
• Supporting a wide variety of terminals
through standardization of data formats as
well as providing the ability to handle
transparent data.
• Sharing network among communication-oriented
services.
60459500 A
^ ^ v
The network makes use of the interactive virtual
terminal (IVT) concept. This concept abstracts
certain functions of a variety of real terminals.
The applications programmer need not be concerned
with character sets and communications protocols.
• An IVT has an input/output device that sends
or receives certain amounts of data termed
logical lines* These logical lines are
transformed into physical lines of characters
of the appropriate character set for the
real terminal.
• Logical lines that exceed the physical
capacity of the real terminal are
automatically folded into two or more
physical lines.
• The spacing of logical lines of output can
be further controlled by the use of format
effectors.
• Output to a device may be optionally paged,
so that data that would overwrite any output
being displayed is not sent until the
terminal user has acknowledged the preceding
output.
Both the application and the terminal user
c a n r e d e fi n e t e r m i n a l c h a r a c t e r i s t i c s o f t h e
actual terminal, which may differ from those
a s s u m e d , a n d s u p p l y o r r e d e fi n e t h e
operational controls provided.
1-3
When an application requires features not provided
by the IVT but known to exist on the connected real
terminal, the application may do one of the
following.
• Embed appropriate control characters in the
output text.
• Tr a n s f e r d a t a i n t r a n s p a r e n t m o d e , i n w h i c h
case all transforms are inhibited, and the
application has direct access to and
responsibility for all real terminal
features including the character set.
TASKS
The applications programmer implements a transaction
system by writing tasks. A task is a program with a
TA F i n t e r f a c e t h a t p e r f o r m s a s p e c i fi c f u n c t i o n . A
single task or several tasks perform a sequence of
e v e n t s c a l l e d a t r a n s a c t i o n . Ta s k s c a n r e a d a n d
update information on the user's data base. They
can send messages to terminals and receive input.
Ta s k s c a n a l s o s c h e d u l e o t h e r t a s k s t o a s s i s t i n
completing transactions.
Tasks that run under TAF can be written in COBOL,
FORTRAN, or COMPASS. A task differs from a normal
batch or interactive program in that it contains
calls to TAF commands and data manager commands and
must have a common block (referred to as the
c o m m u n i c a t i o n b l o c k ) d e fi n e d . T h e c o m m u n i c a t i o n
block is needed to receive terminal input and pass
data between tasks. (The communication block is
described in section 2.)
Binary copies of each task are stored in the task
library. The LIBTASK utility is used to place these
b i n a r y c o p i e s o n t h e t a s k l i b r a r y. S e c t i o n 1 0
describes the task library and LIBTASK.
Tasks written in COBOL must be compiled with the TAF
parameter on the COBOL command. Tasks written in
FORTRAN must be compiled with the Z parameter on the
FORTRAN command (FORTRAN 4) or with DB=0 on the FTN5
command (FORTRAN 5).
TRANSACTION PROCESSING
After following the login procedures outlined in
appendix J, the user indicates the transaction to be
performed by entering a code that is assigned by the
system designers. Such a code could specify that a
user is entering a loan payment; another code would
be used to close out a loan, and so on. TAF receives
this Initial input and places it in a communication
block. This communication block is the means by
which the data is passed from a terminal to a task
or from task to task.
When a transaction is completed, the communication
block is released and can be used by other
tra n sa cti o n s.
1-4
After the communication block has been constructed,
TA F s c h e d u l e s a n i n i t i a l t a s k ( I TA S K ) t o i n t e r p r e t
the code the user entered. Using this code, ITASK
requests TAF to schedule the appropriate task(s) to
process the transaction. The task scheduled may
also call other tasks to assist in completing the
transaction.
TAF REQUESTS
Communication between terminals and tasks is
accomplished by using TAF requests. Output can be
sent to a transaction terminal from the task by
using the SEND request. When this request is
processed, control passes to TAF. TAF extracts the
message from the task and passes it to the network.
The message is then transmitted to the transaction
terminal, and control passes back to the task for
additional processing.
When a task requires additional input from the
t e r m i n a l , t h e WA I T I N P r e q u e s t i s u s e d . T h e t a s k
performs a SEND request to send output to the
terminal, prompting the terminal operator for the
needed input. The WAITINP request is then
processed. Since the terminal operator takes
seconds to respond to the request, the task is
rolled out of central memory and the subcontrol
point and communication block are released. These
resources can then be used to process other
transactions while the terminal operator is
responding. When TAF receives the requested input,
it places it into a new communication block, and the
task is rolled into an available subcontrol point.
The new communication block is passed to the task,
and the task continues processing.
These and other requests are further described in
sections 2 and 5.
ENTERING THE TRANSACTION SUBSYSTEM
T h e s u b s y s t e m y o u w i l l b e a c c e s s i n g i s t h e TA F
subsystem. There are various procedures for
accessing this transaction subsystem. These methods
are discussed in detail in appendix J. Using
a p p e n d i x J , a c o o r d i n a t o r o f TA F a c t i v i t i e s a t a
particular site who knows the types of users and
applications at the site can determine the most
desirable access procedures.
B e c a u s e o f t h e fl e x i b i l i t y o f t h e n e t w o r k a n d t h e
transaction subsystem, the procedure to access the
transaction subsystem can vary substantially from
site to site. Therefore, the coordinator of
transaction subsystem operations at each site should
p r o v i d e e a c h u s e r, o r t e r m i n a l l o c a t i o n , w i t h a
detailed login procedure for that site.
The site should also provide information concerning
terminal characteristics. A variety of terminal
classes Is supported for use on the network with
60459500 C
TAF. Each of these terminal classes has character
istics, which the analyst can change by modifying the
network files and which you can change by entering
terminal definition commands.
A discussion of the terminal characteristics, the
defaults for each terminal class, and the procedure
for changing these characteristics at a terminal is
included in appendix G.
IMPLEMENTING AN APPLICATION
The following steps specify the procedure for
implementing an application.
1. Review this manual.
2. Design the application including:
• Selection of the data manager (CDCS
and/or CRM, or TOTAL) to allow the
c o r r e c t c h o i c e o f fi l e t y p e s , fi l e
s t r u c t u r e , a n d fi l e i n t e r a c t i o n .
• Selection of recovery and backup
techniques, including journalizing
o f fi l e s .
Refer to the CYBER Database Control System 2
Reference Manuals, the TAF/CRM Data Manager
1 Reference Manual, or the TOTAL - CDC 2
Reference Manual for more information (publi
cation numbers are listed in the preface).
3. Describe and Install the data base using the
data manager. Refer to the appropriate data
manager reference manual for this procedure.
4 . Te s t l o a d t h e d a t a b a s e u s i n g t h e d a t a
manager commands (usually done in batch
mode).
5. Using the application design, write the
application tasks to process transaction
input.
6 . O p t i o n a l l y m o d i f y I T A S K t o r e fl e c t t h e
actual application. Tasks MSABT, LOGT, and
S Y S M S G m a y a l s o r e q u i r e m o d i fi c a t i o n .
(Refer to section 11.)
7 . B u i l d a t a s k l i b r a r y. ( R e f e r t o s e c t i o n 1 0 . )
Ta s k s r e s i d e a t s u b c o n t r o l p o i n t s w i t h i n t h e fi e l d
length of the transaction executive. Each task runs |
with its own exchange package, reference address
( r e l a t i v e t o t h e t r a n s a c t i o n e x e c u t i v e ) , a n d fi e l d
l e n g t h ( a s u b s e t o f t h e fi e l d l e n g t h o f t h e t r a n s
action executive). A task, therefore, can reside in
any contiguous segment within the transaction execu
t i v e fi e l d l e n g t h . M e m o r y i s a l l o c a t e d i n 1 0 0 g
word blocks located on even lOOg word boundaries
(for example, 32100g to 32200s). A subcontrol
point consists of one 120g word block of memory
f o r s y s t e m u s e , f o l l o w e d b y s u f fi c i e n t b l o c k s t o
contain an entire task.
The subcontrol point feature allows the transaction
executive to control each task. Some of the advant
ages associated with the subcontrol points are:
• Isolating one subcontrol point from other
subcontrol points and the transaction
executive. This means that no application
program can destroy the transaction
executive or circumvent system security.
• Blocking RA+1 requests from a subcontrol
point. No requests are allowed directly
from a subcontrol point to NOS. Any such
requests are intercepted by the system
monitors, which return control to the
transaction executive. Thus, the only RA+l
requests a task can legally issue are those
processed by the transaction executive.
This includes requests to the data managers.
The transaction subsystem allows a maximum of 31
subcontrol points. An installation parameter sets
the number of subcontrol points that the transaction
executive initializes. When the transaction
executive is loaded, the operator can select a
number of subcontrol points other fhan this default
value. The number of subcontrol points must not be
less than 2 nor greater than 31. Once the
transaction subsystem is initialized, no change in
the number of subcontrol points is allowed. The
optimum number of subcontrol points is selected by
the site.
Each subcontrol point requires eight words of table
s p a c e . N o s p a c e , o t h e r t h a n a t a b l e e n t r y, i s
allocated for a subcontrol point unless it is
a c t i v e . E a c h a c t i v e s u b c o n t r o l p o i n t h a s 11 l g
words reserved, beginning at RA, similar to those
used for batch control points.
8 . B u i l d a n x x J fi l e . ( R e f e r t o s e c t i o n 4 . )
9 . B u i l d a n e t w o r k fi l e , a n d u s e N D L t o
c o n fi g u r e t e r m i n a l s a n d e s t a b l i s h l o g i n
sequences and terminal characteristics.
1 0 . B u i l d t h e T A F c o n fi g u r a t i o n fi l e ( T C F ) .
(Refer to section 4.)
MULTIMAINFRAME
Under a multimalnframe configuration, the transaction
subsystem can be run on either or both mainframes.
H o w e v e r, a d a t a b a s e a n d J 0 U R 0 fi l e ( s e c t i o n 4 )
cannot be shared by the transaction subsystems.
Each subsystem must have a unique data base.
11. Test th e s y s t e m .
EXTENDED MEMORY
SUBCONTROL POINTS
The following discussion is intended for analysts
and may be omitted by the applications programmer.
TA P d o e s n o t a l l o w t h e u s e o f y o u r a c c e s s t o
extended memory. However, the TAF procedure file
c a n d e c l a r e d a t a fi l e s a n d l i b r a r i e s a s e x t e n d e d
memory-resident.
J#*^
60459500 C
1-5
/^^%\
0^*-
TASK/TRANSACTION EXECUTIVE INTERFACE
A task is isolated from the data manager and the
remainder of the system by the transaction
executive. The isolation guarantees that errors in
a task do not propagate beyond the task. The
following types of requests constitute the interface
between the task and the transaction executive.
• Data manager requests
• Journal file requests
the communication block (refer to the description of
m i n fi g u r e 2 - 1 ) . I f t h e c o m m u n i c a t i o n b l o c k i s
passed between tasks in a transaction and overflow
data is present, other tasks in the transaction can
access this data with a LOADCB request.
If COBOL is used, the communication block must be
described in the COMMON-STORAGE SECTION. Shown here
is an example of such a description:
• Memory dump requests
• System r e q u e s t s
• Task scheduling requests
• Input/output requestst
• Ta s k c o n t r o l r e q u e s t s
• Ta s k u t i l i t y r e q u e s t s
• Application recovery requests
• System recovery requests
0^^
I n t e r n a l l y, a t a s k p e r f o r m s a r e q u e s t b y l o a d i n g
address RA+1 of its subcontrol point. This activity
is not visible to the applications programmer who
uses the macros or calls given In this section. The
transaction executive uses the request parameters to
determine what processing is required by the task.
The address field and any fields in a parameter list
that reference an address contained within the task
are verified to ensure that the address referenced
is within the task field length.
Tasks communicate with each other and accumulate
input by using the communication block. The
communication block is discussed next, followed by
the types of requests.
COMMUNICATION BLOCK
Communication between a chain of tasks is provided
by the communication block. The initial input or
the input from a terminal as a result of the WAITINP
request (refer to Input/Output Requests later in this
section) is also stored in the communication block.
The communication block can be used to pass parame
ters or data from task to task. The format of the
c o m m u n i c a t i o n b l o c k i s s h o w n i n fi g u r e 2 - 1 . T h e
length of terminal input is not restricted by the
length of the communication block. The LOADCB re
quest is available to read extra input that overflows
DATA DIVISION.
COMMON-STORAGE SECTION.
01 COMMUNICATION-BLOCK.
03 CB-HEADER-AREA-WORD-ZERO.
05 CB-OATA-BASE-NAME
05 CB-USER-TST-AREA
05 CB-TRANS SEQ-NUMBER
03 CB-HEADER-AREA-WORD-ONE.
05 CBHJSERNAME
05 CB-INPUT-STATUS-BYTE
05 CB-MESSAGE-WORD-COUNT
03 CB-MESSAGE-AREA
03 USER-AREA
03 CB-TRAILER-AREA.
05 FILLER
05 CB-PACKED-0ATE.
07 CB-YEAR
07 CB-M0NTH
07 CB-DAY
05 CB-PACKED-TIME.
07 CB-H0UR
07 CB-MINUTE
07 CB-SEC0ND
WORKING-STORAGE SECTION.
PIC X(2).
COMP-4 PIC 9C6).
COMP-4 PIC 9(6).
PIC X(7).
COMP-4 PIC 9.
COMP-4 PIC 99.
PIC X(570).
PIC X<90).
PIC X(4).
COMP-4 PIC 9.
COMP-4 PIC 9.
COMP-4 PIC 9.
COMP-4 PIC 9.
COMP-4 PIC 9.
COMP-4 PIC 9.
This will be referred to in the manual as the
standard COBOL communication block because of the
correspondence between it and the fields shown and
d e s c r i b e d i n fi g u r e 2 - 1 . H o w e v e r , a p p l i c a t i o n s
programmers may find it convenient to use a more
abbreviated communication block when possible.
C O M P - 4 i s s p e c i fi e d f o r d a t a a r e a s i n t e n d e d f o r
numerical information. Refer to the COBOL 5 Refer
ence Manual for information on the relationship
b e t w e e n t h e n u m b e r o f d i g i t s s p e c i fi e d i n t h e
picture clause for COMP-4 data and the number of
bits reserved.
TThe standard CMR-supported, compiler-generated I/O calls from FORTRAN and COBOL are not allowed.
SORT verb is not supported.
J ^
60459500 B
The COBOL
2-1
59
1118
WORD 0
47
35
data bate
29
23
user area
WORD 1
20
17
15
13
11
5
id | transaction sequence number
i
usemame
message word count
WORD 2
message area
WORD 67
WORD 68
215g
data base
user area
vr
day
hr
min
Data base that the originating terminal is validated to use.
Image of originating terminal user area from the terminal status table (refer to section
8 ) . C o n t a i n s t h e r e c o v e r y fl a g . ( R e f e r t o t h e TA R O a n d T S I M r e q u e s t s f o r m o r e
information.)
transaction Assigned by the transaction executive to each newly initiated transaction. This number is
sequence number generated by incrementing a counter by one and identifies the transaction, or task chain,
throughout its life in the subsystem.
i d T h e fi r s t o c t a l d i g i t o f t h e t r a n s a c t i o n s e q u e n c e n u m b e r . I t i s t h e
i d e n t i fi e r f o r t h e n e t w o r k fi l e u n d e r w h i c h t h e u s e r r u n n i n g t h i s t r a n s a c t i o n
is defined. The value is zero to seven. .
username
One- to seven-character user name, left-justified with binary zero fill from the terminal
status table.
st
Bit 17 of word 1 is set to one if this communication block was created by a TAF-originated
transaction. Word 2, and possibly 3, of the communication block contains additional in
formation (operating system or network-defined conditions that may be processed by TAForiginated tasks). Refer to section 11 for information concerning required system tasks.
Pt
Bit 16 of word 1 is set to one if this communication contains data on which a parity
error occurred during terminal input.
bt
Bit 15 of word 1 is set to one if this communication block was created by a batch
transaction (BTRAN request).
c
Bit 14 of word 1 is set to one if CDCS aborts.
i
Bit 13 of word 1 is set to one if TAF is idling down.
mt
Bit 12 of word 1 is set to one if additional input to be loaded by means of the LOADCB
request exists.
message
word count
Length of the input message is words in the communication block proper.
•message area
A message from a terminal (as a result of initial terminal input, WAITINP, or BWAITINP re
quests) begins at word 2 and is terminated by 12 bits of zero in positions 11-0 of the
last word of the message. All remaining message area words contain binary zero. The max
imum length of a terminal message is 57 words. This area may also contain data from a
BTRAN request. The maximum length of a BTRAN message is 62 words. In all cases, the
length of the message is in the message word count field. The information contained in
this area is available to you, and its contents is passed to any communication block gen
erated by the processing of a CALLTSK or CALLRTN request. To retain the terminal input,
you may only write in words message word count+2 through 67. If there is no need to
retain the terminal input, the entire area can be used.
yr, mo, day,
hr, min, sec
Date and time in packed binary format from the operating system PDATE macro.
TThe main purpose of these fields is to
the EXTRACT routine allows examination
used to access these fields more easily;
and above. ITASK is described in section
notify the system task ITASK of certain conditions. Under COBOL,
of these fields. Also, a COBOL data type, computational-4, can be
computational-4 data types are allowed only on COBOL Version 5.2
12, and EXTRACT is described later in this section.
Figure 2-1. Communication Block Format
2-2
60459500 B
If FORTRAN is used, the communication block must be
in the first block of labeled common.
If more data is input than can be contained in the
communication block, the LOADCB request may be used
to obtain the input.
COBOL Statements
ACCEPT x FROM DATE.
ACCEPT x FROM TIME.
ACCEPT item FROM TTY.
DISPLAY item UPON TTY.
REQUESTS
The following paragraphs describe the various types
of requests a task can make. They describe task
scheduling, input/output, task control, and task
utility requests and show the formats for making
these requests from tasks written in FORTRAN, COBOL,
and COMPASS.
These requests are described in detail in Volume 4
of the NOS 2 Reference Set, FORTRAN Extended 4
Reference Manual, FORTRAN 5 Reference Manual, and
the COBOL 5 Reference Manual. (Refer to the preface
for publication numbers.)
MEMORY REQUESTS (COMPASS ONLY)
DATA MANAGER REQUESTS
A task can make data manager requests to one of the
data managers, (CDCS, CRM, or TOTAL) supported by
the transaction subsystem. (Refer to the preface
for a list of the publications that document these
data managers and the requests used.)
JOURNAL FILE REQUESTS
A task can supplement automatic journal ing by
w r i t i n g d a t a o n a j o u r n a l fi l e . J o u r n a l fi l e s a n d
the journal requests are discussed in section 4.
MEMORY DUMP REQUESTS
These requests are discussed in section 6.
Tasks can interrogate the status of and change their
central memory (CM) field length (FL) via the RA+1
requests MEM and RFL. The format of these calls is
d o cu me n te d fo r th e MEMORY ma cro i n the NOS 2
Reference Set, Volume 4. The use of these requests
in TAF is restricted as follows:
Memory requests should be issued with the
recall (r parameter); otherwise, control may
be returned before the request is processed.
There is an upper limit beyond which a task is
not allowed to increase its CM space; this
limit is referred to as the maximum task field
length (MFL). The MFL for each task is equal
to the task FL plus the value specified by the
E F L I B TA S K d i r e c t i v e f o r t h e t a s k ( r e f e r t o
section 10). If a task attempts to exceed
this value, it may be aborted (refer to docu
mentation of the MEMORY macro NA parameter in
the NOS 2 Reference Set, Volume 4).
SYSTEM REQUESTS
System requests from transaction tasks are limited
to the following.
COMPASS Macros
ABORT
DATE x
Field length cannot be decreased to less than
the last word address of the default commun
ication block transfer address rounded up to
the nearest 100s«
A non-CM-resident task making a memory request
may be rolled out of CM if the request cannot
b e s a t i s fi e d i n i t i a l l y .
ENDRUN
JDATE x
MEMORY (as described below)
MESSAGE x (to console B display, line one
only)
PDATE x
RTTME x
TIME x
FORTRAN Functions and Subroutine Calls
DATE(x) or CALL DATE(x)
JDATE(x) or CALL JDATE(x)
TTME(x) or CALL TIME(x)
60459500 B
Since a task making a memory request may be
rolled out, it may be desirable to free locked
data manager resources prior to the request.
Tasks will also be allowed to use the common memory
manager (CMM) with the following restrictions:
The processing performed by CMM for the task
must not result in CMM using the fast dynamic
loader or the task will be aborted.
• The preceding restrictions on use of MEM and
RFL requests apply.
Common memory manager requests are documented in
detail in the Common Memory Manager 1 Reference
Manual.
2-3
MESSAGE REQUESTS
COMPASS tasks can issue messages to the operator or
the JOURO file by using the RA+1 request MSG. The
function code determines the disposition of the
message. Function code zero causes the message to
b e w r i t t e n t o o n l y t h e J O U R O fi l e . F u n c t i o n c o d e
one causes the message to be placed in line one of
the B display.
• NEWTRAN
I n i t i a t e s u p t o fi v e n e w t a s k s ( C O M PA S S
only).
• TRANCHK
C h e c k s t o s e e i f a s p e c i fi c t a s k i s a c t i v e
(COMPASS only).
FORTRAN termination messages are also written to the
JOURO file.
COBOL and FORTRAN tasks can issue messages to TAF's
dayfile by using the TMSG request. The tasks that
i ssu e th i s re q u e s t m u s t r e s i d e i n t h e s y s t e m t a s k
l i b r a r y. TA S K L X 6
The TMSG request issues a message to TAF's dayfile.
1 NOTE |
If a list has either no tasks or more
than five tasks, TAF aborts the task
and issues the following error
message on the screen.
TASK REQUEST ARGUMENT ERROR
The format is:
COBOL
ENTER TMSG USING message[.length].
CALLRTN Request
y*^^\
message A 01-level data item containing
the dayfile message.
length A computational-l data item
specifying the length of the
message in characters. The
maximum length is 80 characters.
FORTRAN
CALL TMSG(message,length)
message The name of the array that
contains the dayfile message.
length An integer specifying the length
of the message in characters.
The maximum length is 80
characters.
TASK SCHEDULING REQUESTS
A task, including ITASK (refer to section 11), can
call in order a list of other tasks. This process
is referred to as task scheduling. The following
four requests can be used to schedule tasks.
• CALLRTN
Calls up to five tasks. Upon completion of
the called chain of tasks, returns control
to the calling task.
• CALLTSK
Calls up to five tasks. The task making the
call either ceases or continues to run,
allowing the new task chain to proceed
independently.
2-4
The CALLRTN request is used to request that the
transaction executive schedule a task or series of
tasks, with control returning to the calling task
upon completion of the called tasks. A CALLRTN
request cannot be made while data manager requests
are outstanding. The current communication block is
passed to the called tasks and returned to the
caller when the caller is reinitiated. Upon return,
the caller begins execution immediately after the
CALLRTN request. Only the information in the
communication block may have changed. Return from
the called tasks to the caller takes place
automatically after the last called task ceases. A
task waiting for return may be temporarily rolled
from memory.
The format is:
COBOL
ENTER CALLRTN USING task! task2«..taskn.
task^ Parameter whose value Is a oneto s e v e n - c h a r a c te r a l p h a numeric
task name. The tasks are
scheduled by CALLRTN in the
o r d e r s p e c i fi e d . F r o m o n e t o
five tasks can be specified.
FORTRAN
C A L L C A L L RT N ( t a s k l , t a s k 2 t a s k n )
taski Parameter whose value is a oneto s e v e n - c h a r a c te r a l p h a numeric
t a s k n a m e , l e f t - j u s t i fi e d w i t h
e i t h e r b l a n k o r b i n a r y z e r o fi l l
t o a w o r d b o u n d a r y. T h e t a s k s
are scheduled by CALLRTN in the
o r d e r s p e c i fi e d . F r o m o n e t o
five tasks can be specified.
60459500 C
communication block back to the calling task and
allow it to continue execution at the instruction
immediately following the CALLRTN command.
COMPASS
CALLRTN address
address Address of a list of from one to
five task names. Each task name
m u s t b e l e f t - j u s t i fi e d w i t h
b i n a r y z e r o fi l l t o a w o r d
b o u n d a r y.
The
list
is
terminated by a word of binary
z e r o s . Ta s k s a r e s c h e d u l e d b y
CALLRTN in the order they appear
on the list.
1'
1
1
1
1
1
1
1
TASK
A
1 *
1 —
#■
C.B.
CALLRTN
NEXT
INST.
("note"!
CB.
1
I f t a s k i , s p e c i fi e d o n a C A L L R T N
request, makes a CALLRTN request,
taskj + 1 through task,,, speci
fied on the original CALLRTN request,
a r e n o t s c h e d u l e d . ( R e f e r t o fi g u r e
2-4.)
I
TASK
8
■— v. ,
a>
C8.
TASK
CS.
TASK
O
c
/ ^ v
The following diagrams illustrate CALLRTN processing.
JS»\
I n fi g u r e 2 - 2 , T A S K A , a t s u b c o n t r o l p o i n t X ,
executes a CALLRTN to TASK B. TAF will first load a
c o p y o f TA S K B t o a n a v a i l a b l e s u b c o n t r o l p o i n t
( u n l e s s a s e r i a l l y r e u s a b l e c o p y o f TA S K B i s
already at a subcontrol point or CM-resident). TAF
w i l l t h e n c o p y t h e c o n t e n t s o f TA S K A ' s
communication block (CB) to TASK B's communication
block area. TASK B begins execution. When TASK B
h a s c o m p l e t e d e x e c u t i o n , TA F w i l l c o p y t h e
communication block, which was probably modified by
TASK B, back to TASK A and allow TASK A to continue
execution at the instruction immediately following
the CALLRTN command.
1
1
!
Figure 2-4 illustrates the processing referred to in
the preceding note. The majority of the data inputs
are handled by the TASK B-C-D chain. When an excep
t i o n i s f o u n d i n TA S K C , e x c e p t i o n p r o c e s s i n g i s
invoked in the TASK E-F chain. Each new CALLRTN
command cancels the previous one (TASK D is not
executed), but TAF will always bring control back to
the instruction immediately following the original
CALLRTN command (TASK A). The communication block
is passed from task to task as shown in figures 2-2
and 2-3.
TAF
CB.
MAIN
PROCESSING
PATH
4
1
1
1
Figure 2-3. CALLRTN (Chain)
/
1/
•»
CS.
TASK A
> ALTERNATE
PROCESSING
PATH
CS.
TASK a
CALLRTN
NEXT
INST.
SUBCONTRO
POINT X
J SUMONTROL
POINT Y
-1
TASK |
B .
TASK
A
I
_*_
TASK
E
CALLRTN
NEXT
INST.
CALLRTN
NEXT
INST.
i
L_J
task]
^r
TASK
F
Figure 2-2. CALLRTN
TASK I
D I
The CALLRTN command allows a chain (list) of up to
five tasks to be called. Figure 2-3 shows TASK A
calling a chain of three tasks. As each task in the
chain is completed, TAF will automatically pass the
communication block to the next task in the chain
and allow that task to execute. When the last task
i n t h e c h a i n h a s c o m p l e t e d , TA F w i l l p a s s t h e
/|P"v
60459500 B
Figure 2-4. CALLRTN (Multiple Chains)
2-5
CALLTSK Request
The CALLTSK request is used to request that the
transaction executive schedule a task or series of
tasks (task chain). Included in this request is a
parameter option that enables task branching or a
CEASE function to be performed after the call is
honored. If the task is not to cease on this call,
a branching of the chain initiates a new chain that
is Independent of the original chain. The new chain
is assigned a new sequence number for unique
i d e n t i fi c a t i o n w i t h i n t h e t r a n s a c t i o n s u b s y s t e m
(figure 2-1). The number of branches allowed by a
transaction is controlled by an assembly constant
MAXBW. If a CALLTSK request without a CEASE request
is issued from a recoverable transaction, recovery
may be affected. Refer to CALLTSK without CEASE and
Recovery in section 7.
code
Integer whose value is nonzero
if the calling task is to con
tinue after the request, initiat
ing an independent task chain.
If the value of this parameter
is zero, the calling task ceases
after this request. If not
s p e c i fi e d , t h e d e f a u l t i s z e r o .
task*
Parameter whose value is a oneto s e v e n - c h a r a c te r a l p h anumeric
t a s k n a m e , l e f t - j u s t i fi e d w i t h
e i t h e r b l a n k o r b i n a r y z e r o fi l l
t o a w o r d b o u n d a r y. F r o m z e r o
t o f o u r t a s k s c a n b e s p e c i fi e d .
These tasks are scheduled after
t h e o n e s p e c i fi e d i n t h e t a s k
parameter.
COMPASS
The format is:
C A L LT S K a d d r e s s , c e a s e
COBOL
address Address of a list of from one to
five task names. Each task name
o u s t b e l e f t - j u s t i fi e d w i t h b i n a
ry zero fill to a word boundary.
The list is terminated by a word
of binary zeros. CALLTSK sched
ules the tasks in the order they
appear on the list.
ENTER CALLTSK USING task code task1#. .tas^.
task Parameter whose value is a oneCo seven-character alphanumeric
task name. This task is the
next task to call in the present
task chain (same sequence
number) if code is set to zero;
o t h e r w i s e , i t i s t h e fi r s t t a s k
of a branch chain (the called
t a s k g e t s a d i ff e r e n t s e q u e n c e
number and proceeds independently
of the calling task).
code Computational-l item whose value
is nonzero if the calling task
is to continue after the
request,
initiating
an
independent task chain. If the
value of this parameter is zero,
the calling task ceases after
this request. This parameter
must be specified.
task^ parameter whose value is a oneto seven-character alphanumeric
task name. From zero to four
t a s k s c a n b e s p e c i fi e d . T h e s e
tasks are scheduled after the
o n e s p e c i fi e d i n t h e t a s k
parameter.
c e a s e I f s p e c i fi e d , t h e c a l l i n g t a s k
ceases after this request. If
n o t s p e c i fi e d , t h e c a l l i n g t a s k
continues after the request. In
this case the CALLTSK initiates
an independent task chain.
The following figures illustrate CALLTSK processing.
Figure 2-5 shows TASK A making a CALLTSK with a CEASE
request to TASK B. TAF will load a copy of TASK B to
an available subcontrol point (this step is not nec
essary if a serially reusable copy of TASK B is al
ready at a subcontrol point or is CM-resident). The
communication block will be copied from TASK A to
TASK B. TASK A's subcontrol point is released for
use by other transactions, and TASK B is allowed to
begin execution.
CS.
TASK
A
FORTRAN
xsH
TA F
X
CALLTSK
Nx
CALL CALLTSK(task,code,taskj,..., task^
task Parameter whose value is a oneto seven-character alphanumeric
t a s k n a m e , l e f t - j u s t i fi e d w i t h
e i t h e r b l a n k o r b i n a r y z e r o fi l l
t o a w o r d b o u n d a r y. T h i s t a s k
is the next task to call in the
present task chain (same
sequence number) if code is set
to zero; otherwise, it is the
fi r s t t a s k o f a b r a n c h c h a i n
(the called task gets a
d i ff e r e n t s e q u e n c e n u m b e r a n d
proceeds independently of the
calling task).
2-6
CS.
-l,«»*"
1'
CB.
^ *****
TASK
B
Figure 2-5. CALLTSK with CEASE Request
60459500 B
/ $ ^ N
The CALLTSK without a CEASE request allows a new
a s y n c h r o n o u s c h a i n t o b e s t a r t e d . I n fi g u r e 2 - 6 ,
TASK A uses this command to call TASK B. TAF will
copy the contents of TASK A's communication block to
a new communication block. A copy of TASK B will be
loaded to an available subcontrol point (unless a
s e r i a l l y r e u s a b l e c o p y o f TA S K B i s a l r e a d y a t a
subcontrol point or is CM-resident). The new
communication block will be copied to TASK B. TASK
A is allowed to continue execution and TASK B is
allowed to begin execution.
TAF
CS.
NEW CB.
r—
CB.
CALLTSK
NEXT
INST.
TASK
A
TASK
B
I
NEWTRAN Request (COMPASS Only)
The NEWTRAN request initiates a new transaction
chain with a unique sequence number and with the
data base, user area, and user name set to zero in
the communication block. The NEWTRAN request is
designed for system use, primarily by ITASK, and is
provided only for COMPASS.
The format is:
COMPASS
NEWTRAN address
address Address of a parameter table in
the form shown in figure 2-7.
Figure 2-6. CALLTSK without CEASE Request
23
59
V/MMfr^
^
^
^
^
^
^
^
^
^
^
,
0
sequence
task|
J*5^
**t
*#
9
task
0
seqtjence
The transaction executive returns a new 24-bit binary transaction sequence number
i n t h i s fi e l d .
tasl
O n e - t o s e v e n - c h a r a c t e r t a s k n a m e , l e f t - j u s t i fi e d w i t h b i n a r y z e r o fi l l . F r o m
one to five tasks can be specified; the list is terminated by a word of binary
zeros. NEWTRAN schedules the task In the order they appear on the list.
Figure 2-7. NEWTRAN Parameter Table
60459500 B
2-7
TRANCHK Request
BLDABH
The TRANCHK request determines the status of a
transaction. This request is provided only for
COMPASS.
Builds the application block header to use
different character types, terminal format
effectors, and auto input.
/■S
fSsV
• GETABH
The format is:
COMPASS
Returns the last application block header to
the task.
TRANCHK address
address
Address of a parameter table in
the form shown in figure 2-8.
• TERMDEF
D e fi n e s t h e o p e r a t i o n a l c o n t r o l s o r f o r m a t
of the terminal.
INPUT/OUTPUT REQUESTS
• SEND
The following requests are associated with
input/output.
Sends data to terminal. Equivalent to a
write request.
• WA I T I N P
Places terminal input data in the
communication block. Equivalent to a read
request.
• RELSCB
Releases memory used for extra communication
blocks.
, 0 The time delay elapsed
before input was received
from the terminal.
time
NOTE
CM-resident tasks and tasks not asso
c i a te d w i t h a t e r m i n a l ( b a t c h o r i g i n )
are not permitted to make a WAITINP
request (task aborts).
At least one message (SEND) must be
sent to the terminal before making a
WAITINP request, and at least one SEND
request from the original task chain
must follow a message received follow
ing a WAITINP request.
Computational-l item that con
tains the time limit, in decimal
seconds, to wait for input. If
not specified, the default is 480
seconds. The maximum value is
2048 seconds.
FORTRAN
CALL WAITINP(status,time)
status
Integer variable that the system
sets to indicate the status of
the WAITINP request. Upon com
pletion of the request, status
has one of the following values.
No data manager requests may be active
when a task makes a WAITINP request.
All tasks that make WAITINP requests
must be entered in the task library
with the scheduling queue limit set
to one. (Refer to section 10.)
0 The request processed
normally; terminal input
appears in the normal
Input portion (begins in
the third word) of the
communication block.
WAITINP does not cause any data mana
ger cease requests to be Issued.
Therefore, any resources locked or
reserved by a transaction prior to a
WA I T I N P c o n t i n u e t o b e L o c k e d o r
reserved during and after the WAITINP.
< 0 Another task is waiting
for input from the origi
nating terminal. The
WAITINP request must be
reissued if input is
desired.
60459500 C
2-9
> 0 The time delay elapsed
before input was received
from the terminal.
time Integer time limit, in decimal
seconds, to wait for input. If
n o t s p e c i fi e d , t h e d e f a u l t i s
480 seconds. The maximum value
is 2048 seconds.
COMPASS
The overflow data can be requested as many times
during a transaction as desired. Each time, the
overflow data is transmitted as specified previously.
^^\
The format is:
COBOL
ENTER LOADCB USING buffer status r.
buffer
A 01-level item identifying the
user-defined buffer area.
status
Computational-l item that the
system sets to indicate the
LOADCB equest status. The
s i g n i fi c a n c e o f t h e v a l u e s e t
has been described earlier in
the LOADCB request description.
WAITINP time
time
Ti m e l i m i t , i n d e c i m a l s e c o n d s ,
to wait for input. If not
s p e c i fi e d , t h e d e f a u l t i s 4 8 0
seconds. The maximum value is
2048 seconds.
Computational-l item. If a non
zero value is entered for this
parameter, any message data that
overflows the LOADCB buffer spec
i fi e d w i t h t h e b u f f e r p a r a m e t e r
is released (same as RELSCB).
Status of the WAITINP macro is determined by the
following:
• Word 2 of the communication block contains 1
if the time delay elapsed before input was
received from the terminal.
FORTRAN
• The X6 register contains a negative value if
another task is waiting for input from the
o r i g i n a t i n g t e r m i n a l . T h e WA I T I N P r e q u e s t
must be reissued if input is desired. (Word
2 of the communication block should be
checked before X6 is checked.)
• The X6 register is set to zero if the request
processed normally; terminal input appears in
the normal input portion (begins in the third
word) of the communication block. (Word 2 of
the communication block should be checked
before X6 is checked.)
LOADCB Request
If the transaction input data exceeds the message
area of the communication block, bit 12 of word 1 of
t h e c o m m u n i c a t i o n b l o c k ( t h e i fi e l d ) i s s e t . T h e
LOADCB reque s t l o a d s t h e r e m a i n d e r o f t h e i n p u t
m e s s a g e i n t o a u s e r - d e fi n e d b u ff e r. T h i s b u ff e r i s
a single contiguous block of storage for all
additional communication blocks. No headers or
trailers appear In this area.
The maximum input size is determined by an installa
tion parameter.
The data that remains after the communication block
m e s s a g e a r e a fi l l s ( r e f e r r e d t o h e r e a s o v e r fl o w
d a t a ) i s t r a n s f e r r e d t o t h e u s e r - d e fi n e d b u f f e r. I f
the LOADCB request is made with no data overflow (i
field not set) or if a RELSCB request was made prior
to the LOADCB request, no data is transferred and the
s t a t u s w o r d i s s e t t o z e r o . I f t h e o v e r fl o w d a t a
consists of more words than will fit in the buffer,
t h e b u ff e r i s fi l l e d , a n d t h e s t a t u s w o r d i s s e t t o
a value greater than the number of words in the
b u f f e r. I f t h e o v e r fl o w d a t a c a n b e c o n t a i n e d i n
t h e b u ff e r, t h e o v e r fl o w d a t a i s t r a n s f e r r e d t o t h e
buffer, and the number of words transferred is set
in the status word.
2-10
CALL L0ADCB(buffer,length,status,r)
buffer An array identifying the userdefined buffer area.
length Integer length of the array spec
i fi e d w i t h t h e b u f f e r p a r a m e t e r
in words.
s t a t u s Va r i a b l e t h a t t h e s y s t e m s e t s t o
Indicate the LOADCB request
s t a t u s . T h e s i g n i fi c a n c e o f t h e
value set has been described
earlier in the LOADCB request
description. This value is also
returned as the value of the
function, if LOADCB is called as
a FORTRAN function.
r
Integer variable. If a nonzero
value is entered for this param
eter, any message data that over
flows the LOADCB buffer specified
with the buffer parameter is
released (same as RELSCB).
As stated in the description of the status
parameter, the LOADCB request can be referenced as a
FORTRAN function. The format of the function is
LOADCB(buffer,length,status ,r); the parameters are
the same as those already described. The value of
the function is the value of the status parameter.
COMPASS
LOADCB address
address
Address of a parameter table in
the format shown in figure 2-9.
The LOADCB macro status is returned in the X6 regis
ter. The significance of the value returned has been
described earlier in the LOADCB request description.
60459500 B
/S^.
The format is:
SETCHT Request
COBOL
The SETCHT request allows a task to change the appli
cation character type (ACT) of terminal messages
placed in the communication block.
ENTER SETCHT USING username status act.
username
A 01-level item containing a
one- to seven-character user
n a m e , l e f t - j u s t i fi e d w i t h b l a n k
fill. The user name may also be
s p e c i fi e d w i t h a c o m p u t a t i o n a l - l
i t e m w i t h b i n a r y z e r o fi l l . I f
the item contains only binary
zeros, the character type
applies to the originating
terminal. This user name must
be a name appearing in an NCTFi
fi l e . A u s e r n a m e c o n s i s t i n g o f
the character P with binary zero
fi l l c a n n o t b e s p e c i fi e d .
status
Computational-l item whose value
i s s e t b y TA F t o i n d i c a t e u s e r
name status. This value is zero
if the user is not logged in and
o n e i f t h e r e q u e s t i s processed
n o r m a l l y. T h e t a s k i s a b o r t e d
if the user name is not defined
or if the data base for the
s p e c i fi e d u s e r d o e s n o t m a t c h
the data base of the originating
u s e r.
act
A 01-level item containing one
of
the
following
words,
l e f t - j u s t i fi e d .
rNOTTI
This is an optional request; the de
fault character type is 6-bit display
code characters.
The following character types are available.
• 7-bit ASCII, seven and one-half characters
per word.
• 7-bit ASCII characters, right-justified in
12-bit bytes, five characters per word.
• 6-bit display code characters, 10 characters
per word.
This request causes TAF to send a change input char
acter type supervisory message to NAM. For more
information about supervisory messages, refer to the
NAM/CCP Reference Manual.
NOTE
This request does not change the data
currently held in communication
blocks for the task. For example, a
LOADCB request gets data in the
former character type, while the next
WAITINP request gets data in the new
character type.
ASCII7 7-bit ASCII. Seven
and one-half char
acters per word.
ASCIIS 7-bit ASCII, rightj u s t i fi e d i n 1 2 - b i t
bytes, five charac
ters per word.
If 7-bit ASCII characters are used to
originate transactions, ITASK transac
tion tables must be set up in terms
of ASCII and not display code.
59
r
WatM
47
DISPLAY 6-bit display code.
29
length
'v
2-15
TERMDEF Request
A l e f t - j u s t i fi e d 0 1 - l e v e l i t e m
w i t h b i n a r y z e r o o r b l a n k fi l l ,
containing the characteristic
(for example, PW»60, PL»35, or
CN-2B). A maximum of 17 nonblank, nonbinary zero characters
is allowed. The characteristics
are described in the NAM/CCP
Reference Manual and appendix G
of this manual. If the NAM/CCP
Reference Manual specifies x or
h, a 6-bit display code alphanu
meric representation is required
(where x is a 7-bit ASCII charac
ter and h is a hexadecimal
character).
fi e l d i
The TERMDEF request can be used by a task to define
or modify terminal characteristics, where those of
the connected real terminal differ from the assump
tions made for the network's IVT model. This request
can also be used to tailor the operational controls
of the terminal.
I note"!
This is an optional request. Terminal
input and output can be done without
it. Each terminal that logs into the
network is associated with a default
set of terminal characteristics. (Re
fer to appendix G.)
FORTRAN
C A L L T E R M D E F ( u s e r n a m e , s t a t u s , fi e l d } ,
A complete list of terminal characteristics is pro
vided in the NAM/CCP Reference Manual and appendix G
of this manual. Characteristics that may be modified
include:
• Te r m i n a l p h y s i c a l p a g e w i d t h .
• Number of physical lines on a terminal page.
• Specification of a character used to cancel
an input logical line in progress.
• Specification of a character to be used as a
b r e a k c h a r a c t e r. U s e r b r e a k s a r e s e n t t o
the application task for processing.
• Set transparent input mode. This setting
exists for only one logical input line.
The format is:
COBOL
ENTER TERMDEF USING username status field}
fi e l d 2 . . . fi e l d n .
fi e l d 2 , . . . , fi e l d n )
username Parameter whose value is a oneto seven-character user name,
l e f t - j u s t i fi e d w i t h b i n a r y z e r o
o r b l a n k fi l l . I f t h e u s e r n a m e
i s z e r o , t h e t e r m i n a l d e fi n i t i o n
s p e c i fi e d a p p l i e s t o t h e o r i g i
n a ti n g te rmi n a l . Th i s u ser name
must be a name appearing in an
N C T F i fi l e .
s t a t u s Va r i a b l e i n w h i c h TA F p l a c e s a n
u n n o r m a l i z e d fl o a t i n g - p o i n t n u m
ber to indicate user name status.
status contents is zero if the
user is not logged in and greater
than zero if the request is proc
e s s e d n o r m a l l y. T h e t a s k i s
aborted if the user name is not
d e fi n e d o r i f t h e d a t a b a s e f o r
the user does not match the data
base of the originating user.
fi e l d i
username A 01-level item containing a
one- to seven-character user
n a m e , l e f t - j u s t i fi e d w i t h b l a n k
fill. The user name may also be
s p e c i fi e d w i t h a c o m p u t a t i o n a l - l
i t e m w i t h b i n a r y z e r o fi l l . I f
the item contains only binary
z e r o , t h e t e r m i n a l d e fi n i t i o n
s p e c i fi e d a p p l i e s t o t h e
originating terminal. This user
name must be a name appearing in
a n N C T F i fi l e . A u s e r n a m e
consisting of the character P
w i t h b i n a r y z e r o fi l l c a n n o t b e
s p e c i fi e d .
s t a t u s C o m p u t a t i o n a l - l i t e m t h a t TA F
sets to indicate user name
status, status contents is zero
if the user is not logged in and
is one if the request is
processed normally. The task is
aborted if the user name is not
d e fi n e d o r i f t h e u s e r ' s d a t a
base does not match the data
base of the originating user.
2-16
A
l e f t - j u s t i fi e d v a r i a b l e w i t h
b i n a r y z e r o o r b l a n k fi l l , c o n
taining the characteristic (for
example, PW-60, PL=35, or CN=2B).
A maximum of 17 nonblank, nonbinary zero characters is
allowed. The characteristics
are described in the NAM/CCP
Reference Manual and appendix G
of this manual. If the NAM/CCP
Reference Manual specifies x or
h, a 6-bit display code alpha
numeric representation is
required (where x is a 7-bit
ASCII character and h is a
hexadecimal character).
Example:
The following request designates the page width
to be 60 characters, the page length to be 40
lines, and the plus character (ASCII representa
tion is 2B) to be the cancel character for user
USER5; it then assigns the status to variable
STATUS.
CALL TERMDEFC5HUSER5,STATUS,5LPW=60,
5LPL=40,5LCN=2B>
60459500 B
y£-»!S\
f^
There is both a limit on the total output that one
task can send (MAXTO), t and a limit on the output
one task can send before it is rolled out, pending
the transfer of the output to the terminal or
terminals (MLIM).t Also, the maximum output length
for one SEND request is determined by the MAXWSt
I n s t a l l a t i o n p a r a m e t e r.
Example:
T h e f o l l o w i n g s t a t e m e n t s r e d e fi n e t h e
transparent input mode text delimiter to be a
slant (ASCII representation is 2F) and the
character count delimiter to be 4096.
DATA MSG/10HDL=X2F,C40,2L96/
A task can specify the status parameter in COBOL and
FORTRAN or the r parameter in COMPASS so that the
task will wait until the network acknowledges that
t h e m e s s a g e h a s b e e n d e l i v e r e d t o t h e u s e r. I f
recall is selected, any error detected on the output
message causes the task performing the SEND request
to be restarted. Therefore, tasks performing SEND
requests with recall should check status and
compensate for errors. Use of recall can simplify
recovery since the task issuing the SEND request is
i n f o r m e d o f t h e p r o b l e m a t t h e fi r s t a d d r e s s a f t e r
the SEND. When recall is selected, the task is
rolled out if the message length exceeds the MLIM
i n s t a l l a t i o n p a r a m e t e r. A n y d a t a m a n a g e r resources
held by the task, such as locked records, remain
assigned for the duration of the rollout. If
reserving these resources for this period of time
will impact the performance of the application,
t a s k s s h o u l d r e l e a s e a l l fi l e a n d r e c o r d l o c k s
before executing the SEND request.
CALL TERMDEF(5HUSER5,STATUS,MSG>
END
COMPASS
TERMDEF address
address Address of a parameter table in
the format shown in figure 2-12.
SEND Request
The SEND request sends a message to a user; that is,
it performs a write operation. If the task does not
specify the user to which the message should be
sent, it is directed to the terminal that originated
the transaction. At least one SEND request to the
originating terminal must occur from the primary
task chain for each message received. The task can
also specify that the task be ended when the message
is sent.
59
I f r e c a l l i s n o t s e l e c t e d , I TA S K i s i n f o r med of the
problem, rather than the task that issued the
request. ITASK is informed because the issuing task
may have already terminated when the message
delivering problem is detected.
17
43
//^
username
yyyyyyyyyyy
y / f fl f fl $ y
WWk
W,
11
Wa
ec
status
string
z
string + n
O n e - t o s e v e n - c h a r a c t e r u s e r n a m e , l e f t - j u s t i fi e d w i t h b i n a r y z e r o fi l l . I f t h e
u s e r n a m e i s b i n a r y z e r o , t h e t e r m i n a l d e fi n i t i o n s p e c i fi e d a p p l i e s t o t h e
o r i g i n a t i n g u s e r.
The number of 7-bit ASCII characters (at seven and one-half characters per word)
is available in string + 2. Adding two is necessary because string begins in bit
43. If no characters are specified in the string, cc should equal two.
status
An address of a word in which TAF returns the user name status in unnormalized
fl o a t i n g - p o i n t f o r m a t . T h e s t a t u s c o n t e n t s i s z e r o i f t h e u s e r i s n o t l o g g e d i n
and greater than zero if the request is processed normally. The task is aborted
if the user name is not defined or if the data base for the user does not match
the data of the originating user.
string
A s t r i n g o f 7 - b i t A S C I I c h a r a c t e r s , i n h e x a d e c i m a l n o t a t i o n , l e f t - j u s t i fi e d i n
the field, defining the terminal characteristic. (Refer to the NAM/CCP Reference
Manual for a list of these characteristics.) As an example, to change the cancel
key to a +, the string CN«*f is written as 434E3D2B. string + n is the last word
needed for the string.
Figure 2-12. TERMDEF Parameter Table
^
^
K
tRefer to the NOS 2 Installation Handbook (refer to the preface for the publication number)
60459500 B
2-17
The format of the message on the terminal depends on
t h e t e r m i n a l c l a s s a n d t h e f o r m a t e ff e c t o r s i n t h e
message. For example, on synchronous terminals the
cursor for entering the next message to the host
( u p l i n e ) i s a l w a y s t h e fi r s t c h a r a c t e r o f t h e l i n e .
On asynchronous terminals the cursor follows the
last character of output; this assumes no format
effectors are in the message. The NAM/CCP Reference
Manual contains complete information on terminal
protocols.
The format is:
FORTRAN
CALL SEND(messageaddress,length,username,
c e a s e - fl a g . o u t p u t - fl a g , b l o c k , s t a t u s )
The parameters are described in table 2-4.
COMPASS
SEND address
address
COBOL
ENTER "SEND" USING messageaddress username
cease-flag output-flag block status length.
The parameters are described in table 2-3.
NOTE
Under COBOL, SEND must be enclosed in
quotation marks, because SEND is a
reserved word for that compiler.
Address of a parameter table in
the format
s h o w n i n fi g u r e
2-13. This
fi g u r e a n d t h e
parameters in t a b l e 2 - 5 s h o u l d
be used with t a b l e 2 - 6 . T h i s
table shows
interrela tionships
between SEND
parameters.
Setting parameters shown in the
top portion of table 2-6 results
in the corresponding events
shown in the bottom portion.
The entire four-word block must be present, even
if the last three words are not used.
Table 2-3. COBOL SEND Request Parameters (Sheet 1 of 2)
Parameter
Data Type
Value
messageaddress
01-level display item
Data item containing the message to be sent. For 7-bit
ASCII character types, the message must have an end-ofline byte of the single character US for all logical
lines. (Refer to the NAM/CCP Reference Manual for NAM
data formats.) The TAF SEND interface supplies end-ofline bytes for 6-bit display code character types only.
username
01-level display item,
or computational-l
Data item containing a one- to seven-character user
name. If this parameter is omitted or specified as
C0MP-1 VALUE ZERO, the message is sent to the originat
ing terminal. This user name must be a name appearing
in the NCTFi file and must be validated for the same
data base as the sending task.t A user name consisting
of the character P with binary zero fill cannot be
specified. The user name can be binary zero or blankfi l l e d .
cease-flag
Computational-l
Task end flag.
Description
0, omitted
The task continues after the message is sent.
1
The task ends after the message is sent.
/^B5X
tTasks associate d with application identifier SY can SEND to any valid TAF user.
2-18
60459500 B
Table 2-3. COBOL SEND Request Parameters (Sheet 2 of 2)
Parameter
Data Type
o u t p u t - fl a g
Computational-l
Application block type. Currently serves no function.
Retained for compatibility with previous releases.
block
Computational-l
Application block number (ABN) data name.
status
length
J
^
60459500 C
Value
Nonzero
TAF uses the value contained in the data name as the
ABN.
0
TAF assigns the ABN and returns this as the value in
this data name.
Omitted
TAF assigns the ABN, and the value is not returned.
Recall flag; this parameter applies only if the ceaseflag is set to zero.
Computational-l
Computational-l
Description
0, omitted
The task begins processing after the block is transmit
ted to the network.
Nonzero
The task begins processing after the block has been de
livered to the user and acknowledgment is received.
Each nonzero value indicates the status of the block.
The network function, subfunction, and description are
given here. For all values other than 1, the block was
not delivered to the user and the task must recover.
I
Block delivered (FC/ACK).
2
Block not delivered (INTR/USR/RC-1).
3
User break 1 (INTR/USR/RC-1).
4
User break 2 (INTR/USR/RC-1).
10
Terminal not logged in (CON/END).
11
Correspondent unavailable or failed, line disconnect
(C0N/CB/RC-1).
Length of the message in characters. This length
should Include end-of-line bytes for 7-bit ASCII char
acter types. For 6-bit display code output, the COBOL
compiler-generated length is used if the length param
eter is omitted.
2-19
Table 2-4. FORTRAN SEND Request Parameters (Sheet 1 of 2)
Parameter
Data Type
Value
Description
messageaddress Hollerith or leftj u s t i fi e d , z e r o fi l l
Array name containing the message to be sent. For
7-bit ASCII character types, the message must have an
end-of-line byte of the single character US for all
logical lines. (Refer to the NAM/CCP Reference
Manual for NAM data formats.) The TAF SEND interface
supplies end-of-line bytes for 6-bit display code
character types only.
length
Integer
Length of the message in characters. This length
should include the end-of-line bytes for 7-bit ASCII
character types.
username
L e f t - j u s t i fi e d ,
z e r o o r b l a n k fi l l
integer
One- to seven-character user name. This must be a
name appearing in the NCTFi file, which is validated
for the same data base as the task issuing the send.t
I f t h i s p a r a m e t e r i s o m i t t e d o r s p e c i fi e d a s b i n a r y
zero, the message is sent to the originating terminal.
cease-flag
Integer
Task end flag.
0, omitted
The task continues after the message is sent.
1
The task ends after the message is sent.
o u t p u t - fl a g
Integer
Application block type. Currently serves no function.
Retained for compatibility with previous releases.
block
Integer
Application block number.
Nonzero
TAF uses the value of this variable as the ABN.
0
TAF assigns the ABN and returns the value in this var
i a b l e . F o r t h i s p a r a m e t e r, y o u s h o u l d e n t e r a n
i n t e g e r v a r i a b l e a s s i g n e d t h e v a l u e z e r o i n s t e a d of
entering zero, as follows:
INTEGER ABN
ABN=0
CALL SEND(messageaddress,length,username/
c e a s e - fl a g , o u t p u t - fl a g , A B N , s t a t u s )
Omitted
status
Unnormalized
fl o a t i n g p o i n t
TAF assigns the ABN, and the value is not returned.
R e c a l l fl a g ( a p p l i e s o n l y i f c e a s e - fl a g i s s e t t o
zero.
0, omitted
The task begins processing after the block is trans
mitted to the network.
Nonzero
The task begins processing after the block has been
delivered to the terminal and acknowledgment is
received. Each nonzero value indicates the status of
the block. The network function, subfunction, and
description are given here. For all values other
than 1, the block was not delivered to the terminal
and the task must recover.
Block delivered (FC/ACK).
Block not delivered (FC/NAK/RC-l).
User break 1 (INTR/USR/RC-1).
User break 2 (INTR/USR/RC-1).
tTask associated with application identifier SY can SND to any valid TAF user.
2-20
60459500 C
0^
Table 2-4. FORTRAN SEND Request Parameters (Sheet 2 of 2)
Parameter
Data Type
Value
Description
10
Terminal not logged in (CON/END).
11
Correspondent unavailable or failed, line disconnect
(C0N/CB/RC-1).
Table 2-5. COMPASS SEND Request Parameters (Sheet I of 2)
Parameter
Bits
t
59
c
Description
Te r m i n a l fl a g .
0
Message is sent to originating terminal.
1
Message is sent to specified user.
58
Task cease flag.
0
The task cease is not performed.
1
The task cease is performed following the SEND request.
o
57
No function. Retained for compatibility with previous releases.
b
56
Return block flag.
r
a
J^v
Value
60459500 C
0
If a is set to one, the task assigns the block number via the abn
fi e l d . I f a i s s e t t o z e r o , TA F a s s i g n s t h e b l o c k n u m b e r, a n d t h e
number is not returned in the block field.
1
TAF assigns the block number and returns this number in the block
fi e l d .
55
R e c a l l fl a g .
0
TAF does not wait for the block to be delivered to the terminal.
1
TAF waits for the block to be delivered to the terminal.
54
Application block header flag.
0
TAF generates the application block header but does it in its own
area without making use of or changing word 3 of the parameter table
shown in figure 2-8. (Refer to the description of the BLDABH request
for the default values TAF uses.) Because a BLDABH request is not
available to COMPASS tasks, the header TAF supplies when a=0 always
h a s d e f a u l t v a l u e s , e x c e p t f o r a t i c i n fl u e n c e d b y n u m w o r d s .
S p e c i fi c a l l y, i f a i s s e t t o z e r o , t h e t a s k c a n o n l y o u t p u t i n 6 - b i t
display code, cannot use format effectors, cannot use auto-input
mode, and cannot preset the application block number.
I
The task supplies the application block header. (The task supplies
the ABH in the third word SEND parameter table shown in figure 2-8,
with parameters shown in table 2-6.)
2-21
Table 2-5. COMPASS SEND Request Parameters (Sheet 2 of 2)
Parameter
Bits
Value
messageaddress
47-30
Address of message. For 6-bit display code character type, the
message must contain an end-of-line byte from 12 to 66 bits of
zero. For 7-bit ASCII characters, the message must have an end-ofline byte of the single character US for all logical lines in the
output block. (Refer to the NAM/CCP Host Application Programmers
Reference Manual.)
numwords
17-0
Number of words in the message. If the a field is set to one, this
field is not used. The tic field must be used to specify the mes
sage length. The numwords field must contain the unit separator.
username
59-18
User name from one to seven characters with binary zero fill. If
t h e t fi e l d i s s e t t o o n e , t h i s p a r a m e t e r m u s t b e s p e c i fi e d . I f
t h e t fi e l d i s s e t t o z e r o , t h i s fi e l d i s i g n o r e d .
block
17-0
A p p l i c a t i o n b l o c k n u m b e r . I f t h e b fi e l d i s s e t t o o n e , TA F
returns the application block number in this field.
abtt
59-54
A p p l i c a t i o n b l o c k t y p e . T h i s p a r a m e t e r i s i g n o r e d b y TA F. I t i s
retained for compatibility with previous systems.
Description
1
Indicates that this is not the last data block of the message.
2
Indicates that this is the last or only data block of the message.
abn t
41-24
A p p l i c a t i o n b l o c k n u m b e r . I f t h e b fi e l d i s s e t t o o n e , TA F
a s s i g n s a n d s t o r e s a v a l u e i n t h e b l o c k fi e l d . I f t h e b fi e l d i s
set to zero, this value is stored in block.
actt
23-20
Application character type.
-
nfet
xptt
aimt
2
7-bit ASCII characters, seven and one-half per word.
3
7 - b i t A S C I I c h a r a c t e r s , r i g h t - j u s t i fi e d i n 1 2 - b i t b y t e s , fi v e p e r
word.
4
6-bit display code characters, 10 per word.
15
Format effectors.
0
Format effectors appear in the SEND message. Refer to the NAM/CCP
Host Application Programmers Reference Manual for information
concerning format effectors.
1
No format effectors appear in the SEND message.
14
Transparent bit.
0
Nontransparent data. IVT transforms are used.
1
If the act field is set to two or three, IVT transforms are inhib
i t e d . I f t h e a c t fi e l d i s s e t t o f o u r, t h i s b i t i s i g n o r e d .
12
Auto-input mode.
0
No auto-input mode.
I
Auto-input mode enabled.
tlct
11-0
Te x t l e n g t h i n u n i t s s p e c i fi e d b y t h e a c t fi e l d . I f a n o u t p u t
block contains multiple logical lines, all logical lines must
contain end-of-llne bytes, which must be included in the character
count.
status
59-0
S t a t u s o f t h e u s e r n a m e . T h i s fi e l d i s u s e d o n l y i f t h e r fi e l d
is set to one. The value of this field Is a supervisory message
returned by the network. (Refer to the NAM/CCP Host Application
Programmers Reference Manual for a description of the supervisory
messages.)
tThese parameters apply onl.y if the a field is set to one.
2-22
60459500 C
595857565554
47
41
29
23
20
17
15
13
11
messageaddress
numwords
block
abt
abn
act
Vs
tic
status
Figure 2-13. SEND Parameter Tablet
RELSCB Request
T h e R E L S C B r e q u e s t r e l e a s e s a l l o v e r fl o w
communication blocks tt to the system. After an
RELSCB request is processed, subsequent LOADCB
requests return a status word of zero.
The format is:
COBOL
the user does not meet the specified criterion. For
example, an application could use this to obtain a
list of the users that are allowed to use a particu
lar data base by selecting the data base field to be
searched for a certain name.
If the task data base is not the same as the one
being interrogated, then the list equals zero.
The format is:
ENTER RELSCB.
COBOL
There are no parameters.
ENTER TSIM USING code mask criterion rlength
list length.
FORTRAN
CALL RELSCB
There are no parameters.
COMPASS
RELSCB
There are no parameters.
code Computational-l item whose value
I n d i c a t e s w h i c h fi e l d i s t o b e
searched:
Va l u e
0 D a t a b a s e n a m e fi e l d .
1 U s e r a r g u m e n t fi e l d .
2
TSIM Request
r
The TSIM request provides limited interrogation of
the terminal status table. This table, in central
memory, is derived from the network file (refer to
section 9). The TSIM request can search four fields
in the table.
• Data base name field
• User argument field
• Communication line field
• User name field
The two-word TST entry of the users that meet a
d e fi n e d c r i t e r i o n ( c r i t e r i o n ) i s r e t u r n e d t o t h e
u s e r. T h e fi e l d s p e c i fi e d b y c o d e i s e x a m i n e d i n
each terminal table entry by taking the logical
product of the field and mask to isolate a portion
o f t h e fi e l d . T h e l o g i c a l d i f f e r e n c e o f t h i s
product and criterion value is then obtained. If
this result is zero, the terminal entry is placed in
list. No action occurs if it is not zero; that Is,
0^*-
Field
Communication
fi e l d .
line
3 U s e r n a m e fi e l d .
mask Parameter whose value is taken as a
binary mask. It is used in compil
ing the list of user names.
criterion Criterion value for the search.
rlength Computational-l item whose value TAF
sets to indicate the number of en
tries found.
l i s t I t e m i n w h i c h TA F l i s t s f o u n d e n
tries. If zero or absent, no list
is returned but rlength is given as
the number of found entries.
length Computational-l item whose value
indicates the number of words that
list can hold. If zero or absent,
no list is returned but rlength is
given as the number of found
entries. Only the lowest order 12
bits of this value are used.
tThe parameters are described in table 2-5.
ttDescribed under LOADCB Request.
60459500 C
2-23
co
u
•H
cu b.
•ses
O J>£ C « -H
c >.
43
CO 44 X co bl
o cu
*3 00
B
43
44 C —I
C/J W CU i-i
2-24
cu
u
o
43
U-l
U-l
O
C
( 0 4 ) U44 ( J 44
U
• H 4 3 CO
C
O u O
0)
•W
H co
cu ca
x ca
H to
H■
<
-
u.
x<
0)
ca
4-1 >,
<
U
3 43
>.
00
(-
••
43
cu
eo-a
CO it
« c
« -rt
V 6
E »-
U
>N
CU 43
44
cj -a
CO CU
•- c
CO -H
X B
U
bl
cu
44
,
•o
cu
w
■
ca
(h
CU cu
"8 5
C/l
4=
44
44 XI
bi
44 CU
C 44
O.
u -a
8 ^
3 43
3 4)
C
•Ch - We
E E
cu cu
C
O
O. a > 1
ENTER CEASE USING a.
Abnormal CEASE with
memory dump.t
-1 > a > -(217-1) Reserved for CDC.
Computational-l item whose value
indicates the type of CEASE selected:
A n y o t h e r v a l u e s p r o d u c e u n d e fi n e d
results and should not be used.
Type of CEASE
0
Normal CEASE.
1
Abnormal CEASE with
out memory dump.
ITL Request
-1
Normal CEASE and ter
minal remains locked.
217-1 > a > 1
Abnormal CEASE with
memory dump.t
-1 > a > -(217-1) Reserved for CDC.
A n y o t h e r v a l u e s p r o d u c e u n d e fi n e d
results and should not be used.
FORTRAN
The ITL request allows a task to set the time limit
for the task to a new value. The time limit is
expressed in exchange jump time units (that is, the
number of times a task executed its full time slice
without interruption). In addition, each call to
this function decreases the CPU priority of the task
b y 1 u n t i l t h e l o w e r l i m i t o f p r i o r i t y i s reached to
ensure good service to other tasks. The time limit
default value is a product of two installation
parameters. The released value is 1.12 CPU
seconds. If this is exceeded, the task aborts and
the message TIME LIMIT EXCEEDED is issued to the
terminal.
The format is:
CALL CEASE(a)
COBOL
a Integer whose value indicates the type
of CEASE selected:
a
Type
of
CEASE
0
Normal CEASE.
I
Abnormal CEASE with
out memory dump.
ENTER ITL USING ntm.
ntm
Computational-l item whose value
specifies the new time limit.
FORTRAN
-1
Normal CEASE and ter
minal remains locked.
217-i > a > 1
Abnormal CEASE with
memory dump.t
-1 > a > -(217-1) Reserved for CDC.
CALL ITL(nto)
ntm
COMPASS
ITL address
A n y o t h e r v a l u e s p r o d u c e u n d e fi n e d
results and should not be used.
/pi£v
Integer whose value specifies the
new time limit.
address Address of a parameter table in
the format shown in figure 2-17.
COMPASS
LOGT Request (COMPASS Only)
CEASE
Integer whose value indicates the type
of CEASE selected:
Type of CEASE
0
Normal CEASE.
1
Abnormal CEASE with
out memory dump.
-1
Normal CEASE and ter
minal remains locked.
The LOGT request logs out a terminal from TAF and
returns it to nontransaction mode. The terminal can
then access other interactive applications. A
system task is provided using this request. (Refer
to System Tasks in section 11.)
The format is:
COMPASS
LOGT
There are no parameters.
tDumps are identified by the transaction subsystem user name or by the appropriate DSDUMP parameter (refer to
section 6).
60459500 C
2-29
59
11
W^
ntm
WMMflftfo
ntm
New time limit.
Figure 2-17. ITL Parameter Table
KPOINT Request
The KPOINT request allows a task to initiate
execution of any K display command. Section 6
d e s c r i b e s t h r e e K d i s p l a y c o m m a n d s : K . D U M P,
K.DUMPLIM, and K.DSDUMP.
zeros after either a period or a
right parenthesis.
COMPASS
K display commands are normally issued from the
system console to communicate with and to request
specific actions of TAF. K display commands should
be Issued with care and then only when the results
of the command are well-defined.
When a task issues a K display command, the prefix
K. is omitted. For example, the entry from the con
sole is K.DUMP., but the same command Issued from a
task is DUMP.
All K display commands, except K.DUMP, require that
the calling task be on the system task library. Any
task can issue the K.DUMP command.
The format is:
COBOL
ENTER KPOINT USING address.
address 01-level name of the character
string (K display command). The
length of the character string
cannot exceed 80 characters. The
string must begin on a word
boundary and must be terminated by
a period or a right parenthesis;
the exception is the K.MESSAGE
command, which must be terminated
by 6 bits of zeros after either a
period or a right parenthesis.
FORTRAN
CALL KP0INT(address)
address Address of the character string (K
display command). The length of
the character string cannot exceed
80 characters. The string must
begin on a word boundary and must
be terminated by a period or a
right parenthesis; the exception
is the K.MESSAGE command, which
must be terminated by 6 bits of
2-30
KPOINT address
address Address of the character string (K
display command). The length of
the character string cannot exceed
80 characters. The string must be
gin on a word boundary and must be
terminated by a period or a right
parenthesis; the exception is the
K.MESSAGE command, which must be
terminated by 6 bits of zeros after
either a period or a right paren
thesis.
/^H§s.
WAIT Request
The WAIT request allows tasks to make TAF suspend
processing for a specified number of seconds (0 to
3600). The transaction must have no outstanding
data manager requests at the time a WAIT request is
issued.
The format is:
COBOL
ENTER WAIT USING time.
time A computational-2 data item indi
cating the number of seconds for
which processing is to be suspend
e d . I f u n s p e c i fi e d o r o u t o f
range, the task is aborted. Only
t h e I n t e g e r p o r t i o n i s s i g n i fi c a n t .
FORTRAN
CALL WAIT(time)
time A real number or variable indicat
ing the number of seconds for which
processing is to be suspended. If
u n s p e c i fi e d o r o u t o f r a n g e , t h e
task is aborted. Only the integer
p o r t i o n i s s i g n i fi c a n t .
60459500 C
/*«&.
C O M PA S S
WAIT
address
TA S K
The
UTILITY
following
REQUESTS
task
utility
requests
provide
capabili
ties for the FORTRAN and COBOL user, some of which
a d d r e s s T h e a d d r e s s o f a w o r d s p e c i f y i n g t h e a r e d i f fi c u l t t o d o b e c a u s e t h e y a r e a t t h e b i t
number of seconds (N) for which level,
processing is to be suspended. The
word has the form 48/0,12/N. If • LOGIN
u n s p e c i fi e d o r o u t o f r a n g e , t h e
task
is
aborted.
Determine
if
a
s p e c i fi e d
user
is
logged
in.
• EXTRACT
Extract a bit string from a word.
• INSERT
Insert a bit string into a word.
j0^\
60459500
C
2-30.1/2-30.2
|
/P9**-
LOGiN Request
EXTRACT Request
The LOGIN request allows a task to determine if a
specified user is logged in before it issues a SEND
request to that user. TAF aborts a task that issues
a SEND request without recall to a user who is not
logged in.
The EXTRACT request allows a task to extract a bit
string from a word and move it to another word,
r i g h t - j u s t i fi e d . F o r i n s t a n c e , t h e E X T R A C T r e q u e s t
ca n b e u se d to ch e ck fie l d s i n th e te r m i nal status
table or the communication block.
| NOTJ"|
In the following request formats, if n is not within
the specified range, if bbp plus 1 minus n is less
than 0, or if there are any other errors in the
p a r a m e t e r s , TA F a b o r t s t h e t a s k a n d i s s u e s t h e
following message.
It is possible for the receiving user
to log out after the task issues a
LOGIN request and before the task
issues a SEND request. Therefore, it
is recommended that the task issue
the SEND request soon after issuing
the LOGIN request.
TASK REQUEST ARGUMENT ERROR.
The format is:
COBOL
ENTER EXTRACT USING loci loc2 bbp n.
The format is:
loci
D a t a n a m e o f t h e s o u r c e fi e l d .
Any data type is allowed, loci
must begin on a word boundary.
loc2
Data name of the computational-l
d e s t i n a t i o n fi e l d . T h e b i t
s t r i n g i s r i g h t - j u s t i fi e d i n
t h i s fi e l d .
bbp
B e g i n n i n g b i t p o s i t i o n o f fi e l d
loci; this is the leftmost bit
o f t h e fi e l d . B i t s a r e n u m b e r e d
59 through 0.
COBOL
0$^
ENTER LOGIN USING username status.
username A one- to seven-character alpha
numeric user name, left-justi
fi e d . A b i n a r y z e r o s p e c i fi e s
the user associated with the
transaction that is running.
status
Address of the location to
contain the returned status.
The format of the returned
status is computational-l.
Values for status are:
Number of bits to extract; the
range of values for n is 1 to
59, inclusive. The format of n
must be computational-l.
0 User not logged in.
FORTRAN
1 User logged in.
CALL EXTRACT(locl,loc2,bbp,n)
FORTRAN
l o c i N a m e o f t h e i n t e g e r s o u r c e fi e l d .
CALL LOGTN(username,status)
loc2 Name of the integer destination
fi e l d . T h e b i t s t r i n g i s r i g h t j u s t i fi e d i n t h i s fi e l d .
username A one- to seven-character alpha
numeric user name, left-justi
fi e d . P o s s i b l e f o r m s a r e n H f
and nLf (refer to the FORTRAN
Extended 4 Reference Manual). A
b i n a r y z e r o s p e c i fi e s t h e u s e r
associated with the transaction
that is running.
status
Address of the location to
contain the returned status.
The format of the returned
s t a t u s i s i n t e g e r. Va l u e s f o r
status are:
0 User not logged in.
1 User logged in.
bbp
n
B e g i n n i n g b i t p o s i t i o n o f fi e l d
loci; this is the leftmost bit
o f t h e fi e l d . B i t s a r e n u m b e r e d
59 through 0.
Number of bits to extract; the
range of values for n is 1 to
59, inclusive. n must be
integer type.
The COBOL STRING and UNSTRING statements also
provide capabilities for manipulating characteraligned data. The EXTRACT request should be used
only when the use of these COBOL statements is
impossible or inconvenient.
j ^ y
60459500 A
2-31
INSERT Request
APPLICATION RECOVERY REQUESTS
T h e I N S E RT r e q u e s t a l l o w s a t a s k t o i n s e r t a b i t
string into a word. For instance, the INSERT
r e q u e s t c a n b e u s e d t o s e t fi e l d s i n t h e t e r m i n a l
status table.
The following task requests are for use in
recoverable transactions. All are for use by
applications tasks although some are also used by
system tasks.
RERUN
In the following formats, if n is not within
specified range, if bbp plus 1 minus n is less
0, or if there are any other errors in
p a r a m e t e r s , TA F a b o r t s t h e t a s k a n d i s s u e s
following message.
the
than
the
the
TASK REQUEST ARGUMENT ERROR.
Restarts a run
terminal input.
unit using the initial
RGET
Retrieves data from
recovery file (CRF).
the communication
RPUT
The format is:
COBOL
Places data on the communication recovery
fi l e .
ENTER INSERT USING loci loc2 bbp n.
RSECURE
loci Data name of the computational-l
s o u r c e fi e l d . T h e b i t s t r i n g m u s t
b e r i g h t - j u s t i fi e d i n t h i s fi e l d .
Retrieves a message previously saved on the
c o m m u n i c a t i o n r e c o v e r y fi l e b y a S E C U R E
request.
l o c 2 D a t a n a m e o f t h e d e s t i n a t i o n fi e l d .
Any data type is allowed. loc2 must
begin on a word boundary.
SECURE
b b p B e g i n n i n g b i t p o s i t i o n o f fi e l d
loc2; this is the leftmost bit of
t h e fi e l d . B i t s a r e n u m b e r e d 5 9
through 0.
n Number of bits to insert; the range
of values for n is 1 to 59,
inclusive. The format of n must be
computational-l.
FORTRAN
CALL INSERT(locl,loc2,bbp,n)
l o c i N a m e o f t h e i n t e g e r s o u r c e fi e l d .
The
bit
string
must
be
r i g h t - j u s t i fi e d i n t h i s fi e l d .
loc2
bbp
Name of
fi e l d .
the integer destination
B e g i n n i n g b i t p o s i t i o n o f fi e l d
loc2; this is the leftmost bit of
t h e fi e l d . B i t s a r e n u m b e r e d 5 9
through 0.
Number of bits to insert; the range
of values for n is 1 to 59,
inclusive, n must be integer type.
The COBOL STRING and UNSTRING statements also
provide capabilities for manipulating characteraligned data. The INSERT request should be used
only when the use of these COBOL statements is
impossible or inconvenient.
2-32
Signals the completion of a transaction's
work and saves a message on the recovery
file to be sent to the terminal when the run
unit ceases.
TSTAT
Returns the status of one or more specified
objects.
Refer to section 7 for an overview of the recovery
process from the applications programmer's
perspective. Refer to the applicable data manager
r e f e r e n c e m a n u a l ( C D C S , TA F / C R M , o r TO TA L ) f o r
requests associated with data base recovery.
RERUN Request
The RERUN request causes the initial terminal input
for a rerunnable run unit to be resubmitted to the
transaction system. The input comes from the
communication recovery file. The actions that occur
as a result of RERUN are:
1. The recovery status is set to zero so that
the recovery task will not be scheduled.
2 . T h e r e s t a r t s t a t u s ( T S TAT w i t h k e y w o r d
RESTART) is set to one.
3. A termination is processed for the run unit
and ITASK is called to rerun the run unit.
Tr a n s a c t i o n s u s i n g t h i s r e q u e s t m u s t t a k e c a r e t o
avoid entering an infinite loop if the RERUN results
from an error condition.
60459500 A
/<^s
area of the communication
r e c o v e r y fi l e , a n d s o o n . T h i s
parameter is input for both
RPUT and RGET. The maximum
value of index is the value of
the number parameter in the
RECOVER statement in the TCF.
The format is:
COBOL
ENTER RERUN USING status,
status
A computational-l data item
w h o s e v a l u e i s s e t b y TA F t o
indicate the status of the
request. The values are:
status
0 No errors.
29 Recovery is not in
stalled.
0 No errors.
19 The index is outside of
t h e u s e r r e c o v e r y fi l e
message area (RPUT
only).
33 Run unit is not rerunnable.
FORTRAN
20 No message (RGET only).
CALL RERUN (status)
status
21 The message does not
fi t i n t h e r e c o v e r y
file message area (RPUT
only).
An integer variable in which
TA F w i l l r e t u r n a s t a t u s . T h e
values are:
0 No errors.
22 The message does not
fit in the user message
area (RGET only).
29 Recovery is not in
stalled.
23 Incorrect application
character type (act).
33 Run unit is not rerunnable.
28 The RGET act is not
equal to the RPUT act.
2 9 TA F a u t o m a t i c r e c o v e r y
is not installed.
RPUT and RGET Requests
The RPUT request allows a task to put applicationdependent data on the communication recovery file.
The RGET request allows the task to retrieve the
data placed on the recovery file by an RPUT. The
length of the data in each request and the number of
s l o t s f o r d a t a o n t h e r e c o v e r y fi l e i s s p e c i fi e d a t
TAF initialization on the RECOVER statement in the
TCF (refer to section 4). TAF maintains the data on
a user name basis. TAF does not modify the user
d a t a u n l e s s t h e c o m m u n i c a t i o n r e c o v e r y fi l e i s
initialized. These requests may be used by any task
when TAF automatic recovery is installed.
messagelength
A computational-l data item
indicating the length of the
message in the message units
specified by the act parameter.
This parameter is required when
using message units other than
6-bit display code. This is an
i n p u t p a r a m e t e r f o r R P U T. F o r
RGET, the user sets the messagelength of the area to receive
the message. Upon completion
of RGET, TAF places the length
of the message in messagelength.
act
A computational-l data item
indicating the application
character type. The type is
t h e s a m e a s f o r N A M. This is
an input parameter. The values
are:
The format is:
COBOL
ENTER "RPUT" USING message,index[.status .messagelength, act].
ENTER "RGET" USING message,index,status .messagelength(,act].
message An 01-level data item that
contains the message. This is
an input parameter for RPUT and
an output parameter for RGET.
index A computational-l data item
indicating the index for the
recovery record. Index 1
p o i n t s t o t h e fi r s t r e c o r d i n
user area of the communication
r e c o v e r y fi l e ; i n d e x 2 p o i n t s
to the second record in user
60459500 B
A computational-l data item
w h o s e v a l u e i s s e t b y TA F t o
indicate the status of the
request. The values are:
2 7-bit ASCII characters,
seven and one-half per
word.
3 7-bit ASCII characters,
r i g h t - j u s t i fi e d i n 1 2 b i t b y t e s , fi v e p e r
word.
4 6-bit display code char
acters, 10 per word.
This is the default
value.
2-33
act
FORTRAN
An
CALL RPUT(message,index,status.message-length
t.act])
CALL RGET(message,index,status ,message-length
[,act])
message
index
status
An integer variable whose value
i s s e t b y TA F t o i n d i c a t e t h e
status of the request. The
values are:
0 No errors.
19 The index is outside of
the user recovery area.
20 No message (RGET only).
21 The message does not
fi t i n t h e r e c o v e r y
file message area (RPUT
only).
22 The message does not
fit in the user message
area (RGET only).
3 7-bit ASCII characters,
r i g h t - j u s t i fi e d i n 1 2 b i t b y t e s , fi v e p e r
word.
4
6-bit display code
characters, 10 per
word. This is the
default value.
RSECURE Request
The RSECURE request allows a recovery task to obtain
a m e s s a g e p r e v i o u s l y s a v e d o n t h e c o m m u nication
recovery file by a SECURE request. After obtaining
the message, the task would normally send the
message to the appropriate terminal. Any task may
use this request if automatic recovery has been
installed with TAF.
The format is:
COBOL
ENTER "RSECURE" USING message,status ,
message-length ,ac t,format-effec tor,
transparent-mode.
message
An 01-level data item that
contains the message. This is
an output parameter.
status
A computational-l data item
w h o s e v a l u e i s s e t b y TA F t o
indicate the status of the
request. The values are:
0 No errors.
23 Incorrect application
character type (act).
20 No message.
28 The RGET act is not
equal to the RPUT act.
22 The message does not
fit in the user message
area.
2 9 TA F a u t o m a t i c r e c o v e r y
is not installed.
29
message- An integer variable indicating
length the length of message in the
message units specified by the
act parameter. This is an
input parameter for RPUT. For
RGET, the user sets the messagelength of the area to receive
the message. Upon completion
of the request, TAF returns the
message-length as recorded on
the communication recovery file.
2-34
2 7-bit ASCII characters,
seven and one-half per
word.
The name of an array that
contains the message. This is
an input parameter for RPUT and
output parameter for RGET.
An integer variable indicating
the index for recovery record.
I n d e x 1 p o i n t s t o t h e fi r s t
record in user area of the
c o m m u n i c a t i o n r e c o v e r y fi l e ;
index 2 points to the second
record in user area of the
c o m m u n i c a t i o n r e c o v e r y fi l e ,
and so on. This parameter is
input for both RPUT and RGET.
The maximum value of index is
the value of the number
parameter in the RECOVER
statement in the TCF.
integer variable indicating
the application character
type. The type is the same as
for NAM. This is an input
parameter. The values are:
Recovery
stalled.
is
not
in-
message- A computational-l data Item
length
indicating
the
length
of
message in the message units
s p e c i fi e d
by
the
act
p a r a m e t e r. B e f o r e i s s u i n g t h e
request, the user sets the
message-length area in the
task. Upon completion of the
r e q u e s t , TA F r e t u r n s t h e
message-length as recorded on
the communication recovery file.
60459500 B
A computational-l data item
indicating the application
character type. The type is
the same as for NAM. Before
issuing the request, the user
sets the act. Upon completion
of the request, TAF returns the
act as recorded on the recovery
fi l e . T h e v a l u e s a r e :
2 7-bit ASCII characters,
seven and one-half per
word.
messagelength
An integer variable indicating
the length of the message in
m e s s a g e u n i t s s p e c i fied by the
a c t p a r a m e t e r. B e f o r e i s s u i n g
the request, the user sets the
message-length area in the
task. Upon completion of the
r e q u e s t , TA F r e t u r n s t h e
message length as recorded on
the communication recovery file.
act
An integer variable indicating
the application character
type. The type is the same as
NAM. Before issuing the
request, the user sets the
act. Upon completion of the
request, TAF returns the act as
r e c o r d e d o n t h e r e c o v e r y fi l e .
The values are:
3 7-bit ASCII characters,
r i g h t - j u s t i fi e d i n 1 2 b i t b y t e s , fi v e p e r
word.
4
formateffector
6-bit display code
characters, 10 per
word. This is the
default value.
2 7-bit ASCII characters,
seven and one-half per
word.
A computational-l data item
indicating format effector
usage. The values are:
3 7-bit ASCII characters,
r i g h t - j u s t i fi e d i n 1 2 b i t b y t e s , fi v e p e r
word.
0 Format effectors appear
in the message.
4
1 No format effectors
appear in the message.
transpar
ent-mode
A computational-l data item
indicating transparent mode
usage. Default is nontranspar
ent mode. The values are:
formateffec tor
An integer variable indicating
format effector usage. The
values are:
0 Format effectors appear
in the message.
0 Nontransparent data.
Interactive virtual
terminal transforms are
used.
1 Transparent data. IVT
transforms are inhib
ited.
6-bit display code
characters, 10 per
word. This is the
default value.
1 No format effectors
appear in the message.
transpar
ent-mode
An integer variable indicating
transparent mode usage. The
values are:
FORTRAN
0 Nontransparent data.
Interactive virtual
terminal transforms are
used.
CALL RSECURE(message,status,message-length, act,
format-effector,transparent-mode)
message
The name of an array that
contains the message. This is
an output parameter.
status
An integer variable whose value
I s s e t b y TA F t o i n d i c a t e t h e
status of the request. The
values are:
1 Transparent data. IVT
transforms are inhib
ited.
SECURE Request
0 No errors.
20 No message.
22 The message does not
fit in the user message
area.
29 Recovery is not in
stalled.
60459500 A
The SECURE request tells the transaction executive
th a t th e w o r k o f th e r u n u n i t i s c o m p l e te. All that
remains is to commit the data base and end the run
unit. The SECURE request includes a terminal
confirmation message. This message will be sent at
the run unit end time (normal CEASE). If the commit
request fails, the task may RERUN the run unit or
issue a CEASE request with abnormal termination. In
either case, the SECURE message will not be sent.
2-35
TAF records the message associated with SECURE on
permanent storage so that the message can be
delivered in spite of system or terminal failures.
If no failures occur, the message will be sent from
the task's SECURE message area. This means that the
SECURE, data base commit, and CEASE must occur in
the same task. TAF assumes that the message has
been acknowledged by the terminal operator when the
operator enters the next transaction input. The
SECURE message may appear twice if recovery is done
after a failure, but it is guaranteed to appear at
l e a s t o n c e . TA F a l s o s a v e s t h e N A M a p p l i c a t i o n
block header with the message so that it will be
sent with the correct character type and mode. Only
the last SECURE message is saved per run unit. Any
task may use this request if recovery has been
installed with TAF; however, if the run unit is not
recoverable, the SECURE message will not be issued
to the terminal upon recovery (only at initial CEASE
time).
messagelength
A computational-l data item
indicating the length of the
message in the message units
s p e c i fi e d
by
the
act
p a r a m e t e r. T h i s i s a n i n p u t
p a r a m e t e r. I t i s r e q u i r e d w h e n
the act parameter does not
s p e c i f y d i s p l a y.
act
A computational-1 data item
indicating the application
character type. The type is
the same as for NAM. This is
an input parameter. The values
are:
2 7-bit ASCII characters,
seven and one-half per
word.
7-bit ASCII characters,
r i g h t - j u s t i fi e d i n 1 2 b i t b y t e s , fi v e p e r
word.
For a BTRAN run unit the message is recorded on the
communication recovery file but no message is sent
to the terminal/username. The RECOVER statement
maximumsize parameter specifies the message size
that can be recorded on the communication recovery
fi l e .
6-bit display code
characters, 10 per
word. This is the
default value.
The format of the message on the terminal depends on
t h e t e r m i n a l c l a s s a n d t h e f o r m a t e ff e c t o r s i n t h e
message. Refer to the SEND request description
earlier in this section for more information.
formateffec tor
The format is:
COBOL
ENTER "SECURE" USING message,statusf,messagelength,act ,format-effector .transparent-mode] .
0 Format effectors appear
in the message.
message A 01-level data item that
contains the message. This is
an input parameter.
status A computational-l data item
w h o s e v a l u e i s s e t b y TA F t o
indicate the status of the
request. The values are:
0 No errors.
21 The message is too
l a r g e t o fi t i n T A F ' s
communication recovery
fi l e . R e f e r t o t h e
RECOVER statement maxi
mumsize parameter.
1 No format effectors
appear in the message.
transpar- A computational-l data item
ent-mode indicating transparent mode
usage. This is an optional
parameter. It is necessary
only if transparent mode is
used.
The
default
is
nontransparent mode. The
values are:
0 Nontransparent data.
Interactive virtual
terminal transforms are
used.
23 Incorrect application
character type.
24
A computational-l data item
indicating format effector
usage* This is an optional
parameter. It is necessary
only if format effectors are
used. The default is no format
e ff e c t o r s . T h e v a l u e s a r e :
Incorrect formateffector value.
1 Transparent data. IVT
transforms are inhib
ited.
25 Incorrect transparentmode value.
26 The message exceeds the
maximum length for SEND.
27 The message exceeds the
maximum length for a
run unit.
2 9 TA F a u t o m a t i c r e c o v e r y
is not installed.
2-36
FORTRAN
CALL SECURE (message,status,message-length
[ ,act,format-effector.transparent-mode])
message The name of an array that
contains the message. This is
an input parameter.
60459500 A
status An integer variable whose value
i s s e t b y TA F t o i n d i c a t e t h e
status of the request. The
values are:
0 No errors.
transpar- An integer variable indicating
ent-mode transparent mode usage. This
i s a n o p t i o n a l p a r a m e t e r. I t
is
necessary
only
if
transparent mode is used. The
default is nontransparent
mode. The values are:
21 The message is too large
to fit in the communica
t i o n r e c o v e r y fi l e .
Refer to the RECOVER
statement maximumsize
parameter.
0 Nontransparent data.
Interactive virtual
terminal transforms are
used.
1 Transparent data. IVT
transforms are inhib
ited.
23 Incorrect application
character type.
2 4 I n c o r r e c t f o r m a t e ff e c t
or value.
TSTAT Request
25 Incorrect transparentmode value.
26 The message exceeds the
maximum length for SEND.
27 The message exceeds the
maximum length for a
run unit.
2 9 TA F a u t o m a t i c r e c o v e r y
is not installed.
J8*V
messagelength
An integer variable indicating
the length of the message in
the message units specified by
t h e a c t p a r a m e t e r. T h i s i s a n
input parameter.
act
An integer variable indicating
the application character
type. The type is the same as
for NAM. This is an input
parameter. The values are:
2 7-bit ASCII characters,
seven and one-half per
word.
3 7-bit ASCII characters,
r i g h t - j u s t i fi e d 1 2 - b i t
bytes, five per word.
6-bit display
characters, 10
word. This is
default value.
code
per
the
format- An integer variable indicating
effector format effector usage. This is
a n o p t i o n a l p a r a m e t e r. I t i s
necessary only if format effec
tors are used. The default is
no format effectors. The
values are:
0 Format effectors appear
in the message.
1 No format effectors
appear in the message.
60459500 A
T h e T S TAT r e q u e s t r e t u r n s i n f o r m a t i o n a b o u t t h e
current user or run unit. It is used by both system
tasks and applications (user) tasks.
The format is:
COBOL
ENTER "TSTAT** USING status .keyword j, value j,...,
keywordn,valuen.
status A computational-l data item
w h o s e v a l u e i s s e t b y TA F t o
indicate the status of the
request. The values are:
0
No
errors.
12 The keyword speci
fi e d r e q u i r e s T A F
automatic recov
e r y. TA F a u t o m a t i c
recovery is not
installed.
13 End of NEXT proc
essing.
1 4 U S E R i s n o t d e fi n e d
i n t h e n e t w o r k fi l e .
400+i keyword^ is invalid.
keyword ^ An 01-level item that contains
a one- to seven-character
keyword for which a value is
desired. The keyword must be
l e f t - j u s t i fi e d a n d b l a n k fi l l e d . R e f e r t o t a b l e 2 - 7 f o r
k e y w o r d d e fi n i t i o n s .
v a l u e ^ A d a t a i t e m t o w h i c h TA F r e t u r n s
the value for the corresponding
keyword. The keyword^ and
v a l u e ^ fi e l d s m u s t a p p e a r i n
pairs. For USER, NEXT, OLDID,
and NEWID usage is display. For
all other TSTAT keywords, usage
is computational-l.
2-37
TSTAT System Task Keywords
FORTRAN
C A L L T S TAT ( s t a t u s . k e y w o r d j , v a l u e j k e y w o r d a ,
valuen)
status An integer variable whose value
i s s e t b y TA F t o i n d i c a t e t h e
status of the request. The
values are:
0
No
errors.
12 The keyword speci
fi e d r e q u i r e s T A F
automatic recov
e r y. TA F a u t o m a t i c
recovery is not
Installed.
13 End of NEXT proc
essing .
1 4 U S E R i s n o t d e fi n e d
in the network file.
400+i keywordi is invalid.
keyword.£ A variable that contains a oneto seven-character left-just i fi e d k e y w o r d f o r w h i c h a
value is desired. The keyword
m u s t b e b l a n k - fi l l e d . R e f e r t o
table
2-7
for
keyword
d e fi n i t i o n s .
v a l u e ^ A v a r i a b l e fi e l d t o w h i c h T A F
returns the value of the de
sired keyword. The keyword^
and valuer must appear in
pairs. For USER, NEXT, OLDID,
and NEWID valuer is character
d a t a . F o r a l l o t h e r T S TAT
keywords, valuer is an
i n t e g e r.
Some TSTAT keywords (both as COBOL and FORTRAN
parameters) are meant for user tasks and others are
meant for system tasks, such as BTASK, CTASK, and
RTASK.
TSTAT User Task Keywords
• Keywords RESTART, OLDID, and NEWID are meant
for use by application tasks that use
multiple data manager begin-commit sequences
to determine If the run unit is in a
restarted state and, if so, where to begin
processing*
• Keywords STEP, TRAN, OLDIN, NEWID, CRM, and
C D C S a r e u s e d b y RTA S K d u r i n g t e r m i n a l
login/relogin to determine if a run unit
requires rerun. The SEQ (sequence number)
returned is the transaction sequence number
t h a t w a s fi r s t a s s i g n e d t o t h e r u n u n i t .
RTASK can be either a system task or a user
task.
2-38
Keywords NEXT, STEP, TRAN, OLDID, NEWID are
u s e d b y B TA S K t o r e a d s e q u e n t i a l l y t h e
c o m m u n i c a t i o n r e c o v e r y fi l e t o fi n d b a t c h
(BTRAN) run units that require rerunning.
BTASK uses the SRERUN request with username
to rerun BTRAN run units.
SYSTEM TASK RECOVERY REQUESTS
Applications programmers can skip this subsection
since all the requests documented here are available
only to system tasks (that is, tasks residing on the
system task library). Recovery requests that are for
use by both system tasks and application tasks are
documented under Application Recovery Requests ear
lier in this section. Refer to section 8 for an
overview of the recovery process from the data admin
istrator's perspective. Refer to the applicable data
manager reference manual (CDCS, TAF/CRM, or TOTAL)
for requests associated with data base recovery. The
following task requests are used by system tasks for
transaction recovery.
■ CALLTRN
Initiates a run unit*
• SRERUN
Resubmits initial terminal input for a rerunnable run unit.
• TINVOKE
R e t u r n s o r s p e c i fi e s a s y s t e m i d e n t i fi e r f o r
begin-commit sequences in this job.
• W S TAT
Records information needed for recovery
processing.
CALLTRN Request
The CALLTRN request causes the initiation of a run
unit. It is available only to the system task ITASK.
The actions that occur as a result of CALLTRN are:
1 . I TA S K c e a s e s . I f a n e r r o r c o n d i t i o n i s d e
tected, an error message is issued to the
terminal via MSABT.
2. The initial terminal input is logged on the
CRF if the transaction is recoverable. The
transaction will not be scheduled for execu
tion until this circular input-output (CIO)
operation is complete.
3. If the transaction initiated is recoverable,
the commitment history of the previous recov
erable run unit for this user is released.
60459500 B
Table 2-7. TSTAT Keyword Descriptions
Keyword
Value
Description
USER
Return status for the user/terminal specified in value. If USER or NEXT
i s n o t s p e c i fi e d , t h e n t h e r e q u e s t r e f e r s t o t h e o r i g i n a t i n g t e r m i n a l /
user. Only one of USER/NEXT can be specified in a single TSTAT request.
Reserved for tasks on system task library.
NEXT
Return the next user from the communication recovery file(s). NEXT is
available only to system tasks. When NEXT is specified, all other key
words will refer to the next user. Only one of USER/NEXT can be specified
in a single TSTAT request.
SEQ
Return the transaction sequence number for specified user.
STEP
Run unit or job step.
Nonrecoverable run unit or job input.
CDCS down. This applies only to a recoverable run unit.
Normal transaction CEASE or job end. Present only for BTRAN or TAF/CRM
batch concurrency jobs.
jgPN
Task or job abort.
Run unit is no longer rerunnable. This occurs when an I/O error is
detected and the data cannot be recovered for the user.
Recoverable run unit or job input.
CRM begin-commit ids are logged.
NAM down. This applies only to a recoverable run unit.
TRAN
Run unit type.
Terminal user.
BTRAN user jobs.
TAF/CRM user job.
CRM
CRM usage.
CRM may not be used by the transaction.
CRM may be used by the transaction.
CDCS
CDCS usage.
CDCS may not be used by the transaction.
CDCS may be used by the transaction.
RESTART
Run unit is not in restarted state.
Run unit is in restarted state. This state occurs when a RERUN request
was issued.
OLDID
Return the old (previous) CRM begin-commit id from the communication
r e c o v e r y fi l e .
NEWID
Return the new (current) CRM begin-commit id from the communication
r e c o v e r y fi l e .
0^*.
60459500 B
2-39
The format is:
31 username is not in the
n e t w o r k fi l e .
COBOL
33 Run unit
rerunnable.
ENTER CALLTRN USING tname.
tname
01-level data item containing a
one- to seven-character trans
action name.
FORTRAN
is
not
username A variable containing a one- to
seven-character user name, leftj u s t i fi e d a n d b l a n k - fi l l e d . I f
this parameter is omitted, the
rerun applies to the originating
u s e r.
CALL CALLTRN(tname)
tname An integer containing a one- to
seven-character transaction
n a m e , l e f t - j u s t i fi e d w i t h b l a n k
fi l l .
SRERUN Request
The SRERUN request causes the initial terminal input
for a rerunnable run unit to be resubmitted to the
tr a n s a c ti o n s u b s y s t e m . T h e i n p u t i s r e t r i e v e d f r o m
t h e c o m m u n i c a t i o n r e c o v e r y fi l e . T h e a c t i o n s t h a t
occur as result of SRERUN are:
TINVOKE Request
The TINVOKE request returns a system identifier to
be used for all begin-commit sequences in the job or
t a s k . F o r TA F, t h i s s y s t e m i d e n t i fi e r i s t h e t r a n s
action sequence number. Optionally, for the recovery
case, the job or task may supply an old system iden
t i fi e r . T h i s e s t a b l i s h e s t h e t a s k o r j o b a s a
continuation of a previous task or job.
The format is:
COBOL
• The recovery status is set to zero so that
the recovery task will not be scheduled.
• T h e r e s t a r t s t a t u s ( T S TAT w i t h k e y w o r d
RESTART) is set to one.
• The SRERUN is done without requesting run
unit termination.
ENTER TINVOKE USING status,new-system-id,
old-system-id.
status A computational-l item in which
TA F w i l l r e t u r n a s t a t u s * T h e
values are:
0 Request successful.
The format is:
32 old-system-id unknown.
COBOL
ENTER SRERUN USING status[.username].
status A computational-l data item in
w h i c h TA F w i l l r e t u r n a
status. The values are:
0 No errors.
29 Recovery not installed.
new-system-id A computational-l item in which
TAF will return a system identi
fi e r t o b e u s e d f o r a l l b e g i n commit sequences in the job or
task.
old-system-id A computational-l item in which
the task or job supplies the
o l d s y s t e m i d e n t i fi e r t h a t
establishes the task or job as
a continuation of the old one.
31 username not in network
fi l e .
FORTRAN
33 Run unit not rerunnable.
CAIi TINVOKE(status.new-system-id,old-system-id)
username 01-level data item containing a
one- to seven-character user
name. If this parameter Is
omitted, the rerun applies to
the user name under which the
current task is running.
FORTRAN
status An integer variable in which
TA F w i l l r e t u r n a s t a t u s . T h e
values are:
0 Request successful.
32 old-system-id unknown.
CALL SRERUN(status[,username])
s t a t u s A n i n t e g e r i n w h i c h TA F w i l l
return a status. The values
are:
0 No errors.
29 Recovery is not in
stalled.
2-40
/tf^&sjV
n e w - s y s t e m - i d A n i n t e g e r i n w h i c h TA F w i l l
r e t u r n a s y s t e m i d e n t i fi e r t o
be used for all begin-commit
sequences in the task or job.
old-system-id An integer in which the task or
job supplies the old system
i d e n t i fi e r t h a t e s t a b l i s h e s t h e
program as a continuation of a
previous one.
60459500 A
/_C^v
FORTRAN
WSTAT Request
The WSTAT request records information needed for
recovery processing on the communication recovery
file or TAF system tables. WSTAT is used by system
task CTASK.
CALL WSTAT(status.keywordi,valuei,.
valuen)
status
The format is:
COBOL
29
status A computational-l item whose
value is set by TAF to indicate
the status of the request. The
values are:
0
29
No
K e y w o r d s p e c i fi e d
r e q u i r e s TA F a u t o
matic recovery. TAF
automatic recovery
is not installed.
3 1 U S E R i s n o t d e fi n e d
in the network file.
400+i keyword^ is invalid.
keyword^ An 01-level item containing a
one- to seven-character keyword
for which a value is speci
fied. The keyword must be leftj u s t i fi e d a n d b l a n k - fi l l e d . R e
fer to table 2-8 for keyword
d e fi n i t i o n s .
value^ A computational-l item that con
tains the value for the desired
keyword. The keyword^ and
v a l u e j fi e l d s m u s t a p p e a r i n
pairs.
No
errors.
K e y w o r d s p e c i fi e d
r e q u i r e s TA F a u t o
matic recovery. TAF
automatic recovery
is not installed.
30 End of NEXT process
ing.
errors.
30 End of NEXT process
ing.
60459500 B
An integer whose value is set
b y TA F t o g i v e t h e s t a t u s o f
the request. The values are:
0
ENTER "WSTAT" USING status .keyword!.valuet,...,
keywordn,valuen.
,keywordn,
3 1 U S E R i s n o t d e fi n e d
i n t h e n e t w o r k fi l e .
400+i keyword^ is invalid.
keyword^
A variable containing a one- to
seven-character keyword for
w h i c h a v a l u e i s s p e c i fi e d .
The keyword must be leftj u s t i fi e d a n d b l a n k - fi l l e d .
Refer to table 2-8 for keyword
d e fi n i t i o n s .
value£ Integer that contains the value
of the preceding keyword. The
keyword j and value j_ must
appear in pairs.
The WSTAT keywords (both for COBOL and FORTRAN param
eters) are given in table 2-8. All keywords neces
sary for recovery processing for a user name must be
specified in the WSTAT request. For instance, CTASK
makes a TSTAT request specifying NEXT, SEQ, STEP,
TRAN, CRM, and CDCS followed by a WSTAT with SEQ,
TRAN, CRM, CDCS, OLDID, NEWID, USER, and STEP. Any
k e y w o r d n o t s p e c i fi e d r e t a i n s t h e v a l u e a s s o c i a t e d
with it on the previous WSTAT request.
2-41
Ta b l e 2 - 8 . W S TAT K e y w o r d D e s c r i p t i o n s
Keyword
Description
Va l u e
USER
Set status for user name specified in value. If USER is not specified,
then the request refers to the originating user name.
SEQ
The transaction sequence number specified in value is written for a given
user name.
STEP
Transaction or job step.
0
Nonrecoverable run unit or job input.
1
CDCS down. Applies only to recoverable run units.
2
Normal transaction cease or job end. Present only for BTRAN or TAF/CRM
batch concurrency.
3
Task or job abort.
4
Run unit no longer rerunnable. This occurs when an I/O error is detected
and the data cannot be recovered for the user.
5
Recoverable run unit or job input.
6
CRM begin-commit ids are logged.
7
NAM down. Applies only to a recoverable run unit.
8
Allow terminal or job input to TAF.
9
Terminate TAF because of a recovery error.
Transaction type.
TRAN
1
Terminal user.
2
BTRAN user job.
3
TAF/CRM user job.
CRM usage.
CRM
0
CRM may not be used by transaction.
1
CRM may be used by transaction.
CDCS usage.
CDCS
2-42
y^$w$?V
0
CDCS may not be used by transaction.
1
CDCS may be used by transaction.
OLDID
Set old (previous) CRM begin-commit id on the communcation recovery file.
NEWID
Set new (current) CRM begin-commit id on the communication recovery file.
60459500 B
J^v
ACCESS AND USE OF CDCS BY TASKS
The CYBER Database Control System can be used alone
or with one other data manager (CRM or TOTAL) in the
same transaction. If a task is to use CDCS, the
CDCS reference manuals listed in the preface should
be consulted for information on how to set up the
data base (schema, subschema, master directory, and
files). This data base is associated with CDCS and
t h e fi l e s w i l l b e a t t h e c o n t r o l p o i n t o f C D C S
during execution. Tasks can use the CDCS verbs for
data base access provided that they are compiled
with the appropriate subschema relating them to a
CDCS data base.
In the following, xx represents the two-character
d a t a b a s e i d e n t i fi e r.
A TAF application (known by the xx identifier in the
TCF) is linked to a CDCS data base by means of the
subschemas used in the tasks associated with the
a p p l i c a t i o n ( t h e s e a r e t h e t a s k s o n x x TA S K L ) . A l l
tasks in a transaction must use the same subschema
or a fatal task error (detected by CDCS) will occur.
Refer to sections 7 and 8 for information regarding
recoverable transactions and CDCS/transaction aborts.
T h e f o l l o w i n g TA F fi l e s a r e a s s o c i a t e d w i t h a n
application using CDCS:
TCF
xxJ
xxTASKL
xxJORl
XXJ0R2
xxJ0R3
Required.
Required unless all tasks are on
system task library.
Optional.
A transaction will be considered to be connected to
CDCS if it has successfully issued a request to CDCS
a n d th e te r m i n a t e r e q u e s t t o C D C S h a s n o t b e e n
completed. (A CDCS terminate request from other
than the last task in a chain will be ignored.) If
the last task in the chain does not issue a CDCS
terminate request, one will be issued automatically
when the last task completes.
The possibility of a deadlock involving CDCS and
another data manager (TOTAL or CRM) exists. For
instance, if task X locks some resources under one
data manager and then tries to lock other resources
under another data manager that task Y initially
locked, then the two tasks may be deadlocked if task
Y tries to lock any of the resources locked by task
X. It is the responsibility of the installation,
applications programmers, and the data administrator
to prevent these situations from occurring. Such
deadlocks can be prevented by locking resources in a
s p e c i fi e d o r d e r o n l y, f o r e x a m p l e , l o c k i n d a t a
m a n a g e r A r e s o u r c e s fi r s t , t h e n d a t a m a n a g e r B
resources, and so forth.
A task will abort if it attempts to use CDCS when
CDCS is not present in the system or if CDCS aborts
while a transaction is connected to it. If a task
aborts while it is connected to CDCS, TAF will issue
an abnormal termination notice to CDCS for the task
(unless the abort originated with CDCS).
RESTRICT clauses cause tasks to automatically
r e q u e s t a d d i t i o n a l c e n t r a l m e m o r y. A l l o f t h e
advice and requirements relevant to a task
requesting that its FL be increased apply when
RESTRICT clause processing is used (refer to Memory
Requests, section 2).
JlP^V
60459500 A
3-1
SYSTEM FILES
This section is intended for the data administrator
and can be omitted by the applications programmer.
CRM DATA MANAGER xxJ FILE
T h i s s e c t i o n d i s c u s s e s f o u r t o p i c s : t h e x x J fi l e ,
j o u r n a l fi l e s , t h e TA F c o n fi g u r a t i o n fi l e , a n d t h e
communication recovery file.
If data base recovery is to be used, the user speci
fied on the USER statement must be able to read the
xxJ file. This can be done by granting read permis
sion to that user or by making the file public.
An xxJ file is associated with each data base and
has the following functions.
The structure of the xxJ file (when using the CRM
Data Manager) is shown as follows.
• Defines the user's user name, password, and
optional user index.
• Defines optional journal files.
<#ffiv
• Defines optional device residence for the
t a s k l i b r a r y a n d s o m e fi l e s s p e c i fi c t o t h e
individual data managers (refer to the xxJ
fi l e d e s c r i p t i o n s t h a t f o l l o w ) .
Up to three journal files can be specified optionally
to supplement the system journalizing. A task can
write to one of the journal files by using the JOURNL
request.
T C F, t h e TA F c o n fi g u r a t i o n fi l e , d e fi n e s t h e d a t a
bases associated with a data manager, defines the
network files and communication recovery files to be
used, and may contain K display commands.
■A procedure file (TAFxxxx) is used to initialize TAF.
Commands may be added to it for recovery or to estab
lish the operating environment. For example, com
m a n d s th a t a t t a c h j o u r n a l fi l e s ( x x J O R n ) a n d d a t a
b a s e fi l e s c a n b e i n c l u d e d I n t h i s fi l e . R e f e r t o
the NOS 2 Installation Handbook for more information
(refer to the preface for the publication number).
xxJ
USER(username,password,
familyname)t
BRF,number
x x J O R l , d e v l c e t y p e , fi l e t y p e .
xxJ0R2.devicetype, filetype.,
xxJ0R3 ,devicetype,filetype.
xxTASKL,PN~packname,
R-device.
Optional,
CRM(xxpfnl,type.mode,users,
locks,mrl,pkl.hash,rec,fwi,
packname,device)
IXN(xxpfxn,naky,packname,
device)
AKY(akn,ako,akl)
AKY(akn,ako,akl)
RMKDEF(xxpfn1,rkw,rkp.kl,0,
kf ,ks,kg,kc,nl,ie,ch)
RMKDEF(xxpfnl,rkw,rkp,kl.O,
kf,ks,kg.kc.nl,le,ch)
One CRM statement
f o r e a c h fi l e .
xxJ FILE
0^**
Required.
An indirect access permanent file, xxJ, where xx is
the data base name, is required for each data base.
If additional journal files are needed, they are de
fi n e d i n t h e x x J fi l e . T h e x x J fi l e I s s a v e d u n d e r
the transaction subsystem user name. The file is in
job command format and varies depending on the data
manager used.
NOTE
The transaction subsystem user name
should be under the control of a data
a d m i n i s t r a t o r. T h e a p p l i c a t i o n s p r o
grammer should not have access to
this name.
CRM(xxpfnn,type,mode,users,
locks,mrl,pkl.hash,rec,
fwi, packname.device)
IXN(xxpfxn,naky.packname,
device)
AKY(akn,ako,akl)
AKY(akn,ako,akl)
RMKDEF(xxpfnn,rkw,rkp,kl,
O.kf,ks,kg,kc.nl,le.ch)
RMKDEF(xxpfnn,rkw,rkp,kl,
O.kf,ks,kg,kc,nl,ie,ch)
tThis is the username, password, and familyname where all data base files and index files described In the
following CRM and IXN statements are located.
60459500 C
4-1
The IXN and AKY statements are necessary only for
multiple indexed files. The IXN statement describes
the index file; the AKY statement describes an alter
nate key. There is one AKY statement per alternate
key. The RMKDEF statement is necessary if the file
has multiple indexes and is recoverable. The RMKDEF
s t a t e m e n t i n t h e x x J fi l e m u s t b e i d e n t i c a l t o t h e
RMKDEF statement used in the initial MIPGEN creation
of the data base file. There must be one RMKDEF
s t a t e m e n t f o r e a c h a l t e r n a t e k e y i n t h e x x J fi l e .
More information on RMKDEF can be found in the CRM
AAM 2 Reference Manual.
The mode parameter controls access
t o t h e fi l e t o e n s u r e t h a t e i t h e r
TAF or a batch job can write on or
m o d i f y t h e fi l e a t a g i v e n t i m e .
H o w e v e r, TA F a n d a b a t c h j o b c a n
r e a d t h e fi l e s i m u l t a n e o u s l y. R e f e r
to the ATTACH command in the NOS 2
Reference Set, Volume 3, for access
modes granted for different combin
ations of multiple access.
NOTE
The parameters for the xxJ file are:
xx
Data
base
name.
I password Batch password.
number
Number of before image recovery
files for this data base.
devicetype
Device type:
If the TAF procedure file
file that is described on a
ment, the mode specified
procedure file overrides the
ameter in the xxJ file.
Number of transactions allowed to
o p e n fi l e x x p f n ^ c o n c u r r e n t l y .
When TAF terminates, the TAF dayfile
contains a message that gives the
number of OPEN requests not granted
because the value of the users par
ameter was exceeded. Each user uses
38 words plus the pkl parameter size
(In words).
MS Mass storage.
MT Seven-track tape.
NT Nine-track tape.
fi l e t y p e
File type (refer to figure 4-1)i
B Buffered write.
locks
R
Pack name of the auxiliary device on
which the user's task library or data
b a s e fi l e s r e s i d e . T h i s p a r a m e t e r
is optional on the CRM statement.
device
Type of device on which the user's
t a s k l i b r a r y o r d a t a b a s e fi l e s
reside. For example, DI (for an
844) or DI3 (for a multiunit 844
consisting of three devices). This
parameter is optional on the CRM
statement.
xxpfn^
type
Number of records the transaction
c a n l o c k f o r fi l e x x p f n * ; . W h e n
T A F t e r m i n a t e s , t h e T A F d a y fi l e
contains a message that gives the
number of locks not granted because
the value of the locks parameter was
exceeded. Each lock uses two words
plus the pkl parameter size (in
words).
Nonbuffered write.
packname
Tw o - t o s e v e n - c h a r a c t e r fi l e n a m e .
xx is the data base name. pfn^ is
t h e r e m a i n i n g z e r o t o fi v e c h a r a c
ters in the data base file name.
BUFFERED
NONBUFFERED
3-WORD HEADER
3-WORD HEADER
DATA
DATA
./S^jjk
EOR
CRM file type:
A K A c t u a l k e y.
attaches a
CRM state
in the TAF
mode par
3-WORD HEADER
3-WORD HEADER
DA Direct access.
IS Indexed sequential.
mode
D ATA
D ATA
Attach mode of file xxpfn^;
EOR
M M o d i f y, a p p e n d , o r r e a d .
R Read.
RM Read, with another user
concurrently attaching the
file in mode M.
W W r i t e , m o d i f y, a p p e n d , o r
read.
4-2
•
•••
••
•
Figure 4-1. Journal File
(Buffered and Nonbuffered Structure)
60459500 C
>f5il!\
/P8^
naky
Number of alternate keys in the index
fi l e .
akn
A l t e r n a t e k e y n u m b e r. A l t e r n a t e k e y
description statements for one data
base file must be ordered in a con
tinuous sequence by alternate key
number. For a detected key, this is
the only parameter present in the
statement.
ako
Alternate key offset. The position
i n t h e r e c o r d o f t h e fi r s t c h a r a c t e r
o f t h e a l t e r n a t e k e y. T h i s c o r r e
s p o n d s t o t h e k e y o ff s e t p a r a m e t e r
used on data manager requests access
i n g t h e r e c o r d b y t h i s k e y. T h e
fi r s t p o s i t i o n i n t h e r e c o r d i s c h a r
acter position number one (not zero).
atcl
Length of
characters.
R T h i s fi l e i s r e c o v e r a b l e .
rkw
N T h i s fi l e i s n o t r e c o v e r a b l e .
When rec is not specified, N
is assumed.
Relative word in the record in which
the alternate key begins, counting
from 0; required.
rkp
Relative beginning character position
within the relative key word (rkw),
counting from 0; required.
kl
Number of characters in the key, 1
to 255; required.
mrl
Number specifying the maximum record
l e n g t h ( i n c h a r a c t e r s ) f o r fi l e
xxpfn^.
pkl
Number specifying t h e l e n g t h i n
characters of the primary key for
fi l e x x p f n ^ . t
hash
One- to seven-character indirect
access file that contains the binary
code of the hashing routine for file
x x p f n j . . T h i s i n d i r e c t a c c e s s fi l e
must be stored under the username
parameter on the USER statement.
The entry point for the hashing rou
tine must be this file name (hash).
If this parameter is omitted, CRM
uses the hashing routine supplied
with CRM. This parameter applies
only for CRM direct access files.
F i l e r e c o v e r a b i l i t y.
NOTE
A d d i n g r e c o v e r a b l e fi l e s t o t h e d a t a
base that has a record or key length
l a r g e r t h a n a n y p r e v i o u s l y s p e c i fi e d
r e c o v e r a b l e fi l e c a u s e s r e c o v e r y fi l e
v a l i d a t i o n e r r o r s d u r i n g TA F i n i t i a l
i z a t i o n . B e f o r e i m a g e r e c o v e r y fi l e s
need to be recreated and after image
recovery files need to be dumped to
tape (via DMREC) and recreated. To
e n s u r e f u l l d a t a b a s e r e c o v e r a b i l i t y,
recoverable files should only be added
to the data base following a normal
termination of TAF.
fwi
Forced write indicator. When the
f o r c e d w r i t e i n d i c a t o r i s O F F, t h e
m o d i fi e d d a t a fi l e b u f f e r s a r e w r i t
ten to disk when space is needed.
When the forced write indicator is
O N , a l l d a t a fi l e b u f f e r s t h a t a r e
modified in core are written to disk
i m m e d i a t e l y. I f f w i i s n o t s p e c i
fi e d , t h e f o r c e d w r i t e i n d i c a t o r i s
set to OFF.
alternate
key
in
Required to mark position for the
r e s e r v e d fi e l d .
kf
Key format; required.
0 or S Symbolic.
1 o r I I n t e g e r.
2 or U Unco Hated symbolic.
3 or P Purge alternate key defi
nition from the index.
ks
Substructure for each primary key
list in the index; optional.
U Unique (default).
I Indexed sequential; recom
m e n d e d f o r e f fi c i e n c y i n
processing.
F F i r s t - i n , fi r s t - o u t .
Y Sets forced write ON for this
fi l e .
kg
N Sets forced write OFF for
t h i s fi l e .
Length in characters of the repeating
group in which the key resides.
kc
Number of occurrences of the repeat
i n g g r o u p ; z e r o f o r T- t y p e r e c o r d s ,
and a number for a repeating group
embedded within the record.
x x p f x n P e r m a n e n t fi l e n a m e o f t h e i n d e x
fi l e ; m u s t b e g i n w i t h t h e t w o - l e t t e r
a p p l i c a t i o n i d e n t i fi e r x x .
tThe user can specify octal numbers and decimal numbers by using a postradix of B or D, respectively.
Decimal is the default.
/#*N
60459500 C
4-3
nl
Null suppression; a null value is
all spaces (symbolic key) or all
zeros (integer key):
0 Null values
(default).
are indexed
n
User
index
(obtained
analyst).
MS Mass storage.
MT Seven-track tape.
Include/exclude sparse control char
acter:
I Include alternate key value
if the record contains a
sparse control character.
E Exclude alternate key value
if the record contains a
sparse control character.
ch
Characters that qualify as sparse
control characters; up to 36 letters
a n d d i g i t s c a n b e s p e c i fi e d a s a
character string.
site
devicetype Device type:
N Null values are not indexed.
ie
from
NT Nine-track tape,
fi l e t y p e F i l e t y p e ( r e f e r t o fi g u r e 4 - 1 ) :
B Buffered write.
R Nonbuffered write.
packname Pack name of the auxiliary device on
which the user's task library
(xxTASKL) or data sets will reside.
d e v i c e Ty p e o f d e v i c e o n w h i c h t h e u s e r ' s
fi l e w i l l r e s i d e [ f o r e x a m p l e , D I
(for 844) or DI3 (for a multiunit
844 consisting of three devices)].
Four-character data set names.
TOTAL DATA MANAGER xxJ FILE
T h e f o l l o w i n g s h o w s t h e s t r u c t u r e o f t h e x x J fi l e
when using the TOTAL Data Manager.
xxJ
CDCS OR NO DATA MANAGER xxJ FILE
USER(username,password,familyname)t
If an application uses CDCS and one of the other data
managers (CRM or TOTAL)-, then the xxJ file should be
structured as specified for the other data manager.
UI»n.
x x J O R l . d e v i c e t y p e , fi l e t y p e .
x x J 0 R 2 . d e v i c e t y p e , fi l e t y p e .
x x J 0 R 3 . d e v i c e t y p e , fi l e t y p e .
xxTASKL,PN-packname,R-device.
NL.
LG,PN=packnarae,R-device.
aaaa,PNapackname,R-device
Optional.
Either the NL
statement or the
LG statement must
be selected. PN
and R parameters
are optional. NL
c a u s e s TO TA L t o
not log recovery
data. LG causes
TOTAL to log re
covery data.
PN and R parame
ters are optional.
zzzz,PNapackname,R-device
The parameters for the xxJ file are:
xx
Data
base
name.
If an application accesses only the CDCS Data Manager
or no data manager, the structure of the xxJ file is
as follows:
xxJ
USER(username,password,familyname)t
x x J O R l , d e v i c e t y p e , fi l e t y p e .
x x J 0 R 2 , d e v i c e t y p e , fi l e t y p e . O p t i o n a l .
x x J 0 R 3 . d e v i c e t y p e , fi l e t y p e .
xxTASKL,PN-packname,R-device
The parameters are:
Parameter
Description
xx Application (data base) name.
password Batch password,
devicetype Device type:
MS Mass storage.
MT Seven-track tape.
password Batch password.
NT Nine-track tape.
tTAF locates the data base using the familyname parameter in the procedure file that initializes TAF and the
username and password parameters in the xxJ file. The username, password, and familyname parameters are
used for validation.
/<5SR^\
4-4
60459500 C
filetype File type (refer to figure 4-1): CREATING AN xxJ FILE
B B u f f e r e d w r i t e . To e n t e r a n x x J fi l e , t h e d a t a a d m i n i s t r a t o r c a n r u n
a batch job to create and save the file under the
R Nonbuffered write. transaction subsystem user name. This can also be
done at a terminal through IAF. (Refer to the NOS 2
packname Pack name of the auxiliary device on Reference Set, Volume 1, for IAF operating
which the user's task library instructions.)
resides.
device Type of device on which the user's
task library resides.
/0&<
60459500
C
4-4.1/4-4.2
|
/ ^ ! j \
0^\
0^\
JOURNAL FILES
jnum
JOURO (the system journal
fi l e t o w h i c h t h e t r a n s a c
tion executive normally
makes journal entries).
The two types of journal files are system and data
b a s e fi l e s .
SYSTEM JOURNAL FILE
The system journal file (a direct access file named
JOURO that may be defined under the transaction sub
system user name or may be set up by the TAFxxxx
p r o c e d u r e fi l e a t i n i t i a l i z a t i o n ) i s n o t a s s o c i a t e d
with any particular data base. All transaction data
(input from terminals), errors, and transaction com
p l e t i o n n o t i fi c a t i o n i s a u t o m a t i c a l l y r e c o r d e d o n
JOURO. The terminal status table is also journalized
periodically. Data sent to terminals by tasks is not
recorded on JOURO. JOURO will be created at initial
ization if not already present under the transaction
facility user name.
Journal File
D a t a b a s e j o u r n a l fi l e
xxJORl.
D a t a b a s e j o u r n a l fi l e
xxJ0R2.
Data base
xxJ0R3.
journal
fi l e
message Name- of the 01-level data item con
taining the message to be journal
ized.
FORTRAN
DATA BASE JOURNAL FILES
The transaction subsystem allows up to three users p e c i fi e d d i r e c t a c c e s s j o u r n a l fi l e s f o r e a c h d a t a
base. The allowable names are xxJORl, xxJ0R2, and
xxJ0R3, where xx is the data base name. At initial
i z a t i o n , TA F c h e c k s t h e x x J fi l e s a s s o c i a t e d w i t h
all active applications to determine which xxJORn
fi l e s a r e n e e d e d . I t w i l l t h e n a t t a c h a n y s p e c i fi e d
x x J O R n fi l e s n o t a l r e a d y a t t h e c o n t r o l p o i n t a n d
a t t e m p t t o d e fi n e a n y w h i c h i t c a n n o t fi n d . T h e
transaction subsystem user name must have write
p e r m i s s i o n o n t h e s e fi l e s . W h e n a t a s k m a k e s a
journal request (refer to JOURNL request in this sec
tion) , the data base for which the originating termi
nal is validated is used to determine the journal
fi l e o n w h i c h t o w r i t e . I f t h e t a s k i s a s s o c i a t e d
with a terminal validated for all data bases, the
data base specified on the last data base request is
used to determine the proper journal file.
JOURNAL FILE ENTRY HEADER
Each journal file entry (refer to JOURNL request) has
a header In the format shown in figure 4-2.
CALL JOURNL(jnum.message,length)
jnum
Integer whose value indicates the
n u m b e r o f t h e j o u r n a l fi l e t o w h i c h
the entries are to be made.
Journal File
JOURO (the system journal
file to which the transaction
executive normally makes
j ournal en tr ie s).
Data base
xxJORl.
journal
fi l e
Data base
xxJ0R2.
journal
fi l e
Data base
xxJ0R3.
journal
fi l e
message Name of the array containing the mes
sage to be journalized.
l e n g t h I n t e g e r w h o s e v a l u e s p e c i fi e s t h e
length of the message in characters.
COMPASS
JOURNL REQUEST
The JOURNL request allows file entries to be made to
supplement automatic journalizing.
JOURNL address
address Address of a parameter table in the
form shown in figure 4-3.
The format is:
COBOL
ENTER JOURNL USING jnum message.
jnum Computational-l item whose value in
dicates the number of the journal
fi l e t o w h i c h t h e e n t r i e s a r e t o b e
made. The value of this parameter
m u s t b e r i g h t - j u s t i fi e d a n d z e r o fi l l e d .
jf*K
60459500 A
If a journal file is defined on magnetic tape and an
end-of-reel is detected, the transaction executive
unloads the tape and checks for another tape on which
to write. If the operator has not preassigned a
unit, the journal file is placed on mass storage. If
the operator enters the K.ASSIGN command, the trans
action executive copies the mass storage journal file
to the tape and places all subsequent entries on the
t a p e . I f t h e m a s s s t o r a g e fi l e d o e s n o t fi t o n t h e
tape, the message * UNABLE TO USE TAPE* is issued.
4-5
59
35
sequence
11
17
29
reserved
origin
length
y^SSN
task name
hr
username
min
see
reserved
sequence
Transaction sequence indicator.
origin
Origin indicator (octal):
0 Task origin (JOURNL request).
1 Tr a n s a c t i o n s u b s y s t e m o r i g i n ( i n p u t ) .
2 Data manager origin.
3 Tr a n s a c t i o n s u b s y s t e m r e c o v e r y / s t a t i s t i c a l d a t a .
4 E n d - o f - t r a n s a c t i o n i n d i c a t o r.
5 Incomplete block of terminal input data.
6 Te r m i n a l i n p u t f o r a n i n t e r a c t i v e t a s k .
7 I l l e g a l i n t e r c o n t r o l p o i n t t r a n s f e r.
10 On-line LIBTASK update (TT option).
11 CDCS detected error (words following header contain error message).
12 MSG request with zero function code. Normal FORTRAN messages are logged
with this function code.
length
Length of entry (equals header plus data block).
task name
Name of task if task origin requested.
hr,min, sec
Packed time (hour, minute, second).
username
User name associated with transaction, if task origin.
Figure 4-2. Journal File Entry Header
59
53
'////
m>
jnum
35
jnum
17
numwords
0
message
J o u r n a l fi l e n u m b e r, r i g h t - j u s t i fi e d w i t h b i n a r y z e r o fi l l :
0 J O U R O ( r i g h t - j u s t i fi e d w i t h b i n a r y z e r o fi l l : m a k e s j o u r n a l e n t r i e s ) .
1 to 3 Data base journal file (xxJORl, xxJOR2, or xxJ0R3).
numwords
Length of message in words.
message
Address of message to be journalized.
Figure 4-3. JOURNL Parameter Table
4-6
60459500 B
/*tWsv
OFF Data bases specified
on the same statement
are not made available
for TAF processing.
TAF CONFIGURATION FILE
The TAF configuration file is a required indirect
access permanent file saved under the transaction
facility user name. This file is used during TAF
i n i t i a l i z a t i o n a n d r e c o v e r y. I f i t i s n o t l o c a l
when the TAFREC command is reached, TAFREC will
attempt to get it from TAF's user index. The TCF
has the following format:
USER,UN,PW,FM.
DMS ,datamanager,switen,xxj,
XX 2 , . . . , 2CKfi.
NETWORK,ID-i,FM-faraily,
UN-username.
At least one of
each required.
RECOVER,ID-i,MS»maximumsize,
NM-number.
Required or not
allowed (refer to
statement de
scription.
TABCON.n
Required for
batch concur
rency. Refer to
the TAF/CRM Data
Manager Reference
Manual.
DISPLAY,status.
K. command Rvalue i ,
Optional.
DMS STATEMENT
DMS statements on the TCF are used to specify the
data managers to be loaded by TAF and the applica
tions (data bases) to be associated with each data
manager.
The format is:
DMS.datamanager.switch.xxj,xx2,...,xxn.
data
manager
r
switch
xxyyyy
which is the data base name (the
DBMODt file name) specified in
the DATA-BASE-NAMEt statement
of the DBDLt statements, xx is
the unique TAF data base name
and yyyy is any combination of
four alphanumeric characters.
A separate DMS statement for CDCS (OTHER) is not
necessary if CDCS is to be used in conjunction with
another data manager.
The TCF file must contain at least one DMS statement
and each DMS statement with status set to ON must
have at least one data base identifier or TAF will
abort.
The maximum number of data bases that may be associ
ated with one data manager is specified by the in
stallation parameter MAXDB. This value is 25 unless
it is altered by the user's site.
K. commandnsvalue(i
jgp*v
x x i D a t a b a s e i d e n t i fi e r . M u s t n o t
be duplicated on the same or
any other active DMS statement.
For the CRM Data Manager, it is
the two-letter data base name.
For the TOTAL Data Manager, this
parameter has the format:
Name of the data manager. Must
be CRM, TOTAL, or OTHER. The
same data manager can be speci
fied on any number of DMS state
ments. Use the datamanager
value OTHER for specifying an
application that is either not
associated with a data manager
or is associated only with the
CDCS Data Manager.
Data manager status.
ON or OFF.
The maximum length of each DMS statement is 160 6-bit
display code characters.
DISPLAY STATEMENT
The DISPLAY statement on the TCF controls whether or
not the TAF K display will appear at the consoLe dur
ing initialization and recovery. However, an error
in a K display command causes TAFREC to issue an
error message and bring up the K display for correc
tions regardless of the DISPLAY statement. The
format is:
DISPLAY,status.
status
Mus t be
O N T h e s p e c i fi e d d a t a
manager (TOTAL or CRM)
will be loaded. The
data bases specified
on the same statement
are to be made avail
able for TAF process
ing. These data bases
are referred to as
active.
4m<-
A variable having one of the
following values.
ON K display will appear
at the console during
initialization and
recovery to enable the
operator to make
changes at those times.
OFF K display will not
appear at the console
during Initialization
and recovery.
tRefer to the TOTAL - CDC 2 Reference Manual for a detailed description.
60459500 C
4-7
NETWORK STATEMENT
The NETWORK statements on the TCF declare the
n e t w o r k fi l e s ( N C T F i ) TA F u s e s t o d e t e r m i n e t h e
users allowed to access TAF. There must be at least
one and a maximum of eight NETWORK statements. The
format is:
NETWORK,ID-i,FM-familyname,UN=username.
TAF will use. The name of the corresponding CRF is
ZZCRFi. The CRF resides under the same family and
user name as the corresponding network file.
K. STATEMENT
integer specifying a unique
n e t w o r k fi l e i d e n t i fi e r . T h e
range is zero to seven. This
i d e n t i fi e r
is
used
in
constructing the name of the
network file (NCTFi).
Any K display commands that can be issued under the
i n i t i a l K d i s p l a y c a n a p p e a r i n t h e T C F. Va l u e s
s p e c i fi e d i n t h e T C F b e c o m e t h e d e f a u l t values in
place of the installation defaults (refer to the K
display utilities in the NOS 2 Analysis Handbook for
the installation default values). If the operator
changes any of these values during initialization,
those changes remain in effect if TAF is restarted
in recovery mode.
familyname The family name under which the
n e t w o r k fi l e e x i s t s . I f t h e
familyname parameter is not
s p e c i fi e d , t h e d e f a u l t f a m i l y
name is used.
If K display commands are used in the TCF, they must
appear consecutively.
i
An
The user name under which the
n e t w o r k fi l e e x i s t s . I f t h e
username parameter is not
specified, the TAF user name is
used.
RECOVER STATEMENT
The RECOVER statement on the TCF declares the set of
fi l e s TA F i s t o u s e w h e n i n r e c o v e r y m o d e . T h i s
d i r e c t i v e i s r e q u i r e d i f TA F i s a s s e m b l e d w i t h
recovery, but it is not allowed if TAF is assembled
without recovery.
The format is:
USER STATEMENT
The USER statement on the TCF specifies the user
n a m e u n d e r w h i c h TA F i s t o r u n . T h i s u s e r n a m e
should be defined through MODVAL to have the same
user index as defined by the installation parameter
TRUI. Only one USER statement is allowed in the
TCF. The format is as follows:
USER,UN,PW,FM.
or
ACCOUNT,UN,PW.FM.
Parameter
Description
U N T h e u s e r n a m e u n d e r w h i c h TA F i s t o
run.
PW The batch password for the user name.
RECOVER,ID-i,MS-maximumsize,NM-number.
1
An
integer specifying a unique
r e c o v e r y fi l e i d . T h e r a n g e i s
zero to seven. This id is the
id used in constructing the
name of the communication
r e c o v e r y fi l e ( Z Z C R F i ) . O n l y
o n e i d m a y b e s p e c i fi e d p e r
RECOVER statement. The id must
m a t c h a n i d s p e c i fi e d i n a
NETWORK statement.
maximumslze An integer specifying the maxi
mum size of the message, in
words, that TAF will record on
the communication recovery file.
The default Is 57. Maximum is
installation parameter MAXWS.
This is the maximum message
size for the RPUT and SECURE
requests.
number An integer specifying the maxi
mum number of user messages that
can be recorded on the communi
c a t i o n r e c o v e r y fi l e v i a t h e
RPUT request. The default Is
zero, the maximum is 10.
Each RECOVER statement specifies a recovery id. This
id determines the communication recovery file that
4-8
F M T h e f a m i l y u n d e r w h i c h TA F i s t o r u n .
The USER statement should be the first statement in
the TCF.
COMMUNICATION RECOVERY FILE
A communication recovery file is a file TAF uses to
maintain recovery information about recoverable
transactions. New CRFs are created and existing
CRFs are reinitialized at initialization time by
using the K.INT command (refer to section 8). There
c a n b e u p t o e i g h t o f t h e s e fi l e s ( n a m e d C R F O ,
CRF1,...,CRF7).
Each one corresponds to a network file having the
same Identifier (NCTFO, NCTFI,....NCTF7). For every
u s e r d e s c r i p t i o n s t a t e m e n t i n a n e t w o r k fi l e , t h e r e
I s a u s e r e n t r y i n t h e c o r r e s p o n d i n g C R F. T h e s e
entries are added and deleted as follows:
• New user entries are added to a CRF by
adding a user description statement to the
corresponding network file.
• User entries are removed from a CRF by
removing the user description statement from
the corresponding network file.
60459500 C
/^^^Sv
TRANSACTION FACILITY (TAF) K DISPLAYS
The following commands control operation of the TAF Subsystem. Initiate the TAF Subsystem
by using the TAFffff command before issuing these commands.
INITIATING TAF K DISPLAY
When the transaction executive is brought to a control point, the message
REQUEST *K* DISPLAY appears at the control point if a DISPLAY,ON command is specified
i n t h e TA F c o n fi g u r a t i o n fi l e . R e s p o n d w i t h t h e e n t r y :
K , TA F.
Any of the following initialization commands can then be entered. If no values are to be
changed, enter the command:
K.END.
Values are decimal unless otherwise indicated.
Command
8-68
Description
K.BFL=n.
Changes the starting and minimum field length allocated by TAF to
CRM (200008 < n < 100000s). Default is 700008.
K.CMB=n.
Changes the maximum number of communication blocks allowed to the
TAF Subsystem (7 < n <^ 40). Default is 40.
K.ECS=n.
Sets the extended memory field length to be used by the transaction
executive; n is octal thousands of words. Default is 0.
K.EFL=n.
Changes the maximum additional central memory field length made
available to CRM for buffers and capsules (0 < n < 100000s).
Default is 0.
K.END.
Ends input of the transaction executive initialization parameters.
Initialization is completed when the TAF K display appears.
60459300 D
Command
K.ER0=CRF,op.
Description
Specifies whether to override certain I/O and logic errors when
processing the communication recovery files (CRF).
op
Description
NO
Aborts if I/O or logic errors are encountered while
p r o c e s s i n g t h e c o m m u n i c a t i o n r e c o v e r y fi l e s . T h i s i s
the default setting.
YES
I/O or logic errors encountered on a run unit header
record result in the loss of that run unit with no
i n d i c a t i o n t o t h e t e r m i n a l u s e r. T h e l o s s i s n o t e d o n
the recovery report.
I/O or logic errors encountered
within a run unit result in a
status field is set in the run
to inform the terminal user of
on a message record
loss of that run unit. A
unit header, allowing TAF
the run unit loss.
I/O or logic errors encountered on the CRF header record
result in an unconditional abort of the TAF Subsystem.
K.GO.
Ends input of the transaction executive initialization parameters.
Initialization is complete when the TAF K display appears.
K . I N T = t y p , fi l e i d ,
Specifies which communication recovery files (CRF) are to be
i n i t i a l i z e d . T h i s i s t h e o n l y w a y t o i n i t i a l i z e a C R F. F i l e s
specified on a RECOVER command in the TAF configuration file and
s p e c i fi e d i n t h i s c o m m a n d a r e i n i t i a l i z e d . F i l e s s p e c i fi e d o n a
RECOVER command but not specified in this command are used for
r e c o v e r y.
This command also specifies whether CYBER record manager (CRM) data
base recovery files are initialized or recovered. For CRM recovery
files, this command is valid regardless of TAF assembly parameters.
HE
60459300 D
Description
CRF
C o m m u n i c a t i o n r e c o v e r y fi l e s . T h i s p a r a m e t e r i s v a l i d
only if the installation parameter IPTAR equals 1.
CRM
CYBER Record Manager after-image and before-image
r e c o v e r y fi l e s .
8-69
Command
DescriDtion
fi l e i d
Description
n A d i g i t f r o m 1 t o 7 t h a t d e fi n e s a C R F t o b e
initialized. The digit corresponds to the ID parameter
on the RECOVER command in the TAF configuration file.
This parameter is not valid for CRM recovery files.
A L L I f t y p i s C R F, a l l c o m m u n i c a t i o n r e c o v e r y fi l e s d e fi n e d
by RECOVER commands in the TAF configuration file are
i n i t i a l i z e d . I f t y p i s C R M , a l l C R M r e c o v e r y fi l e s a r e
initialized.
NOTE
This parameter must be used with caution
when typ is CRM since the CRM update history
c u r r e n t l y o n t h e a f t e r - i m a g e r e c o v e r y fi l e s
is lost.
NONE If typ is CRF, communication recovery files are
i n i t i a l i z e d ; a l l c o m m u n i c a t i o n r e c o v e r y fi l e s s p e c i fi e d
in RECOVER commands in the TAF configuration file are
recovered. If typ is CRM, all CRM data bases are
recovered based on information in the existing recovery
fi l e s . N o C R M r e c o v e r y fi l e s a r e i n i t i a l i z e d . T h i s
fileid is the default for both typ=CRF and typ=CRM.
K.MFL=n.
Sets the maximum field length to be used by the transaction
executive (40000 < n <_ 376600). Default is 376600.
K.REC=a.
Specifies whether to set the recovery bit in the user area of each
terminal status table entry (YES or NO). If YES, the user recovery
bit is set. If NO, the value of the user recovery bit is not
changed from what it was before the command was issued. Default is
NO.
K.SCP=n.
Changes the number of subcontrol points (2 <^ n < 31). Default is 31
K.STOP.
A b o r t s t h e TA F S u b s y s t e m i n i t i a l i z a t i o n u n c o n d i t i o n a l l y.
K.TFL=n.
Changes the value used as the upper bound for TARGET. This is the
amount of memory CRM uses for data and index blocks
(100008 £3$!%>t
transaction data
length
Length of the transaction in words; Includes the header word and the trans
action data.
transaction data
Transaction name (or transaction name and input data) to be processed by TAF.
Figure 5-1. BTRAN Header Word
BTRANEX.
USER,XYZ1234,XYZ1.
CHARGE,*
C0B0L5.
LIBLOAD(TRANLIB,BTRAN)
LGO.
- -EOR- IDENTIFICATION DIVISION.
PROGRAM-ID. BTRANEX.
ENVIRONMENT DIVISION.
CONFIGURATION SECTION.
SOURCE-COMPUTER. CYBER.
OBJECT-COMPUTER. CYBER.
DATA DIVISION.
WORKING-STORAGE SECTION.
01 BATCH-TRANSACTION.
02 RESERVED-AREA
PIC X<7)
02 DATA-LENGTH
VALUE 2 C O K P - 4
PIC 9999
02 TRANSACTION-DATA
VALUE I S " L P 3 , 5 0 "
PIC X(6)
01 BTRAN-STATUS
VALUE IS 0 COMP-1
PIC 9999
PROCEDURE DIVISION.
START-RUN.
ENTER BTRAN USING BATCH-TRANSACTION, BTRAN-STATUS.
DISPLAY "STATUS*" BTRAN-STATUS.
STOP RUN.
Figure 5-2. BTRAN Request
Table 5-1. BTRAN Status Values
Value
I
Transaction submission is complete.
3
The transaction executive is not
present.
5
The transaction executive Is busy
(should not occur; inform site
analyst).
7
5-2
Des c r ipt ion
The submit block is too long; the maxi
mum length is 62 words.
11
The transaction subsystem is not de
fined as a system control point (should
not occur; inform site analyst).
13
Access to TAF is denied because TAF i3
idling down.
Value
Description
15
The user name associated with the batch
job issuing the BTRAN request is not
v a l i d a t e d i n n e t w o r k fi l e ( j o b i s
aborted).
17
The user name associated with the batch
job issuing the BTRAN request is cur
rently in use within TAF.
19
A conflict in access types was detec
ted, the previous transaction run
u n d e r t h e s p e c i fi e d u s e r n a m e w a s
recoverable and not associated with a
BTRAN-initiated transaction.
21
The transaction data is not within the
field length oE the batch job.
60459500 C
SUBMT REQUEST
COMPASS
The SUBMT request allows a task to route a job to the
local batch input queue. The address parameter in
the call points to the area in the task field length
that contains the job to be routed in control word
format. This format is described in conjunction with
the READCW macro in the NOS 2 Reference Set, Volume
4 (refer to the preface for the publication number).
Using this format, the job may consist of multiple
records.
SUBMT address
a d d r e s s A d d r e s s o f t h e fi r s t w o r d o f t h e
job data to be routed in control
w o r d f o r m a t a s s h o w n i n fi g u r e
5-3.
The first word at address must be a control word in
t h e f o r m a t s h o w n p r e v i o u s l y. T h e l e n g t h fi e l d m u s t
specify the number of 12-bit bytes occupied by the
data in the PRU (maximum of 320 bytes, equivalent to
640 characters). The level number in the trailing
control word specifies whether the PRU is an end-ofr e c o r d o r e n d - o f - fi l e . I f a l o g i c a l r e c o r d e x t e n d s
over more than one PRU, the level number for the
first PRU of the record must be nonzero and other
than 173.
The format is:
COBOL
ENTER SUBMT USING address.
address
Name of the 01-level item
containing the job data to be
routed. This data is in the
format shown in figure 5-3.
A leading and a trailing control word must be
present for each PRU of data.
FORTRAN
CALL SUBMT(address)
Typically, the data would consist of commands which |
would comprise one record. Additional data to be
processed by the batch job could also be present and
typically constitute subsequent records.
address Name of an array containing the
job data to be routed. This
data is in the format shown in
fi g u r e 5 - 3 .
59
»7
0
42
1
23
0
Itngth
data word
data word
4
p
4
number of
y central
, memory word*
data word
lave)
length
Length in 12-bit (two-character) bytes of job data following this control word
(must be five times the number of the central memory words).
level
Logical record level number:
0 or omitted This PRU is an end-of-record.
17g
This
PRU
is
an
e n d - o f - fi l e .
Figure 5-3. SUBMT Parameter Table
60459500 C
5-3
Figure 5-4 shows a task using the SUBMT request.
In the example shown in figure 5-4, the first word
of JOB (00390 to 00410) sets bit 42 in the header
word and gives the length (75) in 12-bit bytes of
the card deck images to follow* This is five times
the number of 10-character (60-bit) words in the job
being submitted, in this case, statements 00420 to
00590.
Each job command must be from 1 to 80 characters
long. All commands to be submitted must be padded
to a multiple of 10 characters and the last 2
characters must be binary zero (character ":" in the
63/64-character set). Thus, if a statement ends in
character position 9,10; 19,20; and so on, a zero
word must be appended. Statements 00460 to 00530
give examples of this.
00100
00110
00120
00130
00140
WORKING -STORAGE SECTION.
01 JOB
0 3 FILLER
0 3 FILLER
0 3 JOB-LENGTH
*
00420
00430
00440
00450
00460
00470
00480
00490
00500
00510
00520
00530
00540
00550
00560
00570
00580
00590
03
03
03
00600
00610
00620
00630
00640
00650
00660
• Include the command SETJOB,DC=DF in the
submitted job. This directs that implicit
output is to be queued at the end of the job.
The example in figure 5-4 uses the first method by
including a ROUTE command at line 00580.
( r e f e r t o !s e c t i o n 2 )
VALUE I S 1
VALUE I S 0
VALUE I S 7 5
COMP-4
COMP-4
COMP-4
PIC 9 ( 5 ) .
PIC 9 ( 5 ) .
PIC 9 ( 6 ) .
THE FOLLOWING IS THE JOB TO BE SUBMITTED
03
*
*
Include ROUTE commands to place the desired
files in the appropriate queues.
IDENTIFICATION DIVISION.
PROGRAM-ID. SUBTEX1.
ENVIRONMENT DIVISION.
DATA DIVISION.
COMMON-STORAGE SECTION.
Standard COBOL Communication Block
00370
00380
00390
00400
00410
At job termination, the implicit output files of the
SUBMT job are not queued by the system. This is
because TAF routes the submitted job using the
disposition code DCaN0. To obtain output from the
job, do either of the following:
JOB-CARD.
05 JOB-ID
05 FILLER
JOB-USER.
05 USER-CARD
05 FILLER
JOB-CHARGE.
05 CHG-CARD
05 FILLER
JOB-DATA.
05 COMMENT
05 FILLER
05 CTR-STATUS-1
05 FILLER
05 CTR-STATUS-2
05 FILLER
05 CTR-STATUS-3
05 FILLER
VALUE I S " J O B . "
VALUE IS A L L " : "
PIC X ( 4 ) .
PIC X ( 6 ) .
VALUE I S "USER,DWG2603,ABC123."
VALUE IS A L L " : "
PIC X ( 2 0 ) .
PIC X ( 1 0 ) .
VALUE I S "CHARGE,5927,693X451."
VALUE IS A L L " : "
PIC X ( 2 0 ) .
PIC X ( 1 0 ) .
VALUE
VALUE
VALUE
VALUE
VALUE
VALUE
VALUE
VALUE
IS
IS
IS
IS
IS
IS
IS
IS
"* SUBMIT BATCH J08."
ALL ":"
"REWIND,INPUT."
ALL ":"
"C0PYSBF."
ALL ":"
"R0UTE,0UTPUT."
ALL ":"
PIC
PIC
PIC
PIC
PIC
PIC
PIC
PIC
X(19).
X ( 11 ) .
X(13).
X(7).
X(8).
X(2).
X<13).
X(7).
SUBMITTED JOB ENDS HERE
0 3 INPUT-LEVEL
0 3 FILLER
PROCEDURE DIVISION.
START-UP.
ENTER SUBMT USING JOB.
DISPLAY "JOB SUBMITTED."
STOP RUN.
VALUE I S 1 5
VALUE IS A L L " : "
COMP-4
2/L
15"
PIC 99.
PIC X ( 8 ) .
Figure 5-4. SUBMT Request
5-4
60459500 A
/J5W^k
MEMORY DUMPS
A task can perform two types of memory dumps. The
first type is a task dump, which is a dump of the
task field length, exchange package, and associated
data buffers. A task dump aids the applications
programmer in debugging a task. The second type Is
a TAF dump, a dump of all or part of the TAF field
length. A TAF d u m p c o n t a i n s p e r t i n e n t i n f o r m a t i o n
that is not contained in a task dump. This section
describes the methods used to obtain both types of
memory dumps.
All task dumps, whether due to an aborted task, an
abnormal CEASE request, or a CMDUMP request, are
h a n d l e d i n t h e s a m e m a n n e r. A j o b fi l e i s c r e a t e d
containing the information to be dumped in binary
format, as well as a command record. The transaction
executive issues a ROUTE request releasing the job
fi l e t o t h e i n p u t q u e u e f o r b a t c h p r o c e s s i n g . A
program called KTSDMP is used, either to generate
l i s t a b l e o u t p u t f r o m t h e b i n a r y fi l e , o r t o t r a n s f e r
it to a direct access permanent file.
TASK DUMP
When dumping to an output queue, a ROUTE command is
included in the command record to direct the output
produced by KTSDMP to the proper queue.
The central memory dump (CMDUMP) request dumps
central memory according to the parameters specified
in the direct subsequent dumps (DSDUMP) request.
Parameters specified on the DSDUMP request are used
under three circumstances.
• When a fatal task error occurs.
• When a default value is requested in a
CMDUMP request.
• When a parameter is in error in a CMDUMP
request.
The purpose of DSDUMP and CMDUMP is to aid
applications programmers in debugging their tasks.
These dump requests allow users to dump any portion
o f t h e i r p r o g r a m s . T h e u s e r s p e c i fi e s t h e fi r s t
word address (fwa) and the last word address (lwa)
of the area to be dumped. The exchange package may
also be dumped by setting the proper parameter(s) to
a nonzero value.
r
The DSDUMP request sets up default values for
subsequent CMDUMP requests made by this task and all
linked tasks in this transaction (those called by
CALLTSK without CEASE). DSDUMP does not cause a
dump; it only sets parameter values that can be
defaulted as a result of a CMDUMP request.
A USER command is always included, thus enabling
KTSDMP to attach the appropriate file if the dump is
d e s t i n e d f o r a u s e r ' s fi l e . I n t h i s c a s e , K T S D M P
appends the binary information to the end of the
p e r m a n e n t fi l e . T h i s m e t h o d o f h a n d l i n g d u m p s
relieves the transaction executive of time-consuming
processing that is better performed by a utility.
DSDUMP REQUEST
The DSDUMP request allows the applications
programmer to change any of the default values of
the CMDUMP request. The DSDUMP does not cause a
dump in itself, except when the system detects an
error (that is, aborts). Any default values on the
D S D U M P a r e s a t i s fi e d f r o m t h e g e n e r a l d e f a u l t
values* All six parameters are required. If an
error occurs on any DSDUMP parameter, the task is
aborted.
The format is:
COBOL
ENTER DSDUMP USING fwa lwa ep db oq qd.
A hierarchy of parameter values allows users to
default any parameters they want on DSDUMP or CMDUMP
calls. At system assembly time, default values are
assembled for each parameter. These default values
can be changed via a K display command. In
addition, if users want to change any default
parameter values for their tasks, they may do so by
using DSDUMP requests.
This hierarchy of default values works in the
following manner. The CMDUMP request causes a dump
a c c o r d i n g t o t h e p a r a m e t e r s i t s p e c i fi e s . I f a
default option is requested, the system determines
if a DSDUMP request has been made for this
transaction. If a DSDUMP request has been made and
if the corresponding parameter value has been
supplied, this value is used. If DSDUMP requests
have not been specified, a new default value, the
system default value for this parameter, is used.
60459500 C
fwa
C o m p u t a t i o n a l - 1 i t e m t h a t s p e c i fi e s
beginning address of task memory to
be dumped; legal values are 0 0 Dump exchange package.
< 0 Use default value.
db
oq
ep
I n t e g e r t h a t s p e c i fi e s t h e e x c h a n g e
package option.
Performs no function. Retained for
compatibility with previous releases.
0 Do not dump exchange package.
> 0 Dump exchange package.
C o m p u t a t i o n a l - l i t e m t h a t s p e c i fi e s
output queue option.
< 0 Use default value (refer to
following note).
0 Dump to local batch output
queue.
1 Dump to remote batch output
queue*
< 0 Use default value.
db
Performs no function. Retained for
compatibility with previous releases.
oq
Output queue option.
< 0 Use default value (refer to
following note).
2 D u m p t o u s e r p e r m a n e n t fi l e
defined under data base user
number.
qd
0 Dump to local batch output
queue.
1 Dump to remote batch queue.
Queue destination option; value
depends on oq selection.
oq
0
2 D u m p t o u s e r p e r m a n e n t fi l e
defined under data base user
number.
qd
P r i n t e r i d , s p e c i fi e d a s a
c o m p u t a t i o n a l - l n u m b e r. I f
negative, use default value
(refer to following note).
qd
Queue destination option;
depends on oq selection.
User
number
' A valid name
s p e c i fi e d i n
display-coded,
Direct
l e f t - j u s t i fi e d
access
▶characters
with either
permanent
file name
blank or
binary zero
. fi l l .
oq
value
qd
0 Integer specifying printer
id.
If
negative,
use
default value (refer to
following note).
1
| NOTE |
If either oq or qd is negative, the
default value will be used for both,
regardless of the option selected for
the other.
User
name
v A valid name
1 specified in
1 display-coded,
1 l e f t - j u s t i fi e d
Direct
[characters with
access
1 either blank or
permanent 1 binary zero
file name >' fi l l .
| NOTE |
FORTRAN
CALL DSDUMP(fwa,lwa,ep,db ,oq,qd)
f w a O c t a l i n t e g e r t h a t s p e c i fi e s t h e b e
ginning address of task memory to be
dumped; legal values are zero v
A transaction is declared to be recoverable when it
i s a d d e d t o t h e a p p l i c a t i o n t a s k l i b r a r y. T h e d a t a
managers (CRM and CDCS) provide methods of declaring
d a t a fi l e s r e c o v e r a b l e . U p o n i n i t i a t i o n o f a r e c o v
erable transaction, ITASK schedules the transaction
via a CALLTRN request. Then the original input (that
is, the transaction name and all unsolicited data) is
logged to the communication recovery file before the
transaction begins execution. The transaction must
indicate to the data manager that it wishes to open
a begin-commit sequence by making a data base BEGIN
request. When the transaction requests to update a
data file, the following occurs.
• The record as read from the data file (the rec
ord In this state is called the before image)
is logged to a before image recovery file, also
known as the before image log file.
• The record is processed by the transaction.
• The updated record (called the after image) is
logged to an after image recovery file when the
program makes a write, rewrite, or delete re
quest. The updated record is also written to
the data file at this time.
After an update or a series of updates, the transac
tion Indicates to the data manager that it wishes to
close the begin-commit sequence by making a data base
COMMIT request. If the transaction does not intend
to open another begin-commit sequence, it indicates
to TAF that its work is done by issuing a SECURE re
quest just prior to the COMMIT request. TAF logs a
message associated with the SECURE request to the CRF
and sends this message to the terminal when the final
transaction CEASE request is processed.
If a failure occurs prior to the BEGIN request, the
data base is unaffected and the transaction is re
started upon recovery using the original data logged
on the CRF.
If a failure occurs between the BEGIN and COMMIT
requests, the data manager rolls back the data base
by applying the before images from the before image
recovery file (BRF) to the affected data files. The
data base is then in the same state as it was at the
beginning of the begin-commit sequence. The trans
action is restarted upon recovery using the data on
the CRF.
60459500 A
If a failure occurs after the COMMIT request, the
data base is not rolled back, all updates become per
manent when the COMMIT is processed. Whether the
transaction is restarted depends upon the data mana
ger being used. CDCS transactions are restarted if a
f a i l u r e o c c u r s a n y t i m e p r i o r t o t h e fi n a l t r a n s a c
tion CEASE request. CRM transactions are rerun un
less both a COMMIT and SECURE request have been suc
cessfully issued. The applications tasks must be de
signed to handle cases where restart can occur after
a COMMIT has been successfully executed. Refer to
section 7 for some suggested transaction structures.
A B R F fi l e i s u s e d r e p e a t e d l y b y t h e a p p l i c a t i o n .
Only the before images for the current begin-commit
sequence need to be saved so each new begin-commit
sequence can overwrite the previous one.
A n a f t e r i m a g e r e c o v e r y fi l e ( A R F ) i s c o n t i n u o u s .
N e w a fte r i m a g e s a r e w r i tte n s e q u e n ti a l ly until the
fi l e i s f u l l . A t t h a t t i m e , l o g g i n g i s s w i t c h e d t o
a second ARF while the after images from the first
ARF are dumped to tape.
The ARF files are not used for automatic recovery.
They provide a backup in case a CRF, BRF, or data
file becomes damaged. If this happens, the data ad
ministrator can use batch recovery to reload the data
file(s) from the dump tape and apply, after images
from an ARF dump, thus restoring the data base to a
correct state as of any desired point in time.
The function performed by each of the recovery compo
nents are as follows.
• Tr a n s a c t i o n r e c o v e r y
- Logs the initial input to the CRF.
- Logs and sends the SECURE message.
- Restarts recoverable transactions after a
failure.
• Data base recovery
- Automatic component
. Rolls back updates in uncommitted
begin-commit sequences.
. Logs before images to the BRF.
• Logs after images to the ARF.
. Switches after image logging when an
ARF is full and submits a batch job to
dump the full ARF to tape.
- Batch component
. Dumps full ARFs to tape.
. Dumps data files to tape upon request.
8-1
• Restores data base files from data file
and ARF tapes.
TAF K DISPLAY
• Maintains a directory of dumped files.
INITIAL K DISPLAY
The nomenclature used here is specific to the TAF/CRM
Data Manager. CDCS automatic recovery uses similar
c o n c e p t s b u t d i f f e r e n t t e r m i n o l o g y. T h e d e t a i l s
associated with data base recovery are documented in
the respective data manager reference manuals. The
remainder of this section covers the details of
transaction recovery.
HARDWARE CONFIGURATION CONSIDERATIONS
Recovery cannot succeed if failures affect more than
one component of the recovery system. For example,
if a single hardware failure destroys both the recov
e r y fi l e s a n d t h e d a t a b a s e , t h e r e i s n o r e c o v e r y
other than to restore the data base from a backup
c o p y ( fi l e d u m p ) . F o r t h i s r e a s o n , t h e d a t a b a s e
fi l e s , t h e c o m m u n i c a t i o n r e c o v e r y fi l e s , t h e b e f o r e
image recovery files, and the after image recovery
fi l e s s h o u l d b e a s s i g n e d t o p h y s i c a l l y s e p a r a t e
d e v i c e s . A l s o , t h e b a c k u p d i r e c t o r y fi l e f o r b a t c h
recovery should not reside on the same device as the
ARFs.
Three K display commands are available to perform
recovery-related functions: K.INT, K.ERO, and K.REC.
K.INT Command
The K.INT command specifies which recovery file(s)
are to be initialized. This is the only means of
initalizing a CRF. Files listed on a RECOVER state
ment in the TCF and on this command will be initial
ized. Files listed on a RECOVER statement but not on
this command will be used for recovery. The INT com
mand also specifies whether CRM data base recovery
files (ARFs and BRFs) are to be initialized or recov
ered. When used for CRM recovery files, this command
is valid regardless of TAF installation options.
The format is:
K . I N T- t y p e , fi l e i d
type File type. The options are:
CRF
Command relates to the
communication recovery
fi l e . T h i s o p t i o n v a l i d
only
if
installation
parameter IPTAR » 1.
CRM
Command relates
r e c o v e r y fi l e s .
The dump tape storage area should be physically
separate from the area housing the disk drives.
Automatic recovery also depends on the integrity of
single input/output operations. An on-line motorgenerator is essential to ensure that disk operations
underway at the time of a power failure have time to
complete correctly.
fi l e i d
to CRM
F i l e i d e n t i fi e r. T h e o p t i o n s a r e :
digits
0-7
.Each digit in the string
s p e c i fi e s a C R F t o b e
initialized. The digit
corresponds to the id
parameter on the RECOVER
s t a t e m e n t i n t h e T C F.
This option is not valid
if type is CRM.
ALL
Transaction recovery is enabled or disabled by the
i n s t a l l a t i o n p a r a m e t e r I P TA R . I f I P TA R i s s e t t o
one, transaction recovery is enabled; if IPTAR is set
to zero, transaction recovery is disabled.
If typ e i s C R F, all CRFs
listed In TCF RECOVER
statements are to be
initialized. If type is
CRM, all CRM after image
r e c o v e r y fi l e s a r e t o b e
initialized.
If recovery is disabled, these requests will not be
honored in recovery mode:
NOTE
Performance improvements through the use of multiple
CRFs and BRFs (TAF/CRM only) will be realized only if
each additional file resides on a separate device.
INSTALLATION
A procedure file for TAF initialization and recovery
is presented in the NOS 2 Installation Handbook.
CALLTRN
RERUN
RGET
RPUT
RSECURE
SECURE
TINVOKE
TSTAT
WSTAT
For logging of input on CRF.
Except for keywords USER and NEXT.
Except for keywords STEP (=8 or =9)
and USER.
A number of other installation parameters have an
effect on recovery. Refer to the NOS 2 Installation
Handbook for details.
8-2
This option must be used with caution
as the CRM data base update history
currently residing on the recovery
fi l e s w i l l b e l o s t .
NONE If type is CRF, no CRF is
to be initialized (all
CRFs listed in TCF RECOVER
sta te me n ts a re to be re
covered) . If type is CRM,
no CRM recovery files will
be initialized. NONE is
the default for both
values of type.
60459500 C
X^&SK
K.ERO Command
The K.ERO command specifies whether to override
certain I/O or logical errors encountered during
p r o c e s s i n g o f t h e c o m m u n i c a t i o n r e c o v e r y fi l e ( s ) .
The format is:
K. ERO»CRF ,o ption
option
Error override option.
NO or YES.
Must be
NO Abort if I/O or logical er
rors are encountered when
processing the communication
r e c o v e r y fi l e ( s ) . T h i s i s
the default.
If DISPLAY,ON is selected in the TCF, the K display
is issued. This display is identical to the initial
K display except that if any values were changed at
initialization, the changed values are retained on
t h e r e s t a r t e d K d i s p l a y. T h i s d o e s n o t a p p l y t o
K.INT and K.ERO commands. Changed values for these
commands are not retained after TAFREC completes.
(This prevents inadvertent initialization of
r e c o v e r y fi l e s i n a r e c o v e r y s i t u a t i o n ) .
TCF/CRF RECOVERY CONSIDERATIONS
TAF CONFIGURATION FILE
The TCF contains several recovery-related items.
YES I/O or logical errors en
countered on a run unit
header record will result in
the loss of that run unit
with no indication to the
t e r m i n a l u s e r. T h e l o s s
will be noted on the recov
ery report.
I/O or logical errors en
countered on a message rec
ord within a run unit will
result in a loss of that run
unit. However, a status in
dicator would be set in the
run unit header that would
enable the terminal user to
be informed.
I/O or logical errors en
countered on the CRF header
record will result in uncon
ditional abort of TAF.
K.REC Command
The K.REC command sets the user recovery bit in the
terminal status table. The format is:
• The RECOVER statement indicates the CRF
i d e n t i fi e r ( z e r o t o s e v e n ) a n d t h e s i z e a n d
number of messages that can be written to
the CRF.
• Default K display values can be changed by
placing K display commands in the TCF.
• The DISPLAY statement provides the option of
having the K display brought up at
initialization and recovery to allow the
operator to override any of the default
values.
Details on these statements are given with the TCF
description in section 4.
The use of multiple CRFs is indicated by multiple
R E C O V E R s t a t e m e n t s i n t h e T C F. E a c h R E C O V E R
statement corresponds to a separate CRF. For each
RECOVER statement there must be a corresponding
NETWORK statement. Refer to Use of Multiple
Communication Recovery Files in this section and
Communication Recovery File in section 4.
COMMUNICATION RECOVERY FILE
K.REC-nnn
nnn Recovery option. Must be YES or
NO.
YES Set the user recovery bit in
the terminal status table.
NO Do not change the present
setting of the user recovery
bit.
J 8 ^
Error Override
Certain errors on the CRF file(s) can be overridden
by using the K.ERO K display command (refer to
Initial K Display in this section). Input/output
errors on the CRF encountered during the running of
t r a n s a c t i o n s c a u s e TA F t o a b o r t a n d TA F R E C t o
attempt recovery of all readable data from the CRF.
RESTART K DISPLAY
File Reformatting
The K display that TAF formats at initialization will
be displayed only if a DISPLAY statement with the ON
parameter selected appears in the TCF. Refer to sec
tion 4 for details on the DISPLAY statement. If the
K display is brought up, the operator makes any
desired changes and types K.GO or K.END to resume
processing. K.STOP will abort TAFREC.
TAF recovery processing reformats the CRF under the
following circumstances.
On a level 3 deadstart, or if TAF aborts, the TAF
p r o c e d u r e fi l e a u t o m a t i c a l l y r e s t a r t s TA F b y t r a n s
ferring control to TAFREC. TAFREC recovers the low
CM pointers and variables that were defined at TAF
i n i t i a l i z a t i o n v i a t h e i n i t i a l K d i s p l a y.
60459500 C
• If the number of user messages per recovery
unit is increased in the number parameter on
the RECOVER statement.
• If the size of user messages per recovery
unit is increased in the maximumsize
parameter on the RECOVER statement.
• If a new user is added to or deleted from
the corresponding network file.
8-3
The RECOVER statement cannot be used to reduce the
number or size of the user messages. The only way
to reduce either of these is to reinitialize the CRF
using the K.INT command.
To reformat ZZCRFi, TAF creates a permanent file
named ZZCRFAi and writes the reformatted CRF to it.
When the reformat is complete, the old CRF (ZZCRFi)
i s p u r g e d a n d t h e n e w C R F ( Z Z C R FA i ) h a s i t s
permanent file name changed to ZZCRFi.
• S e t s t h e K d i s p l a y v a l u e s t o t h o s e i n e ff e c t
prior to failure.
• Identifies the users that were active at the
time of failure. Active users will have the
recovery flag (word 1, bits 0 and 53) set in
the terminal status table (TST).
• Reformats the CRF if necessary (refer to
File Reformatting under Communication
Recovery File in this sec tion).
Multiple Communication Recovery Files
• Prepares the TAF automatic recovery report.
Up to eight CRFs may be active simultaneously. Each
CRF must have a unique identifier. Once a CRF has
been initialized with a given id, it must be brought
up with the same id. If this is not done, recovery
will fail. Advantages of using multiple CRFs are:
• Initializes the transaction sequence number
count.
• The input/output associated with the CRFs is
spread out across several disks. This
improves performance.
• Mul timainf rame recovery becomes possible.
Refer to Mul timainf rame Recovery in this
sec tion.
MULTIMAINFRAME RECOVERY
The guidelines in this subsection pertain to sites
running TAF on several mainframes. These guidelines
are applicable if the ability to recover transaction
processing for a downed mainframe on an alternate
mainframe is desired.
• Make certain that the network (NCTFi) and
C R F ( C R F i ) fi l e i d e n t i fi e r s ( i ) o n e a c h
mainframe are unique among all mainframes.
• Allocate unique data base names to all
applications across all mainframes.
• Allocate recovery-related files to shared
mass storage.
• Define unique terminal user names across all
mainframes.
• When a mainframe goes down, IDLE TAF on the
mainframe that is to run the downed
applications, t
• R e s t a r t TA F w i t h a T C F f i l e t h a t c o n t a i n s
RECOVER statements for the recovery ids of
both mainframes*
• When
TAF
TAF
with
the
on
up
the
downed mainframe is repaired, IDLE
the recovery mainframe. Then bring
independently on the two mainframes
original TCFs.
RECOVERY PROCESSING FLOW
TAF AND SYSTEM FAILURE
Following a TAF or operating system failure, the TAF
i n i t i a l i z a t i o n p r o c e d u r e b r i n g s TA F u p i n r e c o v e r y
mode. During recovery mode initialization, TAFREC
and TAF perform the following functions:
• S c h e d u l e s C TA S K t o m o v e b e g i n - c o m m i t i d s
from BRF to CRF.
BTASK is scheduled to determine which users active
at the time of failure were running recoverable
BTRAN-initiated transactions. BTASK calls CTASK to
recover these transactions.
Recovery for transactions being run from interactive
terminals is postponed until the terminal logs in.
When a terminal logs in, TAF checks the recovery
fl a g ( w o r d 1 , b i t 5 3 ) i n t h e t e r m i n a l s t a t u s t a b l e .
I f t h e r e c o v e r y fl a g i s s e t , R TA S K i s s c h e d u l e d
instead of ITASK. RTASK performs these functions:
• I f t h e r u n u n i t i s n o t r e c o v e r a b l e , R TA S K
sends READY to the terminal and ceases.
• If a recoverable transaction is no longer
rerunnable, RTASK sends a message telling
the terminal operator
1. that recovery has occurred,
2. that the recoverable transaction
will not be rerun automatically, and
3. to enter the next input.
This situation occurs when an input/output
error occurred on the communication recovery
fi l e . T e r m i n a l o p e r a t o r s s h o u l d b e
instructed to inform the data administrator
if this occurs since batch recovery will be
necessary to restore the data base.
• If the transaction SECURE request and a
TA F / C R M C O M M I T r e q u e s t h a v e b e e n
s u c c e s s f u l l y e x e c u t e d , R TA S K s e n d s t h e
terminal confirmation message, and ceases.
The terminal confirmation message was stored
on the CRF as a result of the transaction
SECURE request.
• I f n o n e o f t h e p r e c e d i n g i s t r u e , R TA S K
calls CTASK.
CTASK requests a new transaction sequence number and
returns the begin-commit history to TAF/CRM. CTASK
then makes a RERUN request. The RERUN request turns
off the recovery status, retrieves terminal input
from the CRF, and schedules ITASK using the new
sequence number and original terminal input. ITASK
processes the input as if it had come from the
terminal.
tlf CDCS has been running on both mainframes and interfacing with TAF, CDCS must be dropped on the functional
mainframe or recovery of CDCS data bases will not be possible.
8-4
60459500 C
/ * I D Tr a n s a c t i o n t e r m i n a l t y p e .
DB=aa
Two-character name of the data base
t o b e a c c e s s e d b y ' t h e u s e r. O n l y
one data base can be associated with
a user name.
UA=n
Contents of the user argument area in
the communication block. n ranges
from 0 through 16777215. Default is
zero. User area contents can be ex
amined and changed by tasks. The
appropriate initial value is site
dependent. Bit 0 is the default
task recovery bit.
60459500 C
A s i m p l e s e t o f t e r m i n a l n e t w o r k fi l e d i r e c t i v e s
follows:
//DIAL.
/AJ0HNSN,TT=*ID,DB=8C,
UA=16117711B.
/BJOHNSN,TT=*ID,DB=BC,
UA=00007700B.
/XYZ1,TT=*ID,DB=8C.
NETWORK FILE ORIGINATION
When an error-free network description is ready, an
a n a l y s t s h o u l d c r e a t e a s y s t e m fi l e c a l l e d N C T F i
( w h e r e i i s t h e n e t w o r k fi l e i d e n t i fi e r ) f r o m t h e
t e r m i n a l n e t w o r k d e s c r i p t i o n fi l e .
A t y p i c a l w a y t o o r i g i n a t e a n N C T F i fi l e f o l l o w s .
First, the user establishes a set of network
description statements as a local file.
NCTF.
USER,username,password,familynaae.
' CHARGE,chargenuraber,projectnumber. or (*)
COPYBR,INPUT,NET.
SAVE,NET .
end-of-record
Network description statements
e n d - o f - fi l e
Then the user enters the following at the system
console.
X.DIS.
USER,username,password,familyname.
CHARGE,chargenumber,projectnumber.
GET,NET.
SUI,377777.
DEFINE,NCTFi/CT=PU.
COPY,NET,NCTFi,V.
RETURN,NCTFi,NET.
This creates a direct access public file called NCTFi
under the system user index 377777. NCTFi is used to
generate terminal status table entries.
Figure 9-1 illustrates a terminal status table entry.
Each line gives the user name and its associated data
base, read and update securities, and user area
value.
When a run unit originates from a terminal, the
transaction executive uses the appropriate entry in
the terminal status table to construct words 0 and 1
of the communication block.
After the network file is originated, it must be up
dated to reflect changes, and the transaction execu
tive must be reinitialized to recognize the new in
formation.
9-1
TERMINAL STATUS TABLE ENTRY
59
communication line field
A
55 53
42
ACN
24
38
reserved
17
database
user argument field
/
/
/
database
WordO
11
NT
IF
sequence number
*g'
Wordl
message count
Word 2
Word 68■
t
COMMUNICATION BLOCK
(refer to section 2 for more information)
Word 1
id
Function
A
User active.
L
Terminal logged in.
D
Terminal down.
C
Connection requested from network or terminal off.
R
Recovery required.
N
Recoverable transaction run.
ACN
Application connection number.
^r^t^v
Word 2
id
Function
M
Multiple block input being sent.
I
Input wanted.
F
Last message block sent.
P
Connection to be postponed.
C
CDCS abort.
NT
Number of transactions received from terminal.
/*S§\
Figure 9-1. Communication Between a Terminal Status Table and a Communication Block
9-2
60459500 C
TASK LIBRARY
A task library contains all of the named-transactions
and tasks that may be requested by a user group with
in the transaction subsystem. The task library is
created by the LIBTASK utility.
A t a s k l i b r a r y fi l e i s a d i r e c t a c c e s s p e r m a n e n t
file with no password that must be created with a
DEFINE command before a library creation run
occurs. However, it does not have to be attached by
the user unless the DA option is specified (refer to
L I B TA S K c o m m a n d ) . T h e t r a n s a c t i o n s u b s y s t e m
simultaneously supports one system task library and,
optionally, one task library for each data base.
The system task library, called TASKLIB by default,
may be renamed at the site's option. It is defined
under the transaction subsystem user name and given
write permission to that user name. The name
TASKLIB may also be changed using the K display
command K.TLF. (Refer to the NOS 2 Operator/Analyst
Handbook.)
A user task library must be named xxTASKL where xx
is the name of the data base with which the library
i s a s s o c i a t e d . I t m u s t b e d e fi n e d u n d e r t h e d a t a
base user name, and explicit write permission must
be granted to the transaction subsystem user name to
access the file.
D u r i n g i n i t i a l i z a t i o n , TA F a t t e m p t s t o a t t a c h a
library for each initialized data base. The xxJ
file is accessed to determine the user name needed
to attach the library. When a scheduling request is
received, the transaction subsystem searches for the
n a m e d - t r a n s a c t i o n o r t a s k fi r s t i n t h e a s s o c i a t e d
d a t a b a s e l i b r a r y, i f o n e e x i s t s , a n d t h e n i n t h e
s y s t e m l i b r a r y. T r a n s a c t i o n ' a n d t a s k n a m e s ,
therefore, need be unique only within a given task
l i b r a r y. T h e o n l y e x c e p t i o n t o t h i s p r o c e d u r e i s
the initial task, ITASK, which is always loaded from
the system library.
LIBTASK UTILITY
The LIBTASK utility creates a new library, adds new
named-transactions and tasks to an existing library,
deletes named-transactions and tasks from an
e x i s t i n g l i b r a r y, r e p l a c e s t a s k s i n a n e x i s t i n g
l i b r a r y, a n d c o m p a c t s a n e x i s t i n g l i b r a r y b y
removing inactive records. Named-transactions and
tasks may be added or deleted while the transaction
subsystem is running, because tasks are added as a
n e w fi l e a t t h e e n d o f t h e l i b r a r y. T h e l i b r a r y i s
a m u l t i fi l e fi l e . T h e t r a n s a c t i o n e x e c u t i v e
attempts to read a new library directory if the
LIBTASK command contains the TT option. Thus, on
line update of any task library is allowed.
60459500 C
10
I f t h e l i b r a r y i s m o d i fi e d w h i l e t h e t r a n s a c t i o n
subsystem is running and the user wants the new
directory used, the user number and password of the
L I B TA S K u s e r a r e p a s s e d t o t h e t r a n s a c t i o n
subsystem for validation. This is done by
intercontrol point communication, which is also used
to check if the transaction subsystem is running if
the CR or PR option is selected. Therefore, the
first USER command in the job must have permission
to do intercontrol point communication. (Refer to
the NOS 2 System Maintenance Reference Manual for
t h e u s e o f M O D VA L t o a l t e r p e r m i s s i o n s . ) T h e
LIBTASK run Issues an error message and does not
update the library if the validation fails. The
task binaries to be added or replaced are in ABS or
OVL format produced by the CYBER Loader.
TASK RESIDENCY AND TYPE
An important option of LIBTASK enables the user to
specify the residency and type of tasks on the task
l i b r a r y. A t a s k c a n r e s i d e o n c e n t r a l m e m o r y,
e x t e n d e d m e m o r y, o r m a s s s t o r a g e . T h i s c a n b e
s p e c i fi e d w i t h t h e C a n d E o p t i o n s o n L I B TA S K
directives.
A task can be of either reusable or nonreusable
type. A reusable task must be written so that it is
reinitializing. A reinitializing task (program)
does not modify program areas that the program
considers constant; if it does, it resets
( r e i n i t i a l i z e s ) t h e s e a r e a s u p o n r e e n t r y. M u l t i p l e
requests for a reusable task can be queued together;
this is partly under the control of the person who
sets up the task library and partly under the
control of the transaction executive. The queuing
of multiple requests occurs in an internal list, the
requested task list (RTL). Each entry in this list
represents a scheduling request for a copy of a
task. There may be multiple entries in the RTL list
f o r a g i v e n t a s k . T h e L I B TA S K q u e u e l i m i t i n p u t
directive can be used to specify the maximum number
of transactions that can be queued against one
e n t r y. W h e n t h e t r a n s a c t i o n e x e c u t i v e s c h e d u l e s a
copy of a task from the RTL list, it picks an RTL
entry and forces all of the multiple requests queued
for that RTL entry to use the same copy of the task.
It is generally possible to have multiple copies of
a given task in execution at the same time (note
that this does not apply to CM-resident tasks).
Additional application control of task scheduling is
p r o v i d e d b y t h e Q L I B TA S K o p t i o n i n t h e i n p u t
directives.
A nonreusable task is not a reinitializing task; a
new copy of the task must be loaded from the task
library for each transaction.
10-1
The task type can be specified with the D option on
L I B TA S K d i r e c t i v e s . T h e q u e u e l i m i t c a n b e
specified with the QL option.
I f a t a s k i s s p e c i fi e d a s c e n t r a l m e m o r y - r e s i d e n t
and reusable, it is loaded to a subcontrol point
when TAF is initialized and, unless the task aborts,
remains at that subcontrol point to service
transactions as long as TAF is running. If the task
aborts, another copy of it will be loaded. It is a
single copy task. No additional copies of this task
are loaded to process requests after queue limit has
been reached.
LIBTASK COMMAND
T h e L I B TA S K c o m m a n d h a s t w o f o r m a t s . T h e fi r s t
f o r m a t a l l o w s s p e c i fi c a t i o n o f t h e fi l e c o n t a i n i n g
input directive statements; this format is:
LIBTASK(Pl,P2,...,Pn>
T h e s e c o n d f o r m a t s p e c i fi e s t h a t i n p u t d i r e c t i v e
statements are included in this LIBTASK command.
This format is:
L I B TA S K t P i . p j , . . . , Z , . . . , P n ) ; d x ; d 2 ; . . . ; d n .
Parameter
Description
F i l e i s s p e c i fi e d b y
you.
1-0
No directive
exists.
fi l e
O m i t t e d D e f a u l t fi l e i s I N P U T.
S p e c i fi e s t h e fi l e c o n t a i n i n g t a s k
binaries to be added to the library.
These may be tasks already existing
in the library or they may be new
o n e s . T h e fi l e i s r e w o u n d b e f o r e
processing. Options are:
B
File is LGO.
B-lfn
F i l e i s s p e c i fi e d b y
you.
B-0
N o b i n a r y fi l e e x i s t s .
Omitted
Default file is LGOB.
Specifies the file on which output is
written. Options are:
L
; Unique delimiter that does not occur
in any d^ input directives. This
delimiter does not have to be a
semicolon.
/Sa^V
I=lfn
File
L-lfn
is
O U T P U T.
File is
you.
s p e c i fi e d
by
L«0 No output is written.
dj Input directive statement (refer to
Input Directives in this sec tion).
The input directives on a LIBTASK command remain in
effect for a task in an existing task library until
t h e t a s k i s s p e c i fi e d i n a s u b s e q u e n t L I B TA S K
command; that is, the most recent input directives
(including default input directives) for a task take
p r e c e d e n c e o v e r e a r l i e r i n p u t d i r e c t i v e s . H o w e v e r,
this is not true for a task that is not in a task
l i b r a r y ; i n t h i s c a s e , t h e fi r s t i n p u t d i r e c t i v e s
(including default input directives) take precedence.
For example, you specify the following command:
LIBTASK(p1,p2,P3,...,pn);*T1 DL.
This command logically deletes task Tl. If you
specify task Tl in a subsequent LIBTASK command and
do not specify DL, the task is activated (by
default).
The LIBTASK com and cannot exceed 80 characters.
The parameters (pf) for either format can be in
any order and are:
Parame
ter
Description
I S p e c i fi e s t h e fi l e c o n t a i n i n g i n p u t
d i r e c t i v e s . T h e fi l e i s n o t r e w o u n d
before processing. All directives
that do not refer to a task name
present on the B file or P file are
ignored. Options are:
I
10-2
File
is
COMPILE.
Omitted Default file is OUTPUT.
Specifies the name of a direct access
p e r m a n e n t fi l e t o b e u s e d a s t h e
l i b r a r y fi l e . T h e fi l e i s r e q u i r e d .
Options are:
P
File is TASKLIB.
P-lfn
F i l e i s s p e c i fi e d b y
you.
P-0
N o o l d l i b r a r y fi l e
exists.
Omitted
Default
TASKLIB.
fi l e
is
J^'^Wt^\
Specifies a newly defined direct ac
cess permanent file to be written as
t h e n e w l i b r a r y fi l e . U s e o f t h i s
option eliminates the complete copy
o f t h e P fi l e t o a s c r a t c h fi l e o n
t h e P R o p t i o n , t h u s s i g n i fi c a n t l y
reducing the purge time for long
l i b r a r i e s . T h e P fi l e i s n o t p u r g e d .
Options are:
N
File
is
TA S K L I B .
N»lfn File is specified by
you.
O m i t t e d D e f a u l t fi l e i s t h e
fi l e s p e c i fi e d b y P.
60459500 B
/^S\
J ^
Parameter
L
O
Parameter
Des c r ipt ion
Produces a report of tasks and their
attributes, named-transactions with
attributes, and names of member
tasks. It is not necessary to
specify the TT option when using LO
if I»0 and B=0. Figure 10-1 shows
the format of the report. The
options are:
LO
Same
as
PR
LO»A.
LO=A Report all tasks and
transae tions.
Report only
actions.
omitted
TN
No
report
produced.
trans
i s
S p e c i fi e s t h e n a m e o f a t a s k o r
transaction. This parameter is
valid only when the LO parameter is
also specified. If LO-T, TN names a
task; if LO=X, TN names a
transaction. The options are:
TN*tname The task or trans
action (tname) is
the only one re
ported on.
omitted
DA
CR
Removes inactive task binaries and
old directories from the task
l i b r a r y. L I B TA S K p r o c e s s e s t h e B
fi l e a n d t h e i n p u t d i r e c t i v e s n o r m
a l l y a n d , i f N i s n o t s p e c i fi e d ,
copies the entire library to a
s c r a t c h fi l e . T h e c u r r e n t b i n a r y
for each task in the library is then
t r a n s f e r r e d f r o m t h e s c r a t c h fi l e t o
t h e l i b r a r y fi l e , a n d t h e d i r e c t o r y
is updated and written at the end.
Therefore, only one copy of each
task and one directory remain in the
l i b r a r y . I f N i s s p e c i fi e d , n o
s c r a t c h fi l e i s w r i t t e n , a n d P i s
n o t p u r g e d . T h e n e w l i b r a r y fi l e
contains only the latest copy of
each active task and one directory.
LO«T Report only tasks.
LO=X
Description
All tasks or all
transactions are re
ported on.
Disables all attaches and returns of
t h e l i b r a r y fi l e s i n t h e L I B T A S K
program. With this option selected,
t h e N fi l e a n d t h e fi l e s p e c i fi e d b y
P must be attached prior to the
L I B TA S K c a l l . I f a l i b r a r y i s
attached in the proper mode from
another user name, the DA option
m u s t b e s e l e c t e d s o t h a t L I B TA S K
does not try to attach the
appropriate libraries under the user
name from which the update is being
run.
Creates a new task library. LIBTASK
reads one task at a time from the B
fi l e , c h e c k s f o r a n i n p u t d i r e c t i v e
for the task, constructs a directory
e n t r y, a n d i n s e r t s t h e e n t r y i n
alphabetical order in the library
d i r e c t o r y. T h e d i r e c t o r y i s w r i t t e n
a t t h e e n d o f t h e l i b r a r y. T h i s
option applies only if LIBTASK was
able to attach the task library
(specified by the N option) in write
mode.
This option applies only if LIBTASK
was able to attach the task library
(specified by the N option) in write
mode.
TT
Instructs the transaction executive
t o u p d a t e t h e TA F - r e s i d e n t c o p y o f
t h e t a s k l i b r a r y d i r e c t o r y while TAF
i s r u n n i n g . I f n o t s p e c i fi e d , T A F
will not become aware of the update
until
the
next
time
it
is
initialized.
The installation parameters TLDMN and
TREMN are used to specify the amount
of space to be reserved for adding
tasks and transactions for each of
t h e TA F - r e s i d e n t t a s k l i b r a r y d i r e c
tories. The default allows 10 addi
tions for each. Although further
additions can be made to your task
l i b r a r y, t h e y w i l l n o t b e r e c o g n i z e d
b y TA F u n t i l TA F i s r e i n i t i a l i z e d .
There is no limit to the number of
times existing tasks can be replaced.
The user name from which LIBTASK is
being run must be the same as the
user number in the xxJ file associ
ated with the library being modified,
and TAF must be able to attach the
library in write mode in order for
the update of TAF's copy of the TLD
to take place. You must be validated
fo r i n te rco n tro l p o i n t co mmunication
(the CSTP bit in user's access word
must be set) to use the TT option.
Each time you use the TT parameter
with the LIBTASK command, a file is
added to your task library.
S p e c i fi e s t h a t i n p u t d i r e c t i v e s a r e
on the LIBTASK command. This option
overrides the I option.
/$PV
60459500 B
10-3
Part 1. Task listing. Generated if LO-A or LO-T.
TASK
NAME
PRIORITY
BEG MAX
FIELD
LENGTH
EXTRA
QL
FL
ATTR
DCEORQ
taski
taskg
bp mp
bp mp
ql
ql
fl
fl
e fl
e fl
attrib
attrib
taskn
bp mp
ql
fl
e fl
attrib
t a s k i Ta s k n a m e .
b p B e g i n n i n g p r i o r i t y.
m p M a x i m u m p r i o r i t y.
ql
Queue
limit.
fl F i e l d l e n g t h r e q u i r e d b y t h e t a s k .
e fl E x t r a fi e l d l e n g t h t h e t a s k m a y r e q u e s t .
a t t r i b Ta s k a t t r i b u t e l i s t . T h e a t t r i b u t e i s i n e f f e c t i f t h e l e t t e r a p p e a r s .
D Destructive code.
C Central memory-resident.
E Extended memory-resident.
Refer to Task Input Directives,
later in this section, for infor
mation about these attributes.
0 Task is OFF.
R Solicited communication block.
Q Queueing enforced.
Part 2. Transaction listing. Generated if LO-A or LO-X.
TRANSACTION
UNIT
1ST
TASKS
2ND
3RD
4TH
5TH
D.M.
CD
tnamei
tnamej
taski
taski
task2
taskg
task3
task3
task/;
task/;
tasks
tasks
datamanager
datamanager
re
re
tname3
taski
task2
task3
task/;
tasks
datamanager
re
RECOVER
/^8^S\
tnamei Transaction name.
taski
Task names. If any task does not exist in this library, its name is enclosed in
parentheses.
datamanager
The data managers used by the named-transaction. May be either or both:
C Transaction uses CRM.
D Transaction uses CDCS.
Use of the indicated data manager is allowed if the letter appears.
Recovery indicator. For recoverable transactions, RC appears in this position.
Figure 10-1. Task Library Report
10-4
60459500 A
Adding or deleting tasks within a named-transaction
or altering other attributes is accomplished by
respecifying the directive in full.
INPUT DIRECTIVES
NAMED-TRANSACTION INPUT DIRECTIVE
The named-transaction input directive is used to
create and delete named-transactions.
The format is:
/ tname, Tl=« task 1, T2- task2, T3- task3, T4- task4,
T5-task5,RC,DM»datamanager,DL.
tname Transaction name. Must be one
to seven alphanumeric characters.
taski Name of the task(s) in the namedtransaction, tname. The tasks
will be executed in the order
listed. If a task issues a
CALLTSK with CEASE, the remaining
tasks in the original transaction
will not be executed.
RC
J0^*\
Recovery indicator. When this
p a r a m e t e r i s s p e c i fi e d , t h i s
transaction is recoverable. If
n o t s p e c i fi e d , t h i s t r a n s a c t i o n
is not recoverable.
datamanager The data manager(s) that may be
used by this named-transaction.
If a recoverable transaction
attempts to use CDCS or CRM and
its usage was not declared via
this parameter, the run unit will
be aborted. This parameter is
valid only if the RC parameter is
also specified. The options are:
C The transaction uses CRM.
D The transaction uses
CDCS.
DL Causes
the deletion of transac
tion tname from the task library.
If specified, this parameter must
be the only parameter in addition
to the tname parameter on the
d irec tive.
Additional tasks can be made part of the execution
of a named-trans action if they are initiated via a
CALLRTN or CALLTSK with CEASE. A CALLTSK with
CEASE, however, will prevent any remaining tasks in
the original transaction from being executed.
A task may be part of more than one namedtransaction.
Declaring the named-transaction recoverable is
n e c e s s a r y b u t n o t s u f fi c i e n t t o e n s u r e c o r r e c t
recovery from failures. The transaction must also
be constructed to support recovery as specified in
section 7 of this manual.
Ta s k s s p e c i fi e d i n t h i s d i r e c t i v e d o n o t h a v e t o
e x i s t i n t h e d a t a b a s e t a s k l i b r a r y. T h i s a l l o w s
system tasks to be included in the named-transaction
d e fi n i t i o n . N a m e d - t r a n s a c t i o n s w i t h t a s k s t h a t d o
not exist in the data base task library are enclosed
by parentheses in the report generated by using the
LIBTASK LO parameter.
60459500 A
TASK INPUT DIRECTIVE
To a l t e r t a s k c h a r a c t e r i s t i c s , d i r e c t i v e s t a t e m e n t s
m a y b e e n t e r e d i n t h e d i r e c t i v e fi l e . O n l y o n e
statement should appear for each task. These
characteristics are kept in the directory for use by
the transaction executive when the task is to be
executed.
The directive statement format is:
*name Pi,P2 Pn«
name is the task name and p^ is any of the
following input directives in any order.
Directive
Description
BP-nn Beginning scheduling priority of
task.
BP Beginning priority defaults to 25g.
BP omitted Beginning priority defaults to 20g.
C
S p e c i fi e s a m e m o r y - r e s i d e n t t a s k .
The default is a disk-resident task.
D
S p e c i fi e s a d e s t r u c t i v e c o d e ( n o n reusable) task that is removed from
the subcontrol point when the task
is completed. The default is a
reusable task. This option is
recommended when debugging a task.
DL
S p e c i fi e s t h a t a t a s k ( n a m e ) i s
logically deleted. All logically
deleted tasks are physically deleted
from the task library when the
L I B TA S K c o m m a n d c o n t a i n s t h e P R
option.
S p e c i fi e s a n e x t e n d e d m e m o r y resident library copy of the task.
The default is mass storage-resident.
I f t a s k s a r e s p e c i fi e d a s e x t e n d e d
memory-resident, the transaction
e x e c u t i v e l o a d s a s m a n y a s w i l l fi t
into its available extended memory
during initialization and leaves the
remaining tasks on the mass storage
fi l e . I f n o e x t e n d e d m e m o r y i s
available, all tasks are loaded from
mass storage.
If a LIBTASK command specifying the
TT option is issued while the trans
action executive is running, no
tasks are replaced or added to
e x t e n d e d m e m o r y, a n d o n e o f t h e
following situations occurs.
• O l d c o p y o f t a s k i n extended
memory and new copy in
e x t e n d e d m e m o r y. T h e n e w
copy is ignored, and the old
copy remains on the library
in extended memory.
10-5
Directive
Des c r ipt ion
Directive
• Old copy not in extended
memory and new copy in
e x t e n d e d m e m o r y. T h e n e w
copy is used but is read
from mass storage.
An active task is a copy of a
task which is both:
• At a subcontrol point or
rolled out.
• Old copy in extended memory
and new copy not in extended
m e m o r y. T h e n e w c o p y i s
loaded from mass storage.
•
E F - e fl S p e c i fi e s t h e m a x i m u m a m o u n t b y
which a task will be allowed to
i n c r e a s e i t s i n i t i a l fi e l d l e n g t h ,
efl is assumed to be octal unless it
contains an 8 or 9 or is followed by
a trailing D. The default value is
zero. EF will be increased to the
next multiple of lOOg if it is not
already such a multiple. The maximum
fi e l d l e n g t h a l l o w e d f o r t h e t a s k i s
( i n i t i a l t a s k F L ) + e fl . T h e v a l u e
of efl can range from 0 to 300000g.
I G S p e c i fi e s t h a t a t a s k ( n a m e ) I n t h e
fi l e s p e c i fi e d w i t h t h e B o p t i o n i s
ignored.
MP»nn Maximum scheduling priority of task
(for future use in aging tasks).
MP Maximum priority defaults to 50g.
MP omitted Maximum priority defaults to 40g.
0 Sets task to OFF; requests for the
t a s k a r e r o u t e d t o t h e O F F TA S K
routine (refer to OFFTASK in section
11). The default is ON.
Q
S p e c i fi e s t h a t q u e u i n g i s t o b e
forced, described as follows. This
option alters the normal scheduling
priority of the task (refer to
Scheduling Priority) as follows:
1. When there are no active copies
o f t h e t a s k , t h e fi r s t c o p y o f
the task is scheduled as usual
(refer to Scheduling Priority).
2. While there are from one to six
active copies of the task in
TAF, another copy of the task is
not scheduled until the number
of transactions queued against
its RTL entries equals or
exceeds the queue limit
s p e c i fi e d b y t h e Q L d i r e c t i v e .
W h e n a n RT L e n t r y i s u s e d t o
schedule a task, it is released
and made available for
requesting the scheduling of
other tasks.
3. When the number of active copies
of the task equals seven,
additional copies of the task
will not be scheduled. This
applies even if the queue limit
is 1.
Description
In
the
process
of
handling a transaction
or has transactions
queued against it (the
copy).
If a LIBTASK function specifying the
TT parameter is issued while the
transaction executive is running and
an attempt is made to change the Q
attribute of a task on a library in
u s e b y TA F, t h e n t h e Q a t t r i b u t e
change will not affect TAF schedul
ing
until
the
executive
is
reinitialized.
This parameter is not applicable to
CM-resident tasks.
Q L - n S p e c i fi e s t h e n u m b e r o f r e q u e s t s , u p
t o a m a x i m u m o f fi v e , t h a t c a n b e
queued for an RTL entry for a task.
If a task uses a large amount of
m e m o r y a n d e x e c u t e s r a p i d l y, p e r
formance is not degraded if requests
are queued. In this case, multiple
copies of the task require too much
m e m o r y. I f a t a s k d o e s a l a r g e
a m o u n t o f I / O , t h e n p e r f o r m ance is
degraded if requests are queued. In
this case, multiple copies of the
task enhance performance.
Q L Q u e u e e n t r y l i m i t d e f a u l t s t o fi v e .
QL omitted Queue entry limit defaults to three.
R S p e c i fi e s t h a t t h e F L a s s i g n e d t o a
CM-resident task is to be reduced to
the Initial load value each time the
transaction is run. The default is
no reduce. Non-CM-resident tasks
are always started with their
initial load value.
SC Sets the task communication block
load status to solicited. This
means you must request the
communication block and supply a
valid address (using the BEGIN
request) after the task is initi
ated. The default is unsolicited.
All directives for one task must appear on the same
line. The following situation will result in only
Pj being recognized as an input directive for
TASKI.
*TASK1 pj.
*TASK1 p2.
Improper way to specify
input directives.
*TASK1 pn,
/<3SS|y
10-6
60459500 B
SCHEDULING PRIORITY
UPDATING AN EXISTING TASK LIBRARY
When the tasks are queued, the scheduler will attempt
t o l o a d t h e t a s k w i t h t h e h i g h e s t c u r r e n t p r i o r i t y.
If there are several tasks with the highest priority,
t h e t a s k w i t h t h e l o w e s t fi e l d l e n g t h r e q u i r e m e n t
will be selected for loading. When a task enters the
queue, the beginning priority (BP) is used as the
t a s k ' s c u r r e n t p r i o r i t y. T h e c u r r e n t p r i o r i t y i s
then aged (incremented by one) every second up to the
maximum priority (MP). Tasks in the queue having
i d e n t i c a l c u r r e n t p r i o r i t i e s a n d fi e l d l e n g t h r e
quirements normally will be scheduled in the order
they entered the queue.
The following examples show how you can update (add
new tasks and delete and replace existing tasks) an
existing task library without supplying any
binaries. An explanation is provided after each
LIBTASK command.
With these directives, classes of tasks can be
created. For e x a m p l e , i f t w o c l a s s e s w e r e c r e a t e d
(X and Y) their priorities could be:
XBP = 25g
YBP = 308
XMP = 408
YMP = *58
In this case, no tasks in X could be scheduled until
all tasks in Y having a current priority greater than
40s had been scheduled.
CREATING A NEW TASK LIBRARY
The following examples show how you can create a new
task library. An explanation is provided after each
LIBTASK command.
LIBTASK(P»0,N-lfn !,CR,B-lfn2,1)
L I B T A S K c o p i e s fi l e l f n 2 t o fi l e l f n j a c c o r d i n g
to input directives in the COMPILE file and adds a
new sorted task library directory at the end of file
lfnj.
LIBTASK(P-lfn2,N-lfh1,Z);*name
PliP2»»*»»Pn«
L I B TA S K c o p i e s fi l e l f n 2 t o fi l e l f n j a n d a d d s a
new sorted task library directory at the end of file
l f n i a c c o r d i n g t o i n p u t d i r e c t i v e s o n t h e L I B TA S K
command.
00$^**,
LIBTASK( P-lfn2,N-lfnj,PR,Z);*name
PlfP2»*'*»Pn«
LIBTASK copies all active (not logically deleted or
r e p l a c e d ) t a s k b i n a r i e s f r o m fi l e l f n 2 t o fi l e
lfn} and adds a new sorted task library directory
a t t h e e n d o f fi l e l f n j a c c o r d i n g t o i n p u t
directives on the LIBTASK command.
LIBTASK(P=lfn2,N=lfn1,B-lfn3,I)
L I B T A S K c o p i e s fi l e l f n 2 t o fi l e l f n j , c o p i e s
fi l e l f n 3 t o fi l e l f n j a c c o r d i n g t o i n p u t
d i r e c t i v e s i n t h e C O M P I L E fi l e , a n d a d d s a n e w
s o r t e d t a s k l i b r a r y d i r e c t o r y a t t h e e n d o f fi l e
lfnj.
L I B TA S K ( P - l f n 1 , Z ) ; * n a m e P i , p 2 P n •
LIBTASK adds a new sorted task library directory at
t h e e n d o f fi l e l f n ! a c c o r d i n g t o i n p u t d i r e c t i v e s
on the LIBTASK command.
LIBTASK(P=lfn1,PR,Z);*name Pi,p2»•••»Pn«
L I B TA S K c o p i e s a l l a c t i v e ( n o t l o g i c a l l y deleted or
r e p l a c e d ) t a s k s f r o m fi l e l f n j o n t o a s c r a t c h
fi l e , c o p i e s t h e s c r a t c h fi l e b a c k o n t o fi l e l f n j ,
and adds a new sorted task library directory to the
e n d o f fi l e l f n ! a c c o r d i n g t o t h e i n p u t d i r e c t i v e
on the LIBTASK command. This command is not valid
when TAF is up and has attached file lfn!.
LIBTASK(P«lfni,B-lfn2,Z);*name
Pl»P2»'»»»Pn»
L I B TA S K c o p i e s fi l e l f n 2 t o t h e e n d o f fi l e l f n t
a c c o r d i n g t o i n p u t d i r e c t i v e s o n t h e L I B TA S K
statement. LIBTASK adds a new sorted task library
d i r e c t o r y t o t h e e n d o f fi l e l f n ! .
L IBTASK(P« l fn !,B» l fn 2 ,PR ,I-l fn 3 )
L I B TA S K c o p i e s a l l a c t i v e ( n o t l o g i c a l l y deleted or
r e p l a c e d ) t a s k s f r o m fi l e l f n ! o n t o a s c r a t c h
fi l e , c o p i e s t h e s c r a t c h fi l e b a c k o n t o fi l e l f n ! ,
c o p i e s fi l e l f n 2 t o t h e e n d o f fi l e l f n j
a c c o r d i n g t o i n p u t d i r e c t i v e s o n fi l e l f n 3 , a n d
adds a new sorted task library directory to the end
o f fi l e l f n ! . T n i s c o m m a n d i s n o t v a l i d w h e n TA F
is up and has attached file lfn!.
DELETING A TASK FROM A TASK LIBRARY
With the DL input directive on the LIBTASK command,
you can logically . delete a task from the task
l i b r a r y i f TA F i s u p a n d h a s a t t a c h e d t h e t a s k
library as follows:
LIBTASK(P-lfn!,TT,Z);*name DL.
I n t h i s e x a m p l e , L I B TA S K l o g i c a l l y d e l e t e s a t a s k
(name) from file lfn!. Tne *T °Ption is required
when TAF is up. The DL input directive is the only
input directive allowed for the named task.
With the PR option on the LIBTASK command, you can
delete inactive tasks from the task library when TAF
is not up and when TAF is up but has not attached
t h e t a s k l i b r a r y.
LIBTASK(P=lfn2,N=lfni,B=lfn3,PR,I)
LIBTASK copies all active (not logically deleted or
r e p l a c e d ) t a s k b i n a r i e s f r o m fi l e l f n 2 t o fi l e
l f n j , c o p i e s fi l e l f n 3 t o fi l e l f n j a c c o r d i n g
to input directives in the COMPILE file, and adds a
new sorted task library directory at the end of file
lfn^
60459500 A
LIBTASK(P=lfn!,PR,Z);*name DL.
In this example, LIBTASK physically deletes a task
( n a m e ) f r o m fi l e I f n ^ TA F m u s t n o t h a v e t h e fi l e
attached when this command is executed.
10-7
IGNORING A TASK IN THE REPLACEMENT FILE In this example, LIBTASK skips a binary task (name) ^
o n fi l e l f n 2 w h e n c o p y i n g fi l e l f n 2 t o fi l e I
With the IG input directive on the LIBTASK command, lfn!. The IG input directive is the only input
the user can tell LIBTASK to ignore a task binary in directive allowed for the named task.
the
replacement
fi l e
s p e c i fi e d
with
the
B
option
as
-*=^s
follows:
)
LIBTASK(P-lfn1,B=lfn2,Z);*name IG.
10"8
60459500
A
0^**-
REQUIRED SYSTEM TASKS AND TRANSACTIONS
11
The applications programmer should be aware of the
functions of these tasks but may omit the detailed
information contained in this and section 12.
ITASK recognizes the transaction code EX., which is
used to call the system transaction XTRAN. This
special transaction code is reserved for XTRAN.
Several system tasks are required with every
application: BTRAN recovery task (BTASK), data base
r e c o v e r y t a s k ( C TA S K ) , i n i t i a l t a s k ( I TA S K ) ,
K display director (KDIS), logout transaction
terminal (LOGT), message abort (MSABT), inactive
task (OFFTASK), CDCS rerun task (RCTASK), run unit
recovery task (RTASK), system message (SYSMSG), and
execute named tasks (XTASK). Each must reside on
the system task library of every transaction
system. Limited versions of these system tasks are
supplied by Control Data; however, modifications to
t h e s e t a s k s a r e o f t e n n e c e s s a r y f o r s p e c i fi c
applications. One additional system task, CRMTASK,
is required if the TAF/CRM Data Manager is used.
Refer to the TAF/CRM Data Manager 1 Reference Manual
for information on CRMTASK.
("NOTE"!
Directions for installing these tasks are contained
in the TAF Installation section of the NOS 2 Instal
lation Handbook.
Because TTASK schedules tasks, care
must be taken to avoid entering an
infinite loop when a task calls TTASK.
TTASK is described in more detail in section 12.
K DISPLAY TASK (KDIS)
KDIS is a system task scheduled by the transaction
executive when the K.SWITCH command is entered by
t h e c o n s o l e o p e r a t o r. K D I S r e q u e s t s t h e K d i s p l a y
and displays a complete list of K display commands.
The K display commands are discussed in the NOS 2 I
Analysis
Handbook.
|
LOGOUT TASK (LOGT)
BTRAN RECOVERY TASK (BTASK)
BTASK recovers rerunnable BTRAN run units. BTASK
must be installed on the TAF system library.
This task logs a terminal out of TAF. However, the
task does not log the terminal off the computer
system. The task sends a message, END OF
TRANSACTION SESSION; performs a LOGT request; and
performs a CEASE request. The terminal is then
a v a i l a b l e f o r l o g i n t o TA F o r o t h e r n e t w o r k
applications.
DATA BASE RECOVERY TASK (CTASK)
CTASK helps TAF/CRM recover the data base during TAF
initialization, terminal failure, and NETWORK
failure. CTASK must be installed on the TAF system
l i b r a r y.
INITIAL TASK (ITASK)
T h e p r i m a r y f u n c t i o n s o f I TA S K a r e a n a l y z i n g
t e r m i n a l i n p u t a n d TA F - o r i g i n a t e d t r a n s a c t i o n s . I f
t h e TA F - o r i g i n a t e d t r a n s a c t i o n fi e l d i s s e t i n t h e
communication block (figure 2-1), TTASK uses a table
to initiate the processing routine associated with
that type of transaction. Otherwise, TTASK examines
t h r e e c h a r a c t e r s , s t a r t i n g w i t h t h e fi r s t c h a r a c t e r
o f t h e i n p u t m e s s a g e . T h e fi r s t o f t h e s e t h r e e
characters is the transaction code; the other two
comprise the sub transaction code entered from a
terminal.
00*.
60459500 C
MESSAGE ABORT (MSABT)
Message abort (MSABT) is a system task that sends
error messages to the originating terminal when a
transaction is terminated due to a system-detected
e r r o r. M S A B T c h e c k s f o r e r r o r c o d e s t h a t w e r e
placed in the communication block by the transaction
executive or the initial task. When an error code
is detected, MSABT sends the appropriate error
message and initiates an abnormal CEASE function.
MSABT is scheduled in the same manner as other tasks.
If the TOTAL Data Manager is used, MSABT must be
modified to perform a FREEX command. This ensures
that TOTAL records are released if a task aborts.
Error messages issued by MSABT are described in
appendix B.
11-1
INACTIVE TASK (OFFTASK)
SEND MESSAGE TASK (STASK)
This task is provided to give you control over an
internal condition that might be the result of
o p e r a t i o n a l e r r o r. O F F TA S K i s s c h e d u l e d b y t h e
transaction executive when a request has been
received for an inactive task. The task may be
i n a c t i v e o r o ff d u e t o t h e u s e o f t h e K . O F F TA S K
command or use of a LIBTASK directive when the task
was placed in the library. OFFTASK sends an error
message to the originating terminal and ceases
abnormally. It is expected that you will expand the
t a s k t o h a n d l e a n y s p e c i fi c c o n d i t i o n s t h a t m a y
exist when a transaction is interrupted by an
inactive task.
This task sends a message to the terminal and then
terminates. STASK is called from ITASK only when
ITASK is to terminate after sending a message to the
terminal.
CDCS RERUN TASK (RCTASK)
When CDCS becomes available after a failure, RCTASK
i s a c t i v a t e d . R C TA S K d e t e r m i n e s w h i c h t e r m i n a l s
were effected by the CDCS failure and reruns their
transactions (if rerunnable).
RUN UNIT RECOVERY TASK (RTASK)
The recovery task RTASK is a Control Data-supplied
recovery task that will handle most transaction
application needs; however, some sites may wish to
modify RTASK to handle special requirements. The
following discussion will aid understanding of RTASK
in case a modification is required. RTASK must be
available to all applications. This implies that it
m u s t b e p r e s e n t o n t h e TA F s y s t e m t a s k l i b r a r y
(TASKLIB) or en all of the data base task libraries.
It may be on the TASKLIB and any number of selected
data base task libraries. In this case, only those
a p p l i c a t i o n s w i t h o u t t h e i r o w n c o p y o f RTA S K w i l l
use the version on TASKLIB.
After terminal disconnects, or NAM, TAF, and system
failures, the terminal must go through the login
p r o c e d u r e s w i t h TA F. T h e f o l l o w i n g s t e p s o u t l i n e
the decision process followed by RTASK. When a true
condition is encountered, the remaining steps are
skipped.
1. If the run unit Is not recoverable because
RC was not specified on the LIBTASK directive
for the named-transaction, RTASK sends the
message READY to the terminal.
2. If the run unit is not rerunnable because of
an I/O error encountered by TAFREC, RTASK
tells the terminal operator recovery has
occurred and to enter the next command.
3. If the run unit Is secure and the data base
i s c o m m i t t e d , R TA S K s e n d s t h e t e r m i n a l
confirmation (SECURE) message.
4 . R TA S K t e l l s t h e t e r m i n a l o p e r a t o r t h a t
recovery has occurred, that the transaction
is being rerun, and reruns the transaction.
11-2
/£5S|v
SYSTEM MESSAGE TASK (SYSMSG)
This task sends K.MESSAGE-entered messages and
K display diagnostic messages to terminals. It
calls the subroutine in COMKCBT passing the user
argument bits. The word returned is sent after the
message is sent.
EXECUTE NAMED TASK (XTASK)
The execute named task (XTASK) is a special task
scheduler used to execute most named tasks. It will
not execute tasks by the names ITASK, KDIS, MSABT,
OFFTASK, SYSMSG, and XTASK. These are the names of
r e q u i r e d s y s t e m t a s k s . X TA S K c a n b e u s e d t o
schedule LOGT as a means of logging a terminal out
of transaction mode. XTASK is initiated via system
t r a n s a c t i o n X T R A N , d e s c r i b e d f o l l o w i n g t h e X TA S K
description.
EX.task
EX.
Special three-character transaction
code which causes ITASK to schedule
XTRAN via a CALLTRN request. XTRAN
specifies XTASK as its only task.
task
One- to seven-character alphanumeric
t a s k n a m e , l e f t - j u s t i fi e d ( n o s p a c e
between EX. and task) with a
nonalphanumeric character terminator.
A site may want to delete the TRANS table entry of
STRAN (X.), XTASK in the TRANT table of ITASK, or
t h e s y s t e m t a s k X TA S K a l t o g e t h e r f o r s e c u r i t y
r e a s o n s . X TA S K w a s p r o v i d e d a s a m e a n s o f
scheduling tasks, and as an example of how a site
might use such a task. However, it may provide too
much flexibility, and therefore should be used with
discretion.
sf^^X
XTRAN TRANSACTION
Transaction XTRAN must be defined when the system
task library is created. XTRAN will be scheduled
when the three-character code EX. is entered from a
terminal. This transaction allows scheduling any
task in the local or system task library as
described under XTASK.
The characteristics of XTRAN are:
• Task name is XTASK.
• No data managers.
• Not recoverable.
60459500 C
12
ITASK SYSTEM TASK
r
This section describes some of the features,
options, and requirements of ITASK.
Word 2
and following
MACROS
ITASK contains three tables. These tables are set
up for the following codes.
T TO T, n u m b e r o f e n t r i e s i n t h e
table.
Ta b l e e n t r i e s .
The format of a TTOT entry is shown in figure 12-1.
• Time a task is to be run
TRAN MACRO
• Tr a n s a c t i o n c o d e
The TRAN macro sets up entries for the table of
transaction codes (TRANT). TRANT contains the
address of the table of subtransaction codes for
t h a t p a r t i c u l a r t r a n s a c t i o n c o d e . I TA S K a s s u m e s
that the TRANT table is set up in 6-bit display code
o r d e r. I t u s e s t h e 6 - b i t d i s p l a y c o d e v a l u e o f t h e
transaction code you enter to locate the proper
entry in TRANT.
• Sub transaction code
/0^*-
Word 1
A macro is used to set up each type of ITASK table.
These three COMPASS macros, TIMCNT, TRAN, and STRAN,
are discussed here.
The format is:
TIMCNT MACRO
The TIMCNT macro makes an entry in the table of
time-originating tasks (TTOT). TTOT contains the
time a transaction or task is to be initiated and an
address.
One TTOT contains all of the entries, regardless of
the application that is to use them. This feature
allows tasks to be run at predetermined times
w i t h o u t s p e c i fi c t a s k r e q u e s t s o r t e r m i n a l I n p u t t o
initiate the run.
The format is:
TIMCNT hr,min,sec,address
hr
Minute.
sec
Second.
addr ess
STRAN MACRO
The STRAN macro makes entries in the table of
subtransaction codes (TRANS). TRANS contains the
subtransaction code and the corresponding
transaction name.
s c Tw o - c h a r a c t e r s u b t r a n s a c t i o n c o d e .
tname Name of the transaction to be called.
The format of an entry in TRANS is shown in figure
12-3.
The TTOT table format is:
41
address
The format of an entry in TRANT is shown in figure
12-2.
STRAN sc,tname
address Routine address.
59
code One-character transaction code.
The format is:
Hour.
min
TRAN code
17
'wmmmmmm
S
11
hr
min
0
sec
Address is the tag of a user-written subroutine that is called by ITASK to set up
and call the desired transaction or task.
ITASK then clears the table entry so the request is not repeated.
hrmiitisec
0^^
Time the transaction or task Is to be initiated in hours, minutes, s nd secoii d s .
Figure 12-1. Format of a TTOT Table Entry
60459500 A
12-1
59
53
17
length
0
address
length
Length of subtransaction code table (in format allowing unpack function
retrieve it).
address
Address of section in subtransaction table containing associated entries.
to
Figure 12-2. Format of a TRANT Table Entry
59
47
41
sc
tname
sc
Subtransaction code.
tname
Tr a n s a c t i o n n a m e , l e f t - j u s t i fi e d , z e r o - fi l l e d .
Figure 12-3. Format of a TRANS Table Entry
Each group of entries relating to the same trans
action is placed immediately following the TRANT
entry for that code, although the subtransaction
table is assembled elsewhere. This is an example of
the TRANT and TRANS tables.
TRANT
BSS
TRAN
STRAN
02,TRNAME
STRAN
03,TRANN
A is the transaction code, 02 and 03 are the
subtransaction codes, and TRNAME and TRANN are the
respective transactions to be requested.
A site may want to delete the TRANS table entry of
STRAN (X.), XTASK In ITASK for security reasons.
XTASK is described in more detail in section 11.
ITASK DESCRIPTION
E n t r i e s i n a l l I TA S K t a b l e s , a s w e l l a s t h e u s e r
subroutines for TIMCNT entries in TTOT, should be
inserted in the designated places within the program
before assembly. TRANT and TRANS entries must be in
alphabetical or numerical order according to 6-bit
display codes.
• If no transaction was associated with the
t r a n s a c t i o n c o d e , t h e n I TA S K i n t e r prets the
s t r i n g o f c h a r a c t e r s s t a r t i n g w i t h t h e fi r s t
character input and terminating with the
fi r s t n o n a l p h a n u m e r i c c h a r a c t e r a s a
transaction name. If this string is null or
more than seven characters long, an error
m e s s a g e i s i s s u e d ; o t h e r w i s e , I TA S K w i l l
attempt to schedule the named-transaction.
If the named-transaction does not exist in
the task library corresponding to the
terminal application or in the system task
l i b r a r y, a n e r r o r m e s s a g e i s i s s u e d v i a
MSABT.
I n i t i a l t e r m i n a l i n p u t w h i l e TA F i s i d l i n g d o w n
( f o l l o w i n g a n I D L E , TA F o r K . I D L E c o m m a n d ) i s
processed as follows:
• I f t h e i n p u t i s E X . L O G T, t h e l o g o u t i s
processed normally.
• I f t h e i n p u t i s a n y t h i n g e l s e , I TA S K i s s u e s
the message TAF IDLING DOWN to the terminal
and ceases without trying to schedule the
requested transaction.
TTOT entries must be accompanied by user-written
subroutines to set up and call the task, as follows:
I n i t i a l t e r m i n a l i n p u t , w h i l e TA F i s r u n n i n g
n o r m a l l y, r e s u l t s i n e x e c u t i o n o f a t r a n s a c t i o n a s
follows:
• The system time is retrieved from the
appropriate word in the communication
block. TTOT is then searched for any
entries that were to be run by that time.
• If the first three characters of input are
recognized by ITASK as a transaction code
that is associated with a transaction, then
ITASK attempts to schedule the transaction.
Tr a n s a c t i o n c o d e s c a n b e a s s o c i a t e d w i t h
transaction units through the STRAN macro,
previously described.
• I f s u c h a n e n t r y i s f o u n d , I TA S K j u m p s t o
the user's subroutine to set up and call the
task. This subroutine must set up the
communication block required by the task
that is to be run. It must perform a
C A L LT S K w i t h o u t t h e c e a s e o p t i o n s e t t o
ensure that control is returned to ITASK.
12-2
60459500 A
CONDITIONS REQUIRING TAF-ORIGINATED TRANSACTIONS
TAF-ORIGINATED TRANSACTIONS
/0^**
TAF recognizes certain conditions not normally noted
or processed by user applications. Some of these
conditions are:
T h e c o n d i t i o n s t h a t r e q u i r e TA F - o r i g i n a t e d
transactions and possible methods of processing are
described here. Limited versions of routines needed
to process these transactions are available in
TTASK. To change the existing routines, ITASK must
b e m o d i fi e d t o i n c l u d e t h e n e c e s s a r y c o d e o r c a l l
the necessary tasks. It may be advisable to include
short procedures as subroutines in ITASK, but long
or frequently updated transactions should be
maintained as separate programs apart from ITASK and
m e r e l y c a l l e d f r o m t h e I TA S K s u b r o u t i n e . T h e
recovery situations described in this subsection
apply to sites not using TAF automatic recovery.
• Exceeding a length of time as specified by
an assembly option (TACTL).
• K.IDLE command telling
subsystem to idle down.
the transaction
• Tr a n s a c t i o n e x e c u t i v e r e c o v e r y.
• Te r m i n a l l o g i n .
• Network and terminal failures.
W h e n a n y o f t h e s e c o n d i t i o n s o c c u r s , a TA F originated transaction may be processed. Code in
common deck COMKSTC identifies the condition. ITASK
e x a m i n e s t h e c o m m u n i c a t i o n b l o c k ( fi g u r e 1 2 - 4 ) t o
determine the condition and jumps to a subroutine
which sets up and calls the proper task or sequence
o f t a s k s t o r e s p o n d p r o p e r l y t o t h e i d e n t i fi e d
condition. Although the Control Data-supplied ITASK
contains code to process each of the conditions,
s i t e s m a y w a n t t o m o d i f y I TA S K a n d p r o v i d e
transactions to suit their individual needs.
Time Activation
This might be processed by ITASK as follows:
1 . I TA S K r e t r i e v e s t h e s y s t e m t i m e f r o m t h e
appropriate word in the communication block.
2 . T TA S K t h e n s e a r c h e s t h e T T O T f o r a n y
transactions that are to be run at that time.
To p r o v i d e T A F - o r i g i n a t e d t a s k s t h a t p r o p e r l y
respond to the NAM conditions, the analyst should
refer to the NAM/CCP 1 Reference Manual.
3 . I f s u c h a n e n t r y I s f o u n d , I TA S K j u m p s t o
the user-supplied subroutine that must set
up and call the next task for that
transaction. This subroutine must set up
the communication block required by the task
that is to be run.
A number of co mmo n d e cks a i d i n p ro ce ssi n g th e
TAF-originated transactions as follows:
• COMKSTC gives the values for the condition
field of the communication block.
• COMKNWF describes the fields for the NAM
message word of the communication block.
K.IDLE Console Operator Command
• COMSNCD gives values to fields In the NAM
message word.
S a m e a s I D L E , TA F c o m m a n d . R e f e r t o I TA S K
Description earlier in this section.
47
59
1118
WORDO
^ ^ v
database
35
29
23
id
user area
WORD1
user name
WORD 2
reserved
WORD 3
20
17
15
13
11
5
0
sequence number
i nft
condition
NAM message
message from terminal, terminated by 12 bits
of zero in last word of message; meaningless
data follows
»
WORD 58
WORD 59
available to user
t
i
WORD 67
WORD 68
2158
0
yr
mo
day
hr
min
sec
Figure 12-4. Communication Block for TAF-Originated Transactions
60459500 A
12-3
Terminal Login
Terminal Connection Broken
The application may want to prompt the terminal
user, set application character type, or go through
recovery procedures if the user has the recovery
fi e l d s e t i n t h e u s e r a r e a o f t h e t e r m i n a l s t a t u s
table. Upon terminal login, the NAM message word of
the communication block (figure 12-4) contains the
following information:
A connection may be broken because a line has been
disconnected. If a SEND with recall was active, the
task issuing the SEND rather than ITASK is notified
o f t h e e r r o r. I t m a y b e d e s i r a b l e f o r t h e a p p l i c a
t i o n t o p r o c e s s t h e s e i n c o m p l e t e t r a n s a c t i o ns. TAF
s e t s t h e r e c o v e r y fi e l d i n t h e t e r m i n a l s t a t u s ta b l e
user area. The application can save terminal output
on a data manager file and send it when the user
logs in again. The outstanding block limit speci
fi e d i n t h e l o c a l c o n fi g u r a t i o n fi l e d e t e r m i n e s h o w
many messages must be saved. (Refer to the Network
Products NAM 1 Network Definition Language Reference
Manual.)
S i g n i fi c a n c e
Block size of terminal.
24
S i g n i fi e s a h a r d w i r e d t e r m i n a l i f
set.
2 3 - 1 6 Te r m i n a l c l a s s .
15-8 Page width of terminal.
7-0 Page length of terminal.
Terminal Break Conditions
If some tasks perform SENDs without the recall flag
set, breaks can occur because of the following.
Network Normal Shutdown
TAF monitors task activity on communication blocks
generated by terminal input. When all tasks have
been completed and no tasks are performing WAITINP
r e q u e s t s , TA F s e n d s e n d c o n n e c t i o n s u p e r v i s o r y
messages to NAM for each logged-in user and performs
a NETOFF to end processing with the network. To
initiate this condition, it may be desirable for
ITASK to notify users of the pending shutdown and
begin rejecting new transactions.
• User break k e y s .
• Output device not ready.
Network Failure
• Incorrectly formatted data.
TAF sets the recovery field in the user area of the
terminal status table for all logged-in users. All
t a s k s p e r f o r m i n g WA I T I N P r e q u e s t s a r e s c h e d u l e d .
The application, through ITASK, may want to begin
data base recovery.
For a user to resume processing after a terminal
break, the following must occur.
1 . Te r m i n a l c o m m u n i c a t i o n w i t h N A M m u s t b e
reestablished. When the break occurs, NAM
places the supervisory message associated
with the break in the NAM message word of
t h e c o m m u n i c a t i o n b l o c k . To r e s t a r t
terminal communications, TAF must send a
reset supervisory message to NAM. The
individual application need not provide this
function. Upon the user task SEND request,
TA F i s s u e s t h e r e s e t s u p e r v i s o r y m e s s a g e
prior to honoring the SEND.
2. The user must resume interaction with the
application. The user application must
p r o v i d e t h i s b r e a k r e c o v e r y. T h e f o l l o w i n g
description suggests one method.
ITASK and any recovery tasks can communicate
through the terminal status table user
area. For instance, when ITASK initiates a
t r a n s a c t i o n , i t c o u l d s e t a s e r i e s o f fi e l d s
in the TST to indicate important events in
the transaction. The recovery task could
examine the fields to determine what events
had occurred. Nonrecovery tasks could watch
a recovery field in the TST and CEASE to
allow the recovery task to proceed ir a
q u i e t e n v i r o n m e n t . ( TA F s e t s t h e r e c o v e r y
field in the TST before calling ITASK.)
12-4
Network Immediate Shutdown
TAF performs a NETOFF and sets the recovery field in
the user area of the terminal status table. The
application may want to begin recovery by processing
only transactions from batch input.
Terminal Inactive
NAM issues a terminal inactive supervisory message
when it detects that 10 minutes have elapsed without
message traffic over a connection. TAF passes the
transaction sequence number of any running, task
using that user name to ITASK. The application may
want to log out the user after a period of time to
reduce line connect costs.
Logical Error
One of the application's tasks may have set up an
application block header or message block
i n c o r r e c t l y. I f t h e t a s k p e r f o r m e d a S E N D r e q u e s t
w i t h r e c a l l s e t , t h e t a s k , r a t h e r t h a n I TA S K , i s
n o t i fi e d o f t h e e r r o r.
60459500 A
/>^«i\
J^*v
Block Not Delivered
TERMINAL TYPE AHEAD
This occurs because of a system error. If the task
performed a SEND request with recall set, the task,
r a t h e r t h a n I TA S K , i s n o t i fi e d o f t h e e r r o r. B e f o r e
scheduling ITASK, TAF sets the recovery field in the
user area of the TST. It may be desirable for the
application to recover by sending the lost block.
The application block number of the block that was
lost is returned in the NAM message word of the
c o m m u n i c a t i o n b l o c k . Ta s k s m a y s p e c i f y a b l o c k
number on the SEND or obtain the block number used
b y TA F. R e s e n d i n g t h e l o s t b l o c k m a y c a u s e t h e
block to be delivered out of sequence, if further
blocks had been sent following the lost block.
The network allows terminal operator type-ahead. In
other words, the terminal operator can enter several
transactions without waiting for the response from
t h e fi r s t . T h e n e t w o r k i g n o r e s a l l t y p e - a h e a d w h e n
the terminal operator enters a user break 1 or user
break 2.
Terminal Characteristic Change
A NAM terminal characteristic supervisory message is
s e n t t o I TA S K w h e n t h e t e r m i n a l o p e r a t o r h a s
r e d e fi n e d t h e t e r m i n a l c l a s s , p a g e w i d t h , o r p a g e
length.
jfl^lfes^
Terminal Input Too Large
The terminal operator sent a message longer than the
m a x i m u m i n p u t m e s s a g e s i z e . TA F w i l l n o t h a v e
journalized the input.
USER STATUS
The network allows a terminal user to make a status
request by typing:
ct (alpha)®
c t T h e n e t w o r k c o n t r o l c h a r a c t e r.
(alpha) Any alphabetic character.
TA F w i l l r i g h t j u s t i f y t h e c h a r a c t e r I n w o r d 3 o f
the communication block and Initiate ITASK. At this
point a user-written routine In ITASK must take over
t o p e r f o r m w h a t e v e r a c t i o n i s d e s i r e d . T h e I TA S K
reason code will Indicate a user status message.
J^*
60459500 C
12-5
0^,
0^^
CHARACTER SETS
Ta b l e A - l l i s t s t h e c h a r a c t e r c o d e s f o r t h e A S C I I
63/64-character sets. Users should check with a
site analyst to see which character set is being
used.
Table A-l. 7-Bit ASCII Code Standard Print 63/64-Character Set (Sheet 1 of 2)
7-Bit ASCII Code
ASCII
Character
Octal
Hexadecimal
072
101
102
103
104
105
106
107
110
U l
112
113
114
115
116
117
120
121
122
123
124
125
126
127
130
131
132
060
061
062
063
064
065
066
067
070
071
053
055
052
057
050
051
044
075
3A
41
42
43
44
45
46
47
48
49
4A
4B
4C
4D
4E
4F
50
51
52
53
54
55
56
57
58
59
5A
30
31
32
33
34
35
36
37
38
39
2B
2D
2A
2F
28
29
24
3D
t In the 63/64-character set,
a null character. Also, use
fi l e s m a y c a u s e p r o b l e m s .
is used in print and format
6-Bit
Display Code
(Octal)
001
01
02
03
04
05
06
07
10
11
12
13
14
15
16
17
20
21
22
23
24
25
26
27
30
31
32
33
34
35
36
37
40
41
42
43
44
45
46
47
50
51
52
53
54
this 6-bit display code represents
of the colon in program and data
This is particularly true when it
statements.
0mK
60459500 A
A-l
Table A-l. 7-Bit ASCII Code Standard Print 63/64-Character Set (Sheet 2 of 2)
7-Bit ASCII Code
ASCII
Character
(space)
>
i
l
]
X
ii
!
&
1
<
>
@
\
*
Octal
040
054
056
043
133
135
045
042
137 tt
041
046
047
077
074
076
100
134
136
073
Hexadecimal
20
2C
2E
23
5B
5D
25
22
5F
21
26
27
3F
3C
3E
40
5C
5E
3B
6-Bit
Display Code
(Octal)
55
56
57
60
61
62
63t
64
65
66
67
70
71
72
73
74
75
76
77
/<^V
tin the 63/64-character set, this 6-bit display code repre
sents a colon (:), 7-bit ASCII code 072, 7-bit hexadecimal
code 3A.
ttOn TTY models having no underline, the back arrow (—) takes
its place.
/<^^\
A-2
60459500 A
DIAGNOSTIC
MESSAGES
B
This appendix contains an alphabetical listing of Lowercase letters are used within a message to
m e s s a g e s w h i c h m a y b e i m p o r t a n t t o t h e T A F i d e n t i f y v a r i a b l e fi e l d s . A l l m e s s a g e s b e g i n n i n g
p r o g r a m m e r . E a c h m e s s a g e i s f o l l o w e d b y a n w i t h l o w e r c a s e ( v a r i a b l e ) fi e l d s a r e l i s t e d
e x p l a n a t i o n o f t h e m e s s a g e a n d / o r t h e c i r c u m s t a n c e s a l p h a b e t i c a l l y a c c o r d i n g t o t h e fi r s t n o n v a r i a b l e
causing it to be issued, the recommended action, and field after the messages that begin with nonvariable
t h e r o u t i n e w h i c h i s s u e d t h e m e s s a g e . fi e l d s .
jpx
/$^K
60459500
A
B_l
MESSAGE
ACTION
SIGNIFICANCE
ROUTINE
cmd ACCEPTED..
The network has accepted your terminal
d e fi n i t i o n c o m m a n d c m d .
None.
CCP
AFTER IMAGE ACCUMULATOR TABLE OVERFLOW.
W h e n u p d a t i n g a fi l e , t h e a f t e r i m a g e
a c c u m u l a t i o n t a b l e w a s fi l l e d .
The size of the AAIT
table in OMPEC must be
increased. Inform the
d a t a a d m i n i s t r a t o r.
DMREC
(AAI)
AFTER IMAGE RECOVERY FILE IS FULL.
T h e a c t i v e a f t e r i m a g e r e c o v e r y fi l e u s e d
b y TA F i s f u l l .
This file must be dumped
by DMREC.
TAF
db AFTER IMAGE RECOVERY FILES UNAVAILABLE.
TA F / C R M d a t a m a n a g e r t r i e d t o b r i n g u p a n
a f t e r i m a g e r e c o v e r y fi l e f o r d a t a b a s e d b
but failed. Possible reasons for the
Correct problem with
ARFs.
AAMI
.ysfesx
failure:
- ATTACH error
- ARF header name is incorrect
- ARF header status error
- CIO error on ARF
- Change in ARF block length
- ARF full
If the data base was down previously, it
will remain down. If not down, it will now
be idling down.
AIP DEBUG OPTION TURNED OFF.
Self-explanatory.
None.
TAF
AIP DEBUG OPTION TURNED ON.
Informative message. All network messages
will be placed on trace file ZZZZZDN.
None.
TAF
AIP TOO LARGE FOR LOADING.
A fatal error occurred causing TAF to abort.
Inform site analyst.
TWFA must be increased
in deck COMKTAF.
TAF
filename ALLOCATED.
Informative message.
None.
DMREC
APPLICATION ERROR - NO TERMINAL OUTPUT.
A task error. A transaction has run without
either an error message or a SEND being
sent to the originating terminal.
Correct task or inform
data base administrator.
MSABT
APPLICATION FAILED - applnam
An application has stopped without making a
request to NAM to terminate.
Restart application
and/or contact central
software support,
analyst.
NVF
APPLICATION NETTED OFF - applnam
Application applnam has requested
termination of network access.
None.
NVF
APPLICATION NETTED ON - applnam
An application has successfully requested
and attained network access.
None.
NVF
ARF BLOCK SIZE IS LARGER THAN BUFFER.
The maximum block length field in the
header record for an ARF is larger than the
maximum block length (installation
parameter) allocated by TAF/CRM data
manager.
The file must be dumped
using DMREC and
preallocated.
ARF DUMP TAPE HEADER ERROR.
No header found on ARF tape.
Use alternate tape if
available.
DMREC
ARF ENTRY TABLE OVERFLOW
Too many recoverable file names exist on
this ARF.
Increase the size of the
TLOG table with
installation parameter
TLOGL.
AAMI
ARF FILE HEADER ERROR.
No header was found on the ARF file.
Down the data base, dump
the data base, purge the
old ARF, and create a
new one.
DMREC
ARF HEADER ERROR.
No ARF header on what is supposed to be an
ARF.
Check ARF for validity,
inform data
a d m i n i s t r a t o r.
OMREC
ARF HEADER STATUS (3) POSSIBLE ERROR.
ARF header status shows a possible error
condition.
Inform data
a d m i n i s t r a t o r.
DMREC
ARF ORDINAL MUST BE 01 OR 02.
ARFs can have only 01 or 02 as an ordinal.
Correct directive name
(ARF/BRF).
DMREC
ARITHMETIC OR OTHER SOFTWARE ERROR IN TASK.
A task error. Hardware or the system
detected a software error in the task.
Correct task or inform
data base administrator.
MSA8T
ATTACH ERROR ON - filename.
The transaction executive cannot attach the
file filename under present conditions.
This usually implies that the file does not
exist or modify permission has not been
given to the TAF user name.
Correct error and
reinitialize executive,
or inform the data
a d m i n i s t r a t o r.
TAF
• B-2
60459500 C
#
ROUTINE
ATTACH ERROR ON PF xxxxxxx.
When attempting to attach a permanent file
xxxxxxx, an error was encountered.
Check for valid
directive file name and
presence of a direct
access permanent file by
that name.
DMREC
ATTACH MODE MUST BE W, M, R, OR RM.
The mode parameter on the CYBER
Record Manager (CRM) statement
must be one of the specified values.
Correct the mode
parameter on the CRM
statement or inform the
data administrator.
TAF
n.nnn AVERAGE ACTIVE SUBCONTROL POINTS.
n.nnn is the average number of simul
taneously active subcontrol points when
TAF is not rolled out. An active
subcontrol point is one which is in
recall, is waiting to use the CPU, or is
currently assigned the CPU. The
sampling rate is once per second.
None.
TAF
n.nnn AVERAGE OUTSTANDING CDCS REQUESTS.
n.nnn is the average number of out
standing (uncompleted) systemThentrol
t requests per second, r se
The sampling rate is once per second.
None.
TAF
BACKUP DIRECTORY - xxxxxxx HAS BEEN
RECONSTRUCTED.
No directory file for the specified data
base. A new directory was generated from
the information on the xxJ file.
Inform data
a d m i n i s t r a t o r.
DMREC
BATCH CONCURRENCY DISABLED.
TAF was brought up without BATCH
concurrency enabled. CTBCON=Q).
Ask data administrator
to bring up TAF with
BATCH concurrency
ENABLED.
BAAML
BATCH RECOVERY ACTIVE ON DATA BASE
Self-explanatory
Wait for the completion
of batch recovery, then
reinitialize the
transaction subsystem.
TAF1
BEGIN CRM TASK RECOVERY.
TAF/CRM has received a recovery indication
from TAF.
None.
AAMI
BFL - xxxxxxxB, MINIMUM REQUIRED = zzzzzzzB.
Information on the actual value of the
beginning field length and the minimum
value TAF/CRN requires for the Common
Memory Manager Buffer.
None.
AAMI
BINARY RECORD WAS LESS THAN 64D WORDS LONG.
The task binary file contains records in
the wrong format.
Ensure that a LOAD was
performed after
compilation of the tasks.
LIBTASK
BINARY RECORD WAS NEITHER ABSOLUTE NOR
OVERLAY FORMAT.
The task binary file contains records in
the wrong format.
Ensure that a LOAD was
performed after
compilation of the tasks.
LIBTASK
BLOCK BUFFER OVERFLOW.
When attempting a record load operation,
the data block buffer was found to be too
small.
Increase the length
of the working buffer
WBUF. Inform the data
a d m i n i s t r a t o r.
DMREC
BLOCK BUFFER TOO SMALL.
Tape block on ARF was too large for buffer.
Increase size of buffer
and try again.
DMREC
BLOCK LOAD ERROR.
Block load of a file failed because no
header was found on dump tape. Or, the
targeted f1le or the tape does not match
request file name.
Load from previous dump
tape.
DMREC
BLOCKAGE AMONG CM RESIDENT TASKS.
The sum of initial field lengths for the CM
resident tasks exceeds the minimum size of
total task area.
C o r r e c t e r r o r.
BOTH AFTER IMAGE FILES ACTIVE.
Both after image recovery files for a data
base are active. The after image files
must be dumped by DMREC, if not already
dumped.
Dump the after image
r e c o v e r y fi l e s .
TAF
BRF PARAMETER TOO LARGE OR INVALID.
The parameter on the BRF statement is
nonnumeric, the value is greater than the
installation parameter BMAX, or too many
parameters were specified.
Correct BRF statement or
reassemble TAF and
related decks with a
larger value for BMAX
(if possible).
TAF
BTASK - TAF AUTOMATIC RECOVERY NOT
INSTALLED.
A keyword specified in a TSTAT request
requires TAF automatic recovery to be
installed.
Inform the data
a d m i n i s t r a t o r.
8TASK
BTASK - TASK LOGICAL ERROR.
An unexpected error status was returned.
Inform the data
a d m i n i s t r a t o r.
BTASK
^
JP*s
ACTION
SIGNIFICANCE
MESSAGE
60459500 C
8-3 •
MESSAGE
SIGNIFICANCE
ACTION
ROUTINE
BTASK - xxxxxxx TRANSACTION NOT RUNNABLE
NOW.
This occurs when an I/O error is detected
and the data base cannot be recovered for
the user xxxxxxx.
Inform the data
a d m i n i s t r a t o r.
BTASK
BTASK - USER NOT DEFINED IN NETWORK FILE.
The user is not defined in the NETWORK file
on a TSTAT request.
Inform the data
a d m i n i s t r a t o r.
BTASK
C. B. NOT AVAILABLE TO SCHEDULE CTASK.
Communication block not available to
schedule CTASK.
Increase the number of
communication blocks at
initialization time
using the K.MC8- command.
TAF
CALLRTN NESTED CALL LIMIT EXCEEDED.
A task error. An attempt was made to nest
CALLRTN requests more than 16 levels.
Correct task or inform
data base administrator.
MSABT
CANNOT DEFINE REFORMATTED FILE - filename.
A reformat of the TAF COMMUNICATIONS
recovery file was necessary, but when
attempting to DEFINE the reformatted file
(ZZCRFAi), an error occurred.
Purge the existing file
indicated by filename.
TAFREC
CDCS ABORTED PLEASE WAIT.
A TAF transaction was using CDCS while CDCS
aborted. The transaction will be rerun
after CDCS comes back up.
Operator can log off by
typing in EX.LOGT, or
wait for CDCS.
ITASK
CDCS CONNECTION ESTABLISHED.
Informative message. The connection
between TAF and CDCS has been established.
None.
TAF
CDCS INVOKE FAILURE.
CDCS files are not available.
Inform site analyst or
d a t a a d m i n i s t r a t o r. T h e
transaction should be
rerun after the problem
i s fi x e d .
MSABT
CDCS NOT AVAILABLE.
Your TAF transaction attempted to use CDCS
when it was not present in the system, CDCS
aborted while your transaction was waiting
for completion of a CDCS request (SSC), or
CDCS aborted while your transaction was
rolled out.
Inform data
a d m i n i s t r a t o r.
MSA8T
CDCS REQUESTED ABORT.
TAF aborted the TAF transaction as a result
of a request by CDCS. The detailed error
message returned by CDCS is available in
the JOURO file and will be sent to the
terminal.
Inform data
a d m i n i s t r a t o r.
MSABT
CHANGED TLD DETECTED - filename, username.
An unrecognizable library directory format
was encountered during a library directory
update attempt.
Inform site analyst.
TAF
CIO ERROR ON RECOVERY FILE
A CIO error was encountered while trying to
position the ARF or BRF correctly.
Reinitialize the
transaction subsystem or
inform the site analyst.
TAF1
*CMM* ERROR.
A *CMM* error occurred. Memory cannot be
granted to load *OPEN* routine.
Inform data base
a d m i n i s t r a t o r.
AAMI
CMMBFL IS NOT LARGE ENOUGH.
The size of the beginning field length
(8FL> for the Common Memory Manager Buffer
is not large enough to contain CMMTFL
and CKMCAP and the user's FIT-S and
FSTT-S.
Data base administrator
can either
1) Increase the size of
CMMBFL, or
2) decrease the size of
CMMTFL, or
3) decrease the size of
CMMCAP.
TAF
CONFLICTING LIBTASK OPTIONS - p1,p2.
The user specified an incorrect combination
of LIBTASK command options. Possible
incorrect combinations of p1 and p2 are:
The user must choose
either p1 or p2. For
the P=0,-N combination,
the user must specify N
if no old task library
(P=0) exists.
LIBTASK
- CR,PR
- CR,TT
- PR,TT
- T T, N
Another possible incorrect combination
gives P=0,-N for p1,p2. This means that
the user specified P=0 but did not specify
N.
/*^5§k
U s e r s p e c i fi e d T T o p t i o n w h e n t a s k
l i b r a r y w a s n o t a t t a c h e d b y TA F.
CONTROL CARD ARGUMENT ERRORS.
Errors exist in the parameters on the
LIBTASK command.
Correct and rerun.
LIBTASK
CRF HEADER ERROR - filename.
I/O errors or logical errors were
encountered in the header record of the
n a m e d C R F. T h e fi l e i s u n u s a b l e ,
fi l e n a m e F i l e n a m e
I n i t i a l i z e t h e fi l e
using the K.INT initial
K display command.
TAFREC
• B-4
/ ? i ^ \
60459500 C
ACTION
SIGNIFICANCE
MESSAGE
ROUTINE
CRF RECOVERY/INITIAUZATION ABORTED.
Informative message.
T h e a c t i o n d e p e n d s o n TA F R E C
the message preceding
this one in the dayfile.
CRF RECOVERY/INITIALIZATION COMPLETE.
Informative message.
None.
CRF RECOVERY UNIT ERROR - filename.
I/O errors or logical errors were
encountered in a run unit of the named CRF.
A t t e m p t t o r e c o v e r a n y TA F R E C
g o o d i n f o r m a t i o n u s i n g TA F
the K.ERO=YES initial K
display command, or
i n i t i a l i z e t h e fi l e
using the K.INT initial
K display command.
CRM(...parameter-list...)
This is a copy of a CRM statement that is
in error. A subsequent message follows.
Inform
the
a d m i n i s t r a t o r.
CRM DATA MANAGER NOT LOADED.
An AAM request for CRM was issued by a task
and the CRM Data Manager was not loaded
into TAF at initialization time.
Check the DMS statements MSABT
in the TCF which specify
which data managers are
to be loaded by TAF.
For CRM users, you need
a DMS statement such as:
DMS,CRM,ON,xx,xx,...,xx
TA F R E C
data
TA F
where xx = any data base
i d e n t i fi e r .
CRM DATA MANAGER SUCCESSFULLY LOAOED.
Self-explanatory.
None.
TAF
CRM ERROR nnnB IGNORED ON OPEN OF filenara.
A non-fatal CRM error, nnnB, was returned
to the TAF/CRM data manager while issuing
CRM requests associated with opening a
recoverable CRM file, filenam, for the
fi r s t t i m e . T h i s e r r o r i s i g n o r e d .
Informative.
AAMI
CRM ERROR ENCOUNTERED.
A CRM error occurred while processing the
directory. The CRM error is either an
incorrect key or end of file when this is
the only output message.
Inform data
a d m i n i s t r a t o r.
DMREC
CRM ERROR xxx IN UPDATE PROCESSOR.
A CRM error has occurred during the
application of the after image to a data
fi l e .
Note which error has
occurred and locate
references to the error
in the CRN/AAM Reference
Manual for appropriate
action.
DMREC
TAF
CRM ERROR IN ZZdbOIR (GET).
A CRM error was encountered when trying to
retrieve a VSN record from the directory on
a fi l e l o a d .
Inform data
a d m i n i s t r a t o r.
DMREC
CRM TASK RECOVERY IMPOSSIBLE.
Recovery is not possible when the recovery
file structure is found to be inconsistent
with TAF/CRM tables and parameters
specified on xxJ files.
The last reported BRF
must be corrected or
reallocated.
AAMI
CRMTASK - DATA BASE DOWNED BY OPERATOR.
DMREC notified TAF that the data base was
recovered. But AAMI was not able to access
it because it had been downed by the
o p e r a t o r.
Only an operator may up
the data base that
he/she downed. It
cannot be upped
a u t o m a t i c a l l y.
CRMTASK
CRMTASK - DATA BASE/FILE BEING IDLED.
AAMI will not process any requests on an
i d l e d a t a b a s e / fi l e .
After the cause of the
data base/file being
idle has been fixed, the
operator must bring it
up.
CRMTASK
CRMTASK - DATA BASE/FILE CANNOT BE UPPED.
AAMI was not able to bring up the data
base or fi le.
Oata administrator
must investigate
the cause of AAMI
inability to bring
file/data base up.
CRMTASK
CRMTASK - DATA BASE/FILE NAME UNKNOWN.
DMREC request had an incorrect data base
or file name.
Call the data
administrator to
investigate the cause.
CRMTASK
CRMTASK - INCORRECT REQUEST.
CRMTASK was not called correctly by DMREC.
There may be a
transaction in the
system attempting to use
functions reserved for
DMREC.
CRMTASK
CRMTASK - INCORRECT REQUEST FORMAT.
AAMI rejected this request.
An analyst should
investigate the reason
for this rejection.
CRMTASK
^ ^ N
60459500 C
B-5 •
MESSAGE
SIGNIFICANCE
ACTION
ROUTINE
CRMTASK - INCORRECT TT SEQUENCE NUMBER.
AAMI does not recognize the TT sequence
number returned by DMREC.
Call the analyst to
investigate the
discrepancy between
DMREC and TAF.
CRMTASK - NOT ALL DATA BASE FILES UPPED.
DMREC recovered the data base but AAMI was
unable to attach/open all of data base
fi l e s .
Data administrator
should investigate why
only some of the data
base files came up.
CRMTASK TIMEOUT.
A terminal job timed out while waiting for
the next command.
A valid command must be CRMTASK
entered within the
default time of 480
seconds.
CRT - CIO ERROR.
A CIO error was generated when creating a
l o g fi l e .
Purge the log file and
try again (check file
name).
DMREC
CSM - INCORRECT COMMUNICATION FUNCTION.
An incorrect or unrecognizable request was
received by the transaction executive from
t h e C P U m o n i t o r.
Inform site analyst.
TAF
CTASK - DATA BASE OR FILE DOWN.
T h e d a t a b a s e , TA F / C R M , o r fi l e i s d o w n o n
an RSTDBI request.
Inform the data
a d m i n i s t r a t o r.
CTASK
CTASK - DATA BASE OR FILE IDLE.
T h e d a t a b a s e , TA F / C R M , o r fi l e i s i d l e o n
an RSTDBI request.
Inform the data
a d m i n i s t r a t o r.
CTASK
CTASK - FILE IS NOT INSTALLED.
T h e d a t a b a s e o r fi l e i s n o t a v a i l a b l e i n
t h e x x J fi l e o n a C R M S TAT r e q u e s t .
Inform the data
a d m i n i s t r a t o r.
CTASK
CTASK - INCORRECT RECOVERY CASE.
The recovery case selected for processing
was incorrect.
Inform the data
a d m i n i s t r a t o r.
CTASK
CTASK - NO CRM RECOVERY FILES FOR DATA BASE.
T h e r e i s n o r e c o v e r y fi l e a s s i g n e d t o t h e
data base on an RSTDBI request.
Inform the data
a d m i n i s t r a t o r.
CTASK
CTASK SYSTEM IDENTIFIER UNKNOWN.
T h e o l d s y s t e m i d e n t i fi e r i s u n k n o w n w h e n
issuing a TINVOKE request.
Inform the data
a d m i n i s t r a t o r.
CTASK
CTASK - TABLE AREA NOT LARGE ENOUGH.
Ta k e t a b l e a r e a s u p p l i e d b y C TA S K f o r a
CMRSTAT request is not large enough.
Inform the data
a d m i n i s t r a t o r.
CTASK
CTASK - TASK LOGICAL ERROR.
An unexpected error status was returned.
Inform the data
a d m i n i s t r a t o r.
CTASK
CTASK - TRANSACTION NOT RERUNABLE.
T h e TA F t r a n s a c t i o n w a s n o t r e r u n n a b l e a n d
a RERUN was attempted.
Inform the data
a d m i n i s t r a t o r.
CTASK
CTASK - TRMREC ERROR.
One of the following occurred:
Inform the data
a d m i n i s t r a t o r.
CTASK
- There was no outstanding DBEGIN request.
- An error was encountered on a data base
or recovery file.
- The data base or TAF/CRM is down.
CRMTASK
C R M TA S K
CTASK - USER NOT DEFINED IN NETWORK FILE.
The user specified on a TSTAT, WSTAT, or
RERUN request is not defined in the NETWORK
fi l e .
Inform the data
a d m i n i s t r a t o r.
CTASK
CYCLE NUMBER IS OUTSIDE LIMITS.
The specified cycle number is outside the
limits set by the installation parameter
(CYUCM).
Check the maximum cycle
number and rerun.
DMREC
(CYC)
DATA BASE/FILE ALREADY DOWN OR IDLE.
CRMTASK issued a DBDOWN request to AAMI,
but the data base or file name was already
down or idle.
Inform data base
a d m i n i s t r a t o r.
CRMTASK
DATA BASE/FILE CANNOT BE UPPED.
CRMTASK issued a DBUP request but AAMI was
not able to bring up the data base or file
name.
Inform data base
a d m i n i s t r a t o r.
CRMTASK
OATA BASE/FILE NAME UNKNOWN.
CRMTASK - issued a CRMSTAT, DBUP, or DBDOWN
request but the data base or file name was
not found.
Inform data base
a d m i n i s t r a t o r.
CRMTASK
DATA BASE NAME IN CRM FILE NAME DOES NOT
MATCH xxJ.
The two-character data base name from the
file name on the CRM statement does not
m a t c h t h e x x J h e a d e r.
Correct the CRM
statement and try again.
DMREC
DATA BASE NAME OR FILE NAME MISSING.
N o fi l e n a m e o r d a t a b a s e n a m e o n d i r e c t i v e .
Include file name or
data base name on
directive.
DMREC
DATA BASE NAME OR FILE NAME(S) BOTH
SPECIFIED.
Self-explanatory.
Eliminate file name or
data base name from the
directive.
DMREC
• 8-6
60459500 C
ACTION
SIGNIFICANCE
MESSAGE
ROUTINE
DATA BASE NOT IN EOT
Self-explanatory.
Reinitialize the
transaction executive,
or inform the site
analyst.
TAF1
DATA BLOCK BUFFER OVERFLOW.
ARF tape block size is too large for buffer
allocated for it.
Inform the data
administrator and
lengthen buffer WBUF.
DMREC
DATA MANAGER USAGE NOT SELECTED.
A recoverable TAF transaction tried to use
either the CDCS or CRM Data Managers and
the usage of the data manager was not
selected on the LIBTASK input which
declared the named-transaction to TAF.
Respecify the
characteristics of the
named-transaction via
the LIBTASK directive,
or design the
transaction not to use
CDCS or CRM Data
Managers.
MSABT
DB - NAME MUST NOT START WITH THE LETTER Z.
A data base name was found which starts
with the letter Z. These are reserved
names.
Change the data base
name to one not
beginning with Z. If
the name appears on an
NCTF entry, contact the
user and request a new
i d e n t i fi e r. I f t h e n a m e
appears on the TCF, make
the change on the
applicable DMS statement
or inform the data
a d m i n i s t r a t o r.
TAFREC
An error in defining PRU size or In trying
to define the log file was encountered on a
create directive.
Correct PRU length on
create directive.
DMREC
*DEL*
The system has deleted the last line of
input. This occurred when the terminal
operator entered the cancel character (CN)
followed by the end of line/end of block
t e r m i n a t o r.
None.
CCP
DELIMITER WAS NOT RECOGNIZED.
An incorrect delimiter or an unrecognizable
delimiter was encountered on a directive.
Check directive format
and rerun.
DMREC
DIRECTIVE CONTAINS AN INCORRECT DATE/TIME.
A directive contains an unrecognizable
date/time.
Correct the directive
and rerun.
DMREC
DIRECTIVE FORMAT ERROR.
Error in one or more directive parameter
formats.
Correct directive and
rerun.
DMREC
DIRECTIVE KEYWORD NOT VALID.
The wrong delimiter on the directive
parameter was used, or the directive
keyword is not valid.
Correct directive and
rerun.
DMREC
(SPR)
DIRECTIVE NOT PRECEDED BY EDIT DIRECTIVE.
This directive must be preceded by an edit
directive.
Include an edit
directive.
DMREC
DIRECTORY HEADER FROM THE COPY.
Informative message.
None.
OMREC
OIRECTORY IS FULL-NO MORE ADDITIONS ALLOWED.
The maximum length of the task library
directory has been reached.
LIBTASK must be
reassembled to allow for
a l a r g e r d i r e c t o r y.
LIBTASK
DIRECTORY UNUSABLE.
Attempt to reconstruct the directory failed.
Check the output for the
detailed error message.
OMREC
DISPLAY DUMP NOT ALLOWED TO TERMINAL.
A 6-bit display code dump to a terminal is
not allowed.
Specify the 0 option on
the KTSDMP command if a
dump to a terminal is
desired.
KTSDMP
DMREC COMPLETE.
Informative message. The output f1le may
contain other informative messages and
should be reviewed.
None.
DMREC
DMREC FAILED - xxxxxxx zz.
The DMREC job submitted by TAF failed,
xxxxxxx is the directive being processed,
and zz is the data base name.
Notify the data base
administrator and
correct as directed.
DMREC
DMREC TAPE LABEL ERROR.
No tape header was found on ARF to be used
for an update function.
Check for correct ARF
tape. Use alternate ARF
tape if available.
DMREC
(UPD)
DOWNED BRF TABLE OVERFLOW.
Table of downed BRFs has overflowed.
Inform data
a d m i n i s t r a t o r.
DMREC
(BRT)
/^^ DEFINE ERROR ON FILE.
J^"v
60459500 C
8-7 •
MESSAGE
DSP ERROR ec RETURNED ON J08 ROUTE.
SIGNIFICANCE
ACTION
ROUTINE
DSP has informed the transaction subsystem
that an error was detected in routing a job
for task dump processing, ec is the DSP
error code.
Inform site analyst.
DSP ERROR ec RETURNED ON TASK SUBMIT,
DSP has informed the transaction subsystem
that an error other than a job or user
statement error was detected, ec is the
DSP error code.
Inform site analyst,
TAF
DUMP TAPE SPECIFIES NON-STANDARD
COMPRESSION.
When trying to reload a record formatted
dump tape, the compression mode was
nonstandard.
Try loading from a
previous dump tape and
inform the data
a d m i n i s t r a t o r.
DMREC
DUMP WILL START OVER
DMREC attempted to execute the DUMP
directive but encountered errors.
None.
DMREC
cmd DUPLICATE CHARACTER
The value you specified in the terminal
definition command cmd conflicts with
another terminal definition.
Try another value.
CCP
DUPLICATE DATA BASE IN TCF - xx.
Active data base identifier, xx, in the TCF
is not unique.
Fix TCF so that xx
appears only once among
active (ON) DMS
statements.
TAF
DUPLICATE DUMP ENTRY ON ADD.
When trying to add a file dump entry to the
directory with an add directive, a
duplicate entry was found.
List the directory for
visual check and try
again.
DMREC
DUPLICATE ENTRY ON ADD.
When trying to modify the directory a
duplicate of the entry was found.
List the directory and
check for the needed
e n t r y.
DMREC
DUPLICATE PARAMETER.
A duplicate VSN or duplicate file name was
detected on a single directive.
Correct directive and
rerun.
DMREC
DUPLICATE VSN ENTRY ON ADD.
When trying to add a VSN entry to the
directory with an add directive, a
duplicate entry was found.
List the directory for
visual check and try
again.
DMREC
DXB CONVERSION ERROR ON TRANSACTION SEQUENCE
NUMBER.
An error occurred while converting the
number in the table entry to binary.
Inform data
a d m i n i s t r a t o r.
DMREC
ECS READ ERROR.
S e l f - e x p l a n a t o r y.
Inform customer engineer.
TAF
ECS TASK tasknsme NOW MS RESIDENT.
Task taskname could not be loaded into
extended memory because of insufficient
storage. It Is loaded Into mass storage.
If task must be resident
in extended memory, more
extended memory space
must be allocated for
the TAF user name.
Refer to the NOS 2
Installation Handbook.
TAF
ECS WRITE PARITY ERROR ENCOUNTERED.
Self-explanatory.
Inform customer engineer.
TAF
EDITING COMPLETE.
Informative message.
None.
OMREC
END OF FILE REACHED.
Informative message.
None.
DMREC
END OF VSN TABLE.
DMREC has reached the end of the VSN table
on a LOAD or RECOVER process.
Check the dayfile for
possible tape errors
which may cause this
condition.
DMREC /-rSi§\
ENTER NEXT TRANSACTION.
Option C was selected to allow the entry of
the next transaction. The previous
recoverable information is lost.
Enter next transaction.
RTASK
ERROR IN ACCOUNT/USER CARD ARGUMENT.
The charge or user statement in the xxJ
fi l e i s i n e r r o r.
Correct the charge/user
statement and try again.
DMREC
ERROR IN ADD/DELETE VSN.
The number of added or deleted entries does
not match the number of active files.
Check edit directives
and list the directory
for a visual check.
DMREC
ERROR IN 8RF PARAMETER IN xxJ FILE.
The parameter on the BRF statement is
non-numeric, or the value exceeds the
installation parameter BMAX.
Correct value parameter.
DMREC
ERROR IN BUILDING OIRECTORY ENTRIES.
An error was encountered when DMREC
attempted to add or update a directory
record.
Inform data
a d m i n i s t r a t o r, c o r r e c t
as directed and rerun.
DMREC
(B8E)
ERROR IN BUILDING RECOVERY TABLES.
An error was encountered while attempting
to retrieve a record from the directory
fi l e .
Try an update from an
e a r l i e r fi l e a n d i n f o r m
the data administrator.
DMREC
(BRT)
• 8-8
TAF
S^§\
60459500 C
^eSSRv
MESSAGE
SIGNIFICANCE
ACTION
ROUTINE
DMREC
GRM
ERROR IN BUILDING *RMKDEF* FILE.
DMREC is trying to build a file of RMKDEF
statements to be used in a subsequent
MIPGEN run. An error has occurred in
building the RMKDEF file.
Make sure that RMKDEF
statements are correctly
formatted in the XXJ
file; then rerun the
program.
ERROR IN CRM CARD ARGUMENTS.
The CRM statement in the xxJ file is in
e r r o r.
Correct the CRM
statement and try again.
DMREC
ERROR IN CRM -PUT- (RECORD LOAD).
An error was encountered while attempting
to execute a CRM put onto the data file.
Try to load from
previous dump tape.
OMREC
ERROR IN EDIT PROCESSING.
Editing processor has encountered an error
in trying to execute the directive.
Check the edit directive
parameters and inform
data administrator.
DMREC
ERROR IN IXN CARD ARGUMENTS.
The IXN statement in the xxJ file is in
e r r o r.
Correct the IXN
statement and try again.
DMREC
ERROR IN LIST PROCESSING.
Errors in generating list as described on
directive.
C h e c k l i s t d i r e c ti v e fo r
accuracy and retry.
DMREC
ERROR IN LOADING AAMI.
The loader encountered errors while loading
the TAF CRM AAM interface (AAMI).
The site analyst should
consult the CYBER Loader
Reference Manual (listed
in the preface).
TAF
ERROR IN LOADING HASH CODE filename.
The loader encountered errors while loading
the hashing routine code that is on file
filename.
The site analyst should
consult the CYBER Loader
Reference Manual (listed
in the preface).
ERROR IN LOADING NAM.
The library file NETIO does not contain the
entry points required for TAF.
The site analyst should
consult the CYBER Loader
Reference Manual (listed
in the preface).
TAF
ERROR IN LOADING TOTAL.
The loader encountered errors while loading
Total and the data base descriptor modules
(DBMODs).
The site analyst should
consult the CYBER Loader
Reference Manual (listed
in the preface).
TAF
ERROR IN READING TASKLIB-filename.
Error occurred during transaction executive
initialization or extended memory-resident
task loading. File specified as task
library was incorrectly formatted;
therefore, it could not be read or loaded
into extended memory correctly.
Inform site analyst.
TAF
ERROR IN RECORD DUMP.
During a record dump, DMREC 1s unable to
recognize the first record on the dump file
as an FSTT.
Check structure of file
to be dumped for IS, DA
or AK type and try again.
DMREC
ERROR IN RETRIEVING VSN.
No VSN has been found in the directory that
s a t i s fi e s t h e d i r e c t i v e .
Check directive
parameters. If correct,
inform data
a d m i n i s t r a t o r.
DMREC
ERROR IN SUBMITTED FILE.
An incorrect parameter has been detected on
a SUBMT call from a task.
Correct task or inform
data base administrator.
MSABT
ERROR ON xxJ FILE ARGUMENTS.
The xxJ file contains statements in error,
which causes the transaction subsystem to
abort.
Examine xxJ file.
Inform TAF data
a d m i n i s t r a t o r.
TAF
ERROR STATUS nnnB ON BACKUP DIRECTORY.
CRM error has occurred on directory file.
Inform site analyst.
OMREC
(FER)
ERROR(S) ENCOUNTERED IN OMREC PROCESSING.
Fatal errors were encountered during
processing.
Check the output file
for the detailed error
message.
OMREC
FATAL CIO ERROR STATUS.
A TAF CIO operation returned a fatal error
status which aborted TAF.
Inform site analyst.
TAF
FIELD LENGTH EXCEEOED FOR CMM.
TAF does not have enough field length to
allocate the space potentially required by
CMM.
Increase TAF
i n i t i a l i z a t i o n fi e l d
length.
TAF
FIELD LENGTH EXCEEDED FOR LOCKS.
TAF does not have enough initialization
field length for allocating lock tables.
Decrease the locks
parameter on the CRM
statement, increase the
TA F i n i t i a l i z a t i o n fi e l d
length, or inform site
analyst.
60459500 C
B-9 •
MESSAGE
FIELD LENGTH EXCEEDED FOR RECORD.
SIGNIFICANCE
ACTION
ROUTINE
TAF does not have enough field length to
allocate the space for the record buffer.
D e c r e a s e t h e r e c o r d s i z e TA F
specified in the xxJ
file or increase the TAF
i n i t i a l i z a t i o n fi e l d
length.
FIELD LENGTH EXCEEDED FOR USERS.
TAF does not have enough initialization
fi e l d l e n g t h f o r a l l o c a t i n g fi l e c o n t r o l
tables.
Decrease the users
parameter on the CRM
statement, increase the
TA F i n i t i a l i z a t i o n fi e l d
length, or inform site
analyst.
FILE ATTACH/DEFINE ERROR
An error was detected in attaching or
defining an ARF or BRF.
C h e c k t h e A R F s a n d t h e TA F 1
BRFs for attach mode and
processing mode and
correct if necessary.
xxfilen - FILE, ERROR ON LOCK FUNCTION.
An error occurred while attempting to lock
the specified file. Possible causes are:
- No free file lock table entry (TKOK).
- Another task has file locked.
- Another task has record locked.
Rerun the job at another AAMI
time. If problem
persists, Increase the
number of lock table
entries.
xxfilen - FILE, ERROR ON OPEN FUNCTION.
An error occurred while attempting to open
the specified file. Possible causes are:
- No free file control table entry (TFCB).
- *CRM* error on OPEN function.
- Incorrect key length.
- Incorrect record length.
Correct error. If not
possible, contact site
analyst.
FILE xxJ NOT FOUND.
Transaction subsystem aborts. Data base in
TCF file has no xxJ file, or a PFM error
occurred.
Inform
TA F
data
administrator or site
analyst.
FILE NAME CONFLICT.
The input file name specified on the KTSDMP
command is the same as the output f1le name
s p e c i fi e d .
Correct error and rerun. KTSDMP
FILE NAME MISMATCH ON TAPE HEADER RECORD.
File name on ARF tape and attached ARF
don't match.
C h e c k fi l e n a m e o n A R F D M R E C
tape being used.
FILE NAME MUST BE 2-7 CHARACTERS.
The xxpfni parameter on the CRM statement
must be two to seven characters, the first
two (xx) being the data base name.
Correct
the
xxpfni
parameter on the CRM
statement or inform
data administrator.
FILE NOT ATTACHED - filename.
Either the P or the N parameter file was
not attached when the DA option was used;
filename 1s the permanent file name.
E n s u r e t h a t t h e fi l e i s L I B T A S K
defined or attached
prior to entering the
LIBTASK statement.
FILE hash NOT FOUND.
The Indirect file named hash containing the
binary code of the hashing routine was not
found under the username parameter on the
USER statement in the xxJ file or a PFM
error occurred.
E n s u r e t h a t fi l e h a s h i s T A F
saved under the username
parameter or inform data
a d m i n i s t r a t o r. C o n s u l t
the CYBER Loader Reference
Manual (listed in the
preface).
FILE ORGANIZATION IS NOT IS, DA OR AK.
The file organization parameter on the CRM
statement was not specified as either IS,
DA, or AK.
Correct the CRM
statement and try again.
DMREC
FILE TCF EMPTY.
An empty TCF exists under the TAF user name.
Place the necessary
information on TCF.
TAF
FILE TCF NOT FOUND.
The TCF was not found under the user name
of the Transaction Facility.
Create a TCF f1le under
the TAF user name.
FILE TYPE MUST BE AK, DA, OR IS.
The type parameter on the CRM statement
must be AK (actual key), IS (indexed
sequential) or DA (direct access).
Correct the type
parameter on the CRM
statement or inform the
data administrator.
TAF
FILE TYPE NOT ARF OR BRF.
On a create function a file name was used
that does not conform to the ARF/BRF naming
conventions.
Check file name on
create directive.
OMREC
FL TOO LARGE- nnnnnnB,taskname,tasklibrary.
The initial load field length, nnnnnnB, for
task taskname on task library taskiibrary
exceeds the minimum size of the transient
task area (potential space available to
contain transient tasks). Thus a situation
could arise in which it would not be
possible to load the task.
Correct error.
• 8-10
/^k
TA F
AAMI
TA F
/^sSSs
TA F
60459500
/*-%m>%\
C
)
MESSAGE
ACTION
ROUTINE
TAF
FORMAT ERROR IN THE NETWORK DESCRIPTION
FILE.
During transaction executive
initialization, one or more errors were
found to exist in the network description
fi l e .
Inform site analyst.
FSTT READ ERROR.
No FSTT found on a record load dump tape.
Load from previous tape. DMREC
FWA .GE. LWA+1.
There is a logical error in the structure
of the input file which implies that the
first word address is greater than or equal
to the last word address plus one.
Inform data base administra KTSDMP
GET ERROR ON PF xxxxxxx.
No indirect access permanent file, for use
as an own code file, has been found.
Check for the presence
of the file and try
again.
DMREC
HOST AVAILABLE
CONTROL CHARACTERShar
display
ENTER INPUT TO CONNECT TO HOST
Your selected host is available.
display The host availability
display (HAD), which
appears if you have enabled
it using the HD terminal
definition command.
char The network control
character for your terminal.
Enter any input to
initiate your connection
to the host.
CCP
HOST BUSY CONTROL CHARACTER=char
display
The host rejected your attempt to connect.
display The host availability
display (HAD), which only
appears if you have enabled
it using the HD terminal
definition command.
char The network control
character for your terminal.
Check the status of
the hosts in your
c o n fi g u r a t i o n .
CCP
ENTER char HD TO SEE HOST STATUS
j0^z\
HOST CONNECTED
disp l a y
READY FOR INPUT
CONTROL CHARACTER- char
You are connected to the host.
display The host availability
display (HAD), which
appears if you have enabled
it using the HD terminal
definition command.
char The network control
character for your terminal.
Proceed with your login
to the host.
CCP
HOST CONNECTED
disp l a y
CONTROL CHARACTERShar
The network operator has disabled your
terminal. No further input is possible,
display The host availability
display (HAD), which
appears if you have enabled
it using the HD terminal
definition command,
char The network control
character for your terminal.
None.
CCP
You are connected to the host.
display The host availability
display (HAD), which
appears if you have enabled
it using the HD terminal
definition command.
char The network control
character for your terminal.
Proceed with your login
to the host.
CCP
You have been disconnected from the host.
display The host availability
display (HAD), which
appears if you have enabled
it using the HD terminal
definition command.
char The network control
character for your terminal.
None.
CCP
HOST DISCONNECTED CONTROL CHARACTERS har
di s p l a y
TERMINAL DISABLED 8Y NOP
The network operator has disabled your
terminal. No further input is possible,
display The host availability
display (HAD), which
appears if you have enabled
it using the HD terminal
definition command,
char The network control
character for your terminal.
None.
CCP
HOST NOT AVAILABLE.
NAM is not communicating with the 255x
communications processors. Either NAM was
not initialized or has since failed.
Initialize NAM if it was
not initialized
previously; inform site
analyst if NAM was
active but a malfunction
occurred.
TAF
TERMINAL DISABLED BY NOP
HOST CONNECTED
display
READY FOR INPUT
CONTROL CHARACTERS char
/gp«V
HOST DISCONNECTED CONTROL CHARACTERShar
display
ENTER INPUT TO CONNECT TO HOST
0^*
c
SIGNIFICANCE
60459500 C
B-11 •
MESSAGE
SIGNIFICANCE
ACTION
ROUTINE
Yo u h a v e a t t e m p t e d a c o n n e c t i o n t o a h o s t
that is not up.
display The host availability
display (HAD), which
appears if you have enabled
it using the HD terminal
d e fi n i t i o n c o m m a n d ,
char The network control
character for your terminal.
Check the status of
the hosts in your
c o n fi g u r a t i o n .
CCP
IGNORE TABLE OVERFLOW,
Ignore table, TTIG, is too small.
Inform site analyst to
enlarge TTIG table.
OMREC
xx ILLEGAL COMMAND
The characters xx must be a terminal
d e fi n i t i o n m n e m o n i c o r i n t e r a c t i v e s t a t u s
command.
Ensure the accuracy of
your entry and retry.
CCP
ILLEGAL DATA BASE IN xxJ FILE.
O n e o f t h e s t a t e m e n t s i n t h e x x J fi l e
s p e c i fi e s a n i n c o r r e c t x x p a r a m e t e r a n d
causes the transaction subsystem to abort.
Examine xxJ files.
Inform the TAF data
a d m i n i s t r a t o r.
TAF
ILLEGAL FL REDUCTION.
Ta s k r e q u e s t t o r e d u c e F L w o u l d c a u s e t h e
last word address of the communication
block to be outside the task FL.
Inform data
a d m i n i s t r a t o r.
MSABT
ILLEGAL JOURNAL FILE REQUEST.
Either a task requested that an entry be
m a d e o n a n u n d e fi n e d TA F j o u r n a l fi l e , o r
the task attempted to make an entry longer
t h a n 2 4 9 9 C M w o r d s o n a TA F j o u r n a l fi l e .
Inform data base administra
MSABT
ILLEGAL KEY BEGINNING CHARACTER.
The ke y o ff s e t p a r a m e t e r o n a n A K Y
s t a t e m e n t i n t h e x x J fi l e , i s m i s s i n g o r
incorrect.
Correct AKY command.
TAF
(AKY)
ILLEGAL KEY ORDINAL.
The key ordinal parameter on the AKY
statement is missing or incorrect.
Correct AKY statement.
TAF
(AKY)
ILLEGAL LIBTASK ATTEMPT - filename,
username.
The transaction executive validates all
dynamic attempts to change the task library
by comparing the user name of the requester
against the list of data base user names.
If it does not match, or if the library
fi l e 1 s n o t a t t a c h e d b y TA F, t h e
t r a n s a c t i o n e x e c u t i v e i s s u e s t h i s d a y fi l e
message, where username is the user name of
the incorrect attempt.
Correct and reinitialize
transaction executive.
TAF
ILLEGAL NUM8ER FOR LOCKS.
The locks parameter on the CYBER Record
M a n a g e r ( C R M ) s t a t e m e n t 1 s I n e r r o r. O n e
of the following format conditions exists.
- A n o n n u m e r i c c h a r a c t e r.
- A character after a postradix of B or D.
- An 8 or 9 with a postradix of B.
Correct the locks
parameter on the CRM
statement or inform the
analyst.
TAF
ILLEGAL NUMBER FOR USERS.
The user's parameter on the CRM statement
i s i n e r r o r. O n e o f t h e f o l l o w i n g f o r m a t
conditions exists.
- A n o n n u m e r i c c h a r a c t e r.
- A character after a postradix of B or D.
- An 8 or 9 with a postradix of B.
Correct the user's
parameter on the CRM
statement or inform the
data administrator.
TAF
ILLEGAL NUMBER OF ALTERNATE KEYS.
The number of alternate keys on the IXN
statement is missing or incorrect.
Correct IXN statement.
TAF
(IXN)
ILLEGAL PARAMETER IN RA+1 CALL.
A t a s k e r r o r . T h e p a r a m e t e r s s p e c i fi e d i n
a request from a task are either
i n s u f fi c i e n t o r i n c o r r e c t .
Correct task or inform
data base administrator.
MSABT
ILLEGAL TASK NAME REQUESTED FOR SCHEDULING,
The task requested was not found in the
t a s k l i b r a r y d i r e c t o r y.
Correct task or inform
data base administrator.
MSABT
cmd ILLEGAL TERMINAL CLASS
T h e v a l u e y o u s p e c i fi e d i n t h e t e r m i n a l
d e fi n i t i o n c o m m a n d c m d i s n o t v a l i d f o r
your terminal.
Choose an appropriate
value (refer to appendix
J).
CCP
ILLEGAL TERMINAL INPUT REQUEST.
A t a s k e r r o r. A W A I T I N P r e q u e s t w a s i s s u e d
by a memory resident task or by a task that
did not originate from a terminal.
Correct task or inform
data base administrator.
MSABT
cmd ILLEGAL VALUE
Yo u s p e c i fi e d a n i n v a l i d v a l u e i n t h e
t e r m i n a l d e fi n i t i o n c o m m a n d c m d .
Choose a valid value
(refer to appendix J).
CCP
INACTIVE TASK REQUESTED.
An attempt was made to schedule a task
which has been turned off with a K.OFFTASK
command or a LIBTASK directive.
Correct condition or
inform site analyst.
OFFTASK
INCOMPLETE PARAMETER.
A parameter on a DMREC directive was not
c o m p l e t e d c o r r e c t l y.
Correct the parameter on
the faulty directive.
DMREC
HOST UNAVAILABLE CONTROL CHARACTERShar
display
ENTER char HD TO SEE HOST STATUS
• B-12
60459500 C
MESSAGE
ACTION
SIGNIFICANCE
ROUTINE
One of the following errors occurred:
1. A command was entered other than what
was on the menu.
2 . A t e r m i n a l C R M S TAT r e q u e s t d i d r o t
request its own data base.
Ensure that the command
is correct. If problem
persists, inform the
site analyst.
CRMTASK
INCORRECT COMMON MEMORY MANAGER REQUEST.
Memory request with reserved bits in the
parameter block set incorrectly.
Do not set reserved bits.
MSABT
INCORRECT FAMILY NAME IN EOT.
Self-explanatory.
Reinitialize the
transaction executive or
inform the site analyst.
TAF1
INCORRECT FWA FOR LOAD.
The FWA of the load was not equal to 1118.
Task binaries must be in absolute format.
Ensure that the correct
load procedure is
performed.
LIBTASK
INCORRECT POSITION IN THE DIRECTORY.
The directory structure is inconsistent or
positioning is incorrect.
Inform data
a d m i n i s t r a t o r.
DMREC
(GPL)
INCORRECT SU8-TRANSACTI0N CODE - INITIAL TASK.
There is an unrecognizable subtransaction
code in the terminal input.
Correct terminal input
or inform data base
a d m i n i s t r a t o r.
MSABT
INCORRECT TOTAL INTERLOCK REQUEST.
One of the following.
Inform data base
a d m i n i s t r a t o r.
MSABT
Correct task or inform
data base administrator.
MSABT
INCORRECT COMMANO.
3. A terminal origin job tried to request
the menu.
4. Unpack errors on the terminal message.
- A task that is not on the system task
library issued a CHKON request.
- A task issued a CHKON request with a
CHKON request already in effect.
- A task issued a CHKOFF request without
fi r s t i s s u i n g a C H K O N r e q u e s t .
- A task that issued a CHKOFF request had
a sequence number different from a task
that issued a CHKON request.
INCORRECT WORD COUNT ON TERMINAL OUTPUT.
One or more of the following task errors
occurred on a SEND request.
- The word count was less than or equal to
zero.
- There was an attempt to use SEND MAXWS
or more CM words of information in one
SEND; MAXWS is an installation option.
- There was an attempt to use SEND MAXTO
or more CM words of information by one
task through a series of SEND requests.
MAXTO is an Installation option.
INITIAL TASK NOT IN TASK LI8RARY DIRECTORY.
The task library file does not contain the
i n i t i a l t a s k ( I TA S K ) .
Inform site analyst.
TAF
INITIALIZATION OPTIONS.
This message precedes messages indicating
the values of the initial K display options
e i t h e r d u r i n g i n i t i a l i z a t i o n o r r e c o v e r y.
None.
TAF
INPUT DISCARDED
The network has discarded the last input
from your terminal. May be caused by
entering a user break or interactive status
command while awaiting a response to a
previous user break or interactive status
command.
Reenter your last input.
CCP
INPUT DISCAROED
The system has discarded user input.
Reenter input.
TAF1
INSUFFICIENT FIELD LENGTH FOR THIS COMMAND.
CRMTASK issued a CRMSTAT request but AAMI
was not able to complete it because the
table area supplied by the user was not
large enough.
Inform data base
a d m i n i s t r a t o r.
CRMTASK
INSUFFICIENT FL FOR DATA MANAGER.
The transaction executive requires more
fi e l d l e n g t h a t i n i t i a l i z a t i o n t i m e t h a n i s
avallable.
Correct error and
reinitialize executive.
TAF
INTERMEDIATE IGNORE TABLE OVERFLOW.
Intermediate ignore table FTAB is too
small. Too many potentially recoverable
files have been encountered when reading
ARF's.
Inform site analyst to
enlarge table FTAB.
OMREC
(BRT)
INVALID DATA BASE NAME ON DMS STATEMENT.
A data base name associated with TAF, CRM,
or OTHER exceeds two characters.
Correct the DMS
statement on TCF file.
TAF
INVALID DATA MANAGER PARAMETER
An error has been detected in the parameter
list on a data manager request.
Correct the data manager
request statement.
MSABT
/#^
60459500 C
B-13 •
MESSAGE
INVALID TASK NAME.
ACTION
SIGNIFICANCE
The error message was issued for one of the
following reasons:
- Initialization of a task by the name of
ROUTINE
Correct the task name.
XTASK
BTASK, CTASK, ITASK, KDIS, MSABT,
OFFTASK, RCTASK, RTASK, SYSMSG, or XTASK
w a s a t t e m p t e d u s i n g X TA S K . T h e s e a r e
names of required system tasks and will
n o t b e i n i t i a t e d b y X TA S K .
- A z e r o l e n g t h t a s k n a m e w a s s p e c i fi e d .
- A task name of more than seven
c h a r a c t e r s w a s s p e c i fi e d .
INVAHO TCF ENTRY.
T h e p r e v i o u s d a y fi l e m e s a g e i s t h e
statement in TCF which is incorrect.
Correct that statement
i n T C F.
TAFREC
INVALID TRANSACTION DIRECTORY HEADER
fi l e n a m e .
The transaction directory (TRD) header word
is not TRD.
I n f o r m TA F s i t e a n a l y s t .
TAF
filenam IS INCONSISTENT.
T h e i n c o n s i s t e n t fi l e b i t i s s e t f o r
r e c o v e r a b l e fi l e , fi l e n a m . T h i s i n d i c a t e s
a f a i l u r e ( e i t h e r o f TA F o r t h e s y t e m )
occurred while CRM was trying to update
more than one block. All of the blocks may
not have been updated and this would cause
t h e fi l e t o b e fl a g g e d a s i n c o n s i s t e n t .
It is necessary to
recover the affected
fi l e . A A M I w i l l s u b m i t
an OMREC job to do this.
AAMI
xxJ FILE ERROR - CRM DM NOT LOADED.
A data manager related statement is
s p e c i fi e d i n t h e x x J fi l e b u t t h a t d a t a
manage r 1 s n o t l o a d e d o n t o TA F.
Inform site analyst to
change the xxJ or TCF
fi l e .
TAF
xxJ FILE ERROR - TAF DM NOT LOADED.
A data manager related statement is
s p e c i fi e d i n t h e x x J fi l e b u t t h a t d a t a
manager 1s not loaded on to TAF.
Inform site analyst to
change the xxJ or TCF
fi l e .
TAF
xxJ FILE ERROR - TOTAL DM NOT LOADED.
A data manager related statement is
s p e c i fi e d i n t h e x x J fi l e b u t t h a t d a t a
manager 1s not loaded on to TAF.
Inform site analyst to
change the xxJ or TCF
fi l e .
TAF
xx J FILE NOT FOUND.
When using the TAF's user name and
p a s s w o r d , a n x x J fi l e f o r t h i s d a t a b a s e
was not found.
E n s u r e x x J fi l e e x i s t s
for this data base and
try again.
DMREC
JOURNAL TYPE DOES NOT MATCH xxJ FILE.
T A F j o u r n a l fi l e e n t r i e s i n t h e x x J fi l e d o
n o t m a t c h t h e fi l e s t h e m s e l v e s . T h i s
causes the transaction subsystem to abort.
I n f o r m TA F d a t a
a d m i n i s t r a t o r. E x a m i n e
x x J fi l e f o r t h e T A F
j o u r n a l fi l e e n t r i e s .
TAF
K.BFL=n.
K.CMB=nn.
K.£CS=nrmK.
K.ERO-a.
K.ERO=CRF,xxx.
K.INT=1.
K . I N T = C R F, x x x x x x x .
K. INT =CRM, xxxx.
K.MDM=n.
K.MFL=nnnnnnB.
K.REC=a.
K.SCP=nn.
K.TLF=a.
Va l u e s o f t h e i n i t i a l K d i s p l a y o p t i o n s a t
e i t h e r i n i t i a l i z a t i o n o r r e c o v e r y.
None.
TAF
K. COMMAND NOT VALID.
A K . c o m m a n d i n t h e T C F fi l e i s i m p r o p e r l y
formatted.
Correct the statement in
the TCF or inform the
TA F a n a l y s t .
TAF
K-DISPLAY COMMAND UNSUCCESSFUL, DROP
IGNORED—-command.
A K.DROP or K.DDROP could not be processed
because the task was in recall, the
interactive executive denied a request, or
a command was issued during the initial
l o a d o f t h e t a s k . T h e c o m m a n d fi e l d i s t h e
attempted command or request; blanks
indicate no command was issued.
Reenter the K.DROP or
K.DDROP command. When
the recall operation,
time-sharing request, or
initial load operation
i s c o m p l e t e d , TA F
accepts the command and
aborts the task.
SYSMSG
K-DISPLAY COMMAND UNSUCCESSFUL, FORMAT
ERROR—command.
There is an error in the syntax of the
command or in one of the parameters. The
c o m m a n d fi e l d i s t h e a t t e m p t e d c o m m a n d o r
blanks if the command is longer than seven
characters or contains an incorrect
c h a r a c t e r.
Correct the command and
retry the operation.
SYSMSG
K-DISPLAY COMMAND UNSUCCESSFUL, ILLEGAL
COMMAND— comm and.
The command is not a valid K display
command or was misspelled. The command
fi e l d i s t h e a t t e m p t e d c o m m a n d .
Correct the command and
retry the operation.
SYSMSG
K DISPLAY COMMAND UNSUCCESSFUL, SYSTEM
BUSY—command.
The system is busy and cannot respond to
t h e r e q u e s t . T h e c o m m a n d fi e l d i s t h e
attempted command.
Retry the operation.
SYSMSG
• B-14
60459500 C
MESSAGE
ji^s
ACTION
SIGNIFICANCE
ROUTINE
K.MAXFL,nnnnnnB.
The run-time K display command K.MAXFL was None,
entered with the indicated value.
TAF
K.MAXFL REJECTED.
A value was entered which caused potential
blocked tasks to be detected.
Reenter K.MAXFL with a
larger value.
TAF
KEYWORO IS ILLEGAL FOR THIS FUNCTION.
A keyword was used that is not valid for
the selected directive.
Check format of
directive and valid key
words for that directive.
OMREC
n.nnn KILO CDCS REQUEST REJECTS FOR BUSY.
To t a l n u m b e r o f S S C r e j e c t s f o r b u s y w h e n
less than seven outstanding CDCS SSC
requests existed at the time of the current
request.
None.
TAF
n.nnn KILO CDCS REQUEST REJECTS FOR MAXR.
To t a l n u m b e r o f S S C a t t e m p t s w h e n t h e r e
were seven (MAXR) outstanding CDCS SSC
requests.
None.
n.nnn KILO CDCS REQUESTS FROM TASKS,
Total number of CDCS SSC requests issued by
tasks. The number does not include
t e r m i n a t e r e q u e s t s w h i c h a r e b l o c k e d b y TA F.
None.
TAF
n.nrm KILO ITASK RELOADS.
Upon transaction facility termination, this
m e s s a g e i n d i c a t e s h o w m a n y r e l o a d s o f I TA S K
o c c u r r e d . B e c a u s e I TA S K i s a c e n t r a l
memory resident task, if it makes a fatal
e r r o r, i t m u s t b e r e l o a d e d .
Inform site analyst.
TAF
n.nnn KILO LOCK REJECTS-filename.
TA F C R M c o u l d n o t l o c k r e c o r d s i n fi l e n a m e
for a task because the locks parameter on
t h e C R M s t a t e m e n t f o r t h a t fi l e w a s n o t
large enough.
The site analyst should
consider increasing the
locks parameter on the
CRM statement if lock
failures occur
f r e q u e n t l y.
TAF
n.nnn KILO LOCKS-filename.
TA F C R N p r o c e s s e d n n n n l o c k s f o r fi l e
fi l e n a m e .
None.
TAF
n.nnn KILO NO COMMUNICATION BLOCKS.
Upon transaction facility termination, this
message indicates the number of times a
communication block was needed and was not
available.
Inform site analyst.
The site analyst might
want to consider using
the K.CMB command during
TA F I n i t i a l i z a t i o n .
TAF
n.nm KILO NO FL FOR TASK LOAD.
Upon transaction facility termination, this
m e s s a g e i n d i c a t e s t h e n u m b e r o f t i m e s TA F
was unable to obtain enough memory to load
tasks.
Inform site analyst.
The site analyst might
want to consider using
the K.MFL command during
TA F i n i t i a l i z a t i o n .
TAF
n.nnn KILO NO SUBCONTROL POINTS.
Upon transaction facility termination, this
message indicates the number of times a
subcontrol point area was needed and was
not available.
Inform site analyst.
The site analyst might
want to consider using
the K.SCP command during
TA F i n i t i a l i z a t i o n .
TAF
n.nnn KILO OPEN REJECTS-filename.
TA F C R M c o u l d n o t o p e n fi l e fi l e n a m e f o r a
task because the user's parameter on the
CRN statement is not large enough.
The site anlayst should
consider increasing the
users parameter on the
CRM statement if open
failures occur
f r e q u e n t l y.
TAF
n.nnn KILO OPENS-filename.
TA F C R N p r o c e s s e d n n n n o p e n s f o r fi l e
f1lename.
None.
TAF
n.nnn KILO STORAGE MOVES OF TASKS.
Upon transaction facility termination, this
message indicates the number of subcontrol
points that were moved. This is done to
m a k e m o r e e f f e c t i v e u s e o f t h e fi e l d l e n g t h
O f TA F.
None.
TAF
n.nnn KILO TAF FL INCREASES.
Upon transaction facility termination, this
m e s s a g e i n d i c a t e s t h e n u m b e r o f t i m e s TA F
i n c r e a s e d i t s fi e l d l e n g t h w h i l e t r y i n g t o
satisfy an internal request for a block of
m e m o r y. T h i s i n t e r n a l r e q u e s t i s o f t e n
issued to obtain memory in which to load a
task.
None.
TAF
n.nnn KILO TASK RECALLS.
Upon transaction facility termination, this None,
message indicates the number of times tasks
were put in recall. This is an internal
statistic over which the applications
programmer has little control.
TAF
j d P ^
60459500 C
B-15 •
MESSAGE
SIGNIFICANCE
ACTION
ROUTINE
n.nnn KILO TASK RECALLS FOR OUTPUT.
Upon transaction facility termination, this
message indicates the number of times tasks
were put in recall because the network
block limit (NBL parameter on a TERMINAL
statement) for the terminal in use was
reached.
Refer to the Network
Access Method Network
Definition Language
Reference Manual (listed
in the preface).
TAF
n.nnn KILO TASK RELOADS.
Upon transaction facility termination, this
message indicates how many reloads of tasks
occurred. TAF reloads tasks that have
fatal errors if one of the following is
true.
- The task is central memory resident.
- There are queued transactions waiting to
use the task.
Inform site analyst.
TAF
n.nnn KILO TASK ROLLOUT COMPLETES.
Upon transaction facility termination, this
message indicates the number of times TAF
rolled out tasks. This statistic excludes
the number of times the rollout operation
did not complete.
None.
TAF
n.nnn KILO TASK ROLLOUT STARTS.
Upon transaction facility termination, this
message indicates the number of times TAF
initiated a rollout operation. Rollout
includes writing a task to disk and
releasing the task subcontrol point space.
In some cases, the task is allowed to stay
central memory resident for a while before
it is rolled out.
None.
TAF
n.nnn KILO TRANSACTION ABORTS.
Upon transaction termination, this message
indicates how many transaction tasks have
aborted.
Data administrator may
have to correct data
base to account for
transactions.
TAF
n.nnn KILO TRANSACTIONS PROCESSED.
Upon TAF termination, this message
indicates the number of TAF transactions
processed.
None.
TAF
KL PARAMETER OR CRM CARD NOT SPECIFIED
PROPERLY.
The KL parameter or the CRN statement was
specified improperly or specified as zero
length.
Correct the CRM
statement and try again.
DMREC
KTSDMP COMPLETE.
Dump completed normally.
None.
KTSDMP
LBL - CIO ERROR.
A CIO error was encountered because no
trailer record was found on a block load.
Load from previous dump
tape.
DMREC
LIBRARY DIRECTORY EMPTY - filename.
The task library file Indicated does not
contain a directory.
Inform site analyst.
TAF
LIBRARY DIRECTORY ERROR - filename.
The task library file indicated contains a
nonrecognizable directory.
Inform site analyst.
TAF
LIBRARY DIRECTORY TOO LONG - filename.
The directory record on the task library
file Indicated exceeded the maximum length
allowed by the transaction executive (398
entries).
Inform site analyst.
TAF
LIBRARY FILE TIME OUT.
The library file was busy for the length of
time specified by an assembly constant, so
LIBTASK was unable to attach it. Another
user apparently has the file attached and
will not allow modification.
Retry at a later time.
LIBTASK
LIBTASK ERROR CONDITION UNKNOWN.
The error condition for the error
processing routine ERR within LIBTASK was
unknown.
Inform data base administra
LIBTASK
LIBTASK PFM ERROR DETECTED.
A permanent file error other than FILE BUSY
was received when the library file attach
was attempted.
Correct and rerun.
LIBTASK
LIST COMPLETE.
Informative message.
None.
DMREC
LOAD ERROR IN HASHING ROUTINE.
When attempting to load the hashing routine
on a record load operation, a load error or
no entry point in the hashing routine was
found.
Check for valid hashing
routine, inform analyst.
OMREC
LOADING ECS taskname.
Informative message. The transaction
subsystem is loading task taskname.
None.
TAF
LOG ENTRY TABLE OVERFLOW.
Too many recoverable data base file names
exist on ARF.
Increase size of table
(TLOG).
OMREC
(8LT)
• B-16
60459500
/^^\
C
1
SIGNIFICANCE
MESSAGE
ACTION
ROUTINE
MAXIMUM TERMINALS EXCEEDED.
More than IPTST transaction terminals have
been defined in the Network File(s).
Reduce number of
t e r m i n a l d e fi n i t i o n
statements or increase
IPTST and reassemble
TAFREC.
TAFREC
MEMORY OVERFLOW DURING INITIALIZATION.
TAF aborted because its field length for
i n i t i a l i z a t i o n w a s i n s u f fi c i e n t .
Inform site analyst.
IFL- in deck TAF should
be increased.
Increasing the central
memory field length
parameter on the RFL
command in the TAF
initialization procedure
fi l e ( f f f f ) d o e s n o t
correct this problem.
TAF
MEMORY REQUEST FOR ECS NOT ALLOWED.
Incorrect request of extended memory by
task.
Contact data
a d m i n i s t r a t o r.
MSABT
MEMORY REQUEST WITH D.M.
REQUEST OUTSTANDING.
A task error. MEM or RFL request attempted
with data manager requests outstanding.
Correct task or inform
data base administrator.
MSABT
NFL TOO LARGE nnnnnnB,taskname,task library.
The MFL (initial field length plus
expandable field length) of the non-CN
resident task (taskname) on task library
(tasklibrary) exceeds the minimum size of
the transient task area (potential space
available to contain transient tasks).
Thus a situation could arise in which it
would not be possible to complete
processing of this task.
Reduce the task FL or
EF, or increase the TAF
FL.
TAF
Potentially blocked tasks were detected at
one of the following times:
C o r r e c t e r r o r.
TAF
0^^
MINIMUM TAF MFL NEEDED = nnnnnnB.
- TAF initialization
- Attempted task library update
- Attempt to change TAF maximum FL via
K.MAXFL command
The above operation did not complete
normally. The maximum FL of TAF must be at
least nnnnnnB. If nnnnnnB exceeds the
largest field length possible for TAF
(377700B), then other corrective action is
needed.
J ^ v
MISSING AKY CARD.
Number of AKY statements does not match
number of alternate keys on IXN statement.
Nod ify the IXN statement
or adjust the number of
AKY statements so the
two match.
TAF
(XXJ)
MISSING HEADER WORD ON xxJ FILE.
The first statement on the xxJ file is in
error, causing the transaction subsystem to
abort.
Examine xxJ files for
header xxJ. Inform the
TAF data administrator.
TAF
MISSING HEAOER WORD ON XXJ FILE.
No header word on xxJ was found.
Correct xxJ file and
rerun.
DMREC
MORE THAN FIVE TASKS IN TASK CHAIN.
A task error. Only five tasks can be
requested for scheduling in one CALLRTN,
CALLTSK, or NEWTRAN request; more than five
were requested.
Correct task or inform
data base administrator.
MSABT
MORE THAN ONE ARF SPECIFIED.
More than one ARF was specified on the DUMP
directive.
Correct the directive
and rerun.
DMREC
MORE THAN ONE ENTRY POINT ON A *54* TABLE.
Multiple entry points are not allowed in
tasks.
Rewrite the task with
only one entry point.
LIBTASK
MORE THAN ONE USER STATEMENT IN TCF.
S e l f - e x p l a n a t o r y.
Delete the extra
USER statement.
TAFREC
MRL PARAMETER ON CRM CARD NOT SPECIFIED
PROPERLY.
The MRL parameter on the CRM statement was
specified improperly or specified as zero
length.
Correct the CRN
statement and try again.
DMREC
NS REDUCTION INVALID - filename.
The maximum message size, specified via the
MS parameter on the RECOVER directive, was
less than the actual message record size on
the named CRF.
Correct the RECOVER
directive or select
initialization of the
named CRF via the K.INT
initial K display
command if reducing the
message size is actually
required. (Note that
K.INT will destroy the
current recovery
information).
TAFREC
yf$$ft\
/0^~
60459500 C
B-17 •
ACTION
SIGNIFICANCE
MESSAGE
ROUTINE
MSABT CALL ERROR.
MSABT was called with an incorrect error
code.
Inform data base
a d m i n i s t r a t o r.
MSABT
NAKY PARAMETER ON THE IXN CARD NOT SPECIFIED
PROPERLY.
The NAKY parameter is not specified
properly or of 2ero length.
Correct the IXN
statement and try again.
DMREC
NAM ERROR - ILLOGICAL ABT.
The application block type (ABT) sent to
TAF by NAM is unrecognizable.
Contact Central Software
Support.
TAF
NAM ERROR - INCORRECT ABH.
The application block header (ABH) sent to
TAF by NAM is unrecognizable.
Contact Central Software
Support.
TAF
NAM FUNCTION NOT FOUND.
TAF received a supervisory message from NAM
which had an unrecognizable primary or
secondary function code.
Contact Central Software
Support.
NAM LOGICAL ERROR.
NAM sent TAF a message out of order or an
unrecognizable message.
Contact Central Software
Support.
TAF
NAM NOT AVAILABLE.
Informative message indicating that TAF is
currently at a control point but NAM is
not. TAF transactions can be initiated
from batch only, or TAF-CRM data bases may
be accessed from batch or interactive jobs.
Bring NAM to a control
point, if desired.
TAF
NAM PHYSICAL ERROR EC=ec.
NAM has detected a physical error indicated
by error code ec.
Refer to the NAM
Reference Manual for the
meaning of this error
code.
TAF
NAM REJECT.
During login processing, NAM rejected the
terminal.
Inform site analyst.
TAF
NEED AT LEAST xx SUBCONTROL POINTS.
There are more CN resident tasks defined
than subcontrol points. If non-CM resident
tasks exist, there must be at least one
more subcontrol point than there are CN
resident tasks.
Reinitialize the
transaction executive
and assign more
subcontrol points, or
reduce the number of CM
resident tasks.
TAF
NETOFF COMPLETE.
Informative message indicating that TAF is
no longer communicating with NAN. NAN
initiated shutdown procedures prior to loss
of communications.
When NAN is available,
the central site console
operator command K.NAMON
can be used to resume
communications between
TAF and NAM.
TAF
NETON COMPLETE.
Informative message indicating that TAF is
communicating with NAN.
None.
TAF
NETWORK FILE NOT FOUND - filename.
The network description file, NCTFI, could
not be found.
Check that correct
parameters were
specified on the NETWORK
directive corresponding
to filename.
TAF
TAFREC
NETWORK SHUT DOWN DETECTED.
Self-explanatory.
None.
TAF
NM REDUCTION INVALID - filename.
The maximum number of user messages,
specified by the NM parameter on the
RECOVER directive, was less than the actual
number of user messages on the named CRF.
Correct the RECOVER
directive or select
initialization of the
named CRF via the K.INT
initial K display
command if reducing the
number of user messages
is actually required.
(Note that K.INT will
destroy the current
recovery information).
TAFREC
NO ACCOUNT/USER CARD IN xxJ FILE.
The USER statement in the xxJ file is not
present, causing the transaction subsystem
to abort.
Add USER statement in
x x J fi l e . I n f o r m t h e
TAF data administrator.
TAF
NO ACCOUNT/USER CARD ON XXJ FILE.
No user statement exists on the xxJ file.
Correct the xxJ file and
rerun.
DMREC
(CXJ)
NO ALTERNATE KEY SPECIFIED ON IXN CARD.
Self-explanatory.
Correct the IXN
statement and try again.
DMREC
NO ARF DUMP ENTRIES - DUMP IGNORED.
When trying to build directory entries for
an ARF dump function, no ARF file was found.
Include ARF file name on
dump.
DMREC
NO ARF DUMP ENTRIES IN DIRECTORY.
A search of the directory for the targeted
VSNs of ARF tapes was unsuccessful.
Check time and data or
VSN used to delineate
update.
DMREC
• 8-18
60459500
/s^v
C
1
NESSAGE
0r*«
SIGNIFICANCE
ACTION
ROUTINE
NO 8RF CARD FOR CRN DATA BASE.
There is no BRF statement in the xxJ file
before the first CRM statement for the data
base.
A BRF statement is
required. If no
recovery is desired, the
n u m b e r o f s p e c i fi e d
fi l e s o n t h e B R F s h o u l d
be zero.
TAF
NO BRF CARD FOUND IN xxJ FILE.
There is no BRF statement in the xxJ file
for the data base.
A BFF card is required
and must be added to the
x x J fi l e .
DMREC
NO CRM CARD FOUND IN xxJ FILE.
S e l f - e x p l a n a t o r y.
Correct the CRN
statement and try again.
DMREC
NO DATA BASE ID FOR DATA MANAGER.
A t l e a s t o n e d a t a b a s e i d e n t i fi e r m u s t b e
s p e c i fi e d o n e a c h a c t i v e ( O N ) D M S s t a t e m e n t .
A d d d a t a b a s e i d e n t i fi e r
to DNS statement(s) or
s p e c i f y s t a t u s a s O F F.
TAF
NO DATA BASE NAME IN xxJ FOR TOTAL.
S e l f - e x p l a n a t o r y.
Add data base name to
x x J fi l e .
NO DIRECTIVES.
No directives were supplyed to DMREC.
Supply the correct
directives and rerun.
DNREC
NO DUMP RECORD WITH SPECIFIED VSN.
DMREC could not locate a dump record with
t h e s p e c i fi e d V S N .
Check directory with
list directive for
proper VSN.
DMREC
NO FILE NAME SPECIFIEO ON CRM CARD.
A C R M s t a t e m e n t i n t h e x x J fi l e d i d n o t
c o n t a i n a fi l e n a m e .
C o r r e c t t h e x x J fi l e a n d
try again.
DNREC
NO FILE NAME SPECIFIED ON IXN CARD.
T h e x x J fi l e h a s a n I X N s t a t e m e n t t h a t d o e s
n o t c o n t a i n a fi l e n a m e .
Correct IXN statement on
x x J fi l e a n d r e r u n .
DMREC
(RXJ)
NO FILES TO DUMP.
N o fi l e s h a v e b e e n s p e c i fi e d o n a d u m p
directive.
I n c l u d e fi l e n a m e o n
directive.
DMREC
NO HOSE CONNECTED.
YOU HAVE ENTERED A (ct)TM COMMAND WHEN
THERE IS NO HOST CONNECTION.
Enter (ct)HD to display
host status and then
enter (ct)HN=nn or =mm
to connect to the
selected host.
RTN?
NO HOST AVAILABLE CONTROL CHARACTERShar
display
No hosts are available.
display The host availability
display (HAD), which
appears if you have enabled
it using the HD terminal
d e fi n i t i o n c o m m a n d .
char
The
network
control
character for your terminal.
Check the status of
the hosts in your
c o n fi g u r a t i o n .
CCP
NO HOST CONNECTED CONTROL CHARACTERS har
di s p l a y
Yo u h a v e a t t e m p t e d t o d i s c o n n e c t y o u r
terminal from a host when you have no
connection to a host.
display The host availability
display (HAD), which only
appears if you have enabled
it using the HD terminal
d e fi n i t i o n c o m m a n d .
Enter a HD terminal
d e fi n t i o n c o m m a n d t o
determine the status of
hosts in the system, or
enter any input to
initiate your connection
to the host.
CCP
NO HOST SELECTED CONTROL CHARACTERshar
display
ENTER char HN=NOD6 NUMBER or
HS=NAME TO SELECT HOST
Yo u h a v e n o t s e l e c t e d a h o s t a n d a h o s t i s
available.
display The host availability
display (HAD), which
appears if you have enabled
it using the HD terminal
d e fi n i t i o n c o m m a n d ,
char
The
network
control
character for your terminal.
Select a host.
CCP
NO KEY LENGTH SPECIFIED ON CRM CARD.
The KL parameter on the CRM statement was
n o t s p e c i fi e d .
Correct the CRM
statement and try again.
DNREC
NO MAXIMUM RECORD LENGTH SPECIFIED ON THE
CRM CARD.
The MRL parameter on the CRM statement was
n o t s p e c i fi e d .
Correct the CRN
statement and try again.
DNREC
NO RECORD FOUND FOR GIVEN VSN - DATE/TIME.
T h e fi l e s p e c i fi e d o r i m p l i e d o n t h e l o a d
c a n n o t b e f o u n d o n t h e d i r e c t o r y.
Check load directive for
c o r r e c t fi l e l o a d i n g
parameters.
DMREC
NO SPACE FOR ARF/BRF BUFFER.
No space was available for an ARF or BRF
buffer.
Increase field length of
ONREC.
DMREC
ENTER char HD TO SEE HOST STATUS
ENTER INPUT TO CONNECT TO HOST
/^^
60459500 C
B-19 •
ACTION
SIGNIFICANCE
MESSAGE
ROUTINE
NO TERMINALS IN NETWORK FILE - filename.
A valid network file was found but no
transaction terminals were defined in
Ensure the network file
is correctly named. The
network file is NCTFi
(i=id speci fied on
network directive in
TCF).
TAFREC
NO TRANSACTION NAME IS DEFINED IN TASK
LIBRARY.
No named transaction appears in any task
l i b r a r y.
I f a p p r o p r i a t e , d e fi n e
named transactions.
TAF
NOT ALL DATA BASE FILES UPPED.
CRMTASK issued a DBUP request but AAMI was
unable to attach/open all of the data base
fi l e s .
Inform data base
a d m i n i s t r a t o r.
CRMTASK
NOT AVAILA8LE.
K display message indicating that the entry
is not available for this version.
None.
TAF
filename NOT FOUND.
The user specified the P option on the
KTSDMP command; one of the two files was
not in the user's permanent file catalog or
a PFM error occurred.
S p e c i f y a d i f f e r e n t fi l e
name or inform a site
analyst.
KTSDMP
xxxxxxx NOT FOUND IN DIRECTORY,
Specified file 1s not found in the
d i r e c t o r y.
Check the file name and
t h e l i s t d i r e c t o r y.
DMREC
xxxxxxx NOT IN DIRECTORY.
Error - The task or named TAF transaction
unit, xxxxxxx, was specified in the TN
parameter but was not found on the task
library or transaction unit directory.
Ensure the correct task
or transaction name was
specified with the TN
parameter. Check task
or transaction listing
for presence of
s p e c i fi e d u n i t .
TAF
S^^\
xxxxxx NOT INITIALIZED BY TOTAL.
STATUS IS yyyy.
An error was encountered on the TOTAL data
base.
Regenerate TOTAL data
base. Refer to TOTAL
Reference Manual for
status.
TAF
NOTE FAILURE, THEN TYPE IN CFO, JSN. GO.
An error occurred that requires operator
n o t i fi c a t i o n .
The operator should log
the failure, or notify
the data base
administrator and/or
correct as directed, if
the error was not
recovered by DMREC.
DMREC
NULL DESCRIPTION FILE.
Self-explanatory.
Create a description
file (NCTF1 where 1 is
the machine identifier
specified on the network
statement in the TCF).
OFF TASK taskname-LIBRARY libraryname.
Task taskname in task library libraryname
could not be loaded from extended memory or
recovered and loaded from mass storage.
Task was turned off. TAF transactions
using tasks will abort.
Inform site analyst.
Library must be
recreated.
ONLY *8L0CK* or *RECORD* CAN FOLLOW FILE
NAME.
S e l f - e x p l a n a t o r y.
Correct error and rerun.
DMREC
OPEN ERROR ON COPY OF THE DIRECTORY.
An open error was generated when trying to
access the directory file.
Inform data
a d m i n i s t r a t o r.
DMREC
OPERATOR OVERRIDE.
Operator has overridden TAF.
None.
TAF
OPERATOR TERMINATION.
Operator typed in K.STOP in K display
command.
None.
TAFREC
PACKED OATE/TIME CONVERSION ERROR.
An error was generated when converting the
directive date/time to a packed date/time.
Check the date and time
used on directive and
rerun.
DMREC
PARAMETER FORMAT ERROR.
The input directive contains an incorrect
file name - too many characters or
nonalphanumeric characters.
Correct directive and
rerun.
DMREC
PARITY ERROR IN TAPE WITH VSN=vsn.
Tape with vsn has been mounted and has a
p a r i t y e r r o r.
Clean the tape or
replace it.
OMREC
nnnn PER CENT CPU USAGE.
Summary message indicating CPU usage by the
transaction subsystem.
None.
TAF
PERCENT PARAMETER NOT SPECIFIED PROPERLY.
The percent parameter was not of the
correct format or was specified greater
than 100.
Correct directive and
rerun.
OMREC
PF xxxxxxx - NOT ON xxJ FILE.
The xxJ file does not have the specified
CRM data file defined.
Make necessary xxJ file
entry (CRN statement).
DMREC
(RXJ)
• B-20
TAF
60459500
X*^5\
,^v
60459500 C
G-3
function as the interruption sequence whether entered
during input or output.
(B2) - TERMINATION OR USER BREAK 2 CHARACTER
The B2 command specifies the character that, when
entered as the only character in a logical line (ter
mination character followed by the message transmis
sion key), causes program termination.
(BS) • BACKSPACE CHARACTER
T h e B S c o m m a n d s p e c i fi e s t h e c h a r a c t e r u s e d t o
delete the previous input character.
Format:
ct B2-ub2
Format:
Parameter
ct BS«bs
Parameter
ct Represents the network control
character for your terminal as
defined by the CT terminal def
inition command.
Description
ct Represents the network control
character for your terminal as
defined by the CT terminal def
inition command.
b s S p e c i fi e s t h e n e w b a c k s p a c e c h a r
a c t e r. T h i s c h a r a c t e r m u s t d i f
fer from the characters currently
defined for AB, Bl, B2, CN, CT,
EB, and EL.
It is possible to backspace only to the beginning of
the current physical line; additional backspaces are
disregarded. When a page width of 0 is selected,
the network assumes a page width of 100 characters
for backspacing. If the page width is in the range
20 through 56, backspacing Into previous physical
lines is sometimes permitted.
This command only applies to asynchronous terminals
o n l y.
Description
u b 2 S p e c i fi e s t h e n e w u s e r b r e a k 2
c h a r a c t e r. T h i s c h a r a c t e r m u s t
differ from the characters cur
r e n t l y d e fi n e d f o r A B , B S , B l ,
CN, CT, EB, and EL.
The termination sequence is discussed in section 17.
This command does not apply to bisynchronous 2780 and
3780 terminals.
(CH) • DISPLAY TERMINAL CHARACTERISTICS
The CH command displays some of the terminal's cur
rent characteristics.
Format:
ct CH
(Bl) - INTERRUPTION OR USER BREAK 1 CHARACTER
Parameter
The Bl command specifies the character that, when
entered as the only character in a logical line
(Interruption character followed by the message
transmission key), causes program interruption.
Format:
Des c r ipt ion
ct
Represents the network control
character for your terminal as
defined by the CT terminal def
inition command.
ubl
Specifies the new user break 1
c h a r a c t e r. T h i s c h a r a c t e r m u s t
differ from the characters cur
r e n t l y d e fi n e d f o r A B , B S , B 2 ,
CN, CT, EB, and BL.
The interruption sequence is discussed in section 17.
The BR command determines whether the BREAK key can
also function as the Bl character.
This command does not apply to bisynchronous 2780
and 3780 terminals.
• G-4
ct Represents the network control
character for your terminal as
defined by the CT terminal def
inition command.
The CH command produces a display in the following
format:
ct Bl-ubl
Parameter
Description
TC-tc,BS-bs,CN»cn,AB=ab,Bl-ubl,B2"ub2,EL«"el,EB=eb
where the variable portions appear as ASCII charac
ters If printable, mnemonics (for example, STX) If
nonprlntable, or N/A if the attribute is not appli
cable.
(Cl) • CARRIAGE RETURN IDLE COUNT
The CI command specifies the number of idle charac
ters to be inserted into the output stream after a
carriage return.
Format:
ct CI»ci
60459500 C
Parameter
Description
ct Represents the network control
character for your terminal as
d e fi n e d b y t h e C T t e r m i n a l
definition command.
ct Represents the network control
character for your terminal as
defined by the CT terminal def
inition command.
c i S p e c i fi e s t h e n e w c a r r i a g e r e t u r n
idle count. This value can be
from 0 to 99 or the string CA. A
value of CA restores the carriage
return idle count to the default
value.
option Indicates whether to send a res
ponse to the terminal or not. A
value of Y indicates yes and N
indicates no.
When the network produces a carriage return, the
network outputs the specified number of idle charac
ters before outputting the next line. This allows
time for the carriage return function and ensures
that characters are not lost because of printing
attempts during the carriage return operation.
This command only applies to asynchronous terminals.
jjKSBN.
Parameter
Des c r ipt ion
This command applies only to asynchronous terminals
(except 2741s). If CP-Y and IN-KB are selected, the
system responds to the line feed key by sending a
carriage return and responds to an EL or EB charac
ter by sending the cursor positioning response
s p e c i fi e d b y t h e E L o r E B c o m m a n d . I f I N = B K i s
s e l e c t e d o r y o u a r e a t a n X . 2 5 PA D t e r m i n a l , t h e
system responds only to the EB character by sending
the cursor positioning response selected by the EB
command.
(CN) • CANCEL CHARACTER
(CT) • NETWORK CONTROL CHARACTER
The CN command specifies the character used to cancel
the logical line currently being input.
The CT command specifies a network control character
for the terminal. When you enter this character as
t h e fi r s t c h a r a c t e r o f a l o g i c a l l i n e , i t s i g n a l s
t h a t w h a t f o l l o w s i s a t e r m i n a l d e fi n i t i o n c o m m a n d
or a special command that the network forwards to
your application with a preemptive status.
Format:
ct CN»CQ
Parameter
Description
ct Represents the network control
character for your terminal as
defined by the CT terminal def
inition command.
e n S p e c i fi e s t h e n e w c a n c e l c h a r
acter. This character must
differ from the characters
c u r r e n t l y d e fi n e d f o r B S , B l ,
B2, CT, EB, and EL.
When you enter the cancel character as the last
character in a line, the entire logical line in
progress is cancelled. The system responds to a
cancel line character by printing *DEL* on the next
line and positioning the carriage to the beginning
of a new line. The BR command determines whether
the BREAK key can also function as the CN character.
This command does not apply to bisynchronous 2780,
3270, and 3780 terminals.
(CP) - CURSOR POSITIONING AFTER INPUT
The CP command determines whether or not the system
sends the terminal a response to the line feed key,
the EL character, and the EB character.
Format:
Format:
ct CT-char
Parameter
Description
ct
Represents the current network
control character for your ter
minal.
char
S p e c i fi e s t h e n e w n e t w o r k c o n
t r o l c h a r a c t e r. T h i s c h a r a c t e r
must differ from the characters
c u r r e n t l y d e fi n e d f o r A B , B S ,
Bl, B2, CN, EB, and EL.
If you enter the CT command in a line with multiple
t e r m i n a l d e fi n i t i o n s , t h e n e w v a l u e c h a r d o e s n o t
take effect until the complete line is processed.
(DL) - DELIMITERS FOR SINGLE-MESSAGE TRANSPARENT INPUT
MODE
T h e D L c o m m a n d s p e c i fi e s t h e d e l i m i t e r s t h a t
terminate single-message transparent Input mode.
When you initiate transparent input mode (IN»X,
IN-XK, or IN»XP), the network reads your input and
sends it to the system without translation until it
e n c o u n t e r s a d e l i m i t e r. I f y o u r t e r m i n a l ' s p a r i t y
is set to even, odd, or zero (PA=E, 0, or Z), the
parity bit is stripped (set to zero) before the
characters are sent to the host, although no
ct CP»option
60459500 C
G-5
translation occurs. If your terminal's parity is
set to none or ignore (PA=N or I), the parity bit is
not stripped. See the NAM/CCP Terminal Interfaces
Reference Manual for more information on transparent
i n p u t a n d p a r i t y. T h e fi r s t d e l i m i t e r e n c o u n t e r e d
terminates transparent input mode.
the SEND or ETX key as their only transparent mode
t e r m i n a t o r. F o r X . 2 5 d e v i c e s , t h e PA D f o r w a r d i n g
signal always acts as a transparent mode terminator
in addition to any other options selected.
Format:
(EB) • END-OF-BLOCK CHARACTER
ct DL»Xxx,Ccount,TO
Parameter
ct
Xxx
Des c r ipt ion
Represents the network control
character for your terminal as
d e fi n e d b y t h e C T t e r m i n a l
definition command.
Specifies the 2-digit hexadecimal
code (xx) of the character you
want as a delimiter. The network
does not send the character as
part of the input data. When you
specify a hexadecimal code above
7F, you must have previously set
your ter- minal's parity to none
( PA - N ) o r i g n o r e ( PA - I ) ; o t h e r
wise the network cannot detect
the code when it occurs in a
transparent mode message. If the
terminal's parity is set to none,
the 8-bit hexadecimal code input
from the terminal is matched
against the 8-bit hexadecimal
c o d e s p e c i fi e d a s t h e d e l i m i t e r
(xx). If the terminal's parity
is set to ignore, the bottom 7
bits of the terminal input are
matched against the bottom 7 bits
o f t h e s p e c i fi e d d e l i m i t e r ( x x ) .
The EB command defines the end-of-block character
and defines the cursor-positioning response to that
c h a r a c t e r. T h e E B c h a r a c t e r a c t s a s t h e m e s s a g e
transmission key for terminals operating in block
mode (refer to the IN command).
Format:
ct EB-eb,cpr
Parameter
Description
ct
Represents the network control
character for your terminal as
d e fi n e d b y t h e C T t e r m i n a l
definition command.
eb
S p e c i fi e s t h e n e w e n d - o f - b l o c k
c h a r a c t e r. Yo u c a n s p e c i f y t h e
following values for eb:
eb
Description
char Selects the new EB
character.
This
character must dif
fer from the charac
ters currently de
fined for AB, BS, Bl,
B2, CN, and CT.
Ccount
Specifies a decimal value (count)
from 1 to 40951 that functions
as a character count delimiter.
EB Selects the default
end-of-block charac
ter or character se
quence .
TO
S p e c i fi e s t h a t a t i m e o u t o f b e
tween 200 and 400 milliseconds
will be a transparent mode de
l i m i t e r.
EL Selects the current
logical end-of-line
c h a r a c t e r.
You can select any of the three types of delimiters:
character delimiter (specify Xxx), character count
delimiter (specify Ccount), and timeout delimiter
(specify TO).
The parameter values for DL are order-independent
a n d o p t i o n a l . H o w e v e r, y o u m u s t s p e c i f y a t l e a s t
one of the parameter values. You can omit trailing
commas if you do not specify all three types of
delimiters.
Entering this command with any number of new
delimiters cancels all transparent mode input
delimiters already in effect, including those
specified with the XL command.
The DL command applies
4 t e r m i n a l s . Te r m i n a l
the RETURN key as
terminator and mode 4
only to asynchronous and mode
c l a s s 4 i s c o n fi g u r e d w i t h
the only transparent mode
terminals are configured with
cpr
S p e c i fi e s t h e c u r s o r - p o s i t i o n i n g
r e s p o n s e t o t h e E B c h a r a c t e r.
Yo u c a n s p e c i f y t h e f o l l o w i n g
values for cpr:
cpr
D e s c r i p t io n
CR Send a carriage re
turn to the terminal.
LF Send a line feed to
the terminal.
CL
Send a carriage re
turn and a line feed
to the terminal.
NO
Send no response.
The two EB parameters (EB=eb and cpr) are optional
and order-independent. If you omit one, the system
retains its previous value.
tThese values are valid within the network. However, unless changed during installation, the maximum logical
input line length in IAF (160 characters) limits you.
• G-6
60459500 C
This command is valid only for asynchronous
minals, except for paper tape devices and 2741
minals. The end-of-block character for mode 4
minals is ETX and is not changeable. The X.25
forwarding signal is the default for X.25 PSN
minals and always acts as an end-of-block. If
specify the char form of the eb parameter, it is
effective if It occurs as the last character
packet sequence.
ter
ter
ter
PAD
ter
you
only
in a
The CP command enables or disables the cursorpositioning response specified by the cpr parameter.
(EL) • END-OF-LINE CHARACTER
T h e E L c o m m a n d d e fi n e s t h e l o g i c a l e n d - o f - l i n e
character (car r i a g e r e t u r n ) a n d d e fi n e s t h e c u r s o r p o s i t i o n i n g r e s p o n s e t o t h a t c h a r a c t e r. I t a l s o
d e fi n e s t h e m e s s a g e t r a n s m i s s i o n k e y f o r a s y n c h
ronous terminals not operating in block mode (refer
to the IN command).
Format:
Parameter
el
/#**>
Des c r ipt ion
CL Send a carriage re
turn and a line feed
to the terminal.
NO Send no response.
The two EL parameters (el and cpr) are optional and
order-Independent. If you omit one, the system
retains its previous value.
This command does not apply to 2741, HASP, 3270, and
bisynchronous 2780 and 3780 terminals; the cpr
parameter does not apply to mode 4 or X.25 PSN
terminals; and the char specification does not apply
to mode 4 terminals.
The CP command enables or disables the cursorpositioning response specified by the cpr parameter.
(EP) • ECHOPLEX MODE
The EP command enables or disables the echoing of
input characters back to the terminal.
ct EP-option
Parameter
Represents the network control
character for your terminal as
d e fi n e d b y t h e C T t e r m i n a l
definition command.
Specifies the new logical end-ofl i n e c h a r a c t e r. Yo u c a n s p e c i f y
the following values for el:
el
Description
char Selects the new EL
character.
This
character must dif
fer from the charac
ters currently de
fi n e d f o r A B , B S ,
Bl, B2, CN, and CT.
Description
ct
Represents the network control
character for your terminal as
d e fi n e d b y t h e C T t e r m i n a l
definition command.
option
S p e c i fi e s w h e t h e r t o e n a b l e ( Y )
or disable (N) input echoing.
Some terminals can perform their own character
echoing, such as terminals with a HALF/FULL duplex
switch. If the switch is in the HALF position, set
the EP value to N, and the terminal echoes the
input. If the switch is in the FULL position, set
the EP value to Y and the network echoes the input.
EB Selects the current
end-of-block char
acter or character
sequence.
You can use the EP command and full-duplex mode as a
security measure. If you are in full-duplex mode
and EP is Y during login, the system echoes all of
your input except your password. This is not true,
however, if you enter your user name and password on
the same line.
EL Selects the default
logical end-of-line
c h a r a c t e r.
This command only applies to asynchronous terminals
(except 2741s) but is not valid for X.25 PSN
terminals.
c p r S p e c i fi e s t h e c u r s o r - p o s i t i o n i n g
r e s p o n s e t o t h e E L c h a r a c t e r.
Yo u c a n s p e c i f y t h e f o l l o w i n g
values for cpr:
cpr
CR
LF
60459500 C
Description
Format:
ct EL«el, cpr
ct
cpr
Des cr i p t i o n
Send a carriage re
turn to the terminal.
Send a line feed t o
the terminal.
(FA) • FULL ASCII INPUT MODE
The FA command enables or disables the full-ASCII
input mode.
Format:
ct FAdoption
G-7
Parameter
Description
ct Represents the network control
character for your terminal as
defined by the CT terminal def
inition command.
o p t i o n S p e c i fi e s w h e t h e r t o e n a b l e ( Y )
or disable (N) the full-ASCII
input mode.
In full-ASCII input, all 128 ASCII characters,
i n c l u d i n g N U L , D E L , S T X , L F, a n d a l l B L K a n d
message-forwarding signals (which are normally
discarded), are sent to the host. Exceptions to
this are the following characters:
• NULs, DELs and LFs when encountered as the
fi r s t c h a r a c t e r o f a n i n p u t l i n e o r a s t h e
character following a message-forwarding
signal
The host selected is used until either you change it
or until your terminal is disconnected from the host.
(HD) • DISPLAY OF HOST NODES
The HD command controls when the system displays the
host availability display (HAD), which shows all
paths you can select to connect your terminal to a
host. If your computer system is a multihost
system, your site may choose to show the HAD
whenever you disconnect from a host unless you
i n h i b i t t h e d i s p l a y.
Format:
ct HD-option
Parameter
• CRs that follow LFs when inputting from
paper tape
Description
ct
Represents Che network control
character for your terminal as
defined by the CT terminal def
inition command.
option
Represents Y or N. Y enables
and N disables the automatic
displaying of the HAD.
• DC3s that follow the EL character when in
putting from paper tape
• DCls and DC3s when output control (OC-Y) is
selected
In full-ASCII mode, the network does not recognize
the terminal functions associated with the mnenomics
Bl, B2, CN, AB, and BS. The network does recognize
t e r m i n a l d e fi n i t i o n c o m m a n d s a n d o t h e r c o m m a n d s
beginning with the CT character.
If SE is in effect when you select FA or if FA is in
effect when you select SE, FA takes precedence and
S E w i l l n o t b e e ff e c t i v e u n t i l FA i s t u r n e d o ff . I f
full-ASCII mode Is enabled when you select trans
parent input mode, the network, suspends the fullASCII mode until the transparent input mode
terminates.
This command only applies to asynchronous and mode 4
terminals.
If you specify HD-Y, you get a display of the HAD
immediately and at any time you disconnect from the
host (for example, after you enter the TM command or
after you log out of an application without
s w i t c h i n g t o a n o t h e r a p p l i c a t i o n ) . Yo u a l s o g e t a
header and trailer line along with the HAD (refer to
the TM command).
The HAD has the following format:
message CONTROL CHARACTER»ct
NPU NODE-npu TERMINAL NAME-terminal
HOST
NODE
host}
host 2
host.
STATUS
nodei
node 2
SELECTED/
CONNECTED
condltloni
condition2
noder
conditionn
statusr
statusi
status2
(HC) • HOST CONNECTION
The HC command sets or changes the host connected to
your terminal. The host availability display (HAD)
shows the available hosts (refer to the HD command
for more information on the HAD). This command
disconnects you from your current host and
establishes a new host connection. This command is
equivalent to HS or HN followed by TM.
The variable items In the display have the following
descriptions.
Description
Format:
A message describing the status
of your current host connection.
ct HC«hostname
Parameter
• G-8
ct
Network control character cur
rently defined for your terminal.
npu
The node number of the Network
Processing Unit (NPU) your ter
minal is connected to.
terminal
The name of your terminal.
host*;
Represents the I- to 7-character
n a m e o f a h o s t . T h e fi e l d m a y
be blank.
Des c r ipt ion
ct
Represents the network control
character for your terminal as
defined by the CT terminal def
inition command.
hostname
s p e c i fi e s t h e n a m e o f t h e h o s t
to which you want your terminal
connected. The valid entries
appear in the HAD.
60459500 C
/'SjS^v
Item
<(#Sv
Description
node^
Represents a node number (1-31).
co nd ition ^
Indicates that you have selected
node^ (S), that you are con
nected to the host using node^
(C), or that node^ has been
automatically selected and the
connection to the host is in
progress (SA).
status£
Represents
AVAILABLE.
AVAILABLE or
NOT
Your terminal uses the path to host with the least
t r a f fi c . T h e p a t h s e l e c t e d i s u s e d u n t i l e i t h e r y o u
change it or until your terminal Is disconnected
from the host.
(IC) - FLOW CONTROL FOR INPUT DEVICES
T h e I C c o m m a n d s p e c i fi e s w h e t h e r t h e t e r m i n a l
recognizes DC3s as a stop signal and DC Is as a
resume signal for terminal input.
Format:
ct IC-option
Parameter
(HN) - HOST NOOE SELECTION
r
The HN command 3ets or changes the host or the path
(node) to a host through which your terminal is
connected. This command does not disconnect you
from your current host connection. You must log out
or disconnect with the Secure Login command or TM
terminal definition command before you can connect
to the new selection.
Format:
ct
Represents the network control
character for your terminal as
defined by the CT terminal def
inition command.
option
S p e c i fi e s w h e t h e r t o e n a b l e ( Y )
or disable (N) input control.
Input control applies to asynchronous terminals,
including paper tape devices (except 2741 and X.25
PSN terminals).
ct HN-node
Parameter
Description
Description
ct Represents the network control
character for your terminal as
d e fi n e d b y t h e C T t e r m i n a l
definition command.
n o d e S p e c i fi e s a n o d e n u m b e r . T h e
default is the node the network
processing unit is presently
using to access its supervisor
(CS).
The host availability display (HAD) lists all nodes
your terminal can use. Refer to the HD command for
a description of the HAD.
(IN) - INPUT DEVICE AND TRANSMISSION MODE
The IN command identifies the input device and the
transmission mode of the device. As the input
device, you can specify one of the following:
• A keyboard.
• A p a p e r t a p e r e a d e r.
As the input transmission mode, you can specify
either:
• Normalized line mode (one message or logical
line per terminal transmission block).
(HS) - HOST SELECTION
• Normalized block mode (one or more logical
lines or messages collected Into a block
before it is transmitted).
The HS command selects a host which is connected to
your terminal. The host availability display (HAD)
shows the available hosts (refer to the HD command).
• Transparent mode (input Is not edited or
translated by the network).
Format:
Format:
ct IN-in
ct HS»ho3tname
Parameter
Description
Parameter
Description
Represents the network control
character for your terminal as
defined by the CT terminal def
inition command.
ct
Represents the network control
character for your terminal as
d e fi n e d b y t h e C T t e r m i n a l
definition command.
hostname Specifies the name of the host to
which you want your terminal con
nected. The valid entries appear
in the HAD.
in
S p e c i fi e s t h e I n p u t d e v i c e a n d
t r a n s m i s s i o n m o d e . Yo u c a n
specify the following values for
In:
ct
60459500 C
G-9
in
Description
Parameter
BK Selects block mode
as from a form ter
minal and normalized
input mode.
KB Selects a keyboard
in character or line
mode and normalized
input mode.
PT Selects paper tape
and normalized input
mode.
X
Selects the current
input device and
transparent input
mode.
XK Selects the keyboard
and transparent in
put mode.
XP Selects paper tape
and transparent input
mode.
v a l u e S p e c i fi e s t h e n e w l i n e f e e d i d l e
count. This value can be from 0
to 99 or the string CA. A value
of CA restores the line feed idle
count to the default value.
The line feed idle count is similar to the carriage
return idle count (CI), except that the idle char
acters are output after a line feed instead of after
the carriage return.
This command only applies to asynchronous terminals.
(LK) - LOCKOUT OF UNSOLICITED MESSAGES
The LK command determines whether unsolicited mes
sages from the network operator appear at your ter
minal.
Format:
ct LK-option
Parameter
When the IN value is XK, XP, or X, terminal input is
sent to the host in transparent mode blocks. Trans
parent mode continues until the system encounters a
previously defined transparent mode terminator.
When the IN value is XK and transparent mode
minates, the IN value automatically reverts to
When the IN value is XP and transparent mode
minates, the IN value automatically reverts to
When the IN value is X and transparent mode
minates, the IN value automatically reverts to
value that was previously in effect.
The IN command is not applicable to HASP, 3270 or
bisynchronous 2780 and 3780 terminals. 2741 ter
minals can only select IN-KB, IN-X, and IN-XK. Mode
4 terminals, which are always in block mode, and
X.25 PSN terminals cannot select PT or XP mode.
Description
ct Represents the network control
character for your terminal as
d e fi n e d b y t h e C T t e r m i n a l
definition command.
ter
KB.
ter
P T.
ter
the
When the IN value is PT or XP, the network sends the
X-ON code to start the paper tape reader automat
ically after the end of a message is output to the
terminal and the message empties the terminal's
output queue.
Description
o p t i o n S p e c i fi e s w h e t h e r t o l o c k o u t
unsolicited messages. A value
of Y locks out the messages and
a value of N allows the messages
to appear.
This command is not valid for bisynchronous 2780 and
3780 terminals.
(MS) - MESSAGE TO NETWORK OPERATOR
The MS command sends a message to the network
o p e r a t o r.
Jf-tmgK
Format:
ct MS«message
(LI) . LINE FEED IDLE COUNT
Parameter
T h e L I c o m m a n d s p e c i fi e s t h e n u m b e r o f i d l e
characters to be inserted into the output stream
following a line feed.
Format:
ct LI»value
Parameter
ct
• G-10
Des c r ipt ion
Represents the network control
character for your terminal as
d e fi n e d b y t h e C T t e r m i n a l
definition command.
Description
ct Represents the network control
character for your terminal as
defined by the CT terminal def
inition command.
m e s s a g e S p e c i fi e s y o u r m e s s a g e t o t h e
o p e r a t o r. Yo u c a n u s e a n y
string of 50 characters or less.
If you are having problems with the network (such as
d i f fi c u l t y c o n n e c t i n g t o I A F ) , y o u c a n c o m m u n i c a t e
these problems to the network operator using the MS
command•
60459500 C
(OC) - FLOW CONTROL FOR OUTPUT DEVICES
(PA) - PARITY PROCESSING
The OC command specifies whether the terminal gen
erates DC3s as a stop signal to the network and DCls
as a resume signal for terminal output.
The PA command specifies the parity processing to be
performed by the network.
Format:
Format:
ct PA-pa
ct OC«option
Parameter
Parameter
Des c r ipt ion
ct
Represents the network control
character for your terminal as
defined by the CT terminal def
inition command.
option
Specifies whether to enable (Y)
or disable (N) output control.
If the network receives a DC3 while output control
is enabled, it suspends output until it receives a
DC1 or until you send another block of input.
Description
ct
Represents the network control
character for your terminal as
defined by the CT terminal def
inition command.
pa
Specifies the type of parity pro
c e s s i n g . Yo u c a n s p e c i f y t h e
following values for pa:
pa
E
Description
Set
Output control applies to asynchronous terminals,
including paper tape devices (except 2741s).
(OP) • OUTPUT DEVICE SELECTION
The OP command specifies the type of output device.
Format:
ct OP«op
Parameter
Des c r ipt ion
ct
Represents the network control
character for your terminal as
d e fi n e d b y t h e C T t e r m i n a l
definition command.
op
S p e c i fi e s t h e o u t p u t d e v i c e .
Yo u c a n s p e c i f y t h e f o l l o w i n g
values for op:
op
Description
D I S p e c i fi e s a d i s p l a y
device.
P R S p e c i fi e s a p r i n t e r .
PT
S p e c i fi e s a
tape punch.
paper
You can punch a tape in any mode, but the network
does not provide the proper X-OFF characters unless
OP has a value of PT.
If you select OP-PR, the network does line folding
and page bounding for asynchronous and X.25 PSN
terminals. If OP=>DI, the network assumes the ter
minal performs these functions Itself.
This command only applies to asynchronous terminals
(except 2741s). OP-PT does not apply to X.25 PSN
terminals.
J^V
60459500 C
parity bit for
even parity during
output, and check
for even parity and
set parity bit to
zero on input.
N In transparent mode,
do not set or check
the parity bit be
cause it is part of
the input or output
data. In normalized
mode, set the parity
bit to zero on input
and output.
0
Set
parity
bit
for
odd parity during
output, and check
for odd parity and
set parity bit to
zero on input.
Z
Set
parity
bit
to
zero on output and
check parity bit
against zero on
input.
1 In transparent mode,
do not set or check
the parity bit be
cause It is part of
the input or output
data. Ignore the
parity bit when
checking for trans
parent input mode
delimiters. In nor
malized mode, set the
parity bit to zero
on input and output.
This command only applies to asynchronous terminals
(except 2741s). For X.25 PSN terminals, the parity
bit is set to 0 and not checked for input.
G-ll
(PG) • PAGE WAITING
Parameter
The PG command enables or disables page waiting at
the terminal during output. If you enable page
waiting, the terminal stops at the end of each
output page for your acknowledgement (a null input
line) before output continues.
ct Represents the network control
character for your terminal as
defined by the CT terminal def
inition command.
p w S p e c i fi e s t h e p a g e w i d t h . Y o u
can specify a value of 0 or any
value from 20 to 255. PW-0
s e l e c t s a n i n fi n i t e l y l o n g l i n e .
Format:
ct PG-option
Parameter
ct
Des c r ipt ion
Represents the network control
character for your terminal as
defined by the CT terminal def
inition command.
option
Specifies whether to enable (Y)
or disable (N) page waiting.
When you enter a null input line to get the next
page of output, the null input line has no other
meaning.
(SE) - SPECIAL EDITING MODE
The SE command enables or disables the
editing variant of normalized input mode.
ct SE»option
Parameter
(PL) - PAGE LENGTH
The PL command establishes the maximum number of
physical lines that can be printed as one page. If
OP has a value of PR, the network automatically
positions the carriage to the top of the form after
PL lines have been output.
Format:
ct PL-pl
Des c r ipt ion
ct
Represents the network control
character for your terminal as
defined by the CT terminal def
inition command.
Pi
S p e c i fi e s t h e p a g e l e n g t h . Yo u
can specify 0 or any value from
8 to 255. PL-0 selects an In
fi n i t e l y l o n g p a g e .
The PL value must be nonzero if you want to enable
page waiting, since page waiting only occurs after
the number of lines defined by pl-1 are output.
special
Format:
Page waiting does not apply to bisynchronous 2780 or
3780 terminals or to HASP terminals.
Parameter
Description
Description
ct
Represents the network control
character for your terminal as
defined by the CT terminal def
inition command.
option
Enables (Y) or disables (N)
special editing operations.
When special editing is in effect, any backspace
character entered is stored for transmission to the
h o s t . S i m i l a r l y, a l i n e f e e d e n t r y p r o d u c e s a
normal line feed operation at the terminal and the
network stores the line feed character code for
transmission to the host. A backspace followed by a
line feed causes the system to output a bell and an
exclamation point on an ASCII terminal or an in
verted caret (v) on an APL terminal below the last
character entered.
This command is only valid for asynchronous ter
minals but not for X.25 PSN terminals.
(TC) - TERMINAL CUSS COMMAND
The TC command specifies a terminal class for your
terminal. The terminal class associates your
t e r m i n a l w i t h a p r e d e fi n e d s e t o f t e r m i n a l
c h a r a c t e r i s t i c s . To e f f e c t i v e l y u s e a t e r m i n a l
class, choose a terminal class whose default
t e r m i n a l d e fi n i t i o n c o r r e s p o n d s t o t h e
characteristics of your terminal.
Format:
(PW) - PAGE WIDTH
The PW command establishes the maximum number of
characters that the terminal prints on one output
line. If OP has the value PR, the system automat
ically starts a new line after pw characters have
been output.
Format:
ct PW»pw
• G-12
ct TC-tc
Parameter
Description
ct Represents the network control
character for your terminal as
defined by the CT terminal def
inition command.
tc
S p e c i fi e s t h e t e r m i n a l c l a s s .
The value tc can be from 1 to 17.
60459500 C
Parameter
The following list associates terminal class values
with terminal types:
tc
J 0 ^ Ly
I
M33, M35, M37, M38 teletypes
2
CDC 713-10, 722, 751-1, 752, 756
3
CDC 721
4
IBM 2741
5
M40 teletypes
6
Hazeltine 2000
7
Terminals conforming to the ANSI
X3.64 standard (DEC VT100)
8
Tektronix 4010, 4014
9
HASP protocol, postprint format
control
10
200 User Terminal
11
CDC 714-30
12
CDC 711-10
13
CDC 714-10/20
14
HASP protocol, preprint format
control
15
CDC 734, 731-12, 732-12
16
IBM 2780
17
IBM 3780
18
IBM 3270
A terminal that is not shown as belonging to a ter
minal class may still be operational. The terminal
can be assigned to a terminal class having similar
characteristics and the terminal's definition can be
modified as necessary to correctly define the opera
tional characteristics of the terminal.
If your terminal is on an auto-recognition line and
Its terminal class is other than 1, 4, 10, or 13,
you can use the TC command to change its terminal
class to ensure proper operation.
If you include a TC command in a sequence of ter
minal definition commands, enter the TC command
fi r s t a s I t r e s e t s a l l o t h e r t e r m i n a l c h a r a c t e r
istics.
(TM) - TERMINATING A TERMINAL-HOST CONNECTION
The TM command severs the connection between your
terminal and a host.
Format:
ct TM
J®>^
60459500 C
ct
Terminal Type
Description
Represents the network control
character for your terminal as
defined by the CT command.
You can use the TM command if your application does
not respond to your input. The system responds to
the TM command in the following manner:
host status
had
prompt
CONTROL CHARACTER=ct
The variable items have the following descriptions:
Item
host status
D e s c r i p t i on
Indicates the status of the host
y o u h a v e j u s t s p e c i fi e d o r t o
which you are/were connected.
You can get any one of the fol
lowing messages:
HOST AVAILABLE
HOST BUSY
HOST CONNECTED
HOST DISCONNECTED
HOST UNAVAILABLE
NO HOST AVAILABLE
NO HOST CONNECTED
NO HOST SELECTED
ct
Represents the network control
character for your terminal as
defined by the CT command.
had
Represents the host availability
display (HAD). The HAD appears
only if you have enabled its
automatic display (refer to the
HD command).
prompt
Represents an action the system
wants you to take or a status
message. You can get any one of
the following prompts:
ENTER Ct HD TO SEE HOST
STATUS
ENTER Ct HN=NN TO SELECT HOST
ENTER INPUT TO CONNECT TO
HOST
INPUT DISCARDED
READY FOR INPUT
TERMINAL DISABLED BY NOP
(XL) - MULTIMESSAGE TRANSPARENT MODE
The network provides a transparent mode that allows
you to remain in transparent input mode even after
message blocks have been forwarded to the applica
tion. The XL command specifies the multimessageforwarding signal and the terminator for transparent
Input mode. If your terminal's parity Is set to
even, odd, or zero (PA-E, 0 or Z), the parity bit Is
stripped (set to zero) before the characters are
sent to the host, although no translation occurs.
If your terminal's parity Is set to none or ignore
( PA « N o r I ) , t h e p a r i t y b i t I s n o t s t r i p p e d . S e e
the NAM/CCP Terminal Interfaces Reference manual for
more Information on transparent Input and parity.
G-13
Format:
Parameter
ct XL-Xxx,Ccount,TO,Yyy
Parameter
Description
ct
Represents the network control
character for your terminal as
defined by the CT terminal def
inition command.
Xxx
Selects the character with the
two-digit hexadecimal represen
tation xx as the messageforwarding signal. If you do not
s p e c i f y a v a l u e y y, t h e o c c u r
rence of two successive charac
ters defined by xx acts as a ter
minator for transparent input
mode. When you specify a hexa
decimal code above 7F, you must
have previously set your ter
minal's parity to none (PA-N) or
ignore (PA-I); otherwise the net
work cannot detect the code when
it occurs in a transparent mode
message.
Ccount
Selects a decimal value from 1
to 40951 as a character count
that functions as a messageforwarding signal.
TO
Selects timeout as a transparent
input mode terminator.
Yyy
Selects the character with the
two-digit hexadecimal represen
Description
tation yy as a terminator for
transparent input mode when it
follows xx. When you specify a
hexadecimal code above 7F, you
must have previously set your
terminal's parity to none (PA-N)
o r i g n o r e ( PA - I ) ; o t h e r w i s e t h e
network cannot detect the code
w h e n i t o c c u r s i n a t r a n sparent
mode message.
Y y y, I f s p e c i fi e d , m u s t f o l l o w t h e X x x p a r a m e t e r ;
otherwise, it is ignored. The parameters are
o t h e r w i s e o r d e r - i n d e p e n d e n t . Yo u m u s t s p e c i f y a t
least one of Xxx or TO to select a transparent mode
t e r m i n a t o r. W h e n i t i m m e d i a t e l y f o l l o w s t h e
c h a r a c t e r d e fi n e d b y X x x o n i n p u t , t h e c h a r a c t e r
d e fi n e d b y y y t e r m i n a t e s t r a n s p a r e n t i n p u t m o d e .
T h e c h a r a c t e r s d e fi n e d b y X x x a n d Y y y c a n b e
identical or you can omit Yyy. In either case, two
s u c c e s s i v e i n p u t c h a r a c t e r s d e fi n e d b y X x x a r e
required to terminate transparent mode.
The message-forwarding signals and mode terminators
are not sent to the host.
/^'SaSSs.
This command cancels all transparent mode termina
tors and delimiters defined by the DL command or a
previous XL command. You can select multimessage
transparent input mode by using the XL command in
conjunction with the IN command and selecting IN-X,
IN-XK, or IN-XP.
This command does not apply to HASP and bisynchro
nous terminals.
tThese values are valid with the network. However, unless changed during Installation, the maximum logical
input line length in IAF (160 characters) limits you.
• G-14
/SE8V
60459500 C
y/^S^V
Table G-l. Default Terminal Definitions
Te r a t n e l T y p e s
Naaeooic
TC
Detcriptloa
TIT
Ml)
CDC
713-10.
722,731-1.
712,796
Te r m i n a l c l o u
CDC ! IM
721 2741
TTt IhAZ
M40-2 2000
X3.64
occ
Te k j
4000
ASP 1 CDC
x.:7T HPOST
i 200
any
VT100
J i
COC
714-10,
714-20
HASP
PRE
CDC
734
IBM ! i n
2710
1780
UN
3270
10
11
12
1)
14
13
16
17
IS
CAB
na
na
na
na
na
na
na
na
na
na
na
I
(I)
oa
I
I
1
1
na
na
na
I
na
na
na
na
na
na
na
!(6)
(0)
CAB
CDC
711-10
j UT
]1
CAB
CDC
714-10
Al
Abort output block
CAB
CAM
CAN
CAB
W
Slocking (actor
1
I
1
I
I
1
as
teckapace character
IS
SS
IS
none
as
IS
IS
(I)
t l
Oa.r break 1
ou
ou
ou
OU
su
DU
DU
(I)
na
na
OCA
OCA
OCA
0C4
DC*
oc*
(l>
na
ae
)<7)
na
na
am
na
na
na
am
na
na
na
12
a
Our brack 1
Carriage renin tdlee
a
Cancel character
DL
u
na
Iraak aa ua.r break 1
(and cancel character)
C I
a
a
OC*
a
/^PN
tsc
ISC
isc
CR
KL
Cl
at
Cl
204)
na
204)
2041
204)
Bo
Bo
aa
Bo
No
tor
tOT
na
COT
CL
CL
na
CL
Ct
BL
LP
na
(SC
ISC
Character dallalcer
Ct
at
Character count
dellalter
:o*j
2043
Timeout dellaiter
Bo
COT
na
na
(1)
na
na
na
na
na
na
na
na
na
na
(I)
na
na
na
na
ne
na
na
na
ne
na
(I)
X
X
X
X
X
X
X
X
X
X
Cl
(1)
na
(41
(4)
(4)
(4)
ne
(*)
ne
oa
204)
(1)
na
no
na
na
ne
na
na
na
na
Z!
No
No
(1)
na
na
na
ne
ne
na
na
COT
COT
COT
(2)
aa
(4)
(4)
(4)
(4)
Oat
(4)
na
na
na
CL
CL
CL
Bo
na
Bo
No
No
Bo
ft*
No
na
na
na
at
at
Ct
Cl
(1)
na
(3)
(S>
()>
(3)
TU
())
na
ne
na
i f
LP
LP
LT
Bo
na
No
No
No
Bo
rt*
No
na
na
na
no
na
na
na
tu
na
na
ne
na
aa
na
na
na
am
na
na
KB
Slsgle-axaeaga treaenercot Input aoda
na
tad-of-block
Cod-of-logical line
Character
Cl
Conor poaltlonlng
L»
LP
IB
Input device
I t
Line (oed tdlee
U
lockout NOP aeeaatea
oc
Output device (lew
control
Output device
PA
rarity processing
PS
feae waiting
n.
fare length
fW
hfe width
na
Kl
Kg
Kl
Kl
Kl
aa
na
na
na
na
na
na
na
CK
no
CK
B
K
ax
M
C
aa
B
K
(I)
KM
na
na
aa
na
aa
na
na
na
(1)
No
No
No
Bo
No
No
na
na
ft
Bo
na
na
f t
01
01
rt
DI
01
01
DI
aa
72
24
30
SO
(0
1)2
No
Bo
No
No
(I)
na
na
na
ae
())
na
as
na
ne
(1)
aa
na
»
•
oa
na
na
«M
na
na
na .
na
oa
na
na
na
aa
24
27
24
33
(I)
0
1)
16
16
16
0
1)
0
0
24
to
74
CO
74
(I)
SO
ao
SO
SO
to
eo
80
60
120
ao
na
na
na
na
na
na
na
na
na
ne
na
No
na
No
No
No
No
n.
No
na
na
na
Special adltlRf aoda
rtolttaeesaie
transparent Input eode
(l*
na
Input device (1cm
control
or
na
na
Cchoplcx aoda
foil ASCII Input aoda
IL
X
CAB
aa
Conor paaltloalnt
tu
tc
sc
CAN
ESC
CAB
Cureor poaltlonlng
a
CAB
CAB
Character
a.
CAB
CAB
Network control
character
IS
No
No
No
No
(0) Teralnale belong to urelul claaece 1 th
(1)
(I)
(1)
(4)
(5)
(6)
(7)
ough ) of i through t.
S u a a . ( o c t h e t c r a l M t I f I t w e r e n o t e c n n e c t e d v i a i p a c k e t - s w t t h i n g networtk.
Cad-ot-packet laouence (H bit It reeet to t . r o ) .
The portly bit 1. Ignored oa Input and to generated fo r output aa o r t h * beele t.ral nal type.
CTX (moulting (roa eh. SEND key).
CSC A (reeuttlng (roa th. CAJUIUCI tfTUXN k e y ) .
Prograa attention k«r 1 1. a valid eaar b aak 1.
Prograa attention key 2 le a «at!4 tiaar b cak 2.
0^*-.
60459500 C
G-15
Table G-2. Parameter Ranges for Terminal Definition Commands (Sheet I of 2)
Terolnal Typea
KaeBonli
tty
Deacrlptlon
N33
CDC
713-10,
722,751-1,
752,756
CDC
721
laM
2741
TTT
K40-2
HAZ
2000
X3.64
OEC
VT100
Te k
4000
X.25
any
HASP
POST
CDC
200
OT
CDC
714-30
CDC
711-10
CDC
HASP
714-10, PRE
714-20
CDC
734
IBM
2780
IBM
3780
IBM
3270
TC
Te r m i n a l c l a i a
10
11
12
13
14
IS
16
17
18
AB
Abort output block
(1)
(1)
(I)
(1)
(1)
(I)
(0
(1)
na
na
na
na
na
na
aa
na
na
oa
na
BF
Blocking factor
0-2
0-2
0-2
0-2
0-2
0-2
0-2
0-2
(2)
na
0-2
C-2
0-2
0-2
na
0-2
na
na
0-2
BS
Backepaco character
(1)
(1)
(I)
(1)
(0,(7) (l>
(I)
(1)
(2)
ne
na
na
na
na
aa
na
na
na
na
Bl
User break 1
(1)
(1)
(I)
(1)
(1)
(1)
(1)
(t>
(2)
(l>
(1)
(I)
(1)
(I)
(1)
(1)
na
na
(D
B2
Ueer break 2
(1)
(l)
(1)
(1)
(1)
(2)
(1)
(1)
(1>
(1)
(1)
(1)
(I)
na
na
(1)
BR
Brtak aa uaar break I Y. N
(and cancel character) ( Y, N )
Y, N
( Y. N )
Y. N
( Y. N )
na
na
Y, N
(Y,N)
Y,N
(Y.N)
Y. N
(Y.N)
Y. N
(Y.N)
(2)
oa
na
na
na
na
na
na
na
na
na
na
Cl
Carriage re cum ldlea
0-99,
ca
0-99,
CA
0-99,
CA
0-99,
CA
0-99,
CA
0-99,
CA
0-99.
ca
0-99,
CA
(2)
na
na
na
na
na
na
na
na
na
na
CN
Cancel character
(i>
(1)
(l>
(1)
(1)
(1)
(1)
(l>
(2)
(1)
(I)
(1)
(1)
(1)
(1)
(1)
na
na
(1)
CP
Curaor poaltlonlng
Y. N
Y. N
Y. N
na
Y.N
Y.N
Y,N
Y.N
(2)
na
na
na
na
na
na
na
na
na
na
CT
Network control
character
(1)
(1)
(1)
(1)
(1)
u>
(1)
(2)
(1)
(1)
(l>
(I)
(1)
(t)
(1)
(I)
(I)
(1)
DL
Slngla-aeiMge
tranapareat Input
lode
Character dellatter
0-FF
0-FF
0-FF
6D
0-FF
0-FF
0-FF
0-FF
(2>
na
03
03
03
03
na
03
na
na
na
Character count
dellalter
1-4095
1-4095
na
na
1-4093
1-4093 1-4093 1-4093 (2>
na
na
oa
na
na
na
na
na
na
oa
Tlstcout dellalter
TO
TO
TO
na
TO
TO
TO
TO
(2)
na
na
na
na
na
na
na
ne
na
na
Character
(1).
El,
EB
O ) .
EL,
EB
(l>
EL,
EB
na
(1).
El,
EB
(I).
EL,
EB
(l>.
EL.
EB
(1),
ei.
EB
(2)
na
EB
CB
EB
EB
na
EB
na
na
na
Curaor poatclonlng
(3>
(3)
(3)
na
(3)
(3)
(3)
(3)
(2)
na
No
No
H>
No
na
No
na
na
na
(t).
EL,
EB
na
(1).
El,
(I).
EL,
EB
(1).
EL,
EB
EB,
EL
EB,
El
EB.
El
EB,
EL
na
CB,
EL
na
na
na
»
(l>.
El,
EB
na
Cl.
EB
(2)
EL,
SB
<3)
<3)
(3)
(3)
(3)
(3)
(3)
No
na
No
So
No
No
na
No
na
na
na
EB
EL
(0)
End-of-block
End-of-logleal line
Character
Curaor poaltlonlng
*^™^v
Table G-2. Parameter Ranges for Terminal Definition Commands (Sheet 2 of 2)
Teralnal Typea
Kne■o n l c
EP
FA
Deacrlptlon
Cchoplax aoda
Full ASCII Input aode
TTY
H33
C K
713-10,
722,751-1.
752,756
Y. N
Y,N
Y. N
IBM
2741
TTT
H40-2
HAZ
2000
X3.&4
DEC
VT100
Tek
4000
X.25
any
HASP
POST
CDC
Y, N
na
Y. N
Y. N
Y. N
Y. N
na
na
na
Y. N
Y.N
Y.N
Y. N
Y. N
Y. N
(2)
na
na
na
200
UT
CDC
714-30
aa
CDC
711-10
na
HASP
PRE
CDC
734
IBM
2780
IBM
IBM
3780 3270
na
na
na
na
na
na
Y. N
na
na
na
na
na
na
na
na
na
na
CDC
714-10.
714-20
Y.N
Y. N
Y.N
Y. N
na
na
na
na
na
na
IC
Input device (low
control
Y, N
Y. H
Y. N
na
Y. N
Y. N
Y. N
Y.N
IN
Input device
(4)
(4)
(4)
KB,XX. ( 4 )
X
(4)
(4)
(4)
Line feed ldlea
0-99,
CA
0-99.
CA
0-99,
CA
0-99,
CA
0-99.
CA
0-99,
CA
0-99
a
0-99,
CA
(2)
na
na
na
na
na
oa
na
na
na
na
LI
!
LK
lockout aeaeagea
Y. N
Y. N
Y. N
Y. N
Y.N
Y.N
Y. N
Y. N
(2)
Y.N
Y. N
Y. H
T. N
Y. N
Y. N
Y. N
na
na
Y. N
j
na
na
na
na
na
na
na
na
na
'
"i
OC
Output device flow
control
Y.N
Y. N
Y. N
na
Y.N
Y.N
Y. N
Y. N
na
na
na
OP
(5)
(3)
(5)
PR,
DI
(5)
(5)
(S)
(5)
PR,
DI
na
na
na
na
na
na
na
na
na
Output device
n. j
Parity processing
Z.O,
E.N
Z.O.
E.N
Z.O
E.N
na
Z.O.
E.N
Z.O,
E.N
Z.O.
E.N
Z.O.
E.H
(6)
na
na
na
na
na
na
na
na
na
na
PA
PC
Y. N
Y. N
Y. N
Y. N
Y. N
Y. N
Y.N
Y.N
(2)
na
Y.N
Y. N
Y.N
Y. N
na
Y. N
na
na
Page waiting
Y. N
0,8255
0.8255
0,8255
0,8255
0,8255
0.8255
PL
Page length
0,8255
0.8255
0,8255
0,8255
0,8255
0.8255
0,8255
0,8255
(2)
PW
Page width
235
0.20255
0.20255
0,20255
0.20255
0,20255
0,20255
0,20255
0,20-
(2)
255
0,20- 0,20255
255
0,20255
0,20255
0,20255
0 , 2 0 - 0 , 2 0 - 0 , 2 0 - 0 , 2 0 - 0,20255
255
255
255
SE
Special editing aode
Y. N
T. N
Y. N
Y.N
Y.N
Y.N
Y.N
Y. N
aa
na
na
na
na
na
na
na
na
na
na
TC
Te r a l n a l c l a a a I n p u t
1,2.3.
5-8
1.2.3,
5-8
1.2.3,
5-8
1.2.3,
5-8
1.2.3. 1.2.3, 1.2.3. 1.2.3,
5-8
5-8
5-8
5-8
10,15
11-13
11-13
11-13
14
10,15 16
17
18
XL
Kultlaeaeage
tranaparent Input
aode
0-FF
0-FF
O-FF
0-FF
0-FF
03
03
03
03
oa
03
na
na
na
na
na
na
Character dellalter
C h a r a c t e r t e r a l n a t o r 0-FF
Ti m e o u t d e l l a l t e r
0$^.
Y. N
CDC
721
Character count
dellalter
TO
I-409S
0-FF
TO
1-4095
0-FF
TO
2D
2D
na
1-409! na
0-FF
TO
1-4095
0-FF
TO
O-FF
0-FF
TO
O-FF
O-FF
TO
(2)
(2)
na
1-4093 1-4095 1-4095 ( 2 )
na
na
oa
na
oa
aa
na
oa
aa
na
na
na
na
na
na
na
na
na
na
na
na
oa
na
oa
na
aa
oa
oa
( 0 ) Te r a l n a l a b e l o n g t o u r a l n a l c l a o e e e I t hrough 3 or 5 through 8
(1) Any character (roa the ASCII 128-eharacter eat except any lowereaae or upperca ae alphabetic c h a r a c t e r, a n y d i g i t 0 through 9, MILL. SOU, STX
OIL, or apace.
(2) Saae aa (or the teralnel If It were not connccted by a packet-awitching networ k .
(3) CR, IF, CL, NO.
(4) KB. PT. BK, X, XK. XP.
(3) PI, DI, PT.
la generated for output.
(6) Seae aa for the terminal If It were not connccted by a packet-awitching networ k . P a r i t y l a Ignored on Input and
(7) ASCII BS character code (8 bcxadeclaal) cannot be uaed.
0^
60459500 C
G-17
DELIMITING AND TRANSMITTING TERMINAL INPUT
/0^
You can transmit input to an application in normal
ized mode (also called character mode) or transparent
mode (also called binary mode). In transparent input
mode, the network does not convert any of your input
but sends it directly to your application. Charac
ters like LF and BS, which the network normally
strips from the input stream, become part of the data
sent to your application. Appendix G describes how
you delimit and transmit input in transparent mode
(refer to the DL and XL commands). The default input
mode for all supported terminal classes is normalized
m o d e , h o w e v e r. T h e r e m a i n d e r o f t h i s a p p e n d i x
describes how to delimit and transmit terminal input
in normalized mode under the default conditions of
the various terminal classes. (Appendix G also
describes how you can change these defaults.)
PHYSICAL END-OF-LINE (LINE FEED)
In terminal classes 1 through 8, you can terminate a
p h y s i c a l l i n e o f i n p u t w i t h a l i n e f e e d k e y. T h e
network also terminates a physical line of output
whenever the page width of a terminal is reached
(refer to the PW conn and in appendix G). The
network may respond to the line, feed key by
advancing the cursor or carriage to the beginning of
the next line (refer to the CP command in appendix
G).
This key is transparent to TAF. When the terminal
is not in block mode, it performs the same function
as the carriage return but does not initiate the
t r a n s a c t i o n . R a t h e r, i t c a u s e s t h e m e s s a g e t o b e
stored in the communication block chain until the
message transmission key is pressed.
LOGICAL END-OF-LINE (CARRIAGE RETURN)
Yo u t e r m i n a t e a l o g i c a l l i n e o f i n p u t w i t h a
c a r r i a g e r e t u r n k e y. A l o g i c a l l i n e c a n c o n s i s t o f
one or more physical lines but not vice versa. The
network may respond to the carriage return by
advancing the cursor or carriage to the next line
(refer to the EL command in appendix G).
MESSAGE TRANSMISSION
Yo u t r a n s m i t y o u r i n p u t t o t h e n e t w o r k w i t h t h e
message transmission key. For non-blocks ode devices,
the message transmission key is the carriage return
k e y. H e n c e , f o r t h e s e t e r m i n a l c l a s s e s , l o g i c a l
l i n e s a r e t r a n s m i t t e d s e p a r a t e l y. W h e n t h e
delimiter for the logical end-of-line and
transmission key are different (as with block mode
devices, including PSN and mode 4 terminals), the
terminal stores logical lines until you press the
t r a n s m i s s i o n k e y. I t t h e n s e n d s t h e s i n g l e
transmission consisting of multiple logical lines to
the network. The network sends each logical line
separately to your application.
Ta b l e H - l s h o w s t h e k e y s u s e d b y t h e v a r i o u s
terminal classes to perform the three functions just
described.
0^\
/^SV
60459500 B
H-l
Table H-l. Default Message Delimiter and Transmission Keys
Function
Terminal Class
1
Physical End-ofLine (Line Feed)
LINE FEED
Logical End-of-Line
(Carriage Return)
Message
Transmission Key
RETURN
RETURN
2
J
RETURN
RETURNt
4
ATTN
RETURN
RETURN
5
NEW LINE
RETURN
RETURN
6
LF
CR
CR
7
LINE FEED
CARRIAGE RETURN
CARRIAGE RETURN
8
LF
RETURN
RETURN
9
Varies tt
Va r i e s t t
Va r i e s t t
10
None
RETURN
SEND
11
None
RETURN
SEND
12
None
NEW LINE
ETX
13
None
NEW LINE
ETX
14
Va r i e s t t
Va r i e s t t
Va r i e s t t
15
None
NEW LINE
SEND
16
None
E
M
EOT
17
None
EM
EOT
18
None
Varies
ENTER
tlf in block mode, refer to terminal documentation for terminal key equivalences.
Those listed are for character and line modes,
tt Terminals operating under HASP protocol use different keys for this purpose.
H-2
60459500 C
DETECTION OF POTENTIALLY BLOCKED TASKS
TAF prevents situations from occuring in which the
execution of a task is blocked because it is
impossible under the circumstances to obtain the
needed central memory space for the task, whether
for an initial load or a memory increase. Several
t e r m s w i l l b e d e fi n e d t o a i d i n t h e d e s c r i p t i o n o f
how potentially blocked tasks are detected:
• Minimum size of the total task area
/pPNv
The total task area is the CM in which TAF
will schedule tasks. It includes the space
occupied by CM-resident tasks. The area
e x t e n d s f r o m t h e fi r s t w o r d a d d r e s s i n t o
which tasks can be loaded to the maximum
fi e l d l e n g t h o f TA F. T h e s i z e o f t h i s a r e a
fluctuates if the TAF/CRM Data Manager is
used. The minimum size of this area occurs
when the TAF/CRM buffer takes on its maximum
size.
• Minimum size of the transient task area
0^\
The transient task area is that portion of
the total task area not occupied by
CM-resident tasks. The minimum size of this
area is defined to be the minimum size of
the total task area minus the sum of the
MFLs of all CM-resident tasks.
One or more tasks will be considered to be
potentially blocked under the following
circumstances.
•
If the initial field lengths of the
CM-resident tasks are so large that they all
couldn not be loaded together.
• If the sum of the MFLs for the CM-resident
tasks exceeds the minimum size of the total
task area.
• If the MFL of a non-CM-resident task exceeds
the minimum size of the transient task area.
Following are the situations when potentially
blocked tasks are detected and the actions that are
taken.
• A t TA F i n i t i a l i z a t i o n . P o t e n t i a l l y b l o c k e d
tasks result in TAF being aborted.
• W h e n TA F i s i n f o r m e d , v i a t h e L I B TA S K T T
option, of the update of a task library
a t t a c h e d b y TA F a n d t h e l i b r a r y c o n t a i n s
potentially blocked tasks, the update will
be rejected.
• When an attempt is made to reduce the MFL of
TAF via the K.MAXFL command to a value that
results in potentially blocked tasks, the
command will be rejected.
The preceding checking assumes that the maximum
fi e l d l e n g t h o f TA F i s s e t ( b y d e f a u l t , v i a K . M F L ,
or via K.MAXFL commands) to a value that can be
attained.
j^HPn,
60459500 A
I-1
J ^ v
ACCESSING A HOST
This appendix describes the steps used to access a
host and to use CDC network software. The login
procedure can be divided into eight steps.
Gathering information.
Setting up your terminal.
Connecting your terminal to the network.
Identifying your terminal to the network.
Selecting a host.
/ifls^K
Connecting to the selected host.
Asynchronous terminals
Asynchronous terminals using X.25
protocol
CDC mode 4 synchronous terminals
Houston Automatic Spooling Program
(HASP) terminals
Bisynchronous terminals like IBM
2780/3780
Bisynchronous terminals like IBM 3270
• Must you supply a family name, user name,
password, and application name during login?
If so, get the required information.
• Does your terminal use the ASCII character
set and code?
Identifying yourself and your terminal to
the host.
• Selecting a network application.
T h e fi r s t p a r t o f t h i s a p p e n d i x g i v e s a b r i e f
description of the eight steps. The second part of
th e a p p e n d i x g i v e s a m o r e d e t a i l e d d e s c r i p t i o n o f
the same eight steps followed by additional general
i n f o r m a t i o n . Yo u m a y fi n d t h e b r i e f d e s c r i p t i o n o f
t h e s t e p s s u f fi c i e n t t o a c c o m p l i s h l o g i n a t y o u r
site. If not, consult the detailed description. In
addition to more detail, it provides shortcuts, the
various options that are available at any given
step, and failure conditions.
STEP 2 - SETTING UP YOUR TERMINAL
• Turn power switch on.
• Load and initialize any software or controlware needed by your terminal.
• Set the terminal's duplex or echoplex switch
to the correct position (typically HALF if
your keyboard entries appear unduplicated on
your console's screen or printer).
• Set the terminal's parity switch to its
proper position.
BRIEF DESCRIPTION OF ACCESS
• Set the line speed switch to its proper
setting.
STEP 1 • GATHERING INFORMATION
• Set the transmission mode to either the
character or line mode position.
Find the answers to the following questions.
• Is your terminal hardwired to the system?
• Which key is the data transmission key for
your terminal?
• If you have a dialup terminal, what telephone
number must you dial?
• Into which of the following categories does
your terminal fall?
60459500 C
• Set the online/offline switch to the online
position.
STEP 3 • CONNECTING YOUR TERMINAL TO THE NETWORK
Skip this step if your terminal is hardwired.
Otherwise, determine which of the configurations in
figures J-l, J-2, J-3, and J-4 most closely matches
your terminal and follow the instructions in the
fi g u r e .
J-l
/C="*iS!v
1.
Turn on coupler.
2.
Pick up receiver.
3.
Dial phone number.
4.
Wait for high-pitched tone.
5.
Fit receiver into coupler. Be
sure you put the cord end of
the receiver into the correct
cup, as indicated on the
coupler.
l\w\
&
l o ^ ^ = "
\
1
(.
Figure J-l. Separate Acoustic Coupler
1. Pick up receiver.
2. Push button, such as ORIG but
ton on Teletype model 33 or 35.
3. Dial phone number.
4. Wait for high-pitched tone.
__J
S3
o
o
o
o
o
o
□
o
5. Push button, such as ORIG but
ton on Teletype model 33 or 35.
6 . R e p l a c e r e c e i v e r.
Figure J-2. Data Set Built Into the Terminal
1. Pick up receiver.
2. Set switch to TALK or pu3h TALK
button.
3. Dial phone number.
4. Wait for high-pitched tone.
5. Set switch to DATA or push DATA
button.
6. Replace receiver.
Figure J-3. Data Sets with Switches and Buttons
• J-2
60459500 C
/£^v
1. Pick up receiver.
2. Dial phone number.
3. Wait for high-pitched tone.
4 . F i t r e c e i v e r i n t o c o u p l e r. B e
sure you put the cord end of
the receiver into the correct
cup, as indicated on the
c o u p l e r.
000 000000000
oaaaoac.
OOQOO
ooc
Figure J-4. Terminal with Built-in Acoustic Coupler
STEP 4 - IDENTIFYING YOUR TERMINAL TO THE NETWORK
If the network does not prompt you within a few
seconds after you are connected to it (there might
be a light on the terminal that indicates when your
terminal is connected), perform the appropriate
following steps.
• For asynchronous terminals not using X.25
protocol:
a. Press the key that transmits a carriage
return. The network responds with two
line feeds when it recognizes your line
speed.
b. Type a closing parenthesis (not required
if the terminal uses the ASCII character
set and code) and press the carriage
return key. When the network recognizes
your character code set, it responds
with a line feed.
• For asynchronous terminals using X.25
protocol:
Get the Information from your site.
• For 3270 bisynchronous terminals:
N o i d e n t i fi c a t i o n i s n e c e s s a r y.
STEP 5 - SELECTING A HOST
If you have a choice of hosts or host paths (multihost), the network displays a list of the hosts and
host paths that are available and prompts you to
make a selection. Otherwise, you can enter:
ct HD
to get a list of hosts, ct is your terminal's net
work control character (refer to the NOS Reference
Set, Volume 3, System Commands).
Make your selection with one of the following
commands *
ct HN=node
or
ct HS=hostnarae
node is the number of a host path; and hostname is
the name of a host.
• For mode 4 synchronous terminals:
Press the data transmission key.
• For HASP and 2780/3780 bisynchronous
terminals:
Send a /*C0NFIG card image.
0^
60459500 C
STEP 6 • CONNECTING TO THE SELECTED HOST
If your terminal was not automatically connected to
a host, the network prompts you to connect. Enter a
carriage return to make the connection.
J-3
STEP 7 ■ IDENTIFYING YOURSELF AND YOUR TERMINAL TO
THE HOST
Once your terminal is connected to the host, the host
displays a banner similar to:
WELCOME TO THE NOS SOFTWARE SYSTEM.
COPYRIGHT CONTROL DATA 1978, 198X.
date
time
terminal
name
site identification NOS 2 PSR Level number
Following this banner, you may be prompted for a
family name, then a user name, then a password, and
fi n a l l y a n a p p l i c a t i o n n a m e ( i f t h e r e i s n o
default). For each prompt, enter the appropriate
Information followed by a carriage return.
STEP 8 • SELECTING A NETWORK APPLICATION
If your login is successful, your terminal is placed
under the control of the requested or default
application, which then prompts you for a command.
DETAILED DESCRIPTION OF ACCESS
The following description covers in more detail the
eight steps briefly described earlier. Although each
of the steps is always performed when a terminal
accesses the system, you might find that your net
work's administrators can make many of these steps
unnecessary by having the software perform the steps
for you.
STEP 1 - GATHERING INFORMATION
If you know the answers to the following questions,
or can get the answers from people at your site, the
text following each question will tell you which
steps and corresponding subsections of this appendix
you can skip. If you cannot answer the questions,
read all of the subsections; each procedure
description contains hints for answering the
questions.
1. Is the terminal hardwired, or is it a dialup terminal?
A hardwired terminal is connected directly
to the network through a device called a
modulator/demodulator (modem). A modem can
be either a separate box, or built into the
terminal. A dial-up terminal temporarily
connects to the network through a telephone
line and either an acoustic coupler or a
telephone data set (a coupler or data set
does the same things as a modem).
If you do not need to dial a telephone number
to use the network, then your terminal is
hardwired. (A nearby telephone does not ne
cessarily mean the terminal is dial-up.)
2 . I s y o u r n e t w o r k c o n fi g u r e d f o r a u t o m a t i c
recognition?
• J-4
Yo u r s i t e c a n a s k t h e n e t w o r k s o f t w a r e t o
determine certain things about your terminal
when the terminal joins the network. This
process is called automatic recognition.
[Terminals using X.25 packet-switching net
works (PSN) cannot use automatic recogni
tion.]
I f y o u r n e t w o r k i s c o n fi g u r e d f o r a u t o m a t i c
recognition, you must perform an extra step
each time you connect your terminal to the
network. If your terminal is not so con
figured, you may skip questions 3 and 4.
3. What protocol does your terminal use?
Y o u r t e r m i n a l m u s t fi t I n t o o n e o f t h e
following categories.
• Asynchronous terminals that work like
teletypewriters or IBM 2741 ter
minals.
• Asynchronous using an X.25 PSN
through a packet assembly/disassembly
( PA D ) s e r v i c e ; t h e s e t e r m i n als work
like teletypewriters.
• CDC mode 4 synchronous; mode 4A ter
minals work like the CDC 200 User
Te r m i n a l , w h i l e m o d e 4 C t e r m i n a l s
work like CDC 711 or 714 terminals.
• HASP terminals.
• Bisynchronous terminals that work
like IBM 2780, 3270 or 3780 ter
minals .
If your terminal operating manual does not
tell you what protocol your terminal uses,
question 4 and the terminal classes shown in
the NOS Reference Set, Volume 3, System Com
mands might help you answer this question.
If your network is not configured for auto
matic recognition, skip question 4.
/^^S\
The network software cannot use information from a
/♦SIGNON card image. When such a card image is
received in a signon block, the signon block con
tents are discarded.
Instead, the network software uses a /*CONFIG state
m e n t f o r t h e a u t o m a t i c r e c o g n i t i o n p r o c e d u r e . Yo u
can send the /*CONFIG statement in the signon block
when your terminal permits you to provide the con
tents of that block.
If the signon block does not contain the /*CONFtG
statement and the terminal must use automatic
recognition, a prompt requesting that statement is
sent to the terminal console. When a prompt for the
statement appears, enter the statement through a
card reader.
Parameter
ti
Description
Te r m i n a l
type:
POST HASP postprint (de
fault); this is ter
minal class 9.
PRE HASP preprint; this
is terminal class 14.
C 0 = c o C o n fi g u r a t i o n o r d i n a l , a d e c i m a l
integer from 1 to 255; the de
f a u l t i s 1 . U s e t h e c o n fi g u r a
tion ordinal to select one of
s e v e r a l t e r m i n a l d e fi n i t i o n s d e
fined for the line that describes
a s p e c i fi c c o m b i n a t i o n o f a d d i
tional characteristics. Site ad
ministration personnel can tell
you the correct number to use*
CR=x
I d e n t i fi e s
available
card
readers. The default is 1.
LP=x
I d e n t i fi e s
available
line
printers. The default is 1.
CP=y
I d e n t i fi e s
available
card
punches; y cannot equal z. The
default is 1.
P L = z I d e n t i fi e s a v a i l a b l e p l o t t e r s ; y
cannot equal z. No default
exists for z; you cannot omit
PL-z if you have a plotter.
x, y, or z is a list of numbers specified by either:
1/2/ . . . /7
ALL (all numbers from 1 through 7)
The numbers you use for x, y, and z must match the
HASP stream numbers used for the corresponding de
vices within the workstation. Site administration
personnel should have this Information if you do not
know what numbers to use.
For example:
/*C0NFIG,PRE,C0=2,CR=2,LP=2/3,CP=4/PL=5
i d e n t i fi e s y o u r t e r m i n a l a s t h e s e c o n d p r e p r i n t i n g
w o r k s t a t i o n d e fi n e d f o r t h e c o m m u n i c a t i o n l i n e ,
having:
• A card reader and line printer on stream 2.
• Another printer on stream 3.
• A card punch on stream 4.
• A plotter on stream 5.
The format of the /*CONFIG statement is:
/*C0NFIG,t i,CO=co,CR=x,LP=x,CP=y,PL=z
Blanks are not allowed within the statement; a blank
ends parameter processing. The parameters, which
you can specify in any order, are:
60459500 C
If no prompt for a /*C0NFIG statement appears, you
are ready for the next step.
The software sends you a message that helps you
decide which step comes next. Turn to the
subsection appropriate for the next step you must
perform.
J-9
Procedure for Mode 4 Terminals
/*C0NFIG,3780,C0=4,CR,LP,CP=2
Mode 4 terminals belong to terminal classes 10
through 13 and 15. For automatic recognition, press
the end-of-block key within 1 minute of physical con
nection.
You are ready for the next step. The software sends
you a message that helps you decide which step comes
n e x t . Tu r n t o t h e s u b s e c t i o n a p p r o p r i a t e f o r t h e
next step you must perform.
Procedure for Bisynchronous Terminals
Bisynchronous terminals belong to terminal classes
16, 17, and 18. Enter a /*C0NFIG statement to
specify the type of terminal and the devices avail
able at it.
The format of the /*C0NFIG statement is:
/*C0NFIG,ti,C0=co,CR,LP*CP=y
Blanks are not allowed within the statement; a blank
ends parameter processing. The parameters, which you
can specify in any order, are as follows:
Parameter
ti
Des c r ipt ion
Terminal type:
2780 IBM 2780 (default);
this is terminal
class 16.
3780 IBM 3780; this is
terminal class 17.
3270 IBM 3270; this is
terminal class 18.
C0=co
C
R
Indicates an available card
reader; assumed if not specified.
LP
Indicates an available line
printer; assumed if not spe
c i fi e d .
CP=y
For example:
• J-10
T h e c o n fi g u r a t i o n o r d i n a l , a
decimal integer from 1 through
255; the default is 1. Use the
c o n fi g u a t i o n o r d i n a l t o s e l e c t
o n e o f s e v e r a l t e r m i n a l d e fi n i
t i o n s d e fi n e d f o r t h e l i n e t h a t
describes a specific combination
of additional characteristics.
Site personnel can tell you the
correct number to use.
Indicates an available card
punch; assumed not to exist if
not specified. The »y portion is
not allowed for 2780; for 3270 or
3780, the y portion is required
and can be either 2 or 3 to cor
respond to the device selection
character DC2 or DC3.
identifes your terminal as a 3780 terminal having:
• A card reader and line printer*
• A card punch, which is selected by the char
acter code DC2.
If no prompt for a /*CONFIG statement appears, you
are ready for the next step.
The software expecting the next step sends you a
message which helps you decide which procedure comes
n e x t . Tu r n t o t h e s u b s e c t i o n a p p r o p r i a t e f o r t h e
next step you must perform.
STEP 5 • SELECTING A HOST
You might need to select the host, which runs the
software you want to use. This is not necessary if
your Installation personnel select a host path for
your terminal when the network is configured.
Yo u c a n s e l e c t o r c h a n g e a s i t e - d e fi n e d h o st path
after you connect your terminal to the network. The
host path selected is used until either you change
it or until your terminal is disconnected from the
network.
More than one host path can be available to each
host from a terminal. If one host path fails, you
can select an alternate route to the host.
Selecting a Host
You can select a host or override a site-defined host
selection with the following terminal definition com
mand.
ct HS=hostname
ct represents the network control character for your
terminal. For most asynchronous terminals this is
ESC or X,
Each host may be configured with a unique name.
This name (1 through 7 characters) is indicated by
hostname.
For example:
%HS=ARHN0S
w o u l d s e l e c t t h e p a t h w i t h t h e l e a s t t r a f fi c t o t h e
host called ARHNOS (Z represents your terminal's
network control character).
If you specify the name, your terminal uses the host
p a t h w i t h t h e l e a s t t r a f fi c .
If you do not know the name you need, the host
availability display (HAD) can show you what names
are available. That display is described later in
this appendix.
Once you have selected your host, you are ready for
the next step.
60459500 C
The software sends you a message that helps you
d e c i d e w h i c h s t e p c o m e s n e x t . Tu r n t o t h e s u b
section appropriate for the next step you must
perform.
Selecting a Specific Host Path
U s e t h e f o l l o w i n g t e r m i n a l d e fi n i t i o n c o m m a n d t o
select your own host path or to override the sitedefined host path.
ct HN=nn
ct represents the network control character for your
terminal. For most asynchronous terminals this is
ESC or X.
E a c h a c c e s s h a s a u n i q u e n u m b e r, c a l l e d a n o d e
n u m b e r. T h e h o s t n o d e n u m b e r ( 1 t h r o u g h 3 1 ) i s
indicated by nn.
Controlling the Display of Host Paths
T h e h o s t a v a i l a b i l i t y d i s p l a y ( H A D ) ( fi g u r e J - 8 )
lists all host paths your terminal can currently use
to gain access to the host and all hosts in the net
work. You can turn display of the HAD on and off or
request the display with the following terminal def
inition command.
For example:
ct HD=option
ct represents the network control character for your
terminal. For most asynchronous terminals this is
ESC or Z.
%HN=2
would select access 2 (Z represents your terminal's
network control character).
iggjSRay
If you omit the node number, your terminal uses the
host path the network is using to communicate with
its supervising host.
If you do not know the node number you need, the host
availability display (HAD) can show you what numbers
are available. That display is described in the
following subsection. Each node number may have a
name for Its host, provided by your site to help you
identify the corresponding host system on the HAD.
Once you have selected the host path, you are ready
for the next step.
If the display mode Is N (no), you receive only two
lines at your terminal (the host status message and
the prompt message) instead of the full display when
you disconnect your terminal from a host.
If you enter HD=Y or HD, the full display is issued
immediately when you disconnect your terminal from
t h e h o s t . Yo u t h e n h a v e a c h o i c e o f h o s t s a n d / o r
host paths to which you can request connection.
If you have a multihost system, typically the HAD
a p p e a r s w h e n y o u fi r s t a c c e s s t h e n e t w o r k . T h i s
appearance is controlled by site installation.
Display
host status message
NPU NODEs xx TERMINAL NAME= yyyyyy
HOST
NODE
CONTROL CHARACTER = ct
SELECTED/
CONNECTED
STATUS
host-)
hosts
node-)
nodes
condition-)
conditions
status-)
statusj
hostn
noden
conditionn
statusn
prompt message
Figure J-8. Host Availability Display (Sheet 1 of 2)
/f&i
60459500 C
J-l I
Field
host status
message
Description
Status of a given host, which can be one of the following:
Message
Meaning
You Also See:
HOST CONNECTED
You are connected
to the host.
prompt
message d or e
NO HOST SELECTED
Host is available;
you have not selected
a host.
prompt
message b
NO HOST AVAILABLE
No hosts are avail
able.
prompt
message a
HOST UNAVAILABLE
You have selected
a host that is not
up.
prompt
message a
HOST BUSY
Connection rejected
by host.
prompt
message a
HOST DISCONNECTED
Connection to host
terminated.
prompt
message c or e
HOST AVAILABLE
You have selected
host that is up.
prompt
message c
NO HOST CONNECTED
You are not connected
to a host.
prompt
message c
ct
Network control character currently defined for your terminal.
xx
The number of the host node you are connected to.
yyyyyy
The terminal number of your terminal.
host.;
The 1- to 7-character name of a host; if the network only has
one host, this can be blank.
node,
The host node number used in selecting a path through the network;
1 < node*; < 31.
condition^
S ■ selected, not connected
C - connected, not selected
SC ■ selected and connected
SA ■ selected, attempting connection
status;
Either AVAILABLE or NOT AVAILABLE; a host is only available when
it is connected to the network.
prompt
message
Action to take In response to a host status message, which can be
one of the following:
prompt message a: ENTER Ct HD TO SEE HOST STATUS
prompt message b: ENTER ct HN=nn TO SELECT HOST
prompt message c: ENTER INPUT TO CONNECT TO HOST
prompt message d: READY FOR INPUT
prompt message e: TERMINAL DISABLED BY NOP
prompt message f: INPUT DISCARDED
Figure J-8. Host Availability Display (Sheet 2 of 2)
• J-12
60459500 C
yUSfflJ^
STEP 6 • CONNECTING TO THE SELECTED HOST
Yo u r s i t e p e r s o n n e l m i g h t h a v e c o n fi g u r e d y o u r
terminal so th a t i t i s a u t o m a t i c a l l y c o n n e c t e d w i t h
a host. If so, the network continues to attempt
c o n n e c t i o n i n d e fi n i t e l y e i t h e r u n t i l t h e c o n n e c t i o n
is completed or until you stop it by entering ct
T M . Yo u c a n t e l l t h e n e t w o r k i s a t t e m p t i n g t o
connect you when the HAD shows a SA status for any
host. If your terminal is automatically connected
to a host, you may skip this subsection. If not,
you will have to ask for the connection to be made.
You can ask to be connected to the selected host by
entering a carriage return. If the carriage return
is not preceded by an empty line, the information is
d i s c a r d e d ( u n l e s s i t I s a v a l i d t e r m i n a l d e fi n i t i o n
command).
I f y o u r c o n n e c t i o n i s r e j e c t e d , y o u a r e n o t i fi e d .
If you select another host path you must make
another entry to complete a connection. The network
software physically disconnects dial-up devices if
you do not attempt connection to a host within 2
minutes of completing the previous step.
Once you are connected to a host, you are ready for
the next step.
STEP 7 • IDENTIFYING YOURSELF AND YOUR TERMINAL TO
THE HOST
T h e s t e p t h a t i d e n t i fi e s y o u a n d y o u r t e r m i n a l t o
t h e h o s t s y s t e m i s c a l l e d l o g i n . Yo u r t e r m i n a l i s
i d e n t i fi e d t o t h e h o s t s y s t e m b y a s s i g n i n g i t a
family name, a user name, and a password. The host
can prompt you for each of these things.
Yo u r s i t e c a n s e t u p y o u r t e r m i n a l c o n n e c t i o n s o
that part or all of your login is done automati
c a l l y. I f s o , y o u m i g h t n o t s e e t h e c o r r e s p o n d i n g
prompt and you need not enter the information.
Your site might also require use of a secure login
initiation sequence, prior to login, to ensure that
y o u s e n d y o u r u s e r i d e n t i fi c a t i o n t o t h e c o r r e c t
host software. If required, the sequence contains a
site-selected security character and the sequence
will be recognized by the system at any time. De
pending on your terminal type, the secure login
initiation sequence is entered in one of the follow
ing ways.
• At an asynchronous terminal (not 2741),
press the interactive interrupt key (BREAK
or ATTN) and type the character at a 2741
terminal, press the NL key twice. Then
enter the ATTN key, the character, and press
the NL key.
• At an X.25 terminal, press the interactive
interrupt key, type the character, and press
the message transmission key.
• At a mode 4 terminal, clear the screen, press
SEND, clear the screen again, type the char
acter, and press the end-of-block key.
• At a HASP terminal, type the character and
press the end-of-line key.
• At a 2780 or 3780, enter /* and the character
from the console or a card reader.
• At a 3270, clear the screen, press the pro
gram attention 1 key, type the security char
acter, and press the ENTER key.
This action momentarily disconnects you from the
host. You might need to reconnect your terminal to
the host (if connection is not automatic). Now you
are guaranteed that you are sending your login
entries to the correct host software.
R e f e r t o fi g u r e J - 9 f o r a s a m p l e l o g i n f r o m a n
asynchronous terminal. In the example, the terminal
has not been configured by site personnel for auto
matic login. Everything you would typically enter
is shown in lowercase.
WELCOME TO THE NOS SOFTWARE SYSTEM.
COPYRIGHT CONTROL DATA 1978, 198X.
j^p^H..
85/03/01. 09/51.06. T05A50
CDC NETWORK OPERATING SYSTEM
FAMILY:
USER NAME: jrc3069
PASSWORD: jane
/T05A50 - APPLICATION: iaf
NOS 2
Figure J-9. Sample Login from an Asynchronous Terminal
/#^-
60459500 C
J-13
Automatic Login
The family name or user name assigned to your ter
minal for an automatic login can be:
• A mandatory value.
• A default value.
• A primary value.
If a mandatory value is assigned, you do not receive
a prompt and cannot use any other value.
If a default value is assigned, you are prompted and
you can either: enter an empty line as a response
to the system prompt if you want either the default
f a m i l y o r u s e r n a m e t o a p p l y, o r r e s p o n d t o t h e
prompt with another value.
The default family name value assigned to your
t e r m i n a l f o r a u t o m a t i c l o g i n c a n b e d i ff e r e n t f r o m
the default value used by the host for a family
name. You can override the login default even when
you do not know the system default; this procedure
is described in the following subsection.
If a primary value is assigned, you do not receive a
p r o m p t t h e fi r s t t i m e l o g i n o c c u r s w h i l e y o u a r e
connected to the host. Subsequent logins (refer to
Restarting Login Identification) do prompt you. You
can override a primary value for user name by
entering a different value during an abbreviated
login. Abbreviated login is described in a later
subsection.
The next line is either of the following prompts.
FAMILY:
This indicates that no mandatory or primary
family name has been assigned to your ter
minal. Enter the 1- to 7-character name of
the storage device that contains your per
manent files and press the carriage return.
If you want to use the default login family
name, just press the carriage return after
t h e FA M I LY p r o m p t a p p e a r s . Yo u c a n a l s o
enter a value of 0 to override a preassigned
login default family name and use the system
default family name. If you have no preas
signed default family name, carriage return
selects the system default family name.
USER NAME:
Thi3 indicates that no mandatory or primary
user name has been assigned to your terminal.
Enter the user name you were given. The user
name, which can contain any combination of
d i g i t s , l e t t e r s , a n d a s t e r i s k s , i d e n t i fi e s
you as the terminal operator.
The next prompt appears only after a USER NAME
prompt has appeared. This final prompt is either:
PASSWORD:
PASSWORD:
XXXXXXX
Login Dialog
Login begins when the system displays the following
lines.
WELCOME TO THE NOS SOFTWARE SYSTEM.
COPYRIGHT CONTROL DATA 1978, 198X.
Then a line appears with the date, time, and
terminal name; for example:
83/12/28. 15.23.58. TERM201
N e x t i s a l i n e y o u r s i t e s u p p l i e s t h a t i d e n t i fi e s
the host system used; something similar to:
CDC NETWORK OPERATING SYSTEM NOS 2
J-14
The system attempts to preserve your password's
s e c r e c y. I f y o u h a v e s e t y o u r t e r m i n a l a t f u l l
duplex (refer to the NOS Reference Set, Volume 3,
System Commands), your password will not be displayed
when you enter it. You will not see what you type
in. At some terminals, the network overprints
several characters on a line and asks you to type
your password on that line, as shown by the second
PASSWORD prompt. After creating this row of overstruck characters, the cursor moves back to the
fi r s t c h a r a c t e r.
Enter the password currently associated with your
user name. If you must enter the user name, you
also must enter the password. No default exists for
a password.
60459500 C
You must respond to each prompt within 2 minutes.
If you take too long to respond, this message is
displayed at your terminal.
TIMEOUT.
Your terminal is then disconnected from the host.
If you enter an unacceptable family name, user name,
or password, you receive either the following
message:
IMPROPER LOGIN, TRY AGAIN.
FAMILY:
if no mandatory family name is assigned to your
terminal, or:
IMPROPER LOGIN, TRY AGAIN.
USER NAME:
if a mandatory family name is assigned. Reenter all
needed login information, beginning with the
requested parameter, regardless of when the error
occurred.
Yo u m u s t s p e l l e a c h l o g i n e n t r y c o r r e c t l y. I f y o u
make a mistake, such as typing the letter 0 for the
numeral 0 or the number 1 for the letter 1, your
l o g i n w i l l n o t b e s u c c e s s f u l . Tr y a g a i n w h e n t h e
prompting sequence restarts.
You are allowed four consecutive chances to complete
the login procedure. If you make four unsuccessful
attempts to complete login, this message appears at
your terminal:
USER RETRY LIMIT.
y^PfeS
Yo u r t e r m i n a l i s t h e n d i s c o n n e c t e d f r o m t h e h o s t .
If this happens, check the spelling of all of the
e n t r i e s . I f y o u s p e l l e d e v e r y t h i n g c o r r e c t l y,
contact a site administrator.
When the family name, user name, and password are
accepted by the host, you must next connect your
terminal to an application, if there is no default
network application.
STEP 8 • SELECTING A NETWORK APPLICATION
Yo u r s i t e m a y b e s e t u p s o t h a t y o u r t e r m i n a l i s
connected to t h e I A F a p p l i c a t i o n a u t o m a ti c a l l y. O r
your site may connect your terminal automatically to
another application, depending on the installation.
If so, you might not see the corresponding prompt.
If not, you must complete this step yourself.
You are allowed several chances to make a correct
e n try. H o w e ve r, i f y o u f a i l t o c o n n e c t s u c c e s s f u l l y
after four consecutive attempts, your terminal is
automatically disconnected from the host. If this
happens, check the spelling of the name you used.
If the spelling was correct, contact a site
a d m i n i s t r a t o r.
a u t o m a t i c a l l y. Yo u r h o s t s i t e c a n c o n fi g u r e y o u r
connection for either possibility by preassigning an
automatic connection application name.
A preassigned automatic application connection can
be either mandatory or primary for the connection or
i t c a n b e m a n d a t o r y f o r t h e u s e r. I f e i t h e r y o u o r
your connection has a preassigned mandatory appli
cation, you are not prompted, you are automatically
connected to that application, and you cannot use
any other application. If a mandatory application
program is not running in the host, you are logged
out and disconnected from that host.
If a primary value is assigned, you are not prompted
for the initial connection request after identifying
your terminal to the host, and connection to that
p r o g r a m o c c u r s a u t o m a t i c a l l y. I f t h a t c o n n e c t i o n i s
not successful or if you disconnect from that appli
cation program, you have a choice of actions; you can
select another application or disconnect from the
host.
To override a primary automatic application connec
t i o n o n t h e fi r s t a t t e m p t t o s e l e c t a n a p p l i c a t i o n ,
name a different application in an abbreviated login
e n t r y ( d e s c r i b e d l a t e r i n t h i s a p p e n d i x ) f ollowing a
login prompt.
When a primary value is assigned, you are prompted
on subsequent attempts to select an application,
such as when you are switching applications. When
you are prompted to enter an application name and
you want to be connected to your primary applica
tion, enter an empty line as a response.
Manual Connection
This procedure begins when you see the following
prompting message.
terminalname - APPLICATION:
The terminalname variable on this line is the same
terminal name as the one on the first line of your
login sequence. If your terminal is automatically
logged into a network application, you do not
receive this prompt.
When you receive the APPLICATION prompt, enter the
letters and digits that identify the network appli
cation you want to access; for example, IAF for the
I n t e r a c t i v e F a c i l i t y. Yo u c a n a c c e s s C D C - w r i t t e n
applications from the following list that are in
stalled at your site:
• Remote Batch Facility (enter RBF).
• Interactive Facility (enter IAF).
• Tr a n s a c t i o n F a c i l i t y ( e n t e r TA F ) .
• Te r m i n a l Ve r i f i c a t i o n F a c i l i t y ( e n t e r T V F ) .
• Message Control System (enter MCS).
• P L AT O ( e n t e r P N I , w h i c h s t a n d s f o r t h e
PLATO-NAM Interface).
Automatic Connection
Your host may permit you access only to one network
application, or an application can be connected
60459500 C
Other applications, written at your site, might be
available.
J-15
You must respond to the prompt within 2 minutes. If
you take too long to respond, this message is
displayed at your terminal.
TIMEOUT.
Your terminal is then disconnected from the host.
You must spell your entry correctly. If you make a
mistake, such as typing the letter 0 for the numeral
0 or the letter 1 for the number 1, you receive the
following error message:
ILLEGAL APPLICATION, TRY AGAIN,
terminalname - APPLICATION:
The terminal name is indicated by terminalname. You
can also receive this message if your user name is
not permitted access to the application you named.
If you did not spell the name correctly, try again.
If you did spell the name correctly, disconnect your
terminal and contact a site administrator.
If you make four unsuccessful attempts to enter an
application name, this message appears at your ter
minal.
APPLICATION RETRY LIMIT.
Your terminal is then disconnected from the host.
This step is complete when the application you re
quest connects to your terminal. The application
you asked to use might print an identification line
next.
To u s e t h e s i t e - d e fi n e d l o g i n d e f a u l t f a m i l y n a m e ,
enter:
,RLS4525,PASS123,IAF
y^s^s.
To o v e r r i d e y o u r s i t e - d e fi n e d l o g i n d e f a u l t f a m i l y
name with the host's default family name, enter:
0,RLS4525,PASS123,IAF
To use a login default family name and user name
defined by the site for your terminal, enter:
///IAF
To also use a default application name defined by
the site for your terminal, enter:
You can supply combined entries in response to the
FAMILY, USER NAME, and PASSWORD prompts. Although
you do not need to complete the remaining sequence
on the same line, you must enter the information in
the correct order: family name, user name, password,
and application (if there is no default). For
example:
FAMILY: systema
USER NAME: rls4525,pass123
terminalname - APPLICATION: iaf
If you supply a user/password combination that is
o v e r r i d d e n b y a m a n d a t o r y s p e c i fi c a t i o n , t h i s mes
sage is displayed.
Whether the program sends such a message or not, you
can use commands recognized by that application. If
you need to disconnect your terminal from the appli
cation, the application probably has a command for
that purpose. If the program has no such command,
the subsection called Disconnecting from a Host des
cribes a command you can use.
If you offer an application name that is overridden
by a preassigned mandatory application, the follow
ing message is displayed.
ABBREVIATED LOGIN AND APPLICATION CONNECTION
SWITCHING TO A DIFFERENT APPLICATION
You can shorten the standard login and application
connection procedures by entering all of the re
quired information at once. For example, in res
ponse to the FAMILY prompt, you can enter the fol
lowing information on the same line.
Unless you have a mandatory network application
assigned for your terminal, you can transfer your
terminal's connection from the current application
to another application. There are two ways to do
this, depending on the commands used by the current
application.
FAMILY: familynanie,username,password,application
Separate all entries with a comma. The entries are
order-dependent. Use a comma to indicate any default
or unused entries.
You do not receive any of the remaining login selec
tion prompts if you use this abbreviated login pro
cedure, unless you omit a required entry or supply an
entry that is not recognized. Your password entry is
not protected by the system when you use an abbrevi
ated login procedure.
Here are some examples. To log In and connect to
the Interactive Facility application IAF with a
family name of SYSTEMA, a user name of RLS4525, and
a password of PASS123, enter:
SYSTEMA,RLS4525,PASS123,IAF
• J-16
VOLUNTEERED USER/PASSWORD IGNORED.
VOLUNTEERED APPLICATION IGNORED.
Direct Switches
You can switch in one step by entering a switch com
mand recognized by the current application. The fol
lowing switch commands are recognized by CDC-written
network applications:
Command
Application
RBF
IAF
MCS
IAF
BYE,application
LOGIN,application
For example, if your terminal is connected to RBF,
you can gain access to IAF by entering the IAF
command.
60459500 C
y^v
Do not enter any more input until the application
acknowledges it has processed your switch command.
Otherwise, you may lose the input.
There are three ways to restart login, depending on
the commands recognized by the current application
and installation options.
Indirect Switches
Direct Restarts
If your current application does not have a command
for a direct switch, you must disconnect your ter
minal from the current application with a command
recognized by that application. Then you must
request another application connection from the
host. The following disconnection commands are
recognized by CDC-written network applications:
Yo u c a n r e s t a r t h o s t i d e n t i fi c a t i o n b y e n t e r i n g a
login command recognized by the current application.
The following login commands are recognized by CDCwritten network applications:
Program
RBF
IAF
M
C
S
TAF
TVF
Command
END
BYE,
END
EX.LOGT
END
For example, you can switch your terminal connection
from RBF to an application other than IAF by
entering the END command. You then receive a prompt
for a new application name. Do not enter any more
input until the application acknowledges it has
processed your disconnection command. Otherwise,
you might lose the input.
Dialog for Direct and Indirect Switches
After disconnecting the application, the system in
dicates that a connection switch is in progress by
issuing this message.
application - CONNECT TIME hh.mm.ss.
The application that was just disconnected is In
dicated by application and the time that passed
while the terminal was connected to the program is
indicated by hh.mm.ss.
If you used a switch command, you receive an iden
tifying message from your new application. If you
used a disconnection command, you receive another
prompt for an application name.
terminalname - APPLICATION:
unless the terminal is permitted access to only one
application. If so, you are disconnected from the
host.
If you enter the name of another application in res
ponse to the APPLICATION prompt, you are connected
to that application.
Application
Command
RBF
IAF
MCS
LOGIN
HELLO
LOGIN
For example, if your terminal is connected to IAF,
you can restart login by entering the HELLO command.
Do not enter any more input until the application
acknowledges it has processed your command. Other
wise, you may lose the input.
Indirect Restarts
If your current application does not have a command
for a direct switch, you must disconnect your ter
minal from the current program with a command rec
ognized by that application. Then you must request
restart of login from the host. The disconnection
commands recognized by CDC-written network applica
tion are described earlier in this section under
Switching to a Different Application.
For example, you can restart your terminal login from
RBF by entering the END command. You then receive a
prompt for a new application name. Do not enter any
more input until the application acknowledges it has
processed your disconnection command. Otherwise, you
might lose the input.
Secure Login Restarts
If your site has selected the secure login initiation
option and defined a security character, the sequence
may be entered at any time to immediately disconnect
from the current application and initiate the user
login procedure.
After entering the disconnection command, you receive
another prompt for an application name:
terminalname - APPLICATION:
unless the terminal is permitted access to only one
application program. If so, you are disconnected
from the host and can restart login by reconnecting.
RESTARTING LOGIN IDENTIFICATION
There are many reasons why you might want to restart
l o g i n i d e n t i fi c a t i o n a n d t h e s u b s e q u e n t a p p l i c a t i o n
connection. Perhaps you have several user names
available to you, each with permission to use dif
ferent host resources. Or perhaps someone else left
the terminal connected to an application you do not
need, and you do not want to use their user name.
60459500 C
If you receive the APPLICATION prompt, you use one
of the following commands to ask the host system to
restart login:
HELLO
LOGIN
J-17
DISCONNECTING FROM A HOST
You might want to disconnect your terminal from a
host for several reasons, for example:
• Yo u w a n t t o d i s c o n n e c t f r o m t h e n e t w o r k
properly, w i t h o u t l e a v i n g b e h i n d a n i n d i c a
tion that something went wrong; disconnecting
from a host is the first step in disconnect
ing from a CDC network.
• You are allowed access to more than one host
system, and you want to transfer your ter
minal's connection from the current host to
another host.
There are four ways to do this, depending on the
commands used by the current application.
Disconnecting with Application Commands
You can disconnect in one step by entering a host
disconnection command recognized by the current
application. The following host disconnection
commands are recognized by CDC-written network
applications:
Program
Command
RBF
IAF
MCS
LOGOUT or LOGOFF
BYE or LOGOUT or GOODBYE
BYE or LOGOUT
For example, if your terminal is connected to IAF,
you can disconnect from the host by entering the BYE
command.
The following host disconnection commands are valid
responses to the APPLICATION prompt on CDC host
systems:
8YE
/T*®&?&\
LOGOUT
For example, you can disconnect your terminal from
RBF by entering the END command. You then receive a
prompt for a new application name and enter BYE.
Disconnecting with a Network Software Command
You normally end a connection with a host by using a
command to disconnect you from an application and/or
a command to log out of the host. Events might make
i t i m p o s s i b l e f o r y o u t o d o e i t h e r. W h e n t h i s
happens, you can end your terminal's connection to
t h e h o s t b y e n t e r i n g t h i s t e r m i n a l d e fi n i t i o n
command.
Ct TM
c t r e p r e s e n t s t h e n e t w o r k c o n t r o l c h a r a c t e r. F o r
most asynchronous terminals this is ESC.
The network responds to your TM command with a new
host availablity display. You can use the TM com
mand if an application does not respond to your
entries.
Reconnecting to a Host or Connecting to a Different Host
For a single host system, after your terminal is dis
connected from the host, this message is printed.
Disconnecting with Host Commands
If your current application does not have a command
f o r d i r e c t d i s c o n n e c t i o n , y o u m u s t fi r s t d i s c o n n e c t
your terminal from the current program with a com
mand recognized by that application. Then you must
request host disconnection from the host. Applica
tion disconnection commands are described earlier in
this section under Switching to a Different Applica
tion.
After disconnecting the application, the system in
dicates that a connection switch is in progress by
issuing this message:
HOST DISCONNECTED. CONTROL CHARACTER = Ct
c t i s t h e n e t w o r k c o n t r o l c h a r a c t e r,
is followed by the prompting message.
This message
ENTER INPUT TO CONNECT TO HOST
You can then attempt another connection to the same
host by sending any input you want. If you have a
multihost system, typically the HAD will be dis
played between these two messages. To reach a dif
ferent host, you must complete the procedures for
Selecting a Host and Connecting to the Selected Host
described earlier in this appendix.
/ ^ v
application - CONNECT TIME hh.mm.ss.
The application that was just disconnected is indi
cated by application and the time that passed
while the terminal was connected to the program is
indicated by hh.mm.ss.
Disconnecting from One Host and Connecting to a Different
Host
You then receive another prompt for an application
program name:
You can disconnect from one host establish a connec
tion with another host using the single command
terminalname - APPLICATION:
unless the terminal is permitted access to only one
application. If so, you are disconnected from the
host anyway.
• J-18
ct HC = hn
ct is the network control character, and hn is the
name of the desired host.
60459500 C
^*^v
INTERRUPTIONS
Preventing Messages
Events can sometimes interrupt your input or output.
These interruptions fall into two categories.
Sometimes it is important that output to your
terminal does not include unplanned messages from
t h e n e t w o r k o p e r a t o r. Yo u c a n p r e v e n t d e l i v e r y o f
messages from the network operator by locking them
out with the following terminal definition command.
• Interruptions for communication with the
network operator.
• Temporary suspensions in communication.
ct LK=option
For
c t r e p r e s e n t s t h e n e t w o r k c o n t r o l c h a r a c t e r,
most asynchronous terminals this is ESC.
Communicating with the Network Operator
The term network operator includes any operator who
has access to the network, including the host oper
a t o r. A n y n e t w o r k o p e r a t o r c a n s e n d a n d r e c e i v e
messages that involve you.
After you enter this command with the option Y, any
message to your terminal from the network operator
is discarded by the network software. Messages are
discarded until you again allow delivery by using
the command with the option N.
S i t e a d m i n i s t r a t o r s c a n c o n fi g u r e y o u r t e r m i n a l s o
that messages are discarded as soon as the terminal
is connected to the network. A network application
can also change the LK option in use.
Receiving Messages
The network operator can send short messages to a
terminal. The message appears at your terminal in
this format.
FROM NOP
Suspensions of Communication
message text
These messages can appear at any time a new line of
output is possible at your terminal. For example,
the network operator might want to Inform all con
nected terminals that communication is going to be
suspended intentionally with this message.
FROM NOP
SHUTDOWN IN 5 MIN
Although storage may be low, sometimes the network
cannot prevent you from entering data. Therefore,
the network discards each message from your terminal
and sends this message to your terminal.
Sending Messages
You can respond to such messages by entering the
following terminal definition command.
ct MS=message
c t r e p r e s e n t s t h e n e t w o r k c o n t r o l c h a r a c t e r,
most asynchronous terminals this is ESC.
/ptfev
For
The message text must not exceed 50 graphic charac
ters. Because the network operator can be located
at a terminal that does not support many special
characters, you should avoid characters not in the
ASCII 63-character subset described in appendix A of
the NOS Reference Set, Volume 2, Guide to System
Usage.
You can also begin dialog with the network operator.
For example, if you need to use a remote batch
printer that has been logically disabled, the entry:
%MS=PLEASE ENABLE LP=M4C555
causes the message PLEASE ENABLE LP-M4C555 to appear
at the network operator's terminal, prefixed by the
terminal name of your terminal. The Z character
represents the network control character for your
terminal.
60459500 C
Sometimes, message traffic in the network is so heavy
that all storage is temporarily used up. Also, a
host may be too busy to accept data. During these
times, the network software takes steps that tempor
arily stop input until enough output has occurred to
free additional storage.
WAIT . .
When the following message appears, you can reenter
any information that was previously discarded.
REPEAT . .
If your terminal transmits more than one message at
a time, you must determine which information you
n e e d t o r e e n t e r. T h e a p p l i c a t i o n m i g h t h a v e
commands that can help you determine which messages
it received.
Communication Failures
Events can occur that:
• Cause your application to fail.
• Disconnect your terminal from an application.
• Disconnect your terminal from the host.
• Disconnect your terminal from the network.
J-19
Application Failures
Disconnection from the Network
If an application fails after your terminal is
connected, this message is displayed.
The network informs you that it has lost
communication with the host software by displaying
the host status message:
APPLICATION FAILED.
application CONNECT TIME hh.mm.ss.
terminalname - APPLICATION:
HOST DISCONNECTED. CONTROL CHARACTER = Ct
followed by the prompting message:
The length of time your terminal was connected to
t h e a p p l i c a t i o n i s s p e c i fi e d b y h h . m m . s s ;
application is the name of the application; and
terminalname represents the terminal name the
n e t w o r k u s e s t o i d e n t i f y t h e t e r m i n a l . Yo u e i t h e r
can select another application or log out.
ENTER INPUT TO CONNECT TO HOST
If you have a multihost system, the HAD will be
displayed between these two messages.
If you are at a dial-up terminal and you do not
attempt to connect to the same or a different host
within 2 minutes, your terminal is disconnected from
the network.
Disconnection from an Application and/or a Host
An application is Informed of two events that you
might want to take action on.
• L o n g p e r i o d s o f d e v i c e i n a c t i v i t y.
• Pending network shutdown.
The network software informs an application if more
than 10 minutes have elapsed without any
communication between a device at your terminal and
the application. An application can:
• Ignore this time interval.
• Ask you for continued dialog.
• Disconnect from your terminal or from the
device with or without telling you.
The effect of device inactivity depends on the
application with which the device is currently
connected.
When shutdown of the network is pending, the network
operator can enter a command that informs all
applications of the pending event. Your application
might take action s t h a t e i t h e r r e s u l t i n c o n n e c t i o n
termination or application failure. It also might
send you a message to warn you of the event.
If you receive a message from an application
indicating that shutdown is pending, you should take
steps immediately to save all data or files you are
currently using. Then end connection with both the
application and the host as soon as possible.
If communication between the network and the host
software resumes, you must connect to the host and
log in again but you do not need to access the net
work again (perform dial-up and auto-recognition pro
cedures). These host communication failures occur
either when the host has been shut down or when hard
ware fails in the communication path between the net
work and the host.
All network software conditions (that is, parameters
that may be set with terminal definition commands)
are retained across host disconnection except for
transparent, full ASCII, and special edit input
modes. Refer to the NOS Reference Set, Volume 3,
System Commands for a discussion of these commands.
Failures in the communication path between the net
work hardware and your terminal are treated by the
network software as if your terminal had failed.
These failures can occur because of hardware prob
lems, or maybe because you entered an input charac
ter during output. If you hold the interactive out
put interrupt key down for too long, a communication
failure can occur. This key is identified in the NOS
Reference Set, Volume 3, System Commands.
There are several tests for communication failures.
If your terminal has a CTS, ON-LINE, or CARRIER in
d i c a t o r, t h e l i g h t g o e s o u t w h e n a f a i l u r e o c c u r s .
At other terminals, if a failure has occurred, re
questing the host availability display produces no
response from the network.
Batch input and ouput devices associated with the
failed console stop running, and batch device con
nections are ended. The network software does not
distinguish between dial-up and hardwired terminals
when processing terminal failures.
Terminal failures require you to complete new access
and login procedures to resume communication with the
network. Terminal failures always cause disconnec
tion when the terminal is on a dial-up line.
• J-20
60459500 C
yS^awSX
INDEX
j f fl S S B S i ^
Accessing a host J-l
1-4
Accessing transaction subsystem
A C T 2 - 11
A f t e r i m a g e r e c o v e r y fi l e 8 - 1
AKY statement 4-1
Alternate keys 4-2
Application block header
Building 2-12
Examining 2-14
Modifying 2-12
A p p l i c a t i o n c h a r a c t e r t y p e 2 - 11
ARF 8-i
Attach mode 4-2
Audience 5
Auto-Input mode 1-3; 2-12
Automatic recovery
Description 7-1; 8-1
Report 8-4,6
Requests
Application 2-32
System 2-38
B a c k u p d i r e c t o r y fi l e 8 - 2
Batch
Interface 1-3; 5-1
Subsystem interaction 5-1
Batch output 5-4
Batch recovery 8-1
Before image recovery file 8-1
B e g i n - c o m m i t i d e n t i fi e r 7 - 1 , 3
Begin-commit sequence 7-1; 8-1
BEGIN request
Data base 7-•1,3; 8-1
TA F 2 - 2 8
BLDABH request 2 -12
B l o c k e d t a s k s I -1
•
BRF 8-1
BTASK system task
8-4
BTRAN request 5-■I; 7-1
Build ABH 2-12
BWAITINP request
2-28
Call tasks 2-4
CALLRTN 2-4
CALLTRN request 2-38; 8-1
CALLTSK 7-4,5
CALLTSK request 2-6
CDCS 1-2; 3-1; 4-4; 7-1,3
CEASE request 2-28
Chain 2-4
Change ACT 2-11
6-1
Change CMDUMP request values
Change I/O Limit 2-28
Change task field length
2-3; 10-6
Character sets A
* - l'
Character type
2-11
CLOSE requests
7-2
6-3
CMDUMP request
COMMIT requests
7-1,3; 8-1
60459500 C
Commit updates 7-3
Communication block
D e fi n e d 2 - 1
Diagram 2-2
Dump 6-4
L o a d o v e r fl o w d a t a 2 - 1 0
Release overflow data 2-23
TA F - o r i g i n a t e d t r a n s a c t i o n s 1 2 - 3 , 4
Communication recovery file
Description 4-1,8; 7-1; 8-1
Error override 8-3
Multiple 3-4
Reformat 8-3
User messages
Read 2-33
Write 2-33
Concurrent users 4-2
Confirmation message 2-35; 7-1
Create task library 10-7
C r e a t e x x J fi l e 4 - 4
CRF 4-1,8
C R M fi l e t y p e 4 - 2
CYBER Database Control System 1-1,2; 3-1; 4-4
CYBER Record Manager Data Manager 1-1,2; 4-1,2
Data base
Describe 9-1
J o u r n a l fi l e s 4 - 5
Maximum number of 4-7
Recovery 7-1; 8-1
Data manager
Concurrency l-l; 3-1
Requests 2-3
x x J fi l e s 4 - 1 , 4
Deadlocks 3-1
D e fi n e t e r m i n a l c h a r a c t e r i s t i c s
2-16
Delete tasks from task library
10-7
Describe users and data bases
9-1
Determine if user is logged In
2-31
Determine subsystem for task
2-28
Diagnostics B-l
DIAL directive 9-1
Oisable transaction recovery
8-2
DISPLAY statement 4-7
DMS statement 4-7
DSDUMP request 6-1
Dump
Communication block 6-4
Exchange package 6-4
TA F fi e l d l e n g t h 6 - 4
Ta s k fi e l d l e n g t h 6 - 3 , 4
ECS 5
End task 2-28
Entering transaction subsystem 1-4
E n t r y h e a d e r, j o u r n a l fi l e 4 - 5
ERO command 8-3
Error messages B-l
E s t a b l i s h s y s t e m i d e n t i fi e r 2 - 4 0
Index-1
Examine ABH 2-14
Execute named task 11-2
Executing transaction 7-1
E x t e n d fi e l d l e n g t h 2 - 3 ; 1 0 - 6
Extended core storage 1-5
Extended memory 5; 1-5
Extract bit string f r o m w o r d 2 - 3 1
EXTRACT request 2-31
K display commands 2-30; 4-8; 6-1,4; 8-2,3
K.DSDUMP command 6-4
K.DUMP command 6-5
K.DUMPLIM command 6-5
K.ERO command 8-3
K.INT command
8-2
K.REC command
8-3
K. statement
4-8
KDIS U-l
KPOINT request
2-30
KTSDMP utility/request 6-4
File
CRM type 4-2
D e fi n i t i o n s E - l
Descriptions E-l
Index 4-2
Files
Journal 4-5
JOURO 4-5
NCTFI 4-8
Network 4-8; 9-1
Procedure 4-1
Recoverable 8-1
Recovery 4-8; 8-1
Reserved E-2
System 4-1
TCF 4-1,7; E-l
xxJ 4-1,2,4
xxJORn 4-4
xxTASKL 10-1
Forced write indicator 4-3
F o r m a t e ff e c t o r s 2 - 1 2 , 1 5
Free requests 7-1
FSE C-6
GETABH request 2-14
Global task dump limit
GTDL 6-5
6-5
H a r d w a r e c o n fi g u r a t i o n 8 - 2
Ignore task in replacement file 10-8
11 0 r e q u e s t 2 - 2 8
Implement application 1-5
I n d e x fi l e 4 - 2
Initate a run unit 2-38
Initial task 1-3; U-l; 12-1
I n i t i a l i z e r e c o v e r y fi l e s 8 - 2
Initiate new transaction chain 2-6
Input/output
Limit 2-28
Requests 2-8
I n p u t o v e r fl o w 2 - 1 0 , 2 3
Insert bit string into word 2-31
INSERT request 2-32
I n s t a l l i n g TA F F - l
INT command 8-2
Interactive virtual terminal 1-3; 2-16
Interrogate TST 2-23
ITASK 1-4; 11-1; 12-1
ITL request 2-29
IVT 1-3; 2-16
IXN statement 4-2
J o u r n a l fi l e s 4 - 5
JOURNL request 4-5
JOURO file 4-5
• Index-2
Libraries 10-1
LIBTASK command 10-2
LIBTASK input directives 10-5
LIBTASK utility/command 10-1
Line feed and transmission keys
H-l
List tasks on library 10-3
2-10
Load overflow blocks
LOADCB request 2-10
L o c k c o n fl i c t 7 - 2
LOGIN request 2-31
1-4
Login terminal to TAF
Logout task ll-l
Logout terminal from TAF 2-29; 11-1
LOGT request 2-29
LOGT system task 11-1
Macros 12-1
Manipulate user area of TST 2-26
Memory
Changing from tasks 2-3; 10-5
Dump requests 6-1
Dumps 6-1
Requests 2-3
Message abort 11-1
Modify ABH 2-12
Modify terminal characteristics 2-16
Move data from terminal to task 2-28
MSABT ll-l
Multlmainframe 1-5
Multimainframe recovery 8-4
M u l t i p l e i n d e x e d fi l e s 4 - 2
Multiple RECOVER statements 8-3
NAM 1-3; 12-3
Named-transaction 7-1; 10-5
N C T F i fi l e 4 - 8
NDL 1-5
Network
Access Method 1-3; 12-3
D e fi n i t i o n l a n g u a g e 1 - 5
File origination 9-1
Files 4-8; 9-1
Interface 1-3
NETWORK statement 4-8; 8-3
NEWTRAN request 2-7
OFFTASK 11-2
On-line transaction processing
OPEN requests 7-2
Output from SUBMT jobs 5-4
Override 1/0 errors 8-3
l-l
60459500 C
Parameter
SEND request 2-18
Pa ra me te r ta b l e 2 - 2 5
P r o c e d u r e fi l e 4 - 1 , 4
Put recovery data on CRF
jgpss,
2-33,41
RA+1 calls 1-5; 2-1
RC parameter 7-1
RCTASK system task 11-2
Read data from terminal 2-8
Read recovery data 2-33
Read SECURE message 2-34
R e c o r d d a t a o n j o u r n a l fi l e 4 - 5
R e c o r d l o c k c o n fl i c t 7 - 2
Record locks 4-2
RECOVER statement
4-8; 8-2,3
Recoverable files
8-1
Recovery
CDCS 7-1
CDCS failure
8-5
C R F fi l e 8 - 3
Data base 7-1; 8-1
Disable 8-2
F i l e i d e n t i fi e r 4 - 8
Flag 8-4
General 7-1; 8-1
H a r d w a r e c o n fi g u r a t i o n 8 - 2
I n i t i a l i z e fi l e s 8 - 2
K display commands 4-8; 8-2
Multimainframe 8-4
Multiple data manager tasks 7-5
NAM failure 8-5
Override I/O errors 8-3
Overview 7-1; 8-1
P r o c e s s i n g fl o w 8 - 4
Requests
Application 2-33
System 2-38
System failure 8-4
TAF/CRM Data Manager 7-1
TA F f a i l u r e 8 - 4
Ta s k f a i l u r e 8 - 5
T C F fi l e 8 - 3
Te r m i n a l 7 - 4 ; 8 - 5
Tr a n s a c t i o n 7 - 1 ; 8 - 1
Recovery indicator 10-5
Application 2-32
System 2-38
Release overflow blocks 2-23
RELSCB request 2-23
Requests
Data manager 2-3
Input/output 2-8
J o u r n a l fi l e 2 - 3 ; 4 - 5
Memory 2-3
Memory dump 6-1
Message 2-4
Recovery
Application 2-32
System 2-38
System 2-3
Task
Control 2-28
Scheduling 2-4
Utility 2-30
Rerun request 2-32
R e s e r v e d fi l e s E - 2
RESTRICT clause processing 3-1
Resubmit terminal input 2-32,40
Retrieve recovery data 2-33
RGET request 2-33
RPUT request 2-33
60459500 C
RSECURE request 2-34
RTASK system task 8-4; 11-2
Complete 2-35
Initate 2-38
Running transaction 7-1
Sample deck structures D-l
Schedule tasks 2-4; 10-7
Scheduling priority 10-7
SECURE message
Acknowledge 2-36
BTRAN 2-36
Description 7-3; 8-1
Retrieve 2-34
Write 2-35
SECURE request 2-35; 7-1,3; 8-1
Send message task 11-2
Send message to user 2-17
SEND request 2-17
Set GTDL 6-5
S e t s y s t e m i d e n t i fi e r 2 - 4 0
Set time limit for task 2-29
Set transaction sequence number 2-40
Set user recovery bit 8-3
SETCHT request 2-11
Specify communication block location 2-28
SRERUN request 2-40
Start transaction using batch job 5-1
Start update sequence 7-3
STASK 11-2
Status of current transaction 2-37
Status of current user 2-37
Status of transaction 2-8
STRAN macro 12-1
Subcontrol points 1-5
Submit batch job from task 5-3
Submitting comments 5
SUBMT request 5-3
Subtransaction codes 12-1
Supervisory messages 2-11
Suspend processing 2-30
SYSMSG 11-2
System
Files 4-1
J o u r n a l fi l e s 4 - 5
Requests 2-3
Ta s k l i b r a r y 1 0 - 1
Ta s k s l l - l
TABCON statement 4-7
Tables
Te r m i n a l s t a t u s ( T S T ) 9 - 2
TAF
Automatic recovery report 8-4,6
C o n fi g u r a t i o n fi l e 4 - 7 ; E - l
Control point 1-1,2
Installation F-l
Originated transactions 12-3
P r o c e d u r e fi l e 4 - 1 , 4
Te r m i n a t i o n 8 - 5
TAF/CRM Data Manager 7-1
TAFREC 8-4
TARO request 2-26
Task
Chain 2-4
Control requests 2-28
D e fi n e d 1 - 4 ; 2 - 1
Dump 6-1
Field length changes 2-3; 10-6
Library
Index-3
Create 10-7
D e fi n e d 1 0 - 1
Delete task from 10-7
Ignore task in replacement file
List tasks 10-3
Update 10-7
Pause 2-30
Queue limit 10-6
Queuing 10-1,6,7
Residency 10-1
Scheduling priority 10-7
Scheduling requests 2-4
Ty p e 1 0 - 1
Utility requests 2-30
Ta s k l i b r a r y r e p o r t 1 0 - 3 , 4
TASKLIB 10-1
Tasks
Blocked I-I
Call 2-4
End 2-29
Schedule 2-4; 10-7
Ti m e - o r i g i n a t i n g 1 2 - 1
T C F fi l e 4 - 1 , 7 ; E - l
TERMDEF request 2-16
Terminal
Characteristics
D e fi n e 2 - 1 6 ; G - l
General 12-4,5
Modify 2-16; G-l
Definition co m m a n d s G - l
Failure 7-4; 8-5
N e t w o r k d e s c r i p t i o n fi l e 9 - 1
Recovery 7-4
Status request 12-5
Status table
Figure of 9-2
Interrogate 2-23
Manipulate user area 2-26
Recovery bit 8-3
Terminology and conventions 5
TIMCNT macro 12-1
Ti m e - o r i g i n a t i n g t a s k s 1 2 - 1
TINVOKE request 2-40
TMSG request 2-4
TOTAL Data Manager 1-1,3; 4-4; 7-5
TOTAL task area 1-1
TPSTAT request 2-28
TRAN macro 12-1
TRANCHK request 2-8
TRANS 12-1
• Index-4
10-8
Transaction
Codes 12-1
Coding 7-2
D e fi n e d 1 - 1
Named 7-1
Processing 1-4
Recovery 7-1; 8-1
Rerun 2-32
Subsystem
Entering 1-4
Interaction 5-1
TA F - o r i g i n a t e d 1 2 - 3
Tr a n s a c t i o n - I d 7 - 3
Transaction sequence number
Tr a n s i e n t t a s k a r e a 1 - 1
Transparent mode 2-12
TRANT 12-1
2-23
TSIM request
TST 9-2
TSTAT request
2-37
TTOT 12-1
12-5
Type ahead
2-2,40
Updating task library 10-7
User recovery bit 8-3
USER statement 4-8
User status 12-5
Wa i t f o r t e r m i n a l i n p u t 2 - 9
WAIT request 2-30
WAITINP request 2-9
Write data to CRF 2-33,41
WSTAT request 2-41
XTASK 11-2
XTRAN system transaction 11-2
x x J fi l e s
CDCS Data Manager 4-4
Creating 4-4
CRM Data Manager 4-2
No data manager 4-4
TO TA L 4 - 4
x x J O R n fi l e 4 - 4
x x TA S K L fi l e 1 0 - I
60459500 C
COMMENT SHEET
/0^^l
MANUAL TITLE: CDC TAF Version 1 Reference Manual
P U B L I C AT I O N
NO.:
60459500
NAME_
REVISION:
C
-
COMPANY:
STREET ADDRESS:
CITY:
.STATE:
ZIP CODE:
This form is not intended to bo used as an order blank. Control Data Corporation welcomes your evaluation of
this manual. Please indicate any errors, suggested additions or deletions, or general comments below {please
include page number references).
D Please Reply
D No Reply Necessary
/gs\, o
/p**^
NO POSTAGE STAMP NECESSARY IF MAILED IN U.S.A.
FOLD
FOLD
NO POSTAGE
NECESSARY
IF MAILED
IN THE
UNITED STATES
BUSINESS REPLY MAIL
FIRST CUSS
PERMIT NO. 8241 MINNEAPOLIS, MINN.
POSTAGE WILL BE PAID BY
CONTROL DATA CORPORATION
_i
<
Publications and Graphics Division
ARH219
4201 North Lexington Avenue
Saint Paul, Minnesota 55112
FOLD
FOLD
Source Exif Data:
File Type : PDF File Type Extension : pdf MIME Type : application/pdf PDF Version : 1.3 Linearized : No Page Count : 226 Creator : ScanSnap Manager Producer : Mac OS X 10.5.8 Quartz PDFContext Create Date : 2009:10:20 07:09:04Z Modify Date : 2009:10:20 07:09:04ZEXIF Metadata provided by EXIF.tools