Once again, you prove yourself a pro.... Works perfectly. I ran across another posting where you had the (_all_) statement in it, but I didn't realize what exactly the ~ character was accomplishing. Now I know! Regards, G.I. Jeff ... View more

Sorry, no. I need to double quote specific numeric fields before I plug them into a csv file. It won't be all the fields. Example: SMF30ZIP,20110620,3,Acct_Code,"997KCE999999",Acct_Code2,"KCUN",Acct_Code3,"3",Shift,"1",JESNR,"JOB07760",,,,,, ... View more

data _null_; In my case, I am testing for the file to exist before I set the INFILE filename. I think I understand what you are suggesting but I don't see how it will work in my case. I also think I understand how the FILEVAR is used. I didn't realize you could assign more than one filename to the variable, but again, in my case I don't think this will work. I would rather complete this task in one DATA step if I can honestly. Or maybe I don't understand (highly possible).... Jeff ... View more

Ok guys, new question, same subject: I have my code in place and working, ready to implement into a daily batch job. Again, thank you for all your help in the matter. My new questions is, is there an easy way to code the following DATA step into a macro so that I don't have to repeat it for every file I need to input into a pdb? DATA VMDATA.DAILY_SYSE_GUESTS; LENGTH FILENAME $256; FILENAME = CATS('SYS90H.SYSE.USERLOG.D',PUT(TODAY()-1,YYMMDDN6.)); LNXDATE=TODAY()-1; SYSTEM='SYSE'; IF FILEEXIST(FILENAME) THEN DO; INFILE DUMMY END=EOF FILEVAR=FILENAME MISSOVER; DO WHILE(NOT EOF); INPUT @1 RECTYPE $1. @2 LNXUSER $8. @13 LNXTIME TIME. @25 CPU 4.0 @31 TOTCPUT 5.0 @37 VRTCPUT 5.0 @45 CPURATIO 3.0 @51 VRTIO 4.0 @57 TOTIO 4.0 @82 PAGESEC 4.0 @138 WEIGHT 3.0 @144 VCPUS 1.0; IF RECTYPE NE 'U' THEN CONTINUE; OUTPUT; END; END; ELSE DO; ABORT RETURN 4; END; STOP; RUN; The only things I change in the code are the FILENAME & SYSTEM variables. Those I can figure out how to code simple macro variables for. My real question is the DATA step name. I create a pdb for every file I need to read and then APPEND them all to one pdb at the end of the job. If there is an easier or better way of doing this, I'm all ears!! Again, I will reiterate to you all, I am SAS stupid and have just taken the beginners course. I do not have enough time under my belt with SAS to do what I want with it. Thanks for your time and participation. Jeff ... View more

data _null_; Thanks again. You are right, it was the DELETE statement. Although I can't understand why they would architect that command to restart a DATA step?!? I also need to read up on the STOP command because I don't fully understand it's function while in a DO loop. Also, the first dilemma I presented in this thread (File SYS90H.LNXMEM.D*) was a single job. The job I'm working on now has 6 files I need to read and APPEND into a daily PDB. So, for now, to automate my job (which is my immediate goal) this code will allow this task. In the very near future I probably will need to learn and write a macro to run through all 6 files more efficiently than creating 6 different DATA steps with 6 different APPEND steps. All of the Sas steps will be added to a daily batch job that I ultimately didn't want failing if any/all of these files were missing. If they are, I set an appropriate return code and add a condition check at the end to e-mail me the missing file names. This keeps me from getting woke up at 2 am. Peter.C Thanks for the suggestions and I will use them. I agree with your code, much more efficient and will make it easier to read. Although I will have to revisit your second suggestion soon. I had quite a difficult time getting Sas to recognize the numbers correctly (and I still have some jobs I'm still scratching my head on). Most of the data that I'm working with right now comes from z/VM partitions, straight out of IBM's Performance Toolkit. The data looks very straight forward but when I import it into pdb's, Sas keeps translating the numbers into different formats. There have been many nights I've had to stop by the liquor store on the way home after dealing with these jobs. My main problem is that I am the only active "coder" in the entire building and the ONLY SAS user. So I have no one to bounce my ideas or problems off of. Google only gets me so far. You guys have helped me out IMMENSELY. Thank you!! ... View more

I used to be in the Navy, 90-94. Got out, went to college, got my tech degree, thought it would be fun to be a programmer, went to work for Hallmark Cards, left to go to Yellow Freight trucking company and recently just aquired a job with the federal government working for the USDA. I actually was programming before I joined the Navy and came back to it. I love it. I'm a mainframer for life, one of the youngest in Kansas City. Got a new dillema with your suggested code: I tried it with a different file, non-comma seperated file, and now the same code seems to be looping. OPTIONS NOERRABEND; DATA LNX_USERS; LENGTH FILENAME $256; FILENAME = CATS('SYS90H.SYSE.USERLOG.D',PUT(TODAY()-1,YYMMDDN6.)); IF FILEEXIST(FILENAME) THEN DO; INFILE DUMMY END=EOF FILEVAR=FILENAME MISSOVER; DO WHILE(NOT EOF); INPUT @1 RECTYPE $1. @2 LNXUSER $8. @13 LNXTIME TIME. @25 CPU 4.0 @31 TOTCPUT 5.0 @37 VRTCPUT 5.0 @45 CPURATIO 3.0 @51 VRTIO 4.0 @57 TOTIO 4.0 @82 PAGESEC 4.0 @138 WEIGHT 3.0 @144 VCPUS 1.0; IF RECTYPE NE 'U' THEN DELETE; LNXDATE=TODAY()-1; SYSTEM='SYSE'; OUTPUT; END; END; ELSE DO; ABORT RETURN 4; END; STOP; RUN; I removed the delimiter, dsd and firstobs options from the INFILE statement and added the MISSOVER (after several attempt thinking it might be missing values) and it still doesn't end. This new file has 143k rows but if I feed it the old way I used to, it only took less than a minute to run. It's almost like it's not reaching the END=EOF condition. Is there something that I can write to the SASLOG that will tell me if it's stuck processing the same record or looping through the entire file? Could it be the FILEVAR statement? I've read up on it and it sounds like a placeholder variable for reading multiple files (which is what I want to do with this job, but just trying 1 file for now) but doesn't really sound like a culprit. Jeff ... View more

Thanks for your suggestion. Wasn't making a contest, just trying to be funny. ... View more

Thanks everyone for their input! I truly appreciate your help and will always come back here when I'm frantically banging my head against my desk. Some of you put more advanced stuff here than I'm willing to try AT THIS POINT. I will definitely play around with it in the future and again, thanks for posting it. But the winner in this post is......... DATA _NULL_; !!!!! I achieved my desired results with their code and a very slight modification: OPTIONS NOERRABEND; DATA _NULL_; DTRUN=TODAY()+1; DTRUN1=(PUT(DTRUN,YYMMDD6.)); CALL SYMPUT('DYYMMDD',DTRUN1); STOP; RUN; DATA LNX_USERS; LENGTH FILENAME $256; FILENAME = "SYS90H.LNXMEM.D&DYYMMDD"; IF FILEEXIST(FILENAME) THEN DO; INFILE DUMMY DELIMITER=',' DSD FIRSTOBS=2 END=EOF FILEVAR=FILENAME; DO WHILE(NOT EOF); INPUT GUEST :$8. DATETIME :$15. TOTMEM :8. KBMEMFR :8. KBMEMUS :8. PCTMEMUS :5.2 KBBUFFRS :8. KBCACHED :8. KBSWPFR :8. KBSWPUS :8. PCTSWPUS :5.2 KBSWPCAD :8.; LNXDATE = TODAY()-1; OUTPUT; END; END; ELSE DO; ABORT RETURN 4; END; STOP; RUN; Again, thanks everyone and I will keep in touch! G.I. Jeff ... View more

data _null_; That works, to a point. If the file doesn't exist, I need to set the return code to a specific value so I can flag it in the job stream. So would I just create an ELSE statement off the IF FILEEXIST, setting the return code to, say 4, by: IF FILEEXISTS(FILENAME) THEN DO; ... ... ... ELSE ABORT RETURN 4; I'll give it a try while your mulling that over! 🙂 ... View more

Hi OS2 Rules, I did that in my last run, after looking up the OPTIONS statement. It stopped abending but the job finished with a return code = 8. It looks as if it is ignoring my FILEEXIST condition statement completely. I even moved it up immediately after the FILENAME statement and no change. 1 2 THE SAS SYSTEM 2 OPTIONS NOERRABEND; 3 4 DATA _NULL_; 5 DTRUN=TODAY()-1; 6 DTRUN1=(PUT(DTRUN,YYMMDD6.)); 7 CALL SYMPUT('DYYMMDD',DTRUN1); 8 STOP; 9 RUN; NOTE: THE DATA STATEMENT USED THE FOLLOWING RESOURCES: CPU TIME - 00:00:00.00 ELAPSED TIME - 00:00:00.04 EXCP COUNT - 23 TASK MEMORY - 3222K (123K DATA, 3099K PROGRAM) TOTAL MEMORY - 16989K (6048K DATA, 10941K PROGRAM) NOTE: THE ADDRESS SPACE HAS USED A MAXIMUM OF 664K BELOW THE LINE AND 17508K ABO 9 ! 10 11 DATA LNX_USERS; 12 13 FILENAME LXGSTMEM "SYS90H.LNXMEM.D&DYYMMDD" DISP=SHR; ERROR: SVC99 ERROR RC=4, REASON=1708 : IKJ56228I DATA SET SYS90H.LNXMEM.D110109 ERROR: SVC99 ERROR RC=4, REASON=1708 : IKJ56228I DATA SET SYS90H.LNXMEM.D110109 ERROR: SVC99 ERROR RC=4, REASON=1708 : IKJ56228I DATA SET SYS90H.LNXMEM.D110109 ERROR: ERROR IN THE FILENAME STATEMENT. ERROR: ERROR IN THE FILENAME STATEMENT. ERROR: ERROR IN THE FILENAME STATEMENT. 13 ! 14 15 IF NOT FILEEXIST("SYS90H.LNXMEM.D&DYYMMDD") THEN ABORT RETURN 4; 16 17 INFILE LXGSTMEM DELIMITER=',' DSD FIRSTOBS=2; 18 19 INPUT GUEST :$8. 20 DATETIME :$15. 21 TOTMEM :8. 22 KBMEMFR :8. 23 KBMEMUS :8. 24 PCTMEMUS :5.2 25 KBBUFFRS :8. 26 KBCACHED :8. 27 KBSWPFR :8. 28 KBSWPUS :8. 29 PCTSWPUS :5.2 30 KBSWPCAD :8.; 31 32 LNXDATE = TODAY()-1; 33 ERROR: NO LOGICAL ASSIGN FOR FILENAME LXGSTMEM. ERROR: NO LOGICAL ASSIGN FOR FILENAME LXGSTMEM. ERROR: NO LOGICAL ASSIGN FOR FILENAME LXGSTMEM. NOTE: THE SAS SYSTEM STOPPED PROCESSING THIS STEP BECAUSE OF ERRORS. NOTE: SAS SET OPTION OBS=0 AND WILL CONTINUE TO CHECK STATEMENTS. THIS MAY CAUSE WARNING: THE DATA SET WORK.LNX_USERS MAY BE INCOMPLETE. WHEN THIS STEP WAS STOP NOTE: THE DATA STATEMENT USED THE FOLLOWING RESOURCES: CPU TIME - 00:00:00.02 ELAPSED TIME - 00:00:00.21 EXCP COUNT - 98 TASK MEMORY - 3806K (120K DATA, 3686K PROGRAM) TOTAL MEMORY - 17249K (6048K DATA, 11201K PROGRAM) NOTE: THE ADDRESS SPACE HAS USED A MAXIMUM OF 664K BELOW THE LINE AND 17772K ABO 3 THE SAS SYSTEM ERROR: ERRORS PRINTED ON PAGE 2. ERROR: ERRORS PRINTED ON PAGE 2. ERROR: ERRORS PRINTED ON PAGE 2. NOTE: THE SAS SESSION USED 2.32 CPU SECONDS AND 17249K. NOTE: THE ADDRESS SPACE HAS USED A MAXIMUM OF 664K BELOW THE LINE AND 17772K ABO NOTE: SAS INSTITUTE INC., SAS CAMPUS DRIVE, CARY, NC USA 27513-2414 ... View more