You can also store SAS code in a SAS catalog SOURCE entry and password-protect it there. A simple %INCLUDE statement can be used read the code from the catalog and submit it. ... View more

It would be helpful if you could provide your SCL code so we can see what you are trying to do. ... View more

A strong possibility is that you have run out of WORK space. Check the WORK folder to see if it is running low on space. ... View more

Also no context to this problem has been supplied, for example what is this 16-digit number used for? Also is it a whole number or are there decimals? This information is useful to providing the best advice. For example, in banking most credit card numbers are 16 digits long (4 groups of 4 digits), but are held as character data to avoid any precision or formatting issues. ... View more

Suggest you search SAS support before posting queries of this type as you can get answers a lot quicker. Please refer to this SAS note: http://support.sas.com/kb/18/350.html ... View more

How about exporting the code of a sample EG process which you have already benchmarked in EG, then run the exported code in base SAS? If it performs the same as in EG, then it is not the EG environment that is the issue but the code itself. A comparison of techniques with your different base SAS code may provide the answers. ... View more

Your macro executes an operating system DIR command to get a list of files. By default this ability to execute an operating system command is turned off in EG. A change to your SAS server options would be required, for example I suspect XCMD = OFF. ... View more

Thanks for pointing out the NEXTRVAL=n option. It will still be slower to run than the ARRAY technique, but a whole lot quicker to write in the first place. My view of efficiency involves both code development and run times. This UNIVARIATE technique is an example of coding effiiciency being more important than run-time efficiency. ... View more

Have you tried PROC MIGRATE? The doc says you can use it from 9.2 only. If this fails then the CPORT/CIMPORT option you describe is probably the only option. Good luck! ... View more

Are you using the 32-bit or 64-bit version of Windows 7? If your problem is converting a 32-bit SAS catalog to a 64-bit version then the MIGRATE procedure would be worth checking out. This will only be of use if you are using SAS 6.2. Message was edited by: SASKiwi ... View more

If you are running SAS under Windows then the Control Panel contains a simple scheduler that will do what you want. Other operating systems have similar tools. ... View more

Here is another way of doing this: ods output ExtremeValues = extreme; proc univariate data = sashelp.class; var age; run; ods output close; The ODS statement creates a dataset EXTREME with the top and bottom 5 values. If you have more than one variable just list them in the VAR statement. Message was edited by: SASKiwi ... View more

Curious to know why you are using DDE as compared to say PROC IMPORT where dates are handled automatically. ... View more

I suggest you repeat your test, but don't zip/unzip the file. If this works then it is the zip/unzip causing the problem. If it doesn't work then you can conclude that your transport file is not correct. BTW a transport file on MVS has to have certain file characteristics (eg RECFM = F, LRECL = 80, BLKSIZE = ??). Check the documentation as I am quoting this from memory. It is my understanding that a transport file is always created in ASCII regardless of the platform it is created on, hence the need for the binary transfer. ... View more

It's not clear from your explanation if you are defining a macro variable on your PC and want it to resolve on the mainframe or vice versa. If it is the first case then you need to use %SYSRPUT on your PC (having already signed on to your mainframe SAS session): %let local_var = example; %SYSRPUT remote_var = &local_var / remote = sessionid; The macro variable remote_var should then resolve in your mainframe session. ... View more