Initializing the Controller
The initialization of the controller includes MOSS initial microprogram load (IML),
scanner IML, channel adapter initialization, and control program load.
It can be invoked under the following conditions:
Automatically, at power-on, or at auto-restart
|
Automatically, at a scheduled time without any operator action (Timed IPL).
At the request of the host via a host channel or a telecommunication line (in
this case, the MOSS IML is not invoked)
At the request of the MOSS operator from the control panel
From the controller hard disk. This allows automatic re-IPL, for example in
case of CCU failure. Assume that:
– The required load module has been saved onto the disk, after transferring it
from the host to the controller storage.
– The automatic IPL from disk option has been chosen (see “Disk IPL
Information” on page 4-32).
The various procedures for initializing the controller are described in the
IBM 3745
Basic Operations Guide, SA33-0146.
Automatic IPL and Dump
The IPL with automatic control program loading capability is obtained by saving the
control program load module on the controller hard disk. When two control
program load modules are stored on the disk, the load module designated for
automatic loading is used. See “Generating and Loading the Control Program” on
page 3-2.
The MOSS can re-IPL the controller by using a disk-resident control program load
module specified as
active at the operator console:
When the operator requests IPL either at the control panel or at a 3745
console.
|
At a scheduled time, controllers in a network can be automatically reloaded
|
(Timed IPL).
After a hard stop of the CCU or an NCP abend. In this case, there is an
automatic dump of the controller storage, and then an automatic control
program reloading. This dump is saved on the MOSS disk. The network
|
operator can request transfer of either a part or all of the saved dump to the
|
host.
Diskette Management for Remote Loading and Activation
As described on page 3-3, the remote NCP load modules are:
1. Generated in the host
2. Transferred from the host storage to the local 3745 disk
3. Copied from the local 3745 disk to one diskette (for each remote 3745).
Then, the diskettes are mailed or hand-carried to the remote locations, and there,
each NCP load module is:
4. Copied from the diskette to the remote 3745 disk
Chapter 4. Controller Description
4-29
Summary of Contents for ThinkPad 130
Page 1: ...IBM 3745 Communication Controller Models 130 150 and 170 IBM Introduction GA33 0138 2...
Page 2: ......
Page 3: ...IBM 3745 Communication Controller Models 130 150 and 170 IBM Introduction GA33 0138 2...
Page 8: ...vi IBM 3745 Models 130 150 170 Introduction...
Page 15: ...IBM 3745 Communication Controllers in a Typical Network Chapter 1 Highlights 1 3...
Page 24: ...2 4 IBM 3745 Models 130 150 170 Introduction...
Page 32: ...3 8 IBM 3745 Models 130 150 170 Introduction...
Page 72: ...5 8 IBM 3745 Models 130 150 170 Introduction...
Page 74: ...6 2 IBM 3745 Models 130 150 170 Introduction...
Page 78: ...3745 130 150 170 General Data Flow 6 6 IBM 3745 Models 130 150 170 Introduction...
Page 82: ...A 4 IBM 3745 Models 130 150 170 Introduction...
Page 86: ...X 4 IBM 3745 Models 130 150 170 Introduction...
Page 92: ...X 10 IBM 3745 Models 130 150 170 Introduction...
Page 94: ...X 12 IBM 3745 Models 130 150 170 Introduction...
Page 100: ...X 18 IBM 3745 Models 130 150 170 Introduction...
Page 103: ......
