Re: Problems FTP'ing a save file from PC to AS/400

Whatever...

I still don't have a meaningful answer to my original question.  I don't
understand why you guys are so caught up in the terminology that I used,
rather than trying to help me solve a problem.  You continue to give me a
hard time about things that have absolutely no relevance to the issue at
hand.

I appreciate your corrections, Bill.  I am wrong.  Dead wrong.  I have
always been wrong, and I will always be wrong in the future.  OK?

But other than Jim Norbut's suggestion to change the TCP inactivity timeout
limit via CHGTCPA, (which I cannot try yet since I am work), I haven't
received any help other than people like you and Rob trying to correct my
terminology.

You must be an only child...

Steve


----- Original Message -----
From: "Bill" <billzbubb@subdimension.com>
To: <midrange-l@midrange.com>
Sent: Friday, January 03, 2003 11:59 AM
Subject: Re: Problems FTP'ing a save file from PC to AS/400


> Steve Landess wrote:
> > If you re-read my message, you'll see that I said "running V5R1M0,
> > with cum SF99510".
> >
> > Now, go to IBM's iPTF web site:
> > which has the table of recommended fixes.  You'll see that I was only
> > using the terminology given by IBM.  It says "CUM Package" on the
> > left-hand side.
> >
> > Sorry if I was a little touchy, but I don't think I was wrong...
>
> Steve,
>
> In this case you are incorrect.  SF99510 is the "signal" to the PTF
process
> that the orderer wishes to obtain the latest CUM for OS/400 version 5.1.0
.
> Stating you are on the latest CUM and referencing that PTF signaler is
> misleading and meaningless.
>
> Bill
>
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>