RE: TCP Question

["Andy Nolen-Parkhouse" <aparkhouse@xxxxxxxxx>]

Len,

What problem are you trying to solve by doing this?

- At V4R5 you probably start TCP via the STRTCP command via the startup
program specified in system value QSTRUPPGM.  You could edit this program
to remove the command and any subsequent commands for starting TCP
servers.  Then put it back when you're ready.

- At V5R1 you have the ability to start TCP via an IPL Attribute.  Use
the CHGIPLA command to specify STRTCP to *NO and make sure that you've
eliminated all references to starting TCP servers from your startup
program.  (This won't work unless you have your individual servers
flagged to start automatically at IPL.)

- You could perform a manual IPL and bring the system up in dedicated
mode.  This would prevent the startup program from running at all and
even if the STRTCP IPL Attribute is set to *YES, it will not execute in
dedicated mode.

- If you're concerned about talking to other systems during the first IPL
you could remove your network cables from the back of the machine, then
put them back, bring down and then restart TCP when you're ready.

Just some thoughts HTH,
Andy Nolen-Parkhouse


> On Behalf Of Len Grieco
> Subject: TCP Question
> 
> Hello All,
> 
>       This weekend we are going to complete the migration from our old
> AS/400 model 170 (v4.r5) to our new iSeries model 270 (v5.r1).
> Everything
> is done, what we want to do is stop TCP from automatically starting
> when the
> system is IPL'd.  Can someone explain how this can be done or point us
> in
> the right direction.
> 
> Thank you
> 
> Len Grieco