Hi,   I would suggest you consult with your IT group at the best way to handle authentication and logins.  This is not a SAS programming matter but a systems issue.  I would not recommend you try to do this yourself as your creation could become a major hole in your IT infrastrucure. ... View more

You actually have two problems to solve.  You also have to ensure that program A completes before program B begins.  The easiest way to do that is to create program C to run both A then B:   %include 'program_a.sas'; %include 'program_b.sas';   There are other approaches that involve PROC PRINTTO, but %INCLUDE should be easiest and safest. ... View more

Sounds like you need PROC HTTP, that's fairly similar to what you may be familiar with in Java/etc. ... View more

did you try to suppress information of SAS log, like that: options nosource nonotes errors=0; <...your code...> options source notes; ???     let me know have a nice day   MC ... View more

As I said, your best option will be to discuss this with your IT group and see what they can provide.  Its likely they can link the user directly in without further code.  Dealing with it yourself is quite dangerous.  Remember SAS creates a log file, if you take passwords and use them without anything further they can appear in the log - it just worries me that you might undermine the security of your whole system if you do not do these things properly. ... View more

There are lines in the script file that use the input statement to obtain the credentials. I would make a copy of the tcpunix.scr file that makes it easy (through comments) to identify those lines. Then use a scripted editor to replace the lines with input with a type statement that supplies userid and password, and save to a new file. Run that new script file when connecting. Remove that script file immediately after signing off, for safety reasons. Look if using proc pwencode makes sense to at least obscure the passwords.   I haven't found anything that lets the calling SAS process supply parameters to the scriptfile, or I would have used that. ... View more

My code is a mix of SCL and Base Programming because of which the macro variable "protpath" was getting resolved in the code. Using the below snippet resolved the problem:   %let match_string= %nrstr(procprinttoprint=%"&protpath/outlist/);    Thanks so much everyone for your input. This was urgently required. ... View more

Have you tested the Oracle client by itself? You should be able to go into the SQL Plus client and successfully run an SQL query. If you can't then the client isn't set up correctly.  ... View more

Some of our jobs hang like that.  We were able to fix it by putting -noterminal after the submission statement.  ... View more

Hi @LinusH: First I am establishing a connection to the SAS server on the remote UNIX server then I am creating the batch i.e batch.sas , by including some files like so:- %include "/pgmsetup/startup.sas"; %include "/backup/adhoc/AKReq34.sas"; Then I am submitting the batch by using statements like so:-   "nohup sas93 -noterminal /backup/adhoc/batch.sas -altlog /backup/adhoc/batch.log -print /backup/adhoc/batch.lst 2>/dev/null &"; ... View more

Yes, I think you have hit the nail on the head there KurtBremser.  The INSERTC command takes this form: rc=INSERTC(list-id,cval<,index<,name>>);   Now what is appears he is trying to do is use the iterator i to indicate if the value should be string1 or string2.  As I said its been a long time since I used this, so am fixed on arrays, or macro.  However the question I would say is why have string1/2/3 etc. as macro variables in the first place.  Why not insert these into a list of thier own: if anyspace(selpath) then do; stringlist=makelist(); stringlist=insertc(stringlist,"Path Should Not Contain Blank Spaces",1); stringlist=insertc(stringlist,"select another path",2); link errormsg; tmp_lstbtn._cursor(); return; end; SCL lists are the method for handling lists of values, so use them rather than creating macro variables?   ... View more

@Quentin: I have tried this..but its not working for me. Seems like SAS is unable to identify the windows module WNetGetConnectionA.  ... View more