newsgroups-index (beta)

Current group: bit.listserv.vse-l

RE: FTP from VSE to MVS

RE: FTP from VSE to MVS  
Ward, Garry
From:Ward, Garry
Subject:RE: FTP from VSE to MVS
Date:20 Jan 2005 05:23:06 -0800
This is a multi-part message in MIME format.

------_=_NextPart_001_01C4FEF3.43C53FC0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

As in you define it through ISPF, run an IEBGENER to load some data and
then try to FTP it? Or has there been at least 24 hours between when you
created it and when you tried to retrieve it? It won't be the first time
that I've seen MVS storage administrators default datasets into a pool
that is marked as HSM Level 2 (tape) on close.
=20
If you log on to ISPF and attempt to browse the dataset, does it come
back quickly or does it take a while before it opens?

________________________________

From: owner-vse-l@Lehigh.EDU [mailto:owner-vse-l@Lehigh.EDU] On Behalf
Of Dwakser@aol.com
Sent: Thursday, January 20, 2005 8:15 AM
To: VSE Discussion List
Subject: Re: FTP from VSE to MVS


In a message dated 1/20/2005 8:12:45 AM Eastern Standard Time,
Garry.Ward@maritz.com writes:

=09
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?


Garry:
=20
No way. We merely created (manually) a dataset and logging on as
that user allows access. And, again, it doesn't matter which way we go,
PUT or GET, we get the same results.
=20
David Wakser
InfoCrossing


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_01C4FEF3.43C53FC0
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable





Arial"=20
bottomMargin=3D7 leftMargin=3D7 topMargin=3D7 rightMargin=3D7>
As in you defi=
ne it=20
through ISPF, run an IEBGENER to load some data and then try to FTP it? Or =
has=20
there been at least 24 hours between when you created it and when you tried=
to=20
retrieve it? It won't be the first time that I've seen MVS storage=20
administrators default datasets into a pool that is marked as HSM Level 2 (=
tape)=20
on close.

 <=
/DIV>
If you log on =
to ISPF and=20
attempt to browse the dataset, does it come back quickly or does it take a =
while=20
before it opens?





From: owner-vse-l@Lehigh.EDU=20
[mailto:owner-vse-l@Lehigh.EDU] On Behalf Of=20
Dwakser@aol.com
Sent: Thursday, January 20, 2005 8:15=20
AM
To: VSE Discussion List
Subject: Re: FTP from VSE to=
MVS




In a message dated 1/20/2005 8:12:45 AM Eastern Standard Time,=20
Garry.Ward@maritz.com writes:

style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: blue 2px solid">=
style=3D"BACKGROUND-COLOR: transparent" face=3DArial>
From left fi=
eld, is=20
there a chance that the dataset VSE01.THIS.IS.A.TEST.DATASET was created =
such=20
that HSM/SMS has migrated it to tape and the MVS side is stalling because=
the=20
file hasn't been retrieved yet?



Garry:

 

    No way. We merely created (manually) a dataset=
and=20
logging on as that user allows access. And, again, it doesn't matter which =
way=20
we go, PUT or GET, we get the same results.

 

David Wakser

InfoCrossing




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_01C4FEF3.43C53FC0--
   

Copyright © 2006 newsgroups-index   -   All rights reserved   -   Impressum