Re: Starting TCP

[Jerry Draper <midrangel@xxxxxxxxxxxxx>]

Check your CHGIPLA to see if TCP is starting up at IPL time.

If you have a STRTCP in your QSTRUP it may be starting twice.

You get more control if you use STRTCP because you can choose parms and 
do MONMSG but you must position it appropriately in QSTRUP.

Jerry

On 4/17/2013 9:27 AM, John McKee wrote:
> Thanks.
>
> I should have looked there.  Got hung up on looking for a STR command.
>
> So, the STRTCP command is likely doing nothing worthwhile.
>
> John McKee
>
>
> On Wed, Apr 17, 2013 at 11:16 AM, Steinmetz, Paul <PSteinmetz@xxxxxxxxxx>wrote:
>
> > Previously (2005), TCP had be manually started. IPL attribute was added to
> > include start of TCP, then had to disable STRTCP in QSTRUP.
> > We did know this for a while, TCP was trying to start twice, once from IPL
> > attribute and also from QSTRUP.
> > Caused many errors during IPLs until disabled.
> >
> >
> > -----Original Message-----
> > From: midrange-l-bounces@xxxxxxxxxxxx [mailto:
> > midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of John McKee
> > Sent: Wednesday, April 17, 2013 12:04 PM
> > To: Midrange Systems Technical Discussion
> > Subject: Starting TCP
> >
> > I'm confused. There is a startup job on the controlling subsystem.
> > Essentially the first thing it does is call QSTRUP.  Then, it does STRTCP.
> > I retrieved the source of QSTRUP.  Nothing about starting TCP in it.
> >
> > This startup job, not from IBM, has a MONMSG CPF9999 following the STRTCP
> > command.
> >
> > I thought that TCP would have to be up before the LAN console would be
> > available.  This STRTCP was added locally to the vendor code back in 1998.
> >
> > Two questions:
> >
> > 1) When/how is TCP started?
> > 2) Is this STRTCP doing anything or just a relic from a long time ago?
> >
> > I believe this modification dates back to when we were on a CISC box and
> > just starting on networking.
> >
> > Currently at v5r4m0.
> >
> > I can explain why I was looking, but it started with a request from the
> > boss.
> >
> > John McKee
> > --
> > 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.