Re: File transfer from AS/400 to MVS

["Patrick Townsend" <patownsend@xxxxxxxxxxxxxx>]

Don,

It is likely that the target file on the S/390 is not set up for
Generational Dataset names. The (+1) suffix on the file in the put statement
is invoking this logic on the S/390. But the 501 error is indicating that
the target file does not support this capability. A GDS set on the mainframe
is like a multiple member file on the AS/400. The (+1) means automatically
create a new member for the received data. You will need to provide this
error message to the Sys Admin on the S/390 system.

Patrick
----- Original Message -----
From: "Fisher, Don" <Dfisher@xxxxxxxxxxxxxxxxx>
To: <midrange-l@xxxxxxxxxxxx>
Sent: Tuesday, March 18, 2003 12:14 PM
Subject: File transfer from AS/400 to MVS


> I hope someone out there can help us.  This should not be this difficult.
> We are attempting to use FTP to send a physical file from our V4R1 AS/400
to
> another company's system that is running MVS and OS/390.  to do this, we
> execute the following two commands after entering the user id and
password:
> quote site recfm=fb lrecl=160 blksize=27840 primary=5 secondary=2 cy
> put ourlibrary/ourfile.member 'xxxx.xxxxxxxx.xxxx.xxx.xxxx.origbk(+1)'
>
> This returns the following error messages:
> 550-SVC99 Return code=4 S99INFO=0 S99ERROR=38668 HEX=970C S99ERSN code
> X'000042CE').
> 501 Invalid data set name "xxxx.xxxxxxxx.xxxx.xxx.xxxx.origbk(+1)".  Use
MVS
> Dsname conventions.
>
> If we remove the "origbk(+1)", we get these error messages:
> 550-SVC99 Return code=4 S99INFO=0 S99ERROR=38668 HEX=970C S99ERSN code
> X'000042CE').
> 550 Unable to create data set xxxxxxx.xxxx.xxxxxxxx.xxxx.xxx.xxxx for STOR
>
> We have tried EBCDIC, BINARY, and different NAMEFMT values to no avail.
Can
> anyone tell me either what we're doing wrong or where a manual that
explains
> these error messages might be located?
>
> Thanks.
>
> Donald R. Fisher, III
> Project Manager
> The Roomstore Furniture Company
> (804) 784-7600 extension 2124
> DFisher@xxxxxxxxxxxxxxxxx
>
> _______________________________________________
> 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.
>
>