Re: TCP/IP and IPL and DST

Does your ftp log file log a genuine timestamp?  Compare that to DSPLOG to 
see if something really came up.  Too bad ftp uses those sequenced jobs 
like QTFTP00182.  Otherwise you could do
DSPLOG PERIOD((1700 021105) (0500 021305)) JOB(QTFTPJOB)
You could do
DSPLOG PERIOD((1700 021105) (0500 021305)) OUTPUT(*PRINT) MSGID(CPF1124 
CPF1164) and scan the spool file for QTFTP.

Rob Berendt
-- 
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





PaulMmn <PaulMmn@xxxxxxxxxxxxx> 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
02/18/2005 08:40 AM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
midrange-l@xxxxxxxxxxxx
cc

Subject
TCP/IP and IPL and DST






Question--

How much of TCP/IP is awake and functioning when the iSeries is 
rebooted in manual mode and stopped at DST (Dedicated Service Tools)?

I made brief search thru the archives but didn't find anything that 
seemed to address this issue.

The problem--

We had our machine down over the weekend for repairs.  The CE had the 
machine up to DST and back down a few times over a 3 hour period. 
During that time it appears that some SMTP mail transactions and some 
FTP uploads disappeared.

The business partner that sent us the SMTP transactions (dedicated 
circuit) states that the transmission was normal, with no hangups 
reported.  The log file on the FTP system shows that 3 upload 
attempts were made.  Yet none of these made it to the mailbox or the 
target file.

One theory is that TCP/IP is awake enough to acknowledge the 
attempted transactions, but not enough to actually -do- anything with 
them; they end up in the bit bucket.

Our systems manager doesn't think so; the network group polls the 
SMTP servers to see if they're alive; the iSeries gave no response 
until the system was all the way up and the subsystems were started.

My (perhaps warped) understanding is that TCP/IP has to be awake 
enough to talk to the PC-attached console (thru the dedicated special 
port); it's also awake enough to listen on other ethernet connections 
(which is why, as I understand it, SST and DST now come equipped with 
profiles and passwords).

Can anyone shed any light on the behavior of TCP/IP and maybe explain 
where these transactions might have gone?

Thanks!

Paul E Musselman
PaulMmn@xxxxxxxxxxxxxxxxxxxx
-- 
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.