http://www.sas.com/en_us/offers/14q1/122603-sas-for-academia/overview.html   ... View more

There is somthing weird wiht the encoding. It looks the default settings are Unicode16 (Teradata) and a latin1 (your sas session) When getting Formats into TD  that was mentioned wiht 9.2 as a limitation at up no notes anymore about those anymore. Still strange that conversion there.   ... View more

https://support.sas.com/documentation/cdl/en/emag/67979/HTML/default/viewer.htm#n1ibc6lm34otr5n1qt8oxpez69e4.htm The client and office addon still there to install. There is a webrun start option as that one will use the java of the browser and not a JPRE is is not a good idea.  Java has a bad name with brosers usages as of security holes. ... View more

The macro as generated text code is not the issue it is  compilded than fiexed in size. The macro is generating soms SAS code and the problem is somwhere there.    It seems the clean-up on every turn is not done inside the looping of the loop there  but after that. Fix that .... For fixing the macro you will need to go to the owner of the macro. That is your local company. Maybe your are the owner yourself now. Get to the macro code and analyze that one instead of just using/calling it.    ... View more

oscarboots, You did not mention anything about your environment. Only desktopbased? (Admin access). Than you are probably on your own not getting any IT support. As you are wanting the LAN and other resources managed by the IT support you will have to go to them Server based? Than there must be a Server support group have support for the SAS metadata server and the server tools. The SAS metadata admin access is some job to define services like batch services and scheduling.    ... View more

The EG scheduler will use the WIndows scheduler. That one is unreliable you said. ... View more

What is te question?   The culture and technical conditions are a little bit different   Delivering data (as GDG's). - Mainframe SAS datasets (bound gdg) are containers wiht possible many SAS-datasets and catalogs   Unix/Windows are using a segregated datasets as the suffix "sas7*"     The directory is more like te mainframe bound library   - Mainframes are using an andvanced locking mechanisme not present at Windows Unix, it is just coming. The GDG usage is avoiding the locking questions by creating a new dataset where the old one can get deleted/uncataloged after some period of time.   The SAS GDS looks like a mainframe gdg but the difference: it is working on sas-datasets. The GDG creation part is normally done as delivering ODS (extracts of operational data) by the prodcutions support team.     At Windows/Unix SAS users are not commonly used to the regularities wiht scheduled processing deleivering an dwh. Insteda they are used to code the full physical datasetnames in ther programs (terrible bad coding practice). Do you want to Convert the processing you will need the change some cultural behaviors. - The Dwh processing should run scheduled on your Unix machines cerating those newly datasets (ODS)    The creation-of that code should be modified to use GDS in a SAS appraoch - The users should use those GDS with avoiding the lockings.    It is a more straight forward processing of working wiht extracts/ODS not possible with a RDBMS usage approach. As the common DWH theory is learned by means of Kimball Inmon Lindsted using a RDDMS as pre-req than yes, it is not a well known approach.           ... View more

Babloo, he must fundamental one. The admin con configure to store SP logging files content.  How the data for ARM can be stored directly to a tabel (exteren dbms / sas-share) is described in this nice blog post at: http://blogs.sas.com/content/sgf/2015/09/30/part-1-auditing-data-access-who-did-what-and-when/ There is no need to develop something for functionality that can be configured. There is no need to use macro-processing only some fixed/moving values. The PID number is part of filename as setup in the mentioned config-files. As it is a randomnumber it shoudl be masked/wild-carded.      See:   %let filedate=%sysfunc(putn("&sysdate9"d-1,yymmdd10.)); %put &filedate; /* this date lay-out can be put in the source later */   data &data; set log.output_file; length fname $400; infile "/usr/sas/sas_config/Lev1/SASApp/StoredProcessServ?er/Logs/SASApp_STPServer_2015-10-04_*.log"   dsd truncover  END = end_of_file LRECL=32000 filename=fname ; input var : $ 3000.; var1 = _infile_; if var1 = :'201' then do; Date_TimeStamp= scan(var1,1," "); Status = scan(var1,2," "); Processid = scan(var1,3," "); userid = scan(var1,4," "); Details = scan(var1,-1,'-'); output; end;drop var var1; run;     It will read all log files on that fixed date putting that in a dataset witt the fname having the switch for all read physical files. Why overcomplicating that simple approach?    Reread the infile statement for the filename option. http://support.sas.com/documentation/cdl/en/lestmtsref/68024/HTML/default/viewer.htm#n1rill4udj0tfun1fvce3j401plo.htm   ... View more

Noticing your are trying to analyse a file that has been created from the ARM logging framework to create a table format. Did you realize the same logging framework can be configured to write all data in a RDBMS (SAS/Share) dataset?   ... View more