FWIW, here's what the audit journal records of a normal IPL starting
TCP/IP amounts to on a V7R1 system:
Journal . . . . . . : QAUDJRN Library . . . . . . : QSYS
Sequence . . . . . . : 129
Code . . . . . . . . : T - Audit trail entry
Type . . . . . . . . : JS - Job data
Object . . . . . . . :
Type . . . . . . . :
Date . . . . . . . . : 24-04-13
Time . . . . . . . . : 05:10:15
Flag . . . . . . . . : 0
Count/RRN . . . . . : 0
Commit cycle ID . . : 0
Nested commit level : 0
Job . . . . . . . . : 699358/QSYS/QSYSARB4
User profile . . . . : QSYS
Ignore APY/RMV . . . : No
Ref constraint . . . : No
Object . . . . . . . : Library . . . . . . :
Member . . . . . . . :
Incomplete data . . : No Minimized entry data : *NONE
Sequence . . . . . . : 129
Code . . . . . . . . : T - Audit trail entry
Type . . . . . . . . : JS - Job data
Entry specific data
Column *...+....1....+....2....+....3....+....4....+....5
00001 'BB QSTRTCP QPGMR 699418 QPGMR Q'
00051 'TOCSTRTCPQSYS QSYSNOMAX QSYS *DEV '
00101 ' WYNDSYSPRT '
00151 ' '
00201 ' '
00251 ' '
00301 ' '
Journal . . . . . . : QAUDJRN Library . . . . . . : QSYS
Sequence . . . . . . : 176
Code . . . . . . . . : T - Audit trail entry
Type . . . . . . . . : JS - Job data
Object . . . . . . . :
Type . . . . . . . :
Date . . . . . . . . : 24-04-13
Time . . . . . . . . : 05:10:16
Flag . . . . . . . . : 0
Count/RRN . . . . . : 0
Commit cycle ID . . : 0
Nested commit level : 0
Job . . . . . . . . : 699418/QPGMR/QSTRTCP
User profile . . . . : QPGMR
Ignore APY/RMV . . . : No
Ref constraint . . . : No
Object . . . . . . . : Library . . . . . . :
Member . . . . . . . :
Incomplete data . . : No Minimized entry data : *NONE
Sequence . . . . . . : 176
Code . . . . . . . . : T - Audit trail entry
Type . . . . . . . . : JS - Job data
Entry specific data
Column *...+....1....+....2....+....3....+....4....+....5
00001 'SB QSTRTCP QPGMR 699418 QPGMR Q'
00051 'TOCSTRTCPQSYS QSYSNOMAX QSYS *DEV '
...
Journal . . . . . . : QAUDJRN Library . . . . . . : QSYS
Sequence . . . . . . : 188
Code . . . . . . . . : T - Audit trail entry
Type . . . . . . . . : CD - Command string
Object . . . . . . . :
Type . . . . . . . :
Date . . . . . . . . : 24-04-13
Time . . . . . . . . : 05:10:17
Flag . . . . . . . . : 0
Count/RRN . . . . . : 0
Commit cycle ID . . : 0
Nested commit level : 0
Job . . . . . . . . : 699418/QPGMR/QSTRTCP
User profile . . . . : QPGMR
Ignore APY/RMV . . . : No
Ref constraint . . . : No
Object . . . . . . . : Library . . . . . . :
Member . . . . . . . :
Incomplete data . . : No Minimized entry data : *NONE
Sequence . . . . . . : 188
Code . . . . . . . . : T - Audit trail entry
Type . . . . . . . . : CD - Command string
Entry specific data
Column *...+....1....+....2....+....3....+....4....+....5
00001 'CSTRTCP QSYS *CMD BQSYS/STRTCP'
Journal . . . . . . : QAUDJRN Library . . . . . . : QSYS
Sequence . . . . . . : 956
Code . . . . . . . . : T - Audit trail entry
Type . . . . . . . . : JS - Job data
Object . . . . . . . :
Type . . . . . . . :
Date . . . . . . . . : 24-04-13
Time . . . . . . . . : 05:10:21
Flag . . . . . . . . : 0
Count/RRN . . . . . : 0
Commit cycle ID . . : 0
Nested commit level : 0
Job . . . . . . . . : 699418/QPGMR/QSTRTCP
User profile . . . . : QPGMR
Ignore APY/RMV . . . : No
Ref constraint . . . : No
Object . . . . . . . : Library . . . . . . :
Member . . . . . . . :
Incomplete data . . : No Minimized entry data : *NONE
Sequence . . . . . . : 956
Code . . . . . . . . : T - Audit trail entry
Type . . . . . . . . : JS - Job data
Entry specific data
Column *...+....1....+....2....+....3....+....4....+....5
00001 'EB QSTRTCP QPGMR 699418 QPGMR Q'
00051 'TOCSTRTCPQSYS QSYSNOMAX QSYS *DEV '
00101 ' WYNDSYSPRT '
00151 ' '
00201 ' '
00251 ' '
00301 ' '
It seems indeed that QSYSARB4 submits a QSTRTCP job specifying a job
description of QTOCSTRTCP, in turn running the STRTCP command defined as
the request data in that job description.
Cheers,
Carsten
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of CRPence
Sent: 22. april 2013 00:08
To: midrange-l@xxxxxxxxxxxx
Subject: Re: How does TCPIP start on a 7.1 system?
On 18 Apr 2013 17:15, CRPence wrote:
On 18 Apr 2013 13:02, rob@xxxxxxxxx wrote:
<<SNIP>> So what DOES do the STRTCP, since that's not in the QSTRUP
program? Some obscure autostart job entry on some other subsystem?
Because QTCPIP runs in QSYSWRK [presumably still, on v7r1], I would
look at that subsystem which is started automatically as the side
effect of starting *any* subsystem; i.e. even if the *SBSD started is
not the controlling subsystem (QCTLSBSD).
Also, the history log message about TCP/IP starting may reveal the
information about how the job started; as well or instead, the active
or spooled joblog for the QTCPIP job, which I believe is the name of
the primary job for TCP/IP services on which the various servers
depend.
<<SNIP>>
I found a message in a prior discussion, in which the TCP/IP was
noted to have been started by a QSYSARB job; specifically, QSYSARB4 was
named. However, that may have reflected a problem rather than a proper
and expected implementation and effect?:
Subject: TCP/IP starts twice in V7
http://archive.midrange.com/midrange-l/201209/msg00788.html
I wonder if anyone has found anything more about the *JOBD named
QTOCSTRTCP in QSYS that has been mentioned.? Nobody mentioned if there
was a last-used date on the object [e.g. reflecting the most recent IPL
date], nor any object-read audit results [for that Job Description
and\or the STRTCP *CMD object; of course, after CHGOBJAUD OBJAUD(*ALL)
for those objects].
This communication is intended only for use by the addressee.It may contain confidential or privilegedinformation.
If you receive this communication unintentionally, please inform us immediately and delete this e-mail and any attachments.
Warning: Although we have taken reasonable precautions to ensure no viruses are present in this email, we cannot accept
responsibility for any loss or damage arising from the use of this email or attachments.
midrange.com
