Troubleshooting SAS® DS2 Activity Code for SAS® Real-Time Decision Manager (SAS® Decision Services)


SAS Decision Services enables you to create and use SAS DS2 packages that are compiled and run by the DataFlux® Federation Server. This functionality uses the DataFlux Federation Server internal copy of the SAS DS2 compiler and engine. The DataFlux Federation Server internal version of SAS DS2 might be slightly older than the Base SAS® internal version of SAS DS2. This version difference sometimes causes confusion when you are troubleshooting if the problem that you encounter is specific to a particular version of SAS DS2.

There are two slightly different versions of the connection arguments to PROC DS2 that you can use in order to choose which SAS DS2 compiler you use.

Running the following SAS DS2 code causes the code to be compiled in Base SAS but to run on the DataFlux Federation Server:

proc ds2 nolibs conn="driver=remts;server=your-federation-server;port=21032; protocol=bridge;uid=fedadmin;pwd=XXXXXXXX;conopts=(DSN=BASE_dsn)"; package test_ext /extension='hash' overwrite=yes; endpackage; run; quit;

 

Running the following SAS DS2 code causes the code to be compiled and run in the DataFlux Federation Server version of SAS DS2:

proc ds2 nolibs NOPROMPT="driver=remts;server=your-federation-server;port=21032; protocol=bridge;uid=fedadmin;pwd=XXXXXXXX;conopts=(driver=ds2;conopts=(DSN=BASE_DSN))"; package tap_hash /extension='hash' overwrite=yes; endpackage; run; quit;

 

Use the second method above when you test SAS DS2 code for use in SAS Real-Time Decision Manager (SAS Decision Services) Activities.