The //DD: option also supports DD * and SYSOUT, and all of those other wonderful little features of JCL like DEFER and RLSE and so forth.
The "temporary file" problem is actually a subset of a larger problem - FTP requires that all (non-DD) existing datasets be cataloged, and catalogs all (non-DD) datasets that it creates. Good in most cases, but may not be what you want in all cases. //DD: lets you support PASS and VOL=SER= and so forth. Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Skip Robinson Sent: Thursday, April 27, 2006 11:22 AM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: FTP PUT of a temporary dataset The DD: option can be useful for solving other problems as well. We had case recently where an application occasionally failed in FTPing a 'normally named' data set. The message would be something like 'file not available'. I looked at syslog for a few instances and found each time that a full volume backup was just starting up around the time of the job failure. We had them replace 'FTP dsn...' with 'FTP DD:file...' . Their problem seems to have cleared. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
