Date: Fri, 25 Jan 2008 15:08:31 -0500
Reply-To: Nathaniel.Wooding@DOM.COM
Sender: "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From: Nat Wooding <Nathaniel.Wooding@DOM.COM>
Subject: Re: Mainframe libname
In-Reply-To: <012520081957.8692.479A3F3E0009A6F1000021F422230647629B0A02D2089B9A019C04040A0DBF0A0401089C0E9C@att.net>
Content-Type: text/plain; charset="US-ASCII"
Paul
I had forgotten about HFS so I'm glad that I stopped short of thundering in
with my standard file names.
With HFS, shouldn't he/she still have a Disp=Old on the libname?
Nat
Nat Wooding
Environmental Specialist III
Dominion, Environmental Biology
4111 Castlewood Rd
Richmond, VA 23234
Phone:804-271-5313, Fax: 804-271-2977
Paul Dorfman
<sashole@BELLSOUT
H.NET> To
Sent by: "SAS(r) SAS-L@LISTSERV.UGA.EDU
Discussion" cc
<SAS-L@LISTSERV.U
GA.EDU> Subject
Re: Mainframe libname
01/25/2008 02:57
PM
Please respond to
Paul Dorfman
<sashole@BELLSOUT
H.NET>
Steve,
You are right unless in Shaunak's MF environment HFS (Hierarchical File
System) is set up and running, making the ambiance indistinguishable from
UNIX (through the user's prism, of course), -- which methinks is likely
judging from the file name referenced in the LIBNAME statement. In this
case, the error may lie elsewhere, but we will not know until s/he reveals
what it is.
Kind regards
------------
Paul Dorfman
Jax, FL
------------
-------------- Original message ----------------------
From: Steve James <spj1@CDC.GOV>
>
> It's been a number of years since I've worked on a mainframe (IBM MVS)
> but the environment is quite a bit different from a Windows or Unix
> platform. Where those two are set up in a directory structure (e.g. c:
> \directory\subdirectory\subsubdirectory... etc.), the mainframe
> isn't. The mainframe groups files under userids (either a personal
> one or a group) with a two level name (name + extension). It then may
> store files within a single 'file' as in the case of a Partitioned
> Data-set (PDS) or a SAS data library . A SAS data library is really a
> single file on the mainframe. It may be named something like
> SPJ1.MYDATA.SASDATA where SPJ1 is my userid, MYDATA is the name of the
> dataset and SASDATA is the extension. Within this SAS data library
> there can be many SAS data sets. It looks like from your LIBNAME
> statement below that you are confusing the data structure of the
> mainframe with a data structure that's directory-based since you have
> slashes in the file name.
>
> Steve
>
>
> On Jan 25, 10:23 am, "shaunak.adgaon...@gmail.com"
> <shaunak.adgaon...@gmail.com> wrote:
> > I am new to mainframes. What i want to do is to get the mainframe file
> > to SAS permanent dataset. Will the libname statement be of any use. I
> > will give you the exact code
> >
> > LIBNAME AWDDATA 'SAS_USER/REPORTINGDATA/FSO_ICS';
> >
> > FILENAME AWDIP 'PC.MFD.F5725.SVC.METRICS' disp=shr;
> >
> > DATA AWDDATA.AWDIP;
> > INFILE AWDIP;
> > format key_date yymmdd10.
> > key_time time8.
> > Begin_Date yymmdd10.
> > Begin_Time time8.
> > End_Date yymmdd10.
> > End_Time time8.;
> > INPUT @1 Key_Date
YYMMDD10.
> > @11 Key_Time
time8.
> > @19 Key_Millisecond $6.
> > @25 Record_Code $1.
> > @26 Create_Node $2.
> > @28 Begin_Unit_Code $10.
> > @38 Begin_Work_Type $10.
> > @48 Begin_Status $10.
> > @58 Begin_Queue $8.
> > @66 Begin_Date
YYMMDD10.
> > @77 Begin_Time time8.
> > @92 End_Unit_Code $10.
> > @102 End_Work_Type $10.
> > @112 End_Status $10.
> > @122 End_Queue $8.
> > @130 End_Date
YYMMDD10.
> > @141 End_Time time8.
> > @156 End_User_Identifier $8.
> > @164 Fund
$7.
> > @171 Account $11.
> > ;
> > run;
> >
> > but it gives me error. Please help guys
-----------------------------------------
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.
|