× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. MIDRANGE-L
  3. October 2019

Re: TCP start up

I hope the formatting holds up - this occurred as a part of a BRMS *SYSTEM
save that was submitted via Advanced Job Scheduler with QSYSOPR as the
submitting user. There are no lines omitted in the QSYSOPR messages shown
below. You will notice that we went to restricted state then the STRTCP
command was issued and completed successfully and the next thing that
happened was a start of 10.1.60.150. This is defined as AUTOSTART = *NO
and is the first interface in a list of 8 interfaces under CFGTCP option 1.

CPF0968 60 INFO System ended to restricted condition.

QSYSARB4 QSYS 252408 QWCASCUE 0000
10/26/19 23:04:58.443445 QSYS
TCP1A19 00 INFO STRTCP started for user QSYSOPR in job
253840/QSYSOPR/SYSTEM
SYSTEM QSYSOPR 253840 QTOCNSTCP 0000
10/26/19 23:05:28.348312 QSYSOPR
TCP9529 00 COMPLETION A request to start TCP/IP in restricted state was
performed.
QTCPCTL QSYS 252465 QTOCMAIN 0000
10/26/19 23:05:28.457078 QSYS
CPFA11A 40 INFO IP over SNA not activated.

QTCPWRK QSYS 253852 QSOCACTI 0000
10/26/19 23:05:29.502761 QSYS
TCP9533 10 COMPLETION A request to start TCP/IP has been processed.

QTCPCTL QSYS 252465 QTOCMAIN 0000
10/26/19 23:05:40.824558 QSYS
TCP1A01 00 COMPLETION STRTCP completed successfully.

SYSTEM QSYSOPR 253840 QTOCNSTCP 0000
10/26/19 23:05:40.873358 QSYSOPR
TCP1B03 00 COMPLETION User QSYSOPR started IP interface 10.1.60.150 on
ETHHLIN01.

Thanks,

Steve McKay
(205) 585-8424
samckay1@xxxxxxxxx



On Mon, Oct 28, 2019 at 9:00 AM Rob Berendt <rob@xxxxxxxxx> wrote:

Part of what is returned is the exact program, line number, etc.

Are you absolutely sure that it is only doing a STRTCP and isn't also
doing a STRTCPIFC *ALL?



Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com


-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
Steve McKay
Sent: Monday, October 28, 2019 8:53 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: TCP start up

CAUTION: This email originated from outside of the organization. Do not
click links or open attachments unless you recognize the sender and know
the content is safe.


Yep - so I selected * a got some stuff back. This is telling me "who"
started the interface - I'm trying to figure out "why". The "who" is
QSYSOPR because we performed a BRMS *SYSTEM save (Save 21). There is a
STRTCP in that process and when the STRTCP is executed, the first thing
that happens is that the first listed IP interface is started even though
it's set to "Automatic start = *NO" in the interface description.

So the question remains, why does the STRTCP command activate this
interface that should not be activated and what can be done to prevent it?

Thanks,

Steve McKay
(205) 585-8424
samckay1@xxxxxxxxx



On Mon, Oct 28, 2019 at 8:46 AM Rob Berendt <rob@xxxxxxxxx> wrote:

Select whatever column you want.
From this UDTF:
<snip>
QSYS2.HISTORY_LOG_INFO
</snip>
For more information check out this link:
<snip>
http://ibm.biz/DB2foriServices
</snip>

Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com


-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
Steve McKay
Sent: Monday, October 28, 2019 8:37 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx

Subject: Re: TCP start up

CAUTION: This email originated from outside of the organization. Do not
click links or open attachments unless you recognize the sender and know
the content is safe.


Rob -

SELECT ??what?? FROM TABLE?

Thanks,

Steve McKay
(205) 585-8424
samckay1@xxxxxxxxx



On Mon, Oct 28, 2019 at 8:12 AM Rob Berendt <rob@xxxxxxxxx> wrote:

SELECT...
FROM TABLE (QSYS2.HISTORY_LOG_INFO(
START_TIME => CURRENT TIMESTAMP - 100 DAYS
)) AS X
Where message_id='TCP1B03'
ORDER BY ORDINAL_POSITION desc;

http://ibm.biz/DB2foriServices


Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com


-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
Steve McKay
Sent: Monday, October 28, 2019 7:54 AM
To: Midrange Systems Technical Discussion <
midrange-l@xxxxxxxxxxxxxxxxxx

Subject: TCP start up

CAUTION: This email originated from outside of the organization. Do not
click links or open attachments unless you recognize the sender and
know
the content is safe.


On V7R3, I have 8 interfaces defined. The first IP interface address
defined is set to "Automatic start = *NO" and is normally inactive.

When I start TCP, will this interface be automatically activated
(because
it is the first interface defined)?

I ask because we rebooted this partition over the weekend (for the
first
time since June) and this interface was active when it should not have
been. (It has a specific use and is not normally activated.) Trying to
identify the culprit . . .

Thanks,

Steve McKay
(205) 585-8424
samckay1@xxxxxxxxx
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com

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

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com

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

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com


As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.