Nat,

I agree with your second suggestion...too much work using your first suggestion...lot easier coding a DD card.

Thanks again for your help. Dave

On Fri, 9 Apr 2010 14:06:13 -0400, Nathaniel Wooding <nathaniel.wooding@DOM.COM> wrote:

>Dave >I have never used PKZIP on the mainframe so I don't know the syntax but you may be able to build the whole PKZIP code using a SAS step and then submit it using an X command or, as I did years ago, build a flat file containing the statements and have the internal reader submit that file. > >I suspect, though, that it would be a whole lot simpler to simply stick a DD card in the pkzip step. > >Nat > >-----Original Message----- >From: Dave Brewer [mailto:david.brewer@UC.EDU] >Sent: Friday, April 09, 2010 1:43 PM >To: SAS-L@LISTSERV.UGA.EDU; Nathaniel Wooding (Services - 6) >Subject: Re: MVS Filename vs DD DSNAME= > >Nat, > >Step 2 is a non-SAS step; the step will use PKZIP to compress the >transport file created in step 1 (SAS step). > >I figured that the filename won't work and I need to use a DD card to >allocate my transport data set. I thought that there might be an option on >the FILENAME that would tell the INTERNAL READER that SAS is creating the >data set, but to no avail. > >Thanks for your help. >Dave > >On Fri, 9 Apr 2010 13:26:34 -0400, Nathaniel Wooding ><nathaniel.wooding@DOM.COM> wrote: > >>Dave >> >>When you refer to "step 2 zip step", are you referring to a subsequent >SAS step or a new ZOS Job step. If the former, the filename should be >available. If the latter, you would need to have a new JCL DD card unless >there is some means of passing this information from one job step to the >next -- I never got that fancy. >> >>Nat Wooding >> >>-----Original Message----- >>From: SAS(r) Discussion [mailto:SAS-L@LISTSERV.UGA.EDU] On Behalf Of Dave >>Sent: Friday, April 09, 2010 9:30 AM >>To: SAS-L@LISTSERV.UGA.EDU >>Subject: MVS Filename vs DD DSNAME= >> >>Hi SAS-L >> >>I am transporting files from the mainframe to the PC using PROC CPORT. I >>have this set up as a 2 step process: the first step is the PROC CPORT and >>the second step is PKZIP to compress the file that will then be d/l via >>ftp. >> >>If I use JCL to allocate my transport file, the job runs successfully. >>When I replace the JCL with FILENAME to allocate my transport file, the >>jobs fails b/c the internal reader says it can't find the transport file >>which is referenced in my step 2 zip step. >> >>Is there a way to use FILENAME to allocate the file in the SAS step which >>will then be used in the next step? It appears that zOS will look for all >>needed data sets first and then run the code. How can I get around this? >> >>Thanks. >>Dave >>CONFIDENTIALITY NOTICE: This electronic message contains >>information which may be legally confidential and or privileged and >>does not in any case represent a firm ENERGY COMMODITY bid or offer >>relating thereto which binds the sender without an additional >>express written confirmation to that effect. The information is >>intended solely for the individual or entity named above and access >>by anyone else is unauthorized. If you are not the intended >>recipient, any disclosure, copying, distribution, or use of the >>contents of this information is prohibited and may be unlawful. If >>you have received this electronic transmission in error, please >>reply immediately to the sender that you have received the message >>in error, and delete it. Thank you.