 | This is a multi-part message in MIME format.
------_=_NextPart_001_01C4FEF8.1F3D320E Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable
On the GET, why the SITE commands? All of the information in the SITE commands should be in the MVS catalog for an existing file.=20 =20 We do some LSITE commands: =20 LCD POWER\LST\A =20 LSITE RECFM FB =20 LSITE LRECL 133 =20 LSITE BLOCKSIZE 133 =20 BIN =20 GET 'CLNMRZ.MRZ004.AAA.ATSTAS.PRTFILE1(0)' MRZ0041 =20 GET 'CLNMRZ.MRZ004.AAA.ATSTAS.PRTFILE2(0)' MRZ0042 =20 GET 'CLNMRZ.MRZ004.AAA.ATSTAS.PRTFILE3(0)' MRZ0043 =20 GET 'CLNMRZ.MRZ004.AAA.ATSTAS.PRT3553(0)' MRZ0044 =20 =20 but no SITE commands. =20 We do BIN instead of EBCDIC. Either should get the records transferred without change. Have you tried BIN? =20 Do you see any bytes transferred or does it just start reporting stalls? =20 Garry
________________________________
From: owner-vse-l@Lehigh.EDU [mailto:owner-vse-l@Lehigh.EDU] On Behalf Of Dwakser@aol.com Sent: Thursday, January 20, 2005 8:50 AM To: VSE Discussion List Subject: Re: FTP from VSE to MVS
Priority doesn't seem to be a problem, since the FTP really never starts. The OPEN, the logon sequence and the execution of commands seem timely enough. But at the issuing of the GET (or PUT) things get lost and eventually time out. =20 David Wakser=20
Confidentiality Warning: This e-mail contains information intended only fo= r the use of the individual or entity named above. If the reader of this e= -mail is not the intended recipient or the employee or agent responsible fo= r delivering it to the intended recipient, any dissemination, publication o= r copying of this e-mail is strictly prohibited. The sender does not accept= any responsibility for any loss, disruption or damage to your data or comp= uter system that may occur while using data contained in, or transmitted wi= th, this e-mail. If you have received this e-mail in error, please immedi= ately notify us by return e-mail. Thank you.
------_=_NextPart_001_01C4FEF8.1F3D320E Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable
Arial"=20 bottomMargin=3D7 leftMargin=3D7 topMargin=3D7 rightMargin=3D7>
On the GET, wh= y the SITE=20 commands? All of the information in the SITE commands should be in the MVS= catalog for an existing file.
<= /DIV> We do some LSI= TE=20 commands: <= /DIV> LCD=20 POWER\LST\A &nbs= p; &= nbsp; &nbs= p; &= nbsp; =20
LSITE RECFM=20 FB &= nbsp; &nbs= p; &= nbsp; &nbs= p; =20
LSITE LRECL=20 133 = &nb= sp; = &nb= sp; =20
LSITE BLOCKSIZE=20 133 = &nb= sp; = &nb= sp; =20
BIN &n= bsp;  = ; &n= bsp;  = ; &n= bsp; =20
GET 'CLNMRZ.MRZ004.AAA.ATSTAS.PRTFILE1(0)'=20 MRZ0041 &n= bsp; =20
GET 'CLNMRZ.MRZ004.AAA.ATSTAS.PRTFILE2(0)'=20 MRZ0042 &n= bsp; =20
GET 'CLNMRZ.MRZ004.AAA.ATSTAS.PRTFILE3(0)'=20 MRZ0043 &n= bsp; =20
GET 'CLNMRZ.MRZ004.AAA.ATSTAS.PRT3553(0)'=20 MRZ0044 &n= bsp; <= /SPAN> but no SITE=20 commands. <= /DIV> We do BIN inst= ead of=20 EBCDIC. Either should get the records transferred without change. Have you = tried=20 BIN? <= /DIV> Do you see any= bytes=20 transferred or does it just start reporting stalls? <= /DIV> Garry= DIV>
Priority doesn't seem to be a problem, since the FTP really never star= ts.=20 The OPEN, the logon sequence and the execution of commands seem timely enou= gh.=20 But at the issuing of the GET (or PUT) things get lost and eventually = time=20 out.
David Wakser
Confidentiality Warning: This e-mail contains information intended only fo= r the use of the individual or entity named above. If the reader of this e= -mail is not the intended recipient or the employee or agent responsible fo= r delivering it to the intended recipient, any dissemination, publication o= r copying of this e-mail is strictly prohibited. The sender does not accept= any responsibility for any loss, disruption or damage to your data or comp= uter system that may occur while using data contained in, or transmitted wi= th, this e-mail. If you have received this e-mail in error, please immedi= ately notify us by return e-mail. Thank you.
------_=_NextPart_001_01C4FEF8.1F3D320E-- |