Ali,
This is PART 1. (The original is 488 lines and 400 is the limit !!!)
Also, having got all my work back, the diagrams are a dog's breakfast so you
should copy and paste to a text file and unravel them.
I am not aware of an NCP/3745 newsgroup so this "catch-all" group will =
have to do I guess.
The following are some notes from my presentation on how VTAM manages =
NCPs which deal with loading over a link rather than a channel.=20
<start of notes>
For SDLC links, the availability of a link station for loading and =
static dumping depends on customization of the communication =
controller. For example, with a 3720, 3725 or 3745, there is a MOSS =
operation which is used to provide the appropriate parameters for SDLC =
operation on the line to the load/dump program. These parameters will, =
in general, be the same as the corresponding parameters defined in the =
BUILD and LINE statements in the NCP.
---------------------------------------------------------------------------------
| MOSS prompt | NCP equivalent
|
|------------------------------------------------------+------------------------|
| link IPL ports (per link) |
|
|------------------------------------------------------+------------------------!
x | line address (0 to 255) | LINE
ADDRESS=(xxx,...) |
x | full duplex (F) or half duplex (H) | LINE
ADDRESS=(...,xxx) |
| link interface options (Y = yes, N = no) |
|
x | NRZI | LINE NRZI
|
x | DX facility | LINE DUPLEX
|
x | switched line | LINE CONFG
|
x | answer tone | LINE ANSTONE
|
x | ring indicator | LINE RING
|
x | direct attach (D) or external clock (E) | LINE CLOCKNG
|
x | data rate (H = high, L = low) | LINE DATRATE
|
x | enable timer in 0.1 second intervals | BUILD ENABLTO
|
|------------------------------------------------------+------------------------!
| common options (all links) |
|
|------------------------------------------------------+------------------------!
x | SDLC controller address (1 to FE) | LINE TADDR *
|
| timer values (1 to 4 digits in 0.1 second intervals) |
|
| disable timer | BUILD DSABLTO
|
| link activity timer | GROUP ACTIVTO
|
|-------------------------------------------------------------------------------|
| * The default for TADDR is based on the NCP subarea number
|
| See NCP Resource Definition Reference
|
---------------------------------------------------------------------------------
<your parameters for checking>
x Line Address: 35
x Direct/External: External
x Duplex: D
x Enable Timer: 0 (Timeout yok)
Transmit two flags: y
Transmit flags between frames: y
x NRZI: y
x DX facility:y
x Switched: N
x Ring: N
x Answer: N
Echo: N
x Datarate: High
External Line Speed: Other (not 9600 or 56K my connection is 19.2K =
DialUp with modems dialing each other)
x SDLC Controller Address: C1 (I have coded this - but could not get =
from the guides what this is used for)
<end your parameters for checking>
In addition, if a load or a static dump operation is to be initiated at =
the time an NCP is active, the LINE statement requires that the IPL =
operand of the LINE statement specifies YES. This ensures that the SIM =
SDLC command will be accepted by the NCP and thus cause the Controller =
Load/Dump Program, CLDP, to be loaded.
VTAM V3R2, SSP V3R3 and NCP V5R2, in support of the 3720 and 3745 disk, =
permit the transfer of NCP load modules to the disk as normal PIU flow. =
Subsequent loading may then take place from the disk rather than over a =
link.=20
Also the dump operation can be to disk rather than over a link and the =
dump data can be copied to the host data set as normal PIU flow.
<end of notes>
I checked your parameters against mine, hence the "x"s, and I see I must =
not have been keeping my notes quite up to date.=20
I expect that the "Transmit two flags", "Transmit flags between frames" =
and "Echo" defaults will be acceptable.
It probably will do no harm to "Transmit two flags", between contiguous =
frame I expect. Normally only one flag acting as both the end of one =
frame and the beginning of another is allowed by SDLC architecture but I =
guess there must be some link subsystem hardware which can't cope with =
that, hence the option. Having read the manual (see later) it either =
describes what I did in different terms or implies three flags between =
frames.
It probably will do no harm to "Transmit flags between frames", =
presumably when frames are not contiguous which, as I seem to recall, =
NCP loading requires, an acknowledgement for each frame, will normally =
be the case. I guess this again is a matter of some link subsystem =
hardware not being able to cope with continuous "mark" state between =
frames.
This discussion which has implications for the efficiency of the loading =
process reminds me to point you to the following VTAM start option:
<start NCPBUFSZ>
4.4.99 NCPBUFSZ
_NCPBUFSZ=3D512________
>>__|_____________________|__><
|_NCPBUFSZ=3D_ _512__ __|
|_1024_|
|_2048_|
dependencies
see notes
Specifies the request unit size in bytes (I/O buffer size minus the size =
of the SNA header) used by VTAM when loading or performing a static dump =
of a remote NCP.
Notes:
1. This value does not apply to a MODIFY LOAD command. The length of the =
IPLTEXT RU is always 2048 plus the length of the SNA header.=20
2. This value applies only to static dumps or loads of 3720, 3725, and =
3745 communication controllers. VTAM ignores this value when loading or =
dumping a 3705, and uses a data size of 512 bytes.=20
<end NCPBUFSZ>
Sorry about that for anyone reading this who still has a 3705 <g>.
<Part 2 follows>
Chris Mason
----- Original Message -----
From: "Ali Serdar Yakut" <[EMAIL PROTECTED]>
Newsgroups: bit.listserv.ibm-main
To: <[email protected]>
Sent: Tuesday, 20 December, 2005 10:34 AM
Subject: Remote 3745 Definition
Hi there,
I do not know if this is the right list to post this, but I'm trying
anything for help.
I have got a very urgent situation.
I am trying to have a configuration like -
VTAM1 - NCP1 - NCP2
NCP1 is loaded in a channel attached 3745. NCP2 will be on a link attached
3745.
In the NCP generation and loading guide the following is stated:
You can perform a remote initial load over a TSS or HPTSS SDLC link or
over a nonswitched X.21 link if the remote communication controller has
the remote IPL ports defined. The remote initial load can transfer the
NCP or PEP load module from the host, activate it, and save it on the
remote hard disk. There is a minimum release requirement of NCP V4R2 with
VTAM V3R2 in order to save the module to the remote hard disk.
I have created remote IPL port using LKP function in the communication
controller of NCP2 - the parameters for the Port are:
Line Address: 35
Direct/External: External
Duplex: D
Enable Timer: 0 (Timeout yok)
Transmit two flags: y
Transmit flags between frames: y
NRZI: y
DX facility:y
Switched: N
Ring: N
Answer: N
Echo: N
Datarate: High
External Line Speed: Other (not 9600 or 56K my connection is 19.2K DialUp
with modems dialing each other)
SDLC Controller Address: C1 (I have coded this - but could not get from the
guides what this is used for)
So what should I do now? Create a line and PU (Type4) in NCP1 -
for this connection?
I have made so, but I can not see the PU as online on my VTAM, when there is
no NCP loaded in the remote controller. Can anybody help me with the
procedure- the guides all keep it as trivial, just create remote IPL port,
and load, but no procedure.
I will appreciate for any contribution.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
