John, Assuming there is no load module active - which I think is Ali's current situation, VTAM will be able to work out that a load is required by means of the link level response to sending the first XID, namely RIM (Request Initialization Mode). Use of LOAD=YES avoids the bother of sending an XID and receiving a RIM; VTAM kicks right in with a SIM (Set Initialization Mode).
Actually I need to try a touch of precision here. It is not VTAM but the loader module supplied by SSP that handles the actual load process hence the need for SSP libraries to be in the STEPLIB concatenation of the VTAM procedure. However, your explanation of what activates when is quite right. The advice to exploit the presence of the disk is also good but Ali has found Chapter 10 of the "NCP, SSP, and EP Generation and Loading Guide" so that should help a lot with how to use the disk. I'm afraid that what Mark offered might be compared to statistics: what they show is interesting but what they conceal is vital. In other words, what may be needed in this case is also the BUILD statement SUBAREA operand value and the "link IPL port" parameters. OK, the PATH statement tells us that the subarea number for the relevant NCP is 28. I strongly suspect that the key to Ali's problem is the "SDLC controller address" "link IPL port" parameter needing to be a hexadecimal representation of the subarea number. Thus we need to see Mark's SDLC controller address parameter and - I predict - it is "1C". I think I also picked up a possible issue with ENABLTO/"enable timer" based on a hint that Ali may be using a switched line behaving like a leased line. Chris Mason ----- Original Message ----- From: "John S. Giltner, Jr." <[EMAIL PROTECTED]> Newsgroups: bit.listserv.ibm-main To: <[email protected]> Sent: Tuesday, 20 December, 2005 7:07 PM Subject: Re: Remote 3745 Definition > Ali Serdar Yakut wrote: > > 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. > > > > <--- Begin SNIP ----> > > <--- End SNIP -----> > > ----------------------------------------------------------- > > > > > > > In addition to everything Mark has given you, you need to tell VTAM to > load the NCP. When you active the remote NCP you need to do: > > V NET,ACT,ID=NCP2,LOAD=YES > > Once the NCP is done loading, the PU definition representing it in NCP1 > should show active, NCP2 should show active and the PU representing NCP1 > in NCP2 should show active. > > I would also suggest that after you get it loaded, you store it on the > remote NCP's hard disk. This way if there is a power failure you can > reload it from the hard disk and it takes much less time than loading > over the WAN everytime. In fact once you get it up, you can pre-load new > NCP's to the hard disk and load from there. Then the NCP outage is only > a matter of a few minutes (3-5). I had a remote NCP on a 9.6 Kbps link, > it took 20-30 minutes to transfer. Depending on the size of your NCP > load module it may take 10-15 to transfer and then another 3-5 to load, > that a 20 minute network outage. ---------------------------------------------------------------------- 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
