About FriedEgg

FriedEgg · ‎02-27-2015

Cannot speak to the TOS, but it does seem that Avaya provides an ODBC driver to use for collecting data from the CMS system: https://downloads.avaya.com/elmodocs2/contact_center/r3v11/780701_1/780701_1.pdf

FriedEgg · ‎02-27-2015

You need to use the relative path.

FriedEgg · ‎02-26-2015

You have a serious problem with WETness. DRY your code. http://en.wikipedia.org/wiki/Don%27t_repeat_yourself

FriedEgg · ‎02-25-2015

Are you sure that you want the LIKE condition with the preceding %. Meaning that you are looking to select rows where the name contains the string AN or RE anywhere in the name, rather than just as a prefix, as your data suggests?

FriedEgg · ‎02-19-2015

Most of this information would only 'exist' as the result of running the project. After which you could collect the information using things like the dictionary tables. The egp file itself will contain some information you may be looking for, but also, this is pretty much only after a project is run. Depending on specifically what you want there are some caveats or other ways of going about collecting the information, but nothing probably as easy as you are hoping for.

FriedEgg · ‎02-17-2015

rsubmit

FriedEgg · ‎02-17-2015

@BillJones, Glad it work out for you.

FriedEgg · ‎02-17-2015

I have created a gist containing the various PROC GROOVY codes shared in this post. Using PROC GROOVY in SAS to Calculate Hash Digests

FriedEgg · ‎02-17-2015

If you are having issues with the commons-codec you can use the version that should be included in your sas versioned jar repository using a statement similar to the following: add sasjar="commons_codec" version="1.7.0.0_SAS_20121211183158"; The version will be specific to your installation.

FriedEgg · ‎02-17-2015

I did not test that posting and missed replacing the method call with the proper name. You should be good now.

FriedEgg · ‎02-17-2015

Consider whether you really need to split this dataset of if you are better off processing using BY or CLASS statements.

FriedEgg · ‎02-17-2015

If you are always performing this on dates, then you can use a custom picture format to display the dates the way you want. proc format; picture spaced_dt (default=11) other = '%0d %b %Y' (datatype=date) ; run; %let dt = 20oct1997; %put %sysfunc(putn("&dt."d, spaced_dt.));

FriedEgg · ‎02-17-2015

Here is an alternative to using regular expression. data foo; input Sl_No Security_No : $12.; do rept_int=0 to 9 while (_n_>0); if find(Security_No, repeat(put(rept_int,1.),5)) then do; _n_=0; output; end; end; cards; 1 111111111112 2 989898989898 3 111111111111 4 910000000000 5 999999999990 6 128390203040 7 127777777771 8 739349340595 9 634995038404 ; run;

FriedEgg · ‎02-17-2015

I would recommend you continue using the private Java runtime provided by your SAS installation. This is because they are looking for the base64 encoding of the byte array, you are creating the base64 encoding of the hexadecimal representation of the byte Hmac-SHA1 digest. %let key = kd94hf93k423kf44&pfkkdhi9sl3r4s00; %let message = GET&http%3A%2F%2Fphotos.example.net%2Fphotos&file%3Dvacation.jpg%26oauth_consumer_key%3Ddpf43f3p2l4k3l03%26oauth_nonce%3Dkllo9940pd9333jh%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp%3D1191242096%26oauth_token%3Dnnch734d00sl2jdk%26oauth_version%3D1.0%26size%3Doriginal; proc groovy; add sasjar="commons_codec" version="1.7.0.0_SAS_20121211183158";*version may differ based on your installation. Check your SAS Versioned Jar Repository; submit "&key." "&message."; import javax.crypto.Mac import javax.crypto.spec.SecretKeySpec import org.apache.commons.codec.binary.Base64 def base64hmacsha1(key, message) { mac = Mac.getInstance("HmacSHA1") mac.init(new SecretKeySpec(key.getBytes(), "HmacSHA1")) sha1_bytes = mac.doFinal(message.getBytes()) base64 = new Base64() return new String(base64.encode(sha1_bytes)) } exports.base64hmacsha1 = base64hmacsha1(args[0], args[1]) endsubmit; quit; %put &base64hmacsha1.; /*tR3+Ty81lMeYAr/Fid0kMTYa/WM=*/ Message was edited by: FriedEgg - typo corrected in RED, also added reference for common-codec sasjar

FriedEgg · ‎02-16-2015

%let key = mykey; %let message = helloworld; proc groovy; submit "&key." "&message."; import javax.crypto.Mac import javax.crypto.spec.SecretKeySpec def hmacsha1(key, message) { mac = Mac.getInstance("HmacSHA1") mac.init(new SecretKeySpec(key.getBytes(), "HmacSHA1")) sha1_bytes = mac.doFinal(message.getBytes()) return new BigInteger(1, sha1_bytes).toString(16) } exports.hmacsha1 = hmacsha1(args[0], args[1]) endsubmit; quit; %put &hmacsha1.;

Online Status	Offline
Date Last Visited	‎03-20-2026 07:25 PM