Date: Fri, 9 Apr 2010 13:47:44 -0700
Reply-To: Jack Hamilton <jfh@STANFORDALUMNI.ORG>
Sender: "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From: Jack Hamilton <jfh@STANFORDALUMNI.ORG>
Subject: Re: MVS Filename vs DD DSNAME=
Content-Type: text/plain; charset=us-ascii
It would be helpful for you to show the code and JCL.
This runs without error and as expected:
//S1ALLOC EXEC SASPROD
//SYSIN DD *
filename newfile '.testfile.txt' disp=(new,catlg,catlg)
space=(trk,1) lrecl=80 recfm=fb;
//S2USE EXEC PGM=IEFBR14
//TESTFILE DD DSN=&SYSUID..TESTFILE.TXT,DISP=SHR
I'm not sure what you mean by "internal reader says it can't find the transport file". It's not the internal reader that checks JCL. Do you mean the JCL processor?
And why don't you want to use a DD? That gives you the big benefit of using the OS's enqueuing.
Caelum non animum mutant qui trans mare currunt.
On Apr 9, 2010, at 6:30 , Dave wrote:
> 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
> 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?