Re: ftp problems pc to i5 at v5r3

same problem if user has *allobj
manually did not work
will try the trace
jim

----- Original Message ----- 
From: <michael@xxxxxxxxxxxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Sent: Friday, February 11, 2005 8:24 AM
Subject: RE: ftp problems pc to i5 at v5r3


> Does it work if you do it manually (without the script)?
>
> Same problem for all users (authority)?
>
> You can use TRCTCPAPP to find out where it's hanging in the server.
>
> > -------- Original Message --------
> > Subject: ftp problems pc to i5 at v5r3
> > From: "Jim Franz" <franz400@xxxxxxxxxxxx>
> > Date: Fri, February 11, 2005 8:09 am
> > To: MIDRANGE-L@xxxxxxxxxxxx
> >
> > Recent upgrade from v4r5 S10 to vr5r3 model 520.
> > FTP from i5 to unix servers daily work fine.
> > FTP from pc (dos command prompt) to i5 hangs.
> > Get logged on, but does not start sending.
> > After login (have run this script for years):
> > cd MYLIB
> > put C:\SCI\PXMIT.txt HOMEBU (replace
> > quote rcmd CAll HOMUPDC
> > I can tell on some attempts, CALL does execute....
> > Have cume & hipers as of 3 weeks ago.
> > Any ideas, or how to debug this? I have changed
> > the job log for ftp jobs to 4  00   *seclvl. No ftp exit pgm running.
> > jim franz
> > -- 
> > 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.
>
> -- 
> 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.
>
>