|
I did do the trctcpapp *ftp but cannot see from the trace what went wrong. It signs on, does a chg dir (cd), then starts the "put". And then just sits.... I did, from trying over & over, get it to work 4 times straight, but test 5-10 all failed. Rebooted pc - same problem. I can see on page 12 of trace it reaches the "put". Listed below is last page of trace. Three minutes later I killed ftp job & printed trace. There were no entries during that 3 minutes, like it went to sleep. jim 19:40:57 2005 Trace Point: QTMF2020FF Entry type: RETURN To: 2007 From: qtmfutil 1232 qtmf_CvtToUpperDB(PCHAR, INT) 19:40:57 2005 Trace Point: QTMF200700 Entry type: DATA D34040404000C8D6D4C5C2E4404040400040404040404040404040*BNCFIL .HOMEBU . *......@@@@.......@@@@.@@@@@@@@@ *. *. 19:40:57 2005 Trace Point: QTMF2007FF Entry type: RETURN To: 2006 From: qtmfutil 3563 qtmf_ParseOldName(PSZ, qtmf_F 19:40:57 2005 Trace Point: QTMF2006FF Entry type: RETURN To: 0500 From: qtmfutil 3082 qtmf_ParseFileName(PSZ, INT, 19:40:57 2005 Trace Point: QTMF050000 Entry type: DATA 000000 *........ *...).... 19:40:57 2005 Trace Point: QTMF0903FE Entry type: CALL From: 0500 To: qtmfsutl 1183 qtmf_FindDataConn() 19:40:57 2005 Trace Point: QTMF2004FE Entry type: CALL From: 0903 To: qtmfutil 2229 qtmf_OpenConnection(qtmf_Sock 19:40:57 2005 Trace Point: QTMF200400 Entry type: DATA 00000000000000000200140A0001FE0000000000000000000211A3*...................Ú. ..........t*............................... 00000000000000 *â.aë........ *B=.S........ 19:40:57 2005 Trace Point: QTMF200405 Entry type: DATA 000BD1 *.......J *........ 19:40:57 2005 Trace Point: QTMF200406 Entry type: DATA 00000000000BD1 *...........J *............ 19:40:57 2005 Trace Point: QTMF200407 Entry type: DATA 19:40:57 2005 Trace Point: QTMF2005FE Entry type: CALL From: 2004 To: qtmfutil 2694 qtmf_SetSocketOptions(qtmf_So 19:40:57 2005 Trace Point: QTMF200504 Entry type: DATA 3M0 040528 TRCTCPAPP Output S102E68E Date-02/11/05 Time-19:43:44 Page-12 000BD1000020000000000000000004 *.......J............ *.......... ......... 19:40:57 2005 Trace Point: QTMF200501 Entry type: DATA 0080000000000000000BD1 *......Ø........J *................ 19:40:57 2005 Trace Point: QTMF200502 Entry type: DATA 0080000000000000000BD1 *......Ø........J *................ 19:40:57 2005 Trace Point: QTMF3003FE Entry type: CALL From: 2005 To: qtmfputl 829 qtmf_SetConnInfo(qtmf_FFDCInf 19:40:57 2005 Trace Point: QTMF3003FF Entry type: RETURN To: 2005 From: qtmfputl 839 qtmf_SetConnInfo(qtmf_FFDCInf 19:40:57 2005 Trace Point: QTMF200503 Entry type: DATA 0000080000000000000BD1 *...............J *................ 19:40:57 2005 Trace Point: QTMF2005FF Entry type: RETURN To: 2004 From: qtmfutil 2835 qtmf_SetSocketOptions(qtmf_So ----- Original Message ----- From: "Chris Bipes" <chris.bipes@xxxxxxxxxxxxxxx> To: "'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx> Sent: Friday, February 11, 2005 11:32 AM Subject: RE: ftp problems pc to i5 at v5r3 > Have you checked your FTP configuration? Did your default change from > NameFMT 0 to 1 perhaps? Check OpsNav Application Administration - Host > Applications - TPCIP Utilities - FTP - Server. You may be able to logon but > not use the put command. > > -----Original Message----- > > i have tried running directly from cmd prompt - same hanging on "put". > i do have "local" scripts running with same profile & jobd working ok. > this is only "remote", from my pc. i shutdown zone alarm (which always > prompted me to allow ftp & if i said yes it would work (although lately > ZA no longer prompts me to log on - but i have shut off). > so far network admin says firewall not changed. It's a big deal to trace > this thru > network - i am contract, net admin is contracted, firewall admin is > "managed" by > isp...) will trace i5 side first. > Rob - yes I did load this machine via savrst - tape drives were not > compatible > and company never got v5r1 or 2 for old server before upgrade agreement > expired). it went "fairly" smooth. > jim > -- > 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. > >
As an Amazon Associate we earn from qualifying purchases.
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.