ODS path is reset by SAS Enterprise Guide - sas

I added an ODS path statement in the autoexec_usermods.sas on the workspace server like this:
ods path mylibrary.templat(read) WORK.TEMPLAT(UPDATE)
SASUSER.TEMPLAT(READ) SASHELP.TMPLMST(READ);
When I run a SAS 9.2 session on the server I can see that the template store from my library is added to the ODS path as expected.
However, when I start a session from Enterprise Guide 4.2 the ODS path is still the default path. I know the session has included the autoexec_usermods.sas because libraries that are defined there are available in my session. I suspect that Enterprise Guide runs some code in the background when starting a session that resets or defines the ODS path to the default path. I found a macros.sas in C:\Program Files\SAS\Shared Files\Images which contains a ODS TMPLPATH statement but the path defined here is also different from the default. So my guess is this is not the correct file or there is other code executed somewhere.
Any help on this is appreciated.

You can add this statement to the SAS Enterprise Guide options to guarantee that it is submitted when you connect to your SAS server. You can find the option under:
Tools->Options->SAS Programs: "Submit code when connecting to SAS server"
Check the box and add the code that you want to run.
More information at:
http://www.sascommunity.org/wiki/Tips:Project_Specific_Autoexecs_in_Enterprise_Guide

Related

How to change the reference to the Oracle to SAS folder

I have a reference to a folder that is on Oracle, but the libraries have already been transferred to the SAS server. I do not know how to add / change to open the file outside Oracle
datafile="&glb_path.\01_projects\credit\_test\RCDT2021.xlsx"
dbms=excel replace;
sheet="RCDTCOD";
getnames=yes;
mixed=yes;
usedate=yes;
scantime=yes;```
This folder is 1: 1 already on shared disc. ```\01_projects\credit\_test\RCDT2021.xlsx"```

Stata: Ado package not found

I am looking to install the user-written 'esttab' of stata package 'st0085_2.pkg'. Normally I would type the following to do this:
net install st0085_2.pkg
In this case it outputs:
checking st0085_2 consistency and verifying not already installed...
installing into c:\ado\plus\...
file c:\ado\plus\next.trk already exists
r(602)
So I changed the ado directory path and install the ado to somewhere else (I cant delete next.trk without admin approval):
net set ado "U:\Documents\Stata\AMIE\ado"
net install st0085_2.pkg
The installation is successful but still the esttab command is unrecognized and I try and find where the ado is and it outputs that it has not yet been installed.
I don't see how STATA can say the ado-file already exists when downloading but when retrieving the package is not found? unless they are looking in different directories but even when I ado set a new path (I have tried many combinations) it still cannot find the package.
This is extra frustrating as I have used esttab on other computers.
While I doubt the original poster is still around, the answer may be interesting to others encountering the same situation.
The problem OP encounters here is that he does not have the correct rights to modify/delete the next.trk file in the default ado folder. Usually this happens when you do not have admin rights on a (heavily) locked-down server.
One solution is to copy the files directly: however, this can be rather tricky if the server is really locked down, or you have programs with unspecified dependencies.
The alternative is to change your ado folder. OP took the correct first step by altering the location of net install through net set ado "somefoldername". However, they missed the second step, which tells Stata "somefoldername" is part of the adopath.
This is done through adopath ++ "somefoldername". If I'm not mistaken, this only stays active as long as Stata is open. To make this "permanent", that line of code should be added to the profile.do dofile, which runs automatically at Stata startup. See the Stata FAQ for more information on the profile.do file.

Where Does "Toad for Oracle" saves the my sql queries from editor

I need to copy my sql queries to my own drive, I had created these queries using editor in toad for oracle 12.6..Can some one please help me out where is the folder that toad the my queries.?
Problem is that my toad is not working anymore and I need to re-install it so before that I want to get my saved sql files to my own drive.
The queries are saved in a file called:
SAVEDSQL.xml
This file is (in my case) under:
C:\Program Files\Quest Software\Toad for Oracle\User Files
Your saved SQL is stored in SavedSQL.dat. Its location will be... %APPDATA%\Dell\Toad for Oracle\12.6\SavedSQL.dat
If you back that file up you can restore your current installation to a "new install" state without actually reinstalling. Toad does nothing with its installation folder and the likelihood that something is corrupt with the installation is slim. Your user configuration files may have gone squirrely though. To restore your config files choose "Copy User Settings..." from the Utilities menu. Select the option to rest to a clean set. Toad will restart. Close Toad and copy your backed up savedsql.dat back to %APPDATA%\Dell\Toad for Oracle\12.6\SavedSQL.dat.
If you provide info on what it means for Toad to stop working there may be another issue we can resolve to save you from trashing your config files.
SavedSQL.xml contains lots of cryptic looking info about connections, but no scripts.
SavedSQL.dat does not exist
I should mention that I am using version 12.10 Toad for Oracle Xpert

Unable to open SAS EG Project

I can't open my SAS EG Project with the error message :
"Unable to open file ...abc.egp as valid project file"
This is happen because when my hard disk is full and I was trying to save the project, so it wouldn't let EG to finish writing the project changes.
I've tried to clear the history but no luck.
Thanks
I suspect your SAS EG file might be irreversibly corrupt, so the focus is then on recovery of the file or its content.
If your disk drive is NTFS based, you might be able to recover the file. Check for previous versions in the file properties.
Also, what was the structure of your file inside? If it was a code driven program, then you can make a copy of the file, change extension to "zip" and then unzip the file or look inside for its contents. SAS EG projects are just ZIP archives with XML maps and related SAS code.
The last option is to see if you have logging enabled in your SAS EG. If you do, then all the code you run on that date would be available in your logs, so you can recover the code from the logs.
Regards,
Vasilij

import file into SAS from DropBox

I have trouble with importing both excel and csv files into SAS. It is stored on DropBox on a folder I have locally mapped.
I have tried with:
proc import datafile="C:\Users\Maria\Dropbox\Speciale\skriveri\DATA\sas\csv\prove.xls"
out=data
dbms=xls
replace;
run;
The message in the log is:
ERROR: Physical file does not exist,
C:\Users\Maria\Dropbox\Speciale\skriveri\DATA\sas\csv\prove.xls.
NOTE: The SAS System stopped processing this step because of errors.
I have also tried importing a csv file by replacing xls with csv.
I have checked the path - it's correct and the file names are prove.csv and prove.xls.
I have a 64 bit computer, and tested with SAS 9.3 and 9.2.
I doubt if SAS is able to see the Dropbox folder. Try putting the file in " C:\Users\Maria\" and see what happens.