|
DataMuseum.dkPresents historical artifacts from the history of: CP/M |
This is an automatic "excavation" of a thematic subset of
See our Wiki for more about CP/M Excavated with: AutoArchaeologist - Free & Open Source Software. |
top - metrics - download
Length: 58496 (0xe480)
Types: TextFile
Names: »D172«
└─⟦4b76feb82⟧ Bits:30008865 Diskette med tekster der formodes at være 31-D-163…174
└─⟦this⟧ »D172«
i
T_A_B_L_E_ _O_F_ _C_O_N_T_E_N_T_S_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _P_A_G_E_ _
1. HOST .................................................. 1
1.1 General Message/Answer Formats ................... 1
1.1.1 Message ................................... 2
1.1.2 Answer .................................... 4
2. NETWORK SUPERVISOR FUNCTIONS .......................... 6
2.1 Lookup Process ................................... 8
2.2 Lookup ........................................... 9
2.3 Lookup Reserve ................................... 10
2.4 Cancel Reservation ............................... 11
2.5 Linkup Remote .................................... 11
2.6 Linkup Local ..................................... 13
2.7 Lookup Link ...................................... 14
2.8 Release Link ..................................... 15
3. OPERATOR COMMUNICATION ................................ 16
3.1 Operator Output .................................. 16
3.2 Operator Output-Input ............................ 16
3.3 Formats .......................................... 17
\f
ii
\f
F_ 1_._ _ _ _ _ _ _ _ _H_O_S_T_ 1.
This manual describes the host process complex seen from a job
host. The protocol is used for creation and removal of links be-
tween a job host and a device host.
A link is a logical connection between a device on a device host
and a job host. When a link has been created, it is described in
an external process in the job host.
The host process complex is always included in the monitor when
RC8000/RC4000 is to work as a job host in a network, i.e. when it
has one or more SCC's or FPA's as peripheral devices. The complex
consists of a number of external processes: a main process, al-
ways by the name of 'host', and one subhost process for each SCC/
FPA connected.
The processes are used for operator communication and for control
tasks in the network.
All communication with these processes takes place via the main
process, which has to find out which subhost should handle the
operation. Messages are only accepted from internal processes
which are users of the subhost in question.
All hosts have a unique identification, the host-id. Normally
when a link is created the device is identified by its name at
the device host and the identification of the device host (dh.
host-id). It is, however, also possible only to specify some de-
mands to the device without specifying a specific device, e.g.
the kind of device, number and size of data buffers and operation
mode.
1_._1_ _ _ _ _ _ _ _G_e_n_e_r_a_l_ _M_e_s_s_a_g_e_/_A_n_s_w_e_r_ _F_o_r_m_a_t_s_ 1.1
As all host functions involve addressing of either a device host
or a device connected to a device host a common format for all
messages and answers has been introduced.
\f
1_._1_._1_ _ _ _ _ _M_e_s_s_a_g_e_ 1.1.1
Operation < 12 + function mode < 1 + address mode
first (data)
last (data)
identification field
where
- operation and function mode are specific for the function to
be executed,
- address mode defines the contents of the identification field
as described below,
- first (data) and last (data) define a data block, if the
operation is odd (or else insignificant),
- identification field defines a device or a device host either
by addressing the device (device host) directly or by stating
the address of a process description which is linked to the
device (or which is linked to a device on the device host).
address mode = 0
identification field specifies a device link or a device
host:
identification (device link):
dh.linkno < 12 + hostno
dh. host-id
dh. home-reg < 12 + dh. net-id
jh. host-id
jh. linkno < 12 + jh net-id
identification (device host):
unused < 12 + hostno
dh. host-id
dh. home-reg < 12 + dh. net-id
where
dh. linkno (8) indicates the link number in the device
host \f
hostno (12) states the logical device number for the
external process, representative subhost
which is to handle the operation,
dh. host-id(16) and
dh. net-id (8) address the device host,
dh. home-reg(ion)(8) is a utility parameter stating in which
area of the network the device host in
question should be found,
jh. linkno(8) defines a link number in a jobhost (if
the jobhost is RC8000/4000 the link num-
ber is equal to the logical device number
for the external process representing the
device),
jh. host-id(16) and
jh. net-id (8) define the job host. The value 0 in the
jh. host-id field causes the host process
to set the jh. host-id and net-id, to the
equivalent values for the sender host.
Figures in parenthesis indicate the maximum size of the par-
ameter (in bits). If this is exceeded the operation will re-
turn immediately with result 3.
address mode = 1
identification-field contains the address of an external pro-
cess, which - in case a device link is to be defined - has to
be linked to the device or - if the addressing defines a
device host - has to be linked to a device on the device host
in question.
identification (device link):
process description address of the external process linked to
the device
identification (device host):
process description address of the external process linked to
a device on the device host
\f
If the process description address does not point out a process
linked to a device on the device host, the operation immediately
returns with result 3.
1_._1_._2_ _ _ _ _ _A_n_s_w_e_r_ 1.1.2
Return value
number of halfwords received
number of chars received
dh. linkno < 12 + hostno
dh. host-id
dh. home-reg < 12 + dh. net-id
where
- return value = device status < 16 + link desc. < 12 + funct.
result
F_u_n_c_t_i_o_n_ _r_e_s_u_l_t_:
-1 SENDER STOPPED
0 FUNCTION EXECUTED
1 DEVICE TROUBLES (SPECIFIED IN DEVICE STATUS)
2 DEVICE RESERVED BY OTHER HOST
3 NO RESOURCES AT JOBHOST
4 NO RESOURCES AT DEVICEHOST
5 TIMEOUT
6 DEVICE REQUESTED WITH HIGHER PRIORITY
(examples of this may be that another LOOKUP LINK LOCAL has
already been received)
8 dh. unknown
L_i_n_k_d_e_s_c_r_i_p_t_o_r_: (relevant only for function result <> -1)
Specifies the interpretation of the fields JOBHOST ID and
JOBHOST LINKNO in the datablock
0 No linked present
1 Remote linked subprocess present
2 Local linked subprocess present
\f
D_e_v_i_c_e_ _S_t_a_t_u_s_ (Relevant only when function result = 1):
Bit 0 Device unknown
- 1 Device closed
- 2
- 3
- 4
- 5 Device driver not loaded
- 6 Device reserved by another process
- 7 Reservation rejected from AP (only GAC - interfacing)
- number of halfwords received and
- number of chars received indicate the size of the data block
received in the data buffer at sender's process. The fields
will be 0, if the operation executed does not involve input of
data or if sender was stopped when data were received from the
device host.
- the remaining parameters are described later on, however, it
should be mentioned that dh. linkno is only significant if a
device link has been addressed in the message.
\f
F_ 2_._ _ _ _ _ _ _ _ _N_E_T_W_O_R_K_ _S_U_P_E_R_V_I_S_O_R_ _F_U_N_C_T_I_O_N_S_ 2.
The network supervisor functions are a group of operations used
for supervising and controlling the network.
These functions are usually performed as output-input operations,
i.e. a databuffer is sent to the device host and then, when the
device host has handled the operation, the data containing
answers are received in the original output area.
The data area contains parameters as kind, buffer specification
and device name. The general format is described below.
The network supervisor functions are lookup, lookup reserve, can-
cel reservation, link up remote, lookup link local and release
link.
The format of the data areas used in network supervisor oper-
ations is:
output input
mode < 12 + kind kind
timeout < 12 + buffers max. no. of buffers
buffersize max. buffersize
devicename (0:1) devicename (0:1)
- (2:3) - (2:3)
- (4:5) - (4:5)
- (6:7) - (6:7)
jh. linkno jh. linkno
jh. host-id jh. host-id
jh. home-reg < 12 + jh. net-id jh. home-reg < 12 + jh. net-id
(unused) process description
The format of the individual operation is described later on. If
a field is described as unused the value is of no importance. A
field can be set to 'dummy' value, and is then regarded as irrel-
evant.
\f
dummy value = 0 for buffers, buffersize, devicename
(first char (name) = 0),
dummy value = -1 for mode, kind.
Below the meaning of the individual fiels is described. The
figures in parenthesis indicate the size of the important part of
the field. If this is exceeded the operation will - apart from
dummy value - return with result 3.
mode (8) specifies that the device should be able to
operate in this mode;
kind (8) defines the type of the device,
timeout (8) states the time out value for the operation
buffers (8) specifies the wanted number of operations,
which at the same time should be able to be
sent out from the job host to the device
host,
bufferzise (16) indicates the data block size wanted (in
characters), which one at a time can be
sent to the device,
devicename (12 chars) fixes the name of the device in the device
host (is unrelated to the process name in
the job host),
max buffers (8) states the greatest number of operations
which at the same time can be sent out to
the device,
max bufsize (16) states the size of the greatest data
block, which can be transferred at a time
to the device (in characters). The size is
not necessarily the greatest buffer which
can be sent from an internal process,
jh. linkno (10) specifices linkno for the external process
in job host. If the job host is RC8000/
RC4000 then the linkno is equal to the
logical device number,
jh. host-id (16), define the job host. Host-id is a number,
jh. net-id (8) uniquely defining the host inside a network
determined by net-id, \f
jh. home-reg (8) is a utility parameter stating where the
host in question is to be found in the net-
work,
proc desc (24) indicates the process description address
for the external process, which is defined
by jh. linkno in case the job host is
sender host.
2_._1_ _ _ _ _ _ _ _L_o_o_k_u_p_ _P_r_o_c_e_s_s_ 2.1
The lookup process operation is used for retrieving the par-
ameters from an external process possibly linked to a device.
The data format is the standard data format except for device
name, which is the name of the external process in the job host.
message:
1 < 12 + 2 < 1 + 1
first (data)
last (data)
proc desc (external process)
answer:
return value
number of halfwords
number of chars
dh. linkno < 12 + hostno
dh. host-id
dh. home-reg < 12 + dh. net-id
data:
output: none
input: kind (sub)
max. buffers
max. buffersize
name of external process
- -
- -
- - \f
jh. linkno
jh. host-id
jh. home-reg < 12 + jh. net-id
process description of external process
2_._2_ _ _ _ _ _ _ _L_o_o_k_u_p_ 2.2
The lookup function examines the parameters for a peripheral,
e.g. when all parameters of a peripheral given by a device name
are to be known, or if it is desirable to examine whether a pe-
ripheral exists fulfilling one or more demands on the parameters'
mode, kind, buffers and/or buffer size. Irrelevant parameters are
given dummy value.
F_o_r_m_a_t_s_
message:
1 < 12 + 3 < 1 + address mode
first (data)
last (data)
identification (device host)
answer:
return value
number of halfwords received
number of chars received
dh. linkno < 12 + hostno
dh. host-id
dh. home-reg < 12 + dh. net-id
data
output
+0 mode < 12 + kind
+2 buffers
+4 buffer size
+6 device name (0:1)
+8 - (2:3)
+10 - (4:5)
+12 - (6:7) \f
+14 unused
+16 unused
+18 unused
+20 unused
input:
+0 kind
+2 max buffers
+4 max buffer size
+6 device name (0:1)
+8 - (2:3)
+10 - (4:5)
+12 - (6:7)
+14 unused
+16 unused
+18 unused
2_._3_ _ _ _ _ _ _ _L_o_o_k_u_p_ _R_e_s_e_r_v_e_ 2.3
This function performs a lookup as described earlier. If the de-
vice exists it is reserved, which means that links to the device
can only be established on initiative of the sender host (called
reserver host).
F_o_r_m_a_t_s_
message:
1 < 12 + 4 < 1 + address mode
first (data)
last (data)
identification (device host)
answer:
as in lookup.
data:
as in lookup.
\f
2_._4_ _ _ _ _ _ _ _C_a_n_c_e_l_ _R_e_s_e_r_v_a_t_i_o_n_ 2.4
A reservation made by lookup reserve is removed by cancel
reservation. The reservation can only be removed from reserver
host.
F_o_r_m_a_t_s_
message:
1 < 12 + 5 < 1 + address mode
first (data)
last (data)
identification (device host)
answer:
return value
0
0
data:
output as by lookup.
input does not take place.
2_._5_ _ _ _ _ _ _ _L_i_n_k_u_p_ _R_e_m_o_t_e_ 2.5
The operation linkup remote is used to establish a temporary link
to a device specified by parameter conditions in data (as by
lookup). The link can be established for either the sender job
host or another job host. If the device is occupied it is indi-
cated by timeout how long the operation can wait before it is re-
turned.
If the operation results in the establishment of a link to
RC8000/RC4000 the external process representing the peripheral
will get the work name 'subxxx', where xxx is a number between
000 and 999. At the establishment it is controlled that there is
not already a process (external, internal or area) of the same
name. If the link is established to sender host then only the
sender of the linkup operation will become user of the external
process. On the other hand if the job host is another RC8000/\f
RC4000 than the sender host then all internal processes on that
job host which are users of the subhost 'facing' the device host
will be included as users of the newly established process.
F_o_r_m_a_t_s_
message:
1 < 12 + 6 < 1 + address mode
first (data)
last (data)
identification (device host)
answer:
return value
number of halfwords received
number of chars received
dh. linkno < 12 + hostno.
dh. host-id
dh. home-reg < 12 + dh. net-id
data
output:
+0 mode < 12 + kind
+2 timeout < 12 + buffers
+4 buffer size
+6 device name (0:1)
+8 - (2:3)
+10 - (4:5)
+12 - (6:7)
+14 unused
+16 jh. host-id
+18 jh. home-reg < 12 + jh. net-id
+20 unused
values of timeout can be interpreted as follows:
timeout = 0 do not wait
< 128 wait for up to 'timeout' minutes for the device
to be unoccupied
>_ 128 wait until the device is set free.
\f
If jh. host has the value 0 then sender host is set in as job
host.
input:
+0 kind
+2 max. buffers
+4 max. buffersize (chars)
+6 devicename (0:1)
+8 - (2:3)
+10 - (4:5)
+12 - (6:7)
+14 jh. linkno
+16 jh. hostid
+18 jh. home-reg < 12 + jh. net-id
+20 process description
2_._6_ _ _ _ _ _ _ _L_i_n_k_u_p_ _L_o_c_a_l_ 2.6
This function establishes a local link to a device. The specifi-
cation of the device takes place as by lookup, however, an exter-
nal process description should also be pointed out in the job
host (which can only be sender host). If the device is already
connected to the sender host - whether as local or remote device
- this link will be cancelled first. When establishing the exter-
nal process the sender of the 'linkup local' operation and all
the ancestors of sender are included as users. Furthermore the
process is named as described in 'linkup remote'.
The external process to which the link is to be connected must be
unused. This is defined by jh. linkno (= logical device number).
F_o_r_m_a_t_s_
message:
1 < 12 + 7 < 1 + address mode
first (data)
last (data)
identification (device host)
\f
answer:
as for linkup remote
data
output:
+0 mode < 12 + kind
+2 buffers
+4 buffersize
+6 devicename (0:1)
+8 - (2:3)
+10 - (4:5)
+12 - (6:7)
+14 jh. linkno (= logical deviceno)
+16 unused
+18 unused
+20 unused
input:
+0 kind
+2 max buffers
+4 max buffersize
+6 device name (0:1)
+8 - (2:3)
+10 - (4:5)
+12 - (6:7)
+14 jh. linkno
+16 jh. host-id
+18 jh. home-reg < 12 + jh. net-id
+20 process description addr
jobhost in input data is the same as sender host.
2_._7_ _ _ _ _ _ _ _L_o_o_k_u_p_ _L_i_n_k_ 2.7
Lookup link is used for examination of the parameters for an
existing link. The operation can be executed on both links to
sender host and other job hosts.
\f
F_o_r_m_a_t_s_
message:
1 < 12 + 8 < 1 + address mode
first (data)
last (data)
identification (device link)
answer:
as by linkup remote.
data
output:
no datablock is sent.
input:
as by linkup remote.
2_._8_ _ _ _ _ _ _ _R_e_l_e_a_s_e_ _L_i_n_k_ 2.8
This operation makes it possible to cancel links. The removal of
the link does not wait for the device to complete commenced oper-
ations if any. Answer to release link can be handed over before
the external process is removed, as the device host answers the
release operation immediately.
Links can only be cancelled from hosts which are job host or re-
server host to the link. The operation involves no data trans-
port.
F_o_r_m_a_t_s_
message:
2 < 12 + address mode
unused
unused
identification (device link)
answer:
as by linkup remote.
\f
F_ 3_._ _ _ _ _ _ _ _ _O_P_E_R_A_T_O_R_ _C_O_M_M_U_N_I_C_A_T_I_O_N_ 3.
The two operator operations 'operator output' and 'operator out-
put-input' are introduced to make it easier to communicate with
the operator of a device (or of a device host), as it is possible
to write messages and to return the answer from the operation
without having to establish a link to the operator terminal. The
communication device - the operator terminal - is specified by
stating the device name in the 12 first characters of the output
block. If the value of this field is set to dummy (first charac-
ter = 0), the communication will take place on a terminal defined
by the device host.
The communication can be of either a general kind or concern a
specific device (e.g. an error message), which is stated in func-
tion mode. In the last case the device host will add a specifica-
tion of the device, which might consist of the device name.
3_._1_ _ _ _ _ _ _ _O_p_e_r_a_t_o_r_ _O_u_t_p_u_t_ 3.1
This operation writes out 'outtext' from data until the data buf-
fer is emptied or until it has met and printed an 'nl' character.
3_._2_ _ _ _ _ _ _ _O_p_e_r_a_t_o_r_ _O_u_t_p_u_t_-_I_n_p_u_t_ 3.2
Output is written out as mentioned above. When the output is ter-
minated it switches to input. After this the operator can key in
an answer line. If the length of the answer exceeds the buffer
size the input operation is terminated.
\f
3_._3_ _ _ _ _ _ _ _F_o_r_m_a_t_s_ 3.3
message:
operation < 12 + function mode < 1 + address mode
first (data)
last (data)
identification field
where
operation: 9 operator output
11 operator output-input
function mode: 0 specific mode: The operation concerns a
specific device, and the identification
field addresses a device link,
1 generel mode: The operation is of a gen-
eral kind and the identification field
addresses a device host.
answer:
return value
number of halfwords received
number of chars received
dh. linkno < 12 + hostno
dh. host-id
dh. home-reg < 12 + dh. net-id
where
dh. linkno is dummy for function mode = 1.
return value: -1 operation rejected (sender stopped)
0 operation performed without troubles
1 operation rejected by device host
2 operator terminal malfunctioning
\f
data
output:
+0 device name of operator terminal (0:1)
+2 - - - - - (2:3)
+4 - - - - - (4:5)
+6 - - - - - (6:7)
+8 start of outtext
....
last of buffer
input:
+0 start of intext
....
....
last of buffer
\f
i
T_A_B_L_E_ _O_F_ _C_O_N_T_E_N_T_S_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _P_A_G_E_
1. INTRODUCTION ........................................... 1
2. INSTALLATION ........................................... 2
2.1 Installation with a Predefined ITT3290 Configuration 2
2.2 Installation with a Special Configuration ......... 2
A_P_P_E_N_D_I_X_:
A. REFERENCES ............................................. 3
\f
ii
\f
F_ 1_._ _ _ _ _ _ _ _ _I_N_T_R_O_D_U_C_T_I_O_N_ 1.
This manual describes the implementation of CIS COBOL Forms-2 1.3
on the ITT 3290 Intelligent Terminal Work Station.
The Forms-2 package is an extension to the CIS COBOL package,
which is assumed to have been installed on your ITT 3290
Intelligent Terminal Work Station, see ref. 1.
The Forms-2 package you have received consists of the following
items:
- C_I_S_ _C_O_B_O_L_ _F_O_R_M_S_-_2_ _U_t_i_l_i_t_i_y_ _M_a_n_u_a_l_
- S_o_f_t_w_a_r_e_ _I_s_s_u_e_ _B_u_l_l_e_t_i_n_ _N_o_ _1_7_
- C_I_S_ _C_O_B_O_L_ _F_o_r_m_s_-_2_ _I_s_s_u_e_ _D_i_s_k_
- C_I_S_ _C_O_B_O_L_ _F_o_r_m_s_-_2_ _f_o_r_ _t_h_e_ _I_T_T_ _3_2_9_0_ _I_n_t_e_l_l_i_g_e_n_t_ _T_e_r_m_i_n_a_l_
W_o_r_k_ _S_t_a_t_i_o_n_,_ _I_n_s_t_a_l_l_a_t_i_o_n_ _G_u_i_d_e_
Your copy of CIS COBOL Forms-2 for the ITT 3290 Intelligent
Terminal Work Station has been provided with a serial number, and
it is only to be used in accordance with the Software License
Agreement.
\f
2_._ _ _ _ _ _ _ _ _I_N_S_T_A_L_L_A_T_I_O_N_ 2.
Start by making 2 copies of your CIS COBOL FORMS-2 diskette for
backup purposes.
Transfer all CIS COBOLFORMS-2 files to a system diskette.
If you want your extended CIS COBOL system to have a predefined
ITT3290 configuration, follow the procedure outlined in section
2.1.
On the other hand, if you require a special configuration, follow
the procedure outlined in section 2.2.
For more details on how to get started with the FORMS-2 Utility,
see the C_I_S_ _C_O_B_O_L_ _F_O_R_M_S_-_2_ _U_t_i_l_i_t_y_ _M_a_n_u_a_l_, chapter 1.
2_._1_ _ _ _ _ _ _ _I_n_s_t_a_l_l_a_t_i_o_n_ _w_i_t_h_ _a_ _P_r_e_d_e_f_i_n_e_d_ _I_T_T_3_2_9_0_ _C_o_n_f_i_g_u_r_a_t_i_o_n_ 2.1
FORMS-2 has already been configured to execute with ITT3290. Once
FORMS-2 has been transferred to a system diskette, no further
installation is necessary.
Please note that the implementation of the cursor control keys in
table 1-1 of the C_I_S_ _C_O_B_O_L_ _F_O_R_M_S_-_2_ _U_t_i_l_i_t_y_ _M_a_n_u_a_l_ has been
changed as shown in ref. 1, fig. 1.
2_._2_ _ _ _ _ _ _ _I_n_s_t_a_l_l_a_t_i_o_n_ _w_i_t_h_ _a_ _S_p_e_c_i_a_l_ _C_o_n_f_i_g_u_r_a_t_i_o_n_ 2.2
To install FORMS-2 to run with a special configuration, it is
necessary to execute CONFIG, a utility program. For further
information, see chapter 5 of the C_I_S_ _C_O_B_O_L_ _O_p_e_r_a_t_i_n_g_ _G_u_i_d_e_._ A
description of the character codes for the ITT3290 keyboard may
be found in ref. 2.
\f
F_ A_._ _ _ _ _ _ _ _ _R_E_F_E_R_E_N_C_E_S_ A.
1 RCSL No 42-i 2161:
CIS COBOL for the ITT 3290 Intelligent Terminal Work
Station, Installation Guide
2 RCSL No 42-i2134:
ITT 3290 Intelligent Terminal Work Station
CP/M Operating System, User's Guide
\f
F_
\f
\f
i
T_A_B_L_E_ _O_F_ _C_O_N_T_E_N_T_S_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _P_A_G_E_ _
1. INTRODUCTION .......................................... 1
2. CALL .................................................. 2
3. OPERATION AND PREREQUISTES ............................ 3
3.1 Message and Data Formats ........................ 4
3.2 Limitations ...................................... 5
4. ERROR MESSAGES ........................................ 6
A_P_P_E_N_D_I_X_:
A. REFERENCES ............................................ 9
\f
ii
\f
1_._ _ _ _ _ _ _ _ _I_N_T_R_O_D_U_C_T_I_O_N_ 1.
This manual contains information about the remotejob utility
program.
The program remotejob is intended for use at installations where
several RC8000 computers are interconnected via DDFR-FDLC-links
1, 2. The program makes it possible to start a boss job at a
remote RC8000 computer by means of an fp program call.
\f
2_._ _ _ _ _ _ _ _ _C_A_L_L_ 2.
The syntax for the call of remotejob is:
M_m_m_ 1
remotejob<s'<host'<s'<jobfile' <s'<printer'
P_p_p_ 0
<host': is an integer specifying the remote RC8000 1,
<jobfile': is the name of jobfile at the remote RC8000,
<printer': is the name of an entry describing a printer. (Only
the first 6 characters are used, the entry must
reside at the remote RC8000).
<host', <jobfile', and <printer' must fulfil the syntax described
in 5.
\f
3_._ _ _ _ _ _ _ _ _O_P_E_R_A_T_I_O_N_ _A_N_D_ _P_R_E_R_E_Q_U_I_S_I_T_E_S_ 3.
Remotejob will establish a communication with a process named
boss in a remote RC8000 computer connected via a ddfr-fdlc-link.
A description of the system components involved is shown below.
DDFR: D_isc to d_isc f_ile r_outer
FDLC: F_pa d_ata L_ink c_ontrol
FPAD: F_p_a_ d_river complex
FPA : F_rontend p_rocessor a_dapter
FOA : F_iber o_ptic a_dapter
FOC : F_iber o_ptic c_able
CBL : C_ab_l_e_
Fig.1 System components.
Remotejob will send a message to ddfr requesting a message be
send to the process named boss in the specified host. Remotejob
will await the answer and print the result.
\f
3_._1_ _ _ _ _ _ _ _M_e_s_s_a_g_e_ _a_n_d_ _D_a_t_a_ _F_o_r_m_a_t_s_ 3.1
The message send to ddfr will have the following format
+0 7 < 12+0
+2 first output area address
+4 last output area address
+6 first input area address
+8 last input area address
The output area will hold this information
M_m_m_ + 0
receiver:
P_p_p_ + 2
+ 4 "boss" information used by the ddfr program
+ 6
+ 8 <host'
+10 0
+12 12 < 12 + 0 message:
+14 "job"
M_m_m_ +16
<printer' message which will be
P_p_p_ +18 send to the receiver (boss)
+20
M_m_m_ +22
<jobfile'
P_p_p_ +24
+26
The answer will have the same format as described in 1, 3 more
status results have been added though.
status explanation.
34 answer block expected, received block <explain 1',
35 time out, no answer from process in remote host
within 1 minut, the message is regretted,
36 monitor 84 (general copy) alarm, <result' (this
should not happen when using remotejob). \f
If bit 0 (1 < 23) in the status word is set this indicates that
the process where remotejob runs was stopped as the answer
arrived.
If status is 0 the input area will contain the following:
+ 0 result result of wait answer at remote host
+ 2
+ 4
+ 6
+ 8 answer answer if result = 1
+10
+12
+14
+16
3_._2_ _ _ _ _ _ _ _L_i_m_i_t_a_t_i_o_n_s_ 3.2
The jobfile must be visible from the standard base of the ddfr
process at the remote host, this normally implies that the file
must have system scope.
Ddfr will refuse to send a message with odd operation or with the
wait bit set (see 6).
\f
4_._ _ _ _ _ _ _ _ _E_R_R_O_R_ _M_E_S_S_A_G_E_S_ 4.
If ddfr does not exist, the following message is given:
***remotejob status ddfr: process does not exist
if the user process was stopped when the answer arrives the
following message is printed:
***remotejob status ddfr stopped
if the result is otherwise 0 the following additional message is
given:
message send to boss, answer could not be received
in this case is it not possible to know if a job was started at
the remote host or not.
If the status is not 0, the message ***remotejob result:
followed by one of the following messages is written.
1, all lines busy
3, wrong length of data
4, host unknown <host'
5, line not ready, state = <state'
8, hostmix1, trimming error
9, hostmix2, trimming error
10, fdlc input error, status = <status'
34, answer block expected, received: <block type'
35, boss did not answer within 1 minut, message regretted
36, monitor 84 alarm. result = <result'
If the status word is 0 and the result of wait answer at the
remote host is not 1, the following message is written:
***remotejob device status boss, rejected, untelligible,
disconnected, process does not exist.
\f
otherwise the result from boss is printed, this will be one of
the following.
job enrolled (not an error message)
***job queue full
***file not permanent
***file does not exist
***file unreadable
***user index too large
***illegal identification
***user index conflict
***file too long
***attention status at remote batch terminal
***device unknown
***device not printer
***parent device disconnected
***option unknown
***param at job
***syntax at job
***line too long
If the job is not enrolled the ok bit will be set to false.
\f
\f
A_._ _ _ _ _ _ _ _ _R_E_F_E_R_E_N_C_E_S_ A.
1. RCSL No 31-D579:
Transfer Discfile (xdif) Utility Program and Disc to Disc
File Router Reference Manual.
2. RCSL No 31-D592:
FDLC User>s Manual.
3. RCSL No 31-D477:
Monitor Manual, Part 2.
4. RCSL No 31-D584:
Corrections to RC8000 Monitor Reference Manual Part 2, RCSL
31-D477.
5. RCSL No 31-D364:
SYSTEM 3 UTILITY PROGRAMS Part One.
6. RCSL No 31-D610:
Parent Message in RC8000.
\f
i
T_A_B_L_E_ _O_F_ _C_O_N_T_E_N_T_S_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _P_A_G_E_ _
1. GENEREL DESCRIPTION ................................... 1
2. SPECIFICATION ......................................... 2
2.1 Performance Specifications ....................... 2
2.2 Electrical Specifications ........................ 2
2.3 Environmental Specifications ..................... 2
2.4 Physical Specifications .......................... 2
3. INSTALLATION .......................................... 3
3.1 Installation of CAM801 ........................... 3
3.2 Switches and Strappings .......................... 3
3.3 Deskew Delay Adjustments ......................... 4
4. Check Out Procedures .................................. 5
\f
ii
\f
1_._ _ _ _ _ _ _ _ _G_E_N_E_R_E_L_ _D_E_S_C_R_I_P_T_I_O_N_ 1.
The CAM801 is a cache memory which in connection with the CPU820
form the RC8000 model 55.
It contains 4k words of high speed memory with possibility for
upgrading to 8k words. The data flow between cache memory and
main memory is fully controled by the CAM801, which also has a
bussupervisor unit to controle data flow to and from the main
memory to update the cache if needed.
\f
2_._ _ _ _ _ _ _ _ _S_P_E_C_I_F_I_C_A_T_I_O_N_ 2.
2_._1_ _ _ _ _ _ _ _P_e_r_f_o_r_m_a_n_c_e_ _S_p_e_c_i_f_i_c_a_t_i_o_n_s_ 2.1
Access time chip level: 55ns max.
Access time board level: 150ns
2_._2_ _ _ _ _ _ _ _E_l_e_c_t_r_i_c_a_l_ _S_p_e_c_i_f_i_c_a_t_i_o_n_s_ 2.2
Supply voltage 5V +_ 5%
Current requirement 9A
2_._3_ _ _ _ _ _ _ _E_n_v_i_r_o_n_m_e_n_t_a_l_ _S_p_e_c_i_f_i_c_a_t_i_o_n_s_ 2.3
Ambient temperature 10-35C
Relative Humidity 20-80% without condensation
Heat dissipation 45W
2_._4_ _ _ _ _ _ _ _P_h_y_s_i_c_a_l_ _S_p_e_c_i_f_i_c_a_t_i_o_n_s_ 2.4
Space requirement 2 slots in RC8000.
\f
3_._ _ _ _ _ _ _ _ _I_N_S_T_A_L_L_A_T_I_O_N_ 3.
3_._1_ _ _ _ _ _ _ _I_n_s_t_a_l_l_a_t_i_o_n_ _o_f_ _C_A_M_8_0_1_ 3.1
The CAM801 is installed in a standard RC8000 chassis, CHS815 or
equivalent.
CBL929 is used to connect CPU822 with CAM801. Mount the cabel at
connector 1005 on both boards.
3_._2_ _ _ _ _ _ _ _S_w_i_t_c_h_e_s_ _a_n_d_ _S_t_r_a_p_p_i_n_g_s_ 3.2
The CAM has 10 switches in position 95. Switch 0 is on pin 11-10
and switch 9 is on pin 20-1.
switch 0 ON: Select set 0
1 - 1
2 Power switch off
3 Not used
4 Slow read cycle
5 Fast read cycle
6 Set 0 Hit disable
7 - - - enable
8 Set 1 Hit disable
9 - - - enable
With the normal 4k of cache the switches must be (1 = on, 0 =
off, on means red dot visible):
Switch (0:9) = (1010010110)
With 8k the switches must be
Switch (0:9) = (0010100101)
The CAM also has 2 switches in position 130. They are used to
disable parity lamps, and are normally always on. Pin 1-20 for
set 0 and pin 2-19 for set 1.
\f
3_._3_ _ _ _ _ _ _ _D_e_s_k_e_w_ _D_e_l_a_y_ _A_d_j_u_s_t_m_e_n_t_s_ 3.3
The deskew delays for SELIN and ACK/NACK are adjusted by means of
the potentiometers P1 and P2. The potentiometers are located on
the CAM801 board position 120.
For adjustment the delays may be activated by means of a micro-
programmed test loop.
The test loop is started from the technicians console by means of
the command T5.
The following procedure is recommended for an initial adjustment
of the delays.
1. Turn the potentiometers fully clockwise (maximum delay).
2. Start the test loop.
3. Adjust the delay according to figures below.
P1
selin (119-5)
(109-3)
P2
ACK (142-6)
SET STATUS
(26-11)
\f
4_._ _ _ _ _ _ _ _ _C_h_e_c_k_ _O_u_t_ _P_r_o_c_e_d_u_r_e_s_ 4.
On installation and after repair a test of CAM801 must be carried
out.
The CAM801 is tested with the microprogram in the CPU. Note that
the standard memory test also can be used as cache test on the
RC8000 model 55.
\f
i
T_A_B_L_E_ _O_F_ _C_O_N_T_E_N_T_S_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _P_A_G_E_ _
1. DESCRIPTION ............................................ 1
1.1 Diagram R13068 .................................... 2
\f
ii
\f
1_._ _ _ _ _ _ _ _ _D_E_S_C_R_I_P_T_I_O_N_ 1.
The purpose of the circuit is to meet IBM>s demand of full power
control with satelite-equipment.
The PDP708 contains the neccessary relays and power supply for
these for enabling full EOP-control to be maintained from the IBM
system for two units.
The IBM EPO system sequences power up on the different attached
units in a sequence defined by the order in which these Units EPO
cables are connected to the system.
Powering up of a single unit is accomplished in the following
way (refer to the diagram):
1. The system EPO contact is closed.
2. The POWER ON contact is closed.
3. The powerpick line is connected to the powerhold line, ener-
gizing R3.
4. R3 energizes R1, closes the hold contact (8,12) and the
POWERING COMPLETE contact (5,9), allowing the system to
proceed with powerpicking of the next unit.
5. The system opens the powerpick contact, leaving the POWER ON
contact on.
The PDP708 is equipped with POWERPICK OVERRIDE switch, by means
of which the R3 relay may be forced to follow the POWER ON
contact (not awaiting power pick).
\f
1_._1_ _ _ _ _ _ _ _D_i_a_g_r_a_m_ _R_1_3_0_6_8_ 1.1
\f
i
T_A_B_L_E_ _O_F_ _C_O_N_T_E_N_T_S_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _P_A_G_E_
1. INTRODUCTION ........................................... 1
2. INSTALLATION ........................................... 2
2.1 Installation with a Predefined RC702 or RC855
Configuration ..................................... 2
2.2 Installation with a Special Configuration ......... 2
A_P_P_E_N_D_I_X_:
A. REFERENCES ............................................. 3
\f
ii
\f
F_ 1_._ _ _ _ _ _ _ _ _I_N_T_R_O_D_U_C_T_I_O_N_ 1.
This manual describes the implementation of CIS COBOL Forms-2 1.3
on the RC702/RC855 Microcomputer System.
The Forms-2 package is an extension to the CIS COBOL package,
which is assumed to have been installed on your RC702/RC855
Microcomputer System, see ref. 1.
The Forms-2 package you have received consists of the following
items:
- C_I_S_ _C_O_B_O_L_ _F_O_R_M_S_-_2_ _U_t_i_l_i_t_y_ _M_a_n_u_a_l_
- S_o_f_t_w_a_r_e_ _I_s_s_u_e_ _B_u_l_l_e_t_i_n_ _N_o_ _1_7_
- C_I_S_ _C_O_B_O_L_ _F_o_r_m_s_-_2_ _I_s_s_u_e_ _D_i_s_k_
- C_I_S_ _C_O_B_O_L_ _F_o_r_m_s_-_2_ _f_o_r_ _t_h_e_ _R_C_7_0_2_/_R_C_8_5_5_ _M_i_c_r_o_c_o_m_p_u_t_e_r_
S_y_s_t_e_m_,_ _I_n_s_t_a_l_l_a_t_i_o_n_ _G_u_i_d_e_
Your copy of CIS COBOL Forms-2 for the RC702/RC855 Microcomputer
System has been provided with a serial number, and it is only to
be used in accordance with the Software License Agreement.
\f
2_._ _ _ _ _ _ _ _ _I_N_S_T_A_L_L_A_T_I_O_N_ 2.
Start by making 2 copies of your CIS COBOL FORMS-2 diskette for
backup purposes.
Transfer all CIS COBOLFORMS-2 files to a system diskette.
If you want your extended CIS COBOL system to have a predefined
RC702 or RC855 configuration, follow the procedure outlined in
section 2.1.
On the other hand, if you require a special configuration, follow
the procedure outlined in section 2.2.
For more details on how to get started with the FORMS-2 Utility,
see the C_I_S_ _C_O_B_O_L_ _F_O_R_M_S_-_2_ _U_t_i_l_i_t_y_ _M_a_n_u_a_l_, chapter 1.
2_._1_ _ _ _ _ _ _ _I_n_s_t_a_l_l_a_t_i_o_n_ _w_i_t_h_ _a_ _P_r_e_d_e_f_i_n_e_d_ _R_C_7_0_2_ _o_r_ _R_C_8_5_5_ _C_o_n_f_i_g_u_r_a_t_i_o_n_ 2.1
You can install the FORMS-2 package by simply following the
example in appendix C of ref. 1, substituting the file name
FORMS2.COM for RUNA.COM. For a more detailed description, see
chapter 1 of the C_I_S_ _C_O_B_O_L_ _F_O_R_M_S_-_2_ _U_t_i_l_i_t_y_ _M_a_n_u_a_l_ and note the
following changes:
- The file CONFIG.COM includes predefined configurations for
the RC702 and RC855.
- The implementation of the cursor control keys shown in
table 1-1 has been changed, as shown in ref. 1, fig. 1.
2_._2_ _ _ _ _ _ _ _I_n_s_t_a_l_l_a_t_i_o_n_ _w_i_t_h_ _a_ _S_p_e_c_i_a_l_ _C_o_n_f_i_g_u_r_a_t_i_o_n_ 2.2
If you require a special configuration, please refer to chapter 5
of the C_I_S_ _C_O_B_O_L_ _O_p_e_r_a_t_i_n_g_ _G_u_i_d_e_. A description of the character
codes for the RC702/RC855 keyboard may be found in ref. 1.\f
F_ A_._ _ _ _ _ _ _ _ _R_E_F_E_R_E_N_C_E_S_ A.
1 RCSL No 42-i 2059:
CIS COBOL for the RC702/RC855 Microcomputer System,
Installation Guide
\f
F_
\f
«eof»