10-05-2016
Paul_NYS
Obsidian | Level 7
Member since
09-07-2012
- 216 Posts
- 0 Likes Given
- 0 Solutions
- 3 Likes Received
-
Latest posts by Paul_NYS
Subject Views Posted 3452 10-05-2016 01:16 PM 3457 10-05-2016 01:08 PM 2634 06-14-2016 03:50 PM 1576 06-14-2016 02:39 PM 2646 06-14-2016 02:35 PM 1627 06-08-2016 03:28 PM 1633 06-08-2016 03:16 PM 1266 03-22-2016 05:05 PM 1285 03-22-2016 04:10 PM 1956 02-02-2016 01:00 PM -
Activity Feed for Paul_NYS
- Got a Like for "NOTE 49-169: The meaning of an identifier after a quoted string....." error. 06-24-2019 06:50 PM
- Got a Like for "NOTE 49-169: The meaning of an identifier after a quoted string....." error. 02-26-2018 08:02 AM
- Got a Like for Exporting a SAS data set in SAS format. 03-21-2017 09:23 AM
- Posted Re: ERROR: Windows error code: 1117 in hc_disk_normal_read for....... error on SAS Procedures. 10-05-2016 01:16 PM
- Posted ERROR: Windows error code: 1117 in hc_disk_normal_read for....... error on SAS Procedures. 10-05-2016 01:08 PM
- Posted Re: MEMSIZE and FULLSTIMER options for memory issues on SAS Programming. 06-14-2016 03:50 PM
- Posted Re: Create a data set by grabbing the first <insert number> records from a larger one on SAS Programming. 06-14-2016 02:39 PM
- Posted MEMSIZE and FULLSTIMER options for memory issues on SAS Programming. 06-14-2016 02:35 PM
- Posted Re: Create a data set by grabbing the first <insert number> records from a larger one on SAS Programming. 06-08-2016 03:28 PM
- Posted Create a data set by grabbing the first <insert number> records from a larger one on SAS Programming. 06-08-2016 03:16 PM
- Posted Re: Merging two data sets and ensuring additional records are not created. on SAS Procedures. 03-22-2016 05:05 PM
- Posted Merging two data sets and ensuring additional records are not created. on SAS Procedures. 03-22-2016 04:10 PM
- Posted Re: Collapse multiple records into one and combine column values on SAS Procedures. 02-02-2016 01:00 PM
- Posted Collapse multiple records into one and combine column values on SAS Procedures. 02-02-2016 12:36 PM
- Posted Re: Proc export and 32 vs 64 bit PCs on SAS Procedures. 08-20-2015 10:51 AM
- Posted Re: Proc export and 32 vs 64 bit PCs on SAS Procedures. 08-20-2015 10:49 AM
- Posted Re: Proc export and 32 vs 64 bit PCs on SAS Procedures. 08-19-2015 04:12 PM
- Posted Proc export and 32 vs 64 bit PCs on SAS Procedures. 08-19-2015 02:26 PM
- Posted Re: Merging two data sets without adding records on SAS Programming. 06-15-2015 04:46 PM
- Posted Merging two data sets without adding records on SAS Programming. 06-15-2015 04:17 PM
-
My Liked Posts
Subject Likes Posted 2 08-25-2013 11:39 AM 1 02-03-2014 06:59 PM
10-05-2016
01:16 PM
That is a good thought about the hard drive--I will try that. I thought about running it from the network drive here, but that slows things down dramatically, but the hard drive may not. Paul
... View more
10-05-2016
01:08 PM
Hi Everyone I am running desktop SAS 9.4, EG 7.11 on a Windows 10 laptop with 12 GB memory and plugged into a USB 3.0 64 GB flashdrive (currently 30 GB free). I have used the flashdrive for some time now, but Win 10 is new along with an increase in memory from 4 to 12 GB. I keep getting the below error for I/O error in the below data step. This flashdrive has been great in the past, so it shouldn't be an issue. Any ideas? Also, I use the same flashdrive with the same laptop for other programs yesterday and it was fine. This error happens periodically. Paul data vg2q2016b (rename=entity_idall=entity_id) ; set vg.vg2q2016b; drop gdocket gdocket entity_id1 entity_id2 entity_id3 entity_id4; run; ERROR: Windows error code: 1117 in hc_disk_normal_read for E:\files\VGExtract\vg2q2016b.sas7bdat, The request could not be performed because of an I/O device error. ERROR: File VG.VG2Q2016B.DATA is damaged. I/O processing did not complete.
... View more
06-14-2016
03:50 PM
I am using a Windows 7 desktop. Where is the configuration file located? Paul
... View more
06-14-2016
02:39 PM
Yes Astounding, I actually tried this method after and it works fine as well. Going forward, this is probably what I would use. Paul
... View more
06-14-2016
02:35 PM
Hi Everyone I keep getting the below error for memory size. After taking a look around, it seems using memsize and fullstimer options might be a good way to resolve the error, once it is determined the memory needed. However, I don't see how to implement these options. It appears you can set it in a data step or proc, but don't see examples. Is anyone familiar with this? Paul "ERROR: Unable to allocate sufficient memory. At least 1521783K bytes were requested, but only 786430K were available. You must either increase the amount of memory available, or approach the problem differently. ERROR: The SAS System stopped processing this step because of insufficient memory."
... View more
06-08-2016
03:28 PM
Thanks PG. That works! Paul
... View more
06-08-2016
03:16 PM
Hi Everyone I have a data set with about 100,000 records in it. I would like to create a smaller data set from that one that is composed of the first 50,000 records. I know I can add a sequential counter column to it and then do it that way, but I was wondering if there is a way to do this by just selecting the first 50,000 records of the larger one on the fly? Paul
... View more
03-22-2016
05:05 PM
I thought there were a lot of duplicates actually. But if this is the only scenario that would produce more than one record from the original data set, then I will take a look at the file tomorrow morning and check it further. If that is the case then that is an easier scenario than I thought. I will get back. Thanks Astounding. Paul
... View more
03-22-2016
04:10 PM
Hi Everyone I am merging two data sets with the below statement and when I do a few extra records are being created in the new data set. Is there any way I can either prevent this or identify the additional records in the new data set? In the s0ssrp data set, there are 514,983. In the new s0ssrp1, there are 515,013. Paul data s0ssrp1 (rename=closed_reason=FtcOutcome); merge s0ssrp (in=a) ssrpucms2 (keep=County Docket ReferralDate FtcStatus closed_reason ContractDate); if a; by County Docket; if ReferralDate ge start and ReferralDate le stop then do; FtcReferred="Y"; end; else FtcReferred="N"; run;
... View more
02-02-2016
01:00 PM
Thanks a lot Freelance! That did it. I have not used Proc Summary before. What do the below aspects of it do? (drop=_:) max= Paul
... View more
02-02-2016
12:36 PM
Hi Everyone I would like to collapse the below records (screenshot) that have the same entity_id into one record and keep all the column values, where one is populated. Is there a fairly straight forward way of doing this? Paul
... View more
08-20-2015
10:51 AM
I don't use an export wizard for exporting. I just execute the above statement in Enterprise Guide just as plain SAS code. I don't use any of the GUI in EG for running processes at all. Paul
... View more
08-20-2015
10:49 AM
I have SAS/Access installed and it worked fine before. So that should not be an issue. Paul
... View more
08-19-2015
04:12 PM
This article seems like it is directed toward 64 bit PCs. My issue is now with the 32 bit PC though. Paul
... View more
08-19-2015
02:26 PM
Hi I have two PCs with SAS on them. One with 32 bit and one with 64 bit. I have code that has worked fine for a long time with 32 bit. I updated a program with the 64 bit PC that was originally written with the 32 bit. In running it now on the 32 bit, it now is having a problem with the last proc export statement below. This worked fine in 32 bit prior. I also included the error, which has nothing to do with the lib ref statements. They are fine. The Access DB is 32 bit. Any ideas? Paul Statement: PROC EXPORT DATA=s1PermComb OUTTABLE="metric1btest" DBMS=ACCESS REPLACE; DATABASE="R:\CIP\Projects - Data\Court CW Data Metrics Project\SharePoint Prototype Files\accessTest.accdb"; RUN; Error: ERROR: Connect: Class not registered ERROR: Error in the LIBNAME statement.
... View more