PROC HTTP does set some header item itself, and manually setting the same header attributes yourself I have seen lead to problems.  The documentation for the procedure that you have found online is as in-depth as I have seen available anywhere (which is not very detailed).  I do not recall exactly what headers I have seen cause issues, but I am pretty sure one of the was the content-type.  I have not tried it, but the documentation for PROC SOAP hints that there are some jreotions you can set to receive additional debug logging for the httpclient.  I would try setting that up for your session and see if it can be helpful at all with PROC HTTP. http://support.sas.com/documentation/cdl/en/proc/65145/HTML/default/viewer.htm#n1lvy6ht8ywii2n1jpwp3czll6no.htm the assumption is somewhat confirmed in the 9.4 documentation: http://support.sas.com/documentation/cdl/en/proc/67327/HTML/default/viewer.htm#n1hee3s3s3j9oxn1x6czzzdqsj4u.htm There is also an option in PROC HTTP called VERBOSE, which I do not recall being in the documentation syntax? I have scripts running frequently using a hmac-sha1 authentication schemes daily, through PROC HTTP, so I know at the very least, I know it's possible (even on some of the servers still running 9.2). ... View more

This is deliberate and a effect of the use of macro-quoting. %let m=%str(%')M%str(%'); proc sql; /* will not work */ select count(*) from sashelp.class where sex=&m.; /* will work */ select count(*) from sashelp.class where sex=%unquote(&m.); quit; ... View more

Yes, it is definitely full of quirks in 9.4M2, I for one and looking forward to seeing it improve. ... View more

Here is a quickly thrown together example for PROC LUA.  It is 'incomplete' so far as I do not take it any further than decoding the JSON file to a LUA table. filename foo temp; data _null_; file foo; put '{   "count":8141,   "calls":[     {"connectedTo":"01179817787",      "serviceName":"05 Direct",      "callGuid":"014cc38e-1ac5-44ee-8fdc-1176b9d83632",      "origin":"",      "stateChangedAt":"2015-04-17T00:19:25Z",      "sequence":5,      "appletName":"TM Out Of Hours",      "event":"End",      "state":"Caller",      "duration":"00:01:13"     },     {"connectedTo":"01179817787",      "serviceName":"05 Direct",      "callGuid":"014cc38e-1ac5-44ee-8fdc-1176b9d83632",      "origin":"",      "stateChangedAt":"2015-04-17T00:18:12Z",      "sequence":1,      "appletName":"AN Welcome Message",      "event":"NewApplet",      "state":"",      "ringDuration":"00:00:00",      "duration":"00:00:00",      "additionalParameters":        {"applet Type":"Announcement"        }     }]}'; run; proc fcmp outlib=work.func.luaio; /*sas.fget does not currently work.  the returned variable appears to always be nil*/ /*fileget in lua will circumvent this issue for now called as sas.fileget*/ function fileget(fid, len) $; length c $ 32767; rc = fget(fid, c, len); return (putc(c, cats('$',len,'.'))); endsub; run; options cmplib=work.func; filename LuaPath "%sysfunc(pathname(work,l))"; filename json "%sysfunc(pathname(LuaPath,f))/json.lua"; proc http method='get' url="https://raw.githubusercontent.com/FriedEgg/json4lua/master/json/json.lua" out=json; run; /*forked on Github of - (https://github.com/craigmj/json4lua), by Craig Mason-Jones to make LUA 5.2 compat.  Switch global loadstring to load.*/ proc lua infile="json"; submit; json = require('json') if sas.fileexist("foo") then    local fid = sas.fopen("foo", "s", 200, "B")    local s = "";    local c = "";    while sas.fread(fid) == 0 do       c = sas.fileget(fid, 200)    s = s .. c    end    rc = sas.fclose(fid)    decoded = json.decode(s)    for k in pairs(decoded["calls"][1]) do print(k) end else    print(sas.sysmsg()) end endsubmit; run; ... View more

Editorial Guidelines | SAS SAS Trademarks | SAS Most documentation and other published resources from SAS contain a bibliographic reference on the copyright page, for example, first line of page two in the document here: http://support.sas.com/documentation/cdl/en/acadbas/65468/PDF/default/acadbas.pdf ... View more

This is indeed true, however, by the OP's comment, he can execute PROC GROOVY, but believe he is unable to 'install' the necessary JAR files.  A JSON package for DS2 is very exciting and something I've been looking forward to since it was pre-production.  Wondering now how it will play with the HTTP package and streaming content.  Parsing a JSONstring would also be possible with PROC LUA (another very exciting new/shiny thing), but with no OS access from that procedure (at this time) you would not be able to read from a text file directly, however, with effort, you could go directly from JSON string to SAS Data file. ... View more

In newer versions of SAS the required jar files are typically included in the installation's versioned jar repository, but not necessarily used as the default.  For instance, I have a Windows installation 9.4TS1M2 and it uses groovy-all.jar of version ~1.7 that does not included the groovy.json package.  However, my installation has a package of groovy-all version ~2.1 which does include it.  I can then use this newer version by doing the following: proc groovy; add sasjar="groovy_2.1.3" version="2.1.3.0_SAS_20130517000930"; /*this exact version can different from product-to-product and by OS, etc...*/ submit; import groovy.json.JsonSlurper def slurper = new JsonSlurper() def result = slurper.parseText('{"person":{"name":"Guillaume", "age":33, "pets":["dog", "cat"]}}') assert result.person.name == "Guillaume" assert result.person.age == 33 assert result.person.pets.size() == 2 assert result.person.pets[0] == "dog" assert result.person.pets[1] == "cat" endsubmit; quit; So long as you have internet access you can also download any necessary JAR to the work directory for use in your process... ... View more

, I believe this function was added to SAS as a pre-production feature in 9.1.3 and then officially in 9.2 ... View more