Re: TCP Question

[rob@xxxxxxxxx]

I can run OP's Console in a restricted state, (direct attached). Therefore 
I hope you don't need TCP/IP.


Rob Berendt
-- 
"They that can give up essential liberty to obtain a little temporary 
safety deserve neither liberty nor safety." 
Benjamin Franklin 




"Jim Franz" <franz400@xxxxxxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
03/14/2003 09:08 AM
Please respond to Midrange Systems Technical Discussion
 
        To:     "Midrange Systems Technical Discussion" 
<midrange-l@xxxxxxxxxxxx>
        cc: 
        Fax to: 
        Subject:        Re: TCP Question


Be aware that without TCP - Client Access or any other Telnet will not 
work.
My guess is that OPS Console will not function?
If you are worried about other tcp functions like http, ftp, etc - you can
shut them down thru change attributes cmd for each server - CFGTCP and 
then
option 20 for options to change each server.
jim

----- Original Message -----
From: "Andy Nolen-Parkhouse" <aparkhouse@xxxxxxxxx>
To: "'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx>
Sent: Friday, March 14, 2003 8:37 AM
Subject: RE: TCP Question


> 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
>
>
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>


_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing 
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.