Re: FTP Failing with space issues
On Thu, 27 Apr 2017 13:26:30 -0500, Ron Thomas wrote: >we are looking at copy the file to a GDG, once it reaches the z/OS directory >using the below job. so what i am looking is how we can automate this job so >once file reaches the unix directory it copies and delete the source ? > Heck; I don't mind getting fancy and embellishing my previous idea: cat linux.file | ssh user@zOS "cat >/export/home/PX1COMT/test.txt echo \"\\ //COPYSTEP EXEC PGM=IKJEFT01 //FILE DD PATH='/export/home/PX1COMT/test.txt',PATHDISP=DELETE //PTST DD DISP=SHR,DSN=PTHMICST.TEST.R1.Y(+1) //SYSTSPRT DD SYSOUT=* //SYSTSIN DD * OCOPY INDD(FILE) OUTDD(PTST) TEXT\" | /bin/submit" -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: FTP Failing with space issues
On Thu, Apr 27, 2017 at 1:26 PM, Ron Thomaswrote: > we are looking at copy the file to a GDG, once it reaches the z/OS > directory using the below job. so what i am looking is how we can automate > this job so once file reaches the unix directory it copies and delete the > source ? > > //COPYSTEP EXEC PGM=IKJEFT01 > //FILE DD PATH='/export/home/PX1COMT/test.txt' > //PTST DD DISP=SHR,DSN=PTHMICST.TEST.R1.Y(+1) > //SYSTSPRT DD SYSOUT=* > //SYSTSIN DD * > OCOPY INDD(FILE) OUTDD(PTST) TEXT > > what i am thinking is scheduling the job at different time of the day . is > this a good option or there is any other way to do it ? > That is basically the only method that I know of which does not require using an SMF IEFU8n exit to trap SMF record type 92, subtype 11 (file closed) or type 14 (file renamed). I wish that IBM had something equivalent to the Linux "inotify" system. That is an API which allows a daemon (such as "icrond") to monitor one or more files or directory for changes. The "icrond" is a daemon somewhat akin to "icron" which makes it easier to say "if this file/directory changes run this command/script". > Regards > Ron T > > -- Advertising is a valuable economic factor because it is the cheapest way of selling goods, particularly if the goods are worthless. -- Sinclair Lewis Maranatha! <>< John McKown -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: FTP Failing with space issues
we are looking at copy the file to a GDG, once it reaches the z/OS directory using the below job. so what i am looking is how we can automate this job so once file reaches the unix directory it copies and delete the source ? //COPYSTEP EXEC PGM=IKJEFT01 //FILE DD PATH='/export/home/PX1COMT/test.txt' //PTST DD DISP=SHR,DSN=PTHMICST.TEST.R1.Y(+1) //SYSTSPRT DD SYSOUT=* //SYSTSIN DD * OCOPY INDD(FILE) OUTDD(PTST) TEXT what i am thinking is scheduling the job at different time of the day . is this a good option or there is any other way to do it ? Regards Ron T -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: FTP Failing with space issues
On Thu, 27 Apr 2017 12:43:17 -0500, Paul Gilmartin wrote: > >cat linux.file | sftp user@zOS "cp [-options] /dev/fd/0 > \"//'data.set.name(member)'\"" > Brain check. I mean: cat linux.file | ssh user@zOS "cp [-options] /dev/fd/0 \"//'data.set.name(member)'\"" -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: FTP Failing with space issues
On Thu, 27 Apr 2017 11:51:21 -0500, Ron Thomas wrote: >Thanks for all the suggestions , Also, i would like to know how we can trigger >the copy from the z/OS UNIX directory to a data set as soon the file arrives >in the unix directory from the linux VM? > If I had sftp and I could rely on the associated ssh's not being disabled, I'd not bother to "trigger the copy". I'd do it in one command: cat linux.file | sftp user@zOS "cp [-options] /dev/fd/0 \"//'data.set.name(member)'\"" Preallocate the receiving data set with suitable attributes and space. If you rely on the "cp" command to create that data set, be aware that SPACE in the "cp" command has a bizarre behavior (I think it's a bug (i.e. WAD) institutionalized for spurious compatibility). Specify a secondary extent large enough to contain the data. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: FTP Failing with space issues
Thanks for all the suggestions , Also, i would like to know how we can trigger the copy from the z/OS UNIX directory to a data set as soon the file arrives in the unix directory from the linux VM? Regards Ron T -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: FTP Failing with space issues
The criteria we are planning is the files which are more than 30 days old (Creation Date). Thanks! -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: FTP Failing with space issues
On Tue, Apr 25, 2017 at 2:18 PM, Ron Thomaswrote: > We finally decided to move the files to Z/OS unix , we plan to create a > monthly folder to which we push all the files from linux VM. Once the file > is there we will move back to GDG's . I have a query here , is there any > job which i can use to clean up the files in the z/os unix folder . Please > share if any one has the details on this . > With what criteria? I have my UNIX syslog daemon files going into the /var/log directory. Each day, a new file is generated (more on that later, if you're interested). I only want to keep the last 7 days. So, every day at 01:00 (a.m. local time), I have the cron daemon run the following command: find /var/log -mtime +7 | xargs rm -v # remove files more that 7 days old The stuff after the # is a comment since # is the shell's "begin comment" character, much like C/C++'s // You can run this using cron, as I do. Or you can set up a batch job which runs BPXBATCH do to the same thing and schedule it via something like CA-7. //RMFILES EXEC PGM=BPXBATCH,REGION=0M, // PARM='find /var/log -mtime +7 | xargs rm -v' //STDOUT DD SYSOUT=* //STDIN DD * /* //* Of course, you must run the job using a RACF id which has the appropriate UNIX authority to unlink (the proper UNIX term instead of "delete") the file. This could be "root" (bad idea), or the RACF id of the "owner" of the file(s), or a RACF id with the proper UNIXPRIV profile access, per https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.2.0/com.ibm.zos.v2r2.bpxb200/usspriv.htm If you want to copy each file to a separate GDG and delete it once that it done, it is more difficult because "cp" does not support creating a new GDG (+1) entry. There are "clever" ways to do it, but "clever" ways are often "rickety". > > Regards > Ron T > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- "Irrigation of the land with seawater desalinated by fusion power is ancient. It's called 'rain'." -- Michael McClary, in alt.fusion Maranatha! <>< John McKown -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: FTP Failing with space issues
IBM provides a sample script called skulker. I use it to clean out /tmp on a daily basis for stuff older than a certain number of days old, and is scheduled in CRONTAB # Skulker # Remove files from (first argument) that are equal to or # older than (second argument). # See the UNIX System Services Command Reference book for the complete # skulker documentation. # # NOTE: This file can be modified to suit your particular needs. _ Dave Jousma Manager Mainframe Engineering, Assistant Vice President david.jou...@53.com 1830 East Paris, Grand Rapids, MI 49546 MD RSCB2H p 616.653.8429 f 616.653.2717 -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Ron Thomas Sent: Tuesday, April 25, 2017 3:18 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: FTP Failing with space issues We finally decided to move the files to Z/OS unix , we plan to create a monthly folder to which we push all the files from linux VM. Once the file is there we will move back to GDG's . I have a query here , is there any job which i can use to clean up the files in the z/os unix folder . Please share if any one has the details on this . Regards Ron T -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN This e-mail transmission contains information that is confidential and may be privileged. It is intended only for the addressee(s) named above. If you receive this e-mail in error, please do not read, copy or disseminate it in any manner. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this information is prohibited. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please erase it from your computer system. Your assistance in correcting this error is appreciated. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: FTP Failing with space issues
We finally decided to move the files to Z/OS unix , we plan to create a monthly folder to which we push all the files from linux VM. Once the file is there we will move back to GDG's . I have a query here , is there any job which i can use to clean up the files in the z/os unix folder . Please share if any one has the details on this . Regards Ron T -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: FTP Failing with space issues
On Tue, 25 Apr 2017 05:39:18 -0500, Walt Farrell wrote: >On Mon, 24 Apr 2017 21:30:28 -0500, Paul Gilmartin>wrote: > >>... so I tried: >> >>548 $ sudo cat ~wombat/.ssh/rc >>/bin/id >>/bin/uname >>/bin/date >> >>... I see no evidence that the commands in ~wombat/.ssh/rc were executed. ... > >You could try adding a command that will leave evidence when it runs. For >example, perhaps a "touch" command for a file that doesn't already exist. > Indeed. With a user added as: 575 $ grep wombat /etc/passwd wombat:x:1001:1001:x,x,x,x,x:/home/wombat:/home/wombat/loginshell ... a "ps" in ~wombat/.ssh/rc shows the command: sh -c /home/wombat/loginshell -c '/bin/sh .ssh/rc' I don't understand the purpose of the initial "sh -c". It's disappointing that ssh can't invoke ~/.ssh/rc in a fashion that allows environment variables to be propagated to the interactive shell, as login does with .profile. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: FTP Failing with space issues
On Mon, 24 Apr 2017 21:30:28 -0500, Paul Gilmartinwrote: >... so I tried: > >548 $ sudo cat ~wombat/.ssh/rc >/bin/id >/bin/uname >/bin/date > >... I see no evidence that the commands in ~wombat/.ssh/rc were executed. >I can't tell exactly what happened. Nor does the man page tell what processor >executes the commands in ~/.ssh/.rc "before the user's shell is started." It >seems a contradiction to expect the user's shell to execute a script before it >is started. You could try adding a command that will leave evidence when it runs. For example, perhaps a "touch" command for a file that doesn't already exist. -- Walt -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: FTP Failing with space issues
On Mon, 24 Apr 2017 18:44:10 -0500, Bill Godfrey wrote: >>> >>From "man ssh" (on Linux): >> >>NAME >> ssh - OpenSSH SSH client (remote login program) >> >>SYNOPSIS >> ssh [-options] [user@]hostname [command] >> >>DESCRIPTION >> ... >> If command is specified, it is executed on the remote host instead of a >> login shell. >> >>Note "instead of", providing a circumvention. >> > >What actually happens is that the account's shell is executed with arguments >"-c" and the command text, >which means the account's shell is not running as a "login shell". >I'm speaking of Linux. I haven't worked with ssh/sshd on z/OS. > Empirically, I confirm that. The man page omits mentioning "the account's shell". FILES ... ~/.ssh/rc Commands in this file are executed by ssh when the user logs in, just before the user's shell (or command) is started. See the sshd(8) manual page for more information. ... so I tried: 546 $ grep wombat /etc/passwd wombat:x:1001:1001:x,x,x,x,x:/home/wombat:/usr/lib/openssh/sftp-server 547 $ 547 $ sudo ls -al ~wombat/.ssh total 12 drwx-- 2 wombat wombat 4096 Apr 24 18:38 . drwxr-xr-x 3 wombat wombat 4096 Apr 24 18:35 .. -rwx-- 1 wombat wombat 29 Apr 24 18:43 rc 548 $ 548 $ sudo cat ~wombat/.ssh/rc /bin/id /bin/uname /bin/date ... I see no evidence that the commands in ~wombat/.ssh/rc were executed. I can't tell exactly what happened. Nor does the man page tell what processor executes the commands in ~/.ssh/.rc "before the user's shell is started." It seems a contradiction to expect the user's shell to execute a script before it is started. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: FTP Failing with space issues
On Mon, 24 Apr 2017 16:36:29 -0600, Paul Gilmartin wrote: >On 2017-04-24, at 16:17, Pew, Curtis G wrote: >>> >>> sftp depends on ssh. But ... is it possible to configure ssh so only the >>> sftp >>> agent, not a shell, is allowed as an ssh agent on the server? >> >> Yes, at least on Linux. We have a server where most of the accounts are >> specified with 'sftp-server' as the login shell, so authorized users can >> drop off or pick up files from those accounts, but cannot run any code. >> >> I haven't tried this on z/OS. >> >From "man ssh" (on Linux): > >NAME > ssh - OpenSSH SSH client (remote login program) > >SYNOPSIS > ssh [-options] [user@]hostname [command] > >DESCRIPTION > ... > If command is specified, it is executed on the remote host instead of a > login shell. > >Note "instead of", providing a circumvention. > What actually happens is that the account's shell is executed with arguments "-c" and the command text, which means the account's shell is not running as a "login shell". I'm speaking of Linux. I haven't worked with ssh/sshd on z/OS. Bill -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: FTP Failing with space issues
On 2017-04-24, at 16:17, Pew, Curtis G wrote: >> >> sftp depends on ssh. But ... is it possible to configure ssh so only the >> sftp >> agent, not a shell, is allowed as an ssh agent on the server? > > Yes, at least on Linux. We have a server where most of the accounts are > specified with ‘sftp-server’ as the login shell, so authorized users can drop > off or pick up files from those accounts, but cannot run any code. > > I haven’t tried this on z/OS. > From "man ssh" (on Linux): NAME ssh — OpenSSH SSH client (remote login program) SYNOPSIS ssh [-options] [user@]hostname [command] DESCRIPTION ... If command is specified, it is executed on the remote host instead of a login shell. Note "instead of", providing a circumvention. And, on z/OS, the BPXWUNIX I mentioned earlier. Just don't let "most of the accounts" access/alter critical resources. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: FTP Failing with space issues
On 2017-04-24, at 12:20, Nims,Alva John (Al) wrote: > > ... you have to write to zFS first and then you can do a "!cp / > //'CH2ICST.X.Y.R1'" (without the double quotes) to get it to MVS. > Why bother with a copy. Just leave it in zFS and adjust DD statements in subsequent jobs as needed. With regard to John M.'s concern of "untold damage", the perpetrator can do nothing that couldn't be done by logging on to the z/OS account and executing the command there. If a security administrator has disabled shell on that z/OS account, there remains the need to similarly disable BPXWUNIX. Best just to limit the capabilities of that z/OS account: Protect the resources; don't rely on locking tools. That's how RACF works best. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: FTP Failing with space issues
On Apr 24, 2017, at 5:05 PM, Paul Gilmartin <000433f07816-dmarc-requ...@listserv.ua.edu> wrote: > > sftp depends on ssh. But ... is it possible to configure ssh so only the sftp > agent, not a shell, is allowed as an ssh agent on the server? Yes, at least on Linux. We have a server where most of the accounts are specified with ‘sftp-server’ as the login shell, so authorized users can drop off or pick up files from those accounts, but cannot run any code. I haven’t tried this on z/OS. -- Pew, Curtis G curtis@austin.utexas.edu ITS Systems/Core/Administrative Services -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: FTP Failing with space issues
On Mon, 24 Apr 2017 13:34:09 -0500, John McKown wrote: > >NO! > >You can NOT do a "!cp ..." to copy the file on the _server_ to a dataset on >the _server_. That is because the "!..." sftp command runs the given >command _ON THE CLIENT_ (i.e. your machine). Otherwise, some clever person >could possibly do untold damage by running some arbitrary command that they >just ftp'd to the server on the server. The thought makes me shudder. > sftp depends on ssh. But ... is it possible to configure ssh so only the sftp agent, not a shell, is allowed as an ssh agent on the server? Otherwise, there's the possibility of: cat malicious.script | ssh z/OS "sh" # to do untold damage. Or, in fact: ssh z/OS put malicious.script .profile ... and wait for untold damage to happen. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: FTP Failing with space issues
You are correct! Al Nims University of Florida -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of John McKown Sent: Monday, April 24, 2017 2:34 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: FTP Failing with space issues On Mon, Apr 24, 2017 at 1:20 PM, Nims,Alva John (Al) <ajn...@ufl.edu> wrote: > I agree with Walt, you are using sftp, which is a different beast that > ftp and as far as I know, yes I have not worked with sftp, just had to > do a cursory look at it recently, but have not gone down the road, > sftp does NOT support MVS data sets directly, it only works with zFS > (USS), so you have to write to zFS first and then you can do a "!cp > / //'CH2ICST.X.Y.R1'" (without the double quotes) to get it to MVS. > NO! You can NOT do a "!cp ..." to copy the file on the _server_ to a dataset on the _server_. That is because the "!..." sftp command runs the given command _ON THE CLIENT_ (i.e. your machine). Otherwise, some clever person could possibly do untold damage by running some arbitrary command that they just ftp'd to the server on the server. The thought makes me shudder. > > Al Nims > University of Florida > > -- "Irrigation of the land with seawater desalinated by fusion power is ancient. It's called 'rain'." -- Michael McClary, in alt.fusion Maranatha! <>< John McKown -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: FTP Failing with space issues
On Mon, Apr 24, 2017 at 1:20 PM, Nims,Alva John (Al)wrote: > I agree with Walt, you are using sftp, which is a different beast that ftp > and as far as I know, yes I have not worked with sftp, just had to do a > cursory look at it recently, but have not gone down the road, sftp does NOT > support MVS data sets directly, it only works with zFS (USS), so you have > to write to zFS first and then you can do a "!cp / > //'CH2ICST.X.Y.R1'" (without the double quotes) to get it to MVS. > NO! You can NOT do a "!cp ..." to copy the file on the _server_ to a dataset on the _server_. That is because the "!..." sftp command runs the given command _ON THE CLIENT_ (i.e. your machine). Otherwise, some clever person could possibly do untold damage by running some arbitrary command that they just ftp'd to the server on the server. The thought makes me shudder. > > Al Nims > University of Florida > > -- "Irrigation of the land with seawater desalinated by fusion power is ancient. It's called 'rain'." -- Michael McClary, in alt.fusion Maranatha! <>< John McKown -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: FTP Failing with space issues
I agree with Walt, you are using sftp, which is a different beast that ftp and as far as I know, yes I have not worked with sftp, just had to do a cursory look at it recently, but have not gone down the road, sftp does NOT support MVS data sets directly, it only works with zFS (USS), so you have to write to zFS first and then you can do a "!cp / //'CH2ICST.X.Y.R1'" (without the double quotes) to get it to MVS. Al Nims University of Florida -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Walt Farrell Sent: Monday, April 24, 2017 10:45 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: FTP Failing with space issues On Mon, 24 Apr 2017 08:17:55 -0500, Ron Thomas <ron5...@gmail.com> wrote: >i executed the below script from Linux VM and the below is what it says. >Looks like site command is not supported . So any idea on how this could be >resolved or is there any work around ? > >Script >--- >sftp to1c...@cray.cps.se.com ><< EOF >site blocksize=0 lrecl=3000 recfm=fb prim=25 sec=25 cyl put >/sap/co2ekh/backup/global_chgback_escoa_2017-01-22:22:00:10.txt >//'CH2ICST.X.Y.R1' >quit >EOF > >Log Message > >sftp> site blocksize=0 lrecl=3000 recfm=fb prim=25 sec=25 cyl >Invalid command. >sftp> put /sas/co2ekh/backup/global_chgback_escoa_2017-01-22:22:00:10.txt >//'CH2ICST.X.Y.R1' >Uploading /sas/comtekh/backup/global_chgback_escoa_2017-01-22:22:00:10.txt to >//CH2ICST.X.Y.R1 >/sap/co2ekh/backup/global_chgback_escoa_2017-01-22:22:00:10.txt > 68% 2208KB 1.8MB/s >00:00 ETA >Couldn't write to remote file "//CH2ICST.X.Y.R1": Failure You're not using ftp. You're using sftp, which is entirely different and not related to ftp at all. -- Walt -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: FTP Failing with space issues
On Mon, 24 Apr 2017 09:45:02 -0500, Walt Farrell wrote: >On Mon, 24 Apr 2017 08:17:55 -0500, Ron Thomas wrote: >> >>Script >>--- >>sftp to1c...@cray.cps.se.com >><< EOF >>site blocksize=0 lrecl=3000 recfm=fb prim=25 sec=25 cyl >>put /sap/co2ekh/backup/global_chgback_escoa_2017-01-22:22:00:10.txt >>//'CH2ICST.X.Y.R1' >>quit >>EOF >> >>Log Message >> >>sftp> site blocksize=0 lrecl=3000 recfm=fb prim=25 sec=25 cyl >>Invalid command. >>sftp> put /sas/co2ekh/backup/global_chgback_escoa_2017-01-22:22:00:10.txt >>//'CH2ICST.X.Y.R1' >>Uploading /sas/comtekh/backup/global_chgback_escoa_2017-01-22:22:00:10.txt to >>//CH2ICST.X.Y.R1 >>/sap/co2ekh/backup/global_chgback_escoa_2017-01-22:22:00:10.txt >>68% 2208KB 1.8MB/s >> 00:00 ETA >>Couldn't write to remote file "//CH2ICST.X.Y.R1": Failure > >You're not using ftp. You're using sftp, which is entirely different and not >related to ftp at all. > And sftp does not deal with Classic data sets; only with UNIX files, to which BLKSIZE, LRECL, RECFM, PRIM, and SEC are irrelevant. Unless you install the Dovetailed enhancements. https://dovetail.com/products/sftp.html But your source file is probably a stream-structured file for which a z/OS UNIX file is a better match than a Classic data set. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: FTP Failing with space issues
On Mon, 24 Apr 2017 08:17:55 -0500, Ron Thomaswrote: >i executed the below script from Linux VM and the below is what it says. >Looks like site command is not supported . So any idea on how this could be >resolved or is there any work around ? > >Script >--- >sftp to1c...@cray.cps.se.com ><< EOF >site blocksize=0 lrecl=3000 recfm=fb prim=25 sec=25 cyl >put /sap/co2ekh/backup/global_chgback_escoa_2017-01-22:22:00:10.txt >//'CH2ICST.X.Y.R1' >quit >EOF > >Log Message > >sftp> site blocksize=0 lrecl=3000 recfm=fb prim=25 sec=25 cyl >Invalid command. >sftp> put /sas/co2ekh/backup/global_chgback_escoa_2017-01-22:22:00:10.txt >//'CH2ICST.X.Y.R1' >Uploading /sas/comtekh/backup/global_chgback_escoa_2017-01-22:22:00:10.txt to >//CH2ICST.X.Y.R1 >/sap/co2ekh/backup/global_chgback_escoa_2017-01-22:22:00:10.txt > 68% 2208KB 1.8MB/s >00:00 ETA >Couldn't write to remote file "//CH2ICST.X.Y.R1": Failure You're not using ftp. You're using sftp, which is entirely different and not related to ftp at all. -- Walt -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: FTP Failing with space issues
Have you talked to you z/OS Sysprogs Linux Sysprogs Vtam/Comm Server Sysprogs TCP/IP Sysprogs? Your shop may have restrictions the list is not aware of - for example EXITS for FTP that impact the usage of common functions. If you talk to them, you may be able to solve your problem faster. Lizette > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Ron Thomas > Sent: Monday, April 24, 2017 7:08 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: FTP Failing with space issues > > with the modified one like "quote site blocksize=0 lrecl=3000 recfm=fb wrap > prim=25 sec=25 cyl" it is showing the same error. Thanks! > > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: FTP Failing with space issues
with the modified one like "quote site blocksize=0 lrecl=3000 recfm=fb wrap prim=25 sec=25 cyl" it is showing the same error. Thanks! -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: FTP Failing with space issues
Would the QUOTE command help in this instance, e.g. quote site Regards, Simon. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Ron Thomas Sent: 24 April 2017 14:18 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: FTP Failing with space issues i executed the below script from Linux VM and the below is what it says. Looks like site command is not supported . So any idea on how this could be resolved or is there any work around ? Script --- sftp to1c...@cray.cps.se.com << EOF site blocksize=0 lrecl=3000 recfm=fb prim=25 sec=25 cyl put /sap/co2ekh/backup/global_chgback_escoa_2017-01-22:22:00:10.txt //'CH2ICST.X.Y.R1' quit EOF Log Message sftp> site blocksize=0 lrecl=3000 recfm=fb prim=25 sec=25 cyl Invalid command. sftp> put /sas/co2ekh/backup/global_chgback_escoa_2017-01-22:22:00:10.txt //'CH2ICST.X.Y.R1' Uploading /sas/comtekh/backup/global_chgback_escoa_2017-01-22:22:00:10.txt to //CH2ICST.X.Y.R1 /sap/co2ekh/backup/global_chgback_escoa_2017-01-22:22:00:10.txt 68% 2208KB 1.8MB/s 00:00 ETA Couldn't write to remote file "//CH2ICST.X.Y.R1": Failure Regards Ron T -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ** The information in this E-Mail is confidential and may be legally privileged. It may not represent the views of the SSE Group. It is intended solely for the addressees. Access to this E-Mail by anyone else is unauthorised. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Any unauthorised recipient should advise the sender immediately of the error in transmission. Unless specifically stated otherwise, this email (or any attachments to it) is not an offer capable of acceptance or acceptance of an offer and it does not form part of a binding contractual agreement. SSE plc Registered Office: Inveralmond House 200 Dunkeld Road Perth PH1 3AQ Registered in Scotland No. SC117119 Authorised and regulated by the Financial Conduct Authority for certain consumer credit activities. www.sse.com ** -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: FTP Failing with space issues
i executed the below script from Linux VM and the below is what it says. Looks like site command is not supported . So any idea on how this could be resolved or is there any work around ? Script --- sftp to1c...@cray.cps.se.com << EOF site blocksize=0 lrecl=3000 recfm=fb prim=25 sec=25 cyl put /sap/co2ekh/backup/global_chgback_escoa_2017-01-22:22:00:10.txt //'CH2ICST.X.Y.R1' quit EOF Log Message sftp> site blocksize=0 lrecl=3000 recfm=fb prim=25 sec=25 cyl Invalid command. sftp> put /sas/co2ekh/backup/global_chgback_escoa_2017-01-22:22:00:10.txt //'CH2ICST.X.Y.R1' Uploading /sas/comtekh/backup/global_chgback_escoa_2017-01-22:22:00:10.txt to //CH2ICST.X.Y.R1 /sap/co2ekh/backup/global_chgback_escoa_2017-01-22:22:00:10.txt 68% 2208KB 1.8MB/s 00:00 ETA Couldn't write to remote file "//CH2ICST.X.Y.R1": Failure Regards Ron T -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: FTP Failing with space issues
Ok what you say is that we can do like the one below . is that what you are referring ? SITE BLOCKSIZE=0 LRECL=133 WRAP RECFM=FB PRI=20 SEC=10 CYL put unix_file.txt 'HLQ.MAINFRAME.FILE(+1)' (replace Thanks Ron T -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: FTP Failing with space issues
So going from a "windows" environment to mainframe - there is a difference with record sizes. The "windows" environment has long records. The file being created in the mainframe side (and you should logon to the mainframe to view it in Option 3.4) will have a fixed or VB record length that may not be long enough. The SMS functions may not allocate your file on the mainframe long enough. For example, your CSV file has a maximum line length of 356 characters. But on the mainframe side the default allocation you are getting is an LRECL of 80. This can create this type of error. Note: When working on moving data from PC to MF or MF to PC would be best done while you are active in BOTH environments. Then where there is an error you can look on the system where the error came from can be viewed. If possible, you might want to see if you have access to tools like FILEZILLA or REFLECTIONS FTP. Both can provide a better interface than native FTP, IMO. You need to know how many characters on a line, then set the LRECL to the maximum length. Lizette > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Ron Thomas > Sent: Friday, April 21, 2017 10:40 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: FTP Failing with space issues > > Ok . i tried to copy a csv file that is there in the shell and i am getting > the below message . I tried increasing the LRECL of the PDS file and still the > same issue . Any idea on what could be the issue here ? > > $ cp -T SN_ASC00_03212017.csv "//'ng772pt.X.Y.Z'" > cp: FSUM6260 write error on file "//'ng772pt.X.Y.Z'": EDC5003I Truncation of a > record occurred during an I/O operation. > > Thanks > Ron T > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: FTP Failing with space issues
You may wish to work with your z/OS Sysprogs on setting up GDGs with sufficient size. Then a +1 dataset can be created without the need to delete/allocate process. The GDG can have a limit of 1 or other to accommodate your needs. Lizette > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Ron Thomas > Sent: Thursday, April 20, 2017 8:11 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: FTP Failing with space issues > > failing with X37 abends. The file is already allocated one in mainframe . I am > not sure whether we can allocate the file from linux virtual machine script > ? if possible , how this can be done ? Thanks. > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: FTP Failing with space issues
Ok . i tried to copy a csv file that is there in the shell and i am getting the below message . I tried increasing the LRECL of the PDS file and still the same issue . Any idea on what could be the issue here ? $ cp -T SN_ASC00_03212017.csv "//'ng772pt.X.Y.Z'" cp: FSUM6260 write error on file "//'ng772pt.X.Y.Z'": EDC5003I Truncation of a record occurred during an I/O operation. Thanks Ron T -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: FTP Failing with space issues
Unless your stg admins on the mainframe side say there is a limitation, there is probably no limitation. In my shop, we allow as many files as the users want to send up to the mainframe and in various sizes from small (1tk) to huge >4gb. The SMS code will handle the files locations to the correct storage pools. And I ensure the storage pools have sufficient storage to handle the process. Helps when users tell me they are adding new files to upload to the mainframe. If you contact the team that manages the mainframe storage and tell them what you are going to do, they should be able to help you. Lizette > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Ron Thomas > Sent: Friday, April 21, 2017 10:08 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: FTP Failing with space issues > > Ok , in that case if on the mainframe side has a file system setup , then they > can send the file and from there we can copy back a PDS location. > I need to understand whether there is any limitation on the number of files > send or any memory constraints ? is that the best approach ? > I am new to this one , if this is the best one i can talk to the system folks > for the access and other details . > > Thanks > Ron T > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: FTP Failing with space issues
Ok , in that case if on the mainframe side has a file system setup , then they can send the file and from there we can copy back a PDS location. I need to understand whether there is any limitation on the number of files send or any memory constraints ? is that the best approach ? I am new to this one , if this is the best one i can talk to the system folks for the access and other details . Thanks Ron T -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: FTP Failing with space issues
That will depend on z/OS. Is 16 cylinders sufficient for the file? How large (MB/GB/Bytes) is the file. Otherwise, you should talk to your stg admins on what your file requires. SMS might constrain your dataset. Lizette > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Ron Thomas > Sent: Thursday, April 20, 2017 8:46 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: FTP Failing with space issues > > Ok. is the below one coded will work from linux > > LOCSITE BLOCKSIZE=0 LRECL=133 WRAP RECFM=FB PRI=1 SEC=1 CYL > delete 'HLQ.MAINFRAME.FILE' > get linux_file.txt 'HLQ.MAINFRAME.FILE' (replace > > Thanks > Ron T > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: FTP Failing with space issues
If the mainframe side has a file system setup for you, then instead of put linux_file.txt //'HLQ.MAINFRAME.FILE' It would be something like this: Put linux_file.txt /u/xyz/mainframe.file The single "/" will trigger the mainframe FTP server to treat it as another UNIX file, a file to be accessed via Unix Systems Services(USS). The "/u/xyz/" is just something I made up, it would be whatever is setup for you. Al Nims Systems Admin/Programmer 3 UFIT University of Florida (352) 273-1298 -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Ron Thomas Sent: Thursday, April 20, 2017 3:07 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: FTP Failing with space issues No i haven't thought about that as i am not sure how to do that . Thanks! -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: FTP Failing with space issues
No i haven't thought about that as i am not sure how to do that . Thanks! -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: FTP Failing with space issues
On Thu, 20 Apr 2017 13:33:09 -0500, Ron Thomas wrote: >Ok , whaat i am looking is to push the file from LINUX to Mainframe . So, the >one below is fine ? > >SITE BLOCKSIZE=0 LRECL=133 WRAP RECFM=FB PRI=1 SEC=1 CYL >delete 'HLQ.MAINFRAME.FILE' >put linux_file.txt //'HLQ.MAINFRAME.FILE' > Have you considered using a z/OS UNIX file instead of a Classic data set and bypassing all this mickeymouse? --- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: FTP Failing with space issues
Ok , whaat i am looking is to push the file from LINUX to Mainframe . So, the one below is fine ? SITE BLOCKSIZE=0 LRECL=133 WRAP RECFM=FB PRI=1 SEC=1 CYL delete 'HLQ.MAINFRAME.FILE' put linux_file.txt //'HLQ.MAINFRAME.FILE' Thanks Ron T -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: FTP Failing with space issues
The closest you can get even in 2.02 is to use; BLKsize=### and BLocks . Al Nims Systems Admin/Programmer 3 UFIT University of Florida (352) 273-1298 -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Paul Gilmartin Sent: Thursday, April 20, 2017 1:22 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: FTP Failing with space issues On 2017-04-20, at 09:08, Nims,Alva John (Al) wrote: > You could include one of the following commands in the FTP command stream on > the remote system. > "remote"? It appears to be the OP's local system. (Point of view; I understand.) > QUOTE SITE PRIM=## SEC=## TRacks > Or > QUOTE SITE PRIM=## SEC=## CYlinders > "TRacks" or "CYlinders", but not "BYTES"? (I RTFM.) Bad design for the needs of the OP who probably knows the size of the source file only in bytes. And may not be familiar with the geometries of various IBM storage subsystems. Doesn't IBM nowadays recommend allocation in bytes rather than tracks? Simply, FTP should support: QUOTE SITE PRIM=## SEC=## BYTES -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: FTP Failing with space issues
On 2017-04-20, at 09:08, Nims,Alva John (Al) wrote: > You could include one of the following commands in the FTP command stream on > the remote system. > "remote"? It appears to be the OP's local system. (Point of view; I understand.) > QUOTE SITE PRIM=## SEC=## TRacks > Or > QUOTE SITE PRIM=## SEC=## CYlinders > "TRacks" or "CYlinders", but not "BYTES"? (I RTFM.) Bad design for the needs of the OP who probably knows the size of the source file only in bytes. And may not be familiar with the geometries of various IBM storage subsystems. Doesn't IBM nowadays recommend allocation in bytes rather than tracks? Simply, FTP should support: QUOTE SITE PRIM=## SEC=## BYTES -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: FTP Failing with space issues
Is this an FTP that executes from the z/OS system to "pull" a Linux file to the mainframe or a Linux FTP to "push" a file up to the mainframe? From your example it appears to be a "pull" setup. For a "pull" request running on z/OS I would put a "delete file " step (just an IEBR14) before the FTP step to delete the file to be pulled in and then just set the LOCSITE values and get the file without the "(replace" option, mainly because I have not RTFM in the z/OS CommServer docs to see if z/OS FTP supports the "delete" command. I.E.: //DELFILE EXEC PGM=IEFBR14 //DELFILE DD DISP=(OLD,DELETE),DSN=HLQ.MAINFRAME.FILE //* //FTPSTEP EXEC PGM=FTP, . . . Etc. If it were me I would also use at least "PRI=10 SEC=10" on the LOCSITE instead of 1 cylinder. Using a primary and secondary of 1 cylinder each seems to me to be a sure way to generate x37 abends in the absence of an "x37 avoiding" software product running on the system. HTH Peter -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Ron Thomas Sent: Thursday, April 20, 2017 11:46 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: FTP Failing with space issues Ok. is the below one coded will work from linux LOCSITE BLOCKSIZE=0 LRECL=133 WRAP RECFM=FB PRI=1 SEC=1 CYL delete 'HLQ.MAINFRAME.FILE' get linux_file.txt 'HLQ.MAINFRAME.FILE' (replace Thanks Ron T -- This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: FTP Failing with space issues
Ok. is the below one coded will work from linux LOCSITE BLOCKSIZE=0 LRECL=133 WRAP RECFM=FB PRI=1 SEC=1 CYL delete 'HLQ.MAINFRAME.FILE' get linux_file.txt 'HLQ.MAINFRAME.FILE' (replace Thanks Ron T -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: FTP Failing with space issues
NO. YOU can delete the file and allocate with FTP subcommands QUOTE SITE PRIMARY(X) SECONDARY(Y) and (one of) CYL TRK See the fin manuals for syntax -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Ron Thomas Sent: Thursday, April 20, 2017 10:29 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: FTP Failing with space issues So just wanted to understand , whether we can delete the file that is existing and then allocate the file from the virtual machine shell script ? if so how we can do the same , so we can get the correct data in mainframe with out FTP failure issues ? any sample code i can look ? Thanks, Ron T -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ::DISCLAIMER:: The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: FTP Failing with space issues
So just wanted to understand , whether we can delete the file that is existing and then allocate the file from the virtual machine shell script ? if so how we can do the same , so we can get the correct data in mainframe with out FTP failure issues ? any sample code i can look ? Thanks, Ron T -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: FTP Failing with space issues
> You cannot enlarge an existing dataset. Sorry, I forgot to add, if you allocate it without secondary extents, then you cannot enlarge it. Groete / Greetings Elardus Engelbrecht -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: FTP Failing with space issues
Ron Thomas wrote: >failing with X37 abends. Just post the full message(s). >The file is already allocated one in mainframe . Your failure depends on how the dataset was allocated in the first place and how big it already is and limits placed by SMS. >I am not sure whether we can allocate the file from linux virtual machine >script ? if possible , how this can be done ? You can, see Alva's reply, but then you may need to allocate a brand new dataset with the right allocation parameters. You cannot enlarge an existing dataset. Groete / Greetings Elardus Engelbrecht -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: FTP Failing with space issues
Yes you can. See quite site subcommands primary secondary. Can also delete/reallocate the existing file. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Ron Thomas Sent: Thursday, April 20, 2017 10:11 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: FTP Failing with space issues failing with X37 abends. The file is already allocated one in mainframe . I am not sure whether we can allocate the file from linux virtual machine script ? if possible , how this can be done ? Thanks. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ::DISCLAIMER:: The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: FTP Failing with space issues
failing with X37 abends. The file is already allocated one in mainframe . I am not sure whether we can allocate the file from linux virtual machine script ? if possible , how this can be done ? Thanks. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: FTP Failing with space issues
You could include one of the following commands in the FTP command stream on the remote system. QUOTE SITE PRIM=## SEC=## TRacks Or QUOTE SITE PRIM=## SEC=## CYlinders PRIM is the Primary allocation space using the "TRacks, CYlinders, or BLocks" SEC is the Secondary allocation space using ... "SITE" is a command to the z/OS FTP server and "QUOTE" is usually the local command that "Sends an uninterpreted string of data" to the remote server. Al Nims Systems Admin/Programmer 3 UFIT University of Florida (352) 273-1298 -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Ron Thomas Sent: Thursday, April 20, 2017 10:51 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: FTP Failing with space issues Hello . Some of the files that is FTP'ed to mainframe from a Linux VM machine failed with space issues . Is there any way we can provide a work around logic. Regards Ron T -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: FTP Failing with space issues
Ron Thomas wrote: >Some of the files that is FTP'ed to mainframe from a Linux VM machine failed >with space issues . Files or datasets? What do you mean by 'mainframe'? z/OS? z/VM? Other operating system. Please post the FTP message(s) of the failure. Please post your FTP statements too. >Is there any way we can provide a work around logic. It depends. Groete / Greetings Elardus Engelbrecht -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: FTP Failing with space issues
What kind of space issue, X37 Abends or allocation failures? -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Ron Thomas Sent: Thursday, April 20, 2017 9:51 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: FTP Failing with space issues Hello . Some of the files that is FTP'ed to mainframe from a Linux VM machine failed with space issues . Is there any way we can provide a work around logic. Regards Ron T -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ::DISCLAIMER:: The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN