After executing the X statement, check the automatic macro variable &sysrc. It holds the return code of the external command. Your users woll have different environments, be it permissions or current working directories. Call python with the full absolute path. ... View more

As the SAS Documentation for the INPUT Statement says:   +n moves the pointer n columns.   Consequently, you take explicit control of the input pointer in your first data step and correctly jump over the spaces. In your second data step, the data step reads just a single character (as you instruct it to) regardless of whether it is a space or not.    Consequently, if your INPUT Statement in the second data step should produce the same output as the first one, your data should look like this (i don't recommend it, but I post it for clarification)   cdata voter2; input Age Party : $1. (Ques1-Ques4) ($1.); datalines; 23 D 1122 45 R 5541 67 D 2433 39 R 4444 19 D 2121 75 D 3323 57 R 4344 ; run;    Or you can simply add a colon to your input statement like this   data voter2; input Age Party : $1. (Ques1-Ques4) (:$1); datalines; 23 D 1 1 2 2 45 R 5 5 4 1 67 D 2 4 3 3 39 R 4 4 4 4 19 D 2 1 2 1 75 D 3 3 2 3 57 R 4 3 4 4 ; run; ... View more

Hi there,   Apologies for the delayed reponse on this, Custom strings are not appicable to just the navigation bar, they should work anywhere the application is getting a string from resources.json.   Many thanks Liz     ... View more

You might be better off using %PUT statements to determine the evaluation of your data. The data step you use will set the length of the variable CHECK to the length of the first variable. Which could result in truncation. Please see:   %let a=b; %let b= somethinglonger; data test; check="&a.";output; check="&b.";output; run; proc print data=test; run; compare with: %put A is: &a.; %put B is: &b.; ... View more

Please post AML questions into the Fraud forum. This gives you a better chance that someone with the right expertise pays attention to it.   I don't have implementation experience with AML7.1 but just some training some years ago. One of my takeouts from this training was that the AML7.1 UI is unlike 6.3 not customizable. You can ask via SAS TechSupport but I don't expect that there is much more public information available other than what you've got in the product documentation.   Having said that: The Core and KC data model is not that hard to understand so if you just need to have a better insight where data in the UI comes from then investigate the data models and things should become pretty clear. The UI is mid-tier and I don't expect that the underlying queries are publicly documented BUT if CORE and KC are in Oracle then you can of course retrieve all the queries issued by a user from the Oracle query history (talk to an Oracle DBA; you might not have the select privileges to these system tables and eventually some tracing options need to be turned on to get the queries in chronological order). Similar things should also be possible if the DB is SQL Server. ... View more