Another way of doing that was to build a wrapper script that replaced the default script that called the Oracle bulk-loader, and handle the RC problem in that script. But for 9.1.3 there is hot-fix for this particular problem, and it seems definitely solved in 9.2: http://support.sas.com/kb/13/759.html I haven't seen any similar problem with ODBC/SQL Server. /Linus ... View more

The Bulk Copy facility is available with LIBNAME using the BULKLOAD=YES option. /Linus ... View more

Basically, you paste you macro definition into the Source Code tab in the User Written Transformation. You can also define parameters that is set by the job that is using this transformation, they will automatically set as global macro variables. Some basic information about this exists in the DI Studio User Guide, ch 12. /Linus ... View more

Well, these are the refered macro variables. You should have these %put's right after your SQL that updates your DB2 tables. The contents of these macro variables will be printed to the SAS LOG. /Linus ... View more

SAS default behavior is to overwrite log-files etc. Are you sure that the previous SAS process has ended or that any other process/program (Notepad etc) is not locking the log file? Are you using the same user account? What user rights error message do you get? Typically, these kind of problems needs to be solved at the site by testing different thing, in order to narrow dow the problem, like testing different input programs, start from different directories, using different user account... In problems regarding user rights, maybe the Windows server administrator can help. Regards, LiInus ... View more

Maybe I misunderstood you. I thought you meant the physical table, but maybe you are referring to the transformation output table in the process. If this is the case, which transformation creates this output table, and what is the next step in your job? /Linus ... View more

Generally, transformation output tables are deleted upon the end of the job processing(that is at the en of the SAS session running the job). There is no silver bullet approach to remove intermediate WORK tables. Some transformations remove intermediate tables used within the transformation (tables that are not visible in the process designer). What you are asking for is some automatic way top delete tables that are not longer to any use further on in the job I guess it would be some messy logic for DI Studio to figure that out, including user written code/transformations. So, you can do some user written transformation that deletes those tables at proper locations (not so nice from a process design view), and insert a clean-up routine in the post process (in case you're WORK is a permanent storage or if you run several jobs within the same session). Another possibility is to use VIEWS as transformation output when it's possible. What is your concern, running out of temporary disk space? You can also build shorter jobs, which will automatically delete temporary tables at the job end. /Linus ... View more

Somtimes you can avoid them, often not. For instance some transformations can directly output to the target table, then avoiding the Table Loader. By using user written code you can also control processing more, but I don't recommend that kind of Process design, because it will undermine the benefits of what the tool is meant to do. But I'm not that you have worry too much about performance. Most transformations allow you to define the output tables as views, and having sufficient memory will allow the steps to be performed without costly disk I/O. If you have some crucial steps where performance is a real concern, you can override the default generated in those specific situations. Regards, Linus ... View more

If you run the process flow manually, are you running on the sp server then, or using a workspace server? It seems that the libnames might be assigned differently in these two situations. What output do you get if you add a proc datasets to your program? /Linus ... View more

You could start to investigate the SAS system options LOG, ALTLOG and LOGPARM (with WRITE=IMMEDIATE). Be sure to pint search paths to directories where the user that runs the program have write access. Try to run it interactively from a command prompt at the server, and maybe interactively in a DMS SAS session. Hope this helps, Linus ... View more

If this is from an official SAS paper, I think It would be legitimate to open a track on SAS support. /Linus ... View more

Maybe I'm on thin ice here, since I haven't done any coding (yet) with FCMP. But looking into some examples in the online doc, maybe I could suggest something anyway... It seems that if you are going to use the return() function, I think you are supposed to use the function name as argument, and also using the function name in the assignment statement as well. see: http://support.sas.com/documentation/cdl/en/proc/59565/HTML/default/a002890491.htm In your case, this would be: proc fcmp outlib = sasuser.FCMP_Cat.fcns; function SUMM(x,y); summ = x + y ; return(summ); endsub; quit; Hope this helps... Linus ... View more

Do you want to putput the name of your columns? PROC CONTENTS or PROC DATASETS may be used for that. I also suggest that take a couple of training classes, since most of your questions concern basic programming concepts in SAS. Regards, Linus ... View more

You can use PROC FORMAT to view the contents of your formats, either as tables or as a report, see on-line doc. To mange them you can use PROC FORMAT, PROC CATALOG, and if you are using DMS SAS the SAS Explorer window. /Linus ... View more

If this is strictly a BAS/Foundation installation, it's basically a installation issue. How to install/upgrade are covered by several documents in Install Center area in support.sas.com. SAS 9.2 is backward compatible, so nothing to worry about there. DI Studio: is this environment separated from the environment you plan to upgrade, if so, see above. If not: metadata server is not forward compatible with 9.2, at least, SAS is not supporting such a configuration (running 9.1.3 metadata server on a 9.2 Foundation). For this environment, you will have to wait to phase 2 in 9.2 roll-out. Regards, Linus ... View more