 | This is a multi-part message in MIME format.
------_=_NextPart_001_01C4FEF1.BE07AC0E
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
>From left field, is there a chance that the dataset
VSE01.THIS.IS.A.TEST.DATASET was created such that HSM/SMS has migrated
it to tape and the MVS side is stalling because the file hasn't been
retrieved yet?
________________________________
From: owner-vse-l@Lehigh.EDU [mailto:owner-vse-l@Lehigh.EDU] On Behalf
Of Dwakser@aol.com
Sent: Wednesday, January 19, 2005 12:56 PM
To: VSE Discussion List
Subject: FTP from VSE to MVS
All:
=20
Can anyone make a suggestion as to why an FTP from VSE to MVS
(either GET or PUT) fails with a stall AFTER successfully logging in,
receiving notification of the working directory, and passing parameters
to MVS (and retrieving responses back). The MVS gurus claim that neither
FTP nor ACF2 is logging any errors.
=20
Here are FTPBATCH parameters used:
=20
// EXEC FTPBATCH,SIZE=3DFTPBATCH,PARM=3D'PORT=3D21,ID=3D00' =
=20
LOPEN =20
LUSER 2MVS =20
LPASS 2MVS =20
DEBUG ON =20
OPEN 10.1.9.10 =20
USER VSE01 =20
PASS ABCDEFG =20
EBCDIC =20
SITE RECFM=3DF FILETYPE=3DSEQ =
SITE LRECL=3D80 BLKSIZE=3D80 =
SITE VOLUME=3DWORK01 UNIT=3D3380 =
GET 'VSE01.THIS.IS.A.TEST.DATASET' %NEW,SAM,F,80,80 =20
CLOSE =20
LCLOSE =20
QUIT =20
/* =20
=20
David Wakser
InfoCrossing =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_01C4FEF1.BE07AC0E
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Arial"=20
bottomMargin=3D7 leftMargin=3D7 topMargin=3D7 rightMargin=3D7>
From left fiel=
d, is there=20
a chance that the dataset VSE01.THIS.IS.A.TEST.DATASET was created such tha=
t=20
HSM/SMS has migrated it to tape and the MVS side is stalling because the fi=
le=20
hasn't been retrieved yet?
All:
Can anyone make a suggestion as to why an FTP =
from=20
VSE to MVS (either GET or PUT) fails with a stall AFTER successfully loggin=
g in,=20
receiving notification of the working directory, and passing parameters to =
MVS=20
(and retrieving responses back). The MVS gurus claim that neither FTP nor A=
CF2=20
is logging any errors.
Here are FTPBATCH parameters used:
// EXEC =20
FTPBATCH,SIZE=3DFTPBATCH,PARM=3D'PORT=3D21,ID=3D00' =
=20
LOPEN =
&nb=
sp; =
&nb=
sp; =
=20
LUSER=20
2MVS =
; &n=
bsp; =
; &n=
bsp; =20
LPASS=20
2MVS =
; &n=
bsp; =
; &n=
bsp; =20
DEBUG=20
ON &=
nbsp; &nbs=
p; &=
nbsp; &nbs=
p; =20
OPEN=20
10.1.9.10 =
&nb=
sp; =
&nb=
sp; =20
USER=20
VSE01 &nbs=
p; &=
nbsp; &nbs=
p; &=
nbsp; =20
PASS=20
ABCDEFG &n=
bsp; =
; &n=
bsp; =
; =20
EBCDIC =
; &n=
bsp; =
; &n=
bsp; =
; =20
SITE RECFM=3DF =20
FILETYPE=3DSEQ &=
nbsp; &nbs=
p; =
SITE LRECL=3D80 =20
BLKSIZE=3D80 &nb=
sp; =
&nb=
sp; =20
SITE VOLUME=3DWORK01=20
UNIT=3D3380 &nbs=
p; &=
nbsp; &nbs=
p; =20
GET 'VSE01.THIS.IS.A.TEST.DATASET'=20
%NEW,SAM,F,80,80 =
; =20
CLOSE =
&nb=
sp; =
&nb=
sp; =
=20
LCLOSE =
; &n=
bsp; =
; &n=
bsp; =
; =20
QUIT &=
nbsp; &nbs=
p; &=
nbsp; &nbs=
p; &=
nbsp; =20
/*
David Wakser
InfoCrossing &nbs=
p; &=
nbsp; &nbs=
p; &=
nbsp; =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_01C4FEF1.BE07AC0E--
|
