SAS Management Console, SAS IML Studio uses per default the private JRE delivered by SAS. In some cases SAS uses the standard JRE installed on the PC. For example SAS Enterprise Miner thin client which can be launched via Java Web Start. With us SAS EM 12.1 thin  client (which comes with SAS 9.3 TS1M2) works with Java JRE 1.8 Update 31. ... View more

Hi bnarang, you use ODBC connection defined on the SAS server. Maybe you should have a look on it. (odbc.ini). Do you access an Oracle database? If yes, ask your SAS-administrator to change the username to uppercase. You can define schema with your libname statement, too: libname abc odbc dsn = "xxx" schema = "YYY"; It is important to use uppercase schema-name with odbc connection for Oracle. Hopefully it helps. Regards, Sándor ... View more

Hi, with EG 5.1 it is possible to format a numeric column to a string: proc sql; create table work.xxx as select t1.id format=$CHAR25. from db.tb1 t1; quit; Regards, Sándor ... View more

ncsthbell, I say only that you do not need 3 database connections (usernames/passwords) if you have everything  in one database. After the execution of this SQL-script, you can manage in your SAS-program the Oracle connections (only) with your access. Regards, Sándor ... View more

If you have all data in one database,  your Oracle user can get select grants to the objects in the two other schemas. (--select 'GRANT SELECT ON SCHEMA_1.' || table_name || ' TO YOUR_ID;' from all_tables where owner='SCHEMA_1'; ) you can use your user in the libname statements: (same like from Hai.Kuo) libname schema_my oracle path=db schema=my authdomain=authmy;      libname schema_1 oracle path=db schema=one authdomain=authmy;      libname schema_2 oracle path=db schema=two authdomain=authmy; proc sql;                                                                                             connect to oracle (                                                                                 authdomain=authmy path=db"    );                                                                                                                                                                                                  create table my.myTable as                                                                       select                                                                                                *                                                                                                 from connection to oracle(                                                                            select * from one.TableName                                                                );                                                                                                  disconnect from oracle;                                                                           quit;                                                                                               ... View more

maybe you need a hotfix? 48126 - PROC MIXED might issue the message "integer overflow on computing amount of memory required" unnecessarily ... View more

we use winscp only with Unix servers. having SAS running on Windows server, I would create a share on it and map this share on my pc. ... View more

Hi, usually you can use putty, winscp without changing anything on the unix server. (SSH-connection is per default enabled (port 22) and preferred.) Regards, Sándor ... View more

"If you think an upgrade won’t be feasible, contact Technical Support (support@sas.com) and they can help you through your options." ... View more

does this U: drive point to a shared-filesystem on the Unix server, where SAS runs? (Samba-Share?, U:\ -> SAS_Server:/xx/yy) If yes, you can use PROC IMPORT without PC File Server, too. ... View more

Hi, you should give a try with PROC IMPORT. It supports Export/Import with XLS, XLSX files on Unix Platfrom, too. (SAS OnlineDoc: PROC IMPORT, Supported Data Sources and Environments) Regards, Sándor ... View more