{"id":213,"date":"2014-03-18T20:06:43","date_gmt":"2014-03-18T20:06:43","guid":{"rendered":"http:\/\/www.sebcharrot.com\/blog\/?p=213"},"modified":"2014-03-18T20:06:43","modified_gmt":"2014-03-18T20:06:43","slug":"sas-how-to-exportimport-packages","status":"publish","type":"post","link":"http:\/\/www.sebcharrot.com\/blog\/sas-how-to-exportimport-packages\/","title":{"rendered":"SAS – How to Export\/Import packages"},"content":{"rendered":"
\"\"<\/a>

It’s also possible to import\/export metadata with the Wizard equivalent<\/p><\/div>\n

My team and I have been developing a solution which involves a degree of SAS reports and related metadata. I set up a scheduled, automated backup of our information maps, reports, etc for posterity, and out of general paranoia. For this I used SAS’s command line export and import capabiltiies, which probably weren’t designed to be used that way, but which turned out to be really useful.<\/p>\n

It took a wee bit of trial and error, so I thought I’d document it here.<\/p>\n

(Handy reference link<\/a>)<\/p>\n

Note: If you’re puttying into your SAS server, make sure that your putty session has “Enable X11” ticked.<\/em><\/p>\n

\u00a0Export<\/h1>\n

(Ignore any new lines in the text below – I’ve added those for readability)<\/p>\n

\n

\/usr\/local\/SASHome\/SASPlatformObjectFramework\/9.3\/ExportPackage -host “mysasmachine” -port 8561 -user myuser@saspw -password mypassword -package “myPackage.spk” -objects “\/Shared Data\/mySourceFolder(Folder)” -includeDep -subprop<\/p>\n<\/blockquote>\n