topic Re: PDS Members Create for BY Variable in ODS and Base Reporting

PDS Members Create for BY Variable

rkumar23 — Tue, 25 Nov 2014 03:30:23 GMT

Could somebody throw me an idea where I like to create Seperate PDS members for BY Variable ....

For example based on below GLIBSEQN like to create the Different PDS members ...

DATA LAB1;

INFILE DATALINES ;

INPUT

DAT DATE9. TIM TIME5. GLIBSEQN $ CLUSTER $ DLIB $ DISTNAME $ Deferr $8.

threshold $8. ;

DATALINES;

01OCT14 0:00 10000 04 10015 RVDRVA15 0:00 1:00

01OCT14 0:00 10000 02 10018 KCDRVA18 0:02 1:00

01OCT14 0:00 10000 05 10016 KCDRVA16 0:01 1:00

01OCT14 0:00 10000 00 10017 RVDRVA17 0:00 1:00

01OCT14 0:00 20000 03 1001A KCDRVA1A 0:02 1:00

01OCT14 0:30 20000 02 10018 KCDRVA18 0:02 1:00

01OCT14 0:30 20000 05 10016 KCDRVA16 0:01 1:00

01OCT14 0:30 20000 00 10017 RVDRVA17 0:00 1:00

proc print data=lab1;run;

Re: PDS Members Create for BY Variable

Reeza — Tue, 25 Nov 2014 03:52:45 GMT

I don't know what you mean , can you elaborate on your question.

Here are two links on how to ask a good question.

How do I ask a good question? - Help Center - Stack Overflow

Re: PDS Members Create for BY Variable

rkumar23 — Tue, 25 Nov 2014 06:48:34 GMT

I have put the data hopefully that explain what I was asking...

Re: PDS Members Create for BY Variable

Reeza — Tue, 25 Nov 2014 07:19:56 GMT

What is different "PDS members"?

Are you trying to create separate data sets based on the variable GLIBSEQN? If so, why? SAS group by processing is quite effective.

Regardless, if you need that, see

Split Data into Subsets - sasCommunity

The end of that page at the bottom has some links to other such solutions, or searching this site with "split data into subsets" shows a bunch of different ways as well.

Re: PDS Members Create for BY Variable

rkumar23 — Wed, 26 Nov 2014 06:06:36 GMT

I mean from Different PDS members is to have unique Member created in the PDS(Partition dataset) for each by Variable so ..this is what my program is now...

DATA LAB1;

INFILE DATALINES ;

INPUT DATE DATE9. TIME $ GLIBSEQN $ CLUSTER $ DLIB $

DISTNAME $ DEFERR $ THRESHOLD $ ;

DATALINES;

01OCT14 0:00 10000 04 10015 RVDRVA15 0:00 1:00

01OCT14 0:00 10000 02 10018 KCDRVA18 0:02 1:00

01OCT14 0:00 10000 05 10016 KCDRVA16 0:01 1:00

01OCT14 0:00 10000 00 10017 RVDRVA17 0:00 1:00

01OCT14 0:00 20000 03 1001A KCDRVA1A 0:02 1:00

01OCT14 0:30 20000 02 10018 KCDRVA18 0:02 1:00

01OCT14 0:30 20000 05 10016 KCDRVA16 0:01 1:00

01OCT14 0:30 20000 00 10017 RVDRVA17 0:00 1:00

;

DATA TEST(INDEX=(GLIBSEQN));SET LAB1;RUN;

DATA KEEPTEST;

declare hash EDIT;

EDIT = _new_ hash(ordered: 'ascending');

EDIT.definekey('_unique_key');

EDIT.definedata('DATE', 'TIME', 'GLIBSEQN','CLUSTER','DISTNAME');

EDIT.definedone();

do until(last.glibseqn);set test;by glibseqn;_unique_key+1;

EDIT.ADD();

END;

EDIT.OUTPUT(DATASET:'C'||GLIBSEQN);

Above program is creating TWO output dataset ....I may be lost with options now but Do you have thought how could i write these to the physical dataset example we will have KEEPTEST.C10000 and KEEPTEST.C20000 these need to be in the FILE C1000 ...

Re: PDS Members Create for BY Variable

Reeza — Wed, 26 Nov 2014 12:22:48 GMT

There's a hash example in the link above.

Assuming the data is sorted, I usually use a data step with call execute instead:

proc sort data=sashelp.class out=class; by sex; run;

data _null_;

set class;

by sex;

if first.sex then do;

call execute("Data Sex_"||sex||"; Set class;"||

"Where Sex="||quote(sex)||";run;");

end;

run;

Re: PDS Members Create for BY Variable

Ksharp — Wed, 26 Nov 2014 14:25:32 GMT

Assuming the data is sorted.

DATA LAB1;                                                      
INFILE DATALINES ;                                              
INPUT DATE : DATE9. TIME $ GLIBSEQN $ CLUSTER $ DLIB $             
     DISTNAME $ DEFERR $ THRESHOLD $ ;   
format DATE  DATE9.; 
DATALINES;                                                       
01OCT14  0:00 10000  04  10015  RVDRVA15      0:00     1:00      
01OCT14  0:00 10000  02  10018  KCDRVA18      0:02     1:00      
01OCT14  0:00 10000  05  10016  KCDRVA16      0:01     1:00      
01OCT14  0:00 10000  00  10017  RVDRVA17      0:00     1:00      
01OCT14  0:00 20000  03  1001A  KCDRVA1A      0:02     1:00      
01OCT14  0:30 20000  02  10018  KCDRVA18      0:02     1:00      
01OCT14  0:30 20000  05  10016  KCDRVA16      0:01     1:00      
01OCT14  0:30 20000  00  10017  RVDRVA17      0:00     1:00      
;               
run; 
data _null_;
 if _n_ eq 1 then do;
 if 0 then set LAB1;
  declare hash h(multidata:'y');
  h.definekey('GLIBSEQN');
  h.definedata('DATE','TIME','GLIBSEQN','CLUSTER','DLIB','DISTNAME','DEFERR','THRESHOLD');
  h.definedone();
 end;
set LAB1;
by GLIBSEQN;
h.add();
if last.GLIBSEQN then do;h.output(dataset:cats('C',GLIBSEQN));h.clear();end;
run;

Xia Keshan

Re: PDS Members Create for BY Variable

rkumar23 — Thu, 27 Nov 2014 02:04:57 GMT

Yes that's what I been able to create output dataset however objective is with these output datasets PDS member name is needed to be created dynamically like from above we will have C10000 & C20000 ...Now These should be created as members and then corresponding Observation need to be copied to these members ....So basically

PDS = xxxxxx should have C10000 and C20000 members created and WORK.C10000 & WORK.C20000 Observations be copied over to these coresponding members...Again can not hard code them as above is just an example I can have it changing everytime ....

Thanks for your help in advance...

Re: PDS Members Create for BY Variable

Reeza — Thu, 27 Nov 2014 02:36:28 GMT

code creates the work.c10000 and work.c20000 files.

I'm lost as to what you mean by PDS = xxxxxx .

Does SAS support PDS, I see SPD but that doesn't seem to be what you're referring to.

Re: PDS Members Create for BY Variable

rkumar23 — Thu, 27 Nov 2014 02:38:33 GMT

Yes PDS is Partition datasets .....it's Mainframe files....and easily understood if mainframe personnel

Re: PDS Members Create for BY Variable

Reeza — Thu, 27 Nov 2014 02:41:05 GMT

So once you have the work files what's the next step, uploading them to a mainframe?

Re: PDS Members Create for BY Variable

rkumar23 — Thu, 27 Nov 2014 02:43:54 GMT

This whole processing is on the Mainframe once work files are created I have to use name of the Work file as above example had C10000 and C20000 ....Need to create Members in the Partition dataset(PDS) using these names and then corresponding observation need to be copied from these Work files(i.e. work.c10000 & work.c20000) ...

Re: PDS Members Create for BY Variable

Reeza — Thu, 27 Nov 2014 02:47:23 GMT

I don't understand, but I don't work on mainframes

Perhaps consider itemizing your to do list. I'm sure the code xia has presented and mine accomplish a portion of what you need. I'm still uncertain as to what the remaining part is. You can copy files over using proc copy or proc datasets.

Re: PDS Members Create for BY Variable

Tom — Thu, 27 Nov 2014 02:51:49 GMT

First let's assume that by PDS member you are using IBM mainframe terminology for text files and and not SAS datasets.

You can use the FILEVAR option to dynamically generate the DSN. So to write to TOP.LEVEL.C100000 and TOP.LEVEL.C20000 etc. your program would look something like this.

data _null_;

set lab1 ;

length filename $200 ;

filename = catx('.','TOP.LEVEL',cats('C',GLIBSEQN)) ;

file dummy filevar=filename ;

put .... ;

run;

But I am not sure if you can do that for PDS members. You could try it by generating values for FILENAME that look like TOP.LEVEL.PDS(G10000) instead.

Re: PDS Members Create for BY Variable

jakarman — Thu, 27 Nov 2014 15:52:35 GMT

I hope you are not using the PDS structure but the PDSE one. The difference between those two is that the first one is suffering from need to be compressed regular and the last one not.

Sometimes the PDSE structure is indicated in TSO (allocating the space) as "library". Nice word good for the unwanted confusion.

Within in a mainframe environment you should not use the Filenames & libnames in your code. That habit is just bad practice and you will need to solve that when there is an develop / test / acceptance / production release management approach for you code. A DD statement in the JCL will be the requirement. That is your fileref/libref.

Do you have a limited number predefined naming (split in 5-10) you can code:

...

file <filref>(membr1) ;

...

file <filref>(membr2) ;

...

This approach can be followed on all type of machines (Unix/Windows/Mainframe).

The doc can be found at: http://support.sas.com/documentation/cdl/en/hosto390/67326/HTML/default/viewer.htm#n0rog60ordqc10n1isp7c61frxj0.htm

this example I referred to:

This next example assigns the fileref MYPDSE to the PDSE and then uses the fileref in a simple DATA step:

/* PDSE Example */

filename mypdse 'sales.div1.reg3' disp=shr;

data a;

x=1;

file mypdse(june97);

put x;

file mypdse(jul97);

put x;

run;

Still needing the full path in your program the you can retrieve that with:

%let fullname = %sysfunc(pathname(<fileref>)) ;

Re: PDS Members Create for BY Variable

rkumar23 — Fri, 28 Nov 2014 08:05:27 GMT

Yes...Absolutely PDSE ...however unfortunately I don't have predefined members name so I have to first get the members name using either HASH object method as above or something similar and then create these members name in the PDSE followed by further copying the corresponding records in those PDSE members....

Re: PDS Members Create for BY Variable

jakarman — Fri, 28 Nov 2014 10:21:07 GMT

I have no Mainframe at my hands but I could try to write machine independend code putting it all together.

With the used parathesis the members in a PDSE should be created as long as the data is clustered (at notsorted at the by)

Putting the libname filenames in top is like having it in JCL. The adding of A is needed for naming conventions in the Z/OS member approach

42 ;

43 /* test in UE for PDSE */

44 libname test "/folders/myfolders/test";

NOTE: Libref TEST was successfully assigned as follows:

Engine: V9

Physical Name: /folders/myfolders/test

45 filename test "/folders/myfolders/test";

48 /* machine independent code create sas dataset */

49 DATA test.LAB1;

50 INFILE DATALINES ;

51 INPUT

52 DAT DATE9. TIM TIME5. GLIBSEQN $ CLUSTER $ DLIB $ DISTNAME $ Deferr $8.

53 threshold $8. ;

54 DATALINES;

NOTE: The data set TEST.LAB1 has 8 observations and 8 variables.

NOTE: DATA statement used (Total process time):

real time 0.03 seconds

cpu time 0.04 seconds

63 proc print data=test.lab1;run;

NOTE: There were 8 observations read from the data set TEST.LAB1.

NOTE: The PROCEDURE PRINT printed page 7.

NOTE: PROCEDURE PRINT used (Total process time):

real time 0.09 seconds

cpu time 0.10 seconds

65 DATA _null_ ;

66 Set test.LAB1;

67 by GLIBSEQN ;

68 length filevarpds $256 ;

69 retain filevarpds ;

70 if first.GLIBSEQN then do;

71 filevarpds="%sysfunc(pathname(test))"||"(A"||TRIM(GLIBSEQN)||")" ;

72 end;

73 file outpds filevar = filevarpds ;

74 put _all_ ;

76 run;

NOTE: The file OUTPDS is:

Filename=/folders/myfolders/test(A10000),

Owner Name=root,Group Name=root,

Access Permission=-rwxrwxrwx,

Last Modified=28 november 2014 05:27:08 uur

NOTE: The file OUTPDS is:

Filename=/folders/myfolders/test(A20000),

Owner Name=root,Group Name=root,

Access Permission=-rwxrwxrwx,

Last Modified=28 november 2014 05:27:08 uur

NOTE: 4 records were written to the file OUTPDS.

The minimum record length was 192.

The maximum record length was 192.

NOTE: 4 records were written to the file OUTPDS.

The minimum record length was 192.

The maximum record length was 195.

NOTE: There were 8 observations read from the data set TEST.LAB1.

NOTE: DATA statement used (Total process time):

real time 0.02 seconds

cpu time 0.04 seconds

78 /* http://support.sas.com/documentation/cdl/en/hosto390/67326/HTML/default/viewer.htm#p0agwv4mwi9x6xn17mkwr63wdo0x.htm */

79 /* http://support.sas.com/documentation/cdl/en/hosto390/67326/HTML/default/viewer.htm#n0e5aa1mquetdin1m9b9lifcdma8.htm */

Re: PDS Members Create for BY Variable

Patrick — Sat, 29 Nov 2014 23:22:55 GMT

It's now quite long ago that I've worked with SAS under z/OS but "in my times" you would have stored SAS tables using VSAM and not PDSE.

PDSE would have been used for textual data like SAS code.

Once the VSAM file is allocated (via JCL or a libname statement) you can use it and create/read/update/delete SAS tables as you would do it under any other OS by using normal SAS syntax.

SAS(R) 9.4 Companion for z/OS, Third Edition

So with z/OS it's always the same story: You need to create the external file in the right structure. Once this is done you can use it like you would use a directory in another OS (VSAM file for LIBNAME, PDSE for FILENAME).

I've seen that under SAS 9.4 option "dlcreatedir" also exists for z/OS. Not sure though if this only applies for HFS and if not where SAS would pick up the defaults for defining the file organisation.

Re: PDS Members Create for BY Variable

jakarman — Sun, 30 Nov 2014 08:09:13 GMT

Patrick, The DLCREATEDIR is only for UFS. SAS(R) 9.4 Companion for z/OS, Third Edition that is the HFS type (unix) or Posix based.

Today most of the initital sas process are Posix. When installing on z/OS you must be prepared for that. The old MVS is named boundary-files. The SAS/connect when used is starting a sh-script (unix) and found back by a BPXAS address space when using SDSF RMF or an other monitoring tool.

With SAS V5 the access method was of the BDAM unmovable type. It changed to QSAM (FS/PS) on a low level access method with EXecute Channel Program (excp access). That are the notes in a mainframe SAS log referring to still being there. VSAM (IDCAMS) has never been used for SAS libraries. SAS is very handy to access VSAM data very underestimated as valuable.

With SAS libraries on z/OS I woul prefer half track size blocks (27998) on a 3390 (model-9 type) minimizing IO for big data processing. The default is (was) 6Kb. A topic for a lot of hot discussions.

Another is the use of cardimage/nocardimage (Hollerith 80 colomn) of the sources datasets. Just recently all input datasets are now mandatory for VBS (autoexec config installation) with a goal of lrecl=255..

If you have a hard-copy of the SAS v6 companion, there is on page 44 described the multivolume approach. That one was implemented wrong by SAS, causing a lot of trouble for that bit in a QSAM file indicating continuation on the next volume (SMS HSM implementation). The correction was made in V8 (2004 migration because of milo-euro) leaving the issue to exist for 6-8 years.

Re: PDS Members Create for BY Variable

rkumar23 — Mon, 01 Dec 2014 05:21:30 GMT

Thanks Japp Karman, your idea/code helped to get it working....