| Date: | Fri, 26 Oct 2001 10:42:33 -0400 |
| Reply-To: | "Braten, Michael (Exchange)" <mbraten@BEAR.COM> |
| Sender: | "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU> |
| From: | "Braten, Michael (Exchange)" <mbraten@BEAR.COM> |
| Subject: | Re: OS/390, v8.1, filevar and creating sequential files on the |
| Content-Type: | text/plain |
|---|
You are correct that FILE cant do it. But SAS can allocate a file
dynamically as if done via JCL. This is done by way
of the FILENAME statement. FILENAME in an OS/390 makes use of JCL parms and
creates the physical file. More can be
learned in the MVS Companion manual.
> -----Original Message-----
> From: Puddin' Man [SMTP:pudding_man@POSTMARK.NET]
> Sent: Friday, October 26, 2001 10:08 AM
> To: SAS-L@LISTSERV.UGA.EDU
> Subject: Re: OS/390, v8.1, filevar and creating sequential files on
> the
>
> fly
> Date: Fri, 26 Oct 2001 14:07:54 +0000
> Content-Type: text/plain; charset="iso-8859-1"
>
>
>
> Droogendyk, Harry wrote:
>
> > Listers:
> >
> > Back again. I wish to write an undetermined number of sequential files
> from
> > a data step. Contents of incoming data will determine the name and
> number
> > of files to be created. Seemingly a perfect application for the
> FILEVAR=
> > option on the FILE statement.
>
> --- snip ---
>
> This is a piece o' cake to do with Windoze SAS. I suspect the same
> is true with "La Unices". Not so with "The OS/VS Beasty": I couldn't
> get my OS/390 to do it.
>
> OS/390 requires much info to allocate a new file. It wants DCB's,
> DISP, SPACE, maybe a device class or device, maybe other stuff.
> It appears that the FILE command was not designed to supply all this.
>
> I had no problem getting Svend's code to test out. I suspect it
> is the best way for Harry to go.
>
> Cheers,
> Puddin'
>
> *******************************************************
> *** Puddin' Man *** Pudding_Man@postmark.net *****
> *******************************************************;
****************************************************************
Bear Stearns is not responsible for any recommendation, solicitation,
offer or agreement or any information about any transaction, customer
account or account activity contained in this communication.
***********************************************************************
|